Network slice admission control method and device

By introducing access control methods for access and mobility management network elements in 5G network slices, the problem of terminal equipment access when the number of network slice access users reaches the maximum value is solved, and stable registration and service communication of terminal equipment are realized.

CN120034910APending Publication Date: 2025-05-23HUAWEI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202510045646.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2021-03-29
Publication Date
2025-05-23

AI Technical Summary

Technical Problem

In the 5G network slice deployment scenario, due to network resource limitations, a network slice can only accommodate a limited number of users. When the number of terminal devices access reaches the maximum, how to ensure that the terminal devices can still access network slices has become an urgent problem.

Method used

By implementing the access control method in the access and mobility management network elements, when the number of terminal devices requested by the terminal device to access reaches the maximum value, the terminal device is allowed to access the default contracted network slice, thereby avoiding registration failure.

Benefits of technology

It is realized that the terminal device access can still be ensured when the number of network slice access users reaches the maximum value, which improves the terminal device registration success rate, and ensures that the terminal device can conduct business communication in a timely manner.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120034910A_ABST
    Figure CN120034910A_ABST
Patent Text Reader

Abstract

The invention discloses a network slice admission control method and device, and the method comprises the steps that UE sends a registration request message to an AMF, the AMF receives the registration request message, and the registration request message carries the identification information of a network slice which the UE requests to access. When the number of UEs needing to execute access control in the network slices requested to be accessed by the UE is larger than or equal to a first threshold value, the AMF sends a registration acceptance message carrying identification information of a first network slice to the UE, the first network slice is a network slice allowing the UE to be accessed, and the UE receives the registration acceptance message. According to the method provided by the invention, the UE can still be ensured to be successfully registered and accessed to the network slice under the condition that the number of the UE accessed to the network slice needing to execute admission control in the network slice requested to be accessed by the UE is greater than or equal to the first threshold value.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application. The application number of the original application is 202110336606.2, and the original application date is March 29, 2021. The entire contents of the original application are incorporated into this application by reference. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to a method and device for access control of a network slice. Background Art

[0003] In the fifth-generation (5G) communication system, hundreds of billions of IoT devices will be connected to the network. Different application scenarios have different requirements for the network, and some even conflict with each other. Providing services for different application scenarios through a single network will lead to an extremely complex network architecture and low network management efficiency and resource utilization efficiency.

[0004] Therefore, network slicing technology provides isolated network environments for different application scenarios by creating virtual independent logical networks on the same network infrastructure, so that different application scenarios can customize network functions and features according to their own needs, thereby effectively guaranteeing the quality of service (QoS) requirements of different services. The goal of 5G network slicing is to organically combine terminal devices, access network resources, core network resources, and network operation and maintenance and management systems to provide independent operation and maintenance and isolated networks for different application scenarios or business types.

[0005] In the actual deployment scenario of slices, due to limitations such as network resources, the number of users that a network slice can accommodate is limited. Therefore, when the number of users accessing the network slice reaches the maximum, how to ensure that the terminal devices can access the network slice needs to be solved urgently. Summary of the invention

[0006] The present application provides a network slicing access control method and device, which can ensure that the terminal device can access the network slice when the number of terminal devices accessing the network slice to which the terminal device requests access reaches a certain number (such as the maximum access number).

[0007] In a first aspect, an embodiment of the present application provides a method for controlling admission of a network slice, the method comprising:

[0008] An access and mobility management network element receives a registration request message from a terminal device, where the registration request message carries identification information of a network slice that the terminal device requests to access; when the number of terminal devices that need to perform admission control on the network slice that the terminal device requests to access is greater than or equal to a first threshold, the access and mobility management network element sends a registration acceptance message carrying identification information of a first network slice to the terminal device, where the first network slice is a network slice that allows the terminal device to access.

[0009] In the embodiment of the present application, the access and mobility management network element may also be referred to as a network element or device having access and mobility management functions, etc. For example, the access and mobility management network element may be an access and mobility management function (AMF) network element in a 5G network architecture.

[0010] The network slice that the terminal device requests to access may be one network slice, or may be at least two network slices, such as two or three network slices. It is understandable that although the first threshold is used in the embodiments of the present application to measure whether the network slice that needs to perform access control in the network slice requested by the terminal device still allows access to the terminal device, when the number of network slices that need to perform access control in the network slice requested by the terminal device is two or more, whether the first thresholds corresponding to the two or more network slices are the same is not limited in the embodiments of the present application. In other words, if the network slices that need to perform access control in the network slice requested by the terminal device are network slice 1 and network slice 2, the first threshold used to measure network slice 1 may be different from the first threshold used to measure network slice 2.

[0011] Exemplarily, the network slices that the terminal device requests to access and that need to perform admission control include the second network slice. Then the number of terminal devices accessed by the second network slice is greater than or equal to the first threshold, which can also be understood as: the number of terminal devices currently accessed by the second network slice is greater than or equal to the first threshold; the number of terminal devices already accessed by the second network slice exceeds the quota; or the number of terminal devices already accessed by the second network slice exceeds the quota; or the second network slice cannot allow new terminal devices to access; or the number of terminal devices already accessed by the second network slice reaches the maximum number allowed to access (i.e., the first threshold). Since the number of terminal devices accessed by the second network slice is greater than or equal to the first threshold, the terminal device cannot access the second network slice.

[0012] It can be understood that the first network slice shown in the embodiment of the present application may be a network slice that does not belong to the network slice requested by the terminal device carried in the registration request message.

[0013] Generally, if the number of terminal devices that have accessed the network slices that require access control in the network slice requested by the terminal device exceeds the quota, the terminal device cannot access these network slices, resulting in a registration failure of the terminal device. However, in an embodiment of the present application, even if the number of terminal devices that have accessed the network slices that require access control in the network slice requested by the terminal device exceeds the quota, the terminal device still has a network slice that can be accessed, such as the first network slice, so that not only the terminal device registration is successful, but also the terminal device can be guaranteed to perform service communications in a timely manner through the first network slice.

[0014] In a possible implementation, the first network slice is the default subscribed network slice of the terminal device.

[0015] Generally, the contract information (also referred to as contract data) of a terminal device includes a default contracted network slice. When the number of terminal devices accessing a network slice that needs to be accessed by the terminal device in the network slice that requires access control is greater than or equal to a first threshold, the number of terminal devices accessing the default contracted network slice of the terminal device may not reach a certain number, or the default contracted network slice does not need to perform access control. In this case, the terminal device accesses the default contracted network slice, which not only avoids the situation where the terminal device registration fails, but also enables the terminal device to access the network slice in a timely manner, thereby ensuring the service quality of the terminal device.

[0016] In a possible implementation, the method also includes: the access and mobility management network element determines to allow the terminal device to access the default subscribed network slice.

[0017] In an embodiment of the present application, if the default subscribed network slice does not need to perform admission control, the access and mobility management network element may determine at least one first network slice from one or more default subscribed network slices as a network slice that allows terminal devices to access. If the first network slice needs to perform admission control, the access and mobility management network element may, after confirming that the number of terminal devices accessed by the default subscribed network slice is less than a second threshold, determine at least one first network slice from one or more default subscribed network slices whose number of accessed terminal devices is less than the second threshold as a network slice that allows terminal devices to access.

[0018] In a possible implementation manner, the access and mobility management network element determines to allow the terminal device to access the default subscription network slice, including:

[0019] The access and mobility management network element is configured with first information, wherein the first information is used to indicate that when the number of terminal devices accessing the network slice for which access control needs to be performed in the network slice requested to be accessed by the terminal device is greater than or equal to the first threshold, the terminal device is allowed to access the default subscribed network slice; the access and mobility management network element determines, based on the first information, that the terminal device is allowed to access the default subscribed network slice.

[0020] In a possible implementation manner, the access and mobility management network element determines to allow the terminal device to access the default subscription network slice, including:

[0021] The access and mobility management network element sends a first request message to the unified data management network element; the access and mobility management network element receives a first response message from the unified data management network element, the first response message carries the identification information of the default subscribed network slice and first indication information, the first indication information is used to indicate that when the number of terminal devices accessing the network slice that the terminal device requests to access and that requires access control is greater than or equal to a first threshold, the terminal device is allowed to access the default subscribed network slice; the access and mobility management network element determines, based on the first indication information, that the terminal device is allowed to access the default subscribed network slice.

[0022] In a possible implementation manner, the access and mobility management network element determines to allow the terminal device to access the default subscription network slice, including:

[0023] The access and mobility management network element determines whether to allow the terminal device to access the default subscribed network slice based on the subscription information of the terminal device, wherein the subscription information of the terminal device includes first indication information, and the first indication information is used to indicate that when the number of terminal devices that need to perform access to the network slice that the terminal device requests to access is greater than or equal to a first threshold, the terminal device is allowed to access the default subscribed network slice.

[0024] In one possible implementation, the number of terminal devices accessing the first network slice is less than a second threshold.

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

[0026] The access and mobility management network element sends a second request message to the first network element, the second request message carries the identification information of the network slice that needs to perform admission control in the network slice that the terminal device requests to access and the identification information of the default subscribed network slice; the access and mobility management network element receives a second response message from the first network element, the second response message carries second indication information and third indication information, the second indication information is used to indicate that the number of terminal devices accessing the network slice that needs to perform admission control in the network slice that the terminal device requests to access is greater than or equal to the first threshold, and the third indication information is used to indicate that the number of terminal devices accessing the default subscribed network slice is less than the second threshold.

[0027] In an embodiment of the present application, the access and mobility management network element can simultaneously obtain the number of terminal devices accessing the first network slice and the number of terminal devices accessing the network slice that the terminal device requests to access and that needs to perform access control through the second request message. Thus, when the number of terminal devices accessing the network slice that needs to perform access control in the network slice that the terminal device requests to access is greater than or equal to the first threshold, the access and mobility management network element can determine that the first network slice is a network slice that allows terminal devices to access based on the number of terminal devices accessing the default contracted network slice. This can not only ensure that the terminal device can access the first network slice, avoiding the situation where the terminal device registration fails; but also because the access and mobility management network element can determine the first network slice by interacting with the first network element once (i.e., the second request message and the second response message), the efficiency of signaling interaction is improved.

[0028] In a possible implementation, the second request message also includes fourth indication information, and the fourth indication information is used to indicate that when the number of terminal devices accessing the network slice that requires access control in the network slice requested by the terminal is greater than or equal to the first threshold, the admission control of the default contracted network slice is triggered (which can also be understood as activation).

[0029] In a possible implementation, the second request message also includes fifth indication information, and the fifth indication information is used to instruct the first network element to determine the first network slice from multiple default subscribed network slices, or the fifth indication information is used to instruct the first network element to count terminal devices only for the first network slice among multiple default subscribed network slices.

[0030] In a possible implementation, the first network slice is the network slice with the least number of access terminal devices among the multiple default subscribed network slices.

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

[0032] When the number of terminal devices accessing the network slice that needs to perform admission control in the network slice requested to be accessed by the terminal device is greater than or equal to the first threshold, the access and mobility management network element sends a third request message to the first network element, and the third request message carries the identification information of the default subscribed network slice; the access and mobility management network element receives a third response message from the first network element, and the third response message carries third indication information, and the third indication information is used to indicate that the number of terminal devices accessing the default subscribed network slice is less than the second threshold.

[0033] In a possible implementation, the third request message also includes sixth indication information, and the sixth indication information is used to instruct the first network element to determine the first network slice from multiple default subscribed network slices, or the sixth indication information is used to instruct the first network element to count terminal devices only for the first network slice among multiple default subscribed network slices.

[0034] In a possible implementation, the first network slice is the network slice with the least number of access terminal devices among the multiple default subscribed network slices.

[0035] In one possible implementation, the first network slice is a network slice that does not need to perform admission control.

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

[0037] The access and mobility management network element sends a subscription request message to the first network element, and the subscription request message carries the identification information of the network slice that the terminal device requests to access and the identification information of the terminal device; the access and mobility management network element receives a first notification message from the first network element, and the first notification message carries seventh indication information, and the seventh indication information is used to indicate that the number of terminal devices accessing the second network slice in the network slice that the terminal device requests to access and needs to perform admission control is less than the first number threshold; the access and mobility management network element sends a second notification message to the terminal device, and the second notification message carries the identification information of the second network slice.

[0038] In the embodiment of the present application, when the number of UEs accessing the second network slice is less than the first threshold, it is ensured that the UE can access the second network slice in a timely and effective manner. Thus, the fairness of the UE accessing the network slice is also effectively guaranteed, so that the UE can access the network slice it requests to access.

[0039] In a second aspect, an embodiment of the present application provides a network slice admission control method, the method comprising:

[0040] The terminal device sends a registration request message to the access and mobility management network element, where the registration request message carries identification information of the network slice that the terminal device requests to access;

[0041] The terminal device receives a registration acceptance message from the access and mobility management network element, where the registration acceptance message carries identification information of a first network slice, and the first network slice is a network slice that the terminal device is allowed to access.

[0042] In a possible implementation, the first network slice is the default subscribed network slice of the terminal device.

[0043] In one possible implementation, the number of terminal devices accessing the first network slice is less than a second threshold.

[0044] In a possible implementation, the first network slice is the network slice with the least number of access terminal devices among the multiple default subscribed network slices.

[0045] In one possible implementation, the first network slice is a network slice that does not need to perform admission control.

[0046] In a third aspect, an embodiment of the present application provides a communication device for executing the method in the first aspect or any possible implementation of the first aspect. The communication device includes a corresponding unit for executing the method in the first aspect or any possible implementation of the first aspect.

[0047] Exemplarily, the communication device may be an access and mobility management network element or a chip in the access and mobility management network element.

[0048] In a fourth aspect, an embodiment of the present application provides a communication device for executing the method in the second aspect or any possible implementation of the second aspect. The communication device includes a corresponding method for executing the method in the second aspect or any possible implementation of the second aspect.

[0049] Exemplarily, the communication device may be a terminal device or a chip in the terminal device, etc.

[0050] In the third aspect or the fourth aspect, the communication device may include a transceiver unit and a processing unit. For a detailed description of the transceiver unit and the processing unit, reference may also be made to the device embodiment shown below.

[0051] In a fifth aspect, an embodiment of the present application provides a communication device, the communication device comprising a processor, configured to execute the method described in the first aspect or any possible implementation of the first aspect. Alternatively, the processor is configured to execute a program stored in a memory, and when the program is executed, the method described in the first aspect or any possible implementation of the first aspect is executed.

[0052] In the process of executing the above method, the process of sending a message (such as sending a registration acceptance message or a first request message, etc.) in the above method can be understood as the process of the processor outputting the above message. When the processor outputs the above message, the processor outputs the above message to the transceiver so that the transceiver can transmit it. After the above message is output by the processor, it may also need to undergo other processing before it reaches the transceiver. Similarly, when the processor receives an input message (such as receiving a registration request message or a first response message, etc.), the transceiver receives the above message and inputs it into the processor. Furthermore, after the transceiver receives the above message, the above message may need to undergo other processing before it is input into the processor.

[0053] It can be understood that, for the operations such as transmission, sending and receiving involved in the processor, unless otherwise specified, or if they do not conflict with their actual functions or internal logic in the relevant descriptions, they can be more generally understood as processor output, reception, input and other operations, rather than transmission, sending and receiving operations directly performed by the RF circuit and antenna.

[0054] In the implementation process, the above-mentioned processor can be a processor specifically used to execute these methods, or it can be a processor that executes computer instructions in a memory to execute these methods, such as a general-purpose processor. The above-mentioned memory can be a non-transitory memory, such as a read-only memory (ROM), which can be integrated with the processor on the same chip, or can be respectively arranged on different chips. The embodiment of the present application does not limit the type of memory and the arrangement of the memory and the processor. It is understandable that the description of the processor and the memory is also applicable to the sixth aspect shown below, and the sixth aspect will not be described in detail for the convenience of repeating.

[0055] In a possible implementation manner, the memory is located outside the above communication device.

[0056] In a possible implementation manner, the memory is located within the above-mentioned communication device.

[0057] In the embodiment of the present application, the processor and the memory may also be integrated into one device, that is, the processor and the memory may also be integrated together.

[0058] In a possible implementation manner, the communication device further includes a transceiver, where the transceiver is used to receive a signal or send a signal.

[0059] For example, the transceiver may be used to receive a registration request message and send a registration acceptance message. For another example, the transceiver may be used to send a first request message and receive a first response message. For another example, the transceiver may be used to send a second request message and receive a second response message, etc., which will not be described in detail here.

[0060] In the embodiment of the present application, the communication device may be an access and mobility management network element or a chip in an access and mobility management network element, etc.

[0061] In a sixth aspect, an embodiment of the present application provides a communication device, the communication device comprising a processor, configured to execute the method described in the second aspect or any possible implementation of the second aspect. Alternatively, the processor is configured to execute a program stored in a memory, and when the program is executed, the method described in the second aspect or any possible implementation of the second aspect is executed.

[0062] In a possible implementation manner, the memory is located outside the above communication device.

[0063] In a possible implementation manner, the memory is located within the above-mentioned communication device.

[0064] In the embodiment of the present application, the processor and the memory may also be integrated into one device, that is, the processor and the memory may also be integrated together.

[0065] In a possible implementation manner, the communication device further includes a transceiver, where the transceiver is used to receive a signal or send a signal.

[0066] In the embodiment of the present application, the communication device may be a terminal device or a chip in the terminal device, etc.

[0067] In a seventh aspect, an embodiment of the present application provides a communication device, the communication device comprising a logic circuit and an interface, the logic circuit and the interface are coupled; the interface is used to input a registration request message and output a registration acceptance message. It is understandable that the logic circuit can be used to process the input registration request message, etc., and the embodiment of the present application does not limit the specific implementation of the logic circuit.

[0068] For example, the logic circuit is used to determine that the first network slice is a candidate network slice for the network slice that allows the terminal device to access.

[0069] For another example, the interface is further used to output a second request message and input a second response message.

[0070] For another example, the interface is further used to output a third request message and input a third response message.

[0071] For another example, the interface is also used to output a subscription request message, input a first notification message, and output a second notification message, etc.

[0072] It is understandable that for the specific description of the logic circuit and the interface, reference may also be made to the device embodiment shown below, which will not be described in detail here.

[0073] In an eighth aspect, an embodiment of the present application provides a communication device, which includes a logic circuit and an interface, wherein the logic circuit and the interface are coupled; the interface is used to output a registration request message and input a registration acceptance message.

[0074] The logic circuit is used to process the input registration acceptance message, etc. The embodiment of the present application does not limit the specific implementation of the logic circuit.

[0075] In the seventh and eighth aspects, for the description of the first network slice, the registration request message, the registration acceptance message, the first request message, the first response message, the second request message, the second response message, the third request message, the third response message, the subscription request message, the first notification message and the second notification message, etc., refer to the description of the first or second aspect above; or, refer to the various embodiments shown below, which will not be described in detail here.

[0076] In a ninth aspect, an embodiment of the present application provides a computer-readable storage medium, which is used to store a computer program. When the computer-readable storage medium is run on a computer, the method shown in the above-mentioned first aspect or any possible implementation of the first aspect is executed.

[0077] In the tenth aspect, an embodiment of the present application provides a computer-readable storage medium, which is used to store a computer program. When the computer-readable storage medium is run on a computer, the method shown in the above-mentioned second aspect or any possible implementation of the second aspect is executed.

[0078] In the eleventh aspect, an embodiment of the present application provides a computer program product, which includes a computer program or a computer code. When the computer program product is run on a computer, the method shown in the above-mentioned first aspect or any possible implementation of the first aspect is executed.

[0079] In a twelfth aspect, an embodiment of the present application provides a computer program product, which includes a computer program or a computer code. When the computer program product runs on a computer, the method shown in the above-mentioned second aspect or any possible implementation of the second aspect is executed.

[0080] In a thirteenth aspect, an embodiment of the present application provides a computer program. When the computer program runs on a computer, the method shown in the above-mentioned first aspect or any possible implementation of the first aspect is executed.

[0081] In a fourteenth aspect, an embodiment of the present application provides a computer program. When the computer program runs on a computer, the method shown in the above-mentioned second aspect or any possible implementation of the second aspect is executed.

[0082] In the fifteenth aspect, an embodiment of the present application provides a wireless communication system, which includes an access and mobility management network element and a terminal device, wherein the access and mobility management network element is used to execute the method shown in the above-mentioned first aspect or any possible implementation of the first aspect, and the terminal device is used to execute the method shown in the above-mentioned second aspect or any possible implementation of the second aspect.

[0083] In the sixteenth aspect, an embodiment of the present application provides a wireless communication system, which includes an access and mobility management network element and a first network element, wherein the access and mobility management network element is used to execute the method shown in the above-mentioned first aspect or any possible implementation of the first aspect, and the first network element is used to perform admission control on network slices, etc. For the specific implementation method of the first network element, you can refer to the above-mentioned first aspect, or you can refer to the method embodiment shown below, etc.

[0084] In a seventeenth aspect, an embodiment of the present application provides a wireless communication system, the wireless communication system comprising an access and mobility management network element, a first network element, and a terminal device. For the specific implementation of the access and mobility management network element, the first network element, and the terminal device, reference may be made to the first and second aspects above, or to the method embodiments shown below. BRIEF DESCRIPTION OF THE DRAWINGS

[0085] Figure 1 is a schematic diagram of a communication system provided in an embodiment of the present application;

[0086] Figure 2 is another schematic diagram of a communication system provided in an embodiment of the present application;

[0087] Figure 3 It is a flowchart of a registration method provided in an embodiment of the present application;

[0088] Figure 4 It is a flowchart of a network slice admission control method provided in an embodiment of the present application;

[0089] Figure 5a to Figure 5c This is a flowchart of a method for determining that a UE is allowed to access a default contracted network slice provided in an embodiment of the present application;

[0090] Figures 6 to 8 It is a flowchart of a network slice admission control method provided in an embodiment of the present application;

[0091] Figures 9 to 11 It is a structural diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0092] In order to make the objectives, technical solutions and advantages of the present application clearer, the present application will be further described below in conjunction with the accompanying drawings.

[0093] The terms "first" and "second" in the specification, claims and drawings of this application are only used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units that are not listed, or may optionally include other steps or units that are inherent to these processes, methods, products or devices.

[0094] The "embodiment" mentioned in this article means that the specific features, structures or characteristics described in conjunction with the embodiment can be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It can be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0095] In the present application, "at least one (item)" means one or more, "more than one" means two or more, "at least two (items)" means two or three and more than three, and "and / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c".

[0096] The technical solution provided in this application can be applied to various communication systems, such as: long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), Internet of Things (IoT) system, narrowband Internet of Things (NB-IoT) system, wireless fidelity (WiFi), fifth generation (5G) communication system or new radio (NR) and other future communication systems, such as the sixth generation mobile communication system.

[0097] The terms involved in this application are introduced in detail below.

[0098] 1. Terminal equipment

[0099] The terminal device in this application is a device with wireless transceiver function. The terminal device can communicate with one or more core network (CN) devices (or core devices) via the access network device (or access device) in the radio access network (RAN). The terminal device can also be called user equipment (UE), access terminal, terminal, subscriber unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, user agent or user device, etc. In one possible implementation, the terminal device can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on the water (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.). In one possible implementation, the terminal device can be a handheld device with wireless communication function, a vehicle-mounted device, a wearable device, an Internet of Things, a terminal in the Internet of Vehicles, a fifth generation (5G) network, and any form of terminal device in the future network, etc., and this application does not limit this.

[0100] The terminal device shown in this application may include not only vehicles (such as complete vehicles) in the Internet of Vehicles, but also vehicle-mounted devices or vehicle-mounted terminals in the Internet of Vehicles. This application does not limit the specific form of the terminal device when applied to the Internet of Vehicles.

[0101] For ease of description, the terminal device shown below will take UE as an example to illustrate the method provided in this application.

[0102] 2. AMF

[0103] As mobile broadband access services expand, mobile networks will also develop to better support diverse business models, meet more diverse application services and the needs of more industries. For example, in order to provide better and more complete services to more industries, 5G networks have made adjustments to the network architecture compared to 4G networks. For example, the 5G network splits the mobility management entity (MME) in the 4G network into multiple network elements (or network functions), including access and mobility management function (AMF) and session management function (SMF).

[0104] The AMF shown in this application is a control plane network function provided by the PLMN, which is responsible for the access control and mobility management of the UE accessing the PLMN, including, for example, mobile state management, allocation of user temporary identity, authentication and authorization of users, etc. Therefore, with the development of mobile networks, even if the AMF may evolve into other forms or names, etc., as long as the method shown in this application can be implemented, it belongs to the protection scope of this application.

[0105] For ease of description, the access and mobility management network element shown below will take AMF as an example to illustrate the method provided in this application.

[0106] 3. First Network Element

[0107] The first network element shown in this application can be used for admission control of network slices. For example, the first network element can control and / or monitor the number of terminal devices accessing a network slice that requires admission control, so as to ensure that the total number of terminal devices currently accessing the network slice does not exceed the maximum number of terminal devices allowed to access this network slice (maximum number of UEs per network slice). For example, the first network element can also save the number of terminal devices currently accessing the network slice, or save the list of identifiers of the terminal devices currently accessing the network slice (which can also be called the first identifier list), etc. The identifiers in this first identifier list are used to identify the terminal devices currently accessing the network slice. For another example, the first network element can also configure the maximum value of the number of terminal devices allowed to access the network slice, that is, the first network element can configure the maximum number of users allowed to access the network slice (maximum number of UEs per network slice).

[0108] Exemplarily, the method for the first network element to perform admission control on a network slice can be: If a terminal device (such as terminal device 1) requests to access a network slice that requires admission control, the first network element checks whether the first identifier list (that is, the identifier list of the terminal devices already accessing a network slice that requires admission control requested by this terminal device 1) already contains the identifier of terminal device 1. If the identifier of terminal device 1 is not in this first identifier list, it further checks whether the number of terminal devices identified in the first identifier list has reached the maximum value of the number of terminal devices allowed to access this network slice. If it has not reached this maximum value (which can also be called the maximum number of users), the first network element increments by 1 the number of terminal devices currently accessing this network slice and adds the identifier of terminal device 1 to the first identifier list. If it has reached this maximum value, the terminal device is not allowed to access this network slice.

[0109] Exemplarily, the method for the first network element to perform admission control on a network slice can be: If a terminal device (such as terminal device 2) requests to access a network slice that requires admission control, the first network element checks whether the number of terminal devices accessing this network slice has reached the maximum value. If it has not reached this maximum value, the first network element increments by 1 the number of terminal devices currently accessing this network slice and adds the identifier of this terminal device 2 to the identifier list of the terminal devices already accessing this network slice.

[0110] It can be understood that the first network element shown in this application can also perform admission control on network slices according to other methods, which are not limited in this application.

[0111] Exemplarily, the first network element may include a network slice admission control (NSAC) network element, or a network slice admission control function (NSACF) network element, etc. The present application does not limit the specific name of the first network element. The terminal device that has accessed the network slice described in the present application can also be understood as a terminal device that has registered the network slice. And the number of terminal devices that have accessed the network slice described in the present application can also be understood as the number of registered users on the network slice.

[0112] For ease of description, the method provided by this application will be explained below using the first network element being NSACF as an example.

[0113] Based on the communication device shown above, the present application also provides a communication system. Figure 1 As shown, Figure 1 1 is a schematic diagram of a communication system of an embodiment of the present application. The network architecture may include three parts, namely, a terminal device part, a public land mobile network (PLMN) and a data network (DN). The PLMN described in the present application may specifically be a network that complies with the standard requirements of the third generation partnership project (3GPP), referred to as a 3GPP network. The 3GPP network generally includes but is not limited to the fifth generation mobile communication (5th-generation, 5G) network (referred to as 5G network), the fourth generation mobile communication (4th-generation, 4G) network (referred to as 4G network), etc. The data network DN 120, which may also be referred to as a packet data network (PDN), is generally a network located outside the PLMN, such as a third-party network. Exemplarily, the PLMN may access multiple data network DNs 120, and a variety of services may be deployed on the data network DN 120, thereby providing services such as data and / or voice to the terminal device UE 110.

[0114] like Figure 1As shown, the PLMN may include: NSACF 131, network slice selection function (NSSF) 132, policy control function (PCF) 133, unified data management (UDM) 134, application function (AF) 135, authentication server function (AUSF) 136, access and mobility management function (AMF) 137, session management function (SMF) 138, user plane function (UPF) 139 and (radio) access network ((radio) access network, (R)AN) 140, etc. In the above PLMN, the part except the (radio) access network 140 part can be called the core network (CN) part or the core network part.

[0115] Among them, the unified data management UDM134 is a control plane function provided by the operator, which is responsible for storing the subscriber permanent identifier (SUPI), security context, subscription data and other information of the subscribers in the PLMN. The subscribers of the above-mentioned PLMN may specifically be users who use the services provided by the PLMN, such as users who use the terminal device chip card of China Telecom, or users who use the terminal device chip card of China Mobile, etc. Exemplarily, the SUPI of the subscriber may be the number of the terminal device chip card, etc. The above-mentioned security context may be data (cookie) or token stored on the local terminal device (such as a mobile phone). The subscription data of the above-mentioned subscriber may be the supporting services of the terminal device chip card, such as the traffic package of the mobile phone chip card, etc.

[0116] In the present application, the subscription data may include information about the subscribed network slice (also referred to as subscribed S-NSSAI). The subscription data may also include an eighth indication information, which may be used to indicate whether the subscribed S-NSSAI contained in the subscription data is a default subscribed network slice (also referred to as defaultsubscribed S-NSSAI). Alternatively, it may be understood that, according to the eighth indication information, the default subscribed network slice and the subscribed network slice may be distinguished. In other words, the default subscribed S-NSSAI may be understood as one of the subscribed S-NSSAIs, and is also a subscribed network slice. However, the default subscribed S-NSSAI may be used as a default slice. Optionally, the subscription data may also include a first indication information, which is used to indicate that when the number of UEs accessing the network slice to which the UE requests access and to which access control needs to be performed is greater than or equal to a first threshold, the UE is allowed to access the default subscribed network slice. It can be understood that the subscription data of the subscribed user may also be referred to as the subscription data of the UE, or the subscription information of the UE, etc., and the present application does not limit the specific name of the subscription data.

[0117] Understandable, Figure 1 The specific implementation methods of other network functions in the PLMN shown can refer to relevant protocols or standards, etc., and will not be described in detail in this application.

[0118] Figure 1 Among them, Nnsacf, Nnssf, Nausf, Npcf, Nudm, Naf, Namf, Nsmf, N1, N2, N3, N4, and N6 are interface serial numbers. For example, the meaning of the above interface serial numbers can be found in the meaning defined in the 3GPP standard protocol, and this application does not limit the meaning of the above interface serial numbers. It should be noted that, Figure 1 In the example, only the terminal device 110 is used as the UE. Figure 1 The interface name between the various network functions is just an example. In a specific implementation, the interface name of the system architecture may also be other names, and this application does not limit this.

[0119] Figure 1 The network architecture (eg, 5G network architecture) shown in the embodiment adopts a service-based architecture and a service-based interface. The method shown in the present application can also be applied to a point-to-point interface, such as Figure 2 As shown. Understandably, Figure 2N1, N2, N3, N4, N5, N6, N7, N8, N10, N11, N12, N13, N15, N22, N60, N61, etc. shown in are interface serial numbers. For example, the meaning of the above interface serial numbers can refer to the meaning defined in the 3GPP standard protocol, and this application does not limit the meaning of the above interface serial numbers.

[0120] Understandable, Figure 1 and Figure 2 The communication system shown is only an example. By way of example, the communication system may also include a network repository function (NRF) or a network slice-specific authentication and authorization function (NSSAAF), etc. The present application does not limit the specific architecture of the communication system.

[0121] 4. Network Slicing

[0122] Slicing can be simply understood as cutting the operator's physical network into multiple virtual end-to-end networks. Each virtual network (including the equipment, access network, transmission network and core network within the network) is logically independent, and a failure in any virtual network will not affect other virtual networks. In order to meet diverse needs and isolation between slices, relatively independent management and operation and maintenance of services are required, and tailored business functions and analysis capabilities must be provided. Instances of different business types can be deployed on different network slices, and different instances of the same business type can also be deployed on different network slices. A slice can be composed of a set of network functions (NF) and / or sub-networks. For example, Figure 1 The subnetwork (R)AN 140, AMF 137, SMF 138, and UPF 139 in the CAN bus can form a slice. It can be understood that Figure 1 In the figure, only one network function is shown schematically. In actual network deployment, there may be multiple, dozens or even hundreds of network functions or subnetworks. Many slices can be deployed in a PLMN, and each slice can have different performance to meet the needs of different applications and vertical industries.

[0123] 5. Single network slice selection assistance information (S-NSSAI)

[0124] A network slice can be identified by S-NSSAI, which can be distinguished by slice type / service type (SST), or S-NSSAI can be composed of SST and slice differentiator (SD). For example, SST is used to describe the characteristics of the slice in terms of features and services. SD is used to distinguish different network slices with the same SST characteristics.

[0125] 6. Network slice selection assistance information (NSSAI)

[0126] NSSAI is a set of S-NSSAIs, and a set of one or more network slices can be identified by NSSAI. For example, the identification information of the network slice that the UE requests to access can be called the requested NSSAI, or the requested S-NSSAI. For another example, the identification information of the allowed network slice carried in the registration acceptance message can be called the allowed NSSAI, or the allowed S-NSSAI.

[0127] It is understandable that the description of network slicing can also refer to relevant standards or protocols, etc., and this application does not limit this. The above introduction to terms also applies to the various embodiments shown below. For the sake of simplicity of the application document, it will not be repeated below.

[0128] In the deployment scenario of slices, due to limitations such as network resources, the number of users that a slice can accommodate is limited. For example, in the enhanced mobile broadband (eMBB) service, a slice can accommodate a maximum of 10 million users (UEs) accessing, while in the V2X service, a slice can accommodate a maximum of 2 million users accessing. If the number of users accessing exceeds this number, the service level agreement (SLA) of the slice cannot be guaranteed. Therefore, NSACF is required to control the number of UEs accessing the network slice. Figure 3 As shown, Figure 3 The present invention provides a flow chart of a registration method, which includes:

[0129] 301. The UE sends a registration request message to the AMF, where the registration request message carries the identification information of the requested network slice. Correspondingly, the AMF receives the registration request message.

[0130] The identification information of the requested network slice may also be referred to as requested network slice selection auxiliary information (requested NSSAI).

[0131] 302. AMF determines that the requested network slice includes a network slice that needs to perform admission control, and determines a target network slice, which is the network slice that the UE requests access to and needs to perform admission control.

[0132] The target network slice may also be referred to as the target NSSAI. For example, the target network slice may be a set of slices to which the UE requests access and for which network slice admission control needs to be performed. For example, requested NSSAI = {1, 2, 3}, and network slices {1, 2, 3} all need to perform admission control, then the AMF determines that target NSSAI = {1, 2, 3}.

[0133] 303. AMF interacts with NSACF to determine whether the quota of the target network slice (target NSSAI) has reached the maximum number of terminal devices allowed to access the target network slice.

[0134] Exemplarily, AMF may send a request message to NSACF, where the request message carries a target NSSAI, and the request message is used to request NSACF to check whether the number of terminal devices currently connected to the network slice corresponding to each S-NSSAI contained in the target NSSAI has exceeded the maximum value.

[0135] 304. If the quota of the network slice corresponding to a certain S-NSSAI contained in the target NSSAI is available, that is, the number of terminal devices currently connected to the network slice corresponding to a certain S-NSSAI contained in the target NSSAI does not exceed the maximum value, the AMF returns a registration acceptance message to the UE, and the registration acceptance message carries the identification information of the allowed network slice, wherein the identification information of the allowed network slice includes the above-mentioned S-NSSAI.

[0136] For each network slice in the target network slice, when NSACF determines that the number of UEs currently accessing the network slice does not exceed the maximum number, NSACF can count the number of users of the network slice (i.e., the number of users accessing the network slice plus one). In addition, optionally, NSACF returns indication information 1 to AMF, and the indication information 1 can be used to indicate that the number of terminal devices currently accessing the network slice has not reached the maximum value or to indicate that the network slice has an available quota (quota available), so that AMF includes the identification information of the network slice in the registration acceptance message. That is, the network slice with an available quota is an allowed network slice, and the identification information of the allowed network slice can also be referred to as an allowed NSSAI (allowed NSSAI).

[0137] 305. If the quota of the network slices included in the target NSSAI is not available, that is, the number of terminal devices currently connected to the network slice corresponding to a certain S-NSSAI included in the target NSSAI exceeds the maximum value, the AMF returns a registration reject message to the UE, and the registration reject message carries the identification information of the rejected network slice, wherein the identification information of the rejected network slice includes the above-mentioned S-NSSAI.

[0138] That is to say, NSACF returns indication information 2 to AMF, which is used to indicate that the number of terminal devices currently connected to the network slice in the target NSSAI has reached the maximum value or indicates that the quota of the network slice is unavailable. Thus, AMF includes the network slice without available quota in the registration rejection message. That is, the network slice without available quota is a rejected network slice, and the identification information of the rejected network slice can also be called rejected NSSAI (rejected NSSAI).

[0139] The quota of the network slice shown in the present application can also be understood as: the number of UEs accessed by the network slice, or the number of users allowed to access the network slice, or the number of users registered with the network slice. The quota of the network slice is unavailable, or the quota of the network slice is exceeded, or the number of UEs accessed by the network slice exceeds the quota, which can be understood as: the number of UEs accessed by the network slice exceeds the maximum value, or the number of UEs accessed by the network slice has reached the maximum number of UEs allowed to access, or the number of UEs accessed by the network slice is greater than or equal to the first threshold, or the number of UEs that have accessed the network slice is greater than or equal to the first threshold. The quota of the network slice is available, which can be understood as: the number of UEs accessed by the network slice does not exceed the maximum number, or the number of UEs accessed by the network slice does not reach the maximum number of UEs allowed to access, or the number of UEs accessed by the network slice is less than the first threshold.

[0140] The admission control shown in this application can also be called access control, etc. This application does not limit its name.

[0141] It is understandable that the above descriptions on quotas and access control of network slices are also applicable below. For the sake of simplicity of the application document, the method provided in this application will be described below using the example that the number of UEs accessing the network slice is greater than or equal to the first threshold.

[0142] It is understandable that although the first threshold is used in this application to measure whether the network slice that needs to perform admission control in the network slice requested by the UE is still allowed to access the UE, when the number of network slices that need to perform admission control in the network slice requested by the UE is two or more than two network slices, whether the first thresholds corresponding to the two or more network slices are the same is not limited in this application. In other words, if the network slices that need to perform admission control in the network slice requested by the UE are network slice 1 and network slice 2, the first threshold used to measure network slice 1 may be different from the first threshold used to measure network slice 2.

[0143] from Figure 3 It can be seen from the method shown that when the number of UEs accessing the network slice that needs to perform admission control in the network slice requested by the UE to access is greater than or equal to the first threshold, the registration of the UE will fail, which not only affects the registration process of the UE, but also causes the UE to be unable to access the network slice in a timely and effective manner.

[0144] In view of this, the present application provides a network slice admission control method and device, which can not only improve the accuracy of UE registration success, but also enable the UE to access the network slice in time. In the present application, the network slices that the UE requests to access may all need to perform admission control. Or, some of the network slices that the UE requests to access need to perform admission control, so that the UE can access another part of the network slices that do not need to perform admission control. However, when the UE requests to access a network slice that needs to perform admission control, if the number of UEs accessing the network slice that needs to perform admission control is greater than or equal to the first threshold, the UE cannot access the network slice that needs to perform admission control. When the number of UEs accessing the network slice that needs to perform admission control in the network slice that the UE requests to access is greater than or equal to the first threshold, the number of UEs accessing the default contracted network slice of the UE may not have reached the second threshold, or the default contracted network slice of the UE does not need to perform admission control. In this case, the UE can access the default contracted network slice (also referred to as the default contracted network slice) to improve the situation of UE registration failure.

[0145] The following first generally introduces the method provided in the embodiment of the present application, and then introduces each embodiment separately, and finally introduces the device provided in the embodiment of the present application in combination with the method embodiment.

[0146] Figure 4 This is a network slice admission control method provided by an embodiment of the present application. Exemplarily, the method can be applied to Figure 1 The communication system shown can also be applied to Figure 2 The communication system shown in the figure, etc., the communication system to which the method is applicable is not described in detail in the embodiment of the present application. Figure 4 As shown, the method includes:

[0147] 401. The UE sends a registration request message to the AMF, where the registration request message carries the identification information of the network slice that the UE requests to access. Correspondingly, the AMF receives the registration request message.

[0148] The network slice that the UE requests to access may be one or at least two network slices, such as two or three or more network slices. The identification information of the network slice that the UE requests to access may be referred to as the NSSAI (requested NSSAI) that the UE requests to access or the S-NSSAI (requested S-NSSAI) that the UE requests to access.

[0149] In a possible implementation manner, before the AMF sends a registration acceptance message carrying identification information of the first network slice to the UE, Figure 4 The method shown also includes:

[0150] The AMF determines the network slice on which admission control needs to be performed in the network slice that the UE requests to access.

[0151] Exemplarily, AMF can determine the network slice that needs to perform admission control in the network slice that the UE requests to access according to the following method: 1. Configure the identification information of the network slice that needs to perform admission control in AMF. That is, AMF locally configures the identification information of the network slice that needs to perform admission control, thereby, AMF can determine whether the identification information of the network slice that the UE requests to access includes the identification information of the network slice that needs to perform admission control. 2. The identification information of the network slice that needs to perform admission control is indicated in the UE's contract data. That is, AMF can determine whether the network slice that the UE requests to access includes the identification information of the network slice that needs to perform admission control based on the UE's contract data. The embodiment of the present application does not limit the method for AMF to determine the network slice that needs to perform admission control from the network slice that the UE requests to access. It can be understood that the above description is also applicable to the method for judging whether the default contracted network slice needs to perform admission control, and will not be repeated below.

[0152] 403. When the number of UEs accessing the network slices to which the UE requests access and to which access control is required is greater than or equal to a first threshold, the AMF sends a registration acceptance message carrying identification information of a first network slice to the UE, where the first network slice is a network slice to which the UE is allowed to access. Correspondingly, the UE receives the registration acceptance message.

[0153] The first network slice may be the default subscribed S-NSSAI of the UE. It may also be understood that the first network slice is included in the default subscribed network slice of the UE. Exemplarily, the identification information of the first network slice may be included in the allowed NSSAI in the registration acceptance message. Optionally, the network slice to which the UE requests access has a number of UEs accessed that is greater than or equal to a first threshold (i.e., the maximum number of UEs allowed to access has been exceeded), so the identification information of the network slice to which the UE requests access and the number of UEs accessed that is greater than or equal to the first threshold may be included in the rejected NSSAI in the registration acceptance message. It is understandable that, since the network slice to which the UE requests access requires access control to be performed, the first thresholds corresponding to each network slice may all be different. Therefore, the number of UEs accessing the network slice to which the UE requests access requires access control to be performed is greater than or equal to the first threshold, which may also be understood as: the number of UEs accessing each network slice to which the UE requests access requires access control to be performed is greater than or equal to the first threshold of the corresponding network slice. It is understandable that the above-mentioned first network slice is not included in the network slice to which the UE requests access.

[0154] In one possible implementation, Figure 4 The method shown may also include:

[0155] 402. AMF determines that the UE is allowed to access the default subscribed network slice.

[0156] For example, before the AMF sends a registration acceptance message to the UE, the AMF determines that the UE is allowed to access the default subscribed network slice. The identification information of the default subscribed network slice can be called default subscribed NSSAI, or defaultsubscribed S-NSSAI.

[0157] Exemplarily, the default contracted network slice does not need to perform admission control, that is, the first network slice is a default contracted network slice that does not need to perform admission control. Therefore, step 402 can also be replaced by: AMF determines at least one first network slice from one or more default contracted network slices. For example, AMF can determine a default contracted network slice as the first network slice from the multiple default contracted network slices. It can be understood that the description of this implementation method can also refer to the following about Figure 6 The description of them will not be described in detail here.

[0158] Exemplarily, the default subscribed network slice needs to perform admission control, that is, the first network slice is the default subscribed network slice that needs to perform admission control. Exemplarily, the number of default subscribed network slices for the UE is N, where N is an integer greater than or equal to 1. When the AMF interacts with the NSACF, the AMF may send identification information of one, M, or N default subscribed network slices to the NSACF, where M is an integer greater than 1 and less than N. The NSACF sends the identification information of the default subscribed network slices that are less than the second threshold to the AMF based on whether the number of UEs that have accessed each network slice is less than the second threshold, and the AMF determines at least one first network slice from the default subscribed network slices that are less than the second threshold. For another example, the NSACF may also determine the network slice with the least number of accessed UEs as the first network slice based on the number of UEs that have accessed each network slice, and send the identification information of the first network slice to the AMF. For another example, the number of UEs accessing the default contracted network slice sent by AMF to NSACF is less than the second threshold. In this case, NSACF may not send the identification information of the default contracted network slice to AMF, such as sending the third indication information. For the description of the third indication information, please refer to the following text and will not be described in detail here.

[0159] Exemplarily, the first network slice is a network slice in which the number of UEs that have been connected to the multiple default contracted network slices is less than the second threshold. Alternatively, if the number of network slices in which the number of UEs that have been connected to the multiple default contracted network slices is less than the second threshold is at least two, then the first network slice is any one of the at least two network slices. Alternatively, the first network slice is the network slice in which the number of UEs that have been connected to the multiple default contracted network slices is the least. It is understandable that the description of this implementation method can also refer to the following description of Figure 7 or Figure 8 The description of them will not be described in detail here.

[0160] It is understandable that the registration acceptance message may include one first network slice, or two or more first network slices. If it is allowed to feedback multiple first network slices to the UE, the registration acceptance message may also include two or more first network slices. Therefore, the embodiment of the present application does not limit the number of first network slices determined by the AMF (or NSACF) and the number of first network slices carried in the registration acceptance message. For ease of description, the following will take the registration acceptance message carrying a first network slice as an example to illustrate the method provided by the embodiment of the present application.

[0161] In an embodiment of the present application, even if the number of terminal devices accessing the network slice that needs to perform admission control in the network slice requested by the terminal device is greater than or equal to the first threshold, the terminal device can still access the network slice, such as the first network slice, thereby not only enabling the terminal device to register successfully, but also ensuring that the terminal device can conduct business communications in a timely manner through the first network slice.

[0162] It should be noted that when the default subscribed network slice needs to perform access control, and the number of UEs accessing each network slice in the default subscribed network slice of the UE is greater than or equal to the second threshold, the AMF may also return a registration rejection message to the UE. The registration rejection message includes a rejection reason value and a back off timer. In this case, it means that the network slice that needs to perform access control in the network slice requested by the UE to access can no longer allow the UE to access, and the default subscribed network slice of the UE can no longer allow the UE to access. Therefore, the UE can only initiate a registration request again after the delay timer expires.

[0163] The following details three implementation methods in which AMF determines that the UE is allowed to access the default contracted network slice.

[0164] Implementation method 1:

[0165] Figure 5a This is a flow chart of a method for determining that a UE is allowed to access a default contracted network slice provided in an embodiment of the present application. Figure 5a As shown, the method includes:

[0166] 4021. AMF configures the first information, where the first information is used to indicate that when the number of UEs that need to perform access control in the network slice requested by the UE to access is greater than or equal to the first threshold, the UE is allowed to access the default contracted network slice.

[0167] 4022. AMF determines, based on the first information, that the UE is allowed to access the default subscribed network slice.

[0168] In an embodiment of the present application, the AMF configures the first information, which may also be referred to as the AMF locally configured with the first information (may also be referred to as the AMF configured with a policy). The first information is used to indicate that when the number of UEs accessing the network slice that needs to perform admission control in the network slice that the UE requests to access is greater than or equal to the first threshold, the UE is allowed to access the default contracted network slice. That is to say, according to the first information or policy, when the number of UEs accessing the network slice that needs to perform admission control in the network slice that the UE requests to access is greater than or equal to the first threshold, the AMF may not send a registration rejection message to the UE. Instead, according to the first information or policy, it is determined to allow the UE to access the default contracted network slice. If the default contracted network slice needs to perform admission control, the first information can also be understood as: the first information is used to indicate that when the number of UEs accessing the network slice that needs to perform admission control in the network slice that the UE requests to access is greater than or equal to the first threshold, it is further confirmed whether the number of UEs currently accessing the default contracted network slice is less than the second threshold. As for whether the UE can access the default contracted network slice, it needs to be determined based on whether the number of UEs accessing the default contracted network slice is less than the second threshold.

[0169] Exemplarily, the first information may include first indication information, and the first indication information is used to indicate that when the number of UEs accessing the network slices that the UE requests to access and that need to perform admission control is greater than or equal to a first threshold, the UE is allowed to access the default subscribed network slice. It is understandable that in addition to the first indication information, the first information may also include identification information of one or more default subscribed network slices (such as default subscribed S-NSSAI, or default subscribed NSSAI).

[0170] Implementation method 2:

[0171] Figure 5b This is a flow chart of another method for determining that a UE is allowed to access a default contracted network slice provided in an embodiment of the present application. Figure 5b As shown, the method includes:

[0172] 4024. AMF sends a first request message to UDM. Correspondingly, UDM receives the first request message.

[0173] 4025. UDM sends a first response message to AMF, and accordingly, the AMF receives the first response message.

[0174] Exemplarily, the first response message carries identification information of the first network slice. Alternatively, the first response message carries identification information of one or more default subscribed network slices. In this case, the AMF can determine that the UE is allowed to access the network slice carried in the first response message. That is, when the AMF requests the UDM for the default subscribed network slice, the AMF can determine by default that the UE is allowed to access based on the default subscribed network slice in the first response message.

[0175] Exemplarily, the first response message carries identification information of the first network slice and first indication information, and the first indication information is used to indicate that when the number of UEs accessing the network slice that the UE requests to access and that need to perform admission control is greater than or equal to a first threshold, the above-mentioned UE is allowed to access the default contracted network slice. Alternatively, the first response message carries identification information and first indication information of multiple default contracted network slices. In other words, the AMF can clearly know through the first indication information that the UE can access the default contracted network slice.

[0176] Exemplarily, the first response message may also carry the subscription information of the UE, and the subscription information of the UE includes identification information and first indication information of one or more default subscription network slices. Thus, the AMF can obtain one or more default subscription network slices (such as the first network slice) from the subscription information of the UE.

[0177] 4026. AMF determines, based on the first indication information, that the UE is allowed to access the default subscribed network slice.

[0178] It can be understood that the UDM in the second implementation method can also be other network elements, such as NSSF or PCF, etc. The network element stores the identification information and / or the first indication information of the UE's default subscribed network slice, and the AMF can obtain the identification information and / or the first indication information of the UE's default subscribed network slice from the network element. The network elements all belong to the protection scope of the embodiments of the present application.

[0179] Implementation method three:

[0180] Figure 5c This is another flow chart of a method for determining that a UE is allowed to access a default contracted network slice provided in an embodiment of the present application. Figure 5c As shown, the method includes:

[0181] 4028. AMF determines, based on the UE's subscription information, that the UE is allowed to access the default subscription network slice.

[0182] The subscription information of the UE includes first indication information, and the first indication information is used to indicate that when the number of UEs accessing the network slices that require access control in the network slices requested by the UE is greater than or equal to a first threshold, the UE is allowed to access (or attempt to access) the default subscription network slice. The subscription information of the UE also includes identification information of the default subscription network slice.

[0183] The contract information of the UE may be obtained by the AMF from the UDM. For example, the AMF may obtain the contract information before step 401, after step 401, or before step 402, etc. The embodiment of the present application does not limit when the AMF obtains the contract information. It is understood that the description of the contract information can refer to the description elsewhere, which will not be repeated here.

[0184] It is understandable that the implementation methods 1 to 3 shown above can be independent implementation methods, or they can be combined. For example, implementation method 1 is combined with implementation method 2. For another example, implementation method 2 is combined with implementation method 3. That is, different implementation methods are combined with each other to ensure that AMF can effectively determine that the UE is allowed to access the default contracted network slice. For the combination between different implementation methods, you can also refer to the following Figures 6 to 8 , I will not go into details here.

[0185] Figure 6 is a flow chart of a network slice admission control method provided in an embodiment of the present application, such as Figure 6 As shown, the method includes:

[0186] 601. The UE sends a registration request message to the AMF, and the AMF receives the registration request message accordingly. The registration request message carries the identification information of the network slice that the UE requests to access (i.e., requested NSSAI).

[0187] 602. AMF sends a first request message to UDM. Correspondingly, UDM receives the first request message.

[0188] 603. UDM sends a first response message to AMF, and accordingly, AMF receives the first response message.

[0189] In an embodiment of the present application, the AMF may obtain the subscription information of the UE (also referred to as the subscription data of the UE) through steps 602 and 603. The subscription information of the UE may include identification information of the default subscription network slice. In this case, one implementation method is that the first indication information may be predefined (i.e., configured on the AMF), that is, the subscription information of the UE does not include the first indication information, and the AMF allows the UE to access the default subscription network slice. Alternatively, the subscription information of the UE may include identification information of the first network slice and the first indication information. In an embodiment of the present application, the first indication information may be used to indicate that the first network slice does not need to perform admission control. As shown in Table 1, the subscription information of the UE may include identification information of the network slice subscribed by the UE (subscribed S-NSSAI, or subscribed NSSAI), and some of the network slices subscribed by the UE may also be marked as default subscription network slices. In combination with the eighth indication information shown above, if the eighth indication information is included in the subscription network slice, the subscription network slice may also be referred to as the default subscription network slice. Table 1 also shows the first indication information in the subscription information, that is, the first indication information is used to indicate that when the number of UEs accessing the network slice requested by the UE has reached the maximum number (i.e. the maximum value), the UE is allowed to access the default subscription network slice.

[0190] It is understandable that for the description of the first response message, please refer to the above description of Figure 5b Introduction.

[0191] The above steps 602 and 603 can also be understood as: AMF obtains the UE's contract information from UDM through the NuDm_SDM_Get service operation request, and UDM calls the service operation NuDm_SDM_Get response to return the UE's contract information to AMF.

[0192] Table 1

[0193]

[0194] It can be understood that the above steps 602 and 603 are only examples. For example, AMF can also obtain the network slice of the UE's default subscription based on the configured first information. For the description of the first information, please refer to the above and will not be described in detail here.

[0195] Exemplarily, the AMF may determine the network slice that needs to be admitted to the network slice requested by the UE according to the following method: 1. The identification information of the network slice that needs to be admitted to the AMF is configured. 2. The identification information of the network slice that needs to be admitted to the UE is indicated in the subscription data of the UE. The method for determining the network slice that needs to be admitted to the network slice requested by the UE in the embodiment of the present application can also refer to Figure 4 The method shown will not be described in detail here.

[0196] For the sake of ease of description, the target NSSAI will be used below to replace the identification information of the network slice that the UE requests to access and needs to perform access control.

[0197] 604. AMF sends a fourth request message to NSACF, and accordingly, NSACF receives the fourth request message. The fourth request message carries identification information of the network slice for which admission control needs to be performed in the network slice that the UE requests to access.

[0198] 605. NSACF sends a fourth response message to AMF, and accordingly, AMF receives the fourth response message. The fourth response message carries second indication information, and the second indication information is used to indicate that the number of UEs accessing the network slice that the UE requests to access and that need to perform admission control is greater than or equal to the first threshold.

[0199] Therefore, the AMF can learn from the second indication information that the number of UEs that need to access the network slices that require admission control in the network slice requested by the UE has reached the maximum number (that is, greater than or equal to the first threshold, or has reached the maximum value), and the UE can no longer access the above network slice. Further, the AMF executes steps 606 and 607, so that the UE accesses the first network slice.

[0200] It can be understood that the above steps 604 and 605 can also be understood as: AMF calls NSACF's service-based operation such as Nnsacf_NSQuotaAvailabilityCheck_Request, and the service-based operation carries target S-NSSAI(s). NSACF determines whether the number of UEs accessing each network slice in the target S-NSSAI(s) is greater than or equal to the first threshold based on the maximum number of UEs allowed to access each network slice (max number of UEs pernetwork slice) configured locally. And NSACF calls the service-based operation Nnsacf_NSQuotaAvailabilityCheck_Response to return to AMF whether the number of UEs accessing each network slice in the target S-NSSAI(s) is greater than or equal to the first threshold (also referred to as the quota check result of each network slice in the target S-NSSAI).

[0201] As an implementation method, the fourth response message may also carry the number of UEs accessing each network slice in the target NSSAI.

[0202] It can be understood that step 604 and step 605 may be after step 602 and step 603, that is, the AMF may obtain the UE's contract information before obtaining the second indication information. Alternatively, step 604 and step 605 may be before step 602 and step 603, that is, the AMF may obtain the UE's contract information after obtaining the second indication information.

[0203] 606. AMF determines, based on the first indication information, that the UE is allowed to access the first network slice.

[0204] In an embodiment of the present application, after step 602 and step 603, the AMF may determine that the UE is allowed to access the first network slice based on the first indication information in the first response message; and then execute step 604 and step 605. Alternatively, after step 602 and step 603, the AMF may save the UE's subscription information (or save the above-mentioned first indication information, etc.); then after step 604 and step 605, the AMF determines that the UE is allowed to access the first network slice based on the UE's subscription information. Alternatively, the AMF may not obtain the first indication information through the above-mentioned steps 602 and 603, but may determine that the UE is allowed to access the first network slice through the first information configured locally. It can be understood that for the specific description of AMF determining to allow the UE to access the first network slice, reference can be made to. Figure 5a to Figure 5c , I will not go into details here.

[0205] 607. AMF sends a registration acceptance message to the UE, and correspondingly, the UE receives the registration acceptance message.

[0206] Exemplarily, the registration acceptance message may include an allowed NSSAI, which includes the identification information of the first network slice, that is, the identification information of the default subscribed S-NSSAI. Optionally, the registration acceptance message may also include a rejected NSSAI, which includes the identification information of the network slice (including the second network slice) in which the number of UEs accessed by the UE is greater than or equal to the first threshold in the network slice requested by the UE. 608. AMF sends a subscription request message to NSACF, and accordingly, NSACF receives the subscription request message. The subscription request message carries the identification information of one or more network slices in the network slice that the UE requests to access and that needs to perform access control (such as S-NSSAI or NSSAI), as well as the identification information of the UE.

[0207] The above subscription request message may carry identification information of one or more network slices, and the one or more network slices may be understood as: the network slices that the UE requests to access and that need to perform access control, and the number of UEs accessing each network slice is greater than or equal to the first threshold. Alternatively, it may also be understood as: one or more network slices in the rejected NSSAI carried in the registration acceptance message. It is understandable that the one or more network slices include the second network slice.

[0208] That is to say, the subscription request message may carry the identification information of a network slice, such as the identification information of the second network slice. For another example, the subscription request message may carry the identification information of multiple network slices, and the identification information of the multiple network slices includes the identification information of the second network slice. It can be understood that the conditions satisfied by the one or more network slices can be as shown above and will not be described in detail here.

[0209] The above step 608 can also be understood as: AMF calls a service-oriented operation such as Nnsacf_NSQuotaAvailability_Subscribe, and the service-oriented operation carries the identification information of the network slice in which the UE requests to access and the number of UEs accessed is greater than or equal to the first threshold (such as S-NSSAI in rejected NSSAI for short) and the identification information of the UE (such as UE ID). Exemplarily, through this service-oriented operation, AMF can subscribe to NSACF for an event that the number of UEs accessing one or more network slices (including the second network slice) in the rejected NSSAI is less than the first threshold (such as a quota available event).

[0210] 609. The NSACF determines that the number of UEs accessing the second network slice is less than a first threshold. The identification information of the second network slice is included in the S-NSSAI inrejected NSSAI.

[0211] When it is determined that the number of UEs accessing the second network slice is less than the first threshold (i.e., quota is available), the NSACF notifies the AMF currently serving the UE so that the UE can access the second network slice.

[0212] 610. The NSACF sends a fifth request message to the UDM, and correspondingly, the UDM receives the fifth request message. The fifth request message carries the identification information of the UE.

[0213] 611. The UDM sends a fifth response message to the NSACF, and correspondingly, the NSACF receives the fifth response message. The fifth response message carries the identification information of the AMF currently serving the UE.

[0214] The above steps 610 and 611 can also be understood as: NSACF calls the service operation of UDM, such as Nudm_UECM_Get, which carries the UE ID and AMF registration indication information, and the AMF registration indication information is used to find the AMF registered by the current UE from the UDM. That is, through the service operation, NSACF can query the UDM for the identification information of the AMF currently serving the UE.

[0215] 612. The NSACF sends a first notification message to the AMF currently serving the UE, where the first notification message carries the seventh indication information; accordingly, the AMF currently serving the UE receives the first notification message. The first notification message carries the seventh indication information, where the seventh indication information is used to indicate that the number of UEs accessing the second network slice is less than the first threshold.

[0216] Exemplarily, when the subscription request message carries identification information of a network slice, such as identification information of the second network slice, the first notification message may carry seventh indication information, as shown in step 612 above.

[0217] Exemplarily, when the subscription request message carries identification information of multiple network slices (including the second network slice), the first notification message may also carry identification information of the second network slice. In other words, the second network slice can be understood as: a network slice in the network slice that the UE requests to access that needs to perform access control, and the number of UEs accessing the second network slice is greater than or equal to the first threshold; after a period of time, the number of UEs accessing the second network slice is less than the first threshold. That is, after a period of time, the UE can access the second network slice. It can be understood that if the NSACF determines that the number of UEs accessing multiple network slices is less than the first threshold, that is, when the NSACF determines that there are multiple second network slices, the first notification message may also carry identification information of multiple second network slices.

[0218] The above step 612 can also be understood as: NSACF calls Nnsacf_NSQuotaAvailability_Notify to send a first notification message to the AMF currently serving the UE.

[0219] It is understandable that the AMF currently serving the UE may be the above-mentioned AMF or another AMF, etc., and the embodiment of the present application does not limit this. The accompanying drawings are shown as an example in which the AMF currently serving the UE is the above-mentioned AMF, but it should not be understood as a limitation on the embodiment of the present application.

[0220] 613. AMF sends a second notification message to the UE, and accordingly, the UE receives the second notification message. The second notification message carries identification information of the second network slice.

[0221] The above step 613 can also be understood as: the AMF sends a non-access stratum (NAS) message to the UE, thereby notifying the UE that the number of UEs accessed by a certain S-NSSAI in the rejected NSSAI in the registration acceptance message is less than the first threshold or notifying the UE that a certain S-NSSAI quota in the rejected NSSAI in the registration acceptance message is available.

[0222] Through the method shown in step 608 to step 613, when the number of UEs accessing the second network slice is less than the first threshold, it can be ensured that the UE can access the second network slice in a timely and effective manner. Thus, the fairness of the UE accessing the network slice is also effectively guaranteed, so that the UE can access the network slice it requests to access.

[0223] Understandable, Figure 6 Steps 608 to 613 in the same manner apply to Figure 7 and Figure 8 For example, Figure 7 In the method shown, after step 707, Figure 7 The method shown may also include steps 708 to 713. For steps 708 to 713, please refer to Figure 6 The method shown in step 608 to step 613 is shown. For another example, Figure 8 In the method shown, after step 809, Figure 8 The method shown may also include steps 810 to 815. For steps 810 to 815, please refer to Figure 6 The method shown in step 608 to step 613 is shown in the figure. To avoid redundancy, the method shown in step 608 to step 613 is not described in detail one by one below.

[0224] Through the embodiment of the present application, when the number of UEs accessing the network slice that the UE requests to access and that needs to perform admission control is greater than or equal to the first threshold, the UE is allowed to access the default contracted network slice. At the same time, the default contracted network slice does not need to perform admission control, which effectively ensures that the UE can access the default contracted network slice.

[0225] Understandable, Figure 6 The example in which the first network slice does not need to perform admission control is taken as an example. The method provided in the embodiment of the present application will be described below using the example in which the first network slice needs to perform admission control.

[0226] Figure 7 is a flow chart of a network slice admission control method provided by an embodiment of the present application, such as Figure 7 As shown, the method includes:

[0227] 701. The UE sends a registration request message to the AMF, and the AMF receives the registration request message accordingly. The registration request message carries the identification information of the network slice that the UE requests to access (i.e., requested NSSAI).

[0228] 702. AMF sends a first request message to UDM. Correspondingly, UDM receives the first request message.

[0229] 703. UDM sends a first response message to AMF, and accordingly, AMF receives the first response message.

[0230] It is understood that for the description of steps 701 to 703, please refer to Figure 6 The description of steps 601 to 603 will not be described in detail here.

[0231] 704. AMF determines, based on the first indication information, that the UE is allowed to access the default subscribed network slice.

[0232] It is understood that for the description of step 704, please refer to Figure 4 or, refer to the description of step 402 in Figure 5b The description of etc. will not be described in detail here.

[0233] 705. AMF sends a second request message to NSACF, and NSACF receives the second request message accordingly. The second request message carries the target NSSAI and the identification information of the default subscribed network slice.

[0234] In an embodiment of the present application, by carrying the identification information of the target NSSAI and the default subscribed network slice in the second request message, the NSACF can return to the AMF the number of UEs accessed by each network slice in the target NSSAI and the number of UEs accessed by the default subscribed network slice; or, the NSACF can return to the AMF whether the number of UEs accessed by each network slice in the target NSSAI is greater than or equal to the first threshold, and whether the number of UEs accessed by the default subscribed network slice is less than the second threshold. That is, after receiving the second request message, the NSACF can return the above information to the AMF by default. It can be understood that the embodiment of the present application does not limit the number of default subscribed network slices. For example Figure 4 According to the method shown, the AMF can send identification information of one, M or N default subscribed network slices to the NSACF. Exemplarily, the NSACF can determine the first network slice based on the number of UEs accessed by each default subscribed network slice.

[0235] Optionally, the second request message also includes fourth indication information, and the fourth indication information is used to indicate that when the number of UEs accessing each network slice in the targetNSSAI is greater than or equal to the first threshold, the access control of the default subscribed network slice is triggered (which can also be understood as activated). That is, by carrying the fourth indication information in the second request message, it can explicitly indicate to the NSACF to trigger the access control of the default subscribed network slice. That is, the NSACF obtains the number of UEs accessing the default subscribed network slice according to the fourth indication information, or obtains whether the number of UEs accessing the default subscribed network slice is less than the second threshold. In other words, if the number of UEs accessing the network slice in the target NSSAI is less than the first threshold, the access control of the default subscribed network slice may not be triggered.

[0236] Optionally, the second request message also includes fifth indication information, and the fifth indication information is used to instruct the NSACF to determine the first network slice from multiple default subscribed network slices. In other words, the fifth indication information is used to instruct the NSACF to count UEs only for one network slice (such as the first network slice) among multiple default subscribed network slices. The second request message can carry identification information of multiple default subscribed network slices (i.e., multiple first network slices), so that the NSACF only counts one first network slice among multiple default subscribed network slices according to the fifth indication information, that is, the number of UEs accessing the first network slice is increased by 1. It can be understood that the first network slice counted by the NSACF is the first network slice in the registration acceptance message.

[0237] 706. NSACF sends a second response message to AMF, and accordingly, AMF receives the second response message.

[0238] Optionally, the second response message carries only second indication information, and the second indication information is used to indicate that the number of UEs accessing each network slice in the targetNSSAI is greater than or equal to the first threshold. That is, the second response message may only include the second indication information, so that the AMF may consider that the number of UEs accessing the first network slice is less than the second threshold based on the second indication information.

[0239] Optionally, the second response message carries only the third indication information, and the third indication information is used to indicate that the number of UEs accessing the first network slice is less than the second threshold. Thus, the AMF can assume by default that the number of UEs accessing each network slice in the targetNSSAI is greater than or equal to the first threshold based on the third indication information.

[0240] Optionally, the second response message may carry the second indication information and the third indication information at the same time.

[0241] 707. AMF sends a registration acceptance message to the UE, and correspondingly, the UE receives the registration acceptance message.

[0242] It is understood that for the description of step 707, please refer to Figure 6 The description of step 607 in will not be repeated here.

[0243] Understandable, Figure 7 The method shown may also include steps 708 to 713. For the description of steps 708 to 713, please refer to Figure 6 Steps 608 to 613 are not described in detail here.

[0244] Through the embodiments of the present application, not only can it be ensured that the terminal device can access the first network slice, avoiding the situation where the terminal device registration fails; but also because the access and mobility management network element can determine the first network slice through one interaction with the first network element (i.e., the second request message and the second response message), the efficiency of signaling interaction is improved.

[0245] Figure 8 is a flow chart of a network slice admission control method provided by an embodiment of the present application, such as Figure 8 As shown, the method includes:

[0246] 801. The UE sends a registration request message to the AMF, and the AMF receives the registration request message accordingly. The registration request message carries the identification information of the network slice that the UE requests to access (i.e., requested NSSAI).

[0247] 802. AMF sends a first request message to UDM. Correspondingly, UDM receives the first request message.

[0248] 803. UDM sends a first response message to AMF, and accordingly, AMF receives the first response message.

[0249] 804. AMF determines, based on the first indication information, that the UE is allowed to access the default subscribed network slice.

[0250] It is understood that for the description of steps 802 to 804, please refer to Figure 7 The descriptions of steps 702 to 704 are not described in detail here.

[0251] 805. AMF sends a fourth request message to NSACF, and correspondingly, NSACF receives the fourth request message. The fourth request message carries identification information of the network slice that the UE requests to access and needs to perform admission control.

[0252] 806. NSACF sends a fourth response message to AMF, and accordingly, AMF receives the fourth response message. The fourth response message carries second indication information, and the second indication information is used to indicate that the number of UEs accessing the network slice that the UE requests to access and that need to perform admission control is greater than or equal to the first threshold.

[0253] It is understandable that the present embodiment does not limit the order of step 804 and step 805. For example, the AMF may also execute the above step 804 after receiving the fourth response message; or execute step 805 after executing the above steps 802 to 804.

[0254] It is understood that for the description of step 805 and step 806, please refer to Figure 6Steps 604 and 605 are shown and will not be described in detail here.

[0255] 807. AMF sends a third request message to NSACF, where the third request message carries the identification information of the default contracted network slice.

[0256] Optionally, the third request message also includes sixth indication information, and the sixth indication information is used to instruct the NSACF to determine a default subscribed network slice from the default subscribed network slices in which the number of accessed UEs is less than the second threshold, or the sixth indication information is used to instruct the NSACF to perform UE counting on only one default subscribed network slice (such as the first network slice) among the multiple default subscribed network slices. It can be understood that the description of the sixth indication information can be referred to Figure 7 The description of the fifth indication information will not be repeated here.

[0257] 808. NSACF sends a third response message to AMF, where the third response message carries third indication information, and the third indication information is used to indicate that the number of terminal UEs accessing the first network slice is less than the second threshold.

[0258] Optionally, the third response message may also carry identification information of the first network slice.

[0259] Optionally, the third indication information can also be used to indicate that the number of UEs accessing each network slice in the default contracted network slice is less than the second threshold. In this case, the AMF can determine one from the default contracted network slice as the first network slice.

[0260] 809. AMF sends a registration acceptance message to the UE, and correspondingly, the UE receives the registration acceptance message.

[0261] For instructions on steps 810 to 815, refer to Figure 7 , which will not be described in detail here.

[0262] Understandable, Figures 6 to 8In the method shown, when AMF needs to send a request message (such as the fourth request message, the second request message, or the third request message) to NSACF, the AMF can call a service-based operation such as Nnsacf_NSQuotaAvailabilityCheck_Request. When NSACF returns a response message (such as the fourth response message, the second response message, or the third response message) to AMF, the NSACF can call Nnsacf_NSQuotaAvailabilityCheck_Response. When AMF sends a request message (such as the first request message) to UDM, the AMF can call a service-based operation such as Nudm_SDM_Get. When UDM returns a response message (such as the first response message) to AMF, UDM can call a service-based operation such as Nudm_SDM_Get response.

[0263] In an embodiment of the present application, even if the number of terminal devices accessing the network slice that needs to perform admission control in the network slice requested by the terminal device is greater than or equal to the first threshold, the terminal device can still access the network slice, such as the first network slice, thereby not only enabling the terminal device to register successfully, but also ensuring that the terminal device can conduct business communications in a timely manner through the first network slice.

[0264] The following is an introduction to the communication device provided in the embodiments of the present application.

[0265] The present application divides the functional modules of the communication device according to the above method embodiment. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or software functional modules. It should be noted that the division of modules in the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. Figures 9 to 11 The communication device according to the embodiment of the present application is described in detail.

[0266] Fig. 9 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application, such as Fig. 9 As shown, the communication device includes a processing unit 901 and a transceiver unit 902 .

[0267] In some embodiments of the present application, the communication device may be the access and mobility management network element or AMF or a chip in the AMF shown above. That is, the communication device may be used to execute the steps or functions executed by the AMF in the above method embodiment.

[0268] The transceiver unit 902 is used to input a registration request message;

[0269] The transceiver unit 902 is used to output a registration acceptance message carrying the identification information of the first network slice when the number of UEs accessing the network slice that needs to perform admission control in the network slice requested by the UE to access is greater than or equal to a first threshold.

[0270] In an embodiment of the present application, the transceiver unit 902 is used to input a registration request message, including: the transceiver unit 902 is used to receive a registration request message from the UE. The transceiver unit 902 is used to output a registration acceptance message, including: the transceiver unit 902 is used to send the registration acceptance message to the UE. It can be understood that the description of the transceiver unit here is also applicable to the first request message and the first response message, the second request message and the second response message, the third request message and the third response message, the fourth request message and the fourth response message, etc. shown in the present application. For example, the transceiver unit 902 shown below outputs a first request message, including: the transceiver unit 902 sends a first request message to the UDM.

[0271] In one possible implementation, the processing unit 901 is used to determine whether the UE is allowed to access the default subscribed network slice.

[0272] In one possible implementation, the processing unit 901 is specifically used to configure the first information, and determine whether to allow the UE to access the default subscribed network slice based on the first information.

[0273] In one possible implementation, the processing unit 901 is used to output a first request message and input a first response message through the transceiver unit 902; the processing unit 901 is used to determine whether to allow the UE to access the default contracted network slice based on the first indication information.

[0274] In one possible implementation, the processing unit 901 is specifically used to determine whether to allow the UE to access the default subscription network slice based on the UE's subscription information.

[0275] In a possible implementation, the transceiver unit 902 is further configured to output a second request message and input a second response message.

[0276] In a possible implementation, the transceiver unit 902 is further configured to output a third request message and input a third response message.

[0277] In a possible implementation, the transceiver unit 902 is further configured to output a subscription request message, input a first notification message, and output a second notification message.

[0278] In the embodiments of the present application, for descriptions of a registration request message, a registration response message, a default subscribed network slice, a first request message, a first response message, a second request message, a second response message, a third request message, a third response message, a first indication information, a second indication information, a third indication information, a fourth indication information, a fifth indication information, a sixth indication information, a seventh indication information, a subscription request message, a first notification message, a second notification message, etc., reference may be made to the method embodiments shown above and no further details will be given here.

[0279] It is understandable that the specific description of the transceiver unit and the processing unit shown in the embodiment of the present application is only an example. For the specific functions or execution steps of the transceiver unit and the processing unit, reference can be made to the above method embodiment, which will not be described in detail here. Figure 4 In the receiving step of step 401 shown in FIG. 1 , the processing unit 901 may also be used to perform Figure 4 In step 402 shown in FIG. 1 , the transceiver unit 902 may also be used to perform Figure 4 The sending step in step 403 shown in FIG. 4 is shown in FIG. 4 . For example, the transceiver unit 902 and the processing unit 901 may also be used to perform Figures 6 to 8 The corresponding methods shown will not be described in detail here.

[0280] Reuse Fig. 9 In some other embodiments of the present application, the communication device may be the terminal device (such as UE, etc.) shown above or a chip in the terminal device, etc. That is, the communication device may be used to execute the steps or functions executed by the UE in the above method embodiment, etc.

[0281] The transceiver unit 902 is used to output a registration request message and input a registration acceptance message. Alternatively, it can also be understood that the processing unit 901 outputs a registration request message and inputs a registration acceptance message through the transceiver unit 902.

[0282] In the embodiment of the present application, the description of the registration request message and the registration acceptance message can also be referred to the introduction in the above method embodiment, which will not be described in detail here.

[0283] It can be understood that the specific description of the transceiver unit and the processing unit shown in the embodiment of the present application is only an example. For the specific functions or execution steps of the transceiver unit and the processing unit, reference can be made to the above-mentioned method embodiment, which will not be described in detail here.

[0284] The above describes the AMF and UE of the embodiment of the present application. The following describes possible product forms of the AMF and UE. It should be understood that any product having the above Fig. 9 Any product having the above-mentioned AMF function, or Fig. 9Any form of product with the functions of the UE described above falls within the protection scope of the embodiments of the present application. It should also be understood that the following introduction is only an example and does not limit the product forms of the AMF and UE of the embodiments of the present application to this.

[0285] In one possible implementation, Fig. 9 In the communication device shown, the processing unit 901 may be one or more processors, the transceiver unit 902 may be a transceiver, or the transceiver unit 902 may also be a sending unit and a receiving unit, the sending unit may be a transmitter, the receiving unit may be a receiver, and the sending unit and the receiving unit are integrated into one device, such as a transceiver. In the embodiment of the present application, the processor and the transceiver may be coupled, etc., and the embodiment of the present application does not limit the connection method between the processor and the transceiver.

[0286] like Fig.10 As shown, the communication device 100 includes one or more processors 1020 and a transceiver 1010 .

[0287] Exemplarily, when the communication device is used to execute the steps, methods or functions executed by the above-mentioned AMF, the transceiver 1010 is used to receive a registration request message and send a registration acceptance message, etc. For the specific description of the processor and the transceiver, reference can be made to the description of the processing unit and the transceiver unit shown above, which will not be repeated here.

[0288] Exemplarily, when the communication device is used to execute the steps, methods or functions executed by the above-mentioned UE, the transceiver 1010 is used to send a registration request message and receive a registration acceptance message.

[0289] In the embodiments of the present application, for descriptions of a registration request message, a registration response message, a default subscribed network slice, a first request message, a first response message, a second request message, a second response message, a third request message, a third response message, a first indication information, a second indication information, a third indication information, a fourth indication information, a fifth indication information, a sixth indication information, a seventh indication information, a subscription request message, a first notification message, a second notification message, etc., reference may be made to the method embodiments shown above and no further details will be given here.

[0290] exist Fig.10 In various implementations of the communication device shown, the transceiver may include a receiver and a transmitter, wherein the receiver is used to perform a receiving function (or operation) and the transmitter is used to perform a transmitting function (or operation). The transceiver is used to communicate with other devices / devices through a transmission medium.

[0291] Optionally, the communication device 100 may further include one or more memories 1030 for storing program instructions and / or data. The memory 1030 is coupled to the processor 1020. The coupling in the embodiment of the present application is an indirect coupling or communication connection between devices, units or modules, which may be electrical, mechanical or other forms, and is used for information exchange between devices, units or modules. The processor 1020 may operate in conjunction with the memory 1030. The processor 1020 may execute program instructions stored in the memory 1030. Optionally, at least one of the above one or more memories may be included in the processor. In the embodiment of the present application, the memory 1030 may store first information, or UE's subscription information, etc., Fig.10 Indicated by dotted line.

[0292] The specific connection medium between the transceiver 1010, the processor 1020 and the memory 1030 is not limited in the embodiment of the present application. Fig.10 In the embodiment, the memory 1030, the processor 1020 and the transceiver 1010 are connected via a bus 1040. Fig.10 The connections between the other components are shown in bold lines, which are only for illustration and are not intended to be limiting. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.10 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0293] In the embodiments of the present application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, etc., and may implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor, etc.

[0294] In the embodiment of the present application, the memory may include, but is not limited to, non-volatile memory such as a hard disk drive (HDD) or a solid-state drive (SSD), a random access memory (RAM), an erasable programmable read-only memory (EPROM), a read-only memory (ROM) or a portable read-only memory (CD-ROM), etc. The memory is any storage medium that can be used to carry or store program codes in the form of instructions or data structures and can be read and / or written by a computer (such as a communication device shown in the present application), but is not limited thereto. The memory in the embodiment of the present application can also be a circuit or any other device that can realize a storage function, for storing program instructions and / or data.

[0295] When the above-mentioned communication device is a terminal device, the processor 1020 is mainly used to process the communication protocol and communication data, and to control the entire communication device, execute the software program, and process the data of the software program. The memory 1030 is mainly used to store software programs and data. The transceiver 1010 may include a control circuit and an antenna. The control circuit is mainly used for converting baseband signals and radio frequency signals and processing radio frequency signals. The antenna is mainly used to transmit and receive radio frequency signals in the form of electromagnetic waves. Input and output devices, such as touch screens, display screens, keyboards, etc., are mainly used to receive data input by users and output data to users.

[0296] When the communication device is turned on, the processor 1020 can read the software program in the memory 1030, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be sent wirelessly, the processor 1020 performs baseband processing on the data to be sent, and outputs the baseband signal to the RF circuit. The RF circuit performs RF processing on the baseband signal and then sends the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor 1020. The processor 1020 converts the baseband signal into data and processes the data. In another implementation, the RF circuit and antenna can be set independently of the processor that performs baseband processing. For example, in a distributed scenario, the RF circuit and antenna can be independent of the communication device and arranged remotely.

[0297] It is understandable that the communication device shown in the embodiment of the present application may also have Fig.10The embodiments of the present application do not limit the number of components and the like. The methods executed by the processor and the transceiver shown above are only examples, and the specific steps executed by the processor and the transceiver can refer to the methods described above.

[0298] In another possible implementation, Fig. 9 In the communication device shown, the processing unit 901 may be one or more logic circuits, and the transceiver unit 902 may be an input / output interface, or a communication interface, or an interface circuit, or an interface, etc. Alternatively, the transceiver unit 902 may be a sending unit and a receiving unit, the sending unit may be an output interface, the receiving unit may be an input interface, and the sending unit and the receiving unit may be integrated into one unit, such as an input / output interface. Fig.11 As shown, Fig.11 The communication device shown includes a logic circuit 1101 and an interface 1102. That is, the processing unit 901 can be implemented by the logic circuit 1101, and the transceiver unit 902 can be implemented by the interface 1102. The logic circuit 1101 can be a chip, a processing circuit, an integrated circuit or a system on chip (SoC) chip, etc., and the interface 1102 can be a communication interface, an input / output interface, a pin, etc. For example, Figure 7 The above communication device is used as an example of a chip, and the chip includes a logic circuit 1101 and an interface 1102 .

[0299] In the embodiment of the present application, the logic circuit and the interface may also be coupled to each other. The embodiment of the present application does not limit the specific connection method between the logic circuit and the interface.

[0300] Exemplarily, when the communication device is used to execute the method, function or step executed by the above-mentioned AMF, the interface 1102 is used to input a registration request message and output a registration acceptance message.

[0301] In one possible implementation, logic circuit 1101 is used to determine whether the UE is allowed to access the default subscribed network slice.

[0302] In one possible implementation, the logic circuit 1101 is specifically used to configure the first information, and determine whether to allow the UE to access the default subscribed network slice based on the first information.

[0303] In one possible implementation, the logic circuit 1101 is used to output a first request message and input a first response message through the interface 1102; the logic circuit 1101 is used to determine whether to allow the UE to access the default subscribed network slice based on the first indication information.

[0304] In one possible implementation, the logic circuit 1101 is specifically used to determine whether to allow the UE to access the default subscription network slice based on the UE's subscription information.

[0305] In a possible implementation, the interface 1102 is further configured to output the second request message and input the second response message.

[0306] In a possible implementation, the interface 1102 is further configured to output a third request message and input a third response message.

[0307] In a possible implementation, the interface 1102 is further configured to output a subscription request message, input a first notification message, and output a second notification message.

[0308] In the embodiments of the present application, for descriptions of a registration request message, a registration response message, a default subscribed network slice, a first request message, a first response message, a second request message, a second response message, a third request message, a third response message, a first indication information, a second indication information, a third indication information, a fourth indication information, a fifth indication information, a sixth indication information, a seventh indication information, a subscription request message, a first notification message, a second notification message, etc., reference may be made to the method embodiments shown above and no further details will be given here.

[0309] Exemplarily, when the communication device is used to execute the method, function or step executed by the above-mentioned UE, the interface 1102 is used to output a registration request message and input a registration acceptance message.

[0310] It can be understood that the communication device shown in the embodiment of the present application can implement the method provided in the embodiment of the present application in the form of hardware, or can implement the method provided in the embodiment of the present application in the form of software, etc., and the embodiment of the present application is not limited to this.

[0311] for Fig.11 The specific implementation methods of the various embodiments shown can also refer to the above embodiments, which will not be described in detail here.

[0312] The embodiment of the present application also provides a wireless communication system, which includes an AMF and a UE, and the AMF and the UE can be used to perform any of the above embodiments (such as Figure 4 , Figure 5a to Figure 5c or Figures 6 to 8 ) in the method.

[0313] The embodiment of the present application also provides a wireless communication system, which includes an AMF and an NSACF. The AMF and the NSACF can be used to execute any of the above embodiments (such as Figure 5a to Figure 5c or Figures 6 to 8 ) in the method.

[0314] The embodiment of the present application also provides a wireless communication system, which includes an AMF, a UE and an NSACF. The AMF, the UE and the NSACF can be used to execute any of the above embodiments (such as Figure 4 , Figure 5a to Figure 5c or Figures 6 to 8 ) in the method.

[0315] In addition, the present application also provides a computer program, which is used to implement the operations and / or processing performed by the AMF in the method provided by the present application.

[0316] The present application also provides a computer program, which is used to implement the operations and / or processing performed by the UE in the method provided by the present application.

[0317] The present application also provides a computer-readable storage medium, which stores computer code. When the computer code runs on a computer, the computer executes the operations and / or processing performed by the AMF in the method provided by the present application.

[0318] The present application also provides a computer-readable storage medium, in which computer codes are stored. When the computer codes are executed on a computer, the computer executes the operations and / or processes performed by the UE in the method provided by the present application.

[0319] The present application also provides a computer program product, which includes a computer code or a computer program. When the computer code or computer program runs on a computer, the operations and / or processing performed by the AMF in the method provided by the present application are executed.

[0320] The present application also provides a computer program product, which includes a computer code or a computer program. When the computer code or the computer program runs on a computer, the operations and / or processing performed by the UE in the method provided by the present application are executed.

[0321] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, or it can be an electrical, mechanical or other form of connection.

[0322] The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the technical effects of the solutions provided in the embodiments of the present application.

[0323] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0324] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or partly contributed to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a readable storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned readable storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, etc., and other media that can store program codes.

[0325] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A network slice admission control method, It is characterized in that The method comprises: Sending a registration request message to the access and mobility management network element, where the registration request message carries identification information of the network slice that the terminal device requests to access; Receive a registration acceptance message from the access and mobility management network element, the registration acceptance message carries identification information of a first network slice, the first network slice is a network slice that allows the terminal device to access, and the number of terminal devices accessing the network slice that the terminal device requests to access and that requires access control is greater than or equal to a first threshold.

2. The method according to claim 1, It is characterized in that The first network slice is the default contracted network slice of the terminal device.

3. The method according to any one of claims 1 to 2, It is characterized in that The number of terminal devices accessing the first network slice is less than a second threshold.

4. The method according to any one of claims 1 to 3, It is characterized in that The first network slice is the network slice with the least number of access terminal devices among the multiple default contracted network slices.

5. The method according to any one of claims 1 to 4, It is characterized in that The first network slice is a network slice that does not need to perform admission control.

6. A communication device, It is characterized in that The device comprises: A transceiver unit, configured to send a registration request message to an access and mobility management network element, wherein the registration request message carries identification information of a network slice to which the terminal device requests access; The transceiver unit is also used to receive a registration acceptance message from the access and mobility management network element, the registration acceptance message carries identification information of a first network slice, the first network slice is a network slice that allows the terminal device to access, and the number of terminal devices accessing the network slice that requires access control in the network slice requested by the terminal device is greater than or equal to a first threshold.

7. The device according to claim 6, It is characterized in that The first network slice is the default contracted network slice of the terminal device.

8. The device according to any one of claims 6 to 7, It is characterized in that The number of terminal devices accessing the first network slice is less than a second threshold.

9. The device according to any one of claims 6 to 8, It is characterized in that The first network slice is the network slice with the least number of access terminal devices among the multiple default contracted network slices.

10. The device according to any one of claims 6 to 9, It is characterized in that The first network slice is a network slice that does not need to perform admission control.

11. A communication device, It is characterized in that including a processor and a memory; The processor is used to store computer-executable instructions; The processor is used to execute the computer-executable instructions so that the method according to any one of claims 1 to 5 is performed.

12. A communication device, It is characterized in that comprising a logic circuit and an interface, wherein the logic circuit and the interface are coupled; The interface is used to input and / or output code instructions, and the logic circuit is used to execute the code instructions so that the method described in any one of claims 1 to 5 is executed.

13. A computer-readable storage medium, It is characterized in that The computer-readable storage medium is used to store a computer program. When the computer program is executed, the method according to any one of claims 1 to 5 is executed.

14. A computer program product, It is characterized in that When the computer program product is executed by a computer, the method according to any one of claims 1 to 5 is executed.