Data transmission method, device, related equipment and storage medium

Abstract

The present application discloses a data transmission method, apparatus, transmitting device, receiving device, and storage medium. The method includes: a transmitting device transmitting a data packet; the data packet sequence includes a first portion and a second portion; the first portion is determined by a first functional entity at layer 3 of the transmitting device; the second portion is determined by at least one second functional entity at layer 2 of the transmitting device; and the first functional entity is connected to the at least one second functional entity.

Description

Technical Field

[0001] The present application relates to the field of wireless communications, and in particular to a data transmission method, apparatus, related equipment, and storage medium. Background Art

[0002] The design goal of a minimalist network (Lite Network) for next-generation mobile communications proposes the introduction of user plane (UP) functions (also known as data plane functions) at Layer 3 (L3) for data processing. The introduction of the L3 UP protocol layer provides data sorting capabilities to ensure that packets are delivered to upper layers in order.

[0003] In order to sort and distribute data packets in order, each data packet needs to be assigned a sequence number (SN). However, in related technologies, the length of the SN is not a whole byte, which increases the complexity of data packet processing. Summary of the Invention

[0004] To solve related technical problems, the embodiments of the present application provide a data transmission method, apparatus, related equipment and storage medium.

[0005] The technical solution of the embodiment of the present application is implemented as follows:

[0006] The present invention provides a data transmission method, which is applied to a transmitting device and includes:

[0007] Sending a data packet; the sequence relationship of the data packet includes a first part and a second part; the first part is determined by a first functional entity of the sending device L3; the second part is determined by at least one second functional entity of the sending device layer two (L2, Layer2); the first functional entity is connected to at least one second functional entity.

[0008] In the above scheme, the first part includes the first link identifier for transmitting the data packet; the first link at least represents the connection between the first functional entity and a second functional entity; and / or the second part contains first information; the first information represents the transmission order of the data packet on the corresponding second functional entity.

[0009] In the above solution, when sending the data packet, the method further includes:

[0010] The second functional entity corresponding to the first link sends the second part of the sequential relationship of the data packet.

[0011] In the above solution, the first link identifier includes one of the following:

[0012] Corresponding second functional entity identifier;

[0013] First link index.

[0014] In the above solution, the first part identifies one or more consecutive data packets transmitted on the first link.

[0015] In the above solution, the determination includes at least one of the following:

[0016] Generation and / or resetting of data packet sequence numbers;

[0017] Selection of the initial value of the data packet sequence number;

[0018] Increment or decrement of packet sequence numbers;

[0019] The use of packet sequence numbers in packet sorting;

[0020] The sequence number of the data packet identifies a second functional entity.

[0021] In the above solution, the first functional entity selects at least one link for sending data; each link represents at least a connection between the first functional entity and a second functional entity;

[0022] Use at least one link to send data packets.

[0023] In the above solution, the first functional entity selects at least two links for sending data; the method further includes:

[0024] The first functional entity sends second information; the second information represents the data sending order of the at least two links.

[0025] In the above solution, the first functional entity sends the second information, including one of the following:

[0026] The first functional entity sends a protocol data unit (PDU), where the PDU carries the second information;

[0027] The first functional entity sends a media access control control element (MAC CE), where the MAC CE carries the second information;

[0028] The first functional entity sends downlink control information (DCI); the DCI carries the second information;

[0029] The first functional entity sends uplink control information (UCI); the UCI carries the second information.

[0030] In the above solution, the first functional entity sends the second information to the second functional entity; and the second functional entity sends the MAC CE.

[0031] In the above scheme, the link identifier of the link in the last sending order adjacent to the second link among the at least two links is sent through the second link among the at least two links, or the link identifier of the link in the next sending order adjacent to the second link among the at least two links is sent.

[0032] In the above solution, the first functional entity selects at least one link for sending data, including one of the following:

[0033] The first functional entity selects at least one link for sending data according to transmission conditions of air interface data of at least two second functional entities;

[0034] The first functional entity selects at least one link for sending data according to the amount of data requested by the at least two second functional entities;

[0035] The first functional entity receives second information sent by a receiving end device; selects at least one link for sending data according to the second information; and the second information represents a data sending order of the at least one link.

[0036] In the above solution, the first functional entity selects a target link for sending data; the target link at least represents a connection between the first functional entity and a second functional entity;

[0037] A data packet of a source link is sent on a target link; the source link at least represents a connection between the first functional entity and a second functional entity.

[0038] In the above solution, the method further includes:

[0039] The first functional entity sends third information; the third information includes the target link identifier.

[0040] In the above solution, the first functional entity sends the third information, including one of the following:

[0041] The first functional entity sends a PDU, where the PDU carries the third information;

[0042] The first functional entity sends a MAC CE, where the MAC CE carries the third information;

[0043] The first functional entity sends a DCI; the DCI carries the third information;

[0044] The first functional entity sends UCI; the UCI carries the third information.

[0045] In the above solution, the first functional entity sends the third information to the second functional entity corresponding to the source link; and the second functional entity corresponding to the source link sends the MAC CE.

[0046] In the above solution, the first functional entity determines the target link to be selected for sending data based on the transmission parameters of the air interface data of the second functional entity corresponding to the source link;

[0047] or,

[0048] The first functional entity receives third information sent by the receiving end device; determines the need to select a target link for sending data based on the third information; and the third information includes the target link identifier.

[0049] The present application also provides a data transmission method, which is applied to a receiving device and includes:

[0050] Receive a data packet; the sequence relationship of the data packet includes a first part and a second part; the first part is determined by a first functional entity of the sending device L3; the second part is determined by at least one second functional entity of the sending device L2; the first functional entity is connected to at least one second functional entity.

[0051] In the above scheme, the first part includes the first link identifier for transmitting the data packet; the first link at least represents the connection between the first functional entity and a second functional entity; and / or the second part contains first information; the first information represents the transmission order of the data packet on the corresponding second functional entity.

[0052] In the above solution, the second part of the sequence relationship of the data packets is determined by one of the following methods:

[0053] The second functional entity of the layer 2 of the receiving end device corresponding to the first link receives the second part of the sequence relationship of the data packet;

[0054] The second part of the sequence relationship of the data packets is determined according to the sequence of the HARQ processes of the received data packets.

[0055] In the above solution, the first link identifier includes one of the following:

[0056] The second functional entity identifier of the corresponding sending end device;

[0057] First link index.

[0058] In the above solution, the first part identifies one or more consecutive data packets transmitted on the first link.

[0059] In the above solution, at least one link is used to receive data packets; each link at least represents a connection between a first functional entity of the receiving end device L3 and a second functional entity of the receiving end device L2.

[0060] In the above solution, at least two links are used to receive data packets; the method further includes:

[0061] The first functional entity of the receiving end device receives second information; the second information represents the data sending order of the at least two links.

[0062] In the above solution, the first functional entity of the receiving device receives the second information, including at least one of the following:

[0063] The first functional entity of the receiving end device receives a PDU, where the PDU carries the second information;

[0064] The first functional entity of the receiving end device receives a MAC CE, where the MAC CE carries the second information;

[0065] The first functional entity of the receiving end device receives DCI; the DCI carries the second information;

[0066] The first functional entity of the receiving device receives UCI; the UCI carries the second information.

[0067] In the above solution, the second functional entity of the receiving device receives the MAC CE, parses the MAC CE, obtains the second information, and sends the second information to the first functional entity of the receiving device.

[0068] In the above scheme, the link identifier of the link in the previous sending order adjacent to the second link in the at least two links is received through the second link in the at least two links, or the link identifier of the link in the next sending order adjacent to the second link in the at least two links is received.

[0069] In the above solution, the first functional entity of the receiving device selects at least two links for sending data; and sends second information to the sending device; the second information represents the data sending order of the at least one link.

[0070] In the above solution, the method further includes:

[0071] The first functional entity of the receiving end device receives third information; the third information includes a target link identifier; the target link at least represents a connection between the first functional entity and a second functional entity;

[0072] The target link is used to send data packets of the source link; the source link at least represents a connection between a first functional entity and a second functional entity.

[0073] In the above solution, the first functional entity of the receiving device receives the third information, including at least one of the following:

[0074] The first functional entity of the receiving end device receives a PDU, where the PDU carries the third information;

[0075] The first functional entity of the receiving end device receives a MAC CE, where the MAC CE carries the third information;

[0076] The first functional entity of the receiving end device receives DCI; the DCI carries the third information;

[0077] The first functional entity of the receiving device receives UCI; the UCI carries the third information.

[0078] In the above solution, the second functional entity of the receiving end device corresponding to the source link receives the MAC CE, parses the MAC CE, obtains the third information, and sends the third information to the first functional entity of the receiving end device.

[0079] In the above solution, the method further includes:

[0080] The first functional entity of the receiving end device sends third information; the third information includes a target link identifier; the target link at least represents a connection between the first functional entity and a second functional entity;

[0081] The target link is used to send data packets of the source link; the source link at least represents a connection between a first functional entity and a second functional entity.

[0082] The embodiment of the present application further provides a data transmission device, which is provided on a transmitting end device and includes: a first functional entity unit and a second functional entity unit; wherein,

[0083] The first functional entity unit and the second functional entity unit are used to send data packets; the sequence relationship of the data packets includes a first part and a second part; the first part is determined by the first functional entity unit of the sending end device L3; the second part is determined by at least one second functional entity unit of the sending end device L2; the first functional entity unit is connected to at least one second functional entity unit.

[0084] The embodiment of the present application further provides a data transmission device, which is provided on a receiving end device and includes: a first functional entity unit and a second functional entity unit; wherein,

[0085] The first functional entity unit and the second functional entity unit are used to receive data packets; the sequence relationship of the data packets includes a first part and a second part; the first part is determined by the first functional entity of the sending device L3; the second part is determined by at least one second functional entity of the sending device L2; the first functional entity is connected to at least one second functional entity.

[0086] The embodiment of the present application further provides a sending end device, comprising: a first communication interface and a first processor; wherein,

[0087] The first communication interface is used to send data packets; the sequence relationship of the data packets includes a first part and a second part; the first part is determined by the first functional entity of the sending device L3; the second part is determined by at least one second functional entity of the sending device L2; the first functional entity is connected to at least one second functional entity.

[0088] The embodiment of the present application further provides a receiving end device, comprising: a second communication interface and a second processor; wherein,

[0089] The second communication interface is used to receive data packets; the sequence relationship of the data packets includes a first part and a second part; the first part is determined by the first functional entity of the sending device L3; the second part is determined by at least one second functional entity of the sending device L2; the first functional entity is connected to at least one second functional entity.

[0090] The embodiment of the present application further provides a sending end device, comprising: a first processor and a first memory for storing a computer program that can be run on the processor,

[0091] The first processor is configured to execute the steps of any one of the above-mentioned methods on the sending end device side when running the computer program.

[0092] The embodiment of the present application further provides a receiving end device, comprising: a second processor and a second memory for storing a computer program that can be run on the processor,

[0093] The second processor is configured to execute the steps of any one of the above-mentioned methods on the receiving end device side when running the computer program.

[0094] An embodiment of the present application also provides a storage medium on which a computer program is stored. When the computer program is executed by a processor, the computer program implements the steps of any of the above-mentioned methods on the sending device side, or implements the steps of any of the above-mentioned methods on the receiving device side.

[0095] The data transmission method, apparatus, related equipment, and storage medium provided by the embodiments of the present application include: a sending device sending a data packet; the sequence relationship of the data packet includes a first part and a second part; the first part is determined by a first functional entity of the sending device L3; the second part is determined by at least one second functional entity of the sending device L2; the first functional entity is connected to at least one second functional entity; a receiving end of a receiving device receives the data packet; an end-to-end L3 UP link is decomposed into an L3 functional entity part and a functional entity part of L2 connected to the L3 functional entity, thereby realizing the sending and receiving of short SN data packets and reducing the overhead of the data packet. BRIEF DESCRIPTION OF THE DRAWINGS

[0096] Figure 1 A schematic diagram illustrating the connection between an L3 UP entity and multiple MAC function entities;

[0097] Figure 2 This is a flow chart of the data transmission method according to an embodiment of the present application;

[0098] Figure 3 This is a schematic diagram of the architecture of the SN control solution implemented by the L3 UP and multiple MAC functional entities in the embodiment of the present application;

[0099] Figure 4 This is a schematic diagram of the functions and connection relationships of the L3 UP and MAC functional entities on the network side and the terminal side of the application embodiment of this application;

[0100] Figure 5 This is a schematic diagram of the format of the control PDU used in the embodiment of this application;

[0101] Figure 6 This is a schematic diagram of the MAC PDU subheader format of the MAC CE in the embodiment of the present application;

[0102] Figure 7 This is a schematic diagram of the content format of the MAC CE in the embodiment of the present application;

[0103] Figure 8 This is a structural diagram of a data transmission device according to an embodiment of the present application;

[0104] Figure 9 This is a schematic structural diagram of another data transmission device according to an embodiment of the present application;

[0105] Figure 10 This is a schematic diagram of the structure of the sending end device according to an embodiment of the present application;

[0106] Figure 11 This is a schematic diagram of the receiving device structure according to an embodiment of the present application;

[0107] Figure 12This is a structural diagram of the data transmission system according to an embodiment of the present application. DETAILED DESCRIPTION

[0108] The present application will be described in further detail below with reference to the accompanying drawings and embodiments.

[0109] The design goal of the Lite Network for next-generation mobile communications proposes the introduction of the UP protocol layer at L3 for data processing. Regardless of whether other protocol entities exist at L2 (in the fifth-generation mobile communication technology (5G), L2 includes four protocol layers (also called protocol sublayers): Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), and MAC. Each protocol layer corresponds to a corresponding protocol entity (also called protocol function entity)), the UP protocol entity of the L3 UP protocol layer is directly connected to the MAC protocol entity of L2.

[0110] In third-generation mobile communication technologies (3G), fourth-generation mobile communication technologies (4G), and 5G systems, on the terminal side, the access stratum (AS) only has the control plane (CP) function, that is, only the RRC protocol layer; correspondingly, on the network side, the radio access network (RAN) also has only the CP function, that is, only the RRC protocol layer. The RRC protocol layer performs radio resource control functions and does not have the data processing functions of the UP protocol layer. Specifically, the UP function can be introduced into the L3 layer (the RRC layer of the AS and RAN in the 5G system is called a 3-layer protocol) of the AS and RAN, that is, the L3 UP protocol layer (also referred to as the L3 UP protocol entity or L3 UP entity) is introduced, which is referred to as the L3 UP entity in the following description.

[0111] The L3 UP entity has a data sorting function to ensure that data packets are delivered to the upper layer in order. When an L3 UP entity is connected to multiple L2 functional entities at the same time, the L3 UP entity needs to sort the data submitted by multiple L2 entities; it also needs to distribute data packets between different L2 entities. For example, Figure 1As shown, the L3 UP entity is directly connected to the L2 MAC function entity via an IP flow. In other words, the transport between the L3 UP entity and the MAC function entity is an IP flow, a logical channel that carries the corresponding IP. Each IP flow transmits IP packets. To enable the L3 UP entity to sort and dispatch packets in order, each packet must be assigned a SN. Traditionally, the 5G PDCP function entity defines SNs as two bytes (12 or 18 bits). The SN is 12 or 18 bits, rather than a full byte (e.g., 8, 16, 24, 32 bits, etc.), because the latency between the receiving and transmitting PDCP function entities necessitates a long sorting window. The PDCP SN is directly related to the sorting window length (the sorting window length is half the maximum SN value). However, if a full-byte SN is used, a short full-byte SN results in a too small sorting window, while a long full-byte SN results in an excessively large sorting window, resulting in wasteful usage.

[0112] Such non-integer SNs need to be sorted in combination with the Hyper Frame Number (HFN), which increases the complexity of data packet processing.

[0113] Based on this, in various embodiments of the present application, by decomposing the SN on the entire link, that is, the end-to-end L3 UP link, into the L3 UP part and each L2 functional entity (such as the MAC functional entity) connected to the L3 UP functional entity, the transmission and reception of short SN packets are achieved, which not only reduces the packet overhead but also realizes the flexible definition of SN.

[0114] This embodiment of the present application provides a data transmission method, applied to a transmitting device, including:

[0115] Send a data packet; the sequence relationship of the data packet includes a first part and a second part; the first part is determined by a first functional entity of the sending device L3; the second part is determined by at least one second functional entity of the sending device L2; the first functional entity is connected to at least one second functional entity.

[0116] In actual application, the transmitting device may be a network device (specifically a base station), and the receiving device may be a terminal; the transmitting device may also be a terminal, and correspondingly, the receiving device may be a network device.

[0117] The first part is determined by the first functional entity of the sending device L3. In other words, the first part is maintained on the first functional entity of the sending device L3. Correspondingly, the second part is determined by at least one second functional entity of the sending device L2. It can also be understood that the second part is maintained on at least one second functional entity of the sending device L2.

[0118] In which, the determination or maintenance can also be understood as operation; specifically, the first part is determined by the first functional entity of the sending device L3, which can be understood as the operation of the first part on the first functional entity of the sending device L3; accordingly, the second part is determined by at least one second functional entity of the sending device L2, which can be understood as the operation of the second part on at least one second functional entity of the sending device L2.

[0119] Here, the determining or maintaining may include at least one of the following:

[0120] Generation and / or resetting of data packet SN;

[0121] Selection of the initial value of the data packet SN;

[0122] Increase or decrease of the packet SN (i.e., increase or decrease of the SN);

[0123] The use of packet SN in packet sorting;

[0124] The SN of the data packet identifies a second functional entity.

[0125] During this period, the resetting of the data packet SN may include: resetting the data packet SN to an initial value.

[0126] The increase of the data packet SN means that for the data to be sent, the value of the SN of the corresponding data packet is adopted in an ascending order, that is, the value of the SN of each data packet is obtained by accumulation; correspondingly, the increase of the data packet SN means that for the data to be sent, the value of the SN of the corresponding data packet is adopted in an ascending order, that is, the value of the SN of each data packet is obtained by subtraction.

[0127] The use of the data packet SN in data packet sorting may include: sorting in sequence (such as sorting of adjacent SNs), discarding or restoring SNs, and the like.

[0128] The order relationship of the data packets may also be referred to as a sorting sequence of the data packets.

[0129] In actual application, the first functional entity of L3 may be referred to as a UP functional entity of L3; and the second functional entity of L2 may be a MAC functional entity.

[0130] In one embodiment, the first part includes a first link identifier for transmitting the data packet; the first link at least represents a connection between the first functional entity and a second functional entity.

[0131] In one embodiment, the second part includes first information; the first information represents the transmission order of the data packets on the corresponding second functional entity.

[0132] Here, in actual application, when the second functional entity of L2 is a MAC functional entity, the corresponding link can be called a MAC link, that is, the first link can be called a MAC link.

[0133] In one embodiment, the first link identifier may include one of the following:

[0134] Corresponding second functional entity identifier;

[0135] First link index.

[0136] In actual application, the first functional entity may be connected to multiple second functional entities to form multiple links. In this case, the first link index may be a sequential index of the first link in the multiple links, that is, a number index.

[0137] In actual application, the first part can identify one or more consecutive data packets transmitted on the corresponding first link.

[0138] The second functional entity identifier may be a second functional entity ID, etc.

[0139] From the above description, it can be seen that the sequence relationship of each data packet can include two parts: the first part is the sequence index or other identity identifier of the second functional entity link that transmits the data packet; the second part is the sending order of each data packet within the second functional entity link, that is, the SN that each data packet needs to carry; among them, the first part does not need to be transmitted on the air interface, and the receiving device only needs to receive the identity identification representation of the second functional entity link itself; and the second part is the SN assigned to each data packet by the second functional entity and needs to be transmitted on the air interface.

[0140] Based on this, in one embodiment, when sending a data packet, the method further includes:

[0141] The second part of the sequential relationship in which the second functional entity corresponding to the first link sends the data packets, that is, the second part of the sequential relationship in which the PDU sent by the second functional entity carries the data packets.

[0142] In actual application, when using Figure 1In the connection mode between the first functional entity and the second functional entity shown, the first functional entity needs to select a link to send data.

[0143] Based on this, in one embodiment, the first functional entity selects at least one link for sending data; each link represents at least a connection between the first functional entity and one second functional entity;

[0144] Use at least one link to send data packets.

[0145] In actual application, the first functional entity may select at least one link for sending data as needed.

[0146] Specifically, the first functional entity can select at least one link for sending data based on the transmission status of air interface data of at least two second functional entities; the first functional entity can also select at least one link for sending data based on the amount of data requested by at least two second functional entities; the first functional entity can also receive second information sent by a receiving device (network device); select at least one link for sending data based on the second information; the second information represents the data sending order of the at least one link.

[0147] Among them, the transmission status of the air interface data may include: the data transmission rate on the link, the proportion of the first functional entity PDU being segmented and sent, the proportion of the first functional entity PDU being cascaded and sent (that is, multiple service data units (SDUs) are placed in the data block of the same SN and sent), the block error rate (BLER) of data transmission, the data cache vacancy rate of the second functional entity, the proportion of data discarded in the cache of the second functional entity, etc.

[0148] When the first functional entity selects at least two links to send data packets, the receiving device needs to be informed of the data sending order of the at least two links; for example, assuming that the first functional entity is connected to the second functional entity 1, the second functional entity 2, the second functional entity 3, the second functional entity 4, and the second functional entity 5 respectively; and selects the link connected to the second functional entity 1 and the second functional entity 3 to send data packets, at this time, the receiving device needs to be informed of the data sending order between the link connected to the second functional entity 1 and the link connected to the second functional entity 3.

[0149] Based on this, in one embodiment, the method may further include:

[0150] The first functional entity sends second information; the second information represents the data sending order of the at least two links.

[0151] In one embodiment, the first functional entity sending the second information may include one of the following:

[0152] The first functional entity sends a PDU, where the PDU carries the second information;

[0153] The first functional entity sends a MAC CE, where the MAC CE carries the second information;

[0154] The first functional entity sends DCI; the DCI carries the second information.

[0155] Here, in actual application, the type of PDU sent by the first functional entity is a control PDU.

[0156] When the first functional entity sends the second information through the MAC CE, the first functional entity sends the second information to the second functional entity; and the second functional entity sends the MAC CE.

[0157] When sending the second information, different link identifiers may be sent through different links to reflect the data sending order of at least two links, thereby reducing the control information sent.

[0158] Based on this, in one embodiment, the link identifier of the link in the last sending order adjacent to the second link among the at least two links is sent through the second link among the at least two links, or the link identifier of the link in the next sending order adjacent to the second link among the at least two links is sent.

[0159] In actual application, during the data packet transmission process, a link switching process may occur due to the influence of various factors. When the link needs to be switched, the first functional entity needs to select a target link.

[0160] Based on this, in one embodiment, the first functional entity selects a target link for sending data; the target link at least represents a connection between the first functional entity and a second functional entity;

[0161] A data packet of a source link is sent on a target link; the source link at least represents a connection between the first functional entity and a second functional entity.

[0162] Here, in actual application, the first functional entity selects a target link as needed.

[0163] Specifically, the first functional entity can determine the target link to be selected for sending data based on the transmission parameters of the air interface data of the second functional entity corresponding to the source link; the first functional entity can also receive third information sent by the receiving end device (i.e., the network device); determine the target link to be selected for sending data based on the third information; the third information includes the target link identifier.

[0164] When link switching is performed, the receiving device needs to be informed of the target link.

[0165] Based on this, in one embodiment, the method includes:

[0166] The first functional entity sends third information; the third information includes the target link identifier.

[0167] Here, in one embodiment, the first functional entity sending the third information may include one of the following:

[0168] The first functional entity sends a PDU, where the PDU carries the third information;

[0169] The first functional entity sends a MAC CE, where the MAC CE carries the third information;

[0170] The first functional entity sends DCI; the DCI carries the third information.

[0171] The type of the PDU sent by the first functional entity may be a control PDU.

[0172] When sending the third information through the MAC CE, the first functional entity sends the third information to the second functional entity corresponding to the source link; the second functional entity corresponding to the source link sends the MAC CE.

[0173] Accordingly, an embodiment of the present application further provides a data transmission method, applied to a receiving device, comprising:

[0174] Receive a data packet; the sequence relationship of the data packet includes a first part and a second part; the first part is determined by a first functional entity of the sending device L3; the second part is determined by at least one second functional entity of the sending device L2; the first functional entity is connected to at least one second functional entity.

[0175] The receiving device uses the sequence relationship of the data packets, i.e., performs sorting, in the process of receiving the data packets; specifically, the first functional entity of L3 of the receiving device uses the first part; the second functional entity of L2 of the receiving device uses the second part.

[0176] In one embodiment, the second part of the sequence relationship of the data packets is determined by one of the following methods:

[0177] The second functional entity of L2 of the receiving end device corresponding to the first link receives the second part of the sequence relationship of the data packet;

[0178] The second part of the sequence relationship of the data packets is determined according to the sequence of the HARQ processes of the received data packets.

[0179] Here, in actual application, each data packet corresponds to a HARQ process, so the second part of the data packet sequence relationship can be determined based on the HARQ order. For example, if each data packet is assigned a HARQ process, then each HARQ process also corresponds to a data packet, and the data packet sequence relationship can be determined based on the order in which the data packets are received by each HARQ process. The embodiments of the present application do not limit the specific implementation of determining the second part of the data packet sequence relationship based on the order in which the HARQ processes receive the data packets.

[0180] In one embodiment, when the transmitting device uses at least one link to send data, the receiving device uses at least one link to receive data packets; each link at least represents a connection between a first functional entity of the receiving device L3 and a second functional entity of the receiving device L2.

[0181] When a transmitting device transmits data using at least two links, the receiving device receives data packets using at least two links. At this time, the first functional entity of the receiving device receives second information; the second information indicates the order in which data are transmitted on the at least two links, so that the data packets can be sorted according to the second information.

[0182] In one embodiment, the first functional entity of the receiving device receives the second information, including at least one of the following:

[0183] The first functional entity of the receiving end device receives a PDU, where the PDU carries the second information;

[0184] The first functional entity of the receiving end device receives a MAC CE, where the MAC CE carries the second information;

[0185] The first functional entity of the receiving device receives DCI; the DCI carries the second information.

[0186] Here, when the second information is received through the MAC CE, the second functional entity of the receiving device receives the MAC CE, parses the MAC CE, obtains the second information, and sends the second information to the first functional entity of the receiving device.

[0187] In one embodiment, when the transmitting device sends the link identifier of the link in the previous sending order adjacent to the second link through the second link among the at least two links, the receiving device receives the link identifier of the link in the previous sending order adjacent to the second link through the second link among the at least two links; when the transmitting device sends the link identifier of the link in the next sending order adjacent to the second link through the second link among the at least two links, the transmitting device receives the link identifier of the link in the next sending order adjacent to the second link among the at least two links through the second link among the at least two links.

[0188] When the receiving end device is a base station, the sending end device (ie, the terminal) may be controlled to select a link for sending data, ie, the second information may be sent to the sending end device.

[0189] Based on this, in one embodiment, the method may further include:

[0190] The first functional entity of the receiving device selects at least one link for sending data and sends second information to the sending device; the second information represents the data sending order of the at least one link.

[0191] In one embodiment, the first functional entity of the receiving device sends the second information to the sending device, including:

[0192] The first functional entity of the receiving end device sends a PDU, where the PDU carries the second information;

[0193] The first functional entity sends a MAC CE, where the MAC CE carries the second information;

[0194] The first functional entity sends a DCI; the DCI carries the second information;

[0195] The first functional entity sends UCI; the UCI carries the second information.

[0196] Here, in actual application, the manner in which the first functional entity of the receiving device sends the second information is similar to the specific manner in which the first functional entity of the transmitting device sends the second information, and will not be repeated here.

[0197] In one embodiment, the method may further include:

[0198] The first functional entity of the receiving end device receives third information; the third information includes a target link identifier; the target link at least represents a connection between the first functional entity and a second functional entity;

[0199] The target link is used to send data packets of the source link; the source link at least represents a connection between a first functional entity and a second functional entity.

[0200] Here, in one embodiment, the first functional entity of the receiving end device receives the third information, including at least one of the following:

[0201] The first functional entity of the receiving end device receives a PDU, where the PDU carries the third information;

[0202] The first functional entity of the receiving end device receives a MAC CE, where the MAC CE carries the third information;

[0203] The first functional entity of the receiving end device receives DCI; the DCI carries the third information;

[0204] The first functional entity of the receiving device receives UCI; the UCI carries the third information.

[0205] When the third information is received through the MAC CE, the second functional entity of the receiving device corresponding to the source link receives the MAC CE, parses the MAC CE, obtains the third information, and sends the third information to the first functional entity of the receiving device.

[0206] When the receiving end device is a base station, the sending end device can be controlled to select a target link.

[0207] Based on this, in one embodiment, the method may further include:

[0208] The first functional entity of the receiving end device sends third information; the third information includes a target link identifier; the target link at least represents a connection between the first functional entity and a second functional entity;

[0209] The target link is used to send data packets of the source link; the source link at least represents a connection between a first functional entity and a second functional entity.

[0210] Here, in actual application, the first functional entity of the receiving end device sends the third information to the transmitting end device, including:

[0211] The first functional entity of the receiving end device sends a PDU, where the PDU carries the third information;

[0212] The first functional entity sends a MAC CE, where the MAC CE carries the third information;

[0213] The first functional entity sends a DCI; the DCI carries the third information;

[0214] The first functional entity sends UCI; the UCI carries the third information.

[0215] Here, in actual application, the manner in which the first functional entity of the receiving device sends the third information is similar to the specific manner in which the first functional entity of the sending device sends the third information, and will not be repeated here.

[0216] The present application also provides a data transmission method, such as Figure 2 As shown, the method includes:

[0217] Step 201: A transmitting end device sends a data packet; the sequence relationship of the data packet includes a first part and a second part; the first part is determined by a first functional entity of the transmitting end device L3; the second part is determined by at least one second functional entity of the transmitting end device L2; the first functional entity is connected to the at least one second functional entity;

[0218] Step 202: The receiving device receives the data packet.

[0219] The data transmission method provided by the embodiment of the present application is as follows: a sending end device sends a data packet; the sequence relationship of the data packet includes a first part and a second part; the first part is determined by a first functional entity of the sending end device L3; the second part is determined by at least one second functional entity of the sending end device L2; the first functional entity is connected to at least one second functional entity; the receiving end receives the data packet; the end-to-end L3 UP link is decomposed into an L3 functional entity part and a functional entity part of L2 connected to the L3 functional entity, and the L2 functional entity can define the length of the SN according to the service type, thereby realizing the sending and receiving of short SN data packets, which not only reduces the overhead of the data packet but also realizes the flexible definition of the SN.

[0220] The present application will be described in further detail below in conjunction with application examples.

[0221] In this application embodiment, the first functional entity of L3 is called L3 UP; the second functional entity of L2 is MAC functional entity; and the CP functional entity of L3 is called L3 CP.

[0222] In this application embodiment, a two-level SN mechanism, L3 UP and MAC, is adopted. By binding the SN to the link, a short SN mode is implemented in the air interface data packet. The end-to-end L3 UP SN selection mechanism is used to implement the hopping allocation of SN segments without compromising the continuity of the SN. The MAC functional entity dynamically defines the SN length according to the service type to reduce the transmission overhead caused by the SN length. For example, for high-real-time services, a short SN can be used (i.e., the SN length is reduced compared to related technologies), or even the SN can be eliminated (because there is no retransmission and sorting, so the SN is not required). For non-low-real-time, low-priority services, a longer SN than that of high-real-time services is used, and a best-effort transmission mode is adopted. When the air interface quality deteriorates, a dynamic MAC-level SN selection mechanism such as a long SN is adopted.

[0223] The sorting sequence (i.e., the order relationship) of each data packet consists of two parts: 1. The link identity identifier of the MAC link (the connection between the L3UP and the MAC functional entity) that transmits the data packet (i.e., the first part), such as the sequence index or other identity identifier of the MAC link; 2. The transmission order of each data packet within the MAC link that transmits the data packet (i.e., the link from the MAC layer to the PHY layer) (i.e., the second part). The identity identifier of the MAC link does not need to be transmitted over the air interface; the identity identifier of the link itself that receives the MAC PDU at the receiving end is sufficient; the SN assigned by the MAC to each MAC PDU needs to be transmitted over the air interface, that is, each MAC PDU carries the SN.

[0224] In this application embodiment, if Figure 3 The L3 UP is connected to multiple MAC functional entities; wherein 0# identifies the 0th MAC link, and so on, N# identifies the Nth MAC link.

[0225] The following combination Figure 3 Describe the functions of each functional entity.

[0226] First, the function of L3 CP is described.

[0227] The L3 CP (RRC functional entity) has the SN control function (also known as SN signaling control function). Specifically, the end responsible for signaling configuration (for example, the RRC on the network side) configures the MAC entity of the sender and receiver. The configuration content includes:

[0228] (1) The link identification identifier of each MAC link on the transmitting end, the sending window length, and the bit or byte length of the SN of the MAC link, that is, the value range of the SN. The value range of the SN determines the maximum number of data packets that can be sent on a MAC link. The SN length on each MAC link can be the same or different, and the SN on each MAC link is counted independently. The link identification identifier of the MAC link can be the MAC link number, such as 0, 1, 2, ...; it can also be a defined MAC ID, or other identifier that can identify each MAC link.

[0229] (2) The link identification identifier of each MAC link on the receiving end, the length of the receive sorting window, and the bit or byte length of the SN of the MAC link, that is, the value range of the SN. The range of the SN determines the maximum number of data packets that can be transmitted on a MAC link. The SN length of each MAC link can be the same or different. The SN of each MAC link is counted independently. The MAC link identification number can be the MAC link number, such as 0, 1, 2, ...; it can also be a defined MAC ID, or other identifier that can identify each MAC link.

[0230] Next, the functions of L3 UP are described.

[0231] (1) L3 UP has the SN selection function, which includes:

[0232] The L3 UP selects an available MAC link, obtains the MAC link sequence, and sends the MAC link sequence information (because different MAC links correspond to a group of SNs sent by the air interface for data packets, the MAC link sequence information can also be called SN selection information) to the peer L3 UP. The MAC link sequence can be used to sort data packets between different MAC links.

[0233] As part of the L3 UP flow control function, an available MAC link can be selected for data to be transmitted, and data can be transmitted over the selected MAC link. During data transmission, MAC link switching can also be performed. For example, the L3 UP on the transmitting end (e.g., the network-side L3 UP on the downlink or the terminal-side L3 UP on the uplink) selects a new MAC link for data transmission, i.e., the target MAC link, and is responsible for sending the identifier (e.g., number or MAC ID) of the predecessor old MAC link corresponding to the new MAC link to the receiving end via the new link. Alternatively, the L3 UP can send the identifier (number or MAC ID) of the successor new MAC link corresponding to the predecessor old MAC link (i.e., the source MAC link) to the receiving end via the old MAC link. When the L3 UP sends this link selection information (i.e., sending the identifier of the new MAC link or sending the identifier of the old MAC link), it can do so by introducing a control PDU into the L3 UP, i.e., the L3 UP generates a control PDU and sends it to the receiving end via the control PDU. Alternatively, it can send this information to the MAC functional entity and send it to the receiving end via a MAC CE or DCI carried by the PDCCH.

[0234] (2) The L3 UP has the function of ordering PDUs. Specifically, after receiving the L3 UP PDUs delivered in sequence by the lower layer (i.e., the MAC functional entity) at the receiving end (e.g., the L3 UP on the terminal side in the downstream direction and the L3 UP on the network side in the upstream direction), the L3 UP at the receiving end (e.g., the L3 UP on the terminal side in the downstream direction) orders the data on the link between the MAC links according to the order of the MAC links. The L3 UP at the receiving end can obtain the control information of the MAC link order (also known as the MAC link selection order) from the L3 UP at the transmitting end, and determine the overall ordering position of the data packets on each MAC link based on this control information. If the control information is sent in the form of an L3 UP control packet (i.e., the transmitting L3 UP sends a control PDU), the receiving L3 UP directly receives the control PDU from the transmitting L3 UP and parses it to obtain the control information of the MAC link sequence. If the control information is sent in the form of a MAC CE or DCI carried by a PDCCH, the receiving L3 UP obtains the control information of the MAC link sequence from the lower-layer MAC function entity.

[0235] Then, the functions of the MAC functional entity are described.

[0236] (1) The MAC functional entity has the SN allocation function, which includes:

[0237] The network-side MAC (the uplink and downlink schedulers of the network-side MAC are responsible for scheduling the uplink and downlink air interfaces, respectively) or the transmitting MAC functional entity (here, the transmitting end can be the network side or the terminal side) decides whether to enable the send window (similar to the MAC functional entity controlling the various cycles of semi-persistent scheduling (SPS) and discontinuous reception (DRX)). Specifically, this can be based on the service type or air interface channel quality. For example, if it is a burst of data packets with a long interval between data packets (such as more than 10ms or 8 MAC transmission time intervals (TTIs)), the send window does not need to be enabled. When the transmitting MAC decides whether to enable or not enable the send window, it needs to send an indication to the receiving MAC. The indication can be sent along with the first data packet or separately, such as in the DCI carried by the MAC CE and PDCCH along with the data packet, or it can be sent separately as a MAC CE or PDCCH.

[0238] The opening and closing of the sending window is synchronized with the opening and closing of the receiving window. Specifically, when the sending window is opened, the receiving window is also opened synchronously. When the sending window is closed, the receiving window is also closed synchronously.

[0239] If the send window is enabled, the MAC function entity on the sending end assigns SNs according to the order of the MAC PDUs sent and maintains the send window. A MAC PDU may contain multiple L3 UP PDUs. All L3 UP PDUs in this MAC PDU are identified by a single MAC layer SN. When constructing the MAC PDU, all MAC SUDs (L3 UP PDUs) are included in the MAC PDU in the order they were received from the L3 UP, i.e., they are set in the MAC PDU in the order they were received.

[0240] (2) The MAC functional entity has the PDU ordering function, which includes:

[0241] If the receive window is enabled, the receiving MAC function entity sorts the received MAC PDUs by SN and maintains the receive window. If the receive window is not enabled, the receiving MAC function entity directly delivers the received MAC PDUs to the L3 UP. When the MAC function entity sends L3 UP PDUs to the upper layer L3 UP, they are delivered in the sorted order. Because a MAC PDU may contain multiple L3 UP PDUs, the MAC delivery entity maintains the order in which each MAC SDU (also known as L3 UP PDU) is received and delivers them.

[0242] Figure 4 The functions and connection relationships of the L3 UP and MAC functional entities on the network side and the terminal side are shown. Figure 4 To describe the process of data transmission between the network side and the terminal side.

[0243] Both the network side and the terminal side have equal roles of receiver and sender, that is, the sender can be the network side and the receiver can be the terminal side; the sender can also be the terminal side and the receiver can be the network side.

[0244] The RRC function entity on the network side generates signaling for configuring the terminal and sends it to the RRC entity on the terminal side. The network side controls the terminal side.

[0245] In the downlink (DL) direction, when data is sent from the network to the terminal, the network's Layer 3 Up (L3UP) selects an available MAC link and determines the MAC link priority. Based on the MAC link priority, it generates a control PDU (which can also be a MAC CE or DCI) to select the SN for the terminal's Layer 3 Up (L3UP) and sends it to the terminal. This control PDU carries MAC link priority control information. Alternatively, the network's Layer 3 Up (L3UP) can send this information to the MAC CE entity, using a MAC CE or DCI. Simultaneously, the network's MAC entity's DL MAC scheduler controls whether to open a send window and configures it for the terminal. The DL MAC scheduler schedules the amount of data to be sent and the data content, constructing MAC PDUs. The terminal's MAC functional entity receives data based on the network's MAC configuration information (MAC CE or PDCCH). The terminal's Layer 3 Up (L3UP) receives the MAC link priority control information sent by the network's Layer 3 Up and determines the MAC link priority. Upon receiving data packets from the MAC link, they are sorted based on the MAC link priority control information. Submit the sorted data to the upper layer.

[0246] In the uplink (UL) direction, that is, when the terminal sends data to the network, the L3 UP on the network can select the MAC link and send the MAC link sequence to the terminal; or the L3 UP on the terminal can select the MAC link and send the MAC link sequence to the network. The L3 UP on the network receives the uplink data sent by the MAC, sorts it, and submits it to the upper layer. At the same time, the UL MAC scheduler (which can be on the network or terminal side) is responsible for controlling whether to open the send window and configures it to the terminal side through MAC CE or PDCCH. The UL MAC scheduler schedules the amount of data to be sent and the data content, and sends it to the MAC functional entity on the terminal side. The MAC on the terminal side constructs a MAC PDU and sends it to the network side. The L3 UP on the terminal side selects the MAC link according to the MAC link sequence and sends the data to the corresponding MAC functional entity.

[0247] In the above process, L3 UP selects an available MAC link, obtains the MAC link sequence, and sends the MAC link sequence information to the peer L3 UP. The MAC link sequence can be used to sort data packets between different MAC links.

[0248] In practical applications, there are three ways for L3 UP to send MAC link sequence information:

[0249] In the first method, the MAC link sequence information is sent in the form of L3 UP PDU. Specifically, the L3 UP constructs an L3 UP link selection control packet, that is, a control PDU. The control PDU carries the MAC link sequence information and is sent directly to the peer L3 UP.

[0250] The basic content of the L3 UP link selection control packet includes: MAC link identification (ie MAC link ID), such as MAC link number or MAC ID, etc. The format of the control PDU is as follows: Figure 5 shown.

[0251] The D / C field indicates whether the PDU is a control PDU or a data PDU. The D / C field is at least 1 bit long. Specifically, as shown in Table 1, when the value of the D / C field is 0, the PDU is identified as a control PDU; when the value of the D / C field is 1, the PDU is identified as a data PDU.

[0252] Bit Description 0 Control PDU 1 Data PDU

[0253] Table 1

[0254] PDU Type identifies the type of the PDU, as shown in Table 2. The length of PDU Type can be multiple bits, leaving options for adding new PDU types in the future.

[0255] Bit Description 000 MAC Link Selection 001-111 Reserved

[0256] Table 2

[0257] MAC Link ID is the identifier of the MAC link and has a length of N*1 bytes, where N = 1, 2, 3, .... Usually, N is set to 1, meaning the MAC link identifier is 1 byte long. In this case, an L3 UP can connect to a maximum of 256 MAC functional entities, or 256 MAC links.

[0258] When sending, the meaning of the information field in the L3 UP link selection control packet (i.e., the MAC link identifier) ​​is different on different MAC links and needs to be defined separately. For example, based on the order of MAC links, the MAC link identifier of the MAC link with the previous sending sequence can be defined on the current MAC link, that is, the link identifier of the predecessor MAC link can be defined on the current MAC link; the MAC link identifier of the MAC link with the next sending sequence can also be defined on the current MAC link, that is, the link identifier of the subsequent MAC link can be defined on the current MAC link.

[0259] When MAC link data packets are sequenced, data packets on the current MAC link are sequenced after data packets received on the predecessor MAC link. In practice, for multiple MAC links sending data, the first MAC link in the transmission order does not have a predecessor MAC link. Therefore, the L3 UP link selection control packet carrying MAC link sequence information is not sent on the first MAC link.

[0260] When MAC link packet sequencing is performed, packets received on the current MAC link are prioritized before packets received on subsequent MAC links. In practice, for multiple MAC links sending data, the last MAC link in the transmission sequence has no subsequent MAC link. Therefore, the L3 UP link selection control packet carrying MAC link sequence information is not sent on the last MAC link.

[0261] In actual applications, when MAC link switching is required during data transmission, user handoff, or air interface load balancing, the L3 UP also needs to select an available target MAC link and send the corresponding MAC link sequence information to the peer L3 UP. This allows data packets to be sorted across different MAC links based on the MAC link sequence. This also requires constructing a control PDU that carries the MAC link sequence information, i.e., the target MAC link identifier, and is sent directly to the peer L3 UP.

[0262] The specific sending timing is: L3 UP selects the data packet according to the rate at which the MAC on the MAC link sends data on the air interface. When the rate at which the MAC link sends data on the air interface is low, it means that the air interface of the MAC link is heavily loaded, the BLER of the air interface is poor, or the air interface link quality is poor, and it is necessary to change the MAC link to send data packets.

[0263] In this case, a control PDU can be sent on the source MAC link, and L3 UP sends an L3 UP link selection control packet on the source link. After receiving an ACK confirmation for the control packet (the confirmation can be an ACK of MAC HARQ, and then the MAC notifies L3 UP), it starts sending data on the air interface corresponding to the new MAC link (target).

[0264] Here, for the receiving end, after the receiving L3 UP receives the control PDU, it completes the data packet connection between the source MAC link and the target MAC link. Specifically, when the MAC entity on the source link receives the L3 UP link selection control packet or the last data packet identifier, it is considered that the MAC entity on the other end has sent all the data packets on the source MAC link. The MAC entity notifies the L3 UP that it has completed receiving the data on this MAC link. After receiving this indication, the L3 UP delivers the L3 UP PDU on the source MAC link to the upper layer in sequence, and simultaneously begins the in-sequence delivery processing of the newly received L3 UP PDU on the target MAC link.

[0265] In the second method, the L3 UP sends the MAC link sequence information to the MAC function entity. The MAC function entity sends it to the remote MAC function entity using a MAC CE. The remote MAC function entity parses the MAC CE, obtains the MAC link sequence information, and sends the MAC link sequence information to the remote L3 UP.

[0266] The basic content of the MAC CE includes the identifier of the MAC link, such as the MAC link number or the MAC link ID. The meaning of the MAC link identifier in the MAC CE is the same as that in the control PDU. For example, based on the sequence of the MAC links, the MAC link identifier of the MAC link of the previous transmission sequence can be defined on the current MAC link, that is, the link identifier of the predecessor MAC link can be defined on the current MAC link; the MAC link identifier of the MAC link of the next transmission sequence can also be defined on the current MAC link, that is, the link identifier of the subsequent MAC link can be defined on the current MAC link.

[0267] When L3 UP needs to select a MAC link, it directly sends the MAC link identification information to the MAC function entity of the corresponding link. The MAC function entity then constructs a MAC CE (which may be called a MAC link selection MAC CE) and sends it to the air interface.

[0268] In this application embodiment, a MAC CE may be defined, specifically including:

[0269] (1) Define the MAC PDU subheader information corresponding to the MAC CE; specifically, the index value of the MAC CE type is used to identify the MAC CE type. The MAC CE type is defined on the uplink shared channel (UL-SCH) and the downlink shared channel (DL-SCH). Figure 6 As shown in the figure, LCID is the index value of the MAC CE type.

[0270] (2) Define the content of MAC CE: the identification information of the MAC link. MAC Link ID is the identifier of the MAC link, with a length of N*1 bytes, where N=1,2,3,…. Figure 7 As shown, N is usually set to 1, that is, the MAC link identifier length is 1 byte. In this case, one L3 UP can connect to a maximum of 256 MAC function entities, that is, there are 256 MAC links.

[0271] When MAC link packet sequencing is performed, packets on the current MAC link are sequenced after packets received on the predecessor MAC link. In practice, for multiple MAC links sending data, the first MAC link in the transmission sequence does not have a predecessor MAC link. Therefore, a MAC CE carrying MAC link sequence information is not sent on the first MAC link.

[0272] When MAC link packet sequencing is performed, packets received on the current MAC link are sequenced before packets received on subsequent MAC links. In practice, for multiple MAC links sending data, the last MAC link in the transmission sequence has no subsequent MAC link. Therefore, a MAC CE carrying MAC link sequence information is not sent on the last MAC link.

[0273] In actual applications, when MAC link switching is required during data transmission, user handoff, or air interface load balancing, the L3 UP also needs to select an available target MAC link and send the corresponding MAC link priority information to the peer L3 UP. This allows data packets to be sorted across different MAC links based on the MAC link priority. This also requires the creation of a MAC CE, which carries the MAC link priority information (i.e., the target MAC link identifier) ​​and is sent to the peer L3 UP.

[0274] In the third method, the L3 UP sends the MAC link sequence information to the MAC function entity. The MAC function entity uses the DCI method to send it to the other end through the PDCCH. After the physical layer of the other end receives the PDCCH, it parses the MAC link sequence information and sends it to the MAC function entity. The MAC function entity then sends it to the L3 UP of the other end.

[0275] The basic content of the DCI includes the identification of the MAC link, such as the number of the MAC link or the ID of the MAC link, etc. The meaning of the identification information of the MAC link in the DCI is the same as that in the above-mentioned control PDU, for example: based on the sequence of the MAC links, the MAC link identification of the MAC link of the previous transmission sequence can be defined on the current MAC link, that is, the link identification of the predecessor MAC link can be defined on the current MAC link; the MAC link identification of the MAC link of the next transmission sequence can also be defined on the current MAC link, that is, the link identification of the subsequent MAC link can be defined on the current MAC link.

[0276] When L3 UP needs to select a MAC link, it sends the MAC link identification information directly to the MAC function entity of the corresponding link, and the MAC function entity constructs the DCI and sends it to the air interface.

[0277] In this application embodiment, DCI may be defined, specifically including:

[0278] The idle bits or additional bits in the existing DCI or UCI are used to carry the MAC link identification information. Moreover, since this information does not need to be sent every time, this information is optional in the DCI or UCI format.

[0279] During a MAC link handover, when the source MAC link sends its last MAC PDU, the transmitter sends a DCI or UCI message to the receiver, carrying the last MAC PDU information. Upon receiving the DCI or UCI, the receiver uses this information to identify the target MAC link and to determine that this is the last data packet on the source link.

[0280] For MAC downlink transmission (sent from the network side to the terminal side), the network side notifies the terminal side of the link selection information through the DCI carried by the PDCCH. For MAC uplink transmission (sent from the terminal side to the network side), the terminal side can notify the network side of the link selection information through the UCI carried by the PUCCH or PUSCH.

[0281] In actual application, any of the above methods can be selected as needed to send the MAC link sequence information, that is, the link selection information.

[0282] L3 UP can select a MAC link based on the air interface data transmission status of the lower-layer MAC functional entity. The air interface data transmission status may include the data transmission rate on the MAC link, the proportion of L3 UP PDUs that are fragmented and sent, the proportion of L3 UP PDUs that are concatenated and sent, the BLER of the data transmission, the MAC data buffer empty rate, and the proportion of data discarded in the MAC buffer.

[0283] The MAC function entity (also called the MAC layer) directly sends the amount of data to be allocated to the L3 UP, and the L3 UP can select a MAC link based on the amount of data to be allocated sent by the MAC function entity.

[0284] When the L3 UP is connected to only one MAC function entity (i.e., when there is only one MAC link), the L3 UP sends data directly to the MAC function entity. In this case, the L3 UP does not need to activate the MAC link control mechanism, i.e., control MAC link selection. The MAC function entity independently moves the send window or receive window (which can also be understood as the L3 UP controlling the MAC layer to continuously slide the send window, adjusting the window based on the received or sent data), ensuring that data is sent or received in sequence through the MAC layer.

[0285] When an L3 UP is connected to at least two MAC functional entities, that is, when there are at least two MAC links, the L3 UP enables the MAC link control mechanism, that is, instructs the MAC functional entity to move the sending or receiving window so that data can be sent or received in sequence through the MAC layer.

[0286] The solution provided by this application embodiment has the following advantages:

[0287] (1) MAC selects the appropriate SN solution based on the service type, which is flexible and highly real-time.

[0288] (2) The L3 UP and MAC two-level SN mechanism can shorten the end-to-end SN length from L3 UP to L3 UP;

[0289] (3) The MAC scheduler controls the sorting window, enabling the scheduler to control data, air interface resources, and air interface transmission in an integrated manner;

[0290] (4) Binding part of the SN information to the MAC link shortens the SN length without affecting the communication system.

[0291] In order to implement the method of the transmitting end device side of the embodiment of the present application, the embodiment of the present application also provides a data transmission device, which is set on the transmitting end device, such as Figure 8 As shown, the device includes: a first functional entity unit 801 and a second functional entity unit 802; wherein,

[0292] The first functional entity unit 801 and the second functional entity unit 802 are used to send data packets; the sequence relationship of the data packets includes a first part and a second part; the first part is determined by the first functional entity unit 801 of the sending end device L3; the second part is determined by at least one second functional entity unit 802 of the sending end device L2; the first functional entity unit is connected to at least one second functional entity unit.

[0293] In one embodiment, when sending a data packet, the second functional entity unit 802 corresponding to the first link is further configured to send the second part of the sequence relationship of the data packet.

[0294] In one embodiment, the first functional entity unit 801 selects at least one link for sending data; each link represents at least a connection between the first functional entity unit 801 and one second functional entity unit 802; and at least one link is used to send data packets.

[0295] In one embodiment, the first functional entity unit 801 selects at least two links for sending data; the first functional entity unit 801 may be further used to send second information; the second information represents the data sending order of the at least two links.

[0296] In one embodiment, the first functional entity unit 801 is specifically configured to perform one of the following:

[0297] The first functional entity unit 801 sends a PDU, where the PDU carries the second information;

[0298] The first functional entity unit 801 sends a MAC CE, where the MAC CE carries the second information;

[0299] The first functional entity unit 801 sends DCI; the DCI carries the second information.

[0300] In one embodiment, the first functional entity unit 801 sends the second information to the second functional entity unit 802; and the second functional entity unit 802 sends a MAC CE.

[0301] In one embodiment, the first functional entity unit 801 selects at least one link for sending data, including one of the following:

[0302] The first functional entity unit 801 selects at least one link for sending data according to the transmission status of air interface data of at least two second functional entities;

[0303] The first functional entity unit 801 selects at least one link for sending data according to the amount of data requested by at least two second functional entities;

[0304] The first functional entity unit 801 receives second information sent by a receiving end device; selects at least one link for sending data according to the second information; and the second information represents a data sending order of the at least one link.

[0305] In one embodiment, the first functional entity unit 801 is further configured to select a target link for sending data; the target link at least represents a connection between the first functional entity unit 801 and a second functional entity unit 802;

[0306] A data packet of a source link is sent on a target link; the source link at least represents a connection between the first functional entity and a second functional entity.

[0307] In one embodiment, the first functional entity unit 801 is further configured to send third information; the third information includes the target link identifier.

[0308] In one embodiment, the first functional entity unit 801 sends the third information, including one of the following:

[0309] The first functional entity unit 801 sends a PDU, where the PDU carries the third information;

[0310] The first functional entity unit 1001 sends a MAC CE, where the MAC CE carries the third information;

[0311] The first functional entity unit 801 sends DCI; the DCI carries the third information.

[0312] In one embodiment, the first functional entity unit 801 sends the third information to the second functional entity unit 802 corresponding to the source link; and the second functional entity unit 802 corresponding to the source link sends the MAC CE.

[0313] In one embodiment, the first functional entity unit 801 is specifically configured to:

[0314] Determine, based on the transmission parameters of the air interface data of the second functional entity unit 802 corresponding to the source link, the target link for sending the data;

[0315] or,

[0316] The first functional entity receives third information sent by the receiving end device; determines the need to select a target link for sending data based on the third information; and the third information includes the target link identifier.

[0317] In actual application, the first functional entity unit 801 and the second functional entity unit 802 can be implemented by a processor in a data transmission device in combination with a communication interface.

[0318] In order to implement the method of the receiving end device side of the embodiment of the present application, the embodiment of the present application also provides a data transmission device, which is set on the receiving end device, such as Figure 9 As shown, the device includes: a first functional entity unit 901 and a second functional entity unit 902; wherein,

[0319] The first functional entity unit 901 and the second functional entity unit 902 are used to receive data packets; the sequence relationship of the data packets includes a first part and a second part; the first part is determined by the first functional entity of the sending device L3; the second part is determined by at least one second functional entity of the sending device L2; the first functional entity is connected to at least one second functional entity.

[0320] In one embodiment, the second functional entity unit 902 is configured to determine the second part of the sequence relationship of the data packet by one of the following methods:

[0321] The second functional entity of L2 of the receiving end device corresponding to the first link receives the second part of the sequence relationship of the data packet;

[0322] The second part of the sequence relationship of the data packet is determined by the sequence of the HARQ process

[0323] In one embodiment, at least two links are used to receive data packets; the first functional entity unit 901 is further configured to receive second information; and the second information represents the data sending order of the at least two links.

[0324] In one embodiment, the first functional entity unit 901 receives the second information, including at least one of the following:

[0325] The first functional entity unit 901 receives a PDU, where the PDU carries the second information;

[0326] The first functional entity unit 901 receives a MAC CE, where the MAC CE carries the second information;

[0327] The first functional entity unit 901 receives DCI; the DCI carries the second information.

[0328] In one embodiment, the second functional entity unit 902 is configured to receive a MAC CE, parse the MAC CE, obtain second information, and send the second information to the first functional entity unit 901 .

[0329] The first functional entity unit 901 selects at least two links for sending data; and sends second information to the sending end device; the second information represents the data sending order of the at least one link.

[0330] In one embodiment, the first functional entity unit 901 is further configured to receive third information; the third information includes a target link identifier; the target link at least represents a connection between the first functional entity and a second functional entity;

[0331] The target link is used to send data packets of the source link; the source link at least represents a connection between a first functional entity and a second functional entity.

[0332] In one embodiment, the first functional entity unit 901 receives third information including at least one of the following:

[0333] The first functional entity unit 901 receives a PDU, where the PDU carries the third information;

[0334] The first functional entity unit 901 of the receiving end device receives a MAC CE, where the MAC CE carries the third information;

[0335] The first functional entity unit 901 of the receiving device receives DCI; the DCI carries the third information.

[0336] In one embodiment, the second functional entity unit 902 corresponding to the source link receives the MAC CE, parses the MAC CE, obtains third information, and sends the third information to the first functional entity unit 901.

[0337] In one embodiment, the first functional entity unit 901 is further configured to send third information; the third information includes a target link identifier; the target link at least represents a connection between the first functional entity and a second functional entity;

[0338] The target link is used to send data packets of the source link; the source link at least represents a connection between a first functional entity and a second functional entity.

[0339] In actual application, the first functional entity unit 901 and the second functional entity unit 902 can be implemented by a processor in a data transmission device in combination with a communication interface.

[0340] It should be noted that the data transmission device provided in the above embodiment is only illustrated by the division of the above-mentioned program modules when performing data transmission. In actual applications, the above-mentioned processing can be assigned to different program modules as needed, that is, the internal structure of the device can be divided into different program modules to complete all or part of the above-mentioned processing. In addition, the data transmission device provided in the above embodiment and the data transmission method embodiment are based on the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.

[0341] Based on the hardware implementation of the above program modules, and in order to implement the method of the transmitting end device side of the embodiment of the present application, the embodiment of the present application also provides a transmitting end device, such as Figure 10 As shown, the sending end device 1000 includes:

[0342] The first communication interface 1001 is capable of exchanging information with a receiving device;

[0343] The first processor 1002 is connected to the first communication interface 1001 to implement information exchange with the receiving device and is used to execute the method provided by one or more technical solutions of the sending device when running a computer program. The computer program is stored in the first memory 1003.

[0344] Specifically, the first communication interface 1001 is used to send data packets; the sequence relationship of the data packets includes a first part and a second part; the first part is determined by the first functional entity of the sending device 1000L3; the second part is determined by at least one second functional entity of the sending device 1000L2; the first functional entity is connected to at least one second functional entity.

[0345] In one embodiment, when sending a data packet, the second functional entity corresponding to the first link is further configured to send the second part of the sequence relationship of the data packet through the first communication interface 1001 .

[0346] In one embodiment, the first functional entity selects at least one link for sending data through the first processor 1002; each link represents at least a connection between the first functional entity and a second functional entity unit 802; and at least one link is used to send data packets.

[0347] In one embodiment, the first functional entity selects at least two links for sending data through the first processor 1002; the first functional entity sends second information through the first communication interface 1001; and the second information represents the data sending order of the at least two links.

[0348] In one embodiment, the first functional entity performs one of the following through the first communication interface 1001:

[0349] The first functional entity sends a PDU through the first communication interface 1001, where the PDU carries the second information;

[0350] The first functional entity sends a MAC CE through the first communication interface 1001, where the MAC CE carries the second information;

[0351] The first functional entity sends DCI through the first communication interface 1001; the DCI carries the second information.

[0352] In one embodiment, the first functional entity sends the second information to the second functional entity; and the second functional entity sends a MAC CE.

[0353] In one embodiment, the first functional entity selects, through the first processor 1002, at least one link for sending data, including one of the following:

[0354] The first functional entity selects at least one link for sending data according to transmission conditions of air interface data of at least two second functional entities;

[0355] The first functional entity selects at least one link for sending data according to the amount of data requested by the at least two second functional entities;

[0356] The first functional entity receives second information sent by a receiving device through the first communication interface 1001; selects at least one link for sending data according to the second information; and the second information represents a data sending order of the at least one link.

[0357] In one embodiment, the first functional entity selects a target link for sending data through the first processor 1002; the target link at least represents a connection between the first functional entity and a second functional entity;

[0358] A data packet of a source link is sent on a target link; the source link at least represents a connection between the first functional entity and a second functional entity.

[0359] In one embodiment, the first functional entity sends third information through the first communication interface 1001; the third information includes the target link identifier.

[0360] In one embodiment, the first functional entity sends the third information through the first communication interface 1001, including one of the following:

[0361] The first functional entity sends a PDU, where the PDU carries the third information;

[0362] The first functional entity sends a MAC CE, where the MAC CE carries the third information;

[0363] The first functional entity sends DCI; the DCI carries the third information.

[0364] In one embodiment, the first functional entity sends the third information to the second functional entity corresponding to the source link; and the second functional entity corresponding to the source link sends the MAC CE.

[0365] In one embodiment, the first functional entity determines, through the first processor 1002, based on transmission parameters of the second functional entity air interface data corresponding to the source link, that a target link for sending data needs to be selected;

[0366] or,

[0367] The first functional entity receives third information sent by the receiving device through the first communication interface 1001; determines through the first processor 1002 that a target link for sending data needs to be selected based on the third information; the third information includes the target link identifier.

[0368] It should be noted that the specific processing process of the first processor 1002 and the first communication interface 1001 can be understood by referring to the above method.

[0369] Of course, in actual application, the various components in the transmitting end device 1000 are coupled together through the bus system 1004. It can be understood that the bus system 1004 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 1004 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, Figure 10 Various buses are labeled as bus system 1004.

[0370] The first memory 1003 in the embodiment of the present application is used to store various types of data to support the operation of the sending end device 1000. Examples of such data include: any computer program used to operate on the sending end device 1000.

[0371] The methods disclosed in the above embodiments of the present application can be applied to the first processor 1002 or implemented by the first processor 1002. The first processor 1002 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by an integrated logic circuit of the hardware in the first processor 1002 or by instructions in the form of software. The above first processor 1002 may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The first processor 1002 can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium located in the first memory 1003. The first processor 1002 reads the information in the first memory 1003 and completes the steps of the above method in combination with its hardware.

[0372] In an exemplary embodiment, the sending device 1000 can be implemented by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers (MCUs), microprocessors, or other electronic components to execute the aforementioned method.

[0373] Based on the hardware implementation of the above program modules, and in order to implement the method of the receiving end device side of the embodiment of the present application, the embodiment of the present application also provides a receiving end device, such as Figure 11 As shown, the receiving end device 1100 includes:

[0374] The second communication interface 1101 is capable of exchanging information with the sending end device;

[0375] The second processor 1102 is connected to the second communication interface 1101 to implement information exchange with the sending end device and is used to execute the method provided by one or more technical solutions on the receiving end device when running the computer program. The computer program is stored in the second memory 1103.

[0376] Specifically, the second communication interface 1101 is used to receive data packets; the sequence relationship of the data packets includes a first part and a second part; the first part is determined by the first functional entity of the sending device L3; the second part is determined by at least one second functional entity of the sending device L2; the first functional entity is connected to at least one second functional entity.

[0377] In one embodiment, the second processor 1102 is configured to determine the second part of the sequence relationship of the data packets by one of the following methods:

[0378] The second functional entity of L2 of the receiving end device 1100 corresponding to the first link receives the second part of the sequence relationship of the data packet;

[0379] The second part of the sequence relationship of the data packets is determined by the sequence of the HARQ processes.

[0380] In one embodiment, data packets are received using at least two links; the first functional entity of the receiving device 1100 receives second information through the second communication interface 1101; and the second information represents the data sending order of the at least two links.

[0381] In one embodiment, the first functional entity of the receiving end device 1100 receives the second information through the second communication interface 1101, including at least one of the following:

[0382] The first functional entity of the receiving device 1100 receives a PDU, where the PDU carries the second information;

[0383] The first functional entity of the receiving end device 1100 receives a MAC CE, where the MAC CE carries the second information;

[0384] The first functional entity of the receiving device 1100 receives DCI; the DCI carries the second information.

[0385] In one embodiment, the second functional entity of the receiving device 1100 receives the MAC CE through the second communication interface 1101, parses the MAC CE, obtains second information, and sends the second information to the first functional entity of the receiving device 1100.

[0386] The first functional entity of the receiving device 1100 selects at least two links for sending data through the second processor 1102; and sends second information to the sending device through the second communication interface 1101; the second information represents the data sending order of the at least one link.

[0387] In one embodiment, the first functional entity of the receiving end device 1100 receives third information through the second communication interface 1101; the third information includes a target link identifier; the target link at least represents a connection between the first functional entity and a second functional entity;

[0388] The target link is used to send data packets of the source link; the source link at least represents a connection between a first functional entity and a second functional entity.

[0389] In one embodiment, the first functional entity of the receiving device 1100 receives the third information through the second communication interface 1101, including at least one of the following:

[0390] The first functional entity of the receiving end device 1100 receives a PDU, where the PDU carries the third information;

[0391] The first functional entity of the receiving end device receives a MAC CE, where the MAC CE carries the third information;

[0392] The first functional entity of the receiving device receives DCI; the DCI carries the third information.

[0393] In one embodiment, the second functional entity of the receiving device 1100 corresponding to the source link receives the MAC CE, parses the MAC CE, obtains the third information, and sends the third information to the first functional entity of the receiving device 1100.

[0394] In one embodiment, the first functional entity of the receiving end device 1100 sends third information through the second communication interface 1101; the third information includes a target link identifier; the target link at least represents a connection between the first functional entity and a second functional entity;

[0395] The target link is used to send data packets of the source link; the source link at least represents a connection between a first functional entity and a second functional entity.

[0396] It should be noted that the specific processing procedures of the second communication interface 1101 and the second processor 1102 can be understood by referring to the above method.

[0397] Of course, in actual application, the various components in the receiving end device 1100 are coupled together through the bus system 1104. It can be understood that the bus system 1104 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 1104 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, Figure 11 Various buses are labeled as bus system 1104.

[0398] The second memory 1103 in the embodiment of the present application is used to store various types of data to support the operation of the receiving device 1100. Examples of such data include: any computer program used to operate on the receiving device 1100.

[0399] The methods disclosed in the above embodiments of the present application can be applied to or implemented by the second processor 1102. The second processor 1102 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by hardware integrated logic circuits or software instructions in the second processor 1102. The above second processor 1102 may be a general-purpose processor, a DSP, or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, etc. The second processor 1102 can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of the present application can be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium located in the second memory 1103. The second processor 1102 reads the information in the second memory 1103 and, in conjunction with its hardware, completes the steps of the above method.

[0400] In an exemplary embodiment, the receiving device 1100 may be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general-purpose processors, controllers, MCUs, Microprocessors, or other electronic components to perform the aforementioned method.

[0401] It can be understood that the memory (first memory 1003, second memory 1103) of the embodiment of the present application can be a volatile memory or a non-volatile memory, and can also include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic random access memory (FRAM), a flash memory, a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM); the magnetic surface memory can be a magnetic disk memory or a tape memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), synchronous static random access memory (SSRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus random access memory (DRRAM).The memories described in the embodiments of this application are intended to include, but are not limited to, these and any other suitable types of memories.

[0402] In order to implement the method provided in the embodiment of the present application, the embodiment of the present application also provides a data transmission system, such as Figure 12 As shown, the system includes: a sending end device 1201 and a receiving end device 1202.

[0403] Here, it should be noted that the specific processing procedures of the transmitting device 1201 and the receiving device 1202 have been described in detail above and will not be repeated here.

[0404] In an exemplary embodiment, the present application also provides a storage medium, namely a computer storage medium, specifically a computer-readable storage medium, which includes, for example, a first memory 1003 storing a computer program. The computer program can be executed by the first processor 1002 of the transmitting device 1000 to complete the steps of the aforementioned transmitting device-side method. For another example, the present application also includes a second memory 1103 storing a computer program. The computer program can be executed by the second processor 1102 of the receiving device 1100 to complete the steps of the aforementioned receiving device-side method. The computer-readable storage medium can be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface storage, optical disk, or CD-ROM.

[0405] It should be noted that: "first", "second", etc. are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0406] In addition, the technical solutions described in the embodiments of the present application can be arbitrarily combined without conflict.

[0407] The above description is merely a preferred embodiment of the present application and is not intended to limit the scope of protection of the present application.

Claims

1. A data transmission method, characterized in that: Applicable to the sending end device, including: Sending a data packet; the sequence relationship of the data packet includes a first part and a second part; the first part is determined by a first functional entity of layer 3 of the transmitting end device; the second part is determined by at least one second functional entity of layer 2 of the transmitting end device; the first functional entity is connected to at least one second functional entity; wherein, The first part includes a first link identifier for transmitting the data packet; the first link at least represents a connection between the first functional entity and a second functional entity; and / or the second part contains first information; the first information represents the transmission order of the data packet on the corresponding second functional entity.

2. The method according to claim 1, characterized in that When sending the data packet, the method further includes: The second functional entity corresponding to the first link sends the second part of the sequential relationship of the data packet.

3. The method according to claim 1, characterized in that The first link identifier includes one of the following: Corresponding second functional entity identifier; First link index.

4. The method according to claim 1, wherein The first portion identifies one or more consecutive data packets transmitted on the first link.

5. The method according to claim 1, characterized in that The determination includes at least one of the following: Generation and / or resetting of data packet sequence numbers; Selection of the initial value of the data packet sequence number; Increment or decrement of packet sequence numbers; The use of packet sequence numbers in packet sorting; The sequence number of the data packet identifies a second functional entity.

6. The method according to any one of claims 1 to 5, characterized in that The first functional entity selects at least one link for sending data; each link represents at least a connection between the first functional entity and a second functional entity; Use at least one link to send data packets.

7. The method according to claim 6, characterized in that The first functional entity selects at least two links for sending data; and the method further comprises: The first functional entity sends second information; the second information represents the data sending order of the at least two links.

8. The method according to claim 7, characterized in that The first functional entity sends the second information, including one of the following: The first functional entity sends a protocol data unit PDU, where the PDU carries the second information; The first functional entity sends a media access control control element MAC CE, where the MAC CE carries the second information; The first functional entity sends downlink control information DCI; the DCI carries the second information; The first functional entity sends uplink control information UCI; the UCI carries the second information.

9. The method according to claim 8, characterized in that The first functional entity sends second information to the second functional entity; and the second functional entity sends a MAC CE.

10. The method according to claim 7, characterized in that The link identifier of the link in the last sending order adjacent to the second link in the at least two links is sent through the second link in the at least two links, or the link identifier of the link in the next sending order adjacent to the second link in the at least two links is sent.

11. The method according to claim 6, characterized in that The first functional entity selects at least one link for sending data, including one of the following: The first functional entity selects at least one link for sending data according to transmission conditions of air interface data of at least two second functional entities; The first functional entity selects at least one link for sending data according to the amount of data requested by the at least two second functional entities; The first functional entity receives second information sent by the receiving end device; At least one link for sending data is selected according to the second information; the second information represents the data sending order of the at least one link.

12. The method according to any one of claims 1 to 5, characterized in that The first functional entity selects a target link for sending data; the target link at least represents a connection between the first functional entity and a second functional entity; A data packet of a source link is sent on a target link; the source link at least represents a connection between the first functional entity and a second functional entity.

13. The method according to claim 12, characterized in that The method further comprises: The first functional entity sends third information; the third information includes the target link identifier.

14. The method according to claim 13, characterized in that The first functional entity sends third information, including one of the following: The first functional entity sends a PDU, where the PDU carries the third information; The first functional entity sends a MAC CE, where the MAC CE carries the third information; The first functional entity sends DCI; The DCI carries the third information; The first functional entity sends UCI; the UCI carries the third information.

15. The method according to claim 14, characterized in that The first functional entity sends third information to the second functional entity corresponding to the source link; and the second functional entity corresponding to the source link sends the MAC CE.

16. The method according to claim 12, characterized in that The first functional entity determines, based on the transmission parameters of the air interface data of the second functional entity corresponding to the source link, a target link for sending data; or, The first functional entity receives third information sent by the receiving end device; determines the need to select a target link for sending data based on the third information; and the third information includes the target link identifier.

17. A data transmission method, characterized in that: Applicable to receiving devices, including: Receive a data packet; the sequence relationship of the data packet includes a first part and a second part; the first part is determined by a first functional entity at layer 3 of the transmitting end device; the second part is determined by at least one second functional entity at layer 2 of the transmitting end device; the first functional entity is connected to at least one second functional entity; wherein, The first part includes a first link identifier for transmitting the data packet; the first link at least represents a connection between the first functional entity and a second functional entity; and / or the second part contains first information; the first information represents the transmission order of the data packet on the corresponding second functional entity.

18. The method according to claim 17, characterized in that The second part of the sequence relationship of the data packets is determined by one of the following methods: The second functional entity of the layer 2 of the receiving end device corresponding to the first link receives the second part of the sequence relationship of the data packet; The second part of the sequence relationship of the data packets is determined according to the sequence of the HARQ processes of the received data packets.

19. The method according to claim 17, wherein The first link identifier includes one of the following: The second functional entity identifier of the corresponding sending end device; First link index.

20. The method according to claim 17, wherein The first portion identifies one or more consecutive data packets transmitted on the first link.

21. The method according to any one of claims 17 to 20, characterized in that At least one link is used to receive a data packet; each link at least represents a connection between a first functional entity of layer three of the receiving end device and a second functional entity of layer two of the receiving end device.

22. The method according to claim 21, characterized in that Receiving data packets using at least two links; the method further comprising: The first functional entity of the receiving end device receives second information; the second information represents the data sending order of the at least two links.

23. The method according to claim 22, characterized in that The first functional entity of the receiving end device receives the second information, including at least one of the following: The first functional entity of the receiving end device receives a PDU, where the PDU carries the second information; The first functional entity of the receiving end device receives a MAC CE, where the MAC CE carries the second information; The first functional entity of the receiving end device receives the DCI; The DCI carries the second information; The first functional entity of the receiving end device receives UCI; The UCI carries the second information.

24. The method according to claim 23, wherein The second functional entity of the receiving end device receives the MAC CE, parses the MAC CE, obtains second information, and sends the second information to the first functional entity of the receiving end device.

25. The method according to claim 24, characterized in that The link identifier of the link in the last transmission sequence adjacent to the second link in the at least two links is received through the second link in the at least two links, or the link identifier of the link in the next transmission sequence adjacent to the second link in the at least two links is received.

26. The method according to claim 21, characterized in that The first functional entity of the receiving end device selects at least two links for sending data; and sends second information to the sending end device; the second information represents the data sending order of the at least one link.

27. The method according to any one of claims 17 to 20, characterized in that The method further comprises: The first functional entity of the receiving end device receives third information; the third information includes a target link identifier; the target link at least represents a connection between the first functional entity and a second functional entity; The target link is used to send data packets of the source link; the source link at least represents a connection between a first functional entity and a second functional entity.

28. The method according to claim 27, characterized in that The first functional entity of the receiving end device receives third information, including at least one of the following: The first functional entity of the receiving end device receives a PDU, where the PDU carries the third information; The first functional entity of the receiving end device receives a MAC CE, where the MAC CE carries the third information; The first functional entity of the receiving end device receives the DCI; The DCI carries the third information; The first functional entity of the receiving end device receives UCI; The UCI carries the third information.

29. The method according to claim 28, characterized in that The second functional entity of the receiving end device corresponding to the source link receives the MAC CE, parses the MAC CE, obtains third information, and sends the third information to the first functional entity of the receiving end device.

30. The method according to any one of claims 17 to 20, characterized in that The method further comprises: The first functional entity of the receiving end device sends third information; the third information includes a target link identifier; the target link at least represents a connection between the first functional entity and a second functional entity; The target link is used to send data packets of the source link; the source link at least represents a connection between a first functional entity and a second functional entity.

31. A data transmission device, characterized in that: Set on the sending end device, including: a first functional entity unit and a second functional entity unit; wherein, The first functional entity unit and the second functional entity unit are used to send a data packet; the sequence relationship of the data packet includes a first part and a second part; the first part is determined by the first functional entity unit of the third layer of the transmitting end device; the second part is determined by at least one second functional entity unit of the second layer of the transmitting end device; the first functional entity unit is connected to at least one second functional entity unit; wherein, The first part includes a first link identifier for transmitting the data packet; the first link at least represents a connection between the first functional entity and a second functional entity; and / or the second part contains first information; the first information represents the transmission order of the data packet on the corresponding second functional entity.

32. A data transmission device, characterized in that: Set on the receiving end device, including: a first functional entity unit and a second functional entity unit; wherein, The first functional entity unit and the second functional entity unit are used to receive a data packet; the sequence relationship of the data packet includes a first part and a second part; the first part is determined by a first functional entity at layer 3 of the transmitting end device; the second part is determined by at least one second functional entity at layer 2 of the transmitting end device; the first functional entity is connected to at least one second functional entity; wherein, The first part includes a first link identifier for transmitting the data packet; the first link at least represents a connection between the first functional entity and a second functional entity; and / or the second part contains first information; the first information represents the transmission order of the data packet on the corresponding second functional entity.

33. A transmitting end device, characterized in that: include: A first communication interface and a first processor; wherein, The first communication interface is used to send a data packet; the sequence relationship of the data packet includes a first part and a second part; the first part is determined by a first functional entity at layer 3 of the transmitting end device; the second part is determined by at least one second functional entity at layer 2 of the transmitting end device; the first functional entity is connected to at least one second functional entity; wherein, The first part includes a first link identifier for transmitting the data packet; the first link at least represents a connection between the first functional entity and a second functional entity; and / or the second part contains first information; the first information represents the transmission order of the data packet on the corresponding second functional entity.

34. A receiving device, characterized in that: include: A second communication interface and a second processor; wherein, The second communication interface is used to receive a data packet; the sequence relationship of the data packet includes a first part and a second part; the first part is determined by a first functional entity at layer 3 of the transmitting end device; the second part is determined by at least one second functional entity at layer 2 of the transmitting end device; the first functional entity is connected to at least one second functional entity; wherein, The first part includes a first link identifier for transmitting the data packet; the first link at least represents a connection between the first functional entity and a second functional entity; and / or the second part contains first information; the first information represents the transmission order of the data packet on the corresponding second functional entity.

35. A transmitting end device, characterized in that: include: a first processor and a first memory for storing a computer program capable of being executed on the processor, Wherein, when the first processor is used to run the computer program, it executes the steps of the method according to any one of claims 1 to 16.

36. A receiving device, characterized in that: include: a second processor and a second memory for storing a computer program capable of being executed on the processor, Wherein, when the second processor is used to run the computer program, it executes the steps of the method according to any one of claims 17 to 30.

37. A storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the computer program implements the steps of the method according to any one of claims 1 to 16, or the steps of the method according to any one of claims 17 to 30.

Images