Communication method and device

Abstract

The embodiment of the invention discloses a communication method and device, and the method comprises the steps: receiving a first request from a first network element, the first request is used for requesting network evaluation, the first request comprises a quality of service (QoS) strategy and a target region, and based on the first request, obtaining the traffic statistic data and user data of a plurality of terminal devices in the target region; and determining a network evaluation parameter of each terminal device according to the traffic statistic data, the user data and a QoS strategy issued for each terminal device in the plurality of terminal devices. By determining the network evaluation parameters, the network use conditions of the terminal devices using different QoS strategies are evaluated in advance before the high-priority QoS strategy is issued, so that mutual influence between the terminal devices using different QoS strategies is avoided, and the user experience is improved. Moreover, the network use condition is evaluated through the traffic statistic data and the user data, so that the calculation complexity can be reduced, and the estimation accuracy can be improved.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0002] With the penetration rate of 5G technology reaching its peak, revenue growth from homogenized data services has begun to decline. Operators are seeking new growth by providing differentiated, tiered user experiences. 5G Quality of Service (QoS) is a crucial means of achieving this tiered user experience. For example, a high-priority QoS policy can be issued to users currently broadcasting live to ensure uninterrupted streaming, while a low-priority QoS policy can be issued to other users, resulting in a superior experience for the 5G user compared to other users.

[0003] However, the factors influencing the effectiveness of QoS policies are highly complex, including channel quality and service rates for the protected user and other users in the same cell. QoS policies among different users within the same cell can also influence each other. Therefore, it is difficult to assess the impact of issuing 5G QoS-based experience packages on the network. For example, high-priority QoS policies issued to protected users may affect the experience of other users in the cell. Determining the globally optimal QoS policy is also challenging; for instance, given limited cell resources, how can the most reasonable QoS policy be issued to each user to achieve the globally optimal quality of experience (QoE)? Summary of the Invention

[0004] This application provides a communication method and apparatus that can avoid mutual interference between terminal devices using different QoS policies, thereby improving the user experience.

[0005] In a first aspect, embodiments of this application provide a communication method that can be applied to the network side, such as a network data analytics function (NWDAF) network element or a communication module within an NWDAF network element, or a circuit or chip responsible for communication functions within an NWDAF network element (such as a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip containing a modem core, or a system-in-package (SIP) chip). Taking the application of this method to an NWDAF network element as an example, the method includes:

[0006] The system receives a first request from a first network element, which requests network evaluation. The first request includes a Quality of Service (QoS) policy and a target area. The first network element is a network element responsible for network function operation. Based on the first request, the system obtains call statistics data and user data from multiple terminal devices within the target area. According to the call statistics data, the user data, and the QoS policy issued to each of the multiple terminal devices, the system determines network evaluation parameters for each terminal device. The network evaluation parameters are used to evaluate the network usage of terminal devices using different QoS policies.

[0007] QoS policies can include first-priority QoS policies and second-priority QoS policies. The first-priority QoS policy guarantees a higher quality of service (QoS) for the terminal device than the second-priority QoS policy. Within a target area, a first-priority QoS policy can be issued to a subset of terminal devices, while a second-priority QoS policy can be issued to the remainder. Then, by acquiring call statistics and user data from multiple terminal devices within the target area, network evaluation parameters for each terminal device are determined. This allows for an assessment of network usage for terminal devices using different QoS policies before issuing higher-priority QoS policies, preventing mutual interference between devices using different QoS policies and improving user experience. Alternatively, the total number of users eligible for QoS policies within a certain area can be assessed to avoid over-issuance of QoS policies, which could negatively impact user experience. Furthermore, assessing network usage using call statistics and user data reduces computational complexity and improves prediction accuracy.

[0008] In one possible design, the first request further includes QoS policy distribution rules. Based on these rules, a QoS policy is determined for each terminal device. Determining the QoS policy for each terminal device through these rules ensures that different QoS policies are distributed to different devices. This allows for advance assessment of network usage by terminal devices using different QoS policies, preventing mutual interference between them and improving user experience. Alternatively, the total number of users eligible for QoS policy distribution within a certain area can be assessed to avoid over-distribution of QoS policies, which could negatively impact user experience.

[0009] In one possible design, the first request further includes the number of users to whom QoS policies are issued. The different QoS policies include a first-priority QoS policy and a second-priority QoS policy. Based on the number of users to whom QoS policies are issued, a first number of terminal devices using the first-priority QoS policy is determined. Based on the total number of terminal devices and the first number, a second number of terminal devices using the second-priority QoS policy is determined. By determining the number of users of different user types (terminal devices using different QoS policies) and issuing QoS policies, different numbers of user types in real-world application scenarios can be simulated. This allows for advance assessment of network usage of terminal devices using different QoS policies, avoiding mutual interference between terminal devices using different QoS policies and improving user experience. Alternatively, it can assess the total number of users within a certain area who can receive QoS policies, preventing excessive issuance of QoS policies and impacting user experience.

[0010] In one possible design, a second request is sent to a second network element, the second request including the target area, the second request being used to request the call statistics data within the target area, the second network element being a network element responsible for operation, management, and maintenance; the call statistics data within the target area is received from the second network element. By obtaining the call statistics data within the target area, the network evaluation parameters for each terminal device can be determined, which can reduce computational complexity and improve the accuracy of the prediction.

[0011] In one possible design, the second request includes call statistics indicators corresponding to the requested call statistics data. These call statistics indicators include at least one of the following: the number of times the Reference Received Power (RSRP) measurement on the Physical Uplink Shared Channel (PUSCH) falls within different intervals; the number of times the Signal-to-Noise Ratio (SINR) measurement on the PUSCH falls within different intervals; the distribution of the user's spectral efficiency on the PUSCH falls within different intervals; the number of times the RSRP measurement on the Physical Downlink Shared Channel (PDSCH) falls within different intervals; the number of times the SINR measurement on the PDSCH falls within different intervals; or the distribution of the user's spectral efficiency on the PDSCH falls within different intervals. The call statistics indicators carried in the second request instruct the collection of call statistics data corresponding to those indicators.

[0012] In one possible design, the second request further includes at least one of the following: a collection period or a statistical period, wherein the collection period indicates the time interval for collecting the call statistics data, and the statistical period indicates the time interval for statistically analyzing the call statistics data. The collection period carried in the second request indicates that call statistics data is collected according to the collection period, and the statistical period carried in the second request indicates that the collected call statistics data is statistically analyzed according to the statistical period.

[0013] In one possible design, a third request is sent, including the target area, to request user data within the target area; the user data within the target area is then received. By acquiring user data within the target area, network evaluation parameters for each terminal device can be determined, reducing computational complexity and improving prediction accuracy.

[0014] In one possible design, channel metrics for each terminal device are determined based on the call statistics data, and a service model for each terminal device is determined based on the user data. Network evaluation parameters for each terminal device are then determined based on the channel metrics, service model, and QoS policies issued to each terminal device. By converting call statistics data into channel metrics (e.g., signal-to-noise ratio, power control resource blocks, maximum pairing layer, modulation and coding scheme), and user data into service models (representing the type of application used by the terminal device), and determining network evaluation parameters for each terminal device based on the channel metrics and service models, the network usage of terminal devices using different QoS policies can be evaluated in advance before issuing high-priority QoS policies. This avoids mutual interference between terminal devices using different QoS policies and improves the user experience.

[0015] In one possible design, the value of the call statistics indicator for each terminal device is determined based on the call statistics data; and the value of the call statistics indicator is converted into the channel indicator based on the mapping relationship between the call statistics indicator value and the channel indicator.

[0016] In one possible design, based on the call statistics data, the number of times the call statistics index of each terminal device falls within each interval is determined; based on the number of times the call statistics index falls within each interval, the probability of the call statistics index of each terminal device falling within each interval is determined; based on the probability of the call statistics index falling within each interval, the value of the call statistics index of each terminal device is determined.

[0017] In one possible design, the channel metrics, service model, and QoS policy issued to each terminal device are input into a simulation model to determine the network evaluation parameters for each terminal device. By inputting the channel metrics and service model into the simulation model to determine the network evaluation parameters for each terminal device, the network usage of terminal devices using different QoS policies can be evaluated in advance before issuing high-priority QoS policies, avoiding mutual interference between terminal devices using different QoS policies and improving the user experience.

[0018] In one possible design, an evaluation result is sent to the first network element. This evaluation result includes network usage information of terminal devices using different QoS policies. By informing the first network element of the network usage information of terminal devices using different QoS policies, QoS policies can be issued to terminal devices based on network usage information in practical application scenarios.

[0019] In one possible design, the network evaluation parameters include at least one of the following: throughput, latency, or packet loss rate.

[0020] Secondly, embodiments of this application provide a communication method that can be applied to the network side, such as a first network element or a component (e.g., a circuit, chip, or chip system) within the first network element. Taking the application of this method to a first network element as an example, the method includes:

[0021] A first request is sent to the network data analysis function network element. The first request is used to request network evaluation. The first request includes a Quality of Service (QoS) policy and a target area. The target area is used to indicate the acquisition of call statistics data and user data of multiple terminal devices. The QoS policy, the call statistics data, and the user data are used to determine the network evaluation parameters of each terminal device. The network evaluation parameters are used to evaluate the network usage of terminal devices using different QoS policies.

[0022] By requesting network data analysis functions from network elements to determine network evaluation parameters for each terminal device, the network usage of terminal devices using different QoS policies can be assessed in advance before issuing high-priority QoS policies. This avoids mutual interference between terminal devices using different QoS policies and improves user experience. Alternatively, the total number of users eligible for QoS policies within a certain area can be assessed to avoid over-issuance of QoS policies, which could negatively impact user experience. Furthermore, assessing network usage using call statistics and user data reduces computational complexity and improves prediction accuracy.

[0023] In one possible design, evaluation results are received from the network data analysis function network element. These results include network usage information for terminal devices using different QoS policies. Knowing the network usage information of terminal devices using different QoS policies allows for the issuance of QoS policies to terminal devices in practical application scenarios.

[0024] In one possible design, the network evaluation parameters include at least one of the following: throughput, latency, or packet loss rate.

[0025] Thirdly, embodiments of this application provide a communication method that can be applied to the network side, such as an NWDAF network element or a component (e.g., a circuit, chip, or chip system) within the NWDAF network element. Taking the application of this method to an NWDAF network element as an example, the method includes:

[0026] Acquire user data and channel indicator data from multiple terminal devices within the cell; determine the QoS policy for each of the multiple terminal devices based on the user data and the channel indicator data.

[0027] By acquiring user data and channel indicator data from multiple terminal devices within the cell, the QoS policy for each terminal device is determined. This allows for the selection of the optimal QoS policy for each terminal device when network resources are limited, ensuring a good user experience and preventing interference with other terminal devices.

[0028] In one possible design, a first request is sent to a first network element, which is responsible for operation, management, and maintenance of the channel indicator data. The channel indicator data is then received from the first network element. By obtaining the channel indicator data through management plane reporting, the QoS policy for each terminal device is determined. This allows for the selection and distribution of the optimal QoS policy to the terminal devices when network resources are limited, ensuring a good user experience and avoiding interference with other terminal devices.

[0029] In one possible design, the first request carries a first reporting method, which is management plane reporting. By carrying management plane reporting in the first request, it indicates that the channel indicator data should be reported using the management plane reporting method.

[0030] In one possible design, the first request further includes requested channel metrics, which include at least one of the following: scheduling signal-to-noise ratio (SINR), rank (RANK), number of power control resource blocks (RBs), maximum number of pairing layers, modulation and coding scheme (MCS), spectral efficiency, initial bit error rate (BER), or residual bit error rate (BER). The channel metrics carried in the first request indicate the need to collect the corresponding channel metric data.

[0031] In one possible design, the first request may further include at least one of the following: data reporting method, quantization level, reporting cycle, collection range, or quantization method. The data reporting method, quantization level, reporting cycle, collection range, or quantization method carried in the first request indicate whether the collected data should be processed or reported.

[0032] In one possible design, a second request is sent to a first network element, which is responsible for operation, management, and maintenance, to request the reporting of the channel indicator data via the user plane. A third request is sent to a second network element, which is responsible for session management, and the third network element is responsible for user plane data forwarding and reception. The channel indicator data is then received from the third network element. By obtaining the channel indicator data through user plane reporting, the QoS policy for each terminal device is determined. This allows for the selection of the optimal QoS policy for terminal devices under limited network resources, ensuring a good user experience and avoiding interference with other terminal devices.

[0033] In one possible design, the second request carries a second reporting method, which is user plane reporting. By carrying management plane reporting in the second request, it indicates that channel indicator data should be reported using the management plane reporting method.

[0034] In one possible design, the second request further includes requested channel metrics, which include at least one of the following: scheduling signal-to-noise ratio (SINR), rank (RANK), number of power control resource blocks (RBs), maximum number of pairing layers, modulation and coding scheme (MCS), spectral efficiency, initial bit error rate (BER), or residual bit error rate (BER). The channel metrics carried in the first request indicate the need to collect the corresponding channel metric data.

[0035] In one possible design, the second request may further include at least one of the following: data reporting method, quantization level, reporting cycle, collection range, or quantization method. The data reporting method, quantization level, reporting cycle, collection range, or quantization method carried in the second request indicate whether the collected data should be processed or reported.

[0036] In one possible design, a service model for each terminal device is determined based on the user data; a QoS policy for each terminal device is determined based on the user type, the service model, and the channel indicator data. By converting user data into a service model and determining the QoS policy for each terminal device based on the service model and channel indicator data, the optimal QoS policy is selected and distributed to the terminal device under limited network resources, ensuring a good user experience and avoiding interference with other terminal devices.

[0037] In one possible design, the user type, service model, and channel indicator data of each terminal device are input into a simulation model to determine the optimal QoS policy among multiple candidate QoS policies. By inputting the service model and channel indicator data into the simulation model, the QoS policy for each terminal device is determined. This allows for the selection of the optimal QoS policy for each terminal device under limited network resources, ensuring a good user experience and avoiding interference with other terminal devices.

[0038] Fourthly, embodiments of this application provide a communication device that performs the functions described in the first aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the first aspect. These modules, units, or means can be implemented in software, hardware, or a combination of software and hardware. The device includes:

[0039] The transceiver module is used to receive a first request from a first network element. The first request is used to request network evaluation. The first request includes a Quality of Service (QoS) policy and a target area. The first network element is a network element responsible for network function operation.

[0040] The transceiver module is also used to acquire call statistics data and user data of multiple terminal devices within the target area based on the first request;

[0041] The processing module is configured to determine network evaluation parameters for each terminal device based on the call statistics data, the user data, and the QoS policy issued to each of the plurality of terminal devices. The network evaluation parameters are used to evaluate the network usage of terminal devices using different QoS policies.

[0042] In one possible design, the first request may also include rules for issuing QoS policies;

[0043] The processing module is further configured to determine the QoS policy to be issued to each terminal device according to the QoS policy issuance rules.

[0044] In one possible design, the first request may also include the number of users to whom QoS policies are issued, and the different QoS policies include a first priority QoS policy and a second priority QoS policy.

[0045] The processing module is further configured to determine a first number of terminal devices using the first priority QoS policy based on the number of users issued by the QoS policy; and to determine a second number of terminal devices using the second priority QoS policy based on the total number of the plurality of terminal devices and the first number.

[0046] In one possible design, the transceiver module is further configured to send a second request to a second network element, the second request including the target area, the second request being used to request the call statistics data within the target area, the second network element being a network element responsible for operation, management, and maintenance; and to receive the call statistics data within the target area from the second network element.

[0047] In one possible design, the second request includes call statistics indicators corresponding to the requested call statistics data, the call statistics indicators including at least one of the following: the number of times the Reference Received Power (RSRP) measurement on the Physical Uplink Shared Channel (PUSCH) falls within different intervals, the number of times the Signal-to-Noise Ratio (SINR) measurement on the PUSCH falls within different intervals, the distribution of the user's spectral efficiency on the PUSCH falls within different intervals, the number of times the RSRP measurement on the Physical Downlink Shared Channel (PDSCH) falls within different intervals, the number of times the SINR measurement on the PDSCH falls within different intervals, or the distribution of the user's spectral efficiency on the PDSCH falls within different intervals.

[0048] In one possible design, the second request may further include at least one of the following: a collection period or a statistical period, wherein the collection period is used to indicate the time interval for collecting the call statistics data, and the statistical period is used to indicate the time interval for statistically analyzing the call statistics data.

[0049] In one possible design, the transceiver module is further configured to send a third request, the third request including the target area, the third request being used to request the user data within the target area; and to receive the user data within the target area.

[0050] In one possible design, the processing module is further configured to determine the channel indicators of each terminal device based on the call statistics data, and to determine the service model of each terminal device based on the user data; and to determine the network evaluation parameters of each terminal device based on the channel indicators of each terminal device, the service model of each terminal device, and the QoS policy issued for each terminal device.

[0051] In one possible design, the processing module is further configured to determine the value of the call statistics index for each terminal device based on the call statistics data; and to convert the value of the call statistics index into the channel index based on the mapping relationship between the value of the call statistics index and the channel index.

[0052] In one possible design, the processing module is further configured to determine, based on the call statistics data, the number of times the call statistics index of each terminal device falls within each interval; determine, based on the number of times the call statistics index falls within each interval, the probability that the call statistics index of each terminal device falls within each interval; and determine, based on the probability that the call statistics index falls within each interval, the value of the call statistics index of each terminal device.

[0053] In one possible design, the processing module is further configured to input the channel metrics of each terminal device, the service model of each terminal device, and the QoS policy issued to each terminal device into the simulation model to determine the network evaluation parameters of each terminal device.

[0054] In one possible design, the transceiver module is further configured to send evaluation results to the first network element, the evaluation results including network usage of terminal devices using different QoS policies.

[0055] In one possible design, the network evaluation parameters include at least one of the following: throughput, latency, or packet loss rate.

[0056] The operation and beneficial effects of this communication device can be found in the method and beneficial effects described in the first aspect above, and will not be repeated here.

[0057] Fifthly, embodiments of this application provide a communication device that performs the functions described in the second aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the second aspect. These modules, units, or means can be implemented in software, hardware, or a combination of software and hardware. The device includes:

[0058] The transceiver module is used to send a first request to the network data analysis function network element. The first request is used to request network evaluation. The first request includes a Quality of Service (QoS) policy and a target area. The target area is used to indicate the acquisition of call statistics data and user data of multiple terminal devices. The QoS policy, the call statistics data, and the user data are used to determine the network evaluation parameters of each terminal device. The network evaluation parameters are used to evaluate the network usage of terminal devices using different QoS policies.

[0059] In one possible design, the transceiver module is further configured to receive evaluation results from the network data analysis function network element, the evaluation results including network usage of terminal devices using different QoS policies.

[0060] In one possible design, the network evaluation parameters include at least one of the following: throughput, latency, or packet loss rate.

[0061] The operation and beneficial effects of this communication device can be found in the method and beneficial effects described in the second aspect above, and will not be repeated here.

[0062] Sixthly, embodiments of this application provide a communication device that performs the functions described in the third aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the third aspect. These modules, units, or means can be implemented in software, hardware, or a combination of software and hardware. The device includes:

[0063] The transceiver module is used to acquire user data and channel indicator data from multiple terminal devices within the cell;

[0064] The processing module is used to determine the QoS policy of each of the plurality of terminal devices based on the user data and the channel index data.

[0065] In one possible design, the transceiver module is further configured to send a first request to a first network element, the first request being for requesting the channel index data, the first network element being a network element responsible for operation, management, and maintenance; and to receive the channel index data from the first network element.

[0066] In one possible design, the first request carries a first reporting method, which is a management plane report.

[0067] In one possible design, the first request may further include requested channel metrics, which include at least one of the following: scheduling signal-to-noise ratio (SINR), rank (RANK), number of power control resource blocks (RBs), maximum number of pairing layers, modulation and coding scheme (MCS), spectral efficiency, initial bit error rate (BER), or residual bit error rate (BER).

[0068] In one possible design, the first request may further include at least one of the following: data reporting method, quantization level, reporting cycle, collection range, or quantization method.

[0069] In one possible design, the transceiver module is further configured to send a second request to a first network element, the second request being for requesting the reporting of the channel indicator data via the user plane, wherein the first network element is a network element responsible for operation, management, and maintenance; send a third request to a second network element, the third request being for notifying a third network element to report the channel indicator data, wherein the second network element is a network element responsible for session management, and the third network element is a network element responsible for user plane data forwarding and reception; and receive the channel indicator data from the third network element.

[0070] In one possible design, the second request carries a second reporting method, which is user-side reporting.

[0071] In one possible design, the second request may also include requested channel metrics, which include at least one of the following: scheduling signal-to-noise ratio (SINR), rank (RANK), number of power control resource blocks (RBs), maximum number of pairing layers, modulation and coding scheme (MCS), spectral efficiency, initial bit error rate (BER), or residual bit error rate (BER).

[0072] In one possible design, the second request may also include at least one of the following: data reporting method, quantization level, reporting cycle, collection range, or quantization method.

[0073] In one possible design, the processing module is further configured to determine the service model of each terminal device based on the user data; and to determine the QoS policy of each terminal device based on the user type of each terminal device, the service model of each terminal device, and the channel indicator data of each terminal device.

[0074] In one possible design, the processing module is further configured to input the user type of each terminal device, the service model of each terminal device, and the channel indicator data of each terminal device into the simulation model to determine the optimal QoS strategy among multiple candidate QoS strategies.

[0075] The operation and beneficial effects of this communication device can be found in the method and beneficial effects described in the third aspect above, and will not be repeated here.

[0076] In a seventh aspect, embodiments of this application provide a communication device, which includes a memory and one or more processors. The memory stores part or all of the necessary computer programs or instructions for implementing the functions described in the first or third aspect above. The one or more processors can execute the computer programs or instructions, and when the computer programs or instructions are executed, cause the communication device to implement the methods in any possible design or implementation of the first or third aspect above.

[0077] In one possible design, the communication device may further include an interface circuit, wherein the processor is used to communicate with other devices or components through the interface circuit.

[0078] In one possible design, the communication device may also include the memory.

[0079] The aforementioned communication device may be an NWDAF network element, or a communication module within an NWDAF network element, or a chip within an NWDAF network element responsible for communication functions, such as a modem chip (also known as a baseband chip), or a SoC or SIP chip containing a modem module.

[0080] Eighthly, embodiments of this application provide a communication device, the communication device including a memory and one or more processors. The memory is used to store part or all of the computer program or instructions necessary to implement the functions involved in the second aspect above. The one or more processors are capable of executing the computer program or instructions, and when the computer program or instructions are executed, cause the communication device to implement the methods in any possible design or implementation of the second aspect above.

[0081] In one possible design, the communication device may further include an interface circuit, wherein the processor is used to communicate with other devices or components through the interface circuit.

[0082] In one possible design, the communication device may also include the memory.

[0083] The aforementioned communication device may be a first network element, or a communication module in the first network element, or a chip in the first network element responsible for communication functions, such as a modem chip (also known as a baseband chip) or a SoC or SIP chip containing a modem module.

[0084] Ninthly, this application provides a computer-readable storage medium for storing a computer program that, when executed, causes the method described in any one of the first to third aspects to be implemented.

[0085] In a tenth aspect, this application provides a computer program product including a computer program that, when executed, causes the method described in any one of the first to third aspects to be implemented.

[0086] In one aspect, embodiments of this application provide a communication system, which includes an NWDAF network element and a first network element. The NWDAF network element is used to perform the steps in the first or third aspect described above, and the first network element is used to perform the steps in the second aspect described above.

[0087] In a twelfth aspect, a chip is provided, the chip including a processor and a communication interface for communicating with external or internal devices, the processor for implementing the methods of the above aspects.

[0088] In one possible design, the chip may further include a memory storing computer programs or instructions, which the processor executes, either from the stored computer programs or instructions or derived from other programs or instructions. When the computer program or instructions are executed, the processor implements the methods described above.

[0089] In one possible design, the chip can be integrated into the NWDAF network element or the first network element. Attached Figure Description

[0090] Figure 1 This is a schematic diagram of a communication system architecture;

[0091] Figure 2 This is a schematic diagram of the connection between an NWDAF network element and an NF network element.

[0092] Figure 3 This is a flowchart illustrating a communication method provided in an embodiment of this application;

[0093] Figure 4 This is a schematic diagram of a simulation model;

[0094] Figure 5 This is a flowchart illustrating another communication method provided in an embodiment of this application;

[0095] Figure 6 This is a flowchart illustrating another communication method provided in an embodiment of this application;

[0096] Figure 7 This is a diagram illustrating the selection of a QoS strategy;

[0097] Figure 8 This is a flowchart illustrating another communication method provided in an embodiment of this application;

[0098] Figure 9 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0099] Figure 10 This is a schematic diagram of the structure of a network device provided in an embodiment of this application. Detailed Implementation

[0100] like Figure 1 As shown, Figure 1This is a schematic diagram of a communication system architecture. This communication system is based on the 3rd Generation Partnership Project (3GPP) system architecture for 5G (5th generation mobile communication technology). The system includes terminal equipment (e.g., user equipment, UE), a radio access network (RAN), and a core network. The core network's network functions and entities mainly include: user plane function (UPF) network elements, data network (DN) network elements, access and mobility management function (AMF) network elements, session management function (SMF) network elements, policy control function (PCF) network elements, application function (AF) network elements, network slice selection function (NSSF) network elements, authentication server function (AUSF) network elements, and unified data management (UDM) network elements. The diagram illustrates the interaction relationships between network functions and entities, as well as their corresponding interfaces. For example, the UE and AMF network elements can interact through the N1 interface, and the interaction messages are called N1 Messages. Some interfaces are implemented using a service-oriented approach.

[0101] The UE, (R)AN device, UPF network element, and DN network element are generally referred to as data plane network functions and entities. User data traffic can be transmitted through the protocol data unit session (PDU) established between the UE and the DN network element, and the transmission passes through the (R)AN and UPF network function entities. The remaining parts are referred to as control plane network functions and entities, which are mainly responsible for authentication and authorization, registration management, session management, mobility management, and policy control, thereby achieving reliable and stable transmission of user layer traffic. The user plane is used to carry service data, while the control plane is used to carry signaling messages.

[0102] The following describes the functions of the main entities or network elements included in the communication system:

[0103] Terminal devices can be UEs (User Equipment), handheld terminals, laptops, cellular phones, smartphones, tablets, augmented reality (AR) devices, virtual reality (VR) devices, machine-type communication terminals, or other devices capable of accessing the network. Terminal devices communicate with access network devices using some air interface technology (such as New Radio (NR) or Long Term Evolution (LTE)). Terminal devices can also communicate with each other using some air interface technology (such as NR or LTE). In vehicle-to-everything (V2X) communication, the communication terminal mounted on the vehicle is a type of terminal device, and the roadside unit (RSU) can also be considered a terminal device. Unmanned aerial vehicles (UAVs) carrying communication terminals can also be considered a type of terminal device.

[0104] RAN equipment: Primarily responsible for radio resource management, quality of service management, data compression, and encryption on the air interface side. The access network equipment can include various types of base stations, such as macro base stations, micro base stations, relay stations, and access points. In systems employing different radio access technologies, the names of equipment with base station functions may differ; for example, in 5G systems, it is called a gNB.

[0105] AMF network elements are core network elements primarily responsible for signaling processing, such as access control, mobility management, attach and detach, and gateway selection. When an AMF network element provides services to a session in a terminal device, it provides control plane storage resources for that session to store the session identifier and the SMF network element identifier associated with the session identifier.

[0106] SMF network elements are responsible for user plane network element selection, user plane network element redirection, Internet Protocol (IP) address allocation, bearer establishment, modification and release, and quality of service (QoS) control.

[0107] UPF network elements are responsible for forwarding and receiving user data in terminal devices. They can receive user data from the data network and transmit it to the terminal device through the access network equipment; UPF network elements can also receive user data from the terminal device through the access network equipment and forward it to the data network. The transmission resources and scheduling functions that provide services to the terminal device in the UPF network element are managed and controlled by the SMF network element.

[0108] NEF network elements primarily support secure interaction between 3GPP networks and third-party applications.

[0109] AF network element: mainly supports interaction with the 3GPP core network to provide services, such as influencing data routing decisions, policy control functions, or providing some third-party services to the network side.

[0110] PCF network element: Responsible for policy control decisions, providing policy rules for control plane functions, and traffic-based billing control functions.

[0111] NSSF network element: mainly responsible for network slice selection, determining the network slice instance that the UE is allowed to access based on the UE's slice selection auxiliary information, subscription information, etc.

[0112] UDM network element: mainly responsible for the management of UE subscription data, including the storage and management of UE identifiers, UE access authorization, etc.

[0113] AUSF network element: Supports 3GPP and non-3GPP access authentication.

[0114] NRF network elements: support the registration and discovery of network functions.

[0115] UDR network element: Stores and retrieves subscription data used by UDM and PCF.

[0116] It should be understood that Figure 1 The network elements shown, such as AMF, SMF, UPF, PCF, UDM, NSSF, and AUSF, can be understood as network elements used to implement different functions, such as network slices that can be combined as needed. These network elements can be independent devices or integrated into the same device to implement different functions. They can be network components in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (e.g., a cloud platform). This application does not limit the specific form of the above network elements.

[0117] Figure 1 The interface names between the various network elements are merely examples; in actual implementations, the interface names may differ, and this application does not impose any specific limitations on them. Furthermore, the names of the messages (or signaling) transmitted between the aforementioned network elements are also merely examples and do not constitute any limitation on the function of the messages themselves.

[0118] The technical solutions in this application embodiment can be applied to various communication systems, such as Universal Mobile Telecommunications System (UMTS), Wireless Local Area Network (WLAN), Wireless Fidelity (Wi-Fi) system, 4th generation (4G) mobile communication system, such as Long Term Evolution (LTE) system, 5th generation (5G) mobile communication system, such as New Radio (NR) system, and future evolution communication systems, such as 6th generation (6G) mobile communication system, etc.

[0119] The intelligentization of wireless networks is an important evolutionary trend. 3GPP has added a network data analytics function (NWDAF) element to 5G networks.

[0120] The main functions of the NWDAF network element include: supporting data collection from other network function (NF) network elements and application function (AF) network elements; supporting data collection from network operation and maintenance systems (such as operation administration and maintenance, OAM); and providing metadata open services and data analysis services to NF network elements or AF network elements. The main objectives of introducing the NWDAF network element include: automating and intelligentizing network operation and maintenance, optimizing network performance and service experience, and ensuring end-to-end service level agreements (SLAs). The artificial intelligence (AI) model trained by the NWDAF network element can be applied to network-specific areas such as mobility management, session management, and network automation, using AI methods to replace the numerical formula-based methods in traditional network functions.

[0121] by Figure 1 The network architecture shown is an example. Figure 1 The network architecture shown does not include NWDAF network elements. One possibility is that NWDAF network elements can have direct interfaces with all NFs.

[0122] As an example, Figure 2 This is a schematic diagram illustrating the connection between an NWDAF network element and an NF network element. (Example) Figure 2As shown, the main interfaces between NWDAF network elements and NF network elements include two types: Nnf interfaces and Nnwdaf interfaces. The Nnf interface can be used by an NWDAF network element to request one or more of the following from other NF network elements: subscribing to data delivery for a specific context, unsubscribing to data delivery, requesting specific reports for data in a specific context, etc. The 5G system architecture also allows NWDAF network elements to obtain management data from OAM network elements by calling OAM network element operation and maintenance system services. The Nnwdaf interface can be used by other NF network elements to request one or more of the following from NWDAF network elements: subscribing to network analysis delivery for a specific context, unsubscribing to network analysis delivery, requesting specific reports for network analysis in a specific context, etc. In existing wireless network systems, NWDAF network elements primarily collect data from various traditional NF network elements, learn models through data analysis, and provide AI optimization services such as data analysis to each NF network element.

[0123] The main function of 5G QoS is to provide different quality of service (QoS) for different service flows. The core network sends the QoS requirements for different service flows to the access network through 5G QoS identifiers (5QIs). Each 5QI is mapped to a set of QoS parameters (5G QoS parameters / characteristics), for example:

[0124] Resource type: Determines whether the network should allocate dedicated resources to service flows to meet the guaranteed flow bit rate (GFBR).

[0125] Guaranteed traffic bit rate: The bit rate that the network needs to guarantee for service flows.

[0126] Maximum flow bit rate (MFBR): The maximum bit rate that a network can limit the flow of traffic to.

[0127] Packet delay budget (PDB): Defines the maximum delay for a data packet in a service flow from the UE to the UPFN6 side (or vice versa).

[0128] These characteristics specifically define the QoS requirements for a service flow. The core network can also specify the values ​​of these QoS characteristics. The access network adjusts the scheduling priority of the UE based on the 5QI and QoS characteristics issued by the core network to try to meet the requirements of the 5QI and QoS characteristics.

[0129] QoS policies can guarantee the provision of corresponding 5G QoS, and different QoS policies can provide different 5G QoS. Extensive use of QoS policies in the network consumes network resources and requires evaluation before implementation. Operators' experience guarantee packages use QoS policies such as guaranteed bit rate (GBR) and high-priority non-GBR. Operators are concerned that excessive distribution of experience guarantee packages may negatively impact ordinary users and the network. For example, in high-security scenarios such as concerts, operators want to evaluate the effectiveness of QoS policies in advance. Currently, air interface simulation and machine learning (ML) are two main methods for evaluating complex systems (such as 5G air interface networks). The following section introduces existing technologies based on these two methods to address the above problems.

[0130] Air interface simulation can be end-to-end white-box modeling, such as the open-source ns-3. This air interface simulation technology takes the location information of the UE and base station, as well as the surrounding physical environment information, as input, and outputs key performance indicators such as data rate and latency. The simulation requires modeling not only channel propagation and the PHY layer, but also the behavior of the protocol stack, including the Medium Access Control (MAC) layer, the Radio Link Control (RLC) layer, and the Packet Data Convergence Protocol (PDCP) layer. However, the computational load of channel propagation and physical layer models is high; a single simulation typically takes several minutes or even longer to run, resulting in high computational complexity.

[0131] Machine learning or artificial intelligence techniques are used to fit the relationship between input and output data. The input data consists of user flow data records (UFDRs) such as latency and throughput of existing service flows in the core network. The output is the latency, throughput, and other metrics after conditions change (e.g., changes in the QoS policy of the service flows). However, this method relies on training data collected from the live network or other simulation tools, and simulations based solely on core network data have low accuracy.

[0132] To address the aforementioned technical problems, the embodiments of this application provide the following solutions.

[0133] like Figure 3 As shown, Figure 3 This is a flowchart illustrating a communication method provided in an embodiment of this application. The method mainly includes the following steps:

[0134] S301, the NWDAF network element receives a first request from a first network element. The first request is used to request network evaluation. The first request includes a Quality of Service (QoS) policy and a target area. The first network element is a network element responsible for network function operation.

[0135] The first network element can be an NF consumer (operation and maintenance system). QoS policies are used to guarantee the quality of service for service flows; different QoS policies guarantee different qualities of service. QoS policies can include first-priority QoS policies and second-priority QoS policies, with the first-priority QoS policy guaranteeing a higher quality of service to the terminal device than the second-priority QoS policy. The target area can be represented as a specific region, such as the area inside and around a concert venue. The target area can also be represented as a cell covered by one or more base stations.

[0136] Optionally, the first request also includes QoS policy delivery rules. The NWDAF network element can determine the QoS policy to be delivered to each terminal device based on the QoS policy delivery rules. The QoS policy delivery rules can be as follows: a QoS policy is delivered to the terminal device when preset conditions are met. For example, when the terminal device uses a first type of application (such as a live streaming application), a first-priority QoS policy can be delivered to the terminal device. Alternatively, when the terminal device's current throughput is greater than or equal to a first threshold, a first-priority QoS policy can be delivered to the terminal device; when the terminal device's current throughput is less than the first threshold, a second-priority QoS policy can be delivered to the terminal device.

[0137] Optionally, the first request also includes the number of users to whom the QoS policy is issued. The NWDAF network element can determine a first number of terminal devices using the first priority QoS policy based on the number of users to whom the QoS policy is issued, and determine a second number of terminal devices using the second priority QoS policy based on the total number of the plurality of terminal devices and the first number. The total number of the plurality of terminal devices is the total number of all terminal devices in the target area. Further, the number of users to whom the QoS policy is issued can be used as the first number, and the total number of the plurality of terminal devices can be subtracted from the first number to calculate the second number. Alternatively, if the number of users to whom the QoS policy is issued does not exceed the number of users to whom the QoS policy is issued, the number of terminal devices actually issued the first priority QoS policy can be determined according to the QoS policy issuance rules, and the number of terminal devices actually issued the first priority QoS policy can be used as the first number, and the total number of the plurality of terminal devices can be subtracted from the first number to calculate the second number.

[0138] S302, the NWDAF network element obtains call statistics data and user data of multiple terminal devices in the target area based on the first request.

[0139] Specifically, the NWDAF network element can obtain call statistics data from multiple terminal devices in the target area from the OAM network element, and the NWDAF network element can obtain user data from multiple terminal devices in the target area from the UPF network element.

[0140] The call statistics data can be represented as call statistics indicators of multiple terminal devices within a target area collected within a single acquisition period. The acquisition period can be 100ms or 200ms, etc. Call statistics indicators can include the number of times the reference signal received power (RSRP) measurement on the physical uplink shared channel (PUSCH) falls within different intervals, the number of times the signal-to-interference-plus-noise ratio (SINR) measurement on the PUSCH falls within different intervals, the distribution of user spectral efficiency on the PUSCH falls within different intervals, the number of times the RSRP measurement on the physical downlink shared channel (PDSCH) falls within different intervals, the number of times the SINR measurement on the PDSCH falls within different intervals, or the distribution of user spectral efficiency on the PDSCH falls within different intervals.

[0141] User data can be UFDR (User Data Rate), and user data from multiple terminal devices can be represented as the UFDR of multiple terminal devices within a target area statistically analyzed within a statistical period. The statistical period can be a specific time period, such as the time period with the highest physical resource block (PRB) utilization. User data can also include user plane data, which can be data exchanged between the terminal and the network.

[0142] S303, the NWDAF network element determines the network evaluation parameters for each terminal device based on the call statistics data, the user data, and the QoS policy issued to each of the multiple terminal devices. The network evaluation parameters are used to evaluate the network usage of terminal devices using different QoS policies.

[0143] Firstly, the NWDAF network element can determine the channel indicators of each terminal device based on the call statistics data.

[0144] Specifically, the NWDAF network element can determine the value of the call statistics indicator for each terminal device based on the call statistics data. Further, it can determine the number of times each terminal device's call statistics indicator falls within each interval based on the call statistics data; determine the probability of each terminal device's call statistics indicator falling within each interval based on the number of times the call statistics indicator falls within each interval; and determine the value of each terminal device's call statistics indicator based on the probability of the call statistics indicator falling within each interval.

[0145] Then, based on the mapping relationship between the call statistics index values ​​and channel indicators, the call statistics index values ​​are converted into channel indicators. The following explanation uses the RSRP distribution in the uplink scenario as an example.

[0146] For example, if we want to count the number of times the RSRP measurement value of the target area falls within different intervals during the collection period, for each UE in the cell, RsrpIndexxi represents the number of times the UE's RSRP is located in interval i. Here, RsrpIndex1 represents the number of times the UE's RSRP is located in interval 1, RsrpIndex2 represents the number of times the UE's RSRP is located in interval 2, ..., RsrpIndexN represents the number of times the UE's RSRP is located in interval N, where i is greater than or equal to 1 and less than or equal to N. Based on the number of times the UE's RSRP is located in interval i, we calculate the probability that each UE's call statistics index falls within each interval:

[0147] P(i)=RsrpIndexi / (RsrpIndex1+RsrpIndex2+……+RsrpIndexN)

[0148] Here, P(i) represents the probability that the UE's call statistics index is located in interval i. P(1), P(2), ..., P(N) can be calculated respectively. If the probability of P(i) is the largest, the midpoint of interval i corresponding to P(i) can be taken as the value of the UE's RSRP.

[0149] Then, in the live network, the RSRP, SINR, RANK, and number of power control resource blocks (RBs) of the UE are collected respectively. The mapping relationship between SINR and RSRP, RANK and RSRP, and RSRP and number of power control RBs are fitted to determine the mapping relationship between RSRP value and SINR, RSRP value and RANK, and RSRP value and number of power control RBs. Based on the mapping relationship between RSRP value and SINR, the RSRP value is converted into SINR, the RSRP value is converted into RANK, and the RSRP value is converted into number of power control RBs.

[0150] It should be noted that channel metrics, in addition to SINR, RANK, and the number of power control RBs, can also include maximum number of paired layers, initial transmission error rate (IPR), and residual IPR. The RSRP value can be converted into maximum number of paired layers, IPR, and residual IPR respectively using the methods described above. Further details will not be elaborated here.

[0151] Secondly, the NWDAF network element can determine the service model of each terminal device based on the user data. The service model can represent the type of application used by the terminal device (e.g., a live streaming app or a background traffic app) or its throughput. For example, the total amount of user data for a terminal device within a unit of time can be counted to determine the service model of that terminal device.

[0152] Thirdly, the NWDAF network element can determine the QoS policy to be issued to each terminal device based on the QoS policy included in the first request, the number of users to whom the QoS policy is issued, or the issuance rules of the QoS policy. For example, it can issue a first-priority QoS policy to the terminal device and a second-priority QoS policy to other terminal devices based on the number of users to whom the QoS policy is issued. Alternatively, if the issuance rules of the QoS policy are met, a first-priority QoS policy is issued to the terminal device; if the issuance rules are not met, a second-priority QoS policy is issued to the terminal device.

[0153] Combining the above three aspects, the NWDAF network element can determine the network evaluation parameters for each terminal device based on the channel indicators, service model, and QoS policy issued to each terminal device. Furthermore, the channel indicators, service model, and QoS policy issued to each terminal device can be input into a simulation model to determine the network evaluation parameters for each terminal device. These network evaluation parameters may include throughput and / or latency, etc. Taking an uplink scenario simulation as an example, the simulation process is illustrated below.

[0154] like Figure 4 As shown, Figure 4This is a schematic diagram of a simulation model. The simulation model includes a UE model and a RAN model. The UE model can include the Application (APP) layer, Transmission Control Protocol (TCP) layer, Internet Protocol (IP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Medium Access Control (MAC) layer. The RAN model can include the MAC layer, RLC layer, and PDCP layer. The simulation model can also include a service model. The service model can represent different types of APPs or different throughput rates. For example, different types of APPs can include live video streaming, video-on-demand, or background traffic. It should be noted that the behavior of the protocol layers in the simulation model is consistent with the actual behavior of the protocol layers.

[0155] The channel metrics, service model, and QoS policy of UEx are input into the simulation model. The APP layer of the UE model sends "data packets" (simulated data packet objects, not real network data packets) according to the packet size and interval given by the service model. These data packets are processed sequentially through the TCP, IP, PDCP, and RLC layers of the UE model, and then enter the buffer of the RLC layer. After leaving the MAC layer of the UE model, the data packets enter the MAC layer of the RAN model. The MAC layer of the RAN model limits the transmission rate and latency of each UE's data packets to the MAC layer based on the channel metrics and QoS policies of each UE. After leaving the MAC layer of the RAN model, the data packets continue through the RLC and PDCP layers of the RAN model, completing the simulation of the entire over-the-air uplink data transmission process.

[0156] Each data packet sent by the APP layer of the UE model undergoes the above process. In the simulation, the throughput and latency of each UE are recorded.

[0157] Optionally, the NWDAF network element can evaluate the network usage of terminal devices using different QoS policies based on the network evaluation parameters of each terminal device. The network usage can include the user experience of terminal devices using a first-priority QoS policy, the user experience of terminal devices using a second-priority QoS policy, or the consumption of GBR resources.

[0158] Furthermore, network evaluation parameters for terminal devices using the first-priority QoS policy and those using the second-priority QoS policy can be separately analyzed. Then, the user experience of terminal devices using the first-priority QoS policy can be determined based on their network evaluation parameters, and the user experience of terminal devices using the second-priority QoS policy can be determined based on their network evaluation parameters. Alternatively, the network evaluation parameters for both the first-priority and second-priority QoS policies can be analyzed to determine the consumption of GBR resources.

[0159] It should be noted that the number of terminal devices using the first-priority QoS policy and the number of terminal devices using the second-priority QoS policy can be adjusted. Then, based on the adjusted number of users, the channel indicators, service models, and QoS policies of multiple terminal devices can be re-input into the simulation model for simulation, thereby determining the network usage under different numbers of users under the QoS policy.

[0160] In this embodiment, by acquiring call statistics data and user data from multiple terminal devices within a target area, network evaluation parameters for each terminal device are determined. This allows for an assessment of network usage of terminal devices using different QoS policies before issuing high-priority QoS policies, preventing mutual interference between devices using different QoS policies and improving user experience. Alternatively, the total number of users eligible for QoS policies within a certain area can be assessed to avoid over-issuance of QoS policies, which could negatively impact user experience. Furthermore, assessing network usage using call statistics data and user data reduces computational complexity and improves prediction accuracy.

[0161] like Figure 5 As shown, Figure 5 This is a flowchart illustrating another communication method provided in an embodiment of this application. The method mainly includes the following steps:

[0162] S501, the NF consumer sends a first request to the NWDAF network element. The first request is used to request network evaluation. The first request includes the Quality of Service (QoS) policy and the target area. The first network element is the network element responsible for network function operation.

[0163] The specific implementation process of S501 and Figure 3 The specific implementation process of S301 in the illustrated embodiment is the same, and the specific implementation process of S501 can be referred to Figure 3 S301 in the illustrated embodiment will not be described again here.

[0164] S502, the NWDAF network element sends a second request to the OAM network element.

[0165] The second request includes the target area, and the second request is used to request the call statistics data within the target area.

[0166] Optionally, the second request further includes call statistics indicators corresponding to the requested call statistics data. These call statistics indicators include at least one of the following: the number of times the Reference Received Power (RSRP) measurement on the Physical Uplink Shared Channel (PUSCH) falls within different intervals; the number of times the Signal-to-Noise Ratio (SINR) measurement on the PUSCH falls within different intervals; the distribution of the user's spectral efficiency on the PUSCH falls within different intervals; the number of times the RSRP measurement on the Physical Downlink Shared Channel (PDSCH) falls within different intervals; the number of times the SINR measurement on the PDSCH falls within different intervals; or the distribution of the user's spectral efficiency on the PDSCH falls within different intervals. By carrying these call statistics indicators in the second request, the OAM is instructed to collect call statistics data corresponding to the indicators.

[0167] Optionally, the second request may further include at least one of the following: a collection period or a statistical period, wherein the collection period indicates the time interval for collecting the call statistics data, and the statistical period indicates the time interval for statistically analyzing the call statistics data. After receiving the second request, the OAM may collect call statistics data according to the collection period and perform statistical analysis on the collected call statistics data according to the statistical period.

[0168] As shown in Table 1, the NWDAF subscribes to call statistics data related to the statistical distribution of the base station side and air interface channels from the OAM network element, and instructs the OAM network element on the information shown in Table 1. The information shown in Table 1 includes call statistics indicators, indicator identifiers in the base station network management system, indicator descriptions, collection periods, and statistical periods. The OAM network element collects call statistics data and performs statistics according to the information shown in Table 1. For example, if the collection period is 100ms, the OAM can collect call statistics data corresponding to the call statistics indicators every 100ms. The call statistics indicators are not limited to those shown in Table 1; other indicators can also be used. Similarly, the collection period and statistical period are not limited to the values ​​shown in Table 1; other values ​​can also be used.

[0169] Table 1

[0170]

[0171]

[0172] S503, the OAM network element sends call statistics data to the NWDAF network element.

[0173] S504, the NWDAF network element sends a third request to the SMF network element.

[0174] The third request includes the target area, and the third request is used to request the user data within the target area.

[0175] Specifically, the NWDAF network element determines the network's operating status and identifies the time periods when the network is in a busy state by analyzing the utilization rate of the physical resource block (PRB) between the base station and the UE. For example, it calculates the time point with the highest average PRB utilization across all network sites throughout the day, and then sends a third request to the SMF network element during that time period.

[0176] Optionally, the NWDAF network element can send a third request to the SMF network element multiple times according to a preset period in order to collect user data in batches.

[0177] S505, the SMF network element sends a fourth request to the UPF network element.

[0178] The fourth request includes the target area and is used to request the user data within the target area. The SMF network element transparently transmits the third request sent by the NWDAF network element.

[0179] S506, the UPF network element sends user data to the NWDAF network element.

[0180] S507, the NWDAF network element determines the network evaluation parameters for each terminal device based on call statistics data, user data, and the QoS policies issued to each of the multiple terminal devices. These network evaluation parameters are used to evaluate the network usage of terminal devices using different QoS policies.

[0181] The specific implementation process of S507 and Figure 3 The specific implementation process of S303 in the illustrated embodiment is the same, and the specific implementation process of S507 can be referred to Figure 3 S303 in the illustrated embodiment will not be described again here.

[0182] S508, the NWDAF network element sends evaluation results to NF consumers, the evaluation results including the network usage of terminal devices using different QoS policies.

[0183] In this embodiment, network evaluation parameters for each terminal device are determined by collecting call statistics data from OAM network elements and user data from UPF network elements. This allows for the assessment of network usage of terminal devices using different QoS policies before issuing high-priority QoS policies, preventing mutual interference between terminal devices using different QoS policies and improving user experience. Alternatively, the total number of users eligible for QoS policies within a certain area can be assessed to avoid over-issuance of QoS policies, which could negatively impact user experience. Furthermore, assessing network usage using call statistics data and user data reduces computational complexity and improves prediction accuracy.

[0184] The above embodiments distribute different QoS policies to terminal devices within a target area to assess network usage as a whole. The following embodiments optimize QoS policies to ensure network usage on an individual level.

[0185] like Figure 6 As shown, Figure 6 This is a flowchart illustrating another communication method provided in an embodiment of this application. The method mainly includes the following steps:

[0186] S601, the NWDAF network element acquires user data and channel indicator data from multiple terminal devices within the cell.

[0187] Specifically, the NWDAF network element can obtain user data from multiple terminal devices within the cell from the UPF network element. This user data can be UFDR (User Data Record), and the user data from multiple terminal devices can be represented as the UFDR of multiple terminal devices within the cell, collected within a statistical period. The statistical period can be a specific time interval, such as the period with the highest physical resource block (PRB) utilization. User data can also include user plane data, which can be data exchanged between the terminal and the network.

[0188] The NWDAF network element can subscribe to channel indicator data from multiple terminal devices within the cell from the OAM network element. The NWDAF can instruct the OAM network element on channel indicators so that the NWDAF network element can obtain the corresponding channel indicator data. The channel indicators include at least one of the following: scheduling signal-to-interference-plus-noise ratio (SINR), rank, number of power control resource blocks (RBs), maximum number of pairing layers, modulation and coding scheme (MCS), spectral efficiency, initial bit error rate, or residual bit error rate.

[0189] S602, the NWDAF network element determines the QoS policy for each of the multiple terminal devices based on the user data and the channel indicator data.

[0190] Specifically, the NWDAF network element can determine the service model of each terminal device based on the user data, and determine the QoS policy of each terminal device based on the user type, the service model, and the channel index data of each terminal device.

[0191] The business model can represent the type of application used by the terminal device (e.g., a live streaming app or a background traffic app) or its throughput. For example, the NWDAF network element can count the total amount of user data for a terminal device within a unit of time to determine the business model of that terminal device. User types can include high-priority users (e.g., guaranteed users) and low-priority users (e.g., ordinary users). The NWDAF network element can determine the user type of the terminal device based on its subscription information.

[0192] Furthermore, the NWDAF network element can input the user type, service model, and channel indicator data of each terminal device into the simulation model to determine the optimal QoS strategy among multiple candidate QoS strategies. These multiple candidate QoS strategies may include a first-priority QoS strategy and a second-priority QoS strategy.

[0193] Because of limited network resources, terminal devices using the first-priority QoS policy and those using the second-priority QoS policy may interfere with each other, potentially compromising the user experience of the first-priority QoS policy users. Therefore, for high-priority users (those requiring guaranteed access), when simulating based on user types, service models, and channel metrics data from multiple terminal devices, if the first-priority QoS policy provides good protection, it can be selected. Alternatively, if terminal devices using the first-priority QoS policy do not affect terminal devices using the second-priority QoS policy, the first-priority QoS policy can be selected. Otherwise, the second-priority QoS policy should be chosen.

[0194] For example, such as Figure 7 As shown, Figure 7This is a schematic diagram illustrating the selection of a QoS strategy. For each of the multiple candidate QoS strategies for a given terminal device, the decision module inputs the user type, service model, channel indicator data, and the multiple candidate QoS strategies for each terminal device into the simulation model. The module then determines the evaluation result of each candidate QoS strategy, which may include the guarantee effect of each candidate QoS strategy and / or its impact on other terminal devices. The decision module selects the optimal QoS strategy based on the evaluation results of each candidate QoS strategy. Furthermore, if a candidate QoS strategy offers the best guarantee effect and does not affect other terminal devices, then that QoS strategy is selected.

[0195] In this embodiment, the NWDAF network element obtains user data and channel indicator data from multiple terminal devices within the cell to determine the QoS policy for each terminal device. This ensures that, given limited network resources, the optimal QoS policy is selected and distributed to the terminal device, guaranteeing the user experience of the terminal device and avoiding mutual interference with other terminal devices.

[0196] like Figure 8 As shown, Figure 8 This is a flowchart illustrating another communication method provided in an embodiment of this application. The method mainly includes the following steps:

[0197] S801, PCF network element notifies NWDAF network element terminal equipment to go online.

[0198] For example, after the PCF network element learns that a high-priority (protected user) terminal device has come online, it notifies the NWDAF network element that the high-priority terminal device has come online.

[0199] S802, the NWDAF network element sends a fourth request to the SMF network element.

[0200] The fourth request is used to subscribe to user data from multiple terminal devices within the cell where the user's terminal device resides. The user data can be UFDR (User Data Record), and the user data from multiple terminal devices can be represented as the UFDR of multiple terminal devices within a statistical period. The user data can include user plane data, which can be data exchanged between the terminal and the network.

[0201] The fourth request may carry the identifier of the cell where the user's terminal device is located.

[0202] S803, the SMF network element sends subscription information to the UPF network element.

[0203] The subscription information is used to subscribe to user data from multiple terminal devices within the community. The subscription information can carry the identifier of the community where the user's terminal device is located.

[0204] S804, the UPF network element sends user data from multiple terminal devices within the cell to the NWDAF network element.

[0205] Specifically, after receiving the subscription information, the UPF network element can determine the cell where the user's terminal device is located based on the identifier of the cell where the user's terminal device is located, collect user data from multiple terminal devices (including the user's terminal device) in that cell, and report it to the NWDAF network element.

[0206] Optionally, the UPF network element can collect user data from multiple terminal devices within the cell according to a preset period.

[0207] The following describes how the NWDAF network element obtains channel indicator data from multiple terminal devices within a cell. It mainly includes the following two methods, and the NWDAF network element can choose either method to obtain the channel indicator data.

[0208] The first method, the management-level reporting method, mainly includes:

[0209] S805, the NWDAF network element sends a first request to the OAM network element. This first request is used to request the channel indicator data.

[0210] The first request carries a first reporting method, which is management plane reporting. That is, the OAM network element can use the existing interface between the NWDAF network element and the OAM network element to report channel indicator data of multiple terminal devices within the cell to the NWDAF network element.

[0211] Optionally, the first request may further include requested channel metrics, which include at least one of the following: signal-to-interference-plus-noise ratio (SINR), rank, number of power control resource blocks, maximum number of pairing layers, modulation and coding scheme (MCS), spectral efficiency, initial bit error rate, or residual bit error rate. The OAM network element may collect corresponding channel metric data according to the channel metrics.

[0212] Optionally, the first request may further include at least one of the following: data reporting method, quantization level, reporting period, collection range, or quantization method. The data reporting method may include reporting raw data or reporting raw data after quantization; the quantization level indicates the magnitude of data quantization; the reporting period may indicate the time interval for reporting channel indicator data; the collection range may indicate the user type or cell to which the requested channel indicator data belongs; and the quantization method may indicate the method of processing the collected raw data.

[0213] As shown in Table 2, the NWDAF network element subscribes to the OAM network element to ensure the channel index data of the user's terminal equipment and other terminal equipment in its cell, and instructs the OAM network element on the information shown in Table 2. The information shown in Table 2 includes channel indexes, data reporting method, quantization level, reporting period, collection range, and quantization method. The OAM network element collects and processes the channel index data according to the information shown in Table 2. For example, the data reporting method can include raw data reporting or quantized data reporting. If quantized data reporting is used, taking the scheduling SINR as an example, assuming the raw SINR data is 17.9, the quantization level is 10, and the level division principle is from 0 to 25, with each 2.5 level representing a level, then the level mapped to 17.9 is "17.9 / 2.5 rounded down", i.e., level 7 (levels start from 0). The OAM network element can report level 7 to the NWDAF network element. If raw data reporting is used, the collected SINR does not need to be processed, and 17.9 can be reported directly. For example, if the reporting period is 2 seconds, the OAM network element can report the collected channel index data to the NWDAF network element every 2 seconds.

[0214] Table 2

[0215]

[0216]

[0217] S806, the OAM network element sends the fifth request to the RAN equipment.

[0218] The fifth request is used to request channel indicator data. The information carried in the fifth request is the same as that carried in the first request.

[0219] S807, the RAN device sends channel indicator data of multiple terminal devices in the cell to the OAM network element.

[0220] Specifically, the RAN equipment can collect channel index data from multiple terminal devices within the cell, as shown in Table 2, and process or report the collected channel index data according to the information shown in Table 2.

[0221] S808, the OAM network element sends channel indicator data of multiple terminal devices in the cell to the NWDAF network element.

[0222] The second method, the user-reported method, mainly includes:

[0223] S809, the NWDAF network element sends a second request to the OAM network element. This second request is used to request the reporting of the channel indicator data via the user plane.

[0224] The second request carries a second reporting method, which is user plane reporting. That is, channel indicator data can be reported through the UPF network element.

[0225] Optionally, the second request may also include requested channel metrics, which include at least one of the following: scheduling signal-to-noise ratio (SINR), rank (RANK), number of power control resource blocks (RBs), maximum number of pairing layers, modulation and coding scheme (MCS), spectral efficiency, initial bit error rate (BER), or residual bit error rate (BER).

[0226] Optionally, the second request may also include at least one of the following: data reporting method, quantization level, reporting cycle, collection range, or quantization method.

[0227] The channel indicators, data reporting method, quantization level, reporting period, collection range, or quantization method indications carried in the second request have the same meanings as those carried in the first request. Explanations of this information can be found in S805 and Table 2, and will not be repeated here. For management plane reporting and user plane reporting, channel indicator data corresponding to different channel indicators can be collected, or different reporting periods can be used to report the collected channel indicator data.

[0228] S810, the OAM network element sends the sixth request to the RAN equipment.

[0229] The sixth request is used to request channel indicator data. The information carried in the sixth request is the same as that carried in the second request. For example, the sixth request carries the second reporting method, that is, instructing the RAN equipment to use user plane reporting.

[0230] S811, the RAN device sends channel indicator data of multiple terminal devices in the cell to the UPF network element.

[0231] Specifically, the RAN device can collect channel indicator data from multiple terminal devices within the cell according to the channel indicators, data reporting method, quantization level, reporting period, collection range or quantization method carried in the sixth request, and process and report the collected channel indicator data.

[0232] For example, the RAN device can collect the SINR, RANK, number of power control RBs, and maximum number of paired layers of multiple terminal devices in the cell. Then, it can collect the channel index data of multiple terminal devices in the cell according to the reporting period (e.g., 2s). At the end of the reporting period, it can report the channel index data of multiple terminal devices in the cell to the UPF network element through the header of the user plane part of GPRS tunneling protocol (GTP-U) data packet.

[0233] GTP-U defines an extension header for information transmission between RAN equipment and UPF network elements. Reporting channel indicator data at the user level requires a new extension header. Its format is defined in Table 3. The extension header can include multiple fields, including a UE Temporary Mobile Subscriber Identity (TMSI) field, a timestamp field, and a channel indicator field. These fields may also include a spare field and a next extension headertype field. Each field corresponds to one or more bytes.

[0234] After receiving a GTP-U data packet, the UPF network element parses the GTP-U data packet header and obtains the channel indicator data from the channel indicator field.

[0235] Table 3

[0236]

[0237] S812, the NWDAF network element sends a third request to the SMF network element.

[0238] The third request is used to notify the UPF network element to report the channel indicator data. The third request may include the address information of the NWDAF network element.

[0239] S813, the SMF network element sends a notification message to the UPF network element.

[0240] The notification information is used to notify the UPF network element to report channel indicator data through the user plane reporting method.

[0241] The notification information may include the address information of the NWDAF network element.

[0242] Among them, there is no specific order between S809-S811 and S812-S813. That is, the NWDAF network element can first request the SMF network element to notify the UPF network element to report channel indicator data, and then request the OAM network element to report channel indicator data through the user plane.

[0243] S814, the UPF network element sends channel indicator data of multiple terminal devices in the cell to the NWDAF network element.

[0244] Specifically, after the UPF network element parses the channel index data from the GTP-U data packet header, it sends the channel index data of multiple terminal devices in the cell to the NWDAF network element according to the address information of the NWDAF network element.

[0245] The S815 NWDAF network element determines the QoS policy for each of the multiple terminal devices based on user data and channel indicator data.

[0246] The specific implementation process of S815 and Figure 6 The specific implementation process of S602 in the illustrated embodiment is the same, and the specific implementation process of S815 can be referred to Figure 6 S602 in the illustrated embodiment will not be described again here.

[0247] S816, the NWDAF network element sends QoS policies to the PCF network element.

[0248] Optionally, the PCF network element can distribute QoS policies to terminal devices, enabling the terminal devices to communicate in accordance with the QoS policies.

[0249] In this embodiment, the NWDAF network element obtains user data from multiple terminal devices within the cell from the SMF network element and channel indicator data through user plane reporting or management plane reporting to determine the QoS policy for each terminal device. This ensures that, under limited network resources, the optimal QoS policy is selected and distributed to the terminal device, guaranteeing the user experience of the terminal device and avoiding mutual interference with other terminal devices.

[0250] It is understood that the methods and operations implemented by network devices (e.g., NWDAF network elements or the first network element) in the above-described method embodiments can also be implemented by components (e.g., chips or circuits) that can be used in network devices.

[0251] This application embodiment can divide the network device into functional modules according to the above method example. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware or software functional modules. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. The following description uses the division of functional modules according to each function as an example.

[0252] The above, combined with Figure 3 , Figure 5 , Figure 6 and Figure 8 The methods provided in the embodiments of this application are described in detail below. Figure 9 This application provides a detailed description of the communication device provided in its embodiments. It should be understood that the descriptions of the device embodiments correspond to the descriptions of the method embodiments; therefore, any content not described in detail here will be referred to the method embodiments above, and for the sake of brevity, will not be repeated here.

[0253] Please see Figure 9 , Figure 9 This is a schematic diagram of a communication device provided in an embodiment of this application. The communication device can implement the steps or processes executed by the network device (e.g., an NWDAF network element or a first network element) corresponding to the method embodiments described above. In one possible design, the communication device may include a transceiver module 901 and a processing module 902. Optionally, the communication device may further include a storage module for storing device program code and / or data.

[0254] The communication device can be a network-side device as described in the above embodiments, such as a network device or a communication module in a network device, or a circuit or chip in the network responsible for communication functions.

[0255] In one embodiment:

[0256] The transceiver module 901 is used to receive a first request from a first network element. The first request is used to request network evaluation. The first request includes a Quality of Service (QoS) policy and a target area. The first network element is a network element responsible for network function operation.

[0257] The transceiver module 901 is also configured to acquire call statistics data and user data of multiple terminal devices within the target area based on the first request;

[0258] The processing module 902 is used to determine the network evaluation parameters of each terminal device based on the call statistics data, the user data, and the QoS policy issued to each of the plurality of terminal devices. The network evaluation parameters are used to evaluate the network usage of terminal devices using different QoS policies.

[0259] In one possible design, the first request may also include rules for issuing QoS policies;

[0260] The processing module 902 is further configured to determine the QoS policy to be issued to each terminal device according to the QoS policy issuance rules.

[0261] In one possible design, the first request may also include the number of users to whom QoS policies are issued, and the different QoS policies include a first priority QoS policy and a second priority QoS policy.

[0262] The processing module 902 is further configured to determine a first number of terminal devices using the first priority QoS policy based on the number of users issued by the QoS policy; and to determine a second number of terminal devices using the second priority QoS policy based on the total number of the plurality of terminal devices and the first number.

[0263] Optionally, the transceiver module 901 is further configured to send a second request to a second network element, the second request including the target area, the second request being used to request the call statistics data within the target area, the second network element being a network element responsible for operation, management, and maintenance; and to receive the call statistics data within the target area from the second network element.

[0264] Optionally, the second request includes call statistics indicators corresponding to the requested call statistics data. The call statistics indicators include at least one of the following: the number of times the Reference Received Power (RSRP) measurement value on the Physical Uplink Shared Channel (PUSCH) falls within different intervals; the number of times the Signal-to-Noise Ratio (SINR) measurement value on the PUSCH falls within different intervals; the distribution of the user's spectral efficiency on the PUSCH falls within different intervals; the number of times the RSRP measurement value on the Physical Downlink Shared Channel (PDSCH) falls within different intervals; the number of times the SINR measurement value on the PDSCH falls within different intervals; or the distribution of the user's spectral efficiency on the PDSCH falls within different intervals.

[0265] Optionally, the second request may further include at least one of the following: a collection period or a statistical period, wherein the collection period is used to indicate the time interval for collecting the call statistics data, and the statistical period is used to indicate the time interval for statistically analyzing the call statistics data.

[0266] Optionally, the transceiver module 901 is further configured to send a third request, the third request including the target area, the third request being used to request the user data within the target area; and to receive the user data within the target area.

[0267] Optionally, the processing module 902 is further configured to determine the channel index of each terminal device based on the call statistics data, and to determine the service model of each terminal device based on the user data; and to determine the network evaluation parameters of each terminal device based on the channel index of each terminal device, the service model of each terminal device, and the QoS policy issued for each terminal device.

[0268] Optionally, the processing module 902 is further configured to determine the value of the call statistics index of each terminal device based on the call statistics data; and convert the value of the call statistics index into the channel index based on the mapping relationship between the value of the call statistics index and the channel index.

[0269] Optionally, the processing module 902 is further configured to determine, based on the call statistics data, the number of times the call statistics index of each terminal device is located in each interval; based on the number of times the call statistics index is located in each interval, determine the probability that the call statistics index of each terminal device is located in each interval; and based on the probability that the call statistics index is located in each interval, determine the value of the call statistics index of each terminal device.

[0270] Optionally, the processing module 902 is further configured to input the channel indicators of each terminal device, the service model of each terminal device, and the QoS policy issued to each terminal device into the simulation model to determine the network evaluation parameters of each terminal device.

[0271] Optionally, the transceiver module 901 is further configured to send an evaluation result to the first network element, the evaluation result including the network usage of terminal devices using different QoS policies.

[0272] Optionally, the network evaluation parameters include at least one of the following: throughput, latency, or packet loss rate.

[0273] In one possible design, when the communication device is an NWDAF network element or a communication module within an NWDAF network element, the functionality of the processing module 902 can be implemented by one or more processors. Specifically, the processor may include a modem chip, or a system-on-a-chip (SoC) chip or a SIP chip containing a modem core. The functionality of the transceiver module 901 can be implemented by transceiver circuitry.

[0274] In one possible design, when the communication device is a circuit or chip responsible for communication functions within an NWDAF network element, such as a modem chip or a system-on-a-chip (SoC) or SIP chip containing a modem core, the function of the processing module 902 can be implemented by a circuit system in the aforementioned chip that includes one or more processors or processor cores. The function of the transceiver module 901 can be implemented by the interface circuitry or data transceiver circuitry on the aforementioned chip.

[0275] It should be noted that the implementation of each module can also be referenced accordingly. Figure 3 and Figure 5 The corresponding description of the method embodiment shown describes the methods and functions performed by the NWDAF network element in the above embodiments.

[0276] In another embodiment:

[0277] The transceiver module 901 is used to send a first request to the network data analysis function network element. The first request is used to request network evaluation. The first request includes a Quality of Service (QoS) policy and a target area. The target area is used to indicate the acquisition of call statistics data and user data of multiple terminal devices. The QoS policy, the call statistics data, and the user data are used to determine the network evaluation parameters of each terminal device. The network evaluation parameters are used to evaluate the network usage of terminal devices using different QoS policies.

[0278] Optionally, the transceiver module 901 is also configured to receive evaluation results from the network data analysis function network element, the evaluation results including network usage of terminal devices using different QoS policies.

[0279] Optionally, the network evaluation parameters include at least one of the following: throughput, latency, or packet loss rate.

[0280] In one possible design, when the communication device is a first network element or a communication module within a first network element, the functionality of the processing module 902 can be implemented by one or more processors. Specifically, the processor may include a modem chip, or a system-on-a-chip (SoC) chip or a SIP chip containing a modem core. The functionality of the transceiver module 901 can be implemented by transceiver circuitry.

[0281] In one possible design, when the communication device is a circuit or chip responsible for communication functions in the first network element, such as a modem chip or a system-on-a-chip (SoC) or SIP chip containing a modem core, the function of the processing module 902 can be implemented by a circuit system in the aforementioned chip that includes one or more processors or processor cores. The function of the transceiver module 901 can be implemented by the interface circuit or data transceiver circuit on the aforementioned chip.

[0282] It should be noted that the implementation of each module can also be referenced accordingly. Figure 3 and Figure 5 The corresponding description of the method embodiment shown above executes the methods and functions performed by the first network element in the above embodiments.

[0283] In another embodiment:

[0284] Transceiver module 901 is used to acquire user data and channel indicator data from multiple terminal devices within the cell;

[0285] The processing module 902 is used to determine the QoS policy of each of the plurality of terminal devices based on the user data and the channel index data.

[0286] Optionally, the transceiver module 901 is further configured to send a first request to a first network element, the first request being used to request the channel index data, the first network element being a network element responsible for operation, management, and maintenance; and to receive the channel index data from the first network element.

[0287] Optionally, the first request carries a first reporting method, which is a management plane report.

[0288] Optionally, the first request may further include requested channel metrics, which include at least one of the following: scheduling signal-to-noise ratio (SINR), rank (RANK), number of power control resource blocks (RBs), maximum number of pairing layers, modulation and coding scheme (MCS), spectral efficiency, initial bit error rate (BER), or residual bit error rate (BER).

[0289] Optionally, the first request may further include at least one of the following: data reporting method, quantization level, reporting cycle, collection range, or quantization method.

[0290] Optionally, the transceiver module 901 is further configured to send a second request to a first network element, the second request being used to request the reporting of the channel indicator data via the user plane, wherein the first network element is a network element responsible for operation, management, and maintenance; send a third request to a second network element, the third request being used to notify a third network element to report the channel indicator data, wherein the second network element is a network element responsible for session management, and the third network element is a network element responsible for user plane data forwarding and reception; and receive the channel indicator data from the third network element.

[0291] Optionally, the second request carries a second reporting method, which is user-side reporting.

[0292] Optionally, the second request may also include requested channel metrics, which include at least one of the following: scheduling signal-to-noise ratio (SINR), rank (RANK), number of power control resource blocks (RBs), maximum number of pairing layers, modulation and coding scheme (MCS), spectral efficiency, initial bit error rate (BER), or residual bit error rate (BER).

[0293] Optionally, the second request may also include at least one of the following: data reporting method, quantization level, reporting cycle, collection range, or quantization method.

[0294] Optionally, the processing module 902 is further configured to determine the service model of each terminal device based on the user data;

[0295] The QoS policy for each terminal device is determined based on the user type, the service model, and the channel indicator data of each terminal device.

[0296] Optionally, the processing module 902 is further configured to input the user type of each terminal device, the service model of each terminal device, and the channel index data of each terminal device into the simulation model to determine the optimal QoS strategy among multiple candidate QoS strategies.

[0297] In one possible design, when the communication device is an NWDAF network element or a communication module within an NWDAF network element, the functionality of the processing module 902 can be implemented by one or more processors. Specifically, the processor may include a modem chip, or a system-on-a-chip (SoC) chip or a SIP chip containing a modem core. The functionality of the transceiver module 901 can be implemented by transceiver circuitry.

[0298] In one possible design, when the communication device is a circuit or chip responsible for communication functions within an NWDAF network element, such as a modem chip or a system-on-a-chip (SoC) or SIP chip containing a modem core, the function of the processing module 902 can be implemented by a circuit system in the aforementioned chip that includes one or more processors or processor cores. The function of the transceiver module 901 can be implemented by the interface circuitry or data transceiver circuitry on the aforementioned chip.

[0299] It should be noted that the implementation of each module can also be referenced accordingly. Figure 6 and Figure 8 The corresponding description of the method embodiment shown describes the methods and functions performed by the NWDAF network element in the above embodiments.

[0300] Figure 10 This is a schematic diagram of the structure of a network device provided in an embodiment of this application. This network device can be applied to, for example... Figure 1In the system shown, the functions of the network device (e.g., the first network element or NWDAF network element) in the above method embodiments are executed, or the steps or processes executed by the network device in the above method embodiments are implemented.

[0301] like Figure 10 As shown, the network device includes a processor 1001 and a transceiver 1002. Optionally, the network device also includes a memory 1003. The processor 1001, transceiver 1002, and memory 1003 can communicate with each other via internal connections to transmit control and / or data signals. The memory 1003 stores computer programs, and the processor 1001 retrieves and runs the computer programs from the memory 1003 to control the transceiver 1002 to transmit and receive signals. Optionally, the network device may also include an antenna for transmitting uplink data or uplink control signaling output by the transceiver 1002 via wireless signals.

[0302] The aforementioned processor 1001 can be with Figure 9 Corresponding to the processing module, the processor 1001 and the memory 1003 can be combined into a processing device. The processor 1001 is used to execute the program code stored in the memory 1003 to achieve the above functions. In specific implementation, the memory 1003 can be integrated into the processor 1001 or independent of the processor 1001.

[0303] The transceiver 1002 described above can be used with Figure 9 The transceiver module in this context can also be referred to as a transceiver unit. The transceiver 1002 may include a receiver (or receiver circuit) and a transmitter (or transmitter circuit). The receiver is used to receive signals, and the transmitter is used to transmit signals.

[0304] It should be understood that Figure 10 The network device shown can achieve Figure 3 , Figure 5 , Figure 6 and Figure 8 The methods illustrated in the embodiments involve various processes of the network device. The operations and / or functions of each module in the network device are respectively for implementing the corresponding processes in the above method embodiments. For details, please refer to the descriptions in the above method embodiments; to avoid repetition, detailed descriptions are appropriately omitted here.

[0305] The processor 1001 described above can be used to execute the actions implemented internally by the network device as described in the preceding method embodiments, while the transceiver 1002 can be used to execute the network device receiving or transmitting actions as described in the preceding method embodiments. Please refer to the descriptions in the preceding method embodiments for details, which will not be repeated here.

[0306] The processor 1001 can be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor 1001 can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, etc. The communication bus 1004 can be a peripheral component interconnect standard PCI bus or an extended industry standard structure EISA bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 10 The bus is represented by a single thick line, but this does not imply that there is only one bus or one type of bus. The communication bus 1004 is used to implement communication between these components. In this embodiment, the transceiver 1002 is used for signaling or data communication with other node devices. The memory 1003 may include volatile memory, such as nonvolatile random access memory (NVRAM), phase change RAM (PRAM), magnetoresistive RAM (MRAM), etc., and may also include nonvolatile memory, such as at least one disk storage device, electrically erasable programmable read-only memory (EEPROM), flash memory devices, such as NOR flash memory or NAND flash memory, semiconductor devices, such as solid-state disk (SSD), etc. Optionally, the memory 1003 may also be at least one storage device located remotely from the aforementioned processor 1001. Optionally, the memory 1003 may also store a set of computer program code or configuration information. Alternatively, the processor 1001 may also execute the program stored in the memory 1003. The processor can cooperate with the memory and transceiver to execute any of the methods and functions of the network device in the above embodiments.

[0307] This application also provides a chip system including a processor for supporting network devices to implement the functions involved in any of the above embodiments, such as generating or processing the QoS policies involved in the above methods.

[0308] In one possible design, the chip system may further include a memory for storing necessary computer programs and data for the network device. The chip system may be composed of chips or may include chips and other discrete components. The inputs and outputs of the chip system correspond to the receiving and transmitting operations of the network device in the method embodiment, respectively.

[0309] According to the method provided in the embodiments of this application, this application also provides a computer program product, which includes: a computer program that, when run on a computer, causes the computer to perform... Figure 3 , Figure 5 , Figure 6 and Figure 8 The method of any one of the embodiments shown.

[0310] According to the method provided in the embodiments of this application, this application also provides a computer-readable medium storing a computer program, which, when run on a computer, causes the computer to perform... Figure 3 , Figure 5 , Figure 6 and Figure 8 The method of any one of the embodiments shown.

[0311] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0312] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, The method includes: Receive a first request from a first network element, the first request being used to request network evaluation, the first request including a Quality of Service (QoS) policy and a target area, the first network element being a network element responsible for network function operation; Based on the first request, acquire call statistics data and user data of multiple terminal devices within the target area; Based on the call statistics data, the user data, and the QoS policies issued to each of the plurality of terminal devices, network evaluation parameters for each terminal device are determined. These network evaluation parameters are used to evaluate the network usage of terminal devices using different QoS policies.

2. The method as described in claim 1, characterized in that, The first request also includes QoS policy distribution rules, and the method further includes: Based on the QoS policy distribution rules, the QoS policy distributed to each terminal device is determined.

3. The method as described in claim 1, characterized in that, The first request also includes the number of users to whom QoS policies are issued, wherein the different QoS policies include a first-priority QoS policy and a second-priority QoS policy, and the method further includes: Based on the number of users issued by the QoS policy, determine the first number of terminal devices using the first priority QoS policy; Based on the total number of the plurality of terminal devices and the first number, a second number of terminal devices using the second priority QoS policy is determined.

4. The method according to any one of claims 1-3, characterized in that, The acquisition of call statistics data from multiple terminal devices within the target area includes: A second request is sent to a second network element, the second request including the target area, the second request being used to request the call statistics data within the target area, and the second network element being a network element responsible for operation, management, and maintenance; Receive the call statistics data within the target area from the second network element.

5. The method as described in claim 4, characterized in that, The second request includes call statistics indicators corresponding to the requested call statistics data. The call statistics indicators include at least one of the following: the number of times the Reference Received Power (RSRP) measurement value on the Physical Uplink Shared Channel (PUSCH) falls within different intervals; the number of times the Signal-to-Noise Ratio (SINR) measurement value on the PUSCH falls within different intervals; the distribution of the user's spectral efficiency on the PUSCH falls within different intervals; the number of times the RSRP measurement value on the Physical Downlink Shared Channel (PDSCH) falls within different intervals; the number of times the SINR measurement value on the PDSCH falls within different intervals; or the distribution of the user's spectral efficiency on the PDSCH falls within different intervals.

6. The method as described in claim 4 or 5, characterized in that, The second request further includes at least one of the following: a collection period or a statistical period, wherein the collection period is used to indicate the time interval for collecting the call statistics data, and the statistical period is used to indicate the time interval for statistically analyzing the call statistics data.

7. The method according to any one of claims 1-6, characterized in that, The acquisition of user data from multiple terminal devices within the target area includes: Send a third request, the third request including the target area, the third request being used to request the user data within the target area; Receive the user data within the target area.

8. The method according to any one of claims 1-7, characterized in that, The step of determining the network evaluation parameters for each terminal device based on the call statistics data, the user data, and the QoS policy issued to each of the plurality of terminal devices includes: The channel indicators of each terminal device are determined based on the call statistics data, and the service model of each terminal device is determined based on the user data; Based on the channel metrics of each terminal device, the service model of each terminal device, and the QoS policy issued to each terminal device, the network evaluation parameters of each terminal device are determined.

9. The method as described in claim 8, characterized in that, Determining the channel indicators of each terminal device based on the call statistics data includes: Based on the call statistics data, determine the value of the call statistics indicator for each terminal device; Based on the mapping relationship between the values ​​of the call statistics indicators and the channel indicators, the values ​​of the call statistics indicators are converted into the channel indicators.

10. The method as described in claim 9, characterized in that, The step of determining the value of the call statistics indicator for each terminal device based on the call statistics data includes: Based on the call statistics data, determine the number of times the call statistics index of each terminal device falls within each interval; Based on the number of times the call statistics index falls within each interval, determine the probability that the call statistics index of each terminal device falls within each interval; The value of the call statistics index for each terminal device is determined based on the probability that the call statistics index falls within each interval.

11. The method according to any one of claims 1-10, characterized in that, The step of determining the network evaluation parameters for each terminal device based on the call statistics data, the user data, and the QoS policy issued to each of the plurality of terminal devices includes: The simulation model is input with the channel metrics of each terminal device, the service model of each terminal device, and the QoS policy issued to each terminal device to determine the network evaluation parameters of each terminal device.

12. The method according to any one of claims 1-11, characterized in that, The method further includes: The evaluation results are sent to the first network element, and the evaluation results include the network usage of terminal devices using different QoS policies.

13. The method according to any one of claims 1-12, characterized in that, The network evaluation parameters include at least one of the following: throughput, latency, or packet loss rate.

14. A communication method, characterized in that, The method includes: A first request is sent to the network data analysis function network element. The first request is used to request network evaluation. The first request includes a Quality of Service (QoS) policy and a target area. The target area is used to indicate the acquisition of call statistics data and user data of multiple terminal devices. The QoS policy, the call statistics data, and the user data are used to determine the network evaluation parameters of each terminal device. The network evaluation parameters are used to evaluate the network usage of terminal devices using different QoS policies.

15. The method as described in claim 14, characterized in that, The method further includes: The network data analysis function receives evaluation results from the network element, including network usage of terminal devices using different QoS policies.

16. The method as described in claim 14 or 15, characterized in that, The network evaluation parameters include at least one of the following: throughput, latency, or packet loss rate.

17. A communication method, characterized in that, The method includes: Network data analysis functions allow network elements to acquire user data and channel indicator data from multiple terminal devices within the cell; The network data analysis function network element determines the QoS policy of each of the multiple terminal devices based on the user data and the channel indicator data.

18. The method as described in claim 17, characterized in that, The acquisition of channel indicator data from multiple terminal devices within the cell includes: A first request is sent to a first network element, the first request being used to request the channel index data, the first network element being a network element responsible for operation, management and maintenance; Receive the channel index data from the first network element.

19. The method as described in claim 18, characterized in that, The first request carries a first reporting method, which is a management-level report.

20. The method as described in claim 18 or 19, characterized in that, The first request also includes requested channel metrics, which include at least one of the following: scheduling signal-to-noise ratio (SINR), rank (RANK), number of power control resource blocks (RBs), maximum number of pairing layers, modulation and coding scheme (MCS), spectral efficiency, initial bit error rate (BER), or residual bit error rate (BER).

21. The method according to any one of claims 18-20, characterized in that, The first request also includes at least one of the following: data reporting method, quantization level, reporting cycle, collection range, or quantization method.

22. The method as described in claim 17, characterized in that, The acquisition of channel indicator data from multiple terminal devices within the cell includes: A second request is sent to the first network element, the second request being used to request the channel indicator data to be reported through the user plane, the first network element being the network element responsible for operation, management and maintenance; A third request is sent to the second network element, the third request being used to notify the third network element to report the channel indicator data. The second network element is the network element responsible for session management, and the third network element is the network element responsible for user plane data forwarding and receiving. Receive the channel index data from the third network element.

23. The method as described in claim 22, characterized in that, The second request carries a second reporting method, which is user-side reporting.

24. The method as described in claim 22 or 23, characterized in that, The second request also includes at least one of the following: the channel index of the request, the data reporting method, the number of quantization levels, the reporting period, the collection range, or the quantization method.

25. The method according to any one of claims 17-24, characterized in that, The network data analysis function element determines the QoS policy for each of the multiple terminal devices based on the user data and the channel indicator data, including: The service model for each terminal device is determined based on the user data; The QoS policy for each terminal device is determined based on the user type, the service model, and the channel indicator data of each terminal device.

26. The method as described in claim 25, characterized in that, The step of determining the QoS policy for each terminal device based on the user type, the service model, and the channel indicator data of each terminal device includes: The user type, service model, and channel index data of each terminal device are input into the simulation model to determine the optimal QoS strategy among multiple candidate QoS strategies.

27. A communication device, characterized in that, The device includes a memory and a processor, the memory being used to store a computer program, and the processor running the computer program to cause the communication device to perform the method of any one of claims 1-13, any one of claims 14-16, or any one of claims 17-26.

28. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a computer program that, when executed by a processor, causes the method of any one of claims 1-13, or any one of claims 14-16, or any one of claims 17-26 to be implemented.

29. A chip, characterized in that, The chip includes a processor and a communication interface, the communication interface being used to communicate with external or internal devices, and the processor being used to implement the method as described in any one of claims 1-13, or any one of claims 14-16, or any one of claims 17-26.

30. A computer program product containing instructions, characterized in that, When it is run on a computer, it causes the computer to perform the method of any one of claims 1-13, or any one of claims 14-16, or any one of claims 17-26.

Images