Communication method and apparatus

By coordinating the management of QoS flows among policy control function network elements in different access network devices, the problem of resource waste was solved, and the normal operation of application services was achieved.

WO2026045604A1PCT designated stage Publication Date: 2026-03-05HUAWEI TECH CO LTD
View PDF 4 Cites 0 Cited by

Patent Information

Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-06-28
Publication Date
2026-03-05

AI Technical Summary

Technical Problem

In multiple QoS flows of application services managed by different access network devices, if the QoS flow managed by one access network device is abnormal, the QoS flow managed by another access network device will continue to be transmitted, resulting in resource waste.

Method used

The first policy control function network element receives anomaly indication information, determines the associated second quality of service flow, and sends indication information to the second policy control function network element, instructing to perform anomaly handling, such as stopping transmission or releasing resources, in order to coordinate the management of multiple QoS flows of the same application service.

Benefits of technology

This reduces resource waste, ensures the normal operation of application services, and avoids situations where other QoS flows continue to be transmitted due to an anomaly in one QoS flow.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2025105173_05032026_PF_FP_ABST
    Figure CN2025105173_05032026_PF_FP_ABST
Patent Text Reader

Abstract

The present application discloses a communication method and apparatus. The method is applied to a first policy control function network element. The method comprises: receiving a first message from a session management network element, wherein the first message comprises first indication information for indicating that an anomaly occurs in a first quality of service (QoS) flow; determining that the first QoS flow is associated with a second QoS flow; and sending a second message to a second policy control function network element, wherein the second message comprises second instruction information for instructing the second policy control function network element to perform first processing (for example, stopping transmission, releasing resources, and adjusting a configuration) on the second QoS flow. In the present application, if the anomaly occurs in the first QoS flow, an access network device managing the first QoS flow reports the first QoS flow to the first policy control function network element by means of the session management network element, and the first policy control function network element notifies the second policy control function network element to perform anomaly processing on the second QoS flow associated with the first QoS flow, thereby avoiding resource waste.
Need to check novelty before this filing date? Find Prior Art

Description

A communication method and apparatus

[0001] Cross-reference to related applications

[0002] This application claims priority to Chinese Patent Application No. 202411218742.1, filed with the State Intellectual Property Office of the People's Republic of China on August 30, 2024, entitled "A Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

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

[0004] Quality of Service (QoS) control is a technique used to address network latency, congestion, packet loss, jitter, and other issues, aiming to provide better service capabilities for specified network communications. The finest granularity of QoS control is the QoS flow. Application service flows are carried through QoS flows. Multiple service flows with the same QoS requirements can be mapped to the same QoS flow.

[0005] A single application service can correspond to multiple service streams. For example, extended reality (XR) services correspond to video data streams, audio data streams, and sensor data streams. These service streams may have different QoS requirements, meaning that multiple service streams of the same application service can be mapped to different QoS streams; that is, one application service can correspond to multiple QoS streams. The QoS streams corresponding to an application service need to be managed collaboratively to ensure the normal operation of the application service's service streams. For example, if some QoS streams among the multiple QoS streams corresponding to an application service cannot be transmitted due to transmission resource reasons, then there is no need for the remaining QoS streams to continue transmitting.

[0006] However, multiple QoS flows corresponding to an application service may be managed by different access network devices. One access network device only manages QoS flows based on the policies issued by the core network device, and does not adjust its policies based on the QoS flows managed by another access network device. Therefore, when the QoS flow corresponding to an application service managed by one access network device cannot be transmitted, the QoS flow corresponding to the same application service managed by another access network device will still continue to be transmitted, resulting in wasted resources. Summary of the Invention

[0007] This application provides a communication method and apparatus to solve the problem of resource waste.

[0008] In a first aspect, embodiments of this application provide a communication method, which can be executed by a first policy control function network element or by a component of the first policy control function network element. The method includes: receiving a first message from a session management network element, the first message including first indication information, the first indication information indicating an anomaly in a first quality of service (QoS) flow; determining that the first QoS flow is associated with a second QoS flow; and sending a second message to a second policy control function network element, the second message including second indication information, the second indication information instructing the second policy control function network element to perform a first process on the second QoS flow, the first process including one or more of stopping transmission, releasing resources, or adjusting configuration.

[0009] In this application embodiment, for scenarios where multiple Quality of Service (QoS) flows corresponding to the same application service are managed by different access network devices, for example, a first access network device manages a first QoS flow and a second access network device manages a second QoS flow, if the first QoS flow is abnormal, the first access network device managing the first QoS flow can report it to the first policy control function network element managing the first QoS flow via the session management network element. If the first QoS flow has an associated second QoS flow (e.g., the first QoS flow and the second QoS flow correspond to the same application service), the first policy control function network element can notify the second policy control function network element managing the second QoS flow to perform abnormal handling on the second QoS flow (e.g., stop transmission, release resources, adjust configuration, etc.), thereby avoiding the situation where the first QoS flow managed by the first access network device cannot be transmitted, but the second QoS flow managed by the second access network device continues to transmit, reducing resource waste.

[0010] In one possible implementation, the first quality of service flow is used to carry a first service flow, and the second quality of service flow is used to carry a second service flow, wherein the first service flow and the second service flow belong to a first application service.

[0011] In this implementation, a method is provided to associate the first service quality flow with the second service quality flow. For example, the first service quality flow carrying the first service quality flow and the second service quality flow carrying the second service quality flow belong to the same application service. In order to ensure that the application service can operate normally, it is necessary to coordinate the management of the first service quality flow and the second service quality flow corresponding to the application service. Therefore, the first service quality flow and the second service quality flow are associated.

[0012] In one possible implementation, the first indication information includes one or more of the following: an identifier of the first quality of service flow; an identifier of the third quality of service flow, wherein the third quality of service flow is a quality of service flow that has not experienced any anomalies; an identifier of the first application service, wherein the first application service is the application service to which the first service flow carried by the first quality of service flow and the second service flow carried by the second quality of service flow belong; and first configuration information, wherein the first configuration information is used to indicate that the configuration of the first quality of service flow is a first configuration.

[0013] This implementation provides multiple ways for the first indication information to indicate an anomaly in the first quality of service (QoS) flow. For example, the identifier of the anomaly in the first QoS flow, or the identifier of the first application service corresponding to the anomaly in the first QoS flow, can be understood as a direct indication method. Alternatively, the identifier of a third QoS flow that is not anomaly can be understood as an indirect indication method. This makes the way the first indication information indicates the anomaly in the first QoS flow more flexible, and consequently, the way the first policy control function network element determines the anomaly in the first QoS flow is also more flexible. Furthermore, if the anomaly in the first QoS flow refers to an adjustment of its configuration, the first indication information can also instruct the configuration of the first QoS flow to be adjusted to the first configuration. This allows the first policy control function network element to notify the second policy control function network element to also adjust the configuration of the second QoS flow associated with the first QoS flow to the first configuration, reducing resource waste.

[0014] In one possible implementation, the method further includes: determining the identifier of the first application service based on the identifier of the first quality of service flow and the first mapping relationship, wherein the first mapping relationship is a mapping relationship between the identifier of the quality of service flow and the identifier of the application service.

[0015] This implementation provides a method for the first policy control function network element to determine the identifier of the first application service. For example, the identifier of the first application service can be determined based on the identifier of the first quality of service flow and the first mapping relationship. Besides this, the first policy control function network element can also determine the identifier of the first application service through other methods, without limitation.

[0016] In one possible implementation, the second indication information includes one or more of the following: an identifier of a first application service, wherein the first application service is the application service to which the first service flow carried by the first quality of service flow and the second service flow carried by the second quality of service flow belong; second configuration information, wherein the second configuration information is used to instruct the second policy control function network element to adjust the configuration of the second quality of service flow to the first configuration; and a first policy and charging control rule, wherein the first policy and charging control rule is obtained by the first policy control function network element updating the policy and charging control rule bound to the first quality of service flow, wherein the first quality of service flow and the second quality of service flow are associated.

[0017] In this implementation, a method is provided to indicate the second quality of service flow that requires the first processing using second indication information. For example, the identifier of the first application service corresponding to the second quality of service flow requiring the first processing can be understood as a direct indication method. Another example is the policy and billing control rules bound to the first quality of service flow associated with the second quality of service flow requiring the first processing; this can be understood as an indirect indication method. Furthermore, if the first quality of service flow experiences an anomaly due to an adjustment to its configuration, and the configuration of the first quality of service flow is adjusted to the first configuration, the first policy control function network element can also notify the second policy control function network element to adjust the configuration of the second quality of service flow associated with the first quality of service flow to the first configuration as well, reducing resource waste.

[0018] In one possible implementation, the method further includes: sending an identifier of a first application service to the binding support function network element, wherein the first application service is the application service to which the first service flow carried by the first quality of service flow and the second service flow carried by the second quality of service flow belong; and receiving an identifier of the second policy control function network element from the binding support function network element.

[0019] This implementation provides one method for the first policy control function network element to obtain the identifier of the second policy control function network element. For example, the first policy control function network element obtains the identifier of the second policy control function network element from the bound supporting function network element. Besides this, the first policy control function network element can also obtain the identifier of the second policy control function network element through other methods, without restriction.

[0020] Secondly, embodiments of this application also provide a communication method, which can be executed by a second policy control function network element or by a component of the second policy control function network element. The method includes: receiving a second message from a first policy control function network element, the second message including second indication information, the second indication information being used to instruct the second policy control function network element to perform a first process on a second quality of service flow, the first process including one or more of stopping transmission, releasing resources, or adjusting configuration; and sending a third message to a session management network element, the third message including third indication information, the third indication information being used to instruct the session management network element to perform the first process on the second quality of service flow.

[0021] In one possible implementation, the second indication information includes one or more of the following: an identifier of a first application service, wherein the first application service is the application service to which the second service flow carried by the second quality of service flow belongs; second configuration information, wherein the second configuration information is used to instruct the second policy control function network element to adjust the configuration of the second quality of service flow to the first configuration; and a first policy and charging control rule, wherein the first policy and charging control rule is obtained by the first policy control function network element updating the policy and charging control rule bound to the first quality of service flow according to the first message, wherein the first quality of service flow is associated with the second quality of service flow.

[0022] In one possible implementation, the method further includes: determining the identifier of the second quality of service flow based on the identifier of the first application service and the first mapping relationship, wherein the first mapping relationship is a mapping relationship between the identifier of the quality of service flow and the identifier of the application service.

[0023] In one possible implementation, the third indication information includes one or more of the following: an identifier of the second quality of service flow; an identifier of a first application service, wherein the first application service is the application service to which the second service flow carried by the second quality of service flow belongs; third configuration information, wherein the third configuration information is used to instruct the session management network element to adjust the configuration of the second quality of service flow to the first configuration; and second policy and charging control rules, wherein the second policy and charging control rules are obtained by the second policy control function network element updating the policy and charging control rules bound to the second quality of service flow.

[0024] The beneficial effects of the second aspect and its implementation can be referred to the beneficial effects of the first aspect and any of its implementations.

[0025] Thirdly, embodiments of this application also provide a communication method, which can be executed by a session management network element or by a component of the session management network element. The method includes: receiving a fourth message from a first access network device, the fourth message including first indication information, the first indication information being used to indicate that a first quality of service flow has an anomaly; sending a first message to a first policy control function network element, the first message including the first indication information; receiving a third message from the first policy control function network element, the third message including third indication information, the third indication information being used to instruct the session management network element to perform the first processing on a second quality of service flow; and sending a fifth message to a second access network device, the fifth message including the fourth indication information, the fourth indication information being used to instruct the second access network device to perform the first processing on the second quality of service flow.

[0026] In one possible implementation, the first quality of service flow is used to carry a first service flow, and the second quality of service flow is used to carry a second service flow, wherein the first service flow and the second service flow belong to a first application service.

[0027] In one possible implementation, the first indication information includes one or more of the following: an identifier of the first quality of service flow; an identifier of the third quality of service flow, wherein the third quality of service flow is a quality of service flow that has not experienced any anomalies; an identifier of the first application service, wherein the first application service is the application service to which the first service flow carried by the first quality of service flow and the second service flow carried by the second quality of service flow belong; and first configuration information, wherein the first configuration information is used to indicate that the configuration of the first quality of service flow is a first configuration.

[0028] In one possible implementation, the method further includes: determining the identifier of the first application service based on the identifier of the first quality of service flow and the first mapping relationship, wherein the first mapping relationship is a mapping relationship between the identifier of the quality of service flow and the identifier of the application service.

[0029] In one possible implementation, the third indication information further includes one or more of the following: an identifier of the second quality of service flow; an identifier of a first application service, wherein the first application service is the application service to which the second service flow carried by the second quality of service flow belongs; third configuration information, wherein the third configuration information is used to instruct the session management network element to adjust the configuration of the second quality of service flow to the first configuration; and second policy and charging control rules, wherein the second policy and charging control rules are obtained by the second policy control function network element updating the policy and charging control rules bound to the second quality of service flow.

[0030] In one possible implementation, the method further includes: determining the identifier of the second quality of service flow based on the identifier of the first application service and the first mapping relationship, wherein the first mapping relationship is a mapping relationship between the identifier of the quality of service flow and the identifier of the application service.

[0031] In one possible implementation, the fourth indication information further includes one or more of the following: an identifier of the second quality of service flow; an identifier of a first application service, wherein the first application service is the application service to which the second service flow carried by the second quality of service flow belongs; and fourth configuration information, wherein the fourth configuration information is used to instruct the second access network device to adjust the configuration of the second quality of service flow to the first configuration.

[0032] The beneficial effects of the third aspect and its implementation can be referred to the beneficial effects of the first aspect and any of its implementations.

[0033] Fourthly, embodiments of this application provide a communication device. The communication device is used to perform the method described in the first aspect and any possible implementation thereof. The communication device is, for example, a first policy control function network element, or a functional module within the first policy control function network element, such as a baseband device or a chip system. In one possible implementation, the communication device includes a baseband device and a radio frequency device.

[0034] In another possible implementation, the communication device includes a processing unit (sometimes also called a processing module) and a transceiver unit (sometimes also called a transceiver module). The transceiver unit is capable of both sending and receiving functions. When the transceiver unit performs the sending function, it can be called a sending unit (sometimes also called a sending module); when it performs the receiving function, it can be called a receiving unit (sometimes also called a receiving module). The sending unit and the receiving unit can be the same functional unit, referred to as the transceiver unit, which performs both sending and receiving functions; or, the sending unit and the receiving unit can be different functional units, with "transceiver unit" being a collective term for these functional units.

[0035] Fifthly, embodiments of this application provide yet another communication device. The communication device is used to perform the method described in the second aspect and any possible implementation thereof. The communication device is, for example, a second policy control function network element, or a functional module within a second policy control function network element, such as a baseband device or a chip system. In one possible implementation, the communication device includes a baseband device and a radio frequency device.

[0036] In another possible implementation, the communication device includes a processing unit (sometimes also called a processing module) and a transceiver unit (sometimes also called a transceiver module). The transceiver unit is capable of both sending and receiving functions. When the transceiver unit performs the sending function, it can be called a sending unit (sometimes also called a sending module); when it performs the receiving function, it can be called a receiving unit (sometimes also called a receiving module). The sending unit and the receiving unit can be the same functional unit, referred to as the transceiver unit, which performs both sending and receiving functions; or, the sending unit and the receiving unit can be different functional units, with "transceiver unit" being a collective term for these functional units.

[0037] Sixthly, embodiments of this application provide yet another communication device. The communication device is used to perform the method described in the third aspect and any possible implementation thereof. The communication device is, for example, a session management network element, or a functional module within a session management network element, such as a baseband device or a chip system. In one possible implementation, the communication device includes a baseband device and a radio frequency device.

[0038] In another possible implementation, the communication device includes a processing unit (sometimes also called a processing module) and a transceiver unit (sometimes also called a transceiver module). The transceiver unit is capable of both sending and receiving functions. When the transceiver unit performs the sending function, it can be called a sending unit (sometimes also called a sending module); when it performs the receiving function, it can be called a receiving unit (sometimes also called a receiving module). The sending unit and the receiving unit can be the same functional unit, referred to as the transceiver unit, which performs both sending and receiving functions; or, the sending unit and the receiving unit can be different functional units, with "transceiver unit" being a collective term for these functional units.

[0039] In a seventh aspect, embodiments of this application provide a communication device. The communication device may include one or more processors. Optionally, the communication device may further include a memory. The memory is used to store one or more computer programs or instructions. The one or more processors are used to execute the one or more computer programs or instructions stored in the memory, causing the communication device to perform the methods described in the first aspect and any possible implementation thereof.

[0040] Eighthly, embodiments of this application provide yet another communication device. The communication device may include one or more processors. Optionally, the communication device may further include a memory. The memory is used to store one or more computer programs or instructions. The one or more processors are used to execute the one or more computer programs or instructions stored in the memory, causing the communication device to perform the methods described in the second aspect and any possible implementation thereof.

[0041] Ninthly, embodiments of this application provide another communication device. The communication device may include one or more processors. Optionally, the communication device may further include a memory. The memory is used to store one or more computer programs or instructions. The one or more processors are used to execute the one or more computer programs or instructions stored in the memory, causing the communication device to perform the methods described in the third aspect and any possible implementation thereof.

[0042] In a tenth aspect, embodiments of this application also provide a communication system. The communication system includes at least one of the communication devices described in the fourth aspect, the fifth aspect, or the sixth aspect.

[0043] Eleventhly, embodiments of this application provide a computer-readable storage medium for storing a computer program or instructions that, when executed, enable the implementation of the methods described in the first aspect and any possible implementation thereof, or enable the implementation of the methods described in the second aspect and any possible implementation thereof, or enable the implementation of the methods described in the third aspect and any possible implementation thereof.

[0044] In a twelfth aspect, embodiments of this application also provide a computer program product containing instructions that, when run on a computer, cause the method described in the first aspect and any possible implementation thereof to be implemented, or cause the method described in the second aspect and any possible implementation thereof to be implemented, or cause the method described in the third aspect and any possible implementation thereof to be implemented.

[0045] In a thirteenth aspect, embodiments of this application also provide a chip coupled to a memory for reading and executing program instructions in the memory, so that the device in which the chip is located implements the method described in the first aspect and any possible implementation of the first aspect, or implements the method described in the second aspect and any possible implementation of the second aspect, or implements the method described in the third aspect and any possible implementation of the third aspect. Attached Figure Description

[0046] Figure 1 is a schematic diagram of a network architecture provided in an embodiment of this application;

[0047] Figure 2 is a schematic diagram of a QoS flow carrying service flow provided in an embodiment of this application;

[0048] Figure 3a is a schematic diagram of multiple QoS flows corresponding to collaborative management of multimodal services provided in an embodiment of this application;

[0049] Figure 3b is a schematic diagram of another collaborative management of multiple QoS flows corresponding to multimodal services provided in an embodiment of this application;

[0050] Figure 4a is a schematic diagram of a first quality of service flow, a second quality of service flow, and a third quality of service flow provided in an embodiment of this application;

[0051] Figure 4b is a schematic diagram of a communication method provided in an embodiment of this application;

[0052] Figure 4c is a schematic diagram of another communication method provided in an embodiment of this application;

[0053] Figure 5 is a schematic diagram of a communication device provided in an embodiment of this application;

[0054] Figure 6 is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0055] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the embodiments of this application will be further described in detail below with reference to the accompanying drawings.

[0056] The terms "system" and "network" in this application embodiment can be used interchangeably. "Multiple" refers to two or more; therefore, in this application embodiment, "multiple" can also be understood as "at least two". "At least one" can be understood as one or more, such as one, two, or more. For example, including at least one means including one, two, or more, and is not limited to which ones are included. For example, including at least one of A, B, and C means including A, B, C, A and B, A and C, B and C, or A and B and C. Similarly, the understanding of descriptions such as "at least one" is similar. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, "at least one of A, B, and C" includes A, B, C, AB, AC, BC, or ABC. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. In addition, the character " / ", unless otherwise specified, generally indicates that the objects before and after it are in an "or" relationship.

[0057] Unless otherwise specified, the ordinal numbers such as "first" and "second" mentioned in the embodiments of this application are used to distinguish multiple objects, and are not used to limit the order, sequence, priority or importance of multiple objects, and the description of "first" and "second" does not limit the objects to necessarily being different.

[0058] Furthermore, in the embodiments of this application, "when," "if," and "if" all refer to the device taking corresponding actions under certain objective circumstances, and are not time-limited, nor do they require the device to perform a judgment action, nor do they imply any other limitations. Unless otherwise specified, "if" and "if" can be substituted, and "when" and "in the case of" can be substituted. "When" and "if" / "if" can be substituted.

[0059] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0060] In the embodiments of this application, "for indicating" can include both direct and indirect indication. For example, when descriptive information I is used to indicate information J, it can mean that information I directly indicates information J or indirectly indicates information J, but does not necessarily mean that information I carries information J.

[0061] Let information J, indicated by information I, be called the information to be indicated. In practice, 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 itself or its index. It can also be indirectly indicated by indicating other information, where there is a relationship 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) order of various pieces of information, thereby reducing indication overhead to some extent. Simultaneously, common parts of various pieces of information can be identified and indicated uniformly to reduce the indication overhead caused by individually indicating the same information.

[0062] Furthermore, the specific instruction method can also be any existing instruction method, such as, but not limited to, the above-mentioned instruction methods and their various combinations. As described above, for example, when multiple pieces of information of the same type need to be indicated, the instruction methods for different pieces of information may differ. In specific implementation, the required instruction method can be selected according to specific needs. This application embodiment does not limit the selected instruction method. Therefore, the instruction methods involved in this application embodiment should be understood to cover various methods that enable the party to be instructed to obtain the information to be indicated.

[0063] In the embodiments of this application, "send" and "receive" indicate the direction of signal transmission. For example, "send information to XX" can be understood as the destination of the information being XX, which may include direct transmission via the air interface or indirect transmission via the air interface by other units or modules. "Receive information from YY" can be understood as the source of the information being YY, which may include direct reception from YY via the air interface or indirect reception from YY via the air interface by other units or modules. "Send" can also be understood as the "output" of the chip interface, and "receive" can also be understood as the "input" of the chip interface.

[0064] Information may undergo necessary processing, such as encoding and modulation, between the source and destination ends, but the destination end can understand the valid information from the source end. Similar statements in the embodiments of this application can be understood in a similar way, and will not be repeated here.

[0065] This application will present various aspects, embodiments, or features relating to systems that may include multiple devices, components, modules, etc. It should be understood and appreciated that individual systems may include additional devices, components, modules, etc., and / or may not include all the devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Furthermore, combinations of these approaches are also possible.

[0066] The preceding paragraphs introduced some of the terminology used in the embodiments of this application. Next, the communication system to which the embodiments of this application are applicable will be introduced.

[0067] It should be noted that the network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0068] The technical solutions of this application can be applied to various communication systems. In a communication system, the portion operated by an operator can be called a public land mobile network (PLMN) (also known as an operator network, mobile communication network, etc.). A PLMN is a network created and operated by the government or its approved operators for the purpose of providing land mobile communication services to the public. It is mainly a public network provided by a mobile network operator (MNO) to users for mobile broadband access services. The PLMN described in this application can specifically be a network that conforms to the requirements of the 3rd generation partnership project (3GPP) standard, abbreviated as 3GPP network. 3GPP networks generally include, but are not limited to, 4th-generation (4G) networks (abbreviated as 4G networks), 5th-generation (5G) networks (abbreviated as 5G networks), and other future communication systems. For ease of description, this application will use a 5G network as an example for illustration.

[0069] Figure 1 is a schematic diagram of a network architecture provided in an embodiment of this application. It takes the 5G network architecture based on a service-oriented architecture in a non-roaming scenario as an example, as defined in the 3GPP standardization process. This network architecture can include three parts: a terminal equipment part, a data network (DN) part, and a PLMN part.

[0070] The terminal equipment component may include terminal devices that can establish connections with the operator's network through interfaces provided by the operator's network (such as N1), and use data and / or voice services provided by the operator's network. The terminal devices can also access data networks through the operator's network, using operator services deployed on the data network, and / or services provided by third parties. These third parties may be service providers outside of the operator's network and terminal devices, and may provide other data and / or voice services to the terminal devices. The specific form of these third parties can be determined based on the actual application scenario and is not limited here.

[0071] A terminal device, often simply referred to as a terminal, is a device with wireless transceiver capabilities. It can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; on water (such as on ships); and in the air (such as on airplanes, balloons, and satellites). Terminal devices can include mobile phones, tablets, computers with wireless transceiver capabilities, extended reality (XR) terminals (such as virtual reality (VR) terminals, augmented reality (AR) terminals, wireless terminals in industrial control, wireless terminals in self-driving vehicles, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, user equipment (UE), and terminal devices adapted to the Internet of Things (IoT) (such as terminal devices in smart factories, terminal devices in smart manufacturing, etc.).

[0072] A data network, also known as a packet data network (PDN), is typically a network located outside of a carrier's network, such as a third-party network. A carrier's network can connect to multiple data networks, and various services can be deployed on these networks, providing data and / or voice services to terminal devices. For example, a data network could be the private network of a smart factory. Sensors installed in the workshop can be terminal devices, and a control server for these sensors is deployed within the data network. The control server provides services to the sensors. Sensors can communicate with the control server, receive instructions from it, and transmit the collected sensor data back to the control server accordingly. Another example is a data network that could be a company's internal office network. Employees' mobile phones or computers can be terminal devices, allowing them to access information and data resources on the company's internal office network.

[0073] A PLMN may include, but is not limited to: network slice selection function (NSSF) network elements, authentication server function (AUSF) network elements, network exposure function (NEF) network elements, network repository function (NRF) network elements, access and mobility management function (AMF) network elements, policy control function (PCF) network elements, unified data management (UDM) network elements, session management function (SMF) network elements, binding support function (BSF) network elements, unified data repository (UDR) network elements, user plane function (UPF) network elements, and radio access network (RAN), etc. The portion of the PLMN excluding the (radio) access network can be referred to as the core network (CN).

[0074] For example, the network functions that may be involved in various embodiments of this application will be briefly described below. In addition, Figure 1 also involves other network elements, which will not be described in detail here.

[0075] (R)AN can be viewed as a sub-network of the operator's network, serving as the implementation system between service nodes and terminal devices within the operator's network. For a terminal device to access the operator's network, it first passes through the (R)AN, and then connects to the operator's network's service nodes via the (R)AN. The access network equipment (RAN equipment) in this application embodiment is a device that provides wireless communication functions for terminal devices; it can also be called network equipment, etc. RAN equipment includes, but is not limited to: next-generation node base stations (gNBs) in 5G systems, evolved node Bs (eNBs) in long-term evolution (LTE), radio network controllers (RNCs), node Bs (NBs), base station controllers (BSCs), base transceiver stations (BTSs), home base stations (e.g., home evolved node Bs, or home node Bs (HNBs)), base band units (BBUs), transmitting and receiving points (TRPs), transmitting points (TPs), small cell equipment (picos), mobile switching centers, or network equipment in future networks, etc. In systems employing different wireless access technologies, the names of devices with access network equipment functions may differ. For ease of description, in all embodiments of this application, the aforementioned devices providing wireless communication functions for terminal devices are collectively referred to as access network equipment or simply RAN or AN. It should be understood that this document does not limit the specific type of access network equipment.

[0076] An application function is a control plane function deployed on the application service side. It can be deployed by the operator or by an external third party. Application functions support services such as traffic routing control, policy control interaction, and access network function opening through interaction with other network functions in the core network. For example, in a 5G communication system, an application function may be AF (Automatic Application Function), as shown in Figure 1. In future communication systems, the application function may still be AF, or it may have other names; this application embodiment does not limit this.

[0077] The Network Open Function (NEF) is responsible for providing network-related status information to application services. For example, in a 5G communication system, the NEF can be used, as shown in Figure 1. In future communication systems, the NEF may still be used, or it may have other names; this application does not limit this.

[0078] The network storage function supports service discovery. For example, in a 5G communication system, the network storage function can be NRF, as shown in Figure 1; in future communication systems, the network storage function can still be NRF, or may have other names, which are not limited in the embodiments of this application.

[0079] The binding support function enables service registration, deregistration, and updates, ensuring that other network functions can correctly discover and access related services. It is responsible for creating, deleting, and querying session binding information. For example, in a 5G communication system, the binding support function may be a BSF (Bounding Support Function), as shown in Figure 1; in future communication systems, the binding support function may still be a BSF, or it may have other names, which are not limited in this application embodiment.

[0080] Unified data management is responsible for user subscription management, access authorization, and authentication information generation. For example, in a 5G communication system, unified data management can be UDM, as shown in Figure 1; in future communication systems, unified data management can still be UDM, or may have other names, which are not limited in the embodiments of this application.

[0081] The unified data storage is responsible for storing subscription data, policy data, and application data, providing them for querying and retrieval by other network functions. For example, in a 5G communication system, the unified data storage can be a UDR, as shown in Figure 1; in future communication systems, the unified data storage can still be a UDR, or it may have other names, which are not limited in the embodiments of this application.

[0082] Policy control functions are control plane functions provided by operators. They support a unified policy framework to govern network behavior, provide policy rules and subscription information related to policy decisions to other control functions. For example, in a 5G communication system, the policy control function may be PCF, as shown in Figure 1. In future communication systems, the policy control function may still be PCF, or it may have other names; this application does not limit this.

[0083] The session management function, provided by the PLMN, is a control plane network function responsible for managing the protocol data units (PDUs) of terminal devices. A PDU session is a channel used to transmit PDUs; terminal devices need to exchange data with the DN through PDU sessions. The session management function can be responsible for creating, maintaining, and deleting PDU sessions. The session management function includes session management (such as session creation, modification, and release, including tunnel maintenance between user plane functions and the AN), user plane function selection and control, service and session continuity (SSC) mode selection, roaming, and other session-related functions. For example, in a 5G communication system, the session management function can be an SMF, as shown in Figure 1; in future communication systems, the session management function may still be an SMF, or may have other names, which are not limited in this embodiment.

[0084] Access and Mobility Management (AMM) is a control plane network function provided by the PLMN, responsible for access control and mobility management of terminal devices accessing the PLMN. This includes functions such as mobility state management, allocation of temporary user identities, authentication, and authorization. For example, in a 5G communication system, AMM may be used, as shown in Figure 1. In future communication systems, AMM may still be used, or it may have other names; this application does not limit this.

[0085] User plane functionality is a gateway provided by the PLMN that communicates with the data network (DN). User plane functionality includes packet routing and transmission, packet inspection, traffic usage reporting, quality of service (QoS) processing, uplink packet inspection, downlink packet storage, and other user plane-related functions. For example, in a 5G communication system, user plane functionality can be UPF, as shown in Figure 1; in future communication systems, user plane functionality may still be UPF, or may have other names, which are not limited in this application embodiment.

[0086] In this PLMN, each network function can be a network element implemented on dedicated hardware, a software instance running on dedicated hardware, or a virtualized function instance on a suitable platform, such as a cloud platform. Furthermore, each network function in the PLMN can also be referred to as a network element, functional entity, or device. For example, policy control functions can be called policy control function network elements, policy control function entities, or policy control function devices, and session management functions can be called session management function network elements, session management function entities, or session management function devices, etc. These will not be listed exhaustively here.

[0087] The network functions in the PLMN shown in Figure 1 may also include other network functions. This application embodiment does not limit the other network functions included in the PLMN. Furthermore, the names of the network functions shown in Figure 1 are merely illustrative examples and are not intended to limit the network functions included in the network architecture to which the method of this application embodiment applies. The device names implementing network functions may differ in systems with different access technologies, and this application embodiment does not limit this.

[0088] In Figure 1, Nnssf, Nausf, Nnef, Nnrf, Namf, Npcf, Nsmf, Nudm, Naf, Nbsf, Nudr, N1, N2, N3, N4, and N6 are interface sequence numbers. The meanings of these interface sequence numbers can be found in the 3rd Generation Partnership Project (3GPP) standard protocol, and are not limited here. It should be noted that the interface names between the various network functions in Figure 1 are merely examples; in specific implementations, the interface names in this system architecture may be other names, which this application does not limit.

[0089] It should be noted that the network architecture shown in Figure 1 does not constitute a limitation on the communication systems to which the embodiments of this application can be applied. The network architecture shown in Figure 1 is a 5G system architecture. Optionally, the technical solutions provided in the embodiments of this application can be applied not only to 5G systems, but also to 4G systems, such as LTE systems, or to next-generation mobile communication systems or other similar communication systems, without any specific limitations.

[0090] The technical features related to the embodiments of this application will be described below.

[0091] 1) Policy and charging control (PCC) rules,

[0092] PCC rules can be used to control the service flows of application services. These PCC rules are generated by the PCF network element and sent to the SMF network element. Upon receiving the PCC rule from the PCF network element, the SMF network element binds the PCC rule to the corresponding QoS flow through a QoS flow binding mechanism. The service flow corresponding to this PCC rule can then be carried through the QoS flow bound to it. The principle of the QoS flow binding mechanism is as follows: if the binding parameters of the PCC rule (such as the 5G QoS identifier (5QI), priority, etc.) are consistent with the parameters of the QoS flow, the PCC rule can be bound to that QoS flow. In the current QoS flow binding mechanism, multiple PCC rules with the same binding parameters can be bound to the same QoS flow.

[0093] It should be noted that a PCF network element can generate one PCC rule for one service flow, meaning one service flow corresponds to one PCC rule; or it can generate one PCC rule for multiple service flows, meaning multiple service flows correspond to one PCC rule. In other words, multiple service flows can correspond to one or more PCC rules. For ease of understanding of the embodiments of this application, unless otherwise specified, the following text will use one service flow corresponding to one PCC rule as an example.

[0094] In this embodiment of the application, binding PCC rules to QoS flows can be understood as associating PCC rules with QoS flows, or it can be understood as mapping PCC rules to QoS flows.

[0095] In this application embodiment, multiple PCC rules with the same binding parameters can be understood as multiple PCC rules having one or more identical binding parameters. Binding parameters may include, for example, at least one of the following: 5G QoS identifier (5QI), allocation and retention priority (ARP), QoS notification control (QNC), priority level, averaging window, and maximum data burst volume, etc.

[0096] In this application's embodiments, multiple PCC rules with the same binding parameters can be understood as multiple service flows corresponding to multiple PCC rules having the same QoS requirements. Accordingly, multiple PCC rules with the same binding parameters can be bound to the same QoS flow, which can be understood as multiple service flows with the same QoS requirements being mapped to the same QoS flow, or as multiple service flows with the same QoS requirements being carried by a single QoS flow.

[0097] 2) Application business flow

[0098] Application services can be multimodal services (or multimodal services) or non-multimodal services (or non-multimodal services), and this application embodiment does not limit this. Multimodal services refer to services that require the transmission of multiple types of data, such as video data, audio data, sensor data, command data, or feedback data. Non-multimodal services refer to services other than multimodal services. For example, application services can be XR services used on a terminal, or game services used on a terminal, and this application embodiment does not limit the specific implementation method of the application service.

[0099] The service flow can be a multimodal service flow (or multimodal service flow, or multimodal data flow) or a non-multimodal service flow (or non-multimodal data flow), and this application embodiment does not limit the specific implementation of the service flow. Multimodal service flow refers to the various types of data streams transmitted by a multimodal service, such as video data streams, audio data streams, sensor data streams, command data streams, and feedback data streams transmitted by an XR service. Non-multimodal service flow refers to other service flows besides multimodal service flows. For example, a service flow can be a video data stream, audio data stream, and / or sensor data stream sent from the server to the terminal, or a video data stream, audio data stream, and / or sensor data stream sent from the terminal to the server. This application embodiment does not limit the specific implementation of the service flow. Furthermore, the different service flows involved in the embodiments of this application can be IP flows with different Internet Protocol (IP) 5-tuples; or, different service flows can also be IP flows with the same IP 5-tuple, for example, one IP 5-tuple identifies a video data flow, where I-frames constitute one service flow and P-frames constitute another service flow. Service flows can be called multimodal service flows, multimodal service flows, or multimodal data flows; the specific names of service flows are not limited in the embodiments of this application.

[0100] An application service can correspond to multiple service flows. For example, a game application can generate not only video data but also audio data. These service flows may have different QoS requirements, which means that multiple service flows of the same application service can be mapped to different QoS flows. In other words, an application service that includes multiple service flows can correspond to multiple QoS flows.

[0101] For example, Figure 2 is a schematic diagram of a QoS flow carrying a service flow provided in an embodiment of this application. Figure 2 takes application service 1 as an example. Application service 1 includes four service flows, denoted as service flow 1, service flow 2, service flow 3, and service flow 4. As shown in Figure 2, service flow 1 and service flow 4 have the same QoS requirements, and service flow 1 and service flow 4 are mapped to QoS flow 1, that is, QoS flow 1 carries service flow 1 and service flow 4 of application service 1; service flow 2 and service flow 3 have the same QoS requirements, and service flow 2 and service flow 3 are mapped to QoS flow 2, that is, QoS flow 2 carries service flow 2 and service flow 3 of application service 1.

[0102] To ensure the normal operation of an application service to which multiple service flows belong, it is necessary to coordinate the management of multiple QoS flows corresponding to that application service. For example, if some QoS flows among the multiple QoS flows corresponding to the application service cannot be transmitted due to transmission resource reasons, then there is no need for the remaining QoS flows to continue transmitting.

[0103] For example, taking an application service as a multimodal service and a service flow as a multimodal service flow as an example, Figure 3a is a schematic diagram of a collaborative management of multiple QoS flows corresponding to a multimodal service provided in an embodiment of this application. As shown in Figure 3a, taking multimodal service 1 as including multimodal service flow 1 and multimodal service flow 2, multimodal service flow 1 is sent to terminal device #1, multimodal service flow 2 is sent to terminal device #2, multimodal service flow 1 is mapped to QoS flow 1, and multimodal service flow 2 is mapped to QoS flow 2 as an example, the specific steps for collaborative management of QoS flow 1 and QoS flow 2 corresponding to the multimodal service are as follows:

[0104] Step 1: PCF network element #1 creates PCC rule 1, and PCF network element #2 creates PCC rule 2. PCC rule 1 can be used to perform policy control on multimodal service flow 1 carried by QoS flow 1. PCC rule 2 can be used to perform policy control on multimodal service flow 2 carried by QoS flow 2.

[0105] Step 2: PCF network element #1 sends request message 1 to BSF network element, and PCF network element #2 sends request message 2 to BSF network element. Correspondingly, the BSF network element receives request message 1 from PCF network element #1 and request message 2 from PCF network element #2. Request message 1 and request message 2 can be management update request (Nbsf_Management_Update_Request) messages. Request message 1 and request message 2 can be used to request updates to the information of PCF network elements associated with the policy of multimodal service 1. Request message 1 and request message 2 can include one or more of the following: the identifier of the provider of multimodal service 1; the identifier of multimodal service 1.

[0106] Step 3: The BSF network element sends response message 1 to PCF network element #1 and response message 2 to PCF network element #2. Correspondingly, PCF network element #1 receives response message 1 from the BSF network element, and PCF network element #2 receives response message 2 from the BSF network element. Response message 1 and response message 2 can be management update response (Npcf_Management_Update_Response) messages. Response message 1 and response message 2 can be used to indicate successful request.

[0107] Step 4: The BSF network element establishes a configuration file for multimodal service 1 based on the information of the PCF network elements associated with the policy of multimodal service 1 uploaded from different PCF network elements. The configuration file can be as shown in Table a.

[0108] Table a

[0109] Step 5: PCF network element #1 sends request message 3 to BSF network element, and correspondingly, BSF network element receives request message 3 from PCF network element #1. Request message 3 can be a Management Discovery Request (Nbsf_Management_Discovery_Request) message. Request message 3 is used to request information from other PCF network elements used to manage the QoS flow corresponding to multimodal service 1. Request message 3 may include one or more of the following: the identifier of the provider of multimodal service 1; the identifier of multimodal service 1.

[0110] Step 6: The BSF network element sends response message 3 to PCF network element #1. Correspondingly, PCF network element #1 receives response message 3 from the BSF network element. Response message 3 can be a management discovery response (Npcf_Management_Discovery_Response) message. Response message 3 can include one or more of the following: information about terminal device #2 (e.g., the address of terminal device #2, the identifier of terminal device #2), which can be the IP address of the UE or the UE identifier; and information about PCF network element #2 (e.g., the address of PCF network element #2, the identifier of PCF network element #2).

[0111] Step 7: PCF network element #1 sends request message 4 to PCF network element #2, and correspondingly, PCF network element #2 receives request message 4 from PCF network element #1. Request message 4 can be a Policy Authorization Subscribe Request (Npcf_PolicyAuthorization_Subscribe_Request) message. Request message 4 can be used to request the PCC rule bound to QoS flow 2 corresponding to multimodal service 1. Request message 4 may include one or more of the following: the identifier of the provider of multimodal service 1; the identifier of multimodal service 1; and information about terminal device #2.

[0112] Step 8: PCF network element #2 sends response message 4 to PCF network element #1. Correspondingly, PCF network element #1 receives response message 4 from PCF network element #2. Response message 4 can be a Policy Authorization Subscribe Response (Npcf_PolicyAuthorization_Subscribe_Response) message. Response message 4 can be used to indicate that the request was successful.

[0113] Step 9: PCF element #2 sends instruction message 1 to PCF element #1, and correspondingly, PCF element #1 receives instruction message 1 from PCF element #2. Instruction message 1 can be a policy authorization notification (pcf_PolicyAuthorization_Notify) message. Instruction message 1 can include PCC rule 2.

[0114] It is understandable that PCF network element #2 can also perform the operations performed by PCF network element #1 in steps 5-9.

[0115] Step 10: PCF network element #1 and PCF network element #2 perform collaborative management of PCC rule 1 and PCC rule 2.

[0116] Step 11: PCF network element #1 sends request message 5 to BSF network element, and correspondingly, BSF network element receives request message 5 from PCF network element #1. Request message 5 can be a management subscription request (Nbsf_Management_Subscribe_request) message. Request message 5 can be used to request the BSF network element to establish a configuration file for multimodal service 1. Request message 5 can include one or more of the following: the identifier of the provider of multimodal service 1; the identifier of multimodal service 1.

[0117] Step 12: The BSF network element sends response message 5 to PCF network element #1. Correspondingly, PCF network element #1 receives response message 5 from the BSF network element. Response message 5 can be a management subscription response (Npcf_Management_Subscribe_Response) message. Response message 5 can be used to indicate that the request was successful.

[0118] Step 13: The BSF network element sends indication message 2 to PCF network element #1, and correspondingly, PCF network element #1 receives indication message 2 from the BSF network element. Indication message 2 can be a management notification (Npcf_Management_Notify) message. Indication message 2 may include updates to the configuration file established by the BSF network element for multimodal service 1. For example, if terminal device #2 no longer transmits multimodal service flow 2, the BSF deletes the information related to terminal device #2 from the configuration file. Or, for example, if terminal device #3 starts transmitting multimodal service flow 2, the BSF adds the information related to terminal device #3 to the configuration file.

[0119] For example, taking the application service as a multimodal service and the service flow as a multimodal service flow as an example, Figure 3b is a schematic diagram of another process for collaboratively managing multiple QoS flows corresponding to a multimodal service provided in an embodiment of this application. As shown in Figure 3b, taking multimodal service 1 as including multimodal service flow 1 and multimodal service flow 2, multimodal service flow 1 is sent to terminal device #1, multimodal service flow 2 is sent to terminal device #2, multimodal service flow 1 is mapped to QoS flow 1, and multimodal service flow 2 is mapped to QoS flow 2 as an example, the specific steps for collaboratively managing QoS flow 1 and QoS flow 2 corresponding to the multimodal service are as follows:

[0120] Step a, PCF network element #1 updates PCC rule 1. PCC rule 1 can be used to control the multimodal service flow 1 carried by QoS flow 1.

[0121] Step b: PCF network element #1 sends request message a to UDR network element, and correspondingly, UDR network element receives request message a from PCF network element #1. Request message a can be a data management update request (Nudr_DM_Update_Request) message, which can be used to request an update of the policy information for multimodal service 1 stored in the UDR network element.

[0122] In step c, the UDR network element sends response message a to PCF network element #1, and correspondingly, PCF network element #1 receives response message a from the UDR network element. Response message a can be a data management update response (Nudr_DM_Update_Response) message, which can be used to indicate a successful request.

[0123] In step d, the UDR network element sends an indication message a to the PCF network element #2, and correspondingly, the PCF network element #2 receives the indication message a from the UDR network element. The indication message a can be a data management notification (Nudr_DM_Notify) message, which can be used to indicate that the policy information for multimodal service 1 stored in the UDR network element has been updated.

[0124] Step e: PCF network element #1 updates PCC rule 2. PCC rule 2 can be used to control the multimodal service flow 2 carried by QoS flow 2.

[0125] However, multiple QoS flows corresponding to an application service may be managed by different access network devices. One access network device only manages QoS flows based on the policies issued by the core network device, and does not adjust its policies based on the QoS flows managed by another access network device. Therefore, when the QoS flow corresponding to an application service managed by one access network device cannot be transmitted, the QoS flow corresponding to the same application service managed by another access network device will still continue to be transmitted, resulting in wasted resources.

[0126] Taking Figure 2 as an example, service flows 1 and 4 are sent to terminal device #1, while service flows 2 and 3 are sent to terminal device #2. Terminal devices #1 and #2 are connected to different access network devices, namely access network device #1 and access network device #2, respectively. When access network device #1 cannot transmit QoS flow 1 carrying service flows 1 and 4 due to transmission resource limitations, access network device #2 will still continue to transmit QoS flow 2 carrying service flows 2 and 3, as access network device #2 will only manage QoS flow 2 carrying service flows 2 and 3 according to the policy issued to it by the core network device. This results in wasted resources.

[0127] Therefore, embodiments of this application provide a communication method and apparatus to solve the problem of resource waste.

[0128] The following describes a communication method and apparatus provided by an embodiment of this application with reference to the accompanying drawings. This method can be applied to the communication system shown in Figure 1. For ease of understanding, the following description uses an embodiment of this application applied to the communication system shown in Figure 1 as an example. The access network equipment, application function network element, network open function network element, policy control function network element, session management function network element, user plane function network element, access and mobility management function network element, binding support function network element, unified data storage network element, and unified data management network element involved in the embodiments of this application can be the RAN, AF, NEF, PCF, SMF, UPF, AMF, BSF, UDR, and UDM network elements in Figure 1, respectively. Alternatively, they can be network elements in future communication networks that possess the functions of the aforementioned RAN, AF, NEF, PCF, SMF, UPF, AMF, BSF, UDR, and UDM network elements. The embodiments of this application do not limit these specific network elements. For ease of explanation, this application embodiment uses the following network elements as examples: access network equipment, application function network element, network opening function network element, policy control function network element, session management function network element, user plane function network element, access and mobility management function network element, binding support function network element, unified data storage network element, and unified data management network element, respectively representing the RAN, AF, NEF, PCF, SMF, UPF, AMF, BSF, UDR, and UDM network elements mentioned above. Furthermore, the terminal equipment involved in this application embodiment can be the UE shown in Figure 1.

[0129] To facilitate understanding of the embodiments of this application, the first, second, and third quality of service flows involved in the embodiments of this application will be described below. Each of the first, second, and third quality of service flows may include one or more quality of service flows. For ease of understanding of the embodiments of this application, unless otherwise specified, the following description will assume that each of the first, second, and third quality of service flows includes a single quality of service flow.

[0130] For example, Figure 4a is a schematic diagram of the first quality of service flow, the second quality of service flow, and the third quality of service flow.

[0131] As shown in Figure 4a, the first application service includes a first service flow and a second service flow, and the second application service includes a third service flow. Each of the first, second, and third service flows can include one or more service flows with the same quality of service requirements and belonging to the same service. For ease of understanding of the embodiments of this application, unless otherwise specified, the following description will assume that each of the first, second, and third service flows includes only one service flow.

[0132] This can be understood as follows: the first and second business flows belong to the first application service, and the third business flow belongs to the second application service; or it can be understood as the first and second business flows being associated with the first application service, and the third business flow being associated with the second application service; or it can be understood as the first business flow being one or more business flows of the first application service, the second business flow being one or more business flows of the first application service, and the third business flow being one or more business flows of the second application service. For example, the first application service includes multiple business flows, such as business flow a, business flow b, business flow c, business flow d, and business flow e. Business flows a, b, and c have the same service quality requirements, and business flows d and e have the same service quality requirements. Therefore, business flows a, b, and c are the first business flows, and business flows d and e are the second business flows. That is, the first and second business flows correspond to different service quality requirements; the first business flow is carried within the first service quality flow, and the second business flow is carried within the second service quality flow.

[0133] The service quality requirements of the first, second, and third service flows are different; therefore, they are mapped to different service quality flows. For example, the first service flow is mapped to the first service quality flow, meaning the first service quality flow carries the first service flow of the first application. The second service flow is mapped to the second service quality flow, meaning the second service quality flow carries the second service flow of the first application. The third service flow is mapped to the third service quality flow, meaning the third service quality flow carries the third service flow of the second application.

[0134] This can be understood as follows: the first quality of service flow is used to carry the first business flow, the second quality of service flow can carry the second business flow, and the third quality of service flow is used to carry the third business flow.

[0135] Since the first service flow carried by the first service quality flow and the second service flow carried by the second service quality flow both belong to the first application service, while the third service flow carried by the third service quality flow belongs to the second application service, the first service quality flow and the second service quality flow are associated. That is, there is an association between multiple service flows of the same application service, and there is also an association between multiple service quality flows carrying multiple service flows of the same application service.

[0136] Taking the example where the first service flow of the first application service and the third service flow of the second application service are sent to UE#1, and the second service flow of the first application service is sent to UE#2.

[0137] Since UE#1 accesses RAN#1 and UE#2 accesses RAN#2, the first quality of service flow carrying the first service flow and the third quality of service flow carrying the third service flow are managed by RAN#1 (e.g., created and / or updated), while the second quality of service flow carrying the second service flow is managed by RAN#2 (e.g., created and / or updated).

[0138] Furthermore, since RAN#1 interacts with SMF network element #1 and PCF network element #1, and RAN#2 interacts with SMF network element #2 and PCF network element #2, the policy and charging control rule bound to the first quality of service flow (e.g., policy and charging control rule A) is issued from PCF network element #1 to SMF network element #1; the policy and charging control rule bound to the second quality of service flow (e.g., policy and charging control rule B) is issued from PCF network element #2 to SMF network element #2; and the policy and charging control rule bound to the third quality of service flow (e.g., policy and charging control rule C) is issued from PCF network element #1 to SMF network element #1.

[0139] Specifically, policy and charging control rule A can be used to control the first service flow carried by the first quality of service flow, for example, by indicating the quality of service parameters of the first service flow. Policy and charging control rule B can be used to control the second service flow carried by the second quality of service flow, for example, by indicating the quality of service parameters of the second service flow. Policy and charging control rule C can be used to control the third service flow carried by the third quality of service flow, for example, by indicating the quality of service parameters of the third service flow. Policy and charging control rule A may include one or more policy and charging control rules, policy and charging control rule B may include one or more policy and charging control rules, and policy and charging control rule C may include one or more policy and charging control rules. For ease of understanding of the embodiments of this application, unless otherwise stated, the following description will use the example of policy and charging control rule A including one policy and charging control rule, policy and charging control rule B including one policy and charging control rule, and policy and charging control rule C including one policy and charging control rule.

[0140] It is understood that for the specific descriptions of the service quality flow, service flow, application services, and policy and billing control rules involved in the embodiments of this application, please refer to the specific descriptions of the relevant technical features above, and will not be repeated here.

[0141] Figure 4b shows a schematic diagram of a communication method provided in an embodiment of this application. As shown in Figure 4b, the method may include the following:

[0142] S401: SMF network element #1 sends a first message to PCF network element #1. Correspondingly, PCF network element #1 receives the first message from SMF network element #1. The first message may include first indication information. The first indication information can be used to indicate that a first quality of service flow has encountered an anomaly.

[0143] In this embodiment, an anomaly in the first quality of service flow can refer to an anomaly occurring during the establishment of the first quality of service flow, such as failure to establish the first quality of service flow or adjustment of the configuration of the first quality of service flow during session establishment, or failure to establish the first quality of service flow or adjustment of the configuration of the first quality of service flow during RAN handover; or it can refer to an anomaly occurring during the transmission of the first quality of service flow, such as stopping the transmission of the first quality of service flow, releasing the resources of the first quality of service flow, or adjusting the configuration of the first quality of service flow, etc. This embodiment does not limit this.

[0144] In specific implementation, the first message may be a session management policy control update (Npcf_SMPolicyControl_Update) message, or it may be other messages. This application embodiment does not limit the message name.

[0145] The first instruction information may include one or more of the following, which are described below.

[0146] 1) The identifier of the first QoS flow. For example, the list of rejected QoS flows includes the QoS flow identifier (QFI) #1.

[0147] 2) Identification of the third QoS flow, where the third QoS flow is the QoS flow that has not experienced any anomalies. For example, the list of accepted QoS flows includes QFI#3.

[0148] 3) The identifier of the first application service. For example, the identifier of the first application service is the multi-modality service identifier (MMSID)#1.

[0149] 4) First configuration information, wherein the first configuration information can be used to indicate that the configuration of the first quality of service flow is the first configuration.

[0150] It is understood that the first indication information can indicate whether the quality of service (QoS) flow is abnormal or not through the included bits, for example, a bit value of 0 indicates an abnormality, and a bit value of 1 indicates no abnormality; alternatively, it can also indicate whether the QoS flow is abnormal or not through the name of the first message; or it can also indicate whether the QoS flow is abnormal or not through the included bytes, for example, a byte of failure indicates an abnormality, and a byte of success indicates no abnormality. This application does not limit this aspect.

[0151] It is understandable that the first indication information can directly indicate that the first service quality flow has an anomaly.

[0152] For example, consider a first indication message indicating an anomaly in the Quality of Service (QoS) flow. When the first indication message includes the identifier of the first QoS flow, PCF network element #1 can determine that the first QoS flow is abnormal based on the identifier of the first QoS flow.

[0153] When the first indication information includes the identifier of the first quality of service flow and the first configuration information, PCF network element #1 can determine that the first quality of service flow is abnormal based on the identifier of the first quality of service flow, and determine that the abnormality of the first quality of service flow refers to adjusting the configuration of the first quality of service flow to the first configuration based on the first configuration information.

[0154] When the first indication information includes the identifier of the first application service, PCF network element #1 can determine that the service quality flow corresponding to the first application service is abnormal based on the identifier of the first application service. As shown in Figure 4a above, the first application service corresponds to the first service quality flow and the second service quality flow. The policy and charging control rule A bound to the first service quality flow is issued by PCF network element #1 to SMF network element #1. That is, the first service quality flow corresponds to PCF network element #1. Therefore, PCF network element #1 can determine that the service quality flow corresponding to the first application service is abnormal because the first service quality flow corresponding to the first application service is abnormal.

[0155] When the first indication information includes the identifier of the first application service and the first configuration information, PCF network element #1 can determine that the first service quality flow corresponding to the first application service is abnormal based on the identifier of the first application service, and determine that the abnormality of the first service quality flow refers to adjusting the configuration of the first service quality flow to the first configuration based on the first configuration information.

[0156] Alternatively, the first indication information can indirectly indicate that the first quality of service flow is abnormal.

[0157] For example, consider the first indication information indicating that the Quality of Service (QoS) flow is not abnormal. When the first indication information includes the identifier of the third QoS flow, PCF element #1 can determine that the third QoS flow is not abnormal based on the identifier of the third QoS flow. As shown in Figure 4a above, the policy and charging control rule A bound to the first QoS flow and the policy and charging control rule C bound to the third QoS flow are issued by PCF element #1 to SMF element #1. That is, both the first QoS flow and the third QoS flow correspond to PCF element #1. Therefore, when PCF element #1 determines that the third QoS flow is not abnormal, PCF element #1 can indirectly determine that the first QoS flow is abnormal.

[0158] S402: PCF network element #1 determines the association between the first quality of service flow and the second quality of service flow.

[0159] In this embodiment of the application, after PCF network element #1 receives the first message from SMF network element #1, PCF network element #1 can determine that the first quality of service flow is abnormal based on the first message.

[0160] As shown in Figure 4a above, the first service flow carried by the first quality of service flow belongs to the first application service, that is, the first quality of service flow corresponds to the first application service. Since there are correlations between multiple service flows of the same application service, there are also correlations between multiple quality of service flows carrying multiple service flows of the same application service. That is, multiple quality of service flows corresponding to the same application service need to be managed collaboratively. Therefore, when the first quality of service flow corresponding to the first application service experiences an anomaly, PCF network element #1 can determine the association between the first quality of service flow corresponding to the first application service and other quality of service flows corresponding to the first application service based on the identifier of the first application service, so as to notify other PCF network elements corresponding to the other quality of service flows corresponding to the first application service to perform collaborative management.

[0161] For example, PCF network element #1 determines the association between the first quality of service flow and the second quality of service flow based on the identifier of the first application service, and notifies the PCF network element #2 corresponding to the second quality of service flow to perform collaborative management. It can be understood that the second quality of service flow determined by PCF network element #1 refers to other quality of service flows besides the first quality of service flow corresponding to the first application service, and not to a specific quality of service flow.

[0162] In one possible implementation, after PCF network element #1 receives the first message from SMF network element #1, if the first indication information includes the identifier of the first quality of service flow, then PCF network element #1 can determine the identifier of the first application service based on the identifier of the first quality of service flow and the first mapping relationship. The first mapping relationship is the mapping relationship between the identifier of the quality of service flow and the identifier of the application service. The first mapping relationship can be pre-configured or standard-defined; this embodiment does not limit this.

[0163] For example, in the first mapping relationship, the identifier QFI#1 of the first quality of service flow corresponds to the identifier MMSID#1 of the first application service, the identifier QFI#2 of the second quality of service flow corresponds to the identifier MMSID#2 of the second application service, and the identifier QFI#3 of the third quality of service flow corresponds to the identifier MMSID#1 of the first application service.

[0164] S403: PCF network element #1 sends a second message to PCF network element #2, and correspondingly, PCF network element #2 receives the second message from PCF network element #1.

[0165] In this embodiment, after PCF network element #1 determines that the first quality of service flow is abnormal based on the first message and determines that the first quality of service flow is associated with the second quality of service flow, it needs to perform collaborative management of the first and second quality of service flows corresponding to the first application service to avoid resource waste. That is, if the first quality of service flow is abnormal (e.g., failure to establish the first quality of service flow, stopping the transmission of the first quality of service flow, releasing the resources of the first quality of service flow, or adjusting the configuration of the first quality of service flow), the second quality of service flow needs to undergo first processing (or abnormal processing). The first processing may include one or more of stopping transmission, releasing resources, or adjusting configuration, which is not limited in this embodiment.

[0166] As shown in Figure 4a above, the first Quality of Service (QoS) flow corresponds to PCF element #1, while the second QoS flow corresponds to PCF element #2. Specifically, PCF element #1 sends the policy and charging control rule A bound to the first QoS flow to SMF element #1, and PCF element #2 sends the policy and charging control rule B bound to the second QoS flow to SMF element #2. Therefore, PCF element #1 can send a second message to PCF element #2, and correspondingly, PCF element #2 receives the second message from PCF element #1. The second message may include second instruction information, which can be used to instruct PCF element #2 to perform first processing on the second QoS flow. This achieves collaborative management between the first and second QoS flows, avoiding resource waste.

[0167] In specific implementation, PCF network element #1 can directly send the second message to PCF network element #2, or it can indirectly send the second message to PCF network element #2 (e.g., via UDR network element). This application embodiment does not limit this. The following describes different situations.

[0168] In scenario one, PCF network element #1 directly sends the second message to PCF network element #2.

[0169] The second message can be a policy authorization notification (Npcf_PolicyAuthorization_Notify) message, or it can be other messages. This application embodiment does not limit the message name.

[0170] The second instruction information may include one or more of the following, which are described below.

[0171] 1) The identifier of the first application service. For example, the identifier of the first application service is MMSID#1.

[0172] 2) Second configuration information, wherein the second configuration information can be used to instruct PCF network element #2 to adjust the configuration of the second quality of service flow to the first configuration.

[0173] It is understood that the second indication information can indicate one or more of stopping transmission, releasing resources, or adjusting configuration through the included bits. For example, a bit value of 0 indicates stopping transmission and / or releasing resources, while a bit value of 1 indicates adjusting configuration. Alternatively, the name of the second message can also indicate one or more of stopping transmission, releasing resources, or adjusting configuration. This application embodiment does not limit this.

[0174] For example, consider the second instruction information indicating configuration adjustment. When the second instruction information includes the identifier of the first application service, PCF network element #2 can determine the configuration of the service quality flow corresponding to the first application service to be adjusted based on the identifier of the first application service. As shown in Figure 4a above, the first application service corresponds to the first service quality flow and the second service quality flow, and the policy and charging control rule B bound to the second service quality flow is issued by PCF network element #2 to SMF network element #2. That is, the second service quality flow corresponds to PCF network element #2. Therefore, PCF network element #2 can determine that adjusting the configuration of the service quality flow corresponding to the first application service means adjusting the configuration of the second service quality flow corresponding to the first application service.

[0175] For example, consider the second instruction information indicating configuration adjustment. When the second instruction information includes the identifier of the first application service and the second configuration information, PCF network element #2 can determine to adjust the configuration of the second quality of service flow corresponding to the first application service based on the identifier of the first application service, and determine to adjust the configuration of the second quality of service flow to the first configuration based on the second configuration information.

[0176] In one possible implementation, after PCF network element #1 determines that the first quality of service flow is associated with the second quality of service flow, it needs to determine the identifier of PCF network element #2 corresponding to the second quality of service flow in order to send a second message to PCF network element #2.

[0177] PCF network element #1 can obtain the identifier of PCF network element #2 locally. For example, PCF network element #1 can determine the identifier of PCF network element #2 based on the identifier of the first application service and the second mapping relationship. The second mapping relationship is the mapping relationship between the identifier of the application service and the identifier of the PCF network element. The second mapping relationship can be pre-configured; or it can be obtained from the BSF network element. For example, after PCF network element #1 creates policy and charging control rule A, PCF network element #1 sends the identifier of the first application service to the BSF network element to receive and store the second mapping relationship from the BSF network element. This application embodiment does not limit this aspect.

[0178] For example, in the second mapping relationship, the identifier MMSID#1 of the first application service corresponds to the identifier of PCF network element #1 and the identifier of PCF network element #2. That is to say, the policies and charging control rules for binding one or more service quality flows corresponding to the first application service are managed by PCF network element #1 and PCF network element #2.

[0179] If PCF network element #1 does not store the second mapping relationship locally, it can also obtain the identifier of PCF network element #2 from the BSF network element. For example, PCF network element #1 sends the identifier of the first application service to the BSF network element, and the BSF network element receives the identifier of the first application service from PCF network element #1. The identifier of the first application service is encapsulated or carried in a management discovery request (Nbsf_Management_Discovery request) message, or encapsulated or carried in other messages; this embodiment does not limit this. Similarly, if the BSF network element sends the identifier of PCF network element #2 to PCF network element #1, PCF network element #1 receives the identifier of PCF network element #2 from the BSF network element. The identifier of PCF network element #2 can be encapsulated or carried in a management discovery response (Nbsf_Management_Discovery response) message, or encapsulated or carried in other messages; this embodiment does not limit this.

[0180] Scenario 2: PCF network element #1 sends a second message to PCF network element #2 via UDR network element.

[0181] The second message can be a data management update (Nudr_DM_Update) message or a data management notification (Nudr_DM_Notify) message, or it can be other messages. This application embodiment does not limit the message name.

[0182] For example, PCF network element #1 sends a data management update message to UDR network element, and correspondingly, UDR network element receives the data management update message from PCF network element #1. UDR network element sends a data management notification message to PCF network element #2, and correspondingly, PCF network element #2 receives the data management notification message from UDR network element.

[0183] The second instruction information may include one or more of the following, which are described below.

[0184] 1) The identifier of the first application service. For example, the identifier of the first application service is MMSID#1.

[0185] 2) Second configuration information, wherein the second configuration information can be used to instruct PCF network element #2 to adjust the configuration of the second quality of service flow to the first configuration.

[0186] 3) First policy and charging control rules, wherein the first policy and charging control rules are obtained by PCF network element #1 updating the policy and charging control rules bound to the first quality of service flow (i.e., the above-mentioned policy and charging control rule A).

[0187] It is understood that the second indication information involved in Scenario 2 includes the identifier of the first application service and / or the specific description of the second configuration information. Please refer to the specific description of the relevant technical features in Scenario 1, which will not be repeated here.

[0188] It can be understood that PCF network element #1 can instruct the UDR network element to locate PCF network element #2. In other words, the UDR network element locates PCF network element #2 based on the second indication information, and then forwards the second indication information to PCF network element #2; that is, the UDR network element transparently transmits the second indication information. At this time, the second indication information may include the identifier of the first application service and / or the second configuration information to trigger the UDR network element to locate PCF network element #2.

[0189] PCF network element #1 can instruct the UDR network element to update the policy information of the first application service stored in the UDR network element. In other words, the UDR network element updates the policy information of the first application service stored in the UDR network element according to the second instruction information, thereby triggering PCF network element #2 to update the policy and charging control rules bound to the second quality of service flow (i.e., the aforementioned policy and charging control rule B). At this time, the second instruction information may include the first policy and charging control rule to trigger the UDR network element to update the policy information of the first application service stored in the UDR network element.

[0190] In one possible implementation, after PCF network element #2 receives the second message from PCF network element #1, if the second indication information includes the identifier of the first application service, then PCF network element #2 can determine the identifier of the second quality of service flow based on the identifier of the first application service and the first mapping relationship. The first mapping relationship is the mapping relationship between the identifier of the quality of service flow and the identifier of the application service. The first mapping relationship can be pre-configured or standard-defined; this embodiment does not limit this.

[0191] S404: PCF network element #2 sends a third message to SMF network element #2, and correspondingly, SMF network element #2 receives the third message from PCF network element #2.

[0192] In this embodiment, the third message may include third instruction information. The third instruction information may be used to instruct SMF network element #2 to perform first processing on the second quality of service flow.

[0193] In specific implementation, the third message may be a session management policy association modification (Nsmf_SMPolicyAssociation_Modification) message, or it may be other messages. This application embodiment does not limit the message name.

[0194] The third instruction information may include one or more of the following, which are described below.

[0195] 1) Identifier of the second Quality of Service (QoS) flow. For example, the identifier of the second QoS flow is QFI#2.

[0196] 2) The identifier of the first application service. For example, the identifier of the first application service is MMSID#1.

[0197] 3) Third configuration information, wherein the third configuration information can be used to instruct SMF network element #2 to adjust the configuration of the second quality of service flow to the first configuration.

[0198] 4) Second policy and charging control rules, wherein the second policy and charging control rules are obtained by PCF network element #2 updating the policy and charging control rules bound to the second quality of service flow (i.e. the above-mentioned policy and charging control rule B).

[0199] It is understood that the third indication information can indicate one or more of stopping transmission, releasing resources, or adjusting configuration through the included bits. For example, a bit value of 0 indicates stopping transmission and / or releasing resources, while a bit value of 1 indicates adjusting configuration. Alternatively, the name of the third message can also indicate one or more of stopping transmission, releasing resources, or adjusting configuration. This application embodiment does not limit this.

[0200] It is understandable that the third instruction information can directly instruct SMF network element #2 to perform the first processing on the second quality of service flow.

[0201] For example, consider the third instruction information indicating configuration adjustment. When the third instruction information includes the identifier of the second quality of service flow and the third configuration information, SMF network element #2 can determine to adjust the configuration of the second quality of service flow corresponding to the first application service based on the identifier of the second quality of service flow, and determine to adjust the configuration of the second quality of service flow corresponding to the first application service to the first configuration based on the third configuration information.

[0202] For example, consider the third instruction information indicating configuration adjustment. When the third instruction information includes the identifier of the first application service and the third configuration information, SMF network element #2 can determine to adjust the configuration of the service quality flow corresponding to the first application service based on the identifier of the first application service, and determine to adjust the configuration of the service quality flow corresponding to the first application service to the first configuration based on the third configuration information. As shown in Figure 4a above, the first application service corresponds to the first service quality flow and the second service quality flow. PCF network element #2 is responsible for sending the policy and charging control rule B bound to the second service quality flow to SMF network element #2, and SMF network element #2 is responsible for sending the service quality flow rules, service quality flow configuration, etc. of the second service quality flow to RAN #2. That is, the second service quality flow corresponds to SMF network element #2. Therefore, SMF network element #2 can determine that adjusting the configuration of the service quality flow corresponding to the first application service to the first configuration means adjusting the configuration of the second service quality flow corresponding to the first application service to the first configuration.

[0203] Alternatively, the third instruction information can indirectly instruct SMF network element #2 to perform the first processing on the second quality of service flow.

[0204] For example, consider the third instruction information indicating a configuration adjustment. When the third instruction information includes the second policy and charging control rule, SMF network element #2 can determine the difference between the second policy and charging control rule and the policy and charging control rule B previously issued to SMF network element #2 by PCF network element #2, and indirectly determine the configuration adjustment for the second quality of service flow based on this difference. Furthermore, SMF network element #2 can also indirectly determine the configuration adjustment for the second quality of service flow to the first configuration based on this difference.

[0205] In one possible implementation, after SMF network element #2 receives the third message from PCF network element #2, if the third indication information includes the identifier of the first application service, SMF network element #2 can determine the identifier of the second quality of service flow based on the identifier of the first application service and the first mapping relationship. The first mapping relationship is the mapping relationship between the identifier of the quality of service flow and the identifier of the application service. The first mapping relationship can be pre-configured or standard-defined; this embodiment does not limit this.

[0206] In one possible implementation, as shown in FIG4c, the present application may also perform the following steps before performing S401.

[0207] S401a: RAN#1 has determined that the first quality of service flow is abnormal.

[0208] For example, as shown in Figure 4a above, RAN#1 transmits the first Quality of Service (QoS) flow. The following example illustrates this: the first QoS flow includes three QoS flows, and the first service flow includes three service flows. For instance, the first QoS flow includes QoS flow 11, QoS flow 12, and QoS flow 13. QoS flow 11 carries service flow 11, QoS flow 12 carries service flow 12, and QoS flow 13 carries service flow 13. Service flows 11, 12, and 13 (i.e., the first service flow) belong to application service 1 (i.e., the first application service).

[0209] RAN#1 determines that the first quality of service flow is abnormal, which may include one or more of the following situations, which are described below.

[0210] 1) During the process of establishing the first Quality of Service (QoS) flow in RAN#1, QoS flow 11 failed to be established, but QoS flows 12 and 13 were established successfully. In other words, RAN#1 determined that QoS flow 11 was abnormal.

[0211] 2) During the transmission of the first Quality of Service (QoS) flow in RAN#1, if RAN#1 determines that it cannot guarantee the transmission of QoS flow 11 due to reasons such as transmission resources, for example, after UE#1 switches from RAN#3 to RAN#1, RAN#1 cannot guarantee the transmission of QoS flow 11. In this case, RAN#1 can stop the transmission of QoS flow 11, release the resources of QoS flow 11, or adjust the configuration of QoS flow 11. In other words, RAN#1 determines that QoS flow 11 has encountered an anomaly.

[0212] To ensure the normal operation of Application Service 1, RAN#1 needs to coordinate the management of Service Quality Flows 11, 12, and 13 corresponding to Application Service 1 to avoid resource waste. Therefore, RAN#1 can also stop the transmission of Service Quality Flows 12 and 13, release the resources of stopped Service Quality Flows 12 and 13, or adjust the configuration of Service Quality Flows 12 and 13. In other words, RAN#1 also determines that Service Quality Flows 12 and 13 are experiencing anomalies.

[0213] It is understandable that if Quality of Service (QoS) notification control (QNC) is enabled for QoS flow 11, then RAN#1, when unable to guarantee the transmission of QoS flow 11, can simply stop the transmission of QoS flow 11 without releasing its resources, and also stop the transmission of QoS flows 12 and 13. If QNC is not enabled for QoS flow 11, then RAN#1, when unable to guarantee the transmission of QoS flow 11, can release the transmission of QoS flow 11 and release the resources for QoS flows 12 and 13.

[0214] S401b: RAN#1 sends the fourth message to SMF network element #1, and correspondingly, SMF network element #1 receives the fourth message from RAN#1.

[0215] The fourth message may include the first instruction information.

[0216] Specifically, RAN#1 can send a fourth message to SMF network element #1 via AMF network element. This fourth message can be an N2 message and a PDU session context update request (Nsmf_PDUSession_UpdateSMContext_request) message, or it can be other messages. This application embodiment does not limit the message name.

[0217] It is understood that the specific description of the first indication information involved in S401b can be found in the specific description of the relevant technical features in S401, and will not be repeated here. Optionally, the fourth message may also include the identifier of the first PDU session (i.e., the PDU session of UE#1), wherein the identifier of the first PDU session is used by SMF network element #1 to modify the session. Optionally, if the fourth message includes the identifier of the first quality of service flow, then SMF network element #1 may also determine the identifier of the first application service based on the identifier of the first quality of service flow and the first mapping relationship.

[0218] In one possible implementation, as shown in FIG4c, after executing S404, the present application may further perform the following steps.

[0219] S404a: SMF network element #2 sends the fifth message to RAN #2, and RAN #2 receives the fifth message from SMF network element #2 accordingly.

[0220] The fifth message may include a fourth instruction message, which may be used to instruct RAN#2 to perform a first process on the second quality of service flow.

[0221] Specifically, SMF network element #2 can send a fifth message to RAN #2 via AMF network element. This fifth message can be a PDU session context update response (Nsmf_PDUSession_UpdateSMContext_response) message and an N2 message, or it can be other messages. This application embodiment does not limit the message name.

[0222] The fourth instruction information may include one or more of the following, which are described below.

[0223] 1) Identifier of the second Quality of Service (QoS) flow. For example, the identifier of the second QoS flow is QFI#2.

[0224] 2) The identifier of the first application service. For example, the identifier of the first application service is MMSID#1.

[0225] 3) Fourth configuration information, wherein the fourth configuration information can be used to instruct RAN#2 to adjust the configuration of the second quality of service flow to the first configuration.

[0226] It is understood that the fourth indication information can indicate one or more of stopping transmission, releasing resources, or adjusting configuration through the included bits. For example, a bit value of 0 indicates stopping transmission and / or releasing resources, while a bit value of 1 indicates adjusting configuration. Alternatively, the name of the fifth message can also indicate one or more of stopping transmission, releasing resources, or adjusting configuration. This application embodiment does not limit this.

[0227] For example, consider the fourth instruction information indicating configuration adjustment. When the fourth instruction information includes the identifier of the first application service and the fourth configuration information, RAN#2 can determine to adjust the configuration of the service quality flow corresponding to the first application service based on the identifier of the first application service, and determine to adjust the configuration of the service quality flow corresponding to the first application service to the first configuration based on the fourth configuration information. As shown in Figure 4a above, the first application service corresponds to the first service quality flow and the second service quality flow, and the second service quality flow is managed by RAN#2, that is, the second service quality flow corresponds to RAN#2. Therefore, RAN#2 can determine that adjusting the configuration of the service quality flow corresponding to the first application service to the first configuration means adjusting the configuration of the second service quality flow corresponding to the first application service to the first configuration.

[0228] Optionally, after RAN#2 receives the fifth message from SMF network element #2, if the fourth indication information includes the identifier of the first application service, RAN#2 can determine the identifier of the second quality of service flow based on the identifier of the first application service and the first mapping relationship. The first mapping relationship is the mapping relationship between the identifier of the quality of service flow and the identifier of the application service. The first mapping relationship can be pre-configured or standard-defined; this embodiment does not limit this.

[0229] It is understood that the above embodiments of this application can be implemented individually or in combination with each other, and the embodiments of this application are not limited.

[0230] The methods provided by the embodiments of this application have been described above with reference to the accompanying drawings. The apparatus provided by the embodiments of this application will be described below with reference to the accompanying drawings.

[0231] Based on the same technical concept, embodiments of this application provide a communication device, which includes a module / unit / means for executing the method performed by the device in the above-described method embodiments. This module / unit / means can be implemented in software, or in hardware, or implemented by hardware executing corresponding software.

[0232] For example, referring to FIG5, a schematic diagram of a communication device 500 is provided, which includes a transceiver module 501 and a processing module 502.

[0233] When device 500 is a first policy control function network element, the functions of each module of device 500 are as follows:

[0234] Transceiver module 501 is used to receive a first message from a session management network element, the first message including first indication information, the first indication information being used to indicate that a first quality of service flow has an anomaly;

[0235] Processing module 502 is used to determine the association between the first quality of service flow and the second quality of service flow;

[0236] The transceiver module 501 is used to send a second message to the second policy control function network element. The second message includes second indication information, which is used to instruct the second policy control function network element to perform a first process on the second quality of service flow. The first process includes one or more of stopping transmission, releasing resources, or adjusting configuration.

[0237] Alternatively, when the device 500 is a second policy control function network element, the functions of each module of the device 500 are as follows:

[0238] The transceiver module 501 is used to receive a second message from a first policy control function network element. The second message includes second indication information, which is used to instruct the second policy control function network element to perform a first process on the second quality of service flow. The first process includes one or more of stopping transmission, releasing resources, or adjusting configuration.

[0239] The transceiver module 501 is used to send a third message to the session management network element. The third message includes third indication information, which is used to instruct the session management network element to perform the first processing on the second quality of service flow.

[0240] Alternatively, when the device 500 is a session management network element, the functions of each module of the device 500 are as follows:

[0241] Transceiver module 501 is used to receive a fourth message from a first access network device, the fourth message including first indication information, the first indication information being used to indicate that a first quality of service flow has an anomaly;

[0242] Transceiver module 501 is used to send a first message to a first policy control function network element, the first message including the first indication information;

[0243] The transceiver module 501 is used to receive a third message from the first policy control function network element, the third message including third indication information, the third indication information being used to instruct the session management network element to perform the first processing on the second quality of service flow;

[0244] The transceiver module 501 is used to send a fifth message to the second access network device. The fifth message includes fourth indication information, which is used to instruct the second access network device to perform the first processing on the second quality of service flow.

[0245] In practical implementation, the above-mentioned device 500 can have various product forms. Several possible product forms are introduced below.

[0246] Referring to Figure 6, which is a schematic diagram of another communication device, the communication device 600 includes a processor 601 and an interface circuit 602. The interface circuit 602 is used to receive signals from other communication devices outside the communication device and transmit them to the processor 601, or to send signals from the processor 601 to other communication devices outside the communication device. The processor 601 is used to implement the methods executed by the first policy control function network element, the second policy control function network element, and the session management network element in the above method embodiments through logic circuits or execution instructions.

[0247] The processor 601 and the interface circuit 602 are coupled to each other. It is understood that the interface circuit 602 can be a transceiver or an input / output interface. Optionally, the communication device 600 may also include a memory 603 for storing instructions executed by the processor 601, or storing input data required by the processor 601 to execute instructions, or storing data generated after the processor 601 executes instructions.

[0248] It should be understood that the processor mentioned in the embodiments of this application can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, integrated circuit, etc. When implemented in software, the processor can be a general-purpose processor, implemented by reading software code stored in memory.

[0249] For example, the processor can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0250] It should be understood that the memory mentioned in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0251] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, the memory (storage module) can be integrated into the processor.

[0252] It should be noted that the memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.

[0253] Based on the same technical concept, embodiments of this application also provide a computer-readable storage medium storing a computer program or instructions. When the computer program or instructions are executed by a processor, the methods executed by the first policy control function network element, the second policy control function network element, and the session management network element in the above method embodiments are implemented.

[0254] Based on the same technical concept, this application also provides a computer program product, which includes a computer program or instructions. When the computer program or instructions are executed by a processor, the methods executed by the first policy control function network element, the second policy control function network element, and the session management network element in the above method embodiments are implemented.

[0255] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0256] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more blocks of the flowchart illustrations and / or one or more blocks of the block diagrams.

[0257] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0258] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

Claims

1. A communication method, characterized in that, The method, applied to a first policy control function network element, includes: Receive a first message from the session management network element, the first message including first indication information, the first indication information being used to indicate that a first quality of service flow has an anomaly; Determine the association between the first quality of service flow and the second quality of service flow; A second message is sent to the second policy control function network element. The second message includes second indication information, which is used to instruct the second policy control function network element to perform a first process on the second quality of service flow. The first process includes one or more of stopping transmission, releasing resources, or adjusting configuration.

2. The method according to claim 1, characterized in that, The first quality of service flow is used to carry the first service flow, and the second quality of service flow is used to carry the second service flow. The first service flow and the second service flow belong to the first application service.

3. The method according to claim 1 or 2, characterized in that, The first indication information includes one or more of the following: The identifier of the first service quality flow; The identifier of the third quality of service flow, wherein the third quality of service flow is a quality of service flow that has not experienced any anomalies; The first application service is the application service to which the first service flow carried by the first quality of service flow and the second service flow carried by the second quality of service flow belong; The first configuration information is used to indicate that the configuration of the first quality of service flow is the first configuration.

4. The method according to claim 3, characterized in that, The method further includes: Based on the identifier of the first quality of service flow and the first mapping relationship, the identifier of the first application service is determined, wherein the first mapping relationship is the mapping relationship between the identifier of the quality of service flow and the identifier of the application service.

5. The method according to any one of claims 1-4, characterized in that, The second instruction information includes one or more of the following: The first application service is the application service to which the first service flow carried by the first quality of service flow and the second service flow carried by the second quality of service flow belong; The second configuration information is used to instruct the second policy control function network element to adjust the configuration of the second quality of service flow to the first configuration; The first policy and charging control rules are obtained by updating the policy and charging control rules bound to the first quality of service flow by the first policy control function network element.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: Send the identifier of the first application service to the network element that supports the binding function. The first application service is the application service to which the first service flow carried by the first quality of service flow and the second service flow carried by the second quality of service flow belong. Receive the identifier of the second policy control function network element from the bound support function network element.

7. A communication method, characterized in that, The method, applied to a second policy control function network element, includes: Receive a second message from a first policy control function network element. The second message includes second indication information. The second indication information is used to instruct the second policy control function network element to perform a first process on the second quality of service flow. The first process includes one or more of stopping transmission, releasing resources, or adjusting configuration. A third message is sent to the session management network element, the third message including third indication information, the third indication information being used to instruct the session management network element to perform the first processing on the second quality of service flow.

8. The method according to claim 7, characterized in that, The second instruction information includes one or more of the following: The identifier of the first application service, which is the application service to which the second service flow carried by the second quality of service flow belongs; The second configuration information is used to instruct the second policy control function network element to adjust the configuration of the second quality of service flow to the first configuration; The first policy and charging control rules are obtained by the first policy control function network element updating the policy and charging control rules bound to the first quality of service flow according to the first message. The first quality of service flow is associated with the second quality of service flow.

9. The method according to claim 8, characterized in that, The method further includes: Based on the identifier of the first application service and the first mapping relationship, the identifier of the second quality of service flow is determined, whereby the first mapping relationship is the mapping relationship between the identifier of the quality of service flow and the identifier of the application service.

10. The method according to any one of claims 1-9, characterized in that, The third instruction information includes one or more of the following: The identifier of the second quality of service flow; The identifier of the first application service, which is the application service to which the second service flow carried by the second quality of service flow belongs; The third configuration information is used to instruct the session management network element to adjust the configuration of the second quality of service flow to the first configuration; The second policy and charging control rules are obtained by updating the policy and charging control rules bound to the second quality of service flow by the second policy control function network element.

11. A communication method, characterized in that, Applied to a session management network element, the method includes: Receive a fourth message from a first access network device, the fourth message including first indication information, the first indication information being used to indicate that an anomaly has occurred in the first quality of service flow; Send a first message to the first policy control function network element, the first message including the first indication information; Receive a third message from the first policy control function network element, the third message including third indication information, the third indication information being used to instruct the session management network element to perform the first processing on the second quality of service flow; A fifth message is sent to the second access network device, the fifth message including a fourth indication information, the fourth indication information being used to instruct the second access network device to perform the first processing on the second quality of service flow.

12. The method according to claim 11, characterized in that, The first quality of service flow is used to carry the first service flow, and the second quality of service flow is used to carry the second service flow. The first service flow and the second service flow belong to the first application service.

13. The method according to claim 11 or 12, characterized in that, The first indication information includes one or more of the following: The identifier of the first service quality flow; The identifier of the third quality of service flow, wherein the third quality of service flow is a quality of service flow that has not experienced any anomalies; The first application service is the application service to which the first service flow carried by the first quality of service flow and the second service flow carried by the second quality of service flow belong; The first configuration information is used to indicate that the configuration of the first quality of service flow is the first configuration.

14. The method according to claim 13, characterized in that, The method further includes: Based on the identifier of the first quality of service flow and the first mapping relationship, the identifier of the first application service is determined, wherein the first mapping relationship is the mapping relationship between the identifier of the quality of service flow and the identifier of the application service.

15. The method according to any one of claims 11-14, characterized in that, The third instruction information also includes one or more of the following: The identifier of the second quality of service flow; The identifier of the first application service, which is the application service to which the second service flow carried by the second quality of service flow belongs; The third configuration information is used to instruct the session management network element to adjust the configuration of the second quality of service flow to the first configuration; The second policy and charging control rules are obtained by updating the policy and charging control rules bound to the second quality of service flow by the second policy control function network element.

16. The method according to claim 15, characterized in that, The method further includes: Based on the identifier of the first application service and the first mapping relationship, the identifier of the second quality of service flow is determined, whereby the first mapping relationship is the mapping relationship between the identifier of the quality of service flow and the identifier of the application service.

17. The method according to any one of claims 11-16, characterized in that, The fourth instruction information also includes one or more of the following: The identifier of the second quality of service flow; The identifier of the first application service, which is the application service to which the second service flow carried by the second quality of service flow belongs; The fourth configuration information is used to instruct the second access network device to adjust the configuration of the second quality of service flow to the first configuration.

18. A communication device, characterized in that, The communication device includes a module for performing the method as described in any one of claims 1 to 6, or a module for performing the method as described in any one of claims 7 to 10, or a module for performing the method as described in any one of claims 11 to 17.

19. A communication device, characterized in that, The communication device includes a processor configured to perform the method as described in any one of claims 1 to 6, or the method as described in any one of claims 7 to 10, or the method as described in any one of claims 11 to 17.

20. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program that, when run on a computer, causes the method as described in any one of claims 1 to 6 to be performed, or causes the method as described in any one of claims 7 to 10 to be performed, or causes the method as described in any one of claims 11 to 17 to be performed.

21. A computer program product, characterized in that, The computer program product includes a computer program that, when run on a computer, causes the method as described in any one of claims 1 to 6 to be performed, or causes the method as described in any one of claims 7 to 10 to be performed, or causes the method as described in any one of claims 11 to 17 to be performed.

Citation Information

Patent Citations

  • Communication method and device

    CN116828620A

  • QoS control method and corresponding device

    CN117062145A

  • Collaborative operation method, information providing method, network element, and storage medium

    WO2023169558A1

  • Communication method and apparatus

    WO2024074095A1