Communication method and communication device

By obtaining service usage and threshold generation indication information in network slices, controlling resource preemption and release, the problem of unreasonable resource use in network slices is solved, and intelligent resource management and priority guarantee of business data is achieved.

CN113162870BActive Publication Date: 2024-11-26HUAWEI TECH CO LTD
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202010014074.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-01-07
Publication Date
2024-11-26
Estimated Expiration
2040-01-07

AI Technical Summary

Technical Problem

In future communication technology, how to effectively control the service usage in network slices, ensure the reasonable allocation and use of resources, and avoid the problems of overload or insufficient resources.

Method used

The service usage and traffic threshold of the network slice are obtained through the first network device, indicating information is generated, and sent to the second network device to control resource preemption and release, and ensure that the service usage is within a reasonable range. Specific measures include generating indicator information based on the upper and lower limits of traffic volume, indicating whether resources can be preempted or released, and ensuring the reasonable use of resources for network slices.

Benefits of technology

It realizes intelligent control of network slice resources, avoids resource overload or insufficient resources, ensures the priority and quality of business data, and improves the utilization efficiency and reliability of network resources.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113162870B_ABST
    Figure CN113162870B_ABST
Patent Text Reader

Abstract

The present application provides a communication method and a communication device. The method includes: a first network device can generate indication information according to the service usage of a first network slice and the service volume threshold of the first network slice, and send the indication information to a second network device, and the second network device controls resource preemption according to the indication information, so that the second network device can control the service usage of the access network slice according to the indication information.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of communications, and more specifically, to a communication method and a communication device in the field of communications. Background Art

[0002] In future communication technologies, network slicing (NS) will be used to provide different network resources for different business data. A network slice is not able to provide unlimited network resources for one or more business types. Therefore, how to control the business usage within the network slice is an urgent problem to be solved. Summary of the invention

[0003] The present application provides a communication method and a communication device that can control the service data accessed by a network slice.

[0004] In a first aspect, a communication method is provided, including: a first network device obtains a service usage of a first network slice and a service volume threshold of the first network slice; the first network device generates indication information according to the service usage of the first network slice and the service volume threshold of the first network slice; the first network device sends the indication information to a second network device, and the indication information is used by the second network device to control resource preemption.

[0005] In the above technical solution, the first network device can generate indication information for the second network device to control resource preemption based on the service usage of the first network slice and the service volume threshold of the first network slice. In this way, the second network device can control the service usage of the access network slice based on the indication information.

[0006] Optionally, the first network device is a policy control function (PCF) network element, and the second network device is a radio access network (RAN) device.

[0007] Optionally, the first network device may determine the service usage of the first network slice and the service volume threshold of the first network slice by itself, or may obtain the service usage of the first network slice and the service volume threshold of the first network slice from other network devices.

[0008] In some possible implementations, the traffic threshold of the first network slice includes the traffic upper limit of the first network slice; if the traffic usage of the first network slice is greater than or equal to the traffic upper limit of the first network slice, the indication information is used to instruct the second network device to release resources used by traffic data that has already accessed the first network slice for the first traffic data to be accessed by the first network slice, or the indication information is used to indicate that the first traffic data to be accessed by the first network slice is prohibited from preempting resources used by data services that have already accessed other network slices, or the indication information is used to indicate that the allowed traffic usage of the first network slice is greater than or equal to the traffic upper limit of the first network slice.

[0009] In some possible implementations, if the service usage of the first network slice is greater than or equal to the service volume upper limit of the first network slice, the indication information is used to indicate that the service usage of the first network slice is greater than or equal to the service volume upper limit of the first network slice. Or the indication information is used to indicate that the second network device can release the service data that has already accessed the first network slice or release the resources used by the service data that has already accessed other network slices for the first service data to be accessed by the first network slice when resources are insufficient, that is, the first service data to be accessed by the first network slice is not prohibited from preempting the resources used by the data services that have already accessed other network slices.

[0010] In some possible implementations, the traffic volume upper limit of the first network slice is at least one of the maximum number of sessions allowed to access the first network slice or the maximum traffic bandwidth or the maximum session density allowed by the first network slice.

[0011] Specifically, when the service usage of the first network slice is the number of sessions that have accessed the first network slice, the upper limit of the service volume of the first network slice is the maximum number of sessions allowed to be accessed by the first network slice; when the service usage of the first network slice is the traffic bandwidth occupied by the service data that has accessed the first network slice, the upper limit of the service volume of the first network slice is the maximum traffic bandwidth allowed to be accessed by the first network slice; when the service usage of the first network slice is the density of sessions that have accessed the first network slice, the upper limit of the service volume of the first network slice is the maximum session density allowed by the first network slice.

[0012] In some possible implementations, the traffic volume threshold of the first network slice includes the traffic volume lower limit of the first network slice; if the traffic usage of the first network slice is less than or equal to the traffic volume lower limit of the first network slice, the indication information is used to indicate that the resources used by any service data that has accessed the first network slice are not preempted by any service data to be accessed by the second network slice, or the indication information is used to indicate that the traffic usage of the first network slice is less than or equal to the traffic volume lower limit of the first network slice.

[0013] In some possible implementations, if the service usage of the first network slice is greater than the service volume lower limit of the first network slice, the indication information is used to indicate that the resources used by the service data that has accessed the first network slice can be preempted by the service data to be accessed by the second network slice, or the indication information is used to indicate that the service usage of the first network slice is greater than the service volume lower limit of the first network slice.

[0014] In some possible implementations, the lower limit of the service volume of the first network slice is at least one of the minimum number of sessions or the minimum traffic bandwidth guaranteed by the first network slice for access or the minimum session density guaranteed by the first network slice.

[0015] Specifically, when the service usage of the first network slice is the number of sessions that have accessed the first network slice, the lower limit of the service volume of the first network slice is the minimum number of sessions guaranteed to access the first network slice; when the service usage of the first network slice is the traffic bandwidth occupied by the service data that has accessed the first network slice, the lower limit of the service volume of the first network slice is the minimum traffic bandwidth guaranteed to access the first network slice; when the service usage of the first network slice is the density of sessions that have accessed the first network slice, the lower limit of the service volume of the first network slice is the minimum session density guaranteed by the first network slice.

[0016] In some possible implementations, the method also includes: if the service usage of the first network slice is less than or equal to the lower limit of the service volume of the first network slice, the first network device sets the preemption willingness parameter in the allocation and retention priority ARP parameter of the first service data to not allow preemption, or the first network device sets the preemption opinion parameter in the ARP parameter of each service data that has connected to the first network slice to not allow preemption.

[0017] In some possible implementations, the traffic volume threshold of the first network slice includes a lower limit of the traffic volume of the first network slice and an upper limit of the traffic volume of the first network slice.

[0018] In some possible implementations, if the service usage of the first network slice is less than or equal to the service volume lower limit of the first network slice, the indication information is used to indicate that the resources used by the service data that has accessed the first network slice are not preempted by the service data to be accessed by the second network slice, or the indication information is used to indicate that the service usage of the first network slice is less than or equal to the service volume lower limit of the first network slice.

[0019] In some possible implementations, if the service usage of the first network slice is greater than the service volume lower limit of the first network slice and less than or equal to the service volume upper limit of the first network slice, the indication information is used to instruct the second network device to release the service data that has already accessed the first network slice or release the resources used by the service data that has already accessed other network slices for the first service data to be accessed by the first network slice, or the indication information is used to indicate that the service usage of the first network slice is greater than the service volume lower limit of the first network slice and less than the service volume upper limit of the first network slice.

[0020] In some possible implementations, if the service usage of the first network slice is greater than or equal to the service volume upper limit of the first network slice, the indication information is used to instruct the RAN to release resources used by service data that has already accessed the first network slice for the first service data to be accessed by the first network slice, or the indication information is used to indicate that the first service data to be accessed by the first network slice is prohibited from preempting resources used by data services that have already accessed other network slices, or the indication information is used to indicate that the service usage of the first network slice is greater than or equal to the service volume upper limit of the first network slice.

[0021] In some possible implementations, the service data to be accessed or already accessed to the first network slice is a service quality QoS flow or a packet data unit PDU session, or the service data to be accessed or already accessed to the second network slice is a service quality QoS flow or a packet data unit PDU session.

[0022] According to a second aspect, a communication method is provided, including: a second network device receives indication information from a first network device; the second network device releases resources used by second business data that has already accessed the first network slice for first business data to be accessed to the first network slice according to the indication information; or, the second network device prohibits resources used by business data that has already accessed the first network slice from being preempted by any business data to be accessed to the second network slice according to the indication information.

[0023] In the above technical solution, the second network device can determine whether to release the resources of the second service data that have been accessed in the first network slice for the first service data to be accessed according to the indication information, or determine whether to release the resources of the second service data in any network slice for the first service data to be accessed, so that the second network device can determine the released resources for the first service data to be accessed in the first network slice, so as to better control the resources of the first network slice.

[0024] In some possible implementations, the second network device releasing resources used by second service data that has already accessed the first network slice for first service data to be accessed the first network slice according to the indication information, including:

[0025] If the indication information indicates that the second network device releases resources used by business data that have already accessed the first network slice for first business data to be accessed by the first network slice, or the indication information indicates that the business usage of the first network slice is greater than or equal to the business volume upper limit of the first network slice, then the second network device releases resources used by second business data that have already accessed the first network slice for the first business data to be accessed by the first network slice.

[0026] In some possible implementations, the second network device releases resources used by second service data that has already accessed the first network slice for first service data to be accessed by the first network slice, including: the second network device determines, according to the indication information, that it is prohibited to preempt resources of service data that has already accessed network slices other than the first network slice for the first service data to be accessed by the first network slice; the second network device determines the second service data from the service data that has already accessed the first network slice according to authorized service quality QoS parameters of the first service data and the second service data, wherein the priority of the first service data is higher than that of the second service data, and the preemption capability parameter in the allocation and retention priority ARP parameter in the authorized service quality QoS parameter of the first service data is set to allow preemption, and the preemption willingness parameter in the ARP parameter in the authorized QoS parameter of the second service data is set to allow preemption.

[0027] In some possible implementations, if the resources of the second network device are less than a preset value, the second network device determines the second service data from the service data that has accessed the first network slice according to the authorized service quality QoS parameters of the first service data and the second service data. Less than the preset value means that the idle resources are less than a preset threshold, or the idle resources are less than the resources required to establish the first service data.

[0028] In some possible implementations, the traffic volume upper limit of the first network slice is at least one of the maximum number of sessions allowed to access the first network slice or the maximum traffic bandwidth or the maximum session density allowed by the first network slice.

[0029] In some possible implementations, the second network device prohibits resources used by any service data that has accessed the first network slice from being preempted by any service data to be accessed the second network slice according to the indication information, including:

[0030] If the indication information indicates that the resources used by any service data that has already accessed the first network slice by the second network device are not preempted by any service data to be accessed by the second network slice, or the service usage of the first network slice is less than or equal to the lower limit of the service volume of the first network slice, then the second network device prohibits the resources used by any service data that has already accessed the first network slice from being preempted by the second service data to be accessed by the second network slice.

[0031] In some possible implementations, the lower limit of the service volume of the first network slice is at least one of the minimum number of sessions or the minimum traffic bandwidth guaranteed by the first network slice for access or the minimum session density guaranteed by the first network slice.

[0032] In some possible implementations, if the second network device prohibits resources used by any service data that has accessed the first network slice from being preempted by any service data to be accessed to the second network slice according to the indication information, the method further includes:

[0033] The second network device sets the preemption willingness parameter in the allocation and retention priority ARP parameters of each service data that has accessed the first network slice to not allow preemption.

[0034] In some possible implementations, if the indication information is used to instruct the RAN to release the resources used by the service data that has already accessed the first network slice or the service data that has already accessed other network slices for the first service data to be accessed by the first network slice, or the indication information is used to indicate that the service usage of the first network slice is greater than the lower limit of the service volume of the first network slice and less than the upper limit of the service volume of the first network slice, the method further includes: the second network device releases the resources used by the service data that has already accessed the first network slice or the service data that has already accessed other network slices for the first service data to be accessed by the first network slice. In other words, the RAN can determine, based on the indication information, to allow the first service of the first network slice to preempt the resources used by the service data that has already accessed other network slices, and also allow the resources used by the service data that has already accessed the first network slice to be preempted by the service data to be accessed by other network slices.

[0035] In some possible implementations, the service data to be accessed or already accessed to the first network slice is a service quality QoS flow or a packet data unit PDU session, and the service data to be accessed or already accessed to the second network slice is a service quality QoS flow or a packet data unit PDU session.

[0036] According to a third aspect, a communication method is provided, including: a first network device obtains a service usage of a first network slice and a service volume threshold of the first network slice; the first network device determines whether to release second service data that has been connected to the first network slice and accept first service data to be connected to the first network slice according to the service usage of the first network slice and the service volume threshold of the first network slice.

[0037] In some possible implementations, the traffic volume threshold of the first network slice includes an upper limit of the traffic volume of the first network slice;

[0038] The first network device determines whether to release the second service data that has been accessed to the first network slice and accept the first service data to be accessed to the first network slice according to the service usage of the first network slice and the service volume threshold of the first network slice, including:

[0039] If the service usage of the first network slice is greater than or equal to the service volume upper limit of the first network slice, the first network device determines to release the second service data that has accessed the first network slice and accepts the first service data to be accessed the first network slice; or

[0040] If the service usage of the first network slice is less than the service volume upper limit of the first network slice, the first network device determines to accept the first service data to be accessed by the first network slice.

[0041] In some possible implementations, the traffic volume upper limit of the first network slice is at least one of the maximum number of sessions or the maximum traffic bandwidth allowed to access the first network slice or the maximum session density allowed by the first network slice.

[0042] In some possible implementations, the method further includes:

[0043] The first network device determines, based on the service quality parameters of the first service data and the second service data, to release the second service data that has accessed the first network slice and accept the first service data to be accessed the first network slice.

[0044] In some possible implementations, the first network device determines, according to the service quality parameters of the first service data and the second service data, to release the second service data that has accessed the first network slice and accept the first service data to be accessed the first network slice, including:

[0045] When the priority of the service quality parameters of the second service data is lower than the priority of the service quality parameters of the first service data, and the preemption intention in the service quality parameters of the second service data is to allow preemption, the first network device determines to release the second service data that has accessed the first network slice and accepts the first service data to be accessed the first network slice.

[0046] In some possible implementations, the method also includes: the first network device determines to release the second service data that has accessed the first network slice and accept the first service data to be accessed the first network slice based on at least one of the data network name DNN of the first service data and the second service data, the internal group identifier, the type of service data, the access network type, and the location of the terminal device.

[0047] In some possible implementations, the service data to be accessed or already accessed to the first network slice is a quality of service QoS flow or a packet data unit PDU session.

[0048] In a fourth aspect, a communication device is provided, which is used to execute the method in any possible implementation of the above aspects. Specifically, the device includes a unit for executing the method in any possible implementation of the above aspects.

[0049] In a fifth aspect, a communication device is provided, comprising a processor, which is coupled to a memory and can be used to execute instructions in the memory to implement the method in the first aspect or any possible implementation of the first aspect, or the method in the second aspect or any possible implementation of the second aspect, or the method in the third aspect or any possible implementation of the third aspect.

[0050] In a possible implementation, the device further includes a memory. In a possible implementation, the device further includes a communication interface, and the processor is coupled to the communication interface.

[0051] In one implementation, the device is a first network device. When the device is a first network device, the communication interface may be a transceiver, or an input / output interface.

[0052] In another implementation, the device is a chip configured in the first network device. When the device is a chip configured in the first network device, the communication interface may be an input / output interface.

[0053] In one implementation, the device is a second network device. When the device is a second network device, the communication interface may be a transceiver, or an input / output interface.

[0054] In another implementation, the device is a chip configured in the second network device. When the device is a chip configured in the second network device, the communication interface may be an input / output interface.

[0055] In a sixth aspect, a processor is provided, comprising: an input circuit, an output circuit and a processing circuit. The processing circuit is used to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor executes a method in any possible implementation of the above aspects.

[0056] In the specific implementation process, the above-mentioned processor can be a chip, the input circuit can be an input pin, the output circuit can be an output pin, and the processing circuit can be a transistor, a gate circuit, a trigger, and various logic circuits. The input signal received by the input circuit can be, for example, but not limited to, received and input by a receiver, and the signal output by the output circuit can be, for example, but not limited to, output to a transmitter and transmitted by the transmitter, and the input circuit and the output circuit can be the same circuit, which is used as an input circuit and an output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0057] In a seventh aspect, a device is provided, including a processor and a memory. The processor is used to read instructions stored in the memory, and can receive signals through a receiver and transmit signals through a transmitter to execute the method in any possible implementation of the above aspects.

[0058] In a possible implementation, there are one or more processors and one or more memories.

[0059] In a possible implementation, the memory may be integrated with the processor, or the memory may be separately provided with the processor.

[0060] In the specific implementation process, the memory can be a non-transitory memory, such as a read-only memory (ROM), which can be integrated with the processor on the same chip or can be set on different chips. This application does not limit the type of memory and the setting method of the memory and the processor.

[0061] It should be understood that the relevant data interaction process, such as sending indication information, can be a process of outputting indication information from a processor, and receiving capability information can be a process of receiving input capability information from a processor. Specifically, the processed output data can be output to a transmitter, and the input data received by the processor can come from a receiver. Among them, the transmitter and the receiver can be collectively referred to as a transceiver.

[0062] The above-mentioned device can be a chip, and the processor can be implemented by hardware or by software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor can be a general-purpose processor, which is implemented by reading software codes stored in a memory. The memory can be integrated in the processor or can be located outside the processor and exist independently.

[0063] In an eighth aspect, a computer program product is provided, which includes: a computer program (also referred to as code, or instruction), which, when executed, enables a computer to execute a method in any possible implementation of the above aspects.

[0064] In a ninth aspect, a computer-readable storage medium is provided, which stores a computer program (also referred to as code, or instruction) which, when executed on a computer, enables the computer to execute a method in any possible implementation of the above aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0065] Figure 1 It is a schematic diagram of the system architecture provided in an embodiment of the present application.

[0066] Figure 2-Figure 14 It is a schematic diagram of the communication method provided in an embodiment of the present application.

[0067] Figure 15-16 It is a schematic block diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0068] The technical solution in this application will be described below in conjunction with the accompanying drawings.

[0069] The technical solutions of the embodiments of the present application can be applied to various communication systems, for example: global system for mobile communications (GSM) system, code division multiple access (CDMA) system, wideband code division multiple access (WCDMA) system, general packet radio service (GPRS), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) communication system, future fifth generation (5G) system or new radio (NR), etc.

[0070] Figure 1 A schematic diagram of a system architecture applied to an embodiment of the present application is shown. Figure 1As shown, the system 100 includes: PCF 101, unified data repository (UDR) 102, unified data management (UDM) 103, network data analysis function (NWDAF) 104, network repository function (NRF) 105, network slice selection function (NSSF) network element 106, session management function network element (SMF) 107, user plane function network element (UPF) 108, core access and mobility management function (AMF) 109, data network (DN) 110, RAN 111 or at least one of user equipment (UE) 112.

[0071] Among them, PCF 101 includes user subscription data management function, policy control function, charging policy control function, quality of service (QoS) control, etc.

[0072] UDR 102 is responsible for storing structured data information, wherein the data information includes contract information, policy information, and network data or service data defined in a standard format.

[0073] UDM 103 is responsible for managing the subscription information of UE 112.

[0074] NWDAF 104 can collect data from various network functions (NF), such as PCF 101, SMF 107, UPF 108, AMF 109, etc., and perform analysis and prediction.

[0075] NRF 105 is responsible for providing storage and selection functions of network function entity information for other network elements.

[0076] NSSF 106 selects a suitable network slice for UE 112's service data.

[0077] SMF 107 is responsible for the selection or reselection of UPF, IP address allocation, session establishment, modification and release, and QoS control.

[0078] UPF 108 is mainly responsible for processing service data, such as forwarding, billing, legal interception, etc. UPF 108 may also be called a protocol data unit (PDU) session anchor (PSA).

[0079] AMF 109 is mainly used for the attachment, mobility management, and tracking area update processes of UE 112 in the mobile network. The access management network element terminates the non-access stratum (NAS) message, completes registration management, connection management, and reachability management, allocates the tracking area list (TA list) and mobility management, and transparently routes the session management (SM) message to the session management network element.

[0080] DN 110 provides data transmission services for UE 112 and may be a public data network (PDN) such as the Internet.

[0081] RAN 111 may be a device that communicates with UE 112. The RAN 111 may also be referred to as an access network device or a wireless access network device. It may be a transmission reception point (TRP), an evolved NodeB (eNB or eNodeB) in an LTE system, a home base station (for example, homeevolved NodeB, or home Node B, HNB), a baseband unit (BBU), or a wireless controller in a cloud radio access network (CRAN) scenario. The RAN 111 may be a relay station, an access point, a vehicle-mounted device, a wearable device, a network device in a 5G network, or a network device in a future evolved PLMN network, etc. It may also be an access point (AP) in a WLAN, or a gNB in ​​an NR system. The RAN 111 may also be a city base station, a micro base station, a micro-micro base station, a micro-micro base station, etc., and this application does not limit this.

[0082] In one network structure, RAN 111 may include a centralized unit (CU) node, a distributed unit (DU) node, or a radio access network (RAN) device including a CU node and a DU node, or a device including a control plane CU node (CU-CP node) and a user plane CU node (CU-UP node) and a DU node.

[0083] RAN 111 provides services for the cell, and UE 112 communicates with the cell through the transmission resources (for example, frequency domain resources, or spectrum resources) allocated by RAN 111. The cell may belong to a macro base station (for example, macro eNB or macro gNB, etc.), or to a base station corresponding to a small cell. The small cells here may include: metro cell, micro cell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0084] UE 112, also known as terminal equipment, mobile station (MS), mobile terminal (MT), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user device, etc.

[0085] UE 112 may be a device that provides voice / data connectivity to a user, such as a handheld device or a vehicle-mounted device with a wireless connection function. At present, some examples of terminal devices include: mobile phones, tablet computers, laptop computers, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication functions, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in 5G networks or future evolved public land mobile communication networks (public land mobile The present application does not limit the terminal equipment in the network, PLMN, etc.

[0086] It should be noted that Figure 1 The naming of each network element included in (such as SMF 107, PCF101, RAN 111, UPF 108, NSSF 106, etc.) is only a name, and the name does not limit the function of the network element itself. In 5G networks and other future networks, the above-mentioned network elements may also have other names, and the embodiments of the present application do not specifically limit this. For example, in a 6G network, some or all of the above-mentioned network elements may use the terminology in 5G, or may be other names, etc., which are uniformly explained here and will not be repeated below.

[0087] It should be noted that Figure 1 The network elements in the network do not have to exist at the same time, and the required network elements can be determined based on the needs. Figure 1 The connection relationship between each network element in the network is not uniquely determined and can be adjusted according to needs.

[0088] To facilitate understanding of the embodiments of the present application, the terms involved in the present application are first briefly explained.

[0089] 1. Network Slicing

[0090] A network slice is an end-to-end logical private network that provides specific network capabilities. Through flexible allocation of network resources and on-demand networking, multiple logical subnets with different characteristics and isolation can be virtualized on the same set of physical facilities to provide targeted services to users. This logical subnet is called a network slice. Network slices can be used by operators to provide isolated and customizable network services for different vertical industries, different customers, and different businesses based on the service level agreement (SLA) signed by customers. Different network slices can be identified and distinguished by single network slice selection assistance information (S-NSSAI).

[0091] It should be noted that the above Figure 1 The network functions such as NSSF 106, NRF 105, NWDAF 104, UDM 103, UDR 102, AMF 109, etc. can be shared by multiple network slices, SMF 107 and UPF 108 can belong to a specific network slice. RAN 111 can also be shared by multiple network slices.

[0092] 2. QoS parameters

[0093] QoS parameters include 5G QoS Identifier (5QI), allocation and retention priority (ARP), flow bit rates (FBR), aggregate bit rates (ABR) and other parameters. Among them, 5QI is used to identify the characteristics of service data. FBR is valid for service data with guaranteed bit rate, including guaranteed flow bit rate (GFBR) and maximum flow bit rate (MFBR). ABR is valid for service data with non-guaranteed bit rate, including session aggregate maximum bit rate (session-AMBR) and terminal aggregate maximum bit rate (UE aggregate maximum bit rate, UE-AMBR).

[0094] 3. Allocation and retention priority (ARP) parameters

[0095] ARP parameters are the priority information of service data specified when establishing or modifying service data requests, including priority level (ARP-PL) parameter, preemption capability (ARP-PE_C) parameter, and preemption vulnerability (ARP-PE_V) parameter. ARP-PL indicates the priority of service data in the case of insufficient resources, which can be an integer. Different values ​​represent different priorities, for example, a smaller value has a higher priority; ARP-PE_C is used to indicate whether resources of other low-priority service data can be preempted when resources are insufficient; ARP-PE_V parameter is used to indicate whether the resources occupied by service data are allowed to be released and preempted by high-priority service data when resources are insufficient.

[0096] In the prior art, the capacity of a network slice is limited. If a certain current service data is to be accessed to a network slice, resources within the network slice or outside the network slice can be preempted for the service data. However, it is possible that the user has purchased a network slice with a fixed resource size from the operator. If the resources occupied by the service data that has been accessed to the network slice have reached the upper limit of the resources of the purchased network slice, if the resources of other network slices continue to be preempted for the service data, the preempted resources will result in more resources than the resources of the network slice actually purchased by the user, because the resource planning of the network slice will be inconsistent with the tariff, thereby affecting the feasibility of planning the resources of the network slice.

[0097] The communication method provided in the embodiment of the present application is described below by taking the first network device as PCF 101 and the second network device as RAN 111 as an example, but the embodiment of the present application is not limited thereto. For the convenience of description below, the network element number is omitted, for example, "PCF" represents "PCF 101" and "RAN" represents "RAN 111".

[0098] Combine the following Figure 2 The communication method 200 mentioned in the embodiment of the present application is described.

[0099] S210, PCF obtains the service usage of the first network slice and the service volume upper limit of the first network slice.

[0100] Optionally, the PCF may determine the service usage of the first network slice and the upper limit of the service volume of the first network slice by itself. Optionally, the PCF may obtain the service volume of the first network slice and the upper limit of the service volume of the first network slice from other network elements, for example, the PCF obtains the upper limit of the service volume of the first network slice from the UDR / UDM, or the PCF obtains the upper limit of the service volume of the first network slice sent by OAM through the UDR / UDM; for another example, the PCF may obtain the service volume of the first network slice from the UDR.

[0101] Optionally, the service usage of the first network slice may be the number of sessions that have accessed the first network slice, or the traffic bandwidth occupied by service data that have accessed the first network slice, or the density of sessions that have accessed the first network slice. The service volume threshold of the first network slice may include an upper limit on the service volume of the first network slice.

[0102] Specifically, when the service usage of the first network slice is the number of sessions that have accessed the first network slice, the upper limit of the service volume of the first network slice is the maximum number of sessions allowed to be accessed by the first network slice; when the service usage of the first network slice is the traffic bandwidth occupied by the service data that has accessed the first network slice, the upper limit of the service volume of the first network slice is the maximum traffic bandwidth allowed to be accessed by the first network slice; when the service usage of the first network slice is the density of sessions that have accessed the first network slice, the upper limit of the service volume of the first network slice is the maximum session density allowed by the first network slice.

[0103] like Figure 1 As shown, the service area of ​​the first network slice may include one or more RANs. Each RAN has a certain coverage area, which may be one or more cells. In addition, the service area of ​​the first network slice may also include the service area of ​​the UPF, especially some UPFs deployed at the mobile edge computing (MEC) location, and the size of the service area of ​​the UPF is the area covered by one or several gNBs. The service area of ​​the first network slice may be composed of at least one cell, and / or at least one UPF service area, and the ratio of the sessions that have been accessed to the service area of ​​the first network slice to the area of ​​the service area of ​​the first network slice can be understood as the density of the sessions that have been accessed to the first network slice. Accordingly, the traffic threshold of the first network slice is the maximum allowed value of the ratio of the sessions that have been accessed to the area of ​​the service area of ​​the first network slice.

[0104] S220, PCF generates indication information based on the service usage of the first network slice and the service volume upper limit of the first network slice.

[0105] S220 is described below in four cases.

[0106] In case one, if the service usage of the first network slice is greater than or equal to the service volume upper limit of the first network slice, the indication information is used to instruct the RAN to release the resources used by the service data that has already accessed the first network slice for the first service data to be accessed by the first network slice. In other words, the indication information is used to indicate that the first service data to be accessed by the first network slice is prohibited from preempting the resources used by the data services that have already accessed other network slices.

[0107] Case 2: If the service usage of the first network slice is greater than or equal to the service volume upper limit of the first network slice, the indication information is used to indicate that the service usage of the first network slice is greater than or equal to the service volume upper limit of the first network slice.

[0108] Case three, if the service usage of the first network slice is less than the service volume upper limit of the first network slice, the indication information is used to indicate that when resources are insufficient, the RAN can release the service data that has already accessed the first network slice or release the resources used by the service data that has already accessed other network slices for the first service data to be accessed by the first network slice, that is, the first service data to be accessed by the first network slice is not prohibited from preempting the resources used by the data services that have already accessed other network slices. In other words, the first service data to be accessed by the first network slice can preempt the resources used by the data services that have already accessed other network slices or can also preempt the resources used by the service data that has already accessed the first network slice.

[0109] It should be noted that when the indication information is used to indicate that the service usage of the first network slice is equal to the service volume upper limit of the first network slice, it can be implemented according to situation one or situation three.

[0110] Case four: if the service usage of the first network slice is less than the service volume upper limit of the first network slice, the indication information is used to indicate that the service usage of the first network slice is less than the service volume upper limit of the first network slice.

[0111] S230, the PCF sends indication information to the RAN, and the RAN receives the indication information sent by the PCF.

[0112] Optionally, S230 may include: the PCF directly sends the indication information to the RAN, and the RAN directly receives the indication information sent by the PCF. Optionally, S230 may include: the PCF may send the indication information to the RAN through other network elements, and the RAN may receive the indication information sent by the PCF through other network elements. For example, the PCF may send the indication information to the RAN through the SMF and / or AMF, and the RAN may receive the indication information sent by the PCF through the SMF and / or AMF.

[0113] S240, RAN controls the release of resources used by second service data that have already accessed the first network slice for first service data to be accessed according to the indication information; or, RAN controls the release of resources used by second service data that have already accessed the first network slice or releases resources used by service data that have already accessed other network slices for first service data to be accessed according to the indication information.

[0114] S240 is described below in four cases.

[0115] Case 1, in case 220, S240 includes: RAN can directly determine, according to the indication information, to release resources used by second service data that has already accessed the first network slice for first service data to be accessed the first network slice. In other words, it can be determined, according to the indication information, that resources used by data services that have already accessed other network slices are prohibited from being preempted by first service data to be accessed the first network slice.

[0116] Case 2, in case 2 of S220, S240, includes: RAN can determine, based on the indication information, that the service usage of the first network slice has reached the service usage upper limit of the first network slice. Therefore, RAN can release the resources used by the second service data that has already accessed the first network slice for the first service data to be accessed.

[0117] Case 3, in case 3 of S220, S240, including: RAN can directly determine, based on the indication information, to release the service data that has already accessed the first network slice or release the resources used by the service data that has already accessed other network slices for the first service data to be accessed the first network slice. In other words, RAN determines, based on the indication information, that it does not prohibit the first service data to be accessed the first network slice from preempting the resources used by the data service that has already accessed other network slices.

[0118] Case four, under case four of S220, S240, including: RAN can determine based on the indication information that the service usage of the first network slice has not reached the service volume upper limit of the first network slice, and RAN can determine based on the indication information to release the service data that has already accessed the first network slice or release the resources used by the service data that has already accessed other network slices for the first service data to be accessed. In this way, when the service usage of the first network slice has not reached the service volume upper limit of the first network slice, RAN can release the resources of the service data in any network slice for the first service data to be currently accessed.

[0119] As an optional embodiment, S240 includes: the RAN determines, based on the indication information received in S230, that the first service data to be accessed to the first network slice should seize resources of the service data in the first network slice or that the first service data to be accessed should seize resources of the service data already accessed in any network slice; if the RAN determines that the current available resources of the RAN are insufficient, for example, the current available resources are less than or equal to the preset value, the RAN needs to determine, based on the QoS parameters of the first service data to be accessed and the service data already accessed to the first network slice or other network slices, which service data resources already accessed to the first network slice should be released for the first service data to be accessed to the first network slice. For example, if the service data to be accessed to the first network slice and the service data already accessed to the first network slice or other network slices are PDU sessions, then it can be determined, based on the ARP-PE-C and ARP-PL in the contracted default QoS parameters of the newly established PDU session or the default QoS parameters to be authorized and the ARP-PE-V and ARP-PL in the authorized default QoS parameters of the established PDU session, which service data used by the service data already accessed to the first network slice should be released for the first service data to be accessed to the first network slice. For another example, if the service data to be accessed to the first network slice and the service data that have been accessed to the first network slice or other network slices are QoS Flows, then it can be determined which service data that has been accessed to the first network slice or other network slices should release resources for the first service data to be accessed to the first network slice based on the ARP-PE-C and ARP-PL in the authorized QoS parameters of the newly established or modified QoS Flow and the ARP-PE-V and ARP-PL in the authorized QoS parameters of the established QoS Flow. The following discusses the following situations:

[0120] a) If the priority of the first service data to be accessed to the first network slice is lower than or equal to the priority of any service data that has been accessed to the first network slice or is lower than the priority of any service data that has been accessed to other network slices, for example, the ARP-PL value of the first service data to be accessed to the first network slice is greater than the ARP-PL value of any service data that has been accessed to the first network slice or is greater than the ARP-PL value of any service data that has been accessed to other network slices (the smaller the ARP-PL value, the higher the priority), then RAN determines that it is forbidden to release any service data resources for the first service data to be accessed to the first network slice; if the ARP-PE_C of the first service data to be accessed to the first network slice is set to not allow preemption, then RAN determines that it is forbidden to release any service data resources for the first service data to be accessed to the first network slice. The first service data to be accessed to the first network slice is terminated because RAN cannot allocate resources.

[0121] b) If the priority of the first service data to be accessed to the first network slice is higher than the priority of the second service data that has already been accessed to the first network slice or higher than the priority of the second service data that has already been accessed to other networks, for example, the ARP-PL value of the second service data is greater than the ARP-PL value of the first service data to be accessed to the first network slice (the smaller the ARP-PL value, the higher the priority), and the ARP-PE_C of the first service data is set to allow preemption, and the ARP-PE_V of the second service data is set to allow preemption, then the RAN determines that the first service data to be accessed to the first network slice releases the resources of the second service data that has already been accessed to the first network slice or other network slices.

[0122] Therefore, in the above method 200, the PCF can determine the indication information based on the service usage of the first network slice and the upper limit of the service volume of the first network slice, so that the RAN can determine whether to release the resources of the second service data that has been accessed in the first network slice for the first service data of the first network slice to be accessed, or determine whether to release the resources of the second service data in any network slice for the first service data of the first network slice to be accessed, so that the RAN can determine the released resources for the first service data of the first network slice to be accessed, so as to better control the resources of the first network slice. In addition, while accessing high-priority or important data services as much as possible, ensure that the resources of the first network slice do not exceed the upper limit.

[0123] Combine the following Figure 3 The communication method 300 mentioned in the embodiment of the present application is described.

[0124] S310, PCF obtains the service usage of the first network slice and the lower limit of the service volume of the first network slice.

[0125] Optionally, the PCF may determine the service usage of the first network slice and the lower limit of the service volume of the first network slice by itself. Optionally, the PCF may obtain the service volume of the first network slice and the lower limit of the service volume of the first network slice from other network elements, for example, the PCF obtains the lower limit of the service volume of the first network slice from the UDR / UDM, or the PCF obtains the lower limit of the service volume of the first network slice sent by OAM through the UDR / UDM; for another example, the PCF may obtain the service volume of the first network slice from the UDR.

[0126] Optionally, the service usage of the first network slice may be the number of sessions that have accessed the first network slice, or the traffic bandwidth occupied by service data that have accessed the first network slice, or the density of sessions that have accessed the first network slice. The service volume threshold of the first network slice may include a lower limit for the service volume of the first network slice.

[0127] Specifically, when the service usage of the first network slice is the number of sessions that have accessed the first network slice, the lower limit of the service volume of the first network slice is the minimum number of sessions guaranteed to access the first network slice; when the service usage of the first network slice is the traffic bandwidth occupied by the service data that has accessed the first network slice, the lower limit of the service volume of the first network slice is the minimum traffic bandwidth guaranteed to access the first network slice; when the service usage of the first network slice is the density of sessions that have accessed the first network slice, the lower limit of the service volume of the first network slice is the minimum session density guaranteed by the first network slice.

[0128] S320, PCF generates indication information based on the service usage of the first network slice and the lower limit of the service volume of the first network slice.

[0129] S320 is described below in four cases.

[0130] Case 1: If the service usage of the first network slice is less than or equal to the lower limit of the service volume of the first network slice, the indication information is used to indicate that the resources used by the service data that has accessed the first network slice will not be preempted by the service data to be accessed by the second network slice.

[0131] Case 2: If the service usage of the first network slice is less than or equal to the lower limit of the service volume of the first network slice, the indication information is used to indicate that the service usage of the first network slice is less than or equal to the lower limit of the service volume of the first network slice.

[0132] Case three: if the service usage of the first network slice is greater than the lower limit of the service volume of the first network slice, the indication information is used to indicate that the resources used by the service data that has accessed the first network slice can be preempted by the service data to be accessed by the second network slice.

[0133] Similarly, when the service usage of the first network slice is equal to the lower limit of the service volume of the first network slice, it can be achieved through situation one or situation three.

[0134] Case four: if the service usage of the first network slice is greater than the lower limit of the service volume of the first network slice, the indication information is used to indicate that the service usage of the first network slice is greater than the lower limit of the service volume of the first network slice.

[0135] S330, the PCF sends indication information to the RAN, and the RAN receives the indication information sent by the PCF.

[0136] Optionally, S330 may include: the PCF directly sends the indication information to the RAN, and the RAN directly receives the indication information sent by the PCF. Optionally, S330 may include: the PCF may send the indication information to the RAN through other network elements, and the RAN receives the indication information sent by the PCF through other network elements. For example, the PCF may send the indication information to the RAN through the SMF and / or AMF, and the RAN receives the indication information sent by the PCF through the SMF and / or AMF.

[0137] S340, RAN prohibits the resources used by the service data that has already accessed the first network slice from being preempted by the service data to be accessed to the second network slice, or the resources used by the service data that has already accessed the first network slice can be preempted by the service data to be accessed to the second network slice according to the indication information.

[0138] S340 is described below in two cases.

[0139] Case 1, in case S320, S340, including: RAN can directly determine based on the indication information that resources used by service data that has already accessed the first network slice are prohibited from being preempted by service data to be accessed the second network slice.

[0140] Case 2, in case 2 of S320, S340, includes: RAN can determine based on the indication information that the service usage of the first network slice has not reached the lower limit of the service volume of the first network slice. In order to ensure the minimum guaranteed usage of the first network service, RAN prohibits the resources used by any service data that has accessed the first network slice from being preempted by the service data to be accessed by the second network slice.

[0141] Case three, in case three of S320, S340, includes: RAN can directly determine based on the indication information that the resources used by any service data that has already accessed the first network slice can be preempted by the service data to be accessed the second network slice.

[0142] Case four, under case four of S320, S340, includes: RAN can determine based on the indication information that the service usage of the first network slice has reached the lower limit of the service volume of the first network slice, and RAN can determine based on the indication information that the resources used by the service data that has accessed the first network slice can be preempted by the service data to be accessed the second network slice.

[0143] In case 1 and case 2 of S340, if RAN can determine based on the indication information that resources used by service data that has already accessed the first network slice are prohibited from being preempted by service data to be accessed the second network slice, RAN sets the preemption willingness parameter in the ARP parameter of each service data that has already accessed the first network slice to not allow preemption, or RAN marks the first network slice as not allowing preemption, that is, the resources of any service data that has already accessed the first network slice are not allowed to be preempted and released.

[0144] Therefore, in the above method 300, the PCF can determine the indication information based on the service usage of the first network slice and the lower limit of the service volume of the first network slice, so that the RAN can determine the minimum service usage to ensure the first network slice based on the indication information, thereby enabling the RAN to control the resources of the first network slice.

[0145] Combine the following Figure 4 The communication method 400 mentioned in the embodiment of the present application is described.

[0146] S410, PCF obtains the service usage of the first network slice, the lower limit of the service volume of the first network slice, and the upper limit of the service volume of the first network slice.

[0147] Optionally, the PCF can determine the service usage of the first network slice, the lower limit of the service volume of the first network slice, and the upper limit of the service volume of the first network slice by itself. Optionally, the PCF can obtain the service volume of the first network slice, the lower limit of the service volume of the first network slice, and the upper limit of the service volume of the first network slice from other network elements. For example, the PCF obtains the service volume of the first network slice and the lower limit of the service volume of the first network slice from the UDR / UDM; for another example, the PCF can obtain the service volume of the first network slice from the UDR.

[0148] Optionally, the service usage of the first network slice may be the number of sessions that have accessed the first network slice, or the traffic bandwidth occupied by the service data that have accessed the first network slice, or the density of the sessions that have accessed the first network slice. The service volume threshold of the first network slice may include a lower limit of the service volume of the first network slice and an upper limit of the service volume of the first network slice.

[0149] Specifically, when the service usage of the first network slice is the number of sessions that have accessed the first network slice, the upper limit of the service volume of the first network slice is the maximum number of sessions allowed to access the first network slice, and the lower limit of the service volume of the first network slice is the minimum number of sessions guaranteed to access the first network slice; when the service usage of the first network slice is the traffic bandwidth occupied by the service data that has accessed the first network slice, the lower limit of the service volume of the first network slice is the minimum traffic bandwidth guaranteed to access the first network slice, and the upper limit of the service volume of the first network slice is the maximum traffic bandwidth allowed to access the first network slice; when the service usage of the first network slice is the density of sessions that have accessed the first network slice, the lower limit of the service volume of the first network slice is the minimum session density guaranteed by the first network slice, and the upper limit of the service volume of the first network slice is the maximum session density allowed by the first network slice.

[0150] S420, PCF generates indication information based on the service usage of the first network slice, the lower limit of the service volume of the first network slice, and the upper limit of the service volume of the first network slice.

[0151] S420 is described below in six cases.

[0152] Case 1: If the service usage of the first network slice is less than or equal to the lower limit of the service volume of the first network slice, the indication information is used to indicate that the resources used by the service data that has accessed the first network slice will not be preempted by the service data to be accessed by the second network slice.

[0153] Case 2: If the service usage of the first network slice is less than or equal to the lower limit of the service volume of the first network slice, the indication information is used to indicate that the service usage of the first network slice is less than or equal to the lower limit of the service volume of the first network slice.

[0154] Case three: if the service usage of the first network slice is greater than the lower limit of the service volume of the first network slice and less than or equal to the upper limit of the service volume of the first network slice, the indication information is used to instruct the RAN to release the service data that has already accessed the first network slice or release the resources used by the service data that has already accessed other network slices for the first service data to be accessed by the first network slice.

[0155] Case four: if the service usage of the first network slice is greater than the lower limit of the service volume of the first network slice and less than the upper limit of the service volume of the first network slice, the indication information is used to indicate that the service usage of the first network slice is greater than the lower limit of the service volume of the first network slice and less than the upper limit of the service volume of the first network slice.

[0156] Case five: If the service usage of the first network slice is greater than or equal to the service volume upper limit of the first network slice, the indication information is used to instruct the RAN to release the resources used by the service data that has already accessed the first network slice for the first service data to be accessed by the first network slice, or the indication information is used to instruct the first service data to be accessed by the first network slice to preempt the resources used by the data services that have already accessed other network slices.

[0157] Similarly, if the service usage of the first network slice is equal to the service volume upper limit of the first network slice, it may correspond to situation one, situation three, or situation five.

[0158] Case six: If the service usage of the first network slice is greater than or equal to the service volume upper limit of the first network slice, the indication information is used to indicate that the service usage of the first network slice is greater than or equal to the service volume upper limit of the first network slice.

[0159] S430, the PCF sends indication information to the RAN, and the RAN receives the indication information sent by the PCF.

[0160] Optionally, S430 may include: the PCF directly sends the indication information to the RAN, and the RAN directly receives the indication information sent by the PCF. Optionally, S430 may include: the PCF may send the indication information to the RAN through other network elements, and the RAN receives the indication information sent by the PCF through other network elements. For example, the PCF may send the indication information to the RAN through the SMF and / or AMF, and the RAN receives the indication information sent by the PCF through the SMF and / or AMF.

[0161] S440, RAN controls resource preemption according to the instruction information.

[0162] S440 is described below in six cases.

[0163] Case 1, in case S420, S440, includes: RAN can directly determine based on the indication information that the resources used by any service data that has accessed the first network slice are prohibited from being preempted by any service data to be accessed the second network slice.

[0164] Case 2, in case 2 of S420, S440, includes: RAN can determine based on the indication information that the service usage of the first network slice has not reached the lower limit of the service volume of the first network slice. In order to ensure the minimum guaranteed usage of the first network service, RAN prohibits the resources used by any service data that has accessed the first network slice from being preempted by any service data to be accessed by the second network slice.

[0165] Case 3, in case 3 of S420, S440, including: RAN can directly determine, based on the indication information, to release the service data that has already accessed the first network slice or release the resources used by the service data that has already accessed other network slices for the first service data to be accessed the first network slice. In other words, RAN can determine, based on the indication information, to allow the first service of the first network slice to preempt the resources used by the service data that has already accessed other network slices, and also allow the resources used by the service data that has already accessed the first network slice to be preempted by the service data to be accessed other network slices.

[0166] Case 4, under case 4 of S420, S440, including: RAN can determine, based on the indication information, that the service usage of the first network slice has not reached the upper limit of the service volume of the first network slice but has reached the lower limit of the service volume of the first network slice, and RAN can determine, based on the indication information, to release the service data that has already accessed the first network slice or release the resources used by the service data that has already accessed other network slices for the first service data to be accessed by the first network slice. In other words, RAN can determine, based on the indication information, to allow the first service of the first network slice to preempt the resources used by the service data that has already accessed other network slices, and also allow the resources used by the service data that has already accessed the first network slice to be preempted by the service data to be accessed by other network slices.

[0167] Case five, under case five of S420, S440, includes: RAN can directly determine, based on the indication information, to release the resources used by the second service data that has already accessed the first network slice for the first service data to be accessed the first network slice. In other words, RAN can determine, based on the indication information, to prohibit the first service data to be accessed the first network slice from preempting the resources used by the service data that has already accessed other network slices.

[0168] Case six, in case six of S420, S440, includes: RAN can determine, based on the indication information, that the service usage of the first network slice has reached the service volume upper limit of the first network slice. Therefore, RAN may need to release the resources used by the second service data that has already accessed the first network slice for the first service data to be accessed to the first network slice. In other words, RAN can determine, based on the indication information, that the first service data to be accessed to the first network slice is prohibited from preempting the resources used by the service data that has already accessed other network slices.

[0169] In case 1 and case 2 of S440, if RAN can determine based on the indication information that resources used by service data that has already accessed the first network slice are prohibited from being preempted by service data to be accessed the second network slice, RAN sets the preemption willingness parameter in the ARP parameter of each service data that has already accessed the first network slice to not allow preemption, or RAN marks the first network slice as not allowing preemption, that is, the resources of any service data that has already accessed the first network slice are not allowed to be released.

[0170] In case 5 and case 6 of S440, the service usage of the first network slice reaches the upper limit. Even if the resources of the RAN are sufficient, it is necessary to determine to preempt the resources of the service data in the first network slice for the first service data to be accessed to the first network slice. For which service data resources in the first network slice are preempted, refer to the description of method 200. In order to avoid redundancy, it is not described in detail here.

[0171] In case 3 to case 6 of S440, when the currently available resources of the RAN are insufficient (that is, the currently available resources are less than the preset threshold, or the currently available resources are less than the resources required for the first service data to be accessed), it is necessary to determine whether to preempt the resources of the service data in the first network slice for the first service data to be accessed, or to preempt the resources of the service data that has been accessed in any network slice for the first service data to be accessed. For specific information on which service data resources in the first network slice or other network slices should be preempted, please refer to the description of method 200. In order to avoid repetition, it is not described in detail here.

[0172] Therefore, in the above method 400, the PCF can determine the indication information based on the service usage of the first network slice, the lower limit of the service volume of the first network slice, and the upper limit of the service volume of the first network slice, so that the RAN can determine the minimum guaranteed service usage of the first network slice and the maximum allowed service usage of the first network slice based on the indication information. When the service usage of the first network slice reaches or exceeds the upper limit of the service volume of the first network slice, regardless of whether the resources of the RAN are sufficient, the RAN controls the release of resources of the service data that has already accessed the first network slice for the first service data to be accessed, and cannot preempt the resources of network slices other than the first network slice for the first service data to be accessed, thereby ensuring that the preempted resources do not exceed the upper limit of the resources of the first network slice. When the service usage of the first network slice is greater than the lower limit of the service volume of the first network slice but does not reach or exceed the upper limit of the service volume of the first network slice, the RAN can release the resources used by the service data that has already accessed any network slice that exceeds the lower limit of the service volume for the first service data to be accessed.

[0173] In the above-mentioned methods 200, 300 and 400, the PCF generates indication information and sends the indication information to the RAN, and the RAN controls resource preemption according to the indication information. The method 500 described below is that the PCF controls whether to release the second service data that has accessed the first network slice and accept the first service data to be accessed to the first network slice.

[0174] S510, PCF obtains the service usage of the first network slice and the service volume upper limit of the first network slice.

[0175] Optionally, the PCF may determine the service usage of the first network slice and the upper limit of the service volume of the first network slice by itself. Optionally, the PCF may obtain the service volume of the first network slice and the upper limit of the service volume of the first network slice from other network elements, for example, the PCF obtains the upper limit of the service volume of the first network slice from the UDR / UDM, or the PCF obtains the upper limit of the service volume of the first network slice sent by OAM through the UDR / UDM; for another example, the PCF may obtain the service volume of the first network slice from the UDR.

[0176] Specifically, the description of the service usage of the first network slice and the service volume upper limit of the first network slice refers to the description of method 200

[0177] S520, PCF determines whether to release the second service data that has accessed the first network slice and accept the first service data of the first network slice to be accessed based on the service usage of the first network slice and the service volume threshold of the first network slice.

[0178] S520 can be discussed in two cases.

[0179] Case 1, S520, includes: if the service usage of the first network slice is greater than or equal to the service volume upper limit of the first network slice, the PCF determines to release the service data that has accessed the first network slice and accepts the first service data to be accessed by the first network slice.

[0180] In case 1, if the PCF determines to release the service data that has accessed the first network slice and accept the first service data to be accessed to the first network slice, the PCF needs to determine which service data that has accessed the first network slice to release. The service data that has accessed the first network slice to release can be determined in at least one of the following ways:

[0181] a) PCF determines to release the second service data in the service data that has been connected to the first network slice and accept the first service data to be connected to the first network slice according to the service quality parameters of the service data that has been connected to the first network slice and the service quality parameters of the first service data to be connected to the first network slice. Specifically, the priority (i.e., ARP-PE-PL parameter) of the service data that has been connected to the first network slice is determined according to the authorized default service quality parameter (authorized default QoS) of the service data that has been connected to the first network slice, and is compared with the priority (i.e., ARP-PE-PL parameter) in the subscribed default service quality parameter (subscribed default QoS) or the authorized default service quality parameter of the first service data. If the priority of the second service data that has been connected to the first network slice is lower than the priority of the first service data, and the preemption intention in the service quality parameter of the second service data is to allow preemption, it is determined to release the second service data that has been connected to the first network slice and accept the first service data to be connected to the first network slice. Alternatively, according to the case where the service quality parameters of the service data that has already accessed the first network slice have a preemption intention that allows preemption, if there is a second service data that has already accessed the first network slice and the service quality parameters of the service data have a preemption intention that allows preemption, and the priority in the service quality parameters of the second service data is lower than the priority in the service quality parameters of the first service data, the PCF determines to release the second service data that has already accessed the first network slice and accept the first service data to be accessed the first network slice.

[0182] b), PCF determines to release the second service data in the service data that has been connected to the first network slice and accepts the first service data to be connected to the first network slice according to the (data network name, DNN) of the service data that has been connected to the first network slice and the DNN of the first service data to be connected to the first network slice. Specifically, PCF determines the destination network of the first service data according to the DNN of the first service data to be connected to the first network slice, determines the destination network of the service data that has been connected to the first network slice according to the DNN of the service data that has been connected to the first network slice, and determines the second service data whose importance of the destination network is lower than that of the destination network of the first service data according to the importance of the destination network of the first service data and the importance of the destination network of the service data that has been connected to the first network slice, releases the second service data, and accepts the first service data. For example, if the DNN of the first service data to be connected to the first network slice shows that the first service data is trying to access the destination network related to enterprise production, and the DNN of the second service data that has been connected to the first network slice shows that the destination network connected to the second service data is used for the enterprise mailbox, PCF can determine that the importance of the first service data is higher than that of the second service data, and PCF determines to release the second service data and accept the first service data.

[0183] c), PCF determines to release the second service data in the service data that has been accessed to the first network slice and accepts the first service data to be accessed to the first network slice according to the session type of the service data that has been accessed to the first network slice and the session type of the first service data to be accessed to the first network slice. Specifically, PCF determines the destination network of the first service data according to the session type of the first service data to be accessed to the first network slice, determines the destination network of the service data that has been accessed to the first network slice according to the session type of the service data that has been accessed to the first network slice, and determines the second service data whose importance of the destination network is lower than that of the destination network of the first service data according to the importance of the destination network of the first service data and the importance of the destination network of the service data that has been accessed to the first network slice, releases the second service data, and accepts the first service data. For example, if the session type of the first service data to be accessed to the first network slice is Ethernet type, indicating that the first service data is trying to access the local area network related to enterprise production, and the session type of the second service data that has been accessed is IPv4 or IPv6 type, indicating that the destination network connected to the second service data is the Internet, PCF can determine that the importance of the first service data is higher than that of the second service data, and then determines to release the second service data and accept the first service data.

[0184] d), PCF determines to release the second service data in the service data that has been connected to the first network slice and accept the first service data to be connected to the first network slice according to the service data flow type of the service data that has been connected to the first network slice and the service data flow type of the first service data to be connected to the first network slice. Specifically, the importance of the service data flow type of the service data that has been connected to the first network slice and the importance of the service data flow type of the first service data to be connected to the first network slice are compared, and the second service data whose service data flow type is less important than the service data flow type of the first service data is determined in the service data that has been connected to the first network slice, and the second service data is released and the first service data is accepted. For example, if the 5QI of the first service data to be connected to the first network slice shows that the first service data is a real-time communication service, and the 5QI of the second service data that has been connected shows that the second service data is an Internet connection service, the PCF can determine that the importance of the first service data is higher than the second service data, and the PCF determines to release the second service data and accept the first service data.

[0185] e), PCF determines to release the second service data in the service data that has been accessed to the first network slice and accepts the first service data to be accessed to the first network slice according to the access network type of the service data that has been accessed to the first network slice and the access network type of the first service data to be accessed to the first network slice. Specifically, the importance of the service type corresponding to the access network type of the service data that has been accessed to the first network slice and the importance of the service type corresponding to the access network type of the first service data to be accessed to the first network slice are compared, and the importance of the service type corresponding to the access network type of the service data that has been accessed to the first network slice is determined to be lower than the importance of the service type corresponding to the access network type of the first service data in the service data that has been accessed to the first network slice, and the second service data is released and the first service data is accepted. For example, the first service data to be accessed to the first network slice comes from the wireless local network access of the enterprise premises, indicating that the first service data is a service related to the enterprise production, while the second service data that has been accessed comes from the mobile network base station access, indicating that the second service data is an Internet connection service. The PCF can determine that the importance of the first service data is higher than the second service data, and the PCF determines to release the second service data and accept the first service data.

[0186] f), PCF determines to release the second service data in the service data that has been accessed to the first network slice and accepts the first service data to be accessed to the first network slice according to the location of the terminal device to which the service data that has been accessed to the first network slice belongs and the location of the terminal device to which the first service data to be accessed to the first network slice belongs. Specifically, the importance of the service type corresponding to the terminal device to which the service data that has been accessed to the first network slice belongs is compared with the importance of the service type corresponding to the terminal device to which the first service data to be accessed to the first network slice belongs, and determines in the service data that has been accessed to the first network slice that the importance of the service type corresponding to the terminal device to which the service data belongs is lower than the importance of the service type corresponding to the terminal device to which the first service data belongs, and releases the second service data and accepts the first service data. For example, the terminal device to which the first service data to be accessed to the first network slice belongs is accessed from a wireless base station at the enterprise premises, indicating that the first service data is a service related to the enterprise production, while the terminal device to which the second service data that has been accessed belongs is accessed from a wireless base station outside the premises, indicating that the second service data is a service related to email or instant communication office. The PCF can determine that the importance of the first service data is higher than the second service data, and the PCF determines to release the second service data and accept the first service data.

[0187] Case 2, S520, includes: if the service usage of the first network slice is less than the service volume upper limit of the first network slice, the PCF determines to accept the first service data to be accessed to the first network slice. Optionally, the PCF does not need to release the resources used by any service data in the first network slice.

[0188] Therefore, in method 500, the PCF can determine the release of the second service data that has been accessed to the first network slice and accept the first service data to be accessed to the first network slice based on the service usage of the first network slice and the service volume upper limit of the first network slice. The PCF can control the service data accessing the first network slice. In addition, while accessing high-priority or important data services as much as possible, ensure that the service usage of the first network slice does not exceed the upper limit.

[0189] In an embodiment of the present application, the service data that has been connected to a network slice or is to be connected to a network slice may be a protocol data unit (PDU) session or a QoS flow. If the service data that has been connected to a network slice or is to be connected to a network slice is a PDU session, a PDU session may include one or more QoS flows.

[0190] Combine the following Figure 6-Figure 14 The method for communication in the embodiments of the present application is described in detail.

[0191] like Figure 6 As shown, the method 600 corresponds to the above method 200, and the method 600 includes:

[0192] S601, operation administration and maintenance (OAM) determines the upper limit of the service volume of the first network slice, and sends the upper limit of the service volume of the first network slice to the PCF through UDR / UDM. The PCF saves the upper limit of the service volume of the first network slice.

[0193] Optionally, UDR / UDM can also save the service volume upper limit of the first network slice.

[0194] S602, PCF determines the service usage of the first network slice.

[0195] If the first network slice corresponds to only one PCF, S602 includes: if the PCF establishes service data or releases service data in the first network slice, the PCF updates the service usage of the first network slice saved by itself.

[0196] If the first network slice corresponds to multiple PCFs, S602 includes: after each PCF establishes service data or releases service data in the first network slice, the data volume of service data established in the first network slice or the data volume of service data released is sent to the UDR / UDM, and the UDR / UDM determines the service usage of the first network slice according to the data volume of service data established or the data volume of service data released sent by each PCF corresponding to the first network slice. For example, the UDR / UDM stores the service usage of the first network slice. When the UDR / UDM receives the data volume of service data established or the data volume of service data released sent by each PCF, the UDR / UDM dynamically adjusts the service usage of the first network slice according to the data volume of service data established or the data volume of service data released, and sends the adjusted service usage to each PCF.

[0197] It should be noted that there is no limitation on the order of S601 and S602 , and S601 may be before or after S602 .

[0198] S603, the UE sends a setup request message for the first service data to the AMF through the RAN, the first setup request message includes the first S-NSSAI, the AMF stores the result of the network slice selection performed by the NSSF when the UE registers to the network (that is, the correspondence between the S-NSSAI and the network slice), the AMF determines the first network slice corresponding to the first service data according to the first S-NSSAI, selects the SMF corresponding to the first network slice, and sends a setup request message to the SMF, the setup request message includes the first S-NSSAI.

[0199] It should be noted that there is no restriction on the order of S603, S601 and S602, that is, S603 is initiated when the UE has the need to establish service data and is not subject to the PCF's acquisition of the service usage of the first network slice and the upper limit of the service volume of the first network slice.

[0200] S604, after receiving the establishment request message, SMF requests the session management subscription information of the first network slice from UDM according to the first S-NSSAI, and UDM returns the session management subscription information to SMF. The session management subscription information includes the fifth generation network service quality indicator (5G QoS identifier, 5QI) and ARP parameters of the first service data.

[0201] Specifically, in S603, the establishment request message of the first service data sent by the UE to the AMF through the RAN and the establishment request message sent by the AMF to the SMF may include parameters such as S-NSSAI, DNN, and session type of the first service data. In S604, when the SMF requests the session management subscription information of the first network slice from the UDM, at least one of the parameters such as S-NSSAI, DNN, and session type of the first service data may also be sent to the UDM. The UDM may search for the default QoS parameters of the corresponding network slice and data network subscription of the UE according to at least one of the parameters such as S-NSSAI, DNN, and session type. The default QoS parameters include 5QI and ARP. In this way, the session management subscription information returned by the UDM to the SMF may include the default QoS parameters.

[0202] Optionally, the session management subscription information may further include at least one of the parameters such as the subscribed Session-AMBR, the allowed session type and the default session type.

[0203] S605, SMF requests the session management policy of the first network slice from PCF through a request message, wherein the request message carries at least one of the first S-NSSAI, DNN and the contracted default QoS parameters (5QI and ARP parameters). PCF returns the authorized session management policy.

[0204] Optionally, PCF can modify the contracted default 5QI and ARP parameters according to the operator's local configuration, and include the modified results as authorized default QoS parameters in the session management policy and send it to SMF. In other words, the session management policy now includes the modified 5QI and ARP parameters.

[0205] S606, PCF determines whether the service usage of the first network slice reaches the service volume upper limit of the first network slice.

[0206] If the first network slice corresponds to only one PCF, S606 includes: the PCF determines whether the service usage of the first network slice reaches the service volume upper limit of the first network slice based on the service usage of the first network slice stored by itself and the service volume upper limit of the first network slice obtained in S601. If the first network slice corresponds to multiple PCFs, S606 includes: the PCF can determine whether the service usage of the first network slice reaches the service volume upper limit of the first network slice based on the service usage of the first network slice obtained from the UDR / UDM and the service volume upper limit of the first network slice obtained in S601.

[0207] If the first network slice corresponds to multiple PCFs, S606 includes: UDR / UDM determines the difference between the business volume upper limit of the first network slice and the business usage of the first network slice based on the business usage of the first network slice and the business volume upper limit of the first network slice, which can also be called a quota, and sends the difference to the PCF, and the PCF determines whether the business usage of the first network slice reaches the business volume upper limit of the first network slice based on the difference; specifically, if the difference is greater than zero, it indicates that the business usage of the first network slice does not reach the business volume upper limit of the first network slice; if the difference is less than zero, it indicates that the business usage of the first network slice reaches the business volume upper limit of the first network slice.

[0208] Optionally, S606 may be triggered by S605.

[0209] Optionally, the first network slice corresponds to multiple PCFs, and UDR / UDM can allocate an available quota of the first network slice to each PCF. When the quota of a PCF is about to run out, S606 can be triggered.

[0210] Optionally, S606 may be triggered by the PCF performing a check periodically, for example, when the duration of a timer exceeds, S606 is triggered.

[0211] S607, generating indication information according to the determination result of S606.

[0212] Specifically, the method of generating the indication information refers to the description of S220.

[0213] S608, PCF sends the indication information to SMF.

[0214] Optionally, if the indication information is situation 1 of S220, when the UPF resources are insufficient or the service usage of the first network slice reaches the service volume upper limit of the first network slice, SMF can also seize UPF resources for the first service data according to the indication information.

[0215] S609, SMF sends the indication information to AMF, and AMF sends the indication information to RAN.

[0216] S610, RAN controls resource preemption according to the instruction information. Please refer to the description of S240 for details.

[0217] Optionally, in S610, the RAN may directly control the preemption of resources according to the indication information.

[0218] Optionally, in S610, when resources are insufficient, the RAN may control resource preemption according to the indication information.

[0219] Optionally, in S610, when resources are sufficient, the RAN may control resource preemption according to the indication information.

[0220] If the indication information is used to instruct the RAN to release the resources used by the service data that has already accessed the first network slice for the first service data to be accessed by the first network slice, or the indication information is used to indicate that the service usage of the first network slice is greater than or equal to the service volume upper limit of the first network slice (case 1 and case 2 in S220), then the RAN determines the second service data whose priority is lower than the priority of the first service data (the ARP-PL of the second service data is greater than the ARP-PL of the first service data) and whose ARP-PE_V is allowed to be preempted (for example, ENABLE) among the service data accessing the first network slice, and releases the resources used by the second service data to make room for the first service data. Otherwise, if there is no service data whose priority is lower than the priority of the first service data and whose ARP-PE_V is allowed to be preempted (for example, ENABLE) among the service data accessing the first network slice, then the RAN refuses to establish the first service data.

[0221] S611, if in S610 RAN releases the resources used by the second service data that has already accessed the first network slice for the first service data to be accessed the first network slice, RAN sends a feedback message of the establishment request message to the UE, and the feedback message of the establishment request message is used to indicate acceptance of establishing the first service data.

[0222] If the RAN refuses to establish the first service data in S610, the RAN sends a feedback message of the establishment request message to the UE, where the feedback message of the establishment request message is used to indicate that the establishment of the first service data is refused.

[0223] For example, if the first service data is a PDU session, the feedback message of the establishment request message is an access network resource establishment (AN-specific resource setup) message, which carries PDU session establishment accept (PDU session establishment Accept) information.

[0224] S612: If in S610 RAN releases the resources used by the second service data that has already accessed the first network slice for the first service data to be accessed the first network slice, the UE, RAN, AMF, SMF, UPF and PCF complete the subsequent process of establishing the first service data.

[0225] S613: If in S610 RAN releases the resources used by the second service data that has already accessed the first network slice for the first service data to be accessed the first network slice, the UE, RAN, AMF, SMF, UPF and PCF complete the process of releasing the second service data.

[0226] It should be noted that the order of S612 and S613 is not limited.

[0227] like Figure 7 As shown, the method 700 corresponds to the above method 300, and the method 700 includes:

[0228] S701, operation administration and maintenance (OAM) determines the lower limit of the service volume of the first network slice, and sends the upper limit of the service volume of the first network slice to the PCF through the UDR. The PCF saves the lower limit of the service volume of the first network slice.

[0229] Optionally, UDR / UDM can also save the lower limit of the service volume of the first network slice.

[0230] S702, PCF determines the service usage of the first network slice.

[0231] Specifically, the way in which the PCF in S702 determines the usage of the first network slice refers to the description in S602.

[0232] It should be noted that there is no limitation on the order of S701 and S702 , and S701 may be before or after S702 .

[0233] S703-S705 are the same as S603-S605.

[0234] S706, PCF determines whether the service usage of the first network slice reaches the lower limit of the service volume of the first network slice.

[0235] If the first network slice corresponds to only one PCF, S706 includes: the PCF determines whether the service usage of the first network slice reaches the service volume lower limit of the first network slice based on the service usage of the first network slice stored in the PCF and the service volume lower limit of the first network slice obtained in S701. If the first network slice corresponds to multiple PCFs, S706 includes: the PCF can determine whether the service usage of the first network slice reaches the service volume lower limit of the first network slice based on the service usage of the first network slice obtained from the UDR and the service volume lower limit of the first network slice obtained in S701.

[0236] Optionally, S706 may be triggered by S705. Optionally, S706 may also be triggered by the PCF performing a check periodically, for example, S706 is triggered when the duration of a timer exceeds the duration of the timer.

[0237] S707, generate indication information 1 according to the determination result of S706.

[0238] Specifically, the method of generating the indication information 1 refers to the description of case 1 and case 2 of S320.

[0239] S708, if indication information 1 is used to indicate that the resources used by any service data that has already accessed the first network slice are not preempted by any service data to be accessed the second network slice, or indication information 1 is used to indicate that the service usage of the first network slice is less than or equal to the lower limit of the service volume of the first network slice, then the PCF sets the ARP-PE_V in the ARP parameters of the first service data obtained in S705 to not be preempted (for example, set to DISABLED) or the first network device sets the ARP-PE_V in the ARP parameters of each service data that has already accessed the first network slice to not be preempted (for example, set to DISABLED).

[0240] S709, PCF sends indication information 1 to SMF.

[0241] Optionally, if indication information 1 is situation 1 of S320, when UPF resources are insufficient or the service usage of the first network slice reaches the service volume upper limit of the first network slice, SMF can seize UPF resources for the first service data according to indication information 1.

[0242] It should be noted that there is no restriction on the order of S708 and S707.

[0243] S710, SMF sends indication information 1 to AMF, and AMF sends the indication information to RAN.

[0244] S711, RAN prohibits the resources used by any service data that has accessed the first network slice from being preempted by any service data to be accessed the second network slice according to indication information 1.

[0245] For details of S711, please refer to the description of Case 1 or Case 2 of S340.

[0246] S712: If the indication information is used to indicate that the resources used by any service data that has accessed the first network slice are not preempted by any service data to be accessed the second network slice, or the indication information is used to indicate that the service usage of the first network slice is less than or equal to the lower limit of the service volume of the first network slice (corresponding to case 1 and case 2 in S320), RAN sets the ARP-PE_V in the ARP parameters of each service data that has accessed the first network slice to not be preempted (for example, set it to DISABLED).

[0247] S713: If after S711, the RAN sends a feedback message of the establishment request message to the UE, the feedback message of the establishment request message is used to indicate acceptance of establishment of the first service data.

[0248] For example, if the first service data is a PDU session, the feedback message of the establishment request message is an access network resource establishment (AN-specific resource setup) message, which carries PDU session establishment accept (PDU session establishment Accept) information.

[0249] S714, PCF updates the service usage of the first network slice for the newly established first service data.

[0250] If the first network slice corresponds to only one PCF, S714 includes: if after the PCF establishes the first service data in the first network slice, the PCF updates the service usage of the first network slice saved by itself.

[0251] If the first network slice corresponds to multiple PCFs, S714 includes: after the PCF establishes the first service data in the first network slice, the PCF sends the data volume of the first service data established in the first network slice to the UDR, and the UDR determines the service usage of the first network slice according to the data volume of the service data established or the data volume of the service data released sent by each PCF corresponding to the first network slice. And the updated service usage of the first network slice is sent to the PCF.

[0252] S715, PCF determines whether the service usage of the first network slice reaches the service volume lower limit of the first network slice. If the service volume lower limit of the first network slice is reached, the generated indication information 2 is case 3 or case 4 in S320.

[0253] S716, if indication information 2 is used to indicate that the resources used by any service data that has accessed the first network slice can be preempted by any service data to be accessed the second network slice, or indication information 2 is used to indicate that the service usage of the first network slice is greater than the lower limit of the service volume of the first network slice, then the PCF modifies the ARP-PE_V in the ARP parameter modified in S712 to allow preemption (for example, set to ENABLED) or the first network device sets the ARP-PE_V in the ARP parameter of all service data or part of the service data that has accessed the first network slice to allow preemption (for example, set to DISABLED)

[0254] S717, PCF sends indication information 2 to SMF.

[0255] S718, SMF sends indication information 2 to AMF, and AMF sends the indication information to RAN.

[0256] S719, RAN determines, based on indication information 2, that resources used by any service data that has accessed the first network slice can be preempted by any service data to be accessed the second network slice.

[0257] like Figure 8 As shown, the method 800 corresponds to the above method 400, and the method 800 includes:

[0258] S801, OAM determines the upper limit of the service volume of the first network slice and the lower limit of the service volume of the first network slice, and sends the upper limit of the service volume of the first network slice and the lower limit of the service volume of the first network slice to PCF through UDR / UDM. PCF saves the upper limit of the service volume of the first network slice and the lower limit of the service volume of the first network slice.

[0259] Optionally, UDR / UDM can also save the upper limit of the business volume of the first network slice and the lower limit of the business volume of the first network slice.

[0260] S802, PCF determines the service usage of the first network slice.

[0261] Specifically, the way in which the PCF in S802 determines the usage of the first network slice refers to the description in S602.

[0262] It should be noted that there is no limitation on the order of S801 and S802 , and S801 may be before or after S802 .

[0263] S803-S805 are the same as S603-S605.

[0264] S806, PCF determines the indication information based on the upper limit of the business volume of the first network slice, the lower limit of the business volume of the first network slice, and the business usage of the first network slice.

[0265] If the first network slice corresponds to only one PCF, S806 includes: the PCF determines whether the service usage of the first network slice reaches the service volume upper limit of the first network slice based on the service usage of the first network slice stored by itself and the service volume upper limit of the first network slice obtained in S601. If the first network slice corresponds to multiple PCFs, S806 includes: the PCF can determine the indication information based on the service usage of the first network slice obtained from the UDR / UDM, the service volume upper limit of the first network slice obtained in S801, and the service volume lower limit of the first network slice.

[0266] Specifically, the method for determining the indication information in S806 refers to the description in S420.

[0267] Optionally, S806 may be triggered by S805.

[0268] Optionally, the first network slice corresponds to multiple PCFs, and the UDR can allocate an available quota of the first network slice to each PCF. When the quota of a PCF is about to run out, S806 can be triggered.

[0269] Optionally, S806 may be triggered by a PCF periodic execution check, for example, when the duration of a timer exceeds S806.

[0270] S807, PCF sends the indication information to SMF.

[0271] S808, SMF sends the indication information to AMF, and AMF sends the indication information to RAN.

[0272] If the indication information is case 5 and case 6 in S420, the control resource preemption method of RAN refers to the description of S610-S613 in method 600. If the indication information is case 1 and case 2 in S420, the control resource preemption method of RAN refers to the description of S708-S713 in method 700.

[0273] If the indication information is case 3 or case 4 in S420, the RAN executes S809.

[0274] S809, RAN releases the resources used by the service data that has already accessed the first network slice or releases the resources used by the service data that has already accessed other network slices for the first service data to be accessed the first network slice.

[0275] Specifically, it can be determined to release the resources used by the second service data that has accessed the first network slice or to release the resources used by the second service data that has accessed other network slices. Specifically, how to determine the second service data refers to the description of method 200.

[0276] S810, after S809, the RAN sends a feedback message of the establishment request message to the UE, where the feedback message of the establishment request message is used to indicate acceptance of establishment of the first service data.

[0277] For example, if the first service data is a PDU session, the feedback message of the establishment request message is an AN-specificresource setup message, which carries PDU session establishment Accept information.

[0278] S811, UE, RAN, AMF, SMF, UPF and PCF complete the subsequent process of establishing the first service data.

[0279] S812, UE, RAN, AMF, SMF, UPF and PCF complete the process of releasing the second service data.

[0280] It should be noted that the order of S811 and S812 is not limited.

[0281] As another optional embodiment, in S806, if the service usage of the first network slice is less than or equal to the lower limit of the service volume of the first network slice, the first network slice can be considered to be in a "protection state" at this time, and accordingly, the indication information can indicate a "protection state"; if the service usage of the first network slice is greater than the lower limit of the service volume of the first network slice and less than or equal to the upper limit of the service volume of the first network slice, the first network slice can be considered to be in a "normal state" at this time, and accordingly, the indication information can indicate a "normal state"; if the service usage of the first network slice is greater than or equal to the upper limit of the service volume of the first network slice, the first network slice can be considered to be in a "restriction state" at this time, and accordingly, the indication information can indicate a "restriction state"; if the indication information is used to indicate a "protection state" or a "normal state" or a "restriction state", the RAN can perform resource preemption according to the indication information, and the preemption strategy is as described in methods 600-methods 800.

[0282] As another optional embodiment, in method 800, the lower limit of the service volume of the first network slice is replaced by the lower limit of the resource occupancy rate of the first network slice, and the upper limit of the service volume of the first network slice is replaced by the upper limit of the resource occupancy rate of the first network slice.

[0283] like Fig. 9 As shown, the method 900 corresponds to the above method 500, and the method 900 includes:

[0284] S901, OAM determines the upper limit of the service volume of the first network slice, and sends the upper limit of the service volume of the first network slice to PCF through UDR. PCF saves the upper limit of the service volume of the first network slice.

[0285] Optionally, the UDR can also save the service volume upper limit of the first network slice.

[0286] S902, PCF determines the service usage of the first network slice.

[0287] Specifically, the way in which the PCF in S902 determines the usage of the first network slice refers to the description in S602.

[0288] It should be noted that there is no limitation on the order of S901 and S902 , and S901 may be before or after S902 .

[0289] S903-S905 are the same as S603-S605.

[0290] S906, determine the relationship between the service usage of the first network slice and the upper limit of the service volume of the first network slice.

[0291] Optionally, S906 may be triggered by S905.

[0292] Optionally, S906 may be triggered by the PCF performing a check periodically, for example, when the duration of a timer exceeds, S906 is triggered.

[0293] If the service usage of the first network slice is greater than or equal to the service volume upper limit of the first network slice, the PCF determines to limit the first service data from preempting the resources of service data in network slices identified by other S-NSSAI. Specifically, there are two cases, S907a and S907b.

[0294] S907a: If the service usage of the first network slice is greater than or equal to the service volume upper limit of the first network slice, the PCF may refuse to accept the first service data based on parameters such as 5QI or ARP in the contracted default QoS parameters or authorized default QoS parameters of the first service data, the DNN of the first service data, the service type of the first service data, the access network type of the first service data, and the location of the terminal device of the first service data.

[0295] For example, if the ARP-PL in the ARP parameters of the first service data in S905 is lower than a specific priority, or the ARP-PE-C parameter is not set in the ARP parameters of the first service data in S905, the PCF refuses to establish the first service data. The process ends.

[0296] S907b, if the service usage of the first network slice is greater than or equal to the service volume upper limit of the first network slice, the PCF may determine to release the second service data in the service data that has been connected to the first network slice and accept the first service data to be connected to the first network slice based on the 5QI or ARP in the service quality parameters of the service data that has been connected to the first network slice and the 5QI or ARP in the service quality parameters of the first service data to be connected to the first network slice.

[0297] For example, if the ARP-PL in the ARP parameters of the first service data in S905 is higher than a specific priority, and the ARP-PE-C parameter set in the ARP parameters of the first service data in S905 has preemptive capability (for example, set to ENABLE), the PCF determines that the service data that has accessed the first network slice needs to be released to accept the first service data to be accessed in the first network slice.

[0298] Specifically, the PCF determines which service data that has accessed the first network slice to release through at least one of a)-f) in method 500, which is not described in detail here.

[0299] Specifically, the specific priority in S907a and S907b may be a preset priority, for example, a priority preset by an operator.

[0300] The ARP parameters in S907a and S907b are the parameters in S905. Optionally, the ARP parameters in S907a and S907b may be the ARP parameters generated by the PCF according to the ARP parameters in S905 and the policy charging control rules (PCC rule). Specifically, the PCF may directly adopt the contracted QoS parameters (i.e., the ARP parameters in S905) to authorize the default QoS parameters for the PDU Session; or the PCF may detect a new QoS Flow for the SMF according to the service data flow template (SDFTemplate) in the PCC Rule and authorize appropriate QoS parameters, and the QoS parameters include 5QI and ARP, etc.

[0301] S907c, if the service usage of the first network slice is less than the service volume upper limit of the first network slice, the PCF determines to accept the first service data of the first network slice to be accessed, and there is no need to release any service data that has been accessed in the first network slice.

[0302] After S908, S907b and S907c, UE, RAN, AMF, SMF, UPF and PCF complete the subsequent process of establishing the first service data.

[0303] S909: After S907b, UE, RAN, AMF, SMF, UPF and PCF complete the process of releasing the second service data.

[0304] It should be noted that the order of S908 and S909 is not limited.

[0305] like Fig.10 As shown, method 1000 includes:

[0306] S1001, OAM determines the lower limit of the resource occupancy rate of the first network slice, and configures the lower limit of the resource occupancy rate of the first network slice to RAN.

[0307] It can be understood that method 1000 is described using only one network slice as an example. OAM can determine the lower limit of resource occupancy of multiple network slices and send the lower limit of resource occupancy of multiple network slices to RAN.

[0308] S1002, OAM determines the upper limit of the service volume of the first network slice, and sends the upper limit of the service volume of the first network slice to PCF through UDR. PCF saves the upper limit of the service volume of the first network slice.

[0309] Optionally, the UDR can also save the service volume upper limit of the first network slice.

[0310] S1003, PCF determines the service usage of the first network slice.

[0311] Specifically, the way in which the PCF in S1003 determines the usage of the first network slice can be found in the description in S602.

[0312] It should be noted that there is no limitation on the order of S1001 , S1002 and S1003 .

[0313] S1004-S1006 are the same as S603-S605.

[0314] S1007, PCF determines whether the service usage of the first network slice reaches the service volume upper limit of the first network slice. See the description of S606 for details.

[0315] Optionally, S1007 may be triggered by S1006.

[0316] Optionally, S1007 may be triggered by the PCF performing a check periodically, for example, S606 may be triggered when the duration of a timer exceeds the duration of the timer.

[0317] Optionally, the first network slice corresponds to multiple PCFs, and UDR / UDM can allocate an available quota of the first network slice to each PCF. When the quota of a PCF is about to run out, S1007 can be triggered.

[0318] S1008, generating indication information according to the determination result of S1007.

[0319] Specifically, the method of generating the indication information refers to the description of S220.

[0320] S1009, PCF sends the indication information to SMF.

[0321] S1010, SMF sends the indication information to AMF, and AMF sends the indication information to RAN.

[0322] S1011, RAN controls resource preemption based on the indication information and the lower limit of the resource occupancy rate of the first network slice in S1001.

[0323] If the indication information is used to indicate that the service usage of the first network slice is greater than or equal to the upper limit of the service volume of the first network slice or the indication information is used to indicate the release of resources used by service data that have already accessed the first network slice for the first service data to be accessed to the first network slice (case 1 and case 2 in S220), then the RAN determines the second service data whose priority is lower than the priority of the first service data (the ARP-PL of the second service data is greater than the ARP-PL of the first service data) and whose ARP-PE_V is allowed to be preempted (for example, ENABLE) in the service data accessing the first network slice, and releases the resources used by the second service data to make room for the first service data. Otherwise, if there is no service data whose priority is lower than the priority of the first service data and whose ARP-PE_V is allowed to be preempted (for example, ENABLE) in the service data accessing the first network slice, the RAN refuses to establish the first service data.

[0324] If the indication information is used to indicate that the service usage of the first network slice is less than the upper limit of the service volume of the first network slice, and the RAN determines that the resource occupancy rate of the first network slice of the current RAN is greater than the lower limit of the resource occupancy rate in S1001, the RAN releases the resources used by the service data that has already accessed the first network slice or releases the service data that has already accessed other network slices for the first service data to be accessed by the first network slice. Specifically, refer to the description of S809.

[0325] If the RAN determines that the resource occupancy rate of the first network slice of the current RAN is less than or equal to the lower limit of the resource occupancy rate in S1001, the RAN prohibits the resources used by any service data that has accessed the first network slice from being preempted by any service data to be accessed the second network slice. Optionally, the RAN sets the ARP-PE_V in the ARP parameters of each service data that has accessed the first network slice to not be preempted (for example, to DISABLED).

[0326] It can be understood that the resource occupancy rate of the first network slice of the RAN can be the ratio of the business data that has accessed the first network slice through the RAN to the resources of the RAN and the total resources of the RAN.

[0327] S1012. If in S1011 RAN determines to accept the first service data to be accessed to the first network slice, RAN sends a feedback message of the establishment request message to the UE, and the feedback message of the establishment request message is used to indicate acceptance of establishing the first service data.

[0328] S1013: If in S1011 RAN determines to accept the first service data to be accessed in the first network slice, the UE, RAN, AMF, SMF, UPF and PCF complete the subsequent process of establishing the first service data.

[0329] S1014: If in S1011 RAN releases the resources used by the second service data that has already accessed the first network slice or other network slices for the first service data to be accessed the first network slice, the UE, RAN, AMF, SMF, UPF and PCF complete the process of releasing the second service data.

[0330] As an optional embodiment, the upper limit of the resource occupancy rate of the first network slice may be further sent to the RAN in S1001, and the RAN in S1011 may control resource preemption according to the upper limit of the resource occupancy rate of the first network slice and the lower limit of the resource occupancy rate of the first network slice in S1001. In this case, no indication information is required in method 1000, and steps related to the indication information may be omitted. The specific cases are discussed as follows:

[0331] If the resource occupancy rate of the first network slice of the current RAN is greater than the upper limit of the resource occupancy rate of the first network slice, and the RAN determines to release the resources used by the service data that has already accessed the first network slice for the first service data to be accessed to the first network slice, then the RAN determines the second service data whose priority is lower than the priority of the first service data (the ARP-PL of the second service data is greater than the ARP-PL of the first service data) and whose ARP-PE_V is allowed to be preempted (for example, ENABLE) among the service data accessing the first network slice, and releases the resources used by the second service data to make room for the first service data. Otherwise, if there is no service data whose priority is lower than the priority of the first service data and whose ARP-PE_V is allowed to be preempted (for example, ENABLE) among the service data accessing the first network slice, the RAN refuses to establish the first service data.

[0332] If the resource occupancy rate of the first network slice of the current RAN is less than or equal to the upper limit of the resource occupancy rate of the first network slice and is greater than the lower limit of the resource occupancy rate in S1001, the RAN releases the resources used by the service data that has already accessed the first network slice or releases the services data that has already accessed other network slices for the first service data to be accessed the first network slice. For details, refer to the description of S809.

[0333] If the RAN determines that the resource occupancy rate of the first network slice of the current RAN is less than or equal to the lower limit of the resource occupancy rate of the first network slice, the RAN prohibits the resources used by any service data that has accessed the first network slice from being preempted by any service data to be accessed the second network slice. Optionally, the RAN sets the ARP-PE_V in the ARP parameters of each service data that has accessed the first network slice to not be preempted (for example, to DISABLED).

[0334] like Fig.11 As shown, the method 1100 includes:

[0335] S1101, OAM determines the upper limit of the service volume of the first network slice and the lower limit of the service volume of the first network slice, and sends the upper limit of the service volume of the first network slice and the lower limit of the service volume of the first network slice to NSSF. NSSF saves the upper limit of the service volume of the first network slice and the lower limit of the service volume of the first network slice.

[0336] S1102, an AMF selected in the AMF Set or the default AMF of the RAN sends a subscription request message to the NSSF. The NSSF accepts the subscription request message, which is used to subscribe to the status of the network slice.

[0337] Specifically, after establishing a connection with the RAN or receiving a subscription request message from the RAN, the AMF sends a subscription request message to the NSSF.

[0338] It should be noted that the order of S1101 and S1102 is not limited.

[0339] S1103, NSSF obtains the number of service data established in the first network slice from multiple AMFs of the first network slice, and aggregates them as the service usage of the first network slice.

[0340] It should be noted that the order of S1103 and S1102 is not limited.

[0341] S1104, NSSF determines the status of the first network slice according to the service volume upper limit of the first network slice in S1101, the service volume lower limit of the first network slice and the service usage of the first network slice in S1103.

[0342] If the service usage of the first network slice is less than or equal to the lower limit of the service volume of the first network slice, the NSSF determines that the state of the first network slice is "protection state".

[0343] If the service usage of the first network slice is greater than the lower limit of the service volume of the first network slice and is less than or equal to the upper limit of the service volume of the first network slice, the NSSF determines that the status of the first network slice is "normal".

[0344] If the service usage of the first network slice is greater than or equal to the service volume upper limit of the first network slice, the NSSF determines that the state of the first network slice is "restricted state".

[0345] S1105, NSSF sends a feedback message of the subscription request message to AMF, and the feedback message includes indication information for indicating the status of the first network slice.

[0346] Optionally, if the state of the first network slice in S1104 changes, as an alternative to S1105, the indication information may indicate the state of the first network slice after the change.

[0347] S1106, AMF sends the status of the first network slice to RAN, for example, the status of the first network slice may also be sent to RAN through indication information.

[0348] S1107, the terminal device sends a setup request message for the first service data to the AMF through the RAN, the first setup request message includes the first S-NSSAI, the AMF determines the first network slice corresponding to the first service data according to the first S-NSSAI, selects the SMF corresponding to the first network slice, and sends a setup request message to the SMF, the setup request message still includes the first S-NSSAI.

[0349] S1108, SMF sends a first S-NSSAI to PCF, PCF determines the session management policy of the first network slice based on the first S-NSSAI, and PCF returns the session management policy of the first network slice.

[0350] Optionally, the session management policy includes a 5QI and an ARP parameter of the first service data.

[0351] S1109, SMF sends the session management policy to AMF.

[0352] For example, the session management policy may be sent to the AMF via N1N2 messaging (Namf_Communication_N1N2MessageTransfer).

[0353] S1110, AMF sends the session management policy to RAN.

[0354] For example, the AMF sends the session management policy to the RAN via the N2 interface PDU session request (N2PDU Session Request).

[0355] S1111: If the available resources of RAN are insufficient, RAN controls resource preemption according to the status of the first network slice in S1106.

[0356] If the state of the first network slice is "restricted state", RAN determines the second service data whose priority is lower than that of the first service data (the ARP-PL of the second service data is greater than that of the first service data) and whose ARP-PE_V is allowed to be preempted (for example, ENABLE) among the service data accessing the first network slice, and releases the resources used by the second service data to make way for the first service data. Otherwise, if there is no service data whose priority is lower than that of the first service data and whose ARP-PE_V is allowed to be preempted (for example, ENABLE) among the service data accessing the first network slice, RAN refuses to establish the first service data.

[0357] If the status of the first network slice is "protected state", RAN sets the ARP-PE_V in the ARP parameters of each service data that has accessed the first network slice to not allow preemption (for example, set it to DISABLED).

[0358] If the status of the first network slice is "normal", RAN releases the resources used by the service data that has already accessed the first network slice or releases the services that have already accessed other network slices for the first service data to be accessed the first network slice.

[0359] S1112: If in S1111 RAN releases the resources used by the second service data that has already accessed the first network slice or the service data that has already accessed other network slices for the first service data to be accessed the first network slice, RAN sends a feedback message of the establishment request message to the UE, and the feedback message of the establishment request message is used to indicate acceptance of the establishment of the first service data.

[0360] S1113: If in S1111 RAN releases the resources used by the second service data that has already accessed the first network slice or the second service data that has already accessed other network slices for the first service data to be accessed the first network slice, the UE, RAN, AMF, SMF, UPF and PCF complete the subsequent process of establishing the first service data.

[0361] S1114: If in S1111 RAN releases the resources used by the second service data that has already accessed the first network slice for the first service data to be accessed the first network slice, the UE, RAN, AMF, SMF, UPF and PCF complete the process of releasing the second service data.

[0362] like Fig.12 As shown, the method 1200 includes:

[0363] S1201, OAM / UDR / NSSF / NRF / PCF determines the upper limit of the service volume of the first network slice and the lower limit of the service volume of the first network slice, and sends the upper limit of the service volume of the first network slice and the lower limit of the service volume of the first network slice to NWDAF. NWDAF saves the upper limit of the service volume of the first network slice and the lower limit of the service volume of the first network slice.

[0364] S1202, an AMF selected in the AMF Set or the default AMF of the RAN sends a subscription request message to the NWDAF. The NWDAF accepts the subscription request message, which is used to subscribe to the status of the network slice.

[0365] Specifically, after establishing a connection with the RAN or receiving a subscription request message from the RAN, the AMF sends a subscription request message to the NWDAF.

[0366] It should be noted that the order of S1201 and S1202 is not limited.

[0367] S1203, NWDAF obtains the number of service data established in the first network slice from multiple AMFs and / or SMFs of the first network slice, and aggregates them as the service usage of the first network slice.

[0368] It should be noted that the order of S1203 and S1202 is not limited.

[0369] S1204, NWDAF determines the status of the first network slice according to the service volume upper limit of the first network slice in S1201, the service volume lower limit of the first network slice and the service usage of the first network slice in S1203.

[0370] If the service usage of the first network slice is less than or equal to the lower limit of the service volume of the first network slice, NWDAF determines that the status of the first network slice is "protection state".

[0371] If the service usage of the first network slice is greater than the lower limit of the service volume of the first network slice and is less than or equal to the upper limit of the service volume of the first network slice, NWDAF determines that the status of the first network slice is "normal".

[0372] If the service usage of the first network slice is greater than or equal to the service volume upper limit of the first network slice, NWDAF determines that the status of the first network slice is "restricted state".

[0373] S1205, NWDAF sends a feedback message of the subscription request message to AMF, and the feedback message includes indication information for indicating the status of the first network slice.

[0374] Optionally, if the state of the first network slice in S1204 changes, as an alternative to S1205, the indication information may indicate the state of the first network slice after the change.

[0375] S1206-S1212, same as S1106-1112.

[0376] like Fig.13 As shown, the method 1300 includes:

[0377] S1301, OAM / UDR / NSSF / NRF determines the upper limit of the service volume of the first network slice and the lower limit of the service volume of the first network slice, and sends the upper limit of the service volume of the first network slice and the lower limit of the service volume of the first network slice to NWDAF. NWDAF saves the upper limit of the service volume of the first network slice and the lower limit of the service volume of the first network slice.

[0378] S1302, the session management PCF (SM-PCF) sends a subscription request message to the NWDAF. The NWDAF accepts the subscription request message, which is used to subscribe to the status of the network slice.

[0379] The SM-PCF is used to perform policy control on session management, and the SM-PCF may be a part of the PCF mentioned above.

[0380] Optionally, SM-PCF may periodically send subscription request messages to NWDAF. In addition, SM-PCF may also trigger sending a request message to NWDAF for requesting the status of the network slice upon receiving an association session management policy request sent by SMF.

[0381] It should be noted that the order of S1301 and S1302 is not limited.

[0382] S1303, NWDAF obtains the number of service data established in the first network slice from multiple AMFs and / or SMFs of the first network slice, and aggregates them as the service usage of the first network slice.

[0383] It should be noted that the order of S1303 and S1302 is not limited.

[0384] S1304, NWDAF determines the status of the first network slice according to the service volume upper limit of the first network slice in S1301, the service volume lower limit of the first network slice and the service usage of the first network slice in S1303.

[0385] If the service usage of the first network slice is less than or equal to the lower limit of the service volume of the first network slice, NWDAF determines that the status of the first network slice is "protection state".

[0386] If the service usage of the first network slice is greater than the lower limit of the service volume of the first network slice and is less than or equal to the upper limit of the service volume of the first network slice, NWDAF determines that the status of the first network slice is "normal".

[0387] If the service usage of the first network slice is greater than or equal to the service volume upper limit of the first network slice, NWDAF determines that the status of the first network slice is "restricted state".

[0388] S1305, NWDAF sends a feedback message of the subscription request message to SM-PCF, and the feedback message includes indication information for indicating the status of the first network slice.

[0389] Optionally, if the state of the first network slice in S1305 changes, as an alternative to S1305, the indication information may indicate the state of the first network slice after the change.

[0390] S1306, SM-PCF determines the control strategy of the first network slice according to the indication information.

[0391] If the indication information indicates that the status of the first network slice is "restricted state", SM-PCF determines that the control strategy of the first network slice is: prohibiting the first service data to be accessed by the first network slice from preempting the resources used by the service data that has been accessed by other network slices, and allowing the resources used by the service data that has been accessed by the first network slice to be preempted by the service data to be accessed by other network slices.

[0392] If the indication information indicates that the status of the first network slice is "normal", the SM-PCF determines that the control policy of the first network slice is: the service data to be accessed by the first network slice is allowed to preempt the resources used by the service data that has been accessed by other network slices, and the resources used by the service data that has been accessed by the first network slice are allowed to be preempted by the service data to be accessed by other network slices.

[0393] If the indication information indicates that the status of the first network slice is "protection state", the SM-PCF determines that the control policy of the first network slice is: the resources used by the service data that has already accessed the first network slice are not allowed to be preempted by the service data to be accessed by any network slice, and the service data to be accessed by the first network slice is allowed to preempt the resources used by the service data that has already accessed other network slices.

[0394] Optionally, the SM-PCF adjusts the priority of the first network slice according to the indication information, and the control policy of the first network slice may indicate the priority of the first network slice. Specifically, if the status of the first network slice indicated by the indication information is "protection status", the SM-PCF may determine that the priority of the first network slice is the highest priority, for example, 0. If the status of the first network slice indicated by the indication information is "normal status", the SM-PCF may determine that the priority of the first network slice is a medium priority, for example, 3; if the status of the first network slice indicated by the indication information is "restriction status", the SM-PCF may determine that the priority of the first network slice is the lowest priority, for example, 5.

[0395] S1307, UE sends a setup request message for the first service data to AMF through RAN, and the first setup request message includes the first S-NSSAI. AMF determines the first network slice corresponding to the first service data according to the first S-NSSAI, selects the SMF corresponding to the first network slice, and sends a setup request message to the SMF, and the setup request message still includes the first S-NSSAI. The first S-NSSAI is used to identify the first network slice.

[0396] Specifically, S1307 refers to S603.

[0397] S1308: After receiving the establishment request message, the SMF requests a session management policy from the SM-PCF according to the first S-NSSAI.

[0398] It should be noted that there is no restriction on the order of S1307 and S1308 and the order of S1306.

[0399] S1309, SM-PCF sends the session management policy in S1308 and the control policy of the first network slice in S1306 to SMF.

[0400] The session management policy may include QoS parameters for the first service data.

[0401] S1310, SMF sends the session management policy and the control policy of the first network slice to AMF.

[0402] For example, SMF can send the session management policy and the control policy of the first network slice to AMF through N1N2 message transfer (Namf_Communication_N1N2MessageTransfer).

[0403] S1311, AMF sends the session management policy and the control policy of the first network slice to RAN.

[0404] For example, AMF sends the session management policy and the control policy of the first network slice to RAN through the N2 interface PDU session request (N2PDU Session Request).

[0405] S1312, RAN controls resource preemption according to the control policy of the first network slice in S1310.

[0406] If the control policy of the first network slice is: prohibiting the first service data to be accessed to the first network slice from preempting the resources used by the service data that has been accessed to other network slices, and allowing the resources used by the service data that has been accessed to the first network slice to be preempted by the service data to be accessed to other network slices. Then the RAN preempts the resources used by the service data that has been accessed to the first network slice for the first service data to be accessed, and among the service data accessing the first network slice, the RAN determines the second service data whose priority is lower than that of the first service data (the ARP-PL of the second service data is greater than the ARP-PL of the first service data) and whose ARP-PE_V is allowed to be preempted (for example, ENABLE), and releases the resources used by the second service data to make room for the first service data.

[0407] If the control policy of the first network slice is: service data to be accessed by the first network slice is allowed to preempt resources used by service data already accessed by other network slices, and resources used by service data already accessed by the first network slice are allowed to be preempted by service data to be accessed by other network slices, the RAN releases the service data already accessed by the first network slice or releases the resources used by service data already accessed by other network slices for the first service data to be accessed by the first network slice.

[0408] If the control policy of the first network slice is: the resources used by the service data that has accessed the first network slice are not allowed to be preempted by the service data to be accessed to any network slice, and the service data to be accessed to the first network slice is allowed to preempt the resources used by the service data that has accessed other network slices. Optionally, the RAN sets the ARP-PE_V in the ARP parameters of each service data that has accessed the first network slice to not be preempted (for example, to DISABLED).

[0409] Optionally, if the control policy of the first network slice in S1306 can indicate the priority of the first network slice, the RAN can add the priority of the first network slice to the ARP-PI in the QoS parameters of the first service data in the session management policy to determine the priority of the first service data. If there are multiple network slices, the priorities of the multiple network slices can be added to the ARP-PI in the QoS parameters of the service data to be accessed to the multiple network slices to obtain the priorities of the service data to be accessed to the multiple network slices, thereby comparing the priorities of the service data to be accessed to the multiple network slices to perform resource preemption.

[0410] S1313-S1315 are the same as S1112-S1114.

[0411] like Fig.14 As shown, method 1400 includes:

[0412] S1401, OAM / UDR / NSSF / NRF determines the upper limit of the service volume of the first network slice and the lower limit of the service volume of the first network slice, and sends the upper limit of the service volume of the first network slice and the lower limit of the service volume of the first network slice to NWDAF. NWDAF saves the upper limit of the service volume of the first network slice and the lower limit of the service volume of the first network slice.

[0413] S1402, the network slice management PCF (network slice management, NM-PCF) or NSSF or access management PCF (access management PCF, AM-PCF) can send a subscription request message to NWDAF. NWDAF accepts the subscription request message, which is used to subscribe to the status of the network slice.

[0414] Among them, AM-PCF is used to perform policy control on UE registration management, and AM-PCF can be a part of the PCF mentioned above. NM-PCF is used to perform policy control on network slice management, and NM-PCF can be a part of the PCF.

[0415] Specifically, the NM-PCF / AM-PCF / NSSF may periodically send a subscription request message to the NWDAF.

[0416] It should be noted that the order of S1401 and S1402 is not limited.

[0417] S1403, NWDAF obtains the number of service data established in the first network slice from multiple AMFs and / or SMFs of the first network slice, and aggregates them as the service usage of the first network slice.

[0418] It should be noted that the order of S1403 and S1402 is not limited.

[0419] S1404, NWDAF determines the status of the first network slice according to the service volume upper limit of the first network slice in S1401, the service volume lower limit of the first network slice and the service usage of the first network slice in S1403.

[0420] If the service usage of the first network slice is less than or equal to the lower limit of the service volume of the first network slice, NWDAF determines that the status of the first network slice is "protection state".

[0421] If the service usage of the first network slice is greater than the lower limit of the service volume of the first network slice and is less than or equal to the upper limit of the service volume of the first network slice, NWDAF determines that the status of the first network slice is "normal".

[0422] If the service usage of the first network slice is greater than or equal to the service volume upper limit of the first network slice, NWDAF determines that the status of the first network slice is "restricted state".

[0423] S1405, NWDAF sends a feedback message of the subscription request message to NM-PCF or NSSF or AM-PCF, and the feedback message includes indication information for indicating the status of the first network slice.

[0424] Optionally, if the state of the first network slice in S1405 changes, as an alternative to S1405, the indication information may indicate the state of the first network slice after the change.

[0425] S1406, NM-PCF or NSSF or AM-PCF determines the control strategy of the first network slice according to the indication information.

[0426] If the indication information indicates that the status of the first network slice is "restricted state", NM-PCF or NSSF or AM-PCF determines that the control policy of the first network slice is: prohibiting the first service data to be accessed by the first network slice from preempting the resources used by the service data that has been accessed by other network slices, and allowing the resources used by the service data that has been accessed by the first network slice to be preempted by the service data to be accessed by other network slices.

[0427] If the indication information indicates that the status of the first network slice is "normal", NM-PCF or NSSF or AM-PCF determines that the control policy of the first network slice is: the service data to be accessed by the first network slice is allowed to preempt the resources used by the service data that has been accessed by other network slices, and the resources used by the service data that has been accessed by the first network slice are allowed to be preempted by the service data to be accessed by other network slices.

[0428] If the indication information indicates that the status of the first network slice is "protection state", NM-PCF or NSSF or AM-PCF determines that the control policy of the first network slice is: the resources used by the service data that has already accessed the first network slice are not allowed to be preempted by the service data to be accessed by any network slice, and the service data to be accessed by the first network slice is allowed to preempt the resources used by the service data that has already accessed other network slices.

[0429] Optionally, NM-PCF or NSSF or AM-PCF adjusts the priority of the first network slice according to the indication information. Specifically, if the status of the first network slice in the indication information is "protection state", NM-PCF or NSSF or AM-PCF can determine that the priority of the first network slice is the highest priority, for example, 0. If the status of the first network slice in the indication information is "normal state", NM-PCF or NSSF or AM-PCF can determine that the priority of the first network slice is a medium priority, for example, 3; if the status of the first network slice in the indication information is "restriction state", NM-PCF or NSSF or AM-PCF can determine that the priority of the first network slice is the lowest priority, for example, 5.

[0430] S1407, NM-PCF or NSSF or AM-PCF sends the control policy of the first network slice to AMF, where the AMF can be the AMF registered by the terminal or the default AMF connected to the RAN.

[0431] S1408, the UE sends a setup request message for the first service data to the AMF through the RAN, and the first setup request message includes the first S-NSSAI. The AMF determines the first network slice corresponding to the first service data according to the first S-NSSAI, selects the SMF corresponding to the first network slice, and sends a setup request message to the SMF, and the setup request message still includes the first S-NSSAI. The first S-NSSAI is used to identify the first network slice.

[0432] Specifically, S1408 refers to S603.

[0433] S1409: After receiving the establishment request message, the SMF requests a session management policy from the SM-PCF according to the first S-NSSAI.

[0434] It should be noted that there is no restriction on the order of S1408 and S1409 and the order of S1407.

[0435] S1410, SM-PCF sends the session management policy in S1308 to SMF.

[0436] The session management policy may include QoS parameters for the first service data.

[0437] S1411, SMF sends the session management policy to AMF.

[0438] For example, SMF can send the session management policy and the control policy of the first network slice to AMF through N1N2 message transfer (Namf_Communication_N1N2MessageTransfer).

[0439] S1412, AMF sends the session management policy of S1411 and the control policy of the first network slice in S1407 to RAN.

[0440] For example, AMF sends the session management policy and the control policy of the first network slice to RAN through the N2 interface PDU session request (N2PDU Session Request).

[0441] It should be noted that the AMF can send the session management policy and the control policy of the first network slice to the RAN at the same time or separately.

[0442] S1413-S1416, S1312-S1315.

[0443] It should be noted that, in the above method embodiment, the UE may initiate the establishment request message for sending the first service data as required and is not affected by anything.

[0444] It should also be noted that, in the above method embodiment, the PCF or RAN releases the second service data that has been connected to the first network slice or the second service data that has been connected to other network slices for the first service data to be connected to the first network slice. At this time, the second service data is one or more. In other words, after the PCF or RAN releases the second service data that has been connected to the first network slice or the second service data that has been connected to other network slices, it is necessary to make the resources meet the requirements of establishing the first data service.

[0445] Above, combined Figures 2 to 14 The communication method provided by the embodiment of the present application is described in detail. Figure 15 to Figure 16 The communication device provided in the embodiment of the present application is described in detail.

[0446] Fig.15 is a schematic block diagram of a communication device provided in an embodiment of the present application. Fig.15 As shown, the device 1500 may include a transceiver unit 1510 and a processing unit 1520 .

[0447] In a possible design, the device 1500 may correspond to the PCF or the first network device in the above method embodiment, for example, it may be a PCF or a chip configured in the PCF. The device 1500 is used to execute each step or process corresponding to the PCF in the above methods 200-1400.

[0448] Specifically, the transceiver unit 1510 is used to: obtain the service usage of the first network slice and the service volume threshold of the first network slice; the processing unit 1520 is used to generate indication information according to the service usage of the first network slice and the service volume threshold of the first network slice; the transceiver unit 1510 is also used to send the indication information to the second network device, and the indication information is used by the second network device to control resource preemption.

[0449] Optionally, the traffic volume threshold of the first network slice includes the traffic volume upper limit of the first network slice; if the traffic usage of the first network slice is greater than or equal to the traffic volume upper limit of the first network slice, the indication information is used to instruct the second network device to release resources used by traffic data that has already accessed the first network slice for the first traffic data to be accessed the first network slice, or the indication information is used to indicate that the allowed traffic usage of the first network slice is greater than or equal to the traffic volume upper limit of the first network slice.

[0450] Optionally, the traffic volume upper limit of the first network slice is at least one of the maximum number of sessions or the maximum traffic bandwidth allowed to access the first network slice or the maximum session density allowed by the first network slice.

[0451] Optionally, the traffic volume threshold of the first network slice includes a lower limit of the traffic volume of the first network slice;

[0452] If the service usage of the first network slice is less than or equal to the lower limit of the service volume of the first network slice, the indication information is used to indicate that the resources used by any service data that has accessed the first network slice are not preempted by any service data to be accessed by the second network slice, or the indication information is used to indicate that the service usage of the first network slice is less than or equal to the lower limit of the service volume of the first network slice.

[0453] Optionally, the lower limit of the service volume of the first network slice is at least one of the minimum number of sessions or the minimum traffic bandwidth guaranteed by the first network slice or the minimum session density guaranteed by the first network slice.

[0454] Optionally, if the service usage of the first network slice is less than or equal to the lower limit of the service volume of the first network slice, the processing unit is also used to set the preemption willingness parameter in the allocation and retention priority ARP parameter of the first service data to not allow preemption or to set the preemption opinion parameter in the ARP parameter of each service data that has accessed the first network slice to not allow preemption.

[0455] Optionally, the service data to be accessed or already accessed to the first network slice is a service quality QoS flow or a packet data unit PDU session, or the service data to be accessed or already accessed to the second network slice is a service quality QoS flow or a packet data unit PDU session.

[0456] In a possible design, the device 1500 may correspond to the RAN in the above method embodiment, for example, it may be a RAN, or a chip configured in the RAN. The device 1500 is used to execute each step or process corresponding to the RAN in the above methods 200 to 1400.

[0457] Specifically, the transceiver unit 1510 is used to receive instruction information from the first network device;

[0458] The processing unit 1520 is configured to release resources used by second service data that has already accessed the first network slice for first service data to be accessed the first network slice according to the indication information; or,

[0459] The processing unit 1520 is also used to prohibit resources used by service data that has already accessed the first network slice from being preempted by any service data to be accessed the second network slice according to the indication information.

[0460] Optionally, the processing unit 1520 is specifically configured to:

[0461] If the indication information indicates that resources used by service data that have already accessed the first network slice are released for first service data to be accessed by the first network slice, or if the indication information indicates that the service usage of the first network slice is greater than or equal to the service volume upper limit of the first network slice, then resources used by second service data that have already accessed the first network slice are released for the first service data to be accessed by the first network slice.

[0462] Optionally, the processing unit 1520 is specifically configured to:

[0463] Determine, according to the indication information, that it is prohibited to preempt resources of service data that has accessed network slices other than the first network slice for first service data to be accessed to the first network slice;

[0464] According to the authorized service quality QoS parameters of the first service data and the second service data, the second service data is determined in the service data that has accessed the first network slice, wherein the priority of the first service data is higher than the priority of the second service data, and the preemption capability parameter in the allocation and retention priority ARP parameters in the authorized service quality QoS parameters of the first service data is set to allow preemption, and the preemption willingness parameter in the ARP parameters in the authorized QoS parameters of the second service data is set to allow preemption.

[0465] Optionally, the traffic volume upper limit of the first network slice is at least one of the maximum number of sessions or the maximum traffic bandwidth allowed to access the first network slice or the maximum session density allowed by the first network slice.

[0466] Optionally, the processing unit 1520 is specifically used to: if the indication information indicates that the resources used by any service data that has already accessed the first network slice are not preempted by any service data to be accessed to the second network slice, or the service usage of the first network slice is less than or equal to the lower limit of the service volume of the first network slice, it is prohibited to preempt the resources used by any service data that has already accessed the first network slice from the second service data to be accessed to the second network slice.

[0467] Optionally, the lower limit of the service volume of the first network slice is at least one of the minimum number of sessions or the minimum traffic bandwidth guaranteed by the first network slice or the minimum session density guaranteed by the first network slice.

[0468] Optionally, if the processing unit 1520 is used to prohibit the resources used by the service data that has already accessed the first network slice from being preempted by any service data to be accessed the second network slice according to the indication information, the processing unit 1520 is also used to set the preemption willingness parameter in the allocation and retention priority ARP parameters of each service data that has already accessed the first network slice to not allow preemption.

[0469] Optionally, the service data to be accessed or already accessed to the first network slice is a service quality QoS flow or a packet data unit PDU session, and the service data to be accessed or already accessed to the second network slice is a service quality QoS flow or a packet data unit PDU session.

[0470] It should be understood that the device 1500 here is embodied in the form of a functional unit. The term "unit" here may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a dedicated processor or a group processor, etc.) and a memory for executing one or more software or firmware programs, a merged logic circuit and / or other suitable components that support the described functions. In an optional example, those skilled in the art may understand that the device 1500 may be specifically the PCF in the above-mentioned embodiment, and may be used to execute the various processes and / or steps corresponding to the PCF in the above-mentioned method embodiment, or the device 1500 may be specifically the RAN in the above-mentioned embodiment, and may be used to execute the various processes and / or steps corresponding to the RAN in the above-mentioned method embodiment. To avoid repetition, it will not be repeated here.

[0471] The device 1500 of each of the above schemes has the function of implementing the corresponding steps performed by the PCF in the above method, or the device 1500 of each of the above schemes has the function of implementing the corresponding steps performed by the RAN in the above method. The function can be implemented by hardware, or the corresponding software can be implemented by hardware. The hardware or software includes one or more modules corresponding to the above functions; for example, the communication unit can be replaced by a transceiver (for example, the sending unit in the communication unit can be replaced by a transmitter, and the receiving unit in the communication unit can be replaced by a receiver), and other units, such as the processing unit, can be replaced by a processor to respectively perform the sending and receiving operations and related processing operations in each method embodiment.

[0472] In addition, the communication unit may also be a transceiver circuit (for example, may include a receiving circuit and a sending circuit), and the processing unit may be a processing circuit. Fig.12 The device in the embodiment may be a terminal device or a network device in the foregoing embodiment, or may be a chip or a chip system, such as a system on chip (SoC). The communication unit may be an input / output circuit or a communication interface; the processing unit may be a processor or a microprocessor or an integrated circuit integrated on the chip. This is not limited here.

[0473] Fig.16 The communication device 1600 provided in an embodiment of the present application is shown. The device 1600 includes a processor 1610 and a transceiver 1620. The processor 1610 and the transceiver 1620 communicate with each other through an internal connection path, and the processor 1610 is used to execute instructions to control the transceiver 1620 to send and / or receive signals.

[0474] Optionally, the device 1600 may further include a memory 1630, and the memory 1630 communicates with the processor 1610 and the transceiver 1620 through an internal connection path. The memory 1630 is used to store instructions, and the processor 1610 can execute the instructions stored in the memory 1630. In a possible implementation, the device 1600 is used to implement the various processes and steps corresponding to the PCF in the above method embodiment. In another possible implementation, the device 1600 is used to implement the various processes and steps corresponding to the RAN in the above method embodiment.

[0475] It should be understood that the device 1600 can be specifically the PCF or RAN in the above embodiment, or it can be a chip or a chip system. Correspondingly, the transceiver 1620 can be the transceiver circuit of the chip, which is not limited here. Specifically, the device 1600 can be used to execute the various steps and / or processes corresponding to the PCF or RAN in the above method embodiment. Optionally, the memory 1630 may include a read-only memory and a random access memory, and provide instructions and data to the processor. A part of the memory may also include a non-volatile random access memory. For example, the memory may also store information about the device type. The processor 1610 can be used to execute instructions stored in the memory, and when the processor 1610 executes instructions stored in the memory, the processor 1610 is used to execute the various steps and / or processes of the above method embodiments corresponding to the PCF or RAN.

[0476] In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in a processor or an instruction in the form of software. The steps of the method disclosed in conjunction with the embodiment of the present application can be directly embodied as a hardware processor for execution, or a combination of hardware and software modules in a processor for execution. The software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the above method in conjunction with its hardware. To avoid repetition, it is not described in detail here.

[0477] It should be noted that the processor in the embodiment of the present application can be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by an integrated logic circuit of hardware in the processor or an instruction in the form of software. The above processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor can be combined and performed. The software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0478] It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0479] According to the method provided in the embodiment of the present application, the present application also provides a computer program product, which includes: a computer program code, when the computer program code is run on a computer, the computer executes Figures 2 to 14 The illustrated embodiment shows various steps or processes executed by the PCF or RAN.

[0480] According to the method provided in the embodiment of the present application, the present application also provides a computer-readable storage medium, which stores a program code, and when the program code is run on a computer, the computer executes Figures 2 to 14 The illustrated embodiments include various steps or processes performed by the PCF or RAN.

[0481] According to the method provided in the embodiment of the present application, the present application also provides a communication system, which includes the aforementioned one or more ARNs and one or more PCFs, or includes Figures 2 to 14 At least two network elements in the illustrated embodiment.

[0482] In each of the above device embodiments Figures 2 to 14 In the embodiments shown and in the method embodiments Figures 2 to 14 The embodiments shown are completely corresponding, and the corresponding modules or units perform the corresponding steps. For example, the communication unit (transceiver) performs the steps of receiving or sending in the method embodiment, and the other steps except sending and receiving can be performed by the processing unit (processor). The functions of the specific units can be based on the corresponding method embodiments. Among them, the processor can be one or more.

[0483] In the present application, "indication" may include direct indication and indirect indication, and may also include explicit indication and implicit indication. The information indicated by a certain information is called information to be indicated. In the specific implementation process, there may be many ways to indicate the information to be indicated, such as but not limited to, directly indicating the information to be indicated, such as indicating the information to be indicated itself or the index of the information to be indicated. The information to be indicated may also be indirectly indicated by indicating other information, wherein the other information has an association with the information to be indicated. It is also possible to indicate only a part of the information to be indicated, while the other parts of the information to be indicated are known or agreed in advance. For example, the indication of specific information may also be achieved by means of the arrangement order of each information agreed in advance (such as specified by the protocol), thereby reducing the indication overhead to a certain extent.

[0484] In the embodiments of the present application, each term and English abbreviation is provided for the convenience of description and shall not constitute any limitation to the present application. The present application does not exclude the possibility of defining other terms that can achieve the same or similar functions in existing or future protocols.

[0485] In the embodiments of the present application, the first, second and various digital numbers are only used for the convenience of description and are not used to limit the scope of the embodiments of the present application. For example, to distinguish different network slices, to distinguish different network devices, etc.

[0486] The terms "component", "module", "system", etc. used in this specification are used to represent computer-related entities, hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program and / or a computer. By way of illustration, both applications running on a computing device and a computing device can be components. One or more components may reside in a process and / or an execution thread, and a component may be located on a computer and / or distributed between two or more computers. In addition, these components may be executed from various computer-readable storage media having various data structures stored thereon. Components may, for example, communicate through local and / or remote processes according to signals having one or more data packets (e.g., data from two components interacting with another component between a local system, a distributed system and / or a network, such as the Internet interacting with other systems through signals).

[0487] It should be understood that "at least one" in this article refers to one or more, and "plurality" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b and c can mean: a, or b, or c, or a and b, or a and c, or b and c, or a, b and c, where a, b, c can be single or multiple.

[0488] Those of ordinary skill in the art will appreciate that the various illustrative logical blocks and steps described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or in a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0489] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can be based on the corresponding processes in the aforementioned method embodiments and will not be repeated here.

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

[0491] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0492] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0493] In the above embodiments, the functions of each functional unit can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions (programs). When the computer program instructions (programs) are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server, data center, etc. that contains one or more available media integrated. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

[0494] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium, including several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

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

Claims

1. A communication method, characterized in that: include: The first network device obtains the service usage of the first network slice and the service volume threshold of the first network slice; The first network device generates indication information according to the service usage of the first network slice and the service volume threshold of the first network slice; The first network device sends the indication information to the second network device, where the indication information is used by the second network device to control resource preemption. The traffic volume threshold of the first network slice includes an upper limit of the traffic volume of the first network slice and a lower limit of the traffic volume of the first network slice; If the service usage of the first network slice is greater than or equal to the service volume upper limit of the first network slice, the indication information is used to instruct the second network device to release the resources used by the service data that has already accessed the first network slice for the first service data to be accessed by the first network slice, or the indication information is used to indicate that the allowed service usage of the first network slice is greater than or equal to the service volume upper limit of the first network slice, If the service usage of the first network slice is less than or equal to the lower limit of the service volume of the first network slice, the indication information is used to indicate that the resources used by any service data that has accessed the first network slice are not preempted by any service data to be accessed by the second network slice, or the indication information is used to indicate that the service usage of the first network slice is less than or equal to the lower limit of the service volume of the first network slice.

2. The communication method according to claim 1, characterized in that: The business volume upper limit of the first network slice is at least one of the maximum number of sessions or the maximum traffic bandwidth allowed by the first network slice or the maximum session density allowed by the first network slice.

3. The communication method according to claim 1 or 2, characterized in that: The lower limit of the service volume of the first network slice is at least one of the minimum number of sessions or the minimum traffic bandwidth guaranteed by the first network slice for access or the minimum session density guaranteed by the first network slice.

4. The communication method according to claim 1 or 2, characterized in that: The method further comprises: If the service usage of the first network slice is less than or equal to the lower limit of the service volume of the first network slice, the first network device sets the preemption willingness parameter in the allocation and retention priority ARP parameter of the first service data to not allow preemption, or the first network device sets the preemption opinion parameter in the ARP parameter of each service data that has accessed the first network slice to not allow preemption.

5. The communication method according to claim 1 or 2, characterized in that: The service data to be accessed or already accessed to the first network slice is a service quality QoS flow or a packet data unit PDU session, or the service data to be accessed or already accessed to the second network slice is a service quality QoS flow or a packet data unit PDU session.

6. A communication method, characterized in that: include: The second network device receives indication information from the first network device, where the indication information is generated based on the service usage of the first network slice and the service volume threshold of the first network slice, where the service volume threshold of the first network slice includes an upper limit of the service volume of the first network slice and a lower limit of the service volume of the first network slice; If the service usage of the first network slice is greater than or equal to the service volume upper limit of the first network slice, the indication information is used to instruct the second network device to release the resources used by the service data that has already accessed the first network slice for the first service data to be accessed by the first network slice, or the indication information is used to indicate that the allowed service usage of the first network slice is greater than or equal to the service volume upper limit of the first network slice, If the service usage of the first network slice is less than or equal to the lower limit of the service volume of the first network slice, the indication information is used to indicate that the resources used by any service data that has accessed the first network slice are not preempted by any service data to be accessed by the second network slice, or the indication information is used to indicate that the service usage of the first network slice is less than or equal to the lower limit of the service volume of the first network slice.

7. The communication method according to claim 6, characterized in that: The business volume upper limit of the first network slice is at least one of the maximum number of sessions or the maximum traffic bandwidth allowed by the first network slice or the maximum session density allowed by the first network slice.

8. The communication method according to claim 6 or 7, characterized in that: The lower limit of the service volume of the first network slice is at least one of the minimum number of sessions or the minimum traffic bandwidth guaranteed by the first network slice for access or the minimum session density guaranteed by the first network slice.

9. The communication method according to claim 6 or 7, characterized in that: If the second network device prohibits resources used by any service data that has accessed the first network slice from being preempted by any service data to be accessed the second network slice according to the indication information, the method further includes: The second network device sets the preemption willingness parameter in the allocation and retention priority ARP parameters of each service data that has accessed the first network slice to not allow preemption.

10. The communication method according to claim 6 or 7, characterized in that: The service data to be accessed or already accessed to the first network slice is a service quality QoS flow or a packet data unit PDU session, and the service data to be accessed or already accessed to the second network slice is a service quality QoS flow or a packet data unit PDU session.

11. A communication device, characterized in that: include: A transceiver unit, configured to obtain a service usage of a first network slice and a service volume threshold of the first network slice; A processing unit, configured to generate indication information according to the service usage of the first network slice and the service volume threshold of the first network slice; The transceiver unit is further used to send the indication information to the second network device, where the indication information is used by the second network device to control resource preemption. The traffic volume threshold of the first network slice includes an upper limit of the traffic volume of the first network slice and a lower limit of the traffic volume of the first network slice; If the service usage of the first network slice is greater than or equal to the service volume upper limit of the first network slice, the indication information is used to instruct the second network device to release the resources used by the service data that has already accessed the first network slice for the first service data to be accessed by the first network slice, or the indication information is used to indicate that the allowed service usage of the first network slice is greater than or equal to the service volume upper limit of the first network slice, If the service usage of the first network slice is less than or equal to the lower limit of the service volume of the first network slice, the indication information is used to indicate that the resources used by any service data that has accessed the first network slice are not preempted by any service data to be accessed by the second network slice, or the indication information is used to indicate that the service usage of the first network slice is less than or equal to the lower limit of the service volume of the first network slice.

12. The communication device according to claim 11, characterized in that: The business volume upper limit of the first network slice is at least one of the maximum number of sessions or the maximum traffic bandwidth allowed by the first network slice or the maximum session density allowed by the first network slice.

13. The communication device according to claim 11 or 12, characterized in that: The lower limit of the service volume of the first network slice is at least one of the minimum number of sessions or the minimum traffic bandwidth guaranteed by the first network slice for access or the minimum session density guaranteed by the first network slice.

14. The communication device according to claim 11 or 12, characterized in that: If the service usage of the first network slice is less than or equal to the lower limit of the service volume of the first network slice, the processing unit is also used to set the preemption willingness parameter in the allocation and retention priority ARP parameter of the first service data to not allow preemption or set the preemption opinion parameter in the ARP parameter of each service data that has connected to the first network slice to not allow preemption.

15. The communication device according to claim 11 or 12, characterized in that: The service data to be accessed or already accessed to the first network slice is a service quality QoS flow or a packet data unit PDU session, or the service data to be accessed or already accessed to the second network slice is a service quality QoS flow or a packet data unit PDU session.

16. A communication device, characterized in that: include: A transceiver unit, configured to receive indication information from a first network device, wherein the indication information is generated based on a service usage of a first network slice and a service volume threshold of the first network slice, wherein the service volume threshold of the first network slice includes an upper limit of the service volume of the first network slice and a lower limit of the service volume of the first network slice; If the service usage of the first network slice is greater than or equal to the service volume upper limit of the first network slice, the indication information is used to instruct the second network device to release the resources used by the service data that has already accessed the first network slice for the first service data to be accessed by the first network slice, or the indication information is used to indicate that the allowed service usage of the first network slice is greater than or equal to the service volume upper limit of the first network slice, If the service usage of the first network slice is less than or equal to the lower limit of the service volume of the first network slice, the indication information is used to indicate that the resources used by any service data that has accessed the first network slice are not preempted by any service data to be accessed by the second network slice, or the indication information is used to indicate that the service usage of the first network slice is less than or equal to the lower limit of the service volume of the first network slice.

17. The communication device according to claim 16, characterized in that: The business volume upper limit of the first network slice is at least one of the maximum number of sessions or the maximum traffic bandwidth allowed by the first network slice or the maximum session density allowed by the first network slice.

18. The communication device according to claim 16 or 17, characterized in that: The lower limit of the service volume of the first network slice is at least one of the minimum number of sessions or the minimum traffic bandwidth guaranteed by the first network slice for access or the minimum session density guaranteed by the first network slice.

19. The communication device according to claim 16 or 17, characterized in that: If the processing unit is used to prohibit the resources used by the service data that has already accessed the first network slice from being preempted by any service data to be accessed to the second network slice according to the indication information, the processing unit is also used to set the preemption willingness parameter in the allocation and retention priority ARP parameters of each service data that has already accessed the first network slice to not allow preemption.

20. The communication device according to claim 16 or 17, characterized in that: The service data to be accessed or already accessed to the first network slice is a service quality QoS flow or a packet data unit PDU session, and the service data to be accessed or already accessed to the second network slice is a service quality QoS flow or a packet data unit PDU session.

21. A communication device, characterized in that: include: A processor, wherein the processor is coupled to a memory, wherein the memory is used to store programs or instructions, and when the programs or instructions are executed by the processor, the communication device executes the method according to any one of claims 1 to 10.

22. A computer-readable storage medium for storing a computer program, characterized in that: The computer program comprises instructions for implementing the method of any one of claims 1-10.

23. A chip, characterized in that: include: A processor is used to read instructions stored in a memory, and when the processor executes the instructions, the chip implements the method described in any one of claims 1 to 10.

Citation Information

Cited By

  • Communication method and communication device

    WO2021139378A1