Communication method and communication apparatus

Abstract

A communication method and a communication apparatus. A sensing layer is introduced into a communication protocol stack to achieve information interaction between different protocol layers, and the solution is universal and is conducive to improving the efficiency of data transmission. The method comprises: receiving a first uplink data packet, wherein the first uplink data packet may comprise a first sensing layer packet header, the first sensing layer packet header may carry first control information and / or a first transmission parameter, the first control information is used for requesting a second transmission parameter, the first transmission parameter can be understood as a parameter provided by a first application layer to a first data link layer, the second transmission parameter can be understood as a parameter provided by a second data link layer to the first application layer, and the first uplink data packet here can be a data packet corresponding to a first service flow.

Description

A communication method and communication device

[0001] This application claims priority to Chinese Patent Application No. 202311863894.2, filed on December 29, 2023, entitled "A Communication Method and Communication Device", the entire contents of which are incorporated herein by reference. Technical Field

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

[0003] In communication systems, communication protocols typically define multiple protocol layers. Data packets from the sending end are processed by each protocol layer before being sent to the receiving end, where they are then processed by each protocol layer to retrieve the data packets. The design and operation of different protocol layers are relatively independent, with each layer independently completing its logic using a modular division of labor. However, the data transmission process using existing communication protocols lacks effective interaction between the various protocol layers, impacting transmission efficiency. Therefore, how to achieve effective interaction between the various protocol layers during data transmission to improve transmission efficiency is a pressing technical problem that needs to be solved. Summary of the Invention

[0004] This application provides a communication method and a communication device that can achieve efficient interaction between different protocol layers, thereby improving the data transmission rate.

[0005] In a first aspect, embodiments of this application provide a communication method, which may include: receiving a first uplink data packet; the first uplink data packet includes a first sensing layer header, the first sensing layer header carrying first control information and / or first transmission parameters; the first control information is used to request second transmission parameters; the first transmission parameters are parameters provided by a first application layer to a first data link layer; the second transmission parameters are parameters provided by a second data link layer to a first application layer; the first uplink data packet is a data packet corresponding to a first service flow.

[0006] The first transmission parameter can be understood as the parameter provided by the application layer of the terminal device to the data link layer of the terminal device and / or the data link layer of the access network device. The second transmission parameter can be understood as the parameter provided by the data link layer of the terminal device and / or the data link layer of the access network device to the application layer of the terminal device. The first service flow can be a first quality of service (QoS) flow, or a first data radio bearer (DRB), or a service flow with a first Internet Protocol (IP) attribute (e.g., an IP 5-tuple).

[0007] As can be seen, by carrying the perception layer header in the uplink data packet, the application layer of the terminal device can exchange information with the data link layer of the terminal device and / or the data link layer of the access network device. The data link layer of the terminal device and / or the data link layer of the access network device can obtain parameters provided by the application layer of the terminal device, and can also provide parameters to the application layer of the terminal device. Different protocol layers can interact efficiently with each other by means of the perception layer header, which is conducive to improving data transmission efficiency.

[0008] In one possible implementation, the first perception layer header carries first control information, which includes first information used to request a first parameter. The method further includes sending the first parameter to the first application layer based on the first information. In other words, the first perception layer header may carry first information used by the application layer of the terminal device to request the data link layer of the terminal device to provide the first parameter.

[0009] In one possible implementation, the first perception layer packet header carries first control information, which includes second information used to request the access network device to provide second parameters. The method further includes sending the second information to the access network device. In other words, the first perception layer packet header can carry second information used by the application layer of the terminal device to request the access network device to provide second parameters.

[0010] In one possible implementation, sending the second information to the access network device includes: carrying the second information in the first data link layer header and sending the first data link layer header to the access network device. By carrying the second information in the first data link layer header, the access network device can avoid reading the perception layer header, making the solution more versatile.

[0011] In one possible implementation, the first perception layer packet header carries a first transmission parameter, which includes a third parameter. The method further includes adjusting the transmission strategy of the uplink data packet corresponding to the first service flow based on the third parameter. Therefore, the data link layer of the terminal device can optimize data transmission based on parameters provided by the application layer of the terminal device, thereby improving data transmission efficiency.

[0012] In one possible implementation, before receiving the first uplink data packet, the method further includes: carrying second control information in a second perception layer header and sending the second perception layer header to the first application layer; the second control information is used to request a third parameter. In other words, before the application layer of the terminal device provides parameters to the data link layer, the data link layer can first carry control information requesting the application layer to provide parameters through the perception layer header.

[0013] In one possible implementation, the first sensing layer header carries a first transmission parameter, which includes a fourth parameter. The method further includes: carrying the fourth parameter in a second data link layer header and sending the second data link layer header to the access network device. By carrying the fourth parameter in the second data link layer header, the access network device can avoid reading the sensing layer header, making the solution more universal.

[0014] In one possible implementation, before receiving the first uplink data packet, the method further includes: receiving third control information from the access network device; the third control information is used to request a fourth parameter; and sending the third control information to the first application layer. In other words, before providing parameters to the data link layer of the access network device, the application layer of the terminal device can receive control information from the access network device to request parameters from the application layer.

[0015] In one possible implementation, receiving the third control information from the access network device includes receiving a fourth data link layer header from the access network device, the fourth data link layer header carrying the third control information. Therefore, the access network device can carry the third control information through the data link layer header without modifying the perception layer header.

[0016] In one possible implementation, sending the third control information to the first application layer includes: carrying the third control information in a third perception layer header and sending the third perception layer header to the first application layer. That is, the terminal device can parse the fourth data link layer header to obtain the third control information, and then carry the third control information in the perception layer header.

[0017] In one possible implementation, the first transmission parameter includes at least one of the following: a data delay parameter; the data delay parameter is used to indicate the packet delay budget of the first data packet; the first data packet is a data packet corresponding to the first service flow; a data sequence parameter; the data sequence parameter is used to indicate the sequence identifier corresponding to the first data packet; a data failure parameter; the data failure parameter is used to indicate the sequence identifier of a failed data packet; and a data importance level parameter; the data importance level parameter is used to indicate the importance level of the first data packet.

[0018] In one possible implementation, the second transmission parameter includes at least one of the following: a reference transmission rate; the reference transmission rate is used to indicate the maximum transmission rate that the access network device can provide for the first service flow; a predicted transmission rate; the predicted transmission rate is used to indicate the maximum transmission rate that the access network device can provide for the first service flow at a predicted time; and a data timing parameter; the data timing parameter is used to indicate the time when the access network device expects the application layer of the terminal device to send data packets.

[0019] Secondly, embodiments of this application provide another communication method, which may include: sending a first uplink data packet; the first uplink data packet includes a first sensing layer header, the first sensing layer header carrying first control information and / or first transmission parameters; the first control information is used to request second transmission parameters; the first transmission parameters are parameters provided by the first application layer to the first data link layer; the second transmission parameters are parameters provided by the second data link layer to the first application layer; the first uplink data packet is a data packet corresponding to a first service flow.

[0020] As can be seen, by carrying the perception layer header in the uplink data packet, the application layer of the terminal device can exchange information with the data link layer of the terminal device and / or the data link layer of the access network device. The data link layer of the terminal device and / or the data link layer of the access network device can obtain parameters provided by the application layer of the terminal device, and can also provide parameters to the application layer of the terminal device. Different protocol layers can interact efficiently with each other by means of the perception layer header, which is conducive to improving data transmission efficiency.

[0021] In one possible implementation, the first sensing layer packet header carries first control information, and the method further includes: receiving second transmission parameters; and adjusting the transmission strategy of the uplink data packets corresponding to the first service flow based on the second transmission parameters. In other words, the application layer of the terminal device can optimize data transmission based on the transmission parameters provided by the data link layer of the terminal device and / or the data link layer of the access network device, thereby improving data transmission efficiency.

[0022] In one possible implementation, the first sensing layer packet header carries first transmission parameters. Before sending the first uplink data packet, the method further includes: receiving fourth control information; the fourth control information is used to request the first transmission parameters; and generating the first transmission parameters based on the fourth control information. In other words, the application layer of the terminal device can provide transmission parameters to the data link layer of the terminal device and / or the data link layer of the access network device, so that the data link layer can optimize data transmission based on the parameters provided by the application layer.

[0023] Thirdly, embodiments of this application provide yet another communication method, which may include: receiving a second uplink data packet from a terminal device; the second uplink data packet includes a third data link layer header, the third data link layer header carrying second information and / or a fourth parameter; the second information is used to request the second parameter; the second parameter is a parameter provided by the data link layer of the access network device to the first application layer; the fourth parameter is a parameter provided by the first application layer to the data link layer of the access network device; the second uplink data packet is a data packet corresponding to a first service flow.

[0024] The second parameter can be understood as the parameter provided by the data link layer of the access network device to the application layer of the terminal device, and the fourth parameter can be understood as the parameter provided by the application layer of the terminal device to the data link layer of the access network device.

[0025] As can be seen, by carrying the second information and / or the fourth parameter in the uplink data packet sent by the terminal device to the access network device, the application layer of the terminal device can achieve information interaction with the data link layer of the access network device. The data link layer of the access network device can obtain the parameters provided by the application layer of the terminal device, and can also provide parameters to the application layer of the terminal device. Different protocol layers can interact, which is conducive to improving data transmission efficiency.

[0026] In one possible implementation, the aforementioned third data link layer packet header carries a fourth parameter; the method further includes adjusting the transmission strategy of the uplink data packets corresponding to the first service flow based on the fourth parameter. It is evident that the data link layer of the access network device can optimize data transmission based on parameters provided by the application layer of the terminal device, thereby improving data transmission efficiency.

[0027] In one possible implementation, before receiving the second uplink data packet from the terminal device, the method further includes: sending third control information to the terminal device; the third control information is used to request a fourth parameter. That is, before obtaining the parameters provided by the application layer of the terminal device, the data link layer of the access network device can first send control information requesting the application layer of the terminal device to provide parameters.

[0028] In one possible implementation, sending the third control information to the terminal device includes: carrying the third control information in the header of the first GTP user plane part (GTP-U) packet; sending the first GTP-U packet header to the core network device; receiving a third perception layer packet header from the core network device; the third perception layer packet header carrying the third control information; and sending the third perception layer packet header to the terminal device. In other words, the access network device can first send the third control information to the core network device, which then carries the third control information in the perception layer packet header before sending the perception layer packet header carrying the third control information to the access network device. This method avoids the access network device modifying the perception layer packet header.

[0029] In one possible implementation, sending the third control information to the terminal device includes: carrying the third control information in a fourth data link layer header and sending the fourth data link layer header to the terminal device. That is, the access network device can also directly send the third control information to the terminal device, which then carries the third control information in a perception layer header and sends the perception layer header carrying the third control information to the application layer of the terminal device. This method also avoids the access network device from modifying the perception layer header.

[0030] In one possible implementation, the aforementioned third data link layer header carries second information; the method further includes: sending the second parameter to the terminal device based on the second information. That is, the data link layer of the access network device can provide the second parameter to the application layer of the terminal device.

[0031] In one possible implementation, sending the second parameter to the terminal device includes: carrying the second parameter in a second GTP-U header and sending the second GTP-U header to the core network device; receiving a fourth perception layer header from the core network device; the fourth perception layer header carrying the second parameter; and sending the fourth perception layer header to the terminal device. In other words, the access network device can first send the second parameter to the core network device, which then carries the second parameter in its perception layer header before sending the perception layer header carrying the second parameter back to the access network device. This method avoids the access network device from modifying the perception layer header.

[0032] In one possible implementation, sending the second parameter to the terminal device includes: carrying the second parameter in the fifth data link layer header and sending the fifth data link layer header to the terminal device. That is, the access network device can also directly send the second parameter to the terminal device, which then carries the second parameter in the perception layer header and sends the perception layer header carrying the second parameter to the application layer of the terminal device. This method also avoids the access network device from modifying the perception layer header.

[0033] In one possible implementation, the method further includes: receiving a first downlink data packet from a core network device; the first downlink data packet includes fifth control information and / or third transmission parameters; the fifth control information is used to request fourth transmission parameters; the third transmission parameters are parameters provided by the second application layer to the data link layer of the access network device; the fourth transmission parameters are parameters provided by the data link layer of the access network device to the second application layer; and the first downlink data packet is a data packet corresponding to a first service flow. The third transmission parameters can be understood as parameters provided by the server's application layer to the data link layer of the access network device, and the fourth transmission parameters can be understood as parameters provided by the access network device's data link layer to the server's application layer.

[0034] In one possible implementation, the first downlink data packet includes fifth control information, and the method further includes: sending fourth transmission parameters to the core network device based on the fifth control information. That is, the access network device can first send parameters provided by its data link layer to the server's application layer to the core network device, and then the core network device can carry these parameters in the perception layer header and send the perception layer header containing these parameters to the server.

[0035] In one possible implementation, the first downlink data packet includes a third transmission parameter, and the method further includes adjusting the transmission strategy of the downlink data packet corresponding to the first service flow based on the third transmission parameter. In other words, the data link layer of the access network device can optimize downlink data transmission based on parameters provided by the application layer of the server, thereby improving data transmission efficiency.

[0036] In one possible implementation, before receiving the first downlink data packet from the core network device, the method further includes: sending sixth control information to the core network device; the sixth control information is used to request third transmission parameters. That is, before receiving parameters provided by the application layer of the server, the access network device can send control information to the server through the core network device to request parameters.

[0037] In one possible implementation, sending the sixth control information to the core network device includes: carrying the sixth control information in a third GTP-U header and sending the third GTP-U header to the core network device. That is, the access network device can send the GTP-U header to the core network device by carrying control information used to request parameters from the application layer of the server in the GTP-U header.

[0038] Fourthly, embodiments of this application provide yet another communication method, which may include: receiving a third uplink data packet from an access network device; the third uplink data packet includes seventh control information and / or fifth transmission parameters; the seventh control information is used to request a sixth transmission parameter; the sixth transmission parameter is a parameter provided by a third application layer to a third data link layer; the fifth transmission parameter is a parameter provided by a fourth data link layer to a fourth application layer; and the third uplink data packet is a data packet corresponding to a first service flow.

[0039] The fifth transmission parameter may include parameters provided by the data link layer of the access network device to the application layer of the terminal device and / or the application layer of the server. The sixth transmission parameter may include parameters provided by the application layer of the terminal device and / or the application layer of the server to the data link layer of the access network device.

[0040] As can be seen, by carrying the seventh control information and / or the fifth transmission parameters in the uplink data packets sent by the access network device to the core network device, the data link layer of the access network device can achieve information interaction with the application layer of the terminal device and / or the application layer of the server. The access network device can carry all the information interacting with the application layer of the terminal device and / or the application layer of the server in the uplink data packets sent to the core network device, so that the core network device can carry this part of the interaction information in the perception layer header, thus eliminating the need for the access network device to modify the perception layer header.

[0041] In one possible implementation, the aforementioned third uplink data packet includes seventh control information, which includes third information used to request the terminal device to provide a fifth parameter. The method further includes: carrying the third information in a fifth perception layer header and sending the fifth perception layer header to the access network device. In other words, the core network device can carry the control information sent from the access network device to the terminal device in a perception layer header, and then send the perception layer header to the access network device, which in turn sends it to the terminal device.

[0042] In one possible implementation, the aforementioned third uplink data packet includes seventh control information, which includes fourth information. The fourth information is used to request the server to provide a sixth parameter. The method further includes: carrying the fourth information in a sixth perception layer header and sending the sixth perception layer header to the server. In other words, the core network device can carry the control information sent by the access network device to the server in a perception layer header and then send that perception layer header to the server.

[0043] In one possible implementation, the method further includes: receiving a seventh perception layer header from the server; the seventh perception layer header carrying a sixth parameter; and including the sixth parameter in a fourth GTP-U header and sending the fourth GTP-U header to the access network device. In other words, the core network device can parse the sixth parameter provided by the server's application layer to the data link layer of the access network device from the perception layer header from the server, and then include the sixth parameter in a GTP-U header and send the GTP-U header to the access network device.

[0044] In one possible implementation, the aforementioned third uplink data packet includes a fifth transmission parameter, which in turn includes a seventh parameter. The method further includes: carrying the seventh parameter in an eighth perception layer header and sending the eighth perception layer header to the access network device. In other words, the core network device can carry the transmission parameters sent by the access network device to the terminal device in the perception layer header, and then send the perception layer header to the access network device, which in turn sends it to the terminal device.

[0045] In one possible implementation, the aforementioned third uplink data packet includes a fifth transmission parameter and an eighth parameter in the fifth transmission parameter header. The method further includes: carrying the eighth parameter in an eighth perception layer header and sending the eighth perception layer header to the server. In other words, the core network device can carry the transmission parameters sent by the access network device to the server in the perception layer header and then send the perception layer header to the server.

[0046] In one possible implementation, before receiving the third uplink data packet from the access network device, the process further includes: receiving eighth control information from the server; the eighth control information being used to request an eighth parameter; and sending the eighth control information to the access network device. In other words, before receiving the eighth parameter provided by the access network device to the server, the core network device can first send the eighth control information, used by the server to request the eighth parameter, to the access network device.

[0047] Fifthly, embodiments of this application provide another communication method, which may include: receiving a fourth uplink data packet from a core network device; the fourth uplink data packet includes a ninth perception layer header, the ninth perception layer header carrying fourth information and / or an eighth parameter; the fourth information is used to request a sixth parameter; the eighth parameter is a parameter provided by the data link layer of the access network device to the second application layer, and the sixth parameter is a parameter provided by the second application layer to the data link layer of the access network device; the fourth uplink data packet is a data packet corresponding to a first service flow.

[0048] The sixth parameter can be understood as the parameter provided by the server's application layer to the data link layer of the access network device, and the eighth parameter can be understood as the parameter provided by the access network device's data link layer to the server's application layer.

[0049] As can be seen, by including a perception layer header in the uplink data packets sent by the core network device to the server, information exchange can be achieved between the data link layer of the access network device and the application layer of the server. The application layer of the server can obtain parameters provided by the data link layer of the access network device, and can also provide parameters to the data link layer of the access network device. Different protocol layers can interact efficiently with each other by means of the perception layer header, which is conducive to improving data transmission efficiency.

[0050] In one possible implementation, the aforementioned ninth perception layer header carries fourth information, and the method further includes: sending a sixth parameter to the core network device based on the fourth information. That is, the server can first send the parameters provided by the server's application layer to the data link layer of the access network device to the core network device, which then forwards them to the access network device.

[0051] In one possible implementation, sending the sixth parameter to the core network device includes: carrying the sixth parameter in the tenth perception layer header and sending the tenth perception layer header to the core network device. In other words, the server can carry parameters provided by the server's application layer to the data link layer of the access network device in the perception layer header and send it to the core network device. The core network device then parses the sixth parameter from the perception layer header and forwards it to the access network device.

[0052] In one possible implementation, the ninth sensing layer header carries an eighth parameter, and the method further includes adjusting the transmission strategy of the downlink data packets corresponding to the first service flow based on the eighth parameter. It is evident that the server's application layer can optimize downlink data transmission based on parameters provided by the data link layer of the access network device, thereby improving data transmission efficiency.

[0053] In one possible implementation, before receiving the fourth uplink data packet from the core network device, the method further includes: sending eighth control information to the core network device; the eighth control information is used to request an eighth parameter. That is, before receiving the eighth parameter provided by the access network device, the server can first send eighth control information to the core network device to request the eighth parameter, and then the core network device forwards the eighth control information to the access network device.

[0054] In a sixth aspect, embodiments of this application provide yet another communication method, which may include: a terminal device sending a first uplink data packet to an access network device; the first uplink data packet including a data link layer header, the data link layer header carrying first control information; the first control information being used to request the access network device to provide first transmission parameters; the first transmission parameters being parameters provided by the data link layer of the access network device to the application layer of the terminal device; the first uplink data packet being a data packet corresponding to a first service flow; the access network device receiving the first uplink data packet and, based on the first control information, sending a second uplink data packet to a core network device; the second uplink data packet including the first transmission parameters; the second uplink data packet being a data packet corresponding to the first service flow; the core network device receiving the second uplink data packet and, based on the first transmission parameters, sending a first downlink data packet to the access network device; the first downlink data packet including a perception layer header, the perception layer header carrying the first transmission parameters; the first downlink data packet being a data packet corresponding to the first service flow; the core network device receiving the first downlink data packet and sending the first downlink data packet to the terminal device; the terminal device receiving the first downlink data packet and, based on the first transmission parameters, adjusting the transmission strategy of the uplink data packet corresponding to the first service flow.

[0055] Seventhly, embodiments of this application provide a communication device, which may be a terminal device, a device within a terminal device, or a device compatible with a terminal device. The communication device may also be a chip system. The communication device can execute the methods described in the first or second aspect. The functions of the communication device can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions. The unit or module may be software and / or hardware. The operations performed by the communication device and its beneficial effects can be found in the methods described in the first or second aspect and their beneficial effects.

[0056] Eighthly, embodiments of this application provide a communication device, which may be an access network device, a device within an access network device, or a device compatible with an access network device. The communication device may also be a chip system. The communication device can execute the method described in the third aspect. The functions of the communication device can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions. The unit or module may be software and / or hardware. The operations performed by the communication device and its beneficial effects can be found in the method described in the third aspect above.

[0057] Ninthly, embodiments of this application provide a communication device, which may be a core network device, a device within a core network device, or a device compatible with a core network device. The communication device may also be a chip system. The communication device can execute the method described in the third aspect. The functions of the communication device can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions. The unit or module may be software and / or hardware. The operations performed by the communication device and its beneficial effects can be found in the method described in the fourth aspect above.

[0058] Tenthly, embodiments of this application provide a communication device, which may be a core network device, a device within a core network device, or a device compatible with a core network device. The communication device may also be a chip system. The communication device can execute the method described in the fourth aspect. The functions of the communication device can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions. The unit or module may be software and / or hardware. The operations performed by the communication device and its beneficial effects can be found in the method described in the fourth aspect above.

[0059] Eleventhly, embodiments of this application provide a communication device, which may be a server, a device within a server, or a device compatible with a server. The communication device may also be a chip system. The communication device can execute the method described in the fifth aspect. The functions of the communication device can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions. The unit or module may be software and / or hardware. The operations performed by the communication device and its beneficial effects can be found in the method described in the fifth aspect above.

[0060] In a twelfth aspect, embodiments of this application provide a communication device, the communication device including a processor, the processor being configured to perform the method as described in the first aspect, or the method as described in the second aspect, or the method as described in the third aspect, or the method as described in the fourth aspect, or the method as described in the fifth aspect.

[0061] In a thirteenth aspect, embodiments of this application provide a communication device, the communication device including a processor coupled to a memory for storing programs or instructions, wherein when the program or instructions are executed by the processor, the communication device performs the method described in the first aspect, or the method described in the second aspect, or the method described in the third aspect, or the method described in the fourth aspect, or the method described in the fifth aspect.

[0062] In one possible implementation, the communication device further includes a memory. Optionally, the processor and memory are integrated together. Optionally, the memory and processor are configured independently.

[0063] In a fourteenth aspect, embodiments of this application provide a communication device, the communication device including a processor and an interface circuit, the interface circuit being configured to receive signals from other communication devices outside the communication device and transmit them to the processor or to send signals from the processor to other communication devices outside the communication device, the processor being configured to implement the method as described in the first aspect, or the method as described in the second aspect, or the method as described in the third aspect, or the method as described in the fourth aspect, or the method as described in the fifth aspect through logic circuits or execution code instructions.

[0064] In a fifteenth aspect, embodiments of this application provide a computer-readable storage medium storing a computer program or instructions that, when executed by a communication device, implement the method described in the first aspect, or the method described in the second aspect, or the method described in the third aspect, or the method described in the fourth aspect, or the method described in the fifth aspect.

[0065] In a sixteenth aspect, embodiments of this application provide a computer program product including instructions that, when a communication device reads and executes the instructions, cause the communication device to perform the method described in the first aspect, or the method described in the second aspect, or the method described in the third aspect, or the method described in the fourth aspect, or the method described in the fifth aspect.

[0066] In a seventeenth aspect, embodiments of this application provide a communication system, which includes a terminal device, an access network device, a core network device, and a server. The terminal device is used to perform the method as described in the first or second aspect, the access network device is used to perform the method as described in the third aspect, the core network device is used to perform the method as described in the fourth aspect, and the server is used to perform the method as described in the fifth aspect. Attached Figure Description

[0067] Figure 1A is a schematic diagram of a protocol stack architecture provided in an embodiment of this application;

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

[0069] Figure 2 is a schematic diagram of a protocol stack architecture that introduces a perception layer according to an embodiment of this application;

[0070] Figure 3 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0071] Figure 4 is a schematic diagram of a UE-TLL transmitting data packets according to an embodiment of this application;

[0072] Figure 5 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0073] Figure 6 is a schematic diagram showing the position of an SDP protocol in the protocol stack according to an embodiment of this application;

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

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

[0076] In this application, the terms "first," "second," etc., are used to distinguish identical or similar items with essentially the same function and purpose. Those skilled in the art will understand that the terms "first," "second," etc., do not limit the quantity or execution order, nor do they imply that they must be different. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0077] It should be understood that in this application, "at least one" refers to one or more; "multiple" refers to two or more. Furthermore, the word "equal to" in this application can be used in conjunction with "greater than" or "less than". When "equal to" and "greater than" are used together, the technical solution using "greater than" is adopted; when "equal to" and "less than" are used together, the technical solution using "less than" is adopted.

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

[0079] The relevant names or terms involved in this application will be explained below to facilitate understanding by those skilled in the art.

[0080] I. Terminal Equipment

[0081] A terminal device is a user-side device with wireless transceiver capabilities. It can be a fixed device, mobile device, handheld device (e.g., mobile phone), wearable device, in-vehicle device, or a wireless device (e.g., communication module, modem, or chip system) built into the aforementioned devices. Terminal devices are used to connect people, things, and machines, and can be widely used in various scenarios, such as: cellular communication, device-to-device (D2D) communication, V2X communication, machine-to-machine / machine-type communications (M2M / MTC) communication, Internet of Things (IoT), virtual reality (VR), augmented reality (AR), industrial control, self-driving, remote medical care, smart grid, smart furniture, smart office, smart wearables, smart transportation, smart city, drones, robots, and other scenarios. For example, a terminal device can be a handheld terminal in cellular communication, a communication device in D2D, an IoT device in MTC, a surveillance camera in intelligent transportation and smart cities, or a communication device on a drone, etc. Terminal devices are sometimes referred to as user equipment (UE), user terminal, user device, user unit, user station, terminal, access terminal, access station, UE station, remote station, mobile device, or wireless communication device, etc. In the embodiments of this application, the device used to implement the functions of the terminal device can be the terminal device itself, or it can be a device capable of supporting the terminal device in implementing that function, such as a chip system or a combination of devices or components capable of implementing the functions of the terminal device. This device can be installed in the terminal device.

[0082] II. Access Network Equipment

[0083] Access network equipment is a network-side device with wireless transceiver capabilities. Access network equipment provides wireless communication functionality to terminal devices within a radio access network (RAN), and therefore can also be called RAN equipment. For example, access network equipment can be a base station, an evolved NodeB (eNodeB), a next-generation NodeB (gNB) in a 5G mobile communication system, a transmission reception point (TRP), a 3GPP later-evolved base station, an access node in a WiFi system, a wireless relay node, a wireless backhaul node, etc. In communication systems employing different radio access technologies (RATs), the name of the equipment with base station functionality may differ. For example, in LTE systems it may be called an eNB or eNodeB, while in 5G or NR systems it may be called a gNB. This application does not limit the specific name of the base station. Access network equipment may include one or more co-located or non-co-located transmission and reception points. For example, access network equipment may include one or more central units (CU), one or more distributed units (DU), or one or more CU and one or more DU.

[0084] For example, the functionality of a CU can be implemented by one entity or different entities. For instance, the CU's functionality can be further divided, separating the control plane and user plane and implementing them through different entities: a control plane CU entity (i.e., the CU-CP entity) and a user plane CU entity (i.e., the CU-UP entity). The CU-CP and CU-UP entities can be coupled with a DU to jointly complete the access network device's functionality. In this way, some functions of a wireless access network device can be implemented through multiple network function entities. These network function entities can be network elements in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform). As another example, in vehicle-to-everything (V2X) technology, the access network device can be a roadside unit (RSU). Multiple access network devices in a communication system can be base stations of the same type or different types. Base stations can communicate with terminal devices directly or through relay stations. In this embodiment, the device for implementing the access network device function can be the access network device itself, or it can be a device that supports the access network device in implementing the function, such as a chip system or a combination of devices or components that can implement the access network device function. This device can be installed in the access network device. In this embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices.

[0085] III. Core Network Equipment

[0086] Core network equipment is used to implement functions such as mobility management, data processing, session management, policy and charging. The names of the equipment implementing core network functions may differ in systems using different access technologies, and this application does not limit this. Taking a 5G network as an example, the logical network elements of the 5G core network (5GC) include: access and mobility management function (AMF), session management function (SMF), or user plane function (UPF), etc. AMF is a network element used for access and mobility management of terminal devices, mainly involving functions such as location updates, network registration, and handover control. SMF is a network element used for session management of terminal devices, mainly involving functions such as session establishment, modification, and release. UPF is a network element used for receiving and forwarding user data. UPF is controlled by SMF. Different logical network elements of 5GC can be deployed on the same or different physical devices. For example, AMF and SMF can be deployed on the same physical device or on two separate physical devices. Furthermore, 5GC logical network elements can be deployed on the same physical device as 4G core network elements. The device used to implement the functions of the core network equipment can be the core network equipment itself, or it can be a device that enables the core network equipment to implement the functions, such as a chip system or a combination of devices or components that can implement the functions of the core network equipment. The device can be installed in the core network equipment.

[0087] IV. Server

[0088] A server can be an application server corresponding to various services, providing a variety of possible services to terminal devices. The application server may have an application layer equivalent to the application layer of the terminal device. In this embodiment, the device for implementing the server function can be the server itself, or a device capable of supporting the server in implementing that function, such as a chip system or a combination of devices or components capable of implementing server functions, which can be installed in the server. In this embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices.

[0089] V. Protocol Layer Architecture

[0090] Communication between the terminal device, network device, and server follows a specific protocol stack architecture. Please refer to Figure 1A, which is a schematic diagram of a protocol stack architecture provided in an embodiment of this application. As shown in Figure 1A, taking the terminal device sending a data packet to the server through the network device as an example, the data packet transmission sequentially passes through the terminal device's application layer -> transport layer -> network layer -> access layer -> physical layer, then through the network device's access layer -> data link layer -> physical layer, finally reaching the server's physical layer -> data link layer -> network layer -> transport layer -> application layer.

[0091] The application layer supports protocols such as Hypertext Transfer Protocol (HTTP), File Transfer Protocol (FTP), and Real-Time Transport Protocol (RTP). The transport layer supports protocols such as Transmission Control Protocol (TCP) and User Datagram Protocol (UDP). The network layer supports Internet Protocol (IP) protocols, such as IPv4 or IPv6. The access layer includes the Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), Media Access Control (MAC), and Physical Layer (PHY).

[0092] VI. Interaction between different protocol layers

[0093] Currently, the design and operation of different protocol layers are relatively independent, with each layer's logic completed independently using a modular division of labor. Effective interaction between these different protocol layers is lacking. The lack of interaction between these layers includes, but is not limited to, the following:

[0094] (1) The transport layer lacks the bandwidth capability of the interactive access layer.

[0095] During data transmission from a sender (such as a terminal device) to a receiver (such as a network device), congestion may occur due to the limited nature of wireless resources and the instability of wireless channels. When congestion occurs, if the sender continues to send a large number of data packets, it may lead to increased packet transmission delays or packet loss. Therefore, congestion control is necessary.

[0096] In one implementation, the sender can use TCP congestion control algorithms to prevent excessive data injection into the network. Specifically, the sender's transport layer can maintain a congestion window (Cwnd) and employ a climbing strategy, gradually attempting to increase the transmission rate from a lower one. That is, it initially uses a smaller congestion window value, and if network congestion is confirmed to be absent, it gradually increases the congestion window value, sending more data packets. In this approach, if the access layer has a large bandwidth capacity, the process of probing using the climbing strategy will consume a significant amount of time. For example, assuming the access layer can provide a maximum transmission rate of 1Tbps, if the transport layer starts probing from 1Mbps, reaching 1Tbps will take hundreds of milliseconds, resulting in low bandwidth utilization.

[0097] It is evident that if the transport layer can know the bandwidth capability of the access layer, it can save the time consumed in the trial transmission process and improve transmission efficiency.

[0098] (2) The application layer lacks the bandwidth prediction capability of the interactive access layer.

[0099] The sending application layer can adjust its coding based on the actual data transmission rate at the receiving end to adapt to the channel. For example, if the sender transmits 1080p video data and the receiver experiences stuttering during playback, the sending application layer can automatically adjust to transmit 720p video data to reduce the bandwidth requirements of the access layer and thus avoid stuttering during playback. However, this adjustment method usually occurs only after channel changes affect data transmission; that is, the application layer coding adjustment is triggered only after a period of video playback stuttering, resulting in low data transmission stability.

[0100] It is evident that if the application layer can know the bandwidth changes predicted by the access layer, it can adjust the encoding in advance to avoid lag.

[0101] (3) The access layer lacks the attributes of data packets from the interactive application layer.

[0102] For service flows controlled by the same QoS flow, the base station's access layer uses the same transmission processing (such as scheduling), and data packets belonging to the same service are usually placed in the same QoS flow. However, data packets belonging to the same service may have different QoS requirements, so the attributes of the entire QoS flow will be set according to the data packet with the highest QoS requirement. For example, suppose that some data packets in the QoS flow require a packet delay budget (PDB) of 10ms, while other data packets require a PDB of 20ms. Then, the base station will schedule the entire QoS flow according to the PDB requirement of 10ms, which will affect the base station's capacity.

[0103] It is evident that if the access layer can distinguish between data packets with different attributes (such as PDB, packet importance, etc.) within the same QoS flow, then the access layer can adopt different transmission strategies for data packets with different attributes to improve resource utilization.

[0104] (4) The access layer lacks interactive application layer failed data packets.

[0105] In scenarios involving continuous data packet transmission, such as downlink transmission of artificial intelligence (AI) model data from the server to the UE, or uplink transmission of 3D model data from the UE to the server, the application layer typically generates the data and sends it to the access layer, which then transmits it. In practice, during the transmission of the first model data, the application layer may need to switch to transmitting the second model data due to a change in scenario. In this case, the application layer will choose to terminate the transmission of the remaining data in the first model data and begin transmitting the second model data. However, after the application layer terminates the transmission of the remaining data in the first model data, the data already sent by the application layer to the access layer in the first model data becomes invalid. In this situation, for the data already sent by the application layer to the access layer in the first model data, the access layer will start a discard timer according to the PDB requirements. Before the discard timer expires, it will continue to transmit this invalid data, which not only affects the transmission latency of the second model data but also increases the air interface load.

[0106] It is evident that if the access layer can identify expired data packets, it will help reduce the air interface load.

[0107] (5) The access layer lacks the data packet sending time of the interactive application layer.

[0108] For periodic services, if multiple data packets in a periodic service arrive at the base station access layer at similar times, and the PDB (Programmable Module) requirement time for these multiple data packets is short, the base station will need to schedule a large number of data packets in a short period of time, resulting in high capacity pressure on the base station.

[0109] It is evident that if the access layer can provide the data packet sending time for the application layer, thus dispersing the time for the application layer to send data packets, it will help alleviate the scheduling pressure on the base station.

[0110] VII. RTP Protocol

[0111] RTP is a network transport protocol, typically built on top of the User Datagram Protocol (UDP). After being encapsulated by the RTP protocol, it forms RTP packets containing an RTP header. Currently, if the application layer uses RTP, it can use the RTP header to carry some application-layer information, enabling the provision of application-layer information to other protocol layers for transmission optimization. For example, by carrying packet attribute information in the RTP header, the access layer can distinguish packets with different attributes (such as PDB, packet importance, etc.) and thus adopt different transmission strategies for packets with different attributes. However, this approach to using RTP lacks versatility. If the application layer does not use RTP, it cannot exchange information with other protocol layers. Furthermore, this approach lacks a mechanism for other protocol layers (such as the access layer) to provide feedback information to the application layer.

[0112] Based on this, this application proposes a communication method and apparatus that can efficiently exchange information between different protocol layers and has universality, which is beneficial to improving transmission efficiency.

[0113] The embodiments of this application can be applied to various communication systems, such as Long Term Evolution (LTE) systems, 5th generation (5G) systems, New Radio (NR) systems, Wireless-Fidelity (WiFi) systems, 3rd Generation Partnership Project (3GPP) related communication systems, and other future communication systems, such as 6th generation (6G) mobile communication systems. The embodiments of this application can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), and Internet of Things (IoT) communication systems, or other communication systems. For ease of description, this application uses a 5G system as an example.

[0114] The network architecture applicable to embodiments of this application is described below.

[0115] Please refer to Figure 1B, which is a schematic diagram of a network architecture provided in an embodiment of this application. As shown in Figure 1B, this network architecture, taking a 5G system as an example, may include three parts: a terminal equipment part, an operator network part, and a data network (DN) part.

[0116] The terminal equipment section includes terminal equipment 101, which can also be referred to as user equipment (UE). In this embodiment, the terminal equipment 101 is a device with wireless transceiver capabilities, which can communicate with one or more core networks (CNs) via RAN 102.

[0117] An operator network may include unified data management (UDM), access and mobility management function (AMF), session management function (SMF), policy control function (PCF), user plane function (UPF), and RAN (RAN), etc. The parts of the operator network other than the RAN can be referred to as the core network (CN) or core network portion.

[0118] The data network DN104, also known as a protocol data network (PDN), is typically a network located outside the carrier's network, such as a third-party network. Multiple data networks DN104 can be accessed by the carrier's network, and various services can be deployed on the data network DN104, providing data and / or voice services to terminal devices.

[0119] The following is a brief introduction to the network functions in the operator's network.

[0120] RAN102 can be viewed as a sub-network of the operator's network, serving as the implementation system between service nodes and terminal devices within the operator's network. For a terminal device to access the operator's network, it first passes through RAN102, and then connects to the operator's network's service nodes via RAN102. The access network device in this embodiment is a device that provides wireless communication functions for terminal devices; it can also be referred to as a network device.

[0121] The Access and Mobility Management Function (AMF105) (also known as an AMF network element, AMF network function, or AMF network function entity) is a control plane network function provided by the operator's network. It is responsible for access control and mobility management of terminal devices accessing the operator's network, including functions such as mobility state management, allocation of temporary user identities, authentication, and authorization of users.

[0122] The Session Management Function SMF106 (also known as SMF Network Element, SMF Network Function, or SMF Network Function Entity) is a control plane network function provided by the operator's network, responsible for managing the Protocol Data Unit (PDU) sessions of terminal devices.

[0123] The User Plane Function (UPF103) (also known as a UPF network element, UPF network function, or UPF network function entity) is a gateway provided by the operator, serving as the gateway for communication between the operator's network and the data network DN104. Its main responsibility is processing user packets, such as forwarding and accounting.

[0124] The Unified Data Management Network Element UDM108 (also known as a UDM network element, UDM network function, or UDM network function entity) is a control plane function provided by the operator. It is responsible for storing information such as the subscriber permanent identifier (SUPI), the generic public subscription identifier (GPSI), and the credential of subscribed users within the operator's network. The SUPI is encrypted during transmission; the encrypted SUPI is called the subscription concealed identifier (SUCI). This information stored in UDM108 can be used for authentication and authorization of terminal devices accessing the operator's network.

[0125] The policy control function (PCF) 107 provides policies to the AMF and SMF, such as QoS policies and slice selection policies.

[0126] The Application Function (AF) interacts with the 3GPP core network to provide application-layer services. For example, it provides application-layer data routing and network access capabilities. The AF can interact with the PCF107. The AF can be located either inside or outside the 5G core network. If the AF is inside the 5G core network, it can interact directly with the PCF107. If the AF is outside the 5G core network, the Network Exposure Function (NEF) acts as an intermediate node to forward the interactions between the AF and the PCF107. For example, the interactions are forwarded through the NEF.

[0127] In Figure 1B, N1, N2, N3, N5, N6, N7, N8, N10, and N11 are interface sequence numbers. The meanings of these interface sequence numbers can be found in the definitions in the 3GPP standard protocols, and will not be repeated here. It should be noted that Figure 1B only provides an illustrative example using UE101 as the terminal device, and the interface names between the various network functions in Figure 1B are merely examples. In specific implementations, the interface names of this system architecture may be other names, and this application embodiment does not specifically limit them.

[0128] The methods provided in the embodiments of this application will be described below with reference to the accompanying drawings. Before introducing the embodiments, some terms involved in the embodiments of this application will be uniformly explained.

[0129] (1) Optimization of data transmission

[0130] In this application, data transmission optimization refers to adjusting certain parameters of data transmission to make the performance of data transmission more suitable for the current communication conditions and system capacity. Specifically, it can be one of the following two types of data transmission optimization: ① The application layer optimizes data transmission based on parameters provided by the data link layer, such as adjusting the transmission window when transmitting data, or adjusting the decision on the sending rate when transmitting data; ② The data link layer optimizes data transmission based on parameters provided by the application layer, such as adjusting the scheduling time when transmitting data, or discarding invalid data during transmission.

[0131] (2) Transmission parameters of the data link

[0132] The data link transmission parameters in this application are some parameters related to the transmission of the data link, such as the data link rate, the predicted rate of the data link, the reliability information of the data link, the load information of the data link, the signal quality or signal strength of the data link, or other parameters related to the transmission of the data link. This application does not limit these parameters.

[0133] (3) Data packet service attribute information,

[0134] The data packet service attribute information in this application refers to some attribute information of the data packet in the service to which the data packet belongs, such as data packet importance information, data packet latency requirement information, data packet integrity requirement information, data packet failure information, data packet service type (such as voice, video, game, etc.), data packet encoding information (such as encoding type, encoding resolution, frame rate), data packet jitter information, data packet application protocol type, data packet transport layer protocol type, etc., and this application does not impose any restrictions on this.

[0135] (4) IP quintuple

[0136] In this embodiment, the IP 5-tuple can be used to uniquely identify a service flow. The IP 5-tuple may include the source IP address, destination IP address, source port, destination port, and communication protocol information.

[0137] (5) Data packets

[0138] In this application, all data packets (such as the first uplink data packet, the second uplink data packet, etc.) correspond to the same service flow, for example, the data packet corresponding to the first service flow. The first service flow may be a first QoS flow, or, the first service flow may be a first data radio bearer (DRB), or, the first service flow may be a service flow with a first IP attribute (such as an IP 5-tuple).

[0139] It should be noted that the application layer (e.g., the application layer of the terminal device or the application layer of the server) in this application embodiment can also be described as the traffic logic layer (TLL). The TLL may include HTTP protocol, RTP protocol, real-time transport control protocol (RTCP), FTP protocol, etc., and may also include some transport layer protocols, such as the quick UDP internet connections (QUIC) protocol, or other transport protocols on top of TCP / UDP. The data link layer (DLL) in this application embodiment may include the air interface protocol layer of the 5G system: as shown in Figure 1A, the PHY, MAC layer, RLC layer, PDCP layer, and SDAP layer of the terminal device and access network device; it may also include the WiFi air interface protocol layer, and may also include the data link layer of wired networks (e.g., Ethernet). It is understood that the application layer (TLL) and data link layer (DLL) in this application embodiment are defined only for the convenience of distinguishing different functions, and may be replaced by other names, which are not limited in this application.

[0140] In this embodiment, to achieve efficient interaction between different protocol layers, a perception layer is introduced to transmit interaction information between different protocol layers. Optionally, the perception layer can be placed between the TLL and DLL, or it can be set above the transport layer (TCP / UDP), or it can be set in other locations, such as in the extension header of the network layer (IP), or it can be set in the extension header of other protocol layers. This application does not limit this.

[0141] It should be noted that the perception layer is the name of the layer introduced in this application used to transmit interactive information between different protocol layers. In the embodiments of this application, the perception layer can also be described as a vertical interaction and awareness protocol (VIAP), or an interaction layer, or an interactive perception layer, or other names. This application does not limit the name of the layer with the above functions.

[0142] For example, please refer to Figure 2, which is a schematic diagram of a protocol stack architecture introducing a perception layer provided in an embodiment of this application. As shown in Figure 2, the perception layer can be set above the transport layer of the terminal device and the server, and can also be set above the user plane part of GTP (GTP-U) protocol layer of the core network device. For ease of description, this embodiment of the application uses UE as the terminal device, RAN as the access network device, and CN as the core network device as an example for illustration. The perception layer of the terminal device (UE-perception layer) can be located between the TLL (UE-TLL) and DLL (UE-DLL) of the terminal device; the perception layer of the server (Server-perception layer) can be located between the TLL (Server-TLL) of the server and the DLL (such as RAN-DLL) of the access network device; and the perception layer of the core network device (CN-perception layer) is located above the CN-GTP-U layer. In Figure 2, based on the perception layer, bidirectional interaction between UE-TLL and UE-DLL, UE-TLL and RAN-DLL, and Server-TLL and RAN-DLL can be realized. For ease of understanding, this application uses the protocol stack architecture shown in Figure 2 as an example for illustration.

[0143] Taking upstream transmission as an example, please refer to Figure 3. Figure 3 is a flowchart illustrating a communication method provided in an embodiment of this application, which may include, but is not limited to, the following steps:

[0144] S301, UE-TLL sends a first uplink data packet to UE-DLL. Correspondingly, UE-DLL receives the first uplink data packet from UE-TLL. The first uplink data packet includes a first perception layer header, which carries first control information and / or first transmission parameters.

[0145] Regarding the first control information, it can be used to request second transmission parameters. These second transmission parameters can be used by the TLL to optimize data transmission; therefore, the second transmission parameters can also be understood as parameters provided by the DLL to the UE-TLL. Specifically, the second transmission parameters may include data link transmission parameters. Optionally, the second transmission parameters may include a reference transmission rate, which can be used to indicate the maximum transmission rate that the DLL can provide for the first service flow. The second transmission parameters may also include a predicted transmission rate, which can be used to indicate the maximum transmission rate that the DLL can provide for the first service flow at a predicted time. The second transmission parameters may also include data timing parameters, which can be used to indicate the time when the DLL expects the UE-TLL to send data packets.

[0146] Since the DLL can be a UE-DLL and / or a RAN-DLL, it is described in Scenario 1 and Scenario 2 below.

[0147] Scenario 1: Regarding the UE-TLL requesting a second transmission parameter from the UE-DLL, to distinguish it from Scenario 2, in this scenario, the second transmission parameter is described as a first parameter, and the first control information in this scenario is described as first information. The first parameter can be understood as the parameter provided by the UE-DLL to the UE-TLL. The first parameter can be used by the TLL to optimize data transmission. The first parameter may include data link transmission parameters. That is, the terminal device can carry the first information in the first perception layer header of the first uplink data packet, and then control the UE-DLL to provide the first parameter to the UE-TLL through the first information. See S301a for details.

[0148] S301a, UE-DLL sends the first parameter to UE-TLL based on the first information. Correspondingly, UE-TLL receives the first parameter from UE-DLL.

[0149] After receiving the first uplink data packet from the UE-TLL, the UE-DLL can parse the first perception layer header of the first uplink data packet to obtain first information. Based on the first information, it can generate first parameters and send the first parameters to the UE-TLL. Subsequently, the UE-TLL can adjust the transmission strategy of the uplink data packet corresponding to the first service flow based on the first parameters.

[0150] Scenario 2: Regarding the UE-TLL requesting second transmission parameters from the RAN-DLL, to distinguish it from Scenario 1, in this scenario, the second transmission parameters are described as second parameters, and the first control information in this scenario is described as second information. The second parameters can be understood, for example, as parameters provided by the RAN (such as the RAN-DLL) to the UE-TLL. The second parameters may include data link parameters. The second parameters can be used by the TLL to optimize data transmission. See S301b below for details.

[0151] S301b, UE-DLL sends the second information to RAN. Correspondingly, RAN receives the second information from UE-DLL.

[0152] In this application, the UE-DLL can parse the first perception layer header of the first uplink data packet to obtain the second information, and then carry the second information in the first data link layer header and send the first data link layer header to the RAN. This is because access network devices typically do not parse header content above the network layer. This method avoids the access network device from parsing the first perception layer header from the first uplink data packet, making this application universal. Optionally, the UE-DLL can also forward the first perception layer header to the access network device so that the access network device can obtain the second information by parsing the first perception layer header. Optionally, the first data link layer header can be the data link layer header of the first uplink data packet, or it can be the data link layer header of other uplink data packets corresponding to the first service flow, such as the data link layer header of uplink data packet A or uplink data packet B. Optionally, the data link layer header in this application embodiment (such as the first data link layer header mentioned above) can be an SDAP header, a PDCP header, an RLC header, or other data link layer headers. This application embodiment is not limited to this.

[0153] Regarding the first transmission parameters, these parameters can be used by the DLL to optimize data transmission. Therefore, the first transmission parameters can also be understood as parameters provided by the UE-TLL to the DLL. The first transmission parameters may include data packet service attribute information. Optionally, the first transmission parameters may include data delay parameters, which can be used to indicate the packet delay budget of the first data packet. The first data packet can be a data packet corresponding to the first service flow. The first transmission parameters may also include data sequence parameters, which can be used to indicate the sequence identifier corresponding to the first data packet. The first transmission parameters may also include data failure parameters, which can be used to indicate the sequence identifier of failed data packets. The first transmission parameters may also include data importance level parameters, which can be used to indicate the importance level of the first data packet.

[0154] In some embodiments, the UE-TLL can receive a second perception layer header, which may carry second control information. This second control information can be used to request the UE-TLL to provide first transmission parameters. Optionally, the second perception layer header may be the perception layer header of a downlink data packet corresponding to the first service flow. That is, the terminal device can carry the second control information in the second perception layer header of the downlink data packet corresponding to the first service flow, and then control the UE-TLL to provide the first transmission parameters to the UE-DLL through the second control information.

[0155] Since the DLL can be a UE-DLL and / or a RAN-DLL, it is described in Scenario 3 and Scenario 4 below.

[0156] Scenario 3: Regarding the UE-TLL providing the first transmission parameter to the UE-DLL, to distinguish it from Scenario 4, in this scenario, the first transmission parameter is described as the third parameter. The third parameter can be understood as the parameter provided by the UE-TLL to the UE-DLL. The third parameter can be used by the UE-DLL to optimize data transmission. The third parameter may include data packet service attribute information. See S301c for details.

[0157] S301c, UE-DLL obtains the third parameter and adjusts the transmission strategy of the uplink data packet corresponding to the first service flow based on the third parameter.

[0158] In some embodiments, the second control information can be used to request the UE-TLL to provide data delay parameters, i.e., the third parameter can be a data delay parameter. The UE-DLL can adjust the transmission strategy of the uplink data packets corresponding to the first service flow based on the data delay parameter. The data delay parameter can be used to indicate the packet delay budget (PDB) of the first data packet, where the first data packet is the data packet corresponding to the first service flow.

[0159] Optionally, the data delay parameter may indicate the PDB of the first data packet, or it may indicate the PDB offset of the first data packet.

[0160] When the data delay parameter indicates the PDB of the first data packet, the UE-DLL can adjust the discard timer based on the PDB of the first data packet after obtaining it. For example, assuming the discard timer for the first data packet is originally set to 10ms according to the reference PDB of the first service flow, and the UE-DLL determines the PDB of the first data packet to be 12ms based on the data delay parameter, then the UE-DLL can start the discard timer based on the PDB of 12ms. That is, the first data packet will only be discarded if it has not been sent after the discard timer has expired for 12ms.

[0161] When the data delay parameter indicates the PDB offset of the first data packet, after obtaining the PDB offset of the first data packet, the UE-DLL can determine the PDB of the first data packet based on the reference PDB of the first service flow and the PDB offset of the first data packet, and then adjust the discard timer according to the PDB of the first data packet. For example, assuming the reference PDB of the first service flow is 10ms, and the UE-DLL determines the PDB offset of the first data packet to be 2ms based on the data delay parameter, then the UE-DLL can determine the PDB of the first data packet to be 12ms, and start the discard timer based on the PDB of 12ms.

[0162] In some implementation scenarios, the PDB of uplink data packets, combined with the PDB of downlink data packets, affects the total data transmission latency, thus impacting user experience. Taking a gaming scenario as an example, the time it takes for the terminal device to receive user actions and transmit uplink data packets, and the time it takes for the server to render game footage and transmit downlink data packets, jointly determine the user experience. If the time it takes for the terminal device to receive user actions and transmit uplink data packets is long, the time it takes for the server to render game footage and transmit downlink data packets can be shortened. Conversely, if the time it takes for the server to render game footage and transmit downlink data packets is long, the time it takes for the terminal device to receive user actions and transmit uplink data packets can be shortened. In this embodiment, the UE-TLL can provide data latency parameters to the UE-DLL, allowing the UE-DLL to flexibly adjust the PDB of uplink data packets based on these parameters.

[0163] Scenario 4: Regarding the UE-TLL requesting the first transmission parameter from the RAN-DLL, to distinguish it from Scenario 3, in this scenario, the first transmission parameter is described as the fourth parameter. The fourth parameter can be understood as the parameter provided by the UE-TLL to the RAN-DLL. The fourth parameter can be used by the RAN-DLL to optimize data transmission. The fourth parameter may include data packet service attribute information; for details, see S301d.

[0164] In step S301d, the UE-DLL sends the fourth parameter to the RAN. Correspondingly, the RAN receives the fourth parameter from the UE-DLL.

[0165] Specifically, the UE-DLL can parse the first perception layer header of the first uplink data packet to obtain the fourth parameter, and then carry the fourth parameter in the second data link layer header, sending the second data link layer header to the RAN. Optionally, the second data link layer header can be the data link layer header of the first uplink data packet, or it can be the data link layer header of other uplink data packets corresponding to the first service flow.

[0166] It is understandable that scenarios one through four can be combined arbitrarily. That is, the terminal device can carry any one of the four types of information, including the first information, the second information, the third parameter, and the fourth parameter, in the first perception layer header of the first uplink data packet, or it can carry any combination of the four types. The specific combination can be determined according to actual needs.

[0167] Optionally, if the terminal device carries first information in the first perception layer packet header, the terminal device may delete the first information from the first perception layer packet header when or after the UE-DLL executes step S301a. Similarly, if the terminal device carries a third parameter in the first perception layer packet header, the terminal device may delete the third parameter from the first perception layer packet header when or after the UE-DLL executes step S301c, which helps to save bit overhead.

[0168] S302, UE-DLL sends a second uplink data packet to RAN. Correspondingly, RAN receives the second uplink data packet from UE-DLL. The second uplink data packet includes a third data link layer header, which carries second information and / or a fourth parameter.

[0169] S302 describes the process for scenarios two and four above. Specifically, after receiving the first uplink data packet from the UE-TLL, the UE-DLL learns the second information and / or the fourth parameter. The UE-DLL can then send these parameters to the RAN. Since the UE-DLL might process the first uplink data packet before sending it to the RAN, or it might know the second information and / or the fourth parameter and include them in a new data packet before sending it to the RAN, a second uplink data packet is introduced as the uplink data packet sent by the UE-DLL to the RAN. It should be noted that the first and second uplink data packets may be the same or different. In different scenarios, the UE-DLL can modify the first uplink data packet to obtain the second uplink data packet.

[0170] Optionally, the identifier of the second uplink data packet can be the same as or different from the identifier of the first uplink data packet. Here, the second information and / or the fourth parameter are carried in the third data link layer header, which can avoid the access network device resolving protocol layers above the network layer (IP).

[0171] In some embodiments, the third data link layer packet header may carry second information. After obtaining the second information, the RAN may send the second parameter to the terminal device based on the second information. Optionally, the RAN may send the second parameter to the terminal device in any of the following two ways:

[0172] Method 1: RAN directly sends the second parameter to the terminal device.

[0173] S302a, the RAN sends the second parameter to the UE based on the second information. Accordingly, the UE receives the second parameter from the RAN.

[0174] Specifically, the RAN can generate a second parameter based on the second information, carry the second parameter in the data link layer header, and then send the data link layer header to the UE-DLL. The access network device can add the data link layer header carrying the second parameter to the downlink data packet corresponding to the first service flow. Optionally, the RAN can send the second parameter in the perception layer header to the UE.

[0175] S302b, UE-DLL sends the second parameter to UE-TLL. Correspondingly, UE-TLL receives the second parameter from UE-DLL.

[0176] After the UE-DLL obtains the data link layer header carrying the second parameter, it can extract the second parameter from the data link layer header. Then, the terminal device can carry the second parameter extracted by the UE-DLL in the perception layer header and send this perception layer header carrying the second parameter to the UE-TLL. Upon receiving this perception layer header, the UE-TLL can obtain the second parameter from it.

[0177] In Method 1, the RAN carries the second parameter in the data link layer header and sends this header to the terminal device. The UE-DLL then extracts the second parameter from the data link layer header and carries it in the perception layer header before sending it to the UE-TLL. In this way, the terminal device carries the second parameter in the perception layer header instead of the access network device, avoiding the access network device from modifying the headers above the network layer.

[0178] Method 2: RAN indirectly sends the second parameter to the terminal device.

[0179] Specifically, the RAN can send a second parameter to the core network equipment, so that the core network equipment can carry the second parameter in the perception layer header of the downlink data packet, and then send the downlink data packet with the perception layer header carrying the second parameter to the terminal equipment through the access network equipment. For example, the access network equipment can specifically carry the second parameter in the GTP-U header and send it to the core network equipment. That is, the access network equipment can add the GTP-U header carrying the second parameter to the uplink data packet corresponding to the first service flow. After the core network equipment obtains the GTP-U header, it can extract the second parameter from the GTP-U header, carry the second parameter in the perception layer header, and send the perception layer header carrying the second parameter to the access network equipment, which then sends the perception layer header carrying the second parameter to the terminal equipment.

[0180] In Method 2, the RAN carries the second parameter in the GTP-U header and sends this GTP-U header to the core network device. The core network device then extracts the second parameter from the GTP-U header, carries it in the perception layer header, and sends it to the access network device. Finally, the access network device sends this perception layer header to the terminal device. By having the core network device carry the second parameter in the perception layer header instead of the access network device, the access network device avoids modifying the headers above the network layer.

[0181] S302c, UE-TLL adjusts the transmission strategy of uplink data packets corresponding to the first service flow based on the second parameter.

[0182] In one implementation scenario, when the second parameter includes a reference transmission rate, the second information can be used to request the reference transmission rate. The UE-TLL can adjust the transmission strategy of the uplink data packets corresponding to the first service flow based on the reference transmission rate. Specifically, the reference transmission rate can indicate the maximum transmission rate that the RAN can provide for the terminal device, or it can indicate the maximum transmission rate that the RAN can provide for the first service flow. The UE-TLL can adjust the value of the congestion window based on the reference transmission rate when initiating congestion control for the first service flow. For example, assuming the reference transmission rate is 500 Mbps, the UE-TLL can use a larger congestion window value (e.g., 250 Mbps) instead of starting with a smaller value (e.g., 1 Mbps) when setting the congestion window, thereby reducing the time consumed by the probing mechanism and improving bandwidth utilization.

[0183] In another implementation scenario, if the second parameter includes the predicted transmission rate, the second information can be used to request the predicted transmission rate. The UE-TLL can adjust the transmission strategy of the uplink data packets corresponding to the first service flow based on the predicted transmission rate. Specifically, the predicted transmission rate can indicate the maximum transmission rate the RAN can provide for the first service flow at a certain predicted time. The UE-TLL can adjust the application layer coding of the first service flow based on the predicted transmission rate, such as adjusting the service frame rate or resolution. For example, assuming the current rate of 100Mbps supports 2k resolution transmission for the first service flow, and the predicted transmission rate indicates that the maximum transmission rate the RAN can provide for the first service flow after 2 seconds changes to 20Mbps, the UE-TLL can reduce the resolution to 1080p in advance, thereby improving the stability of data transmission.

[0184] In another implementation scenario, when the second parameter includes a data timing parameter, the second information can be used to request the data timing parameter. The UE-TLL can adjust the transmission strategy of the uplink data packet corresponding to the first service flow based on the data timing parameter. Specifically, the data timing parameter can indicate the time when the RAN expects the UE-TLL to send the data packet. The UE-TLL can adjust the sending time of the uplink data packet corresponding to the first service flow based on the data timing parameter. For periodic services, by indicating the expected time to send the data packet to the UE-TLL, the RAN can avoid the time when each data packet arrives at the RAN too close, and avoid the situation where the access network device needs to schedule a large number of data packets in a short period of time when the PDB requirement is tight. For example, please refer to Figure 4, which is a schematic diagram of a UE-TLL sending data packets according to an embodiment of this application. As shown in Figure 4 (1), the UE-TLL sends data packets 401, 402, and 403 in the periodic service at similar times. In the case shown in Figure 4 (1), the arrival times of data packets 401, 402, and 403 at the RAN are also similar. If the PDB requirements for data packets 401, 402, and 403 are tight, it means that the access network equipment needs to send all the data packets out in a short period of time, which increases the scheduling pressure on the access network equipment. As shown in Figure 4(2), the UE-TLL can distribute the sending of data packets 401, 402, and 403 based on the data timing parameters provided by the RAN. In the case shown in Figure 4(2), the arrival times of data packets 401, 402, and 403 at the RAN will be more dispersed, which helps to alleviate the scheduling pressure on the access network equipment.

[0185] In some embodiments, the third data link layer packet header may carry a fourth parameter, and the RAN may adjust the transmission strategy of the uplink data packets corresponding to the first service flow based on the fourth parameter.

[0186] S302d, the RAN adjusts the transmission strategy of the uplink data packets corresponding to the first service flow based on the fourth parameter.

[0187] In some embodiments, before executing step S302b, the RAN may send third control information to the terminal device. This third control information can be used to request the terminal device to provide a fourth parameter. The fourth parameter can be used by the RAN to optimize data transmission. The fourth parameter may include data packet service attribute information. The way the RAN sends the third control information to the terminal device is similar to the way the RAN sends the second parameter to the terminal device, and may include direct sending and indirect sending. Direct sending includes: the RAN carrying the third control information in the data link layer header, sending the data link layer header to the terminal device, and the UE-DLL extracting the third control information from the data link layer header, then carrying the third control information in the perception layer header and sending it to the UE-TLL. Indirect sending includes: the RAN sending the third control information to the core network device, the core network device carrying the third control information in the perception layer header, then sending the perception layer header carrying the third control information back to the RAN, and finally the RAN sending a downlink data packet carrying the perception layer header with the third control information to the terminal device.

[0188] In one implementation scenario, when the fourth parameter includes a data sequence parameter, the third control information can be used to request the data sequence parameter. The RAN can adjust the transmission strategy of the uplink data packets corresponding to the first service flow based on the data sequence parameter. Specifically, the data sequence parameter can be used to identify data packets in different groups. A group of data packets typically corresponds to a complete application function. For example, all data packets corresponding to an image can be grouped into group A, all data packets corresponding to an AI model can be grouped into group B, all data packets corresponding to a file can be grouped into group C, and all data packets corresponding to a 3D object model can be grouped into group D. Optionally, data packets within the same group can use the same identifier as the data sequence parameter. For example, all data packets corresponding to image A1 can use identifier 1 as the data sequence parameter, all data packets corresponding to image A2 can use identifier 2, all data packets corresponding to file C1 can use identifier 3, and so on. In this case, the RAN can determine the group to which each data packet belongs based on its data sequence parameter, thereby enabling fine-grained management of the uplink transmission time of data packets within the same group. Optionally, data packets within the same group can also use the identifiers of the start and end positions of the data packets as data sequence parameters. For example, data packet 'a' at the starting position corresponding to image A1 can use identifier 'a1' as its data sequence parameter, and data packet 'b' at the ending position corresponding to image A1 can use identifier 'b1' as its data sequence parameter; data packet 'c' at the starting position corresponding to image A2 can use identifier 'c2' as its data sequence parameter, and data packet 'd' at the ending position corresponding to image A2 can use identifier 'd2' as its data sequence parameter, and so on. In this case, the RAN can determine whether data packets belonging to the same group have been transmitted completely based on the data sequence parameters of the data packets at the starting and ending positions within the same group, thereby enabling fine-grained management of the uplink transmission time of data packets belonging to the same group.

[0189] In another implementation scenario, when the fourth parameter includes a data failure parameter, the third control information can be used to request the data failure parameter. The RAN can adjust the transmission strategy of the uplink data packets corresponding to the first service flow based on the data failure parameter. Specifically, the data failure parameter can be used to identify failed data packets within the same data packet group. Based on the data failure parameter, the RAN can stop transmitting failed data packets to the server to save transmission resources and reduce the transmission latency of other unfailed data packets.

[0190] In another implementation scenario, where the fourth parameter includes a data importance level parameter, the third control information can be used to request the data importance level parameter. The RAN can then adjust the transmission strategy of the uplink data packets corresponding to the first service flow based on the data importance level parameter. For example, when transmitting high-importance data packets, the RAN can use a smaller PDB for transmission to improve the transmission reliability of high-importance data packets.

[0191] S303, the RAN sends a third uplink data packet to the CN. Correspondingly, the CN receives the third uplink data packet from the RAN. The third uplink data packet includes seventh control information and / or fifth transmission parameters.

[0192] Regarding the seventh control information, it can be used to request the sixth transmission parameters. The sixth transmission parameters can be used by the RAN for data transmission optimization. Therefore, the sixth transmission parameters can be understood as parameters provided by the TLL (such as UE-TLL and / or Server-TLL) to the RAN-DLL. Specifically, the sixth transmission parameters may include data packet service attribute information.

[0193] Since TLL can be UE-TLL and / or Server-TLL, it is described in scenarios A and B below.

[0194] Scenario A: Regarding the RAN requesting the sixth transmission parameter from the UE-TLL, to distinguish it from Scenario B, in this scenario, the sixth transmission parameter is described as the fifth parameter, and the seventh control information in this scenario is described as the third information. The fifth parameter can be understood as the parameter provided by the UE-TLL to the RAN-DLL. The fifth parameter can be used by the RAN to optimize data transmission. The fifth parameter may include data packet service attribute information. That is, the access network device can carry the third information in the third uplink data packet, for example, it can carry the third information in the GTP-U header, and then the core network device can carry the third information in the perception layer header of the downlink data packet corresponding to the first service flow, so that the terminal device can obtain the third information from the perception layer header of the downlink data packet corresponding to the first service flow, and then control the UE-TLL to provide the fifth parameter to the RAN-DLL. For details, see 303a-303c.

[0195] S303a, the CN sends third information to the UE. Accordingly, the UE receives the third information from the CN.

[0196] Specifically, the CN can carry the third information in the fifth perception layer header, allowing the core network device to send the fifth perception layer header to the terminal device via the access network device. Optionally, the core network device can carry the third information in the perception layer header of the downlink data packet corresponding to the first service flow.

[0197] S303b, the UE-awareness layer sends third information to the UE-TLL. Correspondingly, the UE-TLL receives the third information from the UE-awareness layer.

[0198] Among them, the UE-perception layer can parse the perception layer header of the downlink data packet to obtain the third information, and then send the third information to the UE-TLL.

[0199] S303c, UE-TLL generates the fifth parameter based on the third information.

[0200] After the UE-TLL generates the fifth parameter, it can send the fifth parameter to the UE-Perception Layer. Upon receiving the fifth parameter, the UE-Perception Layer can include it in its perception layer header and then send a perception layer header containing the fifth parameter to the UE-DLL. Upon receiving the perception layer header containing the fifth parameter, the UE-DLL can retrieve the fifth parameter from the header, include it in its data link layer header, and send the data link layer header to the RAN.

[0201] Scenario B involves the RAN requesting the sixth transmission parameter from the Server-TLL. To distinguish it from Scenario A, in this scenario, the sixth transmission parameter is described as the sixth parameter, and the seventh control information is described as the fourth information. The sixth parameter can be understood as the parameter provided by the Server-TLL to the RAN-DLL. The sixth parameter may include data packet service attribute information. The sixth parameter can be used by the RAN to optimize data transmission. That is, the access network device can carry the fourth information in the third uplink packet, and then the core network device can carry the fourth information in the perception layer header of the uplink data packet corresponding to the first service flow, so that the server can obtain the fourth information from the perception layer header of the uplink data packet corresponding to the first service flow, and then control the Server-TLL to provide the fifth parameter to the RAN.

[0202] Regarding the fifth transmission parameter, it can be used by the TLL to optimize data transmission. Therefore, the fifth transmission parameter can also be understood as the parameter provided by the RAN-DLL to the TLL (such as UE-TLL and / or Server-TLL). The fifth transmission parameter may include the transmission parameters of the data link.

[0203] Since TLL can be UE-TLL and / or Server-TLL, it is described in scenarios C and D below.

[0204] Scenario C: For the RAN providing the fifth transmission parameter to the UE-TLL, to distinguish it from Scenario D, in this scenario, the fifth transmission parameter is described as the seventh parameter. The seventh parameter can be understood as the parameter provided by the RAN-DLL to the UE-TLL. The seventh parameter can be used by the TLL to optimize data transmission. The seventh parameter may include data link transmission parameters. See S303d-S303f below for details.

[0205] In S303d, the CN sends the seventh parameter to the UE. Accordingly, the UE receives the seventh parameter from the CN.

[0206] Specifically, the CN can carry the seventh parameter in the eighth perception layer header, allowing the core network device to send the eighth perception layer header to the terminal device via the access network device. Optionally, the core network device can carry the seventh parameter in the perception layer header of the downlink data packet corresponding to the first service flow.

[0207] S303e, the UE-awareness layer sends the seventh parameter to the UE-TLL. Correspondingly, the UE-TLL receives the seventh parameter from the UE-awareness layer.

[0208] S303f, UE-TLL adjusts the transmission strategy of uplink data packets corresponding to the first service flow based on the seventh parameter.

[0209] Scenario D: For the RAN providing the fifth transmission parameter to the Server-TLL, to distinguish it from Scenario C, the fifth transmission parameter is described as the eighth parameter in this scenario. The eighth parameter can be understood as the parameter provided by the RAN-DLL to the Server-TLL. The eighth parameter can be used by the TLL to optimize data transmission. The eighth parameter can include data link transmission parameters. That is, the access network device can carry the eighth parameter in the third uplink data packet, and then the core network device can carry the eighth parameter in the perception layer header of the uplink data packet corresponding to the first service flow. This allows the server to obtain the eighth parameter from the perception layer header of the uplink data packet corresponding to the first service flow, and then the server can adjust the transmission strategy of the downlink data packet corresponding to the first service flow based on the eighth parameter.

[0210] S304, CN sends a fourth uplink data packet to the server. Correspondingly, the server receives the fourth uplink data packet from CN. The fourth uplink data packet includes a ninth sensing layer header, which carries fourth information and / or an eighth parameter.

[0211] S304 describes the process for scenarios B and D above. Specifically, after receiving the third uplink data packet from the RAN, the CN learns the fourth information and / or the eighth parameter. The CN can then send these parameters to the server. Since the CN may process the first uplink data packet before sending it to the server, or the CN may learn the fourth information and / or the eighth parameter and then include them in a new data packet before sending it to the server, a fourth uplink data packet is introduced as the uplink data packet sent by the CN to the server.

[0212] In some embodiments, the ninth sensing layer header carries fourth information, as specifically described in S304a-304c below.

[0213] S304a, the server sends the sixth parameter to the CN based on the fourth information. Correspondingly, the CN receives the sixth parameter.

[0214] The server can generate the sixth parameter based on the fourth information. After generating the sixth parameter, the server can include the sixth parameter in the perception layer header and then send the perception layer header containing the sixth parameter to the CN.

[0215] In S304b, the CN sends the sixth parameter to the RAN. Correspondingly, the RAN receives the sixth parameter from the CN.

[0216] The CN can receive the sensing layer header carrying the sixth parameter, obtain the sixth parameter from the sensing layer header, and then send the sixth parameter to the RAN.

[0217] S304c, the RAN adjusts the transmission strategy of the downlink data packets corresponding to the first service flow based on the sixth parameter.

[0218] In one implementation scenario, when the sixth parameter includes a data delay parameter, the RAN can adjust the transmission strategy of the downlink data packets corresponding to the first service flow based on the data delay parameter. Specifically, the data delay parameter can be used to indicate the PDB of the first data packet, or it can indicate the PDB offset of the first data packet, where the first data packet is the data packet corresponding to the first service flow. The RAN can determine the PDB of the data packet based on the data delay parameter. Furthermore, the RAN can schedule the data packets according to the determined PDB. For example, assuming the data delay parameter indicates that the PDB offset of the first data packet is 4ms, and the reference PDB of the data packet corresponding to the first service flow is 10ms, then the RAN can determine that the PDB of the first data packet is 14ms. Therefore, the RAN can schedule the first data packet based on 14ms, meaning the RAN can send the first data packet out within 14ms. This alleviates the scheduling pressure on the access network equipment compared to the RAN scheduling the first data packet based on 10ms. In this way, the server can dynamically indicate the PDB of different data packets to the access network equipment when transmitting different data packets, thus improving the flexibility of data transmission.

[0219] In another implementation scenario, when the sixth parameter includes a data sequence parameter, the RAN can adjust the transmission strategy of downlink data packets corresponding to the first service flow based on the data sequence parameter. Specifically, the RAN can determine whether packets belonging to the same group have been transmitted completely based on the data sequence parameter, thereby enabling fine-grained management of the downlink transmission time of data packets within the same group.

[0220] In another implementation scenario, when the sixth parameter includes a data failure parameter, the RAN can adjust the transmission strategy of the downlink data packets corresponding to the first service flow based on the data failure parameter. Specifically, the RAN can stop transmitting failed data packets to the terminal device based on the data failure parameter to save transmission resources and reduce the transmission latency of other valid data packets.

[0221] In another implementation scenario, where the sixth parameter includes a data importance level parameter, the RAN can adjust the transmission strategy of the downlink data packets corresponding to the first service flow based on the data importance level parameter. For example, when transmitting data packets with high importance level, the RAN can use a smaller PDB for transmission to improve the transmission reliability of high-importance data packets.

[0222] In some embodiments, the ninth sensing layer header may carry an eighth parameter, as detailed in section 304d below.

[0223] S304d, the server adjusts the transmission strategy of the downlink data packets corresponding to the first service flow based on the eighth parameter.

[0224] In some embodiments, the server may send eighth control information to the access network device, which can be used to request the access network device to provide an eighth parameter. The method by which the server sends the eighth control information to the access network device may include: the server carrying the eighth control information in a perception layer header and sending the perception layer header carrying the eighth control information to the CN; the CN obtaining the eighth control information from the perception layer header and sending the eighth control information to the RAN.

[0225] In one implementation scenario, where the eighth parameter includes a reference transmission rate, the eighth control information can be used to request the reference transmission rate. The server can then adjust the transmission strategy of the downlink data packets corresponding to the first service flow based on the reference transmission rate. For example, when initiating congestion control for the first service flow, the server can adjust the value of the congestion window based on the reference transmission rate, thereby avoiding starting with an excessively small congestion window value.

[0226] In another implementation scenario, where the eighth parameter includes the predicted transmission rate, the eighth control information can be used to request the predicted transmission rate. The server can predict the transmission rate and adjust the downlink transmission strategy of the data packets corresponding to the first service flow. Specifically, the predicted transmission rate can indicate the maximum transmission rate that the RAN can provide for the first service flow at a given predicted time. Based on the predicted transmission rate, the server can adjust the application layer coding of the first service flow, such as adjusting the service frame rate or resolution. In this way, the server can reduce the service frame rate or resolution in advance before the transmission rate corresponding to the first service flow decreases, avoiding playback stuttering.

[0227] In another implementation scenario, the eighth parameter includes the Server-Data Timing Parameter, and the eighth control information can be used to request the Server-Data Timing Parameter. The server can adjust the transmission strategy of the downlink data packets corresponding to the first service flow based on the Server-Data Timing Parameter. Specifically, the Server-Data Timing Parameter can indicate to the RAN the expected time for the server to send data packets. The server can adjust the transmission time of the downlink data packets corresponding to the first service flow based on the Server-Data Timing Parameter. For periodic services, by indicating the expected time for sending data packets to the server, the RAN can avoid data packets arriving at the RAN at too close times, thus preventing access network devices from needing to schedule a large number of data packets in a short period of time when PDB requirements are tight.

[0228] In the embodiment shown in Figure 3, by introducing a perception layer, different protocol layers can interact more efficiently based on the perception layer, and the solution is universal, which helps to improve data transmission efficiency and enhance data transmission performance.

[0229] It should be noted that the scenarios involved in the embodiments of this application can be presented separately or in combination. For example, scenarios one to four can be arbitrarily combined, and scenarios A to D can be arbitrarily combined, etc. The presentation format of control information and transmission parameters can differ for different scenarios. For example, for scenario one, the first control information can be the first information; for scenario two, the first control information can be the second information; and for a combination of scenario one and scenario two, the first control information can include both the first and second information. Similarly, for scenario C, the fifth transmission parameter can be the seventh parameter; for scenario D, the fifth transmission parameter can be the eighth parameter; and for a combination of scenario C and scenario D, the fifth transmission parameter can include both the seventh and eighth parameters. It is understood that the different descriptions of control information and transmission parameters are introduced to distinguish control information and transmission parameters under different scenarios and do not constitute a limitation of this application.

[0230] Figure 3 illustrates an embodiment of this application from the perspective of sending uplink data packets from the terminal device to the server. The following describes an embodiment of this application from the perspective of sending downlink data packets from the server to the terminal device.

[0231] Please refer to Figure 5, which is a flowchart illustrating another communication method provided in an embodiment of this application. Taking downstream transmission as an example, Figure 5 may include, but is not limited to, the following steps:

[0232] S501, the server sends downlink data packet A to the CN. Correspondingly, the CN receives downlink data packet A from the server. Downlink data packet A includes a sensing layer header A, which includes control information A and / or transmission parameters A.

[0233] Control information A can be used to request transmission parameters B, which can be understood as parameters provided by the RAN-DLL to the Server-TLL. Transmission parameters B can be used by the TLL to optimize data transmission and may include data link transmission parameters.

[0234] In some embodiments, the sensing layer packet header A may carry control information A. The CN obtains the control information A from the sensing layer packet header A and then sends the control information A to the RAN. Specifically, see S501a-501c below.

[0235] S501a, CN sends control information A to RAN. Correspondingly, RAN receives control information A from CN.

[0236] For example, the CN can carry control information A in the GTP-U packet header and then send the GTP-U packet header carrying control information A to the RAN. The RAN can obtain control information A from the GTP-U packet header.

[0237] In S501b, the RAN sends transmission parameters B to the server based on control information A. Correspondingly, the server receives transmission parameters B from the RAN.

[0238] The RAN can generate transmission parameter B based on control information A. After generating transmission parameter B, the RAN can send transmission parameter B to the CN. The CN can then include transmission parameter B in the sensing layer header and send a sensing layer header containing transmission parameter B to the server. After receiving the sensing layer header containing transmission parameter B, the server can retrieve transmission parameter B from the sensing layer header.

[0239] S501c, the server adjusts the transmission strategy of the downlink data packets corresponding to the first service flow based on transmission parameter B.

[0240] The implementation principle and process of step S501c are similar to those of step S304d above, and will not be repeated here.

[0241] In some embodiments, the perception layer packet header A may carry transmission parameter A, which can be understood as parameters provided by the Server-TLL to the RAN-DLL. Transmission parameter A can be used by the RAN to optimize data transmission. Transmission parameter A may include data service packet attribute information. The CN can obtain transmission parameter A from the perception layer packet header A and then send transmission parameter A to the RAN. Specifically, see S501d and S501e below.

[0242] In step S501d, the CN sends transmission parameter A to the RAN. Correspondingly, the RAN receives transmission parameter A from the CN.

[0243] The implementation principle of step S501d is similar to that of step S501a above, and will not be repeated here.

[0244] In S501e, the RAN adjusts the transmission strategy of the downlink data packets corresponding to the first service flow based on transmission parameter A.

[0245] Here, the implementation principle and process of step S501e are similar to those of step S304c above, and will not be repeated here.

[0246] S502, CN sends downlink data packet B to RAN. Correspondingly, RAN receives downlink data packet B from CN. Downlink data packet B includes control information B and / or transmission parameters C.

[0247] Regarding control information B, control information B can be used to request transmission parameters d1 and / or d2. Transmission parameter d1 can be understood as the parameters provided by the RAN-DLL to the Server-TLL. Transmission parameter d1 can be used by the TLL for transmission optimization. Transmission parameter d1 may include data link transmission parameters. Transmission parameter d2 can be understood as the parameters provided by the UE-TLL to the RAN-DLL. Transmission parameter d2 can be used by the RAN for data transmission optimization. Transmission parameter d2 may include data packet service attribute information. Since control information B can be used to request transmission parameters d1 and / or d2, it is described in scenarios 1 and 2 below.

[0248] Scenario 1: Control information B is used to request the transmission parameter d1. To distinguish it from Scenario 2, in this scenario, control information B is described as control information b1. For details, please refer to S502a below.

[0249] S502a, the RAN generates transmission parameters d1 based on control information b1.

[0250] After receiving control information b1, the RAN can generate transmission parameters d1 based on the control information b1. Next, the RAN can carry transmission parameters d1 in the perception layer header through the core network equipment, and then send the perception layer header carrying transmission d1 to the server.

[0251] Scenario 2: For control information B used to request transmission parameter d2, to distinguish it from Scenario 1, in this scenario, control information B is described as control information b2. See S502b and S502c below for details.

[0252] In step S502b, the RAN sends control information b2 to the UE. Accordingly, the UE receives control information b2 from the RAN.

[0253] In this configuration, the CN can include control information b2 in the perception layer header and send the perception layer header containing control information b2 to the RAN. The RAN can then send this perception layer header containing control information b2 to the UE. The UE-perception layer can then retrieve the control information b2 from the perception layer header and send information b2 to the UE-TLL. Optionally, the RAN can also include control information b2 in the perception layer header and send the perception layer header containing control information b2 to the UE.

[0254] S502c, UE-TLL generates transmission parameters d2 based on control information b2.

[0255] After receiving control information b2, the UE-TLL can generate transmission parameters d2 based on the control information b2. Here, transmission parameters d2 can be carried in the data link layer header of the uplink data packet corresponding to the first service flow and sent to the access network device.

[0256] Regarding transmission parameter C, transmission parameter C may include transmission parameter c1 and / or transmission parameter c2. Transmission parameter c1 can be understood as the parameter provided by the Server-TLL to the RAN-DLL. Transmission parameter c1 can be used by the RAN to optimize data transmission. Transmission parameter c1 may include data packet service attribute information. Transmission parameter c2 can be understood as the parameter provided by the RAN-DLL to the UE-TLL. Transmission parameter c2 can be used by the TLL to optimize data transmission. Transmission parameter c2 may include data link transmission parameters. Since transmission parameter C may include transmission parameter c1 and / or transmission parameter c2, it will be described in scenarios 3 and 4 below.

[0257] Scenario 3: For transmission parameter C, including transmission parameter c1, see step S502d below.

[0258] S502d, the RAN adjusts the transmission strategy of the downlink data packets corresponding to the first service flow based on the transmission parameter c1.

[0259] Here, the implementation principle and process of step S502d are similar to those of step S304c above, and will not be repeated here.

[0260] Scenario 4: For transmission parameter C, including transmission parameter c2, please refer to steps S502e and S502f below.

[0261] S502e, the RAN sends transmission parameter c2 to the UE. Accordingly, the UE receives transmission parameter c2 from the RAN.

[0262] Specifically, the CN can include the transmission parameter c2 in the sensing layer header and send the sensing layer header containing the transmission parameter c2 to the RAN. The RAN can then send this sensing layer header containing the transmission parameter c2 to the UE-sensing layer. The UE-sensing layer can then retrieve the transmission parameter c2 from the sensing layer header and send it to the UE-TLL. Optionally, the RAN can also include the transmission parameter c2 in the sensing layer header and send it to the UE.

[0263] S502f, UE-TLL adjusts the transmission strategy of the uplink data packets corresponding to the first service flow based on transmission parameter c2.

[0264] Here, the implementation principle and process of step S502f are similar to those of step S302c above, and will not be repeated here.

[0265] S503, the RAN sends a downlink data packet C to the UE. Correspondingly, the UE receives the downlink data packet C from the RAN. The downlink data packet C includes control information C and / or transmission parameters D.

[0266] Specifically, control information C can be used to request transmission parameters E, which can be understood as parameters provided by the UE-TLL to the RAN-DLL. Transmission parameters E can be used by the RAN to optimize data transmission. Transmission parameters E may include data packet service attribute information. Transmission parameters D can be understood as parameters provided by the RAN-DLL to the UE-TLL. Transmission parameters D can be used by the TLL to optimize transmission. Transmission parameters D may include data link transmission parameters.

[0267] In some embodiments, the downlink data packet C may include a sensing layer header, which may include control information C and / or transmission parameters D. In this case, the RAN may first send the control information C and / or transmission parameters D to the CN, and the CN may then send the sensing layer header containing the control information C and / or transmission parameters D to the RAN.

[0268] In some embodiments, the downlink data packet C may include a data link layer header, which may include control information C and / or transmission parameters D. In this case, the RAN may carry the control information C and / or transmission parameters D in the data link layer header and then send the data link layer header carrying the control information C and / or transmission parameters D to the UE-DLL.

[0269] Optionally, the RAN may also include the control information C and / or transmission parameters D in the sensing layer header and then send the sensing layer header containing the control information C and / or transmission parameters D to the UE-DLL.

[0270] In the embodiment shown in Figure 5, by introducing a perception layer, different protocol layers can interact more efficiently based on the perception layer, and the solution is universal, which helps to improve data transmission efficiency and enhance data transmission performance.

[0271] In this embodiment, the aforementioned protocol layer interaction mechanism based on the perception layer can be triggered by the Session Description Protocol (SDP). SDP is an application layer control protocol used to describe multimedia sessions. It is a text-based protocol that can be used for negotiating media types and encoding schemes during session establishment. For example, please refer to Figure 6, which is a schematic diagram of the position of the SDP protocol in the protocol stack according to an embodiment of this application. In one implementation, the terminal device, core network device, and server can negotiate and trigger the perception layer protocol through the SDP protocol. For example, the terminal device can request the server to trigger the perception layer protocol based on the SDP protocol. After the server confirms the triggering, the terminal device, core network device, and server can perform interactions between different protocol layers based on the perception layer.

[0272] It should be noted that, in the embodiments of this application, the sending of packet header A from protocol layer A to protocol layer B can be understood as protocol layer A sending a data packet including packet header A to protocol layer B. The data packets involved in the embodiments of this application can be data packets associated with the same service flow. Furthermore, the control information sent from DLL to TLL in the embodiments of this application can also be described as D2T control information, specifically divided into uplink D2T control information and downlink D2T control information. For example, the control information sent from RAN-DLL to Server-TLL can be described as uplink D2T control information, and the control information sent from RAN-DLL to UE-TLL can be described as downlink D2T control information. The transmission parameters sent from DLL to TLL can also be described as D2T transmission parameters, specifically divided into uplink D2T transmission parameters and downlink D2T transmission parameters. Similarly, the control information sent from TLL to DLL can also be described as T2D control information, specifically divided into uplink T2D control information and downlink T2D control information. For example, the control information sent by the UE-TLL to the RAN-DLL can be described as uplink T2D control information, and the control information sent by the Server-TLL to the RAN-DLL can be described as downlink T2D control information. The transmission parameters sent by the TLL to the DLL can also be described as T2D transmission parameters, which can be specifically divided into uplink T2D transmission parameters and downlink T2D transmission parameters.

[0273] In addition, to implement the embodiments of this application, this application also provides a general design for a sensing layer header, which can be carried in uplink data packets or downlink data packets. Please refer to Table 1, which shows an example of information carried in a sensing layer header:

[0274] Table 1

[0275] The "Empty Packet Indicator" field indicates the absence of a perception layer header in subsequent data packets. The "Flow Identifier" identifies the first service flow. The "End Bit" indicates whether the information has ended; for example, a 0 value for the end bit of D2T control information indicates the end of the D2T control information, while a 1 value indicates that the next line is still D2T control information. Each bit in the "D2T Control Information" field can represent a request switch; for example, the first bit can represent a request switch for the reference transmission rate. A first bit value of 1 indicates that the D2T control information requests the reference transmission rate (i.e., requesting the reference transmission rate to be enabled), while a first bit value of 0 indicates that the D2T control information does not request the reference transmission rate (i.e., requesting the reference transmission rate to be disabled). The "D2T Transmission Parameter Existence Indicator" field indicates the existence of D2T transmission parameters, specifically including the field length and a field bitmap. Each bit in the bitmap can indicate the existence of a specific D2T transmission parameter. The "D2T Transmission Parameter: Reference Transmission Rate" field indicates the reference transmission rate. Whether the parameter transmission rate is the uplink or downlink reference transmission rate can be determined based on whether it is carried in the sensing layer header in the uplink or downlink data packet. The "T2D Transmission Parameter Existence Indication" field indicates the existence of T2D transmission parameters. Specifically, it can include the field length and a bitmap. Each bit in the bitmap can be used to indicate the existence of a specific T2D transmission parameter.

[0276] This application provides a communication device that can be used to implement the functions of the aforementioned terminal device, access network device, core network device, or server. The communication device can be a terminal device, access network device, core network device, or server. The communication device includes units corresponding to the methods / operations / steps / actions performed by the terminal device, access network device, core network device, or server in the above method embodiments. These units can be hardware circuits, software, or a combination of hardware circuits and software. Please refer to Figure 7, which shows a schematic diagram of the structure of a communication device 700 according to an embodiment of this application. The communication device 700 may include an interface unit 701 and a processing unit 702. Specifically, the processing unit 702 is used to process signaling and / or data, which may be data received by the interface unit 701, and the processed signaling and / or data may also be sent by the interface unit 701.

[0277] In one embodiment, when the communication device 700 is a terminal device, wherein:

[0278] Interface unit 701 is used to receive a first uplink data packet; the first uplink data packet includes a first perception layer header, the first perception layer header carries first control information and / or first transmission parameters; the first control information is used to request second transmission parameters; the first transmission parameters are parameters provided by the first application layer to the first data link layer; the second transmission parameters are parameters provided by the second data link layer to the first application layer; the first uplink data packet is a data packet corresponding to the first service flow.

[0279] In this embodiment, the specific implementation of the interface unit 701 and the processing unit 702 can be found in the specific implementation steps of the UE-DLL in Figures 3 and 5, and will not be repeated here.

[0280] In another embodiment, when the communication device 700 is a terminal device, wherein:

[0281] Interface unit 701 is used to send a first uplink data packet; the first uplink data packet includes a first perception layer header, the first perception layer header carries first control information and / or first transmission parameters; the first control information is used to request second transmission parameters; the first transmission parameters are parameters provided by the first application layer to the first data link layer; the second transmission parameters are parameters provided by the second data link layer to the first application layer; the first uplink data packet is a data packet corresponding to the first service flow.

[0282] In this embodiment, the specific implementation of the interface unit 701 and the processing unit 702 can be found in the specific implementation steps of UE-TLL in Figures 3 and 5, and will not be repeated here.

[0283] In yet another embodiment, when the communication device 700 is an access network device, wherein:

[0284] Interface unit 701 is used to receive a second uplink data packet from a terminal device; the second uplink data packet includes a third data link layer header, the third data link layer header carries second information and / or a fourth parameter; the second information is used to request the second parameter; the second parameter is a parameter provided by the data link layer of the access network device to the first application layer; the fourth parameter is a parameter provided by the first application layer to the data link layer of the access network device; the second uplink data packet is a data packet corresponding to the first service flow.

[0285] In this embodiment, the specific implementation of the interface unit 701 and the processing unit 702 can be found in the specific implementation steps of the access network device in Figures 3 and 5, and will not be repeated here.

[0286] In yet another embodiment, when the communication device 700 is a core network device, wherein:

[0287] Interface unit 701 is used to receive a third uplink data packet from an access network device; the third uplink data packet includes seventh control information and / or fifth transmission parameters; the seventh control information is used to request a sixth transmission parameter; the sixth transmission parameter is a parameter provided by the third application layer to the third data link layer; the fifth transmission parameter is a parameter provided by the fourth data link layer to the fourth application layer; the third uplink data packet is a data packet corresponding to the first service flow.

[0288] In this embodiment, the specific implementation of the interface unit 701 and the processing unit 702 can be found in the specific implementation steps of the core network equipment in Figures 3 and 5, and will not be repeated here.

[0289] In yet another embodiment, when the communication device 700 is a server, wherein:

[0290] Interface unit 701 is used to receive a fourth uplink data packet from a core network device; the fourth uplink data packet includes a ninth perception layer header, the ninth perception layer header carries fourth information and / or an eighth parameter; the fourth information is used to request a sixth parameter; the eighth parameter is a parameter provided by the data link layer of the access network device to the second application layer, and the sixth parameter is a parameter provided by the second application layer to the data link layer of the access network device; the fourth uplink data packet is a data packet corresponding to the first service flow.

[0291] In this embodiment, the specific implementation of the interface unit 701 and the processing unit 702 can be found in the specific implementation steps of the server in Figures 3 and 5, and will not be repeated here.

[0292] Figure 8 illustrates a communication device 800 provided in an embodiment of this application, used to implement the functions of the aforementioned terminal device, access network device, core network device, or server. This device can be a communication device or a device used within a communication device. The communication device can be a terminal device, access network device, core network device, or server. The device used within the communication device can be a chip system or a chip within the communication device. The chip system can be composed of chips or can include chips and other discrete components.

[0293] The communication device 800 includes at least one processor 810 for implementing the processing functions of the devices (e.g., terminal devices, access network devices, core network devices, or servers) in the methods provided in this application embodiment. The communication device 800 may also include a communication interface 820 for implementing the transmit and receive operations of the devices (e.g., terminal devices, access network devices, core network devices, or servers) in the methods provided in this application embodiment. In this application embodiment, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface for communicating with other devices via a transmission medium. For example, the communication interface 820 allows the devices in the communication device 800 to communicate with other devices. The processor 810 uses the communication interface 820 to transmit and receive data and is used to implement the methods described in the above method embodiments.

[0294] The communication device 800 may further include at least one memory 830 for storing program instructions and / or data. The memory 830 is coupled to the processor 810. The coupling in this embodiment is an indirect coupling or communication connection between devices, units, or modules, and can be electrical, mechanical, or other forms, for information exchange between devices, units, or modules. The processor 810 may operate in conjunction with the memory 830. The processor 810 may execute program instructions stored in the memory 830. At least one of the at least one memory may be included in the processor.

[0295] This embodiment does not limit the specific connection medium between the communication interface 820, processor 810, and memory 830. In Figure 8, the memory 830, processor 810, and communication interface 820 are connected via a bus, indicated by a thick line. The connection methods between other components are merely illustrative and not intended to be limiting. The bus can be categorized as an address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used in Figure 8, but this does not imply that there is only one bus or one type of bus.

[0296] When the communication device 800 is specifically a device used for equipment (such as terminal equipment, access network equipment, core network equipment, or server), for example, when the communication device 800 is specifically a chip or chip system, the communication interface 820 can output or receive baseband signals. When the communication device 800 is specifically a device (terminal equipment, access network equipment, core network equipment, or server), the communication interface 820 can output or receive radio frequency signals. In the embodiments of this application, the processor can be a general-purpose processor, digital signal processor, application-specific integrated circuit, field-programmable gate array or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, which can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly reflected as being executed by a hardware processor, or executed by a combination of hardware and software modules in the processor.

[0297] It should be noted that the aforementioned communication interface 820 can be used to perform the functions of the aforementioned interface unit 701, and the aforementioned processor 810 can be used to perform the functions of the aforementioned processing unit 702, which will not be elaborated further here.

[0298] When the aforementioned communication device is a chip applied to a terminal device, the chip implements the terminal device functions described in the above method embodiments, and the chip receives information from other devices; or, the chip sends information to other devices.

[0299] When the aforementioned communication device is a chip used in an access network device, the chip implements the functions of the access network device in the above method embodiments. The chip receives information from other devices; or, the chip sends information to other devices.

[0300] When the aforementioned communication device is a chip used in core network equipment, the chip implements the functions of the core network equipment in the above method embodiments. The chip receives information from other devices; or, the chip sends information to other devices.

[0301] When the aforementioned communication device is a chip used in a server, the chip implements the functions of the server in the above method embodiments. The chip receives information from other devices; or, the chip sends information to other devices.

[0302] It is understood that the processor in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor can be a microprocessor or any conventional processor.

[0303] The method steps in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in an access network device or terminal. Of course, the processor and storage medium can also exist as discrete components in the terminal or access network device.

[0304] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer program or instructions can be stored in a computer-readable storage medium or transmitted through the computer-readable storage medium. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a DVD; or it can be a semiconductor medium, such as a solid-state drive (SSD).

[0305] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0306] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

[0307] This application also provides a computer-readable storage medium storing computer-executable instructions. When these instructions are executed, the methods executed by the terminal device, access network device, core network device, or server in the above method embodiments are implemented.

[0308] This application also provides a computer program product, which includes a computer program that, when executed, causes the methods executed by the terminal device, access network device, core network device, or server in the above method embodiments to be implemented.

[0309] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0310] The descriptions of the various embodiments provided in this application can be referenced mutually. Each embodiment has its own emphasis, and parts not described in detail in a certain embodiment can be referred to the relevant descriptions of other embodiments. For the sake of convenience and brevity, for example, the functions and execution steps of the various devices and equipment provided in the embodiments of this application can be referred to the relevant descriptions of the method embodiments of this application. The method embodiments and the device embodiments can also be referenced, combined or cited from each other.

[0311] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A communication method, characterized in that, The method includes: Receive a first uplink data packet; the first uplink data packet includes a first sensing layer header, the first sensing layer header carries first control information and / or first transmission parameters; the first control information is used to request second transmission parameters; the first transmission parameters are parameters provided by the first application layer to the first data link layer; the second transmission parameters are parameters provided by the second data link layer to the first application layer; the first uplink data packet is a data packet corresponding to the first service flow.

2. The method as described in claim 1, characterized in that, The first perception layer header carries the first control information, the first control information including first information used to request a first parameter; the method further includes: Based on the first information, the first parameter is sent to the first application layer.

3. The method as described in claim 1 or 2, characterized in that, The first sensing layer header carries the first control information, the first control information including second information, the second information being used to request the access network device to provide a second parameter; the method further includes: The second information is sent to the access network device.

4. The method as described in claim 3, characterized in that, Sending the second information to the access network device includes: The second information is carried in the first data link layer header and sent to the access network device.

5. The method as described in claim 1 or 3, characterized in that, The first sensing layer packet header carries the first transmission parameter, the first transmission parameter including a third parameter, and the method further includes: Based on the third parameter, the transmission strategy of the uplink data packets corresponding to the first service flow is adjusted.

6. The method as described in claim 5, characterized in that, Before receiving the first uplink data packet, the method further includes: The second control information is carried in the second perception layer header and sent to the first application layer; the second control information is used to request the third parameter.

7. The method as described in claim 1 or 3, characterized in that, The first sensing layer header carries the first transmission parameter, the first transmission parameter including a fourth parameter, and the method further includes: The fourth parameter is carried in the second data link layer header, and the second data link layer header is sent to the access network device.

8. The method as described in claim 7, characterized in that, Before receiving the first uplink data packet, the method further includes: Receive third control information from the access network device; the third control information is used to request the fourth parameter. The third control information is sent to the first application layer.

9. The method as described in claim 8, characterized in that, The receipt of third control information from the access network device includes: Receive a fourth data link layer header from the access network device, the fourth data link layer header carrying third control information.

10. The method as described in claim 9, characterized in that, Sending the third control information to the first application layer includes: The third control information is carried in the third perception layer header and sent to the first application layer.

11. The method according to any one of claims 1-10, characterized in that, The first transmission parameter includes at least one of the following: Data delay parameter; the data delay parameter is used to indicate the packet delay budget of the first data packet; the first data packet is the data packet corresponding to the first service flow; Data sequence parameters; the data sequence parameters are used to indicate the sequence identifier corresponding to the first data packet; Data failure parameters; the data failure parameters are used to indicate the sequence identifier of the failed data packet; Data importance level parameter; the data importance level parameter is used to indicate the importance level of the first data packet.

12. The method according to any one of claims 1-11, characterized in that, The second transmission parameter includes at least one of the following: Reference transmission rate; the reference transmission rate is used to indicate the maximum transmission rate that the access network device can provide for the first service flow; Predicted transmission rate; the predicted transmission rate is used to indicate the maximum transmission rate that the access network device can provide for the first service flow at the predicted time. Data timing parameters; the data timing parameters are used to indicate the time when the access network device expects the application layer of the terminal device to send data packets.

13. A communication method, characterized in that, The method includes: Send a first uplink data packet; the first uplink data packet includes a first perception layer header, the first perception layer header carries first control information and / or first transmission parameters; the first control information is used to request second transmission parameters; the first transmission parameters are parameters provided by the first application layer to the first data link layer; the second transmission parameters are parameters provided by the second data link layer to the first application layer; the first uplink data packet is a data packet corresponding to the first service flow.

14. The method as described in claim 13, characterized in that, The first sensing layer header carries the first control information, and the method further includes: Receive the second transmission parameter; Based on the second transmission parameters, the transmission strategy of the uplink data packets corresponding to the first service flow is adjusted.

15. The method as described in claim 13, characterized in that, The first sensing layer header carries the first transmission parameters, and before sending the first uplink data packet, it further includes: Receive fourth control information; the fourth control information is used to request the first transmission parameters; Based on the fourth control information, the first transmission parameter is generated.

16. A communication method, characterized in that, The method includes: A second uplink data packet is received from a terminal device; the second uplink data packet includes a third data link layer header, the third data link layer header carrying second information and / or a fourth parameter; the second information is used to request the second parameter; the second parameter is a parameter provided by the data link layer of the access network device to the first application layer; the fourth parameter is a parameter provided by the first application layer to the data link layer of the access network device; the second uplink data packet is a data packet corresponding to the first service flow.

17. The method as described in claim 16, characterized in that, The third data link layer header carries the fourth parameter; the method further includes: Based on the fourth parameter, the transmission strategy of the uplink data packets corresponding to the first service flow is adjusted.

18. The method as described in claim 17, characterized in that, Before receiving the second uplink data packet from the terminal device, the method further includes: Send third control information to the terminal device; the third control information is used to request the fourth parameter.

19. The method as described in claim 18, characterized in that, The sending of third control information to the terminal device includes: The third control information is carried in the first GTP-U packet header and sent to the core network equipment. Receive a third sensing layer header from the core network device; the third sensing layer header carries the third control information; The third sensing layer header is sent to the terminal device.

20. The method as described in claim 18, characterized in that, The sending of third control information to the terminal device includes: The third control information is carried in the fourth data link layer header and sent to the terminal device.

21. The method as described in claim 16 or 17, characterized in that, The third data link layer header carries the second information; the method further includes: Based on the second information, the second parameter is sent to the terminal device.

22. The method as described in claim 21, characterized in that, Sending the second parameter to the terminal device includes: The second parameter is carried in the second GTP-U header, and the second GTP-U header is sent to the core network equipment; Receive a fourth sensing layer packet header from the core network device; the fourth sensing layer packet header carries the second parameter; The fourth sensing layer header is sent to the terminal device.

23. The method as described in claim 21, characterized in that, Sending the second parameter to the terminal device includes: The second parameter is carried in the fifth data link layer header, and the fifth data link layer header is sent to the terminal device.

24. The method as described in claim 16, characterized in that, The method further includes: A first downlink data packet is received from a core network device; the first downlink data packet includes fifth control information and / or third transmission parameters; the fifth control information is used to request a fourth transmission parameter; the third transmission parameter is a parameter provided by the second application layer to the data link layer of the access network device; the fourth transmission parameter is a parameter provided by the data link layer of the access network device to the second application layer; the first downlink data packet is a data packet corresponding to the first service flow.

25. The method as described in claim 24, characterized in that, The first downlink data packet includes the fifth control information, and the method further includes: Based on the fifth control information, the fourth transmission parameter is sent to the core network device.

26. The method as described in claim 24 or 25, characterized in that, The first downlink data packet includes the third transmission parameter, and the method further includes: Based on the third transmission parameter, the transmission strategy of the downlink data packets corresponding to the first service flow is adjusted.

27. The method as described in claim 26, characterized in that, Before receiving the first downlink data packet from the core network device, the method further includes: The sixth control information is sent to the core network device; the sixth control information is used to request the third transmission parameters.

28. The method as described in claim 27, characterized in that, Sending the sixth control information to the core network device includes: The sixth control information is carried in the third GTP-U header and sent to the core network equipment.

29. A communication method, characterized in that, The method includes: The system receives a third uplink data packet from an access network device; the third uplink data packet includes seventh control information and / or fifth transmission parameters; the seventh control information is used to request a sixth transmission parameter; the sixth transmission parameter is a parameter provided by the third application layer to the third data link layer; the fifth transmission parameter is a parameter provided by the fourth data link layer to the fourth application layer; the third uplink data packet is a data packet corresponding to the first service flow.

30. The method as described in claim 29, characterized in that, The third uplink data packet includes the seventh control information, the seventh control information includes third information, the third information being used to request the terminal device to provide a fifth parameter, and the method further includes: The third information is carried in the fifth perception layer header and sent to the access network device.

31. The method as described in claim 29 or 30, characterized in that, The third uplink data packet includes the seventh control information, the seventh control information includes fourth information, the fourth information is used to request the server to provide a sixth parameter, and the method further includes: The fourth information is carried in the sixth perception layer header and sent to the server.

32. The method as described in claim 31, characterized in that, The method further includes: Receive a seventh perception layer packet header from the server; the seventh perception layer packet header carries the sixth parameter; The sixth parameter is carried in the fourth GTP-U header and the fourth GTP-U header is sent to the access network device.

33. The method according to any one of claims 29-32, characterized in that, The third uplink data packet includes the fifth transmission parameter, the fifth transmission parameter includes a seventh parameter, and the method further includes: The seventh parameter is carried in the eighth sensing layer header, and the eighth sensing layer header is sent to the access network device.

34. The method according to any one of claims 29-33, characterized in that, The third uplink data packet includes the fifth transmission parameter, the fifth transmission parameter includes an eighth parameter, and the method further includes: The eighth parameter is carried in the eighth perception layer header and the eighth perception layer header is sent to the server.

35. The method as described in claim 34, characterized in that, Before receiving the third uplink data packet from the access network device, the method further includes: Receive the eighth control information from the server; the eighth control information is used to request the eighth parameter; Send the eighth control information to the access network device.

36. A communication method, characterized in that, The method includes: The terminal device sends a first uplink data packet to the access network device; the first uplink data packet includes a data link layer header, and the data link layer header carries first control information; the first control information is used to request the access network device to provide first transmission parameters; the first transmission parameters are parameters provided by the data link layer of the access network device to the application layer of the terminal device; the first uplink data packet is a data packet corresponding to a first service flow. The access network device receives the first uplink data packet and, based on the first control information, sends a second uplink data packet to the core network device; the second uplink data packet includes the first transmission parameters; the second uplink data packet is a data packet corresponding to the first service flow. The core network device receives the second uplink data packet and sends a first downlink data packet to the access network device based on the first transmission parameters; the first downlink data packet includes a perception layer header, which carries the first transmission parameters; the first downlink data packet is a data packet corresponding to the first service flow. The core network device receives the first downlink data packet and sends the first downlink data packet to the terminal device; The terminal device receives the first downlink data packet and adjusts the transmission strategy of the uplink data packet corresponding to the first service flow based on the first transmission parameters.

37. A communication device, characterized in that, It includes modules for performing the method as described in any one of claims 1 to 12, or the method as described in any one of claims 13 to 15, or the method as described in any one of claims 16 to 28, or the method as described in any one of claims 29 to 35.

38. A communication device, characterized in that, The method includes a processor configured to implement, via logic circuitry and / or by executing a computer program or instructions, the method as described in any one of claims 1 to 12, or the method as described in any one of claims 13 to 15, or the method as described in any one of claims 16 to 28, or the method as described in any one of claims 29 to 35.

39. The communication device according to claim 38, characterized in that, Also includes: A memory for storing the computer program or instructions.

40. A communication device, characterized in that, The device includes a processor and an interface circuit. The interface circuit is used to receive signals from other communication devices besides the communication device and transmit them to the processor, or to send signals from the processor to other communication devices besides the communication device. The processor is used to implement the method as described in any one of claims 1 to 12, or the method as described in any one of claims 13 to 15, or the method as described in any one of claims 16 to 28, or the method as described in any one of claims 29 to 35, through logic circuits or execution code instructions.

41. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions that, when executed by a communication device, implement the method as described in any one of claims 1 to 12, or the method as described in any one of claims 13 to 15, or the method as described in any one of claims 16 to 28, or the method as described in any one of claims 29 to 35.

42. A computer program product, characterized in that, Includes computer program code, which, when run on a communication device, implements the method as described in any one of claims 1 to 12, or the method as described in any one of claims 13 to 15, or the method as described in any one of claims 16 to 28, or the method as described in any one of claims 29 to 35.

Images