WO2021026939A1 - 以太帧头的压缩、解压方法和装置 - Google Patents

以太帧头的压缩、解压方法和装置 Download PDF

Info

Publication number
WO2021026939A1
WO2021026939A1 PCT/CN2019/100900 CN2019100900W WO2021026939A1 WO 2021026939 A1 WO2021026939 A1 WO 2021026939A1 CN 2019100900 W CN2019100900 W CN 2019100900W WO 2021026939 A1 WO2021026939 A1 WO 2021026939A1
Authority
WO
WIPO (PCT)
Prior art keywords
header
compression
ethernet frame
correspondence
field
Prior art date
Application number
PCT/CN2019/100900
Other languages
English (en)
French (fr)
Inventor
范强
娄崇
徐小英
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2019/100900 priority Critical patent/WO2021026939A1/zh
Priority to CN201980098681.0A priority patent/CN114208137B/zh
Priority to EP19941327.9A priority patent/EP4016948B1/en
Publication of WO2021026939A1 publication Critical patent/WO2021026939A1/zh
Priority to US17/669,681 priority patent/US11778070B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/04—Protocols for data compression, e.g. ROHC
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks

Definitions

  • This application relates to the field of communication technology, and in particular to methods and devices for compressing and decompressing Ethernet frame headers.
  • the traditional industrial control field realizes automatic control through wired connection, but the deployment method of wired connection makes the cable deployment and maintenance cost relatively high, and due to the limitation of the cable, the mobility of the controlled terminal is poor. For this reason, industrial control that uses wireless transmission instead of wired connection has gained more and more attention.
  • Most industrial control networks use Ethernet technology during deployment. When the wireless network replaces the wired network, the Ethernet frame is transmitted between the control end and the controlled end through the wireless network, so the Ethernet frame needs to be transmitted in the wireless network. Ethernet frames require more resource overhead in wireless network transmission, but wireless resources are limited. Therefore, it is desirable to reduce the overhead of Ethernet frame transmission in wireless networks.
  • This application provides methods and devices for compressing and decompressing Ethernet frame headers to reduce the occupation of Ethernet communication resources by the Ethernet frame headers.
  • a method for compressing an Ethernet frame header which includes: a compression end receives a first Ethernet frame, and the Ethernet frame header of the first Ethernet frame includes a first field to be compressed;
  • the compression field determines the first compression information of the Ethernet header of the first Ethernet frame, the first correspondence includes the correspondence between the first compression information and the value of the first field to be compressed, and the first compression information includes the first context identifier CID;
  • the compressor compresses the Ethernet frame header of the first Ethernet frame according to the first compression information.
  • a compression device which includes units or means for performing each step of the first aspect above.
  • a compression device which includes a processor and an interface circuit.
  • the processor is configured to communicate with other devices through the interface circuit and execute the method provided in the first aspect above.
  • the processor includes one or more.
  • a compression device including a processor, configured to call a program stored in a memory to execute the method provided in the above first aspect.
  • the memory can be located inside the device or outside the device.
  • the processor includes one or more.
  • a computer program is provided, and when the program is called by a processor, the method provided in the above first aspect is executed.
  • the compressor may, after receiving the first Ethernet frame including the first field to be compressed, use the first correspondence relationship between the first compression information and the value of the first field to be compressed, and then use the first compression information
  • the Ethernet header of the Ethernet frame is compressed. Because the Ethernet header of the first Ethernet frame is compressed, communication resources can be saved.
  • the first corresponding relationship stored by the compression end when the corresponding relationship stored by the compression end does not include the value of the first field to be compressed of the first Ethernet frame, the first corresponding relationship is generated, and the compression
  • the correspondence relationship stored at the end includes at least one correspondence relationship between compression information and the value of the field to be compressed.
  • the compression end sends the first correspondence to the decompression end.
  • the compression end sending the first correspondence to the decompression end includes: the compression end sends an uncompressed data packet to the decompression end, and the uncompressed data packet includes the first correspondence relationship.
  • the compressing end sends the first correspondence to the decompressing end, including: the compressing end uses the first packet data convergence protocol data protocol data unit PDCP data to decompress The terminal sends the first correspondence; where the first PDCP data PDU includes: the first Ethernet frame header compressed EHC header, and the first EHC header includes the first indication field, the first CID, and the second Ethernet frame header; second The value of the field to be compressed in the Ethernet frame header of the Ethernet frame is equal to the value of the first field to be compressed; the first indication field is used to indicate whether the first EHC header includes a complete Ethernet frame header.
  • the first EHC header further includes the first profile identification profile ID.
  • the first indication field is further used to indicate that the first EHC header includes the first profile ID.
  • the first PDCP data PDU further includes: PDCP header, service data adaptation layer SDAP header, Ethernet data payload and integrity message authentication code MAC-I .
  • the compressing end sends the first correspondence to the decompressing end, including:
  • the compression end sends the first corresponding relationship to the decompression end through the PDCP control PDU of the packet data convergence protocol control protocol data unit; where the PDCP control PDU includes the first indication information, the first CID, and the value of the first field to be compressed; An indication information is used to indicate that the PDCP control PDU is used to transmit the first correspondence.
  • the PDCP control PDU further includes the first profile ID.
  • the compression end sends a first PDCP data PDU to the decompression end; wherein, the first PDCP data PDU includes: the first EHC header, the first The EHC header includes a first indication field and an Ethernet header of the second Ethernet frame.
  • the value of the field to be compressed in the Ethernet header of the second Ethernet frame is equal to the value of the first field to be compressed; the first indication field is used for Indicates whether the first CID is carried in the first EHC header.
  • the Ethernet header of the second Ethernet frame when the first EHC header carries the first CID, the Ethernet header of the second Ethernet frame is a compressed Ethernet header, or when the first When the EHC header does not carry the first CID, the Ethernet header of the second Ethernet frame is a complete Ethernet header.
  • the first PDCP data PDU further includes: PDCP header, service data adaptation layer SDAP header, Ethernet data payload and integrity message authentication code MAC-I .
  • the compressing end sending the first correspondence to the decompressing end includes: the compressing end sending the first correspondence to the decompressing end multiple times.
  • the method further includes: the compression end receives feedback information from the decompression end, and the feedback information is used to indicate the reception status of the first correspondence.
  • the feedback information includes the first CID.
  • the feedback information further includes at least one of the following: a first profile ID, a second indication field, and a third indication field.
  • the second indication field is used to indicate The first correspondence is a newly added correspondence or a modified correspondence at the decompression end
  • the third indication field is used to indicate whether the feedback information is positive feedback or negative feedback.
  • the compression terminal further stores an indicator variable of the corresponding relationship, and the indicator variable is used to indicate whether the compressed information of the corresponding relationship is used for compression.
  • the compression end further includes: when the correspondence stored on the compression end includes a first correspondence corresponding to the first field to be compressed, and an indicator variable of the first correspondence When the compression information indicating the first correspondence is not used for compression, the compression end sends the first correspondence to the decompression end.
  • the method further includes: when the compression end confirms that the first correspondence relationship is correctly received by the decompression end, the compression end sets the indicator variable to the first value, and the first The value is used to indicate that the compressed information is used for compression.
  • the first compressed information further includes the first profile ID.
  • the method further includes: the compression end sends second indication information to the decompression end, and the second indication information is used to indicate that the first correspondence is newly added at the compression end Correspondence or modified correspondence.
  • the method further includes: the compression end sends the compressed first Ethernet frame to the decompression end, the compressed first Ethernet frame includes the first CID, and does not Including profile ID.
  • the space occupation can be reduced.
  • the compression end sending the compressed first Ethernet frame to the decompression end includes: the compression end sends the compressed first Ethernet frame to the decompression end through the second PDCP data PDU One ether frame.
  • the second PDCP data PDU includes a second EHC header, and the second EHC header further includes verification information.
  • the verification information is generated according to one or more pieces of information in the first correspondence.
  • the compression end in the case where the compression end receives an error report returned by the decompression end according to the verification information, the compression end deletes the first correspondence, or the compression end The first correspondence is set as unavailable.
  • the compression end is a terminal
  • the decompression end is a network device
  • the method further includes:
  • the compression end sends capability information to the decompression end;
  • the capability information includes at least one of the following: the capability of the compression end to support EHC, the number of data radio bearer DRBs in the compression end that support EHC, and the profile information of the configuration file supported by the compression end.
  • the maximum value of the number of correspondences supported by the EHC DRB, MAX_CID the compression end supports the ability to dynamically configure the profile parameters, and the compression end supports the sum of the number of correspondences maintained by the EHC DRB.
  • the compression terminal is a terminal, and the method further includes: the terminal receives configuration information, the configuration information is used to indicate whether the EHC header carries a profile ID; or, the configuration information Including profile ID.
  • the compression terminal receiving capability information
  • the capability information includes at least one of the following: the capability information includes at least one of the following: the compression terminal supports EHC
  • the capacity of the compression terminal supports the number of EHC data radio bearer DRBs, the configuration file profile information supported by the compression terminal, the maximum number of correspondences supported by each DRB supporting EHC, MAX_CID, and the compression terminal supports dynamic configuration of profile parameters The ability of the compression end to support the sum of the number of correspondences maintained by the DRB of EHC.
  • the decompression end is a terminal, and the compression end is a network device.
  • the method further includes: the network device sends configuration information to the decompression end, and the configuration information is used to indicate EHC Whether the header carries the profile ID; or, the configuration information includes the profile ID.
  • a method for decompressing an Ethernet frame header including: a decompression end receives a first Ethernet frame, the first Ethernet frame includes a first context identifier CID; the decompression end determines a first CID that includes the first CID according to the first CID A corresponding relationship, the first corresponding relationship includes the corresponding relationship between the first compressed information and the value of the first field to be decompressed, the first compressed information includes the first CID; the decompression end according to the first compressed information in the first corresponding relationship and the first The value of a field to be decompressed decompresses the Ethernet frame header of the first Ethernet frame.
  • a decompression device which includes units or means for performing each step of the second aspect above.
  • a decompression device including a processor and an interface circuit.
  • the processor is configured to communicate with other devices through the interface circuit and execute the method provided in the second aspect above.
  • the processor includes one or more.
  • a decompression device including a processor, configured to call a program stored in a memory to execute the method provided in the above second aspect.
  • the memory can be located inside the device or outside the device.
  • the processor includes one or more.
  • the decompressor can determine the first correspondence according to the first CID in the first Ethernet frame when receiving the compressed first Ethernet frame, and realize the first correspondence of the compressed Ethernet frame header according to the first correspondence. Decompression. In this embodiment of the application, because the Ethernet frame header of the Ethernet frame is compressed, communication resources can be saved.
  • the method further includes: the decompression end receives the first correspondence from the compression end.
  • the decompression end receiving the first correspondence from the compression end includes: the decompression end receives the uncompressed data packet, and the uncompressed data packet includes the first correspondence.
  • the decompression end receives the first correspondence from the compression end, including: the decompression end receives the first correspondence from the compression end through PDCP data PDU;
  • a PDCP data PDU includes: the first Ethernet frame header compressed EHC header, the first EHC header includes the first indication field, the first CID and the second Ethernet frame header, and the second Ethernet frame header to be compressed The value of is equal to the value of the first field to be compressed; the first indication field is used to indicate whether the first EHC header includes a complete Ethernet frame header.
  • the first EHC header further includes the first profile identification profile ID.
  • the first indication field is also used to indicate that the first EHC header includes the first profile ID.
  • the first PDCP data PDU further includes: PDCP header, service data adaptation layer SDAP header, Ethernet data payload and integrity message authentication code MAC-I .
  • the decompression end receiving the first correspondence from the compression end includes: the decompression end receives the first correspondence from the compression end through PDCP control PDU; where the PDCP control PDU includes the first indication information, the first CID, and the first waiting The value of the compressed field; the first indication information is used to indicate that the PDCP control PDU is used to transmit the first correspondence.
  • the PDCP control PDU further includes: the first profile ID.
  • the decompression end receives the first PDCP data PDU from the compression end; wherein the first PDCP data PDU includes: the first EHC header, the first The EHC header includes a first indication field and an Ethernet frame header of the second Ethernet frame.
  • the value of the field to be compressed in the Ethernet frame header of the second Ethernet frame is equal to the value of the first field to be compressed; the first indication field is used to indicate Whether the first CID is carried in the first EHC header.
  • the Ethernet header of the second Ethernet frame when the first EHC header carries the first CID, the Ethernet header of the second Ethernet frame is a compressed Ethernet header, or when the first When the EHC header does not carry the first CID, the Ethernet header of the second Ethernet frame is a complete Ethernet header.
  • the first PDCP data PDU further includes: PDCP header, service data adaptation layer SDAP header, Ethernet data payload and integrity message authentication code MAC-I .
  • the decompression terminal stores at least one correspondence between compression information and the value of the field to be decompressed
  • the method further includes: when the correspondence relationship stored on the decompression terminal is not When the first compressed information is included, the decompression end stores the first correspondence; or, when the correspondence stored by the decompression end includes the first compressed information, and the first compressed information corresponds to the value of the field to be decompressed and the value of the first field to be decompressed If the value is different, the decompression end modifies the value of the field to be decompressed corresponding to the first compressed information to the value of the first field to be decompressed.
  • the method further includes: the decompression end sends feedback information to the compression end, and the feedback information is used to indicate the reception status of the first correspondence.
  • the feedback information includes the first CID.
  • the feedback information further includes at least one of the following: profile ID, a first indication field, and a second indication field.
  • the first indication field is used to indicate the first
  • the corresponding relationship is a newly added corresponding relationship or a modified corresponding relationship at the decompression end
  • the second indication field is used to indicate whether the feedback information is positive feedback or negative feedback.
  • the first Ethernet frame further includes: first check information.
  • the first verification information is generated according to one or more pieces of information in the first correspondence.
  • the method further includes: the compression end generates second verification information according to one or more information in the first correspondence; in the case that the first verification information is the same as the second verification information, the decompression end decompresses the first verification information.
  • the Ethernet frame header of the Ethernet frame or, when the first verification information is different from the second verification information, the decompression end deletes the first correspondence; and/or, the decompression end sends an error report to the compression end.
  • the embodiments of the present application provide methods and devices for compressing and decompressing Ethernet frame headers.
  • the compression end may include the first compressed information and the first to-be-compressed field.
  • the first corresponding relationship of the value of the compressed field is to compress the Ethernet frame header of the first Ethernet frame according to the first compression information. If it is adapted, the decompression end may receive the compressed first Ethernet frame according to The first correspondence realizes the decompression of the Ethernet header of the compressed first Ethernet frame.
  • communication resources can be saved.
  • FIG. 1 is a schematic diagram of a network architecture provided by an embodiment of this application.
  • FIG. 2 is a schematic diagram of a control system provided by an embodiment of the application.
  • FIG. 3 is a schematic diagram of another control system provided by an embodiment of the application.
  • FIG. 4 is a schematic diagram of another control system provided by an embodiment of the application.
  • FIG. 5 is a schematic diagram of a wireless communication network provided by an embodiment of the application applied to a control network
  • FIG. 6 is a schematic diagram of another network architecture provided by an embodiment of this application.
  • FIG. 7 is a schematic flowchart of a compression and decompression method provided by an embodiment of the application.
  • FIG. 8 is a schematic diagram of a format of an Ethernet frame provided by an embodiment of the application.
  • FIG. 9 is a PDCP data PDU format configured with an EHC header provided by an embodiment of the application.
  • FIG. 10 is a schematic diagram of the format of the first EHC header provided by an embodiment of the application.
  • FIG. 11 is a schematic diagram of a format of a second EHC header provided by an embodiment of the application.
  • FIG. 12 is a schematic flowchart of a method for synchronizing a first correspondence between a compression end and a decompression end according to an embodiment of the application;
  • FIG. 13 is a schematic diagram of a format of feedback information provided by an embodiment of this application.
  • FIG. 14 is a schematic diagram of the format of a third EHC header provided by an embodiment of the application.
  • 15 is a schematic diagram of the format of the fourth EHC header provided by an embodiment of the application.
  • 16 is a schematic diagram of the format of the fifth EHC header provided by an embodiment of the application.
  • FIG. 17 is a schematic diagram of a format of a sixth EHC header provided by an embodiment of this application.
  • FIG. 18 is a schematic diagram of the format of the first PDCP data PDU provided by an embodiment of this application.
  • FIG. 19 is a schematic diagram of the second PDCP data PDU format provided by an embodiment of this application.
  • FIG. 20 is a schematic diagram of a third PDCP data PDU format provided by an embodiment of the application.
  • FIG. 21 is a schematic diagram of the fourth PDCP data PDU format provided by an embodiment of the application.
  • Figure 22 is a schematic diagram of a fifth PDCP data PDU format provided by an embodiment of the application.
  • FIG. 23 is a schematic diagram of a seventh EHC header format provided by an embodiment of this application.
  • FIG. 24 is a schematic diagram of an eighth EHC header format provided by an embodiment of this application.
  • FIG. 25 is a schematic diagram of an Ethernet frame compression apparatus provided by an embodiment of the application.
  • FIG. 26 is a schematic diagram of an Ethernet frame decompression apparatus provided by an embodiment of the application.
  • FIG. 27 is a schematic structural diagram of a network device provided by an embodiment of this application.
  • FIG. 28 is a schematic structural diagram of a terminal device provided by an embodiment of this application.
  • FIG. 29 is a schematic structural diagram of an Ethernet frame compression apparatus provided by an embodiment of this application.
  • FIG. 30 is a schematic structural diagram of an Ethernet frame decompression apparatus provided by an embodiment of the application.
  • FIG. 1 is a schematic diagram of a network architecture to which the embodiments of the present application are applicable. As shown in FIG. 1, the network architecture includes a compression end and a decompression end.
  • the compression terminal may be a terminal or an execution unit in the terminal.
  • the execution unit in the terminal may be a packet data convergence protocol (PDCP) entity or a radio link control (radio link control) in the terminal.
  • RLC radio link control
  • SDAP service data adaptation protocol
  • EHC ethernet header compression
  • the compression end may also be a network device or an execution unit in the network device.
  • the execution unit in the network device may be a PDCP entity, an RLC entity, or a SDAP entity in the network device, or an EHC processing module in the entity.
  • the decompression end may be a terminal or an execution unit in the terminal.
  • the execution unit in the terminal may be a PDCP entity, an RLC entity, or a SDAP entity in the terminal, or an EHC processing module in the entity.
  • the decompression end may also be a network device or an execution unit in the network device.
  • the execution unit in the network device may be a PDCP entity, an RLC entity, or a SDAP entity in the network device, or an EHC processing module in the entity.
  • the compression end may be a terminal, a PDCP entity or an RLC entity or a SDAP entity in the terminal, etc., or an EHC processing module in the entity
  • the decompression end may be a network
  • the compression end may be a network device, a PDCP entity in the network device, an RLC entity or an SDAP entity, etc., or an EHC processing module in the entity
  • the decompression end may be a terminal, The PDCP entity, RLC entity, or SDAP entity in the terminal, or the EHC processing module in the entity.
  • the compression end and the decompression end are both terminals for sidelink communication, the PDCP entity or RLC entity or SDAP entity in the terminal, etc., or one of the entities. EHC processing module.
  • the traditional ether control automation technology (etherCAT) system includes a master (master) and at least one slave (slave).
  • etherCAT a wired time-sensitive network (time sensitive network, TSN) to realize the transmission between master and slave, as shown in Figure 2.
  • TSN time sensitive network
  • the TSN ensures that the transmission delay fluctuation between the master and the slave is within a small range, so as to achieve the similar effect of using a dedicated cable connection between the master and the slave. In this way, a flexible physical connection can be realized between master and slave.
  • the master station can also be called the console (controller), and the slave station can also be called the end device (end device).
  • the wireless network is used to realize the transmission between master and Slave1, and the wireless network ensures that the transmission delay fluctuation between master and Slave1 is within a small range, so as to realize the dedicated use between master and Slave1
  • the cable connection has a similar effect.
  • Slave1 is a slave in the slave group. It communicates with the master through a wireless network, and the remaining slaves establish a wired connection with the slave1. This slave group can also be called a slave chain. In this way, a more flexible physical connection can be achieved between master and slave. Or, the wired connection between slaves can be cancelled, and wireless transmission can be used to replace wired transmission, thereby realizing completely flexible deployment.
  • the master communicates with each slave through a wireless network.
  • the terminal 510 accesses a wireless network through a wireless interface (for example, an air interface) to communicate with other devices, such as a master, through the wireless network.
  • the wireless network includes a radio access network (RAN) 520 and a core network (CN) 530.
  • the RAN 520 is used to connect the terminal 510 to the wireless network
  • the CN 530 is used to manage the terminal and provide other The gateway for device communication.
  • the terminal can be a device with wireless communication function, which can be connected to the slave in the above control system through an adapter to receive the data sent by the master to the slave through the wireless network and send it to the slave, or send the data from the slave to the master through the wireless network Send to master.
  • the terminal can be integrated with the slave on a physical entity, for example, Slave1 in Figure 3 or a slave in Figure 4 can integrate components with wireless communication functions (for example, chips), at this time, the slave integrates wireless communication functions And the function of the industrial control terminal to perform operations according to instructions.
  • a physical entity for example, Slave1 in Figure 3 or a slave in Figure 4 can integrate components with wireless communication functions (for example, chips), at this time, the slave integrates wireless communication functions And the function of the industrial control terminal to perform operations according to instructions.
  • each slave can communicate with the master through the wireless network.
  • each slave is connected to the terminal through an adapter.
  • each slave can integrate a wireless communication function component (for example, a chip) to access a wireless network through a wireless interface.
  • the above two connection methods can be combined.
  • Slave 1 communicates with the master through a wireless network, and the remaining slaves establish a wired connection with this Slave 1.
  • This slave group can also be called a slave chain.
  • Slave 1 is the entrance and exit of the slave group connected to the wireless network, that is, The slave to which the terminal device is connected.
  • Another example is to group slaves.
  • Each group has two slaves, such as Slave 1 and Slave n. They communicate with the master through a wireless network.
  • the remaining slaves establish wired connections with Slave 1 and Slave n.
  • This slave group can also be called The slave chain, Slave 1 and Slave n are the entrance and exit of the slave group connected to the wireless network, that is, the slave connected to the terminal device.
  • the terminal is also called a terminal device or user equipment (UE), which is a device with a wireless communication function and can be connected to a slave, and is called a terminal device in the following embodiments.
  • the terminal device may be independent of the slave or integrated with the slave; when integrated, the terminal device may refer to a device that integrates the physical entity of the slave and the wireless communication function, such as a chip or a system on a chip.
  • Terminal devices may include wireless terminals in industrial control, or terminals with similar requirements in other control systems, such as wireless terminals in self-driving (self-driving) and remote medical surgery (remote medical surgery).
  • Wireless terminals wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, or wireless terminals in smart homes, etc.
  • the network device may be a device in a wireless network, for example, a radio access network (RAN) node or base station that connects a terminal device to the wireless network.
  • RAN nodes or base stations are: gNB, transmission reception point (TRP), evolved Node B (evolved Node B, eNB), radio network controller (RNC), Node B (Node B, NB), base station controller (BSC), base transceiver station (base transceiver station, BTS), home base station (for example, home evolved NodeB, or home Node B, HNB), baseband unit (base Band unit, BBU), relay station, or wireless fidelity (wireless fidelity, Wifi) access point (AP), cloud wireless access network (cloud radio access network, CRAN) scenarios, wireless controller, car networking Roadside unit (RSU) in vehicle to everything (V2X), or access point in integrated access backhaul (IAB) system, etc.
  • RRP transmission reception point
  • RNC radio network controller
  • Node B Node B
  • the RAN device may also integrate the functions of the TSN network node, for example, the function of an integrated console, and the network device may also be the console.
  • a network device may include a centralized unit (CU) node, or a distributed unit (DU) node, or a RAN device including a CU node and a DU node.
  • CU centralized unit
  • DU distributed unit
  • the RAN includes a baseband device and a radio frequency device.
  • the baseband device can be implemented by one node or by multiple nodes.
  • the radio frequency device can be implemented remotely from the baseband device or integrated into the baseband device. Or part of the remote part is integrated in the baseband device.
  • the RAN may include a baseband device and a radio frequency device, where the radio frequency device may be arranged remotely relative to the baseband device, for example, a remote radio unit (RRU) may be arranged remotely relative to the BBU.
  • RRU remote radio unit
  • the control plane protocol layer structure may include the radio resource control (RRC) layer, the packet data convergence protocol (PDCP) layer, the radio link control (RLC) layer, and the media interface. Access control (media access control, MAC) layer and physical layer and other protocol layer functions.
  • the user plane protocol layer structure can include the functions of the PDCP layer, the RLC layer, the MAC layer, and the physical layer; in one implementation, the PDCP layer can also include a service data adaptation protocol (SDAP) layer .
  • SDAP service data adaptation protocol
  • the functions of these protocol layers can be implemented by one node or multiple nodes; for example, in an evolution structure, the RAN can include a centralized unit (CU) and a distributed unit (DU).
  • CU centralized unit
  • DU distributed unit
  • Each DU can be centrally controlled by one CU.
  • CU and DU can be divided according to the protocol layer of the wireless network. For example, the functions of the PDCP layer and above protocol layers are set in the CU, and the protocol layers below the PDCP, such as the RLC layer and MAC layer, are set in the DU.
  • This type of protocol layer division is just an example, it can also be divided in other protocol layers, for example, in the RLC layer, the functions of the RLC layer and above protocol layers are set in the CU, and the functions of the protocol layers below the RLC layer are set in the DU; Or, in a certain protocol layer, for example, part of the functions of the RLC layer and the functions of the protocol layer above the RLC layer are set in the CU, and the remaining functions of the RLC layer and the functions of the protocol layer below the RLC layer are set in the DU. In addition, it can also be divided in other ways, for example, by time delay, and functions that need to meet the delay requirement for processing time are set in the DU, and functions that do not need to meet the delay requirement are set in the CU.
  • the radio frequency device can be remote, not placed in the DU, can also be integrated in the DU, or part of the remote part is integrated in the DU, and there is no restriction here.
  • control plane (CP) and the user plane (UP) of the CU can also be separated and realized by dividing them into different entities, namely the control plane CU entity (CU-CP entity) and the user plane CU entity (CU-UP entity) ).
  • the signaling generated by the CU can be sent to the terminal through the DU, or the signaling generated by the terminal can be sent to the CU through the DU.
  • the DU may directly pass the protocol layer encapsulation without analyzing the signaling and transparently transmit it to the terminal or CU. If the following embodiments involve the transmission of such signaling between the DU and the terminal, at this time, the sending or receiving of the signaling by the DU includes this scenario.
  • RRC or PDCP layer signaling will eventually be processed as PHY layer signaling and sent to the terminal, or converted from received PHY layer signaling. Under this architecture, the RRC or PDCP layer signaling can also be considered to be sent by the DU, or sent by the DU and radio frequency.
  • the network device may be a CU node, or a DU node, or a RAN device including a CU node and a DU node.
  • wireless networks replace wired networks as the last hop of industrial control networks. Compared with wired networks, it can reduce costs, bring convenience to maintenance, and support flexible deployment and mobility of slave stations.
  • the master station transmits the Ethernet frame to the slave station through the wireless network
  • the slave station receives the Ethernet frame through the wireless network, and can send the Ethernet frame to the master station through the wireless network. Therefore, the Ethernet frame needs to be transmitted in the wireless network.
  • the Ethernet frame includes a header and a load, which requires more resource overhead in wireless network transmission.
  • the embodiment of the present application hopes to reduce the transmission overhead of the Ethernet frame in the wireless network to improve resources. Utilization rate.
  • the embodiment of the present application reduces the information transmitted in the wireless network by compressing the Ethernet frame header, thereby reducing resource overhead and improving resource utilization.
  • FIG. 7 is a schematic flowchart of a method for compressing and decompressing a frame header according to an embodiment of the application. It can be understood that in practical applications, the compression process of the compression end and the decompression process of the decompression end can be implemented independently. For example, after the compression end completes the compression process, it can send the compressed ether frame to the decompression end at any time afterwards, and the decompression end The compressed Ethernet frame can be received at any time, and the compressed Ethernet frame can be decompressed, which is not specifically limited in the embodiment of the present application. As shown in FIG. 7, the method provided by the embodiment of the present application may include the following steps:
  • Step S101 The compression end receives an Ethernet frame, and the Ethernet frame header of the Ethernet frame includes the first field to be compressed.
  • the compression end may receive the Ethernet frame from the master station or the slave station.
  • the Ethernet frame includes the Ethernet frame header and payload, and can include multiple fields.
  • it is the 802.1Q Ethernet MAC frame format defined by IEEE 802.3.
  • the Ethernet frame can include the following fields : 7 bytes of preamble, 1 byte of start of frame delimiter (SFD), 6 bytes of destination media access control (MAC) address, 6 words
  • the source MAC address of the stanza 2-byte length/type (for example, 802.1QTagType), 2-byte tag control information (TAG control information, or, taging control information), 2-byte MAC client length/type, which can be Variable-length payload or payload, and a 4-byte frame check sequence (FCS), where the payload may include data (for example, MAC client data), and the optional payload may also include a padding field.
  • the field before the payload is the Ethernet frame header, and the subsequent FCS is used for Ethernet frame verification.
  • Ethernet frame format is only an example, and is not intended to limit this application.
  • the format may be different.
  • the Ethernet frame header may only include the MAC destination address, source MAC address, and length/type fields.
  • Other fields may be partly or completely included in the Ethernet frame.
  • the sizes of the above fields are only examples and are not used to limit the application.
  • the preamble is used to identify and detect the Ethernet frame transmission on the Ethernet transmission link on the Ethernet frame receiving side; SFD is used to determine the starting position of the subsequent Ethernet frame content on the Ethernet frame receiving side; the destination MAC address is the MAC address of the receiving side; The source MAC address is the MAC address of the sender; the length/type is used to identify the marking protocol; the marking control information is used to indicate marking related information, and the MAC client length/type is used to indicate the effective data length of the Ethernet frame or the MAC client protocol Ethernet type.
  • the first field to be compressed may include: destination MAC address, source MAC address, length/type field, TAG control information, or MAC Client length/type.
  • any one or any two or more fields or all of these fields can also be compressed. That is, the first field to be compressed may also include two or more of the above fields.
  • the first field to be compressed may include The destination MAC address and the source MAC address, that is, only the MAC address in the Ethernet frame header is compressed.
  • a field to be compressed may include the destination MAC address, TAG control information, and MAC client length/type.
  • which fields are included in the first field to be compressed may be different. Table 1 below shows the fields included in the Ethernet II type frame format.
  • the first field to be compressed includes any one or any two or all of the destination MAC address, source MAC address, and type field.
  • Step S102 The compressor determines the first compression information of the Ethernet header of the Ethernet frame according to the first correspondence and the first field to be compressed, and the first correspondence includes the first compressed information and the first field to be compressed Correspondence of the value of.
  • the compression terminal may store the correspondence between the compressed information and the value of the field to be compressed, where the first correspondence is the correspondence between the first compressed information and the value of the first field to be compressed.
  • the correspondence stored on the compression end may include the first correspondence, that is, the first correspondence may be pre-stored in the compression end; the correspondence stored on the compression end may not include the first correspondence.
  • the first correspondence can also be generated by the compression terminal in real time or as needed during the data stream transmission process.
  • the embodiment of the present application does not specifically limit the manner of obtaining the first correspondence relationship.
  • the method for generating the first correspondence on the compression end may be determined according to actual application scenarios. The method for generating the first correspondence will be further described in the subsequent embodiments, which will not be repeated in this embodiment of the application.
  • the compressor may determine the first compression information included in the first correspondence as the first compression information of the Ethernet frame header of the Ethernet frame.
  • Each corresponding relationship in the corresponding relationship may be associated with a corresponding relationship identifier, and the compressed information may include the identifier of the corresponding relationship (or called the identifier of compressed information).
  • the first compressed information includes the identifier or the first corresponding relationship.
  • An identifier of compressed information The following embodiments all use the information as a context identifier (CID) as an example.
  • the compressed information may further include a profile identifier (profile identifier, profile ID), so that the first compressed information may also include the first profile ID.
  • profile ID can be used to identify a profile.
  • the profile is used to specify the compression mechanism.
  • the profile is used to indicate the compressible fields and/or the compression method. Different profiles are distinguished by the profile ID.
  • the profile ID is used to indicate the communication protocol of the Ethernet frame header and/or the field to be compressed of the Ethernet frame header.
  • TCP/IP transmission control protocol/internet protocol
  • user datagram protocol/internet protocol user datagram protocol/internet protocol
  • the compressed information may not include the profile ID.
  • the compression end and the decompression end can determine the profile as the default profile. When compressing or decompressing, they can compress or decompress based on the profile.
  • the profile ID may not be included in the compressed information.
  • the compressed information may also include the profile ID to facilitate subsequent expansion.
  • the compression terminal also stores an indicator variable of each correspondence, which is used to indicate whether the compression information of each correspondence is used for compression.
  • the compression terminal stores context information, where the context information may include at least one context entry.
  • the context information is as follows:
  • Entry 1 CID 1, profile 1, compressed field value A1, indication of whether it is available;
  • Entry 2 CID 2, profile 2, compression field value A2, indication of whether it is available;
  • Entry N CID 3, profile N, compression field value AN, indication of availability.
  • the context information may include at least one context entry.
  • Each context entry includes CID, including CID and compressed field value, that is, each corresponding relationship described above.
  • each context entry may also include an indicator variable, which is referred to herein as an availability indicator, for indicating whether the compression information (or compression information) in the context entry where the indicator variable is located is used for compression.
  • the first correspondence is included in one of the context items (for example, the first item). If the compression end does not store the first entry, the first entry is generated into the stored context information.
  • Each corresponding relationship in the corresponding relationship may be associated with a corresponding relationship identifier, and the corresponding relationship identifier may be called a context identifier (CID), that is, each context entry is associated with a CID.
  • the compressed information includes a CID
  • the first compressed information includes a first CID
  • the first CID may also be used as an identifier of the first correspondence.
  • each context entry may include a profile ID.
  • the compression information includes the profile ID
  • the first compression information includes the first profile ID; when the profile ID is not included, the default profile may be used for compression.
  • the profile IDs included in different context entries can be the same, for example, both entry 1 and entry 2 can use profile 1.
  • Step S103 The compressor compresses the Ethernet frame header of the Ethernet frame according to the first compression information.
  • the compression end may compress the Ethernet frame header of the Ethernet frame according to the first compression information. If the first compression information includes the profile ID, the profile can be determined according to the profile ID, and the first field to be compressed can be found according to the compression fields specified by the profile. If the first correspondence does not include the profile ID, the first field to be compressed can be found according to the compression field specified by the default profile.
  • the first field to be compressed may be one or more fields in the Ethernet frame header, and which field or fields are specifically included can be determined according to the profile.
  • the value of the first field to be compressed in the first correspondence relationship is that one field; when the first field to be decompressed is multiple fields in the Ethernet frame header , Setting the value of the first field to be compressed in the first correspondence to a combination of the values of the multiple fields.
  • the compressor may delete the first field to be compressed in the Ethernet frame header, and add the corresponding first CID to the data packet. It can be understood that in actual applications, the Ethernet header of the Ethernet frame may be compressed according to the first compression information in other ways according to the actual application scenario, which is not specifically limited in the embodiment of the present application.
  • the compressed Ethernet frame can be further sent to the decompression end, and the decompression end can be based on the first compression information and the value of the first field to be compressed The corresponding relationship of, realizes the decompression of the compressed Ethernet frame, as described in step S104 to step S107.
  • Step S104 The compression end sends the compressed Ethernet frame to the decompression end.
  • the compression end may choose an adaptive manner to send the compressed ether frame to the decompression end according to the actual application scenario.
  • the embodiment of the present application does not specifically limit the compression end to send the compressed ether frame to the decompression end.
  • the compressed Ethernet frame may include first compression information.
  • the first compression information may include a first CID, so that further, the decompression end can implement the compressed Ethernet frame according to the first CID. Decompression of frames.
  • the compression end sends the compressed Ethernet frame to the decompression end through a packet data convergence protocol control protocol data unit (packet data convergence protocol data protocol data unit, PDCP data PDU).
  • a packet data convergence protocol control protocol data unit packet data convergence protocol data protocol data unit, PDCP data PDU.
  • the EHC header may be configured in the format of the PDCP data PDU.
  • the format of the PDCP data PDU configured with the EHC header in the embodiment of this application including: PDCP header, service data adaptation protocol (SDAP) header, and EHC header , Ethernet data payload (ethernet data payload) and integrity message authentication code (message authentication code for integrity, MAC-I), where the PDCP header includes the PDCP serial number (serial number, SN), and the PDCP SN can be set in different lines in. If configured in the figure, this field is optional, that is, it can be configured or not.
  • Figure 9 only shows a way of the location of the PDCP header, SDAP header, EHC header, Ethernet data payload and MAC-I.
  • the PDCP header, SDAP header, EHC header, Ethernet data payload and MAC-I The position of -I, the specific byte length, and the content contained can be adaptively set according to actual application scenarios, which are not specifically limited in the embodiment of the present application.
  • the length of PDCP SN may be 12 bits or 18 bits.
  • the SDAP header may be located between the EHC header and the Ethernet data payload, or the SDAP header may be located between the Ethernet data payload and the MAC-I, or the SDAP header may be located after the MAC-I.
  • the EHC header may include: indication field F, CID, and the Ethernet frame header; the indication field F is used to indicate whether the EHC header includes a complete or compressed Ethernet frame header or To indicate whether the Ethernet header is compressed, as an example, as shown in FIG. 10, the format of the EHC header of the embodiment of the present application is shown.
  • the length of the indication field F can be 1-3 bits, for example, the length of F can be 1 bit, and the value can be 1 or 0.
  • the decompressor can judge whether the data packet carries a compressed Ethernet frame according to the value of the F field. .
  • the compression end sends the compressed Ethernet frame to the decompression end, so the value of the F field indicates that the EHC header includes a compressed Ethernet frame header or indicates whether the Ethernet header is compressed.
  • the length of the context ID/CID field can be 2-16 bits.
  • the length of the context ID field can be 5 bits, or 6 bits, or 7 bits, or 8 bits, or 16 bits.
  • the Ethernet frame header field is the part of the original Ethernet frame header excluding the first field to be compressed.
  • the order of the above-mentioned fields may be that the F field precedes the CID field and the CID field precedes the Ethernet frame header field; or the CID field precedes the F field and the F field precedes the Ethernet frame header field. That is, the embodiment of the present application does not limit the sequence of these fields.
  • R reserved bits
  • the F field is 1 bit long
  • the CID field is 5 bits long
  • the EHC header may further include the profile ID, and the position of the profile ID may be between the CID and the Ethernet frame header, which is not specifically limited in the embodiment of the present application.
  • the above indication field F may also be used to indicate whether the first EHC header includes a profile ID.
  • a new indication field may be added to the EHC header to indicate whether the first EHC header includes a profile ID.
  • the corresponding relationship stored on the decompression end may include the profile ID or the default profile may be used, in an optional implementation of the embodiment of the present application, it may also be set not to include the profile ID in the EHC header of the compressed Ethernet frame , Which can further reduce the occupied space of the compressed Ethernet frame and further reduce the resource occupation.
  • Step S105 The decompression end receives an Ethernet frame, and the Ethernet frame includes a first correspondence identifier, that is, a first CID.
  • Step S106 The decompression end determines a first correspondence relationship including the first CID according to the first CID, the first correspondence relationship includes the correspondence relationship between the first compressed information and the value of the first field to be decompressed, the first compressed information Including the first CID.
  • the specific content of the first correspondence relationship may be the same as the specific content of the first correspondence relationship on the compression end.
  • the field in the first correspondence relationship corresponding to the first compressed information The value is referred to as the value of the first field to be decompressed.
  • the first compressed information is the same as the description of the compression end above. On the decompression end, it can also be called the first decompression information, and the content included is the same as the description of the compression end above.
  • the decompression terminal may store the correspondence between the compressed information and the value of the field to be decompressed, where the first correspondence is the correspondence between the first compressed information and the value of the first field to be decompressed.
  • the correspondence stored on the decompression end may include the first correspondence, that is, the first correspondence may be pre-stored in the decompression end; the correspondence stored on the decompression end may not include the first correspondence.
  • the first correspondence The corresponding relationship may also be received by the decompression end in real time or from the compression end during data stream transmission.
  • the embodiment of the present application does not specifically limit the manner in which the decompression terminal obtains the first correspondence.
  • the method for the decompression end to obtain the first correspondence can be determined according to actual application scenarios. In the subsequent embodiments, the method for the decompression end to obtain the first correspondence will be further described, which will not be repeated in the embodiments of the present application.
  • the decompression end may determine the value of the field to be decompressed included in the first correspondence as the value of the first field to be decompressed in the Ethernet frame header of the Ethernet frame.
  • Each corresponding relationship in the corresponding relationship may be associated with a corresponding relationship identifier, and the compressed information may include the identifier of the corresponding relationship.
  • the first compressed information includes the identifier of the first corresponding relationship.
  • the compressed information may further include the profile ID, so that the first compressed information may also include the first profile ID.
  • the profile ID can be used to identify the profile, and the profile is used to specify the compression mechanism.
  • the profile is used to indicate the compressible fields and/or the compression method. Different profiles are distinguished by the profile ID.
  • the profile ID is used to indicate the communication protocol of the Ethernet frame header and/or the field to be compressed of the Ethernet frame header.
  • the compression information may not include the profile ID.
  • the decompression terminal may also store an indicator variable of each correspondence, which is used to indicate whether the compression information of each correspondence is used for compression.
  • the decompression end can store context information, where the context information can include at least one context entry.
  • the description of the context information is the same as that in the above embodiment, and will not be repeated here.
  • Step S107 The decompression end decompresses the Ethernet frame header of the Ethernet frame according to the first compression information and the value of the first field to be decompressed.
  • the decompression end may use the reverse process of the compression end to decompress the Ethernet frame header.
  • the decompression end determines the first correspondence between the first CID according to the first CID, so that the value of the first field to be decompressed can be found. If the first correspondence or the first compression information includes the profile ID, the profile can be determined according to the profile ID, and the first field to be decompressed can be found according to the compression field specified by the profile. If the first correspondence does not include the profile ID, the first field to be decompressed can be found according to the compressed field specified by the default profile.
  • the first field to be decompressed may be one or more fields in the Ethernet frame header, and which field or fields are specifically included may be determined according to the profile.
  • the first field to be decompressed is a field in the Ethernet frame header
  • the value of the first field to be decompressed in the first correspondence is filled in the field of the Ethernet frame header to realize the decompression of the Ethernet frame header of the Ethernet frame to be decompressed ;
  • the value of the first field to be decompressed in the first correspondence is split into the multiple fields according to the size of the multiple fields Take the value and fill in the multiple fields respectively to realize the decompression of the Ethernet frame header of the Ethernet frame to be decompressed.
  • the first field to be decompressed includes multiple fields of the Ethernet frame header, such as destination MAC address, source MAC address, and MAC client length/type.
  • the decompression end determines the specific selection of the first field to be decompressed according to the first CID. After the value is set, when the original Ethernet frame header is restored, the corresponding field value is filled in the corresponding Ethernet frame header field position. For example, the decompression terminal fills the destination MAC address value in the destination MAC address field position, and the source MAC address field position fills the source MAC address. Address value, MAC client length/type field position is filled with MAC client length/type value. It can be understood that, in actual applications, a decompression method corresponding to the compression method of the compression end may also be used for decompression according to actual application scenarios, which is not specifically limited in the embodiment of the present application.
  • the compression end may include the first correspondence between the first compression information and the value of the first field to be compressed, according to the first Compression information compresses the Ethernet frame header of the Ethernet frame. If it is adapted, the decompression end can decompress the Ethernet frame header of the compressed Ethernet frame according to the first correspondence when receiving the compressed Ethernet frame. In the embodiment of this application, because the Ethernet frame header of the Ethernet frame is compressed, communication resources can be saved.
  • the first correspondence in the embodiment of the present application can be generated by the compression end and synchronized at the decompression end. After the synchronization of the first correspondence is completed at the decompression end, the decompression end and the compression end can adapt according to the first correspondence. Compression and decompression operations.
  • FIG. 12 is a schematic flowchart of a method for synchronizing a first correspondence between a compression end and a decompression end according to an embodiment of the present application. As shown in FIG. 12, the method provided in this embodiment of the present application includes the following steps:
  • Step S201 The compression end generates a first correspondence.
  • the compression terminal may generate the first correspondence relationship based on the fields to be compressed included in the received Ethernet frame.
  • the Ethernet frame received by the compression end may be the same or different from the Ethernet frame in the embodiment corresponding to FIG. 7, and the value of the field to be compressed in the Ethernet frame header of the Ethernet frame in the embodiment of this application is the same as The values of the first field to be compressed in the embodiment corresponding to FIG. 7 are the same.
  • the field to be compressed is the same as the description in the above embodiment, and can be one or more fields in the Ethernet frame header.
  • the compression end can also be based on the destination MAC address, source MAC address, length/type field, TAG control information, and MAC client
  • One or more of the fields such as end length/type generates the first correspondence.
  • the embodiment of the present application does not limit the specific manner of generating the first correspondence.
  • the compression terminal may store a pre-generated correspondence, and the correspondence includes the correspondence between the compression information and the value of the field to be compressed.
  • the compression end After the compression end receives the Ethernet frame including the first field to be compressed, when the corresponding relationship stored by the compression end does not include the value of the first field to be compressed of the Ethernet frame, the compression end generates the first corresponding relationship, and
  • the first correspondence may include: the value of the CID and the first field to be compressed.
  • the corresponding relationship can be stored in the form of context information, which will not be repeated here.
  • the value of the first field to be compressed is the value of the one field; when the first field to be compressed is multiple fields, the value of the first field to be compressed is the multiple.
  • the combination of the values of two fields can be specified by the profile.
  • the combination of the values of multiple fields can be determined according to the profile. For example, if the position relationship of each field is specified in the profile, it can be combined according to the order of the positions of the fields, which is not specifically limited in the embodiment of the present application.
  • the current compression end saves the correspondence between CID 1 and CID2, the value of the field to be compressed of CID 1 is A, and the value of the field to be compressed of CID 2 is B.
  • the compression end allocates a new CID for the first field to be compressed, such as CID3.
  • the compressed information further includes the profile ID.
  • the compression and decompression ends can determine the profile as the default profile.
  • they can be compressed or decompressed based on the profile, then the information is compressed It is not necessary to include the profile ID.
  • Step S202 The compression end sends the first correspondence to the decompression end.
  • the compression end may send the first corresponding relationship to the decompression end in an adaptive manner according to the actual application scenario, which is not specifically limited in the embodiment of the present application.
  • the compression end sends an uncompressed data packet to the decompression end, and the uncompressed data packet includes the first correspondence.
  • the compression end may send the first correspondence and the received Ethernet frame as an uncompressed data packet to the decompression end.
  • the compression end can send uncompressed data packets to the decompression end through PDCP data PDU; in another optional implementation, the compression end can control the protocol data unit PDCP through the packet data convergence protocol The control PDU sends the first pair of relationships to the decompression end, and the Ethernet frame data packet is sent to the decompression end through the PDCP data PDU.
  • the compression end may send the first correspondence to the decompression end multiple times, and the adapted first correspondence may also correspond to a set threshold value, for example, the compression end pair
  • the first correspondence maintains a variable of sending times.
  • the initial value of this variable can be 0.
  • the compression end sends the first correspondence once the sending times variable accumulates 1.
  • the number of times the first correspondence is sent from the compression end to the decompression end
  • the number threshold it can be considered that the decompression end has successfully received the first correspondence, and it can be considered that the first correspondence has been synchronized between the compression end and the decompression end, and the step S204 may not be performed.
  • the frequency threshold can be predefined by the protocol, or a number configured by the network device that is greater than or equal to 1.
  • the frequency threshold can also be determined by the compressor itself, or configured by other terminal equipment For the compression end, this embodiment of the application does not specifically limit this.
  • Step S203 The decompression end receives the first correspondence from the compression end.
  • the decompression end may receive the first correspondence from the compression end in an adaptive manner according to the actual application scenario, and the embodiment of the present application does not limit the specific manner of receiving.
  • the decompression end stores the first correspondence.
  • the decompression end after the decompression end receives the first correspondence, when the correspondence stored by the decompression end includes the first compressed information, and the first compressed information corresponds to the field to be decompressed.
  • the value is different from the value of the first field to be decompressed, and the decompression end modifies the value of the field to be decompressed corresponding to the first compressed information to the first field to be decompressed.
  • the decompression terminal may also store the corresponding relationship in the form of context information, which will not be repeated here.
  • Step S204 The decompression end sends feedback information to the compression end, where the feedback information is used to indicate the reception status of the first correspondence.
  • the decompression end may also send feedback information to the compression end, where the feedback information is used to indicate the reception status of the first correspondence.
  • the receiving status may include receiving success or receiving failure. It can be understood that, when the receiving state is successful, the compression end and the decompression end may perform corresponding compression and decompression processing based on the first correspondence. When the receiving state is reception failure, the compression end and the decompression end cannot perform corresponding compression and decompression processing based on the first correspondence. Further, the compression end can resend the first correspondence to the compression end, or delete the first correspondence.
  • the corresponding relationship, etc. are not specifically limited in the embodiment of the present application.
  • the feedback information includes the CID or the PDCP SN confirming the data packet carrying the first correspondence. Then the compression end can determine the specific correspondence between unsuccessful reception based on the CID or PDCP SN.
  • the feedback information further includes at least one of the following: profile ID, a first indication field, and a second indication field.
  • the first indication field is used to indicate that the first correspondence is at the decompression end. It is a new correspondence or a modified correspondence
  • the second indication field is used to indicate whether the feedback information is positive feedback or negative feedback.
  • the feedback information is sent through PDCP control PDU, and includes a CID field, a first indication field (AddOrModify), and a second indication field (AckType).
  • the first byte is the header of the PDCP control PDU, where the value of the D/C field indicates that the PDCP PDU is a control PDU, and the value of the PDU type (type) indicates that the control PDU is a control PDU used to transmit feedback information, for example
  • the value of PDU type can be a value other than '000' and '001', such as '010' or '011'.
  • the length of the context ID/CID field can be 2-16 bits, for example, the length of the context ID field can be 5 bits, or 6 bits, or 7 bits, or 8 bits, or 16 bits; the value of the AckType field length It can be 1-4 bits. For example, the length of the AckType field is 1 bit, and the value is 1 or 0.
  • the length of the AddOrModify field can be 1-4 bits, for example, the length of the AddOrModify field is 1 bit, and the value is 1 or 0,
  • the sequence of the above-mentioned fields may be CID field, AckType field, AddOrModify field; AckType field, CID field, AddOrModify field; AckType field, AddOrModify field, CID field.
  • the embodiments of this application do not make limitations.
  • the PDCP control PDU used for feedback is byte-aligned
  • there may be one or more reserved bits in the control PDU as shown in FIG. 13, for example Under the premise of the sequence of the fields, there is at least one reserved bit in at least one position between the PDCP control PDU header and the CID, between the CID field and the AckType field, and between the AckType field and the AddOrModify field.
  • the compression terminal also stores an indicator variable of each corresponding relationship, and the indicator variable is used to indicate whether the compressed information of the corresponding corresponding relationship is used for compression.
  • the compression end An indicator variable of the corresponding relationship may also be stored, and the indicator variable is used to indicate whether the compression information of the corresponding relationship is used for compression.
  • the value of the indicator variable may include 0 and 1. When the indicator variable is 1, it means that the first correspondence is available, and when the indicator variable is 0, it means that the first correspondence is not available. Compression; Or, when the indicator variable is 0, it means that the first correspondence is available, and when the indicator variable is 1, it means that the first correspondence is not available for compression.
  • the compression end sends the first correspondence to the decompression end.
  • the manner in which the compression end sends the first correspondence to the decompression end refers to the record of step S202, which will not be repeated here.
  • the compression end when the compression end confirms that the first correspondence is correctly received by the decompression end, the compression end sets the indicator variable to a first value, and the first value is used to indicate that the compression information is used for compression.
  • the compression end can confirm that the first correspondence is correctly received by the decompression end in multiple ways.
  • the compression end may send the first correspondence to the decompression end N times, and N is greater than or equal to 1.
  • the compression end confirms that the first correspondence is correctly received by the decompression end; or, if the compression end receives the feedback information sent by the decompression end to indicate that the first correspondence is correctly received, the compression end confirms that the first correspondence is correctly received.
  • the corresponding relationship is correctly received by the decompression terminal.
  • the implementation of this application does not limit the specific manner in which the compression end confirms that the first correspondence is correctly received by the decompression end.
  • the first value may be set according to actual application scenarios, for example, may be 1 or 0, which is not specifically limited in the embodiment of the present application.
  • the indicator variable of the first correspondence relationship may be set to a second value, and the second value is used to indicate that the compression information cannot be used for compression.
  • the second value can be set according to actual application scenarios, for example, it can be 0 or 1, which is not specifically limited in the embodiment of the present application.
  • the embodiment of the present application may further include: the compression end sends second indication information to the decompression end, the second indication information is used to indicate that the first correspondence is newly added at the compression end Correspondence or modified correspondence.
  • the second indicator information may be used to indicate that the first correspondence relationship is in the compression The end is the new correspondence or the modified correspondence.
  • the compression and decompression can be synchronized between the compression end and the decompression end, and the subsequent transmission of Ethernet data packets between the compression end and the decompression end can be based on the synchronization corresponding relationship, Compressing and decompressing the Ethernet frame header can reduce the occupation of communication resources by the Ethernet frame header.
  • step S202 may include: the compression end sends the uncompressed data packet to the decompression end through PDCP data PDU.
  • the decompression end sends the first correspondence; where the PDCP data PDU includes: an EHC header, the EHC header includes an indication field, the CID, and the Ethernet frame header; the indication field is used to indicate whether the EHC header includes a complete Or compressed Ethernet header or used to indicate whether the Ethernet header is compressed.
  • the indication field F of the EHC header can be used to indicate whether the EHC header includes a complete or compressed Ethernet frame header. Or it is used to indicate whether the Ethernet frame header is compressed.
  • the length of the indication field F can be 1-3 bits.
  • the length of F can be 1 bit, and the value can be 1 or 0.
  • the decompression end according to the F field The value can determine whether the data packet carries a complete Ethernet frame header.
  • the length of the CID field can be 2-16 bits.
  • the length of the CID field can be 5 bits, or 6 bits, or 7 bits, or 8 bits, or 16 bits; this field indicates the header compression used for the Ethernet frame Corresponding to the compressed information identifier.
  • the Ethernet frame header field is the original Ethernet frame header, including fields to be compressed and fields not to be compressed.
  • the sequence of the above-mentioned fields can be F field, CID field, Ethernet frame header; or CID field, F field, Ethernet frame header.
  • the EHC is byte-aligned.
  • the EHC is byte-aligned.
  • the F field is 1 bit long
  • the CID field is 6 bits long
  • the indication field F is also used to indicate whether the first EHC header includes the profile ID profile ID.
  • the indication field F indicates that the profile ID is included, the EHC header also includes the profile ID.
  • a new indication field may be added to the EHC header to indicate whether the first EHC header includes a profile ID.
  • the indication field F of the EHC header may be used to indicate whether the EHC header includes a complete or compressed Ethernet frame header , And whether to carry the profile ID.
  • the length of the indication field F can be 1-3 bits.
  • the length of F can be 1 bit, and the value can be 1 or 0.
  • the decompression end can determine that the data packet carries a complete Ethernet header according to the value of the F field. And it carries the profile ID field.
  • the length of the CID field can be 2-16 bits.
  • the length of the CID field can be 5 bits, or 6 bits, or 7 bits, or 8 bits, or 16 bits; this field indicates the header compression used for the Ethernet frame Corresponding to the compressed information identifier.
  • the length of the profile ID field can be 2-8 bits.
  • the length of the profile ID field can be 4 bits, or 5 bits, or 6 bits, or 8 bits.
  • the Ethernet frame header field is the original Ethernet frame header, including fields to be compressed and fields not to be compressed.
  • the sequence of the above-mentioned fields can be F field, CID field, profile ID field, and Ethernet frame header; or CID field, F field, profile ID field, and Ethernet frame header.
  • the EHC is byte-aligned.
  • at least one reserved bit may exist in at least one position before the F field, between the F field and the CID field, between the CID field and the profile ID field, and between the profile ID field and the Ethernet frame header.
  • the F field is 1 bit long
  • the CID field is 6 bits long
  • the profile ID is 6 bits long
  • the PDCP data PDU further includes: a PDCP header, a service data adaptation layer SDAP header, an Ethernet data payload, and MAC-I. It is similar to the format of PDCP data PDU in FIG. 9, and will not be repeated here.
  • step S202 may include : The compression end sends the first corresponding relationship to the decompression end through PDCP control PDU; where the PDCP control PDU includes indication information, the CID and the value of the compressible field of the Ethernet frame header; the indication information is used to indicate the PDCP The control PDU is used for the first correspondence.
  • the PDCP control PDU may not include the value of the field to be compressed. Instead, it subsequently sends a PDCP data PDU to the decompression end.
  • the PDCP data PDU has an Ethernet frame header and the value of the field to be compressed in the Ethernet frame header. Equal to the value of the field to be compressed.
  • the indication information is PDU Type
  • the first byte is PDCP
  • the header of the control PDU where the value of the D/C field indicates that the PDCP PDU is a control PDU
  • the value of PDU type indicates that the control PDU is a control PDU used to transmit the first corresponding relationship.
  • the value of the PDU type can be divided by Values other than '000' and '001', such as '010', or '011', etc.
  • the length of the CID field can be 2-16 bits.
  • the length of the CID field can be 5 bits, or 6 bits, or 7 bits, or 8 bits, or 16 bits; this field indicates the header compression used for the Ethernet frame Corresponding to the compressed information identifier.
  • the value of the field to be compressed is the value of the first field to be compressed in the first relationship corresponding to the CID field, that is, only the specific value of the field to be compressed in the Ethernet frame header is included.
  • the sequence of the above-mentioned fields may be the CID field, the value of the field to be compressed; or the CID field, the value of the field to be compressed.
  • control PDU in order to ensure that the PDCP control PDU is byte-aligned, there may be one or more reserved bits in the control PDU, for example, as shown in FIG. 18 Under the premise of the field order, as shown in FIG. 19, there may be at least one reserved bit R between the control PDU header and the CID field.
  • the PDCP control PDU further includes: the profile ID.
  • the PDCP control PDU also includes a profile ID, where the value of the D/C field indicates that the PDCP PDU is a control PDU, and the value of PDU type indicates that the control PDU is used to transmit the first correspondence.
  • Control PDU for example, the value of PDU type can be a value other than '000' and '001', such as '010' or '011'.
  • the length of the context ID/CID field can be 2-16 bits.
  • the length of the context ID field can be 5 bits, or 6 bits, or 7 bits, or 8 bits, or 16 bits; this field indicates the The corresponding compression information identifier used for header compression of the Ethernet frame.
  • the length of the profile ID field can be 2-8 bits.
  • the length of the profile ID field can be 4 bits, or 5 bits, or 6 bits, or 8 bits.
  • the value of the field to be compressed is the value of the first field to be compressed in the first relationship corresponding to the CID field, that is, only the specific value of the field to be compressed is included.
  • the sequence of the above-mentioned fields may be the CID field, the profile ID field, and the value of the field to be compressed; or the profile ID field, the CID field, and the value of the field to be compressed. That is, the embodiment of the present application does not limit the sequence of these fields.
  • the control PDU in order to ensure that the PDCP control PDU is byte-aligned, there may be one or more reserved bits in the control PDU, for example, as shown in FIG. 20
  • the compression end also sends PDCP data PDU to the decompression end; wherein the PDCP data PDU includes: an EHC header, the EHC header carries an indication field and the Ethernet frame header; the indication field is used to indicate the EHC Whether to carry CID in the header.
  • the length of the indication field F can be 1-3 bits.
  • the length of F can be 1 bit and the value can be 1 or 0.
  • Frame header In this step, the compression end sends an uncompressed Ethernet frame to the decompression end, so the value of the F field indicates that the EHC header includes a compressed Ethernet frame header or indicates whether the Ethernet header is compressed.
  • the Ethernet header field is the original Ethernet header or the compressed Ethernet header after removing the fields to be compressed is indicated by the indication field F.
  • the Ethernet frame header is a compressed Ethernet frame header, or when the EHC header does not carry a CID, the Ethernet frame header is a complete Ethernet frame header.
  • the format of the EHC header may be as shown in Figure 23.
  • the length of the context ID/CID field can be 2-16 bits.
  • the length of the context ID field can be 5 bits, or 6 bits, or 7. Bit, or 8 bits, or 16 bits; this field indicates the corresponding compression information identifier used for header compression of the Ethernet frame; when the value of F indicates that the subsequent Ethernet frame header is the original frame header, the decompression end can ignore the CID field
  • the specific value or the CID field does not exist in the EHC header. At this time, in order to ensure the byte alignment of the EHC header, the extra bit positions can be filled with reserved bits.
  • Ethernet header field is the original Ethernet header or the compressed Ethernet header after removing the first field to be compressed is indicated by the F indicator field.
  • the order of the above-mentioned fields may be that the F field precedes the CID field and the CID field precedes the Ethernet frame header field; or the CID field precedes the F field and the F field precedes the Ethernet frame header field. That is, the embodiment of the present application does not limit the sequence of these fields.
  • the first PDCP data PDU further includes: a PDCP header, a service data adaptation layer SDAP header, an Ethernet data payload, and MAC-I. It is similar to the format of PDCP data PDU in FIG. 9, and will not be repeated here.
  • the compression end transmits the compressed ether frame to the decompression end and the decompression end decompresses the compressed ether frame in the embodiment of the present application
  • a verification process can also be set to improve the correct rate of compression and decompression. Therefore, in step S104, the EHC header used to send the PDCP data PDU of the compressed Ethernet frame to the decompression end further includes: verification information.
  • FIG. 24 a schematic diagram of the format of an EHC header including a check code is shown.
  • the check code can be located between the profile ID and the Ethernet frame header. It can be understood that when the profile ID is not included in the EHC header, the check code is
  • the verification code can be located between the CID and the Ethernet frame header, and the verification code can also be located after the Ethernet frame header, or between the F field and the CID, that is, the embodiment of the present application does not limit the sequence of these fields.
  • one or more reserved bits can also be added adaptively in the EHC header, which is not specifically limited in the embodiment of the present application.
  • the verification information is generated according to one or more pieces of information in the first correspondence.
  • the check information may be a cyclic redundancy check (cyclic redundancy check, CRC) or a checksum (checksum).
  • CRC cyclic redundancy check
  • checksum checksum
  • the check information is CRC
  • the compression end receives the Ethernet frame, it is based on the value of the corresponding compression field in the correspondence to be used, the complete CID, One or more of the complete profile ID, original Ethernet frame header, etc. are used as input, and X (X can be determined according to actual applications) bits of first check information CRC 1 are generated through a certain generator polynomial.
  • the decompression end can also determine the corresponding relationship to be used for decompression based on the CID in the EHC header, and/or profile ID, and based on the value of the corresponding compressed field in the corresponding relationship, the complete CID
  • the X-bit second check information CRC 2 is generated through the same generator polynomial as the compression end. If CRC 2 ⁇ CRC 1 , it is confirmed that the decompression has failed; or the decompression end cannot find the context information corresponding to the CID, and it is also confirmed that the decompression has failed.
  • the check information is checksum
  • the compression end receives the Ethernet frame, it is based on the value of the corresponding compression field in the correspondence to be used, and the complete CID , One or more of the complete profile ID, the original Ethernet frame header, etc. are used as input, and a checksum algorithm is used to generate X (X can be determined according to the actual application) bits of the first checksum information checksum1.
  • the decompression end can also determine the corresponding relationship to be used for decompression based on the CID in the EHC header, and/or profile ID, and based on the value of the corresponding compressed field in the corresponding relationship, the complete CID
  • the X-bit second checksum information checksum 2 is generated through the same checksum algorithm as the compression end. If checksum 2 ⁇ checksum 1 , it is confirmed that the decompression failed; or the decompression end cannot find the context information corresponding to the CID, and it is also confirmed that the decompression failed.
  • the decompression end decompresses the Ethernet frame header of the Ethernet frame to be decompressed according to the value of the first field to be decompressed; or In the case that the first verification information is different from the second verification information, the decompression end deletes the first correspondence; and/or, the decompression end sends an error report to the compression end.
  • the decompression end when the first verification information is different from the second verification information, the decompression end confirms that the verification fails, the decompression end may delete the first correspondence stored in the decompression end, or send to the compression end Error report, or delete the first corresponding relationship stored in the decompression end and send an error report to the compression end, which is not specifically limited in the embodiment of the present application.
  • the error report can be used to indicate that the verification fails, and the decompression end cannot achieve decompression of the compressed Ethernet frame.
  • the error report can carry CID, and/or profile ID.
  • the error report may also carry CRC3, which is generated by using a generator polynomial based on the error report itself as input.
  • the compression end may delete the first correspondence relationship, or the compression end may set the first correspondence relationship Is not available.
  • the compression terminal may set the indicator variable corresponding to the first correspondence to the second value to indicate that the first correspondence is not available.
  • the first correspondence also corresponds to the directed decompression terminal
  • the number of transmissions can be set to the initial value.
  • the initial value can be 0.
  • the decompression end when the decompression end confirms that the verification error occurs, it can clear all the correspondences stored on the decompression end and feed back an error report to the compression end.
  • the error report does not carry CID, profile ID .
  • the compressor can clear all correspondences or set all correspondences as unavailable. If the correspondence still corresponds to the number of transmissions, the number of transmissions is set to the initial value (for example, 0).
  • a verification mechanism is introduced to avoid the inconsistency of the correspondence between the compression end and the decompression end, resulting in errors in the decompression of data packets, and the accuracy of compression and decompression is improved.
  • the compression end and decompression end of the embodiment of the present application may also be pre-configured with the ability to execute EHC before performing the foregoing compression and decompression implementation.
  • the compression end is a terminal
  • the decompression end is a network device
  • the method further includes:
  • the compression terminal sends capability information to the decompression terminal;
  • the capability information includes at least one of the following: the capability of the compression terminal to support EHC, and the compression of the number of data radio bearers (DRBs) that support EHC in the compression terminal Compression side Compression side Compression side
  • the compression side supports the configuration file profile information compression side Compression side, the maximum value of the corresponding relationship entries supported by each DRB supporting EHC MAX_CID Compression side
  • the compression side supports dynamic configuration of profile parameters Capability Compression side Compression side
  • the compression side supports the sum of correspondence entries maintained by DRB of EHC Compression side Compression side Compression side Compression side Compression side Compression side Compression side Compression side Compression side Compression side Compression side Compression side Compression side Compression side Compression side Compression side Compression side Compression side Compression side Compression side Compression side Compression side Compression side Compression side Compression side Compression side Compression side Compression side Compression side Compression side Compression side Compression side Compression side Compression side Compression
  • the ability of the compression end to support EHC may specifically include the ability of the compression end to support uplink EHC, and/or the ability of the compression end to support downlink EHC, and the number of DRBs in the compression end that support EHC Used to indicate the maximum number of DRBs that the compressor can be configured to perform EHC operations.
  • the maximum number of DRBs that the compressor supports EHC can be specified by the protocol, or it indicates that the compressor supports DRBs of EHC. There is no limit to the number.
  • the profile information of the configuration file supported by the compression end may specifically include the uplink profile information supported by the compression end, and/or the downlink profile information supported by the compression end, which can be used to indicate which Ethernet protocols corresponding to which profiles the compression end can handle EHC processing of the frame, when this information is not indicated, it means that the compression end supports the EHC processing of the Ethernet protocol frame corresponding to the profile defined by all protocols.
  • Other capabilities such as the number of MAX_CIDs supported by a DRB, and the total number of CIDs supported can be divided into uplink and/or downlink for indication respectively.
  • the MAX_CID supported by a DRB can be specified by the protocol, or it means that there is no limitation.
  • the compression terminal does not indicate the capability information of the compression terminal to support the dynamic configuration of profile parameters, it means that the compression terminal supports/does not support the dynamic configuration of the profile parameters of the network device.
  • the compression side saves and maintains a correspondence, a certain amount of memory is required to store the correspondence. From the perspective of the terminal device, the supported memory is limited, so the memory that can be used to store the correspondence may also be limited. ;
  • the compression end does not indicate the sum of the correspondence entries maintained by the DRB of the compression end supporting EHC, the total number of correspondence relations supported by the compression end may be specified by the protocol, or it means that there is no limit.
  • the capability information may further include: the compression end supports the ability to process feedback information from the decompression end. When the compression end does not indicate the information, it means that the compression end supports/does not support feedback information processing.
  • the capability information may further include the capability of the compression terminal to support multiple transmissions of the first correspondence relationship. When the compression terminal does not indicate the information, it indicates that the compression terminal supports/does not support multiple transmissions of the first correspondence relationship.
  • the compression end may send capability information to the decompression end through a radio resource control (RRC) message, and may also send capability information to the decompression end in other ways, which is not specifically limited in this embodiment of the application.
  • RRC radio resource control
  • the decompression end can configure at least one of the following for the compression end: information about DRB or PDCP entities that support uplink EHC, information about DRB or PDCP entities that support downlink EHC, and DRB or PDCP entities that support uplink EHC.
  • Information about DRB or PDCP entities that support uplink EHC information about DRB or PDCP entities that support downlink EHC
  • DRB or PDCP entities that support uplink EHC DRB or PDCP entities that support uplink EHC.
  • Supported profile information, profile information supported by DRB or PDCP entities that support downlink EHC, the maximum value of compression context information entries used by each DRB or PDCP entity to perform EHC operations, and the compressor that supports EHC The total number of compressed context information entries maintained by the DRB, the EHC performs the feedback operation, the EHC performs the operation of sending the first correspondence multiple times, and the sending times threshold when the first correspondence is sent multiple times.
  • the decompression end may configure the foregoing content for the compression end through
  • MAX_CID is configured in the compression end, if it is found that the entry in the previously stored correspondence has reached MAX_CID, no new correspondence is established for subsequent data packets , And only use the existing correspondence to compress the data packet. If the newly arrived data packet can’t find the correspondence, it will not be compressed; for example, the CID in the compression terminal has been used up, and subsequent data packets can be compressed. , The data packet does not carry the first correspondence when it is sent, or the terminal may not perform compression processing on some data packets based on implementation.
  • the format of the data packet encapsulation can be considered in two ways: one of them is that the EHC header in the PDCP data PDU does not contain the profile ID field, the F field in the EHC header indicates that the data packet is an uncompressed data packet, and the context ID
  • the value of the field is a reserved value, such as all 0s or all 1s.
  • the F field in the EHC header indicates that the data packet is an uncompressed data packet.
  • the Context ID and/or profile ID field takes a reserved value, such as full 0 or all 1 values, the compression end receives the data packet, according to the value of the F field and the reserved value of the CID and/or the reserved value of the profile ID, it can be judged that the data packet is an uncompressed data packet and does not carry the first One correspondence.
  • the compression end when MAX_CID is configured in the compression end, if it is found that the entry in the previously stored correspondence relationship has reached MAX_CID, the compression end still generates the first correspondence relationship, and can Replace any item in the previously stored correspondence relationship with the first correspondence relationship, so as to realize the storage of the first correspondence relationship. Any of the above-mentioned items may be randomly selected by the compression end or determined by other means. This embodiment does not Make a limit.
  • the method further includes: the terminal receives configuration information, the configuration information is also used to indicate whether the EHC header carries the profile ID; or, the configuration information also includes the profile ID, and the The EHC header does not include the profile ID.
  • the EHC header of the DRB data packet does not carry the profile ID, otherwise the EHC header needs to carry the profile ID.
  • the terminal can receive the configuration information sent by the network device through the RRC, and the RRC can indicate whether the EHC header carries the profile ID through a certain field.
  • a presence of profileID field can be used to indicate whether the EHC header carries the profile ID; for example, if the presence of profileID field is carried in the PDCP configuration cell, it means that the EHC header carries the profile ID. If the presence of profileID is not carried Field, the EHC header does not carry the profile ID.
  • the presence of profileID can be set to 1 or 0.
  • 1 means that the EHC header carries the profile ID
  • 0 means that the EHC header does not carry the profile ID.
  • 0 means that the EHC header carries the profile ID
  • 1 means that the EHC header does not carry the profile ID.
  • the presence of profileID fields can be configured for the uplink EHC and downlink EHC operations of the terminal, respectively, to indicate whether the profile ID is carried in the uplink and downlink EHC headers.
  • the presence of profileID-UL field is configured to indicate whether the profile ID is carried in the uplink EHC header
  • the presence of profileID-DL field is configured to indicate whether the profile ID is carried in the downlink EHC header.
  • the presence of profileID-UL can be set to 1 or 0. 1 means that the uplink EHC header carries the profile ID, 0 means that the uplink EHC header does not carry the profile ID, or 0 means that the uplink EHC header carries the profile ID, and 1 means that the uplink EHC header carries the profile ID.
  • the header does not carry the profile ID.
  • Set the presence of profileID-DL to 1 or 0. 1 means the downlink EHC header carries the profile ID
  • 0 means the downlink EHC header does not carry the profile ID
  • 0 means the downlink EHC header carries the profile ID
  • 1 means The downstream EHC header does not carry the profile ID.
  • the embodiment of the present application does not specifically limit the value of each field.
  • the EHC data packet of the DRB carries the profile ID field according to the number of profiles supported by the RRC configuration DRB. For example, if the number of profiles supported by the RRC configuration DRB is 1, then it can be regarded as an indication not to carry profile ID, if the number of profiles supported by the RRC configuration DRB is greater than 1, the task indicator can carry the profile ID.
  • the profile ID of the terminal can be configured through the configuration information, so that the profile ID may not be included in the EHC header, thereby reducing the size of the EHC header. Size, reduce the occupation of communication resources.
  • the compression end is a network device, and the decompression end is a terminal, and the method further includes:
  • the compression terminal receives capability information, and the capability information includes at least one of the following: the capability information includes at least one of the following: the capability of the decompression terminal to support EHC, the number of data radio bearer DRBs in the decompression terminal that supports EHC, The profile information of the configuration file supported by the decompression terminal, the maximum value MAX_CID of the corresponding relationship entry supported by each DRB that supports EHC, the decompression terminal supports the ability to dynamically configure profile parameters, and the decompression terminal supports the correspondence maintained by the DRB of EHC The sum of entries.
  • the compression end after receiving the capability information of the decompression end, can adapt at least one item: DRB supporting uplink EHC or PDCP entity information, and DRB or PDCP supporting downlink EHC Entity information, configuration file information supported by the DRB or PDCP entity supporting uplink EHC, configuration file information supported by the DRB or PDCP entity supporting downlink EHC, and compression context information used by each DRB or PDCP entity when performing EHC operations
  • DRB supporting uplink EHC or PDCP entity information DRB or PDCP supporting downlink EHC Entity information
  • configuration file information supported by the DRB or PDCP entity supporting uplink EHC configuration file information supported by the DRB or PDCP entity supporting downlink EHC
  • compression context information used by each DRB or PDCP entity when performing EHC operations
  • the compression end may configure the foregoing content for the decompression end through RRC signaling.
  • the method further includes: the network device sends configuration information to the terminal, the configuration information is also used to indicate whether the EHC header carries the profile ID; or, the configuration information also includes the profile ID, and the EHC header does not include the profile ID.
  • the compression end is a terminal
  • the decompression end is a terminal
  • the method further includes:
  • the compression terminal receives capability information, and the capability information includes at least one of the following: the capability information includes at least one of the following: the capability of the decompression terminal to support EHC, the number of data radio bearer DRBs in the decompression terminal that supports EHC, The profile information of the configuration file supported by the decompression terminal, the maximum value MAX_CID of the corresponding relationship entry supported by each DRB that supports EHC, the decompression terminal supports the ability to dynamically configure profile parameters, and the decompression terminal supports the correspondence maintained by the DRB of EHC The sum of entries.
  • the compression terminal may receive the capability information of the decompression terminal through a sidelink message, or receive the capability information of the decompression terminal through a base station or other terminal, which is not specifically limited in this embodiment of the application.
  • the decompression end may also receive the capability information of the compression end to realize the interaction of capability information between the decompression end and the compression end, which will not be repeated here.
  • the compression end and the decompression end may also exchange configuration information, which is also used to indicate whether the EHC header carries a profile ID; or, the configuration information also includes a profile ID, and the The EHC header does not include the profile ID. I won't repeat them here.
  • the compression end or the decompression end is switched.
  • the compression end when the compression end is a terminal and the decompression end is a network device, the compression end may switch to a different In the switching process, the decompression end of the initial communication of the compression end can be called the source station, and the decompression end that the compression end will switch to communicate is called the target station.
  • the source station can use the switching request message ( handover request, HR) Submit some or all DRB correspondences in the source station to the target station.
  • the target station can configure EHC to keep (continue) for some or all DRBs of the compression end.
  • the compression end does not need to clear the corresponding DRB correspondence relationship, and can continue to use the original correspondence relationship to perform EHC operations, thereby reducing the compression end
  • the number of times the corresponding relationship is generated can reduce the occupation of computing resources; the target station can also not configure EHC continue for some or all of the DRBs on the compression side.
  • the compression side can clear the corresponding DRB correspondences, thereby reducing the storage space occupation .
  • the compression end and the decompression end are re-established.
  • the corresponding relationship saved in the compression end and the decompression end are saved.
  • the correspondence relationship can be kept unchanged, so that the compression end and the decompression end can continue to use the original correspondence relationship to perform EHC operations after reconstruction, thereby reducing the number of times the compression end generates the correspondence relationship and reducing the occupation of computing resources.
  • the corresponding relationship stored in the compression end and the corresponding relationship stored in the decompression end can also be cleared, thereby reducing the occupation of storage space.
  • a device for implementing any of the above methods.
  • a device is provided that includes units (or means) for implementing each step performed by the terminal device in any of the above methods.
  • another device is also provided, including a unit (or means) for implementing each step performed by the access network device in any of the above methods.
  • another device is also provided, including a unit (or means) for implementing each step executed by the core network device in any of the above methods.
  • FIG. 25 is a schematic diagram of an Ethernet frame header compression apparatus provided by an embodiment of the application.
  • the device is used for the compression end.
  • the device 2500 includes a receiving unit 2510, a determining unit 2520, and a compression unit 2530.
  • the receiving unit 2510 is used to receive the first Ethernet frame.
  • the Ethernet header of the first Ethernet frame includes the first field to be compressed.
  • the determining unit 2520 is used to determine the Ethernet of the first Ethernet frame according to the first correspondence and the first field to be compressed.
  • the first compression information of the frame header, the first correspondence relationship includes the correspondence relationship between the first compression information and the value of the first field to be compressed, the first compression information includes the first context identifier CID, and the compression unit 2530 is used to compress The information compresses the Ethernet header of the first Ethernet frame.
  • the apparatus 1700 may further include a first relationship generating unit, configured to generate a first corresponding relationship when the corresponding relationship stored by the compression end does not include the value of the first field to be compressed of the first Ethernet frame, and the compression end
  • the stored correspondence relationship includes at least one correspondence relationship between compression information and the value of the field to be compressed.
  • it further includes a sending unit, configured to send the first correspondence to the decompression end.
  • the sending unit is specifically configured to send a non-compressed data packet to the decompression end, and the non-compressed data packet includes the first correspondence.
  • the sending unit is specifically configured to send the first correspondence relationship to the decompression end through the first packet data convergence protocol data protocol data unit PDCP data PDU; wherein, the first PDCP data PDU includes: the first Ethernet frame header compression EHC header , The first EHC header includes the first indication field, the first CID, and the Ethernet header of the second Ethernet frame; the value of the field to be compressed in the Ethernet header of the second Ethernet frame is equal to the value of the first field to be compressed ; The first indication field is used to indicate whether the first EHC header includes a complete Ethernet frame header.
  • the first EHC header further includes the first profile identification profile ID.
  • the first indication field is also used to indicate that the first EHC header includes the first profile ID.
  • the first PDCP data PDU further includes: a PDCP header, a service data adaptation layer SDAP header, an Ethernet data payload, and an integrity message authentication code MAC-I.
  • the sending unit is specifically configured to send the first corresponding relationship to the decompression end through the PDCP control PDU of the packet data convergence protocol control protocol data unit; wherein, the PDCP control PDU includes the first indication information, the first CID, and the first to-be-compressed The value of the field; the first indication information is used to indicate that the PDCP control PDU is used to transmit the first correspondence.
  • the PDCP control PDU also includes: profile ID.
  • the sending unit is specifically configured to send the first PDCP data PDU to the decompression end; wherein, the first PDCP data PDU includes: a first EHC header, and the first EHC header includes a first indication field and a second Ethernet frame The value of the field to be compressed in the Ethernet frame header of the two Ethernet frame is equal to the value of the first field to be compressed; the first indication field is used to indicate whether the first CID is carried in the first EHC header.
  • the Ethernet frame header of the second Ethernet frame is a compressed Ethernet frame header, or when the first EHC header does not carry the first CID, the Ethernet frame header of the second Ethernet frame
  • the frame header is a complete Ethernet frame header.
  • the first PDCP data PDU further includes: a PDCP header, a service data adaptation layer SDAP header, an Ethernet data payload, and an integrity message authentication code MAC-I.
  • the sending unit is specifically configured to send the first correspondence to the decompression end multiple times.
  • the receiving unit is further configured to receive feedback information from the decompression end, and the feedback information is used to indicate the reception status of the first correspondence.
  • the feedback information includes the first CID.
  • the feedback information further includes at least one of the following: a first profile ID, a second indication field, and a third indication field.
  • the second indication field is used to indicate that the first correspondence is a new correspondence or modification at the decompression end.
  • the third indication field is used to indicate whether the feedback information is positive feedback or negative feedback.
  • the compression terminal also stores an indicator variable of the corresponding relationship, and the indicator variable is used to indicate whether the compressed information of the corresponding relationship is used for compression.
  • the sending unit is further configured to: when the correspondence stored by the compression end includes the first correspondence corresponding to the first field to be compressed, and the indicator variable of the first correspondence indicates that the compressed information of the first correspondence is not used for compression, The compression end sends the first correspondence to the decompression end.
  • variable setting unit which is used to set the indicator variable to a first value by the compression side when the compression side confirms that the first correspondence is correctly received by the decompression side, and the first value is used to indicate that the compressed information is used for compression.
  • the first compressed information further includes the first profile ID.
  • the sending unit is further configured to send second indication information to the decompression end, where the second indication information is used to indicate that the first correspondence is a new correspondence or a modified correspondence on the compression end.
  • the sending unit is further configured to send the compressed first Ethernet frame to the decompression end, where the compressed first Ethernet frame includes the first CID and does not include the profile ID.
  • the sending unit is further configured to send the compressed first Ethernet frame to the decompression end includes: the compression end sends the compressed first Ethernet frame to the decompression end through the second PDCP data PDU.
  • the second PDCP data PDU includes a second EHC header, and the second EHC header further includes verification information.
  • the verification information is generated according to one or more pieces of information in the first correspondence.
  • it further includes a setting unit, configured to delete the first correspondence or the compression end to set the first correspondence to be unavailable when the compression end receives an error report returned by the decompression end according to the verification information .
  • the compression end is a terminal, the decompression end is a network device, and the sending unit is also used to send capability information to the decompression end;
  • the capability information includes at least one of the following: the compression end supports EHC capability, and the compression end supports EHC The number of data radio bearer DRBs, the profile information of the profile supported by the compression end, the maximum number of correspondences supported by each DRB that supports EHC, MAX_CID, the compression end supports the ability to dynamically configure the profile parameters, and the compression end supports EHC DRB The sum of the number of correspondences maintained.
  • the receiving unit is further configured to receive configuration information, and the configuration information is used to indicate whether the EHC header carries the profile ID; or, the configuration information includes the profile ID.
  • the compression terminal is a network device or terminal, and the receiving unit is also used to receive capability information.
  • the capability information includes at least one of the following: the capability information includes at least one of the following: the capability of the compression terminal to support EHC, and the compression terminal supports The number of EHC data radio bearer DRBs, the profile information of the profile supported by the compression end, the maximum number of correspondences supported by each DRB that supports EHC, MAX_CID, the compression end supports the ability to dynamically configure profile parameters, and the compression end supports EHC The sum of the number of correspondences maintained by the DRB.
  • the sending unit is further used to send configuration information to the decompression end, and the configuration information is also used to indicate whether the EHC header carries the profile ID; or, the configuration information includes the profile ID.
  • FIG. 26 is a schematic diagram of an Ethernet frame header decompression apparatus provided by an embodiment of the application.
  • the device is used for the decompression end.
  • the device 2600 includes a receiving unit 2610, a determining unit 2620, and a decompression unit 2630.
  • the receiving unit 2610 is configured to receive the first Ethernet frame and the first context identifier CID; the determining unit 2620 is configured to determine the first correspondence relationship including the first CID according to the first CID, and the first correspondence relationship includes the first compression information and the first Correspondence between the values of the fields to be decompressed, the first compression information includes the first CID; the decompression unit 2630 is configured to decompress the first Ethernet frame according to the first compression information in the first correspondence and the values of the first fields to be decompressed Ether frame header.
  • the receiving unit is further configured to receive the first correspondence from the compression end.
  • the receiving unit is specifically configured to receive a non-compressed data packet, and the non-compressed data packet includes the first correspondence.
  • the receiving unit is further configured to receive the first corresponding relationship from the compression end through PDCP data PDU; wherein, the first PDCP data PDU includes: a first Ethernet frame header compressed EHC header, and the first EHC header includes a first indication field, The first CID and the Ethernet header of the second Ethernet frame, the value of the field to be compressed in the Ethernet header of the second Ethernet frame is equal to the value of the first field to be compressed; the first indication field is used to indicate the first EHC header Whether to include a complete Ethernet frame header.
  • the first EHC header further includes the first profile identification profile ID.
  • the first indication field is also used to indicate that the first EHC header includes the first profile ID.
  • the first PDCP data PDU further includes: a PDCP header, a service data adaptation layer SDAP header, an Ethernet data payload, and an integrity message authentication code MAC-I.
  • the receiving unit is further configured to receive the first corresponding relationship sent by the compression end through PDCP control PDU; wherein, the PDCP control PDU includes the first indication information, the CID and the value of the first field to be compressed; the first indication information is used for Indicates that the PDCP control PDU is used to transmit the first correspondence.
  • the PDCP control PDU further includes: the first profile ID.
  • the receiving unit is further configured to receive the first PDCP data PDU from the compression end; wherein, the first PDCP data PDU includes: a first EHC header, and the first EHC header includes a first indication field and the Ethernet of the second Ethernet frame.
  • Frame header the value of the field to be compressed in the Ethernet frame header of the second Ethernet frame is equal to the value of the first field to be compressed; the first indication field is used to indicate whether the first CID is carried in the first EHC header.
  • the Ethernet frame header of the second Ethernet frame is a compressed Ethernet frame header, or when the first EHC header does not carry the first CID, the Ethernet frame header of the second Ethernet frame
  • the frame header is a complete Ethernet frame header.
  • the first PDCP data PDU further includes: a PDCP header, a service data adaptation layer SDAP header, an Ethernet data payload, and an integrity message authentication code MAC-I.
  • the decompression terminal stores at least one correspondence between compressed information and the value of the field to be decompressed, and further includes a first correspondence setting unit, configured to decompress when the correspondence stored by the decompression terminal does not include the first compressed information
  • the first corresponding relationship is stored at the end; or, when the corresponding relationship stored by the decompression end includes the first compressed information, and the value of the first compressed information corresponding to the field to be decompressed is different from the value of the first field to be decompressed, the decompression end will first The value of the compressed information corresponding to the field to be decompressed is modified to the value of the first field to be decompressed.
  • it further includes a sending unit, configured to send feedback information to the compression end, where the feedback information is used to indicate the reception status of the first correspondence.
  • the feedback information includes the first CID.
  • the feedback information further includes at least one of the following: profile ID, a first indication field, and a second indication field.
  • the first indication field is used to indicate that the first correspondence is a new correspondence or a modified correspondence at the decompression end.
  • the second indication field is used to indicate whether the feedback information is positive feedback or negative feedback.
  • the first Ethernet frame further includes: first check information.
  • the first verification information is generated according to one or more pieces of information in the first correspondence.
  • it further includes a verification unit, configured to generate second verification information according to one or more pieces of information in the first correspondence; when the first verification information is the same as the second verification information, the decompression terminal Decompress the Ethernet frame header of the first Ethernet frame; or, when the first verification information is different from the second verification information, the decompression end deletes the first correspondence; and/or, the decompression end sends an error report to the compression end.
  • a verification unit configured to generate second verification information according to one or more pieces of information in the first correspondence; when the first verification information is the same as the second verification information, the decompression terminal Decompress the Ethernet frame header of the first Ethernet frame; or, when the first verification information is different from the second verification information, the decompression end deletes the first correspondence; and/or, the decompression end sends an error report to the compression end.
  • each unit in the device can be implemented in the form of software called by processing elements; they can also be implemented in the form of hardware; part of the units can be implemented in the form of software called by the processing elements, and some of the units can be implemented in the form of hardware.
  • each unit can be a separately established processing element, or it can be integrated in a certain chip of the device for implementation.
  • it can also be stored in the memory in the form of a program, which is called and executed by a certain processing element of the device.
  • all or part of these units can be integrated together or implemented independently.
  • the processing element here can also be called a processor, which can be an integrated circuit with signal processing capabilities.
  • each step of the above method or each of the above units may be implemented by an integrated logic circuit of hardware in a processor element or implemented in a form of being called by software through a processing element.
  • the unit in any of the above devices may be one or more integrated circuits configured to implement the above methods, for example: one or more application specific integrated circuits (ASIC), or, one or Multiple microprocessors (digital singnal processors, DSPs), or, one or more field programmable gate arrays (Field Programmable Gate Arrays, FPGAs), or a combination of at least two of these integrated circuits.
  • ASIC application specific integrated circuits
  • DSPs digital singnal processors
  • FPGAs Field Programmable Gate Arrays
  • the unit in the device can be implemented in the form of a processing element scheduler
  • the processing element can be a general-purpose processor, such as a central processing unit (CPU) or other processors that can call programs.
  • CPU central processing unit
  • these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).
  • the above receiving unit is an interface circuit of the device for receiving signals from other devices.
  • the receiving unit is an interface circuit used by the chip to receive signals from other chips or devices.
  • the above unit for sending is an interface circuit of the device for sending signals to other devices.
  • the sending unit is an interface circuit used by the chip to send signals to other chips or devices.
  • FIG. 27 is a schematic structural diagram of a network device provided by an embodiment of this application.
  • the network device is used to implement the operation of the network device in the above embodiment.
  • the network equipment includes: an antenna 2710, a radio frequency device 2720, and a baseband device 2730.
  • the antenna 2710 is connected to the radio frequency device 2720.
  • the radio frequency device 2720 receives the information sent by the terminal device through the antenna 2710, and sends the information sent by the terminal device to the baseband device 2730 for processing.
  • the baseband device 2730 processes the information of the terminal device and sends it to the radio frequency device 2720.
  • the radio frequency device 2720 processes the information of the terminal device and sends it to the terminal device via the antenna 2710.
  • the baseband device 2730 may include one or more processing elements 2731, for example, including a main control CPU and other integrated circuits.
  • the baseband device 2730 may also include a storage element 2732 and an interface 2733.
  • the storage element 2732 is used to store programs and data; the interface 2733 is used to exchange information with the radio frequency device 2720.
  • the interface is, for example, a common public radio interface. , CPRI).
  • the above apparatus for network equipment may be located in the baseband apparatus 2730.
  • the above apparatus for network equipment may be a chip on the baseband apparatus 2730.
  • the chip includes at least one processing element and an interface circuit, wherein the processing element is used to execute the above network For each step of any method executed by the device, the interface circuit is used to communicate with other devices.
  • the unit for the network device to implement each step in the above method can be implemented in the form of a processing element scheduler.
  • the device for the network device includes a processing element and a storage element, and the processing element calls the program stored by the storage element to Perform the method performed by the network device in the above method embodiment.
  • the storage element may be a storage element with the processing element on the same chip, that is, an on-chip storage element, or a storage element on a different chip from the processing element, that is, an off-chip storage element.
  • the unit of the network device that implements each step in the above method may be configured as one or more processing elements, and these processing elements are provided on the baseband device.
  • the processing elements here may be integrated circuits, such as one Or multiple ASICs, or, one or more DSPs, or, one or more FPGAs, or a combination of these types of integrated circuits. These integrated circuits can be integrated together to form a chip.
  • the units for the network equipment to implement each step in the above method can be integrated together and implemented in the form of a system-on-a-chip (SOC).
  • the baseband device includes the SOC chip for implementing the above method.
  • At least one processing element and storage element can be integrated in the chip, and the processing element can call the stored program of the storage element to implement the method executed by the above network device; or, at least one integrated circuit can be integrated in the chip to implement the above network The method executed by the device; or, it can be combined with the above implementations.
  • the functions of some units are implemented in the form of calling programs by processing elements, and the functions of some units are implemented in the form of integrated circuits.
  • the above apparatus for a network device may include at least one processing element and an interface circuit, wherein at least one processing element is used to execute any method executed by the network device provided in the above method embodiments.
  • the processing element can execute part or all of the steps executed by the network device in the first way: calling the program stored in the storage element; or in the second way: combining instructions through the integrated logic circuit of the hardware in the processor element Part or all of the steps performed by the network device are executed in the method; of course, part or all of the steps executed by the network device can be executed in combination with the first method and the second method.
  • the processing element here is the same as the above description, and may be a general-purpose processor, such as a CPU, or one or more integrated circuits configured to implement the above method, such as: one or more ASICs, or, one or more micro-processing DSP, or, one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms.
  • the storage element can be a memory or a collective term for multiple storage elements.
  • FIG. 28 is a schematic structural diagram of a terminal device according to an embodiment of the application.
  • the terminal device is used to implement the operation of the terminal in the above embodiment.
  • the terminal device includes: an antenna 2810, a radio frequency part 2828, and a signal processing part 2830.
  • the antenna 2810 is connected to the radio frequency part 2828.
  • the radio frequency part 2828 receives the information sent by the access network device through the antenna 2810, and sends the information sent by the access network device to the signal processing part 2830 for processing.
  • the signal processing part 2830 processes the information of the terminal device and sends it to the radio frequency part 2828
  • the radio frequency part 2828 processes the information of the terminal device and sends it to the access network equipment via the antenna 2810.
  • the signal processing part 2830 is used to realize the processing of each communication protocol layer of the data.
  • the signal processing part 2830 may be a subsystem of the terminal device, and the terminal device may also include other subsystems, such as a central processing subsystem, which is used to process the operating system and application layer of the terminal device; The system is used to realize the connection with other equipment.
  • the signal processing part 2830 may be a separately provided chip.
  • the above devices may be located in the signal processing part 2830.
  • the signal processing part 2830 may include one or more processing elements 2831, for example, a main control CPU and other integrated circuits.
  • the signal processing part 2830 may also include a storage element 2832 and an interface circuit 2833.
  • the storage element 2832 is used to store data and programs.
  • the program used to execute the method performed by the terminal device in the above method may or may not be stored in the storage element 2832, for example, stored in a memory other than the signal processing part 2830 During use, the signal processing part 2830 loads the program into the cache for use.
  • the interface circuit 2833 is used to communicate with the device.
  • the above device may be located in the signal processing part 2830, and the signal processing part 2830 may be realized by a chip.
  • the chip includes at least one processing element and an interface circuit, wherein the processing element is used to execute each step of any method executed by the above terminal device.
  • the circuit is used to communicate with other devices.
  • the unit that implements each step in the above method can be implemented in the form of a processing element scheduler.
  • the device includes a processing element and a storage element, and the processing element calls the program stored by the storage element to execute the above method embodiments.
  • the storage element may be a storage element whose processing element is on the same chip, that is, an on-chip storage element.
  • the program for executing the method executed by the terminal device in the above method may be a storage element on a different chip from the processing element, that is, an off-chip storage element.
  • the processing element calls or loads a program from the off-chip storage element on the on-chip storage element to call and execute the method executed by the terminal device in the above method embodiment.
  • the unit of the terminal device that implements each step in the above method may be configured as one or more processing elements, and these processing elements are provided on the signal processing part 2830, where the processing elements may be integrated circuits, for example : One or more ASICs, or, one or more DSPs, or, one or more FPGAs, or a combination of these types of integrated circuits. These integrated circuits can be integrated together to form a chip.
  • the units that implement each step in the above method can be integrated together and implemented in the form of a system-on-a-chip (SOC).
  • SOC chip is used to implement the above method.
  • At least one processing element and storage element can be integrated in the chip, and the processing element can call the stored program of the storage element to implement the method executed by the above terminal device; or, at least one integrated circuit can be integrated in the chip to implement the above terminal
  • the method executed by the device or, it can be combined with the above implementations.
  • the functions of some units are implemented in the form of calling programs by processing elements, and the functions of some units are implemented in the form of integrated circuits.
  • the above device may include at least one processing element and an interface circuit, wherein at least one processing element is used to execute any method executed by the terminal device provided in the above method embodiment.
  • the processing element can execute part or all of the steps executed by the terminal device in the first way: calling the program stored in the storage element; or in the second way: combining instructions through the integrated logic circuit of the hardware in the processor element Part or all of the steps executed by the terminal device are executed in a manner; of course, part or all of the steps executed by the terminal device may also be executed in combination with the first manner and the second manner.
  • the processing element here is the same as the above description, and may be a general-purpose processor, such as a CPU, or one or more integrated circuits configured to implement the above method, such as: one or more ASICs, or, one or more micro-processing DSP, or, one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms.
  • the storage element can be a memory or a collective term for multiple storage elements.
  • FIG. 29 is a schematic structural diagram of a compression end device provided by an embodiment of the application, which is used to implement the operation of the compression end in the above embodiment.
  • the compression terminal device includes: a processor 2910, a memory 2920, and an interface 2930, and the processor 2910, a memory 2920, and the interface 2930 are connected in signal.
  • the method executed by the compression terminal device in the above embodiment can be implemented by the processor 2910 calling a program stored in the memory 2920. That is, the apparatus for the compression terminal device includes a memory and a processor, and the memory is used to store a program, which is called by the processor to execute the method executed by the compression terminal device in the above method embodiment.
  • the processor here may be an integrated circuit with signal processing capability, such as a CPU.
  • the apparatus for the compression terminal device may be realized by one or more integrated circuits configured to implement the above method. For example: one or more ASICs, or, one or more microprocessors DSP, or, one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms. Or, the above implementations can be combined.
  • FIG. 30 is a schematic structural diagram of a decompression terminal device provided in an embodiment of this application, which is used to implement the operation of the decompression terminal in the above embodiments.
  • the decompression terminal device includes a processor 3010, a memory 3020, and an interface 3030, and the processor 3010, the memory 3020, and the interface 3030 are connected in signal.
  • the method executed by the decompression terminal device in the above embodiment may be implemented by the processor 3010 calling a program stored in the memory 3020. That is, the device for the decompression terminal device includes a memory and a processor, and the memory is used to store a program, and the program is called by the processor to execute the method executed by the decompression terminal device in the above method embodiment.
  • the processor here may be an integrated circuit with signal processing capability, such as a CPU.
  • the apparatus for the decompression terminal device can be realized by one or more integrated circuits configured to implement the above method. For example: one or more ASICs, or, one or more microprocessors DSP, or, one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms. Or, the above implementations can be combined.
  • a person of ordinary skill in the art can understand that all or part of the steps in the above method embodiments can be implemented by a program instructing relevant hardware.
  • the foregoing program can be stored in a computer readable storage medium. When the program is executed, it is executed. Including the steps of the foregoing method embodiment; and the foregoing storage medium includes: ROM, RAM, magnetic disk, or optical disk and other media that can store program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例提供一种以太帧头的压缩、解压方法和装置，压缩端可以在接收到包括第一待压缩字段的以太帧后，通过包括第一压缩信息和该第一待压缩字段的取值的第一对应关系，根据第一压缩信息对该以太帧的以太帧头进行压缩，适应的，解压端可以在接收到压缩后的以太帧的情况下，根据第一对应关系实现对压缩后的以太帧的以太帧头的解压，本申请实施例中，因为对以太帧的以太帧头进行了压缩，所以可以节省通信资源。

Description

以太帧头的压缩、解压方法和装置 技术领域
本申请涉及通信技术领域，尤其涉及以太帧头的压缩、解压方法和装置。
背景技术
传统的工业控制领域通过有线连接来实现自动化控制，但有线连接的部署方式使得线缆部署和维护成本比较高，且由于受到线缆的限制，被控制端的移动性差。为此，采用无线传输方式代替有线连接方式的工业控制获得了越来越广泛的关注。多数工业控制网络在部署时采用以太网技术，当无线网络替换有线网络时，以太帧通过无线网络在控制端和被控制端之间传输，因此以太帧需要在无线网络中进行传输。以太帧在无线网络传输中需要较多的资源开销，而无线资源是有限的，因此，希望减少以太帧在无线网络中传输的开销。
发明内容
本申请提供以太帧头的压缩、解压方法和装置，以降低以太帧头对以太网通信资源的占用。
第一方面，提供一种以太帧头的压缩方法，包括：压缩端接收第一以太帧，第一以太帧的以太帧头包括第一待压缩字段；压缩端根据第一对应关系和第一待压缩字段确定第一以太帧的以太帧头的第一压缩信息，第一对应关系包括第一压缩信息和第一待压缩字段的取值的对应关系，第一压缩信息包括第一上下文标识CID；压缩端根据第一压缩信息压缩第一以太帧的以太帧头。
此外，提供一种压缩装置，包括用于执行以上第一方面各个步骤的单元或手段(means)。
此外，提供一种压缩装置，包括处理器和接口电路，处理器用于通过接口电路与其它装置通信，并执行以上第一方面提供的方法。该处理器包括一个或多个。
此外，提供一种压缩装置，包括处理器，用于调用存储器中存储的程序，以执行以上第一方面提供的方法。该存储器可以位于该装置之内，也可以位于该装置之外。且该处理器包括一个或多个。
此外，提供一种计算机程序，该程序在被处理器调用时，以上第一方面提供的方法被执行。
此外，提供一种计算机可读存储介质，包括以上程序。
压缩端可以在接收到包括第一待压缩字段的第一以太帧后，通过包括第一压缩信息和该第一待压缩字段的取值的第一对应关系，根据第一压缩信息对该第一以太帧的以太帧头进行压缩，因为对第一以太帧的以太帧头进行了压缩，所以可以节省通信资源。
可选的，在以上第一方面或第一方面的各种实现中，当压缩端存储的对应关系不 包括第一以太帧的第一待压缩字段的取值时，生成第一对应关系，压缩端存储的对应关系包括至少一个压缩信息和待压缩字段的取值的对应关系。
可选的，在以上第一方面或第一方面的各种实现中，压缩端向解压端发送第一对应关系。
可选的，在以上第一方面或第一方面的各种实现中，压缩端向解压端发送第一对应关系包括：压缩端向解压端发送非压缩数据包，非压缩数据包包括第一对应关系。
可选的，在以上第一方面或第一方面的各种实现中，压缩端向解压端发送第一对应关系，包括：压缩端通过第一分组数据汇聚协议数据协议数据单元PDCP data PDU向解压端发送第一对应关系；其中，第一PDCP data PDU包括：第一以太帧头压缩EHC头，第一EHC头包括第一指示字段、第一CID和第二以太帧的以太帧头；第二以太帧的以太帧头的待压缩字段的取值等于所述第一待压缩字段的取值；第一指示字段用于指示第一EHC头中是否包括有完整的以太帧头。
可选的，在以上第一方面或第一方面的各种实现中，第一EHC头还包括第一配置文件标识profile ID。
可选的，在以上第一方面或第一方面的各种实现中，第一指示字段还用于指示第一EHC头包括第一profile ID。
可选的，在以上第一方面或第一方面的各种实现中，第一PDCP data PDU还包括：PDCP头、服务数据适配层SDAP头、以太数据载荷和完整性消息认证码MAC-I。
可选的，在以上第一方面或第一方面的各种实现中，压缩端向解压端发送第一对应关系，包括：
压缩端通过分组数据汇聚协议控制协议数据单元PDCP control PDU向解压端发送第一对应关系；其中，PDCP control PDU包括第一指示信息、第一CID和所述第一待压缩字段的取值；第一指示信息用于指示PDCP control PDU用于传输第一对应关系。
可选的，在以上第一方面或第一方面的各种实现中，PDCP control PDU还包括第一profile ID。
可选的，在以上第一方面或第一方面的各种实现中，还包括：压缩端向解压端发送第一PDCP data PDU；其中，第一PDCP data PDU包括：第一EHC头，第一EHC头包括第一指示字段、和第二以太帧的以太帧头，二以太帧的以太帧头的待压缩字段的取值等于所述第一待压缩字段的取值；第一指示字段用于指示第一EHC头中是否携带第一CID。
可选的，在以上第一方面或第一方面的各种实现中，当第一EHC头携带第一CID时，第二以太帧的以太帧头为压缩的以太帧头，或者，当第一EHC头未携带第一CID时，第二以太帧的以太帧头为完整的以太帧头。
可选的，在以上第一方面或第一方面的各种实现中，第一PDCP data PDU还包括：PDCP头、服务数据适配层SDAP头、以太数据载荷和完整性消息认证码MAC-I。
可选的，在以上第一方面或第一方面的各种实现中，压缩端向解压端发送第一对应关系包括：压缩端向解压端多次发送第一对应关系。
可选的，在以上第一方面或第一方面的各种实现中，还包括：压缩端从解压端接收反馈信息，反馈信息用于指示第一对应关系的接收状态。
可选的，在以上第一方面或第一方面的各种实现中，反馈信息包括第一CID。
可选的，在以上第一方面或第一方面的各种实现中，反馈信息还包括以下至少一项：第一profile ID、第二指示字段、第三指示字段，第二指示字段用于指示第一对应关系在解压端为新增的对应关系或修改的对应关系，第三指示字段用于指示反馈信息为肯定反馈或否定反馈。
可选的，在以上第一方面或第一方面的各种实现中，压缩端还存储有对应关系的指示变量，指示变量用于指示对应关系的压缩信息是否用于压缩。
可选的，在以上第一方面或第一方面的各种实现中，还包括：当压缩端存储的对应关系包括第一待压缩字段对应的第一对应关系，且第一对应关系的指示变量指示第一对应关系的压缩信息不用于压缩时，压缩端向解压缩端发送第一对应关系。
可选的，在以上第一方面或第一方面的各种实现中，还包括：在压缩端确认第一对应关系被解压端正确接收时，压缩端将指示变量设置为第一值，第一值用于指示压缩信息用于压缩。
可选的，在以上第一方面或第一方面的各种实现中，第一压缩信息还包括第一profile ID。
可选的，在以上第一方面或第一方面的各种实现中，还包括：压缩端向解压端发送第二指示信息，第二指示信息用于指示第一对应关系在压缩端为新增的对应关系或修改的对应关系。
可选的，在以上第一方面或第一方面的各种实现中，还包括：压缩端向解压端发送压缩后的第一以太帧，压缩后的第一以太帧包括第一CID，且不包括配置文件标识profile ID。
此时，因压缩后的以太帧不包括profile ID，可以降低对空间的占用。
可选的，在以上第一方面或第一方面的各种实现中，压缩端向解压端发送压缩后的第一以太帧包括：压缩端通过第二PDCP data PDU向解压端发送压缩后的第一以太帧。
可选的，在以上第一方面或第一方面的各种实现中，第二PDCP data PDU包括第二EHC头，第二EHC头还包括：校验信息。
可选的，在以上第一方面或第一方面的各种实现中，校验信息为根据第一对应关系中的一个或多个信息生成的。
可选的，在以上第一方面或第一方面的各种实现中，在压缩端接收到解压端根据校验信息返回的错误报告的情况下，压缩端删除第一对应关系，或压缩端将第一对应关系设置为不可用。
可选的，在以上第一方面或第一方面的各种实现中，压缩端为终端，解压缩端为网络设备，方法还包括：
压缩端向解压端发送能力信息；能力信息包括下述至少一项：压缩端支持EHC的能力，压缩端中支持EHC的数据无线承载DRB的个数，压缩端支持的配置文件profile信息，每个支持EHC的DRB所支持的对应关系数量的最大值MAX_CID，压缩端支持动态配置profile参数的能力，压缩端支持EHC的DRB所维护的对应关系数量的总和。
可选的，在以上第一方面或第一方面的各种实现中，压缩端为终端，该方法还包括：终端接收配置信息，配置信息用于指示EHC头是否携带profile ID；或者，配置信息包括profile ID。
可选的，在以上第一方面或第一方面的各种实现中，还包括：压缩端接收能力信息，能力信息包括下述至少一项：能力信息包括下述至少一项：压缩端支持EHC的能力，压缩端中支持EHC的数据无线承载DRB的个数，压缩端支持的配置文件profile信息，每个支持EHC的DRB所支持的对应关系数量的最大值MAX_CID，压缩端支持动态配置profile参数的能力，压缩端支持EHC的DRB所维护的对应关系数量的总和。
可选的，在以上第一方面或第一方面的各种实现中，解压端为终端，压缩端为网络设备，该方法还包括：网络设备向解压端发送配置信息，配置信息用于指示EHC头是否携带profile ID；或者，配置信息包括profile ID。
第二方面，提供一种以太帧头的解压方法，包括：解压端接收第一以太帧，所述第一以太帧包括第一上下文标识CID；解压端根据第一CID确定包括第一CID的第一对应关系，第一对应关系包括第一压缩信息和第一待解压字段的取值的对应关系，第一压缩信息包括第一CID；解压端根据第一对应关系中的第一压缩信息和第一待解压字段的取值解压第一以太帧的以太帧头。
此外，提供一种解压装置，包括用于执行以上第二方面各个步骤的单元或手段(means)。
此外，提供一种解压装置，包括处理器和接口电路，处理器用于通过接口电路与其它装置通信，并执行以上第二方面提供的方法。该处理器包括一个或多个。
此外，提供一种解压装置，包括处理器，用于调用存储器中存储的程序，以执行以上第二方面提供的方法。该存储器可以位于该装置之内，也可以位于该装置之外。且该处理器包括一个或多个。
此外，提供一种计算机程序，该程序在被处理器调用时，以上第二方面提供的方法被执行。
此外，提供一种计算机可读存储介质，包括以上程序。
解压端可以在接收到压缩后的第一以太帧的情况下，根据第一以太帧中的第一CID确定第一对应关系，根据第一对应关系实现对压缩后的以太帧的以太帧头的解压，本申请实施例中，因为对以太帧的以太帧头进行了压缩，所以可以节省通信资源。
可选的，在以上第二方面或第二方面的各种实现中，还包括：解压端从压缩端接收第一对应关系。
可选的，在以上第二方面或第二方面的各种实现中，解压端从压缩端接收第一对应关系，包括：解压端接收非压缩数据包，非压缩数据包包括第一对应关系。
可选的，在以上第二方面或第二方面的各种实现中，解压端从压缩端接收第一对应关系，包括：解压端通过PDCP data PDU从压缩端接收第一对应关系；其中，第一PDCP data PDU包括：第一以太帧头压缩EHC头，第一EHC头包括第一指示字段、第一CID和第二以太帧的以太帧头，第二以太帧的以太帧头的待压缩字段的取值等于第一待压缩字段的取值；第一指示字段用于指示第一EHC头中是否包括有完整的以太 帧头。
可选的，在以上第二方面或第二方面的各种实现中，第一EHC头还包括第一配置文件标识profile ID。
可选的，在以上第二方面或第二方面的各种实现中，第一指示字段还用于指示第一EHC头包括第一profile ID。
可选的，在以上第二方面或第二方面的各种实现中，第一PDCP data PDU还包括：PDCP头、服务数据适配层SDAP头、以太数据载荷和完整性消息认证码MAC-I。
可选的，解压端从压缩端接收第一对应关系，包括：解压端从压缩端通过PDCP control PDU接收第一对应关系；其中，PDCP control PDU包括第一指示信息、第一CID和第一待压缩字段的取值；第一指示信息用于指示PDCP control PDU用于传输第一对应关系。
可选的，在以上第二方面或第二方面的各种实现中，PDCP control PDU还包括：第一profile ID。
可选的，在以上第二方面或第二方面的各种实现中，还包括：解压端从压缩端接收第一PDCP data PDU；其中，第一PDCP data PDU包括：第一EHC头，第一EHC头包括第一指示字段、和第二以太帧的以太帧头，第二以太帧的以太帧头的待压缩字段的取值等于第一待压缩字段的取值；第一指示字段用于指示第一EHC头中是否携带第一CID。
可选的，在以上第二方面或第二方面的各种实现中，当第一EHC头携带第一CID时，第二以太帧的以太帧头为压缩的以太帧头，或者，当第一EHC头未携带第一CID时，第二以太帧的以太帧头为完整的以太帧头。
可选的，在以上第二方面或第二方面的各种实现中，第一PDCP data PDU还包括：PDCP头、服务数据适配层SDAP头、以太数据载荷和完整性消息认证码MAC-I。
可选的，在以上第二方面或第二方面的各种实现中，解压端存储有至少一个压缩信息和待解压字段的取值的对应关系，方法还包括：当解压端存储的对应关系不包括第一压缩信息时，解压端存储第一对应关系；或者，当解压端存储的对应关系包括第一压缩信息时，且第一压缩信息对应待解压字段的取值与第一待解压字段的取值不同，解压端将第一压缩信息对应待解压字段的取值修改为第一待解压字段的取值。
可选的，在以上第二方面或第二方面的各种实现中，还包括：解压端向压缩端发送反馈信息，反馈信息用于指示第一对应关系的接收状态。
可选的，在以上第二方面或第二方面的各种实现中，反馈信息包括第一CID。
可选的，在以上第二方面或第二方面的各种实现中，反馈信息还包括以下至少一项：profile ID、第一指示字段、第二指示字段，第一指示字段用于指示第一对应关系在解压端为新增的对应关系或修改的对应关系，第二指示字段用于指示反馈信息为肯定反馈或否定反馈。
可选的，在以上第二方面或第二方面的各种实现中，第一以太帧还包括：第一校验信息。
可选的，在以上第二方面或第二方面的各种实现中，第一校验信息为根据第一对应关系中的一个或多个信息生成的。
可选的，还包括：压缩端根据第一对应关系中的一个或多个信息生成第二校验信息；在第一校验信息与第二校验信息相同的情况下，解压端解压第一以太帧的以太帧头；或，在第一校验信息与第二校验信息不同的情况下，解压端删除第一对应关系；和/或，解压端向压缩端发送错误报告。
综上，本申请实施例提供了以太帧头的压缩、解压方法和装置，压缩端可以在接收到包括第一待压缩字段的第一以太帧后，通过包括第一压缩信息和该第一待压缩字段的取值的第一对应关系，根据第一压缩信息对该第一以太帧的以太帧头进行压缩，适应的，解压端可以在接收到压缩后的第一以太帧的情况下，根据第一对应关系实现对压缩后的第一以太帧的以太帧头的解压，本申请实施例中，因为对以太帧的以太帧头进行了压缩，所以可以节省通信资源。
附图说明
图1为本申请实施例提供的一种网络架构的示意图；
图2为本申请实施例提供的一种控制系统的示意图；
图3为本申请实施例提供的另一种控制系统的示意图；
图4为本申请实施例提供的又一种控制系统的示意图；
图5为本申请实施例提供的一种无线通信网络应用于控制网络的示意图；
图6为本申请实施例提供的另一种网络架构的示意图；
图7为本申请实施例提供的一种压缩、解压方法的流程示意图；
图8为本申请实施例提供的一种以太帧的格式示意图；
图9为本申请实施例提供的一种配置了EHC头的PDCP data PDU的格式；
图10为本申请实施例提供的第一种EHC头的格式的示意图；
图11为本申请实施例提供的第二种EHC头的格式的示意图；
图12为本申请实施例提供的一种在压缩端和解压端同步第一对应关系的方法的流程示意图；
图13为本申请实施例提供的一种反馈信息的格式的示意图；
图14为本申请实施例提供的第三种EHC头的格式的示意图；
图15为本申请实施例提供的第四种EHC头的格式的示意图；
图16为本申请实施例提供的第五种EHC头的格式的示意图；
图17为本申请实施例提供的第六种EHC头的格式的示意图；
图18为本申请实施例提供的第一种PDCP data PDU的格式的示意图；
图19为本申请实施例提供的第二种PDCP data PDU格式的示意图；
图20为本申请实施例提供的第三种PDCP data PDU的格式的示意图；
图21为本申请实施例提供的第四种PDCP data PDU格式的示意图；
图22为本申请实施例提供的第五种PDCP data PDU格式的示意图；
图23为本申请实施例提供的第七种EHC头的格式的示意图；
图24为本申请实施例提供的第八种EHC头的格式的示意图；
图25为本申请实施例提供的一种以太帧的压缩装置的示意图；
图26为本申请实施例提供的一种以太帧的解压装置的示意图；
图27为本申请实施例提供的一种网络设备的结构示意图；
图28为本申请实施例提供的一种终端设备的结构示意图；
图29为本申请实施例提供的一种以太帧的压缩装置的结构示意图；
图30为本申请实施例提供的一种以太帧的解压装置的结构示意图。
具体实施方式
本申请实施例提供以太帧头的压缩、解压方法和装置，图1为本申请实施例适用的一种网络架构的示意图，如图1所示，该网络架构中包括压缩端和解压端。
其中，压缩端可以是终端，或终端中的执行单元，示例的，终端中的执行单元可以是终端中的分组数据汇聚协议(packet data convergence protocol，PDCP)实体或无线链路控制(radio link control，RLC)实体或业务数据适配协议(service data adaptation protocol，SDAP)实体等，或实体中的以太帧头压缩(ethernet header compression，EHC)处理模块等。压缩端也可以是网络设备，或网络设备中的执行单元，示例的，网络设备中的执行单元可以是网络设备中的PDCP实体或RLC实体或SDAP实体等，或实体中的EHC处理模块等。
解压端可以是终端，或终端中的执行单元，示例的，终端中的执行单元可以是终端中的PDCP实体或RLC实体或SDAP实体等，或实体中的EHC处理模块等。解压端也可以是网络设备，或网络设备中的执行单元，示例的，网络设备中的执行单元可以是网络设备中的PDCP实体或RLC实体或SDAP实体等，或实体中的EHC处理模块等。
示例的，在对上行数据流的压缩、解压处理的应用场景中，压缩端可以是终端、终端中的PDCP实体或RLC实体或SDAP实体等、或实体中的EHC处理模块，解压端可以是网络设备、网络设备中的PDCP实体或RLC实体或SDAP实体等、或实体中的EHC处理模块。在对下行数据流的压缩、解压处理的应用场景中，压缩端可以是网络设备、网络设备中的PDCP实体或RLC实体或SDAP实体等、或实体中的EHC处理模块，解压端可以是终端、终端中的PDCP实体或RLC实体或SDAP实体等、或实体中的EHC处理模块。对于两个终端之间的侧行链路(sidelink)通信的应用场景中，压缩端和解压端都是进行sidelink通信的终端、终端中的PDCP实体或RLC实体或SDAP实体等、或实体中的EHC处理模块。
具体应用中，在工业控制场景下，如工业物联网(industrial internet of things，IIoT)场景中，大部分工业控制数据具有时延敏感(time sensitive，TS)的特性，工业控制节点需要在确定的时间点产生数据，并需要在特定的时间间隔下传输到对端节点上。为支持工业控制数据的传输，多数工业控制网络在部署时采用以太网技术。
传统的以太网控制自动化技术(ether control automation technology，etherCAT)系统包括主站(master)和至少一个从站(slave)，随着etherCAT的演进，可以利用有线的时间敏感型网络(time sensitive network，TSN)来实现master到slave之间的传输，如图2所示。由TSN来保证master和slave之间的传输时延波动在很小的范围内，从而实现master与slave之间使用专用线缆连接类似的效果。这样master和slave之间就可以实现物理上的灵活连接。主站又可以称为控制台(controller)，从站又可以称 为端设备(end device)。
随着无线技术的演进，期望利用无线网络实现master到slave之间的传输。如图3所示，利用无线网络实现master和Slave1之间的传输，并由无线网络来保证master和Slave1之间的传输时延波动在很小的范围内，从而实现master与Slave1之间使用专用线缆连接类似的效果，Slave1是slave组内的一个slave，通过无线网络与master通信，剩余的slave与该Slave 1建立有线连接，该slave组又可以称为slave链。如此，master和slave之间可以实现更加灵活的物理连接。或者，可以取消slave之间的有线连接，彻底实现用无线传输取代有线传输，进而实现完全灵活的部署。如图4所示，master通过无线网络跟各个slave进行通信。
一种实现如图5所示，终端510通过无线接口(例如空口)接入到无线网络，以通过无线网络跟其它设备通信，例如master。该无线网络包括无线接入网(radio access network，RAN)520和核心网(CN)530，其中RAN 520用于将终端510接入到无线网络，CN 530用于对终端进行管理并提供与其它设备通信的网关。终端可以为具有无线通信功能的设备，其可以通过适配器与以上控制系统中的slave连接，以通过无线网络接收master发送给slave的数据并发送给slave，或者将slave发送给master的数据通过无线网络发送给master。终端可以跟slave集成在一个物理实体上，例如图3中的Slave1或图4中的某个slave上可以集成具有无线通信的功能的元件(例如，芯片)，此时，slave集成有无线通信功能和工业控制终端的按指令执行操作的功能。
以上控制网络中，利用无线网络取代master和slave之间的接口，slave之间仍然采用有线接口。在另一种控制网络中，同样利用无线网络取代master和slave之间的接口，每个slave都可以通过无线网络与master通信，即图4所示的结构中，每个slave都通过适配器连接终端，或者，每个slave都可以集成无线通信功能的元件(例如，芯片)，以通过无线接口接入无线网络。在又一种控制网络中，可以结合以上两种连接方式，部分slave通过无线网络与master通信，其余slave与无线连接master的slave建立有线连接，例如，将slave分组，每个组内有一个slave，例如Slave 1，通过无线网络与master通信，剩余的slave与该Slave 1建立有线连接，该slave组又可以称为slave链，Slave 1是slave组中与无线网络连接的入口和出口，即与终端装置连接的slave。再如，将slave分组，每个组内有两个slave，例如Slave 1和Slave n，通过无线网络与master通信，剩余的slave与Slave 1和Slave n建立有线连接，该slave组又可以称为slave链，Slave 1和Slave n分别为slave组中与无线网络连接的入口和出口，即与终端装置连接的slave。
在本申请实施例中，终端又称之为终端装置或用户设备(user equipment，UE)，为具有无线通信功能的装置，且可以与slave连接，以下实施例中称为终端装置。该终端装置可以独立于slave，也可以与slave集成在一起；当集成在一起时，该终端装置可以指集成有slave物理实体和无线通信功能的装置，例如芯片或片上系统。终端装置可以包括工业控制(industrial control)中的无线终端，也可以为其它控制系统中有类似需求的终端，例如无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、或智慧家庭(smart home) 中的无线终端等。
网络设备可以是无线网络中的设备，例如将终端装置接入到无线网络的无线接入网(radio access network，RAN)节点或基站。目前，一些RAN节点或基站的举例为：gNB、传输接收点(transmission reception point，TRP)、演进型节点B(evolved Node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station,BTS)、家庭基站(例如，home evolved NodeB，或home Node B，HNB)、基带单元(base band unit，BBU)，中继站，或无线保真(wireless fidelity，Wifi)接入点(access point，AP)，云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器、车联网(vehicle to everything，V2X)中的路边装置(road site unit，RSU)、或融合接入回传(integrated access backhaul，IAB)系统中的接入点等。RAN设备也可以集成TSN网络节点的功能，例如集成控制台的功能，则网络设备也可以为该控制台。在一种网络结构中，网络设备可以包括集中单元(centralized unit，CU)节点、或分布单元(distributed unit，DU)节点、或包括CU节点和DU节点的RAN设备。
在一种网络架构中，RAN包括基带装置和射频装置，其中基带装置可以由一个节点实现，也可以由多个节点实现，射频装置可以从基带装置拉远独立实现，也可以集成基带装置中，或者部分拉远部分集成在基带装置中。例如，RAN可以包括基带装置和射频装置，其中射频装置可以相对于基带装置拉远布置，例如射频拉远单元(remote radio unit，RRU)相对于BBU拉远布置。
RAN和终端之间的通信遵循一定的协议层结构。例如控制面协议层结构可以包括无线资源控制(radio resource control，RRC)层、分组数据汇聚层协议(packet data convergence protocol，PDCP)层、无线链路控制(radio link control，RLC)层、媒体接入控制(media access control，MAC)层和物理层等协议层的功能。用户面协议层结构可以包括PDCP层、RLC层、MAC层和物理层等协议层的功能；在一种实现中，PDCP层之上还可以包括业务数据适配(service data adaptation protocol,SDAP)层。这些协议层的功能可以由一个节点实现，或者可以由多个节点实现；例如，在一种演进结构中，RAN可以包括集中单元(centralized unit，CU)和分布单元(distributed unit，DU)，多个DU可以由一个CU集中控制。CU和DU可以根据无线网络的协议层划分，例如PDCP层及以上协议层的功能设置在CU，PDCP以下的协议层，例如RLC层和MAC层等的功能设置在DU。这种协议层的划分仅仅是一种举例，还可以在其它协议层划分，例如在RLC层划分，将RLC层及以上协议层的功能设置在CU，RLC层以下协议层的功能设置在DU；或者，在某个协议层中划分，例如将RLC层的部分功能和RLC层以上的协议层的功能设置在CU，将RLC层的剩余功能和RLC层以下的协议层的功能设置在DU。此外，也可以按其它方式划分，例如按时延划分，将处理时间需要满足时延要求的功能设置在DU，不需要满足该时延要求的功能设置在CU。
可选的，射频装置可以拉远，不放在DU中，也可以集成在DU中，或者部分拉远部分集成在DU中，在此不作任何限制。
可选的，还可以将CU的控制面(CP)和用户面(UP)分离，分成不同实体来实现，分别为控制面CU实体(CU-CP实体)和用户面CU实体(CU-UP实体)。
在以上网络架构中，CU产生的信令可以通过DU发送给终端，或者终端产生的信令可以通过DU发送给CU。DU可以不对该信令进行解析而直接通过协议层封装而透传给终端或CU。以下实施例中如果涉及这种信令在DU和终端之间的传输，此时，DU对信令的发送或接收包括这种场景。例如，RRC或PDCP层的信令最终会处理为PHY层的信令发送给终端，或者，由接收到的PHY层的信令转变而来。在这种架构下，该RRC或PDCP层的信令，即也可以认为是由DU发送的，或者，由DU和射频发送的。
当采用以上CU-DU的结构时，网络设备可以为CU节点、或DU节点、或包括CU节点和DU节点的RAN设备。
在以上描述中已经了解到，无线网络替换有线网络作为工业控制网络的最后一跳，相对于有线网络，可以降低成本、为维护带来方便，且可以支持从站的灵活部署和移动性。如图6所示，主站将以太帧通过无线网络传输至从站，从站通过无线网络接收以太帧，且可以通过无线网络向主站发送以太帧。因此以太帧需要在无线网络中进行传输，以太帧包括头和负载，其在无线网络传输中需要较多的资源开销，本申请实施例希望减少以太帧在无线网络中传输的开销，以提高资源的利用率。
本申请实施例通过以太帧头压缩的方式来减少无线网络中传输的信息，从而减少资源的开销，提高资源的利用率。
下面结合附图对本申请实施例的压缩、解压方法进行进一步说明。本申请以下实施例中的装置，根据其实现的功能，可以位于不同的设备。
图7为本申请实施例提供的一种太帧头的压缩、解压方法的流程示意图。可以理解，实际应用中，压缩端的压缩过程和解压端的解压过程可以是各自独立实现的，示例的，压缩端完成压缩过程后，可以在之后的任意时间向解压端发送压缩的以太帧，解压端可以在任意时间接收压缩的以太帧，以及对该压缩的以太帧进行解压，本申请实施例对此不作具体限定。如图7所示，本申请实施例提供的方法可以包括以下步骤：
步骤S101：压缩端接收以太帧，该以太帧的以太帧头包括第一待压缩字段。
本申请实施例中，压缩端接收可以从主站接收以太帧，或者从从站接收以太帧。以太帧包括以太帧头和负载，且可以包括多个字段，示例的，如图8所示，是IEEE 802.3定义的802.1Q以太MAC帧格式，在该以太帧格式下，以太帧可以包括以下字段：7个字节的前导码(preamble)，1个字节的帧开始定界符(start of frame delimiter，SFD)，6字节的目的媒介访问控制(media access control，MAC)地址，6字节的源MAC地址，2字节的长度/类型(例如802.1QTagType)，2字节的标记控制信息(TAG控制信息，或，taging control information)，2字节的MAC客户端长度/类型，可变长度的负载或载荷，以及4字节的帧校验序列(frame check sequence，FCS)，其中负载可以包括数据(例如MAC客户端数据)，可选的负载还可以包括填充(padding)字段。负载之前的字段为以太帧头，后续的FCS用于以太帧的校验。以上以太帧格式仅为举例，并非用于限制本申请，在不同的以太帧结构中，该格式可以不同，例如以太帧头可以只包括MAC目的地址、源MAC地址、和长度/类型字段，而其它字段可以部分或全部包括在以太帧中，此外，以上各个字段的大小仅仅为举例，不用于限制本申请。 其中，前导码用于以太帧接收侧识别检测以太传输链路上有以太帧传输；SFD用于以太帧接收侧确定确定后续以太帧内容的起始位置；目的MAC地址是接收侧的MAC地址；源MAC地址是发送方的MAC地址；长度/类型用于标识标记协议；标记控制信息用于指示标记相关信息，MAC客户端长度/类型用于指示以太帧的有效数据长度或MAC客户端协议的以太网类型。
示例的，在图8所示的以太帧格式下，压缩以太帧的以太帧头中，第一待压缩字段可以包括：目的MAC地址、源MAC地址、长度/类型字段、TAG控制信息、或MAC客户端长度/类型。此外，也可以将这些字段任意一个或任意两个或更多字段或全部字段进行压缩，即第一待压缩字段还可以包括以上字段中的两个或多个，例如第一待压缩字段可以包括目的MAC地址和源MAC地址，即只对以太帧头中的MAC地址进行压缩，这种压缩方式适用于其他字段变化较大，而MAC地址字段较为静态的场景下的以太帧头压缩；或者第一待压缩字段可以包括目的MAC地址，TAG控制信息，MAC客户端长度/类型。在不同格式的以太帧头中，第一待压缩字段包括哪些字段可以不同。如下表1所示为Ethernet II类型的帧格式中包含的字段，第一待压缩字段包括目的MAC地址、源MAC地址、类型字段中的任意一个或任意两个或全部字段。
表1
6字节 6字节 2字节 46-1500字节 4字节
目标MAC地址 源MAC地址 类型 数据 FCS
步骤S102：该压缩端根据第一对应关系和该第一待压缩字段确定该以太帧的以太帧头的第一压缩信息，该第一对应关系包括该第一压缩信息和该第一待压缩字段的取值的对应关系。
本申请实施例中，压缩端可以存储压缩信息和待压缩字段的取值的对应关系，其中，第一对应关系是第一压缩信息和第一待压缩字段的取值的对应关系。压缩端存储的对应关系中可以包括该第一对应关系，即第一对应关系可以预先存储在压缩端中；压缩端存储的对应关系中也可以不包括该第一对应关系，此时，第一对应关系也可以是压缩端实时或在数据流传输过程中按需要生成的。本申请实施例对得到第一对应关系的方式不做具体限定。压缩端生成第一对应关系的方法可以根据实际的应用场景进行确定，在后续的实施例中也将进一步说明生成该第一对应关系的方法，本申请实施例在此不进行赘述。
压缩端可以将第一对应关系中所包括的第一压缩信息确定为该以太帧的以太帧头的第一压缩信息。对应关系中的每条对应关系可以关联一个对应关系标识，压缩信息可以包括该对应关系的标识(或称为压缩信息的标识)，此时，第一压缩信息包括第一对应关系的标识或第一压缩信息的标识，以下实施例均以该信息为上下文标(context identifier，CID)为例。
可选的，压缩信息还可以包括配置文件标识(profile identifier，profile ID)，从而第一压缩信息还可以包括第一profile ID。其中，profile ID可以用于标识配置文件(profile)，profile用于规定压缩机制，例如profile用于表示可压缩的字段和/或压缩 的方式等，不同的profile通过profile ID进行区分。或者，可以理解为profile ID用于表示以太帧头的通信协议和/或所述以太帧头的待压缩字段。示例的，profile ID＝1可以表示压缩IEEE 802.3以太帧格式中的目的MAC地址+源MAC地址字段，profile ID＝2可以表示压缩IEEE 802.3以太帧格式中的目的MAC地址+源MAC地址字段+TAG控制信息字段，profile ID＝3可以表示压缩Ethernet 2以太帧格式中的目的MAC地址+源MAC地址+length/type字段，等。以上示例中给出了profile规定了以太协议的待压缩字段示例。可选的，可以引入传输层协议，如此压缩端和被压缩端可以使用不同的profile ID区分传输控制协议/互联网协议(transmission control protocol/internet protocol,TCP/IP)和用户数据报协议/互联网协议(user datagram protocol/internet protocol,TCP/IP)。
可选的，所述压缩信息可以不包括profile ID。例如，压缩端和解压端基于一种profile进行以太头压缩的情况下，压缩端和解压端可以将profile确定为默认的profile，在进行压缩或解压时，可以基于profile进行压缩或解压，此时，压缩信息中可以不包括profile ID。在这种情况下，压缩信息也可以包括profile ID，以方便后续扩展。可选的，压缩端还存储有每条对应关系的指示变量，用于指示每条对应关系的压缩信息是否用于压缩。
在一种实现中，压缩端存储上下文信息，其中上下文信息可以包括至少一个上下文条目(entry)。该上下文信息如下：
条目1：CID 1,profile 1,压缩字段取值A1,是否可用指示；
条目2：CID 2,profile 2,压缩字段取值A2，是否可用指示；
……
条目N：CID 3,profile N,压缩字段取值AN,是否可用指示。
其中，N为正整数，即上下文信息可以包括至少一个上下文条目。每个上下文条目包括CID包括CID和压缩字段取值，即以上所描述的每条对应关系。此外，每个上下文条目还可以包括指示变量，这里称为是否可用指示，用于指示该指示变量所在的上下文条目中的压缩信息(或压缩信息)是否用于压缩。第一对应关系即包括于其中的一个上下文条目(例如第一条目)中。如果压缩端没有存储该第一条目，则生成该第一条目到存储的上下文信息中。对应关系中的每条对应关系可以关联一个对应关系标识，该对应关系标识可以称为上下文标识(context identifier，CID)，即每个上下文条目关联一个CID。此时，压缩信息包括CID，第一压缩信息包括第一CID，该第一CID也可以作为该第一对应关系的标识。可选的，每个上下文条目可以包括profile ID，此时，压缩信息包括profile ID，第一压缩信息包括第一profile ID；当不包括profile ID时，可以采用默认的profile进行压缩。此外，不同上下文条目中包括的profile ID可以相同，例如条目1和条目2可以都采用profile 1。
步骤S103：该压缩端根据该第一压缩信息压缩该以太帧的以太帧头。
本申请实施例中，压缩端可以根据第一压缩信息压缩该以太帧的以太帧头。如果第一压缩信息包括profile ID，则可以根据该profile ID确定profile，根据profile规定的压缩字段，找到第一待压缩字段。如果第一对应关系不包括profile ID，则可以根据默认profile规定的压缩字段，找到第一待压缩字段。第一待压缩字段可以是以太帧头 中的一个字段或多个字段，具体包括哪个或哪些字段可以根据profile确定。当第一待解压字段为以太帧头中的一个字段时，第一对应关系中第一待压缩字段的取值为该一个字段；当当第一待解压字段为以太帧头中的多个字段时，将第一对应关系中第一待压缩字段的取值为该多个字段的取值的组合。示例的，压缩端可以将以太帧头中的第一待压缩字段删除，并在数据包中添加对应的第一CID。可以理解，实际应用中，还可以根据实际的应用场景采用其他方式根据第一压缩信息对该以太帧的以太帧头进行压缩，本申请实施例对此不作具体限定。
适应的，在压缩端完成对以太帧的以太帧头的压缩后，可以进一步将压缩后的以太帧发送给解压端，解压端可以根据该第一压缩信息和该第一待压缩字段的取值的对应关系，实现对压缩后的以太帧的解压，具体如步骤S104至步骤S107的记载。
步骤S104：压缩端向解压端发送压缩后的以太帧。
本申请实施例中，压缩端可以根据实际的应用场景选择适应的方式向解压端发送压缩后的以太帧，本申请实施例对压缩端向解压端发送压缩后的以太帧不做具体限定。
本申请实施例中，该压缩后的以太帧可以包括第一压缩信息，具体的，第一压缩信息可以包括第一CID，使得进一步的，解压端可以根据该第一CID实现对该压缩的以太帧的解压。
在一种可选的实现方式中，压缩端通过分组数据汇聚协议控制协议数据单元(packet data convergence protocol data protocol data unit，PDCP data PDU)向解压端发送压缩后的以太帧。
本申请实施例可以在PDCP data PDU的格式中配置EHC头。示例的，如图9所示，示出了本申请实施例的配置了EHC头的PDCP data PDU的格式，包括：PDCP头、服务数据适配层(service data adaptation protocol，SDAP)头、EHC头、以太数据载荷(ethernet data payload)和完整性消息认证码(message authentication code for integrity，MAC-I)，其中，PDCP头包括PDCP序列号(serial number，SN)，PDCP SN可以设置在不同的行中。图中如果配置表示该字段是可选的，即可以配置，也可以不配置。
可以理解，图9只是示出了PDCP头、SDAP头、EHC头、以太数据载荷和MAC-I的位置的一种方式，实际应用中，PDCP头、SDAP头、EHC头、以太数据载荷和MAC-I的位置以及具体字节长度、包含的内容可以根据实际的应用场景进行适应设定，本申请实施例对此不做具体限定。例如，PDCP SN的长度可以是12比特，或者18比特。示例的，SDAP头可以位于EHC头与以太数据载荷之间，或，SDAP头可以位于以太数据载荷和MAC-I之间，或，SDAP头可以位于MAC-I之后。
本申请实施例中，EHC头中可以包括：指示字段F、CID和所述以太帧头；所述指示字段F用于指示所述EHC头中是否包括有完整的或压缩的以太帧头或用于指示以太头是否被压缩，示例的，如图10所示，示出了本申请实施例的EHC头的格式。其中，指示字段F的长度可以为1-3比特，例如F的长度可以是1比特，取值可以为1或者0，解压端根据F字段的取值可以判断该数据包是否携带了压缩以太帧。在本步骤中，压缩端向解压端发送压缩的以太帧，因此该F字段的取值指示EHC头中包括有压缩的以太帧头或指示以太头是否被压缩。上下文标识(context ID/CID)字段长度取值可以为2-16比特，例如context ID字段长度可以为5比特，或6比特，或7比特， 或8比特，或者16比特，该字段表示对该以太帧进行头压缩所采用的压缩信息标识。以太帧头字段为原始以太帧头除去第一待压缩字段后的部分。上述各个字段的顺序可以是F字段在CID字段之前，CID字段在以太帧头字段之前；或者CID字段在F字段之前，F字段在以太帧头字段之前。即本申请实施例对这些字段之间的先后顺序不做限制。
在本申请实施例的一种可选实现方式中，为了保证EHC是字节对齐的，在EHC中还可能存在一个或者多个预留(R)比特位，例如在F字段之前，F字段与CID字段之间，CID字段与以太帧头之间的至少一个位置处存在至少1比特的预留比特位/R bit。例如，如图11所示，F字段长为1比特，CID字段长为5比特，在CID字段后有2比特的预留比特位。
在本申请实施例的一种可选实现方式中，该EHC头中还可以包括profile ID，profile ID的位置可以在CID和以太帧头之间，本申请实施例对此不作具体限定。此时，以上指示字段F还可以用于指示第一EHC头是否包括profile ID。或者，可以在EHC头中增加一个新的指示字段，用于指示第一EHC头是否包括profile ID。
由于解压端存储的对应关系中可以包括profile ID或者可以采用默认的profile，在本申请实施例的一种可选实现方式中，还可以设定在该压缩以太帧的EHC头中不包括profile ID，从而可以进一步降低压缩后的以太帧的占用空间，进一步降低资源占用。
步骤S105：解压端接收以太帧，该以太帧包括第一对应关系标识，即第一CID。
步骤S106：该解压端根据第一CID确定包括该第一CID的第一对应关系，该第一对应关系包括第一压缩信息和第一待解压字段的取值的对应关系，该第一压缩信息包括第一CID。
本申请实施例中，第一对应关系的具体内容可以与压缩端的第一对应关系的具体内容相同，为了与解压端的解压动作相呼应，将第一对应关系中的与第一压缩信息对应的字段取值称为第一待解压字段的取值，第一压缩信息同以上压缩端的描述，在解压端，也可以称为第一解压缩信息，其包括的内容同以上压缩端的描述。
同压缩端，解压端可以存储压缩信息和待解压字段的取值的对应关系，其中，第一对应关系是第一压缩信息和第一待解压字段的取值的对应关系。解压端存储的对应关系中可以包括该第一对应关系，即第一对应关系可以预先存储在解压端中；解压端存储的对应关系中也可以不包括该第一对应关系，此时，第一对应关系也可以是解压端实时或者在数据流传输时从压缩端接收的。本申请实施例对解压端得到第一对应关系的方式不做具体限定。解压端得到第一对应关系的方法可以根据实际的应用场景进行确定，在后续的实施例中也将进一步说明解压端得到该第一对应关系的方法，本申请实施例在此不进行赘述。
解压端可以将第一对应关系中所包括的待解压字段的取值确定为该以太帧的以太帧头的第一待解压字段的取值。对应关系中的每条对应关系可以关联一个对应关系标识，压缩信息可以包括该对应关系的标识，此时，第一压缩信息包括第一对应关系的标识。
可选的，压缩信息还可以包括profile ID，从而第一压缩信息还可以包括第一profile ID。其中，profile ID可以用于标识profile，profile用于规定压缩机制，例如profile用 于表示可压缩的字段和/或压缩的方式等，不同的profile通过profile ID进行区分。或者，可以理解为profile ID用于表示以太帧头的通信协议和/或所述以太帧头的待压缩字段。此外，同压缩侧，所述压缩信息可以不包括profile ID。详细描述参照压缩侧，在此不再赘述。可选的，同压缩端，解压端可还存储有每条对应关系的指示变量，用于指示每条对应关系的压缩信息是否用于压缩。
同压缩端，解压端可以存储上下文信息，其中上下文信息可以包括至少一个上下文条目(entry)。该上下文信息的描述同以上实施例，在此不再赘述。
在解压端，其与压缩端关于压缩的机制理解是一致的，则解压端的描述中的“压缩”可以替换为“解压”。
步骤S107：该解压端根据该第一压缩信息和该第一待解压字段的取值解压该以太帧的以太帧头。
本申请实施例中，解压端可以采用与压缩端相反的过程来解压以太帧头。解压端根据第一CID，确定第一CID所在的第一对应关系，从而可以找到第一待解压字段的取值。如果第一对应关系或第一压缩信息包括profile ID，则可以根据该profile ID确定profile，根据profile规定的压缩字段，找到第一待解压字段。如果第一对应关系不包括profile ID，则可以根据默认profile规定的压缩字段，找到第一待解压字段。第一待解压字段可以是以太帧头中的一个字段或多个字段，具体包括哪个或哪些字段可以根据profile确定。当第一待解压字段为以太帧头中的一个字段时，将第一对应关系中第一待解压字段的取值填入以太帧头的该字段，实现对待解压以太帧的以太帧头的解压；当第一待解压字段为以太帧头中的多个字段时，将第一对应关系中第一待解压字段的取值根据所述多个字段的大小，拆分为所述多个字段的取值，分别填入所述多个字段，实现对待解压以太帧的以太帧头的解压。示例的，第一待解压字段包括以太帧头的多个字段，如包括目的MAC地址，源MAC地址，和MAC客户端长度/类型，解压端根据第一CID确定第一待解压字段的具体取值后，在恢复原始以太帧头时，在对应的以太帧头字段位置填充相应字段的取值，如解压端在目的MAC地址字段位置填充目的MAC地址取值，源MAC地址字段位置填充源MAC地址取值，MAC客户端长度/类型字段位置填充MAC客户端长度/类型取值。可以理解，实际应用中，还可以根据实际的应用场景采用与压缩端的压缩方式对应的解压方式进行解压，本申请实施例对此不作具体限定。
综上，本申请实施例中，压缩端可以在接收到包括第一待压缩字段的以太帧后，通过包括第一压缩信息和该第一待压缩字段的取值的第一对应关系，根据第一压缩信息对该以太帧的以太帧头进行压缩，适应的，解压端可以在接收到压缩后的以太帧的情况下，根据第一对应关系实现对压缩后的以太帧的以太帧头的解压，本申请实施例中，因为对以太帧的以太帧头进行了压缩，所以可以节省通信资源。
本申请实施例的第一对应关系可以通过压缩端生成，并在解压端进行同步，在解压端完成该第一对应关系的同步后，解压端和压缩端可以根据该第一对应关系进行适应的压缩和解压操作，图12为本申请实施例提供的一种在压缩端和解压端同步第一对应关系的方法的流程示意图，如图12所示，本申请实施例提供的方法包括以下步骤：
步骤S201：压缩端生成第一对应关系。
本申请实施例中，压缩端可以在接收到以太帧后，基于接收到的以太帧所包括的待压缩字段，生成第一对应关系。本申请实施例中，压缩端接收的以太帧可以相同也可以不同于图7对应的实施例中的以太帧，且本申请实施例的以太帧的以太帧头的待压缩字段的取值，与图7对应的实施例中的的第一待压缩字段的取值相同。
其中待压缩字段同以上实施例的描述，可以为以太帧头中的一个或多个字段，例如压缩端也可以基于目的MAC地址、源MAC地址、长度/类型字段、TAG控制信息、以及MAC客户端长度/类型等字段中的一个或多个字段生成第一对应关系。本申请实施例对生成第一对应关系的具体方式不作限定。
具体应用中，压缩端可以存储有预先生成的对应关系，该对应关系包括压缩信息和待压缩字段的取值的对应关系。在压缩端接收到包括第一待压缩字段的以太帧后，当该压缩端存储的对应关系不包括该以太帧的第一待压缩字段的取值时，压缩端生成该第一对应关系，该第一对应关系可以包括：CID和第一待压缩字段的取值。参照以上实施例，可以上下文信息的方式存储对应关系，在此不再赘述。当第一待压缩字段为一个字段时，第一待压缩字段的取值为该一个字段的取值；当第一待压缩字段为多个字段时，第一待压缩字段的取值为该多个字段的取值的组合，其中每个字段的取值的长度，可以由profile规定。多个字段的取值的组合方式可以根据profile进行确定，例如，profile中规定了各字段的位置关系，则可以按照各字段的位置顺序进行组合，本申请实施例对此不作具体限定。
示例的，当前压缩端保存了包括CID 1和CID2的对应关系，CID 1的待压缩字段的取值为A，CID 2的待压缩字段的取值为B，当压缩端有新的以太帧到达，并且以太帧头的待压缩字段的取值为C，在当前保存的对应关系中找不到C的匹配项，则压缩端为第一待压缩字段分配一个新的CID，例如CID3。
在一种可选的实现方式中，同以上实施例，该压缩信息还包括profile ID。在压缩端和解压端基于一种profile进行EHC的情况下，压缩端和解压端可以将该profile确定为默认的profile，在进行压缩或解压时，可以基于该profile进行压缩或解压，则压缩信息中可以不包括profile ID。
步骤S202：压缩端向解压端发送该第一对应关系。
本申请实施例中，压缩端可以根据实际的应用场景采用适应的方式向解压端发送该第一对应关系，本申请实施例对此不作具体限定。
在一种可选的实现方式中，该压缩端向解压端发送非压缩数据包，该非压缩数据包包括该第一对应关系。
本申请实施例中，压缩端可以将第一对应关系和接收到的以太帧作为非压缩数据包发送给解压端。在一种可选的实现方式中，压缩端可以通过PDCP data PDU向解压端发送非压缩数据包；在另一种可选的实现方式中，压缩端可以通过分组数据汇聚协议控制协议数据单元PDCP control PDU向解压端发送第一对关系，且通过PDCP data PDU向解压端发送以太帧数据包。
在本申请实施例的一种可选实现方式中，该压缩端可以向解压端多次发送该第一对应关系，则适应的第一对应关系还可以对应设置次数阈值，例如，该压缩端对第一 对应关系维护一个发送次数变量，该变量初始值可以为0，压缩端端对第一对应关系发送一次，则发送次数变量累计1，在压缩端向解压端发送该第一对应关系的次数达到次数阈值时，可以认为解压端已成功接收该第一对应关系，则可以认为第一对应关系在压缩端和解压端已实现同步，则可以不进行步骤S204的步骤。可以理解，次数阈值可以是协议预定义的，或者网络设备配置的大于或等于1的数，在侧行链路通信场景，次数阈值还可以是由压缩端自己确定的，或者由其他终端设备配置给压缩端的，本申请实施例对此不做具体限定。
步骤S203：该解压端从压缩端接收该第一对应关系。
本申请实施例中，解压端可以根据实际的应用场景采用适应的方式从压缩端接收该第一对应关系，本申请实施例对接收的具体方式不做限定。
在一种可选的实现方式中，在解压端接收到第一对应关系后，当该解压端存储的对应关系不包括该第一压缩信息时，该解压端存储该第一对应关系。
在另一种可选的实现方式中，在解压端接收到第一对应关系后，当该解压端存储的对应关系包括该第一压缩信息时，且该第一压缩信息对应待解压字段的取值与该第一待解压字段的取值不同，该解压端将该第一压缩信息对应待解压字段的取值修改为该第一待解压字段。
参照以上实施例，解压端也可以上下文信息的方式存储对应关系，在此不再赘述。
步骤S204：该解压端向该压缩端发送反馈信息，该反馈信息用于指示该第一对应关系的接收状态。
本申请实施中，解压端还可以向该压缩端发送反馈信息，该反馈信息用于指示该第一对应关系的接收状态。示例的，接收状态可以包括接收成功或接收失败。可以理解，在接收状态为接收成功时，压缩端和解压端可以基于该第一对应关系进行相应的压缩、解压处理。在接收状态为接收失败时，压缩端和解压端不能基于该第一对应关系进行相应的压缩、解压处理，进一步的，压缩端可以重新发送该第一对应关系给压缩端，或删除该第一对应关系等，本申请实施例对此不做具体限定。
在一种可选的实现方式中，该反馈信息包括该CID，或确认携带第一对应关系的数据包的PDCP SN。则压缩端可以基于该CID或PDCP SN确定具体的未成功接收的对应关系。
在一种可选的实现方式中，该反馈信息还包括以下至少一项：profile ID、第一指示字段、第二指示字段，该第一指示字段用于指示该第一对应关系在该解压端为新增的对应关系或修改的对应关系，该第二指示字段用于指示该反馈信息为肯定反馈或否定反馈。当反馈信息中包括CID和上述至少一项信息时，CID和各项信息占用的具体比特长度，在反馈信息中的具体位置在本申请实施例中不做限定。
示例的，如图13所示，示出了一种该反馈信息的格式示意图。在该格式示意图中，反馈信息通过PDCP control PDU进行发送，且包括CID字段、第一指示字段(AddOrModify)、第二指示字段(AckType)。第一个字节为PDCP control PDU的头，其中D/C字段的取值表示该PDCP PDU为control PDU，PDU类型(type)取值表示该control PDU是用于传输反馈信息的control PDU，例如PDU type取值可以为除‘000’和‘001’之外的值，如‘010’，或‘011’等。上下文标识(context ID/CID)字段长度 取值可以为2-16比特，例如context ID字段长度可以为5比特，或6比特，或7比特，或8比特，或者16比特；AckType字段长度取值可以为1-4比特，例如AckType字段长度为1比特，取值为1或0，AckType＝1表示反馈成功操作，AckType＝0表示反馈失败操作，或AckType＝0表示反馈成功操作，AckType＝1表示反馈失败操作；AddOrModify字段长度取值可以为1-4比特，例如AddOrModify字段长度为1比特，取值为1或0，AddOrModify＝1表示反馈的是新增上下文信息，AckType＝0表示反馈的是修改上下文信息，或AddOrModify＝0表示反馈的是新增上下文信息，AckType＝1表示反馈的是修改上下文信息。上述各个字段的先后顺序可以是CID字段，AckType字段，AddOrModify字段；AckType字段，CID字段，AddOrModify字段；AckType字段，AddOrModify字段，CID字段。本申请实施例不做限制。
在本申请实施例的可选实现方式中，为了保证用于反馈的PDCP control PDU是字节对齐的，在该control PDU中还可能存在一个或者多个预留比特位，例如在图13所示的字段顺序前提下，在PDCP control PDU头和CID之间，CID字段和AckType字段之间，AckType字段与AddOrModify字段之间的至少一个位置处存在至少1比特的预留比特位。
同以上实施例描述，作为本申请实施例的一种可选的实现方式，该压缩端还存储有每个对应关系的指示变量，该指示变量用于指示相应的对应关系的压缩信息是否用于压缩。
本申请实施例中，考虑到可能存在解压端不能正确接收第一对应关系的情况，则即使压缩端中生成了第一对应关系，该第一对应关系也不可用于压缩，因此，在压缩端还可以存储有该对应关系的指示变量，该指示变量用于指示该对应关系的压缩信息是否用于压缩。示例的，该指示变量的取值可以包括0和1，在指示变量为1的情况下，表示该第一对应关系可用，在指示变量为0的情况下，表示该第一对应关系不可用于压缩；或者，在指示变量为0的情况下，表示该第一对应关系可用，在指示变量为1的情况下，表示该第一对应关系不可用于压缩。
可选的，当该压缩端存储的对应关系包括该以太帧的第一待压缩字段对应的第一对应关系，且该第一对应关系的指示变量指示该第一对应关系的压缩信息不用于压缩时，该压缩端向该解压缩端发送该第一对应关系。
本申请实施例中，压缩端向解压端发送第一对应关系的方式参照步骤S202的记载，在此不再赘述。
可选的，在该压缩端确认该第一对应关系被该解压端正确接收时，该压缩端将该指示变量设置为第一值，该第一值用于指示该压缩信息用于压缩。
本申请实施例中，压缩端确认该第一对应关系被解压端正确接收的方式可以有多种，示例的，压缩端可以向解压端发送N次该第一对应关系，N为大于或等于1的值，则，压缩端确认该第一对应关系被解压端正确接收；或者，压缩端接收解压端发送的用于表明该第一对应关系被正确接收的反馈信息，则压缩端确认该第一对应关系被解压端正确接收。本申请实施对压缩端确认该第一对应关系被解压端正确接收的具体方式不作限定。
本申请实施例中，第一值可以根据实际的应用场景设定，例如可以为1或0，本申请实施例对此不作具体限定。
可以理解，实际应用中，在压缩端初始生成该第一对应关系时，可以将该第一对应关系的指示变量设置为第二值，该第二值用于指示该压缩信息不能用于压缩。第二值可以根据实际的应用场景设定，例如可以为0或1，本申请实施例对此不作具体限定。
作为一种可选的实现方式，本申请实施例还可以包括：该压缩端向解压端发送第二指示信息，该第二指示信息用于指示该第一对应关系在该压缩端为新增的对应关系或修改的对应关系。
本申请实施例中，考虑到第一对应关系可以是新增加的，也可以是之前已经存在但是对应的指示变量为不可用，因此，可以通过第二指示信息指示该第一对应关系在该压缩端为新增的对应关系或修改的对应关系。
综上所述，本申请实施例在压缩端和解压端同步可以进行压缩和解压的对应关系，则后续在压缩端和解压端之间传输以太网数据包时，可以根据该同步的对应关系，对以太帧头进行压缩和解压，从而可以降低以太帧头对通信资源的占用。
作为本申请实施例的步骤S202的一种可选的具体实现，在压缩端通过PDCP data PDU向解压端发送非压缩数据包的方式中，步骤S202可以包括：该压缩端通过PDCP data PDU向该解压端发送该第一对应关系；其中，该PDCP data PDU包括：EHC头，该EHC头包括指示字段、该CID和该以太帧头；该指示字段用于指示该EHC头中是否包括有完整的或压缩的以太帧头或用于指示以太帧头是否被压缩。
示例的，如图14所示，在压缩端通过PDCP data PDU向解压端发送第一对应关系时，该EHC头的指示字段F可以用于指示该EHC头是否包括完整的或压缩的以太帧头或用于指示以太帧头是否被压缩，示例的，该指示字段F的长度可以为1-3比特，例如F的长度可以是1比特，取值可以为1或者0，解压端根据F字段的取值可以判断该数据包是否携带了完整以太帧头。CID字段长度取值可以为2-16比特，例如CID字段长度可以为5比特，或6比特，或7比特，或8比特，或者16比特；该字段表示对该以太帧进行头压缩所采用的对应压缩信息标识。以太帧头字段为原始以太帧头，包括待压缩字段和不压缩字段。上述各个字段的先后顺序可以是F字段，CID字段，以太帧头；或者CID字段，F字段，以太帧头。本申请实施例不做限定。
在本申请实施例的一种可选实现方式中，为例保证EHC是字节对齐的，在EHC中还可能存在一个或者多个预留比特位，例如在以图14为例的字段顺序前提下，在F字段之前，F字段与CID字段之间，以及CID字段与以太帧头之间的至少一个位置处可以存在至少1比特的预留比特位。示例的，如图15所示，F字段长为1比特，CID字段长为6比特，在CID字段和以太帧头之间有1比特的预留比特位。
可选的，在第一对应关系中可能携带profile ID的情况下，该指示字段F还用于指示该第一EHC头是否包括配置文件标识profile ID。当该指示字段F指示包括profile ID时，该EHC头还包括profile ID。或者，可以在EHC头中增加一个新的指示字段，用于指示第一EHC头是否包括profile ID。
示例的，如图16所示，在压缩端通过PDCP data PDU向解压端发送第一对应关系时，该EHC头的指示字段F可以用于指示该EHC头是否包括完整的或压缩的以太帧头，以及是否携带profile ID。该指示字段F的长度可以为1-3比特，例如F的长度可以是1比特，取值可以为1或者0，解压端根据F字段的取值可以判断该数据包携 带了完整以太帧头，并且携带了profile ID字段。CID字段长度取值可以为2-16比特，例如CID字段长度可以为5比特，或6比特，或7比特，或8比特，或者16比特；该字段表示对该以太帧进行头压缩所采用的对应压缩信息标识。profile ID字段的长度取值可以为2-8比特，例如profile ID字段长度可以为4比特，或5比特，或6比特，或者8比特。以太帧头字段为原始以太帧头，包括待压缩字段和不待压缩字段。上述各个字段的先后顺序可以是F字段，CID字段，profile ID字段，以太帧头；或者CID字段，F字段，profile ID字段，以太帧头。
在本申请实施例的一种可选实现方式中，为例保证EHC是字节对齐的，在EHC中还可能存在一个或者多个预留比特位，例如在以图16为例的字段顺序前提下，在F字段之前，F字段与CID字段之间，CID字段和profile ID字段之间，以及profile ID字段与以太帧头之间的至少一个位置处可以存在至少1比特的预留比特位。示例的，如图17所示，F字段长为1比特，CID字段长为6比特，profile ID长度为6比特，在CID字段和profile ID之间有3比特的预留比特位。
可选的，该PDCP data PDU还包括：PDCP头、服务数据适配层SDAP头、以太数据载荷和MAC-I。类似于图9中的PDCP data PDU的格式，在此不再赘述。
作为本申请实施例的步骤S202另一种可选的具体实现，在通过PDCP control PDU向解压端发送第一对关系，且通过PDCP data PDU向解压端发送以太帧的方式中，步骤S202可以包括：压缩端通过PDCP control PDU向该解压端发送该第一对应关系；其中，该PDCP control PDU包括指示信息、该CID和该以太帧头的可压缩字段取值；该指示信息用于指示该PDCP control PDU用于该第一对应关系。可选的，该PDCP control PDU也可以不包括待压缩字段取值，而是后续向解压端发送PDCP data PDU，该PDCP data PDU带有以太帧头，该以太帧头的待压缩字段的取值等于该待压缩字段的取值。
示例的，如图18所示，在PDCP control PDU向解压端发送第一对关系，且通过PDCP data PDU向解压端发送以太帧的方式中，指示信息为PDU Type，第一个字节为PDCP control PDU的头，其中，D/C字段的取值表示该PDCP PDU为control PDU，PDU type取值表示该control PDU是用于传输第一对应关系的control PDU，例如PDU type取值可以为除‘000’和‘001’之外的值，如‘010’，或‘011’等。CID字段长度取值可以为2-16比特，例如CID字段长度可以为5比特，或6比特，或7比特，或8比特，或者16比特；该字段表示对该以太帧进行头压缩所采用的对应压缩信息标识。待压缩字段的取值为CID字段对应的第一关系中第一待压缩字段的取值，即只包括以太帧头中待压缩字段的具体取值。上述各个字段的先后顺序可以是CID字段，待压缩字段的取值；或者CID字段，待压缩字段的取值。
在本申请实施例的一种可选实现方式中，为了保证该PDCP control PDU是字节对齐的，在该control PDU中还可能存在一个或者多个预留比特位，例如在图18为例的字段顺序前提下，如图19所示，在control PDU头和CID字段之间可以存在至少1比特的预留比特位R。
可选的，在第一对应关系中可能携带profile ID的情况下，该PDCP control PDU还包括：profile ID。
示例的，如图20所示，PDCP control PDU还包括profile ID，其中D/C字段的取 值表示该PDCP PDU为control PDU，PDU type取值表示该control PDU是用于传输第一对应关系的control PDU，例如PDU type取值可以为除‘000’和‘001’之外的值，如‘010’，或‘011’等。上下文标识(context ID/CID)字段长度取值可以为2-16比特，例如context ID字段长度可以为5比特，或6比特，或7比特，或8比特，或者16比特；该字段表示对该以太帧进行头压缩所采用的对应压缩信息标识。配置文件标识(profile ID)字段的长度取值可以为2-8比特，例如profile ID字段长度可以为4比特，或5比特，或6比特，或者8比特。待压缩字段的取值为CID字段对应的第一关系中第一待压缩字段的取值，即只包括待压缩字段的具体取值。上述各个字段的先后顺序可以是CID字段，profile ID字段，待压缩字段的取值；或者profile ID字段，CID字段，待压缩字段的取值。即本申请实施例对这些字段之间的先后顺序不做限制。
在本申请实施例的一种可选实现方式中，为了保证该PDCP control PDU是字节对齐的，在该control PDU中还可能存在一个或者多个预留比特位，例如在图20为例的字段顺序前提下，在control PDU头和CID字段之间，CID字段和profile ID字段之间，以及profile ID字段与待压缩字段的取值之间的至少一个位置处可以存在至少1比特的预留比特位。示例的，如图21所示，在control PDU头和CID字段之间可以存在至少1比特的预留比特位。或者，如图22所示，CID字段长为8比特，profile ID长度为7比特，在profile ID之间和待压缩字段的取值字段之间有1比特的预留比特位。
本申请实施例中，压缩端还向该解压端发送PDCP data PDU；其中，该PDCP data PDU包括：EHC头，该EHC头携带指示字段、和该以太帧头；该指示字段用于指示该EHC头中是否携带CID。
本申请实施例中，指示字段F的长度可以为1-3比特，例如F的长度可以是1比特，取值可以为1或者0，F＝0可以表示后续以太帧头是压缩后的以太帧头，F＝1可以标识后续以太帧头是原始的以太帧头，或者，F＝1可以表示后续以太帧头是压缩后的以太帧头，F＝0可以标识后续以太帧头是原始的以太帧头。在本步骤中，压缩端向解压端发送未压缩的以太帧，因此该F字段的取值指示EHC头中包括有压缩的以太帧头或指示以太头是否被压缩。以太帧头字段为原始以太帧头还是除去待压缩字段后的压缩以太帧头由指示字段F进行指示。可选的，当该EHC头携带CID时，该以太帧头为压缩的以太帧头，或者，当该EHC头未携带CID时，该以太帧头为完整的以太帧头。
示例的，该EHC头的格式可以如图23所示，上下文标识(context ID/CID)字段长度取值可以为2-16比特，例如context ID字段长度可以为5比特，或6比特，或7比特，或8比特，或者16比特；该字段表示对该以太帧进行头压缩所采用的对应压缩信息标识；当F取值表示后续以太帧头为原始帧头时，解压端可以忽略CID字段的具体取值，或者EHC头中不存在CID字段，此时为了保证EHC头字节对齐，多出来的比特位置可以填充预留比特位。以太帧头字段为原始以太帧头还是除去第一待压缩字段后的压缩以太帧头由F指示字段进行指示。上述各个字段的顺序可以是F字段在CID字段之前，CID字段在以太帧头字段之前；或者CID字段在F字段之前，F字段在以太帧头字段之前。即本申请实施例对这些字段之间的先后顺序不做限制。
在本申请实施例一种可选的实现方式中，为了保证EHC是字节对齐的，在EHC 中还可能存在一个或者多个预留比特位，例如在F字段之前，F字段与CID字段之间，CID字段与以太帧头之间的至少一个位置处存在至少1比特的预留比特位。
可选的，该第一PDCP data PDU还包括：PDCP头、服务数据适配层SDAP头、以太数据载荷和MAC-I。类似于图9中的PDCP data PDU的格式，在此不再赘述。
本申请实施例的压缩端向解压端传输压缩后的以太帧，以及解压端解压该压缩后的以太帧的场景中，还可以设置校验的过程，以提升压缩、解压的正确率。因此，步骤S104中，用于向解压端发送压缩后的以太帧的PDCP data PDU的EHC头还包括：校验信息。
如图24所示，示出了一种包括校验码的EHC头的格式示意图，校验码可以位于profile ID和以太帧头之间，可以理解，在EHC头中不包括profile ID时，校验码可以位于CID和以太帧头之间，校验码还可以位于以太帧头之后，或F字段和CID之间，即本申请实施例对这些字段之间的先后顺序不做限制。具体应用中，为例对齐EHC头的字节，也可以在EHC头中适应的添加一个或多个预留比特位，本申请实施例对此不作具体限定。
本申请实施例中，该校验信息为根据该第一对应关系中的一个或多个信息生成的。
示例的，校验信息可以是循环冗余校验码(cyclic redundancy check，CRC)也可以是校验和(checksum)。
作为本申请实施例的一种可选的实现方式，在校验信息为CRC的实现中，压缩端收到以太帧后，基于将要使用的对应关系中对应的压缩字段取值、完整的CID、完整的profile ID、原始以太帧头等的一种或多种作为输入，通过一定的生成多项式，生成X(X可以为根据实际应用确定)比特的第一校验信息CRC 1。
适应的，解压端收到压缩的以太帧后，也可以基于EHC头中的CID，和/或profile ID确定解压要用的对应关系，并基于对应关系中对应的压缩字段取值、完整的CID、完整的profile ID、解压出来的以太帧头等的一种或多种作为输入，通过与压缩端相同的生成多项式，生成X比特的第二校验信息CRC 2。如果CRC 2≠CRC 1，则确认解压失败；或者解压端找不到CID对应的context信息，也确认解压失败。
作为本申请实施例的另一种可选的实现方式，在校验信息为checksum的实现中，压缩端收到以太帧后，基于将要使用的对应关系中对应的压缩字段取值、完整的CID、完整的profile ID、原始以太帧头等的一种或多种作为输入，通过一定的checksum算法，生成X(X可以为根据实际应用确定)比特的第一校验信息checksum1。
适应的，解压端收到压缩的以太帧后，也可以基于EHC头中的CID，和/或profile ID确定解压要用的对应关系，并基于对应关系中对应的压缩字段取值、完整的CID、完整的profile ID、解压出来的以太帧头等的一种或多种作为输入，通过与压缩端相同的checksum算法，生成X比特的第二校验信息checksum 2。如果checksum 2≠checksum 1，则确认解压失败；或者解压端找不到CID对应的context信息，也确认解压失败。
作为一种可选的实现方式，在第一校验信息与所述第二校验信息相同的情况下，解压端根据第一待解压字段的取值解压待解压以太帧的以太帧头；或，在第一校验信息与第二校验信息不同的情况下，解压端删除所述第一对应关系；和/或，解压端向压 缩端发送错误报告。
本申请实施例中，在第一校验信息与第二校验信息不同的情况下，解压端确认校验失败，则解压端可以删除解压端存储的第一对应关系，或着向压缩端发送错误报告，或删除解压端存储的第一对应关系并向压缩端发送错误报告，本申请实施例对此不作具体限定。
本申请实施例中，错误报告可以用于指示校验失败，解压端不能实现对压缩的以太帧进行解压。错误报告中可以携带CID，和/或，profile ID。可选的，错误报告中也可以携带CRC3，该CRC3是基于错误报告本身为输入，利用一个生成多项式生成的。
作为本申请实施例的一种可选实现方式，在压缩端接收到解压端根据校验信息返回的错误报告的情况下，压缩端可以删除第一对应关系，或压缩端将第一对应关系设置为不可用。
本申请实施例中，压缩端可以将第一对应关系对应的指示变量设置为第二值，用于指示该第一对应关系不可用，具体应用中，如果第一对应关系还对应有向解压端发送时的发送次数，则可以将发送次数置为初始值，示例的，初始值可以为0。
作为本申请实施例的一种可选实现方式，解压端在确认校验出错时，可以清空解压端存储的全部对应关系，并向压缩端反馈错误报告，该错误报告中不携带CID，profile ID。适应的，压缩端收到错误报告后，可以清空所有对应关系，或者将所有对应关系置为不可用，如果对应关系还对应有发送次数，则发送次数置为初始值(例如为0)。
本申请实施例中，通过引入校验机制，避免因为压缩端和解压端保存的对应关系不一致，导致解压数据包出错，提升了压缩、解压中的正确率。
本申请实施例的压缩端和解压端在进行上述的压缩、解压实现之前，还可以预先配置执行EHC的能力。在本申请实施例的一种可选的配置实现中，该压缩端为终端，该解压缩端为网络设备，该方法还包括：
该压缩端向该解压端发送能力信息；该能力信息包括下述至少一项：该压缩端支持EHC的能力，该压缩端中支持EHC的数据无线承载(data radio bearer，DRB)的个数压缩端压缩端压缩端压缩端，该压缩端支持的配置文件profile信息压缩端压缩端，每个支持EHC的DRB所支持的对应关系条目的最大值MAX_CID压缩端，该压缩端支持动态配置profile参数的能力压缩端压缩端，该压缩端支持EHC的DRB所维护的对应关系条目的总和压缩端压缩端压缩端压缩端压缩端压缩端压缩端压缩端压缩端。
本申请实施例中，该压缩端支持EHC的能力，具体可以包括该压缩端支持上行EHC的能力，和/或，该压缩端支持下行EHC的能力，该压缩端中支持EHC的DRB的个数用于表示压缩端能够被配置执行EHC操作的DRB的最大个数，当压缩端不指示该信息时，压缩端支持EHC的DRB最大个数可以由协议进行规定，或者表示压缩端支持EHC的DRB个数没有限制。该压缩端支持的配置文件profile信息，具体可以包括该压缩端支持的上行profile信息，和/或，该压缩端支持的下行profile信息，可以用于指示该压缩端能够处理哪些profile对应的以太协议帧的EHC处理，当不指示该信息时，表示压缩端支持所有协议定义的profile对应以太协议帧的EHC处理。其他的能力，如一个DRB支持的MAX_CID数目，支持的总CID个数都可以分为上行 和/或下行分别进行指示。可以理解，对于每个支持EHC的DRB所支持的对应关系条目的最大值MAX_CID，当压缩端不指示该MAX_CID时，一个DRB所支持的MAX_CID可以由协议进行规定，或者表示没有限制。当压缩端不指示该该压缩端支持动态配置profile参数的能力信息时，表示压缩端支持/不支持网络设备条动态配置profile参数。可以理解，压缩端保存维护一条对应关系时，需要一定的内存存储该对应关系，从终端设备角度来说，支持的内存是有限的，因此能够被用来存储对应关系的内存可能也是受限的；当压缩端不指示该压缩端支持EHC的DRB所维护的对应关系条目的总和时，压缩端支持的总对应关系数目可以由协议进行规定，或者表示没有限制。
可选的，能力信息还可以包括：该压缩端支持处理解压端的反馈信息的能力，当压缩端不指示该信息时，表示压缩端支持/不支持反馈信息处理。能力信息还可以包括：该压缩端支持多次第一对应关系发送的能力，当压缩端不指示该信息时，表示压缩端支持/不支持多次发送第一对应关系。
具体应用中，压缩端可以通过无线资源控制(radio resource control，RRC)消息向解压端发送能力信息，也可以采用其他方式向解压端发送能力信息，本申请实施例对此不作具体限定。
适应的，解压端可以为压缩端配置以下至少一项：支持上行EHC的DRB或分组数据汇聚协议PDCP实体的信息、支持下行EHC的DRB或PDCP实体的信息、支持上行EHC的DRB或PDCP实体所支持的配置文件信息、支持下行EHC的DRB或PDCP实体所支持的配置文件信息、每个DRB或PDCP实体进行EHC操作时所采用的压缩上下文信息条目的最大值、所述压缩端中支持EHC的DRB所维护的压缩上下文信息条目的总和、EHC进行反馈操作、EHC进行多次发送第一对应关系操作、多次发送第一对应关系时的发送次数阈值。可选的，解压端可以通过RRC信令为压缩端配置上述内容。
本申请实施例一种可选的实现方式中，在压缩端中配置了MAX_CID的情况下，如果发现之前存储的对应关系中的条目已经达到MAX_CID，则对后续数据包不再建立新的对应关系，且只利用现有对应关系进行数据包压缩，如果新到达数据包找不到对应关系，则不进行压缩处理；例如，压缩端中的CID已经用完，后续数据包都可以不进行压缩处理，数据包发送时也不携带第一对应关系，或者终端可以基于实现对部分数据包不进行压缩处理。此时，数据包封装的格式可以有两种考虑：其中一种为，考虑PDCP data PDU中的EHC头中不包含profile ID字段，EHC头中F字段指示数据包是非压缩数据包，同时Context ID字段取值为一个预留的值，如全0或者全1值，压缩端收到该数据包，根据F字段取值和CID预留值，即可判断该数据包是未压缩数据包，且也未携带第一对应关系。另一种为考虑PDCP data PDU中的EHC头包含profile ID字段，EHC头中F字段指示数据包是非压缩数据包，同时Context ID和/或profile ID字段取值为一个预留的值，如全0或者全1值，压缩端收到该数据包，根据F字段取值和CID预留值和/或profile ID预留值，即可判断该数据包是未压缩数据包，且也未携带第一对应 关系。
本申请实施例另一种可选的实现方式中，在压缩端中配置了MAX_CID的情况下，如果发现之前存储的对应关系中的条目已经达到MAX_CID，压缩端仍生成第一对应关系，并可以用第一对应关系替换之前存储的对应关系中的任一条目，从而实现第一对应关系的存储，上述任一条目可以是压缩端随机选择的，或通过其他方式确定的，本申请实施例不做限定。
作为本申请实施例的一种可选实现方式，该方法还包括：该终端接收配置信息，该配置信息还用于指示EHC头是否携带profile ID；或者，该配置信息还包括profile ID，且该EHC头不包括profile ID。
本申请实施例中，当RRC配置一个DRB只支持一个profile时，该DRB的数据包的EHC header中不携带profile ID，否则EHC header中需要携带profile ID。
在配置信息还用于指示EHC头是否携带profile ID的具体实现中，终端可以接收网络设备通过RRC发送的配置信息，该RRC中可以通过一定的字段指示EHC头是否携带profile ID。示例的，可以通过一个presence of profileID字段指示EHC头中是否携带profile ID；例如，在PDCP配置信元中携带了presence of profileID字段，则表示EHC header中携带profile ID，如果未携带该presence of profileID字段，则EHC header中不携带profile ID。
可选的，还可以通过将presence of profileID取值1或0，1表示EHC header携带profile ID，0表示EHC header不携带profile ID。或者，0表示EHC header携带profile ID，1表示EHC header不携带profile ID。
可选的，还可以为终端的上行EHC和下行EHC操作分别配置presence of profileID字段，用于指示上行和下行EHC header中是否携带profile ID。例如，配置presence of profileID-UL字段指示上行EHC header中是否携带profile ID，配置presence of profileID-DL字段指示下行EHC header中是否携带profile ID。或者，还可以通过将presence of profileID-UL取值1或0，1表示上行EHC header携带profile ID，0表示上行EHC header不携带profile ID，或者0表示上行EHC header携带profile ID，1表示上行EHC header不携带profile ID，将presence of profileID-DL取值1或0，1表示下行EHC header携带profile ID，0表示下行EHC header不携带profile ID，或者，0表示下行EHC header携带profile ID，1表示下行EHC header不携带profile ID。本申请实施例对各字段的取值不作具体限定。
可选的，还可以根据RRC配置DRB支持的profile数目隐式确定该DRB的EHC数据包中是否携带profile ID字段，示例的，若RRC配置DRB支持的profile数目为1，则可以认为指示不携带profile ID，，若RRC配置DRB支持的profile数目为大于1的值，则可以任务指示携带profile ID。
在该配置信息还包括profile ID，且该EHC头不包括profile ID的具体实现中，可以通过配置信息配置终端的profile ID，进而使得EHC头中可以不包括profile ID，从而可以减小EHC头的大小，降低对通信资源的占用。
在本申请实施例的一种可选的配置实现中，该压缩端为网络设备，该解压端为终端，该方法还包括：
该压缩端接收能力信息，该能力信息包括下述至少一项：该能力信息包括下述至少一项：该解压端支持EHC的能力，该解压端中支持EHC的数据无线承载DRB的个数，该解压端支持的配置文件profile信息，每个支持EHC的DRB所支持的对应关系条目的最大值MAX_CID，该解压端支持动态配置profile参数的能力，该解压端支持EHC的DRB所维护的对应关系条目的总和。
本申请实施例中，压缩端在接收到解压端的能力信息后，可以适应的为解压端配置至少一项：支持上行EHC的DRB或分组数据汇聚协议PDCP实体的信息、支持下行EHC的DRB或PDCP实体的信息、支持上行EHC的DRB或PDCP实体所支持的配置文件信息、支持下行EHC的DRB或PDCP实体所支持的配置文件信息、每个DRB或PDCP实体进行EHC操作时所采用的压缩上下文信息条目的最大值、所述压缩端中支持EHC的DRB所维护的压缩上下文信息条目的总和。可选的，压缩端可以通过RRC信令为解压端配置上述内容。
作为本申请实施例的一种可选实现方式，该方法还包括：该网络设备向该终端发送配置信息，该配置信息还用于指示EHC头是否携带profile ID；或者，该配置信息还包括profile ID，且该EHC头不包括profile ID。
具体的配置过程可以参照上述实施例的配置过程，在此不再赘述。
在本申请实施例的一种可选的配置实现中，该压缩端为终端，该解压端为终端，该方法还包括：
该压缩端接收能力信息，该能力信息包括下述至少一项：该能力信息包括下述至少一项：该解压端支持EHC的能力，该解压端中支持EHC的数据无线承载DRB的个数，该解压端支持的配置文件profile信息，每个支持EHC的DRB所支持的对应关系条目的最大值MAX_CID，该解压端支持动态配置profile参数的能力，该解压端支持EHC的DRB所维护的对应关系条目的总和。
本申请实施例中，可以是两个终端通过sidelink通信的场景，两个终端之间可以通过sidelink消息交互对EHC的支持能力，例如两个终端直接通过sidelink RRC消息交互sidelink接口的EHC能力，或两个终端通过基站或其他终端交互sidelink接口的EHC能力。也即，本申请实施例中，压缩端可以通过sidelink消息接收解压端的能力信息，或者通过基站或其他终端接收解压端的能力信息，本申请实施例对此不作具体限定。
适应的，解压端也可以接收压缩端的能力信息，实现解压端和压缩端之间能力信息的交互，在此不作赘述。
作为本申请实施例的一种可选实现方式，压缩端和解压端还可以交互配置信息，该配置信息还用于指示EHC头是否携带profile ID；或者，该配置信息还包括profile ID，且该EHC头不包括profile ID。在此不作赘述。
具体的配置过程可以参照上述实施例的配置过程，在此不再赘述。
在本申请实施例的一种可选实现方式中，可能存在压缩端或解压端发生切换的场景，示例的，在压缩端为终端，解压端为网络设备的情况下，压缩端可能切换到不同的网络设备，适应的，在该切换流程中，可以将压缩端初始通信的解压端称为源站，将压缩端将要切换进行通信的解压端称为目标站，源站可以通过切换请求消息(handover request，HR) 将源站中部分或所有DRB的对应关系递交到目标站。进一步的，目标站可以为压缩端的部分或所有DRB配置EHC保持(continue)，此时压缩端不需要清空相应DRB的对应关系，可以继续利用原有的对应关系执行EHC操作，从而可以减少压缩端生成对应关系的次数，减少对计算资源的占用；目标站也可以为压缩端的部分或所有DRB不配置EHC continue，此时，压缩端可以清空相应DRB的对应关系，从而可以降低对存储空间的占用。
在本申请实施例的一种可选实现方式中，可能存在压缩端和解压端进行重建立的场景，当压缩端和解压端进行重建立时，压缩端中保存的对应关系和解压端中保存的对应关系可以保持不变，使得压缩端和解压端可以在重建后继续使用原有的对应关系执行EHC操作，从而可以减少压缩端生成对应关系的次数，减少对计算资源的占用。当压缩端和解压端进行重建立时，压缩端中保存的对应关系和解压端中保存的对应关系也可以清空，从而可以降低对存储空间的占用。
本申请实施例还提供用于实现以上任一种方法的装置，例如，提供一种装置包括用以实现以上任一种方法中终端装置所执行的各个步骤的单元(或手段)。再如，还提供另一种装置，包括用以实现以上任一种方法中接入网设备所执行的各个步骤的单元(或手段)。再如，还提供另一种装置，包括用以实现以上任一种方法中核心网设备所执行的各个步骤的单元(或手段)。
例如，请参考图25，其为本申请实施例提供的一种以太帧头的压缩装置的示意图。该装置用于压缩端，如图25所示，该装置2500包括接收单元2510，确定单元2520，和压缩单元2530。其中接收单元2510用于接收第一以太帧，第一以太帧的以太帧头包括第一待压缩字段，确定单元2520用于根据第一对应关系和第一待压缩字段确定第一以太帧的以太帧头的第一压缩信息，第一对应关系包括第一压缩信息和第一待压缩字段的取值的对应关系，第一压缩信息包括第一上下文标识CID，压缩单元2530用于根据第一压缩信息压缩第一以太帧的以太帧头。
可选的，该装置1700还可以包括第一关系生成单元，用于当压缩端存储的对应关系不包括第一以太帧的第一待压缩字段的取值时，生成第一对应关系，压缩端存储的对应关系包括至少一个压缩信息和待压缩字段的取值的对应关系。
可选的，还包括发送单元，用于向解压端发送第一对应关系。
可选的，发送单元具体用于向解压端发送非压缩数据包，非压缩数据包包括第一对应关系。
可选的，发送单元具体还用于通过第一分组数据汇聚协议数据协议数据单元PDCP data PDU向解压端发送第一对应关系；其中，第一PDCP data PDU包括：第一以太帧头压缩EHC头，第一EHC头包括第一指示字段、第一CID和第二以太帧的以太帧头；第二以太帧的以太帧头的待压缩字段的取值等于所述第一待压缩字段的取值；第一指示字段用于指示第一EHC头中是否包括有完整的以太帧头。
可选的，第一EHC头还包括第一配置文件标识profile ID。
可选的，第一指示字段还用于指示第一EHC头包括第一profile ID。
可选的，第一PDCP data PDU还包括：PDCP头、服务数据适配层SDAP头、以太数据载荷和完整性消息认证码MAC-I。
可选的，发送单元具体还用于通过分组数据汇聚协议控制协议数据单元PDCP  control PDU向解压端发送第一对应关系；其中，PDCP control PDU包括第一指示信息、第一CID和第一待压缩字段的取值；第一指示信息用于指示PDCP control PDU用于传输第一对应关系。
可选的，PDCP control PDU还包括：profile ID。
可选的，发送单元具体还用于向解压端发送第一PDCP data PDU；其中，第一PDCP data PDU包括：第一EHC头，第一EHC头包括第一指示字段、和第二以太帧的以太帧头，二以太帧的以太帧头的待压缩字段的取值等于所述第一待压缩字段的取值；第一指示字段用于指示第一EHC头中是否携带第一CID。
可选的，当第一EHC头携带第一CID时，第二以太帧的以太帧头为压缩的以太帧头，或者，当第一EHC头未携带第一CID时，第二以太帧的以太帧头为完整的以太帧头。
可选的，第一PDCP data PDU还包括：PDCP头、服务数据适配层SDAP头、以太数据载荷和完整性消息认证码MAC-I。
可选的，发送单元具体还用于向解压端多次发送第一对应关系。
可选的，接收单元还用于从解压端接收反馈信息，反馈信息用于指示第一对应关系的接收状态。
反馈信息包括第一CID。
可选的，反馈信息还包括以下至少一项：第一profile ID、第二指示字段、第三指示字段，第二指示字段用于指示第一对应关系在解压端为新增的对应关系或修改的对应关系，第三指示字段用于指示反馈信息为肯定反馈或否定反馈。
可选的，压缩端还存储有对应关系的指示变量，指示变量用于指示对应关系的压缩信息是否用于压缩。
可选的，发送单元还用于当压缩端存储的对应关系包括第一待压缩字段对应的第一对应关系，且第一对应关系的指示变量指示第一对应关系的压缩信息不用于压缩时，压缩端向解压缩端发送第一对应关系。
可选的，还包括变量设置单元，用于在压缩端确认第一对应关系被解压端正确接收时，压缩端将指示变量设置为第一值，第一值用于指示压缩信息用于压缩。
可选的，第一压缩信息还包括第一profile ID。
可选的，发送单元还用于向解压端发送第二指示信息，第二指示信息用于指示第一对应关系在压缩端为新增的对应关系或修改的对应关系。
可选的，发送单元还用于向解压端发送压缩后的第一以太帧，压缩后的第一以太帧包括第一CID，且不包括配置文件标识profile ID。
可选的，发送单元还用于向解压端发送压缩后的第一以太帧包括：压缩端通过第二PDCP data PDU向解压端发送压缩后的第一以太帧。
可选的，第二PDCP data PDU包括第二EHC头，第二EHC头还包括：校验信息。
可选的，校验信息为根据第一对应关系中的一个或多个信息生成的。
可选的，还包括设置单元，用于在压缩端接收到解压端根据校验信息返回的错误报告的情况下，压缩端删除第一对应关系，或压缩端将第一对应关系设置为不可用。
可选的，压缩端为终端，解压缩端为网络设备，发送单元还用于向解压端发送能 力信息；能力信息包括下述至少一项：压缩端支持EHC的能力，压缩端中支持EHC的数据无线承载DRB的个数，压缩端支持的配置文件profile信息，每个支持EHC的DRB所支持的对应关系数量的最大值MAX_CID，压缩端支持动态配置profile参数的能力，压缩端支持EHC的DRB所维护的对应关系数量的总和。
可选的，接收单元还用于接收配置信息，配置信息用于指示EHC头是否携带profile ID；或者，配置信息包括profile ID。
可选的，压缩端为网络设备或终端，接收单元还用于接收能力信息，能力信息包括下述至少一项：能力信息包括下述至少一项：压缩端支持EHC的能力，压缩端中支持EHC的数据无线承载DRB的个数，压缩端支持的配置文件profile信息，每个支持EHC的DRB所支持的对应关系数量的最大值MAX_CID，压缩端支持动态配置profile参数的能力，压缩端支持EHC的DRB所维护的对应关系数量的总和。
可选的，发送单元还用于向解压端发送配置信息，配置信息还用于指示EHC头是否携带profile ID；或者，配置信息包括profile ID。
具体实现方式参照方法实施例的记载，在此不再赘述。
例如，请参考图26，其为本申请实施例提供的一种以太帧头的解压装置的示意图。该装置用于解压端，如图26所示，该装置2600包括接收单元2610，确定单元2620和解压单元2630。其中接收单元2610用于接收第一以太帧，第一上下文标识CID；确定单元2620用于根据第一CID确定包括第一CID的第一对应关系，第一对应关系包括第一压缩信息和第一待解压字段的取值的对应关系，第一压缩信息包括第一CID；解压单元2630用于根据第一对应关系中的第一压缩信息和第一待解压字段的取值解压第一以太帧的以太帧头。
可选的，接收单元还用于从压缩端接收第一对应关系。
可选的，接收单元具体用于接收非压缩数据包，非压缩数据包包括第一对应关系。
可选的，接收单元还用于通过PDCP data PDU从压缩端接收第一对应关系；其中，第一PDCP data PDU包括：第一以太帧头压缩EHC头，第一EHC头包括第一指示字段、第一CID和第二以太帧的以太帧头，第二以太帧的以太帧头的待压缩字段的取值等于第一待压缩字段的取值；第一指示字段用于指示第一EHC头中是否包括有完整的以太帧头。
可选的，第一EHC头还包括第一配置文件标识profile ID。
可选的，第一指示字段还用于指示第一EHC头包括第一profile ID。
可选的，第一PDCP data PDU还包括：PDCP头、服务数据适配层SDAP头、以太数据载荷和完整性消息认证码MAC-I。
可选的，接收单元还用于接收压缩端通过PDCP control PDU发送的第一对应关系；其中，PDCP control PDU包括第一指示信息、CID和第一待压缩字段取值；第一指示信息用于指示PDCP control PDU用于传输第一对应关系。
可选的，PDCP control PDU还包括：第一profile ID。
可选的，接收单元还用于从压缩端接收第一PDCP data PDU；其中，第一PDCP data PDU包括：第一EHC头，第一EHC头包括第一指示字段、和第二以太帧的以太帧头，第二以太帧的以太帧头的待压缩字段的取值等于第一待压缩字段的取值；第一指示字 段用于指示第一EHC头中是否携带第一CID。
可选的，当第一EHC头携带第一CID时，第二以太帧的以太帧头为压缩的以太帧头，或者，当第一EHC头未携带第一CID时，第二以太帧的以太帧头为完整的以太帧头。
可选的，第一PDCP data PDU还包括：PDCP头、服务数据适配层SDAP头、以太数据载荷和完整性消息认证码MAC-I。
可选的，解压端存储有至少一个压缩信息和待解压字段的取值的对应关系，还包括第一对应关系设置单元，用于当解压端存储的对应关系不包括第一压缩信息时，解压端存储第一对应关系；或者，当解压端存储的对应关系包括第一压缩信息时，且第一压缩信息对应待解压字段的取值与第一待解压字段的取值不同，解压端将第一压缩信息对应待解压字段的取值修改为第一待解压字段的取值。
可选的，还包括发送单元，用于向压缩端发送反馈信息，反馈信息用于指示第一对应关系的接收状态。
可选的，反馈信息包括第一CID。
可选的，反馈信息还包括以下至少一项：profile ID、第一指示字段、第二指示字段，第一指示字段用于指示第一对应关系在解压端为新增的对应关系或修改的对应关系，第二指示字段用于指示反馈信息为肯定反馈或否定反馈。
可选的，第一以太帧还包括：第一校验信息。
可选的，第一校验信息为根据第一对应关系中的一个或多个信息生成的。
可选的，还包括校验单元，用于根据第一对应关系中的一个或多个信息生成第二校验信息；在第一校验信息与第二校验信息相同的情况下，解压端解压第一以太帧的以太帧头；或，在第一校验信息与第二校验信息不同的情况下，解压端删除第一对应关系；和/或，解压端向压缩端发送错误报告。
应理解以上装置中单元的划分仅仅是一种逻辑功能的划分，实际实现时可以全部或部分集成到一个物理实体上，也可以物理上分开。且装置中的单元可以全部以软件通过处理元件调用的形式实现；也可以全部以硬件的形式实现；还可以部分单元以软件通过处理元件调用的形式实现，部分单元以硬件的形式实现。例如，各个单元可以为单独设立的处理元件，也可以集成在装置的某一个芯片中实现，此外，也可以以程序的形式存储于存储器中，由装置的某一个处理元件调用并执行该单元的功能。此外这些单元全部或部分可以集成在一起，也可以独立实现。这里的处理元件又可以称为处理器，可以是一种具有信号的处理能力的集成电路。在实现过程中，上述方法的各步骤或以上各个单元可以通过处理器元件中的硬件的集成逻辑电路实现或者以软件通过处理元件调用的形式实现。
在一个例子中，以上任一装置中的单元可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个特定集成电路(Application Specific Integrated Circuit，ASIC)，或，一个或多个微处理器(digital singnal processor，DSP)，或，一个或者多个现场可编程门阵列(Field Programmable Gate Array，FPGA)，或这些集成电路形式中至少两种的组合。再如，当装置中的单元可以通过处理元件调度程序的形式实现时，该处理元件可以是通用处理器，例如中央处理器(Central Processing Unit，CPU) 或其它可以调用程序的处理器。再如，这些单元可以集成在一起，以片上系统(system-on-a-chip，SOC)的形式实现。
以上用于接收的单元(例如接收单元或通信单元)是一种该装置的接口电路，用于从其它装置接收信号。例如，当该装置以芯片的方式实现时，该接收单元是该芯片用于从其它芯片或装置接收信号的接口电路。以上用于发送的单元(例如发送单元或通信单元)是一种该装置的接口电路，用于向其它装置发送信号。例如，当该装置以芯片的方式实现时，该发送单元是该芯片用于向其它芯片或装置发送信号的接口电路。
请参考图27，其为本申请实施例提供的一种网络设备的结构示意图。该网络设备用于实现以上实施例中网络设备的操作。如图27所示，该网络设备包括：天线2710、射频装置2720、基带装置2730。天线2710与射频装置2720连接。在上行方向上，射频装置2720通过天线2710接收终端装置发送的信息，将终端装置发送的信息发送给基带装置2730进行处理。在下行方向上，基带装置2730对终端装置的信息进行处理，并发送给射频装置2720，射频装置2720对终端装置的信息进行处理后经过天线2710发送给终端装置。
基带装置2730可以包括一个或多个处理元件2731，例如，包括一个主控CPU和其它集成电路。此外，该基带装置2730还可以包括存储元件2732和接口2733，存储元件2732用于存储程序和数据；接口2733用于与射频装置2720交互信息，该接口例如为通用公共无线接口(common public radio interface，CPRI)。以上用于网络设备的装置可以位于基带装置2730，例如，以上用于网络设备的装置可以为基带装置2730上的芯片，该芯片包括至少一个处理元件和接口电路，其中处理元件用于执行以上网络设备执行的任一种方法的各个步骤，接口电路用于与其它装置通信。在一种实现中，网络设备实现以上方法中各个步骤的单元可以通过处理元件调度程序的形式实现，例如用于网络设备的装置包括处理元件和存储元件，处理元件调用存储元件存储的程序，以执行以上方法实施例中网络设备执行的方法。存储元件可以为处理元件处于同一芯片上的存储元件，即片内存储元件，也可以为与处理元件处于不同芯片上的存储元件，即片外存储元件。
在另一种实现中，网络设备实现以上方法中各个步骤的单元可以是被配置成一个或多个处理元件，这些处理元件设置于基带装置上，这里的处理元件可以为集成电路，例如：一个或多个ASIC，或，一个或多个DSP，或，一个或者多个FPGA，或者这些类集成电路的组合。这些集成电路可以集成在一起，构成芯片。
网络设备实现以上方法中各个步骤的单元可以集成在一起，以片上系统(system-on-a-chip，SOC)的形式实现，例如，基带装置包括该SOC芯片，用于实现以上方法。该芯片内可以集成至少一个处理元件和存储元件，由处理元件调用存储元件的存储的程序的形式实现以上网络设备执行的方法；或者，该芯片内可以集成至少一个集成电路，用于实现以上网络设备执行的方法；或者，可以结合以上实现方式，部分单元的功能通过处理元件调用程序的形式实现，部分单元的功能通过集成电路的形式实现。
可见，以上用于网络设备的装置可以包括至少一个处理元件和接口电路，其中至少一个处理元件用于执行以上方法实施例所提供的任一种网络设备执行的方法。处理 元件可以以第一种方式：即调用存储元件存储的程序的方式执行网络设备执行的部分或全部步骤；也可以以第二种方式：即通过处理器元件中的硬件的集成逻辑电路结合指令的方式执行网络设备执行的部分或全部步骤；当然，也可以结合第一种方式和第二种方式执行以上网络设备执行的部分或全部步骤。
这里的处理元件同以上描述，可以是通用处理器，例如CPU，还可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个ASIC，或，一个或多个微处理器DSP，或，一个或者多个FPGA等，或这些集成电路形式中至少两种的组合。存储元件可以是一个存储器，也可以是多个存储元件的统称。
请参考图28，其为本申请实施例提供的一种终端装置的结构示意图。该终端装置用于实现以上实施例中终端的操作。如图28所示，该终端装置包括：天线2810、射频部分2828、信号处理部分2830。天线2810与射频部分2828连接。在下行方向上，射频部分2828通过天线2810接收接入网设备发送的信息，将接入网设备发送的信息发送给信号处理部分2830进行处理。在上行方向上，信号处理部分2830对终端装置的信息进行处理，并发送给射频部分2828，射频部分2828对终端装置的信息进行处理后经过天线2810发送给接入网设备。
信号处理部分2830用于实现对数据各通信协议层的处理。信号处理部分2830可以为该终端装置的一个子系统，则该终端装置还可以包括其它子系统，例如中央处理子系统，用于实现对终端装置操作系统以及应用层的处理；再如，周边子系统用于实现与其它设备的连接。信号处理部分2830可以为单独设置的芯片。可选的，以上的装置可以位于信号处理部分2830。
信号处理部分2830可以包括一个或多个处理元件2831，例如，包括一个主控CPU和其它集成电路。此外，该信号处理部分2830还可以包括存储元件2832和接口电路2833。存储元件2832用于存储数据和程序，用于执行以上方法中终端装置所执行的方法的程序可能存储，也可能不存储于该存储元件2832中，例如，存储于信号处理部分2830之外的存储器中，使用时信号处理部分2830加载该程序到缓存中进行使用。接口电路2833用于与装置通信。以上装置可以位于信号处理部分2830，该信号处理部分2830可以通过芯片实现，该芯片包括至少一个处理元件和接口电路，其中处理元件用于执行以上终端装置执行的任一种方法的各个步骤，接口电路用于与其它装置通信。在一种实现中，实现以上方法中各个步骤的单元可以通过处理元件调度程序的形式实现，例如该装置包括处理元件和存储元件，处理元件调用存储元件存储的程序，以执行以上方法实施例中终端装置执行的方法。存储元件可以为处理元件处于同一芯片上的存储元件，即片内存储元件。
在另一种实现中，用于执行以上方法中终端装置所执行的方法的程序可以在与处理元件处于不同芯片上的存储元件，即片外存储元件。此时，处理元件从片外存储元件调用或加载程序于片内存储元件上，以调用并执行以上方法实施例中终端装置执行的方法。
在又一种实现中，终端装置实现以上方法中各个步骤的单元可以是被配置成一个或多个处理元件，这些处理元件设置于信号处理部分2830上，这里的处理元件可以为集成电路，例如：一个或多个ASIC，或，一个或多个DSP，或，一个或者多个FPGA， 或者这些类集成电路的组合。这些集成电路可以集成在一起，构成芯片。
实现以上方法中各个步骤的单元可以集成在一起，以片上系统(system-on-a-chip，SOC)的形式实现，该SOC芯片，用于实现以上方法。该芯片内可以集成至少一个处理元件和存储元件，由处理元件调用存储元件的存储的程序的形式实现以上终端装置执行的方法；或者，该芯片内可以集成至少一个集成电路，用于实现以上终端装置执行的方法；或者，可以结合以上实现方式，部分单元的功能通过处理元件调用程序的形式实现，部分单元的功能通过集成电路的形式实现。
可见，以上装置可以包括至少一个处理元件和接口电路，其中至少一个处理元件用于执行以上方法实施例所提供的任一种终端装置执行的方法。处理元件可以以第一种方式：即调用存储元件存储的程序的方式执行终端装置执行的部分或全部步骤；也可以以第二种方式：即通过处理器元件中的硬件的集成逻辑电路结合指令的方式执行终端装置执行的部分或全部步骤；当然，也可以结合第一种方式和第二种方式执行终端装置执行的部分或全部步骤。
这里的处理元件同以上描述，可以是通用处理器，例如CPU，还可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个ASIC，或，一个或多个微处理器DSP，或，一个或者多个FPGA等，或这些集成电路形式中至少两种的组合。存储元件可以是一个存储器，也可以是多个存储元件的统称。
请参考图29，其为本申请实施例提供的一种压缩端设备的结构示意图，用于实现以上实施例中压缩端的操作。如图29所示，该压缩端设备包括：处理器2910，存储器2920，和接口2930，处理器2910、存储器2920和接口2930信号连接。
以上实施例中压缩端设备执行的方法可以通过处理器2910调用存储器2920中存储的程序来实现。即，用于压缩端设备的装置包括存储器和处理器，存储器用于存储程序，该程序被处理器调用，以执行以上方法实施例中的压缩端设备执行的方法。这里的处理器可以是一种具有信号的处理能力的集成电路，例如CPU。用于压缩端设备的装置可以通过配置成实施以上方法的一个或多个集成电路来实现。例如：一个或多个ASIC，或，一个或多个微处理器DSP，或，一个或者多个FPGA等，或这些集成电路形式中至少两种的组合。或者，可以结合以上实现方式。
请参考图30，其为本申请实施例提供的一种解压端设备的结构示意图，用于实现以上实施例中解压端的操作。如图30所示，该解压端设备包括：处理器3010，存储器3020，和接口3030，处理器3010、存储器3020和接口3030信号连接。
以上实施例中解压端设备执行的方法可以通过处理器3010调用存储器3020中存储的程序来实现。即，用于解压端设备的装置包括存储器和处理器，存储器用于存储程序，该程序被处理器调用，以执行以上方法实施例中的解压端设备执行的方法。这里的处理器可以是一种具有信号的处理能力的集成电路，例如CPU。用于解压端设备的装置可以通过配置成实施以上方法的一个或多个集成电路来实现。例如：一个或多个ASIC，或，一个或多个微处理器DSP，或，一个或者多个FPGA等，或这些集成电路形式中至少两种的组合。或者，可以结合以上实现方式。
本领域普通技术人员可以理解：实现上述方法实施例的全部或部分步骤可以通过程序指令相关的硬件来完成，前述的程序可以存储于一计算机可读取存储介质中，该 程序在执行时，执行包括上述方法实施例的步骤；而前述的存储介质包括：ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。

Claims (76)

  1. 一种以太帧头的压缩方法，其特征在于，包括：
    压缩端接收第一以太帧，所述第一以太帧的以太帧头包括第一待压缩字段；
    所述压缩端根据第一对应关系和所述第一待压缩字段确定所述第一以太帧的以太帧头的第一压缩信息，所述第一对应关系包括所述第一压缩信息和所述第一待压缩字段的取值的对应关系，所述第一压缩信息包括第一上下文标识CID；
    所述压缩端根据所述第一压缩信息压缩所述第一以太帧的以太帧头。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    当所述压缩端存储的对应关系不包括所述第一以太帧的第一待压缩字段的取值时，生成所述第一对应关系，所述压缩端存储的对应关系包括至少一个压缩信息和待压缩字段的取值的对应关系。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述压缩端向解压端发送所述第一对应关系。
  4. 根据权利要求3所述的方法，其特征在于，所述压缩端向解压端发送所述第一对应关系包括：
    所述压缩端向解压端发送非压缩数据包，所述非压缩数据包包括所述第一对应关系。
  5. 根据权利要求3或4所述的方法，所述压缩端向解压端发送所述第一对应关系，包括：
    所述压缩端通过第一分组数据汇聚协议数据协议数据单元PDCP data PDU向所述解压端发送所述第一对应关系；其中，所述第一PDCP data PDU包括：第一以太帧头压缩EHC头，所述第一EHC头包括第一指示字段、所述第一CID和第二以太帧的以太帧头，所述第二以太帧的以太帧头的待压缩字段的取值等于所述第一待压缩字段的取值；所述第一指示字段用于指示所述第一EHC头中是否包括有完整的以太帧头。
  6. 根据权利要求5所述的方法，其特征在于，所述第一EHC头还包括第一配置文件标识profile ID。
  7. 根据权利要求6所述的方法，其特征在于，所述第一指示字段还用于指示所述第一EHC头包括所述第一profile ID。
  8. 根据权利要求5-7任一项所述的方法，其特征在于，所述第一PDCP data PDU还包括：PDCP头、服务数据适配层SDAP头、以太数据载荷和完整性消息认证码MAC-I。
  9. 根据权利要求3或4所述的方法，其特征在于，所述压缩端向解压端发送所述第一对应关系，包括：
    所述压缩端通过分组数据汇聚协议控制协议数据单元PDCP control PDU向所述解压端发送所述第一对应关系；其中，所述PDCP control PDU包括第一指示信息、所述第一CID和所述第一待压缩字段的取值；所述第一指示信息用于指示所述PDCP control PDU用于传输所述第一对应关系。
  10. 根据权利要求9所述的方法，其特征在于，所述PDCP control PDU还包括第一profile ID。
  11. 根据权利要求9或10所述的方法，其特征在于，还包括：
    所述压缩端向所述解压端发送第一PDCP data PDU；其中，所述第一PDCP data PDU包括：第一EHC头，所述第一EHC头包括第一指示字段、和第二以太帧的以太帧头，所述第二以太帧的以太帧头的待压缩字段的取值等于所述第一待压缩字段的取值；所述第一指示字段用于指示所述第一EHC头中是否携带所述第一CID。
  12. 根据权利要求11所述的方法，其特征在于，当所述第一EHC头携带所述第一CID时，所述第二以太帧的以太帧头为压缩的以太帧头，或者，当所述第一EHC头未携带所述第一CID时，所述第二以太帧的以太帧头为完整的以太帧头。
  13. 根据权利要求9-12任一项所述的方法，其特征在于，所述第一PDCP data PDU还包括：PDCP头、服务数据适配层SDAP头、以太数据载荷和完整性消息认证码MAC-I。
  14. 根据权利要求3-13任一项所述的方法，其特征在于，所述压缩端向解压端发送所述第一对应关系包括：
    所述压缩端向所述解压端多次发送所述第一对应关系。
  15. 根据权利要求3-13任一项所述的方法，其特征在于，还包括：
    所述压缩端从所述解压端接收反馈信息，所述反馈信息用于指示所述第一对应关系的接收状态。
  16. 根据权利要求15所述的方法，其特征在于，所述反馈信息包括所述第一CID。
  17. 根据权利要求16所述的方法，其特征在于，所述反馈信息还包括以下至少一项：第一profile ID、第二指示字段、第三指示字段，所述第二指示字段用于指示所述第一对应关系在所述解压端为新增的对应关系或修改的对应关系，所述第三指示字段用于指示所述反馈信息为肯定反馈或否定反馈。
  18. 根据权利要求2-17任一项所述的方法，其特征在于，所述压缩端还存储有所述对应关系的指示变量，所述指示变量用于指示所述对应关系的压缩信息是否用于压缩。
  19. 根据权利要求1所述的方法，其特征在于，还包括：
    当所述压缩端存储的对应关系包括所述第一待压缩字段对应的第一对应关系，且所述第一对应关系的指示变量指示所述第一对应关系的压缩信息不用于压缩时，所述压缩端向所述解压缩端发送所述第一对应关系。
  20. 根据权利要求18或19所述的方法，其特征在于，所述方法还包括：
    在所述压缩端确认所述第一对应关系被所述解压端正确接收时，所述压缩端将所述指示变量设置为第一值，所述第一值用于指示所述压缩信息用于压缩。
  21. 根据权利要求1-20任一项所述的方法，其特征在于，所述第一压缩信息还包括第一profile ID。
  22. 根据权利要求1-21任一项所述的方法，其特征在于，还包括：
    所述压缩端向解压端发送第二指示信息，所述第二指示信息用于指示所述第一对应关系在所述压缩端为新增的对应关系或修改的对应关系。
  23. 根据权利要求1-22任一项所述的方法，其特征在于，还包括：
    所述压缩端向解压端发送压缩后的第一以太帧，所述压缩后的第一以太帧包括所述第一CID，且不包括配置文件标识profile ID。
  24. 根据权利要求23所述的方法，其特征在于，所述压缩端向解压端发送压缩后 的第一以太帧包括：
    所述压缩端通过第二PDCP data PDU向解压端发送压缩后的第一以太帧。
  25. 根据权利要求24所述的方法，其特征在于，所述第二PDCP data PDU包括第二EHC头，所述第二EHC头还包括：校验信息。
  26. 根据权利要求25所述的方法，其特征在于，所述校验信息为根据所述第一对应关系中的一个或多个信息生成的。
  27. 根据权利要求25-26任一项所述的方法，其特征在于，在所述压缩端接收到所述解压端根据所述校验信息返回的错误报告的情况下，所述压缩端删除所述第一对应关系，或所述压缩端将所述第一对应关系设置为不可用。
  28. 根据权利要求1-27所述的方法，其特征在于，所述压缩端为终端，所述解压缩端为网络设备，所述方法还包括：
    所述压缩端向所述解压端发送能力信息；所述能力信息包括下述至少一项：所述压缩端支持EHC的能力，所述压缩端中支持EHC的数据无线承载DRB的个数，所述压缩端支持的配置文件profile信息，每个支持EHC的DRB所支持的对应关系数量的最大值MAX_CID，所述压缩端支持动态配置profile参数的能力，所述压缩端支持EHC的DRB所维护的对应关系数量的总和。
  29. 根据权利要求1-27任一项所述的方法，其特征在于，所述压缩端为终端，所述方法还包括：
    所述终端接收配置信息，所述配置信息用于指示EHC头是否携带profile ID；或者，所述配置信息包括profile ID。
  30. 根据权利要求1-27任一项所述的方法，其特征在于，所述压缩端为网络设备或终端，所述方法还包括：
    所述压缩端接收能力信息，所述能力信息包括下述至少一项：所述能力信息包括下述至少一项：所述压缩端支持EHC的能力，所述压缩端中支持EHC的数据无线承载DRB的个数，所述压缩端支持的配置文件profile信息，每个支持EHC的DRB所支持的对应关系数量的最大值MAX_CID，所述压缩端支持动态配置profile参数的能力，所述压缩端支持EHC的DRB所维护的对应关系数量的总和。
  31. 根据权利要求30所述的方法，其特征在于，所述解压端为终端，所述压缩端为网络设备，所述方法还包括：
    所述网络设备向所述解压端发送配置信息，所述配置信息用于指示EHC头是否携带profile ID；或者，所述配置信息包括profile ID。
  32. 一种以太帧头的解压方法，其特征在于，包括：
    解压端接收第一以太帧，所述第一以太帧包括第一上下文标识CID；
    所述解压端根据所述第一CID确定包括所述第一CID的第一对应关系，所述第一对应关系包括第一压缩信息和第一待解压字段的取值的对应关系，所述第一压缩信息包括所述第一CID；
    所述解压端根据所述第一对应关系中的所述第一压缩信息和所述第一待解压字段的取值解压所述第一以太帧的以太帧头。
  33. 根据权利要求32所述的方法，其特征在于，还包括：
    所述解压端从压缩端接收所述第一对应关系。
  34. 根据权利要求33所述的方法，其特征在于，所述解压端从压缩端接收所述第一对应关系，包括：
    所述解压端接收非压缩数据包，所述非压缩数据包包括所述第一对应关系。
  35. 根据权利要求33或34所述的方法，其特征在于，所述解压端从压缩端接收所述第一对应关系，包括：
    所述解压端通过PDCP data PDU从所述压缩端接收所述第一对应关系；其中，所述第一PDCP data PDU包括：第一以太帧头压缩EHC头，所述第一EHC头包括第一指示字段、所述第一CID和第二以太帧的以太帧头，所述第二以太帧的以太帧头的待压缩字段的取值等于所述第一待压缩字段的取值；所述第一指示字段用于指示所述第一EHC头中是否包括有完整的以太帧头。
  36. 根据权利要求35所述的方法，其特征在于，所述第一EHC头还包括第一配置文件标识profile ID。
  37. 根据权利要求36所述的方法，其特征在于，所述第一指示字段还用于指示所述第一EHC头包括所述第一profile ID。
  38. 根据权利要求35-37任一项所述的方法，其特征在于，所述第一PDCP data PDU还包括：PDCP头、服务数据适配层SDAP头、以太数据载荷和完整性消息认证码MAC-I。
  39. 根据权利要求33或34所述的方法，其特征在于，所述解压端从压缩端接收所述第一对应关系，包括：
    所述解压端通过PDCP control PDU从所述压缩端接收所述第一对应关系；其中，所述PDCP control PDU包括第一指示信息、所述第一CID和所述第一待压缩字段的取值；所述第一指示信息用于指示所述PDCP control PDU用于传输所述第一对应关系。
  40. 根据权利要求39所述的方法，其特征在于，所述PDCP control PDU还包括第一profile ID。
  41. 根据权利要求39或40所述的方法，其特征在于，还包括：
    所述解压端从所述压缩端接收第一PDCP data PDU；其中，所述第一PDCP data PDU包括：第一EHC头，所述第一EHC头包括第一指示字段、和第二以太帧的以太帧头，所述第二以太帧的以太帧头的待压缩字段的取值等于所述第一待压缩字段的取值；所述第一指示字段用于指示所述第一EHC头中是否携带所述第一CID。
  42. 根据权利要求41所述的方法，其特征在于，当所述第一EHC头携带所述第一CID时，所述第二以太帧的以太帧头为压缩的以太帧头，或者，当所述第一EHC头未携带所述第一CID时，所述第二以太帧的以太帧头为完整的以太帧头。
  43. 根据权利要求39-42任一项所述的方法，其特征在于，所述第一PDCP data PDU还包括：PDCP头、服务数据适配层SDAP头、以太数据载荷和完整性消息认证码MAC-I。
  44. 根据权利要求33-43任一项所述的方法，其特征在于，所解压端存储有至少一个压缩信息和待解压字段的取值的对应关系，所述方法还包括：
    当所述解压端存储的对应关系不包括所述第一压缩信息时，所述解压端存储所述第一对应关系；或者，
    当所述解压端存储的对应关系包括所述第一压缩信息时，且所述第一压缩信息对 应待解压字段的取值与所述第一待解压字段的取值不同，所述解压端将所述第一压缩信息对应待解压字段的取值修改为所述第一待解压字段的取值。
  45. 根据权利要求33-44任一项所述的方法，其特征在于，还包括：
    所述解压端向所述压缩端发送反馈信息，所述反馈信息用于指示所述第一对应关系的接收状态。
  46. 根据权利要求45所述的方法，其特征在于，所述反馈信息包括所述第一CID。
  47. 根据权利要求46所述的方法，其特征在于，所述反馈信息还包括以下至少一项：profile ID、第一指示字段、第二指示字段，所述第一指示字段用于指示所述第一对应关系在所述解压端为新增的对应关系或修改的对应关系，所述第二指示字段用于指示所述反馈信息为肯定反馈或否定反馈。
  48. 根据权利要求32-47任一项所述的方法，其特征在于，所述第一以太帧还包括：第一校验信息。
  49. 根据权利要求48所述的方法，其特征在于，所述第一校验信息为根据所述第一对应关系中的一个或多个信息生成的。
  50. 根据权利要求48-49任一项所述的方法，其特征在于，还包括：
    所述压缩端根据所述第一对应关系中的一个或多个信息生成第二校验信息；
    在所述第一校验信息与所述第二校验信息相同的情况下，所述解压端解压所述第一以太帧的以太帧头；或，
    在所述第一校验信息与所述第二校验信息不同的情况下，所述解压端删除所述第一对应关系；和/或，所述解压端向所述压缩端发送错误报告。
  51. 一种以太帧头的压缩方法，其特征在于，包括：
    压缩端向解压端发送数据包，所述数据包包括压缩信息和待压缩字段取值的对应关系，所述压缩信息包括上下文标识CID；
    压缩端利用所述对应关系的压缩信息，压缩第一以太帧，所述第一以太帧的以太帧头包括的待压缩字段的取值为所述对应关系中的待压缩字段取值。
  52. 根据权利要求51所述的方法，其特征在于，所述数据包为分组数据汇聚协议数据协议数据单元PDCP data PDU。
  53. 根据权利要求52所述的方法，其特征在于，所述EHC头包括指示字段、所述CID和第二以太帧的以太帧头，所述第二以太帧的以太帧头的待压缩字段的取值等于所述对应关系中的待压缩字段取值；所述指示字段用于指示所述EHC头中是否包括有完整的以太帧头。
  54. 根据权利要求53所述的方法，其特征在于，所述EHC头还包括配置文件标识profile ID。
  55. 根据权利要求54所述的方法，其特征在于，所述指示字段还用于指示所述EHC头包括所述profile ID。
  56. 根据权利要求51所述的方法，其特征在于，所述数据包为分组数据汇聚协议控制协议数据单元PDCP control PDU。
  57. 根据权利要求56所述的方法，其特征在于，所述EHC头包括指示信息、所述CID和所述第一待压缩字段的取值；所述第一指示信息用于指示所述PDCP control  PDU用于传输所述对应关系。
  58. 根据权利要求57所述的方法，其特征在于，所述PDCP control PDU还包括所述profile ID。
  59. 根据权利要求57或58所述的方法，其特征在于，还包括：
    所述压缩端向解压端发送PDCP data PDU；其中，所述PDCP data PDU包括EHC头，所述EHC头包括指示字段和第二以太帧的以太帧头，所述第二以太帧的以太帧头的待压缩字段的取值等于所述对应关系中的待压缩字段取值；所述指示字段用于指示所述EHC头中是否携带所述CID。
  60. 一种以太帧头的解压缩方法，其特征在于，包括：
    解压端从压缩端接收数据包，所述数据包包括压缩信息和待解压字段取值的对应关系，所述压缩信息包括上下文标识CID；
    解压端利用所述对应关系的压缩信息和待解压字段取值，解压第一以太帧，所述第一以太帧的以太帧头包括所述对应关系中的CID。
  61. 根据权利要求60所述的方法，其特征在于，所述数据包为分组数据汇聚协议数据协议数据单元PDCP data PDU。
  62. 根据权利要求61所述的方法，其特征在于，所述EHC头包括指示字段、所述CID和第二以太帧的以太帧头，所述第二以太帧的以太帧头的待压缩字段的取值等于所述对应关系中的待压缩字段取值；所述指示字段用于指示所述EHC头中是否包括有完整的以太帧头。
  63. 根据权利要求62所述的方法，其特征在于，所述EHC头还包括配置文件标识profile ID。
  64. 根据权利要求63所述的方法，其特征在于，所述指示字段还用于指示所述EHC头包括所述profile ID。
  65. 根据权利要求60所述的方法，其特征在于，所述数据包为分组数据汇聚协议控制协议数据单元PDCP control PDU。
  66. 根据权利要求65所述的方法，其特征在于，所述EHC头包括指示信息、所述CID和所述第一待压缩字段的取值；所述第一指示信息用于指示所述PDCP control PDU用于传输所述对应关系。
  67. 根据权利要求66所述的方法，其特征在于，所述PDCP control PDU还包括所述profile ID。
  68. 根据权利要求66或67所述的方法，其特征在于，还包括：
    所述压缩端向解压端发送PDCP data PDU；其中，所述PDCP data PDU包括EHC头，所述EHC头包括指示字段和第二以太帧的以太帧头，所述第二以太帧的以太帧头的待压缩字段的取值等于所述对应关系中的待压缩字段取值；所述指示字段用于指示所述EHC头中是否携带所述CID。
  69. 一种压缩装置，其特征在于，包括：用于执行权利要求1至31，或，51至59任一项所述的各个步骤的单元。
  70. 一种压缩装置，其特征在于，包括：处理器，用于调用存储器中的程序，以执行权利要求1至31，或，51至59任一项所述的方法。
  71. 一种压缩装置，其特征在于，包括：处理器和接口电路，所述接口电路用于与其它装置通信，所述处理器用于执行权利要求1至31，或，51至59任一项所述的方法。
  72. 一种解压装置，其特征在于，包括：用于执行权利要求32至50，或，60至68任一项所述的各个步骤的单元。
  73. 一种解压装置，其特征在于，包括：处理器，用于调用存储器中的程序，以执行权利要求32至50，或，60至68任一项所述的方法。
  74. 一种解压装置，其特征在于，包括：处理器和接口电路，所述接口电路用于与其它装置通信，所述处理器用于执行权利要求32至50，或，60至68任一项所述的方法。
  75. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储程序，所述程序被处理器调用时，权利要求1至31，或，51至59任一项所述的方法被执行；或，所述程序被处理器调用时，权利要求32至50，或，60至68任一项所述的方法被执行。
  76. 一种计算机程序，其特征在于，当所述程序被处理器调用时，权利要求1至31，或，51至59任一项所述的方法被执行；或，当所述程序被处理器调用时，权利要求32至50，或，60至68任一项所述的方法被执行。
PCT/CN2019/100900 2019-08-15 2019-08-15 以太帧头的压缩、解压方法和装置 WO2021026939A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
PCT/CN2019/100900 WO2021026939A1 (zh) 2019-08-15 2019-08-15 以太帧头的压缩、解压方法和装置
CN201980098681.0A CN114208137B (zh) 2019-08-15 2019-08-15 以太帧头的压缩、解压方法和装置
EP19941327.9A EP4016948B1 (en) 2019-08-15 2019-08-15 Method and apparatus for compressing ethernet header, and method and apparatus for decompressing ethernet header
US17/669,681 US11778070B2 (en) 2019-08-15 2022-02-11 Ethernet header compression method and apparatus and Ethernet header decompression method and apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/100900 WO2021026939A1 (zh) 2019-08-15 2019-08-15 以太帧头的压缩、解压方法和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/669,681 Continuation US11778070B2 (en) 2019-08-15 2022-02-11 Ethernet header compression method and apparatus and Ethernet header decompression method and apparatus

Publications (1)

Publication Number Publication Date
WO2021026939A1 true WO2021026939A1 (zh) 2021-02-18

Family

ID=74570421

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/100900 WO2021026939A1 (zh) 2019-08-15 2019-08-15 以太帧头的压缩、解压方法和装置

Country Status (4)

Country Link
US (1) US11778070B2 (zh)
EP (1) EP4016948B1 (zh)
CN (1) CN114208137B (zh)
WO (1) WO2021026939A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113079133A (zh) * 2021-03-16 2021-07-06 深圳市盛博科技嵌入式计算机有限公司 一种网关的数据传输方法和网关设备
CN113411838A (zh) * 2021-06-28 2021-09-17 展讯通信（上海）有限公司 基于头信息压缩的通信方法及设备
WO2023015420A1 (zh) * 2021-08-09 2023-02-16 Oppo广东移动通信有限公司 数据传输方法及装置

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110971363B (zh) * 2018-09-28 2022-03-08 华为技术有限公司 用于以太网数据的通信方法的方法和装置
EP3925184B1 (en) * 2019-02-14 2024-09-18 Sony Group Corporation Header compression adaptive to quality of radio channel
EP3823248A1 (en) * 2019-11-15 2021-05-19 Acklio Method and apparatus for compression profile distribution
US12020041B2 (en) * 2021-05-19 2024-06-25 Mobileye Vision Technologies Ltd. Fast configuration of a processing circuit

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102083137A (zh) * 2009-12-01 2011-06-01 大唐移动通信设备有限公司 一种传输数据的方法、系统和装置
CN108574656A (zh) * 2017-03-07 2018-09-25 华为技术有限公司 数据处理方法及设备
WO2018196491A1 (zh) * 2017-04-28 2018-11-01 电信科学技术研究院有限公司 上行数据解压缩、压缩的方法和装置

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101453298B (zh) * 2007-12-07 2013-06-05 华为技术有限公司 一种无线网络中头压缩的处理方法及系统、装置
CN104079488B (zh) * 2014-07-22 2017-03-29 武汉虹信通信技术有限责任公司 基于以太网二层头压缩的传输设备及方法
US10218483B2 (en) * 2015-09-25 2019-02-26 Qualcomm Incorporated Systems and methods for signaling and generating variable length block acknowledgment fields in a wireless network
CN109391963B (zh) * 2017-08-11 2022-03-11 华为技术有限公司 一种传输方法和网络设备
US10855814B2 (en) * 2017-10-20 2020-12-01 Comcast Cable Communications, Llc Non-access stratum capability information
WO2020155115A1 (zh) * 2019-02-01 2020-08-06 Oppo广东移动通信有限公司 一种头压缩的处理方法及装置、通信设备
RU2767321C1 (ru) * 2019-04-30 2022-03-17 Гуандун Оппо Мобайл Телекоммьюникейшнз Корп., Лтд. Способ и устройство для беспроводной связи
WO2021012260A1 (zh) * 2019-07-25 2021-01-28 Oppo广东移动通信有限公司 用于传输数据的方法、发送端设备和接收端设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102083137A (zh) * 2009-12-01 2011-06-01 大唐移动通信设备有限公司 一种传输数据的方法、系统和装置
CN108574656A (zh) * 2017-03-07 2018-09-25 华为技术有限公司 数据处理方法及设备
WO2018196491A1 (zh) * 2017-04-28 2018-11-01 电信科学技术研究院有限公司 上行数据解压缩、压缩的方法和装置

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113079133A (zh) * 2021-03-16 2021-07-06 深圳市盛博科技嵌入式计算机有限公司 一种网关的数据传输方法和网关设备
CN113411838A (zh) * 2021-06-28 2021-09-17 展讯通信（上海）有限公司 基于头信息压缩的通信方法及设备
CN113411838B (zh) * 2021-06-28 2022-10-28 展讯通信（上海）有限公司 基于头信息压缩的通信方法及设备
WO2023015420A1 (zh) * 2021-08-09 2023-02-16 Oppo广东移动通信有限公司 数据传输方法及装置

Also Published As

Publication number Publication date
EP4016948A4 (en) 2022-07-20
CN114208137A (zh) 2022-03-18
CN114208137B (zh) 2023-10-20
EP4016948A1 (en) 2022-06-22
EP4016948B1 (en) 2024-10-09
US11778070B2 (en) 2023-10-03
US20220166854A1 (en) 2022-05-26

Similar Documents

Publication Publication Date Title
WO2021026939A1 (zh) 以太帧头的压缩、解压方法和装置
US20220377602A1 (en) Method and apparatus for performing feedback-based ethernet header compression or decompression in wireless communication system
EP3267721B1 (en) Air-interface protocol stack configuration method, and data transmission method and device
US11477306B2 (en) Wireless communication methods and devices
CN113796057B (zh) 无线通信系统中防止数据丢失的用户数据压缩方法和装置
WO2021023044A1 (zh) 一种通信方法和装置
US12074705B2 (en) Method and apparatus for driving PDCP during data decompression failure in next-generation mobile communication system
EP4009603A1 (en) Method and apparatus for performing feedback-based ethernet header compression or decompression in wireless communication system
US20230188973A1 (en) Method and apparatus for signalling network coding capabilities
WO2023102938A1 (zh) 无线通信方法和通信设备
US20230140866A1 (en) Wireless data link layer compression and decompression
CN114270792B (zh) 一种传输信息的方法和装置
TW202021329A (zh) 通訊方法、終端設備和網路設備
WO2024140801A1 (zh) 一种数据传输方法、装置及系统
US20180317132A1 (en) Bicasting Data to Wireless Terminal over At Least Two Air Interfaces
TWI852131B (zh) 執行上行鏈路資料壓縮的方法和使用者設備
US20230209400A1 (en) Method and apparatus for effectively performing header compression or decompression procedure in next-generation mobile communication system
CN115699629B (zh) 一种数据传输方法及其设备
WO2022147801A1 (zh) 数据处理方法及装置
KR20230037637A (ko) 데이터 압축 방법, 장치 및 저장 매체
TW202318910A (zh) 執行上行鏈路資料壓縮的方法和使用者設備
CN117378248A (zh) 用于管理多播和广播业务的技术
JP2020014046A (ja) 端末装置、基地局装置、方法、および、集積回路

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19941327

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019941327

Country of ref document: EP

Effective date: 20220314