Network slice registration method and apparatus, communication device, storage medium, and product

Abstract

The application relates to a network slice registration method and device, communication equipment, storage medium and product. The method comprises the following steps: an AMF receives a registration request message; the registration request message is used for network slice registration. Subscription slice information of a user terminal is acquired from a UDM based on the registration request message, and configuration slice information and allowed slice information of the user terminal are acquired from a PCF. The user terminal is registered in a network slice according to the subscription slice information, the configuration slice information and the allowed slice information, and a network slice registration result is generated. That is, the network slice registration method in the embodiment of the application can not require the user terminal to participate in the process of network slice registration, that is, the AMF still normally supports network slice registration without depending on the user terminal. Further, the use range of the network slice method is expanded, and large-scale popularization and application are facilitated.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a network slicing registration method, apparatus, communication device, storage medium, and product. Background Technology

[0002] With the rapid development of communication technology, all industries are moving towards informatization, digitalization, and intelligentization. However, different types of application scenarios have different network requirements. Therefore, providing network services for different types of application scenarios through a single network cannot meet the differentiated network needs of different application scenarios, resulting in low network management efficiency and low resource utilization.

[0003] To address the issues of low network management efficiency and resource utilization, network slicing technology emerged. This technology allows the creation of multiple virtual end-to-end networks, or network slices, on a unified infrastructure, with each slice isolated from the others. Consequently, different network slices can be adapted to various application scenarios, meeting the differentiated network requirements of different application scenarios.

[0004] However, traditional network slicing methods have a limited scope of application and cannot be widely promoted and applied. Summary of the Invention

[0005] This application provides a network slicing registration method, apparatus, communication device, and computer-readable storage medium, which can expand the scope of application of network slicing methods and facilitate large-scale promotion and application.

[0006] On the one hand, a network slicing registration method is provided, applied to the Access and Mobility Management (AMF) network element, the method comprising:

[0007] Receive a registration request message; the registration request message is used to register a network slice.

[0008] Based on the registration request message, the user terminal's subscription slice information is obtained from the Unified Data Management Network Element (UDM), and the user terminal's configuration slice information and allowed slice information are obtained from the Policy Control Network Element (PCF).

[0009] Based on the signed slice information, the configured slice information, and the allowed slice information, the user terminal is registered for network slices, and a network slice registration result is generated.

[0010] On the other hand, a network slice registration method is provided, applied to a user terminal, the method comprising:

[0011] Send a registration request message to the AMF; the registration request message is used to instruct the AMF to register the user terminal with the AMF for network slices based on the user terminal's subscription slice information obtained from the UDM, the user terminal's configuration slice information and allowed slice information obtained from the PCF;

[0012] Receive a registration response message sent by AMF, which indicates whether the registration was successful or failed.

[0013] On the other hand, a network slice registration method is provided, applied to a policy control network element (PCF), the method comprising:

[0014] Receive a second acquisition request; the second acquisition request is generated based on the registration request message;

[0015] Based on the second acquisition request, the AMF is fed back the configuration slice information and allowed slice information of the user terminal, so that the AMF can perform network slice registration for the user terminal according to the configuration slice information and allowed slice information of the user terminal and the subscription slice information of the user terminal, and generate network slice registration result.

[0016] The user terminal's subscription slice information is obtained by the AMF from the Unified Data Management Network Element (UDM) based on the registration request message.

[0017] On the other hand, a network slicing registration device is provided, applied to the Access and Mobility Management (AMF) network element, the device comprising:

[0018] The registration request message receiving module is used to receive registration request messages; the registration request messages are used for network slice registration.

[0019] The slice information acquisition module is used to obtain the user terminal's subscription slice information from the unified data management network element UDM based on the registration request message, and to obtain the user terminal's configuration slice information and allowed slice information from the policy control network element PCF.

[0020] The first network slice registration module is used to register the user terminal with network slices based on the signed slice information, the configured slice information and the allowed slice information, and generate network slice registration results.

[0021] On the other hand, a network slicing registration device is provided for use in a user terminal, the device comprising:

[0022] The registration request message sending module is used to send a registration request message to the AMF; the registration request message is used to instruct the AMF to register the user terminal with the AMF for network slices based on the user terminal's subscription slice information obtained from the UDM, the user terminal's configuration slice information and allowed slice information obtained from the PCF.

[0023] The registration response message receiving module is used to receive registration response messages sent by AMF, which are used to indicate whether the registration was successful or failed.

[0024] On the other hand, a network slicing registration device is provided for PCF, the device comprising:

[0025] The second acquisition request receiving module is used to receive a second acquisition request; the second acquisition request is generated based on the registration request message;

[0026] The second network slice registration module is used to feed back the configuration slice information and allowed slice information of the user terminal to the AMF based on the second acquisition request, so that the AMF can register the network slice of the user terminal according to the configuration slice information and allowed slice information of the user terminal and the subscription slice information of the user terminal, and generate a network slice registration result.

[0027] The user terminal's subscription slice information is obtained by the AMF from the UDM based on the registration request message.

[0028] On the other hand, a communication device is provided, including a transceiver, a memory, and a processor. The memory stores a computer program, and the processor executes the computer program to control the transceiver to receive a registration request message. The registration request message is used to perform network slice registration.

[0029] The processor executes the computer program to perform the steps of the network slice registration method as described above.

[0030] On the other hand, a communication device is provided, including a transceiver, a memory, and a processor. The memory stores a computer program, and the processor executes the computer program to control the transceiver to send a registration request message to the AMF and receive a registration response message sent by the AMF.

[0031] The registration request message is used to instruct the AMF to register the user terminal with the AMF for network slices based on the user terminal's subscription slice information obtained from the UDM, the user terminal's configuration slice information and allowed slice information obtained from the PCF; the registration response message is used to indicate whether the registration was successful or failed.

[0032] On the other hand, a communication device is provided, including a transceiver, a memory, and a processor. The memory stores a computer program, and the processor executes the computer program to control the transceiver to receive a second acquisition request. The second acquisition request is generated based on a registration request message.

[0033] The processor executes the computer program to feed back the configuration slice information and allowed slice information of the user terminal to the AMF based on the second acquisition request, so that the AMF can perform network slice registration for the user terminal according to the configuration slice information and allowed slice information of the user terminal and the subscription slice information of the user terminal, and generate network slice registration result.

[0034] The user terminal's subscription slice information is obtained by the AMF from the UDM based on the registration request message.

[0035] On the other hand, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps of the network slice registration method as described above.

[0036] On the other hand, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps of the network slice registration method as described above.

[0037] The aforementioned network slice registration method, apparatus, communication equipment, storage medium, and product include an AMF (Application Function) that receives a registration request message for network slice registration. Based on the registration request message, the AMF obtains the user terminal's subscribed slice information from the Unified Data Management Element (UDM) and the user terminal's configured slice information and allowed slice information from the Policy Control Element (PCF). According to the subscribed slice information, configured slice information, and allowed slice information, the AMF registers the user terminal for network slices, generating a network slice registration result. The AMF obtains the user terminal's subscribed slice information from the UDM and the configured slice information and allowed slice information from the PCF, thus achieving network slice registration for the user terminal. This eliminates the need for the user terminal to configure and identify network slice information before sending it to the AMF, as in traditional methods. In other words, the network slice registration method in this embodiment does not require the user terminal to participate in the network slice registration process; the AMF can still support network slice registration normally without relying on the user terminal. This expands the scope of application of the network slice method and facilitates large-scale promotion and application. Attached Figure Description

[0038] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0039] Figure 1 This is a diagram illustrating the application environment of a network slice registration method in one embodiment.

[0040] Figure 2 Here is a flowchart of a network slice registration method in one embodiment;

[0041] Figure 3 for Figure 2 A flowchart illustrating the method for obtaining user terminal subscription slice information from the Unified Data Management Network Element (UDM) based on a registration request message;

[0042] Figure 4 A flowchart of a network slice registration method in another embodiment;

[0043] Figure 5 for Figure 2 A flowchart illustrating the method for obtaining configuration slice information and allowed slice information of user terminals from the policy control network element PCF;

[0044] Figure 6 for Figure 2 The flowchart describes a method for registering network slices for user terminals and generating network slice registration results based on signed slice information, configured slice information, and allowed slice information.

[0045] Figure 7 A flowchart of a network slice registration method in another embodiment;

[0046] Figure 8 Here is a flowchart of a network slice registration method in another embodiment;

[0047] Figure 9 Here is a flowchart of a network slice registration method in yet another embodiment;

[0048] Figure 10 This is a schematic diagram of a network slice registration method in an exemplary embodiment;

[0049] Figure 11 This is a structural block diagram of a network slice registration device in one embodiment;

[0050] Figure 12 This is a schematic diagram of the internal structure of an access network device in one embodiment;

[0051] Figure 13 This is a schematic diagram of the internal structure of the access network device in another embodiment;

[0052] Figure 14 This is a schematic diagram of the internal structure of a terminal device in one embodiment. Detailed Implementation

[0053] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0054] It is understood that the terms "first," "second," etc., used in this application may be used herein to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish one element from another. For example, without departing from the scope of this application, a first acquisition request may be referred to as a second acquisition request, and similarly, a second acquisition request may be referred to as a first acquisition request. Both the first acquisition request and the second acquisition request are acquisition requests, but they are not the same acquisition request.

[0055] With the rapid development of communication technology, all industries are moving towards informatization, digitalization, and intelligentization. However, different types of application scenarios have different network requirements. Therefore, providing network services for different types of application scenarios through a single network cannot meet the differentiated network needs of different application scenarios, resulting in low network management efficiency and low resource utilization.

[0056] To address the issues of low network management efficiency and resource utilization, network slicing technology emerged. This technology allows the creation of multiple virtual end-to-end networks, or network slices, on a unified infrastructure, with each slice isolated from the others. Consequently, different network slices can be adapted to various application scenarios, meeting the differentiated network requirements of different application scenarios.

[0057] Traditional network slicing methods require user terminal support to implement network slicing and registration. For example, the user terminal needs to perform operations such as initiating slice requests, selecting slices, isolating slices, and ensuring SLA (Service Level Assurance) guarantees. Through the SLA, network slicing can provide industry applications with customizable, perceptible, and predictable communication service quality, integrating it into the complete business system and enabling end-to-end control of service quality. However, currently, there are relatively few user terminals that support these network slicing functions, and upgrading existing user terminals is significantly more difficult than upgrading network equipment. Furthermore, without a clear large-scale demand, the development of network slicing functions for user terminals is generally not undertaken. Therefore, traditional network slicing methods relying on user terminals have a limited scope of application and cannot achieve large-scale deployment.

[0058] Figure 1 This is a schematic diagram illustrating the application environment of a network slice registration method in one embodiment. For example... Figure 1 As shown, the application environment includes a user equipment (UE) 120, a base station 140, core network elements 160, and an authentication server 180. The core network element 160 includes an Access and Mobility Management Function (AMF) 162, a Unified Data Management (UDM) 164, and a Policy Control Function (PCF) 166. The user equipment 120 is communicatively connected to the base station 140, the base station 140 is communicatively connected to the AMF 162, the AMF 162 is communicatively connected to the authentication server 180, the UDM 164, and the PCF 166, and the authentication server 180 is communicatively connected to the UDM 164. User terminal 120 receives a registration request message; based on the registration request message, it obtains the user terminal's subscribed slice information from UDM 164 and the user terminal's configured slice information and allowed slice information from PCF 166; according to the subscribed slice information, configured slice information, and allowed slice information, it performs network slice registration for user terminal 120 and generates a network slice registration result. The user terminal 120 can be, but is not limited to, various personal computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, smart in-vehicle devices, smart cars, etc. Portable wearable devices can include smartwatches, smart bracelets, head-mounted devices, etc.

[0059] Figure 2 This is a flowchart of a network slice registration method in one embodiment. The network slice registration method in this embodiment is designed to run on... Figure 1 The description will be based on AMF 162 as an example. Figure 2 As shown, the network slice registration method includes steps 220 to 260, wherein,

[0060] Step 220: Receive the registration request message; the registration request message is used to register network slices.

[0061] The registration request message is sent by the user terminal to the AMF via the base station, and this message is used by the AMF to register the user terminal for network slicing. The registration request message may carry the user terminal's identifier and authentication information, but it does not carry information related to the user terminal and network slices. Here, the user terminal's identifier includes the identifier of the SIM card inserted in the user terminal, the user terminal's IMEI (International Mobile Equipment Identity), and the user terminal's 5G-GUIT (5G-Global Unique Temporary Identifier), etc. However, this application does not impose limitations on these aspects.

[0062] After establishing a communication connection with the base station, the user terminal sends a registration request message to the AMF through the base station. The AMF receives the registration request message and performs network slice registration for the user terminal based on the registration request message.

[0063] Step 240: Obtain the user terminal's subscription slice information from UDM based on the registration request message, and obtain the user terminal's configuration slice information and allowed slice information from PCF.

[0064] The UDM stores a large amount of user terminal subscribed NSSAI (Subscribed NSSAI for short). NSSAI stands for Single Network Slice Selection Assistance information. In other words, the UDM stores a list of subscribed slice information supported by the UE, which includes one or more S-NSSAIs (Single NSSAIs) supported by the UE. However, this application does not impose any limitations on this.

[0065] To identify end-to-end network slices, each network slice is uniquely identified by a single Network Slice Selection Assistance Information (S-NSSAI). An S-NSSAI includes an SST (Slice / Service Type) and an SD (Slice Differentiator). A collection of one or more S-NSSAIs is called Network Slice Selection Assistance Information (NSSAI). In other words, a network slice is uniquely identified by a single S-NSSAI, and a collection of one or more S-NSSAIs is called an NSSAI.

[0066] Therefore, based on the user terminal identifier carried in the registration request message, the AMF can obtain the user terminal's subscription slice information (i.e., subscription NSSAI) from the UDM.

[0067] Secondly, the PCF stores a large amount of user terminal configuration slice information (Configured NSSAI, or simply Configuration NSSAI) and allowed slice information (Allowed NSSAI, or simply Allowed NSSAI). In other words, the PCF stores a list of UE configuration slice information, which contains one or more S-NSSAIs pre-configured for the UE; however, this application does not limit this. The Configuration NSSAI can be pre-configured in the UE's Universal Subscriber Identity Module (USIM), and can be part of the subscribed NSSAI, or it can be consistent with the subscribed NSSAI; this application does not limit this either.

[0068] Similarly, the PCF also stores a list of allowed slice information for the UE. This list contains one or more S-NSSAIs pre-allowed for the UE; however, this application does not limit this. Allowed NSSAIs refer to the NSSAIs provided by the PLMN (Public Land Mobile Network), indicating the S-NSSAIs that the UE can use in the serving PLMN of its current registration area. Generally, allowed NSSAIs include eight S-NSSAIs and are associated with the PLMN and access type (3GPP or non-3GPP). Here, 3GPP stands for 3rd Generation Partnership Project.

[0069] Therefore, based on the user terminal identifier carried in the registration request message, the AMF can obtain the user terminal's allowed slicing information from the PCF.

[0070] Step 260: Based on the contracted slice information, configured slice information, and allowed slice information, register the user terminal for network slices and generate network slice registration results.

[0071] After AMF obtains the user terminal's subscribed slice information from UDM based on the registration request message, and obtains the user terminal's configuration slice information and allowed slice information from PCF, it can perform network slice registration for the user terminal based on the subscribed slice information, configuration slice information, and allowed slice information, and generate network slice registration results.

[0072] Optionally, the AMF can select the corresponding network slice instance from the set of network slice instances serving the UE based on the intersection of the subscribed NSSAI, configured NSSAI, and allowed NSSAI, and complete the registration action through the NSSF (Network Slice Selection Function). Alternatively, the AMF can select at least 8 NSSAIs based on the intersection of the subscribed NSSAI, configured NSSAI, and allowed NSSAI, and the NSSF can select the corresponding network slice instance from the set of network slice instances serving the UE to complete the registration action. This achieves network slice registration for the user terminal and generates network slice registration results.

[0073] Here, the network slice registration result indicates whether the user terminal has successfully registered for a network slice, and provides information about the network slices successfully registered by the user terminal. After generating the network slice registration result, AMF can also send the network slice registration result back to the user terminal.

[0074] In this embodiment, the AMF receives a registration request message, obtains the user terminal's subscribed slice information from the UDM based on the registration request message, and obtains the user terminal's configured slice information and allowed slice information from the PCF. Based on the subscribed slice information, configured slice information, and allowed slice information, the AMF performs network slice registration for the user terminal, generating a network slice registration result. The AMF obtains the user terminal's subscribed slice information from the UDM and the configured slice information and allowed slice information from the PCF, thus achieving network slice registration for the user terminal. This eliminates the need for the user terminal to configure and identify network slice information before sending it to the AMF, as is required in traditional methods. In other words, the network slice registration method in this embodiment does not require the user terminal's participation in the network slice registration process; the AMF can still support network slice registration normally without relying on the user terminal. This expands the scope of application of the network slice method and facilitates large-scale promotion and application.

[0075] In the previous embodiment, the process of AMF obtaining the user terminal's subscription slice information from UDM and obtaining the user terminal's configuration slice information and allowed slice information from PCF was described, thereby realizing the network slice registration process for the user terminal. Figure 3 As shown, in this embodiment, the process of obtaining the subscription slice information is first further described. Step 240, obtaining the user terminal's subscription slice information from the UDM based on the registration request message, includes:

[0076] Step 242: If the authentication and authorization of the user terminal is successful, a first acquisition request is sent to the UDM based on the registration request message; the first acquisition request is used to instruct the UDM to provide the user terminal's subscription slice information.

[0077] Step 244: Receive the subscription slice information of the user terminal sent by UDM.

[0078] After the AMF receives the registration request message sent by the user terminal through the base station, the AMF authenticates and authorizes the user terminal with the authentication server based on the registration request message. The authentication process can be understood as the AMF using the user terminal's identifier carried in the registration request message to verify the user terminal's identity and determine if the user terminal is authorized to perform subsequent operations. The authorization process can be understood as follows: after successful identity verification with the authentication server, the AMF uses the user terminal's identifier carried in the registration request message to authorize the user terminal to determine if the user terminal has permission to access resources.

[0079] If the AMF successfully authenticates and authorizes the user terminal (authentication successful and authorization successful), it sends a first retrieval request to the UDM based on the registration request message. This first retrieval request instructs the UDM to provide the user terminal's subscription slice information. Since the UDM stores a large amount of user terminal subscription slice information (hereinafter referred to as subscription NSSAI), upon receiving the first retrieval request, the UDM can provide the AMF with the user terminal's subscription slice information based on the user terminal identifier carried in the first retrieval request.

[0080] After the UDM sends the user terminal's subscription slice information to the AMF, the AMF receives the user terminal's subscription slice information.

[0081] In this embodiment, upon successful authentication of the user terminal, the AMF sends a first acquisition request to the UDM based on a registration request message. Upon receiving the first acquisition request, the UDM, based on the user terminal identifier carried in the request, can return the user terminal's subscribed slice information to the AMF. Thus, by sending the first acquisition request to the UDM, the AMF can accurately obtain the user terminal's subscribed slice information from the UDM, facilitating subsequent network slice registration for the user terminal.

[0082] In the previous embodiment, the process by which the AMF obtains the subscription slice information of the user terminal was described. For example... Figure 4 As shown, this embodiment provides a network slice registration method, which further includes:

[0083] Step 246: Send an authentication request message to the authentication server based on the registration request message; the authentication request message is used to instruct the authentication server to authenticate the user terminal.

[0084] Upon receiving the registration request message, the AMF initiates network slice registration for the UE. Optionally, the AMF sends an authentication request message to the authentication server based on the user terminal identifier carried in the registration request message. This authentication request message instructs the authentication server to authenticate and authorize the user terminal. The authentication server then requests the user terminal's authentication vector from the UDM based on the authentication request message, and the UDM responds with the user terminal's authentication vector.

[0085] Here, the authentication and authorization vector includes the authentication vector and the authorization vector. The authentication vector (AV) is a set of parameters used for authentication. This parameter set includes at least five parameters: RAND (RandomChallenge), XRES (ExpectedResponse), CK, IK, and AUTN (AuthenticationToken). CK (Crypto Key) and IK (Integrity Key) represent the data confidentiality key and the data integrity key, respectively.

[0086] The authentication vector is a set of parameters used for authentication. This parameter set includes at least four parameters: RAND (RandomChallenge), AUTN (Authentication Token), XRES (Expected Response), and KASME. RAND is an unpredictable random number provided by the network to the UE; AUTN provides information to the UE so that the UE can use it to authenticate with the network; XRES is the expected UE authentication response parameter, used to compare with the RES (short for Resources) (or RES+RES_EXT) generated by the UE to determine whether authentication is successful; KASME is a root key derived from CK / IK and the PLMN ID (Public Land Mobile Network ID) of ASME.

[0087] Next, the authentication server matches the user terminal's authentication vector with the authentication information in the registration request message to complete the authentication process, and then sends an authentication response message to the AMF. Here, the authentication information in the registration request message includes authentication tokens, authentication keys, authentication tokens, and authentication keys, etc., but this application does not limit this information. The authentication response message may include authentication success / failure response messages and authentication success / failure response messages.

[0088] Step 248: Receive the authentication response message sent by the authentication server; the authentication response message indicates whether the user terminal has successfully authenticated.

[0089] After completing authentication, the authentication server sends an authentication response message to the AMF. This response message indicates whether the user terminal's authentication was successful. If the response message includes both authentication success and authorization success messages, the user terminal's authentication was successful. If it includes both authentication failure and authorization failure messages, the user terminal's authentication failed. Generally, if the user terminal's authentication fails, the authentication process will not be initiated; therefore, authentication failure is the default.

[0090] Of course, if the authentication response message includes both a successful authentication response message and an authentication failure response message, it means that the user terminal successfully authenticated but failed to authenticate.

[0091] In this embodiment, the AMF sends an authentication request message to the authentication server based on the registration request message. The authentication server, based on the authentication request message, requests the user terminal's authentication vector from the UDM. The UDM then returns the user terminal's authentication vector. Next, the authentication server matches the user terminal's authentication vector with the authentication information in the registration request message to complete the authentication process, and sends an authentication response message to the AMF. Finally, the AMF receives the authentication response message from the authentication server and determines whether the user terminal has successfully completed the authentication process.

[0092] Because the UDM stores a large number of user terminal authentication and authorization vectors, the AMF obtains these vectors from the UDM through the authentication server. Based on these vectors, the AMF then performs authentication and authorization on the user terminals. This accurate authentication and authorization of user terminals, based on the user terminal authentication and authorization vectors in the UDM, ultimately improves the security and reliability of the subsequent network slice registration process.

[0093] In the previous embodiment, the process of the AMF authenticating and authorizing the user terminal from the authentication server based on the registration request message sent by the user terminal through the base station was described. The detailed process of retrieving the user terminal's subscription slice information from the UDM was also described. Figure 5 As shown in this embodiment, step 240, obtaining the user terminal's configuration slice information and allowed slice information from the PCF, includes:

[0094] Step 520: Send a second acquisition request to the PCF based on the registration request message; the second acquisition request is used to instruct the PCF to provide the user terminal's configuration slice information and allowed slice information.

[0095] Step 540: Receive the configuration slice information and allowed slice information of the user terminal sent by PCF.

[0096] The registration request message does not carry information related to the user terminal and its slices. For example, it does not include the user terminal's configured slice information or allowed slice information. Therefore, after the AMF obtains the user terminal's subscribed slice information from the UDM, the AMF sends a second acquisition request to the PCF based on the registration request message. This second acquisition request instructs the PCF to provide the user terminal's configured slice information and allowed slice information.

[0097] In this application, the network slice information of a user terminal, which originally needed to be stored on the user terminal, can be transferred to the PCF. Since the PCF stores a large amount of network slice information for user terminals, such as configuration slice information and allowed slice information, after receiving the second acquisition request, the PCF can, based on the identifier of the user terminal carried in the second acquisition request, send the configuration slice information and allowed slice information of the user terminal back to the AMF. After the PCF sends the configuration slice information and allowed slice information of the user terminal to the AMF, the AMF can receive the configuration slice information and allowed slice information of the user terminal sent by the PCF.

[0098] In this embodiment, the network slice information of the user terminal, which originally needed to be stored on the user terminal, can be transferred to the PCF. Then, after the AMF obtains the user terminal's subscribed slice information from the UDM, the AMF sends a second acquisition request to the PCF based on the registration request message. Since the PCF stores a large amount of configuration slice information and allowed slice information for user terminals, after receiving the second acquisition request, the PCF can return the user terminal's configuration slice information and allowed slice information to the AMF based on the user terminal identifier carried in the second acquisition request. That is, the AMF can obtain the user terminal's configuration slice information and allowed slice information directly from the PCF, eliminating the need to obtain this information from the user terminal itself. This decouples the process of obtaining configuration slice information and allowed slice information during network slice registration from the user terminal's participation. In other words, the AMF can still support network slice registration normally without relying on the user terminal. Furthermore, this expands the scope of application of the network slicing method, facilitating large-scale promotion and application.

[0099] In the previous embodiment, it was described that the AMF sends a second acquisition request to the PCF based on a registration request message. Based on the user terminal identifier carried in the second acquisition request, the PCF can send back the user terminal's configuration slice information and allowed slice information to the AMF. Thus, the AMF can obtain the user terminal's configuration slice information and allowed slice information from the PCF. This embodiment provides a network slice registration method, which further includes:

[0100] Step 560: Send a policy association request to the PCF based on the registration request message; the policy association request is used to establish a policy association between the PCF and the AMF.

[0101] Step 580: Receive the policy association response message sent by PCF.

[0102] The AMF can also establish a policy association between the AMF and the PCF based on a registration request message. Optionally, the AMF sends a policy association request to the PCF based on the registration request message, whereby the policy association request is used to establish a policy association between the PCF and the AMF. After receiving the policy association request, the PCF sends a policy association response message back to the AMF and establishes a policy association between the PCF and the AMF. Then, the PCF can transmit the policy for the UE to the UE through the AMF. The policy association response message may include the slice-AMBR (Aggregate Maximum Bit Rate) of the serving network.

[0103] The policy association request message sent by the AMF to the PCF may include at least one of the following: subscribed S-NSSAI, allowed NSSAI, S-NSSAI mapping, subscribed slice-AMBR, SUPI (Subscription Permanent Identifier), and Home Public Land Mobile Network (HPLMN) ID. In this case, the subscribed slice-AMBR may include all subscribed slice-AMBRs received by the AMF from the UDM.

[0104] In this embodiment, the AMF can send a policy association request to the PCF based on a registration request message. After receiving the policy association request, the PCF sends a policy association response message back to the AMF, establishing a policy association between the PCF and the AMF. In this way, the AMF can not only obtain the user terminal's configuration slice information and allowed slice information from the PCF, but also establish a policy association between the PCF and the AMF. Then, the PCF can transmit the policy for the UE to the UE through the AMF.

[0105] This facilitates subsequent network slice registration for user terminals based on the user terminal's configured slice information, allowed slice information, and subscribed slice information. Furthermore, combined with the policy association established between the PCF and AMF, the PCF can accurately and transparently transmit policies for the UE through the AMF, improving the accuracy of policy transmission.

[0106] In the previous embodiment, it was described that the network slice information of the user terminal, which originally needed to be stored on the user terminal, could be transferred to the PCF. Thus, after receiving the second acquisition request, the PCF, based on the identifier of the user terminal carried in the second acquisition request, can feed back the user terminal's configuration slice information and allowed slice information to the AMF. Figure 6 As shown in this embodiment, step 260, based on the subscribed slice information, configured slice information, and allowed slice information, performs network slice registration for the user terminal and generates a network slice registration result, including:

[0107] Step 262: Determine the target slice information set from the contracted slice information, configured slice information, and allowed slice information.

[0108] After AMF obtains the user terminal's subscription slice information from UDM, and AMF obtains the user terminal's configuration slice information and allowed slice information from PCF, AMF further determines the target slice information set from the subscription slice information, configuration slice information, and allowed slice information.

[0109] Optionally, the intersection of the subscribed slice information, configured slice information, and allowed slice information is first obtained. Then, based on this intersection and the preset number of slice information, the target slice information set is determined. The preset number of slice information is related to the network's processing capacity; that is, it can be understood as the number of slice information that the network's maximum processing capacity can support. Here, the network's maximum processing capacity can be determined by the NSACF (Network Slice Access Controller) after comprehensively considering information from relevant network elements, including multiple network elements in the transport network, core network, bearer network, and access network, such as AMF, PCF, and UDM. For example, the preset number of slice information may be 6, 8, or 10.

[0110] If the number of network slices in the intersection of the acquired contracted slice information, configured slice information, and permitted slice information is less than or equal to the preset number of slices, then the intersection can be used as the target slice information set. If the number of network slices in the intersection of the acquired contracted slice information, configured slice information, and permitted slice information is greater than the preset number of slices, then a portion of the network slice information needs to be selected from the intersection as the target slice information set. The number of these selected network slices must be less than or equal to the preset number of slices.

[0111] Step 264: Based on the target slice information in the target slice information set, perform network slice registration for the user terminal and generate network slice registration results.

[0112] After determining the target slice information set from the intersection of the signed slice information, configured slice information, and allowed slice information, the AMF can perform network slice registration for user terminals based on the target slice information in the target slice information set.

[0113] Optionally, the AMF can, based on the target slice information in the target slice information set, have the NSSF select the corresponding network slice instance from the set of network slice instances serving the UE to complete the registration action. This achieves network slice registration for the user terminal and generates a network slice registration result. Here, the network slice registration result indicates whether the user terminal has successfully registered for a network slice, and provides information about the network slice successfully registered. After generating the network slice registration result, the AMF can also send the result back to the user terminal.

[0114] For example, the target slice information in the target slice information set includes {S-NSSAI 1, S-NSSAI 2, S-NSSAI 3, S-NSSAI 4, S-NSSAI 5, S-NSSAI 6, S-NSSAI 7, S-NSSAI 8}. Then, the AMF can, based on each target slice information in the target slice information set, have the NSSF select the corresponding network slice instance from the set of network slice instances serving the UE to complete the registration action. For example, for S-NSSAI 1, the NSSF selects the corresponding network slice instance from the set of network slice instances serving the UE to complete the registration action. Then, for S-NSSAI 1 again, the NSSF selects the corresponding network slice instance from the set of network slice instances serving the UE to complete the registration action, and so on, until for S-NSSAI 8, the NSSF selects the corresponding network slice instance from the set of network slice instances serving the UE to complete the registration action. If all target slices in the target slice information set are successfully registered, then the successfully registered network slice information in the generated network slice registration result will include {S-NSSAI 1, S-NSSAI 2, S-NSSAI 3, S-NSSAI 4, S-NSSAI 5, S-NSSAI 6, S-NSSAI 7, S-NSSAI 8}.

[0115] In this embodiment, the AMF determines the target slice information set from the subscribed slice information, configured slice information, and allowed slice information. Then, based on the target slice information in the target slice information set, the user terminal performs network slice registration, generating a network slice registration result. Since different network slices can adapt to various application scenarios, registering the user terminal with network slices based on the target slice information in the target slice information set can meet the differentiated network requirements of different application scenarios on the user terminal.

[0116] Furthermore, the network slice registration method in this embodiment does not require the user terminal to participate in the network slice registration process. That is, AMF can still normally support network slice registration without relying on the user terminal. This expands the scope of application of the network slicing method and facilitates large-scale promotion and application.

[0117] In the previous embodiment, the AMF was described as determining a target slice information set from subscribed slice information, configured slice information, and allowed slice information. Then, based on the target slice information in the target slice information set, the user terminal was registered for network slices. This embodiment provides a network slice registration method, which further includes:

[0118] If the network slice registration result includes the target slice information that has been successfully registered, a registration acceptance message is sent to the user terminal; the registration acceptance message is used to indicate that the AMF has successfully registered the network slice for the user terminal.

[0119] If the network slice registration result does not include the target slice information that was successfully registered, a registration rejection message is sent to the user terminal; the registration rejection message is used to indicate that the AMF failed to register the network slice for the user terminal.

[0120] Based on the target slice information in the target slice information set, AMF sequentially registers the user terminal with network slices and generates network slice registration results. If the network slice registration result includes at least one successfully registered target slice, it indicates that the user terminal has successfully registered with the network slice corresponding to that target slice, and a registration acceptance message can be sent to the user terminal. The registration acceptance message signifies that AMF has successfully registered the user terminal with the network slice.

[0121] If the network slice registration result does not include the target slice information for successful registration, it indicates that the user terminal has not successfully registered with a network slice. In this case, a registration rejection message can be sent to the user terminal. The registration rejection message indicates that the AMF failed to register the user terminal with the network slice.

[0122] In this embodiment, the AMF sequentially registers network slices for the user terminal based on the target slice information in the target slice information set, generating a network slice registration result. If the network slice registration result includes successfully registered target slice information, a registration acceptance message is sent to the user terminal; the registration acceptance message indicates that the AMF has successfully registered the network slice for the user terminal. Conversely, a registration rejection message is sent to the user terminal; the registration rejection message indicates that the AMF has failed to register the network slice for the user terminal.

[0123] When the AMF successfully registers a network slice for a user terminal, it promptly sends a registration acceptance message to the user terminal. This allows the user terminal to access the successfully registered network slice, meeting the differentiated network requirements of various application scenarios on the user terminal. Conversely, if the AMF fails to register a network slice for a user terminal, it promptly sends a registration rejection message to the user terminal. This allows the user terminal to adjust its network slice registration strategy and re-initiate the registration process.

[0124] In the previous embodiment, the process was described in which the AMF registers the user terminal with network slices in sequence based on the target slice information in the target slice information set, and then promptly sends registration acceptance information or feedback registration rejection information to the user terminal.

[0125] like Figure 7 As shown, in this embodiment, a network slice registration method is provided, which further includes:

[0126] Step 266: Obtain the successfully registered target slice information from the network slice registration results, and use the successfully registered target slice information as the new allowed slice information;

[0127] Step 268: Update the allowed slicing information in the PCF based on the new allowed slicing information.

[0128] If the network slice registration result includes at least one successfully registered target slice, it indicates that the user terminal has successfully registered with the network slice corresponding to that target slice. In this case, the AMF can send a registration acceptance message to the user terminal. This registration acceptance message signifies that the AMF has successfully registered the user terminal for the network slice.

[0129] On the other hand, the AMF can obtain the information of successfully registered target slices from the network slice registration results and use this information as new allowed slice information. For example, if the information of successfully registered network slices in the network slice registration results includes {S-NSSAI 1, S-NSSAI 2, S-NSSAI 3, S-NSSAI 4, S-NSSAI 5, S-NSSAI 6, S-NSSAI 7, S-NSSAI 8}, then this information will be used as new allowed slice information. That is, the new allowed slice information will include {S-NSSAI 1, S-NSSAI 2, S-NSSAI 3, S-NSSAI 4, S-NSSAI 5, S-NSSAI 6, S-NSSAI 7, S-NSSAI 8}.

[0130] However, the allowed slice information stored in the PCF is the information before it was updated. Therefore, the allowed slice information in the PCF is updated based on the new allowed slice information to ensure that the allowed slice information in the PCF is consistent with the latest allowed slice information in real time. Optionally, it can be determined whether the allowed slice information stored in the PCF is consistent with the latest allowed slice information. If they are consistent, then it is not necessary to update the allowed slice information in the PCF. If they are inconsistent, then it is necessary to update the allowed slice information in the PCF based on the new allowed slice information.

[0131] In this embodiment, the AMF obtains the successfully registered target slice information from the network slice registration results and uses it as the new allowed slice information. Then, it updates the allowed slice information in the PCF based on the new allowed slice information. This ensures that the AMF updates the allowed slice information in the PCF based on the successfully registered target slice information after each network slice registration for a user terminal. This guarantees that the allowed slice information in the PCF is consistent with the latest allowed slice information in real time. Therefore, when the AMF obtains allowed slice information and configuration slice information from the PCF next time, the real-time performance and accuracy of the allowed slice information obtained by the AMF can be guaranteed. Furthermore, this increases the probability of the AMF successfully registering network slices for the user terminal based on the subscribed slice information, configuration slice information, and allowed slice information.

[0132] Secondly, since this application allows the allowed slice information and configuration slice information of the user terminal, which originally needed to be stored on the user terminal, to be transferred to the PCF, the allowed slice information in the PCF can be updated based on the new allowed slice information. This eliminates the need to distribute the new allowed slice information to the user terminal for storage, thus reducing the reliance on the user terminal to some extent.

[0133] In the previous embodiment, the process was described whereby the AMF obtains successfully registered target slice information from the network slice registration results and uses this information as new allowed slice information. The allowed slice information in the PCF is then updated based on this new allowed slice information. In this embodiment, step 262 is further described, which involves determining the target slice information set from the subscribed slice information, configuration slice information, and allowed slice information, including:

[0134] Obtain the intersection of slice information among contracted slice information, configured slice information, and allowed slice information;

[0135] The target slice information set is determined from the candidate slice information intersection according to the priority order of each candidate slice information and the preset number of slice information; the preset number of slice information is related to the processing capacity of the network.

[0136] Optionally, the intersection of the subscribed slice information, configured slice information, and allowed slice information is first obtained. Then, based on this intersection and the preset number of slice information, the target slice information set is determined. The preset number of slice information is related to the network's processing capacity; that is, it can be understood as the number of slice information that the network's maximum processing capacity can support. Here, the network's maximum processing capacity can be determined by the NSACF (Network Slice Access Controller) after comprehensively considering information from relevant network elements, including multiple network elements in the transport network, core network, bearer network, and access network, such as AMF, PCF, and UDM. For example, the preset number of slice information may be 6, 7, 8, 9, or 10.

[0137] If the number of network slice information in the intersection of the acquired contracted slice information, configured slice information, and allowed slice information is less than or equal to the preset number of slice information, then the intersection of the three can be used as the target slice information set.

[0138] If the number of network slices in the intersection of the acquired contracted slice information, configured slice information, and allowed slice information is greater than the preset number of slices, then a portion of the network slices in the intersection needs to be selected as the target slice information set. The number of these selected network slices must be less than or equal to the preset number of slices. Optionally, the target slice information set is determined from the candidate intersection according to the priority order of each candidate slice and the preset number of slices. The priority order of each candidate slice can be determined based on its usage frequency; for example, the candidate slices corresponding to each candidate slice can be sorted from highest to lowest usage frequency. Alternatively, the priority order can be determined based on parameters such as the network quality of each candidate slice.

[0139] Furthermore, according to the priority order of each candidate slice information in the intersection of slice information, a predetermined number of candidate slice information with the highest ranking is obtained from the intersection of slice information to form the target slice information set. For example, if the predetermined number of slice information is 8, then according to the priority order of each candidate slice information in the intersection of slice information, the top 8 candidate slice information is obtained from the intersection of slice information to form the target slice information set.

[0140] In this embodiment, the AMF obtains the intersection of segment information among the subscribed segment information, configured segment information, and allowed segment information. Then, according to the priority order of each candidate segment information in the intersection and a preset number of segment information, it determines the target segment information set from the candidate intersection. Since the preset number of segment information is related to the network's processing capacity, the AMF can not only determine the target segment information set that matches the network's processing capacity from the segment information intersection, but also accurately and orderly determine the best candidate segment information as the target segment information set based on the priority order of each candidate segment information. This improves the registration success rate of the AMF in registering network segments for user terminals based on the target segment information in the target segment information set.

[0141] Based on the same inventive concept, in this embodiment, such as Figure 8 As shown, a network slice registration method is provided and applied to a user terminal. The method includes:

[0142] Step 802: Send a registration request message to the AMF; the registration request message is used to instruct the AMF to register the user terminal with the AMF for network slices based on the user terminal's subscription slice information obtained from the UDM, the user terminal's configuration slice information and allowed slice information obtained from the PCF.

[0143] Step 804: Receive the registration response message sent by AMF. The registration response message is used to indicate whether the registration was successful or failed.

[0144] In this embodiment, the user terminal sends a registration request message to the AMF via a base station. This enables the AMF to obtain the user terminal's subscribed slice information from the UDM and its configured slice information and allowed slice information from the PCF. Based on these information, the AMF performs network slice registration for the user terminal on the AMF, generating a network slice registration result. Based on the network slice registration result, the AMF then sends back either registration acceptance or registration rejection information. Finally, the user terminal receives the registration acceptance or rejection information from the AMF.

[0145] Since the registration request message does not carry information related to the user terminal and network slices, it eliminates the need for the user terminal to configure and identify network slice information before sending it to the AMF, as is required in traditional methods, to register the user terminal for network slices. In other words, the network slice registration method in this embodiment does not require the user terminal to participate in the registration process; the AMF can still support network slice registration normally without relying on the user terminal. This expands the scope of application of the network slice method and facilitates large-scale deployment and application.

[0146] Based on the same inventive concept, such as Figure 9 As shown, a network slice registration method is provided, applied to PCF, and the method includes:

[0147] Step 902: Receive a second acquisition request; the second acquisition request is generated based on the registration request message;

[0148] Step 904: Based on the second acquisition request, the configuration slice information and allowed slice information of the user terminal are fed back to the AMF, so that the AMF can perform network slice registration for the user terminal according to the configuration slice information and allowed slice information of the user terminal and the subscription slice information of the user terminal, and generate network slice registration result.

[0149] Among them, the user terminal's subscription slice information is obtained by the AMF from the UDM based on the registration request message.

[0150] In this embodiment, the PCF receives a second acquisition request, which is generated based on a registration request message. Then, based on the second acquisition request, the PCF sends the user terminal's configuration slice information and allowed slice information to the AMF, enabling the AMF to register the user terminal for network slices according to the user terminal's configuration slice information, allowed slice information, and subscribed slice information, thereby generating a network slice registration result.

[0151] Since the registration request message does not carry information related to the user terminal and network slices, it eliminates the need for the user terminal to configure and identify network slice information before sending it to the AMF, as is required in traditional methods, to register the user terminal for network slices. In other words, the network slice registration method in this embodiment does not require the user terminal to participate in the registration process; the AMF can still support network slice registration normally without relying on the user terminal. This expands the scope of application of the network slice method and facilitates large-scale deployment and application.

[0152] In one exemplary embodiment, such as Figure 10 As shown, a network slice registration method is provided for operation in Figure 1The description is based on the Access and Mobility Management Element (AMF) 162 in the example, including:

[0153] Step 1002: The user terminal sends a Registration Request message to the base station. This Registration Request message does not carry information related to the user terminal and the slice.

[0154] Step 1004: The base station selects an Access and Mobility Management Element (AMF) based on the registration request message; for example, the base station can select a suitable AMF based on the 5G-TMSI (Temporary Mobile Subscriber Identity) and GUAMI (Globally Unique AMFID) carried in the registration request message; the base station can also select a suitable AMF based on the AMF information indicated in the registration request message, or based on the AMF information pre-configured by the base station; wherein,

[0155] Step 1006: The base station forwards the registration request message to the Access and Mobility Management Element (AMF);

[0156] Step 1008: After receiving the registration request message, the AMF initiates the network slice registration function for the UE;

[0157] Step 1010: The Access and Mobility Management Element (AMF) sends an authentication request message to the authentication server;

[0158] Step 1012: The authentication server extracts the authentication and authorization vector of the user terminal (UE) from the unified data management network element (UDM);

[0159] Step 1014: The Unified Data Management Element (UDM) returns the authentication and authorization vector for the UE;

[0160] Step 1016: The authentication server matches the UE's authentication vector with the authentication information in the registration request message to complete the authentication and sends a successful authentication response to the AMF.

[0161] Step 1018: The Access and Mobility Management Element (AMF) requests the subscription information of the User Terminal (UE) from the Unified Data Management Element (UDM). The subscription information includes the subscription slice information (subscription NSSAI) of the User Terminal (UE).

[0162] Step 1020: The Unified Data Management Element (UDM) returns the subscription information of the User Terminal (UE) to the Inbound and Mobility Management Element (AMF). The subscription information includes subscription slice information (subscription NSSAI).

[0163] Step 1022: The AMF sends a policy association request to the policy control unit (PCF) to request the UE's Configured NSSAI and Allowed NSSAI.

[0164] Step 1024: The Policy Control Unit (PCF) returns a Policy Association Response Message to the AMF, and also returns the UE's Configured NSSAI and Allowed NSSAI;

[0165] Step 1026: The AMF checks and compares the signed NSSAI from the UDM with the configured NSSAI and allowed NSSAI from the Policy Control Unit (PCF), and extracts the intersection of the three for registration (e.g., the intersection of the three includes no more than 10 network slice information).

[0166] Step 1028: Based on the intersection of the three, AMF performs network slice registration for the user terminal; if the registration is successful, it sends a registration acceptance message to the base station; if the registration fails, it sends a registration rejection message to the base station.

[0167] Step 1030: The base station forwards the registration acceptance information or registration rejection information from the AMF.

[0168] In this embodiment, the AMF receives a registration request message. This message is used for network slice registration and does not carry information related to the user terminal or slices. Based on the registration request message, the AMF obtains the user terminal's subscribed slice information from the UDM and the user terminal's configured slice information and allowed slice information from the PCF. According to the subscribed slice information, configured slice information, and allowed slice information, the AMF performs network slice registration for the user terminal, generating a network slice registration result. The AMF obtains the user terminal's subscribed slice information from the UDM and the configured slice information and allowed slice information from the PCF, thus achieving network slice registration for the user terminal. This eliminates the need for the user terminal to configure and identify network slice information before sending it to the AMF, as is required in traditional methods. In other words, the network slice registration method in this embodiment does not require the user terminal's participation in the network slice registration process; the AMF can still support network slice registration normally without relying on the user terminal. This expands the scope of application of the network slice method and facilitates large-scale promotion and application.

[0169] It should be understood that although the steps in the flowchart above are shown sequentially as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowchart above may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0170] Based on the same inventive concept, such as Figure 11 As shown, a network slicing registration device 1100 is provided, applied to access and mobility management network elements. The device includes:

[0171] The registration request message receiving module 1120 is used to receive registration request messages; the registration request messages are used for network slice registration.

[0172] The slice information acquisition module 1140 is used to obtain the user terminal's subscription slice information from the UDM based on the registration request message, and to obtain the user terminal's configuration slice information and allowed slice information from the PCF.

[0173] The first network slice registration module 1160 is used to register the network slice for the user terminal based on the contracted slice information, configured slice information and allowed slice information, and generate the network slice registration result.

[0174] In one embodiment, the slice information acquisition module 1140 includes:

[0175] The first acquisition request sending unit is used to send a first acquisition request to the UDM based on the registration request message when the authentication and authorization of the user terminal is successful; the first acquisition request is used to instruct the UDM to provide the subscription slice information of the user terminal.

[0176] The subscription slice information receiving unit is used to receive subscription slice information of user terminals sent by UDM.

[0177] In one embodiment, a network slice registration apparatus is provided, the apparatus further comprising:

[0178] The authentication and authorization module is used to send an authentication and authorization request message to the authentication server based on the registration request message; the authentication and authorization request message is used to instruct the authentication server to authenticate and authorize the user terminal; it receives the authentication and authorization response message sent by the authentication server; the authentication and authorization response message indicates whether the user terminal has been successfully authenticated and authorized.

[0179] In one embodiment, the slice information acquisition module 1140 further includes:

[0180] The second acquisition request unit is used to send a second acquisition request to the PCF based on the registration request message; the second acquisition request is used to instruct the PCF to provide the configuration slice information and allowed slice information of the user terminal.

[0181] The configuration and allow slice information receiving unit is used to receive the configuration slice information and allow slice information of the user terminal sent by the PCF.

[0182] In one embodiment, a network slice registration apparatus is provided, the apparatus further comprising:

[0183] The policy association module is used to send a policy association request to the PCF based on the registration request message; the policy association request is used to establish a policy association between the PCF and the AMF; and to receive the policy association response message sent by the PCF.

[0184] In one embodiment, the first network slice registration module 1160 includes:

[0185] The target slice information set determination unit is used to determine the target slice information set from the contracted slice information, configured slice information, and allowed slice information;

[0186] The network slice registration unit is used to register the network slice of the user terminal based on the target slice information in the target slice information set and generate the network slice registration result.

[0187] In one embodiment, a network slice registration apparatus is provided, the apparatus further comprising:

[0188] The registration acceptance information sending module is used to send registration acceptance information to the user terminal if the network slice registration result includes the target slice information that has been successfully registered; the registration acceptance information is used to indicate that the AMF has successfully registered the network slice for the user terminal.

[0189] In one embodiment, a network slice registration apparatus is provided, the apparatus further comprising:

[0190] The registration rejection information sending module is used to send registration rejection information to the user terminal if the network slice registration result does not include the target slice information that was successfully registered; the registration rejection information is used to indicate that the AMF failed to register the network slice for the user terminal.

[0191] In one embodiment, a network slice registration apparatus is provided, the apparatus further comprising:

[0192] The allowed slice information update module is used to obtain the successfully registered target slice information from the network slice registration results, use the successfully registered target slice information as the new allowed slice information, and update the allowed slice information in PCF based on the new allowed slice information.

[0193] In one embodiment, the target slice information set determination unit is further configured to obtain the intersection of slice information among the contracted slice information, configured slice information, and allowed slice information; determine the target slice information set from the candidate intersection according to the priority order of each candidate slice information in the slice information intersection and the preset number of slice information; the preset number of slice information is related to the processing capacity of the network.

[0194] In one embodiment, the registration request message does not include the user terminal's configuration slice information and allowed slice information.

[0195] Based on the same inventive concept, a network slicing registration device is provided for use in a user terminal. The device includes:

[0196] The registration request message sending module is used to send a registration request message to the AMF. The registration request message is used to instruct the AMF to register the user terminal with the network slice on the AMF based on the user terminal's subscription slice information obtained from the UDM, the user terminal's configuration slice information and allowed slice information obtained from the PCF.

[0197] The registration response message receiving module is used to receive registration response messages sent by AMF. The registration response message is used to indicate whether the registration was successful or failed.

[0198] Based on the same inventive concept, a network slicing registration device is provided for PCF, the device comprising:

[0199] The second acquisition request receiving module is used to receive the second acquisition request; the second acquisition request is generated based on the registration request message;

[0200] The second network slice registration module is used to feed back the configuration slice information and allowed slice information of the user terminal to the AMF based on the second acquisition request, so that the AMF can register the network slice of the user terminal according to the configuration slice information and allowed slice information of the user terminal and the subscription slice information of the user terminal, and generate the network slice registration result.

[0201] Among them, the user terminal's subscription slice information is obtained by the AMF from the UDM based on the registration request message.

[0202] The division of the various modules in the above-described network slice registration device is merely for illustrative purposes. In other embodiments, the network slice registration device can be divided into different modules as needed to complete all or part of the functions of the above-described network slice registration device.

[0203] Specific limitations regarding the network slice registration device can be found in the limitations of the network slice registration method described above, and will not be repeated here. Each module in the aforementioned network slice registration device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device in hardware form, or stored in the memory of a computer device in software form, so that the processor can call and execute the corresponding operations of each module.

[0204] Figure 12 This is a schematic diagram of the structure of the access network device provided in an embodiment of the present invention. Figure 12 The access network device 1200 shown includes at least one processor 1201, a memory 1202, and at least one network interface 1204. The various components in the access network device 1200 are coupled together via a bus system 1205. It is understood that the bus system 1205 is used to implement communication between these components. In addition to a data bus, the bus system 1205 also includes a power bus, a control bus, and a status signal bus. However, for clarity, ... Figure 12 Various buses are designated as bus system 1205. Additionally, this embodiment of the invention includes a transceiver 1206, which may consist of multiple components, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium.

[0205] It is understood that the memory 1202 in the embodiments of the present invention can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The memory 1202 of the systems and methods described in the embodiments of the present invention is intended to include, but is not limited to, these and any other suitable types of memory.

[0206] In some implementations, memory 1202 stores elements such as executable modules or data structures, or subsets thereof, or extended sets thereof: operating system 1202a. Operating system 1202a includes various system programs, such as a framework layer, core library layer, and driver layer, used to implement various basic business functions and handle hardware-based tasks.

[0207] In this embodiment of the invention, by calling the program or instructions stored in the memory 1202, the receiver is configured to receive a registration request message; the registration request message is used to perform network slice registration; the processor 1201 is configured to obtain the user terminal's subscribed slice information from the unified data management network element UDM based on the registration request message, and obtain the user terminal's configuration slice information and allowed slice information from the policy control network element PCF; and perform network slice registration on the user terminal according to the subscribed slice information, configuration slice information, and allowed slice information, and generate a network slice registration result.

[0208] The methods disclosed in the above embodiments of the present invention, in part or in all of them, can also be applied to processor 1201, implemented by processor 1201, or implemented by processor 1201 in conjunction with other components (e.g., transceivers). Processor 1201 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above methods can be completed by the integrated logic circuit of the hardware in processor 1201 or by instructions in the form of software. The processor 1201 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, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present invention. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of the present invention can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module can reside in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory 1202. The processor 1201 reads the information in memory 1202 and, in conjunction with its hardware, completes the steps of the above method.

[0209] It is understood that the embodiments described in these embodiments of the present invention can be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit can be implemented in one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions of this application, or combinations thereof.

[0210] For software implementation, the techniques of the embodiments of the present invention can be implemented through modules (e.g., procedures, functions, etc.) that perform the functions of the embodiments of the present invention. The software code can be stored in memory and executed by processor 1201. The memory can be implemented in processor 1201 or external to processor 1201.

[0211] In one embodiment, the transmitter is specifically configured to send a first acquisition request to the UDM based on a registration request message when the authentication and authorization of the user terminal is successful; the first acquisition request is used to instruct the UDM to provide the user terminal's subscription slice information; the receiver is specifically configured to receive the user terminal's subscription slice information sent by the UDM.

[0212] In one embodiment, the transmitter is further configured to send an authentication request message to the authentication server based on the registration request message; the authentication request message is used to instruct the authentication server to authenticate the user terminal.

[0213] The receiver is also used to receive authentication response messages sent by the authentication server; the authentication response message indicates whether the user terminal has successfully authenticated.

[0214] In one embodiment, the transmitter is further configured to send a second acquisition request to the PCF based on the registration request message; the second acquisition request is configured to instruct the PCF to provide the user terminal's configuration slice information and allowed slice information.

[0215] The receiver is also used to receive configuration slice information and allowed slice information of user terminals sent by the PCF.

[0216] In one embodiment, the transmitter is further configured to send a policy association request to the PCF based on the registration request message; the policy association request is used to establish a policy association between the PCF and the AMF;

[0217] The receiver is also used to receive policy-related response messages sent by the PCF.

[0218] In one embodiment, the processor is further configured to determine a target slice information set from the subscribed slice information, the configured slice information, and the allowed slice information; and to perform network slice registration for the user terminal based on each target slice information in the target slice information set, thereby generating a network slice registration result.

[0219] In one embodiment, the transmitter is further configured to send a first registration response message to the user terminal if the network slice registration result includes successfully registered target slice information; the first registration response message is used to indicate that the AMF has successfully registered the network slice for the user terminal.

[0220] In one embodiment, the transmitter is further configured to send a second registration response message to the user terminal if the network slice registration result does not include the target slice information that was successfully registered; the second registration response message is used to indicate that the AMF failed to register the network slice for the user terminal.

[0221] In one embodiment, the processor is further configured to obtain the successfully registered target slice information from the network slice registration result, use the successfully registered target slice information as the new allowed slice information, and update the allowed slice information in the PCF based on the new allowed slice information.

[0222] In one embodiment, the processor is further configured to acquire the intersection of slice information among the contracted slice information, configured slice information, and allowed slice information; determine the target slice information set from the candidate intersection according to the priority order of each candidate slice information in the slice information intersection and the preset number of slice information; the preset number of slice information is related to the processing capacity of the network.

[0223] Figure 13 This is a schematic diagram of the structure of another access network device provided in an embodiment of the present invention. Figure 13 The access network device 1300 shown includes at least one processor 1301, a memory 1302, and at least one network interface 1304. The various components in the access network device 1300 are coupled together via a bus system 1305. It is understood that the bus system 1305 is used to implement communication between these components. In addition to a data bus, the bus system 1305 also includes a power bus, a control bus, and a status signal bus. However, for clarity, ... Figure 13 Various buses are designated as bus system 1305. Additionally, this embodiment of the invention includes a transceiver 1306, which may consist of multiple components, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium.

[0224] It is understood that the memory 1302 in this embodiment of the invention can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The memory 1302 of the systems and methods described in the embodiments of the present invention is intended to include, but is not limited to, these and any other suitable types of memory.

[0225] In some implementations, memory 1302 stores elements such as executable modules or data structures, or subsets thereof, or extended sets thereof: operating system 1302a. Operating system 1302a includes various system programs, such as a framework layer, core library layer, driver layer, etc., used to implement various basic business functions and handle hardware-based tasks.

[0226] In this embodiment of the invention, by calling the program or instructions stored in the memory 1302, the receiver is configured to receive a second acquisition request; the second acquisition request is generated based on a registration request message; the processor is configured to feed back the configuration slice information and allowed slice information of the user terminal to the AMF based on the second acquisition request, so that the AMF can perform network slice registration for the user terminal according to the configuration slice information and allowed slice information of the user terminal and the subscription slice information of the user terminal, and generate a network slice registration result; wherein, the subscription slice information of the user terminal is obtained by the AMF from the UDM based on the registration request message.

[0227] The methods disclosed in the above embodiments of the present invention, in part or in all of them, can also be applied to, implemented by, or cooperating with other components (e.g., transceivers) in the processor 1301. The processor 1301 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above methods can be completed by integrated logic circuits in the hardware of the processor 1301 or by instructions in software form. The processor 1301 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, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present invention. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of the present invention can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software module can reside in a mature storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory 1302. Processor 1301 reads the information in memory 1302 and, in conjunction with its hardware, completes the steps of the above method.

[0228] It is understood that the embodiments described in these embodiments of the present invention can be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit can be implemented in one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions of this application, or combinations thereof.

[0229] For software implementation, the techniques of the embodiments of the present invention can be implemented through modules (e.g., procedures, functions, etc.) that perform the functions of the embodiments of the present invention. The software code can be stored in memory and executed by processor 1301. The memory can be implemented in processor 1301 or external to processor 1301.

[0230] In one embodiment, a communication device is provided, see [link to previous document]. Figure 14 . Figure 14 This is a schematic diagram of the structure of the terminal device provided in an embodiment of the present invention. Figure 14 The terminal device 1400 shown includes a memory 1402, at least one network interface 1404, and a user interface 1403. The various components in the terminal device 1400 are coupled together via a bus system 1405. It is understood that the bus system 1405 is used to implement communication between these components. In addition to a data bus, the bus system 1405 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in… Figure 14 Various buses are designated as bus system 1405. Additionally, this embodiment of the invention includes a transceiver 1406, which may consist of multiple components, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium.

[0231] The user interface 1403 may include a display, keyboard, or clicking device (e.g., mouse, trackball, touchpad, or touchscreen).

[0232] It is understood that the memory 1402 in the embodiments of the present invention can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The memory 1402 of the systems and methods described in this embodiment is intended to include, but is not limited to, these and any other suitable types of memory.

[0233] In some implementations, memory 1402 stores elements, executable modules or data structures, or subsets thereof, or extended sets thereof: operating system 1402a and application program 1402b.

[0234] The operating system 1402a includes various system programs, such as the framework layer, core library layer, and driver layer, used to implement various basic business functions and handle hardware-based tasks. The application program 1402b includes various applications, such as a media player and a browser, used to implement various application functions. The program implementing the method of this embodiment can be included in application program 1402b.

[0235] In this embodiment of the invention, by calling the program or instructions stored in memory 1402, specifically the program or instructions stored in application program 1402b, the transmitter is used to send a registration request message to the AMF; the registration request message is used to instruct the AMF to register the user terminal for network slices on the AMF based on the user terminal's subscription slice information obtained from UDM, the user terminal's configuration slice information and allowed slice information obtained from PCF; the receiver is used to receive the registration response message sent by the AMF, the registration response message is used to indicate whether the registration was successful or failed.

[0236] It is understood that the embodiments described in these embodiments of the present invention can be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit can be implemented in one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions of this application, or combinations thereof.

[0237] For software implementation, the technology of the embodiments of the present invention can be implemented through modules (such as procedures, functions, etc.) that execute the functions of the embodiments of the present invention.

[0238] This application also provides a computer-readable storage medium. One or more non-volatile computer-readable storage media containing computer-executable instructions, which, when executed by one or more processors, cause the processors to perform the steps of a network slice registration method.

[0239] This application also provides a computer program product containing instructions that, when run on a computer, cause the computer to execute a network slice registration method.

[0240] Any references to memory, storage, databases, or other media used in this application may include non-volatile and / or volatile memory. Non-volatile memory may include ROM (Read-Only Memory), PROM (Programmable Read-Only Memory), EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), or flash memory. Volatile memory may include RAM (Random Access Memory), which is used as external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms, such as SRAM (Static Random Access Memory), DRAM (Dynamic Random Access Memory), SDRAM (Synchronous Dynamic Random Access Memory), Double Data Rate DDR SDRAM (Double Data Rate Synchronous Dynamic Random Access Memory), ESDRAM (Enhanced Synchronous Dynamic Random Access Memory), SLDRAM (Sync Link Dynamic Random Access Memory), RDRAM (Rambus Dynamic Random Access Memory), and DRDRAM (Direct Rambus Dynamic Random Access Memory).

[0241] The above embodiments merely illustrate several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. A network slice registration method, characterized in that, Applied to the Access and Mobility Management (AMF) network element, the method includes: Receive a registration request message; the registration request message is used to register a network slice. Based on the registration request message, the user terminal's subscription slice information is obtained from the Unified Data Management Network Element (UDM), and the user terminal's configuration slice information and allowed slice information are obtained from the Policy Control Network Element (PCF). Based on the signed slice information, the configured slice information, and the allowed slice information, the user terminal is registered for network slices, and a network slice registration result is generated.

2. The method according to claim 1, characterized in that, The step of obtaining the user terminal's subscription slice information from the Unified Data Management Network Element (UDM) based on the registration request message includes: If the user terminal is successfully authenticated, a first acquisition request is sent to the UDM based on the registration request message; the first acquisition request is used to instruct the UDM to provide the user terminal's subscription slice information. Receive the subscription slice information of the user terminal sent by the UDM.

3. The method according to claim 2, characterized in that, The method further includes: Based on the registration request message, an authentication request message is sent to the authentication server; the authentication request message is used to instruct the authentication server to authenticate the user terminal. Receive the authentication response message sent by the authentication server; the authentication response message indicates whether the user terminal has successfully authenticated.

4. The method according to any one of claims 1-3, characterized in that, The step of obtaining the configuration slice information and allowed slice information of the user terminal from the policy control network element (PCF) includes: A second acquisition request is sent to the PCF based on the registration request message; the second acquisition request is used to instruct the PCF to provide feedback on the configuration slice information and allowed slice information of the user terminal; Receive the configuration slice information and allowed slice information of the user terminal sent by the PCF.

5. The method according to claim 4, characterized in that, The method further includes: Based on the registration request message, a policy association request is sent to the PCF; the policy association request is used to establish a policy association between the PCF and the AMF. Receive the policy association response message sent by the PCF.

6. The method according to any one of claims 1-3, characterized in that, The step of registering the user terminal for network slices based on the signed slice information, the configured slice information, and the allowed slice information, and generating a network slice registration result, includes: The target slice information set is determined from the contracted slice information, the configured slice information, and the allowed slice information; Based on the target slice information in the target slice information set, the user terminal performs network slice registration and generates network slice registration results.

7. The method according to claim 6, characterized in that, The method further includes: If the network slice registration result includes the target slice information that has been successfully registered, then a first registration response message is sent to the user terminal; the first registration response message is used to indicate that the AMF has successfully registered the network slice for the user terminal.

8. The method according to claim 6, characterized in that, The method further includes: If the network slice registration result does not include the successfully registered target slice information, a second registration response message is sent to the user terminal; the second registration response message is used to indicate that the AMF failed to register the network slice for the user terminal.

9. The method according to claim 6, characterized in that, The method further includes: Obtain the successfully registered target slice information from the network slice registration results, and use the successfully registered target slice information as the new allowed slice information; The allowed slice information in the PCF is updated based on the new allowed slice information.

10. The method according to claim 6, characterized in that, The step of determining the target slice information set from the contracted slice information, the configured slice information, and the allowed slice information includes: Obtain the intersection of the slice information among the signed slice information, the configured slice information, and the allowed slice information; The target slice information set is determined from the candidate slice information intersection according to the priority order of each candidate slice information and the preset number of slice information; the preset number of slice information is related to the processing capacity of the network.

11. The method according to any one of claims 1-3, characterized in that, The registration request message does not include the user terminal's configuration slice information and allowed slice information.

12. A network slice registration method, characterized in that, Applied to a user terminal, the method includes: Send a registration request message to the AMF; the registration request message is used to instruct the AMF to register the user terminal with the AMF for network slices based on the user terminal's subscription slice information obtained from the UDM, the user terminal's configuration slice information and allowed slice information obtained from the PCF; Receive a registration response message sent by AMF, which indicates whether the registration was successful or failed.

13. A network slice registration method, characterized in that, Applied to PCF, the method includes: Receive a second acquisition request; the second acquisition request is generated based on the registration request message; Based on the second acquisition request, the AMF sends the configuration slice information and allowed slice information of the user terminal back to the AMF, so that the AMF can register the user terminal for network slices according to the configuration slice information and allowed slice information of the user terminal and the subscription slice information of the user terminal, and generate network slice registration results. The user terminal's subscription slice information is obtained by the AMF from the UDM based on the registration request message.

14. A network slicing registration device, characterized in that, The device is applied to the Access and Mobility Management (AMF) network element and includes: The registration request message receiving module is used to receive registration request messages; the registration request messages are used for network slice registration. The slice information acquisition module is used to obtain the user terminal's subscription slice information from the unified data management network element UDM based on the registration request message, and to obtain the user terminal's configuration slice information and allowed slice information from the policy control network element PCF. The first network slice registration module is used to register the user terminal with network slices based on the signed slice information, the configured slice information and the allowed slice information, and generate network slice registration results.

15. A network slicing registration device, characterized in that, The device, applied to a user terminal, includes: The registration request message sending module is used to send a registration request message to the AMF; the registration request message is used to instruct the AMF to register the user terminal with the AMF for network slices based on the user terminal's subscription slice information obtained from the UDM, the user terminal's configuration slice information and allowed slice information obtained from the PCF. The registration response message receiving module is used to receive registration response messages sent by AMF, which are used to indicate whether the registration was successful or failed.

16. A network slicing registration device, characterized in that, Applied to PCF, the device includes: The second acquisition request receiving module is used to receive a second acquisition request; the second acquisition request is generated based on the registration request message; The second network slice registration module is used to feed back the configuration slice information and allowed slice information of the user terminal to the AMF based on the second acquisition request, so that the AMF can register the network slice of the user terminal according to the configuration slice information and allowed slice information of the user terminal and the subscription slice information of the user terminal, and generate a network slice registration result. The user terminal's subscription slice information is obtained by the AMF from the UDM based on the registration request message.

17. A communication device, comprising a transceiver, a memory, and a processor, wherein the memory stores a computer program, characterized in that, The processor executes the computer program to control the transceiver to receive a registration request message; the registration request message is used to perform network slice registration. The processor executes the computer program for performing the steps of the network slice registration method as described in any one of claims 1 to 11.

18. A communication device, comprising a transceiver, a memory, and a processor, wherein the memory stores a computer program, characterized in that, The processor executes the computer program to control the transceiver to send a registration request message to the AMF and receive a registration response message sent by the AMF. The registration request message is used to instruct the AMF to register the user terminal with the AMF for network slices based on the user terminal's subscription slice information obtained from the UDM, the user terminal's configuration slice information and allowed slice information obtained from the PCF; the registration response message is used to indicate whether the registration was successful or failed.

19. A communication device, comprising a transceiver, a memory, and a processor, wherein the memory stores a computer program, characterized in that, The processor executes the computer program to control the transceiver to receive a second acquisition request; the second acquisition request is generated based on a registration request message; The processor executes the computer program to feed back the configuration slice information and allowed slice information of the user terminal to the AMF based on the second acquisition request, so that the AMF can perform network slice registration for the user terminal according to the configuration slice information and allowed slice information of the user terminal and the subscription slice information of the user terminal, and generate network slice registration result. The user terminal's subscription slice information is obtained by the AMF from the UDM based on the registration request message.

20. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the network slice registration method as described in any one of claims 1 to 13.

21. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the network slice registration method according to any one of claims 1 to 13.

Images