WO2019057015A1 - 一种网络切片管理方法及装置 - Google Patents

一种网络切片管理方法及装置 Download PDF

Info

Publication number
WO2019057015A1
WO2019057015A1 PCT/CN2018/106044 CN2018106044W WO2019057015A1 WO 2019057015 A1 WO2019057015 A1 WO 2019057015A1 CN 2018106044 W CN2018106044 W CN 2018106044W WO 2019057015 A1 WO2019057015 A1 WO 2019057015A1
Authority
WO
WIPO (PCT)
Prior art keywords
management entity
network slice
nssai
management
subscription
Prior art date
Application number
PCT/CN2018/106044
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 华为技术有限公司
Publication of WO2019057015A1 publication Critical patent/WO2019057015A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/102—Entity profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a network slice management method and apparatus.
  • the network slice management system can create a corresponding network slice instance (NSI) according to the communication requirements related to the network slice.
  • a network slice instance can provide a complete end-to-end network service, and the network slice instance can be a network slice subnet instance (NSSI) and/or network function.
  • Network functions may include physical network functions and/or virtual network functions.
  • S-NSSAI single network slice selection assistance information
  • the present application provides a network slice management method and apparatus for providing a method for configuring an S-NSSAI for a control plane network entity such as a unified data management entity.
  • the application provides a network slice management method, the method comprising:
  • the first management entity sends a subscription management message to the second management entity, where the subscription management message includes at least one S-NSSAI corresponding to the network slice instance, and information of at least one terminal device corresponding to the at least one S-NSSAI The at least one terminal device has a right to use the network slice instance;
  • the subscription management complete message is used to indicate the at least one S-NSSAI corresponding to the network slice instance and the at least one S-NSSAI
  • the information of the at least one terminal device is configured in the unified data management entity.
  • the first management entity configures the foregoing information by sending, to the second management entity, at least one S-NSSAI corresponding to the network slice instance and information of at least one terminal device corresponding to the at least one S-NSSAI.
  • the network side can quickly and accurately determine the S-NSSAI corresponding to the terminal device according to the information of the terminal device, thereby being fast according to the S-NSSA corresponding to the terminal device. Determine the network slice instance for the terminal device.
  • the method before the first management entity sends a subscription management message to the second management entity, the method further includes:
  • the first management entity receives the attribute information of the network slice instance from the third management entity, where the attribute information is used to indicate a slice type of the network slice instance and/or a service type supported by the network slice instance, to And the first management entity is configured to determine the at least one S-NSSAI corresponding to the network slice instance.
  • the first management entity can determine the S-NSSAI corresponding to the network slice instance by using the attribute information of the network slice instance, so that at least one S-NSSAI corresponding to the network slice instance can be accurately determined.
  • the S-NSSAI includes an SST, and the SST is determined according to a slice type of the network slice instance and a service type of a service supported by the network slice instance.
  • the method before the first management entity sends the subscription management message to the second management entity, the method further includes:
  • the first management entity receives the at least one S-NSSAI corresponding to the network slice instance from the third management entity.
  • the first management entity can reduce the traffic of the first management entity and reduce the load of the first management entity by receiving the at least one S-NSSAI sent by the third management entity.
  • the method before the first management entity sends the subscription management message to the second management entity, the method further includes:
  • the information of the at least one terminal device corresponding to the at least one S-NSSAI in the subscription management message is a service subscribed by the at least one terminal device indicated by the subscription file and a service supported by the network slice instance. Determined at the same time.
  • the first management entity can determine the service supported by the terminal device by subscribing to the file, so as to accurately determine the information of the at least one terminal device corresponding to the at least one S-NSSAI.
  • the method further includes:
  • the first management entity sends, to the second management entity, N S-NSSAIs, and information of M terminal devices corresponding to the N S-NSSAIs, where the M terminal devices are the at least one terminal A terminal device in the device, to update the S-NSSAI corresponding to the M terminal devices, where M and N are integers greater than 0.
  • the first management entity may modify the S-NSSAI corresponding to any M terminal devices in the at least one terminal device, thereby improving network flexibility.
  • the K S-NSSAIs in the at least one S-NSSAI are the default S-NSSAI of the terminal device, and the K is greater than 0. The integer.
  • the present application provides a communication device having the function of implementing the above method.
  • 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 modules can be software and/or hardware.
  • the communication device includes a processor and a transceiver, the processor configured to send, by the transceiver, a subscription management message to a second management entity, the subscription management message including an instance of a network slice Corresponding at least one single network slice selection assistance information S-NSSAI, and information of at least one terminal device corresponding to the at least one S-NSSAI, the at least one terminal device having a right to use the network slice instance;
  • the processor is configured to receive, by the transceiver, a subscription management complete message from the second management entity, the subscription management complete message being used to indicate the at least one S-NSSAI corresponding to the network slice instance and at least The information of at least one terminal device corresponding to one S-NSSAI is configured in the unified data management entity.
  • the processor is further configured to:
  • the transceiver Receiving, by the transceiver, the attribute information of the network slice instance from a third management entity, where the attribute information is used to indicate a slice type of the network slice instance and/or a service type supported by the network slice instance, to use And determining, by the network device, the at least one S-NSSAI corresponding to the network slice instance.
  • the S-NSSAI includes a service/slice type SST, and the SST is determined according to a slice type of the network slice instance and a service type of a service supported by the network slice instance.
  • the processor before the sending the subscription management message to the second management entity, the processor is further configured to:
  • the at least one S-NSSAI corresponding to the network slice instance is received by the transceiver from a third management entity.
  • the processor before the sending the subscription management message to the second management entity, the processor is further configured to:
  • the information of the at least one terminal device corresponding to the at least one S-NSSAI in the subscription management message is a service subscribed by the at least one terminal device indicated by the subscription file and a service supported by the network slice instance. Determined at the same time.
  • the processor is further configured to:
  • the transceiver Transmitting, by the transceiver, N S-NSSAIs, and information of M terminal devices corresponding to the N S-NSSAIs to the second management entity, where the M terminal devices are the at least one terminal device
  • the terminal device in the device updates the S-NSSAI corresponding to the M terminal devices, where M and N are integers greater than 0.
  • the application provides a network slice management method, where the method includes:
  • the second management entity receives a subscription management message from the first management entity, where the subscription management message includes at least one single network slice selection assistance information S-NSSAI corresponding to the network slice instance, and corresponding to the at least one S-NSSAI Information of at least one terminal device having permission to use the network slice instance;
  • the second management entity Sending, by the second management entity, the information including the at least one S-NSSAI corresponding to the network slice instance and the at least one terminal device corresponding to the at least one S-NSSAI to the unified data management entity, and sending the information to the first management entity Sending a subscription management completion message, where the subscription management completion message is used to indicate that the at least one S-NSSAI corresponding to the network slice instance and the information of the at least one terminal device corresponding to the at least one S-NSSAI are configured in the unified data.
  • the subscription management completion message is used to indicate that the at least one S-NSSAI corresponding to the network slice instance and the information of the at least one terminal device corresponding to the at least one S-NSSAI are configured in the unified data.
  • the network side can quickly and accurately determine the S-NSSAI corresponding to the terminal device according to the information of the terminal device, so that the S-NSSAI corresponding to the terminal device is The terminal device selects the network slice instance that is allowed to be used.
  • the method before the sending, by the second management entity, the subscription management completion message to the first management entity, the method further includes:
  • the second management entity receives a configuration completion message from the unified data management entity, where the configuration completion message is used to indicate the at least one S-NSSAI corresponding to the network slice instance and at least one corresponding to the at least one S-NSSAI
  • the information of the terminal device is configured in the unified data management entity.
  • the S-NSSAI includes a service/slice type SST;
  • the SST is determined according to a slice type of the network slice instance and a service type of a service supported by the network slice instance.
  • the present application provides a communication device having the function of implementing the above method.
  • 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 modules can be software and/or hardware.
  • the communication device includes a processor and a transceiver, the processor being configured to receive, by the transceiver, a subscription management message from a first management entity, the subscription management message including an instance of a network slice Corresponding at least one single network slice selection assistance information S-NSSAI, and information of at least one terminal device corresponding to the at least one S-NSSAI, the at least one terminal device having a right to use the network slice instance;
  • the processor is further configured to send, by the transceiver, information to the unified data management entity including the at least one S-NSSAI corresponding to the network slice instance and the at least one terminal device corresponding to the at least one S-NSSAI, and And sending, to the first management entity, a subscription management complete message, where the subscription management complete message is used to indicate the information of the at least one S-NSSAI corresponding to the network slice instance and the at least one terminal device corresponding to the at least one S-NSSAI It is configured in the unified data management entity.
  • the processor before the sending the subscription management complete message to the first management entity, the processor is further configured to:
  • the transceiver Receiving, by the transceiver, a configuration completion message from the unified data management entity, where the configuration completion message is used to indicate the at least one S-NSSAI corresponding to the network slice instance and the at least one terminal corresponding to the at least one S-NSSAI
  • the information of the device is configured in the unified data management entity.
  • the S-NSSAI includes a service/slice type SST;
  • the SST is determined according to a slice type of the network slice instance and a service type of a service supported by the network slice instance.
  • the present application also provides a computer readable storage medium storing instructions that, when executed on a computer, cause the computer to implement a network slice management method provided by any of the above designs.
  • the present application also provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the network slice management method provided by any of the above designs.
  • the present application also provides a computer program that, when run on a computer, causes the computer to perform the network slice management method provided by any of the above designs.
  • the present application also provides a chip connected to a memory for reading and executing a software program stored in the memory, such that the chip performs a network slice management method provided by any one of the above designs.
  • FIG. 1 is a schematic diagram of a system architecture applicable to an embodiment of the present application
  • FIGS. 2(a) to 2(d) are schematic diagrams of a network element manager provided by an embodiment of the present application.
  • 3(a) to 3(e) are schematic diagrams of a network function manager according to an embodiment of the present application.
  • FIG. 4 is a flowchart of a network slice management method according to an embodiment of the present application.
  • FIG. 5 is a schematic flowchart of a subscription information configuration process according to an embodiment of the present application.
  • FIG. 6 is a schematic flowchart of still another subscription information configuration process according to an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of still another subscription information configuration process according to an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a communication device provided by the present application.
  • FIG. 9 is a schematic structural diagram of another communication device provided by the present application.
  • FIG. 10 is a schematic structural diagram of a communication device provided by the present application.
  • FIG. 11 is a schematic structural diagram of another communication device provided by the present application.
  • NR New Radio
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • LTE-A Advanced Long Term Evolution
  • UMTS Universal Mobile Telecommunication System
  • eLTE evolved Long Term Evolution
  • Network Slice refers to a different logical network that is customized according to different service requirements on a physical or virtual network infrastructure.
  • the network slice can be a complete end-to-end network including the terminal, the access network, the transmission network, the core network and the application server, and can provide complete telecommunication services and have certain network capabilities; the network slice can also be the above terminal and interface. Any combination of network access, transport network, core network and application server.
  • a network slice may have one or more of the following characteristics: the access network may or may not slice.
  • the access network may be shared by multiple network slices. The characteristics of different network slices and the network functions that make up them may be different.
  • Network Slice Instance It is a real-running logical network that can meet certain network characteristics or service requirements.
  • a network slice instance may provide one or more services.
  • a network sharding instance can be created by the network management system.
  • a network management system may create multiple network shard instances and manage them at the same time, including performance monitoring and fault management during network snippet instance running. When multiple network slice instances coexist, some network resources and network functions may be shared between network slice instances.
  • a network tile instance may or may not be created from a network tile template.
  • a complete network slicing instance can provide complete end-to-end network services, and the network slicing instances can be Network Slice Subnet Instance (NSSI) and/or network functions.
  • Network functions may include physical network functions and/or virtual network functions. The following are collectively referred to as physical network functions and/or virtual network functions as network functions.
  • the network slice subnet instance does not need to provide end-to-end complete network services.
  • the network slice subnet instance can be the same device vendor in the network slice instance.
  • a collection of network functions may also be a collection of network functions divided by domain, such as a core network network slice subnet instance, an access network network slice subnet instance, or a collection of other ways, such as a deployment location.
  • a network sliced subnet instance may be shared by multiple network slice instances. The network slice subnet instance is proposed to facilitate network management system management.
  • a network slice instance may consist of several network slice subnet instances, each network slice subnet instance consisting of several network functions and/or several network slice subnet instances; one network slice instance may be composed of several network slice subnet instances and none It is composed of network functions that are divided into network slice subnet instances; a network slice instance may also consist of only a few network functions.
  • Network function is a processing function in the network, defines the functional behavior and interface, the network function can be realized by dedicated hardware, or can be realized by running software on dedicated hardware. It can be implemented as a virtual function on a common hardware platform. Therefore, from the perspective of implementation, network functions can be divided into physical network functions and virtual network functions. From the perspective of use, network functions can be divided into dedicated network functions and shared network functions. Specifically, for multiple (sub)network slice instances, different network functions can be used independently. This network function is called exclusive. Network functions can also share the same network function, which is called shared network function.
  • FIG. 1 exemplarily shows a schematic diagram of a system architecture applicable to an embodiment of the present application.
  • the network slice management system architecture shown in FIG. 1 includes a Communication Service Management Function (CSMF) entity, a Network Slice Management Function (NSMF) entity, and a Network Slice Subnet Management function. Function, NSSMF) entity.
  • CSMF Communication Service Management Function
  • NSMF Network Slice Management Function
  • NSSMF Network Slice Subnet Management function. Function
  • the CSMF entity is mainly used to: convert the communication service requirements of the operator and/or the third party customer into requirements for the network (such as network slicing), and send the network slice instance to the NSMF entity through an interface with the NSMF entity.
  • Requirements such as creating, terminating, modifying network slice instance requests, etc.
  • management data such as performance, fault data, etc.
  • the NSMF entity is mainly used to: receive the requirement of the network slice instance sent by the CSMF entity, manage the lifecycle management (LCM) of the network slice instance, and manage the performance and fault of the network slice instance (the following life cycle) Management, performance management, and fault management are collectively referred to as management.
  • the composition of the network slicing instance is organized.
  • the requirements for decomposing the network slicing instance are the requirements of each network slicing subnet instance and/or network function, and the network slicing subnet instance is sent to each NSSMF entity. One or more of management requests and the like.
  • the NSSMF entity is mainly used to: receive the requirement of the network slice subnet instance sent by the NSMF entity, manage the network slice subnet instance, orchestrate the composition of the sub-row network segment instance, and decompose the network slice subnet instance requirement for each network function. And/or one or more of the requirements of nesting network slice subnet instances, sending nested network slice subnet instance management requests to other NSSMF entities, and the like.
  • FIG. 1 is only an example, and other entities may be included in the network slice management system architecture, for example, including Unified Data Management (UDM) entities, and are not illustrated here.
  • UDM Unified Data Management
  • the first management entity and the third management entity may be independent physical entities or may be located in one physical entity, which are respectively described below.
  • the first management entity and the third management entity are located in one physical entity, and the physical entity is NSMF.
  • the second management entity is an NSSMF, or an element manager (EM). , or network function (NF) manager (manager).
  • the second management entity NSSMF can integrate the functions of the EM or NF manager.
  • information such as subscription management information can be configured in the UDM.
  • information such as subscription management information can be configured in the UDM through interaction with the EM or NF manager.
  • the EM may be an independent device, or may be located on a network element (NE), and may be integrated on a domain manager (DM).
  • the EM can perform configuration actions on one network element.
  • the upper level of the EM is a network manager (NM), and the NM can deliver management messages from the higher layer to the EM.
  • FIG. 2(a) to FIG. 2(d) the EM is an independent device located between the NM and the NE.
  • the EM is integrated on the NE, which can interact directly with the NM.
  • the EM is integrated on the DM, which is located between the NM and the NE.
  • the above various forms of EM may exist at the same time, and may be specifically referred to FIG. 2(d).
  • the NF Manager can be an independent device, it can also be located on the NF, or it may be integrated in a domain manager (NSSMF or DM, etc.), or there is a possible form, that is, NS management under NSSMF management.
  • the device exists.
  • the NF manager is an independent device located between the NSMF and the NF.
  • the NF Manager is integrated on the NF, which can interact directly with the NSMF.
  • the NF Manager is integrated on the NSSMF or DM, which is located between the NSMF and the NF.
  • the NF Manager is an independent device located between the NSSMF and the NF. It should be noted that, in a system, the above various forms of the NF manager may exist at the same time, as specifically shown in FIG. 3(e). .
  • the first management entity is an entity that manages the subscription information
  • the third management entity is an entity that manages the network slice instance, all located in the NSMF, reducing the first management entity and the third management entity being located in different devices.
  • the interaction brought by the second management entity is located in the NSSMF or NF manager or EM, and the second management entity specifically performs the configuration of the UDM, and belongs to the traditional two-layer management architecture, so that the existing network architecture can be used to improve the system. compatibility.
  • the first management entity and the third management entity are located in one physical entity, the physical entity is an NM, and the second management entity is an EM or NF manager.
  • the first management entity is an entity that manages subscription information
  • the third management entity is an entity that manages network slice instances, all located in the NM, reducing the number of the first management entity and the third management entity being located in different devices.
  • the UDM configuration belongs to the traditional two-tier management architecture, so that the existing network architecture can be used to improve system compatibility.
  • the first management entity and the third management entity are independent physical entities.
  • the first management entity is an NM
  • the second management entity is an EM or NF manager
  • the third management entity is an NSMF or a CSMF.
  • the third management entity is located in the NSMF or the CSMF, and the first management entity is the NM. Because the first management entity and the third management entity are located in different network entities, the existing network architecture can be used in this scenario.
  • the management structure of the first management entity and the third management entity reduces changes to the existing network architecture and improves system compatibility.
  • the second management entity is located in the NF manager or EM, and the second management entity performs configuration on the UDM, and belongs to the traditional two-layer management architecture, so that the existing network architecture can be used to improve system compatibility.
  • FIG. 4 a schematic flowchart of a network slice management method according to an embodiment of the present application is shown. Referring to Figure 4, the method includes:
  • Step 401 The first management entity sends a subscription management message to the second management entity, where the subscription management message includes at least one S-NSSAI corresponding to the network slice instance, and at least one terminal corresponding to the at least one S-NSSAI. Information of the device, the at least one terminal device having the right to use the network slice instance.
  • the at least one S-NSSAI may also be referred to as a subscription S-NSSAI (subscribed S-NSSAIs) of each of the at least one terminal device.
  • the at least one S-NSSAI may be used to assist the terminal device in selecting a network sharding instance.
  • the “information of at least one S-NSSAI corresponding to the network slice instance and the information of at least one terminal device corresponding to the at least one S-NSSAI” is simply referred to as “the first”.
  • a subscription message The first subscription information is just an abbreviation and is not intended as a limitation on subscription management messages.
  • the first subscription information may be transmitted on an Itf-N interface between the first management entity and the second management entity, and the Itf-N interface is an interface defined by the 3rd Generation Partnership Project (3GPP) management system.
  • the configuration process and the message are in accordance with the configuration of the configuration message on the Itf-N, and the name of the message carrying the first subscription information is not limited in the embodiment of the present application.
  • the message of the first subscription information may also be other messages, which are not illustrated one by one here.
  • an S-NSSAI may include a service/slice type (SST), the SST indicates a network slice type of the network slice instance, and the slice type of the network slice instance may be an enhanced mobile type.
  • eMBB Enhanced Mobile Broadband
  • URLLC ultra-reliable low latency communications
  • MIoT massive Internet of Things
  • an S-NSSAI may also include a slice differentiator (SD), and the SD may be used to distinguish different network slice instances.
  • the information included in the SD is not limited in this embodiment, and may include, for example, a tenant. (customer) information used to distinguish network slice instances of different tenants, or other information.
  • Step 402 The second management entity receives the subscription management message from the first management entity.
  • Step 403 The second management entity sends, to the unified data management entity, information including the at least one S-NSSAI corresponding to the network slice instance and at least one terminal device corresponding to the at least one S-NSSAI, and the foregoing A management entity sends a subscription management completion message.
  • the subscription management completion message is used to indicate that the at least one S-NSSAI corresponding to the network slice instance and the information of the at least one terminal device corresponding to the at least one S-NSSAI are configured in the unified data management entity.
  • the unified data management entity may implement functions such as managing and storing subscription information, so that the corresponding content may be provided to the terminal device or the network entity according to the first subscription information.
  • the UDM entity may store the subscription data to other data units, such as a Unified Data Repository (UDR) entity, and read the data into the UDR entity when in use.
  • UDR Unified Data Repository
  • the present application only configures the subscription data to the UDM entity, and the interaction between the UDM entity and other data units is not limited in the embodiment of the present application.
  • Step 404 The first management entity receives a subscription management complete message from the second management entity.
  • the subscription management completion message is sent after the second management entity sends the first subscription information to the unified data management entity.
  • At least one S-NSSAI corresponding to the network slice instance in the first subscription information may be determined in multiple manners.
  • the SST in the S-NSSAI is determined according to the slice type of the network slice instance and the service type of the service supported by the network slice instance.
  • the SD when there is an S-NSSAI including the SD, the SD may be generated according to characteristics of a network slice instance, such as tenant information corresponding to the network slice instance, service identifier supported by the network slice instance, and network slice. The geographic extent covered by the instance, and so on.
  • a third management entity is further received in the system, where the first management entity receives attribute information of a network slice instance sent by the third management entity, where the attribute information indicates a slice type of the network slice instance. And/or a service type supported by the network slice instance, for the first management entity to determine the at least one S-NSSAI corresponding to the network slice instance.
  • the attribute information may also indicate a service identifier supported by the network slice instance, tenant information supported by the network slice instance, a geographical range covered by the network slice instance, and the like.
  • the at least one S-NSSAI is generated according to the attribute information, and the SST of each S-NSSAI is the network slice instance indicated by the attribute information.
  • the slice type and the service type of the service supported by the network slice instance are determined.
  • the first management entity may determine the location according to the tenant information corresponding to the network slice instance, the service identifier supported by the network slice instance, and the geographic range covered by the network slice instance. Said SD.
  • At least one S-NSSAI corresponding to the network slice instance is received by the first management entity from a third management entity.
  • the third management entity may simultaneously send the attribute information of the network slice instance to the first management entity, and the at least one S-NSSAI corresponding to the network slice instance.
  • the first management entity receives at least one S-NSSAI corresponding to the network slice instance from the third management entity.
  • a terminal device is taken as an example.
  • the network-side device for example, the device responsible for service negotiation
  • the subscription file indicates
  • the information that the terminal device subscribes to may also indicate the information of the terminal device, where the information of the terminal device includes, but is not limited to, the device identifier of the terminal device, the network to which the terminal device belongs, the temporary identifier of the terminal device in the network, and the like.
  • Information related to the terminal device is taken as an example.
  • the first management entity may obtain the subscription file of the terminal device, for example, the first management entity receives the subscription file sent by the network side device (for example, the device that can be responsible for service negotiation), or the first The management entity may obtain the subscription file of the terminal device by requesting the network device of the subscription file of all the terminal devices to request the terminal device to subscribe to the file.
  • the network side device for example, the device that can be responsible for service negotiation
  • the first management entity may obtain the subscription file of the terminal device by requesting the network device of the subscription file of all the terminal devices to request the terminal device to subscribe to the file.
  • the first management entity may obtain the subscription file of the terminal device in other manners, which is not limited by the embodiment of the present application, and is not illustrated by way of example.
  • the first management entity may determine, according to the subscription file, a service subscribed by the terminal device. If the first management entity determines that the service subscribed by the terminal device is the same as the service supported by the network slice instance indicated by the at least one S-NSSAI, the at least one S-NSSAI may be established. Correspondence relationship of the terminal device. That is, the first management entity may determine the terminal device by using a correspondence between the terminal device and the subscribed service, the correspondence between the service and the network slice instance of the support service, and the correspondence between the network slice instance and the at least one S-NSSAI.
  • the at least one S-NSSAI corresponds to the terminal device.
  • the at least one S-NSSAI corresponding to the terminal device can also be It is called the subscription S-NSSAI (subscribed S-NSSAIs) of the terminal device.
  • the first management entity may determine another terminal device corresponding to the at least one S-NSSAI, thereby establishing a correspondence between the information of the at least one S-NSSAI and the at least one terminal device, where The above process will not be described again.
  • the subscription management message may be generated after the first management entity determines the at least one S-NSSAI corresponding to the network slice instance and the information of the at least one terminal device corresponding to the at least one S-NSSAI.
  • the subscription management message may also include the information of the terminal device and the subscription S-NSSAI of the terminal device, and the subscription management message may also include other information, which is not limited in the embodiment of the present application, and details are not described herein again.
  • step 403 after receiving the first subscription information, the second management entity configures the first subscription information in the unified data management entity.
  • the second management entity sends a subscription configuration message to the unified data management entity, where the subscription configuration message is used to configure the at least one S-NSSAI corresponding to the network slice instance and the at least one S-NSSAI.
  • the information of one terminal device is configured in a unified data management entity.
  • the configuration completion message is sent to the second management entity, where the configuration completion message is used to indicate the at least one S-NSSAI corresponding to the network slice instance and the at least one S-NSSAI
  • the information of the corresponding at least one terminal device is configured to be completed in the unified data management entity.
  • the second management entity After receiving the configuration completion message from the unified data management entity, the second management entity sends a subscription management complete message to the first management entity, where the subscription management complete message is used to indicate the at least corresponding to the network slice instance.
  • Information of one S-NSSAI and at least one terminal device corresponding to at least one S-NSSAI is configured in the unified data management entity.
  • the second management entity may also send information such as a subscription configuration message to the unified data management entity through other management entities.
  • the second management entity may send a subscription configuration message or the like to the unified data management entity through the NSSMF or the EM or NF manager, or if the second management entity is NSSMF, the NSSMF is not integrated.
  • the NSSMF sends a subscription configuration message and the like to the unified data management entity through the EM or NF manager.
  • step 404 after the first management entity receives the subscription management complete message, the first management entity implements, by the second management entity, at least one S-NSSAI and at least one terminal device corresponding to the at least one S-NSSAI.
  • the S-NSSAI configured in the unified data management entity can be used to assist in selecting a network slice instance for the terminal device.
  • the terminal device when selecting a network slice instance to be used, the terminal device needs to send a registration request message to an Access and Mobility Management Function (AMF) entity serving the terminal device, and the registration request message may include P S-NSSAIs, the P S-NSSAIs may be referred to as Requested S-NSSAIs, and the network slice instances corresponding to the P S-NSSAIs are network slice instances that the terminal device needs to select, P is An integer greater than 0.
  • AMF Access and Mobility Management Function
  • the AMF entity After receiving the P S-NSSAIs sent by the terminal device, the AMF entity requests the unified data management entity for the information of the terminal device, and the H S-NSSAIs corresponding to the information of the terminal device, where H is an integer greater than 0.
  • H is an integer greater than 0.
  • the foregoing content is pre-configured in the unified data management entity. For the configuration process, refer to step 401 to step 404.
  • the AMF entity After the AMF entity obtains the information of the terminal device and the H S-NSSAIs corresponding to the information of the terminal device, it is determined whether the H S-NSSAIs are the same as the P S-NSSAIs sent by the terminal device. P S-NSSAI. Specifically, the foregoing determining process is performed by taking any one of P S-NSSAIs (hereinafter referred to as “first S-NSSAI”) as an example, and the AMF entity includes the STT included in the first S-NSSAI (below) It is called "first SST”) and is compared with the H S-NSSAI.
  • first S-NSSAI any one of P S-NSSAIs
  • H S-NSSAI If it is determined that at least one STT included in the S-NSSAI exists in the H S-NSSAI, and is the same as the first SST, determining that the H S-NSSAIs are the same as the first S-NSSAI S-NSSAI; otherwise, it is determined that the same S-NSSAI as the first S-NSSAI does not exist in the H S-NSSAIs.
  • the AMF entity further needs to determine whether the H S-NSSAI includes the first SST and the first An S-NSSAI of an SD can determine that the S-NSSAI is the same as the first S-NSSAI in the H S-NSSAIs only when the first SST and the first SD are included, otherwise the S-NSSAI may be determined. There is no S-NSSAI identical to the first S-NSSAI in the H S-NSSAIs.
  • the AMF entity may determine whether there are P S-NSSAIs in the H S-NSSAIs that are the same as the P S-NSSAIs sent by the terminal device, and if the AMF entity determines the H S-NSSAIs If there are P S-NSSAIs that are the same as the P S-NSSAIs sent by the terminal device, the terminal device is allowed to use the network slice instance corresponding to the H S-NSSAIs, otherwise the terminal device is not allowed to use the H S- Network slicing instance corresponding to NSSAI.
  • the K S-NSSAIs in the at least one S-NSSAI are default S-NSSAIs of the terminal device, and K is greater than 0. Integer.
  • the terminal device does not include the S-NSSAI in the AMF entity sending the registration request message for the terminal device, after receiving the registration request message, the AMF entity determines the default S-NSSAI of the terminal device, and then The network slice instance corresponding to the default S-NSSAI of the terminal device determines the network slice instance requested by the registration request message.
  • the process of the determination may involve the interaction of the AMF and the NSSF (network slice selection function), which is not limited in this embodiment.
  • the first management entity may further modify the correspondence between the information of the at least one S-NSSAI and the at least one terminal device.
  • M terminal devices in at least one terminal device that use a network slice instance corresponding to at least one S-NSSAI need to migrate to a network slice instance corresponding to N S-NSSAIs, where M and N are greater than 0. Integer.
  • the first management entity may send, to the second management entity, N S-NSSAIs, and information of M terminal devices corresponding to the N S-NSSAIs, the M terminal devices. And being a terminal device in the at least one terminal device.
  • the N S-NSSAI and the at least one S-NSSAI may have the same S-NSSAI, and may also have different S-NSSAIs, which is not limited in this embodiment of the present application.
  • the “N S-NSSAIs and the information of the M terminal devices corresponding to the N S-NSSAIs” are simply referred to as “second subscription information”.
  • the second subscription information is only an abbreviation and does not have a limiting effect.
  • the second management entity After receiving the second subscription information, the second management entity sends the second subscription information to the unified data management entity, so as to update the S-NSSAI corresponding to the M terminal devices to N Ss in the unified data management entity.
  • -NSSAI After updating the S-NSSAI corresponding to the M terminal devices to the N S-NSSAIs, the unified data management entity may further send an update message to the AMF entity, where the update message is used to instruct the AMF entity to trigger registration management. (Registration management) process, instructing the AMF entity to update the S-NSSAI corresponding to the M terminal devices to the N S-NSSAIs, the specific content of the process is not limited in this embodiment, and is no longer Narration.
  • FIG. 5 it is a schematic diagram of a subscription information configuration process provided by an embodiment of the present application.
  • at least one S-NSSAI included in the subscription management message is determined by the first management entity, and the specific implementation manners of the first management entity, the second management entity, and the third management entity may be Reference is made to the descriptions in the first to third possible scenarios, and details are not described herein again.
  • Step 501 The third management entity sends a notification message to the first management entity, where the notification message includes attribute information of the network slice instance.
  • the attribute information indicates information such as a slice type of the network slice instance, a service type of a service supported by the network slice instance, and the like.
  • Step 502 The first management entity receives the notification message, and determines at least one S-NSSAI corresponding to the network slice instance according to the attribute information. At the same time, the first management entity determines, according to the obtained subscription file, that the service subscribed by the at least one terminal device corresponding to the subscription file is the same as the service supported by the network slice instance indicated by the attribute information, Corresponding relationship between the at least one S-NSSAI corresponding to the network slice instance and the information of the at least one terminal device.
  • Step 503 The first management entity sends a subscription management message including the first subscription information to the second management entity, where the first subscription information is at least one S-NSSAI corresponding to the network slice instance, and the Information of at least one terminal device corresponding to at least one S-NSSAI corresponding to the network slice instance.
  • Step 504 The second management entity receives the subscription management message from the first management entity, and sends a subscription configuration message including the first subscription information to the unified data management entity.
  • Step 505 The unified data management entity receives the subscription configuration message from the unified data management entity, and sends a configuration completion message to the second management entity, where the configuration completion message is used to indicate that the first subscription information is in the unified data management entity.
  • the configuration is completed.
  • Step 506 The second management entity receives the configuration completion message from the unified data management entity, and sends a subscription management complete message to the first management entity, where the subscription management complete message is used to indicate that the first subscription information is configured in the unified In the data management entity.
  • At least one S-NSSAI included in the subscription management message may also be sent by the third management entity to the first management entity, and the first management entity will perform the at least one S- The NSSAI is configured into the unified data management entity by the second management entity.
  • FIG. 6 a schematic diagram of a subscription information configuration process according to another embodiment of the present application is provided.
  • the first management entity, the second management entity, and the third management entity refer to the descriptions in the first to third possible scenarios, and details are not described herein again.
  • Step 601 The third management entity sends a notification message to the first management entity, where the notification message includes attribute information of the network slice instance, and at least one S-NSSAI corresponding to the network slice instance.
  • Step 602 The first management entity receives the notification message from the third management entity, and determines, according to the obtained subscription file, the service subscribed by the at least one terminal device corresponding to the subscription file, and the network slice instance supports If the services are the same, the correspondence between the at least one S-NSSAI and the information of the at least one terminal device is established.
  • Step 603 The first management entity sends a subscription management message including the first subscription information to the second management entity, where the first subscription information is the at least one S-NSSAI determined in step 602, and the at least one S-NSSAI Corresponding information of at least one terminal device.
  • Step 604 The second management entity receives the subscription management message from the first management entity, and sends a subscription configuration message including the first subscription information to the unified data management entity.
  • Step 605 The unified data management entity receives the subscription configuration message from the second management entity, and sends a configuration completion message to the second management entity, where the configuration completion message is used to indicate that the first subscription information is in the unified data management entity.
  • the configuration is completed.
  • Step 606 The second management entity receives the configuration completion message from the unified data management entity, and sends a subscription management complete message to the first management entity, where the subscription management complete message is used to indicate that the first subscription information is configured in the In a unified data management entity.
  • the subscription information of the terminal device also needs to be modified.
  • M devices migrate from network slice instance A to network slice instance B as an example.
  • the correspondence between the information of the S-NSSAI and the terminal device may be modified, for example, the terminal device needs The migrating to another network snippet instance, the first management entity needs to complete the update of the correspondence between the information of the S-NSSAI and the terminal device by configuring the second subscription information in the unified data management entity.
  • FIG. 7 another schematic diagram of a subscription information configuration process provided by an embodiment of the present application is provided. In the process shown in FIG. 7, the network slice instances A and B are taken as an example.
  • the network slice instance A corresponds to at least one S-NSSAI
  • the at least one S-NSSAI corresponds to information of at least one terminal device.
  • the network splicing instance B corresponds to the N S-NSSAIs, and the M terminal devices of the at least one terminal device need to be migrated to the network splicing instance B. Therefore, the first management entity needs to re-determine the S-NSSAI corresponding to the M terminal devices. .
  • Step 701 The third management entity sends a network slice instance update message to the first management entity, where the network slice instance update message is used to indicate that the M slice devices in the network slice instance A are used to migrate from the network slice instance A to the network slice.
  • the network slice instance update message is used to indicate that the M slice devices in the network slice instance A are used to migrate from the network slice instance A to the network slice.
  • the network slice instance update message may include information such as attribute information of the network slice instance B.
  • Step 702 The first management entity receives the network slice instance update message from the third management entity, and establishes a correspondence between the N S-NSSAIs corresponding to the network slice instance B and the information of the M terminal devices.
  • Step 703 The first management entity sends a subscription management message including the second subscription information to the second management entity, where the second subscription information is the N S-NSSAIs, and the M corresponding to the N S-NSSAIs. Information about terminal devices.
  • Step 704 The second management entity receives the subscription management message from the first management entity, and sends a subscription configuration message including the second subscription information to the unified data management entity.
  • Step 705 The unified data management entity receives the subscription configuration message from the second management entity, and sends a configuration completion message to the second management entity, where the configuration completion message is used to indicate that the second subscription information is in the unified data management entity.
  • the configuration is completed.
  • Step 706 The second management entity receives the configuration completion message from the unified data management entity, and sends a subscription management complete message to the first management entity, where the subscription management complete message is used to indicate that the second subscription information is configured in the In a unified data management entity.
  • Step 707 The unified data management entity instructs the AMF entity serving the M terminal devices to update the S-NSSAI corresponding to the M terminal devices to the N S-NSSAIs.
  • FIG. 8 a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • the communication device 800 can perform the actions performed by the first management entity in the flow of FIG. 4, the communication device 800 comprising:
  • the processing module 801 is configured to send, by the transceiver module 802, a subscription management message to the second management entity, where the subscription management message includes at least one single network slice selection assistance information S-NSSAI corresponding to the network slice instance, and the at least Information of at least one terminal device corresponding to an S-NSSAI, the at least one terminal device having a right to use the network slice instance;
  • the processing module 801 is configured to receive, by the transceiver module 802, a subscription management complete message from the second management entity, where the subscription management complete message is used to indicate the at least one S-NSSAI corresponding to the network slice instance and Information of at least one terminal device corresponding to at least one S-NSSAI is configured in the unified data management entity.
  • processing module 801 is further configured to:
  • the transceiver module 802 Receiving, by the transceiver module 802, the attribute information of the network slice instance from the third management entity, where the attribute information is used to indicate a slice type of the network slice instance and/or a service type supported by the network slice instance, to And determining, by the network device, the at least one S-NSSAI corresponding to the network slice instance.
  • the S-NSSAI includes a service/slice type SST, and the SST is determined according to a slice type of the network slice instance and a service type of a service supported by the network slice instance.
  • the processing module 801 before the sending the subscription management message to the second management entity, the processing module 801 is further configured to:
  • the at least one S-NSSA corresponding to the network slice instance is received by the transceiver module 802 from the third management entity.
  • the processing module 801 before the sending the subscription management message to the second management entity, the processing module 801 is further configured to:
  • the information of the at least one terminal device corresponding to the at least one S-NSSAI in the subscription management message is a service subscribed by the at least one terminal device indicated by the subscription file and a service supported by the network slice instance. Determined at the same time.
  • the processing module 801 is further configured to:
  • N S-NSSAIs and information of M terminal devices corresponding to the N S-NSSAIs to the second management entity, where the M terminal devices are the at least one terminal A terminal device in the device, to update the S-NSSAI corresponding to the M terminal devices, where M and N are integers greater than 0.
  • the structure of the communication device includes a processor and a transceiver for performing the actions performed by the first management entity in the method illustrated in FIG.
  • a possible simplified schematic diagram of a communication device is shown.
  • the structure of the communication device 900 includes a transceiver 901, a processor 902, a bus 903, and a memory 904.
  • the transceiver 901 is integrated by a transmitter and a receiver. In other embodiments, the transmitter and receiver may also be independent of one another.
  • the transceiver 901, the processor 902, and the memory 904 can be connected to each other through the bus 903;
  • the bus 903 can be a peripheral component interconnect (PCI) bus or an extended industry standard structure ( Extended industry standard architecture, EISA) bus.
  • PCI peripheral component interconnect
  • EISA Extended industry standard architecture
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 9, but it does not mean that there is only one bus or one type of bus.
  • the processor 902 is configured to perform control management on an action of the communication device, for performing an action performed by the first management entity in the foregoing embodiment, for example, sending, by using the transceiver 901, a subscription management message to the second management entity, where the subscription is
  • the management message includes at least one single network slice selection assistance information S-NSSAI corresponding to the network slice instance, and information of at least one terminal device corresponding to the at least one S-NSSAI, the at least one terminal device having the use a permission of the network slice instance; receiving, by the transceiver 901, a subscription management completion message from the second management entity, the subscription management completion message being used to indicate the at least one S-NSSAI corresponding to the network slice instance and the at least one S
  • the information of the at least one terminal device corresponding to the NSSAI is configured in the unified data management entity, and/or other processes for performing the techniques described herein.
  • the processor 902 may include one or more processors, for example, including one or more central processing units (CPUs), which may be integrated in the chip, or may be the chip itself. .
  • CPUs central processing units
  • the memory 904 is used to store related instructions and data, as well as program code and data of the network device.
  • the memory 904 includes, but is not limited to, a random access memory (RAM), a read-only memory (ROM), and an erasable programmable read-only memory (Erasable Programmable Read). Only Memory, EPROM), or Compact Disc Read-Only Memory (CD-ROM).
  • Figure 9 only shows a simplified design of the communication device.
  • the communication device 900 is a network device such as a base station, or a terminal device
  • the communication device 900 may include any number of transmitters, receivers, processors, memories, or other components, and all of which may implement channel interception of the present application.
  • the communication devices of the method are all within the scope of the present application.
  • FIG. 10 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • the communication device 1000 can perform the actions performed by the second management entity in the flow of FIG. 4, the communication device 1000 includes: the processing module 1001 is configured to pass from the transceiver module 1002. Receiving, by the first management entity, a subscription management message, where the subscription management message includes at least one single network slice selection assistance information S-NSSAI corresponding to the network slice instance, and at least one terminal device corresponding to the at least one S-NSSAI Information that the at least one terminal device has authority to use the network slice instance;
  • the processing module 1001 is further configured to send, by the transceiver module 1002, information about the at least one S-NSSAI corresponding to the network slice instance and the at least one terminal device corresponding to the at least one S-NSSAI to the unified data management entity. And sending, to the first management entity, a subscription management complete message, where the subscription management complete message is used to indicate the at least one S-NSSAI corresponding to the network slice instance and the at least one terminal device corresponding to the at least one S-NSSAI The information is configured in the unified data management entity.
  • the processing module 1001 before the sending the subscription management completion message to the first management entity, is further configured to:
  • a configuration completion message from the unified data management entity, where the configuration completion message is used to indicate the at least one S-NSSAI corresponding to the network slice instance and at least one corresponding to the at least one S-NSSAI
  • the information of the terminal device is configured in the unified data management entity.
  • the S-NSSAI includes a service/slice type SST;
  • the SST is determined according to a slice type of the network slice instance and a service type of a service supported by the network slice instance.
  • the structure of the communication device includes a processor and a transceiver for performing the actions performed by the second management entity in the method illustrated in FIG.
  • a possible simplified schematic diagram of a communication device is shown.
  • the structure of the communication device 1100 includes a transceiver 1101, a processor 1102, a bus 1103, and a memory 1104.
  • the transceiver 1101 is integrated by a transmitter and a receiver. In other embodiments, the transmitter and receiver may also be independent of one another.
  • the transceiver 1101, the processor 1102, and the memory 1104 can be connected to each other through the bus 1103; the bus 1103 can be a PCI bus or an EISA bus or the like.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 11, but it does not mean that there is only one bus or one type of bus.
  • the processor 1102 is configured to perform control management on an action of the communication device, and is used to perform an action performed by the second management entity in the foregoing embodiment, for example, configured to receive a subscription management message from the first management entity by using the transceiver module 1002.
  • the subscription management message includes at least one single network slice selection assistance information S-NSSAI corresponding to the network slice instance, and information of at least one terminal device corresponding to the at least one S-NSSAI, the at least one terminal device having Using the rights of the network slice instance; further configured to send, by the transceiver module 1002, at least one S-NSSAI corresponding to the network slice instance and at least one corresponding to the at least one S-NSSAI to the unified data management entity a message of the terminal device, and sending a subscription management completion message to the first management entity, where the subscription management completion message is used to indicate the at least one S-NSSAI corresponding to the network slice instance and the at least one S-NSSAI Information of at least one terminal device is configured in the unified data management entity, and/or Other processes of the techniques described herein are performed.
  • the processor 1102 can include one or more processors, for example, including one or more CPUs, and the processor 1102 can be integrated into a chip or can be the chip itself.
  • the memory 1104 is configured to store related instructions and data, as well as program codes and data of the network device.
  • memory 1104 includes, but is not limited to, RAM, ROM, EPROM, or CD-ROM.
  • Figure 11 only shows a simplified design of the communication device.
  • the communication device 1100 is a network device such as a base station, or a terminal device
  • the communication device 1100 can include any number of transmitters, receivers, processors, memories, or other components, and the like, and all can implement the channel interception of the present application.
  • the communication devices of the method are all within the scope of the present application.
  • the division of the module in the embodiment of the present application is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • the functional modules in the embodiments of the present application may be integrated into one processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • the integrated modules if implemented in the form of software functional modules and sold or used as separate products, may be stored in a computer readable storage medium.
  • a computer readable storage medium A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) or a processor to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. .
  • the present application also proposes a communication device for performing the method of FIG. 4 to FIG. 7 relating to the action of the first management entity or the second management entity.
  • the communication device can be a chip or a processing circuit.
  • the chip or processing circuit can be arranged in a first management entity or a second management entity.
  • the foregoing chip may or may not include a memory.
  • the computer program product includes one or more computer instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).
  • Embodiments of the present application are described with reference to flowchart illustrations and/or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present application. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG.
  • These computer program instructions may be provided to a processing module 1001 of a general purpose computer, special purpose computer, embedded processor or other programmable data processing device to produce a machine for execution by a processing module 1001 of a computer or other programmable data processing device.
  • the instructions produce means for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.

Landscapes

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

Abstract

一种网络切片管理方法及装置，其中方法包括：第一管理实体向第二管理实体发送订阅管理消息，所述订阅管理消息中包括与网络切片实例对应的至少一个单一网络切片选择辅助信息S-NSSAI，以及与所述至少一个S-NSSAI对应的至少一个终端设备的信息，所述至少一个终端设备具有使用所述网络切片实例的权限；所述第一管理实体从所述第二管理实体接收订阅管理完成消息，所述订阅管理完成消息用于指示所述与网络切片实例对应的至少一个S-NSSAI以及与至少一个S-NSSAI对应的至少一个终端设备的信息被配置在统一数据管理实体中。

Description

一种网络切片管理方法及装置
本申请要求在2017年9月22日提交国家专利局、申请号为201710867054.1、发明名称为“一种网络切片管理方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种网络切片管理方法及装置。
背景技术
传统蜂窝网络架构只能提供统一的网络服务，难以满足数字化转型浪潮带来的差异性通信需求。为了提供差异性通信服务，在下一代移动网络,即5G网络中，网络将被抽象为多个“网络切片(network slice)”，一个网络切片满足某一类或一个用例的连接通信服务需求，整个5G网络由满足不同连接能力的大量网络切片组成。网络切片管理系统可以根据网络切片相关的通信需求，创建相应的网络切片实例(network slice instance，NSI)。一个网络切片实例能够提供完整的端到端的网络服务，而组成网络切片实例的可以是网络切片子网实例(network slice subnet instance,NSSI)和/或网络功能。网络功能可以包括物理网络功能和/或虚拟网络功能。为了进行网络切片选择，网络切片管理系统会创建一个或多个单一网络切片选择辅助信息(single network slice selection assistance information，S-NSSAI)。
然而，统一数据管理实体等控制面网络实体，如何获得S-NSSAI，仍是亟待解决的问题。
发明内容
本申请提供一种网络切片管理方法及装置，用以提供为统一数据管理实体等控制面网络实体配置S-NSSAI的方法。
第一方面，本申请提供了一种网络切片管理方法，该方法包括：
第一管理实体向第二管理实体发送订阅管理消息，所述订阅管理消息中包括与网络切片实例对应的至少一个S-NSSAI，以及与所述至少一个S-NSSAI对应的至少一个终端设备的信息，所述至少一个终端设备具有使用所述网络切片实例的权限；
所述第一管理实体从所述第二管理实体接收订阅管理完成消息，所述订阅管理完成消息用于指示所述与网络切片实例对应的至少一个S-NSSAI以及与至少一个S-NSSAI对应的至少一个终端设备的信息被配置在统一数据管理实体中。
上述方法中，第一管理实体通过向第二管理实体发送与网络切片实例对应的至少一个S-NSSAI，以及与所述至少一个S-NSSAI对应的至少一个终端设备的信息，实现将上述信息配置在统一数据管理实体中，当终端设备选择网络切片实例时，可以使得网络侧根据终端设备的信息快速、准确的确定与终端设备对应的S-NSSAI，从而根据与终端设备对应的S-NSSA快速的为终端设备确定网络切片实例。
在一种可能的设计中，所述第一管理实体向第二管理实体发送订阅管理消息之前，所 述方法还包括：
所述第一管理实体从第三管理实体接收所述网络切片实例的属性信息，所述属性信息用于指示所述网络切片实例的切片类型和/或所述网络切片实例支持的业务类型，以用于所述第一管理实体确定所述与网络切片实例对应的至少一个S-NSSAI。
通过上述方法，第一管理实体通过网络切片实例的属性信息，可以确定出与网络切片实例相对应的S-NSSAI，从而能够准确的确定与网络切片实例对应的至少一个S-NSSAI。
在一种可能的设计中，所述S-NSSAI包括SST，所述SST是根据所述网络切片实例的切片类型、所述网络切片实例支持的业务的业务类型确定。
在一种可能的设计中，所述第一管理实体向第二管理实体发送所述订阅管理消息之前，所述方法还包括：
所述第一管理实体从第三管理实体接收所述与网络切片实例对应的至少一个S-NSSAI。
通过上述方法，第一管理实体通过接收第三管理实体发送的至少一个S-NSSAI，可以减少第一管理实体的业务量，减轻第一管理实体的负载。
在一种可能的设计中，所述第一管理实体向第二管理实体发送所述订阅管理消息之前，所述方法还包括：
所述第一管理实体获取订阅文件，所述订阅文件指示出所述至少一个终端设备订阅的业务；
所述订阅管理消息中与所述至少一个S-NSSAI对应的至少一个终端设备的信息，为在所述订阅文件指示出的所述至少一个终端设备订阅的业务与所述网络切片实例支持的业务相同时确定的。
通过上述方法，第一管理实体可以通过订阅文件，确定终端设备支持的业务，从而准确的确定出与所述至少一个S-NSSAI对应的至少一个终端设备的信息。
在一种可能的设计中，所述第一管理实体向第二管理实体发送订阅管理消息之后，所述方法还包括：
所述第一管理实体向所述第二管理实体发送N个S-NSSAI，以及与所述N个S-NSSAI对应的M个终端设备的信息，所述M个终端设备为所述至少一个终端设备中的终端设备，以更新所述M个终端设备对应的S-NSSAI，M、N为大于0的整数。
通过上述方法，第一管理实体可以修改所述至少一个终端设备中的任意M个终端设备所对应的S-NSSAI，从而提高网络的灵活性。
在一种可能的设计中，针对所述至少一个终端设备中的任意一个终端设备，所述至少一个S-NSSAI中的K个S-NSSAI为该终端设备的默认S-NSSAI，K为大于0的整数。
第二方面，本申请提供了一种通信设备，该通信设备具有实现上述方法的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。所述模块可以是软件和/或硬件。
在一个可能的设计中，上述通信设备包括处理器和收发器，所述处理器被配置为通过所述收发器向第二管理实体发送订阅管理消息，所述订阅管理消息中包括与网络切片实例对应的至少一个单一网络切片选择辅助信息S-NSSAI，以及与所述至少一个S-NSSAI对应的至少一个终端设备的信息，所述至少一个终端设备具有使用所述网络切片实例的权限；
所述处理器被配置为通过所述收发器从所述第二管理实体接收订阅管理完成消息，所述订阅管理完成消息用于指示所述与网络切片实例对应的至少一个S-NSSAI以及与至少 一个S-NSSAI对应的至少一个终端设备的信息被配置在统一数据管理实体中。
在一种可能的设计中，所述处理器还被配置为：
通过所述收发器从第三管理实体接收所述网络切片实例的属性信息，所述属性信息用于指示所述网络切片实例的切片类型和/或所述网络切片实例支持的业务类型，以用于所述网络设备确定所述与网络切片实例对应的至少一个S-NSSAI。
在一种可能的设计中，所述S-NSSAI包括业务/切片类型SST，所述SST是根据所述网络切片实例的切片类型、所述网络切片实例支持的业务的业务类型确定。
在一种可能的设计中，所述向第二管理实体发送所述订阅管理消息之前，所述处理器还被配置为：
通过所述收发器从第三管理实体接收所述与网络切片实例对应的至少一个S-NSSAI。
在一种可能的设计中，所述向第二管理实体发送所述订阅管理消息之前，所述处理器还被配置为：
通过所述收发器获取订阅文件，所述订阅文件指示出所述至少一个终端设备订阅的业务；
所述订阅管理消息中与所述至少一个S-NSSAI对应的至少一个终端设备的信息，为在所述订阅文件指示出的所述至少一个终端设备订阅的业务与所述网络切片实例支持的业务相同时确定的。
在一种可能的设计中，所述向第二管理实体发送订阅管理消息之后，所述处理器还被配置为：
通过所述收发器向所述第二管理实体发送N个S-NSSAI，以及与所述N个S-NSSAI对应的M个终端设备的信息，所述M个终端设备为所述至少一个终端设备中的终端设备，以更新所述M个终端设备对应的S-NSSAI，M、N为大于0的整数。
第三方面，本申请提供了一种网络切片管理方法，所述方法包括：
第二管理实体从第一管理实体接收订阅管理消息，所述订阅管理消息中包括与网络切片实例对应的至少一个单一网络切片选择辅助信息S-NSSAI，以及与所述至少一个S-NSSAI对应的至少一个终端设备的信息，所述至少一个终端设备具有使用所述网络切片实例的权限；
所述第二管理实体向统一数据管理实体发送包括所述与网络切片实例对应的至少一个S-NSSAI以及与至少一个S-NSSAI对应的至少一个终端设备的信息，并向所述第一管理实体发送订阅管理完成消息，所述订阅管理完成消息用于指示所述与网络切片实例对应的至少一个S-NSSAI以及与至少一个S-NSSAI对应的至少一个终端设备的信息被配置在所述统一数据管理实体中。
上述方法中，第二管理实体接收到第一管理实体发送的与网络切片实例对应的至少一个S-NSSAI以及与所述至少一个S-NSSAI对应的至少一个终端设备的信息之后，将上述信息配置在统一数据管理实体中，当终端设备选择网络切片实例时，可以使得网络侧根据终端设备的信息快速、准确的确定与终端设备对应的S-NSSAI，从而根据与终端设备对应的S-NSSAI为终端设备选择允许使用的网络切片实例。
在一种可能的设计中，所述第二管理实体向所述第一管理实体发送订阅管理完成消息之前，所述方法还包括：
所述第二管理实体从所述统一数据管理实体接收配置完成消息，所述配置完成消息用 于指示所述与网络切片实例对应的至少一个S-NSSAI以及与至少一个S-NSSAI对应的至少一个终端设备的信息在所述统一数据管理实体中被配置完成。
在一种可能的设计中，所述S-NSSAI包括业务/切片类型SST；
所述SST是根据所述网络切片实例的切片类型、所述网络切片实例支持的业务的业务类型确定。
第四方面，本申请提供了一种通信设备，该通信设备具有实现上述方法的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。所述模块可以是软件和/或硬件。
在一个可能的设计中，上述通信设备包括处理器和收发器，所述处理器被配置为通过所述收发器从第一管理实体接收订阅管理消息，所述订阅管理消息中包括与网络切片实例对应的至少一个单一网络切片选择辅助信息S-NSSAI，以及与所述至少一个S-NSSAI对应的至少一个终端设备的信息，所述至少一个终端设备具有使用所述网络切片实例的权限；
所述处理器还被配置为通过所述收发器向统一数据管理实体发送包括所述与网络切片实例对应的至少一个S-NSSAI以及与至少一个S-NSSAI对应的至少一个终端设备的信息，并向所述第一管理实体发送订阅管理完成消息，所述订阅管理完成消息用于指示所述与网络切片实例对应的至少一个S-NSSAI以及与至少一个S-NSSAI对应的至少一个终端设备的信息被配置在所述统一数据管理实体中。
在一种可能的设计中，所述向所述第一管理实体发送订阅管理完成消息之前，所述处理器还被配置为：
通过所述收发器从所述统一数据管理实体接收配置完成消息，所述配置完成消息用于指示所述与网络切片实例对应的至少一个S-NSSAI以及与至少一个S-NSSAI对应的至少一个终端设备的信息在所述统一数据管理实体中被配置完成。
在一种可能的设计中，所述S-NSSAI包括业务/切片类型SST；
所述SST是根据所述网络切片实例的切片类型、所述网络切片实例支持的业务的业务类型确定。
本申请还提供了一种计算机可读存储介质，所述存储介质存储有指令，当所述指令在计算机上运行时，使得计算机实现执行上述任意一种设计提供的网络切片管理方法。
本申请还提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述任意一种设计提供的网络切片管理方法。
本申请还提供了一种计算机程序，当其在计算机上运行时，使得计算机执行上述任意一种设计提供的网络切片管理方法。
本申请还提供了一种芯片，所述芯片与存储器相连，用于读取并执行所述存储器中存储的软件程序，使得所述芯片执行上述任意一种设计提供的网络切片管理方法。
附图说明
图1为适用于本申请实施例的一种系统架构示意图；
图2(a)至2(d)为本申请实施例提供的一种网元管理器示意图；
图3(a)至3(e)为本申请实施例提供的一种网络功能管理器示意图；
图4为本申请实施例提供的一种网络切片管理方法流程图；
图5为本申请实施例提供的一种订阅信息配置流程示意图；
图6为本申请实施例提供的又一种订阅信息配置流程示意图；
图7为本申请实施例提供的又一种订阅信息配置流程示意图；
图8为本申请提供的一种通信设备的结构示意图；
图9为本申请提供的另一种通信设备的结构示意图；
图10为本申请提供的一种通信设备的结构示意图；
图11为本申请提供的另一种通信设备的结构示意图。
具体实施方式
下面将结合附图对本申请作进一步地详细描述。
本申请实施例可以应用于各种移动通信系统，例如：新无线(New Radio，NR)系统、全球移动通讯(Global System of Mobile communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、先进的长期演进(Advanced long term evolution，LTE-A)系统、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、演进的长期演进(evolved Long Term Evolution，eLTE)系统、5G等其它移动通信系统。
以下，对本申请中的部分用语进行解释说明，以便于本领域技术人员理解。
1)、网络切片(Network slice)：指在物理或者虚拟的网络基础设施之上，根据不同的服务需求定制化的、不同的逻辑网络。网络切片可以是一个包括了终端、接入网、传输网、核心网和应用服务器的完整的端到端网络，能够提供完整的电信服务，具有一定网络能力；网络切片也可以是上述终端、接入网、传输网、核心网和应用服务器的任意组合。网络切片可能具有如下一个或多个特性：接入网可能切片，也可能不切片。接入网可能是多个网络切片共用的。不同的网络切片的特性和组成它们的网络功能可能是不一样。
2)、网络切片实例(Network slice instance，NSI)：是一个真实运行的逻辑网络，能满足一定网络特性或服务需求。一个网络切片实例可能提供一种或多种服务。网络切片实例可以由网管系统创建，一个网管系统可能创建多个网络切片实例并同时对它们进行管理，包括在网络切片实例运行过程中的性能监视和故障管理等。当多个网络切片实例共存时，网络切片实例之间可能共享部分网络资源和网络功能。网络切片实例可能从网络切片模板创建，也可能不从网络切片模板创建。一个完整的网络切片实例是能够提供完整的端到端的网络服务的，而组成网络切片实例的可以是网络切片子网实例(Network Slice Subnet Instance,NSSI)和/或网络功能。网络功能可以包括物理网络功能和/或虚拟网络功能。以下统称物理网络功能和/或虚拟网络功能为网络功能。
3)、网络切片子网实例(Network Slice Subnet Instance，NSSI)：网络切片子网实例可以不需要提供端到端的完整的网络服务，网络切片子网实例可以是网络切片实例中同一个设备商的网络功能组成集合，也可能是按域划分的网络功能的集合，例如核心网网络切片子网实例、接入网网络切片子网实例，或由部署位置等其他方式组成集合。网络切片子网实例可能被多个网络切片实例共享。提出网络切片子网实例，可以方便网管系统管理。一个网络切片实例可能由若干网络切片子网实例组成，每个网络切片子网实例由若干网络功能和/或若干网络切片子网实例组成；一个网络切片实例可能由若干网络切片子网实例和没有被划分为网络切片子网实例的网络功能组成；一个网络切片实例也可能仅由若干网络功 能组成。
4)、网络功能(Network function，NF)：是网络中的一种处理功能，定义了功能性的行为和接口，网络功能可以通过专用硬件实现，也可以通过在专用硬件上运行软件实现，也可以在通用的硬件平台上以虚拟功能的形式实现。因此，从实现的角度，可以将网络功能分为物理网络功能和虚拟网络功能。而从使用的角度，网络功能可以分为专属网络功能和共享网络功能，具体地，对于多个(子)网络切片实例而言，可以独立地使用不同的网络功能，这种网络功能称为专属网络功能，也可以共享同一个网络功能，这种网络功能称为共享网络功能。
图1示例性示出了适用于本申请实施例的一种系统架构示意图。图1所示的网络切片管理系统架构中包括通信业务管理功能(Communication Service Management Function，CSMF)实体、网络切片管理功能(Network Slice Management Function，NSMF)实体、网络切片子管理功能(Network Slice Subnet Management Function，NSSMF)实体。
CSMF实体，主要用于：将运营商和/或第三方客户的通信服务需求转化为对网络(如网络切片)的需求，并通过和NSMF实体之间的接口向NSMF实体发送对网络切片实例的需求(如创建、终结、修改网络切片实例请求等)，从NSMF实体获取网络切片实例的管理数据(如性能、故障数据等)，生成运行于网络切片实例之上的通信业务的管理数据，接收运营商和/或第三方客户对网络切片实例管理数据和/或通信业务的管理数据的订阅需求等中的一种或多种。
NSMF实体，主要用于：接收CSMF实体发送的网络切片实例的需求，对网络切片实例的生命周期管理(lifecycle management，LCM)，以及对网络切片实例的性能、故障等进行管理(以下将生命周期管理、性能管理、故障管理统称为管理)，编排网络切片实例的组成，分解网络切片实例的需求为各网络切片子网实例和/或网络功能的需求，向各NSSMF实体发送网络切片子网实例管理请求等中的一种或多种。
NSSMF实体，主要用于：接收NSMF实体发送的网络切片子网实例的需求，对网络切片子网实例进行管理，编排子排网络切片实例的组成，分解网络切片子网实例的需求为各网络功能和/或嵌套网络切片子网实例的需求，向其他NSSMF实体发送嵌套网络切片子网实例管理请求等中的一种或多种。
当然，图1只是示例，网络切片管理系统架构中还可以包括其他实体，例如包括统一数据管理(Unified Data Management，UDM)实体等，在此不再逐一举例说明。
本申请实施例中，第一管理实体与第三管理实体可以分别为独立的物理实体，也可以位于一个物理实体中，下面分别进行描述。
第一种可能的场景中，第一管理实体与第三管理实体位于一个物理实体中，该物理实体为NSMF，此时，第二管理实体为NSSMF，或网元管理器(element manager，EM)，或网络功能(network function，NF)管理器(manager)等。
第二管理实体NSSMF可以集成了EM或NF管理器的功能，第二管理实体NSSMF集成了EM或NF管理器的功能时，可以在UDM中配置订阅管理信息等信息。第二管理实体NSSMF没有集成EM或NF管理器的功能时，可以通过与EM或者NF管理器的交互在UDM中配置订阅管理信息等信息。
需要说明的是，EM可以是独立存在的设备，也可以位于网元(network element，NE)上，还有可能集成在一个域管理器(domain manager，DM)上。EM可以对一个网元执行 配置动作，同时，EM的上级为网络管理器(network manager，NM)，NM可以从更高的层面向EM下发管理消息。具体可以参考图2(a)至图2(d)所示，图2(a)中，EM为独立存在的设备，位于NM和NE之间。图2(b)中，EM集成在NE上，该NE与NM可以直接交互。图2(c)中，EM集成在DM上，该DM位于NM和NE之间。需要说明的是，一个系统中，上述各种形式的EM可以同时存在，具体可以参考图2(d)所示。
NF管理器可以是独立存在的设备，也可以位于NF上，还有可能集成在一个域管理器(NSSMF或DM等)上，或者还有一种可能的形式，即NSSMF管理之下还有NF管理器存在。具体可以参考图3(a)至图3(e)所示，图3(a)中，NF管理器为独立存在的设备，位于NSMF和NF之间。图3(b)中，NF管理器集成在NF上，该NF与NSMF可以直接交互。图3(c)中，NF管理器集成在NSSMF或DM上，该NSSMF或DM位于NSMF和NF之间。图3(d)中，NF管理器为独立存在的设备，位于NSSMF和NF之间。需要说明的是，一个系统中，上述各种形式的NF管理器可以同时存在，具体可以参考图3(e)所示。。
在第一种可能的场景下，第一管理实体为管理订阅信息的实体，第三管理实体为管理网络切片实例的实体，都位于NSMF，减少了第一管理实体和第三管理实体位于不同设备所带来的交互；第二管理实体位于NSSMF或NF管理器或者EM，第二管理实体具体执行对UDM的配置，属于传统的两层管理架构，从而可以沿用现有的网络架构，提高系统的兼容性。
第二种可能的场景中，第一管理实体与第三管理实体位于一个物理实体中，该物理实体为NM，第二管理实体为EM或NF管理器。
这种场景下，第一管理实体为管理订阅信息的实体，第三管理实体为管理网络切片实例的实体，都位于NM，减少了第一管理实体和第三管理实体位于不同设备所带来的交互；由于第一管理实体管理网络切片实例，而网络切片实例一般由NSMF来管理，因此NSMF和NM在同一个实体实现，第二管理实体位于NF管理器或者EM，第二管理实体具体执行对UDM的配置，属于传统的两层管理架构，从而可以沿用现有的网络架构，提高系统的兼容性。
第三种可能的场景中，第一管理实体与第三管理实体为独立的物理实体。第一管理实体为NM，第二管理实体为EM或NF管理器，第三管理实体为NSMF或CSMF。
在这种场景下，第三管理实体位于NSMF或CSMF，第一管理实体为NM，由于第一管理实体与第三管理实体位于不同的网络实体，因此该场景下，可以沿用现有的网络架构中第一管理实体与第三管理实体的管理架构，减少对现有网络架构的改动，提高系统的兼容性。第二管理实体位于NF管理器或者EM，第二管理实体执行对UDM的配置，属于传统的两层管理架构，从而可以沿用现有的网络架构，提高系统的兼容性。
结合前面的描述，如图4所示，为本申请实施例提供的一种网络切片管理方法流程示意图。参见图4，该方法包括：
步骤401：第一管理实体向第二管理实体发送订阅管理消息，所述订阅管理消息中包括与网络切片实例对应的至少一个S-NSSAI，以及与所述至少一个S-NSSAI对应的至少一个终端设备的信息，所述至少一个终端设备具有使用所述网络切片实例的权限。
本申请实施例中，所述至少一个S-NSSAI还可以称为所述至少一个终端设备中每个终端设备的订阅S-NSSAI(subscribed S-NSSAIs)。所述至少一个S-NSSAI可以用来辅助终 端设备选择网络切片实例，具体可以参见后面的描述，在此不再赘述。
为了描述方便，本申请实施例在以下的内容中，将“与网络切片实例对应的至少一个S-NSSAI，以及与所述至少一个S-NSSAI对应的至少一个终端设备的信息”简称为“第一订阅信息”。第一订阅信息只是一个简称，不作为对订阅管理消息的限定。
第一订阅信息可以在第一管理实体和第二管理实体之间的Itf-N接口上传输，Itf-N接口为第三代伙伴计划(The 3rd Generation Partnership Project，3GPP)管理系统规定的接口。配置流程和消息遵循Itf-N上对配置消息的规定，同时，携带第一订阅信息的消息的名称，本申请实施例并不限定，本申请实施例中以订阅管理消息为例进行描述，携带第一订阅信息的消息还可以为其他消息，在此不再逐一举例说明。
本申请实施例中，一个S-NSSAI可以包含业务/切片类型(service/slicetypes,SST)，SST指示出网络切片实例的切片类型(network slice type)，网络切片实例的切片类型可以为增强型移动带宽(Enhanced Mobile Broadband,eMBB)或者高可靠性低时延(ultra-reliable low latency communications，URLLC)或者海量物联网(massive IoT(Internet of Things)，MIoT)等。在其他的实施例中，一个S-NSSAI还可以包含切片区分(slice differentiator，SD)，SD可以用于区分不同的网络切片实例，SD包含的信息本申请实施例并不限定，例如可以含有租户(customer)信息，用于区分不同租户的网络切片实例，或者其它信息。
步骤402：第二管理实体从第一管理实体接收订阅管理消息。
步骤403：所述第二管理实体向统一数据管理实体发送包括所述与网络切片实例对应的至少一个S-NSSAI以及与至少一个S-NSSAI对应的至少一个终端设备的信息，并向所述第一管理实体发送订阅管理完成消息。
其中，所述订阅管理完成消息用于指示所述与网络切片实例对应的至少一个S-NSSAI以及与至少一个S-NSSAI对应的至少一个终端设备的信息被配置在所述统一数据管理实体中。
其中，统一数据管理实体可以实现管理和存储订阅信息等功能，从而，可以根据所述第一订阅信息向终端设备，或者网络实体提供相应的内容。
在其他实施方式中，UDM实体可以将订阅数据存储到其它的数据单元，例如统一数据库(Unified Data Repository，UDR)实体，在使用时到UDR实体中读取数据。本申请仅将订阅数据配置到UDM实体，而UDM实体与其它数据单元的交互，本申请实施例并不限定。
步骤404：所述第一管理实体从所述第二管理实体接收订阅管理完成消息。
其中，所述订阅管理完成消息为所述第二管理实体将所述第一订阅信息发送至统一数据管理实体之后发送的。
在不同的实施方式中，步骤401中，第一订阅信息中，与网络切片实例对应的至少一个S-NSSAI可以通过多种方式确定。
第一种可能的方式：
S-NSSAI中的SST是根据所述网络切片实例的切片类型、所述网络切片实例支持的业务的业务类型确定。
所述至少一个S-NSSAI中，存在包含SD的S-NSSAI时，SD可以是根据一个网络切片实例的特性生成的，例如网络切片实例对应的租户信息，网络切片实例支持的业务标识，网络切片实例覆盖的地理范围等等。
在第一种可能的方式下，系统中还存在第三管理实体，第一管理实体接收来自第三管理实体发送的网络切片实例的属性信息，所述属性信息指示所述网络切片实例的切片类型和/或所述网络切片实例支持的业务类型，以用于所述第一管理实体确定所述与网络切片实例对应的至少一个S-NSSAI。所述属性信息还可以指示网络切片实例支持的业务标识、网络切片实例支持的租户信息、网络切片实例覆盖的地理范围等。
第一管理实体获取所述网络切片实例的属性信息后，根据所述属性信息生成所述至少一个S-NSSAI，每个S-NSSAI的SST为所述属性信息指示出的所述网络切片实例的切片类型、所述网络切片实例支持的业务的业务类型确定的。
所述至少一个S-NSSAI中，存在包含SD的S-NSSAI时，第一管理实体可以根据网络切片实例对应的租户信息，网络切片实例支持的业务标识，网络切片实例覆盖的地理范围等确定所述SD。
第二种可能的方式：
与所述网络切片实例对应的至少一个S-NSSAI是所述第一管理实体从第三管理实体接收到的。在第二种可能的方式下，第三管理实体可以同时向第一管理实体发送网络切片实例的属性信息，以及与所述网络切片实例对应的至少一个S-NSSAI。相应的，第一管理实体从第三管理实体接收与所述网络切片实例对应的至少一个S-NSSAI。
本申请实施例中，第一管理实体确定所述至少一个S-NSSAI之后，确定与所述至少一个S-NSSAI对应的至少一个终端设备的信息。先以一个终端设备为例进行说明，当一个终端设备订阅业务时，在与运营商的协商过程中，网络侧设备(例如可以为负责业务协商的设备)会生成一个订阅文件，该订阅文件指示出该终端设备订阅的业务，还可以指示出该终端设备的信息等，其中，终端设备的信息包括但不限于终端设备的设备标识、终端设备所属的网络、终端设备在网络中的临时标识等与终端设备相关的信息。
该终端设备的订阅文件生成之后，第一管理实体可以获取该终端设备的订阅文件，例如，第一管理实体接收网络侧设备(例如可以为负责业务协商的设备)发送的订阅文件，或者第一管理实体可以向保存所有终端设备的订阅文件的网络侧设备请求该终端设备订阅文件等方式获取该终端设备的订阅文件。当然，以上只是示例，第一管理实体可以其他方式获取该终端设备的订阅文件，本申请实施例对此并不限定，在此不再逐一举例说明。
所述第一管理实体获取该终端设备的订阅文件后，可以根据所述订阅文件确定该终端设备订阅的业务。所述第一管理实体若根据所述订阅文件确定该终端设备订阅的业务，与所述至少一个S-NSSAI所指示的网络切片实例支持的业务相同，则可以建立所述至少一个S-NSSAI与该终端设备的对应关系。即第一管理实体可以通过终端设备与订阅的业务的对应关系、业务与支持业务的网络切片实例的对应关系、网络切片实例与至少一个S-NSSAI的对应关系等对应关系，确定该终端设备与所述至少一个S-NSSAI的对应关系，从而可以建立该终端设备的信息与所述至少一个S-NSSAI的对应关系，需要说明的是，对应该终端设备的所述至少一个S-NSSAI还可以被称为该终端设备的订阅S-NSSAI(subscribed S-NSSAIs)。相应的，通过上述方式，第一管理实体可以确定出与所述至少一个S-NSSAI对应的其他终端设备，从而建立所述至少一个S-NSSAI与至少一个终端设备的信息的对应关系，在此不再赘述上述过程。
第一管理实体确定与网络切片实例对应的至少一个S-NSSAI，以及与所述至少一个S-NSSAI对应的至少一个终端设备的信息之后，可以生成所述订阅管理消息。订阅管理消 息中还可以包括终端设备的信息、以及终端设备的订阅S-NSSAI，订阅管理消息中还可以包括其他信息，本申请实施例并不限定，在此不再赘述。
步骤403中，第二管理实体接收到第一订阅信息之后，将第一订阅信息配置在统一数据管理实体中。
具体的，步骤403中，第二管理实体向统一数据管理实体发送订阅配置消息，订阅配置消息用于将所述与网络切片实例对应的至少一个S-NSSAI以及与至少一个S-NSSAI对应的至少一个终端设备的信息配置在统一数据管理实体中。统一数据管理实体配置完成第一订阅信息之后，向第二管理实体发送配置完成消息，所述配置完成消息用于指示所述与网络切片实例对应的至少一个S-NSSAI以及与至少一个S-NSSAI对应的至少一个终端设备的信息在所述统一数据管理实体中被配置完成。所述第二管理实体从所述统一数据管理实体接收配置完成消息之后，向所述第一管理实体发送订阅管理完成消息，所述订阅管理完成消息用于指示所述与网络切片实例对应的至少一个S-NSSAI以及与至少一个S-NSSAI对应的至少一个终端设备的信息被配置在所述统一数据管理实体中。
在其他的实施例中，第二管理实体也可以通过其他管理实体向统一数据管理实体发送订阅配置消息等信息。例如：第二管理实体为NSMF或NM时，第二管理实体可以通过NSSMF或EM或NF管理器向统一数据管理实体发送订阅配置消息等信息，或者第二管理实体为NSSMF时，NSSMF若没有集成EM或NF管理器的功能，则NSSMF通过EM或NF管理器向统一数据管理实体发送订阅配置消息等信息。
步骤404中，第一管理实体接收到订阅管理完成消息之后，实现了第一管理实体通过第二管理实体将至少一个S-NSSAI，以及与所述至少一个S-NSSAI对应的至少一个终端设备配置到统一数据管理实体中。统一数据管理实体中配置的S-NSSAI可以用来辅助为终端设备选择网络切片实例。举例来说，终端设备在选择需要使用的网络切片实例时，需要向为所述终端设备服务的移动性管理功能(Access and Mobility Management Function，AMF)实体发送注册请求消息，注册请求消息中可以包括P个S-NSSAI，所述P个S-NSSAI可以称为请求使用的(Requested)S-NSSAIs，所述P个S-NSSAI对应的网络切片实例就是终端设备需要选择的网络切片实例，P为大于0的整数。
AMF实体接收到该终端设备发送的P个S-NSSAI之后，向统一数据管理实体请求该终端设备的信息，以及与该终端设备的信息对应的H个S-NSSAI，H为大于0的整数，上述内容是预先配置在统一数据管理实体中的，配置的流程可以参考步骤401至步骤404。
AMF实体获得该终端设备的的信息，以及与该终端设备的信息对应的H个S-NSSAI之后，判断所述H个S-NSSAI中是否存在与该终端设备发送的P个S-NSSAI相同的P个S-NSSAI。具体的，以P个S-NSSAI中的任意一个S-NSSAI(以下称为“第一S-NSSAI”)为例说明上述判断过程，AMF实体将该第一S-NSSAI所包括的STT(以下称为“第一SST”)，与所述H个S-NSSAI进行比较。若确定所述H个S-NSSAI中至少存在一个S-NSSAI所包括的STT，与所述第一SST相同，则确定所述H个S-NSSAI中存在与所述第一S-NSSAI相同的S-NSSAI；否则，确定所述H个S-NSSAI中不存在与所述第一S-NSSAI相同的S-NSSAI。
进一步的，当第一S-NSSAI中包含SD(以下简称“第一SD”)时，AMF实体还需要判断所述H个S-NSSAI中，是否存在同时包括所述第一SST以及所述第一SD的S-NSSAI，只有同时存在包括所述第一SST以及所述第一SD时，才能确定所述H个S-NSSAI中存 在与第一S-NSSAI相同的S-NSSAI，否则可以确定所述H个S-NSSAI中不存在与所述第一S-NSSAI相同的S-NSSAI。
通过上述方法，AMF实体可以确定出所述H个S-NSSAI中是否存在与该终端设备发送的P个S-NSSAI相同的P个S-NSSAI，AMF实体若确定所述H个S-NSSAI中存在与该终端设备发送的P个S-NSSAI相同的P个S-NSSAI，则允许终端设备使用所述H个S-NSSAI对应的网络切片实例，否则不允许终端设备使用所述H个S-NSSAI对应的网络切片实例。
在另一实施例中，针对所述至少一个终端设备中的任意一个终端设备，所述至少一个S-NSSAI中的K个S-NSSAI为该终端设备的默认S-NSSAI，K为大于0的整数。当该终端设备向为所述终端设备服务的AMF实体发送注册请求消息中不包括S-NSSAI时，AMF实体接收到该注册请求消息之后，先确定该终端设备的默认S-NSSAI，然后将与该终端设备的默认S-NSSAI对应的网络切片实例，确定为所述注册请求消息所请求的网络切片实例。确定的过程可能涉及到AMF和NSSF(network slice selection function)的交互，本实施例不做限定。
在另一实施例中，第一管理实体从所述第二管理实体接收订阅管理完成消息之后，还可以修改所述至少一个S-NSSAI与所述至少一个终端设备的信息的对应关系。
结合前面的描述，使用对应至少一个S-NSSAI的网络切片实例的至少一个终端设备中的M个终端设备，需要迁移到与N个S-NSSAI对应的网络切片实例，M、N为大于0的整数。在该场景下，所述第一管理实体可以向所述第二管理实体发送N个S-NSSAI，以及与所述N个S-NSSAI对应的M个终端设备的信息，所述M个终端设备为所述至少一个终端设备中的终端设备。其中，所述N个S-NSSAI与所述至少一个S-NSSAI可以存在相同的S-NSSAI，也可以存在不相同的S-NSSAI，本申请实施例对此并不限定。
为了描述方便，本申请实施例在以下的内容中，将“N个S-NSSAI，以及与所述N个S-NSSAI对应的M个终端设备的信息”简称为“第二订阅信息”。第二订阅信息只是一个简称，不具有限定作用。
第二管理实体接收到第二订阅信息之后，向统一数据管理实体发送所述第二订阅信息，从而实现在统一数据管理实体中将所述M个终端设备对应的S-NSSAI更新为N个S-NSSAI。所述统一数据管理实体将所述M个终端设备对应的S-NSSAI更新为N个S-NSSAI之后，还可以向AMF实体发送更新消息，所述更新消息用于指示所述AMF实体触发注册管理(Registration management)过程，从而指示AMF实体将所述M个终端设备对应的S-NSSAI更新为所述N个S-NSSAI，该过程的具体内容，本申请实施例并不限定，在此不再赘述。
结合图2中的流程，下面通过具体的实施例来进一步描述订阅信息从第一管理实体配置到统一数据管理实体的过程。
如图5所示，为本申请实施例提供的一种订阅信息配置流程示意图。图5所示的流程中，订阅管理消息中包括的至少一个S-NSSAI是由第一管理实体确定的，同时，第一管理实体、第二管理实体、第三管理实体具体的实现方式，可以参考第一至第三种可能的场景中的描述，在此不再赘述。图5所示的流程中，涉及到的消息或信息的具体内容，可以参考步骤401至步骤404中的描述，在此不再重复赘述。
步骤501：第三管理实体向第一管理实体发送通知消息，所述通知消息中包括网络切片实例的属性信息。所述属性信息指示出所述网络切片实例的切片类型、所述网络切片实 例支持的业务的业务类型等信息。
步骤502：第一管理实体接收通知消息，并根据所述属性信息确定与所述网络切片实例对应的至少一个S-NSSAI。同时，所述第一管理实体根据获取到的订阅文件，确定所述订阅文件对应的至少一个终端设备订阅的业务，与所述属性信息指示出的网络切片实例支持的业务相同，则建立所述与所述网络切片实例对应的至少一个S-NSSAI与所述至少一个终端设备的信息的对应关系。
步骤503：第一管理实体向第二管理实体发送包括第一订阅信息的订阅管理消息；所述第一订阅信息为与所述网络切片实例对应的至少一个S-NSSAI以及与所述与所述网络切片实例对应的至少一个S-NSSAI对应的至少一个终端设备的信息。
步骤504：第二管理实体接收来自第一管理实体的订阅管理消息，并向统一数据管理实体发送包括所述第一订阅信息的订阅配置消息。
步骤505：统一数据管理实体接收来自统一数据管理实体的订阅配置消息，并向第二管理实体发送配置完成消息，所述配置完成消息用于指示所述第一订阅信息在所述统一数据管理实体中被配置完成。
步骤506：第二管理实体接收来自统一数据管理实体的配置完成消息，向第一管理实体发送订阅管理完成消息，所述订阅管理完成消息用于指示所述第一订阅信息被配置在所述统一数据管理实体中。
结合图2中的流程，在其他的实施例中，订阅管理消息中包括的至少一个S-NSSAI也可以由第三管理实体发送给第一管理实体，第一管理实体将所述至少一个S-NSSAI通过第二管理实体配置到统一数据管理实体中。具体可以如图6所示，为本申请又一实施例提供的一种订阅信息配置流程示意图。图6所示的流程中，第一管理实体、第二管理实体、第三管理实体具体的实现方式，可以参考第一至第三种可能的场景中的描述，在此不再赘述。图6所示的流程中，涉及到的消息或信息的具体内容，可以参考步骤401至步骤404中的描述，在此不再重复赘述。
步骤601：第三管理实体向第一管理实体发送通知消息，所述通知消息中包括网络切片实例的属性信息，与网络切片实例对应的至少一个S-NSSAI。
步骤602：所述第一管理实体接收来自第三管理实体的通知消息，并根据获取到的订阅文件，确定所述订阅文件对应的至少一个终端设备订阅的业务，与所述网络切片实例支持的业务相同，则建立所述至少一个S-NSSAI与所述至少一个终端设备的信息的对应关系。
步骤603：第一管理实体向第二管理实体发送包括第一订阅信息的订阅管理消息；所述第一订阅信息为步骤602中确定的至少一个S-NSSAI，以及与所述至少一个S-NSSAI对应的至少一个终端设备的信息。
步骤604：第二管理实体接收来自第一管理实体的订阅管理消息，并向统一数据管理实体发送包括所述第一订阅信息的订阅配置消息。
步骤605：统一数据管理实体接收来自第二管理实体的订阅配置消息，并向第二管理实体发送配置完成消息，所述配置完成消息用于指示所述第一订阅信息在所述统一数据管理实体中被配置完成。
步骤606：第二管理实体接收来自统一数据管理实体的配置完成消息，并向第一管理实体发送订阅管理完成消息，所述订阅管理完成消息用于指示所述第一订阅信息被配置在所述统一数据管理实体中。
终端设备从一个网络切片实例迁移到另一个网络切片实例时，终端设备的订阅信息也需要进行修改。下面以M个设备从网络切片实例A迁移到网络切片实例B为例进行描述。
结合图2中的流程，在又一实施例中，第一订阅信息被配置到统一数据管理实体中之后，还可能需要对S-NSSAI与终端设备的信息的对应关系进行修改，例如终端设备需要迁移到另一个网络切片实例，此时第一管理实体需要通过在统一数据管理实体中配置第二订阅信息，从而完成对S-NSSAI与终端设备的信息的对应关系的更新。具体的，如图7所示，为本申请实施例提供的又一种订阅信息配置流程示意图。图7所示的流程中，以网络切片实例A和B为例进行说明，网络切片实例A对应至少一个S-NSSAI，所述至少一个S-NSSAI与至少一个终端设备的信息对应。网络切片实例B对应N个S-NSSAI，所述至少一个终端设备中的M个终端设备需要迁移到网络切片实例B，因此第一管理实体需要重新确定所述M个终端设备对应的S-NSSAI。
步骤701：第三管理实体向第一管理实体发送网络切片实例更新消息，所述网络切片实例更新消息用于指示使用网络切片实例A中的M个终端设备，由网络切片实例A迁移到网络切片实例B。
所述网络切片实例更新消息中可以包括网络切片实例B的属性信息等信息。
步骤702：所述第一管理实体接收来自第三管理实体的网络切片实例更新消息，并建立网络切片实例B对应的N个S-NSSAI与所述M个终端设备的信息的对应关系。
步骤703：第一管理实体向第二管理实体发送包括第二订阅信息的订阅管理消息；所述第二订阅信息为所述N个S-NSSAI，以及与所述N个S-NSSAI对应的M个终端设备的信息。
步骤704：第二管理实体接收来自第一管理实体的订阅管理消息，并向统一数据管理实体发送包括所述第二订阅信息的订阅配置消息。
步骤705：统一数据管理实体接收来自第二管理实体的订阅配置消息，并向第二管理实体发送配置完成消息，所述配置完成消息用于指示所述第二订阅信息在所述统一数据管理实体中被配置完成。
步骤706：第二管理实体接收来自统一数据管理实体的配置完成消息，并向第一管理实体发送订阅管理完成消息，所述订阅管理完成消息用于指示所述第二订阅信息被配置在所述统一数据管理实体中。
步骤707：统一数据管理实体指示为所述M个终端设备服务的AMF实体将所述M个终端设备对应的S-NSSAI更新为所述N个S-NSSAI。
基于相同的技术构思，如图8所示，为本申请实施例提供的一种通信设备结构示意图。
参见图8，在一个具体的实施例中，该通信设备800可以执行图4的流程中第一管理实体所执行的动作，所述通信设备800包括：
处理模块801被配置为通过收发模块802向第二管理实体发送订阅管理消息，所述订阅管理消息中包括与网络切片实例对应的至少一个单一网络切片选择辅助信息S-NSSAI，以及与所述至少一个S-NSSAI对应的至少一个终端设备的信息，所述至少一个终端设备具有使用所述网络切片实例的权限；
所述处理模块801被配置为通过所述收发模块802从所述第二管理实体接收订阅管理完成消息，所述订阅管理完成消息用于指示所述与网络切片实例对应的至少一个S-NSSAI以及与至少一个S-NSSAI对应的至少一个终端设备的信息被配置在统一数据管理实体中。
在一种可能的设计中，所述处理模块801还被配置为：
通过所述收发模块802从第三管理实体接收所述网络切片实例的属性信息，所述属性信息用于指示所述网络切片实例的切片类型和/或所述网络切片实例支持的业务类型，以用于所述网络设备确定所述与网络切片实例对应的至少一个S-NSSAI。
在一种可能的设计中，所述S-NSSAI包括业务/切片类型SST，所述SST是根据所述网络切片实例的切片类型、所述网络切片实例支持的业务的业务类型确定。
在一种可能的设计中，所述向第二管理实体发送所述订阅管理消息之前，所述处理模块801还被配置为：
通过所述收发模块802从第三管理实体接收所述与网络切片实例对应的至少一个S-NSSA。
在一种可能的设计中，所述向第二管理实体发送所述订阅管理消息之前，所述处理模块801还被配置为：
通过所述收发模块802获取订阅文件，所述订阅文件指示出所述至少一个终端设备订阅的业务；
所述订阅管理消息中与所述至少一个S-NSSAI对应的至少一个终端设备的信息，为在所述订阅文件指示出的所述至少一个终端设备订阅的业务与所述网络切片实例支持的业务相同时确定的。
在一种可能的设计中，所述向第二管理实体发送订阅管理消息之后，所述处理模块801还被配置为：
通过所述收发模块802向所述第二管理实体发送N个S-NSSAI，以及与所述N个S-NSSAI对应的M个终端设备的信息，所述M个终端设备为所述至少一个终端设备中的终端设备，以更新所述M个终端设备对应的S-NSSAI，M、N为大于0的整数。
在又一个具体的实例中，通信设备的结构中包括处理器和收发器，用于执行图4所示的方法中第一管理实体所执行的动作。请参照图9，其示出了通信设备的一种可能的简化结构示意图。在图9所对应的示例中，通信设备900的结构中包括收发器901、处理器902、总线903以及存储器904。在图9所示的实施方式中，收发器901由发射器和接收器集成。在其他的实施方式中，发射器和接收器也可以相互独立。
一种可能的方式中，收发器901、处理器902和存储器904可以通过所述总线903相互连接；总线903可以是外设部件互连标准(peripheral component interconnect，PCI)总线或扩展工业标准结构(extended industry standard architecture，EISA)总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图9中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
所述处理器902用于对通信设备的动作进行控制管理，用于执行上述实施例中由第一管理实体执行的动作，例如通过收发器901向第二管理实体发送订阅管理消息，所述订阅管理消息中包括与网络切片实例对应的至少一个单一网络切片选择辅助信息S-NSSAI，以及与所述至少一个S-NSSAI对应的至少一个终端设备的信息，所述至少一个终端设备具有使用所述网络切片实例的权限；通过收发器901从所述第二管理实体接收订阅管理完成消息，所述订阅管理完成消息用于指示所述与网络切片实例对应的至少一个S-NSSAI以及与至少一个S-NSSAI对应的至少一个终端设备的信息被配置在统一数据管理实体中，和/或进行本申请所描述的技术的其他过程。通信设备900执行网络切片管理方法中第一管理实 体的动作的具体细节请参照图4至图7的描述，在此不再赘述。在不同的实施方式中，处理器902可以包括一个或多个处理器，例如包括一个或多个中央处理器(Central Processing Unit，CPU)，处理器902可以集成于芯片中，或者可以为芯片本身。
存储器904用于存储相关指令及数据，以及所述网络设备的程序代码和数据。在不同的实施方式中，存储器904包括但不限于是随机存储记忆体(Random Access Memory，RAM)、只读存储器(Read-Only Memory，ROM)、可擦除可编程只读存储器(Erasable Programmable Read Only Memory，EPROM)、或便携式只读存储器(Compact Disc Read-Only Memory，CD-ROM)。
可以理解的是，图9仅仅示出了所述通信设备的简化设计。在通信设备900为基站等网络设备，或者终端设备时，通信设备900可以包含任意数量的发射器、接收器、处理器、存储器，或者其他的元器件等，而所有可以实现本申请信道侦听方法的通讯设备都在本申请的保护范围之内。
基于相同的技术构思，如图10所示，为本申请实施例提供的一种通信设备结构示意图。
参见图10，在一个具体的实施例中，该通信设备1000可以执行图4的流程中第二管理实体所执行的动作，所述通信设备1000包括：处理模块1001被配置为通过收发模块1002从第一管理实体接收订阅管理消息，所述订阅管理消息中包括与网络切片实例对应的至少一个单一网络切片选择辅助信息S-NSSAI，以及与所述至少一个S-NSSAI对应的至少一个终端设备的信息，所述至少一个终端设备具有使用所述网络切片实例的权限；
所述处理模块1001还被配置为通过所述收发模块1002向统一数据管理实体发送包括所述与网络切片实例对应的至少一个S-NSSAI以及与至少一个S-NSSAI对应的至少一个终端设备的信息，并向所述第一管理实体发送订阅管理完成消息，所述订阅管理完成消息用于指示所述与网络切片实例对应的至少一个S-NSSAI以及与至少一个S-NSSAI对应的至少一个终端设备的信息被配置在所述统一数据管理实体中。
在一种可能的设计中，所述向所述第一管理实体发送订阅管理完成消息之前，所述处理模块1001还被配置为：
通过所述收发模块1002从所述统一数据管理实体接收配置完成消息，所述配置完成消息用于指示所述与网络切片实例对应的至少一个S-NSSAI以及与至少一个S-NSSAI对应的至少一个终端设备的信息在所述统一数据管理实体中被配置完成。
在一种可能的设计中，所述S-NSSAI包括业务/切片类型SST；
所述SST是根据所述网络切片实例的切片类型、所述网络切片实例支持的业务的业务类型确定。
在又一个具体的实例中，通信设备的结构中包括处理器和收发器，用于执行图4所示的方法中第二管理实体所执行的动作。请参照图11，其示出了通信设备的一种可能的简化结构示意图。在图11所对应的示例中，通信设备1100的结构中包括收发器1101、处理器1102、总线1103以及存储器1104。在图11所示的实施方式中，收发器1101由发射器和接收器集成。在其他的实施方式中，发射器和接收器也可以相互独立。
一种可能的方式中，收发器1101、处理器1102和存储器1104可以通过所述总线1103相互连接；总线1103可以是PCI总线或EISA总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图11中仅用一条粗线表示，但并不表示仅有一根总线或 一种类型的总线。
所述处理器1102用于对通信设备的动作进行控制管理，用于执行上述实施例中由第二管理实体执行的动作，例如被配置为通过收发模块1002从第一管理实体接收订阅管理消息，所述订阅管理消息中包括与网络切片实例对应的至少一个单一网络切片选择辅助信息S-NSSAI，以及与所述至少一个S-NSSAI对应的至少一个终端设备的信息，所述至少一个终端设备具有使用所述网络切片实例的权限；还被配置为通过所述收发模块1002向统一数据管理实体发送包括所述与网络切片实例对应的至少一个S-NSSAI以及与至少一个S-NSSAI对应的至少一个终端设备的信息，并向所述第一管理实体发送订阅管理完成消息，所述订阅管理完成消息用于指示所述与网络切片实例对应的至少一个S-NSSAI以及与至少一个S-NSSAI对应的至少一个终端设备的信息被配置在所述统一数据管理实体中，和/或进行本申请所描述的技术的其他过程。通信设备1100执行网络切片管理方法中第二管理实体的动作的具体细节请参照图4至图7的描述，在此不再赘述。在不同的实施方式中，处理器1102可以包括一个或多个处理器，例如包括一个或多个CPU，处理器1102可以集成于芯片中，或者可以为芯片本身。
存储器1104用于存储相关指令及数据，以及所述网络设备的程序代码和数据。在不同的实施方式中，存储器1104包括但不限于是RAM、ROM、EPROM、或CD-ROM。
可以理解的是，图11仅仅示出了所述通信设备的简化设计。在通信设备1100为基站等网络设备，或者终端设备时，通信设备1100可以包含任意数量的发射器、接收器、处理器、存储器，或者其他的元器件等，而所有可以实现本申请信道侦听方法的通讯设备都在本申请的保护范围之内。
需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。在本申请的实施例中的各功能模块可以集成在一个处理模块中，也可以是各个模块单独物理存在，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
所述集成的模块如果以软件功能模块的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
本申请同时还提出一种通信装置，用于执行图4至图7涉及第一管理实体或者第二管理实体动作的方法。该通信装置可以为芯片或者处理电路，示例性地，该芯片或者处理电路可以设置于第一管理实体或者第二管理实体中。其中，在不同的实施方式中，上述芯片中可以包括存储器，也可以不包括存储器。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算 机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
本申请实施例是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计机、嵌入式处理机或其他可编程数据处理设备的处理模块1001以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理模块1001执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
显然，本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请实施例的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (21)

  1. 一种网络切片管理方法，其特征在于，所述方法包括：
    第一管理实体向第二管理实体发送订阅管理消息，所述订阅管理消息中包括与网络切片实例对应的至少一个单一网络切片选择辅助信息S-NSSAI，以及与所述至少一个S-NSSAI对应的至少一个终端设备的信息，所述至少一个终端设备具有使用所述网络切片实例的权限；
    所述第一管理实体从所述第二管理实体接收订阅管理完成消息，所述订阅管理完成消息用于指示所述与网络切片实例对应的至少一个S-NSSAI以及与至少一个S-NSSAI对应的至少一个终端设备的信息被配置在统一数据管理实体中。
  2. 根据权利要求1所述的方法，其特征在于，所述第一管理实体向第二管理实体发送订阅管理消息之前，所述方法还包括：
    所述第一管理实体从第三管理实体接收所述网络切片实例的属性信息，所述属性信息用于指示所述网络切片实例的切片类型和/或所述网络切片实例支持的业务类型，以用于所述第一管理实体确定所述与网络切片实例对应的至少一个S-NSSAI。
  3. 根据权利要求1或2所述的方法，其特征在于，所述S-NSSAI包括业务/切片类型SST，所述SST是根据所述网络切片实例的切片类型、所述网络切片实例支持的业务的业务类型确定。
  4. 根据权利要求1所述的方法，其特征在于，所述第一管理实体向第二管理实体发送订阅管理消息之前，所述方法还包括：
    所述第一管理实体从第三管理实体接收所述与网络切片实例对应的至少一个S-NSSAI。
  5. 根据权利要求1至4任一项所述的方法，其特征在于，所述第一管理实体向第二管理实体发送订阅管理消息之前，所述方法还包括：
    所述第一管理实体获取订阅文件，所述订阅文件指示出所述至少一个终端设备订阅的业务；
    所述订阅管理消息中与所述至少一个S-NSSAI对应的至少一个终端设备的信息，为在所述订阅文件指示出的所述至少一个终端设备订阅的业务与所述网络切片实例支持的业务相同时确定的。
  6. 根据权利要求1至5任一项所述的方法，其特征在于，所述第一管理实体向第二管理实体发送订阅管理消息之后，所述方法还包括：
    所述第一管理实体向所述第二管理实体发送N个S-NSSAI，以及与所述N个S-NSSAI对应的M个终端设备的信息，所述M个终端设备为所述至少一个终端设备中的终端设备，以更新所述M个终端设备对应的S-NSSAI，M、N为大于0的整数。
  7. 一种网络切片管理方法，其特征在于，所述方法包括：
    第二管理实体从第一管理实体接收订阅管理消息，所述订阅管理消息中包括与网络切片实例对应的至少一个单一网络切片选择辅助信息S-NSSAI，以及与所述至少一个S-NSSAI对应的至少一个终端设备的信息，所述至少一个终端设备具有使用所述网络切片实例的权限；
    所述第二管理实体向统一数据管理实体发送包括所述与网络切片实例对应的至少一个S-NSSAI以及与至少一个S-NSSAI对应的至少一个终端设备的信息，并向所述第一管 理实体发送订阅管理完成消息，所述订阅管理完成消息用于指示所述与网络切片实例对应的至少一个S-NSSAI以及与至少一个S-NSSAI对应的至少一个终端设备的信息被配置在所述统一数据管理实体中。
  8. 根据权利要求7所述的方法，其特征在于，所述第二管理实体向所述第一管理实体发送订阅管理完成消息之前，所述方法还包括：
    所述第二管理实体从所述统一数据管理实体接收配置完成消息，所述配置完成消息用于指示所述与网络切片实例对应的至少一个S-NSSAI以及与至少一个S-NSSAI对应的至少一个终端设备的信息在所述统一数据管理实体中被配置完成。
  9. 根据权利要求7或8所述的方法，其特征在于，所述S-NSSAI包括业务/切片类型SST；
    所述SST是根据所述网络切片实例的切片类型、所述网络切片实例支持的业务的业务类型确定。
  10. 一种通信设备，其特征在于，所述通信设备包括：处理器和收发器；
    所述处理器，用于通过所述收发器向第二管理实体发送订阅管理消息，所述订阅管理消息中包括与网络切片实例对应的至少一个单一网络切片选择辅助信息S-NSSAI，以及与所述至少一个S-NSSAI对应的至少一个终端设备的信息，所述至少一个终端设备具有使用所述网络切片实例的权限；
    所述处理器，用于通过所述收发器从所述第二管理实体接收订阅管理完成消息，所述订阅管理完成消息用于指示所述与网络切片实例对应的至少一个S-NSSAI以及与至少一个S-NSSAI对应的至少一个终端设备的信息被配置在统一数据管理实体中。
  11. 根据权利要求10所述的通信设备，其特征在于，所述处理器还用于：
    通过所述收发器从第三管理实体接收所述网络切片实例的属性信息，所述属性信息用于指示所述网络切片实例的切片类型和/或所述网络切片实例支持的业务类型，以用于所述网络设备确定所述与网络切片实例对应的至少一个S-NSSAI。
  12. 根据权利要求10或11所述的通信设备，其特征在于，所述S-NSSAI包括业务/切片类型SST，所述SST是根据所述网络切片实例的切片类型、所述网络切片实例支持的业务的业务类型确定。
  13. 根据权利要求10所述的通信设备，其特征在于，所述向第二管理实体发送订阅管理消息之前，所述处理器还用于：
    通过所述收发器从第三管理实体接收所述与网络切片实例对应的至少一个S-NSSAI。
  14. 根据权利要求10至13任一项所述的通信设备，其特征在于，所述向第二管理实体发送订阅管理消息之前，所述处理器还用于：
    通过所述收发器获取订阅文件，所述订阅文件指示出所述至少一个终端设备订阅的业务；
    所述订阅管理消息中与所述至少一个S-NSSAI对应的至少一个终端设备的信息，为在所述订阅文件指示出的所述至少一个终端设备订阅的业务与所述网络切片实例支持的业务相同时确定的。
  15. 根据权利要求10至14任一项所述的通信设备，其特征在于，所述向第二管理实体发送订阅管理消息之后，所述处理器还用于：
    通过所述收发器向所述第二管理实体发送N个S-NSSAI，以及与所述N个S-NSSAI 对应的M个终端设备的信息，所述M个终端设备为所述至少一个终端设备中的终端设备，以更新所述M个终端设备对应的S-NSSAI，M、N为大于0的整数。
  16. 一种通信设备，其特征在于，所述通信设备包括：处理器和收发器；
    所述处理器，用于通过所述收发器从第一管理实体接收订阅管理消息，所述订阅管理消息中包括与网络切片实例对应的至少一个单一网络切片选择辅助信息S-NSSAI，以及与所述至少一个S-NSSAI对应的至少一个终端设备的信息，所述至少一个终端设备具有使用所述网络切片实例的权限；
    所述处理器，用于通过所述收发器向统一数据管理实体发送包括所述与网络切片实例对应的至少一个S-NSSAI以及与至少一个S-NSSAI对应的至少一个终端设备的信息，并向所述第一管理实体发送订阅管理完成消息，所述订阅管理完成消息用于指示所述与网络切片实例对应的至少一个S-NSSAI以及与至少一个S-NSSAI对应的至少一个终端设备的信息被配置在所述统一数据管理实体中。
  17. 根据权利要求16所述的通信设备，其特征在于，所述向所述第一管理实体发送订阅管理完成消息之前，所述处理器还用于：
    通过所述收发器从所述统一数据管理实体接收配置完成消息，所述配置完成消息用于指示所述与网络切片实例对应的至少一个S-NSSAI以及与至少一个S-NSSAI对应的至少一个终端设备的信息在所述统一数据管理实体中被配置完成。
  18. 根据权利要求16或17所述的通信设备，其特征在于，所述S-NSSAI包括业务/切片类型SST；
    所述SST是根据所述网络切片实例的切片类型、所述网络切片实例支持的业务的业务类型确定。
  19. 一种通信装置，其特征在于，包括处理器，所述处理器用于与存储器耦合，读取并执行所述存储器中的指令，以实现如权利要求1至9中任一项所述的方法。
  20. 一种可读存储介质，其特征在于，包括程序或指令，当所述程序或指令被执行时，如权利要求1至9中任意一项所述的方法被执行。
  21. 一种芯片，其特征在于，所述芯片与存储器相连，用于读取并执行所述存储器中存储的软件程序，以实现如权利要求1至9中任意一项所述的方法。
PCT/CN2018/106044 2017-09-22 2018-09-17 一种网络切片管理方法及装置 WO2019057015A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710867054.1A CN109547231B (zh) 2017-09-22 2017-09-22 一种网络切片管理方法及装置
CN201710867054.1 2017-09-22

Publications (1)

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

Family

ID=65810093

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/106044 WO2019057015A1 (zh) 2017-09-22 2018-09-17 一种网络切片管理方法及装置

Country Status (2)

Country Link
CN (1) CN109547231B (zh)
WO (1) WO2019057015A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111770558A (zh) * 2019-04-02 2020-10-13 中国移动通信有限公司研究院 一种切片接入方法、终端及网络设备
CN113098726A (zh) * 2021-06-10 2021-07-09 深圳艾灵网络有限公司 网络切片方法、设备及存储介质
EP3996331A4 (en) * 2019-08-08 2022-08-24 Huawei Technologies Co., Ltd. METHOD AND DEVICE FOR ADMINISTRATIVE DATA COLLECTION
CN115250510A (zh) * 2021-04-08 2022-10-28 维沃移动通信有限公司 选择网络的方法、装置、终端和网络设备

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112218342A (zh) * 2019-07-11 2021-01-12 中兴通讯股份有限公司 一种实现核心网子切片容灾的方法、装置和系统
CN113766607B (zh) * 2020-06-03 2023-03-31 华为技术有限公司 接入控制方法及相关设备
EP4214937A1 (en) * 2020-09-21 2023-07-26 Telefonaktiebolaget LM Ericsson (publ) Methods and devices for performing service subscriptions

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106851589A (zh) * 2016-12-30 2017-06-13 北京小米移动软件有限公司 无线网络接入方法、装置及系统
CN106982458A (zh) * 2017-03-09 2017-07-25 华为技术有限公司 一种网络切片的选择方法及装置
CN107071799A (zh) * 2017-02-16 2017-08-18 北京小米移动软件有限公司 网络切片配置方法及装置、无线接入网ran节点和终端
WO2017143047A1 (en) * 2016-02-16 2017-08-24 Idac Holdings, Inc. Network slicing operation

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017143047A1 (en) * 2016-02-16 2017-08-24 Idac Holdings, Inc. Network slicing operation
CN106851589A (zh) * 2016-12-30 2017-06-13 北京小米移动软件有限公司 无线网络接入方法、装置及系统
CN107071799A (zh) * 2017-02-16 2017-08-18 北京小米移动软件有限公司 网络切片配置方法及装置、无线接入网ran节点和终端
CN106982458A (zh) * 2017-03-09 2017-07-25 华为技术有限公司 一种网络切片的选择方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"TS 23.501: Updates to Network Slicing Description to Support NSRF", SA WG2 MEETING #S2-120, 31 March 2017 (2017-03-31), XP051247839 *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111770558A (zh) * 2019-04-02 2020-10-13 中国移动通信有限公司研究院 一种切片接入方法、终端及网络设备
EP3996331A4 (en) * 2019-08-08 2022-08-24 Huawei Technologies Co., Ltd. METHOD AND DEVICE FOR ADMINISTRATIVE DATA COLLECTION
CN115250510A (zh) * 2021-04-08 2022-10-28 维沃移动通信有限公司 选择网络的方法、装置、终端和网络设备
CN113098726A (zh) * 2021-06-10 2021-07-09 深圳艾灵网络有限公司 网络切片方法、设备及存储介质
CN113098726B (zh) * 2021-06-10 2021-09-03 深圳艾灵网络有限公司 网络切片方法、设备及存储介质
US11864103B2 (en) 2021-06-10 2024-01-02 Shenzhen Ai-Link Co., Ltd. Network slicing method and device, and storage medium

Also Published As

Publication number Publication date
CN109547231A (zh) 2019-03-29
CN109547231B (zh) 2020-10-23

Similar Documents

Publication Publication Date Title
JP7047113B2 (ja) アプリケーションのサービスレベル合意を保証するための方法、デバイスおよびシステム
WO2019057015A1 (zh) 一种网络切片管理方法及装置
US11425225B2 (en) Method, apparatus, and equipment for exposing edge network capability, and storage medium
CN111436160B (zh) 一种局域网通信方法、装置及系统
CN109314917B (zh) 网络切片选择策略更新方法、及装置
KR102387239B1 (ko) 모바일 네트워크 상호 작용 프록시
JP7184922B2 (ja) Ｕｅのためにポリシーを構成するための方法、装置、及びシステム
WO2018153346A1 (zh) 一种网络切片的选择方法及装置
WO2019062994A1 (zh) 网络切片的管理方法、设备及系统
CN111955031A (zh) 在移动通信系统中使用网络切片的方法和设备
WO2020103523A1 (zh) 一种网络切片的选择方法、网络设备及终端
WO2019007345A1 (zh) 网络切片的选择方法、装置及系统、存储介质
WO2019056883A1 (zh) 一种网络切片的部署方法及相关设备
JP2020530722A (ja) Ｐｄｕタイプ設定方法、ｕｅポリシー設定方法、および関連エンティティ
WO2019033796A1 (zh) 会话处理方法及相关设备
CN111225348B (zh) 一种应用实例迁移的方法及多接入边缘计算主机
EP3648525A1 (en) Network management method and system
WO2020103517A1 (zh) 终端的能力信息的获取方法、装置及系统
CN110650029B (zh) 一种配置方法及装置
WO2018000394A1 (zh) 网络资源的编排方法和设备
WO2019024102A1 (zh) 无线通信中的会话处理方法及终端设备
WO2019019037A1 (zh) 一种网络注册的方法、相关设备及系统
WO2022001298A1 (zh) 通信方法和通信装置
WO2022022322A1 (zh) 访问本地网络的方法和装置
WO2021056448A1 (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: 18857744

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

Country of ref document: EP

Kind code of ref document: A1