Network slice configuration method and device, equipment and storage medium

Abstract

The invention relates to the technical field of communication, and particularly relates to a network slice configuration method, device and equipment and a storage medium, and the method comprises the steps: monitoring whether each network slice managed by core network equipment is limited in resource or not; and when a target network slice resource in each network slice is limited, sending a first terminal configuration update message to a terminal device served by the core network device, the first terminal configuration update message being used for notifying that the target network slice resource is limited, the target network slice is sent to the terminal equipment, so that the terminal equipment updates the target network slice to a rejection network slice list and deletes the target network slice from a configuration network slice list, and a rejection reason corresponding to the target network slice in the rejection network slice list is resource limitation. According to the technical scheme, the terminal equipment can be prevented from initiating an invalid registration request on the network slice with limited resources, the signaling burden of the network is reduced, and the method is mainly used for network slice registration of the terminal equipment.

Description

Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a network slicing configuration method, apparatus, device and storage medium. Background Art

[0002] Network slicing technology can build multiple dedicated, virtualized, and isolated logical networks on a common physical network to meet the differentiated requirements of different users for network capabilities. In the existing technology, when network slice resources are limited, the terminal device cannot know in time, and will initiate invalid network slice registration on the resource-limited network slice, increasing the signaling burden of the network. Summary of the invention

[0003] In order to solve the problems in the related art, the embodiments of the present disclosure provide a network slicing configuration method, apparatus, device and storage medium.

[0004] In a first aspect, an embodiment of the present disclosure provides a network slice configuration method, which is applied to a core network device, and the method includes: Monitoring whether each network slice managed by the core network device is resource-constrained; When there is a target network slice with limited resources in each network slice, a first terminal configuration update message is sent to the terminal device served by the core network device, wherein the first terminal configuration update message is used to notify the target network slice that the resources are limited, so that the terminal device updates the target network slice to the rejected network slice list and deletes the target network slice from the configured network slice list, and the rejection reason corresponding to the target network slice in the rejected network slice list is limited resources.

[0005] In a possible implementation, after sending the first terminal configuration update message to the terminal device served by the core network device, the method further includes: Monitoring whether resources of the target network slice are released; When the resources of the target network slice are released, a second terminal configuration update message is sent to the terminal device served by the core network device, and the second terminal configuration update message is used to notify the target network slice resource release so that the terminal device deletes the target network slice from the rejected network slice list and updates the target network slice to the configured network slice list.

[0006] In a possible implementation manner, the sending a first terminal configuration update message to a terminal device served by the core network device includes: Sending a first terminal configuration update message to a target terminal device, wherein a configured network slice list of the target terminal device includes the target network slice; The sending a second terminal configuration update message to the terminal device served by the core network device includes: Send a second terminal configuration update message to the target terminal device.

[0007] In a possible implementation manner, the sending a first terminal configuration update message to a terminal device served by the core network device includes: Sending the first terminal configuration update message to the terminal device that has requested the core network device to register the target network slice; The sending a second terminal configuration update message to the terminal device served by the core network device includes: The second terminal configuration update message is sent to the terminal device that has requested to register the target network slice to the core network device.

[0008] In a possible implementation, the monitoring whether each network slice managed by the core network device is resource-constrained includes: When it is monitored that the number of terminals served by the network slice has reached a preset maximum number of terminals or the number of protocol data unit PDU sessions established on the network slice has reached a preset maximum number of PDU sessions, it is determined that the network slice resources are monitored to be limited.

[0009] In a second aspect, an embodiment of the present disclosure provides a network slice configuration method, which is applied to a terminal device, and the method includes: Receive a first terminal configuration update message sent by a core network device, where the first terminal configuration update message is used to notify a target network slice that resources are limited; The target network slice is updated to the rejected network slice list and the target network slice is deleted from the configured network slice list, wherein the rejection reason corresponding to the target network slice in the rejected network slice list is resource limitation.

[0010] In a possible implementation, after receiving the first terminal configuration update message sent by the core network device, the method further includes: Receive a second terminal configuration update message sent by the core network device, where the second terminal configuration update message is used to notify the target network slice resource release; The target network slice is deleted from the rejected network slice list and the target network slice is updated to the configured network slice list.

[0011] In a possible implementation, after receiving the second terminal configuration update message sent by the core network device, the method further includes: If the target network slice corresponding to the application currently running on the terminal device is not in the list of allowed network slices, a registration request message is sent to the core network device, and the registration request message carries a requested network slice, which is the target network slice corresponding to the application from the configured network slice list.

[0012] In a third aspect, an embodiment of the present disclosure provides a network slice configuration device, which is applied to a core network device, and the device includes: A first monitoring module is configured to monitor whether each network slice managed by the core network device is resource-constrained; The first configuration module is configured to send a first terminal configuration update message to the terminal device served by the core network device when there is a target network slice with limited resources in each of the network slices. The first terminal configuration update message is used to notify the target network slice that the resources are limited, so that the terminal device updates the target network slice to the rejected network slice list and deletes the target network slice from the configured network slice list. The rejection reason corresponding to the target network slice in the rejected network slice list is resource limitation.

[0013] In a possible implementation, the device further includes: A second monitoring module is configured to monitor whether the resources of the target network slice are released; The second configuration module is configured to send a second terminal configuration update message to the terminal device served by the core network device when the resources of the target network slice are released, and the second terminal configuration update message is used to notify the target network slice resource release so that the terminal device deletes the target network slice from the rejected network slice list and updates the target network slice to the configured network slice list.

[0014] In a possible implementation manner, the first configuration module is configured to: Sending a first terminal configuration update message to a target terminal device, wherein a configured network slice list of the target terminal device includes the target network slice; The second configuration module is configured to: Send a second terminal configuration update message to the target terminal device.

[0015] In a possible implementation manner, the first configuration module is configured to: Sending the first terminal configuration update message to the terminal device that has requested the core network device to register the target network slice; The second configuration module is configured to: The second terminal configuration update message is sent to the terminal device that has requested to register the target network slice to the core network device.

[0016] In a possible implementation, the first monitoring module is configured as follows: When it is monitored that the number of terminals served by the network slice has reached a preset maximum number of terminals or the number of protocol data unit PDU sessions established on the network slice has reached a preset maximum number of PDU sessions, it is determined that the network slice resources are monitored to be limited.

[0017] In a fourth aspect, an embodiment of the present disclosure provides a network slice configuration device, applied to a terminal device, the device comprising: A first receiving unit is configured to receive a first terminal configuration update message sent by a core network device, where the first terminal configuration update message is used to notify a target network slice that resources are limited; The first updating unit is configured to update the target network slice to the rejected network slice list and delete the target network slice from the configured network slice list, wherein the rejection reason corresponding to the target network slice in the rejected network slice list is resource limitation.

[0018] In a possible implementation, the device further includes: A second receiving unit is configured to receive a second terminal configuration update message sent by the core network device, where the second terminal configuration update message is used to notify the target network slice resource release; The second updating unit is configured to delete the target network slice from the rejected network slice list and update the target network slice to the configured network slice list.

[0019] In a possible implementation, the device further includes: The registration request module is configured to send a registration request message to the core network device if the target network slice corresponding to the application currently running on the terminal device is not in the allowed network slice list. The registration request message carries a requested network slice, and the requested network slice is the target network slice corresponding to the application in the configured network slice list.

[0020] In a fifth aspect, an embodiment of the present disclosure provides a core network device, comprising 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 described in the first aspect.

[0021] In a sixth aspect, an embodiment of the present disclosure provides a terminal device, comprising 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 any method described in the second aspect.

[0022] In a seventh aspect, an embodiment of the present disclosure provides a readable storage medium having computer instructions stored thereon, which, when executed by a processor, implement the method described in any one of the first aspect or the second aspect.

[0023] According to the technical solution provided by the embodiment of the present disclosure, the core network device can monitor in real time whether each network slice managed by the core network device is resource-constrained, and when a target network slice in each network slice is resource-constrained, send a first terminal configuration update message to the terminal device served by the core network device, wherein the first terminal configuration update message is used to notify the target network slice that the resources are limited, so that the terminal device updates the target network slice to the rejected network slice list and deletes the target network slice from the configured network slice list. The rejection reason corresponding to the target network slice in the rejected network slice list is resource limitation. In this way, when the terminal device performs network slice registration and selects the requested network slice later, it will not select the resource-constrained target network slice, thereby avoiding the terminal device initiating an invalid registration request on the resource-constrained network slice and reducing the signaling burden of the network.

[0024] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Other features, objectives and advantages of the present disclosure will become more apparent through the following detailed description of non-limiting embodiments in conjunction with the accompanying drawings. In the accompanying drawings:

[0026] Figure 1 A flowchart of a network slice configuration method applied to a core network device provided in an embodiment of the present disclosure is shown.

[0027] Figure 2 A flowchart of a network slice configuration method applied to a terminal device provided in an embodiment of the present disclosure is shown.

[0028] Figure 3 A schematic diagram of the interactive process of the network slice configuration method provided by an embodiment of the present disclosure is shown.

[0029] Figure 4 A structural block diagram of a network slicing configuration device applied to a core network device provided by an embodiment of the present disclosure is shown.

[0030] Figure 5A structural block diagram of a network slicing configuration device applied to a terminal device provided by an embodiment of the present disclosure is shown.

[0031] Figure 6 A structural block diagram of an electronic device according to an embodiment of the present disclosure is shown.

[0032] Figure 7 A schematic diagram showing the structure of a computer system suitable for implementing the method of the embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0033] 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 not related to the description of the exemplary embodiments are omitted in the accompanying drawings.

[0034] In the present disclosure, it should be understood that terms such as "include" or "have" are intended to indicate the presence of features, numbers, steps, behaviors, components, parts, or a combination thereof disclosed in the present specification, and are not intended to exclude the possibility that one or more other features, numbers, steps, behaviors, components, parts, or a combination thereof exist or are added.

[0035] It should also be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present disclosure may be combined with each other. The present disclosure will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0036] Figure 1 A flow chart of a network slice configuration method applied to a core network device provided by an embodiment of the present disclosure is shown. Figure 1 As shown, the network slice configuration method includes the following steps S101-S102:

[0037] In step S101, monitoring whether each network slice managed by the core network device is resource-constrained; In step S102, when the target network slice resources in each network slice are limited, a first terminal configuration update message is sent to the terminal device served by the core network device.

[0038] In one possible implementation, the network slice configuration method may be applied to a core network device capable of performing network slice configuration, wherein the core network device includes an AMF (Access and Mobility Management Function).

[0039] In a possible implementation, the core network device can monitor in real time whether each network slice in the network managed by the core network device is resource-constrained. Resource limitation here means that the available resources in the network slice are limited and cannot meet more user needs.

[0040] In a possible implementation, when it is monitored that resources of a target network slice are limited, the core network device may send a first terminal configuration update message to each terminal device it serves, where the first terminal configuration update message is used to notify the target network slice of resource limitations.

[0041] In a possible implementation manner, several network slices that can be recorded in the terminal device are introduced below: Configured NSSAI (Configured Network Slicing): The network is configured to provide network slices that the terminal device can request to use. The terminal device will maintain a configured network slice list, which records the network slices that the terminal device can request to use; Request NSSAI (Request Network Slice): The network slice requested by the terminal device in the registration request message. The requested network slice can be selected from the configured network slice list. Allowed NSSAI (Allowed Network Slice): The network slice that the terminal device is allowed to use after successfully registering can be carried in the registration reception message after the core network device receives the registration request message and returned to the terminal device; the terminal device will maintain an allowed network slice list, which records the network slices that the terminal device is currently allowed to use; only the allowed network slices that are allowed to be registered can subsequently establish a PDU (Protocol Data Unit) session; rejected NSSAI (rejected network slice): The network slice that the terminal device is not allowed to use when registering can be returned to the terminal device by the core network device in the registration reception message after receiving the registration request message; the terminal device will maintain a rejected network slice list, which records the rejected network slices that the terminal device is not currently allowed to use and the reasons for rejection.

[0042] In this way, after the terminal device receives the first terminal configuration update message, it can update the resource-constrained target network slice to the rejected network slice list, where the rejection reason corresponding to the target network slice in the rejected network slice list is resource limitation, and delete the target network slice in the configured network slice list at the same time. In this way, when selecting a requested network slice from the configured network slice list, the resource-constrained target network slice cannot be selected; in this way, the terminal device is prevented from initiating an invalid registration request on an unavailable network slice.

[0043] In this implementation mode, the core network device can monitor in real time whether each network slice managed by the core network device is resource-constrained, and when a target network slice in each network slice is resource-constrained, send a first terminal configuration update message to the terminal device served by the core network device, wherein the first terminal configuration update message is used to notify the target network slice that the resources are limited, so that the terminal device updates the target network slice to the rejected network slice list and deletes the target network slice from the configured network slice list. The rejection reason corresponding to the target network slice in the rejected network slice list is resource limitation. In this way, when the terminal device performs network slice registration and selects the requested network slice later, it will not select the resource-constrained target network slice, thereby avoiding the terminal device initiating an invalid registration request on the resource-constrained network slice and reducing the signaling burden of the network.

[0044] In a possible implementation, after sending the first terminal configuration update message to the terminal device served by the core network device, the method further includes: Monitoring whether resources of the target network slice are released; When the resources of the target network slice are released, a second terminal configuration update message is sent to the terminal device served by the core network device, and the second terminal configuration update message is used to notify the target network slice resource release so that the terminal device deletes the target network slice from the rejected network slice list and updates the target network slice to the configured network slice list.

[0045] In this implementation, after notifying the terminal device that the resources of the target network slice are limited, the core network device will also monitor in real time whether the resources of the target network slice are released. Here, the release of network slice resources refers to the process of returning previously allocated or occupied resources to an available state. If the resources of the target network slice are released, it means that there are available resources on the target network slice. At this time, the core network device can send a second terminal configuration update message to the terminal device served by the core network device. The second terminal configuration update message is used to notify the release of the target network slice resources. At this time, correspondingly, the terminal device can delete the target network slice from the rejected network slice list and update the target network slice to the configured network slice list. In this way, when the terminal device performs network slice registration and selects the requested network slice later, it can promptly select the target network slice from the configured network slice list as the requested network slice for registration.

[0046] This implementation can also notify the terminal device after the target network slice resources are released so that the terminal device can promptly select the target network slice for registration request.

[0047] In a possible implementation manner, the sending a first terminal configuration update message to a terminal device served by the core network device includes: Sending a first terminal configuration update message to a target terminal device, wherein a configured network slice list of the target terminal device includes the target network slice; The sending a second terminal configuration update message to the terminal device served by the core network device includes: Send a second terminal configuration update message to the target terminal device.

[0048] In this implementation, there are many terminal devices served by the core network device, and some terminal devices may not be configured with the target network slice by the network, that is, regardless of whether the resources of the target network slice are limited, these terminal devices themselves will not initiate a registration request using the unlabeled network slice as a request network slice. Therefore, in order to reduce the signaling burden of the network, the core network device can send a first terminal configuration update message to the target terminal device, and the target terminal device refers to a device that includes the target network slice in the configured network slice list, which avoids these terminal devices configured with the target network slice from initiating invalid network slice registration. Accordingly, if the target network slice resources are released later, the core network device will also send a second terminal configuration update message to these target terminal devices.

[0049] In a possible implementation manner, the sending a first terminal configuration update message to a terminal device served by the core network device includes: Sending the first terminal configuration update message to the terminal device that has requested the core network device to register the target network slice; The sending a second terminal configuration update message to the terminal device served by the core network device includes: The second terminal configuration update message is sent to the terminal device that has requested to register the target network slice to the core network device.

[0050] In this implementation, among the terminal devices served by the core network device, if there is a terminal device that has requested the core network device to register the target network slice, it means that the terminal device has been configured with the target network slice by the network. Therefore, in order to reduce the signaling burden of the network, the core network device can send the first terminal configuration update message to the terminal devices that have requested the core network device to register the target network slice, so as to avoid these terminal devices configured with the target network slice from initiating invalid network slice registration. Correspondingly, if the target network slice resources are released later, the core network device will also send a second terminal configuration update message to these terminal devices that have requested the core network device to register the target network slice.

[0051] In a possible implementation, the monitoring whether each network slice managed by the core network device is resource-constrained includes: When it is monitored that the number of terminals served by the network slice has reached a preset maximum number of terminals or the number of PDU sessions established on the network slice has reached a preset maximum number of PDU sessions, it is determined that the network slice resources are monitored to be limited.

[0052] In this embodiment, the resource limitation of the network slice refers to that the number of terminals served by the network slice has reached the preset maximum number of terminals or the number of PDU sessions established on the network slice has reached the preset maximum number of PDU sessions. When it is monitored that the number of terminals served by the network slice has reached the preset maximum number of terminals or the number of PDU sessions established on the network slice has reached the preset maximum number of PDU sessions, it is determined that the network slice resources are monitored to be limited; when it is monitored that the number of terminals served by the network slice has not reached the preset maximum number of terminals or the number of PDU sessions established on the network slice has not reached the preset maximum number of PDU sessions, it is monitored that the network slice is not resource limited. If, after monitoring that the target network slice resources are limited, it is also monitored that the number of terminals served by the target network slice has not reached the preset maximum number of terminals or the number of PDU sessions established on the network slice has not reached the preset maximum number of PDU sessions, it is monitored that the network slice resources are released.

[0053] Figure 2 A flow chart of a network slice configuration method applied to a terminal device provided by an embodiment of the present disclosure is shown. Figure 2 As shown, the network slice configuration method includes the following steps S201-S202:

[0054] In step S201, a first terminal configuration update message sent by a core network device is received, where the first terminal configuration update message is used to notify the target network slice that resources are limited; In step S202, the target network slice is updated to the rejected network slice list and the target network slice is deleted from the configured network slice list, and the rejection reason corresponding to the target network slice in the rejected network slice list is resource limitation.

[0055] In one possible implementation, the network slicing configuration method may be applied to a terminal device capable of performing network slicing configuration, which terminal device may 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 capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as a NR (New Radio) network, or a terminal device in a future-evolved public land mobile network (PLMN) network, and the like.

[0056] In a possible implementation, the core network device can monitor in real time whether each network slice in the network managed by the core network device is resource-constrained, where resource limitation refers to the limited resources available in the network slice, which cannot meet more user needs. When it is detected that a target network slice is resource-constrained, the core network device can send a first terminal configuration update message to each terminal device it serves, and the first terminal configuration update message is used to notify the target network slice that the resources are limited.

[0057] In a possible implementation manner, several network slices that can be recorded in the terminal device are introduced below: Configure network slices: The network is configured to provide network slices that the terminal device can request to use. The terminal device will maintain a list of configured network slices, which records the network slices that the terminal device can request to use; Requested network slice: The network slice requested by the terminal device in the registration request message. The requested network slice can be selected from the configured network slice list. Allowed network slices: The network slices that are allowed to be used after the terminal device successfully registers can be returned to the terminal device in the registration reception message after the core network device receives the registration request message; the terminal device will maintain an allowed network slice list, which records the network slices that the terminal device is currently allowed to use; only the allowed network slices that are allowed to be registered can be used to establish a PDU session later; Rejected network slices: Network slices that are not allowed to be used when the terminal device registers. After the core network device receives the registration request message, it can be carried in the registration reception message and returned to the terminal device; the terminal device will maintain a rejected network slice list, which records the rejected network slices that the terminal device is currently not allowed to use and the reasons for rejection.

[0058] In this way, after the terminal device receives the first terminal configuration update message, it can update the resource-constrained target network slice to the rejected network slice list, where the rejection reason corresponding to the target network slice in the rejected network slice list is resource limitation, and delete the target network slice in the configured network slice list at the same time. In this way, when selecting a requested network slice from the configured network slice list, the resource-constrained target network slice cannot be selected; in this way, the terminal device is prevented from initiating an invalid registration request on an unavailable network slice.

[0059] In this implementation mode, the core network device can monitor in real time whether each network slice managed by the core network device is resource-constrained, and when a target network slice in each network slice is resource-constrained, send a first terminal configuration update message to the terminal device served by the core network device, wherein the first terminal configuration update message is used to notify the target network slice that the resources are limited, so that the terminal device updates the target network slice to the rejected network slice list and deletes the target network slice from the configured network slice list. The rejection reason corresponding to the target network slice in the rejected network slice list is resource limitation. In this way, when the terminal device performs network slice registration and selects the requested network slice later, it will not select the resource-constrained target network slice, thereby avoiding the terminal device initiating an invalid registration request on the resource-constrained network slice and reducing the signaling burden of the network.

[0060] In a possible implementation, after updating the target network slice to the rejected network slice list, the method further includes: Receive a second terminal configuration update message sent by the core network device, where the second terminal configuration update message is used to notify the target network slice resource release; The target network slice is deleted from the rejected network slice list and the target network slice is updated to the configured network slice list.

[0061] In this implementation, after notifying the terminal device that the resources of the target network slice are limited, the core network device will also monitor in real time whether the resources of the target network slice are released. Here, the release of network slice resources refers to the process of returning previously allocated or occupied resources to an available state. If the resources of the target network slice are released, it means that there are available resources on the target network slice. At this time, the core network device can send a second terminal configuration update message to the terminal device served by the core network device. The second terminal configuration update message is used to notify the release of the target network slice resources. At this time, correspondingly, the terminal device can delete the target network slice from the rejected network slice list and update the target network slice to the configured network slice list. In this way, when the terminal device performs network slice registration and selects the requested network slice later, it can promptly select the target network slice from the configured network slice list as the requested network slice for registration.

[0062] This embodiment can also notify the terminal device after the target network slice resources are released so that the terminal device can promptly select the target network slice for registration request.

[0063] In a possible implementation, after receiving the second terminal configuration update message sent by the core network device, the method further includes: If the target network slice corresponding to the application currently running on the terminal device is not in the list of allowed network slices, a registration request message is sent to the core network device, and the registration request message carries a requested network slice, and the requested network slice is the target network slice corresponding to the application selected from the configured network slice list.

[0064] In this embodiment, some network slices may require that the terminal device does not need to register in the network slice when there is no application request, and only initiates registration and PDU session establishment when there is an application demand. Therefore, when the network slice corresponding to the application currently running on the terminal device is the target network slice, but is not in the allowed network slice list, the terminal device needs to initiate network slice registration. At this time, the terminal device can send a registration request message to the core network device, and the registration request message carries the requested network slice. The requested network slice is the target network slice corresponding to the application selected from the configured network slice list. When the target network slice is successfully registered by the core network device and the allowed network slice carried in the returned registration reception message is the target network slice, the application currently running on the terminal device can establish a PDU session in the target network slice.

[0065] Figure 3 The following is a schematic diagram showing the interactive process of the network slice configuration method provided by the embodiment of the present disclosure. Figure 3As shown, the network slice configuration method includes the following steps S301-S307:

[0066] In step S301, the core network device monitors whether each network slice managed by the core network device is resource-constrained; In step S302, when a target network slice resource is limited in each of the network slices, the core network device sends a first terminal configuration update message to the terminal device served by the core network device; The first terminal configuration update message is used to notify the target network slice that resources are limited; In step S303, the terminal device updates the target network slice to the rejected network slice list and deletes the target network slice from the configured network slice list; The rejection reason corresponding to the target network slice in the rejected network slice list is resource limitation; In step S304, the core network device monitors whether the resources of the target network slice are released; In step 305, when the resources of the target network slice are released, the core network device sends a second terminal configuration update message to the terminal device served by the core network device; The second terminal configuration update message is used to notify the target network slice resource release; In step 306, the terminal device deletes the target network slice from the rejected network slice list and updates the target network slice to the configured network slice list; In step 307, if the target network slice corresponding to the application currently running on the terminal device is not in the list of allowed network slices, the terminal device sends a registration request message to the core network device, and the requested network slice carried in the registration request message is the target network slice.

[0067] The above-mentioned network slicing configuration method can be applied to various communication systems, such as: global mobile communication system, 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 wireless (New Radio, NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-based access to unlicensed spectrum, LTE-U) system, NR system on unlicensed spectrum, non-terrestrial communication network system, universal mobile communication system, WLAN, WiFi, fifth generation communication (5th Generation, 5G) system or other communication systems.

[0068] The following example illustrates the network slice configuration process provided by the present invention.

[0069] If the network slices configured by the PLMN in the terminal device are S-NSSAI1, S-NSSAI2, and S-NSSAI3. Among them, S-NSSAI3 has reached the preset maximum number of terminals, the core network device will send a first terminal configuration update message to the terminal device. The first terminal configuration update message carries the target network slice S-NSSA13, and the reason for rejection is limited resources. After the terminal device receives the first terminal configuration update message, the list of rejected network slices is updated as shown in the following table. The UE will not subsequently initiate a registration request in the target network slice S-NSSAI3.

[0070] reject-nssai rejection reason S-NSSAI3 resource limited After the resources of the subsequent target network slice S-NSSAI3 are released, the core network device will send a second terminal configuration update message to the terminal device, and the second terminal configuration update message carries the configured target network slice S-NSSAI3. After receiving the second terminal configuration update message, the terminal device deletes the target network slice from the rejected network slice list and updates the target network slice S-NSSAI3 to the following configured network slice list. The updated configured network slice list is shown in the following table, including S-NSSAI3. The terminal device can subsequently initiate a registration request on the target network slice S-NSSAI3.

[0071] config-nssai S-NSSAI1 S-NSSAI2 S-NSSAI3 The present disclosure also provides a network slice configuration device, Figure 4 The structure block diagram of a network slice configuration device applied to a core network device provided by an embodiment of the present disclosure is shown. The device can be implemented as part or all of an electronic device through software, hardware, or a combination of both. Figure 4 As shown, the network slice configuration device includes:

[0072] The first monitoring module 401 is configured to monitor whether each network slice managed by the core network device is resource-constrained; The first configuration module 402 is configured to send a first terminal configuration update message to the terminal device served by the core network device when there is a target network slice with limited resources in each of the network slices. The first terminal configuration update message is used to notify the target network slice that the resources are limited, so that the terminal device updates the target network slice to the rejected network slice list and deletes the target network slice from the configured network slice list. The rejection reason corresponding to the target network slice in the rejected network slice list is resource limitation.

[0073] In one possible implementation, the network slice configuration device may be applied to a core network device capable of performing network slice configuration, and the core network device includes an AMF.

[0074] In a possible implementation, the first monitoring module 401 of the core network device can monitor in real time whether each network slice in the network managed by the core network device is resource-constrained. Resource limitation here means that the available resources in the network slice are limited and cannot meet more user needs.

[0075] In a possible implementation, when the first monitoring module 401 detects that resources of a target network slice are limited, the first configuration module 402 may send a first terminal configuration update message to each terminal device served by the core network device, where the first terminal configuration update message is used to notify the target network slice that resources are limited.

[0076] In a possible implementation manner, several network slices that can be recorded in the terminal device are introduced below: Configured NSSAI (Configured Network Slicing): The network is configured to provide network slices that the terminal device can request to use. The terminal device will maintain a configured network slice list, which records the network slices that the terminal device can request to use; Request NSSAI (Request Network Slice): The network slice requested by the terminal device in the registration request message. The requested network slice can be selected from the configured network slice list. Allowed NSSAI (Allowed Network Slice): The network slice that the terminal device is allowed to use after successfully registering can be carried in the registration reception message after the core network device receives the registration request message and returns it to the terminal device; the terminal device will maintain an allowed network slice list, which records the network slices that the terminal device is currently allowed to use; only the allowed network slices that are allowed to be registered can be used to establish a PDU session later; rejected NSSAI (rejected network slice): The network slice that the terminal device is not allowed to use when registering can be returned to the terminal device by the core network device in the registration reception message after receiving the registration request message; the terminal device will maintain a rejected network slice list, which records the rejected network slices that the terminal device is not currently allowed to use and the reasons for rejection.

[0077] In this way, after the terminal device receives the first terminal configuration update message, it can update the resource-constrained target network slice to the rejected network slice list, where the rejection reason corresponding to the target network slice in the rejected network slice list is resource limitation, and delete the target network slice in the configured network slice list at the same time. In this way, when selecting a requested network slice from the configured network slice list, the resource-constrained target network slice cannot be selected; in this way, the terminal device is prevented from initiating an invalid registration request on an unavailable network slice.

[0078] In this implementation mode, the core network device can monitor in real time whether each network slice managed by the core network device is resource-constrained, and when a target network slice in each network slice is resource-constrained, send a first terminal configuration update message to the terminal device served by the core network device, wherein the first terminal configuration update message is used to notify the target network slice that the resources are limited, so that the terminal device updates the target network slice to the rejected network slice list and deletes the target network slice from the configured network slice list. The rejection reason corresponding to the target network slice in the rejected network slice list is resource limitation. In this way, when the terminal device performs network slice registration and selects the requested network slice later, it will not select the resource-constrained target network slice, thereby avoiding the terminal device initiating an invalid registration request on the resource-constrained network slice and reducing the signaling burden of the network.

[0079] In a possible implementation, the device further includes: A second monitoring module is configured to monitor whether the resources of the target network slice are released; The second configuration module is configured to send a second terminal configuration update message to the terminal device served by the core network device when the resources of the target network slice are released, and the second terminal configuration update message is used to notify the target network slice resource release so that the terminal device deletes the target network slice from the rejected network slice list and updates the target network slice to the configured network slice list.

[0080] In this embodiment, after notifying the terminal device that the resources of the target network slice are limited, the second monitoring module will also monitor in real time whether the resources of the target network slice are released. Here, the resource release of the network slice refers to the process of returning the previously allocated or occupied resources to an available state. If the resources of the target network slice are released, it means that there are available resources on the target network slice. At this time, the second configuration module can send a second terminal configuration update message to the terminal device served by the core network device. The second terminal configuration update message is used to notify the release of the target network slice resources. At this time, correspondingly, the terminal device can delete the target network slice from the rejected network slice list and update the target network slice to the configured network slice list. In this way, when the terminal device performs network slice registration and selects the requested network slice later, it can promptly select the target network slice from the configured network slice list as the requested network slice for registration.

[0081] This embodiment can also notify the terminal device after the target network slice resources are released so that the terminal device can promptly select the target network slice for registration request.

[0082] In a possible implementation manner, the first configuration module is configured to: Sending a first terminal configuration update message to a target terminal device, wherein a configured network slice list of the target terminal device includes the target network slice; The second configuration module is configured to: Send a second terminal configuration update message to the target terminal device.

[0083] In this implementation, there are many terminal devices served by the core network device, and some terminal devices may not be configured with the target network slice by the network, that is, regardless of whether the resources of the target network slice are limited, these terminal devices themselves will not initiate a registration request using the unlabeled network slice as a request network slice. Therefore, in order to reduce the signaling burden of the network, the first configuration module can send a first terminal configuration update message to the target terminal device, which refers to the device that includes the target network slice in the configured network slice list, to avoid these terminal devices configured with the target network slice from initiating invalid network slice registration. Correspondingly, if the target network slice resources are released later, the second configuration module will also send a second terminal configuration update message to these target terminal devices.

[0084] In a possible implementation manner, the first configuration module is configured to: Sending the first terminal configuration update message to the terminal device that has requested the core network device to register the target network slice; The second configuration module is configured to: The second terminal configuration update message is sent to the terminal device that has requested to register the target network slice to the core network device.

[0085] In this implementation, among the terminal devices served by the core network device, if there is a terminal device that has requested the core network device to register the target network slice, it means that the terminal device has been configured with the target network slice by the network. Therefore, in order to reduce the signaling burden of the network, the first configuration module can send the first terminal configuration update message to the terminal devices that have requested the core network device to register the target network slice, so as to avoid these terminal devices configured with the target network slice from initiating invalid network slice registration. Correspondingly, if the target network slice resources are released later, the second configuration module will also send a second terminal configuration update message to these terminal devices that have requested the core network device to register the target network slice.

[0086] In a possible implementation, the first monitoring module is configured as follows: When it is monitored that the number of terminals served by the network slice has reached a preset maximum number of terminals or the number of protocol data unit PDU sessions established on the network slice has reached a preset maximum number of PDU sessions, it is determined that the network slice resources are monitored to be limited.

[0087] In this embodiment, the resource limitation of the network slice refers to that the number of terminals served by the network slice has reached the preset maximum number of terminals or the number of PDU sessions established on the network slice has reached the preset maximum number of PDU sessions. When the first monitoring module monitors that the number of terminals served by the network slice has reached the preset maximum number of terminals or the number of PDU sessions established on the network slice has reached the preset maximum number of PDU sessions, it determines that the network slice resources are limited; when it monitors that the number of terminals served by the network slice has not reached the preset maximum number of terminals or the number of PDU sessions established on the network slice has not reached the preset maximum number of PDU sessions, it monitors that the network slice is not resource limited. If, after the first monitoring module monitors that the target network slice resources are limited, the second monitoring module monitors that the number of terminals served by the target network slice has not reached the preset maximum number of terminals or the number of PDU sessions established on the network slice has not reached the preset maximum number of PDU sessions, then the network slice resources are released.

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

[0089] The first receiving unit 501 is configured to receive a first terminal configuration update message sent by a core network device, where the first terminal configuration update message is used to notify the target network slice that resources are limited; The first update unit 502 is configured to update the target network slice to the rejected network slice list and delete the target network slice from the configured network slice list, and the rejection reason corresponding to the target network slice in the rejected network slice list is resource limitation.

[0090] In one possible implementation, the network slicing configuration apparatus may be applied to a terminal device capable of performing network slicing configuration, which terminal device may be a station in a WLAN, a cellular phone, a cordless phone, a session initiation protocol phone, a wireless local loop station, a personal digital processing device, a handheld device with wireless communication capabilities, a computing device or other processing device 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 network, or a terminal device in a future evolving public land mobile network, and the like.

[0091] In a possible implementation, the core network device can monitor in real time whether each network slice in the network managed by the core network device is resource-constrained, where resource limitation refers to the limited resources available in the network slice, which cannot meet more user needs. When it is detected that a target network slice is resource-constrained, the core network device can send a first terminal configuration update message to each terminal device it serves, and the first terminal configuration update message is used to notify the target network slice that the resources are limited.

[0092] In a possible implementation manner, several network slices that can be recorded in the terminal device are introduced below: Configure network slices: The network is configured to provide network slices that the terminal device can request to use. The terminal device will maintain a list of configured network slices, which records the network slices that the terminal device can request to use; Requested network slice: The network slice requested by the terminal device in the registration request message. The requested network slice can be selected from the configured network slice list. Allowed network slices: The network slices that are allowed to be used after the terminal device successfully registers can be returned to the terminal device in the registration reception message after the core network device receives the registration request message; the terminal device will maintain an allowed network slice list, which records the network slices that the terminal device is currently allowed to use; only the allowed network slices that are allowed to be registered can be used to establish a PDU session later; Rejected network slices: Network slices that are not allowed to be used when the terminal device registers. After the core network device receives the registration request message, it can be carried in the registration reception message and returned to the terminal device; the terminal device will maintain a rejected network slice list, which records the rejected network slices that the terminal device is currently not allowed to use and the reasons for rejection.

[0093] In this way, after the first receiving unit 501 receives the first terminal configuration update message, the first updating unit 502 can update the resource-constrained target network slice to the rejected network slice list, where the rejection reason corresponding to the target network slice in the rejected network slice list is resource limitation, and delete the target network slice in the configured network slice list at the same time. In this way, when selecting a requested network slice from the configured network slice list, the resource-constrained target network slice cannot be selected; in this way, the terminal device is prevented from initiating an invalid registration request on an unavailable network slice.

[0094] In this implementation mode, the core network device can monitor in real time whether each network slice managed by the core network device is resource-constrained, and when a target network slice in each network slice is resource-constrained, send a first terminal configuration update message to the terminal device served by the core network device, wherein the first terminal configuration update message is used to notify the target network slice that the resources are limited, so that the terminal device updates the target network slice to the rejected network slice list and deletes the target network slice from the configured network slice list. The rejection reason corresponding to the target network slice in the rejected network slice list is resource limitation. In this way, when the terminal device performs network slice registration and selects the requested network slice later, it will not select the resource-constrained target network slice, thereby avoiding the terminal device initiating an invalid registration request on the resource-constrained network slice and reducing the signaling burden of the network.

[0095] In a possible implementation, the device further includes: A second receiving unit is configured to receive a second terminal configuration update message sent by the core network device, where the second terminal configuration update message is used to notify the target network slice resource release; The second updating unit is configured to delete the target network slice from the rejected network slice list and update the target network slice to the configured network slice list.

[0096] In this embodiment, after notifying the terminal device that the resources of the target network slice are limited, the core network device will also monitor in real time whether the resources of the target network slice are released. Here, the resource release of the network slice refers to the process of returning the previously allocated or occupied resources to an available state. If the resources of the target network slice are released, it means that there are available resources on the target network slice. At this time, the core network device can send a second terminal configuration update message to the terminal device served by the core network device. The second terminal configuration update message is used to notify the release of the target network slice resources. At this time, correspondingly, the second update unit of the terminal device can delete the target network slice from the rejected network slice list and update the target network slice to the configured network slice list. In this way, when the terminal device performs network slice registration and selects the requested network slice later, it can promptly select the target network slice from the configured network slice list as the requested network slice for registration.

[0097] This embodiment can also notify the terminal device after the target network slice resources are released so that the terminal device can promptly select the target network slice for registration request.

[0098] In a possible implementation, the device further includes: The registration request module is configured to send a registration request message to the core network device if the target network slice corresponding to the application currently running on the terminal device is not in the allowed network slice list. The registration request message carries a requested network slice, and the requested network slice is the target network slice corresponding to the application from the configured network slice list.

[0099] In this embodiment, some network slices may require that the terminal device does not need to register in the network slice when there is no application request, and only initiates registration and PDU session establishment when there is an application demand. Therefore, when the network slice corresponding to the application currently running on the terminal device is the target network slice, but is not in the allowed network slice list, the terminal device needs to initiate network slice registration. At this time, the registration request module can send a registration request message to the core network device, and the registration request message carries the requested network slice. The requested network slice is the target network slice corresponding to the application selected from the configured network slice list. When the target network slice is successfully registered by the core network device and the allowed network slice carried in the returned registration reception message is the target network slice, the application currently running on the terminal device can establish a PDU session in the target network slice.

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

[0101] like Figure 6 As shown, the electronic device 600 includes a memory 601 and a processor 602, wherein the memory 601 is used to store one or more computer instructions, wherein the one or more computer instructions are executed by the processor 602 to implement the method according to the embodiment of the present disclosure. When the electronic device is a core network device, the one or more computer instructions are executed by the processor to implement the network slice configuration method applied to the core network device, and when the electronic device is a terminal device, the one or more computer instructions are executed by the processor to implement the network slice configuration method applied to the terminal device.

[0102] Figure 7 A schematic diagram showing the structure of a computer system suitable for implementing the method of the embodiment of the present disclosure is shown.

[0103] like Figure 7 As shown, the computer system 700 includes a processing unit 701, which can perform various processes in the above-mentioned embodiments according to a program stored in a read-only memory (ROM) 702 or a program loaded from a storage part 708 into a 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. An input / output (I / O) interface 705 is also connected to the bus 704.

[0104] 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 installed 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), and an NPU (Neural network Processing Unit); among them, the CPU is mainly used to interpret computer instructions and process 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 processor based on neural network algorithms and acceleration.

[0105] In particular, 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, which includes computer instructions, and the computer instructions are executed by a processor to 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 part 709, and installed from the removable medium 711.

[0106] The flowchart and block diagram in the accompanying drawings illustrate the possible architecture, functions and operations of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of a code, and the module, a program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and the flowchart, and the combination of the boxes in the block diagram and the flowchart can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0107] The units or modules involved in the embodiments described in the present disclosure may be implemented by software or programmable hardware. The units or modules described may also be set in a processor, and the names of these units or modules do not constitute limitations on the units or modules themselves in some cases.

[0108] As another aspect, the present disclosure further provides a computer-readable storage medium, which may be a computer-readable storage medium included in the electronic device or computer system in the above embodiment; or a computer-readable storage medium that exists independently and is not assembled into a device. The computer-readable storage medium stores one or more programs, and the programs are used by one or more processors to execute the method described in the present disclosure.

[0109] The above description is only a preferred embodiment of the present disclosure and an explanation of the technical principles used. Those skilled in the art should understand that the scope of the invention involved in the present disclosure is not limited to the technical solution formed by a 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, the above features are replaced with the technical features with similar functions disclosed in the present disclosure (but not limited to) by each other.

Claims

1. A network slice configuration method, characterized in that: Applied to a core network device, the method comprises: Monitoring whether each network slice managed by the core network device is resource-constrained; When there is a target network slice with limited resources in each network slice, a first terminal configuration update message is sent to the terminal device served by the core network device, wherein the first terminal configuration update message is used to notify the target network slice that the resources are limited, so that the terminal device updates the target network slice to the rejected network slice list and deletes the target network slice from the configured network slice list, and the rejection reason corresponding to the target network slice in the rejected network slice list is limited resources.

2. The method according to claim 1, characterized in that After sending the first terminal configuration update message to the terminal device served by the core network device, the method further includes: Monitoring whether resources of the target network slice are released; When the resources of the target network slice are released, a second terminal configuration update message is sent to the terminal device served by the core network device, and the second terminal configuration update message is used to notify the target network slice resource release so that the terminal device deletes the target network slice from the rejected network slice list and updates the target network slice to the configured network slice list.

3. The method according to claim 2, characterized in that The sending a first terminal configuration update message to the terminal device served by the core network device includes: Sending a first terminal configuration update message to a target terminal device, wherein a configured network slice list of the target terminal device includes the target network slice; The sending a second terminal configuration update message to the terminal device served by the core network device includes: Send a second terminal configuration update message to the target terminal device.

4. The method according to claim 2, characterized in that: The sending a first terminal configuration update message to the terminal device served by the core network device includes: Sending the first terminal configuration update message to the terminal device that has requested the core network device to register the target network slice; The sending a second terminal configuration update message to the terminal device served by the core network device includes: The second terminal configuration update message is sent to the terminal device that has requested to register the target network slice to the core network device.

5. The method according to claim 1, characterized in that The monitoring whether each network slice managed by the core network device is resource-constrained includes: When it is monitored that the number of terminals served by the network slice has reached a preset maximum number of terminals or the number of protocol data unit PDU sessions established on the network slice has reached a preset maximum number of PDU sessions, it is determined that the network slice resources are monitored to be limited.

6. A network slice configuration method, characterized in that: Applied to a terminal device, the method comprises: Receive a first terminal configuration update message sent by a core network device, where the first terminal configuration update message is used to notify a target network slice that resources are limited; The target network slice is updated to the rejected network slice list and the target network slice is deleted from the configured network slice list, wherein the rejection reason corresponding to the target network slice in the rejected network slice list is resource limitation.

7. The method according to claim 6, characterized in that After receiving the first terminal configuration update message sent by the core network device, the method further includes: Receive a second terminal configuration update message sent by the core network device, where the second terminal configuration update message is used to notify the target network slice resource release; The target network slice is deleted from the rejected network slice list and the target network slice is updated to the configured network slice list.

8. The method according to claim 7, characterized in that After receiving the second terminal configuration update message sent by the core network device, the method further includes: If the target network slice corresponding to the application currently running on the terminal device is not in the list of allowed network slices, a registration request message is sent to the core network device, and the registration request message carries a requested network slice, and the requested network slice is the target network slice corresponding to the application in the configured network slice list.

9. A network slice configuration device, characterized in that: Applied to core network equipment, the device includes: A first monitoring module is configured to monitor whether each network slice managed by the core network device is resource-constrained; The first configuration module is configured to send a first terminal configuration update message to the terminal device served by the core network device when there is a target network slice with limited resources in each of the network slices. The first terminal configuration update message is used to notify the target network slice that the resources are limited, so that the terminal device updates the target network slice to the rejected network slice list and deletes the target network slice from the configured network slice list. The rejection reason corresponding to the target network slice in the rejected network slice list is resource limitation.

10. The device according to claim 9, characterized in that The device also includes: A second monitoring module is configured to monitor whether the resources of the target network slice are released; The second configuration module is configured to send a second terminal configuration update message to the terminal device served by the core network device when the resources of the target network slice are released, and the second terminal configuration update message is used to notify the target network slice resource release so that the terminal device deletes the target network slice from the rejected network slice list and updates the target network slice to the configured network slice list.

11. The device according to claim 10, characterized in that The first configuration module is configured to: Sending a first terminal configuration update message to a target terminal device, wherein a configured network slice list of the target terminal device includes the target network slice; The second configuration module is configured as follows: Send a second terminal configuration update message to the target terminal device.

12. The device according to claim 10, characterized in that The first configuration module is configured to: Sending the first terminal configuration update message to the terminal device that has requested the core network device to register the target network slice; The second configuration module is configured as follows: The second terminal configuration update message is sent to the terminal device that has requested to register the target network slice to the core network device.

13. The device according to claim 9, characterized in that The first monitoring module is configured as follows: When it is monitored that the number of terminals served by the network slice has reached a preset maximum number of terminals or the number of protocol data unit PDU sessions established on the network slice has reached a preset maximum number of PDU sessions, it is determined that the network slice resources are monitored to be limited.

14. A network slice configuration device, characterized in that: Applied to a terminal device, the device comprises: A first receiving unit is configured to receive a first terminal configuration update message sent by a core network device, where the first terminal configuration update message is used to notify a target network slice that resources are limited; The first updating unit is configured to update the target network slice to the rejected network slice list and delete the target network slice from the configured network slice list, wherein the rejection reason corresponding to the target network slice in the rejected network slice list is resource limitation.

15. The device according to claim 14, characterized in that The device also includes: A second receiving unit is configured to receive a second terminal configuration update message sent by the core network device, where the second terminal configuration update message is used to notify the target network slice resource release; The second updating unit is configured to delete the target network slice from the rejected network slice list and update the target network slice to the configured network slice list.

16. The device according to claim 15, characterized in that The device also includes: The registration request module is configured to send a registration request message to the core network device after receiving a second terminal configuration update message sent by the core network device, if the target network slice corresponding to the application currently running on the terminal device is not in the allowed network slice list, wherein the registration request message carries a requested network slice, and the requested network slice is the target network slice corresponding to the application in the configured network slice list.

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

18. 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 6 to 8.

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

Images