A method and apparatus for managing network slice data

Abstract

An embodiment of the present application provides a method and apparatus for managing network slice data. The method includes: a target access management function entity T-AMF receives a relocation message sent by an initial access management function entity AMF, where the relocation message includes identification information of a slice unified data management entity UDM and network slice selection assistance information NSSAI allowed by a user; the T-AMF performs authentication and registration service operations according to the relocation message. The method and apparatus for managing network slice data provided by the embodiments of the present application enable the T-AMF to avoid UDM service discovery when completing the registration process according to the UDM identifier of the home slice of the user subscription information, which is beneficial to supporting unified routing management of data, can flexibly plan and deploy slices, avoid number segment management, save resource overhead, improve registration efficiency, and meet the requirements of low latency and physical isolation.

Description

Technical Field

[0001] The present application relates to the field of communications, and in particular, to a method and apparatus for managing network slice data. Background Art

[0002] With the rapid development of mobile communications, digital transformation has almost covered all traditional industries. However, the traditional cellular network architecture can only provide unified network services and is difficult to meet the extremely diverse communication requirements brought about by the wave of digital transformation, including functional differences and performance differences. In the fifth-generation (5G) communication system, the network will be abstracted as "network slices", and one network slice meets the connection communication service requirements of a certain type or a use case. The 5G system can be composed of a large number of network slices with different connection capabilities.

[0003] A network slice instance is a real-running logical network created by a network management system and can meet certain network characteristics or service requirements. A network management system may create one or more network slice instances and manage them simultaneously, including performance monitoring, fault management, modification, etc. during the operation of the network slice instance. A complete network slice instance can provide complete end-to-end network services. In the prior art, in order to meet the isolation of slices, the Unified Data Management (UDM) and the Unified Data Repository (UDR) are deployed within the slice for isolation, and it is required that each UDM or UDR must enforce segmented management, so that users need to change cards and numbers when migrating across slices. Moreover, as the number of slices in more and more application scenarios increases, the number of segments of the UDM or UDR gradually increases, and the management becomes more complex. In order to enable users to migrate between slices without changing cards or numbers and avoid segmented management, it is urgent to propose a solution to improve the flexibility of network deployment and the friendliness of the end-user experience. Summary of the Invention

[0004] The embodiments of the present application provide a method for managing network slice data, which realizes the flexibility of the deployment of the unified data management / storage entity UDM / UDR, enables the unified data management / storage entity UDM / UDR to be orchestrated according to different slice isolation requirements, can be centrally and jointly deployed, or can be deployed down to the slice to meet the requirements of low latency and physical isolation.

[0005] In a first aspect, a method for managing network slice data is provided. The method includes: a Target Access Management Function entity (T-AMF) receives a relocation message sent by an Initial Access Management Function entity (AMF). The relocation message includes identification information of a Slice Unified Data Management entity (UDM) and Network Slice Selection Assistance Information (NSSAI) allowed for a user; the T-AMF performs authentication and registration service operations according to the relocation message.

[0006] In combination with the first aspect, in some possible implementation manners, the method further includes: the identification information of the Slice Unified Data Management entity (UDM) includes address information of the Slice Unified Data Management entity (UDM).

[0007] The method for managing network slice data provided by the embodiments of the present application obtains the UDM identifier of the home slice of the user subscription information through the relocation message received by the Target Access Management Function entity (T-AMF), so that when the T-AMF completes the registration process according to the UDM identifier of the home slice of the user subscription information, UDM service discovery is avoided, which is beneficial to supporting unified routing management of data, can flexibly plan and deploy slices, avoid number segment management, save resource overhead, improve registration efficiency, and meet the requirements of low latency and physical isolation.

[0008] In a second aspect, a method for managing network slice data is provided. The method includes: an Initial Access Management Function entity (AMF) sends a relocation message to a Target Access Management Function entity (T-AMF). The relocation message includes identification information of a Slice Unified Data Management entity (UDM) and Network Slice Selection Assistance Information (NSSAI) allowed for a user. The relocation message is used to instruct the Target Access Management Function entity (T-AMF) to complete a registration process according to the identification information of the Slice Unified Data Management entity (UDM) and the Network Slice Selection Assistance Information (NSSAI) allowed for the user.

[0009] The method for managing network slice data provided by the embodiments of the present application transmits the UDM identifier of the home slice of the user subscription information to the T-AMF through the relocation message sent by the Initial Access Management Function entity (AMF), so that when the T-AMF completes the registration process according to the UDM identifier of the home slice of the user subscription information, UDM service discovery is avoided, which is beneficial to supporting unified routing management of data, can flexibly plan and deploy slices, avoid number segment management, save resource overhead, improve registration efficiency, and meet the requirements of low latency and physical isolation.

[0010] In combination with the second aspect, in some possible implementation manners, the method further includes:

[0011] The initial access management function entity AMF sends a first user subscription data acquisition message to the common unified data management / storage entity UDM / UDR. The first user subscription data acquisition message is used to request the network slice selection assistance information NSSAI subscribed by the user and the identification information of the slice unified data management entity UDM from the common unified data management / storage entity UDM / UDR. The initial access management function entity AMF receives a first response message sent by the common unified data management / storage entity UDM / UDR. The first response message includes the network slice selection assistance information NSSAI subscribed by the user and the identification information of the slice unified data management entity UDM.

[0012] Combined with the second aspect, in some possible implementation manners, the method further includes: The identification information of the slice unified data management entity UDM includes the address information of the slice unified data management entity UDM.

[0013] The method for managing network slice data provided by the embodiments of the present application, by deploying the common unified data management / storage entity UDM / UDR, can, under the diverse requirements of the 5G network, enable the UDM / UDR to be orchestrated according to different slice isolation requirements to support rich scenarios of data slicing. It can be deployed centrally and jointly, or can be deployed down to the slice to meet the requirements of low latency and physical isolation, ensuring data security.

[0014] In a third aspect, a method for managing network slice data is provided. The method includes: The common unified data management / storage entity UDM / UDR receives a first user subscription data acquisition message sent by the initial access management function entity AMF. The first user subscription data acquisition message is used to request the network slice selection assistance information NSSAI subscribed by the user and the identification information of the slice unified data management entity UDM from the common unified data management / storage entity UDM / UDR. The common unified data management / storage entity UDM / UDR sends a first response message to the initial access management function entity AMF. The first response message includes the network slice selection assistance information NSSAI subscribed by the user and the identification information of the slice unified data management entity UDM.

[0015] The method for managing network slice data provided by the embodiments of the present application, by deploying the common unified data management / storage entity UDM / UDR, can, under the diverse requirements of the 5G network, enable the UDM / UDR to be orchestrated according to different slice isolation requirements to support rich scenarios of data slicing. It can be deployed centrally to meet the requirements of low latency and physical isolation, ensuring data security.

[0016] In combination with the third aspect, in some possible implementation manners, before the common unified data management / storage entity UDM / UDR sends a first response message to the initial access management function entity AMF, the method further includes: the common unified data management / storage entity UDM / UDR sends a second user subscription data acquisition message to the slice unified data management / storage entity UDM / UDR, where the second user subscription data acquisition message is used to request the network slice selection assistance information NSSAI subscribed by the user from the slice unified data management / storage entity UDM / UDR; the common unified data management / storage entity UDM / UDR receives a second response message sent by the slice unified data management / storage entity UDM / UDR, and the second response message includes the network slice selection assistance information NSSAI subscribed by the user.

[0017] In combination with the third aspect, in some possible implementation manners, the method further includes: the identification information of the slice unified data management entity UDM includes the address information of the slice unified data management entity UDM.

[0018] The method for managing network slice data provided by the embodiments of the present application can centrally deploy the common unified data management / storage entity UDM / UDR jointly, or can be deployed in the slice in a sinking manner, and can enable the unified data management / storage entity UDM / UDR to be orchestrated according to different slice isolation requirements, realizing the flexibility of deployment and management, thereby meeting the requirements of low latency and physical isolation for data operations.

[0019] Fourth aspect, a device for managing network slice data is provided, and the device includes:

[0020] A receiving unit, configured to receive a relocation message sent by an initial access management function entity AMF, where the relocation message includes identification information of a slice unified data management entity UDM and network slice selection assistance information NSSAI allowed by a user.

[0021] A processing unit, configured to perform authentication and registration service operations according to the relocation message.

[0022] In combination with the fourth aspect, the identification information of the slice unified data management entity UDM includes the address information of the slice unified data management entity UDM.

[0023] Fifth aspect, a device for managing network slice data is provided, and the device includes:

[0024] A sending unit, configured to send a relocation message to a target access management function entity T-AMF, where the relocation message includes identification information of a slice unified data management entity UDM and network slice selection assistance information NSSAI allowed by a user.

[0025] Among them, the relocation message is used to instruct the T-AMF to perform authentication and registration service operations.

[0026] In combination with the fifth aspect, the sending unit is further configured to send a first user subscription data acquisition message to a common unified data management / storage entity UDM / UDR, where the first user subscription data acquisition message is used to request, from the common unified data management / storage entity UDM / UDR, network slice selection assistance information NSSAI subscribed by the user and identification information of a slice unified data management entity UDM;

[0027] A receiving unit, configured to receive a first response message sent by the common unified data management / storage entity UDM / UDR, where the first response message includes the network slice selection assistance information NSSAI subscribed by the user and the identification information of the slice unified data management entity UDM.

[0028] In combination with the fifth aspect, the identification information of the slice unified data management entity UDM includes the address information of the slice unified data management entity UDM.

[0029] In a sixth aspect, there is provided an apparatus for managing network slice data, the apparatus including:

[0030] A receiving unit, configured to receive a first user subscription data acquisition message sent by an initial access management function entity AMF, where the first user subscription data acquisition message is used to request, from a common unified data management / storage entity UDM / UDR, network slice selection assistance information NSSAI subscribed by the user and identification information of a slice unified data management entity UDM;

[0031] A sending unit, configured to send a first response message to the initial access management function entity AMF, where the first response message includes the network slice selection assistance information NSSAI subscribed by the user and the identification information of the slice unified data management entity UDM.

[0032] In combination with the sixth aspect, the sending unit is further configured to send a second user subscription data acquisition message to a slice unified data management / storage entity UDM / UDR, where the second user subscription data acquisition message is used to request, from the slice unified data management / storage entity UDM / UDR, the network slice selection assistance information NSSAI subscribed by the user;

[0033] The receiving unit is further configured to receive a second response message sent by the slice unified data management / storage entity UDM / UDR, where the second response message includes the network slice selection assistance information NSSAI subscribed by the user.

[0034] Combined with the sixth aspect, the identification information of the slice unified data management entity UDM includes the address information of the slice unified data management entity UDM.

[0035] In a seventh aspect, a device for managing network slice data is provided. The structure of the device for managing network slice data includes a processor. The processor is configured to support the device for managing network slice data to execute the functions in the above first aspect or second aspect and their various implementation manners. In a possible design, the device for managing network slice data may further include a transceiver for supporting the device for managing network slice data to receive or send information.

[0036] In a possible design, the device for managing network slice data may further include a memory, which is used to be coupled with the processor to store necessary program instructions and data in the device for managing network slice data.

[0037] Or rather, the device for managing network slice data includes a memory and a processor. The memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the device for managing network slice data executes any one of the methods in the above first aspect or second aspect or third aspect and their various implementation manners.

[0038] In an eighth aspect, a computer-readable storage medium is provided. A computer program is stored in the computer-readable storage medium, and when the computer program is executed, it is used to execute the method in any possible implementation manner in the first aspect or second aspect or third aspect. Description of the Drawings

[0039] Figure 1 It is a schematic diagram of the registration process of AMF redirection in the prior art.

[0040] Figure 2 It is a schematic flowchart of a method for managing network slice data provided by an embodiment of the present application.

[0041] Figure 3 It is a schematic flowchart of another method for managing network slice data provided by an embodiment of the present application.

[0042] Figure 4 It is a schematic flowchart of another method for managing network slice data provided by an embodiment of the present application.

[0043] Figure 5 It is a schematic diagram of the registration process of AMF redirection to which the embodiment of the present application is applied.

[0044] Figure 6 It is a schematic block diagram of a device for managing network slice data provided by an embodiment of the present application.

[0045] Figure 7 It is a schematic block diagram of another device for managing network slice data provided by an embodiment of the present application.

[0046] Figure 8 It is a schematic block diagram of another device for managing network slice data provided by an embodiment of the present application. Detailed implementation manners

[0047] Next, the technical solutions in the present application will be described with reference to the accompanying drawings.

[0048] The technical solutions of the embodiments of the present application can be applied to various communication systems or network management systems that support network slices, such as: Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD), future 5th Generation (5G) systems or New Radio (NR), etc.

[0049] The terminal device in the embodiments of the present application may refer to a user equipment, an access terminal, a user unit, a user station, a mobile station, a mobile device, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent or a user device. The terminal device may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication function, a computing device or other processing devices connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a future 5G network or a terminal device in a future evolved Public Land Mobile Network (PLMN), etc., and the embodiments of the present application are not limited thereto.

[0050] It should be noted that the terms "user equipment", "terminal device", "device", etc. in this article may be replaced with each other.

[0051] Embodiments of the present application relate to network slice technology. A network slice is a logical network that can provide certain network capabilities and has certain network characteristics. A network slice is a concept of a logical network, which is specifically implemented by network slice instances. A network slice instance includes several network function instances, as well as resources such as computing, storage, and network required to form a deployed logical network. For example, in a 5G network, a network slice is a way of networking on demand, bringing new services to operators that can be adjusted according to changing user needs and quickly meet the needs of new applications.

[0052] Network slice technology abstracts the physical infrastructure resources of a 5G network into multiple network slices according to scenario requirements. Each network slice customizes and tailors network functions and orchestrates and manages corresponding network functions according to the needs of the service scenario and the service model. A network slice can be regarded as an instantiated 5G network. Such a network structure allows operators to provide the network as a service to users and can freely combine physical networks according to indicators such as rate, capacity, coverage, latency, reliability, security, and availability, so as to meet the requirements of different users.

[0053] For ease of understanding, some terms appearing in this article are introduced first:

[0054] Network slice: A network slice is a concept that refers to customizing different logical networks on physical or virtual network infrastructure. A network slice can be a complete end-to-end network including terminals, access networks, transmission networks, core networks, and application servers, capable of providing complete telecommunications services and having certain network capabilities. A network slice can also be any combination of some of the above terminals, access networks, transmission networks, core networks, and application servers. A network slice may have one or more of the following characteristics: The access network may or may not be sliced. The access network may be shared by multiple network slices. Among them, the characteristics of different network slices and the network functions that make them up may be different.

[0055] Network function: It is a processing function in the network, which defines functional behaviors and interfaces. Network functions can be implemented through dedicated hardware or in the form of virtual functions on a general 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 exclusive network functions and shared network functions. Specifically, for multiple (sub) network slice instances, different network functions can be used independently, and such network functions are called exclusive network functions; or, the same network function can also be shared, and such network functions are called shared network functions.

[0056] RAN (Radio Access Network): The radio access network, whose main function is to control users' wireless access to the mobile communication network.

[0057] AMF (Access Management Function): The access management function, which can receive non-access stratum (NAS) signaling of terminal devices and relevant signaling of access network devices, complete the user registration process, forward session management (SM) signaling, and perform mobility management.

[0058] NSSF (Network Slice Selection Function): The network slice selection function.

[0059] NRF (Network Repository Function): The network repository function.

[0060] UDM (Unified Data Management): The unified data management function, which is the permanent storage location of user subscription data and is located in the home network where the user is subscribed.

[0061] UDR (Unified Data Repository): The unified data repository.

[0062] PLMN (Public Land Mobile Network): The public land mobile network.

[0063] TAI (Tracking Area Identity): The tracking area identity.

[0064] The network slice identifier is the most important parameter in the network slice technology. The single network slice selection assistance information (S-NSSAI) can uniquely identify a network slice, while the network slice selection assistance information (NSSAI) is a collection of S-NSSAIs, identifying a group of network slices. NSSAI plays a very important role in the slice selection process. According to its storage location and function, NSSAI can be divided into the following types:

[0065] (1)Configured NSSAI: The NSSAI pre-configured in the terminal device, which can also be generated and sent to the terminal device by the NSSF or AMF, and is mainly used to generate the Requested NSSAI used during the initial registration.

[0066] (2)Subscribed NSSAI: The NSSAI subscribed by the user stored in the UDM or UDR.

[0067] (3)Allowed NSSAI: The NSSAI that allows the terminal device to access in the current registration area. It is calculated and generated by the NSSF based on the Requested NSSAI, Subscribed NSSAI, and relevant policies and then sent to the AMF and the terminal device, or directly generated by the AMF in some scenarios. It is saved in the user equipment and the AMF.

[0068] (4)Rejected NSSAI: In the registration process, when the terminal device registers successfully but there are some slices that are rejected for access, the network device sends the S-NSSAIs that are rejected for access to the terminal device, that is, the NSSAI that rejects the user equipment from accessing. For the NSSAI not supported by the PLMN, the terminal device cannot access under this PLMN anymore. For the NSSAI not supported by the current registration area, the terminal device cannot access until it moves out of this registration area.

[0069] (5)Requested NSSAI: The NSSAI that the terminal device requests to send to the AMF during the registration process based on the saved Configured NASSI, Allowed NSSAI, the serving PLMN it is in, the TAI location area it is in, etc. It can be carried in the Radio Resource Control (RRC) and NAS layer messages of the initial registration message, indicating the NSSAI that the terminal device requests to use in this registration.

[0070] GUAMI (Globally Unique AMF Identifier): The globally unique AMF identifier that identifies the AMF.

[0071] SUPI (Network Slice Subnet Management Function): The slice subnet management entity, the unique permanent identity of the user.

[0072] Figure 1 Shows a schematic diagram of the registration process of AMF redirection in the prior art.

[0073] Redirection is applied to: When the initial AMF receives a registration request sent by a terminal device and the initial AMF is not suitable for providing services to the terminal device, the AMF may need to redirect the registration request to another target AMF, and the target AMF completes the registration process. The prerequisite for redirection is that the initial AMF and the target AMF need to pre-register their capabilities on the NRF.

[0074] S100, the terminal device sends a registration request message to the RAN. The message may carry the terminal device's Requested NSSAI and GUAMI. The terminal device's Requested NSSAI includes the S-NSSAIs that the terminal device expects to register for.

[0075] S101, the RAN selects the initial AMF based on the GUAMI or the terminal device's Requested NSSAI.

[0076] S102, the RAN sends a registration request message to the initial AMF.

[0077] S103, the initial AMF queries the NRF for the address of the UDM or UDR storing the Subscribed NSSAI of the terminal device based on the number segment of the terminal device.

[0078] Specifically, the initial AMF sends a query message to the NRF. The query message carries the number segment information of the terminal device. The NRF determines the address of the UDM or UDR storing the Subscribed NSSAI corresponding to the terminal device of this number segment based on the number segment information of the terminal device.

[0079] S104, the NRF sends a response message to the initial AMF. The response message carries the address of the UDM or UDR storing the Subscribed NSSAI of the terminal device.

[0080] S105, the initial AMF sends a message to obtain user subscription data to the UDM or UDR. This message is used to obtain the Subscribed NSSAI of the terminal device stored in the UDM or UDR.

[0081] Specifically, in the existing process, the initial AMF sends a message to obtain user subscription data to the UDM. The message carries the SUPI information of the terminal device. The initial AMF requests the Subscribed NSSAI of the terminal device from the UDM by triggering the Nudm_SDM_Get service operation. The UDM executes the Nudr_DM_Query operation from the UDR to obtain the Subscribed NSSAI of the terminal device through the user's SUPI information.

[0082] S106, the UDM sends a response message to the initial AMF, and the Subscribed S-NSSAIs information corresponding to the terminal device is carried in the response message.

[0083] Specifically, in the existing process, the UDM sends a GET message response message to the initial AMF by executing the Nudm_SDM_Get operation, and the Subscribed S-NSSAIs information of the slice data corresponding to the terminal device is carried in the response message.

[0084] S107, the initial AMF sends a query message to the NSSF, and information such as the Requested NSSAI, Subscribed S-NSSAI, PLMN of the SUPI, and TAI is carried in the message. The request query message is used to query the Allowed NSSAI and the information of the serving AMF from the NSSF.

[0085] S108, after receiving the query request, the NSSF processes the request message according to the received information, local configuration, and other locally available information.

[0086] Specifically, after receiving the query message, the NSSF will perform the following operations:

[0087] (1) The NSSF verifies which S-NSSAIs in the Requested NSSAI can be allowed to access according to the Subscribed S-NSSAIs. When all S-NSSAIs in the Requested NSSAI are not in the Subscribed S-NSSAIs, the NSSF will also consider using the default Subscribed S-NSSAIs.

[0088] (2) The NSSF selects a network slice instance for the terminal device to serve. Currently, there are two ways to allocate slice instances. One is to allocate slice instances for all Allowed S-NSSAIs at registration; the other is to allocate slice instances for the terminal device only when a certain slice is used for the first time. When selecting a slice instance, the NSSF may return the slice instance identifier, or may only return the NRF dedicated to each slice instance.

[0089] (3) The NSSF determines the target AMF group serving the terminal device, or further determines the candidate AMFs according to the configuration or by querying the NRF.

[0090] (4) The NSSF determines the Allowed NSSAI according to the availability of the slice instance in the tracking area where the current terminal device is located.

[0091] S109, the NSSF sends a response message to the initial AMF, carrying the target AMF group, Allowed NSSAI, network slice instance, and NRF instance information in the message.

[0092] S110, the initial AMF determines that it is not in the AMF group based on the AMF group in the response message sent by the NSSF.

[0093] S111, the initial AMF sends a query message to the NRF, which is used to query the NRF for a list of candidate AMFs.

[0094] S112, the NRF sends a response message to the initial AMF, and the response message returns a list of available AMFs.

[0095] S113, the initial AMF selects one from the list of available AMFs as the Target AMF.

[0096] S114, the initial AMF sends a registration request message of the terminal device to the target AMF.

[0097] Specifically, the initial AMF sends the Requested NSSAI, GUAMI, S-NSSAIs that the terminal device expects to register, and the information obtained from the NSSF including: Allowed NSSAI, network slice instance, and NRF instance carried in the registration request message of the terminal device received to the target AMF.

[0098] S115, the target AMF continues to execute the relevant steps of the registration process, that is, the target AMF continues to execute the above S103 - S109 steps, and finally completes the user registration.

[0099] Therefore, it can be seen from the above process that when the target AMF continues to execute the relevant steps of the terminal device registration process, the target AMF still needs to rely on the number segment to obtain the address information of the UDM or UDR that stores the Subscribed NSSAI of the terminal device from the NRF.

[0100] Figure 2 It is a schematic flowchart of a method for managing network slice data provided by an embodiment of the present application.

[0101] S201, the access management function entity AMF sends a message to obtain user subscription data to the common unified data management / storage entity UDM / UDR. This message to obtain user subscription data is used to request the network slice selection assistance information NSSAI subscribed by the user and the identification information of the slice unified data management entity UDM from the common unified data management / storage entity UDM / UDR.

[0102] Specifically, the message for obtaining user subscription data includes user slice subnet management entity identification information, i.e., SUPI information. Based on the SUPI information, the common UDM / UDR can determine the identification information of the slice UDM that stores the network slice selection assistance information NSSAI for the corresponding user subscription, and obtain the network slice selection assistance information NSSAI for this user.

[0103] It can be understood that the identification information of this slice unified data management entity UDM is the identification information of the slice unified data management entity that stores the network slice selection assistance information for this user subscription.

[0104] S202, the common unified data management / storage entity UDM / UDR sends a response message to the access management function entity AMF. The response message includes the network slice selection assistance information NSSAI for the user subscription and the identification information of the slice unified data management entity UDM.

[0105] It should be understood that this access management function entity AMF can be the initial access management function entity or the target access management function entity T-AMF. This application does not make any limitations in this regard. When this access management function entity is the initial access management function entity, it can represent the process of obtaining the network slice selection assistance information NSSAI when the terminal device performs initial registration. When this access management function entity AMF is the target access management function entity T-AMF, it can represent the process of obtaining the network slice selection assistance information NSSAI when the terminal device performs redirected registration.

[0106] In this embodiment, the identification information of the slice unified data management entity UDM can be the address information or other information of the slice unified data management entity UDM. This application does not make any limitations in this regard.

[0107] By deploying the common unified data management / storage entity UDM / UDR, when the access management function entity AMF requests the network slice selection assistance information NSSAI from the common unified data management / storage entity UDM / UDR, the response message returned by the common unified data management / storage entity UDM / UDR carries the identification information of the slice unified data management entity UDM to which the user belongs, that is, the common unified data management / storage entity UDM / UDR uniformly manages the identification information of the slice unified data management entity UDM to which the user belongs, which can support the unified routing and management of data and can plan slice deployment more flexibly.

[0108] Figure 3 It is a schematic flowchart of another method for managing network slice data provided by an embodiment of this application.

[0109] S301, the Access and Mobility Management Function (AMF) entity sends a first user subscription data acquisition message to the Unified Data Management / Repository (UDM / UDR) entity. This first user subscription data acquisition message is used to obtain the Network Slice Selection Assistance Information (NSSAI) subscribed by the user and the identification information of the Slice Unified Data Management (UDM) entity from the Unified Data Management / Repository (UDM / UDR) entity.

[0110] S302, the Unified Data Management / Repository (UDM / UDR) entity sends a second user subscription data acquisition message to the Slice Unified Data Management / Repository (UDM / UDR) entity. This second user subscription data acquisition message is used to obtain the Network Slice Selection Assistance Information (NSSAI) subscribed by the user from the Slice Unified Data Management / Repository (UDM / UDR) entity.

[0111] S303, the Slice Unified Data Management / Repository (UDM / UDR) entity determines to store the Network Slice Selection Assistance Information (NSSAI) subscribed by the user.

[0112] S304, the Slice Unified Data Management / Repository (UDM / UDR) entity sends a second response message to the Unified Data Management / Repository (UDM / UDR) entity. The second response message includes the Network Slice Selection Assistance Information (NSSAI) subscribed by the user.

[0113] S305, the Unified Data Management / Repository (UDM / UDR) entity sends a first response message to the Access and Mobility Management Function (AMF) entity. The first response message includes the Network Slice Selection Assistance Information (NSSAI) subscribed by the user and the identification of the Slice Unified Data Management (UDM) entity.

[0114] Specifically, the Access and Mobility Management Function (AMF) entity sends a first message for obtaining user subscription data to the Unified Data Management / Repository (UDM / UDR) entity. The first message for obtaining user subscription data includes the Subscriber Permanent Identifier (SUPI) information of the user, and is used to obtain the Network Slice Selection Assistance Information (NSSAI) subscribed by the user and the identification information of the UDM entity from the Unified Data Management / Repository (UDM / UDR) entity. The identification information of the UDM entity is stored in the Unified Data Management / Repository (UDM / UDR) entity. Therefore, the Unified Data Management / Repository (UDM / UDR) entity determines the identification information of the UDM entity that manages the NSSAI subscribed by the user according to the SUPI information, and transmits the identification information of the UDM entity to the UDM / UDR entity through a second message for obtaining user subscription data. The UDM / UDR entity obtains the NSSAI subscribed by the user according to the identification information of the UDM entity, and returns it to the Unified Data Management / Repository (UDM / UDR) entity through a second response message. Finally, the Unified Data Management / Repository (UDM / UDR) entity transmits the NSSAI subscribed by the user and the identification information of the UDM entity to the AMF entity through a first response message.

[0115] Optionally, in this embodiment, the identification information of the UDM entity may be the address information of the UDM entity or other information, which is not limited in this application.

[0116] By deploying the Unified Data Management / Repository (UDM / UDR) entity, when the AMF entity requests the NSSAI subscribed by the user from the Unified Data Management / Repository (UDM / UDR) entity, the existing interface is extended to implement the information interaction between the Unified Data Management / Repository (UDM / UDR) entity and the UDM / UDR entity. The identification information of the UDM entity stored in the Unified Data Management / Repository (UDM / UDR) entity can be used to manage slices of discrete users and avoid complex number segment management problems.

[0117] Figure 4 It is a schematic flowchart of another method for managing network slice data provided by an embodiment of this application.

[0118] S401, The first Access and Mobility Management Function (AMF) entity sends a relocation message to the second AMF entity. The relocation message includes the registration request information of the terminal device, Allowed NSSAI, network slice instance, NRF instance, and the identification information of the Slice Unification Data Management (UDM).

[0119] S402, The second AMF entity performs authentication based on the information sent by the first AMF entity and completes the registration.

[0120] When the AMF entity performs the redirection registration process, it can directly locate the UDM / UDR that stores the Network Slice Selection Assistance Information (NSSAI) subscribed by the user by using the address information of the UDM / UDR. This avoids the UDM service discovery process in the redirection registration process, helps save resources, and improves the performance of the device.

[0121] Figure 5 This is a schematic diagram of the application of the embodiments of this application to the registration process of AMF redirection. When the initial AMF is not suitable for providing services to the terminal device, the initial AMF needs to send the registration request of the terminal device to another target AMF, and the target AMF completes the registration process of the terminal device. The following takes Figure 3 the method for managing network slice data shown in Figure 1 the redirection process shown as an example for description.

[0122] S500, The terminal device sends a registration request message to the Radio Access Network (RAN). The message may carry the Requested NSSAI and Globally Unique AMF Identifier (GUAMI) of the terminal device. Among them, the Requested NSSAI of the terminal device includes the S-NSSAIs that the terminal device expects to register for.

[0123] S501, The RAN selects the initial AMF based on the GUAMI or the Requested NSSAI of the terminal device.

[0124] S502, The RAN sends the registration request message of the terminal device to the initial AMF.

[0125] S503, After the initial AMF receives the registration request message of the terminal device, in order to obtain the Subscribed NSSAI of the terminal device, the initial AMF queries the identification information of the common UDM / UDR from the NRF through the number segment of the terminal device.

[0126] Specifically, the initial AMF sends a query message to the NRF. The query message carries the segment information of the terminal device. Based on the segment information of the terminal device, the NRF first needs to determine the identification information of the common UDM / UDR that manages / stores the identification information of the slice UDM / UDR. That is, the common UDM / UDR is used to manage / store the identification information of the slice UDM / UDR. When the initial AMF wants to obtain the Subscribed NSSAI corresponding to the terminal devices of this segment, it needs to first obtain the identification information of the common UDM / UDR.

[0127] S504, the NRF sends a response message to the initial AMF. The response message carries the identification information of the common UDM / UDR.

[0128] S505, using the identification information of the common UDM / UDR obtained from the NRF, the initial AMF sends a message to obtain user subscription data to the locked common UDM / UDR according to the identification information of the common UDM / UDR. This message is used to obtain the Subscribed NSSAI of the terminal device stored in the slice UDM / UDR and the identification information of the slice UDM / UDR.

[0129] S506, when receiving the message to obtain user subscription information sent from the initial AMF, the obtained common UDM / UDR determines the identification information of the slice UDM according to the SUPI information carried in the message to obtain user subscription data, and sends a message to obtain user subscription data to the slice UDM / UDR identified by this identification information. This message to obtain user subscription data is used to obtain the Subscribed NSSAI of the terminal device stored in the slice UDM / UDR.

[0130] S507, the slice UDM / UDR returns the Subscribed NSSAI of the terminal device to the common UDM / UDR through a response message.

[0131] S508, the common UDM / UDR returns the Subscribed NSSAI of the terminal device obtained from the slice UDM / UDR and the identification information of the slice UDM that stores and manages the Subscribed NSSAI of this terminal device in the common UDM / UDR to the initial AMF.

[0132] S509, the initial AMF sends a query message to the NSSF. The message carries information such as Requested NSSAI, Subscribed S-NSSAI, the PLMN and TAI of the SUPI, etc. The request query message is used to query the Allowed NSSAI and the information of the serving AMF from the NSSF.

[0133] At S510, after receiving the query request, the NSSF processes the request message based on the received information, local configuration, and other locally available information.

[0134] Specifically, after receiving the query message, the NSSF performs the following operations:

[0135] (1) The NSSF verifies which S-NSSAIs in the Requested NSSAI are allowed to access according to the Subscribed S-NSSAIs. When all S-NSSAIs in the Requested NSSAI are not in the Subscribed S-NSSAIs, the NSSF also considers using the default Subscribed S-NSSAIs.

[0136] (2) The NSSF selects a network slice instance to serve the terminal device. Currently, there are two ways to allocate slice instances. One way is to allocate slice instances for all Allowed S-NSSAIs at registration; the other way is to allocate slice instances for the terminal device only when a certain slice is used for the first time. When selecting a slice instance, the NSSF may return the slice instance identifier or may just return the NRF dedicated to each slice instance.

[0137] (3) The NSSF determines the target AMF group to serve the terminal device, or further determines candidate AMFs according to the configuration or by querying the NRF.

[0138] (4) The NSSF determines the Allowed NSSAI based on the availability of slice instances in the tracking area where the current terminal device is located.

[0139] At S511, the NSSF sends a response message to the initial AMF, carrying the target AMF group, Allowed NSSAI, network slice instance, and NRF instance information in the message.

[0140] At S512, the initial AMF determines that it is not in the AMF group according to the AMF group in the response message sent by the NSSF.

[0141] At S513, the initial AMF sends a query message to the NRF, which is used to query the NRF for a list of candidate AMFs.

[0142] At S514, the NRF sends a response message to the initial AMF, and the response message returns a list of available AMFs.

[0143] At S515, the initial AMF selects one from the list of available AMFs as the target T-AMF.

[0144] At S516, the initial AMF sends a registration request message of the terminal device to the target T-AMF.

[0145] Specifically, the initial AMF sends the Requested NSSAI, GUAMI, S-NSSAIs that the terminal device expects to register, and the information obtained from the NSSF in the registration request message of the terminal device received, including: Allowed NSSAI, network slice instance, NRF instance, and the identification information of the slice UDM obtained from the common UDM / UDR, to the target T-AMF.

[0146] S517. The target T-AMF locks the storage location of the Subscribed S-NSSAIs of the terminal device according to the received identification information of the slice UDM, no longer performs the UDM discovery process, and only performs authentication and completes user registration.

[0147] Therefore, it can be seen from the above process that by deploying the common unified data management / storage entity UDM / UDR, the address of the slice unified data management UDM is uniformly managed and stored, and the identification information of the slice unified data management UDM can be forwarded to the T-AMF through the initial AMF. When the target T-AMF executes the relevant steps of the terminal device registration process, the target T-AMF does not need to rely on the number segment to obtain the identification information of the slice UDM that manages the Subscribed NSSAI of the terminal device from the NRF. That is, compared with the prior art, during the redirection process, the T-AMF does not need the secondary slice UDM service discovery process, avoiding the secondary number segment query, improving the registration efficiency, and saving resources.

[0148] The embodiments of the present application also provide a device for implementing any of the above methods. For example, a device is provided, including units (or means) for implementing each step performed by the access management function entity AMF in any of the above methods. Again, another device is provided, including units (or means) for implementing each step performed by the common unified data management / storage entity UDM / UDR in any of the above methods.

[0149] Figure 6 is a schematic block diagram of a device for managing network slice data provided by an embodiment of the present application, as Figure 6 shown, the device 600 may include a receiving unit 601 and a processing unit 602.

[0150] The receiving unit is configured to receive a relocation message sent by the initial access management function entity AMF, where the relocation message includes the identification information of the slice unified data management entity UDM and the network slice selection assistance information NSSAI allowed by the user.

[0151] The processing unit is configured to perform authentication and registration service operations according to the relocation message.

[0152] Figure 7 is a schematic block diagram of a device for managing network slice data provided by an embodiment of the present application. As Figure 6 shown, the device 700 may include a receiving unit 701 and a transmitting unit 702.

[0153] The transmitting unit 701 is configured to send a relocation message to a target access management function entity T-AMF. The relocation message includes the identification information of the slice unified data management entity UDM and the network slice selection assistance information NSSAI allowed by the user. The relocation message is used to instruct the target access management function entity T-AMF to complete the registration process according to the identification information of the slice unified data management entity UDM and the network slice selection assistance information NSSAI allowed by the user.

[0154] Optionally, the transmitting unit 701 is further configured to send a first user subscription data acquisition message to a common unified data management / storage entity UDM / UDR. The first user subscription data acquisition message is used to request the network slice selection assistance information NSSAI subscribed by the user and the identification information of the slice unified data management entity UDM from the common unified data management / storage entity UDM / UDR;

[0155] The receiving unit 702 is configured to receive a first response message sent by the common unified data management / storage entity UDM / UDR. The first response message includes the network slice selection assistance information NSSAI subscribed by the user and the identification information of the slice unified data management entity UDM;

[0156] Optionally, the identification information of the slice unified data management entity UDM received by the receiving unit 701 and sent by the transmitting unit 702 includes the address information of the slice unified data management entity UDM.

[0157] Figure 8 is a schematic block diagram of a device for managing network slice data provided by an embodiment of the present application. As Figure 7 shown, the device 800 may include a receiving unit 801 and a transmitting unit 802.

[0158] The receiving unit 801 is configured to receive a first user subscription data acquisition message sent by an access management function entity AMF. The first user subscription data acquisition message is used to request the network slice selection assistance information NSSAI subscribed by the user and the identification information of the slice unified data management entity UDM from the common unified data management / storage entity UDM / UDR;

[0159] The sending unit 802 is used to send a first response message to the access management function entity AMF, and the first response message includes the network slice selection assistance information NSSAI subscribed by the user and the identification information of the slice unified data management entity UDM.

[0160] Optionally, before the sending unit 802 of the device sends a first response message to the access management function entity AMF, the sending unit 802 of the device is further used to send a second user subscribed data message to the slice unified data management / storage entity UDM / UDR, and the second user subscribed data message is used to request the network slice selection assistance information NSSAI subscribed by the user from the slice unified data management / storage entity UDM / UDR;

[0161] The receiving unit 801 is further used to receive a second response message sent by the slice unified data management / storage entity UDM / UDR, and the second response message includes the network slice selection assistance information NSSAI subscribed by the user.

[0162] Optionally, the identification information of the slice unified data management entity UDM received by the receiving unit 801 and sent by the sending unit 802 includes the address information of the slice unified data management entity UDM.

[0163] Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in hardware or software depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0164] This application also provides a computer-readable storage medium, and instructions are stored in the computer-readable storage medium. When the instructions are run on a computer, the computer is caused to execute each step performed by the access management function entity AMF in the method as Figures 2 to 5 shown.

[0165] This application also provides a computer-readable storage medium, and instructions are stored in the computer-readable storage medium. When the instructions are run on a computer, the computer is caused to execute each step performed by the common unified data management / storage entity UDM / UDR in the method as Figures 2 to 5 shown.

[0166] This application also provides a computer program product containing instructions. When the computer program product is run on a computer, the computer is caused to execute each step performed by the access management function entity AMF in the method as Figures 2 to 5 shown.

[0167] The present application also provides a computer program product containing instructions, which, when the computer program product runs on a computer, causes the computer to execute each step performed by the common unified data management / storage entity UDM / UDR in the method as Figures 2 to 5 shown.

[0168] The embodiment of the present application also provides a system for managing network slices, including the device corresponding to the first management function entity and the device corresponding to the second management function entity in the above embodiment.

[0169] The method disclosed in the embodiments of the present application can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit in the hardware of the processor or by instructions in the form of software. The above processor may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and may also be a system on chip (SoC), and may also be a central processing unit (CPU), a network processor (NP), a digital signal processing circuit (DSP), a microcontroller unit (MCU), a programmable logic device (PLD) or other integrated chips. It can implement or execute each method, step and logic block diagram disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as being executed and completed by the hardware decoding processor, or executed and completed by the combination of the hardware and software modules in the decoding processor. The software module may be located in a mature storage medium in the art such as a random access memory (RAM), a flash memory, a read-only memory (ROM), a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the instructions in the memory and combines its hardware to complete the steps of the above method.

[0170] It should be understood that in the embodiments of the present application, the introduction of numbers "first", "second", etc. is only to distinguish different objects. For example, to distinguish different "identifications" or different "management requests", and does not limit the protection scope of the embodiments of the present application.

[0171] It should also be understood that in various embodiments of the present application, the sequence numbers of the above processes do not indicate the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

[0172] It should also be understood that the term "and / or" in this document is merely a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this document generally represents an "or" relationship between the associated objects before and after.

[0173] Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in combination with the embodiments disclosed in this document can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0174] Those skilled in the art can clearly understand that for the convenience and conciseness of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments, and will not be elaborated herein.

[0175] In several embodiments provided in the present application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division, and there can be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed mutual coupling, direct coupling, or communication connection can be through some interfaces, and the indirect coupling or communication connection of the devices or units can be in an electrical, mechanical, or other form.

[0176] The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they can be located in one place, or can be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0177] In addition, the functional units in each embodiment of the present application can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit.

[0178] When the above-mentioned function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical discs.

[0179] As described above, the above are only specific implementation manners of this application, but the protection scope of this application is not limited thereto. Any person skilled in the art within the technical scope disclosed by this application can easily think of changes or substitutions, which should all be covered within the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

1. A method for managing network slice data, characterized in that, it includes: The initial access management function entity AMF sends a first user subscription data acquisition message to the common unified data management / storage entity UDM / UDR, and the first user subscription data acquisition message is used to request the network slice selection assistance information NSSAI subscribed by the user and the identification information of the slice unified data management entity UDM from the common UDM / UDR; The initial AMF receives a first response message sent by the common UDM / UDR, and the first response message includes the NSSAI subscribed by the user and the identification information of the slice UDM; The initial access management function entity AMF sends a relocation message to the target access management function entity T-AMF, and the relocation message includes the identification information of the slice unified data management entity UDM and the NSSAI allowed by the user, wherein, the relocation message is used to instruct the T-AMF to complete the registration process according to the identification information of the slice UDM and the NSSAI allowed by the user.

2. The method according to claim 1, characterized in that, the identification information of the slice UDM includes the address information of the slice UDM.

3. A method for managing network slice data, characterized in that, it includes: The common unified data management / storage entity UDM / UDR receives a first user subscription data acquisition message sent by the initial access management function entity AMF, and the first user subscription data acquisition message is used to request the network slice selection assistance information NSSAI subscribed by the user and the identification information of the slice unified data management entity UDM from the common UDM / UDR; The common UDM / UDR sends a first response message to the initial AMF, and the first response message includes the NSSAI subscribed by the user and the identification information of the slice UDM.

4. The method according to claim 3, characterized in that, before the common UDM / UDR sends the first response message to the initial AMF, the method further includes: The common UDM / UDR sends a second user subscription data acquisition message to the slice UDM / UDR, and the second user subscription data acquisition message is used to request the NSSAI subscribed by the user from the slice UDM / UDR; The common UDM / UDR receives a second response message sent by the slice UDM / UDR, and the second response message includes the NSSAI subscribed by the user.

5. The method according to claim 3 or 4, characterized in that, the identification information of the slice UDM includes the address information of the slice UDM.

6. An apparatus for managing network slice data, characterized in that, it includes: A sending unit, which is used to send a first user subscription data acquisition message to the common unified data management / storage entity UDM / UDR, and the first user subscription data acquisition message is used to request the network slice selection assistance information NSSAI subscribed by the user and the identification information of the slice UDM from the common UDM / UDR; A receiving unit, configured to receive a first response message sent by the common UDM / UDR, where the first response message includes the NSSAI subscribed by the user and the identification information of the slice UDM; The sending unit is further configured to send a relocation message to a target access management function entity T-AMF, where the relocation message includes the identification information of the slice unified data management entity UDM and the NSSAI allowed for the user, wherein the relocation message is used to instruct the T-AMF to complete the registration process according to the identification information of the slice UDM and the NSSAI allowed for the user.

7. The apparatus according to claim 6, wherein, the identification information of the slice UDM in the sending unit or the receiving unit includes the address information of the slice UDM.

8. An apparatus for managing network slice data, wherein, comprising: A receiving unit, configured to receive a first user subscribed data acquisition message sent by an initial access management function entity AMF, where the first user subscribed data acquisition message is used to request the network slice selection assistance information NSSAI subscribed by the user and the identification information of the slice unified data management entity UDM from a common unified data management / storage entity UDM / UDR; A sending unit, configured to send a first response message to the initial AMF, where the first response message includes the NSSAI subscribed by the user and the identification information of the slice UDM.

9. The apparatus according to claim 8, wherein, the sending unit is further configured to send a second user subscribed data acquisition message to the slice UDM / UDR, where the second user subscribed data acquisition message is used to request the NSSAI subscribed by the user from the slice UDM / UDR; the receiving unit is further configured to receive a second response message sent by the slice UDM / UDR, where the second response message includes the NSSAI subscribed by the user.

10. The apparatus according to claim 8 or 9, wherein, the identification information of the slice UDM in the sending unit or the receiving unit includes the address information of the slice UDM.

11. An apparatus for managing network slice data, wherein, comprising: A memory, configured to store a computer program; A processor, configured to execute the computer program stored in the memory, so that the apparatus executes the method according to claim 1 or 2, or executes the method according to any one of claims 3 to 5.

12. A computer-readable medium, wherein, comprising a computer program or instruction, when the computer program or instruction runs on a computer, enabling the computer to execute the method according to claim 1 or 2, or execute the method according to any one of claims 3 to 5.

Images