WO2021088625A1 - 网络切片的使用控制方法、装置及系统 - Google Patents

网络切片的使用控制方法、装置及系统 Download PDF

Info

Publication number
WO2021088625A1
WO2021088625A1 PCT/CN2020/121644 CN2020121644W WO2021088625A1 WO 2021088625 A1 WO2021088625 A1 WO 2021088625A1 CN 2020121644 W CN2020121644 W CN 2020121644W WO 2021088625 A1 WO2021088625 A1 WO 2021088625A1
Authority
WO
WIPO (PCT)
Prior art keywords
network slice
target network
network element
area
slice
Prior art date
Application number
PCT/CN2020/121644
Other languages
English (en)
French (fr)
Inventor
李卓明
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP20884070.2A priority Critical patent/EP4040859A4/en
Publication of WO2021088625A1 publication Critical patent/WO2021088625A1/zh
Priority to US17/737,205 priority patent/US20220264428A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • H04W48/06—Access restriction performed under specific conditions based on traffic conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0226—Traffic management, e.g. flow control or congestion control based on location or mobility
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/82—Miscellaneous aspects
    • H04L47/822—Collecting or measuring resource availability data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0247—Traffic management, e.g. flow control or congestion control based on conditions of the access network or the infrastructure network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure

Definitions

  • This application relates to the field of communication technology, and in particular to a method, device and system for controlling the use of network slicing.
  • a network slice is a logically isolated network used to support specific network capabilities and network characteristics. It can include the entire end-to-end (E2E) network, or part of the network functions can be in multiple network slices. Sharing is a key technology to meet the needs of the 5th generation (5G) mobile communication technology for network differentiation proposed by the 3rd generation partnership project (3GPP).
  • 5G 5th generation
  • 3GPP 3rd generation partnership project
  • the network characteristics of different network slices are not the same, and the network slices are required to be isolated from each other without affecting each other.
  • the network slicing of augmented reality (AR) or virtual reality (VR) services requires large bandwidth and low latency services
  • the network slicing of Internet of Things (IOT) services requires massive terminal access , But the bandwidth is small and there is no requirement for delay.
  • AR augmented reality
  • VR virtual reality
  • IOT Internet of Things
  • the network operator completes the creation and deployment of the network slice, and then adds the control data of the network slice in the user data repository (UDR) network element, for example, the maximum number of registered terminals of the network slice, The maximum number of session connections.
  • the policy control function (PCF) network element controls the number of currently registered terminals not to exceed the maximum number of registered terminals of the network slice in the registration management process, and controls the number of currently established session connections not to exceed the number of network slices in the session management process. The maximum number of session connections.
  • the terminal device is mobile.
  • the mobility of terminal devices may result in very dense terminal devices in a certain area in the network slice or very sparse terminal devices in a certain area in the network slice. If the terminal equipment in a certain area of the network slice is very dense, it is easy to cause congestion of the wireless side network nodes, which not only cannot guarantee the service quality of this network slice, but may also affect the service quality of other network slices.
  • the embodiments of the present application provide a method, device, and system for controlling the use of network slicing, which can limit the excessive use of network slicing resources by customers, guarantee the service quality of network slicing, and improve the utilization efficiency of network resources.
  • the embodiments of the present application adopt the following technical solutions:
  • a method for controlling the use of a network slice includes: a first network element receives a first message for requesting a terminal device to access a target network slice, wherein the target network The slice covers multiple areas, the multiple areas include a first area, and the first area is the area where the terminal device is currently located; the first network element determines whether the terminal device is connected to the target network slice according to the first condition, Wherein, the first condition includes: whether the service usage of the target network slice in the first area exceeds the first service quota. Since the target network slice in the embodiment of the present application covers multiple areas, the first network element can determine whether to access the terminal device to the target network slice according to the first condition.
  • the first condition includes: whether the service usage of the target network slice in the first area exceeds the first service quota.
  • the embodiments of the present application implement sub-regional control of network slicing access, and therefore can avoid congestion or overload of wireless side network nodes in the region, not only cannot guarantee the service quality of this network slice, but may also slice other networks. This can limit the excessive use of network slicing resources by customers, and at the same time guarantee the service quality of network slicing.
  • the first network element determines whether the terminal device is connected to the target network slice according to the first condition, including: when the service usage of the target network slice in the first area reaches or exceeds When the first service quota is reached, the first network element rejects the first message.
  • the first condition further includes: whether the overall service usage of the target network slice exceeds the overall quota.
  • the first network element determines whether the terminal device is connected to the target network slice according to the first condition, including: when the target network slice does not exceed the service usage in the first area The first service quota, but when the overall service usage of the target network slice reaches or exceeds the overall quota, the first network element rejects the first message.
  • the method further includes: the first network element receives a second message from a second network element, the second message carries first information, and the first information indicates the overall service usage of the target network slice The amount meets or exceeds the overall limit. Based on this solution, the first network element can learn that the overall service usage of the target network slice reaches or exceeds the overall quota.
  • the first information is that the quota of service usage in the first area is 0, or the first information is that the overall service usage of the target network slice reaches or exceeds that of the target network slice. An indication of the overall limit.
  • the first network element is a mobility management network element
  • the second network element is a slice selection function network element or a policy control network element
  • the first message is a registration request.
  • the first network element is a mobility management network element
  • the second network element is a slice selection function network element
  • the first message is a session establishment request.
  • the first network element is a session management network element
  • the second network element is a policy control network element
  • the first message is a session establishment request.
  • the method further includes: the first network element receives a third message from a third network element, the third message carrying the overall service usage of the target network slice; and the first network element determines the target The overall service usage of the network slice reaches or exceeds the overall quota of the target network slice. Based on this solution, the first network element can learn that the overall service usage of the target network slice reaches or exceeds the overall quota.
  • the first network element is a policy control network element
  • the third network element is a unified data management network element
  • the first message is an associated registration management policy request or an associated session management policy request.
  • the first network element determines whether the terminal device is connected to the target network slice according to the first condition, including: when the overall service usage of the target network slice reaches or exceeds the overall limit, but When the service usage of the target network slice in the first area does not exceed the first service quota, if the second condition is met, the first network element allows the terminal device to use the target network slice.
  • the first condition including: when the overall service usage of the target network slice reaches or exceeds the overall limit, but When the service usage of the target network slice in the first area does not exceed the first service quota, if the second condition is met, the first network element allows the terminal device to use the target network slice.
  • the terminal equipment in a certain area of the network slice is very sparse, the area may have a lot of free resources, but because the service usage of the entire network slice exceeds the specified limit, the terminal equipment in this area will also be Restricting access causes a waste of resources in this area.
  • the first network element allows the terminal device to use the target network slice.
  • the user can be allowed in the first area under certain scenarios. Regions use target network slicing resources, so the utilization of network resources can be improved, which can not only bring more economic benefits to operators, but also improve the business experience of value users.
  • the first network element is a policy control network element
  • the first message is an associated registration management policy request or an associated slice management policy request
  • the second condition includes: slice subscription information of the target network slice
  • the overall limit is allowed in the target network slice, or the billing method of the target network slice is by session or by traffic, or the service type contracted by the target network slice is a specific service type, or when the terminal device requesting access is a high-value customer , Or the slice operation analysis or prediction result of the target network slice shows that it is lower than a specific threshold, or the mobile behavior analysis prediction result of the terminal device requesting access indicates that the service load of the terminal device requesting access is lower than the specific threshold.
  • the method further includes: when the first network element receives an associated slice management policy request from a slice selection function network element, the first network element determines that the target network slice is in the first area The business usage of does not exceed the first business quota. Based on this solution, the first network element can learn that the service usage of the target network slice in the first area does not exceed the first service quota.
  • the first network element is a policy control network element
  • the first message is an associated session management policy request
  • the second condition includes: the overall limit is allowed to be exceeded in the slice subscription information of the target network slice, Or the charging method of the target network slice is by session or by traffic, or the service type contracted by the target network slice is a specific service type, or the terminal device requesting access is a high-value customer, or the target network slice is The overall number of sessions and traffic bandwidth is lower than the overload risk threshold, or the QoS parameters of the terminal device’s contract indicate that the terminal device’s business is allowed to be preempted, or the slice operation analysis or prediction result of the target network slice shows that it is lower than a specific threshold. Or the mobile or communication behavior analysis and prediction result of the terminal device requesting access indicates that the service load of the terminal device requesting access is lower than a specific threshold.
  • the method further includes: when the first network element receives an associated session management policy request from a session management network element, the first network element determines that the target network slice is in the first area The business usage does not exceed the first business quota. Based on this solution, the first network element can learn that the service usage of the target network slice in the first area does not exceed the first service quota.
  • the first network element is a mobility management network element
  • the first message is a registration request
  • the second condition includes: when the slice selection function network element indicates that the overall service usage of the target network slice reaches Or when the overall quota is exceeded, the quota for the number of sessions indicated by the slice selection function network element exceeds the specified number.
  • the method further includes: when the first network element receives the session quantity quota from the slice selection function network element and the overall service usage of the target network slice reaches or exceeds the target network slice When the overall quota is indicated, the first network element determines that the overall service usage of the target network slice reaches or exceeds the overall quota. Based on this solution, the first network element can learn that the service usage of the target network slice in the first area does not exceed the first service quota.
  • the first network element is a session management network element
  • the first message is a session establishment request
  • the second condition includes: when the policy control network element indicates that the overall service usage of the target network slice reaches Or when the overall quota is exceeded, the service QoS parameter of the terminal device indicated by the policy control network element indicates that the session can be preempted.
  • the method further includes: when the first network element receives the service QoS parameters of the terminal device from the policy control network element and the overall service usage of the target network slice reaches or exceeds the target network When the overall limit of the slice is indicated, the first network element determines that the overall service usage of the target network slice reaches or exceeds the overall limit. Based on this solution, the first network element can learn that the service usage of the target network slice in the first area does not exceed the first service quota.
  • the first network element is a mobility management network element, and the first message is a registration request; or, the first network element is a session management network element, and the first message is a session establishment request;
  • the The second condition includes: the operating load of the target network slice in the first area is lower than the specified threshold; or, the overall operating load of the target network slice is lower than the specified threshold, or the target network slice is in the network of the first area Performance is higher than the specified threshold.
  • the overall service usage of the target network slice is the actual overall number of registered terminals of the target network slice, and the overall quota of the target network slice is the The maximum number of registered terminals allowed by the target network slice as a whole.
  • the overall service usage of the target network slice is the actual overall number of concurrent sessions of the target network slice, and the overall limit of the target network slice is The maximum number of concurrent sessions allowed by the target network slice as a whole.
  • the overall service usage of the target network slice is the actual overall traffic bandwidth of the target network slice, and the overall quota of the target network slice is the target network slice.
  • the service usage of the target network slice in the first area includes the actual number of registered terminals of the target network slice in the first area
  • the first service quota includes the maximum number of registered terminals allowed by the target network slice in the first area.
  • the service usage of the target network slice in the first area includes the actual concurrent sessions of the target network slice in the first area
  • the first service quota includes the maximum number of concurrent sessions allowed by the target network slice in the first area.
  • the service usage of the target network slice in the first area includes the actual traffic bandwidth of the target network slice in the first area
  • the first service quota includes the maximum traffic bandwidth allowed by the target network slice in the first area.
  • a communication device for implementing the above-mentioned various methods.
  • the communication device may be the first network element in the foregoing first aspect, or a device including the foregoing first network element.
  • the communication device includes a module, unit, or means corresponding to the foregoing method, and the module, unit, or means can be realized by hardware, software, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules or units corresponding to the above-mentioned functions.
  • a communication device including: a processor and a memory; the memory is used to store computer instructions, and when the processor executes the instructions, the communication device executes the method described in any of the above aspects.
  • the communication device may be the first network element in the foregoing first aspect, or a device including the foregoing first network element.
  • a communication device including: a processor; the processor is configured to couple with a memory, and after reading an instruction in the memory, execute the method according to any of the foregoing aspects according to the instruction.
  • the communication device may be the first network element in the foregoing first aspect, or a device including the foregoing first network element.
  • a computer-readable storage medium stores instructions that, when run on a computer, enable the computer to execute the method described in any of the above aspects.
  • a computer program product containing instructions which when running on a computer, enables the computer to execute the method described in any of the above aspects.
  • a communication device for example, the communication device may be a chip or a chip system
  • the communication device includes a processor for implementing the functions involved in any of the foregoing aspects.
  • the communication device further includes a memory for storing necessary program instructions and data.
  • the communication device is a chip system, it may be composed of chips, or may include chips and other discrete devices.
  • a communication system in an eighth aspect, includes a first network element and a network element interacting with the first network element. Wherein, the first network element is used to execute the use control method of network slicing as described in the first aspect.
  • the technical effects brought about by the eighth aspect can be referred to the technical effects brought about by the above-mentioned first aspect, which will not be repeated here.
  • FIG. 1 is a schematic structural diagram of a communication system provided by an embodiment of this application.
  • Fig. 2 is a schematic diagram of the application of the communication system shown in Fig. 1 in a 5G network;
  • FIG. 3 is a schematic structural diagram of a communication device provided by an embodiment of the application.
  • FIG. 4 is a schematic flowchart of a method for controlling the use of network slices according to an embodiment of the application
  • FIG. 5 is a schematic diagram 1 of the interaction flow of a method for controlling the use of network slices according to an embodiment of the application;
  • FIG. 6 is a schematic diagram 2 of the interaction flow of a method for controlling the use of network slices according to an embodiment of the application;
  • FIG. 7 is a third schematic diagram of the interaction process of the method for controlling the use of network slices according to an embodiment of the application.
  • FIG. 8 is a fourth schematic diagram of the interaction process of the method for controlling the use of network slices according to an embodiment of this application.
  • FIG. 9 is a fifth schematic diagram of the interaction process of the method for controlling the use of network slices according to an embodiment of the application.
  • FIG. 10 is a sixth schematic diagram of the interaction flow of the method for controlling the use of network slices according to an embodiment of the application.
  • FIG. 11 is a schematic diagram 7 of the interaction process of a method for controlling the use of network slices according to an embodiment of the application.
  • FIG. 12 is a schematic structural diagram of a first network element provided by an embodiment of this application.
  • At least one item (a) refers to any combination of these items, including any combination of a single item (a) or a plurality of items (a).
  • at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple .
  • words such as “first” and “second” are used to distinguish the same or similar items with substantially the same function and effect.
  • words such as “first” and “second” do not limit the quantity and execution order, and words such as “first” and “second” do not limit the difference.
  • words such as “exemplary” or “for example” are used as examples, illustrations, or illustrations. Any embodiment or design solution described as “exemplary” or “for example” in the embodiments of the present application should not be construed as being more preferable or advantageous than other embodiments or design solutions.
  • words such as “exemplary” or “for example” are used to present related concepts in a specific manner to facilitate understanding.
  • the communication system 10 includes a first network element.
  • the first network element may be, for example, a mobility management network element, a policy control network element, or a session management network element.
  • the communication system 10 may also include an access network (radio access network, RAN) device, a slice selection function network element, a unified database network element, a unified data management network element, and a network data analysis function.
  • RAN radio access network
  • a slice selection function network element a unified database network element
  • a unified data management network element a network data analysis function.
  • network elements such as policy control network elements, network slice selection network elements, or unified data management network elements are connected to the service bus.
  • the terminal device can send service data to or receive service data from the DN through the RAN device and the user plane network element.
  • the terminal device in the embodiments of the present application may be a device used to implement wireless communication functions, such as a terminal or a chip that can be used in a terminal, etc., which may be deployed on land, including indoor or outdoor, handheld or vehicle-mounted ; It can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, and satellites, etc.).
  • a terminal or a chip that can be used in a terminal, etc.
  • the terminal device in the embodiments of the present application may be a device used to implement wireless communication functions, such as a terminal or a chip that can be used in a terminal, etc., which may be deployed on land, including indoor or outdoor, handheld or vehicle-mounted ; It can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, and satellites, etc.).
  • the terminal may be a user equipment (UE), an access terminal, a terminal unit, a terminal station, a mobile station, a mobile station, a user equipment (UE), an access terminal, a terminal unit, a terminal station, a mobile station, and a mobile station in a 5G network or a public land mobile network (PLMN) that will be evolved in the future Remote stations, remote terminals, mobile equipment, wireless communication equipment, terminal agents or terminal devices, etc.
  • UE user equipment
  • PLMN public land mobile network
  • the access terminal can be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), with wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices or wearable devices, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, industrial control (industrial) Wireless terminal in control), wireless terminal in self-driving (self-driving), wireless terminal in remote medical (remote medical), wireless terminal in smart grid (smart grid), wireless terminal in transportation safety (transportation safety) Terminals, wireless terminals in smart cities, wireless terminals in smart homes, etc.
  • the terminal can be mobile or fixed.
  • the access network device in the embodiment of the present application is used for the wireless side access of the terminal device.
  • the possible deployment forms include: centralized unit (CU) and distributed unit (DU). ) Separated scenes and single-site scenes.
  • CU supports radio resource control (radio resource control, RRC), packet data convergence protocol (packet data convergence protocol, PDCP), service data adaptation protocol (service data adaptation protocol, SDAP) and other protocols;
  • DU Mainly supports the radio link control layer (radio link control, RLC), media access control layer (media access control,
  • a single site can include (new radio Node, gNB), evolved Node B (evolved Node B, eNB), radio network controller (RNC), and Node B (Node B, NB) , Base Station Controller (BSC), Base Transceiver Station (BTS), Femtocell, Base Band Unit (BBU), Transmission Point (Transmitting and Receiving Point, TRP), Transmitting Point ( transmitting point, TP), mobile switching center, etc.
  • BSC Base Station Controller
  • BTS Base Transceiver Station
  • BBU Base Band Unit
  • TRP Transmission Point
  • TRP Transmitting Point
  • TP mobile switching center
  • the mobility management network element in the embodiment of this application is mainly used for terminal device attachment, mobility management, and tracking area update procedures in the mobile network.
  • the mobility management network element terminates the non-access stratum. , NAS) messages, complete registration management, connection management and reachability management, assign tracking area list (track area list, TA list) and mobility management, etc., and transparently route session management (SM) messages to session management Network element.
  • the mobility management network element may be an access and mobility management function (AMF) network element.
  • AMF access and mobility management function
  • future communications such as 6th generation (6G) communications, the mobility management network element may still be an AMF network element or have other names, which is not limited in the embodiment of the present application.
  • the session management network element in the embodiment of the present application is mainly used for session management in the mobile network, such as session establishment, modification, and release.
  • Specific functions include assigning Internet Protocol (IP) addresses to users, selecting user plane network elements that provide message forwarding functions, and so on.
  • IP Internet Protocol
  • the session management network element may be a session management function (session management function, SMF) network element.
  • SMF session management function
  • future communications such as 6G, the session management network element may still be an SMF network element or have other names, which is not limited in the embodiment of this application.
  • the user plane network element in the embodiment of the present application is mainly responsible for processing user messages, such as forwarding, charging, and lawful interception.
  • the user plane network element may also be referred to as a protocol data unit (PDU) session anchor (PDU) session anchor (PSA).
  • PDU protocol data unit
  • PDU session anchor
  • PSA session anchor
  • the user plane network element may be a user plane function (UPF) network element.
  • UPF user plane function
  • future communications such as 6G, the user plane network element may still be a UPF network element or have other names, which is not limited in the embodiment of this application.
  • the slice selection function network element in the embodiment of the present application is used to select network slices for the terminal device and so on.
  • the slice selection function network element may be a network slice selection function (network slice selection function, NSSF) network element.
  • NSSF network slice selection function
  • future communications such as 6G communications
  • the network slice selection function network element may still be an NSSF network element or have other names, which is not limited in the embodiment of the present application.
  • the policy control network element in the embodiment of this application includes user subscription data management function, policy control function, charging policy control function, quality of service (QoS) control, etc., which are used to guide network behavior
  • the unified policy framework provides policy rule information for control plane functional network elements (such as AMF network elements, etc.).
  • the policy control network element may be a policy control function (PCF) network element.
  • PCF policy control function
  • future communications such as 6G communications
  • the policy control function network element may still be a PCF network element or have other names, which is not limited in the embodiment of the present application.
  • the unified data management network element in the embodiment of the present application is used to be responsible for the management of the contract information of the terminal device and so on.
  • the unified data management network element may be a unified data management (UDM) network element.
  • the unified data management network element may still be a UDM network element or have other names, which is not limited in the embodiment of the present application.
  • the unified database network element in the embodiment of the present application is used to store and query structured data.
  • structured data is data whose structure and semantics are defined by standards, and all parties can understand the meaning represented by the data according to the standards.
  • the unified data repository network element can be stored and inquired by the unified data management network element for the contracted data, the policy control network element can also store or query the policy data, and the application function network element can also be stored and inquired by the application function network element directly or through the network open function network element.
  • Application related data In a 5G communication system, a unified data repository network element may be a unified data repository (UDR) network element. In future communications such as 6G communications, the unified data storage library network element may still be a UDR network element or have other names, which is not limited in the embodiment of the present application.
  • UDR unified data repository
  • the network data analysis function network element in the embodiment of the present application can be selected from various network functions (network functions, NF), such as policy control network elements, session management network elements, user plane network elements, and access management network elements.
  • NF network functions
  • Application function network elements open function network elements through network capabilities collect data, and perform analysis and prediction.
  • the network data analysis network element may be a network data analysis function (NWDAF) network element.
  • NWDAF network data analysis function
  • the data network in the embodiment of the present application provides a data transmission service for the terminal, and may be a public data network (PDN) network, such as the Internet.
  • PDN public data network
  • the network element or entity corresponding to the access network device may be the RAN device in the 5G communication system ( Figure 5 shows that the RAN device is a gNB as an example), and the network element or entity corresponding to the mobility management network element may be 5G
  • the AMF network element in the communication system, the network element or entity corresponding to the session management network element may be the SMF network element in the 5G communication system, and the network element or entity corresponding to the user plane network element may be the UPF network in the 5G communication system
  • the network element or entity corresponding to the policy control network element may be the PCF network element in the 5G communication system, and the network element or entity corresponding to the slice selection function network element may be the NSSF network element in the 5G communication system, the unified database network
  • the network element or entity corresponding to the element can be the UDR network
  • the aforementioned UDR network elements, AMF network elements, SMF network elements and NSSF network elements can communicate with the network elements in the 5G communication system, and can also communicate with the operation, administration and maintenance (operation, administration and maintenance) of the management plane.
  • Entity communication Figure 2 only shows the connection relationship between the UDR network element and the OAM entity).
  • NSSF network elements are often shared by multiple network slices
  • SMF network elements and UPF network elements generally belong to specific network slices.
  • the gNB on the wireless access side is often shared by multiple network slices.
  • 3rd generation partnership project 3rd generation partnership project, 3GPP
  • TS technology standard
  • a network slice can cover multiple areas.
  • the service area of the entire network slice is divided into area A, area B,..., area N, and each area can be one or more cells, or one or more cells.
  • a TA can also be the service area of an AMF network element, an SMF network element, or a UPF network element.
  • there can be multiple gNBs gNB-A in area A, gNB-B in area B, and gNB-N in area N in Figure 2 and multiple AMF networks in the entire service area of the network slice.
  • Each gNB has a certain coverage area, which can be one or more cells, and each cell has a unique cell identification (ID).
  • Each AMF network element also has a serviceable area, which may be one or more tracking areas (TAs).
  • Each TA contains one or more cells, each TA corresponds to a tracking area identity (TAI), and each cell corresponds to a cell ID (cell ID).
  • TAI tracking area identity
  • cell ID cell ID
  • each UPF network element also has a serviceable area, especially some UPF network elements deployed in mobile edge computing (mobile edge computing, MEC) locations (such as UPF network elements in Figure 2).
  • the size of the service area is one Or an area covered by several gNBs.
  • each area of the network slice has some regional restricted network resources. These restricted network resources can only provide services for terminal devices in this area, and cannot provide services for terminal devices located in other areas. Network resources are limited, which has become the resource bottleneck of the largest network service capacity in the region.
  • the restricted network resources in these areas may be the gNB in FIG. 2, such as gNB-A in FIG. 2; or UPF network elements, such as the UPF-B network element in FIG. 2.
  • the operator determines the number of regional restricted network resources for network slicing according to the terminal density that the region needs to support. For example, when the gNB shared by multiple network slices is a regionally restricted network resource, according to the registered terminal density and session density that the newly deployed network slice needs to support, determine the maximum wireless resource allowed to be used by the network slice or the percentage of the entire gNB wireless resource Maximum ratio; if the dedicated UPF network elements in the newly-built network slice are regionally restricted network resources, determine the resources of the UPF network elements that need to be deployed according to the session density, the area area and the guaranteed bandwidth of each terminal that need to be supported by the newly deployed slice According to the total bandwidth of data service traffic of network slices in the area, determine the resource quantity of UPF network elements that need to be deployed.
  • the first network element in the embodiment of the present application may also be referred to as a communication device, which may be a general-purpose device or a dedicated device, which is not specifically limited in the embodiment of the present application.
  • the related functions of the first network element in the embodiments of the present application may be implemented by one device, or jointly implemented by multiple devices, or implemented by one or more functional modules in one device.
  • the embodiment does not specifically limit this. It is understandable that the above functions can be network elements in hardware devices, software functions running on dedicated hardware, or a combination of hardware and software, or instantiated on a platform (for example, a cloud platform) Virtualization function.
  • FIG. 3 is a schematic structural diagram of a communication device 300 provided by an embodiment of the application.
  • the communication device 300 includes one or more processors 301, a communication line 302, and at least one communication interface (in FIG. 3, the communication interface 304 and one processor 301 are taken as an example for illustration), optional
  • the memory 303 may also be included.
  • the processor 301 may be a general-purpose central processing unit (central processing unit, CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more programs for controlling the execution of the program of this application. integrated circuit.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the communication line 302 may include a path for connecting different components.
  • the communication interface 304 may be a transceiver module for communicating with other devices or communication networks, such as Ethernet, RAN, wireless local area networks (WLAN), and so on.
  • the transceiver module may be a device such as a transceiver or a transceiver.
  • the communication interface 304 may also be a transceiver circuit located in the processor 301 to implement signal input and signal output of the processor.
  • the memory 303 may be a device having a storage function. For example, it can be read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM), or other types that can store information and instructions Dynamic storage devices can also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM), or other optical disk storage, optical disc storage ( Including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program codes in the form of instructions or data structures and can be stored by a computer Any other media taken, but not limited to this.
  • the memory can exist independently and is connected to the processor through the communication line 302. The memory can also be integrated with the processor.
  • the memory 303 is used to store computer-executed instructions for executing the solution of the present application, and the processor 301 controls the execution.
  • the processor 301 is configured to execute computer-executable instructions stored in the memory 303, so as to implement the method for controlling the use of network slices provided in the embodiments of the present application.
  • the processor 301 may also perform processing-related functions in the network slice usage control method provided in the following embodiments of the present application, and the communication interface 304 is responsible for communicating with other devices or communication networks. Communication, this embodiment of the application does not specifically limit this.
  • the computer-executable instructions in the embodiments of the present application may also be referred to as application program codes, which are not specifically limited in the embodiments of the present application.
  • the processor 301 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 3.
  • the communication device 300 may include multiple processors, such as the processor 301 and the processor 308 in FIG. 3. Each of these processors can be a single-core processor or a multi-core processor.
  • the processor here may include but is not limited to at least one of the following: central processing unit (CPU), microprocessor, digital signal processor (DSP), microcontroller (microcontroller unit, MCU), or artificial intelligence
  • CPU central processing unit
  • DSP digital signal processor
  • MCU microcontroller unit
  • computing devices such as processors that run software.
  • Each computing device may include one or more cores for executing software instructions to perform operations or processing.
  • the communication device 300 may further include an output device 305 and an input device 306.
  • the output device 305 communicates with the processor 301 and can display information in a variety of ways.
  • the output device 305 may be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector (projector) Wait.
  • the input device 306 communicates with the processor 301, and can receive user input in a variety of ways.
  • the input device 306 may be a mouse, a keyboard, a touch screen device, a sensor device, or the like.
  • the aforementioned communication device 300 may sometimes be referred to as a communication device, which may be a general-purpose device or a special-purpose device.
  • the communication device 300 may be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, an embedded device, the foregoing terminal device, the foregoing network device, or a picture 3 similar structure equipment.
  • PDA personal digital assistant
  • the embodiment of the present application does not limit the type of the communication device 300.
  • a method for controlling the use of network slicing includes the following steps:
  • the first network element receives a first message, where the first message is used to request a terminal device to access a target network slice, where the target network slice covers multiple areas, the multiple areas include the first area, and the first area is the terminal The area where the device is currently located.
  • the first network element determines whether the terminal device is connected to the target network slice according to a first condition, where the first condition includes: whether the service usage of the target network slice in the first area exceeds a first service quota.
  • the first network element determines whether to connect the terminal device to the target network slice according to the first condition, which may include: when the target network slice has a service usage volume in the first area (understandably To be equal, the first network element rejects the first message when the first service quota is equal to or equal to, and is uniformly described here, and will not be described here.
  • the first network element may also allow the terminal device to use the target network slice, which is explained here in a unified manner. Go into details.
  • the service usage of the target network slice in the first area includes the actual number of registered terminals of the target network slice in the first area, and the first service quota includes The maximum number of registered terminals allowed by the target network slice in the first area.
  • the service usage of the target network slice in the first area includes the actual number of concurrent sessions of the target network slice in the first area, and the first service quota includes the target network slice in the first area.
  • the maximum number of concurrent sessions allowed within the target network slice; or, the service usage of the target network slice in the first area includes the actual traffic bandwidth of the target network slice in the first area, and the first service quota includes the target network slice allowed in the first area
  • the maximum traffic bandwidth is described here in a unified manner, and will not be described in detail below.
  • the first condition in the embodiment of the present application may further include: whether the overall service usage of the target network slice exceeds the overall quota.
  • the first network element judging whether to connect the terminal device to the target network slice according to the first condition may include: when the service usage of the target network slice in the first area does not exceed the first service quota , But when the overall service usage of the target network slice reaches or exceeds the overall quota, the first network element rejects the first message.
  • no more than here can be understood as being less than or being understood as being less than or equal to, and this description is also applicable to other embodiments described below, and the description here is unified, and the details are not repeated below.
  • the first network element determines whether to connect the terminal device to the target network slice according to the first condition, which may include: when the overall service usage of the target network slice reaches or exceeds the overall quota, but the target network When the service usage of the slice in the first area does not exceed the first service limit, if the second condition is met, the first network element allows the terminal device to use the target network slice.
  • the second condition here can be understood as a judgment condition for network operation information or user information obtained by the first network element from the OAM entity or other network elements.
  • the overall service usage of the target network slice includes the actual overall number of registered terminals of the target network slice, and the overall limit of the target network slice includes the overall allowable amount of the target network slice. Maximum number of registered terminals.
  • the overall service usage of the target network slice includes the actual overall number of concurrent sessions of the target network slice, and the overall limit of the target network slice includes the maximum number of concurrent sessions allowed by the target network slice as a whole; or, the target network
  • the overall service usage of the slice includes the actual overall traffic bandwidth of the target network slice, and the overall quota of the target network slice includes the maximum traffic bandwidth allowed by the target network slice as a whole, which is explained here in a unified manner and will not be repeated here.
  • the first network element can determine whether to access the terminal device to the target network slice according to the first condition.
  • the first condition includes: whether the service usage of the target network slice in the first area exceeds the first service quota.
  • the embodiments of the present application implement sub-regional control of network slicing access, and therefore can avoid congestion or overload of wireless side network nodes in the region, not only cannot guarantee the service quality of this network slice, but may also slice other networks. This can limit the excessive use of network slicing resources by customers, and at the same time guarantee the service quality of network slicing.
  • the first condition may also include: whether the overall service usage of the target network slice exceeds the overall quota. Further, when the overall service usage of the target network slice reaches or exceeds the overall quota, but the service usage of the target network slice in the first area does not exceed the first service quota, if the second condition is met, the first network element allows The terminal device uses the target network slice. In other words, when the overall service usage of the target network slice reaches or exceeds the overall quota, but the service usage of the target network slice in the first area does not exceed the first service quota, the user can be allowed in the first area under certain scenarios. Regions use target network slicing resources, so the utilization of network resources can be improved, which not only brings more economic benefits to operators, but also improves the business experience of value users.
  • embodiments of the present application are not limited to the 5G network architecture shown in FIG. 2, and can also be applied to other future communication systems, such as 6G network architectures.
  • the names of the network elements used in the embodiments of the present application may maintain the same function in the future communication system, but the names will change.
  • a method for controlling the use of network slices includes the following steps:
  • the OAM entity sends the overall quota of the target network slice to the NSSF network element.
  • the NSSF network element receives the overall quota of the target network slice from the OAM entity.
  • the OAM entity sends information related to the business quota of the target network slice in each area to the AMF network elements in each area covered by the target network slice.
  • the AMF network elements in each area covered by the target network slice receive information about the business quota of the target network slice in each area from the OAM entity.
  • FIG. 5 is only an exemplary case where the OAM entity sends the information related to the first service quota of the target network slice in the first area to the AMF-A network element in the first area covered by the target network slice (ie area A).
  • the AMF-A network element receives the first service quota related information of the target network slice in the first area from the OAM entity.
  • the information related to the first business quota in the embodiment of the present application includes the first business quota or information used to determine the first business quota.
  • the first service quota For the related description of the first service quota, reference may be made to the embodiment shown in FIG. 4, which will not be repeated here.
  • the information used to determine the maximum number of registered terminals allowed by the target network slice in the first area may include, for example, the terminal density supported by the target network slice.
  • the maximum number of registered terminals allowed by the target network slice in the first area can be determined.
  • the terminal density supported by the target network slice configured by the OAM entity to the AMF network elements in each area covered by the target network slice may be the same or different, which is not done in this embodiment of the application. Specific restrictions.
  • the information used to determine the maximum number of concurrent sessions allowed in the first area may include, for example, the density of concurrent sessions supported by the target network slice.
  • the maximum number of concurrent sessions allowed by the target network slice in the first region can be determined.
  • the concurrent session density supported by the target network slice configured by the OAM entity to the AMF network elements in each area covered by the target network slice may be the same or different. This is not the case in this embodiment of the application. Make specific restrictions.
  • the information used to determine the maximum traffic bandwidth allowed in the first area may include, for example, the traffic density supported by the target network slice.
  • the maximum traffic bandwidth allowed by the target network slice in the first region can be determined.
  • the traffic density supported by the target network slice configured by the OAM entity to the SMF network elements in each area covered by the target network slice may be the same or different, which is not done in this embodiment of the application. Specific restrictions.
  • Step S501 may be executed first, and then step S502; or step S502 may be executed first, and then step S501 may be executed; It is also possible to perform step S501 and step S502 at the same time, which is not specifically limited in the embodiment of the present application.
  • the terminal device sends a message a1 to the AMF-A network element through the gNB-A in the service area of the AMF-A network element.
  • the AMF-A network element receives the message a1 from the terminal device.
  • the message a1 carries the network slice selection assistance information (network slice selection assistance information, NSSAI) requested by the terminal device (that is, request NSSAI).
  • NSSAI network slice selection assistance information
  • the request NSSAI includes a single NSSAI (single NSSAI, S-NSSAI) of one or more network slices that the terminal device wishes to register for access.
  • the message a1 may also carry the identity of the TA and/or the identity of the cell where the terminal device is currently located, which is not specifically limited in the embodiment of the present application.
  • the message a1 in the embodiment of the present application may be, for example, a registration request (registration request) message as shown in FIG. 5, which is not specifically limited in the embodiment of the present application.
  • the AMF-A network element determines whether the service usage of the target network slice in the first area exceeds the first service quota.
  • the AMF-A network element can determine the area where the terminal device is currently located (that is, the first area in the embodiment of the present application) according to the identifier of the TA and/or the cell cell where the terminal device is currently located.
  • the AMF-A network element can determine the target network slice that the terminal device wants to register and access according to each S-NSSAI carried by the request NSSAI. Exemplarily, if the terminal device does not have the network slice subscription information corresponding to a certain S-NSSAI, the AMF-A network element will refuse the terminal device to register to the network slice corresponding to the S-NSSAI. If the terminal device has a certain S-NSSAI Corresponding network slice subscription information, the network slice corresponding to the S-NSSAI can be used as the target network slice.
  • the service usage of the target network slice in the first area includes the actual number of registered terminals of the target network slice in the first area.
  • the AMF-A network element maintains the actual number of registered terminals in each area managed by the AMF-A network element for each network slice currently serving during the registration management process, including the actual registration of the target network slice in the first area Number of terminals. Furthermore, the AMF-A network element may compare the actual number of registered terminals of the target network slice in the first area with the maximum number of registered terminals allowed by the target network slice in the first area determined in step S502.
  • step S505 When the actual number of registered terminals of the target network slice in the first area reaches or exceeds the maximum number of registered terminals allowed by the target network slice in the first area, the following branch 1 corresponding to step S505 is executed; when the target network slice is in the first area When the actual number of registered terminals in one area does not exceed the maximum number of registered terminals allowed by the target network slice in the first area, the following step S508 and branch two corresponding to the subsequent steps are executed.
  • the following steps can be continued for the demarcation point
  • the branch 1 corresponding to S505 or the branch 2 corresponding to the following step S508 and subsequent steps continue to be executed, which is not specifically limited in the embodiment of the present application.
  • the AMF-A network element sends a message b1 to the terminal device through the gNB-A.
  • the terminal device receives the message b1 from the AMF-A network element.
  • the message b1 carries the S-NSSAI of the target network slice, which is used to temporarily refuse the terminal device to register to the target network slice at the current location, allowing the terminal device to continue to request registration to the target after changing the location area or waiting for a period of time Network slicing.
  • the message b1 in the embodiment of the present application may be, for example, a registration rejection (registration reject) message as shown in FIG. 5, which is not specifically limited in the embodiment of the present application.
  • step S506 when the actual number of registered terminals of the target network slice in the first area reaches or exceeds the maximum number of registered terminals allowed by the target network slice in the first area, the following step S506 may be performed. -S507:
  • the AMF-A network element sends instruction information to the gNB-A.
  • the gNB-A receives the indication information from the AMF-A network element.
  • the indication information is used to instruct gNB-A to set access class barring (ACB) for the access class (AC) corresponding to the target network slice; or, the indication information is used to indicate gNB-A Broadcast an explicit congestion notification (ECN) to the terminal devices in the area to notify the terminal devices in the area that the target network slice is congested.
  • ACB access class barring
  • ECN explicit congestion notification
  • the gNB-A sends ECN or ACB to the terminal equipment in the area according to the instruction information to prevent the terminal equipment in the area from continuing to try to access the target network slice. Take the interaction of the terminal device as an example for illustration).
  • AMF-A network element will periodically or when the quota of service usage in the first area is used up (or is about to be finished), or when there is no valid cache of the S-NSSAI slice selection result of the target network slice,
  • the NSSF network element sends a message c1.
  • the NSSF network element receives the message c1 from the AMF-A network element.
  • the message c1 carries the actual number of registered terminals of the target network slice in the first area.
  • the message c1 may also carry the actual number of concurrent sessions of the target network slice in the first area.
  • the message c1 in the embodiment of the present application may be, for example, a slice selection request message as shown in FIG. 5, which is not specifically limited in the embodiment of the present application.
  • AMF network elements in other areas covered by the target network slice can also report the actual number of registered terminals of the target network slice in other areas to the NSSF network element.
  • AMF network elements in other areas covered by the target network slice may also report the actual number of concurrent sessions of the target network slice in other areas to the NSSF network element.
  • the NSSF network element determines whether the overall service usage of the target network slice exceeds the overall quota.
  • the overall service usage of the target network slice includes the actual overall number of registered terminals of the target network slice.
  • the NSSF network element obtains the actual number of registered terminals in each area of the target network slice reported by the AMF network elements in each area covered by the target network slice, it can add up the actual number of registered terminals in each area of the target network slice. Furthermore, the sum result is compared with the maximum number of registered terminals allowed in the entire target network slice obtained in step S501.
  • the quota of the number of registered terminals in each area covered by the target network slice can be set to 0; when the actual number of target network slices When the total number of registered terminals does not exceed the maximum number of registered terminals allowed by the target network slice as a whole, the remaining total number of registered terminals (or part of the total remaining number of registered terminals) can be allocated in proportion to the actual number of registered terminals in each area. As a quota for the number of registered terminals in each region.
  • the overall service usage of the target network slice includes the actual number of concurrent sessions of the target network slice.
  • the NSSF network element obtains the actual number of concurrent sessions in each area of the target network slice reported by the AMF network elements in each area covered by the target network slice, it can add up and sum the actual number of concurrent sessions in each area of the target network slice. Furthermore, the sum result is compared with the maximum number of concurrent sessions allowed by the target network slice as a whole obtained in step S501.
  • the quota of the number of concurrent sessions in each area covered by the target network slice can be set to 0; when the actual number of the target network slice When the overall number of concurrent sessions does not exceed the maximum number of concurrent sessions allowed by the target network slice as a whole, the overall remaining number of concurrent sessions (or a part of the overall remaining number of concurrent sessions) can be allocated in proportion to the actual number of concurrent sessions in each region. As a quota for the number of concurrent sessions in each region.
  • the NSSF network element sends a message d1 to the AMF-A network element.
  • the AMF-A network element receives the message d1 from the NSSF network element.
  • the message d1 carries the quota of service usage in the first area.
  • the quota for service usage in the first area may include, for example, a quota for the number of registered terminals in the first area.
  • the quota for service usage in the first area may further include a quota for the number of concurrent sessions in the first area, for example.
  • the AMF-A network element after the AMF-A network element obtains the quota for the number of registered terminals in the first area, it can cache the quota for the number of registered terminals in the first area locally, and each subsequent time a new one After the terminal device of is registered in the target network slice in the first area, 1 will be deducted from the quota of the number of registered terminals in the first area in the cache. When the terminal device logs off from the target network slice or moves out of the first area, the quota for the number of registered terminals in the first area in the cache (that is, the quota plus 1) can be restored.
  • the AMF-A network element may request a new quota for the number of registered terminals in the first area from the NSSF network element through a message c1.
  • the message d1 in the embodiment of the present application may be, for example, a slice selection response message as shown in FIG. 5, which is not specifically limited in the embodiment of the present application.
  • the AMF-A network element can determine that the actual overall number of registered terminals of the target network slice reaches or exceeds the maximum number of registered terminals allowed by the target network slice as a whole, and then executes the following Branch a corresponding to steps S511-S513; when the quota for the number of registered terminals in the first area is not 0, the AMF-A network element can determine that the actual overall number of registered terminals of the target network slice does not exceed the overall allowable number of the target network slice Maximum number of registered terminals, then branch b corresponding to the following step S514 is executed.
  • the above message d1 may not carry the quota for the number of registered terminals in the first area, but carries the target network slice.
  • the actual overall number of registered terminals reaches or exceeds the indication of the maximum number of registered terminals allowed by the target network slice as a whole, which is not specifically limited in the embodiment of the present application.
  • S511-S513 are the same as the above steps S505-S507, and will not be repeated here.
  • the AMF-A network element sends a message e1 to the terminal device through the gNB-A.
  • the terminal device receives the message e1 from the AMF-A network element.
  • the message e1 carries an allowed NSSAI (allowed NSSAI), and the allowed NSSAI includes the S-NSSAI of the target network slice.
  • the message e1 in the embodiment of the present application may be, for example, a registration acceptance (registration accept) message as shown in FIG. 5, which is not specifically limited in the embodiment of the present application.
  • the AMF-A network element refreshes and maintains the number of registered terminals in the first area of the target network slice, and deducts the quota for the number of registered terminals in the first area in the cache. .
  • the terminal device logs off from the target network slice or moves out of the first area, the quota for the number of registered terminals in the first area in the cache (that is, the quota plus 1) can be restored.
  • each target network slice can be processed separately in the manner of the above steps S504-S514, which will not be repeated here.
  • the network slice usage control method provided in the embodiment of the present application further includes the following steps S515-S517 or the following steps S515-S518 as shown in the session establishment process:
  • the terminal device sends the message f1 to the AMF-A network element through the gNB-A.
  • the AMF-A network element receives the message f1 from the terminal device.
  • the message f1 carries the S-NSSAI of the target network slice.
  • the message f1 in the embodiment of the present application may be, for example, a session establishment request message as shown in FIG. 5, which is not specifically limited in the embodiment of the present application.
  • the AMF-A network element determines whether the service usage of the target network slice in the first area exceeds the first service quota.
  • the AMF-A network element can determine the area where the terminal device is currently located (that is, the first area in the embodiment of the present application) according to the identifier of the TA and/or the cell cell where the terminal device is currently located.
  • the AMF-A network element can determine the target network slice that the terminal device wants the session to access according to the S-NSSAI of the target network slice.
  • the service usage of the target network slice in the first area includes the actual number of concurrent sessions of the target network slice in the first area.
  • the AMF-A network element maintains the actual number of concurrent sessions of each network slice currently served in each area managed by the AMF-A network element, including the actual concurrent sessions of the target network slice in the first area. The number of sessions.
  • the AMF-A network element may compare the actual number of concurrent sessions of the target network slice in the first area with the maximum number of concurrent sessions allowed by the target network slice in the first area determined in step S502.
  • the branch i corresponding to the following step S517 is executed; when the target network slice is in the first area When the actual number of concurrent sessions in an area does not exceed the maximum number of concurrent sessions allowed by the target network slice in the first area, the AMF-A network element further determines whether the actual overall number of concurrent sessions of the target network slice exceeds the overall allowable number of the target network slice When the AMF-A network element determines that the actual overall number of concurrent sessions of the target network slice reaches or exceeds the maximum number of concurrent sessions allowed by the target network slice as a whole, the branch i corresponding to the following step S517 is executed; when AMF -When the network element A determines that the actual overall number of concurrent sessions of the target network slice does not exceed the maximum number of concurrent sessions allowed by the overall target network slice, it then executes branch ii corresponding to the following step S518.
  • the branch i corresponding to S517 can also further determine whether the actual total number of concurrent sessions of the target network slice exceeds the maximum number of concurrent sessions allowed by the target network slice as a whole.
  • step S517 When the actual overall number of concurrent sessions of the target network slice is equal to (that is, the above-mentioned reach) the maximum number of concurrent sessions allowed by the target network slice as a whole, for this demarcation point, you can continue to execute the branch i corresponding to the following step S517 or continue to execute the following
  • the branch ii corresponding to step S518 is not specifically limited in the embodiment of the present application.
  • step S510 after the AMF-A network element obtains the quota for the number of concurrent sessions in the first area, it may cache the quota for the number of concurrent sessions in the first area to the local , Each subsequent time a new session is successfully established in the first area, 1 will be deducted from the quota of the number of concurrent sessions in the first area in the cache.
  • the quota for the number of concurrent sessions in the first area in the cache (that is, the quota plus 1) can be restored.
  • the AMF-A network element may then request a new quota for the number of concurrent sessions in the first area from the NSSF network element through a message c1.
  • the AMF-A network element can determine that the actual overall number of concurrent sessions of the target network slice reaches or exceeds the maximum number of concurrent sessions allowed by the target network slice as a whole;
  • the AMF-A network element can determine that the actual total number of concurrent sessions of the target network slice does not exceed the maximum number of concurrent sessions allowed by the target network slice as a whole.
  • the AMF-A network element if the AMF-A network element does not obtain the quota for the number of concurrent sessions in the first area through the above steps S509 and S510, then in the session establishment process of the terminal device, the AMF -A network element can obtain the quota of the number of concurrent sessions in the first area by the above steps S509 and S510, which is not specifically limited in the embodiment of the present application.
  • the message d1 may not carry the quota for the number of concurrent sessions in the first area, but instead carry the target network slice.
  • the actual overall number of concurrent sessions reaches or exceeds the indication of the maximum number of concurrent sessions allowed by the target network slice as a whole, which is not specifically limited in the embodiment of the present application.
  • the AMF-A network element sends a message g1 to the terminal device through the gNB-A.
  • the terminal device receives the message g1 from the AMF-A network element.
  • the message g1 carries an overload indication of the target network slice, which is used to temporarily refuse the terminal device to establish a session on the target network slice at the current location, and allow the terminal device to continue to try to request the target network after changing the location area or waiting for a period of time.
  • the slice establishes a session.
  • the message g1 in the embodiment of the present application may be, for example, a session establishment rejection message as shown in FIG. 5, which is not specifically limited in the embodiment of the present application.
  • the AMF-A network element allows the terminal device to establish a session in the target network slice in the first area, and continues the subsequent session establishment processing flow.
  • the AMF-A network element refreshes and maintains the number of concurrent sessions in the first area of the target network slice, and deducts the quota for the number of concurrent sessions in the first area in the cache. Less.
  • the quota for the number of concurrent sessions in the first area in the cache that is, the quota plus 1 can be restored.
  • the first network element can determine whether to access the terminal device to the target network slice according to the first condition.
  • the first condition includes: whether the service usage of the target network slice in the first area exceeds the first service quota.
  • the embodiments of the present application implement sub-regional control of network slicing access, and therefore can avoid congestion or overload of wireless side network nodes in the region, not only cannot guarantee the service quality of this network slice, but may also slice other networks. This can limit the excessive use of network slicing resources by customers, and at the same time guarantee the service quality of network slicing.
  • step S501 to step S517 or step S518 can be executed by the processor 301 in the communication device 300 shown in FIG. 3 calling the application program code stored in the memory 303.
  • This embodiment There are no restrictions on this.
  • the first network element in the communication system shown in FIG. 1 is a mobility management network element or a session management network element, and the communication system shown in FIG. 1 is applied to the 5G network architecture shown in FIG.
  • the area is the area A in FIG. 2 as an example.
  • another network slice usage control method provided by this embodiment of the present application includes the following steps:
  • the OAM entity sends the overall quota of the target network slice to the UDR network element.
  • the UDR network element receives the overall quota of the target network slice from the OAM entity.
  • the OAM entity sends information about the business quota of the target network slice in each area to the AMF network elements in each area covered by the target network slice.
  • the AMF network elements in each area covered by the target network slice receive information about the business quota of the target network slice in each area from the OAM entity.
  • FIG. 6 is only an exemplary case where the OAM entity sends the first service quota related information of the target network slice in the first area to the AMF-A network element in the first area covered by the target network slice (ie area A).
  • the AMF-A network element receives the first service quota related information of the target network slice in the first area from the OAM entity.
  • the information related to the first service quota in step S602 includes the first service quota required in the registration process of the terminal device or the information used to determine the first service quota.
  • the first service quota required in the registration process of the terminal device or the information used to determine the first service quota reference may be made to step S502 in the embodiment shown in FIG. 5, which will not be repeated here.
  • the OAM entity sends information about the business quota of the target network slice in each area to the SMF network elements in each area covered by the target network slice.
  • the SMF network elements in each area covered by the target network slice receive information about the business quota of the target network slice in each area from the OAM entity.
  • FIG. 6 is only an example of taking the OAM entity to send information related to the first service quota of the target network slice in the first area to the SMF network element in the first area covered by the target network slice (ie area A) as an example for illustration.
  • the SMF network element receives information related to the first service quota of the target network slice in the first area from the OAM entity.
  • the information related to the first service quota in step S603 includes the first service quota required in the session establishment process of the terminal device or the information used to determine the first service quota.
  • the first service quota required in the session establishment process of the terminal device or the information used to determine the first service quota reference may be made to step S502 in the embodiment shown in FIG. 5, which will not be repeated here.
  • step S601, step S602, and step S603 there is no inevitable order of execution between step S601, step S602, and step S603 in the embodiment of the present application. Any one of these steps may be executed first, and then the remaining two steps may be executed respectively; or Perform two of these steps at the same time, and then perform the remaining steps; it is also possible to perform one of the steps first, and then perform the remaining two steps at the same time; it is also possible to perform these three steps at the same time. This is not specifically limited.
  • step S604 is the same as step S503 in the embodiment shown in FIG. 5. For related descriptions, reference may be made to the embodiment shown in FIG. 5, which will not be repeated here.
  • the AMF-A network element determines whether the service usage of the target network slice in the first area exceeds the first service quota.
  • the manner in which the AMF-A network element determines the area where the terminal device is currently located can refer to step S504 in the embodiment shown in FIG. 5, which will not be repeated here. Go into details.
  • the service usage of the target network slice in the first area includes the actual number of registered terminals of the target network slice in the first area.
  • the AMF-A network element maintains the actual number of registered terminals in each area managed by the AMF-A network element for each network slice currently serving during the registration management process, including the actual registration of the target network slice in the first area Number of terminals. Furthermore, the AMF-A network element may compare the actual number of registered terminals of the target network slice in the first area with the maximum number of registered terminals allowed by the target network slice in the first area determined in step S602.
  • step S606 When the actual number of registered terminals of the target network slice in the first area reaches or exceeds the maximum number of registered terminals allowed by the target network slice in the first area, the following branch 1 corresponding to step S606 is executed; when the target network slice is in the first area When the actual number of registered terminals in an area does not exceed the maximum number of registered terminals allowed by the target network slice in the first area, the following step S609 and branch two corresponding to the subsequent steps are executed.
  • the following steps can be continued for the demarcation point
  • the branch 1 corresponding to S606 or the branch 2 corresponding to the following step S609 and subsequent steps continue to be executed, which is not specifically limited in the embodiment of the present application.
  • step S606 is the same as step S505 in the embodiment shown in FIG. 5.
  • step S607 when the actual number of registered terminals of the target network slice in the first area reaches or exceeds the maximum number of registered terminals allowed by the target network slice in the first area, the following step S607 may also be performed -S608:
  • S607-S608 are the same as steps S506-S507 in the embodiment shown in FIG. 5, and related descriptions can refer to the embodiment shown in FIG. 5, which will not be repeated here.
  • the AMF-A network element sends a message h1 to the PCF network element.
  • the PCF network element receives the message h1 from the AMF-A network element.
  • the message h1 carries the S-NSSAI of the target network slice.
  • the message h1 in the embodiment of the present application may be, for example, an associated registration management policy request as shown in FIG. 6, which is not specifically limited in the embodiment of the present application.
  • the PCF network element obtains the overall service usage of the target network slice and the overall quota of the target network slice from the UDR network element.
  • the overall service usage of the target network slice is the actual overall number of registered terminals of the target network slice.
  • the overall limit of the target network slice is the maximum number of registered terminals allowed by the target network slice as a whole.
  • the target network slice has multiple PCF network elements, these PCF network elements are all uniformly using UDR network elements to maintain the overall service usage of the target network slice.
  • the PCF network element determines whether the overall service usage of the target network slice exceeds the overall quota of the target network slice.
  • the PCF network element sends a message j1 to the AMF-A network element.
  • AMF-A receives the message j1 from the PCF network element.
  • the message j1 in the embodiment of the present application may be, for example, an associated registration management policy response as shown in FIG. 6, which is not specifically limited in the embodiment of the present application.
  • the above message j1 may carry an indication that the overall service usage of the target network slice reaches or exceeds the overall quota of the target network slice or is not allowed
  • the terminal device uses the instruction of the target network slice, and then can execute the branch a corresponding to the following step S613; when the overall service usage of the target network slice does not exceed the overall quota of the target network slice, the above message j1 can carry the terminal device's permission to use Instructing the target network slice, the branch b corresponding to the following step S616 may be executed.
  • step S613 is the same as step S505 in the embodiment shown in FIG. 5.
  • the following steps S613-S614 may also be performed:
  • S614-S615 are the same as steps S506-S507 in the embodiment shown in FIG. 5.
  • steps S506-S507 in the embodiment shown in FIG. 5.
  • step S616 is the same as step S514 in the embodiment shown in FIG. 5.
  • the PCF network element may also update the actual overall number of registered terminals of the target network slice to the UDR network element. Subsequently, when the terminal device logs off from the target network slice or moves out of the first area, the PCF network element can also update the actual overall number of registered terminals of the target network slice to the UDR network element, which is not specifically limited in this embodiment of the application.
  • each target network slice can be processed separately according to the above-mentioned steps S605-S616, which will not be repeated here.
  • the method for controlling the use of the network slice provided in the embodiment of the present application further includes the following steps S617-S624 or the following steps S617-S625 as shown in the session establishment process:
  • the terminal device sends the message k1 to the SMF network element through the AMF-A network element.
  • the SMF network element receives the message k1 from the terminal device.
  • the message k1 carries the S-NSSAI of the target network slice.
  • the message k1 in the embodiment of the present application may be, for example, a session establishment request message as shown in FIG. 6, which is not specifically limited in the embodiment of the present application.
  • the SMF network element determines whether the service usage of the target network slice in the first area exceeds the first service quota.
  • the SMF network element can determine the area where the terminal device is currently located (that is, the first area in the embodiment of the present application) according to the identification of the TA and/or the cell cell where the terminal device is currently located.
  • the SMF network element can determine the target network slice that the terminal device wants to access by the session according to the S-NSSAI of the target network slice.
  • the service usage and the first service quota of the target network slice in the first area in step S618 are the service usage and the first service quota of the corresponding target network slice in the first area in the session establishment process of the terminal device .
  • the SMF network element maintains the service usage of each network slice currently served in each area managed by the SMF network element, which includes the service usage of the target network slice in the first area. Furthermore, the SMF network element may compare the service usage of the target network slice in the first area with the first service quota determined in step S603.
  • step S619 When the service usage of the target network slice in the first area reaches or exceeds the first service limit, branch 3 corresponding to the following step S619 is executed; when the service usage of the target network slice in the first area does not exceed the first In case of business quota, the following step S620 and branch four corresponding to the following steps are executed:
  • step S619 is the same as step S517 in the embodiment shown in FIG. 5.
  • the SMF network element sends a message m1 to the PCF network element.
  • the PCF network element receives the message m1 from the SMF network element.
  • the message m1 carries the S-NSSAI of the target network slice.
  • the message m1 in the embodiment of the present application may be, for example, an associated session management policy request as shown in FIG. 6, which is not specifically limited in the embodiment of the present application.
  • the PCF network element obtains the overall service usage of the target network slice and the overall quota of the target network slice from the UDR network element.
  • the related description of the overall service usage of the target network slice and the overall quota of the target network slice may refer to the embodiment shown in FIG. 4, which will not be repeated here.
  • the target network slice has multiple PCF network elements, these PCF network elements are all uniformly using UDR network elements to maintain the overall service usage of the target network slice.
  • the PCF network element determines whether the overall service usage of the target network slice exceeds the overall quota of the target network slice.
  • the PCF network element sends a message n1 to the SMF network element.
  • the SMF network element receives the message n1 from the PCF network element.
  • the message n1 in the embodiment of the present application may be, for example, an associated session management policy response as shown in FIG. 6, which is not specifically limited in the embodiment of the present application.
  • the above message n1 can carry an indication that the overall service usage of the target network slice reaches or exceeds the overall quota of the target network slice or is not allowed
  • the terminal device uses the instruction of the target network slice, and then can execute the branch i corresponding to the following step S624; when the overall service usage of the target network slice does not exceed the overall quota of the target network slice, the above message n1 can carry the terminal device permission to use Instructing the target network slice, branch ii corresponding to the following step S625 may be executed.
  • the SMF network element sends a message p1 to the terminal device through the AMF-A network element.
  • the terminal device receives the message p1 from the SMF network element.
  • the message p1 carries an overload indication of the target network slice, which is used to temporarily refuse the terminal device to establish a session on the target network slice at the current location, and allow the terminal device to continue to try to request the target network after changing the location area or waiting for a period of time.
  • the slice establishes a session.
  • the message p1 in the embodiment of the present application may be, for example, a session establishment rejection message as shown in FIG. 6, which is not specifically limited in the embodiment of the present application.
  • the SMF network element allows the terminal device to establish a session in the target network slice in the first area, and continues the subsequent session establishment processing flow.
  • the PCF network element can also update the overall service usage of the target network slice during the session establishment process to the UDR network element.
  • the PCF network element can also update the overall service usage of the target network slice during the session establishment process to the UDR network element. If the session no longer uses the user plane node in the area due to the movement of the terminal device, the PCF network element can also report the overall service usage of the target network slice during the establishment of a new session to the UDR network element, which is not specifically limited in the embodiment of this application. .
  • the actions of the AMF-A network element in the above steps S601 to S624 or step S625 can be executed by the processor 301 in the communication device 300 shown in FIG. 3 calling the application program code stored in the memory 303.
  • This embodiment There are no restrictions on this.
  • the first network element in the communication system shown in FIG. 1 is used as the policy control network element
  • the communication system shown in FIG. 1 is applied to the 5G network architecture shown in FIG. 2, and the first area is shown in FIG. Take the area A of as an example.
  • another method for controlling the use of network slicing provided by this embodiment of this application includes the following steps:
  • step S701 is the same as step S601 in the embodiment shown in FIG. 6. For related description, refer to the embodiment shown in FIG. 6, which will not be repeated here.
  • the OAM entity sends information related to the business quota of the target network slice in each area to the UDR network element.
  • the UDR network element receives information about the business quota of the target network slice in each area from the OAM entity.
  • the service quota related information of the target network slice in each area includes the first service quota related information of the target network slice in the first area (ie, area A).
  • the first service quota related information of the target network slice in the first area ie, area A.
  • step S701 can be executed first, and then step S702; or step S702 can be executed first, and then step S701 can be executed; It is also possible to perform step S701 and step S702 at the same time, which is not specifically limited in the embodiment of the present application.
  • step S703 is the same as step S604 in the embodiment shown in FIG. 6.
  • step S604 in the embodiment shown in FIG. 6.
  • the AMF-A network element sends a message q1 to the PCF network element.
  • the PCF network element receives the message q1 from the AMF-A network element.
  • the message q1 carries the S-NSSAI of the target network slice.
  • the message q1 may also carry the identity of the TA and/or the identity of the cell where the terminal device is currently located, which is not specifically limited in the embodiment of the present application.
  • the message q1 in the embodiment of the present application may be, for example, an associated registration management policy request as shown in FIG. 7, which is not specifically limited in the embodiment of the present application.
  • the PCF network element obtains the overall service usage of the target network slice and the overall quota of the target network slice from the UDR network element; and the PCF network element obtains the service usage and the first area of the target network slice from the UDR network element. Business limits.
  • the PCF network element determines the area where the terminal device is currently located (that is, the first area in the embodiment of the present application) and the target network slice, refer to step S605 in the embodiment shown in FIG. 6, and details are not described herein again.
  • the overall service usage of the target network slice, the overall quota of the target network slice, the service usage of the target network slice in the first area, and the relevant description of the first service quota can refer to Figure 4 The illustrated embodiment will not be repeated here.
  • the PCF network element may also obtain the first service quota related information from the UDR network element, and then determine the first service quota according to the first service quota related information, which is not done in this embodiment of the application. Specific restrictions.
  • these PCF network elements are all using UDR network elements to maintain the overall service usage of the target network slice and the target network slice in each area. Business usage within.
  • the PCF network element determines whether the service usage of the target network slice in the first area exceeds the first service quota, and the PCF network element determines the overall service usage of the target network slice and the overall quota of the target network slice.
  • the PCF network element sends a message r1 to the AMF-A network element.
  • the AMF-A network element receives the message r1 from the PCF network element.
  • the message r1 in the embodiment of the present application may be, for example, an associated registration management policy response as shown in FIG. 7, which is not specifically limited in the embodiment of the present application.
  • the above message r1 can carry that the service usage of the target network slice in the first area reaches or exceeds the first area.
  • a service quota indication or an indication that the terminal device is not allowed to use the target network slice, and then branch 1 corresponding to the following step S708 can be executed; when the PCF network element determines that the service usage of the target network slice in the first area does not exceed the first Service limit, but when the overall service usage of the target network slice reaches or exceeds the overall limit of the target network slice, the above message r1 can carry that the service usage of the target network slice in the first area does not exceed the first service limit, but the target An indication that the overall service usage of the network slice reaches or exceeds the overall quota of the target network slice or an indication that the terminal device is not allowed to use the target network slice, and then the branch 1 corresponding to the following step S708 can be executed; when the PCF network element determines the target network slice When the service usage in the first area does not exceed the first service quota, and the overall service usage of the target network slice does not exceed the overall quota of the target network slice, the above message r1 may carry an indication that the terminal
  • the branch 1 corresponding to the following step S708 can be continued or continued Determine whether the overall service usage of the target network slice exceeds the overall quota of the target network slice.
  • the PCF network element determines that the overall service usage of the target network slice is equal to (that is, reached) the overall quota of the target network slice, for this demarcation point, you can continue to perform the following step S708 corresponding to branch 1 or perform the following step S711
  • the corresponding branch two is not specifically limited in the embodiment of the present application.
  • step S708 is the same as step S613 in the embodiment shown in FIG. 6.
  • step S613 in the embodiment shown in FIG. 6.
  • step S708 please refer to the embodiment shown in FIG. 6, which will not be repeated here.
  • S709-S710 are the same as steps S614-S615 in the embodiment shown in FIG. 6, and related descriptions can refer to the embodiment shown in FIG. 6, which will not be repeated here.
  • step S711 is the same as step S616 in the embodiment shown in FIG. 6. For related description, refer to the embodiment shown in FIG. 6, which will not be repeated here.
  • the PCF network element may also update the actual overall number of registered terminals of the target network slice and the actual number of registered terminals of the target network slice in the first area to the UDR network element. Subsequently, when the terminal device logs off from the target network slice or moves out of the first area, the PCF network element can also update the actual overall number of registered terminals of the target network slice and the actual number of registered terminals of the target network slice in the first area to the UDR network element
  • the embodiments of this application do not specifically limit this.
  • each target network slice can be processed separately according to the above steps S705-S711, which will not be repeated here.
  • the network slice usage control method provided in the embodiment of the present application further includes the following steps S712-S717 or the following steps S712-S718 as shown in the session establishment process:
  • step S712 is the same as step S617 in the embodiment shown in FIG. 6. For related description, refer to the embodiment shown in FIG. 6, which will not be repeated here.
  • the SMF network element sends a message s1 to the PCF network element.
  • the PCF network element receives the message s1 from the SMF network element.
  • the message s1 carries the S-NSSAI of the target network slice.
  • the message s1 may also carry the identity of the TA and/or the identity of the cell where the terminal device is currently located, which is not specifically limited in the embodiment of the present application.
  • the message s1 in the embodiment of the present application may be, for example, an associated session management policy request as shown in FIG. 7, which is not specifically limited in the embodiment of the present application.
  • the PCF network element obtains the overall service usage of the target network slice and the overall quota of the target network slice from the UDR network element; and the PCF network element obtains the service usage and the first area of the target network slice from the UDR network element. Business limits.
  • the PCF network element determines the area where the terminal device is currently located (that is, the first area in the embodiment of the present application) and the target network slice, refer to step S605 in the embodiment shown in FIG. 6, and details are not described herein again.
  • the overall service usage of the target network slice, the overall quota of the target network slice, the service usage of the target network slice in the first area, and the related description of the first service quota can refer to the figure.
  • the embodiment shown in 4 will not be repeated here.
  • the PCF network element may also obtain the first service quota related information from the UDR network element, and then determine the first service quota according to the first service quota related information, which is not done in this embodiment of the application. Specific restrictions.
  • these PCF network elements are all using UDR network elements to maintain the overall service usage of the target network slice and the target network slice in each area. Business usage within.
  • the PCF network element determines whether the service usage of the target network slice in the first area exceeds the first service quota, and the PCF network element determines whether the overall service usage of the target network slice exceeds the overall quota of the target network slice.
  • the PCF network element sends a message t1 to the SMF network element.
  • the SMF network element receives the message r1 from the PCF network element.
  • the message t1 in the embodiment of the present application may be, for example, an associated session management policy response as shown in FIG. 7, which is not specifically limited in the embodiment of the present application.
  • the above message t1 may carry that the service usage of the target network slice in the first area reaches or exceeds the first area.
  • An indication of a service limit, branch i corresponding to the following step S717 can be executed; when the PCF network element determines that the service usage of the target network slice in the first area does not exceed the first service limit, but the overall service usage of the target network slice When the volume reaches or exceeds the overall limit of the target network slice, the above message t1 can carry that the service usage of the target network slice in the first area does not exceed the first service limit, but the overall service usage of the target network slice reaches or exceeds the target Indication of the overall limit of the network slice, branch i corresponding to the following step S717 can be executed; when the PCF network element determines that the service usage of the target network slice in the first area does not exceed the first service limit, and the overall target network slice When the service usage does not exceed the overall quota of the target network slice, the above message t1 may carry an indication that the terminal device is allowed to use the target network slice, and the branch ii corresponding to the following step S718 may be executed.
  • the branch i corresponding to the following step S717 can be continued or continued Determine whether the overall service usage of the target network slice exceeds the overall quota of the target network slice.
  • the PCF network element determines that the overall service usage of the target network slice is equal to (that is, reached) the overall quota of the target network slice, for this demarcation point, you can continue to execute the branch i corresponding to the following step S717 or execute the following step S718
  • the corresponding branch ii is not specifically limited in the embodiment of the present application.
  • step S717 is the same as step S624 in the embodiment shown in FIG. 6.
  • step S624 in the embodiment shown in FIG. 6.
  • step S718 is the same as step S625 in the embodiment shown in FIG. 6.
  • the PCF network element can also update the UDR network element to the overall service usage of the target network slice during the session establishment process and the service usage of the target network slice in the first area. the amount.
  • the PCF network element may also update the overall service usage of the target network slice during the session establishment process and the service usage of the target network slice in the first area to the UDR network element. If the session no longer uses the user plane node in the area due to the movement of the terminal device, the PCF network element can also report the overall service usage of the target network slice and the target network slice in the first area during the establishment of the new session of the UDR network element.
  • the amount of service usage is not specifically limited in the embodiment of this application.
  • step S701 to step S717 or step S718 can be executed by the processor 301 in the communication device 300 shown in FIG. 3 calling the application program code stored in the memory 303. There are no restrictions.
  • the first network element in the communication system shown in FIG. 1 is used as the policy control network element
  • the communication system shown in FIG. 1 is applied to the 5G network architecture shown in FIG. 2, and the first area is shown in FIG. Take the area A of as an example.
  • another method for controlling the use of network slices provided in this embodiment of the application includes the following steps:
  • S801-S802 are the same as steps S701-S702 in the embodiment shown in FIG. 7.
  • steps S701-S702 in the embodiment shown in FIG. 7.
  • the OAM entity sends to the UDR network element the restriction strategy of the target network slice in each area (may be referred to as the area restriction strategy of the target network slice) and the overall restriction strategy of the target network slice.
  • the UDR network element receives the area restriction strategy and the overall restriction strategy of the target network slice from the OAM entity.
  • the area restriction strategy of the target network slice includes the area restriction strategy of the target network slice in the first area (ie area A) (may be referred to as the first area restriction strategy).
  • the area restriction policy of the target network slice may include, for example, when the service usage of the target network slice in the area reaches or exceeds the service quota in the area, denying the terminal device to use the target network slice.
  • the overall restriction strategy of the target network slice may be, for example, when the overall service usage of the target network slice reaches or exceeds the overall limit, but the service usage of the target network slice in the area does not exceed the limit.
  • the business quota in the area is met, if the second condition is met, the terminal device is allowed to use the target network slice.
  • the corresponding second condition in the registration process of the terminal device may include, for example, that the overall limit is allowed in the slice subscription information of the target network slice, or the charging method of the target network slice is per session or Billing is based on traffic, or the service type contracted by the target network slice is a specific service type, or the terminal device requesting access is a high-value customer, or the slice operation analysis and prediction result of the target network slice shows that it is below a certain threshold, or access is requested
  • the mobile behavior analysis and prediction result of the terminal device indicates that the service load of the terminal device requesting access is lower than a certain threshold.
  • the corresponding second condition in the session establishment process of the terminal device may include, for example, that the overall limit is allowed in the slice subscription information of the target network slice, or the charging method of the target network slice is per session.
  • the service type contracted by the target network slice is a specific service type, or the terminal device requesting access is a high-value customer, or the overall number of sessions and traffic bandwidth of the target network slice is lower than the overload risk threshold, or the terminal
  • the quality of service QoS parameters subscribed by the device indicate that the service of the terminal device is allowed to be preempted, or the slice operation analysis or prediction result of the target network slice shows that it is below a certain threshold, or the mobile or communication behavior analysis prediction result of the terminal device requesting access indicates a request
  • the service load of the connected terminal equipment is lower than a certain threshold.
  • step S801, step S802, and step S803 there is no inevitable order of execution between step S801, step S802, and step S803 in the embodiment of the present application. Any one of these steps may be executed first, and then the remaining two steps may be executed separately; or Perform two of these steps at the same time, and then perform the remaining steps; it is also possible to perform one of the steps first, and then perform the remaining two steps at the same time; it is also possible to perform these three steps at the same time. This is not specifically limited.
  • S804-S807 are the same as steps S703-S706 in the embodiment shown in FIG. 7.
  • steps S703-S706 in the embodiment shown in FIG. 7.
  • the PCF network element also needs to obtain the overall restriction strategy of the target network slice required in the registration process and the area restriction strategy of the target network slice in the first area (that is, area A) from the UDR network element ( It can be referred to as the first area restriction strategy), which will be described in a unified manner here, and will not be repeated here.
  • step S810 when the PCF network element determines that the service usage of the target network slice in the first area reaches or exceeds the first service limit; or when the PCF network element determines that the service usage of the target network slice in the first area does not exceed the first
  • the following step S810 is directly executed; when the PCF network element determines that the service usage of the target network slice in the first area does not exceed the first Service limit, but when the overall service usage of the target network slice reaches or exceeds the overall limit of the target network slice, first perform step S808 and/or step S809 to determine whether the second condition is met, and then perform step S810:
  • the PCF network element obtains the contract information of the terminal device or the target network slice from the UDM network element, and determines whether it is satisfied according to the contract information of the terminal device or the target network slice: the slice contract information of the target network slice allows the overall limit, or the target
  • the billing method for network slicing is based on session or traffic, or the service type contracted by the target network slicing is a specific service type, or the terminal device requesting access is a high-value customer.
  • the PCF network element obtains from the NWDAF network element one or more of the mobile behavior analysis and prediction results of the terminal device requesting access or the slice operation analysis and prediction results of the target network slice, and determines whether it meets: the slice operation of the target network slice
  • the analysis and prediction result shows that it is below a specific threshold, or the analysis and prediction result of the mobile behavior of the terminal device requesting access indicates that the service load of the terminal device requesting access is below the specific threshold.
  • the PCF network element sends a message u1 to the AMF-A network element.
  • the AMF-A network element receives the message u1 from the PCF network element.
  • the message u1 in the embodiment of the present application may be, for example, an associated registration management policy response as shown in FIG. 8, which is not specifically limited in the embodiment of the present application.
  • the message u1 can carry that the service usage of the target network slice in the first area reaches Or an instruction that exceeds the first service quota or an instruction that the terminal device is not allowed to use the target network slice, and then the branch 1 corresponding to the following step S811 can be executed; when the PCF network element determines the service of the target network slice in the first area in step S807 When the usage does not exceed the first service limit, and the overall service usage of the target network slice does not exceed the overall limit of the target network slice, the above message u1 can carry an indication that the terminal device is allowed to use the target network slice, and the following steps can be performed S814 corresponds to branch two; when the PCF network element determines in step S807 that the service usage of the target network slice in the first area does not exceed the first service quota, but the overall service usage of the target network slice reaches or exceeds
  • the branch 1 corresponding to the following step S811 can be continued or continued Determine whether the overall service usage of the target network slice exceeds the overall quota of the target network slice.
  • the PCF network element determines that the overall service usage of the target network slice is equal to (that is, reached) the overall quota of the target network slice, for this demarcation point, you can continue to execute the branch two corresponding to the following step S814 or determine whether the second branch is satisfied.
  • this embodiment of the application does not specifically limit this.
  • step S811 is the same as step S708 in the embodiment shown in FIG. 7.
  • step S708 in the embodiment shown in FIG. 7.
  • S812-S813 are the same as steps S709-S710 in the embodiment shown in FIG. 7.
  • steps S709-S710 in the embodiment shown in FIG. 7.
  • step S814 is the same as step S711 in the embodiment shown in FIG. 7.
  • the PCF network element may also update the actual overall number of registered terminals of the target network slice and the actual number of registered terminals of the target network slice in the first area to the UDR network element. Subsequently, when the terminal device logs off from the target network slice or moves out of the first area, the PCF network element can also update the actual overall number of registered terminals of the target network slice and the actual number of registered terminals of the target network slice in the first area to the UDR network element
  • the embodiments of this application do not specifically limit this.
  • each target network slice can be processed separately according to the above steps S806-S814, which will not be repeated here.
  • the method for controlling the use of the network slice provided in the embodiment of the present application further includes the following steps S815-S823 or the following steps S815-S824 as shown in the session establishment process:
  • S815-S818 are the same as steps S712-S715 in the embodiment shown in FIG. 7.
  • steps S712-S715 in the embodiment shown in FIG. 7.
  • the PCF network element also needs to obtain the overall restriction strategy of the target network slice required in the session establishment process and the area restriction strategy of the target network slice in the first area (ie area A) from the UDR network element (It can be referred to as the first area restriction strategy), which will be described in a unified manner here, and will not be repeated here.
  • step S810 when the PCF network element determines that the service usage of the target network slice in the first area reaches or exceeds the first service limit; or when the PCF network element determines that the service usage of the target network slice in the first area does not exceed the first
  • the following step S810 is directly executed; when the PCF network element determines that the service usage of the target network slice in the first area does not exceed the first Service limit, but when the overall service usage of the target network slice reaches or exceeds the overall limit of the target network slice, first execute step S819 and/or step S820 and/or step S821 to determine whether the second condition is met, and then execute step S822:
  • the PCF network element obtains the contract information of the terminal device or the target network slice from the UDM network element, and determines whether it is satisfied according to the contract information of the terminal device or the target network slice: the slice contract information of the target network slice allows the overall limit, or the target
  • the billing method of network slicing is based on session or traffic, or the service type contracted by the target network slicing is a specific service type, or the terminal device requesting access is a high-value customer, or the service quality QoS parameter indication of the terminal device contract
  • the business of the terminal device is allowed to be preempted.
  • the PCF network element obtains from the NWDAF network element one or more of the mobile or communication behavior analysis and prediction results of the terminal device requesting access or the slice operation analysis and prediction results of the target network slice, and determines whether it meets:
  • the prediction result of slice operation analysis shows that it is lower than a certain threshold, or the analysis prediction result of the movement or communication behavior of the terminal device requesting access indicates that the service load of the terminal device requesting access is below the certain threshold.
  • the PCF network element obtains the traffic bandwidth of the target network slice from the UDR network element; when the overall service usage of the network slice obtained in step S817 is In the case of traffic bandwidth, the PCF network element obtains the overall number of sessions of the target network slice from the UDR network element. Then the PCF network element determines whether it is satisfied: the overall number of sessions and traffic bandwidth of the target network slice are lower than the overload risk threshold.
  • the PCF network element sends a message v1 to the SMF network element.
  • the SMF network element receives the message v1 from the PCF network element.
  • the message v1 in the embodiment of the present application may be, for example, an associated session management policy response as shown in FIG. 8, which is not specifically limited in the embodiment of the present application.
  • the above message v1 may carry that the service usage of the target network slice in the first area reaches Or an indication that the first service quota is exceeded or an indication that the terminal device is not allowed to use the target network slice, then the branch i corresponding to the following step S823 can be executed; when the PCF network element determines the service of the target network slice in the first area in step S818 When the usage does not exceed the first service quota, and the overall service usage of the target network slice does not exceed the overall quota of the target network slice, the above message v1 can carry an indication that the terminal device is allowed to use the target network slice, and the following steps can be performed Branch ii corresponding to S824; when the PCF network element determines in step S818 that the service usage of the target network slice in the first area does not exceed the first service limit, but the overall service usage of the target network slice
  • step S818 determines in step S818 that the service usage of the target network slice in the first area does not exceed the first service quota, but the overall service usage of the target network slice reaches or exceeds the overall quota of the target network slice, according to It is determined in step S819 and/or step S820 and/or step S821 that the second condition is not met, the above message v1 may carry an indication that the terminal device is not allowed to use the target network slice, and the branch i corresponding to the following step S823 may be executed.
  • the branch i corresponding to the following step S823 can be continued or continued Determine whether the overall service usage of the target network slice exceeds the overall quota of the target network slice.
  • the branch ii corresponding to the following step S824 can be continued or whether the second branch is satisfied Conditions, this embodiment of the application does not specifically limit this.
  • step S823 is the same as step S624 in the embodiment shown in FIG. 6.
  • step S624 in the embodiment shown in FIG. 6.
  • step S824 is the same as step S625 in the embodiment shown in FIG. 6.
  • the PCF network element can also update the UDR network element to the overall service usage of the target network slice during the session establishment process and the service usage of the target network slice in the first area. the amount.
  • the PCF network element may also update the overall service usage of the target network slice during the session establishment process and the service usage of the target network slice in the first area to the UDR network element. If the session no longer uses the user plane node in the area due to the movement of the terminal device, the PCF network element can also report the overall service usage of the target network slice and the target network slice in the first area during the establishment of the new session of the UDR network element.
  • the amount of service usage is not specifically limited in the embodiment of this application.
  • the first network element can determine whether to access the terminal device to the target network slice according to the first condition.
  • the first condition includes: whether the service usage of the target network slice in the first area exceeds the first service quota.
  • the embodiments of the present application implement sub-regional control of network slicing access, and therefore can avoid congestion or overload of wireless side network nodes in the region, not only cannot guarantee the service quality of this network slice, but may also slice other networks. This can limit the excessive use of network slicing resources by customers, and at the same time guarantee the service quality of network slicing.
  • the first condition may also include: whether the overall service usage of the target network slice exceeds the overall quota. Considering that if the terminal equipment in a certain area of the network slice is very sparse, there may be a lot of idle resources in this area, but because the service usage of the entire network slice exceeds the specified limit, the terminal equipment in this area will also be restricted to access. Cause a waste of resources in this area. Therefore, in the embodiment of this application, when the overall service usage of the target network slice reaches or exceeds the overall limit, but the service usage of the target network slice in the first area does not exceed the first service limit, if the second condition is met, the first A network element allows the terminal device to use the target network slice.
  • the user can be allowed in the first area under certain scenarios.
  • Regions use target network slicing resources, so the utilization of network resources can be improved, which not only brings more economic benefits to operators, but also improves the business experience of value users.
  • the actions of the PCF network element in the above steps S801 to S823 or step S824 can be executed by the processor 301 in the communication device 300 shown in FIG. 3 calling the application program code stored in the memory 303. There are no restrictions.
  • the first network element in the communication system shown in FIG. 1 is used as the policy control network element
  • the communication system shown in FIG. 1 is applied to the 5G network architecture shown in FIG. 2, and the first area is shown in FIG. Take the area A of as an example.
  • another network slice usage control method provided in this embodiment of this application includes the following steps:
  • step S901 is the same as step S801 in the embodiment shown in FIG. 8. For related descriptions, reference may be made to the embodiment shown in FIG. 8, which will not be repeated here.
  • the OAM entity sends the overall restriction policy of the target network slice to the UDR network element.
  • the UDR network element receives the overall restriction policy of the target network slice from the OAM entity.
  • step S803 in the embodiment shown in FIG. 8, which will not be repeated here.
  • S903-S904 are the same as steps S602-S603 in the embodiment shown in FIG. 6, and related descriptions can refer to the embodiment shown in FIG. 6, which will not be repeated here.
  • steps S901-S904 there is no necessary order of execution between steps S901-S904 in the embodiment of this application. One or more steps may be executed first, and then the remaining steps may be executed, or these 4 steps may be executed simultaneously. Steps, this embodiment of the application does not specifically limit this.
  • S905-S906 are the same as steps S503-S504 in the embodiment shown in FIG. 5, and related descriptions can refer to the embodiment shown in FIG. 5, which will not be repeated here.
  • the service usage of the target network slice in the first area includes the actual number of registered terminals of the target network slice in the first area.
  • the AMF-A network element maintains the actual number of registered terminals in each area managed by the AMF-A network element for each network slice currently serving during the registration management process, including the actual registration of the target network slice in the first area Number of terminals. Furthermore, the AMF-A network element may compare the actual number of registered terminals of the target network slice in the first area with the maximum number of registered terminals allowed by the target network slice in the first area determined in step S903.
  • step S907 When the actual number of registered terminals of the target network slice in the first area reaches or exceeds the maximum number of registered terminals allowed by the target network slice in the first area, the following branch 1 corresponding to step S907 is executed; when the target network slice is in the first area When the actual number of registered terminals in an area does not exceed the maximum number of registered terminals allowed by the target network slice in the first area, the following step S910 and branch 2 corresponding to the subsequent steps are executed.
  • the following steps can be continued for the demarcation point
  • the branch 1 corresponding to S907 or the branch 2 corresponding to the following step S910 and subsequent steps continue to be executed, which is not specifically limited in the embodiment of the present application.
  • step S907 is the same as step S505 in the embodiment shown in FIG. 5.
  • step S505 in the embodiment shown in FIG. 5.
  • S908-S909 are the same as steps S506-S507 in the embodiment shown in FIG. 5, and related descriptions can refer to the embodiment shown in FIG. 5, which will not be repeated here.
  • step S910 is the same as step S508 in the embodiment shown in FIG. 5.
  • the NSSF network element sends a message a2 to the PCF network element.
  • the PCF network element receives the message a2 from the NSSF network element.
  • the message a2 carries the actual number of registered terminals of the target network slice in the first area.
  • the message a2 in the embodiment of the present application may be, for example, an associated slice management policy request as shown in FIG. 9, which is not specifically limited in the embodiment of the present application.
  • S912-S913 are the same as steps S610-S611 in the embodiment shown in FIG. 6, and related descriptions can refer to the embodiment shown in FIG. 6, which will not be repeated here.
  • the PCF network element also needs to obtain the overall restriction strategy of the target network slice required in the registration process from the UDR network element, which is described here in a unified manner, and will not be described in detail below.
  • step S916 when the PCF network element determines that the overall service usage of the target network slice does not exceed the overall quota of the target network slice, the following step S916 is directly executed; when the PCF network element determines that the overall service usage of the target network slice reaches or exceeds the target network When slicing the overall quota, first perform step S914 and/or step S915 to determine whether the second condition is met, and then perform step S916:
  • S914-S915 are the same as steps S808-S809 in the embodiment shown in FIG. 8.
  • steps S808-S809 are the same as steps S808-S809 in the embodiment shown in FIG. 8.
  • S916 The PCF network element sends a message b2 to the NSSF network element.
  • the NSSF network element receives the message b2 from the PCF network element.
  • the message b2 in the embodiment of the present application may be, for example, an associated slice management policy response as shown in FIG. 9, which is not specifically limited in the embodiment of the present application.
  • the NSSF network element sends a message c2 to the AMF-A network element.
  • the AMF-A network element receives the message c2 from the NSSF network element.
  • the message c2 in the embodiment of the present application may be, for example, a slice selection response message as shown in FIG. 9, which is not specifically limited in the embodiment of the present application.
  • the message b2 may carry the quota of the service usage in the first area or allow the terminal device to use the target The indication of network slicing, the above message c2 can carry the quota of the service usage in the first area or the indication of allowing the terminal device to use the target network slice, and then the branch b corresponding to the following step S921 can be executed; when the PCF network in step S913 When the meta determines that the overall service usage of the target network slice reaches or exceeds the overall quota of the target network slice, when the second condition is determined to be satisfied according to step S914 and/or step S915, the above message b2 can carry the service usage in the first area The quota or the indication of allowing the terminal device to use the target network slice or the over-limit access identifier, the above message c2 may carry the quota of the service usage
  • the branch b corresponding to the following step S921 can be continued to be executed or whether it is satisfied
  • the second condition is not specifically limited in the embodiments of this application.
  • step S918 is the same as step S708 in the embodiment shown in FIG. 7.
  • step S708 in the embodiment shown in FIG. 7.
  • step S918 please refer to the embodiment shown in FIG. 7, which will not be repeated here.
  • S919-S920 are the same as steps S709-S710 in the embodiment shown in FIG. 7.
  • steps S709-S710 in the embodiment shown in FIG. 7.
  • step S921 is the same as step S711 in the embodiment shown in FIG. 7.
  • step S711 in the embodiment shown in FIG. 7.
  • the PCF network element may also update the actual overall number of registered terminals of the target network slice to the UDR network element. Subsequently, when the terminal device logs off from the target network slice or moves out of the first area, the PCF network element can also update the actual overall number of registered terminals of the target network slice to the UDR network element, which is not specifically limited in this embodiment of the application.
  • each target network slice can be processed separately in the manner of steps S906-S921 described above, which will not be repeated here.
  • the method for controlling the use of the network slice provided in the embodiment of the present application further includes the following steps S922-S932 or the following steps S922-S933 as shown in the session establishment process:
  • S922-S923 are the same as steps S617-S618 in the embodiment shown in FIG. 6.
  • steps S617-S618 in the embodiment shown in FIG. 6.
  • step S924 when the service usage of the target network slice in the first area reaches or exceeds the first service quota, the branch 3 corresponding to the following step S924 is executed; when the service usage of the target network slice in the first area does not exceed For the first business quota, perform the following step S925 and branch four corresponding to the following steps:
  • step S924 is the same as step S619 in the embodiment shown in FIG. 6.
  • step S619 in the embodiment shown in FIG. 6.
  • S925-S927 are the same as steps S620-S622 in the embodiment shown in FIG. 6.
  • steps S620-S622 in the embodiment shown in FIG. 6.
  • the PCF network element also needs to obtain the overall restriction strategy of the target network slice required in the session establishment process from the UDR network element, which is described here in a unified manner, and will not be repeated in the following.
  • step S931 when the PCF network element determines that the overall service usage of the target network slice does not exceed the overall quota of the target network slice, the following step S931 is directly executed; when the PCF network element determines that the overall service usage of the target network slice reaches or exceeds the target network When slicing the overall quota, first perform step S928 and/or step S929 and/or step S930 to determine whether the second condition is met, and then perform step S931:
  • S928-S930 are the same as steps S819-S821 in the embodiment shown in FIG. 8.
  • steps S819-S821 in the embodiment shown in FIG. 8.
  • the PCF network element sends a message d2 to the SMF network element.
  • the SMF network element receives the message d2 from the PCF network element.
  • the message d2 in the embodiment of the present application may be, for example, an associated session management policy response as shown in FIG. 9, which is not specifically limited in the embodiment of the present application.
  • the above message d2 may carry an indication that the terminal device is allowed to use the target network slice, and the following steps may be performed Branch ii corresponding to S933; when the PCF network element determines in step S927 that the overall service usage of the target network slice reaches or exceeds the overall quota of the target network slice, when it is determined according to step S928 and/or step S929 and/or step S930 to meet the first Second condition, the above message d2 can carry an indication that the terminal device is allowed to use the target network slice or the over-limit access identifier, and then the branch ii corresponding to the following step S933 can be executed; when the PCF network element determines the entire target network slice in step S927 When the service usage reaches or exceeds the overall limit of the target network slice, when it is determined according to step S928 and/or step S9
  • the PCF network element determines that the overall service usage of the target network slice is equal to (that is, the above-mentioned reach) the overall quota of the target network slice, for this demarcation point, you can continue to execute the branch ii corresponding to the following step S933 or determine whether it is satisfied
  • the second condition is not specifically limited in the embodiments of this application.
  • step S932 is the same as step S823 in the embodiment shown in FIG. 8. For related description, refer to the embodiment shown in FIG. 8, which will not be repeated here.
  • step S933 is the same as step S824 in the embodiment shown in FIG. 8.
  • step S824 in the embodiment shown in FIG. 8.
  • the PCF network element can also update the overall service usage of the target network slice during the session establishment process to the UDR network element.
  • the PCF network element can also update the overall service usage of the target network slice during the session establishment process to the UDR network element. If the session no longer uses the user plane node in the area due to the movement of the terminal device, the PCF network element can also report the overall service usage of the target network slice during the establishment of a new session to the UDR network element, which is not specifically limited in the embodiment of this application. .
  • step S904 may not be performed.
  • the first service quota-related information of the target network slice configured in step S903 in the first area may include the corresponding information in the session establishment process of the terminal device.
  • Information about the first service quota of the target network slice in the first area, and then during the session establishment process of the terminal device, the AMF-A network element determines whether the service usage of the target network slice in the first area exceeds the first Service quota, and then when the AMF-A network element determines that the service usage of the target network slice in the first area reaches or exceeds the first service quota, step S924 is executed; when the AMF-A network element determines that the target network slice is in the first area
  • the subsequent steps S925-S932 or S925-S933 will continue to be executed. This embodiment of the application does not do this
  • the actions of the PCF network element, AMF-A network element, or SMF network element in the above steps S901 to S932 or step S933 may be called by the processor 301 in the communication device 300 shown in FIG. 3 to call the application stored in the memory 303
  • the program code is executed, and this embodiment does not impose any restriction on this.
  • the first network element in the communication system shown in FIG. 1 is a mobility management network element or a session management network element, and the communication system shown in FIG. 1 is applied to the 5G network architecture shown in FIG.
  • the area is the area A in FIG. 2 as an example.
  • another network slice usage control method provided by this embodiment of the present application includes the following steps:
  • step S1001 is the same as step S801 in the embodiment shown in FIG. 8. For related descriptions, reference may be made to the embodiment shown in FIG. 8, which will not be repeated here.
  • the OAM entity sends information about the business quota of the target network slice in each area and the overall quota policy of the target network slice to the AMF network elements in each area covered by the target network slice.
  • the AMF network elements in each area covered by the target network slice receive information about the business quota of the target network slice in each area from the OAM entity and the overall quota policy of the target network slice.
  • FIG. 10 is only an example of using the OAM entity to send the AMF-A network element of the first area (ie area A) covered by the target network slice to the first service quota related information and the target of the target network slice in the first area.
  • the overall quota strategy of the network slice is described as an example; correspondingly, the AMF-A network element receives the first service quota related information of the target network slice in the first area from the OAM entity and the overall quota strategy of the target network slice.
  • the information related to the first service quota in step S1002 includes the first service quota required in the registration process of the terminal device or information used to determine the first service quota.
  • the overall quota policy of the target network slice in step S1002 may be, for example, when the overall service usage of the target network slice reaches or exceeds the overall quota, but the service usage of the target network slice in the area does not exceed the service quota in the area If the second condition is met, the terminal device is allowed to use the target network slice.
  • the corresponding second condition in the registration process of the terminal device may include, for example, the session indicated by the NSSF network element when the NSSF network element indicates that the overall service usage of the target network slice reaches or exceeds the overall quota The quantity quota exceeds the specified quantity.
  • the OAM entity sends the relevant information about the business quota of the target network slice in each area and the overall quota policy of the target network slice to the SMF network elements in each area covered by the target network slice.
  • the SMF network elements in each area covered by the target network slice receive information about the business quota of the target network slice in each area from the OAM entity and the overall quota policy of the target network slice.
  • FIG. 10 is only an example of using the OAM entity to send the first service quota related information of the target network slice in the first area and the target network slice to the SMF network element in the first area (ie, area A) covered by the target network slice.
  • the SMF network element receives the first service quota related information of the target network slice in the first area from the OAM entity and the overall quota strategy of the target network slice.
  • the information related to the first service quota in step S1003 includes the first service quota required in the session establishment process of the terminal device or the information used to determine the first service quota.
  • the overall quota policy of the target network slice in step S1003 may be, for example, when the overall service usage of the target network slice reaches or exceeds the overall quota, but the service usage of the target network slice in the area does not exceed the service quota in the area If the second condition is met, the terminal device is allowed to use the target network slice.
  • the corresponding second condition in the session establishment process of the terminal device may be, for example: when the PCF network element indicates that the overall service usage of the target network slice reaches or exceeds the overall quota, the terminal device The service QoS parameter indicates that the session can be preempted.
  • step S1001, step S1002, and step S1003 there is no inevitable sequence of execution between step S1001, step S1002, and step S1003 in the embodiment of the present application, and any one of these steps may be executed first, and then the remaining two steps may be executed respectively; or Perform two of these steps at the same time, and then perform the remaining steps; it is also possible to perform one of the steps first, and then perform the remaining two steps at the same time; it is also possible to perform these three steps at the same time. This is not specifically limited.
  • S1004-S1005 are the same as steps S905-S906 in the embodiment shown in FIG. 9.
  • steps S905-S906 are the same as steps S905-S906 in the embodiment shown in FIG. 9.
  • the service usage of the target network slice in the first area includes the actual number of registered terminals of the target network slice in the first area.
  • the AMF-A network element maintains the actual number of registered terminals in each area managed by the AMF-A network element for each network slice currently serving during the registration management process, including the actual registration of the target network slice in the first area Number of terminals. Furthermore, the AMF-A network element may compare the actual number of registered terminals of the target network slice in the first area with the maximum number of registered terminals allowed by the target network slice in the first area determined in step S1002.
  • step S1006 When the actual number of registered terminals of the target network slice in the first area reaches or exceeds the maximum number of registered terminals allowed by the target network slice in the first area, the following branch 1 corresponding to step S1006 is executed; when the target network slice is in the first area When the actual number of registered terminals in an area does not exceed the maximum number of registered terminals allowed by the target network slice in the first area, the following step S1009 and branch 2 corresponding to the subsequent steps are executed.
  • the following steps can be continued for the demarcation point
  • the branch 1 corresponding to S1006 or the branch 2 corresponding to the following step S1009 and subsequent steps continue to be executed, which is not specifically limited in the embodiment of the present application.
  • S1009-S1012 are the same as steps S910-S913 in the embodiment shown in FIG. 9.
  • steps S910-S913 in the embodiment shown in FIG. 9.
  • the above message b2 may carry the quota of the service usage in the first area or allow the terminal device to use the target The indication of network slicing, the above message c2 can carry the quota of the service usage in the first area or the indication of allowing the terminal device to use the target network slice, and then the branch b corresponding to the following step S1019 can be executed; when the PCF network in step S1012 When the meta determines that the overall service usage of the target network slice reaches or exceeds the overall quota of the target network slice, the above message b2 and message c2 can carry the quota of the service usage in the first area (0) or the overall target network slice An indication that the service usage reaches or exceeds the overall quota of the target network slice. In addition, the above message b2 and message c2 may also carry a quota for the number of
  • the AMF-A network element determines whether the second condition in step S1002 is satisfied.
  • step S1016 corresponds to branch a.
  • the PCF network element determines that the overall service usage of the target network slice is equal to (that is, the above-mentioned reach) the overall quota of the target network slice, for this demarcation point, the branch b corresponding to the following step S1019 can be continued or step S1015 can be executed.
  • the embodiments of the present application do not specifically limit this.
  • step S1016 is the same as step S918 in the embodiment shown in FIG. 9.
  • step S918 in the embodiment shown in FIG. 9.
  • the PCF network element may also update the actual overall number of registered terminals of the target network slice to the UDR network element. Subsequently, when the terminal device logs off from the target network slice or moves out of the first area, the PCF network element can also update the actual overall number of registered terminals of the target network slice to the UDR network element, which is not specifically limited in this embodiment of the application.
  • step S1022 when the service usage of the target network slice in the first area reaches or exceeds the first service quota, the branch 3 corresponding to the following step S1022 is executed; when the service usage of the target network slice in the first area does not exceed In the case of the first business quota, the following step S1023 and branch four corresponding to the following steps are executed:
  • step S1022 is the same as step S924 in the embodiment shown in FIG. 9.
  • S1023-S1025 are the same as steps S925-S927 in the embodiment shown in FIG. 9.
  • steps S925-S927 in the embodiment shown in FIG. 9.
  • the SMF network element determines whether the second condition in step S1003 is satisfied.
  • the PCF network element can also update the overall service usage of the target network slice during the session establishment process to the UDR network element.
  • the PCF network element can also update the overall service usage of the target network slice during the session establishment process to the UDR network element. If the session no longer uses the user plane node in the area due to the movement of the terminal device, the PCF network element can also report the overall service usage of the target network slice during the establishment of a new session to the UDR network element, which is not specifically limited in the embodiment of this application. .
  • the actions of the PCF network element, AMF-A network element, or SMF network element in the above steps S1001 to S1028 or step S1029 can be invoked by the processor 301 in the communication device 300 shown in FIG. 3 to call the application stored in the memory 303
  • the program code is executed, and this embodiment does not impose any restriction on this.
  • the OAM entity sends the overall restriction policy of the target network slice to the UDR network element.
  • the UDR network element receives the overall restriction policy of the target network slice from the OAM entity.
  • the overall restriction strategy of the target network slice may be, for example, when the overall service usage of the target network slice reaches or exceeds the overall limit, but the service usage of the target network slice in the area does not exceed the limit.
  • the business quota in the area is met, if the second condition is met, the terminal device is allowed to use the target network slice.
  • the OAM entity sends information about the business quota of the target network slice in each area and the overall quota of the target network slice to the AMF network elements in each area covered by the target network slice.
  • the AMF network elements in each area covered by the target network slice receive information about the business quota of the target network slice in each area from the OAM entity and the overall quota of the target network slice.
  • FIG. 11 is only an example of using the OAM entity to send the AMF-A network element of the first area (ie area A) covered by the target network slice to the first service quota related information and the target of the target network slice in the first area.
  • the overall limit of the network slice is described as an example; correspondingly, the AMF-A network element receives the first service limit related information of the target network slice in the first area from the OAM entity and the overall limit of the target network slice.
  • step S1101, step S1102, and step S1103 there is no inevitable order of execution between step S1101, step S1102, and step S1103 in the embodiment of the present application. Any one of these steps may be executed first, and then the remaining two steps may be executed respectively; or Perform two of these steps at the same time, and then perform the remaining steps; it is also possible to perform one of the steps first, and then perform the remaining two steps at the same time; it is also possible to perform these three steps at the same time. This is not specifically limited.
  • step S1104 is the same as step S1004 in the embodiment shown in FIG. 10.
  • step S1004 in the embodiment shown in FIG. 10.
  • the service usage of the target network slice in the first area, the first service quota, the overall service usage of the target network slice, and the overall quota of the target network slice in step S1105 are all information required in the registration process of the terminal device
  • the service usage of the target network slice in the first area, the first service quota, the overall service usage of the target network slice, and the overall quota of the target network slice in step S1105 are all information required in the registration process of the terminal device
  • the branch 1 corresponding to the following step S1109 is executed; when the AMF-A network element determines the target network slice When the service usage in the first area does not exceed the first service quota, and the overall service usage of the target network slice does not exceed the overall service limit of the target network slice, execute the branch 2 corresponding to the following step S1112; when the AMF-A network When it is determined that the service usage of the target network slice in the first area does not exceed the first service quota, and the overall service usage of the target network slice reaches or exceeds the overall quota of the target network slice, steps S1106-S1108 are executed:
  • the AMF-A network element obtains the overall quota policy of the target network slice from the UDR network element through an access management (AM)-PCF network element.
  • AM access management
  • the AMF-A network element obtains the slice operation status analysis and prediction from the NWDAF network element.
  • the AMF-A network element determines that the second condition is satisfied, it continues to execute the branch two corresponding to the following step S1112; when the AMF-A network element determines that the second condition is not satisfied, it continues to perform the branch one corresponding to the following step S1109.
  • the branch 1 corresponding to the following step S1109 can be continued to be executed. Or execute steps S1106-S1108, which are not specifically limited in the embodiment of the present application.
  • step S1109 is the same as step S1016 in the embodiment shown in FIG. 10.
  • step S1016 is the same as step S1016 in the embodiment shown in FIG. 10.
  • S1110-S1111 are the same as steps S1017-S1018 in the embodiment shown in FIG. 10.
  • steps S1017-S1018 are the same as steps S1017-S1018 in the embodiment shown in FIG. 10.
  • each target network slice can be processed separately according to the above steps S1105-S1112, which will not be repeated here.
  • the method for controlling the use of network slices provided in the embodiment of the present application further includes the following steps S1113-1118 or the following steps S1113-S1119 as shown in the session establishment process:
  • step S1113 is the same as step S1020 in the embodiment shown in FIG. 10.
  • step S1020 in the embodiment shown in FIG. 10.
  • step S1113 please refer to the embodiment shown in FIG. 10, which will not be repeated here.
  • the SMF network element obtains the slice operation status analysis and prediction from the NWDAF network element.
  • the slice operating state analysis prediction includes one or more of the current or future operating load of the target network slice in the first area, the overall operating load of the target network slice, or the network performance of the target network slice in the first area.
  • the SMF network element determines that the second condition is met, it continues to execute the branch ii corresponding to the following step S1119; when the SMF network element determines that the second condition is not met, it continues to execute the branch i corresponding to the following step S1118.
  • the SMF network element determines that the service usage of the target network slice in the first area is equal to (that is, the above-mentioned reaches) the first service quota, for this demarcation point, the branch i corresponding to the following step S1118 can be continued or executed Steps S1115-S1117, which are not specifically limited in the embodiment of the present application.
  • the demarcation point can continue to execute The branch ii corresponding to the following step S1119 or steps S1115-S1117 are executed, which is not specifically limited in the embodiment of the present application.
  • step S1118 is the same as step S1028 in the embodiment shown in FIG. 10.
  • step S1119 is the same as step S1029 in the embodiment shown in FIG. 10.
  • step S1029 in the embodiment shown in FIG. 10.
  • the actions of the AM-PCF network element, SM-PCF network element, AMF-A network element, or SMF network element in step S1101 to step S1118 or step S1119 may be performed by the processor in the communication device 300 shown in FIG. 3 301 calls the application code stored in the memory 303 to execute, and this embodiment does not impose any limitation on this.
  • the registration process and the session establishment process in the various embodiments shown in FIG. 5 to FIG. 11 can be decoupled from each other.
  • the terminal device may use the registration process in any of the embodiments to register, and use the session establishment process in any of the embodiments to establish a session, which is not specifically limited in this embodiment of the application.
  • the methods and/or steps implemented by the first network element may also be implemented by components (for example, chips or circuits) that can be used for the first network element.
  • an embodiment of the present application also provides a communication device.
  • the communication device may be the first network element in the foregoing method embodiment, or a device including the foregoing first network element, or a component that can be used for the first network element.
  • the communication device includes hardware structures and/or software modules corresponding to various functions.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.
  • FIG. 12 shows a schematic structural diagram of a first network element 120.
  • the first network element 120 includes a transceiver module 1201 and a processing module 1202.
  • the transceiver module 1201 may also be referred to as a transceiver unit to implement a transceiver function, for example, it may be a transceiver circuit, a transceiver, a transceiver or a communication interface.
  • the transceiver module 1201 is configured to receive a first message, and the first message is used to request the terminal device to access the target network slice, where the target network slice covers multiple areas, and the multiple areas include a first area, and the first area It is the area where the terminal device is currently located.
  • the processing module 1202 is configured to determine whether to connect the terminal device to the target network slice according to a first condition, where the first condition includes: whether the service usage of the target network slice in the first area exceeds the first service quota.
  • the processing module 1202 is specifically configured to reject the first message when the service usage of the target network slice in the first area reaches or exceeds the first service limit.
  • the first condition further includes: whether the overall service usage of the target network slice exceeds the overall quota.
  • the processing module 1202 is specifically configured to: when the service usage of the target network slice in the first area does not exceed the first service limit, but the overall service usage of the target network slice reaches or exceeds the overall limit, reject the first news.
  • the transceiver module 1201 is also used to receive a second message from a second network element.
  • the second message carries first information.
  • the first information indicates that the overall service usage of the target network slice reaches or exceeds the overall service usage. Limit.
  • the first information is that the quota of service usage in the first area is 0, or the first information is an indication that the overall service usage of the target network slice reaches or exceeds the overall quota of the target network slice.
  • the transceiver module 1201 is also used to receive a third message from a third network element, the third message carries the overall service usage of the target network slice; the processing module 1202 also uses To determine that the overall service usage of the target network slice reaches or exceeds the overall quota of the target network slice.
  • the processing module 1202 is specifically configured to: when the overall service usage of the target network slice reaches or exceeds the overall limit, but the service usage of the target network slice in the first area does not exceed the first service limit, if the first service limit is met, The second condition is to allow the terminal device to use the target network slice.
  • the first network element is a policy control network element
  • the first message is an associated registration management policy request or an associated slice management policy request
  • the second condition includes: the slice subscription information of the target network slice allows the overall overrun Or when the target network slice is charged by session or traffic, or the service type contracted by the target network slice is a specific service type, or when the terminal device requesting access is a high-value customer, or the target network slice is The slice operation analysis or prediction result shows that it is below a specific threshold, or the mobile behavior analysis prediction result of the terminal device requesting access indicates that the service load of the terminal device requesting access is below the specific threshold.
  • the processing module 1202 is further configured to: when the first network element receives an associated slice management policy request from the slice selection function network element, determine that the service usage of the target network slice in the first area is different. Exceed the first business quota.
  • the first network element is a policy control network element
  • the first message is an associated session management policy request
  • the second condition includes: the overall limit is allowed in the slice subscription information of the target network slice, or the target network
  • the billing method for slices is based on session or traffic, or the service type contracted by the target network slice is a specific service type, or the terminal device requesting access is a high-value customer, or the overall number of sessions and traffic bandwidth of the target network slice It is lower than the overload risk threshold, or the QoS parameters of the terminal equipment contract indicate that the terminal equipment’s business is allowed to be preempted, or the slice operation analysis or prediction result of the target network slice shows that it is below a certain threshold, or the mobile or communication of the terminal equipment requesting access The behavior analysis prediction result indicates that the service load of the terminal device requesting access is lower than a certain threshold.
  • the processing module 1202 is further configured to, when the first network element receives an associated session management policy request from the session management network element, determine that the service usage of the target network slice in the first area does not exceed The first business limit.
  • the first network element is a mobility management network element
  • the first message is a registration request
  • the second condition includes: when the slice selection function network element indicates that the overall service usage of the target network slice reaches or exceeds the overall service usage When quota is set, the quota for the number of sessions indicated by the slice selection function network element exceeds the specified number.
  • the processing module 1202 is further configured to: when the first network element receives the session quantity quota from the slice selection function network element and the overall service usage of the target network slice reaches or exceeds the overall quota of the target network slice In the case of instructions, determine that the overall service usage of the target network slice reaches or exceeds the overall quota.
  • the first network element is a mobility management network element, and the first message is a registration request; or, the first network element is a session management network element, and the first message is a session establishment request;
  • the second condition includes : The operating load of the target network slice in the first area is lower than the specified threshold; or, the overall operating load of the target network slice is lower than the specified threshold, or the network performance of the target network slice in the first area is higher than the specified threshold.
  • the first network element 120 is presented in the form of dividing various functional modules in an integrated manner.
  • the "module” here may refer to a specific ASIC, a circuit, a processor and memory that executes one or more software or firmware programs, an integrated logic circuit, and/or other devices that can provide the above-mentioned functions.
  • the first network element 120 may take the form of the communication device 300 shown in FIG. 3.
  • the processor 301 in the communication device 300 shown in FIG. 3 may invoke the computer execution instructions stored in the memory 303 to enable the communication device 300 to execute the network slice selection method in the foregoing method embodiment.
  • the functions/implementation process of the transceiver module 1201 and the processing module 1202 in FIG. 12 can be implemented by the processor 301 in the communication device 300 shown in FIG. 3 calling the computer execution instructions stored in the memory 303.
  • the function/implementation process of the processing module 1202 in FIG. 12 can be implemented by the processor 301 in the communication device 300 shown in FIG. 3 calling a computer execution instruction stored in the memory 303, and the function of the transceiver module 1201 in FIG. 12 /The realization process can be realized through the communication interface 304 in the communication device 300 shown in FIG. 3.
  • the first network element 120 provided in this embodiment can execute the above-mentioned network slice usage control method, the technical effects that can be obtained can refer to the above-mentioned method embodiment, and will not be repeated here.
  • one or more of the above modules or units can be implemented by software, hardware or a combination of both.
  • the software exists in the form of computer program instructions and is stored in the memory, and the processor can be used to execute the program instructions and implement the above method flow.
  • the processor can be built in SoC (system on chip) or ASIC, or it can be an independent semiconductor chip.
  • SoC system on chip
  • ASIC application specific integrated circuit
  • the processor's internal processing is used to execute software instructions to perform calculations or processing, and may further include necessary hardware accelerators, such as field programmable gate array (FPGA), PLD (programmable logic device) , Or a logic circuit that implements dedicated logic operations.
  • FPGA field programmable gate array
  • PLD programmable logic device
  • the hardware can be a CPU, a microprocessor, a digital signal processing (digital signal processing, DSP) chip, a microcontroller unit (MCU), an artificial intelligence processor, an ASIC, Any one or any combination of SoC, FPGA, PLD, dedicated digital circuit, hardware accelerator, or non-integrated discrete device can run necessary software or do not rely on software to perform the above method flow.
  • DSP digital signal processing
  • MCU microcontroller unit
  • an artificial intelligence processor an ASIC
  • Any one or any combination of SoC, FPGA, PLD, dedicated digital circuit, hardware accelerator, or non-integrated discrete device can run necessary software or do not rely on software to perform the above method flow.
  • an embodiment of the present application further provides a communication device (for example, the communication device may be a chip or a chip system), and the communication device includes a processor for implementing the method in any of the foregoing method embodiments.
  • the communication device further includes a memory.
  • the memory is used to store necessary program instructions and data, and the processor can call the program code stored in the memory to instruct the communication device to execute the method in any of the foregoing method embodiments.
  • the memory may not be in the communication device.
  • the communication device is a chip system, it may be composed of a chip, or may include a chip and other discrete devices, which is not specifically limited in the embodiment of the present application.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or may include one or more data storage devices such as servers and data centers that can be integrated with the medium.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).

Abstract

本申请实施例提供网络切片的使用控制方法、装置及系统，可以限制客户过量使用网络切片资源，同时保障网络切片的业务质量，提高网络资源的利用效率。方法包括：第一网元接收用于请求将终端设备接入到目标网络切片的第一消息，该目标网络切片覆盖包括第一区域的多个区域，该第一区域为终端设备当前所在的区域。进而，第一网元根据第一条件判断是否将该终端设备接入到该目标网络切片，第一条件包括：该目标网络切片在该第一区域内的业务使用量是否超过第一业务限额。可选的，该第一条件还包括该目标网络切片的整体业务使用量是否超过整体限额。本申请适用于通信技术领域。

Description

网络切片的使用控制方法、装置及系统
本申请要求于2019年11月06日提交国家知识产权局、申请号为201911078541.5、申请名称为“网络切片的使用控制方法、装置及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及网络切片的使用控制方法、装置及系统。
背景技术
网络切片(network slice)是一个用于支持特定网络能力与网络特性的逻辑隔离的网络，可以包括端到端(end to end，E2E)的整个网络，也可以部分网络功能在多个网络切片中共享，是满足第三代合作伙伴项目(3rd generation partnership project，3GPP)提出的第五代(5th generation，5G)移动通信技术关于网络差异化需求的关键技术。通常，不同网络切片的网络特征并不相同，且要求网络切片之间相互隔离，互不影响。如增强实现(augmented reality，AR)或虚拟实现(virtual reality，VR)业务的网络切片要求大带宽、低时延业务；物联网(internet of things，IOT)业务的网络切片要求支持海量终端接入，但带宽小，对时延没要求。
目前，客户订购网络切片后，网络运营商完成网络切片的创建和部署，然后在用户数据库(user data repository，UDR)网元中增加网络切片的控制数据，比如，网络切片的最大注册终端数，最大会话连接数。进而策略控制功能(policy control function，PCF)网元在注册管理流程中控制当前注册终端数量不超过网络切片的最大注册终端数，在会话管理流程中控制当前建立的会话连接数量不超过网络切片的最大会话连接数。
但是，终端设备具有可移动性。终端设备的可移动性可能造成网络切片内某个区域的终端设备非常密集或者网络切片内某个区域的终端设备非常稀疏。若网络切片内某个区域的终端设备非常密集，则容易导致无线侧网络节点拥塞，不仅不能很好保障本网络切片的业务质量，还可能影响其他网络切片的业务质量。
因此，如何限制客户过量使用网络切片资源，同时保障网络切片的业务质量，是目前亟待解决的问题。
发明内容
本申请实施例提供网络切片的使用控制方法、装置及系统，可以限制客户过量使用网络切片资源，同时保障网络切片的业务质量，提高网络资源的利用效率。为达到上述目的，本申请的实施例采用如下技术方案：
第一方面，提供了一种网络切片的使用控制方法，该方法包括：第一网元接收第一消息，该第一消息用于请求将终端设备接入到目标网络切片，其中，该目标网络切片覆盖多个区域，该多个区域包括第一区域，该第一区域为该终端设备当前所在的区域；第一网元根据第一条件判断是否将该终端设备接入到该目标网络切片，其中，第一条件包括：该目标网络切片在该第一区域内的业务使用量是否超过第一业务限额。由于本申请实施例中的目标网络切片覆盖多个区域，第一网元可以根据第一条件判断 是否将该终端设备接入到目标网络切片。第一条件包括：目标网络切片在第一区域内的业务使用量是否超过第一业务限额。换句话说，本申请实施例实现了网络切片接入的分区域控制，因此可以避免区域内无线侧网络节点拥塞或过载，不仅不能很好保障本网络切片的业务质量，还可能对其他网络切片的业务质量产生影响的问题，从而可以限制客户过量使用网络切片资源，同时保障网络切片的业务质量。
在一种可能的设计中，第一网元根据第一条件判断是否将该终端设备接入到该目标网络切片，包括：当该目标网络切片在该第一区域内的业务使用量达到或超过该第一业务限额时，第一网元拒绝该第一消息。
在一种可能的设计中，该第一条件还包括：该目标网络切片的整体业务使用量是否超过整体限额。
在一种可能的设计中，第一网元根据第一条件判断是否将该终端设备接入到该目标网络切片，包括：当该目标网络切片在该第一区域内的业务使用量不超过该第一业务限额，但是该目标网络切片的整体业务使用量达到或超过整体限额时，该第一网元拒绝该第一消息。
在一种可能的设计中，该方法还包括：第一网元接收来自第二网元的第二消息，该第二消息携带第一信息，该第一信息指示该目标网络切片的整体业务使用量达到或超过该整体限额。基于该方案，第一网元可以获知目标网络切片的整体业务使用量达到或超过该整体限额。
在一种可能的设计中，该第一信息为该第一区域内的业务使用量的配额为0，或者该第一信息为该目标网络切片的整体业务使用量达到或超过该目标网络切片的整体限额的指示。
在一种可能的设计中，该第一网元为移动管理网元，该第二网元为切片选择功能网元或者策略控制网元，该第一消息为注册请求。
在一种可能的设计中，该第一网元为移动管理网元，该第二网元为切片选择功能网元；该第一消息为会话建立请求。
在一种可能的设计中，该第一网元为会话管理网元，该第二网元为策略控制网元；该第一消息为会话建立请求。
在一种可能的设计中，该方法还包括：第一网元接收来自第三网元的第三消息，该第三消息携带该目标网络切片的整体业务使用量；第一网元确定该目标网络切片的整体业务使用量达到或超过该目标网络切片的整体限额。基于该方案，第一网元可以获知目标网络切片的整体业务使用量达到或超过该整体限额。
在一种可能的设计中，该第一网元为策略控制网元，该第三网元为统一数据管理网元；该第一消息为关联注册管理策略请求或者关联会话管理策略请求。
在一种可能的设计中，第一网元根据第一条件判断是否将该终端设备接入到该目标网络切片，包括：当该目标网络切片的整体业务使用量达到或超过该整体限额，但该目标网络切片在该第一区域内的业务使用量不超过该第一业务限额时，若满足第二条件，该第一网元允许该终端设备使用该目标网络切片。也就是说，考虑到若网络切片内某个区域的终端设备非常稀疏，则该区域可能有大量的空闲资源，但是因为整个网络切片的业务使用量超过指定限额，终端设备在这个区域也会被限制接入，造成这 个区域内的资源浪费。因此，本申请实施例中，当目标网络切片的整体业务使用量达到或超过整体限额，但目标网络切片在第一区域内的业务使用量不超过第一业务限额时，若满足第二条件，第一网元允许终端设备使用目标网络切片。换句话说，当目标网络切片的整体业务使用量达到或超过整体限额，但目标网络切片在第一区域内的业务使用量不超过第一业务限额时，在一定场景下可以允许用户在第一区域使用目标网络切片资源，因此可以提高网络资源的利用率，不仅能为运营商带来更多的经济收益，而且可以提高价值用户的业务体验。
在一种可能的设计中，该第一网元为策略控制网元，该第一消息为关联注册管理策略请求或者关联切片管理策略请求，该第二条件包括：该目标网络切片的切片签约信息中允许整体超限，或者该目标网络切片的计费方式为按会话或按流量计费，或者该目标网络切片签约的业务类型为特定业务类型，或者当请求接入的终端设备属于高价值客户，或者该目标网络切片的切片运行分析或预测结果显示低于特定门限，或者该请求接入的终端设备的移动行为分析预测结果指示该请求接入的终端设备的业务负荷低于特定门限。
在一种可能的设计中，该方法还包括：当该第一网元接收来自切片选择功能网元的关联切片管理策略请求时，该第一网元确定该目标网络切片在该第一区域内的业务使用量不超过该第一业务限额。基于该方案，第一网元可以获知该目标网络切片在该第一区域内的业务使用量不超过该第一业务限额。
在一种可能的设计中，该第一网元为策略控制网元，该第一消息为关联会话管理策略请求，该第二条件包括：该目标网络切片的切片签约信息中允许整体超限，或者该目标网络切片的计费方式为按会话或按流量计费，或者该目标网络切片签约的业务类型为特定业务类型，或者请求接入的终端设备属于高价值客户，或者该目标网络切片的整体会话数量和流量带宽低于过载风险门限，或者该终端设备签约的服务质量QoS参数指示该终端设备的业务允许被抢占，或者该目标网络切片的切片运行分析或预测结果显示低于特定门限，或者该请求接入的终端设备的移动或通信行为分析预测结果指示该请求接入的终端设备的业务负荷低于特定门限。
在一种可能的设计中，该方法还包括：当该第一网元接收来自会话管理网元的关联会话管理策略请求时，该第一网元确定该目标网络切片在该第一区域内的业务使用量不超过该第一业务限额。基于该方案，第一网元可以获知该目标网络切片在该第一区域内的业务使用量不超过该第一业务限额。
在一种可能的设计中，该第一网元为移动管理网元，该第一消息为注册请求，该第二条件包括：当切片选择功能网元指示该目标网络切片的整体业务使用量达到或超过该整体限额时，该切片选择功能网元指示的会话数量配额超过指定数量。
在一种可能的设计中，该方法还包括：当该第一网元接收来自该切片选择功能网元的该会话数量配额以及该目标网络切片的整体业务使用量达到或超过该目标网络切片的整体限额的指示时，该第一网元确定该目标网络切片的整体业务使用量达到或超过该整体限额。基于该方案，第一网元可以获知该目标网络切片在该第一区域内的业务使用量不超过该第一业务限额。
在一种可能的设计中，该第一网元为会话管理网元，该第一消息为会话建立请求， 该第二条件包括：当策略控制网元指示该目标网络切片的整体业务使用量达到或超过该整体限额时，该策略控制网元指示的该终端设备的业务QoS参数指示会话是可被抢占。
在一种可能的设计中，该方法还包括：当该第一网元接收来自该策略控制网元的该终端设备的业务QoS参数和该目标网络切片的整体业务使用量达到或超过该目标网络切片的整体限额的指示时，该第一网元确定该目标网络切片的整体业务使用量达到或超过该整体限额。基于该方案，第一网元可以获知该目标网络切片在该第一区域内的业务使用量不超过该第一业务限额。
在一种可能的设计中，该第一网元为移动管理网元，该第一消息为注册请求；或者，该第一网元为会话管理网元，该第一消息为会话建立请求；该第二条件包括：该目标网络切片在该第一区域内的运行负荷低于指定阈值；或者，该目标网络切片的整体运行负荷低于指定阈值，或者该目标网络切片在该第一区域的网络性能高于指定阈值。
在一种可能的设计中，当该第一消息为注册相关的消息时，该目标网络切片的整体业务使用量为该目标网络切片的实际整体注册终端数，该目标网络切片的整体限额为该目标网络切片整体允许的最大注册终端数。
在一种可能的设计中，当该第一消息为会话建立相关的消息时，该目标网络切片的整体业务使用量为该目标网络切片的实际整体并发会话数，该目标网络切片的整体限额为该目标网络切片整体允许的最大并发会话数。
在一种可能的设计中，当该第一消息为会话建立相关的消息时，该目标网络切片的整体业务使用量为该目标网络切片的实际整体流量带宽，该目标网络切片的整体限额为该目标网络切片整体允许的最大流量带宽。
在一种可能的设计中，当该第一消息为注册相关的消息时，该目标网络切片在该第一区域内的业务使用量包括该目标网络切片在该第一区域内的实际注册终端数，该第一业务限额包括该目标网络切片在该第一区域内允许的最大注册终端数。
在一种可能的设计中，当该第一消息为会话建立相关的消息时，该目标网络切片在该第一区域内的业务使用量包括该目标网络切片在该第一区域内的实际并发会话数，该第一业务限额包括该目标网络切片在该第一区域内允许的最大并发会话数。
在一种可能的设计中，当该第一消息为会话建立相关的消息时，该目标网络切片在该第一区域内的业务使用量包括该目标网络切片在该第一区域内的实际流量带宽，该第一业务限额包括该目标网络切片在该第一区域内允许的最大流量带宽。
第二方面，提供了一种通信装置用于实现上述各种方法。该通信装置可以为上述第一方面中的第一网元，或者包含上述第一网元的装置。所述通信装置包括实现上述方法相应的模块、单元、或手段(means)，该模块、单元、或means可以通过硬件实现，软件实现，或者通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块或单元。
第三方面，提供了一种通信装置，包括：处理器和存储器；该存储器用于存储计算机指令，当该处理器执行该指令时，以使该通信装置执行上述任一方面所述的方法。该通信装置可以为上述第一方面中的第一网元，或者包含上述第一网元的装置。
第四方面，提供了一种通信装置，包括：处理器；所述处理器用于与存储器耦合，并读取存储器中的指令之后，根据所述指令执行如上述任一方面所述的方法。该通信装置可以为上述第一方面中的第一网元，或者包含上述第一网元的装置。
第五方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述任一方面所述的方法。
第六方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述任一方面所述的方法。
第七方面，提供了一种通信装置(例如，该通信装置可以是芯片或芯片系统)，该通信装置包括处理器，用于实现上述任一方面中所涉及的功能。在一种可能的设计中，该通信装置还包括存储器，该存储器，用于保存必要的程序指令和数据。该通信装置是芯片系统时，可以由芯片构成，也可以包含芯片和其他分立器件。
其中，第二方面至第七方面中任一种设计方式所带来的技术效果可参见上述第一方面中不同设计方式所带来的技术效果，此处不再赘述。
第八方面，提供了一种通信系统，该通信系统包括第一网元以及与第一网元交互的网元。其中，该第一网元用于执行如上述第一方面所述的网络切片的使用控制方法。
其中，第八方面所带来的技术效果可参见上述第一方面所带来的技术效果，此处不再赘述。
附图说明
图1为本申请实施例提供的一种通信系统的结构示意图；
图2为图1所示的通信系统在5G网络中的应用示意图；
图3为本申请实施例提供的通信设备的结构示意图；
图4为本申请实施例提供的网络切片的使用控制方法流程示意图；
图5为本申请实施例提供的网络切片的使用控制方法交互流程示意图一；
图6为本申请实施例提供的网络切片的使用控制方法交互流程示意图二；
图7为本申请实施例提供的网络切片的使用控制方法交互流程示意图三；
图8为本申请实施例提供的网络切片的使用控制方法交互流程示意图四；
图9为本申请实施例提供的网络切片的使用控制方法交互流程示意图五；
图10为本申请实施例提供的网络切片的使用控制方法交互流程示意图六；
图11为本申请实施例提供的网络切片的使用控制方法交互流程示意图七；
图12为本申请实施例提供的第一网元的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。其中，在本申请的描述中，除非另有说明，“/”表示前后关联的对象是一种“或”的关系，例如，A/B可以表示A或B；本申请中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，其中A，B可以是单数或者复数。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b，或c中的至少一项(个)，可以表示：a，b，c，a-b，a-c，b-c，或a-b-c，其中a，b， c可以是单个，也可以是多个。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。同时，在本申请实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念，便于理解。
此外，本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
如图1所示，为本申请实施例提供的一种通信系统10。该通信系统10包括第一网元。该第一网元例如可以是移动管理网元、策略控制网元或者会话管理网元。
可选的，如图1所示，该通信系统10还可以包括接入网(radio access network，RAN)设备、切片选择功能网元、统一数据库网元、统一数据管理网元、网络数据分析功能网元、用户面网元、或者连接运营商网络的数据网络(data network，DN)中的一个或多个。其中，策略控制网元、网络切片选择网元或者统一数据管理网元等网元连接到服务总线上。终端设备可以通过RAN设备和用户面网元向DN发送业务数据，或者从DN接收业务数据。下面分别对上述设备或网元进行介绍。
可选的，本申请实施例中的终端设备，可以是用于实现无线通信功能的设备，例如终端或者可用于终端中的芯片等，其可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。其中，终端可以是5G网络或者未来演进的公共陆地移动网(public land mobile network，PLMN)中的用户设备(user equipment，UE)、接入终端、终端单元、终端站、移动站、移动台、远方站、远程终端、移动设备、无线通信设备、终端代理或终端装置等。接入终端可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备或可穿戴设备，虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。终端可以是移动的，也可以是固定的。
可选的，本申请实施例中的接入网设备，用于负责终端设备的无线侧接入，可能的部署形态包括：集中式单元(centralized unit，CU)和分布式单元(distributed unit，DU)的分离场景以及单站点场景。其中，在分离场景中，CU支持无线资源控制(radio resource control，RRC)、分组数据汇聚协议(packet data convergence protocol，PDCP)、 业务数据适配协议(service data adaptation protocol，SDAP)等协议；DU主要支持无线链路控制层(radio link control，RLC)、媒体接入控制层(media access control，
MAC)和物理层协议。在单站点场景中，单站点可以包括(new radio Node，gNB)、演进型节点B(evolved Node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station,BTS)、家庭基站、基带单元(base band unit，BBU)、传输点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)、移动交换中心等。
可选的，本申请实施例中的移动管理网元，主要用于移动网络中的终端设备的附着、移动性管理、跟踪区更新流程，移动管理网元终结了非接入层(non access stratum，NAS)消息、完成注册管理、连接管理以及可达性管理、分配跟踪区域列表(track area list，TA list)以及移动性管理等，并且透明路由会话管理(session management，SM)消息到会话管理网元。在5G通信系统中，移动管理网元可以是接入与移动性管理功能(access and mobility management function，AMF)网元。在未来通信如第六代(6th generation，6G)通信中，移动管理网元仍可以是AMF网元，或者有其它名称，本申请实施例对此不作限定。
可选的，本申请实施例中的会话管理网元，主要用于移动网络中的会话管理，如会话建立、修改、释放。具体功能如为用户分配互联网协议(internet protocol，IP)地址、选择提供报文转发功能的用户面网元等。在5G通信系统中，会话管理网元可以是会话管理功能(session management function，SMF)网元。在未来通信如6G中，会话管理网元仍可以是SMF网元，或有其它的名称，本申请实施例不做限定。
可选的，本申请实施例中的用户面网元，主要负责对用户报文进行处理，如转发、计费、合法监听等。用户面网元也可以称为协议数据单元(protocol data unit，PDU)会话锚点(PDU session anchor，PSA)。在5G通信系统中，用户面网元可以是用户面功能(user plane function，UPF)网元。在未来通信如6G中，用户面网元仍可以是UPF网元，或有其它的名称，本申请实施例不做限定。
可选的，本申请实施例中的切片选择功能网元，用于为终端设备选择网络切片等。在5G通信系统中，切片选择功能网元可以是网络切片选择功能(network slice selection function，NSSF)网元。在未来通信如6G通信中，网络切片选择功能网元仍可以是NSSF网元，或者有其它名称，本申请实施例对此不作限定。
可选的，本申请实施例中的策略控制网元，包含用户签约数据管理功能、策略控制功能、计费策略控制功能、服务质量(quality of service，QoS)控制等，用于指导网络行为的统一策略框架，为控制平面功能网元(例如AMF网元等)提供策略规则信息等。在5G通信系统中，策略控制网元可以是策略控制功能(policy control function，PCF)网元。在未来通信如6G通信中，策略控制功能网元仍可以是PCF网元，或者有其它名称，本申请实施例对此不作限定。
可选的，本申请实施例中的统一数据管理网元，用于负责终端设备的签约信息管理等。在5G通信系统中，统一数据管理网元可以是统一数据管理(unified data management，UDM)网元。在未来通信如6G通信中，统一数据管理网元仍可以是UDM 网元，或者有其它名称，本申请实施例对此不作限定。
可选的，本申请实施例中的统一数据库网元，用于存储和查询结构化数据。其中结构化数据是标准定义结构和语义的数据，各方可以根据标准理解数据所表征的含义。统一数据存储库网元可以由统一数据管理网元存储和查询签约数据，也可以由策略控制网元存储或查询策略数据，还可以由应用功能网元直接或通过网络开放功能网元存储和查询应用相关的数据。在5G通信系统中，统一数据存储库网元可以是统一数据存储库(unified data repository，UDR)网元。在未来通信如6G通信中，统一数据存储库网元仍可以是UDR网元，或者有其它名称，本申请实施例对此不作限定。
可选的，本申请实施例中的网络数据分析功能网元，可以从各个网络功能(network function，NF)，例如策略控制网元、会话管理网元、用户面网元、接入管理网元、应用功能网元(通过网络能力开放功能网元)收集数据，并进行分析和预测。在5G通信系统中，网络数据分析网元可以是网络数据分析功能(network data analytics function，NWDAF)网元。在未来通信如6G通信中，网络数据分析网元仍可以是NWDAF网元，或者有其它名称，本申请实施例对此不作限定。
可选的，本申请实施例中的数据网络，为终端提供数据传输服务，可以是公用数据网(public data network，PDN)网络，如因特网(internet)等。
以5G通信系统为例，如图2所示，为本申请实施例适用的一种可能的与图1所示的通信系统对应的网络架构示意图。其中，接入网设备所对应的网元或者实体可以为5G通信系统中的RAN设备(图5以RAN设备为gNB为例进行示意)，移动管理网元所对应的网元或者实体可以为5G通信系统中的AMF网元，会话管理网元所对应的网元或者实体可以为5G通信系统中的SMF网元，用户面网元所对应的网元或者实体可以为5G通信系统中的UPF网元，策略控制网元所对应的网元或者实体可以为5G通信系统中的PCF网元，切片选择功能网元所对应的网元或者实体可以为5G通信系统中的NSSF网元，统一数据库网元所对应的网元或者实体可以为5G通信系统中的UDR网元，统一数据管理网元所对应的网元或者实体可以为5G通信系统中的UDM网元，网络数据分析功能网元所对应的网元或者实体可以为5G通信系统中的NWDAF网元。其中，上述UDR网元，AMF网元，SMF网元和NSSF网元除了可以与5G通信系统中的网元通信之外，还可以与管理面的操作管理和运维(operation,administration and maintenance)实体通信(图2中仅是示例性的给出了UDR网元与OAM实体的连接关系)。
其中，NSSF网元、NWDAF网元、UDM网元、UDR网元、AMF网元等网元往往是多个网络切片共享的，SMF网元和UPF网元一般是属于特定网络切片的。无线接入侧的gNB也往往是多个网络切片共享的。根据第三代合作伙伴项目(3rd generation partnership project，3GPP)技术标准(technology standard，TS)23.541，gNB上可以为一个网络切片配置需要预留的最小资源占用比例和允许使用的最大资源占用比例。
一个网络切片可以覆盖多个区域。在图2所示的通信系统中，整个网络切片的服务区域分成了区域A、区域B、……、区域N，每个区域可以是一个或多个小区(cell)，也可以是一个或多个TA，还可以是AMF网元、SMF网元或UPF网元的服务区域。相应的，在网络切片的整个服务区域内可以有多个gNB(如图2中区域A中的gNB-A， 区域B中的gNB-B和区域N中的gNB-N)、多个AMF网元(如图2中区域A中的AMF-A网元和区域B中的AMF-B网元)或者多个UPF网元(如图2中的UPF网元、区域A中的UPF-A网元和区域B中的UPF-B网元)。每个gNB都有一定的覆盖区域，可以是一个或多个小区(cell)，每个小区有唯一的小区cell标识(identification，ID)。每个AMF网元也有可以服务的区域，可以是一个或多个跟踪区(tracking area，TA)。每个TA包含一个或多个小区，每个TA都对应一个跟踪区标识(tracking area identity，TAI)，每个小区都对应一个小区标识(cell ID)。另外，每个UPF网元也有可以服务的区域，尤其是有些部署在移动边缘计算(mobile edge computing，MEC)位置的UPF网元(如图2中的UPF网元)，服务区域的大小为一个或几个gNB覆盖的区域。
其中，网络切片的每个区域内都有一些区域性的受限网络资源，这些受限网络资源只能为本区域内的终端设备提供服务，无法为位于其它区域的终端设备提供服务，同时这些网络资源是有限的，成为了本区域最大网络服务能力的资源瓶颈。这些区域的受限网络资源可以是图2中的gNB，例如图2中的gNB-A；也可以是UPF网元，例如图2中的UPF-B网元。运营商在创建和部署网络切片时，首先会根据客户的需求，确定整个网络切片需要支持的终端密度(即所有区域需要支持的终端密度都相同)，或者确定各个区域需要支持的终端密度(即各个区域需要支持的终端密度可能不同)。然后，运营商根据区域需要支持的终端密度，确定网络切片的区域受限网络资源的数量。例如，多个网络切片共享的gNB是区域受限网络资源时，根据新部署的网络切片需要支持的注册终端密度和会话密度，确定本网络切片允许使用的最大无线资源或者占整个gNB无线资源的最大比例；如果新建网络切片内专用的UPF网元是区域受限网络资源时，根据新部署切片需要支持的会话密度、区域面积和每个终端的保障带宽，确定需要部署的UPF网元的资源数量，或者根据该区域内网络切片的数据业务流量总带宽，确定需要部署的UPF网元的资源数量。
可选的，本申请实施例中的第一网元也可以称之为通信装置，其可以是一个通用设备或者是一个专用设备，本申请实施例对此不作具体限定。
可选的，本申请实施例中的第一网元的相关功能可以由一个设备实现，也可以由多个设备共同实现，还可以是由一个设备内的一个或多个功能模块实现，本申请实施例对此不作具体限定。可以理解的是，上述功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行的软件功能，或者是硬件与软件的结合，或者是平台(例如，云平台)上实例化的虚拟化功能。
例如，本申请实施例中的第一网元的相关功能可以通过图3中的通信设备300来实现。图3所示为本申请实施例提供的通信设备300的结构示意图。该通信设备300包括一个或多个处理器301，通信线路302，以及至少一个通信接口(图3中仅是示例性的以包括通信接口304，以及一个处理器301为例进行说明)，可选的还可以包括存储器303。
处理器301可以是一个通用中央处理器(central processing unit，CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
通信线路302可包括一通路，用于连接不同组件之间。
通信接口304，可以是收发模块用于与其他设备或通信网络通信，如以太网，RAN，无线局域网(wireless local area networks，WLAN)等。例如，所述收发模块可以是收发器、收发机一类的装置。可选的，所述通信接口304也可以是位于处理器301内的收发电路，用以实现处理器的信号输入和信号输出。
存储器303可以是具有存储功能的装置。例如可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过通信线路302与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器303用于存储执行本申请方案的计算机执行指令，并由处理器301来控制执行。处理器301用于执行存储器303中存储的计算机执行指令，从而实现本申请实施例中提供的网络切片的使用控制方法。
或者，可选的，本申请实施例中，也可以是处理器301执行本申请下述实施例提供的网络切片的使用控制方法中的处理相关的功能，通信接口304负责与其他设备或通信网络通信，本申请实施例对此不作具体限定。
可选的，本申请实施例中的计算机执行指令也可以称之为应用程序代码，本申请实施例对此不作具体限定。
在具体实现中，作为一种实施例，处理器301可以包括一个或多个CPU，例如图3中的CPU0和CPU1。
在具体实现中，作为一种实施例，通信设备300可以包括多个处理器，例如图3中的处理器301和处理器308。这些处理器中的每一个可以是一个单核(single-core)处理器，也可以是一个多核(multi-core)处理器。这里的处理器可以包括但不限于以下至少一种：中央处理单元(central processing unit，CPU)、微处理器、数字信号处理器(DSP)、微控制器(microcontroller unit，MCU)、或人工智能处理器等各类运行软件的计算设备，每种计算设备可包括一个或多个用于执行软件指令以进行运算或处理的核。
在具体实现中，作为一种实施例，通信设备300还可以包括输出设备305和输入设备306。输出设备305和处理器301通信，可以以多种方式来显示信息。例如，输出设备305可以是液晶显示器(liquid crystal display，LCD)，发光二级管(light emitting diode，LED)显示设备，阴极射线管(cathode ray tube，CRT)显示设备，或投影仪(projector)等。输入设备306和处理器301通信，可以以多种方式接收用户的输入。例如，输入设备306可以是鼠标、键盘、触摸屏设备或传感设备等。
上述的通信设备300有时也可以称为通信装置，其可以是一个通用设备或者是一个专用设备。例如通信设备300可以是台式机、便携式电脑、网络服务器、掌上电脑(personal digital assistant，PDA)、移动手机、平板电脑、无线终端设备、嵌入式设 备、上述终端设备，上述网络设备、或具有图3中类似结构的设备。本申请实施例不限定通信设备300的类型。
如图4所示，为本申请实施例提供的一种网络切片的使用控制方法，该方法包括如下步骤：
S401、第一网元接收第一消息，第一消息用于请求将终端设备接入到目标网络切片，其中，目标网络切片覆盖多个区域，多个区域包括第一区域，第一区域为终端设备当前所在的区域。
S402、第一网元根据第一条件判断是否将该终端设备接入到目标网络切片，其中，第一条件包括：目标网络切片在第一区域内的业务使用量是否超过第一业务限额。
可选的，本申请实施例中，第一网元根据第一条件判断是否将终端设备接入到目标网络切片，可以包括：当目标网络切片在第一区域内的业务使用量达到(可以理解为等于，在此统一说明，以下不再赘述)或超过(可以理解为大于，在此统一说明，以下不再赘述)第一业务限额时，第一网元拒绝第一消息。当然，当目标网络切片在第一区域内的业务使用量达到第一业务限额时，对于这个分界点，第一网元也可以允许该终端设备使用目标网络切片，在此统一说明，以下不再赘述。
可选的，本申请实施例中，在终端设备的注册流程中，目标网络切片在第一区域内的业务使用量包括目标网络切片在第一区域内的实际注册终端数，第一业务限额包括目标网络切片在第一区域内允许的最大注册终端数。在终端设备的会话建立流程中，目标网络切片在第一区域内的业务使用量包括目标网络切片在第一区域内的实际并发会话数，第一业务限额包括目标网络切片在所述第一区域内允许的最大并发会话数；或者，目标网络切片在第一区域内的业务使用量包括目标网络切片在第一区域内的实际流量带宽，第一业务限额包括目标网络切片在第一区域内允许的最大流量带宽，在此统一说明，以下不再赘述。
可选的，本申请实施例中的第一条件还可以包括：目标网络切片的整体业务使用量是否超过整体限额。
一种可能的实现方式中，第一网元根据第一条件判断是否将终端设备接入到目标网络切片，可以包括：当目标网络切片在第一区域内的业务使用量不超过第一业务限额，但是目标网络切片的整体业务使用量达到或超过整体限额时，第一网元拒绝所述第一消息。其中，这里的不超过可以理解为小于或者理解为小于或者等于，该说明同样适用于下述其他实施例，在此统一说明，以下不再赘述。
另一种可能的实现方式中，第一网元根据第一条件判断是否将终端设备接入到目标网络切片，可以包括：当目标网络切片的整体业务使用量达到或超过整体限额，但目标网络切片在第一区域内的业务使用量不超过第一业务限额时，若满足第二条件，第一网元允许终端设备使用目标网络切片。其中，这里的第二条件可以理解为第一网元从OAM实体或其它网元获得的对网络运行信息或者用户信息的判定条件。
可选的，本申请实施例中，在终端设备的注册流程中，目标网络切片的整体业务使用量包括目标网络切片的实际整体注册终端数，目标网络切片的整体限额包括目标网络切片整体允许的最大注册终端数。在终端设备的会话建立流程中，目标网络切片的整体业务使用量包括目标网络切片的实际整体并发会话数，目标网络切片的整体限 额包括目标网络切片整体允许的最大并发会话数；或者，目标网络切片的整体业务使用量包括目标网络切片的实际整体流量带宽，目标网络切片的整体限额包括目标网络切片整体允许的最大流量带宽，在此统一说明，以下不再赘述。
上述方案的具体实现将在后面图5至图11任一所示的交互实施例中结合具体场景详细阐述，在此不予赘述。
由于本申请实施例中的目标网络切片覆盖多个区域，第一网元可以根据第一条件判断是否将该终端设备接入到目标网络切片。其中，一方面，第一条件包括：目标网络切片在第一区域内的业务使用量是否超过第一业务限额。换句话说，本申请实施例实现了网络切片接入的分区域控制，因此可以避免区域内无线侧网络节点拥塞或过载，不仅不能很好保障本网络切片的业务质量，还可能对其他网络切片的业务质量产生影响的问题，从而可以限制客户过量使用网络切片资源，同时保障网络切片的业务质量。另一方面，第一条件还可以包括：目标网络切片的整体业务使用量是否超过整体限额。进一步的，当目标网络切片的整体业务使用量达到或超过整体限额，但目标网络切片在第一区域内的业务使用量不超过第一业务限额时，若满足第二条件，第一网元允许终端设备使用目标网络切片。换句话说，当目标网络切片的整体业务使用量达到或超过整体限额，但目标网络切片在第一区域内的业务使用量不超过第一业务限额时，在一定场景下可以允许用户在第一区域使用目标网络切片资源，因此可以提高网络资源的利用率，不仅能为运营商带来更多的经济收益，而且可以提高价值用户的业务体验。
下面将结合图1至图4对本申请实施例提供的网络切片的使用控制方法进行具体阐述。
需要说明的是，本申请实施例并不限定于图2所示的5G网络架构，还可以应用于未来其它的通信系统，例如6G网络架构等。并且，本申请实施例所使用的各个网元的名称，在未来通信系统中，可能保持功能相同，但名称会改变。
需要说明的是，本申请下述实施例中各个网元之间的消息名字或消息中各参数的名字等只是一个示例，具体实现中也可以是其他的名字，本申请实施例对此不作具体限定。
首先，以图1所示的通信系统中的第一网元为移动管理网元，图1所示的通信系统应用于如图2所示的5G网络架构，第一区域为图2中的区域A为例，如图5所示，为本申请实施例提供的一种网络切片的使用控制方法，包括如下步骤：
S501、OAM实体向NSSF网元发送目标网络切片的整体限额。相应的，NSSF网元接收来自OAM实体的目标网络切片的整体限额。
其中，目标网络切片的整体限额的相关描述可参考图4所示的实施例，在此不再赘述。
S502、OAM实体向目标网络切片覆盖的各个区域的AMF网元发送目标网络切片在各个区域内的业务限额相关信息。相应的，目标网络切片覆盖的各个区域的AMF网元接收来自OAM实体的目标网络切片在各个区域内的业务限额相关信息。其中，图5仅是示例性的以OAM实体向目标网络切片覆盖的第一区域(即区域A)的AMF-A网元发送目标网络切片在第一区域内的第一业务限额相关信息为例进行说明；相应的，AMF-A网元接收来自OAM实体的目标网络切片在第一区域内的第一业务限额相关信 息。
可选的，本申请实施例中的第一业务限额相关信息包括第一业务限额或者用于确定第一业务限额的信息。其中，第一业务限额的相关描述可参考图4所示的实施例，在此不再赘述。
示例性的，本申请实施例中，用于确定目标网络切片在第一区域内允许的最大注册终端数的信息例如可以包括目标网络切片支持的终端密度。其中，根据目标网络切片支持的终端密度和第一区域的面积(可以预先配置到相应的AMF网元上)，可以确定目标网络切片在第一区域内允许的最大注册终端数。需要说明的是，本申请实施例中，OAM实体向目标网络切片覆盖的各个区域的AMF网元配置的目标网络切片支持的终端密度可以相同，也可以不相同，本申请实施例对此不做具体限定。
示例性的，本申请实施例中，用于确定第一区域内允许的最大并发会话数的信息例如可以包括目标网络切片支持的并发会话密度。其中，根据目标网络切片支持的并发会话密度和第一区域的面积(可以预先配置到相应的AMF网元上)，可以确定目标网络切片在第一区域内允许的最大并发会话数。需要说明的是，本申请实施例中，OAM实体向目标网络切片覆盖的各个区域的AMF网元配置的目标网络切片支持的并发会话密度可以相同，也可以不相同，本申请实施例对此不做具体限定。
示例性的，本申请实施例中，用于确定第一区域内允许的最大流量带宽的信息例如可以包括目标网络切片支持的流量密度。其中，根据目标网络切片支持的流量密度和第一区域的面积(可以预先配置到相应的SMF网元上)，可以确定目标网络切片在第一区域内允许的最大流量带宽。需要说明的是，本申请实施例中，OAM实体向目标网络切片覆盖的各个区域的SMF网元配置的目标网络切片支持的流量密度可以相同，也可以不相同，本申请实施例对此不做具体限定。
需要说明的是，本申请实施例中的步骤S501和步骤S502之间没有必然的执行先后顺序，可以是先执行步骤S501，再执行步骤S502；也可以是先执行步骤S502，再执行步骤S501；还可以是同时执行步骤S501和步骤S502，本申请实施例对此不做具体限定。
S503、终端设备在AMF-A网元的服务区域内通过gNB-A向AMF-A网元发送消息a1。相应的，AMF-A网元接收来自终端设备的消息a1。
其中，消息a1携带终端设备请求的网络切片选择辅助信息(network slice selection assistance information，NSSAI)(即request NSSAI)。request NSSAI包括终端设备希望注册接入的一个或多个网络切片的单NSSAI(single NSSAI，S-NSSAI)。
此外，消息a1还可以携带终端设备当前所在的TA的标识和/或小区cell的标识，本申请实施例对此不作具体限定。
示例性的，本申请实施例中的消息a1例如可以为如图5所示的注册请求(registration request)消息，本申请实施例对此不作具体限定。
S504、AMF-A网元确定目标网络切片在第一区域内的业务使用量是否超过第一业务限额。
其中，AMF-A网元可以根据终端设备当前所在的TA的标识和/或小区cell的标识，确定终端设备当前所在的区域(即本申请实施例中的第一区域)。
其中，AMF-A网元可以根据request NSSAI携带的每一个S-NSSAI，确定终端设备希望注册接入的目标网络切片。示例性的，如果终端设备没有某个S-NSSAI对应的网络切片签约信息，AMF-A网元就会拒绝终端设备注册到该S-NSSAI对应的网络切片，如果终端设备有某个S-NSSAI对应的网络切片签约信息，则可以将该S-NSSAI对应的网络切片作为目标网络切片。
本申请实施例中，在终端设备的注册流程中，目标网络切片在第一区域内的业务使用量包括目标网络切片在第一区域内的实际注册终端数。AMF-A网元在注册管理过程中会维护当前服务的各个网络切片在该AMF-A网元管理的各个区域内的实际注册终端数，这其中包括目标网络切片在第一区域内的实际注册终端数。进而，AMF-A网元可以将目标网络切片在第一区域内的实际注册终端数与步骤S502中确定的目标网络切片在第一区域内允许的最大注册终端数进行比较。当目标网络切片在第一区域内的实际注册终端数达到或超过目标网络切片在第一区域内允许的最大注册终端数时，则执行下述步骤S505对应的分支一；当目标网络切片在第一区域内的实际注册终端数不超过目标网络切片在第一区域内允许的最大注册终端数时，则执行下述步骤S508以及之后的步骤对应的分支二。其中，当目标网络切片在第一区域内的实际注册终端数等于(即上述的达到)目标网络切片在第一区域内允许的最大注册终端数时，对于该分界点，可以继续执行下述步骤S505对应的分支一或者继续执行下述步骤S508以及之后的步骤对应的分支二，本申请实施例对此不做具体限定。
分支一：
S505、AMF-A网元通过gNB-A向终端设备发送消息b1。相应的，终端设备接收来自AMF-A网元的消息b1。
其中，该消息b1中携带目标网络切片的S-NSSAI，用于临时拒绝终端设备在当前位置注册到目标网络切片，允许终端设备在改变位置区域或等待一段时间后，继续尝试请求注册到该目标网络切片。
示例性的，本申请实施例中的消息b1例如可以为如图5所示的注册拒绝(registration reject)消息，本申请实施例对此不作具体限定。
可选的，本申请实施例中，当目标网络切片在第一区域内的实际注册终端数达到或超过目标网络切片在第一区域内允许的最大注册终端数时，还可以执行下述步骤S506-S507：
S506、AMF-A网元向gNB-A发送指示信息。相应的，gNB-A接收来自AMF-A网元的指示信息。
其中，该指示信息用于指示gNB-A为目标网络切片对应的接入类别(access class，AC)设置接入类别拦截(access class barring，ACB)；或者，该指示信息用于指示gNB-A向位于本区域的终端设备广播明确拥塞通知(explicit congestion notification，ECN)，以通知本区域的终端设备目标网络切片发生了拥塞。
S507、gNB-A根据指示信息，向本区域的终端设备发送ECN或ACB，以防止本区域的终端设备继续尝试接入目标网络切片(图5中示例性的以gNB-A与当前尝试接入的终端设备的交互为例进行示意)。
分支二：
S508、AMF-A网元会定期或在第一区域内的业务使用量的配额使用完毕(或即将完毕)时，或在没有目标网络切片的S-NSSAI的切片选择结果的有效缓存时，向NSSF网元发送消息c1。NSSF网元接收来自AMF-A网元的消息c1。
其中，消息c1中携带目标网络切片在第一区域内的实际注册终端数。可选的，该消息c1还可以携带目标网络切片在第一区域内的实际并发会话数。
示例性的，本申请实施例中的消息c1例如可以为如图5所示的切片选择请求消息，本申请实施例对此不作具体限定。
类似的，目标网络切片覆盖的其他区域的AMF网元(如图2中区域B中的AMF-B网元)也可以向NSSF网元上报目标网络切片在其他区域内的实际注册终端数。可选的，目标网络切片覆盖的其他区域的AMF网元(如图2中区域B中的AMF-B网元)也可以向NSSF网元上报目标网络切片在其他区域内的实际并发会话数。
S509、NSSF网元确定目标网络切片的整体业务使用量是否超过整体限额。
本申请实施例中，在终端设备的注册流程中，目标网络切片的整体业务使用量包括目标网络切片的实际整体注册终端数。NSSF网元在获得目标网络切片覆盖的各个区域的AMF网元上报的目标网络切片在各个区域内的实际注册终端数之后，可以将目标网络切片在各个区域内的实际注册终端数累加求和，进而将求和结果与步骤S501中获取的目标网络切片整体允许的最大注册终端数进行比较。当目标网络切片的实际整体注册终端数达到或超过目标网络切片整体允许的最大注册终端数时，可以将目标网络切片覆盖的各个区域的注册终端数的配额设置为0；当目标网络切片的实际整体注册终端数不超过目标网络切片整体允许的最大注册终端数时，可以将整体剩余的注册终端数(或者整体剩余的注册终端数中的一部分)按照各个区域实际注册终端数的比例进行分配，作为各个区域的注册终端数的配额。
本申请实施例中，在终端设备的会话建立流程中，目标网络切片的整体业务使用量包括目标网络切片的实际并发会话数。NSSF网元在获得目标网络切片覆盖的各个区域的AMF网元上报的目标网络切片在各个区域内的实际并发会话数之后，可以将目标网络切片在各个区域内的实际并发会话数累加求和，进而将求和结果与步骤S501中获取的目标网络切片整体允许的最大并发会话数进行比较。当目标网络切片的实际整体并发会话数达到或超过目标网络切片整体允许的最大并发会话数时，可以将目标网络切片覆盖的各个区域的并发会话数的配额设置为0；当目标网络切片的实际整体并发会话数不超过目标网络切片整体允许的最大并发会话数时，可以将整体剩余的并发会话数(或者整体剩余的并发会话数中的一部分)按照各个区域实际并发会话数的比例进行分配，作为各个区域的并发会话数的配额。
S510、NSSF网元向AMF-A网元发送消息d1。相应的，AMF-A网元接收来自NSSF网元的消息d1。
其中，消息d1携带第一区域内的业务使用量的配额。第一区域内的业务使用量的配额例如可以包括第一区域内的注册终端数的配额。可选的，第一区域内的业务使用量的配额例如还可以包括第一区域内的并发会话数的配额。
可选的，本申请实施例中，AMF-A网元获取到第一区域内的注册终端数的配额之后，可以将第一区域内的注册终端数的配额缓存到本地，后续每次一个新的终端设备 在第一区域注册到目标网络切片后，就会从缓存中第一区域内的注册终端数的配额中扣除1。当终端设备从目标网络切片注销或移动出第一区域时，可以恢复缓存中第一区域内的注册终端数的配额(即配额加1)。当缓存中第一区域内的注册终端数的配额用尽或即将用尽时，AMF-A网元可以再通过消息c1向NSSF网元请求新的第一区域内的注册终端数的配额。
示例性的，本申请实施例中的消息d1例如可以为如图5所示的切片选择响应消息，本申请实施例对此不作具体限定。
其中，当第一区域内的注册终端数的配额为0时，AMF-A网元可以确定目标网络切片的实际整体注册终端数达到或超过目标网络切片整体允许的最大注册终端数，进而执行下述步骤S511-S513对应的分支a；当第一区域内的注册终端数的配额不为0时，AMF-A网元可以确定目标网络切片的实际整体注册终端数不超过目标网络切片整体允许的最大注册终端数，进而则执行下述步骤S514对应的分支b。
可选的，本申请实施例中，当第一区域内的注册终端数的配额为0时，上述消息d1中也可以不携带第一区域内的注册终端数的配额，而是携带目标网络切片的实际整体注册终端数达到或超过目标网络切片整体允许的最大注册终端数的指示，本申请实施例对此不作具体限定。
分支a：
S511-S513、同上述步骤S505-S507，在此不再赘述。
分支b：
S514、AMF-A网元通过gNB-A向终端设备发送消息e1。相应的，终端设备接收来自AMF-A网元的消息e1。
其中，消息e1携带允许的NSSAI(allowed NSSAI)，允许的NSSAI中包括目标网络切片的S-NSSAI。
示例性的，本申请实施例中的消息e1例如可以为如图5所示的注册接受(registration accept)消息，本申请实施例对此不作具体限定。
其中，本申请实施例中，终端设备成功注册之后，AMF-A网元刷新维护的目标网络切片在第一区域的注册终端数，对缓存中第一区域内的注册终端数的配额进行扣减。当终端设备从目标网络切片注销或移动出第一区域时，可以恢复缓存中第一区域内的注册终端数的配额(即配额加1)。
需要说明的是，本申请实施例中，若上述步骤S504中确定的目标网络切片为多个，或者终端设备不发送request NSSAI，但是签约的默认网络切片有多个(此时每个默认的网络切片均可以作为目标网络切片)时，对于每个目标网络切片，均可以按照上述步骤S504-S514的方式分别进行处理，在此不再一一赘述。
进一步的，在终端设备注册成功之后，本申请实施例提供的网络切片的使用控制方法还包括如下述步骤S515-S517或者如下步骤S515-S518所示的会话建立流程：
S515、终端设备通过gNB-A向AMF-A网元发送消息f1。相应的，AMF-A网元接收来自终端设备的消息f1。
其中，消息f1携带目标网络切片的S-NSSAI。
示例性的，本申请实施例中的消息f1例如可以为如图5所示的会话建立请求消息， 本申请实施例对此不作具体限定。
S516、AMF-A网元确定目标网络切片在第一区域内的业务使用量是否超过第一业务限额。
其中，AMF-A网元可以根据终端设备当前所在的TA的标识和/或小区cell的标识，确定终端设备当前所在的区域(即本申请实施例中的第一区域)。
其中，AMF-A网元可以根据目标网络切片的S-NSSAI，确定终端设备希望会话接入的目标网络切片。
本申请实施例中，在终端设备的会话建立流程中，目标网络切片在第一区域内的业务使用量包括目标网络切片在第一区域内的实际并发会话数。AMF-A网元在会话管理过程中会维护当前服务的各个网络切片在该AMF-A网元管理的各个区域内的实际并发会话数，这其中包括目标网络切片在第一区域内的实际并发会话数。进而，AMF-A网元可以将目标网络切片在第一区域内的实际并发会话数与步骤S502中确定的目标网络切片在第一区域内允许的最大并发会话数进行比较。当目标网络切片在第一区域内的实际并发会话数达到或超过目标网络切片在第一区域内允许的最大并发会话数时，则执行下述步骤S517对应的分支i；当目标网络切片在第一区域内的实际并发会话数不超过目标网络切片在第一区域内允许的最大并发会话数时，则AMF-A网元进一步确定目标网络切片的实际整体并发会话数是否超过目标网络切片整体允许的最大并发会话数，当AMF-A网元确定目标网络切片的实际整体并发会话数达到或超过目标网络切片整体允许的最大并发会话数时，进而执行下述步骤S517对应的分支i；当AMF-A网元确定目标网络切片的实际整体并发会话数不超过目标网络切片整体允许的最大并发会话数时，进而则执行下述步骤S518对应的分支ii。其中，当目标网络切片在第一区域内的实际并发会话数等于(即上述的达到)目标网络切片在第一区域内允许的最大并发会话数时，对于该分界点，可以继续执行下述步骤S517对应的分支i，也可以进一步确定目标网络切片的实际整体并发会话数是否超过目标网络切片整体允许的最大并发会话数。当目标网络切片的实际整体并发会话数等于(即上述的达到)目标网络切片整体允许的最大并发会话数时，对于该分界点，可以继续执行下述步骤S517对应的分支i或者继续执行下述步骤S518对应的分支ii，本申请实施例对此不做具体限定。
可选的，本申请实施例中，在上述步骤S510中，AMF-A网元获取到第一区域内的并发会话数的配额之后，可以将第一区域内的并发会话数的配额缓存到本地，后续每次在第一区域成功建立一个新的会话后，就会从缓存中第一区域内的并发会话数的配额中扣除1。当会话释放或会话因为终端设备的移动切换出第一区域时，可以恢复缓存中第一区域内的会话并发数的配额(即配额加1)。当缓存中第一区域内的并发会话数的配额用尽或即将用尽时，AMF-A网元可以再通过消息c1向NSSF网元请求新的第一区域内的并发会话数的配额。
其中，当第一区域内的并发会话数的配额为0时，AMF-A网元可以确定目标网络切片的实际整体并发会话数达到或超过目标网络切片整体允许的最大并发会话数；当第一区域内的并发会话数的配额不为0时，AMF-A网元可以确定目标网络切片的实际整体并发会话数不超过目标网络切片整体允许的最大并发会话数。
需要说明的是，本申请实施例中，若通过上述步骤S509和步骤S510，AMF-A网元未获取到第一区域内的并发会话数的配额，则在终端设备的会话建立过程中，AMF-A网元可以通过上述步骤S509和步骤S510的方式获取第一区域内的并发会话数的配额，本申请实施例对此不作具体限定。
可选的，本申请实施例中，当第一区域内的并发会话数的配额为0时，上述消息d1中也可以不携带第一区域内的并发会话数的配额，而是携带目标网络切片的实际整体并发会话数达到或超过目标网络切片整体允许的最大并发会话数的指示，本申请实施例对此不作具体限定。
分支i：
S517、AMF-A网元通过gNB-A向终端设备发送消息g1。相应的，终端设备接收来自AMF-A网元的消息g1。
其中，该消息g1中携带目标网络切片的过载指示，用于临时拒绝终端设备在当前位置在目标网络切片建立会话，允许终端设备在改变位置区域或等待一段时间后，继续尝试请求再该目标网络切片建立会话。
示例性的，本申请实施例中的消息g1例如可以为如图5所示的会话建立拒绝消息，本申请实施例对此不作具体限定。
分支ii：
S518、AMF-A网元允许终端设备在第一区域在目标网络切片建立会话，继续后续的会话建立处理流程。
其中，本申请实施例中，终端设备成功建立会话之后，AMF-A网元刷新维护的目标网络切片在第一区域的并发会话数量，对缓存中第一区域内的并发会话数的配额进行扣减。当会话释放或会话因为终端设备的移动切换出第一区域时，可以恢复缓存中第一区域内的会话并发数的配额(即配额加1)。
由于本申请实施例中的目标网络切片覆盖多个区域，第一网元可以根据第一条件判断是否将该终端设备接入到目标网络切片。第一条件包括：目标网络切片在第一区域内的业务使用量是否超过第一业务限额。换句话说，本申请实施例实现了网络切片接入的分区域控制，因此可以避免区域内无线侧网络节点拥塞或过载，不仅不能很好保障本网络切片的业务质量，还可能对其他网络切片的业务质量产生影响的问题，从而可以限制客户过量使用网络切片资源，同时保障网络切片的业务质量。
其中，上述步骤S501至步骤S517或者步骤S518中的AMF-A网元的动作可以由图3所示的通信设备300中的处理器301调用存储器303中存储的应用程序代码来执行，本实施例对此不作任何限制。
可选的，以图1所示的通信系统中的第一网元为移动管理网元或者会话管理网元，图1所示的通信系统应用于如图2所示的5G网络架构，第一区域为图2中的区域A为例，如图6所示，为本申请实施例提供的另一种网络切片的使用控制方法，包括如下步骤：
S601、OAM实体向UDR网元发送目标网络切片的整体限额。相应的，UDR网元接收来自OAM实体的目标网络切片的整体限额。
其中，目标网络切片的整体限额的相关描述可参考图4所示的实施例，在此不再 赘述。
S602、OAM实体向目标网络切片覆盖的各个区域的AMF网元发送目标网络切片在各个区域内的业务限额相关信息。相应的，目标网络切片覆盖的各个区域的AMF网元接收来自OAM实体的目标网络切片在各个区域内的业务限额相关信息。其中，图6仅是示例性的以OAM实体向目标网络切片覆盖的第一区域(即区域A)的AMF-A网元发送目标网络切片在第一区域内的第一业务限额相关信息为例进行说明；相应的，AMF-A网元接收来自OAM实体的目标网络切片在第一区域内的第一业务限额相关信息。
可选的，步骤S602中的第一业务限额相关信息包括终端设备的注册流程中所需的第一业务限额或者用于确定该第一业务限额的信息。其中，终端设备的注册流程中所需的第一业务限额或者用于确定该第一业务限额的信息的相关描述可参考图5所示的实施例中的步骤S502，在此不再赘述。
S603、OAM实体向目标网络切片覆盖的各个区域的SMF网元发送目标网络切片在各个区域内的业务限额相关信息。相应的，目标网络切片覆盖的各个区域的SMF网元接收来自OAM实体的目标网络切片在各个区域内的业务限额相关信息。其中，图6仅是示例性的以OAM实体向目标网络切片覆盖的第一区域(即区域A)的SMF网元发送目标网络切片在第一区域内的第一业务限额相关信息为例进行说明；相应的，SMF网元接收来自OAM实体的目标网络切片在第一区域内的第一业务限额相关信息。
可选的，步骤S603中的第一业务限额相关信息包括终端设备的会话建立流程中所需的第一业务限额或者用于确定该第一业务限额的信息。其中，终端设备的会话建立流程中所需的第一业务限额或者用于确定该第一业务限额的信息的相关描述可参考图5所示的实施例中的步骤S502，在此不再赘述。
需要说明的是，本申请实施例中的步骤S601、步骤S602和步骤S603之间没有必然的执行先后顺序，可以是先执行其中的任意一个步骤，再分别执行剩余的两个步骤；也可以是先同时执行其中的两个步骤，再执行剩余的一个步骤；还可以是先执行其中的一个步骤，再同时执行剩余的两个步骤；还可以是同时执行这三个步骤，本申请实施例对此不做具体限定。
S604、同图5所示的实施例中的步骤S503，相关描述可参考图5所示的实施例，在此不再赘述。
S605、AMF-A网元确定目标网络切片在第一区域内的业务使用量是否超过第一业务限额。
其中，AMF-A网元确定终端设备当前所在的区域(即本申请实施例中的第一区域)和目标网络切片的方式可参考图5所示的实施例中的步骤S504，在此不再赘述。
本申请实施例中，在终端设备的注册流程中，目标网络切片在第一区域内的业务使用量包括目标网络切片在第一区域内的实际注册终端数。AMF-A网元在注册管理过程中会维护当前服务的各个网络切片在该AMF-A网元管理的各个区域内的实际注册终端数，这其中包括目标网络切片在第一区域内的实际注册终端数。进而，AMF-A网元可以将目标网络切片在第一区域内的实际注册终端数与步骤S602中确定的目标网络切片在第一区域内允许的最大注册终端数进行比较。当目标网络切片在第一区域内 的实际注册终端数达到或超过目标网络切片在第一区域内允许的最大注册终端数时，则执行下述步骤S606对应的分支一；当目标网络切片在第一区域内的实际注册终端数不超过目标网络切片在第一区域内允许的最大注册终端数时，则执行下述步骤S609以及之后的步骤对应的分支二。其中，当目标网络切片在第一区域内的实际注册终端数等于(即上述的达到)目标网络切片在第一区域内允许的最大注册终端数时，对于该分界点，可以继续执行下述步骤S606对应的分支一或者继续执行下述步骤S609以及之后的步骤对应的分支二，本申请实施例对此不做具体限定。
分支一：
S606、同图5所示的实施例中的步骤S505，相关描述可参考图5所示的实施例，在此不再赘述。
可选的，本申请实施例中，当目标网络切片在第一区域内的实际注册终端数达到或超过目标网络切片在第一区域内允许的最大注册终端数时，还可以执行下述步骤S607-S608：
S607-S608、同图5所示的实施例中的步骤S506-S507，相关描述可参考图5所示的实施例，在此不再赘述。
分支二：
S609、AMF-A网元向PCF网元发送消息h1。相应的，PCF网元接收来自AMF-A网元的消息h1。
其中，消息h1中携带目标网络切片的S-NSSAI。
示例性的，本申请实施例中的消息h1例如可以为如图6所示的关联注册管理策略请求，本申请实施例对此不作具体限定。
S610、PCF网元从UDR网元获取目标网络切片的整体业务使用量以及目标网络切片的整体限额。
其中，在终端设备的注册流程中，目标网络切片的整体业务使用量为目标网络切片的实际整体注册终端数，相应的，目标网络切片的整体限额为目标网络切片整体允许的最大注册终端数。
需要说明的是，本申请实施例中，如果目标网络切片有多个PCF网元，那么这些PCF网元都在统一使用UDR网元维护目标网络切片的整体业务使用量。
S611、PCF网元确定目标网络切片的整体业务使用量是否超过目标网络切片的整体限额。
S612、PCF网元向AMF-A网元发送消息j1。相应的，AMF-A接收来自PCF网元的消息j1。
示例性的，本申请实施例中的消息j1例如可以为如图6所示的关联注册管理策略响应，本申请实施例对此不作具体限定。
其中，当目标网络切片的整体业务使用量达到或超过目标网络切片的整体限额时，上述消息j1中可以携带目标网络切片的整体业务使用量达到或超过目标网络切片的整体限额的指示或者不允许终端设备使用目标网络切片的指示，进而可以执行下述步骤S613对应的分支a；当目标网络切片的整体业务使用量不超过目标网络切片的整体限额时，上述消息j1中可以携带允许终端设备使用目标网络切片的指示，进而可以执行 下述步骤S616对应的分支b。其中，当目标网络切片的整体业务使用量等于(即上述的达到)目标网络切片的整体限额，对于该分界点，可以继续执行下述步骤S613对应的分支a或者继续执行下述步骤S616对应的分支b，本申请实施例对此不做具体限定。
分支a：
S613、同图5所示的实施例中的步骤S505，相关描述可参考图5所示的实施例，在此不再赘述。
可选的，本申请实施例中，当目标网络切片的实际整体注册终端数达到或超过目标网络切片整体允许的最大注册终端数时，还可以执行下述步骤S613-S614：
S614-S615、同图5所示的实施例中的步骤S506-S507，相关描述可参考图5所示的实施例，在此不再赘述。
分支b：
S616、同图5所示的实施例中的步骤S514，相关描述可参考图5所示的实施例，在此不再赘述。
进一步的，在终端设备注册成功之后，PCF网元还可以向UDR网元更新目标网络切片的实际整体注册终端数。后续当终端设备从目标网络切片注销或移动出第一区域时，PCF网元还可以向UDR网元更新目标网络切片的实际整体注册终端数，本申请实施例对此不作具体限定。
需要说明的是，本申请实施例中，若上述步骤S605中确定的目标网络切片为多个，或者终端设备不发送request NSSAI，但是签约的默认网络切片有多个(此时每个默认的网络切片均可以作为目标网络切片)时，对于每个目标网络切片，均可以按照上述步骤S605-S616的方式分别进行处理，在此不再一一赘述。
进一步的，在终端设备注册成功之后，本申请实施例提供的网络切片的使用控制方法还包括如下述步骤S617-S624或者如下步骤S617-S625所示的会话建立流程：
S617、终端设备通过AMF-A网元向SMF网元发送消息k1。相应的，SMF网元接收来自终端设备的消息k1。
其中，消息k1携带目标网络切片的S-NSSAI。
示例性的，本申请实施例中的消息k1例如可以为如图6所示的会话建立请求消息，本申请实施例对此不作具体限定。
S618、SMF网元确定目标网络切片在第一区域内的业务使用量是否超过第一业务限额。
其中，SMF网元可以根据终端设备当前所在的TA的标识和/或小区cell的标识，确定终端设备当前所在的区域(即本申请实施例中的第一区域)。
其中，SMF网元可以根据目标网络切片的S-NSSAI，确定终端设备希望会话接入的目标网络切片。
其中，步骤S618中的目标网络切片在第一区域内的业务使用量以及第一业务限额为终端设备的会话建立流程中对应的目标网络切片在第一区域内的业务使用量以及第一业务限额。SMF网元在会话管理过程中会维护当前服务的各个网络切片在该SMF网元管理的各个区域内的业务使用量，这其中包括目标网络切片在第一区域内的业务使用量。进而，SMF网元可以将目标网络切片在第一区域内的业务使用量与步骤S603 中确定的第一业务限额进行比较。当目标网络切片在第一区域内的业务使用量达到或超过第一业务限额时，则执行下述步骤S619对应的分支三；当目标网络切片在第一区域内的业务使用量不超过第一业务限额时，则执行下述步骤S620以及之后的步骤对应的分支四：
分支三：
S619、同图5所示的实施例中的步骤S517，相关描述可参考图5所示的实施例，在此不再赘述。
分支四：
S620、SMF网元向PCF网元发送消息m1。相应的，PCF网元接收来自SMF网元的消息m1。
其中，消息m1中携带目标网络切片的S-NSSAI。
示例性的，本申请实施例中的消息m1例如可以为如图6所示的关联会话管理策略请求，本申请实施例对此不作具体限定。
S621、PCF网元从UDR网元获取目标网络切片的整体业务使用量以及目标网络切片的整体限额。
其中，在终端设备的会话建立流程中，目标网络切片的整体业务使用量以及目标网络切片的整体限额的相关描述可参考图4所示的实施例，在此不再赘述。
需要说明的是，本申请实施例中，如果目标网络切片有多个PCF网元，那么这些PCF网元都在统一使用UDR网元维护目标网络切片的整体业务使用量。
S622、PCF网元确定目标网络切片的整体业务使用量是否超过目标网络切片的整体限额。
S623、PCF网元向SMF网元发送消息n1。相应的，SMF网元接收来自PCF网元的消息n1。
示例性的，本申请实施例中的消息n1例如可以为如图6所示的关联会话管理策略响应，本申请实施例对此不作具体限定。
其中，当目标网络切片的整体业务使用量达到或超过目标网络切片的整体限额时，上述消息n1中可以携带目标网络切片的整体业务使用量达到或超过目标网络切片的整体限额的指示或者不允许终端设备使用目标网络切片的指示，进而可以执行下述步骤S624对应的分支i；当目标网络切片的整体业务使用量不超过目标网络切片的整体限额时，上述消息n1中可以携带允许终端设备使用目标网络切片的指示，进而可以执行下述步骤S625对应的分支ii。其中，当目标网络切片的整体业务使用量等于(即上述的达到)目标网络切片的整体限额时，对于该分界点，可以继续执行下述步骤S24对应的分支i或者继续执行下述步骤S625对应的分支ii，本申请实施例对此不做具体限定。
分支i：
S624、SMF网元通过AMF-A网元向终端设备发送消息p1。相应的，终端设备接收来自SMF网元的消息p1。
其中，该消息p1中携带目标网络切片的过载指示，用于临时拒绝终端设备在当前位置在目标网络切片建立会话，允许终端设备在改变位置区域或等待一段时间后，继 续尝试请求再该目标网络切片建立会话。
示例性的，本申请实施例中的消息p1例如可以为如图6所示的会话建立拒绝消息，本申请实施例对此不作具体限定。
分支ii：
S625、SMF网元允许终端设备在第一区域在目标网络切片建立会话，继续后续的会话建立处理流程。
其中，本申请实施例中，终端设备成功建立会话之后，PCF网元还可以向UDR网元可以更新会话建立过程中目标网络切片的整体业务使用量。后续会话释放后，PCF网元还可以向UDR网元更新会话建立过程中目标网络切片的整体业务使用量。若会话因为终端设备的移动不再使用本区域的用户面节点时，PCF网元也可以向UDR网元新会话建立过程中目标网络切片的整体业务使用量，本申请实施例对此不作具体限定。
其中，图6所示的实施例的技术效果可参考图5所示的实施例，在此不再赘述。
其中，上述步骤S601至步骤S624或者步骤S625中的AMF-A网元的动作可以由图3所示的通信设备300中的处理器301调用存储器303中存储的应用程序代码来执行，本实施例对此不作任何限制。
可选的，以图1所示的通信系统中的第一网元为策略控制网元，图1所示的通信系统应用于如图2所示的5G网络架构，第一区域为图2中的区域A为例，如图7所示，为本申请实施例提供的另一种网络切片的使用控制方法，包括如下步骤：
S701、同图6所示的实施例中的步骤S601，相关描述可参考图6所示的实施例，在此不再赘述。
S702、OAM实体向UDR网元发送目标网络切片在各个区域内的业务限额相关信息。相应的，UDR网元接收来自OAM实体的目标网络切片在各个区域内的业务限额相关信息。
其中，目标网络切片在各个区域内的业务限额相关信息包括目标网络切片在第一区域(即区域A)内的第一业务限额相关信息。终端设备注册流程中对应的第一业务限额相关信息的描述可参考图6所示的实施例中的步骤S602，终端设备的会话建立流程中对应的第一业务限额相关信息的描述可参考图6所示的实施例中的步骤S603，在此不再赘述。
需要说明的是，本申请实施例中的步骤S701和步骤S702之间没有必然的执行先后顺序，可以是先执行步骤S701，再执行步骤S702；也可以是先执行步骤S702，再执行步骤S701；还可以是同时执行步骤S701和步骤S702，本申请实施例对此不作具体限定。
S703、同图6所示的实施例中的步骤S604，相关描述可参考图6所示的实施例，在此不再赘述。
S704、AMF-A网元向PCF网元发送消息q1。相应的，PCF网元接收来自AMF-A网元的消息q1。
其中，消息q1中携带目标网络切片的S-NSSAI。此外，消息q1还可以携带终端设备当前所在的TA的标识和/或小区cell的标识，本申请实施例对此不作具体限定。
示例性的，本申请实施例中的消息q1例如可以为如图7所示的关联注册管理策略 请求，本申请实施例对此不作具体限定。
S705、PCF网元从UDR网元获取目标网络切片的整体业务使用量以及目标网络切片的整体限额；以及PCF网元从UDR网元获取目标网络切片在第一区域内的业务使用量以及第一业务限额。
其中，PCF网元确定终端设备当前所在的区域(即本申请实施例中的第一区域)和目标网络切片的方式可参考图6所示的实施例中的步骤S605，在此不再赘述。
其中，在终端设备的注册流程中，目标网络切片的整体业务使用量、目标网络切片的整体限额、目标网络切片在第一区域内的业务使用量以及第一业务限额的相关描述可参考图4所示的实施例，在此不再赘述。
可选的，本申请实施例中，PCF网元也可以是从UDR网元获取第一业务限额相关信息，进而根据第一业务限额相关信息确定第一业务限额，本申请实施例对此不做具体限定。
需要说明的是，本申请实施例中，如果目标网络切片有多个PCF网元，那么这些PCF网元都在统一使用UDR网元维护目标网络切片的整体业务使用量以及目标网络切片在各个区域内的业务使用量。
S706、PCF网元确定目标网络切片在第一区域内的业务使用量是否超过第一业务限额，以及PCF网元确定目标网络切片的整体业务使用量以及目标网络切片的整体限额。
S707、PCF网元向AMF-A网元发送消息r1。相应的，AMF-A网元接收来自PCF网元的消息r1。
示例性的，本申请实施例中的消息r1例如可以为如图7所示的关联注册管理策略响应，本申请实施例对此不作具体限定。
其中，当PCF网元确定目标网络切片在第一区域内的业务使用量达到或超过第一业务限额时，上述消息r1中可以携带目标网络切片在第一区域内的业务使用量达到或超过第一业务限额的指示或者不允许终端设备使用目标网络切片的指示，进而可以执行下述步骤S708对应的分支一；当PCF网元确定目标网络切片在第一区域内的业务使用量不超过第一业务限额，但是目标网络切片的整体业务使用量达到或超过目标网络切片的整体限额时，上述消息r1中可以携带目标网络切片在第一区域内的业务使用量不超过第一业务限额，但是目标网络切片的整体业务使用量达到或超过目标网络切片的整体限额的指示或者不允许终端设备使用目标网络切片的指示，进而可以执行下述步骤S708对应的分支一；当PCF网元确定目标网络切片在第一区域内的业务使用量不超过第一业务限额，并且目标网络切片的整体业务使用量不超过目标网络切片的整体限额时，上述消息r1中可以携带允许终端设备使用目标网络切片的指示，进而可以执行下述步骤S711对应的分支二。其中，当PCF网元确定目标网络切片在第一区域内的业务使用量等于(即上述的达到)第一业务限额时，对于该分界点，可以继续执行下述步骤S708对应的分支一或者继续确定目标网络切片的整体业务使用量是否超过目标网络切片的整体限额。当PCF网元确定目标网络切片的整体业务使用量等于(即上述的达到)目标网络切片的整体限额时，对于该分界点，可以继续执行下述步骤S708对应的分支一或者执行下述步骤S711对应的分支二，本申请实施例对此不做 具体限定。
分支一：
S708、同图6所示的实施例中的步骤S613，相关描述可参考图6所示的实施例，在此不再赘述。
可选的，本申请实施例中，对于分支一，还可以执行下述步骤S709-S710：
S709-S710、同图6所示的实施例中的步骤S614-S615，相关描述可参考图6所示的实施例，在此不再赘述。
分支二：
S711、同图6所示的实施例中的步骤S616，相关描述可参考图6所示的实施例，在此不再赘述。
进一步的，在终端设备注册成功之后，PCF网元还可以向UDR网元更新目标网络切片的实际整体注册终端数和目标网络切片在第一区域内的实际注册终端数。后续当终端设备从目标网络切片注销或移动出第一区域时，PCF网元还可以向UDR网元更新目标网络切片的实际整体注册终端数和目标网络切片在第一区域内的实际注册终端数，本申请实施例对此不作具体限定。
需要说明的是，本申请实施例中，若上述步骤S705中确定的目标网络切片为多个，或者终端设备不发送request NSSAI，但是签约的默认网络切片有多个(此时每个默认的网络切片均可以作为目标网络切片)时，对于每个目标网络切片，均可以按照上述步骤S705-S711的方式分别进行处理，在此不再一一赘述。
进一步的，在终端设备注册成功之后，本申请实施例提供的网络切片的使用控制方法还包括如下述步骤S712-S717或者如下步骤S712-S718所示的会话建立流程：
S712、同图6所示的实施例中的步骤S617，相关描述可参考图6所示的实施例，在此不再赘述。
S713、SMF网元向PCF网元发送消息s1。相应的，PCF网元接收来自SMF网元的消息s1。
其中，消息s1中携带目标网络切片的S-NSSAI。此外，消息s1还可以携带终端设备当前所在的TA的标识和/或小区cell的标识，本申请实施例对此不作具体限定。
示例性的，本申请实施例中的消息s1例如可以为如图7所示的关联会话管理策略请求，本申请实施例对此不作具体限定。
S714、PCF网元从UDR网元获取目标网络切片的整体业务使用量以及目标网络切片的整体限额；以及PCF网元从UDR网元获取目标网络切片在第一区域内的业务使用量以及第一业务限额。
其中，PCF网元确定终端设备当前所在的区域(即本申请实施例中的第一区域)和目标网络切片的方式可参考图6所示的实施例中的步骤S605，在此不再赘述。
其中，在终端设备的会话建立流程中，目标网络切片的整体业务使用量、目标网络切片的整体限额、目标网络切片在第一区域内的业务使用量以及第一业务限额的相关描述可参考图4所示的实施例，在此不再赘述。
可选的，本申请实施例中，PCF网元也可以是从UDR网元获取第一业务限额相关信息，进而根据第一业务限额相关信息确定第一业务限额，本申请实施例对此不做具 体限定。
需要说明的是，本申请实施例中，如果目标网络切片有多个PCF网元，那么这些PCF网元都在统一使用UDR网元维护目标网络切片的整体业务使用量以及目标网络切片在各个区域内的业务使用量。
S715、PCF网元确定目标网络切片在第一区域内的业务使用量是否超过第一业务限额，以及PCF网元确定目标网络切片的整体业务使用量是否超过目标网络切片的整体限额。
S716、PCF网元向SMF网元发送消息t1。相应的，SMF网元接收来自PCF网元的消息r1。
示例性的，本申请实施例中的消息t1例如可以为如图7所示的关联会话管理策略响应，本申请实施例对此不作具体限定。
其中，当PCF网元确定目标网络切片在第一区域内的业务使用量达到或超过第一业务限额时，上述消息t1中可以携带目标网络切片在第一区域内的业务使用量达到或超过第一业务限额的指示，进而可以执行下述步骤S717对应的分支i；当PCF网元确定目标网络切片在第一区域内的业务使用量不超过第一业务限额，但是目标网络切片的整体业务使用量达到或超过目标网络切片的整体限额时，上述消息t1中可以携带目标网络切片在第一区域内的业务使用量不超过第一业务限额，但是目标网络切片的整体业务使用量达到或超过目标网络切片的整体限额的指示，进而可以执行下述步骤S717对应的分支i；当PCF网元确定目标网络切片在第一区域内的业务使用量不超过第一业务限额，并且目标网络切片的整体业务使用量不超过目标网络切片的整体限额时，上述消息t1中可以携带允许终端设备使用目标网络切片的指示，进而可以执行下述步骤S718对应的分支ii。其中，当PCF网元确定目标网络切片在第一区域内的业务使用量等于(即上述的达到)第一业务限额时，对于该分界点，可以继续执行下述步骤S717对应的分支i或者继续确定目标网络切片的整体业务使用量是否超过目标网络切片的整体限额。当PCF网元确定目标网络切片的整体业务使用量等于(即上述的达到)目标网络切片的整体限额时，对于该分界点，可以继续执行下述步骤S717对应的分支i或者执行下述步骤S718对应的分支ii，本申请实施例对此不做具体限定。
分支i：
S717、同图6所示的实施例中的步骤S624，相关描述可参考图6所示的实施例，在此不再赘述。
分支ii：
S718、同图6所示的实施例中的步骤S625，相关描述可参考图6所示的实施例，在此不再赘述。
其中，本申请实施例中，终端设备成功建立会话之后，PCF网元还可以向UDR网元可以更新会话建立过程中目标网络切片的整体业务使用量以及目标网络切片在第一区域内的业务使用量。后续会话释放后，PCF网元还可以向UDR网元更新会话建立过程中目标网络切片的整体业务使用量以及目标网络切片在第一区域内的业务使用量。若会话因为终端设备的移动不再使用本区域的用户面节点时，PCF网元也可以向UDR网元新会话建立过程中目标网络切片的整体业务使用量以及目标网络切片在第一区域 内的业务使用量，本申请实施例对此不作具体限定。
其中，图7所示的实施例的技术效果可参考图5所示的实施例，在此不再赘述。
其中，上述步骤S701至步骤S717或者步骤S718中的SMF网元的动作可以由图3所示的通信设备300中的处理器301调用存储器303中存储的应用程序代码来执行，本实施例对此不作任何限制。
可选的，以图1所示的通信系统中的第一网元为策略控制网元，图1所示的通信系统应用于如图2所示的5G网络架构，第一区域为图2中的区域A为例，如图8所示，为本申请实施例提供的另一种网络切片的使用控制方法，包括如下步骤：
S801-S802、同图7所示的实施例中的步骤S701-S702，相关描述可参考图7所示的实施例，在此不再赘述。
S803、OAM实体向UDR网元发送目标网络切片在各个区域内的限制策略(可以简称目标网络切片的区域限制策略)以及目标网络切片的整体限制策略。相应的，UDR网元接收来自OAM实体的目标网络切片的区域限制策略和整体限制策略。
其中，目标网络切片的区域限制策略包括目标网络切片在第一区域(即区域A)内的区域限制策略(可以简称第一区域限制策略)。
可选的，本申请实施例中，目标网络切片的区域限制策略例如可以包括：当目标网络切片在区域内的业务使用量达到或超过该区域内的业务限额时，拒绝该终端设备使用目标网络切片。
可选的，本申请实施例中，目标网络切片的整体限制策略例如可以是：当目标网络切片的整体业务使用量达到或超过整体限额，但目标网络切片在区域内的业务使用量不超过该区域内的业务限额时，若满足第二条件，允许终端设备使用目标网络切片。
示例性的，本申请实施例中，终端设备的注册流程中对应的第二条件例如可以包括：目标网络切片的切片签约信息中允许整体超限，或者目标网络切片的计费方式为按会话或按流量计费，或者目标网络切片签约的业务类型为特定业务类型，或者请求接入的终端设备属于高价值客户，或者目标网络切片的切片运行分析预测结果显示低于特定门限，或者请求接入的终端设备的移动行为分析预测结果指示请求接入的终端设备的业务负荷低于特定门限。
示例性的，本申请实施例中，终端设备的会话建立流程中对应的第二条件例如可以包括：目标网络切片的切片签约信息中允许整体超限，或者目标网络切片的计费方式为按会话或按流量计费，或者目标网络切片签约的业务类型为特定业务类型，或者请求接入的终端设备属于高价值客户，或者目标网络切片的整体会话数量和流量带宽低于过载风险门限，或者终端设备签约的服务质量QoS参数指示终端设备的业务允许被抢占，或者目标网络切片的切片运行分析或预测结果显示低于特定门限，或者请求接入的终端设备的移动或通信行为分析预测结果指示请求接入的终端设备的业务负荷低于特定门限。
需要说明的是，本申请实施例中的步骤S801、步骤S802和步骤S803之间没有必然的执行先后顺序，可以是先执行其中的任意一个步骤，再分别执行剩余的两个步骤；也可以是先同时执行其中的两个步骤，再执行剩余的一个步骤；还可以是先执行其中的一个步骤，再同时执行剩余的两个步骤；还可以是同时执行这三个步骤，本申请实 施例对此不做具体限定。
S804-S807、同图7所示的实施例中的步骤S703-S706，相关描述可参考图7所示的实施例，在此不再赘述。
此外，本申请实施例中，PCF网元还需要从UDR网元获取注册流程中所需的目标网络切片的整体限制策略以及目标网络切片在第一区域(即区域A)内的区域限制策略(可以简称第一区域限制策略)，在此统一说明，以下不再赘述。
其中，当PCF网元确定目标网络切片在第一区域内的业务使用量达到或超过第一业务限额时；或者当PCF网元确定目标网络切片在第一区域内的业务使用量不超过第一业务限额，并且目标网络切片的整体业务使用量不超过目标网络切片的整体限额时，直接执行下述步骤S810；当PCF网元确定目标网络切片在第一区域内的业务使用量不超过第一业务限额，但是目标网络切片的整体业务使用量达到或超过目标网络切片的整体限额时，先执行步骤S808和/或步骤S809确定是否满足第二条件，进而执行步骤S810：
S808、PCF网元从UDM网元获取终端设备或者目标网络切片的签约信息，并根据终端设备或者目标网络切片的签约信息确定是否满足：目标网络切片的切片签约信息中允许整体超限，或者目标网络切片的计费方式为按会话或按流量计费，或者目标网络切片签约的业务类型为特定业务类型，或者请求接入的终端设备属于高价值客户。
S809、PCF网元从NWDAF网元获取请求接入的终端设备的移动行为分析预测结果或者目标网络切片的切片运行分析预测结果中的一个或多个，并确定是否满足：目标网络切片的切片运行分析预测结果显示低于特定门限，或者请求接入的终端设备的移动行为分析预测结果指示请求接入的终端设备的业务负荷低于特定门限。
S810、PCF网元向AMF-A网元发送消息u1。相应的，AMF-A网元接收来自PCF网元的消息u1。
示例性的，本申请实施例中的消息u1例如可以为如图8所示的关联注册管理策略响应，本申请实施例对此不作具体限定。
其中，当步骤S807中PCF网元确定目标网络切片在第一区域内的业务使用量达到或超过第一业务限额时，上述消息u1中可以携带目标网络切片在第一区域内的业务使用量达到或超过第一业务限额的指示或者不允许终端设备使用目标网络切片的指示，进而可以执行下述步骤S811对应的分支一；当步骤S807中PCF网元确定目标网络切片在第一区域内的业务使用量不超过第一业务限额，并且目标网络切片的整体业务使用量不超过目标网络切片的整体限额时，上述消息u1中可以携带允许终端设备使用目标网络切片的指示，进而可以执行下述步骤S814对应的分支二；当步骤S807中PCF网元确定目标网络切片在第一区域内的业务使用量不超过第一业务限额，但是目标网络切片的整体业务使用量达到或超过目标网络切片的整体限额时，当根据步骤S808和/或步骤S809确定满足第二条件，上述消息u1中可以携带允许终端设备使用目标网络切片的指示，进而可以执行下述步骤S814对应的分支二；当步骤S807中PCF网元确定目标网络切片在第一区域内的业务使用量不超过第一业务限额，但是目标网络切片的整体业务使用量达到或超过目标网络切片的整体限额时，当根据步骤S808和/或步骤S809确定不满足第二条件，上述消息u1中可以携带不允许终端设备使用目标网 络切片的指示，进而可以执行下述步骤S811对应的分支一。其中，当PCF网元确定目标网络切片在第一区域内的业务使用量等于(即上述的达到)第一业务限额时，对于该分界点，可以继续执行下述步骤S811对应的分支一或者继续确定目标网络切片的整体业务使用量是否超过目标网络切片的整体限额。当PCF网元确定目标网络切片的整体业务使用量等于(即上述的达到)目标网络切片的整体限额时，对于该分界点，可以继续执行下述步骤S814对应的分支二或者确定是否满足第二条件，本申请实施例对此不做具体限定。
分支一：
S811、同图7所示的实施例中的步骤S708，相关描述可参考图7所示的实施例，在此不再赘述。
可选的，本申请实施例中，对于分支一，还可以执行下述步骤S812-S813：
S812-S813、同图7所示的实施例中的步骤S709-S710，相关描述可参考图7所示的实施例，在此不再赘述。
分支二：
S814、同图7所示的实施例中的步骤S711，相关描述可参考图7所示的实施例，在此不再赘述。
进一步的，在终端设备注册成功之后，PCF网元还可以向UDR网元更新目标网络切片的实际整体注册终端数和目标网络切片在第一区域内的实际注册终端数。后续当终端设备从目标网络切片注销或移动出第一区域时，PCF网元还可以向UDR网元更新目标网络切片的实际整体注册终端数和目标网络切片在第一区域内的实际注册终端数，本申请实施例对此不作具体限定。
需要说明的是，本申请实施例中，若上述步骤S806中确定的目标网络切片为多个，或者终端设备不发送request NSSAI，但是签约的默认网络切片有多个(此时每个默认的网络切片均可以作为目标网络切片)时，对于每个目标网络切片，均可以按照上述步骤S806-S814的方式分别进行处理，在此不再一一赘述。
进一步的，在终端设备注册成功之后，本申请实施例提供的网络切片的使用控制方法还包括如下述步骤S815-S823或者如下步骤S815-S824所示的会话建立流程：
S815-S818、同图7所示的实施例中的步骤S712-S715，相关描述可参考图7所示的实施例，在此不再赘述。
此外，本申请实施例中，PCF网元还需要从UDR网元获取会话建立流程中所需的目标网络切片的整体限制策略以及目标网络切片在第一区域(即区域A)内的区域限制策略(可以简称第一区域限制策略)，在此统一说明，以下不再赘述。
其中，当PCF网元确定目标网络切片在第一区域内的业务使用量达到或超过第一业务限额时；或者当PCF网元确定目标网络切片在第一区域内的业务使用量不超过第一业务限额，并且目标网络切片的整体业务使用量不超过目标网络切片的整体限额时，直接执行下述步骤S810；当PCF网元确定目标网络切片在第一区域内的业务使用量不超过第一业务限额，但是目标网络切片的整体业务使用量达到或超过目标网络切片的整体限额时，先执行步骤S819和/或步骤S820和/或步骤S821确定是否满足第二条件，进而执行步骤S822：
S819、PCF网元从UDM网元获取终端设备或者目标网络切片的签约信息，并根据终端设备或者目标网络切片的签约信息确定是否满足：目标网络切片的切片签约信息中允许整体超限，或者目标网络切片的计费方式为按会话或按流量计费，或者目标网络切片签约的业务类型为特定业务类型，或者请求接入的终端设备属于高价值客户，或者终端设备签约的服务质量QoS参数指示终端设备的业务允许被抢占。
S820、PCF网元从NWDAF网元获取请求接入的终端设备的移动或通信行为分析预测结果或者目标网络切片的切片运行分析预测结果中的一个或多个，并确定是否满足：目标网络切片的切片运行分析预测结果显示低于特定门限，或者请求接入的终端设备的移动或通信行为分析预测结果指示请求接入的终端设备的业务负荷低于特定门限。
S821、当步骤S817获取的网络网络切片的整体业务使用量为整体会话数量时，PCF网元从UDR网元获取目标网络切片的流量带宽；当步骤S817获取的网络网络切片的整体业务使用量为流量带宽时，PCF网元从UDR网元获取目标网络切片的整体会话数量。进而PCF网元确定是否满足：目标网络切片的整体会话数量和流量带宽低于过载风险门限。
S822、PCF网元向SMF网元发送消息v1。相应的，SMF网元接收来自PCF网元的消息v1。
示例性的，本申请实施例中的消息v1例如可以为如图8所示的关联会话管理策略响应，本申请实施例对此不作具体限定。
其中，当步骤S818中PCF网元确定目标网络切片在第一区域内的业务使用量达到或超过第一业务限额时，上述消息v1中可以携带目标网络切片在第一区域内的业务使用量达到或超过第一业务限额的指示或者不允许终端设备使用目标网络切片的指示，进而可以执行下述步骤S823对应的分支i；当步骤S818中PCF网元确定目标网络切片在第一区域内的业务使用量不超过第一业务限额，并且目标网络切片的整体业务使用量不超过目标网络切片的整体限额时，上述消息v1中可以携带允许终端设备使用目标网络切片的指示，进而可以执行下述步骤S824对应的分支ii；当步骤S818中PCF网元确定目标网络切片在第一区域内的业务使用量不超过第一业务限额，但是目标网络切片的整体业务使用量达到或超过目标网络切片的整体限额时，当根据步骤S819和/或步骤S820和/或步骤S821确定满足第二条件，上述消息v1中可以携带允许终端设备使用目标网络切片的指示，进而可以执行下述步骤S824对应的分支ii；当步骤S818中PCF网元确定目标网络切片在第一区域内的业务使用量不超过第一业务限额，但是目标网络切片的整体业务使用量达到或超过目标网络切片的整体限额时，当根据步骤S819和/或步骤S820和/或步骤S821确定不满足第二条件，上述消息v1中可以携带不允许终端设备使用目标网络切片的指示，进而可以执行下述步骤S823对应的分支i。其中，当PCF网元确定目标网络切片在第一区域内的业务使用量等于(即上述的达到)第一业务限额时，对于该分界点，可以继续执行下述步骤S823对应的分支i或者继续确定目标网络切片的整体业务使用量是否超过目标网络切片的整体限额。当PCF网元确定目标网络切片的整体业务使用量等于(即上述的达到)目标网络切片的整体限额时，对于该分界点，可以继续执行下述步骤S824对应的分支ii或者确定是 否满足第二条件，本申请实施例对此不做具体限定。
分支i：
S823、同图6所示的实施例中的步骤S624，相关描述可参考图6所示的实施例，在此不再赘述。
分支ii：
S824、同图6所示的实施例中的步骤S625，相关描述可参考图6所示的实施例，在此不再赘述。
其中，本申请实施例中，终端设备成功建立会话之后，PCF网元还可以向UDR网元可以更新会话建立过程中目标网络切片的整体业务使用量以及目标网络切片在第一区域内的业务使用量。后续会话释放后，PCF网元还可以向UDR网元更新会话建立过程中目标网络切片的整体业务使用量以及目标网络切片在第一区域内的业务使用量。若会话因为终端设备的移动不再使用本区域的用户面节点时，PCF网元也可以向UDR网元新会话建立过程中目标网络切片的整体业务使用量以及目标网络切片在第一区域内的业务使用量，本申请实施例对此不作具体限定。
由于本申请实施例中的目标网络切片覆盖多个区域，第一网元可以根据第一条件判断是否将该终端设备接入到目标网络切片。其中，一方面，第一条件包括：目标网络切片在第一区域内的业务使用量是否超过第一业务限额。换句话说，本申请实施例实现了网络切片接入的分区域控制，因此可以避免区域内无线侧网络节点拥塞或过载，不仅不能很好保障本网络切片的业务质量，还可能对其他网络切片的业务质量产生影响的问题，从而可以限制客户过量使用网络切片资源，同时保障网络切片的业务质量。另一方面，第一条件还可以包括：目标网络切片的整体业务使用量是否超过整体限额。考虑到若网络切片内某个区域的终端设备非常稀疏，则该区域可能有大量的空闲资源，但是因为整个网络切片的业务使用量超过指定限额，终端设备在这个区域也会被限制接入，造成这个区域内的资源浪费。因此本申请实施例中，当目标网络切片的整体业务使用量达到或超过整体限额，但目标网络切片在第一区域内的业务使用量不超过第一业务限额时，若满足第二条件，第一网元允许终端设备使用目标网络切片。换句话说，当目标网络切片的整体业务使用量达到或超过整体限额，但目标网络切片在第一区域内的业务使用量不超过第一业务限额时，在一定场景下可以允许用户在第一区域使用目标网络切片资源，因此可以提高网络资源的利用率，不仅能为运营商带来更多的经济收益，而且可以提高价值用户的业务体验。
其中，上述步骤S801至步骤S823或者步骤S824中的PCF网元的动作可以由图3所示的通信设备300中的处理器301调用存储器303中存储的应用程序代码来执行，本实施例对此不作任何限制。
可选的，以图1所示的通信系统中的第一网元为策略控制网元，图1所示的通信系统应用于如图2所示的5G网络架构，第一区域为图2中的区域A为例，如图9所示，为本申请实施例提供的另一种网络切片的使用控制方法，包括如下步骤：
S901、同图8所示的实施例中的步骤S801，相关描述可参考图8所示的实施例，在此不再赘述。
S902、OAM实体向UDR网元发送目标网络切片的整体限制策略。相应的，UDR 网元接收来自OAM实体的目标网络切片的整体限制策略。
其中，目标网络切片的整体限制策略的相关描述可参考图8所示的实施例中的步骤S803，在此不再赘述。
S903-S904、同图6所示的实施例中的步骤S602-S603，相关描述可参考图6所示的实施例，在此不再赘述。
需要说明的是，本申请实施例中的步骤S901-S904的各个步骤之间没有必然的执行先后顺序，可以是先执行一个或多个步骤，再执行其余步骤，也可以是同时执行这4个步骤，本申请实施例对此不作具体限定。
S905-S906、同图5所示的实施例中的步骤S503-S504，相关描述可参考图5所示的实施例，在此不再赘述。
本申请实施例中，在终端设备的注册流程中，目标网络切片在第一区域内的业务使用量包括目标网络切片在第一区域内的实际注册终端数。AMF-A网元在注册管理过程中会维护当前服务的各个网络切片在该AMF-A网元管理的各个区域内的实际注册终端数，这其中包括目标网络切片在第一区域内的实际注册终端数。进而，AMF-A网元可以将目标网络切片在第一区域内的实际注册终端数与步骤S903中确定的目标网络切片在第一区域内允许的最大注册终端数进行比较。当目标网络切片在第一区域内的实际注册终端数达到或超过目标网络切片在第一区域内允许的最大注册终端数时，则执行下述步骤S907对应的分支一；当目标网络切片在第一区域内的实际注册终端数不超过目标网络切片在第一区域内允许的最大注册终端数时，则执行下述步骤S910以及之后的步骤对应的分支二。其中，当目标网络切片在第一区域内的实际注册终端数等于(即上述的达到)目标网络切片在第一区域内允许的最大注册终端数时，对于该分界点，可以继续执行下述步骤S907对应的分支一或者继续执行下述步骤S910以及之后的步骤对应的分支二，本申请实施例对此不做具体限定。
分支一：
S907、同图5所示的实施例中的步骤S505，相关描述可参考图5所示的实施例，在此不再赘述。
可选的，本申请实施例中，对于分支一，还可以执行下述步骤S908-S909：
S908-S909、同图5所示的实施例中的步骤S506-S507，相关描述可参考图5所示的实施例，在此不再赘述。
分支二：
S910、同图5所示的实施例中的步骤S508，相关描述可参考图5所示的实施例，在此不再赘述。
S911、NSSF网元向PCF网元发送消息a2。相应的，PCF网元接收来自NSSF网元的消息a2。
其中，消息a2携带目标网络切片在第一区域内的实际注册终端数。
示例性的，本申请实施例中的消息a2例如可以为如图9所示的关联切片管理策略请求，本申请实施例对此不作具体限定。
S912-S913、同图6所示的实施例中的步骤S610-S611，相关描述可参考图6所示的实施例，在此不再赘述。
此外，本申请实施例中，PCF网元还需要从UDR网元获取注册流程中所需的目标网络切片的整体限制策略，在此统一说明，以下不再赘述。
其中，当PCF网元确定目标网络切片的整体业务使用量不超过目标网络切片的整体限额时，直接执行下述步骤S916；当PCF网元确定目标网络切片的整体业务使用量达到或超过目标网络切片的整体限额时，先执行步骤S914和/或步骤S915确定是否满足第二条件，进而执行步骤S916：
S914-S915、同图8所示的实施例中的步骤S808-S809，相关描述可参考图5所示的实施例，在此不再赘述。
S916、PCF网元向NSSF网元发送消息b2。相应的，NSSF网元接收来自PCF网元的消息b2。
示例性的，本申请实施例中的消息b2例如可以为如图9所示的关联切片管理策略响应，本申请实施例对此不作具体限定。
S917、NSSF网元向AMF-A网元发送消息c2。相应的，AMF-A网元接收来自NSSF网元的消息c2。
示例性的，本申请实施例中的消息c2例如可以为如图9所示的切片选择响应消息，本申请实施例对此不作具体限定。
其中，当步骤S913中PCF网元确定目标网络切片的整体业务使用量不超过目标网络切片的整体限额时，上述消息b2中可以携带第一区域内的业务使用量的配额或者允许终端设备使用目标网络切片的指示，上述消息c2中可以携带第一区域内的业务使用量的配额或者允许终端设备使用目标网络切片的指示，进而可以执行下述步骤S921对应的分支b；当步骤S913中PCF网元确定目标网络切片的整体业务使用量达到或超过目标网络切片的整体限额时，当根据步骤S914和/或步骤S915确定满足第二条件，上述消息b2中可以携带第一区域内的业务使用量的配额或者允许终端设备使用目标网络切片的指示或者超限接入标识，上述消息c2中可以携带第一区域内的业务使用量的配额或者允许终端设备使用目标网络切片的指示或者超限接入标识，进而可以执行下述步骤S921对应的分支b；当步骤S913中PCF网元确定目标网络切片的整体业务使用量达到或超过目标网络切片的整体限额时，当根据步骤S914和/或步骤S915确定不满足第二条件，上述消息b2和消息c2中可以携带不允许终端设备使用目标网络切片的指示，进而可以执行下述步骤S918对应的分支a。其中，当PCF网元确定目标网络切片的整体业务使用量等于(即上述的达到)目标网络切片的整体限额时，对于该分界点，可以继续执行下述步骤S921对应的分支b或者确定是否满足第二条件，本申请实施例对此不做具体限定。
分支a：
S918、同图7所示的实施例中的步骤S708，相关描述可参考图7所示的实施例，在此不再赘述。
可选的，本申请实施例中，对于分支a，还可以执行下述步骤S812-S813：
S919-S920、同图7所示的实施例中的步骤S709-S710，相关描述可参考图7所示的实施例，在此不再赘述。
分支b：
S921、同图7所示的实施例中的步骤S711，相关描述可参考图7所示的实施例，在此不再赘述。
进一步的，在终端设备注册成功之后，PCF网元还可以向UDR网元更新目标网络切片的实际整体注册终端数。后续当终端设备从目标网络切片注销或移动出第一区域时，PCF网元还可以向UDR网元更新目标网络切片的实际整体注册终端数，本申请实施例对此不作具体限定。
需要说明的是，本申请实施例中，若上述步骤S906中确定的目标网络切片为多个，或者终端设备不发送request NSSAI，但是签约的默认网络切片有多个(此时每个默认的网络切片均可以作为目标网络切片)时，对于每个目标网络切片，均可以按照上述步骤S906-S921的方式分别进行处理，在此不再一一赘述。
进一步的，在终端设备注册成功之后，本申请实施例提供的网络切片的使用控制方法还包括如下述步骤S922-S932或者如下步骤S922-S933所示的会话建立流程：
S922-S923、同图6所示的实施例中的步骤S617-S618，相关描述可参考图6所示的实施例，在此不再赘述。
其中，当目标网络切片在第一区域内的业务使用量达到或超过第一业务限额时，则执行下述步骤S924对应的分支三；当目标网络切片在第一区域内的业务使用量不超过第一业务限额时，则执行下述步骤S925以及之后的步骤对应的分支四：
分支三：
S924、同图6所示的实施例中的步骤S619，相关描述可参考图6所示的实施例，在此不再赘述。
分支四：
S925-S927、同图6所示的实施例中的步骤S620-S622，相关描述可参考图6所示的实施例，在此不再赘述。
此外，本申请实施例中，PCF网元还需要从UDR网元获取会话建立流程中所需的目标网络切片的整体限制策略，在此统一说明，以下不再赘述。
其中，当PCF网元确定目标网络切片的整体业务使用量不超过目标网络切片的整体限额时，直接执行下述步骤S931；当PCF网元确定目标网络切片的整体业务使用量达到或超过目标网络切片的整体限额时，先执行步骤S928和/或步骤S929和/或步骤S930确定是否满足第二条件，进而执行步骤S931：
S928-S930、同图8所示的实施例中的步骤S819-S821，相关描述可参考图8所示的实施例，在此不再赘述。
S931、PCF网元向SMF网元发送消息d2。相应的，SMF网元接收来自PCF网元的消息d2。
示例性的，本申请实施例中的消息d2例如可以为如图9所示的关联会话管理策略响应，本申请实施例对此不作具体限定。
其中，当步骤S927中PCF网元确定目标网络切片的整体业务使用量不超过目标网络切片的整体限额时，上述消息d2中可以携带允许终端设备使用目标网络切片的指示，进而可以执行下述步骤S933对应的分支ii；当步骤S927中PCF网元确定目标网络切片的整体业务使用量达到或超过目标网络切片的整体限额时，当根据步骤S928 和/或步骤S929和/或步骤S930确定满足第二条件，上述消息d2中可以携带允许终端设备使用目标网络切片的指示或者超限接入标识，进而可以执行下述步骤S933对应的分支ii；当步骤S927中PCF网元确定目标网络切片的整体业务使用量达到或超过目标网络切片的整体限额时，当根据步骤S928和/或步骤S929和/或步骤S930确定不满足第二条件，上述消息d2中可以携带不允许终端设备使用目标网络切片的指示，进而可以执行下述步骤S932对应的分支i。其中，当PCF网元确定目标网络切片的整体业务使用量等于(即上述的达到)目标网络切片的整体限额时，对于该分界点，可以继续执行下述步骤S933对应的分支ii或者确定是否满足第二条件，本申请实施例对此不做具体限定。
分支i：
S932、同图8所示的实施例中的步骤S823，相关描述可参考图8所示的实施例，在此不再赘述。
分支ii：
S933、同图8所示的实施例中的步骤S824，相关描述可参考图8所示的实施例，在此不再赘述。
其中，本申请实施例中，终端设备成功建立会话之后，PCF网元还可以向UDR网元可以更新会话建立过程中目标网络切片的整体业务使用量。后续会话释放后，PCF网元还可以向UDR网元更新会话建立过程中目标网络切片的整体业务使用量。若会话因为终端设备的移动不再使用本区域的用户面节点时，PCF网元也可以向UDR网元新会话建立过程中目标网络切片的整体业务使用量，本申请实施例对此不作具体限定。
可选的，本申请实施例中，也可以不执行步骤S904，而是在步骤S903中配置的目标网络切片在第一区域内的第一业务限额相关信息可以包括终端设备的会话建立流程中对应的目标网络切片在第一区域内的第一业务限额相关信息，进而在终端设备的会话建立过程中，由AMF-A网元确定目标网络切片在第一区域内的业务使用量是否超过第一业务限额，进而当AMF-A网元确定目标网络切片在第一区域内的业务使用量达到或超过第一业务限额时，执行步骤S924；当AMF-A网元确定目标网络切片在第一区域内的业务使用量不超过第一业务限额时，由AMF-A网元向SMF网元发送会话建立请求之后，继续执行后续的步骤S925-S932或者步骤S925-S933，本申请实施例对此不作具体限定。
其中，图9所示的实施例的技术效果可参考图8所示的实施例，在此不再赘述。
其中，上述步骤S901至步骤S932或者步骤S933中的PCF网元或者AMF-A网元或者SMF网元的动作可以由图3所示的通信设备300中的处理器301调用存储器303中存储的应用程序代码来执行，本实施例对此不作任何限制。
可选的，以图1所示的通信系统中的第一网元为移动管理网元或者会话管理网元，图1所示的通信系统应用于如图2所示的5G网络架构，第一区域为图2中的区域A为例，如图10所示，为本申请实施例提供的另一种网络切片的使用控制方法，包括如下步骤：
S1001、同图8所示的实施例中的步骤S801，相关描述可参考图8所示的实施例，在此不再赘述。
S1002、OAM实体向目标网络切片覆盖的各个区域的AMF网元发送目标网络切片在各个区域内的业务限额相关信息以及目标网络切片的整体限额策略。相应的，目标网络切片覆盖的各个区域的AMF网元接收来自OAM实体的目标网络切片在各个区域内的业务限额相关信息以及目标网络切片的整体限额策略。其中，图10仅是示例性的以OAM实体向目标网络切片覆盖的第一区域(即区域A)的AMF-A网元发送目标网络切片在第一区域内的第一业务限额相关信息以及目标网络切片的整体限额策略为例进行说明；相应的，AMF-A网元接收来自OAM实体的目标网络切片在第一区域内的第一业务限额相关信息以及目标网络切片的整体限额策略。
可选的，步骤S1002中的第一业务限额相关信息包括终端设备的注册流程中所需的第一业务限额或者用于确定该第一业务限额的信息。其中，终端设备的注册流程中所需的第一业务限额或者用于确定该第一业务限额的信息的相关描述可参考图5所示的实施例中的步骤S502，在此不再赘述。步骤S1002中的目标网络切片的整体限额策略例如可以是：当目标网络切片的整体业务使用量达到或超过整体限额，但目标网络切片在区域内的业务使用量不超过该区域内的业务限额时，若满足第二条件，允许终端设备使用目标网络切片。
示例性的，本申请实施例中，终端设备的注册流程中对应的第二条件例如可以包括当NSSF网元指示目标网络切片的整体业务使用量达到或超过整体限额时，NSSF网元指示的会话数量配额超过指定数量。
S1003、OAM实体向目标网络切片覆盖的各个区域的SMF网元发送目标网络切片在各个区域内的业务限额相关信息以及目标网络切片的整体限额策略。相应的，目标网络切片覆盖的各个区域的SMF网元接收来自OAM实体的目标网络切片在各个区域内的业务限额相关信息以及目标网络切片的整体限额策略。其中，图10仅是示例性的以OAM实体向目标网络切片覆盖的第一区域(即区域A)的SMF网元发送目标网络切片在第一区域内的第一业务限额相关信息以及目标网络切片的整体限额策略为例进行说明；相应的，SMF网元接收来自OAM实体的目标网络切片在第一区域内的第一业务限额相关信息以及目标网络切片的整体限额策略。
可选的，步骤S1003中的第一业务限额相关信息包括终端设备的会话建立流程中所需的第一业务限额或者用于确定该第一业务限额的信息。其中，终端设备的会话建立流程中所需的第一业务限额或者用于确定该第一业务限额的信息的相关描述可参考图5所示的实施例中的步骤S502，在此不再赘述。步骤S1003中的目标网络切片的整体限额策略例如可以是：当目标网络切片的整体业务使用量达到或超过整体限额，但目标网络切片在区域内的业务使用量不超过该区域内的业务限额时，若满足第二条件，允许终端设备使用目标网络切片。
示例性的，本申请实施例中，终端设备的会话建立流程中对应的第二条件例如可以是：当PCF网元指示所述目标网络切片的整体业务使用量达到或超过整体限额时，终端设备的业务QoS参数指示会话是可被抢占。
需要说明的是，本申请实施例中的步骤S1001、步骤S1002和步骤S1003之间没有必然的执行先后顺序，可以是先执行其中的任意一个步骤，再分别执行剩余的两个步骤；也可以是先同时执行其中的两个步骤，再执行剩余的一个步骤；还可以是先执 行其中的一个步骤，再同时执行剩余的两个步骤；还可以是同时执行这三个步骤，本申请实施例对此不做具体限定。
S1004-S1005、同图9所示的实施例中的步骤S905-S906，相关描述可参考图9所示的实施例，在此不再赘述。
本申请实施例中，在终端设备的注册流程中，目标网络切片在第一区域内的业务使用量包括目标网络切片在第一区域内的实际注册终端数。AMF-A网元在注册管理过程中会维护当前服务的各个网络切片在该AMF-A网元管理的各个区域内的实际注册终端数，这其中包括目标网络切片在第一区域内的实际注册终端数。进而，AMF-A网元可以将目标网络切片在第一区域内的实际注册终端数与步骤S1002中确定的目标网络切片在第一区域内允许的最大注册终端数进行比较。当目标网络切片在第一区域内的实际注册终端数达到或超过目标网络切片在第一区域内允许的最大注册终端数时，则执行下述步骤S1006对应的分支一；当目标网络切片在第一区域内的实际注册终端数不超过目标网络切片在第一区域内允许的最大注册终端数时，则执行下述步骤S1009以及之后的步骤对应的分支二。其中，当目标网络切片在第一区域内的实际注册终端数等于(即上述的达到)目标网络切片在第一区域内允许的最大注册终端数时，对于该分界点，可以继续执行下述步骤S1006对应的分支一或者继续执行下述步骤S1009以及之后的步骤对应的分支二，本申请实施例对此不做具体限定。
分支一：
S1006、同图9所示的实施例中的步骤S907，相关描述可参考图9所示的实施例，在此不再赘述。
可选的，本申请实施例中，对于分支一，还可以执行下述步骤S908-S909：
S1007-S1008、同图9所示的实施例中的步骤S908-S909，相关描述可参考图9所示的实施例，在此不再赘述。
分支二：
S1009-S1012、同图9所示的实施例中的步骤S910-S913，相关描述可参考图9所示的实施例，在此不再赘述。
S1013-S1014、同图9所示的实施例中的步骤S916-S917，相关描述可参考图9所示的实施例，在此不再赘述。
其中，当步骤S1012中PCF网元确定目标网络切片的整体业务使用量不超过目标网络切片的整体限额时，上述消息b2中可以携带第一区域内的业务使用量的配额或者允许终端设备使用目标网络切片的指示，上述消息c2中可以携带第一区域内的业务使用量的配额或者允许终端设备使用目标网络切片的指示，进而可以执行下述步骤S1019应的分支b；当步骤S1012中PCF网元确定目标网络切片的整体业务使用量达到或超过目标网络切片的整体限额时，上述消息b2和消息c2中可以携带第一区域内的业务使用量的配额(为0)或者目标网络切片的整体业务使用量达到或超过目标网络切片的整体限额的指示，此外，上述消息b2和消息c2中还可以携带目标网络切片在第一区域内的会话数量配额，进而执行下述步骤S1015。
S1015、AMF-A网元确定是否满足上述步骤S1002中的第二条件。
当AMF-A网元确定满足上述步骤S1002中的第二条件时，继续执行下述步骤 S1019应的分支b；当AMF-A网元确定不满足上述步骤S1002中的第二条件时，继续执行下述步骤S1016应的分支a。其中，当PCF网元确定目标网络切片的整体业务使用量等于(即上述的达到)目标网络切片的整体限额时，对于该分界点，可以继续执行下述步骤S1019对应的分支b或者执行步骤S1015，本申请实施例对此不做具体限定。
分支a：
S1016、同图9所示的实施例中的步骤S918，相关描述可参考图9所示的实施例，在此不再赘述。
可选的，本申请实施例中，对于分支a，还可以执行下述步骤S1017-S1018：
S1017-S1018、同图9所示的实施例中的步骤S919-S920，相关描述可参考图9所示的实施例，在此不再赘述。
分支b：
S1019、同图9所示的实施例中的步骤S921，相关描述可参考图9所示的实施例，在此不再赘述。
进一步的，在终端设备注册成功之后，PCF网元还可以向UDR网元更新目标网络切片的实际整体注册终端数。后续当终端设备从目标网络切片注销或移动出第一区域时，PCF网元还可以向UDR网元更新目标网络切片的实际整体注册终端数，本申请实施例对此不作具体限定。
需要说明的是，本申请实施例中，若上述步骤S1005中确定的目标网络切片为多个，或者终端设备不发送request NSSAI，但是签约的默认网络切片有多个(此时每个默认的网络切片均可以作为目标网络切片)时，对于每个目标网络切片，均可以按照上述步骤S1005-S1019的方式分别进行处理，在此不再一一赘述。
进一步的，在终端设备注册成功之后，本申请实施例提供的网络切片的使用控制方法还包括如下述步骤S1020-1028或者如下步骤S1020-S1029所示的会话建立流程：
S1020-S1021、同图9所示的实施例中的步骤S922-S923，相关描述可参考图9所示的实施例，在此不再赘述。
其中，当目标网络切片在第一区域内的业务使用量达到或超过第一业务限额时，则执行下述步骤S1022对应的分支三；当目标网络切片在第一区域内的业务使用量不超过第一业务限额时，则执行下述步骤S1023以及之后的步骤对应的分支四：
分支三：
S1022、同图9所示的实施例中的步骤S924，相关描述可参考图9所示的实施例，在此不再赘述。
分支四：
S1023-S1025、同图9所示的实施例中的步骤S925-S927，相关描述可参考图9所示的实施例，在此不再赘述。
S1026、同图9所示的实施例中的步骤S931，相关描述可参考图9所示的实施例，在此不再赘述。
其中，当步骤S1025中PCF网元确定目标网络切片的整体业务使用量不超过目标网络切片的整体限额时，上述消息d2中可以携带第一区域内的业务使用量的配额或者 允许终端设备使用目标网络切片的指示，进而可以执行下述步骤S1029应的分支ii；当步骤S1025中PCF网元确定目标网络切片的整体业务使用量达到或超过目标网络切片的整体限额时，上述消息d2中可以携带第一区域内的业务使用量的配额(为0)或者目标网络切片的整体业务使用量达到或超过目标网络切片的整体限额的指示，此外，上述消息d2中还可以携带终端设备的业务QoS参数，进而执行下述步骤S1027。
S1027、SMF网元确定是否满足上述步骤S1003中的第二条件。
当SMF网元确定满足上述步骤S1003中的第二条件时，继续执行下述步骤S1029应的分支ii；当SMF网元确定不满足上述步骤S1003中的第二条件时，继续执行下述步骤S1028应的分支i。其中，当PCF网元确定目标网络切片的整体业务使用量等于(即上述的达到)目标网络切片的整体限额时，对于该分界点，可以继续执行下述步骤S1029对应的分支ii或者执行步骤S1027，本申请实施例对此不做具体限定。
分支i：
S1028、同图9所示的实施例中的步骤S932，相关描述可参考图9所示的实施例，在此不再赘述。
分支ii：
S1029、同图9所示的实施例中的步骤S933，相关描述可参考图9所示的实施例，在此不再赘述。
其中，本申请实施例中，终端设备成功建立会话之后，PCF网元还可以向UDR网元可以更新会话建立过程中目标网络切片的整体业务使用量。后续会话释放后，PCF网元还可以向UDR网元更新会话建立过程中目标网络切片的整体业务使用量。若会话因为终端设备的移动不再使用本区域的用户面节点时，PCF网元也可以向UDR网元新会话建立过程中目标网络切片的整体业务使用量，本申请实施例对此不作具体限定。
其中，图10所示的实施例的技术效果可参考图8所示的实施例，在此不再赘述。
其中，上述步骤S1001至步骤S1028或者步骤S1029中的PCF网元或者AMF-A网元或者SMF网元的动作可以由图3所示的通信设备300中的处理器301调用存储器303中存储的应用程序代码来执行，本实施例对此不作任何限制。
可选的，以图1所示的通信系统中的第一网元为移动管理网元或者会话管理网元，图1所示的通信系统应用于如图2所示的5G网络架构，第一区域为图2中的区域A为例，如图11所示，为本申请实施例提供的另一种网络切片的使用控制方法，包括如下步骤：
S1101、OAM实体向UDR网元发送目标网络切片的整体限制策略。相应的，UDR网元接收来自OAM实体的目标网络切片的整体限制策略。
可选的，本申请实施例中，目标网络切片的整体限制策略例如可以是：当目标网络切片的整体业务使用量达到或超过整体限额，但目标网络切片在区域内的业务使用量不超过该区域内的业务限额时，若满足第二条件，允许终端设备使用目标网络切片。
示例性的，这里的第二条件可以包括：当前或未来目标网络切片在第一区域内的运行负荷低于指定阈值；或者，当前或未来目标网络切片的整体运行负荷低于指定阈值，或者当前或未来目标网络切片在第一区域的网络性能高于指定阈值。
S1102、OAM实体向目标网络切片覆盖的各个区域的AMF网元发送目标网络切 片在各个区域内的业务限额相关信息以及目标网络切片的整体限额。相应的，目标网络切片覆盖的各个区域的AMF网元接收来自OAM实体的目标网络切片在各个区域内的业务限额相关信息以及目标网络切片的整体限额。其中，图11仅是示例性的以OAM实体向目标网络切片覆盖的第一区域(即区域A)的AMF-A网元发送目标网络切片在第一区域内的第一业务限额相关信息以及目标网络切片的整体限额为例进行说明；相应的，AMF-A网元接收来自OAM实体的目标网络切片在第一区域内的第一业务限额相关信息以及目标网络切片的整体限额。
其中，步骤S1102中的目标网络切片在各个区域内的业务限额相关信息以及目标网络切片的整体限额可参考图5所示的实施例中终端设备的注册流程中所需的目标网络切片在各个区域内的业务限额相关信息以及目标网络切片的整体限额，在此不再赘述。
S1103、OAM实体向目标网络切片覆盖的各个区域的SMF网元发送目标网络切片在各个区域内的业务限额相关信息以及目标网络切片的整体限额。相应的，目标网络切片覆盖的各个区域的SMF网元接收来自OAM实体的目标网络切片在各个区域内的业务限额相关信息以及目标网络切片的整体限额。其中，图11仅是示例性的以OAM实体向目标网络切片覆盖的第一区域(即区域A)的SMF网元发送目标网络切片在第一区域内的第一业务限额相关信息以及目标网络切片的整体限额为例进行说明；相应的，SMF网元接收来自OAM实体的目标网络切片在第一区域内的第一业务限额相关信息以及目标网络切片的整体限额。
其中，步骤S1102中的目标网络切片在各个区域内的业务限额相关信息以及目标网络切片的整体限额可参考图5所示的实施例中终端设备的会话建立流程中所需的目标网络切片在各个区域内的业务限额相关信息以及目标网络切片的整体限额，在此不再赘述。
需要说明的是，本申请实施例中的步骤S1101、步骤S1102和步骤S1103之间没有必然的执行先后顺序，可以是先执行其中的任意一个步骤，再分别执行剩余的两个步骤；也可以是先同时执行其中的两个步骤，再执行剩余的一个步骤；还可以是先执行其中的一个步骤，再同时执行剩余的两个步骤；还可以是同时执行这三个步骤，本申请实施例对此不做具体限定。
S1104、同图10所示的实施例中的步骤S1004，相关描述可参考图10所示的实施例，在此不再赘述。
S1105、AMF-A网元确定目标网络切片在第一区域内的业务使用量是否超过第一业务限额，以及AMF-A网元确定目标网络切片的整体业务使用量是否超过目标网络切片的整体限额。
其中，步骤S1105中目标网络切片在第一区域内的业务使用量、第一业务限额、目标网络切片的整体业务使用量以及目标网络切片的整体限额均为终端设备的注册流程中所需的信息，相关描述可参考图4所示的实施例，在此不再赘述。
其中，当AMF-A网元确定目标网络切片在第一区域内的业务使用量达到或超过第一业务限额时，执行下述步骤S1109对应的分支一；当AMF-A网元确定目标网络切片在第一区域内的业务使用量不超过第一业务限额，并且目标网络切片的整体业务 使用量不超过目标网络切片的整体限额时，执行下述步骤S1112对应的分支二；当AMF-A网元确定目标网络切片在第一区域内的业务使用量不超过第一业务限额，并且目标网络切片的整体业务使用量达到或超过目标网络切片的整体限额时，执行步骤S1106-S1108：
S1106、AMF-A网元通过接入管理(access management，AM)-PCF网元从UDR网元获取目标网络切片的整体限额策略。
需要说明的是，本申请实施例中的AM-PCF网元和下述的会话管理(session management，SM)-PCF网元可以视为将图2所示的PCF网元的功能拆分后部署的两个独立的网元。换言之，图2所示的PCF网元可以视为将本申请实施例中的AM-PCF网元和SM-PCF网元合设的网元。其中，AM-PCF网元主要用于接入和移动性策略的管理，SM-PCF网元主要用于会话策略的管理，在此统一说明，以下不再赘述。
S1107、AMF-A网元从NWDAF网元获取切片运行状态分析预测。
其中，该切片运行状态分析预测包括当前或未来目标网络切片在第一区域内的运行负荷、目标网络切片的整体运行负荷或者目标网络切片在第一区域的网络性能中的一个或多个。
S1108、AMF-A网元确定是否满足第二条件。
当AMF-A网元确定满足第二条件时，继续执行下述步骤S1112应的分支二；当AMF-A网元确定不满足第二条件时，继续执行下述步骤S1109应的分支一。其中，当AMF-A网元确定目标网络切片在第一区域内的业务使用量等于(即上述的达到)第一业务限额时，对于该分界点，可以继续执行下述步骤S1109对应的分支一或者执行步骤S1106-S1108，本申请实施例对此不做具体限定。当AMF-A网元确定目标网络切片在第一区域内的业务使用量不超过第一业务限额，并且目标网络切片的整体业务使用量等于目标网络切片的整体限额时，对于该分界点，可以继续执行下述步骤S1112对应的分支二或者执行步骤S1106-S1108，本申请实施例对此不做具体限定。
分支一：
S1109、同图10所示的实施例中的步骤S1016，相关描述可参考图10所示的实施例，在此不再赘述。
可选的，本申请实施例中，对于分支一，还可以执行下述步骤S1110-S1111：
S1110-S1111、同图10所示的实施例中的步骤S1017-S1018，相关描述可参考图10所示的实施例，在此不再赘述。
分支二：
S1112、同图10所示的实施例中的步骤S1019，相关描述可参考图10所示的实施例，在此不再赘述。
需要说明的是，本申请实施例中，若上述步骤S1105中确定的目标网络切片为多个，或者终端设备不发送request NSSAI，但是签约的默认网络切片有多个(此时每个默认的网络切片均可以作为目标网络切片)时，对于每个目标网络切片，均可以按照上述步骤S1105-S1112的方式分别进行处理，在此不再一一赘述。
进一步的，在终端设备注册成功之后，本申请实施例提供的网络切片的使用控制方法还包括如下述步骤S1113-1118或者如下步骤S1113-S1119所示的会话建立流程：
S1113、同图10所示的实施例中的步骤S1020，相关描述可参考图10所示的实施例，在此不再赘述。
S1114、SMF网元确定目标网络切片在第一区域内的业务使用量是否超过第一业务限额，以及SMF网元确定目标网络切片的整体业务使用量是否超过目标网络切片的整体限额。
其中，步骤S1114中目标网络切片在第一区域内的业务使用量、第一业务限额、目标网络切片的整体业务使用量以及目标网络切片的整体限额均为终端设备的会话建立流程中所需的信息，相关描述可参考图4所示的实施例，在此不再赘述。
其中，当SMF网元确定目标网络切片在第一区域内的业务使用量达到或超过第一业务限额时，执行下述步骤S1118对应的分支i；当SMF网元确定目标网络切片在第一区域内的业务使用量不超过第一业务限额，并且目标网络切片的整体业务使用量不超过目标网络切片的整体限额时，执行下述步骤S1119对应的分支ii；当SMF网元确定目标网络切片在第一区域内的业务使用量不超过第一业务限额，并且目标网络切片的整体业务使用量达到或超过目标网络切片的整体限额时，执行步骤S1115-S1117：
S1115、SMF网元通过SM-PCF网元从UDR网元获取目标网络切片的整体限额策略。
S1116、SMF网元从NWDAF网元获取切片运行状态分析预测。
其中，该切片运行状态分析预测包括当前或未来目标网络切片在第一区域内的运行负荷、目标网络切片的整体运行负荷或者目标网络切片在第一区域的网络性能中的一个或多个。
S1117、SMF网元确定是否满足第二条件。
当SMF网元确定满足第二条件时，继续执行下述步骤S1119应的分支ii；当SMF网元确定不满足第二条件时，继续执行下述步骤S1118应的分支i。其中，当SMF网元确定目标网络切片在第一区域内的业务使用量等于(即上述的达到)第一业务限额时，对于该分界点，可以继续执行下述步骤S1118对应的分支i或者执行步骤S1115-S1117，本申请实施例对此不做具体限定。当SMF网元确定目标网络切片在第一区域内的业务使用量不超过第一业务限额，并且目标网络切片的整体业务使用量等于目标网络切片的整体限额时，对于该分界点，可以继续执行下述步骤S1119对应的分支ii或者执行步骤S1115-S1117，本申请实施例对此不做具体限定。
分支i：
S1118、同图10所示的实施例中的步骤S1028，相关描述可参考图10所示的实施例，在此不再赘述。
分支ii：
S1119、同图10所示的实施例中的步骤S1029，相关描述可参考图10所示的实施例，在此不再赘述。
其中，图11所示的实施例的技术效果可参考图8所示的实施例，在此不再赘述。
其中，上述步骤S1101至步骤S1118或者步骤S1119中的AM-PCF网元或者SM-PCF网元或者AMF-A网元或者SMF网元的动作可以由图3所示的通信设备300中的处理器301调用存储器303中存储的应用程序代码来执行，本实施例对此不作任 何限制。
需要说明的是，上述图5至图11所示的各个实施例中的注册流程和会话建立流程可以相互解耦。换句话说，终端设备可以采用其中任意一个实施例中的注册流程进行注册，采用其中任意一个实施例中的会话建立流程建立会话，本申请实施例对此不作具体限定。
可以理解的是，以上各个实施例中，由第一网元实现的方法和/或步骤，也可以由可用于第一网元的部件(例如芯片或者电路)实现。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。相应的，本申请实施例还提供了通信装置，该通信装置可以为上述方法实施例中的第一网元，或者包含上述第一网元的装置，或者为可用于第一网元的部件。可以理解的是，该通信装置为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
比如，以通信装置为上述方法实施例中的第一网元为例，图12示出了一种第一网元120的结构示意图。该第一网元120包括收发模块1201和处理模块1202。所述收发模块1201，也可以称为收发单元用以实现收发功能，例如可以是收发电路，收发机，收发器或者通信接口。
其中，收发模块1201，用于接收第一消息，第一消息用于请求将终端设备接入到目标网络切片，其中，目标网络切片覆盖多个区域，多个区域包括第一区域，第一区域为终端设备当前所在的区域。处理模块1202，用于根据第一条件判断是否将终端设备接入到目标网络切片，其中，第一条件包括：目标网络切片在第一区域内的业务使用量是否超过第一业务限额。
可选的，处理模块1202具体用于：当目标网络切片在第一区域内的业务使用量达到或超过第一业务限额时，拒绝第一消息。
可选的，第一条件还包括：目标网络切片的整体业务使用量是否超过整体限额。
可选的，处理模块1202具体用于：当目标网络切片在第一区域内的业务使用量不超过第一业务限额，但是目标网络切片的整体业务使用量达到或超过整体限额时，拒绝第一消息。
一种可能的实现方式中，收发模块1201，还用于接收来自第二网元的第二消息，第二消息携带第一信息，第一信息指示目标网络切片的整体业务使用量达到或超过整体限额。
可选的，第一信息为第一区域内的业务使用量的配额为0，或者第一信息为目标网络切片的整体业务使用量达到或超过目标网络切片的整体限额的指示。
另一种可能的实现方式中，其特征在于，收发模块1201，还用于接收来自第三网元的第三消息，第三消息携带目标网络切片的整体业务使用量；处理模块1202，还用于确定目标网络切片的整体业务使用量达到或超过目标网络切片的整体限额。
可选的，处理模块1202具体用于：当目标网络切片的整体业务使用量达到或超过整体限额，但目标网络切片在第一区域内的业务使用量不超过第一业务限额时，若满足第二条件，允许终端设备使用目标网络切片。
一种可能的实现方式中，第一网元为策略控制网元，第一消息为关联注册管理策略请求或者关联切片管理策略请求，第二条件包括：目标网络切片的切片签约信息中允许整体超限，或者目标网络切片的计费方式为按会话或按流量计费，或者目标网络切片签约的业务类型为特定业务类型，或者当请求接入的终端设备属于高价值客户，或者目标网络切片的切片运行分析或预测结果显示低于特定门限，或者请求接入的终端设备的移动行为分析预测结果指示请求接入的终端设备的业务负荷低于特定门限。
可选的，该实现方式下，处理模块1202，还用于当第一网元接收来自切片选择功能网元的关联切片管理策略请求时，确定目标网络切片在第一区域内的业务使用量不超过第一业务限额。
另一种可能的实现方式中，第一网元为策略控制网元，第一消息为关联会话管理策略请求，第二条件包括：目标网络切片的切片签约信息中允许整体超限，或者目标网络切片的计费方式为按会话或按流量计费，或者目标网络切片签约的业务类型为特定业务类型，或者请求接入的终端设备属于高价值客户，或者目标网络切片的整体会话数量和流量带宽低于过载风险门限，或者终端设备签约的QoS参数指示终端设备的业务允许被抢占，或者目标网络切片的切片运行分析或预测结果显示低于特定门限，或者请求接入的终端设备的移动或通信行为分析预测结果指示请求接入的终端设备的业务负荷低于特定门限。
可选的，该实现方式下，处理模块1202，还用于当第一网元接收来自会话管理网元的关联会话管理策略请求时，确定目标网络切片在第一区域内的业务使用量不超过第一业务限额。
又一种可能的实现方式中，第一网元为移动管理网元，第一消息为注册请求，第二条件包括：当切片选择功能网元指示目标网络切片的整体业务使用量达到或超过整体限额时，切片选择功能网元指示的会话数量配额超过指定数量。
可选的，该实现方式下，处理模块1202，还用于当第一网元接收来自切片选择功能网元的会话数量配额以及目标网络切片的整体业务使用量达到或超过目标网络切片的整体限额的指示时，确定目标网络切片的整体业务使用量达到或超过整体限额。
又一种可能的实现方式中，第一网元为会话管理网元，第一消息为会话建立请求，第二条件包括：当策略控制网元指示目标网络切片的整体业务使用量达到或超过整体限额时，策略控制网元指示的终端设备的业务QoS参数指示会话是可被抢占。
可选的，该实现方式下，处理模块1202，还用于当第一网元接收来自策略控制网元的终端设备的业务QoS参数和目标网络切片的整体业务使用量达到或超过目标网络切片的整体限额的指示时，确定目标网络切片的整体业务使用量达到或超过整体限额。
又一种可能的实现方式中，第一网元为移动管理网元，第一消息为注册请求；或者，第一网元为会话管理网元，第一消息为会话建立请求；第二条件包括：目标网络切片在第一区域内的运行负荷低于指定阈值；或者，目标网络切片的整体运行负荷低于指定阈值，或者目标网络切片在第一区域的网络性能高于指定阈值。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本实施例中，该第一网元120以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到该第一网元120可以采用图3所示的通信设备300的形式。
比如，图3所示的通信设备300中的处理器301可以通过调用存储器303中存储的计算机执行指令，使得通信设备300执行上述方法实施例中的网络切片选择的方法。
具体的，图12中的收发模块1201和处理模块1202的功能/实现过程可以通过图3所示的通信设备300中的处理器301调用存储器303中存储的计算机执行指令来实现。或者，图12中的处理模块1202的功能/实现过程可以通过图3所示的通信设备300中的处理器301调用存储器303中存储的计算机执行指令来实现，图12中的收发模块1201的功能/实现过程可以通过图3中所示的通信设备300中的通信接口304来实现。
由于本实施例提供的第一网元120可执行上述的网络切片的使用控制方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
需要说明的是，以上模块或单元的一个或多个可以软件、硬件或二者结合来实现。当以上任一模块或单元以软件实现的时候，所述软件以计算机程序指令的方式存在，并被存储在存储器中，处理器可以用于执行所述程序指令并实现以上方法流程。该处理器可以内置于SoC(片上系统)或ASIC，也可是一个独立的半导体芯片。该处理器内处理用于执行软件指令以进行运算或处理的核外，还可进一步包括必要的硬件加速器，如现场可编程门阵列(field programmable gate array，FPGA)、PLD(可编程逻辑器件)、或者实现专用逻辑运算的逻辑电路。
当以上模块或单元以硬件实现的时候，该硬件可以是CPU、微处理器、数字信号处理(digital signal processing，DSP)芯片、微控制单元(microcontroller unit，MCU)、人工智能处理器、ASIC、SoC、FPGA、PLD、专用数字电路、硬件加速器或非集成的分立器件中的任一个或任一组合，其可以运行必要的软件或不依赖于软件以执行以上方法流程。
可选的，本申请实施例还提供了一种通信装置(例如，该通信装置可以是芯片或芯片系统)，该通信装置包括处理器，用于实现上述任一方法实施例中的方法。在一种可能的设计中，该通信装置还包括存储器。该存储器，用于保存必要的程序指令和数据，处理器可以调用存储器中存储的程序代码以指令该通信装置执行上述任一方法实施例中的方法。当然，存储器也可以不在该通信装置中。该通信装置是芯片系统时，可以由芯片构成，也可以包含芯片和其他分立器件，本申请实施例对此不作具体限定。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储 在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
尽管在此结合各实施例对本申请进行了描述，然而，在实施所要求保护的本申请过程中，本领域技术人员通过查看所述附图、公开内容、以及所附权利要求书，可理解并实现所述公开实施例的其他变化。在权利要求中，“包括”(comprising)一词不排除其他组成部分或步骤，“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (30)

  1. 一种网络切片的使用控制方法，其特征在于，所述方法包括：
    第一网元接收第一消息，所述第一消息用于请求将终端设备接入到目标网络切片，其中，所述目标网络切片覆盖多个区域，所述多个区域包括第一区域，所述第一区域为所述终端设备当前所在的区域；
    所述第一网元根据第一条件判断是否将所述终端设备接入到所述目标网络切片，其中，所述第一条件包括：所述目标网络切片在所述第一区域内的业务使用量是否超过第一业务限额。
  2. 根据权利要求1所述的方法，其特征在于，所述第一网元根据第一条件判断是否将所述终端设备接入到所述目标网络切片，包括：
    当所述目标网络切片在所述第一区域内的业务使用量达到或超过所述第一业务限额时，所述第一网元拒绝所述第一消息。
  3. 根据权利要求1所述的方法，其特征在于，所述第一条件还包括：所述目标网络切片的整体业务使用量是否超过整体限额。
  4. 根据权利要求3所述的方法，其特征在于，所述第一网元根据第一条件判断是否将所述终端设备接入到所述目标网络切片，包括：
    当所述目标网络切片在所述第一区域内的业务使用量不超过所述第一业务限额，但是所述目标网络切片的整体业务使用量达到或超过整体限额时，所述第一网元拒绝所述第一消息。
  5. 根据权利要求4所述的方法，其特征在于，所述方法还包括：
    所述第一网元接收来自第二网元的第二消息，所述第二消息携带第一信息，所述第一信息指示所述目标网络切片的整体业务使用量达到或超过所述整体限额。
  6. 根据权利要求5所述的方法，其特征在于，所述第一信息为所述第一区域内的业务使用量的配额为0，或者所述第一信息为所述目标网络切片的整体业务使用量达到或超过所述目标网络切片的整体限额的指示。
  7. 根据权利要求4所述的方法，其特征在于，所述方法还包括：
    所述第一网元接收来自第三网元的第三消息，所述第三消息携带所述目标网络切片的整体业务使用量；
    所述第一网元确定所述目标网络切片的整体业务使用量达到或超过所述目标网络切片的整体限额。
  8. 根据权利要求3所述的方法，其特征在于，所述第一网元根据第一条件判断是否将所述终端设备接入到所述目标网络切片，包括：
    当所述目标网络切片的整体业务使用量达到或超过所述整体限额，但所述目标网络切片在所述第一区域内的业务使用量不超过所述第一业务限额时，若满足第二条件，所述第一网元允许所述终端设备使用所述目标网络切片。
  9. 根据权利要求8所述的方法，其特征在于，所述第一网元为策略控制网元，所述第一消息为关联注册管理策略请求或者关联切片管理策略请求，所述第二条件包括：
    所述目标网络切片的切片签约信息中允许整体超限，或者所述目标网络切片的计费方式为按会话或按流量计费，或者所述目标网络切片签约的业务类型为特定业务类 型，或者当请求接入的终端设备属于高价值客户，或者所述目标网络切片的切片运行分析或预测结果显示低于特定门限，或者所述请求接入的终端设备的移动行为分析预测结果指示所述请求接入的终端设备的业务负荷低于特定门限。
  10. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    当所述第一网元接收来自切片选择功能网元的关联切片管理策略请求时，所述第一网元确定所述目标网络切片在所述第一区域内的业务使用量不超过所述第一业务限额。
  11. 根据权利要求8所述的方法，其特征在于，所述第一网元为策略控制网元，所述第一消息为关联会话管理策略请求，所述第二条件包括：
    所述目标网络切片的切片签约信息中允许整体超限，或者所述目标网络切片的计费方式为按会话或按流量计费，或者所述目标网络切片签约的业务类型为特定业务类型，或者请求接入的终端设备属于高价值客户，或者所述目标网络切片的整体会话数量和流量带宽低于过载风险门限，或者所述终端设备签约的服务质量QoS参数指示所述终端设备的业务允许被抢占，或者所述目标网络切片的切片运行分析或预测结果显示低于特定门限，或者所述请求接入的终端设备的移动或通信行为分析预测结果指示所述请求接入的终端设备的业务负荷低于特定门限。
  12. 根据权利要求11所述的方法，其特征在于，所述方法还包括：
    当所述第一网元接收来自会话管理网元的关联会话管理策略请求时，所述第一网元确定所述目标网络切片在所述第一区域内的业务使用量不超过所述第一业务限额。
  13. 根据权利要求8所述的方法，其特征在于，所述第一网元为移动管理网元，所述第一消息为注册请求，所述第二条件包括：
    当切片选择功能网元指示所述目标网络切片的整体业务使用量达到或超过所述整体限额时，所述切片选择功能网元指示的会话数量配额超过指定数量。
  14. 根据权利要求13所述的方法，其特征在于，所述方法还包括：
    当所述第一网元接收来自所述切片选择功能网元的所述会话数量配额以及所述目标网络切片的整体业务使用量达到或超过所述目标网络切片的整体限额的指示时，所述第一网元确定所述目标网络切片的整体业务使用量达到或超过所述整体限额。
  15. 根据权利要求8所述的方法，其特征在于，所述第一网元为会话管理网元，所述第一消息为会话建立请求，所述第二条件包括：
    当策略控制网元指示所述目标网络切片的整体业务使用量达到或超过所述整体限额时，所述策略控制网元指示的所述终端设备的业务QoS参数指示会话是可被抢占。
  16. 根据权利要求15所述的方法，其特征在于，所述方法还包括：
    当所述第一网元接收来自所述策略控制网元的所述终端设备的业务QoS参数和所述目标网络切片的整体业务使用量达到或超过所述目标网络切片的整体限额的指示时，所述第一网元确定所述目标网络切片的整体业务使用量达到或超过所述整体限额。
  17. 根据权利要求8所述的方法，其特征在于，所述第一网元为移动管理网元，所述第一消息为注册请求；或者，所述第一网元为会话管理网元，所述第一消息为会话建立请求；
    所述第二条件包括：
    所述目标网络切片在所述第一区域内的运行负荷低于指定阈值；或者，
    所述目标网络切片的整体运行负荷低于指定阈值，或者所述目标网络切片在所述第一区域的网络性能高于指定阈值。
  18. 根据权利要求3-17任一项所述的方法，其特征在于，当所述第一消息为注册相关的消息时，所述目标网络切片的整体业务使用量为所述目标网络切片的实际整体注册终端数，所述目标网络切片的整体限额为所述目标网络切片整体允许的最大注册终端数；
    或者，当所述第一消息为会话建立相关的消息时，所述目标网络切片的整体业务使用量为所述目标网络切片的实际整体并发会话数，所述目标网络切片的整体限额为所述目标网络切片整体允许的最大并发会话数；
    或者，当所述第一消息为会话建立相关的消息时，所述目标网络切片的整体业务使用量为所述目标网络切片的实际整体流量带宽，所述目标网络切片的整体限额为所述目标网络切片整体允许的最大流量带宽。
  19. 根据权利要求1-18任一项所述的方法，其特征在于，当所述第一消息为注册相关的消息时，所述目标网络切片在所述第一区域内的业务使用量包括所述目标网络切片在所述第一区域内的实际注册终端数，所述第一业务限额包括所述目标网络切片在所述第一区域内允许的最大注册终端数；
    或者，当所述第一消息为会话建立相关的消息时，所述目标网络切片在所述第一区域内的业务使用量包括所述目标网络切片在所述第一区域内的实际并发会话数，所述第一业务限额包括所述目标网络切片在所述第一区域内允许的最大并发会话数；
    或者，当所述第一消息为会话建立相关的消息时，所述目标网络切片在所述第一区域内的业务使用量包括所述目标网络切片在所述第一区域内的实际流量带宽，所述第一业务限额包括所述目标网络切片在所述第一区域内允许的最大流量带宽。
  20. 一种第一网元，其特征在于，所述第一网元包括：收发模块和处理模块；
    所述收发模块，用于接收第一消息，所述第一消息用于请求将终端设备接入到目标网络切片，其中，所述目标网络切片覆盖多个区域，所述多个区域包括第一区域，所述第一区域为所述终端设备当前所在的区域；
    所述处理模块，用于根据第一条件判断是否将所述终端设备接入到所述目标网络切片，其中，所述第一条件包括：所述目标网络切片在所述第一区域内的业务使用量是否超过第一业务限额。
  21. 根据权利要求20所述的第一网元，其特征在于，所述处理模块具体用于：
    当所述目标网络切片在所述第一区域内的业务使用量达到或超过所述第一业务限额时，拒绝所述第一消息。
  22. 根据权利要求20所述的第一网元，其特征在于，所述第一条件还包括：所述目标网络切片的整体业务使用量是否超过整体限额。
  23. 根据权利要求22所述的第一网元，其特征在于，所述处理模块具体用于：
    当所述目标网络切片在所述第一区域内的业务使用量不超过所述第一业务限额，但是所述目标网络切片的整体业务使用量达到或超过整体限额时，拒绝所述第一消息。
  24. 根据权利要求22所述的第一网元，其特征在于，所述处理模块具体用于：
    当所述目标网络切片的整体业务使用量达到或超过所述整体限额，但所述目标网络切片在所述第一区域内的业务使用量不超过所述第一业务限额时，若满足第二条件，允许所述终端设备使用所述目标网络切片。
  25. 根据权利要求24所述的第一网元，其特征在于，所述第一网元为策略控制网元，所述第一消息为关联注册管理策略请求或者关联切片管理策略请求，所述第二条件包括：
    所述目标网络切片的切片签约信息中允许整体超限，或者所述目标网络切片的计费方式为按会话或按流量计费，或者所述目标网络切片签约的业务类型为特定业务类型，或者当请求接入的终端设备属于高价值客户，或者所述目标网络切片的切片运行分析或预测结果显示低于特定门限，或者所述请求接入的终端设备的移动行为分析预测结果指示所述请求接入的终端设备的业务负荷低于特定门限。
  26. 根据权利要求24所述的第一网元，其特征在于，所述第一网元为策略控制网元，所述第一消息为关联会话管理策略请求，所述第二条件包括：
    所述目标网络切片的切片签约信息中允许整体超限，或者所述目标网络切片的计费方式为按会话或按流量计费，或者所述目标网络切片签约的业务类型为特定业务类型，或者请求接入的终端设备属于高价值客户，或者所述目标网络切片的整体会话数量和流量带宽低于过载风险门限，或者所述终端设备签约的服务质量QoS参数指示所述终端设备的业务允许被抢占，或者所述目标网络切片的切片运行分析或预测结果显示低于特定门限，或者所述请求接入的终端设备的移动或通信行为分析预测结果指示所述请求接入的终端设备的业务负荷低于特定门限。
  27. 根据权利要求24所述的第一网元，其特征在于，所述第一网元为移动管理网元，所述第一消息为注册请求，所述第二条件包括：
    当切片选择功能网元指示所述目标网络切片的整体业务使用量达到或超过所述整体限额时，所述切片选择功能网元指示的会话数量配额超过指定数量。
  28. 根据权利要求24所述的第一网元，其特征在于，所述第一网元为会话管理网元，所述第一消息为会话建立请求，所述第二条件包括：
    当策略控制网元指示所述目标网络切片的整体业务使用量达到或超过所述整体限额时，所述策略控制网元指示的所述终端设备的业务QoS参数指示会话是可被抢占。
  29. 根据权利要求24所述的第一网元，其特征在于，所述第一网元为移动管理网元，所述第一消息为注册请求；或者，所述第一网元为会话管理网元，所述第一消息为会话建立请求；所述第二条件包括：
    所述目标网络切片在所述第一区域内的运行负荷低于指定阈值；或者，
    所述目标网络切片的整体运行负荷低于指定阈值，或者所述目标网络切片在所述第一区域的网络性能高于指定阈值。
  30. 根据权利要求20-29任一项所述的第一网元，其特征在于，当所述第一消息为注册相关的消息时，所述目标网络切片在所述第一区域内的业务使用量包括所述目标网络切片在所述第一区域内的实际注册终端数，所述第一业务限额包括所述目标网络切片在所述第一区域内允许的最大注册终端数；
    或者，当所述第一消息为会话建立相关的消息时，所述目标网络切片在所述第一 区域内的业务使用量包括所述目标网络切片在所述第一区域内的实际并发会话数，所述第一业务限额包括所述目标网络切片在所述第一区域内允许的最大并发会话数；
    或者，当所述第一消息为会话建立相关的消息时，所述目标网络切片在所述第一区域内的业务使用量包括所述目标网络切片在所述第一区域内的实际流量带宽，所述第一业务限额包括所述目标网络切片在所述第一区域内允许的最大流量带宽。
PCT/CN2020/121644 2019-11-06 2020-10-16 网络切片的使用控制方法、装置及系统 WO2021088625A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20884070.2A EP4040859A4 (en) 2019-11-06 2020-10-16 METHOD, APPARATUS, AND SYSTEM FOR MONITORING NETWORK SLOT USAGE
US17/737,205 US20220264428A1 (en) 2019-11-06 2022-05-05 Method for controlling use of network slice, apparatus, and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201911078541.5 2019-11-06
CN201911078541.5A CN112788704B (zh) 2019-11-06 2019-11-06 网络切片的使用控制方法、装置及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/737,205 Continuation US20220264428A1 (en) 2019-11-06 2022-05-05 Method for controlling use of network slice, apparatus, and system

Publications (1)

Publication Number Publication Date
WO2021088625A1 true WO2021088625A1 (zh) 2021-05-14

Family

ID=75747652

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/121644 WO2021088625A1 (zh) 2019-11-06 2020-10-16 网络切片的使用控制方法、装置及系统

Country Status (4)

Country Link
US (1) US20220264428A1 (zh)
EP (1) EP4040859A4 (zh)
CN (2) CN114867083A (zh)
WO (1) WO2021088625A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230115367A1 (en) * 2021-10-08 2023-04-13 Dish Wireless L.L.C. Selective handover of cellular device based on network slicing

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11963200B2 (en) * 2021-03-09 2024-04-16 Amdocs Development Limited System, method, and computer program for resource orchestration in a 5G network based on user equipment behavior analystics
CN115551122A (zh) * 2021-06-30 2022-12-30 华为技术有限公司 切片准入控制的方法和通信装置
CN115915337A (zh) * 2021-08-06 2023-04-04 华为技术有限公司 一种网络切片接入控制方法及通信装置
CN116347564A (zh) * 2021-12-23 2023-06-27 中国电信股份有限公司 针对切片的核心网辅助小区/接入方式选择的方法及设备
CN116803111A (zh) * 2022-01-14 2023-09-22 北京小米移动软件有限公司 确定注册用户数量的方法、装置、通信设备及存储介质
WO2023133861A1 (zh) * 2022-01-14 2023-07-20 北京小米移动软件有限公司 信息传输方法、装置、通信设备和存储介质
WO2023137750A1 (en) * 2022-01-24 2023-07-27 Zte Corporation Method for slice resource release

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018045511A1 (zh) * 2016-09-07 2018-03-15 华为技术有限公司 接入控制方法和装置
CN108141412A (zh) * 2015-10-28 2018-06-08 英特尔Ip公司 具有端到端网络切片的无线网络中的基于切片的操作
US20180220276A1 (en) * 2017-01-27 2018-08-02 Huawei Technologies Co., Ltd. Method and apparatus for charging operations in a communication network supporting virtual network customers
CN109600768A (zh) * 2017-09-30 2019-04-09 华为技术有限公司 网络切片的管理方法、设备及系统
CN109743213A (zh) * 2019-02-28 2019-05-10 腾讯科技（深圳）有限公司 一种网络切片处理方法和设备以及系统

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109257769B (zh) * 2017-07-12 2020-09-01 维沃移动通信有限公司 一种处理网络切片拥塞的方法、相关设备和系统
CN111491345B (zh) * 2017-08-11 2021-04-20 华为技术有限公司 通信方法、接入网设备及计算机可读存储介质
CN109587742B (zh) * 2017-09-28 2020-09-29 维沃移动通信有限公司 无线通信的方法和设备
CN117596632A (zh) * 2017-10-13 2024-02-23 三星电子株式会社 网络实体及其执行的方法
WO2019120109A1 (zh) * 2017-12-20 2019-06-27 华为技术有限公司 一种切片信息更新方法及装置
CN109951877B (zh) * 2017-12-20 2023-06-02 华为技术有限公司 一种切片信息更新方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108141412A (zh) * 2015-10-28 2018-06-08 英特尔Ip公司 具有端到端网络切片的无线网络中的基于切片的操作
WO2018045511A1 (zh) * 2016-09-07 2018-03-15 华为技术有限公司 接入控制方法和装置
US20180220276A1 (en) * 2017-01-27 2018-08-02 Huawei Technologies Co., Ltd. Method and apparatus for charging operations in a communication network supporting virtual network customers
CN109600768A (zh) * 2017-09-30 2019-04-09 华为技术有限公司 网络切片的管理方法、设备及系统
CN109743213A (zh) * 2019-02-28 2019-05-10 腾讯科技（深圳）有限公司 一种网络切片处理方法和设备以及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LG ELECTRONICS, SAMSUNG: "TS 23.502 Paging handling in Non-allowed area", 3GPP DRAFT; S2-175295_TS 23.502 PAGING HANDLING FOR NON ALLOWED AREA R3, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. San Jose Del Cabo, Mexico; 20170626 - 20170630, 3 July 2017 (2017-07-03), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051310263 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230115367A1 (en) * 2021-10-08 2023-04-13 Dish Wireless L.L.C. Selective handover of cellular device based on network slicing

Also Published As

Publication number Publication date
US20220264428A1 (en) 2022-08-18
CN112788704B (zh) 2022-05-10
EP4040859A4 (en) 2022-11-30
CN114867083A (zh) 2022-08-05
EP4040859A1 (en) 2022-08-10
CN112788704A (zh) 2021-05-11

Similar Documents

Publication Publication Date Title
WO2021088625A1 (zh) 网络切片的使用控制方法、装置及系统
US11588710B2 (en) Intelligent prioritized mobility of low-latency applications
US10708368B1 (en) System and methods for generating a slice deployment description for a network slice instance
US11223976B2 (en) Multiple-slice application delivery based on network slice associations
CN109548082B (zh) 业务重定向方法及装置
US20220400421A1 (en) Cell reselection method and apparatus, and communication device
US11445515B2 (en) Network slice selection based on requested service
CN111052787A (zh) 基于5g环境中的利用水平的功能选择
WO2019137125A1 (zh) 会话管理方法、设备及系统
WO2022048505A1 (zh) 多流关联传输的方法、装置及系统
EP3744069B1 (en) Method and apparatus for handling user service profile information in a communications network implementing mobile edge computing (mec)
KR102233894B1 (ko) 네트워크 기능 장치 및 이를 이용한 요청 처리 방법
WO2023082878A1 (zh) 一种通信方法及装置
US20240049048A1 (en) Traffic engineering in 5g and lte cups architecture
WO2024032603A1 (zh) 一种通信方法及装置
WO2023071320A1 (zh) 一种保障语音业务的方法及通信装置
WO2022247875A1 (zh) 建立连接的方法、装置和系统
WO2023142726A1 (zh) 一种通信方法及装置
EP4354999A1 (en) Communication method, apparatus, and system
WO2023019998A1 (zh) 一种通信隧道管理方法、装置及系统
WO2024051313A1 (zh) 通信资源管理方法、装置、系统及存储介质
EP4274301A1 (en) Communication method and apparatus
KR102084144B1 (ko) 제어 평면 장치 및 이를 이용한 제어 평면 메시지 처리 방법
EP3406057A1 (en) Data sub-flow management
CN117478588A (zh) 高可用性冗余路由交换方法及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20884070

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020884070

Country of ref document: EP

Effective date: 20220506

NENP Non-entry into the national phase

Ref country code: DE