Network slice registration method, amf unit, user equipment, base station and storage medium

Abstract

The application relates to a network slice registration method, an AMF unit, user equipment, a base station and a storage medium. The method comprises the following steps: receiving a registration request sent by user equipment (UE) through a base station, obtaining subscription slice information and default slice information from a user data management unit in response to the registration request, determining allowed slice information corresponding to the UE according to the subscription slice information and the default slice information, and thus completing network slice registration. Since the user equipment does not need to have the ability of identifying network slice information, generating requested network slice information and the like related to slice information in the embodiment, the AMF unit obtains the subscription slice information and the default slice information from the user data management unit, determines the allowed slice information corresponding to the UE according to the subscription slice information and the default slice information, and completes the network slice registration, so that the dependence on the user equipment is reduced.

Description

Technical Field

[0001] This application relates to the field of network slice registration technology, and in particular to a network slice registration method, an AMF unit, a user equipment, a base station, and a storage medium. Background Technology

[0002] With the development of communication technology, all industries are moving towards informatization and intelligentization. Different application scenarios, such as high-definition video, the Internet of Things, and the Internet of Vehicles, have different requirements for network mobility, security, latency, and reliability. To meet the needs of different application scenarios, network slicing has emerged. Network slicing is an on-demand networking method that allows operators to separate multiple network slices on a unified infrastructure. Each network slice is logically isolated to adapt to the needs of different application scenarios.

[0003] After a terminal selects and registers a network slice from among multiple allowed network slices, it can use that network slice for data communication. However, the current network slice registration process is highly dependent on the terminal. Summary of the Invention

[0004] Therefore, it is necessary to provide a network slice registration method, AMF unit, user equipment, base station, and storage medium that can reduce the dependence of the network slice registration process on the terminal, in order to address the above-mentioned technical problems.

[0005] Firstly, this application provides a network slicing registration method. The method is applied to the Access and Mobility Management Function (AMF) unit and includes:

[0006] Receive registration requests sent by user equipment (UE) through the base station;

[0007] In response to the registration request, retrieve the contracted slice information and default slice information from the user data management unit;

[0008] Based on the contracted slice information and the default slice information, the allowed slice information corresponding to the UE is determined; the allowed slice information is used for network slice registration.

[0009] In one embodiment, the allowed slice information corresponding to the UE is determined based on the subscribed slice information and the default slice information, including:

[0010] Based on the preset slice priority rules, the allowed slice information is determined from the signed slice information and the default slice information.

[0011] In one embodiment, allowed slice information is determined from the contracted slice information and the default slice information according to a preset slice priority rule, including:

[0012] Based on the slice priority rules, a number of allowed slices less than or equal to a preset number are determined from the contracted slice information and the default slice information; the preset number is related to the processing capacity of the network accessed by the AMF unit.

[0013] In one embodiment, the slice priority rule includes at least one of the following:

[0014] The default slice information has a higher priority than the signed slice information;

[0015] Slice information that is used more frequently has a higher priority than slice information that is used less frequently.

[0016] In one embodiment, in response to a registration request, subscribed slice information and default slice information are obtained from the user data management unit, including:

[0017] In response to the registration request, an authentication request is sent to the authentication server; the authentication request is used to instruct the authentication server to obtain the UE's authentication parameters from the user data management unit.

[0018] If an authentication response is received from the authentication server, the contracted slice information and default slice information are obtained from the user data management unit; the authentication response is the response sent by the authentication server after the authentication parameters are successfully authenticated.

[0019] In one embodiment, if an authentication response is received from the authentication server, the subscribed slice information and default slice information are obtained from the user data management unit, including:

[0020] If an authentication response is received, a request to obtain the contract data is sent to the user data management unit;

[0021] The user data management unit receives the UE's subscription data sent based on the subscription data acquisition request; the subscription data includes subscription slice information and default slice information.

[0022] In one embodiment, the contracted slice information includes contracted network slice selection assistance information, and the default slice information includes default network slice selection assistance information.

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

[0024] The base station sends a registration response to the UE; the registration response indicates that the network slice registration was successful.

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

[0026] Secondly, this application also provides a network slicing registration method, which is applied to a user equipment (UE) and includes:

[0027] Send a registration request to the AMF unit; the registration request is used to instruct the AMF unit to obtain the subscribed slice information and default slice information from the user data management unit;

[0028] Receive the registration response sent by the AMF unit; the registration response is a response sent by the AMF unit after determining the allowed slice information corresponding to the UE based on the subscribed slice information and the default slice information. The registration response is used to indicate that the network slice registration is successful.

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

[0030] In one embodiment, the registration response did not carry slice permission information.

[0031] Thirdly, this application also provides a network slicing registration method, which is applied to a base station and includes:

[0032] Receive the registration request sent by the UE;

[0033] Send a registration request to the AMF unit; the registration request is used to instruct the AMF unit to obtain the subscription slice information and default slice information from the user data management unit, and to determine the allowed slice information corresponding to the UE based on the subscription slice information and default slice information;

[0034] Receive the registration response sent by the AMF unit and send a registration response to the UE; the registration response is used to indicate that the network slice registration was successful.

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

[0036] In one embodiment, the registration response did not carry slice permission information.

[0037] Fourthly, this application also provides an AMF unit, which includes:

[0038] The receiving module is used to receive the registration request sent by the UE through the base station;

[0039] The acquisition module is used to retrieve the contracted slice information and default slice information from the user data management unit in response to the registration request;

[0040] The determination module is used to determine the allowed slice information corresponding to the UE based on the subscribed slice information and the default slice information; the allowed slice information is used for network slice registration.

[0041] Fifthly, this application also provides a user equipment, which includes:

[0042] The transmitter is used to send a registration request to the AMF unit; the registration request is used to instruct the AMF unit to obtain the subscribed slice information and the default slice information from the user data management unit.

[0043] The receiver is used to receive the registration response sent by the AMF unit. The registration response is a response sent by the AMF unit after determining the allowed slice information corresponding to the UE based on the subscribed slice information and the default slice information. The registration response is used to indicate that the network slice registration is successful.

[0044] Sixthly, this application also provides a base station, which includes:

[0045] Receiver, used to receive registration requests sent by the UE;

[0046] The transmitter is used to send a registration request to the AMF unit; the registration request is used to instruct the AMF unit to obtain the subscription slice information and default slice information from the user data management unit, and to determine the allowed slice information corresponding to the UE based on the subscription slice information and default slice information.

[0047] The receiver is also used to receive the registration response sent by the AMF unit and send a registration response to the UE; the registration response is used to indicate that the network slice registration is successful.

[0048] Seventhly, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, implements the steps of the above-described method.

[0049] Fifthly, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, implements the steps of the above-described method.

[0050] The aforementioned network slice registration method, AMF unit, user equipment, base station, and storage medium receive a registration request sent by the user equipment (UE) through the base station. In response to the registration request, the method retrieves subscribed slice information and default slice information from the user data management unit. Based on the subscribed slice information and default slice information, it determines the allowed slice information corresponding to the UE, thereby completing the network slice registration. Since this embodiment does not require the user equipment to have the capability to identify network slice information or generate requested network slice information, but instead relies on the AMF unit to retrieve the subscribed slice information and default slice information from the user data management unit and determine the allowed slice information corresponding to the UE to complete the network slice registration, the dependence on the user equipment is reduced. Attached Figure Description

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

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

[0053] Figure 3 This is a flowchart illustrating a method for obtaining slice information provided in an embodiment of this application;

[0054] Figure 4 This is a flowchart illustrating another method for obtaining slice information provided in an embodiment of this application;

[0055] Figure 5 This is a flowchart illustrating another network slice registration method provided in an embodiment of this application;

[0056] Figure 6 This is a flowchart illustrating another network slice registration method provided in an embodiment of this application;

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

[0058] Figure 8 This is a structural block diagram of an AMF unit provided in an embodiment of this application;

[0059] Figure 9 This is a schematic diagram of the structure of the user equipment provided in the embodiments of this application;

[0060] Figure 10 This is a schematic diagram of the base station structure provided in the embodiments of this application. Detailed Implementation

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

[0062] Currently, User Equipment (UE) relies heavily on the terminal for network slice registration. For example, the UE needs the ability to identify network slice information and generate requested network slice information. However, UE upgrades are more difficult than network upgrades, especially without significant, undisclosed requirements. Therefore, this application provides a network slice registration method to reduce UE dependence. This method is primarily network-side based. Each network slice is uniquely identified by a Single NetworkSlice Selection Assistance Information (S-NSSAI), and a collection of one or more S-NSSAIs is called an NSSAI. In 5G New Radio (NR), multiple NSSAI categories exist for storage by both the UE and the network. These categories include, but are not limited to, allowed, requested, or configured NSSAIs.

[0063] The network slice registration method provided in this application embodiment can be applied to, for example, Figure 1 The application environment shown includes user equipment 101, base station 102, access and mobility management function (AMF) unit 103, and unified data management (UDM) unit 104. User equipment 101 sends a registration request to base station 102, and base station 102 sends the registration request to AMF unit 103. In response to the registration request, AMF unit 103 obtains the subscribed slice information and default slice information from UDM unit 104, and determines the allowed slice information corresponding to the UE based on the subscribed slice information and default slice information.

[0064] User equipment 101 can be, but is not limited to, smartphones, tablets, and portable wearable devices. Portable wearable devices can be smartwatches, smart bracelets, head-mounted devices, etc. 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. AMF unit 103 and UDM unit 104 can be implemented using independent servers or server clusters composed of multiple servers.

[0065] In one embodiment, such as Figure 2 As shown, Figure 2 This is a flowchart illustrating a network slice registration method provided in an embodiment of this application, applied to... Figure 1 Taking the AMF cell in the image as an example, this method includes the following steps:

[0066] S201. Receive the registration request sent by the user equipment (UE) through the base station.

[0067] In this embodiment, if the UE needs to register for network slicing, it will initiate a registration request. Accordingly, the base station receives the registration request sent by the UE and determines the target AMF unit.

[0068] The registration request may include information such as the 5G Temporary Mobile Station Identifier (S-TMSI) and the Globally Unique AMF Identifier (GUAMI). The base station can select an AMF unit as the target AMF unit based on this information, or determine the target AMF unit based on other rules. For example, if the base station determines the target AMF unit based on other rules, it may use a pre-configured AMF unit or an AMF unit that the UE uses frequently.

[0069] After the base station identifies the target AMF unit, it can send the registration request to the target AMF unit, which then receives the registration request. Figure 1 Taking the AMF unit in the example as the target AMF unit, then the AMF unit receives the registration request sent by the base station.

[0070] S202. In response to the registration request, obtain the contracted slice information and default slice information from the user data management unit.

[0071] After receiving the registration request, the AMF unit will respond to the registration request by obtaining the contracted slice information and default slice information from the UDM unit.

[0072] In this embodiment, the default slice information can be the identifier of any one of the multiple network slices subscribed to by the UE. The subscribed slice information refers to the slice information other than the default slice information among the multiple network slices subscribed to by the UE. The multiple network slices subscribed to by the UE are network slices that the UE is allowed to use. The information of the network slices that the UE is allowed to use must be subscribed to at the UDM unit. Only network slices subscribed to at the UDM unit are entitled to be used by the UE.

[0073] The UDM stores subscription information corresponding to different UEs. For example, if the subscription slice information corresponding to a UE includes S-NSSAI1, S-NSSAI2, and S-NSSAI3, then the UE can use the individual network slices subscribed to by S-NSSAI1, S-NSSAI2, and S-NSSAI3 respectively. Optionally, the subscription slice information may also include other information such as the utilization rate and congestion rate of the individual network slices.

[0074] S203. Based on the subscribed slice information and the default slice information, determine the allowed slice information corresponding to the UE; the allowed slice information is used for network slice registration.

[0075] In this embodiment, the usage frequency of each slice in the subscribed slice information can be determined, and the allowed slice information corresponding to the UE can be determined based on the usage frequency and the default slice information. For example, the default slice information and the slice information with the highest usage frequency can be used as the allowed slice information corresponding to the UE.

[0076] Optionally, the allowed slice information corresponding to the UE can also be determined from the subscribed slice information and the default slice information based on the service type of the user equipment. For example, if the service type of the user equipment is service A, and a certain slice information in the subscribed slice information corresponds to service A, then the default slice information and the slice information corresponding to service A can be used as the allowed slice information.

[0077] The AMF unit determines the allowed slice information corresponding to the UE, and then the Network Slice Selection Function (NSSF) unit selects the corresponding network slice instance based on the allowed slice information, and uses the selected network slice instance to register the network slice.

[0078] The method provided in this application embodiment receives a registration request sent by a user equipment (UE) through a base station, and in response to the registration request, obtains subscribed slice information and default slice information from the user data management unit (AMF). Based on the subscribed slice information and default slice information, it determines the allowed slice information corresponding to the UE, thereby completing network slice registration. Since this embodiment does not require the user equipment to have the capability to identify network slice information or generate requested network slice information, but instead the AMF unit obtains the subscribed slice information and default slice information from the user data management unit and determines the allowed slice information corresponding to the UE based on the subscribed slice information and default slice information to complete network slice registration, the dependence on the user equipment is reduced.

[0079] In some embodiments, based on the above embodiments, S203 can be implemented in the following way:

[0080] Based on the preset slice priority rules, the allowed slice information is determined from the signed slice information and the default slice information.

[0081] For example, the preset slice priority rules include: slice information with high usage frequency has a higher priority than slice information with low usage frequency. In this embodiment, a preset number of slice information can be selected based on the usage frequency of the slice information, starting from the highest usage frequency, and the selected preset number of slice information can be used as the allowed slice information.

[0082] The method provided in this embodiment determines allowed slice information from contracted slice information and default slice information according to preset slice priority rules, ensuring that the determined allowed slice information is slice information with higher priority. This ensures that the determined allowed slice information is likely to be slice information frequently used by the user device, thereby meeting the user's needs and habits.

[0083] In some embodiments, the above-mentioned determination of allowed slice information from contracted slice information and default slice information based on preset slice priority rules can be achieved in the following way:

[0084] Based on the slice priority rules, a number of allowed slices less than or equal to a preset number are determined from the contracted slice information and the default slice information; the preset number is related to the processing capacity of the network accessed by the AMF unit.

[0085] The preset number is related to the processing capacity of the network to which the AMF unit is connected. For example, if the maximum processing capacity of the network to which the AMF unit is connected is 8, the preset number can be set to a value less than or equal to 8.

[0086] In one embodiment, the slice priority rule includes at least one of the following:

[0087] The default slice information has a higher priority than the signed slice information;

[0088] Slice information that is used more frequently has a higher priority than slice information that is used less frequently.

[0089] For example, if the preset quantity is 8, the default slice information includes one S-NSSAI, and the contracted slice information includes 10 S-NSSAIs. Since the default slice information has a higher priority than the contracted slice information, the default slice information is selected as one of the allowed slice information. Then, 7 slice information is selected from the contracted slice information, and these 7 slice information are selected in descending order of usage frequency. Thus, a total of 8 S-NSSAIs are selected as allowed slice information from the default slice information and the contracted slice information.

[0090] For example, if the preset quantity is 8, the default slice information includes one S-NSSAI, and the signed slice information includes two S-NSSAIs, then the two S-NSSAIs in the default slice information and the signed slice information can be used as allowed slice information, that is, the total number of S-NSSAIs in the allowed slice information is 3.

[0091] For example, if the preset quantity is 1, and the default slice information includes an S-NSSAI, then the default slice information will be used as the allowed slice information.

[0092] The slice priority rule in this embodiment can ensure that slice information with higher priority is selected first, thereby increasing the probability that the selected allowed slice information is slice information frequently used by the user device, thus meeting the user's needs and habits.

[0093] Reference Figure 3 , Figure 3 This is a flowchart illustrating a method for obtaining slice information according to an embodiment of this application. This embodiment relates to a possible implementation of how to obtain subscribed slice information and default slice information from a user data management unit in response to a registration request. The above-described S202 may include the following steps:

[0094] S301. In response to the registration request, send an authentication request to the authentication server; the authentication request is used to instruct the authentication server to obtain the UE's authentication parameters from the user data management unit.

[0095] In this embodiment, to improve the security of network slice registration, the AMF unit can verify the UE's identity. The AMF unit can verify the UE's identity in the following way:

[0096] Upon receiving a registration request, the AMF unit responds by sending an authentication request to the authentication server. The authentication server then sends an authentication request to the UDM unit to obtain the UE's authentication parameters. Subsequently, the authentication server authenticates the UE based on the obtained authentication parameters and the UE's authentication parameters carried in the registration request to determine the legitimacy of the UE initiating the registration request.

[0097] The registration request may include the UE's authentication parameters. These parameters can be the original authentication parameters or encrypted authentication parameters obtained by encrypting the original authentication parameters. If the registration request includes encrypted authentication parameters, the AMF unit can decrypt the encrypted authentication parameters to obtain the original authentication parameters and send them to the authentication server along with the original authentication parameters. Alternatively, the AMF unit can send the encrypted authentication parameters to the authentication server, which will then decrypt them to obtain the original authentication parameters.

[0098] The authentication server authenticates the UE based on the original authentication parameters obtained and the UE's authentication parameters carried in the registration request. The authentication process is as follows: if the authentication server determines that the obtained authentication parameters are consistent with the original authentication parameters, the UE's authentication is deemed successful; if the obtained authentication parameters are inconsistent with the original authentication parameters, the UE's authentication is deemed unsuccessful.

[0099] If the authentication server successfully authenticates the UE, it can send an authentication response to the AMF unit, which indicates that the UE's authentication has been successful. If the authentication server fails to authenticate the UE, it can send a failure authentication response to the AMF unit, which indicates that the UE's authentication has failed.

[0100] S302. If an authentication response is received from the authentication server, the contracted slice information and default slice information are obtained from the user data management unit; the authentication response is the response sent by the authentication server after the authentication parameters are successfully authenticated.

[0101] In this embodiment, if the authentication server successfully authenticates the UE, it can send an authentication response indicating successful authentication to the AMF unit, which then receives the response. Upon receiving the authentication response, the AMF unit retrieves the subscribed slice information and default slice information from the user data management unit.

[0102] The method provided in this embodiment, in response to a registration request, sends an authentication request to the authentication server, instructing the authentication server to obtain the authentication parameters of the UE from the user data management unit. Upon receiving the authentication response from the authentication server, it obtains the subscribed slice information and default slice information from the user data management unit. This ensures that the subscribed slice information and default slice information are only obtained from the user data management unit after the authentication of the user equipment is successful, thereby improving the security of network slice registration.

[0103] Reference Figure 4 , Figure 4 This is a flowchart illustrating another method for obtaining slice information provided in this application embodiment. This embodiment relates to a possible implementation of how to obtain subscribed slice information and default slice information from the user data management unit upon receiving an authentication response from the authentication server. Based on the above embodiment, S302 includes the following steps:

[0104] S401. If an authentication response is received, a contract data retrieval request is sent to the user data management unit.

[0105] The subscription data acquisition request includes the UE's identifier. The AMF unit sends the subscription data acquisition request to the UDM unit. In response, the UDM unit receives the subscription data acquisition request and sends the UE's subscription data to the AMF unit.

[0106] S402: Receive the UE's subscription data sent by the user data management unit based on the subscription data acquisition request; the subscription data includes subscription slice information and default slice information.

[0107] The method provided in this embodiment, upon receiving an authentication response, sends a subscription data acquisition request to the user data management unit and receives the UE's subscription data sent by the user data management unit based on the subscription data acquisition request, ensuring that the acquired subscription data is legitimate user equipment subscription data, thereby improving the security of network slice registration of user equipment.

[0108] In some embodiments, the contracted slice information includes contracted network slice selection assistance information, and the default slice information includes default network slice selection assistance information.

[0109] In some embodiments, after the AMF unit determines the allowed slice information corresponding to the UE based on the subscribed slice information and the default slice information, the following steps may also be included:

[0110] The base station sends a registration response to the UE; the registration response indicates that the network slice registration was successful.

[0111] The AMF unit determines the allowed slice information corresponding to the UE, and then the Network Slice Selection Function (NSSF) unit selects the corresponding network slice instance based on the allowed slice information, and uses the selected network slice instance to register the network slice. After the AMF unit determines the network slice registration, it can send a registration response to the base station, and the base station correspondingly sends the registration response to the terminal.

[0112] In some of these embodiments, the registration request does not carry information about network slices.

[0113] In traditional technology, when a UE initiates a slice registration request, it includes information about the network slice in the request. In other words, the current network slice registration process requires the UE to pre-store this information and possess the ability to identify and process it. Therefore, it is necessary to develop these capabilities for the UE to successfully register its network slices.

[0114] In this embodiment, since the registration request does not carry information related to the network slice, the UE does not need to store such information in advance, nor does it need to have the ability to identify and process it. Therefore, the network slice registration method provided in this embodiment does not require the UE to develop the ability to identify and process the network slice's information, reducing the UE's dependence on it.

[0115] The above embodiments introduced a network slice registration method using the AMF unit as the execution subject. This is combined with... Figure 5 ,by Figure 1 The user equipment in this document describes the network slice registration method as the implementing entity. (Refer to...) Figure 5 , Figure 5 This is a flowchart illustrating another network slice registration method provided in an embodiment of this application. The method includes the following steps:

[0116] S501. Send a registration request to the AMF unit; the registration request is used to instruct the AMF unit to obtain the subscribed slice information and default slice information from the user data management unit.

[0117] S502, Receive the registration response sent by the AMF unit.

[0118] The registration response is a response sent by the AMF unit after determining the allowed slice information for the UE based on the subscribed slice information and the default slice information. The registration response is used to indicate that the network slice registration is successful.

[0119] The method provided in this embodiment sends a registration request to the AMF unit and receives a registration response from the AMF unit. Since this embodiment does not require the user equipment to have the ability to identify network slice information, generate network slice information for requests, or other slice-related capabilities, the AMF unit obtains the subscribed slice information and default slice information from the user data management unit, and determines the allowed slice information corresponding to the UE based on the subscribed slice information and default slice information to complete the network slice registration. Therefore, the dependence on the user equipment is reduced.

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

[0121] In one embodiment, the registration response did not carry slice permission information.

[0122] Since this embodiment does not require the user equipment to identify or process slice information, the registration response does not need to be sent to the user equipment. Instead, a registration response indicating whether the network slice registration was successful or failed is sent to the user equipment, thereby reducing network resource overhead and improving the efficiency of network slice registration.

[0123] The above embodiments describe a network slice registration method using user equipment as the execution subject. This is combined with... Figure 6 ,by Figure 1 The base station in the document describes the network slice registration method as the implementing entity. (Refer to...) Figure 6 , Figure 6 This is a flowchart illustrating another network slice registration method provided in an embodiment of this application. The method includes the following steps:

[0124] S601. Receive the registration request sent by the user equipment (UE).

[0125] S602. Send a registration request to the AMF unit; the registration request is used to instruct the AMF unit to obtain the subscribed slice information and default slice information from the user data management unit, and to determine the allowed slice information corresponding to the UE based on the subscribed slice information and default slice information.

[0126] S603. Receive the registration response sent by the AMF unit and send a registration response to the UE; the registration response is used to indicate that the network slice registration is successful.

[0127] The method provided in this embodiment receives a registration request sent by a user equipment (UE) and sends the registration request to an AMF unit, receives a registration response sent by the AMF unit, and sends a registration response to the UE. Since this embodiment does not require the user equipment to have the capability to identify network slice information or generate requested network slice information, the AMF unit obtains the subscribed slice information and default slice information from the user data management unit, and determines the allowed slice information corresponding to the UE based on the subscribed slice information and default slice information to complete the network slice registration. Therefore, the dependence on the user equipment is reduced.

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

[0129] In one embodiment, the registration response did not carry slice permission information.

[0130] Since this embodiment does not require the user equipment to identify or process slice information, the registration response does not need to be sent to the user equipment. Instead, a registration response indicating whether the network slice registration was successful or failed is sent to the user equipment, thereby reducing network resource overhead and improving the efficiency of network slice registration.

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

[0132] S701, the UE sends a registration request to the base station.

[0133] The registration request carries the UE's identifier and authentication parameters, but does not carry information related to network slicing.

[0134] S702, Base station selects AMF unit.

[0135] S703, The base station sends a registration request to the AMF unit.

[0136] In response to the registration request, the S704 and AMF units send an authentication request to the authentication server. The authentication request includes the user identifier and the UE's authentication parameters.

[0137] S705. In response to the authentication request, the authentication server sends an authentication request to the UDM unit.

[0138] In response to the authentication request, the S706 and UDM units send the UE's authentication parameters to the authentication server.

[0139] S707. The authentication server performs authentication on the UE based on the authentication parameters in the authentication request and the authentication parameters obtained from the UDM unit.

[0140] S708. After successful authentication, the authentication server sends an authentication response to the AMF unit.

[0141] After receiving the authentication response, the S709 and AMF units send a contract data retrieval request to the UDM unit.

[0142] The S710 and UDM units send the UE's subscription data to the AMF unit.

[0143] S711 and AMF units determine the allowed slice information corresponding to the UE based on the signed slice information and default slice information in the signed data.

[0144] The AMF unit performs network slice registration based on the allowed slice information corresponding to the UE.

[0145] The S712 and AMF units send a registration response to the base station.

[0146] S713, The base station sends a registration response to the UE.

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

[0148] 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 one or more 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.

[0149] In one embodiment, such as Figure 8 As shown, Figure 8 This is a structural block diagram of an AMF unit provided in an embodiment of this application. The device 800 includes:

[0150] The receiving module 801 is used to receive the registration request sent by the UE through the base station;

[0151] The acquisition module 802 is used to obtain the contracted slice information and default slice information from the user data management unit in response to the registration request;

[0152] The determination module 803 is used to determine the allowed slice information corresponding to the UE based on the subscribed slice information and the default slice information; the allowed slice information is used for network slice registration.

[0153] In one embodiment, the determining module 803 is specifically used to determine allowed slice information from the contracted slice information and the default slice information according to a preset slice priority rule.

[0154] In one embodiment, the determining module 803 is specifically used to determine, according to the slice priority rules, a number of allowed slices less than or equal to a preset number from the contracted slice information and the default slice information; the preset number is related to the processing capacity of the network accessed by the AMF unit.

[0155] In one embodiment, the slice priority rule includes at least one of the following:

[0156] The default slice information has a higher priority than the signed slice information;

[0157] Slice information that is used more frequently has a higher priority than slice information that is used less frequently.

[0158] In one embodiment, the acquisition module 802 includes:

[0159] The sending unit is used to send an authentication request to the authentication server in response to a registration request; the authentication request is used to instruct the authentication server to obtain the UE's authentication parameters from the user data management unit.

[0160] The acquisition unit is used to acquire the contracted slice information and default slice information from the user data management unit if an authentication response is received from the authentication server; the authentication response is the response sent by the authentication server after the authentication parameters are successfully authenticated.

[0161] In one embodiment, the acquisition unit is specifically configured to send a subscription data acquisition request to the user data management unit if an authentication response is received; and receive the UE's subscription data sent by the user data management unit based on the subscription data acquisition request; the subscription data includes subscription slice information and default slice information.

[0162] In one embodiment, the contracted slice information includes contracted network slice selection assistance information, and the default slice information includes default network slice selection assistance information.

[0163] In one embodiment, the apparatus 800 may further include a sending module for sending a registration response to the UE via a base station; the registration response is used to indicate that the network slice registration was successful.

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

[0165] In one embodiment, a communication device is provided, see [link to previous document]. Figure 9 . Figure 9 This is a schematic diagram of the structure of the user equipment provided in the embodiments of this application. Figure 9 The user equipment 900 shown includes at least one processor 901, a memory 902, at least one network interface 904, and a user interface 903. The various components in the user equipment 900 are coupled together via a bus system 905. It is understood that the bus system 905 is used to implement communication between these components. In addition to a data bus, the bus system 905 also includes a power bus, a control bus, and a status signal bus. However, for clarity, ... Figure 9 Various buses are designated as bus system 905. Additionally, this embodiment of the invention includes a transceiver 906, 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.

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

[0167] It is understood that the memory 902 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 902 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.

[0168] In some implementations, memory 902 stores elements such as executable modules or data structures, or subsets thereof, or extended sets thereof: operating system 9021 and application program 9022.

[0169] The operating system 9021 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 9022 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 9022.

[0170] In this embodiment of the invention, by calling the program or instructions stored in the memory 902, specifically the program or instructions stored in the application program 9022, the transmitter is used to send a registration request to the AMF unit; the registration request is used to instruct the AMF unit to obtain the subscribed slice information and the default slice information from the user data management unit; the receiver is used to receive the registration response sent by the AMF unit; the registration response is a response sent by the AMF unit after determining the allowed slice information corresponding to the UE based on the subscribed slice information and the default slice information, and the registration response is used to indicate that the network slice registration is successful.

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

[0172] For software implementation, the techniques described in the embodiments of the present invention can be implemented through 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 901. The memory can be implemented in processor 901 or external to processor 901.

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

[0174] In one embodiment, the registration response did not carry slice permission information.

[0175] Figure 10 This is a schematic diagram of the base station structure provided in the embodiments of this application. Figure 10 The base station 1000 shown includes at least one processor 1001, a memory 1002, and at least one network interface 1004. The various components in the base station 1000 are coupled together via a bus system 1005. It is understood that the bus system 1005 is used to implement communication between these components. In addition to a data bus, the bus system 1005 also includes a power bus, a control bus, and a status signal bus. However, for clarity, ... Figure 10Various buses are labeled as bus system 1005. Additionally, this embodiment of the invention includes a transceiver 1006, 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.

[0176] It is understood that the memory 1002 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 1002 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.

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

[0178] In this embodiment of the invention, by calling the program or instructions stored in the memory 1002, the receiver is configured to receive the registration request sent by the UE; the transmitter is configured to send the registration request to the AMF unit; the registration request is configured to instruct the AMF unit to obtain the subscription slice information and the default slice information from the user data management unit, and to determine the allowed slice information corresponding to the UE based on the subscription slice information and the default slice information.

[0179] The receiver is also used to receive the registration response sent by the AMF unit and send a registration response to the UE; the registration response is used to indicate that the network slice registration is successful.

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

[0181] 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 1001. The memory can be implemented in processor 1001 or external to processor 1001.

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

[0183] In one embodiment, the registration response did not carry slice permission information.

[0184] 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:

[0185] Receive registration requests sent by user equipment (UE) through the base station;

[0186] In response to the registration request, retrieve the contracted slice information and default slice information from the user data management unit;

[0187] Based on the contracted slice information and the default slice information, the allowed slice information corresponding to the UE is determined; the allowed slice information is used for network slice registration.

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

[0189] Based on the preset slice priority rules, the allowed slice information is determined from the signed slice information and the default slice information.

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

[0191] Based on the slice priority rules, a number of allowed slices less than or equal to a preset number are determined from the contracted slice information and the default slice information; the preset number is related to the processing capacity of the network accessed by the AMF unit.

[0192] In one embodiment, the slice priority rule includes at least one of the following:

[0193] The default slice information has a higher priority than the signed slice information;

[0194] Slice information that is used more frequently has a higher priority than slice information that is used less frequently.

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

[0196] In response to the registration request, an authentication request is sent to the authentication server; the authentication request is used to instruct the authentication server to obtain the UE's authentication parameters from the user data management unit.

[0197] If an authentication response is received from the authentication server, the contracted slice information and default slice information are obtained from the user data management unit; the authentication response is the response sent by the authentication server after the authentication parameters are successfully authenticated.

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

[0199] If an authentication response is received, a subscription data acquisition request is sent to the user data management unit; the UE's subscription data is received from the user data management unit based on the subscription data acquisition request; the subscription data includes subscription slice information and default slice information.

[0200] In one embodiment, the contracted slice information includes contracted network slice selection assistance information, and the default slice information includes default network slice selection assistance information.

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

[0202] The base station sends a registration response to the UE; the registration response indicates that the network slice registration was successful.

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

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

[0205] Receive registration requests sent by user equipment (UE) through the base station;

[0206] In response to the registration request, retrieve the contracted slice information and default slice information from the user data management unit;

[0207] Based on the contracted slice information and the default slice information, the allowed slice information corresponding to the UE is determined; the allowed slice information is used for network slice registration.

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

[0209] Based on the preset slice priority rules, the allowed slice information is determined from the signed slice information and the default slice information.

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

[0211] Based on the slice priority rules, a number of allowed slices less than or equal to a preset number are determined from the contracted slice information and the default slice information; the preset number is related to the processing capacity of the network accessed by the AMF unit.

[0212] In one embodiment, the slice priority rule includes at least one of the following:

[0213] The default slice information has a higher priority than the signed slice information;

[0214] Slice information that is used more frequently has a higher priority than slice information that is used less frequently.

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

[0216] In response to the registration request, an authentication request is sent to the authentication server; the authentication request is used to instruct the authentication server to obtain the UE's authentication parameters from the user data management unit.

[0217] If an authentication response is received from the authentication server, the contracted slice information and default slice information are obtained from the user data management unit; the authentication response is the response sent by the authentication server after the authentication parameters are successfully authenticated.

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

[0219] If an authentication response is received, a subscription data acquisition request is sent to the user data management unit; the UE's subscription data is received from the user data management unit based on the subscription data acquisition request; the subscription data includes subscription slice information and default slice information.

[0220] In one embodiment, the contracted slice information includes contracted network slice selection assistance information, and the default slice information includes default network slice selection assistance information.

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

[0222] The base station sends a registration response to the UE; the registration response indicates that the network slice registration was successful.

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

[0224] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

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

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

[0227] 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 is applied to the Access and Mobility Management Function (AMF) unit, and the method includes: Receive registration requests sent by user equipment (UE) through the base station; In response to the registration request, the UE obtains the subscribed slice information and the default slice information from the user data management unit; the default slice information is the identifier of any one of the multiple network slices subscribed to by the UE, and the subscribed slice information refers to the slice information other than the default slice information among the multiple network slice information subscribed to by the UE. Based on the subscribed slice information and the default slice information, the allowed slice information corresponding to the UE is determined; the allowed slice information is used for network slice registration. The determination of the allowed slice information corresponding to the UE based on the subscribed slice information and the default slice information includes: According to the preset slice priority rules, the allowed slice information is determined from the signed slice information and the default slice information; The slice priority rule includes at least one of the following: The default slice information has a higher priority than the signed slice information; Slice information that is used more frequently has a higher priority than slice information that is used less frequently. According to preset slice priority rules, the allowed slice information is determined from the signed slice information and the default slice information, including: According to the slice priority rule, a preset number of allowed slice information is determined from the signed slice information and the default slice information; the preset number is related to the processing capacity of the network accessed by the AMF unit, and the preset number is less than or equal to the processing capacity of the network accessed by the AMF unit.

2. The method according to claim 1, characterized in that, The step of retrieving the contracted slice information and default slice information from the user data management unit in response to the registration request includes: In response to the registration request, an authentication request is sent to the authentication server; the authentication request is used to instruct the authentication server to obtain the authentication parameters of the UE from the user data management unit; If an authentication response is received from the authentication server, the contracted slice information and default slice information are obtained from the user data management unit; the authentication response is the response sent by the authentication server after the authentication parameters are successfully authenticated.

3. The method according to claim 2, characterized in that, If an authentication response is received from the authentication server, the contracted slice information and default slice information are retrieved from the user data management unit, including: If the authentication response is received, a contract data acquisition request is sent to the user data management unit; The user data management unit receives the UE's subscription data sent based on the subscription data acquisition request; the subscription data includes the subscription slice information and the default slice information.

4. The method according to claim 1, characterized in that, The contracted slice information includes contracted network slice selection auxiliary information, and the default slice information includes default network slice selection auxiliary information.

5. The method according to claim 1, characterized in that, The method further includes: The base station sends a registration response to the UE; the registration response indicates that the network slice registration was successful.

6. The method according to claim 1, characterized in that, The registration request did not include information related to network slices.

7. A network slice registration method, characterized in that, The method is applied to a user equipment (UE), and the method includes: A registration request is sent to the AMF unit; the registration request is used to instruct the AMF unit to obtain the subscription slice information and the default slice information from the user data management unit; the default slice information is the identifier of any one of the multiple network slices subscribed to by the UE, and the subscription slice information refers to the slice information other than the default slice information among the multiple network slice information subscribed to by the UE. The system receives a registration response sent by the AMF unit. The registration response is a response sent by the AMF unit after determining the allowed slice information corresponding to the UE based on the subscribed slice information and the default slice information. The registration response is used to indicate that the network slice registration is successful. The determination of the allowed slice information corresponding to the UE based on the subscribed slice information and the default slice information includes: According to the preset slice priority rules, the allowed slice information is determined from the signed slice information and the default slice information; The slice priority rule includes at least one of the following: The default slice information has a higher priority than the signed slice information; Slice information that is used more frequently has a higher priority than slice information that is used less frequently. According to preset slice priority rules, the allowed slice information is determined from the signed slice information and the default slice information, including: According to the slice priority rule, a preset number of allowed slice information is determined from the signed slice information and the default slice information; the preset number is related to the processing capacity of the network accessed by the AMF unit, and the preset number is less than or equal to the processing capacity of the network accessed by the AMF unit.

8. The method according to claim 7, characterized in that, The registration request did not include information related to network slices.

9. The method according to claim 7 or 8, characterized in that, The registration response did not carry the allowed slicing information.

10. A network slice registration method, characterized in that, The method is applied to a base station, and the method includes: Receive the registration request sent by the UE; The registration request is sent to the AMF unit; the registration request is used to instruct the AMF unit to obtain the subscribed slice information and the default slice information from the user data management unit, and to determine the allowed slice information corresponding to the UE based on the subscribed slice information and the default slice information; the default slice information is the identifier of any one of the multiple network slices subscribed to by the UE, and the subscribed slice information refers to the slice information other than the default slice information among the multiple network slice information subscribed to by the UE. The system receives the registration response sent by the AMF unit and sends the registration response to the UE; the registration response indicates that the network slice registration was successful. The determination of the allowed slice information corresponding to the UE based on the subscribed slice information and the default slice information includes: According to the preset slice priority rules, the allowed slice information is determined from the signed slice information and the default slice information; The slice priority rule includes at least one of the following: The default slice information has a higher priority than the signed slice information; Slice information that is used more frequently has a higher priority than slice information that is used less frequently. According to preset slice priority rules, the allowed slice information is determined from the signed slice information and the default slice information, including: According to the slice priority rule, a preset number of allowed slice information is determined from the signed slice information and the default slice information; the preset number is related to the processing capacity of the network accessed by the AMF unit, and the preset number is less than or equal to the processing capacity of the network accessed by the AMF unit.

11. The method according to claim 10, characterized in that, The registration request did not include information related to network slices.

12. The method according to claim 10 or 11, characterized in that, The registration response did not carry the allowed slicing information.

13. An AMF unit, characterized in that, The AMF unit includes: The receiving module is used to receive the registration request sent by the UE through the base station; The acquisition module is used to acquire, in response to the registration request, subscription slice information and default slice information from the user data management unit; the default slice information is the identifier of any one of the multiple network slices subscribed to by the UE, and the subscription slice information refers to the slice information other than the default slice information among the multiple network slice information subscribed to by the UE. The determining module is used to determine the allowed slice information corresponding to the UE based on the subscribed slice information and the default slice information; the allowed slice information is used for network slice registration. The determination of the allowed slice information corresponding to the UE based on the subscribed slice information and the default slice information includes: According to the preset slice priority rules, the allowed slice information is determined from the signed slice information and the default slice information; The slice priority rule includes at least one of the following: The default slice information has a higher priority than the signed slice information; Slice information that is used more frequently has a higher priority than slice information that is used less frequently. According to preset slice priority rules, the allowed slice information is determined from the signed slice information and the default slice information, including: According to the slice priority rule, a preset number of allowed slice information is determined from the signed slice information and the default slice information; the preset number is related to the processing capacity of the network accessed by the AMF unit, and the preset number is less than or equal to the processing capacity of the network accessed by the AMF unit.

14. A user equipment, characterized in that, The user equipment includes: A transmitter is used to send a registration request to the AMF unit; the registration request is used to instruct the AMF unit to obtain subscription slice information and default slice information from the user data management unit; the default slice information is the identifier of any one of the multiple network slices subscribed to by the UE, and the subscription slice information refers to the slice information other than the default slice information among the multiple network slice information subscribed to by the UE. A receiver is used to receive a registration response sent by the AMF unit; the registration response is a response sent by the AMF unit after determining the allowed slice information corresponding to the user equipment based on the subscribed slice information and the default slice information, and the registration response is used to indicate that the network slice registration is successful; The determination of the allowed slice information corresponding to the user equipment based on the subscribed slice information and the default slice information includes: According to the preset slice priority rules, the allowed slice information is determined from the signed slice information and the default slice information; The slice priority rule includes at least one of the following: The default slice information has a higher priority than the signed slice information; Slice information that is used more frequently has a higher priority than slice information that is used less frequently. According to preset slice priority rules, the allowed slice information is determined from the signed slice information and the default slice information, including: According to the slice priority rule, a preset number of allowed slice information is determined from the signed slice information and the default slice information; the preset number is related to the processing capacity of the network accessed by the AMF unit, and the preset number is less than or equal to the processing capacity of the network accessed by the AMF unit.

15. A base station, characterized in that, The base station includes: Receiver, used to receive registration requests sent by the UE; A transmitter is used to send the registration request to the AMF unit; the registration request is used to instruct the AMF unit to obtain the subscribed slice information and the default slice information from the user data management unit, and to determine the allowed slice information corresponding to the UE based on the subscribed slice information and the default slice information; the default slice information is the identifier of any one of the multiple network slices subscribed to by the UE, and the subscribed slice information refers to the slice information other than the default slice information among the multiple network slice information subscribed to by the UE; The receiver is also configured to receive the registration response sent by the AMF unit and send the registration response to the UE; the registration response is used to indicate that the network slice registration was successful. The determination of the allowed slice information corresponding to the UE based on the subscribed slice information and the default slice information includes: According to the preset slice priority rules, the allowed slice information is determined from the signed slice information and the default slice information; The slice priority rule includes at least one of the following: The default slice information has a higher priority than the signed slice information; Slice information that is used more frequently has a higher priority than slice information that is used less frequently. According to preset slice priority rules, the allowed slice information is determined from the signed slice information and the default slice information, including: According to the slice priority rule, a preset number of allowed slice information is determined from the signed slice information and the default slice information; the preset number is related to the processing capacity of the network accessed by the AMF unit, and the preset number is less than or equal to the processing capacity of the network accessed by the AMF unit.

16. 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 12.

17. 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 12.

Images