WO2017054168A1 - 一种用户设备上下文信息的获取方法、相关设备及系统 - Google Patents

一种用户设备上下文信息的获取方法、相关设备及系统 Download PDF

Info

Publication number
WO2017054168A1
WO2017054168A1 PCT/CN2015/091212 CN2015091212W WO2017054168A1 WO 2017054168 A1 WO2017054168 A1 WO 2017054168A1 CN 2015091212 W CN2015091212 W CN 2015091212W WO 2017054168 A1 WO2017054168 A1 WO 2017054168A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
mme
rrc connection
context information
request
Prior art date
Application number
PCT/CN2015/091212
Other languages
English (en)
French (fr)
Inventor
戴明增
张宏平
曾清海
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP15905080.6A priority Critical patent/EP3349509B1/en
Priority to PCT/CN2015/091212 priority patent/WO2017054168A1/zh
Priority to CN201580082422.0A priority patent/CN107925930B/zh
Publication of WO2017054168A1 publication Critical patent/WO2017054168A1/zh
Priority to US15/938,248 priority patent/US10721657B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H04W36/0038—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information of security context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0079—Transmission or use of information for re-establishing the radio link in case of hand-off failure or rejection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method, a related device, and a system for acquiring user equipment context information.
  • Discontinuous Reception is mainly used to save user equipment (User Equipment, UE) power consumption.
  • DRX is configured by Radio Resource Control (RRC).
  • RRC Radio Resource Control
  • the UE configured with the DRX does not continuously monitor the physical downlink control channel (PDCCH), thereby achieving the purpose of reducing power consumption.
  • PDCCH physical downlink control channel
  • the UE performs non-continuous monitoring on the PDCCH according to the specified DRX operation. That is, in a DRX cycle, the UE periodically wakes up for a period of time to monitor the PDCCH, and the rest of the time goes to sleep, otherwise the UE The PDCCH needs to be continuously monitored.
  • the handover failure may occur due to the low frequency of UE monitoring.
  • the UE performs an RRC connection re-establishment procedure.
  • the RRC connection re-establishment is successful.
  • the UE that initiates the RRC re-establishment has a valid UE context information.
  • the UE when the UE reselects to a new cell, the UE sends an RRC re-establishment request to the base station to which the new cell belongs, and if the base station to which the new cell belongs does not have the context information of the UE, the UE is served to the UE through the Context Fetch process.
  • the original cell requests context information to complete the RRC establishment of the UE in the new cell.
  • the cell reselection is a UE autonomous behavior. Therefore, the new cell reselected by the UE may not have an X2 network interface with the original cell, which may result in the Context Fetch process cannot be completed, and the RRC connection reestablishment fails.
  • the embodiments of the present invention provide a method for acquiring user equipment context information, a related device, and a system, which are used to prevent the UE from releasing the signaling and delay of the UE after the handover fails, thereby facilitating fast recovery of the service.
  • a first aspect of the embodiments of the present invention provides a method for acquiring user equipment context information, including:
  • the first base station determines that the first base station does not satisfy the UE context information condition, the first base station sends the UE context information establishment request to the mobility management entity MME;
  • the first base station receives a response message sent by the MME in response to the UE context information establishment request, and the response message carries the UE context information.
  • the connection status information includes an MME identifier to which the UE belongs, and the first base station determines, according to the connection status information, Whether the first base station satisfies the second base station for the UE context information condition, including:
  • the first base station determines that the first base station does not satisfy the requirement for the UE context information.
  • the MME is different from the MME to which the UE belongs, the UE context information establishment request And carrying the UE identifier and the MME identifier to which the UE belongs, where the UE context information establishment request is used to trigger the MME to request context information of the UE to the MME to which the UE belongs according to the MME identifier to which the UE belongs.
  • the connection status information includes a second base station identifier, and the first base station determines the first according to the connection status information. Whether the base station satisfies the conditions for requesting the UE context information, including:
  • the first base station Determining that the first base station does not satisfy the requesting the UE context information condition.
  • the MME is the MME to which the UE belongs, the first base station, and the fourth possible implementation manner.
  • the MME to which the UE belongs is connected, the UE context information establishment request carries an initial message of the UE, and the UE context information establishment request is used to trigger an MME to which the UE belongs to the second base station according to an initial message of the UE.
  • the context information of the UE is requested.
  • the first base station sends the UE context information establishment request to the mobility management entity MME in the fifth possible implementation manner of the first aspect.
  • the method further includes:
  • the first base station sends a reject message of the first RRC connection setup request to the UE, where the reject message is used to trigger the UE to perform a TAU;
  • the first base station receives a second RRC connection setup request sent by the UE, and selects an MME other than the MME to which the UE belongs according to the second RRC connection setup request.
  • the first base station receives the After the response message sent by the MME in response to the UE context information establishment request, the method further includes: the first base station sending an RRC connection re-establishment completion response to the UE, where the RRC connection re-establishment completion response carrying configuration indication , security initialization instructions, configuration information, and security parameters.
  • the first base station receives the After the response message sent by the MME in response to the UE context information establishment request, the method further includes: the first base station receiving the cached data sent by the second base station.
  • a second aspect of the embodiments of the present invention provides a method for acquiring user equipment context information, including:
  • the user equipment UE receives the UE autonomous mobility parameter sent by the second base station;
  • the UE selects a first base station according to the UE autonomous mobility parameter
  • the first RRC connection setup request carries the connection state information of the UE before sending the first RRC connection setup request, where the first RRC connection setup request is used to indicate the And determining, by the first base station, that the first base station does not satisfy the request for the UE context information according to the connection status information, and sending the UE context information establishment request to the mobility management entity MME.
  • the method also includes:
  • an RRC connection setup complete response sent by the first base station where the RRC connection re-establishment completion response carries a configuration indication, a security initialization indication, configuration information, and a security parameter;
  • the UE deletes initial configuration information according to the configuration indication, and uses the configuration information;
  • the UE activates the security parameter according to the security initialization indication.
  • the UE sends, according to the UE autonomous mobility parameter, to the first base station After the radio resource control RRC connection establishment request, the method further includes:
  • the UE performs a TAU procedure, and sends a second RRC connection setup request to the first base station; the second RRC connection setup request is used to trigger the first base station to select an MME other than the MME to which the UE belongs. .
  • a third aspect of the embodiments of the present invention provides a base station, including:
  • a receiving unit configured to receive a first RRC connection establishment request sent by the user equipment UE, where the first RRC connection setup request carries connection state information of the UE before sending the first RRC connection establishment request;
  • a determining unit configured to determine, according to the connection state information, whether the first base station satisfies the UE context information condition
  • a sending unit configured to send the UE context information establishment request to the mobility management entity MME if the determining unit determines that the first base station does not satisfy the UE context information condition
  • the receiving unit is further configured to receive a response message sent by the MME in response to the UE context information establishment request, where the response message carries the UE context information.
  • the connection status information includes an MME identifier to which the UE belongs, and the determining unit is specifically configured to:
  • the determining unit determines the first The base station does not satisfy the request for the UE context information condition.
  • the MME is different from the MME to which the UE belongs, the UE context information establishment request And carrying the UE identifier and the MME identifier to which the UE belongs, where the UE context information establishment request is used to trigger the MME to request context information of the UE to the MME to which the UE belongs according to the MME identifier to which the UE belongs.
  • connection status information includes a second base station identifier, where the determining unit is specifically configured to:
  • the determining unit determines that the first base station does not satisfy the request for the UE context information condition.
  • the MME is an MME to which the UE belongs, the first base station, and the The MME to which the UE belongs is connected, the UE context information establishment request carries an initial message of the UE, and the UE context information establishment request is used to trigger an MME to which the UE belongs to the second base station according to an initial message of the UE.
  • the context information of the UE is requested.
  • the sending unit is further configured to send the first RRC connection to the UE, in a fifth possible implementation manner of the third aspect, Establishing a request rejection message, the rejection message is used to trigger the UE to perform TAU;
  • the receiving unit is further configured to receive a second RRC connection setup request sent by the UE, and select an MME other than the MME to which the UE belongs according to the second RRC connection setup request.
  • the sending unit is further used And sending an RRC connection re-establishment completion response to the UE, where the RRC connection re-establishment completion response carries a configuration indication, a security initialization indication, configuration information, and a security parameter.
  • the receiving unit is further used Receiving The cached data sent by the second base station.
  • a third aspect of the embodiments of the present invention provides a user equipment UE, including:
  • a receiving unit configured to receive the UE autonomous mobility parameter sent by the second base station
  • a selecting unit configured to select a first base station according to the UE autonomous mobility parameter received by the receiving unit
  • a sending unit configured to send, according to the UE autonomous mobility parameter received by the receiving unit, a first radio resource control RRC connection establishment request to the first base station;
  • the first RRC connection setup request carries the connection state information of the UE before sending the first RRC connection setup request, where the first RRC connection setup request is used to indicate that the first base station is according to the connection.
  • the status information determines that the first base station does not satisfy the request for the UE context information condition, and sends the UE context information establishment request to the mobility management entity MME.
  • the receiving unit is further configured to receive an RRC connection setup complete response sent by the first base station, where the RRC connection is heavy Establishing a completion response carrying configuration indication, a security initialization indication, configuration information, and security parameters;
  • the UE further includes: a processing unit, configured to delete initial configuration information according to the configuration indication, and use the configuration information; and activate the security parameter according to the security initialization indication.
  • the receiving unit is further configured to receive, by the first base station, The reject message of the first RRC connection setup request;
  • the processing unit is further configured to perform a TAU process by the UE;
  • the sending unit is further configured to send a second RRC connection setup request to the first base station, where the second RRC connection setup request is used to trigger the first base station to select an MME other than the MME to which the UE belongs. .
  • a fifth aspect of the embodiment of the present invention provides a user equipment UE, including:
  • processor performs the following steps by calling code or instructions in the memory:
  • the first RRC connection setup request carries the connection state information of the UE before sending the first RRC connection setup request, where the first RRC connection setup request is used to indicate that the first base station is according to the connection.
  • the status information determines that the first base station does not satisfy the request for the UE context information condition, and sends the UE context information establishment request to the mobility management entity MME.
  • the processor is also used to:
  • RRC connection setup complete response sent by the first base station, where the RRC connection re-establishment completion response carries a configuration indication, a security initialization indication, configuration information, and a security parameter;
  • the security parameter is activated in accordance with the security initialization indication.
  • the sending by the UE After the resource controls the RRC connection setup request, the processor is further configured to:
  • the second RRC connection setup request is used to trigger the first base station to select an MME other than the MME to which the UE belongs.
  • the first base station receives the RRC connection setup request sent by the UE, and the first base station determines, according to the connection state information of the UE that is carried by the RRC connection setup request, that the first base station does not satisfy the request for the UE context.
  • the first base station sends the UE context information establishment request to the mobility management entity MME, and when the MME establishes the UE context information, the first base station is sent to the first base station.
  • the response message is sent, the response message carries the UE context information, so that the first base station completes the RRC connection re-establishment procedure according to the UE context information, thereby preventing the UE from releasing the UE and re-establishing the connection after the handover fails. Order and delay, which is conducive to the rapid recovery of business complex.
  • FIG. 1 is a network architecture according to an embodiment of the present invention
  • FIG. 2 is a flowchart of a first embodiment of a method for acquiring user equipment context information according to an embodiment of the present invention
  • FIG. 3 is a flowchart of a second embodiment of a method for acquiring user equipment context information according to an embodiment of the present disclosure
  • FIG. 4 is a flowchart of a third embodiment of a method for acquiring user equipment context information according to an embodiment of the present invention
  • FIG. 5 is a flowchart of a fourth embodiment of a method for acquiring user equipment context information according to an embodiment of the present disclosure
  • FIG. 6 is a schematic structural diagram of a base station according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic structural diagram of a first embodiment of a UE according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of a second embodiment of a UE according to an embodiment of the present invention.
  • the embodiments of the present invention provide a method for acquiring user equipment context information, a related device, and a system, which are used to prevent the UE from releasing the signaling and delay of the UE after the handover fails, thereby facilitating fast recovery of the service.
  • references to "an embodiment” herein mean that a particular feature, structure, or characteristic described in connection with the embodiments can be included in at least one embodiment of the invention.
  • the appearances of the phrases in various places in the specification are not necessarily referring to the same embodiments, and are not exclusive or alternative embodiments that are mutually exclusive. Those skilled in the art will understand and implicitly understand that the embodiments described herein can be combined with other embodiments.
  • FIG. 1 is a schematic diagram of a network architecture disclosed in an embodiment of the present invention.
  • the first base station, the second base station, the UE, and the Mobility Management Entity (MME) may be included, where the first base station, the second base station, the UE, and the MME may pass the wireless The way to make a communication connection.
  • MME Mobility Management Entity
  • the UE may include a mobile phone, a tablet (such as using a wireless fee card to access the Internet), a personal digital assistant (PDA), a mobile Internet device (MID), a smart wearable device.
  • PDA personal digital assistant
  • MID mobile Internet device
  • the network architecture shown in FIG. 1 can avoid the signaling and delay of the UE to re-establish the connection after the handover fails, thereby facilitating fast recovery of the service.
  • a method for acquiring user equipment context information the first base station receives a first radio resource control RRC connection setup request sent by the user equipment UE, where the first RRC connection setup request carries the UE to send the first RRC a connection state information before the connection establishment request; the first base station determines, according to the connection state information, whether the first base station satisfies the UE context information condition; if the first Determining, by the base station, that the first base station does not satisfy the UE context information condition, the first base station sends the UE context information establishment request to the mobility management entity MME; and the first base station receives the MME to respond to the UE A response message sent by the context information establishment request, the response message carrying the UE context information.
  • FIG. 2 is a flowchart of a first embodiment of a method for acquiring user equipment context information according to an embodiment of the present invention.
  • a method for acquiring user equipment context information provided by an embodiment of the present invention may include steps S201 to S204:
  • the first base station receives a first radio resource control RRC connection setup request sent by the user equipment UE, where the first RRC connection setup request carries connection state information of the UE before sending the first RRC connection setup request.
  • the second base station when the second base station allows the UE to move autonomously in the long DRX state, the second base station sends the DRX configuration information to the UE, where the DRX configuration information includes the UE autonomous mobility parameter, and the UE autonomous mobility parameter includes the UE autonomous
  • the trigger timing of the mobile the range of the UE's autonomous mobility, the timing of the UE autonomous mobile stop, and the timing at which the UE initiates the RRC connection re-establishment.
  • the triggering time of the autonomous mobility of the UE is that the UE defaults to enter the long DRX sleep period, and the UE enters the UE autonomous mobile state.
  • the UE enters the long DRX sleep period, including: the long DRX inactivity timer expires; or, the long The DRX wakes up timeout; or the UE directly receives the long DRX command; or the triggering time of the UE's autonomous mobile is a specific time, for example, the UE enters the UE's autonomous mobile state after the UE enters the long DRX sleep period; If the signal quality of the serving cell is worse than the preset threshold, the UE enters the autonomous mobile state and the like.
  • the scope of the above-mentioned UE autonomous mobility is a range in which the network can control the autonomous mobility of the UE, and only allows the UE to move autonomously within a certain range, for example, configuring a mobile cell, a frequency, a TA list, etc., and configuring a priority of the candidate mobile cell, the UE According to a certain priority rule, it moves autonomously within the range of the above-mentioned UE autonomous movement.
  • the UE autonomous mobile stop timing is a Prohibit timer for configuring the autonomous movement of the UE, and during this time, the UE stops autonomous movement.
  • the UE autonomous mobile stop timing may be located before the UE enters the DRX waking time, so that the UE can quickly report the measurement report when waking up, trigger the network control switch, and the like.
  • the UE initiates the RRC connection re-establishment the UE initiates an RRC connection re-establishment timing to the new base station or the base station to which the new cell belongs when the UE detects the change to a new cell or changes to a new base station.
  • the first radio resource control RRC connection setup request sent by the user equipment UE is: the UE performs autonomous mobility after entering the long DRX sleep state according to the UE autonomous mobility parameter (for example, performing cell After the cell is replaced by the UE, the UE sends a first radio resource control RRC connection setup request to the first base station according to the timing of the RRC connection re-establishment initiated by the UE including the UE autonomous mobility parameter.
  • the first RRC connection setup request carries the connection state information of the UE before sending the first RRC connection setup request, where the connection state information includes the UE identifier, the RRC connection re-establishment cause, the original cell identifier, or the original base station identifier (ie, Second base station identification) and so on.
  • the UE identifier may be a Subscriber Identity Module (SIM) card number of the UE, or an International Mobile Subscriber Identification Number (IMSI), or a mobile station identification number (so-called mobile number). Subscriber International ISDN/PSTN number, MSISDN), etc.
  • the overall service account of the overall data service status of the associated user may correspond to a normal mobile phone monthly traffic account, that is, under the overall service account, the user uses the UE to access the Internet.
  • the traffic consumed by daily applications such as mail, chat, file transfer, and video is included in the traffic charge corresponding to the overall service account;
  • the data service account of the UE may also be a QQ music listening packet, and a green diamond listening packet.
  • a specific service account associated with the user-specific data service status such as a video content stream packet, in which the user uses the service and consumes traffic that is only included in the specific service account, and does not account for the service corresponding to the specific service account.
  • the OCS system should generate a smooth listen to music with the QQ corresponding to the user's specific business business account, which account for example in the form of a specific service can be 765367XXX_QQ_music_VIP.
  • the first base station determines, according to the connection state information, whether the first base station satisfies the UE context information condition.
  • whether the first base station satisfies the UE context information that is, whether the first base station can request the UE context information through the Context Fetch process.
  • the foregoing connection status information includes a second base station identifier
  • the first base station determines, according to the connection status information, whether the first base station satisfies the condition that the UE context information is requested:
  • the second base station identifier determines whether there is an interface for connecting the first base station and the second base station; if there is no connection for connecting the first base station and the foregoing And the first base station determines that the first base station does not satisfy the foregoing UE context information condition.
  • the first base station determines, according to the identifier of the second base station, whether there is an X2 network connection interface directly connected by the first base station and the second base station, and if not, the first base station cannot request the UE context from the second base station through the Context Fetch process.
  • the information that is, the first base station does not satisfy the above-mentioned UE context information condition.
  • the foregoing connection state information includes an MME identifier to which the UE belongs, and the first base station determines, according to the connection state information, whether the first base station satisfies the condition that the UE context information is requested:
  • the base station determines, according to the MME identifier that the UE belongs to, whether the first base station is connected to the MME to which the UE belongs; if the first base station is not connected to the MME to which the UE belongs, the first base station determines that the first base station does not satisfy the request.
  • UE context information condition That is, the first base station determines, according to the MME identity to which the UE belongs, whether the first base station and the second base station are connected to the same MME. If not, the first base station cannot request the UE by using the Context Fetch procedure to identify the MME to which the UE belongs.
  • the context information that is, the first base station does not satisfy the above-mentioned UE context information condition.
  • the first base station determines that the first base station does not satisfy the UE context information condition, the first base station sends the UE context information establishment request to the mobility management entity MME.
  • the specific manner for the first base station to send the UE context information establishment request to the mobility management entity MME is: if there is no interface for connecting the first base station and the second base station That is, there is no X2 network connection interface for connecting the interface between the first base station and the second base station, and when the first base station is connected to the MME to which the UE belongs, the first base station is to the MME to which the UE belongs.
  • Sending the foregoing UE context information establishment request where the UE context information establishment request carries an initial message of the UE, where the initial UE message includes an identifier of the UE and an identifier of the second base station, and the foregoing UE context information establishment request is used to trigger the UE to belong to
  • the MME requests the second base station for the context information of the UE according to the initial message of the UE.
  • the MME that the UE belongs to requests the second base station to request the context information of the UE, and the MME to which the UE belongs sends the UE context information to the second base station according to the identifier of the second base station.
  • the request that the UE context information acquisition request carries the identifier of the UE, so that the second base station acquires the context information of the UE according to the identifier of the UE, and
  • the context information of the UE is sent to the MME to which the UE belongs.
  • the specific method for the first base station to send the UE context information establishment request to the mobility management entity MME is: if the first base station is not connected to the MME to which the UE belongs, The first base station cannot send the context information of the UE to the MME to which the UE belongs by using the Context Fetch, and the first base station sends the UE context information establishment request to the MME, where the MME is different from the MME to which the UE belongs, and the UE context information establishment request carries the foregoing.
  • the UE context information establishment request is used to trigger the MME to request context information of the UE to the MME to which the UE belongs according to the MME identifier to which the UE belongs.
  • the first base station arbitrarily selects one of the MMEs from all connectable MMEs of the first base station, and if the number of all connectable MMEs of the first base station is When the first eNB selects the MME, the first base station selects the MME with a higher priority as the MME according to the priority of the MME.
  • the second RRC connection setup request is sent by the UE to the first base station when the UE receives the reject message of the first RRC connection setup request sent by the first base station. The foregoing reject message is used to trigger the UE to perform TAU.
  • the first base station receives a response message sent by the MME in response to the UE context information establishment request, where the response message carries the UE context information.
  • the UE context information includes at least the ID of the UE, so that when the RRC connection is re-established, the first base station determines whether the UE that requests the re-establishment is legal according to the UE context information, thereby determining whether to allow RRC re-establishment, if the UE context If the information does not have the ID of the UE, the RRC reestablishment will be rejected.
  • the first base station receives the RRC connection setup request sent by the UE, and the first base station determines, according to the connection state information of the UE that is carried in the RRC connection setup request, that the first base station does not send the RRC connection setup request.
  • the first base station sends the UE context information establishment request to the mobility management entity MME when the UE context information is requested by the Context Fetch, and the UE establishes the UE context information when the MME establishes the UE context information.
  • a response message sent by the first base station where the response message carries the UE context information, so that the first base station completes an RRC connection re-establishment procedure according to the UE context information, thereby preventing the UE from releasing the UE after the handover fails.
  • Establish signaling and delay for the connection which is beneficial to the industry Quick recovery.
  • the method for acquiring user equipment context information shown in FIG. 2 further includes: sending, by the first base station, the UE Determining a first RRC connection setup request, the reject message is used to trigger the UE to perform a TAU; the first base station receives a second RRC connection setup request sent by the UE; and according to the second RRC connection
  • the establishment request requests the MME other than the MME to which the UE belongs.
  • the method for acquiring the user equipment context information shown in FIG. 2 further includes: the first base station The UE sends an RRC connection re-establishment completion response, and the RRC connection re-establishment completion response carries a configuration indication, a security initialization indication, configuration information, and a security parameter.
  • the acquiring method of the user equipment context information shown in FIG. 2 further includes: receiving, by the first base station The cached data sent by the second base station.
  • FIG. 3 is a flowchart of a second embodiment of a method for acquiring user equipment context information according to an embodiment of the present invention.
  • a method for acquiring user equipment context information provided by an embodiment of the present invention may include steps S301 to S303:
  • the user equipment UE receives the UE autonomous mobility parameter sent by the second base station.
  • the second base station when the second base station allows the UE to move autonomously in the long DRX state, the second base station sends the DRX configuration information to the UE, where the DRX configuration information includes the UE autonomous mobility parameter, and the UE autonomous mobility parameter includes the UE autonomous
  • the trigger timing of the mobile the range of the UE's autonomous mobility, the timing of the UE autonomous mobile stop, and the timing at which the UE initiates the RRC connection re-establishment.
  • the triggering time of the autonomous mobility of the UE is that the UE defaults to enter the long DRX sleep period, and the UE enters the UE autonomous mobile state.
  • the UE enters the long DRX sleep period, including: the long DRX inactivity timer expires; or, the long The DRX wakes up timeout; or the UE directly receives the long DRX command; or the triggering time of the UE's autonomous mobile is a specific time, for example, the UE enters the UE's autonomous mobile state after the UE enters the long DRX sleep period; If the signal quality of the serving cell is worse than the preset threshold, the UE enters the autonomous mobile state and the like.
  • the above range of UE autonomous movement is The network can control the scope of the autonomous mobility of the UE, and only allows the UE to move autonomously within a certain range, for example, configuring a mobile cell, a frequency, a TA list, etc., and configuring a priority of the candidate mobile cell, and the UE is in accordance with a certain priority rule.
  • the above E moves autonomously within the range of autonomous movement.
  • the UE autonomous mobile stop timing is a Prohibit timer for configuring the autonomous movement of the UE, and during this time, the UE stops autonomous movement.
  • the UE autonomous mobile stop timing may be located before the UE enters the DRX waking time, so that the UE can quickly report the measurement report when waking up, trigger the network control switch, and the like.
  • the UE When the UE initiates the RRC connection re-establishment, the UE initiates an RRC connection re-establishment timing to the new base station or the base station to which the new cell belongs when the UE detects the change to a new cell or changes to a new base station.
  • the UE selects a first base station according to the UE autonomous mobility parameter.
  • the specific implementation manner of the UE selecting the first base station according to the autonomous mobility parameter of the UE is: the UE selects the first base station according to the range of the autonomous mobility of the UE included in the autonomous mobility parameter of the UE, for example, the UE moves according to autonomous
  • the priority of the cell in the range is selected as the RRC reestablished cell in the range of autonomous mobility, or the UE selects the cell with stronger signal quality within the range of autonomous mobility according to the cell signal quality in the autonomous mobile range.
  • the UE uses the base station to which the RRC reestablishment cell belongs as the first base station.
  • the UE sends a first radio resource control RRC connection setup request to the first base station according to the UE autonomous mobility parameter, where the first RRC connection setup request carries the UE to send the first RRC connection setup.
  • a connection status information before the request the first RRC connection establishment request is used to indicate to the mobility management entity MME that the first base station determines, according to the connection status information, that the first base station does not satisfy the requesting UE context information condition Sending the UE context information establishment request.
  • the first radio resource control RRC connection setup request sent by the user equipment UE is: the UE performs autonomous mobility after entering the long DRX sleep state according to the UE autonomous mobility parameter (for example, performing cell After the cell is replaced by the UE, the UE sends a first radio resource control RRC connection setup request to the first base station according to the timing of the RRC connection re-establishment initiated by the UE including the UE autonomous mobility parameter.
  • the first RRC connection setup request carries the connection state information of the UE before sending the first RRC connection setup request, where the connection state information includes the UE identifier, the RRC connection re-establishment cause, the original cell identifier, or the original base station identifier (ie, Second base station identification) and so on.
  • the UE identifier may be the SIM card number of the UE, or the overall service account of the overall data service status of the associated user, such as the IMSI or the MSISDN.
  • the overall service account may correspond to a normal mobile phone monthly traffic account, that is, under the overall service account.
  • the traffic consumed by the user to use the UE for Internet, email, chat, file transmission, video and other daily applications is included in the traffic tariff corresponding to the overall service account; the data service account of the UE may also be a QQ music listening packet.
  • the green diamond listens to the traffic packet, the music video content packet, and the like, and the specific service account associated with the user-specific data service status. Under the service corresponding to the specific service account, the traffic consumed by the user through the UE and consumed is only included in the traffic.
  • the OCS system should generate a specific service account corresponding to the user's QQ music listening service, the specific business account.
  • the form can be, for example, 765367XXX_QQ_music_VIP.
  • the first RRC connection establishment request is used to instruct the first base station to send, to the mobility management entity MME, when the first base station determines that the first base station does not satisfy the requesting context information of the UE according to the connection status information.
  • the UE context information establishment request The first base station satisfies the UE context information, that is, whether the first base station can request the UE context information through the Context Fetch process.
  • the foregoing connection status information includes a second base station identifier, and the first base station determines, according to the connection status information, whether the first base station satisfies the condition that the UE context information is requested:
  • the second base station identifier determines whether there is an interface for connecting the first base station and the second base station; if there is no interface for connecting the first base station and the second base station, the first base station determines the first The base station does not satisfy the above-mentioned UE context information condition.
  • the first base station determines, according to the identifier of the second base station, whether there is an X2 network connection interface directly connected by the first base station and the second base station, and if not, the first base station cannot request the UE context from the second base station through the Context Fetch process.
  • the information that is, the first base station does not satisfy the above-mentioned UE context information condition.
  • the foregoing connection state information includes an MME identifier to which the UE belongs, and the first base station determines, according to the connection state information, whether the first base station satisfies the condition that the UE context information is requested: Determining, by the base station, whether the first base station is connected to the MME to which the UE belongs according to the MME identifier of the UE; if the first base station is not connected to the foregoing If the MME to which the UE belongs is connected, the first base station determines that the first base station does not satisfy the condition for requesting the UE context information.
  • the first base station determines, according to the MME identity to which the UE belongs, whether the first base station and the second base station are connected to the same MME. If not, the first base station cannot request the UE by using the Context Fetch procedure to identify the MME to which the UE belongs.
  • the context information that is, the first base station does not satisfy the above-mentioned UE context information condition.
  • the specific manner for the first base station to send the UE context information establishment request to the mobility management entity MME is: if there is no interface for connecting the first base station and the second base station That is, there is no X2 network connection interface for connecting the interface between the first base station and the second base station, and in a case where the first base station is connected to the MME to which the UE belongs, the first base station belongs to the UE
  • the MME sends the foregoing UE context information establishment request, and the foregoing UE context information establishment request carries an initial message of the UE, where the initial UE message includes an identifier of the UE and an identifier of the second base station, and the foregoing UE context information establishment request is used to trigger the UE.
  • the associated MME requests the second base station for the context information of the UE according to the initial message of the UE.
  • the MME that the UE belongs to requests the second base station to request the context information of the UE, and the MME to which the UE belongs sends the UE context information to the second base station according to the identifier of the second base station.
  • the request, the UE context information acquisition request carries the identifier of the UE, so that the second base station acquires the context information of the UE according to the identifier of the UE, and sends the context information of the UE to the MME to which the UE belongs.
  • the specific method for the first base station to send the UE context information establishment request to the mobility management entity MME is: if the first base station is not connected to the MME to which the UE belongs, The first base station cannot send the context information of the UE to the MME to which the UE belongs by using the Context Fetch, and the first base station sends the UE context information establishment request to the MME, where the MME is different from the MME to which the UE belongs, and the UE context information establishment request carries the foregoing.
  • the UE context information establishment request is used to trigger the MME to request context information of the UE to the MME to which the UE belongs according to the MME identifier to which the UE belongs.
  • the first base station arbitrarily selects one of the MMEs from all connectable MMEs of the first base station, and if the number of all connectable MMEs of the first base station is The specific implementation manner of the first base station selecting the MME is greater than 1: the first base station selects a priority ratio according to the priority of the MME. The higher MME acts as the above MME.
  • the second RRC connection setup request is sent by the UE to the first base station when the UE receives the reject message of the first RRC connection setup request sent by the first base station. The foregoing reject message is used to trigger the UE to perform TAU.
  • the first base station receives the RRC connection setup request sent by the UE, and the first base station determines, according to the connection state information of the UE that is carried in the RRC connection setup request, that the first base station does not send the RRC connection setup request.
  • the first base station sends the UE context information establishment request to the mobility management entity MME when the UE context information is requested by the Context Fetch, and the UE establishes the UE context information when the MME establishes the UE context information.
  • the response message carries the UE context information, so that the first base station completes an RRC connection re-establishment procedure according to the UE context information, thereby preventing the UE from releasing the UE after the handover fails.
  • the signaling and delay of the connection are established, which facilitates the rapid recovery of the service.
  • the acquiring method of the user equipment context information shown in FIG. 3 further includes: the UE receiving the The RRC connection re-establishment completion response sent by the first base station, the RRC connection re-establishment completion response carries a configuration indication, a security initialization indication, configuration information, and a security parameter; the UE deletes the initial configuration information according to the configuration indication, and uses the The configuration information; the UE activates the security parameter according to the security initialization indication.
  • the first base station After the first base station acquires new UE context information, and the new context information includes the foregoing security parameters (ie, new security parameters, such as a new KeNB), the first base station needs to activate the security parameters of the UE according to the new KeNB. Therefore, the RRC connection re-establishment completion response sent by the first base station to the UE carries the security initialization indication, so that the UE initially derives the secret key according to the security parameter, and sends a security initialization indication to the NAS layer, where the security initialization indication carries the security parameter. So that the NAS simultaneously initializes the security key according to the above security parameters.
  • new security parameters such as a new KeNB
  • the acquiring method of the user equipment context information shown in FIG. 3 further includes: the UE receiving the first base station Sending the first RRC connection setup request reject message, the reject message to the first base station; the UE performing a TAU procedure, and sending a second RRC connection setup request to the first base station; An RRC connection setup request is used to trigger the first base The station selects an MME other than the MME to which the UE belongs.
  • FIG. 4 is a flowchart of a third embodiment of a method for acquiring user equipment context information according to an embodiment of the present invention.
  • a method for acquiring user equipment context information provided by an embodiment of the present invention may include steps S401 to S418:
  • the second base station sends a UE autonomous mobility parameter to the user equipment UE.
  • the second base station when the second base station allows the UE to move autonomously in the long DRX state, the second base station sends the DRX configuration information to the UE, where the DRX configuration information includes the UE autonomous mobility parameter, and the UE autonomous mobility parameter includes the UE autonomous
  • the trigger timing of the mobile the range of the UE's autonomous mobility, the timing of the UE autonomous mobile stop, and the timing at which the UE initiates the RRC connection re-establishment.
  • the triggering time of the autonomous mobility of the UE is that the UE defaults to enter the long DRX sleep period, and the UE enters the UE autonomous mobile state.
  • the UE enters the long DRX sleep period, including: the long DRX inactivity timer expires; or, the long The DRX wakes up timeout; or the UE directly receives the long DRX command; or the triggering time of the UE's autonomous mobile is a specific time, for example, the UE enters the UE's autonomous mobile state after the UE enters the long DRX sleep period; If the signal quality of the serving cell is worse than the preset threshold, the UE enters the autonomous mobile state and the like.
  • the scope of the above-mentioned UE autonomous mobility is a range in which the network can control the autonomous mobility of the UE, and only allows the UE to move autonomously within a certain range, for example, configuring a mobile cell, a frequency, a TA list, etc., and configuring a priority of the candidate mobile cell, the UE According to a certain priority rule, it moves autonomously within the range of the above-mentioned UE autonomous movement.
  • the UE autonomous mobile stop timing is a Prohibit timer for configuring the autonomous movement of the UE, and during this time, the UE stops autonomous movement.
  • the UE autonomous mobile stop timing may be located before the UE enters the DRX waking time, so that the UE can quickly report the measurement report when waking up, trigger the network control switch, and the like.
  • the UE initiates the RRC connection re-establishment the UE initiates an RRC connection re-establishment timing to the new base station or the base station to which the new cell belongs when the UE detects the change to a new cell or changes to a new base station.
  • the UE receives the UE autonomous mobility parameter sent by the first base station.
  • the UE After the UE enters a long DRX sleep state, the UE selects a first base station according to the UE autonomous mobility parameter.
  • the UE selects the specific fact of the first base station according to the autonomous mobility parameter of the UE.
  • the method is: the UE selects the first base station according to the range of the autonomous movement of the UE included in the autonomous mobility parameter of the UE. For example, the UE selects the cell with a higher priority within the range of autonomous mobility according to the priority of the cell in the autonomous mobile range.
  • the UE selects a cell with strong signal quality as an RRC reestablishment cell or the like in the range of autonomous mobility according to the cell signal quality in the autonomous mobile range, and then the UE takes the base station to which the RRC reestablished cell belongs as the first Base station.
  • the UE sends a first sending RRC connection setup request to the first base station.
  • the first radio resource control RRC connection setup request sent by the user equipment UE is: the UE performs autonomous mobility after entering the long DRX sleep state according to the UE autonomous mobility parameter (for example, performing cell After the cell is replaced by the UE, the UE sends a first radio resource control RRC connection setup request to the first base station according to the timing of the RRC connection re-establishment initiated by the UE including the UE autonomous mobility parameter.
  • the first RRC connection setup request carries the connection state information of the UE before sending the first RRC connection setup request, where the connection state information includes the UE identifier, the RRC connection re-establishment cause, the original cell identifier, or the original base station identifier (ie, Second base station identification) and so on.
  • the UE identifier may be a UE SIM card number, or an IMSI, or an overall service account of an associated data service status of the associated user, such as an MSISDN.
  • the overall service account may correspond to a normal mobile phone monthly traffic account, that is, under the overall service account.
  • the traffic consumed by the user to use the UE for Internet, email, chat, file transmission, video and other daily applications is included in the traffic tariff corresponding to the overall service account; the data service account of the UE may also be a QQ music listening packet.
  • the green diamond listens to the traffic packet, the music video content packet, and the like, and the specific service account associated with the user-specific data service status. Under the service corresponding to the specific service account, the traffic consumed by the user through the UE and consumed is only included in the traffic.
  • the OCS system should generate a specific service account corresponding to the user's QQ music listening service, the specific business account.
  • the form can be, for example, 765367XXX_QQ_music_VIP.
  • the first base station receives the first RRC connection setup request sent by the UE, where the first RRC connection setup request carries connection state information of the UE before sending the first RRC connection setup request.
  • the connection status information includes a second base station identifier.
  • the first base station determines, according to the second base station identifier, whether an interface for connecting the first base station and the second base station exists.
  • the first base station requests the second base station for the UE context through the context fetch process, thereby completing the RRC connection re-establishment of the UE at the first base station.
  • step S407 is performed.
  • the first base station determines, according to the identifier of the second base station, whether there is an X2 network connection interface directly connected by the first base station and the second base station, and if not, the first base station cannot request the second base station through the Context Fetch process.
  • UE context information that is, the first base station does not satisfy the above-mentioned UE context information condition.
  • the connection status information includes an MME identity to which the UE belongs, and the first base station determines, according to the MME identity to which the UE belongs, whether the first base station is connected to the MME to which the UE belongs.
  • step S408 is performed.
  • steps S507-517 in the fourth embodiment of the method for acquiring user equipment context information provided by the embodiment of the present invention are performed.
  • the first base station sends the UE context information establishment request to the MME, where the MME is an MME to which the UE belongs, and the UE context information establishment request carries an initial message of the UE, where the initial UE message includes The identity of the UE and the identity of the second base station.
  • the MME receives the UE context information setup request sent by the first base station.
  • the MME requests the second base station for the context information of the UE according to the initial message of the UE, where
  • the specific mode for the MME to request the second base station to request the context information of the UE according to the initial message of the UE is: the MME sends a UE context information acquisition request to the second base station according to the identifier of the second base station, and the UE context information is acquired.
  • the request carries the identifier of the UE, so that the second base station acquires the context information of the UE according to the identifier of the UE, and sends the context information of the UE to the MME.
  • the MME sends a response message to the first base station in response to the UE context information establishment request, where the response message carries the UE context information.
  • the first base station receives a response message sent by the MME in response to the UE context information establishment request.
  • the first base station sends an RRC connection re-establishment completion response to the UE, where
  • the RRC connection re-establishment completion response carries a configuration indication, a security initialization indication, configuration information, and security parameters.
  • the UE receives an RRC connection re-establishment completion response sent by the first base station.
  • the UE deletes initial configuration information according to the configuration indication, and uses the configuration information.
  • the UE activates the security parameter according to the security initialization indication.
  • the first base station after the first base station acquires the new UE context information, and the new context information includes the foregoing security parameter (that is, a new security parameter, such as a new KeNB), the first base station needs to be based on the new KeNB.
  • Activating the security parameter of the UE so the RRC connection re-establishment completion response sent by the first base station to the UE carries the security initialization indication, so that the UE initially derives the secret key according to the security parameter, and sends a security initialization indication to the NAS layer, and the security initialization is performed.
  • the indication carries the above security parameters, so that the NAS simultaneously initializes the security key according to the above security parameters.
  • the MME When the MME detects that the MME is connected to the second base station, the MME sends a UE context release request to the second base station, where the UE context release request carries the identifier or data of the first base station. Forwarding address.
  • the MME detects that the MME and the second base station still maintain the S1 connection, and the MME sends a UE context release request to the second base station, where the UE context release request carries the first The identity of the base station or the data forwarding address such that the second base station forwards the buffered data to the first base station.
  • the second base station receives the UE context release request sent by the MME.
  • the second base station sends the cache data to the first base station according to the identifier or data forwarding address of the first base station, where the UE context release request is carried.
  • the first base station receives cache data sent by the second base station.
  • the first base station receives the RRC connection setup request sent by the UE, and the first base station determines, according to the connection state information of the UE that is carried in the RRC connection setup request, that the first base station does not send the RRC connection setup request.
  • the first base station sends the UE context information establishment request to the mobility management entity MME when the UE context information is requested by the Context Fetch, and the UE establishes the UE context information when the MME establishes the UE context information.
  • the UE releases the signaling and delay of the connection and re-establishes the connection, thereby facilitating fast recovery of the service.
  • FIG. 5 is a flowchart of a fourth embodiment of a method for acquiring user equipment context information according to an embodiment of the present invention.
  • a method for acquiring user equipment context information provided by an embodiment of the present invention may include steps S501 to S524:
  • the second base station sends a UE autonomous mobility parameter to the user equipment UE.
  • the second base station when the second base station allows the UE to move autonomously in the long DRX state, the second base station sends the DRX configuration information to the UE, where the DRX configuration information includes the UE autonomous mobility parameter, and the UE autonomous mobility parameter includes the UE autonomous
  • the trigger timing of the mobile the range of the UE's autonomous mobility, the timing of the UE autonomous mobile stop, and the timing at which the UE initiates the RRC connection re-establishment.
  • the triggering time of the autonomous mobility of the UE is that the UE defaults to enter the long DRX sleep period, and the UE enters the UE autonomous mobile state.
  • the UE enters the long DRX sleep period, including: the long DRX inactivity timer expires; or, the long The DRX wakes up timeout; or the UE directly receives the long DRX command; or the triggering time of the UE's autonomous mobile is a specific time, for example, the UE enters the UE's autonomous mobile state after the UE enters the long DRX sleep period; If the signal quality of the serving cell is worse than the preset threshold, the UE enters the autonomous mobile state and the like.
  • the scope of the above-mentioned UE autonomous mobility is a range in which the network can control the autonomous mobility of the UE, and only allows the UE to move autonomously within a certain range, for example, configuring a mobile cell, a frequency, a TA list, etc., and configuring a priority of the candidate mobile cell, the UE According to a certain priority rule, it moves autonomously within the range of the above-mentioned UE autonomous movement.
  • the UE autonomous mobile stop timing is a Prohibit timer for configuring the autonomous movement of the UE, and during this time, the UE stops autonomous movement.
  • the UE autonomous mobile stop timing may be located before the UE enters the DRX waking time, so that the UE can quickly report the measurement report when waking up, trigger the network control switch, and the like.
  • the UE initiates the RRC connection re-establishment the UE initiates an RRC connection re-establishment timing to the new base station or the base station to which the new cell belongs when the UE detects the change to a new cell or changes to a new base station.
  • the UE receives the UE autonomous mobility parameter sent by the first base station.
  • the UE After the UE enters a long DRX sleep state, the UE selects a first base station according to the UE autonomous mobility parameter.
  • the specific implementation manner of the UE selecting the first base station according to the autonomous mobility parameter of the UE is: the UE selects the first base station according to the range of the autonomous mobility of the UE included in the autonomous mobility parameter of the UE, for example, the UE moves according to autonomous
  • the priority of the cell in the range is selected as the RRC reestablished cell in the range of autonomous mobility, or the UE selects the cell with stronger signal quality within the range of autonomous mobility according to the cell signal quality in the autonomous mobile range.
  • the UE uses the base station to which the RRC reestablishment cell belongs as the first base station.
  • the UE sends a first sending RRC connection setup request to the first base station.
  • the first radio resource control RRC connection setup request sent by the user equipment UE is: the UE performs autonomous mobility after entering the long DRX sleep state according to the UE autonomous mobility parameter (for example, performing cell After the cell is replaced by the UE, the UE sends a first radio resource control RRC connection setup request to the first base station according to the timing of the RRC connection re-establishment initiated by the UE including the UE autonomous mobility parameter.
  • the first RRC connection setup request carries the connection state information of the UE before sending the first RRC connection setup request, where the connection state information includes the UE identifier, the RRC connection re-establishment cause, the original cell identifier, or the original base station identifier (ie, Second base station identification) and so on.
  • the UE identifier may be a UE SIM card number, or an IMSI, or an overall service account of an associated data service status of the associated user, such as an MSISDN.
  • the overall service account may correspond to a normal mobile phone monthly traffic account, that is, under the overall service account.
  • the traffic consumed by the user to use the UE for Internet, email, chat, file transmission, video and other daily applications is included in the traffic tariff corresponding to the overall service account; the data service account of the UE may also be a QQ music listening packet.
  • the green diamond listens to the traffic packet, the music video content packet, and the like, and the specific service account associated with the user-specific data service status. Under the service corresponding to the specific service account, the traffic consumed by the user through the UE and consumed is only included in the traffic.
  • the OCS system should generate a specific service account corresponding to the user's QQ music listening service, the specific business account.
  • the form can be, for example, 765367XXX_QQ_music_VIP.
  • the first base station receives the first RRC connection setup request sent by the UE, where the first RRC connection setup request carries connection state information of the UE before sending the first RRC connection setup request.
  • the connection status information includes an MME identifier to which the UE belongs.
  • the first base station determines, according to the MME identity to which the UE belongs, the first base station. Whether to connect with the MME to which the UE belongs.
  • steps S408-411 in the third embodiment of the method for acquiring user equipment context information provided by the embodiment of the present invention are performed.
  • step S507 is performed.
  • the first base station determines, according to the MME identity that the UE belongs to, whether the first base station and the second base station are connected to the same MME. If not, the first base station cannot use the Context Fetch process to identify the MME to which the UE belongs.
  • the UE context information is requested, that is, the first base station does not satisfy the above-mentioned UE context information condition.
  • the first base station sends a reject message of the first RRC connection setup request to the UE, where the reject message is used to trigger the UE to perform TAU.
  • the UE receives a reject message of the first RRC connection setup request sent by the first base station.
  • the UE performs a TAU procedure, and sends a second RRC connection setup request to the first base station.
  • the first base station receives the second RRC connection setup request sent by the UE, and selects a second MME according to the second RRC connection setup request, where the second MME is an MME to which the UE belongs. MME outside.
  • the second MME is one of the MMEs that the first base station arbitrarily selects from all connectable MMEs of the first base station after receiving the second RRC connection setup request sent by the UE, if the first base station is the first When the number of all connectable MMEs of the base station is greater than 1, the first base station selects the MME according to the priority of the MME, and selects the MME with the higher priority as the second MME according to the priority of the MME.
  • the first base station sends the UE context information establishment request to the second MME.
  • the second MME receives the UE context information setup request sent by the first base station, where the UE context information setup request carries the UE identifier and an MME identifier to which the UE belongs.
  • the second MME sends the UE context information acquisition request to the first MME according to the MME identifier to which the UE belongs, where the first MME is an MME to which the UE belongs.
  • the UE context information acquisition request carries the UE identifier.
  • the first MME acquires the UE context information according to the UE identifier, and sends the UE context information to the second MME.
  • the second MME receives the UE context information sent by the first MME.
  • the second MME sends a response message of the UE context information establishment request to the first base station.
  • the first base station receives the response message that is sent by the second MME in response to the UE context information establishment request, where the response message carries the UE context information.
  • the first base station sends an RRC connection re-establishment completion response to the UE, where the RRC connection re-establishment completion response carries a configuration indication, a security initialization indication, configuration information, and a security parameter.
  • the UE receives an RRC connection re-establishment completion response sent by the first base station.
  • the UE deletes initial configuration information according to the configuration indication, and uses the configuration information.
  • the UE activates the security parameter according to the security initialization indication.
  • the first base station after the first base station acquires the new UE context information, and the new context information includes the foregoing security parameter (that is, a new security parameter, such as a new KeNB), the first base station needs to be based on the new KeNB.
  • Activating the security parameter of the UE so the RRC connection re-establishment completion response sent by the first base station to the UE carries the security initialization indication, so that the UE initially derives the secret key according to the security parameter, and sends a security initialization indication to the NAS layer, and the security initialization is performed.
  • the indication carries the above security parameters, so that the NAS simultaneously initializes the security key according to the above security parameters.
  • the first MME When the first MME detects that the first MME is connected to the second base station, the first MME sends a UE context release request to the second base station, where the UE context release request carries a The identity or data forwarding address of a base station.
  • the first MME after the first MME detects that the first MME and the second base station still maintain the S1 connection, the first MME sends a UE context release request to the second base station, where the first MME establishes the context of the UE.
  • the UE context release request carries the identity or data forwarding address of the first base station, such that the second base station forwards the buffered data to the first base station.
  • the second base station receives the UE context release request sent by the first MME.
  • the second base station sends the cache data to the first base station according to the identifier or data forwarding address of the first base station, where the UE context release request is carried.
  • the first base station receives the cache data sent by the second base station.
  • the first base station receives the RRC connection setup request sent by the UE, and the first base station determines, according to the connection state information of the UE that is carried in the RRC connection setup request, that the first base station does not send the RRC connection setup request.
  • the first base station sends the UE context information establishment request to the mobility management entity MME when the UE context information is requested by the Context Fetch, and the UE establishes the UE context information when the MME establishes the UE context information.
  • the response message carries the UE context information, so that the first base station completes an RRC connection re-establishment procedure according to the UE context information, thereby preventing the UE from releasing the UE after the handover fails.
  • the signaling and delay of the connection are established, which facilitates the rapid recovery of the service.
  • a base station provided by an embodiment of the present invention may include:
  • the receiving unit 601 is configured to receive a first RRC connection establishment request sent by the user equipment UE, where the first RRC connection setup request carries connection state information of the UE before sending the first RRC connection establishment request;
  • a determining unit 602 configured to determine, according to the connection state information, whether the first base station satisfies the UE context information condition;
  • the sending unit 603 is configured to: if the determining unit determines that the first base station does not satisfy the UE context information condition, send the UE context information establishment request to the mobility management entity MME;
  • the receiving unit 601 is further configured to receive a response message sent by the MME in response to the UE context information establishment request, where the response message carries the UE context information.
  • the connection status information includes an MME identifier to which the UE belongs, and the determining unit is specifically configured to: determine, according to the MME identifier that the UE belongs to, whether the first base station is connected to an MME to which the UE belongs; If the first base station is not connected to the MME to which the UE belongs, the determining unit determines that the first base station does not satisfy the UE context information condition.
  • the MME is different from the MME to which the UE belongs, and the UE context information is established.
  • the request to carry the UE identifier and the MME identity to which the UE belongs, the UE context information establishment request is used to trigger the MME to request the context of the UE according to the MME identity to which the UE belongs to the MME to which the UE belongs. information.
  • the connection status information includes a second base station identifier, and the determining unit is specifically configured to: determine, according to the second base station identifier, whether an interface for connecting the first base station and the second base station exists; There is an interface for connecting the first base station and the second base station, and the determining unit determines that the first base station does not satisfy the request for the UE context information condition.
  • the MME is an MME to which the UE belongs, the first base station is connected to an MME to which the UE belongs, and the UE context information establishment request carries an initial message of the UE, and the UE context information establishment request is used. And triggering, by the MME to which the UE belongs, to request, by the second base station, context information of the UE according to an initial message of the UE.
  • the sending unit 603 before the sending unit 603 sends the UE context information establishment request to the mobility management entity MME, the sending unit 603 is further configured to send the first RRC connection setup request rejection message to the UE, where The reject message is used to trigger the UE to perform the TAU; the receiving unit 601 is further configured to receive the second RRC connection setup request sent by the UE, and select, according to the second RRC connection setup request, the UE to belong to MME other than MME.
  • the sending unit 603 is further configured to send an RRC connection re-establishment completion response to the UE, where
  • the RRC connection re-establishment completion response carries a configuration indication, a security initialization indication, configuration information, and security parameters.
  • the receiving unit 601 receives the response message sent by the MME in response to the UE context information establishment request, the receiving unit is further configured to receive the cached data sent by the second base station.
  • the functions of the functional modules of the base station in this embodiment may be specifically implemented according to the method in the foregoing method embodiment.
  • Some or all of the functional modules in the base station may be implemented by hardware circuits, and some or all of the functional modules in the base station may also be implemented by a processor (such as a digital signal processor) by executing code or instructions.
  • the first base station is configured to receive the RRC connection sent by the UE. And requesting, by the first base station, the first base station determines, according to the connection state information before the RRC connection setup request is sent, that the first base station does not satisfy the condition that the UE context information is requested, that is, when the UE context information cannot be requested by the Context Fetch, the first base station Sending, by the mobility management entity MME, the UE context information establishment request, when the MME establishes a response message sent to the first base station when the UE context information is completed, the response message carries the UE context information,
  • the first base station is configured to complete the RRC connection re-establishment process according to the UE context information, so as to prevent the UE from releasing the UE and re-establishing the connection signaling and delay after the handover fails, thereby facilitating fast recovery of the service.
  • a user equipment UE that is provided by an embodiment of the present invention may include:
  • the receiving unit 701 is configured to receive the UE autonomous mobility parameter sent by the second base station.
  • the selecting unit 702 is configured to select the first base station according to the UE autonomous mobility parameter received by the receiving unit;
  • the sending unit 703 is configured to send, according to the UE autonomous mobility parameter received by the receiving unit, a first radio resource control RRC connection establishment request to the first base station;
  • the first RRC connection setup request carries the connection state information of the UE before sending the first RRC connection setup request, where the first RRC connection setup request is used to indicate that the first base station is according to the connection.
  • the status information determines that the first base station does not satisfy the request for the UE context information condition, and sends the UE context information establishment request to the mobility management entity MME.
  • the receiving unit 703 is further configured to receive the The RRC connection setup complete response sent by the first base station, the RRC connection re-establishment completion response carries a configuration indication, a security initialization indication, configuration information, and a security parameter.
  • the UE further includes: a processing unit, configured to perform, according to the configuration indication The initial configuration information is deleted and the configuration information is used; the security parameter is activated according to the security initialization indication.
  • the receiving unit 703 is further configured to receive the a reject message of the first RRC connection setup request sent by a base station;
  • the processing unit is further configured to perform a TAU procedure by the UE;
  • the sending unit is further configured to send the A base station sends a second RRC connection setup request, where the second RRC connection setup request is used to trigger the first base station to select an MME other than the MME to which the UE belongs.
  • the functions of the functional modules of the UE in this embodiment may be specifically implemented according to the method in the foregoing method embodiments.
  • Some or all of the functional modules in the UE may be implemented by hardware circuits, and some or all of the functional modules in the UE may also be implemented by a processor (such as a digital signal processor) by executing code or instructions.
  • the first base station receives the RRC connection setup request sent by the UE, and the first base station determines, according to the connection state information of the UE that is carried in the RRC connection setup request, that the first base station does not send the RRC connection setup request.
  • the first base station sends the UE context information establishment request to the mobility management entity MME when the UE context information is requested by the Context Fetch, and the UE establishes the UE context information when the MME establishes the UE context information.
  • the response message carries the UE context information, so that the first base station completes an RRC connection re-establishment procedure according to the UE context information, thereby preventing the UE from releasing the UE after the handover fails.
  • the signaling and delay of the connection are established, which facilitates the rapid recovery of the service.
  • FIG. 8 is a schematic structural diagram of a second embodiment of a user equipment UE according to an embodiment of the present invention, which may include: a processor 801 and a memory 802; wherein the processor 801 and the memory 802 are coupled by a bus 803.
  • the processor 801 can execute the following steps by calling code or instructions in the memory 801:
  • processor performs the following steps by calling code or instructions in the memory:
  • the first RRC connection setup request carries the connection state information of the UE before sending the first RRC connection setup request, where the first RRC connection setup request is used to indicate the And determining, by the first base station, that the first base station does not satisfy the request for the UE context information according to the connection status information, and sending the UE context information establishment request to the mobility management entity MME.
  • the processor is further configured to: receive the The RRC connection setup completion response sent by the first base station, the RRC connection re-establishment completion response carries a configuration indication, a security initialization indication, configuration information, and a security parameter; deleting the initial configuration information according to the configuration indication, and using the configuration information;
  • the security parameter is activated in accordance with the security initialization indication.
  • the processor is further configured to: receive the a reject message of the first RRC connection setup request sent by the first base station; performing a TAU procedure, and sending a second RRC connection setup request to the first base station; the second RRC connection setup request is used to trigger the first A base station selects an MME other than the MME to which the UE belongs.
  • the functions of the functional modules of the UE in this embodiment may be specifically implemented according to the method in the foregoing method embodiments.
  • Some or all of the functional modules in the UE may be implemented by hardware circuits, and some or all of the functional modules in the UE may also be implemented by a processor (such as a digital signal processor) by executing code or instructions.
  • the first base station receives the RRC connection setup request sent by the UE, and the first base station determines, according to the connection state information of the UE that is carried in the RRC connection setup request, that the first base station does not send the RRC connection setup request.
  • the first base station sends the UE context information establishment request to the mobility management entity MME when the UE context information is requested by the Context Fetch, and the UE establishes the UE context information when the MME establishes the UE context information.
  • the response message carries the UE context information, so that the first base station completes an RRC connection re-establishment procedure according to the UE context information, thereby preventing the UE from releasing the UE after the handover fails.
  • the signaling and delay of the connection are established, which facilitates the rapid recovery of the service.
  • the disclosed apparatus may be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or may be Integrate into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be electrical or otherwise.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • the technical solution of the present invention which is essential or contributes to the prior art, or all or part of the technical solution, may be embodied in the form of a software product stored in a storage medium.
  • a number of instructions are included to cause a computer device (which may be a personal computer, server or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: a U disk, a read-only memory (ROM), and a random access memory.
  • a variety of media that can store program code such as RAM (Random Access Memory), removable hard disk, disk, or optical disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明公开了一种用户设备上下文信息的获取方法，包括：第一基站接收用户设备UE发送的第一无线资源控制RRC连接建立请求，所述第一RRC连接建立请求携带所述UE在发送所述第一RRC连接建立请求之前的连接状态信息；所述第一基站根据所述连接状态信息确定所述第一基站是否满足索要所述UE上下文信息条件；若所述第一基站确定所述第一基站未满足索要所述UE上下文信息条件，所述第一基站向移动性管理实体MME发送所述UE上下文信息建立请求；所述第一基站接收所述MME响应所述UE上下文信息建立请求而发送的响应消息，所述响应消息携带所述UE上下文信息。采用本发明可避免UE在切换失败后，释放UE再重新建立连接的信令和时延，从而有利于业务的快速恢复。

Description

一种用户设备上下文信息的获取方法、相关设备及系统 技术领域
本发明涉及通信技术领域，尤其涉及一种用户设备上下文信息的获取方法、相关设备及系统。
背景技术
非连续接收(Discontinuous Reception，DRX)主要是为了节省用户设备(User Equipment，UE)功率消耗，DRX是由无线资源控制(Radio Resource Control，RRC)配置的。配置了DRX的UE由于不连续监听物理下行控制信道(Physical Downlink Control Channel，PDCCH)，进而达到降低功率消耗的目的。在RRC_CONNECTED状态下，如果配置了DRX，UE按照指定的DRX操作对PDCCH进行非连续的监听，即在一个DRX周期内，UE会定时醒过来一段时间监听PDCCH，其余时间则进入睡眠状态，否则UE需要连续监听PDCCH。
在长DRX态下，由于UE监听的频率较低，可能会导致切换失败。在UE切换失败后，UE将进行RRC连接重建立流程，RRC连接重建立成功的前提是，UE发起RRC重建的小区存在一份有效的UE上下文信息。现有技术中，当UE重选到一个新小区时，UE向新小区所属的基站发送RRC重建立请求，新小区所属基站若不存在该UE的上下文信息，则通过Context Fetch流程向服务该UE的原小区索取上下文信息，从而完成该UE在新小区的RRC建立。
由于小区重选是UE自主行为，因此UE重选的新小区可能与原小区没有X2网络接口，可能导致Context Fetch流程无法完成，进而使得RRC连接重建立失败。
发明内容
本发明实施例提供一种用户设备上下文信息的获取方法、相关设备及系统，用于避免UE在切换失败后，释放UE再重新建立连接的信令和时延，从而有利于业务的快速恢复。
本发明实施例第一方面提供一种用户设备上下文信息的获取方法，包括：
第一基站接收用户设备UE发送的第一无线资源控制RRC连接建立请求，所述第一RRC连接建立请求携带所述UE在发送所述第一RRC连接建立请求之前的连接状态信息；
所述第一基站根据所述连接状态信息确定所述第一基站是否满足索要所述UE上下文信息条件；
若所述第一基站确定所述第一基站未满足索要所述UE上下文信息条件，所述第一基站向移动性管理实体MME发送所述UE上下文信息建立请求；
所述第一基站接收所述MME响应所述UE上下文信息建立请求而发送的响应消息，所述响应消息携带所述UE上下文信息。
结合本发明实施例第一方面，在第一方面的第一种可能的实现方式中，所述连接状态信息包括所述UE所属的MME标识，所述第一基站根据所述连接状态信息确定所述第一基站是否满足向第二基站索要所述UE上下文信息条件，包括：
所述第一基站根据所述UE所属的MME标识判断所述第一基站是否与所述UE所属的MME连接；
若所述第一基站未与所述UE所属的MME连接，则所述第一基站确定所述第一基站不满足索要所述UE上下文信息条件。
结合本发明实施例第一方面的第一种可能的实现方式，在第一方面的第二种可能的实现方式中，所述MME不同于所述UE所属的MME，所述UE上下文信息建立请求携带所述UE标识和所述UE所属的MME标识，所述UE上下文信息建立请求用于触发所述MME根据所述UE所属的MME标识向所述UE所属的MME索要所述UE的上下文信息。
结合本发明实施例第一方面，在第一方面的第三种可能的实现方式中，所述连接状态信息包括第二基站标识，所述第一基站根据所述连接状态信息确定所述第一基站是否满足索要所述UE上下文信息条件，包括：
所述第一基站根据所述第二基站标识判断是否存在用于连接所述第一基站与所述第二基站的接口；
若不存在用于连接所述第一基站与所述第二基站的接口，则所述第一基站 确定所述第一基站不满足索要所述UE上下文信息条件。
结合本发明实施例第一方面的第三种可能的实现方式，在第一方面的第四种可能的实现方式中，所述MME为所述UE所属的MME，所述第一基站与所述UE所属的MME连接，所述UE上下文信息建立请求携带所述UE的初始消息，所述UE上下文信息建立请求用于触发所述UE所属的MME根据所述UE的初始消息向所述第二基站索要所述UE的上下文信息。
结合本发明实施例第一方面的第二种可能的实现方式，在第一方面的第五种可能的实现方式中，所述第一基站向移动性管理实体MME发送所述UE上下文信息建立请求之前，所述方法还包括：
所述第一基站向所述UE发送所述第一RRC连接建立请求的拒绝消息，所述拒绝消息用于触发所述UE执行TAU；
所述第一基站接收所述UE发送的第二RRC连接建立请求；并根据所述第二RRC连接建立请求选取除所述UE所属的MME之外的MME。
结合本发明实施例第一方面、第一方面的第一种至第五种任一种可能的实现方式，在第一方面的第六种可能的实现方式中，所述第一基站接收所述MME响应所述UE上下文信息建立请求而发送的响应消息之后，所述方法还包括：所述第一基站向所述UE发送RRC连接重建立完成响应，所述RRC连接重建立完成响应携带配置指示、安全初始化指示、配置信息以及安全参数。
合本发明实施例第一方面、第一方面的第一种至第六种任一种可能的实现方式，在第一方面的第七种可能的实现方式中，所述第一基站接收所述MME响应所述UE上下文信息建立请求而发送的响应消息之后，所述方法还包括：所述第一基站接收所述第二基站发送的缓存数据。
本发明实施例第二方面提供一种用户设备上下文信息的获取方法，包括：
用户设备UE接收第二基站发送的所述UE自主移动参数；
所述UE根据所述UE自主移动参数选取第一基站；
所述UE根据所述UE自主移动参数向所述第一基站发送第一无线资源控制RRC连接建立请求；
其中，所述第一RRC连接建立请求携带所述UE在发送所述第一RRC连接建立请求之前的连接状态信息，所述第一RRC连接建立请求用于指示所述 第一基站根据所述连接状态信息确定所述第一基站未满足索要UE上下文信息条件时，向移动性管理实体MME发送所述UE上下文信息建立请求。
结合本发明实施例第二方面，在第二方面的第一种可能的实现方式中，所述UE根据所述UE自主移动参数向第一基站发送第一无线资源控制RRC连接建立请求之后，所述方法还包括：
所述UE接收所述第一基站发送的RRC连接建立完成响应，所述RRC连接重建立完成响应携带配置指示、安全初始化指示、配置信息以及安全参数；
所述UE根据所述配置指示删除初始配置信息，并使用所述配置信息；
所述UE根据所述安全初始化指示激活所述安全参数。
结合本发明实施例第二方面或第二方面的第一种可能的实现方式，在第二方面的第二种可能的实现方式中，所述UE根据所述UE自主移动参数向第一基站发送无线资源控制RRC连接建立请求之后，所述方法还包括：
所述UE接收所述第一基站发送的所述第一RRC连接建立请求的拒绝消息；
所述UE执行TAU流程，并向所述第一基站发送第二RRC连接建立请求；所述第二RRC连接建立请求用于触发所述第一基站选取除所述UE所属的MME之外的MME。
本发明实施例第三方面提供一种基站，包括：
接收单元，用于接收用户设备UE发送的第一无线资源控制RRC连接建立请求，所述第一RRC连接建立请求携带所述UE在发送所述第一RRC连接建立请求之前的连接状态信息；
确定单元，用于根据所述连接状态信息确定所述第一基站是否满足索要所述UE上下文信息条件；
发送单元，用于若所述确定单元确定所述第一基站未满足索要所述UE上下文信息条件，向移动性管理实体MME发送所述UE上下文信息建立请求；
所述接收单元，还用于接收所述MME响应所述UE上下文信息建立请求而发送的响应消息，所述响应消息携带所述UE上下文信息。
结合本发明实施例第三方面，在第三方面的第一种可能的实现方式中，所述连接状态信息包括所述UE所属的MME标识，所述确定单元具体用于：
根据所述UE所属的MME标识判断所述第一基站是否与所述UE所属的MME连接；若所述第一基站未与所述UE所属的MME连接，则所述确定单元确定所述第一基站不满足索要所述UE上下文信息条件。
结合本发明实施例第三方面的第一种可能的实现方式，在第三方面的第二种可能的实现方式中，所述MME不同于所述UE所属的MME，所述UE上下文信息建立请求携带所述UE标识和所述UE所属的MME标识，所述UE上下文信息建立请求用于触发所述MME根据所述UE所属的MME标识向所述UE所属的MME索要所述UE的上下文信息。
结合本发明实施例第三方面，在第三方面的第三种可能的实现方式中，所述连接状态信息包括第二基站标识，所述确定单元具体用于：
根据所述第二基站标识判断是否存在用于连接所述第一基站与所述第二基站的接口；若不存在用于连接所述第一基站与所述第二基站的接口，则所述确定单元确定所述第一基站不满足索要所述UE上下文信息条件。
结合本发明实施例第三方面的第三种可能的实现方式，在第三方面的第四种可能的实现方式中，所述MME为所述UE所属的MME，所述第一基站与所述UE所属的MME连接，所述UE上下文信息建立请求携带所述UE的初始消息，所述UE上下文信息建立请求用于触发所述UE所属的MME根据所述UE的初始消息向所述第二基站索要所述UE的上下文信息。
结合本发明实施例第三方面的第二种可能的实现方式，在第三方面的第五种可能的实现方式中，所述发送单元，还用于向所述UE发送所述第一RRC连接建立请求的拒绝消息，所述拒绝消息用于触发所述UE执行TAU；
所述接收单元，还用于接收所述UE发送的第二RRC连接建立请求；并根据所述第二RRC连接建立请求选取除所述UE所属的MME之外的MME。
结合本发明实施例第三方面、第三方面的第一种至第五种任一种可能的实现方式，在第三方面的第六种可能的实现方式中，所述发送单元，还用于向所述UE发送RRC连接重建立完成响应，所述RRC连接重建立完成响应携带配置指示、安全初始化指示、配置信息以及安全参数。
结合本发明实施例第三方面、第三方面的第一种至第六种任一种可能的实现方式，在第三方面的第七种可能的实现方式中，所述接收单元，还用于接收 所述第二基站发送的缓存数据。
本发明实施例第三方面提供一种用户设备UE，包括：
接收单元，用于接收第二基站发送的所述UE自主移动参数；
选取单元，用于根据所述接收单元接收到的所述UE自主移动参数选取第一基站；
发送单元，用于根据所述接收单元接收到的所述UE自主移动参数向所述第一基站发送第一无线资源控制RRC连接建立请求；
其中，所述第一RRC连接建立请求携带所述UE在发送所述第一RRC连接建立请求之前的连接状态信息，所述第一RRC连接建立请求用于指示所述第一基站根据所述连接状态信息确定所述第一基站未满足索要UE上下文信息条件时，向移动性管理实体MME发送所述UE上下文信息建立请求。
结合本发明实施例第四方面，在第四方面的第一种可能的实现方式中，所述接收单元，还用于接收所述第一基站发送的RRC连接建立完成响应，所述RRC连接重建立完成响应携带配置指示、安全初始化指示、配置信息以及安全参数；
所述UE还包括：处理单元，用于根据所述配置指示删除初始配置信息，并使用所述配置信息；根据所述安全初始化指示激活所述安全参数。
结合本发明实施例第四方面或第四方面的第一种可能的实现方式，在第四方面的第二种可能的实现方式中，所述接收单元，还用于接收所述第一基站发送的所述第一RRC连接建立请求的拒绝消息；
所述处理单元，还用于UE执行TAU流程；
所述发送单元，还用于向所述第一基站发送第二RRC连接建立请求；所述第二RRC连接建立请求用于触发所述第一基站选取除所述UE所属的MME之外的MME。
本发明实施例第五方面提供一种用户设备UE，包括：
处理器和存储器；其中，所述处理器通过调用所述存储器中的代码或指令以执行如下步骤：
接收第二基站发送的所述UE自主移动参数；
根据所述UE自主移动参数选取第一基站；
根据所述UE自主移动参数向所述第一基站发送第一无线资源控制RRC连接建立请求；
其中，所述第一RRC连接建立请求携带所述UE在发送所述第一RRC连接建立请求之前的连接状态信息，所述第一RRC连接建立请求用于指示所述第一基站根据所述连接状态信息确定所述第一基站未满足索要UE上下文信息条件时，向移动性管理实体MME发送所述UE上下文信息建立请求。
结合本发明实施例第五方面，在第五方面的第一种可能的实现方式中，所述根据所述UE自主移动参数向第一基站发送第一无线资源控制RRC连接建立请求之后，所述处理器还用于：
接收所述第一基站发送的RRC连接建立完成响应，所述RRC连接重建立完成响应携带配置指示、安全初始化指示、配置信息以及安全参数；
根据所述配置指示删除初始配置信息，并使用所述配置信息；
根据所述安全初始化指示激活所述安全参数。
结合本发明实施例第五方面或第五方面的第一种可能的实现方式，在第五方面的第二种可能的实现方式中，所述根据所述UE自主移动参数向第一基站发送无线资源控制RRC连接建立请求之后，所述处理器还用于：
接收所述第一基站发送的所述第一RRC连接建立请求的拒绝消息；
执行TAU流程，并向所述第一基站发送第二RRC连接建立请求；所述第二RRC连接建立请求用于触发所述第一基站选取除所述UE所属的MME之外的MME。
实施本发明实施例，具有如下有益效果：
本发明实施例中，第一基站在接收UE发送的RRC连接建立请求，第一基站根据RRC连接建立请求携带的UE在发送RRC连接建立请求之前的连接状态信息确定第一基站不满足索要UE上下文信息条件，即不能通过Context Fetch索要UE上下文信息时，第一基站向移动性管理实体MME发送所述UE上下文信息建立请求，在所述MME建立完成所述UE上下文信息时向所述第一基站发送的响应消息，所述响应消息携带所述UE上下文信息，以使得第一基站根据所述UE上下文信息完成RRC连接重建立流程，进而避免UE在切换失败后，释放UE再重新建立连接的信令和时延，从而有利于业务的快速恢 复。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本发明实施例提供的一种网络构架；
图2为本发明实施例提供的用户设备上下文信息的获取方法的第一实施例流程图；
图3为本发明实施例提供的用户设备上下文信息的获取方法的第二实施例流程图；
图4为本发明实施例提供的用户设备上下文信息的获取方法的第三实施例流程图；
图5为本发明实施例提供的用户设备上下文信息的获取方法的第四实施例流程图；
图6为本发明实施例提供的基站的结构示意图；
图7为本发明实施例提供的UE的第一实施例结构示意图；
图8为本发明实施例提供的UE的第二实施例结构示意图。
具体实施方式
本发明实施例提供一种用户设备上下文信息的获取方法、相关设备及系统，用于避免UE在切换失败后，释放UE再重新建立连接的信令和时延，从而有利于业务的快速恢复。
为了使本技术领域的人员更好地理解本发明方案，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分的实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都应当属于本发明保护的范围。
以下分别进行详细说明。
本发明的说明书和权利要求书及所述附图中的术语“第一”、“第二”、“第三”和“第四”等是用于区别不同对象，而不是用于描述特定顺序。此外，术语“包括”和“具有”以及它们任何变形，意图在于覆盖不排他的包含。例如包含了一系列步骤或单元的过程、方法、系统、产品或设备没有限定于已列出的步骤或单元，而是可选地还包括没有列出的步骤或单元，或可选地还包括对于这些过程、方法、产品或设备固有的其它步骤或单元。
在本文中提及“实施例”意味着，结合实施例描述的特定特征、结构或特性可以包含在本发明的至少一个实施例中。在说明书中的各个位置出现该短语并不一定均是指相同的实施例，也不是与其它实施例互斥的独立的或备选的实施例。本领域技术人员显式地和隐式地理解的是，本文所描述的实施例可以与其它实施例相结合。
为了更好理解本发明实施例公开的一种应用于智能音箱的音乐播放方法及智能音箱，下面先对本发明实施例适用的网络构架进行描述。请参阅图1，图1是本发明实施例公开的一种网络构架示意图。在图1所示的网络构架中，可包括第一基站、第二基站、UE和移动性管理实体(Mobility Management Entity，MME)，其中，第一基站、第二基站、UE和MME可以通过无线方式进行通信连接。在所述的网络构架中，UE可以包括移动手机、平板电脑(如使用无线资费卡上网)、个人数字助理(Personal Digital Assistant,PDA)、移动互联网设备(Mobile Internet Device，MID)、智能穿戴设备(如智能手表、智能手环)等各类使用移动通信网络的UE，本发明实施例不作限定。通过图1所示的网络构架，可避免UE在切换失败后，释放UE再重新建立连接的信令和时延，从而有利于业务的快速恢复。
本发明用户设备上下文信息的获取方法的一个实施例。其中，一种用户设备上下文信息的获取方法：第一基站接收用户设备UE发送的第一无线资源控制RRC连接建立请求，所述第一RRC连接建立请求携带所述UE在发送所述第一RRC连接建立请求之前的连接状态信息；所述第一基站根据所述连接状态信息确定所述第一基站是否满足索要所述UE上下文信息条件；若所述第一 基站确定所述第一基站未满足索要所述UE上下文信息条件，所述第一基站向移动性管理实体MME发送所述UE上下文信息建立请求；所述第一基站接收所述MME响应所述UE上下文信息建立请求而发送的响应消息，所述响应消息携带所述UE上下文信息。
请参见图2，图2为本发明实施例提供的一种用户设备上下文信息的获取方法的第一实施例流程图。其中，如图2所示，本发明的一个实施例提供的一种用户设备上下文信息的获取方法可以包括步骤S201～S204：
S201、第一基站接收用户设备UE发送的第一无线资源控制RRC连接建立请求，所述第一RRC连接建立请求携带所述UE在发送所述第一RRC连接建立请求之前的连接状态信息。
本发明实施例中，在第二基站允许UE在长DRX状态下自主移动时，则第二基站向UE发送DRX配置信息，上述DRX配置信息包括UE自主移动参数，上述UE自主移动参数包括UE自主移动的触发时机、UE自主移动的范围、UE自主移动停止时机、UE发起RRC连接重建立的时机。其中，上述UE自主移动的触发时机为UE默认UE进入到长DRX的睡眠期，UE进入UE自主移动状态的时机，上述UE进入长DRX睡眠期包括：长DRX非激活定时器超时；或者，长DRX唤醒时超时；或者UE直接接收到长DRX命令等；或者，UE自主移动的触发时机为一具体时间，比如UE进入长DRX睡眠期起一段时间后，UE进入UE自主移动状态的时机；又如服务小区的信号质量差于预设的门限，UE进入自主移动状态的时机等。上述UE自主移动的范围为网络可以控制UE自主移动的范围，只允许UE在一定的范围内自主移动，比如配置可移动的小区，频率，TA列表等，并配置候选移动小区的优先级，UE按照一定的优先级规则在上述UE自主移动的范围内自主移动。上述UE自主移动停止时机为配置UE自主移动的禁止时间(Prohibit timer)，在这个时间内，UE停止自主移动。上述UE自主移动停止时机可以位于UE进入DRX醒来的前一段时间，这样UE可以在醒来的时候快速上报测量报告，触发网络控制的切换等。上述UE发起RRC连接重建立的时机为UE检测到更换到一个新的小区或者更换到一个新的基站时，UE向新的基站或是新的小区所属的基站发起RRC连接重建立的时机。
本发明实施例中，用户设备UE发送的第一无线资源控制RRC连接建立请求的具体实施方式为：UE根据上述UE自主移动参数，在进入长DRX睡眠态后，UE进行自主移动(比如进行小区重选)，在UE更换小区后，UE根据上述UE自主移动参数包括的UE发起RRC连接重建立的时机向第一基站发送第一无线资源控制RRC连接建立请求。其中，上述第一RRC连接建立请求携带UE在发送第一RRC连接建立请求之前的连接状态信息，上述连接状态信息包括UE标识，RRC连接重建立原因、原小区标识、或是原基站标识(即第二基站标识)等等。其中，UE标识可以是UE的智能卡(Subscriber Identity Module，SIM)卡号，或者国际移动用户识别码(International Mobile Subscriber Identification Number，IMSI)，或者，移动台识别号码(通常所说的手机号码)(Mobile Subscriber International ISDN/PSTN number，MSISDN)等关联用户整体数据业务状态的整体业务账号，该整体业务账号例如可以与通常的手机包月流量账号对应，即在该整体业务账号下，用户利用UE进行上网、邮件、聊天、文件传输、视频等日常应用所消耗的流量均计入该整体业务账号对应的流量资费中；上述UE的数据业务账号还可以是QQ音乐畅听流量包、绿钻畅听流量包、乐视视频内容流量包等关联用户特定数据业务状态的特定业务账号，在该特定业务账号所对应的业务下，用户通过UE使用该业务并消耗的流量只计入该特定业务账号，而不会计入上述整体业务账号，例如某用户购买了QQ音乐畅听流量包，则OCS系统应生成一个与该用户的QQ音乐畅听业务对应的特定业务账号，该特定业务账号的形式例如可以是765367XXX_QQ_music_VIP。
S202、所述第一基站根据所述连接状态信息确定所述第一基站是否满足索要所述UE上下文信息条件。
本发明实施例中，第一基站是否满足索要UE上下文信息，也就是说，第一基站是否可通过Context Fetch流程索要UE上下文信息。
在一发明实施例中，上述连接状态信息包括第二基站标识，上述第一基站根据上述连接状态信息确定所述第一基站是否满足索要UE上下文信息条件的具体实施方式为：上述第一基站根据上述第二基站标识判断是否存在用于连接上述第一基站与上述第二基站的接口；若不存在用于连接上述第一基站与上述 第二基站的接口，则上述第一基站确定上述第一基站不满足索要上述UE上下文信息条件。也就是说，第一基站根据第二基站的标识判断是否有第一基站和第二基站直接连接的X2网络连接接口，若没有，则第一基站不能通过Context Fetch流程向第二基站索要UE上下文信息，即第一基站不满足索要上述UE上下文信息条件。
在另一发明实施例中，上述连接状态信息包括UE所属的MME标识，上述第一基站根据上述连接状态信息确定所述第一基站是否满足索要UE上下文信息条件的具体实施方式为：上述第一基站根据上述UE所属的MME标识判断上述第一基站是否与上述UE所属的MME连接；若上述第一基站未与上述UE所属的MME连接，则上述第一基站确定上述第一基站不满足索要上述UE上下文信息条件。也就是说，第一基站根据上述UE所属的MME标识判断是第一基站和第二基站是否连接到同一个MME，若没有，则第一基站不能通过Context Fetch流程向UE所属的MME标识索要UE上下文信息，即第一基站不满足索要上述UE上下文信息条件。
S203、若所述第一基站确定所述第一基站未满足索要所述UE上下文信息条件，所述第一基站向移动性管理实体MME发送所述UE上下文信息建立请求。
在一本发明实施例中，上述第一基站向移动性管理实体MME发送所述UE上下文信息建立请求的具体实施方式为：若不存在用于连接上述第一基站与所述第二基站的接口，即不存在用于连接上述第一基站与所述第二基站的接口的X2网络连接接口，在上述第一基站与所述UE所属的MME连接的情况下，第一基站向UE所属的MME发送上述UE上下文信息建立请求，上述UE上下文信息建立请求携带UE的初始消息，上述初始UE消息包括UE的标识和第二基站的标识等等，上述UE上下文信息建立请求用于触发上述UE所属的MME根据上述UE的初始消息向所述第二基站索要所述UE的上下文信息。其中，UE所属的MME根据上述UE的初始消息向所述第二基站索要所述UE的上下文信息的具体实施方式为：UE所属的MME根据第二基站的标识向第二基站发送UE上下文信息获取请求，上述UE上下文信息获取请求携带UE的标识，以便于第二基站根据UE的标识获取上述UE的上下文信息，并将上 述UE的上下文信息发送给UE所属的MME。
在另一发明实施例中，上述第一基站向移动性管理实体MME发送所述UE上下文信息建立请求的具体实施方式为：若所述第一基站未与所述UE所属的MME连接，即表示第一基站不能通过Context Fetch向UE所属的MME索要UE的上下文信息，则第一基站向上述MME发送上述UE上下文信息建立请求，上述MME不同于UE所属的MME，上述UE上下文信息建立请求携带上述UE标识和上述UE所属的MME标识，上述UE上下文信息建立请求用于触发上述MME根据上述UE所属的MME标识向上述UE所属的MME索要所述UE的上下文信息。上述MME为第一基站在接收到UE发送的第二RRC连接建立请求之后，第一基站从第一基站所有可连接的MME任意选择其中一个MME，若第一基站所有可连接的MME的数量为大于1时，第一基站选择MME的具体实施方式为：第一基站根据MME的优先级选择优先级比较高的MME作为上述MME。其中，上述第二RRC连接建立请求为UE在接收到第一基站发送的上述第一RRC连接建立请求的拒绝消息时，UE向第一基站发送的。其中，上述拒绝消息用于触发所述UE执行TAU。
S204、所述第一基站接收所述MME响应所述UE上下文信息建立请求而发送的响应消息，所述响应消息携带所述UE上下文信息。
本发明实施例中，UE上下文信息中至少包括UE的ID，从而使得第一基站在RRC连接重建立时，根据UE上下文信息判断请求重建立的UE是否合法，从而决定是否允许RRC重建，若UE上下文信息不存在UE的ID，则RRC重建会被拒绝。
可以看出，本发明实施例中，第一基站在接收UE发送的RRC连接建立请求，第一基站根据RRC连接建立请求携带的UE在发送RRC连接建立请求之前的连接状态信息确定第一基站不满足索要UE上下文信息条件，即不能通过Context Fetch索要UE上下文信息时，第一基站向移动性管理实体MME发送所述UE上下文信息建立请求，在所述MME建立完成所述UE上下文信息时向所述第一基站发送的响应消息，所述响应消息携带所述UE上下文信息，以使得第一基站根据所述UE上下文信息完成RRC连接重建立流程，进而避免UE在切换失败后，释放UE再重新建立连接的信令和时延，从而有利于业 务的快速恢复。
可选的，在第一基站向移动性管理实体MME发送所述UE上下文信息建立请求之前，图2所示的用户设备上下文信息的获取方法还包括：所述第一基站向所述UE发送所述第一RRC连接建立请求的拒绝消息，所述拒绝消息用于触发所述UE执行TAU；所述第一基站接收所述UE发送的第二RRC连接建立请求；并根据所述第二RRC连接建立请求选取除所述UE所属的MME之外的MME。
可选的，在所述第一基站接收所述MME响应所述UE上下文信息建立请求而发送的响应消息之后，图2所示的用户设备上下文信息的获取方法还包括：所述第一基站向所述UE发送RRC连接重建立完成响应，所述RRC连接重建立完成响应携带配置指示、安全初始化指示、配置信息以及安全参数。
可选的，在所述第一基站接收所述MME响应所述UE上下文信息建立请求而发送的响应消息之后，图2所示的用户设备上下文信息的获取方法还包括：所述第一基站接收所述第二基站发送的缓存数据。
请参见图3，图3为本发明实施例提供的一种用户设备上下文信息的获取方法的第二实施例流程图。其中，如图3所示，本发明的一个实施例提供的一种用户设备上下文信息的获取方法可以包括步骤S301～S303：
S301、用户设备UE接收第二基站发送的所述UE自主移动参数。
本发明实施例中，在第二基站允许UE在长DRX状态下自主移动时，则第二基站向UE发送DRX配置信息，上述DRX配置信息包括UE自主移动参数，上述UE自主移动参数包括UE自主移动的触发时机、UE自主移动的范围、UE自主移动停止时机、UE发起RRC连接重建立的时机。其中，上述UE自主移动的触发时机为UE默认UE进入到长DRX的睡眠期，UE进入UE自主移动状态的时机，上述UE进入长DRX睡眠期包括：长DRX非激活定时器超时；或者，长DRX唤醒时超时；或者UE直接接收到长DRX命令等；或者，UE自主移动的触发时机为一具体时间，比如UE进入长DRX睡眠期起一段时间后，UE进入UE自主移动状态的时机；又如服务小区的信号质量差于预设的门限，UE进入自主移动状态的时机等。上述UE自主移动的范围为 网络可以控制UE自主移动的范围，只允许UE在一定的范围内自主移动，比如配置可移动的小区，频率，TA列表等，并配置候选移动小区的优先级，UE按照一定的优先级规则在上述E自主移动的范围内自主移动。上述UE自主移动停止时机为配置UE自主移动的禁止时间(Prohibit timer)，在这个时间内，UE停止自主移动。上述UE自主移动停止时机可以位于UE进入DRX醒来的前一段时间，这样UE可以在醒来的时候快速上报测量报告，触发网络控制的切换等。上述UE发起RRC连接重建立的时机为UE检测到更换到一个新的小区或者更换到一个新的基站时，UE向新的基站或是新的小区所属的基站发起RRC连接重建立的时机。
S302、所述UE根据所述UE自主移动参数选取第一基站。
本发明实施例中，UE根据所述UE自主移动参数选取第一基站的具体实施方式为：UE根据UE自主移动参数包括的UE自主移动的范围选取第一基站，举例来说，UE根据自主移动范围内的小区的优先级在自主移动的范围内选择优先级较高的小区作为RRC重建小区，或者，UE根据自主移动范围内的小区信号质量在自主移动的范围内选择信号质量较强的小区作为RRC重建小区等等，然后UE将上述RRC重建小区所属的基站作为第一基站。
S303、所述UE根据所述UE自主移动参数向所述第一基站发送第一无线资源控制RRC连接建立请求，所述第一RRC连接建立请求携带所述UE在发送所述第一RRC连接建立请求之前的连接状态信息，所述第一RRC连接建立请求用于指示所述第一基站根据所述连接状态信息确定所述第一基站未满足索要UE上下文信息条件时，向移动性管理实体MME发送所述UE上下文信息建立请求。
本发明实施例中，用户设备UE发送的第一无线资源控制RRC连接建立请求的具体实施方式为：UE根据上述UE自主移动参数，在进入长DRX睡眠态后，UE进行自主移动(比如进行小区重选)，在UE更换小区后，UE根据上述UE自主移动参数包括的UE发起RRC连接重建立的时机向第一基站发送第一无线资源控制RRC连接建立请求。其中，上述第一RRC连接建立请求携带UE在发送第一RRC连接建立请求之前的连接状态信息，上述连接状态信息包括UE标识，RRC连接重建立原因、原小区标识、或是原基站标识(即 第二基站标识)等等。其中，UE标识可以是UE的SIM卡号，或者IMSI，或者MSISDN等关联用户整体数据业务状态的整体业务账号，该整体业务账号例如可以与通常的手机包月流量账号对应，即在该整体业务账号下，用户利用UE进行上网、邮件、聊天、文件传输、视频等日常应用所消耗的流量均计入该整体业务账号对应的流量资费中；上述UE的数据业务账号还可以是QQ音乐畅听流量包、绿钻畅听流量包、乐视视频内容流量包等关联用户特定数据业务状态的特定业务账号，在该特定业务账号所对应的业务下，用户通过UE使用该业务并消耗的流量只计入该特定业务账号，而不会计入上述整体业务账号，例如某用户购买了QQ音乐畅听流量包，则OCS系统应生成一个与该用户的QQ音乐畅听业务对应的特定业务账号，该特定业务账号的形式例如可以是765367XXX_QQ_music_VIP。
本发明实施例中，所述第一RRC连接建立请求用于指示所述第一基站根据所述连接状态信息确定所述第一基站未满足索要UE上下文信息条件时，向移动性管理实体MME发送所述UE上下文信息建立请求。其中，第一基站是否满足索要UE上下文信息，也就是说，第一基站是否可通过Context Fetch流程索要UE上下文信息。
在一发明实施例中，上述连接状态信息包括第二基站标识，上述第一基站根据上述连接状态信息确定所述第一基站是否满足索要UE上下文信息条件的具体实施方式为：上述第一基站根据上述第二基站标识判断是否存在用于连接上述第一基站与上述第二基站的接口；若不存在用于连接上述第一基站与上述第二基站的接口，则上述第一基站确定上述第一基站不满足索要上述UE上下文信息条件。也就是说，第一基站根据第二基站的标识判断是否有第一基站和第二基站直接连接的X2网络连接接口，若没有，则第一基站不能通过Context Fetch流程向第二基站索要UE上下文信息，即第一基站不满足索要上述UE上下文信息条件。
在另一发明实施例中，上述连接状态信息包括UE所属的MME标识，上述第一基站根据上述连接状态信息确定所述第一基站是否满足索要UE上下文信息条件的具体实施方式为：上述第一基站根据上述UE所属的MME标识判断上述第一基站是否与上述UE所属的MME连接；若上述第一基站未与上述 UE所属的MME连接，则上述第一基站确定上述第一基站不满足索要上述UE上下文信息条件。也就是说，第一基站根据上述UE所属的MME标识判断是第一基站和第二基站是否连接到同一个MME，若没有，则第一基站不能通过Context Fetch流程向UE所属的MME标识索要UE上下文信息，即第一基站不满足索要上述UE上下文信息条件。
在一本发明实施例中，上述第一基站向移动性管理实体MME发送所述UE上下文信息建立请求的具体实施方式为：若不存在用于连接上述第一基站与所述第二基站的接口，即不存在用于连接上述第一基站与所述第二基站的接口的X2网络连接接口，且在所述第一基站与所述UE所属的MME连接的情况下，第一基站向UE所属的MME发送上述UE上下文信息建立请求，上述UE上下文信息建立请求携带UE的初始消息，上述初始UE消息包括UE的标识和第二基站的标识等等，上述UE上下文信息建立请求用于触发上述UE所属的MME根据上述UE的初始消息向所述第二基站索要所述UE的上下文信息。其中，UE所属的MME根据上述UE的初始消息向所述第二基站索要所述UE的上下文信息的具体实施方式为：UE所属的MME根据第二基站的标识向第二基站发送UE上下文信息获取请求，上述UE上下文信息获取请求携带UE的标识，以便于第二基站根据UE的标识获取上述UE的上下文信息，并将上述UE的上下文信息发送给UE所属的MME。
在另一发明实施例中，上述第一基站向移动性管理实体MME发送所述UE上下文信息建立请求的具体实施方式为：若所述第一基站未与所述UE所属的MME连接，即表示第一基站不能通过Context Fetch向UE所属的MME索要UE的上下文信息，则第一基站向上述MME发送上述UE上下文信息建立请求，上述MME不同于UE所属的MME，上述UE上下文信息建立请求携带上述UE标识和上述UE所属的MME标识，上述UE上下文信息建立请求用于触发上述MME根据上述UE所属的MME标识向上述UE所属的MME索要所述UE的上下文信息。上述MME为第一基站在接收到UE发送的第二RRC连接建立请求之后，第一基站从第一基站所有可连接的MME任意选择其中一个MME，若第一基站所有可连接的MME的数量为大于1时，第一基站选择MME的具体实施方式为：第一基站根据MME的优先级选择优先级比 较高的MME作为上述MME。其中，上述第二RRC连接建立请求为UE在接收到第一基站发送的上述第一RRC连接建立请求的拒绝消息时，UE向第一基站发送的。其中，上述拒绝消息用于触发所述UE执行TAU。
可以看出，本发明实施例中，第一基站在接收UE发送的RRC连接建立请求，第一基站根据RRC连接建立请求携带的UE在发送RRC连接建立请求之前的连接状态信息确定第一基站不满足索要UE上下文信息条件，即不能通过Context Fetch索要UE上下文信息时，第一基站向移动性管理实体MME发送所述UE上下文信息建立请求，在所述MME建立完成所述UE上下文信息时向所述第一基站发送的响应消息，所述响应消息携带所述UE上下文信息，以使得第一基站根据所述UE上下文信息完成RRC连接重建立流程，进而避免UE在切换失败后，释放UE再重新建立连接的信令和时延，从而有利于业务的快速恢复。
可选的，在UE根据所述UE自主移动参数向第一基站发送第一无线资源控制RRC连接建立请求之后，图3所示的用户设备上下文信息的获取方法还包括：所述UE接收所述第一基站发送的RRC连接重建立完成响应，所述RRC连接重建立完成响应携带配置指示、安全初始化指示、配置信息以及安全参数；所述UE根据所述配置指示删除初始配置信息，并使用所述配置信息；所述UE根据所述安全初始化指示激活所述安全参数。由于第一基站获取了新的UE上下文信息后，新的上下文信息包含有上述安全参数(即新的安全参数，如新的KeNB)，则第一基站需要根据新的KeNB)激活UE的安全参数，因此第一基站向UE发送的RRC连接重建立完成响应携带安全初始化指示，以使得UE根据上述安全参数初始衍生秘钥，并向NAS层发送安全初始化指示，该安全初始化指示携带上述安全参数，以使得NAS同时根据上述安全参数初始化安全秘钥。
可选的，UE根据所述UE自主移动参数向第一基站发送无线资源控制RRC连接建立请求之后，图3所示的用户设备上下文信息的获取方法还包括：所述UE接收所述第一基站发送的所述第一RRC连接建立请求的拒绝消息，所述拒绝消息所述第一基站；所述UE执行TAU流程，并向所述第一基站发送第二RRC连接建立请求；所述第二RRC连接建立请求用于触发所述第一基 站选取除所述UE所属的MME之外的MME。
请参见图4，图4为本发明实施例提供的一种用户设备上下文信息的获取方法的第三实施例流程图。其中，如图4所示，本发明的一个实施例提供的一种用户设备上下文信息的获取方法可以包括步骤S401～S418：
S401、第二基站向用户设备UE发送UE自主移动参数。
本发明实施例中，在第二基站允许UE在长DRX状态下自主移动时，则第二基站向UE发送DRX配置信息，上述DRX配置信息包括UE自主移动参数，上述UE自主移动参数包括UE自主移动的触发时机、UE自主移动的范围、UE自主移动停止时机、UE发起RRC连接重建立的时机。其中，上述UE自主移动的触发时机为UE默认UE进入到长DRX的睡眠期，UE进入UE自主移动状态的时机，上述UE进入长DRX睡眠期包括：长DRX非激活定时器超时；或者，长DRX唤醒时超时；或者UE直接接收到长DRX命令等；或者，UE自主移动的触发时机为一具体时间，比如UE进入长DRX睡眠期起一段时间后，UE进入UE自主移动状态的时机；又如服务小区的信号质量差于预设的门限，UE进入自主移动状态的时机等。上述UE自主移动的范围为网络可以控制UE自主移动的范围，只允许UE在一定的范围内自主移动，比如配置可移动的小区，频率，TA列表等，并配置候选移动小区的优先级，UE按照一定的优先级规则在上述UE自主移动的范围内自主移动。上述UE自主移动停止时机为配置UE自主移动的禁止时间(Prohibit timer)，在这个时间内，UE停止自主移动。上述UE自主移动停止时机可以位于UE进入DRX醒来的前一段时间，这样UE可以在醒来的时候快速上报测量报告，触发网络控制的切换等。上述UE发起RRC连接重建立的时机为UE检测到更换到一个新的小区或者更换到一个新的基站时，UE向新的基站或是新的小区所属的基站发起RRC连接重建立的时机。
S402、所述UE接收所述第一基站发送的所述UE自主移动参数。
S403、在所述UE进入长DRX睡眠态后，所述UE根据所述UE自主移动参数选取第一基站。
本发明实施例中，UE根据所述UE自主移动参数选取第一基站的具体实 施方式为：UE根据UE自主移动参数包括的UE自主移动的范围选取第一基站，举例来说，UE根据自主移动范围内的小区的优先级在自主移动的范围内选择优先级较高的小区作为RRC重建小区，或者，UE根据自主移动范围内的小区信号质量在自主移动的范围内选择信号质量较强的小区作为RRC重建小区等等，然后UE将上述RRC重建小区所属的基站作为第一基站。
S404、所述UE向所述第一基站发送第一发送RRC连接建立请求。
本发明实施例中，用户设备UE发送的第一无线资源控制RRC连接建立请求的具体实施方式为：UE根据上述UE自主移动参数，在进入长DRX睡眠态后，UE进行自主移动(比如进行小区重选)，在UE更换小区后，UE根据上述UE自主移动参数包括的UE发起RRC连接重建立的时机向第一基站发送第一无线资源控制RRC连接建立请求。其中，上述第一RRC连接建立请求携带UE在发送第一RRC连接建立请求之前的连接状态信息，上述连接状态信息包括UE标识，RRC连接重建立原因、原小区标识、或是原基站标识(即第二基站标识)等等。其中，UE标识可以是UE SIM卡号，或者IMSI，或者，MSISDN等关联用户整体数据业务状态的整体业务账号，该整体业务账号例如可以与通常的手机包月流量账号对应，即在该整体业务账号下，用户利用UE进行上网、邮件、聊天、文件传输、视频等日常应用所消耗的流量均计入该整体业务账号对应的流量资费中；上述UE的数据业务账号还可以是QQ音乐畅听流量包、绿钻畅听流量包、乐视视频内容流量包等关联用户特定数据业务状态的特定业务账号，在该特定业务账号所对应的业务下，用户通过UE使用该业务并消耗的流量只计入该特定业务账号，而不会计入上述整体业务账号，例如某用户购买了QQ音乐畅听流量包，则OCS系统应生成一个与该用户的QQ音乐畅听业务对应的特定业务账号，该特定业务账号的形式例如可以是765367XXX_QQ_music_VIP。
S405、所述第一基站接收所述UE发送的所述第一RRC连接建立请求，所述第一RRC连接建立请求携带所述UE在发送所述第一RRC连接建立请求之前的连接状态信息，所述连接状态信息包括第二基站标识。
S406、所述第一基站根据所述第二基站标识判断是否存在用于连接所述第一基站与所述第二基站的接口。
若是，则第一基站通过context fetch流程向第二基站索要UE上下文，进而完成UE在第一基站的RRC连接重建立。
若否，则执行步骤S407。
本发明实施例中，第一基站根据第二基站的标识判断是否有第一基站和第二基站直接连接的X2网络连接接口，若没有，则第一基站不能通过Context Fetch流程向第二基站索要UE上下文信息，即第一基站不满足索要上述UE上下文信息条件。
S407、所述连接状态信息包括UE所属的MME标识，所述第一基站根据所述UE所属的MME标识确定第一基站是否与所述UE所属的MME连接。
若是，则执行步骤S408。
若否，则执行本发明实施例提供的用户设备上下文信息的获取方法的第四实施例中的步骤S507～517。
S408、所述第一基站向所述MME发送所述UE上下文信息建立请求，所述MME为所述UE所属的MME，所述UE上下文信息建立请求携带UE的初始消息，所述初始UE消息包括UE的标识和第二基站的标识。
S409、所述MME接收所述第一基站发送的所述UE上下文信息建立请求。
本发明实施例中，在MME接收所述第一基站发送的所述UE上下文信息建立请求之后，上述MME根据上述UE的初始消息向所述第二基站索要所述UE的上下文信息，其中，上述MME根据上述UE的初始消息向所述第二基站索要所述UE的上下文信息的具体实施方式为：上述MME根据第二基站的标识向第二基站发送UE上下文信息获取请求，上述UE上下文信息获取请求携带UE的标识，以便于第二基站根据UE的标识获取上述UE的上下文信息，并将上述UE的上下文信息发送给上述MME。
S410、所述MME响应所述UE上下文信息建立请求而向第一基站发送响应消息，所述响应消息携带所述UE上下文信息。
S411、所述第一基站接收所述MME响应所述UE上下文信息建立请求而发送的响应消息。
S412、所述第一基站向所述UE发送RRC连接重建立完成响应，所述 RRC连接重建立完成响应携带配置指示、安全初始化指示、配置信息以及安全参数。
S413、所述UE接收所述第一基站发送的RRC连接重建立完成响应。
S414、所述UE根据所述配置指示删除初始配置信息，并使用所述配置信息；所述UE根据所述安全初始化指示激活所述安全参数。
本发明实施例中，由于第一基站获取了新的UE上下文信息后，新的上下文信息包含有上述安全参数(即新的安全参数，如新的KeNB)，则第一基站需要根据新的KeNB)激活UE的安全参数，因此第一基站向UE发送的RRC连接重建立完成响应携带安全初始化指示，以使得UE根据上述安全参数初始衍生秘钥，并向NAS层发送安全初始化指示，该安全初始化指示携带上述安全参数，以使得NAS同时根据上述安全参数初始化安全秘钥。
S415、当所述MME检测到所述MME与所述第二基站连接时，所述MME向所述第二基站发送UE上下文释放请求，所述UE上下文释放请求携带有第一基站的标识或数据转发地址。
本发明实施例中，MME在建立好UE的上下文后，MME检测到MME与第二基站还保持着S1连接时，MME向第二基站发送UE上下文释放请求，上述UE上下文释放请求携带有第一基站的标识或数据转发地址，以使得第二基站将缓存的数据转发至第一基站。
S416、所述第二基站接收所述MME发送的所述UE上下文释放请求。
S417、所述第二基站根据所述UE上下文释放请求携带有第一基站的标识或数据转发地址向所述第一基站发送缓存数据。
S418、所述第一基站接收所述第二基站发送的缓存数据。
可以看出，本发明实施例中，第一基站在接收UE发送的RRC连接建立请求，第一基站根据RRC连接建立请求携带的UE在发送RRC连接建立请求之前的连接状态信息确定第一基站不满足索要UE上下文信息条件，即不能通过Context Fetch索要UE上下文信息时，第一基站向移动性管理实体MME发送所述UE上下文信息建立请求，在所述MME建立完成所述UE上下文信息时向所述第一基站发送的响应消息，所述响应消息携带所述UE上下文信息，以使得第一基站根据所述UE上下文信息完成RRC连接重建立流程，进而避 免UE在切换失败后，释放UE再重新建立连接的信令和时延，从而有利于业务的快速恢复。
请参见图5，图5为本发明实施例提供的一种用户设备上下文信息的获取方法的第四实施例流程图。其中，如图5所示，本发明的一个实施例提供的一种用户设备上下文信息的获取方法可以包括步骤S501～S524：
S501、第二基站向用户设备UE发送UE自主移动参数。
本发明实施例中，在第二基站允许UE在长DRX状态下自主移动时，则第二基站向UE发送DRX配置信息，上述DRX配置信息包括UE自主移动参数，上述UE自主移动参数包括UE自主移动的触发时机、UE自主移动的范围、UE自主移动停止时机、UE发起RRC连接重建立的时机。其中，上述UE自主移动的触发时机为UE默认UE进入到长DRX的睡眠期，UE进入UE自主移动状态的时机，上述UE进入长DRX睡眠期包括：长DRX非激活定时器超时；或者，长DRX唤醒时超时；或者UE直接接收到长DRX命令等；或者，UE自主移动的触发时机为一具体时间，比如UE进入长DRX睡眠期起一段时间后，UE进入UE自主移动状态的时机；又如服务小区的信号质量差于预设的门限，UE进入自主移动状态的时机等。上述UE自主移动的范围为网络可以控制UE自主移动的范围，只允许UE在一定的范围内自主移动，比如配置可移动的小区，频率，TA列表等，并配置候选移动小区的优先级，UE按照一定的优先级规则在上述UE自主移动的范围内自主移动。上述UE自主移动停止时机为配置UE自主移动的禁止时间(Prohibit timer)，在这个时间内，UE停止自主移动。上述UE自主移动停止时机可以位于UE进入DRX醒来的前一段时间，这样UE可以在醒来的时候快速上报测量报告，触发网络控制的切换等。上述UE发起RRC连接重建立的时机为UE检测到更换到一个新的小区或者更换到一个新的基站时，UE向新的基站或是新的小区所属的基站发起RRC连接重建立的时机。
S502、所述UE接收所述第一基站发送的所述UE自主移动参数。
S503、在所述UE进入长DRX睡眠态后，所述UE根据所述UE自主移动参数选取第一基站。
本发明实施例中，UE根据所述UE自主移动参数选取第一基站的具体实施方式为：UE根据UE自主移动参数包括的UE自主移动的范围选取第一基站，举例来说，UE根据自主移动范围内的小区的优先级在自主移动的范围内选择优先级较高的小区作为RRC重建小区，或者，UE根据自主移动范围内的小区信号质量在自主移动的范围内选择信号质量较强的小区作为RRC重建小区等等，然后UE将上述RRC重建小区所属的基站作为第一基站。
S504、所述UE向所述第一基站发送第一发送RRC连接建立请求。
本发明实施例中，用户设备UE发送的第一无线资源控制RRC连接建立请求的具体实施方式为：UE根据上述UE自主移动参数，在进入长DRX睡眠态后，UE进行自主移动(比如进行小区重选)，在UE更换小区后，UE根据上述UE自主移动参数包括的UE发起RRC连接重建立的时机向第一基站发送第一无线资源控制RRC连接建立请求。其中，上述第一RRC连接建立请求携带UE在发送第一RRC连接建立请求之前的连接状态信息，上述连接状态信息包括UE标识，RRC连接重建立原因、原小区标识、或是原基站标识(即第二基站标识)等等。其中，UE标识可以是UE SIM卡号，或者IMSI，或者，MSISDN等关联用户整体数据业务状态的整体业务账号，该整体业务账号例如可以与通常的手机包月流量账号对应，即在该整体业务账号下，用户利用UE进行上网、邮件、聊天、文件传输、视频等日常应用所消耗的流量均计入该整体业务账号对应的流量资费中；上述UE的数据业务账号还可以是QQ音乐畅听流量包、绿钻畅听流量包、乐视视频内容流量包等关联用户特定数据业务状态的特定业务账号，在该特定业务账号所对应的业务下，用户通过UE使用该业务并消耗的流量只计入该特定业务账号，而不会计入上述整体业务账号，例如某用户购买了QQ音乐畅听流量包，则OCS系统应生成一个与该用户的QQ音乐畅听业务对应的特定业务账号，该特定业务账号的形式例如可以是765367XXX_QQ_music_VIP。
S505、所述第一基站接收所述UE发送的所述第一RRC连接建立请求，所述第一RRC连接建立请求携带所述UE在发送所述第一RRC连接建立请求之前的连接状态信息，所述连接状态信息包括所述UE所属的MME标识。
S506、所述第一基站根据所述UE所属的MME标识判断所述第一基站 是否与所述UE所属的MME连接。
若是，则执行本发明实施例提供的用户设备上下文信息的获取方法的第三实施例中的步骤S408～411。
若否，则执行步骤S507。
本发明实施例中，第一基站根据上述UE所属的MME标识判断是第一基站和第二基站是否连接到同一个MME，若没有，则第一基站不能通过Context Fetch流程向UE所属的MME标识索要UE上下文信息，即第一基站不满足索要上述UE上下文信息条件。
S507、所述第一基站向所述UE发送所述第一RRC连接建立请求的拒绝消息，所述拒绝消息用于触发所述UE执行TAU。
S508、所述UE接收所述第一基站发送的所述第一RRC连接建立请求的拒绝消息。
S509、所述UE执行TAU流程，并向所述第一基站发送第二RRC连接建立请求；
S510、所述第一基站接收所述UE发送的所述第二RRC连接建立请求，并根据所述第二RRC连接建立请求选取第二MME，所述第二MME为除所述UE所属的MME之外的MME。
本发明实施例中，上述第二MME为第一基站在接收到UE发送的第二RRC连接建立请求之后，第一基站从第一基站所有可连接的MME任意选择的其中一个MME，若第一基站所有可连接的MME的数量为大于1时，第一基站选择MME的具体实施方式为：第一基站根据MME的优先级选择优先级比较高的MME作为上述第二MME。
S511、所述第一基站向所述第二MME发送所述UE上下文信息建立请求。
S512、所述第二MME接收所述第一基站发送的所述UE上下文信息建立请求，所述UE上下文信息建立请求携带所述UE标识和所述UE所属的MME标识。
S513、所述第二MME根据所述UE所属的MME标识向第一MME发送所述UE上下文信息获取请求，所述第一MME为所述UE所属的MME，所 述UE上下文信息获取请求携带所述UE标识。
S514、所述第一MME根据所述UE标识获取所述UE上下文信息，并向所述第二MME发送所述UE上下文信息。
S515、所述第二MME接收所述第一MME发送的所述UE上下文信息。
S516、所述第二MME向所述第一基站发送所述UE上下文信息建立请求的响应消息。
S517、所述第一基站接收所述第二MME响应所述UE上下文信息建立请求而发送的所述响应消息，所述响应消息携带所述UE上下文信息。
S518、所述第一基站向所述UE发送RRC连接重建立完成响应，所述RRC连接重建立完成响应携带配置指示、安全初始化指示、配置信息以及安全参数。
S519、所述UE接收所述第一基站发送的RRC连接重建立完成响应。
S520、所述UE根据所述配置指示删除初始配置信息，并使用所述配置信息；所述UE根据所述安全初始化指示激活所述安全参数。
本发明实施例中，由于第一基站获取了新的UE上下文信息后，新的上下文信息包含有上述安全参数(即新的安全参数，如新的KeNB)，则第一基站需要根据新的KeNB)激活UE的安全参数，因此第一基站向UE发送的RRC连接重建立完成响应携带安全初始化指示，以使得UE根据上述安全参数初始衍生秘钥，并向NAS层发送安全初始化指示，该安全初始化指示携带上述安全参数，以使得NAS同时根据上述安全参数初始化安全秘钥。
S521、当所述第一MME检测到所述第一MME与所述第二基站连接时，所述第一MME向所述第二基站发送UE上下文释放请求，所述UE上下文释放请求携带有第一基站的标识或数据转发地址。
本发明实施例中，第一MME在建立好UE的上下文后，第一MME检测到第一MME与第二基站还保持着S1连接时，第一MME向第二基站发送UE上下文释放请求，上述UE上下文释放请求携带有第一基站的标识或数据转发地址，以使得第二基站将缓存的数据转发至第一基站。
S522、所述第二基站接收所述第一MME发送的所述UE上下文释放请求。
S523、所述第二基站根据所述UE上下文释放请求携带有第一基站的标识或数据转发地址向所述第一基站发送缓存数据。
S524、所述第一基站接收所述第二基站发送的缓存数据。
可以看出，本发明实施例中，第一基站在接收UE发送的RRC连接建立请求，第一基站根据RRC连接建立请求携带的UE在发送RRC连接建立请求之前的连接状态信息确定第一基站不满足索要UE上下文信息条件，即不能通过Context Fetch索要UE上下文信息时，第一基站向移动性管理实体MME发送所述UE上下文信息建立请求，在所述MME建立完成所述UE上下文信息时向所述第一基站发送的响应消息，所述响应消息携带所述UE上下文信息，以使得第一基站根据所述UE上下文信息完成RRC连接重建立流程，进而避免UE在切换失败后，释放UE再重新建立连接的信令和时延，从而有利于业务的快速恢复。
请参见图6，本发明实施例提供的一种基站，可包括：
接收单元601，用于接收用户设备UE发送的第一无线资源控制RRC连接建立请求，所述第一RRC连接建立请求携带所述UE在发送所述第一RRC连接建立请求之前的连接状态信息；
确定单元602，用于根据所述连接状态信息确定所述第一基站是否满足索要所述UE上下文信息条件；
发送单元603，用于若所述确定单元确定所述第一基站未满足索要所述UE上下文信息条件，向移动性管理实体MME发送所述UE上下文信息建立请求；
所述接收单元601，还用于接收所述MME响应所述UE上下文信息建立请求而发送的响应消息，所述响应消息携带所述UE上下文信息。
其中，所述连接状态信息包括所述UE所属的MME标识，所述确定单元具体用于：根据所述UE所属的MME标识判断所述第一基站是否与所述UE所属的MME连接；若所述第一基站未与所述UE所属的MME连接，则所述确定单元确定所述第一基站不满足索要所述UE上下文信息条件。
其中，所述MME不同于所述UE所属的MME，所述UE上下文信息建 立请求携带所述UE标识和所述UE所属的MME标识，所述UE上下文信息建立请求用于触发所述MME根据所述UE所属的MME标识向所述UE所属的MME索要所述UE的上下文信息。
其中，所述连接状态信息包括第二基站标识，所述确定单元具体用于：根据所述第二基站标识判断是否存在用于连接所述第一基站与所述第二基站的接口；若不存在用于连接所述第一基站与所述第二基站的接口，则所述确定单元确定所述第一基站不满足索要所述UE上下文信息条件。
其中，所述MME为所述UE所属的MME，所述第一基站与所述UE所属的MME连接，所述UE上下文信息建立请求携带所述UE的初始消息，所述UE上下文信息建立请求用于触发所述UE所属的MME根据所述UE的初始消息向所述第二基站索要所述UE的上下文信息。
可选的，在发送单元603向移动性管理实体MME发送所述UE上下文信息建立请求之前，所述发送单元603还用于向所述UE发送所述第一RRC连接建立请求的拒绝消息，所述拒绝消息用于触发所述UE执行TAU；所述接收单元601还用于接收所述UE发送的第二RRC连接建立请求；并根据所述第二RRC连接建立请求选取除所述UE所属的MME之外的MME。
可选的，在所述接收单元601接收所述MME响应所述UE上下文信息建立请求而发送的响应消息之后，所述发送单元603还用于向所述UE发送RRC连接重建立完成响应，所述RRC连接重建立完成响应携带配置指示、安全初始化指示、配置信息以及安全参数。
可选的，在所述接收单元601接收所述MME响应所述UE上下文信息建立请求而发送的响应消息之后，所述接收单元还用于接收所述第二基站发送的缓存数据。
可以理解的是，本实施例的基站的各功能模块的功能可根据上述方法实施例中的方法具体实现，其具体实现过程可以参照上述方法实施例的相关描述，此处不再赘述。基站中的部分或全部功能模块可由硬件电路实现，基站中的部分或全部功能模块也可由处理器(如数字信号处理器)通过完成执行代码或指令来实现。
可以看出，本发明实施例中，第一基站在接收UE发送的RRC连接建立 请求，第一基站根据RRC连接建立请求携带的UE在发送RRC连接建立请求之前的连接状态信息确定第一基站不满足索要UE上下文信息条件，即不能通过Context Fetch索要UE上下文信息时，第一基站向移动性管理实体MME发送所述UE上下文信息建立请求，在所述MME建立完成所述UE上下文信息时向所述第一基站发送的响应消息，所述响应消息携带所述UE上下文信息，以使得第一基站根据所述UE上下文信息完成RRC连接重建立流程，进而避免UE在切换失败后，释放UE再重新建立连接的信令和时延，从而有利于业务的快速恢复。
请参见图7，本发明实施例提供的一种用户设备UE，可包括：
接收单元701，用于接收第二基站发送的所述UE自主移动参数；
选取单元702，用于根据所述接收单元接收到的所述UE自主移动参数选取第一基站；
发送单元703，用于根据所述接收单元接收到的所述UE自主移动参数向所述第一基站发送第一无线资源控制RRC连接建立请求；
其中，所述第一RRC连接建立请求携带所述UE在发送所述第一RRC连接建立请求之前的连接状态信息，所述第一RRC连接建立请求用于指示所述第一基站根据所述连接状态信息确定所述第一基站未满足索要UE上下文信息条件时，向移动性管理实体MME发送所述UE上下文信息建立请求。
可选的，在发送单元703根据所述接收单元接收到的所述UE自主移动参数向所述第一基站发送第一无线资源控制RRC连接建立请求之后，所述接收单元，还用于接收所述第一基站发送的RRC连接建立完成响应，所述RRC连接重建立完成响应携带配置指示、安全初始化指示、配置信息以及安全参数；所述UE还包括：处理单元，用于根据所述配置指示删除初始配置信息，并使用所述配置信息；根据所述安全初始化指示激活所述安全参数。
可选的，在发送单元703根据所述接收单元接收到的所述UE自主移动参数向所述第一基站发送第一无线资源控制RRC连接建立请求之后所述接收单元还用于接收所述第一基站发送的所述第一RRC连接建立请求的拒绝消息；所述处理单元，还用于UE执行TAU流程；所述发送单元，还用于向所述第 一基站发送第二RRC连接建立请求；所述第二RRC连接建立请求用于触发所述第一基站选取除所述UE所属的MME之外的MME。
可以理解的是，本实施例的UE的各功能模块的功能可根据上述方法实施例中的方法具体实现，其具体实现过程可以参照上述方法实施例的相关描述，此处不再赘述。UE中的部分或全部功能模块可由硬件电路实现，UE中的部分或全部功能模块也可由处理器(如数字信号处理器)通过完成执行代码或指令来实现。
可以看出，本发明实施例中，第一基站在接收UE发送的RRC连接建立请求，第一基站根据RRC连接建立请求携带的UE在发送RRC连接建立请求之前的连接状态信息确定第一基站不满足索要UE上下文信息条件，即不能通过Context Fetch索要UE上下文信息时，第一基站向移动性管理实体MME发送所述UE上下文信息建立请求，在所述MME建立完成所述UE上下文信息时向所述第一基站发送的响应消息，所述响应消息携带所述UE上下文信息，以使得第一基站根据所述UE上下文信息完成RRC连接重建立流程，进而避免UE在切换失败后，释放UE再重新建立连接的信令和时延，从而有利于业务的快速恢复。
请参见图8，图8为本发明实施例提供的用户设备UE的第二实施例结构示意图，可包括：处理器801和存储器802；其中，处理器801和存储器802通过总线803耦合连接。其中，所述处理器801可通过调用所述存储器801中的代码或指令以执行如下步骤：
处理器和存储器；其中，所述处理器通过调用所述存储器中的代码或指令以执行如下步骤：
接收第二基站发送的所述UE自主移动参数；
根据所述UE自主移动参数选取第一基站；
根据所述UE自主移动参数向所述第一基站发送第一无线资源控制RRC连接建立请求；
其中，所述第一RRC连接建立请求携带所述UE在发送所述第一RRC连接建立请求之前的连接状态信息，所述第一RRC连接建立请求用于指示所述 第一基站根据所述连接状态信息确定所述第一基站未满足索要UE上下文信息条件时，向移动性管理实体MME发送所述UE上下文信息建立请求。
可选的，在本发明一些可能的实现方式中，所述根据所述UE自主移动参数向第一基站发送第一无线资源控制RRC连接建立请求之后，所述处理器还用于：接收所述第一基站发送的RRC连接建立完成响应，所述RRC连接重建立完成响应携带配置指示、安全初始化指示、配置信息以及安全参数；根据所述配置指示删除初始配置信息，并使用所述配置信息；根据所述安全初始化指示激活所述安全参数。
可选的，在本发明一些可能的实现方式中，所述根据所述UE自主移动参数向第一基站发送第一无线资源控制RRC连接建立请求之后，所述处理器还用于：接收所述第一基站发送的所述第一RRC连接建立请求的拒绝消息；执行TAU流程，并向所述第一基站发送第二RRC连接建立请求；所述第二RRC连接建立请求用于触发所述第一基站选取除所述UE所属的MME之外的MME。
可以理解的是，本实施例的UE的各功能模块的功能可根据上述方法实施例中的方法具体实现，其具体实现过程可以参照上述方法实施例的相关描述，此处不再赘述。UE中的部分或全部功能模块可由硬件电路实现，UE中的部分或全部功能模块也可由处理器(如数字信号处理器)通过完成执行代码或指令来实现。
可以看出，本发明实施例中，第一基站在接收UE发送的RRC连接建立请求，第一基站根据RRC连接建立请求携带的UE在发送RRC连接建立请求之前的连接状态信息确定第一基站不满足索要UE上下文信息条件，即不能通过Context Fetch索要UE上下文信息时，第一基站向移动性管理实体MME发送所述UE上下文信息建立请求，在所述MME建立完成所述UE上下文信息时向所述第一基站发送的响应消息，所述响应消息携带所述UE上下文信息，以使得第一基站根据所述UE上下文信息完成RRC连接重建立流程，进而避免UE在切换失败后，释放UE再重新建立连接的信令和时延，从而有利于业务的快速恢复。
需要说明的是，对于前述的各方法实施例，为了简单描述，故将其都表述为一系列的动作组合，但是本领域技术人员应该知悉，本发明并不受所描述的动作顺序的限制，因为依据本发明，某些步骤可以采用其他顺序或者同时进行。其次，本领域技术人员也应该知悉，说明书中所描述的实施例均属于优选实施例，所涉及的动作和模块并不一定是本发明所必须的。
在上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其他实施例的相关描述。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置，可通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可为个人计算机、服务器或者网络设备等)执行本发明各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存 储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，以上实施例仅用以说明本发明的技术方案，而非对其限制；尽管参照前述实施例对本发明进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本发明各实施例技术方案的范围。

Claims (25)

  1. 一种用户设备上下文信息的获取方法，其特征在于，包括：
    第一基站接收用户设备UE发送的第一无线资源控制RRC连接建立请求，所述第一RRC连接建立请求携带所述UE在发送所述第一RRC连接建立请求之前的连接状态信息；
    所述第一基站根据所述连接状态信息确定所述第一基站是否满足索要所述UE上下文信息条件；
    若所述第一基站确定所述第一基站未满足索要所述UE上下文信息条件，所述第一基站向移动性管理实体MME发送所述UE上下文信息建立请求；
    所述第一基站接收所述MME响应所述UE上下文信息建立请求而发送的响应消息，所述响应消息携带所述UE上下文信息。
  2. 根据权利要求1所述的方法，其特征在于，所述连接状态信息包括所述UE所属的MME标识，所述第一基站根据所述连接状态信息确定所述第一基站是否满足向第二基站索要所述UE上下文信息条件，包括：
    所述第一基站根据所述UE所属的MME标识判断所述第一基站是否与所述UE所属的MME连接；
    若所述第一基站未与所述UE所属的MME连接，则所述第一基站确定所述第一基站不满足索要所述UE上下文信息条件。
  3. 根据权利要求2所述的方法，其特征在于，所述MME不同于所述UE所属的MME，所述UE上下文信息建立请求携带所述UE标识和所述UE所属的MME标识，所述UE上下文信息建立请求用于触发所述MME根据所述UE所属的MME标识向所述UE所属的MME索要所述UE的上下文信息。
  4. 根据权利要求1所述的方法，其特征在于，所述连接状态信息包括第二基站标识，所述第一基站根据所述连接状态信息确定所述第一基站是否满足索要所述UE上下文信息条件，包括：
    所述第一基站根据所述第二基站标识判断是否存在用于连接所述第一基站与所述第二基站的接口；
    若不存在用于连接所述第一基站与所述第二基站的接口，则所述第一基站 确定所述第一基站不满足索要所述UE上下文信息条件。
  5. 根据权利要求4所述的方法，其特征在于，所述MME为所述UE所属的MME，所述第一基站与所述UE所属的MME连接，所述UE上下文信息建立请求携带所述UE的初始消息，所述UE上下文信息建立请求用于触发所述UE所属的MME根据所述UE的初始消息向所述第二基站索要所述UE的上下文信息。
  6. 根据权利要求3所述的方法，其特征在于，所述第一基站向移动性管理实体MME发送所述UE上下文信息建立请求之前，所述方法还包括：
    所述第一基站向所述UE发送所述第一RRC连接建立请求的拒绝消息，所述拒绝消息用于触发所述UE执行TAU；
    所述第一基站接收所述UE发送的第二RRC连接建立请求；并根据所述第二RRC连接建立请求选取除所述UE所属的MME之外的MME。
  7. 根据权利要求1～6任一项所述的方法，其特征在于，所述第一基站接收所述MME响应所述UE上下文信息建立请求而发送的响应消息之后，所述方法还包括：所述第一基站向所述UE发送RRC连接重建立完成响应，所述RRC连接重建立完成响应携带配置指示、安全初始化指示、配置信息以及安全参数。
  8. 根据权利要求1～7任一项所述的方法，其特征在于，所述第一基站接收所述MME响应所述UE上下文信息建立请求而发送的响应消息之后，所述方法还包括：所述第一基站接收所述第二基站发送的缓存数据。
  9. 一种用户设备上下文信息的获取方法，其特征在于，包括：
    用户设备UE接收第二基站发送的所述UE自主移动参数；
    所述UE根据所述UE自主移动参数选取第一基站；
    所述UE根据所述UE自主移动参数向所述第一基站发送第一无线资源控制RRC连接建立请求；
    其中，所述第一RRC连接建立请求携带所述UE在发送所述第一RRC连接建立请求之前的连接状态信息，所述第一RRC连接建立请求用于指示所述第一基站根据所述连接状态信息确定所述第一基站未满足索要UE上下文信息条件时，向移动性管理实体MME发送所述UE上下文信息建立请求。
  10. 根据权利要求9所述的方法，其特征在于，所述UE根据所述UE自主移动参数向第一基站发送第一无线资源控制RRC连接建立请求之后，所述方法还包括：
    所述UE接收所述第一基站发送的RRC连接建立完成响应，所述RRC连接重建立完成响应携带配置指示、安全初始化指示、配置信息以及安全参数；
    所述UE根据所述配置指示删除初始配置信息，并使用所述配置信息；
    所述UE根据所述安全初始化指示激活所述安全参数。
  11. 根据权利要求9或10所述的方法，其特征在于，所述UE根据所述UE自主移动参数向第一基站发送无线资源控制RRC连接建立请求之后，所述方法还包括：
    所述UE接收所述第一基站发送的所述第一RRC连接建立请求的拒绝消息；
    所述UE执行TAU流程，并向所述第一基站发送第二RRC连接建立请求；所述第二RRC连接建立请求用于触发所述第一基站选取除所述UE所属的MME之外的MME。
  12. 一种基站，其特征在于，包括：
    接收单元，用于接收用户设备UE发送的第一无线资源控制RRC连接建立请求，所述第一RRC连接建立请求携带所述UE在发送所述第一RRC连接建立请求之前的连接状态信息；
    确定单元，用于根据所述连接状态信息确定所述第一基站是否满足索要所述UE上下文信息条件；
    发送单元，用于若所述确定单元确定所述第一基站未满足索要所述UE上下文信息条件，向移动性管理实体MME发送所述UE上下文信息建立请求；
    所述接收单元，还用于接收所述MME响应所述UE上下文信息建立请求而发送的响应消息，所述响应消息携带所述UE上下文信息。
  13. 根据权利要求12所述的基站，其特征在于，所述连接状态信息包括所述UE所属的MME标识，所述确定单元具体用于：
    根据所述UE所属的MME标识判断所述第一基站是否与所述UE所属的MME连接；若所述第一基站未与所述UE所属的MME连接，则所述确定单 元确定所述第一基站不满足索要所述UE上下文信息条件。
  14. 根据权利要求13所述的基站，其特征在于，所述MME不同于所述UE所属的MME，所述UE上下文信息建立请求携带所述UE标识和所述UE所属的MME标识，所述UE上下文信息建立请求用于触发所述MME根据所述UE所属的MME标识向所述UE所属的MME索要所述UE的上下文信息。
  15. 根据权利要求12所述的基站，其特征在于，所述连接状态信息包括第二基站标识，所述确定单元具体用于：
    根据所述第二基站标识判断是否存在用于连接所述第一基站与所述第二基站的接口；若不存在用于连接所述第一基站与所述第二基站的接口，则所述确定单元确定所述第一基站不满足索要所述UE上下文信息条件。
  16. 根据权利要求15所述的基站，其特征在于，所述MME为所述UE所属的MME，所述第一基站与所述UE所属的MME连接，所述UE上下文信息建立请求携带所述UE的初始消息，所述UE上下文信息建立请求用于触发所述UE所属的MME根据所述UE的初始消息向所述第二基站索要所述UE的上下文信息。
  17. 根据权利要求14所述的基站，其特征在于，
    所述发送单元，还用于向所述UE发送所述第一RRC连接建立请求的拒绝消息，所述拒绝消息用于触发所述UE执行TAU；
    所述接收单元，还用于接收所述UE发送的第二RRC连接建立请求；并根据所述第二RRC连接建立请求选取除所述UE所属的MME之外的MME。
  18. 根据权利要求12～17任一项所述的基站，其特征在于，
    所述发送单元，还用于向所述UE发送RRC连接重建立完成响应，所述RRC连接重建立完成响应携带配置指示、安全初始化指示、配置信息以及安全参数。
  19. 根据权利要求12～18任一项所述的基站，其特征在于，
    所述接收单元，还用于接收所述第二基站发送的缓存数据。
  20. 一种用户设备UE，其特征在于，包括：
    接收单元，用于接收第二基站发送的所述UE自主移动参数；
    选取单元，用于根据所述接收单元接收到的所述UE自主移动参数选取第 一基站；
    发送单元，用于根据所述接收单元接收到的所述UE自主移动参数向所述第一基站发送第一无线资源控制RRC连接建立请求；
    其中，所述第一RRC连接建立请求携带所述UE在发送所述第一RRC连接建立请求之前的连接状态信息，所述第一RRC连接建立请求用于指示所述第一基站根据所述连接状态信息确定所述第一基站未满足索要UE上下文信息条件时，向移动性管理实体MME发送所述UE上下文信息建立请求。
  21. 根据权利要求20所述的UE，其特征在于，
    所述接收单元，还用于接收所述第一基站发送的RRC连接建立完成响应，所述RRC连接重建立完成响应携带配置指示、安全初始化指示、配置信息以及安全参数；
    所述UE还包括：
    处理单元，用于根据所述配置指示删除初始配置信息，并使用所述配置信息；根据所述安全初始化指示激活所述安全参数。
  22. 根据权利要求20或21所述的UE，其特征在于，
    所述接收单元，还用于接收所述第一基站发送的所述第一RRC连接建立请求的拒绝消息；
    所述处理单元，还用于UE执行TAU流程；
    所述发送单元，还用于向所述第一基站发送第二RRC连接建立请求；所述第二RRC连接建立请求用于触发所述第一基站选取除所述UE所属的MME之外的MME。
  23. 一种用户设备UE，其特征在于，包括：
    处理器和存储器；其中，所述处理器通过调用所述存储器中的代码或指令以执行如下步骤：
    接收第二基站发送的所述UE自主移动参数；
    根据所述UE自主移动参数选取第一基站；
    根据所述UE自主移动参数向所述第一基站发送第一无线资源控制RRC连接建立请求；
    其中，所述第一RRC连接建立请求携带所述UE在发送所述第一RRC连 接建立请求之前的连接状态信息，所述第一RRC连接建立请求用于指示所述第一基站根据所述连接状态信息确定所述第一基站未满足索要UE上下文信息条件时，向移动性管理实体MME发送所述UE上下文信息建立请求。
  24. 根据权利要求23所述的UE，其特征在于，所述根据所述UE自主移动参数向第一基站发送第一无线资源控制RRC连接建立请求之后，所述处理器还用于：
    接收所述第一基站发送的RRC连接建立完成响应，所述RRC连接重建立完成响应携带配置指示、安全初始化指示、配置信息以及安全参数；
    根据所述配置指示删除初始配置信息，并使用所述配置信息；
    根据所述安全初始化指示激活所述安全参数。
  25. 根据权利要求23或24所述的UE，其特征在于，所述根据所述UE自主移动参数向第一基站发送无线资源控制RRC连接建立请求之后，所述处理器还用于：
    接收所述第一基站发送的所述第一RRC连接建立请求的拒绝消息；
    执行TAU流程，并向所述第一基站发送第二RRC连接建立请求；所述第二RRC连接建立请求用于触发所述第一基站选取除所述UE所属的MME之外的MME。
PCT/CN2015/091212 2015-09-30 2015-09-30 一种用户设备上下文信息的获取方法、相关设备及系统 WO2017054168A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP15905080.6A EP3349509B1 (en) 2015-09-30 2015-09-30 Methods for acquiring context information of user equipment, and related devices
PCT/CN2015/091212 WO2017054168A1 (zh) 2015-09-30 2015-09-30 一种用户设备上下文信息的获取方法、相关设备及系统
CN201580082422.0A CN107925930B (zh) 2015-09-30 2015-09-30 一种用户设备上下文信息的获取方法、相关设备及系统
US15/938,248 US10721657B2 (en) 2015-09-30 2018-03-28 Method, system, and related device for obtaining user equipment context information

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/091212 WO2017054168A1 (zh) 2015-09-30 2015-09-30 一种用户设备上下文信息的获取方法、相关设备及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/938,248 Continuation US10721657B2 (en) 2015-09-30 2018-03-28 Method, system, and related device for obtaining user equipment context information

Publications (1)

Publication Number Publication Date
WO2017054168A1 true WO2017054168A1 (zh) 2017-04-06

Family

ID=58422541

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/091212 WO2017054168A1 (zh) 2015-09-30 2015-09-30 一种用户设备上下文信息的获取方法、相关设备及系统

Country Status (4)

Country Link
US (1) US10721657B2 (zh)
EP (1) EP3349509B1 (zh)
CN (1) CN107925930B (zh)
WO (1) WO2017054168A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112166645A (zh) * 2018-05-24 2021-01-01 Oppo广东移动通信有限公司 一种提高寻呼可靠性的方法及装置、计算机存储介质

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11234177B2 (en) * 2017-06-23 2022-01-25 Beijing Xiaomi Mobile Software Co., Ltd. Data offloading method and device, access point equipment and station
CN113287336A (zh) * 2019-01-21 2021-08-20 瑞典爱立信有限公司 处置无线电资源控制拒绝
CN112087751B (zh) * 2019-06-14 2022-01-14 华为技术有限公司 安全校验方法及装置
US20230232296A1 (en) * 2020-05-21 2023-07-20 Beijing Xiaomi Mobile Software Co., Ltd. Information sending method, base station switching method, information reception method and apparatus

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008095935A1 (en) * 2007-02-06 2008-08-14 Nokia Siemens Networks Gmbh & Co. Kg A method of handover
WO2011147098A1 (zh) * 2010-05-28 2011-12-01 华为技术有限公司 一种获取上下文的处理方法及设备
CN102598786A (zh) * 2011-11-11 2012-07-18 华为技术有限公司 基站间的切换方法、基站、和通讯系统
CN103108403A (zh) * 2011-11-10 2013-05-15 中兴通讯股份有限公司 跨基站rrc连接重建方法及系统
CN103782628A (zh) * 2013-04-18 2014-05-07 华为技术有限公司 通信方法、设备和系统
CN103858512A (zh) * 2011-08-12 2014-06-11 黑莓有限公司 处理无线通信系统中的连接
CN104823478A (zh) * 2012-11-01 2015-08-05 Lg电子株式会社 在无线通信系统中用于管理ran资源的方法和设备

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2592868B8 (en) * 2009-04-27 2020-11-04 Huawei Technologies Co., Ltd. Service recovery method and apparatus for a wireless communication network
CN101848536B (zh) 2010-04-28 2012-09-05 新邮通信设备有限公司 一种无线资源控制连接重建立方法和一种基站
US20130039287A1 (en) * 2011-08-12 2013-02-14 Venkata Ratnakar Rao Rayavarapu Simplified ue + enb messaging
US9049698B2 (en) * 2012-01-18 2015-06-02 Mediatek Inc. Method of enhanced connection recovery and cell selection
CN103906152B (zh) * 2012-12-24 2022-02-25 北京三星通信技术研究有限公司 支持ue快速恢复的方法
CN114449603B (zh) * 2012-12-24 2024-06-07 北京三星通信技术研究有限公司 无线通信系统中的基站及由其执行的方法
US9980159B2 (en) * 2014-09-26 2018-05-22 Mediatek Inc. RRC re-establishment on secondary eNodeB for dual connectivity

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008095935A1 (en) * 2007-02-06 2008-08-14 Nokia Siemens Networks Gmbh & Co. Kg A method of handover
WO2011147098A1 (zh) * 2010-05-28 2011-12-01 华为技术有限公司 一种获取上下文的处理方法及设备
CN103858512A (zh) * 2011-08-12 2014-06-11 黑莓有限公司 处理无线通信系统中的连接
CN103108403A (zh) * 2011-11-10 2013-05-15 中兴通讯股份有限公司 跨基站rrc连接重建方法及系统
CN102598786A (zh) * 2011-11-11 2012-07-18 华为技术有限公司 基站间的切换方法、基站、和通讯系统
CN104823478A (zh) * 2012-11-01 2015-08-05 Lg电子株式会社 在无线通信系统中用于管理ran资源的方法和设备
CN103782628A (zh) * 2013-04-18 2014-05-07 华为技术有限公司 通信方法、设备和系统

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112166645A (zh) * 2018-05-24 2021-01-01 Oppo广东移动通信有限公司 一种提高寻呼可靠性的方法及装置、计算机存储介质
EP3796743A4 (en) * 2018-05-24 2021-07-14 Guangdong Oppo Mobile Telecommunications Corp., Ltd. PROCESS AND DEVICE FOR IMPROVING THE RELIABILITY OF RADIO PASSING, AND COMPUTER STORAGE SUPPORT
US11356974B2 (en) 2018-05-24 2022-06-07 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Method and device for improving reliabtility of paging
CN112166645B (zh) * 2018-05-24 2023-03-14 Oppo广东移动通信有限公司 一种提高寻呼可靠性的方法及装置、计算机存储介质

Also Published As

Publication number Publication date
CN107925930A (zh) 2018-04-17
CN107925930B (zh) 2020-06-26
EP3349509B1 (en) 2019-12-04
EP3349509A1 (en) 2018-07-18
EP3349509A4 (en) 2018-07-18
US10721657B2 (en) 2020-07-21
US20180220341A1 (en) 2018-08-02

Similar Documents

Publication Publication Date Title
CN110366224B (zh) 信令优化方法、设备、计算机可读存储介质和通信系统
US10721657B2 (en) Method, system, and related device for obtaining user equipment context information
WO2017078143A1 (ja) ユーザ装置、基地局、接続確立方法、及びコンテクスト情報取得方法
US20180295669A1 (en) Method and apparatus for setting up/releasing radio resource control connection between evolved node b and user equipment in communication system
WO2017152757A1 (zh) 一种小区切换方法、系统及相关设备
WO2018126961A1 (zh) 通信的方法、接入网设备和终端
WO2017045149A1 (zh) 一种释放无线资源控制rrc连接的方法及装置
TWI768490B (zh) 用於在通訊網路中管理無線電承載相容性之系統和方法
WO2018102964A1 (zh) 传输信息的方法和设备
WO2017211166A1 (zh) 可穿戴设备的无线承载配置方法与装置
US8547938B2 (en) Data flow transfer between wireless connections
WO2016058164A1 (zh) 一种处理语音业务的方法、终端
WO2016095113A1 (zh) 一种寻呼方法、移动性管理实体及基站
CN101394340A (zh) 数据传输方法、系统和装置
CN108307452A (zh) 连接恢复方法及装置、基站、用户终端
US20140335864A1 (en) Radio communication system, radio base station, radio terminal and radio communication method
TW201804838A (zh) 數據傳輸的方法、接入網設備、終端設備和網絡實體
WO2013113240A1 (zh) 一种传输rn信息、寻呼ue的方法及装置
US10187828B2 (en) Communication device and communication method with improved handover
US11265937B2 (en) Device discovery in a device to device communication using two types of discovery
CN103582035B (zh) 一种无线资源配置的管理方法和系统
WO2017016493A1 (zh) Sc-ptm系统下的组呼区域管理方法
WO2017000412A1 (zh) 一种lc-mtc系统的小区切换方法、装置及系统
TW201743640A (zh) 通信方法、核心網設備、接入網設備、以及終端設備
WO2018201973A1 (zh) 一种消息传输的方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15905080

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2015905080

Country of ref document: EP