KR102178540B1 - Scheme for congestion control in mobile communication system - Google Patents

Abstract

A method of performing congestion control in a mobile communication system, the method comprising: receiving, by a load manager, load information from a base station; And triggering the congestion control by sending a load notification message including the received load information to a PDN Gateway (PGW) or a Serving Gateway (SGW), comprising: a method of performing congestion control in a mobile communication system, comprising: By providing, it is possible to efficiently use base station resources, and to prevent a service interruption of a traffic for which a certain bit rate is requested to be secured due to congestion control.

Description

User plane congestion control technique of mobile communication system {SCHEME FOR CONGESTION CONTROL IN MOBILE COMMUNICATION SYSTEM}

The present invention relates to a user plane congestion control method, system, and entities constituting the same in a mobile communication network, and in particular, to a technique for performing congestion control of a user plane using load information of a base station.

1 illustrates the configuration of a communication system in which a terminal is connected to an external network through a mobile network.

The terminal 180 is connected to a base station (eNB) 110 of a mobile network to receive a communication service. In addition to the base station 110, the mobile network includes a mobile management entity (MME) 100, a serving gateway (SGW) 120, a packet data network gateway (PGW) 130, One or more of a Policy and Charging Rule Function (PCRF) 170, and a Traffic Detection Function (TDF) 140 may be further included. One or more application servers 150 may be included in the external network to which the terminal 180 is connected through the mobile network.

In such a mobile communication network, a control method for a user plane (user plane) may be performed as follows.

In the case of controlling the transmission rate of the user plane by classifying services or applications, the PGW 130 or TDF 140 detects the service/application and then drops packets. ) Or delaying the transmission time by prolonged buffering, rate control or gating may be performed.

In the case of controlling the transmission rate of the user plane without distinguishing between services or applications, a bearer that does not promise to guarantee the bit rate when congestion occurs in the base station (eNB) 110, that is, For non-GBR bearers (non-Guaranteed Bit Rate), an IP flow is randomly selected from among Internet Protocol (IP) flows of several services/applications using any one bearer, and the selected IP flow Transmission rate control or gating can be performed by dropping packets of the packet or delaying the transmission time by prolonged buffering.

The first rate control scheme de-prioritizes data traffic of a specific service/application regardless of the user plane load status of the base station, so there is room for the resource of the base station. Even in the state, specific data traffic is de-prioritized, and as a result, efficient use of base station resources is not achieved.

The second rate control scheme is a scheme in which a base station randomly selects an IP flow among IP flows of a specific bearer without considering service/application features or traffic characteristics, and de-prioritizes it. For example, in the case of a video service that is not provided by a mobile network operator (MNO) such as YouTube, if this rate control technique is applied and the bit rate cannot be satisfied, data traffic is Even if provided, only charging information is counted, and the user's QoE (Quality of Experience) may worsen.

According to the load status of the base station, data traffic to be controlled for congestion is selected with minimum signaling and minimum processing overload, and congestion control is performed in consideration of the characteristics of the service/application of the selected traffic. Techniques, systems, and devices are provided.

A method of performing congestion control in a mobile communication system, the method comprising: receiving, by a load manager, load information from a base station; And triggering the congestion control by sending a load notification message including the received load information to a PDN Gateway (PGW) or a Serving Gateway (SGW), comprising: a method of performing congestion control in a mobile communication system, comprising: Suggest.

In addition, an apparatus of a mobile communication system for performing congestion control, comprising: receiving load information from a base station; A mobile communication system device comprising: a load manager triggering the congestion control by transmitting a load notification message including the received load information to a PDN Gateway (PGW) or a Serving Gateway (SGW).

In addition, in the method of performing congestion control in a mobile communication system, a PGW (PDN Gateway) performs deep packet inspection (DPI) on user data destined for a terminal through a base station to obtain an identifier that identifies the service of the data. action; Marking, by the PGW, an identifier for identifying the service and a minimum bit rate of the data on a GTP-U (GPRS Tunneling Protocol-User) header of the traffic, and transmitting the data to a Serving Gateway (SGW); Receiving, by the PGW, data from the base station in response to the marked GTP-U header; And controlling the transmission rate of the data according to a value of whether the PGW supports the minimum bit rate read from the GTP-U header of the received data. .

In addition, a mobile communication system apparatus for performing congestion control, comprising: performing deep packet inspection (DPI) on user data directed to a terminal through a base station to obtain an identifier for classifying a service of the data; The PGW marks an identifier for identifying the service and a minimum bit rate of the data on a GTP-U (GPRS Tunneling Protocol-User) header of the traffic and transmits the data to the SGW; The PGW receives data from the base station in response to the marked GTP-U header; A mobile communication system device including a PGW for controlling the data rate according to a value of whether the PGW supports the minimum bit rate read from a GTP-U header of the received data.

Efficient use of base station resources is possible because the availability of resources of the base station is considered for congestion control, and the characteristics of each service/application can be considered during congestion control, so the service of traffic that requires securing a certain bit rate due to uniform congestion control is Stopping can be prevented.

In addition, since signaling and additional processes for congestion control are not generated in a system where irregular congestion occurs, efficient operation of the system is possible.

1 is a diagram illustrating a configuration of a communication system in which a terminal is connected to an external network through a mobile network;
2 is a structural diagram of a mobile communication system according to an embodiment of the present specification;
3 is a diagram illustrating a rate control technique according to the first embodiment of the present specification;
4 is a diagram illustrating a rate control operation of a mobile communication system according to an embodiment of the present specification;
5 is a diagram illustrating a rate control technique according to a second embodiment of the present specification;
6 is a diagram illustrating a transmission rate control operation of a mobile communication system according to an embodiment of the present specification;
7 is a diagram illustrating a rate control technique according to a third embodiment of the present specification;
8 is a diagram illustrating a rate control operation of a mobile communication system according to an embodiment of the present specification;
9 is a diagram illustrating a data path through which a terminal in an active state is connected to a base station, an SGW, and a PGW according to an embodiment of the present specification;
10 is a structural diagram of a mobile communication system according to another embodiment of the present specification;
11 is a diagram illustrating a transmission rate control operation of a mobile communication system according to a fourth embodiment of the present specification;
12 is a diagram illustrating a structure of a GTP-U header of user traffic transmitted from a PGW to a base station according to an embodiment of the present specification;
13 is a diagram illustrating a structure of a GTP-U header of user traffic transmitted by a base station to a PGW according to an embodiment of the present specification;
14 is a diagram illustrating a congestion control method of a PGW according to a fourth embodiment of the present specification.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. In the following description of the present invention, if it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present invention, a detailed description thereof will be omitted. In addition, terms to be described later are terms defined in consideration of functions in the present invention and may vary according to the intention or custom of users or operators. Therefore, the definition should be made based on the contents throughout this specification.

Prior to the detailed description of the present invention, examples of interpretable meanings for several terms used in the present specification are presented. However, it should be noted that it is not limited to the interpretation examples presented below.

The base station is a subject that communicates with the terminal, and may be referred to as a BS, NodeB (NB), eNodB (eNB), access point (AP), or the like.

A terminal (User Equipment) is a subject that communicates with a base station, and may be referred to as a UE, a mobile station (MS), a mobile equipment (ME), a device, a terminal, and the like.

According to the first to third embodiments of the present specification, the mobile communication system performs congestion control of the user plane through load information notification and traffic selection using a load manager.

2 is a structural diagram of a mobile communication system according to an embodiment of the present specification.

The load manager 200 is located in the mobile network, collects load information from one or more base stations 230 and transfers the collected load information to other entities in the communication system, and congestion control based on the load information It is the entity that triggers to perform. Optionally, the load manager 200 interacts with the MME 220 to provide information on the PGW 210 or SGW 250 to perform a de-prioritization operation (ie, congestion control). It can be obtained from the MME (220). In addition, optionally, the load manager 200, the PGW 210, the SGW 250, or the TDF 240 to perform the de-prioritization operation, load information and additional information on the de-prioritization target Can also be delivered. Also, optionally, the load manager 200 may trigger transmission rate control according to a dynamically changing load status.

The load manager includes a load manager function (LMF), a load manager entity (LME), a load information function (LIF), and a load information entity (LIE). ), Congestion Manage Function (CMF), Congestion Manage Entity (CME), Congestion Control Function (CCF), Congestion Control Entity (CCE), etc. It can also be called as.

The load information collected by the load manager 200 from the base station 230 may be expressed as load status information, load level information, or load severity information, for example. , Percentage information of the currently in use capacity per radio channel of the base station 230 or a percentage of the currently in use capacity per QCI (Quality Control Information), which is a distinguisher of QoS (Quality of Service) It can be information.

The following first to third embodiments are examples in which a mobile communication system performs transmission rate control using the load manager 200.

3 is a diagram illustrating a rate control technique according to the first embodiment of the present specification.

After making a connection with the base station 230, the load manager 200 receives load information including a base station ID and a load level from the base station 230. The load manager 200 checks a region related to the base station 230 by inquiring a configuration table stored therein, and manages the base station 230 (responsible) at least one PGW Pick up (210). The load manager 200 is a load notification including information of a base station where a load has occurred to the selected one or more PGWs 210 (eg, E-UTRAN Cell Global Identifier (ECGI), which is a base station ID) and load level information Do (load notification) (or overload notification). Upon receiving the load notification, the PGW 210 performs transmission rate control for a terminal of a corresponding cell by using base station information included in the load notification. In this case, the PGW 210 may communicate with the MME 220 to obtain information on the terminal in the cell of the base station. Optionally, the DPI and transmission rate control operation performed by the PGW 210 may be performed by the TDF 240.

The operation of the embodiment according to FIG. 3 will be described in more detail with reference to FIG. 4.

4 is a diagram illustrating a transmission rate control operation of a mobile communication system according to an embodiment of the present specification.

The base station 230 accesses the load manager 200 to an address obtained as a result of a DNS query (Domain Name Server Query) set as a region information parameter, or O&M (Operation and Maintenance; operation and maintenance) A connection with the load manager 200 is established by accessing to an address designated through (400).

The load manager 200 sends configuration information necessary for the base station 230 to report the load information to the base station 230 (402).

The configuration information may include reference information for reporting the amount of a resource currently being used among available resources for non-GBR bearers and information to be reported. The reporting criterion information may be an interval in the case of periodic reporting, and in the case of non-periodic reporting, a threshold of the amount of resources being used (e.g., 50%, 60%, 70 %, 80%, 90%, etc.). The report target information may be a capacity (%) currently being used for each radio channel. For example, the load manager 200 has the purpose of reporting the currently used capacity (%) to the base station 230 when the amount of resources in use exceeds a threshold value of 70%, and the setting information is '70%. It may include information meaning','capacity in use (%)' and transmit.

The base station 230 monitors resources in the base station 230 based on the configuration information and notifies the load information to the load manager 200 (404).

When the load manager 200 is notified that a capacity equal to or greater than the threshold required for triggering of transmission rate control is used, the load manager 200 uses a configuration table set in the load manager 200 to be associated with the base station 230. One or more PGW 210(s) are selected (406).

Table 1 is an example of a setting table stored internally by the load manager 200.

Base station Related PGW eNB1, eNB2, eNB3 PGW1, PGW2 eNB4, eNB5, eNB6 PGW2, PGW3

The load manager 200 stores information on the PGW that manages the base station using the base station's ID (eNB ID or ECGI) in the form of an example as shown in Table 1, and is related to the base station (ie , Responsible) Used when selecting PGW.

The load manager 200 notifies the load information to the selected PGW 210 (408). The load information may include ECGI, which is information on the base station where the load (or congestion) has occurred, and information on the severity of the load (or load level information).

The PGW 210 uses the ECGI to find terminals existing in a cell referred to by the ECGI, and then selects terminals transmitting/receiving a current IP flow from among the found terminals. The PGW 210 includes subscription information of the selected terminals (when the level of application of transmission rate control is different depending on the class such as gold, silver, bronze, etc.) and a bearer QCI (Quality of Service) Class Identifier; QoS class identifier In consideration of ), bearers to be de-prioritized are selected (410).

The PGW 210 performs DPI on the IP flows in the selected bearer, and selects IP flows for a specific service/application as a result of the execution. The PGW 210 performs transmission rate control by performing a packet drop or a delay through a buffer for the selected IP flow (412).

When the PGW 210 is notified of a change in user location information from the MME 220, the PGW 210 may use the ECGI information to find a terminal existing in the cell indicated by the ECGI. Optionally, the PGW 210 may register a user location information change notification with the MME 220 (414). Upon receiving the registration, the MME 220 may notify the PGW 210 of the changed information whenever the cell in which the terminal is located is changed (416). Based on the changed information to be notified, the PGW 210 may obtain current cell information of the terminal.

Optionally, the DPI and transmission rate control performed by the PGW 210 may be performed by the TDF 240. The PGW 210 includes load information (load level information or load severity information) received from the load manager 200 and information on IP flows in the bearer selected in operation 410 (for example, a packet filter). ) May be transmitted to the TDF 240 (418). Upon receiving the load notification, the TDF 240 may perform DPI on the IP flows included in the load notification, and perform transmission rate control in consideration of the received load information (420).

5 is a diagram illustrating a rate control technique according to the second embodiment of the present specification.

In the second embodiment, by obtaining necessary information through the interaction between the load manager 200 and the MME 220, some signaling and de-prioritization target selection procedures of the first embodiment are distributed to the MME 220 It is a technique of letting go.

After establishing a connection with the base station 230, the load manager 200 receives load information including an ID of a terminal causing congestion and a list of load levels from the base station 230. The ID of the terminal may be a System Architecture Evolution (SAE) Temporary Mobile Subscriber Identity (S-TMSI). Upon receiving the load information, the load manager 200 requests bearer information while transmitting the ID of the terminal to the MME 220, and receives bearer information satisfying a condition from the MME 220 in response. . Based on the information received from the MME 220, the load manager 200 selects bearers requiring de-priority and transmits them to the PGW 210. The PGW 210 performs DPI based on the received information, selects an IP flow requiring transmission rate control, and performs transmission rate control such as packet drop or delay through a buffer. Optionally, the DPI and transmission rate control operation performed by the PGW 210 may be performed by the TDF 240.

The operation of the embodiment according to FIG. 5 will be described in more detail with reference to FIG. 6.

6 is a diagram illustrating a rate control operation of a mobile communication system according to an embodiment of the present specification.

The base station 230 connects the load manager 200 to an address obtained as a result of a DNS query set as an area information parameter, or connects to an address designated through O&M to establish a connection with the load manager 200 Do (600).

The load manager 200 sends configuration information necessary for the base station 230 to report the load information to the base station 230 (602).

The configuration information may include reference information for reporting the amount of a resource currently being used among available resources for non-GBR bearers and information to be reported. The reporting criterion information may be an interval in the case of periodic reporting, and in the case of non-periodic reporting, a threshold of the amount of resources being used (e.g., 50%, 60%, 70 %, 80%, 90%, etc.). The report target information may be a capacity (%) currently being used for each radio channel. For example, the load manager 200 has the purpose of reporting the currently used capacity (%) to the base station 230 when the amount of resources in use exceeds a threshold value of 70%, and the setting information is '70%. It may include information meaning','capacity in use (%)' and transmit.

The base station 230 monitors the resource in the base station 230 based on the configuration information and notifies the load manager 200 of the load information (604). At this time, the base station 230 transmits an ID list of a terminal that is currently in a connected mode and transmits and receives a lot of data to cause congestion along with the load information. An example of the terminal ID is S-TMSI. The S-TMSI consists of "MME code + temporary ID of the terminal allocated by the MME".

When the load manager 200, receiving the load information of the base station 230, determines that the state of the load indicated by the load information is greater than or equal to a threshold value requiring control, the bearer for performing transmission rate control In order to obtain information, the MME 220 is selected using the MME code included in the received S-TMSI, and a bearer information request including the S-TMSI list as a parameter is transmitted to the selected MME 220. (606). The bearer information request may further include a transaction ID.

At this time, the load manager 200 may deliver condition information about bearers requesting information together, and examples of the condition information include an arbitrary QCI and a specific Allocation and Retention Priority (ARP). There are bearer characteristics.

Upon receiving the request of the load manager 200, the MME 220 selects bearers satisfying the requested condition information among bearers of terminals corresponding to the S-TMSI list (608).

And the MME 220, associated PGW information (associated PGW info), the ID of the terminal used by the PGW 210 (eg, IMSI (International Mobile Subscriber Identity; International Mobile Subscriber Identity)), and the terminal In response to the request 606, a list including a subscription level (eg, gold, silver, bronze, etc.) among the subscription information for each is transmitted to the load manager 200 (610). The associated PGW information includes information on the selected bearer, and the information on the selected bearers may be delivered in the form of a TEID (Tunnel Endpoint Identifier) or a bearer ID. In this case, the list included in the response may further include a corresponding S-TMSI. In addition, when one or more PGWs are connected to the bearer of the terminal, the associated PGW information is delivered in the form of a list.

Based on the information received from the MME 220, the load manager 200 selects bearers of the terminal requiring de-priority (612), and the ID of the terminal for the selected bearer (from the PGW 210) Information including an ID to be used, eg, IMSI) and a bearer ID, is transmitted to the PGW 210 as a load notification message (614). At this time, the load manager 200 transmits the load information received from the base station 230 to the PGW 210 together in operation 604.

Upon receiving the load notification message, the PGW 210 performs DPI using the received bearer ID list information, and is a target of transmission rate control based on the information on the service/application obtained as a result of the DPI and the received IMSI. Transmission rate control is performed by selecting IP flows and performing packet drops or delays through a buffer (616).

Optionally, the DPI and transmission rate control performed by the PGW 210 may be performed by the TDF 240. The PGW 210 includes load information (load level information or load severity information) received from the load manager 200 and information on IP flows in the bearer selected in operation 612 (for example, a packet filter). A load notification including) may be transmitted to the TDF 240 (618). Upon receiving the load notification, the TDF 240 may perform DPI on the IP flows included in the load notification, and perform transmission rate control in consideration of the received load information (620).

7 is a diagram illustrating a rate control technique according to a third embodiment of the present specification.

The third embodiment is a technique capable of reducing signaling and procedures for interaction with the MME in the second embodiment by using information existing in the base station for congestion control.

After the load manager 200 establishes a connection with the base station 230, the terminal information (S-TMSI) and bearer information (SGW address, TEID) of the terminal that is in a connected mode and causing congestion from the base station 230 Field, load level), or ECGI. The load manager 200 determines whether congestion control is required, finds the address of the SGW using the bearer information, and transmits a load notification message including the SGW address, load level, and TEIDs to the SGW 250 do. The SGW 250 transmits the bearer information, the bearer ID and IMSI found based on the bearer information, and the load level information received from the load manager 200 to the PGW 210. The PGW performs a DPI using the information received from the SGW 250 and selects an IP flow requiring transmission rate control, and performs transmission rate control such as packet drop or delay through a buffer. Optionally, the DPI and transmission rate control operation performed by the PGW 210 may be performed by the TDF 240.

The operation of the embodiment according to FIG. 7 will be described in more detail with reference to FIG. 8.

8 is a diagram illustrating a transmission rate control operation of a mobile communication system according to an embodiment of the present specification.

The base station 230 connects the load manager 200 to an address obtained as a result of a DNS query set as an area information parameter, or connects to an address designated through O&M to establish a connection with the load manager 200 Do (800).

The load manager 200 sends configuration information necessary for the base station 230 to report the load information to the base station 230 (802).

The configuration information may include reference information for reporting the amount of a resource currently being used among available resources for non-GBR bearers and information to be reported. The reporting criterion information may be an interval in the case of periodic reporting, and in the case of non-periodic reporting, a threshold of the amount of resources being used (e.g., 50%, 60%, 70 %, 80%, 90%, etc.). The report target information may be a capacity (%) currently being used for each radio channel. For example, the load manager 200 has the purpose of reporting the currently used capacity (%) to the base station 230 when the amount of resources in use exceeds a threshold value of 70%, and the setting information is '70%. It may include information meaning','capacity in use (%)' and transmit.

The base station 230 monitors the resources in the base station 230 based on the configuration information and notifies the load information (load level information) to the load manager 200 together with the ECGI (804). At this time, the base station 230 is currently in a connected mode and transmits and receives a lot of data to cause congestion, S-TMSI (MME code + temporary ID of the terminal allocated by the MME) and information of bearers (SGW address, TEIDs) together to the load manager 200. The TEID, which is the information of the bearers, is a TEID corresponding to the SGW connecting the S1-U plane in an active state.

9 is a diagram illustrating a data path through which a terminal in an active state is connected to a base station, an SGW, and a PGW according to an embodiment of the present specification.

Referring to FIG. 9, a terminal 290 in an active state is a radio bearer 900 between the terminal 290 and the base station 230, and S1 between the base station 230 and the SGW 250. -U bearer tunnel (S1-U bearer tunnel) 910, and has a data path connected to the S5-U bearer tunnel (S5-U bearer tunnel) 920 between the SGW (250) and the PGW (210). .

The SGW address and TEID transmitted through operation 804 are information corresponding to the S1-U bearer tunnel, and the S1-U SGW tunnel ID (S1-U) allocated by the SGW 250 and notified to the base station 230 (S1-U SGW tunnel id) information, or S1-U eNB tunnel ID (S1-U eNB tunnel id) information allocated by the eNB and notified to the SGW for connection with the SGW.

When the load manager 200, which has received the load information of the base station 230, determines that the state of the load indicated by the load information is greater than or equal to the threshold value requiring control, the bearer of the terminal to be subjected to transmission rate control The load notification is transmitted to the SGW 250 by using the SGW address as information (806). The load notification 806 transmitted by the load manager 200 may include TEID information and load information (load level) received in operation 804.

After receiving the load notification from the load manager 200, the SGW 250 searches for corresponding bearers based on the TEID information included in the load notification and finds IMSI and bearer IDs related to the found bearers. (808), a load notification including load information (load level) received from the IMSI and the load manager 200 is transmitted to the PGW 210 (810). The load notification 810 transmitted from the SGW 250 to the PGW 210 may include the IMSI, the bearer ID, or TEIDs. The TEIDs included in the load notification 810 are information corresponding to a corresponding tunnel (S5-U bearer tunnel), and may be S5 SGW TEID or S5 PGW TEID.

Upon receiving the load notification 810, the PGW 210 performs DPI, and based on the received IMSI, bearer ID list or TEID list information, and service/application information based on the DPI performance result IP flows to be congested control are selected, and transmission rate control is performed by performing packet drop or delay through a buffer (812).

Optionally, the DPI and transmission rate control performed by the PGW 210 may be performed by the TDF 240. The PGW 210 includes load information (load level information or load severity information) received from the load manager 200 and information about IP flows in the bearer received in operation 810 (eg, packet filter (packet filter)). filter)) may be transmitted to the TDF 240 (814). Upon receiving the load notification, the TDF 240 may perform DPI on IP flows included in the load notification, and perform transmission rate control in consideration of the received load information (816).

The fourth embodiment of the present specification is a technique in which a mobile communication system performs transmission rate control using a set minimum bit rate.

The techniques of the first to third embodiments using a load manager make it possible to control the transmission rate by considering the load situation of the base station in the PGW or TDF. When the congestion situation persists for a predetermined time or longer, it is very effective to perform congestion control by performing signaling and corresponding processes using the techniques of the first to third embodiments. Meanwhile, when the congestion situation does not last for a certain period of time, but occurs at irregular intervals, signaling for congestion control that occurs periodically may act as a system overhead.

When congestion lasting for a short time occurs at irregular intervals, a method of controlling the transmission rate in consideration of service characteristics is provided. This embodiment is an effective technique especially when the entire data transmission is useless if transmission is not performed at a certain bit rate, such as video traffic.

A fourth embodiment of the present specification will be described with reference to FIGS. 10 and 11 below.

10 is a structural diagram of a mobile communication system according to another embodiment of the present specification.

The terminal 290 transmits and receives data traffic from the application server 1000 of an external network through a mobile network. The PGW 210 to perform congestion control performs DPI on the data traffic, and as a result, determines the detected service/application identifier and the minimum bit rate for the service/application as the GTP of the corresponding traffic. -U header is marked and transmitted to the base station 230 through the SGW 250. The base station 230 marks whether or not the minimum bit rate is supported and the available time on the GTP-U header and sends it to the PGW 210 through the SGW 250. The PGW 210 supports the minimum bit rate of the traffic according to whether a GTP-U header for the traffic arrives from the base station, and whether the arrived GTP-U header is marked as capable of supporting the minimum bit rate. Or, congestion control is performed by dropping packets of the corresponding traffic.

Referring to Fig. 11, a fourth embodiment will be described in detail.

11 is a diagram illustrating a transmission rate control operation of a mobile communication system according to a fourth embodiment of the present specification.

The PGW 210 (or TDF) performs DPI on the traffic provided to the terminal 290, and as a result, an identifier for distinguishing the detected service/application and the minimum bit rate for the service. ) Is marked on a GTP-U (GTP-User; General Packet Radio Service (GPRS) Tunneling Protocol-User)) header, which transmits the traffic, and transmitted to the SGW 250 (1100). In this embodiment, congestion control operations performed by the PGW 210 may be performed by the TDF 240, but for convenience of explanation, only the PGW 210 will be described.

Referring to FIG. 12, the identifier for distinguishing the service/application is marked on a Service Class Indicator (SCI), and the minimum bit rate is marked as an additional extension field.

12 is a diagram illustrating a structure of a GTP-U header of user traffic transmitted to a base station by a PGW according to an embodiment of the present specification.

The minimum bit rate may be marked in the additional extension field 1200, and the service/application identification identifier may be marked in the SCI field 1202.

In order to check the response to be received from the base station 230, the PGW 210 includes a set TEID and a source address of an internal IP header, a destination address, a source port, and a destination. The port (destination port), protocol (protocol) information, and minimum bit rate information is stored inside (eg, a separate setting table). Then, a timer T waiting for the response is started.

The SGW 250 inserts the header extension field marked by the PGW 210 into the GTP-U header to the base station 230 without modification and transmits it (1102).

The base station 230, which has received the minimum bit rate marked on the GTP-U header by the PGW 210, checks whether support for the minimum bit rate requested for the corresponding traffic is possible (1103). At this time, the base station 230 checks whether support of the minimum bit rate is possible based on the current base station resource status, the resource status allocated to the terminal, and the maximum bit rate allowed to the terminal.

13 is a diagram illustrating a structure of a GTP-U header of user traffic transmitted to a PGW by a base station according to an embodiment of the present specification.

Depending on the result of the check, the base station 230 provides information on whether or not support is possible and, if so, for what time the support is possible, the support field 1302 and time field 1306 of the GTP-U header extension field 1300. Is marked and transmitted to the SGW 250 (1104). In this case, when there is no uplink data, a dummy flag marking is performed in the dummy status field 1304 of the GTP-U header extension field 1300 to indicate that there is no uplink data.

The base station 230 processes the GTP-U header for the received data and then transmits the processed data to the terminal.

The SGW 250, which has received data including whether or not to accept the minimum bit rate set by the base station 230, transmits the support status, the dummy status, and information of the time field to the PGW 210. The transmitted data is copied to the GTP-U header and transmitted (1106).

The PGW 210 receives a GTP-U header through a relay of the SGW 250 (1106). The PGW 210 compares the TEID and IP packet information (address, port, protocol) stored therein with the received IP packet information of the GTP-U header (1108). In this case, the PGW 210 compares the stored source address and port information with destination address and port information of the received packet, and compares the stored destination address and port information with source address and port information of the received packet. Compare.

If the result of the comparison matches and the support field and the time field of the received GTP-U header are marked, it is assumed that the stored minimum bit rate is guaranteed for the time marked in the time field, and the marked time During the period, the transmission rate is controlled by setting the minimum bit rate for the corresponding traffic as a lower limit.

On the other hand, if the information is found in the stored information but matches the information of the received TEID and the IP packet, but is marked as unaccept, the corresponding IP flow is processed with close gating and dropped. .

In the comparison of operation 1108, if the matching response does not come within the timer T set by the PGW 210 to wait for a response, the PGW 210 resets the timer up to N times while increasing a counter. ), the minimum bit rate value is set in the GTP-U header and transmitted to the base station 230. If a matching response of operation 1108 does not come from the base station 230 until the N attempts, the corresponding IP flow is closed gating. Handle and drop.

On the other hand, when a matching response is received in operation 1108 and the support status and the time are received, if the time has ended and the IP flow of the corresponding service/application is to be transmitted, the PGW 210 is at least The bit rate is marked in the extension field of the GTP-U header and the transmission to the base station is restarted.

14 is a diagram illustrating a congestion control method of a PGW according to a fourth embodiment of the present specification.

The PGW 210 marks the minimum bit rate information as an extension field in the GTP-U header of the traffic to be transmitted to the terminal 290 and transmits it to the SGW 250. At this time, the PGW 210 stores the TEID information and IP packet information (address, port, protocol) of the traffic therein. A timer is started to receive a response to the GTP-U header from the base station 230 (1400).

The PGW 210 receives the GTP-U header transmitted from the base station 230 from the SGW 250 (1402).

The PGW 210 compares the IP packet information and TEID information marked on the received GTP-U header with the IP packet information and TEID information stored in step 1400 to check whether they match (1404).

If the PGW 210 matches the result of the verification, the PGW 210 performs transmission rate control for the traffic using the support status field and the time field of the minimum bit rate recorded in the extended field of the received GTP-U header ( 1406).

It should be noted that the configuration diagram of the system illustrated in FIGS. 2 to 14, an exemplary diagram for a congestion control method, and an exemplary diagram for marking a GTP-U header are not intended to limit the scope of the present invention. That is, it should not be construed that all the constituent parts or steps of operation described in FIGS. 2 to 14 are essential constituents for the implementation of the invention. Can be implemented.

The above-described operations can be realized by providing a memory device storing a corresponding program code in an entity, a function, a base station, a load manager, or an arbitrary component in a terminal device. That is, an entity, a function, a base station, a load manager, or a control unit of a terminal device may execute the above-described operations by reading and executing a program code stored in a memory device by a processor or a CPU (Central Processing Unit).

An entity, a function, a base station, a load manager, or various components of a terminal device, and a module described in this specification are hardware circuits, for example, a complementary metal oxide semiconductor. It may be operated using hardware circuitry such as a combination of base logic circuitry, firmware, software, and/or hardware and firmware and/or software embedded in a machine-readable medium. As an example, various electrical structures and methods may be implemented using transistors, logic gates, and electrical circuits such as application-specific semiconductors.

Meanwhile, although specific embodiments have been described in the detailed description of the present invention, various modifications may be made without departing from the scope of the present invention. Therefore, the scope of the present invention is limited to the described embodiments and should not be defined, and should be defined by the scope of the claims and equivalents as well as the scope of the claims to be described later.

Claims (18)

In the method of a load manager in a mobile communication system,
Connecting to the base station through a DNS query (Domain Name Server Query);
Transmitting configuration information for reporting load information to the base station;
Receiving load information from the base station in response to the setting information; And
Triggering congestion control of the PGW or the SGW by transmitting a load notification message including information on a bearer selected for congestion control based on the received load information to a PGW (PDN Gateway) or SGW (Serving Gateway) Including,
The setting information includes reference information related to a criterion for the base station to report the load information and report target information related to a target to be reported by the base station as the load information,
The reference information includes a threshold value, and the report target information includes an amount of a resource being used by the base station.
The method of claim 1,
The receiving operation is an operation of receiving an identifier of the base station and the load information from the base station.
The method of claim 1,
The receiving operation is an operation of receiving an ID of a terminal causing congestion and the load information from the base station,
The ID of the terminal is a method of a load manager, characterized in that consisting of a code of a mobile management entity (MME) managing the terminal and a temporary ID of the terminal allocated by the MME.
The method of claim 3,
Before the triggering operation,
Requesting the bearer information from the MME using the code of the MME; And
And receiving a response including the bearer information from the MME.
The method of claim 1,
The receiving operation is an operation of receiving the address of the SGW, information about a bearer tunnel between the base station and the SGW, and the load information from the base station.
In the load manager of a mobile communication system,
It connects with a base station through a DNS query (Domain Name Server Query) method, transmits configuration information for reporting load information based on the resource usage state of the base station to the base station, and load information from the base station in response to the configuration information And transmits a load notification message including information on a bearer selected for congestion control to a PGW (PDN Gateway) or SGW (Serving Gateway) to trigger congestion control of the PGW or the SGW,
The setting information includes reference information related to a criterion for the base station to report the load information and report target information related to a target to be reported by the base station as the load information,
The reference information includes a threshold value, and the report target information includes an amount of a resource being used by the base station.
In the method of PGW (PDN Gateway) in a mobile communication system,
Performing deep packet inspection (DPI) on user data destined for a terminal through a base station to obtain an identifier for classifying the service of the data
action;
Marking an identifier for classifying the service and a minimum bit rate of the data on a GPRS Tunneling Protocol-User (GTP-U) header of the traffic and transmitting the data to a Serving Gateway (SGW);
Receiving information on a supportable value of a minimum bit rate and a support time value in response to the marked GTP-U header from the base station; And
And controlling the transmission rate of the data according to a value of whether the minimum bit rate is supported or not read from a GTP-U header of the received information.
The method of claim 7,
The operation of performing the transmission rate control,
The method of PGW, characterized in that the operation of controlling the transmission rate of the data according to a support value of the minimum bit rate and a support time value of the minimum bit rate read from the GTP-U header of the received information.
The method of claim 7,
Before the receiving operation,
Further comprising the operation of storing TEID (Tunnel Endpoint ID) and IP packet information of the data,
After the receiving operation,
And comparing the stored TEID and IP packet information with TEID and IP packet information of the received data to determine whether they match.
In the mobile communication system PGW (PDN Gateway),
A deep packet inspection (DPI) is performed on user data destined for the terminal through the base station to obtain an identifier for classifying the service of the data, and the identifier for classifying the service and the minimum bit rate of the data are determined by GTP-U ( GPRS Tunneling Protocol-User) a processor to mark the header; And
Transmitting the data to the SGW, and including a transceiver for receiving information on the supportable value and support time value of the minimum bit rate in response to the marked GTP-U header from the base station,
The processor controls the transmission rate of the data according to a value of whether to support the minimum bit rate read from the GTP-U header of the received information.
The method of claim 6,
And the transmission/reception unit receives an identifier of the base station and the load information in response to the setting information from the base station.
The method of claim 6,
The transceiver receives the ID of the terminal causing congestion and the load information in response to the setting information from the base station,
The ID of the terminal is a load manager comprising a code of a mobile management entity (MME) managing the terminal and a temporary ID of the terminal allocated by the MME.
The method of claim 12,
Before the triggering,
The transmission/reception unit requests the bearer information from the MME using the code of the MME,
Load manager, characterized in that receiving a response including the bearer information from the MME.
The method of claim 6,
The transmission/reception unit receives the address of the SGW, information on a bearer tunnel between the base station and the SGW, and the load information in response to the configuration information from the base station.
The method of claim 6,
The load information is received when the amount of the resource being used by the base station exceeds the threshold value.
The method of claim 10,
Wherein the processor controls the data rate according to a support value of the minimum bit rate and a support time value of the minimum bit rate read from a GTP-U header of the received information.
The method of claim 10,
The processor is:
Before receiving information on the supportable value and support time value of the minimum bit rate in response to the marked GTP-U header from the base station, store TEID (Tunnel Endpoint ID) and IP packet information of the data and,
After receiving information on the supportability value and support time value of the minimum bit rate in response to the marked GTP-U header from the base station, the stored TEID and IP packet information, and the received data PGW, characterized in that to compare the TEID and IP packet information to determine whether or not match.
The method of claim 1,
The load information is received when the amount of the resource being used by the base station exceeds the threshold value.

Images