KR100561678B1 - Mobile Communication Terminal Supporting Multi-Bearer and Method for Data Transmitting and Receiving Using the Same - Google Patents

Abstract

The present invention relates to a mobile communication terminal that supports the use of a plurality of bearers and a data transmission / reception method using the same.

Data transmission and reception method using a mobile communication terminal that supports the use of a plurality of bearers of the present invention, when the setup of the API layer module and bearer and the opening of the socket to provide an API for the execution of a wireless data-based application to the application. A data transmitting / receiving method using a mobile communication terminal for allowing wireless data-based applications executed on a mobile platform including a bearer manager and a bearer manager for registering a socket identifier to transmit and receive data using a plurality of bearers, the method comprising: A first step of assigning an identifier of the bearer to the application as an application requests setup of a bearer through the mobile platform; A second step of assigning an identifier of the socket to the application when the application opens the socket for the granted bearer identifier; Registering, by the application, the granted bearer identifier and socket identifier to the bearer management unit; The application includes a fourth step of transmitting data through a corresponding socket, and when the response data is received, checking the registered bearer identifier and the socket identifier and transferring the data to the corresponding application.

Bearer, Socket, Mobile Platform

Description

Mobile communication terminal supporting multiple bearer use and method for transmitting and receiving data using the same {Mobile Communication Terminal Supporting Multi-Bearer and Method for Data Transmitting and Receiving Using the Same}

1 is a first structural diagram of a mobile communication terminal supporting data transmission and reception using a conventional single bearer;

2 is a second structural diagram of a mobile communication terminal supporting data transmission and reception using a conventional single bearer;

3 is a structural diagram of a mobile communication terminal supported using a plurality of bearers according to an embodiment of the present invention;

4 is a structural diagram of a mobile communication terminal supported using a plurality of bearers according to another embodiment of the present invention;

5 is a flowchart illustrating a data transmission / reception process using a mobile communication terminal supported using a plurality of bearers according to an embodiment of the present invention.

<Description of Symbols for Main Parts of Drawings>

110, 120: application 200: mobile platform

210: API layer module 211: network bearer setup API

212: Network Socket Creation API 213: Server Connection API

214: socket registration API 220: bearer management unit

310, 320, 330: Bearer 311 ~ 314: Socket

410, 420: application 500: terminal S / W

510: application execution module 520: bearer management unit

610, 620, 630: Bearer 611 ~ 614: Socket

The present invention relates to a mobile communication terminal that supports the use of a plurality of bearers (bearer) and a data transmission / reception method using the same. When the setup of a bearer and opening of a corresponding socket are completed by a wireless data based application, By registering the identifier of the bearer and the identifier of the socket for the effective bearer use.

In the case of the existing mobile communication terminal, as shown in FIG. 1 and FIG. 2, the mobile terminal 20 is executed on the mobile platform 20 including the API layer module 21 which is a set of application programming interfaces (APIs) for executing the applications 11 and 12. The various applications 11 and 12 or the various applications 41 and 42 executed on the application execution module 50, which is the software (S / W) area of the terminal, are simultaneously connected to one radio bearer 30 or 60. Only was available.

Therefore, in the related art, several application applications 11, 12, 41, and 42 simultaneously open and use sockets 31 to 34 and 61 to 64 using one radio bearer 30 and 60. In this case, since there is only one bearer 30, 60, there is no need to manage the bearer socket.

Currently, as the wireless data environment develops, a wireless multi-bearer that can be simultaneously supported by one mobile communication terminal is supported, such as a concept in which multiple LAN cards are simultaneously used in one PC in a wired line.

The type of mobile communication terminal that supports the use of multiple bearers is the multiple primary PDP CONTEXT (Packet Data Protocol) of the WCDMA terminal, where the concept of the multiple primary PDP CONTEXT is derived from 3GPP and various QoS (Quality) Simultaneous use of a logical or physical bearer supporting the of service means that the mobile communication terminal is supported.

Therefore, as application applications using a plurality of bearers are developed at the same time, when various application applications communicate simultaneously in a wireless environment in which a plurality of bearers are supported, a socket for a plurality of bearers used for each application is managed. Function is required.

Accordingly, the present invention is to solve the above-mentioned disadvantages and problems of the prior art, a variety of applications based on wireless data in a variety of mobile communication terminal supporting a plurality of bearers effectively a plurality of bearers and a plurality of sockets. It is an object of the present invention to provide a mobile communication terminal that supports the use of a plurality of bearers to enable use and a data transmission / reception method using the same.

The object of the present invention is to move the wireless data-based applications running on the mobile platform including an API layer module that provides an API for the execution of the wireless data-based application to transmit and receive data using a plurality of bearers. As a communication terminal, the mobile platform further comprises a bearer management unit for registering a bearer identifier and a socket identifier for a corresponding application when setup of a bearer and opening of a socket are performed through an API provided by the API layer module. When the setup of the bearer and the opening of the socket are completed, the application registers a bearer identifier and a socket identifier to the bearer management unit so that data is transmitted to the corresponding application through the registered bearer identifier and the socket identifier. complex Using the bearer is achieved by a mobile communication terminal that supports the data transmission and reception.

Another object of the present invention is to set up a bearer identifier and a socket identifier for a corresponding application when setup of an API layer module and a bearer for providing an API for executing a wireless data-based application and opening of a socket are performed. A data transmission / reception method using a mobile communication terminal that enables wireless data-based applications executed on a mobile platform including a management unit to transmit and receive data using a plurality of bearers, wherein the application setups a bearer through the mobile platform. Providing a bearer identifier to the application in response to the request; A second step of assigning an identifier of the socket to the application when the application opens the socket for the granted bearer identifier; Registering, by the application, the granted bearer identifier and socket identifier to the bearer management unit; And a fourth step of transmitting data to the application through the corresponding socket when the application transmits data through the corresponding socket and the response data is received. A data transmission and reception method using a mobile communication terminal supporting data transmission and reception using a bearer is achieved.

Details of the above objects and technical configurations of the present invention and the effects thereof will be more clearly understood by the following detailed description based on the drawings showing the preferred embodiments of the present invention.

First, FIG. 3 is a structural diagram of a mobile communication terminal supported using a plurality of bearers according to an embodiment of the present invention.

As shown, the mobile communication terminal according to the present invention includes a mobile platform 200 supporting a plurality of bearers (310 ~ 330) for executing a plurality of wireless data-based applications (110, 120) It is composed.

The mobile communication terminal allows a plurality of applications 110 and 120 to open and receive a plurality of sockets 311 to 314 corresponding to the bearer 310 to transmit and receive data, and for this purpose, the bearer 310 and The sockets 311 to 314 each have an identifier.

In addition, the mobile platform 200 includes a bearer 310 set up for the API layer module 210 and the applications 110 and 120 that provide an API as a function for the execution of the applications 110 and 120. The bearer manager 220 that stores identifier information for the sockets 311 to 314 supports the use of a plurality of bearers.

In more detail, the API layer module 210 includes a network bearer setup API 211 for setting up a bearer 310 to enable communication for executing a wireless data-based application 110, 120, and the bearer. A network socket creation API 212 for creating sockets 311 to 314 for 310, and a server connection API 213 for attempting to connect to a server through the generated sockets 311 to 314. .

In addition, the API layer module 210 is an API for supporting a plurality of bearers, and the data transmitted through the socket using the bearer identifier and the socket identifier for the application 110 or 120 to be executed on the platform as parameters. It further includes a socket registration API (214) for specifying a bearer to use when transmitting and receiving.

The respective APIs will be described in more detail as follows.

First, the network bearer setup API 211 is for attempting to access the Internet for the execution of an application. Before the socket is used, this API must be called to enable the Internet access so that TCP / IP communication through the socket is possible.

The network bearer setup API 211 is a function to be called for each application. Even if another application previously allows the network access by calling the network bearer setup API, the socket cannot be used unless the current application calls it.

The prototype of the network bearer setup API 211 is M_Int32 MC_net Connect (NETCONNECTCB cb, void * param), and uses a callback function cb that is called when the access succeeds or fails as a parameter.

The network bearer setup API returns "0" when the Internet access succeeds, "M_E_INPROGRESS" when the corresponding application or another application attempts to access the Internet, and when the Internet access is already allowed for this application. Returns "M_E_ISCONN" and "M_E_ERROR" if other errors occur.

Next, the network socket creation API 212 for creating a socket for the bearer is an API for creating a socket for TCP or UDP communication, and accesses the Internet through the network bearer setup API 211 before the API is called. Should be allowed.

The prototype of the network socket creation API 212 is M_Int32 MC_netSocket (M_Int32 domain, M_Int32 type). The parameter "domain" indicates a communication domain, and in the case of an Internet socket, "AF_INET", and "type" is a socket. MC_SOCKET_STREAM indicating that the socket is based on TCP or MC_SOCKET_DGRAM indicating that the socket is based on UDP is possible.

The network socket creation API 212 uses a socket identifier as a return value when the socket creation is successful. When the socket creation fails, "M_E_NOTSUP" when the domain or type is not supported, and "M_E_NOTCONN when internet access is not allowed." Returns "M_E_NOSPACE" if the socket can no longer be created and "M_E_ERROR" for other errors.

Next, the server connection API 213 for attempting to connect to the server through the socket created as described above attempts to connect to the server through a TCP socket. The prototype of the API 213 is M_Int32 MC_netSocketConnect (M_Int32 fd, M_Int32 addr, M_Int16 port, NETSOCKCONNECTCB cb, void * param).

The parameter of the function "fd" is the socket identifier, "addr" is the address of the server, "port" is the port number of the server, "cb" is a callback function called when the connection is successful or failed, and "param" is Represents the value passed when the callback function is called.

The server connection API 213 returns "0" if the server connection is successful, "M_E_NOTSUP" for a socket that does not support this function, "M_E_BADFD" for an invalid socket identifier, and Internet access is not possible. "M_E_NOTCONN" if it is already connected to the server, "M_E_ISCONN" if the connection is already in progress, "M_E_INPROGRESS" if the connection is already in progress, "M_E_INVALID" if the address is invalid or if the callback function is NULL. Can return "M_E_ERROR".

Finally, the socket registration API 214, which is an API for supporting a plurality of bearers, is used to specify which bearer the data transmitted through the socket will use to send and receive data. The prototype is M_Int32 OEMH_netSocketRegister (M_Int32 context_id, M_Int32 fd).

The parameter of the function "context_id" represents [in] NSAPI, i.e., the bearer identifier, and "fd" represents the [in] socket identifier. The socket registration API 214 returns "0" on success, "M_E_INVALID" in case of wrong context_id or fd, and "M_E_ERROR" in case of other error.

Next, the bearer manager 220 performs setup of the bearer and the opening of the socket through the APIs 211 and 212 provided by the API layer module 210. 110) Register the bearer identifier and the socket identifier for 120.

Accordingly, when data is received from the mobile communication terminal on which the plurality of applications 110 and 120 based on the wireless data are executed on the mobile platform 200, the mobile platform 200 may bear the bearer manager 220. The bearer and the socket for each application registered in the identifier are checked to transmit data to the corresponding application 110 or 120.

Next, FIG. 4 is a structural diagram of a mobile communication terminal supported using a plurality of bearers according to another embodiment of the present invention, in which bearer management is not performed on a platform as shown in FIG. It is shown.

As shown, the mobile communication terminal according to another embodiment of the present invention, the application execution module 510 which is the execution base of the application 410, 420, and the plurality of wireless data-based applications 410, 420 And a software area 500 including a bearer manager 520 supporting a plurality of bearers 610 to 630 for execution.

The mobile communication terminal allows a plurality of applications 410 and 420 to open and receive a plurality of sockets 611 to 614 corresponding to the bearers 610 to 630 to transmit and receive data. 630 and the sockets 611 to 614 each have an identifier.

In addition, the bearer manager 520 may set up the bearers 610 to 630 and open (create) the sockets 611 to 614 to execute the applications 410 and 420. Register a bearer identifier and a socket identifier for 420.

That is, the applications 410 and 420 register the bearer identifier and the socket identifier in the bearer manager 520 when the setup of the bearers 610 to 630 and the opening of the sockets 611 to 614 are completed. Allows data to be passed to the application through the bearer identifier and the socket identifier.

A method of transmitting and receiving wireless data in a mobile communication terminal according to the present invention as described with reference to FIGS. 3 and 4 will now be described with reference to FIG. 5.

5 is a flowchart illustrating a data transmission / reception process using a mobile communication terminal supported using a plurality of bearers according to an embodiment of the present invention.

In the meantime, the description of the mobile communication terminal is divided according to the difference between the execution base of the application and the area provided by the bearer management unit, as shown in FIGS. 3 and 4. For convenience of description, the mobile communication terminal of FIG. 3 will be described.

As shown, when the application 110 requests the setup of the bearer 310 through the mobile platform 200 (S101), the mobile platform 200 receives the identifier of the bearer 310, the application 110 To give (S102).

In addition, when the application 110 opens the socket 311 for the granted bearer identifier (S103), the application 110 is given an identifier of the socket (S104).

Next, the application 110 registers the granted bearer identifier and socket identifier to the bearer manager 220 of the mobile platform 200 (S105). In this case, the bearer manager 220 may be configured in the platform 200 in the case of the application application 110 on the terminal platform 200, or in the software of the terminal.

In the case of the application 110 running on the mobile platform 200, the API layer module 210 of the mobile platform 200 uses the bearer identifier and the socket identifier for the application 110 to be executed as parameters to the corresponding socket 311. And a socket registration API 214 for designating a bearer 310 to be used when transmitting and receiving data transmitted through the network), and registering a bearer identifier and a socket identifier in the bearer management unit 220 may include registering the socket. This is done via API 214.

Next, the application 110 transmits data through the corresponding socket 311 (S106), and when the response data is received, the application 110 checks the bearer identifier and the socket identifier registered in the bearer management unit 220 to check the corresponding application ( Data is transmitted to 110 (S107).

On the other hand, as described above, the setup of the bearer for the application 110, the opening of the socket, and the registration process for each identifier are identically repeated when communication through the plurality of sockets 311 to 314 is required.

At this time, the setup of the bearer and the opening of the socket and the registration for each identifier are performed on the plurality of applications 110 and 120, and then the sockets 311 (311) in which the respective applications 110 and 120 are opened. When data is transmitted through 312 to receive response data for each transmitted data, the platform (or S / W) of the terminal checks and receives a bearer identifier and a socket identifier designated for each application in the bearer manager 220. Divided data and transfer the data to the corresponding application 110 or 120.

As those skilled in the art to which the present invention pertains may implement the present invention in other specific forms without changing the technical spirit or essential features, the embodiments described above are exemplary in all respects and are not intended to be limiting. You must do it. The scope of the present invention is shown by the following claims rather than the detailed description, and all changes or modifications derived from the meaning and scope of the claims and their equivalents should be construed as being included in the scope of the present invention. do.

Accordingly, in the mobile communication terminal and the data transmission / reception method using the same, the use of a plurality of bearers of the present invention, various applications based on wireless data are effectively applied to a plurality of bearers and a plurality of bearers in various types of mobile communication terminals supporting a plurality of bearers. The effect is that sockets can be used.

Claims (6)

A mobile communication terminal including a mobile platform that supports a plurality of bearers for executing a wireless data-based application, wherein the plurality of applications open a plurality of sockets corresponding to the bearers to transmit and receive data. The mobile platform, An API layer module providing a plurality of APIs for allowing the plurality of applications to transmit and receive data through the plurality of bearers; When a bearer setup and opening of a socket are performed through an API provided by the API layer module by a specific application, a bearer manager that registers a bearer identifier and a socket identifier for the corresponding application through an API provided by the API layer module is performed. ; Including; When a plurality of applications are executed through different bearers on the mobile platform, when the mobile platform receives data through a specific bearer and a socket, the mobile platform checks a bearer identifier and a socket identifier registered for each application to the bearer manager. And a mobile communication terminal supporting data transmission and reception using a plurality of bearers, characterized in that data is transmitted to a corresponding application. The method of claim 1, The API layer module, A network bearer setup API for setting up a bearer to enable communication for wireless data based application execution; A network socket creation API for creating a socket for the bearer; A server connection API for attempting a server connection through the created socket; And A socket registration API for specifying a bearer to be used for transmitting and receiving data transmitted through the socket, using the bearer identifier and the socket identifier for the application to be executed as parameters; A mobile communication terminal supporting data transmission and reception using a plurality of bearers, comprising a. In the mobile communication terminal including an application execution module for supporting a plurality of bearers for executing a wireless data-based application, the plurality of applications open a plurality of sockets corresponding to the bearer to transmit and receive data , A bearer manager configured to register a bearer identifier and a socket identifier for the corresponding application when the bearer is set up and the socket is opened by a specific application; Including; When the application execution module receives data to the mobile communication terminal through a specific bearer and a socket when a plurality of applications are executed through different bearers on the application execution module, a bearer identifier and a socket registered for each application in the bearer management unit. A mobile communication terminal supporting data transmission and reception using a plurality of bearers, characterized in that the identification is confirmed, and data is transmitted to the corresponding application. When the setup of the bearer and the opening of the socket are performed, the API layer module providing an API for executing the wireless data based application is executed on the mobile platform including a bearer manager for registering the bearer identifier and the socket identifier for the application. A data transmission / reception method using a mobile communication terminal that enables wireless data-based applications to transmit and receive data using a plurality of bearers, A first step of assigning an identifier of the bearer to the application as the application requests setup of a bearer through the mobile platform; A second step of assigning an identifier of the socket to the application when the application opens the socket for the granted bearer identifier; Registering, by the application, the granted bearer identifier and socket identifier to the bearer management unit; Transmitting, by the application, data through the socket, and confirming the registered bearer identifier and the socket identifier when the response data is received, and transmitting the data to the application; Data transmission and reception method using a mobile communication terminal that supports data transmission and reception using a plurality of bearers, characterized in that comprises a. The method of claim 4, wherein The API layer module includes a socket registration API for designating a bearer to be used when transmitting and receiving data transmitted through a corresponding socket using a bearer identifier and a socket identifier for an application to be executed as parameters. The third step is a data transmission and reception method using a mobile communication terminal that supports data transmission and reception using a plurality of bearers, characterized in that performed through the socket registration API. Wireless data-based applications running on an application execution module including a bearer management unit for registering a bearer identifier and a socket identifier for the application for the execution of the wireless data-based application to transmit and receive data using a plurality of bearers. A data transmission and reception method using a mobile communication terminal, Giving an identifier of the bearer to the application as the application requests setup of a bearer through the application execution module; A second step of assigning an identifier of the socket to the application when the application opens the socket for the granted bearer identifier; Registering, by the application, the granted bearer identifier and socket identifier to the bearer management unit; Transmitting, by the application, data through the socket, and confirming the registered bearer identifier and the socket identifier when the response data is received, and transmitting the data to the application; Data transmission and reception method using a mobile communication terminal that supports data transmission and reception using a plurality of bearers, characterized in that comprises a.

Images