CN104519538A

CN104519538A - User equipment, and method, device and system for receiving request messages

Info

Publication number: CN104519538A
Application number: CN201310459284.6A
Authority: CN
Inventors: 卢飞; 谢宝国; 梁爽
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2013-09-27
Filing date: 2013-09-27
Publication date: 2015-04-15
Anticipated expiration: 2033-09-27
Also published as: CN104519538B; WO2015043244A1

Abstract

The invention discloses user equipment, and a method, a device and a system for receiving request messages. The method for receiving the request messages includes receiving the request messages with business types and/or circuit-domain rollback response. Each request message is transmitted by the user equipment and can be one of a tracking area updating request message, a routing area updating request message and an expanding business request message. The user equipment, the method, the device and the system have the advantages that the problem of high 2G/3G (second generation/third generation) network reselection access signaling overhead under the condition that existing UE (user equipment) is constrained can be solved by the aid of the user equipment, the method, the device and the system, the signaling overhead can be lowered, and the 2G/3G network access efficiency can be improved.

Description

User equipment, request message receiving method, device and system

Technical Field

The present invention relates to the field of communications, and in particular, to a user equipment, a request message receiving method, an apparatus, and a system thereof.

Background

The standardization work group of the third Generation Partnership Project (3 rd Generation Partnership Project, 3GPP for short) is currently working on the evolution of Packet switched Core Network (PS Core for short) and Universal Mobile telecommunications System Radio Access Network (UTRAN for short). The research topic is called System Architecture Evolution (SAE for short), and aims to enable an Evolved Packet Network (Evolved Packet Core, EPC for short) to provide a higher transmission rate, a shorter transmission delay, optimize packets, and support mobility management between Evolved UTRAN (Evolved UTRAN, E-UTRAN for short), UTRAN, Wireless Local Area Network (WLAN for short) and other non-3 GPP access networks.

Fig. 1 is a schematic structural diagram of an SAE architecture according to the related art, and as shown in fig. 1, a Network element included in an Evolved Radio Access Network (E-RAN) is an Evolved node B (eNodeB) for providing a Radio resource for a user to Access; a Packet Data Network (PDN) is a Network that provides services to users; the EPC provides lower transmission delay and allows more radio access system access, and its network elements include: a Mobility Management Entity (MME), a Serving Gateway (SGW), a Packet data network Gateway (PDN Gateway, PGW), a Policy and Charging Rules Function Entity (Policy and Charging Rules Function, PCRF), and a Home Subscriber Server (HSS), where the MME is a Mobility Management unit of the SAE System, and in a Universal Mobile Telecommunications System (UMTS), the Mobility Management unit is a Serving General Packet Radio Service (GPRS) support Node (SGSN).

In order to support Circuit domain services, 3GPP introduces a Circuit domain Fallback (CSFB) mechanism in a network, in the CSFB mechanism, an MME is connected to a Mobile Switching Center (MSC) through an SGs interface (interface between the MME and the Mobile switching Center), and the MSC and a Visitor Location Register (VLR) are integrated in an actual network. Fig. 2 is a schematic diagram illustrating a procedure for updating a Tracking area and activating an SGs connection according to a related art, and as shown in fig. 2, a User Equipment (UE) registered under a coverage area of UTRAN moves to an coverage area of E-UTRAN and activates an SGs during a Tracking Area Update (TAU). For a Routing Area Update (RAU) procedure triggered when a UE registered under the coverage Area of E-UTRAN moves to the coverage Area of UTRAN, the procedure is similar to the procedure shown in fig. 2 and will not be separately described here. As shown in fig. 2, the method comprises the following steps:

step S201, UE moves to an E-UTRAN coverage area under MME, sends a tracking area update request message to MME, requests to register in a new area, the update request message carries a Packet-Temporary Mobile Subscriber Identity (P-TMSI for short) allocated by SGSN for UE;

step S202, the new MME finds the old SGSN according to the P-TMSI identification, and sends a context request signaling to the old SGSN to acquire the context of the UE;

step S203, the old SGSN sends the mobility management and bearer (bearer) information of the user to the new MME, namely, context response is carried out;

step S204, the new MME confirms the context after receiving the context response;

step S205, the new MME initiates a request message for updating the bearer to the SGW, the request message for updating the bearer carries a tunnel identifier of a source GPRS Tunneling Protocol-Control Plane (GTP-C for short) and a tunnel identifier of a destination GTP-C, and the SGW updates the binding relationship of the bearer;

step S206, the SGW sends an update bearer request to the PGW, and sends parameters such as address information of the SGW, tunnel identifier information, access technology type, and the like to the PGW.

Step S207, the PGW updates the context of the PGW and returns an update bearer response message to the SGW, wherein the content of the response message comprises the address, the tunnel identifier and the like of the PGW;

step S208, the SGW returns an update bearer response to the new MME, and brings a target GTP-C tunnel identifier, an address of the SGW, an address of a PGW, tunnel information and the like specified by the SGW to the MME;

step S209, the new MME notifies the HSS of the change of the registration position through a position updating message;

step S210, HSS maintains single registration principle for UE, sends position cancel signaling to old SGSN, only maintains registration of new MME;

step S211, the old SGSN returns a location cancellation response to the HSS;

step S212, the HSS confirms the position update of the new MME;

step S213, MME sends a position update request message to MSC to request the establishment of SGs connection, the position update request message carries parameters such as International Mobile Subscriber Identity (IMSI), Location Area Identity (LAI), MME name, position update type and the like;

step S214, MSC checks user, and sends location updating request message to HSS after checking;

step S215, HSS returns location update confirmation message to MSC;

step S216, the MSC returns a location update acceptance message to the MME, wherein the location update acceptance message carries a Temporary Mobile Subscriber Identity (TMSI);

step S217, if the new MME confirms that the UE is effective in the current tracking area, a tracking area update acceptance message is sent to the UE, and LAI and TMSI are required to be carried in the TAU acceptance message;

in step S218, if the new MME allocates a new globally unique Temporary identifier (globally unique Temporary Identity, GUTI for short) to the UE through the TAU procedure, the UE returns a tracking area update completion message to confirm to the MME.

FIG. 3 is a flow of a UE in an IDLE (ECM _ IDLE) state being restricted (back off) by an MME according to the related art

The schematic diagram is that the idle-state UE satisfies the triggering condition of the TAU request specified by the protocol to initiate the TAU request. As shown in fig. 3, the process includes the following steps:

step S301, the idle UE satisfies the triggering condition of TAU of protocol 3GPP TS24.301 to initiate TAU request, and requests to register in a new area, and the TAU message carries the originally distributed GUTI value;

step S302, the MME rejects the TAU request message sent by the UE because the resource is limited, and returns a TAU reject message to the UE, wherein the message carries a limited timer (back off timer);

step S303, after the UE receives the TAU request rejection message sent by the MME, the UE changes the state TO the limited state of EMM, REGISTERED, ATTEMPTING-TO-UPDATE, and starts a limited timer, and during the operation of the limited timer, the UE cannot actively send the non-emergency service message of a Packet Switch (PS) domain TO the network side;

step S304, after VLR receives circuit domain terminal call service, VLR sends SGs paging message to MME;

step S305, MME sends paging message to UE through eNodeB, the paging message carries SAE-Temporary Mobile Subscriber Identity (SAE-temporal Mobile Subscriber Identity, abbreviated as S-TMSI) allocated by network for user and circuit domain identification for marking paging service.

Step S306, because the UE is in EMM.REGISTERED.ATTEMPING-TO-UPDATE state, after receiving the paging message sent by the network side, the UE needs TO send TAU request as the paging response message;

step S307, the MME returns a TAU acceptance message to the UE;

in step S308, the UE needs to send an extended service request message to the MME to indicate that the UE has accepted the circuit domain fallback request and will attempt to connect to a second generation or third generation (2G/3G) network.

It can be seen that, in the related art, when the UE is limited, after receiving the paging response, the UE needs to send a TAU request message to the network to re-register to the network, and then can send an extended service request message to the network to indicate whether the circuit domain fallback request can be accepted; after this process, the UE will reselect the 2G/3G network for access. It can be seen from this process that the time for the UE to reselect the 2G/3G network access is relatively long, which is likely to result in relatively long call waiting time and relatively poor user experience; on the other hand, the UE sends more signaling to the network side, which is also likely to cause network congestion.

Aiming at the problem that the cost for reselecting a 2G/3G network access signaling is high under the condition that UE is limited in the related technology, an effective solution is not provided at present.

Disclosure of Invention

The invention provides user equipment, a request message receiving method, a device and a system, which are used for at least solving the problem of high overhead of reselecting a 2G/3G network access signaling under the condition that UE is limited.

According to an aspect of the present invention, there is provided a request message receiving method including: receiving a request message which is sent by user equipment and carries a service type and/or a circuit domain backspace response, wherein the request message comprises one of the following: a tracking area update request message, a routing area update request message, and an extended service request message.

Preferably, after receiving the request message, the method further comprises: sending an SGs service request message or an SGs paging rejection message to a visitor location register according to the request message, wherein the SGs service request message or the SGs paging rejection message is used for indicating the operation of the circuit domain fallback service executed by the user equipment; or sending a predetermined reason value for rejecting the request message to the user equipment according to the request message, wherein the user equipment determines to access a second generation or third generation network according to the predetermined reason value.

Preferably, the user equipment is in a limited state where it cannot actively send non-emergency service messages of the packet switched domain to the network side.

Preferably, the service types include: and finally calling the circuit domain backspace service or the initial calling circuit domain backspace emergency service.

Preferably, after receiving the request message carrying the circuit domain fallback response sent by the user equipment, the method further includes: and determining that the user equipment accepts the circuit domain backspacing service or rejects the circuit domain backspacing service according to the circuit domain backspacing response.

Preferably, in the case that the request message is an extended service request, the extended service request is sent by the user equipment in a limited state according to the trigger of the circuit domain fallback service.

Preferably, the SGs service request message is used to indicate the ue to receive the terminating circuit domain fallback service when the service type carried in the request message is the terminating circuit domain fallback service and/or the circuit domain fallback response indicates that the ue receives the terminating circuit domain fallback.

Preferably, the SGs service request message is used to instruct the user equipment to actively initiate an origination circuit domain fallback service, when the service type carried in the request message is an origination circuit domain fallback emergency service.

Preferably, the SGs paging rejection message is used to indicate the ue to reject the cs fallback service when the service type carried in the request message is the cs fallback service and/or the cs fallback response indicates the ue to reject the cs fallback.

According to another aspect of the present invention, there is also provided a request message receiving apparatus including: a first receiving module, configured to receive a request message carrying a service type and/or a circuit domain fallback response sent by a user equipment, where the request message includes one of: a tracking area update request message, a routing area update request message, and an extended service request message.

Preferably, the apparatus further comprises: a first sending module, configured to send an SGs service request message or an SGs paging reject message to a visitor location register according to the request message, where the SGs service request message or the SGs paging reject message is used to indicate an operation of a circuit domain fallback service executed by the user equipment; or, the first sending module is configured to send, to the user equipment according to the request message, a predetermined cause value for rejecting the request message, where the user equipment determines to access a second-generation or third-generation network according to the predetermined cause value.

Preferably, the apparatus is located in a mobility management unit, wherein the mobility management unit comprises: a mobility management entity and/or a general packet radio service support node.

Preferably, the apparatus further comprises: and the first determining module is used for determining that the user equipment accepts the circuit domain backspacing service or rejects the circuit domain backspacing service according to the circuit domain backspacing response.

Preferably, the first transmitting module further comprises: a first determining unit, configured to determine, according to the request message, that the user equipment accepts a terminating circuit domain fallback service when the service type carried in the request message is the terminating circuit domain fallback service and/or the circuit domain fallback response indicates that the user equipment accepts the terminating circuit domain fallback; a first sending unit, configured to send the SGs service request message to the visitor location register, where the SGs service request message is used to indicate that the user equipment receives a call circuit domain fallback service.

Preferably, the first transmitting module further comprises: a second determining unit, configured to determine, according to the request message, that the user equipment actively initiates an origination circuit domain fallback service when the service type carried in the request message is an origination circuit domain fallback emergency service; a second sending unit, configured to send the SGs service request message to the visitor location register, where the SGs service request message is used to instruct the user equipment to actively initiate an origination circuit domain fallback service.

Preferably, the first transmitting module further comprises: a third determining unit, configured to determine, according to the request message, that the ue rejects the cs fallback service when the service type carried in the request message is the cs fallback service and/or the cs fallback response indicates that the ue rejects the cs fallback; a third sending unit, configured to send the SGs paging rejection message to the visitor location register, where the SGs paging rejection message is used to instruct the ue to reject the terminating circuit domain fallback service.

According to another aspect of the present invention, there is also provided a user equipment, including: a second sending module, configured to send a request message carrying a service type and/or a circuit domain fallback response, where the request message includes one of: a tracking area update request message, a routing area update request message, and an extended service request message.

Preferably, the user equipment further comprises: a second determining module, configured to determine to access a second generation or third generation network according to a predetermined cause value for rejecting the request message from a mobility management unit, where the mobility management unit sends the predetermined cause value to the user equipment according to the request message.

Preferably, the second sending module is further configured to: and sending the extended service request as the request message to the mobile management unit in a limited state according to the trigger of the circuit domain backspacing service.

According to another aspect of the present invention, there is also provided a request message transmission system including: a mobility management unit comprising the request message receiving device, and the user equipment.

By the invention, the request message which is sent by the user equipment and carries the service type and/or the circuit domain backspace response is received, wherein the request message comprises one of the following messages: the mode of the tracking area updating request message, the routing area updating request message and the extended service request message solves the problem of high signaling overhead when the UE is limited to reselect the 2G/3G network, reduces the signaling overhead and improves the efficiency of accessing the 2G/3G network.

Drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:

fig. 1 is a structural diagram of an architecture of SAE according to the related art;

fig. 2 is a flowchart of a tracking area update and activation of SGs connection according to the related art;

fig. 3 is a flowchart illustrating an idle-state UE being restricted by an MME according to the related art;

fig. 4 is a first preferred flowchart of a request message receiving method according to an embodiment of the present invention;

fig. 5 is a schematic diagram of a preferred flow chart of a request message receiving method according to an embodiment of the present invention;

fig. 6 is a first schematic diagram of a preferred structure of a request message receiving device according to an embodiment of the present invention;

fig. 7 is a schematic diagram of a preferred structure of a request message receiving device according to an embodiment of the present invention;

fig. 8 is a schematic diagram of a preferred structure of a request message receiving apparatus according to an embodiment of the present invention;

fig. 9 is a diagram illustrating a preferred structure of a request message receiving apparatus according to an embodiment of the present invention;

fig. 10 is a schematic diagram of a preferred structure of a request message receiving device according to an embodiment of the present invention;

fig. 11 is a schematic diagram of a preferred structure of a user equipment according to an embodiment of the present invention;

fig. 12 is a system configuration diagram of a request message transmission system according to an embodiment of the present invention;

fig. 13 is a flowchart illustrating a method for differentiating traffic by a mobility management procedure according to a preferred embodiment of the present invention;

FIG. 14 is a flowchart illustrating a method for implementing step S1302 according to an embodiment of the present invention;

fig. 15 is a flowchart illustrating an implementation method of step S1303 according to a preferred embodiment of the present invention;

FIG. 16 is a flowchart illustrating another implementation of step S1302 according to the preferred embodiment of the present invention;

fig. 17 is a schematic flowchart of another implementation method of step S1303 according to the embodiment of the present invention;

FIG. 18 is a schematic workflow diagram of a mobility management procedure differentiated services system according to a preferred embodiment of the present invention;

fig. 19 is a flow diagram of a terminating circuit domain fallback service according to a preferred embodiment of the present invention;

fig. 20 is a flow chart of the originating circuit domain fallback service according to the preferred embodiment of the present invention.

Detailed Description

It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present invention will be described in detail below with reference to the embodiments with reference to the attached drawings.

The steps illustrated in the flow charts of the drawings may be performed in a computer system such as a set of computer-executable instructions and, although a logical order is illustrated in the flow charts, in some cases, the steps illustrated or described may be performed in an order different than here.

The embodiment provides a request message receiving method, which comprises the following steps: receiving a request message carrying a service type and/or a circuit domain fallback response sent by user equipment, wherein the request message comprises one of the following: a tracking area update request message, a routing area update request message, and an extended service request message.

According to the technical scheme, the service type and/or the circuit domain fallback response are/is carried in the tracking area update request message, the routing area update request message and the extended service request message and sent, and compared with the technical scheme that the related message of the circuit domain fallback can be reported to the network side only after the user terminal needs to be re-registered to the network in the related technology, the user terminal in the system applying the scheme can report the related information of the circuit and the fallback service to the network side without the non-emergency service message of the PS domain, so that the process of reselecting the 2G/3G network access can be completed by using as few signaling as possible under the condition that the user terminal cannot actively send the non-emergency service message of the PS domain to the network side, and the problem of high signaling overhead of reselecting the 2G/3G network access under the condition that the UE is limited is solved, signaling overhead is reduced, access time is shortened, the efficiency of accessing a 2G/3G network is improved, and user experience is improved.

Fig. 4 is a first preferred flowchart of a request message receiving method according to an embodiment of the present invention, as shown in fig. 4, the flowchart includes the following steps:

step S402, receiving a request message carrying a service type and/or a circuit domain fallback response sent by a user equipment, wherein the request message includes one of the following: a tracking area updating request message, a routing area updating request message and an extended service request message;

step S404, according to the request message, sending an SGs service request message or an SGs paging rejection message to the visitor location register, wherein the SGs service request message or the SGs paging rejection message is used for indicating the operation of the circuit domain fallback service executed by the user equipment.

Through the steps, by receiving the service type carried in the request message by the user terminal and/or the request message of the circuit domain fallback response, the mobile management unit on the network side can acquire the operation of the circuit domain fallback service executed by the user terminal through the request message, and after sending the SGs service request message for indicating the operation of the circuit domain fallback service executed by the user equipment to the visitor location register, the network side can support the user equipment to reselect the access of the 2G/3G network, thereby completing the circuit domain fallback; if the user equipment rejects the call circuit domain fallback service, the mobile management unit sends an SGs paging rejection message to the visitor location register, and the visitor location register can trigger the busy processing of the current user or release the current call. Therefore, by adopting the steps, the technical problems of longer time for reselecting the 2G/3G network for access and higher signaling cost caused by the fact that the limited user equipment in the related technology cannot actively send the non-emergency service of the packet switching domain to the network side are solved, the efficiency of accessing the 2G/3G network is improved, and the user experience is improved; meanwhile, the signaling sent to the network side is reduced by adopting the steps, so that the network congestion is avoided.

Preferably, the mobile management unit includes: a mobility management entity and/or a general packet radio service support node.

Preferably, the user equipment is in a limited state, such as an emm.registered.attemptingto-UPDATE state, in which the user equipment cannot actively send non-emergency service messages of the packet switched domain TO the network side, and at this time, the user equipment cannot actively send non-emergency service messages of the PS domain TO the network side.

Preferably, the circuit domain fallback response is used to instruct the user equipment to accept/reject the circuit domain fallback service. After receiving the request message carrying the circuit domain fallback response sent by the user equipment, the method further includes: and determining that the user equipment accepts the circuit domain backspacing service or rejects the circuit domain backspacing service according to the circuit domain backspacing response. For example, after the user equipment rejects the CSFB service, if the user equipment does not notify the MSC of a response rejecting the circuit domain fallback, the MSC will continue to resend the paging request message, thereby causing signaling redundancy or congestion. It can be seen that in this way congestion of the network can be further avoided.

Preferably, the traffic types include: and finally calling the circuit domain backspace service or the initial calling circuit domain backspace emergency service.

Preferably, the SGs service request message is used to indicate the ue to receive the terminating circuit domain fallback service when the service type carried in the request message is the terminating circuit domain fallback service and/or the circuit domain fallback response indicates the ue to receive the terminating circuit domain fallback.

Preferably, the SGs service request message is used to instruct the user equipment to actively initiate an origination circuit domain fallback emergency service, when the service type carried in the request message is the origination circuit domain fallback emergency service.

Preferably, the SGs paging rejection message is used to instruct the ue to reject the cs fallback service when the service type carried in the request message is the cs fallback service and/or the cs fallback response indicates the ue to reject the cs fallback.

Fig. 5 is a schematic diagram of a preferred flow chart of a request message receiving method according to an embodiment of the present invention, as shown in fig. 5, the flow chart includes the following steps:

step S502, receiving a request message carrying a service type and/or a circuit domain fallback response sent by a user equipment, wherein the request message includes one of the following: a tracking area updating request message, a routing area updating request message and an extended service request message;

step S504, according to the request message, sending a predetermined reason value for rejecting the request message to the user equipment, wherein the user equipment determines to access the second generation or third generation network according to the predetermined reason value.

Through the steps, the mobile management unit can acquire the operation of the circuit domain fallback service executed by the user terminal through the request message by receiving the request message of the user terminal carrying the service type and/or the circuit domain fallback response in the request message, after the predetermined reason value for rejecting the request message is sent to the user equipment, the network side can support the user equipment to reselect the access of the 2G/3G network, and at the moment, the user equipment determines to access the 2G/3G network according to the predetermined reason value responded by the mobile management unit, so that the circuit domain fallback is completed. Therefore, by adopting the steps, the technical problem that the time for reselecting the 2G/3G network for access is long due to the fact that the limited user equipment in the related technology cannot actively send the non-emergency service of the packet switching domain to the network side is solved, the efficiency of accessing the 2G/3G network is improved, and the user experience is improved; meanwhile, the signaling sent to the network side is reduced by adopting the steps, so that the network congestion is avoided.

Preferably, the user equipment is in a limited state in which it cannot actively send non-emergency service messages of the packet switched domain to the network side.

Preferably, the circuit domain fallback response is used to indicate that the user equipment accepts circuit domain fallback.

Preferably, in the case that the request message is an extended service request, before the mobility management unit receives the extended service request sent by the user equipment, the method further includes: and the user equipment sends an extended service request to the mobile management unit according to the triggering of the circuit domain backspacing service in a limited state.

The present embodiment also provides a request message receiving apparatus, which may be applied to a mobile management unit, where the apparatus is configured to implement the request message receiving method, and a specific implementation process of the apparatus described in the apparatus embodiment is described in detail in the method embodiment, and is not described herein again.

The request message receiving apparatus includes: a first receiving module, configured to receive a request message carrying a service type and/or a circuit domain fallback response sent by a user equipment, where the request message includes one of: a tracking area update request message, a routing area update request message, and an extended service request message.

Fig. 6 is a schematic diagram of a preferred structure of a request message receiving apparatus according to an embodiment of the present invention, as shown in fig. 6, the apparatus includes: a first receiving module 62 and a first sending module 64, where the first receiving module 62 is configured to receive a request message carrying a service type and/or a circuit domain fallback response, where the request message includes one of: a tracking area updating request message, a routing area updating request message and an extended service request message; the first sending module 64 is coupled to the first receiving module 62, and configured to send an SGs service request message or an SGs paging reject message to the visitor location register according to the request message, where the SGs service request message or the SGs paging reject message is used to indicate an operation of the circuit domain fallback service executed by the user equipment.

The modules and units related in the embodiments of the present invention may be implemented by software, or may be implemented by hardware. The modules and units described in this embodiment may also be disposed in the processor, and for example, may be described as: a processor includes a first receiving module 62 and a first transmitting module 64. The names of these modules do not form a limitation on the module itself in some cases, for example, the first receiving module may also be described as a "module for receiving a request message carrying a service type and/or a circuit domain fallback response sent by the user equipment".

Preferably, the first sending module 64 is further configured to send, to the user equipment, a predetermined cause value for rejecting the request message according to the request message, wherein the user equipment determines to access the second generation or third generation network according to the predetermined cause value.

Preferably, the circuit domain fallback response is used to instruct the user equipment to accept/reject the circuit domain fallback service. Fig. 7 is a schematic diagram of a preferred structure of a request message receiving apparatus according to an embodiment of the present invention, as shown in fig. 7, preferably, the apparatus further includes: the first determining module 72 is coupled to the first receiving module 62, and configured to determine, according to the circuit domain fallback response, that the user equipment accepts the circuit domain fallback service or rejects the circuit domain fallback service.

Preferably, the SGs service request message is used to indicate the user equipment to receive the terminating circuit domain fallback service, when the service type carried in the request message is the terminating circuit domain fallback service. Fig. 8 is a schematic diagram of a preferred structure of a request message receiving apparatus according to an embodiment of the present invention, as shown in fig. 8, preferably, the first sending module 64 further includes: a first determining unit 641, configured to determine, according to the request message, that the user equipment receives the terminating circuit domain fallback service when the service type carried in the request message is the terminating circuit domain fallback service and/or the circuit domain fallback response indicates that the user equipment receives the terminating circuit domain fallback; the first sending unit 642 is coupled to the first determining unit 641, and is configured to send an SGs service request message to the visitor location register, where the SGs service request message is used to instruct the ue to accept the terminating circuit domain fallback service.

Preferably, the SGs service request message is used to instruct the user equipment to actively initiate an origination circuit domain fallback service, when the service type carried in the request message is an origination circuit domain fallback emergency service. Fig. 9 is a schematic diagram of a preferred structure of a request message receiving apparatus according to an embodiment of the present invention, as shown in fig. 9, preferably, the first sending module 64 further includes: a second determining unit 643, configured to determine, according to the request message, that the user equipment actively initiates an origination circuit domain fallback emergency service when the service type carried in the request message is an origination circuit domain fallback emergency service; the second sending unit 644 is coupled to the second determining unit 643, and configured to send an SGs service request message to the visitor location register, where the SGs service request message is used to instruct the user equipment to actively initiate an origination circuit domain fallback emergency service.

Preferably, the SGs paging rejection message is used to instruct the user equipment to reject the call circuit domain fallback service, when the service type carried in the request message is the call circuit domain fallback service and/or the circuit domain fallback response indicates that the user equipment rejects the call circuit domain fallback. Fig. 10 is a schematic diagram of a preferred structure of the request message receiving apparatus according to the embodiment of the present invention, as shown in fig. 10, preferably, the first sending module 64 further includes: a third determining unit 645, configured to determine, according to the request message, that the ue rejects the terminating circuit domain fallback service when the service type carried in the request message is the terminating circuit domain fallback service and/or the circuit domain fallback response indicates that the ue rejects the terminating circuit domain fallback; the third sending unit 646 is coupled to the third determining unit 645, and is configured to send an SGs paging reject message to the visitor location register, where the SGs paging reject message is used to instruct the ue to reject the terminating call circuit domain fallback service.

The embodiment also provides a user equipment, where the user equipment is also configured to implement the request message receiving method, and a specific implementation process of the user equipment described in the embodiment of the apparatus has been described in detail in the embodiment of the method, and is not described herein again.

The user equipment includes: a second sending module, configured to send a request message carrying a service type and/or a circuit domain fallback response, where the request message includes one of the following: a tracking area update request message, a routing area update request message, and an extended service request message.

Fig. 11 is a schematic diagram of a preferred structure of a user equipment according to an embodiment of the present invention, and as shown in fig. 11, the user equipment includes: a second sending module 112 and a second determining module 114, where the second sending module 112 is coupled to the mobility management unit through a Non-Access-Stratum (NAS), and configured to send a request message carrying a service type and/or a circuit domain fallback response, where the request message includes one of: a tracking area updating request message, a routing area updating request message and an extended service request message; the second determining module 114 is coupled to the mobile management unit through the NAS layer, and configured to update an accept message according to a tracking area from the mobile management unit, and instruct, to start searching for a second generation network or a third generation network and perform access, where the mobile management unit sends, according to the request message, an SGs service request message or an SGs reject paging message to the visitor location register, and the SGs service request message or the SGs reject paging message is used to instruct, by the user equipment, an operation of a circuit domain fallback service.

The modules and units related in the embodiments of the present invention may be implemented by software, or may be implemented by hardware. The modules and units described in this embodiment may also be disposed in the processor, and for example, may be described as: a processor includes a second sending module 112 and a second determining module 114. The names of these modules do not form a limitation on the module itself in some cases, for example, the third sending module may also be described as a "module for sending a request message carrying a service type and/or a circuit domain fallback response".

Preferably, the second determining module 114 is further configured to determine to access the second generation or third generation network according to the predetermined cause value for rejecting the request message from the mobility management unit, wherein the mobility management unit sends the predetermined cause value to the user equipment according to the request message.

Preferably, the circuit domain fallback response is used to instruct the user equipment to accept/reject the circuit domain fallback service.

Preferably, in the case that the request message is an extended service request, the second sending module 112 is further configured to: and sending an extended service request to the mobile management unit according to the trigger of the circuit domain backspacing service.

Preferably, the service type carried in the request message includes an end call circuit domain fallback service or an initial call circuit domain fallback emergency service.

Fig. 12 is a schematic system structure diagram of a mobility management system according to an embodiment of the present invention, and as shown in fig. 12, the system includes: a mobility management unit 122 including the request message receiving means 1222, and the user equipment 124. Preferably, the mobility management unit 122 is coupled with the user equipment 124 through the NAS layer.

The following description and illustrations have been presented in conjunction with a preferred embodiment.

The preferred embodiment provides a method, a system and a device for distinguishing services in a mobility management process. By the preferred embodiment, the 2G/3G network can be accessed quickly when user equipment (including various user terminals) is limited, and meanwhile, signaling sent by the UE to the network side can be saved, so that the standby time of the UE can be prolonged, and certain benefits are provided for avoiding network congestion.

A method for differentiating services in a mobility management process according to the preferred embodiment includes the following steps:

step 1, carrying service type and/or circuit domain backspacing response in a tracking area updating request message or a routing area updating request message sent by UE to a mobile management unit;

step 2, the mobile management unit sends SGs service request message or SGs paging rejection message to VLR, or rejects tracking area update request message and routing area update request by adopting proper reason value.

Preferably, the mobility management unit is an MME and/or an SGSN;

preferably, the service type carried in the tracking area update request message or the routing area update request message sent by the UE to the mobile management unit is a terminating circuit domain fallback service or an originating circuit domain fallback emergency service;

preferably, the circuit domain fallback response carried in the tracking area update request message or the routing area update request message sent by the UE to the mobile management unit is that the UE accepts circuit domain fallback or rejects circuit domain fallback;

preferably, the process of sending the SGs service request message to the VLR by the mobility management unit includes: the mobile management unit receives the tracking area update request message or the routing area update request message, and sends an SGs service request message to the VLR, wherein the SGs service request message is used for indicating that the UE receives the final call circuit domain fallback service or actively initiates the initial call circuit domain fallback service;

preferably, the process of sending the SGs paging rejection message to the VLR by the mobile management unit includes the mobile management unit receiving a tracking area update request message or a routing area update request message, and sending the SGs paging rejection message to the VLR, for indicating that the UE has rejected the terminating call circuit domain fallback service;

preferably, the mobile management unit rejects the tracking area update request message or the routing area update request by using a proper reason value, and after receiving the proper reason value for rejection, the UE directly selects the 2G/3G for access;

a method for differentiating services in a mobility management process according to the preferred embodiment includes: when initiating a final call circuit domain backspacing service or an initial call circuit domain backspacing emergency service, the limited UE sends an extended service request message to a mobile management unit;

wherein, the restricted UE is UE with state of EMM.REGISTERED.ATTEMPING-TO-UPDATE;

preferably, the transmitting the extended service request message to the mobility management unit includes: when the limited UE initiates a final call circuit domain backspacing service or an initial call circuit domain backspacing emergency service, the limited UE does not send a tracking area updating request message or a routing area updating request message;

preferably, the sending of the extended service request message to the mobile management unit is triggered by a paging triggered by a terminating circuit domain fallback service or an originating circuit domain fallback emergency service.

Embodiments of the present invention will now be described by way of example with reference to the accompanying drawings.

It should be noted that, in the following example, a method for implementing service differentiation in a mobility management process through a tracking area update request is shown, however, the following scheme is not limited to the use of a tracking area update request, and may also be implemented by using a routing area update request message, and since the implementation method is similar to the process shown in the following example, details are not described here again.

Fig. 13 is a flowchart illustrating a method for differentiating services by a mobility management procedure according to a preferred embodiment of the present invention, and as shown in fig. 13, the flowchart includes the following steps:

step S1301, after the UE in the EMM, REGISTERED, ATTEMPTING-TO-UPDATE state receives the paging message, the UE stops running the limited timer and replies a tracking area updating request message TO the mobile management unit, wherein the tracking area updating request message carries the service type and/or the circuit domain rollback response;

step S1302, the mobile management unit receives the tracking area update request message, and receives a service type and/or a circuit domain fallback response carried in the message, and if the service type is a terminating circuit domain fallback service and/or a circuit domain fallback response, the UE receives the circuit domain fallback service, the mobile management unit may send an SGs service request message to the VLR; if the service type is the terminating circuit domain fallback service and/or the circuit domain fallback response is that the UE rejects the circuit domain fallback service, the mobile management unit may send an SGs reject paging message to the VLR.

Step S1303, if the mobility management unit rejects the TAU request message, the mobility management unit rejects the tracking area request message using the appropriate cause value, and the UE directly accesses the 2G/3G network after receiving the appropriate cause value.

Step S1302 and step S1303 are described below using specific examples.

Fig. 14 is a flowchart illustrating a method for implementing step S1302 according to an embodiment of the present invention, where as shown in fig. 14, an MME accepts a tracking area update request and notifies a VLR of an SGs service request message, and the flowchart includes the following steps:

step S1401, VLR sends SGs paging message to MME after VLR receives circuit domain terminal call service;

step S1402, MME sends paging message to UE through eNodeB, the paging message carries S-TMSI distributed by network for user and circuit domain identification for marking paging service;

step S1403, after receiving the paging message, the UE in the emm.registered.attemptingto-UPDATE state stops running the restricted timer, and replies a tracking area UPDATE request message TO the MME, where the tracking area UPDATE request message carries a service type and/or a circuit domain fallback response (CSFB response); the service type can be a terminal call circuit domain backspace service, which can be realized by newly adding an information unit in a message or expanding an existing information unit; and the circuit domain fallback response is that the UE accepts or rejects the circuit domain fallback service. In practical implementation, preferably, the message may only carry the circuit domain fallback response but not the service type, and is used to implicitly indicate that the service type is the terminating circuit domain fallback service;

step S1404, when the circuit domain backspacing response is that the UE receives the terminal call circuit domain backspacing service, the MME sends an SGs service request message to the VLR; when the circuit domain backspacing response is that the UE rejects the circuit domain backspacing service, the MME sends an SGs paging rejection message to the VLR;

step S1405, the MME sends a TAU accept message to the UE; after receiving the TAU receiving message, the UE starts a timer and starts to search for a 2G/3G cell for access; if the UE rejects the fallback service of the terminal call circuit domain, the UE stays in the E-UTRAN network.

Fig. 15 is a flowchart illustrating an implementation method of step S1303 according to a preferred embodiment of the present invention, where as shown in fig. 15, an MME rejects a tracking area request message with a suitable cause value, and then a UE selects a 2G/3G network for circuit domain access, where the flowchart includes the following steps:

step S1501, after the VLR receives the circuit domain final call service, the VLR sends an SGs paging message to the MME;

step S1502, MME sends paging message to UE through eNodeB, the paging message carries S-TMSI distributed by network for user and circuit domain identification for marking paging service;

step S1503, after the UE in the EMM.REGISTERED.ATTEMPING-TO-UPDATE state receives the paging message, the UE stops running the limited timer and replies a tracking area UPDATE request message TO the MME, wherein the tracking area UPDATE request message carries the service type and/or the circuit domain fallback response (CSFB response); the service type can be a terminal call circuit domain backspace service, which can be realized by newly adding an information unit in a message or expanding an existing information unit; and the circuit domain fallback response is that the UE accepts the circuit domain fallback service. In practical implementation, preferably, the message may only carry the circuit domain fallback response but not the service type, and is used to implicitly indicate that the service type is the terminating circuit domain fallback service;

step S1504, if UE carries out Local IP Access (LIPA) service from Home eNode B, and the gateway address carried by Home eNode B to MME is not consistent with the gateway address stored by MME, MME sends TAU rejection message to UE, in the TAU rejection message sent by MME to UE, the appropriate reason value is carried, the reason value that can be carried includes 'no effective bearing context', after UE receives the appropriate reason value, UE directly selects 2G/3G to carry out circuit domain Access; similar to the case that the MME needs to reject the TAU request in other scenarios, detailed description is not given. If the circuit domain backspacing response is that the UE rejects the circuit domain backspacing service, after the UE receives a proper rejection reason value, the UE will re-register to the E-UTRAN network.

Fig. 16 is a flowchart illustrating another implementation method of step S1302 according to the preferred embodiment of the present invention, where as shown in fig. 16, the UE initiates a circuit domain fallback originated emergency service, and the MME receives a tracking area update request and notifies the VLR of an SGs service request message, where the flowchart includes the following steps:

step S1601, after UE in EMM.REGISTERED.ATTEMPING-TO-UPDATE state receives an emergency service that an upper layer indicates that an originating circuit domain needs TO be initiated, the UE sends a tracking area UPDATE request message TO MME, wherein the tracking area UPDATE request message carries a service type; the service type can be an emergency service of initial call circuit domain backspacing, which can be realized by newly adding an information unit in a message or expanding an existing information unit;

step S1602, MME sends TAU acceptance message to UE; after receiving the TAU receiving message, the UE starts a timer and starts to search for a 2G/3G cell for access;

fig. 17 is a flowchart illustrating another implementation method of step S1303 according to the embodiment of the present invention, where as shown in fig. 17, the UE initiates an emergency circuit domain fallback originating service, the MME rejects the tracking area request message with a suitable cause value, and then the UE selects a 2G/3G network to perform circuit domain access, where the flowchart includes the following steps:

step S1701, after UE in EMM.REGISTERED.ATTEMPING-TO-UPDATE state receives the emergency service that the upper layer indicates that the initial call circuit domain backspacing needs TO be initiated, UE sends a tracking area updating request message TO MME, wherein the tracking area updating request message carries the service type; the service type can be an emergency service of initial call circuit domain backspacing, which can be realized by newly adding an information unit in a message or expanding an existing information unit;

step S1702, if the UE performs the LIPA service from the Home eNodeB, and the gateway address carried by the Home eNodeB to the MME is not consistent with the gateway address stored by the MME, the MME sends a TAU rejection message to the UE, and the TAU rejection message sent by the MME to the UE carries a proper reason value, wherein the reason value that can be carried includes 'no effective bearing context', and the UE directly selects 2G/3G to perform circuit domain access after receiving the proper reason value; similar to the case that the MME needs to reject the TAU request in other scenarios, detailed description is not given.

Fig. 18 is a schematic operation flow diagram of a mobility management procedure differentiated services system according to a preferred embodiment of the present invention, and as shown in fig. 18, the flow includes the following steps:

step S1801, UE in EMM, REGISTERED, ATTEMPING-TO-UPDATE receives paging message or upper layer indication that needs TO initiate circuit domain fallback service or initial call circuit domain fallback emergency service;

step S1802, the UE stops running the limited timer, and temporarily sends the extended service request message to the mobility management unit without sending the tracking area update request message or the routing area update request message to the mobility management unit.

Fig. 19 is a schematic flow chart of the terminating circuit domain fallback service according to the preferred embodiment of the present invention, and as shown in fig. 19, the flow chart includes the following steps:

step S1901, after VLR receives circuit domain call terminating service, VLR sends SGs paging message to MME;

step S1902, MME sends paging message to UE through eNodeB, the paging message carries S-TMSI distributed by network for user and circuit domain identification for marking paging service;

step S1903, after receiving the paging message, the UE in the emm.registered.attemptingto-UPDATE state stops running the limited timer, temporarily stops sending the tracking area UPDATE request message TO the MME, and sends the extended service request message TO the MME, where the message carries the service type and the circuit domain fallback response (CSFB response); the service type can be a terminal call circuit domain backspace service; a circuit domain fallback response (CSFB response) is used to indicate that the UE accepts or rejects the CSFB service,

step S1904, if MME receives the extended service request message and CSFB response indicates that UE receives the CSFB service, MME sends SGs service request message to VLR; if the MME accepts the extended service request message and CSFBresponse indicates that the UE rejects the terminal call CSFB service, the MME sends an SGs rejection paging message to the VLR;

step 1905, the MME sends an extended service accept message to the UE; after receiving the extended service receiving message, the UE starts a timer and starts to search for a 2G/3G cell for access; if MME rejects the request message of the extended service, MME chooses the appropriate reason value and carries to UE in the request message of the extended service, for example, if UE carries on LIPA business from Home eNodeB, and Home eNodeB carries to the gateway address of MME and is inconsistent with gateway address that MME stores, MME sends the rejection message of the extended service to UE, in the rejection message of the extended service that MME sends to UE, carry the appropriate reason value, the reason value that can carry includes "there is no valid bearing context", after UE receives the appropriate reason value, choose directly to 2G/3G to carry on the circuit domain to cut in.

Fig. 20 is a schematic flow chart of the originating circuit domain fallback service according to the preferred embodiment of the present invention, and as shown in fig. 20, the flow chart includes the following steps:

step S2001, after UE in EMM.REGISTERED.ATTEMPING-TO-UPDATE state receives the emergency service that the upper layer indicates that the initiation of the initial call circuit domain rollback is needed, UE temporarily stops sending the tracking area UPDATE request message TO MME and sends the extended service request message TO MME, wherein the message carries the service type; the service type can be an emergency service of initial call circuit domain backspacing;

step S2002, the MME sends an extended service acceptance message to the UE; after receiving the extended service receiving message, the UE starts a timer and starts to search for a 2G/3G cell for access; if MME rejects the request message of the extended service, MME chooses the appropriate cause value and carries to UE in the request message of the extended service, for example if UE carries on LIPA business from Home eNodeB, and the gateway address that Home eNodeB carries to MME is inconsistent with gateway address that MME stores, MME sends the rejection message of the extended service to UE, in the rejection message of the extended service that MME sends to UE, carry the appropriate cause value, the cause value that can carry includes "there is no valid bearing context", after UE receives the appropriate cause value, directly choose to carry on the circuit domain to cut in to 2G/3G.

Through the embodiments, the preferred embodiments and the implementation manners of the present invention, when the UE is limited, after receiving the paging message, the UE carries the service type and/or the circuit domain fallback response in the tracking area update request message, the routing area update request message, or the extended service request message, which solves the problem of high overhead of reselecting the 2G/3G network access signaling under the condition that the UE is limited, saves the signaling, reduces the call waiting time, and thus ensures that the terminating user can obtain good user experience when the UE is limited.

It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and they may alternatively be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, or fabricated separately as individual integrated circuit modules, or fabricated as a single integrated circuit module from multiple modules or steps. Thus, the present invention is not limited to any specific combination of hardware and software.

The above description is only a preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A request message receiving method, characterized by comprising:

receiving a request message which is sent by user equipment and carries a service type and/or a circuit domain backspace response, wherein the request message comprises one of the following: a tracking area update request message, a routing area update request message, and an extended service request message.

2. The method of claim 1, wherein after receiving the request message, the method further comprises:

sending an SGs service request message or an SGs paging rejection message to a visitor location register according to the request message, wherein the SGs service request message or the SGs paging rejection message is used for indicating the operation of the circuit domain fallback service executed by the user equipment; or,

and sending a predetermined reason value for rejecting the request message to the user equipment according to the request message, wherein the user equipment determines to access a second generation or third generation network according to the predetermined reason value.

3. The method of claim 1, wherein the UE is in a limited state where it cannot actively send non-emergency service messages of a packet switched domain to the network side.

4. The method of claim 1, wherein the traffic type comprises: and finally calling the circuit domain backspace service or the initial calling circuit domain backspace emergency service.

5. The method according to claim 1, wherein after receiving the request message carrying the cs fallback response sent by the ue, the method further comprises:

and determining that the user equipment accepts the circuit domain backspacing service or rejects the circuit domain backspacing service according to the circuit domain backspacing response.

6. The method of claim 1, wherein in case that the request message is an extended service request, the extended service request is sent by the ue in a restricted state according to triggering of the circuit domain fallback service.

7. The method according to any of claims 2 to 6, wherein the SGs service request message is used to indicate the UE to accept the CS domain fallback service when the service type carried in the request message is CS domain fallback service for terminating call and/or the CS domain fallback response indicates that the UE accepts CS domain fallback for terminating call.

8. The method according to any of claims 2 to 6, wherein the SGs service request message is used to instruct the UE to actively initiate an originated circuit domain fallback service, when the service type carried in the request message is an originated circuit domain fallback emergency service.

9. The method according to any of claims 2 to 6, wherein the SGs paging reject message is used to instruct the UE to reject the CS domain fallback service, when the service type carried in the request message is CS domain fallback service and/or the CS domain fallback response indicates that the UE rejects CS domain fallback.

10. A request message receiving apparatus, characterized by comprising:

a first receiving module, configured to receive a request message carrying a service type and/or a circuit domain fallback response sent by a user equipment, where the request message includes one of: a tracking area update request message, a routing area update request message, and an extended service request message.

11. The apparatus of claim 10, further comprising:

a first sending module, configured to send an SGs service request message or an SGs paging reject message to a visitor location register according to the request message, where the SGs service request message or the SGs paging reject message is used to indicate an operation of a circuit domain fallback service executed by the user equipment; or,

the first sending module is configured to send, to the user equipment, a predetermined cause value for rejecting the request message according to the request message, where the user equipment determines to access a second-generation or third-generation network according to the predetermined cause value.

12. The apparatus of claim 10, wherein the apparatus is located in a mobility management unit, and wherein the mobility management unit comprises: a mobility management entity and/or a general packet radio service support node.

13. The apparatus of claim 10, further comprising:

and the first determining module is used for determining that the user equipment accepts the circuit domain backspacing service or rejects the circuit domain backspacing service according to the circuit domain backspacing response.

14. The apparatus of claim 10, wherein in case that the request message is an extended service request, the extended service request is sent by the ue in a restricted state according to triggering of the circuit domain fallback service.

15. The apparatus of any of claims 11-14, wherein the first sending module further comprises:

a first determining unit, configured to determine, according to the request message, that the user equipment accepts a terminating circuit domain fallback service when the service type carried in the request message is the terminating circuit domain fallback service and/or the circuit domain fallback response indicates that the user equipment accepts the terminating circuit domain fallback;

a first sending unit, configured to send the SGs service request message to the visitor location register, where the SGs service request message is used to indicate that the user equipment receives a call circuit domain fallback service.

16. The apparatus of any of claims 11-14, wherein the first sending module further comprises:

a second determining unit, configured to determine, according to the request message, that the user equipment actively initiates an origination circuit domain fallback service when the service type carried in the request message is an origination circuit domain fallback emergency service;

a second sending unit, configured to send the SGs service request message to the visitor location register, where the SGs service request message is used to instruct the user equipment to actively initiate an origination circuit domain fallback service.

17. The apparatus of any of claims 11-14, wherein the first sending module further comprises:

a third determining unit, configured to determine, according to the request message, that the ue rejects the cs fallback service when the service type carried in the request message is the cs fallback service and/or the cs fallback response indicates that the ue rejects the cs fallback;

a third sending unit, configured to send the SGs paging rejection message to the visitor location register, where the SGs paging rejection message is used to instruct the ue to reject the terminating circuit domain fallback service.

18. A user equipment, comprising:

a second sending module, configured to send a request message carrying a service type and/or a circuit domain fallback response, where the request message includes one of the following: a tracking area update request message, a routing area update request message, and an extended service request message.

19. The user equipment of claim 18, wherein the user equipment further comprises:

a second determining module, configured to determine to access a second generation or third generation network according to a predetermined cause value for rejecting the request message from a mobility management unit, where the mobility management unit sends the predetermined cause value to the user equipment according to the request message.

20. The ue of claim 18, wherein the second sending module is further configured to: and sending the extended service request as the request message to the mobile management unit in a limited state according to the trigger of the circuit domain backspacing service.

21. The UE of any one of claims 18 to 20, wherein the traffic type comprises: and finally calling the circuit domain backspace service or the initial calling circuit domain backspace emergency service.

22. A request message transmission system, comprising: a mobility management unit comprising the request message receiving apparatus of any one of claims 10 to 17, and the user equipment of any one of claims 18 to 21.