Rate control method of terminal equipment group in network slice and communication device

Abstract

The invention relates to a rate control method of a terminal equipment group in a network slice and a communication device. The rate control method and the communication device can be used for controlling and adjusting the bit rate of per slice per application per UE (User Equipment) Group granularity. In one network slice, bit rate control and adjustment can be carried out on a certain terminal device group corresponding to or belonging to the same application or service in the network slice as a whole. The terminal device group is composed of a part of terminal devices (or users) in the network slice and belongs to or runs the same application. It can be ensured that the aggregation bit rate of the terminal device group does not exceed the preset threshold value, and influences on other terminal devices or other services are avoided. And the bit rate of the terminal equipment group can be ensured to meet the lowest requirement, so that the service or application of the terminal equipment group can meet the lowest requirement of normal transmission, and the user experience is improved.

Description

Technical Field

[0001] The present application relates to the field of communications, and more specifically, to a rate control method and communication device for a terminal device group within a network slice. Background Art

[0002] Federated learning (FL) defines a machine learning framework that can effectively solve the data silo problem, allowing all participants to jointly model without sharing data, technically breaking down data silos and achieving artificial intelligence (AI) collaboration. Based on the different data source characteristics of the participating parties, federated learning can be divided into three categories: horizontal federated learning, vertical federated learning, and federated transfer learning.

[0003] In the process of horizontal federated learning, it is necessary to limit the aggregate bit rate of a selected group of terminal devices, that is, it is necessary to monitor and adjust the aggregate bit rate at the granularity of the terminal device group to avoid affecting other terminals or services.

[0004] At present, the methods for controlling and adjusting the bit rate of terminal devices on a certain network slice are all used to limit the aggregate data rate of all terminal devices in a network slice, and it is impossible to monitor and adjust the aggregate data rate for a specific terminal device group in the network slice. Therefore, the terminal device group may have an impact on other terminal devices or other services, resulting in the transmission rate of other terminal devices or other services failing to meet the requirements. In addition, it is impossible to ensure that the transmission rate of the terminal device group meets the requirements, which may affect the services or applications running on the terminal device group, affect communication efficiency, and reduce user experience. Summary of the invention

[0005] The present application provides a rate control method and communication device for a terminal device group within a network slice, which can control and adjust the bit rate at the granularity of per slice per application per UE Group, so that the bit rate of the terminal device group meets the requirements of the application or service. It avoids affecting other terminal devices or other services, and ensures that the service or application of the terminal device group can meet the minimum requirements for normal transmission, improves communication efficiency, and improves user experience.

[0006] In a first aspect, a rate control method for a terminal device group in a network slice is provided, the method comprising: a policy control function network element (PCF) obtains first information, the first information comprising: an aggregated bit rate of a first terminal device group corresponding to a first application in a first network slice, or at least one of a minimum bit rate of terminal devices in a first terminal device group corresponding to a first application in the first network slice; the policy control function network element receives second information from a data storage network element or a unified data management network element, the second information comprising: bit rate information; the policy control function network element determines an adjustment strategy based on the first information and the bit rate information, if conditions are met, the adjustment strategy being used to adjust the aggregated bit rate of the first terminal device group, or at least one of the minimum bit rates of terminal devices in the first terminal device group.

[0007] The first aspect provides a rate control method for a terminal device group within a network slice, wherein the PCF obtains at least one of the aggregated bit rate information per slice per application per UE group or the minimum bit rate information of the UE in the UE group, and obtains at least one of the maximum aggregated bit rate threshold per slice per application per UE group, the threshold of the minimum aggregated bit rate of the UE group, or the minimum bit rate threshold of the UE in the UE group. The PCF compares the aggregated bit rate of the UE group or the minimum bit rate of the UE in the UE group with the corresponding threshold to determine whether the condition is met. If not, the PCF performs a policy adjustment. In a network slice, the overall bit rate control and adjustment of a terminal device group (UE group) corresponding to or belonging to the same application (or service) in the network slice is achieved. It can ensure that the aggregated bit rate of the UE group does not exceed the requirement to avoid affecting other UEs or services. It can also ensure that the aggregated bit rate of the UE group is not lower than the set minimum aggregated bit rate to ensure the minimum requirement for normal transmission of the service, thereby improving communication efficiency.

[0008] In a possible implementation of the first aspect, the bit rate information includes: at least one of the maximum aggregation bit rate threshold of the first terminal device group, the minimum aggregation bit rate threshold of the first terminal device group, or the minimum bit rate threshold of the terminal devices in the first terminal device group; when the conditions are met, it includes: the aggregation bit rate of the first terminal device group is greater than the maximum aggregation bit rate threshold of the first terminal device group, the aggregation bit rate of the first terminal device group is less than the minimum aggregation bit rate threshold of the first terminal device group, or the minimum bit rate of the terminal devices in the first terminal device group is less than at least one of the minimum bit rate thresholds of the terminal devices in the first terminal device group. In this implementation, the accuracy of determining whether the aggregation bit rate of the UE group meets the conditions can be improved, and the accuracy of adjusting the aggregation bit rate of the first terminal device group is ensured. Exemplarily, the expression "first terminal device group" can also be replaced by: "third terminal device group".

[0009] In a possible implementation of the first aspect, the method further includes: the policy control function network element receives third information from the network open function network element, the third information includes first indication information, the first indication information is used to indicate: triggering at least one of the aggregate bit rate monitoring of the first terminal device group or the minimum bit rate monitoring of the terminal devices in the first terminal device group, and the third information also includes: the identifiers of all terminal devices in the first terminal device group or at least one of the identifiers of the first terminal device group, the identifier of the first network slice, and the identifier of the first application; in response to the third information, the policy control function network element sends a subscription request to the network analysis function network element, the subscription request is used to obtain the first information, and the subscription request includes: the identifiers of all terminal devices in the first terminal device group or at least one of the identifiers of the first terminal device group, the identifier of the first network slice, the identifier of the first application, and the analysis type identifier. The analysis type identifier is used to indicate the data volume and session-related analysis of the terminal device or the terminal device group. In this implementation, the PCF can clearly know that it needs to monitor and adjust the bit rate of the first terminal device group, and can obtain the aggregate bit rate of the first terminal device group, or the minimum bit rate of the terminal devices in the first terminal device group, thereby ensuring that the PCF can adjust the aggregate bit rate of the first terminal device group. Exemplarily, the expression "first terminal device group" can also be replaced by: "third terminal device group".

[0010] Exemplarily, the third information also includes: the identifiers (UE sub-list) of all UEs in the sub-UE group (UE sub Group) served by the PCF, which are used to identify the UE identifiers served by the PCF. When the PCF subsequently performs policy adjustments, it only makes adjustments to the UEs in the UE list served by the PCF. The subscription request also includes: the identifiers (UE sub-list) of all UEs in the sub-UE group (UE sub Group) served by the PCF, which are used to identify the UE identifiers served by the PCF. Subsequently, the NWDAF can obtain the SMF serving the UE from the corresponding PCF based on the service UE list provided by each PCF.

[0011] In a possible implementation of the first aspect, the bit rate information includes: the remaining group aggregate bit rate of the second terminal device group corresponding to the first application in the first network slice, the first terminal device group is a subset of the second terminal device group (the second terminal device group includes the first terminal device group), the policy control function network element is a policy control function network element serving the first terminal device group, and the terminal devices included in the first terminal device group are terminal devices managed by the policy control function network element; the method also includes: the policy control function network element updates the remaining group aggregate bit rate according to the aggregate bit rate of the first terminal device group in the first information; when the conditions are met, it includes: the remaining group aggregate bit rate after the update is greater than the preset first threshold, or less than the preset second threshold. In this implementation, each PCF obtains the aggregate bit rate of the sub-UE group (for example, the first UE group) for which it is responsible, and then updates the remaining group aggregate bit rate (for example, the remaining group aggregate bit rate of the third UE group) and determines whether it meets the requirements. In this way, the bit rate of the sub-UE group granularity is monitored and adjusted, and the communication efficiency is improved. Exemplarily, the expression of "second terminal device group" can also be replaced by: "third terminal device group".

[0012] Exemplarily, the Remaining Group-Aggregate Bit Rate refers to the remaining or available bit rate of a certain UE group (i.e., the remaining or available resource size of the UE group). The remaining group-aggregate bit rate is a dynamically changing value. As the bit rate of some UEs in the UE group increases, the value of the remaining group-aggregate bit rate may decrease; as the bit rate of some UEs in the UE group decreases, the value of the remaining group-aggregate bit rate may increase. For example, assuming that the identifier of the internal UE group is the identifier of the third UE group, the remaining group-aggregate bit rate refers to the remaining or available bit rate of the third UE group, which is a dynamically changing value. The first threshold value can be a preset value for comparison with the remaining group-aggregate bit rate.

[0013] In a possible implementation of the first aspect, the policy control function network element updates the aggregate bit rate of the remaining group according to the aggregate bit rate of the first terminal device group in the first information, including: the policy control function network element determines the change value of the aggregate bit rate of the first terminal device group; the policy control function network element determines the aggregate bit rate of the remaining group according to the change value, and obtains the updated aggregate bit rate of the remaining group. In this implementation, the accuracy of the updated aggregate bit rate of the remaining group can be improved, thereby ensuring the accuracy of adjusting the aggregate bit rate of the first terminal device group. Exemplarily, the expression "second terminal device group" can also be replaced by: "third terminal device group". The first terminal device group is a subset of the second terminal device group (that is, the second terminal device group includes the first terminal device group).

[0014] In a possible implementation of the first aspect, the method further includes: the policy control function network element sends the updated remaining group aggregate bit rate to the data storage network element or the unified data management network element. In this implementation, it can be ensured that the remaining group aggregate bit rate can accurately reflect the actual remaining group aggregate bit rate of the UE group.

[0015] In a possible implementation of the first aspect, the method further includes: the policy control function network element receives fourth information from the network open function network element, the fourth information includes first indication information, the first indication information indicates: triggering at least one of the aggregated bit rate monitoring of the first terminal device group or the minimum bit rate monitoring of the terminal devices in the first terminal device group, and the fourth information also includes: at least one of the identifiers of all terminal devices in the second terminal device group or the identifier of the second terminal device group, the identifier of all terminal devices in the first terminal device group or the identifier of the first terminal device group, the identifier of the first network slice, and the identifier of the first application; according to the fourth information, the policy control function network element obtains the first information. The first terminal device group is a subset of the second terminal device group. Exemplarily, the expression of "second terminal device group" can also be replaced by: "third terminal device group". In this implementation, in this implementation, the PCF can clearly need to monitor and adjust the bit rate of the first terminal device group, and the PCF can obtain the aggregated bit rate of the first terminal device group or the minimum bit rate of the terminal devices in the first terminal device group, ensuring that the PCF can adjust the aggregated bit rate of the first terminal device group.

[0016] In a possible implementation of the first aspect, the policy control function network element receives the second information from the data storage network element, including: the policy control function network element sends a query request to the data storage network element or the unified data management network element, the query request includes: the identifiers of all terminal devices in the first terminal device group or at least one of the identifiers of the first terminal device group, the identifier of the first network slice, and the identifier of the first application; or, the query request includes: the identifiers of all terminal devices in the second terminal device group or at least one of the identifiers of the second terminal device group, the identifier of the first network slice, and the identifier of the first application, wherein the second terminal device group includes the first terminal device group; the policy control function network element receives the second information from the data storage network element or the unified data management network element in response to the query request. In this implementation, the PCF can obtain the second information, ensuring that the PCF can adjust the aggregate bit rate of the first terminal device group. Exemplarily, the expression "second terminal device group" can also be replaced by: "third terminal device group".

[0017] In a possible implementation of the first aspect, the adjustment strategy includes at least one of the following: if the service quality flow of the terminal device in the first terminal device group is a guaranteed bit rate service quality flow, modify the maximum bit rate value of the guaranteed bit rate service quality flow; adjust the allocation retention priority (ARP) or priority parameter of the service quality flow of the terminal device in the first terminal device group; release the service quality flow of some terminal devices in the first terminal device group. Among them, the first terminal device group is a terminal device group served by the PCF, that is, when each PCF performs policy adjustment, it only adjusts the UEs in the UE list (UE sub-list) served by the PCF. In this implementation, it can be made that: the UE group aggregate bit rate is less than or equal to the maximum aggregate bit rate threshold of the UE group, and greater than the minimum aggregate bit rate threshold of the UE group, or the minimum bit rate of the UE in the UE group is greater than the minimum bit rate threshold of the UE in the UE group. Thereby avoiding the impact on other terminal devices or other services, and ensuring that the services or applications of the terminal device group can meet the minimum requirements of normal transmission, thereby improving communication efficiency.

[0018] In a second aspect, a rate control method for a terminal device group in a network slice is provided, the method comprising: an application function network element (AF) sends a first parameter to a data storage network element or a unified data management network element, the first parameter comprising: a maximum aggregate bit rate threshold of a third terminal device group corresponding to a first application in a first network slice, a minimum aggregate bit rate threshold of a third terminal device group, a minimum bit rate threshold of a terminal device in the third terminal device group, or at least one of the aggregate bit rates of the remaining groups of the third terminal device group, the first parameter further comprising: an identifier of all terminal devices in the third terminal device group or at least one of an identifier of the third terminal device group, an identifier of the first network slice, and an identifier of the first application; the application function network element sends a first request message to a network open function network element, the first request message comprising second indication information, an identifier of the first network slice, and an identifier of the first application; wherein the second indication information indicates: triggering at least one of aggregate bit rate monitoring of the third terminal device group or minimum bit rate monitoring of the terminal devices in the third terminal device group, and the first request message further comprising: an identifier of all terminal devices in the third terminal device group or at least one of an identifier of the third terminal device group. Exemplarily, the expression "third terminal device group" may also be replaced by: "second terminal device group". Alternatively, the expression "third terminal device group" may also be replaced by: "first terminal device group".

[0019] The second aspect provides a rate control method for a terminal device group within a network slice, wherein the AF configures at least one of the maximum aggregate bit rate threshold per Slice per Application per UE Group, the threshold for the minimum aggregate bit rate of the UE group, the minimum bit rate threshold of the UE in the UE group, and the aggregate bit rate of the remaining groups per slice per application per UE group in the UDM or UDR. The PCF is instructed to monitor the aggregate bit rate of the terminal device group so that the PCF can monitor and adjust the bit rate at the UE group granularity. This ensures that the aggregate bit rate of the UE group does not exceed the requirement to avoid affecting other UEs or services. It can also ensure that the aggregate bit rate of the UE group is not lower than the set minimum aggregate bit rate to ensure the minimum requirement for normal transmission of the service, thereby improving communication efficiency.

[0020] According to a third aspect, a rate control method for a terminal device group in a network slice is provided, the method comprising: a network open function network element (NEF) receiving a first request message from an application function network element, the first request message comprising second indication information, the second indication information being used to indicate: triggering at least one of aggregated bit rate monitoring of a third terminal device group corresponding to a first application in the first network slice, or minimum bit rate monitoring of terminal devices in the third terminal device group, the first request message further comprising: an identifier of all terminal devices in the third terminal device group or at least one of an identifier of the third terminal device group, an identifier of the first network slice, and an identifier of the first application; the network open function network element determines a set of policy control function network elements according to the first request message, the set of policy control function network elements comprising: Multiple policy control function network elements served by terminal devices in a third terminal device group; the network open function network element sends third information to each policy control function network element in the policy control function network element set, respectively, the third information includes first indication information, the first indication information is used to indicate: triggering at least one of the aggregated bit rate monitoring of the first terminal device group corresponding to the first application in the first network slice, or the minimum bit rate monitoring of the terminal devices in the first terminal device group, the third information also includes: the identification of all terminal devices in the first terminal device group or at least one of the identification of the first terminal device group, the identification of the terminal device served by the policy control function network element, the identification of the first network slice, and the identification of the first application, wherein the first terminal device group and the third terminal device group are the same terminal device group.

[0021] The third aspect provides a rate control method for a terminal device group within a network slice, where NEF instructs PCF to monitor and adjust the aggregate bit rate of the first terminal device group, so that PCF can monitor and adjust the bit rate at the UE group granularity. This ensures that the aggregate bit rate of the UE group does not exceed the requirement, avoiding impact on other UEs or services. It can also ensure that the aggregate bit rate of the UE group is not lower than the set minimum aggregate bit rate to ensure the minimum requirement for normal transmission of the service, thereby improving communication efficiency.

[0022] In a fourth aspect, a rate control method for a terminal device group in a network slice is provided, the method comprising: a network open function network element (NEF) receives a first request message from an application function network element, the first request message comprising second indication information, the second indication information being used to indicate: a policy control function network element performs at least one of aggregated bit rate monitoring of a third terminal device group corresponding to a first application in a first network slice, or performs minimum bit rate monitoring of terminal devices in the third terminal device group, the first request message further comprising: an identifier of the terminal device included in the third terminal device group or at least one of an identifier of the third terminal device group, an identifier of the first network slice, and an identifier of the first application: the network open function network element determines a policy control function network element set according to the first request message, the policy control function network element set comprising a plurality of policy control function network elements serving the terminal devices in the third terminal device group; the network The network open function network element sends fourth information to each policy control function network element in the policy control function network element set respectively, and the fourth information includes first indication information, and the first indication information is used to indicate: triggering at least one of the aggregated bit rate monitoring of the first terminal device group corresponding to the first application in the first network slice, or the minimum bit rate monitoring of the terminal devices in the first terminal device group, and the fourth information also includes: the identification of all terminal devices in the first terminal device group or at least one of the identifications of the first terminal device group, the identification of all terminal devices in the second terminal device group or at least one of the identifications of the second terminal device group, the identification of the first network slice, and the identification of the first application, wherein the terminal devices included in the first terminal device group are terminal devices managed by a policy control function network element, the second terminal device group includes the first terminal device group, and the second terminal device group and the third terminal device group are the same terminal device group.

[0023] The fourth aspect provides a rate control method for a terminal device group within a network slice, where the NEF instructs the PCF to monitor and adjust the aggregate bit rate of the first terminal device group, so that the PCF can monitor and adjust the bit rate at the UE group granularity. This ensures that the aggregate bit rate of the UE group does not exceed the requirement, avoiding impact on other UEs or services. It can also ensure that the aggregate bit rate of the UE group is not lower than the set minimum aggregate bit rate to ensure the minimum requirement for normal transmission of the service, thereby improving communication efficiency.

[0024] In a possible implementation manner of the fourth aspect, the method also includes: the network open function network element receives fifth information from each policy control function network element in the policy control function network element set, the fifth information including: the aggregated bit rate of the first terminal device group, or at least one of the minimum bit rate of the terminal devices in the first terminal device group; the network open function network element determines the aggregated bit rate of the third terminal device group, or at least one of the minimum bit rate of the terminal devices in the third terminal device group based on the fifth information; the network open function network element sends sixth information to the application function network element, the sixth information including: the sixth information includes: the aggregated bit rate of the third terminal device group, the minimum bit rate of the terminal devices in the third terminal device group, indication information for indicating that the aggregated bit rate of the third terminal device group is greater than the maximum aggregated bit rate threshold of the third terminal device group, indication information for indicating that the aggregated bit rate of the third terminal device group is less than the minimum aggregated bit rate threshold of the third terminal device group, or indication information for indicating that the minimum bit rate of the terminal devices in the third terminal device group is less than the minimum bit rate threshold of the terminal devices in the third terminal device group.

[0025] In this implementation, NEF aggregates the information fed back by different PCFs, determines the aggregate bit rate information of UE and / or the minimum bit rate of UE in the UE group, and compares the acquired aggregate bit rate of UE group and / or the minimum bit rate of UE in the UE group with the requirements in the request information of AF to determine whether the requirements can be met. If not, AF is notified, and the execution policy adjustment is triggered by AF, thereby realizing the monitoring and adjustment of the bit rate at the UE group granularity. It can ensure that the aggregate bit rate of UE group does not exceed the requirements to avoid affecting other UE or services, and it can also ensure that the aggregate bit rate of UE group is not lower than the set minimum aggregate bit rate to ensure the minimum requirements for normal transmission of services, thereby improving communication efficiency.

[0026] In a fifth aspect, a rate control method for a terminal device group within a network slice is provided, the method comprising: a data storage network element (UDR) or a unified data management network element (UDM) receives a first parameter from an application function network element, the first parameter comprising: a maximum aggregation bit rate threshold of a third terminal device group corresponding to a first application within the first network slice, a minimum aggregation bit rate threshold of the third terminal device group, a minimum bit rate threshold of a terminal device in the third terminal device group, or at least one of the aggregation bit rates of the remaining groups of the third terminal device group, the first parameter also comprises: an identifier of all terminal devices in the third terminal device group or at least one of an identifier of the third terminal device group, an identifier of the first network slice, and an identifier of the first application; the data storage network element or the unified data management network element stores the first parameter. Exemplarily, the expression "third terminal device group" may also be replaced by: "second terminal device group". Alternatively, the expression "third terminal device group" may also be replaced by: "first terminal device group".

[0027] The rate control method for the terminal device group within the network slice provided in the fifth aspect stores the first parameter in the UDR or UDM so that the PCF can obtain the first parameter, ensuring that the PCF can adjust the aggregate bit rate of the first terminal device group. This can ensure that the aggregate bit rate of the UE group does not exceed the requirements to avoid affecting other UEs or services. It can also ensure that the aggregate bit rate of the UE group is not lower than the set minimum aggregate bit rate to ensure the minimum requirement for normal transmission of the service, thereby improving communication efficiency.

[0028] In a possible implementation manner of the fifth aspect, the method also includes: the data storage network element or the unified data management network element receives a first query request from the policy control function network element, the first query request is used to query at least one of the maximum aggregation bit rate threshold of the first terminal device group corresponding to the first application in the first network slice, the minimum aggregation bit rate threshold of the first terminal device group, or the minimum bit rate threshold of the terminal devices in the first terminal device group, the first query request includes: the identifiers of all terminal devices in the first terminal device group or at least one of the identifiers of the first terminal device group, the identifier of the first network slice, and the identifier of the first application, wherein the first terminal device group and the third terminal device group are the same terminal device group; in response to the first query request, the data storage network element or the unified data management network element sends to the policy control function network element: the maximum aggregation bit rate threshold of the first terminal device group, the minimum aggregation bit rate threshold of the first terminal device group, or at least one of the minimum bit rate thresholds of the terminal devices in the first terminal device group. In this implementation, the PCF can obtain: at least one of the maximum aggregation bit rate threshold of the first terminal device group, the minimum aggregation bit rate threshold of the first terminal device group, or the minimum bit rate threshold of the terminal devices in the first terminal device group, ensuring that the PCF can adjust the aggregation bit rate of the first terminal device group. This can ensure that the aggregation bit rate of the UE group does not exceed the requirement, avoiding the impact on other UEs or services. It can also ensure that the aggregation bit rate of the UE group is not lower than the set minimum aggregation bit rate to ensure the minimum requirement for normal transmission of the service, thereby improving communication efficiency.

[0029] In a possible implementation of the fifth aspect, the method also includes: the data storage network element or the unified data management network element receives a second query request sent from the policy control function network element, the second query request is used to query the remaining group aggregate bit rate of the second terminal device group corresponding to the first application in the first network slice, or at least one of the minimum bit rate thresholds of the terminal devices in the second terminal device group, the second query request includes: the identifiers of all terminal devices in the second terminal device group or at least one of the identifiers of the second terminal device group, the identifier of the first network slice, and the identifier of the first application, wherein the second terminal device group and the third terminal device group are the same terminal device group; in response to the second query request, the data storage network element or the unified data management network element sends the remaining group aggregate bit rate of the second terminal device group or at least one of the minimum bit rate thresholds of the terminal devices in the second terminal device group to the policy control function network element; the data storage network element or the unified data management network element receives the updated remaining group aggregate bit rate sent by the policy control function network element. In this implementation, the PCF can obtain: at least one of the remaining group aggregate bit rate of the second terminal device group or the minimum bit rate threshold of the terminal device in the second terminal device group, ensuring that the PCF can adjust the aggregate bit rate of the first terminal device group (sub-UE group). This can ensure that the UE group aggregate bit rate does not exceed the requirement to avoid affecting other UEs or services. It can also ensure that the aggregate bit rate of the UE group is not lower than the set minimum aggregate bit rate to ensure the minimum requirement for normal transmission of the service, thereby improving communication efficiency.

[0030] In a sixth aspect, a method for controlling the rate of a terminal device group in a network slice is provided, the method comprising: an application function network element (AF) sending seventh information, the seventh information comprising: an identifier of all terminal devices in a third terminal device group corresponding to a first application in a first network slice or at least one of an identifier of the third terminal device group, an identifier of the first network slice, and an identifier of the first application; the application function network element receiving eighth information in response to the seventh information, the eighth information comprising: an aggregated bit rate of the third terminal device group corresponding to the first application in the first network slice, a minimum bit rate of the terminal devices in the third terminal device group corresponding to the first application in the first network slice, and an aggregated bit rate for indicating the third terminal device group. At least one of the following information: indication information for indicating that the aggregate bit rate of the third terminal device group is greater than the maximum aggregate bit rate threshold of the third terminal device group, indication information for indicating that the aggregate bit rate of the third terminal device group is less than the minimum aggregate bit rate threshold of the third terminal device group, or indication information for indicating that the minimum bit rate of the terminal devices in the third terminal device group is less than the minimum bit rate threshold of the terminal devices in the third terminal device group; the application function network element determines, based on the eighth information and if conditions are met, an adjustment strategy for adjusting at least one of the aggregate bit rate of the third terminal device group or the minimum bit rate of the terminal devices in the third terminal device group; the application function network element sends the adjustment strategy to the policy control function network element.

[0031] The sixth aspect provides a rate control method for a terminal device group within a network slice, wherein the AF obtains the aggregate bit rate information per slice per application per UE group (per Slice per Application per UE Group), or the comparison result between the aggregate bit rate of the UE group and the threshold. The AF determines whether the requirements can be met. The execution policy adjustment is triggered by the AF to implement the monitoring and adjustment of the bit rate at the UE group granularity. It can ensure that the aggregate bit rate of the UE group does not exceed the requirements to avoid affecting other UEs or services, and it can also ensure that the aggregate bit rate of the UE group is not lower than the set minimum aggregate bit rate to ensure the minimum requirements for normal transmission of the service, thereby improving communication efficiency.

[0032] In a possible implementation of the sixth aspect, the seventh information also includes second indication information, and the second indication information is used to indicate: triggering at least one of the aggregate bit rate monitoring of the third terminal device group, or the minimum bit rate monitoring of the terminal devices in the third terminal device group. In this implementation, the PCF can clearly know the need to monitor and adjust the bit rate of the first terminal device group, and the PCF can obtain the aggregate bit rate of the sub-UE group it serves, or the minimum bit rate of the terminal devices in the sub-UE group, so that the AF can monitor and adjust the bit rate at the UE group granularity. In turn, it can ensure that the aggregate bit rate of the UE group does not exceed the requirements to avoid affecting other UEs or services. It can also ensure that the aggregate bit rate of the UE group is not lower than the set minimum aggregate bit rate to ensure the minimum requirement for normal transmission of the service, thereby improving communication efficiency.

[0033] In a possible implementation manner of the sixth aspect, the seventh information also includes: at least one of: a maximum aggregation bit rate threshold of the third terminal device group, a minimum aggregation bit rate threshold of the third terminal device group, or a minimum bit rate threshold of the terminal devices in the third terminal device group.

[0034] In a possible implementation of the sixth aspect, when the condition is met, it includes: at least one of the following conditions is met: the aggregate bit rate of the third terminal device group is greater than the maximum aggregate bit rate threshold of the third terminal device group, the aggregate bit rate of the third terminal device group is less than the minimum aggregate bit rate threshold of the third terminal device group, or the minimum bit rate of the terminal devices in the third terminal device group is less than the minimum bit rate threshold of the terminal devices in the third terminal device group. In this implementation, the accuracy of determining whether the aggregate bit rate of the UE group meets the condition can be improved, and the accuracy of adjusting the aggregate bit rate of the first terminal device group is ensured.

[0035] In a possible implementation of the sixth aspect, the adjustment strategy includes at least one of the following: if the service quality flow of the terminal device in the third terminal device group is a guaranteed bit rate service quality flow, modify the maximum bit rate value of the guaranteed bit rate service quality flow; adjust the allocation maintenance priority or priority parameter of the service quality flow of the terminal device in the third terminal device group; release the service quality flow of some terminal devices in the third terminal device group. In this implementation, it can be made that: the UE group aggregate bit rate is less than or equal to the maximum aggregate bit rate threshold of the UE group, and greater than the minimum aggregate bit rate threshold of the UE group, or the minimum bit rate of the UE in the UE group is greater than the minimum bit rate threshold of the UE in the UE group. Thereby avoiding the impact on other terminal devices or other services, and ensuring that the services or applications of the terminal device group can meet the minimum requirements for normal transmission, thereby improving communication efficiency.

[0036] In the seventh aspect, a rate control method for a terminal device group in a network slice is provided, the method comprising: a policy control function network element (PCF) receives fourth information from a network open function network element, the fourth information comprising first indication information, the first indication information being used to indicate: triggering at least one of aggregated bit rate monitoring of a first terminal device group corresponding to a first application in a first network slice, or minimum bit rate monitoring of terminal devices in the first terminal device group, the fourth information comprising: at least one of the identifiers of all terminal devices in the first terminal device group or the identifier of the first terminal device group, the identifier of the first network slice, and the identifier of the first application, the policy control function network element being a policy control function network element serving the first terminal device group; according to the fourth information, the policy control function network element obtains at least one of the aggregated bit rate of the first terminal device group or the minimum bit rate of the terminal devices in the first terminal device group; the policy control function network element sends at least one of the aggregated bit rate of the first terminal device group or the minimum bit rate of the terminal devices in the first terminal device group to the network open function network element.

[0037] In the seventh aspect, the rate control method for the terminal device group in the network slice provided by PCF can determine at least one of the aggregate bit rate of the sub-UE group (first terminal device group) served by itself or the minimum bit rate of the terminal devices in the sub-UE group, and send it to NEF, so that NEF determines at least one of the aggregate bit rate of the third terminal device group or the minimum bit rate of the terminal devices in the sub-third terminal device group, thereby judging whether the requirements can be met. If the requirements are not met, the execution policy adjustment is triggered to realize the monitoring and adjustment of the bit rate at the UE group granularity.

[0038] In an eighth aspect, a rate control method for a terminal device group in a network slice is provided, the method comprising: a network analysis function network element (NWDAF) receives request information from a policy control function network element or a network open function network element, the request information comprising: an identifier of all terminal devices in a third terminal device group corresponding to a first application in a first network slice or at least one of the identifiers of the third terminal device group, an identifier of the first network slice, an identifier of the first application, and an analysis type identifier; the network analysis function network element determines, according to the request information, an aggregate bit rate of the third terminal device group, or at least one of the minimum bit rates of the terminal devices in the third terminal device group; the network analysis function network element sends ninth information to the policy control function network element or the network open function network element, the ninth information comprising: an aggregate bit rate of the third terminal device group, or at least one of the minimum bit rates of the terminal devices in the third terminal device group. Exemplarily, the expression "third terminal device group" may also be replaced by: "second terminal device group". Alternatively, the expression "third terminal device group" may also be replaced by: "second terminal device group".

[0039] In the eighth aspect, the rate control method of the terminal device group in the network slice provided by the NWDAF can determine at least one of the aggregate bit rate of the third terminal device group or the minimum bit rate of the terminal devices in the third terminal device group, and send it to the NEF or PCF, so that the NEF or PCF determines at least one of the aggregate bit rate of the third terminal device group or the minimum bit rate of the terminal devices in the sub-third terminal device group, thereby judging whether the requirements can be met. If the requirements are not met, the execution policy adjustment is triggered, thereby realizing the monitoring and adjustment of the bit rate at the UE group granularity.

[0040] In a possible implementation manner of the eighth aspect, the request information also includes: the request information also includes: the maximum aggregation bit rate threshold of the third terminal device group, the minimum aggregation bit rate threshold of the third terminal device group, or at least one of the minimum bit rate thresholds of the terminal devices in the third terminal device group; the ninth information also includes: indication information for indicating that the aggregation bit rate of the third terminal device group is greater than the maximum aggregation bit rate threshold of the third terminal device group, indication information for indicating that the aggregation bit rate of the third terminal device group is less than the minimum aggregation bit rate threshold of the third terminal device group, or at least one of the indication information for indicating that the minimum bit rate of the terminal devices in the third terminal device group is less than the minimum bit rate threshold of the terminal devices in the third terminal device group.

[0041] In the ninth aspect, a communication device is provided, which includes a module or unit for executing each step in any one of the above aspects from the first to the seventh, or any possible implementation method in any one of the aspects from the first to the eighth. The module or unit can be a hardware circuit, or it can be software, or it can be a hardware circuit combined with software. The communication device can be a core network element (for example, a PCF, NEF, AF, NWDAF, UDM, or UDR), or it can be a device in a core network element (for example, a chip, or a chip system, or a circuit), or it can be a device that can be used in combination with a core network element.

[0042] In a possible implementation of the ninth aspect, the communication device includes a transceiver unit (also referred to as an interface module) and a processing unit (also referred to as a processing module). The processing unit is used to control the transceiver unit to perform signal transmission and reception. The processing unit is used to process data or information, etc.

[0043] In the tenth aspect, a communication device is provided, which includes at least one processor for executing the method of any one of the first to eighth aspects above, or for executing the method in any possible implementation of any one of the first to eighth aspects.

[0044] In the eleventh aspect, a communication device is provided, which includes at least one processor and an interface circuit, the interface circuit is used to output and / or input signals, and the at least one processor is used to execute: the method of any one of the first to eighth aspects above, or the method of any possible implementation of any one of the first to eighth aspects above.

[0045] In the twelfth aspect, a core network network element is provided, which includes the communication device provided in the ninth aspect, or includes the communication device provided in the tenth aspect, or includes the communication device provided in the eleventh aspect.

[0046] Exemplarily, the core network element may be: PCF, NEF, AF, NWDAF, UDM or UDR.

[0047] In the thirteenth aspect, a computer program product is provided, which includes a computer program, which, when executed by a processor, is used to execute: the method of any one of the first to eighth aspects above, or the method of any possible implementation of any one of the first to eighth aspects above.

[0048] In a fourteenth aspect, a computer-readable storage medium is provided, in which a computer program is stored. When the computer program is executed, it is used to execute: the method of any one of the first to eighth aspects above, or the method of any possible implementation of any one of the first to eighth aspects above.

[0049] In the fifteenth aspect, a chip is provided, which includes: a processor for executing a computer program or instruction in a memory, so that a communication device equipped with the chip executes: a method in any one of the first to eighth aspects above, or a method in any possible implementation manner in any one of the first to eighth aspects above. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] Figure 1 This is a schematic diagram of horizontal federated learning.

[0051] Figure 2 This is a schematic diagram of the horizontal federated learning model training process using 5GS for intermediate result transmission.

[0052] Figure 3 This is a schematic diagram of an example of AF configuring corresponding parameters in UDR through the external parameter provision process.

[0053] Figure 4 This is a schematic diagram of an example of AF configuring corresponding parameters to a core network element.

[0054] Figure 5 This is a schematic diagram of an example of a communication system architecture provided by the present application and applicable to the method of the present application.

[0055] Figure 6 This is a schematic interactive diagram of a rate control method for a terminal device group within a network slice provided in the present application.

[0056] Figure 7 This is a schematic interactive diagram of another example of a rate control method for a terminal device group within a network slice provided by the present application.

[0057] Figure 8 This is a schematic interactive diagram of another example of a rate control method for a terminal device group within a network slice provided in the present application.

[0058] Fig. 9 This is a schematic interactive diagram of another example of a rate control method for a terminal device group within a network slice provided in the present application.

[0059] Fig.10 This is a schematic interactive diagram of another example of a rate control method for a terminal device group within a network slice provided in the present application.

[0060] Fig.11 It is a schematic block diagram of the communication device structure of an embodiment of the present application.

[0061] Fig.12 It is a schematic block diagram of the communication device structure of another embodiment of the present application.

[0062] Fig.13 It is a schematic block diagram of the chip system structure of an embodiment of the present application. DETAILED DESCRIPTION

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

[0064] In the description of the embodiments of the present application, unless otherwise specified, " / " means or, for example, A / B can mean A or B; "and / or" in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, "multiple" means two or more than two.

[0065] In the following, the terms "first" and "second" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of this embodiment, unless otherwise specified, "plurality" means two or more.

[0066] Various aspects or features of the present application may be implemented as methods, devices, or products using standard programming and / or engineering techniques. The term "product" used in the present application covers computer programs that can be accessed from any computer-readable device, carrier, or medium. For example, computer-readable media may include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks, or tapes, etc.), optical disks (e.g., compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROM), cards, sticks, or key drives, etc.). In addition, the various storage media described herein may represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data.

[0067] Federated learning defines a machine learning framework that can solve the problem of different data owners collaborating without exchanging data. It can effectively help multiple institutions use data and conduct machine learning modeling while meeting the requirements of user privacy protection, data security, and government regulations. As a distributed machine learning framework, federated learning can effectively solve the problem of data silos, allowing all participants to jointly model without sharing data, technically breaking down data silos and achieving AI collaboration. Based on the different data source characteristics of the participating parties, federated learning can be divided into three categories: horizontal federated learning, vertical federated learning, and federated transfer learning.

[0068] When the user features of two datasets overlap a lot but the users overlap less, the datasets are split horizontally (i.e., user dimension) and the data with the same user features but different users are taken out for training. This method is called horizontal federated learning. Figure 1As shown, it is assumed that the data set of operator A contains the data of user 1, user 2, user 3, and user 4. Among them, the data of each user contains feature 1, feature 2, feature 3, feature 4, and feature 5. The data set of operator B contains the data of user 4, user 5, user 6, user 7, and user 8, and the data of each user contains feature 2, feature 3, feature 4, feature 5, and feature 6. It can be seen that the user intersection of the data set of operator A and the data set of operator B is very small, but most of the user features are the same. The part of the data in the data set of operator A and the data set of operator B with the same user features but different users (i.e. feature 2, feature 3, feature 4, feature 5) can be used for horizontal federated learning model training.

[0069] Currently, in the process of training horizontal federated learning models, the 5G system (5G system, 5GS) can be used to transmit intermediate results. For example, Figure 2 The figure shows a schematic diagram of a horizontal federated learning model training process using 5GS for intermediate result transmission. Figure 2 As shown, first, each user equipment (UE) (UE1, UE 2...UE K) needs to download the latest training model from the server (Server) through 5GS, and then iterate the model training process. The iteration process generally includes the following steps:

[0070] Step 1: Each participant (i.e., each UE) calculates the model gradient using local data, and then encrypts the gradient and uploads it to the server;

[0071] Step 2: The server aggregates the model gradient (for example, averaging the model gradients fed back by all UEs) and updates the model gradient;

[0072] Step 3: The server distributes the updated model gradient to each participant;

[0073] Step 4: All participants update their local model gradients based on the updated model gradients.

[0074] For horizontal federated learning at the application layer, in order to ensure the efficiency and quality of model training, the application function network element (AF) needs to select a group of suitable UEs (i.e., UE Group) to participate in model training. After that, AF will establish a session with the selected group of UEs to transmit the intermediate data of FL model training. During the FL model training process, in order to avoid affecting other UEs or services. The application service provider (ASP) and the mobile network operator (MNO) generally sign a service-level agreement (SLA) to agree on the maximum aggregate bit rate between specific FL service endpoints (selected UE group and application server (AS)), or may also agree on the minimum aggregate bit rate between specific FL service endpoints (selected UE group and AS) to ensure the minimum bit rate requirement of FL service.

[0075] In other words, in the horizontal federated learning process at the application layer, it is necessary to limit the aggregate bit rate of a selected group of UEs to avoid affecting other UEs or services. In addition, the selected group of UEs and other UEs belong to or correspond to the same network slice.

[0076] At present, the technologies related to the bit rate of UE on a certain network slice (in this application, network slice can also be referred to as slice, both have the same meaning and can be replaced with each other) mainly include the following three. In the embodiment of the present application, the bit rate of UE can be understood as the size of the transmission rate when UE transmits data or the size of the resources occupied. The bit rate of UE can also be referred to as the bit rate of UE, the data rate of UE, etc.

[0077] The first type: The 17th version (3GPP R17) released by the 3rd Generation Partnership Project (3GPP) introduced slice (Slice)-maximum bit rate (maximum bit rate, MBR)-single network slice selection assistance information (S-NSSAI), or it can also be called: "Slice-MBR per S-NSSAI". Among them, S-NSSAI is used to identify a network slice type; or it can be understood that S-NSSAI is used to identify a network slice; or it can be understood that S-NSSAI is the identification information of a network slice. Slice-MBR per S-NSSAI is mainly used to limit the maximum aggregate data rate of the guaranteed bit rate (guaranteed bit rate, GBR) and non-guaranteed bit rate (Non-GBR) of all UEs in a slice. In an embodiment of the present application, the aggregate data rate (i.e., the aggregate bit rate) can be understood as the sum of the bit rates corresponding to multiple UEs respectively. For example, the sum of the bit rates corresponding to all UEs in a slice can be called the aggregate bit rate of the UEs in the slice. Slice-MBR per S-NSSAI monitoring (also known as Slice-MBR monitoring) is divided into two methods: one is Slice-MBR monitoring assisted by the network data analysis function (NWDAF) network element, and the other is Slice-MBR monitoring based on the policy control function (PCF) network element.

[0078] For Slice-MBR monitoring based on NWDAF assistance, network slicing-related policy control supports operators to limit the maximum aggregate data rate of each slice by configuring the "uplink and / or downlink maximum slice data rate". NWDAF can provide the PCF with the data volume statistics (Data Volume Dispersion Analytics) of all UEs on the slice. PCF calculates the aggregate bit rate of all UEs on the network slice based on this and compares it with the "maximum slice data rate". One or more PCFs can be deployed on a network slice, and each PCF can serve multiple UEs, or in other words, each PCF can correspond to or be responsible for multiple UEs. If multiple PCFs are deployed on the S-NSSAI, each PCF subscribes to the "uplink and / or downlink maximum slice data rate" to NWDAF respectively and makes a judgment.

[0079] For PCF-based Slice-MBR monitoring, if the PCF cannot obtain the data volume statistics of all UEs in the slice from the NWDAF, the "remaining maximum slice data rate" of a slice is maintained by the unified data repository (UDR). The "remaining maximum slice data rate" corresponding to a slice is a dynamically changing value. As the data rate used by all UEs in the slice increases (that is, the aggregate bit rate of all UEs in the slice increases), the value of the "remaining maximum slice data rate" will decrease. Each PCF interacts with the UDR to obtain and update the value. For example, the PCF can determine the increase value (that is, the increase amount) of the data rate used by the multiple UEs it is responsible for, that is, the PCF can determine the change amount of the aggregate bit rate of the multiple UEs it is responsible for, and the "remaining maximum slice data rate" obtained from the UDR minus the increase value (or the change amount) can be used to obtain the updated "remaining maximum slice data rate", and then the updated "remaining maximum slice data rate" is continued to be stored in the UDR, and the corresponding policy control is performed according to the value. If multiple PCFs are deployed on S-NSSAI (i.e., multiple PCFs are deployed on one network slice), each PCF can obtain or update the value from UDR, and use the Etags mechanism to ensure that the "remaining maximum slice data rate" in UDR can be correctly updated. Each PCF can also subscribe to the change notification of network slice-specific policy control information from UDR, so that after the "remaining maximum slice data rate" stored in UDR changes, UDR can promptly send a notification of "remaining maximum slice data rate change" to PCF. When the "remaining maximum slice data rate" is relatively large, PCF can configure a "local remaining maximum slice data rate", and only when the "local remaining maximum slice data rate" reaches a specific threshold or passes a specific time window (time period), PCF interacts with UDR to obtain the "remaining maximum slice data rate". By configuring the "local remaining maximum slice data rate" by PCF, PCF can avoid frequent interaction with UDR to obtain the "remaining maximum slice data rate", thereby reducing the consumption of communication resources. For example, the value of the "local remaining maximum slice data rate" configured by PCF is smaller than the value of the "remaining maximum slice data rate".

[0080] When the PCF finds that the data rate used by the current network slice (i.e., the aggregate bit rate of the UE on the current network slice) is about to exceed or has exceeded the "maximum slice data rate", or when the PCF finds that the "remaining maximum slice data rate" of the current network slice is close to zero, the PCF will make corresponding policy adjustments. For example, specific policy adjustments may include the following:

[0081] Reject new session management (SM) policy associations. For example, the session management function (SMF) network element will reject the establishment of new packet data unit (PDU) sessions;

[0082] Reject new GBR service data flows with high GBR requirements;

[0083] Modify the value of the authorized session aggregation maximum bit rate (Session-AMBR) (if the home public land mobile network (HPLMN) allows it);

[0084] Modify the MBR value in the policy and charging control (PCC) rules of GBR service data flows;

[0085] In addition, the PCF must meet some adjustment criteria when performing policy adjustments. For example, try to avoid frequent policy decisions that trigger signaling interactions with the UE (such as changing the authorized Session-AMBR or changing the MBR of the GBR service data flow); for example, according to the operator's policy, it is also possible to accept new PDU sessions or PCC rules belonging to the GBR service data flow that exceed the maximum slice data rate and apply different billing to them.

[0086] In summary, the first solution mentioned above is used to limit the aggregate data rate of all UEs in the slice, and it is impossible to monitor and adjust the aggregate data rate for a specific UE group.

[0087] Second: External parameter provision scheme:

[0088] AF can configure the corresponding parameters in UDR through the external parameter provision process, for example Figure 3 As shown, Figure 3 The process shown includes:

[0089] Step 0: The network function (NF) sends a subscriber data management (SDM) subscription request (Nudm_SDM_Subscribe request) to the unified data management (UDM) network element.

[0090] In step 0b, AF subscribes and receives from NWDAF UE Mobility analytics and / or UE Communication Analytics.

[0091] In step 0c, the AF validates the received data and derives the expected UE behaviour parameters.

[0092] Step 1 to Step 2: AF sends a parameter provision create / update / delete request (ParameterProvision_Create / Update / Deleterequest) to UDM through the network exposure function (NEF).

[0093] Step 3 to Step 4: UDM configures the parameters provided by AF into UDR.

[0094] Step 5 to Step 6: UDM sends a parameter provision create / update / delete response message (ParameterProvision_Create / Update / Delete response) to AF through NEF, indicating whether the operation is successful.

[0095] Step 7: UDM sends SDM notification (Nudm_SDM_Notification Notify) to NF.

[0096] The second solution mentioned above is mainly used for AF to provide configuration parameters to network elements, and is not used to limit the aggregate data rate of UE groups within a slice.

[0097] The third solution is to establish an AF session that meets the required quality of service flows (QoS).

[0098] For example Figure 4 As shown, the AF can request the PCF to create an AF session and specify the QoS requirements of the AF session through the following process. Figure 4 The process shown includes:

[0099] Step 1-Step 3 (including Step 3a and Step 3b): The AF sends a request (sessionWithQoS_Create request) to create an AF session that meets specific QoS requirements to the PCF through the NEF.

[0100] Step 4 to step 5 (including step 4, step 4a, step 4b, step 5): PCF sends a response message to AF through NEF, indicating whether the creation of the AF session that meets the specific QoS requirements is successful.

[0101] Step 6 to step 8 (including step 6, step 6a, step 7, step 7a, step 7b, step 8): PCF sends a policy authorization notification to AF through NEF and time sensitive communication and time synchronization function network element (time sensitive communication and time synchronization function, TSCTSF).

[0102] The third solution mentioned above is mainly used for AF to request the network to set session QoS parameters, and is not used to limit the aggregate data rate of the UE group within the slice.

[0103] In view of this, the present application provides a rate control method and communication device for a terminal device group within a network slice, which can control and adjust the bit rate at a granularity of per slice per application per UE group (per Slice per Application per UE Group), so that the bit rate of the terminal device group meets the requirements of the application or service. In other words, within a network slice, the bit rate of a terminal device group corresponding to or belonging to the same application (or service) in the network slice can be controlled and adjusted as a whole. The terminal device group (user group) is composed of some terminal devices (or users) within the network slice, and belongs to or runs the same application. It can ensure that the aggregate bit rate of the terminal device group does not exceed the preset threshold to avoid affecting other terminal devices or other services. In addition, it can also ensure that the bit rate of the terminal device group meets the minimum requirements to ensure that the services or applications of the terminal device group can meet the minimum requirements for normal transmission, thereby improving communication efficiency and user experience.

[0104] The method provided in this application is described below with reference to specific examples.

[0105] First, a schematic diagram of a communication system architecture applicable to the present application is described.

[0106] Figure 5 The figure shows a schematic diagram of a communication system architecture that can be applied to the present application. Figure 5As shown, the communication system mainly includes: terminal equipment, access network equipment, various core network elements and a data network (DN).

[0107] Figure 5 The terminal device in the invention can be used to connect to the access network device deployed by the operator through the wireless air interface, and then connect to the data network through the core network network element (such as the user plane function (UPF) network element); the access network device is mainly used to implement wireless physical layer functions, resource scheduling and wireless resource management, wireless access control and mobility management functions; the core network network element can be used for device registration, security authentication, mobility management and location management of the terminal device; or, it can also be used to establish a channel with the terminal device, and forward data packets between the terminal device and the external data network on the channel; the data network can correspond to a variety of different service domains, such as IP multimedia subsystem (IP multimedia subsystem, IMS), Internet (Internet), Internet protocol television (internet protocol television, IPTV), other operator service domains, etc., and is mainly used to provide a variety of data service services for terminal devices.

[0108] It should be noted that Figure 5 This is only an exemplary architecture diagram and should not impose any limitations on the communication system applicable to the embodiments of the present application. Figure 5 In addition to the functional units shown in , the network architecture may also include other functional units or functional network elements, which are not limited in the embodiments of the present application. Figure 5 The fifth generation (5G) communication system network architecture is shown, but the embodiments of the present application are also applicable to future new communication system network architectures, such as the sixth generation (6G) communication system network architecture.

[0109] exist Figure 5In the architecture shown, the terminal device can be a device with wireless transceiver function, which can also be called user equipment (UE). The terminal device can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.). The terminal device can be a mobile phone, a tablet computer (pad), a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc.

[0110] exist Figure 5In the architecture shown, the access network device can be an access network (AN) / radio access network (RAN) device, a network composed of multiple 5G-AN / 5G-RAN nodes. For example, the 5G-AN / 5G-RAN node can be: an access point (AP), a base station (BS), a central unit (CU) and a distributed unit (DU) separated gNB, a transmission receive point (TRP), a transmission point (TP) or some other access node. It can also be a base station (NodeB, NB) in a wideband code division multiple access (WCDMA) system, an evolutionary base station (Evolutional NodeB, eNB or eNodeB) in an LTE system, or an open access network (open RAN, O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system. Alternatively, the access network device may be a relay station, an access point (WiFi AP) in wireless fidelity technology, a global interoperability for microwave access (WiMAX), a network device in a 5G network, or an access network device in a future evolved public land mobile network (PLMN), etc., and the embodiments of the present application are not limited thereto.

[0111] In one possible scenario, an access network device, or a wireless access network device, may also be referred to as a RAN node. A RAN node may be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next generation NodeB (gNB), a next generation base station in a sixth generation (6G) mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system. A RAN node may be a macro base station, a micro base station or an indoor station, a relay node or a donor node, or a wireless controller in a CRAN scenario. Optionally, a RAN node may also be a server, a wearable device, a vehicle or an onboard device, etc. For example, an access network device in a vehicle to everything (V2X) technology may be a road side unit (RSU). All or part of the functions of the RAN node in this application may also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (e.g., a cloud platform). The RAN node in the present application may also be a logical node, a logical module or software that can implement all or part of the RAN node functions.

[0112] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, and different RAN nodes respectively implement part of the functions of the base station. For example, the RAN node can be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU can be set separately, or can also be included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or a radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU) or a remote radio head (RRH).

[0113] exist Figure 5In the example shown, the core network elements may include: unified data management network element (UDM), operations, administration and management network element (OAM), access and mobility management function (AMF), session management function (SMF), PCF, AF, binding support function (BSF) network element, network exposure function network element (NEF), network storage function network element (NRF), NWDAF, UDR, etc.

[0114] Exemplarily, the NWDAF network element can provide network data analysis functions. For example, the NWDAF has data collection, training, analysis, and reasoning functions, and can be used to collect relevant data from other network elements, third-party service servers, terminal devices, or network management systems, perform analysis and training based on the relevant data, and provide data analysis results to other network elements, third-party service servers, terminal devices, or network management systems. The analysis results can assist the network in selecting service quality parameters for services, or assist the network in executing traffic routing, or assist the network in selecting background data transmission strategies, etc.

[0115] AF can meet the requirements of the application side to the network side, such as QoS requirements or user status event subscription, etc. AF can be a third-party functional entity or an application server deployed by the operator.

[0116] NEF is mainly responsible for providing 5G network capabilities and events to the outside world, as well as receiving relevant external information.

[0117] PCF is mainly responsible for the generation of UE access strategy and QoS flow control strategy.

[0118] UDR mainly provides storage capabilities for contract data, policy data, and capability exposure related data.

[0119] It should be understood that the above description of the functions of each core network element is merely exemplary and should not impose any limitations on the functions of each core network element in the embodiments of the present application.

[0120] exist Figure 5In the communication system shown in the figure, each device can establish a connection through the next generation network (NG) interface to achieve communication, such as: the terminal device establishes an air interface connection with the RAN device through the new radio (NR) interface to transmit user plane data and control plane signaling; the access network device (for example, AN / RAN device) can establish a control plane signaling connection with the AMF through the NG interface 2 (referred to as N2); the access network device (for example, AN / RAN device) can establish a user plane signaling connection with the UPF through the NG interface 3 (referred to as N3); the UPF can establish a control plane signaling connection with the SMF through the NG interface 4 (referred to as N4); the UPF can exchange user plane data with the data network through the NG interface 6 (referred to as N6).

[0121] exist Figure 5 In the communication system shown in the figure, each core network element can also communicate with other core network elements through the provided interface. For example, AMF can communicate with other core network elements through the Namf interface provided by itself; SMF can communicate with other core network elements through the Nsmf interface provided by itself; BSF can communicate with other core network elements through the Nbsf interface provided by itself, etc.

[0122] It should be understood that the interface names between network elements in the embodiments of the present application are merely exemplary, and the interfaces between network elements may also have other names, and the present application does not limit the names of the interfaces.

[0123] The method provided by this application is described below with reference to specific examples. The method provided by this application can be applied in Figure 5 The architecture shown can, of course, also be applied to other architectures, and the embodiments of the present application are not limited thereto.

[0124] It should be understood that in the embodiments of the present application, each network element is used as an example to illustrate the method. As an example but not a limitation, the network element in the present application may also be a chip, a chip system, or a processor that supports the network element to implement the method; or, it may also be a logical node, a logical module, or software that can implement all or part of the network element functions.

[0125] It should also be understood that in the present application, "sending information to...(network element)" can be understood as the destination end of the information being the network element. It can include sending information to the network element directly or indirectly. "Receiving information from...(network element) or receiving information from the network element" can be understood as the source end of the information being the network element, which can include receiving information from the network element directly or indirectly. The information may be processed as necessary between the source end and the destination end of the information transmission, such as format changes, etc., but the destination end can understand the valid information from the source end. Similar expressions in the present application can be understood similarly and will not be repeated here.

[0126] Figure 6 is a schematic interactive diagram of a method for controlling the rate of a terminal device group in a network slice according to an embodiment of the present application. The method 600 can be applied in Figure 5 The scenario shown can of course also be applied to other communication scenarios, and the embodiments of the present application are not limited here.

[0127] Figure 6 In the process shown, the AF configures the maximum bit rate requirement (Group-MBR) and / or minimum bit rate requirement per slice per application per UE group in the UDR or UDM, and the PCF obtains the aggregate bit rate monitoring result per slice per application per UE group from the NWDAF, and then compares it with the maximum bit rate requirement and / or minimum bit rate requirement in the UDR or UDM. When it is determined that the aggregate bit rate of the current UE group does not meet the requirements, the PCF executes the corresponding adjustment strategy. Figure 6 As shown, Figure 6 The method 600 shown in FIG. 6 may include S601 to S613. Figure 6 Each step in method 600 is described in detail.

[0128] S601, AF configures parameters and applicable conditions of the parameters in UDM or UDR through the External Parameter Provisioning process.

[0129] The configuration parameters include at least one of the following:

[0130] The maximum aggregate bit rate threshold of the UE group (Group-MBR for UL / DL), the minimum aggregate bit rate threshold of the UE group (Group-Min-BR for UL / DL), and the minimum bit rate threshold of the UE in the UE group (Min BitRate of UE for UL / DL).

[0131] The maximum aggregate bit rate threshold of the UE group indicates: the maximum aggregate bit rate requirement of the UE group in uplink or downlink. Of course, the maximum aggregate bit rate threshold of the UE group may also be referred to as "Group-MBR", etc., which is not limited in the embodiments of the present application.

[0132] The minimum aggregate bit rate threshold of the UE group indicates: the minimum aggregate bit rate requirement of the UE group in uplink or downlink. Of course, the minimum aggregate bit rate threshold of the UE group may also be referred to as "Group-Min-BR", etc., which is not limited in the embodiments of the present application.

[0133] The minimum bit rate threshold of the UE in the UE group represents: the minimum bit rate requirement that each UE in the UE group (Group) must meet in uplink or downlink. Of course, Min BitRate of UE for UL / DL can also be called "Min BitRate of UE" or other names, etc., and the embodiments of the present application are not limited here.

[0134] The applicable conditions of the parameters (or can be called the applicable conditions of the configuration parameters) include: the identifiers of all UEs in the internal UE group or at least one of the identifiers of the internal UE group, the network slice identifier (S-NSSAI), and the application identifier (ApplicationID).

[0135] Among them, the network slice identifier (S-NSSAI) is used to identify a network slice, which corresponds to or includes multiple UEs, and these UEs can run or correspond to different applications. The application identifier (Application ID) is used to identify an application, and the internal UE group identifier (Internal Group ID) is used to identify a UE group.

[0136] In the embodiment of the present application, the identifier of the internal UE group can be understood as the identifier of the UE group that can be identified by each core network element (such as PCF, NWDAF, etc.) inside the core network, and the corresponding identifier is the external UE group identifier (ExternalGroup ID). The identifier of the external UE group can be understood as the identifier of the UE group that can be identified by the network element (such as AF) outside the core network. For the same group of UEs, the corresponding external UE group identifier and the internal UE group identifier are different. However, the UEs included in the external UE group and the UEs included in the corresponding internal UE group are the same, that is, the UEs included in the external UE group and the internal UE group refer to the same UE group.

[0137] The applicable conditions of the above parameters can be understood as: a UE group (Group) consisting of UEs running or belonging to the application identified by the Application ID within the network slice identified by the S-NSSAI; or, a UE group (Group) consisting of the identifiers of all UEs in the internal UE group among all UEs running or belonging to the application identified by the Application ID within the network slice identified by the S-NSSAI. It can be understood that other UEs may also exist on the network slice, running or belonging to other applications. In other words, the UE group (Group) is a UE group consisting of all or part of the UEs within the network slice identified by the S-NSSAI.

[0138] It should also be understood that in S601, the UE group in the maximum aggregate bit rate threshold of the UE group, the minimum aggregate bit rate threshold of the UE group, the minimum bit rate threshold of the UE in the UE group, and the UE group identified by the internal UE group identifier (Internal Group ID) are the same UE group. In other words, the UE group in the maximum aggregate bit rate threshold of the UE group (Group-MBR for UL / DL), the minimum aggregate bit rate threshold of the UE group (Group-Min-BR for UL / DL) and the minimum bit rate threshold of the UE in the UE group (Min BitRate of UE for UL / DL) is: the UE group (Group) composed of UEs running or belonging to the application identified by the Application ID within the network slice identified by the S-NSSAI. In other words, there is a corresponding (mapping) relationship between the applicable conditions of the above-mentioned configuration parameters and the configuration parameters.

[0139] For example, assuming that the parameter application conditions in S601 include: a first network slice identifier, an identifier of a first application, and an internal identifier of a first UE group, S601 can also be described as: AF configures a first parameter in UDM or UDR: The first parameter includes:

[0140] At least one of the maximum aggregate bit rate threshold of the first UE group corresponding to the first application in the first network slice, the minimum aggregate bit rate threshold of the first UE group, and the minimum bit rate threshold of the UE in the first UE group.

[0141] The first parameter also includes: the identifiers of all UEs in the first UE group or at least one of the identifiers of the first UE group, the identifier of the first network slice, and the identifier of the first application.

[0142] It can be understood that UDM or UDR can store multiple groups of configuration parameters and applicable conditions of multiple groups of configuration parameters, and one group of configuration parameters corresponds to one group of applicable conditions of configuration parameters (that is, there is a mapping relationship between the parameters and the applicable conditions of the parameters). Each group of configuration parameters includes at least one of the following: the maximum aggregate bit rate threshold of the UE group, the minimum aggregate bit rate threshold of the UE group, and the minimum bit rate threshold of the UE in the UE group. The applicable conditions of different groups of configuration parameters are different. For example, the applicable conditions of each group of configuration parameters include: network slice identifier (S-NSSAI), application identifier (Application ID), internal UE group identifier (Internal Group ID) or identifier of all UEs in the internal UE group. Among the applicable conditions corresponding to different groups of configuration parameters, at least one is different.

[0143] According to the applicable conditions of the parameters, namely the network slice identifier (S-NSSAI), the application identifier (Application ID), and the internal UE group identifier (Internal Group ID), the corresponding parameters can be determined, for example: at least one of the maximum aggregation bit rate threshold of the UE group, the minimum aggregation bit rate threshold of the UE group, and the minimum bit rate threshold of the UE in the UE group.

[0144] Optionally, in some possible implementations of the present application, the parameters in S601 and the applicable conditions of the parameters may not be configured by the AF in the UDM or UDR through an external parameter provision process, but may be pre-configured in the UDM or UDR. For example, the operator configures the above parameters and the applicable conditions of the parameters in the UDM or UDR based on an agreement signed between the operator and the third-party AF.

[0145] S602. The AF sends a first request message to the NEF. The first request message carries: applicable conditions and indication information of the parameters.

[0146] Correspondingly, the NEF receives the first request information.

[0147] Optionally, the first request information may also be referred to as a first request message.

[0148] Optionally, the first request information may be a session setting request.

[0149] For example, the first request information may be a request to create an AF session that meets specific QoS requirements (AFsession with required QoS create request).

[0150] For another example, the first request information may also be a request to update an AF session that meets specific QoS requirements (AFsession with required QoS update request).

[0151] Among them, the indication information is used to instruct (or trigger) the PCF to perform aggregate bit rate monitoring and adjustment of the UE Group. For example, the indication information may include "Group Aggregated BitRate Monitoring", and "Group AggregatedBitRate Monitoring" is used to instruct (or trigger) the PCF to perform aggregate bit rate monitoring and adjustment of the UE Group. Alternatively, the indication information may be used to indicate (or trigger): the PCF performs monitoring and adjustment of the minimum bit rate of UE in the UE Group. For example, the indication information may include "Min BitRate of UE Monitoring". "Min BitRate of UEMonitoring" is used to indicate (or trigger): the PCF performs monitoring and adjustment of the minimum bit rate of UE in the UE Group.

[0152] In other words, the indication information may indicate (or trigger) at least one of: the PCF performing monitoring and adjustment of the aggregate bit rate of the UE Group or the PCF performing monitoring and adjustment of the minimum bit rate of the UEs in the UE Group.

[0153] Optionally, the indication information may also be referred to as second indication information.

[0154] The applicable conditions of the configuration parameters (i.e., the applicable conditions of the parameters) may include: network slice identifier (S-NSSAI), application identifier (Application ID), and external UE group identifier (External Group ID). The identifier of the external UE group is the identifier of the internal UE group corresponding to S601, that is, the identifier of the external UE group in S602 and the identifier of the internal UE group in S601 are two different identifiers of the same UE group. The network slice identifier (S-NSSAI), application identifier (Application ID) and the applicable conditions of these two parameters in S601 are the same, both indicating the same slice and the same application.

[0155] Optionally, the applicable conditions of the configuration parameters in S602 may also include: the identifiers of all UEs included in the external UE group (i.e., the identifiers of a group of UEs), where the identifiers of this group of UEs may be a group of generic public subscription identifiers (GPSI), or may be a group of IP addresses of UEs, etc., which is not limited in the embodiments of the present application.

[0156] In other words, the applicable conditions of the configuration parameters in S602 may include: the identifiers of all UEs in the external UE group or at least one of the identifiers of the external UE group, the first network slice identifier, and the identifier of the first application.

[0157] For example, assuming that the applicable conditions of the parameters in S601 include: the first network slice identifier, the identifier of the first application, and the internal identifier of the first UE group, then in S602, the applicable conditions of the parameters include: the identifiers of all UEs in the first UE group, or at least one of the external identifiers of the first UE group, the first network slice identifier, and the identifier of the first application.

[0158] S603, NEF obtains the corresponding internal UE group identifier and UE identifier list from UDM.

[0159] For example, the NEF may retrieve the identifier of the corresponding internal UE group and the UE identifier list from the UDM according to the identifier of the external UE group, where the UE identifier list is a list of identifiers of UEs included in the internal UE group.

[0160] In some implementations, the UDM may store a correspondence (mapping relationship) between the identifier of the external UE group and the identifier of the internal UE group, and the NEF may send a request message to the UDM. For example, the request message may be an SDM acquisition request (Nudm_SDM_get request), carrying the identifier of the external UE group (for example, the external identifier of the first UE group), for requesting the UDM for the identifier of the corresponding internal UE group (for example, the internal identifier of the first UE group) and the identifiers of the UEs included in the UE group (the first UE group). After receiving the request message, the UDM determines the identifier of the internal UE group corresponding to the identifier of the external UE group from the stored mapping relationship according to the identifier of the external UE group. Further, the UDM may also determine the identifiers of each UE included in the internal UE group according to the determined identifier of the internal UE group. It should be understood that the UEs included in the external UE group and the UEs included in the internal UE group are the same, that is, the external UE group and the internal UE group are the same UE group. The UDM feeds back the determined identifier of the internal UE group and the identifier list of each UE included in the internal UE group to the NEF. For example, the UDM may send the internal UE group identifier and the UE identifier list to the NEF via an SDM get response (Nudm_SDM_get response).

[0161] Exemplarily, the UE identifier may be a Subscription Permanent Identifier (SUPI) of the UE, and the SUPI is an internal UE identifier. Of course, in other implementations of the present application, the UE identifier may also be an identifier in other forms, which is not limited in the embodiments of the present application.

[0162] For example, the UDM may send the internal UE group identifier (Internal Group ID) and the UE identifier list (SUPIlist) to the NEF. The UE identifier list is a list of identifiers of UEs included in the internal UE group.

[0163] For example, assume that in S602, the applicable conditions of the parameters include: the first network slice identifier, the identifier of the first application, and the external identifier of the first UE group. Then in S603, the NEF obtains: the internal identifier of the first UE group and the identifier list of all UEs included in the first UE group.

[0164] Optionally, if the applicable conditions of the configuration parameters in S602 include: the identifiers of all UEs included in the external UE group (for example, the first UE group) (that is, the identifiers of a group of UEs, such as a group of GPSIs or a group of UE IP addresses), in method 600, "the identifiers of all UEs included in the external UE group" may also be referred to as "external UE identifier list". Then in S603, the NEF may also obtain the internal UE identifier list according to the external UE identifier list.

[0165] For example, if the applicable conditions of the configuration parameters in S602 include a group of GPSIs, then in S603, the NEF may obtain the SUPI corresponding to the GPSI through the UDM, that is, obtain a list of all UE identities (SUPI list) in the corresponding internal UE group.

[0166] For another example, if the applicable conditions of the configuration parameters in S602 include a group of UE IP addresses, and the NEF identifies that the UE IP address is an external IP address (i.e., a public network address (UE public IP address)) based on the configuration, for each UE IP address, in S603, the NEF first discovers the UPF that supports the network address translation (NAT) function for the UE from the NRF, and then the NEF sends a request to the UPF, the request includes the UE public network address (UE public IP address), and the UPF obtains the UE private network address (UE private IP address) corresponding to the UE public network address based on the NAT function, and the UE private network address is a private IP address (i.e., an internal address) used inside the core network, and then the UPF feeds back the UE private network address (UE private IP address) to the NEF. In this way, the NEF can obtain the UE identification list (UE private network address list) of all the internal UE groups.

[0167] S604. The NEF obtains the serving PCF set for the UE from the BSF according to the UE identification list.

[0168] In some possible implementations, the PCFs serving different UEs may be different. In other words, one PCF may serve, be responsible for or manage one or more UEs, and the UEs included in the internal UE group (for example, the first UE group) may be served by different PCFs. Therefore, in S604, the NEF may obtain a set of service PCFs corresponding to all UEs in the internal UE group (for example, the first UE group), and the service PCF set includes one or more service PCFs (hereinafter, for the convenience of description, the service PCF is referred to as PCF). In this case, the NEF can also count which UEs each PCF corresponds to (or which UEs it serves).

[0169] Optionally, a PCF set can also be expressed as: PCF(s).

[0170] For example, assuming that the internal UE group (for example, the first UE group) includes 6 UEs, namely UE1 to UE6, the information finally determined by the NEF may be in the following form:<PCF1:UE1,UE2> ,<PCF2:UE3,UE4,UE5> ,<PCF3:UE6> , indicating that PCF1 serves UE1 and UE2; PCF2 serves UE3 to UE5; and PCF3 serves UE6.

[0171] Among them, UE1 and UE2 form a sub-UE group (UE sub Group), which is responsible for or managed by PCF1. The UE identification list included in this sub-UE group can be called a sub-UE group identification list (SUPI sub list), which are the identifications of UE1 and UE2 respectively. PCF1 is a policy control function network element serving the sub-UE group.

[0172] Similarly, UE3 to UE5 form another sub-UE group (UE sub Group), which is responsible for or managed by PCF2. The UE identification list included in this sub-UE group can be called a sub-UE group identification list (SUPI sub list), which are the identifications of UE3 to UE5 respectively; PCF2 is a policy control function network element serving the sub-UE group.

[0173] UE6 alone constitutes another sub-UE group (UE sub Group), which is responsible for or managed by PCF3. The UE identification list included in this sub-UE group can be called a sub-UE group identification list (SUPI sub list), which is the identification of UE6; PCF3 is a policy control function network element serving the sub-UE group.

[0174] The above three sub-UE groups constitute an internal UE group. In other words, all sub-UE groups (UE sub Group) managed by PCFs in the PCF set constitute an internal UE group (UE Group), and the sub-UE group is a subset of the first UE group (or internal UE group).

[0175] Exemplarily, in S604, the NEF may send a management discovery request (Nbsf_management_discovery request) to the BSF, carrying a UE identification list. After receiving the request, the BSF determines the serving PCF set for the UE, and feeds back the PCF set to the NEF by sending a management discovery response (Nbsf_management_discovery response).

[0176] S605. The NEF sends a request message to each PCF in the serving PCF set. The request message carries: parameter application conditions and indication information.

[0177] Correspondingly, each PCF in the PCF set receives the request message.

[0178] For example, the request message may be a policy authorization create or update request (policy authorizationcreate / update request).

[0179] Optionally, the information carried in the request message in S605 may also be referred to as third information.

[0180] The indication information is used to instruct (or trigger) the PCF to perform aggregate bit rate monitoring and adjustment of the UE Group. For example, the indication information may include "Group Aggregated BitRate Monitoring". Optionally, the indication information may also be used to instruct (or trigger): the PCF performs monitoring and adjustment of the minimum bit rate of UEs in the UE Group. For example, the indication information may include "Min BitRate of UE Monitoring".

[0181] In other words, the indication information may indicate that: the PCF performs at least one of monitoring and adjusting the aggregate bit rate of the UE Group, or the PCF performs monitoring and adjusting the minimum bit rate of the UEs in the UE Group.

[0182] Optionally, the indication information in S605 may also be referred to as first indication information.

[0183] In S605, the parameter applicability conditions may include: at least one of the UE list included in the internal UE group (such as SUPI list, UE IPaddress list) and the internal UE group identifier (Internal Group ID), the network slice identifier (S-NSSAI), and the application identifier (Application ID).

[0184] It should also be understood that in S605, the parameter application condition also includes: the identifiers (UE sub-list) of all UEs in the sub-UE group (UE subGroup) served by the PCF, which are used to identify the UE identifiers served by the PCF. When the PCF subsequently performs policy adjustments, it only adjusts the UEs in the UE sub-list (UE sub-list) of all UEs served by the PCF.

[0185] For example, assume that: the network slice identifier in S601 to S604 is the identifier of the first network slice, the application identifier is the identifier of the first application, the UE group identifier is the identifier of the first UE group, the PCF set includes PCF1, UE1 and UE2 form a sub-UE group, and PCF1 is a policy control function network element serving the sub-UE group. Then in S605, the request message sent by NEF to PCF1 includes: at least one of the list of all UEs included in the first UE group and the identifier of the first UE group, the first network slice identifier, the identifier of the first application, the identifiers of all UEs of the sub-UE group (UE sub Group) served by PCF1 (UE sub-list), and indication information.

[0186] Optionally, S605 can also be expressed as: the policy control function network element receives third information from the network open function network element, the third information includes first indication information, the first indication information is used to indicate: triggering (triggering) the aggregated bit rate monitoring of the first terminal device group, or at least one of the minimum bit rate monitoring of the terminal devices in the first terminal device group, the third information also includes: the identification of all terminal devices in the first terminal device group or at least one of the identification of the first terminal device group, the identification of the first network slice, the identification of the first application, and the identification of all UEs served by the policy control function network element (UE sub-list).

[0187] S606. Each PCF in the serving PCF set sends a subscription message to the NWDAF according to the request message. The subscription message is used to subscribe to (or request) at least one of the aggregate bit rate of the internal UE group or the minimum bit rate of the UE in the internal UE group.

[0188] In some possible implementations, the subscription message (or request message) may carry: at least one of the UE list included in the internal UE group and the internal UE group identifier (Internal Group ID), the network slice identifier (S-NSSAI), and the application identifier (Application ID).

[0189] It should also be understood that the subscription message in S606 also includes: the identifiers (UE sub-list) of all UEs in the sub-UE group (UE sub Group) served by the PCF, which is used to identify the UE identifiers served by the PCF. Subsequently, the NWDAF can obtain the SMF serving the UE from the corresponding PCF based on the service UE list (UE sub-list) provided by each PCF.

[0190] In some possible implementations, the subscription message may also include: an analysis type identifier (AnalyticsID). Since NWDAF can perform various different types of analysis on the UE, such as analyzing the UE's mobility, the UE's data volume or bit rate, etc., various different types of analysis results will be generated. Therefore, the subscription message may carry the type of analysis to instruct NWDAF to perform at least one of an analysis of the UE group's aggregate bit rate or an analysis of the minimum bit rate of the UE in the UE group. For example, the subscription message may include an analysis type identifier. Exemplarily, the analysis type identifier may be a hotspot analysis (Dispersion Analytics), indicating that PCF requests hotspot analysis (i.e., analysis related to the data volume and session of the UE or UE group at different locations or different slices) from NWDAF.

[0191] Correspondingly, NWDAF receives subscription messages sent by multiple PCFs respectively.

[0192] S607, NWDAF obtains the SMF set serving the internal UE group from the PCF included in the PCF set based on the network slice identifier, application identifier and UE identifier list, and the SMF set includes one or more SMFs.

[0193] In some possible implementations, NWDAF can send a request message to each PCF in the service PCF set, including: network slice identifier, application identifier and identifiers of all UEs served by the PCF (UE sub-list). The PCF determines the serving SMF of the UE based on this information and then sends it to NWDAF. It can be understood that for a PCF, the serving SMFs corresponding to all UEs served by the PCF may include one or more.

[0194] Optionally, for a PCF, the PCF may also discover the serving UPF of the UE from the serving SMF of the UE, where the serving UPF includes one or more UPFs.

[0195] Each PCF in the PCF set can send the SMF corresponding to the UE it serves to the NWDAF. Optionally, each PCF in the PCF set can also send the UPF corresponding to the UE it serves to the NWDAF. Based on the information fed back by each PCF in the PCF set, the NWDAF can determine the SMF (serving SMF) serving the UE included in the internal UE group. An SMF can serve one or more UEs, that is, one SMF is responsible for one or more UEs. Optionally, the NWDAF can also determine the UPF set corresponding to the internal UE group, and these UPFs serve the multiple UEs included in the internal UE group. In other words, in S607, the NWDAF can determine an SMF set, which includes one or more SMFs, and these SMFs serve the multiple UEs included in the internal UE group. Optionally, the NWDAF can also determine a UPF set, which includes one or more UPFs, and these UPFs serve the multiple UEs included in the internal UE group. Optionally, the SMF set can also be expressed as: SMF(s), and the UPF set can also be expressed as: UPF(s).

[0196] For example, assuming that the internal UE group (the first UE group) includes 6 UEs, namely UE1 to UE6, the information finally determined by the NWDAF may be in the following form:<PCF1:UE1,SMF1;UE2,SMF2> ,<PCF2:UE3,UE4,UE5;SMF3> ,<PCF3:UE6;SMF4> : Indicates: PCF1 serves UE1 and UE2, SMF1 serves UE1, SMF2 serves UE2; PCF2 serves UE3 to UE5, SMF3 serves UE3 to UE5; PCF3 serves UE6, SMF4 serves UE6.

[0197] For example, in combination with the above example, the NWDAF may determine SMF1, SMF2, SMF3 and SMF4, where SMF1, SMF2, SMF3 and SMF4 include all SMFs serving multiple UEs included in the internal UE group.

[0198] As a possible implementation method, NWDAF can send an event open subscription request (Npcf_eventexposure_subscribe) to each PCF separately, carrying: network slice identifier (S-NSSAI), application identifier (Application ID) and UE identifier list (all UEs in the UE identifier list are UEs served by the PCF). After receiving the subscription request, PCF sends an event open subscription notification (Npcf_eventexposure_notify) to NWDAF, carrying one or more SMFs corresponding to the UE managed by the PCF. NWDAF can determine the SMF serving each UE based on the information fed back by each PCF in the PCF set, that is, determine the SMF (or SMF set) serving the internal UE group, and the SMF set includes one or more SMFs. The UEs managed by each PCF can form a sub-UE group (UE sub Group), and the sub-UE groups managed by all PCFs in the PCF set constitute an internal UE group. The identifier list of UEs included in a sub-UE group can also be called a sub-UE group identifier list (SUPI sub list).

[0199] S608, NWDAF obtains from the SMF included in the SMF set, or obtains from the UPF through the SMF: the bit rate corresponding to each UE in the internal UE group.

[0200] For example, assuming that the network slice identifier in S601 to S607 is the identifier of the first network slice, the ApplicationID identifier is the first application, and the internal UE group identifier is the first UE group, then in S608, NWDAF can obtain: the bit rate corresponding to each UE in the first UE group (i.e., the internal UE group) running the first application on the first network slice identifier.

[0201] Exemplarily, in S608, NWDAF may obtain from SMF, or obtain from UPF through SMF, a bit rate report corresponding to each UE in an internal UE group (eg, the first UE group), and the UE bit rate report includes parameters such as the bit rate of the UE.

[0202] S609, NWDAF determines at least one of the UE group aggregate bit rate or the minimum bit rate of the UE in the UE group according to the bit rate corresponding to each UE in the UE group.

[0203] In some possible implementations, NWDAF can determine the bit rate of each UE based on the bit rate report of each UE in the UE group, and then add the bit rate of each UE in the UE group to obtain the UE group aggregate bit rate corresponding to the UE group (Aggregated Bit Rate per S-NSSAI per App ID per UE Group).

[0204] In some other possible implementations, the NWDAF may determine the minimum bit rate of the UEs in the UE group (Min BitRate per S-NSSAI per App ID per UE) based on the bit rate report of each UE in the UE group.

[0205] It should be understood that the "UE group" in S609 is the internal UE group mentioned above.

[0206] S610, the NWDAF sends at least one of the UE group aggregate bit rate corresponding to the internal UE group or the minimum bit rate of the UEs in the internal UE group to the PCF that subscribes to the NWDAF analysis result.

[0207] For example, assuming that: the network slice identifier in S601 to S609 is the identifier of the first network slice, the application identifier is the identifier of the first application, and the UE group identifier is the identifier of the first UE group. Optionally, S610 can also be expressed as: each PCF obtains first information, and the first information includes: the aggregated bit rate of the first terminal device group corresponding to the first application in the first network slice, or at least one of the minimum bit rates of the terminal devices in the first terminal device group corresponding to the first application in the first network slice.

[0208] Optionally, S610 can also be expressed as: the policy control function network element obtains first information, and the first information includes: the aggregated bit rate of the first terminal device group (i.e., the first UE group) corresponding to the first application in the first network slice, or at least one of the minimum bit rates of the terminal devices in the first terminal device group corresponding to the first application in the first network slice.

[0209] Optionally, S610 can also be expressed as: NWDAF sends ninth information to the PCF that subscribes to the NWDAF analysis results respectively, and the ninth information includes: the aggregated bit rate of the first terminal device group corresponding to the first application in the first network slice, or at least one of the minimum bit rate of the terminal devices in the first terminal device group corresponding to the first application in the first network slice.

[0210] S611, each PCF obtains from the UDM or UDR: at least one of the maximum aggregate bit rate threshold of the UE group (Group-MBRfor UL / DL), the minimum aggregate bit rate threshold of the UE group (Group-Min-BR for UL / DL), and the minimum bit rate threshold of the UE in the UE group (Min BitRate of UE for UL / DL).

[0211] Assume: for PCF1, PCF1 is a PCF in the service PCF set, and has sent a subscription message to NWDAF. PCF1 can send a query request (for example, a first query request) to UDM or UDR, carrying: an internal UE group identifier (Internal Group ID) or at least one of the list of all UE identifiers in the internal UE group, a network slice identifier (S-NSSAI), and an application identifier (Application ID). After receiving the query request, UDM or UDR determines which UE group corresponds to the network slice identifier (S-NSSAI), the application identifier (Application ID), the internal UE group identifier (Internal Group ID) or the list of all UE identifiers in the internal group, and then determines the corresponding UE group: at least one of the maximum aggregate bit rate threshold of the UE group (Group-MBR for UL / DL), the minimum aggregate bit rate threshold of the UE group (Group-Min-BR forUL / DL), and the minimum bit rate threshold of the UE in the UE group (Min BitRate of UE for UL / DL). Afterwards, UDM or UDR can send a query response to PCF1, and the query response includes at least one of: the maximum aggregate bit rate threshold of the UE group (Group-MBR for UL / DL), the minimum aggregate bit rate threshold of the UE group (Group-Min-BR for UL / DL), and the minimum bit rate threshold of the UE in the UE group (Min BitRate of UE for UL / DL).

[0212] It should be understood that for each PCF in the PCF set, at least one of the maximum aggregate bit rate threshold of the UE group, the minimum aggregate bit rate threshold of the UE group, and the minimum bit rate threshold of the UE in the UE group is obtained through a process similar to PCF1.

[0213] For example, assuming that the network slice identifier in S601 to S610 is the identifier of the first network slice, the application identifier is the identifier of the first application, and the UE group identifier is the identifier of the first UE group. Then PCF1 obtains from the UDM or UDR: at least one of the maximum aggregate bit rate threshold of the first UE group, the minimum aggregate bit rate threshold of the first UE group, and the minimum bit rate threshold of the UE in the first UE group.

[0214] Optionally, S611 can also be expressed as: the policy control function network element receives second information from the data storage network element or the unified data management network element, and the second information includes: the maximum aggregation bit rate threshold of the first terminal device group, the minimum aggregation bit rate threshold of the first terminal device group, or at least one of the minimum bit rate threshold of the terminal devices in the first terminal device group.

[0215] S612: Each PCF determines whether the bit rate of the UE group meets the requirement.

[0216] For example, if the aggregate bit rate of the UE group (first UE group) is greater than the maximum aggregate bit rate threshold of the UE group (first UE group), it is determined that the aggregate bit rate of the UE group (first UE group) does not meet the requirement. In this case, although the requirement for normal transmission of the service of the UE group (first UE group) can be met, it may affect other UEs or services.

[0217] For another example, if the aggregate bit rate of the UE group (first UE group) is less than the minimum aggregate bit rate threshold of the UE group (first UE group), it is determined that the aggregate bit rate of the UE group (first UE group) does not meet the requirement. In this case, the minimum requirement for normal transmission of the service of the UE group may not be met, and normal transmission of the service data cannot be guaranteed.

[0218] For another example, if the minimum bit rate of the UE in the UE group (first UE group) is less than the minimum bit rate threshold of the UE in the UE group (first UE group), it is determined that the bit rate of the UE group (first UE group) does not meet the requirement. In this case, the minimum requirement for normal transmission of the service of the UE group may not be met, and normal transmission of the service data cannot be guaranteed.

[0219] S613: When the bit rate of the UE group does not meet the requirement, each PCF generates an adjustment strategy.

[0220] It should be understood that in S613, when each PCF performs policy adjustment, it only adjusts the UEs in the UE list (UE sub-list) served by the PCF.

[0221] In some possible implementations, the adjustment strategy may include at least one of the following:

[0222] If the UE QoS flow in the sub-UE group is a guaranteed bit rate QoS flow, modify the maximum bit rate value of the guaranteed bit rate QoS flow;

[0223] Adjusting the allocation retention priority (ARP) or priority parameter of the quality of service flow of the UE in the sub-UE group;

[0224] The service quality flows of some UEs in the sub-UE group are released.

[0225] For example, UE1 and UE2 form a sub-UE group (referred to as a sub-UE group), PCF1 is a policy control function network element serving the sub-UE group, and for PCF1, the adjustment strategy may include at least one of the following:

[0226] If the UE QoS flow in the sub-UE group is a guaranteed bit rate QoS flow, modify the maximum bit rate value of the guaranteed bit rate QoS flow;

[0227] Adjust the ARP or priority parameters of the service quality flow of the UE in the sub-UE group;

[0228] The service quality flows of some UEs in the sub-UE group are released.

[0229] Of course, in other implementations of the present application, the adjustment strategy may also include other bit rate adjustment strategies. After adjustment using the adjustment strategy, it can be achieved that: the UE group aggregate bit rate is less than or equal to the maximum aggregate bit rate threshold of the UE group and greater than the minimum aggregate bit rate threshold of the UE group, or the minimum bit rate of the UE in the UE group is greater than the minimum bit rate threshold of the UE in the UE group.

[0230] After determining the adjustment strategy, the PCF can execute the adjustment strategy.

[0231] Optionally, in each step of method 600, the expression "first UE group (i.e., first terminal device group)" may also be replaced by: "third UE group (i.e., third terminal device group)". That is, in the embodiment shown in method 600, the first terminal device group and the third terminal device group are the same terminal device group.

[0232] It should also be understood that in method 600, the expression "identifiers of UEs in a UE group" refers to identifiers corresponding to all UEs in the UE group, that is, a list of UE identifiers. For example, the expression "identifiers of UEs in a first group" refers to identifiers corresponding to all UEs in the first UE group. For another example, the expression "identifiers of UEs in a subgroup" refers to identifiers corresponding to all UEs in the sub-UE group. For another example, the identifiers of UEs included in an external UE group refer to identifiers of all UEs included in the external UE group. For another example, the identifiers of UEs included in an internal UE group refer to identifiers of all UEs included in the internal UE group.

[0233] The method provided in the embodiment of the present application subscribes to at least one of the aggregate bit rate information of each slice per application per UE group (per Slice per Application per UE Group) or the minimum bit rate information of UE in the UE group to NWDAF through PCF, and configures at least one of the maximum aggregate bit rate threshold of each slice per application per UE group, the threshold of the minimum aggregate bit rate of the UE group, or the minimum bit rate threshold of the UE in the UE group in the UDM or UDR. PCF compares the aggregate bit rate of the UE group and / or the minimum bit rate of the UE in the UE group obtained from NWDAF with the threshold stored in the UDM or UDR to determine whether the conditions set in the UDM or UDR are met. If not, PCF performs policy adjustment to realize the monitoring and adjustment of the bit rate at the UE group granularity. It can ensure that the aggregate bit rate of the UE group does not exceed the requirements to avoid affecting other UEs or services. It can also ensure that the aggregate bit rate of the UE group is not lower than the set minimum aggregate bit rate to ensure the minimum requirements for normal transmission of the service, thereby improving communication efficiency.

[0234] Figure 7 is a schematic interactive diagram of a rate control method for a terminal device group in a network slice in another embodiment of the present application. The method 700 can be applied in Figure 5 The scenario shown can of course also be applied to other communication scenarios, and the embodiments of the present application are not limited here.

[0235] Figure 7 In the process shown, the AF configures the maximum bit rate requirement (Group-MBR) and / or minimum bit rate requirement per slice per application per UE group in the UDR or UDM, and the PCF obtains the aggregate bit rate monitoring result per slice per application per UE group from the NWDAF, and then compares it with the maximum bit rate requirement and / or minimum bit rate requirement in the UDR or UDM. When it is determined that the aggregate bit rate of the current UE group does not meet the requirements, the PCF executes the corresponding adjustment strategy. Figure 7As shown, Figure 7 The method 700 shown in FIG. 7 may include S701 to S713. Figure 7 Each step in method 700 is described in detail.

[0236] S701, AF configures the parameters and the applicable conditions of the parameters in UDR or UDM through the external parameter provision process.

[0237] The configuration parameters include at least one of the following:

[0238] Maximum aggregate bit rate threshold of the UE group (Group-MBR for UL / DL), minimum aggregate bit rate threshold of the UE group (Group-Min-BR for UL / DL), minimum bit rate threshold of the UE in the UE group (Min BitRate of UE for UL / DL);

[0239] The applicable conditions of the parameter include: the identifier of the UE in the internal UE group or at least one of the identifiers of the internal UE group, the network slice identifier (S-NSSAI), and the application identifier (Application ID). It should be understood that the identifier of the UE in the internal UE group refers to the identifiers corresponding to all UEs in the internal UE group.

[0240] Optionally, in some possible implementations of the present application, the parameters in S701 and the applicable conditions of the parameters may not be configured by the AF in the UDM or UDR through an external parameter provision process, but may be pre-configured in the UDM or UDR. For example, the operator configures the above parameters and the applicable conditions of the parameters in the UDM or UDR based on an agreement signed between the operator and the third-party AF.

[0241] S702. The AF sends a first request message to the NEF. The first request message carries parameter application conditions and indication information.

[0242] The indication information may indicate (or trigger) that the PCF performs at least one of monitoring and adjusting the aggregate bit rate of the UE Group, or monitoring and adjusting the minimum bit rate of the UEs in the UE Group.

[0243] The applicable conditions of configuration parameters may include: network slice identifier (S-NSSAI), application identifier (ApplicationID), and external UE group identifier (External Group ID).

[0244] Optionally, the applicable conditions of the configuration parameters in S702 may also include: the identifiers of all UEs included in the external UE group (i.e., the identifiers of a group of UEs). The identifiers of this group of UEs may be a group of GPSIs, or may also be a group of IP addresses of UEs, etc. The embodiments of the present application are not limited here.

[0245] In other words, the applicable conditions of the configuration parameters in S702 may include: the identifiers of all UEs in the external UE group or at least one of the identifiers of the external UE group, the first network slice identifier, and the identifier of the first application.

[0246] S703. NEF obtains the corresponding internal UE group identifier and UE identifier list from UDM.

[0247] S704. The NEF obtains the serving PCF set for the UE from the BSF according to the UE identification list.

[0248] S705. The NEF sends a request message to each PCF in the serving PCF set. The request message carries the configuration parameter applicable conditions, indication information, and a UE identity list (SUPI list).

[0249] The indication information may indicate: the PCF performs at least one of monitoring and adjusting the aggregate bit rate of the UE Group, or the PCF performs monitoring and adjusting the minimum bit rate of the UE in the UE Group.

[0250] The configuration parameter application conditions may include: at least one of the UE list included in the internal UE group and the internal UE group identifier (Internal Group ID), as well as the network slice identifier (S-NSSAI) and the application identifier (Application ID).

[0251] For the specific description of S701 to S705, reference may be made to the above specific description of S601 to S605, which will not be repeated here for the sake of brevity.

[0252] S706.NEF sends a subscription message to NWDAF, where the subscription message is used to subscribe to (or request): at least one of the aggregate bit rate of the UE group or the minimum bit rate of the UE in the UE group. The subscription message carries indication information, where the indication information is used to indicate that NWDAF sends the subscription result to each PCF. The subscription message includes: the identifier or address of each PCF in the PCF set, and the list of UEs served by each PCF.

[0253] In some possible implementations, the subscription message (also referred to as a request message) may also carry: at least one of the UE list included in the UE group and the UE group identifier (Internal Group ID), as well as the network slice identifier (S-NSSAI), the application identifier (Application ID), and the identifier of the UE in the sub-UE group (UE sub Group) served by each PCF (UE sub-list).

[0254] It can be understood that the "UE group" in S706 is the "internal UE" group described in S703 to S705.

[0255] For example, assuming that: the network slice identifier in S701 to S705 is the identifier of the first network slice, the application identifier is the identifier of the first application, and the UE group identifier is the identifier of the first UE group, then the subscription message in S706 carries: at least one of the UE list included in the first UE group and the identifier of the first UE group, as well as the identifier of the first network slice, the identifier of the first application, and the identifier (UE sub-list) of the UE in the sub-UE group (UE sub Group) served by each PCF.

[0256] In some possible implementations, the subscription message may also include: an analysis type identifier (AnalyticsID). Since NWDAF can perform various different types of analysis on the UE, such as analyzing the UE's mobility, the UE's data volume or bit rate, etc., various different types of analysis results will be generated. Therefore, the subscription message may carry the type of analysis to instruct NWDAF to perform at least one of an analysis of the UE group's aggregate bit rate or an analysis of the minimum bit rate of the UE in the UE group. For example, the subscription message may include an analysis type identifier. Exemplarily, the analysis type identifier may be a hotspot analysis (Dispersion Analytics), indicating that PCF requests hotspot analysis (i.e., analysis related to the data volume and session of the UE or UE group at different locations or different slices) from NWDAF.

[0257] It should also be understood that S705 is an optional step. If method 700 does not include S705, S706 is directly executed after S704. NEF directly sends a subscription message to NWDAF in S706. The subscription message may carry: configuration parameter applicable conditions, PCF list and UE list corresponding to (served by) each PCF. The subscription message indicates that NWDAF sends the analysis result to each PCF in the PCF set. The subscription message is used to subscribe to (or request): at least one of the aggregate bit rate of the UE group or the minimum bit rate of the UE in the UE group.

[0258] S707: NWDAF obtains the SMF set serving the internal UE group from the PCF included in the PCF set according to the subscription message sent by the NEF, and the SMF set includes one or more SMFs.

[0259] S708, NWDAF obtains the bit rate corresponding to each UE in the UE group from the SMF included in the SMF set, or obtains from the UPF through the SMF.

[0260] It can be understood that the "UE group" in S708 is the "internal UE" group described in S703 to S707.

[0261] For example, assuming that: the network slice identifier in S701 to S707 is the identifier of the first network slice, the application identifier is the identifier of the first application, and the UE group identifier is the identifier of the first UE group, then in S708, NWDAF obtains: the bit rate corresponding to each UE in the first UE group corresponding to the first application on the first network slice.

[0262] S709, the NWDAF determines at least one of a UE group aggregate bit rate corresponding to the UE group or a minimum bit rate of the UEs in the UE group according to the bit rate corresponding to each UE in the UE group.

[0263] S710, the NWDAF sends at least one of the UE group aggregate bit rate corresponding to the UE group or the minimum bit rate of the UEs in the UE group to each PCF.

[0264] Optionally, if method 700 does not include S705, then in S710, NWDAF also needs to send to each PCF in the PCF set: the UE list (UE sub-list) corresponding to the PCF and indication information, where the indication information is used to instruct the PCF to perform the aggregate bit rate adjustment of the UE Group, or to perform the adjustment of the minimum bit rate of the UE in the UE Group.

[0265] S711, each PCF obtains from the UDR: at least one of the maximum aggregate bit rate threshold of the UE group, the minimum aggregate bit rate threshold of the UE group, and the minimum bit rate threshold of the UEs in the UE group.

[0266] S712: Each PCF determines whether the bit rate of the UE group meets the requirement.

[0267] For example, if at least one of the following conditions is met: the aggregate bit rate of the UE group is greater than the maximum bit rate threshold of the UE group, the aggregate bit rate of the UE group is less than the minimum bit rate threshold of the UE group, or the minimum bit rate of the UEs in the UE group is less than the minimum bit rate threshold of the UEs in the UE group, it is determined that the bit rate of the UE group does not meet the requirements.

[0268] S713: When the bit rate of the UE group does not meet the requirement, each PCF generates an adjustment strategy.

[0269] It should be understood that in S713, when each PCF performs policy adjustment, it only adjusts the UEs in the UE list served by the PCF.

[0270] For the specific description of S707 to S713, reference may be made to the above specific description of S607 to S613, which will not be repeated here for the sake of brevity.

[0271] It should also be understood that in method 700, the expression "identifiers of UEs in a UE group" refers to identifiers corresponding to all UEs in the UE group, that is, a list of UE identifiers. For example, the expression "identifiers of UEs in a first group" refers to identifiers corresponding to all UEs in the first UE group. For another example, the expression "identifiers of UEs in a subgroup" refers to identifiers corresponding to all UEs in the sub-UE group. For another example, "identifiers of UEs included in an external UE group" refers to identifiers of all UEs included in an external UE group. For another example, "identifiers of UEs included in an internal UE group" refers to identifiers of all UEs included in an internal UE group.

[0272] In the method provided in the embodiment of the present application, NEF subscribes to NWDAF for the aggregate bit rate information of each slice per application per UE group and / or the minimum bit rate information of UE in the UE group, and instructs NWDAF to send the information to PCF. At least one of the maximum aggregate bit rate threshold of each slice per application per UE group, the threshold of the minimum aggregate bit rate of the UE group, or the minimum bit rate threshold of the UE in the UE group is configured in UDM or UDR. PCF compares the aggregate bit rate of the UE group and / or the minimum bit rate of the UE in the UE group obtained from NWDAF with the threshold stored in UDR to determine whether the conditions set in UDM or UDR are met. If not, PCF performs policy adjustment to realize the monitoring and adjustment of the bit rate at the sub-UE group granularity. It can ensure that the aggregate bit rate of the sub-UE group does not exceed the requirements to avoid affecting other UEs or services. It can also ensure that the aggregate bit rate of the sub-UE group is not lower than the set minimum aggregate bit rate to ensure the minimum requirement for normal transmission of the service, thereby improving communication efficiency.

[0273] Figure 8 is a schematic interactive diagram of another example of a rate control method for a terminal device group within a network slice provided by the present application. The method 800 can be applied in Figure 5 The scenario shown can of course also be applied to other communication scenarios, and the embodiments of the present application are not limited here.

[0274] Figure 8 In the process shown, the AF configures the remaining group-aggregate bit rate (Remaining Group-Aggregate BitRate) per Slice per Application per UE Group in the UDR or UDM. Each PCF obtains the aggregate bit rate of the sub-UE group it is responsible for, and then obtains and updates the remaining group aggregate bit rate from the UDR or UDM. When the remaining group aggregate bit rate is close to zero or greater than the threshold, the PCF executes the corresponding adjustment strategy. Figure 8 As shown, Figure 8 The method 800 shown in FIG. 8 may include S801 to S811. Figure 8 Each step in method 800 is described in detail.

[0275] S801, AF configures the parameters and the applicable conditions of the parameters in the UDM or UDR through the External Parameter Provisioning process.

[0276] The configured parameters include: Remaining Group-Aggregate Bit Rate and a first threshold.

[0277] Optionally, in some other possible implementations, the configured parameters may also include: at least one of the maximum aggregate bit rate threshold of the UE group (Group-MBR for UL / DL), the minimum aggregate bit rate threshold of the UE group (Group-Min-BR for UL / DL), and the minimum bit rate threshold of the UE in the UE group (Min BitRate of UE for UL / DL).

[0278] The applicable conditions of the parameters include: the identifiers of all UEs in the internal UE group or at least one of the identifiers of the internal UE group (InternalGroup ID), the network slice identifier (S-NSSAI), and the application identifier (Application ID).

[0279] The remaining group-aggregate bit rate (Remaining Group-Aggregate Bit Rate) can be understood as: the remaining aggregate bit rate of the UE group (Group) corresponding to the application identified by the Application ID and the internal UE group identifier running or belonging to the network slice identified by the S-NSSAI. In other words, the remaining group aggregate bit rate refers to the remaining or available bit rate of a certain UE group (i.e., the remaining or available resource size of the UE group). The remaining group aggregate bit rate is a dynamically changing value. As the bit rate of some UEs in the UE group increases, the value of the remaining group aggregate bit rate may decrease; as the bit rate of some UEs in the UE group decreases, the value of the remaining group aggregate bit rate may increase. For example, assuming that the identifier of the internal UE group is the identifier of the third UE group, the remaining group aggregate bit rate refers to the remaining or available bit rate of the third UE group, which is a dynamically changing value. The first threshold value can be a preset value for comparison with the remaining group aggregate bit rate.

[0280] For the specific description of other parameters in S801, reference may be made to the specific description of S601 in the above method 600, which will not be repeated here for the sake of brevity.

[0281] For example, assuming that the parameter application conditions in S801 include: a first network slice identifier, an identifier of a first application, and an internal identifier of a third UE group, S801 can also be described as: AF configures a first parameter in UDR or UDM: The first parameter includes:

[0282] The remaining group aggregate bit rate and the first threshold of the third UE group corresponding to the first application in the first network slice may optionally also include: at least one of the minimum bit rate threshold of the UE in the third UE group or the maximum aggregate bit rate threshold of the third UE group.

[0283] The first parameter also includes: the identifiers of all UEs in the third UE group or at least one of the identifiers of the third UE group, the identifier of the first network slice, and the identifier of the first application.

[0284] Optionally, in some possible implementations of the present application, the parameters in S801 and the applicable conditions of the parameters may not be configured by the AF in the UDM or UDR through an external parameter provision process, but may be pre-configured in the UDM or UDR. For example, the operator configures the above parameters and the applicable conditions of the parameters in the UDM or UDR based on an agreement signed between the operator and the third-party AF.

[0285] Optionally, the third UE group may also be referred to as a third terminal device group, and the third UE group is the internal UE group in S801.

[0286] S802. The AF sends a first request message to the NEF. The first request message carries: applicable conditions and indication information of the parameters.

[0287] Correspondingly, the NEF receives the first request information.

[0288] Optionally, the first request information may also be referred to as a first request message.

[0289] Optionally, the first request information may be a session setting request.

[0290] The indication information may indicate (or trigger) that the PCF performs at least one of monitoring and adjusting the aggregate bit rate of the UE Group, or monitoring and adjusting the minimum bit rate of the UEs in the UE Group.

[0291] Optionally, the indication information may also be referred to as second indication information.

[0292] The applicable conditions of the configuration parameters may include: network slice identifier (S-NSSAI), application identifier (ApplicationID), and external UE group identifier (External Group ID). The external UE group identifier (External Group ID) is the internal UE group identifier (Internal Group ID) corresponding to S801.

[0293] Optionally, the applicable conditions of the configuration parameters in S802 may also include: the identifiers of all UEs included in the external UE group (i.e., the identifiers of a group of UEs). The identifiers of this group of UEs may be a group of GPSIs, or may also be a group of IP addresses of UEs, etc. The embodiments of the present application are not limited here.

[0294] In other words, the applicable conditions of the configuration parameters in S802 may include: the identifiers of all UEs in the external UE group or at least one of the identifiers of the external UE group, the first network slice identifier, and the identifier of the first application.

[0295] For example, assume that: the applicable conditions of the parameters in S801 include: the first network slice identifier, the identifier of the first application, and the internal identifier of the third UE group; in S802, the applicable conditions of the parameters include: the identifiers of all UEs included in the third UE group or at least one of the external identifiers of the third UE group, the first network slice identifier, and the identifier of the first application.

[0296] S803. NEF obtains the corresponding internal UE group identifier and UE identifier list from UDM.

[0297] For the specific description of S803, please refer to the description of S603 in method 600, which will not be repeated here for the sake of brevity.

[0298] S804. The NEF obtains the serving PCF set for the UE from the BSF according to the UE identification list.

[0299] In some possible implementations, the PCFs serving different UEs may be different. In other words, one PCF may serve, be responsible for or manage one or more UEs, and the UEs included in the internal UE group may be served by different PCFs. Therefore, in S804, the NEF may obtain the service PCF set corresponding to all UEs in the internal UE group, and the service PCF set includes one or more service PCFs (hereinafter, for the convenience of description, the service PCF set is referred to as the PCF set, and the service PCF is referred to as the PCF). In this case, the NEF can also count which UEs each PCF corresponds to (or which UEs it serves).

[0300] For example, assuming that the internal UE group (eg, the third UE group) includes 6 UEs, namely UE1 to UE6, the information finally determined by the NEF may be in the following form:<PCF1:UE1,UE2> ,<PCF2:UE3,UE4,UE5> ,<PCF3:UE6> , indicating that PCF1 serves UE1 and UE2; PCF2 serves UE3 to UE5; and PCF3 serves UE6.

[0301] Among them, UE1 and UE2 form a sub-UE group (UE subGroup), and this sub-UE group is responsible for or managed by PCF1. The UE identification list included in this sub-UE group can be called a sub-UE group identification list (SUPI sub list), which are the identifications of UE1 and UE2 respectively. In method 800, the sub-UE group composed of UE1 and UE2 can be called a first terminal device group, and the first terminal device group can also be called a first UE group. PCF1 is a policy control function network element serving the first terminal device group.

[0302] Similarly, UE3 to UE5 form another sub-UE group (UE sub Group), which is responsible for or managed by PCF2. The UE identification list included in this sub-UE group can be called a sub-UE group identification list (SUPI sub list), which are the identifications of UE3 to UE5 respectively; the sub-UE group composed of UE3 to UE5 can also be called a first terminal device group or a first UE group, and PCF2 is a policy control function network element serving the first terminal device group.

[0303] UE6 alone forms another sub-UE group (UE sub Group), which is responsible for or managed by PCF3. The UE identification list included in this sub-UE group can be called a sub-UE group identification list (SUPI sub list), which is the identification of UE6; the sub-UE group composed of UE6 can also be called a first terminal device group or a first UE group, and PCF3 is a policy control function network element serving the first terminal device group.

[0304] The above three sub-UE groups constitute the third UE group. In other words, all sub-UE groups managed by PCFs in the PCF set constitute an internal UE group (UE Group). The first UE group is a subset of the third UE group (or internal UE group), or the third UE group includes the first UE group.

[0305] Optionally, in method 800, the sub-UE group consisting of UEs that each PCF is responsible for can be called a first terminal device group or a first UE group, the internal UE group can be called a third terminal device group or a third UE group, the first UE group is a subset of the third UE group, or the third UE group includes the first UE group.

[0306] Optionally, a PCF set can also be expressed as: PCF(s).

[0307] S805. The NEF sends a request message to each PCF in the serving PCF set. The request message carries: parameter application conditions, indication information, and a sub-UE identity list (SUPI sub list) corresponding to the PCF.

[0308] Correspondingly, each PCF in the PCF set receives the request message.

[0309] Optionally, the request information in S805 may also be referred to as fourth information.

[0310] For example, the request information may be a policy authorization create or update request (policy authorizationcreate / update request).

[0311] The indication information is used to instruct (or trigger) the PCF to perform aggregate bit rate monitoring and adjustment of the UE group (i.e., the sub-UE group or the first UE group) for which it is responsible or serves. For example, the indication information may include "Group AggregatedBitRate Monitoring". Optionally, the indication information may also be used to instruct (or trigger): the PCF performs monitoring and adjustment of the minimum bit rate of the UE in the UE group (i.e., the sub-UE group or the first UE group) for which it is responsible or serves. For example, the indication information may include "Min BitRate of UE Monitoring".

[0312] In other words, the indication information may indicate: triggering the PCF to perform aggregate bit rate monitoring and adjustment of the UE group (i.e., the sub-UE group or the first UE group) for which it is responsible or serves, or the PCF to perform at least one of monitoring and adjustment of the minimum bit rate of the UE in the UE group for which it is responsible or serves.

[0313] Optionally, the indication information in S805 may also be referred to as first indication information.

[0314] The parameter application conditions may include: the identifiers of all UEs in the internal UE group or at least one of the identifiers of an internal UE group (for example, a third UE group), a network slice identifier (S-NSSAI), and an application identifier (Application ID).

[0315] For example, assuming that: the network slice identifier in S801 to S804 is the identifier of the first network slice, the application identifier is the identifier of the first application, and the UE group identifier is the identifier of the third UE group, then for S805, the request message can carry: a list of all UEs included in the third UE group and at least one of the identifiers of the third UE group, as well as the first network slice identifier and the identifier of the first application.

[0316] It should also be understood that the request message in S805 also carries: a UE identity list (SUPI sub list) included in the sub-UE group corresponding to (or responsible for) the PCF.

[0317] For example, assuming that UE1 and UE2 form a UE sub group (UE sub Group), and this UE sub group (i.e., the first UE group) is responsible for or managed by PCF1, that is, PCF1 is a policy control function network element serving the first UE group. In S805, NEF may send a request message to PCF1, and the request message carries:

[0318] The identifier of the sub-UE group (first UE group) corresponding to (or responsible for) PCF1 or at least one of the UE identifier lists (SUPI sub list) included in the sub-UE group (first UE group), the network slice identifier, the application identifier, the internal UE group includes at least one of the identifiers of all UE lists (SUPI list) or the internal UE group, and the indication information. Among them, the internal UE group can also be called the third UE group, and the first UE group is a subset of the third UE group (or the internal UE group) (or the third UE group includes the first UE group).

[0319] Optionally, S805 can also be expressed as: the network open function network element sends fourth information to each policy control function network element in the policy control function network element set respectively, and the fourth information includes first indication information, and the first indication information is used to indicate: triggering (triggering) at least one of the aggregated bit rate monitoring of the first terminal device group corresponding to the first application in the first network slice, or the minimum bit rate monitoring of the terminal devices in the first terminal device group, and the fourth information also includes: the identification of all terminal devices in the first terminal device group or at least one of the identifications of the first terminal device group, the identification of all terminal devices in the third terminal device group or at least one of the identifications of the third terminal device group, the identification of the first network slice, and the identification of the first application. The terminal devices included in the first terminal device group are terminal devices managed by a policy control function network element, the first terminal device group is a subset of the second terminal device group, and the second terminal device group and the third terminal device group are the same terminal device group.

[0320] S806, each PCF in the PCF set obtains the bit rate corresponding to each UE in its corresponding sub-UE group from the UPF according to the request message.

[0321] As a possible implementation, after receiving the request information, each PCF can determine the SMF serving the UE in the sub-UE group, that is, determine the SMF (or SMF set) serving the sub-UE group, and the SMF set includes one or more SMFs. Then, according to the SMF set, the UPF set serving the sub-UE group is obtained from the SMF included in the SMF set, and the UPF set includes one or more UPFs. Finally, the PCF obtains the bit rate corresponding to each UE in the sub-UE group from the UPF included in the UPF set.

[0322] Exemplarily, in S806, each PCF may obtain a bit rate report corresponding to each UE in the sub-UE group from the UPF, and the bit rate report of the UE includes parameters such as the bit rate of the UE.

[0323] For example, assuming that UE1 and UE2 form a sub-UE group (UE sub Group), and this sub-UE group is responsible for or managed by PCF1, then in S806, PCF1 can obtain the bit rate corresponding to each UE in the sub-UE group (i.e., the first UE group) from UPF, that is, the bit rates corresponding to UE1 and UE2 respectively.

[0324] S807: Each PCF in the PCF set determines an aggregate bit rate of the sub-UE group according to a bit rate corresponding to each UE in the corresponding sub-UE group.

[0325] In some possible implementations, each PCF may determine the bit rate of each UE based on the bit rate report of each UE in the sub-UE group, and then add the bit rate of each UE in the sub-UE group to obtain the sub-UE group aggregate bit rate corresponding to the sub-UE group.

[0326] Optionally, in S807, each PCF may also determine a minimum bit rate of UEs in the sub-UE group (Min BitRate per S-NSSAI per App ID per UE) according to a bit rate corresponding to each UE in the corresponding sub-UE group.

[0327] For example, assuming that UE1 and UE2 form a sub-UE group (UE sub Group), and this sub-UE group (i.e., the first UE group) is responsible for or managed by PCF1, then in S807, PCF1 can determine the aggregate bit rate of the first UE group, and optionally, can also determine the minimum bit rate of the UEs in the first UE group.

[0328] Optionally, S806 and S807 can also be expressed as: the policy control function network element obtains first information, and the first information includes: the aggregated bit rate of the first terminal device group (i.e., the first UE group or sub-UE group) corresponding to the first application in the first network slice, or at least one of the minimum bit rates of the terminal devices in the first terminal device group corresponding to the first application in the first network slice.

[0329] S808, each PCF in the PCF set obtains from the UDR or UDM: a remaining group-aggregate bit rate (Remaining Group-Aggregate Bit Rate) and a first threshold.

[0330] Optionally, in S808, each PCF may also obtain from the UDR or UDM: a minimum bit rate threshold of UE in the UE group (Min BitRate of UE for UL / DL).

[0331] Optionally, in S808, each PCF may also obtain from the UDR or UDM: a maximum aggregate bit rate threshold of a UE group (Group-MBR for UL / DL).

[0332] Assumption: For PCF1, PCF1 is a PCF in the service PCF set. PCF1 can send a query request (for example, a first query request) to UDM or UDR, carrying: the internal UE group identifier (Internal Group ID) or at least one of the list of all UE identifiers in the internal UE group, the network slice identifier (S-NSSAI), and the application identifier (ApplicationID). After receiving the query request, UDR or UDM determines which UE group corresponds to the network slice identifier (S-NSSAI), application identifier (Application ID), and internal UE group identifier (Internal Group ID), and then determines the corresponding remaining group aggregate bit rate (Remaining Group-Aggregate Bit Rate) and the first threshold value of the UE group. The remaining group aggregate bit rate (Remaining Group-Aggregate Bit Rate) and the first threshold value are sent to PCF1.

[0333] Optionally, the UDR or UDM may also send at least one of a maximum aggregate bit rate threshold of the UE group (Group-MBR for UL / DL) or a minimum bit rate threshold of the UE in the UE group (Min BitRate of UE for UL / DL) to PCF1.

[0334] It should be understood that the remaining group aggregate bit rate in S808 corresponds to the remaining group aggregate bit rate of the internal UE group (i.e., the third UE group or the second UE group), rather than the remaining group aggregate bit rate of the sub-UE group (i.e., the first UE group) composed of UEs served by a certain PCF. Similarly, the UE group in the maximum aggregate bit rate threshold of the UE group refers to: the internal UE group (i.e., the third UE group or the second UE group), rather than the sub-UE group (i.e., the first UE group) composed of UEs served by a certain PCF.

[0335] For example, assuming that UE1 and UE2 form a UE sub group (UE sub Group), and this UE sub group (ie, the first UE group) is responsible for or managed by PCF1, then in S808, PCF1 can obtain from UDR: the remaining group aggregate bit rate of the third UE group and the first threshold.

[0336] Optionally, in S808, PCF1 may also obtain from UDR or UDM: a minimum bit rate threshold of UEs in the third UE group. Optionally, in S808, PCF1 may also obtain from UDR or UDM: a maximum aggregate bit rate threshold of the third UE group. The first UE group is a subset of the third UE group (or internal UE group).

[0337] Optionally, S808 can also be expressed as: the policy control function network element receives the second information from the data storage network element or the unified data management network element, the second information includes: the remaining group aggregate bit rate of the third terminal device group, optionally, the second information may also include: the first threshold or at least one of the minimum bit rate thresholds of the UE in the third terminal device group.

[0338] S809: Each PCF in the PCF set updates the aggregate bit rate of the remaining groups according to the aggregate bit rate of the sub-UE group corresponding to itself, to obtain an updated aggregate bit rate of the remaining groups.

[0339] As a possible implementation method, each PCF calculates the change value of the aggregate bit rate corresponding to the sub-UE group twice according to the change in the aggregate bit rate of the sub-UE group (the first UE group), and uses the change value to update the aggregate bit rate of the remaining group to obtain the updated aggregate bit rate of the remaining group (Modified Remaining Group-Aggregate Bit Rate).

[0340] For example, suppose UE1 and UE2 form a sub-UE group, which is under the charge or management of PCF1 and is called the first UE group. The aggregate bit rate of the remaining group is M. The aggregate bit rate of the sub-UE group (the first UE group) calculated by PCF1 at a certain time is N1, and the aggregate bit rate of the sub-UE group calculated at the next time is N2. The change values ​​of the aggregate bit rates corresponding to the two times are N2-N1, and then the aggregate bit rate of the remaining group is subtracted from the change, that is, M-(N2-N1), and the value obtained is the updated aggregate bit rate of the remaining group. It can be understood that the value of N2-N1 can be positive or negative. In other words, the updated aggregate bit rate of the remaining group can increase or decrease relative to the aggregate bit rate of the remaining group before the update.

[0341] Optionally, as a possible implementation method, the timing for the PCF to obtain and update the aggregate bit rate of the UE group can be continuously or periodically obtained and updated before the session established by the UE ends, that is, S808 and S809 can be executed multiple times. Alternatively, when the PCF finds that the value of the remaining group aggregate bit rate is relatively large, the PCF can configure a "local remaining group aggregate bit rate", and only when the "local remaining group aggregate bit rate" reaches a specific threshold or passes a specific time window (time period), the PCF interacts with the UDR or UDM to obtain and update the "remaining group aggregate bit rate". By configuring the "local remaining maximum slice data rate" by the PCF, the PCF can avoid frequent interactions with the UDR or UDM to obtain the "remaining group aggregate bit rate".

[0342] It should also be understood that for each PCF, when the PCF obtains the updated remaining group aggregate bit rate, it is necessary to store the updated remaining group aggregate bit rate in the UDR or UDM in a timely manner. In this way, the remaining group aggregate bit rate obtained by other PCFs from the UDR or UDM is the latest remaining group aggregate bit rate, thereby ensuring that the remaining group aggregate bit rate stored in the UDR or UDM can accurately reflect the actual remaining group aggregate bit rate of the UE group.

[0343] Optionally, as a possible implementation method, each PCF can use the Etags mechanism to ensure that the "remaining group aggregate bit rate" in the UDR or UDM can be correctly updated. Each PCF can also subscribe to the change notification of the network slice specific policy control information to the UDR or UDM, so that after the "remaining group aggregate bit rate" stored in the UDR or UDM changes, the UDR or UDM can promptly send the changed value of the remaining group aggregate bit rate to the PCF.

[0344] S810: Each PCF in the PCF set determines whether the updated remaining group aggregate bit rate meets the requirement.

[0345] For example, if the updated aggregate bit rate of the remaining group is greater than the first threshold, the updated aggregate bit rate of the remaining group does not meet the requirement. The updated aggregate bit rate of the remaining group is greater than the first threshold, which means that the value of the aggregate bit rate of the remaining group is relatively large, and the bit rate used by the UE in the UE group is relatively small. For the sub-UE group (first UE group) corresponding to the PCF, the sub-UE group aggregate bit rate may be lower than the set minimum aggregate bit rate, or the minimum bit rate of the UE in the sub-UE group may be less than the minimum bit rate threshold of the UE in the UE group, which may not meet the minimum requirement for normal transmission of the sub-UE group, and normal data transmission cannot be guaranteed.

[0346] Optionally, the first threshold may be determined by the maximum bit rate threshold of the UE group (eg, the third UE group) and the minimum bit rate threshold of the UE group. For example, the first threshold may be equal to the difference between the maximum bit rate threshold of the UE group and the minimum bit rate threshold of the UE group.

[0347] For another example, if the updated aggregate bit rate of the remaining group is less than or close to zero (or less than the second threshold), the updated aggregate bit rate of the remaining group does not meet the requirements. The updated aggregate bit rate of the remaining group is close to zero, which means that the value of the aggregate bit rate of the remaining group is relatively small, and the bit rate used by the UE in the UE group is relatively large. For the sub-UE group corresponding to the PCF, the sub-UE group aggregate bit rate may be greater than the set maximum aggregate bit rate. Although it can meet the requirements for normal transmission of the UE group service, it may affect other UEs or services. Optionally, the second threshold may be a value less than zero. When the second threshold is a value less than zero and the updated aggregate bit rate of the remaining group is less than the second threshold, it means that the bit rate used by the UE in the UE group has exceeded the set maximum value, and therefore may affect other UEs or services.

[0348] Of course, in the case where both the first threshold and the second threshold exist, if the updated aggregate bit rate of the remaining groups is less than or equal to the first threshold and greater than or equal to the second threshold, it is determined that the updated aggregate bit rate of the remaining groups meets the requirement.

[0349] Optionally, the PCF may also determine whether the bit rate of the UE in the sub-UE group meets the requirement based on the minimum bit rate of the UE in the sub-UE group (the first UE group) and the minimum bit rate threshold of the UE in the UE group (the third UE group). For example, if the minimum bit rate of the UE in the sub-UE group is less than or equal to the minimum bit rate threshold of the UE in the UE group, it is determined that the bit rate of the UE in the sub-UE group does not meet the requirement. In this case, the minimum requirement for normal transmission of the service of the UE group may not be met, and normal data transmission cannot be guaranteed.

[0350] S811: When the updated remaining group aggregate bit rate does not meet the requirement, each PCF in the PCF set generates an adjustment strategy.

[0351] Of course, if the minimum bit rate of the UE in the sub-UE group (first UE group) does not meet the requirements, for example, the minimum bit rate of the UE in the sub-UE group is less than or equal to the minimum bit rate threshold of the UE in the UE group (third UE group), then the PCF (for example, PCF1) can also generate an adjustment strategy.

[0352] It should be understood that in S811, when each PCF performs policy adjustment, it only adjusts the UEs in the UE list served by the PCF.

[0353] In some possible implementations, the adjustment strategy may include at least one of the following:

[0354] If the UE service quality flow in the sub-UE group (the first UE group) is a guaranteed bit rate service quality flow, modifying the maximum bit rate value of the guaranteed bit rate service quality flow;

[0355] Adjusting the ARP or priority parameter of the service quality flow of the UE in the sub-UE group (the first UE group);

[0356] The service quality flows of some UEs in the sub-UE group (the first UE group) are released.

[0357] After the adjustment strategy is determined, each PCF in the PCF set may execute the adjustment strategy.

[0358] Of course, in other implementations of the present application, the adjustment strategy may also include other bit rate adjustment strategies. After adjustment using the adjustment strategy, it can be achieved that: the aggregate bit rate of the remaining group meets the requirements (for example, less than or equal to the first threshold, or greater than the second threshold, etc.), or the minimum bit rate of the UE in the sub-UE group is greater than the minimum bit rate threshold of the UE in the UE group.

[0359] Optionally, in each step of method 800, the expression of "third UE group (i.e., third terminal device group)" may also be replaced by: "second UE group (i.e., second terminal device group)". That is, in the embodiment of method 800, the second terminal device group and the third terminal device group are the same terminal device group, and the first UE group is a subset of the second UE group or the third UE group (i.e., the second UE group or the third UE group includes the first UE group).

[0360] It should also be understood that in method 800, the description of "identifiers of UEs in a UE group" refers to identifiers corresponding to all UEs in the UE group, that is, a list of UE identifiers. For example, the description of "identifiers of UEs in the third group" refers to identifiers corresponding to all UEs in the third UE group. For another example, the description of "identifiers of UEs in the first group" refers to identifiers corresponding to all UEs in the first UE group. For another example, "identifiers of UEs included in an external UE group" refers to identifiers of all UEs included in an external UE group. For another example, "identifiers of UEs included in an internal UE group" refers to identifiers of all UEs included in an internal UE group.

[0361] In the method provided in the embodiment of the present application, the AF configures the remaining group-aggregate bit rate (Remaining Group-Aggregate Bit Rate) per slice per application per UE group (perSlice per Application per UE Group) in the UDR or UDM. Each PCF obtains the aggregate bit rate of the sub-UE group (for example, the first UE group) for which it is responsible, and then obtains and updates the remaining group-aggregate bit rate (for example, the remaining group-aggregate bit rate of the third UE group) from the UDR or UDM. When the remaining group-aggregate bit rate is close to zero or greater than the threshold, the PCF executes the corresponding adjustment strategy. The bit rate at the sub-UE group granularity is monitored and adjusted. It can ensure that the sub-UE group aggregate bit rate does not exceed the requirement to avoid affecting other UEs or services. It can also ensure that the aggregate bit rate of the sub-UE group is not lower than the set minimum aggregate bit rate to ensure the minimum requirement for normal transmission of the service, thereby improving communication efficiency.

[0362] Fig. 9 is a schematic interactive diagram of another example of a rate control method for a terminal device group in a network slice provided by the present application. The method 900 can be applied in Figure 5 The scenario shown can of course also be applied to other communication scenarios, and the embodiments of the present application are not limited here.

[0363] Fig. 9 In the process shown, AF sends a request message to NWDAF through NEF to request the aggregate bit rate monitoring result of each slice, each application, and each UE group (per Slice per Application per UE Group). Optionally, the request message includes the maximum bit rate requirement and / or minimum bit rate requirement of each slice, each application, and each UE group. When NWDAF finds that the aggregate bit rate monitoring result of the UE group does not meet the requirements, NWDAF sends a notification to AF, and AF triggers the policy adjustment. Fig. 9 As shown, Fig. 9 The method 900 shown in FIG. 1 may include S901 to S911. Fig. 9 Each step in method 900 is described in detail.

[0364] S901, AF sends a request message to NEF, the request message is used to subscribe (request) to NWDAF for at least one of the aggregate bit rate of a UE group corresponding to a certain application on a certain slice, or the minimum bit rate of UEs in the UE group. The request message includes: parameters and applicable conditions of the parameters.

[0365] Correspondingly, NEF receives the request information.

[0366] Optionally, the request information in S901 may also be referred to as seventh information, that is, the AF sends the seventh information to the NEF.

[0367] The parameters include at least one of the following:

[0368] Maximum aggregate bit rate threshold of the UE group (Group-MBR for UL / DL), minimum aggregate bit rate threshold of the UE group (Group-Min-BR for UL / DL), minimum bit rate threshold of the UE in the UE group (Min BitRate of UE for UL / DL);

[0369] The applicable conditions of the parameters (or can be called the applicable conditions of the configuration parameters) include: network slice identifier (S-NSSAI), application identifier (Application ID), and external UE group identifier (External Group ID).

[0370] Optionally, the applicable conditions of the configuration parameters in S901 may also include: the identifiers of all UEs included in the external UE group (i.e., the identifiers of a group of UEs). The identifiers of this group of UEs may be a group of GPSIs, or may be a group of IP addresses of UEs, etc. The embodiments of the present application are not limited here.

[0371] In other words, the applicable conditions of the configuration parameters in S901 may include: the identifiers of all UEs in the external UE group or at least one of the identifiers of the external UE group, the first network slice identifier, and the identifier of the first application.

[0372] It should be understood that if the request information in S901 requests: the aggregate bit rate of the first UE group corresponding to the first application on the first slice, the parameters include: at least one of the maximum aggregate bit rate threshold of the first UE group (Group-MBR for UL / DL), the minimum aggregate bit rate threshold of the first UE group, and the minimum bit rate threshold of the UE in the first UE group. The applicable conditions of the parameters include: at least one of the identifiers of all UEs in the first UE group or the external identifier of the first UE group, the identifier of the first network slice (S-NSSAI), and the identifier of the first application (Application ID).

[0373] For detailed description of the parameters and applicable conditions of the parameters, please refer to the description of S601 in method 600, which will not be repeated here for the sake of brevity.

[0374] Optionally, the request information in S901 may not include the above parameters, that is, it may not include: the maximum aggregate bit rate threshold of the UE group, the minimum aggregate bit rate threshold of the UE group, and the minimum bit rate threshold of the UE in the UE group, but may include the applicable conditions of the parameters.

[0375] In some possible implementations, the request information in S901 may also include: an analysis type identifier (Analytics ID). Since NWDAF can perform various different types of analysis on the UE, such as analyzing the mobility of the UE, the data volume or bit rate of the UE, etc., various different types of analysis results will be generated. Therefore, the request information may carry the type of analysis to instruct NWDAF to perform data volume and session-related analysis of the UE or UE group at different locations or different slices, that is, to analyze at least one of the aggregate bit rate of the UE group (such as the first UE group) or the minimum bit rate of the UE in the UE group. For example, the request information may include an analysis type identifier. Exemplarily, the analysis type identifier may be a hotspot analysis (Dispersion Analytics), indicating that AF requests hotspot analysis (i.e., analysis of the data volume and session-related analysis of the UE or UE group at different locations or different slices) from NWDAF.

[0376] Exemplarily, the AF may send an analysis exposure subscription request (Nnef_analytics exposure_subscribe) to the NEF to subscribe to the aggregate bit rate of the UE group corresponding to a certain service on a certain slice from the NWDAF. The analysis exposure subscription request carries: parameters, applicable conditions of the parameters, and analysis type identifier.

[0377] S902: NEF forwards the request information to NWDAF.

[0378] In S902, as a possible implementation manner, the NEF may first obtain, from the UDM, according to the identifier of the external UE group, the identifier of the internal UE group corresponding to the identifier of the external UE group and the identifiers of all UEs included in the internal UE group.

[0379] For example, the UDM may store the correspondence (mapping relationship) between the identifier of the external UE group and the identifier of the internal UE group, and the NEF may send a request message to the UDM, carrying the identifier of the external UE group (e.g., the external identifier of the first UE group), to request the UDM for the identifier of the corresponding internal UE group (e.g., the internal identifier of the first UE group). After receiving the request message, the UDM determines the identifier of the internal UE group corresponding to the identifier of the external UE group from the stored mapping relationship according to the identifier of the external UE group. Further, the UDM may also determine the identifiers of each UE included in the internal UE group according to the determined identifier of the internal UE group. It should be understood that the UEs included in the external UE group and the UEs included in the internal UE group are the same, that is, the UEs included in the external UE group and the internal UE group refer to the same UE group. The UDM will feed back the determined identifier of the internal UE group and the identifier list of each UE included in the internal UE group to the NEF. For example, the UDM may send the identifier of the internal UE group and the identifier list of the UE to the NEF via an SDM get response (Nudm_SDM_get response). In this case, in S902, in the request information forwarded by NEF to NWDAF, the applicable conditions of the configuration parameters include: network slice identifier (S-NSSAI), application identifier (ApplicationID), internal UE group identifier (Internal Group ID), and the identifiers of each UE included in the internal UE group.

[0380] As another possible implementation method, NEF can first obtain the identifier of the external UE group from UDM based on the identifier of the external UE group. In this case, in S902, in the request information forwarded by NEF to NWDAF, the applicable conditions of the configuration parameters include: network slice identifier (S-NSSAI), application identifier (Application ID), and internal UE group identifier (Internal Group ID).

[0381] As another possible implementation method, NNEF can forward the request information directly to NWDAF. In this case, in S902, the applicable conditions of the configuration parameters in the request information forwarded by NEF to NWDAF include: network slice identifier (S-NSSAI), application identifier (Application ID), and external UE group identifier (External Group ID).

[0382] For the relationship between the identifier of the external UE group and the identifier of the internal UE group, reference may be made to the description of the corresponding part of S601 in method 600, which will not be repeated here.

[0383] Optionally, if the applicable conditions of the configuration parameters in S901 include: the identifiers of all UEs in the external UE group (i.e., an external UE identifier list, such as a group of GPSIs or a group of UE IP addresses), the NEF can also obtain the internal UE identifier list based on the external UE identifier list. In S902, in the request information forwarded by the NEF to the NWDAF, the applicable conditions of the configuration parameters include: the network slice identifier (S-NSSAI), the application identifier (Application ID), and the identifiers of each UE included in the internal UE group.

[0384] For example, if the applicable conditions of the configuration parameters in S901 include a group of GPSIs, then in S902, the NEF may obtain the SUPI corresponding to the GPSI through the UDM, that is, obtain the identity list (SUPIlist) of all UEs in the corresponding internal UE group.

[0385] For another example, if the applicable conditions of the configuration parameters in S901 include a group of UE IP addresses, and NEF identifies that the UE IP address is an external IP address (i.e., a public network address (UE public IP address)) based on the configuration, for each UE IP address, in S902, NEF first discovers the UPF that supports the NAT function for the UE from NRF, and then sends a request to the UPF, the request includes the UE public network address (UE public IP address), and UPF obtains the UE private network address (UE private IP address) corresponding to the UE public network address based on the NAT function, and the UE private network address is a private IP address used within the network (i.e., an internal address), and then UPF feeds back the UE private network address (UE private IP address) to NEF. In this way, NEF can obtain the identification list (UE private network address list) of all UEs in the internal UE group.

[0386] Exemplarily, NEF can send an analysis subscription request (Nnwsdf_analytics_subscription_subscribe) to NWDAF, which is used to instruct: AF subscribes to NWDAF for the aggregate bit rate of the UE group corresponding to a certain service on a certain slice, and / or the minimum bit rate of the UE in the UE group. The analysis subscription request carries: parameters, applicable conditions of the parameters, and analysis type identifier.

[0387] Optionally, the above S901 and S902 can also be collectively referred to as: AF subscribes to the aggregate bit rate of the UE group corresponding to a certain service on the slice and / or the minimum bit rate of the UE in the UE group to NWDAF through NEF, and the subscription message carries: configuration parameters and applicable conditions of the configuration parameters.

[0388] For example, assume that the request information in S901 is used to request at least one of the aggregate bit rate of the first UE group corresponding to the first application on the first network slice, or the minimum bit rate of the UE in the first UE group. Then the applicable conditions of the parameters in S901 include: the first network slice identifier, the identifier of the first application, and the external identifier of the first UE group, and in S902, the applicable conditions of the parameters include: the first network slice identifier, the identifier of the first application, the internal identifier or the external identifier of the first UE group.

[0389] S903, after receiving the request information, the NWDAF obtains the identifier list of UEs included in the internal UE group from the UDM according to the identifier of the internal UE group (Internal Group ID).

[0390] For example, the UDM may store the identifier of each UE in an internal UE group (e.g., the first UE group). NEF may send a request message to the UDM. For example, the request message may be an SDM acquisition request (Nudm_SDM_get request), carrying the identifier of the internal UE group (e.g., the first UE group), and is used to request the UDM for the identifier of the UE in the internal UE group. After receiving the request message, the UDM determines the identifiers of each UE included in the internal UE group based on the identifier of the internal UE group. For example, the UDM may send a list of identifiers of the UEs included in the internal UE group to the NEF via an SDM acquisition response (Nudm_SDM_get response).

[0391] For example, the UDM may determine a UE identity list (SUPI list) and send it to the NEF. The UE identity list is an identity list of UEs included in the internal UE group. The identity list of UEs included in the internal UE group is an identity list of all UEs in the internal UE group.

[0392] It should be understood that S903 is an optional step. If the applicable conditions of the configuration parameters in the request information forwarded by the NEF to the NWDAF in S902 include: the identifiers of all UEs in the internal UE group, the NWDAF may not execute S903 and directly execute S904.

[0393] If the applicable condition of the configuration parameter in the request information forwarded by the NEF to the NWDAF in S902 includes: the identifier of the internal UE group, the NWDAF needs to execute S903.

[0394] If the applicable conditions of the configuration parameters in the request information forwarded by NEF to NWDAF in S902 include: the identifier of the external UE group, then S903 can be replaced by: NWDAF retrieves the corresponding internal UE group identifier and UE identifier list from UDM based on the identifier of the external UE group, and the UE identifier list is a list of identifiers of all UEs in the internal UE group.

[0395] For example, assume that: in S902, the applicable conditions of the parameters include: a first network slice identifier, an identifier of a first application, and a first UE table.

[0396] S904, NWDAF obtains a serving PCF set for the UE from BSF according to the UE identity list, where the PCF set includes one or more PCFs. The UE identity list is an identity list of all UEs in the internal UE group.

[0397] In some possible implementations, the PCFs serving different UEs may be different. In other words, one PCF can serve, be responsible for or manage one or more UEs, and the UEs included in the internal UE group (for example, the first UE group) may be served by different PCFs. Therefore, in S804, the NWDAF may obtain the service PCF set corresponding to all UEs in the internal UE group, and the service PCF set includes one or more service PCFs (hereinafter, for the convenience of description, the service PCF will be referred to as PCF). In this case, the NWDAF can also count which UEs each PCF corresponds to (or which UEs it serves). Optionally, the service PCF set can also be expressed as: PCF(s).

[0398] For example, assuming that the internal UE group (for example, the first UE group) includes 6 UEs, namely UE1 to UE6, the information finally determined by the NWDAF may be in the following form:<PCF1:UE1,UE2> ,<PCF2:UE3,UE4,UE5> ,<PCF3:UE6> , indicating that PCF1 serves UE1 and UE2; PCF2 serves UE3 to UE5; and PCF3 serves UE6.

[0399] Exemplarily, in S904, NWDAF may send a management discovery request (Nbsf_management_discovery request) to BSF, carrying a UE identification list. After receiving the request, BSF determines the serving PCF set of the UE, and feeds back the PCF set to NWDAF by sending a management discovery response (Nbsf_management_discovery response).

[0400] S905, NWDAF obtains the SMF set serving the internal UE group from the PCF included in the PCF set based on the network slice identifier (S-NSSAI), application identifier (Application ID) and UE identifier list, and the SMF set includes one or more SMFs.

[0401] In some possible implementations, NWDAF may send a request message to each PCF in the service PCF set, where the request message includes: a network slice identifier, an application identifier, and an identifier of the UE served by the PCF (UE sub-list). The PCF determines the serving SMF of the UE based on this information, and then sends it to the NWDAF. It can be understood that for a PCF, the serving SMF corresponding to the UE served by the PCF may include one or more. Each PCF in the PCF set may send the SMF corresponding to the UE it serves to the NWDAF. In this way, based on the information fed back by each PCF, the NWDAF can determine the SMF (serving SMF) serving the UE included in the internal UE group.

[0402] In other words, the NWDAF may determine an SMF set, which includes one or more SMFs, which serve multiple UEs included in the internal UE group. Optionally, the SMF set may also be expressed as: SMF(s).

[0403] For example, assuming that the internal UE group (for example, the first UE group) includes 6 UEs, namely UE1 to UE6, the information finally determined by the NWDAF may be in the following form:<PCF1:UE1,SMF1;UE2,SMF2> ,<PCF2:UE3,UE4,UE5;SMF3> ,<PCF3:UE6;SMF4> , indicating that: PCF1 serves UE1 and UE2, SMF1 serves UE1, SMF2 serves UE2; PCF2 serves UE3 to UE5, SMF3 serves UE3 to UE5; PCF3 serves UE6, and SMF4 serves UE6. Combining the above examples, NWDAF can determine SMF1, SMF2, SMF3 and SMF4, which include all SMFs serving multiple UEs included in the internal UE group.

[0404] As a possible implementation method, NWDAF can send an event open subscription request (Npcf_eventexposure_subscribe) to each PCF, carrying: network slice identifier (S-NSSAI), application identifier (Application ID) and UE identifier list. After receiving the subscription request, PCF sends an event open subscription notification (Npcf_eventexposure_notify) to NWDAF, carrying one or more SMFs corresponding to the UE managed by the PCF, or one or more SMFs serving the UE managed by the PCF. NWDAF can determine the SMF serving each UE based on the information fed back by each PCF in the PCF set, that is, determine the SMF (or SMF set) serving the internal UE group, and the SMF set includes one or more SMFs. The UE managed by each PCF can form a sub-UE group (UE sub Group), and the sub-UE groups managed by all PCFs in the PCF set form a UE group (UE Group), that is, the internal UE group or external UE group mentioned above. The UE identifier list included in a sub-UE group can also be called a sub-UE group identifier list (SUPI sub list).

[0405] S906, NWDAF obtains the UPF set serving the internal UE group from the SMFs included in the SMF set according to the SMF set, and the UPF set includes one or more UPFs.

[0406] As a possible implementation method, NWDAF can send an event open subscription request (Nsmf_eventexposure_subscribe) to each SMF in the SMF set, carrying the list of UE identities served or responsible by the SMF. After receiving the subscription request, SMF sends an event open subscription notification (Nsmf_eventexposure_notify) to NWDAF, carrying one or more UPFs corresponding to multiple UEs served by the SMF. Based on the information fed back by each SMF in the SMF set, NWDAF can determine the UPF serving each UE in the internal UE group, that is, determine the UPF (or UPF set) serving the internal UE group, and the UPF set includes one or more UPFs. The UE managed (or served) by each UPF can form a sub-UE group (UE sub Group), and the sub-UE groups managed by all UPFs in the UPF set constitute a UE group (first UE group). The list of UE identities included in a sub-UE group can also be called a sub-UE group identity list (SUPI sub list).

[0407] Optionally, the UPF set can also be expressed as: UPF(s).

[0408] S907, NWDAF obtains the bit rate corresponding to each UE in the internal UE group from the UPF in the UPF set.

[0409] For example, assuming that the network slice identifier in S901 to S906 is the identifier of the first network slice, the ApplicationID identifier is the first application, and the internal UE group identifier is the first UE group, the NWDAF can obtain from the UPF in the UPF set the bit rate corresponding to each UE in the first UE group (i.e., the internal UE group) running the first application on the first network slice identifier.

[0410] Exemplarily, in S907, NWDAF may obtain a bit rate report corresponding to each UE in an internal UE group (eg, the first UE group) from UPF via SMF, where the UE bit rate report includes parameters such as the bit rate of the UE.

[0411] As a possible implementation method, NWDAF can send an event exposure subscription request (Nupf_event exposure_subscribe) to each UPF, carrying: application identifier (Application ID) and the list of UE identifiers served or responsible by the UPF. After receiving the subscription request, UPF sends an event exposure subscription notification (Npcf_eventexposure_notify) to NWDAF, carrying the corresponding bit rate report for each UE managed (served) by the UPF. Based on the information fed back by each UPF, NWDAF can determine the bit rate of each UE in the UE group (i.e., the internal UE group).

[0412] S908, the NWDAF determines at least one of a UE group aggregate bit rate corresponding to the UE group or a minimum bit rate of the UEs in the UE group according to the bit rate corresponding to each UE in the UE group.

[0413] In some possible implementations, NWDAF can determine the bit rate of each UE based on the bit rate report of each UE in the UE group, and then add the bit rate of each UE in the UE group to obtain the UE group aggregate bit rate (Aggregate Bit Rate per S-NSSAI per App ID per UE Group) corresponding to the UE group.

[0414] In some other possible implementations, the NWDAF may determine the minimum bit rate of the UEs in the UE group (Min BitRate per S-NSSAI per App ID per UE) based on the bit rate report of each UE in the UE group.

[0415] It should be understood that the "UE group" in S908 is the internal UE group mentioned above.

[0416] S909, the NWDAF sends at least one of the UE group aggregate bit rate corresponding to the UE group or the minimum bit rate of the UEs in the UE group to the AF through the NEF.

[0417] For example, assuming that: the network slice identifier in S901 to S908 is the identifier of the first network slice, the application identifier is the identifier of the first application, and the UE group identifier is the identifier of the first UE group, then in S909, NWDAF can send at least one of the UE group aggregate bit rate corresponding to the first UE group, or the minimum bit rate of the UE in the first UE group to AF through NEF.

[0418] Optionally, S909 can also be expressed as: NWDAF sends ninth information to AF, and the ninth information includes: the aggregated bit rate of the first terminal device group corresponding to the first application in the first network slice, or at least one of the minimum bit rates of the terminal devices in the first terminal device group corresponding to the first application in the first network slice.

[0419] Optionally, in S909, as another possible implementation, the NWDAF may also compare: the aggregate bit rate of the UE group (for example, the first UE group) with the maximum aggregate bit rate threshold of the UE group (the first UE group), compare the aggregate bit rate of the UE group with the minimum aggregate bit rate threshold of the UE group, obtain the comparison result, and then send the comparison result to the AF through the NEF. For example, the comparison result may include: the aggregate bit rate of the UE group (the first UE group) is greater than the maximum aggregate bit rate threshold of the UE group (the first UE group), the aggregate bit rate of the UE group is less than the minimum aggregate bit rate threshold of the UE group, or the aggregate bit rate of the UE group is less than or equal to the maximum aggregate bit rate threshold of the UE group, and greater than or equal to the minimum aggregate bit rate threshold of the UE group.

[0420] Optionally, in S909, as another possible implementation, the NWDAF may also compare the minimum bit rate of the UE in the UE group (for example, the first UE group) with the minimum bit rate threshold of the UE in the UE group (the first UE group), and then send the comparison result to the AF through the NEF. For example, the comparison result may include at least one of: the minimum bit rate of the UE in the UE group (the first UE group) is less than or equal to the minimum bit rate threshold of the UE in the UE group (the first UE group), or the minimum bit rate of the UE in the UE group is greater than the minimum bit rate threshold of the UE in the UE group.

[0421] Optionally, the NWDAF may send the above comparison result to the AF via the NEF. That is, the ninth information may also include the above comparison result.

[0422] Optionally, S909 can also be expressed as: AF receives the eighth information in response to the seventh information, and the eighth information includes: the aggregated bit rate of the first terminal device group (i.e., the first UE group) corresponding to the first application in the first network slice, the minimum bit rate of the terminal devices in the first terminal device group corresponding to the first application in the first network slice, indication information used to indicate that the aggregated bit rate of the first terminal device group is greater than the maximum aggregated bit rate threshold of the first terminal device group, indication information used to indicate that the aggregated bit rate of the first terminal device group is less than the minimum aggregated bit rate threshold of the first terminal device group, or at least one of the indication information used to indicate that the minimum bit rate of the terminal devices in the first terminal device group is less than the minimum bit rate threshold of the terminal devices in the first terminal device group.

[0423] Optionally, in S909, as another possible implementation method, NWDAF may also compare the aggregate bit rate of the UE group (for example, the first UE group) with the maximum aggregate bit rate threshold of the UE group (first UE group). When the aggregate bit rate of the UE group (first UE group) is greater than or equal to the maximum aggregate bit rate threshold of the UE group (first UE group), or the aggregate bit rate of the UE group is less than or equal to the minimum aggregate bit rate threshold of the UE group, NWDAF may send an indication message to AF via NEF, and the indication message is used to indicate that AF needs to generate an adjustment strategy.

[0424] Optionally, in S909, as another possible implementation method, NWDAF may also compare the minimum bit rate of UEs in a UE group (for example, the first UE group) with the minimum bit rate threshold of UEs in the UE group (first UE group). When the minimum bit rate of UEs in the UE group (first UE group) is less than or equal to the minimum bit rate threshold of UEs in the UE group (first UE group), NWDAF may send an indication message to AF via NEF, and the indication message is used to indicate that AF needs to generate an adjustment strategy.

[0425] S910, the AF determines whether the bit rate of the UE group meets the requirement based on the information from the NWDAF.

[0426] For example, if the NWDAF sends at least one of: the UE group aggregate bit rate corresponding to the UE group (for example, the first UE group) or the minimum bit rate of the UE in the UE group to the AF. Then the AF can compare the UE group aggregate bit rate corresponding to the UE group with the maximum aggregate bit rate threshold of the UE group (for example, the first UE group), or compare the UE group (for example, the first UE group) aggregate bit rate with the minimum aggregate bit rate threshold of the UE group to obtain a comparison result. The comparison result may include: the aggregate bit rate of the first UE group is greater than the maximum aggregate bit rate threshold of the first UE group, the aggregate bit rate of the first UE group is less than the minimum aggregate bit rate threshold of the first UE group, or the aggregate bit rate of the first UE group is less than or equal to the maximum aggregate bit rate threshold of the first UE group, and greater than or equal to at least one of the minimum aggregate bit rate threshold of the first UE group.

[0427] If the NWDAF sends the minimum bit rate of the UE in the first UE group to the AF, the AF may compare the minimum bit rate of the UE in the first UE group with the minimum bit rate threshold of the UE in the first UE group to obtain a comparison result. For example, the comparison result may include at least one of: the minimum bit rate of the UE in the first UE group is less than the minimum bit rate threshold of the UE in the first UE group, or the minimum bit rate of the UE in the first UE group is greater than or equal to the minimum bit rate threshold of the UE in the first UE group.

[0428] Optionally, the AF may also use the comparison result sent by the NWDAF to determine whether the bit rate of the UE group meets the requirement.

[0429] For example, if the aggregate bit rate of the UE group (first UE group) is greater than the maximum aggregate bit rate threshold of the UE group (first UE group), it is determined that the aggregate bit rate of the UE group (first UE group) does not meet the requirement. In this case, although the requirement for normal transmission of the service of the UE group (first UE group) can be met, it may affect other UEs or services.

[0430] For another example, if the aggregate bit rate of the UE group (first UE group) is less than the minimum aggregate bit rate threshold of the UE group (first UE group), it is determined that the aggregate bit rate of the UE group (first UE group) does not meet the requirement. In this case, the minimum requirement for normal transmission of the service of the UE group may not be met, and normal transmission of the service data cannot be guaranteed.

[0431] For another example, if the minimum bit rate of the UE in the UE group (first UE group) is less than the minimum bit rate threshold of the UE in the UE group (first UE group), it is determined that the bit rate of the UE group (first UE group) does not meet the requirement. In this case, the minimum requirement for normal transmission of the service of the UE group may not be met, and normal transmission of the service data cannot be guaranteed.

[0432] Of course, if in S909, the NWDAF sends indication information to the AF through the NEF, and the indication information is used to indicate that the AF needs to generate an adjustment strategy, then S910 can be omitted, and S911 is directly executed after S909, and S911 can be replaced by: the AF generates an adjustment strategy according to the indication information.

[0433] S911: When the bit rate of the UE group does not meet the requirement, the AF generates an adjustment strategy.

[0434] In some possible implementations, the adjustment strategy may include at least one of the following:

[0435] If the UE service quality flow in the UE group (for example, the first UE group) is a guaranteed bit rate service quality flow, modifying the maximum bit rate value of the guaranteed bit rate service quality flow;

[0436] Adjusting the ARP or priority parameter of the service quality flow of the UE in the UE group (for example, the first UE group);

[0437] The service quality flows of some UEs in the internal UE group (for example, the first UE group) are released.

[0438] Of course, in other implementations of the present application, the adjustment strategy may also include other bit rate adjustment strategies. After adjustment using the adjustment strategy, it can be achieved that: the UE group aggregate bit rate is less than the maximum bit rate threshold of the UE group and greater than the minimum bit rate threshold of the UE group, or the minimum bit rate of the UE in the UE group is greater than the minimum bit rate threshold of the UE in the UE group.

[0439] When the AF generates an adjustment policy, the AF may send the adjustment policy to the PCF, and the PCF finally executes the adjustment policy.

[0440] Optionally, in each step of method 900, the expression "first UE group (i.e., first terminal device group)" may also be replaced by: "third UE group (i.e., third terminal device group)". That is, in the embodiment shown in method 900, the first terminal device group and the third terminal device group are the same terminal device group.

[0441] It should also be understood that in method 900, the expression "identifiers of UEs in a UE group" refers to identifiers corresponding to all UEs in the UE group, that is, a list of UE identifiers. For example, the description of "identifiers of UEs in a first group" refers to identifiers corresponding to all UEs in the first UE group. For another example, "identifiers of UEs included in an external UE group" refers to identifiers of all UEs included in an external UE group. For another example, "identifiers of UEs included in an internal UE group" refers to identifiers of all UEs included in an internal UE group.

[0442] In the method provided in the embodiment of the present application, AF subscribes to at least one of the aggregate bit rate information of each slice per application per UE group (perSlice per Application per UE Group) or the minimum bit rate information of UE in the UE group to NWDAF through NEF, and requests at least one of the maximum aggregate bit rate threshold of each slice per application per UE group, the threshold of the minimum aggregate bit rate of the UE group, or the minimum bit rate threshold of the UE in the UE group in the message. NWDAF compares the acquired UE group aggregate bit rate and / or the minimum bit rate of the UE in the UE group with the requirements in the request information of AF to determine whether the requirements can be met. If not, AF is notified, and the execution policy adjustment is triggered by AF to realize the monitoring and adjustment of the bit rate at the UE group granularity. It can ensure that the aggregate bit rate of the UE group does not exceed the requirements to avoid affecting other UEs or services, and it can also ensure that the aggregate bit rate of the UE group is not lower than the set minimum aggregate bit rate to ensure the minimum requirements for normal transmission of the service, thereby improving communication efficiency.

[0443] Fig.10 is a schematic interactive diagram of another example of a rate control method for a terminal device group within a network slice provided by the present application. The method 1000 can be applied in Figure 5 The scenario shown can of course also be applied to other communication scenarios, and the embodiments of the present application are not limited here.

[0444] Fig.10 In the process shown, the AF directly sends a request message to the NEF to request the aggregate bit rate monitoring result of each slice, each application, and each UE group (per Slice per Application per UE Group). Optionally, the request message includes the maximum bit rate requirement and / or minimum bit rate requirement of each slice, each application, and each UE group. When the NEF finds that the aggregate bit rate monitoring result of the UE group does not meet the requirements, the NEF sends a notification to the AF, and the AF triggers the policy adjustment. Fig.10 As shown, Fig.10 The method 1000 shown in FIG. 1 may include S1001 to S1011. Fig.10 Each step in method 1000 is described in detail.

[0445] S1001, AF sends a request message to NEF, where the request message includes: applicable conditions and indication information of parameters.

[0446] Correspondingly, NEF receives the request information.

[0447] Optionally, the request information in S1001 may also be referred to as seventh information, that is, the AF sends the seventh information to the NEF.

[0448] For example, the request information may be a request to create an AF session that meets specific QoS requirements (AFsession with required QoS create request).

[0449] For another example, the request information may also be a request to update an AF session that meets specific QoS requirements (AFsession with required QoS update request).

[0450] Among them, the applicable conditions of the parameters (or can be called the applicable conditions of the configuration parameters) include: network slice identifier (S-NSSAI), application identifier (Application ID), and external UE group identifier (External Group ID).

[0451] Optionally, the applicable conditions of the parameters in S1001 may also include: the identifiers of all UEs included in the external UE group (i.e., the identifiers of a group of UEs). The identifiers of this group of UEs may be a group of GPSIs, or may also be a group of IP addresses of UEs, etc. The embodiments of the present application are not limited here.

[0452] In other words, the applicable conditions of the parameters in S1001 may include: the identifiers of all UEs in the external UE group or at least one of the identifiers of the external UE group, the network slice identifier, and the application identifier.

[0453] The indication information may indicate (or trigger) that the PCF performs at least one of monitoring and adjusting the aggregate bit rate of the UE Group, or monitoring and adjusting the minimum bit rate of the UE in the UE Group. For example, the indication information may include "Group Aggregated BitRate Monitoring", which is used to indicate (or trigger) that the PCF performs monitoring and adjusting the aggregate bit rate of the UE Group. For another example, the indication information may include "Min BitRate of UE Monitoring", which is used to indicate (or trigger) that the PCF performs monitoring and adjusting the minimum bit rate of the UE in the UE Group.

[0454] Optionally, the indication information in S1001 may also be referred to as second indication information.

[0455] Optionally, the request information may also include: at least one of the maximum aggregate bit rate threshold of the UE group (Group-MBR for UL / DL), the minimum aggregate bit rate threshold of the UE group (Group-Min-BR for UL / DL), and the minimum bit rate threshold of the UE in the UE group (Min BitRate of UE for UL / DL). That is, the request information may also include parameters.

[0456] For example, assuming that: the applicable conditions of the parameters in S1001 include: the identifiers of all UEs in the third UE group or at least one of the external identifiers of the third UE group, the first network slice identifier, and the identifier of the first application, then the parameters in S1001 include: the maximum bit rate threshold of the third UE group, the minimum bit rate threshold of the third UE group, and at least one of the minimum bit rate threshold of the UEs in the third UE group.

[0457] For the description of each parameter included in the request information, please refer to the description of each parameter in the above method 900, which will not be repeated here.

[0458] S1002. The NEF obtains the internal UE group identifier and the UE identifier list from the UDM according to the external UE group identifier. The UE identifier list is a list of identifiers of UEs included in the internal UE group.

[0459] S1003. The NEF obtains the serving PCF set for the UE from the BSF according to the UE identification list.

[0460] Optionally, in method 1000, the sub-UE group consisting of UEs that each PCF is responsible for can be called a first terminal device group or a first UE group, the internal UE can be called a third terminal device group or a third UE group, the first UE group is a subset of the third UE group, or the third UE group includes the first UE group.

[0461] Optionally, a PCF set can also be expressed as: PCF(s).

[0462] S1004. The NEF sends a request message to each PCF in the serving PCF set. The request message carries: parameter application conditions, indication information, and a sub-UE identity list (SUPI sub list) corresponding to the PCF.

[0463] Correspondingly, each PCF in the PCF set (ie, the service PCF set) receives the request message.

[0464] Optionally, the information carried in the request information in S1004 may also be referred to as fourth information.

[0465] The indication information is used to instruct (or trigger) the PCF to perform aggregate bit rate monitoring and adjustment of the UE group (i.e., the sub-UE group or the first UE group) for which it is responsible or serves. For example, the indication information may include "Group AggregatedBitRate Monitoring". Optionally, the indication information may also be used to instruct (or trigger): the PCF performs monitoring and adjustment of the minimum bit rate of the UE in the UE group (i.e., the sub-UE group or the first UE group) for which it is responsible or serves. For example, the indication information may include "Min BitRate of UE Monitoring".

[0466] In other words, the indication information can indicate (or trigger) that the PCF performs aggregate bit rate monitoring and adjustment of the UE group (i.e., sub-UE group or first UE group) for which it is responsible or serves, or that the PCF performs at least one of monitoring and adjustment of the minimum bit rate of the UE in the UE group for which it is responsible or serves.

[0467] Optionally, the indication information in the request message may also be referred to as first indication information.

[0468] Parameter applicability conditions may include: network slice identifier (S-NSSAI) and application identifier (Application ID).

[0469] For example, assuming that: the network slice identifier in S1001 and S1002 is the identifier of the first network slice, the application identifier is the identifier of the first application, and the UE group identifier is the identifier of the third UE group, then for S1004, the request message can carry: as well as the first network slice identifier and the identifier of the first application.

[0470] It should also be understood that the request message in S1004 also carries: a list of all UE identities (SUPI sub list) included in the sub-UE group or the first UE group corresponding to (or responsible for) the PCF.

[0471] For example, assuming that UE1 and UE2 form a UE sub group (UE sub Group), and this UE sub group (i.e., the first UE group) is responsible for or managed by PCF1, that is, PCF1 is a policy control function network element serving the first UE group. In S1004, NEF may send a request message to PCF1, and the request message carries:

[0472] The identifier of the sub-UE group (first UE group) corresponding to (or responsible for) PCF1 or at least one of the lists of all UE identifiers (SUPI sub list) included in the sub-UE group (first UE group), the network slice identifier, the application identifier, and indication information.

[0473] S1005, each PCF in the PCF set obtains the bit rate corresponding to each UE in its corresponding sub-UE group from the UPF according to the request message.

[0474] S1006: Each PCF in the PCF set determines an aggregate bit rate of the sub-UE group according to a bit rate corresponding to each UE in the corresponding sub-UE group.

[0475] For the above-mentioned S1002 to S1006, reference may be made to the detailed description of S803 to S807 in method 800, which will not be repeated here for the sake of brevity.

[0476] S1007: Each PCF in the PCF set sends the aggregate bit rate of the sub-UE group it is responsible for to the NEF.

[0477] Optionally, in S1007, each PCF in the PCF set also sends the minimum bit rate of the UEs in the sub-UE group (first UE group) for which it is responsible to the NEF.

[0478] For example, each PCF in the PCF set can send the aggregate bit rate of the sub-UE group (first UE group) it is responsible for or the minimum bit rate of the UE in the sub-UE group (first UE group) it is responsible for to the NEF through a policy authorization create / update response message.

[0479] Optionally, assuming that: the sub-UE group composed of UEs that each PCF is responsible for can be called the first terminal device group or the first UE group, and the UE group (internal UE group or external UE group) in S1001 and S1002 is the third terminal device group or the third UE group, then S1007 can also be described as: the NEF receives the fifth information from each PCF in the PCF set, and the fifth information includes: the aggregate bit rate of the first terminal device group, or at least one of the minimum bit rates of the terminal devices in the first terminal device group. Among them, the first UE group is a subset of the third UE group (or internal UE group), or the third UE group includes the first UE group.

[0480] S1008: The NEF determines at least one of a UE group aggregate bit rate corresponding to the UE group or a minimum bit rate of UEs in the UE group according to information fed back by each PCF in the PCF set.

[0481] For example, the NEF may add the aggregate bit rates of the sub-UE groups (eg, the first UE group) fed back by each PCF in the PCF set to obtain the aggregate bit rate of the UE group (eg, the third UE group). The UE group is the internal UE group mentioned above.

[0482] Optionally, the NEF may also determine the minimum bit rate of the UE in the UE group (e.g., the third UE group) based on the minimum bit rate of the UE in the sub-UE group (e.g., the first UE group) fed back by each PCF in the PCF set. For example, the minimum bit rate of the UE with the smallest value may be determined as the minimum bit rate of the UE in the UE group.

[0483] S1009: The NEF sends at least one of the UE group aggregate bit rate corresponding to the UE group or the minimum bit rate of the UEs in the UE group to the AF.

[0484] For example, the NEF may send at least one of the UE group aggregate bit rate corresponding to the third UE group or the minimum bit rate of the UEs in the third UE group to the AF.

[0485] Optionally, in some other possible implementations, if the request information (seventh information) in S1001 includes: the maximum aggregate bit rate threshold of the UE group and the minimum aggregate bit rate threshold of the UE group. The NEF may also compare: the aggregate bit rate of the UE group (e.g., the third UE group) with the maximum aggregate bit rate threshold of the UE group (the third UE group), compare the aggregate bit rate of the UE group with the minimum aggregate bit rate threshold of the UE group, obtain the comparison result, and then send the comparison result to the AF. For example, the comparison result may include: the aggregate bit rate of the third UE group is greater than the maximum aggregate bit rate threshold of the third UE group, the aggregate bit rate of the third UE group is less than the minimum aggregate bit rate threshold of the third UE group, or the aggregate bit rate of the third UE group is less than or equal to the maximum aggregate bit rate threshold of the third UE group, and greater than or equal to the minimum aggregate bit rate threshold of the third UE group.

[0486] Optionally, as another possible implementation, if the request information in S1001 includes: the minimum bit rate threshold of the UE in the UE group. NEFF may also compare: the minimum bit rate of the UE in the UE group (for example, the third UE group) with the minimum bit rate threshold of the UE in the UE group (the third UE group), obtain a comparison result, and then send the comparison result to AF. For example, the comparison result may include: the minimum bit rate of the UE in the UE group (the third UE group) is less than or equal to the minimum aggregate bit rate threshold of the UE in the UE group (the third UE group), or the minimum aggregate bit rate of the UE in the UE group is greater than at least one of the minimum bit rate threshold of the UE in the UE group.

[0487] In this case, in S1009 , the NEF may also send the above comparison result to the AF.

[0488] For example, assuming that in method 1000, the sub-UE group composed of UEs for which each PCF is responsible can be referred to as a first terminal device group or a first UE group, and the UE group (internal UE group or external UE group) in S1001 and S1002 is a third terminal device group or a third UE group, S1009 can also be expressed as:

[0489] NEF sends sixth information to AF, and the sixth information includes: the aggregated bit rate of the third terminal device group corresponding to the first application in the first network slice, the minimum bit rate of the terminal devices in the third terminal device group corresponding to the first application in the first network slice, indication information used to indicate that the aggregated bit rate of the third terminal device group is greater than the maximum aggregated bit rate threshold of the third terminal device group, indication information used to indicate that the aggregated bit rate of the third terminal device group is less than the minimum aggregated bit rate threshold of the third terminal device group, and indication information used to indicate that the minimum bit rate of the terminal devices in the third terminal device group is less than the minimum bit rate threshold of the terminal devices in the third terminal device group.

[0490] Alternatively, S1009 can also be expressed as:

[0491] AF receives eighth information in response to the seventh information, and the eighth information includes: an aggregated bit rate of the third terminal device group corresponding to the first application in the first network slice, a minimum bit rate of the terminal devices in the third terminal device group corresponding to the first application in the first network slice, indication information used to indicate that the aggregated bit rate of the third terminal device group is greater than a maximum aggregated bit rate threshold of the third terminal device group, indication information used to indicate that the aggregated bit rate of the third terminal device group is less than a minimum aggregated bit rate threshold of the third terminal device group, and indication information used to indicate that the minimum bit rate of the terminal devices in the third terminal device group is less than a minimum bit rate threshold of the terminal devices in the third terminal device group.

[0492] Optionally, in S1009, as another possible implementation method, the NEF may also compare the aggregate bit rate of the UE group (for example, the third UE group) with the maximum aggregate bit rate threshold of the UE group (the third UE group). When the aggregate bit rate of the UE group (the third UE group) is greater than or equal to the maximum aggregate bit rate threshold of the UE group (the third UE group), or the aggregate bit rate of the UE group is less than or equal to the minimum aggregate bit rate threshold of the UE group, the NEF sends an indication message to the AF, where the indication message is used to indicate that the AF needs to generate an adjustment strategy.

[0493] Optionally, in S1009, as another possible implementation method, the NEF may also compare the minimum bit rate of the UE in the UE group (for example, the third UE group) with the minimum bit rate threshold of the UE in the UE group (the third UE group). When the minimum bit rate of the UE in the UE group (the third UE group) is less than or equal to the minimum bit rate threshold of the UE in the UE group (the third UE group), the NEF sends an indication message to the AF, and the indication message is used to indicate that the AF needs to generate an adjustment strategy.

[0494] S1010, the AF determines whether the bit rate of the UE group meets the requirement based on the information from the NEF.

[0495] For example, if the NEF sends at least one of the aggregate bit rate of the UE group (e.g., the third UE group) or the minimum bit rate of the UE in the UE group (e.g., the third UE group) to the AF. The AF may compare the aggregate bit rate of the UE group (e.g., the third UE group) with the maximum aggregate bit rate threshold of the UE group (the third UE group), or compare the aggregate bit rate of the UE group with the minimum aggregate bit rate threshold of the UE group to obtain a comparison result. The comparison result may include: the aggregate bit rate of the third UE group is greater than the maximum aggregate bit rate threshold of the third UE group, the aggregate bit rate of the third UE group is less than the minimum aggregate bit rate threshold of the first UE group, or the aggregate bit rate of the third UE group is less than or equal to the maximum aggregate bit rate threshold of the third UE group and greater than or equal to the minimum aggregate bit rate threshold of the third UE group.

[0496] If the NEF sends the minimum bit rate of the UE in the third UE group to the AF, the AF may compare the minimum bit rate of the UE in the third UE group with the minimum bit rate threshold of the UE in the third UE group to obtain a comparison result. For example, the comparison result may include: the minimum bit rate of the UE in the third UE group is less than the minimum bit rate threshold of the UE in the third UE group, or the minimum bit rate of the UE in the third UE group is greater than or equal to at least one of the minimum bit rate threshold of the UE in the third UE group.

[0497] Optionally, the AF may also use the comparison result sent by the NEF to determine whether the bit rate of the UE group meets the requirement.

[0498] For example, if the aggregate bit rate of the third UE group is greater than the maximum aggregate bit rate threshold of the third UE group, it is determined that the aggregate bit rate of the third UE group does not meet the requirement. In this case, although the requirements for normal transmission of services of the third UE group can be met, other UEs or services may be affected.

[0499] For another example, if the aggregate bit rate of the third UE group is less than the minimum aggregate bit rate threshold of the third UE group, it is determined that the aggregate bit rate of the third UE group does not meet the requirement. In this case, the minimum requirement for normal transmission of the service of the third UE group may not be met, and the normal transmission of the service data cannot be guaranteed.

[0500] For another example, if the minimum bit rate of the UE in the third UE group is less than the minimum bit rate threshold of the UE in the third UE group, it is determined that the bit rate of the third UE group does not meet the requirement. In this case, the minimum requirement for normal transmission of the service of the third UE group may not be met, and the normal transmission of the service data cannot be guaranteed.

[0501] Of course, if in S1009, the NEF sends an indication message to the AF, the indication message is used to indicate that the AF needs to generate an adjustment strategy, then S1010 can be omitted, and S1011 is directly executed after S1009, and S1011 can be replaced by: the AF generates an adjustment strategy according to the indication message.

[0502] S1011: When the bit rate of the UE group does not meet the requirement, the AF generates an adjustment strategy.

[0503] In some possible implementations, the adjustment strategy may include at least one of the following:

[0504] If the UE service quality flow in the UE group (for example, the third UE group) is a guaranteed bit rate service quality flow, modifying the maximum bit rate value of the guaranteed bit rate service quality flow;

[0505] Adjusting the ARP or priority parameter of the service quality flow of the UE in the UE group (for example, the third UE group);

[0506] The service quality flows of some UEs in the UE group (for example, the third UE group) are released.

[0507] Of course, in other implementations of the present application, the adjustment strategy may also include other bit rate adjustment strategies. After adjustment using the adjustment strategy, it can be achieved that: the UE group aggregate bit rate is less than the maximum bit rate threshold of the UE group and greater than the minimum bit rate threshold of the UE group, or the minimum bit rate of the UE in the UE group is greater than the minimum bit rate threshold of the UE in the UE group.

[0508] When the AF generates an adjustment policy, the AF may send the adjustment policy to the PCF, and the PCF finally executes the adjustment policy.

[0509] Optionally, in each step of method 1000, the expression "third UE group (i.e., third terminal device group)" may also be replaced by: "second UE group (i.e., second terminal device group)". That is, in the embodiment shown in method 1000, the second terminal device group and the third terminal device group are the same terminal device group, and the first UE group is a subset of the second UE group or the third UE group.

[0510] It should also be understood that in method 1000, the description of "identifiers of UEs in a UE group" refers to identifiers corresponding to all UEs in the UE group, that is, a list of UE identifiers. For example, the description of "identifiers of UEs in the third group" refers to identifiers corresponding to all UEs in the third UE group. For example, the description of "identifiers of UEs in the first group" refers to identifiers corresponding to all UEs in the first UE group. For another example, "identifiers of UEs included in an external UE group" refers to identifiers of all UEs included in the external UE group. For another example, "identifiers of UEs included in an internal UE group" refers to identifiers of all UEs included in the internal UE group.

[0511] The method provided in the embodiment of the present application requests the aggregate bit rate information of each application per UE group (per Slice per Application per UE Group) and / or the minimum bit rate information of the UE in the UE group from the NEF through the AF, and the request message includes at least one of the maximum aggregate bit rate threshold of each slice per application per UE group, the threshold of the minimum aggregate bit rate of the UE group, or the minimum bit rate threshold of the UE in the UE group. The NEF aggregates the information fed back by different PCFs, determines the aggregate bit rate information of the UE and / or the minimum bit rate of the UE in the UE group, and compares the obtained aggregate bit rate of the UE group and / or the minimum bit rate of the UE in the UE group with the requirements in the request information of the AF to determine whether the requirements can be met. If not, the AF is notified, and the AF triggers the execution policy adjustment, thereby realizing the monitoring and adjustment of the bit rate at the UE group granularity. It can ensure that the aggregate bit rate of the UE group does not exceed the requirements to avoid affecting other UEs or services, and can also ensure that the aggregate bit rate of the UE group is not lower than the set minimum aggregate bit rate to ensure the minimum requirements for normal transmission of the service, thereby improving communication efficiency.

[0512] It should be understood that the above is only to help those skilled in the art better understand the embodiments of the present application, rather than to limit the scope of the embodiments of the present application. According to the above examples given, those skilled in the art can obviously make various equivalent modifications or changes. For example, some steps in each method of the above method may be unnecessary, or some new steps may be added. Or a combination of any two or any multiple embodiments of the above. Such modifications, changes or combined solutions also fall within the scope of the embodiments of the present application.

[0513] It should also be understood that the division of the methods, situations, categories and embodiments in the embodiments of the present application is only for the convenience of description and should not constitute a special limitation. The features of various methods, categories, situations and embodiments can be combined without contradiction.

[0514] It should also be understood that the various numerical numbers involved in the embodiments of the present application are only for the convenience of description and are not used to limit the scope of the embodiments of the present application. The size of the sequence number of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0515] It should also be understood that the above description of the embodiments of the present application focuses on emphasizing the differences between the various embodiments. The same or similar points that are not mentioned can be referenced to each other. For the sake of brevity, they will not be repeated here.

[0516] In this embodiment, each network element (including the above-mentioned PCF, NEF, AF, NWDAF, UDM, UDR, SMF, UPF, etc.) can be divided into functional modules according to the above method. For example, each function can be divided into functional modules, or two or more functions can be integrated into one processing module. The above-mentioned integrated module can be implemented in the form of hardware. It should be noted that the division of modules in this embodiment is schematic and is only a logical function division. There may be other division methods in actual implementation.

[0517] It should be noted that the relevant contents of each step involved in the above method embodiment can all be referred to the functional description of the corresponding functional module, which will not be repeated here.

[0518] The PCF, NEF, AF, NWDAF, UDM, or UDR, etc. provided in the embodiments of the present application are used to execute the rate control method of any terminal device group within a network slice provided in the above method embodiments, so the same effect as the above method can be achieved. In the case of using an integrated unit, PCF, NEF, AF, NWDAF, UDM, UDR, SMF, or UPF may include a processing module, a storage module, and a communication module. Among them, the processing module can be used to control and manage the actions of the network element. For example, it can be used to support the network element to execute the steps executed by the processing unit. The storage module can be used to support the storage of program codes and data, etc. The communication module can be used to support communication between the network element and other devices.

[0519] Among them, the processing module can be a processor or a controller. It can implement or execute various exemplary logic boxes, modules and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of digital signal processing (DSP) and a microprocessor, and so on. The storage module can be a memory. The communication module can specifically be a device that interacts with other devices, such as a radio frequency circuit, a Wi-Fi chip, etc.

[0520] Fig.11 A schematic block diagram of a communication device provided in an embodiment of the present application is shown, Fig.11 As shown, the communication device 1100 may include: a processing unit 1110 and a communication unit 1120. Optionally, the communication device 1100 may further include a storage unit 1130.

[0521] In some embodiments, the communication device 1100 may correspond to the PCF described in the above methods 600 to 800. It may also be a chip or component applied to the PCF, and each module or unit in the communication device 1100 is respectively used to execute each action or processing performed by the PCF described in the above methods 600 to 800.

[0522] In some possible implementations, the communication unit 1120 is used to: obtain first information, where the first information includes: at least one of an aggregate bit rate of a first terminal device group corresponding to a first application in a first network slice, or a minimum bit rate of a terminal device in a first terminal device group corresponding to the first application in the first network slice;

[0523] The communication unit 1120 is further configured to: receive second information from the data storage network element or the unified data management network element, the second information including: bit rate information;

[0524] The processing unit 1110 is used to: determine an adjustment strategy based on the first information and the bit rate information, if conditions are met, and the adjustment strategy is used to adjust the aggregate bit rate of the first terminal device group or at least one of the minimum bit rates of the terminal devices in the first terminal device group.

[0525] In some possible implementations, the bit rate information includes: at least one of a maximum aggregate bit rate threshold of the first terminal device group, a minimum aggregate bit rate threshold of the first terminal device group, or a minimum bit rate threshold of a terminal device in the first terminal device group;

[0526] Subject to the conditions being met, including:

[0527] The aggregation bit rate of the first terminal device group is greater than the maximum aggregation bit rate threshold of the first terminal device group, the aggregation bit rate of the first terminal device group is less than the minimum aggregation bit rate threshold of the first terminal device group, and if the minimum bit rate of the terminal devices in the first terminal device group is less than the minimum bit rate threshold of the terminal devices in the first terminal device group, at least one of the following is satisfied.

[0528] In some possible implementations, the communication unit 1120 is also used to: receive third information from a network open function network element, the third information includes first indication information, the first indication information is used to indicate: triggering at least one of aggregated bit rate monitoring of the first terminal device group, or minimum bit rate monitoring of the terminal devices in the first terminal device group, the third information also includes: identifiers of all terminal devices included in the first terminal device group or at least one of the identifiers of the first terminal device group, as well as an identifier of the first network slice, and an identifier of the first application; in response to the third information, sending a subscription request to the network analysis function network element, the subscription request is used to obtain the first information, the subscription request includes: identifiers of all terminal devices in the first terminal device group or at least one of the identifiers of the first terminal device group, as well as an identifier of the first network slice, an identifier of the first application, and an analysis type identifier.

[0529] In some possible implementations, the bit rate information includes: the aggregate bit rate of the remaining groups of the second terminal device group corresponding to the first application in the first network slice, the first terminal device group is a subset of the second terminal device group (the second terminal device group includes the first terminal device group), and the policy control function network element is a policy control function network element serving the first terminal device group. The method also includes: the processing unit 1110 is also used to: update the aggregate bit rate of the remaining group according to the aggregate bit rate of the first terminal device group in the first information; when the conditions are met, including: the updated aggregate bit rate of the remaining group is greater than a preset first threshold, or less than a preset second threshold.

[0530] In some possible implementations, the processing unit 1110 is further used to: determine a change value of the aggregate bit rate of the first terminal device group; determine the aggregate bit rate of the remaining group according to the change value, and obtain the updated aggregate bit rate of the remaining group.

[0531] In some possible implementations, the communication unit 1120 is further configured to: send the updated remaining group aggregate bit rate to a data storage network element or a unified data management network element.

[0532] In some possible implementations, the communication unit 1120 is also used to: receive fourth information from a network open function network element, the fourth information includes first indication information, the first indication information indicates: triggering aggregate bit rate monitoring of the first terminal device group, the fourth information also includes: the identification of all terminal devices in the second terminal device group or at least one of the identifications of the second terminal device group, the identification of all terminal devices in the first terminal device group or at least one of the identifications of the first terminal device group, the identification of the first network slice, and the identification of the first application; according to the fourth information, obtain the first information.

[0533] In some possible implementations, the communication unit 1120 is also used to: send a query request to a data storage network element or a unified data management network element, the query request including: the identifiers of all terminal devices in the first terminal device group or at least one of the identifiers of the first terminal device group, the identifier of the first network slice, and the identifier of the first application; or, the query request including: the identifiers of all terminal devices in the second terminal device group or at least one of the identifiers of the second terminal device group, the identifier of the first network slice, and the identifier of the first application, and the second terminal device group includes the first terminal device group; receive second information in response to the query request from the data storage network element or the unified data management network element.

[0534] In some possible implementations, the adjustment strategy includes at least one of the following: if the service quality flow of the terminal device in the first terminal device group is a guaranteed bit rate service quality flow, modifying the maximum bit rate value of the guaranteed bit rate service quality flow; adjusting the allocation maintenance priority or priority parameter of the service quality flow of the terminal device in the first terminal device group; releasing the service quality flow of some terminal devices in the first terminal device group.

[0535] In some embodiments, the communication device 1100 may correspond to the AF described in the above methods 600 to 800, or may be a chip or component applied to the AF, and each module or unit in the communication device 1100 is respectively used to execute each action or processing process performed by the AF described in the above methods 600 to 800.

[0536] In some possible implementations, the communication unit 1120 is used to: send a first parameter to a data storage network element or a unified data management network element, the first parameter including: a maximum aggregation bit rate threshold of a third terminal device group corresponding to a first application in a first network slice, a minimum aggregation bit rate threshold of a third terminal device group, a minimum bit rate threshold of a terminal device in a third terminal device group, or at least one of the aggregation bit rates of the remaining groups of the third terminal device group, the first parameter also includes: an identifier of all terminal devices in the third terminal device group or at least one of an identifier of a third terminal device group, an identifier of the first network slice, and an identifier of the first application; send a first request message to a network open function network element, the first request message including second indication information, an identifier of the first network slice, and an identifier of the first application; the second indication information indicates: triggering a policy control function network element to perform at least one of aggregation bit rate monitoring of the third terminal device group, minimum bit rate monitoring of the terminal devices in the third terminal device group, or aggregation bit rate monitoring of the third terminal device group, the first request message also includes: an identifier of all terminal devices in the third terminal device group or at least one of an identifier of the third terminal device group.

[0537] In some embodiments, the communication device 1100 may correspond to the NEF described in the above methods 600 to 800, or may be a chip or component applied to the NEF, and each module or unit in the communication device 1100 is respectively used to execute each action or processing process performed by the NEF described in the above methods 600 to 700.

[0538] In some possible implementations, the communication unit 1120 is used to: receive a first request message from an application function network element, the first request message including second indication information, the second indication information being used to indicate: triggering a policy control function network element to perform at least one of aggregated bit rate monitoring of a third terminal device group corresponding to the first application in the first network slice, or minimum bit rate monitoring of terminal devices in the third terminal device group, the first request message also including: identifiers of all terminal devices in the third terminal device group or at least one of the identifiers of the third terminal device group, an identifier of the first network slice, and an identifier of the first application;

[0539] The processing unit 1110 is configured to: determine, according to the first request message, a policy control function network element set, where the policy control function network element set includes a plurality of policy control function network elements serving the terminal devices in the third terminal device group;

[0540] The communication unit 1120 is also used to: send third information to each policy control function network element in the policy control function network element set, respectively, the third information includes first indication information, the first indication information is used to indicate: performing aggregate bit rate monitoring of the first terminal device group corresponding to the first application in the first network slice, or performing at least one of the minimum bit rate monitoring of the terminal devices in the first terminal device group, the third information also includes: the identification of all terminal devices in the first terminal device group or at least one of the identification of the first terminal device group, the identification of the terminal device served by the policy control function network element, the identification of the first network slice, the identification of the first application, the first terminal device group and the third terminal device group are the same terminal device group.

[0541] In some embodiments, the communication device 1100 may correspond to the NEF described in the above-mentioned method 900 and method 1000, or may be a chip or component applied to the NEF, and each module or unit in the communication device 1100 is respectively used to execute each action or processing process performed by the above-mentioned method 900 and method 1000 NEF.

[0542] In some possible implementations, the communication unit 1120 is used to: receive a first request message from an application function network element, the first request message includes second indication information, and the second indication information is used to indicate: triggering the policy control function network element to perform at least one of aggregated bit rate monitoring of the third terminal device group corresponding to the first application in the first network slice, or performing minimum bit rate monitoring of the terminal devices in the third terminal device group; the first request message also includes: the identifiers of all terminal devices in the third terminal device group or at least one of the identifiers of the third terminal device group, the identifier of the first network slice, and the identifier of the first application.

[0543] The processing unit 1110 is configured to: determine, according to the first request message, a policy control function network element set, where the policy control function network element set includes a plurality of policy control function network elements serving the terminal devices in the third terminal device group;

[0544] The communication unit 1120 is also used to: send fourth information to each policy control function network element in the policy control function network element set respectively, the fourth information includes first indication information, the first indication information is used to indicate: triggering the aggregate bit rate monitoring of the first terminal device group corresponding to the first application in the first network slice, or at least one of the minimum bit rate monitoring of the terminal devices in the first terminal device group, the fourth information also includes: the identification of all terminal devices in the first terminal device group or at least one of the identifications of the first terminal device group, the identification of all terminal devices in the second terminal device group or at least one of the identifications of the second terminal device group, the identification of the first network slice, the identification of the first application, the terminal devices included in the first terminal device group are terminal devices managed by a policy control function network element, the first terminal device group is a subset of the second terminal device group (or, the second terminal device group includes the first terminal device group), and the second terminal device group and the third terminal device group are the same terminal device group.

[0545] In some possible implementations, the communication unit 1120 is also used to: receive fifth information from each policy control function network element in the policy control function network element set, the fifth information including: the aggregate bit rate of the first terminal device group, or at least one of the minimum bit rate of the terminal devices in the first terminal device group; the processing unit 1110 is also used to: determine, based on the fifth information, the aggregate bit rate of the third terminal device group, or at least one of the minimum bit rate of the terminal devices in the third terminal device group; the communication unit 1120 is also used to: send sixth information to the application function network element, the sixth information including: the aggregate bit rate of the third terminal device group, the minimum bit rate of the terminal devices in the third terminal device group, indication information for indicating that the aggregate bit rate of the third terminal device group is greater than the maximum aggregate bit rate threshold of the third terminal device group, indication information for indicating that the aggregate bit rate of the third terminal device group is less than the minimum aggregate bit rate threshold of the third terminal device group, or indication information for indicating that the minimum bit rate of the terminal devices in the third terminal device group is less than the minimum bit rate threshold of the terminal devices in the third terminal device group.

[0546] In some embodiments, the communication device 1100 may correspond to the UDR or UDM described in the above methods 600 to 800, or may be a chip or component applied to the UDR or UDM, and each module or unit in the communication device 1100 is respectively used to execute each action or processing process performed by the UDR or UDM described in the above methods 600 to 800.

[0547] In some possible implementations, the communication unit 1120 is used to: receive a first parameter from an application function network element, the first parameter including: a maximum aggregation bit rate threshold of a third terminal device group corresponding to the first application in the first network slice, a minimum aggregation bit rate threshold of the third terminal device group, a minimum bit rate threshold of the terminal devices in the third terminal device group, or at least one of the aggregation bit rates of the remaining groups of the third terminal device group, the first parameter also includes: an identifier of the first network slice, an identifier of the first application; the processing unit 1110 is used to: store the first parameter.

[0548] In some possible implementations, the communication unit 1120 is also used to: receive a first query request from a policy control function network element, the first query request is used to query at least one of the maximum aggregation bit rate threshold of the first terminal device group corresponding to the first application in the first network slice, the minimum aggregation bit rate threshold of the first terminal device group, or the minimum bit rate threshold of the terminal devices in the first terminal device group, the first query request includes: the identifiers of all terminal devices in the first terminal device group or at least one of the identifiers of the first terminal device group, the identifier of the first network slice, the identifier of the first application, the first terminal device group and the third terminal device group are the same terminal device group; in response to the first query request, send to the policy control function network element: the maximum aggregation bit rate threshold of the first terminal device group, the minimum aggregation bit rate threshold of the first terminal device group, or at least one of the minimum bit rate thresholds of the terminal devices in the first terminal device group.

[0549] In some possible implementations, the communication unit 1120 is also used to: receive a second query request sent from a policy control function network element, the second query request is used to query the remaining group aggregate bit rate of the second terminal device group corresponding to the first application in the first network slice, or at least one of the minimum bit rate thresholds of the terminal devices in the second terminal device group, the second query request includes: the identifiers of all terminal devices in the second terminal device group or at least one of the identifiers of the second terminal device group, the identifier of the first network slice, the identifier of the first application, the second terminal device group and the third terminal device group are the same terminal device group; in response to the second query request, send to the policy control function network element: the remaining group aggregate bit rate of the second terminal device group, or at least one of the minimum bit rate thresholds of the terminal devices in the second terminal device group; receive the updated remaining group aggregate bit rate sent by the policy control function network element.

[0550] In some embodiments, the communication device 1100 may correspond to the AF described in the above methods 900 and 1000, or may be a chip or component applied to the AF, and each module or unit in the communication device 1100 is respectively used to execute each action or processing process performed by the AF described in the above methods 900 and 1000.

[0551] In some possible implementations, the communication unit 1120 is used to: send seventh information, the seventh information including: the identifiers of all terminal devices of the third terminal device group corresponding to the first application in the first network slice or at least one of the identifiers of the third terminal device group, the identifier of the first network slice, and the identifier of the first application; receive eighth information in response to the seventh information, the eighth information including: the aggregated bit rate of the third terminal device group corresponding to the first application in the first network slice, the minimum bit rate of the terminal devices in the third terminal device group corresponding to the first application in the first network slice, and a value used to indicate that the aggregated bit rate of the third terminal device group is greater than the maximum aggregated bit rate of the third terminal device group At least one of the following information: indication information of a threshold, indication information for indicating that the aggregate bit rate of the third terminal device group is less than the minimum aggregate bit rate threshold of the third terminal device group, or indication information for indicating that the minimum bit rate of the terminal devices in the third terminal device group is less than the minimum bit rate threshold of the terminal devices in the third terminal device group; the processing unit 1110 is used to: according to the eighth information, if the conditions are met, determine an adjustment strategy, the adjustment strategy is used to adjust the aggregate bit rate of the third terminal device group, or at least one of the minimum bit rate of the terminal devices in the third terminal device group; the communication unit 1120 is also used to: send the adjustment strategy to the policy control function network element.

[0552] In some possible implementations, the seventh information also includes second indication information, and the second indication information is used to indicate: triggering the policy control function network element to perform at least one of aggregate bit rate monitoring of the third terminal device group, or minimum bit rate monitoring of the terminal devices in the third terminal device group.

[0553] In some possible implementations, the seventh information further includes: at least one of a maximum aggregate bit rate threshold of the third terminal device group, a minimum aggregate bit rate threshold of the third terminal device group, or a minimum bit rate threshold of a terminal device in the third terminal device group.

[0554] In some possible implementations, when the conditions are met, they include: the aggregate bit rate of the third terminal device group is greater than the maximum aggregate bit rate threshold of the third terminal device group, the aggregate bit rate of the third terminal device group is less than the minimum aggregate bit rate threshold of the third terminal device group, or the minimum bit rate of the terminal devices in the third terminal device group is less than at least one of the minimum bit rate threshold of the terminal devices in the third terminal device group.

[0555] In some possible implementations, the adjustment strategy includes at least one of the following: if the service quality flow of the terminal device in the third terminal device group is a guaranteed bit rate service quality flow, modifying the maximum bit rate value of the guaranteed bit rate service quality flow; adjusting the allocation maintenance priority or priority parameter of the service quality flow of the terminal device in the third terminal device group; releasing the service quality flow of some terminal devices in the third terminal device group.

[0556] In some embodiments, the communication device 1100 may correspond to the PCF described in the above method 1000, or may be a chip or component applied to the PCF, and each module or unit in the communication device 1100 is used to execute each action or processing process performed by the PCF described in the above method 1000.

[0557] In some possible implementations, the communication unit 1120 is used to: receive fourth information from a network open function network element, the fourth information includes first indication information, the first indication information is used to indicate: triggering at least one of the aggregated bit rate monitoring of the first terminal device group corresponding to the first application in the first network slice, or the minimum bit rate monitoring of the terminal devices in the first terminal device group, the fourth information includes: the identification of all terminal devices in the first terminal device group or at least one of the identification of the first terminal device group, the identification of the first network slice, and the identification of the first application, the policy control function network element is a policy control function network element serving the first terminal device group; according to the fourth information, obtaining at least one of the aggregated bit rate of the first terminal device group or the minimum bit rate of the terminal devices in the first terminal device group; sending at least one of the aggregated bit rate of the first terminal device group or the minimum bit rate of the terminal devices in the first terminal device group to the network open function network element.

[0558] In some embodiments, the communication device 1100 may correspond to the NWDAF described in the above methods 600, 700 and 1000. It may also be a chip or component applied to the NWDAF, and each module or unit in the communication device 1100 is used to execute each action or processing performed by the NWDAF described in the above methods 600, 700 and 1000.

[0559] In some possible implementations, the communication unit 1120 is used to: receive request information from a policy control function network element or a network open function network element, the request information including: the identifiers of all terminal devices in the third terminal device group corresponding to the first application in the first network slice or at least one of the identifiers of the third terminal device group, the identifier of the first network slice, the identifier of the first application, and an analysis type identifier, wherein the analysis type identifier is used to indicate to perform data volume and session-related analysis on the terminal device or the terminal device group; the processing unit 1110 is used to: determine, according to the request information, the aggregate bit rate of the third terminal device group, or at least one of the minimum bit rates of the terminal devices in the third terminal device group; the communication unit 1120 is also used to: send ninth information to the policy control function network element or the network open function network element, the ninth information including: the aggregate bit rate of the third terminal device group, or at least one of the minimum bit rates of the terminal devices in the third terminal device group.

[0560] In some possible implementations, the request information also includes: a maximum aggregation bit rate threshold of the third terminal device group, a minimum aggregation bit rate threshold of the third terminal device group, or at least one of a minimum bit rate threshold of the terminal devices in the third terminal device group; the ninth information also includes: indication information for indicating that the aggregation bit rate of the third terminal device group is greater than the maximum aggregation bit rate threshold of the third terminal device group, indication information for indicating that the aggregation bit rate of the third terminal device group is less than the minimum aggregation bit rate threshold of the third terminal device group, or at least one of indication information for indicating that the minimum bit rate of the terminal devices in the third terminal device group is less than the minimum bit rate threshold of the terminal devices in the third terminal device group.

[0561] It should be understood that the specific process of each unit in the communication device 1100 performing the above corresponding steps can be referred to in conjunction with the above Figures 6 to 10 For the sake of brevity, the relevant descriptions of the PCF, NEF, AF, NWDAF, UDM or UDR execution steps described in the various embodiments shown in are not repeated here.

[0562] Optionally, the communication unit 1120 may include a receiving unit (module) and a sending unit (module), which are used to perform the steps of receiving information and sending information by the PCF, NEF, AF, NWDAF, UDM or UDR in the aforementioned method embodiments. The storage unit 1130 is used to store instructions executed by the processing unit 1110 and the communication unit 1120. The processing unit 1110, the communication unit 1120 and the storage unit 1130 are connected in communication, the storage unit 1130 stores instructions, the processing unit 1110 is used to execute the instructions stored in the storage unit, and the communication unit 1120 is used to perform specific signal transmission and reception under the drive of the processing unit 1110.

[0563] It should be understood that the communication unit 1120 may be a transceiver, an input / output interface or an interface circuit, etc., the storage unit may be a memory, and the processing unit 1110 may be implemented by a processor. Fig.12 A schematic structural block diagram of another example of a communication device provided in this application, such as Fig.12 As shown, the communication device 1200 may include a processor 1210, a memory 1220, a transceiver 1230, and a bus system 1240. The various components of the communication device 1200 are coupled together through the bus system 1240, wherein the bus system 1240 may include a power bus, a control bus, and a status signal bus in addition to a data bus. However, for the sake of clarity, Fig.12 In the figure, various buses are labeled as bus system 1240. For convenience of representation, Fig.12 The drawing is only schematic.

[0564] It should also be understood that Fig.12 The communication device 1200 may be a PCF, a NEF, an AF, a NWDAF, a UDM, or a UDR. Alternatively, the PCF, the NEF, the AF, the NWDAF, the UDM, or the UDR may include Fig.12 The communication device 1200 is provided.

[0565] Fig.11 The communication device 1100 or Fig.12 The communication device 1200 can implement the steps performed by the PCF, NEF, AF, NWDAF, UDM or UDR in the embodiments shown in the aforementioned methods 600 to 1000. Similar descriptions can refer to the descriptions in the aforementioned corresponding methods. To avoid repetition, they will not be repeated here.

[0566] The present application also provides a chip system, such as Fig.13 As shown, the chip system includes at least one processor 1310 and at least one interface circuit 1320. The processor 1310 and the interface circuit 1320 can be interconnected via lines. For example, the interface circuit 1320 can be used to receive signals from other devices. For another example, the interface circuit 1320 can be used to send signals to other devices. Exemplarily, the interface circuit 1320 can read instructions stored in the memory and send the instructions to the processor 1310. When the instructions are executed by the processor 1310, the chip system can execute the various steps performed by the PCF, NEF, AF, NWDAF, UDM or UDR in the above embodiments. Of course, the chip system can also include other discrete devices, which are not specifically limited in the embodiments of the present application.

[0567] It should also be understood that the division of units in the above device is only a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. And the units in the device can all be implemented in the form of software calling through processing elements; they can also be all implemented in the form of hardware; some units can also be implemented in the form of software calling through processing elements, and some units can be implemented in the form of hardware. For example, each unit can be a separately established processing element, or it can be integrated in a certain chip of the device. In addition, it can also be stored in the memory in the form of a program, and called and executed by a certain processing element of the device. The processing element here can also be called a processor, which can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each unit above can be implemented by an integrated logic circuit of hardware in the processor element or in the form of software calling through a processing element. In one example, the unit in any of the above devices may be one or more integrated circuits configured to implement the above method, such as one or more application specific integrated circuits (ASIC), or one or more digital signal processors (DSP), or one or more field programmable gate arrays (FPGA), or a combination of at least two of these integrated circuit forms. For another example, when the unit in the device can be implemented in the form of a processing element scheduler, the processing element can be a general-purpose processor, such as a central processing unit (CPU) or other processor that can call a program. For another example, these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0568] The embodiment of the present application also provides a device, which is included in PCF, NEF, AF, NWDAF, UDM or UDR, and the device has the function of implementing PCF, NEF, AF, NWDAF, UDM or UDR in any method of the above embodiments. The function can be implemented by hardware, or the corresponding software can be implemented by hardware. The hardware or software includes at least one module or unit corresponding to the above function. For example, a detection module or unit, a display module or unit, a determination module or unit, and a calculation module or unit, etc.

[0569] An embodiment of the present application also provides a system for rate control of a terminal device group within a network slice, the system comprising: at least one of the PCF, NEF, AF, NWDAF, UDM or UDR provided in the above method embodiments.

[0570] The embodiment of the present application also provides a computer-readable storage medium for storing computer program code, the computer program including instructions for executing any one of the rate control methods for a terminal device group within a network slice provided in the embodiment of the present application. The readable medium may be a read-only memory (ROM) or a random access memory (RAM), which is not limited in the embodiment of the present application.

[0571] The present application also provides a computer program product, which includes instructions. When the instructions are executed, the PCF, NEF, AF, NWDAF, UDM or UDR performs corresponding operations corresponding to any of the above methods.

[0572] The embodiment of the present application further provides a chip located in a communication device, the chip comprising: a processing unit and a communication unit, the processing unit, for example, may be a processor, the communication unit, for example, may be an input / output interface, a pin or a circuit, etc. The processing unit may execute computer instructions to enable the communication device to execute any of the rate control methods for a terminal device group within a network slice provided in the embodiment of the present application.

[0573] Optionally, the computer instructions are stored in a storage unit.

[0574] Optionally, the storage unit is a storage unit within the chip, such as a register, a cache, etc. The storage unit may also be a storage unit within the terminal that is located outside the chip, such as a ROM or other types of static storage devices that can store static information and instructions, random RAM, etc. Among them, the processor mentioned in any of the above may be a CPU, a microprocessor, an ASIC, or one or more integrated circuits for controlling the execution of the program of the rate control method of the terminal device group within the above network slice. The processing unit and the storage unit may be decoupled and respectively arranged on different physical devices, and connected by wire or wireless means to implement the respective functions of the processing unit and the storage unit, so as to support the system chip to implement the various functions in the above embodiments. Alternatively, the processing unit and the memory may also be coupled on the same device.

[0575] Among them, the PCF, NEF, AF, NWDAF, UDM, UDR, computer-readable storage medium, computer program product or chip provided in this embodiment are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods provided above, and will not be repeated here.

[0576] It is understood that the memory in the embodiment 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 ROM, a programmable read-only memory (programmable ROM, PROM), an erasable programmable read-only memory (erasable PROM, EPROM), an electrically erasable programmable read-only memory (electrically EPROM, EEPROM) or a flash memory. The volatile memory can be a RAM, which is used as an external cache. There are many different types of RAM, such as static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (doubledata rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (direct rambus RAM, DRRAM).

[0577] Various objects such as various messages / information / equipment / network elements / systems / devices / actions / operations / processes / concepts that may appear in this application are named. It can be understood that these specific names do not constitute a limitation on the relevant objects. The names assigned may change with factors such as scenarios, contexts or usage habits. The understanding of the technical meaning of the technical terms in this application should be mainly determined from the functions and technical effects embodied / executed in the technical scheme.

[0578] In the various embodiments of the present application, unless otherwise specified or provided in a logical conflict, the terms and / or descriptions between the different embodiments are consistent and may be referenced to each other, and the technical features in the different embodiments may be combined to form new embodiments according to their inherent logical relationships.

[0579] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or 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 can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0580] The method in the embodiment of the present application 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 programs or instructions. When the computer program or instruction is loaded and executed on a computer, the process or function described in the embodiment of the present application is executed in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program or instruction can be stored in a computer-readable storage medium or transmitted via the computer-readable storage medium. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server that integrates one or more available media.

[0581] 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.

[0582] 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.

[0583] 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.

[0584] 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, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a readable storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned readable storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard drives, ROM, RAM, magnetic disks, or optical disks.

[0585] 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 method for controlling the rate of a terminal device group in a network slice, characterized in that: The method comprises: The policy control function network element obtains first information, where the first information includes: at least one of an aggregate bit rate of a first terminal device group corresponding to a first application in a first network slice, or a minimum bit rate of a terminal device in a first terminal device group corresponding to the first application in the first network slice; The policy control function network element receives second information from the data storage network element or the unified data management network element, where the second information includes: bit rate information; The policy control function network element determines an adjustment strategy based on the first information and the bit rate information if conditions are met, and the adjustment strategy is used to adjust the aggregate bit rate of the first terminal device group or at least one of the minimum bit rates of the terminal devices in the first terminal device group.

2. The method according to claim 1, characterized in that The bit rate information includes: at least one of a maximum aggregate bit rate threshold of the first terminal device group, a minimum aggregate bit rate threshold of the first terminal device group, or a minimum bit rate threshold of a terminal device in the first terminal device group; The above mentioned conditions, if met, include: At least one of the following conditions is satisfied: the aggregate bit rate of the first terminal device group is greater than the maximum aggregate bit rate threshold of the first terminal device group, the aggregate bit rate of the first terminal device group is less than the minimum aggregate bit rate threshold of the first terminal device group, or the minimum bit rate of the terminal devices in the first terminal device group is less than the minimum bit rate threshold of the terminal devices in the first terminal device group.

3. The method according to claim 1 or 2, characterized in that: The method further comprises: The policy control function network element receives third information from the network open function network element, where the third information includes first indication information, where the first indication information is used to indicate: triggering at least one of aggregate bit rate monitoring of the first terminal device group or minimum bit rate monitoring of terminal devices in the first terminal device group, and the third information further includes: identifiers of all terminal devices in the first terminal device group or at least one of the identifiers of the first terminal device group, an identifier of the first network slice, and an identifier of the first application; In response to the third information, the policy control function network element sends a subscription request to the network analysis function network element, and the subscription request is used to obtain the first information, and the subscription request includes: the identifiers of all terminal devices in the first terminal device group or at least one of the identifiers of the first terminal device group, the identifier of the first network slice, the identifier of the first application, and the analysis type identifier.

4. The method according to claim 1, characterized in that: The bit rate information includes: a remaining group aggregate bit rate of a second terminal device group corresponding to the first application in the first network slice, the second terminal device group includes the first terminal device group, the policy control function network element is a policy control function network element serving the first terminal device group, and the method further includes: The policy control function network element updates the aggregate bit rate of the remaining groups according to the aggregate bit rate of the first terminal device group in the first information; The above mentioned conditions, if met, include: The updated remaining group aggregate bit rate is greater than a preset first threshold, or less than a preset second threshold.

5. The method according to claim 4, characterized in that The policy control function network element updates the aggregate bit rate of the remaining groups according to the aggregate bit rate of the first terminal device group in the first information, including: The policy control function network element determines a change value of the aggregated bit rate of the first terminal device group; The policy control function network element determines the updated remaining group aggregate bit rate according to the change value.

6. The method according to claim 4 or 5, characterized in that: The method further comprises: The policy control function network element sends the updated remaining group aggregate bit rate to the data storage network element or the unified data management network element.

7. The method according to any one of claims 4 to 6, characterized in that The method further comprises: The policy control function network element receives fourth information from the network open function network element, the fourth information includes first indication information, the first indication information indicates: triggering at least one of the aggregated bit rate monitoring of the first terminal device group or the minimum bit rate monitoring of the terminal devices in the first terminal device group, the fourth information also includes: the identifiers of all terminal devices in the second terminal device group or at least one of the identifiers of the second terminal device group, the identifiers of all terminal devices in the first terminal device group or at least one of the identifiers of the first terminal device group, the identifier of the first network slice, and the identifier of the first application; According to the fourth information, the policy control function network element obtains the first information.

8. The method according to any one of claims 1 to 7, characterized in that The policy control function network element receives the second information from the data storage network element, including: The policy control function network element sends a query request to the data storage network element or the unified data management network element; The query request includes: the identifiers of all terminal devices in the first terminal device group or at least one of the identifiers of the first terminal device group, the identifier of the first network slice, and the identifier of the first application; or The query request includes: at least one of the identifiers of all terminal devices in the second terminal device group or the identifier of the second terminal device group, the identifier of the first network slice, and the identifier of the first application, wherein the second terminal device group includes the first terminal device group; The policy control function network element receives the second information in response to the query request from the data storage network element or the unified data management network element.

9. The method according to any one of claims 1 to 8, characterized in that The adjustment strategy includes at least one of the following: If the quality of service flow of the terminal device in the first terminal device group is a guaranteed bit rate quality of service flow, modifying the maximum bit rate value of the guaranteed bit rate quality of service flow; Adjusting the allocation maintenance priority or priority parameter of the quality of service flow of the terminal devices in the first terminal device group; The quality of service flows of some terminal devices in the first terminal device group are released.

10. A method for controlling the rate of a terminal device group in a network slice, characterized in that: The method comprises: The application function network element sends a first parameter to the data storage network element or the unified data management network element, where the first parameter includes: a maximum aggregation bit rate threshold of a third terminal device group corresponding to the first application in the first network slice, a minimum aggregation bit rate threshold of the third terminal device group, a minimum bit rate threshold of a terminal device in the third terminal device group, or at least one of the aggregation bit rates of the remaining groups of the third terminal device group, and the first parameter also includes: an identifier of all terminal devices in the third terminal device group or at least one of an identifier of the third terminal device group, an identifier of the first network slice, and an identifier of the first application; The application function network element sends a first request message to the network open function network element, where the first request message includes second indication information, an identifier of the first network slice, and an identifier of the first application; Among them, the second indication information indicates: triggering at least one of the aggregate bit rate monitoring of the third terminal device group, or the minimum bit rate monitoring of the terminal devices in the third terminal device group, and the first request message also includes: the identification of all terminal devices in the third terminal device group or at least one of the identifications of the third terminal device group.

11. A method for controlling the rate of a terminal device group in a network slice, characterized in that: The method comprises: The network open function network element receives a first request message from an application function network element, where the first request message includes second indication information, where the second indication information is used to indicate: triggering at least one of aggregated bit rate monitoring of a third terminal device group corresponding to a first application in a first network slice, or minimum bit rate monitoring of terminal devices in the third terminal device group, and the first request message also includes: identification of all terminal devices in the third terminal device group or at least one of identification of the third terminal device group, an identification of the first network slice, and an identification of the first application; The network open function network element determines, according to the first request message, a policy control function network element set, where the policy control function network element set includes a plurality of policy control function network elements serving the terminal devices in the third terminal device group; The network open function network element sends third information to each policy control function network element in the policy control function network element set respectively, and the third information includes first indication information, and the first indication information is used to indicate: triggering at least one of the aggregated bit rate monitoring of the first terminal device group corresponding to the first application in the first network slice, or the minimum bit rate monitoring of the terminal devices in the first terminal device group, and the third information also includes: the identifiers of all terminal devices in the first terminal device group or at least one of the identifiers of the first terminal device group, the identifier of the terminal device served by the policy control function network element, the identifier of the first network slice, and the identifier of the first application, wherein the first terminal device group and the third terminal device group are the same terminal device group.

12. A method for controlling the rate of a terminal device group in a network slice, characterized in that: The method comprises: The network open function network element receives a first request message from an application function network element, where the first request message includes second indication information, where the second indication information is used to indicate: triggering at least one of aggregated bit rate monitoring of a third terminal device group corresponding to a first application in a first network slice, or minimum bit rate monitoring of terminal devices in the third terminal device group; the first request message also includes: identification of all terminal devices in the third terminal device group or at least one of the identification of the third terminal device group, an identification of the first network slice, and an identification of the first application; The network open function network element determines, according to the first request message, a policy control function network element set, where the policy control function network element set includes a plurality of policy control function network elements serving the terminal devices in the third terminal device group; The network open function network element sends fourth information to each policy control function network element in the policy control function network element set respectively, and the fourth information includes first indication information, and the first indication information is used to indicate: triggering at least one of the aggregated bit rate monitoring of the first terminal device group corresponding to the first application in the first network slice, or the minimum bit rate monitoring of the terminal devices in the first terminal device group, and the fourth information also includes: the identification of all terminal devices in the first terminal device group or at least one of the identifications of the first terminal device group, the identification of all terminal devices in the second terminal device group or at least one of the identifications of the second terminal device group, the identification of the first network slice, and the identification of the first application, wherein the terminal devices included in the first terminal device group are terminal devices managed by a policy control function network element, the second terminal device group includes the first terminal device group, and the second terminal device group and the third terminal device group are the same terminal device group.

13. The method according to claim 12, characterized in that The method further comprises: The network open function network element receives fifth information from each policy control function network element in the policy control function network element set, wherein the fifth information includes: an aggregate bit rate of the first terminal device group, or at least one of a minimum bit rate of a terminal device in the first terminal device group; The network open function network element determines, according to the fifth information, at least one of an aggregate bit rate of the third terminal device group or a minimum bit rate of the terminal devices in the third terminal device group; The network open function network element sends sixth information to the application function network element, and the sixth information includes: the aggregated bit rate of the third terminal device group, the minimum bit rate of the terminal devices in the third terminal device group, indication information used to indicate that the aggregated bit rate of the third terminal device group is greater than the maximum aggregated bit rate threshold of the third terminal device group, indication information used to indicate that the aggregated bit rate of the third terminal device group is less than the minimum aggregated bit rate threshold of the third terminal device group, or at least one of indication information used to indicate that the minimum bit rate of the terminal devices in the third terminal device group is less than the minimum bit rate threshold of the terminal devices in the third terminal device group.

14. A method for controlling the rate of a terminal device group in a network slice, characterized in that: The method comprises: The data storage network element or the unified data management network element receives a first parameter from the application function network element, wherein the first parameter includes: a maximum aggregation bit rate threshold of a third terminal device group corresponding to the first application in the first network slice, a minimum aggregation bit rate threshold of the third terminal device group, a minimum bit rate threshold of a terminal device in the third terminal device group, or at least one of the aggregation bit rates of the remaining groups of the third terminal device group, and the first parameter also includes: an identifier of all terminal devices in the third terminal device group or at least one of an identifier of the third terminal device group, an identifier of the first network slice, and an identifier of the first application; The data storage network element or the unified data management network element stores the first parameter.

15. The method according to claim 14, characterized in that The method further comprises: The data storage network element or the unified data management network element receives a first query request from a policy control function network element, where the first query request is used to query at least one of a maximum aggregation bit rate threshold of a first terminal device group corresponding to a first application in a first network slice, a minimum aggregation bit rate threshold of the first terminal device group, or a minimum bit rate threshold of a terminal device in the first terminal device group, and the first query request includes: identifiers of all terminal devices in the first terminal device group or at least one of the identifiers of the first terminal device group, an identifier of the first network slice, and an identifier of the first application, wherein the first terminal device group and the third terminal device group are the same terminal device group; In response to the first query request, the data storage network element or the unified data management network element sends to the policy control function network element: at least one of the maximum aggregation bit rate threshold of the first terminal device group, the minimum aggregation bit rate threshold of the first terminal device group, or the minimum bit rate threshold of the terminal devices in the first terminal device group.

16. The method according to claim 14 or 15, characterized in that The method further comprises: The data storage network element or the unified data management network element receives a second query request sent from a policy control function network element, where the second query request is used to query at least one of the remaining group aggregate bit rate of the second terminal device group corresponding to the first application in the first network slice, or the minimum bit rate threshold of the terminal devices in the second terminal device group, and the second query request includes: the identifiers of all terminal devices in the second terminal device group or at least one of the identifiers of the second terminal device group, the identifier of the first network slice, and the identifier of the first application, wherein the second terminal device group and the third terminal device group are the same terminal device group; In response to the second query request, the data storage network element or the unified data management network element sends at least one of the remaining group aggregate bit rate of the second terminal device group or the minimum bit rate threshold of the terminal devices in the second terminal device group to the policy control function network element; The data storage network element or the unified data management network element receives the updated remaining group aggregate bit rate sent by the policy control function network element.

17. A method for controlling the rate of a terminal device group in a network slice, characterized in that: The method comprises: The application function network element sends seventh information, where the seventh information includes: identifiers of all terminal devices in the third terminal device group corresponding to the first application in the first network slice or at least one of the identifiers of the third terminal device group, the identifier of the first network slice, and the identifier of the first application; The application function network element receives eighth information in response to the seventh information, the eighth information including: an aggregated bit rate of a third terminal device group corresponding to the first application in the first network slice, a minimum bit rate of terminal devices in the third terminal device group corresponding to the first application in the first network slice, indication information for indicating that the aggregated bit rate of the third terminal device group is greater than a maximum aggregated bit rate threshold of the third terminal device group, indication information for indicating that the aggregated bit rate of the third terminal device group is less than a minimum aggregated bit rate threshold of the third terminal device group, or at least one of indication information for indicating that the minimum bit rate of the terminal devices in the third terminal device group is less than a minimum bit rate threshold of the terminal devices in the third terminal device group; The application function network element determines, according to the eighth information, an adjustment strategy when a condition is met, where the adjustment strategy is used to adjust at least one of the aggregate bit rate of the third terminal device group or the minimum bit rate of the terminal devices in the third terminal device group; The application function network element sends the adjustment policy to the policy control function network element.

18. The method according to claim 17, characterized in that The seventh information also includes second indication information, where the second indication information is used to indicate: triggering at least one of aggregate bit rate monitoring of the third terminal device group or minimum bit rate monitoring of the terminal devices in the third terminal device group.

19. The method according to claim 17 or 18, characterized in that The seventh information further includes: at least one of a maximum aggregate bit rate threshold of the third terminal device group, a minimum aggregate bit rate threshold of the third terminal device group, or a minimum bit rate threshold of a terminal device in the third terminal device group.

20. The method according to any one of claims 17 to 19, characterized in that The above mentioned conditions, if met, include: It satisfies at least one of the following conditions: the aggregate bit rate of the third terminal device group is greater than the maximum aggregate bit rate threshold of the third terminal device group, the aggregate bit rate of the third terminal device group is less than the minimum aggregate bit rate threshold of the third terminal device group, or the minimum bit rate of the terminal devices in the third terminal device group is less than the minimum bit rate threshold of the terminal devices in the third terminal device group.

21. The method according to any one of claims 17 to 20, characterized in that The adjustment strategy includes at least one of the following: If the quality of service flow of the terminal device in the third terminal device group is a guaranteed bit rate quality of service flow, modifying the maximum bit rate value of the guaranteed bit rate quality of service flow; Adjusting the allocation maintenance priority or priority parameter of the quality of service flow of the terminal devices in the third terminal device group; The quality of service flows of some terminal devices in the third terminal device group are released.

22. A method for controlling the rate of a terminal device group in a network slice, characterized in that: The method comprises: The policy control function network element receives fourth information from the network open function network element, where the fourth information includes first indication information, where the first indication information is used to indicate: triggering at least one of aggregate bit rate monitoring of a first terminal device group corresponding to a first application in a first network slice, or minimum bit rate monitoring of terminal devices in the first terminal device group, and the fourth information includes: identifiers of all terminal devices in the first terminal device group or at least one of the identifiers of the first terminal device group, an identifier of the first network slice, and an identifier of the first application, and the policy control function network element is a policy control function network element serving the first terminal device group; According to the fourth information, the policy control function network element obtains at least one of the aggregate bit rate of the first terminal device group or the minimum bit rate of the terminal devices in the first terminal device group; The policy control function network element sends at least one of the aggregate bit rate of the first terminal device group or the minimum bit rate of the terminal devices in the first terminal device group to the network open function network element.

23. A method for controlling the rate of a terminal device group in a network slice, characterized in that: The method comprises: The network analysis function network element receives request information from the policy control function network element or the network open function network element, wherein the request information includes: the identifiers of all terminal devices in the third terminal device group corresponding to the first application in the first network slice or at least one of the identifiers of the third terminal device group, the identifier of the first network slice, the identifier of the first application, and the analysis type identifier; The network analysis function network element determines, according to the request information, at least one of an aggregate bit rate of the third terminal device group or a minimum bit rate of the terminal devices in the third terminal device group; The network analysis function network element sends ninth information to the policy control function network element or the network open function network element, and the ninth information includes: the aggregate bit rate of the third terminal device group, or at least one of the minimum bit rates of the terminal devices in the third terminal device group.

24. The method according to claim 23, characterized in that The request information also includes: at least one of the maximum aggregation bit rate threshold of the third terminal device group, the minimum aggregation bit rate threshold of the third terminal device group, or the minimum bit rate threshold of the terminal devices in the third terminal device group; the ninth information also includes: indication information for indicating that the aggregation bit rate of the third terminal device group is greater than the maximum aggregation bit rate threshold of the third terminal device group, indication information for indicating that the aggregation bit rate of the third terminal device group is less than the minimum aggregation bit rate threshold of the third terminal device group, or at least one of the indication information for indicating that the minimum bit rate of the terminal devices in the third terminal device group is less than the minimum bit rate threshold of the terminal devices in the third terminal device group.

25. A communication device, characterized in that: Comprising: a unit for performing: each step of the method as claimed in any one of claims 1 to 9, or a unit for each step of the method as claimed in claim 10, or a unit for each step of the method as claimed in claim 11, or a unit for each step of the method as claimed in claim 12 or 13, or a unit for each step of the method as claimed in any one of claims 14 to 16, or a unit for each step of the method as claimed in any one of claims 17 to 21, or a unit for each step of the method as claimed in claim 22, or a unit for each step of the method as claimed in claim 23 or 24.

26. A communication device, characterized in that: The method comprises at least one processor and an interface circuit, wherein the at least one processor is used to execute: the method as claimed in any one of claims 1 to 9, or the method as claimed in claim 10, or the method as claimed in claim 11, or the method as claimed in claim 12 or 13, or the method as claimed in any one of claims 14 to 16, or the method as claimed in any one of claims 17 to 21, or the method as claimed in claim 22, or the method as claimed in claim 23 or 24.

27. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program or instructions, and when the computer reads and executes the computer program or instructions, the computer executes: the method as claimed in any one of claims 1 to 9, or the method as claimed in claim 10, or the method as claimed in claim 11, or the method as claimed in claim 12 or 13, or the method as claimed in any one of claims 14 to 16, or the method as claimed in any one of claims 17 to 21, or the method as claimed in claim 22, or the method as claimed in claim 23 or 24.

28. A chip, characterized in that: include: A processor, configured to execute a computer program or instruction in a memory so that a communication device equipped with the chip performs: a method as claimed in any one of claims 1 to 9, or a method as claimed in claim 10, or a method as claimed in claim 11, or a method as claimed in claim 12 or 13, or a method as claimed in any one of claims 14 to 16, or a method as claimed in any one of claims 17 to 21, or a method as claimed in claim 22, or a method as claimed in claim 23 or 24.

Images