Network slice registration method, device, system, amf unit and ue

Abstract

This application relates to a network slice registration method, apparatus, system, AMF unit, and UE. The method includes: receiving a slice registration request initiated by a user terminal (UE), and determining the target network slice corresponding to the UE based on the slice registration request and the network slice information corresponding to the UE stored in the AMF unit. This method can improve the utilization rate of network slices.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a network slicing registration method, apparatus, system, AMF unit, and UE. Background Technology

[0002] With the rapid development of internet technology, network slicing technology has emerged. Slicing technology can divide a physical network into multiple virtual networks, resulting in multiple isolated and independent network slices. Furthermore, a user equipment (UE) can select one of these network slices to register and use for data communication.

[0003] Currently, network slicing technology requires UE development support, resulting in relatively low utilization of network slices. Summary of the Invention

[0004] Therefore, it is necessary to provide a network slice registration method, apparatus, system, AMF unit, and UE that can improve the utilization rate of network slices, addressing the aforementioned technical problems.

[0005] In a first aspect, this application provides a network slicing registration method applied to an Access and Mobility Management Function (AMF) unit, the method comprising:

[0006] Receive slice registration requests initiated by user terminal (UE);

[0007] Based on the slice registration request and the network slice information corresponding to the UE stored in the AMF unit, the target network slice corresponding to the UE is determined.

[0008] In one embodiment, determining the target network slice corresponding to the UE based on the slice registration request and the network slice information corresponding to the UE stored in the AMF unit includes:

[0009] In response to the slice registration request, obtain the contracted slice information from the Unified Data Management (UDM);

[0010] Based on the contracted slice information and the network slice information, the target network slice is determined.

[0011] In one embodiment, the subscribed slice information includes subscribing to NSSAI; the network slice information includes configuring NSSAI and allowing NSSAI; determining the target network slice based on the subscribed slice information and the network slice information includes:

[0012] The intersection of the signed NSSAI, the configured NSSAI, and the allowed NSSAI is determined as the target network slice.

[0013] In one embodiment, the response to the slice registration request includes obtaining subscribed slice information from the Unified Data Management (UDM), including:

[0014] Based on the slice registration request, authenticate the UE.

[0015] If authentication is successful, obtain the contracted slice information from the UDM.

[0016] In one embodiment, the authentication of the UE based on the slice registration request includes:

[0017] According to the slice registration request, an authentication request is sent to the authentication server. The authentication request includes the first user authentication information corresponding to the UE. The authentication request is used to instruct the authentication server to obtain the second user authentication information from the UDM. After successfully authenticating the UE based on the first user authentication information and the second user authentication information, the authentication server sends back a successful authentication response.

[0018] Receive the authentication result sent by the authentication server based on the successful authentication response.

[0019] In one embodiment, the authentication result includes a UDM identifier. If the authentication is successful, obtaining the contracted slice information from the UDM includes:

[0020] If authentication is successful, a subscription slice information request is sent to the UDM corresponding to the UDM identifier; the subscription slice information request includes the user identifier.

[0021] Receive the subscription slice information corresponding to the user identifier sent by the UDM.

[0022] In one embodiment, the method further includes:

[0023] Send a slice registration response to the UE; the slice registration response indicates that the network slice registration was successful.

[0024] In one embodiment, receiving the slice registration request initiated by the user terminal UE includes:

[0025] Receive the slice registration request forwarded by the UE through the base station BS;

[0026] The slice registration response is sent to the UE, including:

[0027] The BS sends the slice registration response to the UE.

[0028] In one embodiment, the slice registration request does not carry information related to the network slice.

[0029] Secondly, this application also provides a network slicing registration method applied to a UE, the method comprising:

[0030] Send a slice registration request; the slice registration request is used to instruct the AMF unit to determine the target network slice corresponding to the UE based on the slice registration request and the network slice information corresponding to the UE stored in the AMF unit;

[0031] Receive the slice registration response; this response indicates that the network slice registration was successful.

[0032] In one embodiment, the slice registration request does not carry information related to the network slice.

[0033] Thirdly, this application also provides a network slice registration device. The device includes:

[0034] The receiving module is used to receive slice registration requests initiated by the user terminal (UE).

[0035] The determination module is used to determine the target network slice corresponding to the UE based on the slice registration request and the network slice information corresponding to the UE stored in the AMF unit.

[0036] Fourthly, this application also provides a network slice registration apparatus, the apparatus comprising:

[0037] The sending module is used to send a slice registration request; the slice registration request is used to instruct the AMF unit to determine the target network slice corresponding to the UE based on the slice registration request and the network slice information corresponding to the UE stored in the AMF unit.

[0038] The receiving module is used to receive the slice registration response; the slice registration response indicates that the network slice registration was successful.

[0039] Fifthly, this application also provides a network slice registration system, which includes a UE, a BS, an AMF unit, an authentication server, and a UDM;

[0040] This AMF unit is used to execute the network slice registration method described above;

[0041] This UE is used to perform the network slice registration method described above.

[0042] Sixthly, this application also provides an AMF unit, which includes a transceiver, a processor, and a memory, the memory storing a computer program;

[0043] This transceiver is used to receive slice registration requests initiated by user terminal (UE).

[0044] The processor executes the computer program to determine the target network slice corresponding to the UE based on the slice registration request and the network slice information corresponding to the UE stored in the AMF unit.

[0045] Seventhly, this application also provides a UE, which includes a transceiver;

[0046] The transceiver is used to send a slice registration request; the slice registration request is used to instruct the AMF unit to determine the target network slice corresponding to the UE based on the slice registration request and the network slice information corresponding to the UE stored in the AMF unit.

[0047] The transceiver is also used to receive slice registration responses, which indicate that the network slice registration was successful.

[0048] Eighthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of any of the above methods.

[0049] Ninthly, this application also provides a computer program product, which includes a computer program that, when executed by a processor, implements the steps of any of the above methods.

[0050] The aforementioned network slice registration method, apparatus, system, AMF unit, and UE receive a slice registration request initiated by a user terminal (UE) and determine the target network slice corresponding to the UE based on the slice registration request and the network slice information corresponding to the UE stored in the AMF unit. Currently, because traditional slicing technology requires UE development support, the UE needs to store its corresponding network slice information in advance. Then, the UE initiates a slice registration request carrying relevant information about the network slice to the AMF unit based on its stored network slice information, and determines the target network slice based on the content returned by the AMF unit. However, in the method provided in this embodiment, since the network slice information corresponding to the UE is stored in the AMF unit, the slice registration request initiated by the UE does not need to carry the relevant information about the network slice. Furthermore, the AMF unit can determine the target network slice corresponding to the UE based on the slice registration request initiated by the UE and the stored network slice information. Therefore, the UE does not need development support for the slicing technology to achieve network slice registration, avoiding the UE's dependence on the slicing technology, improving the flexibility of network slice usage, and thus increasing the utilization rate of network slices. Attached Figure Description

[0051] Figure 1 This is a diagram illustrating the application environment of the network slice registration method in this application embodiment;

[0052] Figure 2 This is a flowchart illustrating the network slice registration method in an embodiment of this application;

[0053] Figure 3 This is a schematic diagram of a process for determining a target network slice in an embodiment of this application;

[0054] Figure 4 This is a schematic diagram of a process for obtaining contracted slice information in an embodiment of this application;

[0055] Figure 5 This is a schematic diagram of an authentication process in an embodiment of this application;

[0056] Figure 6 This is a schematic diagram of another process for obtaining contracted slice information in an embodiment of this application;

[0057] Figure 7 This is a flowchart illustrating the network slice registration method in an embodiment of this application;

[0058] Figure 8 This is a schematic diagram of the signaling interaction of a network slice registration method in an embodiment of this application;

[0059] Figure 9 This is a structural block diagram of a network slicing registration device according to an embodiment of this application;

[0060] Figure 10 This is a structural block diagram of yet another network slicing registration device in this application embodiment;

[0061] Figure 11 This is a schematic diagram of the structure of an AMF unit in an embodiment of this application;

[0062] Figure 12 This is a schematic diagram of the structure of a UE according to an embodiment of this application. Detailed Implementation

[0063] 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.

[0064] Currently, when a UE registers a network slice, it needs to support functions such as initiating a network slice registration request and selecting a network slice. Therefore, slicing technology requires UE development support. In other words, if a UE does not support slicing technology, it cannot register a network slice and therefore cannot use the corresponding network slice. This results in low network slice utilization. Therefore, it is necessary to provide a network slice registration method that can improve network slice utilization to address the above technical problems. This method will be introduced below.

[0065] Figure 1 This is a diagram illustrating the application environment of the network slice registration method in this application embodiment, such as... Figure 1 As shown, the scenario includes a user terminal 101, a base station 102, an Access and Mobility Management function (AMF) unit 103, an authentication server 104, and a Unified Data Management (UDM) unit 105.

[0066] The user terminal 101 may be, but is not limited to, various personal computers, laptops, smartphones, tablets and portable wearable devices, and the portable wearable devices may be smartwatches, smart bracelets, head-mounted devices, etc.

[0067] Base station 102 can be a base station (BTS) in Global System for Mobile communication (GSM) or Code Division Multiple Access (CDMA), a base station (NodeB, NB) in Wideband Code Division Multiple Access (WCDMA), an evolved Node B (eNB or eNodeB) in LTE, a relay station or access point, or a base station in a 5G network, etc.

[0068] AMF unit 103, authentication server 104 and unified data management 105 can be implemented using independent servers or server clusters composed of multiple servers.

[0069] It is understood that the above only illustrates one possible application environment, and the embodiments of this application are not limited thereto.

[0070] Figure 2 This is a flowchart illustrating the network slice registration method in an embodiment of this application. The method is applied to... Figure 1 In the AMF unit shown, in one embodiment, as Figure 2 As shown, it includes the following steps:

[0071] S201, Receive slice registration request initiated by user terminal UE.

[0072] In this embodiment, when the UE needs to register a network slice, it will initiate a slice registration request, and then the Access and Mobility Management function (AMF) will receive the slice registration request initiated by the UE.

[0073] Optionally, the slice registration request may include a user identifier, allowing the AMF unit to determine which user initiated the network slice registration. In other words, the user identifier indicates the user operating the UE. Alternatively, the slice registration request may include a terminal identifier, allowing the AMF unit to determine which terminal initiated the network slice registration. The user identifier can be at least one of numbers, letters, symbols, and characters. The terminal identifier can be the terminal's number, model, name, etc.

[0074] Optionally, the UE can store the mapping between user identifiers and AMF units, and then directly send a slice registration request to the AMF unit when network slice registration is required. The UE can also transmit or forward slice registration requests to the AMF unit through other devices.

[0075] In one embodiment, optionally, the slice registration request does not carry information related to the network slice.

[0076] Currently, in traditional technologies, when a UE initiates a slice registration request, it includes network slice information in the request. In other words, in the traditional network slice registration process, the UE needs to store the network slice information in advance and possess the ability to identify and process this information, thus requiring corresponding development support from the UE. However, in this embodiment, since the slice registration request does not carry network slice information, the UE does not need to store the network slice information in advance, nor does it need to possess the ability to identify and process it. Therefore, in the network slice registration method provided in this embodiment, the UE does not require corresponding development support.

[0077] Among them, the network slice related information includes, but is not limited to, Allowed Network Slice Selection Assistance Information, Requested Network Slice Selection Assistance Information, or Configured Network Slice Selection Assistance Information.

[0078] S202, Based on the slice registration request and the network slice information corresponding to the UE stored in the AMF unit, determine the target network slice corresponding to the UE.

[0079] In this embodiment, the network slice information can be pre-stored in the AMF unit, corresponding to the UE. For example, the network slice information may include configuring NSSAI, allowing NSSAI, and subscribing to NSSAI. The slice registration request includes a user identifier. The AMF unit stores network slice information corresponding to different user identifiers. Therefore, when the AMF unit receives a slice registration request, it can determine the network slice information corresponding to that user identifier, i.e., the network slice information corresponding to the UE, based on the user identifier in the slice registration request.

[0080] Furthermore, the AMF unit can determine the target network slice for the UE based on the slice registration request and the network slice information corresponding to the UE stored in the AMF unit. For example, after receiving the slice registration request, the AMF unit can determine the target network slice by registering based on the largest intersection of configured NSSAI, allowed NSSAI, and subscribed NSSAI, according to the network slice information corresponding to the UE stored in the AMF unit. In this way, the UE can then use the AMF unit to access the target network slice.

[0081] The network slice registration method provided in this embodiment receives a slice registration request initiated by a user terminal (UE) and determines the target network slice corresponding to the UE based on the slice registration request and the network slice information corresponding to the UE stored in the AMF unit. Currently, because traditional slicing technology requires UE development support, the UE needs to store its corresponding network slice information in advance. Then, the UE initiates a slice registration request carrying relevant information about the network slice to the AMF unit based on its stored network slice information, and determines the target network slice based on the content returned by the AMF unit. However, in the method provided in this embodiment, since the network slice information corresponding to the UE is stored in the AMF unit, the slice registration request initiated by the UE does not need to carry the relevant information about the network slice. Furthermore, the AMF unit can determine the target network slice corresponding to the UE based on the slice registration request initiated by the UE and the stored network slice information. Therefore, the UE does not need development support for the slicing technology to achieve network slice registration, avoiding the UE's dependence on the slicing technology, improving the flexibility of network slice usage, and thus increasing the utilization rate of network slices.

[0082] Figure 3 This is a schematic diagram of a process for determining a target network slice in an embodiment of this application. (Refer to...) Figure 3 This embodiment relates to an optional implementation of how to determine the target network slice corresponding to the UE. Based on the above embodiment, S202, which determines the target network slice corresponding to the UE according to the slice registration request and the network slice information corresponding to the UE stored in the AMF unit, includes the following steps:

[0083] S301, in response to the slice registration request, obtains the signed slice information from the UDM.

[0084] In this embodiment, the subscribed slice information reflects the network slices that a user can use, and may be content pre-stored in the UDM. For example, the UDM stores subscribed slice information corresponding to different user identifiers. Assuming user 1 purchases service 1 and service 2, user 1 can use network slice 1 corresponding to service 1 and network slice 2 corresponding to service 2. Thus, the UDM stores subscribed slice information 1 corresponding to user identifier 1 of user 1, which indicates network slice 1 and network slice 2. In some implementations, the subscribed slice information may also include other information such as network slice utilization rate and congestion rate.

[0085] Furthermore, after receiving the slice registration request initiated by the UE, the AMF unit will respond to the slice registration request and obtain the subscribed slice information from the unified data management.

[0086] For example, the slice registration request includes a user identifier, and the AMF unit and UDM are communicatively connected. Thus, the AMF unit can respond to a slice registration request initiated by the UE by sending a subscription slice information request, including the user identifier, to the UDM. After receiving the subscription slice information request, the UDM finds the subscription slice information corresponding to the user identifier based on the user identifier and returns the subscription slice information corresponding to the user identifier to the AMF unit.

[0087] S302, determine the target network slice based on the contracted slice information and network slice information.

[0088] In this embodiment, after obtaining the contracted slice information returned by UDM, the AMF unit can determine the target network slice based on the contracted slice information and the network slice information.

[0089] Optionally, the AMF unit can determine the intersection of the contracted slice information and the network slice information based on the contracted slice information and the network slice information, and select the network slice with the highest priority from the intersection as the target network slice. Of course, the AMF unit can also determine the target network slice based on the contracted slice information and the network slice information in other ways, and this embodiment is not limited to this.

[0090] In this embodiment, the AMF unit can respond to a slice registration request by obtaining subscribed slice information from the Unified Data Management (UDM) and determining the target network slice based on the subscribed slice information and network slice information. Therefore, the dependence of the existing network slice registration process on the UE is reduced, and the UE's network slice registration process can be implemented without corresponding development support for the UE, thereby improving the utilization rate of network slices.

[0091] Optionally, in one embodiment, the subscribed slice information includes subscribing to NSSAI; the network slice information includes configuring NSSAI and allowing NSSAI; in step S302 above, determining the target network slice based on the subscribed slice information and the network slice information can be achieved in the following way:

[0092] The intersection of signing up for NSSAI, configuring NSSAI, and allowing NSSAI is determined as the target network slice.

[0093] In this embodiment, the subscribed slice information includes subscribing to NSSAI; the network slice information includes configuring NSSAI and allowing NSSAI.

[0094] The subscribed NSSAI indicates the network slice identifiers that a user can use. For example, if a user has purchased service 1, the subscribed NSSAI includes network slice identifier 1 corresponding to service 1. While both configured NSSAI and allowed NSSAI are pre-stored in the AMF unit, configured NSSAI indicates the network slices supported by default and is not equivalent to subscribed NSSAI. For example, if user 1's region supports service 2, the configured NSSAI includes network slice identifier 2 corresponding to service 2. Generally, configured NSSAI remains static. Allowed NSSAI indicates the network slices that a user can use. Allowed NSSAI is continuously updated based on the user's service needs, network slice status, and other factors; that is, it is dynamically updated with each slice registration request initiated by the UE.

[0095] NSSAI includes S-NSSAI. In other words, S-NSSAI is used to identify network slices and can be understood as network slice identifiers; therefore, NSSAI is a set of network slice identifiers. For example, configuring NSSAI includes S-NSSAI1, S-NSSAI2, and S-NSSAI3; signing up NSSAI includes S-NSSAI1 and S-NSSAI2; and allowing NSSAI includes S-NSSAI1, S-NSSAI4, and S-NSSAI5. Here, S-NSSAI1, S-NSSAI2, S-NSSAI3, S-NSSAI4, and S-NSSAI5 correspond to network slice 1, network slice 2, network slice 3, and network slice 5, respectively.

[0096] Furthermore, the AMF unit can determine the target network slice by identifying the intersection of subscribed NSSAI, configured NSSAI, and allowed NSSAI. Continuing the example above, if the intersection of subscribed NSSAI, configured NSSAI, and allowed NSSAI is S-NSSAI1, then the AMF unit will use S-NSSAI1 as the target network slice. Thus, after slice registration is completed, the UE can access network slice 1 using the AMF unit.

[0097] Optionally, after the AMF unit determines the target network slice, it can write the user identifier in the slice registration request into the slice information corresponding to the target network slice.

[0098] Optionally, the AMF unit updates the target network slice to its stored allowed NSSAIs. Continuing the example above, if the UE has not yet initiated this slice registration request, and the AMF unit stores allowed NSSAIs including S-NSSAI1, S-NSSAI4, and S-NSSAI5, then if the target network slice is determined to be NSSAI1, the AMF unit updates the stored allowed NSSAIs to S-NSSAI1.

[0099] It should be noted that since the intersection between signing NSSAI, configuring NSSAI, and allowing NSSAI may include more than one S-NSSAI, the number of target slice networks can be N, where N is an integer greater than or equal to 1. N is related to the slice processing limit of the AMF unit, for example, 8.

[0100] In this embodiment, the intersection of signing up for NSSAI, configuring NSSAI, and allowing NSSAI is determined as the target network slice. In this way, the UE can subsequently access the target network slice through the AMF unit to achieve network slice registration. Moreover, this registration process reduces the dependence on the UE, thereby improving the utilization rate of the network slice.

[0101] Figure 4 This is a schematic diagram of a process for obtaining contracted slice information in an embodiment of this application. (Refer to...) Figure 4 This embodiment relates to an optional implementation of how to obtain contracted slice information from the UDM. Based on the above embodiment, step S301, in response to a slice registration request, obtains contracted slice information from the UDM, including the following steps:

[0102] S401, Authenticate the UE based on the slice registration request.

[0103] S402: If authentication is successful, obtain the contracted slice information from UDM.

[0104] In this embodiment, in order to improve the security of the registration process, the AMF unit can verify the identity of the UE. Therefore, after receiving the slice registration request, the AMF unit will first authenticate the UE according to the slice registration request to determine whether the identity of the party initiating the slice registration request is legitimate.

[0105] Optionally, the slice registration request may include authentication information. The AMF unit can determine whether authentication is successful based on the authentication information in the slice registration request. For example, the AMF unit determines whether the authentication information includes preset content; if it does, authentication is successful; otherwise, it fails.

[0106] Alternatively, the authentication information carried in the slice registration request can be encrypted using a preset key. After receiving the slice registration request, the AMF unit first decrypts the authentication information using the preset key to obtain the authentication information, and then determines whether the authentication is successful.

[0107] This embodiment does not limit the specific authentication process, as long as it can authenticate the UE based on the slice registration request. Furthermore, the AMF unit will only obtain the subscribed slice information from the UDM if the authentication is successful.

[0108] This embodiment improves the security of the network slice registration process by authenticating the UE based on the slice registration request and obtaining the subscribed slice information from the UDM after successful authentication.

[0109] Figure 5 This is a schematic diagram of an authentication process in an embodiment of this application, referring to... Figure 5 This embodiment relates to an optional implementation of how to authenticate the UE. Based on the above embodiment, step S401, which authenticates the UE according to the slice registration request, includes the following steps:

[0110] S501, based on the slice registration request, send an authentication request to the authentication server; the authentication request includes the first user authentication information corresponding to the UE, and the authentication request is used to instruct the authentication server to obtain the second user authentication information from the UDM, and after successfully authenticating the UE based on the first user authentication information and the second user authentication information, send back an authentication success response.

[0111] S502, Receive the authentication result sent by the authentication server based on the successful authentication response.

[0112] In this embodiment, upon receiving a slice registration request, the AMF unit sends an authentication request, including first user authentication information, to the authentication server. After receiving this authentication request, the authentication server can then obtain second user authentication information from the UDM. Further, based on the first and second user authentication information, the authentication server authenticates the UE and, upon successful authentication, sends a successful authentication response back to the AMF unit.

[0113] For example, the slice registration request includes a user identifier and first user authentication information. Upon receiving the slice registration request, the AMF unit sends an authentication request to the authentication server, which also includes the user identifier and first user authentication information. After receiving the authentication request, the authentication server first sends an authentication information request to the UDM based on the user identifier in the authentication request. Upon receiving the authentication information request, the UDM returns the second user authentication information corresponding to the user identifier to the authentication server.

[0114] In this way, the authentication server can authenticate the UE based on the first user authentication information and the second user authentication information. For example, the authentication server compares whether the first user authentication information and the second user authentication information are the same. If they are the same, the authentication is successful; otherwise, the authentication is unsuccessful.

[0115] Furthermore, if the authentication server successfully authenticates the user, it will send an authentication success response to the AMF unit, which will then send the authentication result based on the successful authentication response.

[0116] In some embodiments, after the authentication server authenticates the UE based on the first user authentication information and the second user authentication information, it will return a corresponding response to the AMF unit regardless of whether the authentication is successful or not.

[0117] In this embodiment, an authentication request is sent to the authentication server based on the slice registration request, and the authentication server sends an authentication result based on the successful authentication response. Since the authentication request includes the first user authentication information corresponding to the UE, and instructs the authentication server to obtain the second user authentication information from the UDM, and after successfully authenticating the UE based on the first and second user authentication information, a successful authentication response is sent back. Therefore, using the authentication server to complete the authentication process can reduce the processing load on the AMF unit and further improve the security of network slice registration.

[0118] Figure 6 This is a schematic diagram of another process for obtaining contracted slice information in an embodiment of this application, referred to... Figure 6 This embodiment relates to an optional implementation of how to obtain contracted slice information from the UDM. Based on the above embodiment, the authentication result includes the UDM identifier. In step S402, if the authentication is successful, obtaining the contracted slice information from the UDM includes the following steps:

[0119] S601, if authentication is successful, sends a subscription slice information request to the UDM corresponding to the UDM identifier; the subscription slice information request includes the user identifier.

[0120] S602 receives the subscription slice information corresponding to the user identifier sent by UDM.

[0121] In this embodiment, taking the steps S501 and S502 as an example, after the AMF unit receives the authentication success response from the authentication server, it can determine that the authentication has been successful. The authentication success response includes a UDM identifier, which helps the AMF unit locate the UDM, and may include, but is not limited to, the IP address and port number of the UDM.

[0122] Furthermore, once authentication is successful, the AMF unit can locate the UDM based on the UDM identifier and send a subscription slice information request to the UDM corresponding to the UDM identifier. This subscription slice information request includes the user identifier. Upon receiving the subscription slice information request from the AMF unit, the UDM can locate the subscription slice information corresponding to the user identifier based on the user identifier in the request and return the corresponding subscription slice information to the UDM.

[0123] Of course, in some embodiments, the AMF unit can also pre-store the UDM identifier, so that when the authentication is successful, it can directly send a request for subscription slice information including the user identifier to the UDM corresponding to the UDM identifier.

[0124] In this embodiment, upon successful authentication, a request for subscribed slice information is sent to the UDM corresponding to the UDM identifier, and the subscribed slice information corresponding to the user identifier is received from the UDM. Therefore, the security of network slice registration and the reliability of subscribed slice information are improved.

[0125] Optionally, in one embodiment, the network slice registration method described above further includes the following steps:

[0126] Send a slice registration response to the UE; the slice registration response indicates that the network slice registration was successful.

[0127] In this embodiment, the AMF unit sends a slice registration response to the UE after completing network slice registration. This slice registration response indicates that the network slice registration was successful.

[0128] Optionally, the AMF unit can send a slice registration response to the UE after determining the target network slice, or it can write the user identifier into the information corresponding to the network slice before sending the slice registration response to the UE.

[0129] Of course, in some embodiments, if network slice registration fails, the AMF unit will also return a slice registration response indicating that network slice registration has failed.

[0130] It should be noted that the AMF unit does not carry network slice information when sending the slice registration response to the UE. As a result, the UE does not need to store, identify, or process network slice information after receiving the slice registration response, thereby reducing the UE's dependence on the network slice registration process.

[0131] Optionally, in one embodiment, the above-described S201, receiving the slice registration request initiated by the user terminal UE, can be implemented in the following way:

[0132] Receive the slice registration request forwarded by the UE through the base station BS.

[0133] Similarly, the above-mentioned "sending slice registration response to UE" can be achieved in the following way:

[0134] The BS sends a slice registration response to the UE.

[0135] In this embodiment, the AMF unit and the UE do not communicate directly, but rather indirectly through the base station (BS). That is, when the UE needs to perform network slicing, it sends a slice registration request to the BS, and after receiving the slice registration request, the BS forwards the slice registration request to the AMF unit.

[0136] Furthermore, when the AMF unit needs to send a slice registration response to the UE, the AMF unit first sends the slice registration response to the BS, and after receiving the slice registration response, the BS forwards the slice registration response to the UE.

[0137] The relationship between the UE and the BS may be many-to-many. Optionally, the UE can determine the BS to use based on the signal strength with different candidate BSs. For example, if the UE simultaneously searches for BS1 and BS2, and the signal strength with BS1 is the strongest, then the UE sends a slice registration request to BS1. The UE can also pre-configure the mapping between user identifiers and base stations. For example, if user identifier 1 corresponds to BS1, when user 1 initiates a slice registration request through the UE, the UE sends a slice registration request to BS1.

[0138] The relationship between the BS and AMF units may be one-to-many. Optionally, when the UE sends a slice registration request to the BS, it may carry an indication such as 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier) ​​or GUAM (Globally Unique AMF Unit Identifier) ​​so that the BS can determine the AMF unit corresponding to the indication in the slice registration request and forward the slice registration request to that AMF unit.

[0139] In some embodiments, the BS can also pre-configure AMF units, that is, the BS stores the correspondence between itself or the user identifier and the AMF unit. Then, after receiving a slice registration request, the BS forwards the slice registration request to the corresponding AMF unit according to the pre-configured correspondence. The slice registration response is similar and will not be described in detail here.

[0140] The above mainly introduced the process of the network slice registration method being executed in the AMF unit. Next, we will introduce the process of the network slice registration method being executed in the UE. Figure 7 This is a flowchart illustrating the network slice registration method in an embodiment of this application. The method is applied to... Figure 1 In one embodiment of the user terminal shown, such as Figure 7 As shown, it includes the following steps:

[0141] S701, Send a slice registration request; the slice registration request is used to instruct the AMF unit to determine the target network slice corresponding to the UE based on the slice registration request and the network slice information corresponding to the UE stored in the AMF unit.

[0142] S702, Receive slice registration response; the slice registration response is used to indicate that the network slice registration was successful.

[0143] In this embodiment, the UE initiates a slice registration request when network slice registration is required. Optionally, the UE can store the correspondence between user identifiers and AMF units, and then directly send the slice registration request to the AMF unit when network slice registration is required. The UE can also pass through or forward the slice registration request to the AMF unit through devices such as the BS.

[0144] Optionally, the slice registration request may include a user identifier, allowing the AMF unit to determine which user initiated the network slice registration. In other words, the user identifier indicates the user operating the UE. Alternatively, the slice registration request may include a terminal identifier, allowing the AMF unit to determine which terminal initiated the network slice registration. The user identifier can be at least one of numbers, letters, symbols, and characters. The terminal identifier can be the terminal's number, model, name, etc.

[0145] Optionally, in one embodiment, the slice registration request does not carry information related to the network slice. This information includes, but is not limited to, allowing NSSAI, requesting NSSAI, or configuring NSSAI. Thus, the UE does not need to store network slice information in advance, nor does it need to have the ability to identify and process such information.

[0146] Furthermore, after receiving the slice registration request, the AMF unit can determine the target network slice corresponding to the UE based on the slice registration request and the network slice information corresponding to the UE stored in the AMF unit. The process of the AMF unit determining the target network slice can be referred to the description in the above embodiments, and will not be repeated here.

[0147] Furthermore, after determining the target network slice, the AMF unit will send a slice registration response to the UE, and the UE will be able to receive the slice registration response.

[0148] Of course, in some embodiments, if network slice registration fails, the AMF unit will also return a slice registration response indicating that network slice registration has failed. This slice registration response indicates that network slice registration was successful.

[0149] It should be noted that the AMF unit does not carry network slice information when sending the slice registration response to the UE. Therefore, the UE does not need to store, identify, or process network slice information after receiving the slice registration response.

[0150] The network slice registration method provided in this embodiment involves the UE sending a slice registration request and receiving a slice registration response, whereby the slice registration response indicates successful network slice registration. Since the slice registration request instructs the AMF unit to determine the target network slice corresponding to the UE based on the slice registration request and the network slice information corresponding to the UE stored in the AMF unit, the slice registration request initiated by the UE does not need to carry network slice-related information. The AMF unit can then determine the target network slice corresponding to the UE based on the slice registration request initiated by the UE and the stored network slice information. Thus, the UE can achieve network slice registration without requiring development support for the slice technology, avoiding the UE's dependence on the slice technology, improving the flexibility of network slice usage, and consequently increasing the utilization rate of network slices.

[0151] To more clearly illustrate the network slice registration method in this application, this document combines... Figure 8 illustrate. Figure 8 This is a schematic diagram of the signaling interaction of a network slice registration method according to an embodiment of this application. Figure 8 As shown, the network slice registration method includes the following steps:

[0152] In S801, the UE sends a slice registration request to the BS. The slice registration request carries the user identifier and first user authentication information, but does not carry network slice-related information.

[0153] S802, BS selects the AMF unit.

[0154] S803, BS forwards slice registration request to AMF unit.

[0155] S804, the AMF unit sends an authentication request to the authentication server. The authentication request includes the user identifier and the first user authentication information.

[0156] S805, the authentication server sends an authentication information request to the UDM. This authentication information request includes the user identifier.

[0157] S806, UDM determines the second authentication information. It can be understood that the second authentication information is the information corresponding to the user identifier.

[0158] S807, UDM sends the second authentication information to the authentication server.

[0159] S808, the authentication server performs authentication. For example, the authentication server compares the first authentication information with the second authentication information.

[0160] S809: After successful authentication, the authentication server sends an authentication success response to the AMF unit. This success response includes the UDM identifier.

[0161] S810, the AMF unit sends a subscription slice information request to the UDM. The subscription slice information request includes the user identifier.

[0162] S811, UDM confirmed its contract with NSSAI. It's understandable that the NSSAI contract corresponds to the user's identifier.

[0163] S812, UDM sends the signed NSSAI to the AMF unit.

[0164] S813, the AMF unit will use the intersection of the signed NSSAI, the storage configured NSSAI, and the allowed NSSAI as the target network slice to complete the registration.

[0165] S814, the AMF unit sends a slice registration response to the BS.

[0166] S815, the BS forwards the slice registration response to the UE.

[0167] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to 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 flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0168] Based on the same inventive concept, this application also provides a network slice registration apparatus for implementing the network slice registration method described above. The solution provided by this apparatus is similar to the implementation described in the above method; therefore, the specific limitations in the network slice registration apparatus embodiments provided below can be found in the limitations of the network slice registration method described above, and will not be repeated here.

[0169] Figure 9 This is a structural block diagram of a network slicing registration device according to an embodiment of this application, such as... Figure 9 As shown, this application embodiment provides a network slice registration device 900, including: a receiving module 901 and a determining module 902, wherein:

[0170] The receiving module 901 is used to receive the slice registration request initiated by the user terminal UE.

[0171] The determination module 902 is used to determine the target network slice corresponding to the UE based on the slice registration request and the network slice information corresponding to the UE stored in the AMF unit.

[0172] The network slice registration apparatus provided in this embodiment receives a slice registration request initiated by a user terminal (UE) and determines the target network slice corresponding to the UE based on the slice registration request and the network slice information corresponding to the UE stored in the AMF unit. Currently, in traditional technologies, slicing technology requires UE development support. Therefore, the UE needs to store its corresponding network slice information in advance. Then, the UE initiates a slice registration request carrying relevant information about the network slice to the AMF unit based on its stored network slice information, and determines the target network slice based on the content returned by the AMF unit. However, in the apparatus provided in this embodiment, since the network slice information corresponding to the UE is stored in the AMF unit, the slice registration request initiated by the UE does not need to carry the relevant information about the network slice. Furthermore, the AMF unit can determine the target network slice corresponding to the UE based on the slice registration request initiated by the UE and the stored network slice information. Therefore, the UE does not need development support for the slicing technology to achieve network slice registration, avoiding the UE's dependence on the slicing technology, improving the flexibility of network slice usage, and thus increasing the utilization rate of network slices.

[0173] Optionally, the determining module 902 includes:

[0174] The acquisition unit is used to obtain the contracted slice information from the Unified Data Management (UDM) in response to the slice registration request.

[0175] The first determining unit is used to determine the target network slice based on the contracted slice information and the network slice information.

[0176] Optionally, the contracted slice information includes contracted NSSAI; the network slice information includes configured NSSAI and allowed NSSAI; the first determining unit is further configured to determine the intersection of contracted NSSAI, configured NSSAI and allowed NSSAI as the target network slice.

[0177] Optionally, the acquisition unit includes:

[0178] The authentication subunit is used to authenticate the UE based on the slice registration request.

[0179] The Acquisition Subunit is used to obtain the contracted slice information from the UDM after successful authentication.

[0180] Optionally, the authentication subunit is used to send an authentication request to the authentication server according to the slice registration request; the authentication request includes the first user authentication information corresponding to the UE, the authentication request is used to instruct the authentication server to obtain the second user authentication information from the UDM, and after successfully authenticating the UE according to the first user authentication information and the second user authentication information, it sends back an authentication success response; and receives the authentication result sent by the authentication server based on the authentication success response.

[0181] Optionally, the authentication result includes a UDM identifier; an acquisition subunit is used to send a subscription slice information request to the UDM corresponding to the UDM identifier if the authentication is successful; the subscription slice information request includes a user identifier; and the subunit receives the subscription slice information corresponding to the user identifier sent by the UDM.

[0182] Optionally, the network slice registration device 900 further includes:

[0183] The sending module is used to send a slice registration response to the UE; the slice registration response indicates that the network slice registration was successful.

[0184] Optionally, the receiving module 901 is further configured to receive a slice registration request forwarded by the UE through the base station BS; the sending module is further configured to send a slice registration response to the UE through the BS.

[0185] Optionally, the slice registration request does not carry information about the network slice.

[0186] Figure 10 This is a structural block diagram of another network slicing registration device in the embodiments of this application, such as... Figure 10 As shown, this application embodiment provides a network slice registration device 1000, including: a sending module 1001 and a receiving module 1002, wherein:

[0187] The sending module 1001 is used to send a slice registration request; the slice registration request is used to instruct the AMF unit to determine the target network slice corresponding to the UE based on the slice registration request and the network slice information corresponding to the UE stored in the AMF unit.

[0188] The receiving module 1002 is used to receive the slice registration response; the slice registration response is used to indicate that the network slice registration is successful.

[0189] Optionally, the slice registration request does not carry information about the network slice.

[0190] The network slice registration apparatus provided in this embodiment allows the UE to send a slice registration request and receive a slice registration response, whereby the slice registration response indicates successful network slice registration. Since the slice registration request instructs the AMF unit to determine the target network slice corresponding to the UE based on the slice registration request and the network slice information corresponding to the UE stored in the AMF unit, the slice registration request initiated by the UE does not need to carry network slice-related information. The AMF unit can then determine the target network slice corresponding to the UE based on the slice registration request initiated by the UE and the stored network slice information. Thus, the UE can achieve network slice registration without requiring development support for the slice technology, avoiding the UE's dependence on the slice technology, improving the flexibility of network slice usage, and consequently increasing the utilization rate of network slices.

[0191] Each module in the aforementioned network slicing 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, or stored in the memory of a computer device as software, so that the processor can call and execute the corresponding operations of each module.

[0192] In one embodiment, a network slice registration system is provided. Please refer to [reference needed]. Figure 1 The network slice registration system includes a UE, a BS, an AMF unit, an authentication server, and a UDM. The AMF unit and the UE execute the network slice registration method described in the above embodiments, which will not be repeated here.

[0193] Figure 11 This is a schematic diagram of the structure of an AMF unit in an embodiment of this application, as shown below. Figure 11 As shown, the AMF unit 1100 includes at least one transceiver 1101, a processor 1102, a memory 1103, and at least one bus system 1104.

[0194] Bus system 1104 is used to implement communication connections between components. Memory 1103 may include high-speed RAM memory and may also include non-volatile memory (NVM), such as at least one disk storage device. The memory stores computer programs. Transceiver 1101 may be coupled to processor 1102, and can perform receiving or sending operations under the instruction or control of processor 1102.

[0195] In this embodiment, transceiver 1101 is used to receive slice registration requests initiated by user terminal UE.

[0196] The processor 1102 executes a computer program to determine the target network slice corresponding to the UE based on the slice registration request and the network slice information corresponding to the UE stored in the AMF unit.

[0197] In one embodiment, the processor 1102 is further configured to, in response to the slice registration request, obtain subscribed slice information from the Unified Data Management (UDM); and determine the target network slice based on the subscribed slice information and the network slice information.

[0198] In one embodiment, the processor 1102 is further configured to determine the intersection of the signed NSSAI, the configured NSSAI, and the allowed NSSAI as the target network slice.

[0199] In one embodiment, the processor 1102 is further configured to authenticate the UE according to the slice registration request; and if the authentication is successful, obtain the subscribed slice information from the UDM.

[0200] In one embodiment, transceiver 1101 is further configured to send an authentication request to an authentication server according to the slice registration request; the authentication request includes first user authentication information corresponding to the UE, the authentication request is used to instruct the authentication server to obtain second user authentication information from the UDM, and after successfully authenticating the UE according to the first user authentication information and the second user authentication information, to send back an authentication success response; and to receive the authentication result sent by the authentication server based on the authentication success response.

[0201] In one embodiment, transceiver 1101 is further configured to send a subscription slice information request to the UDM corresponding to the UDM identifier when authentication is successful; the subscription slice information request includes a user identifier; and receive the subscription slice information corresponding to the user identifier sent by the UDM.

[0202] In one embodiment, transceiver 1101 is further configured to send a slice registration response to the UE; the slice registration response is used to indicate that the network slice registration is successful.

[0203] In one embodiment, transceiver 1101 is further configured to receive the slice registration request forwarded by the UE through the base station BS; and send the slice registration response to the UE through the BS.

[0204] In one embodiment, the slice registration request does not carry information related to the network slice.

[0205] Figure 12 This is a schematic diagram of the structure of a UE according to an embodiment of this application, as shown below. Figure 12 As shown, UE1200 may include a processor 1201, a memory 1202, at least one network interface 1203 and a user interface 1203, a bus system 1205 and a transceiver 1206.

[0206] The various components in UE1200 are coupled together via bus system 1205. It is understood that bus system 1205 is used to implement communication between these components. In addition to a data bus, bus system 1205 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 1 Various buses are designated as bus system 1205. Additionally, this embodiment of the invention includes a transceiver 1206, which may consist of multiple elements, including transceivers and receivers, providing a unit for communicating with various other devices over a transmission medium.

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

[0208] 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.

[0209] In some implementations, memory 1202 stores elements such as executable modules or data structures, or subsets thereof, or extended sets thereof: operating system 1207 and application program 1208.

[0210] The operating system 1207 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 1208 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 the application program 1208.

[0211] In this embodiment of the invention, the program or instructions stored in the memory 1202 are invoked, specifically, the program or instructions stored in the application program 1208.

[0212] 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.

[0213] It is understood that the embodiments described in this invention can be implemented using 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 described in this application, or combinations thereof.

[0214] For software implementation, the technology described in the embodiments of the present invention can be implemented by modules (e.g., procedures, functions, etc.) that perform the functions described in 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.

[0215] In this embodiment, transceiver 1206 is used to send a slice registration request; the slice registration request is used to instruct the AMF unit to determine the target network slice corresponding to the UE based on the slice registration request and the network slice information corresponding to the UE stored in the AMF unit; and to receive a slice registration response; the slice registration response is used to indicate that the network slice registration is successful.

[0216] In one embodiment, the slice registration request does not carry information related to the network slice.

[0217] Those skilled in the art will understand that Figure 11 and Figure 12 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the AMF unit and UE to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0218] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, the computer program performing the following steps when executed by a processor:

[0219] Receive slice registration requests initiated by user terminal (UE);

[0220] Based on the slice registration request and the network slice information corresponding to the UE stored in the AMF unit, the target network slice corresponding to the UE is determined.

[0221] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0222] In response to the slice registration request, the system obtains the subscribed slice information from the Unified Data Management (UDM); and determines the target network slice based on the subscribed slice information and the network slice information.

[0223] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0224] The intersection of the signed NSSAI, the configured NSSAI, and the allowed NSSAI is determined as the target network slice.

[0225] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0226] Based on the slice registration request, the UE is authenticated; if the authentication is successful, the subscribed slice information is obtained from the UDM.

[0227] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0228] According to the slice registration request, an authentication request is sent to the authentication server; the authentication request includes the first user authentication information corresponding to the UE, the authentication request is used to instruct the authentication server to obtain the second user authentication information from the UDM, and after successfully authenticating the UE according to the first user authentication information and the second user authentication information, a successful authentication response is sent back; the authentication result sent by the authentication server based on the successful authentication response is received.

[0229] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0230] If authentication is successful, a subscription slice information request is sent to the UDM corresponding to the UDM identifier; the subscription slice information request includes a user identifier; and the subscription slice information corresponding to the user identifier sent by the UDM is received.

[0231] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0232] A slice registration response is sent to the UE; the slice registration response is used to indicate that the network slice registration is successful.

[0233] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0234] Receive the slice registration request forwarded by the UE through the base station (BS); send the slice registration response to the UE through the BS.

[0235] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0236] Send a slice registration request; the slice registration request is used to instruct the AMF unit to determine the target network slice corresponding to the UE based on the slice registration request and the network slice information corresponding to the UE stored in the AMF unit;

[0237] Receive a slice registration response; the slice registration response indicates that the network slice registration was successful.

[0238] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, performs the following steps:

[0239] Receive slice registration requests initiated by user terminal (UE);

[0240] Based on the slice registration request and the network slice information corresponding to the UE stored in the AMF unit, the target network slice corresponding to the UE is determined.

[0241] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0242] In response to the slice registration request, the system obtains the subscribed slice information from the Unified Data Management (UDM); and determines the target network slice based on the subscribed slice information and the network slice information.

[0243] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0244] The intersection of the signed NSSAI, the configured NSSAI, and the allowed NSSAI is determined as the target network slice.

[0245] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0246] Based on the slice registration request, the UE is authenticated; if the authentication is successful, the subscribed slice information is obtained from the UDM.

[0247] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0248] According to the slice registration request, an authentication request is sent to the authentication server; the authentication request includes the first user authentication information corresponding to the UE, the authentication request is used to instruct the authentication server to obtain the second user authentication information from the UDM, and after successfully authenticating the UE according to the first user authentication information and the second user authentication information, a successful authentication response is sent back; the authentication result sent by the authentication server based on the successful authentication response is received.

[0249] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0250] If authentication is successful, a subscription slice information request is sent to the UDM corresponding to the UDM identifier; the subscription slice information request includes a user identifier; and the subscription slice information corresponding to the user identifier sent by the UDM is received.

[0251] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0252] A slice registration response is sent to the UE; the slice registration response is used to indicate that the network slice registration is successful.

[0253] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0254] Receive the slice registration request forwarded by the UE through the base station (BS); send the slice registration response to the UE through the BS.

[0255] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0256] Send a slice registration request; the slice registration request is used to instruct the AMF unit to determine the target network slice corresponding to the UE based on the slice registration request and the network slice information corresponding to the UE stored in the AMF unit;

[0257] Receive a slice registration response; the slice registration response indicates that the network slice registration was successful.

[0258] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0259] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0260] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are 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 application should be determined by the appended claims.

Claims

1. A network slice registration method, characterized in that, The method, applied to the Access and Mobility Management Function (AMF) unit, includes: Receive a slice registration request initiated by a user terminal (UE); the slice registration request does not carry network slice-related information; Based on the user identifier in the slice registration request and the network slice information corresponding to different user identifiers stored in the AMF unit, the network slice information corresponding to the UE is determined; the network slice information includes configuring NSSAI and allowing NSSAI. In response to the slice registration request, the system obtains the contracted slice information from the Unified Data Management (UDM); the contracted slice information includes the contracted NSSAI. The target network slice is determined based on the contracted slice information and the network slice information; The step of determining the target network slice based on the contracted slice information and the network slice information includes: The intersection of the signed NSSAI, the configured NSSAI, and the allowed NSSAI is determined as the target network slice; After determining the target network slice, the target network slice is updated to its own stored NSSAI allowed.

2. The method according to claim 1, characterized in that, The step of obtaining the contracted slice information from the Unified Data Management (UDM) in response to the slice registration request includes: The UE is authenticated based on the slice registration request; If authentication is successful, the contracted slice information is obtained from the UDM.

3. The method according to claim 2, characterized in that, The step of authenticating the UE according to the slice registration request includes: According to the slice registration request, an authentication request is sent to the authentication server; the authentication request includes the first user authentication information corresponding to the UE, and the authentication request is used to instruct the authentication server to obtain the second user authentication information from the UDM, and after successfully authenticating the UE according to the first user authentication information and the second user authentication information, a successful authentication response is sent back. Receive the authentication result sent by the authentication server based on the successful authentication response.

4. The method according to claim 3, characterized in that, The authentication result includes the UDM identifier; Upon successful authentication, obtaining the contracted slice information from the UDM includes: If authentication is successful, a subscription slice information request is sent to the UDM corresponding to the UDM identifier; the subscription slice information request includes the user identifier. Receive the subscription slice information corresponding to the user identifier sent by the UDM.

5. The method according to any one of claims 1-4, characterized in that, The method further includes: A slice registration response is sent to the UE; the slice registration response is used to indicate that the network slice registration is successful.

6. The method according to claim 5, characterized in that, The process of receiving a slice registration request initiated by a user terminal (UE) includes: Receive the slice registration request forwarded by the UE through the base station BS; Sending the slice registration response to the UE includes: The BS sends the slice registration response to the UE.

7. A slice registration method, characterized in that, Applied to a UE, the method includes: A slice registration request is sent; the slice registration request is used to instruct the AMF unit to determine the network slice information corresponding to the UE based on the user identifier in the slice registration request and the network slice information corresponding to different user identifiers stored by the AMF unit. The network slice information is used to determine the target network slice by comparing it with the subscribed slice information; the slice registration request does not carry network slice related information; the network slice information includes configuring NSSAI and allowing NSSAI; the subscribed slice information includes subscribed NSSAI. Receive a slice registration response; the slice registration response indicates that the network slice registration was successful. The determination of the target network slice includes: The intersection of the signed NSSAI, the configured NSSAI, and the allowed NSSAI is determined as the target network slice; After determining the target network slice, the AMF unit updates the target network slice with the NSSAI allowed in its own storage.

8. A network slicing registration device, characterized in that, The device is applied to an AMF unit, and the device includes: The receiving module is used to receive a slice registration request initiated by a user terminal (UE); the slice registration request does not carry network slice related information. The determination module is configured to determine the network slice information corresponding to the UE based on the user identifier in the slice registration request and the network slice information corresponding to different user identifiers stored in the AMF unit; in response to the slice registration request, obtain the subscribed slice information from the Unified Data Management (UDM); and determine the target network slice based on the subscribed slice information and the network slice information; the network slice information includes configuring NSSAI and allowing NSSAI; the subscribed slice information includes subscribed NSSAI. The step of determining the target network slice based on the contracted slice information and the network slice information includes: The intersection of the signed NSSAI, the configured NSSAI, and the allowed NSSAI is determined as the target network slice; After determining the target network slice, the target network slice is updated to its own stored NSSAI allowed.

9. A network slicing registration device, characterized in that, The device is applied to a UE, and the device includes: A sending module is used to send a slice registration request; the slice registration request is used to instruct the AMF unit to determine the network slice information corresponding to the UE based on the user identifier in the slice registration request and the network slice information corresponding to different user identifiers stored in the AMF unit. The network slice information is used to determine the target network slice by comparing it with the subscribed slice information; the slice registration request does not carry network slice related information; the network slice information includes configuring NSSAI and allowing NSSAI; the subscribed slice information includes subscribed NSSAI. The receiving module is used to receive the slice registration response; the slice registration response indicates that the network slice registration was successful. The determination of the target network slice includes: The intersection of the signed NSSAI, the configured NSSAI, and the allowed NSSAI is determined as the target network slice; After determining the target network slice, the AMF unit updates the target network slice with the NSSAI allowed in its own storage.

10. A network slicing registration system, characterized in that, The slice registration system includes UE, BS, AMF unit, authentication server and UDM; The AMF unit is used to perform the method according to any one of claims 1-6; The UE is used to perform the method of claim 7.

11. An AMF unit, characterized in that, The AMF unit includes a transceiver, a processor, and a memory, wherein the memory stores a computer program. The transceiver is used to receive a slice registration request initiated by a user terminal (UE); the slice registration request does not carry information related to network slices. The processor executes the computer program to determine the network slice information corresponding to the UE based on the user identifier in the slice registration request and the network slice information corresponding to different user identifiers stored in the AMF unit. In response to the slice registration request, obtain the contracted slice information from the Unified Data Management (UDM); The target network slice is determined based on the contracted slice information and the network slice information; The network slicing information includes configuring NSSAI and allowing NSSAI; The contracted slice information includes the contract with NSSAI; The step of determining the target network slice based on the contracted slice information and the network slice information includes: The intersection of the signed NSSAI, the configured NSSAI, and the allowed NSSAI is determined as the target network slice; After determining the target network slice, the target network slice is updated to its own stored NSSAI allowed.

12. A UE, characterized in that, The UE includes a transceiver; The transceiver is used to send a slice registration request; the slice registration request is used to instruct the AMF unit to determine the network slice information corresponding to the UE based on the user identifier in the slice registration request and the network slice information corresponding to different user identifiers stored in the AMF unit; the network slice information is used to determine the target network slice with the subscribed slice information. The slice registration request did not carry any information related to the network slice; The network slice information includes configuring NSSAI and allowing NSSAI; the subscribed slice information includes subscribing to NSSAI. The transceiver is also used to receive slice registration responses; The slice registration response is used to indicate that the network slice registration was successful; The determination of the target network slice includes: The intersection of the signed NSSAI, the configured NSSAI, and the allowed NSSAI is determined as the target network slice; After determining the target network slice, the AMF unit updates the target network slice with the NSSAI allowed in its own storage.

13. 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 method according to any one of claims 1 to 7.

14. 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 method according to any one of claims 1 to 7.

Images