Communication method and device

Abstract

The invention provides a communication method and device, and relates to the technical field of communication. In the method, an application network element can request a core network element (such as a network open network element or a user plane network element) to send indication information of service quality configuration to the application network element through a user plane path. Subsequently, the core network element can indicate whether the indication information of the service quality configuration can be sent through the user plane path to the application network element based on the request of the application network element. Through the method, the application network element and the core network element can negotiate the sending mode of the indication information of the service quality configuration based on the demand of the application network element, so that the wireless access network node determines which mode is adopted to send the indication information to the application network element.

Description

Technical Field

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

[0002] In a communication system, radio access network (RAN) nodes can obtain a Quality of Service (QoS) profile based on the network status and send corresponding indication information to application network elements to specify the QoS profile. Subsequently, the application network elements can determine the task scheduling result corresponding to the QoS profile and execute the task based on the scheduling result. In this process, because the QoS profile is related to the task scheduling result, the quality of service provided by the network can meet the QoS requirements of the task, thereby ensuring a good user experience.

[0003] Currently, RAN nodes can send the above-mentioned indication information to application network elements in various ways. However, which specific method the RAN node uses to send the indication information is still an issue that urgently needs to be resolved. Summary of the Invention

[0004] This application provides a communication method and apparatus that enables RAN nodes to determine which method to use to send service quality configuration indication information to application network elements.

[0005] To achieve the above objectives, this application adopts the following technical solution:

[0006] Firstly, a communication method is provided, which can be executed by a first network element in the core network. Here, the first network element can refer to the network element itself, or to a processor, circuit, module, logic node, chip, or chip system within the first network element that implements the method. For example, the first network element can be a network open element, a user plane element, or a newly added core network element.

[0007] The method includes: receiving first information from an application network element and sending second information to the application network element. The first information indicates that service quality configuration information can be sent to the application network element via a user plane path. The second information indicates that service quality configuration information can be sent to the application network element via a user plane path, or that service quality configuration information cannot be sent to the application network element via a user plane path.

[0008] Based on the method provided in the first aspect above, the first network element and the application network element can negotiate whether to send service quality configuration indication information to the application network element through the user plane path, based on the application network element's needs. Therefore, the method provided in the first aspect above enables the radio access network node to determine which method to use to send service quality configuration indication information to the application network element.

[0009] In one possible implementation, the first information includes one or more of the following: first indication information or identification information of at least one service flow. The first indication information is used to indicate the granularity of the indication information for the quality of service configuration sent via the user plane path, and the at least one service flow is a service flow associated with the indication information for the quality of service configuration sent via the user plane path.

[0010] Based on the above possible implementations, if the first information includes first indication information, the first network element can determine the granularity of the indication information for the service quality configuration requested by the application network element to be sent through the user plane path. If the first information includes identification information of at least one service flow, the first network element can determine which service flow-related indication information the application network element requests to be sent through the user plane path.

[0011] In one possible implementation, the second information includes identification information of the first service flow, which belongs to at least one service flow; the second information is used to indicate that service quality configuration can be sent to the application network element through the user plane path, including: the second information is used to indicate that service quality configuration associated with the first service flow can be sent to the application network element through the user plane path; the second information is used to indicate that service quality configuration cannot be sent to the application network element through the user plane path, including: the second information is used to indicate that service quality configuration associated with the first service flow cannot be sent to the application network element through the user plane path.

[0012] Based on the above possible implementation methods, the indication information for determining the quality of service configuration associated with the first service flow by the application network element can be sent through the user plane path, or the indication information for determining the quality of service configuration associated with the first service flow cannot be sent through the user plane path.

[0013] In one possible implementation, the granularity of the quality of service configuration indication information sent via the user plane path is either a quality of service stream or an Internet protocol stream.

[0014] Based on the above possible implementation methods, the first network element can determine that the application network element request is sent with the QoS flow as the granularity, and the QoS configuration indication information is sent through the user plane path. Alternatively, the first network element can determine that the application network element request is sent with the Internet Protocol flow as the granularity, and the QoS configuration indication information is sent through the user plane path.

[0015] In one possible implementation, the method further includes: sending third information to a second network element in the core network based on first information, the third information indicating whether service quality configuration can be sent to the application network element via a user plane path; receiving fourth information from the second network element, the fourth information indicating whether service quality configuration can be sent to the application network element via a user plane path, or the fourth information indicating whether service quality configuration cannot be sent to the application network element via a user plane path; when the fourth information indicates that service quality configuration can be sent to the application network element via a user plane path, the second information indicates that service quality configuration can be sent to the application network element via a user plane path; when the fourth information indicates that service quality configuration cannot be sent to the application network element via a user plane path, the second information indicates that service quality configuration cannot be sent to the application network element via a user plane path.

[0016] Based on the above possible implementation methods, the first network element can request the second network element to confirm whether it can send service quality configuration indication information to the application network element through the user plane path.

[0017] In one possible implementation, the third information indication confirms whether service quality configuration indication information can be sent to the application network element through the user plane path, including: the third information indication confirms whether the node on the user plane path can send service quality configuration indication information to the application network element.

[0018] Based on the above possible implementation methods, the first network element can request the second network element to confirm whether the nodes on the user plane path can send service quality configuration indication information to the application network element.

[0019] In one possible implementation, the first information is carried in a subscription request message or a Hypertext Transfer Protocol (HTTP) POST request message.

[0020] Based on the above possible implementation methods, the first network element can receive the first information through a subscription request message or a Hypertext Transfer Protocol POST request message.

[0021] In one possible implementation, the first information also indicates that service quality configuration information be sent to the terminal via air interface signaling.

[0022] Based on the above possible implementation methods, the first network element and the application network element can also negotiate whether to send service quality configuration indication information to the terminal through air interface signaling.

[0023] In one possible implementation, the first network element is a user plane network element, and the second information is used to indicate that service quality configuration can be sent to the application network element through the user plane path. The method further includes: receiving service quality configuration indication information associated with a first service quality flow from a radio access network node; and sending service quality configuration indication information associated with a first Internet Protocol flow to the application network element, wherein the first service quality flow and the first Internet Protocol flow have a mapping relationship.

[0024] Based on the above possible implementation methods, after receiving the indication information of the quality of service configuration associated with the first quality of service flow, the first network element can map the first quality of service flow to the first Internet Protocol flow, so as to provide the application network element with the indication information of the quality of service configuration associated with the first Internet Protocol flow.

[0025] In one possible implementation, the user plane path includes a user plane channel between a radio access network node and a user plane network element, as well as a user plane channel or application programming interface between a user plane network element and an application network element.

[0026] Based on the above possible implementation methods, the first network element and the application network element can negotiate whether the service quality configuration indication information can be sent through the user plane channel between the radio access network node and the user plane network element, as well as the user plane channel or application programming interface between the user plane network element and the application network element.

[0027] Secondly, a communication method is provided, which can be executed by an application network element. Here, "application network element" can refer to the application network element itself, or to processors, circuits, modules, logic nodes, chips, or chip systems within the application network element that implement the method.

[0028] The method includes: sending first information to a first network element in the core network, and receiving second information from the first network element. The first information indicates that quality of service (QoS) configuration information can be sent to the application network element via a user plane path. The second information indicates either that QoS configuration information can be sent to the application network element via a user plane path, or that QoS configuration information cannot be sent to the application network element via a user plane path.

[0029] Based on the method provided in the second aspect above, the first network element and the application network element can negotiate whether to send a quality of service (QoS) configuration indication information to the application network element through the user plane path, based on the application network element's needs. Therefore, the method provided in the second aspect above enables the radio access network node to determine which method to use to send the QoS configuration indication information to the application network element.

[0030] In one possible implementation, the first information includes one or more of the following: first indication information or identification information of at least one service flow; wherein the first indication information is used to indicate the granularity of the indication information of the quality of service configuration sent through the user plane path, and at least one service flow is a service flow associated with the indication information of the quality of service configuration sent through the user plane path.

[0031] Based on the above possible implementations, if the first information includes first indication information, the granularity of the indication information for the quality of service configuration sent through the user plane path can be indicated to the first network element. If the first information includes identification information for at least one service flow, the indication information for which service flows are associated with the quality of service configuration can be indicated to the first network element through the user plane path.

[0032] In one possible implementation, the second information includes identification information of the first service flow, which belongs to at least one service flow; the second information is used to indicate that service quality configuration can be sent to the application network element through the user plane path, including: the second information is used to indicate that service quality configuration associated with the first service flow can be sent to the application network element through the user plane path; the second information is used to indicate that service quality configuration cannot be sent to the application network element through the user plane path, including: the second information is used to indicate that service quality configuration associated with the first service flow cannot be sent to the application network element through the user plane path.

[0033] Based on the above possible implementation methods, the application network element can determine whether the indication information of the quality of service configuration associated with the first service flow can be sent through the user plane path, or whether the indication information of the quality of service configuration associated with the first service flow cannot be sent through the user plane path.

[0034] In one possible implementation, the granularity of the quality of service configuration indication information sent via the user plane path is either a quality of service stream or an Internet protocol stream.

[0035] Based on the above possible implementations, the application network element can request the transmission of quality of service (QoS) configuration indication information at the granularity of QoS flow through the user plane path. Alternatively, the application network element can request the transmission of QoS configuration indication information at the granularity of Internet Protocol (IP) flow through the user plane path.

[0036] In one possible implementation, the first information is carried in a subscription request message or a Hypertext Transfer Protocol (HTTP) POST request message.

[0037] Based on the above possible implementation methods, the application network element can send the first information through a subscription request message or a Hypertext Transfer Protocol POST request message.

[0038] In one possible implementation, the first information also indicates that service quality configuration information be sent to the terminal via air interface signaling.

[0039] Based on the above possible implementation methods, the first network element and the application network element can also negotiate whether to send service quality configuration indication information to the terminal through air interface signaling.

[0040] In one possible implementation, the first network element is either a user plane network element or a network open network element.

[0041] Based on the above possible implementation methods, the application network element can negotiate with the user plane network element or the network open network element whether to send service quality configuration instruction information to the application network element through the user plane path.

[0042] In one possible implementation, the user plane path includes a user plane channel between a radio access network node and a user plane network element, as well as a user plane channel or application programming interface between a user plane network element and an application network element.

[0043] Based on the above possible implementation methods, the first network element and the application network element can negotiate whether the service quality configuration indication information can be sent through the user plane channel between the radio access network node and the user plane network element, as well as the user plane channel or application programming interface between the user plane network element and the application network element.

[0044] Thirdly, a communication method is provided, which can be executed by a second network element in the core network. Here, the second network element can refer to the second network element itself, or to a processor, circuit, module, logical node, chip, or chip system within the second network element that implements the method. For example, the second network element may be a session management network element, or a newly added core network element.

[0045] The method includes: receiving third information from a first network element in the core network, the third information indicating whether service quality configuration indication information can be sent to an application network element via a user plane path; sending fifth information to a third network element based on the third information, the fifth information indicating that the third network element can send service quality configuration indication information to the application network element via a user plane path; receiving sixth information from the third network element, the sixth information indicating whether the third network element can send service quality configuration indication information to the application network element via a user plane path, or the sixth information indicating whether the third network element cannot send service quality configuration indication information to the application network element via a user plane path; and sending seventh information to a fourth network element based on the third information. The seventh information instructs the fourth network element to send a quality of service (QoS) configuration instruction to the application network element via a user plane path; receives an eighth information from the fourth network element, the eighth information indicating that the fourth network element can send the QoS configuration instruction to the application network element via a user plane path, or the eighth information indicating that the fourth network element cannot send the QoS configuration instruction to the application network element via a user plane path; and sends a fourth information to the first network element based on the sixth and eighth information, the fourth information indicating that the QoS configuration instruction can be sent to the application network element via a user plane path, or the fourth information indicating that the QoS configuration instruction cannot be sent to the application network element via a user plane path.

[0046] Based on the method provided in the third aspect above, the second network element can negotiate with the third and fourth network elements respectively, based on the instructions of the first network element, whether to send service quality configuration instruction information to the application network element through the user plane path, and indicate the negotiation result to the first network element so that the first network element can notify the application network element of the negotiation result.

[0047] In one possible implementation, the third information includes one or more of the following: second indication information or identification information of at least one service flow; wherein the second indication information is used to indicate the granularity of the indication information of the quality of service configuration sent through the user plane path, and the at least one service flow is a service flow associated with the indication information of the quality of service configuration sent through the user plane path.

[0048] Based on the above possible implementations, if the third information includes the second indication information, the second network element can determine the granularity of the indication information for the service quality configuration requested by the application network element to be sent through the user plane path. If the third information includes the identification information of at least one service flow, the second network element can determine which service flow-related indication information the application network element requests to be sent through the user plane path.

[0049] In one possible implementation, the sixth information includes identification information of the second service flow, which belongs to the at least one service flow; the sixth information is used to indicate that the third network element can send service quality configuration indication information to the application network element through the user plane path, including: the sixth information is used to indicate that the third network element can send service quality configuration indication information associated with the second service flow to the application network element through the user plane path; the sixth information is used to indicate that the third network element cannot send service quality configuration indication information to the application network element through the user plane path, including: the sixth information is used to indicate that the third network element cannot send service quality configuration indication information associated with the second service flow to the application network element through the user plane path.

[0050] Based on the above possible implementation methods, the second network element can determine whether the third network element can send the service quality configuration indication information associated with the second service flow through the user plane path, or determine whether the third network element cannot send the service quality configuration indication information associated with the second service flow through the user plane path.

[0051] In one possible implementation, the eighth information includes identification information of a third service flow, which belongs to the at least one service flow; the eighth information is used to indicate that the fourth network element can send service quality configuration indication information to the application network element through the user plane path, including: the eighth information is used to indicate that the fourth network element can send service quality configuration indication information associated with the third service flow to the application network element through the user plane path; the eighth information is used to indicate that the fourth network element cannot send service quality configuration indication information to the application network element through the user plane path, including: the eighth information is used to indicate that the fourth network element cannot send service quality configuration indication information associated with the third service flow to the application network element through the user plane path.

[0052] Based on the above possible implementation methods, the second network element can determine whether the fourth network element can send the service quality configuration indication information associated with the third service flow through the user plane path, or determine whether the fourth network element cannot send the service quality configuration indication information associated with the third service flow through the user plane path.

[0053] In one possible implementation, sending the seventh information to the fourth network element based on the third information includes: when the sixth information is used to indicate that the third network element can send service quality configuration indication information to the application network element through the user plane path, sending the seventh information to the fourth network element based on the third information.

[0054] Based on the above possible implementation methods, signaling overhead can be saved.

[0055] In one possible implementation, the third network element is a radio access network node and the fourth network element is a user plane network element; or, the third network element is a user plane network element and the fourth network element is a radio access network node.

[0056] Based on the above possible implementation methods, the second network element can negotiate with the radio access network node and the user plane network element respectively, based on the instructions of the first network element, whether to send service quality configuration instruction information to the application network element through the user plane path.

[0057] In one possible implementation, the user plane path includes a user plane channel between the radio access network node and the user plane network element, as well as a user plane channel or application programming interface between the user plane network element and the application network element.

[0058] Based on the above possible implementation methods, the first network element can instruct the second network element to confirm whether the service quality configuration indication information can be sent through the user plane channel between the radio access network node and the user plane network element, as well as the user plane channel or application programming interface between the user plane network element and the application network element.

[0059] Fourthly, a communication device is provided for implementing the method provided in the first aspect. The communication device can be the first network element in the first aspect. The communication device includes modules, units, or means corresponding to the above method, which can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions.

[0060] In one possible implementation, the communication device may include a processing module and an interface module. The processing module can be used to implement the processing functions described in the first aspect and any possible implementation thereof. The processing module may be, for example, a processor. The interface module, also referred to as an interface unit, is used to implement the sending and / or receiving functions described in the first aspect and any possible implementation thereof. The interface module may consist of an interface circuit, a transceiver, a transceiver unit, or a communication interface.

[0061] In one possible implementation, the processing module is configured to control the interface module to receive first information from the application network element, the first information indicating that service quality configuration indication information is sent to the application network element via the user plane path; the processing module is further configured to control the interface module to send second information to the application network element, the second information indicating that service quality configuration indication information can be sent to the application network element via the user plane path, or the second information indicating that service quality configuration indication information cannot be sent to the application network element via the user plane path.

[0062] In one possible implementation, the first information includes one or more of the following: first indication information or identification information of at least one service flow; wherein the first indication information is used to indicate the granularity of the indication information of the quality of service configuration sent through the user plane path, and the at least one service flow is a service flow associated with the indication information of the quality of service configuration sent through the user plane path.

[0063] In one possible implementation, the second information includes identification information of a first service flow, which belongs to the at least one service flow; the second information is used to indicate that service quality configuration can be sent to the application network element via the user plane path, including: the second information is used to indicate that service quality configuration associated with the first service flow can be sent to the application network element via the user plane path; the second information is used to indicate that service quality configuration cannot be sent to the application network element via the user plane path, including: the second information is used to indicate that service quality configuration associated with the first service flow cannot be sent to the application network element via the user plane path.

[0064] In one possible implementation, the granularity of the QoS configuration indication information sent via the user plane path is either a QoS stream or an Internet Protocol stream.

[0065] In one possible implementation, the processing module is further configured to control the interface module to send third information to the second network element in the core network according to the first information, the third information indicating whether service quality configuration indication information can be sent to the application network element through the user plane path; the processing module is further configured to control the interface module to receive fourth information from the second network element, the fourth information indicating whether service quality configuration indication information can be sent to the application network element through the user plane path, or the fourth information indicating whether service quality configuration indication information cannot be sent to the application network element through the user plane path; when the fourth information indicates that service quality configuration indication information can be sent to the application network element through the user plane path, the second information indicates that service quality configuration indication information can be sent to the application network element through the user plane path; when the fourth information indicates that service quality configuration indication information cannot be sent to the application network element through the user plane path, the second information indicates that service quality configuration indication information cannot be sent to the application network element through the user plane path.

[0066] In one possible implementation, the third information indication confirms whether service quality configuration indication information can be sent to the application network element through the user plane path, including: the third information indication confirms whether the node on the user plane path can send service quality configuration indication information to the application network element.

[0067] In one possible implementation, the first information is carried in a subscription request message or a Hypertext Transfer Protocol POST request message.

[0068] In one possible implementation, the first information also indicates that service quality configuration information be sent to the terminal via air interface signaling.

[0069] In one possible implementation, the communication device is a user plane network element or a network open network element.

[0070] In one possible implementation, the communication device is a user plane network element, and the second information is used to indicate that service quality configuration information can be sent to the application network element through the user plane path. The processing module is further used to control the interface module to receive service quality configuration information associated with a first service quality flow from the radio access network node. The processing module is also used to control the interface module to send service quality configuration information associated with a first Internet Protocol flow to the application network element, wherein the first service quality flow and the first Internet Protocol flow have a mapping relationship.

[0071] In one possible implementation, the user plane path includes a user plane channel between a radio access network node and a user plane network element, as well as a user plane channel or application programming interface between the user plane network element and the application network element.

[0072] Fifthly, a communication device is provided for implementing the method provided in the second aspect. This communication device can be an application network element as described in the second aspect. The communication device includes modules, units, or means that implement the method described above. These modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above.

[0073] In one possible implementation, the communication device may include a processing module and an interface module. The processing module can be used to implement the processing functions in the second aspect described above and any possible implementation thereof. The processing module may be, for example, a processor. The interface module, also referred to as an interface unit, is used to implement the sending and / or receiving functions in the second aspect described above and any possible implementation thereof. The interface module may consist of an interface circuit, a transceiver, a transceiver unit, or a communication interface.

[0074] In one possible implementation, the processing module is configured to control the interface module to send first information to a first network element in the core network, the first information indicating that service quality configuration indication information is sent to the communication device via a user plane path; the processing module is further configured to control the interface module to receive second information from the first network element, the second information indicating that service quality configuration indication information can be sent to the communication device via a user plane path, or the second information indicating that service quality configuration indication information cannot be sent to the communication device via a user plane path.

[0075] In one possible implementation, the first information includes one or more of the following: first indication information or identification information of at least one service flow; wherein the first indication information is used to indicate the granularity of the indication information of the quality of service configuration sent through the user plane path, and the at least one service flow is a service flow associated with the indication information of the quality of service configuration sent through the user plane path.

[0076] In one possible implementation, the second information includes identification information of a first service flow, which belongs to the at least one service flow; the second information is used to indicate that service quality configuration can be sent to the communication device via a user plane path, including: the second information is used to indicate that service quality configuration associated with the first service flow can be sent to the communication device via a user plane path; the second information is used to indicate that service quality configuration cannot be sent to the communication device via a user plane path, including: the second information is used to indicate that service quality configuration associated with the first service flow cannot be sent to the communication device via a user plane path.

[0077] In one possible implementation, the granularity of the QoS configuration indication information sent via the user plane path is either a QoS stream or an Internet Protocol stream.

[0078] In one possible implementation, the first information is carried in a subscription request message or a Hypertext Transfer Protocol POST request message.

[0079] In one possible implementation, the first information also indicates that service quality configuration information be sent to the terminal via air interface signaling.

[0080] In one possible implementation, the first network element is a user plane network element or a network open network element.

[0081] In one possible implementation, the user plane path includes a user plane channel between a radio access network node and a user plane network element, as well as a user plane channel or application programming interface between the user plane network element and the communication device.

[0082] Sixthly, a communication device is provided for implementing the method provided in the third aspect above. The communication device can be the second network element in the third aspect. The communication device includes modules, units, or means that implement the method described above. These modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above.

[0083] In one possible implementation, the communication device may include a processing module and an interface module. The processing module can be used to implement the processing functions in the third aspect described above and any possible implementation thereof. The processing module may be, for example, a processor. The interface module, also referred to as an interface unit, is used to implement the sending and / or receiving functions in the third aspect described above and any possible implementation thereof. The interface module may consist of an interface circuit, a transceiver, a transceiver unit, or a communication interface.

[0084] In one possible implementation, the processing module is configured to control the interface module to receive third information from a first network element in the core network, the third information indicating whether service quality configuration indication information can be sent to the application network element via the user plane path; the processing module is further configured to control the interface module to send fifth information to a third network element based on the third information, the fifth information indicating that the third network element can send service quality configuration indication information to the application network element via the user plane path; the processing module is further configured to control the interface module to receive sixth information from the third network element, the sixth information indicating that the third network element can send service quality configuration indication information to the application network element via the user plane path, or the sixth information indicating that the third network element cannot send service quality configuration indication information to the application network element via the user plane path; the processing module is further configured to control the interface module to receive, based on, the third network element, the third network element, the third network element, the third network element, the fourth network element, the fifth network element, the sixth ... The third information sends a seventh information to the fourth network element, the seventh information instructing the fourth network element to send a quality of service (QoS) configuration instruction to the application network element via a user plane path; the processing module is further configured to control the interface module to receive an eighth information from the fourth network element, the eighth information indicating that the fourth network element can send the QoS configuration instruction to the application network element via a user plane path, or the eighth information indicating that the fourth network element cannot send the QoS configuration instruction to the application network element via a user plane path; the processing module is further configured to control the interface module to send a fourth information to the first network element based on the sixth information and the eighth information, the fourth information indicating that the QoS configuration instruction can be sent to the application network element via a user plane path, or the fourth information indicating that the QoS configuration instruction cannot be sent to the application network element via a user plane path.

[0085] In one possible implementation, the third information includes one or more of the following: second indication information or identification information of at least one service flow; wherein the second indication information is used to indicate the granularity of the indication information of the quality of service configuration sent through the user plane path, and the at least one service flow is a service flow associated with the indication information of the quality of service configuration sent through the user plane path.

[0086] In one possible implementation, the sixth information includes identification information of the second service flow, which belongs to the at least one service flow; the sixth information is used to indicate that the third network element can send service quality configuration indication information to the application network element through the user plane path, including: the sixth information is used to indicate that the third network element can send service quality configuration indication information associated with the second service flow to the application network element through the user plane path; the sixth information is used to indicate that the third network element cannot send service quality configuration indication information to the application network element through the user plane path, including: the sixth information is used to indicate that the third network element cannot send service quality configuration indication information associated with the second service flow to the application network element through the user plane path.

[0087] In one possible implementation, the eighth information includes identification information of a third service flow, which belongs to the at least one service flow; the eighth information is used to indicate that the fourth network element can send service quality configuration indication information to the application network element through the user plane path, including: the eighth information is used to indicate that the fourth network element can send service quality configuration indication information associated with the third service flow to the application network element through the user plane path; the eighth information is used to indicate that the fourth network element cannot send service quality configuration indication information to the application network element through the user plane path, including: the eighth information is used to indicate that the fourth network element cannot send service quality configuration indication information associated with the third service flow to the application network element through the user plane path.

[0088] In one possible implementation, the processing module is specifically configured to control the interface module to send the seventh information to the fourth network element based on the third information when the sixth information is used to indicate that the third network element can send the quality of service configuration to the application network element through the user plane path.

[0089] In one possible implementation, the third network element is a radio access network node and the fourth network element is a user plane network element; or, the third network element is a user plane network element and the fourth network element is a radio access network node.

[0090] In one possible implementation, the user plane path includes a user plane channel between the radio access network node and the user plane network element, as well as a user plane channel or application programming interface between the user plane network element and the application network element.

[0091] A seventh aspect provides a communication device, comprising: a processor; configured to cause the communication device to perform the method described in any of the preceding aspects by executing a computer program (or computer-executable instructions) stored in a memory, and / or by means of logic circuitry. The communication device may be a first network element as described in the first aspect; or, the communication device may be an application network element as described in the second aspect; or, the communication device may be a second network element as described in the third aspect. Optionally, the number of processors may be one or more.

[0092] In one possible implementation, the communication device also includes a memory.

[0093] In one possible implementation, the processor and memory are integrated together; or, the memory is independent of the processor.

[0094] In one possible implementation, the communication device further includes a communication interface for communicating with other devices, such as transmitting or receiving data and / or signals. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface.

[0095] In one possible implementation, the communication device is a chip or a chip system. Optionally, when the communication device is a chip system, it can be composed of chips or may include chips and other discrete components.

[0096] Eighthly, a communication device is provided, comprising: a processor and an interface circuit; the interface circuit is configured to receive a computer program or instructions and transmit them to the processor; the processor is configured to execute the computer program or instructions to cause the communication device to perform the method described in any of the preceding aspects. The communication device may be a first network element as described in the first aspect; or, the communication device may be an application network element as described in the second aspect; or, the communication device may be a second network element as described in the third aspect. Optionally, the number of processors may be one or more.

[0097] In one possible implementation, the communication device is a chip or a chip system. Optionally, when the communication device is a chip system, it can be composed of chips or may include chips and other discrete components.

[0098] Ninthly, a computer-readable storage medium is provided that stores instructions which, when executed on a computer, cause the computer to perform the methods described in any of the preceding aspects.

[0099] In a tenth aspect, a computer program product containing instructions is provided, which, when run on a computer, enables the computer to perform the methods described in any of the preceding aspects.

[0100] In an eleventh aspect, a communication system is provided, comprising at least two of the following: a first network element for performing the method described in the first aspect, an application network element for performing the method described in the second aspect, or a second network element for performing the method described in the third aspect.

[0101] The technical effects of any possible implementation of aspects four through eleven can be found in the technical effects of any one of aspects one through three or different possible implementations of any one of aspects, and will not be repeated here.

[0102] Understandably, provided that the solutions do not contradict each other, the solutions in the above aspects can be combined. Attached Figure Description

[0103] Figure 1A This is a schematic diagram of the architecture of the open radio access network (O-RAN) provided in this application;

[0104] Figure 1B A schematic diagram of the virtual reality (VR) task provided in this application;

[0105] Figure 1C A schematic diagram of the deep neural network (DNN) model provided in this application;

[0106] Figure 1D A schematic diagram illustrating the process by which the RAN node, as provided in this application, instructs the compute node to provide the QoS profile through an alternative QoS mechanism;

[0107] Figure 2A A schematic diagram of the communication system architecture provided in this application;

[0108] Figure 2B A schematic diagram of the fifth-generation (5G) network architecture provided for this application;

[0109] Figure 3 A schematic diagram of the hardware structure of the communication device provided in this application;

[0110] Figure 4 A flowchart illustrating the communication method provided in this application;

[0111] Figure 5 Flowchart 2 of the communication method provided in this application;

[0112] Figure 6A schematic diagram of the communication device provided in this application. Detailed Implementation

[0113] Before introducing the technical solution of this application, the relevant technical terms involved in this application are explained. It is understood that these explanations are intended to make this application easier to understand and should not be regarded as a limitation on the scope of protection claimed in this application.

[0114] 1. Terminal

[0115] The terminal in this application is a device with wireless transceiver capabilities, on which third-party application services can be deployed. The terminal can be deployed on land, including indoors, outdoors, handheld, or vehicle-mounted; it can also be deployed on water (such as on ships); and it can be deployed in the air (such as on airplanes, balloons, and satellites). The terminal can also be referred to as a terminal device, which can be user equipment (UE), mobile station (MS), mobile terminal (MT), or a device used to provide voice or data connectivity to users. The UE includes handheld devices with wireless communication capabilities, vehicle-mounted devices (e.g., cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains), wearable devices (e.g., smartwatches, smart bracelets, pedometers), or computing devices. For example, the UE can be a mobile phone, tablet computer, laptop computer, PDA, mobile internet device (MID), satellite terminal, or computer with wireless transceiver capabilities. UE can also be a VR terminal device, an augmented reality (AR) terminal device, a wireless modem, a point-of-sale (POS) machine, customer-premises equipment (CPE), a smart robot, a robotic arm, workshop equipment, smart home devices (e.g., refrigerators, televisions, air conditioners, electricity meters, etc.), a wireless terminal in industrial control, a wireless terminal in autonomous driving, a wireless terminal in telemedicine, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in intelligent transportation, a wireless terminal in a smart city, a wireless terminal in a smart home, an in-vehicle terminal, a roadside unit (RSU) with terminal functionality, or a flying device (e.g., a smart robot, a hot air balloon, a drone, an airplane), etc. A terminal can also be other devices with terminal functionality; for example, a terminal can be a device that acts as a terminal in device-to-device (D2D) communication.

[0116] By way of example and not limitation, in this application, the terminal can be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into a user's clothing or accessories. For example, wearable devices are not merely hardware devices, but also devices that achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include devices that are feature-rich, large in size, and can achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as devices that focus on only one type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0117] In this application, the terminal can also be a terminal in an Internet of Things (IoT) system. IoT is an important component of future information technology development, and its main technical feature is connecting objects to networks through communication technologies, thereby realizing an intelligent network of human-machine interconnection and machine-to-machine interconnection. The terminal in this application can be a terminal in machine-type communication (MTC). The terminal in this application can be an on-board module, on-board component, on-board chip, or on-board unit built into a vehicle as one or more components or units. The vehicle can implement the methods of this application through the built-in on-board module, on-board component, on-board chip, or on-board unit.

[0118] 2. RAN Node

[0119] The RAN node in this application can be any device with wireless transceiver capabilities, providing wireless access services to terminals. RAN nodes can include, but are not limited to: evolved base stations (NodeB, eNB, or e-NodeB) in Long Term Evolution (LTE), evolved base stations (ng-eNB) in Next Generation LTE, base stations (gNodeB or gNB) or transmission receiving points / transmission reception points (TRPs) in New Radio (NR), base stations in subsequent evolutions of the 3rd Generation Partnership Project (3GPP), access nodes in Wireless Fidelity (WiFi) systems, wireless relay nodes, wireless backhaul nodes, etc. Base stations can be: macro base stations, micro base stations, pico base stations, small cells, relay stations, or balloon stations, etc. Multiple base stations can support networks using the same technology mentioned above, or they can support networks using different technologies mentioned above. A base station can contain one or more co-located or non-co-located TRPs. RAN nodes can also be radio controllers in cloud radio access network (CRAN) scenarios. RAN nodes can also be centralized units (CUs), distributed units (DUs), CU-control plane (CP), CU-user plane (UP), radio units (RUs), roadside units (RSUs) with base station functionality, wired access gateways, or core network elements. Specifically, CUs can perform the functions of the radio resource control (RRC) layer and the packet data convergence protocol (PDCP) layer of a base station. CUs can also perform the functions of the service data adaptation protocol (SDAP) layer. DUs can perform the functions of the radio link control (RLC) layer and the medium access control (MAC) layer of a base station. DUs can also perform some or all of the physical layer functions.Furthermore, the CU can control one or more DUs, and the DU can support one or more cells. The CU can connect to the DU via the F1 interface. The CU can handle slow processing of non-real-time functions within the base station, such as handover and connection management, while the DU can handle fast processing of real-time functions within the base station, such as encoding / decoding and fast scheduling. The RU can be used to implement radio frequency signal transmission and reception functions. The CU and DU can be set up separately or included in the same network element, such as in the baseband unit (BBU). The RU can be included in radio frequency equipment or radio frequency units, such as in the remote radio unit (RRU), active antenna unit (AAU), or remote radio head (RRH). It is understood that the CU can be classified as a network device in the access network or a network device in the core network, without limitation. Any of the CU (or CU-CP, CU-UP), DU, and RU units in this application can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules.

[0120] Understandably, CU (or CU-CP and CU-UP), DU, or RU may have different names in different systems, but those skilled in the art will understand their meaning. For example, in an O-RAN system, the baseband unit and radio unit can be divided into three different modules and their protocol layers: O-RU (Open RU), O-DU (Open DU), and O-CU (Open CU), and these modules should be kept consistent with and reused as much as possible with the RAN network elements defined by the 3GPP standard. In other words, in an O-RAN system, CU can also be called O-CU, DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU.

[0121] For example, please refer to Figure 1A This is a schematic diagram of the O-RAN architecture. Figure 1A In this architecture, the RNA node can include a service management and orchestration framework (SMO) module, a near-real-time RAN intelligent controller (Near-RT RIC), an O-CU, an O-DU, and an O-RU. Each module will be described below.

[0122] a. The SMO module is a subsystem for Operation Administration and Maintenance (OAM) network management and non-real-time radio resource control. The SMO module primarily has the following three functions: 1) Cloud infrastructure OAM implementation, such as operating, maintaining, and managing cloud infrastructure through the O2 interface; 2) RAN OAM, such as operating, maintaining, and managing the radio access network through the O1 interface; 3) Non-real-time RAN Intelligent Control (Non-RT RIC), such as combining artificial intelligence and big data analytics to implement non-real-time macro-control and intervention of O-RAN radio resources through the A1 interface. Each managed logical network element in the O-RAN architecture (such as O-RU, O-DU, or O-CU) can act as an independent entity, communicating with the SMO module using an independent, publicly accessible O1 communication interface. In some embodiments, the SMO module may include Non-RT RIC functionality, configuration functionality, policy functionality, design functionality, and inventory functionality.

[0123] b. The Near-RT RIC can be used to collect network information and perform optimization tasks. The Near-RT RIC can communicate with the O-CU and O-DU via the E2 interface. In some embodiments, the Near-RT RIC can be divided into QoS management (QoS magmt.) functions, radio connection management (radio connection magmt.) functions, interference management (interference magmt.) functions, and mobility management (mobility magmt.) functions, etc.

[0124] c. The functions of O-CU are similar to those of CU, O-DU are similar to those of DU, and O-RU are similar to those of RU. O-DU can communicate with O-CU through the F1 interface and with O-RU through the fronthaul interface or the low layer split (LLS) interface.

[0125] In addition, RAN nodes can also be servers, wearable devices, machine communication devices, or in-vehicle devices. For example, the access network equipment in vehicle-to-everything (V2X) technology can be an RSU. The following explanation uses a RAN node as a base station as an example. The multiple RAN nodes can be base stations of the same type or different types. A base station can communicate with a terminal, or it can communicate with a terminal through a relay station. A terminal can communicate with multiple base stations using different technologies. For example, a terminal can communicate with a base station supporting LTE networks, or with a base station supporting 5G networks, or it can support dual connectivity with both LTE and 5G base stations, or dual connectivity with base stations of future networks and 5G base stations. Alternatively, a terminal can communicate with multiple base stations using the same technology. For example, a terminal can support dual connectivity with LTE base stations, or dual connectivity with 5G base stations (which can be called NR-DC (new radio dual connectivity)), or dual connectivity with base stations of future networks.

[0126] Understandably, in some scenarios, the roles of RAN nodes and terminals are relative. For example, a helicopter or drone, which is usually configured as a terminal, can also be configured as a mobile base station, and a device that accesses the RAN via a helicopter or drone is configured as a terminal.

[0127] 3. Extended Reality (XR)

[0128] XR refers to various environments that combine reality and virtuality, generated by computing technology and wearable devices, as well as human-computer interaction. It boasts advantages such as multiple perspectives and strong interactivity, providing users with a completely new experience and possessing immense application value and commercial potential. XR mainly includes virtual and real-world interaction technologies such as VR, AR, and mixed reality (MR), which can be widely applied in entertainment, gaming, healthcare, advertising, industry, online education, and engineering. The following sections will introduce VR, AR, and MR technologies respectively.

[0129] VR technology integrates computer graphics, multimedia, and other technologies to simulate the functions of human senses such as sight, hearing, and touch, making users feel as if they are actually there, immersed in a computer-generated virtual world. This allows for real-time communication through language and gestures, enhancing the sense of immersion. Through VR technology, people can experience the real world realistically while overcoming the limitations of time and space, experiencing the wonder of entering a virtual world. VR technology typically requires users to wear XR terminals (such as head-mounted displays) to simulate visual and / or auditory and / or tactile sensations. VR technology can also track user movements, updating the simulated visual and / or auditory and / or tactile content in real time. For example, VR technology can process user status information (such as location and posture) to display scene content corresponding to the user's status on the XR terminal.

[0130] AR technology uses computer technology to overlay virtual information onto the real world, displaying it through devices such as mobile phones, tablets, and glasses, allowing people to perceive it and thus achieving a great fusion of reality and virtuality, enriching the real world. In short, it gives objects more information, enhances their three-dimensionality, and strengthens visual effects and interactive experiences. For example, AR technology can process perceived visual information (usually including depth information) to merge virtual information with the real world, making it perceptible to the user and thus "enhancing" the real world.

[0131] MR technology can blend the real world and the virtual world to create new visual environments that contain both physical entities and virtual information, and the content seen in these visual environments is "real-time".

[0132] 4. Multi-node collaboration

[0133] In recent years, video rendering services such as cloud gaming and VR, and artificial intelligence (AI) services such as terminal visual cognition, AR, and MR, have placed increasing demands on network bandwidth and terminal computing power. However, the limited network bandwidth and terminal computing power can no longer meet the needs of these services.

[0134] Taking video rendering as an example, if video rendering is performed on the terminal, the terminal's computing power is insufficient to achieve high-quality rendering of pure local video. If video rendering is performed in the cloud, it cannot meet the low latency requirement, and due to the limitations of network transmission capabilities, the image will exhibit black border effects, distortion, and other phenomena.

[0135] Taking AI services as an example, if AI services are executed on the terminal, the terminal's computing power and power are insufficient to support local AI inference. If AI services are executed in the cloud, while meeting the low latency requirement, cloud-based AI inference requires a large uplink bandwidth, which will lead to limitations in uplink coverage and the number of users.

[0136] Therefore, to balance the computing power of the terminal and the transmission capacity of the network, a multi-node collaborative task processing scheme is proposed. Here, a task can refer to the work of processing data through multiple steps. These multiple steps can be parallel steps, serial steps, or a combination of parallel and serial steps. To facilitate the description of the multiple steps included in a task, one or more related steps can be regarded as a subtask; that is, a task can include multiple subtasks.

[0137] In this application, a service, such as a video rendering service or an AI service, may include one or more tasks. If a service includes one task, the terminal and the cloud may each execute a portion of the sub-task to reduce the task's requirements on the terminal, computing power, and network bandwidth. If a service includes multiple tasks, the terminal and the cloud may collaborate to process all or part of the multiple tasks. For each of the multiple tasks, the terminal and the cloud may each execute a portion of the sub-task to reduce the multiple tasks' requirements on the terminal, computing power, and network bandwidth.

[0138] It is understood that the terminal or cloud in this application can be collectively referred to as a computing node. The computing node can be any device with computing and communication capabilities. Besides terminals and the cloud, a computing node can also be a RAN node, a functional module of a RAN node (such as a CU, DU, or RIC), a core network element, or an application network element. For a description of terminals and RAN nodes, please refer to the explanation of the technical terms used in this application above. Core network elements can be, for example, one or more of the following: user plane function (UPF) network elements, access and mobility management function (AMF) network elements, session management function (SMF) network elements, or policy control function (PCF) network elements. Application network elements can also be referred to as application function (AF) network elements. Application network elements can be, for example, servers, application servers (AS), cloud servers, cloud platforms, mobile edge computing (MEC) platforms, cloud computing or computing execution entities (CEF), etc., without restriction. Cloud platforms can reside in the data network behind UPF network elements and can interact with the 5th generation system (5GS) via the N6 interface to exchange user plane application layer data and provide computing services.

[0139] In summary, a task can be divided into multiple subtasks, which can be executed by multiple computing nodes. It should be understood that this application does not limit the number of computing nodes executing a task. For example, a task can be divided into 3 subtasks, each executed by 3 computing nodes, or it can be divided into 2 subtasks, each executed by 2 computing nodes.

[0140] The following section uses the terminal and cloud as examples to illustrate the specific process of multiple computing nodes executing tasks.

[0141] Please refer to Figure 1B The VR task can be divided into subtask 101 and subtask 102. The terminal can acquire initial data (such as image information), input the initial data into subtask 101 to obtain intermediate data, and then send the intermediate data to the cloud. After receiving the intermediate data, the cloud inputs it into subtask 102 to obtain the target data.

[0142] Understandably, there are multiple ways to split tasks, and different splitting methods can correspond to different communication needs.

[0143] For example, taking video rendering tasks as an example, the video rendering task can be divided according to the separation of foreground and background. For instance, the foreground part of the image is generally difficult to predict and has a small rendering load, so it can be rendered locally on the terminal. The background part of the image is predictable, but the rendering load of lighting and texture effects is large, so it can be rendered in the cloud. Alternatively, the video rendering task can be divided according to the user's gaze point. For instance, the image at the center of the gaze point can be rendered locally on the terminal, while the image around the gaze point can be rendered in the cloud. Or, the video rendering task can be divided according to objects. For instance, different nodes can be selected for rendering based on the rendering load and data volume requirements of different objects.

[0144] For video rendering tasks, different segmentation methods correspond to different amounts of video data to be transmitted, thus affecting communication requirements. For example, as shown in Table 1, pure cloud rendering requires an average data transmission bit rate of 4 Mbps, a peak of 40 Mbps, and an allowable transmission latency of 25 ms. Edge-cloud collaborative rendering requires an average data transmission bit rate of 0.49 Mbps to 1.8 Mbps, a peak of 3.8 Mbps, and an allowable transmission latency of 50 ms. It is evident that edge-cloud collaborative processing of video rendering tasks can reduce downlink transmission rate requirements. Therefore, selecting an appropriate video rendering task segmentation method can increase the number of downlink transmission users accessing the network.

[0145] Table 1

[0146]

[0147] Taking AI computing tasks as an example, the computational model of an AI computing task can be divided into multiple sub-models, and one or more sub-models can be regarded as a sub-task. For example, the AI ​​computing model is a neural network (NN) model or a DNN model. NN / DNN models can include multiple layers, such as input layers, convolutional layers, pooling layers, and fully connected layers. These layers can be segmented; for example, the input layer and convolutional layers can be deployed on the terminal, while the pooling layer and fully connected layer can be deployed in the cloud. In this way, the terminal can perceive user behavior data (such as user location information, posture information, or voice information) or surrounding environment data (such as video or images of the surrounding environment) through sensing modules such as radar, cameras, handheld devices, or microphones. This data is then sequentially input into the input layer and convolutional layer to obtain intermediate data, which is then sent to the cloud. Subsequently, after receiving the intermediate data, the cloud sequentially inputs it into the pooling layer and fully connected layer to obtain the target data. Optionally, the cloud can also send the target data to the terminal.

[0148] Further research revealed that when tasks are segmented, the amount of intermediate data and the computational load on the terminal may vary depending on the location of the task segmentation (hereinafter referred to as the task segmentation point).

[0149] For example, with Figure 1C Taking the DNN model shown as an example, this DNN model includes an input layer, convolutional layer 1, pooling layer 1, convolutional layer 2, pooling layer 2, convolutional layer 3, pooling layer 3, convolutional layer 4, pooling layer 4, convolutional layer 5, an activation function (such as a rectified linear unit (ReLU)), pooling layer 5, fully connected layer 1, fully connected layer 2, and an output layer. Initial data is sequentially input into the above layers to obtain the target data. Figure 1CThe diagram also shows five candidate split points, numbered 0 through 4, located in different positions within the DNN model. Understandably, layers before a candidate split point can be deployed on the terminal, while layers after a candidate split point can be deployed in the cloud. For example, candidate split point 0 is located before the input layer, so the terminal doesn't perform any tasks, sending initial data to the cloud for execution. Candidate split point 1 is located after pooling layer 1, so the terminal executes tasks before pooling layer 1, while the cloud executes tasks after. Candidate split point 2 is located after pooling layer 2, so the terminal executes tasks before pooling layer 2, while the cloud executes tasks after. Candidate split point 3 is located after pooling layer 5, so the terminal executes tasks before pooling layer 5, while the cloud executes tasks after. Candidate split point 4 is located after the output layer, so the terminal executes all tasks, the cloud doesn't perform any tasks, and the terminal doesn't send intermediate data to the cloud. The approximate output uplink data size (UL data size) (i.e., the amount of intermediate data) and the computational load in the UE differ for each candidate segmentation point. Taking candidate segmentation point 1 and candidate segmentation point 2 as examples, in Table 2, the approximate output uplink data size for candidate segmentation point 1 is 120 Mbit / s, and the computational load of the terminal corresponding to candidate segmentation point 1 is low; the approximate output uplink data size for candidate segmentation point 2 is 24 Mbit / s, and the computational load of the terminal corresponding to candidate segmentation point 2 is high. The larger the approximate output uplink data size, the more data the terminal needs to transmit, i.e., the larger the amount of intermediate data, and therefore the smaller the computational load of the terminal. Conversely, the smaller the approximate output uplink data size, the less data the terminal needs to transmit, and the higher the computational load of the terminal. Therefore, under the premise of meeting the terminal's computational load requirements, selecting an appropriate task segmentation point can reduce the data rate to be transmitted, thereby increasing the number of users who can access the network.

[0150] Table 2

[0151] Split point Approximate output uplink data size (Mbit / s) Computational load of the terminal Candidate split point 1 120 Low Candidate split point 2 24 High

[0152] In summary, the scheduling results of tasks (such as the task splitting point) can affect the size of intermediate data, communication requirements, and the computing load of the terminal, so determining the task scheduling results is crucial.

[0153] 5. Alternative QoS mechanisms

[0154] To mitigate the risk of releasing Quality of Service (QoS) flows due to RAN resource constraints, RAN nodes can use an alternative QoS mechanism to indicate QoS profiles to compute nodes. Specifically, different alternative QoS profiles (also known as alternative QoS configuration information) can describe the QoS requirements for different task splitting points. In this way, RAN nodes can select an appropriate alternative QoS profile based on the current communication status and indicate the selected profile to the compute nodes, enabling the compute nodes to determine the task scheduling outcome.

[0155] The following example, using a compute node comprising terminals and application network elements, illustrates the specific process by which the RAN node instructs the compute node on its QoS profile through an alternative QoS mechanism. Figure 1D As shown, the process may include the following steps:

[0156] S111: The RAN node obtains at least one alternative QoS profile from the core network.

[0157] S112: The RAN node determines the target QoS profile from at least one alternative QoS profile based on the network status.

[0158] Understandably, if a RAN node cannot meet the QoS requirements of the current QoS profile—for example, if it cannot meet the guaranteed flow bit rate (GFBR), guaranteed bit rate (GBR), packet delay budget (PDB), or packet error rate (PER)—the RAN node can determine which QoS requirements can be met by considering at least one alternative QoS profile in order of priority. If the RAN node can meet the GFBR, GBR, PDB, or PER requirements of an alternative QoS profile, then the RAN node will use that matched alternative QoS profile to provide service for the corresponding QoS flow. This matched alternative QoS profile becomes the target QoS profile.

[0159] In this application, GFBR can refer to uplink GFBR, downlink GFBR, or the sum of uplink and downlink GFBR. Similarly, GBR can refer to uplink GBR, downlink GBR, or the sum of uplink and downlink GBR; PDB can refer to uplink PDB, downlink PDB, or the sum of uplink and downlink PDB; and PER can refer to uplink PER, downlink PER, or the sum of uplink and downlink PER. This is a unified explanation here and will not be repeated later.

[0160] S113: The RAN node sends indication information to the core network, specifying the target QoS profile. Correspondingly, the core network receives the indication information from the RAN node.

[0161] For example, the RAN node sends the above-mentioned instruction information to the SMF network element in the core network.

[0162] S114: The core network sends the aforementioned instruction information to the terminal. Correspondingly, the terminal receives the aforementioned instruction information from the core network.

[0163] For example, SMF network elements send the above indication information to the terminal through non-access stratum (NAS) signaling so that the terminal can determine that the current QoS profile has changed or the scheduling result of the task based on the indication information.

[0164] S115: The core network sends the aforementioned instruction information to the application network element. Correspondingly, the application network element receives the instruction information from the core network.

[0165] For example, the SMF network element sends this indication information to the application network element so that the application network element can determine whether the current QoS profile has changed or the scheduling result of the task based on the indication information.

[0166] Understandably, the core network can execute S114 first and then S115, or execute S115 first and then S114, or execute S114 and S115 simultaneously, without restriction.

[0167] Understandably, once the network status is restored and the RAN can meet the previous QoS configuration file, the RAN node can notify the terminal and application network elements through the core network so that the terminal and application network elements can execute tasks using the previous task splitting method.

[0168] In the above process, since the QoS profile is related to the task scheduling result, the QoS provided by the network can meet the QoS requirements of the task to ensure user experience. In addition to sending indication information for the target QoS profile to the application network element via the control plane path (e.g., the RAN node sending this indication information to the application network element via the SMF network element), this indication information can also be sent to the application network element via the user plane path (e.g., the RAN node sending this indication information to the application network element via the UPF network element). Therefore, determining which method the RAN node specifically adopts to send this indication information is a problem that urgently needs to be solved.

[0169] To address the aforementioned problems, this application provides a communication method. This communication method can be used in various communication systems. For example, the communication system can be a Universal Mobile Telecommunications System (UMTS) system, an LTE system, a 5G communication system, a WiFi system, a 3GPP-related communication system, a communication system evolved after 5G, or a system integrating multiple systems, etc., without limitation. Among them, 5G can also be referred to as NR. The following uses... Figure 2A The method provided in this application will be described using the communication system 20 shown as an example. Figure 2A This is merely an illustrative diagram and does not constitute a limitation on the applicable scenarios of the technical solutions provided in this application.

[0170] like Figure 2A The diagram shown is a schematic diagram of the architecture of the communication system 20 provided in this application. Figure 2A In the communication system 20, the network element 201 may include a network element 201 and a network element 202 that can communicate with the network element 201. Optionally, the communication system 20 may further include at least one of the following: a network element 203 that is communicatively connected to the network element 202 and the network element 201; a network element 204 that is communicatively connected to the network element 201; a network element 205 that is communicatively connected to the network element 204 and the network element 203; or a terminal 206 that is communicatively connected to the network element 205.

[0171] exist Figure 2A In this core network, network elements 201, 203, and 204 are located. These network elements can be existing core network elements or newly added core network elements, without restriction. For example, network element 201 is a network open network element, network element 203 is a user plane network element, and network element 204 is a session management network element. Network element 202 is located in the data network after the user plane network element and can interact with the user plane network element for application layer data, or network element 202 may also be located in the core network. In addition, applications can be installed on network element 202 to provide application services such as computing and data. For example, network element 202 is an application network element. Network element 205 and terminal 206 are located in the RAN. This RAN can be a 3GPP-related cellular system, such as a 4G, 5G mobile communication system, or a future-oriented evolution system. The RAN can also be an O-RAN, CRAN, or WiFi system, etc. The RAN can also be a communication system that integrates two or more of the above systems. For example, network element 205 is a RAN node, and terminal 206 is one or more terminals accessing that RAN node. The descriptions of the application network element, RAN node, and terminal are provided above and will not be repeated here.

[0172] exist Figure 2AIn this process, network element 202 can negotiate with network element 201 (or network element 203) the method by which network element 205 sends the QoS configuration indication information to network element 202, so that network element 205 can determine which method to use to send the QoS configuration indication information to network element 202. For example, network element 202 can send a first message to network element 201 (or network element 203). The first message indicates that the QoS configuration indication information should be sent to network element 202 via the user plane path. After receiving the first message, network element 201 (or network element 203) sends a second message to network element 202. The second message indicates that the QoS configuration indication information can be sent to network element 202 via the user plane path, or that the second message cannot be sent to network element 202 via the user plane path.

[0173] In some embodiments, after receiving the first information, network element 201 can negotiate with network element 203 and network element 205 to send QoS configuration indication information to network element 202, and send the second information to network element 202 based on the negotiation result.

[0174] The above process will be described below. Figure 4 The method shown and Figure 5 The method shown will be explained in detail here, but will not be elaborated upon further.

[0175] It is understood that the above-mentioned communication system 20 can be applied to a variety of communication networks, such as the 5G network currently under discussion, or other future networks, etc. This application embodiment does not specifically limit it in this regard.

[0176] For example, communication system 20 is suitable for Figure 2B The 5G network shown includes network exposure function (NEF) network elements, network repository function (NRF) network elements, policy and charging rules function (PCRF) network elements, PCF network elements, unified data repository (UDR) network elements, unified data management (UDM) network elements, AMF network elements, SMF network elements, AF network elements, UPF network elements, RAN nodes, terminals, and data network (DN).

[0177] exist Figure 2BIn this configuration, terminals can access the 5G network through RAN nodes. Terminals communicate with AMF network elements via the N1 interface (N1 for short); RAN nodes communicate with AMF network elements via the N2 interface (N2 for short) and with UPF network elements via the N3 interface (N3 for short); SMF network elements communicate with UPF network elements via the N4 interface (N4 for short), and UPF network elements access the DN via the N6 interface (N6 for short). Furthermore, Figure 2B The network elements shown, such as NEF, NRF, PCRF, PCF, UDR, UDM, AMF, SMF, or AF, can interact using service-oriented interfaces. For example, the service-oriented interface provided by the NEF network element is Nnef; that of the NRF network element is Nnrf; that of the PCRF network element is Npcrf; that of the PCF network element is Npcf; that of the UDR network element is Nudr; that of the UDM network element is Nudm; that of the AMF network element is Namf; that of the SMF network element is Nsmf; and that of the AF network element is Naf.

[0178] Understandably, the device or entity corresponding to network element 201 in communication system 20 is... Figure 2B The NEF network element in the 5G network shown. The device or entity corresponding to network element 202 in communication system 20 is... Figure 2B The AF network element in the 5G network shown. The device or entity corresponding to network element 203 in communication system 20 is... Figure 2B The UPF network element in the 5G network is shown. The device or entity corresponding to network element 204 in communication system 20 is... Figure 2B The SMF network element in the 5G network shown. The device or entity corresponding to network element 205 in communication system 20 is... Figure 2B The RAN node in the 5G network shown. The device or entity corresponding to terminal 206 in communication system 20 is... Figure 2B The terminal shown is in the 5G network.

[0179] Understandable. Figure 2A The communication system 20 shown is for illustrative purposes only and is not intended to limit the technical solutions of this application. Those skilled in the art should understand that in specific implementations, the communication system 20 may also include other devices, and the number of network elements and terminals may be determined according to specific needs without limitation.

[0180] Optionally, this application Figure 2A Each network element in the process can also be referred to as a communication device, which can be a general-purpose device or a special-purpose device. This application does not make any specific limitation in this regard.

[0181] Optionally, this application Figure 2A The functions of each network element can be implemented by one device, multiple devices working together, or one or more functional modules within a single device; this application does not impose any specific limitations on this. It is understood that the aforementioned functions can be network elements within hardware devices, software functions running on dedicated hardware, a combination of hardware and software, or virtualization functions instantiated on a platform (e.g., a cloud platform).

[0182] In practical implementation, Figure 2A Each of the network elements shown can be adopted Figure 3 The shown composition structure, or including Figure 3 The components shown. Figure 3 The diagram shows a hardware structure of a communication device applicable to this application. The communication device 30 includes at least one processor 301 and at least one communication interface 304 for implementing the method provided in this application. The communication device 30 may also include a communication line 302 and a memory 303.

[0183] The processor 301 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program of the present application.

[0184] Communication line 302 may include a path for transmitting information between the aforementioned components, such as a bus.

[0185] Communication interface 304 is used for communication with other devices or communication networks. Communication interface 304 can be any transceiver-like device, such as an Ethernet interface, a radio access network (RAN) interface, a wireless local area network (WLAN) interface, a transceiver, pins, a bus, interface circuits, or transceiver circuits, etc.

[0186] The memory 303 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM), cache, or other type of dynamic storage device capable of storing information and instructions. It may also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media, or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto. The memory may exist independently and be coupled to the processor 301 via communication line 302. The memory 303 may also be integrated with the processor 301. The memory provided in this application is generally non-volatile.

[0187] The memory 303 stores computer execution instructions involved in the scheme provided in this application, and the processor 301 controls the execution of these instructions. The processor 301 executes the computer execution instructions stored in the memory 303 to implement the method provided in this application. Alternatively, in this application, the processor 301 may execute the processing-related functions of the method provided below, and the communication interface 304 may be responsible for communicating with other devices or communication networks. This application does not specifically limit the specific implementation of this method.

[0188] Optionally, the computer execution instructions in this application may also be referred to as application code, and this application does not specifically limit them.

[0189] The coupling in this application is an indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, and is used for information exchange between devices, units, or modules.

[0190] As one embodiment, processor 301 may include one or more CPUs, for example Figure 3 CPU0 and CPU1 in the CPU.

[0191] As one embodiment, the communication device 30 may include multiple processors, such as Figure 3Processors 301 and 307 are described herein. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor here may refer to one or more devices, circuits, and / or processing cores used to process data (e.g., computer program instructions).

[0192] As one embodiment, the communication device 30 may further include an output device 305 and / or an input device 306. The output device 305 is coupled to the processor 301 and can display information in various ways. For example, the output device 305 may be a liquid crystal display (LCD), a light-emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector, etc. The input device 306 is coupled to the processor 301 and can receive user input in various ways. For example, the input device 306 may be a mouse, keyboard, touchscreen device, or sensing device, etc.

[0193] Understandable. Figure 3 The structural composition shown does not constitute a limitation on the communication device, except... Figure 3 In addition to the components shown, the communication device may include more or fewer components than illustrated, or combine certain components, or have different component arrangements.

[0194] The method provided in this application will now be described with reference to the accompanying drawings. Each network element in the following embodiments may possess... Figure 3 The components shown are not described in detail.

[0195] It is understood that each network element in this application (such as the first network element, application network element, second network element, third network element, or fourth network element, etc. below) can perform some or all of the steps in this application. These steps are merely examples, and this application can also perform other steps or variations of various steps. Furthermore, the steps can be performed in different orders as presented in this application, and it is possible that not all the steps in this application need to be performed.

[0196] It is understood that the methods described below in this application use network elements (such as the first network element, application network element, second network element, third network element, and fourth network element, etc.) as examples to illustrate the method, but this application does not limit the execution subject of the interaction. For example, the network element in the method provided in the following embodiments of this application can also be a chip, chip system, or processor that supports the network element in implementing the method, or it can be a logical node, logical module, or software that can implement all or part of the network element functions.

[0197] like Figure 4 The image shows a communication method provided in this application, which may include the following steps:

[0198] S401: The application network element sends the first information to the first network element. Correspondingly, the first network element receives the first information from the application network element.

[0199] In this application, the application network element can be located in the data network, and the first network element can be located in the core network. Figure 2A Taking the communication system 20 shown as an example, the application network element can be network element 202 in the communication system 20, and the first network element can be network element 201 or network element 203 in the communication system 20. Alternatively, both the application network element and the first network element are located in the core network. Figure 2B Taking the 5G network shown as an example, the application network element is... Figure 2B The first network element in the AF network is Figure 2B The UPF or NEF network elements in the network.

[0200] In this application, the first information can instruct / request / subscribe to send QoS configuration instruction information to the application network element through the user plane path.

[0201] In this application, the user plane path includes the user plane channel between the RAN node and the user plane network element, as well as the user plane channel or application programming interface (API) between the user plane network element and the application network element. The RAN node can be... Figure 2A In the communication system 20 shown, the network element 205, the user plane network element can be... Figure 2A Network element 203 in the communication system 20 shown. Alternatively, the RAN node can be... Figure 2B In the RAN node, the user plane network element can be Figure 2B UPF network elements in the network.

[0202] In this application, the user plane channel between the RAN node and the user plane network element can refer to a general packet radio service (GPRS) tunnel. For example, QoS configuration indication information can be carried in the user plane part of the GPRS tunneling protocol (GTP-U) header of one or more uplink data transmitted on the NG3 interface.

[0203] In this application, the user plane channel between the user plane network element and the application network element can refer to a real-time transport protocol (RTP) channel or a real-time transport control protocol (RTCP) channel. For example, QoS configuration indication information is carried in the RTP header or RTCP header of the data packet sent by the user plane network element to the application network element.

[0204] In this application, the API between user plane network elements and application network elements can be a direct API between them. For example, QoS configuration indication information can be carried through the Nupf_EventExposure_Notify message on the API between user plane network elements and application network elements. Alternatively, the API between user plane network elements and application network elements can also be understood as an API between network open network elements and application network elements. For example, a user plane network element sends QoS configuration indication information to a capability open network element (or a local capability open network element), and the capability open network element (or local capability open network element) sends QoS configuration indication information to the application network element using an API (such as the Nupf_AFsessionWithQoS_Notify message on the API).

[0205] In summary, for RAN nodes, sending QoS configuration indication information via the user plane path essentially involves including this indication information in the header of the data sent to user plane network elements. For user plane network elements, sending QoS configuration indication information via the user plane path essentially involves directly calling the API, or calling the API through open capability network elements, or sending the indication information to the application network element via uplink data packets. Therefore, compared to sending QoS configuration indication information via the control plane path (refer to the introduction in the alternative QoS mechanisms above), this method allows for timely delivery of the indication information to the application network element, achieving rapid transmission. In other words, sending QoS configuration indication information via the user plane path can also be understood as the network (such as RAN nodes and / or user plane network elements) providing rapid QoS notification services to application network elements.

[0206] The following explains the specific meaning of the QoS configuration indication information.

[0207] In this application, the indication information for QoS configuration can indicate QoS configuration, such as a QoS profile. The QoS profile can be a QoS profile determined according to the aforementioned alternative QoS mechanisms. The QoS profile can include at least one of QoS parameters such as GFBR, GBR, PDB, or PER. The QoS profile may also include identification information for that QoS profile. The identification information of the QoS profile is used to distinguish different QoS profiles.

[0208] As an example, the indication information for QoS configuration includes at least one of the following: QoS profile identification information, QoS configuration parameter information, identification information of the QoS flow associated with the QoS profile, identification information of the session associated with the QoS profile, identification information of the Internet Protocol (IP) flow associated with the QoS profile, QoS profile adjustment information, or QoS notification control (QNC) information. The QoS configuration parameter information includes at least one of GFBR, GBR, PDB, or PER included in the QoS profile. The QoS flow identification information is used to distinguish different QoS flows. The session associated with the QoS profile can be a Protocol Data Unit (PDU), and the session identification information is used to distinguish different sessions. The IP flow identification information is used to distinguish different IP flows. The QoS profile adjustment information or QNC information can indicate that the QoS profile has changed or been adjusted.

[0209] This application does not limit the number of QoS flows, IP flows, or sessions. For example, a QoS profile can be associated with one QoS flow, or with two or more QoS flows. Similarly, a QoS profile can be associated with one IP flow, or with two or more IP flows, and a QoS profile can be associated with one session, or with two or more sessions. Furthermore, in this application, the identification information of any IP flow can include attribute information such as the source address and destination address of the IP flow. This is a unified explanation here and will not be repeated later.

[0210] In this application, the first information can be provided to the first network element through one of the examples 1 to 4 below, instructing it to send QoS configuration instruction information to the application network element through the user plane path.

[0211] Example 1: The first information includes at least one bit, the value of which indicates that QoS configuration indication information is sent to the application network element through the user plane path. Taking the first information including 1 bit as an example, when the value of this 1 bit is "0" or "1", it indicates that QoS configuration indication information is sent to the application network element through the user plane path.

[0212] Example 2: The first information carries corresponding fields to indicate that QoS configuration information is sent to the application network element through the user plane path. For example, when the first information includes "userPlaneQoSnotification", "upf", "fastQoSnotification", "upfQoSnotification" or "up", it indicates that QoS configuration information is sent to the application network element through the user plane path.

[0213] Example 3: The first information includes one or more of the following: first indication information or identification information of at least one service flow. The first indication information is used to indicate the granularity of the QoS configuration indication information sent through the user plane path. This granularity can also be understood as the granularity of the QoS configuration file indicated by the indication information. This granularity can be a QoS flow, an IP flow, or a session (such as a PDU session). That is, the application network element instructs the sending of the above indication information to the application network element through the user plane path at the granularity of QoS flow, IP flow, or session. For example, the first indication information may include at least one bit, through which the at least one bit indicates a QoS flow, an IP flow, or a session. Taking a first indication information including 1 bit as an example, when the value of the 1 bit is "0", it indicates a QoS flow; when the value of the 1 bit is "1", it indicates an IP flow. Taking a first indication information including 2 bits as an example, when the value of the 2 bits is "00", it indicates a QoS flow; when the value of the 2 bits is "01", it indicates an IP flow; and when the value of the 2 bits is "10", it indicates a PDU session. Taking a first indication information consisting of 3 bits as an example, the first indication information can be indicated using a bitmap. Specifically, when the value of the 3 bits is "100", it indicates a QoS flow; when the value of the 3 bits is "010", it indicates an IP flow; and when the value of the 3 bits is "001", it indicates a PDU session. The aforementioned at least one service flow is a service flow associated with the QoS configuration indication information sent through the user plane path. This at least one service flow can also be understood as a service flow associated with the QoS configuration file indicated by the indication information. That is, the application network element indicates that it sends at least one service flow associated with the QoS configuration indication information to the application network element through the user plane path.

[0214] Optionally, at least one of the aforementioned service flows is a latency-sensitive service flow. This avoids the network providing fast QoS notification services to latency-insensitive service flows, thereby reducing network load and resource overhead.

[0215] Optionally, the identification information of at least one service flow is related to the granularity indicated by the first indication information. For example, when the granularity indicated by the first indication information is a QoS flow, the first information may include the identification information of at least one QoS flow; when the granularity indicated by the first indication information is an IP flow, the first information may include the identification information of at least one IP flow; and when the granularity indicated by the first indication information is a session, the first information may include the identification information of at least one session.

[0216] Example 4: Example 3 above can also be combined with Example 1 or Example 2 above. Taking the combination of Example 3 and Example 2 as an example, the first information may include "upf", first indication information (indicating granularity at the IP flow level), and identification information of IP flow 1. In this case, the first information indicates that the QoS configuration associated with IP flow 1 is sent at the IP flow level via the user plane path. Alternatively, the first information may include "upf", first indication information (indicating QoS flow level), and identification information of QoS flow 1. In this case, the first information indicates that the QoS configuration associated with QoS flow 1 is sent at the QoS flow level via the user plane path.

[0217] It is understood that Examples 1 to 4 above are merely examples of the information carried by the first information. In specific applications, the first information may carry more or less information than in the examples above, or the first information may indicate the above function in other ways, without limitation.

[0218] Optionally, the first information may also indicate the sending of QoS configuration indication information to the terminal via air interface signaling. The terminal may be... Figure 2A Terminal 206 in the communication system 20 shown, or Figure 2B The terminal in the 5G network shown. The air interface signaling includes at least one of the following: downlink control information (DCI), medium access control control element (MAC CE), PDCP control PDU message, or radio resource control (RRC) message.

[0219] As an example, the first information can indicate to the first network element, through at least one bit, that QoS configuration indication information is to be sent to the terminal via air interface signaling. For example, the first information includes 1 bit, and when the value of this 1 bit is "0" or "1", it indicates that QoS configuration indication information is to be sent to the terminal via air interface signaling.

[0220] As another example, the first information carries corresponding fields to indicate that QoS configuration information is to be sent to the terminal via air interface signaling. For example, when the first information includes "uu", "dci", "macce", "pdcppdu", or "rrc", it indicates that QoS configuration information is to be sent to the terminal via air interface signaling. "dci" can further indicate that QoS configuration information is to be sent to the terminal via DCI. "macce" can further indicate that QoS configuration information is to be sent to the terminal via MAC CE. "pdcppdu" can further indicate that QoS configuration information is to be sent to the terminal via PDCP control PDU messages. "rrc" can further indicate that QoS configuration information is to be sent to the terminal via RRC messages.

[0221] S402: The first network element sends the second information to the application network element. Correspondingly, the application network element receives the second information from the first network element.

[0222] In this application, the second information is used to indicate whether QoS configuration can be sent to the application network element through the user plane path, or the second information is used to indicate whether QoS configuration cannot be sent to the application network element through the user plane path.

[0223] One possible implementation is that after receiving the first information, the first network element can determine whether the RAN node and / or user plane network element can send QoS configuration indication information to the application network element through the user plane path.

[0224] Understandably, if the first network element determines that the RAN node and / or user plane network element can send QoS configuration indication information to the application network element through the user plane path, then the second information indicates that the QoS configuration indication information can be sent to the application network element through the user plane path. If the first network element determines that the RAN node and / or user plane network element cannot send QoS configuration indication information to the application network element through the user plane path, then the second information indicates that the QoS configuration indication information cannot be sent to the application network element through the user plane path.

[0225] As an example, the second information may include at least one bit indicating whether QoS configuration indication information can be sent to the application network element via the user plane path. Taking a second information consisting of one bit as an example, when the value of the one bit is "1", it indicates that QoS configuration indication information can be sent to the application network element via the user plane path; when the value of the one bit is "0", it indicates that QoS configuration indication information cannot be sent to the application network element via the user plane path, and vice versa.

[0226] As another example, the second information can carry corresponding fields for indication. For instance, when the second information includes "success", "yes", or "true", it indicates that QoS configuration information can be sent to the application network element through the user plane path; when the second information includes "failure", "no", or "false", it indicates that QoS configuration information cannot be sent to the application network element through the user plane path.

[0227] Optionally, the second information may further include identification information of service flows associated with QoS configuration indication information that can be sent to the application network element via the user plane path, or identification information of service flows associated with QoS configuration indication information that cannot be sent to the application network element via the user plane path. In this way, the application network element can determine which service flows have QoS configuration indication information associated with that can be sent via the user plane path and which service flows have QoS configuration indication information associated with that cannot be sent via the user plane path.

[0228] For example, the second information includes the identification information of the first service flow. In this case, the second information may indicate that the QoS configuration associated with the first service flow can be sent to the application network element through the user plane path; or, the second information may indicate that the QoS configuration associated with the first service flow cannot be sent to the application network element through the user plane path.

[0229] Understandably, when the first information includes the identification information of at least one service flow, the first service flow can belong to at least one service flow; that is, the first service flow is all or part of the at least one service flow. When the first service flow is all of the at least one service flow, it means that the network (such as RAN nodes and / or user plane network elements) can provide fast QoS notification service for all of the at least one service flow. When the first service flow is part of the at least one service flow, it means that the network can provide fast QoS notification service for part of the at least one service flow.

[0230] The following section uses the first network element as an example of a network open network element and / or a user plane network element to introduce the specific process by which the first network element determines whether the RAN node and / or the user plane network element can send QoS configuration indication information to the application network element through the user plane path.

[0231] Case 1: The first network element is an open network element.

[0232] One possible implementation is that the first network element determines whether the RAN node and the user plane network element can send QoS configuration indication information to the application network element through the user plane path, based on the subscription conditions of the application network element.

[0233] For example, when the number of times the first network element requests the fast QoS notification service (e.g., the number of times it sends the first message) is greater than or equal to a first threshold, the first network element determines that the RAN node and user plane network element cannot send QoS configuration indication information to the application network element through the user plane path; when the number of times the first network element requests the fast QoS notification service (e.g., the number of times it sends the first message) is less than the first threshold, the first network element determines that the RAN node and user plane network element can send QoS configuration indication information to the application network element through the user plane path. Alternatively, when the number of times the first network element requests the fast QoS notification service (e.g., the number of times it sends the first message) is greater than or equal to a second threshold within a certain period, the first network element determines that the RAN node and user plane network element cannot send QoS configuration indication information to the application network element through the user plane path; when the number of times the first network element requests the fast QoS notification service (e.g., the number of times it sends the first message) is less than the second threshold within a certain period, the first network element determines that the RAN node and user plane network element can send QoS configuration indication information to the application network element through the user plane path.

[0234] Another possible implementation is that the first network element determines whether the RAN node and the user plane network element can send QoS configuration indication information to the application network element through the user plane path, based on the capability information of the RAN node and the capability information of the user plane network element.

[0235] In this application, the capability information of the RAN node indicates whether the RAN node supports providing the fast QoS notification service, and the capability information of the user plane network element indicates whether the user plane network element supports providing the fast QoS notification service. For example, when the capability information of the RAN node indicates that the RAN node supports providing the fast QoS notification service, and the capability information of the user plane network element also indicates that it supports providing the fast QoS notification service, the first network element determines that the RAN node and the user plane network element can send QoS configuration indication information to the application network element through the user plane path. When either the capability information of the RAN node or the capability information of the user plane network element indicates that it does not support providing the fast QoS notification service, the first network element determines that the RAN node and the user plane network element cannot send QoS configuration indication information to the application network element through the user plane path.

[0236] Understandably, the RAN node's capability information can be sent by the RAN node to the first network element, such as through the session management network element. This capability information can be sent by the RAN node periodically or irregularly to the first network element, or it can be sent by the RAN node based on a request from the first network element. When the RAN node is overloaded, such as when the number of QoS flows requiring fast QoS notification service is large, or the number of PDU sessions requiring fast QoS notification service is large, this capability information indicates that the RAN node does not support providing fast QoS notification service. When the RAN node is under light load, such as when the number of QoS flows requiring fast QoS notification service is small, or the number of PDU sessions requiring fast QoS notification service is small, this capability information indicates that the RAN node supports providing fast QoS notification service.

[0237] Understandably, the capability information of a user plane network element can be sent from the user plane network element to the first network element, such as through a session management network element. It is also understood that this capability information can be sent by the user plane network element periodically or irregularly to the first network element, or it can be sent by the user plane network element based on a request from the first network element. When a user plane network element does not have an API to the application network element, or does not have the ability to modify the RTC header or RTCP header, or is overloaded (e.g., the user plane network element needs to provide a large number of QoS flows for fast QoS notification service, or the user plane network element needs to provide a large number of PDU sessions for fast QoS notification service, or the user plane network element needs to provide a large number of IP flows for fast QoS notification service), this capability information indicates that the user plane network element does not support providing fast QoS notification service. When a user plane network element has an API to an application network element and its load is relatively light, or when a user plane network element has the ability to modify RTC or RTCP headers and its load is relatively light, this capability information indicates that the user plane network element supports providing fast QoS notification services. Here, "relatively light load" can be understood as: the number of QoS flows for which the user plane network element needs to provide fast QoS notification services is small, or the number of PDU sessions for which the user plane network element needs to provide fast QoS notification services is small, or the number of IP flows for which the user plane network element needs to provide fast QoS notification services is small.

[0238] Another possible implementation is that the first network element determines whether the RAN node and the user plane network element can send QoS configuration indication information to the application network element through the user plane path, based on the subscription conditions of the application network element, the capability information of the RAN node and the capability information of the user plane network element.

[0239] For example, when the number of times the first network element requests the fast QoS notification service (e.g., the number of times it sends the first message) is greater than or equal to the first threshold, or when the capability information of the RAN node indicates that it does not support providing the fast QoS notification service, or when the capability information of the user plane network element indicates that it does not support providing the fast QoS notification service, the first network element determines that the RAN node and the user plane network element cannot send QoS configuration indication information to the application network element through the user plane path; when the number of times the first network element requests the fast QoS notification service (e.g., the number of times it sends the first message) is less than the first threshold, and when the capability information of the RAN node and the capability information of the user plane network element both indicate that they support providing the fast QoS notification service, the first network element determines that the RAN node and the user plane network element can send QoS configuration indication information to the application network element through the user plane path.

[0240] Understandably, after determining whether the RAN node and the user plane network element can send QoS configuration indication information to the application network element through the user plane path, the first network element can send indication information to the RAN node and the user plane network element respectively to indicate whether to send QoS configuration indication information to the application network element through the user plane path.

[0241] Scenario 2: The first network element is a user plane network element.

[0242] One possible implementation is that the first network element determines whether the RAN node and the user plane network element can send QoS configuration indication information to the application network element through the user plane path, based on the subscription conditions of the application network element. For details, please refer to the corresponding description in Case 1.

[0243] Another possible implementation is that the first network element determines whether the RAN node and user plane network element can send QoS configuration indication information to the application network element through the user plane path, based on the capability information of the RAN node and the user plane network element. Alternatively, the first network element determines whether the RAN node and user plane network element can send QoS configuration indication information to the application network element through the user plane path, based on the subscription conditions of the application network element, the capability information of the RAN node, and the capability information of the user plane network element. The above process is similar to Case 1, except that in Case 2, the capability information of the RAN node is sent by the RAN node to the first network element, such as through the user plane path or through the control plane path (e.g., through the session management network element). The capability information of the user plane network element is determined by the first network element itself.

[0244] Understandably, after determining whether the RAN node can send QoS configuration indication information to the application network element through the user plane path, the first network element can send corresponding indication information to the RAN node to indicate whether the RAN node should send QoS configuration indication information to the application network element through the user plane path.

[0245] Case 3: The first network element is either an open network element or a user plane network element.

[0246] One possible implementation is that the network open element determines whether the RAN node can send QoS configuration indication information to the application network element through the user plane path, based on the subscription conditions of the application network element and / or the capability information of the RAN node, and sends a second message to the application network element.

[0247] Understandably, once the network open element determines whether the RAN node can send QoS configuration indication information to the application network element through the user plane path, it can send corresponding indication information to the RAN node to indicate whether the RAN node should send QoS configuration indication information to the application network element through the user plane path.

[0248] One possible implementation is that the user plane network element determines whether it can send QoS configuration indication information to the application network element through the user plane path based on the subscription conditions of the application network element and / or the capability information of the user plane network element, and sends second information to the application network element.

[0249] Optionally, when a user plane network element cannot send QoS configuration indication information to an application network element through the user plane path, the user plane network element may send corresponding notification information to the RAN node to prevent the RAN node from sending QoS configuration indication information through the user plane path.

[0250] Understandably, if the first information in S401 indicates that QoS configuration indication information is sent to the terminal via air interface signaling, then the second information is also used to indicate whether QoS configuration indication information can be sent to the terminal via air interface signaling, or to indicate whether QoS configuration indication information cannot be sent to the terminal via air interface signaling.

[0251] For example, the first network element can determine whether it can send QoS configuration indication information to the terminal via air interface signaling based on the capability information of the RAN node and / or the subscription conditions of the application network element.

[0252] based on Figure 4 The method shown allows the first network element and the application network element to negotiate, based on the application network element's needs, whether to send QoS configuration indication information to the application network element via the user plane path. Therefore, Figure 4The method shown enables the RAN node to determine which method to use to send QoS configuration indication information to the application network element. During the negotiation process, the first network element considers at least one of the following: the application network element's subscription conditions, the RAN node's capability information, or the user plane network element's capability information. When the first network element considers the application network element's subscription conditions, it can prevent an application network element from subscribing to too many fast QoS notification services. When the first network element considers the RAN node's capability information, it can prevent RAN nodes that cannot provide fast QoS notification services from providing that service. When the first network element considers the user plane network element's capability information, it can prevent user plane network elements that cannot provide fast QoS notification services from providing that service.

[0253] Optional, in Figure 4 In one possible implementation of the method shown, the application network element can send first information to the first network element during the application session establishment process. For example, the first information can be carried in a subscription request message or a Hypertext Transfer Protocol (HTTP) POST request message. The subscription request message can be a Fast QoS Notification Subscription Request Message.

[0254] One possible design is that when the first network element is an open network element, the first information is carried in a separate fast QoS notification subscription request message, or in an HTTP POST request message.

[0255] In one scenario, the HTTP POST request message can be sent by an application network element to a first network element via the AsSessionWithQoS API. This HTTP POST request message can be used to request the establishment of an application session with QoS requirements (Nnef_AFsessionWithQoS_Create). The HTTP POST request message can include at least one of the following: first information, the identifier of the application network element (e.g., AS ID), the terminal address (e.g., the terminal's IP address), the notification destination address (e.g., the address of the application network element or the port number of the application on the application network element), IP flow description information, or one or more alternative QoS reference parameters (also known as alternative QoS parameter sets or alternative QoS configuration files). It is understood that when the HTTP POST request message includes the first information, it indicates that the application network element explicitly instructs the user plane path to send QoS configuration instructions. For example, the first information can be carried in the AsSessionWithQoSSubscription information element (IE). In specific applications, the application network element can also implicitly instruct the user plane path to send QoS configuration instructions. For example, an HTTP POST request message that does not include initial information indicates that the application network element instructs the user plane path to send QoS configuration indication information when the parameters in the QoS reference parameters carried in the message are greater than or less than a threshold value. For instance, when the uplink / downlink GBR carried in the message is greater than or equal to threshold 1, and / or the PDB / PER carried in the message is less than or equal to threshold 2, it instructs the user plane path to send QoS configuration indication information.

[0256] In another scenario, the HTTP POST request message can be sent by the application network element to the first network element via the ReportingNetworkStatus API. This HTTP POST request message can be used to request an open subscription to network events (Nnef_EventExposure_Subscribe). The first information can be carried in the NetworkStatusReportingSubscription IE.

[0257] Another possible design is that, when the first network element is a user plane network element, the first information is carried in a fast QoS notification subscription request message. This fast QoS notification subscription request message can be a separately defined Nupf_AFsessionWithQoS_Subscription message, or it can be carried in a Nupf_EventExposure_Subscribe message.

[0258] Understandably, when the first information is carried in a separate Fast QoS Notification Subscription Request message, the second information can be carried in a separate Fast QoS Notification Subscription Response message. Similarly, when the first information is carried in an HTTP POST request message, the second information can be carried in an HTTP POST response message.

[0259] Optional, in Figure 4 In one possible implementation of the method shown, the first network element can send at least one alternative QoS profile to the RAN node, so that the RAN node can adjust the QoS profile according to the network status and adopt... Figure 4 The method shown negotiates the transmission mode to indicate the adjusted QoS configuration file to the application network element. Specifically, it can be as follows: Figure 5 As shown, Figure 4 The method shown may also include the following steps:

[0260] S403: The first network element sends the ninth information to the second network element. Correspondingly, the second network element receives the ninth information from the first network element.

[0261] In this application, the second network element can be Figure 2A Network element 204 in the communication system 20 shown, or Figure 2B The SMF network element in the 5G network shown is illustrated. The ninth piece of information may include at least one alternative QoS profile. An alternative QoS profile may include at least one of GFBR, GBR, PDB, or PER. An alternative QoS profile may also include identification information for that profile. Furthermore, the granularity of the alternative QoS profile can be QoS flow, IP flow, or session (such as a PDU session), so an alternative QoS profile may also include identification information for QoS flows, IP flows, or sessions.

[0262] Optionally, at least one alternative QoS profile may be provided by the application network element. For example, at least one alternative QoS profile may be determined based on one or more of the alternative QoS reference parameters mentioned above.

[0263] Optionally, the ninth information may also include all or part of the information indicated by the first information. For example, the first network element may directly carry the first information in the ninth information, or the first network element may further process the first information, such as adding information, deleting information, or changing the information format, and carry the processed information in the ninth information.

[0264] One possible implementation is that the first network element sends the ninth information to the second network element through a PCF network element or a PCRF network element.

[0265] S404: The second network element sends the tenth message to the RAN node. Correspondingly, the RAN node receives the tenth message from the second network element.

[0266] In this application, the tenth information may include all or part of the information indicated by the ninth information. For example, after receiving the ninth information, the second network element may directly forward the ninth information to the RAN node. Alternatively, after receiving the ninth information, the second network element may further process the ninth information, such as adding information, deleting information, or changing the information format, and then send the processed information (i.e., the tenth information) to the RAN node. Optionally, the second network element may send the tenth information to the RAN node through the AMF network element.

[0267] Understandably, RAN nodes can identify QoS flows or sessions, but not IP flows. Therefore, the granularity of the alternative QoS profiles included in the tenth information is QoS flows or sessions. If the granularity of the alternative QoS profiles provided by the application network element is IP flows, the first network element can map the alternative QoS profiles of IP flows to alternative QoS profiles of QoS flows (e.g., replacing the IP flow identification information in the alternative QoS profiles with the identification information of the corresponding QoS flow) and then send them to the second network element. Alternatively, the second network element can map the alternative QoS profiles of IP flows to alternative QoS profiles of QoS flows (e.g., replacing the IP flow identification information in the alternative QoS profiles with the identification information of the corresponding QoS flow) and then send them to the RAN node. In this application, there is a mapping (or correspondence) relationship between IP flows and QoS flows. For example, multiple IP flows with the same or similar QoS requirements can be mapped to one QoS flow.

[0268] One possible implementation is that during the PDU session resource establishment or adjustment process, the second network element sends the tenth information to the RAN node. For example, the tenth information can be carried in a PDU session resource establishment request message or a PDU session resource adjustment request message.

[0269] Understandably, if the RAN node does not support providing fast QoS notification services, such as deciding to discontinue this service for a period of time for network optimization purposes, the RAN node can send a third indication message to the second network element to instruct it not to send QoS configuration indication messages to the application network element via the user plane path. Subsequently, the second network element can use the first network element to instruct the application network element that the RAN node cannot send QoS configuration indication messages to the application network element via the user plane path.

[0270] Understandably, if the RAN node decides (e.g., for network optimization purposes) to provide fast QoS notification service for certain QoS flows, it can send the identifier information of the QoS flows for which fast QoS notification service is supported to the second network element, or send the identifier information of the QoS flows for which fast QoS notification service is not supported. Subsequently, the second network element can send the above information to the application network element through the first network element.

[0271] S405: The RAN node determines the target QoS profile from at least one alternative QoS profile based on the network status.

[0272] Understandably, the process of S405 is similar to that of S112 above, and can be referred to the corresponding description in S112 above, so it will not be repeated here.

[0273] S406: The RAN node sends the fourth instruction information to the application network element based on the previous negotiation results. Correspondingly, the application network element receives the fourth instruction information from the RAN node.

[0274] In this application, the fourth indication information indicates a target QoS profile. For example, the fourth indication information includes at least one of the following: identification information of the target QoS profile, target QoS configuration parameter information, identification information of the QoS flow associated with the target QoS profile, identification information of the session associated with the target QoS profile, QoS profile adjustment information, or QNC information. The target QoS configuration parameter information includes at least one of GFBR, GBR, PDB, or PER included in the target QoS profile. The QoS profile adjustment information or QNC information can indicate that the QoS profile has changed or been adjusted.

[0275] Optionally, the fourth indication information may also include one or more of the following: the identification information of the application associated with the target QoS profile, the identification information of the application network element, or the time information of the RAN node determining the target QoS profile.

[0276] One possible implementation is that the RAN node sends the fourth indication information to the application network element through the control plane path. For example, the RAN node sends the fourth indication information to the session management network element, and after receiving the fourth indication information, the session management network element sends the fourth indication information to the application network element through the network open network element.

[0277] As an example, if the second information indicated above cannot send the QoS configuration indication information to the application network element through the user plane path, then the RAN node sends the fourth indication information to the application network element through the control plane path.

[0278] As another example, if the second information indicated above can send QoS configuration indication information to the application network element through the user plane path, but in S404 the RAN node decides not to support providing fast QoS notification service for network optimization purposes, the RAN node sends the fourth indication information to the application network element through the control plane path.

[0279] Another possible implementation is that the RAN node sends the fourth indication information to the user plane network element through the user plane path. For example, the RAN node can send a data packet to the user plane network element through the NG3 interface. The GTP-U header of the data packet includes the fourth indication information, so that the user plane network element can send the fourth indication information to the application network element.

[0280] For example, if the second information indication can send QoS configuration indication information to the application network element through the user plane path, then the RAN node sends the fourth indication information to the user plane network element through the user plane path.

[0281] Optionally, if the granularity indicated in the first information is a QoS flow, the RAN node can send the fourth indication information at the QoS flow granularity. The fourth indication information also includes the identification information of the QoS flow associated with the target QoS profile. If the granularity indicated in the first information is a session, the RAN node can send the fourth indication information at the session granularity. The fourth indication information also includes the identification information of the session associated with the target QoS profile.

[0282] Optionally, if the first information indicates identification information for at least one service flow, the RAN node further determines whether the service flow associated with the target QoS profile belongs to that at least one service flow. If it does, the RAN node sends fourth indication information to the application network element via the user plane path; if it does not, the RAN node sends fourth indication information to the application network element via the control plane path. The fourth indication information may also include identification information for the service flow associated with the target QoS profile. Furthermore, S401 describes that the service flow indicated by the first information can be a QoS flow, an IP flow, or a session. However, in practice, the RAN node can identify QoS flows or sessions but not IP flows. Therefore, when the service flow indicated by the first information is a QoS flow, the fourth indication information includes the identification information of the QoS flow associated with the target QoS profile; when the service flow indicated by the first information is a session, the fourth indication information includes the identification information of the session associated with the target QoS profile; and when the service flow indicated by the first information is an IP flow, the fourth indication information includes the identification information of the QoS flow associated with the target QoS profile, which is the QoS flow corresponding to the aforementioned IP flow.

[0283] Optionally, if the first information indicates that QoS configuration indication information is sent to the terminal via air interface signaling, the RAN node may also send a fourth indication information to the terminal via air interface signaling.

[0284] Understandably, after receiving the fourth indication information, the user plane network element can send it to the application network element through the user plane path. For example, the user plane network element can directly call the API to send the fourth indication information to the application network element, or the user plane network element can send the fourth indication information to the application network element through the capability open network element or the local capability open network element using the API, or the user plane network element can send a data packet to the application network element, the RTP header or RTCP header of which includes the fourth indication information.

[0285] Understandably, after receiving the fourth instruction information, the user plane network element can further process the fourth instruction information (such as adding information, deleting information, or changing the information format) and then send the processed information to the application network element.

[0286] For example, if the fourth indication information received by the user plane network element is associated with the first QoS flow, or the target QoS profile is associated with the first QoS flow, or the fourth indication information includes the identification information of the first QoS flow, then the user plane network element can map the first QoS flow to the first IP flow; that is, the indication information sent by the user plane network element to the application network element is associated with the first IP flow. The first IP flow and the first QoS flow have a mapping (or correspondence) relationship. For instance, after receiving the fourth indication information from the RAN node, the user plane network element replaces the identification information of the first QoS flow in the fourth indication information with the identification information of the first IP flow to obtain the fifth indication information, and sends the fifth indication information to the application network element. It is understood that if the granularity of the indication in the first information is an IP flow, then the user plane network element can perform the above process.

[0287] For example, if the fourth indication information includes the identification information of QoS flows (or the identification information of sessions), the user plane network element determines whether it supports providing fast QoS notification services for these QoS flows (sessions). If it supports it, the user plane network element sends the fourth indication information to the application network element through the user plane path. If it does not support it, the user plane network element deletes the identification information of the unsupported QoS flows (or sessions) and then sends the information to the application network element through the user plane path.

[0288] Understandably, after receiving the fourth indication information, the application network element can adjust service characteristics based on this information, such as adjusting the task splitting point or service traffic mode. The service traffic mode can indicate bit rate, bit rate, frame rate, or resolution, etc.

[0289] One possible design is that different alternative QoS profiles can be used to describe the QoS requirements of different task splitting points. Therefore, application network elements can determine the task splitting point corresponding to the target QoS profile based on the fourth indication information, and execute the task according to the task splitting point so that the quality of service provided by the RAN node meets the QoS requirements of the task.

[0290] Another possible design is that different alternative QoS profiles can be used to describe the QoS requirements of different service traffic patterns. Therefore, application network elements can determine the service traffic pattern corresponding to the target QoS profile based on the fourth indication information, and execute services according to the service traffic pattern so that the quality of service provided by the RAN node meets the QoS requirements of the service traffic pattern.

[0291] Optional, in Figure 4In one possible implementation of the method shown, the first network element is an open network element. After receiving the first information, the first network element can instruct other network elements, such as the second network element, to confirm whether QoS configuration indication information can be sent to the application network element through the user plane path. Confirming whether QoS configuration indication information can be sent to the application network element through the user plane path means confirming whether nodes on the user plane path (such as RAN nodes and user plane network elements) can send QoS configuration indication information to the application network element. Specifically, it can be as follows: Figure 5 As shown, Figure 4 The method shown may also include the following steps:

[0292] S401A: The first network element sends third information to the second network element based on the first information. Correspondingly, the second network element receives the third information from the first network element.

[0293] In this application, the third information indicates whether QoS configuration indication information can be sent to the application network element through the user plane path. For example, the third information indicates that the second network element can confirm whether the nodes on the user plane path (such as RAN nodes and user plane network elements) can send QoS configuration indication information to the application network element.

[0294] For example, the third information includes all or part of the information indicated by the first information. For instance, the first network element may directly carry the first information in the third information, or the first network element may further process the first information, such as adding, deleting, or changing the information format, and carry the processed information in the third information. For example, the third information includes one or more of the following: second indication information or identification information of at least one service flow. The second indication information is used to indicate the granularity of the service quality configuration indication information sent through the user plane path (such as QoS flow, IP flow, or session), and the at least one service flow may be the service flow indicated in the first information.

[0295] Optionally, the third information also includes at least one alternative QoS profile. A description of the alternative QoS profile can be found in the corresponding description in S403. It should be understood that if the first network element executes S401A, then the first network element may not execute S403.

[0296] One possible implementation is that the first network element sends third information to the second network element through a PCF network element or a PCRF network element. The second network element can be an SMF network element.

[0297] S401B: The second network element sends the fifth information to the third network element. Correspondingly, the third network element receives the fifth information from the second network element.

[0298] In this application, the fifth information instructs the third network element to send QoS configuration indication information to the application network element through the user plane path. For example, the fifth information includes all or part of the information in the third information. For instance, the second network element can directly carry the third information in the fifth information, or the second network element can further process the third information, such as adding information, deleting information, or changing the information format, and carry the processed information in the fifth information.

[0299] The second network element can be an SMF network element, and the third network element can be a RAN node or a user plane network element. When the third network element is a user plane network element, the fifth information can be carried in a session establishment request message (such as N4 Session EstablishmentRequest), a session modification request message (such as N4 Session Modification Request), a session association establishment request message (such as N4 Association Setup Request), or a session association update request message (such as N4 AssociationUpdate Request). The session establishment request message and the session association establishment request message are used to request the establishment of a session or an N4 interface. The session modification request message and the session association update request message are used to request the configuration of a session or an N4 interface. When the third network element is a RAN node, the fifth information can be carried in a session establishment request message (such as PDU SessionEstablishment Request) or a session modification request message (such as PDU Session Modification Request).

[0300] Understandably, when the third network element is a RAN node, the other descriptions in S401B can be found in the corresponding descriptions in S404. Furthermore, if the second network element executes S401B, then the second network element may not need to execute S404.

[0301] S401C: The third network element sends the sixth information to the second network element. Correspondingly, the second network element receives the sixth information from the third network element.

[0302] In this application, the sixth information is used to indicate that the third network element can send QoS configuration indication information to the application network element through the user plane path, or the sixth information is used to indicate that the third network element cannot send QoS configuration indication information to the application network element through the user plane path.

[0303] One possible implementation is that the third network element determines whether it can send QoS configuration indication information to the application network element through the user plane path based on its own capability information and / or the subscription conditions of the application network element. When the third network element is a RAN node, its capability information is the same as the RAN node's capability information; when the third network element is a user plane network element, its capability information is the same as the user plane network element's capability information. Therefore, the above process can be referenced from the corresponding description in S402 regarding whether the first network element can send QoS configuration indication information to the application network element through the user plane path.

[0304] Understandably, if the third network element determines that it can send QoS configuration indication information to the application network element through the user plane path, then the sixth information indicates that the third network element can send QoS configuration indication information to the application network element through the user plane path. If the third network element determines that it cannot send QoS configuration indication information to the application network element through the user plane path, then the sixth information indicates that the third network element cannot send QoS configuration indication information to the application network element through the user plane path.

[0305] Optionally, the sixth information may further include identification information of service flows associated with QoS configuration indication information that can be sent to the application network element via the user plane path, or identification information of service flows associated with QoS configuration indication information that cannot be sent to the application network element via the user plane path. In this way, the second network element can determine which service flows are associated with QoS configuration indication information that the third network element can or cannot send.

[0306] For example, the sixth information includes the identification information of the second service flow. In this case, the sixth information may indicate that the third network element can send the indication information of the QoS configuration associated with the second service flow to the application network element through the user plane path; or, the sixth information may indicate that the third network element cannot send the indication information of the QoS configuration associated with the second service flow to the application network element through the user plane path. The second service flow belongs to at least one of the aforementioned service flows, that is, the second service flow is all or part of the at least one service flow.

[0307] S401D: The second network element sends the seventh information to the fourth network element. Correspondingly, the fourth network element receives the seventh information from the second network element.

[0308] In this application, the seventh information instructs the fourth network element to send QoS configuration indication information to the application network element through the user plane path. For example, the seventh information may include all or part of the information in the third information. For instance, the second network element may directly include the third information in the seventh information, or the second network element may further process the third information, such as adding, deleting, or changing its format, and include the processed information in the seventh information.

[0309] One possible design is that when the third network element is a RAN node, the fourth network element is a user plane network element, and when the third network element is a user plane network element, the fourth network element is a RAN node. Figure 5 The diagram is drawn with the third network element as the user plane network element and the fourth network element as the RAN node as an example.

[0310] Optionally, when the fourth network element is a user plane network element, the seventh information can be carried in a session establishment request message (such as N4 Session Establishment Request), a session modification request message (such as N4 Session Modification Request), a session association establishment request message (such as N4 Association Setup Request), or a session association update request message (such as N4 Association Update Request). When the fourth network element is a RAN node, the seventh information can be carried in a session establishment request message (such as PDU Session Establishment Request) or a session modification request message (such as PDU Session Modification Request).

[0311] Understandably, when the fourth network element is a RAN node, other descriptions of S401D can be found in the corresponding descriptions in S404. Moreover, if the second network element executes S401D, then the second network element may not execute S404.

[0312] As is understood, the user plane path in this application essentially includes two paths: one between the RAN node and the user plane network element, and the other between the user plane network element and the application network element. Therefore, the QoS configuration indication information can only be sent to the application network element via the user plane path when both the RAN node and the user plane network element can send the QoS configuration indication information. Thus, to save signaling overhead, the second network element can send the seventh information to the fourth network element if the sixth information indicates that the third network element can send the QoS configuration indication information to the application network element via the user plane path. If the sixth information indicates that the third network element cannot send the QoS configuration indication information to the application network element via the user plane path, then the second network element will not send the seventh information to the fourth network element.

[0313] Optionally, the seventh information may also include the identification information of the second service flow, so that the fourth network element can determine whether it can send the indication information of the QoS configuration associated with the second service flow to the application network element through the user plane path.

[0314] S401E: The fourth network element sends the eighth message to the second network element. Correspondingly, the second network element receives the eighth message from the fourth network element.

[0315] In this application, the eighth information is used to indicate that the fourth network element can send QoS configuration indication information to the application network element through the user plane path, or the eighth information is used to indicate that the fourth network element cannot send QoS configuration indication information to the application network element through the user plane path.

[0316] One possible implementation is that the fourth network element determines whether it can send QoS configuration indication information to the application network element through the user plane path based on its own capability information and / or the subscription conditions of the application network element. When the fourth network element is a RAN node, its capability information is the same as the RAN node's capability information; when the fourth network element is a user plane network element, its capability information is the same as the user plane network element's capability information. Therefore, the above process can be referenced from the corresponding description in S402 regarding whether the first network element can send QoS configuration indication information to the application network element through the user plane path.

[0317] Understandably, if the fourth network element determines that it can send QoS configuration indication information to the application network element through the user plane path, then the eighth information indicates that the fourth network element can send QoS configuration indication information to the application network element through the user plane path. If the fourth network element determines that it cannot send QoS configuration indication information to the application network element through the user plane path, then the fourth information indicates that the fourth network element cannot send QoS configuration indication information to the application network element through the user plane path.

[0318] Optionally, the eighth information may further include identification information of service flows associated with QoS configuration indication information that can be sent to the application network element via the user plane path, or identification information of service flows associated with QoS configuration indication information that cannot be sent to the application network element via the user plane path. In this way, the second network element can determine which service flows' QoS configuration indication information can or cannot be sent by the fourth network element.

[0319] For example, the eighth information includes the identification information of the third service flow. In this case, the eighth information may indicate that the fourth network element can send the indication information of the QoS configuration associated with the third service flow to the application network element through the user plane path; or, the eighth information may indicate that the fourth network element cannot send the indication information of the QoS configuration associated with the third service flow to the application network element through the user plane path. The third service flow belongs to at least one of the above-mentioned service flows (i.e., the third service flow is all or part of the service flows in at least one service flow), or the third service flow belongs to the second service flow (i.e., the third service flow is all or part of the service flows in the second service flow).

[0320] S401F: The second network element sends the fourth information to the first network element. Correspondingly, the first network element receives the fourth information from the second network element.

[0321] One possible implementation is that the second network element sends the fourth information to the first network element based on the sixth and eighth information.

[0322] In this application, the fourth information is used to indicate whether QoS configuration can be sent to the application network element through the user plane path, or to indicate whether QoS configuration cannot be sent to the application network element through the user plane path.

[0323] Understandably, the fourth information can be used to determine the second information. For example, when the fourth information indicates that QoS configuration indication information can be sent to the application network element through the user plane path, the second information is used to indicate that QoS configuration indication information can be sent to the application network element through the user plane path; when the fourth information indicates that QoS configuration indication information cannot be sent to the application network element through the user plane path, the second information is used to indicate that QoS configuration indication information cannot be sent to the application network element through the user plane path.

[0324] Understandably, if the second information includes the identifier information of the first service flow, the second network element can determine the first service flow based on the third service flow, such that the third service flow is the first service flow. Alternatively, the second network element can determine the first service flow based on both the second and third service flows, such that the first service flow belongs to both the second and third service flows, meaning that the first service flow is a service flow included by both the second and third service flows.

[0325] Optional, in Figure 5 In one possible implementation of the method shown, the RAN node can have Figure 1A The architecture shown is as follows. In this case, the target QoS profile determined in S405 can be determined by the O-DU, O-CU, Near-RT RIC, or SMO modules in the RAN node. The following sections will elaborate on this in conjunction with S404 to S406.

[0326] Scenario A: O-DU determines the target QoS profile.

[0327] One possible implementation is that in S404, the second network element sends the tenth information to the O-CU. After receiving the tenth information, the O-CU sends the tenth information to the O-DU through the F1 interface. Alternatively, the second network element sends the tenth information directly to the O-DU.

[0328] One possible implementation, in S405, is that the O-DU determines the target QoS profile from at least one alternative QoS profile based on the network status.

[0329] In one possible implementation, in S406, the O-DU sends the fourth indication information to the O-CU through the F1 interface. After receiving the fourth indication information, the O-CU sends the fourth indication information to the user plane network element through the user plane path.

[0330] Optionally, the O-DU can also send a fourth indication message to the terminal. For example, the O-DU sends the fourth indication message to the terminal via DCI or MAC CE messages. Another example is that the O-DU sends the fourth indication message to the O-CU via the F1 interface, so that the O-CU can send the fourth indication message to the terminal via RRC messages or PDCP control PDU messages. Understandably, if the O-CU is further separated into O-CU-CP and O-CU-UP, then O-CU-CP sends the fourth indication message to the terminal via RRC messages, or O-CU-UP sends the fourth indication message to the terminal via PDCP control PDU messages.

[0331] Scenario B: O-CU determines the target QoS profile.

[0332] One possible implementation is that in S404, the second network element sends the tenth information to the O-DU. After receiving the tenth information, the O-DU sends the tenth information to the O-CU through the F1 interface. Alternatively, the second network element sends the tenth information directly to the O-CU.

[0333] One possible implementation, in S405, is that the O-CU determines the target QoS profile from at least one alternative QoS profile based on the network status.

[0334] One possible implementation is that in S406, the O-CU sends the fourth instruction information to the user plane network element through the user plane path.

[0335] Optionally, the O-CU can also send a fourth indication message to the terminal. For example, the O-CU sends the fourth indication message to the terminal via an RRC message or a PDCPcontrol PDU message. Understandably, if the O-CU is further divided into O-CU-CP and O-CU-UP, then O-CU-CP sends the fourth indication message to the terminal via an RRC message, or O-CU-UP sends the fourth indication message to the terminal via a PDCPcontrol PDU message. As another example, the O-CU sends the fourth indication message to the O-DU via the F1 interface, so that the O-DU can send the fourth indication message to the terminal via a DCI or MAC CE message.

[0336] It is understandable that, in addition to the O-RAN architecture, the RAN node of this application can also have a CU-DU separation architecture. For example, the RAN node can be separated into one CU and at least one DU. The descriptions of cases A and B above also apply to RAN nodes under the CU-DU separation architecture. For example, "O-CU" in cases A and B can be replaced with "CU in the CU-DU separation architecture", and "O-DU" in cases A and B can be replaced with "DU in the CU-DU separation architecture".

[0337] Case C: Near-RT RIC determines the target QoS profile.

[0338] One possible implementation in S404 is that the second network element sends the tenth information to the O-CU. After receiving the tenth information, the O-CU forwards it to the Near-RT RIC via the E2 interface. Alternatively, the second network element sends the tenth information to the O-DU. After receiving the tenth information, the O-DU forwards it to the Near-RT RIC via the E2 interface.

[0339] One possible implementation, in S405, is that Near-RT RIC determines the target QoS profile from at least one alternative QoS profile based on network conditions.

[0340] Understandably, to implement S405, the O-DU needs to send network element status information to the Near-RT RIC before S405 is implemented. For example, the O-DU can report network element status information to the Near-RT RIC through the E2 interface. Alternatively, the O-DU can first send network element status information to the O-CU through the F1 interface, and then the O-CU can forward the information to the Near-RT RIC through the E2 interface.

[0341] One possible implementation, in S406, is that the Near-RT RIC sends the fourth indication information to the O-CU via the E2 interface, so that the O-CU can send the fourth indication information to the user plane network element via the user plane path. Alternatively, the Near-RT RIC sends the fourth indication information to the O-DU via the E2 interface, and after receiving the fourth indication information, the O-DU sends the fourth indication information to the O-CU via the F1 interface, so that the O-CU can send the fourth indication information to the user plane network element via the user plane path.

[0342] Optionally, the O-DU or O-CU may also send a fourth instruction message to the terminal. For details, please refer to the descriptions in Situation A or Situation B above; further elaboration is unnecessary.

[0343] Case D: The SMO module determines the target QoS profile.

[0344] One possible implementation, in S404, is that the second network element sends the tenth information to the O-CU. After receiving the tenth information, the O-CU forwards it to the SMO module through the O1 interface. Alternatively, the second network element sends the tenth information to the O-DU. After receiving the tenth information, the O-DU forwards it to the SMO module through the O1 interface. Or, the second network element sends the tenth information to the Near-RT RIC in the manner described in Case C. After receiving the tenth information, the Near-RT RIC sends it to the SMO module through the A1 (or O1) interface.

[0345] One possible implementation, in S405, is that the SMO module determines the target QoS profile from at least one alternative QoS profile based on the network status.

[0346] Understandably, to implement S405, the O-DU needs to send network element status information to the SMO module before S405 is implemented. For example, the O-DU can send the network element status information to the Near-RT RIC in the manner described in Case C, and then the Near-RT RIC sends it to the SMO module through the A1 (or O1) interface. Alternatively, the O-DU can report the network element status information to the SMO module through the O1 interface. Or, the O-DU can first send the network element status information to the O-CU through the F1 interface, and then the O-CU forwards the information to the SMO module through the O1 interface.

[0347] One possible implementation, in S406, is that the SMO module sends the fourth indication information to the O-CU via the O1 interface, so that the O-CU can send the fourth indication information to the user plane network element via the user plane path. Alternatively, the SMO module sends the fourth indication information to the O-DU via the O1 interface. After receiving the fourth indication information, the O-DU sends the fourth indication information to the O-CU via the F1 interface, so that the O-CU can send the fourth indication information to the user plane network element via the user plane path. Alternatively, the SMO module sends the fourth indication information to the Near-RT RIC via the A1 (or O1) interface. After receiving the fourth indication information, the Near-RT RIC can send the fourth indication information to the O-CU or O-DU using the method described in Case C.

[0348] Optionally, the O-DU or O-CU may also send a fourth instruction message to the terminal. For details, please refer to the descriptions in Situation A or Situation B above; further elaboration is unnecessary.

[0349] It is understood that the operations performed by the Near-RT RIC in this application can also be performed by the QoS management function, wireless connectivity management function, or interference management function of the Near-RT RIC. Similarly, the operations performed by the SMO module in this application can also be performed by the Non-RT RIC function or configuration function of the SMO module.

[0350] Understandably, the actions of the application network element, the first network element, or the second network element in the above steps can be performed by... Figure 3 The processor 301 in the communication device 30 shown calls the application code stored in the memory 303 to execute it, and this application does not impose any restrictions on this.

[0351] The various embodiments mentioned above in this application can be combined without contradiction, and no limitation is imposed.

[0352] The above mainly describes the solution provided in this application from the perspective of interaction between various network elements. Correspondingly, this application also provides a communication device, which can be the first network element in the above method embodiments, or a device containing the first network element, or a component usable in the first network element; or, the communication device can be an application network element in the above method embodiments, or a device containing the application network element, or a component usable in the application network element; or, the communication device can be the second network element in the above method embodiments, or a device containing the second network element, or a component usable in the second network element. It is understood that the first network element, application network element, or second network element, etc., in order to achieve the above functions, includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, in conjunction with the unit and algorithm operations of the various examples described in the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0353] This application can divide the first network element, application network element, or second network element into functional modules based on the above method examples. 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 as software functional modules. It is understood that the module division in this application is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0354] For example, when dividing the functional modules using an integrated approach. Figure 6 A schematic diagram of a communication device 60 is shown. The communication device 60 includes a processing module 601 and an interface module 602. The processing module 601, also called a processing unit, is used to perform operations other than transmission and reception operations, and may be, for example, a processing circuit or a processor. The interface module 602, also called an interface unit, is used to perform transmission and reception operations, and may be, for example, an interface circuit, a transceiver, a transceiver unit, or a communication interface.

[0355] In some embodiments, the communication device 60 may further include a storage module. Figure 6 (Not shown in the image) is used to store program instructions and data.

[0356] For example, the communication device 60 is used to implement the functions of the first network element. The communication device 60 is, for example, a... Figure 4 The illustrated embodiments or Figure 5 The first network element described in the illustrated embodiment.

[0357] The processing module 601 is used to control the interface module 602 to receive first information from the application network element. The first information indicates that QoS configuration information is sent to the application network element through the user plane path. For example, the processing module 601 can be used to execute S401.

[0358] The processing module 601 is further configured to control the interface module 602 to send second information to the application network element. The second information indicates whether QoS configuration can be sent to the application network element via the user plane path, or indicates whether QoS configuration cannot be sent to the application network element via the user plane path. For example, the processing module 601 can also execute S402.

[0359] When used to implement the functions of the first network element, other functions that the communication device 60 can implement can be found in [reference needed]. Figure 4 The illustrated embodiments or Figure 5 The relevant descriptions of the embodiments shown will not be elaborated upon further.

[0360] Alternatively, by way of example, communication device 60 is used to implement the functions of application network elements. Communication device 60 is, for example, a... Figure 4 The illustrated embodiments or Figure 5 The application network element described in the illustrated embodiment.

[0361] The processing module 601 is used to control the interface module 602 to send first information to the first network element in the core network. The first information indicates that QoS configuration information is sent to the communication device 60 via the user plane path. For example, the processing module 601 can be used to execute S401.

[0362] The processing module 601 is further configured to control the interface module 602 to receive second information from the first network element. The second information indicates whether QoS configuration can be sent to the communication device 60 via the user plane path, or indicates whether QoS configuration cannot be sent to the communication device 60 via the user plane path. For example, the processing module 601 can also execute S402.

[0363] When used to implement the functions of application network elements, for other functions that the communication device 60 can perform, please refer to [reference needed]. Figure 4 The illustrated embodiments or Figure 5 The relevant descriptions of the embodiments shown will not be elaborated upon further.

[0364] Alternatively, by way of example, the communication device 60 is used to implement the function of the second network element. The communication device 60 is, for example, a... Figure 5 The second network element described in the illustrated embodiment.

[0365] The processing module 601 controls the interface module 602 to receive third information from a first network element in the core network. This third information indicates whether QoS configuration can be sent to the application network element via the user plane path. For example, the processing module 601 can execute S401A.

[0366] The processing module 601 is also used to control the interface module 602 to send fifth information to the third network element based on the third information. The fifth information instructs the third network element to send QoS configuration indication information to the application network element through the user plane path. For example, the processing module 601 can also be used to execute S401B.

[0367] The processing module 601 is further configured to control the interface module 602 to receive sixth information from the third network element. This sixth information indicates whether the third network element can send QoS configuration indication information to the application network element via the user plane path, or whether it cannot send QoS configuration indication information to the application network element via the user plane path. For example, the processing module 601 can also execute S401C.

[0368] The processing module 601 is also used to control the interface module 602 to send seventh information to the fourth network element based on the third information. The seventh information instructs the fourth network element to send QoS configuration indication information to the application network element through the user plane path. For example, the processing module 601 can also be used to execute S401D.

[0369] The processing module 601 is further configured to control the interface module 602 to receive the eighth information from the fourth network element. The eighth information is used to indicate whether the fourth network element can send QoS configuration indication information to the application network element via the user plane path, or to indicate whether the fourth network element cannot send QoS configuration indication information to the application network element via the user plane path. For example, the processing module 601 can also be used to execute S401E.

[0370] The processing module 601 is further configured to control the interface module 602 to send fourth information to the first network element based on the sixth and eighth information. The fourth information indicates whether QoS configuration can be sent to the application network element via the user plane path, or indicates whether QoS configuration cannot be sent to the application network element via the user plane path. For example, the processing module 601 can also execute S401F.

[0371] When used to implement the functions of the second network element, for other functions that the communication device 60 can perform, please refer to [reference needed]. Figure 5 The relevant descriptions of the embodiments shown will not be elaborated upon further.

[0372] In a simplified embodiment, those skilled in the art will recognize that the communication device 60 can employ... Figure 3 The form shown. For example, Figure 3 The processor 301 can call computer execution instructions stored in the memory 303 to cause the communication device 60 to execute the method described in the above method embodiment.

[0373] For example, Figure 6 The functions / implementation processes of the processing module 601 and the interface module 602 can be accessed through... Figure 3 The processor 301 in the memory calls computer execution instructions stored in the memory 303 to implement the function. Alternatively, Figure 6 The function / implementation process of the processing module 601 can be achieved through... Figure 3 The processor 301 in the memory calls computer execution instructions stored in the memory 303 to implement this. Figure 6 The function / implementation process of interface module 602 can be achieved through... Figure 3 Figure 6 It is implemented using the communication interface 304.

[0374] It is understood that one or more of the above modules or units can be implemented by software, hardware, or a combination of both. When any of the above modules or units are implemented by software, the software exists as computer program instructions and is stored in memory. The processor can be used to execute the program instructions and implement the above method flow. The processor can be built into a system-on-a-chip (SoC) or ASIC, or it can be a separate semiconductor chip. In addition to the core that executes the software instructions for computation or processing, the processor may further include necessary hardware accelerators, such as field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), or logic circuits that implement dedicated logic operations.

[0375] When the above modules or units are implemented in hardware, the hardware can be any one or any combination of a CPU, microprocessor, digital signal processing (DSP) chip, microcontroller unit (MCU), artificial intelligence processor, ASIC, SoC, FPGA, PLD, application-specific digital circuit, hardware accelerator, or non-integrated discrete device, which can run the necessary software or perform the above method flow independently of software.

[0376] Optionally, this application also provides a chip system, including: at least one processor and an interface, wherein the at least one processor is coupled to a memory via the interface, and when the at least one processor executes a computer program or instructions in the memory, the method in any of the above method embodiments is executed. In one possible implementation, the chip system further includes a memory. Optionally, the chip system may be composed of chips or may include chips and other discrete devices; this application does not specifically limit this.

[0377] Optionally, this application also provides a computer-readable storage medium. All or part of the processes in the above method embodiments can be implemented by a computer program instructing related hardware. This program can be stored in the aforementioned computer-readable storage medium. When executed, the program can include the processes described in the above method embodiments. The computer-readable storage medium can be an internal storage unit of the communication device in any of the foregoing embodiments, such as the hard disk or memory of the communication device. The aforementioned computer-readable storage medium can also be an external storage device of the communication device, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the communication device. Further, the aforementioned computer-readable storage medium can include both internal storage units and external storage devices of the communication device. The aforementioned computer-readable storage medium is used to store the aforementioned computer program and other programs and data required by the communication device. The aforementioned computer-readable storage medium can also be used to temporarily store data that has been output or will be output.

[0378] Optionally, this application also provides a computer program product. All or part of the processes in the above method embodiments can be executed by a computer program instructing related hardware. This program can be stored in the above computer program product, and when executed, it can include the processes described in the above method embodiments.

[0379] Optionally, this application also provides computer instructions. All or part of the processes in the above method embodiments can be executed by computer instructions instructing related hardware (such as a computer, processor, first network element, application network element, or second network element, etc.). The program can be stored in the aforementioned computer-readable storage medium or the aforementioned computer program product.

[0380] Optionally, this application also provides a communication system, including at least two of the following: a first network element, an application network element, or a second network element in the above embodiments.

[0381] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0382] It is understood that the term "connection" in this application can refer to a direct connection or an indirect connection; furthermore, it can refer to an electrical connection or a communication connection. For example, the connection of two electrical components A and B can refer to a direct connection between A and B, or an indirect connection between A and B through other electrical components or connection media, enabling the transmission of electrical signals between A and B; similarly, the connection of two devices A and B can refer to a direct connection between A and B, or an indirect connection between A and B through other communication devices or communication media, enabling communication between A and B.

[0383] It is understood that the message names between various network elements or the names of various parameters in the messages in the above embodiments of this application are just examples, and other names may be used in the specific implementation. This application does not make any specific limitations on this.

[0384] It is understood that in this application, " / " can indicate that the objects before and after it are in an "or" relationship. For example, A / B can mean A or B. "And / or" can be used to describe three relationships between the related objects. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. Here, A and B can be singular or plural. Furthermore, expressions like "at least one of A, B, and C" or "at least one of A, B, or C" are generally used to indicate any of the following: A exists alone; B exists alone; C exists alone; A and B exist simultaneously; A and C exist simultaneously; B and C exist simultaneously; A, B, and C exist simultaneously. The above examples using three elements (A, B, and C) illustrate the optional entries for this item. When the expression contains more elements, its meaning can be obtained according to the aforementioned rules.

[0385] To facilitate the description of the technical solutions of this application, the terms "first" and "second" may be used to distinguish technical features with the same or similar functions. The terms "first" and "second" do not limit the number or execution order, nor do they imply that they are necessarily different. In this application, the terms "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design scheme described as "exemplary" or "for example" should not be construed as being more preferred or advantageous than other embodiments or design schemes. The use of "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner for ease of understanding.

[0386] It is understood that the term "embodiment" used throughout the specification means that a specific feature, structure, or characteristic related to an embodiment is included in at least one embodiment of this application. Therefore, various embodiments throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It is understood that in the various embodiments of this application, the sequence number of each process does not imply a sequential order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of this application.

[0387] It is understood that in this application, "for indicating" can include direct and indirect indication, as well as explicit and implicit indication. When describing a certain indication information for indicating A, it can include whether the indication information directly or indirectly indicates A, but does not necessarily mean that the indication information carries A. The information indicated by a certain piece of information (such as the first indication information mentioned above) is called the information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated, such as, but not limited to, directly indicating the information to be indicated, such as the information to be indicated itself or its index. It can also indirectly indicate the information to be indicated by indicating other information, where there is a correlation between the other information and the information to be indicated. It can also indicate only a part of the information to be indicated, while the other parts are known or pre-agreed upon. For example, the indication of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing the indication overhead to some extent.

[0388] It is understood that in this application, "when," "under the circumstances," "if," and "if" all refer to the corresponding processing that will be carried out under certain objective circumstances, and are not time-limited, nor do they require that there must be a judgment action when implemented, nor do they imply any other limitations.

[0389] In this application, "greater than or equal to" can be replaced with "greater than" or "equal to"; "less than or equal to" can be replaced with "less than" or "equal to". For example, "A is greater than or equal to B" can be replaced with "A is greater than B" or "A is equal to B"; "A is less than or equal to B" can be replaced with "A is less than B" or "A is equal to B".

[0390] It is understood that some optional features in this application can be implemented independently in certain scenarios without relying on other features, such as the current underlying solution, to solve corresponding technical problems and achieve corresponding effects. Alternatively, they can be combined with other features as needed in other scenarios. Correspondingly, the apparatus provided in this application can also implement these features or functions, which will not be elaborated upon here. For example, S401B to S401E in this application can be implemented without relying on S401 to S401A. That is, the second network element can independently initiate a process to confirm whether the RAN node and the user plane network element can send QoS configuration indication information to the application network element through the user plane path.

[0391] It is understood that the same step or step with the same function or technical feature in this application can be referenced and learned from each other in different embodiments.

[0392] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0393] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0394] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0395] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope 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 by comprising: A first network element applied in a core network, the method comprises: receiving first information from an application network element, the first information indicating that indication information of a quality of service configuration is sent to the application network element through a user plane path; sending second information to the application network element, the second information being used for indicating that indication information of a quality of service configuration can be sent to the application network element through a user plane path, or the second information being used for indicating that indication information of a quality of service configuration cannot be sent to the application network element through a user plane path.

2. The method of claim 1, wherein, The first information comprises one or more of the following: first indication information or identification information of at least one service flow; wherein the first indication information is used for indicating granularity of indication information of a quality of service configuration sent through a user plane path, and the at least one service flow is a service flow associated with the indication information of a quality of service configuration sent through a user plane path.

3. The method of claim 2, wherein, The second information comprises identification information of a first service flow, and the first service flow belongs to the at least one service flow; The second information used for indicating that indication information of a quality of service configuration can be sent to the application network element through a user plane path comprises: the second information used for indicating that indication information of a quality of service configuration associated with the first service flow can be sent to the application network element through a user plane path; The second information used for indicating that indication information of a quality of service configuration cannot be sent to the application network element through a user plane path comprises: the second information used for indicating that indication information of a quality of service configuration associated with the first service flow cannot be sent to the application network element through a user plane path.

4. The method according to claim 2 or 3, characterized in that, The granularity of the indication information of a quality of service configuration sent through a user plane path is a quality of service flow or an Internet protocol flow.

5. The method according to any one of claims 1-4, characterized in that, The method further comprises: sending third information to a second network element in the core network according to the first information, the third information indicating confirmation of whether indication information of a quality of service configuration can be sent to the application network element through a user plane path; receiving fourth information from the second network element, the fourth information being used for indicating that indication information of a quality of service configuration can be sent to the application network element through a user plane path, or the fourth information being used for indicating that indication information of a quality of service configuration cannot be sent to the application network element through a user plane path; when the fourth information indicates that indication information of a quality of service configuration can be sent to the application network element through a user plane path, the second information is used for indicating that indication information of a quality of service configuration can be sent to the application network element through a user plane path; when the fourth information indicates that indication information of a quality of service configuration cannot be sent to the application network element through a user plane path, the second information is used for indicating that indication information of a quality of service configuration cannot be sent to the application network element through a user plane path.

6. The method of claim 5, wherein, The third information indicating confirmation of whether indication information of a quality of service configuration can be sent to the application network element through a user plane path comprises: The third information indicates confirmation of whether a node on a user plane path can send indication information of a quality of service configuration to the application network element.

7. The method according to any one of claims 1 to 6, characterized in that, The first information is carried in a subscription request message or a hypertext transfer protocol POST request message.

8. The method according to any one of claims 1-7, characterized in that, The first information further indicates indication information of the service quality configuration sent to the terminal through air interface signaling.

9. The method according to any one of claims 1-8, characterized in that, The first network element is a user plane network element or a network exposure network element.

10. The method of claim 9, wherein, The first network element is a user plane network element, and the second information is used for indicating indication information of the service quality configuration capable of being sent to the application network element through the user plane path. Receiving indication information of the service quality configuration of the first service quality flow associated from a radio access network node; Sending indication information of the service quality configuration of the first Internet protocol flow associated to the application network element, the first service quality flow and the first Internet protocol flow having a mapping relationship.

11. The method according to any one of claims 1-10, characterized in that, The user plane path includes a user plane channel between the radio access network node and the user plane network element, and a user plane channel or an application program interface between the user plane network element and the application network element.

12. A communication method characterized by comprising: Applied to an application network element, the method comprises: Sending first information to a first network element in a core network, the first information indicating indication information of the service quality configuration sent to the application network element through a user plane path; Receiving second information from the first network element, the second information being used for indicating indication information of the service quality configuration capable of being sent to the application network element through the user plane path, or the second information being used for indicating indication information of the service quality configuration incapable of being sent to the application network element through the user plane path.

13. The method of claim 12, wherein, The first information comprises one or more of the following: first indication information or identification information of at least one service flow; wherein the first indication information is used for indicating granularity of the indication information of the service quality configuration sent through the user plane path, and the at least one service flow is a service flow associated with the indication information of the service quality configuration sent through the user plane path.

14. The method of claim 13, wherein, The second information comprises identification information of a first service flow, and the first service flow belongs to the at least one service flow; The second information is used for indicating indication information of the service quality configuration capable of being sent to the application network element through the user plane path, comprising that the second information is used for indicating indication information of the service quality configuration associated with the first service flow capable of being sent to the application network element through the user plane path; The second information is used for indicating indication information of the service quality configuration incapable of being sent to the application network element through the user plane path, comprising that the second information is used for indicating indication information of the service quality configuration associated with the first service flow incapable of being sent to the application network element through the user plane path.

15. The method according to claim 13 or 14, characterized in that, The granularity of the indication information of the service quality configuration sent through the user plane path is a service quality flow or an Internet protocol flow.

16. The method according to any one of claims 12-15, characterized in that, The first information is carried in a subscription request message or a hypertext transfer protocol POST request message.

17. The method according to any one of claims 12-16, characterized by, The first information further indicates indication information of the service quality configuration sent to the terminal through air interface signaling.

18. The method according to any one of claims 12-17, characterized by, The first network element is a user plane network element or a network exposure network element.

19. The method according to any one of claims 12-18, characterized by, The user plane path includes a user plane channel between the radio access network node and the user plane network element, and a user plane channel or an application program interface between the user plane network element and the application network element.

20. A communications device, characterized by comprising means or modules for performing the method of any one of claims 1 to 11, or comprising means or modules for performing the method of any one of claims 12 to 19.

21. A communications device, characterized by comprising: a processor coupled with a memory for storing programs or instructions which, when executed by the processor, cause the apparatus to perform the method of any one of claims 1 to 11, or the method of any one of claims 12 to 19.

22. A computer readable storage medium having stored thereon a computer program or instructions, characterized in that, The computer program or instructions, when executed, cause a computer to perform the method of any one of claims 1 to 11, or the method of any one of claims 12 to 19.

23. A computer program product comprising computer program code in said computer program product, characterised in that, The computer program code, when running on a computer, causes the computer to implement the method of any one of claims 1 to 11, or the method of any one of claims 12 to 19.

Images