A communication method and apparatus

Abstract

The application relates to the communication technical field, and discloses a communication method and device. The method comprises the following steps: a network device receives indication information, the indication information is used for indicating that M QoS flows have an association relationship, and then the network device can process the M QoS flows according to the indication information. In this way, when the network device processes the M QoS flows, the association relationship between the M QoS flows is considered, so that the synchronization requirement between different data flows can be met.

Description

Technical Field

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

[0002] In mobile communication networks, operators can provide users with a wider variety of services, including voice, data, and video. Different services have different requirements for latency, bandwidth, and other parameters. Taking multimedia services as an example, there are differences in the importance of different data streams. For instance, immersive voice and audio services (IVAS) have multiple channels, where the main channel data stream has a higher priority than the surround channel data stream. Similarly, in Scalable Video Coding (SVC), the base layer data stream has a higher priority than the extension layer data stream.

[0003] To differentiate various data streams, the 5G communication system introduces a Quality of Service (QoS) scheme, providing network services with different QoS levels to meet diverse business needs. Specifically, a terminal device can establish one or more PDU sessions, and each PDU session can transmit multiple data streams with different QoS requirements, referred to as QoS streams.

[0004] However, for multimedia services, there may be synchronization requirements between different data streams. For example, for multimedia services that simultaneously contain video, audio, and text, it is required that the video, audio, and text of the same frame be sent to the receiving end synchronously in order to achieve synchronous reproduction of the three types of information. Summary of the Invention

[0005] This application provides a communication method and apparatus to facilitate the synchronization needs between different data streams.

[0006] Firstly, embodiments of this application provide a communication method that can be applied to a first network device or to a chip within the first network device. Taking the application of this method to a first network device as an example, in this method, the first network device receives indication information, which indicates that M QoS flows are associated, where M is an integer greater than 1; subsequently, the first network device can process the M QoS flows according to the indication information.

[0007] In this approach, when processing M QoS flows, the network device considers the correlation between the M QoS flows, thereby facilitating the fulfillment of synchronization requirements between different data flows.

[0008] In one possible design, the first network device processes M QoS flows, including: the first network device accepting or rejecting the establishment requests of the M QoS flows; or, the first network device accepting or rejecting the modification requests of the M QoS flows.

[0009] In one possible design, the first network device processes M QoS flows, including: the first network device determining the burst to which the data packets in the M QoS flows belong, and processing the data packets belonging to the first burst in the M QoS flows; and after processing the data packets belonging to the first burst, processing the data packets belonging to the second burst in the M QoS flows.

[0010] In this approach, network devices process data packets from M QoS streams in bursts, without spanning multiple bursts. For example, the next burst can only begin after the air interface transmission of one burst has ended. This facilitates the synchronous arrival of data packets from the same burst at the receiving end within a certain time interval, effectively avoiding the problem of large delays (i.e., asynchrony) in the arrival of data packets from the same burst at the receiving end caused by transmitting a portion of the data packets from the first burst, then a portion of the data packets from the second burst, and then the remaining portion of the data packets from the first burst.

[0011] In one possible design, the first network device determines the burst to which the data packets in the M QoS flows belong, including: the first network device determining the burst to which the data packets in the M QoS flows belong based on burst identification information of the data packets in the M QoS flows; or, the first network device determining the burst to which the data packets in the M QoS flows belong based on payload information of the data packets in the M QoS flows; or, the first network device determining the burst to which the data packets in the M QoS flows belong based on a distinguishing identifier between different bursts; or, the first network device determining the burst to which the data packets in the M QoS flows belong based on the transmission time interval of the data packets in different bursts.

[0012] In one possible design, the first network device processes data packets belonging to the first burst among M QoS flows, including: the first network device transmitting data packets belonging to the first burst among M QoS flows according to the priority of the M QoS flows, thus ensuring the data transmission of high-priority QoS flows first; or, the first network device transmitting data packets belonging to the first burst among M QoS flows according to the transmission ratio information of the M QoS flows, thus effectively ensuring that different data flows arrive at the receiving end in a relatively balanced manner; or, the first network device transmitting data packets belonging to the first burst among M QoS flows in a first-in-first-out (FIFO) manner.

[0013] In one possible design, the first network device processes data packets belonging to the first burst in M ​​QoS streams, including: after the first network device determines that the data packets belonging to the first burst exceed the transmission delay requirement, it discards the data packets belonging to the first burst in the M QoS streams that have not yet been transmitted.

[0014] In one possible design, the indication information includes M associated information corresponding to each of the M QoS flows, and the M associated information are identical.

[0015] In one possible design, M QoS flows belong to a first PDU session; the indication information includes association information corresponding to the first PDU session, which is used to indicate that the first PDU session is an associated session, and the QoS flows included in the associated session have an association relationship.

[0016] In one possible design, the association information includes an association identifier and / or association type information.

[0017] In one possible design, the association type information is used to indicate an association type, which includes at least one of a first type, a second type, and a third type; the first type is used to indicate that data packets belonging to the same burst in the M QoS flows are transmitted according to the priority of the M QoS flows; the second type is used to indicate that data packets belonging to the same burst in the M QoS flows are transmitted according to the transmission ratio information of the M QoS flows; and the third type is used to indicate that data packets belonging to the same burst in the M QoS flows are transmitted in a first-in-first-out (FIFO) manner.

[0018] In one possible design, when the association type information indicates a second type, the association type information includes the transmission ratio information, or the indication information further includes the transmission ratio information.

[0019] In one possible design, the first network device receiving the indication information may mean that the first network device receives the indication information from the core network device.

[0020] In one possible design, the first network device receiving the instruction information may mean that the first network device receives the instruction information from the second network device; wherein the second network device is the primary network device of the terminal device and the first network device is the secondary network device of the terminal device; or, the second network device is the source network device of the terminal device and the first network device is the target network device of the terminal device.

[0021] In one possible design, the indication information includes at least one of the following: (1) an identifier of an associated session, wherein the associated session includes M QoS flows that are associated; (2) an identifier of multiple QoS flows that are associated, wherein the multiple QoS flows that are associated include M QoS flows; (3) an identifier of a logical channel corresponding to the multiple QoS flows that are associated; (4) an identifier of a data radio bearer (DRB) corresponding to the multiple QoS flows that are associated; (5) multiple TFTs, wherein the QoS flows matched with each of the multiple TFTs are associated, wherein the QoS flows matched with each of the multiple TFTs include M QoS flows.

[0022] In one possible design, the indication information may also include association identifiers and / or association type information.

[0023] In one possible design, the first network device receiving the instruction information may mean that the first network device receives the instruction information from the terminal device.

[0024] In one possible design, the logical channels corresponding to the M QoS flows are located in different logical channel groups.

[0025] It should be noted that, as a possible alternative, the communication method provided in the first aspect above can also be described as follows: receiving indication information, the indication information being used to indicate the synchronous QoS stream set to which the first QoS stream belongs; and then the network device can process the QoS streams within the synchronous QoS stream set according to the indication information.

[0026] In one possible design, the indication information may include at least one of the following: association identifier, association type information, and association indication; wherein QoS flows with the same association identifier belong to the same synchronous QoS flow set, QoS flows with the same association type belong to the same synchronous QoS flow set, and QoS flows included in a PDU session with an association indication belong to the same synchronous QoS flow set. For example, when the indication information includes an association identifier, it can be understood that the indication information is used to indicate the identifier of the synchronous QoS flow set to which the QoS flow belongs; when the indication information includes association type information, it can be understood that the indication information is used to indicate the type of the synchronous QoS flow set to which the QoS flow belongs; and when the indication information includes an association indication, it can be understood that the indication information is used to indicate that all QoS flows included in a PDU session belong to the same synchronous QoS flow set.

[0027] Secondly, embodiments of this application provide a communication method that can be applied to core network equipment (such as SMF or AMF network elements) or to chips within the core network equipment. Taking the application of this method to a core network equipment as an example, in this method, the core network equipment determines indication information, which indicates that M QoS flows have an association relationship; M is an integer greater than 1; and sends the indication information to the network equipment.

[0028] In one possible design, the indication information includes M associated information corresponding to each of the M QoS flows, and the M associated information are identical.

[0029] In one possible design, M QoS flows belong to a first PDU session; the indication information includes association information corresponding to the first PDU session, which is used to indicate that the first PDU session is an associated session, and the QoS flows included in the associated session have an association relationship.

[0030] In one possible design, the association information includes an association identifier and / or association type information.

[0031] In one possible design, the association type information is used to indicate an association type, which includes at least one of a first type, a second type, and a third type; the first type is used to indicate that data packets belonging to the same burst in the M QoS flows are transmitted according to the priority of the M QoS flows; the second type is used to indicate that data packets belonging to the same burst in the M QoS flows are transmitted according to the transmission ratio information of the M QoS flows; and the third type is used to indicate that data packets belonging to the same burst in the M QoS flows are transmitted in a first-in-first-out (FIFO) manner.

[0032] In one possible design, when the association type information indicates a second type, the association type information includes the transmission ratio information, or the indication information further includes the transmission ratio information.

[0033] Thirdly, embodiments of this application provide a communication method that can be applied to a terminal device or to a chip within the terminal device. Taking the application of this method to a terminal device as an example, in this method, the terminal device receives indication information; wherein, the indication information is used to indicate that M QoS flows have an association relationship, or, the indication information is used to indicate that the DRBs or LCHs corresponding to the M QoS flows have an association relationship, where M is an integer greater than 1; furthermore, the terminal device processes the M QoS flows according to the indication information.

[0034] In one possible design, the indication information includes M associated information corresponding to each of the M QoS flows, and the M associated information are identical.

[0035] In one possible design, M QoS flows belong to a first PDU session; the indication information includes association information corresponding to the first PDU session, which is used to indicate that the first PDU session is an associated session, and the QoS flows included in the associated session have an association relationship.

[0036] In one possible design, the association information includes an association identifier and / or association type information.

[0037] In one possible design, the association type information is used to indicate an association type, which includes at least one of a first type, a second type, and a third type; the first type is used to indicate that data packets belonging to the same burst in the M QoS flows are transmitted according to their priority; the second type is used to indicate that data packets belonging to the same burst in the M QoS flows are transmitted according to their transmission ratio information; and the third type is used to indicate that data packets belonging to the same burst in the M QoS flows are transmitted in a first-in, first-out (FIFO) manner.

[0038] In one possible design, when the association type information indicates the second type, the indication information also includes the transmission ratio information.

[0039] In one possible design, the terminal device processes the M QoS flows, including: the terminal device determining the burst to which the data packets in the M QoS flows belong, and processing the data packets belonging to the first burst in the M QoS flows; and after processing the data packets belonging to the first burst, processing the data packets belonging to the second burst in the M QoS flows.

[0040] In one possible design, the terminal device determines the burst to which the data packets in the M QoS flows belong, including: the terminal device determining the burst to which the data packets in the M QoS flows belong based on burst identification information of the data packets in the M QoS flows; or, the terminal device determining the burst to which the data packets in the M QoS flows belong based on payload information; or, the terminal device determining the burst to which the data packets in the M QoS flows belong based on a distinguishing identifier between different bursts; or, the terminal device determining the burst to which the data packets in the M QoS flows belong based on the transmission time interval of data packets in different bursts.

[0041] In one possible design, the terminal device processes data packets belonging to the first burst in the M QoS flows, including: the terminal device receiving an uplink grant from the network device; and the terminal device transmitting data packets belonging to the first burst in the M QoS flows on the resources indicated by the uplink grant according to the priority of the M QoS flows; or, the terminal device transmitting data packets belonging to the first burst in the M QoS flows on the resources indicated by the uplink grant according to the transmission ratio information of the M QoS flows; or, the terminal device transmitting data packets belonging to the first burst in the M QoS flows on the resources indicated by the uplink grant in a first-in, first-out (FIFO) manner.

[0042] In one possible design, the terminal device processes data packets belonging to the first burst in the M QoS streams, including: after determining that the data packets belonging to the first burst exceed the transmission delay requirement, the terminal device discards the data packets belonging to the first burst in the M QoS streams that have not yet been transmitted.

[0043] It should be noted that the communication method provided in the second or third aspect corresponds to the first aspect. Therefore, the beneficial effects of the relevant technical features of the second or third aspect can be referred to the description in the first aspect, and will not be repeated here.

[0044] Fourthly, embodiments of this application provide a communication method that can be applied to a CU or to a chip within the CU. Taking the application of this method to a CU as an example, in this method, the CU receives first indication information, which indicates that M QoS flows are associated, where M is an integer greater than 1; and the CU processes the M QoS flows according to the first indication information.

[0045] In one possible design, the CU processes the M QoS flows, including: the CU accepting or rejecting the establishment requests of the M QoS flows; or, the CU accepting or rejecting the modification requests of the M QoS flows.

[0046] In one possible design, the method further includes: the CU determining the DRB or LCH corresponding to the M QoS flows; and sending second indication information to the DU, the second indication information being used to indicate that the DRB or LCH corresponding to the M QoS flows have an association relationship.

[0047] In one possible design, the second indication information includes an association identifier and / or association type information.

[0048] In one possible design, the association type information is used to indicate an association type, which includes at least one of a first type, a second type, and a third type; the first type is used to indicate that data packets belonging to the same burst in the M QoS flows are transmitted according to their priority; the second type is used to indicate that data packets belonging to the same burst in the M QoS flows are transmitted according to their transmission ratio information; and the third type is used to indicate that data packets belonging to the same burst in the M QoS flows are transmitted in a first-in, first-out (FIFO) manner.

[0049] In one possible design, when the association type information indicates the second type, the indication information also includes the transmission ratio information.

[0050] In one possible design, the CU processes the M QoS flows by sending data packets of the M QoS flows to the DU, wherein the data packets of the M QoS flows include burst identification information.

[0051] In one possible design, the CU processes the M QoS flows, including: the CU receiving drop indication information from the DU, the drop indication information including identification information of a first burst; and then discarding data packets belonging to the first burst but not yet transmitted in the DRB or logical channel corresponding to the drop indication information. Here, the DRB or logical channel corresponding to the drop indication information can be the DRB or logical channel mapped by the M QoS flows.

[0052] Fifthly, embodiments of this application provide a communication method that can be applied to a DU or to a chip within the DU. Taking the application of this method to a DU as an example, in this method, the DU receives second indication information from a CU, the second indication information indicating that the DRBs or LCHs corresponding to M QoS flows are associated; and the DU processes data packets in the M QoS flows according to the second indication information.

[0053] In one possible design, the second indication information includes an association identifier and / or association type information.

[0054] In one possible design, the association type information is used to indicate an association type, which includes at least one of a first type, a second type, and a third type; the first type is used to indicate that data packets belonging to the same burst in the M QoS flows are transmitted according to their priority; the second type is used to indicate that data packets belonging to the same burst in the M QoS flows are transmitted according to their transmission ratio information; and the third type is used to indicate that data packets belonging to the same burst in the M QoS flows are transmitted in a first-in, first-out (FIFO) manner.

[0055] In one possible design, when the association type information indicates the second type, the indication information also includes the transmission ratio information.

[0056] In one possible design, the DU processes the data packets of the M QoS flows, including: the DU determining the burst to which the data packets in the M QoS flows belong, and processing the data packets belonging to the first burst in the M QoS flows; and, after processing the data packets belonging to the first burst, processing the data packets belonging to the second burst in the M QoS flows.

[0057] In one possible design, the DU processes data packets belonging to the first burst in the M QoS flows, including: the DU transmitting data packets belonging to the first burst in the M QoS flows according to the priority of the M QoS flows; or, the DU transmitting data packets belonging to the first burst in the M QoS flows according to the transmission ratio information of the M QoS flows; or, the DU transmitting data packets belonging to the first burst in the M QoS flows in a first-in-first-out (FIFO) manner.

[0058] In one possible design, the DU processes data packets belonging to the first burst in the M QoS flows, including: after the DU determines that the data packets belonging to the first burst exceed the transmission delay requirement, it sends a drop indication information for the corresponding DRB or logical channel to the CU. The drop indication information includes the identification information of the first burst, and the drop indication information is used to indicate the dropping of data packets belonging to the first burst in the corresponding DRB or logical channel that have not yet been transmitted.

[0059] Sixthly, embodiments of this application provide a communication method that can be applied to a CU-CP or to a chip within the CU-CP. Taking the application of this method to a CU-CP as an example, in this method, the CU-CP receives first indication information, which indicates that M QoS flows are associated; and the CU-CP processes the M QoS flows according to the first indication information.

[0060] In one possible design, the CU-CP processes the M QoS flows, including: the CU-CP accepting or rejecting the establishment requests of the M QoS flows; or, the CU-CP accepting or rejecting the modification requests of the M QoS flows.

[0061] In one possible design, the method further includes: the CU-CP determining the DRB or LCH corresponding to the M QoS flows, and sending second indication information to the DU, the second indication information being used to indicate that the DRB or LCH corresponding to the M QoS flows have an association relationship.

[0062] In one possible design, the second indication information includes an association identifier and / or association type information.

[0063] In one possible design, the association type information is used to indicate an association type, which includes at least one of a first type, a second type, and a third type; the first type is used to indicate that data packets belonging to the same burst in the M QoS flows are transmitted according to their priority; the second type is used to indicate that data packets belonging to the same burst in the M QoS flows are transmitted according to their transmission ratio information; and the third type is used to indicate that data packets belonging to the same burst in the M QoS flows are transmitted in a first-in, first-out (FIFO) manner.

[0064] In one possible design, when the association type information indicates the second type, the indication information also includes the transmission ratio information.

[0065] Seventhly, embodiments of this application provide a communication method that can be applied to a CU-UP or to a chip within the CU-UP. Taking the application of this method to a CU-UP as an example, in this method, the CU-UP receives discard indication information from a DU, the discard indication information including identification information of a first burst; then the CU-UP discards data packets belonging to the first burst but not yet transmitted in the DRB or logical channel corresponding to the discard indication information. Alternatively, in this method, the CU-UP receives third indication information from a CU-CP, the third indication information indicating a burst identification method, and the CU-UP determines the burst to which the data packet belongs based on the third indication information.

[0066] Eighthly, this application provides a communication system including a first network device and a core network device. Exemplarily, the first network device may include a CU and a DU; further, the CU may include a CU-CP and a CU-UP. The first network device can be used to execute the methods in any possible design or implementation of the first, fourth, to seventh aspects, and the core network device can be used to execute the methods in any possible design or implementation of the second aspect.

[0067] In one embodiment, the core network device is configured to: determine indication information, the indication information being used to indicate that M QoS flows are associated, where M is an integer greater than 1; send the indication information to a first network device; and the first network device is configured to: receive the indication information from the core network device.

[0068] In one possible design of this embodiment, the first network device is further configured to process M QoS flows according to indication information.

[0069] In one possible design of this embodiment, the communication system further includes a second network device; the first network device is further configured to send indication information to the second network device; the second network device is configured to receive the indication information from the first network device and process M QoS streams according to the indication information; wherein, the first network device is the main network device of the terminal device, and the second network device is the auxiliary network device of the terminal device.

[0070] In one possible design of this embodiment, the communication system further includes a second network device; the first network device is further configured to send indication information to the second network device; the second network device is configured to receive the indication information from the first network device and process M QoS streams according to the indication information; wherein, the first network device is the source network device of the terminal device, and the second network device is the target network device of the terminal device.

[0071] Ninthly, this application provides a communication device, which can be a network device (such as a first network device) or a chip disposed within a network device. Exemplarily, the network device may include a CU and a DU; further, the CU may include a CU-CP and a CU-UP. The communication device has the functions to implement the first, fourth to seventh aspects described above. For example, the communication device includes modules, units, or means corresponding to the steps involved in the first, fourth to seventh aspects described above. These functions, units, or means can be implemented by software, hardware, or hardware executing corresponding software.

[0072] In one possible design, the communication device includes a processing unit and a communication unit. The communication unit can be used to transmit and receive signals to enable communication between the communication device and other devices, such as receiving configuration information from a network device. The processing unit can be used to perform some internal operations of the communication device. The functions performed by the processing unit and the communication unit can correspond to the steps involved in the first, fourth to seventh aspects described above.

[0073] In one possible design, the communication device includes a processor and may further include a transceiver for transmitting and receiving signals. The processor executes program instructions to perform the methods in any possible design or implementation of the first, fourth, to seventh aspects described above. The communication device may also include one or more memories for coupling with the processor. The one or more memories may be integrated with the processor or may be separate from it; this application is not limiting. The memories may store necessary computer programs or instructions for implementing the functions involved in the first, fourth, to seventh aspects described above. The processor can execute the computer programs or instructions stored in the memories, and when the computer programs or instructions are executed, the communication device implements the methods in any possible design or implementation of the first, fourth, to seventh aspects described above.

[0074] In one possible design, the communication device includes a processor and a memory, the memory of which can store necessary computer programs or instructions for implementing the functions described in the first, fourth to seventh aspects above. The processor can execute the computer programs or instructions stored in the memory, and when the computer programs or instructions are executed, cause the communication device to implement the methods in any possible design or implementation of the first, fourth to seventh aspects above.

[0075] In one possible design, the communication device includes at least one processor and an interface circuit, wherein the at least one processor is configured to communicate with other devices via the interface circuit and to perform the methods in any possible design or implementation of the first, fourth to seventh aspects described above.

[0076] Tenthly, this application provides a communication device, which can be a core network device or a chip disposed within a core network device. The communication device has the functions described in the second aspect above. For example, the communication device includes modules, units, or means corresponding to the steps described in the second aspect above. These functions, units, or means can be implemented by software, hardware, or hardware executing corresponding software.

[0077] In one possible design, the communication device includes a processing unit and a communication unit. The communication unit can be used to transmit and receive signals to enable communication between the communication device and other devices, such as sending system information to a terminal device. The processing unit can be used to perform some internal operations of the communication device. The functions performed by the processing unit and the communication unit can correspond to the steps involved in the second aspect above.

[0078] In one possible design, the communication device includes a processor and a memory, the memory of which can store the necessary computer programs or instructions for implementing the functions described in the second aspect above. The processor can execute the computer programs or instructions stored in the memory, and when the computer programs or instructions are executed, cause the communication device to implement the methods in any possible design or implementation of the second aspect above.

[0079] In one possible design, the communication device includes at least one processor and interface circuitry, wherein the at least one processor is configured to communicate with other devices via the interface circuitry and execute the methods in any possible design or implementation of the second aspect described above. The communication device may further include one or more memories coupled to the processor. The one or more memories may be integrated with the processor or disposed separately from it; this application is not limiting. The memories may store necessary computer programs or instructions for implementing the functions involved in the second aspect described above. The processor can execute the computer programs or instructions stored in the memories, and when the computer programs or instructions are executed, the communication device implements the methods in any possible design or implementation of the second aspect described above.

[0080] Eleventhly, this application provides a communication device, which can be a terminal device or a chip disposed within a terminal device. The communication device has the functions described in the third aspect above. For example, the communication device includes modules, units, or means corresponding to the steps described in the third aspect above. These functions, units, or means can be implemented by software, hardware, or hardware executing corresponding software.

[0081] In one possible design, the communication device includes a processing unit and a communication unit. The communication unit can be used to send and receive signals to enable communication between the communication device and other devices, such as sending system information to a terminal device. The processing unit can be used to perform some internal operations of the communication device. The functions performed by the processing unit and the communication unit can correspond to the steps involved in the third aspect above.

[0082] In one possible design, the communication device includes a processor and may further include a transceiver for transmitting and receiving signals. The processor executes program instructions to perform the methods in any possible design or implementation of the third aspect described above. The communication device may also include one or more memories for coupling with the processor. The one or more memories may be integrated with the processor or disposed separately from it; this application is not limiting. The memories may store the necessary computer programs or instructions for implementing the functions involved in the third aspect described above. The processor can execute the computer programs or instructions stored in the memories, and when the computer programs or instructions are executed, the communication device implements the methods in any possible design or implementation of the third aspect described above.

[0083] In one possible design, the communication device includes a processor and a memory, the memory of which can store the necessary computer programs or instructions for implementing the functions involved in the third aspect above. The processor can execute the computer programs or instructions stored in the memory, and when the computer programs or instructions are executed, cause the communication device to implement the methods in any possible design or implementation of the third aspect above.

[0084] In one possible design, the communication device includes at least one processor and an interface circuit, wherein the at least one processor is configured to communicate with other devices via the interface circuit and to perform the methods in any possible design or implementation of the third aspect described above.

[0085] In a twelfth aspect, this application provides a computer-readable storage medium storing computer-readable instructions that, when read and executed by a computer, cause the computer to perform any of the possible designs in the first to seventh aspects described above.

[0086] In a thirteenth aspect, this application provides a computer program product that, when read and executed by a computer, causes the computer to perform any of the possible designs in the first to seventh aspects described above.

[0087] In a fourteenth aspect, this application provides a chip including a processor coupled to a memory for reading and executing a software program stored in the memory to implement the methods in any of the possible designs of the first to seventh aspects described above.

[0088] These or other aspects of this application will become more apparent from the description of the following embodiments. Attached Figure Description

[0089] Figure 1This is a schematic diagram of a network architecture applicable to an embodiment of this application;

[0090] Figure 2a This is an example diagram of the protocol layer structure between a terminal device and a network device provided in an embodiment of this application;

[0091] Figure 2b A schematic diagram of a CU-DU separation architecture provided in an embodiment of this application;

[0092] Figure 2c A schematic diagram of yet another CU-DU separation architecture provided in an embodiment of this application;

[0093] Figure 2d A schematic diagram of an air interface protocol stack distribution provided in an embodiment of this application;

[0094] Figure 3a This is a schematic diagram of a QoS model in a 5G communication system provided in an embodiment of this application;

[0095] Figure 3b This is a schematic diagram of the PDU session establishment process provided in the embodiments of this application;

[0096] Figure 4 A schematic diagram illustrating the transmission of multiple video frames provided in an embodiment of this application;

[0097] Figure 5 A flowchart illustrating the communication method provided in Embodiment 1 of this application;

[0098] Figure 6 This is a flowchart illustrating the communication method provided in Embodiment 2 of this application.

[0099] Figure 7 This is a flowchart illustrating the communication method provided in Embodiment 3 of this application;

[0100] Figure 8 This is a flowchart illustrating the communication method provided in Embodiment 5 of this application.

[0101] Figure 9 This is a flowchart illustrating the communication method provided in Embodiment Six of this application;

[0102] Figure 10 The following are possible exemplary block diagrams of the apparatus involved in the embodiments of this application;

[0103] Figure 11 This application provides a schematic diagram of the structure of a network device according to an embodiment of the present application.

[0104] Figure 12 A schematic diagram of the structure of a core network device provided in an embodiment of this application;

[0105] Figure 13 This is a schematic diagram of the structure of a terminal device provided in an embodiment of this application. Detailed Implementation

[0106] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0107] Figure 1 This is a schematic diagram of a network architecture applicable to an embodiment of this application. For example... Figure 1 As shown, terminal devices can access a wireless network to obtain services from an external network (such as a data network (DN)) or communicate with other devices, such as other terminal devices. This wireless network includes a radio access network (RAN) and a core network (CN). The RAN is used to connect terminal devices to the wireless network, while the CN manages the terminal devices and provides a gateway for communication with the DN.

[0108] The following sections respectively address... Figure 1 The terminal equipment, RAN, CN, and DN involved are described in detail.

[0109] I. Terminal Equipment

[0110] Terminal equipment includes devices that provide voice and / or data connectivity to users, such as handheld devices with wireless connectivity or processing devices connected to a wireless modem. The terminal equipment can communicate with the core network via a radio access network (RAN) and exchange voice and / or data with the RAN. The terminal equipment can include user equipment (UE), wireless terminal equipment, mobile terminal equipment, device-to-device (D2D) terminal equipment, vehicle-to-everything (V2X) terminal equipment, machine-to-machine / machine-type communications (M2M / MTC) terminal equipment, internet of things (IoT) terminal equipment, subscriber unit, subscriber station, mobile station, remote station, access point (AP), remote terminal, access terminal, user terminal, user agent, or user device, etc. For example, this can include mobile phones (or "cellular" phones), computers with mobile terminal devices, portable, pocket-sized, handheld, and computer-embedded mobile devices. Examples include Personal Communication Service (PCS) phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, and Personal Digital Assistants (PDAs). It also includes limited devices, such as those with low power consumption, limited storage capacity, or limited computing power. Examples include information sensing devices such as barcode scanners, radio frequency identification (RFID), sensors, Global Positioning System (GPS), and laser scanners.

[0111] 2. RAN

[0112] The RAN may include one or more RAN devices, such as RAN device 1101 and RAN device 1102. The interface between the RAN device and the terminal device may be a Uu interface (or air interface). Of course, in future communications, the names of these interfaces may remain unchanged or may be replaced by other names, and this application does not limit this.

[0113] RAN equipment refers to nodes or devices that connect terminal devices to a wireless network. RAN equipment can also be called network equipment or base stations. Examples of RAN equipment include, but are not limited to: next-generation NodeBs (gNBs), evolved NodeBs (eNBs), radio network controllers (RNCs), node Bs (NBs), base station controllers (BSCs), base transceiver stations (BTSs), home base stations (e.g., home evolved nodeBs or home node Bs, HNBs), baseband units (BBUs), transmitting and receiving points (TRPs), transmitting points (TPs), and mobile switching centers in 5G communication systems.

[0114] (1) Protocol layer structure

[0115] Communication between RAN devices and terminal devices follows a certain protocol layer structure. For example, the control plane protocol layer structure may include the functions of protocol layers such as RRC layer, packet data convergence protocol (PDCP) layer, radio link control (RLC) layer, media access control (MAC) layer, and physical layer. The user plane protocol layer structure may include the functions of protocol layers such as PDCP layer, RLC layer, MAC layer, and physical layer. In one possible implementation, a service data adaptation protocol (SDAP) layer may also be included above the PDCP layer.

[0116] Taking data transmission between network devices and terminal devices as an example, data transmission needs to pass through user plane protocol layers, such as the SDAP layer, PDCP layer, RLC layer, MAC layer, and physical layer. The SDAP layer, PDCP layer, RLC layer, MAC layer, and physical layer can also be collectively referred to as the access layer. Based on the direction of data transmission, it is divided into sending and receiving; each of the above layers is further divided into a sending part and a receiving part. For example, see the following example for downstream data transmission. Figure 2a The diagram shows the transmission of downlink data between layers. Figure 2a Downward arrows indicate data transmission, and upward arrows indicate data reception. After receiving data from the upper layer, the PDCP layer transmits the data to the RLC and MAC layers. The MAC layer then generates transport blocks, which are then wirelessly transmitted through the physical layer. Data is encapsulated in each layer. Data received by a layer from the upper layer is considered a Service Data Unit (SDU) for that layer. After layer encapsulation, it becomes a PDU and is then passed to the next layer. For example, data received by the PDCP layer from the upper layer is called a PDCP SDU, and data sent by the PDCP layer to the lower layer is called a PDCP PDU; similarly, data received by the RLC layer from the upper layer is called an RLC SDU, and data sent by the RLC layer to the lower layer is called an RLC PDU. In the protocol, inter-layer communication is mostly represented by channels. The RLC layer and MAC layer correspond via a logical channel (LCH), the MAC layer and physical layer correspond via a transport channel, and the physical layer and below correspond via physical channels, used to map to the physical layer at the other end.

[0117] For example, according to Figure 2a It can also be seen that the terminal device has an application layer and a non-access layer. The application layer can provide services to applications installed on the terminal device. For example, downlink data received by the terminal device can be sequentially transmitted from the physical layer to the application layer, and then provided to the application by the application layer. Alternatively, the application layer can acquire data generated by the application and sequentially transmit the data to the physical layer for transmission to other communication devices. The non-access layer can be used to forward user data, such as forwarding uplink data received from the application layer to the SDAP layer or forwarding downlink data received from the SDAP layer to the application layer.

[0118] (2) CU and DU

[0119] In this embodiment, the RAN device may include one or more centralized units (CUs) and one or more distributed units (DUs), and multiple DUs may be centrally controlled by one CU. As an example, the interface between the CU and DU can be called an F1 interface, where the control plane (CP) interface can be F1-C and the user plane (UP) interface can be F1-U. The CU and DU can be distinguished according to the protocol layer of the wireless network: for example... Figure 2b As shown, the functional settings of the PDCP layer and above are configured in the CU, while the functional settings of the protocol layers below the PDCP layer (such as the RLC layer and MAC layer) are configured in the DU.

[0120] It is understandable that the above division of CU and DU processing functions according to protocol layers is merely an example. Other division methods are also possible. For instance, functions of protocol layers above the PDCP layer can be placed in the CU, while functions of protocol layers at and below the PDCP layer can be placed in the DU. Alternatively, the CU or DU can be divided into functions with more protocol layers, or it can be divided into partial processing functions with protocol layers. In one design, some functions of the RLC layer and functions of protocol layers above the RLC layer are placed in the CU, while the remaining functions of the RLC layer and functions of protocol layers below the RLC layer are placed in the DU. In another design, the functions of the CU or DU can be divided according to service type or other system requirements, such as by latency. Functions whose processing time needs to meet latency requirements are placed in the DU, while functions that do not need to meet this latency requirement are placed in the CU. In yet another design, the CU can also have one or more core network functions. For example, the CU can be located on the network side for convenient centralized management; the DU can have multiple radio frequency functions, or the radio frequency functions can be remotely located. This application does not limit this aspect.

[0121] For example, the functionality of a CU can be implemented by a single entity, or it can be implemented by different entities. For instance, such as... Figure 2cAs shown, the functions of the CU can be further divided, that is, the control plane and user plane can be separated and implemented through different entities, namely the control plane CU entity (i.e., the CU-CP entity) and the user plane CU entity (i.e., the CU-UP entity). The CU-CP entity and the CU-UP entity can be coupled with the DU to jointly complete the functions of the RAN device. The interface between the CU-CP entity and the CU-UP entity can be an E1 interface, the interface between the CU-CP entity and the DU can be an F1-C interface, and the interface between the CU-UP entity and the DU can be an F1-U interface. A DU and a CU-UP can be connected to a CU-CP. Under the control of the same CU-CP, a DU can be connected to multiple CU-UPs, and a CU-UP can be connected to multiple DUs.

[0122] based on Figure 2c , Figure 2d This is a schematic diagram of an air interface protocol stack distribution. For example... Figure 2d As shown, for both the user plane and control plane, the air interface protocol stack can be RLC, MAC, and PHY in the DU, and PDCP and above protocol layers in the CU.

[0123] It should be noted that: in the above Figures 2b to 2d In the illustrated architecture, signaling generated by the CU can be sent to the terminal device via the DU, or signaling generated by the terminal device can be sent to the CU via the DU. The DU can directly encapsulate the signaling through the protocol layer and transmit it to the terminal device or CU without parsing it. In the following embodiments, if such signaling transmission between the DU and the terminal device is involved, the DU's sending or receiving of signaling includes this scenario. For example, RRC or PDCP layer signaling will eventually be processed into physical layer signaling and sent to the terminal device, or it may be transformed from received physical layer signaling. In this architecture, the RRC or PDCP layer signaling can also be considered as being sent by the DU, or by the DU and the radio frequency device.

[0124] III. CN

[0125] A CN can include one or more CN devices. Taking a 5G communication system as an example, a CN can include access and mobility management function (AMF) network elements, session management function (SMF) network elements, user plane function (UPF) network elements, policy control function (PCF) network elements, unified data management (UDM) network elements, application function (AF) network elements, etc.

[0126] AMF network elements are control plane network elements provided by the operator's network, responsible for access control and mobility management of terminal equipment accessing the operator's network, including functions such as mobility state management, allocation of temporary user identities, authentication and authorization of users.

[0127] The SMF (Service Provider Function) network element is a control plane network element provided by the operator's network, responsible for managing the Protocol Data Unit (PDU) sessions of terminal equipment. A PDU session is a channel used to transmit PDUs; terminal equipment needs to exchange PDUs with the DN (Digital Network Controller) through PDU sessions. The SMF network element is responsible for establishing, maintaining, and deleting PDU sessions. The SMF network element includes session management (such as session establishment, modification, and release, including tunnel maintenance between the UPF and RAN), UPF network element selection and control, service and session continuity (SSC) mode selection, roaming, and other session-related functions.

[0128] UPF network elements are gateways provided by operators, serving as the gateway for communication between the operator's network and the DN (Digital Network). UPF network elements include user plane-related functions such as packet routing and transmission, packet inspection, service usage reporting, Quality of Service (QoS) processing, lawful interception, uplink packet inspection, and downlink packet storage.

[0129] PCF network elements are control plane functions provided by operators to provide PDU session policies to SMF network elements. These policies can include billing-related policies, QoS-related policies, and authorization-related policies.

[0130] UDM network elements are control plane network elements provided by operators, responsible for storing information such as subscriber permanent identifiers (SUPI), security contexts, and subscription data of subscribed users in the operator's network.

[0131] AF network elements are functional network elements that provide various service functions. They can interact with the core network through other network elements and can also interact with the policy management framework for policy management.

[0132] In addition, although not shown, the CN may also include other possible network elements, such as the network exposure function (NEF) and the unified data repository (UDR) network element. The NEF network element is used to provide the framework, authentication and interface related to network capability exposure, and to transfer information between 5G system network functions and other network functions; the UDR network element is mainly used to store user-related subscription data, policy data, structured data for exposure, and application data.

[0133] IV. DN

[0134] DN, also known as packet data network (PDN), is a network located outside of the operator's network. The operator's network can access multiple DNs, and various services can be deployed on DNs to provide data and / or voice services to terminal devices.

[0135] Figure 1 In this context, Npcf, Nudm, Naf, Namf, Nsmf, N1, N2, N3, N4, and N6 are interface sequence numbers. The meanings of these interface sequence numbers can be found in the relevant standard protocols and are not limited here.

[0136] Understandable Figure 1 The example provided uses a 5G communication system, but the solutions in this embodiment can also be applied to other possible communication systems, such as the future sixth-generation (6G) communication system. The aforementioned network elements or functions can be network components in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform). Optionally, the aforementioned network elements or functions can be implemented by one device, multiple devices working together, or a functional module within a single device; this embodiment does not specifically limit this.

[0137] In the above Figure 1In the network architecture shown, terminal devices and DNs can transmit data through PDU sessions. Each PDU session can transmit multiple data streams with different QoS requirements, which are called QoS streams.

[0138] Figure 3a This is a schematic diagram of the QoS model in a 5G communication system. Figure 3a As shown, in the downlink direction, after the service data flows (SDFs) of a downlink PDU session arrive at the UPF network element, the UPF network element can use the traffic filtering template (TFT) corresponding to the PDU session to distinguish the data packets into different QoS flows. Data packets within a QoS flow are marked with a QoS flow indicator (QFI). The UPF network element transmits the data packets to the network devices on the access network side through the N3 interface. After receiving the data packets, the network devices determine the QoS flow to which the data belongs based on the QFI corresponding to the data packets. Then, based on the pre-configured QoS parameters corresponding to the QoS flow, the SDAP layer corresponding to the PDU session maps the data packets to the corresponding data radio bearer (DRB), that is, delivers the data packets to the PDCP layer entity corresponding to the DRB. The processing in the uplink direction is similar. After the upper layer of the terminal device receives the data packets, it first performs the mapping of the data packets to the QoS flow, and then delivers the data packets to the SDAP layer entity. The SDAP layer entity continues to perform the mapping of the QoS flow to the DRB, that is, delivers the data packets to the PDCP layer entity corresponding to the DRB. The mapping of uplink data packets to QoS flows and the mapping of QoS flows to DRBs can be configured by the network device sending signaling to the terminal device.

[0139] Figure 3b See the flowchart for establishing a PDU session. Figure 3b As shown, the process includes:

[0140] Step 301: The SMF network element sends a PDU session resource setup request message to the network device through the AMF network element. The PDU session resource setup request message includes the identifier of the PDU session to be established and the QoS parameters of multiple QoS flows in the PDU session, such as multiple QoS flows including QoS flow 1, QoS flow 2, QoS flow 3, QoS flow 4, and QoS flow 5.

[0141] The QoS parameters may include the 5G QoS identifier (5QI), and may also include other possible information, without limitation. 5QI is a scalar used to index the corresponding 5G QoS feature. In one example, the 5G QoS feature may include priority level, packet delay budget (PDB), etc.; here, the priority level represents the priority of the QoS flow, and the smaller the value, the higher the priority.

[0142] Step 302: The network device receives the PDU session resource establishment request and establishes a PDU session and QoS flow according to the PDU session resource establishment request.

[0143] For example, a network device may accept establishment requests for all or part of the QoS flows in the same PDU session; for instance, the network device may accept establishment requests for QoS flows 1, QoS flows 2, and QoS flows 3, but reject establishment requests for QoS flows 4 and QoS flows 5.

[0144] Step 303: The network device sends a PDU session resource establishment response message to the SMF network element through the AMF network element.

[0145] Here, the PDU session resource establishment response message may include a QoS flow failure list, which includes the identifiers of rejected QoS flows, such as the identifiers of QoS flow 4 and QoS flow 5.

[0146] As can be seen from steps 301 to 303 above, during the PDU session establishment process, network devices can reject establishment requests for some QoS streams within the PDU session. However, for multimedia services, there may be a need for synchronous transmission between data streams mapped to different QoS streams. For example, the 3D voice standard IVAS supports up to 16 channels, and synchronization between channels is required. Taking 5 channels as an example, the data streams of the 5 channels are respectively mapped to QoS stream 1, QoS stream 2, QoS stream 3, QoS stream 4, and QoS stream 5 in the same PDU session. If the network device accepts the establishment requests for QoS stream 1, QoS stream 2, and QoS stream 3, but rejects the establishment requests for QoS stream 4 and QoS stream 5, the synchronization requirement between channels cannot be met, thus affecting the user experience. Similarly, in SVC video services, the basic layer and extended layer of the same frame of video need to be synchronously sent to the receiving end for video reconstruction to obtain a clearer video presentation experience. Furthermore, for multimedia services that simultaneously contain video, audio, and text, the same frame of video, audio, and text also requires synchronous delivery to the receiving end to achieve synchronous reproduction of the three types of information. For example, services such as augmented reality, virtual reality, mixed reality, and cloud gaming also require synchronous transmission and presentation to ensure a good user experience.

[0147] Based on this, the embodiments of this application will introduce a synchronous QoS stream set, in which multiple QoS streams belonging to the same synchronous QoS stream set are associated, thereby enabling network devices to process multiple QoS streams based on the association between multiple QoS streams, which is convenient for meeting the synchronization requirements between different data streams.

[0148] The relevant technical features involved in the embodiments of this application will be explained below. It should be noted that these explanations are for the purpose of making the embodiments of this application easier to understand, and should not be regarded as a limitation on the scope of protection claimed by this application.

[0149] I. Synchronous QoS Stream Set

[0150] Synchronous QoS stream set can also be called synchronous QoS stream group or other possible names, without any specific limitation.

[0151] A synchronous QoS stream set may include multiple QoS streams, which may belong to the same PDU session or different PDU sessions. In this embodiment, the example of multiple QoS streams in a synchronous QoS stream set belonging to the same PDU session will be used for description.

[0152] When multiple QoS flows included in a synchronous QoS flow set belong to the same PDU session, in one example, a PDU session may include one synchronous QoS flow set. For instance, a PDU session may contain 10 QoS flows, of which 6 QoS flows belong to the same synchronous QoS flow set, while the other 4 QoS flows do not belong to any synchronous QoS flow set. Alternatively, a PDU session may contain 10 QoS flows, all of which belong to the same synchronous QoS flow set. In this case, the PDU session can also be called an associated session. That is, all QoS flows in an associated session belong to the same synchronous QoS flow set. In yet another example, a PDU session may include multiple synchronous QoS flow sets. For instance, a PDU session may contain 10 QoS flows, of which 6 QoS flows belong to one synchronous QoS flow set, while the other 4 QoS flows belong to another synchronous QoS flow set.

[0153] II. Related Information

[0154] The association information involved in this application embodiment may include association ID and / or association type information, wherein the association type information is used to indicate the association type (or the association type information may be directly referred to as the association type). Exemplarily, the association information may also include other possible information, which is not specifically limited.

[0155] In one example, the association information can refer to the association information corresponding to a QoS flow (i.e., the association information at the QoS flow level). In this case, the association identifier corresponding to the QoS flow can refer to the identifier of the synchronous QoS flow set to which the QoS flow belongs; multiple QoS flows belonging to the same synchronous QoS flow set have the same association identifier. The association type corresponding to the QoS flow can refer to the type of the synchronous QoS flow set to which the QoS flow belongs; multiple QoS flows belonging to the same synchronous QoS flow set have the same association type.

[0156] In another example, the association information can refer to the association information corresponding to a PDU session (i.e., PDU session-level association information), where all QoS flows in the PDU session belong to the same synchronous QoS flow set. In this case, the association identifier corresponding to the PDU session can refer to the identifier of the synchronous QoS flow set to which all QoS flows in the PDU session belong; the association type corresponding to the PDU session can refer to the type of the synchronous QoS flow set to which all QoS flows in the PDU session belong.

[0157] The types of synchronous QoS flow sets involved in the two examples above are explained below.

[0158] The type of a synchronous QoS stream set can be used to indicate the processing method (or scheduling method, transmission method, etc.) of data packets in multiple QoS streams of that synchronous QoS stream set; for example, the type of a synchronous QoS stream set can be type 1, type 2, or type 3.

[0159] The first type is used to indicate that data packets belonging to the same burst in multiple QoS flows are transmitted according to their priorities within a synchronous QoS flow set. That is, for each burst (per-burst) of data packets in multiple QoS flows, scheduling is performed according to the priorities of the multiple QoS flows. In this case, the multiple QoS flows of a synchronous QoS flow set can be mapped to different DRBs. For example, each QoS flow in a synchronous QoS flow set can occupy its own DRB and not be mapped to the same DRB as any other QoS flow; or, the multiple QoS flows of a synchronous QoS flow set can be mapped to different logical channels. For example, each QoS flow in a synchronous QoS flow set can occupy its own logical channel and not be mapped to the same logical channel as any other QoS flow. In one example, the multiple QoS flows of a synchronous QoS flow set can be mapped to different logical channels of different DRBs, or they can be mapped to different logical channels of the same DRB. In the embodiments of this application, the scheduling method corresponding to the first type can prioritize the data transmission of high-priority QoS flows.

[0160] The second type is used to indicate the transmission of data packets belonging to the same burst in multiple QoS flows according to the transmission ratio information of multiple QoS flows in a synchronous QoS flow set. That is, for each burst of data packets in multiple QoS flows, scheduling is performed according to the transmission ratio information of the multiple QoS flows. In this case, the multiple QoS flows in the synchronous QoS flow set can be mapped to different DRBs or different logical channels (the specific implementation can be the same as the first type mentioned above, and will not be repeated). The transmission ratio information of multiple QoS flows can include the data ratio of multiple QoS flows, such as the data bit rate ratio or the data packet count ratio of multiple QoS flows; or, the transmission ratio information of multiple QoS flows can include the data ratio factor of multiple QoS flows. For example, the value of the data ratio factor of each QoS flow can be an integer from 0 to 63. For example, if the synchronous QoS flow set includes three QoS flows, namely QoS flow 1, QoS flow 2, and QoS flow 3, and the data ratio factor of QoS flow 1 is 2, the data ratio factor of QoS flow 2 is 2, and the data ratio factor of QoS flow 3 is 5, then the data ratio of the multiple QoS flows is 2:2:5. In this embodiment of the application, the scheduling method corresponding to the second type can effectively ensure that different data streams of the same multimedia service arrive at the receiving end in a relatively balanced manner.

[0161] The third type is used to indicate that data packets belonging to the same burst from multiple QoS streams in a synchronous QoS stream set are transmitted in a first-in-first-service (FIFS) manner. In other words, for each burst of data packets in multiple QoS streams, scheduling is performed according to the FIFS method. In this case, multiple QoS streams in a synchronous QoS stream set can be mapped to the same DRB (which can correspond to a logical channel) or the same logical channel.

[0162] III. Cache Status Report

[0163] In 5G communication systems, logical channels can be used to carry data, and different service types of data can be carried through different logical channels. Each logical channel can be associated with a scheduling priority, which can be configured by the network device. For example, a logical channel carrying URLLC service data can be configured with a higher priority, while a logical channel carrying eMBB service data can be configured with a lower priority. When a terminal device has new data to send but no logical channels have data to send, or a higher-priority logical channel has data to send, the terminal device can trigger a buffer status report (BSR) to reflect the total amount of data to be sent on at least one logical channel, for scheduling by the network device.

[0164] Furthermore, to reduce the number of information bits transmitted over the air interface, terminal devices can report BSRs for logical channel groups (LCGs) instead of individual logical channels. The BSR reported by the terminal device for a logical channel group indicates the amount of data to be transmitted in that logical channel group. A logical channel group can include one or more logical channels. When configuring the attribute parameters (logicalChannelConfig) for each logical channel, the network device can assign a corresponding LCG ID to that logical channel. For example, if the network device assigns LCG ID LCG1 to logical channel 1, it means that logical channel 1 belongs to LCG1.

[0165] IV. Emergencies

[0166] Data packets in the same burst originate from the same frame of video and / or audio. Taking video as an example, a video can be composed of a series of consecutively played images. When 24 images are played rapidly per second, the human eye perceives it as a continuous sequence of images (i.e., video). Frame rate refers to the number of images played per second; for example, 24 frames per second means 24 images are played per second, 60 frames per second means 60 images are played per second, and so on. A burst can be understood as one video frame, corresponding to one image (i.e., a burst can include a data packet corresponding to one image). When the frame rate is 60 frames per second, the duration of one video frame is 1000ms / 60Hz, approximately 16ms. Figure 4 A diagram illustrating multiple video frames, such as Figure 4 As shown, video frame 1, video frame 2 and video frame 3 are three consecutive video frames. Taking video frame 1 as an example, video frame 1 can include multiple data packets. These multiple data packets can be distributed in the beginning of video frame 1 (for example, multiple data packets can be distributed in the first 8ms of 16ms). There can be a transmission time interval (gap) between multiple data packets in different video frames.

[0167] A single burst of data packets can be mapped to one or more QoS streams. For example, burst 1 may consist of 10 packets, with 3 packets mapped to QoS stream 1, 5 packets to QoS stream 2, and another 2 packets to QoS stream 3. Since the data packets in the same burst originate from the same frame of video and / or audio, they are typically required to be delivered synchronously to the receiver within a certain time interval.

[0168] Based on the above-mentioned technical features, the communication method provided in the embodiments of this application will be described in detail below with reference to Embodiments 1 to 6.

[0169] For example, the communication method provided in this application embodiment may include: a network device receiving indication information, which indicates that M QoS flows have a correlation relationship, and then the network device can process the M QoS flows according to the indication information. In this manner, when processing the M QoS flows, the network device considers the correlation relationship between the M QoS flows, thereby facilitating the satisfaction of synchronization requirements between different data flows.

[0170] The method in this application embodiment can be applied to a variety of possible scenarios. In different scenarios, the network device can receive the correlation information of M QoS flows from different devices, that is, different devices indicate that the M QoS flows of the network device are related. See Embodiment 1 to Embodiment 4.

[0171] Example 1

[0172] In Embodiment 1, the network device can receive correlation indication information of M QoS flows from the core network device.

[0173] Figure 5 This is a flowchart illustrating the communication method provided in Embodiment 1 of this application, as shown below. Figure 5 As shown, the method includes the following steps:

[0174] Step 501: The SMF network element sends indication information a1 to the network device through the AMF network element. Correspondingly, the network device can receive indication information a1.

[0175] The relevant technical features involved in the indication information a1 are described here.

[0176] I. Explanation of instruction information a1.

[0177] The indication information a1 is used to indicate that the M QoS flows are related, or in other words, the indication information a1 is used to indicate that the M QoS flows belong to a synchronous QoS flow set. For example, the M QoS flows include QoS flow 1, QoS flow 2, and QoS flow 3, and QoS flow 1, QoS flow 2, and QoS flow 3 all belong to the first PDU session.

[0178] In implementation method a1, the indication information a1 can include M associated information corresponding to M QoS flows respectively. For example, indication information a1 can include associated information corresponding to QoS flow 1, QoS flow 2, and QoS flow 3. In this case, after receiving indication information a1, if the network device determines that the associated information corresponding to QoS flow 1, QoS flow 2, and QoS flow 3 are the same, then it can determine that QoS flow 1, QoS flow 2, and QoS flow 3 belong to the same synchronous QoS flow set.

[0179] It should be noted that when the indication information a1 includes the association types corresponding to the M QoS flows, and the association type is the second type, the indication information a1 may also include the transmission ratio information of the M QoS flows, such as the data ratio coefficients corresponding to the M QoS flows. In other possible embodiments, the indication information a1 may not include the transmission ratio information of the M QoS flows. In this case, the transmission ratio information of the M QoS flows may be predefined by the protocol, or it may be notified to the network device through other possible means, without any specific limitation.

[0180] In implementation method a2, the indication information a1 may include the association information and / or association session indication corresponding to the first PDU session. In this case, after receiving the indication information a1, the network device can determine that the first PDU session is an association session, that is, all QoS flows (e.g., M QoS flows) in the first PDU session belong to the same synchronous QoS flow set. Among them, (1) the association session indication can be used to indicate that the first PDU session is an association session; for example, if the first PDU session corresponds to an association session indication, it means that the first PDU session is an association session, and if the first PDU session does not correspond to an association session indication, it means that the first PDU session is not an association session. Alternatively, (2) the value of the associated session indicator can be used to indicate whether the first PDU session is a PDU session. For example, if the value of the associated session indicator is a boolean, if the value of the associated session indicator corresponding to the first PDU session is true, then the first PDU session is an associated session. If the value of the associated session indicator corresponding to the first PDU session is false, then the first PDU session is not an associated session. For another example, if the value of the associated session indicator is an enumeration, if the value of the associated session indicator corresponding to the first PDU session is 1, then the first PDU session is an associated session. If the value of the associated session indicator corresponding to the first PDU session is 0, then the first PDU session is not an associated session.

[0181] It should be noted that when the indication information a1 includes the association type corresponding to the first PDU session, and the association type is the second type, the indication information a1 may also include the transmission ratio information of the M QoS streams in the first PDU session, such as the data ratio of the M QoS streams. In other possible embodiments, the indication information a1 may not include the transmission ratio information of the M QoS streams, and there is no specific limitation.

[0182] Understandably, in other possible examples, the indication information a1 can also be described in other ways. For example, one possible description is: indication information a1 is used to indicate the synchronous QoS flow set to which the QoS flow belongs. Exemplarily, indication information a1 may include at least one of the following: association identifier, association type information, and association indication. Wherein, when indication information a1 includes an association identifier, it can be understood that indication information a1 is used to indicate the identifier of the synchronous QoS flow set to which the QoS flow belongs; when indication information a1 includes association type information, it can be understood that indication information a1 is used to indicate the type of the synchronous QoS flow set to which the QoS flow belongs; when indication information a1 includes an association indication, it can be understood that indication information a1 is used to indicate that all QoS flows included in the PDU session belong to the same synchronous QoS flow set.

[0183] II. The implementation method of SMF network elements sending indication information a1 to network devices is described.

[0184] There are several ways for an SMF network element to send indication information a1 to a network device. In one possible implementation, the SMF network element can send indication information a1 to the network device via a PDU session resource establishment request message or a PDU session resource modification request message. For example, if a terminal device has downlink service reception or uplink service transmission needs, it will initiate a PDU session resource establishment request, which will trigger the SMF network element to send a PDU session resource establishment request message to the network device. The PDU session resource establishment request message can carry indication information a1. Another example is when a terminal device needs to modify the QoS flow in an established PDU session. In this case, the terminal device will initiate a PDU session resource modification request, which will trigger the SMF network element to send a PDU session resource modification request message to the network device. The PDU session resource modification request message can also carry indication information a1. Understandably, the SMF network element can also send indication information a1 to the network device via other possible messages; there are no specific limitations.

[0185] The following uses the PDU session resource establishment request message as an example to describe some possible implementations of carrying indication information a1 in the PDU session resource establishment request message.

[0186] In implementation method b1 (corresponding to implementation method a1 above), the PDU session resource establishment request message may include a QoS Flow Setup Request List, which may include one or more QoS Flow Setup Request Items corresponding to QoS flows. The QoS Flow Setup Request Items corresponding to QoS flows include QFI, QoS Flow Level QoS Parameters, and Evolved Radio Access Bearer (E-RAB) ID. In this embodiment, the QoS Flow Setup Request Items corresponding to QoS flows may also include the associated information (i.e., association identifier and / or association type) corresponding to the QoS flow. That is, information element (IE)1 and / or information element 2 may be added to the QoS Flow Setup Request Items corresponding to QoS flows, where information element 1 carries the association identifier corresponding to the QoS flow, and information element 2 carries the association type corresponding to the QoS flow.

[0187] Tables 1 to 3 below show some examples of indication information a1 carried in PDU session resource establishment request messages.

[0188] Table 1: Examples of PDU session resource establishment request messages carrying indication information a1

[0189] QoS Flow Setup Request List QoS Flow Setup Request Item >>QFI >>QoS Flow Level QoS Parameters >>E-RAB ID <![CDATA[ >>Association ID (Element 1) ]]>

[0190] As shown in Table 1, a new information element 1 can be added to the QoS flow establishment request project corresponding to the QoS flow.

[0191] Table 2: Examples of PDU session resource establishment request messages carrying indication information a1

[0192]

[0193]

[0194] As shown in Table 2, a new information element 2 can be added to the QoS flow establishment request project corresponding to the QoS flow. Furthermore, when the association type corresponding to the QoS flow is type two, another information element (e.g., information element 3) can be added to the QoS flow establishment request project to carry the data ratio coefficient of the QoS flow, as shown in Table 3.

[0195] Table 3: Examples of PDU session resource establishment request messages carrying indication information a1

[0196] QoS Flow Setup Request List QoS Flow Setup Request Item >>QoS Flow Identifier >>QoS Flow Level QoS Parameters >>E-RAB ID <![CDATA[ >>Association ID (Element 1) ]]> <![CDATA[ >>Association type(cell 2) ]]> <![CDATA[ >>Data Ratio Factor (Xinyuan 3) ]]>

[0197] It should be noted that, taking QoS flow 1 as an example, if QoS flow 1 belongs to the synchronous QoS flow set with other QoS flows, then the above-mentioned information element 1 and / or information element 2 (and information element 3) can be added to the QoS flow establishment request project corresponding to QoS flow 1; if QoS flow 1 does not belong to the synchronous QoS flow set with any other QoS flows, then the above-mentioned information element 1 and information element 2 (and information element 3) do not need to be added to the QoS flow establishment request project corresponding to QoS flow 1.

[0198] In implementation method b2 (corresponding to implementation method a2 above), the PDU session resource setup request includes a PDU session resource setup request item corresponding to the PDU session. This item may include the PDU session ID, the PDU session non-access stratum PDU (NAS-PDU), single network slice selection assistance information (S-NSSAI), and a PDU session resource setup request transfer. The PDU session resource setup request transfer may include a QoS flow setup request list. In this embodiment, the PDU session resource setup request item may further include at least one of the following: associated session indication, associated relationship identifier, and associated relationship type. That is, at least one of information element 4, information element 5, and information element 6 may be added to the PDU session resource setup request item, where information element 4 carries the associated session indication, information element 5 carries the associated relationship identifier corresponding to the PDU session, and information element 6 carries the associated relationship type corresponding to the PDU session.

[0199] Tables 4 to 6 below show some examples of indication information a1 carried in PDU session resource establishment request messages.

[0200] Table 4: Examples of PDU session resource establishment request messages carrying indication information a1

[0201] >PDU Session Resource Setup Request Item >>PDU Session ID >>PDU Session NAS-PDU >>S-NSSAI >>PDU Session Resource Setup Request Transfer <![CDATA[ >>Associated Session (Cell 4) ]]>

[0202] As shown in Table 4, information element 4 can be added to the PDU session resource establishment request project corresponding to the PDU session.

[0203] Table 5: Examples of PDU session resource establishment request messages carrying indication information a1

[0204] >PDU Session Resource Setup Request Item >>PDU Session ID >>PDU Session NAS-PDU >>S-NSSAI >>PDU Session Resource Setup Request Transfer <![CDATA[ >>Associated type (cell 6) ]]>

[0205] As shown in Table 5, information element 6 can be added to the PDU session resource establishment request project corresponding to the PDU session.

[0206] Table 6: Examples of PDU session resource establishment request messages carrying indication information a1

[0207] >PDU Session Resource Setup Request Item >>PDU Session ID >>PDU Session NAS-PDU >>S-NSSAI >>PDU Session Resource Setup Request Transfer <![CDATA[ >>Associated Session (Sentence Cell 4) ]]> <![CDATA[ >>Associated type (cell 6) ]]> <![CDATA[ >>Data Ratio(Cell 7) ]]>

[0208] As shown in Table 6, information elements 4 and 6 can be added to the PDU session resource establishment request project corresponding to the PDU session. Among them, when the association type corresponding to the PDU session is the second type, another information element (such as information element 7) can be added to the PDU session resource establishment request project corresponding to the PDU session to carry the data ratio.

[0209] Step 502: The network device performs admission control on M QoS flows according to the instruction information a1.

[0210] Here, the network device can, based on the instruction information a1, take simultaneous acceptance or simultaneous rejection control measures for QoS flows belonging to the same synchronous QoS flow set.

[0211] For example, if the PDU session resource establishment request message carries indication information a1, the network device can, based on indication information a1, simultaneously accept establishment requests for all QoS flows in the synchronous QoS flow set, or simultaneously reject establishment requests for all QoS flows in the synchronous QoS flow set. For instance, if the synchronous QoS flow set includes QoS flow 1, QoS flow 2, and QoS flow 3, the network device can establish QoS flow 1, QoS flow 2, and QoS flow 3, or it can choose not to establish QoS flow 1, QoS flow 2, and QoS flow 3; that is, the network device will not establish only one or two of QoS flow 1, QoS flow 2, and QoS flow 3. Similarly, if the PDU session resource modification request message carries indication information a1, the network device can, based on indication information a1, simultaneously accept modification requests for all QoS flows in the synchronous QoS flow set, or simultaneously reject modification requests for all QoS flows in the synchronous QoS flow set. For example, if the synchronous QoS flow set includes QoS flow 1, QoS flow 2, and QoS flow 3, then the network device can modify QoS flow 1, QoS flow 2, and QoS flow 3, or it can choose not to modify QoS flow 1, QoS flow 2, and QoS flow 3; that is, the network device will not modify only one or two of QoS flow 1, QoS flow 2, and QoS flow 3.

[0212] For example, taking the network device accepting the establishment request of all QoS flows in a synchronous QoS flow set as an example, the network device can also configure air interface resources for all QoS flows in the synchronous QoS flow set. For instance, in one example (referred to as Example 1), the network device can map different QoS flows of the same synchronous QoS flow set to different DRBs or different logical channels. In another example (referred to as Example 2), the network device can map different QoS flows of the same synchronous QoS flow set to the same DRB (which can correspond to a logical channel) or the same logical channel. It should be noted that if the indication information a1 includes an association type, Example 1 can be used when the association type is the first type or the second type, and Example 2 can be used when the association type is the third type.

[0213] For example, in connection with Example 1 above, the network device can also configure the different logical channels mapped to different QoS flows of the synchronous QoS flow set to different logical channel groups (e.g., each logical channel group includes one logical channel), or define a new BSR format for each logical channel, so that after the terminal device reports the BSR, the network device can determine the amount of uplink data to be transmitted for each QoS flow in the same synchronous QoS flow set, so as to achieve differentiated scheduling.

[0214] In this embodiment, the network device can use various criteria to control the admission of M QoS flows. As one implementation, the network device can determine whether to admit M QoS flows based on information such as the current serving cell of the terminal device and the network device's load. Furthermore, the network device can also consider whether the QoS requirements of the M QoS flows can be met by configuring more serving cells or adding secondary base stations, based on information such as the terminal device's capabilities and coverage, and thus determine whether to admit the M QoS flows. In this case, the network device's admission control process may trigger the configuration of secondary carriers and / or secondary base stations for the terminal device. The process of configuring secondary carriers and / or secondary base stations for the terminal device can refer to existing solutions and will not be elaborated here.

[0215] It should be noted that the synchronous QoS stream sets, QoS streams, and DRBs or logical channels involved in steps 501 and 502 above can be applied to both uplink and downlink directions simultaneously, unless otherwise specified. However, in specific implementations, they can be applied only to uplink, only to downlink, or to both uplink and downlink directions simultaneously.

[0216] Step 503: The network device sends a response message to the SMF network element through the AMF network element.

[0217] In one example, if in step 501 above, the SMF network element sends indication information a1 to the network device via a PDU session resource setup request message, then the response message here can be a PDU session resource setup response message. The PDU session resource setup response message may include a QoS flow setup failure list, which includes identifiers of QoS flows rejected by the network device; or, the PDU session resource setup response message may include identifiers of synchronous QoS flow sets rejected by the network device.

[0218] In another example, if in step 501 above, the SMF network element sends indication information a1 to the network device via a PDU session resource modification request message, then the response message here can be a PDU session resource modification response message. The PDU session resource modification response message may include a QoS flow modification failure list, which includes identifiers of QoS flows that were refused modification by the network device; or, the PDU session resource modification response message may include identifiers of synchronous QoS flow sets that were refused modification by the network device.

[0219] Step 504: The network device sends instruction information a2 to the terminal device; correspondingly, the terminal device receives instruction information a2.

[0220] For example, the instruction information a2 may include instruction information a2' and / or instruction information a2".

[0221] Wherein, (1) the indication information a2' is used to indicate that M QoS flows have an association relationship. For example, the SMF network element can send a PDU session establishment accept message or a PDU session modification accept message to the terminal device through the AMF network element and network device. The PDU session establishment accept message or the PDU session modification accept message can contain the configuration information of M QoS flows, such as the TFT, QoS parameters, etc. corresponding to each QoS flow. Optionally, the PDU session establishment accept message or the PDU session modification accept message can also include the indication information a2'. The way the PDU session establishment accept message or the PDU session modification accept message includes the indication information a2' can be adapted to the description of the indication information a1 above. For example, the configuration information of each QoS flow can include the association relationship identifier and / or association relationship type corresponding to the QoS flow.

[0222] For example, the PDU session establishment accept message or the PDU session modification accept message is a non-access stratum message. The AMF network element and the network device are used to transparently transmit the PDU session establishment accept message or the PDU session modification accept message. In this embodiment, this transparent transmission behavior can also be referred to as: the AMF network element or the network device sends the PDU session establishment accept message or the PDU session modification accept message to the terminal device.

[0223] (2) The indication information a2” is used to indicate that the DRBs or LCHs corresponding to the M QoS flows have an association relationship. For example, the network device can send an RRC reconfiguration message to the terminal device. The RRC reconfiguration message may include the configuration information of one or more DRBs or LCHs, as well as the mapping relationship between the M QoS flows and the DRBs and LCHs. Optionally, the RRC reconfiguration message may also include the indication information a2”. In one example, the indication information a2” indicates the implementation of the association relationship between the DRBs or LCHs corresponding to the M QoS flows, which can be adapted to the description of the indication information a1 above; for example, the M QoS flows correspond to the M DRBs, and the configuration information of each DRB in the M DRBs may include the association relationship identifier and / or association relationship type corresponding to that DRB.

[0224] Step 505: The terminal device sends a response message to the network device.

[0225] For example, in step 504 above, the network device sends indication information a2” to the terminal device through the RRC reconfiguration message. Then the response message here can be the RRC reconfiguration complete message.

[0226] Step 506: The network device processes data packets (involving downlink transmission) in the M QoS streams according to the instruction information a1.

[0227] For example, a network device can determine the burst to which data packets in M ​​QoS flows belong, and then process the data packets belonging to the first burst in the M QoS flows; and after processing the data packets belonging to the first burst, it processes the data packets belonging to the second burst in the M QoS flows. In other words, for multiple QoS flows in a synchronous QoS flow, the network device can sequentially process data packets belonging to different bursts in multiple QoS flows; when processing data packets in the M QoS flows, the network device processes them in bursts, without crossing bursts. For example, the air interface transmission of one burst can only begin after the air interface transmission of the next burst has ended. This approach facilitates the synchronous arrival of data packets from the same burst at the receiving end within a certain time interval, effectively avoiding the problem of large delays (i.e., asynchrony) in the arrival of data packets from the same burst at the receiving end caused by transmitting part of the data packets from the first burst, then part of the data packets from the second burst, and then the remaining data packets from the first burst.

[0228] I. A description of the method by which network devices determine the burst to which data packets in M ​​QoS flows belong.

[0229] In this embodiment of the application, the network device can determine the burst to which the data packets in the M QoS flows belong in various ways. Several possible implementation methods are described below.

[0230] In implementation c1, the network device can determine the burst to which a data packet belongs in one of the M QoS flows based on the burst identifier information of the data packets in the M QoS flows. For example, the N3GTP-U header of the data packet (GTP-U is one of the protocols of General Packet Radio Service (GPRS) Tunnel Protocol) can carry burst identifier information, which indicates the burst to which the data packet belongs. For instance, the N3GTP-U header can include a 2-bit field, where four different values ​​represent different bursts; for example, a value of 00 in the N3GTP-U header indicates that the data packet belongs to burst 1, a value of 01 indicates burst 2, a value of 10 indicates burst 3, and a value of 11 indicates burst 4. Furthermore, after receiving two consecutive data packets from the M QoS flows in the N3 tunnel, the network device can determine whether the two consecutive data packets belong to the same burst by reading the values ​​of the aforementioned fields in the N3GTP-U header of these two consecutive data packets.

[0231] In implementation c2, the network device can determine the burst to which data packets in the M QoS flows belong based on the packet payload information. For example, the packet payload information can refer to the entire payload or a portion of the payload information; for instance, after receiving two consecutive data packets from the M QoS flows from the N3 tunnel, the network device can compare whether the 41st bit of the payload of these two consecutive data packets is the same. If they are the same, then the two consecutive data packets belong to the same burst; if they are different, then the two consecutive data packets belong to different bursts.

[0232] In implementation c3, the network device can determine the burst to which data packets in M ​​QoS flows belong based on the distinguishing identifier between different bursts. For example, the distinguishing identifier between different bursts can be a special data packet, which can be the end mark of the burst; for instance, after receiving the special data packet from the N3 tunnel, the network device can determine that at least one data packet transmitted before this special data packet belongs to burst 1, and at least one data packet transmitted before this special data packet belongs to burst 2. For example, this special data packet can be added by the UPF network element after identifying the burst boundary, or it can be added by the application server; the specific method is not limited.

[0233] Implementation method c4 allows network devices to adjust the transmission time intervals based on different bursts of data packets (see [link]). Figure 4 As shown in the diagram, determine the burst to which the data packets in the M QoS flows belong. The transmission time interval can be predefined by the protocol, or it can be indicated to the network device by the core network device or the terminal device; there is no specific limitation.

[0234] It should be noted that the specific implementation method (c1 through c4) used can be determined by the core network, network management system, application server, or terminal device notifying the network device, or it can be predefined by the protocol. Understandably, the burst identification methods described above can be implemented independently.

[0235] II. A description of how network devices handle data packets belonging to the first burst among M QoS flows.

[0236] In this embodiment of the application, the network device processing data packets belonging to the first burst in M ​​QoS streams may include: the network device transmitting data packets belonging to the first burst in M ​​QoS streams to the terminal device, and / or, the network device discarding data packets belonging to the first burst in M ​​QoS streams that have not yet been transmitted.

[0237] (1) There are several ways for a network device to transmit data packets belonging to the first burst in M ​​QoS streams. Here are some possible implementation methods: Implementation method d1: The network device transmits data packets belonging to the first burst in M ​​QoS streams according to the priority of M QoS streams; Implementation method d2: The network device transmits data packets belonging to the first burst in M ​​QoS streams according to the transmission ratio information of M QoS streams; Implementation method d3: The network device transmits data packets belonging to the first burst in M ​​QoS streams according to the first-in-first-out service method.

[0238] It should be noted that if the indication information a1 includes the relationship type, then when the relationship type is the first type, the above implementation method d1 can be used; when the relationship type is the second type, the above implementation method d2 can be used; and when the relationship type is the third type, the above implementation method d3 can be used.

[0239] (2) The network device discarding data packets belonging to the first burst in M ​​QoS flows that have not yet been transmitted can mean that the network device determines that the final time limit for the air interface transmission of the first burst has arrived, and therefore discards data packets belonging to the first burst in M ​​QoS flows that have not yet been transmitted to the terminal device. Alternatively, the network device determines that data packets belonging to the first burst exceed the transmission delay requirement, and therefore discards data packets belonging to the first burst in M ​​QoS flows that have not yet been transmitted to the terminal device. For example, the network device can determine whether the data exceeds the transmission delay requirement based on the PDB and / or frame spread delay (FSD) of the data packet. Here, PDB defines the upper limit of the delay for data packet transmission between the terminal device and the UPF network element, and the value of PDB can be the same in uplink and downlink. FSD represents the maximum acceptable delay for other data packets in the same burst to arrive at the receiving end after the first data packet of the same burst arrives at the receiving end; the network device can obtain the FSD of the PDU session or QoS flow from the core network device or the terminal device, for example, the PDU session resource establishment request message sent by the SMF network element or AMF network element to the network device may include the FSD of the PDU session or QoS flow. Understandably, since network devices consider the FSD of the air interface segment when determining whether each burst of data packets exceeds the transmission latency requirement, the FSD used by network devices to determine whether each burst of data packets exceeds the transmission latency requirement can be less than the FSD specified at the application layer.

[0240] As can be seen from the above, the end of the first burst of air interface transmission mentioned above can mean that all data packets of the first burst have been transmitted in the air interface, or that the final time limit for the first burst of air interface transmission has been reached.

[0241] It should be noted that: (1) The above description is based on the example of a network device processing data packets belonging to the first burst in M ​​QoS streams. The network device can use the same method to process data packets belonging to other bursts (such as the second burst) in M ​​QoS streams. (2) In other possible embodiments, if the network device determines that the final time limit for the air interface transmission of the first burst has arrived or the data packets belonging to the first burst have exceeded the transmission delay requirement, it may not discard the data packets belonging to the first burst in the M QoS streams that have not yet been transmitted. For example, its priority can be reduced to participate in subsequent air interface transmission.

[0242] Regarding step 506 above, in other possible embodiments, the network device processes data packets in the M QoS flows according to the instruction information a1. This can also mean: the network device transmits and / or discards data packets in the M QoS flows according to their priority; or, the network device transmits and / or discards data packets in the M QoS flows according to their transmission ratio information; or, the network device transmits data packets in the M QoS flows in a first-in, first-out (FIFO) manner. The difference between this processing method and the method described above is that the processing method described above processes data in bursts, while this processing method may not consider bursts. Other than this difference, please refer to the description above.

[0243] Step 507: The terminal device processes data packets (involving uplink transmission) in the M QoS streams according to the instruction information a2.

[0244] For example, the specific implementation of the terminal device processing data packets in M ​​QoS streams can be adapted to the description of the network device processing data packets in M ​​QoS streams. The difference lies in that the terminal device needs to receive uplink grants from the network device, and then schedule the data packets of the M QoS streams for transmission over the air interface according to the indication information a2. For example, the terminal device can transmit data packets belonging to the first burst of the M QoS streams on the resources indicated by the uplink grant according to the priority of the M QoS streams; or, the terminal device can transmit data packets belonging to the first burst of the M QoS streams on the resources indicated by the uplink grant according to the transmission ratio information of the M QoS streams; or, the terminal device can transmit data packets belonging to the first burst of the M QoS streams on the resources indicated by the uplink grant in a first-in, first-out (FIFO) manner.

[0245] It should be noted that: (1) The "scheduling" of the terminal device can refer to the redistribution of the uplink resources allocated to the terminal device among different logical channels. From the perspective of the terminal device, when the terminal device receives a block of uplink resources that can be used for data transmission (which can be dynamically scheduled or pre-configured scheduled resources), if inappropriate data is placed on the uplink resources (or the data is placed on inappropriate resources), it may lead to the inability to meet the data demand or reduce the efficiency of the communication system. Therefore, in order to place the appropriate data on the appropriate resources, the terminal device can select the data in the appropriate logical channel for the uplink resources. For example, the "the terminal device transmits the data packets belonging to the first burst of M QoS streams on the uplink resources according to the priority of M QoS streams" described above is a scheduling method of the terminal device. In addition, the relevant implementation of this process can be found in the logical channel prioritization process in 3GPP TS38.321v15.4.0.

[0246] (2) The specific burst identification method used by the terminal device can be indicated by a higher layer (such as the application layer) or the core network device. The higher layer indication can be via control plane signaling to notify the burst identification method, or it can be that for each uplink data packet, when the higher layer delivers it to the access layer, the corresponding indication information indicates whether the data packet belongs to the same burst as the previous data packet. The burst identification method indicated by the core network device can be found in the description on the network device side.

[0247] Furthermore, in this embodiment, (1) if the network device configures the different logical channels mapped to the M QoS flows to be configured into different logical channel groups, the terminal device can report a BSR for each logical channel group; if the network device defines a new BSR format for each logical channel, the terminal device can report a BSR using the new BSR format for each logical channel mapped to the M QoS flows. It should be noted that the terminal device can report BSR in bursts, thereby enabling the network device to schedule the data packets of the M QoS flows to be transmitted over the air interface according to the priority or data rate information of the QoS flows for each burst. Alternatively, (2) if the network device configures the different logical channels mapped to the M QoS flows to be configured into the same logical channel group, the terminal device can report a BSR for that logical channel group.

[0248] For example, the BSR reported by the terminal device may include information such as the association identifier, the association type, or the identifier of the PDU session to which the M QoS flows belong.

[0249] It should be noted that the process described in steps 501 to 507 above is only one possible example. In specific implementations, adaptive adjustments can be made based on the process described above. For example, the network device can perform admission control on M QoS flows according to the indication information a1, instead of processing the data packets in the M QoS flows according to the indication information a1. In this case, the implementation of the network device processing the data packets in the M QoS flows can refer to existing technologies. As another example, the network device can process the data packets in the M QoS flows according to the indication information a1, instead of performing admission control on the M QoS flows according to the indication information a1. In this case, the implementation of the network device performing admission control on the M QoS flows can refer to existing technologies.

[0250] As described in Embodiment 1 above, the network device can receive indication information a1 from the core network device, and then perform admission control and / or process data packets in the M QoS flows according to the indication information a1, thereby facilitating the satisfaction of synchronization requirements between different data flows. For example, in the example described above, if the IVAS supports 5 channels, and the data flows of the 5 channels are respectively mapped to QoS flows 1, QoS flows 2, QoS flows 3, QoS flows 4, and QoS flows 5 in the same PDU session, then using the method in this embodiment, QoS flows 1, QoS flows 2, QoS flows 3, QoS flows 4, and QoS flows 5 can be set to have an association relationship. Therefore, the network device can simultaneously accept QoS flows 1, QoS flows 2, QoS flows 3, QoS flows 4, and QoS flows 5, avoiding accepting only a portion of the QoS flows, thus facilitating the satisfaction of synchronization requirements between different channels and improving user experience. Furthermore, for multimedia services that simultaneously contain video, audio, and text, the method in this embodiment can effectively avoid network problems that affect user experience, such as having video but no sound.

[0251] Furthermore, by mapping different QoS flows in the synchronous QoS set to different DRBs or logical channels, differentiated air interface scheduling can be achieved, prioritizing the data transmission of high-priority QoS flows. By performing air interface scheduling on a burst basis and introducing frame spread delay, cross-frame delay accumulation can be effectively avoided, ensuring a superior service experience.

[0252] Example 2

[0253] In Embodiment 2, the method described in this application embodiment will be applied to a dual-connection scenario as an example.

[0254] In a dual-connectivity scenario, a terminal device can connect to two network devices simultaneously. One network device is the primary network device, and the other is the secondary network device. In this case, the primary network device can receive correlation indications for M QoS flows from the core network device, and the secondary network device can receive correlation indications for M QoS flows from the primary network device.

[0255] Figure 6 This is a flowchart illustrating the communication method provided in Embodiment 2 of this application, as shown below. Figure 6 As shown, the method includes the following steps:

[0256] In step 601, the SMF network element sends indication information b1 to the main network device through the AMF network element. Correspondingly, the main network device can receive indication information b1.

[0257] For example, indication information b1 is used to indicate that M QoS flows are associated. The specific implementation of indication information b1 can refer to indication information a1 in Embodiment 1.

[0258] In step 602, the primary network device sends indication information b2 to the secondary network device. Accordingly, the secondary network device can receive indication information b2.

[0259] For example, taking the aforementioned indication information b1 carried in a PDU session resource establishment request message or a PDU session resource modification request message as an example, after the primary network device receives the PDU session resource establishment request message or the PDU session resource modification request message, based on the PDU session configuration information and indication information b1 therein, if it determines that it cannot accept a secondary network device but there is a secondary network device that can provide services and that the secondary network device may accept it, or if it can accept it but wants to inquire whether the secondary network device can accept it based on considerations such as load balancing, the primary network device can trigger the secondary base station addition process, that is, send a secondary base station addition request message to the secondary network device. The secondary base station addition request message may include the PDU session configuration information and indication information b2. Among them, the functions and implementations of indication information b2 and indication information b1 can be the same.

[0260] It should be noted that the above description is based on the example of the primary network device triggering the secondary base station addition process. In other possible embodiments, if the terminal device has already been configured with a secondary network device, the primary network device can also trigger the secondary base station modification process, that is, send a secondary base station modification request (S-node modification request) message to the secondary network device. The secondary base station modification request message may include the configuration information and indication information b2 of the PDU session.

[0261] Understandably, the instruction information b2 can be carried in a secondary base station add request message or a secondary base station modify request message, or it can be carried in other possible messages, without any specific limitation.

[0262] Step 603: The auxiliary network device performs admission control on M QoS flows according to the instruction information b2.

[0263] Here, the implementation of the secondary network device in accepting M QoS flows according to the instruction information b2 can be referred to step 502 in Embodiment 1, and will not be described in detail here.

[0264] In step 604, the secondary network device sends a response message to the primary network device. Correspondingly, the primary network device receives the response message.

[0265] Here, the response message may include information on whether each QoS flow is accepted. For example, the response message may include the identifier of the QoS flow rejected by the secondary network device or the identifier of the set of synchronous QoS flows rejected by the secondary network device.

[0266] For example, if in step 602 above, the primary network device sends indication information b2 to the secondary network device via a secondary base station addition request message, then the response message here can be a secondary base station addition request acknowledgement (S-node addition request acknowledgement) message. If in step 602 above, the primary network device sends indication information b2 to the secondary network device via a secondary base station modification request message, then the response message here can be a secondary base station modification request acknowledgement (S-node modification request acknowledgement) message.

[0267] Step 605: The main network device sends instruction information b3 to the terminal device.

[0268] For example, the instruction information b3 may include instruction information b3' and / or instruction information b3".

[0269] Wherein, (1) the indication information b3' is used to indicate that M QoS flows have an association relationship. For example, the SMF network element can send a PDU session establishment acceptance message or a PDU session modification acceptance message to the terminal device through the AMF network element and the main network device. The PDU session establishment acceptance message or the PDU session modification acceptance message carries the indication information b3'. The way in which the PDU session establishment acceptance message or the PDU session modification acceptance message carries the indication information b3' can be seen from a2' in Embodiment 1.

[0270] (2) The indication information b3” is used to indicate that the DRBs or LCHs corresponding to the M QoS flows have an association relationship. For example, the primary network device can obtain the configuration information of the secondary base station, and then send the secondary base station configuration information to the terminal device through the RRC reconfiguration message. The secondary base station configuration information may include the configuration information of one or more DRBs or LCHs, as well as the mapping relationship between the M QoS flows and the DRBs and LCHs. The implementation of the indication information b3” indicating that the DRBs or LCHs corresponding to the M QoS flows have an association relationship can be found in a3 in Embodiment 1.

[0271] Step 606: The terminal device sends a response message to the main network device.

[0272] For example, in step 605 above, the main network device sends indication information b3” to the terminal device through the RRC reconfiguration message. Then the response message b1 here can be the RRC reconfiguration completed message.

[0273] Step 607: The main network device sends a response message to the SMF network element through the AMF network element.

[0274] In one example, if in step 601 above, the SMF network element sends indication information b1 to the network device via a PDU session resource establishment request message, then the response message b2 here can be a PDU session resource establishment response message. The PDU session resource establishment response message may include a QoS flow establishment failure list, which includes the identifiers of QoS flows that were refused to be established by the secondary network device; or, the PDU session resource establishment response message may include the identifiers of the synchronization QoS flow sets that were refused to be established by the secondary network device.

[0275] In another example, if in step 601 above, the SMF network element sends indication information b1 to the network device via a PDU session resource modification request message, then the response message b2 here can be a PDU session resource modification response message. The PDU session resource modification response message may include a QoS flow modification failure list, which includes the identifiers of the QoS flows that the secondary network device refused to modify; or, the PDU session resource modification response message may include the identifiers of the synchronization QoS flow sets that the secondary network device refused to modify.

[0276] Step 608: The auxiliary network device processes data packets (involving downlink transmission) in M ​​QoS streams according to the instruction information b2.

[0277] Here, if the primary network device triggers the secondary base station addition process in step 602 above, the process of the terminal device accessing the secondary network device may also be included before step 608. For example, the terminal device can access the secondary network device according to the dedicated preamble and / or physical random access channel (PRACH) resources configured by the secondary network device.

[0278] For example, the specific implementation of step 608 can be found in step 506 of embodiment one.

[0279] Step 609: The terminal device processes data packets (involving uplink transmission) in M ​​QoS streams according to the instruction information b3.

[0280] For example, the specific implementation of step 609 can be found in step 507 of embodiment one.

[0281] As can be seen from the above embodiment 2, after the main network device determines that M QoS flows have a correlation relationship based on the message sent by the core network device, it can indicate to the auxiliary network device that the M QoS flows have a correlation relationship. This allows the auxiliary network device to perform admission control and / or process data packets in the M QoS flows based on the correlation relationship between the M QoS flows, which facilitates the synchronization requirements between different data flows.

[0282] Example 3

[0283] In Embodiment 3, the method described in this application embodiment will be used as an example of a switching scenario.

[0284] For example, the handover scenario can include a variety of possible handover situations, such as situation 1, where the terminal device switches from one cell of a network device to another cell of the network device; and situation 2, where the terminal device switches from a cell of a first network device to a cell of a second network device. In situation 2, the first network device can be the source network device, and the second network device can be the target network device. The source network device and the target network device can be network devices under the same AMF network element, or they can be network devices under different AMF network elements.

[0285] In scenario 1, the network device can receive correlation indication information for M QoS flows from the core network device; in scenario 2, the source network device can receive correlation indication information for M QoS flows from the core network device, and the target network device can receive correlation indication information for M QoS flows from the source network device. Scenario 2 will be described below.

[0286] Figure 7This is a flowchart illustrating the communication method provided in Embodiment 3 of this application, as shown below. Figure 7 As shown, the method includes the following steps:

[0287] Step 701: The SMF network element sends indication information c1 to the source network device through the AMF network element. Correspondingly, the source network device can receive indication information c1.

[0288] For example, indication information c1 is used to indicate that M QoS flows are associated. The specific implementation of indication information c1 can refer to indication information a1 in Embodiment 1.

[0289] Step 702, Source network device indication information c1, processes M QoS flows.

[0290] For example, the source network device can perform admission control on M QoS flows according to the indication information c1, and / or process data packets in the M QoS flows according to the indication information c1. For a specific implementation, please refer to the description in Embodiment 1 above.

[0291] In step 703, the source network device sends a handover request message to the target network device. Correspondingly, the target network device can receive the handover request message.

[0292] For example, after the source network device determines that the terminal device needs to switch to the target network device, it can send a handover request message to the target network device. The handover request message includes configuration information for M QoS flows and indication information c2. The functions and implementations of indication information c2 and indication information c1 can be the same.

[0293] Step 704: The target network device performs admission control on M QoS flows according to the instruction information c2.

[0294] Here, the implementation of the target network device's admission control of M QoS flows according to the instruction information c2 can be referred to step 502 in Embodiment 1, and will not be repeated here.

[0295] In step 705, the target network device sends a handover request acknowledgement message to the source network device. Correspondingly, the master network device receives the handover request acknowledgement message.

[0296] Here, the handover request confirmation message may include information on whether each QoS flow is accepted. For example, the handover request confirmation message may include the identifier of the QoS flow rejected by the target network device or the identifier of the set of synchronous QoS flows rejected by the target network device.

[0297] Step 706: The source network device sends an RRC reconfiguration message containing a handover command to the terminal device. Correspondingly, the terminal device receives the RRC reconfiguration message and performs the appropriate configuration based on it.

[0298] Here, the switching command may include configuration information for one or more DRBs or LCHs, as well as the mapping relationships between M QoS flows and DRBs and LCHs. Optionally, the switching command may also include indication information c3, which indicates that the DRBs or LCHs corresponding to the M QoS flows are associated.

[0299] Step 707: The target network device processes data packets (involving downlink transmission) in M ​​QoS streams according to the instruction information c2.

[0300] For example, the specific implementation of step 707 can be found in step 506 of embodiment one.

[0301] It should be noted that, prior to step 707, a process for the terminal device to access the target network device may also be included.

[0302] Step 708: The terminal device processes data packets (involving uplink transmission) in M ​​QoS streams according to the instruction information c3.

[0303] For example, the specific implementation of step 708 can be found in step 507 of embodiment one.

[0304] It should be noted that the process described in steps 701 to 708 above only illustrates some possible steps. In actual implementation, other possible steps may also be included.

[0305] As can be seen from the content of Embodiment 3 above, after the source network device determines that the M QoS flows are related based on the message sent by the core network device, it can indicate to the target network device that the M QoS flows are related. This allows the target network device to perform admission control and / or process the data packets in the M QoS flows based on the relationship between the M QoS flows, which facilitates the synchronization requirements between different data flows.

[0306] Example 4

[0307] The above embodiments one to three describe methods for a network device to obtain correlation indication information of M QoS flows in different scenarios. It should be noted that in the scenarios described in embodiments one to three, the network device can also obtain correlation indication information of M QoS flows in other ways. For example, the network device can also obtain correlation indication information of M QoS flows in other ways from a terminal device.

[0308] For example, the communication method provided in Embodiment 4 of this application may include: a terminal device sending indication information d1 to a network device, such as indication information d1 indicating that M QoS flows have an association relationship. Correspondingly, the network device receives indication information d1 and then processes the M QoS flows according to indication information d1. The network device here may be the network device in Embodiment 1, or it may be the primary or secondary network device in Embodiment 2, or it may be the source or target network device in Embodiment 3.

[0309] In one example, the terminal device can send indication information d1 to the network device via a UE assistance INFO message. Indication information d1 may include at least one of the following:

[0310] (1) The identifier of one or more PDU sessions (or associated sessions) indicating that all QoS flows included in each PDU session belong to the same synchronous QoS flow set. For example, the identifier of one or more PDU sessions includes the identifier of the first PDU session, which includes M QoS flows.

[0311] (2) Multiple QoS flow identifiers (QFIs) indicate that multiple QoS flows are related. For example, multiple QoS flows are M QoS flows.

[0312] (3) The identifier of the logical channel corresponding to multiple QoS flows indicates that the logical channels corresponding to multiple QoS flows are related, which can implicitly indicate that multiple QoS flows are related.

[0313] (4) The identifier of DRBs corresponding to multiple QoS flows indicates that the DRBs corresponding to multiple QoS flows are related, which can implicitly indicate that multiple QoS flows are related.

[0314] (5) Multiple TFTs, each of which is associated with a QoS stream matched to a specific TFT; where each TFT can correspond to a QoS stream for filtering that QoS stream. For example, there are M TFTs, and the M TFTs correspond to M QoS streams.

[0315] (6) Synchronization indication information, which may include at least one of the following: association identifier, association type, and association indication.

[0316] For example, the indication information d1 may include {PDU session identifier + multiple QFIs}, indicating that multiple specified QoS flows within the PDU session belong to the same synchronous QoS flow set.

[0317] For another example, the indication information d1 may include {synchronization indication information + identifiers of one or more PDU sessions}, indicating that all QoS flows included in each PDU session belong to the same synchronous QoS flow set.

[0318] For another example, the indication information d1 may include {one or more {PDU session IDs + multiple QFIs}}, indicating that a specified QoS flow within one or more PDU sessions belongs to the same synchronous QoS flow set.

[0319] It should be noted that: (1) When the indication information d1 includes the above (3) and / or (4), this method can be applied to the scenario where the PDU session has been established. In this case, the network device can process the data packets in the M QoS streams according to the indication information d1, instead of performing admission control on the M QoS streams according to the indication information d1.

[0320] (2) When the indication information d1 includes at least one of (1), (2), (5), and (6) above, the terminal device can send a non-access stratum message (the non-access stratum message includes the indication information d1) to the network device. The network device then sends the non-access stratum message to the core network device (such as an AMF or SMF network element). The core network device can then determine that the M QoS flows are associated based on the indication information d1 and can indicate the association between the M QoS flows to the network device through the PDU session establishment or modification process. In this case, the terminal device can determine that the M QoS flows are associated based on the application layer message sent by the application server and then send a non-access stratum message to the network device.

[0321] In the above embodiments one to four, the network device (such as the network device in embodiment one, or the main network device or auxiliary network device in embodiment two, or the source network device or target network device in embodiment three) is described as a whole device. In some possible cases, the network device may also include separate nodes, for example, see Figure 2b and Figure 2c .

[0322] The following will be based on the above. Figure 2b and Figure 2c The network device shown is described in conjunction with Embodiments 5 and 6, illustrating the interactions between different nodes included in the network device.

[0323] Example 5

[0324] In Example 5, a network device will be used as the example. Figure 2b Taking the network device shown (i.e., the network device may include CU and DU) as an example, one possible implementation is described.

[0325] Figure 8 This is a flowchart illustrating the communication method provided in Embodiment 5 of this application, as shown below. Figure 8 As shown, the method includes the following steps:

[0326] Step 801, CU receives indication information e1.

[0327] Here, the indication information e1 can be used to indicate that M QoS flows are associated. There are multiple ways for the CU to receive the indication information e1. For example, the CU can receive the indication information e1 from the SMF network element or the AMF network element. For specific implementation, please refer to the relevant description of the network device receiving the indication information a1 in the above embodiment 1.

[0328] Step 802: The CU performs admission control on the M QoS flows according to the instruction information e1.

[0329] Here, the CU can, based on the indication information e1, take simultaneous admission control measures for QoS flows belonging to the same synchronous QoS flow set, either accepting or rejecting them simultaneously.

[0330] In step 803, the CU sends indication information e2 to the DU. Correspondingly, the DU can receive indication information e2.

[0331] For example, the CU can determine the DRB or LCH corresponding to M QoS flows and send indication information e2 to the DU. The indication information e2 is used to indicate that the DRB or LCH corresponding to the M QoS flows have an association relationship. In one example, the indication information e2 may include at least one of the following: association relationship identifier, association relationship type, and association relationship indication.

[0332] As an alternative, the CU can indicate the synchronous QoS set to which each of the M QoS flows belongs in the DRB configuration, instead of directly indicating the correlation between the DRBs corresponding to the M QoS flows. In this way, the DU can determine the correlation between DRBs based on the correlation between QoS flows.

[0333] Step 804: The CU sends M data packets from the QoS stream to the DU.

[0334] For example, after the CU receives data packets from M QoS flows from the UPF network element, it can send the data packets from the M QoS flows to the DU. Furthermore, the CU can also indicate to the DU the burst to which the data packets in the M QoS flows belong. For example, the CU can indicate to the DU the burst to which the data packets belong through the F1GTP-U header of the data packets. That is, the F1GTP-U header of the data packets can include burst identification information. For example, the F1GTP-U header can include a 2-bit field, and the four different values ​​of this field represent different bursts.

[0335] In other possible embodiments, the DU can also determine the burst to which the data packets in the M QoS flows belong based on the packet payload information (see implementation c2 above), the distinguishing identifier between different bursts (see implementation c3 above), or the transmission time interval of data packets in different bursts (see implementation c4 above). For example, the CU can indicate to the DU which burst identification method to use, and then the DU determines the burst to which the data packets in the M QoS flows belong based on the burst identification method indicated by the CU; alternatively, the burst identification method can be predefined by the protocol.

[0336] Step 805: DU processes data packets in M ​​QoS streams according to instruction information e2.

[0337] For example, DU can process data packets belonging to the first burst in the M QoS flows according to the burst to which the data packets in the M QoS flows belong; and after processing the data packets belonging to the first burst, it can process the data packets belonging to the second burst in the M QoS flows.

[0338] The DU's processing of data packets belonging to the first burst in M ​​QoS flows may include: the DU transmitting data packets belonging to the first burst in M ​​QoS flows to the terminal device. For specific implementation, please refer to the description in Embodiment 1 of the network device transmitting data packets belonging to the first burst in M ​​QoS flows to the terminal device.

[0339] Optionally, the DU's processing of data packets belonging to the first burst in the M QoS flows may further include: the DU sending drop indication information for the corresponding DRB or logical channel to the CU, the drop indication information including the identifier information of the first burst; correspondingly, after receiving the drop indication information, the CU can drop data packets belonging to the first burst in the corresponding DRB or logical channel that have not yet been transmitted to the terminal device. Here, the DRB or logical channel corresponding to the drop indication information can be understood as the DRB or logical channel corresponding to the M QoS flows. In one example, the DU can send the drop indication information to the CU through control plane signaling, and the drop indication information may include the corresponding DRB ID or logical channel ID. In another example, the DU can send the drop indication information to the CU through the user plane tunnel corresponding to the DRB or logical channel, and then the CU can drop the data packets belonging to the first burst in the DRB or logical channel.

[0340] There are several ways to implement the DU sending the corresponding DRB or logical channel discard indication information to the CU. For example, if the DU determines that the final time limit for the air interface transmission of the first burst has arrived, it can send the corresponding DRB or logical channel discard indication information to the CU. Alternatively, if the DU determines that the data packets belonging to the first burst have exceeded the transmission delay requirement, it can send the corresponding DRB or logical channel discard indication information to the CU. For instance, if the DRBs corresponding to M QoS flows include DRB1, DRB2, and DRB3, then DRB1, DRB2, and DRB3 are related. After the DU determines that the final time limit for the air interface transmission of the first burst has arrived, it can send the corresponding DRB1, DRB2, and DRB3 discard indication information to the CU.

[0341] Example 6

[0342] In Example 6, a network device will be used as the example. Figure 2c Using the network device shown as an example, one possible implementation is described.

[0343] Figure 9 This is a flowchart illustrating the communication method provided in Embodiment Six of this application, as shown below. Figure 9 As shown, the method includes the following steps:

[0344] Step 901, CU-CP receives indication information f1.

[0345] Here, the indication information f1 can be used to indicate that M QoS flows are related. There are multiple ways for the CU-CP to receive the indication information f1. For example, the CU-CP can receive the indication information f1 from the SMF network element or the AMF network element. For specific implementation, please refer to the relevant description of the network device receiving the indication information a1 in the above embodiment 1.

[0346] Step 902: CU-CP performs admission control on M QoS flows according to the instruction information f1.

[0347] Here, the CU-CP can, based on the indication information f1, take simultaneous admission control measures on QoS flows belonging to the same synchronous QoS flow set, either accepting or rejecting them simultaneously.

[0348] In step 903, the CU-CP sends indication information f2 to the DU. Accordingly, the DU can receive indication information f2.

[0349] For example, the CU-CP can determine the DRB or LCH corresponding to M QoS flows and send indication information f2 to the DU. The indication information f2 is used to indicate that the DRB or LCH corresponding to the M QoS flows have an association relationship.

[0350] Step 904: CU-UP sends M data packets from QoS streams to DU.

[0351] For example, after receiving data packets from M QoS flows from the UPF network element, the CU-UP can send the data packets from the M QoS flows to the DU. Furthermore, the CU-UP can also indicate to the DU the burst to which the data packets in the M QoS flows belong. For example, the CU-UP can indicate to the DU the burst to which the data packets belong through the F1GTP-U header of the data packets, that is, the F1GTP-U header of the data packets can include burst identification information.

[0352] There are several ways for CU-UP to determine the burst to which the data packets in the M QoS flows belong. For example, CU-UP can receive indication information f3 from CU-CP. The indication information f3 is used to indicate the burst identification method of the data packets. Then, CU-UP can determine the burst to which the data packets in the M QoS flows belong based on the burst identification method of the data packets.

[0353] Step 905: DU processes data packets in M ​​QoS streams according to instruction information f2.

[0354] For example, DU can determine the burst to which the data packets in M ​​QoS streams belong, and then process the data packets belonging to the first burst in the M QoS streams; and after processing the data packets belonging to the first burst, process the data packets belonging to the second burst in the M QoS streams.

[0355] The DU's processing of data packets belonging to the first burst in M ​​QoS flows may include: the DU transmitting data packets belonging to the first burst in M ​​QoS flows to the terminal device. For specific implementation, please refer to the description in Embodiment 1 of the network device transmitting data packets belonging to the first burst in M ​​QoS flows to the terminal device.

[0356] Optionally, the DU's processing of data packets belonging to the first burst in the M QoS flows may further include: the DU sending a drop indication message for the corresponding DRB or logical channel to the CU-UP, the drop indication message including the identifier information of the first burst; correspondingly, after receiving the drop indication message, the CU-UP can drop data packets belonging to the first burst in the corresponding DRB or logical channel that have not yet been transmitted to the terminal device. There are several ways to implement the DU sending the drop indication message for the corresponding DRB or logical channel to the CU-UP. For example, if the DU determines that the final time limit for the air interface transmission of the first burst has arrived, it can send the drop indication message for the corresponding DRB or logical channel to the CU-UP; or if the DU determines that the data packets belonging to the first burst have exceeded the transmission delay requirement, it can send the drop indication message for the corresponding DRB or logical channel to the CU-UP.

[0357] Regarding Embodiments 1 to 6 above, it should be noted that:

[0358] (1) The step numbers of the flowcharts described in Embodiments 1 to 6 are merely examples of the execution flow and do not constitute a restriction on the order of execution of the steps. There is no strict execution order between steps that do not have a temporal dependency relationship in the embodiments of this application. In addition, not all steps shown in the flowcharts are mandatory steps. Some steps can be added or deleted based on the actual needs of each flowchart.

[0359] (2) The above focuses on describing the differences between different embodiments in Embodiment 1 to Embodiment 6. Except for the differences, Embodiment 1 to Embodiment 6 can be referred to each other.

[0360] (3) Some messages from the 5G communication system were used in the above embodiments one to six, but different messages or message names may be used in specific implementations. This application does not limit this.

[0361] The above primarily describes the solutions provided by the embodiments of this application from the perspective of device interaction. It is understood that, to achieve the above functions, network devices, core network devices, or terminal devices may include 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, the embodiments of 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.

[0362] This application embodiment can divide network devices, core network devices, or terminal devices into functional units according to the above method examples. For example, each function can be divided into a separate functional unit, or two or more functions can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0363] When using integrated units, Figure 10 A possible exemplary block diagram of the apparatus involved in an embodiment of this application is shown. For example... Figure 10 As shown, the device 1000 may include a processing unit 1002 and a communication unit 1003. The processing unit 1002 is used to control and manage the operation of the device 1000. The communication unit 1003 is used to support communication between the device 1000 and other devices. Optionally, the communication unit 1003 is also called a transceiver unit, and may include a receiving unit and / or a sending unit, respectively used to perform receiving and sending operations. The device 1000 may also include a storage unit 1001 for storing the program code and / or data of the device 1000.

[0364] The device 1000 can be a network device as described in the above embodiments, or it can be a chip disposed within a network device. Specifically, in embodiment two, the network device can be a primary network device or a secondary network device; in embodiment three, the network device can be a source network device or a target network device; in embodiment five, the network device can include a CU and a DU; and in embodiment six, the network device can include a CU-CP, a CU-UP, and a DU. The processing unit 1002 can support the device 1000 in executing the actions of the network device in the above method examples. Alternatively, the processing unit 1002 can primarily execute the internal actions of the network device in the method examples, and the communication unit 1003 can support communication between the device 1000 and other devices.

[0365] Specifically, in one embodiment, the communication unit 1003 is used to receive indication information, which indicates that M QoS streams are associated, where M is an integer greater than 1; and then, the processing unit 1002 is used to process the M QoS streams according to the indication information.

[0366] In one possible design, the processing unit 1002 is specifically used to: accept or reject the establishment requests of M QoS flows; or, accept or reject the modification requests of M QoS flows.

[0367] In one possible design, the processing unit 1002 is specifically used to: determine the burst to which the data packets in the M QoS streams belong, and process the data packets in the M QoS streams that belong to the first burst; and, after processing the data packets belonging to the first burst, process the data packets in the M QoS streams that belong to the second burst.

[0368] In one possible design, the processing unit 1002 is specifically used to: determine the burst to which the data packets in the M QoS flows belong based on the burst identification information of the data packets in the M QoS flows; or, determine the burst to which the data packets in the M QoS flows belong based on the payload information of the data packets in the M QoS flows; or, determine the burst to which the data packets in the M QoS flows belong based on the distinguishing identifier between different bursts; or, determine the burst to which the data packets in the M QoS flows belong based on the transmission time interval of the data packets in different bursts.

[0369] In one possible design, the communication unit 1003 is further configured to: transmit data packets belonging to the first burst in the M QoS streams according to their priority; or, transmit data packets belonging to the first burst in the M QoS streams according to their transmission ratio information; or, transmit data packets belonging to the first burst in the M QoS streams in a first-in-first-out (FIFO) manner.

[0370] In one possible design, the processing unit 1002 is specifically used to: after determining that the data packets belonging to the first burst exceed the transmission delay requirement, discard the data packets belonging to the first burst that have not yet been transmitted from the M QoS streams.

[0371] In one possible design, the indication information includes M associated information corresponding to each of the M QoS flows, and the M associated information are identical.

[0372] In one possible design, M QoS flows belong to a first PDU session; the indication information includes association information corresponding to the first PDU session, which is used to indicate that the first PDU session is an associated session, and the QoS flows included in the associated session have an association relationship.

[0373] In one possible design, the association information includes an association identifier and / or association type information.

[0374] In one possible design, the association type information is used to indicate an association type, which includes at least one of a first type, a second type, and a third type; the first type is used to indicate that data packets belonging to the same burst in the M QoS flows are transmitted according to the priority of the M QoS flows; the second type is used to indicate that data packets belonging to the same burst in the M QoS flows are transmitted according to the transmission ratio information of the M QoS flows; and the third type is used to indicate that data packets belonging to the same burst in the M QoS flows are transmitted in a first-in-first-out (FIFO) manner.

[0375] In one possible design, when the association type information indicates a second type, the association type information includes the transmission ratio information, or the indication information further includes the transmission ratio information.

[0376] In one possible design, the communication unit 1003 is specifically used to receive the indication information from the core network equipment.

[0377] In one possible design, the network device is the target network device of the terminal device, and the communication unit 1003 is specifically used to receive the indication information from the source network device.

[0378] In one possible design, the network device is an auxiliary network device for the terminal device, and the communication unit 1003 is specifically used to receive the instruction information from the main network device.

[0379] In one possible design, the indication information includes at least one of the following: (1) an identifier of an associated session, wherein the associated session includes M QoS flows that are associated; (2) an identifier of multiple QoS flows that are associated, wherein the multiple QoS flows that are associated include M QoS flows; (3) an identifier of a logical channel corresponding to the multiple QoS flows that are associated; (4) an identifier of a data radio bearer (DRB) corresponding to the multiple QoS flows that are associated; (5) multiple TFTs, wherein the QoS flows matched with each of the multiple TFTs are associated, wherein the QoS flows matched with each of the multiple TFTs include M QoS flows.

[0380] In one possible design, the indication information may also include association identifiers and / or association type information.

[0381] In one possible design, the communication unit 1003 is specifically used to receive the indication information from the terminal device.

[0382] In one possible design, the logical channels corresponding to the M QoS flows are located in different logical channel groups.

[0383] The device 1000 can be a core network device in the above embodiments, or it can be a chip installed in the core network device. The processing unit 1002 can support the device 1000 in performing the actions of the core network device in the method examples above. Alternatively, the processing unit 1002 mainly performs the internal actions of the core network device in the method examples, and the communication unit 1003 can support communication between the device 1000 and other devices.

[0384] Specifically, in one embodiment, the processing unit 1002 is used to determine indication information, which indicates that M QoS flows are associated; M is an integer greater than 1; and the communication unit 1003 is used to send the indication information to the network device.

[0385] In one possible design, the indication information includes M associated information corresponding to each of the M QoS flows, and the M associated information are identical.

[0386] In one possible design, M QoS flows belong to a first PDU session; the indication information includes association information corresponding to the first PDU session, which is used to indicate that the first PDU session is an associated session, and the QoS flows included in the associated session have an association relationship.

[0387] In one possible design, the association information includes an association identifier and / or association type information.

[0388] In one possible design, the association type information is used to indicate an association type, which includes at least one of a first type, a second type, and a third type; the first type is used to indicate that data packets belonging to the same burst in the M QoS flows are transmitted according to the priority of the M QoS flows; the second type is used to indicate that data packets belonging to the same burst in the M QoS flows are transmitted according to the transmission ratio information of the M QoS flows; and the third type is used to indicate that data packets belonging to the same burst in the M QoS flows are transmitted in a first-in-first-out (FIFO) manner.

[0389] In one possible design, when the association type information indicates a second type, the association type information includes the transmission ratio information, or the indication information further includes the transmission ratio information.

[0390] The device 1000 can be the terminal device in the above embodiments, or it can be a chip installed in the terminal device. The processing unit 1002 can support the device 1000 in performing the actions of the terminal device in the above method examples. Alternatively, the processing unit 1002 mainly performs the internal actions of the terminal device in the method examples, and the communication unit 1003 can support communication between the device 1000 and other devices.

[0391] Specifically, in one embodiment, the communication unit 1003 is used to receive indication information; wherein, the indication information is used to indicate that M QoS flows have an association relationship, or, the indication information is used to indicate that the DRB or LCH corresponding to the M QoS flows have an association relationship, where M is an integer greater than 1; furthermore, the processing unit 1002 is used to process the M QoS flows according to the indication information.

[0392] In one possible design, the processing unit 1002 is configured to: determine the burst to which the data packets in the M QoS flows belong, and process the data packets in the M QoS flows that belong to the first burst; and, after processing the data packets belonging to the first burst, process the data packets in the M QoS flows that belong to the second burst.

[0393] It should be understood that the division of units in the above device is merely a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, all units in the device can be implemented entirely through software calls from processing elements; all units can be implemented entirely in hardware; or some units can be implemented through software calls from processing elements, and others in hardware. For example, each unit can be a separate processing element, or it can be integrated into a chip within the device. Alternatively, it can be stored as a program in memory, called and executed by a processing element of the device. Moreover, these units can be fully or partially integrated together, or implemented independently. The processing element mentioned here can also be called a processor, which can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each of the above units can be implemented through integrated logic circuits in the processor element or through software calls from processing elements.

[0394] In one example, a unit in any of the above devices can be one or more integrated circuits configured to implement the methods described above, such as: one or more application-specific integrated circuits (ASICs), or one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs), or a combination of at least two of these forms of integrated circuits. As another example, when a unit in the device can be implemented in the form of a processing element scheduler, the processing element can be a processor, such as a general-purpose central processing unit (CPU), or other processor capable of calling programs. Furthermore, these units can be integrated together to implement a system-on-a-chip (SOC).

[0395] The receiving unit described above is an interface circuit of the device, used to receive signals from other devices. For example, when the device is implemented as a chip, the receiving unit is an interface circuit for the chip to receive signals from other chips or devices. The transmitting unit described above is an interface circuit of the device, used to transmit signals to other devices. For example, when the device is implemented as a chip, the transmitting unit is an interface circuit for the chip to transmit signals to other chips or devices.

[0396] See Figure 11 This is a schematic diagram of the structure of a network device provided in an embodiment of this application. This network device (or base station) can be applied to, for example... Figure 1 In the system architecture shown, the functions of the network device in the above method embodiments are executed. Network device 110 may include one or more DU 1101 and one or more CU 1102. DU 1101 may include at least one antenna 11011, at least one radio frequency unit 11012, at least one processor 11013, and at least one memory 11014. The DU 1101 is mainly used for transmitting and receiving radio frequency signals, converting radio frequency signals to baseband signals, and performing some baseband processing. CU 1102 may include at least one processor 11022 and at least one memory 11021.

[0397] The CU 1102 is mainly used for baseband processing and controlling network devices. The DU 1101 and CU 1102 can be physically installed together or physically separated, i.e., a distributed base station. The CU 1102 is the control center of the network device, also known as a processing unit, and is mainly used to complete baseband processing functions. For example, the CU 1102 can be used to control the network device to execute the operation procedures of the network device in the above method embodiments.

[0398] Additionally, optionally, the network device 110 may include one or more radio frequency units, one or more DUs, and one or more CUs. The DU may include at least one processor 11013 and at least one memory 11014, the radio frequency unit may include at least one antenna 11011 and at least one radio frequency unit 11012, and the CU may include at least one processor 11022 and at least one memory 11021.

[0399] In one example, the CU1102 can be composed of one or more single boards. Multiple single boards can collectively support a single access-indicating wireless access network (such as a 5G network), or they can each support wireless access networks with different access standards (such as LTE, 5G, or other networks). The memory 11021 and processor 11022 can serve one or more single boards. That is, each single board can have its own memory and processor, or multiple single boards can share the same memory and processor. Furthermore, each single board can also have necessary circuitry. Similarly, the DU1101 can be composed of one or more single boards. Multiple single boards can collectively support a single access-indicating wireless access network (such as a 5G network), or they can each support wireless access networks with different access standards (such as LTE, 5G, or other networks). The memory 11014 and processor 11013 can serve one or more single boards. That is, each single board can have its own memory and processor, or multiple single boards can share the same memory and processor. Furthermore, each single board can also have necessary circuitry.

[0400] Figure 11 The network device shown can achieve Figure 5 or Figure 6 or Figure 7 The illustrated method embodiments involve various processes of network devices. Figure 11 The operations and / or functions of each module in the network device shown are respectively for implementing the corresponding processes in the above method embodiments. For details, please refer to the descriptions in the above method embodiments; to avoid repetition, detailed descriptions are appropriately omitted here.

[0401] refer to Figure 12This is a schematic diagram of the structure of a core network device provided in an embodiment of this application. It can be an SMF network element or an AMF network element in the above embodiments, used to implement the operation of the SMF network element or AMF network element in the above embodiments.

[0402] like Figure 12 As shown, the core network device 1200 may include a processor 1201, a memory 1202, and an interface circuit 1203. The processor 1201 can be used to process communication protocols and communication data, and to control communication devices. The memory 1202 can be used to store programs and data, and the processor 1201 can execute the methods performed by the AMF or SMF network elements in this embodiment based on the program. The interface circuit 1203 can be used for communication between the core network device 1200 and other devices, which can be wired or wireless communication; the interface circuit can be, for example, a service-oriented communication interface.

[0403] The memory 1202 described above can also be externally connected to the core network device 1200. In this case, the core network device 1200 may include an interface circuit 1203 and a processor 1201. The interface circuit 1203 can also be externally connected to the core network device 1200. In this case, the core network device 1200 may include a memory 1202 and a processor 1201. When both the interface circuit 1203 and the memory 1202 are externally connected to the core network device 1200, the communication device 1200 may include a processor 1201.

[0404] Figure 12 The core network equipment shown can achieve Figure 5 or Figure 6 or Figure 7 The illustrated method embodiment involves various processes related to the core network equipment. Figure 12 The operations and / or functions of each module in the core network device shown are respectively for implementing the corresponding processes in the above method embodiments. For details, please refer to the descriptions in the above method embodiments; to avoid repetition, detailed descriptions are appropriately omitted here.

[0405] Please refer to Figure 13 This is a schematic diagram of the structure of a terminal device provided in an embodiment of this application. It can be the terminal device in the above embodiments, used to implement the operations of the terminal device in the above embodiments. For example... Figure 13As shown, the terminal device includes an antenna 1310, a radio frequency (RF) section 1320, and a signal processing section 1330. The antenna 1310 is connected to the RF section 1320. In the downlink direction, the RF section 1320 receives information sent by the network device through the antenna 1310 and sends the information to the signal processing section 1330 for processing. In the uplink direction, the signal processing section 1330 processes the information from the terminal device and sends it to the RF section 1320. The RF section 1320 processes the information from the terminal device and then sends it to the network device through the antenna 1310.

[0406] The signal processing section 1330 may include a modem subsystem for processing data at various communication protocol layers; it may also include a central processing subsystem for processing the terminal device's operating system and application layers; furthermore, it may include other subsystems, such as a multimedia subsystem and a peripheral subsystem, wherein the multimedia subsystem controls the terminal device's camera, screen display, etc., and the peripheral subsystem enables connection with other devices. The modem subsystem may be a separately configured chip.

[0407] The modem subsystem may include one or more processing elements 1331, such as a main control CPU and other integrated circuits. Furthermore, the modem subsystem may also include a storage element 1332 and an interface circuit 1333. The storage element 1332 is used to store data and programs; however, the program used to execute the methods performed by the terminal device in the above methods may not be stored in the storage element 1332, but rather in a memory outside the modem subsystem, which loads and uses it when needed. The interface circuit 1333 is used for communication with other subsystems.

[0408] The modulation and demodulation subsystem can be implemented using a chip, which includes at least one processing element and an interface circuit. The processing element executes the steps of any of the methods performed by the terminal device described above, and the interface circuit communicates with other devices. In one implementation, the unit in the terminal device that implements the steps of the above methods can be implemented in the form of a processing element scheduler. For example, the device for the terminal device includes a processing element and a storage element. The processing element calls a program stored in the storage element to execute the method performed by the terminal device in the above method embodiments. The storage element can be a storage element on the same chip as the processing element, i.e., an on-chip storage element.

[0409] In another implementation, the program used to execute the method performed by the terminal device in the above method can be located on a storage element on a different chip than the processing element, i.e., an off-chip storage element. In this case, the processing element calls or loads the program from the off-chip storage element onto the on-chip storage element to call and execute the method executed by the terminal device in the above method embodiments.

[0410] In another implementation, the units in the terminal device that implement the steps of the above methods can be configured as one or more processing elements located on the modem subsystem. These processing elements can be integrated circuits, such as one or more ASICs, one or more DSPs, one or more FPGAs, or combinations of these types of integrated circuits. These integrated circuits can be integrated together to form a chip.

[0411] The units implementing each step of the above method in the terminal device can be integrated together and implemented in the form of a System-on-Chip (SoC). This SoC chip is used to implement the above method. The chip can integrate at least one processing element and a storage element, with the processing element calling a stored program in the storage element to implement the method executed by the terminal device; alternatively, the chip can integrate at least one integrated circuit to implement the method executed by the terminal device; or, a combination of the above implementation methods can be used, with the function of some units implemented by the processing element calling a program, and the function of some units implemented by the integrated circuit.

[0412] As can be seen, the above-described apparatus for a terminal device may include at least one processing element and an interface circuit, wherein the at least one processing element is used to execute any of the methods provided by the terminal device in the above-described method embodiments. The processing element may execute part or all of the steps executed by the terminal device in a first manner: that is, by calling a program stored in a storage element; or in a second manner: that is, by combining instructions with the integrated logic circuits of the hardware in the processor element; of course, it may also combine the first and second methods to execute part or all of the steps executed by the terminal device.

[0413] The processing element here is the same as described above and can be implemented using a processor. The function of the processing element can be the same as... Figure 10 The processing unit described herein has the same function. Exemplarily, the processing element can be a general-purpose processor, such as a CPU, or one or more integrated circuits configured to implement the above methods, such as one or more ASICs, or one or more microprocessors (DSPs), or one or more FPGAs, or a combination of at least two of these integrated circuit forms. The storage element can be implemented using a memory, and the function of the storage element can be the same as... Figure 10 The storage unit described herein has the same function. Storage elements can be implemented using memory, and their function can be the same as... Figure 10 The storage units described herein have the same function. A storage element can be a single memory or a collective term for multiple memory units.

[0414] Figure 13 The terminal device shown can achieve Figure 5 or Figure 6 or Figure 7 The illustrated method embodiments involve various processes of the terminal device. Figure 13 The operations and / or functions of each module in the terminal device shown are respectively for implementing the corresponding processes in the above method embodiments. For details, please refer to the descriptions in the above method embodiments; to avoid repetition, detailed descriptions are appropriately omitted here.

[0415] The terms "system" and "network" in this application embodiment are used interchangeably. "At least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "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, and C" includes A, B, C, AB, AC, BC, or ABC. And, unless otherwise specified, the ordinal numbers such as "first" and "second" mentioned in this application embodiment are used to distinguish multiple objects and are not used to limit the order, sequence, priority, or importance of multiple objects.

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

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

[0418] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0419] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0420] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A communication method, characterized in that, The method is applicable to a first network device or a chip used in the first network device, and the method includes: Receive indication information, the indication information being used to indicate that M QoS flows are associated, where M is an integer greater than 1, and the M QoS flows are associated with the same multimedia service that includes different types of data; The M QoS flows are processed according to the indicated information.

2. The method according to claim 1, characterized in that, The M QoS streams respectively carry different types of data of the multimedia service, or the M QoS streams respectively carry different levels of the same type of data of the multimedia service.

3. The method according to claim 1 or 2, characterized in that, The different types of data include at least two of the following: video, audio, or text.

4. The method according to any one of claims 1 to 3, characterized in that, Processing the M QoS streams includes: Accept the establishment requests of the M QoS flows or reject the establishment requests of the M QoS flows; or, Accept the modification requests of the M QoS flows or reject the modification requests of the M QoS flows.

5. The method according to any one of claims 1 to 4, characterized in that, Processing the M QoS streams includes: Determine the burst to which the data packets in the M QoS flows belong; Process the data packets belonging to the first burst in the M QoS streams; and after processing the data packets belonging to the first burst, process the data packets belonging to the second burst in the M QoS streams.

6. The method according to claim 5, characterized in that, Determining the burst to which the data packets in the M QoS flows belong includes: Based on the burst identifier information of the data packets in the M QoS flows, determine the burst to which the data packets in the M QoS flows belong; or, Based on the payload information of the data packets in the M QoS flows, determine the burst to which the data packets in the M QoS flows belong; or, Based on the distinguishing identifiers between different bursts, determine the burst to which the data packets in the M QoS flows belong; or, Based on the transmission time interval of different bursts of data packets, determine the burst to which the data packets in the M QoS streams belong.

7. The method according to claim 5, characterized in that, Processing the data packets belonging to the first burst in the M QoS flows includes: According to the priority of the M QoS flows, transmit the data packets belonging to the first burst from the M QoS flows; or, According to the transmission ratio information of the M QoS flows, transmit the data packets belonging to the first burst from the M QoS flows; or, Data packets belonging to the first burst from the M QoS streams are transmitted in a first-in, first-out (FIFO) manner.

8. The method according to claim 5, characterized in that, Processing the data packets belonging to the first burst in the M QoS flows includes: Once it is determined that a data packet belonging to the first burst exceeds the transmission delay requirement, data packets belonging to the first burst but not yet transmitted from the M QoS flows are discarded.

9. The method according to any one of claims 1 to 8, characterized in that, The indication information includes M association information corresponding to the M QoS flows respectively, and the M association information are the same.

10. The method according to any one of claims 1 to 8, characterized in that, The M QoS streams belong to the first protocol data unit (PDU) session; The indication information includes association information corresponding to the first PDU session. The association information is used to indicate that the first PDU session is an associated session, and the QoS flows included in the associated session have an association relationship.

11. The method according to claim 9 or 10, characterized in that, The association information includes an association relationship identifier and / or association relationship type information.

12. The method according to claim 11, characterized in that, The association type information is used to indicate the association type, which includes at least one of a first type, a second type, and a third type; The first type is used to indicate that data packets belonging to the same burst in the M QoS flows are transmitted according to the priority of the M QoS flows; The second type is used to indicate that data packets belonging to the same burst in the M QoS flows are transmitted according to the transmission ratio information of the M QoS flows; The third type is used to indicate that data packets belonging to the same burst in the M QoS flows are transmitted in a first-in, first-out (FIFO) manner.

13. The method according to claim 12, characterized in that, When the association type information indicates the second type, the indication information also includes the transmission ratio information.

14. The method according to any one of claims 1 to 13, characterized in that, The receiving indication information includes: Receive the instruction information from the core network equipment.

15. The method according to any one of claims 1 to 13, characterized in that, The receiving indication information includes: Receive the indication information from the second network device; Wherein, the second network device is the primary network device of the terminal device, and the first network device is the secondary network device of the terminal device; or, the second network device is the source network device of the terminal device, and the first network device is the target network device of the terminal device.

16. The method according to any one of claims 1 to 8, characterized in that, The instruction information includes at least one of the following: The identifier of the associated session, wherein the QoS flows included in the associated session have an association relationship, and the associated session includes the M QoS flows; Identifiers of multiple QoS flows with an association relationship, including the M QoS flows; Identifiers of logical channels corresponding to multiple QoS flows that are related; Identifiers of the Data Radio Bearer (DRB) corresponding to multiple related QoS flows; Multiple flow filtering templates (TFTs) are associated with QoS flows matched to each TFT, and the QoS flows matched to each TFT include the M QoS flows.

17. The method according to claim 16, characterized in that, The indication information also includes an association identifier and / or association type information.

18. The method according to any one of claims 1 to 8, 16 or 17, characterized in that, The receiving indication information includes: Receive the instruction information from the terminal device.

19. The method according to any one of claims 1 to 18, characterized in that, The logical channels corresponding to the M QoS flows are located in different logical channel groups.

20. A communication system, characterized in that, The communication system includes: a first network device and a core network device; The core network device is used to: determine indication information, the indication information indicating that M QoS flows are associated, where M is an integer greater than 1, and the M QoS flows are associated with the same multimedia service including different types of data; and send the indication information to the first network device. The first network device is used to receive the indication information from the core network device.

21. The communication system according to claim 20, characterized in that, The M QoS streams respectively carry different types of data of the multimedia service, or the M QoS streams respectively carry different levels of the same type of data of the multimedia service.

22. The communication system according to claim 20 or 21, characterized in that, The different types of data include at least two of the following: video, audio, or text.

23. The communication system according to any one of claims 20 to 22, characterized in that, The first network device is further configured to process the M QoS flows according to the indication information.

24. The communication system according to any one of claims 20 to 22, characterized in that, The communication system also includes a second network device; The first network device is further configured to send the indication information to the second network device; The second network device is configured to receive the indication information from the first network device and process the M QoS flows according to the indication information; The first network device is the main network device of the terminal device, and the second network device is the auxiliary network device of the terminal device.

25. The communication system according to any one of claims 20 to 23, characterized in that, The communication system also includes a second network device; The first network device is further configured to send the indication information to the second network device; The second network device is configured to receive the indication information from the first network device and process the M QoS flows according to the indication information; The first network device is the source network device of the terminal device, and the second network device is the target network device of the terminal device.

26. A communication device, characterized in that, It includes units for performing each step of the method as described in any one of claims 1 to 19.

27. A communication device, characterized in that, It includes at least one processor and an interface circuit, wherein the at least one processor is configured to communicate with other devices via the interface circuit and to perform the method as described in any one of claims 1 to 19.

28. A communication device, characterized in that, Includes a processor for invoking a program stored in memory to perform the method as described in any one of claims 1 to 19.

29. A computer-readable storage medium, characterized in that, Includes a program, which, when run by a processor, executes the method as described in any one of claims 1 to 19.

30. A computer program product, characterized in that, When a computer reads and executes a program or instruction in the computer program product, the method described in any one of claims 1 to 19 is performed.

Images