KR100442626B1 - Method for maintaining quality of service priority in packet core network using publick network - Google Patents

Abstract

The present invention provides a first network for assigning one class of a first number of quality of service priority classes to input packet data, and a second number of quality of service priority classes different from the first number for input packet data. A method of maintaining a quality of service priority for packet data transmitted between second networks that assigns one of the classes, the first quality of service quality classes for upstream and downstream streams, respectively. Resetting the priority and dividing the transmission rate range supported by the first network for each of the upstream and the downstream into a third number of intervals to divide the first number of quality of service classes into the second number. New mapping and input corresponding to each of the quality of service priority classes of Determines whether the packet data is upstream or downstream, and if it is upstream, allocates one of the quality of service priority classes mapped to the upstream; The service quality priority is maintained by allocating one of the quality of service priority classes mapped to the downstream.

Description

How to Maintain Quality of Service Priority in Packet-Core Networks Using Public Networks {METHOD FOR MAINTAINING QUALITY OF SERVICE PRIORITY IN PACKET CORE NETWORK USING PUBLICK NETWORK}

The present invention relates to a code division multiple access communication system, and more particularly, to a method of maintaining quality of service priority in a packet core network using a public network.

UMTS (Universal Mobile Terrestrial System) using Code Division Multiple Access (CDMA), which is one of the third generation mobile communication systems, is not only a voice service but also packet data. It supports (packet data) service and supports high speed data communication and video communication. A general packet radio service (GPRS) network, which is a packet data domain of the core network (CN) of the UMTS, performs a packet data service, and includes a mobile station (MS) and a UTRAN. Call processing between UMTS Terrestrial Radio Access Networks (QTS) is performed according to a priority of Quality of Service (QoS). The call processing according to the QoS priority is implemented through a bandwidth allocation priority for a channel bearer and a queuing priority for traffic control when a call is first established in the GPRS network.

Next, the structure of the packet radio service network will be described with reference to FIG. 1.

1 is a diagram schematically illustrating a general packet wireless service network.

Referring to FIG. 1, a packet radio service support node (GSN), which is a node supporting packet radio service, includes functions required to support packet radio service function for GSM and / or UMTS. And at least one packet radio service support node in any PLMN 300. The gateway GPRS support node (GGSN) 130 is a node connected by a packet data network because of the evaluation of a packet data protocol (PDP) address. Here, the PDP address includes routing information for users to which a PS (Packet Switched) is attached, and the routing information is a current connection point of a mobile station (MS), that is, a service packet wireless service support node (SGSN). Support Node) is used to tunnel N-PDUs to a connection point such as 110. The gateway packet radio service support node 130 requests location information from a home location register (HLR) 307 through an optical Gc 305 interface. The gateway packet radio service support node 130 becomes the first point of a PDN interconnect with a GSM PLMN that supports GPRS (ie, Gi 309 reference point supported by the gateway packet radio service support node 130). will be. The gateway packet radio service support node 130 function is a function corresponding to GSM and UMTS in common.

The service packet radio service support node 110 is a node serving the mobile station. The service packet radio service support node 110 may include GSM (ie, a Gb 311 interface supported by the service packet radio service support node 110) and / or UMTS (ie, the service packet radio service support node ( Packet radio service for the Iu 313 interface supported by 110). In the PS connection, the service packet radio service support node 110 establishes, for example, a mobility management context including information related to mobility and security of the mobile station. In activation of the PDP environment, the service packet radio service support node 110 establishes a PDP environment to be used for routing purposes with the gateway packet radio service support node 130 for use by the subscriber.

The service packet radio service support node 110 and the gateway packet radio service support node 130 functions may be combined in the same physical node or may exist in different physical nodes. The service packet radio service support node 110 and the gateway packet radio service support node 130 include an IP or other (at the operator's option, for example ATM-SVC) routing function and are interconnected by an IP router. . In the UMTS, the service packet radio service support node 110 and a radio network controller (RNC) are interconnected with one or more IP routers. When the service packet radio service support node 110 and the gateway packet radio service support node 130 are in different PLMNs, the service packet radio service support node 110 and the gateway packet radio service support node 130 are connected to a Gp. 315 are interconnected via an interface. The Gp 315 interface not only provides the Gn 317 interface function but also has the security function required for PLMN internal communication. The security function is based on mutual agreement between operators.

The service packet wireless service support node 110 transmits location information to a Mobile Switching Center (MSC) / Visitor Location Register (VLR) 321 through an optical Gs 319 interface. The service packet radio service support node 110 receives a paging request from the mobile switch / visitor location register 321 via the Gs 319 interface. The service packet radio service support node 110 interfaces with the GSM-SCF for selective Customized Applications for Mobile Network Enhanced Logic (CAMEL) control. Depending on the results resulting from the CAMEL interaction, the SESSION and packet data transmissions generally proceed.

In addition, the illustrated Ga 323 interface is a CDR (Call Detail Record) transmission device (for example, the service packet radio service support node 110 or the gateway packet radio service support node 130) and the CDR reception function (CGF) Perform a data collection interface between 325. The Gb 311 interface is an interface between the service packet radio service support node 110 and a base station system (BSS) 327, and the Gc 305 interface is the gateway packet radio service support node. An interface between the 130 and the home location register 307. The Gd 329 interface may include a short message service gateway (SMS-GMSC) 331, the service packet wireless service support node 110, and a short message service-interaction mobile exchange (SMS-GMSC). SMS-IWMSC: Short Message Service Interworking MSC (331) interface, Gf 333 interface is the interface between the service packet radio service support node 110 and the EIR (335). The Gi 309 is a reference point between the GPRS and an external packet data network, the Gn 317 is an interface between two GSNs in the same PLMN, and the Gp 315 supports two packet radio services in different PLMNs. As an interface between nodes, the Gp 315 interface enables packet radio service network service support through regions served by the interoperable packet radio service PLMNs. A Gr 337 interface is an interface between the service packet radio service support node 110 and a home location register 307, and the Gs 319 interface is a mobile switch / visitor location with the service packet radio service support node 110. It is an interface between the registers 321, and the Iu 313 is considered as a reference point while being an interface between the RNSs and the core network. And, R 339 is a reference point between a non-ISDN compatible TE (tunnel end point) and MT, and typically supports a reference serial interface. Um 341 is an interface between a mobile station and a portion of a GSM fixed network, and the Um 341 interface is a GSM network interface for providing packet radio service over the air to the mobile station. The MT portion of the mobile station is used to connect a packet radio service in GSM via the Um 341 interface. Uu 343 is an interface between the mobile station and the UMTS fixed network portion and is a UMTS network interface for providing packet radio service to the mobile station over the air. In FIG. 1, a portion indicated by a dotted line between components is a signal interface, and a portion indicated by a solid line is a signal and data transfer interface.

In FIG. 1, a packet wireless service network structure has been described. Next, a QoS structure of a packet wireless service network will be described with reference to FIG.

2 is a diagram schematically illustrating a quality of service (QoS) structure of a general packet radio service network.

Referring to FIG. 2, in the QoS architecture supporting the packet radio service network as shown, QoS in the core network between the gateway packet radio service support node 130 and the service packet radio service support node 110 is prioritized. It does not specify a support structure for rank control. But. A plurality of service packet wireless service support nodes 110 may be connected to one gateway packet wireless service support node 130, and each of the plurality of service packet wireless service support nodes 110 has different QoS priorities. Since a plurality of mobile stations are connected and the service packet radio service support node 110 and the gateway packet radio service support node 130 are also connected by a router, the wireless packet service support nodes each have their own buffer ( buffer). In this case, when the gateway packet wireless service support node 130 or the service packet wireless service support node 110 does not perform QoS priority control based on the priority according to the order stored in the buffer, it is performed in the previous step. QoS priority control effects are attenuated. This has the problem that QoS priority support at the mobile station-to-end level is not possible in the packet radio service network.

On the other hand, between the service packet wireless service support node 110 and the gateway packet wireless service support node 130 may support QoS priorities through packet queuing, scheduling, and shaping. This QoS priority is determined using the UMTS traffic class given to the call during initial call setup. Here, the UMTS traffic class is classified into four classes. Since the description of the UMTS traffic class will be described later, a detailed description thereof will be omitted.

Meanwhile, a network in which the service packet radio service support node 110 and the gateway packet radio service support node 130 are connected to the packet radio service network will be referred to as a "packet core network", and the packet core A network is directly connected between the service packet wireless service support node 110 and the gateway packet wireless service support node 130, that is, the Iu interface between the service packet wireless service support node 110 and the gateway packet wireless service support node 130. 313, when the Gn interface 317 and the Gi interface 309 are directly connected, QoS priority support according to the UMTS traffic class is possible. However, an indirect connection through another network such as a public network or a private network is not directly connected between the service packet wireless service support node 110 and the gateway packet wireless service support node 130. In this case, QoS priority support according to a UMTS traffic class is impossible between the service packet wireless service support node 110 and the gateway packet wireless service support node 130.

Next, a structure in which the packet core network is connected through the public network will be described with reference to FIG. 3.

FIG. 3 is a diagram schematically illustrating a packet core network in the packet wireless service network of FIG. 1.

Referring to FIG. 3, the service packet wireless service support node 110 and the gateway packet wireless service support node 130 are connected through a private network or a public network 400. For convenience of explanation, it will be described on the assumption that only the service packet wireless service support node 110 and the gateway packet wireless service support node 130 are connected through a public network. When the service packet wireless service support node 110 and the gateway packet wireless service support node 130 are connected through the public network 400, the service packet wireless service support node 110 and the gateway packet wireless service support node 130 are described. QoS priority support is not possible because other networks, such as the public network, support QoS priorities according to Diff-Serv QoS rather than UMTS traffic classes. Here, the Diff-Serv QoS has three different Per Hop Behaviors (PHBs) of EF, AF, and BF, and the AF has four classes and each of the four classes has Drop Precedence. Since the Serv QoS will be described later, a detailed description thereof will be omitted.

As described above, in the packet core network of the UMTS packet radio service network, it is possible to provide normal service quality only when QoS priority according to the UMTS traffic class is guaranteed. The service packet radio service support node 110 and the gateway of the packet core network are provided. When the packet radio service support nodes 130 are connected through another type of network, such as a public network, QoS priority cannot be guaranteed according to the UMTS traffic class, and the QoS priority cannot be guaranteed. there was.

Accordingly, an object of the present invention is to provide a method for maintaining quality of service priorities in a packet core network using a public network.

Another object of the present invention is to provide a method of mapping a UMTS traffic class with a Diff-Serv QoS of a public network in a packet core network using a public network.

The present invention for achieving the above object; A first network for assigning one class of the first number of quality of service priority classes to input packet data, and one of a second number of quality of service priority classes different from the first number for input packet data A method of maintaining a quality of service priority for packet data transmitted between second networks, wherein the first class of service quality priority classes are assigned to each of upstream and downstream streams, respectively. Resetting and dividing the transmission rate range supported by the first network into a third number of intervals for each of the upstream and the downstream streams to divide the first number of quality of service classes into the second number of quality of service. New mapping corresponding to each of the priority classes; After mapping the quality of service priority class to each of the stream and the downstream stream, it is determined whether the input packet data is the upstream or the downstream stream. If the result is the upstream stream, the service is mapped to the upstream stream. Assigning one of the quality priority classes, and in the case of the downstream analysis, assigning one of the service quality priority classes mapped to the downstream stream to control to maintain the service quality priority. It is characterized by including.

1 schematically illustrates a typical packet wireless service network.

2 is a diagram schematically illustrating a quality of service (QoS) structure of a general packet radio service network.

FIG. 3 is a diagram schematically illustrating a packet core network in the packet wireless service network of FIG. 1.

4 is a flowchart illustrating a traffic class mapping process for supporting quality of service priorities according to an embodiment of the present invention.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. It should be noted that in the following description, only parts necessary for understanding the operation according to the present invention will be described, and descriptions of other parts will be omitted so as not to distract from the gist of the present invention.

4 is a flowchart illustrating a UMTS traffic class and Diff-Serv QoS mapping process for supporting quality of service priority according to an embodiment of the present invention.

Before describing FIG. 4, the UMTS traffic class and Diff-Serv QoS mapping process as shown in FIG. 4 is performed by a service packet radio service support node (SGSN) 110 and a gateway packet radio service. It is performed on all of the support node (GGSN: Gateway GPRS Support Node) (GGSN) 130, it will be described on the assumption that it is performed in the service packet wireless service support node 110 for convenience of description.

Referring to FIG. 4, first, in step 411, the service packet wireless service support node 110 is referred to as a packet data protocol (PDP) between the gateway packet wireless service support node 130. If the context is opened, the flow proceeds to step 413. Here, the process of opening the PDP context is as follows.

First, in order to transmit data, that is, packet data, in the UMTS packet domain, a wireless service tunneling protocol (GTP: GPTP Tunneling Protocol) for transmitting the packet data is referred to as a tunnel. You must create The path through which the GTP tunnel is generated is largely when the mobile station requests a core network (CN), that is, when it requests the UMTS core network from MS-Initiated Activate and an external network, that is, a network request. It is divided into two paths: Network Requested Activate.

In detail, the mobile station generates a GTP tunnel for transmitting the packet data as it detects the occurrence of the packet data. In this way, the mobile station transmits an Activate PDP Context Request message to the service packet radio service support node 110 to create a GTP tunnel. The parameters included in the PDP context activation request message may include a Network Layer Service Access Point Identifier (NSAPI), a TI, and a PDP type (type). ), A PDP address, an access point network, a quality of service (QoS), and the like.

In this case, the NSAPI is information generated by the mobile station, and a total of 11 values from 5 to 15 can be used. The NSAPI value has a one-to-one correspondence with a PDP address and a PDP context identifier (PDP context ID). The PDP address indicates an IP address of the mobile station used in the UMTS packet domain and is information constituting one of the PDP context information. Here, the PDP context stores various kinds of information of the GTP tunnel, and the PDP context is managed by a PDP context ID. In addition, the PDP type indicates the type, that is, the type of GTP tunnel to be created through the PDP context activation request message. In this case, the GTP tunnel includes Internet Protocol (IP), Point to Point Protocol (PPP), Mobile IP, and the like. The access point network indicates an access point of a service network to which a mobile station requesting to create the GTP tunnel is currently connected. In addition, the quality of service represents the quality of packet data transmitted through the currently generated GTP tunnel. That is, packet data using the GTP tunnel having a high quality of service is processed before packet data using the GTP tunnel having a low quality of service.

Upon receiving the PDP context activation request message, the service packet radio service support node 110 establishes a radio access bearer with the UTRAN by transmitting a radio access bearer setup message to a UMTS Terrestrial Radio Access Network (UTRAN). In addition, the UTRAN sends a radio access bearer setup message to the mobile station to establish a radio access bearer with the mobile station. In this way, as the radio access bearer is established between the service packet radio service support node 110 and the UTRAN and also between the UTRAN and the mobile station, resources necessary for packet data transmission over the air are allocated.

Meanwhile, in the state in which the UTRAN and the radio access bearer are established, the service packet radio service support node 110 transmits a Create PDP Context Request message to the gateway packet radio service support node 130. In this case, a tunnel endpoint ID (TEID: Tunnel Endpoint ID) is newly set between the service packet wireless service support node 110 and the gateway packet wireless service support node 130. The tunnel endpoint ID uses a GTP tunnel. It is configured to transmit packet data between network nodes. That is, the service packet wireless service support node 110 stores the tunnel endpoint ID of the gateway packet wireless service support node 130, and the gateway packet wireless service support node 130 stores the service packet wireless service support node. The tunnel termination point ID of 110 is stored. Thus, the PDP context creation request message includes a tunnel end point ID to be used when the gateway packet radio service support node 130 transmits packet data to the service packet radio service support node 110.

Upon receipt of the PDP context creation request message, the gateway packet wireless service support node 130 generates a PDP response to the service packet wireless service support node 110 when the PDP context creation for the PDP context creation request message is normally completed. PDP Context Response) message is sent. As a result, the GTP tunnel generation is completed between the service packet radio service support node 110 and the gateway packet radio service support node 130, and the actual packet data transmission is possible due to the GTP tunnel generation. Upon receiving the PDP generation response message, the service packet radio service support node 110 transmits an Activate PDP Context Accept message to the mobile station. As the mobile station receives the PDP activation allowance message, a radio channel is created between the mobile station and the UTRAN, and a GTP is established between the UTRAN and a service packet radio service support node 110 and a gateway packet radio service support node 130. The tunnel has been created. That is, the mobile station can transmit and receive all packet data transmitted to the mobile station's own PDP address. Meanwhile, the GTP tunnel generated in the above-described PDP context process has one-to-one correspondence with one PDP context. If the GTP tunnels are different, the PTP contexts have different tunnel information.

As described above, after the PDP context is opened, the service packet wireless service support node 110 proceeds to step 413. In step 413, if there is packet data to be transmitted through the open PDP context, the service packet wireless service support node 110 analyzes a system type and an interface of the packet data. Here, the system type refers to a corresponding class of the UMTS traffic class (tracffic class), and the interface means an interface type with the gateway packet radio service support node 130 or the UTRAN. Here, the interface type includes a service packet radio service support node 110_Iu and a gateway packet radio service support node 130_Gn as an uplink interface, and a service packet radio service support node 110_Gn and a gateway packet as downlink interfaces. Wireless service support node 130_Gi exists.

Here, the UMTS traffic class will be described.

The UMTS traffic class is classified into four classes: a conversational class, a streaming class, an interactive class, and a background class. The Conversational class is a class allocated to real time large-capacity high-speed data such as a video, the Streaming Class is a class allocated to data such as a VOD, the Interactive Class is a class assigned to data such as a web (WEB) service, and the background class is As the lowest class, the lowest priority among the UMTS traffic classes.

Meanwhile, in the embodiment of the present invention, since the connection between the service packet radio service support node 110 and the gateway packet radio service support node 130 is connected through a public network 400, the public The network 400 supports the Diff-Serv QoS class. Here, the Diff-Serv QoS class will be described.

First, the Diff-Serv QoS class is classified into an Expedit Forwarding (EF) class, an Assured Forwarding (AF) class, and a Best Effort (BE) class. Here, the EF class has a highest priority given to a signaling packet such as a control message, and the AF class has four lower classes, that is, four classes of AF_CL1, AF_CL 2, AF_CL 3, and AF_CL 4, and the lower class Each of the four classes is mapped to three priorities according to the maximum bit rate or guaranteed bit rate that can be supported. Here, the three priorities have three priorities of Low Drop Precedence, Medium Drop Precedence, and High Drop Precedence, respectively, and the Low Drop Precedence, Medium Drop Precedence, and High Drop Precedence are each Low Quality Level ( Min ~ Max), Normal Quality Level (Min ~ Max), and High Quality Level (Min ~ Max). Here, the Low Quality Level (Min ~ Max) is less than 64kbps as an example, the Normal Quality Level (Min ~ Max) is 64 ~ 127kbps. High Quality Level (Min ~ Max) is mapped to correspond to data having a size of 128 kbps or more.

As described above, since the UMTS traffic class has four classes, while the Diff-Serv QoS class has 14 classes, it is impossible to support the QoS priority of transmitted packet data. By mapping the UMTS traffic class and the Diff-Serv QoS class, it is possible to maintain the same QoS priority of packet data transmitted between the packet core network and the general public network.

The UMTS traffic class and Diff-Serv QoS class mapping includes (1) UMTS traffic class priority (different class priority for upstream and downstream), ② supportable bandwidth level (ie, maximum bandwidth and guaranteed bandwidth). (Guaranteed bandwidth) level). Considering the above points, the UMTS traffic class and Diff-Serv QoS class mapping in the upstream will be described.

First, in the UMTS packet core network, signaling between the service packet radio service support node 110 and the gateway packet radio service support node 130, that is, important signaling such as a control message, is also transmitted in the form of packet data, that is, IP packet data. QoS priority mapping is needed for. Here, the signaling includes GTP-c, Mobile IP signaling, PPP signaling, and the like, and the signaling is always mapped to the highest priority EF class. Thus, all QoS modules and the packet data transmitting the signaling in the service packet radio service support node 110 and the gateway packet radio service support node 130 are controlled first.

For the remaining packet data other than the packet data transmitting the signaling, the UMTS traffic class characteristics are first considered in the UMTS traffic class and Diff-Serv QoS class mapping.

According to the UMTS traffic class characteristic, QoS priorities of upstream and downstream are newly mapped.

First, in the upstream, the priority of the UMTS traffic class will be described.

In the case of the upstream, the streaming class of the UMTS traffic class has the same service priority as the interactive class. The reason is that the representative service to which the streaming class is assigned is a VOD service, and the representative service to which the interactive class is assigned is a WEB service. In the case of the VOD service, since there is almost no packet data transmitted upward, the streaming class is Has a higher QoS priority than the interactive class but gives the same QoS priority. Thus, when looking at the QoS priority in the upstream, it has the priority of conversational class> streaming class = interactive class> background class.

Next, in the case of the downstream, the priority of the UMTS traffic class will be described.

In the case of the downstream, the streaming class of the UMTS traffic class has the same service priority as the conversational class. The reason is that the representative service to which the streaming class is assigned is a VOD service, and the representative service to which the conversational class is assigned is a real-time video service. In the case of the real-time video service, the amount of packet data transmitted downward is transmitted downward of the VOD service. Almost similar to the amount of packet data, the coversational class has a higher QoS priority than the streaming class but is given the same QoS priority. Thus, in the downstream, the QoS priority has a priority of conversational class = streaming class> interactive class> background class.

For the remaining packet data other than the packet data transmitting the signaling, the supportable bandwidth level for each UMTS traffic class is considered in the UMTS traffic class and Diff-Serv QoS class mapping.

The supportable bandwidth level is defined as the maximum bandwidth "maximum bit rate for up / downlink" and the minimum bandwidth "guaranteed for up / downlink" defined in the UMTS communication system. In the uplink, the guaranteed bit rate, which is the minimum bandwidth, becomes the reference bandwidth, and in the downlink, the maximum bit rate becomes the reference bandwidth. This is because the downlink in the UMTS communication system ignores the minimum bandwidth guaranteed bit rate for the interactive class and the background class. In this case, three new levels for each UMTS traffic class are defined with the supportable bandwidth level, that is, bit rate, as follows.

(1) low quality level (min to max)

<64 kbps

(2) normal quality level (min ~ max)

64 kbps to 127 kbps

(3) high quality level (min ~ max)

128 kbps or more

The three levels, that is, the low quality level, and the bit rate defined in the general quality level and the high quality level are values that can be adjusted to suit system characteristics. In an embodiment of the present invention, the low quality level is less than 64 kbps as an example. The general quality level is set at 64 kbps to 127 kbps, and the high quality level is set at 128 kbps or higher. The low quality level is mapped to low drop precedencd, medium drop precedence, and high drop precedence of Diff-Serv QoS, respectively.

In consideration of the above two considerations, that is, the UMTS traffic class characteristics and the supportable bandwidth levels, when the UMTS traffic class and the Diff-Serv QoS class are finally mapped in the upstream, the upstream QoS priority mapping table shown in Table 1 below. same as (table)

In addition, when the UMTS traffic class and the Diff-Serv QoS class are mapped in the downstream in consideration of the UMTS traffic class characteristics and the supportable bandwidth levels, the following is the downstream QoS priority mapping table of Table 2 below.

After storing the upstream QoS priority mapping table of Table 1 and the downstream QoS priority mapping table of Table 2 in each of the service packet radio service support node 110 and the gateway packet radio service support node 130, the service When packet data is inputted / outputted to each of the packet radio service support node 110 and the gateway packet radio service support node 130, QoS priorities are mapped according to the upstream and downstream QoS priority mapping tables.

Then, when the packet data is input while the PDP context is open, the process of mapping QoS priorities to the input packet data by the service packet wireless service support node 110 will be described with reference to FIG. 4. Let's explain.

As described above, when the packet data is input in the state in which the PDP context is opened in step 411, that is, in the state in which the GTP tunnel is generated, the service packet wireless service support node 110 proceeds to step 413 to input the packet data. The system type and interface are analyzed. In this case, the system type is analyzed to determine from which system packet data input to the service packet wireless service support node 110 is generated or transmitted, and an interface is an interface type of the input packet data. Is analyzed to determine.

If the received packet data is data transmitted from the UTRAN to the service packet radio service support node 110 through an Iu interface (SGSN_Iu), that is, the service packet radio service support node 110 when it is upstream. Proceeds to step 415. Although FIG. 4 illustrates the service packet wireless service support node 110 as a reference, when the gateway packet wireless service support node 130 is the reference, the input packet data is a gateway packet wireless service support node through the Gn interface. In the case of data transmitted to 130, (GGSN_Gn) becomes an upstream. In step 415, the service packet radio service support node 110 maps the QoS priorities corresponding to the upstream QoS priority mapping table shown in Table 1 because the input packet data is upstream. Proceed.

On the other hand, if the inputted packet data is the data transmitted to the service packet wireless service support node 110 through the Gn interface (SGSN_Gn) as a result of the analysis in step 413, that is, the service packet wireless service support node when it is downstream. 110 proceeds to step 417. Although FIG. 4 illustrates the service packet wireless service support node 110 as a reference, when the gateway packet wireless service support node 130 is the reference, the input packet data is a gateway packet wireless service support node through the Gi interface. In the case of data transmitted to 130, (GGSN_Gi) is a downstream stream. In step 417, the service packet wireless service support node 110 maps QoS priorities to correspond to the downstream QoS priority mapping table shown in Table 2 because the input data is downstream. do. In step 419, the service packet radio service support node 110 allocates, stores and terminates a newly mapped QoS priority for the input packet data.

Meanwhile, in the detailed description of the present invention, specific embodiments have been described, but various modifications are possible without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined not only by the scope of the following claims, but also by the equivalents of the claims.

As described above, in the packet core network, the QoS priority scheme of the packet core network when the service packet wireless service support node and the gateway packet wireless service support node are not directly connected but indirectly connected through another network such as a public network. By mapping the UMTS traffic class and the Diff-Serv QoS class which is the QoS priority system of the public network, the QoS priority can be maintained continuously.

Claims (4)

A first network for assigning one class of the first number of quality of service priority classes to input packet data, and one of a second number of quality of service priority classes different from the first number for input packet data In the method for maintaining the quality of service priority for packet data transmitted between the second network to give a class of: Resetting the quality of service priority levels of the first number of quality of service classes for each of upstream and downstream streams; and a third number of transmission rate ranges supported by the first network for each of the upstream and downstream streams. Dividing the first number of quality of service priority classes to each of the second number of quality of service priority classes by dividing the data into intervals of After mapping a quality of service priority class to each of the upstream and downstream streams, it is determined whether the input packet data is the upstream or the downstream stream, and in the case of the upstream stream, the mapping corresponds to the upstream stream. Allocating one of the quality of service class prioritized, and in the case of the downstream determination result, to assign one of the service quality priority classes mapped to the downstream to control to maintain the quality of service priority Said method comprising a process. The method of claim 1, And if the input packet data is packet data indicating a control message, assigning a quality of service priority having the highest priority to both the upstream and the downstream streams. A first network for assigning one class of the first number of quality of service priority classes to input packet data, and one of a second number of quality of service priority classes different from the first number for input packet data In the method for maintaining the quality of service priority for packet data transmitted between the second network to give a class of: Resetting the quality of service priority levels of the first number of quality of service classes for each of upstream and downstream streams; and a third number of transmission rate ranges supported by the first network for each of the upstream and downstream streams. Dividing the first number of quality of service priority classes to each of the second number of quality of service priority classes by dividing the data into intervals of After mapping a quality of service priority class for each of the upstream and downstream streams, if packet data is input, the system type and interface type are examined for the input packet data to determine whether it is upstream or downstream. Process, Allocating one of newly mapped quality of service priority classes to an upstream when the input packet data is an upstream as a result of the determination; And if the input packet data is a downstream stream, allocating one of the newly mapped quality of service priority classes to the downstream stream as a result of the determination. The method of claim 3, And if the input packet data is packet data indicating a control message, assigning a quality of service priority having the highest priority to both the upstream and the downstream streams.