WO2021102970A1

WO2021102970A1 - Radio communication method and device

Info

Publication number: WO2021102970A1
Application number: PCT/CN2019/122125
Authority: WO
Inventors: 付喆; 刘建华
Original assignee: Oppo广东移动通信有限公司
Priority date: 2019-11-29
Filing date: 2019-11-29
Publication date: 2021-06-03
Also published as: CN114342462B; CN114342462A

Abstract

The embodiments of the present application provide a radio communication method and device. For an Ethernet type PDU session, compression parameters are effectively configured, thereby avoiding the problem of not supporting compression of an IP header, and also avoiding the problem of unnecessary reduction of resource efficiency of an air interface. The radio communication method comprises: a first device configuring EHC parameters and/or RoHC parameters for a first DRB, an Ethernet-type PDU session being mapped onto the first DRB; the first device sending compression information to a compression end device, the compression information including the EHC parameters and/or the RoHC parameters.

Description

Wireless communication method and equipment

Technical field

The embodiments of the present application relate to the communication field, and more specifically, to a wireless communication method and device.

Background technique

In the New Radio (NR) system, the core network can distinguish between multiple protocol data unit (Protocol Data Unit, PDU) session types, such as Internet Protocol (IP) type and Ethernet (Ethernet) type, each type of packet will be configured to a different PDU session. However, the core network does not differentiate the Ethernet payload, that is, Ethernet IP (over Ethernet) packets and Ethernet non-IP (non-IP over Ethernet) packets may be mapped in a PDU session, and then It is mapped to a data radio bearer (Data Radio Bearer, DRB). Of course, there may be only IP over Ethernet packets or non-IP over Ethernet packets in a PDU session. That is to say, it is uncertain whether there is an IP over Ethernet packet in a DRB, which may result in uncertain whether Robust Header Compression (RoHC) parameters should be configured in a DRB.

Summary of the invention

The embodiments of the present application provide a wireless communication method and device for effectively configuring compression parameters for an Ethernet type PDU session, avoiding the problem of not supporting IP header compression, and at the same time avoiding the problem of unnecessary resource efficiency reduction on the air interface.

In a first aspect, a wireless communication method is provided, the method including:

The first device configures Ethernet Header Compression (EHC) parameters and/or RoHC parameters for the first DRB, where an Ethernet type PDU session is mapped on the first DRB;

The first device sends compression information to the compression end device, where the compression information includes the EHC parameter and/or the RoHC parameter.

In a second aspect, a wireless communication method is provided, and the method includes:

The compression terminal device receives compression information sent by the first device, where the compression information includes EHC parameters and/or RoHC parameters configured for the first DRB, and an Ethernet type PDU session is mapped on the first DRB;

The compression terminal device compresses the Ethernet frame header of the data packet corresponding to the PDU session according to the compression information.

In a third aspect, a wireless communication device is provided, which is configured to execute the method in the above-mentioned first aspect or its implementation manners.

Specifically, the wireless communication device includes a functional module for executing the method in the foregoing first aspect or each of its implementation manners.

In a fourth aspect, a wireless communication device is provided, which is used to execute the method in the second aspect or its implementation manners.

Specifically, the wireless communication device includes a functional module for executing the method in the foregoing second aspect or each of its implementation manners.

In a fifth aspect, a wireless communication device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the above-mentioned first aspect or each of its implementation modes.

In a sixth aspect, a wireless communication device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the second aspect or its implementation manners.

In a seventh aspect, a device is provided for implementing any one of the first aspect to the second aspect or the method in each implementation manner thereof.

Specifically, the device includes: a processor, configured to call and run a computer program from the memory, so that the device installed with the device executes any one of the above-mentioned first aspect to the second aspect or any of the implementations thereof method.

In an eighth aspect, a computer-readable storage medium is provided for storing a computer program that enables a computer to execute any one of the first aspect to the second aspect or the method in each implementation manner thereof.

In a ninth aspect, a computer program product is provided, including computer program instructions that cause a computer to execute any one of the above-mentioned first to second aspects or the method in each implementation manner thereof.

In a tenth aspect, a computer program is provided, which when running on a computer, causes the computer to execute any one of the above-mentioned first aspect to the second aspect or the method in each implementation manner thereof.

Through the above technical solution, the first device configures the EHC parameters and/or RoHC parameters for the first DRB mapped to the Ethernet type PDU session, that is, for the Ethernet type PDU session, the compression parameters are effectively configured to avoid not supporting IP The problem of packet header compression, while avoiding the problem of unnecessary resource efficiency reduction of the air interface.

Description of the drawings

FIG. 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application.

Fig. 2 is a schematic flowchart of a wireless communication method provided according to an embodiment of the present application.

Fig. 3 is a schematic diagram of configuring EHC parameters and/or RoHC parameters according to an embodiment of the present application.

Fig. 4 is another schematic diagram of configuring EHC parameters and/or RoHC parameters according to an embodiment of the present application.

Fig. 5 is a schematic block diagram of a wireless communication device according to an embodiment of the present application.

Fig. 6 is a schematic block diagram of another wireless communication device provided according to an embodiment of the present application.

Fig. 7 is a schematic block diagram of a communication device provided according to an embodiment of the present application.

Fig. 8 is a schematic block diagram of an apparatus provided according to an embodiment of the present application.

Fig. 9 is a schematic block diagram of a communication system according to an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Regarding the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of this application.

The embodiments of this application can be applied to various communication systems, such as: Global System of Mobile Communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (Wideband Code) Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Wireless The (New Radio, NR) system, the evolution system of the NR system, the LTE (LTE-based access to unlicensed spectrum, LTE-U) system on the unlicensed spectrum, the NR (NR-based access to unlicensed spectrum, on the unlicensed spectrum, NR-U) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), next-generation communication systems or other communication systems, etc.

Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communication, but also support, for example, Device to Device (Device to Device, D2D) communication, machine to machine (Machine to Machine, M2M) communication, machine type communication (MTC), and vehicle to vehicle (V2V) communication, etc. The embodiments of this application can also be applied to these communications system.

Optionally, the communication system in the embodiments of the present application can be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, can also be applied to a dual connectivity (DC) scenario, and can also be applied to a standalone (SA) deployment. Network scene.

The embodiment of the application does not limit the applied frequency spectrum. For example, the embodiments of this application can be applied to licensed spectrum or unlicensed spectrum.

Exemplarily, the communication system 100 applied in the embodiment of the present application is shown in FIG. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or called a communication terminal or terminal). The network device 110 may provide communication coverage for a specific geographic area, and may communicate with terminal devices located in the coverage area.

Figure 1 exemplarily shows one network device and two terminal devices. Optionally, the communication system 100 may include multiple network devices and the coverage of each network device may include other numbers of terminal devices. The embodiment does not limit this.

Optionally, the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which are not limited in the embodiment of the present application.

It should be understood that the devices with communication functions in the network/system in the embodiments of the present application may be referred to as communication devices. Taking the communication system 100 shown in FIG. 1 as an example, the communication device may include a network device 110 having a communication function and a terminal device 120. The network device 110 and the terminal device 120 may be the specific devices described above, which will not be repeated here. The communication device may also include other devices in the communication system 100, such as network controllers, mobility management entities and other network entities, which are not limited in the embodiment of the present application.

It should be understood that the terms "system" and "network" in this article are often used interchangeably in this article. The term "and/or" in this article is only an association relationship that describes the associated objects, which means that there can be three kinds of relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, exist alone B these three situations. In addition, the character "/" in this text generally indicates that the associated objects before and after are in an "or" relationship.

The embodiments of this application describe various embodiments in combination with terminal equipment and network equipment. Among them, terminal equipment may also be referred to as User Equipment (UE), access terminal, subscriber unit, user station, mobile station, mobile station, and remote Station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc. The terminal device can be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, and personal digital processing (Personal Digital Assistant, PDA) devices, handheld devices with wireless communication functions, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, and next-generation communication systems, such as terminal devices in the NR network or Terminal equipment in the public land mobile network (PLMN) network that will evolve in the future.

As an example and not a limitation, in the embodiment of the present application, the terminal device may also be a wearable device. Wearable devices can also be referred to as wearable smart devices. It is a general term for using wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes. A wearable device is a portable device that is directly worn on the body or integrated into the user's clothes or accessories. Wearable devices are not only a kind of hardware device, but also realize powerful functions through software support, data interaction, and cloud interaction. In a broad sense, wearable smart devices include full-featured, large-sized, complete or partial functions that can be achieved without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, and need to cooperate with other devices such as smart phones. Use, such as all kinds of smart bracelets and smart jewelry for physical sign monitoring.

A network device can be a device used to communicate with a mobile device. The network device can be an access point (AP) in WLAN, a base station (BTS) in GSM or CDMA, or a device in WCDMA A base station (NodeB, NB), can also be an Evolutional Node B (eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device or base station in the NR network ( gNB) or network equipment in the future evolved PLMN network.

In the embodiment of the present application, the network equipment provides services for the cell, and the terminal equipment communicates with the network equipment through the transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell, and the cell may be a network equipment (for example, The cell corresponding to the base station. The cell can belong to a macro base station or a base station corresponding to a small cell. The small cell here can include: Metro cell, Micro cell, Pico Cells, Femto cells, etc. These small cells have the characteristics of small coverage and low transmit power, and are suitable for providing high-rate data transmission services.

The 5G Industrial Internet (Industrial Internet of Things, IIoT) needs to support the transmission of services such as Industrial Automation (Factory Automation), Transmission Automation (Transport Industry), and Intelligent Power (Electrical Power Distribution) in 5G systems. Based on its transmission requirements for delay and reliability, IIoT introduces the concepts of Time Sensitive Networking (TSN) or Time Sensitive Communication (TSC), and requires header compression processing for TSN services. Among them, the TSC service can be carried by an Ethernet (Ethernet) frame, or can be carried by an IP packet.

The introduction of the Ethernet frame issue is because the existing communication system only supports header compression for data packets whose PDU session (session) is IP. The PDU session refers to the association between the terminal device and the data network that provides the PDU connection service. In the 5G NR system, the PDU session type can be not only an IP packet type, but also an Ethernet type. For example, for the PDU layer, when the PDU Session type is IPv4, IPv6, or IPv4v6, the PDU session corresponds to IPv4 packets and/or IPv6 packets; when the PDU Session type is Ethernet, the PDU The session corresponds to Ethernet frames.

Packet Data Convergence Protocol (PDCP) introduces header compression and decompression functions to compress IP data packets. The current Robust Header Compression (RoHC) is configured for DRB. The compression end and decompression end use different header compression methods and header compression parameters according to the configured profile, and the RoHC protocol is used for compression and decompression. Compression processing.

In addition, according to the conclusion of the RAN2#105bis meeting, a new header compression mechanism (a completely 3GPP internal mechanism) can also be used to perform header compression processing on Ethernet packets. Specifically, this mechanism currently supports a mechanism for state transition based on feedback (feedback), that is, a mechanism for the compressor to switch from sending a full packet to sending a compressed packet. However, considering that if it is configured in RLC UM mode and the possibility of packet loss in DRB of EHC, there may be a problem that the decompression end has sent feedback, but the compression end has not received the feedback, resulting in the problem that state transitions cannot be performed.

In the NR system, the core network only distinguishes five PDU session types (IPv4, IPv6, IPv4v6, Ethernet, unstructured), and each type of packet will be configured to a different PDU session. However, the core network does not differentiate the Ethernet payload, that is, Ethernet IP (over Ethernet) packets and Ethernet non-IP (non-IP over Ethernet) packets may be mapped in a PDU session, and then Mapped to a DRB. Of course, there may be only IP over Ethernet packets or non-IP over Ethernet packets in a PDU session. This may result in uncertainty as to whether or not to configure RoHC in a DRB. Always configure the RoHC parameters, which may bring complexity to the terminal equipment processing (even if the packet in the DRB is not an IP over Ethernet packet, the terminal equipment must detect whether there is an IP packet, or whether to compress the IP packet). Always not configuring RoHC parameters may cause possible IP headers to be uncompressed, resulting in a decrease in air interface transmission efficiency.

Based on the above technical problems, this solution provides a solution for configuring Ethernet header compression (EHC) to avoid this problem.

The following describes in detail the Ethernet header compression (EHC) solution designed by the present application in response to the above technical problems.

FIG. 2 is a schematic flowchart of a wireless communication method 200 according to an embodiment of the present application. As shown in FIG. 2, the method 200 may include some or all of the following contents:

S210: The first device configures EHC parameters and/or RoHC parameters for a first DRB, where an Ethernet type PDU session is mapped on the first DRB;

S220: The first device sends compression information to the compression end device, where the compression information includes the EHC parameter and/or the RoHC parameter;

S230. The compression terminal device receives the compression information sent by the first device, where the compression information includes the EHC parameter and/or the RoHC parameter configured for the first DRB, and the first DRB is mapped with an Ethernet type PDU session;

S240: The compression terminal device compresses the Ethernet frame header of the data packet corresponding to the PDU session according to the compression information.

It should be noted that, in this embodiment of the present application, the compressed information may be compressed configuration information.

Optionally, in this embodiment of the application, if the PDU session corresponds to an Ethernet IP (IP over Ethernet) packet and an Ethernet non-IP (non-IP over Ethernet) packet, the first device combines the Ethernet IP packet with the Ethernet packet. Network non-IP packets are mapped or configured to different DRBs. Correspondingly, through the core network (such as through the instruction information from the core network device), or through the compression terminal device (such as through the instruction information from the compression terminal device), or through the first device itself (such as by parsing the received packet Format information), the first device determines whether the PDU session contains more than one packet type (Ethernet IP packet and Ethernet non-IP packet).

Optionally, the first device is an access network device.

Optionally, the compression terminal device may be a terminal device or a network device.

Optionally, the foregoing step S210 may specifically be:

The first device configures the EHC parameter and/or the RoHC parameter for the first DRB according to the first information, where:

The first information includes at least one of the following:

The compression capability of the compression terminal device, the packet type corresponding to the PDU session, whether the Ethernet load corresponding to the PDU session is an IP packet, whether the PDU session includes Ethernet IP packets and/or Ethernet non-IP packets, packet analysis information , The first indication information from the compression terminal device, and the second indication information from the second device.

Optionally, the compression capability of the compression terminal device includes but is not limited to at least one of the following:

Whether the compression end device supports EHC, whether the compression end device supports RoHC, whether the compression end device supports the compression of Ethernet IP packets, whether the compression end device supports the compression of IP packets, whether the compression end device supports or does not support at the same time EHC and RoHC compression.

Optionally, the packet type corresponding to the PDU session includes at least one of the following:

Ethernet IP packet, Ethernet non-IP packet.

Optionally, in this embodiment of the present application, the first device receives the first indication information sent by the compression end device, and the first indication information is used to indicate at least one of the following: the compression capability of the compression end device, the The packet type corresponding to the PDU session, and whether there are Ethernet IP packets and/or Ethernet non-IP packets in the Ethernet load corresponding to the PDU session.

Optionally, in this embodiment of the present application, the first device receives the second indication information sent by the second device, and the second indication information is used to indicate at least one of the following: the packet type corresponding to the PDU session, and the PDU Whether there are Ethernet IP packets and/or Ethernet non-IP packets in the Ethernet load corresponding to the session.

Optionally, the content indicated by the second indication information is obtained by the second device from the third device.

Optionally, the first device is an access network device, the second device is a Session Management Function (SMF) entity, and the third device is a Policy Control Function (PCF) entity or a data network (Data Network, DN) entity or terminal device.

Optionally, in the embodiment of the present application, the first device obtains at least one of the following by parsing the received high-level packet: the packet type corresponding to the PDU session, and whether there is an Ethernet IP in the Ethernet load corresponding to the PDU session Packets and/or Ethernet non-IP packets.

Optionally, in this embodiment of the present application, the first device configures the EHC parameter and/or the RoHC parameter for the first DRB according to the first information, including one of the following:

If the compression end device supports Ethernet header compression, the first device configures the EHC parameter and the RoHC parameter for the first DRB;

If the compression end device does not support the compression of IP packets, or the compression end device does not support the compression of Ethernet IP packets, the first device configures the EHC parameters only for the first DRB, or the first device is the first DRB. A DRB configures the EHC parameter and the RoHC parameter indicating that the header is not compressed;

If the compression end device supports compression of IP packets, or the compression end device supports compression of Ethernet IP packets, the first device configures the EHC parameters and the RoHC parameters for the first DRB;

If the compression end device does not support EHC, or the first device does not expect the compression end device to perform EHC compression, or the compression end device supports the compression of IP packets, or the compression end device does not support the compression of Ethernet IP packets, or , The compression end device does not support the compression of Ethernet non-IP packets, or the compression end device supports the compression of Ethernet IP packets, the first device configures the RoHC parameters for the first DRB, or the first device is The first DRB configures the RoHC parameter and the EHC parameter indicating that the header is not compressed;

If the compression end device supports compression of IP packets, or the compression end device supports compression of Ethernet IP packets, and there are Ethernet IP packets and/or Ethernet non-IP packets in the Ethernet load corresponding to the PDU session, the first A device configures the EHC parameter and the RoHC parameter for the first DRB;

If the compression end device supports compression of IP packets, or the compression end device supports compression of Ethernet IP packets, and the PDU session corresponds to Ethernet IP packets and Ethernet non-IP packets, the first device is configured for the first DRB The EHC parameter and the RoHC parameter;

If the compression end device does not support EHC, or the first device does not expect the compression end device to perform EHC compression, the first device configures the EHC parameter for the first DRB indicating that the header is not compressed, or the first device does not The first DRB configures EHC compression parameters;

If the first device does not expect the compression end device to perform EHC compression, the first device configures the EHC parameter for the first DRB indicating that the header is not compressed, or the first device does not configure the EHC parameter for the first DRB, Or the first device configures an EHC parameter for the first DRB that indicates that the header is not compressed;

If the first device does not expect the compression end device to perform RoHC compression, the first device configures the RoHC parameter for the first DRB indicating that the header is not compressed, or the first device does not configure the RoHC parameter for the first DRB;

If the PDU session corresponds to an Ethernet IP packet and an Ethernet non-IP packet, and the first DRB is mapped with an Ethernet IP packet corresponding to the PDU session, the first device configures the EHC parameter and the RoHC parameter for the first DRB ；

Even if it is determined according to the first information that the EHC parameters and the RoHC parameters can be configured for the first DRB, if the first device does not expect the compression end device to perform EHC compression, the first device configures the first DRB to indicate that the header is not configured. The compressed EHC parameter, or the first device does not configure the EHC parameter for the first DRB;

Even if it is determined according to the first information that the EHC parameters and the RoHC parameters can be configured for the first DRB, if the first device does not expect the compression end device to perform RoHC compression, the first device configures the first DRB to indicate that the header is not configured. The compressed RoHC parameter, or the first device does not configure the RoHC parameter for the first DRB;

If the PDU session corresponds to an Ethernet IP packet and an Ethernet non-IP packet, and the first DRB only maps the Ethernet non-IP packet corresponding to the PDU session, the first device configures the EHC parameters only for the first DRB, Or, the first device configures the EHC parameter and the RoHC parameter indicating that the header is not compressed for the first DRB;

If there are Ethernet IP packets and Ethernet non-IP packets in the Ethernet load corresponding to the PDU session, and the first DRB is mapped with the Ethernet IP packet in the Ethernet load corresponding to the PDU session, the first device is the The first DRB configures the EHC parameter and the RoHC parameter;

If there are Ethernet IP packets and Ethernet non-IP packets in the Ethernet load corresponding to the PDU session, and the first DRB is mapped with the Ethernet non-IP packets in the Ethernet load corresponding to the PDU session, the first device only Configure the EHC parameter for the first DRB, or the first device configures the EHC parameter and the RoHC parameter indicating that the header is not compressed for the first DRB;

If the compression end device does not support both RoHC and EHC compression, the first device only configures one of EHC parameters and RoHC parameters, or the first device configures EHC parameters and RoHC parameters, and the EHC parameters or RoHC parameters indicate The header is not compressed.

Optionally, in the embodiment of the present application, the compression terminal device determines the packet format corresponding to the PDU session according to the second information, where:

The second information includes at least one of the following:

The compression information, the compression capability of the compression terminal device, the data packet analysis information, and the third indication information from the access network device or the core network device.

Optionally, the data packet analysis information and/or the third indication information includes at least one of the following:

The data packet in the Ethernet load corresponding to the PDU session is an Ethernet IP packet or an Ethernet non-IP packet;

Whether the Ethernet packet corresponding to the PDU session includes an IP packet header;

Whether the Ethernet packet corresponding to the PDU session includes an IP packet.

Optionally, the compression end device obtains the data packet parsing information by parsing the upper layer packet received on the first DRB.

Optionally, the compression end device determines the packet format corresponding to the PDU session according to the second information, including one of the following:

The compression end device analyzes the high-level packet received on the first DRB to determine whether the packet format and/or the Ethernet load corresponding to the PDU session contains Ethernet packets, IP packets, Ethernet IP packets, and Ethernet packets. At least one of non-IP packets;

If the compression end device supports compression and EHC of IP packets, the compression end device determines whether there are Ethernet packets or IP packets in the Ethernet load corresponding to the PDU session by analyzing the upper layer packets received on the first DRB. , At least one of Ethernet IP packets and Ethernet non-IP packets;

If the compression end device supports the compression of Ethernet IP packets, the compression end device determines whether there are Ethernet packets or IP packets in the Ethernet load corresponding to the PDU session by analyzing the upper layer packet received on the first DRB , At least one of Ethernet IP packets and Ethernet non-IP packets;

If the compression information only includes the EHC parameters configured for the first DRB, the compression end device only determines the Ethernet load corresponding to the PDU session by analyzing the Ethernet header of the higher layer packet received on the first DRB Whether there is an Ethernet packet in the file;

If the compression information includes the EHC parameters and the RoHC parameters configured for the first DRB, the compression end device determines the PDU session by analyzing the Ethernet header and IP header of the higher layer packet received on the first DRB Whether there is at least one of an Ethernet packet, an IP packet, an Ethernet IP packet, and an Ethernet non-IP packet in the corresponding Ethernet load.

Optionally, the compression end device compresses the Ethernet frame header of the data packet corresponding to the PDU session according to the compression information, including one of the following:

If the compression information includes RoHC parameters and EHC parameters, the compression end device compresses the Ethernet IP header and the Ethernet frame header respectively;

If the compression information includes one of RoHC parameters and EHC parameters, the compression end device compresses only one of the IP header and the Ethernet frame header;

If the compression information includes two of the RoHC parameter and the EHC parameter, and at least one of them is configured to be non-compressed, the compression end device only compresses one of the IP header and the Ethernet frame header;

If the compression information includes two of the RoHC parameter and the EHC parameter, and both are configured to be non-compressed, the compression end device does not compress the IP header and the Ethernet frame header;

If the unconfigured compression information includes two of the RoHC parameter and the EHC parameter, the compression end device does not compress the IP header and the Ethernet frame header;

If there are non-IP packets and IP packets in the Ethernet load corresponding to the PDU session, the compression end device compresses the Ethernet frame header and IP header of the Ethernet IP packet, and compresses the Ethernet frame header for the Ethernet non-IP packet;

If there is an IP packet in the Ethernet load corresponding to the PDU session, the compression end device compresses the IP header and the Ethernet frame header respectively; specifically, compresses the Ethernet frame header and IP header for the Ethernet IP packet, and compresses the Ethernet non-IP packet Ethernet frame header;

If there is no IP packet in the Ethernet load corresponding to the PDU session, the compression end device only compresses the Ethernet frame header of the Ethernet packet;

If there are non-IP and IP packet headers in the Ethernet load corresponding to the PDU session, the compression end device compresses the IP packet header and the Ethernet frame header respectively; specifically, compresses the Ethernet frame header and the IP packet header for the Ethernet IP packet. The IP packet compresses the Ethernet frame header;

If there is an IP header in the Ethernet load corresponding to the PDU session, the compression end device compresses the Ethernet frame header and the IP header respectively; specifically, the Ethernet frame header and IP header are compressed for the Ethernet IP packet, and the Ethernet non-IP packet is compressed Ethernet frame header;

If there is no IP packet header in the Ethernet load corresponding to the PDU session, the compression end device only compresses the Ethernet frame header of the Ethernet packet.

It should be noted that, in the embodiment of the present application, the Ethernet frame header may also be referred to as an Ethernet packet header.

Optionally, in this embodiment of the present application, the compression end device determines whether to compress the Ethernet frame header and/or the IP packet header according to the second information.

Therefore, in the embodiment of the present application, the first device configures EHC parameters and/or RoHC parameters for the first DRB mapped to the Ethernet type PDU session, that is, for the Ethernet type PDU session, the compression parameters are effectively configured to avoid The problem of not supporting IP header compression is avoided, and the problem of unnecessary resource efficiency reduction of the air interface is avoided at the same time.

The wireless communication method 200 of the embodiment of the present application will be described in detail below through specific embodiments.

In Embodiment 1, the first device is a gNB and the compression end device is a UE as an example for description. Specifically, as shown in FIG. 3, the gNB may configure compression configuration information for the UE, and the compression configuration information includes EHC parameters and/or RoHC parameters configured for the DRB 1 mapped to the Ethernet type PDU session.

Optionally, in Embodiment 1, as shown in FIG. 3, the gNB receives the indication information 1 sent by the UE, where the indication information 1 is used to indicate at least one of the following:

Whether the UE supports EHC, whether the UE supports RoHC, whether the UE supports the compression of Ethernet IP packets, whether the UE supports the compression of IP packets, whether the UE supports both RoHC and EHC compression.

Optionally, in Embodiment 1, as shown in FIG. 3, the gNB receives the indication information 2 sent by the SMF entity, where the indication information 2 is used to indicate whether the packet type corresponding to the PDU session is an Ethernet non-IP type or Ethernet IP type, or the indication information 2 is used to indicate whether there are Ethernet IP packets and/or Ethernet non-IP packets in the Ethernet load corresponding to the PDU session.

In Embodiment 1, as shown in FIG. 3, the gNB configures EHC parameters and/or RoHC parameters for DRB 1 according to the first information. Wherein, the first information may be at least one of the following: content indicated by the indication information 1 and content indicated by the indication information 2.

Specifically, in Example 1,

1) gNB maps the above-mentioned Ethernet type PDU session to DRB1.

2) gNB configures RoHC parameters and EHC parameters for DRB1. (If the UE capability does not support IP compression, or Ethernet IP compression, only EHC parameters are configured. If the UE capability does not support EHC, or the gNB does not want to configure EHC compression, the gNB configures the DRB 1 Ethernet header to be uncompressed, that is, EHC Compression (compression) is empty (NULL), or EHC non-compressed (non-compressed), or EHC parameters are not configured. The same applies to RoHC parameters.

Optionally, in Embodiment 1, as shown in FIG. 3, the UE receives the compressed configuration information configured for DRB1.

Optionally, in Embodiment 1, as shown in FIG. 3, the UE determines the packet format according to the second information.

Wherein, the second information is at least one of the following:

UE compression capability, the compression configuration information (whether to configure RoHC parameters for IP compression), packet analysis information (the compression end parses the received high-level packet, and determines whether the packet type is Ethernet non-IP type or Ethernet IP type), indicating Information 3 (from gNB or core network equipment, such as SMF entity).

Optionally, in Embodiment 1, if the UE supports EHC and IP compression, or Ethernet IP compression, each time the UE receives a high-layer packet, it parses the high-layer packet to determine the above-mentioned Ethernet type PDU Whether there is at least one of the following in the Ethernet load corresponding to the session: Ethernet packet, IP packet, Ethernet non-IP packet, Ethernet IP packet.

Optionally, in Embodiment 1, the indication information 3 is used to indicate whether the Ethernet packet type and/or Ethernet load corresponding to the above-mentioned Ethernet type PDU session includes at least one of the following: Ethernet packet, IP Packets, Ethernet non-IP packets, Ethernet IP packets.

Further, if it is determined that there is an IP packet or an Ethernet IP packet in the Ethernet load corresponding to the PDU session of the Ethernet type, the UE compresses the Ethernet packet and the IP packet respectively. Otherwise, the UE only compresses the Ethernet packet.

In Embodiment 2, the first device is a gNB and the compression end device is a UE as an example for description. Specifically, as shown in FIG. 4, the gNB may configure compression configuration information for the UE, and the compression configuration information includes EHC parameters and/or RoHC parameters configured for the DRB 1 mapped to the Ethernet type PDU session.

Optionally, in Embodiment 2, as shown in FIG. 4, the gNB receives the indication information a sent by the UE, where the indication information a is used to indicate at least one of the following:

Optionally, in Embodiment 2, as shown in FIG. 4, the SMF entity obtains indication information c from the PCF entity or the DN entity, and the indication information c is used to indicate that the packet type corresponding to the PDU session is an Ethernet non-IP type. It is also the Ethernet IP type, or the indication information c is used to indicate whether there is an Ethernet IP packet and/or an Ethernet non-IP packet (non-IP over Ethernet+IP over Ethernet) in the Ethernet load corresponding to the PDU session.

In Embodiment 2, as shown in Figure 4, the gNB receives the indication information b sent by the SMF entity, where the indication information b is used to indicate whether the packet type corresponding to the PDU session is an Ethernet non-IP type or an Ethernet IP type Or, the indication information b is used to indicate whether there are Ethernet IP packets and/or Ethernet non-IP packets in the Ethernet load corresponding to the PDU session.

Optionally, in Embodiment 2, as shown in FIG. 4, the gNB configures EHC parameters and/or RoHC parameters for DRB 1 according to the first information. Wherein, the first information may be at least one of the following: the content indicated by the indication information a, the content indicated by the indication information b, packet format information (gNB parses the received high-level packets on its own to determine the packet format information, and The format information includes whether the packet type is an Ethernet non-IP type, or an Ethernet IP type, or whether there is an Ethernet IP packet).

Specifically, in Example 2,

1) Even if they are all Ethernet-type PDU sessions, gNB maps Ethernet IP packets and Ethernet non-IP packets to different DRBs. Correspondingly, only the EHC parameters and RoHC parameters are configured for the DRB mapping Ethernet IP packets, and the EHC parameters are configured for the DRB mapping Ethernet non-IP packets.

Optionally, when mapping the DRB and PDU session, the gNB does not further distinguish whether the load of the Ethernet packet is an IP packet. Correspondingly, the gNB determines the UE compression capability support according to the above indication information a, and/or, after determining the existence of IP and Ethernet non-IP packets according to the above indication information b, the gNB configures EHC parameters and RoHC parameters for DRB1, otherwise, only DRB 1 Configure EHC parameters.

For example, if the UE capability does not support IP compression, or does not support IP over Ethernet compression, only DRB 1 is configured with EHC parameters.

For example, if the UE capability supports IP compression or IP over Ethernet compression, and the above indication information b indicates that there are Ethernet IP packets and/or Ethernet non-IP packets in the Ethernet load corresponding to the PDU session, it is configured for DRB 1 EHC parameters and RoHC parameters.

For example, even if the EHC parameters and RoHC parameters can be configured according to the first information, if the gNB does not want to configure EHC compression, the gNB configures the DBR 1 Ethernet header to be uncompressed, that is, EHC compression is NULL, or EHC non-compressed, or no EHC is configured parameter. The same applies to ROHC.

Optionally, in Embodiment 2, as shown in FIG. 4, the UE receives the compression configuration information configured for DRB1. For example, configure the PDU session mapping of the Ethernet type in DRB 1.

Optionally, in Embodiment 2, as shown in FIG. 4, the UE determines the packet format according to the second information.

Wherein, the second information is at least one of the following:

UE compression capability, the compression configuration information (whether to configure RoHC parameters for IP compression), packet analysis information (the compression end parses the received high-level packet, and determines whether the packet type is Ethernet non-IP type or Ethernet IP type), indicating Information d (from gNB or core network equipment, such as SMF entity).

Optionally, in Embodiment 2, if the UE supports EHC and IP compression, or Ethernet IP compression, each time the UE receives a high-level packet, it will parse the high-level packet to determine the above-mentioned Ethernet type PDU Whether there is at least one of the following in the Ethernet load corresponding to the session: Ethernet packet, IP packet, Ethernet non-IP packet, Ethernet IP packet.

Optionally, in Embodiment 2, the indication information d is used to indicate whether the packet type and/or Ethernet load corresponding to the above-mentioned Ethernet type PDU session includes at least one of the following: Ethernet packet, IP packet , Ethernet non-IP packet, Ethernet IP packet.

Further, if it is determined that there is an IP header or an Ethernet IP packet in the Ethernet load corresponding to the PDU session of the Ethernet type, the UE compresses the Ethernet frame header and the IP packet header respectively. Otherwise, the UE only compresses the Ethernet frame header.

Optionally, in Embodiment 2, if only the EHC parameters are configured for DRB 1, and no RoHC parameters are configured, the UE only analyzes the Ethernet packet header and does not further analyze the IP packet header. If RoCH parameters and EHC parameters are configured for DRB 1, the UE will parse the Ethernet packet header and IP packet header each time it receives a higher layer packet to determine whether there is an IP packet header. If it exists, the Ethernet header and the IP header are compressed respectively, otherwise only the Ethernet header is compressed.

The method embodiments of the present application are described in detail above with reference to Figs. 2 to 4, and the device embodiments of the present application are described in detail below in conjunction with Figs. 5 to 9. It should be understood that the device embodiments and the method embodiments correspond to each other and are similar The description can refer to the method embodiment.

Fig. 5 shows a schematic block diagram of a wireless communication device 300 according to an embodiment of the present application. The wireless communication device 300 is the first device. As shown in FIG. 5, the wireless communication device 300 includes:

The processing unit 310 is configured to configure EHC parameters and/or RoHC parameters for the first DRB, where an Ethernet type PDU session is mapped on the first DRB;

The communication unit 320 is configured to send compression information to the compression terminal device, where the compression information includes the EHC parameter and/or the RoHC parameter.

Optionally, the processing unit 310 is specifically configured to:

Configure the EHC parameter and/or the RoHC parameter for the first DRB according to the first information, where:

The first information includes at least one of the following:

Optionally, the compression capability of the compression terminal device includes at least one of the following:

Ethernet IP packet, Ethernet non-IP packet.

Optionally, the first indication information is used to indicate at least one of the following:

The compression capability of the compression terminal device, the packet type corresponding to the PDU session, and whether there are Ethernet IP packets and/or Ethernet non-IP packets in the Ethernet load corresponding to the PDU session.

Optionally, the second indication information is used to indicate at least one of the following:

The packet type corresponding to the PDU session, and whether there are Ethernet IP packets and/or Ethernet non-IP packets in the Ethernet load corresponding to the PDU session.

Optionally, the first device is an access network device, the second device is an SMF entity, and the third device is a PCF entity or a DN entity or a terminal device.

Optionally, the processing unit 310 is further configured to obtain at least one of the following by parsing the received high-level packet:

Optionally, the processing unit 310 configures the EHC parameter and/or the RoHC parameter for the first DRB according to the first information, including one of the following:

If the compression end device supports Ethernet header compression, the processing unit 310 configures the EHC parameter and the RoHC parameter for the first DRB;

If the compression end device does not support the compression of IP packets, or the compression end device does not support the compression of Ethernet IP packets, the processing unit 310 configures the EHC parameters only for the first DRB, or the processing unit 310 is for the first DRB. A DRB configures the EHC parameter and the RoHC parameter indicating that the header is not compressed;

If the compression end device supports compression of IP packets, or the compression end device supports compression of Ethernet IP packets, the processing unit 310 configures the EHC parameters and the RoHC parameters for the first DRB;

If the compression end device does not support EHC, or the first device does not expect the compression end device to perform EHC compression, or the compression end device supports the compression of IP packets, or the compression end device does not support the compression of Ethernet IP packets, or , The compression end device does not support the compression of Ethernet non-IP packets, or the compression end device supports the compression of Ethernet IP packets, the processing unit 310 configures the RoHC parameters for the first DRB, or the processing unit 310 is The first DRB configures the RoHC parameter and the EHC parameter indicating that the header is not compressed;

If the compression end device supports compression of IP packets, or the compression end device supports compression of Ethernet IP packets, and there are Ethernet IP packets and/or Ethernet non-IP packets in the Ethernet load corresponding to the PDU session, this process The unit 310 configures the EHC parameter and the RoHC parameter for the first DRB;

If the compression end device supports compression of IP packets, or the compression end device supports compression of Ethernet IP packets, and the PDU session corresponds to an Ethernet IP packet and an Ethernet non-IP packet, the processing unit 310 configures the first DRB The EHC parameter and the RoHC parameter;

If the compression end device does not support EHC, or the processing unit 310 does not expect the compression end device to perform EHC compression, the processing unit 310 configures the EHC parameter for the first DRB indicating that the header is not compressed, or the processing unit 310 does not The first DRB configures EHC compression parameters;

If the first device does not expect the compression end device to perform EHC compression, the processing unit 310 configures the EHC parameter for the first DRB indicating that the header is not compressed, or the processing unit 310 does not configure the EHC parameter for the first DRB, Or, the processing unit 310 configures the EHC parameter indicating that the header is not compressed for the first DRB;

If the first device does not expect the compression end device to perform RoHC compression, the processing unit 310 configures the RoHC parameter for the first DRB indicating that the header is not compressed, or the processing unit 310 does not configure the RoHC parameter for the first DRB;

If the PDU session corresponds to an Ethernet IP packet and an Ethernet non-IP packet, and the first DRB is mapped with an Ethernet IP packet corresponding to the PDU session, the processing unit 310 configures the EHC parameter and the RoHC parameter for the first DRB ；

If the PDU session corresponds to an Ethernet IP packet and an Ethernet non-IP packet, and the first DRB only maps the Ethernet non-IP packet corresponding to the PDU session, the processing unit 310 configures the EHC parameter only for the first DRB, Alternatively, the processing unit 310 configures the EHC parameter and the RoHC parameter indicating that the header is not compressed for the first DRB;

If there are Ethernet IP packets and Ethernet non-IP packets in the Ethernet load corresponding to the PDU session, and the first DRB is mapped with the Ethernet IP packet in the Ethernet load corresponding to the PDU session, the processing unit 310 is the The first DRB configures the EHC parameter and the RoHC parameter;

If there are Ethernet IP packets and Ethernet non-IP packets in the Ethernet load corresponding to the PDU session, and the first DRB is mapped with the Ethernet non-IP packets in the Ethernet load corresponding to the PDU session, the processing unit 310 only Configure the EHC parameter for the first DRB, or the processing unit 310 configures the EHC parameter for the first DRB and the RoHC parameter indicating that the header is not compressed;

If the compression end device does not support simultaneous RoHC and EHC compression, the processing unit 310 only configures one of the EHC parameter and the RoHC parameter, or the processing unit 310 configures the EHC parameter and the RoHC parameter, and the EHC parameter The parameter or the RoHC parameter indicates that the header is not compressed.

Optionally, if the PDU session corresponds to an Ethernet IP packet and an Ethernet non-IP packet, the processing unit 310 is further configured to map or configure the Ethernet IP packet and the Ethernet non-IP packet to different DRBs.

Optionally, the first device is an access network device.

Optionally, in some embodiments, the aforementioned communication unit may be a communication interface or a transceiver, or an input/output interface of a communication chip or a system-on-chip. The aforementioned processing unit may be one or more processors.

It should be understood that the wireless communication device 300 according to the embodiment of the present application may correspond to the terminal device in the method embodiment of the present application, and the above-mentioned and other operations and/or functions of each unit in the wireless communication device 300 are used to implement the functions shown in FIG. 2 respectively. The corresponding process of the first device in the method 200 is shown. For the sake of brevity, it will not be repeated here.

Fig. 6 shows a schematic block diagram of a wireless communication device 400 according to an embodiment of the present application. The wireless communication device 400 is a compression terminal device. As shown in FIG. 6, the wireless communication device 400 includes:

The communication unit 410 is configured to receive compression information sent by the first device, where the compression information includes EHC parameters and/or RoHC parameters configured for the first DRB, and an Ethernet type PDU session is mapped on the first DRB;

The processing unit 420 is configured to compress the Ethernet frame header of the data packet corresponding to the PDU session according to the compression information.

Optionally, the processing unit 420 is further configured to determine a packet format corresponding to the PDU session according to the second information, where the second information includes at least one of the following:

Optionally, the processing unit 420 is further configured to obtain the data packet parsing information by parsing the high-level packet received on the first DRB.

Optionally, the processing unit 420 determines the packet format corresponding to the PDU session according to the second information, including one of the following:

The processing unit 420 analyzes the high-level packet received on the first DRB to determine whether the packet format and/or the Ethernet load corresponding to the PDU session contains an Ethernet packet, an IP packet, an Ethernet IP packet, At least one of Ethernet non-IP packets;

If the compression terminal device supports IP packet compression and EHC, the processing unit 420 analyzes the upper layer packet received on the first DRB to determine whether there are Ethernet packets or IP packets in the Ethernet load corresponding to the PDU session , At least one of Ethernet IP packets and Ethernet non-IP packets;

If the compression end device supports the compression of Ethernet IP packets, the processing unit 420 analyzes the high-level packets received on the first DRB to determine whether there are Ethernet packets or IP packets in the Ethernet load corresponding to the PDU session. , At least one of Ethernet IP packets and Ethernet non-IP packets;

If the compression information only includes the EHC parameters configured for the first DRB, the processing unit 420 only determines the Ethernet load corresponding to the PDU session by parsing the Ethernet header of the higher layer packet received on the first DRB Whether there is an Ethernet packet in the file;

If the compression information includes the EHC parameter and the RoHC parameter configured for the first DRB, the processing unit 420 determines the PDU session by analyzing the Ethernet header and IP header of the higher layer packet received on the first DRB Whether there is at least one of an Ethernet packet, an IP packet, an Ethernet IP packet, and an Ethernet non-IP packet in the corresponding Ethernet load.

Optionally, the processing unit 420 compresses the Ethernet frame header of the data packet corresponding to the PDU session according to the compression information, including one of the following:

If the compression information includes the RoHC parameter and the EHC parameter, the processing unit 420 compresses the Ethernet IP header and the Ethernet frame header respectively;

If the compression information includes one of the RoHC parameter and the EHC parameter, the processing unit 420 compresses only one of the IP packet header and the Ethernet frame header;

If the compression information includes two of the RoHC parameter and the EHC parameter, and at least one of them is configured to be non-compressed, the processing unit 420 only compresses one of the IP header and the Ethernet frame header;

If the compression information includes two of the RoHC parameter and the EHC parameter, and both are configured to be non-compressed, the processing unit 420 does not compress the IP header and the Ethernet frame header;

If the unconfigured compression information includes two of the RoHC parameter and the EHC parameter, the processing unit 420 does not compress the IP header and the Ethernet frame header;

If there are non-IP packets and IP packets in the Ethernet load corresponding to the PDU session, the processing unit 420 compresses the Ethernet frame header and the IP header of the Ethernet IP packet, and compresses the Ethernet frame header of the Ethernet non-IP packet;

If there is an IP packet in the Ethernet load corresponding to the PDU session, the processing unit 420 compresses the IP packet header and the Ethernet frame header respectively;

If there is no IP packet in the Ethernet load corresponding to the PDU session, the processing unit 420 only compresses the Ethernet frame header of the Ethernet packet;

If there are non-IP and IP packet headers in the Ethernet load corresponding to the PDU session, the processing unit 420 compresses the IP packet header and the Ethernet frame header respectively;

If there is an IP header in the Ethernet load corresponding to the PDU session, the processing unit 420 compresses the Ethernet header and the IP header respectively;

If there is no IP header in the Ethernet load corresponding to the PDU session, the processing unit 420 only compresses the Ethernet header of the Ethernet packet.

Optionally, the processing unit 420 is further configured to determine whether to compress the Ethernet frame header and/or the IP packet header according to the second information.

Optionally, the first device is an access network device.

Optionally, in some embodiments, the above-mentioned communication unit may be a communication interface or a transceiver, or an input/output interface of a communication chip or a system-on-chip.

It should be understood that the wireless communication device 400 according to the embodiment of the present application may correspond to the network device in the method embodiment of the present application, and the above-mentioned and other operations and/or functions of each unit in the wireless communication device 400 are respectively intended to realize the The corresponding process of the compression terminal device in the method 200 is shown, and for the sake of brevity, it will not be repeated here.

FIG. 7 is a schematic structural diagram of a communication device 500 provided by an embodiment of the present application. The communication device 500 shown in FIG. 7 includes a processor 510, and the processor 510 can call and run a computer program from the memory to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 7, the communication device 500 may further include a memory 520. The processor 510 may call and run a computer program from the memory 520 to implement the method in the embodiment of the present application.

The memory 520 may be a separate device independent of the processor 510, or may be integrated in the processor 510.

Optionally, as shown in FIG. 7, the communication device 500 may further include a transceiver 530, and the processor 510 may control the transceiver 530 to communicate with other devices. Specifically, it may send information or data to other devices, or receive other devices. Information or data sent by the device.

Wherein, the transceiver 530 may include a transmitter and a receiver. The transceiver 530 may further include an antenna, and the number of antennas may be one or more.

Optionally, the communication device 500 may specifically be the first device of the embodiment of the present application, and the communication device 500 may implement the corresponding process implemented by the first device in each method of the embodiment of the present application. For the sake of brevity, it is not here. Go into details again.

Optionally, the communication device 500 may specifically be the compression terminal device of the embodiment of the present application, and the communication device 500 may implement the corresponding processes implemented by the compression terminal device in the various methods of the embodiments of the present application. For the sake of brevity, it is not here. Go into details again.

Fig. 8 is a schematic structural diagram of a device according to an embodiment of the present application. The apparatus 600 shown in FIG. 8 includes a processor 610, and the processor 610 can call and run a computer program from the memory to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 8, the apparatus 600 may further include a memory 620. The processor 610 may call and run a computer program from the memory 620 to implement the method in the embodiment of the present application.

The memory 620 may be a separate device independent of the processor 610, or may be integrated in the processor 610.

Optionally, the device 600 may further include an input interface 630. The processor 610 can control the input interface 630 to communicate with other devices or chips, and specifically, can obtain information or data sent by other devices or chips.

Optionally, the device 600 may further include an output interface 640. The processor 610 can control the output interface 640 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.

Optionally, the device can be applied to the first device in the embodiment of the present application, and the device can implement the corresponding process implemented by the first device in each method of the embodiment of the present application. For brevity, details are not described herein again.

Optionally, the device can be applied to the compression end device in the embodiment of the present application, and the device can implement the corresponding process implemented by the compression end device in each method in the embodiment of the present application. For the sake of brevity, details are not described herein again.

Optionally, the device mentioned in the embodiment of the present application may also be a chip. For example, it can be a system-on-chip, a system-on-chip, a system-on-chip, or a system-on-chip.

FIG. 9 is a schematic block diagram of a communication system 700 according to an embodiment of the present application. As shown in FIG. 9, the communication system 700 includes a terminal device 710 and a network device 720.

Wherein, the terminal device 710 can be used to implement the corresponding function implemented by the compression terminal device in the above method, and the network device 720 can be used to implement the corresponding function implemented by the compression terminal device or the first device in the above method. For brevity , I won’t repeat it here.

It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capability. In the implementation process, the steps of the foregoing method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in the form of software. The above-mentioned processor may be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (ASIC), a ready-made programmable gate array (Field Programmable Gate Array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like. The steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor. The software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

It can be understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), and electrically available Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory. The volatile memory may be a random access memory (Random Access Memory, RAM), which is used as an external cache. By way of exemplary but not restrictive description, many forms of RAM are available, such as static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (Double Data Rate SDRAM, DDR SDRAM), Enhanced Synchronous Dynamic Random Access Memory (Enhanced SDRAM, ESDRAM), Synchronous Link Dynamic Random Access Memory (Synchlink DRAM, SLDRAM) ) And Direct Rambus RAM (DR RAM). It should be noted that the memories of the systems and methods described herein are intended to include, but are not limited to, these and any other suitable types of memories.

It should be understood that the foregoing memory is exemplary but not restrictive. For example, the memory in the embodiment of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is to say, the memory in the embodiments of the present application is intended to include, but is not limited to, these and any other suitable types of memory.

The embodiments of the present application also provide a computer-readable storage medium for storing computer programs.

Optionally, the computer-readable storage medium may be applied to the first device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the first device in each method of the embodiment of the present application. For the sake of brevity, I won't repeat them here.

Optionally, the computer-readable storage medium can be applied to the compression end device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the compression end device in each method of the embodiment of the present application. For the sake of brevity, I won't repeat them here.

The embodiments of the present application also provide a computer program product, including computer program instructions.

Optionally, the computer program product can be applied to the first device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the first device in each method of the embodiment of the present application. For the sake of brevity, This will not be repeated here.

Optionally, the computer program product can be applied to the compression end device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the compression end device in each method of the embodiment of the present application. For the sake of brevity, This will not be repeated here.

The embodiment of the present application also provides a computer program.

Optionally, the computer program can be applied to the first device in the embodiment of the present application, and when the computer program runs on the computer, the computer is caused to execute the corresponding process implemented by the first device in each method of the embodiment of the present application, For the sake of brevity, I will not repeat them here.

Optionally, the computer program can be applied to the compression end device in the embodiment of the present application, and when the computer program runs on the computer, the computer is caused to execute the corresponding process implemented by the compression end device in each method of the embodiment of the present application. For the sake of brevity, I will not repeat them here.

A person of ordinary skill in the art may realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether these functions are executed by hardware or software depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and conciseness of description, the specific working process of the above-described system, device, and unit can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, device, and method can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

In addition, the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.

If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium. In response to this understanding, the technical solution of this application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the embodiments of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disks or optical disks and other media that can store program codes. .

The above are only specific implementations of this application, but the scope of protection of this application is not limited to this. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in this application. Should be covered within the scope of protection of this application. Therefore, the protection scope of this application shall be subject to the protection scope of the claims.

Claims

A wireless communication method, characterized by comprising:

The first device configures the Ethernet header compression EHC parameters and/or the robustness header compression RoHC parameters for the first data radio bearer DRB, wherein the first DRB is mapped with an Ethernet type protocol data unit PDU session;

The first device sends compression information to the compression end device, where the compression information includes the EHC parameter and/or the RoHC parameter.
The method according to claim 1, wherein the first device configuring EHC parameters and/or RoHC parameters for the first DRB comprises:

The first device configures the EHC parameter and/or the RoHC parameter for the first DRB according to the first information, where:

The first information includes at least one of the following:

The compression capability of the compression terminal device, the packet type corresponding to the PDU session, whether the Ethernet load corresponding to the PDU session is an Internet Protocol IP packet, and whether the PDU session includes an Ethernet IP packet and/or an Ethernet non- IP packet, packet analysis information, the first indication information from the compression terminal device, and the second indication information from the second device.
The method according to claim 2, wherein the compression capability of the compression terminal device comprises at least one of the following:

Whether the compression end device supports EHC, whether the compression end device supports RoHC, whether the compression end device supports the compression of Ethernet IP packets, whether the compression end device supports the compression of IP packets, whether the compression end device Supports or does not support EHC and RoHC compression at the same time.
The method according to claim 2 or 3, wherein the packet type corresponding to the PDU session includes at least one of the following:

Ethernet IP packet, Ethernet non-IP packet.
The method according to any one of claims 2 to 4, wherein the first indication information is used to indicate at least one of the following:

The compression capability of the compression terminal device, the packet type corresponding to the PDU session, and whether there are Ethernet IP packets and/or Ethernet non-IP packets in the Ethernet load corresponding to the PDU session.
The method according to any one of claims 2 to 5, wherein the second indication information is used to indicate at least one of the following:

The packet type corresponding to the PDU session, and whether there are Ethernet IP packets and/or Ethernet non-IP packets in the Ethernet load corresponding to the PDU session.
The method according to any one of claims 2 to 6, wherein the content indicated by the second indication information is obtained by the second device from a third device.
The method according to claim 7, wherein the first device is an access network device, the second device is a session management function SMF entity, and the third device is a policy control function PCF entity or a data network DN entity or terminal equipment.
The method according to any one of claims 2 to 8, wherein the method further comprises:

The first device obtains at least one of the following by analyzing the received high-level packet:

The packet type corresponding to the PDU session, and whether there are Ethernet IP packets and/or Ethernet non-IP packets in the Ethernet load corresponding to the PDU session.
The method according to any one of claims 2 to 9, wherein the first device configures the EHC parameters and/or the RoHC parameters for the first DRB according to first information, including: One of:

If the compression end device supports Ethernet header compression, the first device configures the EHC parameters and the RoHC parameters for the first DRB;

If the compression end device does not support the compression of IP packets, or the compression end device does not support the compression of Ethernet IP packets, the first device configures the EHC parameters only for the first DRB, or the The first device configures the EHC parameter and the RoHC parameter indicating that the header is not compressed for the first DRB;

If the compression end device supports compression of IP packets, or the compression end device supports compression of Ethernet IP packets, the first device configures the EHC parameters and the RoHC parameters for the first DRB;

If the compression end device does not support EHC, or the first device does not expect the compression end device to perform EHC compression, or the compression end device supports compression of IP packets, or the compression end device does not support Ethernet IP Packet compression, or the compression end device does not support the compression of Ethernet non-IP packets, or the compression end device supports the compression of Ethernet IP packets, and the first device configures the first DRB RoHC parameter, or, the first device configures the RoHC parameter and the EHC parameter indicating that the header is not compressed for the first DRB;

If the compression end device supports compression of IP packets, or the compression end device supports compression of Ethernet IP packets, and there are Ethernet IP packets and/or Ethernet non-IP packets in the Ethernet load corresponding to the PDU session , The first device configures the EHC parameter and the RoHC parameter for the first DRB;

If the compression end device supports compression of IP packets, or the compression end device supports compression of Ethernet IP packets, and the PDU session corresponds to an Ethernet IP packet and an Ethernet non-IP packet, the first device is all Configuring the EHC parameter and the RoHC parameter in the first DRB;

If the compression end device does not support EHC, or the first device does not expect the compression end device to perform EHC compression, the first device configures the first DRB with the EHC parameter indicating that the header is not compressed, or The first device does not configure EHC compression parameters for the first DRB;

If the first device does not expect the compression end device to perform EHC compression, the first device configures the EHC parameter for the first DRB indicating that the header is not compressed, or the first device is not the first DRB. A DRB configures the EHC parameter, or the first device configures the EHC parameter for the first DRB indicating that the header is not compressed;

If the first device does not expect the compression end device to perform RoHC compression, the first device configures the RoHC parameter for the first DRB indicating that the header is not compressed, or the first device is not the first DRB. A DRB configures the RoHC parameters;

If the PDU session corresponds to an Ethernet IP packet and an Ethernet non-IP packet, and the first DRB is mapped with an Ethernet IP packet corresponding to the PDU session, the first device configures the first DRB EHC parameters and the RoHC parameters;

If the PDU session corresponds to an Ethernet IP packet and an Ethernet non-IP packet, and the first DRB only maps the Ethernet non-IP packet corresponding to the PDU session, the first device is only the first DRB Configure the EHC parameter, or the first device configures the EHC parameter and the RoHC parameter indicating that the header is not compressed for the first DRB;

If there are Ethernet IP packets and Ethernet non-IP packets in the Ethernet load corresponding to the PDU session, and the first DRB is mapped with the Ethernet IP packet in the Ethernet load corresponding to the PDU session, the first A device configures the EHC parameters and the RoHC parameters for the first DRB;

If there are Ethernet IP packets and Ethernet non-IP packets in the Ethernet load corresponding to the PDU session, and the first DRB is mapped with the Ethernet non-IP packets in the Ethernet load corresponding to the PDU session, the The first device configures the EHC parameter only for the first DRB, or the first device configures the EHC parameter and the RoHC parameter indicating that the header is not compressed for the first DRB;

If the compression end device does not support RoHC and EHC compression at the same time, the first device configures only one of the EHC parameters and the RoHC parameters, or the first device configures the EHC parameters and all the RoHC parameters. The RoHC parameter, and the EHC parameter or the RoHC parameter indicates that the header is not compressed.
The method according to any one of claims 1 to 10, wherein the method further comprises:

If the PDU session corresponds to an Ethernet IP packet and an Ethernet non-IP packet, the first device maps or configures the Ethernet IP packet and the Ethernet non-IP packet to different DRBs.
The method according to any one of claims 1 to 11, wherein the first device is an access network device.
A wireless communication method, characterized by comprising:

The compression terminal device receives the compression information sent by the first device, where the compression information includes Ethernet header compression EHC parameters and/or robustness header compression RoHC parameters configured for the first data radio bearer DRB, and the first DRB A protocol data unit PDU session mapped with an Ethernet type;

The compression terminal device compresses the Ethernet frame header of the data packet corresponding to the PDU session according to the compression information.
The method according to claim 13, wherein the method further comprises:

The compression terminal device determines the packet format corresponding to the PDU session according to the second information, where:

The second information includes at least one of the following:

The compression information, the compression capability of the compression terminal device, data packet analysis information, and third indication information from the access network device or the core network device.
The method according to claim 14, wherein the compression capability of the compression terminal device comprises at least one of the following:

Whether the compression end device supports EHC, whether the compression end device supports RoHC, whether the compression end device supports the compression of Ethernet IP packets, whether the compression end device supports the compression of Internet Protocol IP packets, the compression end Whether the device supports EHC and RoHC compression at the same time or not.
The method according to claim 14 or 15, wherein the data packet analysis information and/or the third indication information comprises at least one of the following:

The data packet in the Ethernet load corresponding to the PDU session is an Ethernet IP packet or an Ethernet non-IP packet;

Whether the Ethernet packet corresponding to the PDU session includes an IP packet header;

Whether the Ethernet packet corresponding to the PDU session includes an IP packet.
The method according to any one of claims 14 to 16, wherein the method further comprises:

The compression terminal device obtains the data packet analysis information by parsing the high-level packet received on the first DRB.
The method according to any one of claims 14 to 17, wherein the compression end device determines the packet format corresponding to the PDU session according to the second information, including one of the following:

The compression end device determines whether there is an Ethernet packet, an IP packet, or an Ethernet IP packet in the packet format and/or Ethernet load corresponding to the PDU session by analyzing the high-level packet received on the first DRB , At least one of Ethernet non-IP packets;

If the compression end device supports compression of IP packets and EHC, the compression end device determines whether there is an Ethernet in the Ethernet load corresponding to the PDU session by analyzing the upper layer packet received on the first DRB. At least one of a packet, an IP packet, an Ethernet IP packet, and an Ethernet non-IP packet;

If the compression end device supports the compression of Ethernet IP packets, the compression end device determines whether there is Ethernet in the Ethernet load corresponding to the PDU session by analyzing the upper layer packet received on the first DRB. At least one of a packet, an IP packet, an Ethernet IP packet, and an Ethernet non-IP packet;

If the compression information only includes the EHC parameters configured for the first DRB, the compression end device only determines the PDU by analyzing the Ethernet header of the higher layer packet received on the first DRB Whether there are Ethernet packets in the Ethernet load corresponding to the session;

If the compression information includes the EHC parameters and the RoHC parameters configured for the first DRB, the compression end device performs processing on the Ethernet header and IP header of the higher layer packet received on the first DRB. Parsing to determine whether there is at least one of an Ethernet packet, an IP packet, an Ethernet IP packet, and an Ethernet non-IP packet in the Ethernet load corresponding to the PDU session.
The method according to any one of claims 13 to 18, wherein the compression end device compresses the Ethernet frame header of the data packet corresponding to the PDU session according to the compression information, including one of the following :

If the compression information includes the RoHC parameter and the EHC parameter, the compression end device compresses the Ethernet IP header and the Ethernet frame header respectively;

If the compression information includes one of the RoHC parameter and the EHC parameter, the compression end device compresses only one of the IP packet header and the Ethernet frame header;

If the compression information includes two of the RoHC parameters and the EHC parameters, and at least one of them is configured to be non-compressed, the compression end device compresses only one of the IP header and the Ethernet frame header;

If the compression information includes two of the RoHC parameters and the EHC parameters, and both are configured to be non-compressed, the compression end device does not compress the IP header and the Ethernet frame header;

If the unconfigured compression information includes two of the RoHC parameter and the EHC parameter, the compression end device does not compress the IP packet header and the Ethernet frame header;

If there are non-IP packets and IP packets in the Ethernet load corresponding to the PDU session, the compression end device compresses the Ethernet frame header and the IP header of the Ethernet IP packet, and compresses the Ethernet frame header of the Ethernet non-IP packet;

If there is an IP packet in the Ethernet load corresponding to the PDU session, the compression end device compresses the IP packet header and the Ethernet frame header respectively;

If there is no IP packet in the Ethernet load corresponding to the PDU session, the compression end device only compresses the Ethernet frame header of the Ethernet packet;

If there are non-IP and IP packet headers in the Ethernet load corresponding to the PDU session, the compression end device compresses the IP packet header and the Ethernet frame header respectively;

If there is an IP packet header in the Ethernet load corresponding to the PDU session, the compression end device compresses the Ethernet frame header and the IP packet header respectively;

If there is no IP packet header in the Ethernet load corresponding to the PDU session, the compression end device only compresses the Ethernet frame header of the Ethernet packet.
The method according to any one of claims 14 to 19, wherein the method further comprises:

The compression terminal device determines whether to compress the Ethernet frame header and/or the IP packet header according to the second information.
The method according to any one of claims 13 to 20, wherein the first device is an access network device.
A wireless communication device, wherein the wireless communication device is a first device, and the wireless communication device includes:

A processing unit, configured to configure Ethernet header compression EHC parameters and/or robustness header compression RoHC parameters for the first data radio bearer DRB, wherein the first DRB is mapped with an Ethernet type protocol data unit PDU session;

The communication unit is configured to send compression information to the compression terminal device, where the compression information includes the EHC parameter and/or the RoHC parameter.
The device according to claim 22, wherein the processing unit is specifically configured to:

Configure the EHC parameters and/or the RoHC parameters for the first DRB according to the first information, where:

The first information includes at least one of the following:

The compression capability of the compression terminal device, the packet type corresponding to the PDU session, whether the Ethernet load corresponding to the PDU session is an Internet Protocol IP packet, and whether the PDU session includes an Ethernet IP packet and/or an Ethernet non- IP packet, packet analysis information, the first indication information from the compression terminal device, and the second indication information from the second device.
The device according to claim 23, wherein the compression capability of the compression end device comprises at least one of the following:

Whether the compression end device supports EHC, whether the compression end device supports RoHC, whether the compression end device supports the compression of Ethernet IP packets, whether the compression end device supports the compression of IP packets, whether the compression end device Supports or does not support EHC and RoHC compression at the same time.
The device according to claim 23 or 24, wherein the packet type corresponding to the PDU session includes at least one of the following:

Ethernet IP packet, Ethernet non-IP packet.
The device according to any one of claims 23 to 25, wherein the first indication information is used to indicate at least one of the following:

The compression capability of the compression terminal device, the packet type corresponding to the PDU session, and whether there are Ethernet IP packets and/or Ethernet non-IP packets in the Ethernet load corresponding to the PDU session.
The device according to any one of claims 23 to 26, wherein the second indication information is used to indicate at least one of the following:

The packet type corresponding to the PDU session, and whether there are Ethernet IP packets and/or Ethernet non-IP packets in the Ethernet load corresponding to the PDU session.
The device according to any one of claims 23 to 27, wherein the content indicated by the second indication information is obtained by the second device from a third device.
The device according to claim 28, wherein the first device is an access network device, the second device is a session management function SMF entity, and the third device is a policy control function PCF entity or a data network DN entity or terminal equipment.
The device according to any one of claims 23 to 29, wherein the processing unit is further configured to obtain at least one of the following by parsing the received high-level packet:

The packet type corresponding to the PDU session, and whether there are Ethernet IP packets and/or Ethernet non-IP packets in the Ethernet load corresponding to the PDU session.
The device according to any one of claims 23 to 30, wherein the processing unit configures the EHC parameters and/or the RoHC parameters for the first DRB according to the first information, including the following One:

If the compression end device supports Ethernet header compression, the processing unit configures the EHC parameters and the RoHC parameters for the first DRB;

If the compression end device does not support the compression of IP packets, or the compression end device does not support the compression of Ethernet IP packets, the processing unit configures the EHC parameters only for the first DRB, or the processing The unit configures the EHC parameter and the RoHC parameter indicating that the header is not compressed for the first DRB;

If the compression end device supports compression of IP packets, or the compression end device supports compression of Ethernet IP packets, the processing unit configures the EHC parameters and the RoHC parameters for the first DRB;

If the compression end device does not support EHC, or the first device does not expect the compression end device to perform EHC compression, or the compression end device supports compression of IP packets, or the compression end device does not support Ethernet IP Packet compression, or the compression end device does not support the compression of Ethernet non-IP packets, or the compression end device supports the compression of Ethernet IP packets, and the processing unit configures the RoHC for the first DRB Parameter, or, the processing unit configures the RoHC parameter and the EHC parameter indicating that the header is not compressed for the first DRB;

If the compression end device supports compression of IP packets, or the compression end device supports compression of Ethernet IP packets, and there are Ethernet IP packets and/or Ethernet non-IP packets in the Ethernet load corresponding to the PDU session , The processing unit configures the EHC parameter and the RoHC parameter for the first DRB;

If the compression end device supports compression of IP packets, or the compression end device supports compression of Ethernet IP packets, and the PDU session corresponds to an Ethernet IP packet and an Ethernet non-IP packet, the processing unit is the The first DRB configures the EHC parameters and the RoHC parameters;

If the compression end device does not support EHC, or the processing unit does not expect the compression end device to perform EHC compression, the processing unit configures the EHC parameter indicating that the header is not compressed for the first DRB, or the The processing unit does not configure EHC compression parameters for the first DRB;

If the first device does not expect the compression end device to perform EHC compression, the processing unit configures the EHC parameter indicating that the header is not compressed for the first DRB, or the processing unit is not the first DRB Configure the EHC parameter, or the processing unit configures the EHC parameter for the first DRB indicating that the packet header is not compressed;

If the first device does not expect the compression end device to perform RoHC compression, the processing unit configures the RoHC parameter indicating that the header is not compressed for the first DRB, or the processing unit is not the first DRB Configure the RoHC parameters;

If the PDU session corresponds to an Ethernet IP packet and an Ethernet non-IP packet, and the first DRB is mapped with an Ethernet IP packet corresponding to the PDU session, the processing unit configures the EHC for the first DRB Parameters and the RoHC parameters;

If the PDU session corresponds to an Ethernet IP packet and an Ethernet non-IP packet, and the first DRB only maps the Ethernet non-IP packet corresponding to the PDU session, the processing unit configures only the first DRB The EHC parameter, or the processing unit configures the EHC parameter and the RoHC parameter indicating that the header is not compressed for the first DRB;

If there are Ethernet IP packets and Ethernet non-IP packets in the Ethernet load corresponding to the PDU session, and the first DRB is mapped with the Ethernet IP packets in the Ethernet load corresponding to the PDU session, the processing The unit configures the EHC parameter and the RoHC parameter for the first DRB;

If there are Ethernet IP packets and Ethernet non-IP packets in the Ethernet load corresponding to the PDU session, and the first DRB is mapped with the Ethernet non-IP packets in the Ethernet load corresponding to the PDU session, the The processing unit configures only the EHC parameters for the first DRB, or the processing unit configures the EHC parameters for the first DRB and the RoHC parameters indicating that the header is not compressed;

If the compression end device does not support simultaneous RoHC and EHC compression, the processing unit configures only one of the EHC parameter and the RoHC parameter, or the processing unit configures the EHC parameter and the RoHC Parameter, and the EHC parameter or the RoHC parameter indicates that the header is not compressed.
The device according to any one of claims 22 to 31, characterized in that:

If the PDU session corresponds to an Ethernet IP packet and an Ethernet non-IP packet, the processing unit is further configured to map or configure the Ethernet IP packet and the Ethernet non-IP packet to different DRBs.
The device according to any one of claims 22 to 32, wherein the first device is an access network device.
A wireless communication device, wherein the wireless communication device is a compression terminal device, and the wireless communication device includes:

The communication unit is configured to receive compression information sent by the first device, where the compression information includes Ethernet header compression EHC parameters and/or robustness header compression RoHC parameters configured for the first data radio bearer DRB, and the first A protocol data unit PDU session of the Ethernet type is mapped on the DRB;

The processing unit is configured to compress the Ethernet frame header of the data packet corresponding to the PDU session according to the compression information.
The device according to claim 34, wherein the processing unit is further configured to determine a packet format corresponding to the PDU session according to the second information, wherein:

The second information includes at least one of the following:

The compression information, the compression capability of the compression terminal device, data packet analysis information, and third indication information from the access network device or the core network device.
The device according to claim 35, wherein the compression capability of the compression terminal device comprises at least one of the following:

Whether the compression end device supports EHC, whether the compression end device supports RoHC, whether the compression end device supports the compression of Ethernet IP packets, whether the compression end device supports the compression of Internet Protocol IP packets, the compression end Whether the device supports EHC and RoHC compression at the same time or not.
The device according to claim 35 or 36, wherein the data packet analysis information and/or the third indication information comprises at least one of the following:

The data packet in the Ethernet load corresponding to the PDU session is an Ethernet IP packet or an Ethernet non-IP packet;

Whether the Ethernet packet corresponding to the PDU session includes an IP packet header;

Whether the Ethernet packet corresponding to the PDU session includes an IP packet.
The device according to any one of claims 35 to 37, wherein the processing unit is further configured to obtain the data packet analysis information by parsing a higher layer packet received on the first DRB.
The device according to any one of claims 35 to 38, wherein the processing unit determines the packet format corresponding to the PDU session according to the second information, comprising one of the following:

The processing unit determines whether the packet format corresponding to the PDU session and/or the Ethernet load exists in an Ethernet packet, an IP packet, an Ethernet IP packet, or an Ethernet packet by analyzing the high-level packet received on the first DRB. At least one of Ethernet non-IP packets;

If the compression terminal device supports IP packet compression and EHC, the processing unit determines whether there is an Ethernet packet in the Ethernet load corresponding to the PDU session by analyzing the upper layer packet received on the first DRB , At least one of IP packets, Ethernet IP packets, and Ethernet non-IP packets;

If the compression terminal device supports the compression of Ethernet IP packets, the processing unit determines whether there are Ethernet packets in the Ethernet load corresponding to the PDU session by analyzing the higher layer packets received on the first DRB , At least one of IP packets, Ethernet IP packets, and Ethernet non-IP packets;

If the compression information only includes the EHC parameters configured for the first DRB, the processing unit only determines the PDU session by analyzing the Ethernet header of the higher layer packet received on the first DRB Whether there is an Ethernet packet in the corresponding Ethernet load;

If the compression information includes the EHC parameters and the RoHC parameters configured for the first DRB, the processing unit analyzes the Ethernet header and IP header of the higher layer packet received on the first DRB To determine whether there is at least one of an Ethernet packet, an IP packet, an Ethernet IP packet, and an Ethernet non-IP packet in the Ethernet load corresponding to the PDU session.
The device according to any one of claims 34 to 39, wherein the processing unit compresses the Ethernet frame header of the data packet corresponding to the PDU session according to the compression information, comprising one of the following:

If the compression information includes the RoHC parameter and the EHC parameter, the processing unit compresses the Ethernet IP header and the Ethernet frame header respectively;

If the compression information includes one of the RoHC parameter and the EHC parameter, the processing unit compresses only one of the IP packet header and the Ethernet frame header;

If the compression information includes two of the RoHC parameters and the EHC parameters, and at least one of them is configured to be non-compressed, the processing unit compresses only one of the IP header and the Ethernet frame header;

If the compression information includes two of the RoHC parameter and the EHC parameter, and both are configured as non-compressed, the processing unit does not compress the IP header and the Ethernet frame header;

If the unconfigured compression information includes two of the RoHC parameter and the EHC parameter, the processing unit does not compress the IP packet header and the Ethernet frame header;

If there are non-IP packets and IP packets in the Ethernet load corresponding to the PDU session, the processing unit compresses the Ethernet frame header and the IP header of the Ethernet IP packet, and compresses the Ethernet frame header of the Ethernet non-IP packet;

If there is an IP packet in the Ethernet load corresponding to the PDU session, the processing unit compresses the IP packet header and the Ethernet frame header respectively;

If there is no IP packet in the Ethernet load corresponding to the PDU session, the processing unit only compresses the Ethernet frame header of the Ethernet packet;

If there are non-IP and IP packet headers in the Ethernet load corresponding to the PDU session, the processing unit compresses the IP packet header and the Ethernet frame header respectively;

If there is an IP header in the Ethernet load corresponding to the PDU session, the processing unit compresses the Ethernet header and the IP header respectively;

If there is no IP packet header in the Ethernet load corresponding to the PDU session, the processing unit only compresses the Ethernet frame header of the Ethernet packet.
The device according to any one of claims 35 to 40, wherein the processing unit is further configured to determine whether to compress an Ethernet frame header and/or an IP packet header according to the second information.
The device according to any one of claims 34 to 41, wherein the first device is an access network device.
A terminal device, characterized by comprising: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute as claimed in claims 1 to 12 Any of the methods.
A network device, characterized by comprising: a processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, and execute as claimed in claims 13 to 21 Any of the methods.
An apparatus, characterized by comprising: a processor, configured to call and run a computer program from a memory, so that a device installed with the apparatus executes the method according to any one of claims 1 to 12.
A device, characterized by comprising: a processor, configured to call and run a computer program from a memory, so that a device installed with the device executes the method according to any one of claims 13 to 21.
A computer-readable storage medium, characterized in that it is used to store a computer program that enables a computer to execute the method according to any one of claims 1 to 12.
A computer-readable storage medium, characterized in that it is used to store a computer program that enables a computer to execute the method according to any one of claims 13 to 21.
A computer program product, characterized by comprising computer program instructions, which cause a computer to execute the method according to any one of claims 1 to 12.
A computer program product, characterized by comprising computer program instructions, which cause a computer to execute the method according to any one of claims 13 to 21.
A computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 12.
A computer program, wherein the computer program causes a computer to execute the method according to any one of claims 13-21.