WO2019056279A1 - 连接管理方法、用户设备、核心网实体及*** - Google Patents

连接管理方法、用户设备、核心网实体及*** Download PDF

Info

Publication number
WO2019056279A1
WO2019056279A1 PCT/CN2017/102808 CN2017102808W WO2019056279A1 WO 2019056279 A1 WO2019056279 A1 WO 2019056279A1 CN 2017102808 W CN2017102808 W CN 2017102808W WO 2019056279 A1 WO2019056279 A1 WO 2019056279A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
core network
network entity
request message
inactive state
Prior art date
Application number
PCT/CN2017/102808
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 US16/649,377 priority Critical patent/US11291069B2/en
Priority to PCT/CN2017/102808 priority patent/WO2019056279A1/zh
Priority to CN201780088304.XA priority patent/CN110431913B/zh
Priority to EP17925692.0A priority patent/EP3678449B1/en
Publication of WO2019056279A1 publication Critical patent/WO2019056279A1/zh

Links

Images

Classifications

    • 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
    • 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/30—Connection release
    • H04W76/34—Selective release of ongoing connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast

Definitions

  • the present application relates to the field of wireless communications technologies, and in particular, to a connection management method, a user equipment, a core network entity, and a system.
  • the radio resource control (Radio Resource Control, RRC) is inactive (state), which means that the user equipment (User Equipment, abbreviation: UE) is in an idle (IDLE) state with the base station, and the base station and the core network. The connection is connected.
  • the radio access network Radio Access Network, RAN
  • RAN Radio Access Network
  • 5G fifth generation mobile communication technology
  • some 4G base stations accessing the 5G core network do not support the RRC Inactive state. If the UE enters a base station cell that does not support the RRC Inactive state, that is, the UE in the RRC Inactive state moves out of the radio access network notification area RNA (RAN notification Area) covered by the camping base station supporting the RRC Inactive state, moves and camps When a base station that does not support the RRC Inactive state is reached, the UE cannot communicate with the base station that does not support the RRC Inactive state. The UE in the RRC Inactive state can only send an RRC resume request if it wants to communicate with the network. However, the RAN that does not support the RRC Inactive state cannot recognize the request, and the UE cannot communicate with the current base station.
  • RNA radio access network notification Area
  • the embodiments of the present invention provide a connection management method, a user equipment, a core network entity, and a system, which can implement communication between a UE in an RRC Inactive state and a base station that does not support an RRC Inactive state.
  • the embodiment of the present invention provides a connection management method, including: a user equipment UE accessing a network through a first base station, the UE is in a radio resource connection inactive state (RRC Inactive state); and the UE accesses through the second base station.
  • the network the second base station does not support the RRC Inactive state, and the UE can send the first request message to the first core network entity by using the second base station.
  • the first core network entity is connected to the first base station, and the first core network entity receives the first request message sent by the UE through the second base station, and can release the connection with the first base station according to the first request message.
  • the UE may send the first request message to the first core network entity by using the second base station, and further, the first core network entity may send the second request message to the second core network entity, so that the second core network entity Receiving a second request message sent by the first core network entity, and releasing a connection with the first base station according to the second request message.
  • the first base station may be a base station corresponding to a network that is accessed before the UE moves, such as a radio access network (RA), that is, a base station that is connected before the UE moves.
  • the second base station may be a base station that is accessed after the UE moves, such as a base station corresponding to the RAN, that is, a base station that is connected after the UE moves, and the second base station does not support the RRC Inactive state.
  • the first base station may be a 5G base station
  • the second base station may be a 4G base station that does not support the RRC Inactive state, or may be a 5G base station that does not support the RRC Inactive state, and the like, which are not enumerated here.
  • the UE supports the RRC Inactive state, and the UE may be in the RRC Inactive state when communicating with the first base station. Therefore, the UE in the RRC Inactive state and the base not supporting the RRC Inactive state can be implemented. Communication between stations.
  • the UE may receive the broadcast message sent by the second base station, and determine, according to the broadcast message, whether the second base station supports the RRC Inactive state, and further determine that the second base station does not support the RRC Inactive state.
  • a request message is sent to the first core network entity.
  • the first core network entity may be a core network entity in a network accessed by the second base station
  • the second core network entity may be a core network entity in the network accessed by the first base station.
  • the core network entity may be an Access and Mobility Management Function (AMF), a Mobility Management Entity (MME), or a 3G core network entity such as a serving general packet radio service.
  • AMF Access and Mobility Management Function
  • MME Mobility Management Entity
  • 3G core network entity such as a serving general packet radio service.
  • GPRS General Packet Radio Service
  • SGSN Serving GPRS Support Node
  • SGSN Serving GPRS Support Node
  • the first base station is a 5G base station
  • the second base station can be a 4G base station
  • the first core network entity can be an MME
  • the second core network entity can be an AMF
  • the first base station and the second base station are both In the 4G base station
  • the first core network entity and the second core network entity may both be AMFs, and the two may be the same AMF or different AMFs.
  • the UE may switch the state of the UE from the RRC Inactive state to the idle state IDLE state.
  • the first request message may include indication information indicating that the UE is switched from the RRC Inactive state to the idle state IDLE state.
  • the first request message and/or the second request message may also be used to indicate that the core network entity performs a protocol data unit (abbreviation: PDU) session deactivation process (PDU session deactivation). Procedure). Further, after receiving the first request message, the first core network entity may further perform a PDU session deactivation procedure, including releasing a connection with a Session Management Function (SMF) and the like. Alternatively, after the second core network entity receives the second request message sent by the first core network entity, the second core network entity may further perform a PDU session deactivation procedure.
  • PDU protocol data unit
  • Procedure protocol data unit
  • the first core network entity may further perform a PDU session deactivation procedure, including releasing a connection with a Session Management Function (SMF) and the like.
  • SMF Session Management Function
  • the second core network entity may further perform a PDU session deactivation procedure.
  • the first request message may be a location update request, such as a Tracking Area Update (TAU) Request, an attach request, such as an Attach Request, a registration request, such as a Registration Request, or a service request, such as a Service Request.
  • a location update request such as a Tracking Area Update (TAU) Request
  • an attach request such as an Attach Request
  • a registration request such as a Registration Request
  • a service request such as a Service Request.
  • RRC resume request instead of an RRC resume request.
  • the second request message may be a message between core networks, such as a context request context request, a context switch context transfer message, and the like.
  • the first request message may further include UE capability information indicating that the UE supports the RRC Inactive state. That is, the first request message may also carry capability information of the UE supporting the RRC Inactive state.
  • the first base station supports the RRC Inactive state, that is, the first base station may be a base station supporting the RRC Inactive state.
  • the embodiment of the present invention further provides a user equipment, which has a function of implementing the behavior of the user equipment UE in the foregoing method example.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more units or modules corresponding to the functions described above.
  • a communication unit and a processing unit may be included in the structure of the user equipment, the processing unit being configured to support the user equipment to perform corresponding functions in the above methods.
  • the communication unit is configured to support a user equipment and Communication between his devices.
  • the user equipment may further comprise a storage unit for coupling with the processing unit, which stores program instructions (operation instructions) and data necessary for the user equipment.
  • the processing unit can be a processor
  • the communication unit can be a transceiver
  • the storage unit can be a memory.
  • an embodiment of the present invention provides a core network entity, where the core network entity has a function of implementing a behavior of a core network entity, such as a first core network entity or a second core network entity, in the foregoing method example.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more units or modules corresponding to the functions described above.
  • the structure of the core network entity includes a communication unit and a processing unit, the processing unit being configured to support the core network entity to perform the corresponding functions in the above methods.
  • the communication unit is configured to support communication between a core network entity and other devices.
  • the core network entity may also include a storage unit for coupling with the processing unit, which stores program instructions (operation instructions) and data necessary for the core network entity.
  • the processing unit can be a processor
  • the communication unit can be a transceiver
  • the storage unit can be a memory.
  • an embodiment of the present invention provides a communication system, including the user equipment and/or a core network entity of the foregoing aspect, such as a first core network entity or a second core network entity.
  • the system may further include other devices, such as a first base station, a second base station, an SMF, and the like, that interact with the user equipment or the core network entity in the solution provided by the embodiment of the present invention.
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions for use by the user equipment, including a program designed to perform the above aspects.
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions used by the core network entity, such as a first core network entity or a second core network entity, for performing the foregoing aspects. Designed program.
  • embodiments of the present invention provide a computer program comprising instructions that, when run on a computer, cause the computer to perform the methods described in the various aspects above.
  • the present application also provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the methods described in the various aspects above.
  • the present application provides a chip system including a processor for supporting a user device to implement the functions involved in the above aspects, such as, for example, generating or processing data and/or processing in the above methods. information.
  • the chip system further includes a memory for storing program instructions and data necessary for the user equipment.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • the present application provides a chip system including a processor for supporting a core network entity such as a first core network entity or a second core network entity to implement the functions involved in the above aspects, for example, for example Receiving or processing data and/or information involved in the above methods.
  • the chip system further includes a memory for storing necessary program instructions and data of the core network entity.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • the UE may access the network through the first base station, and the UE may be in the RRC Inactive state. Further, the UE may also access the network by using the second base station, for example, the UE moves from the cell where the first base station is located to the cell where the second base station is located, and the UE may notify the core network entity after determining that the second base station does not support the RRC Inactive state. Sending a request message, so that the core network entity can release the first message after receiving the request message A connection between the base stations, thereby enabling communication between the UE in the RRC Inactive state and the base station not supporting the RRC Inactive state.
  • FIG. 1 is an application scenario diagram of a communication system according to an embodiment of the present invention
  • connection management method is a schematic diagram of interaction of a connection management method according to an embodiment of the present invention
  • connection management method 3 is a schematic diagram of interaction of another connection management method according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of interaction of still another connection management method according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of interaction of still another connection management method according to an embodiment of the present invention.
  • connection management system is a schematic structural diagram of a connection management system according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a user equipment according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of another user equipment according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of still another user equipment according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of a core network entity according to an embodiment of the present invention.
  • FIG. 11 is a schematic structural diagram of another core network entity according to an embodiment of the present invention.
  • FIG. 12 is a schematic structural diagram of still another core network entity according to an embodiment of the present invention.
  • GSM Global System for Mobile Communications
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • TD-SCDMA Time Division-Synchronous Code Division Multiple Access
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • the core network entity involved in this application may be an MME, an AMF, or an SGSN, etc., which is not limited in this application.
  • a user equipment is a device having a communication function, which may also be referred to as a terminal, which may include a handheld device having a wireless communication function, an in-vehicle device, a wearable device, a computing device, or other processing connected to a wireless modem.
  • Equipment, etc. User equipment can be called different names in different networks, such as: terminal, UE, mobile station, subscriber unit, station, cellular phone, personal digital assistant, wireless modem, wireless communication device, handheld device, laptop, cordless Telephone, wireless local loop station, etc.
  • the user equipment can be a wireless terminal or a wired terminal.
  • the wireless terminal can be a device that provides voice and/or data connectivity to the user, a handheld device with wireless connectivity, or other processing device connected to the wireless modem, which can be accessed via a wireless access network (eg, RAN, radio access) Network) communicates with one or more core networks.
  • a wireless access network eg, RAN, radio access
  • a base station may also be referred to as a base station device, and is deployed in a wireless access network to provide wireless communication work.
  • the name of the base station may be different in different wireless access systems.
  • a base station is called a Node B (NodeB)
  • a base station in an LTE network is called an evolved Node B (evolved NodeB).
  • eNB or eNodeB in the future 5G system, it can be called a Transmission Reception Point (TRP) network node or a g-NodeB (gNB), etc., which are not enumerated here.
  • TRP Transmission Reception Point
  • gNB g-NodeB
  • FIG. 1 is a structural diagram of a communication system according to an embodiment of the present invention.
  • the communication system may include a UE, a first base station, a second base station, and a first core network entity.
  • the system also optionally includes a second core network entity.
  • the UE is a UE that supports the RRC Inactive state, and the UE may be in the RRC Inactive state when communicating with the first base station.
  • the first base station may be a base station that is accessed by the UE before the mobile station moves, such as a base station corresponding to the RAN
  • the second base station may be a network that is accessed by the UE after the mobile station moves, such as a base station corresponding to the RAN
  • the first base station may support the RRC Inactive state.
  • the RRC Inactive state may not be supported, and the second base station does not support the RRC Inactive state.
  • the first core network entity may be a core network entity in a network accessed by the second base station
  • the second core network entity may be a core network entity in a network accessed by the first base station.
  • the core network entity corresponding to the first base station, that is, the second core network entity, and the core network entity corresponding to the second base station, that is, the first core network entity may be the same or different.
  • the communication system may further include an SMF, a user port function entity (English: User Port Function, abbreviated: UPF) (not shown), and the like.
  • the RRC resume request sent by the UE in the RRC Inactive state cannot be identified by the RAN (base station, such as the second base station described above) that does not support the RRC Inactive state, so that the UE in the RRC Inactive state cannot and the RAN that does not support the RRC Inactive state.
  • the present application can send a request message, such as a service request or a registration request, to the RAN that does not support the RRC Inactive state, to indicate that the core network entity, such as the first core network entity or the second core network entity, is released and the first The connection between the base stations, thereby implementing communication between the UE in the RRC Inactive state and the RAN not supporting the RRC Inactive state.
  • the present application discloses a connection management method, a user equipment, a core network entity, and a system, which facilitates communication between a UE in an RRC Inactive state and a RAN that does not support an RRC Inactive state. The details are explained below.
  • FIG. 2 is a schematic diagram of interaction of a connection management method according to an embodiment of the present invention.
  • the connection management method in the embodiment of the present invention may include the following steps:
  • the UE accesses the network by using the first base station.
  • the UE accesses the network by using the second base station, and the second base station does not support the RRC Inactive state.
  • the UE may establish a connection with the first base station and the second base station, respectively.
  • the first base station may be a base station corresponding to the RAN that is accessed before the UE moves
  • the second base station may be a base station corresponding to the RAN that is accessed after the UE moves
  • the UE is a UE that supports the RRC Inactive state, such as the UE. It can be in the RRC Inactive state when communicating with the first base station.
  • the UE sends a first request message to the first core network entity by using the second base station.
  • the second base station may notify the UE whether the second base station supports the RRC Inactive state by sending a broadcast message to the UE. Therefore, the UE may determine, according to the broadcast message, whether the second base station supports the RRC Inactive state, and may further send a request message to the core network entity, such as the MME or the AMF, when determining that the second base station does not support the RRC Inactive state, so that the core network entity A connection with the first base station is released according to the request message.
  • the core network entity such as the MME or the AMF
  • the UE may send the first request message to the first core network entity by using the second base station, where The first request message triggers the first core network entity to release the connection between the first core network entity and the first base station, that is, steps 203-204 are performed.
  • the UE may send a first request message to the first core network entity by using the second base station, and send, by the first core network device, a second request message to the second core network device, where the second request message triggers the release of the second core network entity.
  • the connection between the second core network entity and the first base station, that is, steps 203, 205-206 are performed.
  • the broadcast message may include information indicating whether the second base station supports the RRC Inactive state.
  • the broadcast message may include “0” or “1”, indicating that the RRC Inactive state is not supported by “0”, and supporting the RRC Inactive state by “1”.
  • the broadcast message may directly carry the capability information of the RRC Inactive state or the RRC Inactive state, or may be indicated by other means, which is not limited in this application.
  • the broadcast message may also carry the capability information of the RRC Inactive state of the second base station when the second base station supports the RRC Inactive state, and does not carry the second base station when the second base station does not support the RRC Inactive state.
  • the UE can determine whether the second base station supports the RRC Inactive state according to whether the broadcast message carries the capability information supporting the RRC Inactive state, after receiving the broadcast message sent by the second base station. Specifically, when detecting that the broadcast message carries capability information that supports the RRC Inactive state, determining that the second base station supports the RRC Inactive state, and determining that the broadcast message does not carry the capability information supporting the RRC Inactive state, determining the second base station RRC Inactive state is not supported.
  • the first request message may be used to indicate that the first core network entity releases the connection with the first base station, so that the first core network entity can timely receive the first request message.
  • the connection with the first base station is released.
  • the second request message may be used to indicate that the second core network entity releases the connection with the first base station, so that the second core network entity can release the first base station in time when receiving the second request message. connection.
  • the first request message may be a location update request, such as a TAU Request, an attach request, such as an Attach Request, a registration request, such as a Registration Request, or a service request, such as a Service Request.
  • a location update request such as a TAU Request
  • an attach request such as an Attach Request
  • a registration request such as a Registration Request
  • a service request such as a Service Request.
  • the first core network entity releases the connection with the first base station according to the first request message.
  • the first core network entity sends a second request message to the second core network entity.
  • the second core network entity releases the connection with the first base station according to the second request message.
  • the UE may switch the state of the UE from the RRC Inactive state to the IDLE state, that is, perform state switching.
  • the RRC layer may notify the non-access stratum (NAS) layer and set the IDLE state from the RRC Inactive state.
  • NAS non-access stratum
  • the UE is in the RRC Inactive state
  • the first request message is a location update request, an attach request, a registration request, or a service request triggered by the broadcast message. That is, after the UE receives the broadcast message and determines that the second base station does not support the RRC Inactive state, the UE can still maintain the RRC Inactive state, but can trigger the execution of the first request message in the IDLE state according to the broadcast message. Instead of sending an RRC resume request in the RRC Inactive state, the location update request, the attach request, the registration request, or the service request can be ensured, thereby ensuring that the network side recognizes the first request message, thereby releasing the connection with the first base station. .
  • the first request message may include indication information, where the indication information may indicate that the UE is switched from the RRC Inactive state to an idle state IDLE state. Therefore, the core network entity may determine to release the connection with the first base station when receiving the first request message including the indication information.
  • the first request message and/or the second request message may also be used to indicate that the core network entity performs a PDU session deactivation procedure.
  • the first core network entity may further perform a PDU session deactivation procedure, for example, the first core network entity may release the connection with the SMF.
  • the second core network entity may further perform a PDU session deactivation procedure.
  • the second core network entity such as the AMF performs a PDU session deactivation procedure, and the AMF may send a session management context update request, such as Nsmf_PDUSession_UpdateSMContext, to the SMF, so that the SMF may initiate a PDU session deactivation procedure or the like to complete the release of the N3 connection.
  • a session management context update request such as Nsmf_PDUSession_UpdateSMContext
  • the first request message may further include UE capability information, where the UE capability information may indicate that the UE supports the RRC Inactive state. That is, the first request message may further carry capability information of the UE supporting the RRC Inactive state.
  • the first base station can support the RRC Inactive state. That is, the present application is also applicable to the UE moving from the RAN supporting the RRC Inactive state (that is, the network where the first base station supporting the RRC Inactive state is located) to the RAN not supporting the RRC Inactive state (that is, the second base station not supporting the RRC Inactive state). The scene of the network).
  • the released connection may include an N2 and/or N3 connection between the core network entity and the first base station, and the like.
  • releasing the connection with the first base station by the core network entity may include: deleting the UE context in the first base station, and releasing the N2 of the RAN of the core network entity and the first base station.
  • the connection releases the context of the first base station in the UPF, releases the N3 connection of the UPF with the first base station, deactivates one or more of the PDU session, and the like.
  • the UE may send a request message to the core network entity, such as the AMF, to trigger the release of the connection with the first base station, and the AMF sends a session management context update request, such as Nsmf_PDUSession_UpdateSMContext, to the SMF, so that the SMF may initiate a PDU session deactivation procedure, etc., to complete. Release of the N3 connection.
  • the core network entity such as the AMF, may also send an N2UE Context Release Command to the first base station.
  • the core network entity may also send a location update receiving response to the UE. Further optionally, the core network entity may also send an N2Request to the second base station, where the N2Request may carry information such as Service Accept. Further optionally, the second base station may also send a Service Accept to the UE in the RRC connection reconfiguration request.
  • the UE may send a first request message to the first core network entity, and send, by the first core network entity, a second request message, such as a context request or a context transfer message, to the second core network entity, so that the second core network entity triggers. Release its connection with the first base station and perform a PDU session deactivation procedure and the like.
  • the second core network entity such as the AMF may trigger release of its N2 connection with the first base station, and the AMF sends a session management context update request, such as Nsmf_PDUSession_UpdateSMContext, to the SMF, and the deactivated PDU session is initiated by the SMF.
  • the PDU session deactivation procedure is implemented to complete the release of the N3 connection.
  • the second core network entity may further send an N2UE Context Release Command to the first base station.
  • the first core network entity may also send a location update receiving response to the UE.
  • the first core network entity may also send an N2Request to the second base station, where the N2Request may carry information such as Service Accept.
  • the second base station may also send a Service Accept to the UE in the RRC connection reconfiguration request.
  • the order of the information of the sending location update receiving response, releasing the connection with the first base station, performing the PDU session deactivation procedure, and transmitting the N2UE Context Release Command is not limited, and may be performed simultaneously or at different times. Not limited.
  • the UE may access the network through the first base station, and the UE may be in the RRC Inactive state. Further, the UE may also access the network by using the second base station, for example, the UE moves from the cell where the first base station is located to the cell where the second base station is located, and the UE may notify the core network entity after determining that the second base station does not support the RRC Inactive state. Sending a request message, so that the core network entity can release the connection with the first base station after receiving the request message, thereby implementing communication between the UE in the RRC Inactive state and the base station not supporting the RRC Inactive state .
  • FIG. 3 is a schematic diagram of interaction of another connection management method according to an embodiment of the present invention.
  • the connection management method in the embodiment of the present invention may include the following steps:
  • the UE accesses the network by using the first base station, and the UE is in an RRC Inactive state.
  • the UE accesses the network by using the second base station.
  • the UE may be in an RRC Inactive state.
  • the first base station may be a base station supporting the RRC Inactive state.
  • the second base station sends a broadcast message to the UE.
  • the UE may need to switch from the RAN where the first base station is located to the RAN where the second base station is located.
  • the first base station is the base station corresponding to the RAN before the UE moves
  • the second The base station is the base station corresponding to the RAN after the UE has moved.
  • the broadcast message can be used to indicate whether the second base station supports the RRC Inactive state. In the embodiment of the present invention, it is assumed that the broadcast message indicates that the second base station does not support the RRC Inactive state.
  • the UE determines, according to the broadcast message, that the second base station does not support the RRC Inactive state, and switches the state of the UE from the RRC Inactive state to the IDLE state.
  • the UE sends a request message to the AMF, where the request message carries indication information, where the indication information indicates that the UE is switched to the IDLE state by the RRC Inactive state.
  • the UE may receive the broadcast message from the second base station, if it is determined that the second base station does not support the RRC Inactive state according to the broadcast message, for example, the broadcast message does not carry the capability information of the second base station supporting the RRC Inactive state.
  • the UE may switch the state of the UE from the RRC Inactive state to the IDLE state, and further send a request message (ie, a first request message) to the core network entity (ie, the first core network entity), such as a location update request, and attach. Requests, registration requests or business requests, etc.
  • the UE may send the request message to the second base station, and the second base station forwards the request message to the AMF.
  • the UE may send a location update based registration request, such as a Registration Request, to the second base station, through the second base station. Send the Registration Request to AMF.
  • the request message such as the registration request, may include an indication information, where the indication information is used to indicate that the UE is switched to the IDLE state by the RRC Inactive state, that is, the indication indication of the inactive->idle is carried in the request message.
  • the request message may further include UE capability information, where the UE capability information may be used to indicate that the UE supports the RRC Inactive state. That is, the request message may further carry the capability information of the UE supporting the RRC Inactive state, for example, the UE capability information may be carried in the UE Network Capability in the request message.
  • the AMF releases the connection with the first base station.
  • the AMF can release the connection with the first base station.
  • the AMF performs a PDU session deactivation procedure.
  • the request message is further used to indicate that the AMF performs a PDU session deactivation procedure. Therefore, when receiving the request message, the AMF can also perform a PDU session deactivation procedure, including releasing the connection between the AMF and the SMF. Further, the SMF can also release the connection to the UPF.
  • the embodiment of the present invention may be applied to a scenario where a UE moves from a cell of a 5G base station (first base station) supporting the RRC Inactive state to a 5G base station (second base station) cell that does not support the RRC Inactive state.
  • the AMFs corresponding to the first base station and the second base station may be the same or different, and the same or different manners of message transmission and connection release may be referred to the related description of the embodiment shown in FIG. 2, and details are not described herein. .
  • the UE may receive the broadcast message sent by the second base station, and determine, according to the broadcast message, that the second base station does not support the RRC Inactive state, and then switch the state of the UE from the RRC Inactive state to the IDLE state. And sending a request message to the AMF to indicate that the AMF releases the connection with the first base station accessed before the mobile, so that the AMF can release the connection with the first base station and other related connections after receiving the request message. Thereby, communication between the UE in the RRC Inactive state and the base station not supporting the RRC Inactive state is achieved.
  • FIG. 4 is a schematic diagram of interaction of another connection management method according to an embodiment of the present invention.
  • the connection management method in the embodiment of the present invention may include the following steps:
  • the UE accesses the network by using the first base station, and the UE is in an RRC Inactive state.
  • the UE accesses the network by using the second base station.
  • the first base station may be a base station supporting the RRC Inactive state.
  • the second base station sends a broadcast message to the UE.
  • steps 401-403 can refer to the description of steps 301-303 in the foregoing embodiment shown in FIG. 3, and details are not described herein.
  • the UE sends a request message to the AMF when the second base station does not support the RRC Inactive state according to the broadcast message.
  • the UE may receive the broadcast message from the second base station, and may determine, according to the broadcast message, that the second base station does not support the RRC Inactive state, for example, the broadcast message does not carry the second base station to support the RRC Inactive state.
  • the broadcast message triggers sending a request to the core network entity (ie, the first core network entity), such as the AMF.
  • Information ie, the first request message
  • the UE may send the request message to the second base station, and the second base station forwards the request message to the AMF.
  • the UE may send a location update based registration request, such as a Registration Request, to the second base station, and send the Registration Request to the AMF through the second base station.
  • the request message such as the Registration Request
  • the request message may further include UE capability information, where the UE capability information may be used to indicate that the UE supports the RRC Inactive state, that is, the request message may further carry the capability information of the UE supporting the RRC Inactive state.
  • the UE capability information may be carried in the UE Network Capability in the request message.
  • the AMF releases the connection with the first base station.
  • the AMF can release the connection with the first base station.
  • the AMF performs a PDU session deactivation procedure.
  • the request message is further used to indicate that the AMF performs a PDU session deactivation procedure.
  • the AMF can also perform a PDU session deactivation procedure, including releasing the connection with the SMF. Further, the SMF can also release the connection to the UPF.
  • the AMFs corresponding to the first base station and the second base station may be the same or different, and the same or different manners of message transmission and connection release may be referred to the related description of the embodiment shown in FIG. 2, and details are not described herein. .
  • the UE may also switch the state of the UE from the RRC Inactive state to the IDLE state to facilitate communication with the second base station that does not support the RRC Inactive state.
  • the UE in the RRC Inactive state may receive the broadcast message sent by the second base station, and determine, according to the broadcast message, that the second base station does not support the RRC Inactive state, and trigger the broadcast message to send to the AMF. Requesting a message, such as a registration request or a service request, etc., so that after receiving the request message, the AMF can release the connection with the first base station and other related connections according to the request message, thereby implementing the UE in the RRC Inactive state. Communication with a RAN that does not support RRC Inactive state.
  • FIG. 5 is a schematic diagram of interaction of another connection management method according to an embodiment of the present invention.
  • the connection management method in the embodiment of the present invention may include the following steps:
  • the UE accesses the network by using the first base station, and the UE is in an RRC Inactive state.
  • the UE accesses the network by using the second base station.
  • the second base station sends a broadcast message to the UE.
  • steps 501-503 can refer to the description of steps 301-303 in the foregoing embodiment shown in FIG. 3, and details are not described herein.
  • the UE sends, according to the broadcast message, that the second base station does not support the RRC inactive state, and sends a first request message to the MME.
  • the MME sends a second request message to the AMF.
  • the AMF releases a connection with the first base station.
  • the AMF performs a PDU session deactivation procedure.
  • the embodiment of the present invention is applicable to a scenario in which the UE moves from a cell that supports the RRC Inactive state, that is, the cell of the first base station, to a cell that does not support the RRC Inactive state, that is, the cell of the second base station.
  • the UE may receive the broadcast message from the second base station, and may, when determining that the second base station does not support the RRC Inactive state according to the broadcast message, to the 4G core network entity MME (the first core network entity) through the second base station.
  • the request message (ie, the first request message) is sent, such as a location update request, an attach request, a registration request, or a service request.
  • the UE may send a location update request, such as a TAU request or an attach request, to the MME through the second base station.
  • a location update request such as a TAU request or an attach request
  • the MME may also send a second request message, such as a context request, to the AMF (second core network entity), and then the AMF may trigger the release of the AMF when receiving the context request.
  • AMF second core network entity
  • the UE may send a first request message to the AMF (new AMF, corresponding to the first core network entity) corresponding to the second base station, and the new AMF (AMF) corresponding to the first base station
  • AMF new AMF
  • the second core network entity sends a second request message, such as a context transfer message, so that the old AMF can release the connection with the first base station, and the like, and the process is similar to the connection release process of the foregoing scenario, and details are not described herein.
  • FIG. 6 is a schematic structural diagram of a connection management system according to an embodiment of the present invention.
  • the connection management system of the embodiment of the present invention includes a UE1, a first base station 2, a second base station 3, a first core network entity 4, and a second core network entity 5. among them,
  • the UE1 is configured to access the network by using the first base station 2, the UE1 is in a radio resource connection inactive state RRC Inactive state; the second base station 3 accesses the network, and the second base station 3 does not support the RRC Inactive Sending a first request message to the first core network entity 4 through the second base station 3.
  • the first core network entity 4 is configured to be connected to the first base station 2; receive the first request message sent by the UE1 through the second base station 3, and the second base station 3 does not support the RRC Inactive state; release and The connection between the first base stations 2.
  • the second core network entity 5 is configured to be connected to the first base station 2, and receive a second request message sent by the second core network entity 4, where the second request message is that the first core network entity 4 receives the UE
  • the second base station 3 does not support the RRC Inactive state; and the first base station 2 is released. the connection between.
  • the first base station 2 may be a base station corresponding to a network accessed by the UE before the mobile station moves
  • the second base station 3 may be a base station corresponding to the network accessed by the UE after the mobile station moves.
  • the first base station, the second base station, the first core network entity, and the second core network entity in the embodiment of the present invention reference may be made to the related description of the embodiment shown in FIG. 2 to FIG. 5, and details are not described herein.
  • FIG. 7 is a schematic diagram showing a possible structure of the user equipment involved in the foregoing embodiment.
  • the user equipment 700 can include a communication unit 701 and a processing unit 702.
  • the unit may perform the corresponding function of the UE in the foregoing method example, for example, the communication unit 701 is configured to access the network by using the first base station, where the user equipment UE is in a radio resource connection inactive state RRC Inactive state;
  • the unit 701 is further configured to access the network by using the second base station, where the second base station does not support the RRC Inactive state;
  • the communication unit 701 is further configured to send, by using the second base station, the first core network entity a request message, to enable the first core network entity to release a connection with the first base station according to the first request message, or to enable the first core network entity to send a second to a second core network entity Requesting a message, and releasing, by the second core network entity, the connection with the first base station according to the second request message.
  • the communication unit 701 is further configured to receive the broadcast message sent by the second base station, and the processing unit 702 is configured to determine, according to the broadcast message, whether the second base station supports the RRC Inactive state. Further, the communication unit 701 may send a request message to the core network entity through the second base station when the processing unit 702 determines that the second base station does not support the RRC Inactive state.
  • the first base station is a base station corresponding to the network accessed by the UE before the mobile station moves
  • the second base station is a base station corresponding to the network accessed by the UE after the mobile station moves.
  • the first core network entity may be a core network entity of a network accessed by the second base station
  • the second core network entity may be a core network entity of the network accessed by the first base station
  • the processing unit 701 is further configured to switch the state of the UE from the RRC Inactive state to an idle state IDLE state.
  • the first request message may include indication information, where the indication information may indicate that the UE is switched from the RRC Inactive state to an idle state IDLE state.
  • the first request message may be a location update request, an attach request, a registration request, or a service request.
  • the first request message further includes UE capability information, where the UE capability information indicates that the UE supports the RRC Inactive state.
  • the first base station supports the RRC Inactive state.
  • the first core network entity may be an MME or an AMF or an SGSN
  • the second core network entity may be an AMF
  • each functional unit in the 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.
  • FIG. 8 shows another possible structural diagram of the user equipment involved in the above embodiment.
  • the user equipment 800 may include: a processing unit 802 and a communication. Unit 803.
  • Processing unit 802 can be used to control management of actions of user equipment, for example, processing unit 802 for supporting user equipment to perform process 304 and the like in FIG. 3, and/or other processes for the techniques described herein.
  • Communication unit 803 is used to support communication of user equipment with other network entities, such as with the functional units or network entities illustrated in Figures 2-5.
  • the user equipment may further include a storage unit 801 for storing program codes (operation instructions) and data of the user equipment.
  • the processing unit 802 can be a processor or a controller, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and a dedicated integrated circuit.
  • ASIC Application-Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication unit 803 can be a transceiver.
  • the storage unit 801 can be a memory.
  • the processing unit 802 is a processor
  • the communication unit 803 is a transceiver
  • the storage unit 801 is a memory
  • the user equipment involved in the embodiment of the present invention may be the user equipment shown in FIG.
  • the user equipment 900 can include a processor 902, a transceiver 903, a memory 901, and a bus 904.
  • the transceiver 903, the processor 902, and the memory 901 are connected to each other through a bus 904.
  • the bus 904 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA). ) Bus, etc.
  • PCI peripheral component interconnect
  • EISA extended industry standard architecture
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 9, but it does not mean that there is only one bus or one type of bus.
  • the steps of a method or algorithm described in connection with the present disclosure may be implemented in a hardware or may be implemented by a processor executing software instructions.
  • the software instructions may be composed of corresponding software modules or units, which may be stored in a random access memory (RAM), flash memory, read only memory (ROM), erasable and programmable. Erasable Programmable ROM (EPROM), electrically erasable programmable read only memory (EEPROM), registers, hard disk, removable hard disk, compact disk read only (CD-ROM) or any other form known in the art.
  • RAM random access memory
  • ROM read only memory
  • EPROM Erasable Programmable ROM
  • EEPROM electrically erasable programmable read only memory
  • registers hard disk, removable hard disk, compact disk read only (CD-ROM) or any other form known in the art.
  • CD-ROM compact disk read only
  • An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium.
  • the storage medium can
  • FIG. 10 is a schematic diagram showing a possible structure of a core network entity involved in the foregoing embodiment.
  • the core network entity 1000 may include: a communication unit 1001 and a processing unit 1002.
  • the unit may perform the corresponding functions of the core network entity, such as the AMF, in the foregoing method example, for example, the communication unit 1001 is configured to be connected to the first base station, and the user equipment UE accessing the network by the first base station is in a radio resource connection.
  • the RRC Inactive state the communication unit 1001 is further configured to receive a first request message sent by the UE by using the second base station, or receive a second request message sent by another core network entity, where The second request message is sent by the another core network entity to the core network entity when the another core network entity receives the first request message sent by the UE by using the second base station, and the second The base station does not support the RRC Inactive state; the processing unit 1002 is configured to invoke the communication unit 1001 to release a connection with the first base station.
  • the first base station may be a base station corresponding to the network accessed by the UE before the mobile station moves
  • the second base station may be a base station corresponding to the network accessed by the UE after the mobile station moves.
  • the first request message includes indication information, where the indication information indicates that the UE is switched from the RRC Inactive state to an idle state IDLE state.
  • processing unit 1002 is further configured to invoke the communication unit 1001 to perform protocol data unit session de-excitation Live process PDU session deactivation procedure.
  • the first request message is a location update request, an attach request, a registration request, or a service request.
  • the first request message further includes UE capability information, where the UE capability information indicates that the UE supports the RRC Inactive state.
  • the first base station supports the RRC Inactive state.
  • the core network entity may be an MME or an AMF or an SGSN, and the second core network entity may be an AMF.
  • each functional unit in the 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.
  • FIG. 11 is a schematic diagram showing another possible structure of the core network entity involved in the foregoing embodiment.
  • the core network entity 1100 may include: a processing unit 1102. And communication unit 1103.
  • the processing unit 1102 can be used to control and manage the actions of the core network entity.
  • the processing unit 1102 is configured to support the core network entity to perform the processes 306, 307 in FIG. 3, the processes 405, 406, etc. in FIG. 4, and/or Other processes for the techniques described herein.
  • the communication unit 1103 is for supporting communication between the core network entity and other network entities, such as communication with the functional units or network entities shown in Figures 2-5.
  • the core network entity may also include a storage unit 1101 for storing program code (operation instructions) and data of the core network entity.
  • the processing unit 1102 may be a processor or a controller, and may be, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application-specific integrated circuit (Application-Specific). Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication unit 1103 can be a transceiver.
  • the storage unit 1101 may be a memory.
  • the core network entity involved in the embodiment of the present invention may be the core network entity shown in FIG.
  • the core network entity 1200 can include a processor 1202, a transceiver 1203, a memory 1201, and a bus 1204.
  • the transceiver 1203, the processor 1202, and the memory 1201 are connected to each other through a bus 1204.
  • the bus 1204 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA). ) Bus, etc.
  • PCI peripheral component interconnect
  • EISA extended industry standard architecture
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 12, but it does not mean that there is only one bus or one type of bus.
  • the steps of a method or algorithm described in connection with the present disclosure may be implemented in a hardware or may be implemented by a processor executing software instructions.
  • the software instructions may be composed of corresponding software modules or units, which may be stored in a random access memory (RAM), flash memory, read only memory (ROM), erasable and programmable. Read only memory (Erasable Programmable) ROM, EPROM), electrically erasable programmable read only memory (EEPROM), registers, hard disk, removable hard disk, compact disk read only (CD-ROM) or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and the storage medium can be located in an ASIC. Additionally, the ASIC can be located in a core network entity. Of course, the processor and the storage medium can also exist as discrete components in the core network entity.
  • each step of the above method may be completed by an integrated logic circuit of hardware in a processor or an instruction in a form of software.
  • the steps of the method disclosed in the embodiments of the present application may be directly implemented by the hardware processor, or may be performed by a combination of hardware and software modules in the processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory, and the processor reads the information in the memory and combines the hardware to complete the steps of the above method. To avoid repetition, it will not be described in detail here.
  • the size of the serial numbers of the above processes does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not be taken to the embodiments of the present invention.
  • the implementation process constitutes any limitation.
  • the disclosed system, apparatus, user equipment, core network entity and method may be implemented in other manners.
  • 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 Can be integrated 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 in an electrical, mechanical or other form.
  • 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 application 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 embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).

Landscapes

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

Abstract

本申请公开了一种连接管理方法、用户设备、核心网实体及***，其中，该方法包括：UE通过第一基站接入网络，所述UE处于RRC Inactive state；所述UE通过第二基站接入网络，第二基站不支持RRC Inactive state；所述UE通过第二基站向第一核心网实体发送第一请求消息，以使第一核心网实体根据第一请求消息释放与第一基站的连接，或者，以使第一核心网实体向第二核心网实体发送第二请求消息，并由第二核心网实体根据第二请求消息释放与第一基站的连接。采用本申请，能够实现处于RRC Inactive state的UE与不支持RRC Inactive state的基站之间的通信。

Description

连接管理方法、用户设备、核心网实体及*** 技术领域
本申请涉及无线通信技术领域，尤其涉及一种连接管理方法、用户设备、核心网实体及***。
背景技术
无线资源控制(Radio Resource Control，缩写：RRC)非激活(Inactive)态(state)，是指用户设备(User Equipment，缩写：UE)与基站之间为空闲(IDLE)态，基站与核心网之间为连接(connected)态。当UE为RRC Inactive state时，需要无线接入网络(Radio Access Network，缩写：RAN)具有支持RRC Inactive的功能，从而实现对UE的寻呼、可达性管理等等。然而，在第五代移动通信技术(The Fifth Generation Mobile Communication Technology，缩写：5G)网络中，可能存在不支持RRC Inactive state的基站，比如接入5G核心网的某些4G基站不支持RRC Inactive state，如果UE进入一个不支持RRC Inactive state的基站小区，即RRC Inactive state的UE移出驻留的支持RRC Inactive state的基站所覆盖的无线接入网络通知区域RNA(RAN notification Area)，移动并驻留到一个不支持RRC Inactive state的基站时，该UE无法和该不支持RRC Inactive state的基站进行通信。因RRC Inactive state下的UE如果要跟网络通信，只能发送RRC resume请求，但是不支持RRC Inactive state的RAN无法识别该请求，就会导致该UE没法跟当前的基站通信。
发明内容
本发明实施例提供了一种连接管理方法、用户设备、核心网实体及***，能够实现处于RRC Inactive state的UE与不支持RRC Inactive state的基站之间的通信。
一方面，本发明实施例提供了一种连接管理方法，包括：用户设备UE通过第一基站接入网络，该UE处于无线资源连接非激活态(RRC Inactive state)；UE通过第二基站接入网络，该第二基站不支持RRC Inactive state，由此该UE可通过该第二基站向第一核心网实体发送第一请求消息。该第一核心网实体和第一基站连接，第一核心网实体接收UE通过该第二基站发送的第一请求消息，并可根据该第一请求消息释放与该第一基站之间的连接。或者，该UE可通过该第二基站向第一核心网实体发送第一请求消息，进一步的，第一核心网实体可向第二核心网实体发送第二请求消息，从而该第二核心网实体可接收该第一核心网实体发送的第二请求消息，并可根据该第二请求消息释放与该第一基站的连接。
其中，该第一基站可以为该UE移动前接入的网络如无线接入网络(Radio Access Network，缩写：RAN)对应的基站，即UE移动前连接的基站。该第二基站可以为该UE移动后接入的网络如RAN对应的基站，即该UE移动后连接的基站，该第二基站不支持RRC Inactive state。例如，该第一基站可以是5G基站，第二基站可以是不支持RRC Inactive state的4G基站，也可以是不支持RRC Inactive state的5G基站，等等，此处不一一列举。进一步的，该UE支持RRC Inactive state，且该UE与该第一基站通信时可以处于该RRC Inactive state。从而能够实现处于RRC Inactive state的UE与不支持RRC Inactive state的基 站之间的通信。
在一种可能的设计中，UE可通过接收该第二基站发送的广播消息，并根据该广播消息确定该第二基站是否支持RRC Inactive state，进而可在确定该第二基站不支持RRC Inactive state时，触发向第一核心网实体发送请求消息。
在一种可能的设计中，该第一核心网实体可以为第二基站接入的网络中的核心网实体，该第二核心网实体可以为该第一基站接入的网络中的核心网实体。该核心网实体可以是接入和移动性管理功能实体(Access and Mobility Management Function，缩写：AMF)、移动管理实体(Mobility Management Entity，缩写：MME)或3G的核心网实体如服务通用分组无线业务(General Packet Radio Service，缩写：GPRS)支持节点(Serving GPRS Support Node，缩写：SGSN)，或者为其他通信***中的核心网实体，本申请不做限定。例如，该第一基站为5G基站，第二基站可为4G基站时，该第一核心网实体可以为MME，第二核心网实体可以为AMF；又如，第一基站和第二基站均为4G基站时，该第一核心网实体和第二核心网实体可以均为AMF，且两者可以是同一个AMF，也可以是不同的AMF。
在一种可能的设计中，在UE通过该第二基站向第一核心网实体发送第一请求消息之前，该UE可将该UE的状态由该RRC Inactive state切换为空闲态IDLE state。
在一种可能的设计中，该第一请求消息可包括指示信息，该指示信息指示该UE由该RRC Inactive state切换为空闲态IDLE state。
在一种可能的设计中，该第一请求消息和/或该第二请求消息还可用于指示该核心网实体执行协议数据单元(Protocol Data Unit，缩写：PDU)会话去激活流程(PDU session deactivation procedure)。进一步的，该第一核心网实体在接收到该第一请求消息之后，还可执行PDU session deactivation procedure，包括释放与会话管理功能实体(Session Management Function，缩写：SMF)的连接等等。或者，第二核心网实体接收第一核心网实体发送的第二请求消息之后，该第二核心网实体还可执行PDU session deactivation procedure。
在一种可能的设计中，该第一请求消息可以为位置更新请求如跟踪区更新(Tracking Area Update，缩写：TAU)Request、附着请求如Attach Request、注册请求如Registration Request或业务请求如Service Request，而不是RRC resume请求。
在一种可能的设计中，该第二请求消息可以是核心网之间的消息，如上下文请求context request、上下文转换context transfer消息等等。
在一种可能的设计中，该第一请求消息还可包括UE能力信息，该UE能力信息指示该UE支持RRC Inactive state。也即，该第一请求消息还可携带UE支持RRC Inactive state的能力信息。
在一种可能的设计中，该第一基站支持该RRC Inactive state，也即，该第一基站可以为支持RRC Inactive state的基站。
另一方面，本发明实施例还提供了一种用户设备，该用户设备具有实现上述方法示例中用户设备UE行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元或模块。
在一种可能的设计中，用户设备的结构中可包括通信单元和处理单元，所述处理单元被配置为支持用户设备执行上述方法中相应的功能。所述通信单元用于支持用户设备与其 他设备之间的通信。所述用户设备还可以包括存储单元，所述存储单元用于与处理单元耦合，其保存用户设备必要的程序指令(操作指令)和数据。作为示例，处理单元可以为处理器，通信单元可以为收发器，存储单元可以为存储器。
又一方面，本发明实施例提供一种核心网实体，该核心网实体具有实现上述方法示例中核心网实体如第一核心网实体或第二核心网实体行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元或模块。
在一种可能的设计中，核心网实体的结构中包括通信单元和处理单元，所述处理单元被配置为支持核心网实体执行上述方法中相应的功能。所述通信单元用于支持核心网实体与其他设备之间的通信。所述核心网实体还可以包括存储单元，所述存储单元用于与处理单元耦合，其保存核心网实体必要的程序指令(操作指令)和数据。作为示例，处理单元可以为处理器，通信单元可以为收发器，存储单元可以为存储器。
又一方面，本发明实施例提供了一种通信***，该***包括上述方面的用户设备和/或核心网实体如第一核心网实体或第二核心网实体。在另一种可能的设计中，该***还可以包括本发明实施例提供的方案中与该用户设备或核心网实体进行交互的其他设备，如第一基站、第二基站、SMF等等。
又一方面，本发明实施例提供了一种计算机存储介质，用于储存为上述用户设备所用的计算机软件指令，其包括用于执行上述方面所设计的程序。
又一方面，本发明实施例提供了一种计算机存储介质，用于储存为上述核心网实体如第一核心网实体或第二核心网实体所用的计算机软件指令，其包括用于执行上述方面所设计的程序。
又一方面，本发明实施例提供了一种计算机程序，包括指令，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
又一方面，本申请还提供了一种包括指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
又一方面，本申请提供了一种芯片***，该芯片***包括处理器，用于支持用户设备实现上述方面中所涉及的功能，例如，例如生成或处理上述方法中所涉及的数据和/或信息。在一种可能的设计中，所述芯片***还包括存储器，所述存储器，用于保存用户设备必要的程序指令和数据。该芯片***，可以由芯片构成，也可以包括芯片和其他分立器件。
又一方面，本申请提供了一种芯片***，该芯片***包括处理器，用于支持核心网实体如第一核心网实体或第二核心网实体实现上述方面中所涉及的功能，例如，例如接收或处理上述方法中所涉及的数据和/或信息。在一种可能的设计中，所述芯片***还包括存储器，所述存储器，用于保存核心网实体必要的程序指令和数据。该芯片***，可以由芯片构成，也可以包括芯片和其他分立器件。
在本申请要求保护的技术方案中，UE可通过第一基站接入网络，此时UE可以处于RRC Inactive state。进一步的，UE还可通过第二基站接入网络，比如UE由第一基站所在小区移动到第二基站所在小区，则UE可在确定该第二基站不支持RRC Inactive state之后，向核心网实体发送请求消息，从而核心网实体能够在接收到该请求消息之后，释放与该第 一基站之间的连接，由此实现了处于RRC Inactive state的UE与不支持RRC Inactive state的基站之间的通信。
附图说明
图1是本发明实施例提供的一种通信***的应用场景图；
图2是本发明实施例提供的一种连接管理方法的交互示意图；
图3是本发明实施例提供的另一种连接管理方法的交互示意图；
图4是本发明实施例提供的又一种连接管理方法的交互示意图；
图5是本发明实施例提供的又一种连接管理方法的交互示意图；
图6是本发明实施例提供的一种连接管理***的结构示意图；
图7是本发明实施例提供的一种用户设备的结构示意图；
图8是本发明实施例提供的另一种用户设备的结构示意图；
图9是本发明实施例提供的又一种用户设备的结构示意图；
图10是本发明实施例提供的一种核心网实体的结构示意图；
图11是本发明实施例提供的另一种核心网实体的结构示意图；
图12是本发明实施例提供的又一种核心网实体的结构示意图。
具体实施方式
下面结合本发明实施例中的附图对本发明实施例进行描述。
应理解，本申请的技术方案可具体应用于各种通信网络中,例如：全球移动通讯***(Global system for mobile communications，缩写：GSM)、码分多址(Code Division Multiple Access，缩写：CDMA)、宽带码分多址(Wideband Code Division Multiple Access，缩写：WCDMA)、时分同步码分多址(Time Division-Synchronous Code Division Multiple Access，缩写：TD-SCDMA)、通用移动通信***(Universal Mobile Telecommunications System，缩写：UMTS)、长期演进(Long Term Evolution，缩写：LTE)网络等，随着通信技术的不断发展，本申请的技术方案还可用于未来网络，如5G网络，也可以称为新空口(New Radio，缩写：NR)网络，或者可用于D2D(device to device)网络，M2M(machine to machine)网络等等。
本申请涉及的核心网实体可以是MME、AMF或SGSN等等，本申请不做限定。
在本申请中，用户设备是一种具有通信功能的设备，也可以称为终端，其可以包括具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备等。在不同的网络中用户设备可以叫做不同的名称，例如：终端，UE，移动台，用户单元，站台，蜂窝电话，个人数字助理，无线调制解调器，无线通信设备，手持设备，膝上型电脑，无绳电话，无线本地环路台等。该用户设备可以是无线终端或有线终端。该无线终端可以是指向用户提供语音和/或数据连通性的设备，具有无线连接功能的手持式设备、或连接到无线调制解调器的其他处理设备，其可以经无线接入网(如RAN，radio access network)与一个或多个核心网进行通信。
在本申请中，基站也可称为基站设备，是一种部署在无线接入网用以提供无线通信功 能的设备。在不同的无线接入***中基站的名称可能有所不同，例如在通用移动通讯***UMTS网络中基站称为节点B(NodeB),在LTE网络中的基站称为演进的节点B(evolved NodeB，缩写：eNB或者eNodeB)，在未来5G***中可以称为收发节点(Transmission Reception Point，缩写：TRP)网络节点或g节点B(g-NodeB，gNB)，等等，此处不一一列举。
下面对本申请的应用场景进行介绍，请参见图1，图1是本发明实施例提供的一种通信***的架构图。具体的，如图1所示，该通信***中可包括UE、第一基站、第二基站以及第一核心网实体。该***还可选的包括第二核心网实体。其中，该UE为支持RRC Inactive state的UE，且该UE在与该第一基站进行通信时可以处于RRC Inactive state。该第一基站可以为该UE移动前接入的网络如RAN对应的基站，该第二基站可以为该UE移动后接入的网络如RAN对应的基站，该第一基站可以支持RRC Inactive state也可以不支持RRC Inactive state，该第二基站不支持RRC Inactive state。该第一核心网实体可以为第二基站接入的网络中的核心网实体，该第二核心网实体可以为该第一基站接入的网络中的核心网实体。可选的，该第一基站对应的核心网实体即第二核心网实体和第二基站对应的核心网实体即第一核心网实体可以相同也可以不同。进一步的，该通信***还可选的包括SMF、用户端口功能实体(英文：User Port Function，缩写：UPF)(图中未示出)等等。
由于RRC Inactive state下的UE发送的RRC resume请求不能被不支持RRC Inactive state的RAN(基站，如上述的第二基站)识别，使得处于RRC Inactive state的UE无法和该不支持RRC Inactive state的RAN进行通信。由此，本申请能够通过向不支持RRC Inactive state的RAN发送请求消息如业务请求或注册请求等，以指示核心网实体如上述的第一核心网实体或第二核心网实体释放与该第一基站之间的连接，从而实现处于RRC Inactive state的UE与不支持RRC Inactive state的RAN之间的通信。
本申请公开了一种连接管理方法、用户设备、核心网实体及***，有助于实现处于RRC Inactive state的UE与不支持RRC Inactive state的RAN之间的通信。以下分别详细说明。
请参见图2，图2是本发明实施例提供的一种连接管理方法的交互示意图。具体的，如图2所示，本发明实施例的连接管理方法可以包括以下步骤：
201、UE通过第一基站接入网络。
202、UE通过第二基站接入网络，该第二基站不支持RRC Inactive state。
具体的，UE可分别与第一基站和第二基站建立连接。其中，该第一基站可以为UE移动前接入的RAN对应的基站，该第二基站可以为该UE移动后接入的RAN对应的基站，且UE为支持RRC Inactive state的UE，比如该UE与第一基站进行通信时可以处于RRC Inactive state。
203、UE通过第二基站向第一核心网实体发送第一请求消息。
可选的，第二基站可通过向UE发送广播消息，告知UE该第二基站是否支持RRC Inactive state。从而UE可根据该广播消息确定该第二基站是否支持RRC Inactive state，进而可在确定该第二基站不支持RRC Inactive state时，向核心网实体如MME或AMF发送请求消息，以使核心网实体根据该请求消息释放与该第一基站之间的连接。具体的，在一些 场景中，如第一基站接入网络中的核心网实体与第二基站接入网络中的核心网实体相同时，UE可通过第二基站向第一核心网实体发送第一请求消息，由该第一请求消息触发第一核心网实体释放该第一核心网实体与该第一基站之间的连接，即执行步骤203-204。或者，在其他场景中，比如第一基站接入网络中的核心网实体(即第二核心网实体)与第二基站接入网络中的核心网实体(即第一核心网实体)不同时，UE可通过第二基站向第一核心网实体发送第一请求消息，通过该第一核心网设备向第二核心网设备发送第二请求消息，由该第二请求消息触发第二核心网实体释放该第二核心网实体与该第一基站之间的连接，即执行步骤203、205-206。
具体的，该广播消息可包括指示该第二基站是否支持RRC Inactive state的信息。例如，该广播消息可包括“0”或“1”，通过“0”指示不支持该RRC Inactive state，通过“1”指示支持该RRC Inactive state。或者，该广播消息可以直接携带该第二基站支持RRC Inactive state或不支持RRC Inactive state的能力信息，或者可以通过其他方式指示，本申请不做限定。或者，可选的，该广播消息还可仅在第二基站支持RRC Inactive state时携带该第二基站支持RRC Inactive state的能力信息，在第二基站不支持RRC Inactive state时不携带该第二基站是否支持RRC Inactive state的能力信息；从而UE在接收到第二基站发送的广播消息后，可根据该广播消息中是否携带支持RRC Inactive state的能力信息来确定该第二基站是否支持RRC Inactive state，具体可在检测到该广播消息携带支持RRC Inactive state的能力信息时，确定该第二基站支持RRC Inactive state，在检测到该广播消息没有携带支持RRC Inactive state的能力信息时，确定该第二基站不支持RRC Inactive state。
其中，该请求消息如上述的第一请求消息可用于指示该第一核心网实体释放与第一基站之间的连接，以便于第一核心网实体在接收到该第一请求消息时，能够及时地释放与该第一基站的连接。该第二请求消息可用于指示第二核心网实体释放与第一基站之间的连接，以便于第二核心网实体在接收到该第二请求消息时，能够及时地释放与该第一基站的连接。
可选的，该第一请求消息可以为位置更新请求如TAU Request、附着请求如Attach Request、注册请求如Registration Request或业务请求如Service Request。
204、第一核心网实体根据第一请求消息释放与第一基站之间的连接。
205、第一核心网实体向第二核心网实体发送第二请求消息。
206、第二核心网实体根据第二请求消息释放与第一基站之间的连接。
可选的，在该UE通过该第二基站向核心网实体发送请求消息之前，该UE可将该UE的状态由该RRC Inactive state切换为IDLE state，即进行状态切换。具体的，在进行状态切换时，可以由RRC层通知非接入层(Non-access stratum，缩写：NAS)层，从RRC Inactive state置为IDLE state。
可选的，该UE处于该RRC Inactive state，该第一请求消息是该广播消息触发的位置更新请求、附着请求、注册请求或业务请求。也就是说，UE在接收到该广播消息，确定该第二基站不支持该RRC Inactive state之后，UE仍可保持RRC Inactive state，但是可以根据该广播消息触发执行IDLE state下的第一请求消息如位置更新请求、附着请求、注册请求或业务请求等等，而不是发送RRC Inactive state下的RRC resume请求，由此可以确保网络侧识别出该第一请求消息，进而释放与该第一基站的连接。
进一步可选的，该第一请求消息可以包括指示信息，该指示信息可指示该UE由该RRC Inactive state切换为空闲态IDLE state。从而核心网实体可在接收到该包括该指示信息的第一请求消息时，确定释放与该第一基站的连接。
进一步可选的，该第一请求消息和/或该第二请求消息还可用于指示该核心网实体执行PDU session deactivation procedure。具体的，该第一核心网实体在接收到该第一请求消息之后，还可执行PDU session deactivation procedure，比如该第一核心网实体可释放与SMF的连接。或者，第二核心网实体接收第一核心网实体发送的第二请求消息之后，该第二核心网实体还可执行PDU session deactivation procedure。具体的，第二核心网实体如AMF在执行PDU session deactivation procedure，AMF可向SMF发送会话管理上下文更新请求如Nsmf_PDUSession_UpdateSMContext，从而SMF可发起PDU session deactivation procedure等，以完成N3连接的释放。
可选的，该第一请求消息还可以包括UE能力信息，该UE能力信息可以指示该UE支持RRC Inactive state。也就是说，该第一请求消息还可以携带UE支持RRC Inactive state的能力信息。
可选的，该第一基站可以支持该RRC Inactive state。也就是说，本申请也适用于UE从支持RRC Inactive state的RAN(即支持RRC Inactive state的第一基站所在网络)移动到不支持RRC Inactive state的RAN(即不支持RRC Inactive state的第二基站所在网络)的场景。
进一步可选的，该释放的连接可包括核心网实体与第一基站之间的N2和/或N3连接等等。具体的，核心网实体(如第一核心网实体或第二核心网实体)释放与第一基站的连接可以包括：删除第一基站中UE context，释放核心网实体与第一基站所在RAN的N2连接，释放UPF中第一基站的context，释放UPF与第一基站的N3连接，去激活PDU session等等中的一项或多项。
具体的，如果该第一基站和第二基站对应的核心网实体相同时，也即UE移动前后的进行通信的核心网实体不变。此时UE可向该核心网实体如AMF发送请求消息触发释放其与第一基站的连接，以及由AMF向SMF发送会话管理上下文更新请求如Nsmf_PDUSession_UpdateSMContext，从而SMF可发起PDU session deactivation procedure等，以完成N3连接的释放。进一步可选的，该核心网实体如AMF还可向第一基站发送N2UE Context Release Command。进一步的，该核心网实体还可发送位置更新接收响应给UE。进一步可选的，该核心网实体还可发送N2Request给第二基站，该N2Request中可携带Service Accept等信息。进一步可选的，该第二基站还可在RRC connection reconfiguration请求中携带Service Accept发送给UE。
或者，如果该第一基站和第二基站对应的核心网实体不同，也即UE移动前后的进行通信的核心网实体发生改变，即存在上述的第一核心网实体和第二核心网实体时，UE可向该第一核心网实体发送第一请求消息，并由第一核心网实体向第二核心网实体发送第二请求消息如context request或context transfer消息等等，使得第二核心网实体触发释放其与第一基站的连接以及执行PDU session deactivation procedure等。可选的，第二核心网实体如AMF可触发release其与第一基站的N2连接，以及由AMF向SMF发送会话管理上下文更新请求如Nsmf_PDUSession_UpdateSMContext，并由SMF发起deactivate PDU session，即 实现执行PDU session deactivation procedure，以完成N3连接的释放。进一步可选的，第二核心网实体还可向第一基站发送N2UE Context Release Command。进一步的，该第一核心网实体还可发送位置更新接收响应给UE。进一步可选的，第一核心网实体还可发送N2Request给第二基站，该N2Request中可携带Service Accept等信息。进一步可选的，该第二基站还可在RRC connection reconfiguration请求中携带Service Accept发送给UE。
具体的，该发送位置更新接收响应、释放与第一基站的连接、执行PDU session deactivation procedure、发送N2UE Context Release Command等信息的顺序不受限制，其可以同时执行，也可以不同时执行，本申请不做限定。
在本发明实施例中，UE可通过第一基站接入网络，此时UE可以处于RRC Inactive state。进一步的，UE还可通过第二基站接入网络，比如UE由第一基站所在小区移动到第二基站所在小区，则UE可在确定该第二基站不支持RRC Inactive state之后，向核心网实体发送请求消息，从而核心网实体能够在接收到该请求消息之后，释放与该第一基站之间的连接，由此实现了处于RRC Inactive state的UE与不支持RRC Inactive state的基站之间的通信。
请参见图3，图3是本发明实施例提供的另一种连接管理方法的交互示意图。具体的，如图3所示，本发明实施例的连接管理方法可以包括以下步骤：
301、UE通过第一基站接入网络，UE处于RRC Inactive state。
302、UE通过第二基站接入网络。
其中，该UE可以处于RRC Inactive state。可选的，该第一基站可以为支持该RRC Inactive state的基站。
303、第二基站向UE发送广播消息。
具体的，在某些情况下，UE可能需要从第一基站所在RAN切换到第二基站所在RAN，比如UE发生移动时，该第一基站即为UE移动前的RAN对应的基站，该第二基站即为该UE发生移动后的RAN对应的基站。该广播消息可用于指示该第二基站是否支持RRC Inactive state。在本发明实施例中，假设该广播消息指示该第二基站不支持RRC Inactive state。
304、UE根据该广播消息确定第二基站不支持RRC Inactive state，将该UE的状态由RRC Inactive state切换为IDLE state。
305、UE向AMF发送请求消息，该请求消息中携带有指示信息，该指示信息指示该UE由该RRC Inactive state切换为IDLE state。
具体的，UE可接收来自于该第二基站的该广播消息，如果根据该广播消息确定该第二基站不支持RRC Inactive state，比如该广播消息中未携带第二基站支持RRC Inactive state的能力信息时，UE可将该UE的状态由该RRC Inactive state切换为IDLE state，进而向核心网实体(即第一核心网实体)如AMF发送请求消息(即第一请求消息)如位置更新请求、附着请求、注册请求或业务请求等等。其中，UE可通过向该第二基站发送该请求消息，并由该第二基站向AMF转发该请求消息。例如，UE在将RRC Inactive state切换为IDLE state之后，可向第二基站发送基于位置更新的注册请求如Registration Request，通过该第二基站 向AMF发送该Registration Request。
可选的，该请求消息如Registration Request可以包括一个指示信息，该指示信息可用于指示该UE由该RRC Inactive state切换为IDLE state，也即在请求消息中携带inactive->idle的指示indication。
进一步可选的，该请求消息如Registration Request还可包括UE能力信息，该UE能力信息可用于指示该UE支持该RRC Inactive state。也就是说，该请求消息还可以携带UE支持RRC Inactive state的能力信息，比如该UE能力信息可携带于该请求消息中的UE Network Capability中。
306、AMF释放与第一基站的连接。
具体的，AMF在接收到该请求消息如Registration Request之后，即可释放与该第一基站之间的连接。
307、AMF执行PDU session deactivation procedure。
可选的，该请求消息还可用于指示该AMF执行PDU session deactivation procedure。从而AMF在接收到该请求消息时，还可执行PDU session deactivation procedure，包括释放AMF与SMF的连接。进一步的，SMF还可释放与UPF的连接。
可选的，本发明实施例可以应用于UE从支持RRC Inactive state的5G基站(第一基站)的小区移动到不支持RRC Inactive state的5G基站(第二基站)小区的场景。具体的，该第一基站和第二基站对应的AMF可以相同，也可以不同，其相同或不同时的消息发送和连接释放方式可参照上述图2所示实施例的相关描述，此处不赘述。
在本发明实施例中，UE可在接收到第二基站发送的广播消息，并根据该广播消息确定该第二基站不支持RRC Inactive state之后，将该UE的状态由RRC Inactive state切换为IDLE state，并向AMF发送请求消息以指示该AMF释放与移动前接入的第一基站之间的连接，从而AMF在接收到请求消息之后，能够释放与该第一基站之间的连接以及其它相关连接，由此实现了处于RRC Inactive state的UE与不支持RRC Inactive state的基站之间的通信。
请参见图4，图4是本发明实施例提供的又一种连接管理方法的交互示意图。具体的，如图4所示，本发明实施例的连接管理方法可以包括以下步骤：
401、UE通过第一基站接入网络，UE处于RRC Inactive state。
402、UE通过第二基站接入网络。
其中，该第一基站可以为支持该RRC Inactive state的基站。
403、第二基站向UE发送广播消息。
具体的，该步骤401-403可参照上述图3所示实施例中的步骤301-303的描述，此处不赘述。
404、UE根据该广播消息确定第二基站不支持RRC Inactive state时，向AMF发送请求消息。
具体的，UE可接收来自于该第二基站的该广播消息，并可在根据该广播消息确定该第二基站不支持RRC Inactive state，比如该广播消息中未携带第二基站支持RRC Inactive state的能力信息时，由该广播消息触发向核心网实体(即第一核心网实体)如AMF发送请求消 息(即第一请求消息)如位置更新请求、附着请求、注册请求或业务请求等等。其中，UE可通过向该第二基站发送该请求消息，并由该第二基站向AMF转发该请求消息。例如，UE可向第二基站发送基于位置更新的注册请求如Registration Request，通过该第二基站向AMF发送该Registration Request。
可选的，该请求消息如Registration Request可以包括一个指示信息，该指示信息可用于指示该UE由该RRC Inactive state切换为IDLE state，也即在请求消息中携带inactive->idle的indication。
进一步可选的，该请求消息如Registration Request还可包括UE能力信息，该UE能力信息可用于指示该UE支持RRC Inactive state，也即，该请求消息还可以携带UE支持RRC Inactive state的能力信息。例如，该UE能力信息可携带于该请求消息中的UE Network Capability中。
405、AMF释放与第一基站的连接。
具体的，AMF在接收到该请求消息如Registration Request之后，即可释放与该第一基站之间的连接。
406、AMF执行PDU session deactivation procedure。
可选的，该请求消息还可用于指示该AMF执行PDU session deactivation procedure。从而AMF在接收到该请求消息时，还可执行PDU session deactivation procedure，包括可释放与SMF的连接。进一步的，SMF还可释放与UPF的连接。
具体的，该第一基站和第二基站对应的AMF可以相同，也可以不同，其相同或不同时的消息发送和连接释放方式可参照上述图2所示实施例的相关描述，此处不赘述。
进一步可选的，在向AMF发送请求消息之后，UE还可将该UE的状态由该RRC Inactive state切换为IDLE state，以便于与该不支持RRC Inactive state的第二基站进行通信。
在本发明实施例中，处于RRC Inactive state的UE可在接收到第二基站发送的广播消息，并根据该广播消息确定该第二基站不支持RRC Inactive state时，由该广播消息触发向AMF发送请求消息如注册请求或业务请求等等，从而AMF在接收到请求消息之后，能够根据该请求消息释放与该第一基站之间的连接以及其它相关连接，由此实现了处于RRC Inactive state的UE与不支持RRC Inactive state的RAN之间的通信。
请参见图5，图5是本发明实施例提供的又一种连接管理方法的交互示意图。具体的，如图5所示，本发明实施例的连接管理方法可以包括以下步骤：
501、UE通过第一基站接入网络，UE处于RRC Inactive state。
502、UE通过第二基站接入网络。
503、第二基站向UE发送广播消息。
具体的，该步骤501-503可参照上述图3所示实施例中的步骤301-303的描述，此处不赘述。
504、UE根据该广播消息确定第二基站不支持RRC inactive state时，向MME发送第一请求消息。
505、MME向AMF发送第二请求消息。
506、AMF释放与第一基站之间的连接。
507、AMF执行PDU session deactivation procedure。
可选的，本发明实施例可应用于UE从支持RRC Inactive state的5G基站即第一基站的小区移动到不支持RRC Inactive state的4G基站即第二基站的小区的场景。UE可接收来自于该第二基站的该广播消息，并可在根据该广播消息确定该第二基站不支持RRC Inactive state时，通过第二基站向4G核心网实体MME(第一核心网实体)发送请求消息(即第一请求消息)如位置更新请求、附着请求、注册请求或业务请求等等。例如，UE可通过第二基站向MME发送位置更新请求如TAU request或附着请求Attach request。进一步的，MME接收到该TAU request或Attach request后，还可向AMF(第二核心网实体)发送第二请求消息如context request，进而AMF可在接收到该context request时，触发释放该AMF与第一基站之间的连接、执行PDU session deactivation procedure等等。
可选的，在其他场景中，比如UE从支持RRC Inactive state的5G基站即第一基站的小区移动到不支持RRC Inactive state的5G基站即第二基站的小区的场景下，该第一基站和第二基站对应的AMF不同时，UE可向第二基站对应的AMF(new AMF，即第一核心网实体)发送第一请求消息，由new AMF向第一基站对应的AMF(old AMF，即第二核心网实体)发送第二请求消息如context transfer消息，从而old AMF可释放与第一基站之间的连接等等，其过程与上述场景的连接释放过程类似，此处不赘述。
上述方法实施例都是对本申请的连接管理方法的举例说明，对各个实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其他实施例的相关描述。
请参见图6，是本发明实施例提供的一种连接管理***的结构示意图。如图6所示，本发明实施例的连接管理***包括UE1、第一基站2、第二基站3和第一核心网实体4、第二核心网实体5。其中，
所述UE1，用于通过第一基站2接入网络，所述UE1处于无线资源连接非激活态RRC Inactive state；通过第二基站3接入网络，所述第二基站3不支持所述RRC Inactive state；通过所述第二基站3向第一核心网实体4发送第一请求消息。
所述第一核心网实体4，用于和第一基站2连接；接收所述UE1通过第二基站3发送的第一请求消息，所述第二基站3不支持所述RRC Inactive state；释放与所述第一基站2之间的连接。
所述第二核心网实体5，用于和第一基站2连接；接收第二核心网实体4发送的第二请求消息，该第二请求消息是该第一核心网实体4接收到所述UE通过第二基站3发送的第一请求消息时，第一核心网实体4向该第二核心网实体5发送的，所述第二基站3不支持RRC Inactive state；释放与所述第一基站2之间的连接。
可选的，该第一基站2可以为UE移动前接入的网络对应的基站，该第二基站3可以为该UE移动后接入的网络对应的基站。本发明实施例中的UE、第一基站、第二基站和第一核心网实体、第二核心网实体可参照上述图2至图5所示实施例的相关描述，此处不赘述。
图7示出了上述实施例中所涉及的用户设备的一种可能的结构示意图，参阅图7所示， 该用户设备700可包括：通信单元701和处理单元702。其中，这些单元可以执行上述方法示例中UE的相应功能，例如，通信单元701，用于通过第一基站接入网络，所述用户设备UE处于无线资源连接非激活态RRC Inactive state；所述通信单元701，还用于通过第二基站接入网络，所述第二基站不支持所述RRC Inactive state；所述通信单元701，还用于通过所述第二基站向第一核心网实体发送第一请求消息，以使所述第一核心网实体根据所述第一请求消息释放与所述第一基站的连接，或者，以使所述第一核心网实体向第二核心网实体发送第二请求消息，并由所述第二核心网实体根据所述第二请求消息释放与所述第一基站的连接。进一步的，所述通信单元701，还用于接收所述第二基站发送的广播消息；处理单元702，用于根据所述广播消息确定所述第二基站是否支持所述RRC Inactive state。进而通信单元701可在处理单元702确定该第二基站不支持RRC Inactive state时，通过第二基站向核心网实体发送请求消息。
可选的，所述第一基站为所述UE移动前接入的网络对应的基站，所述第二基站为所述UE移动后接入的网络对应的基站。
可选的，该第一核心网实体可以为第二基站接入的网络的核心网实体，第二核心网实体可以为第一基站接入的网络的核心网实体。
可选的，所述处理单元701，还可用于将所述UE的状态由所述RRC Inactive state切换为空闲态IDLE state。
可选的，所述第一请求消息可包括指示信息，所述指示信息可指示所述UE由所述RRC Inactive state切换为空闲态IDLE state。
可选的，所述第一请求消息可以为位置更新请求、附着请求、注册请求或业务请求。
可选的，所述第一请求消息还包括UE能力信息，所述UE能力信息指示所述UE支持所述RRC Inactive state。
可选的，所述第一基站支持所述RRC Inactive state。
可选的，所述第一核心网实体可以为MME或AMF或SGSN等等，第二核心网实体可以为AMF。
需要说明的是，本发明实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。本发明实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
在采用集成的单元的情况下，图8示出了上述实施例中所涉及的用户设备的另一种可能的结构示意图，如图8所示，该用户设备800可包括：处理单元802和通信单元803。处理单元802可用于对用户设备的动作进行控制管理，例如，处理单元802用于支持用户设备执行图3中的过程304等等，和/或用于本文所描述的技术的其它过程。通信单元803用于支持用户设备与其他网络实体的通信，例如与图2至图5中示出的功能单元或网络实体之间的通信。用户设备还可以包括存储单元801，用于存储用户设备的程序代码(操作指令)和数据。
其中，处理单元802可以是处理器或控制器，例如可以是中央处理器(Central Processing Unit，CPU)，通用处理器，数字信号处理器(Digital Signal Processor，DSP)，专用集成电 路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信单元803可以是收发器。存储单元801可以是存储器。
当处理单元802为处理器，通信单元803为收发器，存储单元801为存储器时，本发明实施例所涉及的用户设备可以为图9所示的用户设备。
参阅图9所示，该用户设备900可包括：处理器902、收发器903、存储器901以及总线904。其中，收发器903、处理器902以及存储器901通过总线904相互连接；总线904可以是外设部件互连标准(peripheral component interconnect，简称PCI)总线或扩展工业标准结构(extended industry standard architecture，简称EISA)总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图9中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
结合本申请公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块或单元组成，软件模块或单元可以被存放于随机存取存储器(Random Access Memory，RAM)、闪存、只读存储器(Read Only Memory，ROM)、可擦除可编程只读存储器(Erasable Programmable ROM，EPROM)、电可擦可编程只读存储器(Electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、只读光盘(CD-ROM)或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于用户设备中。当然，处理器和存储介质也可以作为分立组件存在于用户设备中。
图10示出了上述实施例中所涉及的核心网实体的一种可能的结构示意图，参阅图10所示，该核心网实体1000可包括：通信单元1001和处理单元1002。其中，这些单元可以执行上述方法示例中核心网实体如AMF的相应功能，例如，通信单元1001，用于和第一基站连接，通过所述第一基站接入网络的用户设备UE处于无线资源连接非激活态RRC Inactive state；所述通信单元1001，还用于接收所述UE通过第二基站发送的第一请求消息，或者，接收另一核心网实体发送的第二请求消息，其中，所述第二请求消息是所述另一核心网实体接收到所述UE通过第二基站发送的第一请求消息时，由所述另一核心网实体向所述核心网实体发送的，所述第二基站不支持所述RRC Inactive state；所述处理单元1002，用于调用所述通信单元1001释放与所述第一基站之间的连接。
可选的，所述第一基站可以为所述UE移动前接入的网络对应的基站，所述第二基站可以为所述UE移动后接入的网络对应的基站。
可选的，所述第一请求消息包括指示信息，所述指示信息指示所述UE由所述RRC Inactive state切换为空闲态IDLE state。
可选的，所述处理单元1002，还用于调用通信单元1001执行协议数据单元会话去激 活流程PDU session deactivation procedure。
可选的，所述第一请求消息为位置更新请求、附着请求、注册请求或业务请求。
可选的，所述第一请求消息还包括UE能力信息，所述UE能力信息指示所述UE支持所述RRC Inactive state。
可选的，所述第一基站支持所述RRC Inactive state。
可选的，所述核心网实体可以为MME或AMF或SGSN等等，第二核心网实体可以为AMF。
需要说明的是，本发明实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。本发明实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
在采用集成的单元的情况下，图11示出了上述实施例中所涉及的核心网实体的另一种可能的结构示意图，如图11所示，该核心网实体1100可包括：处理单元1102和通信单元1103。处理单元1102可用于对核心网实体的动作进行控制管理，例如，处理单元1102用于支持核心网实体执行图3中的过程306、307，图4中的过程405、406等等，和/或用于本文所描述的技术的其它过程。通信单元1103用于支持核心网实体与其他网络实体的通信，例如与图2至图5中示出的功能单元或网络实体之间的通信。核心网实体还可以包括存储单元1101，用于存储核心网实体的程序代码(操作指令)和数据。
其中，处理单元1102可以是处理器或控制器，例如可以是中央处理器(Central Processing Unit，CPU)，通用处理器，数字信号处理器(Digital Signal Processor，DSP)，专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信单元1103可以是收发器。存储单元1101可以是存储器。
当处理单元1102为处理器，通信单元1103为收发器，存储单元1101为存储器时，本发明实施例所涉及的核心网实体可以为图12所示的核心网实体。
参阅图12所示，该核心网实体1200可包括：处理器1202、收发器1203、存储器1201以及总线1204。其中，收发器1203、处理器1202以及存储器1201通过总线1204相互连接；总线1204可以是外设部件互连标准(peripheral component interconnect，简称PCI)总线或扩展工业标准结构(extended industry standard architecture，简称EISA)总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图12中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
结合本申请公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块或单元组成，软件模块或单元可以被存放于随机存取存储器(Random Access Memory，RAM)、闪存、只读存储器(Read Only Memory，ROM)、可擦除可编程只读存储器(Erasable Programmable  ROM，EPROM)、电可擦可编程只读存储器(Electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、只读光盘(CD-ROM)或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于核心网实体中。当然，处理器和存储介质也可以作为分立组件存在于核心网实体中。
在实现过程中，上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
还应理解，本文中涉及的第一、第二、第三、第四以及各种数字编号仅为描述方便进行的区分，并不用来限制本发明实施例的范围。
应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本发明实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各种说明性逻辑块(illustrative logical block)和步骤(step)，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的***、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的***、装置、用户设备、核心网实体和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个***，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (40)

  1. 一种连接管理方法，其特征在于，包括：
    用户设备UE通过第一基站接入网络，所述UE处于无线资源连接非激活态RRC Inactive state；
    所述UE通过第二基站接入网络，所述第二基站不支持所述RRC Inactive state；
    所述UE通过所述第二基站向第一核心网实体发送第一请求消息，以使所述第一核心网实体根据所述第一请求消息释放与所述第一基站的连接；或者，
    所述UE通过所述第二基站向第一核心网实体发送第一请求消息，以使所述第一核心网实体向第二核心网实体发送第二请求消息，并由所述第二核心网实体根据所述第二请求消息释放与所述第一基站的连接；
    其中，所述第一核心网实体为所述第二基站接入的网络的核心网实体，所述第二核心网实体为所述第一基站接入的网络的核心网实体。
  2. 根据权利要求1所述的方法，其特征在于，在所述UE通过所述第二基站向第一核心网实体发送第一请求消息之前，所述方法还包括：
    所述UE接收所述第二基站发送的广播消息；
    所述UE根据所述广播消息确定所述第二基站不支持所述RRC Inactive state。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一基站为所述UE移动前接入的网络对应的基站，所述第二基站为所述UE移动后接入的网络对应的基站。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，在所述UE通过所述第二基站向第一核心网实体发送第一请求消息之前，所述方法还包括：
    所述UE将所述UE的状态由所述RRC Inactive state切换为空闲态IDLE state。
  5. 根据权利要求1-4任一项所述的方法，其特征在于，所述第一请求消息包括指示信息，所述指示信息指示所述UE由所述RRC Inactive state切换为空闲态IDLE state。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，所述第一请求消息为位置更新请求、附着请求、注册请求或业务请求。
  7. 根据权利要求1-6任一项所述的方法，其特征在于，所述第一请求消息还包括UE能力信息，所述UE能力信息指示所述UE支持所述RRC Inactive state。
  8. 根据权利要求1-7任一项所述的方法，其特征在于，所述第一基站支持所述RRC Inactive state。
  9. 根据权利要求1-8任一项所述的方法，其特征在于，所述第一核心网实体为移动管理实体MME或接入和移动性管理功能实体AMF，所述第二核心网实体为AMF。
  10. 一种连接管理方法，其特征在于，包括：
    核心网实体和第一基站连接，通过所述第一基站接入网络的用户设备UE处于无线资源连接非激活态RRC Inactive state；
    所述核心网实体接收所述UE通过第二基站发送的第一请求消息，或者，所述核心网实体接收另一核心网实体发送的第二请求消息，其中，所述第二请求消息是所述另一核心网实体接收到所述UE通过第二基站发送的第一请求消息时，由所述另一核心网实体向所 述核心网实体发送的，所述第二基站不支持所述RRC Inactive state；
    所述核心网实体释放与所述第一基站之间的连接。
  11. 根据权利要求10所述的方法，其特征在于，所述第一基站为所述UE移动前接入的网络对应的基站，所述第二基站为所述UE移动后接入的网络对应的基站。
  12. 根据权利要求10或11所述的方法，其特征在于，所述第一请求消息包括指示信息，所述指示信息指示所述UE由所述RRC Inactive state切换为空闲态IDLE state。
  13. 根据权利要求10-12任一项所述的方法，其特征在于，在所述核心网实体接收所述UE通过第二基站发送的第一请求消息之后，或者，所述核心网实体接收另一核心网实体发送的第二请求消息之后，所述方法还包括：
    所述核心网实体执行协议数据单元会话去激活流程PDU session deactivation procedure。
  14. 根据权利要求10-13任一项所述的方法，其特征在于，所述第一请求消息为位置更新请求、附着请求、注册请求或业务请求。
  15. 根据权利要求10-14任一项所述的方法，其特征在于，所述第一请求消息还包括UE能力信息，所述UE能力信息指示所述UE支持所述RRC Inactive state。
  16. 根据权利要求10-15任一项所述的方法，其特征在于，所述第一基站支持所述RRC Inactive state。
  17. 根据权利要求10-16任一项所述的方法，其特征在于，所述核心网实体为移动管理实体MME或接入和移动性管理功能实体AMF，所述另一核心网实体为AMF。
  18. 一种用户设备UE，其特征在于，包括：通信单元；
    所述通信单元，用于通过第一基站接入网络，所述UE处于无线资源连接非激活态RRC Inactive state；
    所述通信单元，还用于通过第二基站接入网络，所述第二基站不支持所述RRC Inactive state；
    所述通信单元，还用于通过所述第二基站向第一核心网实体发送第一请求消息，以使所述第一核心网实体根据所述第一请求消息释放与所述第一基站的连接；或者，
    所述通信单元，还用于通过所述第二基站向第一核心网实体发送第一请求消息，以使所述第一核心网实体向第二核心网实体发送第二请求消息，并由所述第二核心网实体根据所述第二请求消息释放与所述第一基站的连接；
    其中，所述第一核心网实体为所述第二基站接入的网络的核心网实体，所述第二核心网实体为所述第一基站接入的网络的核心网实体。
  19. 根据权利要求18所述的UE，其特征在于，所述UE还包括：处理单元；
    所述通信单元，还用于接收所述第二基站发送的广播消息；
    所述处理单元，用于根据所述广播消息确定所述第二基站是否支持所述RRC Inactive state。
  20. 根据权利要求18或19所述的UE，其特征在于，所述第一基站为所述UE移动前接入的网络对应的基站，所述第二基站为所述UE移动后接入的网络对应的基站。
  21. 根据权利要求18-20任一项所述的UE，其特征在于，
    所述处理单元，还用于将所述UE的状态由所述RRC Inactive state切换为空闲态IDLE  state。
  22. 根据权利要求18-21任一项所述的UE，其特征在于，所述第一请求消息包括指示信息，所述指示信息指示所述UE由所述RRC Inactive state切换为空闲态IDLE state。
  23. 根据权利要求18-22任一项所述的UE，其特征在于，所述第一请求消息为位置更新请求、附着请求、注册请求或业务请求。
  24. 根据权利要求18-23任一项所述的UE，其特征在于，所述第一请求消息还包括UE能力信息，所述UE能力信息指示所述UE支持所述RRC Inactive state。
  25. 根据权利要求18-24任一项所述的UE，其特征在于，所述第一基站支持所述RRC Inactive state。
  26. 根据权利要求18-25任一项所述的UE，其特征在于，所述第一核心网实体为移动管理实体MME或接入和移动性管理功能实体AMF，所述第二核心网实体为AMF。
  27. 一种核心网实体，其特征在于，包括：通信单元和处理单元；
    所述通信单元，用于和第一基站连接，通过所述第一基站接入网络的用户设备UE处于无线资源连接非激活态RRC Inactive state；
    所述通信单元，还用于接收所述UE通过第二基站发送的第一请求消息，或者，接收另一核心网实体发送的第二请求消息，其中，所述第二请求消息是所述另一核心网实体接收到所述UE通过第二基站发送的第一请求消息时，由所述另一核心网实体向所述核心网实体发送的，所述第二基站不支持所述RRC Inactive state；
    所述处理单元，用于调用所述通信单元释放与所述第一基站之间的连接。
  28. 根据权利要求27所述的核心网实体，其特征在于，所述第一基站为所述UE移动前接入的网络对应的基站，所述第二基站为所述UE移动后接入的网络对应的基站。
  29. 根据权利要求27或28所述的核心网实体，其特征在于，所述第一请求消息包括指示信息，所述指示信息指示所述UE由所述RRC Inactive state切换为空闲态IDLE state。
  30. 根据权利要求28-29任一项所述的核心网实体，其特征在于，
    所述处理单元，还用于调用所述通信单元执行协议数据单元会话去激活流程PDU session deactivation procedure。
  31. 根据权利要求28-30任一项所述的核心网实体，其特征在于，所述第一请求消息为位置更新请求、附着请求、注册请求或业务请求。
  32. 根据权利要求28-31任一项所述的核心网实体，其特征在于，所述第一请求消息还包括UE能力信息，所述UE能力信息指示所述UE支持所述RRC Inactive state。
  33. 根据权利要求28-32任一项所述的核心网实体，其特征在于，所述第一基站支持所述RRC Inactive state。
  34. 根据权利要求28-33任一项所述的核心网实体，其特征在于，所述核心网实体为移动管理实体MME或接入和移动性管理功能实体AMF，所述另一核心网实体为AMF。
  35. 一种用户设备UE，其特征在于，包括：
    处理器和存储器；
    通过调用所述存储器存储的操作指令，所述处理器被设置使得所述用户设备执行如权利要求1-9任意一项所述的方法。
  36. 一种核心网实体，其特征在于，包括：
    处理器和存储器；
    通过调用所述存储器存储的操作指令，所述处理器被设置使得所述核心网实体执行如权利要求10-17任意一项所述的方法。
  37. 一种***，其特征在于，包括如权利要求18-26任一所述的用户设备和如权利要求27-34任一所述的的核心网实体。
  38. 一种计算机程序，包括指令，当其在计算机上运行时，使得计算机执行如权利要求1-9任一项所述的方法，或者执行如权利要求10-17任一项所述的方法。
  39. 一种计算机可读存储介质，包括指令，当所述指令在计算机上运行时，使得计算机执行如权利要求1-9任一项所述的方法，或者执行如权利要求10-17任一项所述的方法。
  40. 一种包含指令的计算机程序产品，当所述指令在计算机上运行时，使得计算机执行如权利要求1-9任一项所述的方法，或者执行如权利要求10-17任一项所述的方法。
PCT/CN2017/102808 2017-09-21 2017-09-21 连接管理方法、用户设备、核心网实体及*** WO2019056279A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
US16/649,377 US11291069B2 (en) 2017-09-21 2017-09-21 Connection management method, user equipment, core network entity, and system
PCT/CN2017/102808 WO2019056279A1 (zh) 2017-09-21 2017-09-21 连接管理方法、用户设备、核心网实体及***
CN201780088304.XA CN110431913B (zh) 2017-09-21 2017-09-21 连接管理方法、用户设备、核心网实体及***
EP17925692.0A EP3678449B1 (en) 2017-09-21 2017-09-21 Connection management method and user equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/102808 WO2019056279A1 (zh) 2017-09-21 2017-09-21 连接管理方法、用户设备、核心网实体及***

Publications (1)

Publication Number Publication Date
WO2019056279A1 true WO2019056279A1 (zh) 2019-03-28

Family

ID=65809911

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/102808 WO2019056279A1 (zh) 2017-09-21 2017-09-21 连接管理方法、用户设备、核心网实体及***

Country Status (4)

Country Link
US (1) US11291069B2 (zh)
EP (1) EP3678449B1 (zh)
CN (1) CN110431913B (zh)
WO (1) WO2019056279A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113973260A (zh) * 2020-07-22 2022-01-25 大唐移动通信设备有限公司 上行信号定位的方法、通信基站和测量基站及ue

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2019145858A (ja) * 2016-06-30 2019-08-29 シャープ株式会社 端末装置、制御装置、及び通信制御方法
US11889298B2 (en) * 2017-11-20 2024-01-30 Telefonaktiebolaget Lm Ericsson (Publ) Security gateway selection in hybrid 4G and 5G networks
CN110149728B (zh) * 2018-02-13 2020-09-29 华为技术有限公司 无线资源控制rrc状态转换的方法、通信装置、网络设备以及计算机存储介质
WO2019165629A1 (zh) * 2018-03-01 2019-09-06 华为技术有限公司 会话管理方法及装置、通信***
EP4013181A4 (en) * 2019-08-07 2023-08-09 Mitsubishi Electric Corporation COMMUNICATION SYSTEM, COMMUNICATION TERMINAL AND NETWORK
CN113364721B (zh) * 2020-03-04 2023-06-30 大唐移动通信设备有限公司 一种sctp连接管理方法及装置
WO2022028437A1 (zh) * 2020-08-03 2022-02-10 华为技术有限公司 一种通信方法、装置以及***
EP3968696A1 (en) * 2020-09-15 2022-03-16 Nokia Technologies Oy Ng based context release and data forwarding for multi-hop mobility

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160309379A1 (en) * 2013-12-06 2016-10-20 Interdigital Patent Holdings, Inc. Layered connectivity in wireless systems
CN106658758A (zh) * 2017-02-10 2017-05-10 北京小米移动软件有限公司 状态转换方法、状态保持方法、装置及用户设备

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102238664B (zh) 2010-04-23 2014-10-22 中兴通讯股份有限公司 基站切换中无线资源连接重建拒绝的方法和***
JP6034491B2 (ja) * 2012-08-07 2016-11-30 ▲ホア▼▲ウェイ▼技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ． ハンドオーバー処理方法および基地局
CN105325030A (zh) * 2013-06-21 2016-02-10 三菱电机株式会社 通信方法及通信装置
US11026136B2 (en) * 2014-03-07 2021-06-01 Parallel Wireless, Inc. Handovers with simplified network topology
US10512106B2 (en) * 2016-08-12 2019-12-17 Electronics And Telecommunications Research Institute State transition method based on random access procedure in communication system
RU2727163C1 (ru) * 2016-09-30 2020-07-21 Телефонактиеболагет Лм Эрикссон (Пабл) Осведомленность базовой сети о состоянии оборудования пользователя, ue
WO2018086600A1 (en) * 2016-11-11 2018-05-17 Chou Chie Ming Data packet delivery in rrc inactive state
EP3560241A4 (en) * 2016-12-21 2020-11-18 FG Innovation Company Limited STATE TRANSITION PROCEDURE OF A WIRELESS COMMUNICATION SYSTEM
EP3370448B1 (en) * 2017-03-01 2020-10-28 HTC Corporation Device and method for handling a temporary user equipment capability
US11184791B2 (en) * 2017-03-25 2021-11-23 Lg Electronics Inc. Access control method and device for supporting same
WO2018193496A1 (ja) * 2017-04-17 2018-10-25 富士通株式会社 無線端末、基地局、無線通信システム及び無線通信方法
CN109548109B (zh) 2017-08-14 2021-03-09 电信科学技术研究院 一种ue和网络状态不匹配的处理方法及装置、存储介质

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160309379A1 (en) * 2013-12-06 2016-10-20 Interdigital Patent Holdings, Inc. Layered connectivity in wireless systems
CN106658758A (zh) * 2017-02-10 2017-05-10 北京小米移动软件有限公司 状态转换方法、状态保持方法、装置及用户设备

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"23.501 §5.3 and 5.4: AMF UE state information terminology update", SA WG2 MEETING #122E S2-176773, 15 September 2017 (2017-09-15), XP051336060 *
"TS 23.502: Fallback to CN paging Upon RAN Paging Failure", SA WG2 MEETING #122 BIS S2-175556, 25 August 2017 (2017-08-25), XP051325407 *
See also references of EP3678449A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113973260A (zh) * 2020-07-22 2022-01-25 大唐移动通信设备有限公司 上行信号定位的方法、通信基站和测量基站及ue
CN113973260B (zh) * 2020-07-22 2023-08-01 大唐移动通信设备有限公司 上行信号定位的方法、通信基站和测量基站及ue

Also Published As

Publication number Publication date
EP3678449B1 (en) 2022-06-01
US11291069B2 (en) 2022-03-29
EP3678449A4 (en) 2020-08-26
CN110431913A (zh) 2019-11-08
EP3678449A1 (en) 2020-07-08
US20200275515A1 (en) 2020-08-27
CN110431913B (zh) 2022-02-25

Similar Documents

Publication Publication Date Title
WO2019056279A1 (zh) 连接管理方法、用户设备、核心网实体及***
JP6908720B2 (ja) コアネットワーク制御プレーンデバイス選択方法および装置
JP2021524209A (ja) セッション管理の方法、装置、およびシステム
EP3577952B1 (en) Method and system for selection of an access and mobility management function in an access network environment
WO2018202138A1 (zh) 通信方法及相关设备
JP7104143B2 (ja) 通信方法および通信装置
US11483898B2 (en) Session management method and session management network element
CN109644341B (zh) 用于通信的方法、装置、通信设备、无线电接入***和计算机可读介质
US20210022203A1 (en) Method for deactivating user plane connection and network entity for controlling user plane connection deactivation in network
JP7253565B2 (ja) 通信方法及び通信装置
WO2020057625A1 (zh) 网关切换方法、网关重选方法和通信装置
WO2022007484A1 (zh) 重定向方法、网络设备、终端设备及可读存储介质
EP3923630A1 (en) Communication method and apparatus
WO2018214762A1 (zh) 一种获取寻呼参数的方法及装置
US11622403B2 (en) Data sending method, apparatus, and system
WO2021160096A1 (zh) 一种私网签约信息更新方法及装置
WO2023051288A1 (zh) 一种隧道管理方法、装置及***
WO2022206393A1 (zh) 通信方法及装置
WO2022068901A1 (zh) 网络接入引导方法、装置及电子设备
WO2022165752A1 (zh) 状态转换方法、装置、设备及存储介质
WO2018205154A1 (zh) 一种数据处理方法及终端设备、网络设备
WO2019096199A1 (zh) 通信方法、装置及计算机可读存储介质
WO2021088054A1 (zh) 一种通信方法及装置
WO2022099516A1 (zh) 通信方法、装置和***
WO2018082039A1 (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: 17925692

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: 2017925692

Country of ref document: EP

Effective date: 20200331