CN115843064A

CN115843064A - Data transmission method, communication device, chip and module equipment thereof

Info

Publication number: CN115843064A
Application number: CN202111103444.4A
Authority: CN
Inventors: 徐敏
Original assignee: Spreadtrum Communications Shanghai Co Ltd
Current assignee: Spreadtrum Communications Shanghai Co Ltd
Priority date: 2021-09-18
Filing date: 2021-09-18
Publication date: 2023-03-24
Also published as: WO2023040126A1

Abstract

The application discloses a data transmission method, a communication device, a chip and module equipment thereof. The method comprises the following steps: adding a bearing identifier and a first sequence number to the first data packet to obtain a second data packet; the bearer identifier is used for indicating a radio bearer of the first data packet, and the first sequence number is used for representing a sending sequence of the first data packet; and sending the second data packet to the first access equipment. By implementing the method provided by the embodiment of the application, the second data packet added with the bearer identifier and the first sequence number can be sent to the first access device, so that the reliable transmission of data is ensured.

Description

Data transmission method, communication device, chip and module equipment thereof

Technical Field

The present application relates to the field of communications technologies, and in particular, to a data transmission method, a communication device, a chip, and a module device thereof.

Background

With the development of terminal devices, the terminal devices may connect access network devices of different access technologies simultaneously, such as: the terminal device may access a Premise Radio Access Station (PRAS) and a wireless access point (WiFi AP) at the same time, and perform data transmission. Due to the adoption of different access technologies, data of different links cannot be sequenced and combined.

Meanwhile, in next generation radio (NR) communication, the requirements of high-reliability and Low-Latency Communications (URLLC) on Latency and reliability are met by introducing duplicate transmission. Specifically, duplicate transmission refers to the transmission of the same data packet over two links. In the prior art, communications based on the two links for duplicate transmission are both NR communications. However, the terminal device can currently support Wireless Local Area Network (WLAN) communication and cellular communication, and therefore, in the case that communication based on two links for duplicate transmission is cellular communication and WLAN communication, research on how to implement packet transmission has important practical value for improving communication performance.

Disclosure of Invention

The application discloses a data transmission method, a communication device, a chip and module equipment thereof, which are beneficial to ensuring reliable data transmission by sending a second data packet added with a bearing identifier and a first serial number to first access equipment.

In a first aspect, the present application provides a data transmission method, including: adding a bearing identifier and a first sequence number to the first data packet to obtain a second data packet; the bearer identifier is used for indicating a radio bearer of the first data packet, and the first sequence number is used for representing the sending sequence of the first data packet; and sending the second data packet to the first access equipment.

In one implementation, the first data packet is sent to a second access device.

In one implementation, the first packet includes a quality of service flow identifier QFI; and determining the bearing identification according to the QFI.

In one implementation, the first sequence number is the same as the second sequence number, or the first sequence number is different from the second sequence number; the second sequence number is a sequence number added to the first data packet by the second access device, and the second sequence number is used for representing a sending sequence of the first data packet.

In one implementation, the first sequence number is a PDCP sequence number of the first packet, and the first sequence number is used to characterize a transmission order of the first packet in the PDCP layer.

In one implementation, an initial PDCP sequence number is obtained, and an offset between the first sequence number and the second sequence number is the initial PDCP sequence number.

In one implementation, indication information is received from a second access device, the indication information indicating that duplicate delivery transmission is initiated.

In one implementation, the first packet is received.

In one implementation, a first message is sent to the second access device, where the first message is used to indicate that the second data packet is successfully sent.

In one implementation, the first message includes a bearer identifier and a first sequence number.

In one implementation, the first access device is a device supporting wireless local area network WLAN communication, and the second access device is a device supporting cellular communication.

In one implementation, the first access device is a wireless access point WiFi AP, and the second access device is a residential radio access station PRAS.

In a second aspect, the present application provides a data transmission method, including: receiving a second data packet from the first access device, wherein the second data packet comprises a bearing identification, a first sequence number and a first data packet; the bearer identifier is used for indicating a radio bearer of the first data packet, and the first sequence number is used for representing the sending sequence of the first data packet; and determining the sending sequence of the first data packet according to the bearing identification and the first sequence number.

In one implementation, the first packet includes a quality of service flow identifier QFI, and the bearer identifier is determined according to the QFI.

In one implementation, the first sequence number is the same as the second sequence number, or the first sequence number is different from the second sequence number; the second sequence number is a sequence number added by the second access device to the first data packet, and the second sequence number is used for representing a transmission sequence of the first data packet.

In one implementation, a second message is sent to the second access device, where the second message is used to indicate that the second data packet is successfully received.

In one implementation, the second message includes a bearer identifier and a first sequence number.

In a third aspect, the present application provides a communication device comprising means for implementing the method of the first aspect and any of its possible implementations, or comprising means for implementing the method of the second aspect and any of its possible implementations.

In a fourth aspect, the present application provides a communication device comprising a processor configured to perform the method of the first aspect and any of its possible implementations or to implement the method of the second aspect and any of its possible implementations.

In a fifth aspect, the present application provides a communication device comprising a processor and a memory for storing computer-executable instructions; the processor is configured to invoke the program code from the memory to perform the method of the first aspect and any of its possible implementations, or to implement the method of the second aspect and any of its possible implementations.

In a sixth aspect, the present application provides a chip, where the chip is configured to add a bearer identifier and a first sequence number to a first data packet to obtain a second data packet; the bearer identifier is used for indicating a radio bearer of the first data packet, and the first sequence number is used for representing a sending sequence of the first data packet; and sending the second data packet to the first access equipment.

In a seventh aspect, the present application provides another chip, where the chip is configured to receive a second data packet from a first access device, where the second data packet includes a bearer identifier, a first sequence number, and a first data packet; the bearer identifier is used for indicating a radio bearer of the first data packet, and the first sequence number is used for representing the sending sequence of the first data packet; and determining the sending sequence of the first data packet according to the bearing identification and the first sequence number.

In an eighth aspect, the present application provides a module device, which includes a communication module, a power module, a storage module, and a chip module, wherein: the power module is used for providing electric energy for the module equipment; the storage module is used for storing data and instructions; the communication module is used for carrying out internal communication of the module equipment or is used for carrying out communication between the module equipment and external equipment; this chip module is used for: adding a bearing identifier and a first sequence number to the first data packet to obtain a second data packet; the bearer identifier is used for indicating a radio bearer of the first data packet, and the first sequence number is used for representing the sending sequence of the first data packet; and sending the second data packet to the first access equipment.

In a ninth aspect, the present application provides another module device, which includes a communication module, a power module, a storage module, and a chip module, wherein: the power module is used for providing electric energy for the module equipment; the storage module is used for storing data and instructions; the communication module is used for carrying out internal communication of the module equipment or is used for carrying out communication between the module equipment and external equipment; this chip module is used for: receiving a second data packet from the first access device, wherein the second data packet comprises a bearing identification, a first sequence number and a first data packet; the bearer identifier is used for indicating a radio bearer of the first data packet, and the first sequence number is used for representing the sending sequence of the first data packet; and determining the sending sequence of the first data packet according to the bearing identification and the first sequence number.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is an architecture diagram of a communication system according to an embodiment of the present application;

fig. 2 is a flowchart of a data transmission method according to an embodiment of the present application;

fig. 3 is a flowchart of a data transmission method according to an embodiment of the present application;

fig. 4 is a flowchart of a data transmission method according to an embodiment of the present application;

fig. 5 is a flowchart of a data transmission method according to an embodiment of the present application

Fig. 6 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of another communication device according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of a module apparatus according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

For ease of understanding, terms referred to in the present application will be first introduced.

1、PRAS

PRAS is an access point in a Customer Premises Network (CPN). The PRAS may be deployed in a licensed spectrum or an unlicensed spectrum. In CPN, terminal devices may access the network through PRAS. The terminal device and the PRAS may be connected by a Long Term Evolution (LTE) technology or an NR technology. The CPN may further include a WiFi AP, and the terminal device may also access the network through the WiFi AP. In the CPN, there may be multiple access points, where there may be one or more PRAS and one or more WiFi APs. It should be noted that the PRAS and the WiFi AP may communicate with the network through an Evolved home Gateway (edrg) in the CPN.

2. Data transmission for cellular communication link

Links based on PRAS transmissions, such as the communication links between the eRG and the PRAS and between the PRAS and the terminal device, may be referred to as cellular communication links. Among them, a Packet Data Convergence Protocol (PDCP) layer may exist in the PRAS. When the eRG is switched among different PRASs and data is transmitted, the data packets can be sequenced and combined through the PDCP serial numbers in the PRASs, so that the switching of the eRG among the PRASs can be realized, and the uninterrupted data transmission is ensured.

3. Data transmission of a WLAN link

Links based on WiFi AP transmissions, such as communication links between the errg and the WiFi AP and between the WiFi AP and the terminal device, may be referred to as WLAN communication links. It should be noted that, the protocol stack of the Wifi AP is different from that in the cellular system, and the Wifi AP does not have a PDCP layer, i.e. a PDCP sequence number.

In the LTE system, data transmission through the WLAN communication link in the LTE system may be implemented by an LTE-WLAN Aggregation (LWA) technology. For an access point using LWA technology, such as an LTE base station, a packet processed by the PDCP layer may be added with a DRB ID by using LWAApplication Protocol (LWAAP, LWA application Protocol), and the processed packet may be transmitted over a WLAN link through a new interface (Xw interface) to a Wifi AP. After receiving the data packet of the WLAN link, the terminal device may determine the PDCP entity corresponding to the data packet by using the DRB ID carried in the header of the LWAAP layer, and merge the data packet by using the PDCP sequence number in the PDCP layer. Wherein, the base station can place the data packet to the corresponding PDCP entity, and the data packet can add PDCP sequence number in the PDCP entity for characterizing the sequence of the PDCP layer.

In the NR system, a Service Data Adaptation Protocol (SDAP) layer is added above the PDCP layer. The SDAP may implement a function of mapping quality of service flow (Qos flow) to Radio Bearer (RB), and may add information such as Qos Flow Identifier (QFI) to the header. However, the PDCP layer in the CPN network is generally located in the PRAS, and if LWA needs to be implemented, the errg receives a data packet to be sent and forwards the data packet to the PRAS first, and then the PRAS needs to forward the processed data packet to the wifi AP through the errg each time. By this way, the time delay is increased, and the reliability of WLAN link data transmission cannot be guaranteed.

In view of this, the data transmission method provided in the embodiment of the present application is favorable to ensure sequential and reliable transmission of data by sending the second data packet to which the bearer identifier and the first sequence number are added to the WLAN link.

Referring to fig. 1, fig. 1 is an architecture diagram of a communication system according to an embodiment of the present disclosure. As shown in fig. 1, the communication system may include a terminal device 101, a first access device 102, a second access device 103, and a gateway device 104. In this embodiment, the terminal device 101 may access the first access device 102 and the second access device 103 at the same time, and the first access device 102 and the second access device 103 may communicate with the network through the gateway device 104.

In one implementation, the first access device 102 may be a Wireless Local Area Network (WLAN) enabled device and the second access device 103 may be a cellular enabled device. Specifically, the first access device 102 may be a WiFi AP, and the second access device 103 may be a PRAS. It should be noted that the PRAS and the WiFi AP may be access points in the CPN. In the embodiment of the present application, the following description uses the first access device 102 as a WiFi AP, the second access device 103 as a PRAS, and the gateway device 104 as an errg, which are not limited to the present application. Optionally, the first access device 102 may also be a PRAS, and the second access device 103 may also be a WiFi AP, which is not limited in this application.

The terminal device 101 and the second access device 103 may be connected through an LTE technology or an NR technology, which is not limited in this application. Optionally, the numbers of the terminal device 101, the first access device 102, the second access device 103, and the gateway device 104 shown in fig. 1 are only for example and do not limit the present application.

In this embodiment of the present application, when the second access device 103 accessed by the terminal device 101 finds that the current network is poor or the service reliability requirement is high, the second access device 103 may start duplicate transmission. In downlink, when the gateway device 104 receives the instruction to start the duplicate transmission, after receiving the first downlink packet, the gateway device 104 may add the first bearer identifier and the first sequence number to the first downlink packet to obtain a second downlink packet, and send the second downlink packet to the first access device 102. Optionally, after receiving the first downlink data packet, the gateway device 104 may further send the first downlink data packet to the second access device 103.

Optionally, after receiving the second downlink data packet from the gateway device 104, the first access device 102 may further send the second downlink data packet to the terminal device 101. Correspondingly, the terminal device 101 may receive the second downlink data packet through the first access device 102, and determine the sending sequence of the first downlink data packet through the first bearer identifier and the first sequence number in the second downlink data packet, so as to sequence and combine the first downlink data packet according to the sending sequence, thereby being beneficial to ensuring reliable transmission of downlink data.

In the uplink, when the terminal device 101 receives the instruction to start the duplicate transmission, the terminal device 101 may add the second bearer identifier and the third sequence number to the first uplink data packet to obtain a second uplink data packet, and send the second uplink data packet to the first access device 102. Optionally, the terminal device 101 may further send the first uplink data packet to the second access device 103. Wherein the first uplink data packet may be generated by the terminal device 101.

Optionally, after receiving the second uplink data packet from the terminal device 101, the first access device 102 may further send the second uplink data packet to the gateway device 104. Accordingly, the gateway device 104 may receive the second uplink data packet from the first access device 102, and determine the sending sequence of the first uplink data packet through the second bearer identifier and the third sequence number in the second uplink data packet, so as to sequence and combine the first uplink data packet according to the sending sequence, thereby being beneficial to ensuring reliable transmission of uplink data.

In the embodiment of the present application, a communication link from a network to a terminal device is a downlink, data transmitted on the downlink is referred to as downlink data, and a transmission direction of the downlink data is referred to as a downlink direction; and the communication link from the terminal device to the network is an uplink, the data transmitted on the uplink is referred to as uplink data, and the transmission direction of the uplink data is referred to as an uplink direction.

The terminal device 101 is an entity, such as a mobile phone, on the user side for receiving or transmitting signals. A terminal device may also be referred to as a terminal (terminal), a User Equipment (UE), a Mobile Station (MS), a Mobile Terminal (MT), etc. The terminal device may be a mobile phone (mobile phone), a wearable device, a tablet (Pad), a computer with wireless transceiving function, a Virtual Reality (VR) terminal device, an Augmented Reality (AR) terminal device, a wireless terminal in industrial control (industrial control), a wireless terminal in self-driving (self-driving), a wireless terminal in remote surgery (remote surgery), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation safety (transportation safety), a wireless terminal in city (city), a wireless terminal in smart home (smart home), a device for supporting enhanced Machine-Type communication (eMTC), and/or a Long Term Evolution (LTE) terminal supporting universal mobile communication technology, and so on. The embodiment of the present application does not limit the specific technology and the specific device form adopted by the terminal device.

The access devices (such as the first access device 102, the second access device 103, and the gateway device 104) may include indoor access devices, such as Customer Premises Network (CPN) devices, or access nodes (APs) in a wireless fidelity (WiFi) system. The CPN device may include a Premise Radio Access Station (PRAS) and an Evolved home Gateway (edrg). Optionally, the access device may also be an evolved NodeB (eNB), a transmission point (TRP), a next generation base station (next generation NodeB, gNB) in an NR system, or a base station in another future mobile communication system. The embodiments of the present application do not limit the specific technologies and the specific device forms used by the network devices.

It should be noted that the wireless communication systems to which the technical solutions of the embodiments of the present application can be applied include, but are not limited to: a narrowband Band-internet of Things (NB-IoT) system, a Wideband Code Division Multiple Access (WCDMA) system, a Code Division Multiple Access (CDMA 2000) system, a Time Division-Synchronous Code Division Multiple Access (TD-SCDMA) system, a Long Term Evolution (LTE) system, a fifth generation (5 th generation, 5G) mobile communication system, a 5G New Radio (NR) system, a vehicle-mounted wireless short-range communication system, and the like. Optionally, the method of the embodiment of the present application is also applicable to various future wireless communication systems, for example: sixth generation, seventh generation, and other future mobile communication systems, and the like.

The technical solution of the present invention is also applicable to different network architectures, including but not limited to a relay network architecture, a dual link architecture, a Vehicle-to-any-object communication (Vehicle-to-any) architecture, and the like.

The term "connect" in the embodiments of the present application refers to various connection manners, such as direct connection or indirect connection, to implement communication between devices, which is not limited in this embodiment of the present application.

It should be understood that the term "and/or" herein is only one kind of association relationship describing the association object, and means that there may be three kinds of relationships, for example, a and/or B, and may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" in this document indicates that the former and latter related objects are in an "or" relationship. The "plurality" appearing in the embodiments of the present application means two or more. The descriptions of the first, second, etc. appearing in the embodiments of the present application are only for illustrating and differentiating the objects, and do not represent the order or the particular limitation of the number of the devices in the embodiments of the present application, and do not constitute any limitation to the embodiments of the present application.

Referring to fig. 2, fig. 2 is a flowchart of a data transmission method according to an embodiment of the present application. The method mainly describes data transmission on the downlink. The data transmission method may be implemented by the terminal device, the first access device, the second access device, and the gateway device, or may be implemented by a chip in the terminal device, a chip in the first access device, a chip in the second access device, and a chip in the gateway device. In the embodiments corresponding to fig. 2 and fig. 3, the above-mentioned "first data packet" may be named as "first downlink data packet" so as to distinguish from the "first uplink data packet" in the uplink in the embodiments corresponding to fig. 4 and fig. 5. As shown in fig. 2, the data transmission method includes, but is not limited to, the following steps S201 to S204.

Optionally, in step S201, the gateway device receives a first downlink data packet from the network. The first downlink data packet may be a downlink data packet to be transmitted to the terminal device. Specifically, the first downlink data packet may be sent by an access network device or a core network device in the network.

In the downlink, the gateway device may connect to a network and receive a downlink data packet to be transmitted from the network to transmit the downlink data packet to other access devices. As can be seen from the foregoing, the gateway device may be an egrg, and the egrg may be connected to a network to receive downstream packets from the network. It should be noted that the first downlink data packet may be any one of downlink data packets to be transmitted from a network, and this application is not limited to this.

Step S202, the gateway equipment adds a first bearing identifier and a first serial number to the first downlink data packet to obtain a second downlink data packet; the first bearer identification is used for indicating a radio bearer of the first downlink data packet, and the first sequence number is used for representing a sending sequence of the first downlink data packet. The first bearer identifier and the first sequence number are added to the first downlink data packet in the downlink.

In the embodiment of the present application, an adaptation (Adapter) layer may be introduced, and the Adapter layer may be used to add a bearer identifier and a sequence number to a first data packet (e.g., a first downlink data packet, or a first uplink data packet mentioned below). It should be noted that both the sender (e.g., gateway device in downlink) and the receiver (e.g., terminal device in downlink) can introduce the Adapter layer. By introducing the Adapter layer into the receiving end, the receiving end can process the information added by the sending end through the Adapter layer. For example, if the terminal device receives a second downlink data packet to which the gateway device adds the first bearer identifier and the first sequence number through the Adapter layer, the terminal device may strip the first bearer identifier and the first sequence number in the second downlink data packet through the Adapter layer of the terminal device, so as to process the first bearer identifier and the first sequence number.

It should be noted that, after receiving the first downlink packet, the gateway device may perform some processing on the first downlink packet through the Adapter layer, for example, add the first bearer identifier and the first sequence number to the first downlink packet. The adding of the first bearer identifier and the first sequence number to the first downlink data packet may be understood as adding the first bearer identifier and the first sequence number to a packet header of the first downlink data packet, or adding the first bearer identifier and the first sequence number to a load (payload) of the first downlink data packet, which is not limited in this application.

In one implementation, the first downlink packet may include a quality of service flow identifier QFI; the gateway device may determine the first bearer identity according to the QFI. The QFI is used for identifying QoS flow, and the QoS flow has a mapping relation with a first Data Resource Bearer (DRB). Optionally, the first bearer identifier may be a data resource bearer identifier (DRB ID) of the first downlink data packet, where the DRB ID is used to identify a DRB. The DRB ID may be used to determine a PDCP entity that processes the first downlink packet.

When the gateway device receives a first downlink packet from a network, the gateway device may determine a first bearer identifier according to a QFI carried in a general packet radio service tunneling protocol (GTP) tunnel and a mapping relationship between QoS flow and DRB. Specifically, the identifier of the DRB corresponding to the QoS flow indicated by the QFI may be determined as the DRB ID of the first downlink packet, that is, the first bearer identifier in the mapping relationship. It should be noted that, in the present invention, bearers and Logical Channels (LCHs) are also in one-to-one correspondence, and the bearer identifier may also be a Logical channel identifier. In an optional implementation manner, before the gateway device determines the first bearer identifier, the mapping relationship between the QoS flow and the DRB and/or the mapping relationship between the DRB and the LCH may be obtained from the PRAS.

In an implementation manner, the gateway device receives the downlink data packet and determines QFI according to information carried in the GTP tunnel, and may add information such as QFI to the header of the downlink data packet to implement the SDAP function.

In one implementation, the first sequence number may be a PDCP sequence number of the first downlink data packet, and the PDCP sequence number may be used to characterize a transmission order of the first downlink data packet in the PDCP layer. It should be noted that, after receiving the data packet from the network, the gateway device may transmit the data packet through the WLAN link, or may transmit the data packet through the PRAS in the PRAS link or over the air interface. If transmitted through the PRAS, the PDCP layer of the PRAS may add sequence numbers to characterize the transmission order of data.

Optionally, the gateway device may obtain the initial PDCP sequence number when the first sequence number is the PDCP sequence number. The initial PDCP sequence number may be a PDCP sequence number of a first downlink packet to be transmitted to the first access device by the gateway device. Optionally, the gateway device may receive first indication information from the second access device, where the first indication information may be used to indicate an initial PDCP sequence number. That is, the gateway device may obtain the initial PDCP sequence number through the first indication information. It should be noted that the second access device may determine the initial PDCP sequence number by using the PDCP sequence number of the first downlink data packet to be transmitted.

It should be noted that, when the gateway device transmits the first downlink data packet, the first sequence number may be determined according to the initial PDCP sequence number obtained from the second access device. The first downlink data packet may be a first downlink data packet to be transmitted to the first access device, or may be any one of downlink data packets after the first downlink data packet. When the first downlink data packet is a first downlink data packet to be transmitted to the first access device, the first sequence number may be a PDCP sequence number of the first downlink data packet, that is, the initial PDCP sequence number; when the first downlink data packet is another downlink data packet to be transmitted, the first sequence number may be a PDCP sequence number accumulated on the initial PDCP sequence number. Exemplarily, assuming that the initial PDCP sequence number obtained by the gateway device is No. 5, if the first downlink data packet is a first downlink data packet to be transmitted to the first access device, the first sequence number may be No. 5; if the first downlink data packet is a third downlink data packet to be transmitted to the first access device, the first sequence number may be obtained by accumulating 2 on the initial PDCP sequence number, that is, the first sequence number may be number 7.

It should be noted that the gateway device receives the initial PDCP sequence number from the second access device for example, and in other implementations, the gateway device may determine the initial PDCP sequence number according to the PDCP sequence number from the second access device (e.g., referred to as PDCP sequence number a). In other words, the PDCP sequence number sent by the second access device to the gateway device may be the initial PDCP sequence number, or the PDCP sequence number a used to determine the initial PDCP sequence number. When the PDCP sequence number sent by the second access device to the gateway device is the PDCP sequence number a, the PDCP sequence number a is the PDCP sequence number of the last downlink packet received by the second access device from the gateway device. When the PDCP sequence number sent by the second access device to the gateway device is the initial PDCP sequence number, the initial PDCP sequence number is the PDCP sequence number obtained by adding 1 to the PDCP sequence number of the last downlink packet received by the second access device from the gateway device.

For example, assuming that the PDCP sequence number of the last downlink packet received by the second access device is 5, the second access device may send the PDCP sequence number of the last downlink packet to the gateway device, that is, send the above 5 to the gateway device, where the 5 is the PDCP sequence number a. When the gateway device obtains the PDCP sequence number a, the gateway device may determine that the initial PDCP sequence number is number 6 by adding 1 to the PDCP sequence number a. For another example, assuming that the PDCP sequence number of the last downlink packet received by the second access device is 5, the second access device may add 1 to the PDCP sequence number of the last downlink packet and send the result to the gateway device, that is, send No. 6 to the gateway device, where the No. 6 is the initial PDCP sequence number. Accordingly, the gateway device may directly determine that the initial PDCP sequence number is No. 6.

The gateway device may determine the first sequence number from an initial PDCP sequence number by determining the initial PDCP sequence number. It can be understood that the gateway device only needs to obtain the initial PDCP sequence number once for the first downlink data packet to be transmitted; for the subsequent downlink data packet of the first downlink data packet, the gateway device may add 1 to the initial PDCP sequence number to obtain the PDCP sequence number of the subsequent downlink data packet. By the mode, the time for acquiring the PDCP sequence number in the downlink can be reduced, so that the transmission time of the downlink data packet is reduced, and the time delay is further reduced.

Optionally, the first sequence number may also be an Adapter sequence number of the first downlink data packet, and the Adapter sequence number may be used to characterize a sending sequence of the first downlink data packet in an Adapter layer. It should be noted that there may be an offset between the Adapter sequence number and the PDCP sequence number.

The offset between the Adapter sequence number and the PDCP sequence number may be a preset value, that is, the gateway device may determine the offset between the Adapter sequence number and the PDCP sequence number in advance. Optionally, the gateway device may obtain the offset between the Adapter sequence number and the PDCP sequence number from the second access device. Optionally, the offset between the Adapter sequence number and the PDCP sequence number may be determined by the gateway device and the second access device, for example, the second access device determines the initial PDCP sequence number, the gateway determines the initial value of the Adapter sequence number, and the two devices interact with each other to obtain the offset between the two devices, which is not limited in this application.

It should be noted that, after the gateway device obtains the offset between the Adapter sequence number and the PDCP sequence number, the gateway device may determine the first sequence number according to the initial PDCP sequence number obtained by the second access device and the offset between the Adapter sequence number and the PDCP sequence number. For example, assuming that the offset between the Adapter sequence number and the PDCP sequence number is 5, if the initial PDCP sequence number received by the gateway device from the second access device is 6, the gateway device may determine that the first sequence number is 1 (i.e., a difference between the initial PDCP sequence number and the offset between the Adapter sequence number and the PDCP sequence number), and may also determine that the first sequence number is 11 (i.e., a sum of the initial PDCP sequence number and the offset between the Adapter sequence number and the PDCP sequence number). For another example, assuming that the offset between the Adapter sequence number and the PDCP sequence number is 5, if the initial PDCP sequence number received by the gateway device from the second access device is 5, the gateway device may determine that the first sequence number is 0 (i.e., the offset between the Adapter sequence number and the PDCP sequence number is subtracted from the initial PDCP sequence number), or may determine that the first sequence number is 10 (i.e., the offset between the Adapter sequence number and the PDCP sequence number is added to the initial PDCP sequence number). In the embodiment of the present application, the first sequence number is described below by taking a difference between an initial PDCP sequence number and an offset (between an Adapter sequence number and a PDCP sequence number) as an example, which does not limit the present application.

Wherein, the offset between the Adapter sequence number and the PDCP sequence number can be determined according to the initial PDCP sequence number and the initial Adapter sequence number. It should be noted that the gateway device may determine the initial Adapter sequence number, that is, determine the Adapter sequence number of the first downlink packet to be transmitted to the first access device by the gateway device. Specifically, the initial Adapter serial number may be 0, may also be No. 1, and may also be another integer number, which is not limited in this application.

After the gateway device determines an initial Adapter sequence number and determines an initial PDCP sequence number (e.g., received from the second access device or determined from the PDCP sequence number a from the second access device), an offset between the Adapter sequence number and the PDCP sequence number may be determined based on the initial Adapter sequence number and the initial PDCP sequence number. For example, assuming that the initial Adapter sequence number is 0 and the initial PDCP sequence number is No. 4, the gateway device may determine that an offset between the Adapter sequence number and the PDCP sequence number is 4. As another example, assuming that the initial Adapter sequence number is 1 and the initial PDCP sequence number is 4, the gateway device may determine that the offset between the Adapter sequence number and the PDCP sequence number is 3.

Optionally, the terminal device may obtain an offset between the Adapter sequence number and the PDCP sequence number, so that when receiving the second downlink data packet from the first access device, the terminal device may determine the PDCP sequence number of the first downlink data packet according to the first sequence number (i.e., the Adapter sequence number) in the second downlink data packet and the offset between the Adapter sequence number and the PDCP sequence number, and may sequence the first data packet according to the PDCP sequence number. Optionally, the terminal device may obtain the offset between the Adapter sequence number and the PDCP sequence number from the second access device, and may also obtain the offset between the Adapter sequence number and the PDCP sequence number from the gateway device, which is not limited in this application. Optionally, the terminal device may receive second indication information from the second access device, where the second indication information may be used to indicate an offset between the Adapter sequence number and the PDCP sequence number.

For example, assuming that the offset between the Adapter sequence number and the PDCP sequence number obtained by the terminal device is 5, if the first sequence number in the first downlink packet received by the terminal device from the first access device is 1, the terminal device may determine that the PDCP sequence number of the first downlink packet is No. 6. Assuming that the offset between the Adapter sequence number and the PDCP sequence number obtained by the terminal device is 5, if the first sequence number in the first downlink data packet received by the terminal device from the first access device is 0, the terminal device may determine that the PDCP sequence number of the first downlink data packet is No. 5.

Step S203, the gateway device sends the second downlink data packet to the first access device. Accordingly, the first access device may receive the second downlink data packet.

After determining the first bearer identifier and the first sequence number, the gateway device may send the second downlink data packet to which the first bearer identifier and the first sequence number are added to the first access device. Correspondingly, after receiving the second downlink data packet, the first access device may forward the second downlink data packet to the terminal device.

Optionally, in step S204, the first access device sends the second downlink data packet to the terminal device. Correspondingly, the terminal device receives the second downlink data packet, where the second downlink data packet may include the first bearer identifier, the first sequence number, and the first downlink data packet.

It should be noted that, after receiving the second downlink data packet through the first access device, the terminal device may determine the PDCP entity of the first downlink data packet according to the first bearer identifier in the second downlink data packet; the PDCP sequence number of the first downlink data packet in the PDCP entity may also be determined according to the first sequence number in the second downlink data packet, so as to sequence and merge the first downlink data packet. It should be noted that the terminal device may receive the downlink data packet (e.g., referred to as a historical downlink data packet) from the second access device before receiving the second downlink data packet from the first access device. Optionally, the sorting and merging of the first downlink data packet according to the first sequence number may be implemented by sorting or merging the first downlink data packet in the second downlink data packet with the historical downlink data packet from the second access device. The historical downlink data packet may include a downlink data packet corresponding to a PDCP sequence number that is previous to the PDCP sequence number of the first downlink data packet. For example, if the PDCP sequence number of the first downlink data packet is No. 5, the terminal may sort the first downlink data packet with the historical downlink data packet having the PDCP sequence number of No. 4 from the second access device.

In a downlink, the gateway device may add the first bearer identifier and the first sequence number to the first downlink data packet to obtain a second downlink data packet by receiving the first downlink data packet from the network, and send the second downlink data packet to the first access device, so that the terminal device may receive the second downlink data packet through the first access device, and obtain the PDCP sequence number of the first downlink data packet according to the first bearer identifier and the first sequence number in the second downlink data packet, thereby sequencing and merging the first downlink data packets, and further ensuring continuity of downlink data transmission.

Referring to fig. 3, fig. 3 is a flowchart of a data transmission method according to an embodiment of the present application. The method mainly describes the duplicate transmission on the downlink. The data transmission method may be implemented by the terminal device, the first access device, the second access device, and the gateway device, or may be implemented by a chip in the terminal device, a chip in the first access device, a chip in the second access device, and a chip in the gateway device. As shown in fig. 3, the data transmission method includes, but is not limited to, the following steps S301 to S306.

In step S301, the gateway device receives a first downlink data packet from the network. The first downlink data packet may be a downlink data packet to be transmitted to the terminal device. Specifically, the first downlink data packet may be sent by an access network device or a core network device in the network.

Before the duplicate transmission is started, the terminal equipment can access the network through the second access equipment. However, under the condition of poor network condition, the terminal device can be switched from the second access device to the first access device; or, the terminal device may add the first access device link to perform dual connectivity transmission. At this time, the second access device may determine to start duplicate transmission, that is, perform downlink data packet transmission on two links at the same time, so as to ensure that the downlink data packet transmission is not interrupted in the process of switching the terminal device to the first access device.

It should be noted that, the execution process of step S301 may refer to the specific description of step S201 in the corresponding embodiment of fig. 2, and is not described herein again.

Step S302, the gateway equipment adds a first bearing identifier and a first serial number to the first downlink data packet to obtain a second downlink data packet; the first bearer identification is used for indicating a radio bearer of the first downlink data packet, and the first sequence number is used for representing a sending sequence of the first downlink data packet.

It should be noted that, after receiving the indication of starting the duplicate transmission, the gateway device may send the data of the first downlink packet to both the first access device and the second access device. Because the first access device does not have a PDCP layer, the gateway device may add the first bearer identifier and the first sequence number to the first downlink data packet to obtain a second downlink data packet, and send the second downlink data packet to the first access device, where the second downlink data packet includes the first bearer identifier, the first sequence number, and the first downlink data packet.

In one implementation, the gateway device may receive third indication information from the second access device, where the third indication information may be used to instruct the gateway device to initiate a repeated (duplicate) transmission of a downlink. Optionally, the third indication information may be the same indication information as the first indication information, or may be different indication information. When the third indication information is the same indication information as the first indication information, the third indication information may also be used to indicate an initial PDCP sequence number.

Optionally, the terminal device may also receive fourth indication information from the second access device, where the fourth indication information is used to instruct the terminal device to start a downlink duplicate (duplicate) transmission. Optionally, after receiving the fourth indication information, the terminal device may establish dual connectivity with the first access device and the second access device. Optionally, the fourth indication information may be the same indication information as the second indication information, or may be different indication information. When the fourth indication information and the second indication information are the same indication information, the fourth indication information may further be used to indicate an offset between the Adapter sequence number and the PDCP sequence number. Optionally, the fourth indication information may be the same indication information as the first indication information, or may be different indication information. When the fourth indication information is the same indication information as the first indication information, the fourth indication information may also be used to indicate an initial PDCP sequence number.

It should be noted that, when the second access device finds that the current network condition is poor, the second access device may send third indication information and fourth indication information to the gateway device and the terminal device, respectively, where both the third indication information and the fourth indication information may be used for indicating to start the duplicate transmission. Optionally, under the condition that the terminal device finds that the current network condition is poor, the terminal device may send a request to a second access device to which the terminal device is accessed, at this time, the second access device may respond to the request, and send the third indication information and the fourth indication information to the gateway device and the terminal device, respectively, so as to start duplicate transmission.

It should be noted that, for the execution process of step S302, reference may be made to the specific description of step S202 in the corresponding embodiment of fig. 2, and details are not described here again.

Step S303, the gateway device sends the second downlink data packet to the first access device. Correspondingly, the first access device receives the second downlink data packet.

Optionally, in a scenario of non-duplicate transmission, the gateway device may transmit different downlink data packets through the two links, so that the terminal device connected to the two links can quickly acquire the downlink data packets. It should be noted that, the third indication information is used to indicate a duplicate transmission for example, and optionally, the second access device may also send the third indication information and the fourth indication information to the gateway device and the terminal device, so as to indicate to start the multi-link transmission.

It should be noted that, in a scenario of non-duplicate transmission, the gateway device may determine sequence numbers of downlink packets transmitted by two links respectively. Specifically, the gateway device may add sequence numbers to different downlink data packets according to the sending sequence. Exemplarily, it is assumed that the gateway device sequentially sorts the first 4 downlink data packets to be transmitted into number 1, number 2, number 3, and number 4 according to the sending sequence; after the multilink transmission is started, the gateway device may send downlink data packets with serial numbers of No. 1 and No. 2 to the first access device, and send downlink data packets with serial numbers of No. 3 and No. 4 to the second access device; and the PDCP sequence number can be carried in the downlink data packet and can be determined according to the initial PDCP sequence number obtained after the multi-link transmission is started. After receiving the four downlink data packets, the terminal device may determine the sending sequence of the downlink data packets according to the sequence number added by the gateway device. Optionally, the sequence number added by the gateway device may be a PDCP sequence number, or an Adapter sequence number, which is not limited in this application. It should be noted that, the execution process of step S303 may refer to the specific description of step S203 in the corresponding embodiment of fig. 2, and is not described herein again.

Step S304, the gateway device sends the first downlink data packet to the second access device. Correspondingly, the second access device receives the first downlink data packet.

It should be noted that, the execution of step S303 and step S304 is not sequential, and this application does not limit this.

Step S305, the second access device adds the second serial number to the first downlink data packet to obtain a third downlink data packet, and sends the third downlink data packet to the terminal device. And the second sequence number is used for representing the transmission sequence of the first downlink data packet.

Optionally, in a scenario of duplicate transmission, after the second access device receives the first downlink data packet, the second access device may add a second sequence number to the first downlink data packet to obtain a third downlink data packet. The second sequence number is used for representing the sending sequence of the first downlink data packet. The second sequence number may be a PDCP sequence number of the first downlink packet.

In an implementation manner, in a case that the first sequence number is a PDCP sequence number and the second sequence number is also a PDCP sequence number, a value of the first sequence number may be the same as a value of the second sequence number. Optionally, the first serial number may also be different from the second serial number, and the first serial number is an Adapter serial number, which is not limited in this application.

It should be noted that, in the case that the first sequence number is an Adapter sequence number and the second sequence number is a PDCP sequence number, at this time, there may be an offset between the first sequence number and the second sequence number, where the offset may be the offset (between the Adapter sequence number and the PDCP sequence number) described in the embodiment of fig. 2.

Optionally, if the terminal device receives a third downlink data packet from the second access device, the terminal device may determine the PDCP sequence number of the first downlink data packet according to the second sequence number added to the third downlink data packet, so that the terminal device may perform repeated detection, sorting, and merging on the first downlink data packet according to the PDCP sequence number.

Step S306, the first access device sends the second downlink data packet to the terminal device. Correspondingly, the terminal device receives a second downlink data packet from the first access device, where the second downlink data packet includes the first bearer identifier, the first sequence number, and the first downlink data packet.

It should be noted that, the execution of step S305 and step S306 is not sequential, and this application does not limit this. Optionally, in the scenario of duplicate transmission, the terminal device may receive the second downlink data packet through the first access device, and may also receive the third downlink data packet through the second access device. For example, when the first access device network is poor, the terminal device may receive the third downlink data packet through the second access device. The terminal device receives the second downlink data packet through the first access device as an example, which does not limit the present application.

In an implementation manner, the terminal device may send a second message to the second access device, where the second message is used to indicate that the second downlink data packet is successfully received. It should be noted that, after the terminal device successfully receives the second downlink data packet, the terminal device may send a second message to the second access device.

In an implementation manner, the second message may include a first bearer identifier and a first sequence number, and at this time, the second message may be specifically used to indicate that the terminal device successfully receives the second downlink data packet including the first bearer identifier and the first sequence number. It should be noted that, after receiving the second message, the second access device may stop retransmitting the downlink data packet including the first sequence number in the second message to the terminal device. That is, after receiving the first downlink data packet from the gateway device, the second receiving device may determine a sequence number (e.g., PDCP sequence number) of the first downlink data packet, determine whether the sequence number of the first downlink data packet is the same as the first sequence number of the second message, and if so, stop sending or retransmitting the third downlink data packet to the terminal device; if not, the third downlink data packet may be sent to the terminal device.

Optionally, if the terminal device successfully receives the third downlink data packet from the second access device, the terminal device may send a third message to the first access device, where the third message may be used to indicate that the third downlink data packet is successfully received. Optionally, if the terminal device successfully receives the third downlink data packet from the second access device, the third message sent by the terminal device to the first access device may also include the first bearer identifier and the second sequence number, so as to instruct the first access device to stop retransmitting the downlink data packet corresponding to the second sequence number (i.e., the PDCP sequence number), that is, instruct the first access device to stop retransmitting the third downlink data packet.

Optionally, after the terminal device successfully receives the second downlink data packet from the first access device and completes the duplicate transmission, the terminal device may disconnect from the second access device, so as to switch from the second access device to the first access device. For example, after the terminal device successfully receives the downlink data packet from the WIFI link and completes the duplicate transmission, the terminal device may disconnect from the PRAS, so as to switch from the PRAS to the WIFI AP. Optionally, the PRAS may instruct the terminal device to delete the connection with the PRAS.

It should be noted that, for the relevant content of the step S306, reference may be made to the detailed description in the step S204 in the embodiment corresponding to fig. 2, and details are not repeated herein.

After the network equipment receives the third indication information used for indicating duplicate transmission, the second downlink data packet comprising the first downlink data packet can be sent to the first access equipment, the first downlink data packet is sent to the second access equipment, and the first downlink data packet is transmitted through the two links, so that the terminal equipment can receive the first downlink data packet from the link with better signal quality more quickly, the first downlink data packet can be sequenced and combined according to the PDCP serial number of the first downlink data packet, the continuous transmission of the downlink data packet is further ensured, and the time delay of downlink data packet transmission is reduced.

Referring to fig. 4, fig. 4 is a flowchart of a data transmission method according to an embodiment of the present disclosure. The method mainly describes data transmission on the uplink. The data transmission method may be implemented by the terminal device, the first access device, the second access device, and the gateway device, or may be implemented by a chip in the terminal device, a chip in the first access device, a chip in the second access device, and a chip in the gateway device. In the embodiments corresponding to fig. 4 and 5, the above-mentioned "first data packet" may be named as "first uplink data packet" in order to distinguish from the "first downlink data packet" in the downlink in the embodiments corresponding to fig. 2 and 3. As shown in fig. 4, the data transmission method includes, but is not limited to, the following steps S401 to S403.

Step S401, the terminal equipment adds a second bearing identification and a third serial number to the first uplink data packet to obtain a second uplink data packet; the second bearer identification is used for indicating the radio bearer of the first uplink data packet, and the third sequence number is used for representing the sending sequence of the first uplink data packet. The second bearer identifier and the third sequence number are the bearer identifier and the sequence number added to the first uplink packet in the uplink.

It should be noted that, before the terminal device adds the second bearer identifier and the third sequence number to the first uplink data packet to obtain the second uplink data packet, the terminal device may obtain the first uplink data packet. The first uplink data packet may be an uplink data packet to be transmitted, which is generated by the terminal device.

In one implementation, the first uplink packet may include a quality of service flow identifier QFI; the terminal device may determine the second bearer identity according to the QFI. The second bearer identifier may be a DRB ID of the first uplink data packet, and the DRB ID is used to identify a DRB. The DRB ID may be used to determine a PDCP entity that processes the first uplink packet.

In an implementation manner, the third sequence number may be a PDCP sequence number of the first uplink data packet, and the PDCP sequence number may be used to characterize a transmission order of the first uplink data packet in the PDCP layer. Optionally, the third sequence number may also be an Adapter sequence number of the first uplink data packet, and the Adapter sequence number may be used to characterize a sending sequence of the first uplink data packet in an Adapter layer, which is not limited in this application.

Optionally, if the third sequence number is an Adapter sequence number of the first uplink data packet, the gateway device may obtain an offset between the Adapter sequence number and the PDCP sequence number. Specifically, the gateway device may obtain, through the second access device, an offset between the Adapter sequence number and the PDCP sequence number from the terminal device. Optionally, the gateway device may also obtain the offset between the Adapter sequence number and the PDCP sequence number in another manner, which is not limited in this application.

Optionally, if the third sequence number is the PDCP sequence number of the first uplink data packet, the gateway device may obtain an initial PDCP sequence number. Specifically, the gateway device may obtain an initial PDCP sequence number from the terminal device through the second access device. Optionally, the gateway device may also obtain the initial PDCP sequence number in other manners, which is not limited in this application.

It should be noted that, for the relevant description about the second bearer identifier and the third sequence number in step S401, reference may be made to specific contents about the first bearer identifier and the first sequence number in step S202 in the corresponding embodiment of fig. 2, and details are not described here again.

Step S402, the terminal device sends a second uplink data packet to the first access device. Accordingly, the first access device may receive the second uplink data packet.

After determining the second bearer identifier and the third sequence number, the terminal device may send the second uplink data packet to which the second bearer identifier and the third sequence number are added to the first access device. Accordingly, after receiving the second uplink data packet, the first access device may forward the second uplink data packet to the gateway device.

Optionally, the first access device may be a WiFi AP. After receiving the second uplink data packet, the WiFi AP may further perform WiFi side protocol stack processing on the second uplink data packet, and send the processed second uplink data packet to the first access device.

It should be noted that, for the relevant content in step S402, reference may be made to the detailed description in step S203 of the embodiment corresponding to fig. 2, and details are not repeated herein.

Step S403, the first access device sends the second uplink data packet to the gateway device. Accordingly, the gateway device receives a second uplink data packet from the first access device, where the second uplink data packet may include the second bearer identifier, the third sequence number, and the first uplink data packet. Optionally, the second uplink data packet may be a second uplink data packet processed by the first access device, and the processed second uplink data packet may include a second bearer identifier, a third sequence number, and a first uplink data packet.

In an implementation manner, the gateway device may determine, according to the second bearer identifier, a PDCP entity of the first uplink data packet; the gateway device may further determine, according to the third sequence number, a PDCP sequence number of the first uplink data packet in the PDCP entity; the PDCP sequence number is used to characterize a transmission order of the first uplink data packet in the PDCP entity.

It should be noted that, after receiving the second uplink data packet, the gateway device may sequentially upload the second uplink data packet to the network according to the sequence of the sequence numbers. For example, if the third sequence number is a PDCP sequence number, the gateway device may upload the first uplink packet to the network according to the sequence of the PDCP sequence number in the PDCP layer. For another example, if the third sequence number is an Adapter sequence number, the gateway device may obtain an offset between the Adapter sequence number and a PDCP sequence number, so as to determine the PDCP sequence number of the first uplink packet according to the offset between the Adapter sequence number and the PDCP sequence number, and sequentially upload the first uplink packet. Optionally, when the third sequence number is an Adapter sequence number, the gateway device may also send the third sequence number to the second access device, so as to determine the PDCP sequence number of the first uplink data packet by the second access device, which is not limited in this application.

It should be noted that, for the relevant content in step S403, reference may be made to the detailed description in step S204 of the embodiment corresponding to fig. 2, and details are not repeated herein.

In the uplink, the terminal device adds the second bearer identifier and the third sequence number to the first uplink data packet to obtain a second uplink data packet, and sends the second uplink data packet to the first access device, so that the gateway device can receive the second uplink data packet through the first access device, and obtain the PDCP sequence number of the first uplink data packet according to the second bearer identifier and the third sequence number in the second uplink data packet, thereby sequencing and combining the first uplink data packet, and further ensuring the continuity of uplink data transmission.

Referring to fig. 5, fig. 5 is a flowchart of a data transmission method according to an embodiment of the present application. The method mainly describes duplicate transmission on the uplink. The data transmission method may be implemented by the terminal device, the first access device, the second access device, and the gateway device, or may be implemented by a chip in the terminal device, a chip in the first access device, a chip in the second access device, and a chip in the gateway device. As shown in fig. 5, the data transmission method includes, but is not limited to, the following steps S501 to S505.

Step S501, adding a second bearing identifier and a third serial number to a first uplink data packet by the terminal equipment to obtain a second uplink data packet; the second bearer identification is used for indicating the radio bearer of the first uplink data packet, and the third sequence number is used for representing the sending sequence of the first uplink data packet.

In one implementation, the terminal device may receive fifth indication information from the second access device, where the fifth indication information is used to indicate that the terminal device starts uplink repeat (duplicate) transmission. Optionally, after receiving the fifth indication information, the terminal device may be connected to the first access device and the second access device at the same time.

Under the scenario of non-duplicate transmission, the terminal device may transmit different uplink data packets through the two links, so that the terminal device connecting the two links can quickly transmit the successful uplink data packets. It should be noted that the fifth indication information is used to indicate duplicate transmission for example, optionally, the second access device may also send the indication information to the gateway device and the terminal device, so as to indicate to start multilink transmission.

As in the downlink, the second access device may determine the current network status, or the terminal device may determine the current network status. However, whether to initiate the duplicate transmission may also be determined by the second access device, and this application is not described herein again.

It should be noted that, the execution process of step S501 may refer to the specific description of step S501 in the embodiment corresponding to fig. 4, and is not described herein again.

Step S502, the terminal device sends a second uplink data packet to the first access device. Correspondingly, the first access device receives the second uplink data packet.

By starting the duplicate transmission, the terminal device may send the data of the first uplink data packet to both the first access device and the second access device, so as to transmit the data of the first uplink data packet through different links. Wherein, there is no PDCP layer in the first access device, and there is no corresponding PDCP sequence number. Therefore, the terminal device may add the second bearer identifier and the third sequence number to the first uplink data packet to obtain a second uplink data packet, and send the second uplink data packet to the first access device, where the second uplink data packet includes the second bearer identifier, the third sequence number, and the first uplink data packet.

It should be noted that, the process of executing step S502 may refer to the specific description of step S402 in the embodiment corresponding to fig. 4, and is not described herein again.

Step S503, the terminal device adds a fourth sequence number to the first uplink data packet to obtain a third uplink data packet, and sends the third uplink data packet to the second access device. And the fourth sequence number is used for representing the transmission sequence of the first uplink data packet.

It should be noted that, the execution of step S501, step S502, and step S503 is not sequential, and this application does not limit this. That is to say, the terminal device adds the second bearer and the third sequence number to the first uplink data packet and sends the first uplink data packet to the first access device, and the terminal device adds the fourth sequence number to the first uplink data packet and sends the first uplink data packet to the second access device are not in sequence with each other.

Optionally, in a scenario of duplicate transmission, after the second access device receives the third uplink data packet and obtains the first uplink data packet, the second access device may determine the fourth sequence number. And the fourth sequence number is used for representing the sending sequence of the first uplink data packet. The fourth sequence number may be a PDCP sequence number of the first uplink packet.

In an implementation manner, in a case that the third sequence number is a PDCP sequence number and the fourth sequence number is also a PDCP sequence number, a value of the first sequence number may be the same as a value of the second sequence number. Optionally, the third serial number may also be different from the fourth serial number, and the third serial number is the Adapter serial number, which is not limited in this application.

It should be noted that, in the case that the third sequence number is an Adapter sequence number and the fourth sequence number is a PDCP sequence number, at this time, there may be an offset between the third sequence number and the fourth sequence number, where the offset may be the offset (between the Adapter sequence number and the PDCP sequence number) described in the embodiment of fig. 2.

Step S504, the second access device sends the first uplink data packet to the gateway device; the fourth sequence number may be sent to the gateway device at the same time.

In an optional implementation method, the second access device may send the fourth sequence number to the gateway device, and notify the gateway device that the first uplink data packet identified by the fourth sequence number has been successfully received. Subsequently, the relevant data packets may be delivered in order to the gateway device.

Optionally, in a scenario of non-duplicate transmission, the terminal device may send different uplink data packets to the first access device and the second access device, respectively, which is not limited in this application.

Optionally, if the gateway device receives a third uplink data packet from the second access device, the gateway device may determine the PDCP sequence number of the first uplink data packet according to a fourth sequence number added to the third uplink data packet, so that the gateway device may upload the received first uplink data packets to the network in sequence according to the sequence of the sequence numbers.

Step S505, the first access device sends the second uplink data packet to the gateway device. Accordingly, the gateway device may receive, through the first access device, a second uplink data packet from the terminal device, where the second uplink data packet may include a second bearer identifier, a third sequence number, and the first uplink data packet.

It should be noted that, the execution of step S504 and step S505 is not sequential, and this application does not limit this. Optionally, in the scenario of duplicate transmission, the gateway device may receive the second uplink data packet through the first access device, and may also receive the third uplink data packet through the second access device. For example, when the network of the first access device is poor, the terminal device may receive the third uplink data packet through the second access device. The gateway device receives the second uplink data packet through the first access device as an example, which is not limited to the present application.

Optionally, if the gateway device receives the second uplink data packet from the first access device, the gateway device may determine the PDCP sequence number of the first uplink data packet according to a third sequence number added to the second uplink data packet, so that the gateway device may upload the received first uplink data packets to the network in sequence according to the sequence of the sequence numbers. Optionally, when the third sequence number is an Adapter sequence number, the gateway device may determine the PDCP sequence number of the first uplink datagram according to the Adapter sequence number and the initial PDCP sequence number acquired by the gateway device. Optionally, when the third sequence number is an Adapter sequence number, the gateway device may determine the PDCP sequence number of the first uplink datagram according to the Adapter sequence number and an offset between the Adapter sequence number and the PDCP sequence number.

In an implementation manner, the terminal device may send a first message to the second access device, where the first message is used to indicate that the first uplink data packet is successfully sent.

It should be noted that, if the terminal device receives the feedback message of successfully receiving the uplink data packet of a certain link, the terminal device may notify another link of the sequence number of the successfully received uplink data packet. For example, if the terminal device receives a feedback message from the WiFi link, where the feedback message is used to indicate that the WiFi link successfully receives the second uplink data packet, the terminal device may send a first message to the second access device in the PRAS link, where the first message may be used to indicate that the first uplink data packet included in the second uplink data packet is successfully received.

In one implementation manner, the first message may include the second bearer identifier and the third sequence number. It should be noted that the second access device may determine, according to the second bearer identifier and the third sequence number in the first message, the PDCP sequence number of the first uplink data packet, so as to instruct the second access device to stop sending resource scheduling information to the terminal device, where the resource scheduling information is used to schedule retransmission of the uplink data packet corresponding to the PDCP sequence number, that is, to stop scheduling retransmission of the third uplink data packet.

For example, if the terminal device receives a feedback message from the WiFi link, where the feedback message may be used to indicate that the network device successfully receives the second uplink data packet, the terminal device may send a first message to the PRAS link, where the first message is used to indicate that the first uplink data packet included in the second uplink data packet is successfully received. Optionally, the first message may include the second bearer identifier and the third sequence number, and the first message may also be used to instruct the PRAS to stop scheduling and retransmitting resources of an uplink data packet of the PDCP sequence number corresponding to the third sequence number.

Optionally, if the gateway successfully receives the first uplink data packet from the second access device, the gateway device may send a fourth message to the first access device, where the fourth message may be used to indicate that the first uplink data packet is successfully received. Optionally, if the gateway device successfully receives the first uplink data packet from the second access device, a fourth message sent by the gateway device to the first access device may also include the second bearer identifier and a fourth sequence number, so as to instruct the first access device to stop sending the resource scheduling information to the terminal device, where the resource scheduling information is used for retransmission of the uplink data packet corresponding to the fourth sequence number (i.e., the PDCP sequence number), that is, to stop scheduling retransmission of the second uplink data packet.

Optionally, the terminal device may successfully transmit the second uplink data packet through the first access device, and after the duplicate transmission is completed, the terminal device may disconnect from the second access device, so as to switch from the second access device to the first access device. For example, the terminal device successfully transmits the uplink data packet through the WIFI link, and after the duplicate transmission is completed, the connection with the PRAS link may be disconnected, so as to switch from the PRAS to the WIFI AP. Optionally, the PRAS may instruct the terminal device to delete the connection with the PRAS.

It should be noted that, the execution process of step S505 may refer to the specific description of step S403 in the embodiment corresponding to fig. 4, and is not described herein again.

After receiving the fifth indication information for indicating duplicate transmission, the terminal device may send a second uplink data packet including the first uplink data packet to the first access device, and send a third uplink data packet including the first uplink data packet to the second access device, so as to perform transmission of the first uplink data packet through the two links, thereby enabling the gateway device to receive the first uplink data packet from the link with better signal quality more quickly, and may sequence and combine the first uplink data packet according to the PDCP sequence number of the first uplink data packet, thereby ensuring continuous transmission of the uplink data packet, and reducing the time delay of uplink data packet transmission.

Referring to fig. 6, fig. 6 is a schematic structural diagram of a communication device according to an embodiment of the present disclosure. The apparatus may be a gateway device in downlink, or may be an apparatus in a gateway device, or may be an apparatus capable of being used in cooperation with a gateway device. Optionally, the apparatus may be a terminal device in an uplink, or may be an apparatus in the terminal device, or may be an apparatus capable of being used in cooperation with the terminal device. The communication apparatus shown in fig. 6 may include a processing unit 601 and a communication unit 602. The processing unit 601 is configured to perform data processing. The communication unit 602 is integrated with a receiving unit, a transmitting unit, and the like. The communication unit 602 may also be referred to as a transceiving unit. Alternatively, communication section 602 may be divided into a reception section and a transmission section. Wherein, the detailed description of each unit is as follows:

the processing unit 601 is configured to add a bearer identifier and a first sequence number to the first data packet to obtain a second data packet; the bearer identifier is used for indicating a radio bearer of the first data packet, and the first sequence number is used for representing the sending sequence of the first data packet;

the communication unit 602 is configured to send the second data packet to the first access device.

In an implementation manner, the communication unit 602 is further configured to send the first data packet to a second access device.

In one implementation, the first packet includes a quality of service flow identifier QFI; the processing unit 601 is further configured to determine the bearer identifier according to the QFI.

In an implementation manner, the processing unit 601 is further configured to obtain an initial PDCP sequence number, where an offset between the first sequence number and the second sequence number is the initial PDCP sequence number.

In an implementation manner, the communication unit 602 is further configured to receive indication information from the second access device, where the indication information is used to indicate that a duplicate transmission is started.

In an implementation manner, the communication unit 602 is further configured to receive the first data packet.

In an implementation manner, the communication unit 602 is further configured to send a first message to the second access device, where the first message is used to indicate that the second data packet is successfully sent.

The apparatus may be a terminal device in downlink, or may be an apparatus in a terminal device, or may be an apparatus capable of being used in cooperation with a terminal device. Optionally, the apparatus may be a gateway device in an uplink, may also be an apparatus in the gateway device, or may be an apparatus capable of being used in cooperation with the gateway device. The communication apparatus shown in fig. 6 may include a processing unit 601 and a communication unit 602. The processing unit 601 is configured to perform data processing. The communication unit 602 is integrated with a receiving unit, a transmitting unit, and the like. The communication unit 602 may also be referred to as a transceiving unit. Alternatively, communication section 602 may be divided into a reception section and a transmission section. Wherein, the detailed description of each unit is as follows:

the communication unit 602 is configured to receive a second data packet from the first access device, where the second data packet includes a bearer identifier, a first sequence number, and a first data packet; the bearer identifier is used for indicating a radio bearer of the first data packet, and the first sequence number is used for representing the sending sequence of the first data packet;

the processing unit 601 is configured to determine a transmission order of the first data packet according to the bearer identifier and the first sequence number.

In one implementation, the first packet includes a quality of service flow identifier QFI, and the bearer identity is determined based on the QFI.

In an implementation manner, the communication unit 602 is further configured to send a second message to the second access device, where the second message is used to indicate that the second data packet is successfully received.

According to the embodiment of the present application, the units in the communication apparatus shown in fig. 6 may be respectively or entirely combined into one or several other units to form the unit, or some unit(s) therein may be further split into multiple units with smaller functions to form the unit(s), which may achieve the same operation without affecting the achievement of the technical effect of the embodiment of the present application. The units are divided based on logic functions, and in practical application, the functions of one unit can be realized by a plurality of units, or the functions of a plurality of units can be realized by one unit. In other embodiments of the present application, the communication device may also include other units, and in practical applications, these functions may also be implemented by assistance of other units, and may be implemented by cooperation of multiple units.

The communication device may be, for example: a chip, or a chip module. Each module included in each apparatus and product described in the above embodiments may be a software module, a hardware module, or a part of the software module and a part of the hardware module. For example, for each device or product applied to or integrated in a chip, each module included in the device or product may be implemented by hardware such as a circuit, or at least a part of the modules may be implemented by a software program running on a processor integrated in the chip, and the rest (if any) part of the modules may be implemented by hardware such as a circuit; for each device and product applied to or integrated with the chip module, each module included in the device and product may be implemented in a hardware manner such as a circuit, and different modules may be located in the same component (e.g., a chip, a circuit module, etc.) or different components of the chip module, or at least a part of the modules may be implemented in a software program running on a processor integrated within the chip module, and the rest (if any) part of the modules may be implemented in a hardware manner such as a circuit; for each device and product applied to or integrated in the terminal, each module included in the device and product may be implemented by using hardware such as a circuit, different modules may be located in the same component (e.g., a chip, a circuit module, etc.) or different components in the terminal, or at least a part of the modules may be implemented by using a software program running on a processor integrated in the terminal, and the rest (if any) part of the modules may be implemented by using hardware such as a circuit.

The embodiments of the present application and the embodiments of the foregoing method are based on the same concept, and the technical effects brought by the embodiments are also the same, and for the specific principle, reference is made to the description of the foregoing embodiments, which is not repeated herein.

Referring to fig. 7, fig. 7 is a communication device 70 according to an embodiment of the present disclosure. The communication device 70 may be used to implement the functionality of the gateway apparatus in the downlink of the above-described method embodiments. The communication means may be a gateway device or means for a gateway device. The above-mentioned device for the gateway apparatus may be a chip system or a chip in the gateway apparatus. Optionally, the communication device 70 may be configured to implement the functions of the terminal device in the uplink in the above method embodiment. The communication means may be a terminal device or a means for a terminal device. The above-mentioned device for terminal equipment may be a chip system or a chip in the terminal equipment. The chip system may be composed of a chip, or may include a chip and other discrete devices. As shown in fig. 7, the communication device 70 may include a processor 701 and a transceiver 702. Optionally, the communication device may further include a memory 703. The processor 701, transceiver 702, and memory 703 may be connected by a bus 704 or otherwise. The bus lines are shown in fig. 7 by thick lines, and the connection manner between other components is merely illustrative and not limited thereto. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 7, but this is not intended to represent only one bus or type of bus.

The coupling in the embodiments of the present application is an indirect coupling or a communication connection between devices, units or modules, and may be an electrical, mechanical or other form for information interaction between the devices, units or modules. The specific connection medium among the processor 701, the transceiver 702, and the memory 703 is not limited in this embodiment.

The memory 703 may include both read-only memory and random-access memory, and provides instructions and data to the processor 701. A portion of the memory 703 may also include non-volatile random access memory.

The Processor 701 may be a Central Processing Unit (CPU), and the Processor 701 may also be other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor, and optionally, the processor 701 may be any conventional processor or the like. Wherein:

a memory 703 for storing program instructions.

A processor 701 for invoking program instructions stored in the memory 703 for:

adding a bearing identifier and a first sequence number to the first data packet to obtain a second data packet; the bearer identifier is used for indicating a radio bearer of the first data packet, and the first sequence number is used for representing the sending sequence of the first data packet;

the transceiver 702 is invoked for sending the second data packet to the first access device.

In one implementation, the transceiver 702 is further configured to transmit the first data packet to a second access device.

In one implementation, the first packet includes a quality of service flow identifier QFI; the processor 701 is further configured to determine the bearer identifier according to the QFI.

In an implementation manner, the processor 701 is further configured to obtain an initial PDCP sequence number, where an offset between the first sequence number and the second sequence number is the initial PDCP sequence number.

In one implementation, the transceiver 702 is further configured to receive indication information from the second access device, where the indication information is used to indicate that repeated duplicate transmission is started.

In one implementation, the transceiver 702 is further configured to receive the first data packet.

In an implementation manner, the transceiver 702 is further configured to send a first message to the second access device, where the first message is used to indicate that the second data packet is successfully sent.

The communication device 70 may be used to implement the functions of the terminal equipment in the downlink of the above-described method embodiments. The communication means may be a terminal device or a means for a terminal device. The device for the terminal equipment can be a chip system or a chip in the terminal equipment. Optionally, the communication device 70 may be configured to implement the function of the gateway device in the uplink in the above method embodiment. The communication means may be a gateway device or means for a gateway device. The above-mentioned device for the gateway apparatus may be a chip system or a chip in the gateway apparatus. The chip system may be composed of a chip, or may include a chip and other discrete devices. As shown in fig. 7, the communication device 70 may include a processor 701 and a transceiver 702. Optionally, the communication device may further include a memory 703. Wherein:

a memory 703 for storing program instructions.

A processor 701 for invoking program instructions stored in memory 703 for:

invoking a transceiver 702 for receiving a second data packet from the first access device, the second data packet comprising a bearer identification, a first sequence number, and a first data packet; the bearer identifier is used for indicating a radio bearer of the first data packet, and the first sequence number is used for representing the sending sequence of the first data packet;

the processor 701 is configured to determine a transmission sequence of the first data packet according to the bearer identifier and the first sequence number.

In one implementation, the transceiver 702 is further configured to send a second message to the second access device, where the second message is used to indicate that the second data packet is successfully received.

In the embodiments of the present application, the methods provided by the embodiments of the present application may be implemented by running a computer program (including program codes) capable of executing the steps involved in the respective methods as shown in fig. 2 to 5 on a general-purpose computing device such as a computer including a Central Processing Unit (CPU), a random access storage medium (RAM), a read-only storage medium (ROM), and the like, and a storage element. The computer program may be recorded on a computer-readable recording medium, for example, and loaded and executed in the above-described computing apparatus via the computer-readable recording medium.

Based on the same inventive concept, the principle and the advantageous effect of the communication apparatus to solve the problem provided in the embodiment of the present application are similar to the principle and the advantageous effect of the communication apparatus to solve the problem in the embodiment of the method of the present application, and for brevity, the principle and the advantageous effect of the implementation of the method may be referred to, and are not described herein again.

The embodiment of the present application further provides a chip, where the chip may perform relevant steps of the gateway device in the downlink or the terminal device in the uplink in the foregoing method embodiments. The chip is used for: adding a bearing identifier and a first sequence number to the first data packet to obtain a second data packet; the bearer identifier is used for indicating a radio bearer of the first data packet, and the first sequence number is used for representing the sending sequence of the first data packet; the chip is further configured to send the second packet to the first access device.

In one implementation, the chip is further configured to send the first data packet to a second access device.

In one implementation, the first packet includes a quality of service flow identifier QFI; the chip is also used for determining the bearing identification according to the QFI.

In one implementation, the chip is further configured to obtain an initial PDCP sequence number, where an offset between the first sequence number and the second sequence number is the initial PDCP sequence number.

In one implementation, the chip is further configured to receive indication information from the second access device, where the indication information is used to indicate that repeated duplicate transmission is started.

In one implementation, the chip is further configured to receive the first data packet.

In an implementation manner, the chip is further configured to send a first message to the second access device, where the first message is used to indicate that the second data packet is successfully sent.

In one implementation, the chip includes at least one processor, at least one first memory, and at least one second memory; the at least one first memory and the at least one processor are interconnected through a line, and instructions are stored in the first memory; the at least one second memory and the at least one processor are interconnected through a line, and the second memory stores the data required to be stored in the method embodiment.

For each device and product applied to or integrated in the chip, each module included in the device and product may be implemented in hardware such as a circuit, or at least a part of the modules may be implemented in software that runs on a processor integrated in the chip, and the rest (if any) part of the modules may be implemented in hardware such as a circuit.

The embodiment of the present application further provides another chip, where the chip may perform the relevant steps of the terminal device in the uplink or the gateway device in the downlink in the foregoing method embodiments. The chip is used for: receiving a second data packet from the first access device, wherein the second data packet comprises a bearer identification, a first sequence number and a first data packet; the bearer identifier is used for indicating a radio bearer of the first data packet, and the first sequence number is used for representing the sending sequence of the first data packet; the chip is further configured to determine a transmission order of the first data packet according to the bearer identifier and the first sequence number.

In one implementation, the chip is further configured to send a second message to the second access device, where the second message is used to indicate that the second packet is successfully received.

In one implementation, the chip includes at least one processor, at least one first memory, and at least one second memory; the at least one first memory and the at least one processor are interconnected through a line, and instructions are stored in the first memory; the at least one second memory and the at least one processor are interconnected through a line, and the second memory stores data required to be stored in the method embodiment.

For each device or product applied to or integrated in the chip, each module included in the device or product may be implemented by hardware such as a circuit, or at least a part of the modules may be implemented by a software program running on a processor integrated in the chip, and the rest (if any) part of the modules may be implemented by hardware such as a circuit.

Referring to fig. 8, fig. 8 is a schematic structural diagram of a module apparatus according to an embodiment of the present disclosure. The module device 80 can perform the steps related to the gateway device in the downlink or the terminal device in the uplink in the foregoing method embodiments, and the module device 80 includes: a communication module 801, a power module 802, a storage module 803, and a chip module 804.

The power module 802 is used for providing power for the module device; the storage module 803 is used for storing data and instructions; the communication module 801 is used for performing internal communication of module equipment or performing communication between the module equipment and external equipment; the chip module 804 is used for:

and sending the second data packet to the first access equipment.

In an implementation manner, the chip module 804 is further configured to send the first data packet to a second access device.

In an implementation manner, the chip module 804 is further configured to obtain an initial PDCP sequence number, where an offset between the first sequence number and the second sequence number is the initial PDCP sequence number.

In one implementation, the chip module 804 is further configured to receive indication information from the second access device, where the indication information is used to indicate that repeated duplicate transmission is started.

In one implementation, the chip module 804 is further configured to receive the first data packet.

In an implementation manner, the chip module 804 is further configured to send a first message to the second access device, where the first message is used to indicate that the second data packet is successfully sent.

For each device and product applied to or integrated in the chip module, each module included in the device and product may be implemented by using hardware such as a circuit, and different modules may be located in the same component (e.g., a chip, a circuit module, etc.) or different components of the chip module, or at least some of the modules may be implemented by using a software program running on a processor integrated in the chip module, and the rest (if any) of the modules may be implemented by using hardware such as a circuit.

Referring to fig. 8, fig. 8 is a schematic structural diagram of another module apparatus according to an embodiment of the present disclosure. The module apparatus 80 can perform the steps related to the terminal apparatus in uplink or the gateway apparatus in downlink in the foregoing method embodiments, and the module apparatus 80 includes: a communication module 801, a power module 802, a storage module 803, and a chip module 804.

receiving a second data packet from the first access device, wherein the second data packet comprises a bearing identification, a first sequence number and a first data packet; the bearer identifier is used for indicating a radio bearer of the first data packet, and the first sequence number is used for representing a sending sequence of the first data packet;

and determining the sending sequence of the first data packet according to the bearing identification and the first sequence number.

In an implementation manner, the chip module 804 is further configured to send a second message to the second access device, where the second message is used to indicate that the second data packet is successfully received.

For each device and product applied to or integrated in the chip module, each module included in the device and product may be implemented in a hardware manner such as a circuit, and different modules may be located in the same component (for example, a chip, a circuit module, etc.) or different components of the chip module, or at least part of the modules may be implemented in a software program, the software program runs on a processor integrated inside the chip module, and the rest (if any) part of the modules may be implemented in a hardware manner such as a circuit.

The embodiment of the present application further provides a computer-readable storage medium, in which one or more instructions are stored, and the one or more instructions are adapted to be loaded by a processor and execute the method provided by the foregoing method embodiment.

Embodiments of the present application also provide a computer program product containing instructions, which when run on a computer, cause the computer to perform the method provided by the above method embodiments.

It should be noted that, for simplicity of description, the above-mentioned embodiments of the method are described as a series of acts or combinations, but those skilled in the art should understand that the present application is not limited by the order of acts described, as some steps may be performed in other orders or simultaneously according to the present application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.

The steps in the method of the embodiment of the application can be sequentially adjusted, combined and deleted according to actual needs.

The modules in the device can be merged, divided and deleted according to actual needs.

Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, which may include: flash disks, read-Only memories (ROMs), random Access Memories (RAMs), magnetic or optical disks, and the like.

The above disclosure is only one preferred embodiment of the present invention, which is only a part of the present invention, and certainly not intended to limit the scope of the present invention. All other embodiments, which can be obtained by a person skilled in the art without inventive step based on the embodiments of the present invention, are within the scope of protection of the present invention.

Claims

1. A method of data transmission, the method comprising:

adding a bearing identifier and a first sequence number to the first data packet to obtain a second data packet; the bearer identifier is used for indicating a radio bearer of the first data packet, and the first sequence number is used for representing a sending sequence of the first data packet;

and sending the second data packet to the first access equipment.

2. The method of claim 1, further comprising:

and sending the first data packet to a second access device.

3. The method of claim 1, wherein the first packet comprises a quality of service flow identifier QFI; the method further comprises the following steps:

and determining the bearing identification according to the QFI.

4. The method of claim 2, wherein the first sequence number is the same as the second sequence number, or wherein the first sequence number is different from the second sequence number;

the second sequence number is a sequence number added to the first data packet by the second access device, and the second sequence number is used for characterizing a sending sequence of the first data packet.

5. The method as claimed in claim 4, wherein the first sequence number is a PDCP sequence number of the first packet, and wherein the first sequence number is used to characterize a transmission order of the first packet in a PDCP layer.

6. The method according to claim 4 or 5, characterized in that the method further comprises:

and acquiring an initial PDCP sequence number, wherein the offset between the first sequence number and the second sequence number is the initial PDCP sequence number.

7. The method according to any one of claims 1-3, further comprising:

and receiving indication information from the second access equipment, wherein the indication information is used for indicating the starting of repeated duty transmission.

8. The method of claim 1, further comprising:

and receiving the first data packet.

9. The method of claim 2, further comprising:

and sending a first message to the second access device, wherein the first message is used for indicating that the second data packet is successfully sent.

10. The method of claim 9, wherein the first message comprises the bearer identification and the first sequence number.

11. The method of claim 2, wherein the first access device is a Wireless Local Area Network (WLAN) communication enabled device and the second access device is a cellular communication enabled device.

12. The method of claim 2, wherein the first access device is a wireless access point wifi ap and the second access device is a residential radio access station PRAS.

13. A method of data transmission, the method comprising:

receiving a second data packet from a first access device, wherein the second data packet comprises a bearing identification, a first sequence number and a first data packet; the bearer identifier is used for indicating a radio bearer of the first data packet, and the first sequence number is used for representing a sending sequence of the first data packet;

14. The method of claim 13, wherein the first packet includes a quality of service flow identifier QFI, and wherein the bearer identification is determined based on the QFI.

15. The method of claim 13, wherein the first sequence number is the same as the second sequence number, or wherein the first sequence number is different from the second sequence number;

the second sequence number is a sequence number added to the first data packet by the second access device, and the second sequence number is used for representing a sending sequence of the first data packet.

16. The method as claimed in claim 15, wherein the first sequence number is a PDCP sequence number of the first packet, and wherein the first sequence number is used to characterize a transmission order of the first packet in a PDCP layer.

17. The method according to claim 15 or 16, characterized in that the method further comprises:

18. The method according to any one of claims 13-16, further comprising:

and sending a second message to a second access device, wherein the second message is used for indicating that the second data packet is successfully received.

19. The method of claim 18, wherein the second message comprises the bearer identification and the first sequence number.

20. The method of claim 18, wherein the first access device is a Wireless Local Area Network (WLAN) communication enabled device and the second access device is a cellular communication enabled device.

21. The method of claim 18, wherein the first access device is a wireless access point WiFiAP and the second access device is a premise radio access station PRAS.

22. A communication apparatus, characterized in that it comprises means for performing the method according to any of claims 1-21.

23. A communications apparatus, comprising a processor;

the processor configured to perform the method of any one of claims 1 to 21.

24. The communications apparatus of claim 23, the communications apparatus further comprising a memory:

the memory for storing a computer program;

the processor, in particular for invoking the computer program from the memory, to perform the method of any of claims 1-21.

25. A chip, characterized in that,

the chip is used for adding a bearing identifier and a first serial number to the first data packet to obtain a second data packet; the bearer identifier is used for indicating a radio bearer of the first data packet, and the first sequence number is used for representing a sending sequence of the first data packet;

the chip is further configured to send the second data packet to the first access device.

26. A chip, characterized in that,

the chip is used for receiving a second data packet from the first access device, wherein the second data packet comprises a bearing identifier, a first sequence number and a first data packet; the bearer identifier is used for indicating a radio bearer of the first data packet, and the first sequence number is used for representing a sending sequence of the first data packet;

the chip is further configured to determine a sending sequence of the first data packet according to the bearer identifier and the first sequence number.

27. The utility model provides a module equipment, its characterized in that, module equipment includes communication module, power module, storage module and chip module, wherein:

the power supply module is used for providing electric energy for the module equipment;

the storage module is used for storing data and instructions;

the communication module is used for carrying out internal communication of module equipment or is used for carrying out communication between the module equipment and external equipment;

the chip module is used for:

and sending the second data packet to the first access equipment.

28. The utility model provides a module equipment, its characterized in that, module equipment includes communication module, power module, storage module and chip module, wherein:

the storage module is used for storing data and instructions;

the chip module is used for: