WO2018205114A1 - 一种状态切换方法及装置 - Google Patents
一种状态切换方法及装置 Download PDFInfo
- Publication number
- WO2018205114A1 WO2018205114A1 PCT/CN2017/083515 CN2017083515W WO2018205114A1 WO 2018205114 A1 WO2018205114 A1 WO 2018205114A1 CN 2017083515 W CN2017083515 W CN 2017083515W WO 2018205114 A1 WO2018205114 A1 WO 2018205114A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- terminal device
- indication information
- information
- network element
- mobility management
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/16—Discovering, processing access restriction or access information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
- H04W28/18—Negotiating wireless communication parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/02—Buffering or recovering information during reselection ; Modification of the traffic flow during hand-off
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
-
- 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
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/08—Mobility data transfer
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
- H04W8/20—Transfer of user or subscriber data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/04—Large scale networks; Deep hierarchical networks
- H04W84/042—Public Land Mobile systems, e.g. cellular systems
Definitions
- the present application relates to the field of communications technologies, and in particular, to a state switching method and apparatus.
- the fifth generation (English: the 5th Generation, 5G for short) communication system defines a communication mode: only the mobile terminal initiated connection (English: Mobile Initiated Connection Only, MICO) mode.
- the terminal negotiates the MICO mode with the network side during the registration process.
- the network side may also instruct the terminal to register as the "public land mobile network (PLMN)" ("all PLMN") registration area.
- PLMN public land mobile network
- all PLMN all PLMN
- the network side rejects any request for transmitting downlink data (including user plane data and control plane signaling).
- the network side does not initiate a paging procedure for the terminal, and the terminal does not need to listen for paging (ie, a paging process).
- the "all PLMN" registration area it means that the UE has already registered in the entire PLMN network area, and the terminal does not need to re-register to the PLMN network because of its mobility, that is, the terminal does not need to initiate a mobility registration update. Type registration process.
- a terminal transits a terminal from an idle state to a connected state through a service request process, and can also activate a terminal PDU session through a service request (ie, service request) process to transmit Data business.
- a service request ie, service request
- the terminal may have left the source access and the mobile.
- the service area of the Access and Mobility Management Function (AMF) entity which will cause the following problem: there is no context (ie context) of the terminal on the new AMF entity, which will determine that the service request process fails and requires the terminal to be re-enabled. Conduct the registration request process. This increases the signaling flow between the terminal and the network, introduces unnecessary signaling overhead, and increases the delay of the terminal transitioning from the idle state to the connected state.
- AMF Access and Mobility Management Function
- the present application provides a state switching method and apparatus for solving the problem that the signaling overhead of the terminal fails to be transmitted in the MICO mode.
- the embodiment of the present application provides a state switching method, where the first mobility management network element acquires indication information and identification information of the terminal device from a terminal device, where the indication information is used to indicate The terminal device is in the mobile terminal only initiates the connection MICO mode; if the context information of the terminal device does not exist in the first mobility management network element, the first mobility management network element according to the indication information and the The identification information is requested by the second mobility management network element.
- the first mobility management network element After the first mobility management network element obtains the context information of the terminal device, the first mobility management network element does not need to re-initiate the new registration request process, which reduces the signaling interaction between the terminal device and the network, and reduces the terminal device from the idle state. The delay to switch to the connected state.
- the first mobility management network element acquires indication information and the terminal from the terminal device.
- the identifier information of the device includes: the first mobility management network element receives a request message from the base station, where the request message carries the indication information and the identifier information.
- the request message is a service request message or a registration request message.
- the indication information and the identification information of the terminal device are obtained through the service request message or the registration request message, so that the acquisition manner is more flexible.
- the indication information is a service type of the service request message, and the service type is a MICO data service.
- the manner in which the first mobility management network element obtains the indication information is more flexible by using the service type in the service request message as the indication information.
- the indication information is a registration type of the registration request message, and the registration type is a MICO data registration.
- the manner in which the first mobility management network element acquires the indication information is more flexible.
- the registration request message also carries a packet data unit PDU session identifier to be activated.
- the registration request message carries the PDU session identifier, which saves signaling resources.
- the registration request message further carries an activation flag, which is used to indicate that the terminal device needs to send uplink data.
- the activation request flag is carried in the registration request message, so that the first mobility management network element more specifically aims the UE to send the registration request message.
- the identification information is used to uniquely identify the terminal device globally.
- the indication information is further used to indicate that the registration area of the terminal device is a full public land mobile network PLMN registration area; or the indication information includes first indication information and second indication information, The first indication information is used to indicate that the terminal device is in a mobile terminal only to initiate a connection MICO mode, and the second indication information is used to indicate that the registration area of the terminal device is a full public land mobile network PLMN registration area.
- the above design provides an indication of the indication information, making the design more flexible.
- the method may further include: the first mobility management network element acquiring, from the terminal device, an identifier of a packet data unit PDU session to be activated; the first mobility management network element Determining, according to the identifier of the PDU session to be activated, a PDU session corresponding to the identifier of the PDU session for the terminal device.
- the embodiment of the present application provides a state switching method, including: the terminal device learns the terminal setting The mobile terminal initiates the connection to the MICO mode; when the terminal device needs to send the uplink data, the terminal device sends the indication information and the identifier information of the terminal device to the first mobility management network element, where the indication information is used. The device is instructed to be in the MICO mode.
- the terminal device sends the indication information and the identification information of the terminal device to the first mobility management network element, so that the first mobility management network element can determine the second mobility management network element that acquires the context information of the terminal device.
- the new registration request process does not need to be re-initiated, the signaling interaction between the terminal device and the network is reduced, and the delay of the terminal device transitioning from the idle state to the connected state is reduced.
- the terminal device sends the indication information to the first mobility management network element, where the terminal device sends a radio resource control RRC message to the first mobility management network element by using the base station, where The indication information is carried in the RRC message.
- the terminal device sends the identifier information of the terminal device to the first mobility management network element, where the terminal device sends the radio resource to the first mobility management network element by using the base station. And controlling the RRC message, where the RRC message carries the identifier information of the terminal device.
- the identification information is used to uniquely identify the terminal device globally.
- the above design provides an indication of the indication information, making the design more flexible.
- the indication information and the identification information of the terminal device are obtained through the service request message or the registration request message, so that the acquisition manner is more flexible.
- the manner in which the first mobility management network element obtains the indication information is more flexible by using the service type in the service request message as the indication information.
- the indication information is a registration type of the registration request message, and the registration type is a MICO data registration.
- the manner in which the first mobility management network element acquires the indication information is more flexible.
- the registration request message also carries a packet data unit PDU session identifier to be activated.
- the registration request message carries the PDU session identifier, which saves signaling resources.
- the registration request message further carries an activation flag, which is used to indicate that the terminal device needs to send uplink data.
- the embodiment of the present application provides a state switching method, including: a first mobility management network element from the end Obtaining, by the terminal device, an identifier of the packet data unit PDU session to be activated and the identifier information of the terminal device; if the context information of the terminal device does not exist in the first mobility management network element, the first mobility management The network element requests the context information from the second mobility management network element according to the identifier information, and the first mobility management network element activates the terminal device according to the identifier of the PDU session to be activated.
- the PDU session corresponding to the identity of the PDU session.
- the first mobility management network element After the first mobility management network element obtains the context information of the terminal device, the first mobility management network element does not need to re-initiate the new registration request process, which reduces the signaling interaction between the terminal device and the network, and reduces the terminal device from the idle state. The delay to switch to the connected state.
- the PDU session corresponding to the identifier of the PDU session is activated by the terminal device, where the first mobility management network element sends the identifier of the PDU session to be activated to the session management network element. So that the session management network element activates the PDU session.
- the first mobility management network element acquires, from the terminal device, the identifier of the packet data unit PDU session to be activated and the identifier information of the terminal device, including: the first mobility management network element
- the base station receives the registration request message, where the registration request message carries the identifier of the PDU session to be activated and the terminal device identification information.
- the registration request message further carries an activation flag, where the activation flag is used to indicate that the terminal device needs to send uplink data.
- the embodiment of the present application provides a state switching device, where the state switching device is applied to a first mobility management network element, where the device includes:
- An obtaining module configured to acquire, from the terminal device, the indication information and the identifier information of the terminal device, where the indication information is used to indicate that the terminal device is in a mobile terminal only initiates a connection MICO mode;
- a processing module configured to determine that context information of the terminal device does not exist in the first mobility management network element
- a sending module configured to: when the processing module determines that the context information of the terminal device does not exist in the first mobility management network element, according to the indication information and the identifier information, to the second mobility management The network element requests the context information.
- the acquiring module is specifically configured to: receive a request message from a base station, where the request message carries the indication information and the identifier information.
- the request message is a service request message or a registration request message.
- the indication information is a service type of the service request message, and the service type is a MICO data service.
- the indication information is a registration type of the registration request message, and the registration type is a MICO data registration.
- the registration request message also carries a packet data unit PDU session identifier to be activated.
- the registration request message further carries an activation flag, which is used to indicate that the terminal device needs to send uplink data.
- the identification information is used to uniquely identify the terminal device globally.
- the processing module is further configured to: determine, according to the indication information, that the context information needs to be requested; and the first mobility management network element determines the first according to the identifier information.
- Two mobility management The sending module is configured to send a UE context request to the second mobility management network element.
- the indication information is further used to indicate that the registration area of the terminal device is a full public land mobile network PLMN registration area; or the indication information includes first indication information and second indication information, The first indication information is used to indicate that the terminal device is in a mobile terminal only to initiate a connection MICO mode, and the second indication information is used to indicate that the registration area of the terminal device is a full public land mobile network PLMN registration area.
- the obtaining module is further configured to acquire, from the terminal device, an identifier of a packet data unit PDU session to be activated; the processing module is further configured to: according to the PDU session to be activated And identifying, for the terminal device, a PDU session corresponding to the identifier of the PDU session.
- the fifth aspect is based on the same inventive concept as the method embodiment provided by the second aspect.
- the embodiment of the present application provides a state switching device, where the device is applied to a terminal device, including:
- the sending module is configured to send, by using a base station, a radio resource control RRC message to the first mobility management network element, where the RRC message carries the indication information.
- the sending module is configured to send, by using a base station, a radio resource control RRC message to the first mobility management network element, where the RRC message carries the identifier information of the terminal device.
- the identification information is used to uniquely identify the terminal device globally.
- the indication information is further used to indicate that the registration area of the terminal device is a full public land mobile network PLMN registration area; or the indication information includes first indication information and second indication information, The first indication information is used to indicate that the terminal device is in a mobile terminal only to initiate a connection MICO mode, and the second indication information is used to indicate that the registration area of the terminal device is a full public land mobile network PLMN registration area.
- the indication information is a registration type of the registration request message, and the registration type is a MICO data registration.
- the registration request message also carries a packet data unit PDU session identifier to be activated.
- the registration request message further carries an activation flag, which is used to indicate that the terminal device needs to send uplink data.
- the sixth aspect is based on the same inventive concept as the method embodiment provided by the third aspect.
- the embodiment of the present application provides a state switching device, where the device is applied to the first mobility management network element, including:
- An acquiring module configured to acquire, from a terminal device, an identifier of a packet data unit PDU session to be activated and identifier information of the terminal device, where the processing module is configured to determine that the terminal does not exist in the first mobility management network element Context information of the device, the sending module, configured to: when the processing module determines that the context information of the terminal device does not exist in the first mobility management network element, according to the identifier information, to the second mobility management The network element requests the context information.
- the processing module is further configured to activate, according to the identifier of the PDU session to be activated, the terminal device The PDU session corresponding to the identifier of the PDU session.
- the processing module in the PDU session corresponding to the identifier of the PDU session, is used to: the sending module sends the PDU to be activated to the session management network element. An identification of the session such that the session management network element activates the PDU session.
- the acquiring module is specifically configured to: receive a registration request message from the base station, where the registration request message carries an identifier of the PDU session to be activated and the terminal device identification information.
- the registration request message further carries an activation flag, where the activation flag is used to indicate that the terminal device needs to send uplink data.
- the embodiment of the present application provides a mobility management network element, including: a communication interface, a processor, and a memory, where the communication interface is used for sending and receiving data, and the memory is used to store a software program, where the processor uses The method of the first aspect or the first aspect, or the third aspect, or any one of the foregoing third aspects, is provided for reading the software program stored in the memory.
- an embodiment of the present application provides a terminal device, including: a transceiver, a processor, and a memory, where the transceiver is configured to send and receive data, the memory is used to store a software program, and the processor is configured to read A software program stored in the memory and implementing the method provided by the second aspect or any one of the above second aspects.
- the embodiment of the present application further provides a computer storage medium, where the software program stores a software program, where the software program can implement the first aspect or the first one when being read and executed by one or more processors A method provided by any one of the aspects, or a method provided by implementing the design of any one of the second aspect or the second aspect, or the method provided by any one of the third aspect or the third aspect.
- an embodiment of the present application provides a computer program product comprising instructions that, when run on a computer, cause the computer to perform the above method.
- FIG. 1 is a schematic diagram of a sliced 5G network architecture provided by an embodiment of the present application.
- FIG. 2 is a schematic flowchart of a first state transition method according to an embodiment of the present application
- FIG. 3 is a schematic flowchart of a second state transition method according to an embodiment of the present disclosure
- FIG. 4 is a schematic flowchart of a third state transition method according to an embodiment of the present application.
- FIG. 5 is a schematic flowchart of a fourth state transition method according to an embodiment of the present disclosure.
- FIG. 7 is a schematic flowchart of a sixth state transition method according to an embodiment of the present disclosure.
- FIG. 9 is a schematic structural diagram of a mobility management network element according to an embodiment of the present disclosure.
- FIG. 10 is a schematic structural diagram of another mobility management network element according to an embodiment of the present disclosure.
- FIG. 11 is a schematic structural diagram of a terminal device according to an embodiment of the present application.
- FIG. 12 is a schematic structural diagram of another terminal device according to an embodiment of the present disclosure.
- the embodiments of the present application can be applied to a 5G communication system or long term evolution (English: long term evolution, Abbreviation: LTE) system and other mobile communication systems.
- 5G communication system can be applied to applications in various industries, such as mobile broadband, multimedia, machine type communication (English: machine type communication, referred to as: MTC), industrial control, and intelligent transportation system (English: intelligent transportation system, referred to as: ITS) and so on.
- the 5G network is constructed in a flexible manner, specifically separating the network functions, that is, the control plane (English: Control Plane, CP: abbreviation: CP) and the user plane (English: User Plane, abbreviation: UP) function separation, movement in the CP Sexual management (English: Mobile Management, referred to as: MM) function and session management (English: session management, referred to as: SM) function separation.
- Network Slice technology is proposed in 5G.
- Network slicing technology is to cut a physical network into multiple virtual end-to-end networks.
- Each virtual network (including devices, access technologies, transmission paths and core networks in the network) is logically independent.
- Each network slice is instantiated by a separate network function or combination of functions with different functional characteristics for different needs and services.
- the proposed network segmentation enables different users and user groups to flexibly and dynamically define and customize network capabilities according to their different application scenarios and requirements.
- a network slice includes a control plane function (English: control plane function, CPF for short) entity and a user plane function (English: user plane function, abbreviated as: UPF) entity.
- the CPF entity mainly completes the access control and mobility management functions (AMF) of the access authentication and mobility management functions of the terminal device, and the establishment of the user plane transmission path. Session management functions such as release and change (English: session management function, SMF for short).
- the UPF entity mainly performs functions such as routing and forwarding of user plane data.
- FIG. 1 is a schematic diagram of a sliced 5G network architecture according to an embodiment of the present application.
- the 5G network architecture provided in the embodiment of the present application mainly includes the following network entity functions:
- (Wireless) Access Network (R) AN A network consisting of at least one 5G-RAN node implementing wireless physical layer functions, resource scheduling and radio resource management, radio access control, and mobility management functions.
- the 5G-RAN is connected to the UPF through the user plane interface N3, and is used to transmit data of the terminal device.
- the 5G-RAN establishes a control plane signaling connection through the control plane interface N2 and the AMF, and is used to implement functions such as radio access bearer control.
- the 5G-RAN node may be a Global System for Mobile communication (GSM) system or a base station in a code division multiple access (CDMA) system (English: Base Transceiver) Station, abbreviated as: BTS), may also be a base station (NodeB) in a Wideband Code Division Multiple Access (WCDMA) system, or an evolved base station in an LTE system (English: Evolutional Node B, referred to as eNB or eNodeB), or a base station device, a small base station device, a wireless access node (WiFi AP), and a wireless interoperability microwave access base station (English: Worldwide Interoperability for Microwave Access Base Station) in the future 5G network. : WiMAX BS), etc., this application is not limited thereto.
- AMF Mainly responsible for UE authentication, UE mobility management, network slice selection, SMF selection and other functions.
- the AMF acts as an anchor for the N1 and N2 signaling connections and provides a route for the SMF to provide N1/N2SM messages.
- the AMF maintains and manages the status information of the user equipment (English: User Equipment, UE for short).
- SMF Mainly responsible for all control plane functions of UE session management, including UPF selection, Internet Protocol (IP) address allocation, Quality of Service (QoS: QoS) management, (from PCF) ) Get PCC strategies, etc.
- IP Internet Protocol
- QoS QoS
- PCF PCF
- UPF As the anchor point of the protocol data unit (English: Protocol Data Unit, PDU for short), it is responsible for data packet filtering, data transmission/transfer, rate control, and accounting information generation for the user equipment.
- PDU Protocol Data Unit
- the policy control function (English: Policy Rules Function, PCF) can also be called the Policy and Charging Rules Function (English: Policy and Charging Rules Function, PCRF).
- PCF or PCRF is responsible for policy control decisions and flow-based charging control.
- User Data Management (English: User Data Management, UDM for short) can be called Home Subscriber Server (English: Home Subscriber Server, HSS for short).
- the user data management entity English can also correspond to Subscriber Data Management, and the abbreviation can also correspond to SDM.
- UDM, SDM, or HSS are used to help operators achieve unified management of all user-related data.
- the data network (English: Data Network, DN for short) provides data transmission services for users. It can be a PDN network, such as the Internet (Internet) and IP Multimedia Service (English: IP Multi-media Service, IMS for short).
- the application function (English: Application, abbreviation: AF) mainly performs dynamic policy/billing control on the forwarding plane behavior. These services require dynamic policy and charging control.
- the AF transmits the dynamic session information required by the PCF, and receives the IP-CAN access network (IP-CAN) specific information and the IP-CAN bearer layer event confirmation.
- IP-CAN IP-CAN access network
- the unstructured data storage function (English: Unstructured Data Storage Function, UDSF for short) is used to store the UE context (UE Context).
- User equipment (English: User Equipment, UE for short) may be called a terminal, and may also be called an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, and a wireless device. Communication device, user agent or user device, etc. In FIG. 1, the UE is taken as an example for description.
- the terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (WLL) station, and a personal digital processing (English: Personal Digital) Assistant, referred to as PDA), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, IoT devices, such as fire detection sensors, smart water meters/meters, factories Monitor equipment and more.
- SIP Session Initiation Protocol
- WLL wireless local loop
- PDA Personal Digital Processing
- the plurality of items referred to in the present application mean two or more. "and/or”, describing the association relationship of the associated objects, indicating that there may be three relationships, for example, A and/or B, which may indicate that there are three cases where A exists separately, A and B exist at the same time, and B exists separately.
- the character "/" generally indicates that the contextual object is an "or” relationship.
- first, second, third, etc. may be used to describe various messages, requests, and devices in the embodiments of the present application, these messages, requests, and devices should not be limited to these terms. These terms are only used to distinguish messages, requests, and devices from each other.
- the first mobility management network element After the first mobility management network element acquires the context information of the terminal device, the first mobility management network element does not need to re-initiate the new registration request process, which reduces the signaling interaction between the terminal device and the network, and reduces the terminal device from the idle state. The delay to the connected state.
- the embodiment of the present application is described by taking the mobility management network element related to the AMF as an example. Since the terminal device transitions from the idle state to the connected state, it may have left the service area of the old/source AMF entity, thereby The mobility management network element is a new/target AMF, and the second mobility management network element is an old/source AMF. In the following embodiments, for convenience of description, they are collectively referred to as old AMF and new AMF.
- the transition from the idle state to the connected state of the terminal device involved in the embodiment of the present application may be that the connection state of the terminal device itself is changed from the idle state to the connected state, or may further include converting a certain PDU session of the terminal device from the deactivated state. It is active.
- FIG. 2 is a schematic diagram of a state switching method according to an embodiment of the present application.
- the New AMF determines that the context information of the UE does not exist in the New AMF.
- the New AMF requests the context information from the old AMF according to the indication information and the identifier information. That is, the New AMF sends a request message to the old AMF for requesting context information of the UE.
- the old AMF After receiving the request message, the old AMF sends the context information of the UE to the New AMF, so that the New AMF acquires context information of the UE.
- the indication information and the identifier information of the UE may be sent by using the same message, or the indication information and the identifier information of the UE may be sent through different messages.
- the indication information and the identification information of the UE may be carried in the NAS message, or both carried in the non-NAS message, and may also be carried in the NAS message and carried in the non-NAS message (for example, the indication information is The NAS message is sent, and the identity of the UE is sent in a non-NAS message.
- the indication information when the indication information is sent in the non-NAS message, and the non-NAS message is a service request message, the indication information may be a service type of the service request message, and the service type is MICO. data service.
- the indication information for indicating the MICO mode is a cell that is independently set in the service request.
- the registration request may further carry a packet data unit PDU session identifier to be activated, such as a PDU session ID.
- a packet data unit PDU session identifier to be activated, such as a PDU session ID.
- the registration request message further carries an activation flag, where the activation flag is used to indicate that the terminal device needs to send uplink data.
- S302 The UE sends a service request (Service Request) to the RAN by using the second RRC message, where the service request carries the indication information.
- Service Request a service request (Service Request) to the RAN by using the second RRC message, where the service request carries the indication information.
- the service request may further carry a PDU session ID (ie, an identifier of the PDU session to be activated).
- a PDU session ID ie, an identifier of the PDU session to be activated
- the first RRC message and the second RRC message may be the same message or different messages.
- the context information of the UE may also be sent to the UDSF.
- the old AMF may perform a Security Verification of Service request on the Service Request message, and successfully return a UE context to the New AMF.
- the old AMF returns the UE context directly to the New AMF after receiving the UE context request.
- the New AMF may further perform S306.
- the New AMF sends a Service Request Accept message to the UE.
- the New AMF may send the Service Request Accept message to the UE by using the N2message of step S309 and the RRC message of S310.
- the SMF returns N2SM information to the New AMF through the N11 interface signaling, where the N2SM information includes QoS information and CN N3 Tunnel Information.
- the CN N3tunnel Info is used by the RAN to correctly send the data of the UE to the corresponding UPF; the QoS profile includes the QoS parameter information corresponding to all QoS flows of the PDU session corresponding to the PDU session ID, Establish an air interface bearer in the RAN.
- the New AMF sends the N2SM information received from the SMF and other information (such as a security context security context, a handover restriction list, and the like) to the RAN through N2 interface signaling (N2message).
- N2message is for example N2request.
- the RAN performs an RRC Connection Reconfiguration process with the UE based on the QoS profile of the PDU sessions to be activated, and establishes a secure connection between the UE and the RAN.
- the RAN returns an N2SM information (informatation ion) to the New AMF through an N2request ACK message.
- the N2SM information includes N3 Tunnel information, QoS Flow (List of accepted QoS Flows for the PDU Sessions activated), and QoS Flow (List of rejected QoS Flows for the PDU session). PDU Sessions activated).
- the New AMF sends the N2SM information to the corresponding SMF. Specifically, the New AMF sends the N2SM information to the corresponding SMF through the N11 interface signaling (N11message).
- the SMF may initiate an IP-Connectivity Access Network Session Modification (IP-Connectivity Access Network Session Modification). IP-CAN Session Modification).
- IP-Connectivity Access Network Session Modification IP-Connectivity Access Network Session Modification
- the N4 message update procedure is performed between the SMF and the UPF, and specifically, the RAN N3 tunnel information is configured on the UPF, and the RAN N3 tunnel information is used by the UPF to correctly send the data of the UE to the corresponding RAN.
- the SMF returns an Ack message (N11message ACK) corresponding to the N11 interface signaling of S311 to the New AMF.
- the UE sends the indication information to the New AMF in a Service Request message (by the service type indication).
- the New AMF identifies that the UE is in the MICO mode according to the service type, and then determines that the local is not present.
- the service request failure process is not executed, but the UE context retrieval process is triggered.
- the UE reports the identification information of the UE to the RAN in the RRC message, and reports it to the AMF by the AN.
- the indication information is further used to indicate that the registration area of the terminal device is an all PLMN registration area
- the New may further determine, according to the indication information, that the registration area of the UE is an all PLMN registration area.
- Service type is set to "MICO packet service”.
- the UE sends a service request (Service Request) and identifier information of the UE to the RAN through an RRC message.
- Service Request a service request
- identifier information of the UE to the RAN through an RRC message.
- the UE sends the service request and the identifier information of the UE to the RAN in the same RRC message as an example.
- the service request may further carry a PDU session ID to be activated (ie, an identifier of the PDU session to be activated).
- the RAN After receiving the identifier information of the UE and the service request, the RAN determines an Old AMF that is served by the UE according to the identifier information of the UE, and sends the identifier information of the UE and the indication information to the Old AMF.
- the RAN may send the identification information of the UE and the indication information to the Old AMF through the N2 message. If the RAN cannot connect to the Old AMF serving the UE according to the identification information of the UE, a New AMF may be selected for the UE according to the pre-configured policy of selecting the AMF, such as according to the load information of each AMF. In FIG. 4, the RAN can be connected to the old AMF serving the UE according to the identification information of the UE. Therefore, the RAN sends the identification information of the UE and the indication information to the New AMF. When carrying the PDU session ID to be activated in the service request, the RAN also sends the PDU session ID to be activated to the New AMF.
- the New AMF identifies that the UE is in the MICO mode according to the service type (MICO Packet service) in the service request, and determines whether the context information of the UE is stored locally. If the determination is yes, the process of continuing the Idle to the connected process is continued.
- the context of the UE is stored, and the service request failure procedure is not executed, but the UE context recovery procedure is triggered. That is, the New AMF determines the old AMF according to the identity information of the UE, and sends a request (such as the UE context request) to the old AMF to acquire the context of the UE.
- the UE context request carries the identifier information of the UE and the Service request message.
- the context information of the UE may also be sent to the UDSF.
- the old AMF may perform a Security Verification of Service request on the Service Request message, and successfully return a UE context to the New AMF.
- the old AMF returns the UE context directly to the New AMF after receiving the UE context request.
- Old AMF returns UE context to New AMF.
- the method further includes steps S407 to S415.
- steps S407 to S415 refer to steps S307 to S315 in FIG. 3, and details are not described herein again.
- the UE sends the indication information and the identifier information of the UE in a Service Request message (not indicated by the service type) to the New AMF.
- the New AMF identifies the UE according to the indication information.
- the service request failure procedure is not executed, but the UE context retrieval process is triggered.
- the UE sends the second identity of the UE (eg, 5G S-TMSI) to the RAN through an RRC message for the RAN to select the AMF.
- the indication information is also used to indicate When the registration area of the terminal device is an all PLMN registration area, the New may further determine, according to the indication information, that the registration area of the UE is an all PLMN registration area.
- the UE sends a service request (Service Request) to the RAN by using the second RRC message, where the service request carries the indication information and the identifier information of the UE.
- Service Request a service request
- the service request carries the indication information and the identifier information of the UE.
- the service request may further carry a PDU session ID (ie, an identifier of the PDU session to be activated).
- a PDU session ID ie, an identifier of the PDU session to be activated
- the first RRC message and the second RRC message may be the same message or different messages.
- the RAN After receiving the service request and the second identifier of the UE, the RAN determines the old AMF served by the UE according to the identifier information of the UE in the service request, and sends the identifier information of the UE and the indication information to the old AMF.
- the RAN may send the identification information of the UE and the indication information to the old AMF through the N2 message. If the RAN cannot connect to the old AMF serving the UE according to the identification information of the UE, the New AMF may be selected according to the second identifier, or a New AMF may be selected for the UE according to the policy of selecting the AMF, for example, according to the load information of each AMF.
- the New AMF may be selected according to the second identifier, or a New AMF may be selected for the UE according to the policy of selecting the AMF, for example, according to the load information of each AMF.
- the RAN can be connected to the old AMF serving the UE according to the identification information of the UE. Therefore, the RAN sends the identification information of the UE and the indication information to the New AMF.
- the RAN When carrying the PDU session ID to be activated in the service request, the RAN also sends the PDU session ID to be activated to the New AMF.
- the New AMF identifies that the UE is in the MICO mode according to the indication information, and determines whether the context information of the UE is stored locally. If the determination is yes, the process of continuing the Idle to connected is continued. If the context of the UE is not stored locally, To perform the service request failure process, the UE context recovery process is triggered, that is, the New AMF determines the old AMF according to the identity information of the UE, and sends a request (such as the UE context request) to the old AMF to acquire the context of the UE.
- the UE context request carries the identifier information of the UE and the Service request message.
- the New AMF may further determine, according to the indication information, that the registration area of the UE is an all PLMN registration area.
- the context information of the UE may also be sent to the UDSF.
- the old AMF may perform a Security Verification of Service request on the Service Request message, and successfully return a UE context to the New AMF.
- the old AMF returns the UE context directly to the New AMF after receiving the UE context request.
- the New AMF may further perform S306.
- the New AMF sends a Service Request Accept message to the UE.
- the New AMF may send the Service Request Accept message to the UE through the N2message of step S509 and the RRC message of S510.
- the UE carries the indication information and the UE identifier in a registration request message (the indication information
- the new AMF is sent to the New AMF by using the registration type indication.
- the New AMF identifies that the UE is in the MICO mode according to the indication information, and does not allocate the UE to the tracking area list (English: Tracking Area list, referred to as TA list), and determines that there is no local
- the UE context retrieve process is triggered when the UE Context is stored.
- the New may further determine, according to the indication information, that the registration area of the UE is an all PLMN registration area.
- the UE When the UE is in the MICO mode and triggers the uplink data transmission, the UE sets the registration type in the registration request to “MICO packet registration”, and the registration request may further carry the identifier of the UE. information.
- the registration request may further carry a PDU session ID to be activated (ie, an identifier of the PDU session to be activated).
- the registration request may further include an activation flag, where the activation flag is used to indicate that the UE needs to send uplink data.
- the RAN After receiving the registration request, the RAN determines the old AMF served by the UE according to the information of the unique identifier AMF sent by the UE, and sends the identifier information of the UE and the indication information to the old AMF.
- the RAN may send the identification information of the UE and the indication information to the old AMF through the N2 message.
- a New AMF may be selected for the UE according to the policy of selecting the AMF, such as according to the load information of each AMF.
- FIG. 6 is an example in which the RAN cannot connect to the old AMF serving the UE according to the identification information of the UE, and the RAN sends the registration request to the New AMF (the identification information of the UE and the indication information (registration type). )).
- the RAN also sends the PDU session ID to be activated to the New AMF.
- the context information of the UE may also be sent to the UDSF.
- the old AMF may perform a Security Verification of Registration request on the Registration request message, and successfully return a UE context to the New AMF.
- the old AMF returns the UE context directly to the New AMF after receiving the UE context request.
- Old AMF returns the UE context to New AMF.
- the New AMF may further perform S606.
- the method further includes steps S607 to S615.
- steps S607 to S615 refer to steps S307 to S315 in FIG. 3, and details are not described herein again.
- the UE sends the indication information and the UE identifier to the New AMF in the registration request message (not in the registration type indication).
- the New AMF identifies that the UE is in the MICO mode according to the indication information, and does not allocate the UE.
- the tracking area list (English: Tracking Area list, referred to as TA list), and triggers the UE context retrieval process when it is determined that the UE Context is not stored locally.
- the New may further determine, according to the indication information, that the registration area of the UE is an all PLMN registration area.
- the RAN After receiving the registration request, the RAN determines an old AMF serving as a UE according to the information of the unique identifier AMF sent by the UE, and sends the identifier information of the UE and the indication information to the old AMF.
- the RAN may send the identification information of the UE and the indication information to the old AMF through the N2 message. If the RAN cannot connect to the old AMF serving the UE according to the information identifying the AMF uniquely, a New AMF may be selected for the UE according to the policy of selecting the AMF, such as according to the load information of each AMF. In the example of FIG.
- Old AMF returns the UE context to New AMF.
- the New AMF may also send the Service Request Accept message to the UE by using the N2message of the S708 and the RRC message of the S709.
- the first mobility management network element After the first mobility management network element acquires the context information of the terminal device, the first mobility management network element does not need to re-initiate the new registration request process, which reduces the signaling interaction between the terminal device and the network, and reduces the terminal device from the idle state. The delay to the connected state.
- the identifier of the PDU session to be activated and the identifier information of the UE may be sent by using the same message, or the identifier of the PDU session to be activated and the identifier information of the UE may be sent through different messages.
- the indication information and the identification information of the UE may be carried in the NAS message, or both carried in the non-NAS message, and may also be carried in the NAS message and carried in the non-NAS message (for example, the indication information is The NAS message is sent, and the identity of the UE is sent in a non-NAS message.
- the UE sends the identifier of the PDU session to be activated and the UE identifier to the New AMF in the registration request message.
- the New AMF determines that the registration request message includes the identifier of the PDU session to be activated.
- the UE activates the PDU session; when it is determined that the UE Context is not stored locally, the UE context retrieval process is triggered.
- the New may further determine, according to the indication information, that the registration area of the UE is an all PLMN registration area.
- a New AMF may be selected for the UE according to the policy of selecting the AMF, such as according to the load information of each AMF.
- the RAN is not able to connect to the old AMF serving the UE according to the identification information of the UE. Therefore, the RAN sends the identifier information of the UE and the identifier of the PDU session to be activated to the New AMF.
- the New AMF determines whether the context information of the UE is stored locally. If the determination is yes, the process of continuing the Idle-to-connected process is continued.
- the context of the UE triggers the UE context recovery procedure, that is, the New AMF determines the old AMF according to the identity information of the UE, and sends a request (such as the UE context request) to the old AMF to acquire the context of the UE.
- the UE context request carries the identifier information of the UE and the Registration request message.
- the New AMF may further determine, according to the indication information, that the registration area of the UE is an all PLMN registration area.
- the context information of the UE may also be sent to the UDSF.
- the New AMF may also send the Service Request Accept message to the UE by using the N2message of the S808 and the RRC message of the S809.
- the obtaining module 901 is configured to acquire the indication information and the identifier information of the terminal device from the terminal device, where the indication information is used to indicate that the terminal device is in a mobile terminal only initiates a connection MICO mode;
- the processing module 902 is configured to determine that context information of the terminal device does not exist in the first mobility management network element
- the sending module 903 is configured to: when the processing module 902 determines that the context information of the terminal device does not exist in the first mobility management network element, according to the indication information and the identifier information, move to the second mobile The sexual management network element requests the context information.
- the acquiring module 901 is specifically configured to: receive a request message from a base station, where the request message carries the indication information and the identifier information.
- the request message is a service request message or a registration request message.
- the indication information is a service type of the service request message, and the service type is a MICO data service.
- the registration request message further carries a packet data unit PDU session identifier to be activated.
- the registration request message further carries an activation flag, where the activation flag is used to indicate that the terminal device needs to send uplink data.
- the identifier information is used to uniquely identify the terminal device globally.
- the processing module 902 is further configured to: determine, according to the indication information, that the context information needs to be requested; and the first mobility management network element determines, according to the identifier information, The second mobility management network element; the sending module is specifically configured to send a UE context request to the second mobility management network element.
- the indication information is further used to indicate that the registration area of the terminal device is a full public land mobile network PLMN registration area; or the indication information includes first indication information and second indication information.
- the first indication information is used to indicate that the terminal device is in a mobile terminal only to initiate a connection MICO mode
- the second indication information is used to indicate that the registration area of the terminal device is a full public land mobile network PLMN registration area.
- the obtaining module 901 is configured to acquire, from the terminal device, an identifier of the packet data unit PDU session to be activated and the identifier information of the terminal device, where the processing module 902 is configured to determine the first mobility management network element.
- the context information of the terminal device does not exist in the context;
- the sending module 903 is configured to: when the processing module 902 determines that the context information of the terminal device does not exist in the first mobility management network element, according to the identifier The information is requested by the second mobility management network element.
- the processing module 902 is further configured to activate, according to the identifier of the PDU session to be activated, a PDU session corresponding to the identifier of the PDU session for the terminal device.
- the PDU session corresponding to the identifier of the PDU session is activated by the terminal device, where the first mobility management network element sends the PDU session to be activated to the session management network element. Identifying to cause the session management network element to activate the PDU session.
- the first mobility management network element acquires, from the terminal device, the identifier of the packet data unit PDU session to be activated and the identifier information of the terminal device, including: the first mobility management network element And receiving, by the base station, a registration request message, where the registration request message carries an identifier of the PDU session to be activated and the terminal device identification information.
- the registration request message further carries an activation flag, where the activation flag is used to indicate that the terminal device needs to send uplink data.
- each functional module in each embodiment of the present application may be integrated into one processing. In the device, it can also be physically existed alone, or two or more modules can be integrated into one module.
- the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
- the state switching device applied to the first mobility management network element may include a communication interface 1010, a processor 1020, and a memory 1030.
- the hardware of the entity corresponding to the unit shown in FIG. 9 above may be the processor 1020.
- the processor 1020 transmits and receives data through the communication interface 1010 and is used to implement the method performed by the New AMF described in FIGS. 2-8.
- each step of the processing flow may be completed by an integrated logic circuit of hardware in the processor 1020 or an instruction in the form of software.
- the processor 1020 can be a general purpose processor, a digital signal processor, and a dedicated set.
- the methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or executed in a circuit, a field programmable gate array, or other programmable logic device, a discrete gate or a transistor logic device, or a discrete hardware component.
- a general purpose processor can be a microprocessor or any conventional processor or the like.
- the steps of the method disclosed in the embodiments of the present application may be directly implemented as a hardware processor, or may be performed by a combination of hardware and software modules in the processor.
- Program code for processor 1020 to implement the above methods may be stored in memory 1030.
- the memory 1030 may be a non-volatile memory, such as a hard disk drive (HDD) or a solid state drive (SSD), or a volatile memory (English: volatile) Memory), such as random access memory (English: random-access memory, abbreviation: RAM).
- Memory 1030 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.
- the specific connection medium between the communication interface 1010, the processor 1020, and the memory 1030 is not limited in the embodiment of the present application.
- the memory 1030, the processor 1020, and the communication interface 1010 are connected by a bus 1040 in FIG. 10.
- the bus is indicated by a thick line in FIG. 10, and the connection manner between other components is only schematically illustrated. , not limited to.
- 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 FIG. 10, but it does not mean that there is only one bus or one type of bus.
- the embodiment of the present application provides a state switching device, which is applied to a terminal device.
- the device can be implemented as shown in FIG. 2 to FIG. 8.
- the device includes:
- a determining module 1101 configured to learn that the terminal device is in a mobile terminal only initiates a connection MICO mode
- the sending module 1102 is configured to: when the terminal device needs to send uplink data, send the indication information and the identifier information of the terminal device to the first mobility management network element, where the indication information is used to indicate that the terminal device is in the MICO mode.
- the sending module 1102 is specifically configured to send, by using a base station, a radio resource control RRC message to the first mobility management network element, where the RRC message carries the indication information.
- the sending module 1102 is specifically configured to send, by using a base station, a radio resource control RRC message to the first mobility management network element, where the RRC message carries the identifier information of the terminal device. .
- the identifier information is used to uniquely identify the terminal device globally.
- the indication information is further used to indicate that the registration area of the terminal device is a full public land mobile network PLMN registration area; or the indication information includes first indication information and second indication information.
- the first indication information is used to indicate that the terminal device is in a mobile terminal only to initiate a connection MICO mode
- the second indication information is used to indicate that the registration area of the terminal device is a full public land mobile network PLMN registration area.
- the sending module 1102 is specifically configured to send a request message to the first mobility management network element, where the request message carries the indication information and/or the terminal device Identification information; the request message is a service request message or a registration request message.
- the indication information is a service type of the service request message, and the service type is a MICO data service.
- the indication information is a registration type of the registration request message, and the registration type is a MICO data registration.
- the registration request message further carries a packet data unit PDU session identifier to be activated.
- the registration request message further carries an activation flag, where the activation flag is used to indicate that the terminal device needs to send uplink data.
- each functional module in each embodiment of the present application may be integrated into one processing. In the device, it can also be physically existed alone, or two or more modules can be integrated into one module.
- the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
- the state switching device applied to the terminal device may include a transceiver 1210, a processor 1220, and a memory 1230.
- the hardware of the entity corresponding to the module shown in FIG. 11 above may be the processor 1220.
- the processor 1220 transmits and receives data through the transceiver 1210 and is used to implement the method performed by the UE described in FIGS. 2-8.
- each step of the processing flow may be completed by an integrated logic circuit of hardware in the processor 1220 or an instruction in the form of software.
- the processor 1220 can be a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or a transistor logic device, and a discrete hardware component, which can be implemented or executed in the embodiment of the present application.
- a general purpose processor can be a microprocessor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present application may be directly implemented as a hardware processor, or may be performed by a combination of hardware and software modules in the processor.
- Program code for processor 1220 to implement the above methods may be stored in memory 1230.
- the memory 1230 may be a non-volatile memory, such as a hard disk drive (HDD) or a solid state drive (English: solid-state dr ive, abbreviated as SSD), or a volatile memory (English: Volatile memory), such as random access memory (English: random-access memory, abbreviation: RAM).
- Memory 1230 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.
- connection medium between the above transceiver 1210, the processor 1220, and the memory 1230 is not limited in the embodiment of the present application.
- the memory 1230, the processor 1220, and the transceiver 1210 are connected by a bus 1240 in FIG. 12, and the bus is indicated by a thick line in FIG. 12, and the connection manner between other components is only schematically illustrated. , not limited to.
- 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 embodiment of the present application further provides a computer storage medium, where the software program stores a software program, and the software program can implement the measurement provided by the foregoing embodiment when being read and executed by one or more processors.
- the computer storage medium may include: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. medium.
- embodiments of the present application can be provided as a method, system, or computer program product.
- the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment in combination of software and hardware.
- the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
- the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
- the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
- These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
- the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Quality & Reliability (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
一种状态切换方法及装置,用以解决在MICO模式下终端进行服务请求流程失败带来信令开销增大的问题。该方法包括:第一移动性管理网元从终端设备获取指示信息和所述终端设备的标识信息,所述指示信息用于指示所述终端设备处于只移动终端发起连接MICO模式;如果所述第一移动性管理网元内不存在所述终端设备的上下文信息,所述第一移动性管理网元根据所述指示信息和所述标识信息,向第二移动性管理网元请求所述上下文信息。
Description
本申请涉及通信技术领域,特别涉及一种状态切换方法及装置。
第五代(英文:the 5th Generation,简称:5G)通信系统定义了一种通信模式:只移动终端发起的连接(英文:Mobile Initiated Connection Only,简称:MICO)模式。终端在注册流程中会和网络侧协商MICO模式。在协商过程中,网络侧还可能会指示终端注册为“整个公用大陆移动网(英文:public land mobile network,简称:PLMN)”(“all PLMN”)注册区。在MICO模式下,只有终端主动发起上行业务,,当终端处于空闲态时,网络侧拒绝任何传递下行数据(包括用户面数据和控制面信令)的请求。并且,对于处于MICO模式下且处于空闲(CM-IDLE)态的终端,网络侧不发起对该终端的寻呼流程,终端也不需要侦听寻呼(即paging流程)。另外,对于“all PLMN”注册区,意味着UE已经在整个PLMN网络区注册,终端不需要因为其移动性而重新注册到该PLMN网络,即终端不需要发起移动性注册更新(mobility registration update)类型的注册流程。
在5G网络中,终端通过服务请求(即service request)流程,将终端从空闲态(idle)转换到连接态(connected),还可以通过服务请求(即service request)流程激活终端的PDU会话以传递数据业务。在MICO模式下,由于上述原因,即UE处于MICO模式并且分配“All PLMN”注册区,当终端需要从空闲态转换到连接态并发起服务请求流程时,终端可能已经离开了源接入和移动性管理功能(Access and Mobility Management function,AMF)实体的服务区域,这样将会导致以下问题:新AMF实体上没有终端的上下文(即context),从而会判定此次服务请求流程失败,要求终端重新进行注册请求流程。这会增加终端和网络之间的信令流程,带来不必要的信令开销,还会增加终端从空闲态转换到连接态的时延。
发明内容
本申请提供一种状态切换方法及装置,用以解决在MICO模式下终端进行服务请求流程失败带来信令开销增大的问题。
第一方面,本申请实施例提供了一种状态切换方法,该方法包括:第一移动性管理网元从终端设备获取指示信息和所述终端设备的标识信息,所述指示信息用于指示所述终端设备处于只移动终端发起连接MICO模式;如果所述第一移动性管理网元内不存在所述终端设备的上下文信息,所述第一移动性管理网元根据所述指示信息和所述标识信息,向第二移动性管理网元请求所述上下文信息。
通过上述方式,第一移动性管理网元获取到终端设备的上下文信息后,不需要重新发起新的注册请求流程,减少了终端设备与网络之间的信令交互,降低了终端设备从空闲态转换到连接态的时延。
在一种可能的设计中,所述第一移动性管理网元从终端设备获取指示信息和所述终端
设备的标识信息,包括:所述第一移动性管理网元从基站接收请求消息,所述请求消息中携带所述指示信息和所述标识信息。
通过上述设计,提供了一种扩展的获取指示信息和所述终端设备的标识信息的方式,使得获取方式更灵活。
在一种可能的设计中,所述请求消息为服务请求消息或注册请求消息。
通过上述设计,通过服务请求消息或注册请求消息获取指示信息和所述终端设备的标识信息,使得获取方式更灵活。
在一种可能的设计中,所述指示信息为所述服务请求消息的服务类型,所述服务类型为MICO数据服务。
通过上述设计,通过服务请求消息中的服务类型作为指示信息,使得第一移动性管理网元获取指示信息的方式更灵活。
在一种可能的设计中,所述指示信息为所述注册请求消息的注册类型,所述注册类型为MICO数据注册。
通过上述设计,通过注册请求消息中的注册类型作为指示信息,使得第一移动性管理网元获取指示信息的方式更灵活。
在一种可能的设计中,所述注册请求消息还携带待激活的分组数据单元PDU会话标识。
通过上述设计,在注册请求消息携带PDU会话标识,节省信令资源。
在一种可能的设计中,所述注册请求消息还携带激活标记,所述激活标记用于指示所述终端设备需要发送上行数据。
通过上述设计,在注册请求消息中携带激活标记,使得第一移动性管理网元更明确UE发送注册请求消息的目的。
在一种可能的设计中,所述标识信息用于全球唯一识别所述终端设备。
在一种可能的设计中,所述第一移动性管理网元根据所述指示信息和所述标识信息,向第二移动性管理网元请求所述上下文信息,包括:所述第一移动性管理网元根据所述指示信息确定需要请求所述上下文信息;以及,所述第一移动性管理网元根据所述标识信息确定所述第二移动性管理网元;所述第一移动性管理网元向所述第二移动性管理网元发送UE上下文请求。
通过上述设计,基于标识信息确定第二移动性管理网元,来向第二移动性管理网元获取UE的上下文,从而不需要重新发起新的注册请求流程,减少了终端设备与网络之间的信令交互,降低了终端设备从空闲态转换到连接态的时延。
在一种可能的设计中,所述指示信息还用于指示所述终端设备的注册区域为全公用陆地移动网PLMN注册区域;或者,所述指示信息包括第一指示信息和第二指示信息,所述第一指示信息用于指示所述终端设备处于只移动终端发起连接MICO模式,所述第二指示信息用于指示所述终端设备的注册区域为全公用陆地移动网PLMN注册区域。
上述设计,提供了指示信息的指示方式,使得设计更加灵活。
在一种可能的设计中,所述方法还可以包括:所述第一移动性管理网元从所述终端设备获取待激活的分组数据单元PDU会话的标识;所述第一移动性管理网元根据所述待激活的PDU会话的标识,为所述终端设备激活所述PDU会话的标识对应的PDU会话。
第二方面,本申请实施例提供了一种状态切换方法,包括:终端设备获知所述终端设
备处于只移动终端发起连接MICO模式;当所述终端设备需要发送上行数据时,所述终端设备向第一移动性管理网元发送指示信息和所述终端设备的标识信息,所述指示信息用于指示所述终端设备处于MICO模式。
通过上述方式,终端设备向第一移动性管理网元发送指示信息和所述终端设备的标识信息,从而第一移动性管理网元能够确定获取终端设备的上下文信息的第二移动性管理网元,来获取终端设备的上下文信息,不需要重新发起新的注册请求流程,减少了终端设备与网络之间的信令交互,降低了终端设备从空闲态转换到连接态的时延。
在一种可能的设计中,所述终端设备向第一移动性管理网元发送指示信息,包括:所述终端设备通过基站向所述第一移动性管理网元发送无线资源控制RRC消息,所述RRC消息中携带所述指示信息。
在一种可能的设计中,所述终端设备向第一移动性管理网元发送所述终端设备的标识信息,包括:所述终端设备通过基站向所述第一移动性管理网元发送无线资源控制RRC消息,所述RRC消息中携带所述终端设备的标识信息。
上述设计,提供了一种灵活的获取所述终端设备的标识信息的方式。
在一种可能的设计中,所述标识信息用于全球唯一识别所述终端设备。
在一种可能的设计中,所述指示信息还用于指示所述终端设备的注册区域为全公用陆地移动网PLMN注册区域;或者,所述指示信息包括第一指示信息和第二指示信息,所述第一指示信息用于指示所述终端设备处于只移动终端发起连接MICO模式,所述第二指示信息用于指示所述终端设备的注册区域为全公用陆地移动网PLMN注册区域。
上述设计,提供了指示信息的指示方式,使得设计更加灵活。
在一种可能的设计中,所述终端设备向第一移动性管理网元发送指示信息和所述终端设备的标识信息,包括:所述终端设备向所述第一移动性管理网元发送请求消息,所述请求消息中携带所述指示信息和/或所述终端设备的标识信息;所述请求消息为服务请求消息或注册请求消息。
通过上述设计,通过服务请求消息或注册请求消息获取指示信息和所述终端设备的标识信息,使得获取方式更灵活。
在一种可能的设计中,所述指示信息为所述服务请求消息的服务类型,所述服务类型为MICO数据服务。
通过上述设计,通过服务请求消息中的服务类型作为指示信息,使得第一移动性管理网元获取指示信息的方式更灵活。
在一种可能的设计中,所述指示信息为所述注册请求消息的注册类型,所述注册类型为MICO数据注册。
通过上述设计,通过注册请求消息中的注册类型作为指示信息,使得第一移动性管理网元获取指示信息的方式更灵活。
在一种可能的设计中,所述注册请求消息还携带待激活的分组数据单元PDU会话标识。
通过上述设计,在注册请求消息携带PDU会话标识,节省信令资源。
在一种可能的设计中,所述注册请求消息还携带激活标记,所述激活标记用于指示所述终端设备需要发送上行数据。
第三方面,本申请实施例提供了一种状态切换方法,包括:第一移动性管理网元从终
端设备获取待激活的分组数据单元PDU会话的标识和所述终端设备的标识信息;如果所述第一移动性管理网元内不存在所述终端设备的上下文信息,所述第一移动性管理网元根据所述标识信息,向第二移动性管理网元请求所述上下文信息;所述第一移动管理网元并根据所述待激活的PDU会话的标识,为所述终端设备激活所述PDU会话的标识对应的PDU会话。
通过上述设计,第一移动性管理网元获取到终端设备的上下文信息后,不需要重新发起新的注册请求流程,减少了终端设备与网络之间的信令交互,降低了终端设备从空闲态转换到连接态的时延。
在一种可能的设计中,为所述终端设备激活所述PDU会话的标识对应的PDU会话,包括:所述第一移动管理网元向会话管理网元发送所述待激活的PDU会话的标识,以使得所述会话管理网元激活所述PDU会话。
在一种可能的设计中,第一移动性管理网元从终端设备获取待激活的分组数据单元PDU会话的标识和所述终端设备的标识信息,包括:所述第一移动性管理网元从基站接收注册请求消息,所述注册请求消息中携带待激活的PDU会话的标识和所述终端设备标识信息。
在一种可能的设计中,所述注册请求消息中还携带激活标记,所述激活标记用于指示所述终端设备需要发送上行数据。
第四方面,基于与第一方面提供的方法实施例的同样发明构思,本申请实施例提供了一种状态切换装置,该状态切换装置应用于第一移动性管理网元,所述装置包括:
获取模块,用于从终端设备获取指示信息和所述终端设备的标识信息,所述指示信息用于指示所述终端设备处于只移动终端发起连接MICO模式;
处理模块,用于确定在所述第一移动性管理网元内不存在所述终端设备的上下文信息;
发送模块,用于在所述处理模块确定在所述第一移动性管理网元内不存在所述终端设备的上下文信息时,根据所述指示信息和所述标识信息,向第二移动性管理网元请求所述上下文信息。
在一种可能的设计中,所述获取模块,具体用于:从基站接收请求消息,所述请求消息中携带所述指示信息和所述标识信息。
在一种可能的设计中,所述请求消息为服务请求消息或注册请求消息。
在一种可能的设计中,所述指示信息为所述服务请求消息的服务类型,所述服务类型为MICO数据服务。
在一种可能的设计中,所述指示信息为所述注册请求消息的注册类型,所述注册类型为MICO数据注册。
在一种可能的设计中,所述注册请求消息还携带待激活的分组数据单元PDU会话标识。
在一种可能的设计中,所述注册请求消息还携带激活标记,所述激活标记用于指示所述终端设备需要发送上行数据。
在一种可能的设计中,所述标识信息用于全球唯一识别所述终端设备。
在一种可能的设计中,所述处理模块,还用于:根据所述指示信息确定需要请求所述上下文信息;以及,所述第一移动性管理网元根据所述标识信息确定所述第二移动性管理
网元;所述发送模块,具体用于向所述第二移动性管理网元发送UE上下文请求。
在一种可能的设计中,所述指示信息还用于指示所述终端设备的注册区域为全公用陆地移动网PLMN注册区域;或者,所述指示信息包括第一指示信息和第二指示信息,所述第一指示信息用于指示所述终端设备处于只移动终端发起连接MICO模式,所述第二指示信息用于指示所述终端设备的注册区域为全公用陆地移动网PLMN注册区域。
在一种可能的设计中,所述获取模块,还用于从所述终端设备获取待激活的分组数据单元PDU会话的标识;所述处理模块,还用于根据所述待激活的PDU会话的标识,为所述终端设备激活所述PDU会话的标识对应的PDU会话。
第五方面,基于与第二方面提供的方法实施例的同样发明构思,本申请实施例提供了一种状态切换装置,所述装置应用于终端设备,包括:
确定模块,用于获知所述终端设备处于只移动终端发起连接MICO模式;
发送模块,用于在所述终端设备需要发送上行数据时,向第一移动性管理网元发送指示信息和所述终端设备的标识信息,所述指示信息用于指示所述终端设备处于MICO模式。
在一种可能的设计中,所述发送模块,具体用于通过基站向所述第一移动性管理网元发送无线资源控制RRC消息,所述RRC消息中携带所述指示信息。
在一种可能的设计中,所述发送模块,具体用于通过基站向所述第一移动性管理网元发送无线资源控制RRC消息,所述RRC消息中携带所述终端设备的标识信息。
在一种可能的设计中,所述标识信息用于全球唯一识别所述终端设备。
在一种可能的设计中,所述指示信息还用于指示所述终端设备的注册区域为全公用陆地移动网PLMN注册区域;或者,所述指示信息包括第一指示信息和第二指示信息,所述第一指示信息用于指示所述终端设备处于只移动终端发起连接MICO模式,所述第二指示信息用于指示所述终端设备的注册区域为全公用陆地移动网PLMN注册区域。
在一种可能的设计中,所述发送模块,具体用于向所述第一移动性管理网元发送请求消息,所述请求消息中携带所述指示信息和/或所述终端设备的标识信息;所述请求消息为服务请求消息或注册请求消息。
在一种可能的设计中,所述指示信息为所述服务请求消息的服务类型,所述服务类型为MICO数据服务。
在一种可能的设计中,所述指示信息为所述注册请求消息的注册类型,所述注册类型为MICO数据注册。
在一种可能的设计中,所述注册请求消息还携带待激活的分组数据单元PDU会话标识。
在一种可能的设计中,所述注册请求消息还携带激活标记,所述激活标记用于指示所述终端设备需要发送上行数据。
第六方面,基于与第三方面提供的方法实施例的同样发明构思,本申请实施例提供了一种状态切换装置,所述装置应用于第一移动性管理网元,包括:
获取模块,用于从终端设备获取待激活的分组数据单元PDU会话的标识和所述终端设备的标识信息;处理模块,用于确定在所述第一移动性管理网元内不存在所述终端设备的上下文信息;发送模块,用于在所述处理模块确定在所述第一移动性管理网元内不存在所述终端设备的上下文信息时,根据所述标识信息,向第二移动性管理网元请求所述上下文信息。所述处理模块,还用于根据所述待激活的PDU会话的标识,为所述终端设备激活所
述PDU会话的标识对应的PDU会话。
在一种可能的设计中,所述处理模块,在为所述终端设备激活所述PDU会话的标识对应的PDU会话,具体用于:指示发送模块向会话管理网元发送所述待激活的PDU会话的标识,以使得所述会话管理网元激活所述PDU会话。
在一种可能的设计中,所述获取模块,具体用于:从基站接收注册请求消息,所述注册请求消息中携带待激活的PDU会话的标识和所述终端设备标识信息。
在一种可能的设计中,所述注册请求消息中还携带激活标记,所述激活标记用于指示所述终端设备需要发送上行数据。
第七方面,本申请实施例提供了一种移动性管理网元,包括:通信接口、处理器以及存储器,所述通信接口用于收发数据,所述存储器用于存储软件程序,所述处理器用于读取所述存储器中存储的软件程序并实现第第一方面或第一方面的任意一种设计,或第三方面,或上述第三方面的任意一种设计提供的方法。
第八方面,本申请实施例提供了一种终端设备,包括:收发器、处理器以及存储器,所述收发器用于收发数据,所述存储器用于存储软件程序,所述处理器用于读取所述存储器中存储的软件程序并实现第二方面或上述第二方面的任意一种设计提供的方法。
第九方面,本申请实施例中还提供一种计算机存储介质,该存储介质中存储软件程序,该软件程序在被一个或多个处理器读取并执行时可实现第一方面或上述第一方面的任意一种设计提供的方法,或者实现第二方面或者第二方面的任一种设计所提供的方法,或者实现第三方面或者第三方面的任一种设计所提供的方法。
第十方面,本申请实施例提供了一种包含指令的计算机程序产品,当其在计算机上运行时,使得计算机执行上述方法。
图1为本申请实施例提供的切片化的5G网络架构示意图;
图2为本申请实施例提供的第一种状态转换方法流程示意图;
图3为本申请实施例提供的第二种状态转换方法流程示意图;
图4为本申请实施例提供的第三种状态转换方法流程示意图;
图5为本申请实施例提供的第四种状态转换方法流程示意图;
图6为本申请实施例提供的第五种状态转换方法流程示意图;
图7为本申请实施例提供的第六种状态转换方法流程示意图;
图8为本申请实施例提供的第七种状态转换方法流程示意图;
图9为本申请实施例提供的一种移动性管理网元结构示意图;
图10为本申请实施例提供的另一种移动性管理网元结构示意图;
图11为本申请实施例提供的一种终端设备结构示意图;
图12为本申请实施例提供的另一种终端设备结构示意图。
本申请实施例可以应用于5G通信系统或者长期演进(英文:long term evolution,
简称:LTE)系统等移动通信系统。
5G通信系统可以应用到各行各业的应用中,比如移动宽带、多媒体、机器类通信(英文:machine type communication,简称:MTC)、工业控制、和智能交通系统(英文:intelligent transportation system,简称:ITS)等。目前,5G网络以灵活的方式构建,具体是将网络功能分离,即控制面(英文:Control Plane,简称:CP)和用户面(英文:User Plane,简称:UP)功能分离,CP中的移动性管理(英文:Mobile Management,简称:MM)功能和会话管理(英文:session management,简称:SM)功能分离。此外,在5G中提出了网络切片(Network Slice)技术。网络切片技术是将一个物理网络切割成多个虚拟的端到端的网络,每个虚拟网络之间(包括网络内的设备、接入技术、传输路径和核心网)均是逻辑独立的。每个网络切片由一个独立的网络功能或功能组合实例化构成,具备不同的功能特点,面向不同的需求和服务。网络切片的提出使得不同用户、用户组可以根据其不同应用场景和需求灵活、动态的定义和定制网络能力。
一个网络切片包括控制面功能(英文:control plane function,简称:CPF)实体和用户面功能(英文:user plane function,简称:UPF)实体。其中,CPF实体主要完成终端设备的接入鉴权、安全加密、位置注册等接入控制和移动性管理功能(英文:access control and mobility management function,简称:AMF),以及用户面传输路径的建立、释放和更改等会话管理功能(英文:session management function,简称:SMF)。UPF实体主要完成用户面数据的路由转发等功能。
参见图1所示为本申请实施例提供一种切片化的5G网络架构示意图。本申请实施例中提供的5G网络架构中主要包括以下网络实体功能:
(无线)接入网(R)AN:由至少一个5G-RAN节点组成的网络,实现无线物理层功能、资源调度和无线资源管理、无线接入控制以及移动性管理功能。5G-RAN通过用户面接口N3和UPF相连,用于传送终端设备的数据;5G-RAN通过控制面接口N2和AMF建立控制面信令连接,用于实现无线接入承载控制等功能。5G-RAN节点具体可以是全球移动通信(英文:Global System for Mobile communication,简称:GSM)系统或码分多址(英文:Code Division Multiple Access,简称:CDMA)系统中的基站(英文:Base Transceiver Station,简称:BTS),也可以是宽带码分多址(英文:Wideband Code Division Multiple Access,简称:WCDMA)系统中的基站(NodeB),还可以是LTE系统中的演进型基站(英文:Evolutional Node B,简称:eNB或eNodeB),或者是未来5G网络中的基站设备、小基站设备、无线访问节点(WiFi AP)、无线互通微波接入基站(英文:Worldwide Interoperability for Microwave Access Base Station,简称:WiMAX BS)等,本申请对此并不限定。
AMF:主要负责UE的认证,UE移动性管理,网络切片的选择,SMF的选择等功能。AMF作为N1和N2信令连接的锚点并为SMF提供N1/N2SM消息的路由。AMF维护和管理用户设备(英文:User Equipment,简称:UE)的状态信息。
SMF:主要负责UE会话管理的所有控制面功能,包括UPF选择,网络协议(Internet Procol,简称:IP)地址分配,会话的服务质量(英文:Quality of Service,简称:QoS)管理,(从PCF)获取PCC策略等。
UPF:作为协议数据单元(英文:Protocol Data Unit,简称:PDU)会话连接的锚定点,负责对用户设备的数据报文过滤、数据传输/转发、速率控制、生成计费信息等。
策略控制功能实体(英文:Policy Rules Function,简称:PCF),还可以称为策略计费控制功能实体(英文:Policy and Charging Rules Function,简称:PCRF)。其中,PCF或者PCRF负责策略控制决策和基于流计费控制。
用户数据管理实体(英文:User Data Management,简称:UDM),可以称为归属签约用户服务器(英文:Home Subscriber Server,简称:HSS)。用户数据管理实体英文还可以对应于Subscriber Data Management,简称还可以对应于SDM。UDM、SDM或者HSS用于帮助运营商实现对所有与用户相关的数据的统一管理。
数据网络(英文:Data Network,简称:DN),为用户提供数据传输服务,可以是PDN网络,如因特网(Internet)、IP多媒体业务(英文:IP Multi-media Service,简称:IMS)等。
应用功能(英文:Application,简称:AF),主要对转发面行为进行动态策略/计费控制。这些业务需要动态策略和计费控制。AF传送PCF需要的动态会话信息,接收IP连接接入网(IP-CAN)的特定信息和IP-CAN承载层事件的确认。
非结构化数据存储功能(英文:Unstructured Data Storage Function,简称:UDSF),用于存储UE上下文(UE Context)。
用户设备(英文:User Equipment,简称:UE)可以称为终端,也可称为接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、无线通信设备、用户代理或用户装置等。图1中以UE为例进行说明。终端可以是蜂窝电话、无绳电话、会话启动协议(英文:Session Initiation Protocol,简称:SIP)电话、无线本地环路(英文:Wireless Local Loop,简称:WLL)站、个人数字处理(英文:Personal Digital Assistant,简称:PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、物联网终端设备,比如火灾检测传感器、智能水表/电表、工厂监控设备等等。
需要说明的是,本申请中涉及的多个,是指两个或两个以上。“和/或”,描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。同时,应当理解,尽管在本申请实施例中可能采用术语第一、第二、第三等来描述各种消息、请求、设备,但这些消息、请求、设备不应限于这些术语。这些术语仅用来将消息、请求、设备彼此区分开。
本申请实施例提供了一种状态切换的方法及装置,针对MICO场景下,提出一种获取终端的上下文的方式,具体的:处于MICO模式的终端设备在需要发送上行数据时,向第一移动性管理网元发送指示信息和所述终端设备的标识信息,所述指示信息用于指示所述终端设备处于MICO模式,第一移动性管理网元在从终端设备获取到指示信息和所述终端设备的标识信息后,在确定所述第一移动性管理网元内不存在所述终端设备的上下文信息时,所述第一移动性管理网元根据所述指示信息和所述标识信息,向第二移动性管理网元请求所述上下文信息。通过上述方式第一移动性管理网元获取到终端设备的上下文信息后,不需要重新发起新的注册请求流程,减少了终端设备与网络之间的信令交互,降低了终端设备从空闲态转换到连接态的时延。
本申请实施例以涉及到的移动性管理网元是AMF为例进行说明。由于终端设备由空闲态转换到连接态时,可能已经离开了旧/源(old/source)AMF实体的服务区域,从而第一
移动性管理网元是新/目标(New/target)AMF,而第二移动性管理网元是旧/源(old/source)AMF。以下实施例中,为了描述方便,统称为旧(old)AMF,新(New)AMF。
本申请实施例中涉及到的终端设备由空闲态转换到连接态可以是终端设备本身的连接状态从空闲态转换为连接态,或者还可以包括将终端设备的某个PDU会话从去激活态转换为激活态。
下面结合附图对本申请实施例提供的方案进行具体说明。
参见图2所示,为本申请实施例提供的一种状态切换方法示意图;
S201,处于MICO模式的UE在需要发送上行数据时,向New AMF发送指示信息和所述UE的标识信息。其中,所述指示信息用于指示所述终端设备处于MICO模式。
可选的,UE的标识信息可以是全球唯一标识UE的信息,或者全球唯一临时标识UE的信息。例如:全球唯一标识UE的信息为5G-全球唯一临时标识(英文:Globally Unique Temporary UE Identity,简称:5G-GUTI)。此外,在5G网络中,全球唯一标识UE的信息还可具有其他的名称,本发明并不在此限制。
S202,New AMF在从UE获取到指示信息和所述终端设备的标识信息后,确定所述New AMF内不存在所述UE的上下文信息。
S203,所述New AMF根据所述指示信息和所述标识信息,向old AMF请求所述上下文信息;即,New AMF向old AMF发送请求消息,用于请求UE的上下文信息。
S204,所述old AMF在接收到所述请求消息后,向所述New AMF发送所述UE的上下文信息,从而所述New AMF获取到所述UE的上下文信息。
可选的,UE可以在(英文:Non Access Stratum,简称:NAS)消息或者非NAS消息中向New AMF发送上述指示信息和UE的标识信息。
需要说明的是,可选地,可以通过同一条消息发送指示信息和UE的标识信息,或者,还可以通过不同的消息中发送指示信息和UE的标识信息。例如,指示信息和UE的标识信息可以均携带在NAS消息中发送,或者均携带在非NAS消息中发送,还可以一个携带在NAS消息发送,一个携带在非NAS消息中发送(比如指示信息在NAS消息中发送,UE的标识在非NAS消息中发送)。
可选地,指示信息既包含在NAS消息中,又包含在非NAS消息中。可选地,UE的标识既包含在NAS消息中,又包含在非NAS消息中。本申请实施例中,非NAS层消息包括,UE和RAN之间的RRC信令,RAN和AMF之间的N2接口信令;NAS层消息具体可以是服务请求(Service request)或者是注册请求(registration request),该NAS层消息可以在无线资源控制(英文:Radio Resource Control,简称:RRC)消息中发给RAN,RAN再通过N2接口信令将其发给AMF。
可选地,所述指示信息在用于指示所述终端设备处于MICO模式同时,还用于指示所述终端设备的注册区域为全公用陆地移动网PLMN注册区域;或者,所述指示信息包括第一指示信息和第二指示信息,所述第一指示信息用于指示所述终端设备处于MICO模式,所述第二指示信息用于指示所述终端设备的注册区域为all PLMN注册区域。
可选地,在通过非NAS消息中发送指示信息时,且非NAS消息为服务请求(Service request)消息时,所述指示信息可以为所述服务请求消息的服务类型,所述服务类型为MICO数据服务。或者,用于指示MICO模式的指示信息为服务请求中独立设置的信元。
可选地,在通过非NAS消息中发送指示信息时,且非NAS消息为注册请求
(registration request)消息时,所述指示信息可以为所述注册请求消息的注册类型,所述注册类型为MICO数据注册。或者,用于指示MICO模式的指示信息为注册请求中独立设置的信元。
可选地,所述注册请求中还可以携带待激活的分组数据单元PDU会话标识,比如PDU session ID。从而AMF能够获知需要激活的PDU会话。可选地,所述注册请求消息还携带激活标记(Active flag),所述激活标记用于指示所述终端设备需要发送上行数据。
参见图3,以UE将所述指示信息携带在服务请求(Service request)消息(不通过服务类型指示)中发送给New AMF为例,New AMF根据指示信息识别UE处于MICO模式,则在确定本地没有存储UE Context时,不执行服务请求失败流程,而是触发UE上下文恢复(UE context retrieve)流程。在所述指示信息还用于指示所述终端设备的注册区域为all PLMN注册区域时,所述New AMF还可以根据指示信息确定UE的注册区域为all PLMN注册区域。UE在RRC消息中将UE的标识信息上报给RAN,并由AN上报给AMF。
S301,UE通过第一RRC消息向RAN发送UE的标识信息;
S302,UE通过第二RRC消息向RAN发送服务请求(Service request),其中服务请求中携带指示信息。
可选的,服务请求中还可以携带PDU会话ID(PDU session ID)(即待激活的PDU会话的标识)。
其中,第一RRC消息和第二RRC消息可以同一个消息也可以为不同的消息。
S303,RAN在接收到UE的标识信息以及所述指示信息后,根据所述UE的标识信息确定为UE服务的old AMF,并向old AMF发送UE的标识信息以及所述指示信息。RAN可以通过N2消息向old AMF发送UE的标识信息以及所述指示信息。如果RAN根据UE的标识信息无法连接到为UE服务的old AMF时,可以根据选择AMF的策略,比如根据各个AMF的负载信息,为UE选择一个New AMF。图3中以RAN根据UE的标识信息无法连接到为UE服务的old AMF的情况为例,从而,RAN向New AMF发送所述UE的标识信息以及所述指示信息。在服务请求中携带待激活的PDU会话ID时,所述RAN还将待激活的PDU会话ID发送给New AMF。
S304,New AMF根据所述指示信息识别UE处于MICO模式,则判断本地是否存储有该UE的上下文信息,若判断有,则继续执行Idle转connected的流程,若本地没有存储该UE的上下文,不去执行服务请求失败流程,而是触发UE上下文恢复流程,即New AMF根据UE的标识信息确定old AMF,向old AMF发送请求(比如UE context request)获取UE的上下文。其中,UE context request中携带UE的标识信息以及所述Service request消息。在所述指示信息还用于指示所述终端设备的注册区域为all PLMN注册区域时,所述New AMF还可以根据指示信息确定UE的注册区域为all PLMN注册区域。
或者,在new AMF判断本地没有存储该UE的上下文信息时,还可以向UDSF发送请求获取该UE的上下文信息。
可选地,old AMF在接收到UE context request后,Old AMF可以对Service request消息进行安全性验证(Security Verification of Service request),成功则向New AMF返回UE context。或者,old AMF在接收到UE context request后,直接向New AMF返回UE context。
S305,Old AMF向New AMF返回UE context。比如,Old AMF通过UE上下文响应(UE
context response)消息向New AMF返回UE context。
可选地,New AMF在接收到Old AMF发送的UE context后,还可以执行S306。
S306,New AMF向UE发送服务请求接受(Service request Accept)消息。
或者,New AMF可以通过步骤S309的N2message和S310的RRC消息将该服务请求接受(Service request Accept)消息发送给UE。
可选的,所述方法还包括:
S307、New AMF根据UE指示的PDU会话ID(PDU session ID)(即待激活的PDU会话的标识),通过N11接口信令(N11message)向对应的SMF发送待激活的PDU session ID,以使得SMF激活该PDU session。
S308,SMF通过N11接口信令向New AMF返回N2SM信息,N2SM信息包括QoS信息(QoS profile)以及核心网N3隧道信息(CN N3Tunnel Info)。其中,该CN N3tunnel Info用于RAN将该UE的数据正确地发送到对应的UPF;QoS profile包括了该PDU session ID对应的PDU session的所有QoS流(QoS flow)所对应的QoS参数信息,用于RAN建立空口承载。
S309,New AMF将从SMF收到的N2SM信息以及其它一些信息(比如:安全上下文security context,切换限制列表Handover Restriction List等)通过N2接口信令(N2message)发送给RAN。N2message比如是N2request。
S310,RAN基于待激活的PDU sessions的QoS profile,RAN与UE进行RRC连接重配置(RRC Connection Reconfiguration)流程,同时建立UE和RAN之间的安全连接。
S311,RAN通过N2request ACK(确认)消息向New AMF返回N2SM信息(informat ion)。其中N2SM information中包括N3隧道信息(N3Tunnel info)、接受激活的PDU会话的QoS Flow(List of accepted QoS Flows for the PDU Sessions activated)、拒绝激活的PDU会话的QoS Flow(List of rejected QoS Flows for the PDU Sessions activated)。
S312,New AMF将N2SM information发送给对应的SMF。具体的,New AMF通过N11接口信令(N11message)将N2SM information发送给对应的SMF。
可选地,如果部署了动态策略控制和计费(英文:Policy Control and Charging,简称:PCC)策略,则执行S313,SMF可能会发起IP连接访问网络会话调整(IP-Connectivity Access Network Session Modification,IP-CAN Session Modification)。
S314,SMF与UPF之间执行N4信息更新流程(N4message update procedure),具体是将RAN N3tunnel information配置到UPF上,该RAN N3tunnel information用于UPF将该UE的数据正确地发送到对应的RAN。
可选地,SMF与UPF之间执行N4信息更新流程之后,执行S315。
S315、SMF向New AMF返回对应于S311的N11接口信令的Ack消息(N11message ACK)。
参见图4,以UE将所述指示信息携带在服务请求(Service request)消息(通过服务类型指示)中发送给New AMF为例,New AMF根据服务类型识别UE处于MICO模式,则在确定本地没有存储UE Context时,不执行服务请求失败流程,而是触发UE上下文恢复(UE context retrieve)流程。UE在RRC消息中将UE的标识信息上报给RAN,并由AN上报给AMF。在所述指示信息还用于指示所述终端设备的注册区域为all PLMN注册区域时,所述New还可以用根据指示信息确定UE的注册区域为all PLMN注册区域。
S401,UE在处于MICO模式并触发上行数据传输时,UE将服务请求中的服务类型
(Service type)设置为“MICO数据服务”(“MICO packet service”)。
S402,UE通过RRC消息向RAN发送服务请求(Service request)以及UE的标识信息。在该实施例中,以UE将服务请求以及UE的标识信息配置在同一RRC消息中发送给RAN为例。
可选的,服务请求中还可以携带待激活的PDU会话ID(PDU session ID)(即待激活的PDU会话的标识)。
S403,RAN在接收到UE的标识信息以及所述服务请求后,根据所述UE的标识信息确定为UE服务的Old AMF,并向Old AMF发送UE的标识信息以及所述指示信息。RAN可以通过N2消息向Old AMF发送UE的标识信息以及所述指示信息。如果RAN根据UE的标识信息无法连接到为UE服务的Old AMF时,可以根据预配置的选择AMF的策略,比如根据各个AMF的负载信息,为UE选择一个New AMF。图4中以RAN根据UE的标识信息无法连接到为UE服务的old AMF的情况为例,从而,RAN向New AMF发送所述UE的标识信息以及所述指示信息。在服务请求中携带待激活的PDU会话ID时,所述RAN还将待激活的PDU会话ID发送给New AMF。
S404,New AMF根据服务请求中的服务类型(MICO Packet service)识别UE处于MICO模式,则判断本地是否存储有该UE的上下文信息,若判断有,则继续执行Idle转connected的流程,若本地没有存储该UE的上下文,不去执行服务请求失败流程,而是触发UE上下文恢复流程,即New AMF根据UE的标识信息确定old AMF,向old AMF发送请求(比如UE context request)获取UE的上下文。其中,UE context request中携带UE的标识信息以及所述Service request消息。
或者,在new AMF判断本地没有存储该UE的上下文信息时,还可以向UDSF发送请求获取该UE的上下文信息。
可选地,old AMF在接收到UE context request后,Old AMF可以对Service request消息进行安全性验证(Security Verification of Service request),成功则向New AMF返回UE context。或者,old AMF在接收到UE context request后,直接向New AMF返回UE context。
S405,Old AMF向New AMF返回UE context。
可选地,New AMF在接收到Old AMF发送的UE context后,还可以执行S406。
S406,New AMF向UE发送服务请求接受(Service request Accept)消息。
可选的,所述方法还包括步骤S407至S415。其中步骤S407至S415可参见图3中步骤S307至S315,此处不再赘述。
可选地,New AMF向UE发送服务请求接受(Service request Accept)消息时,New AMF也可以通过步骤S409的N2message和S410的RRC消息将该服务请求接受(Service request Accept)消息发送给UE。
参见图5所示,以UE将所述指示信息和UE的标识信息携带在服务请求(Service request)消息(不通过服务类型指示)中发送给New AMF为例,New AMF根据指示信息识别UE处于MICO模式,则在确定本地没有存储UE Context时,不执行服务请求失败流程,而是触发UE上下文恢复(UE context retrieve)流程。UE通过RRC消息将UE的第二标识(例如,5G S-TMSI)发送给RAN,用于RAN选择AMF。在所述指示信息还用于指示
所述终端设备的注册区域为all PLMN注册区域时,所述New还可以用根据指示信息确定UE的注册区域为all PLMN注册区域。
S501,UE通过第一RRC消息向RAN发送UE的第二标识(例如,5G临时移动用户标识(英文:Serving–Temporary Mobile Subscriber Identity,简称:S-TMSI))发送给RAN。第二标记用于RAN选择AMF。
S502,UE通过第二RRC消息向RAN发送服务请求(Service request),其中,服务请求中携带所述指示信息以及UE的标识信息。
可选的,服务请求中还可以携带PDU会话ID(PDU session ID)(即待激活的PDU会话的标识)。
其中,第一RRC消息和第二RRC消息可以同一个消息也可以为不同的消息。
S503,RAN在接收到服务请求以及UE的第二标识后,根据服务请求中所述UE的标识信息确定为UE服务的old AMF,并向old AMF发送UE的标识信息以及所述指示信息。RAN可以通过N2消息向old AMF发送UE的标识信息以及所述指示信息。如果RAN根据UE的标识信息无法连接到为UE服务的old AMF时,可以根据第二标识选择New AMF,或者,根据选择AMF的策略,比如根据各个AMF的负载信息,为UE选择一个New AMF。图5中以RAN根据UE的标识信息无法连接到为UE服务的old AMF的情况为例,从而,RAN向New AMF发送所述UE的标识信息以及所述指示信息。在服务请求中携带待激活的PDU会话ID时,所述RAN还将待激活的PDU会话ID发送给New AMF。
S504,New AMF根据所述指示信息识别UE处于MICO模式,则判断本地是否存储有该UE的上下文信息,若判断有,则继续执行Idle转connected的流程,若本地没有存储该UE的上下文,不去执行服务请求失败流程,而是触发UE上下文恢复流程,即New AMF根据UE的标识信息确定old AMF,向old AMF发送请求(比如UE context request)获取UE的上下文。其中,UE context request中携带UE的标识信息以及所述Service request消息。在所述指示信息还用于指示所述终端设备的注册区域为all PLMN注册区域时,所述New AMF还可以根据指示信息确定UE的注册区域为all PLMN注册区域。
或者,在new AMF判断本地没有存储该UE的上下文信息时,还可以向UDSF发送请求获取该UE的上下文信息。
可选地,old AMF在接收到UE context request后,Old AMF可以对Service request消息进行安全性验证(Security Verification of Service request),成功则向New AMF返回UE context。或者,old AMF在接收到UE context request后,直接向New AMF返回UE context。
S505,Old AMF向New AMF返回UE context。比如,Old AMF通过UE上下文响应(UE context response)消息向New AMF返回UE context。
可选地,New AMF在接收到Old AMF发送的UE context后,还可以执行S306。
S506,New AMF向UE发送服务请求接受(Service request Accept)消息。
或者,New AMF可以通过步骤S509的N2message和S510的RRC消息将该服务请求接受(Service request Accept)消息发送给UE。
可选地,所述方法还可以包括S507至S515,其中步骤S507至S515可参见图3中步骤S307至S315,此处不再赘述。
参见图6所示,以UE将所述指示信息和UE标识携带在注册请求消息(所述指示信息
通过注册类型指示)中发送给New AMF为例,New AMF根据指示信息识别UE处于MICO模式,不为UE分配至跟踪区列表(英文:Tracking Area list,简称:TA list),并在确定本地没有存储UE Context时,触发UE上下文恢复(UE context retrieve)流程。在所述指示信息还用于指示所述终端设备的注册区域为all PLMN注册区域时,所述New还可以用根据指示信息确定UE的注册区域为all PLMN注册区域。
S601,UE在处于MICO模式并触发上行数据传输时,UE将注册请求中的注册类型(registration type)设置为“MICO数据注册”(“MICO packet registration”),注册请求中还可以携带UE的标识信息。
S602,UE通过RRC消息向RAN发送注册请求(registration request)。其中,UE还可以在RRC消息中将唯一标识AMF的信息(比如,5G-GUAMFI(global unique AMF ID))通知给RAN;可选地,该唯一标识AMF的信息也可以为UE的标识5G-GUTI,因为5G-GUTI包含了5G-GUAMFI。
可选的,注册请求中还可以携带待激活的PDU会话ID(PDU session ID)(即待激活的PDU会话的标识)。
可选地,注册请求中还可以携带激活标记(Active flag),激活标记用于指示UE需要发送上行数据。
S603,RAN在接收到所述注册请求后,根据所述UE发送的唯一标识AMF的信息,确定为UE服务的old AMF,并向old AMF发送UE的标识信息以及所述指示信息。RAN可以通过N2消息向old AMF发送UE的标识信息以及所述指示信息。
如果RAN根据唯一标识AMF的信息,无法连接到为UE服务的old AMF时,可以根据选择AMF的策略,比如根据各个AMF的负载信息,为UE选择一个New AMF。图6中以RAN根据UE的标识信息无法连接到为UE服务的old AMF的情况为例,从而,RAN向New AMF发送所述注册请求(所述UE的标识信息以及所述指示信息(注册类型))。在所述注册请求中携带待激活的PDU会话ID时,所述RAN还将待激活的PDU会话ID发送给New AMF。
S604,New AMF根据注册请求中的注册类型(MICO Packet registration)识别UE处于MICO模式,则判断本地是否存储有该UE的上下文信息,若判断有,则继续执行Idle转connected的流程,若本地没有存储该UE的上下文,则触发UE上下文恢复流程,即New AMF根据UE的标识信息确定old AMF,向old AMF发送请求(比如UE context request)获取UE的上下文。其中,UE context request中携带UE的标识信息以及所述Registration request消息。在所述指示信息还用于指示所述终端设备的注册区域为all PLMN注册区域时,所述New AMF还可以根据指示信息确定UE的注册区域为all PLMN注册区域。
或者,在new AMF判断本地没有存储该UE的上下文信息时,还可以向UDSF发送请求获取该UE的上下文信息。
可选地,old AMF在接收到UE context request后,Old AMF可以对Registration request消息进行安全性验证(Security Verification of Registration request),成功则向New AMF返回UE context。或者,old AMF在接收到UE context request后,直接向New AMF返回UE context。
S605,Old AMF向New AMF返回UE context。
可选地,New AMF在接收到Old AMF发送的UE context后,还可以执行S606。
S606,New AMF向UE发送注册请求接受(Service request Accept)消息。
可选的,所述方法还包括步骤S607至S615。其中步骤S607至S615可参见图3中步骤S307至S315,此处不再赘述。
可选地,New AMF向UE发送服务请求接受(Service request Accept)消息时,New AMF也可以通过步骤S609的N2message和S610的RRC消息将该服务请求接受(Service request Accept)消息发送给UE。
参见图7所示,UE将所述指示信息和UE标识携带在注册请求消息(不通过注册类型指示)中发送给New AMF为例,New AMF根据指示信息识别UE处于MICO模式,不为UE分配至跟踪区列表(英文:Tracking Area list,简称:TA list),并在确定本地没有存储UE Context时,触发UE上下文恢复(UE context retrieve)流程。在所述指示信息还用于指示所述终端设备的注册区域为all PLMN注册区域时,所述New还可以用根据指示信息确定UE的注册区域为all PLMN注册区域。
S701,UE通过RRC消息向RAN发送注册请求(registration request),其中注册请求中携带所述指示信息以及UE的标识信息。
其中,UE还可以在RRC消息中将唯一标识AMF的信息(比如,5G-GUAMFI(global unique AMF ID))通知给RAN;可选地,该唯一标识AMF的信息也可以为UE的标识5G-GUTI,因为5G-GUTI包含了5G-GUAMFI。
可选的,注册请求中还可以携带待激活的PDU会话ID(PDU session ID)(即待激活的PDU会话的标识)。
另外,注册请求中还可以携带激活标记(Active flag),激活标记用于指示UE需要发送上行数据。
S702,RAN在接收到所述注册请求后,根据所述UE发送的唯一标识AMF的信息,确定为UE服务的old AMF,并向old AMF发送UE的标识信息以及所述指示信息。RAN可以通过N2消息向old AMF发送UE的标识信息以及所述指示信息。如果RAN根据唯一标识AMF的信息,无法连接到为UE服务的old AMF时,可以根据选择AMF的策略,比如根据各个AMF的负载信息,为UE选择一个New AMF。图7中以RAN根据UE的标识信息无法连接到为UE服务的old AMF的情况为例,从而,RAN向New AMF发送所述UE的标识信息以及所述指示信息。在注册请求中携带待激活的PDU会话ID时,所述RAN还将待激活的PDU会话ID发送给New AMF。
S703,New AMF根据注册请求中的注册类型(MICO Packet registration)识别UE处于MICO模式,则判断本地是否存储有该UE的上下文信息,若判断有,则继续执行Idle转connected的流程,若本地没有存储该UE的上下文,则触发UE上下文恢复流程,即New AMF根据UE的标识信息确定old AMF,向old AMF发送请求(比如UE context request)获取UE的上下文。其中,UE context request中携带UE的标识信息以及所述Registration request消息。在所述指示信息还用于指示所述终端设备的注册区域为all PLMN注册区域时,所述New AMF还可以根据指示信息确定UE的注册区域为all PLMN注册区域。
或者,在new AMF判断本地没有存储该UE的上下文信息时,还可以向UDSF发送请求获取该UE的上下文信息。
可选地,old AMF在接收到UE context request后,Old AMF可以对Registration request消息进行安全性验证(Security Verification of Registration request),成功则向New AMF返回UE context。或者,old AMF在接收到UE context request后,直
接向New AMF返回UE context。
S704,Old AMF向New AMF返回UE context。
可选地,New AMF在接收到Old AMF发送的UE context后,还可以执行S705。
S705,New AMF向UE发送注册请求接受(Registration request Accept)消息。
可选的,所述方法还包括步骤S706至S714。其中步骤S706至S714可参见图3中步骤S307至S315,此处不再赘述。
可选地,New AMF向UE发送服务请求接受(Service request Accept)消息时,New AMF也可以通过步骤S708的N2message和S709的RRC消息将该服务请求接受(Service request Accept)消息发送给UE。
本申请实施例中,处于MICO模式的终端设备在需要发送上行数据时,还可以向第一移动性管理网元发送待激活的PDU会话的标识和所述终端设备的标识信息,第一移动性管理网元在从终端设备获取到待激活的PDU会话的标识和所述终端设备的标识信息后,在确定所述第一移动性管理网元内不存在所述终端设备的上下文信息时,所述第一移动性管理网元根据所述标识信息,向第二移动性管理网元请求所述上下文信息。所述第一移动管理网元并根据所述待激活的PDU会话的标识,为所述终端设备激活所述PDU会话的标识对应的PDU会话。通过上述方式第一移动性管理网元获取到终端设备的上下文信息后,不需要重新发起新的注册请求流程,减少了终端设备与网络之间的信令交互,降低了终端设备从空闲态转换到连接态的时延。
需要说明的是,可选地,可以通过同一条消息发送待激活的PDU会话的标识和UE的标识信息,或者,还可以通过不同的消息中发送待激活的PDU会话的标识和UE的标识信息。例如,指示信息和UE的标识信息可以均携带在NAS消息中发送,或者均携带在非NAS消息中发送,还可以一个携带在NAS消息发送,一个携带在非NAS消息中发送(比如指示信息在NAS消息中发送,UE的标识在非NAS消息中发送)。比如,第一移动性管理网元从终端设备获取待激活的分组数据单元PDU会话的标识和所述终端设备的标识信息时,可以从基站发送的注册请求消息中,获取待激活的PDU会话的标识和所述终端设备标识信息,即UE将待激活的PDU会话的标识和UE的标识信息携带在注册请求消息中,通过基站发送给第一移动性管理网元。
参见图8所示,UE将待激活的PDU会话的标识和UE标识携带在注册请求消息中发送给New AMF为例,New AMF确定注册请求消息中包括待激活的PDU会话的标识时,需要为所述UE激活所述PDU会话;在确定本地没有存储UE Context时,触发UE上下文恢复(UE context retrieve)流程。在所述指示信息还用于指示所述终端设备的注册区域为all PLMN注册区域时,所述New还可以用根据指示信息确定UE的注册区域为all PLMN注册区域。
S801,UE通过RRC消息向RAN发送注册请求(registration request),其中注册请求中携带待激活的PDU会话的标识(比如:PDU session ID)和所述UE的标识信息。
其中,UE还可以在RRC消息中将唯一标识AMF的信息(比如,5G-GUAMFI(global unique AMF ID))通知给RAN;可选地,该唯一标识AMF的信息也可以为UE的标识5G-GUTI,因为5G-GUTI包含了5G-GUAMFI。
可选地,注册请求中还可以携带激活标记(Active flag),激活标记用于指示UE需要发送上行数据。
S802,RAN在接收到所述注册请求后,根据所述UE发送的唯一标识AMF的信息,确定
为UE服务的old AMF,并向old AMF发送UE的标识信息以及所述指示信息。RAN可以通过N2消息向old AMF发送UE的标识信息以及所述指示信息。
如果RAN根据唯一标识AMF的信息,无法连接到为UE服务的old AMF时,可以根据选择AMF的策略,比如根据各个AMF的负载信息,为UE选择一个New AMF。图7中以RAN根据UE的标识信息无法连接到为UE服务的old AMF的情况为例,从而,RAN向New AMF发送所述UE的标识信息以及所述待激活的PDU会话的标识。
S803,New AMF在接收到待激活的PDU会话的标识以及UE的标识信息后,判断本地是否存储有该UE的上下文信息,若判断有,则继续执行Idle转connected的流程,若本地没有存储该UE的上下文,则触发UE上下文恢复流程,即New AMF根据UE的标识信息确定old AMF,向old AMF发送请求(比如UE context request)获取UE的上下文。其中,UE context request中携带UE的标识信息以及所述Registration request消息。在所述指示信息还用于指示所述终端设备的注册区域为all PLMN注册区域时,所述New AMF还可以根据指示信息确定UE的注册区域为all PLMN注册区域。
或者,在new AMF判断本地没有存储该UE的上下文信息时,还可以向UDSF发送请求获取该UE的上下文信息。
可选地,old AMF在接收到UE context request后,Old AMF可以对Registration request消息进行安全性验证(Security Verification of Registration request),成功则向New AMF返回UE context。或者,old AMF在接收到UE context request后,直接向New AMF返回UE context。
S804,Old AMF向New AMF返回UE context。
可选地,New AMF在接收到Old AMF发送的UE context后,还可以执行S805。
S805,New AMF向UE发送注册请求接受(Registration request Accept)消息。
可选的,所述方法还包括步骤S806至S814。其中步骤S806至S814可参见图3中步骤S307至S315,此处不再赘述。
可选地,New AMF向UE发送服务请求接受(Service request Accept)消息时,New AMF也可以通过步骤S808的N2message和S809的RRC消息将该服务请求接受(Service request Accept)消息发送给UE。
基于与上述方法实施例的同样发明构思,本申请实施例提供了一种状态切换装置,该状态切换装置应用于第一移动性管理网元,参见图9所示,该装置可以实现如图2至图8所示的New AMF所执行的数据传输方法。所述装置包括:
获取模块901,用于从终端设备获取指示信息和所述终端设备的标识信息,所述指示信息用于指示所述终端设备处于只移动终端发起连接MICO模式;
处理模块902,用于确定在所述第一移动性管理网元内不存在所述终端设备的上下文信息;
发送模块903,用于在所述处理模块902确定在所述第一移动性管理网元内不存在所述终端设备的上下文信息时,根据所述指示信息和所述标识信息,向第二移动性管理网元请求所述上下文信息。
在一种可能的实现方式中,所述获取模块901,具体用于:从基站接收请求消息,所述请求消息中携带所述指示信息和所述标识信息。
在一种可能的实现方式中,所述请求消息为服务请求消息或注册请求消息。
在一种可能的实现方式中,所述指示信息为所述服务请求消息的服务类型,所述服务类型为MICO数据服务。
在一种可能的实现方式中,所述指示信息为所述注册请求消息的注册类型,所述注册类型为MICO数据注册。
在一种可能的实现方式中,所述注册请求消息还携带待激活的分组数据单元PDU会话标识。
在一种可能的实现方式中,所述注册请求消息还携带激活标记,所述激活标记用于指示所述终端设备需要发送上行数据。
在一种可能的实现方式中,所述标识信息用于全球唯一识别所述终端设备。
在一种可能的实现方式中,所述处理模块902,还用于:根据所述指示信息确定需要请求所述上下文信息;以及,所述第一移动性管理网元根据所述标识信息确定所述第二移动性管理网元;所述发送模块,具体用于向所述第二移动性管理网元发送UE上下文请求。
在一种可能的实现方式中,所述指示信息还用于指示所述终端设备的注册区域为全公用陆地移动网PLMN注册区域;或者,所述指示信息包括第一指示信息和第二指示信息,所述第一指示信息用于指示所述终端设备处于只移动终端发起连接MICO模式,所述第二指示信息用于指示所述终端设备的注册区域为全公用陆地移动网PLMN注册区域。
可选地,获取模块901,用于从终端设备获取待激活的分组数据单元PDU会话的标识和所述终端设备的标识信息;处理模块902,用于确定在所述第一移动性管理网元内不存在所述终端设备的上下文信息;发送模块903,用于在所述处理模块902确定在所述第一移动性管理网元内不存在所述终端设备的上下文信息时,根据所述标识信息,向第二移动性管理网元请求所述上下文信息。所述处理模块902,还用于根据所述待激活的PDU会话的标识,为所述终端设备激活所述PDU会话的标识对应的PDU会话。
在一种可能的实现方式中,为所述终端设备激活所述PDU会话的标识对应的PDU会话,包括:所述第一移动管理网元向会话管理网元发送所述待激活的PDU会话的标识,以使得所述会话管理网元激活所述PDU会话。
在一种可能的实现方式中,第一移动性管理网元从终端设备获取待激活的分组数据单元PDU会话的标识和所述终端设备的标识信息,包括:所述第一移动性管理网元从基站接收注册请求消息,所述注册请求消息中携带待激活的PDU会话的标识和所述终端设备标识信息。
在一种可能的实现方式中,所述注册请求消息中还携带激活标记,所述激活标记用于指示所述终端设备需要发送上行数据。
本申请实施例中对模块的划分是示意性的,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,另外,在本申请各个实施例中的各功能模块可以集成在一个处理器中,也可以是单独物理存在,也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现,也可以采用软件功能模块的形式实现。
如图10所示,应用于第一移动性管理网元的状态切换装置可以包括通信接口1010、处理器1020以及存储器1030。上述图9所示的单元对应的实体的硬件可以为处理器1020。处理器1020通过通信接口1010收发数据,并用于实现图2~图8中所述的New AMF所执行的方法。在实现过程中,处理流程的各步骤可以通过处理器1020中的硬件的集成逻辑电路或者软件形式的指令完成。处理器1020可以是通用处理器、数字信号处理器、专用集
成电路、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件,可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成,或者用处理器中的硬件及软件模块组合执行完成。处理器1020用于实现上述方法所执行的程序代码可以存储在存储器1030中。存储器1030可以是非易失性存储器,比如硬盘(英文:hard disk drive,缩写:HDD)或固态硬盘(英文:solid-state drive,缩写:SSD)等,还可以是易失性存储器(英文:volatile memory),例如随机存取存储器(英文:random-access memory,缩写:RAM)。存储器1030是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质,但不限于此。
本申请实施例中不限定上述通信接口1010、处理器1020以及存储器1030之间的具体连接介质。本申请实施例在图10中以存储器1030、处理器1020以及通信接口1010之间通过总线1040连接,总线在图10中以粗线表示,其它部件之间的连接方式,仅是进行示意性说明,并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示,图10中仅用一条粗线表示,但并不表示仅有一根总线或一种类型的总线。
基于与上述方法实施例的同样发明构思,本申请实施例提供了一种状态切换装置,该状态切换装置应用于终端设备,参见图11所示,该装置可以实现如图2至图8所示的UE所执行的数据传输方法。所述装置包括:
确定模块1101,用于获知所述终端设备处于只移动终端发起连接MICO模式;
发送模块1102,用于在所述终端设备需要发送上行数据时,向第一移动性管理网元发送指示信息和所述终端设备的标识信息,所述指示信息用于指示所述终端设备处于MICO模式。
在一种可能的实现方式中,所述发送模块1102,具体用于通过基站向所述第一移动性管理网元发送无线资源控制RRC消息,所述RRC消息中携带所述指示信息。
在一种可能的实现方式中,所述发送模块1102,具体用于通过基站向所述第一移动性管理网元发送无线资源控制RRC消息,所述RRC消息中携带所述终端设备的标识信息。
在一种可能的实现方式中,所述标识信息用于全球唯一识别所述终端设备。
在一种可能的实现方式中,所述指示信息还用于指示所述终端设备的注册区域为全公用陆地移动网PLMN注册区域;或者,所述指示信息包括第一指示信息和第二指示信息,所述第一指示信息用于指示所述终端设备处于只移动终端发起连接MICO模式,所述第二指示信息用于指示所述终端设备的注册区域为全公用陆地移动网PLMN注册区域。
在一种可能的实现方式中,所述发送模块1102,具体用于向所述第一移动性管理网元发送请求消息,所述请求消息中携带所述指示信息和/或所述终端设备的标识信息;所述请求消息为服务请求消息或注册请求消息。
在一种可能的实现方式中,所述指示信息为所述服务请求消息的服务类型,所述服务类型为MICO数据服务。
在一种可能的实现方式中,所述指示信息为所述注册请求消息的注册类型,所述注册类型为MICO数据注册。
在一种可能的实现方式中,所述注册请求消息还携带待激活的分组数据单元PDU会话标识。
在一种可能的实现方式中,所述注册请求消息还携带激活标记,所述激活标记用于指示所述终端设备需要发送上行数据。
本申请实施例中对模块的划分是示意性的,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,另外,在本申请各个实施例中的各功能模块可以集成在一个处理器中,也可以是单独物理存在,也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现,也可以采用软件功能模块的形式实现。
如图12所示,应用于终端设备的状态切换装置可以包括收发器1210、处理器1220以及存储器1230。上述图11所示的模块对应的实体的硬件可以为处理器1220。处理器1220通过收发器1210收发数据,并用于实现图2~图8中所述的UE所执行的方法。在实现过程中,处理流程的各步骤可以通过处理器1220中的硬件的集成逻辑电路或者软件形式的指令完成。处理器1220可以是通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件,可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成,或者用处理器中的硬件及软件模块组合执行完成。处理器1220用于实现上述方法所执行的程序代码可以存储在存储器1230中。存储器1230可以是非易失性存储器,比如硬盘(英文:hard disk drive,缩写:HDD)或固态硬盘(英文:solid-state dr ive,缩写:SSD)等,还可以是易失性存储器(英文:volatile memory),例如随机存取存储器(英文:random-access memory,缩写:RAM)。存储器1230是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质,但不限于此。
本申请实施例中不限定上述收发器1210、处理器1220以及存储器1230之间的具体连接介质。本申请实施例在图12中以存储器1230、处理器1220以及收发器1210之间通过总线1240连接,总线在图12中以粗线表示,其它部件之间的连接方式,仅是进行示意性说明,并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示,图12中仅用一条粗线表示,但并不表示仅有一根总线或一种类型的总线。
基于以上实施例,本申请实施例还提供了一种计算机存储介质,该存储介质中存储软件程序,该软件程序在被一个或多个处理器读取并执行时可实现上述实施例提供的测量方法。所述计算机存储介质可以包括:U盘、移动硬盘、只读存储器(Read-Only Memory,ROM)、随机存取存储器(Random Access Memory,RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
本领域内的技术人员应明白,本申请的实施例可提供为方法、系统、或计算机程序产品。因此,本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且,本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器
以产生一个机器,使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中,使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品,该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上,使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理,从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然,本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申请实施例的精神和范围。这样,倘若本申请实施例的这些修改和变型属于本申请权利要求及其等同技术的范围之内,则本申请也意图包含这些改动和变型在内。
Claims (30)
- 一种状态切换方法,其特征在于,包括:第一移动性管理网元从终端设备获取指示信息和所述终端设备的标识信息,所述指示信息用于指示所述终端设备处于只移动终端发起连接MICO模式;如果所述第一移动性管理网元内不存在所述终端设备的上下文信息,所述第一移动性管理网元根据所述指示信息和所述标识信息,向第二移动性管理网元请求所述上下文信息。
- 如权利要求1所述的方法,其特征在于,所述第一移动性管理网元从终端设备获取指示信息和所述终端设备的标识信息,包括:所述第一移动性管理网元从基站接收请求消息,所述请求消息中携带所述指示信息和所述标识信息。
- 如权利要求2所述的方法,其特征在于,所述请求消息为服务请求消息或注册请求消息。
- 如权利要求1至3任一所述的方法,其特征在于,所述第一移动性管理网元根据所述指示信息和所述标识信息,向第二移动性管理网元请求所述上下文信息,包括:所述第一移动性管理网元根据所述指示信息确定需要请求所述上下文信息;以及,所述第一移动性管理网元根据所述标识信息确定所述第二移动性管理网元;所述第一移动性管理网元向所述第二移动性管理网元发送UE上下文请求。
- 如权利要求1至4任一所述的方法,其特征在于,所述方法还包括:所述第一移动性管理网元从所述终端设备获取待激活的分组数据单元PDU会话的标识;所述第一移动性管理网元根据所述待激活的PDU会话的标识,为所述终端设备激活所述PDU会话的标识对应的PDU会话。
- 一种状态切换方法,其特征在于,包括:终端设备获知所述终端设备处于只移动终端发起连接MICO模式;当所述终端设备需要发送上行数据时,所述终端设备向第一移动性管理网元发送指示信息和所述终端设备的标识信息,所述指示信息用于指示所述终端设备处于MICO模式。
- 如权利要求6所述的方法,其特征在于,所述终端设备向第一移动性管理网元发送指示信息,包括:所述终端设备通过基站向所述第一移动性管理网元发送无线资源控制RRC消息,所述RRC消息中携带所述指示信息。
- 如权利要求6或7所述的方法,其特征在于,所述终端设备向第一移动性管理网元发送所述终端设备的标识信息,包括:所述终端设备通过基站向所述第一移动性管理网元发送无线资源控制RRC消息,所述RRC消息中携带所述终端设备的标识信息。
- 如权利要求1至5任一、或6至8任一所述的方法,其特征在于,所述标识信息用于全球唯一识别所述终端设备。
- 如权利要求1至5任一、或6至9任一所述的方法,其特征在于,所述指示信息还用于指示所述终端设备的注册区域为全公用陆地移动网PLMN注册区域;或者,所述指示信息包括第一指示信息和第二指示信息,所述第一指示信息用于指示所述终端设备处于只移动终端发起连接MICO模式,所述第二指示信息用于指示所述终端设备的注册区域为全公用陆地移动网PLMN注册区域。
- 如权利要求6至10任一所述的方法,其特征在于,所述终端设备向第一移动性管理网元发送指示信息和所述终端设备的标识信息,包括:所述终端设备向所述第一移动性管理网元发送请求消息,所述请求消息中携带所述指示信息和/或所述终端设备的标识信息;所述请求消息为服务请求消息或注册请求消息。
- 如权利要求3或11所述的方法,其特征在于,所述指示信息为所述服务请求消息的服务类型,所述服务类型为MICO数据服务。
- 如权利要求3或11所述的方法,其特征在于,所述指示信息为所述注册请求消息的注册类型,所述注册类型为MICO数据注册。
- 如权利要求3、11、或13所述的方法,其特征在于,所述注册请求消息还携带待激活的分组数据单元PDU会话标识。
- 如权利要求3、11、13、或14中任一所述的方法,其特征在于,所述注册请求消息还携带激活标记,所述激活标记用于指示所述终端设备需要发送上行数据。
- 一种状态切换装置,其特征在于,所述状态切换装置应用于第一移动性管理网元,包括:获取模块,用于从终端设备获取指示信息和所述终端设备的标识信息,所述指示信息用于指示所述终端设备处于只移动终端发起连接MICO模式;处理模块,用于确定在所述第一移动性管理网元内不存在所述终端设备的上下文信息;发送模块,用于在所述处理模块确定在所述第一移动性管理网元内不存在所述终端设备的上下文信息时,根据所述指示信息和所述标识信息,向第二移动性管理网元请求所述上下文信息。
- 如权利要求16所述的装置,其特征在于,所述获取模块,具体用于:从基站接收请求消息,所述请求消息中携带所述指示信息和所述标识信息。
- 如权利要求17所述的装置,其特征在于,所述请求消息为服务请求消息或注册请求消息。
- 如权利要求16至18任一所述的装置,其特征在于,所述处理模块,还用于:根据所述指示信息确定需要请求所述上下文信息;以及,所述第一移动性管理网元根据所述标识信息确定所述第二移动性管理网元;所述发送模块,具体用于向所述第二移动性管理网元发送UE上下文请求。
- 如权利要求16至19任一所述的装置,其特征在于,所述获取模块,还用于从所述终端设备获取待激活的分组数据单元PDU会话的标识;所述处理模块,还用于根据所述待激活的PDU会话的标识,为所述终端设备激活所述PDU会话的标识对应的PDU会话。
- 一种状态切换装置,其特征在于,所述装置应用于终端设备,包括:确定模块,用于获知所述终端设备处于只移动终端发起连接MICO模式;发送模块,用于在所述终端设备需要发送上行数据时,向第一移动性管理网元发送指示信息和所述终端设备的标识信息,所述指示信息用于指示所述终端设备处于MICO模式。
- 如权利要求21所述的装置,其特征在于,所述发送模块,具体用于通过基站向所述第一移动性管理网元发送无线资源控制RRC消息,所述RRC消息中携带所述指示信息。
- 如权利要求21或22所述的装置,其特征在于,所述发送模块,具体用于通过基站向所述第一移动性管理网元发送无线资源控制RRC消息,所述RRC消息中携带所述终端设备的标识信息。
- 如权利要求16至20任一、或21至23任一所述的状态切换装置,其特征在于,所述标识信息用于全球唯一识别所述终端设备。
- 如权利要求16至20任一、或21至24任一所述的状态切换装置,其特征在于,所述指示信息还用于指示所述终端设备的注册区域为全公用陆地移动网PLMN注册区域;或者,所述指示信息包括第一指示信息和第二指示信息,所述第一指示信息用于指示所述终端设备处于只移动终端发起连接MICO模式,所述第二指示信息用于指示所述终端设备的注册区域为全公用陆地移动网PLMN注册区域。
- 如权利要求21至25任一所述的状态切换装置,其特征在于,所述发送模块,具体用于向所述第一移动性管理网元发送请求消息,所述请求消息中携带所述指示信息和/或所述终端设备的标识信息;所述请求消息为服务请求消息或注册请求消息。
- 如权利要求18或26所述的状态切换装置,其特征在于,所述指示信息为所述服务请求消息的服务类型,所述服务类型为MICO数据服务。
- 如权利要求18或26所述的状态切换装置,其特征在于,所述指示信息为所述注册请求消息的注册类型,所述注册类型为MICO数据注册。
- 如权利要求18、26、或28所述的状态切换装置,其特征在于,所述注册请求消息还携带待激活的分组数据单元PDU会话标识。
- 如权利要求18、26、28、或29中任一所述的状态切换装置,其特征在于,所述注册请求消息还携带激活标记,所述激活标记用于指示所述终端设备需要发送上行数据。
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2017/083515 WO2018205114A1 (zh) | 2017-05-08 | 2017-05-08 | 一种状态切换方法及装置 |
EP17908850.5A EP3614707B1 (en) | 2017-05-08 | 2017-05-08 | State switching method and apparatus |
CN202110429023.4A CN113316223B (zh) | 2017-05-08 | 2017-05-08 | 一种状态切换方法及装置 |
CN201780040935.4A CN109417699B (zh) | 2017-05-08 | 2017-05-08 | 一种状态切换方法及装置 |
US16/678,343 US20200084613A1 (en) | 2017-05-08 | 2019-11-08 | Status switching method and apparatus |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2017/083515 WO2018205114A1 (zh) | 2017-05-08 | 2017-05-08 | 一种状态切换方法及装置 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/678,343 Continuation US20200084613A1 (en) | 2017-05-08 | 2019-11-08 | Status switching method and apparatus |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2018205114A1 true WO2018205114A1 (zh) | 2018-11-15 |
Family
ID=64104198
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2017/083515 WO2018205114A1 (zh) | 2017-05-08 | 2017-05-08 | 一种状态切换方法及装置 |
Country Status (4)
Country | Link |
---|---|
US (1) | US20200084613A1 (zh) |
EP (1) | EP3614707B1 (zh) |
CN (2) | CN109417699B (zh) |
WO (1) | WO2018205114A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2022251993A1 (zh) * | 2021-05-31 | 2022-12-08 | 华为技术有限公司 | 一种标签的管理方法以及相关装置 |
Families Citing this family (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN115190570A (zh) * | 2016-08-11 | 2022-10-14 | 北京三星通信技术研究有限公司 | 对用户设备进行轻连接控制的方法及相应设备 |
CN109005565B (zh) * | 2017-06-06 | 2022-11-04 | 大唐移动通信设备有限公司 | 一种会话管理方法和装置 |
CN111770533B (zh) * | 2017-11-20 | 2022-02-11 | Oppo广东移动通信有限公司 | 一种业务激活及去激活的方法、装置、计算机存储介质 |
WO2019221033A1 (en) | 2018-05-18 | 2019-11-21 | Nec Corporation | A method for synchronizing status of ue in a communication network |
US11388769B2 (en) * | 2019-06-18 | 2022-07-12 | Qualcomm Incorporated | Techniques for communicating management information for mechanisms using wireless communications |
CN112911658B (zh) * | 2019-12-04 | 2022-03-29 | 大唐移动通信设备有限公司 | 一种通信方法及装置 |
CN111405567B (zh) * | 2020-03-18 | 2021-10-08 | 广州爱浦路网络技术有限公司 | 一种amf扩展方法及amf |
CN114449680A (zh) * | 2020-11-06 | 2022-05-06 | 维沃移动通信有限公司 | 连接态建立方法、终端、核心网功能及接入网设备 |
WO2022116015A1 (zh) * | 2020-12-01 | 2022-06-09 | Oppo广东移动通信有限公司 | 数据处理方法、装置、电子设备及存储介质 |
CN117320120A (zh) * | 2022-06-23 | 2023-12-29 | 华为技术有限公司 | 通信方法与装置 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101552980A (zh) * | 2008-03-31 | 2009-10-07 | 华为技术有限公司 | 网络侧分离ue时的处理方法、移动性管理装置及网络系统 |
US20100115275A1 (en) * | 2008-11-03 | 2010-05-06 | Samsung Electronics Co. Ltd. | Security system and method for wireless communication system |
CN104144524A (zh) * | 2013-05-08 | 2014-11-12 | 电信科学技术研究院 | 一种小数据传输方法和演进基站及用户终端 |
Family Cites Families (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP4597234B2 (ja) * | 2008-09-26 | 2010-12-15 | 株式会社エヌ・ティ・ティ・ドコモ | 移動局 |
US8428045B2 (en) * | 2010-03-16 | 2013-04-23 | Harman International Industries, Incorporated | Media clock recovery |
CN103229546B (zh) * | 2010-09-28 | 2017-02-15 | 黑莓有限公司 | 用于在ue移出住宅/企业网络覆盖时释放与本地gw的连接的方法和装置 |
US9413641B2 (en) * | 2013-11-22 | 2016-08-09 | General Dynamics C4 Systems, Inc. | Apparatus and methods for accessing a data network |
US20150189574A1 (en) * | 2013-12-26 | 2015-07-02 | Samsung Electronics Co., Ltd. | Methods for dormant cell signaling for advanced cellular network |
CN105612811B (zh) * | 2014-01-29 | 2020-10-09 | 华为技术有限公司 | 配置方法和通信设备 |
CN105813146B (zh) * | 2014-12-31 | 2020-09-08 | 中兴通讯股份有限公司 | 业务流传输路径优化方法、装置及mme |
CN105429988B (zh) * | 2015-11-30 | 2018-08-24 | 东莞酷派软件技术有限公司 | 基于多业务的ims注册方法和ims注册系统 |
JP7028887B2 (ja) * | 2017-03-20 | 2022-03-02 | エルジー エレクトロニクス インコーポレイティド | 無線通信システムにおいてレイヤ間の相互作用方法及びそのための装置 |
BR112019000582A2 (pt) * | 2017-04-19 | 2019-11-05 | Lg Electronics Inc | método para processamento de procedimento de estabelecimento de sessão de pdu e nó de amf |
AU2018255075B2 (en) * | 2017-04-19 | 2020-02-06 | Lg Electronics Inc. | Method for processing PDU session establishment procedure and AMF node |
-
2017
- 2017-05-08 CN CN201780040935.4A patent/CN109417699B/zh active Active
- 2017-05-08 CN CN202110429023.4A patent/CN113316223B/zh active Active
- 2017-05-08 EP EP17908850.5A patent/EP3614707B1/en active Active
- 2017-05-08 WO PCT/CN2017/083515 patent/WO2018205114A1/zh unknown
-
2019
- 2019-11-08 US US16/678,343 patent/US20200084613A1/en not_active Abandoned
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101552980A (zh) * | 2008-03-31 | 2009-10-07 | 华为技术有限公司 | 网络侧分离ue时的处理方法、移动性管理装置及网络系统 |
US20100115275A1 (en) * | 2008-11-03 | 2010-05-06 | Samsung Electronics Co. Ltd. | Security system and method for wireless communication system |
CN104144524A (zh) * | 2013-05-08 | 2014-11-12 | 电信科学技术研究院 | 一种小数据传输方法和演进基站及用户终端 |
Non-Patent Citations (1)
Title |
---|
See also references of EP3614707A4 * |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2022251993A1 (zh) * | 2021-05-31 | 2022-12-08 | 华为技术有限公司 | 一种标签的管理方法以及相关装置 |
Also Published As
Publication number | Publication date |
---|---|
US20200084613A1 (en) | 2020-03-12 |
EP3614707A1 (en) | 2020-02-26 |
CN113316223A (zh) | 2021-08-27 |
CN109417699A (zh) | 2019-03-01 |
EP3614707A4 (en) | 2020-02-26 |
CN109417699B (zh) | 2022-01-14 |
CN113316223B (zh) | 2022-10-18 |
EP3614707B1 (en) | 2021-03-31 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2018205114A1 (zh) | 一种状态切换方法及装置 | |
US12015682B2 (en) | Service subscription method and system for reporting service change in communication system | |
US10764951B2 (en) | Registration method of user terminal in wireless communication system and apparatus therefor | |
CN112996087B (zh) | 一种网络切片选择方法、终端设备及网络设备 | |
EP3669591B1 (en) | Network entity, user equipment and method for the control and use of network slices | |
WO2019137286A1 (zh) | 一种本地数据网络的指示方法及装置 | |
US20190037636A1 (en) | Method for transmitting/receiving location registration-related message in wireless communication system and apparatus for same | |
US20190104455A1 (en) | Method for changing connection mode in base station, and base station therefor, and method for changing connection mode in user equipment, and user equipment thereof | |
WO2017079906A1 (zh) | 选择服务网络的方法、网络设备和管理设备 | |
EP3592033A1 (en) | Communication method and device | |
CN109819485B (zh) | 一种通信方法、装置及系统 | |
JP7389225B2 (ja) | セキュリティ保護モードを決定するための方法および装置 | |
CN110913439A (zh) | 一种网元选择方法及装置 | |
EP4044630A1 (en) | Communication method, apparatus, and device | |
CN114175770B (zh) | 利用接入和移动性管理功能重新分配进行注册的方法 | |
WO2021031065A1 (en) | A method of registration with access and mobility management function re-allocation | |
CN111867057A (zh) | 通信方法、装置和系统 | |
WO2019037500A1 (zh) | 一种选择无线接入网设备的方法及装置 | |
CN110691427B (zh) | 一种业务传输方法及装置 | |
US20160135063A1 (en) | Method and apparatus for controlling of ddn message, and computer readable medium for the same | |
EP4080911A1 (en) | Method and apparatus for tracking area topology | |
RU2783840C2 (ru) | Пользовательское устройство, сетевое устройство и способ радиосвязи |
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: 17908850 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: 2017908850 Country of ref document: EP Effective date: 20191119 |