KR20140035791A - Apparatus and method for controlling services under network congestion in wireless communication system - Google Patents

Abstract

The present invention relates to a method and a device for controlling a certain service in network congestion in a wireless communication system. The method for controlling a certain service in network congestion in a wireless communication system includes a receiving step receiving a paging message from a mobility management entity (MME) when a downlink packet is generated in a certain terminal; a confirming step confirming the setting state of a core network domain included in the paging message; and a paging processing step processing the paging message first when the core network domain is set as a packet-based voice call service. [Reference numerals] (S420) Confirm QVI/APN of Bearer. If QCI is 1/5 or IMS APN, it is for VoLTE, and set to CN=PS_Voice of Paging; (S440) Process a paging, that CN domain = PS_Voice or CN domain = PS, voice indicator, prior to a paging that CN domain = PS; (S450) Existing operation

Description

Method and apparatus for controlling a specific service in a network congestion situation in a wireless communication system

The present invention relates to a technology for controlling a service in a wireless communication system, and more particularly, to a method and apparatus for preferentially processing paging for a specific service that is sensitive to delay when network congestion occurs.

The present invention also relates to a method and apparatus for improving user experience service quality through control for each service, especially when network congestion occurs.

The invention also relates in particular to a method and apparatus for an IMS network to notify a user of a call failure due to operator determined barring.

In general, mobile communication systems have been developed to provide voice services while guaranteeing user activity. However, the mobile communication system is gradually expanding not only to voice but also to data service, and now it has developed to the extent of providing high-speed data service. However, in a mobile communication system in which a service is currently provided, a lack of resources and users demand higher speed services, and therefore, a more advanced mobile communication system is required.

As a system under development in the next generation mobile communication system in response to this demand, standard works for LTE (Long Term Evolution) are underway in the 3rd Generation Partnership Project (3GPP). LTE is a technology that implements high-speed packet-based communication with a transmission rate of up to 100 Mbps. Various methods are discussed for this purpose. For example, there is a method of reducing the number of nodes located on a communication path by simplifying the structure of a network, and a method of approaching wireless protocols to a wireless channel as much as possible.

1 is a diagram illustrating a structure of a general LTE mobile communication system.

1, a radio access network of an LTE mobile communication system includes an Evolved Node B (EUTRAN) 110, a Mobility Management Entity 120, And an S-GW (Serving-Gateway, 30). A user equipment (UE) 100 accesses an external network through an ENB, an S-GW, and a P-GW (PDN-Gateway).

The ENB (base station) 110 is a Radio Access Network (RAN) node, which corresponds to the RNC of the UTRAN system and the BSC of the GERAN system. The ENB 110 is connected to the UE 100 through a radio channel and plays a role similar to that of the existing RNC / BSC. The ENB can use multiple cells at the same time.

In LTE, all user traffic, including real-time services such as Voice over IP (VoIP) over the Internet protocol, is serviced through a shared channel, which requires a device that collects scheduling information of UEs and schedules them. In charge.

The MME 120 is a device that is in charge of various control functions. One MME may be connected to a plurality of base stations.

The S-GW 130 is a device for providing a data bearer, and generates or removes a data bearer under the control of the MME 120.

An application function (AF) 140 is a device that exchanges information associated with an application at the user and application level.

Policy Charging and Rules Function (PCRF) 150 is a device that controls a policy related to a quality of service (QoS) of a user, and corresponds to a policy and charging control (PCC) rule. Is transmitted to and applied to the P-GW 160. Policy Charging and Rules Function (PCRF) 150 is an entity that collectively controls QoS and billing for traffic. In general, UP refers to UE 100 and RAN node 110 through which user data is transmitted and received. , Refers to a path connecting the S-GW 130 at the RAN node 110 and the P-GW 160 at the S-GW 130. However, a portion of the path using a radio channel with a severe resource limitation is a path between the UE 100 and the RAN node 110.

In wireless communication systems such as LTE, the unit that can apply QoS is an EPS bearer. One EPS bearer is used to transmit IP flows having the same QoS requirements. QoS bearer parameters can be assigned to an EPS bearer, which includes a QoS Class Identifier (QCI) and an Allocation and Retention Priority (ARP). The QCI is a parameter that defines the QoS priority as an integer value, and the ARP is a parameter that determines whether to allow or reject the creation of a new EPS bearer.

The EPS bearer corresponds to the PDP context of the GPRS system. One EPS bearer belongs to a PDN connection, and the PDN connection may have an access point name (APN) as an attribute. If a PDN connection is created for an IMS service, such as VoLTE, the corresponding PDN connection must be created using a well-known IMS APN.

On the other hand, in the LTE network, CSFB (CS) using IMS-based Voice over LTE (VoLTE) technology as a packet switched method to support voice calls or recycling a CS (circuit switched) method of 2G / 3G systems fall back) technology. VoLTE in LTE network is a term that can be used in the same concept as Voice over IMS (VoIMS).

If the UE is in idle mode, downlink data to be sent to the UE is generated, or if a mobile terminating call is generated for the UE, the UE is received. Paging is transmitted to indicate that there is data (or call setup) to be made. Paging resources available in one cell are limited, and if paging for multiple terminals is crowded, some terminals may be due to limited paging resources. A situation may arise in which only paging for a device can be sent. A voice call is a service that is very sensitive to transmission delay. If such paging channel congestion occurs, transmission of paging is delayed or paging is dropped.

On the other hand, various applications are emerging due to the increase in smartphone use, and in the LTE network that supports only the packet network, these smartphone applications are all treated as packet data applications together with VoLTE and RCS provided by the operator. Therefore, there is a need for a method that can block each application differentially while the network is overloaded.

On the other hand, as described above, since the barring service is activated as the user registers, if the operator wants to restrict the service arbitrarily, the terminal context that must be maintained in the HSS or TAS or SCSCF to perform this operation. (UE context) is not defined. In addition, there is no method for notifying the UE that a session attempted by the UE has failed due to operator determined barring.

SUMMARY OF THE INVENTION The present invention has been made to solve the above problems, and provides a method and apparatus for preferentially performing paging for a service delay-sensitive service such as a voice call when a plurality of pagings should be transmitted in a limited resource. It is for that purpose.

Another object of the present invention is to provide a method and an apparatus capable of differentially blocking the execution of respective applications installed in a user terminal in a state in which an overload occurs in a network.

In addition, another object of the present invention is to notify the terminal when the operator applies the operator determined bar (Operator Determined Barring), and to define the subsequent procedure of the terminal.

In the wireless communication system of the present invention for solving the above problems, a method of controlling a base station in a receiving step of receiving a paging message from a mobility management entity (MME) when a downlink packet for any terminal; And checking a setting state of the core network domain included in the paging message, and if the core network domain is set to a packet-based voice call service, paging processing to process the paging message first. do.

In addition, in the wireless communication system of the present invention, a base station for controlling a service includes a transceiver for transmitting and receiving signals to and from nodes of the wireless communication system, and a mobility management entity (MME) when a downlink packet is generated for any terminal. A control unit for receiving a paging message, checking a setting state of a core network domain included in the paging message, and prioritizing the paging message when the core network domain is set to a packet-based voice call service. Characterized in that.

According to an embodiment of the present invention, when a call is received for a user terminal in a system using VoLTE, a user who is generated due to a long voice call setup time is prevented from delaying transmission of paging for a received call or dropping paging. Diminished service quality can be prevented.

In addition, the present invention can block each application differentially in the state of the overload occurs in the network, it is possible to prevent the service quality deterioration while congestion is effectively controlled.

In addition, according to the present invention, the operator may apply an operator determined barring (ODB), and the terminal may know that the session request has failed due to the ODB and may clear the session.

1 is a diagram illustrating a structure of a general LTE mobile communication system.
2 is a flowchart showing an operation sequence of nodes of a wireless communication system according to the first embodiment of the present invention.
3 is a flow chart showing another operation sequence of wireless communication system nodes according to the first embodiment of the present invention.
4 is a flowchart showing another operation sequence of nodes in a wireless communication system according to the first embodiment of the present invention.
FIG. 5 is a flowchart illustrating a method of determining that a packet generated in an idle UE is for VoLTE when an MME receives a DDN message from an SGW according to the first embodiment of the present invention.
FIG. 6 is a diagram illustrating a method for determining whether a corresponding packet is a packet for VoLTE and notifying the MME when the SGW receives a user packet from the PGW according to another embodiment of the present invention.
7 and 8 are flowcharts illustrating a method for notifying the MME of when congestion occurs in a specific channel and when congestion is resolved according to another embodiment of the first embodiment of the present invention.
FIG. 9A is a flowchart illustrating an operation sequence of an MME that receives information from a ENB that a paging channel is congested. FIG.
9B is a flowchart illustrating the operation of nodes in a network in a congestion situation using service marking.
10 is a flowchart illustrating a process of differentially blocking execution of respective applications installed in a terminal using an application ID according to the second embodiment of the present invention.
FIG. 11 is a flowchart illustrating a process of determining whether or not restrictions are applied when application barring information is broadcast through SIB in an allowed form from an eNB 1010.
FIG. 12 is a flowchart illustrating a process of determining whether to restrict an application barring information when the application barring information is broadcasted through an SIB in an unlicensed form from the eNB 1010.
FIG. 13 illustrates an example of an application map that an operator broadcasts through an eNB. FIG.
FIG. 14 is a flowchart illustrating a process of differentially blocking execution of respective applications installed in a terminal using an application ID according to solution 2; FIG.
FIG. 15 is a flowchart illustrating a process of differentially blocking execution of respective applications installed in a terminal according to Solution 3 of Embodiment 2 of the present invention. FIG.
16 shows an example of a packet filter structure according to an embodiment of the present invention.
FIG. 17 is a flow chart showing the procedure for solution 4 of the second embodiment of the present invention. FIG.
FIG. 18 is a diagram schematically illustrating an EPS network and an IMS network on which an embodiment of the present invention is based. FIG.
FIG. 19 illustrates Barring of all outcoming call operations defined in an IMS network. FIG.
20 is a flowchart illustrating a process in which a terminal 1810 registers with an IMS network and receives ODB according to an embodiment of the present invention.
21 is a diagram showing an example of a response message proposed in an embodiment of the present invention.
FIG. 22 illustrates an example of a UE context passed between an HSS and a TAS, in accordance with an embodiment of the present invention. FIG.
FIG. 23 is a diagram illustrating an example of an XML schema used for an ODB implementation according to an embodiment of the present invention. FIG.
24 and 25 are flowcharts illustrating a method for notifying the MME of when congestion occurs in a specific channel and when congestion is resolved according to an embodiment of the present invention.
26 is a flowchart illustrating operation according to another embodiment of the present invention.
27 is a flowchart illustrating operation according to another embodiment of the present invention.

Hereinafter, preferred embodiments of the present invention will be described with reference to the accompanying drawings. In the following description, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear.

In addition, in the following description of the embodiments of the present invention, the basic third generation partnership project (3GPP) LTE system will be the main target, but the main points of the embodiments of the present invention have a similar technical background and system form other It is possible to apply a slight modification in a communication / computer system without departing from the scope of the present invention, which will be possible in the judgment of a person skilled in the art.

Embodiments of the present invention described below will be described by dividing into first to third embodiments.

In this case, the first embodiment describes a method for preferentially performing paging for a service that is sensitive to transmission delay, such as a voice call, when it is necessary to transmit a plurality of paging on a limited resource.

In addition, the second embodiment describes a method capable of differentially blocking the execution of each application installed in the user terminal in the state of overload in the network.

In addition, the third embodiment describes a process of notifying the terminal when the operator applies the operator determined barring.

<First Example >

The following describes a first embodiment, which is a method for preferentially performing paging for a service sensitive to transmission delay, such as a voice call.

A service sensitive to the transmission delay illustrated in the first embodiment may include a packet based voice call. A packet-based voice call is a concept compared to a conventional circuit-based voice call, and specifically, may include a VoLTE call and a VoIMS call. Hereinafter, for convenience of explanation, it is assumed that a packet-based voice call is a VoLTE call.

2 is a flowchart showing an operation sequence of nodes of a wireless communication system according to the first embodiment of the present invention.

When the downlink packet for the terminal 210 entering the idle state reaches the SGW 240, the SGW 240 sends a downlink data notification (DDN) to the MME 230 in step S205. Send a message. The DDN message includes an EPS bearer identifier (ID) to inform which EPS bearer the packet has arrived.

In step S210, the MME 230 may determine that a VoLTE call has occurred when the QCI of the corresponding EPS bearer is 1 or 5 based on the EPS bearer context referred to by the EPS bearer ID. This is because the EPS bearer uses QCI 1 (media bearer) or QCI 5 (IMS signaling bearer) when using VoLTE. Alternatively, the MME 230 checks the APN of the PDN connection (PDN connection) to which the corresponding EPS bearer belongs, and if it matches with the IMS APN, may recognize that a VoLTE call has occurred.

Through the above method, if the MME 230 detects that a VoLTE call has occurred, even though the VoLTE call is actually a service supported through the PS core network, the MME 230 performs the ENB in step S215. A core network domain (CN Domain) included in the paging message sent to 220 is set to a circuit switched (CS).

At the same time, the MME 230 sets the CS paging for VoIMS flag to true in the UE context in order to remember that CS Paging was actually transmitted for the VoLTE call, which is PS data.

Then, in step S220, the ENB 220 is configured to preferentially transmit the paging of the CN domain to CS rather than the paging of the CN domain to PS according to the characteristics of the CS call sensitive to delay.

Then, in step S225, the eNB 220 transmits paging for the terminal 210 to the terminal prior to paging for another PS domain according to the configuration.

Then, the terminal 210 receiving the paging from the eNB 220 transmits an extended service request message (Extended Service Request) to the MME 230 in step S230, the CSFB response indicator included in the extended service request message The IE (CSFB response indicator IE) is set to include mobile terminating CS fallback or 1xCS fallback and send.

Upon receiving the extended service request message from the terminal 210, the MME 230 transfers to the corresponding terminal even if the terminal includes a CSFB response indicator in the extended service request message in step S235. It can be seen that the paging for VoIMS set in step (CS paging for VoIMS) is True. Accordingly, the MME 230 may know that a VoLTE call is generated instead of the CS call, and performs a general service request process instead of the CSFB process in a later procedure.

Accordingly, the MME 230 transmits an initial context setup request message to the eNB 220 in step S240, and the eNB 220 performs an RRC connection reconfiguration message for setting a data radio bearer (DRB) in step S245. To the terminal 210.

When the terminal 210 receives the RRC connection reconfiguration message for setting the data radio bearer (DRB) from the ENB 220 in step S250, the terminal 210 recognizes that the extended service request transmitted previously has been successfully performed. .

Specifically, when a terminal performing PS-based communication transmits an extended service request in response to paging for a CS, a system change to a CS network must be performed before the extended service request of the terminal is performed. This is considered successful.

On the other hand, in the present invention, when the terminal receiving the CS paging transmits the extended service request, the extended service request when receiving the bearer setup-related message according to the conventional PS-based service request operation (not a system change) You will notice that this was successful.

2, in brief, the MME 230 instructs the eNB 210 to transmit CS paging to the UE 210 even though a PS call other than the CS is generated. Record it. Since the terminal 210 receives the CS paging from the eNB 220, the terminal 210 transmits the extended service request message to the MME 230, and the MME 230 checks the recorded terminal context and the CS extended service of the terminal. It can be identified that the request is actually about a PS service request, and accordingly performs the procedure according to the PS service request.

3 is a flowchart illustrating another operation sequence of nodes of the wireless communication system according to the first embodiment of the present invention.

When the downlink packet for the terminal 310 entering the idle state reaches the SGW 340, the SGW 340 transmits a downlink data notification (DDN) message to the MME 330. The DDN message includes an EPS bearer identifier (ID) to inform which EPS bearer the packet has arrived.

The MME 330 may determine that a VoLTE call has occurred when the QCI of the corresponding EPS bearer is 1 or 5 based on the EPS bearer context referred to by the EPS bearer ID in step S320. This is because the EPS bearer uses QCI 1 (media bearer) or QCI 5 (IMS signaling bearer) when using VoLTE. Alternatively, the MME 330 may check the APN of the PDN connection to which the corresponding EPS bearer belongs, and know that a VoLTE call occurs even if it matches the IMS APN.

Through the above method, if the MME 330 detects that a VoLTE call has occurred, even though the VoLTE call is actually a service supported through the PS core network, the MME 330 sends the ENB 320 in step S330. Set the CN domain included in the paging message to CS.

At the same time, the MME 330 sets the CS paging for VoIMS flag to true in the UE context in order to remember that CS Paging was actually transmitted for the VoLTE call, which is PS data.

Then, in step S340, the ENB 320 is configured to preferentially transmit the paging of the CN domain to CS rather than the paging of the CN domain to PS according to the characteristics of the CS call sensitive to delay.

Then, in step S350, the eNB 320 transmits the paging for the terminal 310 to the terminal 310 in preference to paging for another PS domain according to the configuration.

The terminal 310 receiving the paging from the eNB 320, even if the cn_Domain is set to CS in the paging message, the most recently received Attach Accept message or TAU accept message from the MME 330 If IMS voice over PS session in S1 mode supported is received through EPS network feature support IE (IE) and the IMS registration is successful, the extended service for CSFB in step S370. The MME 330 transmits a service request message for the PS service instead of the extended service request message.

That is, according to the embodiment of Figure 3, even if the terminal 310 receives the CS paging, if a specific condition is met, instead of the extended service request message for the CS service request, the service request message for the PS service request To the MME 330.

4 is a flowchart illustrating another operation sequence of the nodes of the wireless communication system according to the first embodiment of the present invention.

When the downlink packet for the terminal 410 entering the idle state reaches the SGW 440, the SGW 440 transmits a downlink data notification (DDN) message to the MME 430. The DDN message includes an EPS bearer identifier (ID) to inform which EPS bearer the packet has arrived.

In step S420, the MME 430 may determine that a VoLTE call has occurred when the QCI of the corresponding EPS bearer is 1 or 5 based on the EPS bearer context referred to by the EPS bearer ID. This is because the EPS bearer uses QCI 1 (media bearer) or QCI 5 (IMS signaling bearer) when using VoLTE. Alternatively, the MME 430 may check the APN of the PDN connection to which the corresponding EPS bearer belongs, and know that a VoLTE call has occurred even if it matches the IMS APN.

In this case, the MME 430 transmits a paging message sent to the ENB 420 in step S430 by including information indicating that the CN domain is PS, but indicating paging for the VoLTE service. As shown in the figure, the MME 430 sets the CN domain of the paging message to PS_Voice. As another example, the MME may include a separate voice indicator indicating that the service is for a voice call while setting the CN domain of the paging message to PS.

Then, in step S440, even if the CN domain is PS, if the ENB 420 knows that it is for VoLTE service, that is, it is configured for packet-based voice call service, the ENB 420 is set to transmit the corresponding paging. As shown in the figure, when the CN domain of the paging message is PS_Voice, the CN domain is PS. Upon receiving this, the terminal performs a general service request process in step S450.

According to the embodiment of FIG. 4, when downlink data, particularly VoLTE, is generated for the terminal 410, the MME 430 may inform the eNB 420 of paging information including an identifier indicating that a packet-based voice call service has occurred. To pass. The eNB 420 then preferentially processes paging for the packet-based voice call service over the CS service.

FIG. 5 is a flowchart illustrating a method of determining whether a packet generated in an idle UE is for VoLTE when an MME receives a DDN message from an SGW according to the first embodiment of the present invention.

When the downlink packet for the terminal entering the idle state reaches the SGW, the MME receives a downlink data notification (DDN) message from the SGW in step S510. The DDN message includes an EPS bearer identifier (ID) to inform which EPS bearer the packet has arrived.

Then, in step S520, the MME may determine that a VoLTE call has occurred when the QCI of the corresponding EPS bearer is 1 or 5 based on the EPS bearer context indicated by the EPS bearer ID. This is because the EPS bearer uses QCI 1 (media bearer) or QCI 5 (IMS signaling bearer) when using VoLTE. Or, the MME checks the APN of the PDN connection to which the corresponding EPS bearer belongs, and it can be known that the VoLTE call occurs even if it matches the IMS APN. The operation of the MME shown in FIG. 5 may be used together with the embodiments shown in FIGS. 2 to 4 described above.

As a result, the MME determines that the downlink packet is VoLTE in step S530 when the QCI of the EPS bearer is 1 or 5 in step S520, or when the APDN matches the IMS APN in the PDN connection. If not, the MME proceeds to step S540 and determines that the downlink packet is not VoLTE.

FIG. 6 is a diagram illustrating a method of determining whether a corresponding packet is a packet for VoLTE and notifying the MME when the SGW receives a user packet from the PGW according to another embodiment of the present invention.

The SGW 620 may determine that a VoLTE call has occurred when the QCI of the EPS bearer is 1 or 5 with reference to the context of the bearer to which the packet received from the PGW 610 belongs. This is because the EPS bearer uses QCI 1 (media bearer) or QCI 5 (IMS signaling bearer) when using VoLTE.

Alternatively, the SGW 620 may check the APN of the PDN connection to which the EPS bearer belongs, and know that a VoLTE call occurs even if it matches the IMS APN. In this case, the SGW 620 includes an IE indicating that it is for VoIMS in the DDN message transmitted to the MME 610 or sets a priority level to be sent.

When the MME 620 receives the DDN message from the SGW 620, the MME 620 recognizes that the DDN is for VoLTE, and when the MME 620 performs the operation corresponding to FIGS. 2 to 4 described above, it separately identifies the VoLTE call. Can be omitted.

7 and 8 are flowcharts illustrating a method for notifying the MME of when congestion occurs in a specific channel and when congestion is resolved according to another embodiment of the first embodiment of the present invention.

In this embodiment, a case where the paging channel is congested will be described with an example. When the paging channel becomes congested, the eNB 710 transmits an overload start message to the MME 720 in step S710. This message may include the PLMN ID of the congested cell, the cell ID, and the channel on which congestion occurred (paging channel in this example), the level of congestion, or the level of load desired to be reduced due to congestion, and how long congestion will last. .

Receiving the overload start message from the eNB 710, the MME 720 considers that the corresponding channel of the cell is congested from a subsequent procedure, and if a congestion duration is included in the overload start message, a timer is executed to execute the congestion time. The cell is considered congested until it expires.

As illustrated in FIG. 8, the MME 720 may receive an overload stop message indicating that the corresponding cell is no longer congested from the eNB 710 through step S810. Then, the MME 720 considers that the congestion state for the corresponding channel of the cell has been cleared. Alternatively, if the overload initiation message includes a congestion duration, congestion continues until the timer for congestion duration expires. Alternatively, even if the congestion duration is not included in the overload initiation message, the MME may operate the timer according to the internally set time, and consider that the congestion continues until the timer expires.

Meanwhile, when congestion occurs or is resolved for a specific channel (paging channel in this example) of a specific cell of the eNB, the eNB may inform the MME through S1AP signaling as shown in FIGS. 7 to 8. In another embodiment, the O & M method may be used. This is done by the ENB notifying the appropriate O & M server of its congestion status, and the O & M server notifying other nodes (MME, PGW, etc.) of the ENB congestion status. The message sent between the nodes includes information similar to that shown in Figures 7-8 above. The MME and the PGW that receive this are considered to be congested or that the specific cells and channels of the corresponding ENB are congested or have proper control.

FIG. 9A is a flowchart illustrating an operation sequence of an MME that receives information that a paging channel is congested from an ENB.

In step S910, the MME 720 receives a DDN message for an idle UE from the SGW. In step S920, the MME 720 selects a candidate group of cells to which the paging message is to be transmitted according to the stored context. For each candidate cell, the MME 720 first checks in step S930 whether an overload start message indicating that the paging channel of the cell is congested is received.

If the overload start message is received from the corresponding cell, the MME 720 responds to the DDN using the method described above (method of finding out directly by the MME of FIG. 5 or the method of SGW of FIG. 6 notifying through DDN) in step S940. Find out if the service to which the packet belongs is VoLTE or if the service has high priority. If the VoLTE service is correct or a high priority service, the MME 720 proceeds to step S950 and preferentially delivers a paging message to the corresponding cell. At this time, the MME 720 sets the CN domain of the paging message transmitted to the PS.

If the EPS bearer, known as DDN, is not for VoLTE service or is of low priority, the MME 720 may receive an overload stop message indicating that the paging channel congestion for that cell has ended from the ENB using that cell. Until the transmission priority for the paging message is lowered.

Note that the above embodiment does not necessarily include the process of reporting the congestion. That is, even if the MME does not report that a cell of a particular ENB is congested, the MME may preferentially transmit paging for the VoLTE service to paging for a general PS data service.

9A, the MME 720 may determine whether paging is transmitted based on state information on a paging channel of a cell informed by the ENB. Accordingly, paging for VoLTE services can be preferentially transmitted through a congested paging channel. Alternatively, paging transmission may be determined according to the congestion situation of the ENB through the O & M-based method described above.

9B is a flowchart illustrating operation of nodes in a network in a congestion situation using service marking.

As described above with reference to FIGS. 7 to 8, when congestion occurs in a specific cell and a specific channel of the eNB, the eNB may inform the MME and the PGW of the congestion state by using a signaling method or an O & M method. The operation of the PGW / TDF / MME described with respect to 9b may proceed in consideration of this. However, it should be noted that the embodiment shown in FIG. 9B does not necessarily include the reporting of the congestion.

First, the terminal performs an access procedure to the network in step S970, and after completing the access procedure, the terminal may switch to the idle mode in step S972. In the meantime, if congestion occurs in a particular cell or channel in the ENB, the ENB can inform the MME.

If a downlink packet for the UE is generated as in step S976, the TDF or TGW analyzes the content of the downlink packet and transmits service information to the next node in step S978. Put it in the Service Class Identity (SCI) field of (GTP-U). According to an embodiment of the present invention, the SCI value may be an identifier for identifying a corresponding packet based on a PS-based voice call service or another service (messaging, video call, RCS-rich communication suite).

If there is an SCI field marked in the header of the GTP-U packet received through the TDF or the PGW, the SGW extracts it in step S984. In step S986, the SGW includes the SGW in the SCI field of the DDN message delivered to the MME.

Upon receiving the DDN, the MME selects a candidate cell to send paging, and if it is determined that the paging channel of the cell is congested, the MME checks the SCI field entered by the SGW in the DDN in step S988. If paging for the confirmation elapses, the PS voice call service or the service having a high priority, the process proceeds to step S990 and processes the priority, otherwise, a determination process for delaying paging is performed.

Meanwhile, in the above embodiments, when congestion occurs between the control plane (eNB) and the core network or the exchange of control signaling between the core network entities), paging of a high priority service such as a PS voice call is processed. The paging for the low priority service can be extended to the embodiment which does not process.

In addition, if congestion occurs in the control plane (e.g., heavy load handling paging at the base station or MME), another effective way to reduce signaling in the control plane is to allow the user in which the SGW is idle. When a downlink message is generated for a terminal, the downlink data notification (DDN) message is transmitted. If a downlink message is generated for the user terminal in the idle state, the SGW sends a DDN message to the MME, and the MME sends a paging request to the base station (s) based thereon. The target base station (s) sends a paging message. If the user terminal receives the paging message, the terminal performs a service request process for receiving the downlink message. As such, the DDN transmitted by the SGW causes various control message exchanges such as paging and service requests, thus increasing the congestion in the control plane.

To solve this problem, the MME may ask the SGW to limit the number or frequency of DDN messages when congestion occurs in the control plane. In this request process, the MME may inform the SGW about which services the DDN should restrict or allow, and may also provide information for determining the degree of restriction and the time when the restriction is applied in the SGW. Upon receiving this, if the downlink message to be delivered to the UE belongs to the target service, the SGW determines whether to transmit the DDN message according to the degree of restriction and the application time.

26 is a flowchart illustrating operation according to another embodiment of the present invention.

First, in step S2610, the MME determines whether congestion has occurred in the control plane. This determination process is performed by comparing the throughput with the number of operations (or messages) to be processed, for example, or congestion information (eg, a channel in which congestion occurs when connected eNBs inform congestion as in step S2605). Information indicating that this is a paging channel).

Subsequently, when the MME receives the DDN message from the SGW in step S2615, while transmitting a DDN Ack (Downlink Data Notification Acknowledge) message to the SGW in step S2620, the IE indicates that the number of DDNs should be reduced due to congestion. (For example, it may include DL traffic throttling IE).

In this case, the IE may include one or more of restrictions or exceptions, a throttling delay, and a throttling factor as information that can be used to control a DDN message in the SGW. have.

If the subject of the restriction is included, the SGW may apply the DDN transmission restriction if the target includes a downlink message generated in step S2625. If an exception destination is included, the SGW does not apply DDN transmission restrictions if the downlink message that occurred is included in the destination. In this case, Allocation and Retention Priority (ARP), QoS Class Identifier (QCI), UE identifier, or Service Class Identifier (SCI) may be used as information for identifying a target. If a time limit is included, the SGW applies the limit until the time passes. The degree of restriction is a value that indicates the percentage of messages that should be restricted among the DDN messages that need to be transmitted.

On the other hand, when the restriction request of the MME does not include the restriction / exception target, the SGW may determine the target to apply the restriction based on the preset ARP or QCI.

For example, if the MME informs an exception of 5 for QCI, 10 for throttling delay, and 40 for throttling factor in the DDN Ack message, the SGW will send packets belonging to bearers whose QCI is not 5 for 10 seconds. Only 60% of the resulting DDN messages are delivered to the MME. If the MME informs SCI of the messenger service SCI, the throttling delay 10 seconds and the throttling factor 40 via the DDN Ack message, the SGW sends the GTP-U header of the packet received from the target SCI and PGW for 10 seconds. Compares the SCI field of the SCI field and delivers only 60% of the required DDN message to the MME due to matching packets. If the MME simply informs the throttling delay of 10 seconds and the throttling factor of 40%, and the SGW configuration does not apply the restriction to packets belonging to bearers with QCI number 5, the SGW for 10 seconds bearers with QCI not 5 Only 60% of the necessary DDN messages are delivered to the MME due to the packets belonging to the.

On the other hand, if congestion occurs in the control plane, the transmission request for the DDN message may be requested through a separate message instead of the DDN ack message.

27 is a flowchart illustrating operation according to another embodiment of the present invention.

First, in step S2710, the MME determines whether congestion has occurred in the control plane. This determination process is performed by comparing the throughput with the number of operations (or messages) to be processed, for example, or congestion information (e.g., congestion has occurred when connected eNBs inform congestion, as in step S2705). Information indicating that the channel is a paging channel).

Thereafter, the MME may proceed to step S2715 and may transmit a message indicating a request to reduce the number of DDNs due to congestion, for example, an overload start or error indication message, to the SGW. In this case, the message may include one or more of the object of restriction, the object of exception, the time that the restriction is applied (throttling delay), and the degree of restriction (throttling factor) as information that can be used when the SGW controls the DDN message. .

If the target of the restriction is included, the SGW may apply the DDN transmission restriction if the downlink message generated as in step S2720 is included in the target.

If an exception destination is included, the SGW does not apply DDN transmission restrictions if the downlink message that occurred is included in the destination. In this case, Allocation and Retention Priority (ARP), QoS Class Identifier (QCI), UE identifier, or Service Class Identifier (SCI) may be used as information for identifying a target. If a time limit is included, the SGW applies the limit until the time has passed. The degree of restriction is a value that indicates the percentage of messages that should be restricted among all DDN messages. If the restriction request of the MME does not include the restriction / exception target, the SGW may determine the target to which the restriction is applied based on a preset ARP or QCI. The operation of the SGW receiving this is the same as the embodiment based on the DDN Ack message. If congestion in the control plane is cleared, the MME may explicitly send a message to the SGW to inform the SGW that the restriction of the DDN message is no longer needed.

<2nd Example >

Hereinafter, a description will be given of a second embodiment, which is a method for differentially blocking execution of respective applications installed in a terminal in a state in which an overload occurs in a network.

One) solution  One : application ID How to use

10 is a flowchart illustrating a process of differentially blocking execution of respective applications installed in a terminal using an application ID according to the second embodiment of the present invention.

First, the terminal 1000 performs an attach procedure to the network in step S1000. Then, in step S1005, the operator sets an application name and an application ID to the terminal through OMA-DM. Then, the terminal framework and the modem 1002 of the terminal 100 correspondingly stores the application name and the application ID.

The operator then broadcasts the ID of the application to block access to the network and the parameters for blocking by using the SIB of the base station through step S1030. In this case, the transmitted parameter may include a barring time and a barring factor.

Meanwhile, when the application 1001 of the terminal 1000 opens a socket for data transmission and reception, the application 1001 uses the name of the application or the application ID received from the operator as a parameter in step S1015. To the terminal framework and modem 1002.

Then, an OS or service framework in the terminal that creates a socket and allocates a port number, that is, the terminal framework and the modem 1002 are used by the terminal and the assigned port number in step S1020. The application name, the application name transmitted by the application 1001 to the parameter, and the application ID mapped with the application name assigned by the operator. ) Stores the mapping between the sender address, sender port used by the operator, and the ID set by the operator for the application.

In operation S1025, the application 1001 attempts to transmit data, thereby checking whether there is a barring when attempting to transmit a request for switching to the connected mode.

The checking of the barring is performed in step S1035 by using mapping information stored by the terminal framework and the modem 1002. The terminal framework and the modem 1002 check, from the stored mapping information, an application ID mapped to a sender address and a sender port of an IP packet that the application 1001 attempts to transmit. The terminal framework and the modem 1002 check whether the corresponding application ID corresponds to baring among application barring information included in the SIB broadcast from the eNB 1010.

If the barring is applicable, the terminal framework and the modem 1002 inform the application 1001 of the reject in step S1040. On the other hand, if it does not correspond to the barring (Barring), the terminal framework and modem 1002 transmits a service request (service request) to the network to switch to the connected mode (connected mode) in step S1050.

Meanwhile, in step S1035 of FIG. 10, a process of determining whether the terminal framework and the modem 1002 are barring will be described in detail with reference to FIGS. 11 and 12. First, FIG. 11 is a flowchart illustrating a process of determining whether or not restrictions are applied when application barring information is broadcasted through an SIB in an allowed form from an eNB 1010.

In step S1110, the terminal framework and the modem 1002 check the application ID and the index mapped to the source address and the port number of the IP packet transmitted from the application 1001. In step S1115, the terminal framework and the modem 1002 determine whether the application ID or the index is being broadcast from the eNB.

If the application restriction information is defined to be broadcast in the form of Allowed as shown in FIG. 10, and the restriction information is not broadcasted by the base station, the terminal framework and the modem 1002 proceed to step S1120 to reject data transmission. Message to the application 1001.

On the other hand, the flowchart of FIG. 10 is defined such that the application restriction information is broadcast in the form of Allowed, and if the restriction information is broadcast by the base station, the terminal framework and the modem 1002 proceed to step S1125, and the limiting factor. It is determined whether the load factor of the baring factor is a value between 0 and 1. If the value is not between 0 and 1, the terminal framework and the modem 1002, if the load factor is 0, proceeds to step S1130 and delivers a message to the application 1001 that rejects data transmission. On the other hand, if the load factor is 1, the terminal framework and the modem 1002 proceeds to step S1135 and sends a service request to the network to request the switch to the connected mode.

On the other hand, if the load factor is a value between 0 and 1, the terminal framework and modem 1002 proceeds to step S1140 to generate a random number to generate the random number and the size of the load factor generated. Compare. If the random number is larger than the load factor, the terminal framework and the modem 1002 proceeds to step S1135 to send a service request to the network to request the switch to the connected mode. On the other hand, if the random number is smaller than the load factor, the terminal framework and modem 1002 proceeds to step S1130 and delivers a message to the application 1001 rejecting data transmission.

In brief summary of FIG. 11, if the application ID of the application to be executed is not transmitted through the SIB of the eNB, the terminal regards the barring target and applies a barring factor. When applying a barring factor, if it is set as a load factor, a value between 0 and 1 is transmitted to the base station as a load factor, and the terminal generates a random number between 0 and 1 If the number is greater than (or less than) the number broadcasted from the eNB, it reports that it has passed the barring and transmits a connection request. If Barring does not pass, that is, barring, it notifies the application 1001 that data transmission has been rejected.

Meanwhile, FIG. 12 is a flowchart illustrating a process of determining whether or not restrictions are applied when application barring information is broadcasted through an SIB in a disallowed form from the eNB 1010. That is, if restriction information is not broadcasted, it is determined that it is not barring. If restriction information is broadcast, it is calculated whether barring is applied.

In step S1210, the terminal framework and the modem 1002 check the application ID and the index mapped to the source address and the port number of the IP packet transmitted from the application 1001. In step S1215, the terminal framework and the modem 1002 determine whether the application ID or the index is broadcast from the eNB.

If not broadcasting, the terminal framework and modem 1002 proceeds to step S1220, and sends a service request to the network to request to switch to the connected mode.

On the other hand, if broadcasting, the terminal framework and modem 1002 proceeds to step S1225, and determines whether the load factor (barring factor) of the load factor (bar factor) is a value between 0 and 1. If the value is not between 0 and 1, the terminal framework and modem 1002, if the load factor is 1, proceeds to step S1230 and transmits a message to the application 1001, which rejects data transmission. On the other hand, if the load factor is 0, the terminal framework and modem 1002 proceeds to step S1235 and sends a service request to the network to request the switch to the connected mode.

On the other hand, if the load factor is a value between 0 and 1, the terminal framework and modem 1002 proceeds to step S1240 to generate a random number to generate the random number and the size of the load factor generated. Compare. If the random number is smaller than the load factor, the terminal framework and the modem 1002 proceeds to step S1245 and sends a service request to the network to request the switch to the connected mode. On the other hand, if the random number is larger than the load factor, the terminal framework and modem 1002 proceeds to step S1230 and delivers a message to the application 1001 rejecting data transmission.

The solution 1 described above uses OMA-DM, but is simple and has the following three characteristics.

1) Due to the problem of authentication and OMA-DM server configuration, only a home operator can apply the configuration of the terminal using OMA-DM, so all roaming partners are required for roaming. For each roaming partner, the configuration list of the application name and ID used by the roaming partner should be stored in the terminal, and if the list is updated by the roaming partner, it should be updated.

2) The amount of information broadcast increases according to the number of applications to which barring info equal to the length of the application ID is applied.

Ex) When 32 bit is used as the application ID, the amount of information broadcast according to the number of applications to which the same barring info is to be applied is the application ID size (32 bit) x the number of applications (application_num) + the limit information size (barring-info -size).

3) All operators must use the same application name. The application ID can use a different id, but the application name must be the same.

2) solution  2: application  index( index How to use)

The second feature of the solution 1 is to set an application index value to the terminal instead of an application ID and broadcast a map (for example, a bitmap) marking the corresponding index th bit. This can be solved by reducing the amount of information.

The solution 2 will be described with reference to FIGS. 13 and 14.

FIG. 13 is a diagram illustrating an example of an application map that an operator broadcasts through an eNB. FIG.

FIG. 14 is a flowchart illustrating a process of differentially blocking execution of respective applications installed in a terminal using an application ID according to solution 2. FIG.

First, in step S1410, the operator sets an application index, an application name, and an application ID for the terminal using the OMA-DM. For example, in the case of (application index, application name, application ID), (1, KakaoTalk, 112345) (6, skype, 1235234) may be set.

In operation S1420, the operator broadcasts an SIB including an application map as shown in FIG. 13. In the application map illustrated in FIG. 13, since the first bit and the sixth bit are marked, the terminal determines that the corresponding application is a barring target.

As shown in the flowchart of FIG. 14, when the application index is used, the application index is included in the information set through the OMA-DM in step S1410. When determining the restriction target, the application index does not exist but corresponds to the application index. The procedure described in FIG. 12 is the same except that the bit is determined based on whether the bit is marked in the application map. Accordingly, detailed description of FIG. 14 will be omitted. Solution 2 above can solve feature 2 of solution 1 by reducing the amount of information broadcast.

3) solution  3: VPLMN of Signaling  How to use

Solutions 1 and 2 use OMA-DM, so the home operator had to set up information on the list to be used by all roaming partners. In order to solve this problem, Solution 3 proposes a method of providing a list to be used directly by a roaming partner through signaling through a PCO, as shown in FIG. 15.

FIG. 15 is a flowchart illustrating a process of differentially blocking execution of respective applications installed in a terminal according to Solution 3 of the second embodiment of the present invention.

A description of each step illustrated in FIG. 15 is as follows.

S1505: The UE (terminal) sends a PDN connection request message for generating a default PDN connection while sending an attach request message to the MME to the attach request message. Send it as an ESM message. In this case, an application barring enabled is set in a protocol configuration option (PCO) transmitted through the PDN connection request message and transmitted.

S1510: The MME receiving the access request message sends a create session request message to the SGW / PGW to create a default PDN connection, and inserts the PCO value received from the terminal. .

S1515, S1520: The PGW having application barring enabled is configured to obtain an application list request message including an application index, an application ID, and an application name from the application control server. application list request) to obtain the application list. If the PGW uses an application list set in the PGW, steps S1515 and S1520 are omitted.

S1525: The PGW sets an application list in the PCO in the create session responses and sends it to the MME.

S1530: The MME receiving the PCO including the application list from the PGW, transmits a connection acceptance message including the application list to the terminal. Specifically, the MME copies the application list as it is to the PCO in the activate default EPS bearer context request for transmitting to the terminal and includes it in the access acceptance message. S1535: The terminal that receives the application list from the MME through the PCO stores the application list for later use. The stored application is treated validly in a registered PLMN representing an operator of the currently registered network and in an equivalent PLMN that is equivalently treated with the PLMN. And the rest of the access process proceeds.

S1540: When a communication service is opened for data transmission in an application of a terminal, the terminal requests a terminal framework and a modem (OS / service Framework) while giving one of the parameters to transmit the application name.

-S1545: The terminal framework and modem (OS / service framework) that are requested to execute the application allocate the sender port and find the application index and the application ID in the application list received in step S1530 using the application name received from the application. Map with a port number and store the mapping relationship.

S1550: Sends data using the port assigned by the application.

S1555: Meanwhile, the eNB broadcasts an SIB including application restriction information, application map information, and the like in a licensed or unlicensed form.

S1560: an application mapped to a source address and a port of the IP data using an SIB broadcast from an eNB in a terminal framework and a modem (OS / service framework) receiving IP data Make sure you broadcast to limit the ID or application index. The confirmation method is as shown in FIG. 11 or 12.

S1565: If the barring result is confirmed to be a barring object, the process proceeds to step A to inform the application that the transmission is impossible.

On the other hand, if the verification result is not barring, the process proceeds to step B and transmits a service request message (service request) for switching to the connected mode (connected mode) for data transmission to the network.

The method of notifying the application-barring-enable from the terminal to the network through the PCO shown in FIG. 15 and informing the terminal of the application list in the network can be used in all messages capable of delivering the PCO.

On the other hand, the assumption in FIG. 15 is a case where the MME of the roaming network uses the PGW of the roaming network when setting the application list using the PCO.

If the roaming network's MME cannot use the roaming network's PGW and the home network's PGW needs to be used, the MME checks whether there is an application barring enabled in the PCO received from the terminal, and then determines the value. Is stored in the MME, and the application barring enabled value is cleared when the S1510 message (create session request / update bearer request) is transmitted to SGW / PGW.

Then, after receiving the message of step S1525 (create session response / update bearer response) from the PGW / SGW, when transmitting a connection accept / TAU accept (attach accept / TAU accept) message to the terminal, the application list to be set in the MME Set to PCO, change the contents of PCO, and transmit to the terminal to transmit the roaming network application list.

Solution 3, like Solution 2, can reduce the amount of information that needs to be broadcast by using an application index, while at the same time allowing home operators to not set up roaming partner information.

4) solution  4: How to Use Packet Filters

Solutions 1, 2, and 3 assume that operators use the same application name. To solve the situation where application names cannot be used identically, solution 4 proposes a method using a packet filter.

When the network generates a default bearer during the attachment process of the terminal, the network transmits a default EPS bearer context request along with the attach accept, and at this time, a packet filter Use) to specify the application. That is, an application index or an application ID value is set in a packet filter classified into a sender address, a sender port, a receiver address, and a receiver port corresponding to application traffic, and this is transmitted to the terminal. Deliver it for storage.

An example of the packet filter structure is shown in FIG. 16. As shown in FIG. 16, the packet filter proposed by the present invention includes information such as an application index or an application ID.

Then, when the application attempts to transmit data, the IP header of the data set in the terminal is analyzed to find a matching filter, and then the application index or application ID set in the filter is found. Then check the broadcasted information to see if it is subject to restriction.

Detailed description of the process will be described with reference to FIG. 17.

17 is a flowchart showing the procedure for solution 4 of the second embodiment of the present invention.

S1705: The terminal transmits a packet filter including an indicator that application barring is applicable to the PCO when the attach request message is transmitted, and an application ID or an application index. An indicator (indicator_) indicating that packet packet interpretation is possible is transmitted to the MME.

S1710, S1715: The MME transmits PCO information received from the UE to the SGW / PGW through a session creation request message. Then, the PGW stores the PCO information of the terminal and then proceeds with the attach process.

S1720: After the attach process, the PGW obtains information on the packet filter from the PCRF by using IP CAN session modification / creation. At this time, the PGW requests the PCRF for an application list and the PCRF sends the PGW in a response message to the PGW. When the PGW uses an application list stored in the PGW, step S1720 may be omitted.

S1725: The PGW configures the packet filter by adding an application index or an application ID to the field after the packet filter content in the packet filter information having the format shown in FIG. The PGW transmits the packet filter to the MME through a bearer create request message or a bearer update request message that can install a packet filter in the terminal.

S1730: The MME transmits the information received from the PGW to the UE through a bearer modify request message or an activate dedicate bearer request.

S1735: The terminal stores the packet filter including the application index or application ID received from the MME.

S1740, S1745: The terminal transmits data after requesting to open a communication service.

S1750: The terminal framework of the terminal and the modem (service framework / OS) checks the packet filter matched using the information of the IP packet addresses and ports transmitted by the application, the application ID or the application stored in the packet filter Find the index. S1755: Meanwhile, the terminal acquires application related restriction information broadcasted by the eNB to the SIB.

S1760: The terminal checks whether the application index or the application ID corresponding to the transmitted data is barring through the process of FIG. 11 or 12. If the result of the test is limited, the A stage notifies the application that it cannot communicate. On the other hand, if not limited, in step B, a connection request message for switching to connected mode (connected mode) is transmitted to the network.

<Third Example >

Hereinafter, a description will be given of the third embodiment, which is a process of informing the terminal when the operator applies the operator determined barring.

Currently, a call barring service is defined in the IMS network in which a user arbitrarily barries a call. Barring of all incoming call, Barring of all outgoing call, Barring of outgoing international call, Barring of incoming calls when roaming, etc. With this, it only applies if the user requests it. However, a case may arise where an operator wants to apply the service arbitrarily to the user in order to protect their revenue. For example, operators need to restrict outgoing or incoming calls for users who do not pay telecommunications fees.

However, according to the related art, a method for notifying a user that call barring is applied due to a service provider decision is not defined, and a method for clearing a session attempted by the terminal is not defined.

18 is a diagram briefly showing an EPS network and an IMS network on which an embodiment of the present invention is based. Hereinafter, only the entities related to the present invention among the entities shown in FIG. 18 will be described briefly.

Referring to FIG. 18, a user equipment (UE) represents a terminal 1810, and an eNB (shown as EUTRAN in the figure) 1820 is an entity that controls radio resources and is connected to the terminal 1810 through a wireless channel. do.

The MME manages an idle mode (idle) terminal 1810 as a mobility management entity (1830) and performs a function related to roaming and authentication of the terminal. In addition, the MME 1830 processes the bearer signal generated by the terminal 1810.

The home subscriber server (HSS) 1840 stores subscription information for each terminal, and when the terminal 1810 accesses a network, the MSS 1830 delivers information related to the terminal 1810 to the MME 1830. It is used to control the terminal 1810. In addition, it stores a service profile to be provided to each terminal 1810 for services provided by the IMS network.

A session control function (CSCF) of an IMS network is composed of a P-CSCF 1850, an I-CSCF 1860, and an S-CSCF 1870. The P-CSCF 1850 is a Proxy CSCF, and the S-CSCF 1870 is a serving CSCF that is in charge of IMS session control and service control.

The TAS 1880 is responsible for providing supplementary services of IMS calls to a telephony application server.

FIG. 19 is a schematic diagram of Barring of all outgoing call operations currently defined in an IMS network based on the network architecture.

First, the user registers a supplementary service in step S1900 to prevent the user from using an outgoing call for the terminal 1810. In order to register the additional service, the terminal 1810 may access an arbitrary server provided by an operator or an operator and register a service for prohibiting the call origination. Then, the information on the additional service registered by the terminal 1810 is shared with the TAS 1880, and the TAS 1880 may identify that the outgoing call to the corresponding terminal 1810 is prohibited.

In step S1905, the terminal 1810 transmits a registration message (REGISTER) to the PCSCF in order to perform registration in the IMS network. Then, in step S1940, the PCSCF delivers the registration message (REGISTER) to the SCSCF.

Then, the SCSCF 1870 downloads a service profile of the terminal 1810 from the HSS 1840 in step S1915. The service profile includes an initial filter criterion (iFC). The SCSCF 1870 then sends a 200OK message to the PCSCF 1850 in step S1920. The PCSCF 1850 then transmits the 200OK message to the terminal 1810 in response to the registration request.

By performing the above procedure, the terminal 1810 completes the registration procedure in the IMS network.

Thereafter, the terminal 1810 transmits an INVITE message to the PCSCF 1850 in step S1930 to initiate the IMS session. Then, in step S1935, the PCSCF 1850 transmits the INVITE message to the SCSCF 1870.

Then, in step S1940, SCSCF 1870 checks the iFC for the terminal 1810. According to the iFC, the invite message transmitted from the terminal 1810 is set to be delivered to the TAS 1880. Accordingly, the SCSCF 1870 forwards the invite message to the TAS 1880 according to iFC in step S1945.

In step S1950, the TAS 1880 confirms that the outgoing call of the terminal 1810 is prohibited and rejects the corresponding session request. Accordingly, the TAS 1880 transmits a session rejection message 603 Declined to the terminal in step S19550.

20 is a flowchart illustrating a process in which a terminal 1810 registers in an IMS network and receives ODB according to an embodiment of the present invention.

Briefly summarizing the embodiment of the present invention described below, the terminal 1810 to which the ODB is applied receives a response message including an indicator indicating a session rejection from the TAS 1880. In addition, when the response message includes an action to be taken by the terminal afterwards, the terminal 1810 performs the instructed operation. Hereinafter, an ODB application process will be described in detail with reference to FIG. 20.

First, the operator or operator applies an operator determined barring (ODB) to the terminal 1810 in step S2005, and registers the relevant context for the terminal.

Thereafter, the terminal 1810 transmits a registration message (REGISTER) to the PCSCF 1850 to perform a registration procedure on the IMS network in step S2010. Then, the PCSCF 1850 forwards the registration message (REGISTER) to the SCSCF 1870 in step S2015.

Thereafter, the SCSCF 1870 downloads the service profile for the terminal 1810 from the HSS 1840. The service profile includes an initial filter criterion (iFC). According to an embodiment of the present invention, the iFC includes a context for ODB application.

The SCSCF 1870 transmits a 200OK message to the PCSCF 1850 in operation S2025, and the PCSCF 1850 transmits the received 200OK message to the terminal 1810.

Thereafter, the terminal 1810 transmits an INVITE message to the PCSCF 1850 to initiate an IMS session in step S2035. Then, the PCSCF 1850 forwards the INVITE message to the SCSCF 1870 in step S2040.

Then, in step S2045, the SCSCF 1870 checks the iFC for the terminal 1810. According to the iFC, the invite message transmitted from the terminal 1810 is set to be delivered to the TAS 1880. Accordingly, the SCSCF 1870 transmits an INVITE message to the TAS 1880 according to iFC in step S2050.

The TAS 1880 then processes the session according to the information in the ODB context. The TAS 1880 may send a response to the terminal 1810 in the form of 3xx, 4xx, 5xx, 6xx as shown in step S2060 or below, or may forward the session to another destination. In the embodiment described in FIG. 20, an embodiment of transmitting a response to the terminal 1810 will be described.

The TAS 1880 transmits a response message for the INVITE of the terminal 1810 to the SCSCF 1870. In this case, the response message includes an indicator indicating that the session request of the terminal 1810 has been rejected due to the ODB.

The embodiment of the present invention proposes an 'operator determined barring' indicator as an example. The indicator may be included as a header in a SIP message or may be included in the form of a feature tag. As another example, it may be included in an XML form included in a SIP response message.

Then, the SCSCF 1870 transfers the response message to the PCSCF 2065, and the PCSCF 2065 transfers the received response message to the terminal 1810.

Then, the terminal 1810 receives the response message and checks the 'operator determined barring' indicator included in the response message. Then, the terminal 1810 may confirm that its session request is rejected due to the operator's restriction setting.

In addition, the terminal 1810 checks whether the required message (Required_action) is included in the response message. The information on the required operation may be information that may be selectively included in the response message. When included, the terminal 1810 terminates the session when the required action (Required_action) includes a request to close the requested session (close). On the other hand, if the required action (required_action) is not included, the terminal 1810 may perform a default action (default action). The default action is preconfigured in the UE or can be updated by the operator through OMA-DM.

21 is a diagram illustrating an example of a response message proposed in an embodiment of the present invention.

As shown in FIG. 21, the response message may include an indicator (operator determined barring) indicating that the session request has been rejected and information about a required action (Required_action).

FIG. 22 is a diagram illustrating an example of a UE context delivered between an HSS and a TAS according to an embodiment of the present invention. The terminal context is applied to step 2005 of FIG. 20.

Data reference is any number.

XML tag is an xml tag used in data, and in the embodiment of the present invention, IMS_ODB is proposed.

An access key is an IMS public user identity or an MSISDN that is a reference identity to access data, and can be applied to Sh-Pull, Sh-Update, Sh-Subs-Notif messages. Can be.

FIG. 23 is a diagram illustrating an example of an XML schema used for OBD implementation according to an embodiment of the present invention. FIG.

24 and 25 are flowcharts illustrating a method for notifying the MME of when congestion occurs in a specific channel and when congestion is resolved according to an embodiment of the present invention.

Conceptually, the ENB may inform using an arbitrary control message (eg, S1-AP message) that sends its congestion to the MME, as shown in step S2410 or step S2510. That is, the congestion information of the ENB may be inserted and transmitted in a piggybacked form in a message (for example, an initial context setup response) transmitted to the MME for another purpose. Congestion information piggybacked on any S1-AP message includes the presence of congestion, the object of congestion (cell, PLMN, channel, etc.), congestion duration, degree of congestion, or the level of load desired to be reduced due to congestion. can do.

In this embodiment, a case where the paging channel is congested will be described with an example. In step S2410, the ENB of FIG. 24 inserts overload status information (eg, Overload Start IE) into an arbitrary S1-AP message sent to the MME when the paging channel is congested. The overload status information may simply include a flag indicating whether an overload situation has begun, and may be the subject of congestion, i.e., the PLMN ID, cell ID, or channel of congestion (in this example, paging). Channel), and the level of load desired to be reduced due to congestion or congestion, and the time the congestion will last.

The MME, which receives the information that the overload has started from the eNB, considers it to be congested for a specific PLMN, a specific cell, or a specific channel according to the target information included in the state information from a subsequent procedure, and the congestion duration in the overload state information. If this is included, the timer is considered to be congested until the congestion time expires. In fact, even if the S1-AP message received from the ENB is for a specific UE, the overload status information included in the S1-AP message may not be for a specific terminal.

As shown in FIG. 25, the MME receives overload state information (eg, Overload Stop IE) from the eNB in step S2510 that the target (specific PLMN, specific cell, and specific channel) is no longer congested for the target. Can be received. Then, the MME considers that the congestion state for the target (the cell, the channel of the PLMN) is resolved. Alternatively, when the overload status information includes the congestion duration, the MME considers congestion to be over when the timer for the congestion duration expires.

Alternatively, even if the congestion duration is not included in the overload status information, the MME may operate the timer according to the internally set time, and may consider that congestion continues until the timer expires.

Meanwhile, as shown in FIGS. 24 and 25, the ENB may use different IEs for starting and ending to inform the MME of the overload status. However, the IEB may use one IE, for example, an overload status information element (Overload Status IE). May be informed by inserting into any control message (e.g., S1-AP message).

In this case, the ENB may indicate whether there is an overload using an overload flag of the overload state information, or otherwise reduce the level of load desired to be reduced due to congestion or information about the overload state information. You can also use it. In this case, the congestion level is a value indicating that there is no congestion, and the load level desired to be reduced due to congestion may be set to 0. Alternatively, the ENB may inform that the congestion state has ended by setting the congestion duration of the overload state information to zero.

Each node of the wireless communication network illustrated in the above-described drawings and the detailed description may be configured as a transceiver for transmitting and receiving signals with other nodes and a controller for controlling the functions of the nodes. Since detailed functions of the controller of each node have been described in each embodiment, detailed description thereof will be omitted.

The embodiments of the present invention disclosed in the present specification and drawings are merely illustrative examples of the present invention and are not intended to limit the scope of the present invention in order to facilitate understanding of the present invention. It will be apparent to those skilled in the art that other modifications based on the technical idea of the present invention are possible in addition to the embodiments disclosed herein.

Claims (10)

In the service control method of a base station in a wireless communication system,
Receiving a paging message from a Mobility Management Entity (MME) when a downlink packet for any terminal is generated;
Confirming a setting state of a core network domain included in the paging message;
And a paging processing step of processing the paging message first when the core network domain is set to a packet-based voice call service. 2. The method according to claim 1,
If the core network domain of the paging message is set to packet switched voice (PS_Voice), detecting that a packet-based voice call service has occurred. 2. The method according to claim 1,
If the core network domain of the paging message is set to packet switched and includes a voice indicator, detecting that a packet-based voice call service has occurred. The method of claim 1, wherein the packet-based voice call service,
Service control method comprising a Voice over LTE (VoLTE) or Voice over IMS (VoIMS). The method of claim 1, wherein the paging processing step,
Paging for the packet-based voice call is prioritized over paging for a packet switched (PS) service. A base station for controlling a service in a wireless communication system,
Transmitting and receiving unit for transmitting and receiving signals with the nodes of the wireless communication system; And
Receive a paging message from a Mobility Management Entity (MME) when the downlink packet for any terminal occurs, check the configuration state of the core network domain included in the paging message, the core network domain is packet-based And a control unit which controls to process the paging message first when the voice call service is set. 7. The apparatus of claim 6,
And detecting that a packet-based voice call service has occurred when the core network domain of the paging message is set to packet switched voice (PS_Voice). 7. The apparatus of claim 6,
And detecting that a packet-based voice call service has occurred when the core network domain of the paging message is set to packet switched and includes a voice indicator. The method of claim 6, wherein the packet-based voice call service,
A base station comprising VoLTE (Voice over LTE) or Voice over IMS (VoIMS). The method of claim 6, wherein the base station,
Paging for the packet-based voice call is prioritized over paging for a packet switched (PS) service.

Images