Communication method and apparatus, and system

Abstract

The present application is applied to the technical field of communications. Provided are a communication method and apparatus, and a system. The communication method provided in the present application can assist a network in managing flows on the basis of a dependency relationship between the flows. The communication method comprises: a terminal device receiving first information, wherein the first information is used for indicating a first dependency relationship between a first flow and a second flow, the first dependency relationship comprising: the first flow being dependent on the second flow.

Description

Communication methods, devices and systems

[0001] This application claims priority to Chinese Patent Application No. 202411999415.4, filed with the State Intellectual Property Office of China on December 31, 2024, entitled "Communication Method, Apparatus and System", the entire contents of which are incorporated herein by reference. Technical Field

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

[0003] In communication systems, some services can achieve better data transmission through multiple Quality of Service (QoS) flows.

[0004] In scenarios where the same service is transmitted through multiple QoS flows, the network side assigns the same group number to these multiple QoS flows. When performing access control, the base station treats all QoS flows within the same group as a whole. For example, it may accept access from all QoS flows within this group, or it may reject access from all QoS flows within this group.

[0005] However, the above method suffers from poor business performance. Summary of the Invention

[0006] This application provides communication methods, apparatus, and systems that can improve service performance.

[0007] The embodiments of this application adopt the following technical solutions:

[0008] Firstly, a communication method is provided, which can be executed by a terminal device or by a module (e.g., a processor, chip, or chip system) applied to the terminal device. Taking the execution of the method by a terminal device as an example, the method includes: the terminal device receiving first information, the first information indicating a first dependency relationship between a first stream and a second stream, the first dependency relationship including: the first stream depends on the second stream.

[0009] Based on the communication method provided in the embodiments of this application, the network can indicate to the terminal device the dependency relationship between the first flow and the second flow. When managing the first flow and the second flow, the network can refer to the dependency relationship between the first flow and the second flow for management. Compared with directly treating the first flow and the second flow as a whole, this is more in line with the needs of some services and can improve the performance of services.

[0010] In one possible design, the first information is also used to indicate a second dependency between the first flow and the third flow, the second dependency including: the first flow depends on the third flow; wherein, there is a third dependency between the second flow and the third flow, the third dependency including: the second flow and the third flow depend on each other.

[0011] Based on this scheme, the dependencies between multiple flows can be indicated, which is convenient for reference when scheduling flows in the network.

[0012] In one possible design, the method further includes: the terminal device receiving second information, the second information indicating that the third stream depends on the second stream; and the terminal device receiving third information, the third information indicating that the second stream depends on the third stream.

[0013] This solution provides a method for indicating a third dependency relationship between a second stream and a third stream, which can be indicated by sending second information and third information respectively.

[0014] In one possible design, the second information is used to establish or modify a third stream, which in turn is used to establish or modify the second stream.

[0015] Based on this scheme, the dependencies between a stream and other streams can be indicated during the process of creating / modifying a stream.

[0016] In one possible design, the second information includes the identification information of the second stream, and the third information includes the identification information of the third stream.

[0017] Based on this scheme, the second information can indicate that the third flow depends on the second flow corresponding to the identification information through the identification information of the second flow, and the third information can indicate that the second flow depends on the third flow corresponding to the identification information through the identification information of the third flow.

[0018] In one possible design, the method further includes: the terminal device receiving identification information of a first stream group, wherein the multiple streams included in the first stream group are interdependent, and the first stream group includes a second stream and a third stream.

[0019] Based on this scheme, multiple interdependent flows can be grouped into the same flow group, and the flow group can be identified by identification information.

[0020] In one possible design, the first information includes identification information for a first flow group, which indicates the dependency between the first flow and flows in the first flow group. For example, the first information indicates that the first flow depends on flows in the first flow group.

[0021] Based on this scheme, the first information can carry the identification information of the first flow group to indicate the dependency relationship between the first flow and the flows in the first flow group, without having to carry the identification information of each flow in the first flow group, which can save signaling overhead.

[0022] In one possible design, the first information includes the identification information of the second stream.

[0023] Based on this scheme, the first information can indicate that the first flow depends on the second flow corresponding to the identification information through the identification information of the second flow.

[0024] In one possible design, the first information is used to indicate a first value corresponding to a first stream, and the method further includes: the terminal device receiving fourth information, which is used to indicate a second value corresponding to a second stream; the magnitude relationship between the first value and the second value is used to indicate a first dependency relationship.

[0025] Based on this scheme, the network can assign corresponding values ​​to streams, and the dependency relationship between different streams can be indicated by the size relationship between the values ​​corresponding to different streams.

[0026] In one possible design, the method further includes: a terminal device receiving fifth information, the fifth information being used to indicate a third value corresponding to a third stream, the second value being the same as the third value; wherein the magnitude relationship between the first value and the third value is used to indicate a second dependency relationship between the first stream and the third stream, the second dependency relationship including: the first stream depends on the third stream, the second value being the same as the third value, which is used to indicate mutual dependency between the second stream and the third stream.

[0027] This scheme provides a method to indicate the interdependence between different flows: when the values ​​corresponding to different flows are the same, it means that the different flows are interdependent.

[0028] In one possible design, the method further includes: a terminal device receiving sixth information, the sixth information being used to establish a first stream group, the first stream group including a second stream and a third stream, and the multiple streams included in the first stream group having dependencies on each other.

[0029] This solution provides a method to directly establish a flow group comprising multiple flows using a single message (or signaling, message), which saves signaling overhead compared to existing solutions where a single message can only establish one flow.

[0030] In one possible design, the sixth information includes the value corresponding to each flow in the first flow group, and the magnitude relationship between the values ​​corresponding to each flow, used to indicate the dependencies between the multiple flows included in the first flow group. Alternatively, in another possible design, the multiple flows included in the first flow group are interdependent.

[0031] Based on this scheme, the dependencies between multiple flows in a flow group can take different forms: depending on the magnitude of the values ​​corresponding to the multiple flows, the multiple flows can have the same or different dependencies. Alternatively, the dependencies between multiple flows in a flow group established through the sixth information can be mutual dependencies.

[0032] In one possible design, the first information includes the identification information of the second stream. Alternatively, in another possible design, the first information includes the identification information of the first stream group. Alternatively, in yet another possible design, the sixth information includes the value corresponding to each stream in the first stream group, and the first information includes a first value corresponding to the first stream, and the magnitude relationship between the first value and the value corresponding to each stream, used to indicate the dependency relationship between the first stream and each stream. Alternatively, in yet another possible design, the sixth information includes the value corresponding to the first stream group, and the first information includes a first value corresponding to the first stream, and the magnitude relationship between the value corresponding to the first stream group and the first value, used to indicate the dependency relationship between the first stream and the multiple streams included in the first stream group.

[0033] This solution provides several ways to indicate a first dependency relationship in the first information when the second flow belongs to a flow group: First, the first information can carry the identifier information of the second flow within the group, directly indicating that the first flow depends on the flow corresponding to that identifier. Alternatively, the first information can carry the identifier information of the flow group, indicating that the first flow depends on each flow in the flow group corresponding to that identifier, thus indicating that the first flow depends on the second flow. Alternatively, the first information can carry the value corresponding to the first flow, and the sixth information can carry the values ​​corresponding to each flow in the flow group (including the value corresponding to the second flow), thus indicating that the first flow depends on the second flow based on the magnitude relationship between the values ​​corresponding to the first and second flows. Alternatively, the first information can carry the value corresponding to the first flow, and the sixth information can carry the value corresponding to the flow group, thus indicating that the first flow depends on each flow in the flow group based on the magnitude relationship between the values ​​corresponding to the first flow and the flow group, thereby indicating that the first flow depends on the second flow.

[0034] In one possible design, the first information is used to establish a second flow group, the flow group comprising the first flow group having dependencies on the flow group comprising the first flow group.

[0035] Based on this scheme, the first flow can belong to another flow group, and flows in different flow groups can have dependencies.

[0036] In one possible design, the multiple flows included in the second flow group are interdependent.

[0037] In one possible design, the first information includes identification information for a first flow group. Alternatively, in another possible design, the sixth information includes the value corresponding to each flow in the first flow group, the first information includes the value corresponding to each flow in the second flow group, and the magnitude relationship between the values ​​of each flow in the second flow group and the values ​​of each flow in the first flow group, used to indicate the dependency relationship between each flow included in the second flow group and each flow included in the first flow group. Alternatively, in another possible design, the sixth information includes the value corresponding to the first flow group, the first information includes the value corresponding to the second flow group, and the magnitude relationship between the values ​​of the first flow group and the values ​​of the second flow group, used to indicate the dependency relationship between multiple flows included in the second flow group and multiple flows included in the first flow group.

[0038] This solution provides several ways to indicate a first dependency relationship in the case where the second flow belongs to the first flow group, and the first flow belongs to another flow group (the second flow group): First, the first information can carry the identification information of the first flow group, indicating that the flow in the second flow group depends on the flow in the flow group corresponding to the identification information, thus indicating that the first flow in the second flow group depends on the second flow in the first flow group. Alternatively, the first information can carry the value corresponding to each flow in the second flow group (including the value corresponding to the first flow), and the sixth information can carry the value corresponding to each flow in the first flow group (including the value corresponding to the second flow), thereby indicating that the first flow depends on the second flow through the size relationship between the values ​​corresponding to the first and second flows. Or, the first information can carry the value corresponding to the second flow group, and the sixth information can carry the value corresponding to the first flow group, thereby indicating that the flow in the second flow group depends on the flow in the first flow group through the size relationship between the values ​​corresponding to the first and second flows, thus indicating that the first flow depends on the second flow.

[0039] Secondly, a communication method is provided, which can be executed by a first network element or by a module (e.g., a processor, a chip, or a chip system) applied to the first network element. Taking the execution of the method by the first network element as an example, the method includes: the first network element sending first information, the first information being used to indicate a first dependency relationship between a first flow and a second flow, the first dependency relationship including: the first flow depends on the second flow.

[0040] Based on the communication method provided in the embodiments of this application, the network can indicate to the terminal device the dependency relationship between the first flow and the second flow. When managing the first flow and the second flow, the network can refer to the dependency relationship between the first flow and the second flow for management. Compared with directly treating the first flow and the second flow as a whole, this is more in line with the needs of some services and can improve the performance of services.

[0041] In one possible design, the first information is also used to indicate a second dependency between the first flow and the third flow, the second dependency including: the first flow depends on the third flow; wherein, there is a third dependency between the second flow and the third flow, the third dependency including: the second flow and the third flow depend on each other.

[0042] Based on this scheme, different degrees of dependency between multiple flows can be indicated, which is convenient for reference when scheduling flows in the network.

[0043] In one possible design, the method further includes: a first network element sending second information, the second information indicating that a third flow depends on a second flow; and the first network element sending and receiving third information, the third information indicating that the second flow depends on a third flow.

[0044] This solution provides a method for indicating a third dependency relationship between a second flow and a third flow, which can be jointly indicated by sending second information and third information respectively.

[0045] In one possible design, the second information is used to establish or modify the third stream, and the third information is used to establish or modify the second stream.

[0046] Based on this scheme, the dependencies between a stream and other streams can be indicated during the process of creating / modifying a stream.

[0047] In one possible design, the second information includes the identification information of the second stream, and the third information includes the identification information of the third stream.

[0048] Based on this scheme, the second information can indicate that the third flow depends on the second flow corresponding to the identification information through the identification information of the second flow, and the third information can indicate that the second flow depends on the third flow corresponding to the identification information through the identification information of the third flow.

[0049] In one possible design, the method further includes: a first network element sending identification information of a first flow group, wherein multiple flows included in the first flow group are interdependent, and the first flow group includes a second flow and a third flow.

[0050] Based on this scheme, multiple interdependent flows can be grouped into the same flow group, and the flow group can be identified by identification information.

[0051] In one possible design, the first information includes identification information for a first flow group, which is used to indicate the dependency between the first flow and the flows in the first flow group.

[0052] Based on this scheme, the first information can carry the identification information of the first flow group to indicate the dependency relationship between the first flow and the flows in the first flow group, without having to carry the identification information of each flow in the first flow group, which can save signaling overhead.

[0053] In one possible design, the first information includes the identification information of the second stream.

[0054] Based on this scheme, the first information can indicate that the first flow depends on the second flow corresponding to the identification information through the identification information of the second flow.

[0055] In one possible design, the first information is used to indicate the first value corresponding to the first flow, and the method further includes: the first network element sending fourth information, the fourth information being used to indicate the second value corresponding to the second flow; the magnitude relationship between the first value and the second value is used to indicate the first dependency relationship.

[0056] Based on this scheme, the network can assign corresponding values ​​to streams, and the dependency relationship between different streams can be indicated by the size relationship between the values ​​corresponding to different streams.

[0057] In one possible design, the method further includes: a first network element sending fifth information, the fifth information being used to indicate a third value corresponding to a third flow, the second value being the same as the third value; wherein, the magnitude relationship between the first value and the third value is used to indicate a second dependency relationship between the first flow and the third flow, the second dependency relationship including: the first flow depends on the third flow, the second value being the same as the third value, which is used to indicate mutual dependency between the second flow and the third flow.

[0058] This scheme provides a method to indicate the interdependence between different flows: when the values ​​corresponding to different flows are the same, it means that the different flows are interdependent.

[0059] In one possible design, the method further includes: a first network element sending sixth information, the sixth information being used to establish a first flow group, the first flow group including a second flow and a third flow, and the multiple flows included in the first flow group having dependencies on each other.

[0060] This solution provides a method to directly establish a stream group comprising multiple streams using a single message, which saves signaling overhead compared to existing solutions where a single message can only establish one stream.

[0061] In one possible design, the sixth information includes the value corresponding to each flow in the first flow group, the magnitude relationship between the values ​​corresponding to each flow, and is used to indicate the dependency relationship between the multiple flows included in the first flow group; or, the multiple flows included in the first flow group are interdependent.

[0062] Based on this scheme, the dependencies between multiple flows in a flow group can be in different ways: depending on the size relationship between the values ​​corresponding to the multiple flows, the multiple flows can have the same or different dependencies, or the multiple flows in the flow group can depend on each other.

[0063] In one possible design, the first information includes the identification information of the second stream; or, the first information includes the identification information of the first stream group; or, the sixth information includes the value corresponding to each stream in the first stream group, the first information includes the first value corresponding to the first stream, and the size relationship between the first value and the value corresponding to each stream, used to indicate the dependency relationship between the first stream and each stream; or, the sixth information includes the value corresponding to the first stream group, the first information includes the first value corresponding to the first stream, and the size relationship between the value corresponding to the first stream group and the first value, used to indicate the dependency relationship between the first stream and the multiple streams included in the first stream group.

[0064] This solution provides several ways to indicate first dependencies using first information.

[0065] In one possible design, the first information is used to establish a second flow group, the flow group comprising the first flow group having dependencies on the flow group comprising the first flow group.

[0066] Based on this scheme, the first flow can belong to another flow group, and flows in different flow groups can have dependencies.

[0067] In one possible design, the multiple flows included in the second flow group are interdependent.

[0068] In one possible design, the first information includes identification information for a first flow group; or, the sixth information includes the value corresponding to each flow in the first flow group, the first information includes the value corresponding to each flow in the second flow group, and the magnitude relationship between the value corresponding to each flow in the second flow group and the value corresponding to each flow in the first flow group, used to indicate the dependency relationship between each flow included in the second flow group and each flow included in the first flow group; or, the sixth information includes the value corresponding to the first flow group, the first information includes the value corresponding to the second flow group, and the magnitude relationship between the value corresponding to the first flow group and the value corresponding to the second flow group, used to indicate the dependency relationship between multiple flows included in the second flow group and multiple flows included in the first flow group.

[0069] This solution provides multiple ways to indicate the first dependency when the first flow belongs to a flow group.

[0070] Thirdly, a communication device is provided for implementing the method in the first aspect described above.

[0071] The communication device can be a terminal device (or a component, such as a chip, in any of the possible designs of the first aspect described above) in the first aspect.

[0072] The communication device includes modules, units, or means that implement the above methods. These modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions.

[0073] In one possible design, the communication device includes a transceiver module and a processing module: the transceiver module is used to receive first information, which indicates a first dependency relationship between a first stream and a second stream, the first dependency relationship including that the first stream depends on the second stream; the processing module is used to determine the first dependency relationship based on the first information.

[0074] In one possible design, the first information is also used to indicate a second dependency between the first flow and the third flow, the second dependency including: the first flow depends on the third flow; wherein, there is a third dependency between the second flow and the third flow, the third dependency including: the second flow and the third flow depend on each other.

[0075] In one possible design, the transceiver module is further configured to receive second information, which indicates that a third stream depends on the second stream. The transceiver module is also configured to receive third information, which indicates that the second stream depends on the third stream.

[0076] In one possible design, the second information is used to establish or modify the third stream, and the third information is used to establish or modify the second stream.

[0077] In one possible design, the second information includes the identification information of the second stream, and the third information includes the identification information of the third stream.

[0078] In one possible design, the transceiver module is also used to receive identification information of a first stream group, which includes multiple streams that are interdependent and includes a second stream and a third stream.

[0079] In one possible design, the first information includes identification information for a first flow group, which is used to indicate the dependency between the first flow and the flows in the first flow group.

[0080] In one possible design, the first information includes the identification information of the second stream.

[0081] In one possible design, the first information is used to indicate the first value corresponding to the first stream. The transceiver module is also used to receive the fourth information, which is used to indicate the second value corresponding to the second stream. The size relationship between the first value and the second value is used to indicate the first dependency relationship.

[0082] In one possible design, the transceiver module is also used to receive fifth information, which indicates the third value corresponding to the third stream, and the second value and the third value are the same; wherein, the magnitude relationship between the first value and the third value is used to indicate the second dependency relationship between the first stream and the third stream, and the second dependency relationship includes: the first stream depends on the third stream, and the second value and the third value are the same, which is used to indicate the mutual dependency between the second stream and the third stream.

[0083] In one possible design, the transceiver module is also used to receive a sixth message, which is used to establish a first stream group, which includes a second stream and a third stream, and there are dependencies between the multiple streams included in the first stream group.

[0084] In one possible design, the sixth information includes the value corresponding to each flow in the first flow group, the magnitude relationship between the values ​​corresponding to each flow, and is used to indicate the dependency relationship between the multiple flows included in the first flow group; or, the multiple flows included in the first flow group are interdependent.

[0085] In one possible design, the first information includes the identification information of the second stream; or, the first information includes the identification information of the first stream group; or, the sixth information includes the value corresponding to each stream in the first stream group, the first information includes the first value corresponding to the first stream, and the size relationship between the first value and the value corresponding to each stream, used to indicate the dependency relationship between the first stream and each stream; or, the sixth information includes the value corresponding to the first stream group, the first information includes the first value corresponding to the first stream, and the size relationship between the value corresponding to the first stream group and the first value, used to indicate the dependency relationship between the first stream and the multiple streams included in the first stream group.

[0086] In one possible design, the first information is used to establish a second flow group, the flow group comprising the first flow group having dependencies on the flow group comprising the first flow group.

[0087] In one possible design, the multiple flows included in the second flow group are interdependent.

[0088] In one possible design, the first information includes identification information for a first flow group; or, the sixth information includes the value corresponding to each flow in the first flow group, the first information includes the value corresponding to each flow in the second flow group, and the magnitude relationship between the value corresponding to each flow in the second flow group and the value corresponding to each flow in the first flow group, used to indicate the dependency relationship between each flow included in the second flow group and each flow included in the first flow group; or, the sixth information includes the value corresponding to the first flow group, the first information includes the value corresponding to the second flow group, and the magnitude relationship between the value corresponding to the first flow group and the value corresponding to the second flow group, used to indicate the dependency relationship between multiple flows included in the second flow group and multiple flows included in the first flow group.

[0089] Fourthly, a communication device is provided for implementing the method in the second aspect above.

[0090] The communication device includes modules, units, or means that implement the above methods. These modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions.

[0091] The communication device can be the first network element (or a component in the first network element, such as a chip) in any of the possible designs of the second aspect described above.

[0092] In one possible design, the communication device includes a transceiver module and a processing module: the processing module is used to determine first information, and the transceiver module is used to send the first information, the first information being used to indicate a first dependency relationship between a first stream and a second stream, the first dependency relationship including: the first stream depends on the second stream.

[0093] In one possible design, the first information is also used to indicate a second dependency between the first flow and the third flow, the second dependency including: the first flow depends on the third flow; wherein, there is a third dependency between the second flow and the third flow, the third dependency including: the second flow and the third flow depend on each other.

[0094] In one possible design, the transceiver module is also used to send second information, which indicates that a third stream depends on the second stream. The first network element sends and receives the third information, which indicates that the second stream depends on the third stream.

[0095] In one possible design, the second information is used to establish or modify the third stream, and the third information is used to establish or modify the second stream.

[0096] In one possible design, the second information includes the identification information of the second stream, and the third information includes the identification information of the third stream.

[0097] In one possible design, the transceiver module is also used to send identification information of a first stream group, which includes multiple streams that are interdependent and includes a second stream and a third stream.

[0098] In one possible design, the first information includes identification information for a first flow group, which is used to indicate the dependency between the first flow and the flows in the first flow group.

[0099] In one possible design, the first information includes the identification information of the second stream.

[0100] In one possible design, the first information is used to indicate the first value corresponding to the first stream. The transceiver module is also used to send fourth information, which is used to indicate the second value corresponding to the second stream. The size relationship between the first value and the second value is used to indicate the first dependency relationship.

[0101] In one possible design, the transceiver module is also used to send a fifth message, which indicates a third value corresponding to the third stream, and the second and third values ​​are the same; wherein, the magnitude relationship between the first and third values ​​is used to indicate a second dependency relationship between the first and third streams, and the second dependency relationship includes: the first stream depends on the third stream, and the second and third values ​​are the same, which is used to indicate that the second and third streams are mutually dependent.

[0102] In one possible design, the transceiver module is also used to send a sixth message, which is used to establish a first stream group, which includes a second stream and a third stream, and there are dependencies between the multiple streams included in the first stream group.

[0103] In one possible design, the sixth information includes the value corresponding to each flow in the first flow group, the magnitude relationship between the values ​​corresponding to each flow, and is used to indicate the dependency relationship between the multiple flows included in the first flow group; or, the multiple flows included in the first flow group are interdependent.

[0104] In one possible design, the first information includes the identification information of the second stream; or, the first information includes the identification information of the first stream group; or, the sixth information includes the value corresponding to each stream in the first stream group, the first information includes the first value corresponding to the first stream, and the size relationship between the first value and the value corresponding to each stream, used to indicate the dependency relationship between the first stream and each stream; or, the sixth information includes the value corresponding to the first stream group, the first information includes the first value corresponding to the first stream, and the size relationship between the value corresponding to the first stream group and the first value, used to indicate the dependency relationship between the first stream and the multiple streams included in the first stream group.

[0105] In one possible design, the first information is used to establish a second flow group, the flow group comprising the first flow group having dependencies on the flow group comprising the first flow group.

[0106] In one possible design, the multiple flows included in the second flow group are interdependent.

[0107] In one possible design, the first information includes identification information for a first flow group; or, the sixth information includes the value corresponding to each flow in the first flow group, the first information includes the value corresponding to each flow in the second flow group, and the magnitude relationship between the value corresponding to each flow in the second flow group and the value corresponding to each flow in the first flow group, used to indicate the dependency relationship between each flow included in the second flow group and each flow included in the first flow group; or, the sixth information includes the value corresponding to the first flow group, the first information includes the value corresponding to the second flow group, and the magnitude relationship between the value corresponding to the first flow group and the value corresponding to the second flow group, used to indicate the dependency relationship between multiple flows included in the second flow group and multiple flows included in the first flow group.

[0108] Fifthly, a communication device is provided, comprising: a processor configured to execute instructions stored in a memory, wherein when the processor executes the instructions, the communication device performs the method described in any of the preceding aspects. The communication device may be a terminal device (or a component, such as a chip, in any possible design of the first aspect). Alternatively, the communication device may be a first network element (or a component, such as a chip, in any possible design of the second aspect).

[0109] In one possible design, the communication device also includes a memory for storing computer instructions. Optionally, the processor and memory are integrated together, or they are separate.

[0110] In one possible design, the memory is coupled to the processor and is located outside the communication device.

[0111] A sixth aspect provides a communication device, comprising: a processor and an interface circuit for communicating with a module outside the communication device; the processor for executing the method described in any of the preceding aspects via logic circuitry or by running a computer program or instructions. The communication device may be a terminal device (or a component, such as a chip, in any possible design of the first aspect). Alternatively, the communication device may be a first network element (or a component, such as a chip, in any possible design of the second aspect).

[0112] Alternatively, the interface circuit can be a code / data read / write interface circuit, which receives computer execution instructions (which are stored in memory and may be read directly from memory or may be transmitted through other devices) and transmits them to the processor so that the processor runs the computer execution instructions to perform the methods described in any of the above aspects.

[0113] In one possible design, the communication device also includes a memory for storing computer programs or instructions. Optionally, the processor and memory are integrated together, or the processor and memory are separate.

[0114] In one possible design, the memory is coupled to the processor and is located outside the communication device.

[0115] In some possible designs, the communication device can be a chip or a chip system.

[0116] In a seventh aspect, this application provides a computer-readable storage medium storing instructions that, when executed on a computer, enable the computer to perform the methods described in the first to second aspects, or any possible design of the first to second aspects.

[0117] Eighthly, this application provides a computer program product containing instructions that, when executed on a computer, enable the computer to perform the methods described in the first to second aspects, or any possible design of the first to second aspects.

[0118] A ninth aspect provides a communication device (e.g., the communication device may be a chip or a chip system), the communication device including a processor for implementing the functions involved in the first to second aspects, or any possible design of the first to second aspects. In one possible design, the communication device further includes a memory for storing necessary program instructions and data. When the communication device is a chip system, it may be composed of chips or may include chips and other discrete devices.

[0119] In a tenth aspect, a communication system is provided, the communication apparatus including a terminal device and a first network element. The terminal device is used to implement the first aspect described above, or any possible design method of the first aspect. The first network element is used to implement the second aspect described above, or any possible design method of the second aspect.

[0120] The technical effects of any of the design methods in aspects three through ten can be found in the technical effects of the different design methods in aspects one through two above, and will not be repeated here.

[0121] It should be noted that any of the possible implementations of any of the above aspects can be combined, provided that the solutions do not contradict each other. Attached Figure Description

[0122] Figure 1 is a schematic diagram of the dependencies between the three QoS flows;

[0123] Figure 2 is a schematic diagram of the QoS architecture in a 5G system;

[0124] Figure 3 is a schematic diagram of the QoS flow creation process in a 5G system;

[0125] Figure 4 is a schematic diagram of a communication system applicable to an embodiment of this application;

[0126] Figure 5 is an interactive schematic diagram of a communication method provided in an embodiment of this application;

[0127] Figure 6 is a schematic diagram of an exemplary process provided in an embodiment of this application;

[0128] Figure 7 is a schematic diagram of an exemplary process provided in an embodiment of this application;

[0129] Figure 8 is a schematic diagram of an exemplary process provided in an embodiment of this application;

[0130] Figure 9 is a schematic diagram of an exemplary process provided in an embodiment of this application;

[0131] Figure 10 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

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

[0133] To facilitate understanding of the technical solutions of the embodiments of this application, a brief introduction to the relevant technologies of this application is given below.

[0134] 1. Multimodal:

[0135] Multimodal refers to the process where, if the Application Firewall (AF) determines that a service requires multiple QoS flows based on business needs, the AF will assign these multiple QoS flows the same group number, called the Multi-modality Service ID (MSSID). The AF sends the MMSID information, along with some synchronization requirements for these multiple QoS flows (such as video and audio data being aligned on the timeline with an error not exceeding 5ms), to the core network element responsible for QoS flow parameter settings: the Policy Control Function (PCF). When setting QoS parameters, the PCF can set the parameters according to the AF's requirements. For example, if the AF instructs that the difference in packet delay budget (PDB) between different QoS flows in the MMSID should not exceed 20ms, and the PCF sets the delay budget for QoS flow 1 in the MMSID to 40ms, then the delay budget for QoS flow 2 in the MMSID should be between 35ms and 45ms.

[0136] Furthermore, the PCF can send the MSSID information to the access network device. When performing access control, the access network device can treat the QoS flow within the same group as a whole, accepting access to all QoS flows within the group, or rejecting access to all QoS flows within the group.

[0137] 2. QoS Architecture in 5th Generation (5G) Mobile Communication Systems

[0138] In a 5G system, there can be one or more Protocol Data Unit (PDU) sessions between a terminal device and a User Plane Function (UPF) network element. A PDU session can contain one or more QoS flows. At the air interface between the terminal device and the access network device, the QoS flow is mapped to the radio bearer (RB). Between the access network device and the UPF network element, the QoS flow is mapped to the Next Generation-User Plane (NG-U) tunnel. If there are multiple QoS flows in a PDU session, QoS flows with similar QoS parameters can be mapped to the same RB at the air interface. Figure 2 shows an exemplary QoS architecture diagram in a 5G system, illustrating an example of multiple QoS flows within a single PDU session.

[0139] 3. QoS flow creation process in 5G system

[0140] Currently, in 5G systems, QoS flows are created through PDU session modification messages. This can be understood as follows: after the PDU session—the tunnel between the terminal device and the network—is established, a new QoS flow needs to be added within this tunnel. Therefore, this modification of the tunnel requires the use of PDU session modification messages. Establishing a QoS flow through PDU session modification can be initiated by the network itself or triggered by the terminal device.

[0141] Figure 3 illustrates the QoS flow creation process in a current 5G system. As shown in Figure 3, if the establishment of a QoS flow is triggered by a terminal device, the process includes S301: The terminal device sends a PDU session modification request to the network-side device. This PDU session modification request includes a QoS rule, where the QoS rule represents the QoS flow identifier (QFI) mapped to a certain service (e.g., the service can be represented by an Internet Protocol (IP) 5-tuple identifier). Optionally, the QoS flow ID may correspond to a set of standardized QoS parameters; otherwise, the PDU session request can carry a QoS flow description to define the QoS parameters associated with the QoS flow ID.

[0142] The QoS rule carried in the PDU session modification request sent by the terminal device is the QoS rule expected by the terminal device. The network-side device will refer to the QoS rule sent by the terminal device to configure the QoS flow, but will not necessarily configure it according to the QoS rule sent by the terminal device. The QoS flow is ultimately based on the parameters carried in the PDU session modification command sent by the network-side device to the terminal device in S302. The PDU session modification command carries the network-authorized QoS rule, and optionally, may also carry the network-authorized QoS flow description.

[0143] If the QoS flow is initiated by the network, the network-side device can proactively send a PDU session modification command to the terminal device, without being triggered by a PDU session modification request sent by the terminal device. Optionally, the network-side device's proactive sending of the PDU session modification command to the terminal device can be triggered by an auto-attack (AF).

[0144] In addition, according to the existing protocol, only one QoS flow can be created each time a PDU session is modified.

[0145] In addition, after the QoS flow is established, the terminal device can send a PDU session modification request to the network-side device to trigger a modification of the QoS flow. The network-side device can then send a PDU session modification command to the terminal device based on the request, carrying the modified QoS rule and, optionally, the modified QoS flow description. Alternatively, the network-side device can proactively send a PDU session modification command to the terminal device to modify the QoS flow.

[0146] Based on the above introduction to multimodal communication, if a service requires multiple QoS flows, the core network can allocate multiple QoS flows to the same group and notify the access network device based on the AF's requirements for the parameters of multiple QoS flows. When performing access control, the access network device treats the QoS flows in the same group as a whole, accepting access to all QoS flows in the group or rejecting access to all QoS flows in the group.

[0147] However, in practical applications, multiple QoS flows for a service may not be treated as a single entity. For example, different types of data in a service may have different requirements, and if multiple QoS flows are set up based on different types of data, these multiple QoS flows may have different dependencies.

[0148] Taking the text-based video service based on artificial intelligence-generated content (AIGC) as an example, users input text on the application (APP) of their terminal devices. The server generates a video based on the text content and provides it to the terminal devices. After watching the video for a period of time, users will have an initial reaction. The terminal devices can generate feedback information based on the user's initial reaction (such as facial features captured by the camera, the location where the user's eyes are focused, and the "satisfaction" selected by the user on the App interface) and send it back to the server. The server can then decide whether to optimize the subsequent video content based on the feedback information.

[0149] It can be seen that the Wensheng video service involves at least three types of data: text content, video data, and feedback information. These three types of data differ in volume and frequency, and have different requirements for network bandwidth, latency, and reliability. Therefore, different QoS flows can be used to transmit different types of data.

[0150] Furthermore, it can be seen that these three QoS flows are actually dependent on each other to varying degrees. For example, if the QoS flow corresponding to the text content is released for some reason (such as the terminal device switching base stations and the target base station performing access control), then the text-to-video service cannot continue, and the QoS flow corresponding to the video data, even if it survives, is meaningless, and vice versa. Therefore, it is evident that the QoS flow corresponding to the text content and the QoS flow corresponding to the video data are interdependent. The QoS flow corresponding to the feedback information depends on the QoS flow corresponding to the text / video data; if one of these two QoS flows is released, the QoS flow corresponding to the feedback information is also unnecessary to survive. However, the reverse is not true; even if the QoS flow corresponding to the feedback information is released, it does not affect the QoS flow corresponding to the text / video data.

[0151] It is evident that there are varying degrees of dependency among these three QoS flows. Abstractly, the dependency relationships among these three QoS flows are shown in Figure 1.

[0152] In summary, some services may have dependencies among multiple QoS flows, where one flow depends on another, but the first flow is not depended on by the second. In other words, the dependencies between different QoS flows may not be mutually dependent and cannot be treated as a single entity. However, current multimodal methods treat different QoS flows within a group as a whole, which is insufficient to meet service requirements and leads to poor service performance. To address this issue, embodiments of this application provide a communication method that can improve service performance.

[0153] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can represent A or B. "And / or" in this application is merely a description of 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, and B alone, where A and B can be singular or plural. Furthermore, in the description of this application, unless otherwise stated, "multiple" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and that "first" and "second" are not necessarily different. Meanwhile, in the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is being used as an example, illustration, or description. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of terms such as "exemplary" or "for example" is intended to present related concepts in a concrete manner for ease of understanding.

[0154] In the embodiments of this application, "instruction" can include direct and indirect instructions, as well as explicit and implicit instructions. The information indicated by a certain piece of information (such as the first information below) is called the information to be instructed. In the specific implementation process, there are many ways to instruct the information to be instructed, such as, but not limited to, directly instructing the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly instruct the information to be instructed by instructing other information, where there is a correlation between the other information and the information to be instructed. It can also instruct only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement order of various pieces of information, thereby reducing instruction overhead to some extent. At the same time, common parts of various pieces of information can be identified and uniformly indicated to reduce the instruction overhead caused by individually indicating the same information.

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

[0156] It should be understood that the information to be indicated can be sent as a whole or divided into multiple sub-information messages sent separately, and the sending period and / or timing of these sub-information messages can be the same or different. The specific sending method is not limited in this application embodiment. The sending period and / or timing of these sub-information messages can be predefined, for example, according to a protocol, or configured by the sending device by sending configuration information to the receiving device.

[0157] In this application embodiment, "predefined," "pre-configured," or "pre-configured" can be implemented by pre-saving corresponding codes, tables, or other methods that can be used to indicate relevant information in the device. For example, it can be burned into the device when it leaves the factory, or configured when it first connects to the network. This application embodiment does not limit the specific implementation method. "Saving" can refer to saving in one or more memories. The one or more memories can be separate settings or integrated into the encoder or decoder, processor, or communication device. The one or more memories can also be partially separate settings and partially integrated into the decoder, processor, or communication device. The type of memory can be any form of storage medium, and this application embodiment does not limit this.

[0158] The “protocol” mentioned in the embodiments of this application may refer to a protocol family in the field of communication, a standard protocol with a similar protocol family frame structure, or a related protocol applied to future communication systems. The embodiments of this application do not specifically limit this.

[0159] In the embodiments of this application, descriptions such as "when," "under the circumstances," "if," and "if" all refer to the device making corresponding processing under certain objective circumstances, and are not limited to a specific time. They do not require the device to make a judgment action during implementation, nor do they imply any other limitations.

[0160] In this embodiment of the application, "sending information" can be understood as one device sending information to another device, or it can also be understood as one logic module within a device sending information to another logic module. For example, "terminal device sending information" can be understood as a terminal device sending information to another device (such as the first network element), or it can be understood as logic module 1 in the terminal device sending information to logic module 2 in the terminal device.

[0161] In this application, "receiving information" can be understood as one device receiving information from another device, or it can also be understood as a logical module within a device receiving information from another logical module. For example, "terminal device receiving information" can be understood as the terminal device receiving information from another device (such as the first network element), or it can be understood as logical module 1 in the terminal device receiving information from logical module 2 in the terminal device.

[0162] In this application, the phrase "sending information to... (e.g., a terminal device)" or the related illustrations in the accompanying drawings can be understood as the destination of the information being the terminal device. This can include sending information directly or indirectly to the terminal device. Similarly, the phrases "receiving information from... (e.g., a terminal device)," "receiving information from... (e.g., a terminal device)," or "receiving information sent (e.g., by a terminal device)," or the related illustrations in the accompanying drawings, can be understood as the source of the information being the terminal. This can include receiving information directly or indirectly from the terminal. Information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be interpreted similarly, and will not be elaborated further here.

[0163] The technical solutions provided in this application can be used in various communication systems, such as 3GPP communication systems, including 4G mobile communication systems, Long Term Evolution (LTE) systems, 5G mobile communication systems and their evolution systems, NTN systems, NB-IoT systems, Vehicle-to-Everything (V2X) systems, LTE and New Radio (NR) hybrid networking systems, or device-to-device (D2D) systems, machine-to-machine (M2M) communication systems, Internet of Things (IoT) systems, Wireless Fidelity (WiFi) systems, and other communication systems, such as future communication systems. Furthermore, the term "system" can be used interchangeably with "network."

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

[0165] Figure 4 is a schematic diagram of a non-limiting, possible communication system applicable to an embodiment of this application. As shown in Figure 4, the communication system 10 includes a radio access network (RAN) 100 and a core network (CN) 200. RAN 100 includes at least one RAN node (110a and 110b in Figure 4, collectively referred to as 110) and at least one terminal device (120a-120j in Figure 4, collectively referred to as 120). RAN 100 may also include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices (not shown in Figure 4). Terminal device 120 is wirelessly connected to RAN node 110. RAN node 110 is wirelessly or wired connected to core network 200. The core network device in core network 200 and RAN node 110 in RAN 100 can be different physical devices, or they can be the same physical device integrating core network logical functions and radio access network logical functions.

[0166] Optionally, the communication system 10 also includes the Internet 300.

[0167] RAN 100 can be a cellular system related to the 3rd Generation Partnership Project (3GPP), such as 4G, 5G mobile communication systems, or future-oriented evolution systems. RAN 100 can also be an open RAN (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system. RAN 100 can also be a communication system that integrates two or more of the above systems.

[0168] RAN node 110, sometimes also referred to as access network equipment, RAN entity, or access node, constitutes part of the communication system and is used to help terminal devices achieve wireless access. Multiple RAN nodes 110 in communication system 10 can be of the same type or different types. In some scenarios, the roles of RAN node 110 and terminal device 120 are relative. For example, network element 120i in Figure 4 can be a helicopter or drone, which can be configured as a mobile base station. For terminal devices 120j accessing RAN 100 through network element 120i, network element 120i is a base station; but for base station 110a, network element 120i is a terminal device. RAN node 110 and terminal device 120 are sometimes both referred to as communication devices. For example, network elements 110a and 110b in Figure 4 can be understood as communication devices with base station functions, and network elements 120a-120j can be understood as communication devices with terminal functions.

[0169] In one possible scenario, the RAN node can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a base station in a future mobile communication system, or an access node in a WiFi system. The RAN node can be a macro base station (as shown in Figure 4, 110a), a micro base station or indoor station (as shown in Figure 4, 110b), a relay node or donor node, or a radio controller in a CRAN scenario. Optionally, the RAN node can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, in V2X technology, the RAN node can be a roadside unit (RSU). All or part of the functions of the RAN node in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). The RAN node can also be equipped with communication modules, circuits, or chips that perform corresponding communication functions. The RAN node can also be configured with program instructions for performing corresponding communication functions and corresponding program instructions. The RAN node in this application can also be a logical node, logical module, or software that can implement all or part of the functions of the RAN node.

[0170] In another possible scenario, multiple RAN nodes collaborate to assist terminal devices in achieving wireless access, with different RAN nodes each implementing a portion of the base station's functions. For example, RAN nodes can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs), etc. CUs and DUs can be set up separately or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

[0171] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0172] Terminal devices can be devices or modules that access the aforementioned communication system and have corresponding communication functions. Terminal devices can also be called terminals, user equipment (UE), mobile stations, mobile terminals, etc. Terminal devices can be widely used in various scenarios, such as D2D, V2X communication, machine-type communication (MTC), IoT, virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminal devices can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, transportation vehicles with wireless communication capabilities, communication modules, etc. The embodiments of this application do not limit the device form of the terminal device. Terminal devices typically contain communication modules, circuits, or chips that perform corresponding communication functions. Terminal devices can also be configured with program instructions for performing corresponding communication functions.

[0173] Logically, the core network can be divided into two parts: the user plane and the control plane. The control plane is responsible for mobile network management, while the user plane is responsible for service data transmission. Different network elements in the core network are responsible for different functions. Taking the 5G core network as an example, the access and mobility management function (AMF) network element is mainly responsible for user access management, security authentication, and mobility management. The session management function (SMF) network element is mainly responsible for interacting with the separate data plane, creating, updating, and deleting PDU sessions, and managing the session context with the UPF network element. The UPF network element is mainly responsible for managing user plane data transmission and traffic statistics.

[0174] In this embodiment of the application, the network element can also be referred to as an entity or functional entity.

[0175] The communication method provided in the embodiments of this application will be described in detail below with reference to Figure 4.

[0176] It should be noted that the message name or the name of each parameter in the message in the following embodiments of this application is just an example, and other names may be used in the specific implementation. This application does not specifically limit this.

[0177] It should be noted that the names of various network elements in the following embodiments of this application are merely examples, and may be used in specific implementations. This application does not impose specific limitations on these names. For instance, the SMF network element in the following embodiments may also have other names in future communication networks.

[0178] Figure 5 illustrates a communication method provided in an embodiment of this application. Figure 5 uses a terminal device and a first network element as illustrative examples to illustrate the method, but this application does not limit the illustrative execution entities. For example, the terminal device in Figure 5 could also be a module applied to the terminal device, such as a chip, chip system, or processor, or it could be a logical node, logical module, or software capable of implementing all or part of the terminal device's functions. Similarly, the first network element in Figure 5 could also be a module applied to the first network element, such as a chip, chip system, or processor, or it could be a logical node, logical module, or software capable of implementing all or part of the first network element's functions. The communication method includes the following steps:

[0179] S501, the first network element sends first information to the terminal device, and the terminal device receives the first information accordingly. The first information indicates a first dependency relationship between the first flow and the second flow, including that the first flow depends on the second flow.

[0180] Based on the communication method provided in the embodiments of this application, the network can indicate to the terminal device the dependency relationship between the first flow and the second flow. When managing the first flow and the second flow, the network can refer to the dependency relationship between the first flow and the second flow for management. Compared with directly treating the first flow and the second flow as a whole, this is more in line with the needs of some services and can improve the performance of services.

[0181] The embodiments of this application do not limit the first network element. For example, the first network element may be an SMF network element.

[0182] In this embodiment, different flows may have dependencies on each other. Here, "flow" is used to transmit data, and can also be referred to as a data transmission channel or other name representing the flow used to transmit data. For example, a flow can be a QoS flow, a data flow, a service flow, etc.

[0183] Taking two different flows, a and b, as an example, the dependency relationship between flows a and b can include: flow a depends on flow b, flow b depends on flow a, or flow a and flow b depend on each other. Here, "flow a depends on flow b" can also be expressed as "flow b is dependent on flow a", and "flow b depends on flow a" can also be expressed as "flow a is dependent on flow b".

[0184] In this embodiment, the dependency relationship between flows describes a unidirectional dependency. A flow that is depended upon will affect flows that depend on it. Conversely, if no opposite dependency is established, a flow that depends on another flow will not affect the flow it depends on. In this embodiment, the mutual dependency between flows describes a bidirectional dependency, where any flow will affect the other. These effects include, for example, impacts on services, data transmission, network management flows, access control of flows executed by RAN nodes, and adjustments to flow-related parameters. The following describes the dependency relationship between flows from different perspectives.

[0185] Alternatively, the unidirectional dependency between different flows can be understood from the perspective of their impact on business operations. Taking flow a's dependency on flow b as an example, this can be understood as follows: if flow b is dismantled, then flow a will also become meaningless for its corresponding business. In other words, whether flow a is dismantled or not after flow b is dismantled has no difference in impact on the business. Or, the impact of "flow a continues to transmit after flow b is dismantled" and "flow a is also dismantled after flow b is dismantled" is the same for the business. If flow a is dismantled, flow b will still be meaningful for its corresponding business. In other words, whether flow b is dismantled or not after flow a is dismantled makes a difference in the operation of the business. Or, the impact of "flow b continues to be maintained after flow a is dismantled" and "flow b is also dismantled after flow a is dismantled" is different for the business.

[0186] Taking the dependency relationship between the three QoS streams in the text-based video service as shown in Figure 1, if the QoS stream corresponding to the text content / video data is torn down, the service cannot continue. In this case, whether the QoS stream corresponding to the feedback information is torn down or maintained is meaningless for the text-based video service. Conversely, if the QoS stream corresponding to the feedback information is torn down, the server can still generate video based on the user-input text content, the service can continue, and the QoS stream corresponding to the text content / video data is still meaningful for the text-based video service.

[0187] The application scenarios of the communication method provided in this application embodiment are not limited. The service and the dependency relationship between different streams shown in Figure 1 are only a possible example. The communication method provided in this application embodiment is not limited to the example shown in Figure 1, nor is it limited to AI-related services.

[0188] Alternatively, the bidirectional dependency between different flows can be understood from the perspective of their impact on business operations. Taking the interdependence of flows a and b as an example, the interdependence of flows a and b can be understood as follows: if either flow a or flow b is removed, the other flow will also become meaningless to the business. In other words, whether the other flow is removed or not after either flow a or flow b is removed has no difference in impact on the business. Or, the impact on the business is the same whether "the other flow continues to be maintained after either flow a or flow b is removed" or "the other flow is also removed after either flow a or flow b is removed".

[0189] Taking the dependency relationship between the three QoS streams in the text-based video service as shown in Figure 1, if the QoS stream corresponding to the text content is torn down, the server cannot generate video based on the user's input text content, and the service cannot continue. In this case, whether the QoS stream corresponding to the video data is torn down or maintained is meaningless for the text-based video service. Conversely, if the QoS stream corresponding to the video data is torn down, the server will not generate video based on the user's input text content, and the service cannot continue. In this case, whether the QoS stream corresponding to the text content is torn down or maintained is meaningless for the text-based video service.

[0190] Alternatively, the unidirectional dependency between different streams can be understood from the perspective of their impact on data transmission. Taking stream a's dependency on stream b as an example, this can be understood as follows: if stream b is dismantled, no data will be transmitted through stream a. If stream a is dismantled, stream b can still transmit data.

[0191] Taking the dependency relationship between the three QoS streams in the text-based video service as shown in Figure 1, if the QoS stream corresponding to the text content / video data is torn down, the service cannot continue. At this time, the server stops generating video, and the terminal device cannot obtain feedback information about the video. The QoS stream corresponding to the feedback information has no data to carry. Conversely, if the QoS stream corresponding to the feedback information is torn down, the server can still generate video based on the user-input text content, the service can continue, and the QoS stream corresponding to the text content / video data can still transmit data.

[0192] Alternatively, the bidirectional dependency between different streams can be understood from the perspective of its impact on data transmission. Taking the interdependence of stream a and stream b as an example, the interdependence of stream a and stream b can be understood as follows: if either stream a or stream b is dismantled, no data will be transmitted through the other stream.

[0193] Taking the dependency relationship between the three QoS streams in the text-based video service as shown in Figure 1 as an example, if any one of the QoS streams corresponding to the text content and the video data is removed, the server cannot generate video based on the text content, and the other QoS stream has no data to carry.

[0194] Optionally, the unidirectional or bidirectional dependencies between different flows can be understood from the perspective of network flow management. Taking flow a's dependence on flow b as an example, this can be understood as: if flow b is dismantled, flow a also needs to be dismantled. If flow a is dismantled, flow b does not need to be dismantled. Taking the mutual dependence of flows a and b as an example, this can be understood as: if either flow a or flow b is dismantled, the other flow also needs to be dismantled.

[0195] Optionally, the unidirectional or bidirectional dependency relationships between different flows can be understood from the perspective of RAN node access control. Taking flow a's dependency on flow b as an example, when the RAN node performs access control on flows a and b, if the RAN node rejects flow b's access, it also needs to reject flow a's access. Conversely, if the RAN node rejects flow a's access, it may not necessarily reject flow b's access and may accept flow b's access. Taking the mutual dependency between flows a and b as an example, when the RAN node performs access control on flows a and b, if the RAN node rejects access to either flow b or flow a, it also needs to reject the other flow's access.

[0196] Optionally, the unidirectional or bidirectional dependency between different flows can be understood from the perspective of RAN node redirection / migration. Taking flow a's dependency on flow b as an example, when the RAN node redirects / migrates flow a and flow b, if flow b switches from its original RAN node A / slice A / cell A / carrier A to the target RAN node B / slice B / cell B / carrier B, then flow a also needs to switch to the target RAN node B / slice B / cell B / carrier B. Conversely, if flow a switches from its original RAN node A / slice A / cell A / carrier A to the target RAN node B / slice B / cell B / carrier B, flow b does not necessarily need to switch to the target RAN node B / slice B / cell B / carrier B.

[0197] Optionally, the unidirectional or bidirectional dependency between different flows can be understood by adjusting the relevant parameters of the flows. Taking flow a's dependency on flow b as an example, if flow b's relevant parameters are adjusted, then flow a also needs to have its parameters adjusted accordingly to ensure that the difference between the values ​​of those parameters in flow a and flow b is within a certain range. For example, if flow b's PDB is adjusted, flow a also needs to have its PDB adjusted to ensure that the difference between the PDB values ​​of flow a and flow b is within a certain range. Conversely, if flow a's relevant parameters are adjusted, flow b may not need to have its parameters adjusted accordingly. Taking the mutual dependency between flow a and flow b as an example, if either flow a or flow b has its relevant parameters adjusted, then the other flow also needs to have its parameters adjusted accordingly to ensure that the difference between the values ​​of those parameters in flow a and flow b is within a certain range.

[0198] In this embodiment of the application, different flows that have a dependency relationship may belong to the same service, or they may belong to different services.

[0199] The following embodiments use the example of a first dependency relationship including a first stream depending on a second stream. If the first dependency relationship is another dependency relationship, such as a second stream depending on a first stream, or a first stream and a second stream depending on each other, the communication method provided in this application embodiment can still be applied.

[0200] Optionally, in this embodiment, a flow may belong to a flow group, and a flow group includes multiple flows. Taking the first flow and the second flow as examples, the first flow may belong to the second flow group, and / or the second flow may belong to the first flow group.

[0201] Optionally, the first network element or terminal device can assign identification information to the flow group, for example, it can assign a unique ID to the flow group.

[0202] In one possible implementation, identification information can be assigned to a flow group first, and then the flow within that flow group can be established. In this implementation, the identification information assigned to the flow group can be transmitted between the first network element and the terminal device first, followed by a message for establishing the flow. This message for establishing the flow can carry the identification information of the flow group to indicate the flow group to which the flow belongs. Specifically, the transmission of the identification information assigned to the flow group between the first network element and the terminal device can be either the first network element assigning the identification information to the flow group and sending it to the terminal device, or the terminal device assigning the identification information to the flow group and sending it to the first network element. This application embodiment does not limit the message carrying the identification information of the flow group; it can be an existing message or a newly defined message.

[0203] The message used to establish the flow can be sent proactively by the terminal device or by the first network element. For details, please refer to the above introduction to the QoS flow creation process in Figure 3.

[0204] In another possible implementation, a flow can be established first, and then identification information can be assigned to a flow group to determine the flows included in that flow group. In this implementation, the first network element and the terminal device can first transmit a message for establishing a flow. After the first network element or the terminal device assigns identification information to a flow group and determines that the flow group includes the already established flows, the first network element and the terminal device can transmit a message for modifying the flow. This message for modifying the flow can carry the identification information of the flow group to indicate the flow group to which the flow belongs. The message for modifying the flow can be sent actively by the terminal device or by the first network element. For details, please refer to the above description of the QoS flow creation process in Figure 3.

[0205] In another possible implementation, the first network element or terminal device can establish a flow group comprising multiple flows through a single message. Optionally, the message used to establish the flow group may carry identification information of the flow group; this implementation will be described in detail later and will not be elaborated on here.

[0206] Optionally, the multiple flows included in a flow group may have dependencies on each other. Specifically, the multiple flows in a flow group may have one type of dependency; for example, any two flows in a flow group may be mutually dependent. Alternatively, the multiple flows in a flow group may have multiple types of dependencies; for example, suppose a first flow group includes a second, third, and fourth flow, where the second and third flows are mutually dependent, and the second flow depends on the fourth flow.

[0207] Optionally, multiple flows included in one flow group may have dependencies on multiple flows included in another flow group. Specifically, these dependencies may be singular; for example, all flows in the second flow group depend on flows in the first flow group. Alternatively, multiple dependencies may exist between multiple flows in one flow group and multiple flows in another flow group. For instance, suppose the first flow group includes the second and third flows, and the second flow group includes the first and fourth flows, where the first flow depends on the second and third flows, and the fourth flow is depended upon by the second and third flows.

[0208] Optionally, the flow group can be divided by the first network element based on the dependencies between different flows. In one possible implementation, the first network element can divide multiple interdependent flows into the same flow group. For example, the first network element can assign the second and third flows to the first flow group based on the interdependence between them, send the identification information of the first flow group to the terminal device, and indicate that the second and third flows belong to the first flow group. If the first network element later discovers that the fourth flow is interdependent with the second flow, and also interdependent with the third flow, the first network element can also assign the fourth flow to the first flow group, and include the identification information of the first flow group in the information sent to the terminal device for establishing / modifying the fourth flow.

[0209] In another possible implementation, the first network element can group multiple flows that have the same dependency relationship with a certain flow into the same flow group. For example, assuming that the first flow depends on the second flow and the fourth flow also depends on the second flow, the first network element can assign the fourth flow and the first flow to the first flow group.

[0210] This application does not limit the specific implementation of the first information indicating the first dependency relationship in the embodiments. Several possible implementations are introduced below.

[0211] Implementation Method 1: The first information includes the identification information of the second stream, such as the ID of the second stream. The terminal device can determine that the first stream depends on the second stream corresponding to the identification information in the first information.

[0212] Optionally, in implementation method one, the second stream can be a stream established before the first stream.

[0213] Optionally, the first information can be carried in a message used to establish / modify the first stream (or, the first information can be used to establish / modify the first stream), for example, the first information can be carried in a PDU session modification command message. Alternatively, if the first stream belongs to a stream group, the first information can be carried in a message used to establish / modify the stream group (or, the first information can be used to establish / modify the stream group). Alternatively, the first information can be carried in other messages, for example, the first information can be carried in a newly defined message used to indicate dependencies, which is not limited in this embodiment.

[0214] Optionally, the first information can be a newly defined information cell used to indicate the existence of dependencies between different streams.

[0215] For example, the first information could be a new information element in the message used to establish / modify a flow. If this information element includes the identification information of an already established flow, it indicates that "the currently established / modified flow depends on the flow corresponding to the identification information." Alternatively, if this information element does not include the identification information of an already established flow, it can indicate that "the currently established / modified flow does not depend on other already established flows."

[0216] For example, the first information could be a newly added information element in the message used to establish / modify a flow group. If this information element includes the identification information of an already established flow, it indicates that "the flow in the currently established / modified flow group depends on the flow corresponding to the identification information." Alternatively, if this information element does not include the identification information of an already established flow, it can indicate that "the currently established / modified flow group does not depend on other already established flows."

[0217] For example, the first piece of information could be a new information cell that includes identification information for different flows. This information cell can indicate the dependencies between different flows through the order in which the identification information for different flows is arranged. For instance, it can be predefined that when this information cell includes identification information for two flows, the flow corresponding to the earlier identification information depends on the flow corresponding to the later identification information. Alternatively, it can be predefined that in this information cell, the flow corresponding to the later identification information depends on the flow corresponding to the earlier identification information.

[0218] Implementation Method 2: The first information includes the identification information of a first flow group, which includes a second flow and at least one other flow. The first information can indicate that the first flow depends on each flow in the first flow group by carrying the identification information of the first flow group.

[0219] Optionally, in implementation method two, the first flow group may include multiple flows established prior to the first flow.

[0220] Optionally, the first information can be carried in a message used to establish / modify the first stream. Alternatively, if the first stream belongs to a stream group, the first information can be carried in a message used to establish / modify the stream group. Alternatively, the first information can be carried in other messages; for example, the first information can be carried in a newly defined message used to indicate dependencies. This embodiment of the application does not limit this approach.

[0221] Optionally, the first information can be a newly defined information cell used to indicate the dependency relationship between a stream and a stream group.

[0222] For example, the first information could be a newly added information element in the message used to establish / modify a flow. If this information element includes the identification information of the flow group, it indicates that "the currently established / modified flow depends on the flow in the flow group corresponding to the identification information". Alternatively, if this information element does not include the identification information of the flow group, it can indicate that "the currently established / modified flow does not depend on the flow in the already established flow group".

[0223] For example, the first information could be a new information element that includes both flow identification information and flow group identification information. This information element can indicate the dependency relationship between a flow and a flow group through the order in which the flow identification information and flow group identification information are included. For instance, it can be predefined that when this information element includes both flow identification information and flow group identification information, if the flow identification information precedes the flow group identification information, then the flow depends on the flow in the flow group; if the flow group identification information precedes the flow identification information, then the flow is depended on by the flow in the flow group. Alternatively, it can be predefined that when this information element includes both flow identification information and flow group identification information, if the flow identification information precedes the flow group identification information, then the flow is depended on by the flow in the flow group; if the flow group identification information precedes the flow identification information, then the flow depends on the flow in the flow group.

[0224] Optionally, the first information can be a newly defined information cell used to indicate the dependency relationship between flow groups.

[0225] For example, the first information could be a newly added information element in a message used to establish / modify a flow group. If this information element includes the identification information of an already established flow group, it indicates that "the flow in the currently established / modified flow group depends on the flow in the flow group corresponding to the identification information." Alternatively, if this information element does not include the identification information of an already established flow group, it can indicate that "the flow in the currently established / modified flow group does not depend on the flow in other flow groups."

[0226] For example, the first information could be a new information cell that includes identification information of different flow groups. This information cell can indicate the dependency relationship between flows in different flow groups through the order of the identification information of the different flow groups included. For details, please refer to the above introduction on how information cells indicate the dependency relationship between flows and flow groups through the order of the identification information of the flows and the identification information of the flow groups included.

[0227] Implementation Method 3: The first information includes the first value corresponding to the first flow. The first network element will also send information indicating the second value corresponding to the second flow to the terminal device (this information indicating the second value can be called the fourth information). After receiving the fourth information and the first information, the terminal device can determine that the first flow depends on the second flow based on the size relationship between the first value and the second value. That is, the size relationship between the first value and the second value can be used to indicate the first dependency relationship.

[0228] In implementation method three, the first network element can set corresponding values ​​for flows and indicate them to the terminal device. The magnitude relationship between the values ​​corresponding to different flows can indicate the dependency relationship between different flows. For example, it can be predefined that if the value corresponding to one flow is greater than the value corresponding to another flow, then that flow depends on the other flow; if the value corresponding to one flow is less than the value corresponding to another flow, then that flow is depended on by the other flow. Alternatively, it can be predefined that if the value corresponding to one flow is greater than the value corresponding to another flow, then that flow is depended on by the other flow; if the value corresponding to one flow is less than the value corresponding to another flow, then that flow depends on the other flow. Furthermore, it can be predefined that if the value corresponding to one flow is the same as the value corresponding to another flow, then that flow and the other flow are mutually dependent.

[0229] This application does not limit the implementation method of determining the value corresponding to the flow by the first network element. Taking the first value and the second value as examples, the first value can be a random value generated by the first network element, and the second value can be obtained by adding / subtracting a predefined value from the first value; or, the second value can be a random value generated by the first network element, and the first value can be obtained by adding / subtracting a predefined value from the second value. For another example, the first value and the second value can be generated by the first network element according to a pre-configured algorithm.

[0230] Optionally, the first information / fourth information can be a newly defined information element, which can carry the value corresponding to the stream.

[0231] Optionally, the first information can be carried in a message used to establish / modify a first stream, and the fourth information can be carried in a message used to establish / modify a second stream (or, the fourth information can be used to establish / modify a second stream). Alternatively, if the first stream belongs to a stream group, the first information can be carried in a message used to establish / modify the stream group; if the second stream belongs to a stream group, the fourth information can be carried in a message used to establish / modify the stream group. Alternatively, the first and fourth information can be carried in other messages, for example, the first and fourth information can be carried in a newly defined message used to indicate dependencies; this embodiment of the application does not limit this.

[0232] The embodiments of this application do not limit the timing of the transmission of the first information and the fourth information. The first information may be sent before the fourth information, after the fourth information, or at the same time.

[0233] Optionally, if the first flow belongs to the second flow group and the second flow belongs to the first flow group, the size relationship between the values ​​corresponding to the flows included in the first flow group and the values ​​corresponding to the flows included in the second flow group can indicate the dependency relationship between the flows included in the first flow group and the flows included in the second flow group.

[0234] When the first flow belongs to the second flow group, optionally, each flow in the second flow group can have its own corresponding value. The values ​​corresponding to different flows can be the same or different; that is, the first value indicated by the first information is indicated at the flow level. Optionally, the first information can also indicate the values ​​corresponding to one or more other flows in the second flow group. For example, the first information can indicate the value corresponding to each flow in the second flow group. Alternatively, the second flow group can correspond to a single value, which is the first value; it can also be understood that each flow in the second flow group corresponds to the first value. The first information can indicate the first value corresponding to the second flow group; that is, the first value indicated by the first information is indicated at the flow group level.

[0235] Similarly, when the second flow belongs to the first flow group, optionally, each flow in the first flow group can have its own corresponding value. The values ​​corresponding to different flows can be the same or different. The second value indicated by the fourth information is indicated at the flow level. Optionally, the fourth information can also indicate the values ​​corresponding to one or more other flows in the first flow group. For example, the fourth information can indicate the value corresponding to each flow in the first flow group. Alternatively, the first flow group can correspond to a single value, which is the second value. The fourth information can indicate the second value corresponding to the first flow group. That is, the second value indicated by the fourth information is indicated at the flow group level.

[0236] Optionally, before the first network element sends the first information to the terminal device, the terminal device may send information to the first network element requesting (or instructing) the establishment / modification of the first flow (this information may be referred to as the seventh information). For example, the seventh information may be a PDU session modification request (or, in other words, the seventh information may be carried in the PDU session modification request). The seventh information may carry identification information of the second flow, indicating that the terminal device expects the first flow to depend on the second flow. Alternatively, if the second flow belongs to a flow group, the seventh information may carry identification information of the flow group, indicating that the terminal device expects the first flow to depend on the flows included in the flow group. Alternatively, the seventh information may carry a value indicating that the terminal device expects the first flow to correspond to this value; this value may be the same as or different from the first value.

[0237] Alternatively, if the terminal device sends seventh information to the first network element before the first network element sends first information to the terminal device, the first information sent by the first network element to the terminal device can indicate that the established / modified first flow satisfies the request / instruction of the seventh information (or, the first information can indicate that the first network element agrees to the request / instruction of the seventh information). In this optional scheme, the first information can indicate the first dependency relationship by indicating that the established / modified first flow satisfies the request / instruction of the seventh information, without needing to carry the identification information of the second flow, the identification information of the first flow group, or the first value corresponding to the first flow. Alternatively, the first information can both indicate that the established / modified first flow satisfies the request / instruction of the seventh information and carry the identification information of the second flow, the identification information of the first flow group, or the first value corresponding to the first flow.

[0238] This application does not limit the specific implementation of the first information indicating that the established / modified first flow meets the request / instruction of the seventh information. Optionally, after the terminal device sends the seventh information, if the first information sent by the first network element includes an acknowledgment character (ACK), it means that the first information indicates that the established / modified first flow meets the request / instruction of the seventh information. Optionally, if the first information sent by the first network element does not include an acknowledgment (ACK) or includes a negative-acknowledgment (NACK), it means that the established / modified first flow does not meet the request / instruction of the seventh information.

[0239] In this embodiment of the application, ACK and NACK are merely ways to indicate a positive or negative response to the request content. Other methods, such as Accept, Flag=True, can also be used to express a positive response, and Reject, Flag=False, etc., to express a negative response. These will not be elaborated further here.

[0240] For example, if the seventh information carries the identification information of the second flow, indicating that the terminal device expects the first flow to depend on the second flow, and the first information sent by the first network element includes an ACK, it is used to indicate that the established / modified first flow depends on the second flow. Alternatively, if the second flow belongs to a flow group, and the seventh information carries the identification information of the flow group, indicating that the terminal device expects the first flow to depend on the flows included in the flow group, and the first information sent by the first network element includes an ACK, it is used to indicate that the established / modified first flow depends on the flows included in the flow group. Or, if the seventh information carries a value, indicating that the terminal device expects the first flow to correspond to that value, and the first information sent by the first network element includes an ACK, it is used to indicate that the value corresponding to the established / modified first flow is the value carried in the seventh information.

[0241] The above describes possible implementations of the first information indicating the first dependency relationship. Optionally, if other flows exist, such as a third flow, a second dependency relationship may exist between the first flow and the third flow, and a third dependency relationship may also exist between the second flow and the third flow. This application does not limit the second and third dependencies. For example, a second dependency relationship may include: the first flow depends on the third flow, and a third dependency relationship may include: the second flow and the third flow depend on each other.

[0242] Optionally, the third flow can belong to a flow group. For example, the third flow and the second flow can belong to the first flow group.

[0243] Optionally, the first information may also indicate a second dependency. The first network element may also indicate a third dependency to the terminal device. This application embodiment does not limit the specific implementation of the first information indicating the second dependency and the first network element indicating the third dependency to the terminal device.

[0244] Optionally, if the second dependency relationship is that the first flow depends on the third flow, the first information may include the identification information of the third flow. Alternatively, if the third flow belongs to a flow group, the first information may include the identification information of the flow group. Alternatively, the first network element may send information indicating a third value corresponding to the third flow (this information indicating the third value may be called fifth information) to the terminal device, and the magnitude relationship between the third value and the first value indicated by the first information is used to indicate the second dependency relationship. For specific implementation details, please refer to the above descriptions of implementation methods one, two, and three for the first information indicating the first dependency relationship.

[0245] Optionally, if the third dependency relationship is that the second flow depends on the third flow, or the third flow depends on the second flow, the specific implementation of the first network element indicating the third dependency relationship to the terminal device can refer to the above introduction on the implementation of the first information indicating the first dependency relationship.

[0246] Optionally, the following uses the example of a third dependency relationship between the second and third flows to introduce several possible implementations of how the first network element indicates the third dependency relationship to the terminal device.

[0247] Implementation Method 4: The first network element sends second information to the terminal device, indicating that the third flow depends on the second flow. The terminal device receives the second information. The first network element then sends third information to the terminal device, indicating that the second flow depends on the third flow. The terminal device receives the third information. After receiving the second and third information, the terminal device can determine the mutual dependency between the second and third flows based on them. In this embodiment, the timing of the transmission of the second and third information in Implementation Method 4 is not limited; the second information can be sent before, after, or simultaneously with the third information.

[0248] Furthermore, after determining the second and third information, the first network element can also determine the mutual dependency between the second and third flows based on the fact that the third flow depends on the second flow, and the second flow depends on the third flow. Optionally, the first network element can assign the second and third flows to the same flow group, such as the first flow group, based on the mutual dependency between them, and send the flow group identification information to the terminal device. Optionally, the flow group identification information sent by the first network element can be carried in a message used to establish / modify the second flow, or in a message used to establish / modify the third flow, or in other messages, such as in a newly defined message. This application embodiment does not limit this.

[0249] Optionally, in implementation method four, the second information may include the identification information of the second stream, such as the ID of the second stream. The terminal device can determine that the third stream depends on the second stream corresponding to the identification information based on the identification information of the third stream in the second information. The third information may include the identification information of the third stream. The terminal device can determine that the second stream depends on the third stream corresponding to the identification information based on the identification information of the third stream in the third information.

[0250] Optionally, the second information can be carried in a message used to establish / modify a third stream (or, the second information can be used to establish / modify a third stream), for example, the second information can be carried in a PDU session modification command message. Alternatively, if the third stream belongs to a stream group, the second information can be carried in a message used to establish / modify a stream group (or, the second information can be used to establish / modify a first stream group). Alternatively, the second information can be carried in other messages, for example, the second information can be carried in a newly defined message used to indicate dependencies; this embodiment of the application does not limit this. Similarly, the third information can be carried in a message used to establish / modify a second stream, or, if the second stream belongs to a stream group, the third information can be carried in a message used to establish / modify a stream group, or the third information can be carried in other messages; this embodiment of the application does not limit this.

[0251] Optionally, the second / third information can be newly defined information cells used to indicate a dependency relationship between different flows. For details, please refer to the above description of implementation method one where the first information indicates the first dependency relationship.

[0252] Implementation Method 5: The first network element sends fourth information to the terminal device, indicating the second value corresponding to the second flow. The terminal device then receives the fourth information. The first network element also sends fifth information to the terminal device, indicating the third value corresponding to the third flow. The terminal device can determine the interdependence between the second and third flows based on the fact that the second and third values ​​are the same; that is, the same second and third values ​​indicate an interdependence between the second and third flows.

[0253] This application does not limit the timing of sending the fourth and fifth information. The fourth information can be sent before the fifth information, after the fifth information, or at the same time.

[0254] The specific implementation of the fourth and fifth information can be found in the above description of the third method for implementing the first information to indicate the first dependency relationship, and will not be elaborated here.

[0255] Optionally, in one possible case, the second and third flows may belong to the same flow group, such as the first flow group. In this case, the fourth and fifth information can be the same information. Optionally, the fourth information (or fifth information) can indicate the value corresponding to the first flow group at the flow group level (i.e., the value corresponding to the first flow group can be called either the second or the third value). Alternatively, the fourth information (or fifth information) can indicate the second value corresponding to the second flow and the third value corresponding to the third flow at the flow level.

[0256] Optionally, before the first network element sends the second information to the terminal device, the terminal device may send information to the first network element requesting (or instructing) the establishment / modification of a third flow. This information may carry identification information of the second flow, indicating that the terminal device expects the third flow to depend on the second flow. Alternatively, if the second flow belongs to the first flow group, this information may carry identification information of the first flow group, indicating that the terminal device expects the third flow to depend on flows included in the first flow group. See the above description of the seventh information for details.

[0257] Alternatively, if the terminal device sends a request (or instruction) to the first network element to establish / modify a third flow before the first network element sends the second information to the terminal device, the second information sent by the first network element to the terminal device can instruct the established / modified third flow to satisfy the request / instruction of the information (or, in other words, the third information can instruct the first network element to agree to the request / instruction of the information). In this optional scheme, the second information can indicate that the established / modified third flow satisfies the request / instruction of the information sent by the terminal device, indicating that the third flow depends on the second flow, without necessarily carrying the identification information of the second flow or the identification information of the first flow group. Alternatively, the second information can both instruct the established / modified third flow to satisfy the request / instruction and carry the identification information of the second flow or the identification information of the first flow group. For details, please refer to the above description of the first information instructing the established / modified first flow to satisfy the request / instruction of the seventh information to indicate the first dependency relationship.

[0258] Similarly, optionally, before the first network element sends the third information to the terminal device, the terminal device may send information to the first network element requesting (or instructing) the establishment / modification of a second flow. This information may carry the identification information of the third flow, indicating that the terminal device expects the second flow to depend on the third flow. Alternatively, if the third flow belongs to the first flow group, this information may carry the identification information of the first flow group, indicating that the terminal device expects the second flow to depend on the flows included in the first flow group. Additionally, optionally, if the terminal device sends information requesting (or instructing) the establishment / modification of a second flow to the first network element before sending the third information, the third information sent by the first network element to the terminal device may instruct the established / modified second flow to satisfy the request / instruction of this information (or, in other words, the second information may instruct the first network element to agree to the request / instruction of this information). The third information may indicate that the established / modified second flow satisfies the request / instruction of this information, indicating that the second flow depends on the third flow. For details, refer to the above description of the first information instructing the established / modified first flow to satisfy the request / instruction of the seventh information to indicate the first dependency relationship.

[0259] Optionally, before the first network element sends the fourth information to the terminal device, the terminal device may send information to the first network element requesting (or instructing) the establishment / modification of the second flow. This information may carry a value indicating that the terminal device expects the second flow to correspond to that value. See the description of the seventh information above for details.

[0260] Alternatively, if the terminal device sends a request (or indication) to the first network element to establish / modify a second flow before the first network element sends the fourth information to the terminal device, and this information carries the value that the terminal device expects the second flow to correspond to, the fourth information sent by the first network element to the terminal device can instruct the established / modified third flow to satisfy the request / instruction of this information, that is, to indicate that the value corresponding to the third flow is the value expected by the terminal device. In this alternative scheme, the fourth information does not necessarily need to carry the value corresponding to the second flow, or the fourth information can both instruct the established / modified third flow to satisfy the request / instruction of the terminal device and carry the value corresponding to the second flow. For details, please refer to the above description of the first information instructing the established / modified first flow to satisfy the request / instruction of the seventh information to indicate the first dependency relationship.

[0261] Similarly, optionally, before the first network element sends the fifth information to the terminal device, the terminal device may send information to the first network element requesting (or instructing) the establishment / modification of a third flow. This information may carry a value indicating that the terminal device expects the third flow to correspond to that value. Alternatively, if the terminal device sends information requesting (or instructing) the establishment / modification of a third flow to the first network element before sending the fifth information, and this information carries the value that the terminal device expects the third flow to correspond to, the fifth information sent by the first network element to the terminal device may instruct the established / modified third flow to satisfy the request / instruction of this information, that is, to indicate that the value corresponding to the third flow is the value expected by the terminal device. For details, refer to the above description of the first information instructing the establishment / modification of the first flow to satisfy the request / instruction of the seventh information to indicate the first dependency relationship.

[0262] Additionally, embodiments of this application also provide a method for establishing a stream group comprising multiple streams using a single message. The method includes:

[0263] The first network element sends the sixth information to the terminal device, which is used to establish a flow group. Correspondingly, the terminal device receives the sixth information.

[0264] Optionally, the sixth information can be carried in an existing message, for example, in a PDU session modification command. Alternatively, the sixth information can be carried in a newly defined message; this embodiment of the application does not limit this.

[0265] Optionally, the sixth piece of information may include parameters corresponding to each flow in the flow group, such as QoS rule and QoS flow description.

[0266] Optionally, the sixth information may include the identification information assigned to the flow group by the first network element.

[0267] Optionally, before the first network element sends the sixth information, the terminal device may send a request (or instruction) to the first network element to establish a flow group (this information may be referred to as the eighth information). The eighth information may trigger the first network element to establish a flow group and send the sixth information to the terminal device.

[0268] Optionally, the eighth information may include parameters that the terminal device expects for each flow in the flow group, such as QoS rule and QoS flow description.

[0269] Optionally, the sixth or eighth information may indicate the number of flows included in the flow group. This application embodiment does not limit the manner in which the sixth or eighth information indicates the number of flows. For example, the sixth information may include identification information for each flow included in the flow group, such as a QoS flow ID; the number of flow identification information can indicate the number of flows. As another example, the eighth information may indicate that a flow in the flow group has not been assigned identification information, such as the field "no QoS flow identifier assigned"; the number of flows included in the flow group can be indicated by the number of flows without assigned identifiers indicated by the eighth information. As another example, the sixth or eighth information may include packet filter (e.g., IP 5-tuple) parameters corresponding to the flow; the number of packet filter parameters included in the sixth or eighth information can indicate the number of flows. As yet another example, the sixth or eighth information may include a newly defined field whose value is the number of flows included in the flow group.

[0270] Optionally, the sixth or eighth message can be a newly defined information element that indicates the establishment of a stream group. For example, the sixth or eighth message may include a new operation code: create a new group.

[0271] Optionally, the above embodiment of establishing a flow group through the sixth information can be combined with the method embodiment shown in FIG5.

[0272] In the combined embodiment, there are dependencies between the multiple flows included in the flow group established by the sixth information. The following uses the example of the sixth information establishing a first flow group, which includes a second and a third flow group, to illustrate the dependencies between the multiple flows included in the first flow group.

[0273] In one possible implementation, the multiple flows included in the first flow group can be interdependent. In this implementation, the terminal device and the first network element can default to each other (e.g., pre-agreed upon by the terminal device and the first network element, or, for example, predefined by the protocol), and the multiple flows included in the flow group can be interdependent.

[0274] Optionally, in this implementation, the sixth information may include the value corresponding to the first flow group. The magnitude relationship between the value corresponding to the first flow group and the values ​​corresponding to other flows / flow groups can indicate the dependency relationship between the flows in the first flow group and the flows in other flows / flow groups. For details, please refer to the description of the values ​​corresponding to the flows / flow groups in the method embodiment shown in Figure 5 above.

[0275] In another possible implementation, the sixth information may include the value corresponding to each flow in the first flow group, and the size relationship between the values ​​corresponding to each flow, which is used to indicate the dependency relationship between the multiple flows included in the first flow group. For details, please refer to the above description of the values ​​corresponding to the flow / flow group in the method embodiment shown in Figure 5.

[0276] Optionally, in the combined embodiment, the first information may indicate a first dependency between the first stream and the second stream in any of the following ways:

[0277] (1) The first information includes the identification information of the second stream. The first information can indicate a first dependency relationship between the first stream and the second stream corresponding to the identification information through the identification information of the second stream.

[0278] (2) The first information includes the identification information of the first flow group. The first information can indicate, through the identification information of the first flow group, that there is a first dependency relationship between the first flow and each flow in the first flow group corresponding to the identification information.

[0279] (3) The sixth information includes the value corresponding to each flow in the first flow group. The first information includes the first value corresponding to the first flow and the size relationship between the first value and the value corresponding to each flow in the first flow group, which is used to indicate the dependency relationship between the first flow and each flow. Among them, the size relationship between the first value and the value corresponding to the second flow is used to indicate the first dependency relationship between the first flow and the second flow.

[0280] (4) The sixth information includes the value corresponding to the first flow group, and the first information includes the first value corresponding to the first flow, the value corresponding to the first flow group, and the size relationship between the first value and the first value, which are used to indicate the dependency relationship between the first flow and the multiple flows included in the first flow group. It can be understood that in this method, there is a first dependency relationship between the first flow and each flow in the first flow group.

[0281] Optionally, the above methods (1)-(4) can be applied to scenarios where the first information is used to establish / modify the first-class.

[0282] For details of the above methods (1)-(4), please refer to the above description of the implementation method of the first information indicating the first dependency relationship in the embodiment shown in Figure 5.

[0283] Optionally, in the combined embodiment, the first flow may belong to another flow group different from the first flow group, such as the second flow group. In this case, the first information can be used to establish the second flow group, where the flows included in the second flow group have dependencies on the flows included in the first flow group, and the second flow group includes the first flow. For a specific implementation of using the first information to establish the second flow group, please refer to the above description of using the sixth information to establish the flow group.

[0284] Optionally, before the first network element sends the first information to the terminal device, the terminal device may send a request (or instruction) to the first network element to establish a second flow group (this information may be referred to as the ninth information). The ninth information can trigger the first network element to establish the second flow group and send the first information to the terminal device. For details on the ninth information, please refer to the description of the eighth information above.

[0285] Optionally, when the first information is used to establish the second flow group, the first information may indicate the first dependency between the first flow and the second flow in any of the following ways:

[0286] (5) The first information includes the identification information of the second flow. The first information can indicate, through the identification information of the second flow, that there is a first dependency relationship between the flow in the second flow group and the second flow corresponding to the identification information.

[0287] (6) The first information includes the identification information of the first flow group. The first information can indicate, through the identification information of the first flow group, that there is a first dependency relationship between each flow in the second flow group and each flow in the first flow group corresponding to the identification information.

[0288] (7) The sixth information includes the value corresponding to each flow in the first flow group, the first information includes the value corresponding to each flow in the second flow group, the value corresponding to each flow in the second flow group, and the size relationship between the value corresponding to each flow in the second flow group and the value corresponding to each flow in the first flow group, which is used to indicate the dependency relationship between each flow included in the second flow group and each flow included in the first flow group.

[0289] (8) The sixth information includes the value corresponding to the first flow group, the first information includes the value corresponding to the second flow group, the value corresponding to the first flow group, and the size relationship between the value corresponding to the second flow group and the value corresponding to the second flow group, which is used to indicate the dependency relationship between the multiple flows included in the second flow group and the multiple flows included in the first flow group.

[0290] For details of the above methods (5)-(8), please refer to the above description of the implementation method of the first information indicating the first dependency relationship in the embodiment shown in Figure 5.

[0291] Alternatively, the sixth information may indicate the dependencies between flows in the first flow group and other flows / flow groups. For example, the sixth information may include identification information of other flows to indicate a dependency between each flow in the first flow group and the flow corresponding to the identification information. Or, for example, the sixth information may include identification information of other flow groups to indicate a dependency between each flow in the first flow group and each flow in the flow group corresponding to the identification information. Or, for example, the sixth information may include the value corresponding to each flow in the first flow group, or the value corresponding to the first flow group, and the relationship between the value corresponding to each flow in the first flow group and the values ​​corresponding to other flows, which can indicate the dependencies between each flow in the first flow group and other flows. The relationship between the value corresponding to the first flow group and the values ​​corresponding to other flow groups can indicate the dependencies between multiple flows in the first flow group and multiple flows in other flow groups.

[0292] Optionally, the dependency indicated by the sixth information can be "the flow in the first flow group depends on other flows / flow groups", or "the flow in the first flow group is depended on by other flows / flow groups", or "the flow in the first flow group depends on other flows / flow groups".

[0293] The following assumes that the first network element is an SMF network element, the first flow is QoS flow3, the second flow is QoS flow1, the third flow is QoS flow2, the first flow depends on the second flow, the first flow depends on the third flow, and the second flow and the third flow depend on each other. Several exemplary processes of the embodiments of this application will be introduced.

[0294] Figure 6 is a schematic diagram of an exemplary process provided in an embodiment of this application. As shown in Figure 6, the process includes the following steps:

[0295] S601 (Optional step): The terminal device sends a PDU session modification request to the SMF network element through the RAN node to request the establishment of QoS flow1.

[0296] The S602 and SMF network elements send a PDU session modification command to the terminal device, carrying the QoS rule and QoS flow description corresponding to QoS flow1.

[0297] S603 (Optional Step): The terminal device sends a PDU session modification request to the SMF network element through the RAN node, requesting the establishment of QoS flow2. This PDU session modification request includes a new information element, which includes the identifier of QoS flow1, indicating that QoS flow2 is expected to depend on QoS flow1.

[0298] The S604 and SMF network elements send a PDU session modification command to the terminal device, carrying the QoS rule and QoS flow description corresponding to QoS flow2.

[0299] Optionally, the PDU session modification command may include a new information element, which includes an identifier of QoS flow1, indicating that QoS flow2 depends on QoS flow1.

[0300] Optionally, if the process shown in Figure 6 includes S603, the PDU session modification command sent by the SMF network element in S604 may include ACK, indicating that QoS flow2 depends on QoS flow1.

[0301] S605 (Optional Step): The terminal device sends a PDU session modification request to the SMF network element through the RAN node, requesting modification of QoS flow1. This PDU session modification request includes a new information element, which includes an identifier for QoS flow2, indicating that QoS flow1 is expected to depend on QoS flow2.

[0302] The S606 and SMF network elements send a PDU session modification command to the terminal device, carrying the QoS rule corresponding to the modified QoS flow1.

[0303] Optionally, the PDU session modification command includes a new information element that includes an identifier for QoS flow2, indicating that the modified QoS flow1 depends on QoS flow2.

[0304] Optionally, the SMF network element can determine that QoS flow1 and QoS flow2 are interdependent based on the fact that QoS flow1 depends on QoS flow2, and QoS flow2 depends on QoS flow1. It can then assign QoS flow1 and QoS flow2 to the same flow group, such as the first flow group, and allocate identification information to this flow group. Optionally, the SMF network element can carry the flow group identification information in the PDU session modification command in S606.

[0305] Optionally, if the PDU session modification command in S606 carries flow group identification information, the PDU session modification command may not include new information cells indicating that QoS flow1 depends on QoS flow2. After receiving the PDU session modification command, the terminal device can determine, based on the flow group identification information, that QoS flow1 and QoS flow2 belong to the flow group corresponding to that identification information, and that QoS flow1 and QoS flow2 are interdependent. For example, the SMF network element and the terminal device may pre-agree, or the protocol may pre-define, that multiple QoS flows included in the same flow group are interdependent.

[0306] Optionally, if the process shown in Figure 6 includes S605, the PDU session modification command sent by the SMF network element in S606 may include ACK, indicating that QoS flow1 depends on QoS flow2.

[0307] S607 (Optional Step): The terminal device sends a PDU session modification request to the SMF network element through the RAN node, requesting the establishment of QoS flow3. This PDU session modification request includes a new information element, which includes identifiers for QoS flow1 and QoS flow2, indicating that QoS flow3 is expected to depend on QoS flow1 and QoS flow2. Alternatively, if the PDU session modification command in S606 carries flow group identification information, this new information element may include the flow group identification information, indicating that QoS flow3 is expected to depend on the QoS flow in the flow group corresponding to this identification information.

[0308] The S608 and SMF network elements send a PDU session modification command to the terminal device, carrying the QoS rule and QoS flow description corresponding to QoS flow3.

[0309] Optionally, the PDU session modification command includes a new information element, which includes identifiers for QoS flow1 and QoS flow2, indicating that QoS flow3 depends on QoS flow1 and QoS flow2. Alternatively, if the PDU session modification command in S606 carries flow group identification information, the new information element may include the flow group identification information, indicating that QoS flow3 depends on the QoS flow in the flow group corresponding to the identification information.

[0310] Optionally, if the process shown in Figure 6 includes S607, the PDU session modification command sent by the SMF network element in S608 may include ACK, indicating that QoS flow3 depends on QoS flow1 and QoS flow2, or indicating that QoS flow3 depends on the QoS flow in the flow group corresponding to the identification information.

[0311] Figure 7 is a schematic diagram of another exemplary process provided in an embodiment of this application. As shown in Figure 7, the process includes the following steps:

[0312] S701 (Optional Step): The terminal device sends a PDU session modification request to the SMF network element through the RAN node, requesting the establishment of QoS flow1. This PDU session modification request includes a new information element, which includes the value X corresponding to QoS flow1.

[0313] The S702 and SMF network elements send a PDU session modification command to the terminal device, carrying the QoS rule and QoS flow description corresponding to QoS flow1.

[0314] Optionally, the PDU session modification command includes a new information element, which includes the value corresponding to QoS flow1: X.

[0315] Optionally, if the process shown in Figure 7 includes S701, the PDU session modification command sent by the SMF network element in S702 may include ACK, indicating that the value corresponding to QoS flow1 is X.

[0316] S703 (Optional Step): The terminal device sends a PDU session modification request to the SMF network element through the RAN node, requesting the establishment of QoS flow2. This PDU session modification request includes a new information element, which includes the value X corresponding to QoS flow2. The values ​​corresponding to QoS flow1 and QoS flow2 are the same, indicating that the terminal device expects QoS flow1 and QoS flow2 to be interdependent.

[0317] The S704 and SMF network elements send a PDU session modification command to the terminal device, carrying the QoS rule and QoS flow description corresponding to QoS flow2.

[0318] Optionally, the PDU session modification command includes a new information element, which includes the value X corresponding to QoS flow2. The value corresponding to QoS flow1 is the same as the value corresponding to QoS flow2, indicating that QoS flow1 and QoS flow2 are interdependent.

[0319] Optionally, if the process shown in Figure 7 includes S703, the PDU session modification command sent by the SMF network element in S704 may include ACK, indicating that the value corresponding to QoS flow2 is X.

[0320] S705 (Optional Step): The terminal device sends a PDU session modification request to the SMF network element through the RAN node, requesting the establishment of QoS flow3. This PDU session modification request includes a new information element, which includes the value Y corresponding to QoS flow3. The relationship between the values ​​of QoS flow1, QoS flow2, and QoS flow3 indicates to the terminal device that it expects QoS flow3 to depend on QoS flow1 and QoS flow2.

[0321] The S706 and SMF network elements send a PDU session modification command to the terminal device, carrying the QoS rule and QoS flow description corresponding to QoS flow3.

[0322] Optionally, the PDU session modification command includes a new information element, which includes the value Y corresponding to QoS flow3. The magnitude relationship between the values ​​corresponding to QoS flow1, QoS flow2, and QoS flow3 can indicate that QoS flow3 depends on QoS flow1 and QoS flow2.

[0323] Optionally, if the process shown in Figure 7 includes S705, the PDU session modification command sent by the SMF network element in S706 may include ACK, indicating that the value corresponding to QoS flow3 is Y.

[0324] Figure 8 is a schematic diagram of another exemplary process provided in an embodiment of this application. As shown in Figure 8, the process includes the following steps:

[0325] S801 (Optional Step): The terminal device sends a PDU session modification request to the SMF network element through the RAN node to request the establishment of a first flow group. Optionally, the number of "no QoS flow identifier assigned" in the PDU session modification request can indicate the number of QoS flows that the terminal device expects the first flow group to include.

[0326] The S802 and SMF network elements send a PDU session modification command to the terminal device, carrying the QoS rule and QoS flow description corresponding to each QoS flow in the first flow group. The first flow group includes QoS flow1 and QoS flow2.

[0327] In S802, the PDU session modification command sent by the SMF network element includes the identification information of the first flow group, and / or the identification information of each QoS flow included in the first flow group.

[0328] By default, terminal devices and SMF network elements can establish interdependence among multiple QoS flows within the same flow group. That is, QoS flow1 and QoS flow2 within the first flow group are interdependent.

[0329] S803a (Optional Step): The terminal device sends a PDU session modification request to the SMF network element through the RAN node, requesting the establishment of QoS flow3. This PDU session modification request includes a new information element, which includes identification information of the first flow group, indicating that the terminal device expects QoS flow3 to depend on each flow in the first flow group. Alternatively, the information element includes identification information of QoS flow1 and QoS flow2, indicating that the terminal device expects QoS flow3 to depend on both QoS flow1 and QoS flow2.

[0330] The S804a and SMF network elements send a PDU session modification command to the terminal device, carrying the QoS rule and QoS flow description corresponding to QoS flow3.

[0331] Optionally, the PDU session modification command includes a new information element, which includes identification information of a first flow group, indicating that QoS flow3 depends on each flow in the first flow group; or, the information element includes identification information of QoS flow1 and QoS flow2, indicating that QoS flow3 depends on QoS flow1 and QoS flow2.

[0332] Optionally, if the process shown in Figure 8 includes S803a, the PDU session modification command sent by the SMF network element in S804a may include ACK, indicating that QoS flow3 depends on each flow in the first flow group, or indicating that QoS flow3 depends on QoS flow1 and QoS flow2.

[0333] Alternatively, S803a-S804a can also be replaced with: S803b-S804b:

[0334] S803b (Optional Step): The terminal device sends a PDU session modification request to the SMF network element through the RAN node, requesting the establishment of a second flow group. This PDU session modification request includes a new information element, which includes the identification information of the first flow group, indicating that the terminal device expects flows in the second flow group to depend on flows in the first flow group. Alternatively, this information element includes the identification information of QoS flow1 and QoS flow2, indicating that the terminal device expects flows in the second flow group to depend on QoS flow1 and QoS flow2.

[0335] The S804b and SMF network elements send a PDU session modification command to the terminal device, carrying the QoS rule and QoS flow description corresponding to each flow in the second flow group. The second flow group includes QoS flow3 and at least one other flow, such as QoS flow4. QoS flow3 and QoS flow4 are interdependent.

[0336] Optionally, in S804b, the PDU session modification command sent by the SMF network element includes a new information element. This information element includes the identification information of the first flow group, indicating that the flow in the second flow group depends on the flow in the first flow group. Alternatively, this information element includes the identification information of QoS flow1 and the identification information of QoS flow2, indicating that the flow in the second flow group depends on QoS flow1 and QoS flow2.

[0337] Optionally, if the process shown in Figure 8 includes S803b, the PDU session modification command sent by the SMF network element in S804b may include ACK, indicating that the flow in the second flow group depends on the flow in the first flow group, or indicating that the flow in the second flow group depends on QoS flow1 and QoS flow2.

[0338] Figure 9 is a schematic diagram of another exemplary process provided in an embodiment of this application. As shown in Figure 9, the process includes the following steps:

[0339] S901 (Optional Step): The terminal device sends a PDU session modification request to the SMF network element through the RAN node to request the establishment of a first flow group. This PDU session modification request includes a new information element, which includes the value X corresponding to the first flow group.

[0340] The S902 and SMF network elements send a PDU session modification command to the terminal device, carrying the QoS rule and QoS flow description corresponding to each QoS flow in the first flow group. The first flow group includes QoS flow1 and QoS flow2.

[0341] In S902, the PDU session modification command sent by the SMF network element includes the identification information of the first flow group, and / or the identification information of each QoS flow included in the first flow group.

[0342] Optionally, in S902, the PDU session modification command sent by the SMF network element includes a new information element, which includes the value corresponding to the first flow group: X.

[0343] Optionally, if the process shown in Figure 9 includes S901, the PDU session modification command sent by the SMF network element in S902 may include ACK, indicating that the value corresponding to the first flow group is X.

[0344] In this context, it is permissible by default that multiple QoS flows within the same flow group are interdependent with each other, between the terminal device and the SMF network element. That is, QoS flow1 and QoS flow2 within the first flow group are interdependent with each other.

[0345] S903a (Optional Step): The terminal device sends a PDU session modification request to the SMF network element through the RAN node, requesting the establishment of QoS flow3. This PDU session modification request includes a new information element, which includes the value corresponding to QoS flow3: Y, and the magnitude relationship between the value of QoS flow3 and the value corresponding to the first flow group, indicating that the terminal device expects QoS flow3 to depend on each flow in the first flow group.

[0346] The S904a and SMF network elements send a PDU session modification command to the terminal device, carrying the QoS rule and QoS flow description corresponding to QoS flow3.

[0347] Optionally, the PDU session modification command includes a new information element, which includes the value corresponding to QoS flow3: Y, the magnitude relationship between the value corresponding to QoS flow3 and the value corresponding to the first flow group, indicating that QoS flow3 depends on each flow in the first flow group.

[0348] Optionally, if the process shown in Figure 9 includes S903a, the PDU session modification command sent by the SMF network element in S904a may include ACK, indicating that the value corresponding to QoS flow3 is Y.

[0349] Alternatively, S903a-S904a can also be replaced with: S903b-S904b:

[0350] S903b (Optional Step): The terminal device sends a PDU session modification request to the SMF network element through the RAN node, requesting the establishment of a second flow group. This PDU session modification request includes a new information element, which includes the value corresponding to the second flow group: Y. The relationship between the values ​​corresponding to the first and second flow groups indicates that the terminal device expects the flows in the second flow group to depend on the flows in the first flow group.

[0351] The S904b and SMF network elements send a PDU session modification command to the terminal device, carrying the QoS rule and QoS flow description corresponding to each flow in the second flow group. The second flow group includes QoS flow3 and at least one other flow, such as QoS flow4. QoS flow3 and QoS flow4 are interdependent.

[0352] Optionally, in S904b, the PDU session modification command sent by the SMF network element includes a new information element, which includes the value corresponding to the second flow group: Y. The relationship between the values ​​corresponding to the first flow group and the values ​​corresponding to the second flow group indicates that the flow in the second flow group depends on the flow in the first flow group.

[0353] Optionally, if the process shown in Figure 9 includes S903b, the PDU session modification command sent by the SMF network element in S904b may include ACK, indicating that the value corresponding to the second flow group is Y.

[0354] Alternatively, the first network element may send tenth information to the RAN node, which may indicate dependencies between different flows. For example, the tenth information may indicate a first dependency.

[0355] Optionally, the tenth piece of information can correspond to a flow, for example, it can be a newly added parameter of the flow. For example, if the flow is a QoS flow, the tenth piece of information can be a newly added parameter in the QoS parameters of the QoS flow level.

[0356] This application does not limit the specific implementation of the tenth information indicating the dependency relationship. The following uses the tenth information corresponding to the first flow as an example to introduce several possible implementations.

[0357] In one possible implementation, the RAN node can assume that multiple flows in a flow group are interdependent, for example, through pre-agreed agreements between the RAN node and the first network element, or through protocol pre-definition. The tenth information corresponding to the first flow can include the identifier information of the flow group to which the first flow belongs. Based on the tenth information corresponding to the first flow and the tenth information corresponding to other flows, the RAN node can determine which flows are included in the flow group, thereby determining the interdependencies between these flows.

[0358] In another possible implementation, the tenth information corresponding to the first stream may include identification information of other streams / stream groups, indicating a dependency between the first stream and the streams in the other streams / stream groups corresponding to the identification information. For example, the tenth information may indicate that the first stream depends on the stream corresponding to the identification information. As another example, the tenth information may indicate that the first stream depends on each stream in the stream group corresponding to the identification information.

[0359] In another possible implementation, the tenth information corresponding to the first stream may include the value corresponding to the first stream. The tenth information corresponding to other streams may include the values ​​corresponding to the other streams. The magnitude relationship between the value corresponding to the first stream and the values ​​corresponding to other streams can indicate the dependency relationship between the first stream and other streams; for details, please refer to the above introduction on how the first information indicates the value corresponding to the first stream.

[0360] Optionally, the RAN node can configure the mapping relationship between flows and radio bearers based on the tenth information. For example, the RAN node can configure the mapping relationship between the flow's identifier information, the identifier information of the radio bearer corresponding to the flow, and the identifier information of other flows / flow groups that depend on the flow, based on the tenth information. As another example, the RAN node can configure the mapping relationship between the flow's identifier information, the identifier information of the radio bearer corresponding to the flow, and the identifier information of the flow group to which the flow belongs, based on the tenth information. As yet another example, the RAN node can configure the mapping relationship between the flow's identifier information, the identifier information of the radio bearer corresponding to the flow, and the value corresponding to the flow, based on the tenth information.

[0361] Optionally, the RAN node can manage flows and / or radio bearers based on the tenth information. For example, after a flow is released, the RAN node can determine whether the flow is dependent on flows in other flows / flow groups. If the flow is dependent on flows in other flows / flow groups, the RAN node can release the flows in those other flows / flow groups. As another example, after a radio bearer is released, the RAN node can determine whether the flows mapped to that radio bearer are dependent on flows in other flows / flow groups. If the flows mapped to that radio bearer are dependent on flows in other flows / flow groups, the RAN node can release the radio bearers mapped to those flows / flow groups. Optionally, the RAN node can release the radio bearers mapped to flows in other flows / flow groups if it determines that the radio bearers mapped to flows in other flows / flow groups only map flows in those other flows / flow groups.

[0362] For example, suppose the RAN node configures the mapping relationship between QoS flow and radio bearer as shown in Table 1 based on the tenth information:

[0363] Table 1

[0364] As shown in Table 1, QoS flow1 depends on QoS flow2, and QoS flow2 depends on QoS flow1, therefore QoS flow1 and QoS flow2 are mutually dependent. QoS flow3 depends on both QoS flow1 and QoS flow2. QoS flow1 is mapped to radio bearer 1, QoS flow2 is mapped to radio bearer 2, and QoS flow3 is mapped to radio bearer 3. After the RAN node releases QoS flow1 or radio bearer 1, based on the mapping relationship, it determines that QoS flow1 is dependent on QoS flow2 and QoS flow3, and the RAN node can then release QoS flow2 and QoS flow3. Furthermore, if the RAN node also determines that only QoS flow2 is mapped on radio bearer 2, the RAN node can also release radio bearer 2; if it determines that only QoS flow3 is mapped on radio bearer 3, the RAN node can also release radio bearer 3.

[0365] Optionally, in the above embodiments, "the value corresponding to the stream" can also be replaced with other comparable information, such as "the priority corresponding to the stream". The difference in priority between different streams can indicate the dependency between different streams.

[0366] For example, a lower-priority stream can be defined to depend on a higher-priority stream. Alternatively, a higher-priority stream can depend on a lower-priority stream. Streams with the same priority depend on each other.

[0367] This application does not limit the representation of the priority of the flow in the embodiments. For example, priority can be represented by a numerical value, where a larger value indicates a lower priority, or vice versa. Another example is that priority can be represented by levels, such as three levels: low, medium, and high.

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

[0369] This application embodiment can divide the communication device into functional modules according to the above method embodiment. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be understood that the module division in this application embodiment is illustrative and is only a logical functional division. In actual implementation, there may be other division methods.

[0370] Figure 10 shows a schematic diagram of a communication device 1000. The communication device 1000 includes a transceiver module 1002 and a processing module 1001. Optionally, the communication device 1000 may also include a storage module 1003. The transceiver module 1002, also known as a transceiver unit, is used to implement transceiver functions, and may be, for example, a transceiver circuit, transceiver, transceiver device, or communication interface.

[0371] The communication device 1000 can be the first network element in the above embodiments, or it can be a chip within the first network element. Alternatively, the communication device can be the terminal device in the above embodiments, or it can be a chip within the terminal device. The communication device 1000 can be used to implement the communication method of any of the above embodiments.

[0372] For example, the transceiver module 1002 is used to support the communication device 1000 in sending and receiving information, or to communicate with other devices. The processing module 1001 is used to control and manage the operation of the communication device 1000, and to execute the processing performed by the communication device 1000 in the above embodiments. Optionally, if the communication device 1000 includes a storage module 1003, the processing module 1001 can also execute programs or instructions stored in the memory, so that the communication device 1000 implements the methods and functions involved in any of the above embodiments.

[0373] For example, if the communication device 1000 is the terminal device in the above embodiments, the transceiver module 1002 can be used to execute, for example, step S501 in FIG5, and / or other processes of the technology described herein. The processing module 1001 can be used to determine a first dependency relationship based on the first information, and / or other processes of the technology described herein. All relevant content of each step involved in the above method embodiments can be referenced to the functional description of the corresponding functional module, and will not be repeated here.

[0374] For example, if the communication device 1000 is the first network element in the above embodiments, the processing module 1001 can be used to determine the first information and / or for other processes of the technology described herein. The transceiver module 1002 can be used to execute, for example, step S501 in FIG5 and / or for other processes of the technology described herein. All relevant content of each step involved in the above method embodiments can be referenced to the functional description of the corresponding functional module, and will not be repeated here.

[0375] For example, in hardware implementation, the functions of processing module 1001 can be executed by a processor, and the functions of transceiver module 1002 can be executed by a transceiver (transmitter / receiver) and / or communication interface. The processing module 1001 can be embedded in or independent of the processor of communication device 1000 in hardware form, or it can be stored in the memory of communication device 1000 in software form, so that the processor can call and execute the operations corresponding to the above functional units.

[0376] Alternatively, the modules in Figure 10 can also be called units. For example, the processing module can be called a processing unit, and the transceiver module can be called a transceiver unit. Furthermore, in the embodiment shown in Figure 10, the names of the units may not be those shown in the figure; for example, the transceiver module can also be called a communication module or a communication unit.

[0377] If the units in Figure 10 are implemented as software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. This computer software product, stored in a storage medium, includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. Storage media for storing computer software products include various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0378] In this embodiment, the communication device 1000 is presented in an integrated manner, divided into various functional modules. Here, "module" can refer to a specific ASIC, circuit, processor and memory executing one or more software or firmware programs, integrated logic circuits, and / or other devices that can provide the aforementioned functions. In a simplified embodiment, those skilled in the art will recognize that the communication device 1000 can take the form of the communication device shown in FIG11.

[0379] As shown in FIG11, the communication device 1100 includes one or more processors 1101 (FIG11 is only an exemplary example illustrating the inclusion of one processor 1101). The processor 1101 can be used to execute instructions to enable the communication device 1100 to implement the methods described in the above-described method embodiments. For example, the processor 1101 can be used to determine the first information in S501. The processor 1101 can be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program according to the present application.

[0380] Optionally, the communication device 1100 may also include a communication line 1102. The communication line 1102 may include a path for connecting different components.

[0381] Optionally, the communication device 1100 may further include at least one communication interface (Figure 11 is merely exemplary, including communication interface 1104, and is described using this as an example). Communication interface 1104 may be a transceiver module for communicating with other devices or communication networks, such as Ethernet, RAN, terminals, wireless local area networks (WLANs), etc. For example, the transceiver module may be a transceiver or similar device. Optionally, the communication interface 1104 may also be a transceiver circuit or input / output interface located within the processor 1101, used to implement signal input and signal output for the processor.

[0382] Optionally, the communication device 1100 may further include a memory 1103. The memory 1103 may be a device with storage functionality. For example, it may be a read-only memory (ROM) or other types of static storage devices capable of storing static information and instructions; random access memory (RAM) or other types of dynamic storage devices capable of storing information and instructions; electrically erasable programmable read-only memory (EEPROM); compact disc read-only memory (CD-ROM) or other optical disc storage; optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.); magnetic disk storage media or other magnetic storage devices; or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory may exist independently and be connected to the processor via communication line 1102. Alternatively, the memory may be integrated with the processor.

[0383] The memory 1103 stores computer execution instructions for implementing the scheme of this application, and the processor 1101 controls the execution. The processor 1101 executes the computer execution instructions stored in the memory 1103, thereby implementing the communication method provided in the embodiments of this application.

[0384] Alternatively, in this embodiment, the processor 1101 may execute the processing-related functions in the communication method provided in this embodiment, and the communication interface 1104 may be responsible for communicating with other devices or communication networks. This embodiment does not specifically limit this.

[0385] Optionally, the computer execution instructions in the embodiments of this application may also be referred to as application code, and the embodiments of this application do not specifically limit this.

[0386] In a specific implementation, as one embodiment, processor 1101 may include one or more CPUs, such as CPU0 and CPU1 in FIG11.

[0387] In a specific implementation, as one embodiment, the communication device 1100 may include multiple processors, such as processors 1101 and 1107 in FIG. 11. Each of these processors may be a single-core processor or a multi-core processor. The processors here may include, but are not limited to, at least one of the following: a central processing unit (CPU), a microprocessor, a digital signal processor (DSP), a microcontroller unit (MCU), or an artificial intelligence processor, etc., and various computing devices that run software. Each computing device may include one or more cores for executing software instructions to perform calculations or processing.

[0388] In a specific implementation, as one embodiment, the communication device 1100 may further include an output device 1105 and an input device 1106. The output device 1105 communicates with the processor 1101 and can display information in various ways. For example, the output device 1105 may be a liquid crystal display (LCD), a light-emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector, etc. The input device 1106 communicates with the processor 1101 and can receive user input in various ways. For example, the input device 1106 may be a mouse, keyboard, touchscreen device, or sensing device, etc.

[0389] The aforementioned communication device 1100 may sometimes be referred to as a communication equipment, which can be a general-purpose device or a special-purpose device. For example, the communication device 1100 may be a desktop computer, a portable computer, a web server, a handheld computer (personal digital assistant, PDA), a mobile phone, a tablet computer, a wireless terminal device, an embedded device, or a device with a similar structure to that in Figure 11. The embodiments of this application do not limit the type of communication device 1100.

[0390] Furthermore, the composition shown in FIG11 does not constitute a limitation on the communication device. In addition to the components shown in FIG11, the communication device 1100 may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0391] In the communication device 1100 shown in Figure 11, the processor 1101 can call the computer execution instructions stored in the memory 1103 to make the communication device 1100 execute the communication method in the above method embodiment.

[0392] Specifically, the functions / implementation processes of the transceiver module 1002 and processing module 1001 in Figure 10 can be implemented by the processor 1101 in the communication device 1100 shown in Figure 11 calling computer execution instructions stored in the memory 1103. Alternatively, the functions / implementation processes of the processing module 1001 in Figure 10 can be implemented by the processor 1101 in the communication device 1100 shown in Figure 11 calling computer execution instructions stored in the memory 1103, and the functions / implementation processes of the transceiver module 1002 in Figure 10 can be implemented by the communication interface 1104 in the communication device 1100 shown in Figure 11.

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

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

[0395] Optionally, embodiments of this application also provide a communication device (e.g., the communication device may be a chip or a chip system), which includes a processor for implementing the methods in any of the above method embodiments. In one possible design, the communication device further includes a memory. The memory is used to store necessary program instructions and data, and the processor can call the program code stored in the memory to instruct the communication device to execute the methods in any of the above method embodiments. Of course, the memory may not be included in the communication device. When the communication device is a chip system, it may be composed of chips or may include chips and other discrete devices; embodiments of this application do not specifically limit this.

[0396] Optionally, embodiments of this application also provide a computer-readable storage medium storing a computer program or instructions that, when run on a communication device, enable the communication device to execute the methods described in any of the above method embodiments or any implementation thereof.

[0397] Optionally, embodiments of this application also provide a computer program product, which includes a computer program or instructions that, when run on a communication device, enable the communication device to execute the methods described in any of the above method embodiments or any implementation thereof.

[0398] Optionally, embodiments of this application also provide a communication system, which includes the first network element and the terminal device described in the above method embodiments.

[0399] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device containing one or more servers, data centers, etc., that can be integrated with the medium. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).

[0400] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, the disclosure, and the appended claims, will understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple instances. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.

[0401] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the scope of this application. Accordingly, this specification and drawings are merely exemplary illustrations of the application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from its scope. Thus, if such modifications and modifications fall within the scope of the claims and their equivalents, this application is also intended to include such modifications and modifications.

Claims

1. A communication method, characterized in that, The method includes: Receive first information, the first information being used to indicate a first dependency relationship between a first stream and a second stream, the first dependency relationship including: the first stream depends on the second stream.

2. The method according to claim 1, characterized in that, The first information is also used to indicate a second dependency relationship between the first stream and the third stream, the second dependency relationship including: the first stream depends on the third stream; wherein, there is a third dependency relationship between the second stream and the third stream, the third dependency relationship including: the second stream and the third stream depend on each other.

3. The method according to claim 2, characterized in that, The method further includes: Receive second information, which indicates that the third stream depends on the second stream; Receive third information, which indicates that the second stream depends on the third stream.

4. The method according to claim 3, characterized in that, The second information includes the identification information of the second stream, and the third information includes the identification information of the third stream.

5. The method according to any one of claims 2-4, characterized in that, The method further includes: Receive the identification information of a first flow group, wherein the multiple flows included in the first flow group are interdependent, and the first flow group includes the second flow and the third flow.

6. The method according to claim 5, characterized in that, The first information includes the identification information of the first flow group, and the first information is used to indicate the dependency relationship between the first flow and the flow in the first flow group.

7. The method according to any one of claims 1-5, characterized in that, The first information includes the identification information of the second stream.

8. The method according to claim 1 or 2, characterized in that, The first information is used to indicate a first value corresponding to the first stream, and the method further includes: Receive fourth information, which is used to indicate the second value corresponding to the second stream; the size relationship between the first value and the second value is used to indicate the first dependency relationship.

9. The method according to claim 8, characterized in that, The method further includes: Receive fifth information, the fifth information being used to indicate a third value corresponding to a third stream, the second value being the same as the third value; wherein, the magnitude relationship between the first value and the third value is used to indicate a second dependency relationship between the first stream and the third stream, the second dependency relationship including: the first stream depends on the third stream, the second value being the same as the third value, being used to indicate that the second stream and the third stream are mutually dependent.

10. The method according to claim 1 or 2, characterized in that, The method further includes: Receive sixth information, the sixth information being used to establish a first flow group, the first flow group including a second flow and a third flow, and the multiple flows included in the first flow group having dependencies on each other.

11. The method according to claim 10, characterized in that, The sixth information includes the value corresponding to each flow in the first flow group, and the size relationship between the values ​​corresponding to each flow, which is used to indicate the dependency relationship between the multiple flows included in the first flow group; or, The multiple flows included in the first flow group are interdependent.

12. The method according to claim 10 or 11, characterized in that, The first information includes the identification information of the second stream; or, The first information includes the identification information of the first stream group; or, The sixth information includes the value corresponding to each flow in the first flow group. The first information includes the first value corresponding to the first flow and the size relationship between the first value and the value corresponding to each flow, which is used to indicate the dependency relationship between the first flow and each flow. or, The sixth information includes the value corresponding to the first flow group, the first information includes the first value corresponding to the first flow, and the size relationship between the value corresponding to the first flow group and the first value, which is used to indicate the dependency relationship between the first flow and the multiple flows included in the first flow group.

13. The method according to claim 10 or 11, characterized in that, The first information is used to establish a second flow group, wherein the flow included in the second flow group has a dependency relationship with the flow included in the first flow group, and the second flow group includes the first flow.

14. The method according to claim 13, characterized in that, The first information includes the identification information of the first stream group; or, The sixth information includes the value corresponding to each flow in the first flow group, the first information includes the value corresponding to each flow in the second flow group, the value corresponding to each flow in the second flow group, and the size relationship between the value corresponding to each flow in the second flow group and the value corresponding to each flow in the first flow group, which is used to indicate the dependency relationship between each flow in the second flow group and each flow in the first flow group; or, The sixth information includes the value corresponding to the first flow group, the first information includes the value corresponding to the second flow group, the value corresponding to the first flow group and the value corresponding to the second flow group, and the size relationship between them, which is used to indicate the dependency relationship between the multiple flows included in the second flow group and the multiple flows included in the first flow group.

15. A communication method, characterized in that, The method includes: Send a first message, the first message being used to indicate a first dependency relationship between a first stream and a second stream, the first dependency relationship including: the first stream depends on the second stream.

16. The method according to claim 15, characterized in that, The first information is also used to indicate a second dependency relationship between the first stream and the third stream, the second dependency relationship including: the first stream depends on the third stream; wherein, there is a third dependency relationship between the second stream and the third stream, the third dependency relationship including: the second stream and the third stream depend on each other.

17. The method according to claim 16, characterized in that, The method further includes: Send a second message, the second message being used to indicate that the third stream depends on the second stream; Send a third message, which indicates that the second stream depends on the third stream.

18. The method according to claim 17, characterized in that, The second information includes the identification information of the second stream, and the third information includes the identification information of the third stream.

19. The method according to any one of claims 16-18, characterized in that, The method further includes: Send identification information for a first stream group, wherein the multiple streams included in the first stream group are interdependent, and the first stream group includes the second stream and the third stream.

20. The method according to claim 19, characterized in that, The first information includes the identification information of the first flow group, and the first information is used to indicate the dependency relationship between the first flow and the flow in the first flow group.

21. The method according to any one of claims 15-20, characterized in that, The first information includes the identification information of the second stream.

22. The method according to claim 15 or 16, characterized in that, The first information is used to indicate a first value corresponding to the first stream, and the method further includes: Send a fourth message, which indicates the second value corresponding to the second stream; the size relationship between the first value and the second value is used to indicate the first dependency relationship.

23. The method according to claim 22, characterized in that, The method further includes: Send a fifth message, which is used to indicate a third value corresponding to the third stream, wherein the second value and the third value are the same; wherein the magnitude relationship between the first value and the third value is used to indicate a second dependency relationship between the first stream and the third stream, the second dependency relationship including: the first stream depends on the third stream, and the second value and the third value are the same, which is used to indicate that the second stream and the third stream are mutually dependent.

24. The method according to claim 15 or 16, characterized in that, The method further includes: A sixth message is sent, which is used to establish a first stream group, the first stream group including a second stream and a third stream, and there are dependencies between the multiple streams included in the first stream group.

25. The method according to claim 24, characterized in that, The sixth information includes the value corresponding to each flow in the first flow group, and the size relationship between the values ​​corresponding to each flow, which is used to indicate the dependency relationship between the multiple flows included in the first flow group; or, The multiple flows included in the first flow group are interdependent.

26. The method according to claim 24 or 25, characterized in that, The first information includes the identification information of the second stream; or, The first information includes the identification information of the first stream group; or, The sixth information includes the value corresponding to each flow in the first flow group. The first information includes the first value corresponding to the first flow and the size relationship between the first value and the value corresponding to each flow, which is used to indicate the dependency relationship between the first flow and each flow. or, The sixth information includes the value corresponding to the first flow group, the first information includes the first value corresponding to the first flow, and the size relationship between the value corresponding to the first flow group and the first value, which is used to indicate the dependency relationship between the first flow and the multiple flows included in the first flow group.

27. The method according to claim 24 or 25, characterized in that, The first information is used to establish a second flow group, wherein the flow included in the second flow group has a dependency relationship with the flow included in the first flow group, and the second flow group includes the first flow.

28. The method according to claim 27, characterized in that, The first information includes the identification information of the first stream group; or, The sixth information includes the value corresponding to each flow in the first flow group, the first information includes the value corresponding to each flow in the second flow group, the value corresponding to each flow in the second flow group, and the size relationship between the value corresponding to each flow in the second flow group and the value corresponding to each flow in the first flow group, which is used to indicate the dependency relationship between each flow in the second flow group and each flow in the first flow group; or, The sixth information includes the value corresponding to the first flow group, the first information includes the value corresponding to the second flow group, the value corresponding to the first flow group and the value corresponding to the second flow group, and the size relationship between them, which is used to indicate the dependency relationship between the multiple flows included in the second flow group and the multiple flows included in the first flow group.

29. A communication device, characterized in that, The communication device includes a module or unit for implementing the method of any one of claims 1-14; or, the communication device includes a module or unit for implementing the method of any one of claims 15-28.

30. A communication device, characterized in that, The communication device includes a processor, which, when executing instructions, causes the communication device to perform the method of any one of claims 1-14, or causes the communication device to perform the method of any one of claims 15-28.

31. A computer-readable storage medium, characterized in that, It stores instructions that, when executed by a computer, cause the method of any one of claims 1-28 to be performed.

32. A computer program product, characterized in that, The computer program product includes instructions that, when executed by a computer, cause the method of any one of claims 1-28 to be performed.

33. A communication system, characterized in that, The communication system includes a first network element and a terminal device, wherein the terminal device is used to perform the method of any one of claims 1-14, and the first network element is used to perform the method of any one of claims 15-28.

Images