WO2019214450A1 - 一种空口非激活态维持方法和装置 - Google Patents

一种空口非激活态维持方法和装置 Download PDF

Info

Publication number
WO2019214450A1
WO2019214450A1 PCT/CN2019/084341 CN2019084341W WO2019214450A1 WO 2019214450 A1 WO2019214450 A1 WO 2019214450A1 CN 2019084341 W CN2019084341 W CN 2019084341W WO 2019214450 A1 WO2019214450 A1 WO 2019214450A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
secondary base
information
rrc
air interface
Prior art date
Application number
PCT/CN2019/084341
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 KR1020207035164A priority Critical patent/KR102410198B1/ko
Priority to MX2020011833A priority patent/MX2020011833A/es
Priority to US17/054,116 priority patent/US11576101B2/en
Publication of WO2019214450A1 publication Critical patent/WO2019214450A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • 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
    • 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/0058—Transmission of hand-off measurement information, e.g. measurement reports
    • 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/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • 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/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/10—Interfaces between hierarchically different network devices between terminal device and access point, i.e. wireless air interface

Definitions

  • the present disclosure relates to the field of mobile communication technologies, and in particular, to an air interface inactive state maintaining method and apparatus.
  • terminal UE User Equipment
  • SC Single Connectivity
  • DC/MC Dual/Multiple Connectivity
  • the UE has only one data transmission channel on both the air interface and the network side.
  • the DC/MC dual/multi-connection mode the UE has two or more data transmission channels on the air interface or the network side.
  • the UE can establish and maintain two independent wireless link connections (air interface data transmission channels) with two NG-RAN base stations in the air interface, and one base station is called a master base station (MN).
  • MN master base station
  • Another base station is called a secondary base station (SN); and the MN and the SN can simultaneously establish and maintain two independent network side connections (network data transmission channels) on the NG interface and the core network user plane network element UPF. ), but only the MN can establish and maintain an NG-C connection with the core network control plane network element node AMF, and the related architecture is as shown in FIG.
  • the UE in dual-connection configuration operation can also enter the RRC_INACTIVE inactive state dual-connection operation and combine the RRC_INACTIVE inactive state.
  • the advantage is that the network-side primary and secondary base stations MN/SN and UE can simultaneously maintain their dual-connection communication configurations. Context, so as to prevent the network side and the terminal UE from falling back to the single-connection configuration operation, and then may again go back to the dual-connection operation through the configuration, as shown in FIG. 2 .
  • the process of the UE and the network side entering and exiting the RRC_INACTIVE inactive state may be supported by the current standard protocol; but as the UE moves, when the UE leaves the current service master
  • the SN of the base station MN and the secondary base station are covered, for example, the MN has changed, the SN has changed, and so on, how the UE remains in the RRC_INACTIVE inactive state, and the current standard protocol cannot be effectively supported.
  • the present disclosure proposes an air interface inactive state maintaining method and apparatus, which can effectively support the UE to maintain the RRC_INACTIVE inactive state.
  • an air interface inactive state maintaining method comprising:
  • the RRC uplink notification message carries information that is notified by the serving cell that the UE has left the source secondary base station;
  • a migration operation of a related high-level configuration that is anchored by the UE to the source secondary base station side PDU Session where the migration target node is a target secondary base station or a current primary base station;
  • the RRC downlink reply message is sent to the UE, where the RRC downlink reply message carries the migration operation completion indication information; and the UE is still in the dual-connection or single-connection air interface inactive state.
  • the present disclosure also proposes an air interface inactive state maintaining method, the method comprising:
  • the present disclosure also proposes an air interface inactive state maintaining method, the method comprising:
  • the message is released based on the received context information, and the context information of the locally saved UE at the source secondary base station side is released.
  • the present disclosure also proposes an air interface inactive state maintaining method, the method comprising:
  • the secondary base station notification message includes: context information of the UE at the source secondary base station side;
  • the target secondary base station locally stores the received context information of the UE on the source secondary base station side, and completes the migration operation of the UE context information between different secondary base stations.
  • the present disclosure also provides an air interface inactive state maintaining device, which is disposed on a base station, and the device includes:
  • the first receiving unit is configured to receive an RRC uplink notification message sent by the UE, where the RRC uplink notification message carries information that is notified by the serving cell that the UE has left the source secondary base station;
  • a migration configuration unit configured to perform, according to the RRC uplink notification message, a migration operation of a related high-level configuration that is anchored by the UE to the source secondary base station side PDU Session, where the migration target node is a target secondary base station or a current primary base station; and, maintaining the UE still In the dual connection or single connection air port inactive state
  • the first sending unit is configured to send an RRC downlink reply message to the UE after performing the migrating operation of the high-level configuration, where the RRC downlink reply message carries the migration operation completion indication information.
  • the present disclosure also provides an air interface inactive state maintaining device, which is disposed on the user equipment UE, and the device includes:
  • the measuring unit is configured to perform RRM air interface measurement on the candidate target serving cells on both sides of the primary base station and the source secondary base station based on the RRM measurement configuration information of the primary base station and the source secondary base station when the air interface is inactive, to determine the current Mobile environment;
  • a second sending unit configured to send an RRC uplink notification message to the primary base station when the update event of the wireless coverage of the source secondary base station is detected by the air interface RRM; the RRC uplink notification message carries the notification that the UE has left the source Information about the coverage of the serving cell of the base station;
  • the second receiving unit is configured to receive an RRC downlink reply message sent by the primary base station, where the RRC downlink reply message carries the migration operation completion indication information.
  • the present disclosure also provides an air interface inactive state maintaining device, which is disposed on a base station, and the device includes:
  • a third receiving unit configured to receive a context information release message sent by the primary base station
  • a releasing unit configured to release the message based on the received context information, and release the context information of the locally saved UE at the source secondary base station side.
  • the present disclosure also provides an air interface inactive state maintaining device, which is disposed on a base station, and the device includes:
  • a fourth receiving unit configured to receive a secondary base station notification message sent by the primary base station;
  • the secondary base station notification message includes: context information of the UE at the source secondary base station side;
  • the storage unit is configured to store, on the target secondary base station, the context information of the received UE on the source secondary base station side, and complete the migration operation of the UE context information between different secondary base stations.
  • the present disclosure also provides an electronic device including a memory, a processor, and a computer program stored on the memory and operable on the processor, the processor executing the computer program to implement the disclosure provided by the present disclosure
  • the processing of any air interface inactive state maintenance method including a memory, a processor, and a computer program stored on the memory and operable on the processor, the processor executing the computer program to implement the disclosure provided by the present disclosure.
  • the present disclosure also proposes a computer readable storage medium having stored thereon a computer program that, when executed by a processor, implements the processing of any of the air interface inactive state maintenance methods provided by the present disclosure.
  • the technical solution provided by the present disclosure includes: receiving an RRC uplink notification message sent by the UE; the RRC uplink notification message carries information that is notified by the serving cell that the UE has left the source secondary base station; a notification message, performing a migration operation of the associated high-level configuration of the UE anchored to the PDU session of the source secondary base station side, where the migration target node is the target secondary base station or the current primary base station; after performing the migration operation of the high-level configuration, sending to the UE
  • the RRC downlink reply message carries the migration operation completion indication information; and the UE is still in the dual connectivity or single connection air interface inactive state.
  • the MN when the UE in the dual-connection configuration and enters the inactive state, when the secondary base station changes, the MN can know in time that the UE moves from the source secondary base station to the target secondary base station, or only leaves the source auxiliary.
  • the base station does not enter the new target secondary base station, and the UE context information stored in the source secondary base station can be transferred to the target secondary base station or the primary base station or deleted in time, thereby ensuring the network side connection status and related high-level configuration. It can be consistent with the latest mobile state of the UE, thus providing an effective solution to support the UE to maintain the RRC_INACTIVE inactive state.
  • 1 is an architecture diagram of an active state of a dual connectivity operation of a terminal UE
  • FIG. 2 is a schematic diagram of an inactive state of a dual connectivity operation of a terminal UE
  • 3 is a dual connectivity inactive state UE moving from SN-1 cell coverage to SN-2 cell coverage;
  • FIG. 4 is an architectural diagram of a dual connectivity inactive UE at source SN-1;
  • 5 is an architectural diagram of a dual-connected inactive UE after a new target SN-2;
  • FIG. 6 , FIG. 7 , FIG. 8 and FIG. 9 are respectively a flowchart of a method for maintaining an inactive state of an air interface according to an embodiment of the present disclosure.
  • the present disclosure proposes an air interface inactive state maintaining method, the method comprising:
  • Step 011 Receive an RRC uplink notification message sent by the UE.
  • the RRC uplink notification message carries information that is notified by the serving cell that the UE has left the source secondary base station.
  • the RRC uplink notification message is an RRC Connection Resume Request message or other applicable RRC uplink message;
  • the RRC uplink notification message is an uplink message that can be transmitted between the UE and the network side when the UE is in an inactive state;
  • the RRC uplink notification message includes: a P-I-RNTI allocated by the primary base station to the UE, context index information S-I-RNTI allocated by the SgNB1 to the UE, a new serving cell identity id under SgNB2, and secondary base station update indication information.
  • the RRC uplink notification message includes: an S-I-RNTI allocated by the SgNB1 to the UE, a new serving cell identity id under the SgNB2, and secondary base station update indication information;
  • the primary base station is the primary base station corresponding to the UE, the SgNB1 is the source secondary base station, and the SgNB2 is the target secondary base station; that is, the SgNB1 is the secondary base station corresponding to the UE before the location switch, and the SgNB2 is the secondary base station corresponding to the UE after the location switch;
  • Step 012 Perform, according to the RRC uplink notification message, a migration operation of a related high-level configuration that is anchored by the UE to the source secondary base station side PDU Session, where the migration target node is a target secondary base station or a current primary base station;
  • step 012 includes:
  • Step 0121 the primary base station determines, according to the new serving cell identifier id under the SgNB2, that the UE moves to the serving cell corresponding to the new serving cell identifier id under the SgNB2;
  • Step 0122 The primary base station acquires the context of the UE on the SgNB1 side.
  • the method includes: when the host station stores the context information of the UE on the SgNB1 side, the primary base station finds the context information of the stored UE on the SgNB1 side by using an index method according to the S-I-RNTI information;
  • Another method includes: the primary base station initiates a UE Context acquisition process to the source secondary base station SgNB1, including:
  • Step 0122 The primary base station sends a context information request message to the source secondary base station SgNB1, where the SI-RNTI information is included, and the SI-RNTI information includes related UE context index information in the SgNB1.
  • the context information request message is Retrieve UE Context Request message.
  • the primary base station initiates a UE Context acquisition process to the source secondary base station SgNB1 through the Xn interface.
  • Step 0122b The primary base station receives the context information response message replied by the source secondary base station SgNB1, where the context information response message carries the context information of the UE that is originally saved in the SgNB1 on the SgNB1 side.
  • the context information response message is a Retrieve UE Context Response message.
  • Step 0123 The primary base station sends a secondary base station notification message to the target secondary base station SgNB2.
  • the secondary base station notification message includes: the context information of the UE corresponding to the source SgNB1 on the SgNB1 side;
  • the primary base station receives the secondary base station notification acknowledgement message sent by the target secondary base station SgNB2, and the secondary base station notification acknowledgement message includes: SgNB2 side downlink transmission address information required for carrying the PDU Session2;
  • the secondary base station notification message is a SN Addition Request message; and the secondary base station notification confirmation message is a SN Addition Request ACK message.
  • Step 0125 The primary base station initiates a PDU Session resource modification indication process to the AMF/SMF.
  • the method includes: the primary base station sends a PDU session resource modification indication information to the AMF/SMF, where the PDU session resource modification indication information carries the base station downlink transmission address information used to carry the migrated PDU session.
  • Step 0126 The primary base station sends a context information release message to the source SgNB1, so that the SgNB1 releases the context information of the originally saved UE on the SgNB1 side based on the message.
  • the context information release message may be a UE Context Release message.
  • Step 013 Send an RRC downlink reply message to the UE, where the RRC downlink reply message carries the migration operation completion indication information; and maintain the UE still in the dual connectivity or single connection air interface inactive state.
  • the RRC downlink reply message is an RRC Connection Resume Reject message or other applicable RRC downlink message;
  • the RRC downlink notification message is a downlink message that the network side can transmit to the UE when the air interface is inactive.
  • the RRC downlink reply message includes: New S-I-RNTI information, and SN update completion indication information.
  • the RRC downlink reply message further includes a newly allocated New P-I-RNTI.
  • Step 014 The primary base station starts the UE to return to the dual connectivity active state when the UE needs to switch to the dual connectivity active state. For example, if the UE has uplink user data arriving to be transmitted, or if downlink user data arrives to be transmitted, or if downlink control data arrives to be transmitted, it is necessary to switch to the dual connectivity activation state.
  • an air interface inactive state maintaining method comprising:
  • Step 021 The primary base station receives an RRC uplink notification message sent by the UE.
  • the RRC uplink notification message is an RRC Connection Resume Request message or other applicable RRC uplink message
  • the RRC uplink notification message includes: a PI-RNTI allocated by the primary base station to the UE, an SI-RNTI allocated by the SgNB1 to the UE, and a secondary base station release indication information.
  • the primary base station is the primary base station corresponding to the UE, and the SgNB1 is the source secondary base station; after the handover, the UE does not have the corresponding secondary base station cell;
  • Step 022 The primary base station determines that the UE moves to the serving cell corresponding to the new serving cell identifier id under SgNB2.
  • Step 023 The primary base station acquires context information of the UE on the SgNB1 side.
  • the method includes: when the host station stores the context information of the UE on the SgNB1 side, the primary base station finds the context information of the stored UE on the SgNB1 side by using an index method according to the S-I-RNTI information;
  • Another method includes: the primary base station initiates a UE Context acquisition process to the source secondary base station SgNB1, including:
  • Step 023a The primary base station sends a context information request message to the source secondary base station SgNB1, where the S-I-RNTI information is carried, and the S-I-RNTI information includes related UE context index information in the SgNB1.
  • the primary base station initiates a UE Context acquisition process to the source secondary base station SgNB1 through the Xn interface.
  • Step 023b The primary base station receives the context information response message replied by the source secondary base station SgNB1, and the context information response message carries the context information information of the UE that is originally saved in the SgNB1 at the source secondary base station side.
  • Step 026 The primary base station sends an RRC downlink reply message to the UE.
  • the RRC downlink reply message is an RRC Connection Resume Reject message or other applicable RRC downlink message
  • the RRC downlink reply message includes: SN release completion indication information.
  • the RRC downlink reply message further includes a newly allocated New P-I-RNTI.
  • the RRC downlink reply message further includes the P-I-RNTI allocated by the base station to the UE before.
  • Step 027 The primary base station initiates a PDU Session resource modification indication process to the AMF/SMF.
  • the method includes: the primary base station sends the PDU session resource modification indication information to the AMF/SMF, where the PDU session resource modification indication information carries the downlink transmission address information required for carrying the PDU Session2.
  • the downlink address is a downlink address newly configured by the primary base station to carry the PDU Session2.
  • the PDU Session resource modification indication information is a PDU Session Resource Modify Indication message.
  • step 028 the primary base station sends a UE Context Release message to the source SgNB1, so that the SgNB1 releases the context information of the originally saved UE on the SgNB1 side based on the message.
  • Step 029 The primary base station starts the UE to return to the dual connectivity active state when the UE needs to switch to the dual connectivity active state. For example, if the UE has uplink user data arriving to be transmitted, or if downlink user data arrives to be transmitted, or if downlink control data arrives to be transmitted, it is necessary to switch to the dual connectivity activation state.
  • the embodiments of the present disclosure provide an air interface inactive state maintaining method, where the method includes:
  • Step 031 The RRC uplink notification message sent by the UE to the primary base station; the RRC uplink notification message is an RRC Connection Resume Request message or other applicable RRC uplink message;
  • the primary base station is the primary base station corresponding to the UE
  • the SgNB1 is the secondary base station corresponding to the UE before the location switch
  • the SgNB2 is the secondary base station corresponding to the UE after the location switch
  • Step 032 The UE receives an RRC downlink reply message sent by the primary base station, where the RRC downlink reply message is an RRC Connection Resume Reject message or other applicable RRC downlink message.
  • the RRC downlink reply message includes: New SI-RNTI information, and a reject cause value.
  • Casue value SN Change Done;
  • the RRC downlink reply message further includes a newly allocated New P-I-RNTI.
  • Step 033 When the UE needs to switch to the dual connectivity active state, the UE sends an RRC Connection Resume Request message to the primary base station.
  • the RRC Connection Resume Request message or other applicable RRC uplink message includes: a P-I-RNTI allocated by the primary base station to the UE, an S-I-RNTI allocated by the SgNB1 to the UE, and UL data Arriving.
  • the embodiments of the present disclosure provide an air interface inactive state maintaining method, where the method includes:
  • Step 041 The UE sends an RRC uplink notification message to the primary base station; the RRC uplink notification message is an RRC Connection Resume Request message or other applicable RRC uplink message.
  • the primary base station is the primary base station corresponding to the UE
  • the SgNB1 is the secondary base station corresponding to the UE before the location switch
  • the SgNB2 is the secondary base station corresponding to the UE after the location switch
  • the RRC downlink reply message further includes a P-I-RNTI allocated by the primary base station to the UE.
  • Step 043 An RRC Connection Resume Request message or other applicable RRC uplink message sent by the UE to the primary base station when the UE needs to switch to the dual connectivity active state.
  • the RRC Connection Resume Request message or other applicable RRC uplink message includes: a P-I-RNTI allocated by the primary base station to the UE, an S-I-RNTI allocated by the SgNB1 to the UE, and UL data Arriving.
  • the embodiments of the present disclosure provide an air interface inactive state maintaining method, where the method includes:
  • Step 051 The source secondary base station SgNB1 receives the context information request message sent by the primary base station, where the S-I-RNTI information is carried, and the S-I-RNTI information includes related UE context index information in the SgNB1.
  • the source secondary base station SgNB1 receives the UE Context acquisition process initiated by the primary base station through the Xn interface.
  • Step 052 The source secondary base station SgNB1 sends a reply context information response message to the primary base station, where the context information response message carries the context information of the UE that is originally saved in the SgNB1 on the SgNB1 side.
  • Step 053 The source secondary base station SgNB1 receives the UE Context Release message sent by the primary base station.
  • Step 054 The SgNB1 releases the context information of the locally saved UE on the SgNB1 side based on the received UE Context Release message.
  • an air interface inactive state maintaining method comprising:
  • Step 061 The target secondary base station SgNB2 receives the secondary base station notification message sent by the primary base station; the secondary base station notification message includes: the context information of the UE corresponding to the source SgNB1 on the SgNB1 side;
  • Step 062 The target secondary base station SgNB2 locally stores the received context information of the UE on the SgNB1 side;
  • Step 063 The target secondary base station SgNB2 sends a secondary base station notification confirmation message to the primary base station; the secondary base station notification confirmation message includes: SgNB2 side downlink transmission address information required for carrying the PDU Session2.
  • the process is as shown in FIG. 6: a UE is in the MeNB and SgNB1 dual-connection working mode, and the PDU Session 1 is anchored on the MeNB side; and the PDU Session 2 is anchored on the SgNB1 side.
  • the user data of PDU Sessions 1 and 2 is temporarily suspended.
  • the MeNB decides to reconfigure the UE to the RRC_INACTIVE inactive state through the air interface Suspend process, thereby releasing the MCG Radio Link and the SCG Radio Link and the lower layer wireless configuration.
  • the MeNB maintains the NG-C and NG-U (MN) network connection, and the high-level configuration related to the PDU Session1; the SgNB1 stores the NG-U (SN) network connection, and the high-level configuration related to the PDU Session2; the UE stores the PDU Session1 and 2 related high-level configuration.
  • MN NG-C and NG-U
  • Step 101 The UE is in the dual connectivity configuration and the RRC_INACTIVE inactive state, and still performs the RRM radio measurement for each inter-frequency point where the candidate target secondary base station is deployed.
  • the UE After the UE detects that it has entered the new target secondary base station SgNB2, the UE triggers an RRC connection recovery procedure in the air interface Uu, and initiates an RRC Connection Resume Request message or other applicable RRC uplink message.
  • the P-I-RNTI information includes source MeNB base station identifier id and index information of the UE's MeNB side context saved by the MeNB side.
  • the S-I-RNTI information includes the source SgNB1 base station identifier id and index information of the UE's SgNB1 side context saved by the SgNB1 side.
  • the MeNB side context information that is, the MeNB side network connection
  • the context information of the UE stored in the SgNB1 side ie, the network connection on the SgNB1 side and the related high-level configuration
  • Step 103 The MeNB initiates a UE Context acquisition process to the source secondary base station SgNB1 through the Xn interface, and initiates a Retrieve UE Context Request message, where the SI-RNTI information includes related UE context index information in the SgNB1. Based on the acquisition request message, the source secondary base station The SgNB1 replies to the Retrieve UE Context Response message, and sends the context information of the originally saved UE in the SgNB1 to the MeNB on the SgNB1 side.
  • Step 104 The MeNB initiates an SN establishment procedure to the new target secondary base station SgNB2 through the Xn interface, and initiates a SN Addition Request message.
  • the SN Addition Request message includes: the context information of the originally saved UE in the SgNB1 side in the source SgNB1, thereby the context information. Send to SgNB2 and save it. Based on the context information, SgNB2 then learns that it needs to carry PDU Session 2 (originally carried by SgNB1) and its associated context configuration. Note: Because it is inactive, SgNB2 does not need to establish the wireless configuration of the SCG low layer, and only continues to save the UE's network connection and related high-level configuration on the SN side.
  • Step S105 The SgNB2 sends an SN Addition Request ACK message to the MeNB through the Xn interface.
  • the SN Addition Request ACK message includes: SgNB2 side downlink transmission address information required for carrying the PDU Session2. Based on the SN side context information forwarded by the MeNB, the SgNB2 can learn the uplink transmission address of the PDU Session2 on the UPF side, and further establish an NG-U (SN) network connection (NG-U data transmission channel) with the UPF, and further complete the establishment. Connected to the MN's Xn network.
  • Step 106 The MeNB initiates an RRC Connection Resume Reject message or other applicable RRC downlink message to the UE through the air interface Uu.
  • Step 107 The MeNB initiates a PDU Session Resource Modify Indication process to the AMF/SMF through the NG-C interface, and provides the UPG with the SgNB2 side downlink transmission address information that the SgNB2 just allocated to carry the PDU Session2, so that the UPF and the SgNB2 are established.
  • NG-U (SN) network connection (NG-U data transmission channel).
  • Step 108 The MeNB initiates a UE Context release process to the source SgNB1 through the Xn interface, and initiates a UE Context Release message. Based on the message, SgNB1 then releases the previously saved UE's context information on the SgNB1 side.
  • Step 109 When the UE has uplink user data to be transmitted, the UE initiates a RACH procedure to the source MeNB, and indicates the DRB id or QoS Flow id information related to the uplink user data, and attempts to return to the RRC_ACTIVE state.
  • a UE is in the dual connection working mode of MgNB and SgNB1, and the PDU Session 1/2 anchor is established on the MgNB side; and the PDU Session 3/4 anchor is established on the SgNB1 side.
  • MgNB decides to reconfigure the UE to the RRC_INACTIVE inactive state through the air interface Suspend process, thereby releasing the MCG Radio Link and SCG Radio Link and the lower layer wireless configuration.
  • the MgNB stores the NG-C and NG-U (MN) network connections, and the high-level configuration related to the PDU Session 1/2; the SgNB1 stores the NG-U (SN) network connection, and the high-level configuration related to the PDU Session 3/4; The PDU Session1/2/3/4 related high-level configuration.
  • Step 201 The UE is in the dual connectivity configuration and the RRC_INACTIVE inactive state, and still performs the RRM radio measurement for each inter-frequency point where the candidate target secondary base station is deployed.
  • the UE After the UE detects that it has entered the new target secondary base station SgNB2, the UE triggers an RRC connection recovery procedure in the air interface Uu, and initiates an RRC Connection Resume Request message or other applicable RRC uplink message.
  • the RRC Connection Resume Request message or other applicable RRC uplink message includes: the SI-RNTI information allocated to the UE before the MgNB/SgNB1 (because the UE does not leave the coverage of the MgNB serving cell, the PI-RNTI information is not reported temporarily), and the SgNB2 is newly updated.
  • the S-I-RNTI information includes the source SgNB1 base station identifier id and index information of the UE's SgNB1 side context saved by the SgNB1 side.
  • the MgNB knows that the UE has moved to the coverage of a serving cell of SgNB2.
  • Step 203 The MNB initiates a UE Context acquisition process to the source secondary base station SgNB1 through the Xn interface, and initiates a Retrieve UE Context Request message, where the SI-RNTI information includes related UE context index information in the SgNB1. Based on the acquisition request message, the source secondary base station The SgNB1 replies to the Retrieve UE Context Response message, and sends the context information of the originally saved UE in the SgNB1 to the MgNB on the SgNB1 side.
  • Step 204 The NB establishes a SN establishment procedure to the new target secondary base station SgNB2 through the Xn interface, and initiates a SN Addition Request message.
  • the SN Addition Request message includes: the context information of the originally saved UE in the SgNB1 side in the source SgNB1, thereby the context information. Send to SgNB2 and save it. Based on this context information, SgNB2 then learns that it needs to carry PDU Session 3/4 (originally hosted by SgNB1) and its associated context configuration. Note: Because it is inactive, SgNB2 does not need to establish the wireless configuration of the SCG low layer, and only continues to save the UE's network connection and related high-level configuration on the SN side.
  • Step 205 SgNB2 sends an SN Addition Request ACK message to the MgNB through the Xn interface.
  • the SN Addition Request ACK message includes: SgNB2 side downlink transmission address information required for carrying the PDU Session 3/4.
  • the SgNB2 can learn the uplink transmission address of the PDU Session3/4 on the UPF side, and further establish an NG-U (SN) network connection (NG-U data transmission channel) with the UPF, and further The establishment is completed and the MN's Xn network connection.
  • Step 206 The MME initiates an RRC Connection Resume Reject message or other applicable RRC downlink message to the UE through the air interface Uu.
  • Step 207 The NB initiates a PDU Session Resource Modify Indication process to the AMF/SMF through the NG-C interface, and provides the UPG with the SgNB2 side downlink transmission address information that the SgNB2 just allocated to carry the PDU Session 3/4, so that the UPF and the SgNB2 are established.
  • New NG-U (SN) network connection (NG-U data transmission channel).
  • Step 208 The MgNB initiates a UE Context release process to the source SgNB1 through the Xn interface, and initiates a UE Context Release message. Based on the message, SgNB1 then releases the context information of the originally saved UE on the SgNB1 side.
  • Step 209 When the UE has the uplink control signaling to be transmitted, the UE initiates a RACH procedure to the source MgNB, and indicates the DRB id or QoS Flow id information related to the uplink user data, and attempts to return to the RRC_ACTIVE state.
  • the process is as shown in FIG. 8: a UE is in the MeNB and SgNB1 dual-connection working mode, and the PDU Session 1 is anchored on the MeNB side; and the PDU Session 2 is anchored on the SgNB1 side.
  • the user data of PDU Sessions 1 and 2 is temporarily suspended.
  • the MeNB decides to reconfigure the UE to the RRC_INACTIVE inactive state through the air interface Suspend process, thereby releasing the MCG Radio Link and the SCG Radio Link and the lower layer wireless configuration.
  • the MeNB maintains the NG-C and NG-U (MN) network connection, and the high-level configuration related to the PDU Session1; the SgNB1 stores the NG-U (SN) network connection, and the high-level configuration related to the PDU Session2; the UE stores the PDU Session1 and 2 related high-level configuration.
  • MN NG-C and NG-U
  • Step 301 The UE is in the dual connectivity configuration and the RRC_INACTIVE inactive state, and still performs the RRM radio measurement for each inter-frequency point where the candidate target secondary base station is deployed. After the UE detects that it has left the SgNB1 service coverage but has not entered the service coverage of the new target secondary base station SgNB2, the UE triggers the RRC connection recovery procedure in the air interface Uu, and initiates an RRC Connection Resume Request message or other applicable RRC uplink message.
  • the P-I-RNTI information includes source MeNB base station identifier id and index information of the UE's MeNB side context saved by the MeNB side.
  • the S-I-RNTI information includes the source SgNB1 base station identifier id and index information of the UE's SgNB1 side context saved by the SgNB1 side.
  • Step 303 The MeNB initiates a UE Context acquisition process to the source secondary base station SgNB1 through the Xn interface, and initiates a Retrieve UE Context Request message, where the SI-RNTI information includes related UE context index information in the SgNB1. Based on the acquisition request message, the source secondary base station The SgNB1 replies to the Retrieve UE Context Response message, and sends the context information of the originally saved UE in the SgNB1 to the MeNB on the SgNB1 side.
  • Step 304 Since the UE has not entered the service coverage of the new target secondary base station SgNB2, the MeNB does not need to initiate an SN establishment procedure to the new target secondary base station SgNB2 through the Xn interface.
  • Step 305 SgNB2 does not need to establish an Xn network connection with the MN temporarily.
  • Step 306 The MeNB initiates an RRC Connection Resume Reject message or other applicable RRC downlink message to the UE through the air interface Uu.
  • Step 307 The MeNB initiates a PDU Session Resource Modify Indication process to the AMF/SMF through the NG-C interface, and provides the UPF with the downlink transmission address information that the MeNB has just allocated to carry the backhaul PDU Session2, so that the UPF and the MeNB establish a new one.
  • NG-U (MN) network connection (NG-U data transmission channel).
  • Step 308 The MeNB initiates a UE Context release process to the source SgNB1 through the Xn interface, and initiates a UE Context Release message. Based on the message, SgNB1 then releases the context information of the originally saved UE on the SgNB1 side.
  • Step 309 When the UE has the uplink user data to be transmitted, the UE initiates a RACH procedure to the source MeNB, and indicates the DRB id or QoS Flow id information related to the uplink user data, and attempts to return to the RRC_ACTIVE state.
  • a UE is in the dual connectivity mode of MgNB and SgNB1, and the PDU Session 1/2 anchor is established on the MgNB side; and the PDU Session 3/4 anchor is established on the SgNB1 side.
  • MgNB decides to reconfigure the UE to RRC_INACTIVE inactive state through the air interface Suspend process, thus releasing MCG Radio Link and SCG Radio Link and lower layer wireless. Configuration.
  • the MgNB stores the NG-C and NG-U (MN) network connections, and the high-level configuration related to the PDU Session 1/2; the SgNB1 stores the NG-U (SN) network connection, and the high-level configuration related to the PDU Session 3/4; The PDU Session1/2/3/4 related high-level configuration.
  • Step 401 The UE is in the dual connectivity configuration and the RRC_INACTIVE inactive state, and still performs the RRM radio measurement for each inter-frequency point where the candidate target secondary base station is deployed. After the UE detects that it has left the SgNB1 service coverage but has not entered the service coverage of the new target secondary base station SgNB2, the UE triggers the RRC connection recovery procedure in the air interface Uu, and initiates an RRC Connection Resume Request message or other applicable RRC uplink message.
  • the P-I-RNTI information includes the source MgNB base station identifier id and index information of the UE's MgNB side context saved by the MgNB side.
  • the S-I-RNTI information includes the source SgNB1 base station identifier id and index information of the UE's SgNB1 side context saved by the SgNB1 side.
  • Step 403 The MNB initiates a UE Context acquisition process to the source secondary base station SgNB1 through the Xn interface, and initiates a Retrieve UE Context Request message, where the SI-RNTI information includes related UE context index information in the SgNB1. Based on the acquisition request message, the source secondary base station The SgNB1 replies to the Retrieve UE Context Response message, and sends the context information of the originally saved UE in the SgNB1 to the MgNB on the SgNB1 side.
  • Step 404 Since the UE has not entered the service coverage of the new target secondary base station SgNB2, the MgNB does not need to pass the Xn interface to initiate the SN establishment procedure to the new target secondary base station SgNB2.
  • Step 405 SgNB2 does not need to establish an Xn network connection with the MN temporarily.
  • Step 406 The MME initiates an RRC Connection Resume Reject message or other applicable RRC downlink message to the UE through the air interface Uu.
  • Step 407 The NB initiates a PDU Session Resource Modify Indication process to the AMF/SMF through the NG-C interface, and provides the UPF with the downlink transmission address information that the NB Session 3/4 for the backhaul PDU Session3/4 is allocated by the NB, so that the UPF and the MgNB are established.
  • New NG-U (MN) network connection (NG-U data transmission channel).
  • Step 408 The MgNB initiates a UE Context release process to the source SgNB1 through the Xn interface, and initiates a UE Context Release message. Based on the message, SgNB1 then releases the context information of the originally saved UE on the SgNB1 side.
  • Step 409 When the UE has the uplink control signaling to be transmitted, the UE initiates a RACH procedure to the source MGNB, and indicates the DRB id or QoS Flow id information related to the uplink user data, and attempts to return to the RRC_ACTIVE state.
  • the embodiment of the present disclosure further provides an air interface inactive state maintaining device, which is disposed on a base station, and the air interface inactive state maintaining device provided by the present disclosure includes:
  • the first receiving unit is configured to receive an RRC uplink notification message sent by the UE, where the RRC uplink notification message carries information that is notified by the serving cell that the UE has left the source secondary base station;
  • a migration configuration unit configured to perform, according to the RRC uplink notification message, a migration operation of a related high-level configuration in which the UE is anchored at the source secondary base station side PDU Session, where the migration target node is the target secondary base station or the current primary base station; and is configured to maintain The UE is still in a dual-connected or single-connected air interface inactive state;
  • the first sending unit is configured to send an RRC downlink reply message to the UE after performing the migrating operation of the high-level configuration, where the RRC downlink reply message carries the migration operation completion indication information.
  • the RRC uplink notification message is an RRC Connection Resume Request message
  • the RRC downlink reply message is an RRC Connection Resume Reject message.
  • the migration configuration unit further includes a context obtaining module, configured to acquire, after receiving the RRC uplink notification message sent by the UE, the context information of the UE at the source secondary base station side;
  • the obtaining, by the context obtaining module, the context information of the UE on the source secondary base station side includes:
  • the primary base station sends a context information request message to the source secondary base station, where the information about the UE context index in the active secondary base station is received; the primary base station receives the context information response message replied by the source secondary base station, where the context information response message carries the source secondary base station according to the The UE context index information, and the found UE stored on the source secondary base station is in the source secondary base station side context information.
  • the RRC uplink notification message includes: context index information allocated by the source secondary base station to the UE, and secondary base station release indication information.
  • the RRC uplink notification message further includes at least one of the following: a P-I-RNTI allocated by the primary base station to the UE, and S-I-RNTI and UE RRM measurement result information allocated by the primary base station to the UE.
  • the migration configuration unit further includes a context notification module, configured to: after the acquiring the context information of the UE at the source secondary base station side, according to the new serving cell identifier id of the target secondary base station reported by the UE, The target secondary base station sends a secondary base station notification message, where the secondary base station notification message includes: context information of the UE on the source secondary base station side.
  • the migration configuration unit further includes an address obtaining module, configured to: after the sending the secondary base station notification message to the target secondary base station, receive the secondary base station notification confirmation message sent by the target secondary base station;
  • the acknowledgment message includes: setting the downlink transmission address information of the base station that carries the migrated PDU Session anchored on the secondary base station side.
  • the migration configuration unit further includes an address configuration module, configured to reconfigure the downlink transmission address information of the primary base station that is set to carry the migrated PDU session.
  • the migration configuration unit is further configured to send a PDU Session resource modification indication message to the AMF/SMF, where the PDU Session resource modification indication message carries a PDU session that is configured to carry the migrated PDU.
  • the base station downlink transmits address information.
  • the migration configuration unit further includes a release module, configured to send a context information release message to the source secondary base station, so that the source secondary base station releases the locally saved UE according to the context information release message.
  • a release module configured to send a context information release message to the source secondary base station, so that the source secondary base station releases the locally saved UE according to the context information release message.
  • Source secondary base station side context information configured to send a context information release message to the source secondary base station, so that the source secondary base station releases the locally saved UE according to the context information release message.
  • the RRC downlink reply message includes: context index information corresponding to the context information of the target secondary base station side, and secondary base station update completion indication information.
  • the RRC downlink reply message includes: the secondary base station release completion indication information.
  • the embodiment of the present disclosure further provides an air interface inactive state maintaining device, which is disposed on the user equipment UE, and the air interface inactive state maintaining device provided by the present disclosure includes:
  • the measuring unit is configured to perform RRM air interface measurement on the candidate target serving cells on both sides of the primary base station and the source secondary base station based on the RRM measurement configuration information of the primary base station and the source secondary base station when the air interface is inactive, to determine the current Mobile environment;
  • a second sending unit configured to send an RRC uplink notification message to the primary base station when the update event of the wireless coverage of the source secondary base station is detected by the air interface RRM; the RRC uplink notification message carries the notification that the UE has left the source Information about the coverage of the serving cell of the base station;
  • the second receiving unit is configured to receive an RRC downlink reply message sent by the primary base station, where the RRC downlink reply message carries the migration operation completion indication information.
  • the RRC uplink notification message when the update event is that the wireless coverage of the secondary base station is updated to the target secondary base station, includes: the SI-RNTI allocated by the source secondary base station to the UE, and the new serving cell under the target secondary base station.
  • the RRC downlink reply message includes: New SI-RNTI information, and secondary base station update completion indication information.
  • the RRC uplink notification message when the update event is a radio coverage disappearing event of the secondary base station, includes: an SI-RNTI allocated by the source secondary base station to the UE, and a secondary base station release indication information; the RRC downlink The reply message includes: the secondary base station release completion indication information.
  • the RRC uplink notification message further includes: P-I-RNTI or S-I-RNTI, UE RRM measurement result information allocated by the primary base station to the UE.
  • the embodiment of the present disclosure further provides an air interface inactive state maintaining device, which is disposed on a base station, especially as a base station on the source secondary base station side, and the air interface inactive according to the present disclosure is activated.
  • State maintenance devices include:
  • a third receiving unit configured to receive a context information release message sent by the primary base station
  • a releasing unit configured to release the message based on the received context information, and release the context information of the locally saved UE at the source secondary base station side.
  • the third receiving unit before the third receiving unit receives the context information release message sent by the primary base station, the third receiving unit is further configured to: receive a context information request message sent by the primary base station, where the active secondary base station is involved UE context index information;
  • the air interface inactive state maintaining device includes:
  • the air interface inactive state maintaining apparatus further includes a third sending unit and an address searching unit, where the address searching unit is configured to acquire, according to the UE context index information, the UE corresponding to the locally stored UE context index information at the source secondary base station
  • the third context is configured to send a context information response message to the primary base station, where the context information response message carries context information of the UE stored in the source secondary base station on the source secondary base station side.
  • the embodiment of the present disclosure further provides an air interface inactive state maintaining device, which is disposed on a base station, especially a base station on a target secondary base station side, and the air interface inactive according to the present disclosure is activated.
  • State maintenance devices include:
  • a fourth receiving unit configured to receive a secondary base station notification message sent by the primary base station;
  • the secondary base station notification message includes: context information of the UE at the source secondary base station side;
  • the storage unit is configured to locally store, at the target secondary base station, the context information of the received UE at the source secondary base station side, and the air interface inactive state maintaining device is further configured to complete the migration operation of the UE context information between different secondary base stations.
  • the air interface inactive state maintaining apparatus further includes a fourth sending unit, where the fourth sending unit is configured to send a secondary base station notification confirmation to the primary base station after receiving the secondary base station notification message sent by the primary base station.
  • the secondary base station notification acknowledgement message includes: configured to carry the secondary base station side downlink transmission address information that is required to be anchored to the secondary base station side PDU Session.
  • the embodiment of the present disclosure further provides a base station, where the base station includes an air interface inactive state maintaining device disposed on a primary base station side, and is disposed at a source secondary base station, provided by an embodiment of the present disclosure. At least one of an air interface inactive state maintaining device on the side and an air interface inactive state maintaining device disposed on the target secondary base station side.
  • an embodiment of the present disclosure further provides an electronic device including a memory, a processor, and a computer program stored on the memory and operable on the processor, the processing The processing of any air interface inactive state maintaining method provided by the embodiments of the present disclosure is implemented when the computer program is executed.
  • the embodiments of the present disclosure further provide a computer readable storage medium, where the computer program is stored, and when the computer program is executed by the processor, the implementation of any of the embodiments of the present disclosure is implemented.
  • the processing of the air interface inactive state maintenance method is not limited to, but not limited to, but not limited to, but not limited to, but not limited to, but not limited to, but not limited to, but not limited to, but not limited to, but not limited to the embodiments of the present disclosure.
  • the solution provided by the embodiment of the present disclosure can achieve the following effects: in a dual-connection configuration and entering an inactive state, when the secondary base station changes, the MN can know in time that the UE moves from the source secondary base station to the target secondary base station. Or leaving only the source secondary base station and not entering the new target secondary base station, and the UE context information stored in the source secondary base station can be transferred to the target secondary base station or the primary base station or deleted in time, thereby ensuring network connection.
  • the state and associated high-level configuration can be consistent with the latest mobile state of the UE, thereby providing an effective solution to support the UE to remain in the RRC_INACTIVE inactive state.

Landscapes

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

Abstract

本公开提出了一种空口非激活态维持方法和装置，该方法包括：接收UE发送的RRC上行通知消息；所述RRC上行通知消息携带有通知UE已离开源辅基站的服务小区覆盖的信息；基于所述RRC上行通知消息，执行UE锚定在源辅基站侧PDU Session的相关高层配置的迁移操作，迁移目标节点是目标辅基站或者当前主基站；在执行所述高层配置的迁移操作之后，向所述UE发送RRC下行回复消息；并且维持UE仍然处于双连接或单连接空口非激活态。通过本公开的方案，当UE发生辅基站变化的时候，MN能够及时知道UE从源辅基站移动到了目标辅基站的服务小区覆盖，并保证网络侧连接状态和相关的高层配置能和UE的最新移动状态保持对应一致，从而提供一种支持UE维持在非激活状态的解决方案。

Description

一种空口非激活态维持方法和装置 技术领域
本公开涉及移动通讯技术领域，尤指一种空口非激活态维持方法和装置。
背景技术
在5G***中，支持终端UE(用户设备)单连接(Single Connectivity，SC)和双/多连接(Dual/Multiple Connectivity，DC/MC)配置和操作功能。在SC单连接模式下，UE在空口和网络侧都只有一条数据传输通道，而在DC/MC双/多连接模式下，UE在空口或网络侧都有两条或者以上的数据传输通道。以双连接为例，UE可以在空口，同时与两个NG-RAN基站建立和保持两条独立的无线链路连接(空口数据传输通道)，一个基站称为主基站(Master Node，MN)，另一个基站称为辅基站(Secondary Node，SN)；而MN和SN可以在NG接口，同时和核心网用户面网元节点UPF，同时建立和保持两条独立的网络侧连接(网络数据传输通道)，但只有MN能和核心网控制面网元节点AMF建立和保持NG-C连接，相关架构如附图1所示。处于双连接配置操作的UE，也可以进入到RRC_INACTIVE非激活状态双连接操作同时结合着RRC_INACTIVE非激活状态的好处是：网络侧主辅基站MN/SN和UE都可以同时保持着各自双连接通讯配置的上下文，从而避免网络侧和终端UE回落到单连接配置操作，之后可能又再次通过配置回到双连接操作，相关架构如附图2所示。
在UE不改变当前服务主基站MN和辅基站SN的前提下，UE和网络侧进入和退出RRC_INACTIVE非激活状态的流程，当前标准协议已可以支持；但随着UE移动，当UE离开当前服务主基站MN和辅基站SN小区覆盖的时候，比如：MN发生了切换，SN发生了改变等，UE如何一直维持在RRC_INACTIVE非激活状态，当前标准协议还不能有效地支持。
发明内容
为了解决上述问题，本公开提出了一种空口非激活态维持方法和装置，能够有效的支持UE维持在RRC_INACTIVE非激活状态。
为了解决上述技术问题，本公开提出了一种空口非激活态维持方法，所述方法包括：
接收UE发送的RRC上行通知消息；所述RRC上行通知消息携带有通知UE已离开源辅基站的服务小区覆盖的信息；
基于所述RRC上行通知消息，执行UE锚定在源辅基站侧PDU Session的相关高层配置的迁移操作，迁移目标节点是目标辅基站或者当前主基站；
在执行所述高层配置的迁移操作之后，向所述UE发送RRC下行回复消息，所述RRC下行回复消息携带有迁移操作完成指示信息；并且维持UE仍然处于双连接或单连接空口非激活态。
本公开还提出了一种空口非激活态维持方法，所述方法包括：
在处于空口非激活态时，基于主基站和源辅基站的RRM测量配置信息，执行对主基站和源辅基站两侧的候选目标服务小区的RRM空口测量，以判定当前的移动环境；
在通过所述空口RRM测量感知到源辅基站无线覆盖的更新事件时，向主基站发送的RRC上行通知消息；所述RRC上行通知消息携带有通知UE已离开源辅基站的服务小区覆盖的信息；
接收主基站发送的RRC下行回复消息，所述RRC下行回复消息携带有迁移操作完成指示信息。
本公开还提出了一种空口非激活态维持方法，所述方法包括：
接收主基站发送的上下文信息释放消息；
基于接收的上下文信息释放消息，释放掉本地保存的UE在源辅基站侧上下文信息。
本公开还提出了一种空口非激活态维持方法，所述方法包括：
接收主基站发送的辅基站通知消息；所述辅基站通知消息包含：UE在源辅基站侧上下文信息；
在目标辅基站本地存储接收的UE在源辅基站侧上下文信息，完成对UE上下文信息在不同辅基站之间的迁移操作。
本公开还提出了一种空口非激活态维持装置，设置在基站上，所述装置包括：
第一接收单元，设置为接收UE发送的RRC上行通知消息；所述RRC上行通知消息携带有通知UE已离开源辅基站的服务小区覆盖的信息；
迁移配置单元，设置为基于所述RRC上行通知消息，执行UE锚定在源辅基站侧PDU Session的相关高层配置的迁移操作，迁移目标节点是目标辅基站或者当前主基站；以及，维持UE仍然处于双连接或单连接空口非激活态
第一发送单元，设置为在执行所述高层配置的迁移操作之后，向所述UE发送RRC下行回复消息，所述RRC下行回复消息携带有迁移操作完成指示信息。
本公开还提出了一种空口非激活态维持装置，设置在用户设备UE上，所述装置包括：
测量单元，设置为在处于空口非激活态时，基于主基站和源辅基站的RRM测量配置信息，执行对主基站和源辅基站两侧的候选目标服务小区的RRM空口测量，以判定当前的移动环境；
第二发送单元，设置为在通过所述空口RRM测量感知到源辅基站无线覆盖的更新事件时，向主基站发送的RRC上行通知消息；所述RRC上行通知消息携带有通知UE已离开源辅基站的服务小区覆盖的信息；
第二接收单元，设置为接收主基站发送的RRC下行回复消息，所述RRC下行回复消息携带有迁移操作完成指示信息。
本公开还提出了一种空口非激活态维持装置，设置在基站上，所述装置包括：
第三接收单元，设置为接收主基站发送的上下文信息释放消息；
释放单元，设置为基于接收的上下文信息释放消息，释放掉本地保存的UE在源辅基站侧上下文信息。
本公开还提出了一种空口非激活态维持装置，设置在基站上，所述装置包括：
第四接收单元，设置为接收主基站发送的辅基站通知消息；所述辅基站通知消息包含：UE在源辅基站侧上下文信息；
存储单元，设置为在目标辅基站本地存储接收的UE在源辅基站侧上下文信息，完成对UE上下文信息在不同辅基站之间的迁移操作。
本公开还提出了一种电子设备，包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现本公开提供的任一空口非激活态维持方法的处理。
本公开还提出了一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现本公开提供的任一空口非激活态维持方法的处理。
与相关技术相比，本公开提供的技术方案包括：接收UE发送的RRC上行通知消息；所述RRC上行通知消息携带有通知UE已离开源辅基站的服务小区覆盖的信息；基于所述RRC上行通知消息，执行UE锚定在源辅基站侧PDU Session的相关高层配置的迁移操作，迁移目标节点是目标辅基站或者当前主基站；在执行所述高层配置的迁移操作之后，向所述UE发送RRC下行回复消息，所述RRC下行回复消息携带有迁移操作完成指示信息；并且维持UE仍然处于双连接或单连接空口非激活态。通过本公开的方案，处于双连接配置且进入非激活状态的UE，当发生辅基站变化的时候，MN能够及时知道UE从源辅基站移动到了目标辅基站的服务小区覆盖，或者仅离开源辅基站而并没有进入新的目标辅基站，源辅基站内保存的UE上下文信息，能够及时地被传递转移到目标辅基站或主基站内或者被删除，从而保证网络侧连接状态和相关的高层配置能和UE的最新移动状态保持对应一致，从而提供了一种有效的支持UE维持在RRC_INACTIVE非激活状态的解决方案。
附图说明
下面对本公开实施例中的附图进行说明，实施例中的附图是用于对本公开的进一步理解，与说明书一起用于解释本公开，并不构成对本公开保护范围的限制。
图1为终端UE双连接操作激活态架构图；
图2为终端UE双连接操作非激活态架构图；
图3为双连接非激活态UE从SN-1小区覆盖移动到SN-2小区覆盖；
图4为双连接非激活态UE在源SN-1的架构图；
图5为双连接非激活态UE在新目标SN-2后的架构图；
图6、图7、图8和图9分别为本公开实施例提供的一种空口非激活态维持方法的流程图。
具体实施方式
为了便于本领域技术人员的理解，下面结合附图对本公开作进一步的描述，并不能用来限制本公开的保护范围。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的各种方式可以相互组合。
本公开提出了一种空口非激活态维持方法，所述方法包括：
步骤011，接收UE发送的RRC上行通知消息；所述RRC上行通知消息携带有通知UE已离开源辅基站的服务小区覆盖的信息；
该RRC上行通知消息为RRC Connection Resume Request消息或其它适用的RRC上行消息；RRC上行通知消息为UE在空口非激活态时与网络侧之间能够进行传输的上行消息；
在一个示例中，所述RRC上行通知消息包含：主基站给UE分配的P-I-RNTI、SgNB1给UE分配的上下文索引信息S-I-RNTI、SgNB2下新服务小区标识id、以及辅基站更新指示信息。本公开实施例中，辅基站更新指示信息可以携带恢复原因值Casue value中，例如，设置恢复原因值Casue value＝SN change；
在另一个示例中，所述RRC上行通知消息包含：SgNB1给UE分配的S-I-RNTI、SgNB2下新服务小区标识id、以及辅基站更新指示信息；
其中，主基站为UE对应的主基站，SgNB1为源辅基站，SgNB2为目标辅基站；即，SgNB1为UE位置切换之前对应的辅基站，SgNB2为UE位置切换之后对应的辅基站；
步骤012，基于所述RRC上行通知消息，执行UE锚定在源辅基站侧PDU Session的相关高层配置的迁移操作，迁移目标节点是目标辅基站或者当前主基站；
其中，步骤012包括：
步骤0121，主基站根据接收SgNB2下新服务小区标识id，确定UE移动到SgNB2下新服务小区标识id对应的服务小区；
步骤0122，主基站获取UE在SgNB1侧上下文；
一种方式包括：在主机站存储有UE在SgNB1侧上下文信息的情况下，主基站基于S-I-RNTI信息，通过索引方式，找到储存的UE在SgNB1侧上下文信息；
另一种方式包括：主基站向源辅基站SgNB1发起UE Context获取流程，包括：
步骤0122a、主基站向源辅基站SgNB1发送上下文信息请求消息，其中携带有S-I-RNTI信息，所述S-I-RNTI信息含有SgNB1内相关的UE上下文索引信息；优选地，所述上下文信息请求消息为Retrieve UE Context Request消息。
其中，主基站通过Xn接口向源辅基站SgNB1发起UE Context获取流程。
步骤0122b、主基站接收源辅基站SgNB1回复的上下文信息响应消息，所述上下文信息响应消息携带SgNB1内原来保存的UE在SgNB1侧上下文信息。优选地，所述上下文信息响应消息为Retrieve UE Context Response消息。
步骤0123，主基站向目标辅基站SgNB2发送辅基站通知消息；所述辅基站通知消息 包含：源SgNB1对应的UE在SgNB1侧上下文信息；
步骤0124，主基站接收目标辅基站SgNB2发送的辅基站通知确认消息；所述辅基站通知确认消息包含：用于承载PDU Session2需要的SgNB2侧下行传输地址信息；
本公开实施例中，优选地，所述辅基站通知消息为SN Addition Request消息；所述辅基站通知确认消息为SN Addition Request ACK消息。
步骤0125，主基站向AMF/SMF发起PDU Session资源修改指示流程；
包括：主基站向AMF/SMF发送PDU Session资源修改指示信息，所述PDU Session资源修改指示信息携带有用于承载被迁移后的PDU Session的基站下行传输地址信息。
步骤0126，主基站向源SgNB1发送上下文信息释放消息，从而使得SgNB1基于该消息，释放掉原来保存的UE在SgNB1侧上下文信息。其中，上下文信息释放消息可以是UE Context Release消息。
步骤013，向所述UE发送RRC下行回复消息，所述RRC下行回复消息携带有迁移操作完成指示信息；并且维持UE仍然处于双连接或单连接空口非激活态。
该RRC下行回复消息为RRC Connection Resume Reject消息或其它适用的RRC下行消息；RRC下行通知消息为UE在空口非激活态时网络侧能够向UE传输的下行消息；
该RRC下行回复消息包含：New S-I-RNTI信息、和SN更新完成指示信息。本公开实施例中，SN更新完成指示信息可以携带在拒绝原因值Casue value中，例如，设置拒绝原因值Casue value＝SN Change Done；
在主基站给UE新分配P-I-RNTI的情况下，该RRC下行回复消息还包含新分配的New P-I-RNTI。
步骤014，主基站在UE需要切换至双连接激活态时，启动UE恢复到双连接激活态。例如，在UE有上行用户数据抵达待传输，或有下行用户数据抵达待传输，或有下行控制数据抵达待传输的情况下，需要切换至双连接激活态。
基于与上述实施例相同或相似的构思，本公开提出了一种空口非激活态维持方法，所述方法包括：
步骤021，主基站接收UE发送的RRC上行通知消息；
该RRC上行通知消息为RRC Connection Resume Request消息或其它适用的RRC上行消息；
在一个示例中，所述RRC上行通知消息包含：主基站给UE分配的P-I-RNTI、SgNB1给UE分配的S-I-RNTI、以及辅基站释放指示信息，本公开实施例中，辅基站释放指示信息可以携带恢复原因值Casue value中，例如，设置恢复原因值Casue value＝SN Release；
在另一个示例中，所述RRC上行通知消息包含：SgNB1给UE分配的S-I-RNTI、以及恢复原因值Casue value＝SN Release；
其中，主基站为UE对应的主基站，SgNB1为源辅基站；在切换之后，UE不存在相应的辅基站小区；
步骤022，主基站确定UE移动到SgNB2下新服务小区标识id对应的服务小区；
其中，基于接收的恢复原因值Casue value＝SN Release，主基站确定UE移出SgNB1下的服务小区。
步骤023，主基站获取UE在SgNB1侧上下文信息；
一种方式包括：在主机站存储有UE在SgNB1侧上下文信息的情况下，主基站基于S-I-RNTI信息，通过索引方式，找到储存的UE在SgNB1侧上下文信息；
另一种方式包括：主基站向源辅基站SgNB1发起UE Context获取流程，包括：
步骤023a、主基站向源辅基站SgNB1发送上下文信息请求消息，其中携带有S-I-RNTI信息，所述S-I-RNTI信息含有SgNB1内相关的UE上下文索引信息；
其中，主基站通过Xn接口向源辅基站SgNB1发起UE Context获取流程。
步骤023b、主基站接收源辅基站SgNB1回复的上下文信息响应消息，所述上下文信息响应消息携带SgNB1内原来保存的UE在源辅基站侧上下文信息信息。
步骤026，主基站向UE发送RRC下行回复消息；
该RRC下行回复消息为RRC Connection Resume Reject消息或其它适用的RRC下行消息；
该RRC下行回复消息包含：SN释放完成指示信息。本公开实施例中，SN释放完成指示信息可以携带在拒绝原因值Casue value中，例如，设置拒绝原因值Casue value＝SN Release Done；
在主基站给UE新分配P-I-RNTI的情况下，该RRC下行回复消息还包含新分配的New P-I-RNTI。或者，主基站没有给UE新分配P-I-RNTI的情况下，该RRC下行回复消息还包含基站给UE之前分配的P-I-RNTI。
步骤027，主基站向AMF/SMF发起PDU Session资源修改指示流程；
包括：主基站向AMF/SMF发送PDU Session资源修改指示信息，所述PDU Session资源修改指示信息携带有用于承载PDU Session2需要的下行传输地址信息。该下行地址是主基站为承载PDU Session2新配置的下行地址。
优选地，所述PDU Session资源修改指示信息为PDU Session Resource Modify Indication消息。
步骤028，主基站向源SgNB1发送UE Context Release消息，从而使得SgNB1基于该消息，释放掉原来保存的UE在SgNB1侧上下文信息。
步骤029，主基站在UE需要切换至双连接激活态时，启动UE恢复到双连接激活态。例如，在UE有上行用户数据抵达待传输，或有下行用户数据抵达待传输，或有下行控制数据抵达待传输的情况下，需要切换至双连接激活态。
基于与上述实施例相同或相似的构思，本公开实施例提出了一种空口非激活态维持方法，所述方法包括：
步骤031，UE向主基站发送的RRC上行通知消息；该RRC上行通知消息为RRC  Connection Resume Request消息或其它适用的RRC上行消息；
在一个示例中，所述RRC上行通知消息包含：主基站给UE分配的P-I-RNTI、SgNB1给UE分配的S-I-RNTI、SgNB2下新服务小区标识id、以及恢复原因值Casue value＝SN change；
在另一个示例中，所述RRC上行通知消息包含：SgNB1给UE分配的S-I-RNTI、SgNB2下新服务小区标识id、以及恢复原因值Casue value＝SN change；
其中，主基站为UE对应的主基站，SgNB1为UE位置切换之前对应的辅基站，SgNB2为UE位置切换之后对应的辅基站；
步骤032，UE接收主基站发送的RRC下行回复消息，该RRC下行回复消息为RRC Connection Resume Reject消息或其它适用的RRC下行消息；该RRC下行回复消息包含：New S-I-RNTI信息、和拒绝原因值Casue value＝SN Change Done；
在主基站给UE新分配P-I-RNTI的情况下，该RRC下行回复消息还包含新分配的New P-I-RNTI。
步骤033，在UE需要切换至双连接激活态时，UE向主基站发送RRC Connection Resume Request消息。
例如，在一个示例中，所述RRC Connection Resume Request消息或其它适用的RRC上行消息包含：主基站给UE分配的P-I-RNTI、SgNB1给UE分配的S-I-RNTI、以及UL data Arriving。
基于与上述实施例相同或相似的构思，本公开实施例提出了一种空口非激活态维持方法，所述方法包括：
步骤041，UE向主基站发送RRC上行通知消息；该RRC上行通知消息为RRC Connection Resume Request消息或其它适用的RRC上行消息；
在一个示例中，所述RRC上行通知消息包含：主基站给UE分配的P-I-RNTI、SgNB1给UE分配的S-I-RNTI、以及恢复原因值Casue value＝SN Release；
在另一个示例中，所述RRC上行通知消息包含：SgNB1给UE分配的S-I-RNTI、以及恢复原因值Casue value＝SN Release；
其中，主基站为UE对应的主基站，SgNB1为UE位置切换之前对应的辅基站，SgNB2为UE位置切换之后对应的辅基站；
步骤042，UE接收主基站发送的RRC下行回复消息；该RRC下行回复消息为RRC Connection Resume Reject消息或其它适用的RRC下行消息；该RRC下行回复消息包含：拒绝原因值Casue value＝SN Change Done；
可选地，该RRC下行回复消息还包含主基站为UE分配的P-I-RNTI。
步骤043，在UE需要切换至双连接激活态时，UE向主基站发送的RRC Connection Resume Request消息或其它适用的RRC上行消息。
例如，在一个示例中，所述RRC Connection Resume Request消息或其它适用的RRC 上行消息包含：主基站给UE分配的P-I-RNTI、SgNB1给UE分配的S-I-RNTI以及UL data Arriving。
基于与上述实施例相同或相似的构思，本公开实施例提出了一种空口非激活态维持方法，所述方法包括：
步骤051，源辅基站SgNB1接收主基站发送的上下文信息请求消息，其中携带有S-I-RNTI信息，所述S-I-RNTI信息含有SgNB1内相关的UE上下文索引信息；
其中，源辅基站SgNB1通过Xn接口接收主基站发发起的UE Context获取流程。
步骤052、源辅基站SgNB1向主基站发送回复的上下文信息响应消息，所述上下文信息响应消息携带SgNB1内原来保存的UE在SgNB1侧上下文信息。
步骤053，源辅基站SgNB1接收主基站发送的UE Context Release消息；
步骤054，SgNB1基于接收的UE Context Release消息，释放掉本地保存的UE在SgNB1侧上下文信息。
基于与上述实施例相同或相似的构思，本公开提出了一种空口非激活态维持方法，所述方法包括：
步骤061，目标辅基站SgNB2接收主基站发送的辅基站通知消息；所述辅基站通知消息包含：源SgNB1对应的UE在SgNB1侧上下文信息；
步骤062，目标辅基站SgNB2在本地存储接收的UE在SgNB1侧上下文信息；
步骤063，目标辅基站SgNB2向主基站发送辅基站通知确认消息；所述辅基站通知确认消息包含：用于承载PDU Session2需要的SgNB2侧下行传输地址信息。
下面结合具体的实施场景进行说明。
实施例1
流程如附图6所示：某UE处于MeNB和SgNB1双连接工作模式，且PDU Session1锚定建立在MeNB侧；同时PDU Session2锚定建立在SgNB1侧。某时刻，PDU Session1和2的用户数据暂时中断停止，MeNB决定通过空口Suspend流程，将UE重配置到RRC_INACTIVE非激活状态，从而释放掉MCG Radio Link和SCG Radio Link和低层的无线配置。MeNB保存着NG-C和NG-U(MN)网络连接，和PDU Session1相关的高层配置；SgNB1保存着NG-U(SN)网络连接，和PDU Session2相关的高层配置；UE保存着PDU Session1和2相关的高层配置。
步骤101：UE处于双连接配置和RRC_INACTIVE非激活状态，仍然继续执行对部署有候选目标辅基站的各个异频点RRM无线测量。当UE测量后，发现自己已进入到新的目标辅基站SgNB2之后，UE在空口Uu触发RRC连接恢复流程，发起RRC Connection Resume Request消息或其它适用的RRC上行消息。RRC Connection Resume Request消息或其它适用的RRC上行消息包含：MeNB/SgNB1之前给UE分配的P-I-RNTI和S-I-RNTI信息，SgNB2下新服务小区标识id，恢复原因值Casue value＝SN change。
P-I-RNTI信息包含源MeNB基站标识id和MeNB侧保存的UE在MeNB侧上下文的 索引信息。
S-I-RNTI信息包含源SgNB1基站标识id和SgNB1侧保存的UE在SgNB1侧上下文的索引信息。
步骤102：MeNB接收到该RRC Connection Resume Request消息或其它适用的RRC上行消息之后，基于P-I-RNTI信息，通过索引方式，能找到MeNB内保存的UE在MeNB侧上下文信息(即MeNB侧的网络连接和相关高层配置)；基于S-I-RNTI信息，通过索引方式，能找到SgNB1内保存的UE在SgNB1侧上下文信息(即SgNB1侧的网络连接和相关高层配置)；基于UE上报的恢复原因值Casue value＝SN change，得知该UE移动发生了辅基站SN变化(SgNB1-)SgNB2)，基于SgNB2下新服务小区标识id，MeNB得知UE已经移动到了SgNB2某服务小区覆盖之下。
步骤103：MeNB通过Xn接口，向源辅基站SgNB1发起UE Context获取流程，发起Retrieve UE Context Request消息，其中S-I-RNTI信息含有SgNB1内相关的UE上下文索引信息；基于该获取请求消息，源辅基站SgNB1回复Retrieve UE Context Response消息，把SgNB1内原来保存的UE在SgNB1侧上下文信息发送给MeNB。
步骤104：MeNB再通过Xn接口，向新目标辅基站SgNB2发起SN建立流程，发起SN Addition Request消息；SN Addition Request消息包含：源SgNB1内原来保存的UE在SgNB1侧上下文信息，从而将该上下文信息发送给SgNB2并进行保存。基于该上下文信息，SgNB2于是得知自己需要去承载PDU Session2(原来被SgNB1承载)及其相关的上下文配置。注：因为是非激活态，SgNB2不需要建立SCG低层的无线配置，仅仅继续保存UE在SN侧的网络连接和相关高层配置。
步骤105：SgNB2通过Xn接口，向MeNB发起SN Addition Request ACK消息；SN Addition Request ACK消息包含：用于承载PDU Session2需要的SgNB2侧下行传输地址信息。SgNB2基于MeNB转发来的SN侧上下文信息，可得知PDU Session2原来在UPF侧的上行传输地址，进一步和UPF建立NG-U(SN)网络连接(NG-U数据传输通道)，再进一步建立完成和MN的Xn网络连接。
步骤106：MeNB通过空口Uu向UE发起RRC Connection Resume Reject消息或其它适用的RRC下行消息；该RRC Connection Resume Reject消息或其它适用的RRC下行消息包含：MeNB给UE新分配的New P-I-RNTI和New S-I-RNTI信息，拒绝原因值Casue value＝SN Change Done。
步骤107：MeNB通过NG-C接口向AMF/SMF发起PDU Session Resource Modify Indication流程，向UPF提供SgNB2刚分配的用于承载PDU Session2需要的SgNB2侧下行传输地址信息，从而UPF和SgNB2建立完成新的NG-U(SN)网络连接(NG-U数据传输通道)。
步骤108：MeNB通过Xn接口，向源SgNB1发起UE Context释放流程，发起UE Context Release消息。基于该消息，SgNB1随后释放掉原来保存的UE在SgNB1侧上下 文信息。
步骤109：当UE有上行用户数据抵达待传输，UE向源MeNB发起RACH流程，并且指示该上行用户数据相关的DRB id或QoS Flow id信息，尝试恢复到RRC_ACTIVE状态。
实施例2
流程如附图7所示：某UE处于MgNB和SgNB1双连接工作模式，且PDU Session1/2锚定建立在MgNB侧；同时PDU Session3/4锚定建立在SgNB1侧。某时刻，PDU Session1/2和3/4的用户数据暂时中断停止，MgNB决定通过空口Suspend流程，将UE重配置到RRC_INACTIVE非激活状态，从而释放掉MCG Radio Link和SCG Radio Link和低层的无线配置。MgNB保存着NG-C和NG-U(MN)网络连接，和PDU Session1/2相关的高层配置；SgNB1保存着NG-U(SN)网络连接，和PDU Session3/4相关的高层配置；UE保存着PDU Session1/2/3/4相关的高层配置。
步骤201：UE处于双连接配置和RRC_INACTIVE非激活状态，仍然继续执行对部署有候选目标辅基站的各个异频点RRM无线测量。当UE测量后，发现自己已进入到新的目标辅基站SgNB2之后，UE在空口Uu触发RRC连接恢复流程，发起RRC Connection Resume Request消息或其它适用的RRC上行消息。RRC Connection Resume Request消息或其它适用的RRC上行消息包含：MgNB/SgNB1之前给UE分配的S-I-RNTI信息(由于UE没有离开MgNB服务小区的覆盖，因此暂时不用上报P-I-RNTI信息)，SgNB2下新服务小区物理层标识NR-PCI，恢复原因值Casue value＝SN change。
S-I-RNTI信息包含源SgNB1基站标识id和SgNB1侧保存的UE在SgNB1侧上下文的索引信息。
步骤202：MgNB接收到该RRC Connection Resume Request消息或其它适用的RRC上行消息之后，基于S-I-RNTI信息，通过索引方式，能找到SgNB1内保存的UE在SgNB1侧上下文信息(即SgNB1侧的网络连接和相关高层配置)；基于UE上报的恢复原因值Casue value＝SN change，得知该UE移动发生了辅基站SN变化(SgNB1-)SgNB2)，基于SgNB2下新服务小区物理层标识NR-PCI，通过网管地址匹配查询，MgNB得知UE已经移动到了SgNB2某服务小区覆盖之下。
步骤203：MgNB通过Xn接口，向源辅基站SgNB1发起UE Context获取流程，发起Retrieve UE Context Request消息，其中S-I-RNTI信息含有SgNB1内相关的UE上下文索引信息；基于该获取请求消息，源辅基站SgNB1回复Retrieve UE Context Response消息，把SgNB1内原来保存的UE在SgNB1侧上下文信息发送给MgNB。
步骤204：MgNB再通过Xn接口，向新目标辅基站SgNB2发起SN建立流程，发起SN Addition Request消息；SN Addition Request消息包含：源SgNB1内原来保存的UE在SgNB1侧上下文信息，从而将该上下文信息发送给SgNB2并进行保存。基于该上下文信息，SgNB2于是得知自己需要去承载PDU Session3/4(原来被SgNB1承载)及其相关的 上下文配置。注：因为是非激活态，SgNB2不需要建立SCG低层的无线配置，仅仅继续保存UE在SN侧的网络连接和相关高层配置。
步骤205：SgNB2通过Xn接口，向MgNB发起SN Addition Request ACK消息；SN Addition Request ACK消息包含：用于承载PDU Session3/4需要的SgNB2侧下行传输地址信息。SgNB2基于MgNB转发来的SN侧上下文信息，可得知PDU Session3/4原来在UPF侧的上行传输地址，进一步和UPF建立NG-U(SN)网络连接(NG-U数据传输通道)，再进一步建立完成和MN的Xn网络连接。
步骤206：MgNB通过空口Uu向UE发起RRC Connection Resume Reject消息或其它适用的RRC下行消息；该RRC Connection Resume Reject消息或其它适用的RRC下行消息包含：MgNB给UE新分配的New S-I-RNTI信息，拒绝原因值Casue value＝SN Change Done。
步骤207：MgNB通过NG-C接口向AMF/SMF发起PDU Session Resource Modify Indication流程，向UPF提供SgNB2刚分配的用于承载PDU Session3/4需要的SgNB2侧下行传输地址信息，从而UPF和SgNB2建立完成新的NG-U(SN)网络连接(NG-U数据传输通道)。
步骤208：MgNB通过Xn接口，向源SgNB1发起UE Context释放流程，发起UE Context Release消息。基于该消息，SgNB1随后释放掉原来保存的UE在SgNB1侧上下文信息。
步骤209：当UE有上行控制信令抵达待传输，UE向源MgNB发起RACH流程，并且指示该上行用户数据相关的DRB id或QoS Flow id信息，尝试恢复到RRC_ACTIVE状态。
实施例3
流程如附图8所示：某UE处于MeNB和SgNB1双连接工作模式，且PDU Session1锚定建立在MeNB侧；同时PDU Session2锚定建立在SgNB1侧。某时刻，PDU Session1和2的用户数据暂时中断停止，MeNB决定通过空口Suspend流程，将UE重配置到RRC_INACTIVE非激活状态，从而释放掉MCG Radio Link和SCG Radio Link和低层的无线配置。MeNB保存着NG-C和NG-U(MN)网络连接，和PDU Session1相关的高层配置；SgNB1保存着NG-U(SN)网络连接，和PDU Session2相关的高层配置；UE保存着PDU Session1和2相关的高层配置。
步骤301：UE处于双连接配置和RRC_INACTIVE非激活状态，仍然继续执行对部署有候选目标辅基站的各个异频点RRM无线测量。当UE测量后，发现自己离开SgNB1服务覆盖，但还没进入新目标辅基站SgNB2的服务覆盖，UE在空口Uu触发RRC连接恢复流程，发起RRC Connection Resume Request消息或其它适用的RRC上行消息。RRC Connection Resume Request消息或其它适用的RRC上行消息包含：MeNB/SgNB1之前给UE分配的P-I-RNTI和S-I-RNTI信息，恢复原因值Casue value＝SN Release。
P-I-RNTI信息包含源MeNB基站标识id和MeNB侧保存的UE在MeNB侧上下文的索引信息。
S-I-RNTI信息包含源SgNB1基站标识id和SgNB1侧保存的UE在SgNB1侧上下文的索引信息。
步骤302：MeNB接收到该RRC Connection Resume Request消息或其它适用的RRC上行消息之后，基于P-I-RNTI信息，通过索引方式，能找到MeNB内保存的UE在MeNB侧上下文信息(即MeNB侧的网络连接和相关高层配置)；基于S-I-RNTI信息，通过索引方式，能找到SgNB1内保存的UE在SgNB1侧上下文信息(即SgNB1侧的网络连接和相关高层配置)；基于UE上报的恢复原因值Casue value＝SN Release，得知该UE移动离开了源辅基站SgNB1服务覆盖。
步骤303：MeNB通过Xn接口，向源辅基站SgNB1发起UE Context获取流程，发起Retrieve UE Context Request消息，其中S-I-RNTI信息含有SgNB1内相关的UE上下文索引信息；基于该获取请求消息，源辅基站SgNB1回复Retrieve UE Context Response消息，把SgNB1内原来保存的UE在SgNB1侧上下文信息发送给MeNB。
步骤304：由于UE还没进入新目标辅基站SgNB2的服务覆盖，MeNB不需要通过Xn接口，向新目标辅基站SgNB2发起SN建立流程。
步骤305：SgNB2暂时不需要和MN建立Xn网络连接。
步骤306：MeNB通过空口Uu向UE发起RRC Connection Resume Reject消息或其它适用的RRC下行消息；该RRC Connection Resume Reject消息或其它适用的RRC下行消息包含：MeNB给UE新分配的New P-I-RNTI信息，拒绝原因值Casue value＝SN Release Done。
步骤307：MeNB通过NG-C接口向AMF/SMF发起PDU Session Resource Modify Indication流程，向UPF提供MeNB刚分配的用于承载回流的PDU Session2需要的下行传输地址信息，从而UPF和MeNB建立完成新的NG-U(MN)网络连接(NG-U数据传输通道)。
步骤308：MeNB通过Xn接口，向源SgNB1发起UE Context释放流程，发起UE Context Release消息。基于该消息，SgNB1随后释放掉原来保存的UE在SgNB1侧上下文信息。
步骤309：当UE有上行用户数据抵达待传输，UE向源MeNB发起RACH流程，并且指示该上行用户数据相关的DRB id或QoS Flow id信息，尝试恢复到RRC_ACTIVE状态。
实施例4
流程如附图9所示：某UE处于MgNB和SgNB1双连接工作模式，且PDU Session1/2锚定建立在MgNB侧；同时PDU Session3/4锚定建立在SgNB1侧。某时刻，PDU Session1/2和3/4的用户数据都暂时中断停止，MgNB决定通过空口Suspend流程，将UE重配置到 RRC_INACTIVE非激活状态，从而释放掉MCG Radio Link和SCG Radio Link和低层的无线配置。MgNB保存着NG-C和NG-U(MN)网络连接，和PDU Session1/2相关的高层配置；SgNB1保存着NG-U(SN)网络连接，和PDU Session3/4相关的高层配置；UE保存着PDU Session1/2/3/4相关的高层配置。
步骤401：UE处于双连接配置和RRC_INACTIVE非激活状态，仍然继续执行对部署有候选目标辅基站的各个异频点RRM无线测量。当UE测量后，发现自己离开SgNB1服务覆盖，但还没进入新目标辅基站SgNB2的服务覆盖，UE在空口Uu触发RRC连接恢复流程，发起RRC Connection Resume Request消息或其它适用的RRC上行消息。RRC Connection Resume Request消息或其它适用的RRC上行消息包含：MgNB/SgNB1之前给UE分配的P-I-RNTI和S-I-RNTI信息，恢复原因值Casue value＝SN Release。
P-I-RNTI信息包含源MgNB基站标识id和MgNB侧保存的UE在MgNB侧上下文的索引信息。
S-I-RNTI信息包含源SgNB1基站标识id和SgNB1侧保存的UE在SgNB1侧上下文的索引信息。
步骤402：MgNB接收到该RRC Connection Resume Request消息或其它适用的RRC上行消息之后，基于P-I-RNTI信息，通过索引方式，能找到MgNB内保存的UE在MgNB侧上下文信息(即MgNB侧的网络连接和相关高层配置)；基于S-I-RNTI信息，通过索引方式，能找到SgNB1内保存的UE在SgNB1侧上下文信息(即SgNB1侧的网络连接和相关高层配置)；基于UE上报的恢复原因值Casue value＝SN Release，得知该UE移动离开了源辅基站SgNB1服务覆盖。
步骤403：MgNB通过Xn接口，向源辅基站SgNB1发起UE Context获取流程，发起Retrieve UE Context Request消息，其中S-I-RNTI信息含有SgNB1内相关的UE上下文索引信息；基于该获取请求消息，源辅基站SgNB1回复Retrieve UE Context Response消息，把SgNB1内原来保存的UE在SgNB1侧上下文信息发送给MgNB。
步骤404：由于UE还没进入新目标辅基站SgNB2的服务覆盖，MgNB不需要通过Xn接口，向新目标辅基站SgNB2发起SN建立流程。
步骤405：SgNB2暂时不需要和MN建立Xn网络连接。
步骤406：MgNB通过空口Uu向UE发起RRC Connection Resume Reject消息或其它适用的RRC下行消息；该RRC Connection Resume Reject消息或其它适用的RRC下行消息包含：MgNB给UE新分配的New P-I-RNTI信息，拒绝原因值Casue value＝SN Release Done。
步骤407：MgNB通过NG-C接口向AMF/SMF发起PDU Session Resource Modify Indication流程，向UPF提供MgNB刚分配的用于承载回流的PDU Session3/4需要的下行传输地址信息，从而UPF和MgNB建立完成新的NG-U(MN)网络连接(NG-U数据传输通道)。
步骤408：MgNB通过Xn接口，向源SgNB1发起UE Context释放流程，发起UE Context Release消息。基于该消息，SgNB1随后释放掉原来保存的UE在SgNB1侧上下文信息。
步骤409：当UE有上行控制信令抵达待传输，UE向源MgNB发起RACH流程，并且指示该上行用户数据相关的DRB id或QoS Flow id信息，尝试恢复到RRC_ACTIVE状态。
基于与上述实施例相同或相似的构思，本公开实施例还提供一种空口非激活态维持装置，设置在基站上，本公开提出的一种空口非激活态维持装置包括：
第一接收单元，设置为接收UE发送的RRC上行通知消息；所述RRC上行通知消息携带有通知UE已离开源辅基站的服务小区覆盖的信息；
迁移配置单元，设置为基于所述RRC上行通知消息，执行UE锚定在源辅基站侧PDU Session的相关高层配置的迁移操作，迁移目标节点是目标辅基站或者当前主基站；以及，设置为维持UE仍然处于双连接或单连接空口非激活态；
第一发送单元，设置为在执行所述高层配置的迁移操作之后，向所述UE发送RRC下行回复消息，所述RRC下行回复消息携带有迁移操作完成指示信息。
本公开实施例中，所述RRC上行通知消息为RRC Connection Resume Request消息；
所述RRC下行回复消息为RRC Connection Resume Reject消息。
本公开实施例中，所述迁移配置单元还包括上下文获取模块，设置为在接收UE发送的RRC上行通知消息之后，获取UE在源辅基站侧上下文信息；
所述上下文获取模块获取UE在源辅基站侧上下文信息包括：
基于上下文索引信息，通过索引查找到主基站本地储存的UE在源辅基站侧上下文信息；
或，
向源辅基站发送上下文信息请求消息，其中携带有源辅基站内相关的UE上下文索引信息；主基站接收源辅基站回复的上下文信息响应消息，所述上下文信息响应消息携带源辅基站根据所述UE上下文索引信息，而找到的在源辅基站上存储的UE在源辅基站侧上下文信息。
本公开实施例中，所述RRC上行通知消息包含：源辅基站给UE分配的上下文索引信息、以及辅基站释放指示信息。
本公开实施例中，所述RRC上行通知消息还包含如下内容至少一项：主基站给UE分配的P-I-RNTI、主基站给UE分配的S-I-RNTI、UE RRM测量结果信息。
本公开实施例中，所述迁移配置单元还包括上下文通知模块，设置为在所述获取UE在源辅基站侧上下文信息之后，根据UE上报的所述目标辅基站下新服务小区标识id，向目标辅基站发送辅基站通知消息；所述辅基站通知消息包含：UE在源辅基站侧的上下文信息。
本公开实施例中，所述迁移配置单元还包括地址获取模块，设置为在所述向目标辅基站发送辅基站通知消息之后，接收目标辅基站发送的辅基站通知确认消息；所述辅基站通知确认消息包含：设置为承载锚定于辅基站侧的迁移后的PDU Session的基站下行传输地址信息。
本公开实施例中，所述迁移配置单元还包括地址配置模块，设置为重新配置设置为承载被迁移后的PDU Session的主基站下行传输地址信息。
本公开实施例中，所述迁移配置单元还网络侧更新模块，设置为向AMF/SMF发送PDU Session资源修改指示消息，所述PDU Session资源修改指示消息携带有设置为承载被迁移后的PDU Session的基站下行传输地址信息。
本公开实施例中，所述迁移配置单元还包括释放模块，设置为向源辅基站发送的上下文信息释放消息，以使得所述源辅基站根据所述上下文信息释放消息释放掉本地保存的UE在源辅基站侧上下文信息。
本公开实施例中，所述RRC下行回复消息包含：UE在目标辅基站侧上下文信息对应的上下文索引信息、以及辅基站更新完成指示信息。
本公开实施例中，所述RRC下行回复消息包含：辅基站释放完成指示信息。
基于与上述实施例相同或相似的构思，本公开实施例还提供一种空口非激活态维持装置，设置在用户设备UE上，本公开提出的一种空口非激活态维持装置包括：
测量单元，设置为在处于空口非激活态时，基于主基站和源辅基站的RRM测量配置信息，执行对主基站和源辅基站两侧的候选目标服务小区的RRM空口测量，以判定当前的移动环境；
第二发送单元，设置为在通过所述空口RRM测量感知到源辅基站无线覆盖的更新事件时，向主基站发送的RRC上行通知消息；所述RRC上行通知消息携带有通知UE已离开源辅基站的服务小区覆盖的信息；
第二接收单元，设置为接收主基站发送的RRC下行回复消息，所述RRC下行回复消息携带有迁移操作完成指示信息。
本公开实施例中，在所述更新事件为辅基站的无线覆盖更新到目标辅基站时，所述RRC上行通知消息包含：源辅基站给UE分配的S-I-RNTI、目标辅基站下新服务小区标识id、以及辅基站更新指示信息；所述RRC下行回复消息包含：New S-I-RNTI信息、以及、辅基站更新完成指示信息。
本公开实施例中，所述更新事件为辅基站的无线覆盖消失事件时，所述RRC上行通知消息包含：源辅基站给UE分配的S-I-RNTI、以及辅基站释放指示信息；所述RRC下行回复消息包含：辅基站释放完成指示信息。
本公开实施例中，所述RRC上行通知消息还包含：主基站给UE分配的P-I-RNTI或S-I-RNTI，UE RRM测量结果信息。
基于与上述实施例相同或相似的构思，本公开实施例还提供一种空口非激活态维持装 置，设置在基站上，尤其是作为源辅基站侧的基站，本公开提出的一种空口非激活态维持装置包括：
第三接收单元，设置为接收主基站发送的上下文信息释放消息；
释放单元，设置为基于接收的上下文信息释放消息，释放掉本地保存的UE在源辅基站侧上下文信息。
本公开实施例中，在第三接收单元接收主基站发送的上下文信息释放消息之前，所述第三接收单元还设置为：接收主基站发送的上下文信息请求消息，其中携带有源辅基站内相关的UE上下文索引信息；
空口非激活态维持装置包括：
该空口非激活态维持装置还包括第三发送单元和地址查找单元；所述地址查找单元设置为根据所述UE上下文索引信息，获取本地存储的所述UE上下文索引信息对应的UE在源辅基站侧上下文信息；所述第三发送单元设置为向主基站发送上下文信息响应消息，所述上下文信息响应消息携带源辅基站内存储的UE在源辅基站侧上下文信息。
基于与上述实施例相同或相似的构思，本公开实施例还提供一种空口非激活态维持装置，设置在基站上，尤其是作为目标辅基站侧的基站，本公开提出的一种空口非激活态维持装置包括：
第四接收单元，设置为接收主基站发送的辅基站通知消息；所述辅基站通知消息包含：UE在源辅基站侧上下文信息；
存储单元，设置为在目标辅基站本地存储接收的UE在源辅基站侧上下文信息，该空口非激活态维持装置还设置为完成对UE上下文信息在不同辅基站之间的迁移操作。
本公开实施例中，该空口非激活态维持装置还包括第四发送单元：所述第四发送单元设置为在所述接收主基站发送的辅基站通知消息之后，向主基站发送辅基站通知确认消息；所述辅基站通知确认消息包含：设置为承载锚定于辅基站侧PDU Session需要的辅基站侧下行传输地址信息。
基于与上述实施例相同或相似的构思，本公开实施例还提供一种基站，所述基站包括本公开实施例提供的设置在主基站侧上的空口非激活态维持装置、设置在源辅基站侧上的空口非激活态维持装置、和设置在目标辅基站侧上的空口非激活态维持装置中的至少一个。
基于与上述实施例相同或相似的构思，本公开实施例还提供一种电子设备，包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现本公开实施例提供的任一空口非激活态维持方法的处理。
基于与上述实施例相同或相似的构思，本公开实施例还提供一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现本公开实施例提供的任一空口非激活态维持方法的处理。
需要说明的是，以上所述的实施例仅是为了便于本领域的技术人员理解而已，并不用 于限制本公开的保护范围，在不脱离本公开的发明构思的前提下，本领域技术人员对本公开所做出的任何显而易见的替换和改进等均在本公开的保护范围之内。
工业实用性
本公开实施例提供的方案能够实现以下效果：处于双连接配置且进入非激活状态的UE，在发生辅基站变化的时候，MN能够及时知道UE从源辅基站移动到了目标辅基站的服务小区覆盖，或者仅离开源辅基站而并没有进入新的目标辅基站，源辅基站内保存的UE上下文信息，能够及时地被传递转移到目标辅基站或主基站内或者被删除，从而保证网络侧连接状态和相关的高层配置能和UE的最新移动状态保持对应一致，从而提供了一种有效的支持UE维持在RRC_INACTIVE非激活状态的解决方案。

Claims (27)

  1. 一种空口非激活态维持方法，其中，所述方法包括：
    接收UE发送的RRC上行通知消息；所述RRC上行通知消息携带有通知UE已离开源辅基站的服务小区覆盖的信息；
    基于所述RRC上行通知消息，执行UE锚定在源辅基站侧PDU Session的相关高层配置的迁移操作，迁移目标节点是目标辅基站或者当前主基站；
    在执行所述高层配置的迁移操作之后，向所述UE发送RRC下行回复消息，所述RRC下行回复消息携带有迁移操作完成指示信息；并且维持UE仍然处于双连接或单连接空口非激活态。
  2. 根据权利要求1所述的空口非激活态维持方法，其中，
    所述RRC上行通知消息为RRC Connection Resume Request RRC连接恢复请求消息；
    所述RRC下行回复消息为RRC Connection Resume Reject RRC连接恢复拒绝消息。
  3. 根据权利要求1所述的空口非激活态维持方法，其中，所述执行UE锚定在源辅基站侧PDU Session的相关高层配置的迁移操作包括：
    获取UE在源辅基站侧上下文信息；
    所述获取UE在源辅基站侧上下文信息包括：
    基于上下文索引信息，通过索引查找到主基站本地储存的UE在源辅基站侧上下文信息；
    或，
    向源辅基站发送上下文信息请求消息，其中携带有源辅基站内相关的UE上下文索引信息；主基站接收源辅基站回复的上下文信息响应消息，所述上下文信息响应消息携带源辅基站根据所述UE上下文索引信息，而找到的在源辅基站上存储的UE在源辅基站侧上下文信息。
  4. 根据权利要求3所述的空口非激活态维持方法，其中，
    所述RRC上行通知消息包含：源辅基站给UE分配的上下文索引信息、目标辅基站下新服务小区标识id、以及辅基站更新指示信息。
  5. 根据权利要求3所述的空口非激活态维持方法，其中，
    所述RRC上行通知消息包含：源辅基站给UE分配的上下文索引信息、以及辅基站释放指示信息。
  6. 根据权利要求4或5所述的空口非激活态维持方法，其中，所述RRC上行通知消息还包含：主基站给UE分配的P-I-RNTI或S-I-RNTI，UE RRM测量结果信息。
  7. 根据权利要求4所述的空口非激活态维持方法，其中，
    在所述获取UE在源辅基站侧上下文信息之后，所述执行UE锚定在源辅基站侧PDU Session的相关高层配置的迁移操作还包括：
    根据UE上报的所述目标辅基站下新服务小区标识id，向目标辅基站发送辅基站通知 消息；所述辅基站通知消息包含：UE在源辅基站侧的上下文信息。
  8. 根据权利要求7所述的空口非激活态维持方法，其中，在所述向目标辅基站发送辅基站通知消息之后，所述方法还包括：
    接收目标辅基站发送的辅基站通知确认消息；所述辅基站通知确认消息包含：用于承载锚定于辅基站侧的迁移后的PDU Session的基站下行传输地址信息。
  9. 根据权利要求5所述的空口非激活态维持方法，其中，所述执行UE锚定在源辅基站侧PDU Session的相关高层配置的迁移操作还包括：
    重新配置用于承载被迁移后的PDU Session的主基站下行传输地址信息。
  10. 根据权利要求8或9所述的空口非激活态维持方法，其中，
    所述执行UE锚定在源辅基站侧PDU Session的相关高层配置的迁移操作还包括：
    向AMF/SMF发送PDU Session资源修改指示消息，所述PDU Session资源修改指示消息携带有用于承载被迁移后的PDU Session的基站下行传输地址信息。
  11. 根据权利要求3所述的空口非激活态维持方法，其中，所述执行UE锚定在源辅基站侧PDU Session的相关高层配置的迁移操作还包括：
    向源辅基站发送的上下文信息释放消息，以使得所述源辅基站根据所述上下文信息释放消息释放掉本地保存的UE在源辅基站侧上下文信息。
  12. 根据权利要求4所述的空口非激活态维持方法，其中，所述RRC下行回复消息包含：UE在目标辅基站侧上下文信息对应的上下文索引信息、以及辅基站更新完成指示信息。
  13. 根据权利要求5所述的空口非激活态维持方法，其中，所述RRC下行回复消息包含：辅基站释放完成指示信息。
  14. 一种空口非激活态维持方法，其中，所述方法包括：
    在处于空口非激活态时，基于主基站和源辅基站的RRM测量配置信息，执行对主基站和源辅基站两侧的候选目标服务小区的RRM空口测量，以判定当前的移动环境；
    在通过所述空口RRM测量感知到源辅基站无线覆盖的更新事件时，向主基站发送的RRC上行通知消息；所述RRC上行通知消息携带有通知UE已离开源辅基站的服务小区覆盖的信息；
    接收主基站发送的RRC下行回复消息，所述RRC下行回复消息携带有迁移操作完成指示信息。
  15. 根据权利要求14所述的空口非激活态维持方法，其中，
    在所述更新事件为辅基站的无线覆盖更新到目标辅基站时，
    所述RRC上行通知消息包含：源辅基站给UE分配的S-I-RNTI、目标辅基站下新服务小区标识id、以及辅基站更新指示信息；
    所述RRC下行回复消息包含：New S-I-RNTI信息、以及、辅基站更新完成指示信息。
  16. 根据权利要求14所述的空口非激活态维持方法，其中，
    所述更新事件为辅基站的无线覆盖消失事件时，
    所述RRC上行通知消息包含：源辅基站给UE分配的S-I-RNTI、以及辅基站释放指示信息；
    所述RRC下行回复消息包含：辅基站释放完成指示信息。
  17. 根据权利要求15或16所述的空口非激活态维持方法，其中，所述RRC上行通知消息还包含：主基站给UE分配的P-I-RNTI或S-I-RNTI，UE RRM测量结果信息。
  18. 一种空口非激活态维持方法，其中，所述方法包括：
    接收主基站发送的上下文信息释放消息；
    基于接收的上下文信息释放消息，释放掉本地保存的UE在源辅基站侧上下文信息。
  19. 根据权利要求18所述的空口非激活态维持方法，其中，在所述接收主基站发送的上下文信息释放消息之前，所述方法还包括：
    接收主基站发送的上下文信息请求消息，其中携带有源辅基站内相关的UE上下文索引信息；
    根据所述UE上下文索引信息，获取本地存储的所述UE上下文索引信息对应的UE在源辅基站侧上下文信息；
    向主基站发送上下文信息响应消息，所述上下文信息响应消息携带源辅基站内存储的UE在源辅基站侧上下文信息。
  20. 一种空口非激活态维持方法，其中，所述方法包括：
    接收主基站发送的辅基站通知消息；所述辅基站通知消息包含：UE在源辅基站侧上下文信息；
    在目标辅基站本地存储接收的UE在源辅基站侧上下文信息，完成对UE上下文信息在不同辅基站之间的迁移操作。
  21. 根据权利要求20所述的空口非激活态维持方法，其中，在所述接收主基站发送的辅基站通知消息之后，所述方法还包括：
    向主基站发送辅基站通知确认消息；所述辅基站通知确认消息包含：用于承载锚定于辅基站侧PDU Session需要的辅基站侧下行传输地址信息。
  22. 一种空口非激活态维持装置，设置在基站上，其中，所述装置包括：
    第一接收单元，设置为接收UE发送的RRC上行通知消息；所述RRC上行通知消息携带有通知UE已离开源辅基站的服务小区覆盖的信息；
    迁移配置单元，设置为基于所述RRC上行通知消息，执行UE锚定在源辅基站侧PDU Session的相关高层配置的迁移操作，迁移目标节点是目标辅基站或者当前主基站；以及，维持UE仍然处于双连接或单连接空口非激活态
    第一发送单元，设置为在执行所述高层配置的迁移操作之后，向所述UE发送RRC下行回复消息，所述RRC下行回复消息携带有迁移操作完成指示信息。
  23. 一种空口非激活态维持装置，设置在用户设备UE上，其中，所述装置包括：
    测量单元，设置为在处于空口非激活态时，基于主基站和源辅基站的RRM测量配置信息，执行对主基站和源辅基站两侧的候选目标服务小区的RRM空口测量，以判定当前的移动环境；
    第二发送单元，设置为在通过所述空口RRM测量感知到源辅基站无线覆盖的更新事件时，向主基站发送的RRC上行通知消息；所述RRC上行通知消息携带有通知UE已离开源辅基站的服务小区覆盖的信息；
    第二接收单元，设置为接收主基站发送的RRC下行回复消息，所述RRC下行回复消息携带有迁移操作完成指示信息。
  24. 一种空口非激活态维持装置，设置在基站上，其中，所述装置包括：
    第三接收单元，设置为接收主基站发送的上下文信息释放消息；
    释放单元，设置为基于接收的上下文信息释放消息，释放掉本地保存的UE在源辅基站侧上下文信息。
  25. 一种空口非激活态维持装置，设置在基站上，其中，所述装置包括：
    第四接收单元，设置为接收主基站发送的辅基站通知消息；所述辅基站通知消息包含：UE在源辅基站侧上下文信息；
    存储单元，设置为在目标辅基站本地存储接收的UE在源辅基站侧上下文信息，完成对UE上下文信息在不同辅基站之间的迁移操作。
  26. 一种电子设备，包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，其中，所述处理器执行所述计算机程序时实现如权利要求1至21中任一权项所述的方法的处理。
  27. 一种计算机可读存储介质，其上存储有计算机程序，其中，所述计算机程序被处理器执行时实现如权利要求1至21中任一权项所述的方法的处理。
PCT/CN2019/084341 2018-05-09 2019-04-25 一种空口非激活态维持方法和装置 WO2019214450A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
KR1020207035164A KR102410198B1 (ko) 2018-05-09 2019-04-25 무선 인터페이스 비활성 상태 유지 방법 및 장치
MX2020011833A MX2020011833A (es) 2018-05-09 2019-04-25 Dispositivo y metodo de mantenimiento del estado inactivo de interfaz aerea.
US17/054,116 US11576101B2 (en) 2018-05-09 2019-04-25 Air interface inactive state maintaining method and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810438746.9 2018-05-09
CN201810438746.9A CN110475389B (zh) 2018-05-09 2018-05-09 一种空口非激活态维持方法和装置

Publications (1)

Publication Number Publication Date
WO2019214450A1 true WO2019214450A1 (zh) 2019-11-14

Family

ID=68467511

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/084341 WO2019214450A1 (zh) 2018-05-09 2019-04-25 一种空口非激活态维持方法和装置

Country Status (5)

Country Link
US (1) US11576101B2 (zh)
KR (1) KR102410198B1 (zh)
CN (1) CN110475389B (zh)
MX (1) MX2020011833A (zh)
WO (1) WO2019214450A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4014578A4 (en) * 2019-08-15 2023-05-10 Qualcomm Incorporated EARLY MEASUREMENT OF NEW RADIO (NR) AT MULTIPLE SECONDARY NODES (MULTI-SN)
CN115134050A (zh) * 2021-03-24 2022-09-30 展讯通信（上海）有限公司 高层标识的处理方法及相关装置
WO2024060151A1 (en) * 2022-09-22 2024-03-28 Apple Inc. Multi-cell group connectivity realization model for secondary cell group (scg) switch

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104469869A (zh) * 2013-09-23 2015-03-25 中兴通讯股份有限公司 一种小小区切换方法和基站
CN105228229A (zh) * 2014-06-27 2016-01-06 中兴通讯股份有限公司 用户设备ue资源处理方法、装置、基站及终端
WO2017204539A1 (ko) * 2016-05-24 2017-11-30 삼성전자 주식회사 이동통신 시스템에서 단말 및 기지국의 저전력 동작을 위한 방법 및 장치
CN107959983A (zh) * 2016-10-14 2018-04-24 诺基亚技术有限公司 利用上行链路信号快速激活多连接性的装置和方法

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100442782C (zh) * 2005-11-04 2008-12-10 华为技术有限公司 一种提高分组业务在线用户数目的方法
JP6185651B2 (ja) 2013-04-03 2017-08-23 インターデイジタル パテント ホールディングス インコーポレイテッド スモールセル配備のためのセル検出、識別および測定
WO2015142104A1 (en) * 2014-03-21 2015-09-24 Samsung Electronics Co., Ltd. Method and apparatus for transmitting/receiving signal in mobile communication system supporting a plurality of carriers
KR20150111798A (ko) * 2014-03-26 2015-10-06 삼성전자주식회사 반송파 결합을 지원하는 무선 통신 시스템에서 동기 획득 방법 및 장치
US9900817B2 (en) * 2014-03-27 2018-02-20 Telefonaktiebolaget Lm Ericsson (Publ) System and method for identifying a handover target cell during cell reconfiguration periods
CN110832917B (zh) * 2017-02-12 2021-11-12 鸿颖创新有限公司 无线电接入网络通报区域更新方法和用户设备
US10952176B2 (en) * 2017-03-17 2021-03-16 Samsung Electronics Co., Ltd. AF influenced PDU session management and subscription procedures
KR102472292B1 (ko) * 2018-01-10 2022-11-30 삼성전자 주식회사 무선 통신 시스템에서 경쟁 및 비경쟁 기반 빔 실패 복구를 수행하는 방법 및 장치

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104469869A (zh) * 2013-09-23 2015-03-25 中兴通讯股份有限公司 一种小小区切换方法和基站
CN105228229A (zh) * 2014-06-27 2016-01-06 中兴通讯股份有限公司 用户设备ue资源处理方法、装置、基站及终端
WO2017204539A1 (ko) * 2016-05-24 2017-11-30 삼성전자 주식회사 이동통신 시스템에서 단말 및 기지국의 저전력 동작을 위한 방법 및 장치
CN107959983A (zh) * 2016-10-14 2018-04-24 诺基亚技术有限公司 利用上行链路信号快速激活多连接性的装置和方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ZTE CORPORATION ET AL.: "CN Area Update in INACTIVE State", 3GPP TSG-RAN WG2 MEETING#101 R2-1802038, 15 February 2018 (2018-02-15), XP051399807 *

Also Published As

Publication number Publication date
US11576101B2 (en) 2023-02-07
MX2020011833A (es) 2021-05-27
KR20210005728A (ko) 2021-01-14
US20210120475A1 (en) 2021-04-22
CN110475389A (zh) 2019-11-19
CN110475389B (zh) 2022-10-14
KR102410198B1 (ko) 2022-06-22

Similar Documents

Publication Publication Date Title
EP3675579B1 (en) Data scheduling methods, apparatus and computer-readable mediums
WO2019237999A1 (zh) 传输链路管理、建立、迁移方法、装置、基站及存储介质
KR101749012B1 (ko) Ｌｔｅ 시스템에서 작은 데이터 전송을 위한 상시접속 베어러
WO2016123809A1 (zh) 一种信令优化方法和设备
US20220174773A1 (en) HANDLING QoS MOBILITY AND DUAL CONNECTIVITY IN NR
US8913588B2 (en) Handover method, communication device and communication system
WO2017054538A1 (zh) 建立辅助信令链路的方法及其装置、基站及终端
JP2017507581A (ja) ユーザ機器のハンドオーバにサービスを提供するための方法、基地局、および二重接続性システム
EP3114877B1 (en) Method for data forwarding in a small cell system
US20230379788A1 (en) Source secondary node (s-sn) initiated cancellation of conditional pscell change (cpc) in a multi-radio dual-connectivity (mr-dc) system
WO2018059299A1 (zh) 小区切换的方法、装置及***和计算机存储介质
WO2018137666A1 (zh) 一种数据传输方法、网络设备及终端设备
WO2016161759A1 (zh) 数据的传输方法及装置
CN113543251A (zh) 一种小小区***中不同MeNB间切换的方法及设备
TWI669018B (zh) 處理雙連結中交遞的裝置及方法
CN102007794A (zh) 通信***、网络切换处理方法和装置
WO2019214450A1 (zh) 一种空口非激活态维持方法和装置
TWI679915B (zh) 處理雙連結中次要節點改變的裝置及方法
WO2020253536A1 (zh) 双连接重建立中数据的处理方法及装置
EP3506675B1 (en) Method and apparatus for updating network side position area
EP4084573A1 (en) Network connection reestablishment method and device, storage medium, and electronic device
WO2020096564A1 (en) Method and system for supporting multiple fully separated network slices
US20230049140A1 (en) Managing a conditional configuration upon addition or release of a bearer
KR20100071795A (ko) 무선링크실패에 따른 무선접속 복구방법
CN114079912B (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: 19799289

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20207035164

Country of ref document: KR

Kind code of ref document: A

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 13.04.2021)

122 Ep: pct application non-entry in european phase

Ref document number: 19799289

Country of ref document: EP

Kind code of ref document: A1