WO2012167478A1 - 处理寻呼的方法、用户设备和系统 - Google Patents
处理寻呼的方法、用户设备和系统 Download PDFInfo
- Publication number
- WO2012167478A1 WO2012167478A1 PCT/CN2011/077180 CN2011077180W WO2012167478A1 WO 2012167478 A1 WO2012167478 A1 WO 2012167478A1 CN 2011077180 W CN2011077180 W CN 2011077180W WO 2012167478 A1 WO2012167478 A1 WO 2012167478A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- user equipment
- mme
- sgsn
- mobility management
- message
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
- H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
Definitions
- the present invention relates to the field of communications technologies, and in particular, to a method, user equipment and system for processing paging. Background technique
- the 2G/3G network and the LTE network coexist in a certain period of time.
- the UE User Equipment, User Equipment
- TAU Tracking Area Update
- RAU Radio Access Type
- the ISR Idle mode signal reduction
- the ISR mechanism between 3GPP (The 3rd Generation Partnership Project) access network is a dual registration mechanism, that is, the UE is registered in two different access networks.
- the ISR mechanism is activated, when the UE moves from the MME (Mobility Management Entity) to the SGSN (Serving GPRS Support Node), the UE context on the MME is not deleted; correspondingly, the UE When moving from the SGSN to the MME, the UE context on the SGSN will not be deleted.
- MME Mobility Management Entity
- SGSN Serving GPRS Support Node
- the SGW Serving Gateway
- DDN Downlink Data Notification, downlink data
- the network side may according to the context of the UE saved on the MME.
- the corresponding bearer is established. If the UE resides on the 2G/3G network, the network side establishes a corresponding 7-load according to the context of the UE saved on the SGSN.
- the network side may spoof the UE.
- the part of the bearer may be lost or the bearer with the inconsistent context information of the two ends may be affected, which seriously affects the normal use of the service. Bad user experience. Summary of the invention
- the embodiment of the present invention provides a method, a user equipment, and a system for processing a paging, which are used to solve the problem that after the radio access type change occurs in the state in which the ISR mechanism is activated, the network side may cause the UE to page the UE.
- the bearer is lost or the bearer with inconsistent context information is established at both ends.
- An embodiment of the present invention provides a method for processing paging, including:
- the user equipment receives the paging message sent by the mobility management network element
- the user equipment sends a location update message according to the value of the temporary identifier (TIN) for the next update; the mobility management network element receives the location update message, and obtains bearer context information of the user equipment.
- TIN temporary identifier
- the embodiment of the invention further provides a user equipment, including:
- a receiving module configured to receive a paging message sent by the mobility management network element
- the sending module is configured to: after receiving the paging message sent by the mobility management network element, send the location update message to the mobility management network element according to the value of the TIN, so that the mobility management network element obtains the bearer context information of the user equipment.
- the embodiment of the invention further provides a system for processing paging, comprising: a mobility management network element and a user equipment;
- the mobility management network element is configured to send a paging message to the user equipment, and after receiving the location update message sent by the user equipment, obtain the bearer context information of the user equipment;
- the user equipment is configured to receive a paging message sent by the mobility management network element, and send a location update message to the mobility management network element according to the value of the TIN.
- the user equipment After receiving the paging message sent by the network side, the user equipment sends a location update message by determining the value of the TIN on the user equipment, and the mobility management network element obtains the bearer of the user equipment after receiving the location update message.
- Context information, the bearer context information on the mobility management network element on the network side is consistent with the bearer context information on the user equipment, and the part of the bearer lost in the paging process or the inconsistent bearer context information is established.
- the problem of bearer ensures the normal use of the business and improves the user experience.
- FIG. 3 is a schematic flowchart diagram of a first method according to an embodiment of the present disclosure
- FIG. 4 is a schematic flowchart of a second method according to an embodiment of the present invention.
- FIG. 5 is a second state diagram according to an embodiment of the present invention.
- FIG. 6 is a schematic flowchart diagram of a third method according to an embodiment of the present disclosure.
- FIG. 7 is a schematic flowchart diagram of a fourth method according to an embodiment of the present disclosure.
- FIG. 8 is a third state diagram according to an embodiment of the present invention.
- FIG. 9 is a schematic flowchart diagram of a fifth method according to an embodiment of the present disclosure.
- FIG. 10 is a schematic structural diagram of a device according to an embodiment of the present disclosure.
- FIG. 11 is a schematic structural diagram of a system according to an embodiment of the present invention. detailed description
- GSM Global System of Mobile communication
- UMTS Universal Mobile Telecommunications System
- the CN can be logically divided into a Circuit Switched Domain (CS Domain) and a Packet Switched Domain (PS Domain).
- CS Domain Circuit Switched Domain
- PS Domain Packet Switched Domain
- the CS domain mainly handles voice services
- the PS domain mainly handles packet services.
- the signaling plane control entity of the PS domain is an SGSN (Serving GPRS Support Node).
- the SGSN is connected to the BSC (Base Station Controller) through the Gb interface, and is connected to the RNC (Radio Network Controller) through the Iu interface. It is GPRS (General Packet Radio Service) / UMTS. Data business services.
- GPRS General Packet Radio Service
- UMTS Universal Mobile Telecommunication Standard
- LTE Long Term Evolution
- EPS evolved packet system
- FIG. 1 is a current wireless evolution network architecture diagram.
- the BTS Base Transceiver Station
- the BSC form the wireless access part of the 2G network, called GERAN (GSM EDGE Radio Access Network, GSM/EDGE Radio Access Network).
- GERAN GSM EDGE Radio Access Network, GSM/EDGE Radio Access Network.
- NodeB (Node B) and RNC form the wireless access part of the 3G network, called UTRAN (UTTS Terrestrial Radio Access Network).
- UTRAN UTTS Terrestrial Radio Access Network
- the LTE network is composed of an eNodeB (evolved NodeB, evolved Node B), an MME, an SGW (Serving Gateway), and a PGW (PDN Gateway, Packet Data Network Gateway).
- the eNodeB constitutes a radio access part of the LTE network, and is called an E-UTRAN (Evolved UTMS Terretrial Radio Access Network, an evolved UMTS terrestrial radio access network).
- the main functions of the eNodeB include: implementation of radio resource management functions; IP header compression and user data stream encryption; MME selection when the UE is attached; scheduling transmission of paging information; scheduling transmission of broadcast information; and setting and providing eNodeB measurements.
- the core network in the wireless evolution network architecture diagram shown in FIG. 1 mainly includes the following network elements SGSN, MME, SGW, and PGW.
- the SGSN supports GTPv2 (GPRS Tunnelling Protocol Version 2, GPRS Tunneling Protocol Second Edition), which is 2G/3G.
- the mobile management network element of the network implements functions such as managing the user context of 2G/3G network users.
- the MME is a mobility management entity responsible for NAS (Non-Access-Stratiction) signaling and NAS signaling encryption. Roaming, tracking, etc., assign user temporary identity, security function, etc., which corresponds to the control plane part of the current SGSN system SGSN.
- the SGW is responsible for the local mobility anchor and the mobility anchor inside the 3GPP system and the lawful interception related information; the PGW is responsible for policy enforcement and charging and legal interception related functions.
- the user equipment can access different networks in the architecture, for example, UE1 accesses the LTE network, UE2 accesses the 3G network, and UE3 accesses the 2G network.
- the S3 interface between the SGSN and the MME is used for performing user context transmission and the like when the user equipment moves between the 2G/3G network and the LTE network.
- the MME and the SGSN are respectively connected to the SGW, and the MME is connected to the SGSN.
- the UE accesses and establishes bearer A under the MME and activates the ISR mechanism. As shown in the state 0 of FIG. 2, at this time, the UE is on the MME side.
- Context information of bearer A is reserved on the UE
- Context information of bearer A is reserved on the MME.
- the UE moves from the LTE network to the 2G/3G network, and the SGSN obtains the latest context information of the UE (including the context information of the bearer A) from the MME side, and the UE establishes the bearer B on the SGSN side.
- the value of the local TIN of the UE is set to P-TMSL as shown in state 1 of FIG. In this case, the UE is on the SGSN side,
- Context information of bearer A and bearer B is reserved on the UE;
- Context information of bearer A is reserved on the MME
- Context information of bearer A and bearer B is reserved on the SGSN.
- the UE moves from the 2G/3G network to the LTE network. Since the local ISR mechanism of the UE is deactivated, the UE sends a TAU message to the MME to synchronize the context information. If the MME is in an overload state, the MME will reject the TAU process. The MME sends a TAU Reject message to the UE, and carries a value of the Mobility Management back-off timer in the TAU Reject message. After receiving the value of the mobility management delay timer, the UE will The local mobility management delay timer of the UE is started. During the operation of the local mobility management delay timer, the UE temporarily does not initiate the TAU procedure.
- the processing method when the MME is overloaded is a congestion processing mechanism of the NAS layer.
- the MME may reject the MM (Mobility Management) request message sent by the UE.
- the MME sends a value of the mobility management delay timer to the MME.
- UE UE will initiate a local mobility management deferral timer, during which the UE will not initiate any NAS request (except for the UE) Service users, emergency services, and called services), which can be reduced in the event of network overload
- the UE is on the MME side.
- Context information of bearer A and bearer B is reserved on the UE;
- Context information of bearer A is reserved on the MME
- Context information of bearer A and bearer B is reserved on the SGSN.
- the RAU process is initiated to the SGSN. If the SGSN is in an overload state, the UE initiates the RAU message, and the SGSN includes the RAU Reject message sent to the UE.
- the mobility management delays the value of the timer. After receiving the UE, the local mobility management delay timer is started, and the NAS message (except for the service user, emergency service, and called service) is not sent during the mobility management delay timer operation. During the operation of the mobility management delay timer, the UE moves from the 2G/3G network to the LTE network.
- the mobility management delay timer is not related to the RAT in the current protocol, after the UE moves to the LTE network, the UE local mobility management is postponed. The timer is still running. Because the value of the TIN on the UE is set to P-TMSI, the UE needs to initiate the TAU procedure. However, since the UE local mobility management delay timer is still running, the UE does not initiate TAU temporarily. Process. This scenario also causes the MME to not match the bearer context information retained by the SGSN.
- the bearer context information reserved by the 2G/3G network and the LTE network may be inconsistent.
- the network side may restrict access by using a broadcast message in order to restrict part of user access.
- Device type table When these devices are moved to a network with restricted access, they do not actively initiate TAU messages, but can receive scenarios of called services.
- the UE After the SGW receives the Create Bearer Request message, the UE needs to page the UE to make the UE in the connected state, and then perform the process of establishing a new bearer.
- the SGW sends a DDN message to the MME and the SGSN, causing the SGSN and the MME to simultaneously page.
- UE the UE is on the MME side, and after receiving the paging message, the UE sends a Service Request message to the MME.
- the MME After receiving the Service Request message, the MME sends an Initial Context Setup Request message to the eNodeB, where the message carries the bearer information on the MME.
- the bearer information includes a bearer ID (bearer ID), etc. If there are multiple bearers, the carried message will include a bearer information list, and the list includes information of each bearer. At this time, the bearer information on the MME includes only the Bearer ID of the bearer A.
- the eNodeB notifies the UE of the received Bearer ID and the like to establish a radio access bearer. If the Bearer ID notified by the eNodeB to the UE does not exist locally, the radio access bearer corresponding to the Bearer ID will fail to be established, if the UE is local.
- the Bearer ID is not included in the Bearer ID list in which the eNodeB requests the UE to establish a radio access bearer.
- the UE locally deletes the bearer context information corresponding to the Bearer ID. Since the Bearer ID of the bearer B of the UE is not included in the Bearer ID list in which the eNodeB requests the UE to establish a radio access bearer, the UE locally deletes the context information of the bearer B.
- the eNodeB After the radio access bearer between the UE and the eNodeB is established, the eNodeB sends an Initial Context Setup Response message to the MME, and the MME sends a Modify Bearer Request message to the SGW, and the SGW sends a Modify to the MME.
- the SGW After the SGW receives the Modify Bearer Request message sent by the MME, the SGW can learn that the UE is camped on the MME side, and the SGW sends a Stop Paging message to the SGSN to stop the SGSN and then page the UE.
- the entire paging process is completed and the UE is in the connected state.
- the process of establishing a new bearer is performed, and the newly created bearer is the bearer C.
- a person skilled in the art can understand that there are other situations that may cause the network side to initiate paging to the UE, such as receiving a modify bearer request, receiving a downlink data packet, and the like.
- the UE is on the MME side.
- Context information of bearer A and bearer C is reserved on the UE; Context information of bearer A and bearer C is reserved on the MME;
- Context information of bearer A and bearer B is reserved on the SGSN.
- the UE when the mobility management delay timer expires on the UE, the UE initiates a TAU procedure to the MME, and the MME requests the SGSN for the latest context information, and the context information on the MME is updated to the context information of the bearer A and the bearer B.
- the UE initiates the Service Request process, and the MME deletes the context information of the bearer B that is not on the UE.
- the UE deletes the context information of the bearer C that is not on the MME, and the UE and the MME only have the context of the bearer A. information.
- the MME does not obtain the bearer context information from the SGSN, and the bearer context information of the UE and the MME are inconsistent, resulting in partial bearer loss, which seriously affects the normal service. Use, resulting in a bad user experience.
- step 2) the UE does not establish a new 7-B on the SGSN side, but ⁇ ⁇ ⁇ 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7
- the bearer context information is obtained, which causes the bearer context information of the UE and the SGSN to be inconsistent, causing partial bearer loss or establishing a bearer with inconsistent bearer context information.
- the current wireless evolved network architecture includes an LTE network and a 2G/3G network.
- the network architecture With the development of the network architecture, more network coexistence scenarios may occur, and the UE may be in three or more types. Switching between mobility management network elements may also occur When the network side pages the UE, part of the bearer is lost or a bearer with inconsistent bearer context information is established.
- an embodiment of the present invention provides a method for processing paging, including:
- the user equipment receives a paging message sent by the mobility management network element.
- the user equipment sends a location update message according to the value of the TIN;
- the mobility management network element receives a location update message, and obtains a bearer context of the user equipment.
- GUTI Globally Unique Temporary Identity
- RAT-Related TMSI Radio Access Type Related Temporary Mobile Subscriber Indentity
- the value of the TIN is P-TMSI, which indicates that the bearer context information of the user equipment changes on the SGSN side; the value of the TIN is GUTI, indicating that the bearer context information of the user equipment changes on the MME side; the value of the TIN is RAT-Related TMSI , indicating that the context information of the user device has not changed.
- the value of the TIN reflects the change of the bearer context information of the user equipment. For example, after the user equipment establishes a bearer on the SGSN, the value of the TIN of the user equipment is set to P-TMSI, indicating that the bearer context information of the user equipment changes on the SGSN side. When the user equipment moves to the MME side, the TAU is initiated. After the MME obtains the bearer context information from the SGSN, the value of the TIN of the user equipment is set to RAT-Related TMSI, indicating that the bearer context information on the current MME, SGSN, and UE is consistent, and no change occurs.
- the TIN may have other values, which may be used to indicate that changes in bearer context information occur on different network sides.
- the user equipment sends a location update message according to the value of the TIN, and the mobility management network element obtains the bearer context information after receiving the location update message, that is, the user equipment determines the value of the TIN, Obtaining on which network side the bearer context information changes, by sending a location update message to the mobility management network element of the network side where the current user equipment is located, so that the mobility management network element moves to the network side where the bearer context information changes.
- the management NE obtains the context information.
- the mobility management network element on the network side obtains the bearer context information on the user equipment after acquiring the bearer context information from the mobility management network element on the network side where the bearer context information changes. It is consistent with the bearer context information on the mobility management network element on the network side where the user equipment is located. Therefore, during the paging process, the bearer is not lost, which ensures the normal use of the service and improves the user experience.
- the method provided by the embodiment of the present invention may be specifically:
- the user equipment receives a paging message sent by the MME.
- the user equipment sends a TAU message when the value of the TIN of the user equipment is P-TMSI.
- the MME receives the TAU message, and acquires bearer context information of the user equipment from the SGSN.
- the user equipment After receiving the paging message sent by the MME, the user equipment determines that the bearer context information changes on the SGSN side, and the user equipment needs to send a location update message. Therefore, the user equipment sends a TAU message.
- the TAU message is a type of the location update message.
- the MME After receiving the TAU message, the MME obtains the bearer context information of the user equipment from the SGSN.
- FIG. 5 is a state diagram after the UE is used on the MME side by using the method provided by the embodiment of the present invention. To illustrate the technical effects of the embodiment of the present invention, FIG. 5 only shows the state 2 before the paging occurs, and after the paging occurs. State 3', as shown in Figure 5:
- the state 2 of FIG. 5 is similar to the state 2 of FIG. 2.
- the UE is on the MME side, and the mobility management delay timer on the UE is in the running state.
- Context information of bearer A and bearer B is reserved on the UE;
- Context information of bearer A is reserved on the MME
- Context information of bearer A and bearer B is maintained on the SGSN.
- the network side initiates paging.
- the UE After receiving the paging request sent by the MME, the UE determines that its own TIN value is P-TMSI, and then sends a TAU message. After receiving the TAU message, the MME obtains the bearer context information from the SGSN.
- the UE is on the MME side.
- Context information of bearer A and bearer B is reserved on the UE;
- Context information of bearer A and bearer B is reserved on the SGSN.
- the UE determines that the bearer context information has changed on the SGSN side by determining the value of the TIN of the TIN. Therefore, the UE sends the TALK' information, and the MME receives the TAU message.
- the MME obtains the bearer context information from the SGSN.
- the bearer context information on the MME is consistent with the bearer context information on the UE. Therefore, the context information of the bearer B on the UE is not deleted in the process of paging the UE by the MME, that is, the bearer. B will not be lost, ensuring the normal use of the business and improving the user experience.
- step 202 can be specifically:
- the mobility management delay timer of the user equipment When the mobility management delay timer of the user equipment is in the running state and the value of the TIN of the user equipment is P-TMSI, the user equipment sends a TAU message.
- the mobility management delay timer is in the running state, indicating that the user equipment does not actively send the TAU message.
- FIG. 6 illustrates a scenario in which the UE initially camps on the MME side and activates the ISR mechanism.
- the UE moves from the LTE network to the 2G/3G network, and establishes a new load on the 2G/3G network. Then, the UE returns from the 2G/3G network to the LTE network.
- the UE initiates the TAU procedure to the MME
- the UE is rejected due to the MME overload, and the UE starts the mobility management delay timer, and the UE cannot actively send the NAS message during the running of the timer.
- the called service can be accepted.
- the UE When the UE receives the paging sent by the MME, the UE determines that the internal TIN value is P-TMSI, and then sends a TAU message. After receiving the TAU message, the MME obtains the bearer context of the UE from the SGSN. information. details as follows:
- the UE initiates an attach procedure to the MME, accesses the LTE network, and activates the ISR mechanism; that is, the UE is on the MME side.
- the UE moves from the LTE network to the 2G/3G network;
- the UE moves to the SGSN side.
- the UE establishes a new bearer under the 2G/3G network
- the UE moves from the 2G/3G network to the LTE network;
- the UE moves to the MME side.
- the UE sends a Tracking Area Update (TAU) message to the MME.
- TAU Tracking Area Update
- the UE After the UE establishes a new bearer in the SGSN, the UE needs to send a TAU message to the MME after the UE moves to the MME side, so that the MME obtains bearer context information from the SGSN.
- the MME sends a tracking area update reject (TAU Reject) message to the UE, because the MME is overloaded;
- TAU Reject tracking area update reject
- the TAU Reject message includes a mobility management delay timer. After receiving the TAU Reject message sent by the MME and including the mobility management delay timer, the UE starts its own mobile tube. The delay timer is not used. The UE does not actively send NAS messages (except for service users, emergency services, and called services). At this time, there is a case where the bearer context information on the UE and the MME are inconsistent.
- the PGW After receiving the downlink data packet sent by the PGW, the PGW sends the downlink data packet to the SGW.
- a person skilled in the art can understand that there are other ways to cause the network side to initiate paging to the UE, for example, receiving a new bearer request or receiving a modify bearer request.
- the SGW sends a downlink data notification (DDN) message to the MME and the SGSN, respectively.
- DDN downlink data notification
- the MME and the SGSN respectively send a downlink data notification response (DDN Ack) message to the SGW.
- DDN Ack downlink data notification response
- the MME sends a paging message to the eNodeB.
- the SGSN sends a paging message to the RNC/BSC.
- the eNodeB sends a paging message to the UE.
- the RNC/BSC sends a paging message to the UE.
- the UE sends a tracking area update message to the MME.
- the UE is on the MME side. After receiving the paging message sent by the eNodeB, the UE determines that the value of the TIN is P-TMSI, and learns that the bearer context information has changed on the SGSN side. Therefore, the UE sends a TAU message, and the MME receives the TAU message. Afterwards, the MME obtains bearer context information from the SGSN.
- the UE may also determine whether the mobility management delay timer is in the running state at the same time.
- the mobility management delay timer is in the running state and the value of the TIN is P-TMSI, the TAU message is sent.
- the MME sends a context request (Context Request) message to the SGSN.
- the SGSN sends a context response (Context Response) message to the MME; at this time, the MME has obtained the bearer context information from the SGSN. At this time, the bearer context information on the UE and the MME are consistent.
- Context Response Context Response
- the MME sends a Modify Bearer Request message to the SGW.
- 313 The SGW sends a Modify Bearer Response message to the MME.
- the radio bearer between the UE and the eNodeB is established. Because the bearer context information on the UE and the MME is consistent, the SGW does not appear in the process. Some of the bearers are lost.
- the MME sends a Tracking Area Update Accept (TAU Accept) message to the UE.
- TAU Accept Tracking Area Update Accept
- the downlink data packets can be sent from the SGW to the UE.
- the uplink and downlink channels (for example, the connection on the wireless side) are established, and the new bearer request process or the modify bearer request process is continued.
- the UE after receiving the page sent by the MME, the UE determines that the bearer context has changed on the SGSN side by determining the value of its own TIN. Therefore, the UE sends a TAU message, and the MME receives the TAU. After the message, the bearer context information is obtained from the SGSN. Since the bearer context information on the MME is consistent with the bearer context information on the UE, the partial bearer is not lost during the paging process, which ensures the normal use of the service and improves the normal use of the service. user experience.
- the method provided by the embodiment of the present invention may be specifically:
- the user equipment receives the paging message sent by the SGSN.
- 402 When the value of the TIN of the user equipment is GUTI, the user equipment sends a RAU message; 403: The SGSN receives the RAU message, and acquires bearer context information of the user equipment from the MME.
- the user equipment After receiving the paging message sent by the SGSN, the user equipment determines that the bearer context information has changed on the MME side, and the user equipment needs to send a location update message, so the user equipment sends a RAU message.
- the RAU message is a type of location update message.
- the SGSN After receiving the RAU message, the SGSN obtains bearer context information from the MME.
- FIG. 8 is a state diagram after the UE is used on the SGSN side by using the method provided by the embodiment of the present invention. To illustrate the technical effects of the embodiment of the present invention, FIG. 8 only shows the state 2 before the paging occurs and after the paging occurs. State 3", as shown in Figure 8:
- the state of Figure 8 is not as follows: The UE is on the SGSN side, and the mobility management on the UE delays the timer in the running state.
- Context information of bearer A and bearer B is reserved on the UE;
- Context information of bearer A and bearer B is reserved on the MME;
- Context information of bearer A is maintained on the SGSN.
- the network side initiates paging.
- the UE After receiving the paging request sent by the SGSN, the UE determines that its own TIN value is a GUIT, and then sends a RAU message, and the SGSN obtains the bearer context information from the MME after receiving the RAU message.
- the UE is on the SGSN side
- Context information of bearer A and bearer B is reserved on the UE;
- Context information of bearer A and bearer B is reserved on the SGSN.
- the UE determines that the bearer context information has changed on the MME side by determining the value of the TIN of the TIN. Therefore, the UE sends the RAU message, and the SGSN obtains the bearer of the user equipment from the MME. Context information, because the bearer context information on the SGSN is consistent with the bearer context information on the UE, the context information of the bearer B on the UE is not deleted in the process of paging the UE by the SGSN, that is, the bearer B is not lost, and the guarantee is guaranteed. The normal use of the business improves the user experience.
- step 402 can be specifically:
- the user equipment When the mobility management delay timer of the user equipment is in the running state and the value of the TIN of the user equipment is GUTI, the user equipment sends a RAU message.
- the mobility management delay timer is in the running state, indicating that the user equipment does not actively send the RAU. Message.
- FIG. 9 illustrates a scenario in which the UE initially camps on the SGSN side and activates the ISR mechanism.
- the UE moves from the 2G/3G network to the LTE network, and establishes a new bearer in the LTE network, and then The UE returns from the LTE network to the 2G/3G network.
- the UE initiates the RAU procedure to the SGSN
- the UE is rejected due to the SGSN overload, and the UE starts the mobility management delay timer.
- the UE cannot actively send the NAS message during the running of the timer, but may The received service is received.
- the UE When the UE receives the paging sent by the SGSN, the UE determines that the internal TIN value is the GUIT and then sends the RAU message. After receiving the RAU message, the SGSN obtains the bearer context information of the UE from the MME. Specific ⁇ below:
- the UE initiates an attach procedure to the SGSN, accesses the 2G/3G network, and activates the ISR mechanism.
- the UE is on the SGSN side.
- the UE moves from the 2G/3G network to the LTE network;
- the UE moves to the MME side.
- the UE establishes a new bearer under the LTE network
- the UE sets the TIN to GUTI.
- the UE moves from the LTE network to the 2G/3G network;
- the UE moves to the SGSN side.
- the UE sends a Routing Area Update (RAU) message to the SGSN.
- RAU Routing Area Update
- the UE Because the UE establishes a new payload under the MME, the UE needs to send a RAU message to the MME after the UE moves to the SGSN side. After receiving the RAU message, the SGSN obtains the bearer context information from the MME.
- the SGSN sends a Routing Area Update Reject (RAU Reject) message to the UE because the SGSN is overloaded;
- RAU Reject Routing Area Update Reject
- the RAU Reject message includes the mobility management delay timer time.
- UE receives MME After the RAU Reject message containing the mobility management delay timer is sent, the mobile management delay timer is started. If the timer does not time out, the UE does not actively send the NAS message (except for the service user, emergency service, and called). business). At this time, the bearer context information on the UE and the SGSN is inconsistent.
- the PGW After receiving the downlink data packet sent by the PGW, the PGW sends the downlink data packet to the SGW.
- a person skilled in the art can understand that there are other ways to cause the network side to initiate paging to the UE, for example, receiving a new bearer request or receiving a modify bearer request.
- the SGW sends a downlink data notification (DDN) message to the MME and the SGSN, respectively.
- DDN downlink data notification
- the MME and the SGSN respectively send a downlink data notification response (DDN Ack) message to the SGW.
- DDN Ack downlink data notification response
- the MME sends a paging message to the eNodeB.
- the SGSN sends a paging message to the RNC/BSC.
- the eNodeB sends a paging message to the UE.
- the RNC/BSC sends a paging message to the UE.
- the UE sends a Routing Area Update (RAU) message to the SGSN.
- RAU Routing Area Update
- the UE is on the SGSN side. After receiving the paging message sent by the RNC/BSC, the UE determines that the TIN value is GUTI, and learns that the bearer context information has changed on the MME side. Therefore, the RAU message is sent, and the SGSN receives the RAU message.
- the bearer context information is obtained from the MME.
- the UE may also determine whether the mobility management delay timer is in the running state at the same time.
- the mobility management delay timer is in the running state and the value of the TIN is GUTI, the RAU message is sent.
- the SGSN sends a context request (Context Request) message to the MME.
- the MME sends a context response (Context Response) message to the SGSN; at this time, the SGSN has acquired bearer context information from the MME. At this time, the UE and the bearer context information on the SGSN remain consistent.
- Context Response Context Response
- the SGSN sends a Modify Bearer Request message to the SGW.
- 513 The SGW sends a Modify Bearer Response message to the SGSN.
- the radio bearer between the UE and the RNC/BSC is established. Because the bearer context information on the UE and the SGSN is consistent, in this process, Partial bearer loss will occur.
- the SGSN sends a Routing Area Update Accept (RAU Accept) message to the UE.
- RAU Accept Routing Area Update Accept
- the downlink data packet can be sent from the SGW to the UE.
- the upstream and downstream channels (for example, the wireless side connection) are established, and the new load request process or the modify bearer request process is continued.
- an embodiment of the present invention further provides a user equipment, including:
- the receiving module 601 is configured to receive a paging message sent by the mobility management network element.
- the sending module 602 is configured to: after receiving the paging message sent by the mobility management network element, according to
- the value of the TIN sends a location update message to the mobility management network element, so that the mobility management network element can obtain the bearer context information of the user equipment.
- the user equipment After receiving the paging message sent by the mobility management network element, the user equipment according to the embodiment of the present invention sends a location update message to the mobility management network element according to the value of its own TIN, and the mobility management network element receives the location update. After the message, the bearer context information of the user equipment is obtained.
- the receiving module 601 is specifically configured to receive a paging message sent by the MME.
- the sending module 602 is specifically configured to: after receiving the paging message sent by the MME, when the value of the TIN is P-TMSI, send a TAU message to the MME, so that the MME obtains the user setting from the SGSN.
- the bearer context information is specifically configured to: after receiving the paging message sent by the MME, when the value of the TIN is P-TMSI, send a TAU message to the MME, so that the MME obtains the user setting from the SGSN.
- the bearer context information is specifically configured to: after receiving the paging message sent by the MME, when the value of the TIN is P-TMSI, send a TAU message to the MME, so that the MME obtains the user setting from the SGSN.
- the sending module 602 is specifically configured to: after receiving the paging message sent by the MME, send a TAU message to the MME when the mobility management delay timer is in the running state and the value of the TIN is P-TMSI.
- the user equipment After receiving the paging message sent by the MME, the user equipment sends a TAU message to the MME when the value of the TIN is P-TMSI. After receiving the TAU message, the MME obtains the bearer context information of the user equipment.
- the receiving module 601 is specifically configured to receive a paging message sent by the SGSN.
- the sending module 602 is specifically configured to: after receiving the paging message sent by the SGSN, when the value of the TIN is a GUTI, send the RAU message to the SGSN, so that the SGSN obtains the bearer context information of the user equipment from the MME.
- the sending module 602 is specifically configured to: after receiving the paging message sent by the SGSN, send a RAU message to the SGSN when the mobility management delay timer is in the running state and the value of the TIN is GUTI.
- the user equipment After receiving the paging message sent by the SGSN, the user equipment sends a RAU message to the SGSN when the TIN value is GUTI. After receiving the RAU message, the SGSN obtains the bearer context information of the user equipment.
- the user equipment provided by the embodiment of the present invention sends a location update message to the mobility management network element by determining the value of the TIN on the user equipment after receiving the paging message sent by the network side, and the mobility management network.
- the UE After receiving the location update message, the UE obtains the bearer context information of the user equipment, and the bearer context information on the mobility management network element of the network side where the user equipment is located is consistent with the bearer context information on the user equipment, thereby being able to overcome the search.
- the problem of losing part of the bearer in the call process or establishing a bearer with inconsistent context information at both ends ensures the normal use of the service and improves the user experience.
- the embodiment of the present invention further provides a system for processing paging, including: a mobility management network element 701 and a user equipment 702;
- the mobility management network element is configured to send a paging message to the user equipment, and after receiving the location update message sent by the user equipment, obtain the bearer context information of the user equipment;
- the user equipment is configured to receive a paging message sent by the mobility management network element, and send a location update message to the mobility management network element according to the value of the TIN.
- the mobility management network element may be an MME
- the MME is specifically configured to send a paging message to the user equipment, and after receiving the TAU message sent by the user equipment, obtain the bearer context information of the user equipment from the SGSN;
- the user equipment is specifically configured to receive a paging message sent by the MME, and send a TAU message to the MME when the value of the TIN is P-TMSI.
- the user equipment is specifically configured to receive a paging message sent by the MME, and send a TAU message to the MME when the mobility management delay timer is in an running state and the value of the TIN is P-TMSI.
- the mobility management network element may be an SGSN
- the SGSN is specifically configured to send a paging message to the user equipment, and after receiving the RAU message sent by the user equipment, obtain the bearer context information of the user equipment from the MME;
- the user equipment is specifically configured to receive a paging message sent by the SGSN, and send a RAU message to the SGSN when the value of the TIN is GUTI.
- the user equipment is specifically configured to: receive the paging message sent by the SGSN, and send a RAU message to the SGSN when the mobility management delay timer is in the running state and the value of the TIN is GUTI.
- the system for processing paging After receiving the paging message sent by the network side, the system for processing paging sends a location update message by determining the value of the TIN on the user equipment, and the mobility management network element receives the location update message.
- the bearer context information of the user equipment is obtained, and the bearer context information on the mobility management network element of the network side where the user equipment is located and the bearer on the user equipment are implemented. The following information is consistent, which can overcome the problem of losing part of the bearer in the paging process or establishing a bearer with inconsistent context information on both ends, ensuring the normal use of the service and improving the user experience.
- modules in the user equipment in the embodiment may be distributed in the user equipment of the embodiment according to the embodiment, or may be correspondingly changed in one or more user equipments different from the embodiment. .
- the modules of the above embodiments may be combined into one module, or may be further split into multiple sub-modules.
- the method includes the steps of the foregoing method embodiments; and the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本发明涉及一种处理寻呼的方法、用户设备和系统。其中一种方法包括:用户设备接收移动性管理网元发送的寻呼消息;该用户设备根据用于下次更新的临时标识(TIN)的值发送位置更新消息,该移动性管理网元接收位置更新消息,获取用户设备的承载上下文信息。本发明实施例在用户设备收到寻呼消息后,通过判断用户设备的TIN的值来发送位置更新消息,移动性管理网元收到位置更新消息后,获取承载上下文信息,可以实现用户设备所在的网络侧的移动性管理网元上的承载上下文信息与用户设备上的承载上下文信息保持一致,进而能够克服在寻呼过程中丟失部分承载或者建立了两端承载上下文信息不一致的承载的问题,保障了业务的正常使用,提高了用户体验。
Description
处理寻呼的方法、 用户设备和系统 技术领域
本发明涉及通信技术领域, 特别是涉及一种处理寻呼的方法、 用户设备 和系统。 背景技术
网络从 2G/3G网络向 LTE ( Long Term Evolution, 长期演进计划) 网络 演进的过程中, 在一定时期内, 会存在 2G/3G网络与 LTE网络并存的场景。 在 2G/3G网络与 LTE网络的交接处, UE ( Uer Equipment, 用户设备)在从 2G/3G网络移动到 LTE网络时, 会发起 TAU ( Tracking Area Update , 跟踪区 更新)流程; UE从 LTE网络移动到 2G/3G网络时,会发起 RAU( Routing Area Update,路由区更新)流程。为了减少 UE在 Idle (空闲)态下由于 RAT ( Radio Access Type,无线接入类型)的变化而引发的 TAU或 RAU, 引入了 ISR ( Idle mode signalling reduction, 空闲模式下的信令节约 )机制。 目前 3GPP ( The 3rd Generation Partnership Project, 第三代合作伙伴计划)接入网洛之间的 ISR机 制为双注册机制, 即 UE在两个不同的接入网络都注册。 在 ISR机制激活的 情况下, UE从 MME ( Mobility Management Entity, 移动管理实体)移动到 SGSN ( Serving GPRS Support Node, 服务 GPRS支持节点) 时, MME上的 UE上下文不会被删除; 相应地, UE从 SGSN移动到 MME时, SGSN上的 UE上下文也不会被删除。
在 2G/3G网络与 LTE网络共存的场景下, SGW ( Serving Gateway, 服务 网关)收到下行数据或者信令时,如果 ISR机制激活, SGW向 MME和 SGSN 同时发生 DDN(Downlink Data Notification, 下行数据通知)消息, SGSN 和 MME会同时寻呼 UE。
若 UE驻留在 LTE网络, 则网络侧会根据 MME上保存的 UE的上下文
建立相应的承载; 若 UE驻留在 2G/3G网络, 则网络侧会根据 SGSN上保存 的 UE的上下文建立相应的 7 载。
发明人发现现有技术至少存在以下问题:
UE在 ISR机制激活的状态下, 发生无线接入类型变化后, 网络侧对 UE 进行寻呼可能会导致部分承载丟失或者建立了两端承载上下文信息不一致的 承载, 严重影响业务的正常使用, 造成不良的用户体验。 发明内容
本发明实施例提供了一种处理寻呼的方法、 用户设备和系统, 用以解决 UE在 ISR机制激活的状态下, 发生无线接入类型变化后, 网络侧对 UE进行 寻呼可能会导致部分承载丟失或者建立了两端承载上下文信息不一致的承载 的问题。
本发明实施例提供了一种处理寻呼的方法, 包括:
用户设备接收移动性管理网元发送的寻呼消息;
该用户设备根据用于下次更新的临时标识( TIN )的值发送位置更新消息; 该移动性管理网元接收位置更新消息, 获取该用户设备的承载上下文信 息。
本发明实施例还提供了一种用户设备, 包括:
接收模块, 用于接收移动性管理网元发送的寻呼消息;
发送模块, 用于, 在接收移动性管理网元发送的寻呼消息后, 根据 TIN 的值发送位置更新消息至移动性管理网元, 便于该移动性管理网元获取用户 设备的承载上下文信息。
本发明实施例还提供了一种处理寻呼的系统, 包括: 移动性管理网元和 用户设备;
该移动性管理网元, 用于发送寻呼消息至该用户设备, 在接收到该用户 设备发送的位置更新消息后, 获取该用户设备的承载上下文信息;
该用户设备, 用于接收该移动性管理网元发送的寻呼消息, 根据 TIN的 值发送位置更新消息至该移动性管理网元。
本发明实施例在用户设备收到网络侧发来的寻呼消息后, 通过判断用户 设备上的 TIN的值来发送位置更新消息, 移动性管理网元收到位置更新消息 后获取用户设备的承载上下文信息, 可以实现网络侧的移动性管理网元上的 承载上下文信息与用户设备上的承载上下文信息保持一致, 进而能够克服在 寻呼过程中丟失部分承载或者建立了两端承载上下文信息不一致的承载的问 题, 保障了业务的正常使用, 提高了用户体验。 附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案, 下面将对实 施例或现有技术描述中所需要使用的附图作简单地介绍, 显而易见地, 下面 描述中的附图仅仅是本发明的一些实施例, 对于本领域普通技术人员来讲, 在不付出创造性劳动性的前提下, 还可以根据这些附图获得其他的附图。
图 1为当前无线演进网络架构图;
图 2为本发明实施例提供的第一种状态图;
图 3为本发明实施例提供的第一种方法的流程示意图;
图 4为本发明实施例提供的第二种方法的流程示意图;
图 5为本发明实施例提供的第二种状态图;
图 6为本发明实施例提供的第三种方法的流程示意图;
图 7为本发明实施例提供的第四种方法的流程示意图;
图 8为本发明实施例提供的第三种状态图;
图 9为本发明实施例提供的第五种方法的流程示意图;
图 10为本发明实施例提供的一种装置的结构示意图;
图 11为本发明实施例提供的一种系统的结构示意图。
具体实施方式
下面将结合本发明实施例中的附图, 对本发明实施例中的技术方案进行 清楚、 完整地描述, 显然, 所描述的实施例仅仅是本发明一部分实施例, 而 不是全部的实施例。 基于本发明中的实施例, 本领域普通技术人员在没有付 出创造性劳动前提下所获得的所有其他实施例, 都属于本发明保护的范围。
GSM ( Global System of Mobile communication, 全球移动通信系统) /UMTS ( Universal Mobile Telecommunications System, 通用移动通信系统) 是 3GPP组织定义的移动通信网络, 这种通信网络现在已经得到了广泛的部 署和应用。
它主要包括无线接入网络( Radio Access Network, 简称: RAN )和核心 网络(Core Network, 简称: CN ) 两部分。 CN从逻辑上可以分为电路交换 域( Circuit Switched Domain, 简称: CS域)和分组交换域 ( Packet Switched Domain, 简称: PS域)。 CS域主要处理语音业务, PS域主要处理分组业务。
PS域的信令面控制实体为 SGSN ( Serving GPRS Support Node, 服务 GPRS支持节点)。 SGSN通过 Gb接口和 BSC ( Base Station Controller, 基站 控制器)连接, 通过 Iu接口和 RNC ( Radio Network Controller, 无线网络控 制器)连接, 为 GPRS ( General Packet Radio Service , 通用分组无线服务技 术) /UMTS的数据业务服务。 UE通过 BSC的 Gb接口接入 SGSN完成 PS 业务时一般称之为 GPRS业务; UE通过 RNC的 Iu接口接入 SGSN完成 PS 业务时一般称之为 UMTS业务。
为了应对无线宽带技术的挑战,保持 3GPP网络的领先优势, 3GPP组织 制定了长期演进计划 ( Long Term Evolution, 简称: LTE )。 在该演进计划的 指导下定义了新的移动通信网络的架构, 该架构与现在的 GPRS/UMTS架构 相比更加扁平,并且只保留了分组域,因此可以称为演进的分组网络(evolved packet system, 简称: EPS )。
网络从 2G/3G 网络向 LTE网络演进的过程中, 在一定时期内, 会存在
2G/3G网络与 LTE网络并存的场景。 图 1是当前无线演进网络架构图。
如图 1所示, BTS ( Base Transceiver Station, 基站^:发台 )和 BSC构成 了 2G网络的无线接入部分,称为 GERAN( GSM EDGE Radio Access Network, GSM/EDGE无线接入网)。
NodeB (节点 B )和 RNC构成了 3G网络的无线接入部分,称为 UTRAN ( UTMS Terrestrial Radio Access Network,UMTS陆地无线接入网)。
LTE网络由 eNodeB(evolved NodeB,演进的节点 B)、MME、SGW( Serving Gateway,服务网关)和 PGW ( PDN Gateway, 分组数据网络网关)构成。 其 中 eNodeB构成了 LTE网络的无线接入部分,称为 E-UTRAN( Evolved UTMS Terretrial Radio Access Network,演进的 UMTS陆地无线接入网)。 eNodeB的主 要功能包括: 实现无线资源管理功能; IP 头压缩及用户数据流加密; UE 附 着时的 MME选择; 寻呼信息的调度传输; 广播信息的调度传输; 以及设置 和提供 eNodeB的测量等。
图 1所示的无线演进网络架构图中的核心网主要包含以下网元 SGSN、 MME、 SGW和 PGW其中, SGSN支持 GTPv2 ( GPRS Tunnelling Protocol Version 2, GPRS隧道协议第二版), 是 2G/3G网络的移动管理网元, 实现对 2G/3G 网络用户的用户上下文的管理等功能, MME是移动管理实体, 负责 NAS ( Non- Access-Stratum, 非接入层)信令和 NAS信令加密以及漫游、 跟 踪等功能, 分配用户临时身份标识、 安全功能等, 它对应于当前 UMTS系统 内部 SGSN的控制平面部分。 SGW负责本地的移动性锚点和 3GPP系统内部 的移动性锚点以及合法监听相关信息; PGW则负责策略执行和计费以及合法 监听相关功能。
用户设备可以在该架构下接入不同的网络,例如: UE1接入到 LTE网络, UE2接入到 3G网络, UE3接入到 2G网络。 SGSN与 MME之间的 S3接口 用于用户设备在 2G/3G网络与 LTE网络之间移动时,进行用户上下文的发送 等功能。
在上述无线演进网络架构中, 如图 2所示, MME与 SGSN分别与 SGW 相连, MME与 SGSN相连;
1 )假设初始状态, UE在 MME下接入并建立承载 A,并激活 ISR机制。 如图 2的状态 0所示, 此时, UE在 MME侧,
UE上保留有承载 A的上下文信息;
MME上保留有承载 A的上下文信息。
2 ) UE从 LTE网络移动到 2G/3G网络, SGSN从 MME侧取得 UE的最 新的上下文信息(包含承载 A的上下文信息),UE在 SGSN侧又建立承载 B。 此时, 为了能够在以后的无线接入类型切换后发起 TAU流程,保持 SGSN与 MME上的该 UE的上下文信息一致, UE本地的 TIN的值会设置为 P-TMSL 如图 2的状态 1所示, 此时, UE在 SGSN侧,
UE上保留有承载 A和承载 B的上下文信息;
MME上保留有承载 A的上下文信息;
SGSN上保留有承载 A和承载 B的上下文信息。
3 ) UE从 2G/3G网络移动到 LTE网络, 由于 UE本地的 ISR机制被去激 活, UE会向 MME发送 TAU消息来同步上下文信息, 若 MME此时处于过 载状态, MME将拒绝该 TAU流程, MME会向 UE发送 TAU Reject ( TAU 拒绝) 消息, 并且在 TAU Reject消息中携带移动管理推迟定时器(Mobility Management back-off timer )的值, UE收到该移动管理推迟定时器的值之后, 将启动 UE本地的移动管理推迟定时器, 在本地的移动管理推迟定时器的运 行期间, UE暂时不发起 TAU流程。
上述 MME过载时的处理方式是一种 NAS层的拥塞处理机制。 在 MME 出现过载时, MME可能会拒绝 UE发送的 MM ( Mobility Management, 移动 管理)请求消息, 当 NAS请求消息(例如: TAU消息)被拒绝时, MME会 发送一个移动管理推迟定时器的值给 UE, UE会启动本地的移动管理推迟定 时器,在该移动管理推迟定时器运行期间, UE不会发起任何的 NAS请求(除
了服务用户、 紧急业务和被叫业务), 从而可以在网络出现过载的情况下减少
UE对网络造成的沖击。
如图 2的状态 2所示, 此时, UE在 MME侧,
UE上保留有承载 A和承载 B的上下文信息;
MME上保留有承载 A的上下文信息;
SGSN上保留有承载 A和承载 B的上下文信息。
类似的, UE从 2G/3G网络移动到 LTE网络前, 向 SGSN发起 RAU流 程, 若 SGSN处于过载状态, 将拒绝 UE发起的 RAU消息, SGSN在给 UE 发送的 RAU Reject ( RAU拒绝) 消息中包含移动管理推迟定时器的值, UE 收到后启动本地的移动管理推迟定时器, 在该移动管理推迟定时器运行期间 不会发送 NAS消息 (除了服务用户、 紧急业务和被叫业务)。 在该移动管理 推迟定时器运行期间, UE从 2G/3G网络移动到 LTE网络, 由于移动管理推 迟定时器在当前的协议中与 RAT无关, 所以 UE移动到 LTE网络后, UE本 地的移动管理推迟定时器仍然处于运行状态, 由于此时 UE上的 TIN的值被 设置为 P-TMSI, UE需要发起 TAU流程, 但是由于 UE本地的移动管理推迟 定时器仍然处于运行状态, 所以 UE暂时不发起 TAU流程。 该场景也会造成 MME与 SGSN保留有的承载上下文信息不匹配。
本领域普通技术人员可以理解, 在其他情形下也有可能导致 2G/3G网络 和 LTE网络所保留的承载上下文信息不一致, 例如: 网络侧为了限制部分的 用户接入, 可以通过广播消息发送限制接入的设备类型表, 这些类型的设备 在移动到受限接入的网络下时, 不会主动发起 TAU消息, 但是可以接收被叫 业务的场景。
4 ) SGW收到 Create Bearer Request (创建 载请求) 消息后, 由于 UE 没有处于连接态, 因此, 网络侧需要寻呼 UE, 使 UE处于连接态, 再执行新 的承载建立的流程。
SGW向 MME和 SGSN发送 DDN消息, 引发 SGSN和 MME同时寻呼
UE。此时, UE在 MME侧, UE收到 MME发送寻呼消息后, UE发送 Service Request (服务请求) 消息给 MME。
MME收到 Service Request消息后, MME向 eNodeB发送 Initial Context Setup Request (初始上下文建立请求)消息, 该消息中携带 MME上的承载信 息。 通常, 承载信息包括 Bearer ID (承载标识)等, 如果有多个承载, 携带 的消息中将包含一个承载信息列表, 该列表中包含各个承载的信息。 此时, MME上的承载信息仅包括承载 A的 Bearer ID。
eNodeB将收到的 Bearer ID等信息通知给 UE建立无线接入承载, 如果 eNodeB通知给 UE的 Bearer ID在 UE本地的不存在, 该 Bearer ID对应的无 线接入承载将建立失败, 如果 UE本地的 Bearer ID没有包含在 eNodeB请求 UE建立无线接入承载的 Bearer ID列表中, UE本地将删除该 Bearer ID对应 的承载上下文信息。 由于 UE本地的承载 B的 Bearer ID没有包含在 eNodeB 请求 UE建立无线接入承载的 Bearer ID列表中, UE本地将删除承载 B的上 下文信息。
UE与 eNodeB之间的无线接入承载建立后, eNodeB向 MME发送 Initial Context Setup Response (初始上下文建立响应) 消息, MME向 SGW发送 Modify Bearer Request( 爹改 载清求)消息, SGW向 MME发送 Modify Bearer Response( 爹改 载响应)消息, SGW收到 MME发送的 Modify Bearer Request 消息后, SGW可以获知 UE驻留在 MME侧, SGW向 SGSN发送 Stop Paging 消息, 停止 SGSN再寻呼 UE。
至此, 整个寻呼过程完成, UE 处于连接态。 寻呼过程完成后, 执行建 立新的承载的流程, 新建的承载为承载 C。
本领域的普通技术人员可以理解, 还有其他情况可以引发网络侧向 UE 发起寻呼, 例如收到修改承载请求, 收到下行数据包等。
如图 2的状态 3所示, 此时, UE在 MME侧,
UE上保留有承载 A和承载 C的上下文信息;
MME上保留有承载 A和承载 C的上下文信息;
SGSN上保留有承载 A和承载 B的上下文信息。
可见, UE上原先的承载 B的上下文信息丟失。
可以预见, 当 UE上的移动管理推迟定时器超时, UE向 MME发起 TAU 流程, MME向 SGSN请求最新的上下文信息, MME上的上下文信息更新为 承载 A和承载 B的上下文信息。
随后, UE因为进行其他业务, 发起 Service Request流程, MME会删除 UE上没有的承载 B的上下文信息, UE会删除 MME上没有的承载 C的上下 文信息, 导致 UE和 MME上仅有承载 A的上下文信息。
上述的过程中,由于在步骤 4 )中,网络侧寻呼 UE时, MME没有从 SGSN 上获取承载上下文信息, 造成 UE与 MME的承载上下文信息不一致, 导致 部分承载丟失, 严重影响了业务的正常使用, 造成不良的用户体验。
本领域普通技术人员可以理解, 假设在步骤 2 ), UE没有在 SGSN侧建 立新的 7 载 B, 而是^ ί'爹改了 7 载 Α的上下文信息, 回到 MME侧后, 也有可 能在寻呼过程中, 因为 MME上的承载 A的上下文信息与 UE上的承载 A的 上下文信息不一致,而导致建立起来的承载 A两端的承载上下文信息不一致, 造成承载 A上的业务发生紊乱(例如: 发生业务质量问题或者数据包过滤问 题)。
本领域普通技术人员可以理解, 假设初始状态, UE在 SGSN下接入并 激活 ISR机制的状态下, 经过网络切换以及承载上下文信息变化后, 也有可 能当网络侧寻呼 UE时, SGSN没有从 MME上获取承载上下文信息, 造成 UE与 SGSN上的承载上下文信息不一致,导致部分承载丟失或者建立了两端 承载上下文信息不一致的承载的问题。
本领域普通技术人员可以理解, 当前的无线演进网络架构中包含 LTE网 络与 2G/3G网络, 随着网络架构的发展, 可能出现更多网络并存的场景, UE 可能会在三种甚至更多种的移动性管理网元之间进行切换, 同样可能会发生
当网络侧寻呼 UE时, 部分承载丟失或者建立了两端承载上下文信息不一致 的承载的问题。
为解决上述问题, 如图 3所示, 本发明实施例提供了一种处理寻呼的方 法, 包括:
101 : 用户设备接收移动性管理网元发送的寻呼消息;
102: 该用户设备根据 TIN的值发送位置更新消息;
分组临时移动用户标识)、 GUTI ( Globally Unique Temporary Identity, 全球唯 一临时标识)或 RAT-Related TMSI ( Radio Access Type Related Temporary Mobile Subscriber Indentity, 无线接入类型相关的临时移动用户标识)。
TIN的值为 P-TMSI,表明用户设备在 SGSN侧时承载上下文信息发生了 变化; TIN的值为 GUTI, 表明用户设备在 MME侧时承载上下文信息发生了 变化; TIN的值为 RAT-Related TMSI, 表明用户设备的上下文信息没有发生 变化。
可见, TIN的值反映了用户设备的承载上下文信息的变化情况。 例如: 用户设备在 SGSN侧新建了承载后,用户设备的 TIN的值被设置为 P-TMSI, 表明用户设备的承载上下文信息在 SGSN侧发生了变化, 当用户设备移动到 MME侧后, 发起 TAU流程, MME从 SGSN获取承载上下文信息后, 用户 设备的 TIN的值会被设置为 RAT-Related TMSI,表明当前 MME、 SGSN, UE 上的承载上下文信息一致, 没有发生变化。
本领域普通技术人员可以理解, 随着技术的发展, TIN可能还会有其他 的取值, 可以用来表示在不同的网络侧发生了承载上下文信息的变化。
用户设备根据 TIN的值发送位置更新消息, 移动性管理网元收到该位置 更新消息后会获取承载上下文信息, 即用户设备通过判断 TIN的取值, 可以
获知承载上下文信息在哪个网络侧发生了变化, 通过发送位置更新消息给当 前用户设备所在的网络侧的移动性管理网元, 以便移动性管理网元向发生承 载上下文信息变化的网络侧的移动性管理网元获取 载上下文信息。
当用户设备根据 TIN的值来发送位置更新消息, 所在网络侧的移动性管 理网元从发生承载上下文信息变化的网络侧的移动性管理网元获取承载上下 文信息后, 用户设备上的承载上下文信息与用户设备所在的网络侧的移动性 管理网元上的承载上下文信息保持一致, 因此, 在寻呼过程中, 不会丟失承 载, 保障了业务的正常使用, 提高了用户的体验。
本领域普通技术人员可以理解, 在当前无线网络演进架构中, 当 TIN的 值为 RAT-Related TMSI时, 用户设备无需发送位置更新消息, 用户设备将直 接发起 Service Request流程。
本领域普通技术人员可以理解, 在当前无线网络演进架构中, 根据 TIN 的值发送位置更新消息存在两种情况, 下面进行分别说明。
情况一:
假设用户设备在 MME侧, 如图 4所示, 本发明实施例提供的方法可以 具体为:
201 : 用户设备接收 MME发送的寻呼消息;
202:该用户设备的 TIN的值为 P-TMSI时,该用户设备发送 TAU消息; 203: 该 MME接收 TAU消息, 从 SGSN获取用户设备的承载上下文信 息。
当用户设备接收到 MME 发送的寻呼消息后, 通过判断 TIN 的值为 P-TMSI, 获知承载上下文信息在 SGSN侧发生了变化, 用户设备需要发送位 置更新消息, 因此用户设备发送 TAU消息。 其中, TAU消息是位置更新消息 的一种, MME收到 TAU消息后, 会从 SGSN获取用户设备的承载上下文信 息。
一般的, 在寻呼过程中, 发送 TAU消息后, 用户设备不再发送 Service
Requestc
为了说明本发明实施例提供的方法的技术效果, 下面结合图 5进行说明。 图 5是当 UE在 MME侧, 使用本发明实施例提供的方法后的状态图, 为了 说明本发明实施例的技术效果, 图 5只显示寻呼发生前的状态 2,和寻呼发生后 的状态 3', 如图 5所示:
图 5的状态 2,类似图 2的状态 2, 此时, UE在 MME侧, UE上的移动管理推 迟定时器处于运行状态,
UE上保留有承载 A和承载 B的上下文信息;
MME上保留有承载 A的上下文信息;
SGSN上保有有承载 A和承载 B的上下文信息。
此时, 网络侧发起寻呼, UE收到 MME发送的寻呼请求后, 判断自身的 TIN的值为 P-TMSI后, 发送 TAU消息, MME收到 TAU消息后从 SGSN获取承 载上下文信息。
如图 5的状态 3,所示, 此时, UE在 MME侧,
UE上保留有承载 A和承载 B的上下文信息;
MME上保留有承载 A和承载 B的上下信息;
SGSN上保留有承载 A和承载 B的上下文信息。
可见, 使用了本发明实施例提供的方法后, UE通过判断自身的 TIN的值 为 P-TMSI, 获知承载上下文信息在 SGSN侧发生了变化, 因此 UE发送 TALK' 息, MME收到 TAU消息后, MME从 SGSN上获取承载上下文信息, 由于 MME 上的承载上下文信息与 UE上的承载上下文信息一致,因此 UE上的承载 B的上 下文信息不会在 MME寻呼 UE的过程中被删除, 即承载 B不会丟失, 保障了业 务的正常使用, 提高了用户体验。
进一步的, 步骤 202可以具体为:
当用户设备的移动管理推迟定时器处于运行态且用户设备的 TIN的值为 P-TMSI, 该用户设备发送 TAU消息。
其中,移动管理推迟定时器处于运行态表明用户设备不会主动发送 TAU 消息。
下面将在具体场景中, 对上述本发明实施例提供的方法作进一步的举例 说明。 如图 6所示, 图 6描述了 UE初始驻留在 MME侧并激活 ISR机制的 场景, 在该场景下, UE从 LTE网络移动到 2G/3G网络, 并在 2G/3G网络建 立新的 载, 然后, UE从 2G/3G网络回到 LTE网络, UE向 MME发起 TAU 流程时由于 MME过载而被拒绝, 并且 UE启动移动管理推迟定时器, UE在 该定时器运行期间不能主动发送 NAS消息, 但可以接受被叫业务, 在 UE收 到 MME发送的寻呼时, UE判断其内部的 TIN的值为 P-TMSI后发送 TAU 消息, MME收到 TAU消息后, MME从 SGSN获取 UE的承载上下文信息。 具体如下:
300a: UE向 MME发起附着流程,接入到 LTE网络,并激活 ISR机制; 即, UE在 MME侧。
300b: UE从 LTE网络移动到 2G/3G网络;
即, UE移动到 SGSN侧。
300c: UE在 2G/3G网络下建立新的承载;
其中, UE将 TIN设置为 P-TMSL
300d: UE从 2G/3G网络移动到 LTE网络;
即, UE移动到 MME侧。
301 : UE向 MME发送跟踪区更新 ( TAU ) 消息;
因为 UE在 SGSN下建立了新的 载, 因此 UE移动到 MME侧后, 需 要向 MME发送 TAU消息, 以便 MME从 SGSN获取承载上下文信息。
302: 由于 MME过载, MME向 UE发送跟踪区更新拒绝( TAU Reject ) 消息;
其中, TAU Reject消息中包含了移动管理推迟定时器时间。 UE收到 MME 发送的包含移动管理推迟定时器时间的 TAU Reject消息后启动自身的移动管
理推迟定时器,在该定时器未超时的情况下, UE不会主动发送 NAS消息(除 了服务用户、 紧急业务和被叫业务)。 此时, UE与 MME上的承载上下文信 息出现了不一致的情况。
303: PGW收到向该 UE发送的下行数据包后, PGW将该下行数据包发 送给 SGW;
本领域普通技术人员可以理解, 还有其他方式可以引发网络侧向 UE发 起寻呼, 例如接收到新建承载请求或者接收到修改承载请求等。
304: SGW分别向 MME和 SGSN发送下行数据通知( DDN ) 消息; 305: MME和 SGSN分别向 SGW发送下行数据通知应答 ( DDN Ack ) 消息;
306a: MME向 eNodeB发送寻呼消息;
306b: SGSN向 RNC/BSC发送寻呼消息;
307a: eNodeB向 UE发送寻呼消息;
308a: RNC/BSC向 UE发送寻呼消息;
309: UE向 MME发送跟踪区更新消息;
UE此时在 MME侧, UE接收到 eNodeB发送的寻呼消息后, 判断 TIN 的值为 P-TMSI, 获知了承载上下文信息在 SGSN侧发生了变化, 因此 UE发 送 TAU消息, MME收到 TAU消息后, MME从 SGSN上获取承载上下文信 息。
可选的, UE也可以同时判断移动管理推迟定时器是否处于运行态, 当 移动管理推迟定时器处于运行态且 TIN的值为 P-TMSI时, 发送 TAU消息。
310: MME向 SGSN发送上下文请求( Context Request ) 消息;
311 : SGSN向 MME发送上下文响应 ( Context Response ) 消息; 此时, MME已经从 SGSN上获取了承载上下文信息。此时, UE与 MME 上的承载上下文信息保持了一致。
312: MME向 SGW发送修改承载请求( Modify Bearer Request ) 消息;
313: SGW向 MME发送修改承载响应( Modify Bearer Response )消息; 此时, UE与 eNodeB之间的无线承载已经建立, 由于 UE与 MME上的 承载上下文信息一致, 因此在此过程中, 不会出现部分承载丟失的情况。
314: MME向 UE发送跟踪区更新接受 ( TAU Accept ) 消息。
上下行通道打通后, 对于下行的数据包就可以从 SGW发送到 UE。
同样的,如果是新建承载请求或者修改承载请求引发的寻呼,在 TAU流 程结束后, 上下行通道(例如无线侧的连接)建立后, 就继续进行新建承载 请求流程或者修改承载请求流程。
在本场景下, UE在收到 MME发来的寻呼后, 通过判断自身的 TIN的 值为 P-TMSI,获知了承载上下文在 SGSN侧发生了变化, 因此 UE发送 TAU 消息, MME收到 TAU消息后,从 SGSN上获取承载上下文信息, 由于 MME 上的承载上下文信息与 UE上的承载上下文信息一致, 在寻呼过程中, 不会 造成部分承载的丟失, 保障了业务的正常使用, 提高了用户体验。
情况二:
假设用户设备在 SGSN侧, 如图 7所示, 本发明实施例提供的方法可以 具体为:
401 : 用户设备接收 SGSN发送的寻呼消息;
402: 该用户设备的 TIN的值为 GUTI时, 该用户设备发送 RAU消息; 403: 该 SGSN接收 RAU消息, 从 MME获取用户设备的承载上下文信 息。
当用户设备接收到 SGSN发送的寻呼消息后,通过判断 TIN的值为 GUTI, 获知承载上下文信息在 MME侧发生了变化, 用户设备需要发送位置更新消 息, 因此用户设备发送 RAU消息。其中, RAU消息是位置更新消息的一种, SGSN收到 RAU消息后, SGSN会从 MME获取承载上下文信息。
一般的, 在寻呼过程中, 发送 RAU消息后, 用户设备不再发送 Service Requestc
为了说明本发明实施例提供的方法的技术效果,下面结合图 8进行说明。 图 8是当 UE在 SGSN侧, 使用本发明实施例提供的方法后的状态图, 为了说明本发明实施例的技术效果, 图 8只显示寻呼发生前的状态 2"和寻呼 发生后的状态 3", 如图 8所示:
图 8的状态 2"H没如下: UE在 SGSN侧, UE上的移动管理推迟定时 器处于运行夫态,
UE上保留有承载 A和承载 B的上下文信息;
MME上保留有承载 A和承载 B的上下文信息;
SGSN上保有有承载 A的上下文信息。
此时, 网络侧发起寻呼, UE收到 SGSN发送的寻呼请求后, 判断自身 的 TIN的值为 GUIT后, 发送 RAU消息, SGSN收到 RAU消息后从 MME 获取承载上下文信息。
如图 8的状态 3"所示, 此时, UE在 SGSN侧,
UE上保留有承载 A和承载 B的上下文信息;
MME上保留有承载 A和承载 B的上下信息;
SGSN上保留有承载 A和承载 B的上下文信息。
可见, 使用了本发明实施例提供的方法后, UE通过判断自身的 TIN的 值为 GUTI,获知承载上下文信息在 MME侧发生了变化, 因此 UE发送 RAU 消息, SGSN从 MME上获取用户设备的承载上下文信息, 由于 SGSN上的 承载上下文信息与 UE上的承载上下文信息一致,因此 UE上的承载 B的上下 文信息不会在 SGSN寻呼 UE的过程中被删除, 即承载 B不会丟失, 保障了 业务的正常使用, 提高了用户体验。
进一步的, 步骤 402可以具体为:
当用户设备的移动管理推迟定时器处于运行态且用户设备的 TIN的值为 GUTI, 该用户设备发送 RAU消息。
其中,移动管理推迟定时器处于运行态表明用户设备不会主动发送 RAU
消息。
下面将在具体场景中, 对上述本发明实施例提供的方法作进一步的举例 说明。 如图 9所示, 图 9描述了 UE初始驻留在 SGSN侧并激活 ISR机制的 场景, 在该场景下, UE从 2G/3G网络移动到 LTE网络, 并在 LTE网络建立 新的承载, 然后, UE从 LTE网络回到 2G/3G网络, UE向 SGSN发起 RAU 流程时由于 SGSN过载而被拒绝, 并且 UE启动移动管理推迟定时器, UE在 该定时器运行期间不能主动发送 NAS消息, 但可以接受被叫业务, 在 UE收 到 SGSN发送的寻呼时, UE判断其内部的 TIN的值为 GUIT后发送 RAU消 息, SGSN收到 RAU消息后, 会从 MME获取 UE的承载上下文信息。 具体 ^口下:
500a: UE向 SGSN发起附着流程, 接入到 2G/3G网络, 并激活 ISR机 制;
即, UE在 SGSN侧。
500b: UE从 2G/3G网络移动到 LTE网络;
即, UE移动到 MME侧。
500c: UE在 LTE网络下建立新的承载;
其中, UE将 TIN设置为 GUTI。
500d: UE从 LTE网络移动到 2G/3G网络;
即, UE移动到 SGSN侧。
501 : UE向 SGSN发送路由区更新 ( RAU ) 消息;
因为 UE在 MME下建立了新的 载, 因此 UE移动到 SGSN侧后, 需 要向 MME发送 RAU消息, SGSN收到 RAU消息后会从 MME获取承载上 下文信息。
502:由于 SGSN过载, SGSN向 UE发送路由区更新拒绝( RAU Reject ) 消息;
其中, RAU Reject消息中包含了移动管理推迟定时器时间。 UE收到 MME
发送的包含移动管理推迟定时器时间的 RAU Reject消息后启动自身的移动管 理推迟定时器,在该定时器未超时的情况下, UE不会主动发送 NAS消息(除 了服务用户、 紧急业务和被叫业务)。 此时, UE与 SGSN上的承载上下文信 息出现了不一致的情况。
503: PGW收到向该 UE发送的下行数据包后, PGW将该下行数据包发 送给 SGW;
本领域普通技术人员可以理解, 还有其他方式可以引发网络侧向 UE发 起寻呼, 例如接收到新建承载请求或者接收到修改承载请求等。
504: SGW分别向 MME和 SGSN发送下行数据通知( DDN ) 消息; 505: MME和 SGSN分别向 SGW发送下行数据通知应答 ( DDN Ack ) 消息;
506a: MME向 eNodeB发送寻呼消息;
506b: SGSN向 RNC/BSC发送寻呼消息;
507a: eNodeB向 UE发送寻呼消息;
508a: RNC/BSC向 UE发送寻呼消息;
509: UE向 SGSN发送路由区更新 ( RAU ) 消息;
UE此时在 SGSN侧, UE接收到 RNC/BSC发送的寻呼消息后,判断 TIN 的值为 GUTI,获知了承载上下文信息在 MME侧发生了变化,因此发送 RAU 消息, SGSN收到 RAU消息后会从 MME上获取承载上下文信息。
可选的, UE也可以同时判断移动管理推迟定时器是否处于运行态, 当 移动管理推迟定时器处于运行态且 TIN的值为 GUTI时, 发送 RAU消息。
510: SGSN向 MME发送上下文请求( Context Request ) 消息;
511 : MME向 SGSN发送上下文响应 ( Context Response ) 消息; 此时, SGSN已经从 MME上获取了承载上下文信息。此时, UE与 SGSN 上的承载上下文信息保持了一致。
512: SGSN向 SGW发送修改承载请求( Modify Bearer Request ) 消息;
513: SGW向 SGSN发送修改承载响应( Modify Bearer Response )消息; 此时, UE与 RNC/BSC之间的无线承载已经建立, 由于 UE与 SGSN上 的承载上下文信息一致, 因此在此过程中, 不会出现部分承载丟失的情况。
514: SGSN向 UE发送路由区更新接受 ( RAU Accept ) 消息。
上下行通道打通后, 下行数据包就能够从 SGW发送至 UE。
同样的, 如果是新建承载请求或者修改承载请求引发的寻呼, 在 RAU 流程结束后, 上下行通道(例如无线侧的连接)建立后, 就继续进行新建承 载请求流程或者修改承载请求流程。
在本场景下, UE在收到 SGSN发来的寻呼后, 通过判断自身的 TIN的 值为 GUTI, 获知了承载上下文在 MME侧发生了变化, 因此 UE发送 RAU 消息, SGSN收到 RAU消息后,从 MME上获取承载上下文信息,由于 SGSN 上的承载上下文信息与 UE上的承载上下文信息一致, 在寻呼过程中, 不会 造成部分承载的丟失, 保障了业务的正常使用, 提高了用户体验。 如图 10所示, 本发明实施例还提供了一种用户设备, 包括:
接收模块 601, 用于接收移动性管理网元发送的寻呼消息;
发送模块 602, 用于, 在接收移动性管理网元发送的寻呼消息后, 根据
TIN 的值发送位置更新消息至移动性管理网元, 便于该移动性管理网元获取 用户设备的承载上下文信息。
本发明实施例提供的用户设备在收到移动性管理网元发送的寻呼消息后, 根据自身的 TIN的值来发送位置更新消息至移动性管理网元, 移动性管理网 元收到位置更新消息后会获取用户设备的承载上下文信息。
可选的,
接收模块 601, 具体用于接收 MME发送的寻呼消息;
发送模块 602, 具体用于, 在接收 MME发送的寻呼消息后, 当 TIN的 值为 P-TMSI时, 发送 TAU消息至 MME, 便于 MME从 SGSN获取用户设
备的承载上下文信息。
其中, 进一步的, 发送模块 602, 具体用于, 在接收 MME发送的寻呼 消息后, 当移动管理推迟定时器处于运行态且 TIN的值为 P-TMSI时, 发送 TAU消息至 MME。
本发明实施例提供的用户设备在收到 MME发送的寻呼消息后, 当 TIN 的值为 P-TMSI时, 发送 TAU消息至 MME, MME收到 TAU消息后会获取 用户设备的承载上下文信息。
可选的,
接收模块 601, 具体用于接收 SGSN发送的寻呼消息;
发送模块 602, 具体用于, 在接收 SGSN发送的寻呼消息后, 当 TIN的 值为 GUTI时, 发送 RAU消息至 SGSN, 便于 SGSN从 MME获取用户设备 的承载上下文信息。
其中, 进一步的, 发送模块 602, 具体用于, 在接收 SGSN发送的寻呼 消息后,当移动管理推迟定时器处于运行态且 TIN的值为 GUTI时,发送 RAU 消息至 SGSN。
本发明实施例提供的用户设备在收到 SGSN发送的寻呼消息后, 当 TIN 的值为 GUTI时, 发送 RAU消息至 SGSN, SGSN收到 RAU消息后会获取 用户设备的承载上下文信息。
综上, 本发明实施例提供的用户设备, 通过接收到网络侧发来的寻呼消 息后, 通过判断用户设备上的 TIN的值来发送位置更新消息至移动性管理网 元,移动性管理网元接收到位置更新消息后获取用户设备的承载上下文信息, 可以实现用户设备所在的网络侧的移动性管理网元上的承载上下文信息与用 户设备上的承载上下文信息保持一致, 进而能够克服在寻呼过程中丟失部分 承载或者建立了两端承载上下文信息不一致的承载的问题, 保障了业务的正 常使用, 提高了用户体验。
如图 11所示, 本发明实施例还提供了一种处理寻呼的系统, 包括: 移动 性管理网元 701和用户设备 702;
该移动性管理网元, 用于发送寻呼消息至所述用户设备, 在接收到用户 设备发送的位置更新消息后, 获取该用户设备的承载上下文信息;
该用户设备, 用于接收该移动性管理网元发送的寻呼消息, 根据 TIN的 值发送位置更新消息至该移动性管理网元。
该移动性管理网元可以为 MME;
该 MME具体用于发送寻呼消息至该用户设备, 在接收到该用户设备发 送的 TAU消息后, 从 SGSN获取用户设备的承载上下文信息;
该用户设备, 具体用于接收该 MME发送的寻呼消息, 当 TIN 的值为 P-TMSI时, 发送 TAU消息至该 MME。
进一步的, 该用户设备, 具体用于接收该 MME发送的寻呼消息, 当移 动管理推迟定时器处于运行态且 TIN的值为 P-TMSI时,发送 TAU消息至该 MME。
该移动性管理网元可以为 SGSN;
该 SGSN具体用于发送寻呼消息至该用户设备, 在接收到该用户设备发 送的 RAU消息后, 从 MME获取该用户设备的承载上下文信息;
该用户设备, 具体用于接收该 SGSN发送的寻呼消息, 当 TIN 的值为 GUTI时, 发送 RAU消息至该 SGSN。
进一步的, 该用户设备, 具体用于, 接收该 SGSN发送的寻呼消息, 当 移动管理推迟定时器处于运行态且 TIN的值为 GUTI时,发送 RAU消息至该 SGSN。
本发明实施例提供的处理寻呼的系统通过接收到网络侧发来的寻呼消息 后, 通过判断用户设备上的 TIN的值来发送位置更新消息, 移动性管理网元 接收到位置更新消息后获取用户设备的承载上下文信息, 可以实现用户设备 所在的网络侧的移动性管理网元上的承载上下文信息与用户设备上的承载上
下文信息保持一致, 进而能够克服在寻呼过程中丟失部分承载或者建立了两 端承载上下文信息不一致的承载的问题, 保障了业务的正常使用, 提高了用 户体验。
本领域普通技术人员可以理解: 附图只是一个实施例的示意图, 附图中 的模块或流程并不一定是实施本发明所必须的。
本领域普通技术人员可以理解: 实施例中的用户设备中的模块可以按照 实施例描述分布于实施例的用户设备中, 也可以进行相应变化位于不同于本 实施例的一个或多个用户设备中。 上述实施例的模块可以合并为一个模块, 也可以进一步拆分成多个子模块。
本领域普通技术人员可以理解: 实现上述方法实施例的全部或部分步骤 可以通过程序指令相关的硬件来完成, 前述的程序可以存储于一计算机可读 取存储介质中, 该程序在执行时, 执行包括上述方法实施例的步骤; 而前述 的存储介质包括: ROM, RAM, 磁碟或者光盘等各种可以存储程序代码的介 质。
最后应说明的是: 以上实施例仅用以说明本发明的技术方案, 而非对其 限制; 尽管参照前述实施例对本发明进行了详细的说明, 本领域的普通技术 人员应当理解: 其依然可以对前述实施例所记载的技术方案进行 ^ί'爹改, 或者 对其中部分技术特征进行等同替换; 而这些修改或者替换, 并不使相应技术 方案的本质脱离本发明实施例技术方案的精神和范围。
Claims
1、 一种处理寻呼的方法, 其特征在于, 包括:
用户设备接收移动性管理网元发送的寻呼消息;
所述用户设备根据用于下次更新的临时标识( TIN )的值发送位置更新消 息;
所述移动性管理网元接收所述位置更新消息, 获取所述用户设备的承载 上下文信息。
2、 如权利要求 1所述的方法, 其特征在于,
所述用户设备接收移动性管理网元发送的寻呼消息, 包括:
用户设备接收移动管理实体(MME )发送的寻呼消息;
所述用户设备根据 TIN的值发送位置更新消息, 包括:
所述用户设备的 TIN的值为分组临时移动用户标识 (P-TMSI ) , 所述用 户设备发送跟踪区更新 (TAU ) 消息;
所述移动性管理网元接收所述位置更新消息, 获取所述用户设备的承载 上下文信息, 包括:
所述 MME接收所述 TAU消息,从服务通用分组无线业务支持节点( SGSN ) 获取所述用户设备的承载上下文信息。
3、 如权利要求 2所述的方法, 其特征在于,
所述用户设备的 TIN的值为 P-TMSI, 所述用户设备发送 TAU, 包括: 所述用户设备的移动管理推迟定时器处于运行态且所述用户设备的 TIN 的值为 P-TMSI, 所述用户设备发送 TAU消息。
4、 如权利要求 1所述的方法, 其特征在于,
所述用户设备接收移动性管理网元发送的寻呼消息, 包括:
用户设备接收 SGSN发送的寻呼消息;
所述用户设备根据 TIN的值发送位置更新消息, 包括:
所述用户设备的 TIN的值为全球唯一临时标识 (GUTI ) , 所述用户设备 发送路由区更新 (RAU ) 消息;
所述移动性管理网元获取所述用户设备的承载上下文信息, 包括: 所述 SGSN接收所述 RAU消息, 从 MME获取所述用户设备的承载上下文 信息。
5、 如权利要求 4所述的方法, 其特征在于,
所述用户设备的 TIN的值为 GUTI, 所述用户设备发送 RAU消息, 包括: 所述用户设备的移动管理推迟定时器处于运行态且所述用户设备的 TIN 的值为 GUTI, 所述用户设备发送 RAU消息。
6、 一种用户设备, 其特征在于, 包括:
接收模块, 用于接收移动性管理网元发送的寻呼消息;
发送模块, 用于, 在接收移动性管理网元发送的寻呼消息后, 根据 TIN 的值发送位置更新消息至所述移动性管理网元, 便于所述移动性管理网元获 取用户设备的承载上下文信息。
7、 如权利要求 6所述的用户设备, 其特征在于,
所述接收模块, 具体用于接收 MME发送的寻呼消息;
所述发送模块, 具体用于, 在接收 MME发送的寻呼消息后, 当 TIN的值 为 P-TMSI时,发送 TAU消息至所述 MME,便于所述 MME从 SGSN获取用户设 备的承载上下文信息。
8、 如权利要求 7所述的用户设备, 其特征在于,
所述发送模块, 具体用于, 在接收 MME发送的寻呼消息后, 当移动管理 推迟定时器处于运行态且 TIN的值为 P-TMSI时, 发送 TAU消息至所述 MME。
9、 如权利要求 6所述的用户设备, 其特征在于,
所述接收模块, 具体用于接收 SGSN发送的寻呼消息;
所述发送模块, 具体用于, 在接收 SGSN发送的寻呼消息后, 当 TIN的值 为 GUTI时, 发送 RAU消息至所述 SGSN, 便于所述 SGSN从 MME获取用户设 备的承载上下文信息。
10、 如权利要求 9所述的用户设备, 其特征在于,
所述发送模块, 具体用于, 在接收 SGSN发送的寻呼消息后, 当移动管理 推迟定时器处于运行态且 TIN的值为 GUTI时, 发送 RAU消息至所述 SGSN。
11、 一种处理寻呼的系统, 其特征在于, 包括: 移动性管理网元和用户 设备;
所述移动性管理网元, 用于发送寻呼消息至所述用户设备, 在接收到所 述用户设备发送的位置更新消息后, 获取所述用户设备的承载上下文信息; 所述用户设备,用于接收所述移动性管理网元发送的寻呼消息,根据 TIN 的值发送位置更新消息至所述移动性管理网元。
12、如权利要求 11所述的系统,其特征在于,所述移动性管理网元为 MME; 所述 MME, 具体用于发送寻呼消息至所述用户设备, 在接收到所述用户 设备发送的 TAU消息后, 从 SGSN获取用户设备的承载上下文信息;
所述用户设备, 具体用于接收所述 MME发送的寻呼消息, 当 TIN的值为 P-TMSI时, 发送 TAU消息至所述 MME。
13、 如权利要求 12所述的系统, 其特征在于,
所述用户设备, 具体用于, 接收所述 MME发送的寻呼消息, 当移动管理 推迟定时器处于运行态且 TIN的值为 P-TMSI时, 发送 TAU消息至所述 MME。
14、如权利要求 11所述的系统,其特征在于,所述移动性管理网元为 SGSN; 所述 SGSN, 具体用于发送寻呼消息至所述用户设备, 在接收到所述用户 设备发送的 RAU消息后, 从 MME获取所述用户设备的承载上下文信息;
所述用户设备, 具体用于接收所述 SGSN发送的寻呼消息, 当 TIN的值为 GUTI时, 发送 RAU消息至所述 SGSN。
15、 如权利要求 14所述的系统, 其特征在于,
所述用户设备, 具体用于, 接收所述 SGSN发送的寻呼消息, 当移动管理 推迟定时器处于运行态且 TIN的值为 GUTI时, 发送 RAU消息至所述 SGSN。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2011/077180 WO2012167478A1 (zh) | 2011-07-15 | 2011-07-15 | 处理寻呼的方法、用户设备和系统 |
EP11867314.4A EP2713640B1 (en) | 2011-07-15 | 2011-07-15 | Method, user equipment and system for processing paging |
CN201180001335.XA CN102986261B (zh) | 2011-07-15 | 2011-07-15 | 处理寻呼的方法、用户设备和系统 |
US14/155,942 US9491732B2 (en) | 2011-07-15 | 2014-01-15 | Paging processing method, user equipment and system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2011/077180 WO2012167478A1 (zh) | 2011-07-15 | 2011-07-15 | 处理寻呼的方法、用户设备和系统 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/155,942 Continuation US9491732B2 (en) | 2011-07-15 | 2014-01-15 | Paging processing method, user equipment and system |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2012167478A1 true WO2012167478A1 (zh) | 2012-12-13 |
Family
ID=47295368
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2011/077180 WO2012167478A1 (zh) | 2011-07-15 | 2011-07-15 | 处理寻呼的方法、用户设备和系统 |
Country Status (4)
Country | Link |
---|---|
US (1) | US9491732B2 (zh) |
EP (1) | EP2713640B1 (zh) |
CN (1) | CN102986261B (zh) |
WO (1) | WO2012167478A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
TWI682679B (zh) * | 2017-11-28 | 2020-01-11 | 新加坡商 聯發科技(新加坡)私人有限公司 | 行動管理擁塞控制方法及使用者設備 |
Families Citing this family (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2861038B1 (en) | 2012-06-29 | 2019-12-18 | Huawei Technologies Co., Ltd. | Information processing method, forwarding plane apparatus and control plane apparatus |
US9635702B2 (en) * | 2012-08-02 | 2017-04-25 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for reducing signaling in a core network |
CN105900504B (zh) * | 2014-01-13 | 2019-06-11 | Lg电子株式会社 | 下行链路数据传输方法和服务网关 |
WO2016000144A1 (zh) * | 2014-06-30 | 2016-01-07 | 华为技术有限公司 | 一种网络中的寻呼方法、装置和系统 |
WO2016032146A1 (ko) * | 2014-08-28 | 2016-03-03 | 엘지전자 주식회사 | 페이징 처리 방법 및 다운링크 데이터 전달 방법 |
KR101681624B1 (ko) * | 2014-12-22 | 2016-12-02 | 닛본 덴끼 가부시끼가이샤 | 이동 통신 시스템, sgw, 단말기, 이동 통신 시스템의 수신 방법, sgw 의 수신 방법, 및 단말기의 수신 방법 |
JP5896083B1 (ja) * | 2014-12-22 | 2016-03-30 | 日本電気株式会社 | 移動通信システム、sgw、移動通信システムの着信方法、及びsgwの着信方法 |
US9974049B2 (en) * | 2015-01-29 | 2018-05-15 | Intel IP Corporation | Adaptive paging techniques for extended coverage-capable devices |
KR20180019538A (ko) * | 2015-06-18 | 2018-02-26 | 소니 주식회사 | 시스템, 방법 및 단말 장치 |
EP3629669B1 (en) * | 2015-09-22 | 2022-11-02 | Huawei Technologies Co., Ltd. | Control method,local control-plane device, system and computer-readable storage medium for switching a user equipment from idle state to active state |
US10575278B2 (en) * | 2015-10-23 | 2020-02-25 | Lg Electronics Inc. | Method for controlling idle-mode signaling reduction of terminal in wireless communication system and apparatus for the same |
CN110149732B (zh) * | 2018-02-11 | 2021-12-31 | 华为技术有限公司 | 一种通信方法及无线通信装置 |
CN111526321B (zh) * | 2020-04-16 | 2021-04-23 | Oppo广东移动通信有限公司 | 语音通话方法、语音通话装置、存储介质与电子设备 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101296479A (zh) * | 2007-04-24 | 2008-10-29 | 华为技术有限公司 | 下行数据处理方法及通信系统 |
CN101360331A (zh) * | 2007-08-02 | 2009-02-04 | 华为技术有限公司 | 一种服务网关信息更新方法、系统及装置 |
CN101448320A (zh) * | 2008-03-26 | 2009-06-03 | 中兴通讯股份有限公司 | 注销网络方法及双模用户设备 |
CN101505474A (zh) * | 2008-02-04 | 2009-08-12 | 华为技术有限公司 | 用户切换过程中网络侧处理方法、网元设备及网络系统 |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040102199A1 (en) * | 2002-11-22 | 2004-05-27 | Serge Haumont | Paging area having multiple radio technologies |
CN101415175B (zh) * | 2007-10-16 | 2012-01-04 | 华为技术有限公司 | 一种双注册处理方法及装置 |
CN101500223B (zh) * | 2008-02-01 | 2012-08-29 | 华为技术有限公司 | 终端跨接入网元切换的方法及移动性管理网元 |
CN101282511B (zh) * | 2008-05-16 | 2011-07-13 | 中兴通讯股份有限公司 | 承载处理方法 |
CN101998590B (zh) * | 2009-08-25 | 2015-05-20 | 中兴通讯股份有限公司 | 一种用户可达的实现方法以及多模终端 |
CN102026143A (zh) * | 2009-09-23 | 2011-04-20 | 华为技术有限公司 | 实现空闲态节约信令的方法及设备 |
CN101969634B (zh) * | 2010-06-12 | 2014-09-10 | 中兴通讯股份有限公司 | 一种用户数据的同步方法和系统 |
JP5347009B2 (ja) * | 2010-11-04 | 2013-11-20 | 宏達國際電子股▲ふん▼有限公司 | タイマ設定方法及び関連する通信装置 |
KR101479895B1 (ko) * | 2011-04-29 | 2015-01-06 | 엘지전자 주식회사 | 세션 관리 및 이동성 관리에 관련된 데이터를 처리하는 방법 |
-
2011
- 2011-07-15 EP EP11867314.4A patent/EP2713640B1/en active Active
- 2011-07-15 CN CN201180001335.XA patent/CN102986261B/zh active Active
- 2011-07-15 WO PCT/CN2011/077180 patent/WO2012167478A1/zh active Application Filing
-
2014
- 2014-01-15 US US14/155,942 patent/US9491732B2/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101296479A (zh) * | 2007-04-24 | 2008-10-29 | 华为技术有限公司 | 下行数据处理方法及通信系统 |
CN101360331A (zh) * | 2007-08-02 | 2009-02-04 | 华为技术有限公司 | 一种服务网关信息更新方法、系统及装置 |
CN101505474A (zh) * | 2008-02-04 | 2009-08-12 | 华为技术有限公司 | 用户切换过程中网络侧处理方法、网元设备及网络系统 |
CN101448320A (zh) * | 2008-03-26 | 2009-06-03 | 中兴通讯股份有限公司 | 注销网络方法及双模用户设备 |
Non-Patent Citations (1)
Title |
---|
See also references of EP2713640A4 * |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
TWI682679B (zh) * | 2017-11-28 | 2020-01-11 | 新加坡商 聯發科技(新加坡)私人有限公司 | 行動管理擁塞控制方法及使用者設備 |
Also Published As
Publication number | Publication date |
---|---|
US9491732B2 (en) | 2016-11-08 |
CN102986261A (zh) | 2013-03-20 |
US20140128110A1 (en) | 2014-05-08 |
EP2713640A4 (en) | 2014-12-03 |
EP2713640A1 (en) | 2014-04-02 |
CN102986261B (zh) | 2015-11-25 |
EP2713640B1 (en) | 2019-08-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
RU2764259C1 (ru) | Способ для активизации или деактивизации соединения плоскости пользователя в каждом сеансе | |
JP6821821B2 (ja) | 要求に対する応答方法及びネットワーク装置 | |
US11218904B2 (en) | Method for applying reflective quality of service in wireless communication system, and device therefor | |
CN109155909B (zh) | 无线通信系统中用于更新ue配置的方法及其装置 | |
KR102287842B1 (ko) | 무선 통신 시스템에서의 등록 해제 방법 및 이를 위한 장치 | |
CN110402604B (zh) | 在无线通信系统中通知移动性事件的方法及其设备 | |
US10716083B2 (en) | Tracking area assignment method in wireless communication system and device therefor | |
WO2012167478A1 (zh) | 处理寻呼的方法、用户设备和系统 | |
US9504005B2 (en) | Method for processing data associated with location area update in a wireless communication system | |
WO2018070172A1 (en) | User equipment, system and communication method for managing overload in the context of control plane cellular internet of things evolved packet system optimisation | |
CN110999522A (zh) | 用于无线设备的服务间隙控制 | |
CN113613293A (zh) | 用于在wtru中所使用的方法及wtru | |
US10517121B2 (en) | Service processing method, related apparatus, and system | |
WO2020173137A1 (zh) | 一种数据传输方法、相关设备、程序产品以及存储介质 | |
EP2761904B1 (en) | Method for processing data associated with location area update in a wireless communication system | |
CN114071788B (zh) | Ue和网络之间的多接入pdu会话状态同步方法及相关用户设备 | |
WO2011109938A1 (zh) | 无线接入网元信息上报方法、设备和系统 | |
WO2016180018A1 (zh) | 一种接入方法及相应的接入节点、终端和通信网络 | |
WO2012122910A1 (zh) | 一种双通道通信方法和系统 | |
WO2013104111A1 (zh) | 业务恢复方法和移动管理网元 | |
WO2016019559A1 (zh) | 共享网络的用户设备识别装置、系统及方法 | |
CN111629406A (zh) | 一种切换处理的方法、相关设备、程序产品以及存储介质 | |
WO2011097813A1 (zh) | 去激活isr的方法、修改承载参数的方法和网络系统 | |
WO2021163855A1 (zh) | 信息发送方法、接收方法、装置、设备及存储介质 | |
CN118451749A (zh) | 通信保持方法和装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 201180001335.X Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 11867314 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2011867314 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |