WO2018165974A1 - 面向网络切片的用户设备状态信息管理方法及装置 - Google Patents

面向网络切片的用户设备状态信息管理方法及装置 Download PDF

Info

Publication number
WO2018165974A1
WO2018165974A1 PCT/CN2017/077056 CN2017077056W WO2018165974A1 WO 2018165974 A1 WO2018165974 A1 WO 2018165974A1 CN 2017077056 W CN2017077056 W CN 2017077056W WO 2018165974 A1 WO2018165974 A1 WO 2018165974A1
Authority
WO
WIPO (PCT)
Prior art keywords
user equipment
network device
slice
access node
slave
Prior art date
Application number
PCT/CN2017/077056
Other languages
English (en)
French (fr)
Inventor
乔晓强
李岩
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2017/077056 priority Critical patent/WO2018165974A1/zh
Publication of WO2018165974A1 publication Critical patent/WO2018165974A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery

Definitions

  • the embodiments of the present invention relate to the field of wireless communications technologies, and in particular, to a user equipment state information management method and apparatus for network slicing.
  • Network slicing enables multiple services to share a set of broadband network infrastructure while maintaining a relatively independent implementation of services by creating multiple independent, dedicated virtual sub-networks in the same physical network.
  • network segmentation can be used to implement services such as mobile broadband, multimedia, Massive Machine Type Communication, and Critical Machine Type Communication.
  • the user equipment may attach a single network slice or may be attached to multiple network slices.
  • different network slices can be completely isolated on logical resources and logical functions, and only shared on physical resources.
  • the UE is connected to the first core network slice and the second core network slice instantiated in the core network through an access network (AN), wherein the first core network slice and the second core network Slices share physical resources and include complete independent control planes and user plane functions in logical functions.
  • AN access network
  • a multi-slice management method based on master-slave relationship is proposed in the related method. That is, the UE is attached to multiple network slices, one of which is a primary slice, for example, the network slice that the UE first attaches is a primary slice, and other slices except the primary slice are dependent slices, and the UE notifies when attached to the dependent slice. Main slice.
  • the current implementation lacks considerations on how to maintain and manage the UE state. If each network slice cannot properly maintain the state of the UE, it may cause repeated paging when the downlink packet arrives. For example, multiple network slices simultaneously initiate a paging process; or cause unnecessary paging procedures, for example, the current slice needs to initiate a paging process, but in fact other network slices are in the process of doing business, and there is no need to initiate a search. call.
  • the embodiment of the invention provides a user equipment state information management method and device for network slicing, so as to implement management and maintenance of the UE state in the multi-slice management mode of the master-slave slice.
  • an embodiment of the present invention provides a user equipment status information management method for network segmentation, including:
  • the first network device corresponding to the first slave slice When the first network device corresponding to the first slave slice receives the downlink data notification message of the user equipment, the first network device sends a paging request message to the second network device corresponding to the primary slice.
  • the first network device establishes the user equipment by using the access node indicated by the access node information a connection of the first slave slice, and identifying a state of the user equipment of the first slave slice as an active state;
  • the user equipment has established a connection with the first slave slice.
  • the UE status of each dependent slice is maintained by the primary slice.
  • the dependent slice When one of the dependent slices receives the downlink data, the dependent slice first interacts with the primary slice, if the UE has been connected with other dependent slices.
  • the ingress node establishes a connection, and the primary slice sends the access node information of the UE to the current slave slice (corresponding to the first slave slice), so that the current slave slice is directly connected to the UE through the corresponding access node, only in the UE and all the dependent slices.
  • the current slave slice In the case of no connection, the current slave slice needs to initiate a paging process, thereby avoiding unnecessary paging.
  • the method further includes:
  • the first network device pages the user equipment by using each access node
  • the first network device After the first network device establishes a connection between the user equipment and the first slave slice by one of the access nodes, the first network device slices the first slave The status of the user equipment is identified as an activated status;
  • the user equipment has established a connection with the first slave slice.
  • the first network device when the paging response message received by the first network device from the second network does not carry the access node information currently accessed by the user equipment, the first network device establishes by using a paging mode.
  • the first slave slice is connected to the user equipment, and sends the second notification information and the access node information of the user equipment and the first slave slice to the second network device, so that the management of the slave slice state by the primary slice can be implemented.
  • the method further includes:
  • the first network device establishes a connection between the user equipment and the first slave slice by using an access node that sends the service request message, and identifies the user equipment status of the first slave slice as an active state. ;
  • the first network device when the user side initiates a service request, the first network device establishes a connection between the user equipment and the first slave slice by using the access node that sends the service request message, and the user equipment of the first slave slice is set.
  • the status identifier is an active state, and the third notification information and the access node information that the user equipment is connected to the first slave slice are sent to the second network device, so that the management of the slave slice status by the primary slice can be implemented.
  • the method further includes:
  • the first network device When the first network device receives the context release complete message of the user equipment, the first network device deletes the access node information that the user equipment is connected to the first slave slice, and the The status of the user equipment of a slave slice is identified as an idle state;
  • the first network device sends, to the second network device, fourth notification information and access node information released by the user equipment, where the fourth notification information is used to notify the second network device: the user equipment The connection to the first dependent slice has been released.
  • the first network device after the first network device releases the connection between the user equipment and the slave slice, the first network device sends the fourth notification information and the access node information released by the user equipment to the second network device.
  • the main slice manages the state of the slave slice.
  • an embodiment of the present invention provides a user equipment status information management method for network segmentation, including:
  • the second network device sends a paging response message to the first network device, where the paging response is when the second network device has stored the access node information currently accessed by the user equipment.
  • the message carries the access node information, where the access node information is used for establishing the connection between the user equipment and the first slave slice;
  • the user equipment has established a connection with the first slave slice.
  • an embodiment of the present invention provides a user equipment status information management method for network segmentation, including:
  • the second network device After the second network device establishes the connection between the user equipment and the primary slice by one of the access nodes, the second network device will use the user of the primary slice The status of the device is identified as active.
  • the primary slice maintains the UE status of each dependent slice, and the status of each dependent slice remains the same.
  • the dependent slice passes.
  • the primary slice initiates a paging procedure, and other dependent slices also establish a connection with the UE through the node accessed by the primary slice, so that the UEs under all slices are in an active state.
  • the paging process is initiated by the primary slice, and when multiple downlinks receive downlink data, a paging process needs to be initiated, thereby avoiding repetition and no The necessary paging.
  • the method further includes:
  • the second network device establishes a connection between the user equipment and the primary slice by using the access node that sends the service request message, and identifies a status of the user equipment of the primary slice as an activated state;
  • the second network device further forwards the service request message to the network device corresponding to each of the subordinate slices, so that the network device corresponding to each of the subordinate slices respectively is established by using an access node that sends the service request message
  • the connection of the respective slave slices to the user equipment, and the status of the user equipment of the respective slave slices are identified as an active state.
  • the UE status of each subordinate slice is maintained by the primary slice, and the UE status of each slice remains the same.
  • the primary slice forwards the service request message to each subordinate slice to
  • Each of the dependent slices is made to establish a connection with the UE, and each of the dependent slices identifies the state of the UE as an active state, thereby maintaining consistency of UE states under the respective dependent slices.
  • the method further includes:
  • the second network device releases the user plane resource of the user equipment under the primary slice
  • the second network device When the second network device receives the context release complete message of the user equipment, the second network device deletes the context information of the user equipment, and identifies the user equipment status of the primary slice as idle. And the Context Release Complete message is forwarded to the network device corresponding to each of the Dependent Slices, so that the network device corresponding to each of the Dependent Slices deletes the context information of the user equipment and identifies the user equipment status. Is idle.
  • the primary slice uniformly maintains the state of each dependent slice, and the status of each dependent slice remains the same.
  • the access node initiates the release process of the S1 connection, it indicates that all the S1 connections of the UE connected by the UE are connected. Release is to be performed, and each slice (including the primary slice and the dependent slice) identifies the UE state as idle, thereby ensuring consistency of UE status, avoiding repeated and unnecessary paging in the paging process
  • the embodiment of the present invention provides a network device-oriented user equipment state information management apparatus, where the apparatus has the first aspect method.
  • the function of the first network device behavior may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the device comprises:
  • a sending unit configured to: when the receiving unit receives the downlink data notification message of the user equipment, send a paging request message to the second network device corresponding to the primary slice;
  • the receiving unit is further configured to receive a paging response message from the second network device;
  • a paging connection unit configured to establish, by the access node indicated by the access node information, the user equipment and the location when the paging response message carries the access node information currently accessed by the user equipment Determining a connection of the first slave slice, and identifying a state of the user equipment of the first slave slice as an active state;
  • the sending unit is further configured to send, to the second network device, first notification information, and access node information that is connected to the first slave slice by the user equipment, where the first notification information is used to notify the A second network device: the user equipment has established a connection with the first slave slice.
  • the paging connection unit is further configured to:
  • the paging response message does not carry the access node information currently accessed by the user equipment, paging the user equipment by using each access node; when accessing through one of the access nodes After the node establishes the connection between the user equipment and the first slave slice, the state of the user equipment of the first slave slice is identified as an active state;
  • the sending unit is further configured to send, to the second network device, second notification information, and access node information that is connected to the first slave slice by the user equipment, where the second notification information is used to notify the Two network devices: the user equipment has established a connection with the first slave slice.
  • the status of the user equipment of the first slave slice is identified as an idle state
  • the receiving unit is further configured to receive, by the access node, a service request message that the user equipment accesses the first slave slice;
  • the paging connection unit is further configured to establish, by the access node that sends the service request message, a connection between the user equipment and the first slave slice, and set the user equipment status of the first slave slice Identification Active state
  • the sending unit is further configured to send, to the second network device, third notification information, and access node information that is connected to the first slave slice by the user equipment, where the third notification information is used to notify the A second network device: the user equipment has established a connection with the first slave slice.
  • the receiving unit is further configured to receive a context release request message, where the context release request message is used to request to release the user equipment to connect with the first slave slice;
  • the sending unit is further configured to send a context release command of the user equipment to the access node that sends the context release request message;
  • the paging connection unit is further configured to delete the access node information that is connected to the first slave slice by the user equipment, and The state identifier of the user equipment of the first slave slice is an idle state;
  • the sending unit is further configured to send the fourth notification information and the access node information released by the user equipment to the second network device, where the fourth notification information is used to notify the second network device: The user equipment has released the connection to the first dependent slice.
  • the apparatus comprises a processor and a transceiver, the transceiver being configured to perform respective functions of the transmitting unit and the receiving unit, the processor being configured to perform the seeking Call the function of the connection unit. Also included in the apparatus is a memory for coupling with a processor that retains program instructions and data necessary for the apparatus.
  • the embodiment of the present invention provides a network device-oriented user equipment state information management apparatus, where the apparatus has the second aspect method.
  • the function of the second network device behavior may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the device comprises:
  • a receiving unit configured to receive a paging request message from a first network device corresponding to the first slave slice
  • a sending unit configured to send a paging response message to the first network device, where the paging response message is when the second network device has stored access node information currently accessed by the user equipment Carrying the access node information, where the access node information is used for establishing the connection between the user equipment and the first slave slice;
  • the receiving unit is further configured to receive, by the first network device, notification information, and access node information that is connected to the first slave slice by the user equipment, where the notification information is used to notify the second network device
  • the user equipment has established a connection with the first slave slice.
  • the apparatus comprises a processor and a transceiver, the transceiver being configured to perform respective functions of the transmitting unit and the receiving unit, the processor being configured to control the transmitting The unit and the receiving unit perform respective functions. Also included in the apparatus is a memory for coupling with a processor that retains program instructions and data necessary for the apparatus.
  • the network device-oriented user equipment status information management party of the third aspect is implemented.
  • the embodiment of the present invention provides a user equipment status information management apparatus for network slicing, and the apparatus has the function of implementing the behavior of the second network equipment in the method of the third aspect.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the device comprises:
  • a receiving unit configured to receive a paging request message from a first network device corresponding to the first slave slice
  • a sending unit configured to send, to each access node, a paging message for paging the user equipment
  • a slice connecting unit configured to identify a state of the user equipment of the primary slice as being activated after establishing, by one of the access nodes, the connection of the user equipment to the primary slice status;
  • a sending unit configured to send access node information of the user equipment to the primary slice to a network device corresponding to each of the slave slices, where the access node information is used to connect the respective slave slice to the user equipment The establishment of.
  • the status of the user equipment of the primary slice and the respective dependent slices is an idle state
  • the receiving unit is further configured to receive, by the access node, a service request message that the user equipment accesses the primary slice;
  • the slice connection unit is further configured to establish, by the access node that sends the service request message, a connection between the user equipment and the primary slice, and identify a status of the user equipment of the primary slice as Activation state
  • the sending unit is further configured to forward the service request message to a network device corresponding to each of the slave segments, so that the network device corresponding to each of the slave segments respectively sends an access node that sends the service request message Establishing a connection of the respective slave slices to the user equipment, and identifying a status of the user equipment of the respective slave slices as an active state.
  • the receiving unit receives a context release request message from an access node, and the sending unit forwards the context release request message to a network device corresponding to each of the respective slave slices;
  • the slice connection unit is further configured to release a user plane resource of the user equipment under the primary slice;
  • the receiving unit is further configured to receive a context release response message of the user equipment from a network device corresponding to each of the slave segments respectively;
  • the sending unit is further configured to send a context release command of the user equipment to the access node that sends the context release request message;
  • the slice connection unit is further configured to: when the receiving unit receives the context release completion message of the user equipment, delete the context information of the user equipment, and identify the user equipment status of the primary slice as an idle state;
  • the sending unit is further configured to: forward the context release complete message to the network device corresponding to each of the slave slices, so that the network device corresponding to each of the slave slices deletes the context information of the user equipment and the identifier The user equipment status is idle.
  • the apparatus comprises a processor and a transceiver, the transceiver being configured to perform respective functions of the transmitting unit and the receiving unit, the processor being configured to perform the slice The function of the connection unit. Also included in the apparatus is a memory for coupling with a processor that retains program instructions and data necessary for the apparatus.
  • an embodiment of the present invention provides a computer readable storage medium having instructions stored therein that, when run on a computer, cause the computer to perform the methods described in the above aspects.
  • an embodiment of the present invention provides a computer program product comprising instructions that, when run on a computer, cause the computer to perform the methods described in the above aspects.
  • the network slice-oriented user equipment state information management method and apparatus of the embodiment of the invention can implement management and maintenance of the UE state in the multi-slice management mode of the master-slave slice.
  • FIG. 1 is a schematic diagram of a UE attaching multiple network slices
  • FIG. 2 is a schematic diagram of multi-slice management based on a master-slave relationship
  • FIG. 3 is a schematic structural diagram of a communication system according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of creating multiple network slices in a physical network of the communication system of FIG. 3;
  • FIG. 5 is a flowchart of a method for managing UE state information oriented to a network slice according to Embodiment 1 of the present invention
  • FIG. 6 is a flowchart of a method for managing UE state information for a network slice according to Embodiment 2 of the present invention.
  • FIG. 7 is a flowchart of a UE state information management method for network slice according to Embodiment 3 of the present invention.
  • FIG. 8 is a flowchart of a UE state information management method for network slice according to Embodiment 4 of the present invention.
  • FIG. 9 is a flowchart of a method for managing UE state information oriented to a network slice according to Embodiment 5 of the present invention.
  • FIG. 10 is a flowchart of a method for managing UE state information for network slice according to Embodiment 6 of the present invention.
  • FIG. 11 is a flowchart of a method for managing UE state information for network slice according to Embodiment 7 of the present invention.
  • FIG. 12 is a schematic structural diagram of a user equipment state information management apparatus for network slicing according to an embodiment of the present invention.
  • FIG. 13 is a schematic structural diagram of another user equipment status information management apparatus for network slicing according to an embodiment of the present disclosure
  • FIG. 14 is a schematic structural diagram of another user equipment status information management apparatus for network slicing according to an embodiment of the present disclosure.
  • FIG. 15 is a schematic structural diagram of a network device according to an embodiment of the present invention.
  • FIG. 3 is a schematic structural diagram of a communication system according to an embodiment of the present invention.
  • the user equipment UE accesses the service network through a Radio Access Network (RAN) and a Core Network (CN).
  • RAN Radio Access Network
  • CN Core Network
  • the technology described in this embodiment of the present invention may be applicable to a Long Term Evolution (LTE) system, or other wireless communication system using various radio access technologies, for example, using code division multiple access, frequency division multiple access, and time division multiple access. , Orthogonal Frequency Division Multiple Access, single carrier frequency division multiple access and other access technology systems.
  • LTE Long Term Evolution
  • Orthogonal Frequency Division Multiple Access single carrier frequency division multiple access and other access technology systems.
  • it can also be applied to the subsequent evolution system using the LTE system, such as the fifth generation 5G system and the like.
  • the user equipment UE may include various handheld devices having wireless communication functions, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to the wireless modem, and various forms of user equipment ( User Equipment, UE), Mobile Station (MS), Terminal, Terminal Equipment, etc.
  • user equipment User Equipment, UE
  • MS Mobile Station
  • Terminal Terminal Equipment
  • a base station is a device deployed in a radio access network to provide a wireless communication function for a UE.
  • the base station may include various forms of macro base stations, micro base stations, relay stations, access points, and the like.
  • the names of devices with base station functions may be different, for example, in an LTE network, called an evolved NodeB (eNB or eNodeB), in the third generation.
  • eNB evolved NodeB
  • eNodeB evolved NodeB
  • 3G network it is called a Node B and so on.
  • a plurality of dedicated virtual sub-networks can be created, each dedicated virtual sub-network as one network slice, and multiple network slices share the physical network of the system shown in FIG.
  • the network shown in FIG. 3 can deploy services such as Mobile Broadband Slice, Massive Machine Type Communication, and Critical Machine Type Communication.
  • multiple slices may be managed according to the multi-slice management method based on the master-slave relationship shown in FIG. 2.
  • the embodiment of the present invention provides a UE state information management method for network slice.
  • FIG. 5 is a flowchart of a method for managing UE state information oriented to a network slice according to Embodiment 1 of the present invention.
  • the UE status in each dependent slice is maintained by the primary slice, and the UE status in each dependent slice may be different.
  • the processing steps of the method include:
  • Step S101 The first network device receives the downlink data notification message.
  • the first network device is a network device corresponding to the first dependent slice, and the first dependent slice is any one of the dependent slices maintained by the primary slice.
  • the downlink data notification message includes information indicating a UE that receives downlink data.
  • Step S102 The first network device sends a paging request message to the second network device.
  • the second network device is a network device corresponding to the primary slice.
  • the paging request message sent by the first network device carries information about the UE.
  • Step S103 After receiving the paging request message, the second network device sends a paging response message to the first network device.
  • the paging response message carries the access node information, where the access node information is used by the UE Establishment of a connection with the first dependent slice.
  • the paging response message does not carry the access node information currently accessed by the UE.
  • the access node information corresponding to the UE may be the access node information that the UE accesses the second dependent slice.
  • the primary slice maintains the UE status of each dependent slice.
  • the first dependent slice and the second dependent slice are both dependent slices maintained by the primary slice, and the second dependent slice is any dependent slice maintained by the primary slice that is distinct from the first dependent slice.
  • the number of the second dependent slices may be one or more.
  • Step S104 The first network device receives the paging response message from the second network device, and determines whether the paging response message carries the access node information currently accessed by the UE, if the paging response message carries the If the access node information currently accessed by the UE is performed, the subsequent step S105 is performed; if the paging response message does not carry the access node information currently accessed by the UE, step S106 is performed.
  • Step S105 The first network device establishes a connection between the UE and the first slave slice by using an access node indicated by the access node information, and identifies a state of the UE of the first slave slice as an active state. And perform the subsequent step S107.
  • Step S106 The first network device pages the UE by using each access node. After the first network device establishes the connection between the UE and the first slave slice by one of the access nodes, the first network device will slice the first slave The UE status is identified as an active state, and a subsequent step S107 is performed.
  • Step S107 The first network device sends notification information to the second network device, and access node information that is connected to the first slave slice by the user equipment, where the notification information is used to notify the second network.
  • Device The user equipment has established a connection with the first slave slice.
  • the UE status of each dependent slice is maintained by the primary slice.
  • the dependent slice first interacts with the primary slice, if the UE has passed the access node with other dependent slices.
  • the primary slice sends the access node information of the UE to the current dependent slice (corresponding to the first dependent slice), so that the current dependent slice is directly connected to the UE through the corresponding access node, and only the UE and all the dependent slices are not connected.
  • the current slave slice needs to initiate a paging process, thereby avoiding Avoid making unnecessary pages.
  • the first network device and the second network device may be independent network devices, or may be the same network device.
  • the first network device and the second network device are respectively the same network device.
  • Different virtual machines, respectively, are used to manage the first dependent slice and the main slice.
  • each slice including a primary slice and a dependent slice
  • the access node may be connected by an Access and Mobility Management Function (AMF) unit in the access node and the slice.
  • AMF Access and Mobility Management Function
  • the connection between the slice control device and the access node is temporarily referred to as an N2 connection.
  • the N2 connection in the 5G corresponds to the 4G system
  • the access node is connected to the S1 of the MME node.
  • the N2 connection-related protocol in the 5G is not defined.
  • the connection between the access node and the slice may refer to the description of the related term of the S1 connection, and the S1 connection and the N2 connection are not distinguished.
  • FIG. 6 is a flowchart of a UE state information management method for network slice according to Embodiment 2 of the present invention.
  • the UE status of each dependent slice is maintained by the primary slice, and the UE status of each dependent slice may be different.
  • the processing steps of the method shown in Figure 6 include:
  • Step S200 The Tracking Area Update (TAU) process is completed between the UE and the second network device, where the second network device is a network device corresponding to the primary slice.
  • TAU Tracking Area Update
  • Step S201 The first network device receives a Downlink Data Notification message from the user plane device, where the first network device is a network device corresponding to the first slave slice, and the first slave slice is a slave of the primary slice maintenance. Any of the dependent slices in the slice.
  • Step S202 When the first network device determines that the first slave slice is in an idle state, that is, the first slave slice has released the UE S1 context, the first network device sends a paging request (Paging Request) message to the second network device.
  • Paging Request paging request
  • Step S203 The second network device sends a paging response (Paging Response) message to the first network device after receiving the paging request message.
  • Paging Response paging response
  • the paging response message carries the currently accessed access node information of the UE, and step 209 is performed; otherwise, the paging response message is carried in the first device.
  • Information related to paging, such as TAList, etc., and steps 204-208 are performed.
  • Step S204 The first network device needs to initiate a paging process because the paging response message received from the first network device indicates that the current UE does not have an active connection, that is, the first network device sends a paging (Paging). The message is sent to all relevant access nodes.
  • All the related access nodes may be pre-configured by the first network device, or may be requested by the first network device from the second network device.
  • Step S205 Each access node that receives the paging message starts paging the UE.
  • Step S206 The access node that receives the paging response message sent by the UE establishes an RRC connection with the access node if there is no Radio Resource Control (RRC) connection with the UE.
  • RRC Radio Resource Control
  • Step S207 The UE sends a service request (Service Request) message to the access node that establishes the RRC connection, where the service request message carries related information of the first dependent slice, for example, the ID of the first dependent slice or other identifier Information about the first dependent slice.
  • Service Request Service Request
  • Step S208 The access node that receives the service request message sent by the UE forwards the service request message to the first network device.
  • Step S209 The first network device sends a context setup request (Context Setup Request) message to the corresponding access node, where the context setup request message carries relevant context information of the UE.
  • a context setup request Context Setup Request
  • the method for the first network device to determine the corresponding access node includes: if the paging response message received by the first network device in step S203 carries the access node information currently accessed by the UE, the first network device responds according to the paging The current access node information of the UE carried in the message determines the access node.
  • the first network device sends a context establishment request message to the access node that forwards the service request message of the UE.
  • Step S210 Establish a radio bearer between the access node that receives the context setup request message and the UE.
  • Step S211 After the radio bearer is established between the access node and the UE, the access node sends a context setup complete message to the first network device, and the first network device confirms between the UE and the access node according to the context setup complete message.
  • the radio bearer setup is complete.
  • Step S212 The first network device identifies the UE status of the first slave slice as an active state, and sends a UE S1 connection notification message to the second network device, where the UE S1 connection notification message carries: notification information, and the UE and the An access node information connected by a slave slice, the notification information being used to notify the second network device that the user equipment has established a connection with the first slave slice.
  • the second network device may wait for the first After the network device sends the UE S1 connection establishment notification message, the related access node information is directly sent to the requested other slave slice, so that unnecessary paging procedure can be avoided.
  • FIG. 7 is a flowchart of a method for managing UE state information oriented to a network slice according to Embodiment 3 of the present invention.
  • the UE state of each sub-slice is maintained by the main slice, and the UE status of each sub-sliced slice may be different.
  • the method of the embodiment of the present invention is sent by the UE. Connect to the slave slice.
  • the processing steps of the method shown in Figure 7 include:
  • Step S300 If there is no RRC connection between the current UE and the access node, the UE first completes the RRC connection with the access node.
  • Step S301 The UE sends a service request (Service Request) message to the access node that establishes the RRC connection, where the service request message carries related information of the first dependent slice, for example, the ID of the first dependent slice or other identifier Information of the first dependent slice or information enabling the RAN node to select the first network device to the first dependent slice.
  • Service Request Service Request
  • Step S302 The access node forwards the service request message to the first network device.
  • the access node determines the first network device carrying the first dependent slice according to the related information of the first dependent slice in the service request message, and forwards the service request message to the first network device.
  • Step S303 The first network device sends a context setup request (Context Setup Request) message to the access node that forwards the service request message, where the context setup request message carries relevant context information of the UE.
  • a context setup request Context Setup Request
  • Step S304 Establish a radio bearer between the access node that receives the context setup request message and the UE.
  • Step S305 After the radio bearer is established between the access node and the UE, the access node sends a context setup complete message to the first network device, and the first network device confirms between the UE and the access node according to the context setup complete message. The radio bearer setup is complete.
  • Step S306 The first network device identifies the UE status of the first slave slice as an active state, and sends a UE S1 connection notification message to the second network device, where the UE S1 connection notification message carries the notification information and the UE and the first The access node information of the slave slice connection, the notification information is used to notify the second network device that the user equipment has established a connection with the first slave slice.
  • the embodiment of the present invention provides a process for a UE to initiate a service request under the premise that different subordinate slices independently maintain different UE states.
  • a subordinate slice processes a service request of the UE, the status of the subordinate slice is updated to an active state, and the main message is notified.
  • Slice to ensure that the primary slice correctly maintains the UE state of all dependent slices.
  • FIG. 8 is a flowchart of a method for managing UE state information oriented to a network slice according to Embodiment 4 of the present invention.
  • the UE status of each dependent slice is maintained by the primary slice, and the UE status of each dependent slice may be different.
  • the method of the embodiment of the present invention mainly relates to a process of releasing a connection between a slave slice and a UE, as shown in FIG. 8 , including:
  • Step S401 When the connection of the first dependent slice to the UE needs to be released, the access node sends an S1 UE Context Release Request message to the first network device.
  • the access node is an access node to which the UE attaches to the first dependent slice.
  • the access node determines that the interaction between the UE and the first dependent slice is in an idle state, or in the case of O&M intervention, etc., the access node It is determined that the connection of the first dependent slice to the UE needs to be released.
  • Step S402 After receiving the S1 UE context release request message, the first network device releases the corresponding user plane resource, and sends an S1 UE context release command (Context Release Command) to the access node to notify the access node to release and first The slave S1 is connected to the UE S1.
  • S1 UE context release command Context Release Command
  • Step S403 The access node releases the connection with the UE S1 of the first dependent slice, and determines whether the UE has an S1 connection with other dependent slices. If the UE further has an S1 connection with other dependent slices, step S404 is performed; if the access node and the access node The UE S1 connection of the first slave slice is the last S1 connection of the UE, and then step S405 is performed.
  • Step S404 The access node releases the radio bearer of the UE corresponding to the first dependent slice.
  • Step S405 The access node sends an RRC Connection Release message to the UE to notify the UE to release the RRC connection with the access node.
  • Step S406 The access node sends an S1 connection release complete (Release Complete) message to the first network device, and the access node deletes the UE context of the first slave slice; and deletes the UE after receiving the S1 connection release complete message by the first network device.
  • S1 connection release complete Release Complete
  • Step S407 The first network device sends an S1 connection release notification message of the first slave slice to the second network device, where the release notification message may include the notification information and the access node information released by the UE, where the notification information is used. Notifying the second network device that the user equipment has released a connection with the first dependent slice. If all slices have released the S1 connection with the corresponding access node, the second network device deletes all access node information of the UE.
  • the primary slice maintains the UE status of each dependent slice, and the UE status of each dependent slice may be different.
  • the dependent slice updates the status of the UE to idle. The status, while notifying the primary slice, thereby ensuring that the primary slice correctly maintains the UE state of all dependent slices, and when subsequent dependent slices need to handle the paging process, repeated and unnecessary paging can be avoided by interaction with the primary slice.
  • the UE status of each dependent slice is maintained by the primary slice, and the UE status of each dependent slice may be different.
  • a dependent slice may pass The interaction of the main slices to avoid duplication and unnecessary paging.
  • the embodiment of the present invention further provides another UE status information management scheme, in which the primary slice uniformly maintains the UEs of the respective dependent slices. State, the UE status of each slave slice is the same.
  • FIG. 9 is a flowchart of a method for managing UE state information oriented to a network slice according to Embodiment 5 of the present invention.
  • the UE status of each dependent slice is uniformly maintained by the primary slice, and each dependent slice is The UE status is consistent.
  • the processing steps of the method in the embodiment of the present invention include:
  • Step S500 The TAU process is completed between the UE and the second network device, where the second network device is a network device corresponding to the primary slice.
  • Step S501 The first network device receives the downlink data notification message.
  • the first network device is a network device corresponding to the first dependent slice, and the first dependent slice is any one of the dependent slices maintained by the primary slice.
  • the downlink data notification message includes information indicating a UE that receives downlink data.
  • Step S502 When the first network device determines that the first slave slice is in an idle state, that is, the first slave slice has released the UE S1 context, the first network device sends a paging request (Paging Request) message to the second network device.
  • Paging Request paging request
  • Step S503 After receiving the paging request message from the first network device, the second network device sends a paging message for paging the UE to each access node, and only one access node is drawn as an example in FIG. .
  • the respective access nodes may be pre-configured by the second network device, or may be requested by the second network device from other network devices.
  • Step S504 Each access node that receives the paging message starts paging the UE.
  • Step S505 After the second network device establishes the connection between the UE and the primary slice by one of the access nodes, the second network device uses the UE of the primary slice The status ID is active.
  • the process of establishing a connection between the UE and the primary slice by one of the access nodes is performed in S206 to S211 in the second embodiment, where the interaction process with the first network device in steps S206-S211 is changed to The interaction process with the second network device changes the dependent slice to the primary slice.
  • Step S506 The second network device sends, to the network device corresponding to each of the subordinate slices, information about the access node of the UE accessing the primary slice, so that the network devices corresponding to the respective subordinate slices are respectively connected.
  • the ingress node establishes a connection of the respective slave slices with the UE, and identifies the UE status of the respective slave slice as an active state.
  • the first network device receives the access node information of the primary slice sent by the second network device, and establishes a connection between the first dependent slice and the UE by referring to S209-S212, and identifies the UE status of the first dependent slice as active.
  • the process of establishing a connection with the UE by the other sub-slices is the same as the process of establishing the first slave slice with the UE by the first network device, and details are not described herein.
  • the primary slice maintains the UE status of each dependent slice, and the status of each dependent slice remains the same.
  • the dependent slice passes the primary slice.
  • Initiating the paging procedure other slave slices are also established by the node accessed by the primary slice and the UE Connect so that the UEs under all slices are active.
  • the paging process is initiated by the primary slice, and when multiple downlinks receive downlink data, a paging process needs to be initiated, thereby avoiding repetition and no The necessary paging.
  • FIG. 10 is a flowchart of a method for managing UE state information oriented to a network slice according to Embodiment 6 of the present invention.
  • the UE status of each dependent slice is uniformly maintained by the primary slice, and the UE states of the respective dependent slices remain consistent.
  • the processing steps of the method in the embodiment of the present invention include:
  • Step S600 If there is no RRC connection between the current UE and the access node, the UE first completes the RRC connection with the access node.
  • Step S601 The UE sends a service request (Service Request) message to the access node that establishes the RRC connection, where the service request message carries related information of the primary slice, for example, the ID of the primary slice or other information that can identify the primary slice. .
  • Service Request Service Request
  • the service request message sent by the UE is first forwarded by the access node to the primary slice, and then forwarded by the primary slice to other dependent slices.
  • Step S602 The access node sends the received service request message to the second network device, where the second network device is a network device corresponding to the primary slice.
  • Step S603 The second network device establishes a connection between the UE and the primary slice by using the access node that sends the service request message, and identifies a UE status of the primary slice as an activated state.
  • the process of the second network device establishing the primary slice to connect to the UE and the UE status of the primary slice to the active state may refer to S209 to S212, and the difference is that the first network device in S209 to S212 is changed to the second network device.
  • the first dependent slice is changed to the main slice.
  • Step S604 The second network device forwards the service request message to the network device corresponding to each of the subordinate slices, so that the network devices corresponding to the respective subordinate slices respectively establish the subordinate slices by using corresponding access nodes. a connection of the UE, and identifying a UE status of each of the dependent slices as an active state.
  • the first network device corresponding to the first slave slice receives the service request message forwarded by the second network device, and the first network device determines the access node that sends the service request message as the interworking access node, and refers to S209-S212.
  • Establishing a connection between the first dependent slice and the UE, and identifying a UE status of the first dependent slice as an active state, and the process of establishing a connection with the UE by the other dependent slice and establishing a connection between the first dependent slice and the UE by the first network device The same, no longer repeat them.
  • step S603 and step S604 are in no particular order.
  • the UE status of each dependent slice is maintained by the primary slice, and each slice is The UE state is consistent.
  • the primary slice forwards the service request message to each of the dependent slices, so that each of the dependent slices establishes a connection with the UE, and each of the dependent slices identifies the state of the UE as an active state. Thereby the consistency of the UE state under each subordinate slice is maintained.
  • FIG. 11 is a flowchart of a UE state information management method according to Embodiment 7 of the present invention.
  • the UE status of each dependent slice is uniformly maintained by the primary slice, and the UE states of the respective dependent slices remain consistent.
  • the method of the embodiment of the present invention mainly relates to a process of performing a slice release and a UE connection, as shown in FIG. 11 , including:
  • Step S701 When the access node determines that the connection between the UE and each slice needs to be released, the access node sends an S1 UE Context Release Request message to the second network device.
  • the second network device is a network device corresponding to the primary slice, and the access node is an access node to which the UE is attached to each slice.
  • the access node determines that the UE's interaction with all slices is in an idle state, or in the case of O&M intervention, etc., the access node determines that the UE needs to release the connection with each slice.
  • Step S702 The second network device sends the S1 UE context release request message to the network device corresponding to each of the slave slices, so that the network devices corresponding to the respective slave slices release the user plane resources of the corresponding slave slice, when the corresponding slave slice is After the user plane resource is released, the S1 UE context release response message sent by the network device corresponding to each slave slice to the second network device is sent.
  • Step S703 The second network device releases the user plane resource of the UE under the primary slice.
  • Step S704 The second network device sends a context release command of the UE to the access node that sends the context release request message.
  • Step S705 After receiving the context release command of the UE, the access node releases the RRC connection with the UE.
  • Step S706 After releasing the RRC connection with the UE, the access node sends an S1UE context release complete message to the second network device.
  • Step S707 When the second network device receives the context release complete message of the S1 UE, the second network device deletes the context information of the UE, identifies the UE status of the primary slice as an idle state, and, to each dependent slice The corresponding network device forwards the context release complete message of the S1 UE, so that the network device corresponding to each of the respective slave slices deletes the context information of the UE and identifies that the UE state is an idle state.
  • the primary slice uniformly maintains the state of each dependent slice, and the status of each dependent slice remains the same.
  • the access node initiates the release process of the S1 connection, it indicates that all the S1 connections of the UE connected are to be performed.
  • each slice (including the primary slice and the dependent slice) identifies the UE state as an idle state, thereby ensuring consistency of UE state, avoiding repeated and unnecessary paging in the paging flow.
  • FIG. 12 is a schematic structural diagram of a UE state information management apparatus for network slice according to an embodiment of the present invention.
  • the device shown in FIG. 12 is deployed on the first network device corresponding to the first slave slice, and includes:
  • the sending unit 801 is configured to: when the receiving unit 802 receives the downlink data notification message of the user equipment, send a paging request message to the second network device corresponding to the primary slice;
  • the receiving unit 802 is further configured to receive a paging response message from the second network device.
  • a paging connection unit 803 configured to: when the paging response message carries the access node information currently accessed by the user equipment, establish the user equipment by using an access node indicated by the access node information a connection of the first slave slice, and identifying a state of the user equipment of the first slave slice as an active state;
  • the sending unit 801 is further configured to send, to the second network device, first notification information, and access node information that is connected to the first slave slice by the user equipment, where the first notification information is used to notify the Said second network device: said user equipment has established a connection with said first dependent slice.
  • the paging connection unit 803 is further configured to:
  • the paging response message does not carry the access node information currently accessed by the user equipment, paging the user equipment by using each access node; when accessing through one of the access nodes After the node establishes the connection between the user equipment and the first slave slice, the state of the user equipment of the first slave slice is identified as an active state;
  • the sending unit 801 is further configured to: send, to the second network device, second notification information, and access node information that is connected by the user equipment to the first slave slice, where the second notification information is used to notify the Said second network device: said user equipment has established a connection with said first dependent slice.
  • the status of the user equipment of the first slave slice is identified as an idle state
  • the receiving unit 802 is further configured to receive, by the access node, a service request message that the user equipment accesses the first slave slice;
  • the paging connection unit 803 is further configured to establish, by using an access node that sends the service request message, a connection between the user equipment and the first slave slice, and the user equipment of the first slave slice The status identifier is activated.
  • the sending unit 801 is further configured to send, to the second network device, third notification information, and access node information that is connected by the user equipment to the first slave slice, where the third notification information is used to notify the Said second network device: said user equipment has established a connection with said first dependent slice.
  • the receiving unit 802 is further configured to receive a context release request message from the access node, where the context release request message is used to request to release the user equipment to connect with the first slave slice;
  • the sending unit 801 is further configured to send the context release command of the user equipment to the access node that sends the context release request message;
  • the paging connection unit 803 is further configured to delete the access node information that is connected to the first slave slice by the user equipment, and And identifying a status of the user equipment of the first slave slice as an idle state;
  • the sending unit 801 is further configured to send the fourth notification information and the access node information that is released by the user equipment to the second network device, where the fourth notification information is used to notify the second network device: The user equipment has released the connection with the first dependent slice.
  • the UE status of each dependent slice is maintained by the primary slice.
  • the dependent slice first interacts with the primary slice, if the UE has passed the access node with other dependent slices.
  • the primary slice sends the access node information of the UE to the current dependent slice (corresponding to the first dependent slice), so that the current dependent slice is directly connected to the UE through the corresponding node, and only if the UE and all the dependent slices are not connected.
  • the paging process needs to be initiated, so that unnecessary paging can be avoided.
  • FIG. 13 is a schematic structural diagram of another UE state information management apparatus for network slice according to an embodiment of the present invention.
  • the device shown in FIG. 13 is deployed in a second network device corresponding to the primary slice, and includes: a receiving unit 901, a sending unit 902, and a processing unit 903, where the processing unit 903 is configured to control the sending unit 902 and the processing unit 903 to implement the following functions. :
  • the receiving unit 901 is configured to receive a paging request message from the first network device corresponding to the first slave slice.
  • the sending unit 902 is configured to send a paging response message to the first network device, where the paging response message is when the second network device has stored access node information corresponding to the user equipment. Carrying the access node information, where the access node information is used for establishing the connection between the user equipment and the first slave slice;
  • the receiving unit 901 is further configured to receive, by the first network device, notification information, and access node information that is connected to the first slave slice by the user equipment, where the notification information is used to notify the second network.
  • the user equipment has established a connection with the first slave slice.
  • the UE status of each dependent slice is maintained by the primary slice.
  • the dependent slice first interacts with the primary slice, if the UE has passed the access node with other dependent slices.
  • the primary slice sends the access node information of the UE to the current dependent slice (corresponding to the first dependent slice), so that the current dependent slice is directly connected to the UE through the corresponding node, and only if the UE and all the dependent slices are not connected.
  • the paging process needs to be initiated, so that unnecessary paging can be avoided.
  • FIG. 14 is a schematic structural diagram of another user equipment status information management apparatus for network slicing according to an embodiment of the present invention.
  • the device shown in FIG. 14 is deployed on the second network device corresponding to the primary slice, and includes:
  • the receiving unit 1001 is configured to receive a paging request message from the first network device corresponding to the first slave slice.
  • the sending unit 1002 is configured to send, to each access node, a paging message for paging the user equipment.
  • a slice connection unit 1003 configured to identify, after the connection between the user equipment and the primary slice is established by one of the access nodes, the status of the user equipment of the primary slice is Activation state
  • the sending unit 1002 is configured to send, to the network device corresponding to each of the slave slices, access node information of the user equipment to access the primary slice, where the access node information is used by the respective slave slice and the user equipment The establishment of the connection.
  • the status of the user equipment of the primary slice and the respective dependent slices is an idle state
  • the receiving unit 1001 is further configured to receive, by the access node, a service request message that the user equipment accesses the primary slice;
  • the slice connection unit 1003 is further configured to establish, by the access node that sends the service request message, a connection between the user equipment and the primary slice, and identify a status of the user equipment of the primary slice. Active state
  • the sending unit 1002 is further configured to forward the service request message to the network device corresponding to each of the slave segments, so that the network device corresponding to each of the slave segments respectively sends the service request message by using the access
  • the node establishes a connection of the respective slave slices with the user equipment, and identifies a status of the user equipment of the respective slave slices as an active state.
  • the receiving unit 1001 receives a context release request message from an access node, and the sending unit 1002 forwards the context release request message to a network device corresponding to each of the respective slave slices.
  • the slice connection unit 1003 is further configured to release a user plane resource of the user equipment under the primary slice;
  • the receiving unit 1001 is further configured to receive a context release response message of the user equipment from a network device corresponding to each of the slave segments respectively.
  • the sending unit 1002 is further configured to send a context release command of the user equipment to the access node that sends the context release request message;
  • the slice connection unit 1003 is further configured to delete the context information of the user equipment and identify the user equipment status of the primary slice as idle when the receiving unit 1001 receives the context release complete message of the user equipment. status;
  • the sending unit 1002 is further configured to forward the context release complete message to the network device corresponding to each of the slave slices, so that the network device corresponding to each of the slave slices deletes the context information and the identifier of the user equipment.
  • the user equipment status is an idle state.
  • the primary slice maintains the UE status of each dependent slice, and the status of each dependent slice remains the same.
  • the dependent slice passes the primary slice.
  • a paging procedure is initiated, and other slave slices also establish a connection with the UE through the node accessed by the primary slice, so that the UEs under all slices are in an active state.
  • the paging process is initiated by the primary slice, and when multiple downlinks receive downlink data, a paging process needs to be initiated, thereby avoiding repetition and no The necessary paging.
  • the network devices shown in FIG. 12 to FIG. 14 may be different devices or the same devices when actually implemented.
  • the embodiment of the present invention further provides a specific structure of a network device, where the network device is configured to implement the functions of the foregoing first network device and/or the second network device.
  • the network device includes a transmitter/receiver 1101, a controller/processor 1102, a memory 1103, and a communication unit 1104.
  • the transmitter/receiver 1101 is configured to support transmission and reception of information between a network device and a UE, and with other network devices.
  • the controller/processor 1102 performs various functions for communicating with network devices.
  • the uplink signal from the UE or other network element is received via the antenna, coordinated by the receiver 1101, and further processed by the controller/processor 1102 to recover the service data sent by the UE or other network element. And signaling information.
  • traffic data and signaling messages are processed by controller/processor 1102 and mediated by transmitter 1101 to generate downlink signals for transmission to the UE or other network elements via the antenna.
  • the controller/processor 1102 also performs a UE state information management method performed by the first network device and/or the second network device in the solution of the embodiment of the present invention.
  • the memory 1103 is used to store program codes and data of the network device.
  • the communication unit 1104 is configured to support the network device to communicate with other network entities.
  • the controller/processor 1102 in FIG. 15 is independent or through the memory 1103.
  • the transmitter/receiver 1101 is used to implement the functions implemented by the transmitting unit 801 and the receiving unit 802 in FIG.
  • the controller/processor 1102 in FIG. 15 is independent or through the memory 1103.
  • the transmitter/receiver 1101 is used to implement the functions implemented by the transmitting unit 902 and the receiving unit 901 in FIG.
  • the controller/processor 1102 in FIG. 15 is independent or through the memory 1103.
  • the transmitter/receiver 1101 is used to implement the functions implemented by the receiving unit 1001 and the transmitting unit 1002 in FIG.
  • Figure 15 only shows a simplified design of the network device.
  • the network device may include any number of transmitters, receivers, processors, controllers, memories, communication units, etc., and all network devices that can implement the present invention are within the scope of the present invention.
  • the controller/processor for performing the above network device of the present invention may be a central processing unit (CPU), a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), and a field programmable gate array (FPGA). Or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the steps of a method or algorithm described in connection with the present disclosure may be implemented in a hardware, or may be implemented by a processor executing software instructions.
  • the software instructions may be comprised of corresponding software modules that may be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable hard disk, CD-ROM, or any other form of storage well known in the art.
  • An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and the storage medium can be located in an ASIC. Additionally, the ASIC can be located in the STA.
  • the processor and the storage medium can also exist as discrete components in the STA.
  • the functions described herein can be implemented in hardware, software, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium, or the like.

Abstract

本申请涉及一种在主从切片的多切片管理方式下实现对UE状态的管理维护的UE状态信息管理方法及装置。该方法包括：当与第一从属切片对应的第一网络设备接收到UE的下行数据通知消息时，第一网络设备向与主切片对应的第二网络设备发送寻呼请求消息；第一网络设备从第二网络设备接收寻呼响应消息；如果寻呼响应消息中携带UE当前接入的接入节点信息，则第一网络设备通过接入节点信息所指示的接入节点建立UE与第一从属切片的连接，并且将第一从属切片的UE的状态标识为激活状态；第一网络设备向第二网络设备发送用于通知所述第二网络设备：所述UE已与所述第一从属切片建立连接的第一通知信息以及UE与第一从属切片连接的接入节点信息。

Description

面向网络切片的用户设备状态信息管理方法及装置 技术领域
本发明实施例涉及无线通信技术领域，尤其涉及一种面向网络切片的用户设备状态信息管理方法及装置。
背景技术
随着通信技术的发展，5G网络架构中引入了切片(Slicing)的概念。网络切片通过在同一物理网络中创建多个独立的专属虚拟子网络，实现多种业务在共享一套宽带网络基础设施的同时保持业务实现的相对独立。例如，利用网络切片可以实现移动宽带、多媒体、大规模机器类通信(Massive Machine Type Communication)和关键机器类通信(Critical Machine Type Communication)等业务。
对于采用网络切片技术的核心网络架构，用户设备(User Equipment，UE)可以附着单个网络切片，也可以附着到多个网络切片。在UE同时附着到多个网络切片的场景中，不同网络切片在逻辑资源和逻辑功能上可以完全隔离，只在物理资源上共享。例如，在图1中，UE通过接入网络(Access Network，AN)与核心网络中实例化的第一核心网络切片和第二核心网络切片连接，其中，第一核心网络切片和第二核心网络切片共享物理资源，在逻辑功能上均包含完整独立的控制面和用户面功能。
在采用图1所示的多切片逻辑架构的系统中，如何对多切片进行管理成为影响UE使用多切片所提供服务的一个重要因素。如图2所示，相关方法中提出了一种基于主从关系的多切片管理方法。即，UE附着到多个网络切片，其中一个网络切片为主切片，例如UE初次附着的网络切片为主切片，主切片之外的其它切片均为从属切片，UE附着到从属切片时，会通知主切片。
对于图2中所示的多切片管理方法，目前的实现方案缺乏对UE状态如何维护和管理的考虑，如果各个网络切片不能正确维护UE的状态，当下行数据包到达时可能会导致重复寻呼，例如，多个网络切片同时发起寻呼流程；又或者导致不必要的寻呼流程，例如，当前切片需要发起寻呼流程，但实际上其它网络切片正在进行业务，此时并不需要发起寻呼。
发明内容
本发明实施例提供了一种面向网络切片的用户设备状态信息管理方法及装置，以在主从切片的多切片管理方式下实现对UE状态的管理维护。
第一方面，本发明实施例提供了一种面向网络切片的用户设备状态信息管理方法，包括：
当与第一从属切片对应的第一网络设备接收到用户设备的下行数据通知消息时，所述第一网络设备向与主切片对应的第二网络设备发送寻呼请求消息；
所述第一网络设备从所述第二网络设备接收寻呼响应消息；
如果所述寻呼响应消息中携带所述用户设备当前接入的接入节点信息，则所述第一网络设备通过所述接入节点信息所指示的接入节点建立所述用户设备与所述第一从属切片的连接，并且将所述第一从属切片的所述用户设备的状态标识为激活状态；
所述第一网络设备向所述第二网络设备发送第一通知信息以及所述用户设备与所述第一从属切片连接的接入节点信息，所述第一通知信息用于通知所述第二网络设备：所述用户设备已与所述第一从属切片建立连接。
在本发明实施例的实现方式中，由主切片维护各个从属切片的UE状态，当其中一个从属切片接收到下行数据时，该从属切片首先与主切片交互，如果UE已经与其它从属切片通过接入节点建立连接，则主切片将UE的接入节点信息发送给当前从属切片(对应第一从属切片)，使当前从属切片直接通过相应接入节点与UE连接，只有在UE与所有从属切片都无连接的情况下，当前从属切片才需要发起寻呼流程，从而可以避免发起不必要的寻呼
在一种可能的设计中，所述方法还包括：
如果所述寻呼响应消息中未携带所述用户设备当前接入的接入节点信息，则所述第一网络设备通过各个接入节点寻呼所述用户设备；
当所述第一网络设备通过所述各个接入节点中的其中一个接入节点建立所述用户设备与所述第一从属切片的连接之后，所述第一网络设备将所述第一从属切片的所述用户设备的状态标识为激活状态；
所述第一网络设备向所述第二网络设备发送第二通知信息以及所述用户设备与所述第一从属切片连接的接入节点信息，所述第二通知信息用于通知所述第二网络设备：所述用户设备已与所述第一从属切片建立连接。
在本发明实施例的实现方式中，当第一网络设备从第二网络接收到的寻呼响应消息中未携带用户设备当前接入的接入节点信息时，第一网络设备通过寻呼方式建立第一从属切片与用户设备的连接，并且向第二网络设备发送第二通知信息以及用户设备与第一从属切片连接的接入节点信息，进而可以实现主切片对从属切片状态的管理。
在一种可能的设计中，如果所述第一从属切片的所述用户设备的状态标识为空闲状态，所述方法还包括：
所述第一网络设备从接入节点接收所述用户设备接入所述第一从属切片的服务请求消息；
所述第一网络设备通过发送所述服务请求消息的接入节点建立所述用户设备与所述第一从属切片的连接，并且将所述第一从属切片的所述用户设备状态标识为激活状态；
所述第一网络设备向所述第二网络设备发送第三通知信息，以及所述用户设备与所述第一从属切片连接的接入节点信息，所述第三通知信息用于通知所述第二网络设备：所述用户设备已与所述第一从属切片建立连接。
在本发明实施例的实现方式中，当用户侧发起服务请求时，第一网络设备通过发送服务请求消息的接入节点建立用户设备与第一从属切片的连接，将第一从属切片的用户设备状态标识为激活状态，并且向第二网络设备发送第三通知信息和用户设备与所述第一从属切片连接的接入节点信息，进而可以实现主切片对从属切片状态的管理。
在一种可能的设计中，所述方法还包括：
所述第一网络设备从接入节点接收上下文释放请求消息，所述上下文释放请求消息用于请求释放所述用户设备与所述第一从属切片连接；
所述第一网络设备向发送所述上下文释放请求消息的所述接入节点发送所述用户设备的上下文释放命令；
当所述第一网络设备接收到所述用户设备的上下文释放完成消息时，所述第一网络设备删除所述用户设备与所述第一从属切片连接的接入节点信息，并且将所述第一从属切片的所述用户设备的状态标识为空闲状态；
所述第一网络设备向所述第二网络设备发送第四通知信息以及所述用户设备释放的接入节点信息，所述第四通知信息用于通知所述第二网络设备：所述用户设备已释放与所述第一从属切片的连接。
在本发明实施例的实现方式中，当第一网络设备释放用户设备与从属切片的连接之后，第一网络设备向第二网络设备发送所述第四通知信息以及用户设备释放的接入节点信息，由此实现主切片对从属切片状态的管理。
第二方面，本发明实施例提供了一种面向网络切片的用户设备状态信息管理方法，包括：
与主切片对应的第二网络设备从与第一从属切片对应的第一网络设备接收寻呼请求消息；
所述第二网络设备向所述第一网络设备发送寻呼响应消息，其中，当所述第二网络设备已经存储了所述用户设备当前接入的接入节点信息时，所述寻呼响应消息中携带所述接入节点信息，所述接入节点信息用于所述用户设备与所述第一从属切片连接的建立；
所述第二网络设备从所述第一网络设备接收通知信息以及所述用户设备与所述第一从属切片连接的接入节点信息，所述通知消息用于通知所述第二网络设备：所述用户设备已与所述第一从属切片建立连接。
第三方面，本发明实施例提供了一种面向网络切片的用户设备状态信息管理方法，包括：
与主切片对应的第二网络设备从与第一从属切片对应的第一网络设备接收寻呼请求消息；
所述第二网络设备向各个接入节点发送用于寻呼所述用户设备的寻呼消息；
当所述第二网络设备通过所述各个接入节点中的其中一个接入节点建立所述用户设备与所述主切片的连接之后，所述第二网络设备将所述主切片的所述用户设备的状态标识为激活状态；
所述第二网络设备向各个从属切片分别对应的网络设备发送所述用户设备接入所述主切片的接入节点信息，所述接入节点信息用于所述各个从属切片与所述用户设备连接的建立。
在本发明实施例的实现方式中，主切片维护各个从属切片的UE状态，并且各个从属切片的状态保持一致，当某个从属切片在UE处于空闲状态接收到的下行数据时，该从属切片通过主切片发起寻呼流程，其它从属切片也通过主切片接入的节点与UE建立连接，从而使所有切片下的UE为激活状态。在本发明实施例方案中，当网络侧有下行数据时，通过主切片发起寻呼流程，当有多个切片都接收到下行数据时，均需要发起一次寻呼流程，从而可以避免重复和不必要的寻呼。
在一种可能的设计中，如果所述主切片及所述各个从属切片的所述用户设备的状态均为空闲状态，所述方法还包括：
所述第二网络设备从接入节点接收所述用户设备接入所述主切片的服务请求消息；
所述第二网络设备通过发送所述服务请求消息的所述接入节点建立所述用户设备与所述主切片的连接，并且将所述主切片的所述用户设备的状态标识为激活状态；
所述第二网络设备还将所述服务请求消息转发至所述各个从属切片分别对应的网络设备，以使所述各个从属切片分别对应的网络设备通过发送所述服务请求消息的接入节点建立所述各个从属切片与所述用户设备的连接，以及将所述各个从属切片的所述用户设备的状态标识为激活状态。
在本发明实施例的实现方式中，由主切片维护各个从属切片的UE状态，并且各个切片的UE状态保持一致，当UE发起服务请求流程时，主切片将服务请求消息转发各个从属切片，以使各个从属切片均与UE建立连接，并且各个从属切片均将UE的状态标识为激活状态，从而保持了各个从属切片下UE状态的一致性。
在一种可能的设计中，所述方法还包括：
所述第二网络设备从接入节点接收上下文释放请求消息，向所述各个从属切片分别对应的网络设备转发所述上下文释放请求消息；
所述第二网络设备释放所述用户设备在所述主切片下的用户面资源；
所述第二网络设备从所述各个从属切片分别对应的网络设备接收所述用户设备的上下文释放响应消息；
所述第二网络设备向发送所述上下文释放请求消息的所述接入节点发送所述用户设备的上下文释放命令；
当所述第二网络设备接收到所述用户设备的上下文释放完成消息时，所述第二网络设备删除所述用户设备的上下文信息，将所述主切片的用户设备状态标识为空闲状 态，以及，向所述各个从属切片分别对应的网络设备转发所述上下文释放完成消息，以使所述各个从属切片分别对应的网络设备删除所述用户设备的上下文信息以及标识所述用户设备状态为空闲状态。
在本发明实施例的实现方式中，主切片统一维护各个从属切片的状态，各个从属切片的状态保持一致，当接入节点发起S1连接的释放流程时，表明UE连接的所有切片的S1连接均要进行释放，并且各个切片(包括主切片和从属切片)将UE状态标识为空闲状态，从而确保UE状态的一致性，避免在寻呼流程中发起重复和不必要的寻呼
第四方面，为了实现上述第一方面的面向网络切片的用户设备状态信息管理方法，本发明实施例提供了一种面向网络切片的用户设备状态信息管理装置，该装置具有实现第一方面方法中第一网络设备行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中，所述装置包括：
发送单元，用于当接收单元接收到用户设备的下行数据通知消息时，向与主切片对应的第二网络设备发送寻呼请求消息；
所述接收单元，还用于从所述第二网络设备接收寻呼响应消息；
寻呼连接单元，用于当所述寻呼响应消息中携带所述用户设备当前接入的接入节点信息时，通过所述接入节点信息所指示的接入节点建立所述用户设备与所述第一从属切片的连接，并且将所述第一从属切片的所述用户设备的状态标识为激活状态；
所述发送单元，还用于向所述第二网络设备发送第一通知信息以及所述用户设备与所述第一从属切片连接的接入节点信息，所述第一通知信息用于通知所述第二网络设备：所述用户设备已与所述第一从属切片建立连接。
在一种可能的设计中，所述寻呼连接单元还用于：
如果所述寻呼响应消息中未携带所述用户设备当前接入的接入节点信息，则通过各个接入节点寻呼所述用户设备；当通过所述各个接入节点中的其中一个接入节点建立所述用户设备与所述第一从属切片的连接之后，将所述第一从属切片的所述用户设备的状态标识为激活状态；
所述发送单元还用于向所述第二网络设备发送第二通知信息以及所述用户设备与所述第一从属切片连接的接入节点信息，所述第二通知信息用于通知所述第二网络设备：所述用户设备已与所述第一从属切片建立连接。
在一种可能的设计中，所述第一从属切片的所述用户设备的状态标识为空闲状态；
所述接收单元，还用于从接入节点接收所述用户设备接入所述第一从属切片的服务请求消息；
所述寻呼连接单元，还用于通过发送所述服务请求消息的接入节点建立所述用户设备与所述第一从属切片的连接，并且将所述第一从属切片的所述用户设备状态标识 为激活状态；
所述发送单元，还用于向所述第二网络设备发送第三通知信息以及所述用户设备与所述第一从属切片连接的接入节点信息，所述第三通知信息用于通知所述第二网络设备：所述用户设备已与所述第一从属切片建立连接。
在一种可能的设计中，所述接收单元，还用于从接入节点接收上下文释放请求消息，所述上下文释放请求消息用于请求释放所述用户设备与所述第一从属切片连接；
所述发送单元，还用于向发送所述上下文释放请求消息的所述接入节点发送所述用户设备的上下文释放命令；
当所述接收单元接收到所述用户设备的上下文释放完成消息时，所述寻呼连接单元，还用于删除所述用户设备与所述第一从属切片连接的接入节点信息，并且将所述第一从属切片的所述用户设备的状态标识为空闲状态；
所述发送单元，还用于向所述第二网络设备发送第四通知信息以及所述用户设备释放的接入节点信息，所述第四通知信息用于通知所述第二网络设备：所述用户设备已释放与所述第一从属切片的连接。
在又一种可能的设计中，所述装置的结构包括处理器和收发器，所述收发器被配置为执行上述发送单元和接收单元的相应功能，所述处理器被配置为执行所述寻呼连接单元的功能。所述装置中还可以包括存储器，所述存储器用于与处理器耦合，其保存所述装置必要的程序指令和数据。
第五方面，为了实现上述第二方面的面向网络切片的用户设备状态信息管理方法，本发明实施例提供了一种面向网络切片的用户设备状态信息管理装置，该装置具有实现第二方面方法中第二网络设备行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中，所述装置包括：
接收单元，用于从与第一从属切片对应的第一网络设备接收寻呼请求消息；
发送单元，用于向所述第一网络设备发送寻呼响应消息，其中，当所述第二网络设备已经存储了所述用户设备当前接入的接入节点信息时，所述寻呼响应消息中携带所述接入节点信息，所述接入节点信息用于所述用户设备与所述第一从属切片连接的建立；
所述接收单元，还用于从所述第一网络设备接收通知信息以及所述用户设备与所述第一从属切片连接的接入节点信息，所述通知信息用于通知所述第二网络设备：所述用户设备已与所述第一从属切片建立连接。
在又一种可能的设计中，所述装置的结构包括处理器和收发器，所述收发器被配置为执行上述发送单元和接收单元的相应功能，所述处理器被配置为控制所述发送单元和所述接收单元执行相应的功能。所述装置中还可以包括存储器，所述存储器用于与处理器耦合，其保存所述装置必要的程序指令和数据。
第六方面，为了实现上述第三方面的面向网络切片的用户设备状态信息管理方 法，本发明实施例提供了一种面向网络切片的用户设备状态信息管理装置，该装置具有实现第三方面方法中第二网络设备行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中，所述装置包括：
接收单元，用于从与第一从属切片对应的第一网络设备接收寻呼请求消息；
发送单元，用于向各个接入节点发送用于寻呼所述用户设备的寻呼消息；
切片连接单元，用于当通过所述各个接入节点中的其中一个接入节点建立所述用户设备与所述主切片的连接之后，将所述主切片的所述用户设备的状态标识为激活状态；
发送单元，用于向各个从属切片分别对应的网络设备发送所述用户设备接入所述主切片的接入节点信息，所述接入节点信息用于所述各个从属切片与所述用户设备连接的建立。
在一种可能的设计中，所述主切片及所述各个从属切片的所述用户设备的状态均为空闲状态；
所述接收单元，还用于从接入节点接收所述用户设备接入所述主切片的服务请求消息；
所述切片连接单元，还用于通过发送所述服务请求消息的所述接入节点建立所述用户设备与所述主切片的连接，并且将所述主切片的所述用户设备的状态标识为激活状态；
所述发送单元，还用于将所述服务请求消息转发至所述各个从属切片分别对应的网络设备，以使所述各个从属切片分别对应的网络设备通过发送所述服务请求消息的接入节点建立所述各个从属切片与所述用户设备的连接，以及将所述各个从属切片的所述用户设备的状态标识为激活状态。
在一种可能的设计中，所述接收单元从接入节点接收上下文释放请求消息，所述发送单元向所述各个从属切片分别对应的网络设备转发所述上下文释放请求消息；
所述切片连接单元，还用于释放所述用户设备在所述主切片下的用户面资源；
所述接收单元，还用于从所述各个从属切片分别对应的网络设备接收所述用户设备的上下文释放响应消息；
所述发送单元，还用于向发送所述上下文释放请求消息的所述接入节点发送所述用户设备的上下文释放命令；
所述切片连接单元，还用于当所述接收单元接收到所述用户设备的上下文释放完成消息时，删除所述用户设备的上下文信息以及将所述主切片的用户设备状态标识为空闲状态；
所述发送单元，还用于向所述各个从属切片分别对应的网络设备转发所述上下文释放完成消息，以使所述各个从属切片分别对应的网络设备删除所述用户设备的上下文信息以及标识所述用户设备状态为空闲状态。
在又一种可能的设计中，所述装置的结构包括处理器和收发器，所述收发器被配置为执行上述发送单元和接收单元的相应功能，所述处理器被配置为执行所述切片连接单元的功能。所述装置中还可以包括存储器，所述存储器用于与处理器耦合，其保存所述装置必要的程序指令和数据。
第七方面，本发明实施例提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
第八方面，本发明实施例提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
本发明实施例的面向网络切片的用户设备状态信息管理方法及装置，能够在主从切片的多切片管理方式下实现对UE状态的管理维护。
附图说明
图1是UE附着多个网络切片的示意图；
图2是基于主从关系的多切片管理示意图；
图3是本发明实施例所涉及的一种通信系统的结构示意图；
图4是图3通信系统的物理网络中创建多个网络切片的示意图；
图5是本发明实施例一提供的面向网络切片的UE状态信息管理方法的流程图；
图6是本发明实施例二提供的面向网络切片的UE状态信息管理方法的流程图；
图7是本发明实施例三提供的面向网络切片的UE状态信息管理方法的流程图；
图8是本发明实施例四提供的面向网络切片的UE状态信息管理方法的流程图；
图9是本发明实施例五提供的面向网络切片的UE状态信息管理方法的流程图；
图10是本发明实施例六提供的面向网络切片的UE状态信息管理方法的流程图；
图11是本发明实施例七提供的面向网络切片的UE状态信息管理方法的流程图；
图12是本发明实施例提供的一种面向网络切片的用户设备状态信息管理装置的结构示意图；
图13是本发明实施例提供的另一种面向网络切片的用户设备状态信息管理装置的结构示意图；
图14是本发明实施例提供的又一种面向网络切片的用户设备状态信息管理装置的结构示意图；
图15是本发明实施例提供的一种网络设备的结构示意图。
具体实施方式
图3是本发明实施例所涉及的一种通信系统的结构示意图。如图3所示，用户设备UE通过无线接入网(Radio Access Network，RAN)及核心网(Core Network，CN)接入业务网络。本发明实施例描述的技术可以适用于长期演进(Long Term Evolution，LTE)系统，或其它采用各种无线接入技术的无线通信系统，例如采用码分多址，频分多址，时分多址，正交频分多址，单载波频分多址等接入技术的系统。此外，还可以适用于使用LTE系统后续的演进系统，如第五代5G系统等。
在本发明实施例方案中，用户设备UE可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备，以及各种形式的用户设备(User Equipment，UE)，移动台(Mobile station，MS)，终端(terminal)，终端设备(Terminal Equipment)等等。为方便描述，本申请中，上面提到的设备统称为用户设备或UE。本发明所涉及到的基站(base station，BS)是一种部署在无线接入网中用以为UE提供无线通信功能的装置。所述基站可以包括各种形式的宏基站，微基站，中继站，接入点等等。在采用不同的无线接入技术的系统中，具备基站功能的设备的名称可能会有所不同，例如在LTE网络中，称为演进的节点B(evolved NodeB，eNB或者eNodeB)，在第三代3G网络中，称为节点B(Node B)等等。
在图3所示通信系统的物理网络中可以创建多个专属虚拟子网络，每个专属虚拟子网络作为一个网络切片，多个网络切片共享图3所示系统的物理网络。如图4所示，图3所示网络可以部署移动宽带切片(Mobile Broadband slice)、大规模机器类通信(Massive Machine Type Communication)和关键机器类通信(Critical Machine Type Communication)等业务。
当UE附着接入图4所示系统的多个切片时，多个切片可以按照图2所示的基于主从关系的多切片管理方法进行管理。在图4所示系统下，为了实现对UE状态的维护，本发明实施例提供了一种面向网络切片的UE状态信息管理方法。
图5是本发明实施例一提供的面向网络切片的UE状态信息管理方法的流程图。在本发明实施例方法中，由主切片维护各个从属切片中的UE状态，各个从属切片中的UE状态可以不同。当其中一个从属切片接收到网络侧发送的下行数据时，如图5所示，该方法的处理步骤包括：
步骤S101：第一网络设备接收下行数据通知消息。
其中，第一网络设备是与第一从属切片对应的网络设备，第一从属切片是主切片维护的各个从属切片中的任意一个从属切片。所述下行数据通知消息中包含用于指示接收下行数据的UE的信息。
步骤S102：第一网络设备向第二网络设备发送寻呼请求消息。第二网络设备是与主切片对应的网络设备。可选的，在第一网络设备发送的寻呼请求消息中携带有所述UE的信息。
步骤S103：第二网络设备接收到所述寻呼请求消息后，第二网络设备向第一网络设备发送寻呼响应消息。
其中，当第二网络设备确定已经存储了所述UE当前接入的接入节点信息时，在所述寻呼响应消息中携带所述接入节点信息，该接入节点信息用于所述UE与所述第一从属切片连接的建立。
当第二网络设备中没有存储与所述UE对应的接入节点信息时，在所述寻呼响应消息中不携带UE当前接入的接入节点信息。
可选的，与UE对应的接入节点信息可以是UE接入第二从属切片的接入节点信息。在本发明实施例方案中，主切片维护各个从属切片的UE状态。第一从属切片和第二从属切片都是主切片所维护的从属切片，并且第二从属切片是主切片所维护的区别于第一从属切片的任意从属切片。可选的，第二从属切片的数量可以为一个也可以为多个。
步骤S104：第一网络设备从第二网络设备接收寻呼响应消息，并且确定所述寻呼响应消息中是否携带UE当前接入的接入节点信息，如果所述寻呼响应消息中携带所述UE当前接入的接入节点信息，则执行后续步骤S105；如果所述寻呼响应消息中未携带所述UE当前接入的接入节点信息，则执行步骤S106。
步骤S105：第一网络设备通过所述接入节点信息所指示的接入节点建立所述UE与所述第一从属切片的连接，并且将所述第一从属切片的UE的状态标识为激活状态，并执行后续步骤S107。
步骤S106：第一网络设备通过各个接入节点寻呼所述UE。当所述第一网络设备通过所述各个接入节点中的其中一个接入节点建立所述UE与所述第一从属切片的连接之后，所述第一网络设备将所述第一从属切片的UE状态标识为激活状态，并执行后续步骤S107。
步骤S107：所述第一网络设备向所述第二网络设备发送通知信息以及所述用户设备与所述第一从属切片连接的接入节点信息，所述通知信息用于通知所述第二网络设备：所述用户设备已与所述第一从属切片建立连接。
在本发明实施例方案中，由主切片维护各个从属切片的UE状态，当其中一个从属切片接收到下行数据时，该从属切片首先与主切片交互，如果UE已经与其它从属切片通过接入节点建立连接，则主切片将UE的接入节点信息发送给当前从属切片(对应第一从属切片)，使当前从属切片直接通过相应接入节点与UE连接，只有在UE与所有从属切片都无连接的情况下，当前从属切片才需要发起寻呼流程，从而可以避 免发起不必要的寻呼。
在本发明实施例方案中，上述第一网络设备和第二网络设备可以分别是独立的网络设备，也可以是同一个网络设备，例如，第一网络设备和第二网络设备分别是同一网络设备中不同的虚拟机，分别用于管理第一从属切片和主切片的例程。
在本发明实施例方案中，各个切片(包括主切片和从属切片)与接入节点连接可以是接入节点与切片中的接入和移动性管理功能(Access and Mobility Management Function，AMF)单元连接。在5G系统中，切片控制设备与接入节点之间的连接暂称为N2连接。需要说明的是5G中的N2连接对应4G系统中，接入节点与MME节点的S1连接。由于5G中的N2连接相关协议尚未定义，本发明实施例方案中，接入节点与切片之间的连接可以参照S1连接相关术语的描述，S1连接和N2连接不做区分。
图6是本发明实施例二提供的面向网络切片的UE状态信息管理方法的流程图。在本发明实施例方法中，由主切片维护各个从属切片的UE状态，各个从属切片的UE状态可以不同。图6所示方法的处理步骤包括：
步骤S200：UE和第二网络设备之间完成跟踪区更新(Tracking Area Update，TAU)流程，其中，第二网络设备是与主切片对应的网络设备。
步骤S201：第一网络设备从用户面设备接收下行数据通知(Downlink Data Notification)消息，其中，第一网络设备是与第一从属切片对应的网络设备，第一从属切片是主切片维护的各个从属切片中的任意一个从属切片。
步骤S202：第一网络设备判定第一从属切片为空闲状态时，即第一从属切片已经释放了UE S1上下文，第一网络设备向第二网络设备发送寻呼请求(Paging Request)消息。
步骤S203：第二网络设备第一网络设备接收寻呼请求消息后向第一网络设备发送寻呼响应(Paging Response)消息。
其中，如果当前有其它从属切片与UE保持S1连接，则寻呼响应消息中携带UE的当前接入的接入节点信息，并且执行步骤209；否则寻呼响应消息中携带用于第一设备进行寻呼的相关信息，如TAList等，并且执行步骤204-208。
步骤S204：由于从第一网络设备接收到的寻呼响应消息指明当前UE不存在活动连接，因此第一网络设备需要发起寻呼(Paging)流程，即，第一网络设备发送寻呼(Paging)消息给所有相关的接入节点。
其中，所有相关的接入节点可以是第一网络设备预先配置的，还可以是第一网络设备从第二网络设备请求获取的。
步骤S205：接收到寻呼消息的各个接入节点开始寻呼UE。
步骤S206：接收到UE发送的寻呼响应消息的接入节点如果与UE之间没有无线资源控制(Radio Resource Control，RRC)连接，则UE建立与该接入节点的RRC连接。
步骤S207：UE向建立RRC连接的接入节点发送服务请求(Service Request)消息，其中，所述服务请求消息中携带第一从属切片的相关信息，例如，第一从属切片的ID或者其它能标识第一从属切片的信息。
步骤S208：接收到UE发送的服务请求消息的接入节点向第一网络设备转发所述服务请求消息。
步骤S209：第一网络设备向相应接入节点发送上下文建立请求(Context Setup Request)消息，其中，在所述上下文建立请求消息中携带UE的相关上下文信息。
第一网络设备确定相应接入节点的方法包括：如果第一网络设备在步骤S203中接收到的寻呼响应消息中携带UE当前接入的接入节点信息，则第一网络设备根据寻呼响应消息中携带的UE的当前接入节点信息确定接入节点。
如果第一网络在步骤S203中接收到的寻呼响应消息中未携带UE的相关接入节点信息，则第一网络设备向转发UE的服务请求消息的接入节点发送上下文建立请求消息。
步骤S210：接收到所述上下文建立请求消息的接入节点与UE之间建立无线承载。
步骤S211：所述接入节点与UE之间建立无线承载之后，接入节点向第一网络设备发送上下文建立完成消息，第一网络设备根据所述上下文建立完成消息确认UE与接入节点之间无线承载建立完成。
步骤S212：第一网络设备将第一从属切片的UE状态标识为激活状态，并向第二网络设备发送UE S1连接通知消息，其中，在UE S1连接通知消息中携带：通知信息以及UE与第一从属切片连接的接入节点信息，所述通知信息用于通知所述第二网络设备：所述用户设备已与所述第一从属切片建立连接。
在本发明实施例方案中，如果第一网络设备需要发起寻呼，并且在第一网络设备寻呼过程中有其它从属切片向第二网络设备发送寻呼请求消息，第二网络设备可以等第一网络设备发送UE S1连接建立通知消息之后，直接向请求的其它从属切片发送相关的接入节点信息，从而可以避免不必要的寻呼流程。
图7是本发明实施例三提供的面向网络切片的UE状态信息管理方法的流程图。在本发明实施例方法中，由主切片维护各个从属切片的UE状态，各个从属切片的UE状态可以不同，与实施例一和实施例二不同的是，本发明实施例方法由UE侧发 起与从属切片的连接。图7所示方法的处理步骤包括：
步骤S300：如果当前UE与接入节点之间无RRC连接，则UE首先完成与接入节点之间的RRC连接。
步骤S301：UE向建立RRC连接的接入节点发送服务请求(Service Request)消息，其中，所述服务请求消息中携带第一从属切片的相关信息，例如，第一从属切片的ID或者其它能标识第一从属切片的信息或能够让RAN节点选择到第一从属切片的第一网络设备的信息。
步骤S302：接入节点向第一网络设备转发所述服务请求消息。
接入节点根据服务请求消息中的第一从属切片的相关信息确定承载第一从属切片的第一网络设备，并且向第一网络设备转发所述服务请求消息。
步骤S303：第一网络设备向转发所述服务请求消息的接入节点发送上下文建立请求(Context Setup Request)消息，其中，在所述上下文建立请求消息中携带UE的相关上下文信息。
步骤S304：接收到所述上下文建立请求消息的接入节点与UE之间建立无线承载。
步骤S305：所述接入节点与UE之间建立无线承载之后，接入节点向第一网络设备发送上下文建立完成消息，第一网络设备根据所述上下文建立完成消息确认UE与接入节点之间无线承载建立完成。
步骤S306：第一网络设备将第一从属切片的UE状态标识为激活状态，并向第二网络设备发送UE S1连接通知消息，其中，在UE S1连接通知消息中携带通知信息以及UE与第一从属切片连接的接入节点信息，所述通知信息用于通知所述第二网络设备：所述用户设备已与所述第一从属切片建立连接。
本发明实施例提供了各个从属切片独立维护不同UE状态前提下的UE发起服务请求的流程，当某个从属切片处理UE的服务请求时，将该从属切片的状态更新为激活状态，并且通知主切片，保证主切片正确维护所有从属切片的UE状态。
图8是本发明实施例四提供的面向网络切片的UE状态信息管理方法的流程图。在本发明实施例方法中，由主切片维护各个从属切片的UE状态，各个从属切片的UE状态可以不同。本发明实施例方法主要涉及从属切片释放与UE连接的处理过程，如图8所示，包括：
步骤S401：当需要释放第一从属切片与UE的连接时，接入节点向第一网络设备发送S1 UE上下文释放请求(Context Release Request)消息。
其中，所述接入节点是UE附着到第一从属切片的接入节点。当所述接入节点确定UE与第一从属切片的交互处于空闲状态，或者在O&M干预等情况下，接入节点 确定需要释放第一从属切片与UE的连接。
步骤S402：第一网络设备接收到S1 UE上下文释放请求消息后，释放相应的用户面资源，并向接入节点发送S1 UE上下文释放命令(Context Release Command)，以通知接入节点释放与第一从属切片的UE S1连接。
步骤S403：接入节点释放与第一从属切片的UE S1连接，并判断UE是否与其它从属切片有S1连接，如果UE还与其它从属切片有S1连接，则执行步骤S404；如果接入节点与第一从属切片的UE S1连接是UE最后的S1连接，则执行步骤S405。
步骤S404：接入节点释放与第一从属切片对应的UE的无线承载。
步骤S405：接入节点向UE发送RRC连接释放(RRC Connection Release)消息，以通知UE释放与接入节点的RRC连接。
步骤S406：接入节点向第一网络设备发送S1连接释放完成(Release Complete)消息，并且接入节点删除第一从属切片的UE上下文；第一网络设备接收到的S1连接释放完成消息后删除UE与第一从属切片连接的接入节点的相关信息，并将第一从属切片的UE状态标识为空闲(Idle)状态。
步骤S407：第一网络设备向第二网络设备发送第一从属切片的S1连接释放通知消息，其中，在该释放通知消息中可以包括通知信息以及UE释放的接入节点信息，该通知信息用于通知所述第二网络设备：所述用户设备已释放与所述第一从属切片的连接。如果所有切片都已经释放与相应接入节点的S1连接，则第二网络设备删除UE的所有接入节点信息。
在本发明实施例方案中，主切片维护各个从属切片的UE状态，各个从属切片的UE状态可以不同，当某个从属切片需要释放UE的S1连接时，该从属切片将UE的状态更新为空闲状态，同时通知主切片，由此可以保证主切片正确维护所有从属切片的UE状态，当后续从属切片需要处理寻呼流程时，可以通过与主切片的交互来避免重复和不必要的寻呼。
综上可以看出，上述实施例一至实施例四中，由主切片维护各个从属切片的UE状态，各个从属切片的UE状态可以不同，当某个从属切片需要处理寻呼流程时，可以通过与主切片的交互来避免重复和不必要的寻呼。
除上述实施例一至实施例四的UE状态信息管理方案，本发明实施例还提供了另一种UE状态信息的管理方案，在该另一种管理方案中，主切片统一维护各个从属切片的UE状态，各个从属切片的UE状态一致。
图9是本发明实施例五提供的面向网络切片的UE状态信息管理方法的流程图。在本发明实施例方法中，由主切片统一维护各个从属切片的UE状态，各个从属切片 的UE状态一致。当从属切片接收到网络侧发送的下行数据时，如图9所示，本发明实施例方法的处理步骤包括：
步骤S500：UE和第二网络设备之间完成TAU流程，其中，第二网络设备是与主切片对应的网络设备。
步骤S501：第一网络设备接收下行数据通知消息。
其中，第一网络设备是与第一从属切片对应的网络设备，第一从属切片是主切片维护的各个从属切片中的任意一个从属切片。所述下行数据通知消息中包含用于指示接收下行数据的UE的信息。
步骤S502：第一网络设备判定第一从属切片为空闲状态时，即第一从属切片已经释放了UE S1上下文，第一网络设备向第二网络设备发送寻呼请求(Paging Request)消息。
步骤S503：第二网络设备从第一网络设备接收寻呼请求消息之后，向各个接入节点发送用于寻呼所述UE的寻呼消息，在图9中仅画出一个接入节点作为示例。其中，所述各个接入节点可以是第二网络设备预先配置的，还可以是第二网络设备从其它网络设备中请求获取的。
步骤S504：接收到寻呼消息的各个接入节点开始寻呼UE。
步骤S505：当所述第二网络设备通过所述各个接入节点中的其中一个接入节点建立所述UE与所述主切片的连接之后，所述第二网络设备将所述主切片的UE状态标识为激活状态。
具体的，各个接入节点中的其中一个接入节点建立UE与主切片之间的连接的过程参见实施例二中S206～S211，其中步骤S206～S211中与第一网络设备的交互流程改为与第二网络设备的交互流程，从属切片改为主切片。
步骤S506：所述第二网络设备向各个从属切片分别对应的网络设备发送所述UE接入所述主切片的接入节点的信息，以使所述各个从属切片分别对应的网络设备通过相应接入节点建立所述各个从属切片与所述UE的连接，以及将所述各个从属切片的UE状态标识为激活状态。
例如，第一网络设备接收第二网络设备发送的主切片的接入节点信息，并参照S209～S212建立第一从属切片与UE之间的连接，并且将第一从属切片的UE状态标识为激活状态，其它从属切片建立与UE连接的过程与第一网络设备建立第一从属切片与UE连接的过程相同，不再赘述。
在本发明实施例方案中，主切片维护各个从属切片的UE状态，并且各个从属切片的状态保持一致，当某个从属切片在UE处于空闲状态接收到的下行数据时，该从属切片通过主切片发起寻呼流程，其它从属切片也通过主切片接入的节点与UE建立 连接，从而使所有切片下的UE为激活状态。在本发明实施例方案中，当网络侧有下行数据时，通过主切片发起寻呼流程，当有多个切片都接收到下行数据时，均需要发起一次寻呼流程，从而可以避免重复和不必要的寻呼。
图10是本发明实施例六提供的面向网络切片的UE状态信息管理方法的流程图。在本发明实施例方法中，由主切片统一维护各个从属切片的UE状态，各个从属切片的UE状态保持一致。当UE向从属切片发起服务请求时，如图10所示，本发明实施例方法的处理步骤包括：
步骤S600：如果当前UE与接入节点之间无RRC连接，则UE首先完成与接入节点之间的RRC连接。
步骤S601：UE向建立RRC连接的接入节点发送服务请求(Service Request)消息，其中，所述服务请求消息中携带主切片的相关信息，例如，主切片的ID或者其它能标识主切片的信息。
在本发明实施例方案中，UE发送的服务请求消息都先由接入节点转发到主切片，再由主切片转发到其它从属切片。
步骤S602：接入节点将接收到的服务请求消息发送给第二网络设备，其中，第二网络设备是与主切片对应的网络设备。
步骤S603：第二网络设备通过发送所述服务请求消息的所述接入节点建立所述UE与所述主切片的连接，并且将所述主切片的UE状态标识为激活状态。
其中，第二网络设备建立主切片与UE连接并将主切片的UE状态标识为激活状态的过程可以参照S209～S212，不同的是将S209～S212中的第一网络设备改为第二网络设备，第一从属切片改为主切片。
步骤S604：第二网络设备向所述各个从属切片分别对应的网络设备转发所述服务请求消息，以使所述各个从属切片分别对应的网络设备通过相应的接入节点建立所述各个从属切片与所述UE的连接，以及将所述各个从属切片的UE状态标识为激活状态。
例如，与第一从属切片对应的第一网络设备接收第二网络设备转发的服务请求消息，第一网络设备将发送该服务请求消息的接入节点确定为交互接入节点，并且参照S209～S212建立第一从属切片与UE之间的连接，并且将第一从属切片的UE状态标识为激活状态，其它从属切片建立与UE连接的过程与第一网络设备建立第一从属切片与UE连接的过程相同，不再赘述。
在本发明实施例方案中，步骤S603和步骤S604的执行，不分先后顺序。
在本发明实施例方案中，由主切片维护各个从属切片的UE状态，并且各个切片 的UE状态保持一致，当UE发起服务请求流程时，主切片将服务请求消息转发各个从属切片，以使各个从属切片均与UE建立连接，并且各个从属切片均将UE的状态标识为激活状态，从而保持了各个从属切片下UE状态的一致性。
图11是本发明实施例七提供的UE状态信息管理方法的流程图。在本发明实施例方法中，由主切片统一维护各个从属切片的UE状态，各个从属切片的UE状态保持一致。本发明实施例方法主要涉及切片释放与UE连接的处理过程，如图11所示，包括：
步骤S701：当接入节点确定需要释放UE与各个切片的连接时，接入节点向第二网络设备发送S1 UE上下文释放请求(Context Release Request)消息。
所述第二网络设备是与主切片对应的网络设备，所述接入节点是UE附着到各个切片的接入节点。当所述接入节点确定UE与所有切片的交互处于空闲状态，或者在O&M干预等情况下，接入节点确定需要释放UE与各个切片的连接。
步骤S702：第二网络设备向各个从属切片分别对应的网络设备发送所述S1 UE上下文释放请求消息，以使各个从属切片分别对应的网络设备释放相应从属切片的用户面资源，当相应从属切片的用户面资源释放完成后，各个从属切片分别对应的网络设备向第二网络设备发送的S1 UE上下文释放响应消息。
步骤S703：第二网络设备释放所述UE在所述主切片下的用户面资源.
步骤S704：所述第二网络设备向发送所述上下文释放请求消息的所述接入节点发送所述UE的上下文释放命令。
步骤S705：接入节点接收到UE的上下文释放命令后，释放与UE之间的RRC连接。
步骤S706：接入节点释放与UE之间的RRC连接之后，向第二网络设备发送S1UE上下文释放完成消息。
步骤S707：当所述第二网络设备接收到S1 UE的上下文释放完成消息时，第二网络设备删除所述UE的上下文信息，将主切片的UE状态标识为空闲状态，以及，向各个从属切片分别对应的网络设备转发S1 UE的上下文释放完成消息，以使所述各个从属切片分别对应的网络设备删除所述UE的上下文信息以及标识所述UE状态为空闲状态。
在本发明实施例方案中，主切片统一维护各个从属切片的状态，各个从属切片的状态保持一致，当接入节点发起S1连接的释放流程时，表明UE连接的所有切片的S1连接均要进行释放，并且各个切片(包括主切片和从属切片)将UE状态标识为空闲状态，从而确保UE状态的一致性，避免在寻呼流程中发起重复和不必要的寻呼。
图12是本发明实施例提供的一种面向网络切片的UE状态信息管理装置的结构示意图。图12所示的装置部署于与第一从属切片对应的第一网络设备，包括：
发送单元801，用于当接收单元802接收到用户设备的下行数据通知消息时，向与主切片对应的第二网络设备发送寻呼请求消息；
所述接收单元802，还用于从所述第二网络设备接收寻呼响应消息；
寻呼连接单元803，用于当所述寻呼响应消息中携带所述用户设备当前接入的接入节点信息时，通过所述接入节点信息所指示的接入节点建立所述用户设备与所述第一从属切片的连接，并且将所述第一从属切片的所述用户设备的状态标识为激活状态；
所述发送单元801，还用于向所述第二网络设备发送第一通知信息以及所述用户设备与所述第一从属切片连接的接入节点信息，所述第一通知信息用于通知所述第二网络设备：所述用户设备已与所述第一从属切片建立连接。
在一种可能的设计中，所述寻呼连接单元803还用于：
如果所述寻呼响应消息中未携带所述用户设备当前接入的接入节点信息，则通过各个接入节点寻呼所述用户设备；当通过所述各个接入节点中的其中一个接入节点建立所述用户设备与所述第一从属切片的连接之后，将所述第一从属切片的所述用户设备的状态标识为激活状态；
所述发送单元801还用于：向所述第二网络设备发送第二通知信息以及所述用户设备与所述第一从属切片连接的接入节点信息，所述第二通知信息用于通知所述第二网络设备：所述用户设备已与所述第一从属切片建立连接。
在一种可能的设计中，所述第一从属切片的所述用户设备的状态标识为空闲状态；
所述接收单元802，还用于从接入节点接收所述用户设备接入所述第一从属切片的服务请求消息；
所述寻呼连接单元803，还用于通过发送所述服务请求消息的接入节点建立所述用户设备与所述第一从属切片的连接，并且将所述第一从属切片的所述用户设备状态标识为激活状态；
所述发送单元801，还用于向所述第二网络设备发送第三通知信息以及所述用户设备与所述第一从属切片连接的接入节点信息，所述第三通知信息用于通知所述第二网络设备：所述用户设备已与所述第一从属切片建立连接。
在一种可能的设计中，所述接收单元802，还用于从接入节点接收上下文释放请求消息，所述上下文释放请求消息用于请求释放所述用户设备与所述第一从属切片连接；
所述发送单元801，还用于向发送所述上下文释放请求消息的所述接入节点发送所述用户设备的上下文释放命令；
当所述接收单元802接收到所述用户设备的上下文释放完成消息时，所述寻呼连接单元803，还用于删除所述用户设备与所述第一从属切片连接的接入节点信息，并 且将所述第一从属切片的所述用户设备的状态标识为空闲状态；
所述发送单元801，还用于向所述第二网络设备发送第四通知信息以及所述用户设备释放的接入节点信息，所述第四通知信息用于通知所述第二网络设备：所述用户设备已释放与所述第一从属切片的连接。
在本发明实施例方案中，由主切片维护各个从属切片的UE状态，当其中一个从属切片接收到下行数据时，该从属切片首先与主切片交互，如果UE已经与其它从属切片通过接入节点建立连接，则主切片将UE的接入节点信息发送给当前从属切片(对应第一从属切片)，使当前从属切片直接通过相应节点与UE连接，只有在UE与所有从属切片都无连接的情况下，当前从属切片才需要发起寻呼流程，从而可以避免发起不必要的寻呼。
图13是本发明实施例提供的另一种面向网络切片的UE状态信息管理装置的结构示意图。图13所示的装置部署于与主切片对应的第二网络设备，包括：接收单元901、发送单元902和处理单元903，其中处理单元903用于控制发送单元902和处理单元903实现下述功能：
接收单元901，用于从与第一从属切片对应的第一网络设备接收寻呼请求消息；
发送单元902，用于向所述第一网络设备发送寻呼响应消息，其中，当所述第二网络设备已经存储了与所述用户设备对应的接入节点信息时，所述寻呼响应消息中携带所述接入节点信息，所述接入节点信息用于所述用户设备与所述第一从属切片连接的建立；
所述接收单元901，还用于从所述第一网络设备接收通知信息以及所述用户设备与所述第一从属切片连接的接入节点信息，所述通知信息用于通知所述第二网络设备：所述用户设备已与所述第一从属切片建立连接。
在本发明实施例方案中，由主切片维护各个从属切片的UE状态，当其中一个从属切片接收到下行数据时，该从属切片首先与主切片交互，如果UE已经与其它从属切片通过接入节点建立连接，则主切片将UE的接入节点信息发送给当前从属切片(对应第一从属切片)，使当前从属切片直接通过相应节点与UE连接，只有在UE与所有从属切片都无连接的情况下，当前从属切片才需要发起寻呼流程，从而可以避免发起不必要的寻呼。
图14是本发明实施例提供的又一种面向网络切片的用户设备状态信息管理装置的结构示意图。图14所示的装置部署于与主切片对应的第二网络设备，包括：
接收单元1001，用于从与第一从属切片对应的第一网络设备接收寻呼请求消息；
发送单元1002，用于向各个接入节点发送用于寻呼所述用户设备的寻呼消息；
切片连接单元1003，用于当通过所述各个接入节点中的其中一个接入节点建立所述用户设备与所述主切片的连接之后，将所述主切片的所述用户设备的状态标识为 激活状态；
发送单元1002，用于向各个从属切片分别对应的网络设备发送所述用户设备接入所述主切片的接入节点信息，所述接入节点信息用于所述各个从属切片与所述用户设备连接的建立。
在一种可能的设计中，所述主切片及所述各个从属切片的所述用户设备的状态均为空闲状态；
所述接收单元1001，还用于从接入节点接收所述用户设备接入所述主切片的服务请求消息；
所述切片连接单元1003，还用于通过发送所述服务请求消息的所述接入节点建立所述用户设备与所述主切片的连接，并且将所述主切片的所述用户设备的状态标识为激活状态；
所述发送单元1002，还用于将所述服务请求消息转发至所述各个从属切片分别对应的网络设备，以使所述各个从属切片分别对应的网络设备通过发送所述服务请求消息的接入节点建立所述各个从属切片与所述用户设备的连接，以及将所述各个从属切片的所述用户设备的状态标识为激活状态。
在一种可能的设计中，所述接收单元1001从接入节点接收上下文释放请求消息，所述发送单元1002向所述各个从属切片分别对应的网络设备转发所述上下文释放请求消息；
所述切片连接单元1003，还用于释放所述用户设备在所述主切片下的用户面资源；
所述接收单元1001，还用于从所述各个从属切片分别对应的网络设备接收所述用户设备的上下文释放响应消息；
所述发送单元1002，还用于向发送所述上下文释放请求消息的所述接入节点发送所述用户设备的上下文释放命令；
所述切片连接单元1003，还用于当所述接收单元1001接收到所述用户设备的上下文释放完成消息时，删除所述用户设备的上下文信息以及将所述主切片的用户设备状态标识为空闲状态；
所述发送单元1002，还用于向所述各个从属切片分别对应的网络设备转发所述上下文释放完成消息，以使所述各个从属切片分别对应的网络设备删除所述用户设备的上下文信息以及标识所述用户设备状态为空闲状态。
在本发明实施例方案中，主切片维护各个从属切片的UE状态，并且各个从属切片的状态保持一致，当某个从属切片在UE处于空闲状态接收到的下行数据时，该从属切片通过主切片发起寻呼流程，其它从属切片也通过主切片接入的节点与UE建立连接，从而使所有切片下的UE为激活状态。在本发明实施例方案中，当网络侧有下行数据时，通过主切片发起寻呼流程，当有多个切片都接收到下行数据时，均需要发起一次寻呼流程，从而可以避免重复和不必要的寻呼。
图12至图14所示的网络设备在实际实现时，可以是不同的设备，也可以是相同的设备。本发明实施例还提供了一种网络设备的具体结构，该网络设备用于实现上述第一网络设备和/或第二网络设备的功能。如图15所示，网络设备包括发射器/接收器1101，控制器/处理器1102，存储器1103以及通信单元1104。所述发射器/接收器1101用于支持网络设备与UE，以及与其它网络设备之间收发信息。所述控制器/处理器1102执行各种用于与网络设备通信的功能。在上行链路，来自UE或者其它网元的上行链路信号经由天线接收，由接收器1101进行调解，并进一步由控制器/处理器1102进行处理来恢复UE或其它网元所发送到业务数据和信令信息。在下行链路上，业务数据和信令消息由控制器/处理器1102进行处理，并由发射器1101进行调解来产生下行链路信号，并经由天线发射给UE或其它网元。控制器/处理器1102还执行本发明实施例方案中第一网络设备和/或第二网络设备所执行的UE状态信息管理方法。存储器1103用于存储网络设备的程序代码和数据。通信单元1104用于支持网络设备与其它网络实体进行通信。
可选的，当图15所示的网络设备作为图12所示的协装置执行本发明实施例的UE状态信息管理方法时，图15中的控制器/处理器1102独立或者通过与存储器1103的配合来实现图12中寻呼连接单元803所实现的功能，发射器/接收器1101用于实现图12中发送单元801和接收单元802所实现的功能。
可选的，当图15所示的网络设备作为图13所示的协装置执行本发明实施例的UE状态信息管理方法时，图15中的控制器/处理器1102独立或者通过与存储器1103的配合来实现图13中处理单元903所实现的功能，发射器/接收器1101用于实现图13中发送单元902和接收单元901所实现的功能。
可选的，当图15所示的网络设备作为图14所示的协装置执行本发明实施例的UE状态信息管理方法时，图15中的控制器/处理器1102独立或者通过与存储器1103的配合来实现图14中切片连接单元1003所实现的功能，发射器/接收器1101用于实现图14中接收单元1001和发送单元1002所实现的功能。
可以理解的是，图15仅仅示出了网络设备的简化设计。在实际应用中，网络设备可以包含任意数量的发射器，接收器，处理器，控制器，存储器，通信单元等，而所有可以实现本发明的网络设备都在本发明的保护范围之内。
用于执行本发明上述网络设备的控制器/处理器可以是中央处理器(CPU)，通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)，现场可编程门阵列(FPGA)或者其他可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。
结合本发明公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动硬盘、CD-ROM或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于STA中。当然，处理器和存储介质也可以作为分立组件存在于STA中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本发明所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质等。
以上所述的具体实施方式，对本发明的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本发明的具体实施方式而已，并不用于限定本发明的保护范围，凡在本发明的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本发明的保护范围之内。

Claims (16)

  1. 一种面向网络切片的用户设备状态信息管理方法，其特征在于，包括：
    当与第一从属切片对应的第一网络设备接收到用户设备的下行数据通知消息时，所述第一网络设备向与主切片对应的第二网络设备发送寻呼请求消息；
    所述第一网络设备从所述第二网络设备接收寻呼响应消息；
    如果所述寻呼响应消息中携带所述用户设备当前接入的接入节点信息，则所述第一网络设备通过所述接入节点信息所指示的接入节点建立所述用户设备与所述第一从属切片的连接，并且将所述第一从属切片的所述用户设备的状态标识为激活状态；
    所述第一网络设备向所述第二网络设备发送第一通知信息以及所述用户设备与所述第一从属切片连接的接入节点信息，所述第一通知信息用于通知所述第二网络设备：所述用户设备已与所述第一从属切片建立连接。
  2. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    如果所述寻呼响应消息中未携带所述用户设备当前接入的接入节点信息，则所述第一网络设备通过各个接入节点寻呼所述用户设备；
    当所述第一网络设备通过所述各个接入节点中的其中一个接入节点建立所述用户设备与所述第一从属切片的连接之后，所述第一网络设备将所述第一从属切片的所述用户设备的状态标识为激活状态；
    所述第一网络设备向所述第二网络设备发送第二通知信息以及所述用户设备与所述第一从属切片连接的接入节点信息，所述第二通知信息用于通知所述第二网络设备：所述用户设备已与所述第一从属切片建立连接。
  3. 如权利要求1或2所述的方法，其特征在于，如果所述第一从属切片的所述用户设备的状态标识为空闲状态，所述方法还包括：
    所述第一网络设备从接入节点接收所述用户设备接入所述第一从属切片的服务请求消息；
    所述第一网络设备通过发送所述服务请求消息的接入节点建立所述用户设备与所述第一从属切片的连接，并且将所述第一从属切片的所述用户设备状态标识为激活状态；
    所述第一网络设备向所述第二网络设备发送第三通知信息，以及所述用户设备与所述第一从属切片连接的接入节点信息，所述第三通知信息用于通知所述第二网络设备：所述用户设备已与所述第一从属切片建立连接。
  4. 如权利要求1至3任一项所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备从接入节点接收上下文释放请求消息，所述上下文释放请 求消息用于请求释放所述用户设备与所述第一从属切片连接；
    所述第一网络设备向发送所述上下文释放请求消息的所述接入节点发送所述用户设备的上下文释放命令；
    当所述第一网络设备接收到所述用户设备的上下文释放完成消息时，所述第一网络设备删除所述用户设备与所述第一从属切片连接的接入节点信息，并且将所述第一从属切片的所述用户设备的状态标识为空闲状态；
    所述第一网络设备向所述第二网络设备发送第四通知信息以及所述用户设备释放的接入节点信息，所述第四通知信息用于通知所述第二网络设备：所述用户设备已释放与所述第一从属切片的连接。
  5. 一种面向网络切片的用户设备状态信息管理方法，其特征在于，包括：
    与主切片对应的第二网络设备从与第一从属切片对应的第一网络设备接收寻呼请求消息；
    所述第二网络设备向所述第一网络设备发送寻呼响应消息，其中，当所述第二网络设备已经存储了所述用户设备当前接入的接入节点信息时，所述寻呼响应消息中携带所述接入节点信息，所述接入节点信息用于所述用户设备与所述第一从属切片连接的建立；
    所述第二网络设备从所述第一网络设备接收通知信息以及所述用户设备与所述第一从属切片连接的接入节点信息，所述通知消息用于通知所述第二网络设备：所述用户设备已与所述第一从属切片建立连接。
  6. 一种面向网络切片的用户设备状态信息管理方法，其特征在于，包括：
    与主切片对应的第二网络设备从与第一从属切片对应的第一网络设备接收寻呼请求消息；
    所述第二网络设备向各个接入节点发送用于寻呼所述用户设备的寻呼消息；
    当所述第二网络设备通过所述各个接入节点中的其中一个接入节点建立所述用户设备与所述主切片的连接之后，所述第二网络设备将所述主切片的所述用户设备的状态标识为激活状态；
    所述第二网络设备向各个从属切片分别对应的网络设备发送所述用户设备接入所述主切片的接入节点信息，所述接入节点信息用于所述各个从属切片与所述用户设备连接的建立。
  7. 如权利要求6所述的方法，其特征在于，如果所述主切片及所述各个从属切片的所述用户设备的状态均为空闲状态，所述方法还包括：
    所述第二网络设备从接入节点接收所述用户设备接入所述主切片的服务请求消息；
    所述第二网络设备通过发送所述服务请求消息的所述接入节点建立所述用户设备与所述主切片的连接，并且将所述主切片的所述用户设备的状态标识为激 活状态；
    所述第二网络设备将所述服务请求消息转发至所述各个从属切片分别对应的网络设备，以使所述各个从属切片分别对应的网络设备通过发送所述服务请求消息的接入节点建立所述各个从属切片与所述用户设备的连接，以及将所述各个从属切片的所述用户设备的状态标识为激活状态。
  8. 如权利要求6或7所述的方法，其特征在于，所述方法还包括：
    所述第二网络设备从接入节点接收上下文释放请求消息，向所述各个从属切片分别对应的网络设备转发所述上下文释放请求消息；
    所述第二网络设备释放所述用户设备在所述主切片下的用户面资源；
    所述第二网络设备从所述各个从属切片分别对应的网络设备接收所述用户设备的上下文释放响应消息；
    所述第二网络设备向发送所述上下文释放请求消息的所述接入节点发送所述用户设备的上下文释放命令；
    当所述第二网络设备接收到所述用户设备的上下文释放完成消息时，所述第二网络设备删除所述用户设备的上下文信息，将所述主切片的用户设备状态标识为空闲状态，以及，向所述各个从属切片分别对应的网络设备转发所述上下文释放完成消息，以使所述各个从属切片分别对应的网络设备删除所述用户设备的上下文信息以及标识所述用户设备状态为空闲状态。
  9. 一种面向网络切片的用户设备状态信息管理装置，其特征在于，所述装置部署于与第一从属切片对应的第一网络设备，包括：
    发送单元，用于当接收单元接收到用户设备的下行数据通知消息时，向与主切片对应的第二网络设备发送寻呼请求消息；
    所述接收单元，还用于从所述第二网络设备接收寻呼响应消息；
    寻呼连接单元，用于当所述寻呼响应消息中携带所述用户设备当前接入的接入节点信息时，通过所述接入节点信息所指示的接入节点建立所述用户设备与所述第一从属切片的连接，并且将所述第一从属切片的所述用户设备的状态标识为激活状态；
    所述发送单元，还用于向所述第二网络设备发送第一通知信息以及所述用户设备与所述第一从属切片连接的接入节点信息，所述第一通知信息用于通知所述第二网络设备：所述用户设备已与所述第一从属切片建立连接。
  10. 如权利要求9所述的装置，其特征在于，所述寻呼连接单元还用于：
    如果所述寻呼响应消息中未携带所述用户设备当前接入的接入节点信息，则通过各个接入节点寻呼所述用户设备；当通过所述各个接入节点中的其中一个接入节点建立所述用户设备与所述第一从属切片的连接之后，将所述第一从属切片 的所述用户设备的状态标识为激活状态；
    所述发送单元还用于向所述第二网络设备发送第二通知信息以及所述用户设备与所述第一从属切片连接的接入节点信息，所述第二通知信息用于通知所述第二网络设备：所述用户设备已与所述第一从属切片建立连接。
  11. 如权利要求9或10所述的装置，其特征在于，所述第一从属切片的所述用户设备的状态标识为空闲状态；
    所述接收单元，还用于从接入节点接收所述用户设备接入所述第一从属切片的服务请求消息；
    所述寻呼连接单元，还用于通过发送所述服务请求消息的接入节点建立所述用户设备与所述第一从属切片的连接，并且将所述第一从属切片的所述用户设备状态标识为激活状态；
    所述发送单元，还用于向所述第二网络设备发送第三通知信息以及所述用户设备与所述第一从属切片连接的接入节点信息，所述第三通知信息用于通知所述第二网络设备：所述用户设备已与所述第一从属切片建立连接。
  12. 如权利要求9至11任一项所述的装置，其特征在于，
    所述接收单元，还用于从接入节点接收上下文释放请求消息，所述上下文释放请求消息用于请求释放所述用户设备与所述第一从属切片连接；
    所述发送单元，还用于向发送所述上下文释放请求消息的所述接入节点发送所述用户设备的上下文释放命令；
    当所述接收单元接收到所述用户设备的上下文释放完成消息时，所述寻呼连接单元，还用于删除所述用户设备与所述第一从属切片连接的接入节点信息，并且将所述第一从属切片的所述用户设备的状态标识为空闲状态；
    所述发送单元，还用于向所述第二网络设备发送第四通知信息以及所述用户设备释放的接入节点信息，所述第四通知信息用于通知所述第二网络设备：所述用户设备已释放与所述第一从属切片的连接。
  13. 一种面向网络切片的用户设备状态信息管理装置，其特征在于，所述装置部署于与主切片对应的第二网络设备，包括：
    接收单元，用于从与第一从属切片对应的第一网络设备接收寻呼请求消息；
    发送单元，用于向所述第一网络设备发送寻呼响应消息，其中，当所述第二网络设备已经存储了所述用户设备当前接入的接入节点信息时，所述寻呼响应消息中携带所述接入节点信息，所述接入节点信息用于所述用户设备与所述第一从属切片连接的建立；
    所述接收单元，还用于从所述第一网络设备接收通知信息以及所述用户设备与所述第一从属切片连接的接入节点信息，所述通知信息用于通知所述第二网络设备：所述用户设备已与所述第一从属切片建立连接。
  14. 一种面向网络切片的用户设备状态信息管理装置，其特征在于，所述装置部署于与主切片对应的第二网络设备，包括：
    接收单元，用于从与第一从属切片对应的第一网络设备接收寻呼请求消息；
    发送单元，用于向各个接入节点发送用于寻呼所述用户设备的寻呼消息；
    切片连接单元，用于当通过所述各个接入节点中的其中一个接入节点建立所述用户设备与所述主切片的连接之后，将所述主切片的所述用户设备的状态标识为激活状态；
    发送单元，用于向各个从属切片分别对应的网络设备发送所述用户设备接入所述主切片的接入节点信息，所述接入节点信息用于所述各个从属切片与所述用户设备连接的建立。
  15. 如权利要求14所述的装置，其特征在于，所述主切片及所述各个从属切片的所述用户设备的状态均为空闲状态；
    所述接收单元，还用于从接入节点接收所述用户设备接入所述主切片的服务请求消息；
    所述切片连接单元，还用于通过发送所述服务请求消息的所述接入节点建立所述用户设备与所述主切片的连接，并且将所述主切片的所述用户设备的状态标识为激活状态；
    所述发送单元，还用于将所述服务请求消息转发至所述各个从属切片分别对应的网络设备，以使所述各个从属切片分别对应的网络设备通过发送所述服务请求消息的接入节点建立所述各个从属切片与所述用户设备的连接，以及将所述各个从属切片的所述用户设备的状态标识为激活状态。
  16. 如权利要求14或15所述的装置，其特征在于，所述接收单元从接入节点接收上下文释放请求消息，所述发送单元向所述各个从属切片分别对应的网络设备转发所述上下文释放请求消息；
    所述切片连接单元，还用于释放所述用户设备在所述主切片下的用户面资源；
    所述接收单元，还用于从所述各个从属切片分别对应的网络设备接收所述用户设备的上下文释放响应消息；
    所述发送单元，还用于向发送所述上下文释放请求消息的所述接入节点发送所述用户设备的上下文释放命令；
    所述切片连接单元，还用于当所述接收单元接收到所述用户设备的上下文释放完成消息时，删除所述用户设备的上下文信息以及将所述主切片的用户设备状态标识为空闲状态；
    所述发送单元，还用于向所述各个从属切片分别对应的网络设备转发所述上下文释放完成消息，以使所述各个从属切片分别对应的网络设备删除所述用户设备的上下文信息以及标识所述用户设备状态为空闲状态。
PCT/CN2017/077056 2017-03-17 2017-03-17 面向网络切片的用户设备状态信息管理方法及装置 WO2018165974A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/077056 WO2018165974A1 (zh) 2017-03-17 2017-03-17 面向网络切片的用户设备状态信息管理方法及装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/077056 WO2018165974A1 (zh) 2017-03-17 2017-03-17 面向网络切片的用户设备状态信息管理方法及装置

Publications (1)

Publication Number Publication Date
WO2018165974A1 true WO2018165974A1 (zh) 2018-09-20

Family

ID=63522757

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/077056 WO2018165974A1 (zh) 2017-03-17 2017-03-17 面向网络切片的用户设备状态信息管理方法及装置

Country Status (1)

Country Link
WO (1) WO2018165974A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106060900A (zh) * 2016-05-13 2016-10-26 宇龙计算机通信科技(深圳)有限公司 网络切片的接入控制方法及装置、终端化小区和sdn控制器
CN106412905A (zh) * 2016-12-12 2017-02-15 中国联合网络通信集团有限公司 网络切片选择方法、ue、mme和系统
US20170070892A1 (en) * 2015-09-07 2017-03-09 Electronics And Telecommunications Research Institute Mobile communication network system and method for composing network component configurations

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170070892A1 (en) * 2015-09-07 2017-03-09 Electronics And Telecommunications Research Institute Mobile communication network system and method for composing network component configurations
CN106060900A (zh) * 2016-05-13 2016-10-26 宇龙计算机通信科技(深圳)有限公司 网络切片的接入控制方法及装置、终端化小区和sdn控制器
CN106412905A (zh) * 2016-12-12 2017-02-15 中国联合网络通信集团有限公司 网络切片选择方法、ue、mme和系统

Similar Documents

Publication Publication Date Title
CN110447302B (zh) 用于在无线通信系统中管理会话以改变用户平面功能的方法和装置
US11140654B2 (en) Method for sending paging message and related device
JP7135100B2 (ja) パケット伝送方法、装置、およびシステム
US11071015B2 (en) Access traffic steering/switching/splitting method in a network and network entity performing the same
WO2019174505A1 (zh) 一种基于网络切片的通信方法及装置
WO2019196811A1 (zh) 通信方法和相关装置
CN109819485B (zh) 一种通信方法、装置及系统
WO2019033796A1 (zh) 会话处理方法及相关设备
CN110381554B (zh) 通信方法、装置、系统和计算机存储介质
WO2016000322A1 (zh) Drb转换方法及装置
CN110475388B (zh) 处理无线资源控制讯息中恢复原因的装置及方法
WO2020135850A1 (zh) 通信方法和装置
WO2020073802A1 (zh) 一种鉴权的方法及装置
WO2019037500A1 (zh) 一种选择无线接入网设备的方法及装置
WO2015018232A1 (zh) 设备到设备连接管理方法、装置及基站
WO2019223702A1 (zh) 管理pdu会话的方法、装置和系统
WO2016177106A1 (zh) 专用核心网的选择方法和装置
WO2019214732A1 (zh) 通信方法和装置
JP6829308B2 (ja) セッション管理方法及びセッション管理ネットワーク要素
WO2019174582A1 (zh) 一种消息传输方法和装置
WO2019024102A1 (zh) 无线通信中的会话处理方法及终端设备
CN110999517A (zh) 用于设备到设备（d2d）通信的方法和设备
WO2016061791A1 (zh) 接口建立方法及装置
WO2013113240A1 (zh) 一种传输rn信息、寻呼ue的方法及装置
TWI816295B (zh) 配置演進分組系統非接入層安全演算法的方法及相關裝置

Legal Events

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

Ref document number: 17901251

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17901251

Country of ref document: EP

Kind code of ref document: A1