Registration method and device of network slice, equipment and storage medium

Abstract

The invention relates to the technical field of communication, in particular to a network slice registration method and device, equipment and a storage medium, and the method comprises the steps: detecting a tracking area where terminal equipment is located currently; when the detected tracking area is not the tracking area recorded in the allowed network slice list, sending a mobility registration request carrying a first request network slice to core network equipment, the first request network slice comprises a network slice of which the rejection reason is not in the tracking area in the rejection network slice list and an allowed network slice in the allowed network slice list; receiving a first registration receiving message which is returned by the core network equipment and carries a first allowed network slice, a first rejected network slice and a rejection reason of the first allowed network slice and the first rejected network slice in the first request network slice; and updating the rejected network slice list and the allowed network slice list. The technical scheme can improve the registration efficiency of the network slice, and is mainly used for network slice registration of the terminal equipment.

Description

Technical Field

[0001] The present disclosure relates to the field of communication technologies, and particularly to a method, apparatus, device, and storage medium for registering network slices. Background Art

[0002] In order to meet the diverse service requirements of users, the Network Slice Selection Assistance Information (NSSAI) technology has emerged. Through the network slice technology, multiple dedicated, virtualized, and isolated logical networks can be constructed on a common physical network to meet the different differential requirements of users for network capabilities.

[0003] In the prior art, different Tracking Areas (TAs) can support different network slices. When the TA of the terminal device changes, the Access and Mobility Management Function (AMF) can send a UE Configuration Update Command to the terminal device to notify the terminal device to re-initiate network registration and request the allowable network slices, which results in low registration efficiency of the network slices of the terminal. Summary of the Invention

[0004] To solve the problems in the related art, embodiments of the present disclosure provide a method, apparatus, device, and storage medium for registering network slices.

[0005] In a first aspect, embodiments of the present disclosure provide a method for registering network slices, which is applied to a terminal device. The method includes:

[0006] Detect the tracking area where the terminal device is currently located;

[0007] When the tracking area is not the tracking area recorded in the allowed network slice list, send a mobility registration request to the core network device. The mobility registration request carries a first requested network slice of the terminal device. The first requested network slice includes a rejected network slice selected from the rejected network slice list and / or an allowed network slice selected from the allowed network slice list. Among them, the rejected network slice list records the rejected network slices and their rejection reasons, and the selected rejected network slice is the rejected network slice whose rejection reason is not in the tracking area. The allowed network slice list records the allowed network slices and their corresponding tracking areas;

[0008] Receive a first registration reception message returned by the core network device in response to the mobility registration request, where the first registration reception message carries the first allowed network slice, the first rejected network slice, and the rejection reason in the first requested network slice;

[0009] Update the first rejected network slice and its rejection reason to the rejected network slice list, and correspondingly update the first allowed network slice and the tracking area where the terminal device is currently located in the allowed network slice list.

[0010] In a possible implementation manner, the method further includes:

[0011] When the terminal device initiates an initial registration, send an initial registration request to the core network device, where the initial registration request carries a second requested network slice, and the second requested network slice is a network slice selected from the configured network slices;

[0012] Receive a second registration reception message returned by the core network device in response to the initial registration request, where the second registration reception message carries the second allowed network slice, the second rejected network slice, and the rejection reason in the second requested network slice;

[0013] Update the second rejected network slice and its rejection reason to the rejected network slice list, and correspondingly update the second allowed network slice and the tracking area where the terminal device is currently located in the allowed network slice list.

[0014] In a possible implementation manner, the method further includes:

[0015] Delete the rejected network slice in the first requested network slice from the rejected network slice list.

[0016] In a possible implementation manner, the deleting the rejected network slice in the first requested network slice from the rejected network slice list includes:

[0017] When the rejected network slice in the first requested network slice is the first allowed network slice, delete the rejected network slice in the first requested network slice from the rejected network slice list.

[0018] In a possible implementation manner, the detecting the tracking area where the terminal device is currently located includes:

[0019] Receive a broadcast message from the base station, where the broadcast message carries the tracking area code of the tracking area where the terminal device is currently located;

[0020] Determine the tracking area where the terminal device is currently located based on the tracking area code.

[0021] In a second aspect, an embodiment of the present disclosure provides a method for registering a network slice, which is applied to a core network device. The method includes:

[0022] Receive a mobility registration request sent by a terminal device. The mobility registration request carries a first requested network slice of the terminal device. The first requested network slice includes a rejected network slice selected from a rejected network slice list and / or an allowed network slice selected from an allowed network slice list. Among them, the rejected network slice list records the rejected network slice and its rejection reason. The selected rejected network slice is a rejected network slice whose rejection reason is not in the tracking area. The allowed network slice list records the allowed network slice and its corresponding tracking area.

[0023] In response to the mobility registration request, determine the first allowed network slice, the first rejected network slice and its rejection reason in the first requested network slice.

[0024] Return a first registration acceptance message to the terminal device. The first registration acceptance message carries the first allowed network slice, the first rejected network slice and its rejection reason in the first requested network slice.

[0025] In a third aspect, an embodiment of the present disclosure provides a device for registering a network slice, which is applied to a terminal device. The device includes:

[0026] A detection module configured to detect the tracking area where the terminal device is currently located.

[0027] A mobile registration request module configured to send a mobility registration request to a core network device when the tracking area is not the tracking area recorded in the allowed network slice list. The mobility registration request carries a first requested network slice of the terminal device. The first requested network slice includes a rejected network slice selected from a rejected network slice list and / or an allowed network slice selected from the allowed network slice list. Among them, the rejected network slice list records the rejected network slice and its rejection reason. The selected rejected network slice is a rejected network slice whose rejection reason is not in the tracking area. The allowed network slice list records the allowed network slice and its corresponding tracking area.

[0028] A first registration acceptance module configured to receive a first registration acceptance message returned by the core network device in response to the mobility registration request. The first registration acceptance message carries the first allowed network slice, the first rejected network slice and its rejection reason in the first requested network slice.

[0029] A first update module, configured to update the first rejected network slice and its rejection reason to the rejected network slice list, and correspondingly update the first allowed network slice and the tracking area where the terminal device is currently located in the allowed network slice list.

[0030] In a possible implementation manner, the apparatus further includes:

[0031] An initial registration request module, configured to send an initial registration request to the core network device when the terminal device initiates an initial registration. The initial registration request carries a second requested network slice, and the second requested network slice is a configured network slice.

[0032] A second registration reception module, configured to receive a second registration reception message returned by the core network device in response to the initial registration request. The second registration reception message carries a second allowed network slice, a second rejected network slice, and its rejection reason in the second requested network slice.

[0033] A second update module, configured to update the second rejected network slice and its rejection reason to the rejected network slice list, and correspondingly update the second allowed network slice and the tracking area where the terminal device is currently located in the allowed network slice list.

[0034] In a possible implementation manner, the apparatus further includes:

[0035] A deletion module, configured to delete the rejected network slice in the first requested network slice from the rejected network slice list.

[0036] In a possible implementation manner, the deletion module is configured to:

[0037] When the rejected network slice in the first requested network slice is the first allowed network slice, delete the rejected network slice in the first requested network slice from the rejected network slice list.

[0038] In a possible implementation manner, the detection module is configured to:

[0039] Receive a broadcast message from a base station, where the broadcast message carries a tracking area code of the tracking area where the terminal device is currently located.

[0040] Determine the tracking area where the terminal device is currently located based on the tracking area code.

[0041] Fourthly, an embodiment of the present disclosure provides a registration device for network slicing, which is applied to a core network device. The device includes:

[0042] A request receiving module, configured to receive a mobility registration request sent by a terminal device. The mobility registration request carries a first requested network slice of the terminal device. The first requested network slice includes a rejected network slice selected from a rejected network slice list and / or an allowed network slice selected from an allowed network slice list. Among them, the rejected network slice list records the rejected network slice and its rejection reason. The selected rejected network slice is the rejected network slice whose rejection reason is not in the tracking area. The allowed network slice list records the allowed network slice and its corresponding tracking area.

[0043] A slice determination module, configured to determine a first allowed network slice, a first rejected network slice and its rejection reason in the first requested network slice in response to the mobility registration request.

[0044] A sending module, configured to return a first registration received message to the terminal device. The first registration received message carries the first allowed network slice, the first rejected network slice and its rejection reason in the first requested network slice.

[0045] Fifthly, an embodiment of the present disclosure provides a terminal device, including a memory and a processor. The memory is used to store one or more computer instructions. Among them, the one or more computer instructions are executed by the processor to implement the method according to any one of the first aspect.

[0046] Sixthly, an embodiment of the present disclosure provides a core network device, including a memory and a processor. The memory is used to store one or more computer instructions. Among them, the one or more computer instructions are executed by the processor to implement the method according to the second aspect.

[0047] Seventhly, an embodiment of the present disclosure provides a readable storage medium, on which computer instructions are stored. When the computer instructions are executed by a processor, the method according to any one of the first aspect or the second aspect is implemented.

[0048] According to the technical solution provided by the embodiments of the present disclosure, the terminal device can autonomously detect the tracking area where the terminal device is currently located, and when the detected tracking area is not the tracking area recorded in the allowed network slice list, send a mobility registration request to the core network device. The mobility registration request carries a first requested network slice of the terminal device. The first requested network slice includes a rejected network slice selected from the rejected network slice list and / or an allowed network slice selected from the allowed network slice list. Among them, the rejected network slice list records the rejected network slice and its rejection reason, and the selected rejected network slice is the rejected network slice whose rejection reason is not in the tracking area. The allowed network slice list records the allowed network slice and its corresponding tracking area. In this way, when the terminal needs to re-register the network slice due to movement, it can autonomously select a requested network slice from the network slices not in the current tracking area and the network slices in the allowed network slice list to send a mobility registration request, which speeds up the registration speed and improves the registration efficiency. Moreover, the rejected network slice whose rejection reason is not in the tracking area can be selected as the requested network slice to ensure that the rejected network slice can be used and avoid waste of the rejected network slice.

[0049] In addition, after the terminal device receives the first registration acceptance message returned by the core network device in response to the mobility registration request, it can update the rejected network slice and its rejection reason in the rejected network slice list according to the first allowed network slice, the first rejected network slice and its rejection reason in the first requested network slice carried in the first registration acceptance message, and update the first allowed network slice and the tracking area where the terminal device is currently located correspondingly in the allowed network slice list. In this way, the rejected network slice list and the allowed network slice list are updated and maintained to ensure that the terminal can autonomously determine whether the tracking area where the terminal device is currently located is in the tracking area recorded in the allowed network slice list, and autonomously send a mobility registration request from the network slices whose rejection reason in the rejected network slice list is not in the tracking area and the network slices in the allowed network slice list.

[0050] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the present disclosure. Description of the Drawings

[0051] In combination with the drawings, through the following detailed description of non-limiting embodiments, other features, objects and advantages of the present disclosure will become more obvious. In the drawings:

[0052] Figure 1 A flowchart of a method for registering a network slice applied to a terminal device provided by an embodiment of the present disclosure is shown.

[0053] Figure 2 The flowchart showing the registration method of the network slice applied to the core network device provided by the embodiments of the present disclosure.

[0054] Figure 3 The schematic diagram showing the interaction process of the registration method of the network slice provided by the embodiments of the present disclosure.

[0055] Figure 4 The structural block diagram showing a registration device of the network slice applied to a terminal device provided by the embodiments of the present disclosure.

[0056] Figure 5 The structural block diagram showing a registration device of the network slice applied to a core network device provided by the embodiments of the present disclosure.

[0057] Figure 6 The structural block diagram showing an electronic device according to an embodiment of the present disclosure.

[0058] Figure 7 The structural schematic diagram showing a computer system suitable for implementing the method of the embodiments of the present disclosure. Detailed implementation manners

[0059] Hereinafter, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings so that those skilled in the art can easily implement them. In addition, for the sake of clarity, parts irrelevant to the description of the exemplary embodiments are omitted in the drawings.

[0060] In the present disclosure, it should be understood that terms such as "including" or "having" are intended to indicate the presence of features, numbers, steps, actions, components, parts, or combinations thereof disclosed in this specification, and are not intended to exclude the possibility of the presence or addition of one or more other features, numbers, steps, actions, components, parts, or combinations thereof.

[0061] In addition, it should be noted that, without conflict, the embodiments in the present disclosure and the features in the embodiments can be combined with each other. Hereinafter, the present disclosure will be described in detail with reference to the accompanying drawings and in combination with the embodiments.

[0062] Figure 1 The flowchart showing the registration method of the network slice applied to a terminal device provided by the embodiments of the present disclosure. As Figure 1 shown, the registration method of the network slice includes the following steps S101 - S104:

[0063] In step S101, detect the tracking area where the terminal device is currently located;

[0064] In step S102, when the tracking area is not the tracking area recorded in the allowed network slice list, send a mobility registration request to the core network device;

[0065] In step S103, a first registration reception message returned by the core network device in response to the mobility registration request is received. The first registration reception message carries the first allowed network slice, the first denied network slice, and the reason for rejection in the first requested network slice.

[0066] In step S104, the first denied network slice and the reason for rejection are updated to the denied network slice list, and the first allowed network slice and the tracking area where the terminal device is currently located are correspondingly updated in the allowed network slice list.

[0067] In a possible implementation, the registration method of this network slice can be applied to a terminal device capable of performing network slice registration. The terminal device can be a station (STAION, ST) in a WLAN (Wireless Local Area Networks), a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication function, a computing device or other processing devices connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR (New Radio) network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0068] In a possible implementation, the following several network slices can be recorded in the terminal device:

[0069] Subscribed S-NSSAIs (subscribed network slices): Network slices provided by the operator subscribed by the terminal device, which may include one or more network slices;

[0070] Default Configured NSSAI (default configured network slice): According to the operator's policy, one or more Subscribed S-NSSAIs may be set as the Default Configured NSSAI;

[0071] Configured NSSAI (Configured Network Slice): The network slice configured by the network for the terminal device to use. The terminal device maintains a list of configured network slices, and the configured network slices that the terminal device can use are recorded in this list of configured network slices;

[0072] Request NSSAI (Requested Network Slice): The network slice that the terminal device requests to use this time and carries in the registration request message;

[0073] Allowed NSSAI (Allowed Network Slice): Among the requested network slices of the terminal device, the network slices that are allowed to be used. After receiving the registration request message, the core network device carries them in the registration acceptance message and returns them to the terminal device; The terminal device maintains a list of allowed network slices, and the allowed network slices that the terminal device is currently allowed to use are recorded in this list of allowed network slices;

[0074] Rejected NSSAI (Rejected Network Slice): Among the requested network slices of the terminal device, the network slices that are not allowed to be used. After receiving the registration request message, the core network device carries them in the registration acceptance message and returns them to the terminal device; The terminal device maintains a list of rejected network slices, and the rejected network slices that the terminal device is currently not allowed to use are recorded in this list of rejected network slices;

[0075] In a possible implementation, different tracking areas may support different network slices. One tracking area may also support one or more network slices, and one network slice may be available in one or more tracking areas.

[0076] In a possible implementation, the list of allowed network slices maintained by the terminal device records the currently allowed network slices and their corresponding tracking areas, and the list of rejected network slices records the currently rejected network slices and the reasons for rejection.

[0077] In a possible implementation, the terminal device can autonomously detect the tracking area where the terminal device is currently located. When the detected tracking area is not the tracking area recorded in the list of allowed network slices, the terminal device can send a mobility registration request to the core network device. The mobility registration request carries the first requested network slice of the terminal device, and is used to request the core network device to determine which network slices in the first requested network slice are allowed to be used in the tracking area after the change of the terminal device.

[0078] In a possible implementation manner, the first requested network slice includes a rejected network slice selected from the list of rejected network slices and / or an allowed network slice selected from the list of allowed network slices. Generally, the number of selected requested network slices does not exceed 8. Here, the selected rejected network slice is a rejected network slice whose rejection reason is not within the tracking area. It was previously rejected because it was not within the previous tracking area. Now, the tracking area where the terminal device is currently located has changed and is no longer within the previous tracking area. Therefore, the network slice whose rejection reason is not within the tracking area can be selected as the requested network slice to ensure that the rejected network slice can be used and avoid waste of the rejected network slice. The selected allowed network slice here is randomly selected from the list of allowed network slices. The first requested network slice can be preferentially selected from the list of rejected network slices, or preferentially selected from the list of allowed network slices, or selected from the list of rejected network slices and the list of allowed network slices respectively, and there is no limitation here.

[0079] In a possible implementation, the core network device may be an AMF (Access and Mobility Management Function). After receiving the mobility registration request, the AMF may request the Subscribed S-NSSAIs of the terminal device from the UDM (Unified Data Management). The AMF may also interact with the base station through the N2 interface to obtain the tracking area where the terminal device is currently located and the network slices supported under each tracking area, and determine whether to allow the registration of the first requested network slice carried in the mobility registration request based on this. For example, when a certain first requested network slice is the Subscribed S-NSSAIs of the terminal device and is a network slice supported by the tracking area where the terminal device is currently located, it may be determined that the first requested network slice is the first allowed network slice allowed to be registered. If a certain first requested network slice is the Subscribed S-NSSAIs of the terminal device but is not a network slice supported by the tracking area where the terminal device is currently located, it may be determined that the first requested network slice is the first rejected network slice not allowed to be registered and the rejection reason is not in the tracking area. Only the slices allowed to be registered can proceed with PDU (Protocol Data Unit) session establishment later. It should be noted here that the rejection reason may include not only not being in the tracking area, but also not being in the PLMN (for example, when a certain first requested network slice is not the Subscribed S-NSSAIs of the terminal device, it may be determined that the first requested network slice is the first rejected network slice not allowed to be registered and the rejection reason is not in the PLMN) or authentication failure, etc.

[0080] In a possible implementation, the core network device may carry the first allowed network slice, the first rejected network slice and its rejection reason in the first registration reception message and return them to the terminal device.

[0081] In a possible implementation, after receiving the first registration reception message, the terminal device may update the first rejected network slice and its rejection reason to the rejected network slice list, and correspondingly update the first allowed network slice and the tracking area where the terminal device is currently located in the allowed network slice list, so as to realize the update and maintenance of the allowed network slice list and the rejected network slice list. In this way, subsequently, the terminal device can continue to select the requested network slice for network slice registration from the network slices in the rejected network slice list with the rejection reason of not being in the tracking area and the network slices in the allowed network slice list.

[0082] In this embodiment, the terminal device can autonomously detect the tracking area where the terminal device is currently located. When the detected tracking area is not the tracking area recorded in the allowed network slice list, the terminal device sends a mobility registration request to the core network device. The mobility registration request carries a first requested network slice of the terminal device. The first requested network slice includes a rejected network slice selected from the rejected network slice list and / or an allowed network slice selected from the allowed network slice list. Among them, the rejected network slice list records the rejected network slice and its rejection reason. The selected rejected network slice is a rejected network slice whose rejection reason is not in the tracking area. The allowed network slice list records the allowed network slice and its corresponding tracking area. In this way, when the terminal needs to re-register the network slice due to movement, it can autonomously select a requested network slice from the network slices not in the current tracking area and the network slices in the allowed network slice list to send a mobility registration request, which speeds up the registration speed and improves the registration efficiency. Moreover, the rejected network slice whose rejection reason is not in the tracking area can be selected as the requested network slice to ensure that the rejected network slice can be used and avoid waste of the rejected network slice.

[0083] In addition, after the terminal device receives the first registration acceptance message returned by the core network device in response to the mobility registration request, it can update the rejected network slice and its rejection reason in the first requested network slice carried in the first registration acceptance message to the rejected network slice list, and update the allowed network slice in the first requested network slice and the tracking area where the terminal device is currently located correspondingly in the allowed network slice list. In this way, the rejected network slice list and the allowed network slice list are updated and maintained to ensure that the terminal can autonomously determine whether the tracking area where the terminal device is currently located is in the tracking area recorded in the allowed network slice list, and can autonomously send a mobility registration request by selecting a requested network slice from the network slices in the rejected network slice list whose rejection reason is not in the tracking area and the network slices in the allowed network slice list.

[0084] In a possible implementation manner, the method further includes:

[0085] When the terminal device initiates an initial registration, it sends an initial registration request to the core network device. The initial registration request carries a second requested network slice, and the second requested network slice is a network slice selected from the configured network slices.

[0086] Receive a second registration reception message returned by the core network device in response to the initial registration request. The second registration reception message carries a second allowed network slice, a second rejected network slice, and the reason for rejection thereof.

[0087] Update the second rejected network slice and the reason for rejection thereof to the rejected network slice list, and correspondingly update the second allowed network slice and the tracking area where the terminal device is currently located in the allowed network slice list.

[0088] In this embodiment, when the terminal device is powered on, it will initiate an initial registration and send an initial registration request to the core network device. Since it is an initial registration, both the allowed network slice list and the rejected network slice list are empty. At this time, the second requested network slice carried in the initial registration request is a network slice selected from the configured network slices. There are two cases. One case is that the configured network slice list is empty. At this time, the second requested network slice is also empty. The other case is that there are pre-configured network slices in the configured network slice list. At this time, the second requested network slice is the network slice selected from the configured network slice list.

[0089] In this embodiment, after receiving the initial registration request, the core network device can request the Subscribed S-NSSAIs of the terminal device from the UDM. The core network device can also interact with the base station through the N2 interface to obtain the tracking area where the terminal device is currently located and the network slices supported under each tracking area from the base station. If the second requested network slice is empty, the second allowed network slice that is allowed to be registered, the second rejected network slice that is not allowed to be registered, and the reason for rejection thereof can be determined from the Subscribed S-NSSAIs of the terminal device. If the second requested network slice is not empty, the second allowed network slice that is allowed to be registered, the second rejected network slice that is not allowed to be registered, and the reason for rejection thereof can be determined from the second requested network slice. Only the slices allowed to be registered can perform PDU session establishment subsequently. The reasons for rejection include the following three: not in the tracking area, not in the PLMN, and authentication failure.

[0090] In this embodiment, the core network device can carry the second allowed network slice, the first rejected network slice, and the reason for rejection thereof in the second requested network slice in the second registration reception message and return it to the terminal device.

[0091] In this embodiment, after receiving the second registration reception message, the terminal device may update the second rejected network slice and its rejection reason to the rejected network slice list, and correspondingly update the second allowed network slice and the tracking area where the terminal device is currently located in the allowed network slice list. In this way, the initial allowed network slice list and rejected network slice list are established, and subsequent updates and maintenance of the allowed network slice list and rejected network slice list can be performed according to the processes described in steps S101 to S104 above.

[0092] In a possible embodiment, the method further includes:

[0093] Delete the rejected network slice in the first requested network slice from the rejected network slice list.

[0094] In this embodiment, during this registration, the core network device will re-determine whether the rejected network slice in the first requested network slice with the rejection reason of not being in the tracking area is allowed. Therefore, after determining the first requested network slice, the rejected network slice in the first requested network slice with the rejection reason of not being in the tracking area can be deleted from the rejected network slice list to avoid duplicate records.

[0095] In a possible embodiment, the deleting the rejected network slice in the first requested network slice from the rejected network slice list includes:

[0096] When the rejected network slice in the first requested network slice is the first allowed network slice, delete the rejected network slice in the first requested network slice from the rejected network slice list.

[0097] In this embodiment, if the rejected network slice of the first requested network slice is identified by the core network device as the first allowed network slice, the rejected network slice in the first requested network slice with the rejection reason of not being in the tracking area can be deleted from the rejected network slice list. If the rejected network slice of the first requested network slice is identified by the core network device as the first rejected network slice again and the rejection reason is not being in the tracking area, the rejected network slice may not be deleted from the rejected network slice list.

[0098] In a possible embodiment, the detecting the tracking area where the terminal device is currently located includes:

[0099] Receive a broadcast message from the base station, where the broadcast message carries a tracking area code of the tracking area where the terminal device is currently located;

[0100] Determine the tracking area where the terminal device is currently located based on the tracking area code.

[0101] In this embodiment, the base station periodically broadcasts this broadcast message to the terminal devices in its own cell. The Tracking Area Code (TAC) of the tracking area where the terminal device is currently located is included in the Cell Access Related Info (cell access related information) in the SIB1 (System Information Block #1) of this broadcast message. Based on this tracking area code, the terminal device can determine the tracking area where the terminal device is currently located.

[0102] Figure 2 The flowchart of the registration method of the network slice applied to the core network device provided by the embodiments of the present disclosure is shown. As Figure 2 shown, the registration method of the network slice includes the following steps S201 - S203:

[0103] In step S201, receive a mobility registration request sent by a terminal device, where the first requested network slice of the terminal device is carried in the mobility registration request;

[0104] In step S202, in response to the mobility registration request, determine the first allowed network slice, the first rejected network slice in the first requested network slice, and the reason for rejection;

[0105] In step S203, return a first registration acceptance message to the terminal device, where the first allowed network slice, the first rejected network slice in the first requested network slice, and the reason for rejection are carried in the first registration acceptance message.

[0106] In a possible implementation manner, the registration method of this network slice can be applied to a core network device capable of performing the registration of the network slice, and this core network device can be an AMF.

[0107] In a possible implementation manner, different tracking areas can support different network slices, one tracking area can also support one or more network slices, and one network slice can be available under one or more tracking areas. The allowed network slice list maintained by the terminal device records the currently allowed network slices and their corresponding tracking areas, and the rejected network slice list records the rejected network slices and the reasons for rejection.

[0108] In a possible implementation manner, the terminal device can autonomously detect the tracking area where the terminal device is currently located. When the detected tracking area is not the tracking area recorded in the allowed network slice list, the terminal device can send a mobility registration request to the core network device. The mobility registration request carries the first requested network slice of the terminal device, and is used to request the core network device to determine which network slices in the first requested network slice are allowed to be used in the tracking area after the change of the terminal device.

[0109] In a possible implementation manner, the first requested network slice includes the rejected network slices selected from the rejected network slice list and / or the allowed network slices selected from the allowed network slice list. Generally, the number of selected requested network slices does not exceed 8. The rejected network slices selected here are the network slices whose rejection reason is not in the tracking area. They were previously rejected because they were not in the previous tracking area. Now the tracking area where the terminal device is currently located has changed and is no longer in the previous tracking area. Therefore, the network slices whose rejection reason is not in the tracking area can be selected as the requested network slices to ensure that the rejected network slices can be used and avoid waste of the rejected network slices. The allowed network slices selected here are randomly selected from the allowed network slice list. The first requested network slice can be preferentially selected from the rejected network slice list, or can be preferentially selected from the allowed network slice list, or can be selected from the rejected network slice list and the allowed network slice list respectively, and no limitation is made here.

[0110] In a possible implementation, after receiving the mobility registration request, the core network device may request the Subscribed S-NSSAIs of the terminal device from the UDM. The AMF may also interact with the base station through the N2 interface to obtain the tracking area where the terminal device is currently located and the network slices supported under each tracking area, and determine whether to allow the registration of the first requested network slice carried in the mobility registration request based on this. For example, when a certain first requested network slice is the Subscribed S-NSSAIs of the terminal device and is a network slice supported by the tracking area where the terminal device is currently located, it may be determined that the first requested network slice is the first allowed network slice allowed to be registered. If a certain first requested network slice is the Subscribed S-NSSAIs of the terminal device but is not a network slice supported by the tracking area where the terminal device is currently located, it may be determined that the first requested network slice is the first rejected network slice not allowed to be registered and the rejection reason is not in the tracking area. Only the slices allowed to be registered can proceed with PDU session establishment later. It should be noted here that the rejection reason may include not only not being in the tracking area, but also not being in the PLMN (for example, when a certain first requested network slice is not the Subscribed S-NSSAIs of the terminal device, it may be determined that the first requested network slice is the first rejected network slice not allowed to be registered and the rejection reason is not in the PLMN) or authentication failure, etc.

[0111] In a possible implementation, the core network device may carry the first allowed network slice, the first rejected network slice and its rejection reason in the first registration reception message and return them to the terminal device.

[0112] In a possible implementation, after receiving the first registration reception message, the terminal device may update the first rejected network slice and its rejection reason to the rejected network slice list, and correspondingly update the first allowed network slice and the tracking area where the terminal device is currently located in the allowed network slice list, so as to update and maintain the allowed network slice list and the rejected network slice list. In this way, subsequently, the terminal device can continue to select the requested network slice for network slice registration from the network slices selected from the network slices with the rejection reason of not being in the tracking area in the rejected network slice list and the network slices in the allowed network slice list.

[0113] In this embodiment, the terminal device can autonomously detect the tracking area where the terminal device is currently located. When the detected tracking area is not the tracking area recorded in the allowed network slice list, the terminal device sends a mobility registration request to the core network device. The mobility registration request carries a first requested network slice of the terminal device. The first requested network slice includes a rejected network slice selected from the rejected network slice list and / or an allowed network slice selected from the allowed network slice list. Among them, the rejected network slice list records the rejected network slice and its rejection reason. The selected rejected network slice is the rejected network slice whose rejection reason is not in the tracking area. The allowed network slice list records the allowed network slice and its corresponding tracking area. In this way, when the terminal needs to re-register the network slice due to movement, it can autonomously select a requested network slice from the network slices not in the current tracking area and the network slices in the allowed network slice list to send a mobility registration request, which can speed up the registration speed and improve the registration efficiency. Moreover, the rejected network slice whose rejection reason is not in the tracking area can be selected as the requested network slice to ensure that the rejected network slice can be used and avoid waste of the rejected network slice.

[0114] Figure 3 The interaction process schematic diagram of the network slice registration method provided by the embodiments of the present disclosure is shown. As Figure 3 shown, the network slice registration method includes the following steps S301 - S307:

[0115] In step S301, when initiating an initial registration, the terminal device sends an initial registration request to the core network device;

[0116] The initial registration request carries a second requested network slice, which is a network slice selected from the configured network slices;

[0117] In step S302, in response to receiving the initial registration request, the core network device returns a second registration acceptance message to the terminal device;

[0118] The second registration acceptance message carries a second allowed network slice, a second rejected network slice, and its rejection reason;

[0119] In step S303, the terminal device detects the tracking area where the terminal device is currently located;

[0120] It should be noted here that the terminal device will continuously perform step S303.

[0121] In step S304, the terminal device updates the second rejected network slice and its rejection reason to the rejected network slice list, and correspondingly updates the second allowed network slice and the tracking area where the terminal device is currently located in the allowed network slice list;

[0122] In step 305, when the tracking area where the terminal device is currently located is not the tracking area recorded in the allowed network slice list, the terminal device sends a mobility registration request to the core network device.

[0123] In step 306, in response to receiving the mobility registration request, the core network device returns a first registration acceptance message to the terminal device.

[0124] In step 307, the terminal device updates the first rejected network slice and its rejection reason to the rejected network slice list, and correspondingly updates the first allowed network slice and the tracking area where the terminal device is currently located in the allowed network slice list.

[0125] The above network slice registration method can be applied to various communication systems, such as: Global System for Mobile Communications, Code Division Multiple Access system, Wideband Code Division Multiple Access system, General Packet Radio Service, Long Term Evolution system, Advanced Long Term Evolution system, New Radio (NR) system, Evolution system of NR system, LTE-based access to unlicensed spectrum (LTE-U) system on unlicensed spectrum, NR system on unlicensed spectrum, non-terrestrial communication network system, Universal Mobile Telecommunications System, WLAN, WiFi, 5th Generation (5G) system or other communication systems, etc.

[0126] The following takes an example to illustrate the network slice registration process provided by the present disclosure.

[0127] If the network slices subscribed by the terminal device are S-NSSAI1, S-NSSAI2, S-NSSAI3, and S-NSSAI4, the configured network slices configured by the PLMN for the terminal device are S-NSSAI1, S-NSSAI2, S-NSSAI3, the network slices supported by the tracking area TA1 are S-NSSAI1, S-NSSAI4, the network slices supported by the tracking area TA2 are S-NSSAI1, S-NSSAI2, and the network slices of the tracking area TA3 support S-NSSAI2, S-NSSAI3.

[0128] The initial configured network slice list is shown in Table 1:

[0129] Table 1

[0130] config-nssai S-NSSAI1 S-NSSAI2 S-NSSAI3

[0131] When the terminal device is in tracking area TA1 and sends a mobile registration request to the AMF, the requested network slice carried in the request is selected from the config-nssai list, which is S-NSSAI1, S-NSSAI2, and S-NSSAI3. After receiving the mobile registration request, the AMF carries the allowed network slice S-NSSAI1 and the rejected network slices S-NSSAI2 and S-NSSAI3 in the returned registration acceptance message. The rejection reasons corresponding to S-NSSAI2 and S-NSSAI3 are both not in the current TA. After receiving the registration acceptance message, the terminal device updates the allowed network slice list as shown in Table 2:

[0132] Table 2

[0133] allow-nssai TA S-NSSAI1 TA1

[0134] Update the rejected network slice list as shown in Table 3:

[0135] Table 3

[0136] reject-nssai Reason for rejection S-NSSAI2 Not in TA area S-NSSAI3 Not in TA area

[0137] The terminal device moves to a new cell, receives the broadcast message from the base station, obtains the TAC of the current cell in SIB1 of the broadcast message, and finds that it has entered TA2. Then the terminal device actively initiates a mobile registration request, carrying the requested network slices S-NSSAI2 and S-NSSAI3 selected from the rejected network slice list and S-NSSAI1 selected from the allowed network slice list. After receiving the mobile registration request, the AMF carries the allowed network slices S-NSSAI1 and S-NSSAI2 and the rejected network slice S-NSSAI3 in the registration acceptance message, and the rejection reason is not in the current TA. After the terminal device receives the registration acceptance message, it updates the allowed network slice list as shown in Table 4:

[0138] Table 4

[0139] alow-nssai TA S-NSSAI1 TA1, A2 S-NSSAI2 TA1

[0140] Update the rejected network slice list as shown in Table 5:

[0141] Table 5

[0142]

[0143] The terminal device continues to move to a new cell, receives the broadcast message from the base station, obtains the TAC of the current cell in SIB1 of the broadcast message, and finds that it enters TA3. Then the terminal device actively initiates a mobility registration request, carrying the requested network slice as S-NSSAI3 selected from the rejected network slice list, and selecting S-NSSAI1 and S-NSSAI2 from the allowed network slice list. After receiving the mobility registration request, the AMF carries the allowed network slices as S-NSSAI2 and S-NSSAI3, and the rejected network slice as S-NSSAI1 in the registration acceptance message, with the rejection reason being not in the current TA. After receiving the registration acceptance message, the terminal device updates the allowed network slice list as shown in Table 6:

[0144] Table 6

[0145] alow-nssai TA S-NSSAI2 TA2, TA3 S-NSSAI3 TA3

[0146] Update the rejected network slice list as shown in Table 7:

[0147] Table 7

[0148]

[0149] The present disclosure also provides a registration device for network slices, Figure 4 showing a structural block diagram of a registration device for network slices applied to a terminal device according to an embodiment of the present disclosure. This device can be implemented as part or all of an electronic device through software, hardware, or a combination of both. As Figure 4 shown, the registration device for network slices includes:

[0150] A detection module 401, configured to detect the tracking area where the terminal device is currently located;

[0151] A mobility registration request module 402, configured to send a mobility registration request to the core network device when the tracking area is not the tracking area recorded in the allowed network slice list. The mobility registration request carries the first requested network slice of the terminal device, and the first requested network slice includes the rejected network slice selected from the rejected network slice list and / or the allowed network slice selected from the allowed network slice list. Among them, the rejected network slice list records the rejected network slice and its rejection reason, the selected rejected network slice is the rejected network slice whose rejection reason is not in the tracking area, and the allowed network slice list records the allowed network slice and its corresponding tracking area;

[0152] The first registration receiving module 403 is configured to receive a first registration receiving message returned by the core network device in response to the mobility registration request, where the first registration receiving message carries the first allowed network slice, the first rejected network slice, and the rejection reason in the first requested network slice;

[0153] The first update module 404 is configured to update the first rejected network slice and the rejection reason thereof to the rejected network slice list, and correspondingly update the first allowed network slice and the tracking area where the terminal device is currently located in the allowed network slice list.

[0154] In a possible implementation manner, the device further includes:

[0155] The initial registration request module is configured to send an initial registration request to the core network device when the terminal device initiates an initial registration, where the initial registration request carries a second requested network slice, and the second requested network slice is a configured network slice;

[0156] The second registration receiving module is configured to receive a second registration receiving message returned by the core network device in response to the initial registration request, where the second registration receiving message carries the second allowed network slice, the second rejected network slice, and the rejection reason in the second requested network slice;

[0157] The second update module is configured to update the second rejected network slice and the rejection reason thereof to the rejected network slice list, and correspondingly update the second allowed network slice and the tracking area where the terminal device is currently located in the allowed network slice list.

[0158] In a possible implementation manner, the device further includes:

[0159] The deletion module is configured to delete the rejected network slice in the first requested network slice from the rejected network slice list.

[0160] In a possible implementation manner, the deletion module is configured to:

[0161] When the rejected network slice in the first requested network slice is the first allowed network slice, delete the rejected network slice in the first requested network slice from the rejected network slice list.

[0162] In a possible implementation manner, the detection module is configured to:

[0163] Receive a broadcast message from the base station, where the broadcast message carries the tracking area code of the tracking area where the terminal device is currently located;

[0164] Based on the tracking area code, determine the tracking area where the terminal device is currently located.

[0165] The present disclosure also provides a registration device for a network slice. Figure 5 The structural block diagram of a registration device for a network slice applied to a core network device provided by an embodiment of the present disclosure is shown. This device can be implemented as part or all of an electronic device through software, hardware, or a combination of both. As Figure 5 shown, the registration device for the network slice includes:

[0166] A request receiving module 501, configured to receive a mobility registration request sent by a terminal device. The mobility registration request carries a first requested network slice of the terminal device. The first requested network slice includes a rejected network slice selected from a rejected network slice list and / or an allowed network slice selected from an allowed network slice list. Among them, the rejected network slice list records the rejected network slice and its rejection reason. The selected rejected network slice is a rejected network slice whose rejection reason is not in the tracking area. The allowed network slice list records the allowed network slice and its corresponding tracking area.

[0167] A slice determination module 502, configured to determine a first allowed network slice, a first rejected network slice, and its rejection reason in the first requested network slice in response to the mobility registration request.

[0168] A sending module 503, configured to return a first registration reception message to the terminal device. The first registration reception message carries the first allowed network slice, the first rejected network slice, and its rejection reason in the first requested network slice.

[0169] The technical terms and technical features mentioned in the embodiments of this device are the same as or similar to those mentioned in the above method embodiments. For the explanations and descriptions of the technical terms and technical features involved in this device, reference can be made to the explanations and descriptions of the above method embodiments, which will not be repeated here.

[0170] The present disclosure also discloses an electronic device, which can be a terminal device or a core network device. Figure 6 The structural block diagram of an electronic device according to an embodiment of the present disclosure is shown.

[0171] As Figure 6As shown, the electronic device 600 includes a memory 601 and a processor 602. Among them, the memory 601 is used to store one or more computer instructions, and the one or more computer instructions are executed by the processor 602 to implement the method according to the embodiments of the present disclosure. When the electronic device is a terminal device, the one or more computer instructions are executed by the processor to implement the registration method for network slices applied to the terminal device. When the electronic device is a core network device, the one or more computer instructions are executed by the processor to implement the registration method for network slices applied to the core network device.

[0172] Figure 7 The structural schematic diagram of a computer system suitable for implementing the method according to the embodiments of the present disclosure is shown.

[0173] As Figure 7 shown, the computer system 700 includes a processing unit 701, which can execute various processes in the above embodiments according to the program stored in the read-only memory (ROM) 702 or the program loaded from the storage section 708 into the random access memory (RAM) 703. In the RAM 703, various programs and data required for the operation of the computer system 700 are also stored. The processing unit 701, the ROM 702, and the RAM 703 are connected to each other through a bus 704. The input / output (I / O) interface 705 is also connected to the bus 704.

[0174] The following components are connected to the I / O interface 705: an input section 706 including a keyboard, a mouse, etc.; an output section 707 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc. and a speaker, etc.; a storage section 708 including a hard disk, etc.; and a communication section 709 including a network interface card such as a LAN card, a modem, etc. The communication section 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the I / O interface 705 as needed. A removable medium 711 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc. is mounted on the drive 710 as needed so that a computer program read therefrom is installed into the storage section 708 as needed. Among them, the processing unit 701 can be implemented as a processing unit such as a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), a TPU (Tensor Processing Unit), an FPGA (Field Programmable Gate Array), an NPU (Neural network Processing Unit), etc.; among them, the CPU mainly interprets computer instructions and processes data in computer software; the GPU is mainly used to process image data; the TPU is mainly used for machine learning workloads, and the NPU is a new type of processor based on neural network algorithms and acceleration.

[0175] Specifically, according to an embodiment of the present disclosure, the method described above can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product that includes computer instructions that, when executed by a processor, implement the method steps described above. In such an embodiment, the computer program product can be downloaded and installed from a network through the communication section 709, and / or installed from the removable medium 711.

[0176] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagram may represent a module, a segment of a program, or a part of code that contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than that marked in the accompanying drawings. For example, two consecutive blocks shown may actually be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flowchart, as well as combinations of blocks in the block diagram and / or flowchart, may be implemented by a dedicated hardware-based system that performs the specified functions or operations, or may be implemented by a combination of dedicated hardware and computer instructions.

[0177] The units or modules described in the embodiments of the present disclosure can be implemented in software or in programmable hardware. The described units or modules can also be provided in a processor, and the names of these units or modules do not, in some cases, constitute a limitation to the units or modules themselves.

[0178] On the other hand, the present disclosure also provides a computer-readable storage medium, which can be the computer-readable storage medium included in the electronic device or computer system in the above embodiments; or it can exist separately and be a computer-readable storage medium not assembled into the device. The computer-readable storage medium stores one or more programs, and the programs are used by one or more processors to execute the methods described in the present disclosure.

[0179] The above description is only a preferred embodiment of the present disclosure and an explanation of the applied technical principles. Those skilled in the art should understand that the scope of the invention involved in the present disclosure is not limited to the technical solutions formed by the specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the inventive concept. For example, technical solutions formed by mutually replacing the above features with (but not limited to) technical features having similar functions disclosed in the present disclosure.

Claims

1. A network slice registration method, characterized in that: Applied to a terminal device, the method comprises: Detecting the tracking area where the terminal device is currently located; When the tracking area is not a tracking area recorded in the allowed network slice list, a mobility registration request is sent to the core network device, wherein the mobility registration request carries the first requested network slice of the terminal device, and the first requested network slice includes a rejected network slice selected from the rejected network slice list and / or an allowed network slice selected from the allowed network slice list; wherein the rejected network slices and their rejection reasons are recorded in the rejected network slice list, and the selected rejected network slice is a rejected network slice whose rejection reason is that it is not in the tracking area; the allowed network slice list records the allowed network slices and their corresponding tracking areas; Receiving a first registration reception message returned by the core network device in response to the mobility registration request, wherein the first registration reception message carries a first allowed network slice in the first requested network slice, a first rejected network slice and a rejection reason thereof; The first rejected network slice and the reason for rejection are updated in the rejected network slice list, and the first allowed network slice and the tracking area where the terminal device is currently located are correspondingly updated in the allowed network slice list.

2. The method according to claim 1, characterized in that The method further comprises: When the terminal device initiates initial registration, an initial registration request is sent to the core network device, where the initial registration request carries a second requested network slice, where the second requested network slice is a network slice selected from the configured network slices; Receive a second registration reception message returned by the core network device in response to the initial registration request, wherein the second registration reception message carries a second allowed network slice, a second rejected network slice and a rejection reason; The second rejected network slice and the reason for rejection are updated in the rejected network slice list, and the second allowed network slice and the tracking area where the terminal device is currently located are correspondingly updated in the allowed network slice list.

3. The method according to claim 1, characterized in that The method further comprises: The rejected network slices in the first requested network slices are deleted from the rejected network slice list.

4. The method according to claim 3, characterized in that The deleting the rejected network slice in the first requested network slice from the rejected network slice list includes: When the rejected network slice in the first requested network slice is the first allowed network slice, the rejected network slice in the first requested network slice is deleted from the rejected network slice list.

5. The method according to claim 1, characterized in that: The detecting the tracking area where the terminal device is currently located comprises: Receiving a broadcast message from a base station, wherein the broadcast message carries a tracking area code of a tracking area where the terminal device is currently located; Based on the tracking area code, the tracking area where the terminal device is currently located is determined.

6. A method for registering a network slice, characterized in that: Applied to a core network device, the method comprises: Receive a mobility registration request sent by a terminal device, wherein the mobility registration request carries a first requested network slice of the terminal device, wherein the first requested network slice includes a rejected network slice selected from a rejected network slice list and / or an allowed network slice selected from an allowed network slice list; wherein the rejected network slices and their rejection reasons are recorded in the rejected network slice list, and the selected rejected network slice is a rejected network slice whose rejection reason is that the slice is not within a tracking area; and the allowed network slice list records the allowed network slices and their corresponding tracking areas; In response to the mobility registration request, determining a first allowed network slice, a first rejected network slice and a rejection reason thereof in the first requested network slice; A first registration reception message is returned to the terminal device, wherein the first registration reception message carries the first allowed network slice in the first requested network slice, the first rejected network slice and the reason for rejection.

7. A network slice registration device, characterized in that: Applied to a terminal device, the device comprises: A detection module, configured to detect a tracking area where the terminal device is currently located; A mobile registration request module is configured to send a mobility registration request to a core network device when the tracking area is not a tracking area recorded in an allowed network slice list, wherein the mobility registration request carries a first requested network slice of the terminal device, wherein the first requested network slice includes a rejected network slice selected from a rejected network slice list and / or an allowed network slice selected from the allowed network slice list; wherein the rejected network slices and their rejection reasons are recorded in the rejected network slice list, and the selected rejected network slice is a rejected network slice whose rejection reason is that the slice is not within the tracking area; and the allowed network slice list records allowed network slices and their corresponding tracking areas; A first registration receiving module is configured to receive a first registration receiving message returned by the core network device in response to the mobility registration request, wherein the first registration receiving message carries a first allowed network slice in the first requested network slice, a first rejected network slice and a rejection reason thereof; The first update module is configured to update the first rejected network slice and the reason for rejection thereof to the rejected network slice list, and to update the first allowed network slice and the tracking area where the terminal device is currently located in the allowed network slice list accordingly.

8. The device according to claim 7, characterized in that The device also includes: An initial registration request module is configured to send an initial registration request to the core network device when the terminal device initiates initial registration, wherein the initial registration request carries a second requested network slice, and the second requested network slice is a configured network slice; A second registration receiving module is configured to receive a second registration receiving message returned by the core network device in response to the initial registration request, wherein the second registration receiving message carries a second allowed network slice in the second requested network slice, a second rejected network slice and a rejection reason thereof; The second update module is configured to update the second rejected network slice and the reason for rejection to the rejected network slice list, and to update the second allowed network slice and the tracking area where the terminal device is currently located in the allowed network slice list accordingly.

9. The device according to claim 7, characterized in that The device also includes: The deletion module is configured to delete the rejected network slices in the first requested network slices from the rejected network slice list.

10. The device according to claim 9, characterized in that The deletion module is configured to: When the rejected network slice in the first requested network slice is the first allowed network slice, the rejected network slice in the first requested network slice is deleted from the rejected network slice list.

11. The device according to claim 7, characterized in that The detection module is configured as follows: Receiving a broadcast message from a base station, wherein the broadcast message carries a tracking area code of a tracking area where the terminal device is currently located; Based on the tracking area code, the tracking area where the terminal device is currently located is determined.

12. A network slice registration device, characterized in that: Applied to core network equipment, the device includes: A request receiving module is configured to receive a mobility registration request sent by a terminal device, wherein the mobility registration request carries a first requested network slice of the terminal device, wherein the first requested network slice includes a rejected network slice selected from a rejected network slice list and / or an allowed network slice selected from an allowed network slice list; wherein the rejected network slice list records the rejected network slices and the reasons for rejection, and the selected rejected network slice is a rejected network slice whose reason for rejection is that the slice is not within a tracking area; and the allowed network slice list records the allowed network slices and their corresponding tracking areas; A slice determination module, configured to determine, in response to the mobility registration request, a first allowed network slice, a first rejected network slice and a rejection reason in the first requested network slice; The sending module is configured to return a first registration reception message to the terminal device, wherein the first registration reception message carries the first allowed network slice in the first requested network slice, the first rejected network slice and the reason for rejection.

13. A terminal device, characterized in that: The method comprises a memory and a processor, wherein the memory is used to store one or more computer instructions, wherein the one or more computer instructions are executed by the processor to implement the method according to any one of claims 1 to 5.

14. A core network device, characterized in that: The method comprises a memory and a processor, wherein the memory is used to store one or more computer instructions, wherein the one or more computer instructions are executed by the processor to implement the method of claim 6.

15. A readable storage medium, characterized in that: Computer instructions are stored thereon, and when the computer instructions are executed by a processor, the method described in any one of claims 1 to 6 is implemented.

Images