WO2023015481A1

WO2023015481A1 - Communication method and communication apparatus

Info

Publication number: WO2023015481A1
Application number: PCT/CN2021/112045
Authority: WO
Inventors: 唐骥; 倪伟; 李延冰
Original assignee: 华为技术有限公司
Priority date: 2021-08-11
Filing date: 2021-08-11
Publication date: 2023-02-16
Also published as: CN115968561A

Abstract

The present application provides a communication method and a communication apparatus, the method comprising: a first device sends a first data packet to a second device, the first data packet being a complete header data packet associated with a first service, and the complete header data packet comprising a context ID (CID) and a context; the first device receives first feedback information for the first data packet from a second device, the first feedback information being used to instruct to create the correspondence between a first CID and a first context in the first data packet; and the first device sends a complete header data packet associated with the first service to the second device. In the present application, a compression end (that is, the first device) sends multiple times the complete header data packet to a decompression end (that is, the second device) so to trigger the decompression end to carry out context synchronization, which can prevent the problem of service abnormality caused by contextual errors of the decompression end, and helps to improve the reliability of communication.

Description

Communication method and communication device

technical field

The present application relates to the technical field of communication, and in particular, to a communication method and a communication device.

Background technique

In the 5G system, a 5G local area network (LAN) service is introduced, which supports the transmission of Ethernet services. Among them, the fields included in the Ethernet packet header are mostly static fields (that is, the fields with the same content in the packet headers of all packets of the same Ethernet service flow). Therefore, in order to save transmission overhead, in the third generation In the R16 version (Release16) standard of the partner program (the 3rd generation partnership project, 3GPP), a solution for Ethernet header compression (Ethernet header compress, EHC) is proposed, that is, the static fields in the Ethernet packet header are saved In a context (context), each context corresponds to a context index (context ID, CID), and the compression end and decompression end save the same context information. Therefore, the compression end can use the CID to replace the Ethernet packet header when transmitting Ethernet services, and the decompression end obtains the original packet header from the context according to the CID to restore data. However, the current standard does not define the context consistency detection mechanism between the compression end and the decompression end, that is, when the decompression end fails to decompress (such as context loss, context inconsistency and other reasons lead to decompression failure), it cannot be fed back to the compression end, resulting in business failures. persistent exception. Based on this, how to improve the reliability of EHC transmission has become one of the problems to be solved urgently.

Contents of the invention

The present application provides a communication method and a communication device, which improve the reliability of communication.

In a first aspect, the present application provides a communication method, the method includes: a first device sends a first data packet to a second device, the first data packet is a complete header data packet associated with the first service, The complete header data packet includes a context index and a context; the first device receives first feedback information from the second device for the first data packet, and the first feedback information is used to indicate that the creation is completed Correspondence between the first context index in the first data packet and the first context; the first device sends a complete header data packet associated with the first service to the second device.

In this application, the compression end (i.e. the first device) sends the complete header data packet to the decompression end (i.e. the second device) multiple times (for example, 2 times) to trigger the decompression end to perform context synchronization/update, which can avoid The problem of business abnormality caused by the wrong context of the decompression terminal is beneficial to improve the reliability of communication.

In a possible implementation, the first device sends a complete header data packet associated with the first service to the second device, including:

The first device periodically sends a complete header data packet associated with the first service to the second device.

In this application, the first device periodically sends the complete header data packet to the second device (that is, the first device periodically rolls back, from sending the compressed header data packet to sending the complete header data packet). message header data packet), which can trigger the second device to periodically perform context synchronization/update, which is more conducive to improving the reliability of communication.

In a possible implementation, the first device periodically sends a complete header data packet associated with the first service to the second device, including:

The first device determines a first context index corresponding to the compressed header data packet associated with the first service;

When the first time interval is greater than the preset duration, the first device sends a complete header data packet associated with the first service to the second device, and the first time interval is the first time stamp and The time interval between the second time stamps; the first time stamp is the time stamp when the first device receives the first feedback information, and the second time stamp is the time stamp when the first device determines the The timestamp when the first context was indexed.

In this application, by setting the context timeout time threshold, the complete message header data packet is sent periodically, which is easy to operate and has strong applicability.

In a possible implementation, the method also includes:

When the first time interval is less than or equal to the preset time length, the first device sends the compressed header data packet to the second device.

When the number of compressed header data packets associated with the first service sent by the first device to the second device is greater than a preset number, the first device sends the second device with the A complete header data packet associated with the first service.

In this application, by setting the threshold of sending times, the complete message header data packet is sent periodically, which is easy to implement and has high applicability.

In a possible implementation, the method also includes:

When the sending number is less than or equal to the preset number, the first device sends a compressed header data packet associated with the first service to the second device.

In a possible implementation, after the first device sends the first data packet to the second device, before the first device receives the first feedback information for the first data packet from the second device, the The method also includes:

The first device sends a complete header data packet associated with the first service to the second device.

In this application, after the first device sends the first data packet to the second device, before the first device receives the first feedback information for the first data packet from the second device, it sends a complete header data packet, which does not affect The normal reception of the first service by the second device is conducive to improving service transmission efficiency.

In a second aspect, the present application provides a communication method, the method includes: the second device receives the first data packet from the first device, and the first data packet is a complete header data packet associated with the first service , the complete header data packet includes a context index and a context; the second device sends first feedback information for the first data packet to the first device, and the first feedback information is used to indicate the creation of Complete the correspondence between the first context index and the first context in the first data packet; the second device receives a complete header data packet from the first device and associated with the first service .

In a possible implementation, the second device receives a complete header data packet from the first device and associated with the first service, including:

The second device receives a complete header data packet associated with the first service periodically sent by the first device.

In a possible implementation, after the second device receives the first data packet from the first device, the second device sends the first feedback information for the first data packet to the first device Previously, the method further included:

The second device receives a complete header data packet from the first device and associated with the first service.

In a possible implementation, the method also includes:

The second device updates the context index corresponding to the first service and the correspondence between contexts according to the complete header data packet associated with the first service.

In a third aspect, the present application provides a communication device, the communication device is a first device, and the device includes: a transceiver unit, configured to send a first data packet to a second device, and the first data packet is related to the first device A complete message header data packet associated with a service, the complete message header data packet includes a context index and a context; the transceiver unit is configured to receive first feedback from the second device for the first data packet Information, the first feedback information is used to indicate that the corresponding relationship between the first context index in the first data packet and the first context has been created; the transceiving unit is configured to send the corresponding relationship to the second device A complete header data packet associated with the first service.

In a possible implementation, the transceiving unit is configured to periodically send a complete header data packet associated with the first service to the second device.

In a possible implementation, the device also includes:

A processing unit, configured to determine a first context index corresponding to the compressed header data packet associated with the first service;

The processing unit is further configured to send a complete header data packet associated with the first service to the second device through the transceiver unit when it is determined that the first time interval is greater than a preset duration, and the second A time interval is the time interval between the first time stamp and the second time stamp; the first time stamp is the time stamp when the first device receives the first feedback information, and the second time stamp A timestamp when the first context index is determined for the first device.

In a possible implementation, the processing unit is further configured to, when it is determined that the first time interval is less than or equal to the preset duration, send the compressed message to the second device through the transceiver unit header packet.

In a possible implementation, the device also includes:

A processing unit configured to, when it is determined that the number of compressed header data packets associated with the first service sent to the second device through the transceiver unit is greater than a preset number, send the message to the second device through the transceiver unit The second device sends a complete header data packet associated with the first service.

In a possible implementation, the processing unit is further configured to, when it is determined that the sending number is less than or equal to the preset number, send the first service to the second device through the transceiver unit Associated compressed header packets.

In a possible implementation, after the first device sends the first data packet to the second device, before the first device receives the first feedback information for the first data packet from the second device, the The transceiver unit is also used for:

sending a complete header data packet associated with the first service to the second device.

In a fourth aspect, the present application provides a communication device, the communication device is a second device, and the device includes: a transceiver unit, configured to receive a first data packet from the first device, and the first data packet is related to A complete header data packet associated with the first service, where the complete header data packet includes a context index and a context; the transceiver unit is configured to send a first message for the first data packet to the first device Feedback information, the first feedback information is used to indicate that the corresponding relationship between the first context index in the first data packet and the first context has been created; the transceiving unit is configured to receive information from the first device And a complete header data packet associated with the first service.

In a possible implementation, the transceiving unit is configured to receive a complete header data packet associated with the first service periodically sent by the first device.

In a possible implementation, after the second device receives the first data packet from the first device, the second device sends the first feedback information for the first data packet to the first device Previously, the transceiver unit was used to:

Receive a complete header data packet from the first device and associated with the first service.

In a possible implementation, the device also includes:

A processing unit, configured to update the context index corresponding to the first service and the corresponding relationship between the contexts according to the complete header data packet associated with the first service.

In a fifth aspect, the present application provides a communication device. The device may be the first device, or a device in the first device, or a device that can be matched with the first device. Wherein, the communication device may also be a system on a chip. The communication device can execute the method described in the first aspect. The functions of the communication device may be realized by hardware, or may be realized by executing corresponding software by hardware. The hardware or software includes one or more units or modules corresponding to the above functions. The unit or module can be software and/or hardware. For the operations and beneficial effects performed by the communication device, reference can be made to the method and beneficial effects described in the first aspect above, and repeated descriptions will not be repeated.

In a sixth aspect, the present application provides a communication device, which may be a second device, or a device in the second device, or a device that can be used in conjunction with the second device. Wherein, the communication device may also be a system on a chip. The communication device can execute the method described in the second aspect. The functions of the communication device may be realized by hardware, or may be realized by executing corresponding software by hardware. The hardware or software includes one or more units or modules corresponding to the above functions. The unit or module can be software and/or hardware. For operations and beneficial effects performed by the communication device, reference may be made to the method and beneficial effects described in the second aspect above, and repeated descriptions will not be repeated.

In a seventh aspect, the present application provides a communication device, the communication device includes a processor and a transceiver, and the processor and the transceiver are used to execute at least one computer program or instruction stored in a memory, so that the The device implements the method according to any one of the first aspect to the second aspect.

In an eighth aspect, the present application provides a communication device, the communication device includes a processor, a transceiver, and a memory, and the processor, the transceiver, and the memory are coupled; the processor and the transceiver are used to implement any of the first to second aspects. one method.

In the ninth aspect, the present application provides a computer-readable storage medium, in which computer programs or instructions are stored, and when the computer programs or instructions are executed by the computer, any one of the first to second aspects can be realized. method. In a tenth aspect, the present application provides a computer program product including instructions, the computer program product includes computer program code, when the computer program code is run on a computer, to achieve any one of the first aspect to the second aspect Methods.

Description of drawings

Figure 1a is a schematic diagram of a 5G network architecture;

Figure 1b is a schematic diagram of downlink data transmission between layers;

Figure 1c is a schematic diagram of a CU-DU separation architecture;

Figure 1d is a schematic diagram of another CU-DU separation architecture;

Figure 1e is a schematic diagram of the distribution of an air interface protocol stack;

Fig. 2 is a schematic structural diagram of the EHC message format provided by the embodiment of the present application;

Fig. 3 is a schematic flow chart of EHC message transmission provided by the embodiment of the present application;

FIG. 4 is a schematic flowchart of a communication method provided in an embodiment of the present application;

FIG. 5 is a schematic structural diagram of a communication device provided by an embodiment of the present application;

FIG. 6 is a schematic structural diagram of another communication device provided by an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application.

In the description of the present application, unless otherwise specified, "/" means "or", for example, A/B may mean A or B. The "and/or" in this article is just an association relationship describing associated objects, which means that there can be three relationships, for example, A and/or B, which can mean: A exists alone, A and B exist at the same time, and B exists alone These three situations. In addition, "at least one" means one or more, and "plurality" means two or more. Words such as "first" and "second" do not limit the number and order of execution, and words such as "first" and "second" do not necessarily limit the difference.

In this application, words such as "exemplary" or "for example" are used to mean an example, illustration or description. Any embodiment or design described herein as "exemplary" or "for example" is not to be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete manner.

The technical solution of the embodiment of the present application can be applied to various communication systems, such as: global system of mobile communication (global system of mobile communication, GSM) system, code division multiple access (code division multiple access, CDMA) system, broadband code division multiple access (wideband code division multiple access, WCDMA) system, general packet radio service (general packet radio service, GPRS), long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunications System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) Communication System, Fifth Generation (5G) System or new radio (new radio, NR) and future communication systems, etc., are not limited here.

For ease of understanding, the 5G system in the embodiment of this application is taken as an example, and the network elements related to this application in the 5G system are introduced in detail as follows:

Please refer to FIG. 1a, which is a schematic diagram of a 5G network architecture. As shown in Figure 1a, the network architecture can include terminal equipment, (wireless) access network ((radio) access network, (R)AN), core network (core network, CN) and data network (data network, DN ). Among them, (R)AN (hereinafter referred to as RAN) is used to connect the terminal equipment to the wireless network, and CN is used to manage the terminal equipment and provide a gateway for communicating with the DN.

The terminal equipment, RAN, CN, and DN involved in FIG. 1a will be described in detail below.

1. Terminal equipment

Terminal devices include devices that provide voice and/or data connectivity to a user, and may include, for example, handheld devices with wireless connectivity, or processing devices connected to a wireless modem. The terminal equipment can communicate with the core network via the wireless access network, and the terminal equipment can include user equipment (user equipment, UE), wireless terminal equipment, mobile terminal equipment, and device-to-device communication (device-to-device, D2D) Terminal equipment, vehicle to everything (V2X) terminal equipment, machine-to-machine/machine-type communications (M2M/MTC) terminal equipment, Internet of things (IoT) ) terminal equipment, subscriber unit, subscriber station, mobile station, remote station, access point (access point, AP), remote terminal, access terminal, user terminal, user agent, or user equipment, etc. For example, it may include mobile phones (or "cellular" phones), computers with mobile terminal equipment, portable, pocket, hand-held, computer built-in mobile devices, and the like. For example, personal communication service (PCS) telephone, cordless telephone, session initiation protocol (session initiation protocol, SIP) telephone, wireless local loop (wireless local loop, WLL) station, personal digital assistant (personal digital assistant, PDA), and other devices; it can also include limited devices, such as devices with low power consumption, or devices with limited storage capabilities, or devices with limited computing capabilities.

2. RAN

The RAN may include one or more RAN devices (or access network devices), and the interface between the access network device and the terminal device may be a Uu interface (or called an air interface). Of course, in future communications, the names of these interfaces may remain unchanged, or may be replaced by other names, which is not limited in this application.

An access network device is a node or device that connects a terminal device to a wireless network. For example, the access network device includes but is not limited to: a new generation base station (generation node B, gNB) and an evolved node B ( evolved node B, eNB), next generation evolved node B (next generation eNB, ng-eNB), wireless backhaul equipment, radio network controller (radio network controller, RNC), node B (node B, NB), base station Controller (base station controller, BSC), base transceiver station (base transceiver station, BTS), home base station ((home evolved nodeB, HeNB) or (home node B, HNB)), baseband unit (baseBand unit, BBU), Transmission receiving point (transmitting and receiving point, TRP), transmitting point (transmitting point, TP), mobile switching center, etc.

(1) Protocol layer structure

The communication between the access network device and the terminal device follows a certain protocol layer structure. For example, the control plane protocol layer structure may include radio resource control (radio resource control, RRC) layer, packet data convergence protocol (packet data convergence protocol, PDCP ) layer, radio link control (radio link control, RLC) layer, media access control (media access control, MAC) layer and physical layer; the user plane protocol layer structure can include PDCP layer, RLC layer, MAC layer and physical layer , in a possible implementation, the PDCP layer may further include a service data adaptation protocol (service data adaptation protocol, SDAP) layer.

Taking the data transmission between the access network device and the terminal device as an example, the data transmission needs to go through the user plane protocol layer, such as the SDAP layer, PDCP layer, RLC layer, MAC layer, and physical layer. Among them, the SDAP layer, PDCP layer, The RLC layer, the MAC layer, and the physical layer may also be collectively referred to as an access layer. Exemplarily, at least one data radio bearer (data radio bearer, DRB) is established between the access network device and the terminal device to transmit data, and each DRB may correspond to a set of functional entities, such as including a PDCP layer entity, the At least one RLC layer entity corresponding to the PDCP layer entity, at least one MAC layer entity corresponding to the at least one RLC layer entity, and at least one physical layer entity corresponding to the at least one MAC layer entity. It should be noted that at least one signaling radio bearer (Signalling radio bearer, SRB) can also be established between the access network device and the terminal device to transmit signaling, and the DRB and the SRB can be collectively called a radio bearer (radio bearer, RB). .

Downlink data transmission is taken as an example. FIG. 1b is a schematic diagram of downlink data transmission between layers. The downward arrow in FIG. 1b indicates data transmission, and the upward arrow indicates data reception. After the SDAP layer entity obtains the data from the upper layer, it can map the data to the PDCP layer entity of the corresponding DRB according to the QoS flow indicator (QFI) of the data, and the PDCP layer entity can transmit the data to at least one corresponding to the PDCP layer entity. An RLC layer entity is further transmitted by at least one RLC layer entity to the corresponding MAC layer entity, and then the MAC layer entity generates a transmission block, and then performs wireless transmission through the corresponding physical layer entity. The data is encapsulated correspondingly in each layer. The data received by a certain layer from the upper layer of the layer is regarded as the service data unit (service data unit, SDU) of the layer, which becomes a protocol data unit (protocol data unit) after layer encapsulation. unit, PDU), and then passed to the next layer. For example, the data received by the PDCP layer entity from the upper layer is called PDCP SDU, and the data sent by the PDCP layer entity to the lower layer is called PDCP PDU; the data received by the RLC layer entity from the upper layer is called RLC SDU, and the data sent by the RLC layer entity to the lower layer It is called RLC PDU. Among them, data can be transmitted between different layers through corresponding channels, for example, data can be transmitted between RLC layer entities and MAC layer entities through a logical channel (logical channel, LCH), and between MAC layer entities and physical layer entities can be transmitted through Transport channel (transport channel) to transmit data.

Exemplarily, according to FIG. 1b, it can also be seen that the terminal device also has an application layer and a non-access layer; wherein, the application layer can be used to provide services to applications installed in the terminal device, for example, the received Downlink data can be sequentially transmitted from the physical layer to the application layer, and then provided to the application program by the application layer; for another example, the application layer can obtain the data generated by the application program, and transmit the data to the physical layer in sequence, and send it to other communication devices. The non-access layer can be used to forward user data, such as forwarding uplink data received from the application layer to the SDAP layer or forwarding downlink data received from the SDAP layer to the application layer.

(2) CU and DU

In the embodiment of the present application, the access network device may include one or more centralized units (centralized unit, CU) and one or more distributed units (distributed unit, DU), and multiple DUs may be centrally controlled by one CU. As an example, the interface between the CU and the DU may be called an F1 interface, where a control plane (control panel, CP) interface may be F1-C, and a user plane (user panel, UP) interface may be F1-U. The CU and DU can be divided according to the protocol layer of the wireless network: for example, please refer to FIG. 1c, which is a schematic diagram of a CU-DU separation architecture. As shown in Figure 1c, the functions of the protocol layers above the PDCP layer are set in the CU, and the functions of the protocol layers below the PDCP layer (such as the RLC layer and MAC layer, etc.) are set in the DU.

It can be understood that the above-mentioned division of the processing functions of CU and DU according to the protocol layer is only an example, and it can also be divided according to other methods. For example, the functions of the protocol layers above the RLC layer are set in the CU, the RLC layer and the following protocol layers. The functions of the DU are set in the DU, and for example, the CU or DU can be divided into functions with more protocol layers, and for example, the CU or DU can also be divided into partial processing functions with protocol layers. In one design, part of the functions of the RLC layer and the functions of the protocol layers above the RLC layer are set in the CU, and the rest of the functions of the RLC layer and the functions of the protocol layers below the RLC layer are set in the DU. In another design, the functions of the CU or DU can also be divided according to the business type or other system requirements, for example, according to the delay, and the functions whose processing time needs to meet the delay requirement are set in the DU, which does not need to meet the delay The required feature set is in the CU. In another design, the CU may also have one or more functions of the core network. For example, the CU can be set on the network side to facilitate centralized management; the DU can have multiple radio functions, or the radio functions can be remotely set. This embodiment of the present application does not limit it.

Exemplarily, the function of the CU may be implemented by one entity, or may also be implemented by different entities. For example, please refer to FIG. 1d, which is a schematic diagram of another CU-DU separation architecture. As shown in Figure 1d, the functions of the CU can be further divided, that is, the control plane and the user plane are separated and realized by different entities, which are the control plane CU entity (ie, the CU-CP entity) and the user plane CU entity (ie, the CU-CP entity). CU-UP entity), the CU-CP entity and the CU-UP entity can be coupled with the DU to jointly complete the functions of the RAN device. The interface between CU-CP entity and CU-UP entity can be E1 interface, the interface between CU-CP entity and DU can be F1-C interface, and the interface between CU-UP entity and DU can be F1-U interface. Among them, one DU and one CU-UP can be connected to one CU-CP. Under the control of the same CU-CP, one DU can be connected to multiple CU-UPs, and one CU-UP can be connected to multiple DUs.

Based on Fig. 1e, Fig. 1e is a schematic diagram of distribution of an air interface protocol stack. As shown in Figure 1e, for both the user plane and the control plane, the air interface protocol stack can be RLC, MAC, and PHY in the DU, and PDCP and above protocol layers in the CU.

It should be noted that: in the architecture shown in FIG. 1c to FIG. 1e above, the signaling generated by the CU can be sent to the terminal device through the DU, or the signaling generated by the terminal device can be sent to the CU through the DU. The DU can directly encapsulate the signaling through the protocol layer and transparently transmit it to the terminal device or CU without parsing the signaling. In the following embodiments, if the signaling is transmitted between the DU and the terminal device, at this time, the sending or receiving of the signaling by the DU includes this scenario. For example, signaling at the RRC or PDCP layer will eventually be processed as data at the physical layer and sent to the terminal device, or converted from received data at the physical layer. Under this framework, the signaling at the RRC or PDCP layer can also be considered to be sent by the DU, or sent by the DU and the radio frequency device.

3. CN

The CN may include one or more CN devices. Taking the 5G communication system as an example, the CN may include access and mobility management function (access and mobility management function, AMF) network elements, session management function (session management function, SMF) ) network element, user plane function (UPF) network element, policy control function (PCF) network element, unified data management (unified data management, UDM) network element, application function (application function, AF) ) Network elements, etc.

The AMF network element is a control plane network element provided by the operator network, responsible for access control and mobility management of terminal equipment accessing the operator network, such as including mobility status management, assigning temporary user IDs, authenticating and authorizing users, etc. .

The SMF network element is a control plane network element provided by the operator network, and is responsible for managing the PDU session of the terminal device. A PDU session is a channel for transmitting PDUs, and terminal equipment needs to transmit PDUs with DN through the PDU session. The PDU session is established, maintained and deleted by the SMF network element. SMF network elements include session management (such as session establishment, modification and release, including tunnel maintenance between UPF and RAN), selection and control of UPF network elements, service and session continuity (service and session continuity, SSC) mode selection, Session-related functions such as roaming.

The UPF network element is the gateway provided by the operator, and is the gateway for communication between the operator's network and the DN. UPF network elements include data packet routing and transmission, packet inspection, quality of service (QoS) processing, lawful interception, uplink packet detection, downlink data packet storage and other user-plane-related functions.

The PCF network element is a control plane function provided by the operator, and is used to provide the policy of the PDU session to the SMF network element. Policies may include accounting-related policies, QoS-related policies, and authorization-related policies.

The AF network element is a functional network element that provides various business services, can interact with the core network through other network elements, and can interact with the policy management framework for policy management.

In addition, although not shown, the CN may also include other possible network elements, such as network exposure function (network exposure function, NEF), network element unified data repository (unified data repository, UDR) network element.

It should be noted that, in the embodiment of the present application, the access network device and the core network device may be collectively referred to as a network device.

4. DN

DN can also be called packet data network (packet data network, PDN), which is a network located outside the operator's network. The operator's network can access multiple DNs, and application servers corresponding to various services can be deployed in the DN. End devices offer a wide variety of possible services.

In Fig. 1a, Npcf, Nudm, Naf, Namf, Nsmf, N1, N2, N3, N4, and N6 are interface serial numbers. For the meanings of these interface serial numbers, refer to the meanings defined in relevant standard protocols, and there is no limitation here.

It can be understood that the 5G communication system is taken as an example in Fig. 1a, and the solutions in the embodiments of the present application can also be applied to other possible communication systems, such as LTE communication systems or future sixth generation (the 6th generation) generation, 6G) communication system. The foregoing network element or function may be a network element in a hardware device, or a software function running on dedicated hardware, or a virtualization function instantiated on a platform (for example, a cloud platform). Optionally, the foregoing network element or function may be implemented by one device, or jointly implemented by multiple devices, or may be a functional module in one device, which is not specifically limited in this embodiment of the present application.

The relevant technical features involved in the embodiments of the present application are explained below. It should be noted that these explanations are for the purpose of making the embodiments of the present application easier to understand, and should not be regarded as limiting the scope of protection required by the present application.

1. Ethernet header compression (ethernet header compress, EHC)

Among them, in the 5G system, the 5G LAN service is introduced, which supports the transmission of Ethernet services. Among them, the fields included in the Ethernet message header are mostly static fields (that is, in the message headers (or described as data packet headers) of all messages (or described as data packets) of the same Ethernet service flow, the contents are the same field), therefore, in order to save transmission overhead, the EHC solution is proposed, that is, the static fields in the Ethernet packet header are stored in a context (context), and each context corresponds to a context index (context ID, CID ), the compression side and the decompression side save the same context information. Therefore, the compression end can use the CID to replace the Ethernet packet header when transmitting Ethernet services, and the decompression end obtains the original packet header (or described as a complete message header) for data recovery. Generally speaking, the fields that can be compressed in the Ethernet packet header are shown in Table 1 below:

Table 1

2. EHC message

Among them, EHC is usually performed at the PDCP layer, that is, EHC is a function defined at the PDCP layer, which is configured based on the DRB granularity, and is delivered by the access network device to the terminal device through the air interface. Among them, the EHC message has two formats, namely a full header (full header, FH) format and a compressed message header (compress header, CH) format. Wherein, FH represents an uncompressed message, and CH represents a compressed message.

For example, please refer to FIG. 2 . FIG. 2 is a schematic structural diagram of an EHC message format provided by an embodiment of the present application. As shown in Figure 2, a complete message header data packet (FH Packet) includes an EHC header (EHC header), an Ethernet header (ETH header) and a data (data) part. The compressed header data packet (CHPacket) includes an EHC header (EHCheader) and a data (data) part. That is to say, the DRB with the EHC function enabled must encapsulate an additional layer of EHC header (EHC header) when sending data. For example, please refer to FIG. 2 together. The EHC header shown in FIG. 2 consists of two fields, which are respectively a type (Type) field and a context index (CID) field. Wherein, the Type field is used to indicate that the EHC message is a message of FH type (FH message for short), or a message of CH type (CH message for short).

For easy understanding, please refer to FIG. 3 , which is a schematic flow chart of EHC message transmission provided by the embodiment of the present application. As shown in Figure 3, before the data is sent, the compressor can first extract the message characteristics (or be described as Ethernet message characteristics) of the Ethernet message to be sent, and perform context matching (or be described as extracting the Ethernet message feature). Network packet characteristics are matched against existing/existing contexts). Wherein, the characteristics of the Ethernet packet may include destination address, source address, information in fields such as Q-TAG and LENGTH/TYPE. Wherein, the existing/existing context can be understood as the context saved/created/established in the compression end. Wherein, if the extracted feature of the Ethernet packet matches the value of each field included in any context in the existing context, it is considered as a hit, otherwise it is considered as not a hit. Generally speaking, if the context is hit/matched, its CID will be obtained. If the context is not hit (or described as not matching the context), a new CID will be applied to save the message characteristics (that is, create the context).

Among them, if the compression end does not hit/match the context when performing context matching, the compression end can send an FH type message (ie FH message) to the decompression end, wherein, if the decompression end receives the FH type message , then obtain the CID in the FH message, and extract information such as the complete message header of the Ethernet (that is, the characteristics of the Ethernet message) for creating/saving the context, and send feedback information (feedback) to the compression end, wherein the feedback information Including CID and other information, therefore, when the compression end receives the feedback information sent from the decompression end, the compression end can determine that the decompression end has established the context corresponding to the CID according to the CID included/carried in the received feedback information , that is, the decompression end (successfully) establishes the context corresponding to the CID. Subsequently, the compression end can send a message of the CH type to the decompression end.

Wherein, if the compression end successfully matches the corresponding context when performing context matching, then obtains the corresponding CID, and sends a message of CH type (that is, a CH message) to the decompression end. Wherein, the CH message includes information such as CID. Therefore, if the decompression end receives a message of the CH type, it can extract the CID in the CH message, and query the corresponding context information according to the extracted CID to decompress the CH message.

It is understandable that the current standard does not define the context consistency detection mechanism between the compression end and the decompression end, that is, when the decompression end fails to decompress, it cannot be fed back to the compression end, resulting in continuous abnormal business. Generally speaking, the reasons for decompression failure at the decompression end may include context loss, context inconsistency, etc. The reasons for context errors at the decompression end may be bit errors during air interface transmission, or operations such as active context reset at the decompression end. Do limit. Based on this, how to improve the reliability of EHC transmission has become one of the problems to be solved urgently.

Wherein, the method in the embodiment of the present application is not limited to the compressed transmission of the header part of the data packet, but also can be applied to the compressed transmission of the data part of the data packet, or can also be applied to the entire data packet (that is, the header part and the Data part) compressed transmission, etc., are not limited here. For the convenience of description, the embodiments of the present application all take the compressed transmission of the header part of the data packet as an example for schematic illustration.

Among them, the solution provided by this application can be applied to uplink transmission or downlink transmission, wherein, in downlink transmission, the compression end can be an access network device, the decompression end can be a terminal device, and in uplink transmission, the compression end can be a terminal device , the decompression end is the access network device. For convenience of description, in the following embodiments, the compression end may be described as the first device, and the decompression end may be described as the second device. Wherein, the decompression end described in the embodiment of the present application may also be described as a decompression end, etc., which is not limited here.

Wherein, the message described in the embodiment of the present application may also be described as a data packet, etc., which is not limited here. The complete header data packet described in the embodiment of the present application may also be described as a data packet/message with an uncompressed header, or as an FH packet, etc., which is not limited here. The compressed header data packet described in the embodiment of this application can also be described as a data packet/message with a compressed header, or it can also be described as a header compressed data packet, or it can also be described as a compressed packet, or it can be described as CH Messages, etc., are not limited here. The context described in this application may also be described as a packet header compression context, or may also be described as a header compression context, or may also be described as context or context information, etc., which are not limited here. The context index described in this application may also be described as a context identifier, or as an index or identifier, etc., which is not limited here.

The embodiment of the present application proposes a communication method, which can improve communication reliability. The communication method and communication device provided by this application are introduced in detail below:

Please refer to FIG. 4 . FIG. 4 is a schematic flowchart of a communication method provided by an embodiment of the present application. As shown in Figure 4, the communication method includes the following steps S401-S402, the method execution body shown in Figure 4 may be the first device, or the method execution body shown in Figure 4 may also be a chip in the first device, etc. , without limitation here. For convenience of description, the first device will be used as an example for description below.

S401. The first device sends a first data packet to the second device.

In some feasible implementation manners, the first device sends the first data packet to the second device, and the first data packet is a complete header data packet associated with the first service, wherein the complete header data packet includes the context index and context. Wherein, the above-mentioned complete message header data packet can also be understood as an FH type message, or an FH message, etc., and there is no limitation here. In this application, the service data transmitted based on the first radio bearer may be described as the first service. Wherein, one service corresponds to one CID. In this application, the first service may be a unicast service, or may also be a multicast service (such as live broadcast service, public safety service, batch software update service, etc.), which is determined according to the actual application scenario, and is not limited here .

Specifically, when the first device needs to send data to the second device through the first radio bearer, the first device can first extract the packet features of the data to be sent, and perform context matching (or describe as combining the extracted packet features with existing/existing context to match). The message features may include field information such as destination address, source address, Q-TAG, and LENGTH/TYPE. Understandably, if the existing context of the first device does not match the corresponding context, the first device may create/apply for a new CID, and store/save the new CID in association with the extracted message characteristics , further, the first device sends a first data packet to the second device, where the first data packet includes the CID and the context. Wherein, the context involved in the embodiment of the present application may be understood as information such as message features, and no limitation is set here.

S402. The first device receives first feedback information for the first data packet from the second device.

In some feasible implementation manners, after the second device receives the first data packet from the first device, the second device can obtain information such as CID and context included in the first data packet, and compare the CID and the corresponding The context is associatively stored/saved. Further, the second device sends feedback information for the first data packet (for convenience of description, hereinafter referred to as first feedback information) to the first device, where the first feedback information is used to instruct the second device to (successfully) establish a corresponding context. That is to say, for the second device, when the second device receives the FH message from the first device, for example, the FH message can be the first data packet, regardless of whether the second device exists in the FH message or not. For the context corresponding to the included CID, the second device needs to save the latest parsed content into the context, and feed back feedback to the first device. Wherein, each feedback includes CID and other information, therefore, when the first device receives the first feedback information of the second device for the first data packet, the first device can determine according to the first feedback information that the second device has sent the The corresponding context is established, or it is described that the first device can determine that the second device has updated the corresponding context according to the first feedback information, or it can be described that the first device can determine that the second device has implemented the Synchronization of the context corresponding to the CID between the first devices.

Optionally, in order not to affect the normal transmission of the first service, after the first device sends the first data packet to the second device and before the first device receives the first feedback information for the first data packet from the second device, if If the first device needs to send a data packet, the first device may send the data packet with an uncompressed header to the second device. That is to say, the first device may send a complete header data packet associated with the first service to the second device.

S403. The first device sends a complete header data packet associated with the first service to the second device.

In some feasible implementation manners, in order to avoid context inconsistency/out-of-synchronization between the second device and the first device, the first device may send the first data packet to the second device, or the first device may receive the After receiving the first feedback information of the first data packet from the second device, the first device sends (again or multiple times) a complete header data packet associated with the first service to the second device.

In a feasible implementation manner, the first device may periodically send a complete header data packet associated with the first service to the second device. That is to say, the first device can periodically roll back, from sending a compressed header data packet (ie CH message) to sending a complete message header data packet (ie FH message), so as to trigger the second Devices perform context synchronization. For example, after the first device sends a complete header data packet to the second device and receives feedback information about the complete header data packet from the second device, it sends the second device every 1 second. The device sends a complete header data packet once; for another example, the first device may send a complete header data packet to the second device, and after receiving the feedback information from the second device for the complete header data packet, the subsequent Each time it is determined that the first device sends the compressed header data packet to the second device n times, it sends the complete header data packet to the second device again.

Optionally, the first device may also aperiodically send a complete header data packet associated with the first service to the second device, for example, the first device may send a complete header data packet to the second device, And after receiving the feedback information from the second device for the complete header data packet, first send the complete header data packet to the second device at an interval of △t1 seconds, followed by intervals of △t2 seconds, △t3 seconds, and △t4 seconds Wait and then send the complete header data packet to the second device, where the values of △t1, △t2, △t3 and △t4 can be completely different, or partly different, or, △t1, △t2 , △t3 and △t4 can satisfy a certain relationship, which is determined according to the actual application scenario, and is not limited here.

Optionally, after receiving the first feedback information from the second device for the first data packet, the first device may send the same complete header data packet to the second device n consecutive times, so as to trigger the second device to perform Context synchronization, where n is an integer greater than or equal to 1.

For the convenience of understanding, the following embodiments of the present application all take the first device periodically sending a complete header data packet associated with the first service to the second device as an example for schematic illustration.

Specifically, that the first device periodically sends the complete header data packet associated with the first service to the second device may be understood as: the first device determines the first packet corresponding to the compressed header data packet associated with the first service. Context index, when the first time interval is greater than the preset duration, the first device sends a complete header data packet associated with the first service to the second device; when the first time interval is less than or equal to the preset duration, the first The device sends the compressed header data packet to the second device. Wherein, the first time interval is the time interval between the first time stamp and the second time stamp, the first time stamp is the time stamp when the first device receives the first feedback information, and the second time stamp is determined by the first device The timestamp when the first context was indexed. Understandably, it may also be that when the first time interval is greater than or equal to the preset duration, the first device sends a complete header data packet associated with the first service to the second device, and when the first time interval is less than the preset duration When , the first device sends the compressed header data packet to the second device, which is not limited here. For the convenience of description, in this embodiment of the present application, when the first time interval is equal to the preset time length, the first device sends a compressed header data packet to the second device as an example for illustration. That is to say, the first device can set the context timeout time (that is, the preset duration), wherein when the first device sends the FH message and receives the feedback information (feedback), it reads the current system time and records it as the first a timestamp. Check the current time (that is, the second timestamp) each time the context index corresponding to the data to be sent is determined. If the time interval between the second timestamp and the first timestamp exceeds (that is, is greater than) the context timeout time , then (re)send the FH message to trigger the second device to update the context. Otherwise, send a CH message, that is, if the time interval between the second timestamp and the first timestamp does not exceed (that is, be less than or equal to) the context timeout time, then send a CH message.

During specific implementation, the first device can set a feedback information flag (feedbackFlag) for each context. When the feedbackFlag is false, it means that the corresponding context has not yet been established/has not been established in the second device. Therefore, the first The device needs to send a complete message header data packet (that is, an FH message) to the second device. When the feedbackFlag is true, it means that the corresponding context has been established/has been established in the second device, so it is necessary to further determine the compression to be sent The time interval between the second time stamp corresponding to the header data packet and the first time stamp of the last received feedback information, and judge the size of the time interval and the preset time length, if the time interval is greater than the preset time interval time, then set the feedbackFlag to false, and send the complete header data packet to the second device, if the time interval is less than or equal to the preset duration, then send the compressed header data packet to the second device.

Optionally, that the first device periodically sends the complete header data packet associated with the first service to the second device can also be understood as: when the first device sends the compressed packet associated with the first service to the second device When the number of sent header data packets is greater than the preset number, the first device sends the complete header data packets associated with the first service to the second device; when the sent number is less than or equal to the preset number, the first device sends the second device The second device sends the compressed header data packet associated with the first service. Understandably, it may also be that when the number of compressed header data packets associated with the first service sent by the first device to the second device is greater than or equal to the preset number, the first device sends the second device to the second device. A complete header data packet associated with a service; when the number sent is less than the preset number, the first device sends a compressed header data packet associated with the first service to the second device, which is not limited here. For the convenience of description, this embodiment of the present application uses an example in which the first device sends compressed header data packets to the second device when the number of compressed header data packets sent is equal to the preset number for illustration. That is to say, the first device may set a corresponding compressed packet sending threshold (that is, a preset number), wherein, when the first device determines that the number of continuously sent CH messages exceeds (that is, is greater than) the compressed packet sending threshold value, the first device (re)sends the FH message to trigger the second device to update the context. Otherwise, the first device continues to send CH messages, that is, when the first device determines that the number of FH messages sent continuously does not exceed (that is, is less than or equal to) the threshold value for sending compressed packets, the first device sends CH messages to the second device. message.

During specific implementation, the first device may set a feedback information flag (feedbackFlag) and a CH_cnt field for each context, where the CH_cnt field indicates the number of continuously sent CH messages. Wherein, when the feedbackFlag is false, it means that the corresponding context has not been established/has not been established in the second device, therefore, the first device needs to send a complete message header data packet (ie FH message) to the second device . When the feedbackFlag is true, it means that the corresponding context has been established/has been established in the second device, so it is necessary to further determine which compressed message to send is the compressed message header data packet (ie CH message) to be sent Header data (that is, read the value of the CH_cnt field). Wherein, when the value of the CH_cnt field does not exceed (that is, less than or equal to) the threshold value (that is, the preset number), the first device may send the compressed header data packet to the second device, and when the value of the CH_cnt field exceeds ( That is, when it is greater than) the threshold value, the first device needs to set the feedbackFlag to false, and set the value of the CH_cnt field to 0, and send an FH type message (that is, a complete message header data packet) to the second device, and wait again Feedback from decompressor.

In the embodiment of this application, context synchronization is actively triggered by the compression end (that is, the first device in this application), which can ensure the consistency of the context between the compression end and the decompression end (that is, the second device in this application), and avoid A business exception caused by an error in the end context.

The communication device provided by the present application will be described in detail below with reference to FIG. 5 to FIG. 6 .

Please refer to FIG. 5 . FIG. 5 is a schematic structural diagram of a communication device provided by an embodiment of the present application. The communication apparatus shown in FIG. 5 may be used to perform some or all functions of the first device in the method embodiment described in FIG. 4 above. The device may be the first device, or a device in the first device, or a device that can be matched with the first device. Wherein, the communication device may also be a system on a chip. The communication device shown in FIG. 5 may include a transceiver unit 501 and a processing unit 502 . Wherein, the processing unit 502 is configured to perform data processing. The transceiver unit 501 is integrated with a receiving unit and a sending unit. The transceiver unit 501 may also be called a communication unit. Alternatively, the transceiver unit 501 may also be split into a receiving unit and a sending unit. The processing unit 502 below is the same as the transceiver unit 501 , and will not be described in detail below. in:

In one implementation manner, the transceiver unit 501 is configured to send a first data packet to the second device, the first data packet is a complete header data packet associated with the first service, and the complete header data The packet includes a context index and a context; the transceiving unit 501 is configured to receive first feedback information for the first data packet from the second device, and the first feedback information is used to indicate that the creation of the first data packet is completed Correspondence between the first context index in the data packet and the first context; the transceiving unit 501 is configured to send a complete header data packet associated with the first service to the second device.

Optionally, the transceiving unit 501 is further configured to periodically send a complete header data packet associated with the first service to the second device.

Optionally, the device further includes: a processing unit 502, configured to determine a first context index corresponding to the compressed header data packet associated with the first service; When a time interval is greater than the preset time length, the complete header data packet associated with the first service is sent to the second device through the transceiver unit 501, and the first time interval is the first time stamp and the second time stamp. The time interval between two time stamps; the first time stamp is the time stamp when the first device receives the first feedback information, and the second time stamp is the time stamp when the first device determines the first feedback information A timestamp when the context was indexed.

Optionally, the processing unit 502 is further configured to send the compressed packet header to the second device through the transceiver unit 501 when it is determined that the first time interval is less than or equal to the preset duration data pack.

Optionally, the apparatus further includes: a processing unit 502, configured to determine that the number of compressed header data packets associated with the first service sent to the second device through the transceiver unit 501 is greater than When the number is preset, send a complete header data packet associated with the first service to the second device through the transceiver unit 501 .

Optionally, the processing unit 502 is further configured to, when it is determined that the sending quantity is less than or equal to the preset quantity, send the information associated with the first service to the second device through the transceiver unit 501 Compress header packets.

Optionally, after the first device sends the first data packet to the second device, before the first device receives first feedback information from the second device for the first data packet, the transceiving unit 501 It is also used for: sending a complete header data packet associated with the first service to the second device.

For other possible implementations of the communication device, refer to the relevant description of the functions of the access network device in the method embodiment corresponding to FIG. 4 above, which will not be repeated here.

Please refer to FIG. 5 together. FIG. 5 shows a schematic structural diagram of a communication device according to an embodiment of the present application. The communication apparatus shown in FIG. 5 may be used to execute some or all functions of the second device in the method embodiment described in FIG. 4 above. The device may be the second device, or a device in the second device, or a device that can be matched with the second device. Wherein, the communication device may also be a system on a chip. The communication device shown in FIG. 5 may include a transceiver unit 501 and a processing unit 502 . in:

In one implementation, the transceiver unit 501 is configured to receive a first data packet from the first device, the first data packet is a complete packet header data packet associated with the first service, and the complete packet header The data packet includes a context index and a context; the transceiving unit 501 is configured to send first feedback information for the first data packet to the first device, and the first feedback information is used to indicate that the creation of the first A correspondence between the first context index and the first context in a data packet; the transceiving unit 501 is configured to receive a complete header data packet from the first device and associated with the first service.

Optionally, the transceiving unit 501 is further configured to receive a complete header data packet associated with the first service periodically sent by the first device.

Optionally, after the second device receives the first data packet from the first device, before the second device sends the first feedback information for the first data packet to the first device, the The transceiving unit 501 is configured to: receive a complete header data packet from the first device and associated with the first service.

Optionally, the apparatus further includes: a processing unit 502, configured to update a context index corresponding to the first service and a correspondence between contexts according to a complete header data packet associated with the first service.

For other possible implementation manners of the communication apparatus, reference may be made to the relevant description of the functions of the access network device in the method embodiment corresponding to FIG. 4 above, which will not be repeated here.

Please refer to FIG. 6 . FIG. 6 is a schematic structural diagram of another communication device provided by an embodiment of the present application. As shown in FIG. 6 , a communication device provided by an embodiment of the present application is used to realize the functions of the target access network device in FIG. 4 above. The apparatus may be a target access network device or an apparatus for the target access network device. The apparatus for the target access network device may be a chip system or a chip in the target access network device. Wherein, the system-on-a-chip may consist of chips, or may include chips and other discrete devices.

Alternatively, the communication device is configured to realize the functions of the first terminal device (terminal device for short) in FIG. 4 above. The device may be a terminal device or a device for a terminal device. The apparatus for a terminal device may be a chip system or a chip in the terminal device.

The communication device includes at least one processor 620, configured to implement the data processing function of the target access network device or terminal device in the method provided by the embodiment of the present application. The apparatus may also include a communication interface 610, configured to implement the transceiving operation of the target access network device or terminal device in the method provided by the embodiment of the present application. In the embodiment of the present application, the communication interface may be a transceiver, a circuit, a bus, a module or other types of communication interfaces for communicating with other devices through a transmission medium. For example, the communication interface 610 is used by the device in the device to communicate with other devices. The processor 620 uses the communication interface 610 to send and receive data, and is used to implement the method described in FIG. 4 of the above method embodiment.

The apparatus may also include at least one memory 630 for storing program instructions and/or data. The memory 630 is coupled to the processor 620 . The coupling in the embodiments of the present application is an indirect coupling or a communication connection between devices, units or modules, which may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules. Processor 620 may cooperate with memory 630 . Processor 620 may execute program instructions stored in memory 630 . At least one of the at least one memory may be included in the processor.

When the device is turned on, the processor 620 can read the software program in the memory 630, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be sent wirelessly, the processor 620 performs baseband processing on the data to be sent, and then outputs the baseband signal to the radio frequency circuit (not shown in the figure), and the radio frequency circuit performs radio frequency processing on the baseband signal, and passes the radio frequency signal through the antenna in the form of electromagnetic waves Send out. When data is sent to the device, the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor 620, and the processor 620 converts the baseband signal into data and processes the data .

In another implementation, the radio frequency circuit and antenna can be set independently from the processor 620 for baseband processing. layout.

In this embodiment of the present application, a specific connection medium among the communication interface 610, the processor 620, and the memory 630 is not limited. In the embodiment of the present application, in 6, the memory 630, the processor 620, and the communication interface 610 are connected through the bus 640, and the bus is represented by a thick line in 6, and the connection mode between other components is only for schematic illustration, and Do not limit yourself. The bus can be divided into address bus, data bus, control bus and so on. For ease of representation, only one thick line is used in 6, but it does not mean that there is only one bus or one type of bus.

When the device is specifically a device for access network equipment, terminal equipment, or core network equipment, for example, when the device is specifically a chip or a chip system, what the communication interface 610 outputs or receives may be a baseband signal. When the device is specifically an access network device, a terminal device, or a core network device, what the communication interface 610 outputs or receives may be a radio frequency signal. In this embodiment of the application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or Execute the methods, operations and logic block diagrams disclosed in the embodiments of the present application. A general purpose processor may be a microprocessor or any conventional processor or the like. The operations of the method disclosed in the embodiments of the present application may be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor.

The embodiment of the present application also provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the instruction is run on a processor, the method flow of the above-mentioned method embodiment is realized.

The embodiment of the present application further provides a computer program product. When the computer program product is run on a processor, the method flow of the above method embodiment is implemented.

It should be noted that for the foregoing method embodiments, for the sake of simple description, they are expressed as a series of action combinations, but those skilled in the art should know that the present application is not limited by the described action sequence. Because of this application, certain operations may be performed in other orders or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification belong to preferred embodiments, and the actions and modules involved are not necessarily required by this application.

The descriptions of the various embodiments provided in this application can refer to each other, and the descriptions of each embodiment have their own emphases. For the parts that are not described in detail in a certain embodiment, you can refer to the relevant descriptions of other embodiments. For the convenience and brevity of description, for example, regarding the functions and operations of the various devices and devices provided in the embodiments of the present application, reference may be made to the relevant descriptions of the method embodiments of the present application. May be cross-referenced, combined or cited.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and are not intended to limit it; although the application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: It is still possible to modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements for some or all of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the technical solutions of the various embodiments of the present application. scope.

Claims

A communication method, characterized in that the method comprises:

The first device sends a first data packet to the second device, where the first data packet is a complete header data packet associated with the first service, and the complete header data packet includes a context index and a context;

The first device receives first feedback information for the first data packet from the second device, where the first feedback information is used to indicate that the first context index and the second context index in the first data packet are created and completed. Correspondence between contexts;

The first device sends a complete header data packet associated with the first service to the second device.
The method according to claim 1, wherein the first device sends a complete header data packet associated with the first service to the second device, comprising:

The first device periodically sends a complete header data packet associated with the first service to the second device.
The method according to claim 2, wherein the first device periodically sends a complete header data packet associated with the first service to the second device, including:

The first device determines a first context index corresponding to the compressed header data packet associated with the first service;

When the first time interval is greater than the preset duration, the first device sends a complete header data packet associated with the first service to the second device, and the first time interval is the first time stamp and The time interval between the second time stamps; the first time stamp is the time stamp when the first device receives the first feedback information, and the second time stamp is the time stamp when the first device determines the The timestamp when the first context was indexed.
The method according to claim 3, further comprising:

When the first time interval is less than or equal to the preset time length, the first device sends the compressed header data packet to the second device.
The method according to claim 2, wherein the first device periodically sends a complete header data packet associated with the first service to the second device, including:

When the number of compressed header data packets associated with the first service sent by the first device to the second device is greater than a preset number, the first device sends the second device with the A complete header data packet associated with the first service.
The method according to claim 5, wherein the method further comprises:

When the sending number is less than or equal to the preset number, the first device sends a compressed header data packet associated with the first service to the second device.
The method according to any one of claims 1-6, wherein after the first device sends the first data packet to the second device, the first device receives a Before the first feedback information of the data packet, the method also includes:

The first device sends a complete header data packet associated with the first service to the second device.
A communication method, characterized in that the method comprises:

The second device receives the first data packet from the first device, the first data packet is a complete header data packet associated with the first service, and the complete header data packet includes a context index and a context;

The second device sends first feedback information for the first data packet to the first device, where the first feedback information is used to indicate that the creation of the first context index and the second context index in the first data packet is completed. Correspondence between contexts;

The second device receives a complete header data packet from the first device and associated with the first service.
The method according to claim 8, wherein the second device receives a complete header data packet from the first device and associated with the first service, comprising:

The second device receives a complete header data packet associated with the first service periodically sent by the first device.
The method according to claim 8 or 9, characterized in that, after the second device receives the first data packet from the first device, the second device sends the first data packet to the first device Before the first feedback information of the data packet, the method also includes:

The second device receives a complete header data packet from the first device and associated with the first service.
The method according to any one of claims 8-10, wherein the method further comprises:

The second device updates the context index corresponding to the first service and the correspondence between contexts according to the complete header data packet associated with the first service.
A communication device, characterized in that the device is a first device, and the device includes:

A transceiver unit, configured to send a first data packet to the second device, the first data packet is a complete header data packet associated with the first service, and the complete header data packet includes a context index and a context;

The transceiving unit is configured to receive first feedback information from the second device for the first data packet, where the first feedback information is used to indicate that the first context index in the first data packet has been created and the correspondence between the first context;

The transceiving unit is configured to send a complete header data packet associated with the first service to the second device.
The device according to claim 12, characterized in that,

The transceiver unit is configured to periodically send a complete header data packet associated with the first service to the second device.
The device according to claim 13, further comprising:

A processing unit, configured to determine a first context index corresponding to the compressed header data packet associated with the first service;

The processing unit is further configured to send a complete header data packet associated with the first service to the second device through the transceiver unit when it is determined that the first time interval is greater than a preset duration, and the second A time interval is the time interval between the first time stamp and the second time stamp; the first time stamp is the time stamp when the first device receives the first feedback information, and the second time stamp A timestamp when the first context index is determined for the first device.
The device according to claim 14, characterized in that,

The processing unit is further configured to, when it is determined that the first time interval is less than or equal to the preset duration, send the compressed header data packet to the second device through the transceiver unit.
The device according to claim 13, further comprising:

A processing unit configured to, when it is determined that the number of compressed header data packets associated with the first service sent to the second device through the transceiver unit is greater than a preset number, send the message to the second device through the transceiver unit The second device sends a complete header data packet associated with the first service.
The device according to claim 16, characterized in that,

The processing unit is further configured to, when it is determined that the sending number is less than or equal to the preset number, send the compressed header data packet associated with the first service to the second device through the transceiver unit .
The device according to any one of claims 12-17, wherein after the first device sends the first data packet to the second device, the first device receives a Before the first feedback information of the data packet, the transceiver unit is also used for:

sending a complete header data packet associated with the first service to the second device.
A communication device, characterized in that the device is a second device, and the device includes:

A transceiver unit, configured to receive a first data packet from the first device, the first data packet is a complete header data packet associated with the first service, and the complete header data packet includes a context index and a context;

The transceiving unit is configured to send first feedback information for the first data packet to the first device, where the first feedback information is used to indicate that the creation of the first context index in the first data packet is completed and the correspondence between the first context;

The transceiving unit is configured to receive a complete header data packet from the first device and associated with the first service.
The device according to claim 19, characterized in that,

The transceiving unit is configured to receive a complete header data packet associated with the first service periodically sent by the first device.
The apparatus according to claim 19 or 20, characterized in that, after the second device receives the first data packet from the first device, the second device sends the first data packet to the first device Before the first feedback information of the data packet, the transceiver unit is used for:

Receive a complete header data packet from the first device and associated with the first service.
The device according to any one of claims 19-21, wherein the device further comprises:

A processing unit, configured to update the context index corresponding to the first service and the corresponding relationship between the contexts according to the complete header data packet associated with the first service.
A communication device, characterized in that it includes a processor and a transceiver, the processor and the transceiver are used to execute at least one computer program or instructions stored in a memory, so that the device implements claims 1-7 The method described in any one of claims 8-11, or implement the method described in any one of claims 8-11.
A computer-readable storage medium, characterized in that computer programs or instructions are stored in the storage medium, and when the computer programs or instructions are executed by a computer, the method described in any one of claims 1 to 7 is realized. method, or, implement the method as described in any one of claims 8-11.
A computer program product, characterized in that the computer program product includes computer program code, and when the computer program code is run on a computer, the method according to any one of claims 1 to 7 can be realized, or To realize the method described in any one of claims 8-11.