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

Communication method and communication device

[0001] This application claims priority to the Chinese patent application with application number 202311863894.2 filed with the State Intellectual Property Office of China on December 29, 2023, and priority to the Chinese patent application with the invention name “A Communication Method and Communication Device”, all contents of which are incorporated by reference into this application. Technical Field

[0002] The embodiments of the present application relate to the field of communication technology, and in particular, to a communication method and a communication device. Background Art

[0003] In communication systems, protocols typically define multiple protocol layers. Data packets from the sender are processed by each protocol layer before being sent to the receiver. The receiver then reprocesses the data packets through each layer. The different protocol layers are designed and operated relatively independently, utilizing a modular division of labor to independently implement their logic. However, the data transmission process using existing communication protocols lacks effective interaction between the various layers, impacting transmission efficiency. Therefore, achieving effective interaction between the various protocol layers during data transmission and improving transmission efficiency is a pressing technical challenge. Summary of the Invention

[0004] The embodiments of the present application provide a communication method and a communication device, which can achieve efficient interaction between different protocol layers, thereby facilitating an improvement in data transmission rate.

[0005] In a first aspect, an embodiment of the present application provides a communication method, which may include: receiving 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 a first transmission parameter; the first control information is used to request a second transmission parameter; the first transmission parameter is a parameter provided by the first application layer to the first data link layer; the second transmission parameter is a parameter 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 business flow.

[0006] Among them, 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. Among them, the first service flow can be a first quality of service (quality of service, QoS) flow, or the first service flow can be a first data radio bearer (data radio bearer, DRB), or the first service flow can be a service flow with a first Internet protocol (internet protocol, IP) attribute (such as IP quintuple).

[0007] It can be seen that by carrying the perception layer header in the uplink data packet, the application layer of the terminal device can realize information interaction 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 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 efficiently with the help 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, the first control information including first information, and the first information is used to request the 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 the 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 header carries first control information, the first control information includes second information, and the second information is used to request the access network device to provide the second parameter. The method further includes: sending the second information to the access network device. In other words, the first perception layer header may carry the second information used by the application layer of the terminal device to request the access network device to provide the second parameter.

[0010] In one possible implementation, sending the second information to the access network device includes: carrying the second information in a first data link layer header, and sending the first data link layer header to the access network device. Carrying the second information in the first data link layer header prevents the access network device from reading the perception layer header, making the solution universal.

[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 a transmission strategy for an uplink data packet corresponding to the first service flow based on the third parameter. This indicates that the data link layer of the terminal device can optimize data transmission based on the 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 the 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 the third parameter. In other words, before the application layer of the terminal device provides the parameter to the data link layer, the data link layer may first carry the control information requesting the application layer to provide the parameter in the perception layer header.

[0013] In one possible implementation, the first perception layer header carries the first transmission parameter, which includes a fourth parameter. The method further includes: carrying the fourth parameter in the 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 perception layer header, making the solution 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 the fourth parameter; and sending the third control information to the first application layer. In other words, before providing the parameters to the data link layer of the access network device, the application layer of the terminal device may receive control information from the access network device for requesting the application layer to provide the parameters.

[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, where the fourth data link layer header carries the third control information. Thus, the access network device can carry the third control information via 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. In other words, the terminal device may 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 above-mentioned 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 the data packet corresponding to the first business 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 the failed data packet; 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 above-mentioned 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 the predicted time; 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 a data packet.

[0019] In a second aspect, an embodiment of the present application provides another communication method, which may include: sending a first uplink data packet; the first uplink data packet includes a first perception layer header, and the first perception layer header carries first control information and / or a first transmission parameter; the first control information is used to request a second transmission parameter; the first transmission parameter is a parameter provided by the first application layer to the first data link layer; the second transmission parameter is a parameter 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 business flow.

[0020] It can be seen that by carrying the perception layer header in the uplink data packet, the application layer of the terminal device can realize information interaction 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 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 efficiently with the help of the perception layer header, which is conducive to improving data transmission efficiency.

[0021] In one possible implementation, the first perception layer packet header carries the first control information, and the method further includes: receiving a second transmission parameter; and adjusting the transmission strategy of the uplink data packet corresponding to the first service flow based on the second transmission parameter. 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 perception layer packet header carries the first transmission parameter, and before sending the first uplink data packet, the further steps include: receiving fourth control information; the fourth control information being used to request the first transmission parameter; and generating the first transmission parameter based on the fourth control information. In other words, the application layer of the terminal device can provide the transmission parameter 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 parameter provided by the application layer.

[0023] In a third aspect, an embodiment of the present application provides 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, and the third data link layer header carries second information and / or a fourth parameter; the second information is used to request a 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.

[0024] Among them, 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] It can be seen that 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 realize 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 with each other, which is conducive to improving data transmission efficiency.

[0026] In one possible implementation, the third data link layer packet header carries a fourth parameter; and the method further includes adjusting a transmission strategy for uplink data packets corresponding to the first service flow based on the fourth parameter. This indicates that the data link layer of the access network device can optimize data transmission based on the 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 the fourth parameter. In other words, before obtaining the parameter provided by the application layer of the terminal device, the data link layer of the access network device may first send control information requesting the application layer of the terminal device to provide the parameter.

[0028] In one possible implementation, sending the third control information to the terminal device includes: carrying the third control information in a first GTP user plane portion (GTP-U) header, and sending the first GTP-U header to the core network device; receiving a third perception layer header from the core network device; the third perception layer header carrying the third control information; and sending the third perception layer header to the terminal device. In other words, the access network device may first send the third control information to the core network device, which then carries the third control information in a perception layer header, and then sends the perception layer header carrying the third control information to the access network device. This approach prevents the access network device from modifying the perception layer 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. In other words, the access network device may also directly send the third control information to the terminal device, and the terminal device may carry the third control information in a perception layer header, which then sends the perception layer header carrying the third control information to the application layer of the terminal device. This approach also avoids the access network device from modifying the perception layer header.

[0030] In one possible implementation, the third data link layer header carries the second information; and the method further includes: sending the second parameter to the terminal device based on the second information. In other words, 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 may first send the second parameter to the core network device, which then carries the second parameter in a perception layer header and then sends the perception layer header carrying the second parameter to the access network device. This approach prevents 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 a fifth data link layer header, and sending the fifth data link layer header to the terminal device. In other words, the access network device may also directly send the second parameter to the terminal device, and the terminal device may carry the second parameter in a perception layer header, which then sends the perception layer header carrying the second parameter to the application layer of the terminal device. This approach 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 a third transmission parameter; 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; and the first downlink data packet is a data packet corresponding to the first service flow. The third transmission parameter can be understood as a parameter provided by the application layer of the server to the data link layer of the access network device, and the fourth transmission parameter can be understood as a parameter provided by the data link layer of the access network device to the application layer of the server.

[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 may first send the parameters provided by the access network device's data link layer to the server's application layer to the core network device. The core network device may then carry the parameters in a perception layer header and send the perception layer header carrying the 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 a transmission strategy for 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 the 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 the third transmission parameter. In other words, before receiving the parameters provided by the application layer of the server, the access network device may send control information for requesting the parameters to the server through the core network device.

[0037] In one possible implementation, the sending of 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 may carry control information for requesting the application layer of the server to provide parameters in a GTP-U header, and then send the GTP-U header to the core network device.

[0038] In a fourth aspect, an embodiment of the present application provides 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 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.

[0039] The fifth transmission parameter may include a parameter 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 a parameter 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] It can be seen that by carrying the seventh control information and / or the fifth transmission parameter in the uplink data packet sent by the access network device to the core network device, the data link layer of the access network device can realize 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 packet sent to the core network device, so that the core network device carries this part of the interaction information in the perception layer header, thereby eliminating the need for the access network device to modify the perception layer header.

[0041] In one possible implementation, the third uplink data packet includes seventh control information, the seventh control information includes third information, and the third information is 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 by the access network device to the terminal device in a perception layer header, then send the perception layer header to the access network device, which then sends it to the terminal device.

[0042] In one possible implementation, the third uplink data packet includes seventh control information, the seventh control information includes fourth information, and 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 the 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 the sixth parameter; and carrying 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 may parse the perception layer header from the server to obtain the sixth parameter provided by the application layer of the server to the data link layer of the access network device, and then carry 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 third uplink data packet includes a fifth transmission parameter, which 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 may carry the transmission parameters sent by the access network device to the terminal device in a perception layer header, then send the perception layer header to the access network device, which then sends it to the terminal device.

[0045] In one possible implementation, the third uplink data packet includes the 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 may carry the transmission parameter sent by the access network device to the server in a 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 method 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. That is, before receiving the eighth parameter provided by the access network device to the server, the core network device may first send the eighth control information from the server to the access network device for requesting the eighth parameter.

[0047] In a fifth aspect, an embodiment of the present application provides 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, and 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.

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

[0049] It can be seen that by carrying the perception layer header in the uplink data packet sent by the core network device to the server, information interaction 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 the 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 the help of the perception layer header, which is conducive to improving data transmission efficiency.

[0050] In one possible implementation, the ninth perception layer packet header carries the fourth information, and the method further includes: sending a sixth parameter to the core network device based on the fourth information. In other words, the server may 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 the parameters to the access network device.

[0051] In one possible implementation, the sending of the sixth parameter to the core network device includes: carrying the sixth parameter in a tenth perception layer header, and sending the tenth perception layer header to the core network device. That is, the server may carry the parameter 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 may parse the sixth parameter from the perception layer header and then forward it to the access network device.

[0052] In one possible implementation, the ninth perception layer packet header carries the eighth parameter, and the method further includes adjusting the transmission strategy of the downlink data packet corresponding to the first service flow based on the eighth parameter. This indicates that the server's application layer can optimize downlink data transmission based on the 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. In other words, before receiving the eighth parameter provided by the access network device to the server, the server may first send the eighth control information for requesting the eighth parameter to the core network device, and the core network device may then forward the eighth control information to the access network device.

[0054] In a sixth aspect, an embodiment of the present application provides another communication method, which may include: a terminal device sends a first uplink data packet to an 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 a first transmission parameter; the first transmission parameter is a parameter 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 the 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 parameter; 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 based on the first transmission parameter, sends a first downlink data packet to the access network device; the first downlink data packet includes a perception layer header, and the perception layer header carries the first transmission parameter; 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 based on the first transmission parameter, adjusts the transmission strategy of the uplink data packet corresponding to the first service flow.

[0055] In a seventh aspect, an embodiment of the present application provides a communication device, which may be a terminal device, a device in a terminal device, or a device that can be used in conjunction with a terminal device. The communication device may also be a chip system. The communication device may execute the method described in the first aspect or the second aspect. The functions of the communication device may be implemented by 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 and beneficial effects performed by the communication device may refer to the methods and beneficial effects described in the first aspect or the second aspect above.

[0056] In an eighth aspect, an embodiment of the present application provides a communication device, which may be an access network device, a device in an access network device, or a device that can be used in conjunction with an access network device. The communication device may also be a chip system. The communication device may execute the method described in the third aspect. The functions of the communication device may be implemented by hardware, or by hardware executing corresponding software implementations. The hardware or software includes one or more units or modules corresponding to the above functions. The units or modules may be software and / or hardware. The operations and beneficial effects performed by the communication device may refer to the method and beneficial effects described in the third aspect above.

[0057] In a ninth aspect, an embodiment of the present application provides a communication device, which may be a core network device, a device in a core network device, or a device that can be used in conjunction with a core network device. The communication device may also be a chip system. The communication device may execute the method described in the third aspect. The functions of the communication device may be implemented by 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 and beneficial effects performed by the communication device may refer to the method and beneficial effects described in the fourth aspect above.

[0058] In a tenth aspect, an embodiment of the present application provides a communication device, which may be a core network device, a device in a core network device, or a device that can be used in conjunction with a core network device. The communication device may also be a chip system. The communication device may execute the method described in the fourth aspect. The functions of the communication device may be implemented by hardware, or by hardware executing corresponding software implementations. 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 and beneficial effects performed by the communication device may refer to the method and beneficial effects described in the fourth aspect above.

[0059] In an eleventh aspect, an embodiment of the present application provides a communication device, which may be a server, a device in a server, or a device that can be used in conjunction with a server. The communication device may also be a chip system. The communication device may execute the method described in the fifth aspect. The functions of the communication device may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions. The units or modules may be software and / or hardware. The operations and beneficial effects performed by the communication device may refer to the method and beneficial effects described in the fifth aspect above.

[0060] In aspect 12, an embodiment of the present application provides a communication device, the communication device including a processor, the processor being used to execute the method as described in aspect 1, or the method as described in aspect 2, or the method as described in aspect 3, or the method as described in aspect 4, or the method as described in aspect 5.

[0061] In the thirteenth aspect, an embodiment of the present application provides a communication device, which includes a processor, the processor is coupled to a memory, and the memory is used to store programs or instructions. When the program or instructions are executed by the processor, the communication device executes the method described in the first aspect, or executes the method described in the second aspect, or executes the method described in the third aspect, or executes the method described in the fourth aspect, or executes the method described in the fifth aspect.

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

[0063] In the fourteenth aspect, an embodiment of the present application provides a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device, and the processor is used 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 a logic circuit or executing code instructions.

[0064] In aspect 15, an embodiment of the present application provides a computer-readable storage medium, in which a computer program or instruction is stored. When the computer program or instruction is executed by a communication device, the method described in aspect 1, or the method described in aspect 2, or the method described in aspect 3, or the method described in aspect 4, or the method described in aspect 5 is implemented.

[0065] In aspect 16, an embodiment of the present application provides a computer program product comprising instructions, which, when a communication device reads and executes the instructions, causes the communication device to execute the method as described in aspect 1, or the method as described in aspect 2, or the method as described in aspect 3, or the method as described in aspect 4, or the method as described in aspect 5.

[0066] In the seventeenth aspect, an embodiment of the present application provides 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 execute the method as described in the first aspect or the second aspect, the access network device is used to execute the method as described in the third aspect, the core network device is used to execute the method as described in the fourth aspect, and the server is used to execute the method as described in the fifth aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0067] FIG1A is a schematic diagram of a protocol stack architecture provided in an embodiment of the present application;

[0068] FIG1B is a schematic diagram of a network architecture provided in an embodiment of the present application;

[0069] FIG2 is a schematic diagram of a protocol stack architecture that introduces a perception layer according to an embodiment of the present application;

[0070] FIG3 is a flow chart of a communication method provided in an embodiment of the present application;

[0071] FIG4 is a schematic diagram of a UE-TLL sending a data packet according to an embodiment of the present application;

[0072] FIG5 is a flow chart of another communication method provided in an embodiment of the present application;

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

[0074] FIG7 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0075] FIG8 is a schematic structural diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0076] In this application, words such as "first" and "second" are used to distinguish between identical or similar items with substantially the same functions and effects. Those skilled in the art will understand that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit differences. "And / or" describes the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the related objects are in an "or" relationship.

[0077] It should be understood that, in this application, "at least one" refers to one or more, and "a plurality" refers to two or more. Furthermore, in this application, "equal to" can be used in conjunction with "greater than" or "less than." When "equal to" and "greater than" are used together, the technical solution of "greater than" is adopted; when "equal to" and "less than" are used together, the technical solution of "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 to the terminal device directly or indirectly. "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, which can include receiving information from the terminal device directly or indirectly. The information may be processed as necessary between the source and destination of the information, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be understood similarly and will not be elaborated on here.

[0079] The following first explains the relevant names or terms involved in this application to facilitate understanding by those skilled in the art.

[0080] 1. 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 (such as a mobile phone), wearable device, in-vehicle device, or a wireless device built into any of the above devices (such as a communication module, modem, or chip system). Terminal devices are used to connect people, objects, and machines, and can be used in a wide range of scenarios, such as cellular communications, device-to-device (D2D) communications, vehicle-to-everything (V2X) communications, machine-to-machine / machine-type communications (M2M / MTC) communications, the Internet of Things (IoT), virtual reality (VR), augmented reality (AR), industrial control, self-driving, remote medical care, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, drones, robots, and other scenarios. Exemplarily, the terminal device may 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. The terminal device may sometimes be 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 embodiment of the present application, the device for realizing the function of the terminal device may be the terminal device, or may be a device that can support the terminal device to realize the function, such as a chip system or a combination device or component that can realize the function of the terminal device, and the device may be installed in the terminal device.

[0082] 2. Access Network Equipment

[0083] Access network equipment is a network-side device with wireless transceiver functions. Access network equipment can be a device that provides wireless communication functions for terminal devices in a radio access network (RAN), and therefore, it can also be called a RAN device. For example, an access network device 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 base station that has been subsequently evolved by 3GPP, an access node in a WiFi system, a wireless relay node, a wireless backhaul node, etc. In communication systems using different radio access technologies (RAT), the names of devices with base station functions may be different. For example, it can be called eNB or eNodeB in an LTE system, and it can be called gNB in ​​a 5G system or NR system. This application does not limit the specific name of the base station. The access network device may include one or more co-sited or non-co-sited transmission and reception points. For another example, the access network device may include one or more centralized units (CU), one or more distributed units (DU), or one or more CUs and one or more DUs.

[0084] Exemplarily, the functions of the CU can be implemented by one entity or different entities. For example, the functions of the CU are further divided, that is, the control plane and the user plane are separated and implemented through different entities, namely the control plane CU entity (i.e., CU-CP entity) and the user plane CU entity (i.e., CU-UP entity). The CU-CP entity and the CU-UP entity can be coupled with the DU to jointly complete the functions of the access network device. In this way, some functions of the wireless access network device can be implemented through multiple network function entities. These network function entities can be network elements in hardware devices, or software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform). For another example, in vehicle to everything (V2X) technology, the access network device can be a road side unit (RSU). Multiple access network devices in the communication system can be base stations of the same type or different types. The base station can communicate with the terminal device, or it can communicate with the terminal device through a relay station. In the embodiments of the present application, the apparatus for implementing the functions of the access network device may be the access network device itself, or may be an apparatus capable of supporting the access network device in implementing the functions, such as a system-on-chip or a combination of devices or components capable of implementing the functions of the access network device, which may be installed in the access network device. In the embodiments of the present application, the system-on-chip may be composed of a chip or may include a chip and other discrete components.

[0085] 3. Core Network Equipment

[0086] Core network equipment is used to implement functions such as mobility management, data processing, session management, policy and billing. The names of devices implementing core network functions in systems with different access technologies may vary, and this application does not limit this. Taking the 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). The AMF is a network element used to manage access and mobility of terminal devices, mainly involving functions such as terminal device location update, network registration, and handover control. The SMF is a network element used to manage sessions of terminal devices, mainly involving functions such as session establishment, modification, and release. The UPF is a network element used to receive and forward user data. The UPF is controlled by the SMF. Different logical network elements of the 5GC can be deployed on the same or different physical devices. For example, the AMF and SMF can be deployed on the same physical device or on two physical devices. In addition, the logical network elements of the 5GC can be deployed on the same physical device as the network elements of the 4G core network. The device for realizing the functions of the core network equipment can be the core network equipment, or it can be a device that can support the core network equipment to realize the functions, such as a chip system or a combination of devices and components that can realize the functions of the core network equipment. The device can be installed in the core network equipment.

[0087] 4. Server

[0088] The server can be an application server corresponding to a variety of businesses, and can provide a variety of possible services for the terminal device. Among them, the application server can be provided with an application layer equivalent to the application layer of the terminal device. In the embodiment of the present application, the device for implementing the server function can be the server itself, or it can be a device that can support the server to implement the function, such as a chip system or a combination device or component that can implement the server function, which can be installed in the server. In the embodiment of the present application, the chip system can be composed of chips, or it can include chips and other discrete devices.

[0089] 5. Protocol Layer Architecture

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

[0091] Among them, the protocols supported by the application layer may include the hypertext transfer protocol (HTTP), file transfer protocol (FTP), real-time transport protocol (RTP), etc. The protocols supported by the transport layer may include the transmission control protocol (TCP), user datagram protocol (UDP), etc. The protocols supported by the network layer may include the Internet protocol (IP) protocol, such as IPv4 or IPv6. The access layer may include the service data adaptation protocol (SDAP) layer, the packet data convergence protocol (PDCP) layer, the radio link control (RLC) layer, the media access control (MAC) layer, and the physical layer (PHY).

[0092] 6. Interaction between different protocol layers

[0093] Currently, the design and operation of different protocol layers are relatively independent, and the logic of each protocol layer is independently completed through modular division of labor. There is a lack of effective interaction between different protocol layers. The lack of interaction between different protocol layers includes but is not limited to the following:

[0094] (1) The transport layer lacks the bandwidth capability to interact with the access layer

[0095] When a sender (such as a terminal device) transmits data to a receiver (such as a network device), congestion may occur due to the limited radio resources and unstable wireless channels. If the sender continues to send a large number of packets during congestion, this may result in increased packet transmission delays or packet loss. Therefore, congestion control is necessary.

[0096] In one implementation, the sender can use the TCP congestion control algorithm to prevent excessive data from entering the network. Specifically, the sender's transport layer can maintain a congestion window (Cwnd) and employ a ramping strategy to continuously attempt to increase the transmission rate from a lower one to a higher one. This strategy involves first using a smaller congestion window value. Once the network is confirmed to be free of congestion, the congestion window value is gradually increased, and more data packets are sent. In this approach, if the access layer has a large bandwidth capacity, the trial process using the ramping strategy will be time-consuming. For example, assuming the access layer can provide a maximum transmission rate of 1 Tbps, the transport layer will start the trial from 1 Mbps. Trialing to 1 Tbps will take hundreds of milliseconds, resulting in low bandwidth utilization.

[0097] It can be seen that if the transport layer can know the bandwidth capability of the access layer, the time consumed in the trial transmission process can be saved and the transmission efficiency can be improved.

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

[0099] The sender's application layer can adjust the application layer encoding based on the actual transmission rate of the data reaching the receiver in order to adapt to the channel. For example, if the sender transmits 1080P video data, if the receiver encounters a freeze during video playback, the sender's application layer can automatically adjust to transmit 720P video data to reduce the bandwidth demand on the access layer, thereby avoiding freezes during the broadcast process. However, this adjustment method is usually made after the channel changes affect the data transmission. That is, after a period of video playback freezes, the application layer encoding adjustment is triggered, resulting in low data transmission stability.

[0100] It can be seen 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 properties of interactive application layer data packets

[0102] For service flows controlled by the same QoS flow, the base station's access layer uses the same transmission processing (e.g., scheduling). Typically, packets belonging to the same service are placed in the same QoS flow. However, packets belonging to the same service may have different QoS requirements, so the properties of the entire QoS flow are set based on the packet with the highest QoS requirement. For example, assuming that the packet delay budget (PDB) requirement for some packets in a QoS flow is 10ms, while the PDB requirement for other packets is 20ms, the base station will schedule the entire QoS flow based on the 10ms PDB requirement, which will affect the base station's capacity.

[0103] It can be seen that if the access layer can distinguish packets with different attributes (such as PDB, importance of packets, etc.) in the same QoS flow, then the access layer can adopt different transmission strategies for packets with different attributes to improve resource utilization.

[0104] (4) The access layer lacks interaction with the application layer and invalid data packets

[0105] For continuous data packet transmission scenarios, such as the scenario where the server transmits artificial intelligence (AI) model data to the UE in the downlink, or the scenario where the UE transmits three-dimensional model data to the server in the uplink, the application layer usually generates data and sends it to the access layer, and then the access layer sends it. In actual applications, during the process of transmitting the first model data, the application layer may need to switch the first model data to the second model data for transmission due to scene changes. At this time, the application layer will choose to stop sending the remaining data in the first model data and start sending the second model data. However, after the application layer stops sending the remaining data in the first model data, the data in the first model data that the application layer has sent to the access layer will become invalid. In this case, for the data in the first model data that the application layer has sent to the access layer, the access layer will start the discard timer according to the PDB requirements, and will continue to send these invalid data before the discard timer times out. This will not only affect the transmission delay of the second model data, but also increase the air interface burden.

[0106] It can be seen that if the access layer can be informed of invalid data packets, it will be helpful to reduce the air interface burden.

[0107] (5) The access layer lacks the time to send data packets from the interactive application layer

[0108] For periodic services, if multiple data packets in the periodic services arrive at the base station access layer at a close time, and the PDB requirements of the multiple data packets are short, the base station will need to schedule a large number of data packets in a short period of time, which will put great pressure on the base station's capacity.

[0109] It can be seen that if the access layer can provide the application layer with the sending time of data packets, so that the time for the application layer to send data packets is dispersed, it will be helpful to alleviate the scheduling pressure of the base station.

[0110] 7. RTP Protocol

[0111] The RTP protocol is a network transmission protocol, usually built on the User Datagram Protocol (UDP). After being encapsulated and processed by the network transmission RTP protocol, an RTP data packet containing an RTP header can be formed. At present, if the application layer adopts the RTP protocol, the RTP header can be used to carry part of the application layer information, so that the application layer information can be provided to other protocol layers for transmission optimization. For example, by carrying the attribute information of the data packet through the RTP header, the access layer can be enabled to distinguish between different data packets with different attributes (such as PDB, the importance of the data packet, etc.), thereby adopting different transmission strategies for data packets with different attributes. However, this method of adopting the RTP protocol lacks versatility. If the application layer does not adopt the RTP protocol, it will not be possible to realize the interaction of the application layer information with other protocol layers. In addition, this method also lacks a mechanism for other protocol layers (such as the access layer) to feedback information to the application layer.

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

[0113] The embodiments of the present application can be applied to various communication systems, for example, long term evolution (LTE) systems, fifth generation (5G) systems, new radio (NR) systems, wireless-fidelity (WiFi) systems, third generation partnership project (3GPP) related communication systems, and other communication systems that may appear in the future, such as sixth generation (6G) mobile communication systems. The embodiments of the present 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 the convenience of description, this application takes the 5G system as an example.

[0114] The following describes a network architecture applicable to the embodiments of the present application.

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

[0116] The terminal device portion includes a terminal device 101, which may also be referred to as user equipment (UE). The terminal device 101 involved in the embodiments of the present application is a device with wireless transceiver functions, which can communicate with one or more core networks (CNs) via RAN 102.

[0117] The operator network may include unified data management 108 (UDM), access and mobility management function 105 (AMF), session management function 106 (SMF), policy control function 107 (PCF), user plane function 103 (UPF), and RAN 102. In the above operator network, the parts other than the RAN part can be referred to as the core network (CN) part or core network part.

[0118] Data network DN104, also known as a protocol data network (PDN), is typically located outside of a carrier network, such as a third-party network. A carrier network can access multiple data networks DN104, which can host a variety of services, including data and / or voice services, to provide terminal devices.

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

[0120] RAN 102 can be considered a subnetwork of the operator network, serving as the implementation system between service nodes and terminal devices within the operator network. To access the operator network, a terminal device first passes through RAN 102, and then connects to a service node within the operator network through RAN 102. The access network device in the embodiments of this application is a device that provides wireless communication capabilities for terminal devices and may also be referred to as a network device.

[0121] The access and mobility management function AMF105 (also known as the AMF network element, AMF network function or AMF network function entity) is a control plane network function provided by the operator network, responsible for the access control and mobility management of terminal devices accessing the operator network, such as mobile status management, allocation of user temporary identity, authentication and authorization of users and other functions.

[0122] The session management function SMF106 (also called SMF network element, SMF network function or SMF network function entity) is a control plane network function provided by the operator network, responsible for managing the protocol data unit (PDU) session of the terminal device.

[0123] The user plane function UPF 103 (also called UPF network element, UPF network function or UPF network function entity) is a gateway provided by the operator and is the gateway for communication between the operator network and the data network DN 104. It is mainly responsible for processing user messages, such as forwarding and billing.

[0124] The unified data management network element UDM108 (also known as the UDM network element, UDM network function or UDM network function entity) is a control plane function provided by the operator, responsible for storing the permanent identity identifier (SUPI) of the subscriber in the operator's network, the generic public subscription identifier (GPSI) of the subscriber, the credential and other information. The SUPI will be encrypted during transmission, and the encrypted SUPI is called a hidden user subscription identifier (SUCI). The information stored in UDM108 can be used for authentication and authorization of terminal devices to access the operator's network.

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

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

[0127] In Figure 1B, N1, N2, N3, N5, N6, N7, N8, N10, and N11 are interface serial numbers. The meanings of these interface serial numbers can be found in the definitions in the 3GPP standard protocol and are not described in detail here. It should be noted that Figure 1B only illustrates an example using the terminal device UE101, and the interface names between the various network functions in Figure 1B are merely examples. In a specific implementation, the interface names of the system architecture may also be other names, and this embodiment of the present application does not specifically limit this.

[0128] The following describes the method provided by the embodiment of the present application in conjunction with the accompanying drawings. Before introducing the embodiment, some terms involved in the embodiment of the present application are explained in a unified manner.

[0129] (1) Optimization of data transmission

[0130] In this application, data transmission optimization refers to adjusting some parameters of data transmission to make the data transmission performance more compatible with 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 the parameters provided by the data link layer, such as adjusting the transmission window when transmitting data, such as adjusting the decision of the sending rate when transmitting data, etc.; ② The data link layer optimizes data transmission based on the parameters provided by the application layer, such as adjusting the scheduling time when transmitting data, discarding invalid data when transmitting data, etc.

[0131] (2) Data link transmission parameters

[0132] The transmission parameters of the data link in this application are some parameters related to the transmission of the data link, such as the rate of the data link, 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, etc., or other parameters related to the transmission of the data link. This application does not impose any restrictions on this.

[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 delay requirement information, data packet integrity requirement information, data packet failure information, data packet service type (such as voice, video, game, etc.), data packet coding information (such as coding type, coding resolution, frame rate), data packet jitter information, data packet application protocol type, data packet transport layer protocol type, etc. This application does not impose any restrictions on this.

[0135] (4)IP quintuple

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

[0137] (5) Data Packet

[0138] The data packets in this application (such as the first uplink data packet, the second uplink data packet, etc.) are all data packets corresponding to the same service flow, for example, data packets corresponding to the first service flow. The first service flow can be a first QoS flow, or the first service flow can be a first data radio bearer (DRB), or the first service flow can be a service flow with a first IP attribute (such as an IP quintuple).

[0139] It should be noted that the application layer in the embodiment of the present application (such as the application layer of the terminal device or the application layer of the server) can also be described as a 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 quick UDP internet connections (QUIC) protocol, or other transport protocols above TCP / UDP. The data link layer (DLL) in the embodiment of the present application may include the air interface protocol layer of the 5G system: the PHY, MAC layer, RLC layer, PDCP layer, and SDAP layer of the terminal device and access network device in Figure 1A; it may also include a WiFi air interface protocol layer, and may also include a data link layer of a wired network (such as Ethernet). It can be understood that the application layer (TLL) and data link layer (DLL) in the embodiment of the present application are defined only for the convenience of distinguishing different functions, and may also be replaced by other names, which is not limited by the present application.

[0140] In the embodiments of the present application, 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 the DLL, the perception layer can be set above the transport layer (TCP / UDP), or can be set at other locations, such as in the extension header of the network layer (IP), or in the extension header of other protocol layers, which is not limited by the present application.

[0141] It should be noted that the perception layer is the name of the layer introduced in this application for transmitting interaction information between different protocol layers. In the embodiment of this application, the perception layer can also be described as the vertical interaction and awareness protocol (VIAP), or the interaction layer, or the 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 that introduces a perception layer provided in an embodiment of the present 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 GTP user plane part (user plane part of GTP, GTP-U) protocol layer of the core network device. For ease of description, the embodiment of the present application is explained as an example of a terminal device being a UE, an access network device being a RAN, and a core network device being a CN. Among them, the perception layer of the terminal device (UE-perception layer) can be located between the TLL (UE-TLL) of the terminal device and the 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 (CN-perception layer) of the core network device 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 achieved. For ease of understanding, the embodiment of the present application is described using the protocol stack architecture shown in FIG2 as an example.

[0143] Taking uplink transmission as an example, please refer to FIG3 , which is a flow chart of a communication method provided in an embodiment of the present 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. Accordingly, 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] For the first control information, the first control information can be used to request the second transmission parameter, and the second transmission parameter can be used by TLL to optimize data transmission. Therefore, the second transmission parameter can also be understood as the parameter provided by DLL to UE-TLL. Specifically, the second transmission parameter may include the transmission parameter of the data link. Optionally, the second transmission parameter may include a reference transmission rate, which may be used to indicate the maximum transmission rate that DLL can provide for the first service flow. The second transmission parameter may also include a predicted transmission rate, which may be used to indicate the maximum transmission rate that DLL can provide for the first service flow at the predicted moment. The second transmission parameter may also include a data timing parameter, which may be used to indicate the time when DLL expects UE-TLL to send a data packet.

[0146] Since the DLL can be a UE-DLL and / or a RAN-DLL, the following scenarios 1 and 2 are respectively described.

[0147] Scenario 1: UE-TLL requests the second transmission parameter from UE-DLL. To distinguish it from Scenario 2, in this scenario, the second transmission parameter is described as the first parameter, and the first control information in this scenario is described as the first information. The first parameter can be understood as the parameter provided by UE-DLL to UE-TLL. The first parameter can be used by TLL to optimize data transmission. The first parameter may include the transmission parameter of the data link. 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. For details, see S301a.

[0148] S301a: UE-DLL sends a 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 may parse the first perception layer header of the first uplink data packet to obtain first information, and then generate a first parameter based on the first information and send the first parameter to the UE-TLL. Furthermore, the UE-TLL may adjust the transmission strategy of the uplink data packet corresponding to the first service flow based on the first parameter.

[0150] Scenario 2: The UE-TLL requests the RAN-DLL for a second transmission parameter. To distinguish this scenario from Scenario 1, the second transmission parameter is described as a second parameter in this scenario, and the first control information in this scenario is described as second information. The second parameter can be understood as a parameter provided by the RAN (e.g., RAN-DLL) to the UE-TLL. The second parameter may include a data link parameter. The second parameter can be used by the TLL to optimize data transmission. For details, see S301b below.

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

[0152] Among them, 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 the access network device usually does not parse the header content above the network layer. In this way, the access network device can avoid parsing the first perception layer header from the first uplink data packet, making the present 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 obtains 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 the embodiment of the present application (such as the above-mentioned first data link layer header) can be an SDAP header, a PDCP header, an RLC header, or other data link layer headers, and the embodiment of the present application is not limited to this.

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

[0154] In some embodiments, the UE-TLL may receive a second perception layer header, which may carry second control information. The second control information may be used to request the UE-TLL to provide the first transmission parameter. Optionally, the second perception layer header may be a perception layer header of a downlink data packet corresponding to the first service flow. In other words, the terminal device may 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 parameter to the UE-DLL through the second control information.

[0155] Since the DLL can be a UE-DLL and / or a RAN-DLL, the following scenarios 3 and 4 are respectively described.

[0156] In Scenario 3, the UE-TLL provides the UE-DLL with the first transmission parameter. To distinguish this 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. For details, see S301c.

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

[0158] In some embodiments, the second control information may be used to request the UE-TLL to provide a data delay parameter, i.e., the third parameter may be the data delay parameter, and the UE-DLL may adjust the transmission strategy of the uplink data packet corresponding to the first service flow based on the data delay parameter. The data delay parameter may be used to indicate a packet delay budget (PDB) for 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 may indicate a PDB offset of the first data packet.

[0160] If the data delay parameter indicates the PDB of the first data packet, after obtaining the PDB of the first data packet, the UE-DLL may adjust the discard timer based on the PDB of the first data packet. For example, assuming that 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 that the PDB of the first data packet is 12ms based on the data delay parameter, the UE-DLL may start the discard timer based on the PDB of 12ms. In other words, the first data packet will be discarded only if it has not been sent after the discard timer expires after 12ms.

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

[0162] In some implementation scenarios, the PDB of the uplink data packet combined with the PDB of the downlink data packet affects the total data transmission delay, and thus affects the user experience. Taking the game scenario as an example, the time it takes for the terminal device to receive the user operation and transmit the uplink data packet, and the time it takes for the server to render the game screen and transmit the downlink data packet jointly determine the user experience. If the time it takes for the terminal device to receive the user operation and transmit the uplink data packet is long, then the time it takes for the server to render the game screen and transmit the downlink data packet can be adjusted to be shorter. Correspondingly, if the time it takes for the server to render the game screen and transmit the downlink data packet is long, then the time it takes for the terminal device to receive the user operation and transmit the uplink data packet can be adjusted to be shorter. In an embodiment of the present application, the UE-TLL can provide data delay parameters to the UE-DLL so that the UE-DLL can flexibly adjust the PDB of the uplink data packet based on the data delay parameters.

[0163] In scenario 4, the UE-TLL requests the first transmission parameter from the RAN-DLL. To distinguish this from scenario 3, the first transmission parameter is described as the fourth parameter in this scenario. 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] S301d: UE-DLL sends the fourth parameter to RAN. Correspondingly, RAN receives the fourth parameter from UE-DLL.

[0165] The UE-DLL may parse the first perception layer header of the first uplink data packet to obtain the fourth parameter, then carry the fourth parameter in the second data link layer header and send the second data link layer header to the RAN. Optionally, the second data link layer header may be the data link layer header of the first uplink data packet or the data link layer header of another uplink data packet corresponding to the first service flow.

[0166] It can be understood that the above-mentioned scenarios one to four can be combined arbitrarily, that is, the terminal device can carry any one of the above-mentioned first information, second information, third parameter, and fourth parameter in the first perception layer header of the first uplink data packet, or can carry any combination of the four, which can be determined according to actual needs.

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

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

[0169] S302 is the process for the above-mentioned scenarios 2 and 4. Specifically, after receiving the first uplink data packet from the UE-TLL, the UE-DLL obtains the second information and / or fourth parameters, and the UE-DLL can then send these parameters to the RAN. The UE-DLL may perform some processing on the first uplink data packet before sending it to the RAN device, or the UE-DLL may obtain the second information and / or fourth parameters and, when a new data packet needs to be sent, place the second information and / or fourth parameters in the new data packet and send it to the RAN. Therefore, 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 uplink data packet and the second uplink data packet may be the same or different. In different scenarios, the UE-DLL may modify the content of the first uplink data packet to obtain the second uplink data packet.

[0170] Optionally, the identifier of the second uplink data packet may 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 by the third data link layer header, which can avoid the access network device from parsing the protocol layer above the network layer (IP).

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

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

[0173] S302a: The RAN sends a second parameter to the UE based on the second information. Correspondingly, the UE receives the second parameter from the RAN.

[0174] The RAN may generate a second parameter based on the second information, carry the second parameter in a data link layer header, and then send the data link layer header to the UE-DLL. The access network device may add the data link layer header carrying the second parameter to the downlink data packet corresponding to the first service flow. Optionally, the RAN may carry the second parameter in a perception layer header and send it 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 layer in the perception layer header and send the perception layer header carrying the second parameter to the UE-TLL. After receiving the perception layer header, the UE-TLL can obtain the second parameter from the perception layer header.

[0177] In method 1, the RAN carries the second parameter in a data link layer header and sends it to the terminal device. The UE-DLL extracts the second parameter from the data link layer header and then carries the second parameter in a perception layer header and sends 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, preventing the access network device from modifying the packet header above the network layer.

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

[0179] Among them, the RAN can send the second parameter to the core network device, so that the core network device carries the second parameter in the perception layer header of the downlink data packet, and then sends the downlink data packet carrying the perception layer header of the second parameter to the terminal device through the access network device. For example, the access network device can specifically carry the second parameter in the GTP-U header and send it to the core network device. That is, the access network device 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 device obtains the GTP-U header, it can extract the second parameter from the GTP-U header. The core network device can carry the second parameter in the perception layer header and send the perception layer header carrying the second parameter to the access network device, and then the access network device sends the perception layer header carrying the second parameter to the terminal device.

[0180] In method 2, the RAN carries the second parameter in a GTP-U header and sends it to the core network device. The core network device extracts the second parameter from the GTP-U header and then carries it in a perception layer header and sends it to the access network device. The access network device then sends the perception layer header to the terminal device. In this way, the core network device carries the second parameter in the perception layer header instead of the access network device, preventing the access network device from modifying the network layer header.

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

[0182] In one implementation scenario, for the case where 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 packet 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 that the RAN can provide for the first service flow. Among them, the UE-TLL can adjust the value of the congestion window based on the reference transmission rate when starting congestion control for the first service flow. For example, assuming that the reference transmission rate is 500Mbps, the UE-TLL does not need to start from a smaller value (such as 1Mbps) when setting the congestion window, but can use a larger congestion window value (such as 250Mbps), which is conducive to reducing the time consumed by the trial mechanism and improving bandwidth utilization.

[0183] In another implementation scenario, for the case where the second parameter includes a 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 packet corresponding to the first service flow based on the predicted transmission rate. Specifically, the predicted transmission rate can indicate the maximum transmission rate that the RAN can provide for the first service flow at a certain predicted moment. 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 that the current rate of the first service flow is 100Mbps and supports 2k resolution transmission, the predicted transmission rate indicates that the maximum transmission rate that the RAN can provide for the first service flow after 2s will change to 20Mbps. Based on this, the UE-TLL can reduce the resolution to 1080p in advance, thereby improving the stability of data transmission.

[0184] In another implementation scenario, for the case where 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, the RAN can avoid the time when each data packet arrives at the RAN too close by indicating the expected time to send the data packet to the UE-TLL. In the case of tight PDB requirements, it can avoid the situation where the access network equipment needs to schedule a large number of data packets in a short time. For example, please refer to Figure 4, which is a schematic diagram of a UE-TLL sending a data packet provided in an embodiment of the present application. As shown in (1) of Figure 4, the time when the UE-TLL sends data packet 401, data packet 402, and data packet 403 in the periodic service is close. In the case shown in (1) of Figure 4, the time when data packet 401, data packet 402, and data packet 403 arrive at the RAN will also be close. If the PDB requirements for data packets 401, 402, and 403 are tight, this means that the access network device needs to send all the data packets in a short period of time, which increases the scheduling pressure on the access network device. As shown in (2) of Figure 4, the UE-TLL can disperse the transmission of data packets 401, 402, and 403 based on the data timing parameters provided by the RAN. In the case shown in (2) of Figure 4, the arrival time of data packets 401, 402, and 403 at the RAN will be more dispersed, which helps alleviate the scheduling pressure on the access network device.

[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 packet corresponding to the first service flow based on the fourth parameter.

[0186] S302d: The RAN adjusts the transmission strategy of the uplink data packet 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. The third control information may be used to request the terminal device to provide a fourth parameter. The fourth parameter may be used by the RAN to optimize data transmission. The fourth parameter may include data packet service attribute information. The manner in which the RAN sends the third control information to the terminal device is similar to the manner in which the RAN sends the second parameter to the terminal device, and may include direct and indirect transmission. The direct transmission method includes: the RAN carries the third control information in a data link layer header, sends the data link layer header to the terminal device, and the UE-DLL extracts the third control information from the data link layer header and then sends the third control information in a perception layer header to the UE-TLL. The indirect transmission method includes: the RAN sends the third control information to a core network device, the core network device carries the third control information in a perception layer header, and then sends the perception layer header carrying the third control information to the RAN. Finally, the RAN sends a downlink data packet containing the perception layer header carrying 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 may be used to request the data sequence parameter. The RAN may adjust the transmission strategy for uplink data packets corresponding to the first service flow based on the data sequence parameter. Specifically, the data sequence parameter may be used to identify data packets in different groups. Data packets in a group typically correspond to a complete application function. For example, all data packets corresponding to an image may be grouped into Group A, all data packets corresponding to an AI model may be grouped into Group B, all data packets corresponding to a file may be grouped into Group C, and all data packets corresponding to a three-dimensional (3D) object model may be grouped into Group D. Optionally, data packets in the same group may use the same identifier as the data sequence parameter. For example, all data packets corresponding to image A1 may use identifier 1 as the data sequence parameter, all data packets corresponding to image A2 may use identifier 2 as the data sequence parameter, all data packets corresponding to file C1 may use identifier 3 as the data sequence parameter, and so on. In this case, the RAN can determine the group to which each data packet belongs based on the data sequence parameter of each data packet, thereby enabling refined management of the uplink transmission time of data packets in the same group. Optionally, data packets in the same group may also use the identifiers of the starting and ending data packets as data sequence parameters. For example, data packet a at the starting position corresponding to image A1 can use identifier a1 as the data sequence parameter, and data packet b at the ending position corresponding to image A1 can use identifier b1 as the data sequence parameter; data packet c at the starting position corresponding to image A2 can use identifier c2 as the data sequence parameter, and data packet d at the ending position corresponding to image A2 can use identifier d2 as the data sequence parameter, and so on. In this case, the RAN can determine whether the data packets belonging to the same group are transmitted completely based on the data sequence parameters of the data packets at the starting position and the data sequence parameters of the data packets at the ending position in the same group, thereby finely managing the uplink transmission time of the data packets belonging to the same group.

[0189] In another implementation scenario, if the fourth parameter includes a data expiration parameter, the third control information may be used to request the data expiration parameter. The RAN may adjust the transmission policy for uplink data packets corresponding to the first service flow based on the data expiration parameter. Specifically, the data expiration parameter may be used to identify invalid data packets within the same group. Based on the data expiration parameter, the RAN may stop transmitting invalid data packets to the server, thereby conserving transmission resources and reducing the transmission latency of other non-invalid data packets.

[0190] In another implementation scenario, when the fourth parameter includes a data importance parameter, the third control information may be used to request the data importance parameter. The RAN may adjust the transmission strategy for uplink data packets corresponding to the first service flow based on the data importance parameter. For example, when transmitting data packets with a high importance level, the RAN may use a smaller PDB to improve the transmission reliability of the 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 the seventh control information and / or the fifth transmission parameter.

[0192] The seventh control information may be used to request a sixth transmission parameter, which may be used by the RAN to optimize data transmission. Therefore, the sixth transmission parameter may be understood as a parameter provided by a TLL (e.g., a UE-TLL and / or a Server-TLL) to the RAN-DLL. Specifically, the sixth transmission parameter may include data packet service attribute information.

[0193] Since TLL can be UE-TLL and / or Server-TLL, the following scenarios A and B are described respectively.

[0194] In scenario A, regarding the RAN's request for 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 can include data packet service attribute information. In other words, the access network device can carry the third information in the third uplink data packet, for example, the third information can be carried in the GTP-U header, and then the third information can be carried in the perception layer header of the downlink data packet corresponding to the first service flow through the core network device. This allows the terminal device to obtain the third information from the perception layer header of the downlink data packet corresponding to the first service flow, thereby controlling the UE-TLL to provide the fifth parameter to the RAN-DLL. For details, see 303a-303c.

[0195] S303a: The CN sends the third information to the UE. Correspondingly, the UE receives the third information from the CN.

[0196] The CN may carry the third information in the fifth perception layer header, and the core network device may send the fifth perception layer header to the terminal device through the access network device. Optionally, the core network device may carry the third information in the perception layer header of the downlink data packet corresponding to the first service flow.

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

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

[0199] S303c: UE-TLL generates a 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. After receiving the fifth parameter, the UE-perception layer can include the fifth parameter in a perception layer header and then send the perception layer header carrying the fifth parameter to the UE-DLL. After receiving the perception layer header carrying the fifth parameter, the UE-DLL can obtain the fifth parameter from the perception layer header, include the fifth parameter in a data link layer header, and send the data link layer header to the RAN.

[0201] In Scenario B, regarding the RAN's request for the sixth transmission parameter from the Server-TLL, to distinguish it from Scenario A, the sixth transmission parameter is described as the sixth parameter in this scenario, and the seventh control information in this scenario 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. In other words, the access network device can carry the fourth information in the third uplink packet, and then, through the core network device, carry the fourth information in the perception layer header of the uplink data packet corresponding to the first service flow. This allows the server to obtain the fourth information from the perception layer header of the uplink data packet corresponding to the first service flow, thereby controlling the Server-TLL to provide the fifth parameter to the RAN.

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

[0203] Since TLL can be UE-TLL and / or Server-TLL, the following scenarios C and D are used to describe them respectively.

[0204] In scenario C, the RAN provides the fifth transmission parameter to the UE-TLL. To distinguish this 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. For details, see S303d-S303f below.

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

[0206] Among them, the CN can carry the seventh parameter in the eighth perception layer header, and then the core network device can send the eighth perception layer header to the terminal device through 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-perception layer sends the seventh parameter to the UE-TLL. Correspondingly, the UE-TLL receives the seventh parameter from the UE-perception layer.

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

[0209] Scenario D: RAN provides the fifth transmission parameter to Server-TLL. In order to distinguish it from Scenario C, in this scenario, the fifth transmission parameter is described as the eighth parameter, and the eighth parameter can be understood as the parameter provided by RAN-DLL to Server-TLL. The eighth parameter can be used by TLL to optimize data transmission. The eighth parameter may include the transmission parameter of the data link. In other words, the access network device can carry the eighth parameter in the third uplink data packet, and then carry the eighth parameter in the perception layer header of the uplink data packet corresponding to the first business flow through the core network device, so that the server can obtain the eighth parameter from the perception layer header of the uplink data packet corresponding to the first business flow, and then the server can adjust the transmission strategy of the downlink data packet corresponding to the first business flow based on the eighth parameter.

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

[0211] S304 is the process for the aforementioned scenarios B and D. Specifically, after receiving the third uplink data packet from the RAN, the CN obtains the fourth information and / or the eighth parameter and can then send these parameters to the server. The CN may process the first uplink data packet before sending it to the server, or the CN may obtain the fourth information and / or the eighth parameter and, when a new data packet needs to be sent, include the fourth information and / or the eighth parameter in the new data packet and send it to the server. Therefore, the fourth uplink data packet is introduced as the uplink data packet sent by the CN to the server.

[0212] In some embodiments, the ninth perception layer header carries fourth information. For details, see S304a-304c below.

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

[0214] The server may generate a sixth parameter based on the fourth information. After generating the sixth parameter, the server may carry the sixth parameter in a perception layer header and then send the perception layer header carrying the sixth parameter to the CN.

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

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

[0217] S304c: The RAN adjusts a transmission strategy of the downlink data packet 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 for the downlink data packet 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 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 packet based on the determined PDB of the data packet. 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, the RAN can determine that the PDB of the first data packet is 14ms. Furthermore, the RAN can schedule the first data packet based on 14ms, meaning that the RAN can send the first data packet within 14ms. This can alleviate scheduling pressure on access network devices compared to 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 device when transmitting them, which helps improve data transmission flexibility.

[0219] In another implementation scenario, when the sixth parameter includes a data sequence parameter, the RAN can adjust the transmission policy for the downlink data packets corresponding to the first service flow based on the data sequence parameter. Specifically, the RAN can determine whether transmission of the same packet is complete based on the data sequence parameter, thereby finely managing the downlink transmission time of the data packets in the same packet.

[0220] In another implementation scenario, when the sixth parameter includes a data expiration parameter, the RAN may adjust the transmission policy for downlink data packets corresponding to the first service flow based on the data expiration parameter. Specifically, the RAN may stop transmitting expired data packets to the terminal device based on the data expiration parameter to conserve transmission resources and reduce the transmission delay of other non-expired data packets.

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

[0222] In some embodiments, the ninth perception layer header may carry an eighth parameter. For details, see 304d below.

[0223] S304d: The server adjusts the transmission strategy of the downlink data packet 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, where the eighth control information may be used to request the access network device to provide an eighth parameter. The server sending the eighth control information to the access network device may include: the server carrying the eighth control information in a perception layer header, sending the perception layer header carrying the eighth control information to the CN; and the CN obtaining the eighth control information from the perception layer header, and sending the header carrying the eighth control information to the RAN.

[0225] In one implementation scenario, when the eighth parameter includes a reference transmission rate, the eighth control information may be used to request the reference transmission rate. The server may adjust the transmission policy for 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 may adjust the congestion window value based on the reference transmission rate, thereby avoiding starting with an excessively small congestion window value.

[0226] In another implementation scenario, when the eighth parameter includes a predicted transmission rate, the eighth control information may be used to request the predicted transmission rate. The server may predict the transmission rate and adjust the downlink transmission strategy for the data packets corresponding to the first service flow. Specifically, the predicted transmission rate may indicate the maximum transmission rate that the RAN can provide for the first service flow at a predicted time. Based on the predicted transmission rate, the server may 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 is reduced, thereby avoiding playback lag.

[0227] In another implementation scenario, the eighth parameter includes a server-data timing parameter, and the eighth control information may be used to request the server-data timing parameter. The server may adjust the transmission strategy for the downlink data packet corresponding to the first service flow based on the server-data timing parameter. Specifically, the server-data timing parameter may indicate the time at which the RAN expects the server to send the data packet. The server may adjust the transmission time of the downlink data packet corresponding to the first service flow based on the server-data timing parameter. For periodic services, the RAN can prevent data packets from arriving at the RAN too close together by indicating the expected time to send the data packet to the server. This can prevent the access network equipment from having 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 FIG3 , by introducing the perception layer, different protocol layers can interact more efficiently based on the perception layer, and the solution is universal, which is conducive to improving data transmission efficiency and enhancing data transmission performance.

[0229] It should be noted that the scenarios involved in the embodiments of the present application may be presented separately or in combination. For example, scenarios one to four may be arbitrarily combined, scenarios A to D may be arbitrarily combined, and so on. For different scenarios, the presentation form of the control information and transmission parameters may be different. For example, for scenario one, the first control information may be the first information, for scenario two, the first control information may be the second information, and for the combination of scenario one and scenario two, the first control information may include the first information and the second information. For another example, for scenario C, the fifth transmission parameter may be the seventh parameter, for scenario D, the fifth transmission parameter may be the eighth parameter, and for the combination of scenario C and scenario D, the fifth transmission parameter may include the seventh parameter and the eighth parameter. It can be understood that the introduction of different descriptions of control information and transmission parameters is to distinguish the control information and transmission parameters in different scenarios, and does not constitute a limitation of the present application.

[0230] FIG3 describes an embodiment of the present application from the perspective of a terminal device sending an uplink data packet to a server, and the following describes an embodiment of the present application from the perspective of a server sending a downlink data packet to a terminal device.

[0231] Please refer to FIG5 , which is a flowchart of another communication method provided by an embodiment of the present application. FIG5 takes downlink transmission as an example, and may include but is not limited to the following steps:

[0232] S501: The server sends a downlink data packet A to the CN. Correspondingly, the CN receives the downlink data packet A from the server. The downlink data packet A includes a perception layer header A, which includes control information A and / or transmission parameter 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 can include data link transmission parameters.

[0234] In some embodiments, the perception layer header A may carry control information A. The CN obtains the control information A from the perception layer header A and then sends the control information A to the RAN. For details, 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 may carry the control information A in a GTP-U header, and then send the GTP-U header carrying the control information A to the RAN. The RAN may obtain the control information A from the GTP-U header.

[0237] S501b: The RAN sends a transmission parameter B to the server based on the control information A. Correspondingly, the server receives the transmission parameter 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 carry transmission parameter B in a perception layer packet header and then send the perception layer packet header carrying transmission parameter B to the server. After receiving the perception layer packet header carrying transmission parameter B, the server can obtain transmission parameter B from the perception layer packet header.

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

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

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

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

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

[0244] S501e: The RAN adjusts the transmission strategy of the downlink data packet corresponding to the first service flow based on the transmission parameter A.

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

[0246] S502: CN sends a downlink data packet B to RAN. Correspondingly, RAN receives the downlink data packet B from CN. The downlink data packet B includes control information B and / or transmission parameter C.

[0247] Regarding control information B, it can be used to request transmission parameter d1 and / or transmission parameter d2. Transmission parameter d1 can be understood as a parameter provided by the RAN-DLL to the Server-TLL. Transmission parameter d1 can be used by the TLL to optimize transmission. Transmission parameter d1 can include data link transmission parameters. Transmission parameter d2 can be understood as a parameter provided by the UE-TLL to the RAN-DLL. Transmission parameter d2 can be used by the RAN to optimize data transmission. Transmission parameter d2 can include data packet service attribute information. Since control information B can be used to request transmission parameter d1 and / or transmission parameter d2, the following scenarios 1 and 2 describe them separately.

[0248] In scenario 1, control information B is used to request 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 a transmission parameter d1 based on the control information b1.

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

[0251] In scenario 2, control information B is used to request transmission parameter d2. To distinguish from scenario 1, in this scenario, control information B is described as control information b2. For details, see S502b and S502c below.

[0252] S502b: The RAN sends control information b2 to the UE. Correspondingly, the UE receives the control information b2 from the RAN.

[0253] The CN can carry the control information b2 in a perception layer header and send the perception layer header carrying the control information b2 to the RAN. The RAN can then send the perception layer header carrying the control information b2 to the UE. The UE-perception layer can then obtain the control information b2 from the perception layer header and send the information b2 to the UE-TLL. Alternatively, the RAN can also carry the control information b2 in a perception layer header and send the perception layer header carrying the control information b2 to the UE.

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

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

[0256] Regarding transmission parameters C, transmission parameters C may include transmission parameters C1 and / or transmission parameters C2. Transmission parameters C1 can be understood as parameters provided by the Server-TLL to the RAN-DLL. Transmission parameters C1 can be used to optimize data transmission by the RAN. Transmission parameters C1 can include data packet service attribute information. Transmission parameters C2 can be understood as parameters provided by the RAN-DLL to the UE-TLL. Transmission parameters C2 can be used to optimize data transmission by the TLL. Transmission parameters C2 may include data link transmission parameters. Since transmission parameters C may include transmission parameters C1 and / or C2, they are described in the following scenarios 3 and 4, respectively.

[0257] Scenario 3: The transmission parameter C includes the transmission parameter c1. For details, please refer to the following step S502d.

[0258] S502d: The RAN adjusts the transmission strategy of the downlink data packet 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 the above step S304c, and will not be repeated here.

[0260] Scenario 4: The transmission parameter C includes the transmission parameter c2. For details, please refer to the following steps S502e and S502f.

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

[0262] The CN can carry the transmission parameter c2 in a perception layer header and send the perception layer header carrying the transmission parameter c2 to the RAN. The RAN can then send the perception layer header carrying the transmission parameter c2 to the UE-perception layer. The UE-perception layer can then obtain the transmission parameter c2 from the perception layer header and send the transmission parameter c2 to the UE-TLL. Optionally, the RAN can also carry the transmission parameter c2 in a perception layer header and send the perception layer header carrying the transmission parameter c2 to the UE.

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

[0264] Here, the implementation principle and process of step S502f are similar to those of the above step S302c, 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 parameter D.

[0266] 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 perception layer header, which may include control information C and / or transmission parameter D. In this case, the RAN may first send the control information C and / or transmission parameter D to the CN. The CN then carries the control information C and / or transmission parameter D in the perception layer header and then sends the perception layer header carrying the control information C and / or transmission parameter 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 parameter D. In this case, the RAN may carry the control information C and / or transmission parameter D in the data link layer header, and then send the data link layer header carrying the control information C and / or transmission parameter D to the UE-DLL.

[0269] Optionally, the RAN may also carry the control information C and / or the transmission parameter D in a perception layer header, and then send the perception layer header carrying the control information C and / or the transmission parameter D to the UE-DLL.

[0270] In the embodiment shown in FIG5 , by introducing the perception layer, different protocol layers can interact more efficiently based on the perception layer, and the solution is universal, which is conducive to improving data transmission efficiency and enhancing data transmission performance.

[0271] In an embodiment of the present application, the above-mentioned 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 for describing multimedia sessions. It is a text-based protocol that can be used for negotiation of media types and encoding schemes during session establishment. For example, please refer to Figure 6, which is a schematic diagram of the position of an SDP protocol in a protocol stack provided in an embodiment of the present application. In one implementation, the terminal device, the core network device and the server can negotiate to 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 trigger, the terminal device, the core network device and the server can perform interactions between different protocol layers based on the perception layer.

[0272] It should be noted that the description of protocol layer A sending packet header A to protocol layer B in the embodiment of the present application 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 embodiment of the present application can be data packets associated with the same business flow. In addition, the control information sent by DLL to TLL in the embodiment of the present application can also be described as D2T control information, which can be specifically divided into uplink D2T control information and downlink D2T control information. For example, the control information sent by RAN-DLL to Server-TLL can be described as uplink D2T control information, and the control information sent by RAN-DLL to UE-TLL can be described as downlink D2T control information. The transmission parameters sent by DLL to TLL can also be described as D2T transmission parameters, which can be specifically divided into uplink D2T transmission parameters and downlink D2T transmission parameters. Similarly, the control information sent by TLL to DLL can also be described as T2D control information, which can be 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 the present application, the embodiments of the present application also provide a general design of a perception layer header, which can be carried in an uplink data packet or a downlink data packet. Please refer to Table 1, which shows an example of information carried by a perception layer header:

[0274] Table 1

[0275] Among them, the "Empty Packet Indication" field can be used to indicate that there is no perception layer header in the subsequent data packet. The "Flow Identifier" can be used to identify the first service flow. The "End Bit" can be used to indicate whether the information ends. For example, the end bit of the D2T control information takes a value of 0, which can indicate the end of the D2T control information. The end bit of the D2T control information takes a value of 1, which can indicate that the next line is still D2T control information. Each bit in the "D2T Control Information" field can be used to indicate a request switch. For example, the first bit can indicate a request switch for the reference transmission rate. The first bit taking a value of 1 can indicate that the D2T control information is used to request the reference transmission rate, that is, requesting the reference transmission rate to be turned on; the first bit taking a value of 0 can indicate that the D2T control information does not request the reference transmission rate, that is, requesting the reference transmission rate to be turned off. The "D2T Transmission Parameter Existence Indication" field can be used to indicate the existence of D2T transmission parameters, which can specifically include a field length and a field bitmap. Each bit in the bitmap can be used to indicate whether a D2T transmission parameter exists. The "D2T Transmission Parameter: Reference Transmission Rate" field indicates the reference transmission rate. Whether the parameter transmission rate is the uplink reference transmission rate or the downlink reference transmission rate is determined by whether the perception layer header is carried in the uplink or downlink data packet. The "T2D Transmission Parameter Presence Indication" field indicates the presence of T2D transmission parameters. Specifically, it may include a field length and a bitmap. Each bit in the bitmap can be used to indicate whether a T2D transmission parameter exists.

[0276] The present application provides a communication device that can be used to implement the functions of the above-mentioned terminal equipment, or access network equipment, or core network equipment, or server. The communication device can be a terminal device, or an access network device, or a core network device, or a server. The communication device includes a unit corresponding to the method / operation / step / action performed by the terminal device, or the access network device, or the core network device, or the server in the above-mentioned method embodiment. The unit can be a hardware circuit, or software, or a combination of a hardware circuit and software. Please refer to Figure 7, which shows a structural diagram of a communication device 700 of an embodiment of the present 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, and the signaling and / or data 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, and the first perception layer header carries first control information and / or a first transmission parameter; the first control information is used to request a second transmission parameter; the first transmission parameter is a parameter provided by the first application layer to the first data link layer; the second transmission parameter is a parameter 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, for the specific implementation of the above-mentioned interface unit 701 and processing unit 702, reference may be made to the specific implementation steps of the UE-DLL in FIG3 and FIG5 , which 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, and the first perception layer header carries first control information and / or a first transmission parameter; the first control information is used to request a second transmission parameter; the first transmission parameter is a parameter provided by the first application layer to the first data link layer; the second transmission parameter is a parameter 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 business flow.

[0282] In this embodiment, for the specific implementation of the above-mentioned interface unit 701 and processing unit 702, reference may be made to the specific implementation steps of UE-TLL in FIG3 and FIG5 , which will not be repeated here.

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

[0284] Interface unit 701 is used to receive a second uplink data packet from the terminal device; the second uplink data packet includes a third data link layer header, and 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, for the specific implementation of the above-mentioned interface unit 701 and processing unit 702, reference may be made to the specific implementation steps of the access network device in Figures 3 and 5, which will not be repeated here.

[0286] In yet another embodiment, when the communication apparatus 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 parameter; 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, for the specific implementation of the above-mentioned interface unit 701 and processing unit 702, reference may be made to the specific implementation steps of the core network device in Figures 3 and 5, which 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, and 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, for the specific implementation of the above-mentioned interface unit 701 and processing unit 702, reference may be made to the specific implementation steps of the server in Figures 3 and 5, which will not be repeated here.

[0292] As shown in Figure 8, a communication device 800 provided in an embodiment of the present application is used to implement the functions of the above-mentioned terminal device, or access network device, or core network device, or server. The device can be a communication device or a device used in a communication device. The communication device can be a terminal device, or an access network device, or a core network device, or a server. The device used in the communication device can be a chip system or chip within the communication device. The chip system can be composed of a chip or can also include a chip and other discrete devices.

[0293] The communication device 800 includes at least one processor 810 for implementing the processing functions of the device (e.g., terminal device, or access network device, or core network device, or server) in the method provided in the embodiment of the present application. The communication device 800 may also include a communication interface 820 for implementing the transceiver operation of the device (e.g., terminal device, or access network device, or core network device, or server) in the method provided in the embodiment of the present application. In the embodiment of the present application, 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 is used for the device in the communication device 800 to communicate with other devices. The processor 810 uses the communication interface 820 to send and receive data, and is used to implement the method described in the above method embodiment.

[0294] The communication device 800 may also 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 the embodiments of the present application is an indirect coupling or communication connection between devices, units, or modules, which may be electrical, mechanical, or other forms, and is used for information exchange between the 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] The specific connection medium between the communication interface 820, processor 810, and memory 830 is not limited in the embodiments of the present application. In Figure 8, the embodiment of the present application shows that the memory 830, processor 810, and communication interface 820 are connected via a bus. The bus is represented by a bold line in Figure 8. The connection method between other components is only for schematic illustration and is not limiting. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one bold line is used in Figure 8, but this does not mean that there is only one bus or one type of bus.

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

[0297] It should be noted that the communication interface 820 may be used to execute the functions of the interface unit 701 , and the processor 810 may be used to execute the functions of the processing unit 702 , which will not be described in detail here.

[0298] When the above-mentioned communication device is a chip applied to a terminal device, the chip implements the terminal device function in the above-mentioned method embodiment, and the chip receives information from other devices; or, the chip sends information to other devices.

[0299] When the 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 embodiment. The chip receives information from other devices; or the chip sends information to other devices.

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

[0301] When the communication device is a chip used in a server, the chip implements the server function in the above method embodiment. 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 the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0303] The method steps in the embodiments of the present application can be implemented by hardware or by a processor executing software instructions. The software instructions can be composed 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, mobile hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and storage medium can be located in an ASIC. In addition, the ASIC can be located in an access network device or a terminal. Of course, the processor and storage medium can also exist as discrete components in a terminal or access network device.

[0304] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part 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 instruction is loaded and executed on a computer, the process or function described in the embodiment of the present application is executed in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program or instruction can be stored in a computer-readable storage medium or transmitted via 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, a hard disk, or a tape; it can also be an optical medium, such as a DVD; it can also be a semiconductor medium, such as a solid state drive (SSD).

[0305] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0306] It is understood that the various numbers used in the embodiments of this application are merely for ease of description and are not intended to limit the scope of the embodiments of this application. The order of the sequence numbers of the above-mentioned processes does not necessarily imply a specific order of execution; the order of execution of the processes should be determined by their functions and inherent logic.

[0307] An embodiment of the present application also provides a computer-readable storage medium, which stores computer execution instructions. When the computer execution instructions are executed, the method executed by the terminal device, or access network device, or core network device, or server in the above method embodiment is implemented.

[0308] An embodiment of the present application also provides a computer program product, which includes a computer program. When the computer program is executed, the method executed by the terminal device, or access network device, or core network device, or server in the above method embodiment is implemented.

[0309] It should be noted that for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the order of the actions described, because according to this application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in this specification are all preferred embodiments, and the actions and modules involved are not necessarily required by this application.

[0310] The descriptions of the various embodiments provided in this application can refer to each other. The descriptions of each embodiment have their own focus. For parts not described in detail in a particular embodiment, please refer to the relevant descriptions of other embodiments. For the convenience and brevity of description, for example, the functions and execution steps of the various devices and equipment provided in the embodiments of this application can refer to the relevant descriptions of the method embodiments of this application. The various method embodiments and the various device embodiments can also refer to, be combined with, or quote each other.

[0311] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some or all of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A communication method, characterized in that, The method includes: Receiving a first uplink data packet; the first uplink data packet includes a first perception layer header, and 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 a first application layer to a first data link layer; the second transmission parameters are parameters provided by a second data link layer to the first application layer; the first uplink data packet is a data packet corresponding to a first service flow.

2. The method according to claim 1, wherein The first perception layer header carries the first control information, and the first control information includes first information, and the first information is used to request first parameters; the method further includes: Based on the first information, sending the first parameters to the first application layer.

3. The method according to claim 1 or 2, characterized in that, The first perception layer header carries the first control information, and the first control information includes second information, and the second information is used to request an access network device to provide second parameters; the method further includes: Sending the second information to the access network device.

4. The method according to claim 3, wherein The sending the second information to the access network device includes: Carrying the second information in a first data link layer header, and sending the first data link layer header to the access network device.

5. The method according to claim 1 or 3, characterized in that, The first perception layer header carries the first transmission parameters, and the first transmission parameters include third parameters, the method further includes: Based on the third parameters, adjusting the transmission strategy of the uplink data packet corresponding to the first service flow.

6. The method according to claim 5, wherein Before receiving the first uplink data packet, it 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 the third parameters.

7. The method according to claim 1 or 3, characterized in that, The first perception layer header carries the first transmission parameters, and the first transmission parameters include fourth parameters, the method further includes: Carrying the fourth parameters in a second data link layer header, and sending the second data link layer header to the access network device.

8. The method according to claim 7, characterized in that, Before receiving the first uplink data packet, it further includes: Receiving third control information from an access network device; the third control information is used to request the fourth parameters; Sending the third control information to the first application layer.

9. The method according to claim 8, characterized in that, The receiving the third control information from the access network device includes: Receiving a fourth data link layer header from the access network device, and the fourth data link layer header carries the third control information.

10. The method according to claim 9, wherein The 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.

11. The method according to any one of claims 1 to 10, characterized in that, The first transmission parameters include at least one of the following: A data delay parameter; the data delay parameter is used to indicate the packet delay budget of a 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. 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 to 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 moment; 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.

13. A communication method, characterized in that, The method includes: Sending a first uplink data packet; the first uplink data packet includes a first sensing layer header, and 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 parameter is a parameter provided by the first application layer to the first data link layer; the second transmission parameter is a parameter 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 according to claim 13, wherein The first sensing layer header carries the first control information, and the method further includes: Receiving the second transmission parameter; Adjusting the transmission strategy of the uplink data packet corresponding to the first service flow based on the second transmission parameter.

15. The method according to claim 13, wherein Before sending the first uplink data packet, the first sensing layer header carries the first transmission parameter, and the method further includes: Receiving fourth control information; the fourth control information is used to request the first transmission parameter; Generating the first transmission parameter based on the fourth control information.

16. A communication method, characterized in that, The method includes: Receiving a second uplink data packet from a terminal device; the second uplink data packet includes a third data link layer header, and the third data link layer header carries second information and / or fourth parameters; the second information is used to request second parameters; 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 according to claim 16, wherein The third data link layer header carries the fourth parameter, and the method further includes: Adjusting the transmission strategy of the uplink data packet corresponding to the first service flow based on the fourth parameter.

18. The method according to claim 17, characterized in that, 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 the fourth parameter.

19. The method according to claim 18, wherein Sending the third control information to the terminal device includes: Carrying the third control information in a first GTP-U header and sending the first GTP-U header to a core network device; Receiving a third sensing layer header from the core network device; the third sensing layer header carries the third control information; Sending the third sensing layer header to the terminal device.

20. The method according to claim 18, wherein 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.

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

22. The method according to claim 21, wherein The sending the second parameter to the terminal device includes: Carrying the second parameter in a second GTP-U packet header and sending the second GTP-U packet header to the core network device; Receiving a fourth sensing layer packet header from the core network device; the fourth sensing layer packet header carries the second parameter; Sending the fourth sensing layer packet header to the terminal device.

23. The method according to claim 21, wherein The sending the second parameter to the terminal device includes: Carrying the second parameter in a fifth data link layer packet header and sending the fifth data link layer packet header to the terminal device.

24. The method according to claim 16, wherein The method further includes: Receiving a first downlink data packet from the core network device; the first downlink data packet includes fifth control information and / or a third transmission parameter; the fifth control information is used to request a fourth transmission parameter; the third transmission parameter is a parameter provided by a 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 according to claim 24, wherein The first downlink data packet includes the fifth control information, and the method further includes: Based on the fifth control information, sending the fourth transmission parameter to the core network device.

26. The method according to 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, adjusting the transmission policy of the downlink data packet corresponding to the first service flow.

27. The method according to claim 26, wherein Before receiving the first downlink data packet from the core network device, it further includes: Sending sixth control information to the core network device; the sixth control information is used to request the third transmission parameter.

28. The method according to claim 27, wherein The sending the sixth control information to the core network device includes: Carrying the sixth control information in a third GTP-U packet header and sending the third GTP-U packet header to the core network device.

29. A communication method, characterized in that, The method includes: Receiving a third uplink data packet from the access network device; the third uplink data packet includes seventh control information and / or a fifth transmission parameter; 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; the third uplink data packet is a data packet corresponding to the first service flow.

30. The method according to claim 29, wherein The third uplink data packet includes the seventh control information, and the seventh control information includes third information, and the third information is used to request the terminal device to provide a fifth parameter, and the method further includes: Carrying the third information in a fifth sensing layer packet header and sending the fifth sensing layer packet header to the access network device.

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

32. The method according to claim 31, characterized in that, The method further includes: Receiving a seventh sensing layer packet header from the server; the seventh sensing layer packet header carries the sixth parameter; Carry the sixth parameter in the fourth GTP-U packet header and send the fourth GTP-U packet header 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, and the fifth transmission parameter includes a seventh parameter. The method further includes: Carry the seventh parameter in the eighth sensing layer packet header and send the eighth sensing layer packet header to the access network device.

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

35. The method according to claim 34, characterized in that, Before receiving the third uplink data packet from the access network device, it further includes: Receiving 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 packet header, and the data link layer packet header carries first control information; the first control information is used to request the access network device to provide a first transmission parameter; the first transmission parameter is a parameter 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 parameter; 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, based on the first transmission parameter, sends a first downlink data packet to the access network device; the first downlink data packet includes a sensing layer packet header, and the sensing layer packet header carries the first transmission parameter; 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, based on the first transmission parameter, adjusts the transmission strategy of the uplink data packet corresponding to the first service flow.

37. A communication device, characterized in that, It includes a module for executing the method according to any one of claims 1 to 12, or a module for executing the method according to any one of claims 13 to 15, or a module for executing the method according to any one of claims 16 to 28, or a module for executing the method according to any one of claims 29 to 35.

38. A communication device, characterized in that, Comprising a processor, which is configured to cause the method according to any one of claims 1 to 12, or the method according to any one of claims 13 to 15, or the method according to any one of claims 16 to 28, or the method according to any one of claims 29 to 35 to be implemented by means of logic circuitry and / or by executing a computer program or instructions.

39. The communication device according to claim 38, wherein Further comprising: A memory for storing the computer program or instructions.

40. A communication device, characterized in that, Comprising 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 send signals from the processor to other communication devices outside the communication device, the processor being configured to implement the method according to any one of claims 1 to 12, or the method according to any one of claims 13 to 15, or the method according to any one of claims 16 to 28, or the method according to any one of claims 29 to 35 by means of logic circuitry or by executing code instructions.

41. A computer-readable storage medium, characterized in that, A computer program or instructions are stored in the storage medium, and when the computer program or instructions are executed by the communication device, the method according to any one of claims 1 to 12, or the method according to any one of claims 13 to 15, or the method according to any one of claims 16 to 28, or the method according to any one of claims 29 to 35 is implemented.

42. A computer program product, characterized in that, Comprising computer program code, and when the computer program code runs on the communication device, the communication device implements the method according to any one of claims 1 to 12, or the method according to any one of claims 13 to 15, or the method according to any one of claims 16 to 28, or the method according to any one of claims 29 to 35.

Images