Method, nwdaF entity and communication system for providing QoS capabilities

Abstract

The present disclosure provides a method, a NWDAF entity and a communication system for providing QoS capability. The method for providing QoS capability comprises: obtaining QoS capability related data from a network entity after receiving a QoS capability analysis request sent by a task allocation entity; determining a QoS capability analysis result according to the QoS capability related data and pre-configuration information; and sending the QoS capability analysis result to the task allocation entity.

Description

Technical Field

[0001] This disclosure relates to the field of communications, and in particular to a method, NWDAF entity, and communication system for providing QoS capabilities. Background Technology

[0002] In recent years, AI (Artificial Intelligence) / ML (Machine Learning) applications have gradually increased, giving rise to federated learning and distributed learning methods. By breaking down an AI / ML task, a portion involving user privacy is performed on the terminal side first, and then the intermediate data / model is transmitted to the network side. This allows the computationally and energy-intensive parts of the task to be performed on the network side, thus ensuring user privacy while reducing the computational requirements of the devices.

[0003] Research indicates that different task splitting points place varying demands on network and device capabilities. Generally, the earlier the splitting point, the less computation the terminal bears; conversely, the later the splitting point, the lower the required data transfer rate. Therefore, when selecting AI / ML task splitting points (e.g., terminals, third-party servers, carrier cloud servers, or core network elements), factors such as network transmission capacity, terminal computing power, and the characteristics of the task itself must be considered simultaneously. Furthermore, in scenarios involving federated learning among group users, the selection of the user group for federated learning also requires support from network-side data. Summary of the Invention

[0004] The inventors noted that the 3GPP (3rd Generation Partnership Project) SA2 project proposal for AI / ML also includes a requirement for network support for AI / ML task splitting, requiring the network to expose network information related to AI / ML tasks to the nodes allocating these tasks to ensure their execution. This could lead to sensitive network information being directly exposed to user terminals (UEs) or third-party servers, posing a threat to network system information security.

[0005] Accordingly, this disclosure provides a scheme for providing QoS capabilities, which can reasonably utilize network resources to ensure the smooth execution of AI / ML tasks while ensuring that sensitive information on the network side is not leaked.

[0006] According to a first aspect of the present disclosure, a method for providing QoS capabilities is provided, comprising: after receiving a QoS capability analysis request sent by a task allocation entity, obtaining QoS capability-related data from a network entity; determining a QoS capability analysis result based on the QoS capability-related data and pre-configured information; and sending the QoS capability analysis result to the task allocation entity.

[0007] In some embodiments, obtaining QoS capability-related data from a network entity includes: determining whether the Data Storage Function (ADRF) entity or the Data Collection Coordination Function (DCCF) entity has QoS capability-related data; if neither the ADRF entity nor the DCCF entity has QoS capability-related data, then sending a data acquisition request to the network entity; and receiving the QoS capability-related data sent by the network entity.

[0008] In some embodiments, the network entity includes at least one of the following: Operation and Maintenance Management (OAM) entity, Access and Mobility Management Function (AMF) entity, Session Management Function (SMF) entity, Network Storage Function (NRF) entity, or User Plane Function (UPF) entity; the QoS capability-related data sent by the OAM entity includes radio network resource information; the QoS capability-related data sent by the AMF entity includes at least one of terminal behavior information and terminal mobility information; the QoS capability-related data sent by the SMF entity includes slice information and Protocol Data Unit (PDU) session information; the QoS capability-related data sent by the NRF entity includes network element status information; and the QoS capability-related data sent by the UPF entity includes user plane related information.

[0009] In some embodiments, if the ADRF entity or DCCF entity has QoS capability-related data, then the QoS capability-related data is extracted.

[0010] In some embodiments, sending the QoS capability analysis results to the task allocation entity includes: determining whether the task allocation entity is a trusted network entity; if the task allocation entity is a trusted network entity, then directly sending the QoS capability analysis results to the task allocation entity.

[0011] In some embodiments, if the task allocation entity is an untrusted network entity, the QoS capability analysis results are sent to the Network Open Function (NEF) entity so that the NEF entity can perform preset processing on the QoS capability analysis results and send the processing results to the task allocation entity.

[0012] In some embodiments, the QoS capability analysis results include at least one of the following: the target terminal's terminal identifier, the QoS capabilities provided to the target terminal, and the duration.

[0013] In some embodiments, QoS capabilities include at least one of 5G QoS level, guaranteed flow bit rate (GFBR), maximum flow bit rate (MFBR), and confidence level.

[0014] In some embodiments, the QoS capability analysis request includes at least one of analysis identifier, analysis filtering information, analysis report target, notification target address, data time window, and preferred analysis precision, wherein the analysis filtering information includes at least one of region of interest, single network slice selection aid information S-NSSAI, QoS level, GFBR, and MFBR.

[0015] According to a second aspect of the present disclosure, a Network Data Analysis Function (NWDAF) entity is provided, comprising: a first processing module configured to obtain QoS capability-related data from a network entity after receiving a QoS capability analysis request sent by a task allocation entity; a second processing module configured to determine a QoS capability analysis result based on the QoS capability-related data and pre-configured information; and a third processing module configured to send the QoS capability analysis result to the task allocation entity.

[0016] According to a third aspect of the present disclosure, an NWDAF entity is provided, comprising: a memory configured to store instructions; and a processor coupled to the memory, the processor being configured to execute instructions stored in the memory to implement the method as described in any of the above embodiments.

[0017] According to a fourth aspect of the present disclosure, a communication system is provided, comprising: an NWDAF entity as described in any of the above embodiments; a task allocation entity configured to send a QoS capability analysis request to the NWDAF entity and receive a QoS capability analysis result sent by the NWDAF entity; and a network entity configured to send corresponding QoS capability-related data to the NWDAF entity according to a data acquisition request sent by the NWDAF entity.

[0018] In some embodiments, the task allocation entity is configured to send a QoS capability analysis request to the NWDAF entity and receive the QoS capability analysis results from the NWDAF entity when it is a trusted network entity.

[0019] In some embodiments, the system further includes a NEF entity, wherein: the task allocation entity is configured to send a QoS capability analysis request to the NEF entity when it is an untrusted network entity, and is also configured to receive QoS capability analysis results sent by the NEF entity; the NEF entity is configured to send a QoS capability analysis request to an NWDAF entity and send the QoS capability analysis results sent by the NWDAF entity to the task allocation entity.

[0020] According to a fifth aspect of the present disclosure, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions that, when executed by a processor, implement the method as described in any of the above embodiments.

[0021] Other features and advantages of this disclosure will become clear from the following detailed description of exemplary embodiments with reference to the accompanying drawings. Attached Figure Description

[0022] To more clearly illustrate the technical solutions in the embodiments of this disclosure or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this disclosure. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0023] Figure 1 This is a flowchart illustrating a method for providing QoS capabilities according to an embodiment of this disclosure;

[0024] Figure 2 This is a schematic diagram of the structure of an NWDAF entity according to an embodiment of the present disclosure;

[0025] Figure 3 This is a schematic diagram of the structure of an NWDAF entity according to another embodiment of this disclosure;

[0026] Figure 4 This is a schematic diagram of the structure of a communication system according to an embodiment of the present disclosure;

[0027] Figure 5 This is a schematic diagram of the structure of a communication system according to another embodiment of the present disclosure;

[0028] Figure 6 This is a flowchart illustrating a method for providing QoS capabilities according to another embodiment of this disclosure. Detailed Implementation

[0029] The technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. The following description of at least one exemplary embodiment is merely illustrative and is in no way intended to limit this disclosure or its application or use. All other embodiments obtained by those skilled in the art based on the embodiments of this disclosure without creative effort are within the scope of protection of this disclosure.

[0030] Unless otherwise specifically stated, the relative arrangement, numerical expressions, and values ​​of the components and steps set forth in these embodiments do not limit the scope of this disclosure.

[0031] At the same time, it should be understood that, for ease of description, the dimensions of the various parts shown in the accompanying drawings are not drawn according to actual scale.

[0032] Techniques, methods, and equipment known to those skilled in the art may not be discussed in detail, but where appropriate, such techniques, methods, and equipment should be considered part of the specification.

[0033] In all examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not as limitations. Therefore, other examples of exemplary embodiments may have different values.

[0034] It should be noted that similar labels and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be discussed further in subsequent figures.

[0035] Figure 1 This is a flowchart illustrating a method for providing QoS (Quality of Service) capabilities according to an embodiment of this disclosure. In some embodiments, the following methods for providing QoS capabilities are performed by an NWDAF (Network Data Analytics Function) entity.

[0036] In step 101, after receiving the QoS capability analysis request sent by the task allocation entity, QoS capability-related data is obtained from the network entity.

[0037] It should be noted that if the task allocation entity is a trusted network entity, it will directly send the QoS capability analysis request to the NWDAF entity. If the task allocation entity is an untrusted network entity, it will send the QoS capability analysis request to the NWDAF entity through the NEF (Network Exposure Function) entity.

[0038] In some embodiments, the QoS capability analysis request includes at least one of analysis identifier, analysis filtering information, analysis report target, notification target address, data time window, and preferred analysis precision, wherein the analysis filtering information includes at least one of region of interest, S-NSSAI (Single Network Slice Selection Assistance Information), QoS level, GFBR (Guaranteed Flow Bit Rate), and MFBR (Maximum Flow Bit Rate).

[0039] For example, the contents included in a QoS capability analysis request are shown in Table 1.

[0040]

[0041] Table 1

[0042] In some embodiments, the steps of obtaining QoS capability-related data from network entities include:

[0043] First, determine whether the ADRF (Analytics Data Repository Function) or DCCF (Data Collection Coordination Function) entity contains QoS-related data.

[0044] Next, if neither the ADRF entity nor the DCCF entity has QoS capability-related data, a data acquisition request is sent to the network entity in order to receive the QoS capability-related data sent by the network entity.

[0045] In some embodiments, if the ADRF entity or DCCF entity has QoS capability-related data, the QoS capability-related data is extracted directly from the ADRF entity or DCCF entity. In this case, it is not necessary to obtain the QoS capability-related data from the network entity.

[0046] In some embodiments, the network entity includes at least one of the following: OAM (Operation Administration and Maintenance) entity, AMF (Access and Mobility Management Function) entity, SMF (Session Management Function) entity, NRF (Network Repository Function) entity, or UPF (User Plane Function) entity.

[0047] For example, the QoS capability-related data sent by the OAM entity includes wireless network resource information; the QoS capability-related data sent by the AMF entity includes at least one of terminal behavior information and terminal mobility information; the QoS capability-related data sent by the SMF entity includes slice information and PDU (Protocol Data Unit) session information; the QoS capability-related data sent by the NRF entity includes network element status information; and the QoS capability-related data sent by the UPF entity includes user plane related information.

[0048] For example, QoS capability-related data obtained from network entities are shown in Table 2.

[0049]

[0050]

[0051] Table 2

[0052] In step 102, the QoS capability analysis results are determined based on the QoS capability-related data and pre-configured information.

[0053] It should be noted that the NWDAF entity performs data analysis based on QoS capability-related data and pre-configured information, thereby hiding the corresponding sensitive information and determining the QoS capability analysis results that can be provided to the target UE without affecting other services.

[0054] In step 103, the QoS capability analysis results are sent to the task allocation entity.

[0055] In some embodiments, the step of sending the QoS capability analysis results to the task allocation entity includes:

[0056] First, determine whether the task assignment entity is a trusted network entity.

[0057] Next, if the task allocation entity is a trusted network entity, the QoS capability analysis results will be sent directly to the task allocation entity.

[0058] If the task allocation entity is an untrusted network entity, the QoS capability analysis results are sent to the NEF entity so that the NEF entity can perform preset processing on the QoS capability analysis results and send the processing results to the task allocation entity.

[0059] In some embodiments, the QoS capability analysis results include at least one of the following: the target terminal's terminal identifier, the QoS capabilities provided to the target terminal, and the duration.

[0060] For example, QoS capabilities include at least one of 5G QoS level, GFBR, MFBR, and confidence level.

[0061] For example, the contents included in the QoS capability analysis results are shown in Table 3.

[0062]

[0063]

[0064] Table 3

[0065] In the method for providing QoS capabilities provided in the above embodiments of this disclosure, data analysis is performed based on QoS capability-related data and pre-configured information to hide the corresponding sensitive information and determine the QoS capability analysis results that can be provided to the target UE without affecting other services.

[0066] Figure 2 This is a schematic diagram of the structure of an NWDAF entity according to an embodiment of this disclosure. Figure 2 As shown, the NWDAF entity includes a first processing module 21, a second processing module 22, and a third processing module 23.

[0067] The first processing module 21 is configured to obtain QoS capability-related data from the network entity after receiving a QoS capability analysis request sent by the task allocation entity.

[0068] It should be noted that if the task allocation entity is a trusted network entity, it will directly send the QoS capability analysis request to the NWDAF entity. If the task allocation entity is an untrusted network entity, it will send the QoS capability analysis request to the NWDAF entity through the NEF entity.

[0069] In some embodiments, the QoS capability analysis request includes at least one of analysis identifier, analysis filtering information, analysis report target, notification target address, data time window, and preferred analysis precision, wherein the analysis filtering information includes at least one of region of interest, S-NSSAI, QoS level, GFBR, and MFBR.

[0070] In some embodiments, the first processing module 21 first determines whether the ADRF entity or the DCCF entity has QoS capability-related data. If neither the ADRF entity nor the DCCF entity has QoS capability-related data, the first processing module 21 sends a data acquisition request to the network entity in order to receive the QoS capability-related data sent by the network entity.

[0071] In some embodiments, if the ADRF entity or DCCF entity contains QoS capability-related data, the first processing module 21 directly extracts the QoS capability-related data from the ADRF entity or DCCF entity. In this case, the first processing module 21 does not need to obtain the QoS capability-related data from the network entity.

[0072] In some embodiments, the network entity includes at least one of the following: OAM entity, AMF entity, SMF entity, NRF entity, or UPF entity.

[0073] For example, the QoS capability-related data sent by the OAM entity includes wireless network resource information; the QoS capability-related data sent by the AMF entity includes at least one of terminal behavior information and terminal mobility information; the QoS capability-related data sent by the SMF entity includes slice information and PDU session information; the QoS capability-related data sent by the NRF entity includes network element status information; and the QoS capability-related data sent by the UPF entity includes user plane related information.

[0074] The second processing module 22 is configured to determine the QoS capability analysis results based on QoS capability-related data and pre-configured information.

[0075] It should be noted that the NWDAF entity performs data analysis based on QoS capability-related data and pre-configured information, thereby hiding the corresponding sensitive information and determining the QoS capability analysis results that can be provided to the target UE without affecting other services.

[0076] The third processing module 23 is configured to send the QoS capability analysis results to the task allocation entity.

[0077] In some embodiments, the third processing module 23 determines whether the task allocation entity is a trusted network entity. If the task allocation entity is a trusted network entity, the third processing module 23 directly sends the QoS capability analysis result to the task allocation entity. If the task allocation entity is an untrusted network entity, the third processing module 23 sends the QoS capability analysis result to the NEF entity so that the NEF entity can perform preset processing on the QoS capability analysis result and send the processing result to the task allocation entity.

[0078] In some embodiments, the QoS capability analysis results include at least one of the following: the target terminal's terminal identifier, the QoS capabilities provided to the target terminal, and the duration.

[0079] For example, QoS capabilities include at least one of 5G QoS level, GFBR, MFBR, and confidence level.

[0080] Figure 3 This is a schematic diagram of the structure of an NWDAF entity according to another embodiment of this disclosure. Figure 3 As shown, the NWDAF entity includes a memory 31 and a processor 32.

[0081] Memory 31 is used to store instructions, and processor 32 is coupled to memory 31. Processor 32 is configured to execute instructions based on memory storage, as shown in the example. Figure 1 The method involved in any of the embodiments.

[0082] like Figure 3 As shown, the NWDAF entity also includes a communication interface 33 for exchanging information with other devices. Additionally, the NWDAF entity includes a bus 34, through which the processor 32, communication interface 33, and memory 31 communicate with each other.

[0083] The memory 31 may include high-speed RAM, and may also include non-volatile memory, such as at least one disk storage device. The memory 31 may also be a memory array. The memory 31 may also be divided into blocks, and the blocks may be combined into virtual volumes according to certain rules.

[0084] Furthermore, processor 32 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present disclosure.

[0085] This disclosure also relates to a computer-readable storage medium storing computer instructions that, when executed by a processor, implement... Figure 1 The method involved in any of the embodiments.

[0086] Figure 4 This is a schematic diagram of the structure of a communication system according to an embodiment of this disclosure. Figure 4 As shown, the communication system includes a task allocation entity 41, an NWDAF entity 42, and a network entity 43. The NWDAF entity 42 is... Figure 2 or Figure 3 The NWDAF entity involved in any of the embodiments.

[0087] The task allocation entity 41 is configured to send a QoS capability analysis request to the NWDAF entity 42 and receive the QoS capability analysis results sent by the NWDAF entity 42.

[0088] Network entity 43 is configured to send the corresponding QoS capability-related data to NWDAF entity 42 in response to the data acquisition request sent by NWDAF entity 42.

[0089] Figure 5 This is a schematic diagram of the structure of a communication system according to another embodiment of the present disclosure. Figure 5 and Figure 4 The difference is that, in Figure 5 In the illustrated embodiment, the communication system also includes NEF entity 44.

[0090] In some embodiments, if the task allocation entity 41 is a trusted network entity, it sends a QoS capability analysis request to the NWDAF entity 42 and receives the QoS capability analysis result from the NWDAF entity 42.

[0091] In some embodiments, if the task allocation entity 41 is an untrusted network entity, it sends a QoS capability analysis request to the NEF entity 44, which in turn sends the QoS capability analysis request to the NWDAF entity 42.

[0092] In addition, NEF entity 44 sends the QoS capability analysis results sent by NWDAF entity 42 to task allocation entity 41, and task allocation entity 41 receives the QoS capability analysis results sent by NEF entity 44.

[0093] Figure 6 This is a flowchart illustrating a method for providing QoS capabilities according to another embodiment of this disclosure.

[0094] In step 61a, if the task allocation entity is a trusted network entity, the task allocation entity directly sends the QoS capability analysis request to the NWDAF entity.

[0095] In step 61b1, if the task allocation entity is an untrusted network entity, the task allocation entity sends a QoS capability analysis request to the NEF entity.

[0096] In step 61b2, the NEF entity sends a QoS capability analysis request to the NWDAF entity.

[0097] In some embodiments, the QoS capability analysis request includes at least one of analysis identifier, analysis filtering information, analysis report target, notification target address, data time window, and preferred analysis precision, wherein the analysis filtering information includes at least one of region of interest, S-NSSAI, QoS level, GFBR, and MFBR.

[0098] In step 62, after receiving the QoS capability analysis request, the NWDAF entity determines whether the ADRF entity or the DCCF entity has QoS capability-related data.

[0099] In step 63, if neither the ADRF entity nor the DCCF entity has QoS capability-related data, the NWDAF entity sends a data acquisition request to the network entity.

[0100] In step 64, the network entity sends QoS capability-related data to the NWDAF entity.

[0101] In some embodiments, the network entity includes at least one of the following: OAM entity, AMF entity, SMF entity, NRF entity, or UPF entity.

[0102] For example, the QoS capability-related data sent by the OAM entity includes wireless network resource information; the QoS capability-related data sent by the AMF entity includes at least one of terminal behavior information and terminal mobility information; the QoS capability-related data sent by the SMF entity includes slice information and PDU session information; the QoS capability-related data sent by the NRF entity includes network element status information; and the QoS capability-related data sent by the UPF entity includes user plane related information.

[0103] In step 65, the NWDAF entity determines the QoS capability analysis results based on QoS capability-related data and pre-configured information.

[0104] It should be noted that the NWDAF entity performs data analysis based on QoS capability-related data and pre-configured information, thereby hiding the corresponding sensitive information and determining the QoS capability analysis results that can be provided to the target UE without affecting other services.

[0105] In step 66a, if the task allocation entity is a trusted network entity, the NWDAF entity sends the QoS capability analysis results to the task allocation entity.

[0106] In step 66b1, if the task allocation entity is an untrusted network entity, the NWDAF entity sends the QoS capability analysis results to the NEF entity.

[0107] In step 66b2, the NEF entity performs preset processing on the QoS capability analysis results and sends the processing results to the task allocation entity.

[0108] In some embodiments, the QoS capability analysis results include at least one of the following: the target terminal's terminal identifier, the QoS capabilities provided to the target terminal, and the duration.

[0109] For example, QoS capabilities include at least one of 5G QoS level, GFBR, MFBR, and confidence level.

[0110] By implementing the above embodiments of this disclosure, the following beneficial effects can be obtained:

[0111] 1. This disclosure can effectively assist in completing AI / ML tasks by selectively opening up some network information to the necessary AI / ML task allocation nodes (network elements / third-party servers / carrier cloud servers / UEs, etc.), enabling them to make decisions on AI / ML task splitting points and select UEs for federated learning task groups based on network information.

[0112] 2. This disclosure meets the requirements of AI / ML tasks without fully exposing network information, and the limited and controllable open network resources can effectively help operators monitor and manage both network resources and AI / ML tasks.

[0113] In some embodiments, the functional units described above may be implemented as general-purpose processors, programmable logic controllers (PLCs), digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or any suitable combination thereof for performing the functions described herein.

[0114] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0115] The description in this disclosure is provided for illustrative and descriptive purposes only and is not intended to be exhaustive or to limit the disclosure to its forms. Many modifications and variations will be apparent to those skilled in the art. The embodiments were chosen and described in order to better illustrate the principles and practical application of this disclosure and to enable those skilled in the art to understand this disclosure and to design various embodiments with various modifications suitable for a particular purpose.

Claims

1. A method for providing QoS capabilities, comprising: After receiving a QoS capability analysis request from the task allocation entity, obtain QoS capability-related data from the network entity; Based on the QoS capability-related data and pre-configuration information, the QoS capability analysis result is determined. The QoS capability analysis result is used to inform the task allocation entity what level of QoS support the network can provide. The QoS capability analysis result includes the QoS capabilities provided for the target terminal. The QoS capabilities include at least one of 5G QoS level, guaranteed flow bit rate GFBR, maximum flow bit rate MFBR, and confidence level. The QoS capability analysis results are sent to the task allocation entity.

2. The method according to claim 1, wherein, The QoS capability-related data obtained from network entities includes: Determine whether the data storage function ADRF entity or the data collection coordination function DCCF entity contains the QoS capability-related data. If neither the ADRF entity nor the DCCF entity has the QoS capability-related data, a data acquisition request is sent to the network entity. Receive the QoS capability-related data sent by the network entity.

3. The method according to claim 1, wherein, The network entity includes at least one of the following: Operation and Maintenance Management (OAM) entity, Access and Mobility Management Function (AMF) entity, Session Management Function (SMF) entity, Network Storage Function (NRF) entity, or User Plane Function (UPF) entity; The QoS capability-related data sent by the OAM entity includes wireless network resource information; The QoS capability-related data sent by the AMF entity includes at least one of terminal behavior information and terminal mobility information; The QoS capability-related data sent by the SMF entity includes slice information and Protocol Data Unit (PDU) session information; The QoS capability-related data sent by the NRF entity includes network element status information; The QoS capability-related data sent by the UPF entity includes user plane related information.

4. The method according to claim 2, further comprising: If the ADRF entity or the DCCF entity contains the QoS capability-related data, then the QoS capability-related data is extracted.

5. The method according to claim 1, wherein, Sending the QoS capability analysis results to the task allocation entity includes: Determine whether the task allocation entity is a trusted network entity; If the task allocation entity is a trusted network entity, the QoS capability analysis results are sent directly to the task allocation entity.

6. The method according to claim 5, further comprising: If the task allocation entity is an untrusted network entity, the QoS capability analysis result is sent to the Network Open Function (NEF) entity so that the NEF entity can perform preset processing on the QoS capability analysis result and send the processing result to the task allocation entity.

7. The method according to claim 1, wherein, The QoS capability analysis results also include at least one of the target terminal's terminal identifier and duration.

8. The method according to any one of claims 1-7, wherein, The QoS capability analysis request includes at least one of the following: analysis identifier, analysis filtering information, analysis report target, notification target address, data time window, and preferred analysis precision. The analysis filtering information includes at least one of the following: region of interest, single network slice selection aid information (S-NSSAI), QoS level, GFBR, and MFBR.

9. A Network Data Analysis Function (NWDAF) entity, comprising: The first processing module is configured to obtain QoS capability-related data from the network entity after receiving a QoS capability analysis request sent by the task allocation entity. The second processing module is configured to determine the QoS capability analysis result based on the QoS capability related data and pre-configured information. The QoS capability analysis result is used to inform the task allocation entity what level of QoS support the network can provide. The QoS capability analysis result includes the QoS capabilities provided for the target terminal. The QoS capabilities include at least one of 5G QoS level, guaranteed flow bit rate GFBR, maximum flow bit rate MFBR, and confidence level. The third processing module is configured to send the QoS capability analysis results to the task allocation entity.

10. A Network Data Analysis Function (NWDAF) entity, comprising: The memory is configured to store instructions; A processor, coupled to memory, configured to implement the method as described in any one of claims 1-8 based on memory-stored instruction execution.

11. A communication system, comprising: The NWDAF entity as described in claim 9 or 10; The task allocation entity is configured to send a QoS capability analysis request to the NWDAF entity and receive a QoS capability analysis result sent by the NWDAF entity. The QoS capability analysis result is used to inform the task allocation entity what level of QoS support the network can provide. The QoS capability analysis result includes the QoS capabilities provided for the target terminal. The QoS capabilities include at least one of 5G QoS level, guaranteed flow bit rate GFBR, maximum flow bit rate MFBR, and confidence level. The network entity is configured to send corresponding QoS capability-related data to the NWDAF entity based on the data acquisition request sent by the NWDAF entity.

12. The system according to claim 11, wherein, The task allocation entity is configured to send a QoS capability analysis request to the NWDAF entity and receive the QoS capability analysis result from the NWDAF entity when it is a trusted network entity.

13. The system of claim 11, further comprising a NEF entity, wherein: The task allocation entity is configured to send a QoS capability analysis request to the NEF entity when it is an untrusted network entity, and is also configured to receive the QoS capability analysis result sent by the NEF entity. The NEF entity is configured to send the QoS capability analysis request to the NWDAF entity and send the QoS capability analysis result sent by the NWDAF entity to the task allocation entity.

14. A non-transient computer-readable storage medium, wherein, A computer-readable storage medium stores computer instructions that, when executed by a processor, implement the method as described in any one of claims 1-8.

Images