KR100446638B1 - Packet terminal capable of supporting multiple packet calls and method for supporting multiple packet calls in the same - Google Patents

Abstract

The present invention relates to a packet terminal capable of supporting multiple packet calls and a method for supporting multiple packet calls in the packet terminal, wherein the packet terminal capable of supporting multiple packet calls is a packet terminal capable of using a packet service by accessing a packet mobile communication network. When setting a packet data protocol for a packet service required by a user, a delimiter for distinguishing each protocol layer constituting a protocol with the packet mobile communication network is set to be different according to the packet service. It is characterized by distinguishing a plurality of packet data protocols by linking the delimiters for each layer. According to the present invention, since one packet terminal can simultaneously provide various types of services in one packet mobile communication system, services having different resource allocation requirements such as voice, video, and data services can coexist.

Description

Packet terminal capable of supporting multi-packet call and method of supporting multi-packet call in this packet terminal

The present invention relates to a packet terminal capable of supporting packet services in an IMT-2000 (International Mobile Telecommunications-2000) asynchronous packet mobile communication system. In particular, a packet terminal capable of supporting multiple calls and multiple packets in the packet terminal To call support methods.

Currently, packet service based on internet service is evolving into various forms regardless of wired or wireless network.

In addition, various types of services (voice, video, etc.), which are based on circuit networks, are attempting to evolve into packet networks.

In order to accommodate various multimedia services as described above, the limits, performance, capacity, and efficiency of radio resources are basically different in packet mobile communication systems.

Similarly, a terminal for supporting packet services should be able to accommodate various multimedia services at the same time. Since these services that are simultaneously accommodated require conditions of different radio resources, call establishment for providing these services should be made independently. do.

As such, there is a Korean Patent Application Publication No. 2001-46636 as a technology for a radio call processing method for overcoming a problem such as a limitation of radio resources. This technique is based on the fact that the base station knows the available resources when an arbitrary call setup is required from the mobile station, and has a lower class of service than the requested call if it is determined that it does not satisfy the quality of service (QoS) of the requested call. Pause the service of the call in service of the service, characterized in that the service of the requested call is made, but as described above by satisfying the requirements such as providing a variety of multimedia services by setting up a multi-packet call from the same terminal I can't give it.

As a result, in the conventional asynchronous IMT-2000 packet terminal, only one packet call has been set up to provide a service within the range, and various multimedia services are not provided because the call setup itself does not provide a system that independently operates a plurality of calls. There is a problem that it is difficult to accommodate at the same time.

Accordingly, an object of the present invention is to solve the above-described problems, and in a packet mobile communication system, one packet terminal supports multiple calls, so that various application services can be simultaneously accommodated in the one packet terminal. A packet terminal capable of supporting multiple calls in a mobile communication system and a method for supporting multiple packet calls in the packet terminal are provided.

1 is a block diagram of an IMT-2000 packet service system according to an embodiment of the present invention.

2 is a software functional block diagram of an MT of an IMT-2000 packet system according to an embodiment of the present invention.

3 is a flowchart of a multi-packet call support method in MT of an IMT-2000 packet service system according to an embodiment of the present invention.

4 is a diagram illustrating a multi-packet call processing table stored in an MT of an IMT-2000 packet service system according to an embodiment of the present invention.

A packet terminal capable of supporting multiple packet calls according to a feature of the present invention for achieving the above object,

A packet terminal capable of using a packet service by accessing a packet mobile communication network, the packet terminal comprising: a user matching block configured to perform a user interface and an environment setting operation; An internet protocol block connected to the user matching block and configured to deliver all packet service data including mobile internet protocol data; A session management block connected to the Internet protocol block and performing a packet data protocol and session management operation; And a radio resource management block connected to the session management block and the packet mobile communication network, the radio resource management block performing radio resource management and signal connection management operations, wherein a first separator is formed between the user matching block and the Internet protocol block. A second delimiter between the protocol block and the session management block, and a third delimiter between the session management block and the radio resource management block, and the first delimiter, the second delimiter, and the third delimiter according to the packet service. The method may be configured differently, and the multi-packet call may be set by distinguishing packet calls corresponding to a plurality of packet services by linking the first delimiter, the second delimiter, and the third delimiter.

Here, the first identifier is a Call Identifier (CI) which is a connection identifier for identifying a packet call connection, and the second identifier is a Network Service Access Point (NSAP), an identifier for identifying connections in a network. The third delimiter is an RB number allocated to the packet mobile communication network.

The packet terminal may further include a packet data transfer block connected to the radio resource management block and the Internet protocol block and performing a substantial transfer of packet service data with the packet mobile communication network. The second delimiter and the third delimiter are stored in one table, and the table is managed by the packet data transfer block.

The packet data delivery block includes a manager Packet Data Convergence Protocol task for packet service, and the manager PDCP task includes an agent PDCP task whenever a packet data protocol corresponding to a user's packet service request is set. agent PDCP task), and the corresponding PDPD task is called by using the identifiers stored in the table.

In addition, a multi-packet call support method in a packet terminal according to an aspect of the present invention,

A method of supporting a multi-packet call in a packet terminal capable of using packet service by accessing a packet mobile communication network, the method comprising: a) another packet call that is already in service according to a packet service request from a user; Establishing a new packet call including a delimiter that can be distinguished from and; And b) accessing the packet mobile communication network using a packet call distinguished through a delimiter corresponding to the packet service when receiving a packet service data request from a user, and performing the packet service data reception. The delimiter is a first delimiter between the user matching block and the internet protocol block, a second delimiter between the internet protocol block and the session management block, and a third delimiter between the session management block and the radio resource management block. Include.

Wherein step a) comprises: i) requesting radio resource allocation to the packet mobile communication network according to a packet service request from the user; ii) allocating a radio resource corresponding to the packet service request by the packet mobile communication network according to the radio resource allocation request; And iii) setting an environment according to the radio resource allocated in step ii).

In addition, in step iii), a separator for distinguishing the packet call is stored in a specific table.

In addition, the step b), iv) using the identifier corresponding to the packet service from the user to distinguish the corresponding packet call; v) requesting packet service data by accessing the packet mobile communication network through the packet call classified in step iv); vi) classifying a corresponding packet call using an identifier corresponding to packet service data provided according to the request in step v); And vii) receiving the packet service data through the packet call classified in step vi).

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a block diagram of an IMT-2000 packet service system according to an embodiment of the present invention.

As shown in FIG. 1, the IMT-2000 packet service system according to an embodiment of the present invention includes a packet terminal 10, 20, a general packet radio service (GPRS) / universal mobile telecommunications system (UMTS) core network 30, 40. ), An external data network (Public Domain Network (PDN) 50), and interface protocols between them (R interface, Uu interface, Ui) Interface, Gp interface, Gi interface, etc.).

The packet terminal consists of a terminal equipment (terminal equipment (hereinafter TE) hereinafter 10), a mobile terminal (mobile terminal (hereinafter referred to as MT) 20), and an R interface which is an interface between them.

The mobile subscriber may access the MT 20 using a TE 10 such as a notebook or a general personal computer to provide packet data services such as the Internet.

The TE 20 of the packet terminal and the GPRS / UMTS core network 30 are connected to the Um / Uu interface, which is a UMTS interface. The Um / Uu interface is an interface between the mobile station and the GPRS fixed network part. As an interface supporting data services, the Um interface is a UMTS interface, and the Uu interface is an Iu interface, which is an interconnection point between a base station controller and a core network.

The interface between the GPRS / UMTS core network 30 and the external data network PDN 50 uses a Gi interface, which is a reference point between the GPRS and the external packet data network.

In addition, the interface between the GPRS / UMTS core network 30 and another GPRS / UMTS core network 40 is standardized as a Gp interface, which is a GPRS Support Network (GSN) in another Public Land Mobile Network (PLMN). Is the interface between.

In the IMT-2000 packet system having the structure of FIG. 1, a packet terminal for providing a packet service, in particular, the MT 20 has a software configuration as shown in FIG.

2 is a software functional block diagram of an MT 20 of an IMT-2000 packet system according to an embodiment of the present invention.

The user registration block 200 is connected to the TE 10 to perform a user interface and configuration work.

The session management function block 210 is connected to the user matching block 200 and performs packet data protocol and session management tasks.

The packet terminal mobility management block 220 is connected to the session management block 210 and performs subscriber management and mobility management tasks of the packet terminal.

The radio resource management block 230 is connected to a base station / control station connected to the packet terminal mobility management block 220 and the GPRS / UMTS core network 30 and performs radio resource management and signal connection management.

The text service function block 240 is connected to the user matching block 200, the packet terminal mobility management block 220, and the radio resource management block 230, and performs a protocol processing task for a short text service.

The text service data delivery block 250 is connected to the radio resource management block 230 and performs a task of delivering and managing data defined and generated by the text service function block 240.

The mobile IP block 260 is connected to the user matching block 200 and performs an IP mobile protocol processing task for providing IP mobility of the MT 20.

The internet protocol block 270 is connected to the user matching block 200, the session management block 210, and the mobile IP block 260, and performs a task of delivering all packet service data including mobile IP protocol data.

The packet data delivery block 280 is connected to the radio resource management block 230 and the internet protocol block 270 and performs a substantial transfer of packet service data.

The radio link management block 290 is connected to a base station / control station connected to the radio resource management block 230, the text service data transfer block 250, and the GPRS / UMTS core network 30, and is generated in these blocks. Perform reliable delivery and management of all controlled data.

Among the blocks, data management for packet multi-call management is related to a user interface block (UI) block, an IP (Internet Protocol) block including a Point to Point Protocol (PPP) function block, a PDCP block, and an SM ( A session management block, a packet mobility management (PMM) block, a radio resource control (RRC) block, and a radio link control (RLC) block.

Here, the UI block is the user matching block 200, the IP block is the Internet protocol block 270, the PDCP block is the packet data delivery block 280, and the SM block is the session management function block 210. The PMM block refers to the packet terminal mobility management block 220, and refers to the mobility management layer of the packet terminal. The RRC block refers to the radio resource management layer 230, and the RLC block refers to the radio. Corresponds to link management block 290.

Serving GPRS Support Node (SGSN) is a packet switching device that stores location information of each terminal in order to provide GPRS service to a subscriber, and performs subscriber authentication and matching function with Gateway GPRS Support Node (GGSN).

The GGSN is a packet network switching device that assigns an IP address to a user requesting packet service, delivers packet data from SGSN to an external packet network, and performs a tunneling function to deliver external packet data to a subscriber.

Therefore, when the packet service is started, various messages are sequentially transmitted from the TE 10 to the MT 20, the session management layer, the mobility management layer of the packet terminal, and the radio resource management layer, and then the GPRS is transmitted through the packet switching device / packet network switching device. The response message transmitted to the / UMTS core network 30, and transmitted from the GPRS / UMTS core network 30, is transmitted to the MT 20 in the reverse order through the packet switching apparatus / packet network switching apparatus.

Hereinafter, a multi-call support method of the MT 20 in the IMT-2000 packet service system according to an embodiment of the present invention will be described with reference to FIGS. 3 and 4.

First, when the MT 20 is turned on, all tasks are initialized and packet service may be started from this time (S100).

As such, when packet service is started, tasks of all blocks related to packet service are activated and wait for data to be received. At this time, data is received from either the TE 10 or the GPRS / UMTS core network 30, and the received data is divided into control data for establishing a packet service based environment and service data for actual service. Therefore, when data is received from the outside, it is first determined whether the received data is control data or service data (S102).

First, when received data is received from TE 10, it is determined whether or not the control data is a PPP block of IP. However, when the received data is received from the GPRS / UMTS core network 30, when the data received through the PHY layer is delivered to the RLC via the MAC, the RLC determines whether the RRC data or the PDCP data is based on the received data header. If it is RRC data, it is determined as control data, and if it is PDCP data, it is determined as service data.

If it is determined that the data received from the outside in the determination step (S102) as the control data, whether the upstream data transmitted from the TE (10) to the GPRS / UMTS core network (30) or vice versa in the GPRS / UMTS core network (30) Whether or not the downlink data transmitted to the TE (10) should be determined (S104). This determination may be performed in IP or RLC as in the determination of whether the control signal is present.

If the data received in step S104 is determined to be uplink data, the uplink data received at the beginning of the packet service is data for requesting the first call setup, so that the PPP block removes the UI block of the MT 20 from the TE 10. At the same time, the APN 400 and the CI 600, which are received through the AP 600, are stored and managed, and the requested packet call connection data is transferred to the SM block (S106). Here, APN 400 is unique data for identifying a packet terminal user, and CI 600 is a connection identifier for identifying a packet call connection.

Next, the SM block receiving the packet call connection data from the PPP block manages the NSAP 700 and simultaneously transmits the currently required request data to the PMM block, which is a lower protocol (S108). Here NSAP 700 is an identifier that can identify connections at the network layer.

Next, the PMM block receiving the request data from the SM block manages the International Mobility Service Identifier (IMSI) 300 and transmits the request data to the RRC block, which is a radio resource management layer (S110). Here, the IMSI 300 is a terminal identifier that can distinguish terminals worldwide.

The RRC block, which has received the request data from the PMM block, transmits a message requesting radio bearer (hereinafter referred to as RB) to the GPRS / UMTS core network 30 and then is delivered from the GPRS / UMTS core network 30. The state transition is performed in the standby mode for receiving data (S112).

Meanwhile, in the GPRS / UMTS core network 30, when a message requesting radio resource allocation is transmitted from the MT 20, the GPRS / UMTS core network 30 allocates a radio resource necessary for the requested call and transmits the result to the MT 20. Here, the available radio resources to be allocated to the call requested from the MT 20 may not be secured. In this case, since the corresponding resources may be allocated by a repetition request or the like, the present embodiment will be described under the assumption that the available radio resources are secured. .

When the radio resource allocation result is received in the GPRS / UMTS core network 30, since the radio resource allocation result is downlink control data, the RRC block in the standby state is operated through the steps S100, S102, and S104.

The RRC block receives the radio resource allocation result transmitted from the GPRS / UMTS core network 30 (S114) and transmits a reception response thereto to the GPRS / UMTS core network 30 (S116). Thereafter, the environment is set according to the performance of the resources allocated to the PDCP to actually transmit and receive packet service data through the allocated radio resources (S118). At this time, the management of the radio resource number (RB Number, 800) is also performed at the same time.

When the environment setting is completed in step S118, the PDCP switches to a service operation mode capable of packet service (S120).

Meanwhile, the RRC block receiving the resource allocation result in step S114 immediately receives a PDP (Packet Data Protocol) generation result, which is a message of an application layer, and transmits the result to the PMM and SM (S122). If the PDP generation result is unsuccessful, it is restarted in the packet service start step (S100). If the PDP generation result is success, the PMM block, the SM block, and the PPP block respectively perform the PDP generation result reception process. That is, according to the PDP generation result, the related data, for example, IMSI 300, APN 400, IP 500, CI 600, NSAP 700, are included in the multiple call processing routing table shown in FIG. , RB number 800 and the like are delivered to the PDCP block, and the PDCP block stores the corresponding data in the multi-call processing routing table (S124).

Here, the PDP has different parameter values according to the characteristics of the packet service.These parameters include maximum service data unit size, up / down maximum bandwidth, and minimum bandwidth (up / down). guaranted bandwidth, allowable delay, and data throughput. These parameters vary in value depending on the type of service to be provided.

Thereafter, the SM block transmits the PDP generation result to the UI block requesting packet call setup through the PPP block (S124).

As such, after the control step for signal setup according to the call setup request by the TE 10 is completed, the actual service data can be transmitted and received via the MT 20 between the TE 10 and the GPRS / UMTS core network 30. The mode is changed. Therefore, from now on, transmission and reception of service data between the TE 10 and the GPRS / UMTS core network 30 will be described.

From the MT 20 side, service data transmission between the TE 10 and the GPRS / UMTS core network 30 is divided into uplink data and downlink data. That is, after the packet service start step (S100), the control data determination step (S102) is determined as the service data, the upstream data determination step (S130) is performed, and in this step (S130) whether the service data is uplink data or downlink data. It is divided accordingly.

First, if the service data is uplink data transmitted from the TE 10 to the GPRS / UMTS core network 30, the data requested by the user is transferred to the PPP block via TCP / IP or UDP / IP, which is an Internet protocol layer ( S132), the PPP block is transmitted to the PDCP block which processes the IMT-2000 packet data again (S134). At this time, the multiple call processing routing table stored in the step S124 is referred to.

Next, the PDCP block transfers the data transmitted from the PPP block to the RLC block by specifying the RB number 800 and the like by referring to the multi-call processing routing table (S136), and the RLC block transfers the data back to the lower layer (MAC / PHY) is transferred to the GPRS / UMTS core network 30 using the already allocated RB and then returns to the data receiving mode to wait for data reception (S138 and S140).

On the other hand, if it is determined in step S130 that the service data is the downlink data transmitted from the GPRS / UMTS core network 30 to the TE 10, the corresponding data is passed through the lower protocol (PHY / MAC / RLC) through PDCP. The block is transferred to the block (S142), and the PDCP block transfers the PPP block after processing the corresponding function (S144).

Next, the PPP block transfers the data transferred from the PDCP block to a user interface program, for example, a web browser, an FTP interface, etc. (S146), and the user interface program performs a service process on the transferred data (S148). .

Through the above process, a packet service for processing multiple calls can be accommodated. In this process, reference to multiple calls involves UI block / PPP block / SM block / PMM block / RRC block / RLC block when establishing and releasing a call, and UI block / PPP block when serving through the set call. / PDCP block / RLC block, etc. are involved. These related blocks support multiple calls with reference to the multiple call processing routing table shown in FIG.

An important block for supporting a plurality of packet calls here is a PDCP block. Conventionally, a PDCP block in a system in which a plurality of packet calls are not supported exists as a single independent task and informs the PDCP task of shape data or packet call setup and release related status data directly. Whenever a manager PDCP task exists and a packet call is established, agent tasks are generated to view the identifiers stored in the multi-call processing routing table and to call the task to interface with the RRC block and the RLC block. .

As shown in Fig. 4, the IMT-2000 packet terminal has an IMSI 300 value which is a unique number worldwide. The packet terminal has an IP address with the IMSI 300 and manages the APN 400 according to the characteristics of each terminal subscriber.

The IMSI 300 value is a value held by the terminal from the beginning and is unique worldwide. In other words, the number is assigned according to the rules recommended by the 3GPP specification as a unique value that can identify the terminal worldwide. The APN 400 managed according to this value and the subscriber characteristics (GPRS subscriber, MIP subscriber, ISP subscriber, etc.) of the terminal are managed in association with each other, and each terminal is assigned and managed with a valid IP address 500 in its domain. .

The subscriber number managed in this way manages the newly created and managed CI 600 in association with the corresponding numbers at that time, whenever a call for service is actually set up, and an application task or an API (Access) of the network layer. NSAPI for identifying Point Identifier) is managed in association with the corresponding CI (600).

Eventually, if several packet calls are set, the CI 600 and the NSAPI 700 are sequentially generated and managed. Finally, these identifiers are managed in association with RB number 800, which is the number of the radio resource channel that is actually delivered.

These identifiers are used as identifiers for each layer of the protocol, and these identifiers can be linked to distinguish a plurality of packet calls. That is, when setting a plurality of PDPs, the CI 600 is used between the UI block and the PPP block, the NSAP 700 is used between the PPP block and the SM block, and the RB number 800 is used between the SM block and the RRC block. Is used to set a plurality of PDPs. For service data, the CI 600 is used between the UI block and the PPP block, the NSAP 700 is used between the PPP block and the PDCP block, and the RB number is used between the PDCP block and the RLC block. Is distinguished so that it can be delivered on the corresponding packet call.

Therefore, a plurality of packet calls are internally set in one terminal, and various multimedia services can be realized at the same time. That is, each time one call is established, a radio resource (RB) is captured as a PDP is generated, and they have different performance parameters, and thus, the requirements are made possible through radio resources to which different services are allocated.

Although the present invention has been described with reference to the most practical and preferred embodiments, the present invention is not limited to the above disclosed embodiments, but also includes various modifications and equivalents within the scope of the following claims.

According to the present invention, since one packet terminal can simultaneously provide various types of services in one packet mobile communication system, services having different resource allocation requirements such as voice, video, and data services can coexist.

Claims (14)

A packet terminal capable of using a plurality of packet services by connecting to a packet mobile communication network, A user registration block for performing a user interface and configuration task; An internet protocol block connected to the user matching block and configured to deliver all packet service data including mobile internet protocol data; A session management block connected to the Internet protocol block and performing a packet data protocol and session management operation; And A radio resource management block connected to the session management block and the packet mobile communication network and performing radio resource management and signal connection management. Including; A first delimiter between the user matching block and the internet protocol block, a second delimiter between the internet protocol block and the session management block, and a third delimiter between the session management block and the radio resource management block; The first delimiter, the second delimiter, and the third delimiter are set differently according to a service, and the packet delimiters corresponding to a plurality of packet services are distinguished by linking the first delimiter, the second delimiter, and the third delimiter. Characterized in that Packet terminal capable of supporting multiple packet calls. The method of claim 1, The first identifier is a Call Identifier (CI) which is a connection identifier for identifying a packet call connection, The second delimiter is a network service access point (NSAP), which is an identifier for identifying connections in a network. The third identifier is an RB number (Radio Bearer Number) allocated by the packet mobile communication network. A packet terminal capable of supporting multiple packet calls, characterized in that. The method of claim 2, A packet data delivery block connected to the radio resource management block and the internet protocol block, and performing a substantial transfer of packet service data between the packet terminal and the packet mobile communication network; The first delimiter, the second delimiter and the third delimiter are stored in one table, and the table is managed by the packet data transfer block. Packet terminal capable of supporting multiple packet calls. The method of claim 2, The delimiter is a packet terminal capable of supporting multiple packet calls, characterized in that passed as a parameter between each of the blocks. The method of claim 3, The packet data delivery block includes a manager PDCP task for a packet service, The manager PDCP task generates an agent PDCP task whenever a packet data protocol corresponding to a user's packet service request is set, and calls the corresponding agent PDCP task using the identifiers stored in the table. Characterized Packet terminal capable of supporting multiple packet calls. The method of claim 1, The packet service is a packet terminal capable of supporting multiple packet calls, characterized in that the packet data protocol is set to have different parameter values according to characteristics. The method of claim 6, The parameter value is a packet terminal capable of supporting multiple packet calls, characterized in that the data size that can be transmitted at one time, the maximum bandwidth up and down, the minimum bandwidth, the allowable delay rate, the data throughput. A method for supporting a multi-packet call in a packet terminal capable of using a packet service by accessing a packet mobile communication network, a) establishing, according to a packet service request from the user, a new packet call including an identifier that can be distinguished from another packet call if another packet call is already in service; And b) receiving a packet service data by accessing the packet mobile communication network using a packet call distinguished through a delimiter corresponding to the packet service when a packet service data request is received from a user; Including, The delimiter is a first delimiter between the user matching block and the internet protocol block, a second delimiter between the internet protocol block and the session management block, and a third delimiter between the session management block and the radio resource management block. Containing A method for supporting multiple packet calls in a packet terminal. The method of claim 8, Step a) i) requesting radio resource allocation to the packet mobile communication network according to a packet service request from the user; ii) allocating a radio resource corresponding to the packet service request by the packet mobile communication network according to the radio resource allocation request; And iii) setting an environment according to the radio resources allocated in step ii) Multiple packet call support method in a packet terminal comprising a. The method of claim 9, In step iii), the identifier for distinguishing the packet call is stored in a specific table. The method of claim 8, Step b) iv) classifying the corresponding packet call using an identifier corresponding to the packet service from the user; v) requesting packet service data by accessing the packet mobile communication network through the packet call classified in step iv); vi) classifying a corresponding packet call using an identifier corresponding to packet service data provided according to the request in step v); And vii) receiving the packet service data through the packet call classified in step vi). Multiple packet call support method in a packet terminal comprising a. The method according to any one of claims 8 to 11, The delimiter is for distinguishing each protocol layer forming a protocol between the packet terminal and the packet mobile communication network. The packet call can be distinguished by the association of the classifiers. Multiple packet call support method in a packet terminal, characterized in that. The method of claim 12, The protocol layer includes an application layer, a point to point protocol (PPP) layer, a session management (SM) layer, a radio resource control (RRC) layer, Call Identifier (CI), which is a connection identifier for identifying a packet call connection, is used between the application layer and the PPP layer. A network service access point (NSAP) is used between the PPP layer and the SM layer, which is an identifier for identifying connections in a network layer. Using a radio bearer number (RB number) between the SM layer and the RRC layer Multiple packet call support method in a packet terminal, characterized in that. The method of claim 13, The identifiers are stored in one table, and the table is managed by a packet data convergence protocol (PDCP) layer that performs a substantial transfer of packet service data.