Communication method and communication device

Abstract

According to the communication method and the communication device, a sensing layer is introduced into a communication protocol stack to realize information interaction between different protocol layers, and the scheme has universality and is beneficial to improving the efficiency of data transmission. The method may comprise: receiving a first uplink data packet; the first uplink data packet may comprise a first sensing layer packet header, and the first sensing layer packet header may carry first control information and / or a first transmission parameter; wherein the first control information is used for requesting a second transmission parameter; the first transmission parameter can be understood as a parameter provided by the first application layer to the 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; the first uplink data packet can be a data packet corresponding to the first service flow.

Description

Technical Field

[0001] 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

[0002] In a communication system, multiple protocol layers are usually defined in a communication protocol. The data packet at the sender is processed by each protocol layer and then sent to the receiver. The receiver can obtain the data packet after reverse processing by each protocol layer. Among them, the design and operation of different protocol layers are relatively independent, and the logic of each protocol layer is independently completed by modular division of labor. In the process of transmitting data through existing communication protocols, the various protocol layers lack effective interaction, which affects the transmission efficiency. Therefore, how to achieve effective interaction between various protocol layers in the data transmission process and improve the transmission efficiency is a technical problem that needs to be solved urgently. Summary of the invention

[0003] 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 improving the data transmission rate.

[0004] 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 service flow.

[0005] Among them, the first transmission parameter can be understood as a 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 a 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).

[0006] 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 exchange 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 beneficial to improving data transmission efficiency.

[0007] In a possible implementation, the first perception layer header carries first control information, the first control information includes first information, and the first information is used to request a first parameter; the method further includes: sending the first parameter to the first application layer based on the first information. That is, the first perception layer header can 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.

[0008] In a 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 a second parameter; the above method further includes: sending the second information to the access network device. That is, the first perception layer header can carry the second information used by the application layer of the terminal device to request the access network device to provide the second parameter.

[0009] In a possible implementation, the sending of 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. By carrying the second information in the first data link layer header, the access network device can avoid reading the perception layer header, making the solution universal.

[0010] In a possible implementation, the first perception layer packet header carries a first transmission parameter, the first transmission parameter includes a third parameter, and the method further includes: adjusting the transmission strategy of the uplink data packet corresponding to the first service flow based on the third parameter. It can be seen 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 facilitating the improvement of data transmission efficiency.

[0011] In a possible implementation, before the first uplink data packet is received, the method further includes: carrying the second control information in the 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. That is, before the application layer of the terminal device provides the parameters to the data link layer, the data link layer can first carry the control information requesting the application layer to provide the parameters through the perception layer header.

[0012] In a possible implementation, the first perception layer header carries a first transmission parameter, the first transmission parameter includes a fourth parameter, and the method further includes: carrying the fourth parameter in a second data link layer header, and sending the second data link layer header to the access network device. By carrying the fourth parameter in the second data link layer header, the access network device can be prevented from reading the perception layer header, so that the solution has universality.

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

[0014] In a possible implementation, the receiving of the third control information from the access network device includes: receiving a fourth data link layer header from the access network device, the fourth data link layer header carrying the third control information. It can be seen that the access network device can carry the third control information through the data link layer header without modifying the perception layer header.

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

[0016] In a 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 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 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.

[0017] In one possible implementation, the second transmission parameter includes at least one of the following: a reference transmission rate; the reference transmission rate is used to indicate the maximum transmission rate that the access network device can provide for the first service flow; a predicted transmission rate; the predicted transmission rate is used to indicate the maximum transmission rate that the access network device can provide for the first service flow at a predicted time; 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.

[0018] 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, 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.

[0019] 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 exchange 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 beneficial to improving data transmission efficiency.

[0020] In a 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 facilitating the improvement of data transmission efficiency.

[0021] In a possible implementation, the first perception layer packet header carries the first transmission parameter, and before sending the first uplink data packet, the method further includes: receiving fourth control information; the fourth control information is used to request the first transmission 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 parameters provided by the application layer.

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

[0023] Among them, the second parameter can be understood as a 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 a parameter provided by the application layer of the terminal device to the data link layer of the access network device.

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

[0025] In a possible implementation, the third data link layer packet header carries a fourth parameter; the method further includes: adjusting the transmission strategy of the uplink data packet corresponding to the first service flow based on the fourth parameter. It can be seen 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 facilitating the improvement of data transmission efficiency.

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

[0027] In a possible implementation, the sending of the third control information to the terminal device includes: carrying the third control information in a first GTP user plane part (user plane part of GTP, GTP-U) header, 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 carries the third control information; and sending the third perception layer header to the terminal device. In other words, the access network device can first send the third control information to the core network device, and the core network device carries the third control information in the perception layer header, and then sends the perception layer header carrying the third control information to the access network device. In this way, the access network device can be prevented from modifying the perception layer header.

[0028] In a possible implementation, the sending of the third control information to the terminal device includes: carrying the third control information in a fourth data link layer header, and sending the fourth data link layer header to the terminal device. That is, the access network device may also directly send the third control information to the terminal device, and the terminal 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 application layer of the terminal device. In this way, the access network device can also avoid modifying the perception layer header.

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

[0030] In a possible implementation, the sending of the second parameter to the terminal device includes: carrying the second parameter in the second GTP-U header, and sending the second GTP-U header to the core network device; receiving the fourth perception layer header from the core network device; the fourth perception layer header carries the second parameter; and sending the fourth perception layer header to the terminal device. In other words, the access network device can first send the second parameter to the core network device, and the core network device carries the second parameter in the perception layer header, and then sends the perception layer header carrying the second parameter to the access network device. In this way, the access network device can be prevented from modifying the perception layer header.

[0031] In a possible implementation, the sending of 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. That is, 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, and then send the perception layer header carrying the second parameter to the application layer of the terminal device. In this way, the access network device may also be prevented from modifying the perception layer header.

[0032] In a 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; 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.

[0033] In a possible implementation, the above first downlink data packet includes fifth control information, and the method further includes: sending fourth transmission parameters to a core network device based on the fifth control information. That is to say, the access network device can first send the parameters provided by the data link layer of the access network device to the application layer of the server to the core network device, and then the core network device can carry the parameter in the perception layer packet header and send the perception layer packet header carrying the parameter to the server.

[0034] In a possible implementation, the above first downlink data packet includes third transmission parameters, and the method further includes: adjusting the transmission policy of the downlink data packet corresponding to the first service flow based on the third transmission parameters. That is to say, the data link layer of the access network device can optimize the downlink data transmission based on the parameters provided by the application layer of the server, which is beneficial to improving the data transmission efficiency.

[0035] In a possible implementation, 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 third transmission parameters. That is to say, before receiving the parameters provided by the application layer of the server, the access network device can send control information for requesting parameters to the server through the core network device.

[0036] In a possible implementation, 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. That is to say, the access network device can carry the control information for requesting the parameters provided by the application layer of the server in the GTP-U packet header and then send the GTP-U packet header to the core network device.

[0037] 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 sixth transmission parameters; the sixth transmission parameters are parameters provided by a third application layer to a third data link layer; the fifth transmission parameters are parameters provided by a fourth data link layer to a fourth application layer; the third uplink data packet is a data packet corresponding to a first service flow.

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

[0039] 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, and 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.

[0040] In a possible implementation, the third uplink data packet includes the seventh control information, the seventh control information includes the third information, the third information is used to request the terminal device to provide the fifth parameter, and the method further includes: carrying the third information in the fifth perception layer header, and sending the fifth perception layer header to the access network device. That is, the core network device can carry the control information sent by the access network device to the terminal device in the perception layer header, and then send the perception layer header to the access network device, and the access network device sends it to the terminal device.

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

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

[0043] In a possible implementation, the third uplink data packet includes the fifth transmission parameter, the fifth transmission parameter includes the seventh parameter, and the method further includes: carrying the seventh parameter in the eighth perception layer header, and sending the eighth perception layer header to the access network device. That is, the core network device can carry the transmission parameter sent by the access network device to the terminal device in the perception layer header, and then send the perception layer header to the access network device, and the access network device sends it to the terminal device.

[0044] In a possible implementation, the third uplink data packet includes a fifth transmission parameter, an eighth parameter of the fifth transmission parameter header, and the method further includes: carrying the eighth parameter in an eighth perception layer header, and sending the eighth perception layer header to the server. That is, the core network device can carry the transmission parameter sent by the access network device to the server in the perception layer header, and then send the perception layer header to the server.

[0045] In a 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 is used to request the 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 used by the server to request the eighth parameter to the access network device.

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

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

[0048] 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 beneficial to improving data transmission efficiency.

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

[0050] In a 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 can carry the parameter provided by the application layer of the server to the data link layer of the access network device in the perception layer header and send it to the core network device, and the core network device parses the sixth parameter from the perception layer header and then forwards it to the access network device.

[0051] In a 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. It can be seen that the application layer of the server can optimize the downlink data transmission based on the parameters provided by the data link layer of the access network device, thereby facilitating the improvement of data transmission efficiency.

[0052] In a possible implementation, before the fourth uplink data packet from the core network device is received, the method further includes: sending eighth control information to the core network device; the eighth control information is used to request an eighth parameter. That is, before the server receives 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 then the core network device forwards the eighth control information to the access network device.

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

[0054] In the seventh aspect, an embodiment of the present application provides a communication device, which may be a terminal device, or a device in a terminal device, or a device that can be used in combination 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 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 methods and beneficial effects described in the first aspect or the second aspect above.

[0055] In an eighth aspect, an embodiment of the present application provides a communication device, which may be an access network device, or a device in an access network device, or a device that can be used in combination 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 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 third aspect above.

[0056] In the ninth aspect, an embodiment of the present application provides a communication device, which may be a core network device, or a device in a core network device, or a device that can be used in combination with a core network device. Among them, 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 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.

[0057] In the tenth aspect, an embodiment of the present application provides a communication device, which may be a core network device, or a device in a core network device, or a device that can be used in combination with a core network device. Among them, 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.

[0058] In the 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 combination with a server. Among them, 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 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 fifth aspect above.

[0059] In aspect 12, an embodiment of the present application provides a communication device, the communication device comprising 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.

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

[0061] In a 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 configured.

[0062] 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 logic circuits or execution code instructions.

[0063] In aspect 15, an embodiment of the present application provides a computer-readable storage medium, in which a computer program or instructions are stored. When the computer program or instructions are 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.

[0064] In a sixteenth aspect, an embodiment of the present application provides a computer program product including instructions. When a communication device reads and executes the instructions, the communication device is caused to execute the method described in the first aspect, or the method described in the second aspect, or the method described in the third aspect, or the method described in the fourth aspect, or the method described in the fifth aspect.

[0065] In a seventeenth aspect, an embodiment of the present application provides a communication system. The communication system includes a terminal device, an access network device, a core network device, and a server. The terminal device is configured to execute the method described in the first aspect or the second aspect, the access network device is configured to execute the method described in the third aspect, the core network device is configured to execute the method described in the fourth aspect, and the server is configured to execute the method described in the fifth aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0066] Figure 1A FIG. [X] is a schematic diagram of a protocol stack architecture provided by an embodiment of the present application;

[0067] Figure 1B FIG. [X] is a schematic diagram of a network architecture provided by an embodiment of the present application;

[0068] Figure 2 FIG. [X] is a schematic diagram of a protocol stack architecture introducing a sensing layer provided by an embodiment of the present application;

[0069] Figure 3 FIG. [X] is a schematic flowchart of a communication method provided by an embodiment of the present application;

[0070] Figure 4 FIG. [X] is a schematic diagram of a UE-TLL sending data packets provided by an embodiment of the present application;

[0071] Figure 5 FIG. [X] is a schematic flowchart of another communication method provided by an embodiment of the present application;

[0072] Figure 6 FIG. [X] is a schematic diagram of the position of the SDP protocol in the protocol stack provided by an embodiment of the present application;

[0073] Figure 7 FIG. [X] is a schematic structural diagram of a communication device provided by an embodiment of the present application;

[0074] Figure 8 FIG. [X] is a schematic structural diagram of another communication device provided by an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0075] In this application, terms such as "first" and "second" are used to distinguish identical or similar items with basically the same functions and roles. Those skilled in the art can understand that terms such as "first" and "second" do not limit the quantity and execution order, and "first", "second", etc. do not necessarily mean different. "And / or" describes the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.

[0076] It should be understood that in this application, "at least one" means one or more; "multiple" means two or more. In addition, "equal to" in this application can be used in combination with "greater than" or "less than". In the case of "equal to" combined with "greater than", the technical solution of "greater than" is adopted; in the case of "equal to" combined with "less than", the technical solution of "less than" is adopted.

[0077] In this application, "sending information to... (such as a terminal device)" can be understood as the destination of the information being the terminal device. It can include directly or indirectly sending information to the terminal device. "Receiving information from... (such as a terminal device)" or "receiving information from... (such as a terminal device)" can be understood as the source of the information being the terminal device, and it can include directly or indirectly receiving information from the terminal device. Necessary processing may be performed on the information between the source and destination of the information transmission, such as format change, etc., 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 here.

[0078] First, the relevant names or terms involved in this application are described below to facilitate understanding by those skilled in the art.

[0079] I. Terminal device

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

[0081] II. Access Network Equipment

[0082] An access network device is a network-side device with wireless transceiver capabilities. The access network device can be a device that provides wireless communication functions for terminal devices in a radio access network (RAN), and thus can also be referred to as a RAN device. For example, the 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 evolved by 3GPP in the future, an access node in a WiFi system, a wireless relay node, a wireless backhaul node, etc. In communication systems using different radio access technologies (RATs), the names of devices with base station functions may vary. For example, in the LTE system, it can be called an eNB or eNodeB, and in the 5G system or NR system, it can be called a gNB. This application does not limit the specific name of the base station. The access network device can include one or more co-located or non-co-located transmission reception points. For another example, the access network device can include one or more central units (CUs), one or more distributed units (DUs), or one or more CUs and one or more DUs.

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

[0084] III. Core network device

[0085] The core network device is used to implement functions such as mobility management, data processing, session management, policy and charging. In systems with different access technologies, the names of the devices implementing the core network functions may be different, 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), etc. AMF is a network element used for access and mobility management of terminal devices, mainly involving functions such as location update, network registration, and handover control of terminal devices. SMF is a network element used for session management of terminal devices, mainly involving functions such as session establishment, modification, and release. UPF is a network element used for receiving and forwarding user data. UPF is controlled by SMF. Different logical network elements of 5GC can be deployed on the same or different physical devices. For example, AMF and SMF can be deployed on the same physical device or on two physical devices. In addition, the logical network elements of 5GC can be deployed on the same physical device as the network elements of the 4G core network. The device for implementing the functions of the core network device can be the core network device itself or a device capable of supporting the core network device to implement this function, such as a chip system or a combined device or component that can implement the functions of the core network device, and this device can be installed in the core network device.

[0086] IV. Server

[0087] The server can be an application server corresponding to multiple services and can provide multiple possible services for terminal devices. Among them, an application layer equivalent to the application layer of the terminal device can be set in the application server. In the embodiments of this application, the device for implementing the server function can be the server itself or a device capable of supporting the server to implement this function, such as a chip system or a combined device or component that can implement the server function, and this device can be installed in the server. In the embodiments of this application, the chip system can be composed of chips or can also include chips and other discrete devices.

[0088] V. Protocol Layer Architecture

[0089] The communication among the terminal device, network device, and server follows a certain protocol stack architecture. Please refer to Figure 1A , Figure 1A which is a schematic diagram of a protocol stack architecture provided by the embodiments of this application. As shown in Figure 1AAs shown, taking the example of a terminal device sending data packets to a server via a network device, the data packet transmission sequentially passes through the application layer -> transport layer -> network layer -> access layer -> physical layer of the terminal device, and then through the access layer -> data link layer -> physical layer of the network device, arriving at the physical layer -> data link layer -> network layer -> transport layer -> application layer of the server.

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

[0091] VI. Interaction between Different Protocol Layers

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

[0093] (1) The transport layer lacks the bandwidth capacity to interact with the access layer

[0094] During the process of a sender (such as a terminal device) transmitting data to a receiver (such as a network device), due to the limited nature of wireless resources and the instability of the wireless channel, congestion may occur during data transmission. When congestion occurs, if the sender continues to send a large number of data packets, it may lead to an increase in the data packet transmission delay or data packet loss. Therefore, congestion control is required.

[0095] In one implementation, the sender can prevent excessive data injection into the network through the TCP congestion control algorithm. Specifically, the transport layer of the sender can maintain a congestion window (Cwnd), and adopt a climbing strategy to continuously attempt to increase the transmission rate from a lower rate. That is, first use a smaller value of the congestion window. If it is confirmed that there is no network congestion, gradually increase the value of the congestion window and send more data packets. In this way, if the access layer bandwidth capacity is large, the process of using the climbing strategy for probing will consume a lot of time. For example, assume that the maximum transmission rate that the access layer can provide is 1 Tbps, and the transport layer starts probing from 1 Mbps. It will take hundreds of milliseconds to probe up to 1 Tbps, resulting in low bandwidth utilization.

[0096] It can be seen that if the transport layer can obtain the bandwidth capacity of the access layer, the time consumed in the probing transmission process can be saved, and the transmission efficiency can be improved.

[0097] (2) The application layer lacks the ability to interact with the access layer for bandwidth prediction

[0098] The application layer of the sender can adjust the application layer encoding according to the actual transmission rate of the data reaching the receiver, so as to adapt to the channel. For example, assume that the sender transmits 1080P video data. If the receiver experiences stuttering during the video playback, the application layer of the sender can automatically adjust to transmit 720P video data to reduce the bandwidth requirement for the access layer, thereby avoiding stuttering during the playback process. However, this adjustment method usually makes the adjustment after the channel change affects the data transmission, that is, the application layer encoding is triggered to be adjusted after experiencing a period of video playback stuttering, resulting in low data transmission stability.

[0099] It can be seen that if the application layer can obtain the predicted bandwidth change of the access layer, it can adjust the encoding in advance to avoid stuttering.

[0100] (3) The access layer lacks the ability to interact with the application layer for the attributes of data packets

[0101] For the traffic flows controlled by the same QoS flow, the access layer of the base station will use the same transmission processing (such as scheduling). Generally, the data packets belonging to the same service will be placed in the same QoS flow. However, the data packets belonging to the same service may have different QoS requirements, so that the attributes of the entire QoS flow will be set according to the data packet with the highest QoS requirement. For example, assume that the packet delay budget (PDB) of a part of the data packets in the QoS flow requires 10 ms, and the PDB of another part of the data packets requires 20 ms. Then the base station will schedule the entire QoS flow according to the PDB requirement of 10 ms, which will affect the capacity of the base station.

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

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

[0104] For the scenario of continuous data packet transmission, such as the scenario where the server downloads artificial intelligence (AI) model data to the UE, or the scenario where the UE uploads 3D model data to the server. Generally, after the application layer generates the data, it sends it to the access layer, and then the access layer sends it. In actual applications, during the transmission of the first model data, due to the change of the scenario, it may be necessary to switch the first model data to the second model data for transmission. At this time, the application layer will choose to terminate the transmission of the remaining data in the first model data and start to send the second model data. However, after the application layer terminates the transmission of the remaining data in the first model data, it will cause the data that the application layer has sent to the access layer in the first model data to become invalid. In this case, for the data that the application layer has sent to the access layer in the first model data, the access layer will start a discard timer according to the PDB requirement. Before the discard timer times out, it will continue to send this invalid data, which will not only affect the transmission delay of the second model data, but also increase the air interface burden.

[0105] It can be seen that if the access layer can know the invalid data packets, it will be beneficial to reduce the air interface burden.

[0106] (5) The access layer lacks interaction with the application layer for the sending time of the data packets

[0107] For periodic services, if the arrival times of multiple data packets in a periodic service at the base station access layer are close, and the PDB requirements for the multiple data packets are short, it will cause the base station to need to schedule a large number of data packets in a short time, resulting in a large capacity pressure on the base station.

[0108] It can be seen that if the access layer can provide the transmission time of the data packets in the application layer, so that the transmission time of the data packets in the application layer is dispersed, it will be beneficial to relieve the scheduling pressure of the base station.

[0109] VII. RTP Protocol

[0110] The RTP protocol is a network transmission protocol, usually created on the User Datagram Protocol (UDP). After being encapsulated and processed by the RTP protocol during network transmission, an RTP data packet containing an RTP header can be formed. Currently, if the application layer adopts the RTP protocol, it can use the RTP header to carry part of the application layer information to provide the information of the application layer to other protocol layers for transmission optimization. For example, by carrying the attribute information of the data packet in the RTP header, the access layer can distinguish data packets with different attributes (such as PDB, importance of the data packet, etc.), so as to adopt different transmission strategies for data packets with different attributes. However, this way of adopting the RTP protocol lacks generality. If the application layer does not adopt the RTP protocol, the interaction between the information of the application layer and other protocol layers cannot be achieved. In addition, this way also lacks a mechanism for other protocol layers (such as the access layer) to feedback information to the application layer.

[0111] Based on this, the present application proposes a communication method and device, which can efficiently interact information between different protocol layers, and has generality, which is beneficial to improving the transmission efficiency.

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

[0113] The following introduces the network architecture applicable to the embodiments of this application.

[0114] Please refer to Figure 1B , Figure 1B which is a schematic diagram of a network architecture provided for the embodiments of this application. As Figure 1B shown, taking the 5G system as an example, this network architecture can include three parts: the terminal device part, the operator network part, and the data network 104 (Data Network, DN) part.

[0115] The terminal device part includes the terminal device 101, and the terminal device 101 can also be referred to as a user equipment (UE). In the embodiments of this application, the terminal device 101 involved, as a device with wireless transceiver functions, can communicate with one or more core networks (CN) via the RAN 102.

[0116] The operator network may include a Unified Data Management (UDM) 108, an Access and Mobility Management Function (AMF) 105, a Session Management Function (SMF) 106, a Policy Control Function (PCF) 107, a User Plane Function (UPF) 103, a Radio Access Network (RAN) 102, etc. In the above operator network, the parts other than the RAN part may be referred to as the Core Network (CN) part or the core network part.

[0117] The Data Network (DN) 104, which may also be referred to as a Protocol Data Network (PDN), is generally a network located outside the operator network, such as a third-party network. The operator network can access multiple Data Networks (DNs) 104. Multiple services can be deployed on the Data Network (DN) 104, providing services such as data and / or voice for terminal devices.

[0118] A brief introduction to the network functions in the operator network is given below.

[0119] The RAN 102 can be regarded as a sub-network of the operator network and is the implementation system between the service nodes and the terminal devices in the operator network. For a terminal device to access the operator network, it first passes through the RAN 102 and can then be connected to the service nodes of the operator network through the RAN 102. The access network device in the embodiments of the present application is a device that provides wireless communication functions for terminal devices and may also be referred to as a network device.

[0120] The Access and Mobility Management Function (AMF) 105 (which may also be referred to as the AMF network element, the AMF network function, or the AMF network function entity) is a control-plane network function provided by the operator network and is responsible for the access control and mobility management of terminal devices accessing the operator network. For example, it includes functions such as mobile status management, allocation of user temporary identity identifiers, authentication and authorization of users, etc.

[0121] The Session Management Function (SMF) 106 (which may also be referred to as the SMF network element, the SMF network function, or the SMF network function entity) is a control-plane network function provided by the operator network and is responsible for managing the Protocol Data Unit (PDU) sessions of terminal devices.

[0122] The User Plane Function UPF 103 (which can also be referred to as the UPF network element, UPF network function, or UPF network function entity) is a gateway provided by the operator and serves as the gateway for communication between the operator's network and the Data Network DN 104. It is mainly responsible for processing user packets, such as forwarding, charging, etc.

[0123] The Unified Data Management network element UDM 108 (which can also be referred to as the UDM network element, UDM network function, or UDM network function entity) is a control plane function provided by the operator and is responsible for storing information such as the subscriber permanent identifier (SUPI), the generic public subscription identifier (GPSI) of the subscribed users, and credentials in the operator's network. Among them, the SUPI will be encrypted first during transmission, and the encrypted SUPI is called the subscription concealed identifier (SUCI). The information stored in UDM 108 can be used for the authentication and authorization of the terminal device to access the operator's network.

[0124] The Policy Control Function (PCF) 107 provides policies to the AMF and SMF, such as QoS policies, slice selection policies, etc.

[0125] The Application Function AF interacts with the 3GPP core network to provide application layer services. For example: providing application layer data routing and providing access network capabilities. AF can interact with PCF 107. The location of AF can be inside or outside the 5G core network. If AF is inside the 5G core network, then it can directly interact with PCF 107. If AF is outside the 5G core network, then the Network Exposure Function (NEF) acts as an intermediate node to forward the interaction content between AF and PCF 107. For example, forwarding through NEF.

[0126] Figure 1B Among them, N1, N2, N3, N5, N6, N7, N8, N10, and N11 are interface sequence numbers. The meanings of these interface sequence numbers can be referred to the meanings defined in the 3GPP standard protocol and will not be elaborated here. It should be noted that Figure 1B only an exemplary description is made with the terminal device being UE 101, Figure 1B and the interface names between the various network functions are only examples. In specific implementations, the interface names of this system architecture may also be other names, and the embodiments of this application do not make specific limitations on this.

[0127] The method provided by the embodiments of the present application will be described below in conjunction with the accompanying drawings. Before introducing the embodiments, some terms related to the embodiments of the present application are uniformly explained.

[0128] (1) Optimization of data transmission

[0129] The optimization of data transmission in the present application refers to enabling the performance of data transmission to be more adapted to the current communication situation and system capacity by adjusting some parameters of data transmission. Specifically, it can be one of the following two types of data transmission optimizations: ① 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 judging 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 discarding transmitted data, etc.

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

[0131] The transmission parameters of the data link in the present application are some parameters associated with 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 associated with the transmission of the data link. The present application does not limit this.

[0132] (3) Packet service attribute information

[0133] The packet service attribute information in the present application is some attribute information of the packet in the service to which the packet belongs, such as packet importance information, packet delay requirement information, packet integrity requirement information, packet invalidation information, the service type of the packet (such as voice, video, game, etc.), the coding information of the packet (such as coding type, coding resolution, frame rate), the jitter information of the packet, the application protocol type of the packet, the transport layer protocol type of the packet, etc. The present application does not limit this.

[0134] (4) IP five-tuple

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

[0136] (5) Packet

[0137] 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 traffic flow, for example, data packets corresponding to the first traffic flow. The first traffic flow can be the first QoS flow, or the first traffic flow can be the first data radio bearer (DRB), or the first traffic flow can be a traffic flow with the first IP attribute (such as an IP five-tuple).

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

[0139] In the embodiments of this application, to achieve efficient interaction between different protocol layers, a perception layer is introduced to transmit the 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 also be set in other positions, such as in the extension header of the network layer (IP), or can also be set in the extension header of other protocol layers. This application does not make any limitations in this regard.

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

[0141] Exemplarily, see Figure 2 , Figure 2 which is a schematic diagram of a protocol stack architecture introducing a sensing layer provided by an embodiment of the present application. As Figure 2 shown, the sensing 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 (GTP-U) protocol layer of the core network device. For ease of description, an embodiment of the present application takes the terminal device as a UE, the access network device as a RAN, and the core network device as a CN as an example for illustration. Among them, the sensing layer of the terminal device (UE-sensing layer) can be located between the TLL (UE-TLL) and the DLL (UE-DLL) of the terminal device, the sensing layer of the server (Server-sensing layer) can be located between the TLL (Server-TLL) of the server and the DLL of the access network device (such as RAN-DLL), and the sensing layer of the core network device (CN-sensing layer) is located above the CN-GTP-U layer. Figure 2 In, based on the sensing layer, two-way interaction between UE-TLL and UE-DLL, UE-TLL and RAN-DLL, and Server-TLL and RAN-DLL can be realized. For ease of understanding, an embodiment of the present application takes Figure 2 the protocol stack architecture shown as an example for illustration.

[0142] Taking the uplink transmission as an example, see Figure 3 , Figure 3 which is a schematic diagram of a communication method provided by an embodiment of the present application, and may include but is not limited to the following steps:

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

[0144] Regarding 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 the TLL for data transmission optimization. Therefore, the second transmission parameter can also be understood as the parameter provided by the DLL to the UE-TLL. Specifically, the second transmission parameter can include the transmission parameter of the data link. Optionally, the second transmission parameter can include the reference transmission rate, and the reference transmission rate can be used to indicate the maximum transmission rate that the DLL can provide for the first traffic flow. The second transmission parameter can also include the predicted transmission rate, and the predicted transmission rate can be used to indicate the maximum transmission rate that the DLL can provide for the first traffic flow at the predicted moment. The second transmission parameter can further include the data timing parameter, and the data timing parameter can be used to indicate the time when the DLL expects the UE-TLL to send the data packet.

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

[0146] Scenario 1: Regarding the UE-TLL requesting the second transmission parameter from the UE-DLL, for the purpose of distinguishing 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 the UE-DLL to the UE-TLL. The first parameter can be used by the TLL for data transmission optimization. The first parameter can include the transmission parameter of the data link. That is to say, the terminal device can carry the first information in the first sensing 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. Specifically, refer to S301a.

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

[0148] Among them, after the UE-DLL receives the first uplink data packet from the UE-TLL, it can parse the first sensing layer header of the first uplink data packet to obtain the first information, and then based on the first information, it can generate the first parameter and send the first parameter to the UE-TLL. Furthermore, the UE-TLL can adjust the transmission strategy of the uplink data packet corresponding to the first traffic flow based on the first parameter.

[0149] Scenario 2: For the UE-TLL to request the second transmission parameter from the RAN-DLL. To distinguish it from Scenario 1, in this scenario, the second transmission parameter is described as the second parameter, and the first control information in this scenario is described as the second information. The second parameter can be understood, for example, as the parameter provided by the RAN (such as RAN-DLL) to the UE-TLL. The second parameter may include parameters of the data link. The second parameter can be used for the TLL to optimize data transmission. Specifically, refer to S301b below.

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

[0151] Among them, the UE-DLL can parse the first sensing layer header of the first uplink data packet to obtain the second information, and then carry the second information in the first data link layer header and send the first data link layer header to the RAN. This is because access network devices usually do not parse the header content above the network layer. In this way, it can be avoided that the access network device parses the first sensing layer header from the first uplink data packet, making this application universal. Optionally, the UE-DLL can also forward the first sensing layer header to the access network device so that the access network device can obtain the second information by parsing the first sensing layer header. Optionally, the first data link layer header can be the data link layer header of the first uplink data packet, or 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 (such as the above-mentioned first data link layer header) in the embodiments of the present application can be an SDAP header, a PDCP header, an RLC header, or other data link layer headers, and the embodiments of the present application are not limited thereto.

[0152] Regarding the first transmission parameter, the first transmission parameter can be used for 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 packet service attribute information. Optionally, the first transmission parameter may include a data delay parameter, and the data delay parameter can be used to indicate the packet delay budget of the first data packet. The first data packet can be the data packet corresponding to the first service flow. The first transmission parameter may also include a data sequence parameter, and the data sequence parameter can be used to indicate the sequence identifier corresponding to the first data packet. The first transmission parameter may further include a data failure parameter, and the data failure parameter can be used to indicate the sequence identifier of the failed data packet. The first transmission parameter may further include a data importance level parameter, and the data importance level parameter can be used to indicate the importance level of the first data packet.

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

[0154] Since the DLL may be the UE-DLL and / or the RAN-DLL, it is described in Scenario 3 and Scenario 4 below respectively.

[0155] Scenario 3: For the UE-TLL to provide the first transmission parameters to the UE-DLL, in order to distinguish from Scenario 4, in this scenario, the first transmission parameters are described as the third parameters, which can be understood as the parameters provided by the UE-TLL to the UE-DLL. The third parameters can be used for the UE-DLL to optimize data transmission. The third parameters may include packet service attribute information. Specifically, refer to S301c.

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

[0157] In some embodiments, the second control information may be used to request the UE-TLL to provide data delay parameters, that is, the third parameters may be data delay parameters, and the UE-DLL may adjust the transmission strategy of the uplink data packet corresponding to the first traffic flow based on the data delay parameters. Among them, the data delay parameters may be used to indicate the packet delay budget (PDB) of the first data packet, and the first data packet is the data packet corresponding to the first traffic flow.

[0158] Optionally, the data delay parameters may indicate the PDB of the first data packet, or may indicate the PDB offset of the first data packet.

[0159] In the case where the data delay parameters indicate the PDB of the first data packet, after the UE-DLL obtains the PDB of the first data packet, it may adjust the discard timer according to the PDB of the first data packet. Exemplarily, assuming that the discard timer of the first data packet is originally set to 10 ms according to the reference PDB of the first traffic flow, and the UE-DLL determines that the PDB of the first data packet is 12 ms based on the data delay parameters, then the UE-DLL may start the discard timer based on the PDB of 12 ms, that is, the first data packet will be discarded only if it is not sent after the discard timer counts down for 12 ms.

[0160] When the data delay parameter indicates the PDB offset of the first data packet, after obtaining the PDB offset of the first data packet, the UE-DLL can determine the PDB of the first data packet according to the reference PDB of the first traffic flow and the PDB offset of the first data packet, and then adjust the discard timer according to the PDB of the first data packet. Exemplarily, assume that the reference PDB of the first traffic flow is 10 ms, and the UE-DLL determines that the PDB offset of the first data packet is 2 ms based on the data delay parameter. Then the UE-DLL can determine that the PDB of the first data packet is 12 ms, and start the discard timer based on the PDB of 12 ms.

[0161] 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 for the terminal device to receive the user operation and transmit the uplink data packet, and the time for the server to render the game screen and transmit the downlink data packet together determine the user experience. If the time consumed by the terminal device to receive the user operation and transmit the uplink data packet is long, then the time for the server to render the game screen and transmit the downlink data packet can be adjusted shorter. Correspondingly, if the time consumed by the server to render the game screen and transmit the downlink data packet is long, then the time for the terminal device to receive the user operation and transmit the uplink data packet can be adjusted shorter. In the embodiments of this application, the UE-TLL can provide the data delay parameter to the UE-DLL, so that the UE-DLL can flexibly adjust the PDB of the uplink data packet based on the data delay parameter.

[0162] Scenario 4: For the UE-TLL to request the first transmission parameter from the RAN-DLL, in order to distinguish it from Scenario 3, in this scenario, the first transmission parameter is described as the fourth parameter, and the fourth parameter can be understood as the parameter provided by the UE-TLL to the RAN-DLL. The fourth parameter can be used for the RAN-DLL to optimize data transmission. The fourth parameter can include packet service attribute information. Specifically, refer to S301d.

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

[0164] Among them, the UE-DLL can parse the first perception layer header of the first uplink data packet to obtain the fourth parameter, and then carry the fourth parameter in the second data link layer header and send the second data link layer header to the RAN. Optionally, the second data link layer header can be the data link layer header of the first uplink data packet, or the data link layer header of other uplink data packets corresponding to the first traffic flow.

[0165] It can be understood that the above Scenarios 1 to 4 can be combined arbitrarily, that is, the terminal device can carry any one of the above first information, second information, third parameter, and fourth parameter in the first sensing layer packet header of the first uplink data packet, or can carry any combination of the four, which can be specifically determined according to actual requirements.

[0166] Optionally, for the case where the terminal device carries the first information in the first sensing layer packet header, the terminal device can delete the first information from the first sensing layer packet header when or after executing step S301a of UE-DLL. Similarly, for the case where the terminal device carries the third parameter in the first sensing layer packet header, the terminal device can delete the third parameter from the first sensing layer packet header when or after executing step S301c of UE-DLL, which is beneficial to saving bit overhead.

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

[0168] S302 is a process for the above Scenarios 2 and 4. Specifically, after receiving the first uplink data packet of UE-TLL, UE-DLL obtains the second information and / or the fourth parameter, and UE-DLL can send these parameters to the RAN. Since UE-DLL may perform some processing on the first uplink data packet and then send it to the RAN device, or UE-DLL obtains the second information and / or the fourth parameter, and when a new data packet needs to be sent, the second information and / or the fourth parameter are placed in the new data packet and sent to the RAN. Therefore, a second uplink data packet is introduced as the uplink data packet sent by UE-DLL to the RAN. It should be noted that the first uplink data packet and the second uplink packet may be the same or different. In different scenarios, UE-DLL can modify some content of the first uplink data packet to obtain the second uplink data packet.

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

[0170] In some embodiments, the third data link layer packet header can carry the second information. After the RAN obtains the second information, the RAN can send a 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 can include any one of the following two manners:

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

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

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

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

[0175] Among them, after the UE-DLL obtains the data link layer packet header carrying the second parameter, it can extract the second parameter from the data link layer packet header. Then the terminal device can carry the second parameter extracted by the UE-DLL layer in the sensing layer packet header and send the sensing layer packet header carrying the second parameter to the UE-TLL. After receiving the sensing layer packet header, the UE-TLL can obtain the second parameter from the sensing layer packet header.

[0176] In Method 1, the RAN carries the second parameter in the data link layer packet header, sends the data link layer packet header to the terminal device, and the UE-DLL extracts the second parameter from the data link layer packet header and then carries the second parameter in the sensing layer packet header and sends it to the UE-TLL. In this way, the terminal device replaces the access network device to carry the second parameter in the sensing layer packet header, which can avoid the access network device modifying the packet header above the network layer.

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

[0178] Among them, the RAN can send a second parameter to the core network device so that the core network device carries the second parameter in the sensing layer header of the downlink data packet and then sends the downlink data packet with the second parameter carried in the sensing layer header 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 with the second parameter carried in 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 sensing layer header and send the sensing layer header with the second parameter carried to the access network device, and then the access network device sends the sensing layer header with the second parameter carried to the terminal device.

[0179] In Method 2, the RAN carries the second parameter in the GTP-U header, sends the GTP-U header to the core network device, and the core network device extracts the second parameter from the GTP-U header and then carries the second parameter in the sensing layer header and sends it to the access network device. Finally, the access network device sends the sensing layer header to the terminal device. In this way, the core network device replaces the access network device to carry the second parameter in the sensing layer header, which can avoid the access network device modifying the header above the network layer.

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

[0181] In an implementation scenario, for the case where the second parameter includes the 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 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 the congestion control of the first service flow. For example, assuming that the reference transmission rate is 500 Mbps, the UE-TLL can start setting the congestion window without starting from a smaller value (such as 1 Mbps), but can use a larger congestion window value (such as 250 Mbps), which is beneficial to reducing the time consumed by the probing mechanism and improving the bandwidth utilization rate.

[0182] In another implementation scenario, for the case where the second parameter includes the predicted transmission rate, the second information can be used to request the predicted transmission rate. The UE-TLL can adjust the transmission policy of the uplink data packets corresponding to the first traffic 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 traffic flow at a certain predicted moment. The UE-TLL can adjust the application layer coding of the first traffic flow based on the predicted transmission rate, such as adjusting the traffic frame rate or resolution. Exemplarily, assume that the current rate of 100 Mbps for the first traffic flow supports sending at a resolution of 2k, and the predicted transmission rate indicates that the maximum transmission rate that the RAN can provide for the first traffic flow changes to 20 Mbps after 2 s. Based on this, the UE-TLL can reduce the resolution to 1080p in advance, thereby improving the stability of data transmission.

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

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

[0185] S302d. The RAN adjusts the transmission policy of the uplink data packets corresponding to the first traffic flow based on the fourth parameter.

[0186] In some embodiments, before the RAN executes step S302b, it 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 for the optimization of data transmission by the RAN. The fourth parameter may include packet service attribute information. Among them, 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, and may include two methods: direct sending and indirect sending. The direct sending method includes: the RAN carries the third control information in the data link layer packet header, sends the data link layer packet header to the terminal device, and the UE-DLL extracts the third control information from the data link layer packet header, and then carries the third control information in the sensing layer packet header and sends it to the UE-TLL. The indirect sending method includes: the RAN sends the third control information to the core network device, the core network device carries the third control information in the sensing layer packet header, then sends the sensing layer packet header carrying the third control information to the RAN, and finally the RAN sends the downlink data packet carrying the third control information in the sensing layer packet header to the terminal device.

[0187] In an implementation scenario, for the case where the fourth parameter includes a data sequence parameter, the third control information can be used to request the data sequence parameter. The RAN can adjust the transmission policy of the uplink data packets corresponding to the first traffic flow based on the data sequence parameter. Specifically, the data sequence parameter can be used to identify data packets in different groups. Among them, the data packets in one group usually correspond to a complete application function. For example, all the data packets corresponding to an image can be divided into group A, all the data packets corresponding to an AI model can be divided into group B, all the data packets corresponding to a file can be divided into group C, and all the data packets corresponding to a three-dimensional (3D) object model can be divided into group D. Optionally, the data packets in the same group can use the same identifier as the data sequence parameter. For example, all the data packets corresponding to image A1 can use identifier 1 as the data sequence parameter, all the data packets corresponding to image A2 can use identifier 2 as the data sequence parameter, all the data packets corresponding to file C1 can 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 according to the data sequence parameter of each data packet, and then can perform refined management on the uplink transmission time of the data packets in the same group. Optionally, the data packets in the same group can also use the identifiers of the data packets at the start position and the end position as the data sequence parameter. For example, the data packet a at the start position corresponding to image A1 can use identifier a1 as the data sequence parameter, and the data packet b at the end position corresponding to image A1 can use identifier b1 as the data sequence parameter; the data packet c at the start position corresponding to image A2 can use identifier c2 as the data sequence parameter, and the data packet d at the end 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 have been transmitted completely according to the data sequence parameter of the data packet at the start position and the data sequence parameter of the data packet at the end position in the same group, and then perform refined management on the uplink transmission time of the data packets belonging to the same group.

[0188] In another implementation scenario, for the case where the fourth parameter includes a data failure parameter, the third control information can be used to request the data failure parameter. The RAN can adjust the transmission policy of the uplink data packets corresponding to the first traffic flow based on the data failure parameter. Specifically, the data failure parameter can be used to identify the failed data packets among the data packets in the same group. The RAN can stop transmitting the failed data packets to the server based on the data failure parameter to save transmission resources and reduce the transmission delay of other unfailed data packets at the same time.

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

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

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

[0192] Since the TLL can be UE-TLL and / or Server-TLL, it is described separately through the following Scenario A and Scenario B.

[0193] Scenario A. For the RAN to request 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 for data transmission optimization. The fifth parameter can include data packet service attribute information. That is, the access network device can carry the third information in the third uplink data packet. For example, the third information can be carried in the GTP-U header, and then the core network device can carry the third information in the sensing layer header of the downlink data packet corresponding to the first service flow, so that the terminal device can obtain the third information from the sensing layer header of the downlink data packet corresponding to the first service flow, and then control the UE-TLL to provide the fifth parameter to the RAN-DLL. Specifically, refer to 303a - 303c.

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

[0195] Among them, the CN can carry the third information in the fifth sensing layer header, and then the core network device can send the fifth sensing layer header to the terminal device through the access network device. Optionally, the core network device can carry the third information in the sensing layer header of the downlink data packet corresponding to the first service flow.

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

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

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

[0199] Among them, after the UE-TLL generates the fifth parameter, the UE-TLL can send the fifth parameter to the UE-awareness layer. After receiving the fifth parameter, the UE-awareness layer can carry the fifth parameter in the awareness layer packet header and then send the awareness layer packet header carrying the fifth parameter to the UE-DLL. After receiving the awareness layer packet header carrying the fifth parameter, the UE-DLL can obtain the fifth parameter from the awareness layer packet header, carry the fifth parameter in the data link layer packet header, and send the data link layer packet header to the RAN.

[0200] Scenario B: For the RAN to request the sixth transmission parameter from the Server-TLL, in order to distinguish it from Scenario A, in this scenario, the sixth transmission parameter is described as the sixth parameter, 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 can include the packet service attribute information. The sixth parameter can be used for the RAN to optimize data transmission. That is to say, the access network device can carry the fourth information in the third uplink packet, and then carry the fourth information in the awareness layer packet header of the uplink data packet corresponding to the first service flow through the core network device, so that the server can obtain the fourth information from the awareness layer packet header of the uplink data packet corresponding to the first service flow, and then control the Server-TLL to provide the fifth parameter to the RAN.

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

[0202] Since the TLL can be UE-TLL and / or Server-TLL, it is described separately by the following Scenario C and Scenario D.

[0203] Scenario C: For the RAN to provide the fifth transmission parameter to the UE-TLL. To distinguish it from Scenario D, in this scenario, the fifth transmission parameter is described as the seventh parameter, which can be understood as the parameter provided by the RAN-DLL to the UE-TLL. The seventh parameter can be used for the optimization of data transmission by the TLL. The seventh parameter may include the transmission parameters of the data link. Specifically, refer to S303d - S303f below.

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

[0205] Among them, the CN can carry the seventh parameter in the eighth perception layer packet header, and then the core network device can send the eighth perception layer packet header to the terminal device through the access network device. Optionally, the core network device can carry the seventh parameter in the perception layer packet header of the downlink data packet corresponding to the first service flow.

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

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

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

[0209] S304, The CN sends the 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 the ninth perception layer packet header, and the ninth perception layer packet header carries the fourth information and / or the eighth parameter.

[0210] S304 is the process for Scenario B and Scenario D described above. Specifically, after the CN receives the third uplink data packet from the RAN, the CN obtains the fourth information and / or the eighth parameter, and the CN can send these parameters to the server. Since the CN may perform some processing on the first uplink data packet before sending it to the server, or, after the CN obtains the fourth information and / or the eighth parameter, when a new data packet needs to be sent, the fourth information and / or the eighth parameter are placed in the new data packet and sent to the server. Therefore, a fourth uplink data packet is introduced as the uplink data packet sent by the CN to the server.

[0211] In some embodiments, the ninth perception layer packet header carries the fourth information. Specifically, refer to S304a - 304c below.

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

[0213] Among them, the server can generate the sixth parameter based on the fourth information. After the server generates the sixth parameter, it can carry the sixth parameter in the perception layer packet header and then send the perception layer packet header carrying the sixth parameter to the CN.

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

[0215] Among them, the CN can receive the perception layer packet header carrying the sixth parameter, obtain the sixth parameter from the perception layer packet header, and then send the sixth parameter to the RAN.

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

[0217] In an implementation scenario, for the case where the sixth parameter includes a data delay parameter, the RAN can adjust the transmission policy of the downlink data packet corresponding to the first traffic 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 traffic 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 according to the determined PDB of the data packet. For example, assuming that the data delay parameter indicates that the PDB offset of the first data packet is 4 ms and the reference PDB of the data packet corresponding to the first traffic flow is 10 ms, then the RAN can determine that the PDB of the first data packet is 14 ms. Furthermore, the RAN can schedule the first data packet based on 14 ms, that is, the RAN can send the first data packet within 14 ms. In this way, compared with the RAN scheduling the first data packet based on 10 ms, the scheduling pressure on the access network device can be alleviated. In this way, the server can dynamically indicate the PDBs of different data packets to the access network device when transmitting different data packets, which is beneficial to improving the flexibility of data transmission.

[0218] In another implementation scenario, for the case where the sixth parameter includes a data sequence parameter, the RAN can adjust the transmission policy of the downlink data packet corresponding to the first traffic flow based on the data sequence parameter. Among them, the RAN can determine whether the transmission of the same packet is completed based on the data sequence parameter, and then perform refined management on the downlink transmission time of the data packets in the same packet.

[0219] In yet another implementation scenario, for the case where the sixth parameter includes a data failure parameter, the RAN can adjust the transmission policy of the downlink data packet corresponding to the first traffic flow based on the data failure parameter. Among them, the RAN can stop transmitting the expired data packets to the terminal device based on the data failure parameter to save transmission resources and reduce the transmission delay of other non-expired data packets at the same time.

[0220] In yet another implementation scenario, for the case where the sixth parameter includes a data importance level parameter, the RAN can adjust the transmission policy of the downlink data packet corresponding to the first traffic flow based on the data importance level parameter. For example, when the RAN transmits data packets with a high importance level, it can use a smaller PDB for transmission to improve the transmission reliability of data packets with a high importance level.

[0221] In some embodiments, the ninth sensing layer packet header can carry the eighth parameter. Specifically, see 304d below.

[0222] S304d, the server adjusts the transmission policy of the downlink data packet corresponding to the first traffic flow based on the eighth parameter.

[0223] In some embodiments, the server may send eighth control information to the access network device, and the eighth control information may be used to request the access network device to provide an eighth parameter. Wherein, the manner in which the server sends the eighth control information to the access network device may include: the server carries the eighth control information in the perception layer packet header and sends the perception layer packet header carrying the eighth control information to the CN; the CN obtains the eighth control information from the perception layer packet header and sends the eighth control information to the RAN.

[0224] In an implementation scenario, for the case where 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 of the downlink data packets corresponding to the first service flow based on the reference transmission rate. For example, when starting congestion control for the first service flow, the server may adjust the value of the congestion window based on the reference transmission rate, so as to avoid starting the probe from too small a value of the congestion window.

[0225] In another implementation scenario, for the case where 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 policy of 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 certain predicted moment. The server may adjust the application layer encoding of the first service flow based on the predicted transmission rate, such as adjusting the service frame rate or resolution. In this way, the server can reduce the service frame rate or resolution in advance before the transmission rate corresponding to the first service flow decreases, avoiding the situation of playback jitter.

[0226] In yet another implementation scenario, for the case where the eighth parameter includes Server-data timing parameters, the eighth control information may be used to request Server-data timing parameters. The server may adjust the transmission policy of the downlink data packets corresponding to the first service flow based on the Server-data timing parameters. Specifically, the Server-data timing parameters may indicate the time when the RAN expects the server to send data packets. The server may adjust the sending time of the downlink data packets corresponding to the first service flow based on the Server-data timing parameters. For periodic services, by indicating the expected time to send data packets to the server, the RAN can avoid the situation where the arrival times of each data packet are too close, and avoid the situation where the access network device needs to schedule a large number of data packets in a short time when the PDB requirements are tight.

[0227] In Figure 3 In the illustrated embodiment, by introducing the perception layer, different protocol layers can interact more efficiently based on the perception layer, and at the same time, the solution has generality, which is beneficial to improving data transmission efficiency and enhancing data transmission performance.

[0228] It should be noted that the scenarios involved in the embodiments of the present application can be presented separately or in combination. For example, Scenario 1 to Scenario 4 can be combined arbitrarily, and Scenario A to Scenario D can be combined arbitrarily, etc. For different scenarios, the presentation forms of the control information and transmission parameters can be different. For example, for Scenario 1, the first control information can be the first information; for Scenario 2, the first control information can be the second information; for the combined case of Scenario 1 and Scenario 2, the first control information can include the first information and the second information. Another example is that for Scenario C, the fifth transmission parameter can be the seventh parameter; for Scenario D, the fifth transmission parameter can be the eighth parameter; for the combined case of Scenario C and Scenario D, the fifth transmission parameter can include the seventh parameter and the eighth parameter. It can be understood that introducing different descriptions for the control information and transmission parameters is to distinguish the control information and transmission parameters in different scenarios, and does not constitute a limitation to the present application.

[0229] Figure 3 The embodiments of the present application are described from the perspective of the terminal device sending an uplink data packet to the server. Next, the embodiments of the present application are described from the perspective of the server sending a downlink data packet to the terminal device.

[0230] Please refer to Figure 5 , Figure 5 which is a schematic flowchart of another communication method provided by the embodiments of the present application. Figure 5 Taking downlink transmission as an example, it may include but is not limited to the following steps:

[0231] 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 sensing layer header A, and the sensing layer header A includes control information A and / or transmission parameter A.

[0232] Among them, the control information A can be used to request a transmission parameter B. The transmission parameter B can be understood as a parameter provided by the RAN-DLL to the Server-TLL. The transmission parameter B can be used for the TLL to optimize data transmission, and the transmission parameter B can include the transmission parameters of the data link.

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

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

[0235] Among them, CN can carry control information A in the GTP-U header, and then send the GTP-U header carrying control information A to the RAN. The RAN can obtain control information A from the GTP-U header.

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

[0237] Among them, 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 the sensing layer header and then send the sensing layer header carrying transmission parameter B to the server. After receiving the sensing layer header carrying transmission parameter B, the server can obtain transmission parameter B from the sensing layer header.

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

[0239] Among them, the implementation principle and process of step S501c are similar to those of step S304d above and will not be elaborated here.

[0240] In some embodiments, the sensing layer header A can carry transmission parameter A, and transmission parameter A can be understood as the parameter provided by Server-TLL to RAN-DLL. Transmission parameter A can be used for optimizing data transmission by the RAN. Transmission parameter A can include data service packet attribute information. The CN can obtain transmission parameter A from the sensing layer header A and then send transmission parameter A to the RAN. Specifically, refer to S501d and S501e below.

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

[0242] Among them, the implementation principle of step S501d is similar to that of step S501a above and will not be elaborated here.

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

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

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

[0246] Regarding control information B, control information B can be used to request transmission parameter d1 and / or transmission parameter d2. Among them, transmission parameter d1 can be understood as a parameter provided by RAN-DLL to Server-TLL. Transmission parameter d1 can be used for TLL to perform transmission optimization. Transmission parameter d1 can include transmission parameters of the data link. Transmission parameter d2 can be understood as a parameter provided by UE-TLL to RAN-DLL. Transmission parameter d2 can be used for RAN to optimize data transmission. Transmission parameter d2 can include packet service attribute information. Since control information B can be used to request transmission parameter d1 and / or transmission parameter d2, it is described separately through Scenario 1 and Scenario 2 below.

[0247] Scenario 1: Regarding control information B used to request transmission parameter d1, in order to distinguish it from Scenario 2, in this scenario, control information B is described as control information b1. Specifically, refer to S502a below.

[0248] S502a, RAN generates transmission parameter d1 based on control information b1.

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

[0250] Scenario 2: Regarding control information B used to request transmission parameter d2, in order to distinguish it from Scenario 1, in this scenario, control information B is described as control information b2. Specifically, refer to S502b and S502c below.

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

[0252] Among them, CN can carry control information b2 in the perception layer packet header and send the perception layer packet header carrying control information b2 to RAN. Then RAN can send the perception layer packet header carrying control information b2 to the UE. Next, the UE-perception layer can obtain control information b2 from the perception layer packet header and then send information b2 to UE-TLL. Optionally, RAN can also carry control information b2 in the perception layer packet header and send the perception layer packet header carrying control information b2 to the UE.

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

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

[0255] Regarding the transmission parameter C, the transmission parameter C may include the transmission parameter c1 and / or the transmission parameter c2. Among them, the transmission parameter c1 can be understood as the parameter provided by the Server-TLL to the RAN-DLL. The transmission parameter c1 can be used for the optimization of data transmission by the RAN. The transmission parameter c1 may include the packet service attribute information. The transmission parameter c2 can be understood as the parameter provided by the RAN-DLL to the UE-TLL. The transmission parameter c2 can be used for the optimization of data transmission by the TLL. The transmission parameter c2 may include the transmission parameters of the data link. Since the transmission parameter C may include the transmission parameter c1 and / or the transmission parameter c2, it is described separately through the following Scenario 3 and Scenario 4.

[0256] Scenario 3: Regarding the transmission parameter C including the transmission parameter c1, specifically, the following step S502d can be referred to.

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

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

[0259] Scenario 4: Regarding the transmission parameter C including the transmission parameter c2, specifically, the following steps S502e and S502f can be referred to.

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

[0261] Among them, the CN can carry the transmission parameter c2 in the sensing layer header and send the sensing layer header carrying the transmission parameter c2 to the RAN. Then the RAN can send the sensing layer header carrying the transmission parameter c2 to the UE-sensing layer. Then the UE-sensing layer can obtain the transmission parameter c2 from the sensing layer header and then send the transmission parameter c2 to the UE-TLL. Optionally, the RAN can also carry the transmission parameter c2 in the sensing layer header and send the sensing layer header carrying the transmission parameter c2 to the UE.

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

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

[0264] S503, the RAN sends the 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.

[0265] Among them, the control information C can be used to request the transmission parameter E. The transmission parameter E can be understood as the parameter provided by the UE-TLL to the RAN-DLL. The transmission parameter E can be used for the RAN to optimize data transmission. The transmission parameter E can include packet service attribute information. The transmission parameter D can be understood as the parameter provided by the RAN-DLL to the UE-TLL. The transmission parameter D can be used for the TLL to perform transmission optimization. The transmission parameter D can include the transmission parameters of the data link.

[0266] In some embodiments, the downlink data packet C can include a perception layer header, and the perception layer header can include the control information C and / or the transmission parameter D. In this case, the RAN can first send the control information C and / or the transmission parameter D to the CN, and the CN will carry the control information C and / or the transmission parameter D in the perception layer header and then send the perception layer header carrying the control information C and / or the transmission parameter D to the RAN.

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

[0268] Optionally, the RAN can also carry the control information C and / or the transmission parameter D in the 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.

[0269] In Figure 5 the illustrated embodiment, by introducing the perception layer, the interaction between different protocol layers can be more efficient based on the perception layer, and at the same time the solution has generality, so it is beneficial to improve the data transmission efficiency and enhance the data transmission performance.

[0270] In the embodiments 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 used to describe multimedia sessions. It is a text-based protocol and can be used for the negotiation of media types and coding schemes during session establishment. Exemplarily, please refer to Figure 6 , Figure 6It is a schematic diagram of the position of the SDP protocol in the protocol stack provided by the embodiments 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 to trigger the perception layer protocol from the server 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.

[0271] It should be noted that in the embodiments of the present application, when it is described that protocol layer A sends header A to protocol layer B, it can be understood that protocol layer A sends a data packet including header A to protocol layer B. The data packets involved in the embodiments of the present application can be data packets associated with the same service flow. In addition, the control information sent by DLL to TLL in the embodiments 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 UE-TLL to RAN-DLL can be described as uplink T2D control information, and the control information sent by Server-TLL to RAN-DLL can be described as downlink T2D control information. The transmission parameters sent by TLL to DLL can also be described as T2D transmission parameters, which can be specifically divided into uplink T2D transmission parameters and downlink T2D transmission parameters.

[0272] In addition, to implement the embodiments of the present application, the embodiments of the present application also provide a general design of the perception layer header, which can be carried in the uplink data packet or the downlink data packet. Please refer to Table 1. Table 1 is an example of the information carried by the perception layer header:

[0273] Table 1

[0274]

[0275]

[0276] Among them, the "empty packet indication" field can be used to indicate the non-existence of the perception layer packet header in subsequent data packets. The "flow identifier" can be used to identify the first service flow. The "termination bit" can be used to indicate whether the information ends. For example, if the termination bit of the D2T control information takes the value of 0, it can indicate the end of the D2T control information; if the termination bit of the D2T control information takes the value of 1, it can indicate that the next line is still D2T control information. Each bit in the "D2T control information" field can be used to represent a request switch. For example, the first bit can represent the request switch for the reference transmission rate. When the first bit takes the value of 1, it can indicate that the D2T control information is used to request the reference transmission rate, that is, the request for the reference transmission rate is enabled; when the first bit takes the value of 0, it can indicate that the D2T control information does not request the reference transmission rate, that is, the request for the reference transmission rate is disabled. The "D2T transmission parameter existence indication" field can be used to indicate the existing D2T transmission parameters, specifically including the field length and the field bit mapping (bitmap). Each bit in the bitmap can be used to indicate whether a certain D2T transmission parameter exists. The "D2T transmission parameter: reference transmission rate" field can indicate the reference transmission rate. According to whether the perception layer packet header is carried in the uplink data packet or the downlink data packet, it can be determined whether the parameter transmission rate is the uplink reference transmission rate or the downlink reference transmission rate. The "T2D transmission parameter existence indication" field can indicate the existing T2D transmission parameters, specifically including the field length and the bitmap. Each bit in the bitmap can be used to indicate whether a certain T2D transmission parameter exists.

[0277] The present application provides a communication device, which can be used to implement the functions of the above-mentioned terminal device, access network device, core network device, or server. The communication device can be a terminal device, an access network device, a core network device, or a server. The communication device includes units corresponding one by one to the methods / operations / steps / actions executed by the terminal device, access network device, core network device, or server in the above method embodiments. The unit can be a hardware circuit, software, or a combination of hardware circuit and software. Please refer to Figure 7 , Figure 7 FIG. shows a schematic structural diagram of a communication device 700 according to 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 configured to process signaling and / or data. 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;

[0278] In one implementation, when the communication device 700 is a terminal device, where:

[0279] An interface unit 701 for 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.

[0280] In this embodiment, for the specific implementation manners of the above interface unit 701 and processing unit 702, reference can be made to Figure 3 and Figure 5 the specific implementation steps of the UE-DLL therein, which will not be elaborated herein.

[0281] In another embodiment, when the communication device 700 is a terminal device, where:

[0282] An interface unit 701 for 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 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.

[0283] In this embodiment, for the specific implementation manners of the above interface unit 701 and processing unit 702, reference can be made to Figure 3 and Figure 5 the specific implementation steps of the UE-TLL therein, which will not be elaborated herein.

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

[0285] An interface unit 701 for 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 parameters are parameters provided by the data link layer of the access network device to the first application layer; the fourth parameters are parameters provided by the first application layer to the data link layer of the access network device; the second uplink data packet is a data packet corresponding to a first service flow.

[0286] In this embodiment, for the specific implementation manners of the above interface unit 701 and processing unit 702, reference can be made to Figure 3 and Figure 5 the specific implementation steps of the access network device therein, which will not be elaborated herein.

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

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

[0289] In this embodiment, for the specific implementation manners of the above interface unit 701 and processing unit 702, reference may be made to Figure 3 and Figure 5 the specific implementation steps of the core network device therein, which will not be elaborated herein.

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

[0291] An interface unit 701, configured 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 eighth parameters; the fourth information is used to request sixth parameters; the eighth parameters are parameters provided by a data link layer of an access network device to a second application layer, and the sixth parameters are parameters provided by the second application layer to the data link layer of the access network device; the fourth uplink data packet is a data packet corresponding to a first service flow.

[0292] In this embodiment, for the specific implementation manners of the above interface unit 701 and processing unit 702, reference may be made to Figure 3 and Figure 5 the specific implementation steps of the server therein, which will not be elaborated herein.

[0293] As Figure 8 shown, a communication device 800 provided by an embodiment of the present application is used to implement the functions of the above terminal device, or access network device, or core network device, or server. The device may be a communication device or a device in a communication device. The communication device may be a terminal device, or an access network device, or a core network device, or a server. The device in the communication device may be a chip system or a chip in the communication device. Among them, the chip system may be composed of chips, or may include chips and other discrete devices.

[0294] The communication device 800 includes at least one processor 810, which is used to implement the processing functions of the device (such as a terminal device, or an access network device, or a core network device, or a server) in the method provided by the embodiments of the present application. The communication device 800 may further include a communication interface 820, which is used to implement the transceiver operations of the device (such as a terminal device, or an access network device, or a core network device, or a server) in the method provided by the embodiments of the present application. In the embodiments of the present application, the communication interface may be a transceiver, a circuit, a bus, a module, or other types of communication interfaces, and is used to communicate with other devices through 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 embodiments.

[0295] The communication device 800 may further include at least one memory 830, which is used to store 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, and may be electrical, mechanical, or other forms, and is used for information interaction between devices, units, or modules. The processor 810 may cooperate with the memory 830. The processor 810 may execute the program instructions stored in the memory 830. At least one of the at least one memory may be included in the processor.

[0296] In the embodiments of the present application, the specific connection medium between the above communication interface 820, processor 810, and memory 830 is not limited. In the embodiments of the present application Figure 8 it is shown that the memory 830, processor 810, and communication interface 820 are connected through a bus. The bus is represented by a thick line in Figure 8 The connection manners between other components are only for illustrative purposes and are not to be construed as limiting. The bus may be divided into an address bus, a data bus, a control bus, etc. For the sake of convenience of representation, Figure 8 only one thick line is used to represent it in

[0297] 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, what the communication interface 820 outputs or receives can be a baseband signal. When the communication device 800 is specifically a device (terminal device, or access network device, or core network device, or server), what the communication interface 820 outputs or receives can be a radio frequency signal. In the embodiments of the present application, the processor can be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor can be a microprocessor or any conventional processor, etc. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as being executed by a hardware processor, or executed by a combination of hardware and software modules in the processor.

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

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

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

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

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

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

[0304] The method steps in the embodiments of the present application may be implemented in a hardware manner or by a processor executing software instructions. The software instructions may be composed of corresponding software modules, and the software modules may be stored in a random access memory (RAM), flash memory, read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, hard disks, removable hard disks, CD-ROMs, or any other form of storage medium well 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 may also be a component of the processor. The processor and the storage medium may be located in the ASIC. Additionally, the ASIC may be located in an access network device or a terminal. Of course, the processor and the storage medium may also exist as discrete components in the terminal or the access network device.

[0305] 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 instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are executed in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer program or instructions can be stored in a computer-readable storage medium or transmitted through the computer-readable storage medium. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server integrating one or more available media. The available medium can be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; it can also be an optical medium, such as a DVD; or it can be a semiconductor medium, such as a solid state drive (SSD).

[0306] In various embodiments of the present application, if there is no special description and logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0307] It can be understood that the various numerical numbers involved in the embodiments of the present application are only for the convenience of description and do not limit the scope of the embodiments of the present application. The magnitudes of the serial numbers of the above processes do not mean the order of execution. The order of execution of each process should be determined by its function and internal logic.

[0308] The embodiments of the present application also provide a computer-readable storage medium in which computer-executable instructions are stored. When the computer-executable instructions are executed, the methods executed by the terminal device, or the access network device, or the core network device, or the server in the above method embodiments are implemented.

[0309] The embodiments of the present application also provide a computer program product that includes a computer program. When the computer program is executed, the methods executed by the terminal device, or the access network device, or the core network device, or the server in the above method embodiments are implemented.

[0310] It should be noted that, for the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations. However, those skilled in the art should know that this application is not limited by the described action sequence, because according to this application, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0311] The descriptions of the embodiments provided in this application can be referred to each other. The descriptions of each embodiment have their own emphases. For the parts not detailed in a certain embodiment, reference can be made to the relevant descriptions of other embodiments. For the convenience and brevity of description, for example, the functions and steps performed by 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 method embodiments can also refer to, combine with, or quote from each other among the device embodiments.

[0312] Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of this application, not to limit them; although this application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions recorded in the foregoing embodiments, or perform equivalent replacements on some or all of the technical features; and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A communication method, characterized in that, The method includes: 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, and 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, characterized in that, 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, and 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, wherein 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, wherein 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-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 traffic 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 traffic flow at the predicted time; 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 traffic 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 traffic 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 traffic 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 traffic flow based on the fourth parameter.

18. The method according to claim 17, wherein 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, 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, 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, wherein The method further includes: Receive 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, wherein Before receiving the third uplink data packet from the access network device, it further includes: Receive 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, Includes a module for executing 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.

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

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, a method according to any one of claims 1 to 12, or a method according to any one of claims 13 to 15, or a method according to any one of claims 16 to 28, or a method according to any one of claims 29 to 35 is implemented.

Images