CN114342462B

CN114342462B - Wireless communication method and device

Info

Publication number: CN114342462B
Application number: CN201980100010.3A
Authority: CN
Inventors: 付喆; ***
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2019-11-29
Filing date: 2019-11-29
Publication date: 2023-09-29
Anticipated expiration: 2039-11-29
Also published as: CN114342462A; WO2021102970A1

Abstract

The embodiment of the application provides a wireless communication method and device, which are used for effectively configuring compression parameters for an Ethernet type PDU session, avoiding the problem that IP packet header compression is not supported, and simultaneously avoiding the problem that unnecessary resource efficiency of an air interface is reduced. The wireless communication method comprises the following steps: the first device configures EHC parameters and/or RoHC parameters for a first DRB, wherein the first DRB is mapped with an Ethernet type PDU session; the first device transmits compression information to a compression end device, the compression information including the EHC parameter and/or the RoHC parameter.

Description

Wireless communication method and device

Technical Field

The embodiment of the application relates to the field of communication, and more particularly relates to a wireless communication method and device.

Background

In a New Radio (NR) system, a core network may distinguish between multiple protocol data unit (Protocol Data Unit, PDU) session (session) types, e.g., internet protocol (Internet Protocol, IP) type and Ethernet (Ethernet) type, each type of packet being configured to a different PDU session. However, the core network does not distinguish between Ethernet payload (payload) portions, i.e., ethernet IP (IP over Ethernet) packets and Ethernet non-IP (non-IP over Ethernet) packets may be mapped in a PDU session and thus in a data radio bearer (Data Radio Bearer, DRB). It is of course also possible that only IP over Ethernet packets or non-IP over Ethernet packets are present in one PDU session. That is, whether an IP over Ethernet packet exists in one DRB is uncertain, which may cause uncertainty as to whether a robust header compression (Robust Header Compression, roHC) parameter is to be configured in one DRB.

Disclosure of Invention

The embodiment of the application provides a wireless communication method and device, which are used for effectively configuring compression parameters for an Ethernet type PDU session, avoiding the problem that IP packet header compression is not supported, and simultaneously avoiding the problem that unnecessary resource efficiency of an air interface is reduced.

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

the first device configures an ethernet header compression (Ethernet Header Compression, EHC) parameter and/or a RoHC parameter for a first DRB on which an ethernet type PDU session is mapped;

the first device transmits compression information to a compression end device, the compression information including the EHC parameter and/or the RoHC parameter.

In a second aspect, there is provided a wireless communication method comprising:

the compression end equipment receives compression information sent by first equipment, wherein the compression information comprises EHC parameters and/or RoHC parameters configured for a first DRB, and the first DRB is mapped with a PDU session of an Ethernet type;

and the compression end equipment 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 for performing the method of the first aspect or implementations thereof.

In particular, the wireless communication device comprises functional modules for performing the method of the first aspect or implementations thereof described above.

In a fourth aspect, a wireless communication device is provided for performing the method of the second aspect or implementations thereof.

Specifically, the wireless communication device comprises functional modules for performing the method of the second aspect or implementations thereof described above.

In a fifth aspect, a wireless communication device is provided that includes a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory and executing the method in the first aspect or various implementation manners thereof.

In a sixth aspect, a wireless communication device is provided that includes a processor and a memory. The memory is for storing a computer program and the processor is for calling and running the computer program stored in the memory for performing the method of the second aspect or implementations thereof described above.

A seventh aspect provides an apparatus for implementing the method of any one of the first to second aspects or each implementation thereof.

Specifically, the device comprises: a processor for calling and running a computer program from a memory, causing a device in which the apparatus is installed to perform the method as in any one of the first to second aspects or implementations thereof described above.

In an eighth aspect, a computer-readable storage medium is provided for storing a computer program that causes a computer to perform the method of any one of the above-described first to second aspects or implementations thereof.

A ninth aspect provides a computer program product comprising computer program instructions for causing a computer to perform the method of any one of the first to second aspects or implementations thereof.

In a tenth aspect, there is provided a computer program which, when run on a computer, causes the computer to perform the method of any one of the first to second aspects or implementations thereof.

Through the technical scheme, the first device configures the EHC parameter and/or the RoHC parameter for the first DRB mapped with the PDU session of the Ethernet type, namely, effectively configures the compression parameter for the PDU session of the Ethernet type, thereby avoiding the problem that IP packet header compression is not supported and simultaneously avoiding the problem that unnecessary resource efficiency of an air interface is reduced.

Drawings

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

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

Fig. 3 is a schematic diagram of a configuration of EHC parameters and/or RoHC parameters provided in accordance with an embodiment of the application.

Fig. 4 is a schematic diagram of another configuration of EHC parameters and/or RoHC parameters provided in accordance with an embodiment of the application.

Fig. 5 is a schematic block diagram of a wireless communication device provided in accordance with an embodiment of the present application.

Fig. 6 is a schematic block diagram of another wireless communication device provided in accordance with 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 in accordance with an embodiment of the present application.

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

Detailed Description

The following description of the technical solutions according to the embodiments of the present application will be given with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art to which the application pertains without inventive faculty, are intended to fall within the scope of the application.

The embodiment of the application can be applied to various communication systems, such as: global system for mobile communications (Global System of Mobile communication, GSM), code division multiple access (Code Division Multiple Access, CDMA) system, wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, general packet Radio service (General Packet Radio Service, GPRS), long term evolution (Long Term Evolution, LTE) system, long term evolution advanced (Advanced long term evolution, LTE-a) system, new Radio (NR) system, evolution system of NR system, LTE-based access to unlicensed spectrum, LTE-U) system over unlicensed spectrum, NR (NR-based access to unlicensed spectrum, NR-U) system over unlicensed spectrum, universal mobile communication system (Universal Mobile Telecommunication System, UMTS), wireless local area network (Wireless Local Area Networks, WLAN), wireless fidelity (Wireless Fidelity, wiFi), next generation communication system or other communication system, etc.

Generally, the number of connections supported by the conventional communication system is limited and easy to implement, however, as the communication technology advances, the mobile communication system will support not only conventional communication but also, for example, device-to-Device (D2D) communication, machine-to-machine (Machine to Machine, M2M) communication, machine type communication (Machine Type Communication, MTC), inter-vehicle (Vehicle to Vehicle, V2V) communication, and the like, to which the embodiments of the present application can also be applied.

Optionally, the communication system in the embodiment of the present application may be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, or a Stand Alone (SA) fabric scenario.

The frequency spectrum of the application of the embodiment of the application is not limited. For example, the embodiment of the application can be applied to licensed spectrum and unlicensed spectrum.

An exemplary communication system 100 to which embodiments of the present application may be applied 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 referred to as a communication terminal, terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices located within the coverage area.

Fig. 1 illustrates one network device and two terminal devices by way of example, and the communication system 100 may alternatively include multiple network devices and may include other numbers of terminal devices within the coverage area of each network device, as embodiments of the application are not limited in this regard.

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

It should be understood that a device having a communication function in a network/system according to an embodiment of the present application may be referred to as a communication device. Taking the communication system 100 shown in fig. 1 as an example, the communication device may include a network device 110 and a terminal device 120 with communication functions, where the network device 110 and the terminal device 120 may be specific devices described above, and are not described herein again; the communication device may also include other devices in the communication system 100, such as a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.

It should be understood that the terms "system" and "network" are used interchangeably herein. The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

The embodiments of the present application describe various embodiments in connection with a terminal device and a network device, wherein: a terminal device may also be called a User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a User terminal, a wireless communication device, a User agent, a User device, or the like. The terminal device may be a station (STALON, ST) in a WLAN, may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle mounted device, a wearable device, and a next generation communication system, e.g. a terminal device in an NR network or a terminal device in a future evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.

By way of example, and not limitation, in embodiments of the present application, the terminal device may also be a wearable device. The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wear by applying wearable technology and developing wearable devices, such as glasses, gloves, watches, clothes, shoes and the like. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart jewelry, etc. for physical sign monitoring.

The network device may be a device for communicating with the mobile device, the network device may be an Access Point (AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or an Access Point, or a vehicle device, a wearable device, and a network device in NR network or a base station (gNB) or a network device in future evolved PLMN network, etc.

In the embodiment of the present application, a network device provides a service for a cell, and a terminal device communicates with the network device through a transmission resource (for example, a frequency domain resource, or a spectrum resource) used by the cell, where the cell may be a cell corresponding to the network device (for example, a base station), and the cell may belong to a macro base station or a base station corresponding to a Small cell (Small cell), where the Small cell may include: urban cells (Metro cells), micro cells (Micro cells), pico cells (Pico cells), femto cells (Femto cells) and the like, and the small cells have the characteristics of small coverage area and low transmitting power and are suitable for providing high-rate data transmission services.

The demand in the 5G industrial internet (Industrial intenet of Things, IIoT) supports the transmission of business such as industrial automation (Factory automation), transmission automation (Transport Industry) and intelligent power (Electrical Power Distribution) in 5G systems. IIoT introduces the concept of time sensitive networks (Time Sensitive Networking, TSN) or time sensitive communications (Time Sensitive Communication, TSC) based on its latency and reliability transmission requirements, and requires header compression of TSN traffic. The TSC traffic may be carried by Ethernet frames or IP packets.

The Ethernet frame problem is introduced because only header compression of data packets having a PDU session (session) of IP is supported in the existing communication system, wherein the PDU session refers to an association between the terminal device and the data network providing the PDU connection service. In the 5G NR system, the PDU session may be of the IP packet type or the Ethernet type. For example, for a PDU layer (PDU layer), when the PDU Session type is IPv4, IPv6, or IPv4v6, the PDU Session corresponds to an IPv4 packet (packets) and/or an IPv6 packet; when the PDU Session type is Ethernet, the PDU Session corresponds to Ethernet frames.

Header compression and decompression functions are incorporated into the packet data convergence protocol (Packet Data Convergence Protocol, PDCP) to header compress IP packets. The current robust packet header compression (Robust Header Compression, roHC) is configured for DRBs, and the compression end and the decompression end use different header compression modes and header compression parameters according to the configured configuration file (profile) to perform compression and decompression processing by adopting the RoHC protocol.

In addition, according to the conclusion of the RAN2#105bis conference, a new header compression mechanism (a mechanism inside the 3 GPP) can be used to perform header compression processing on the Ethernet packet. Specifically, the mechanism currently supports a mechanism for performing state transition based on feedback (feedback), that is, a mechanism that a compression end transitions from transmitting a full packet (full packet) to transmitting a compressed packet (compressed packet). However, considering that if configured in RLC UM mode, and the possibility of packet loss of the DRB of the EHC, there may be a problem that the decompression side transmits the feedback, but the compression side does not receive the feedback, resulting in failure to perform state transition.

In the NR system, the core network distinguishes only 5 PDU session types (IPv 4, IPv6, IPv4v6, ethernet, unstructured), and each type of packet is configured to a different PDU session. However, the core network does not distinguish between Ethernet payload (payload) portions, i.e., ethernet IP (IP over Ethernet) packets and Ethernet non-IP (non-IP over Ethernet) packets may be mapped in one PDU session and thus one DRB. It is of course also possible that only IP over Ethernet packets or non-IP over Ethernet packets are present in one PDU session. This may make it uncertain whether RoHC is to be configured in one DRB. Configuring RoHC parameters always may lead to complexity of processing by the terminal device (even if the packet in the DRB is not an IP over Ethernet packet, the terminal device should detect whether there is an IP packet or not, and should not compress the IP packet). Always not configuring RoHC parameters may cause that the possible IP header cannot be compressed, resulting in a decrease of the air interface transmission efficiency.

Based on the technical problems, the scheme provides a scheme for configuring Ethernet Header Compression (EHC), and the problem is avoided.

The following describes in detail an Ethernet Header Compression (EHC) scheme devised by the present application in view of the above technical problems.

Fig. 2 is a schematic flow chart of a wireless communication method 200 according to an embodiment of the application, as shown in fig. 2, the method 200 may include some or all of the following:

s210, the first device configures an EHC parameter and/or a RoHC parameter for a first DRB, wherein the first DRB is mapped with an Ethernet type PDU session;

s220, the first device sends compression information to a compression end device, where the compression information includes the EHC parameter and/or the RoHC parameter;

s230, the compression end 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 a first DRB, and the first DRB has an ethernet type PDU session mapped thereon;

and S240, the compression end equipment 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 the embodiment of the present application, the compressed information may be compressed configuration information.

Optionally, in an embodiment of the present application, if the PDU session corresponds to an Ethernet IP (IP over Ethernet) packet and an Ethernet non-IP (over Ethernet) packet, the first device maps or configures the Ethernet IP packet and the Ethernet non-IP packet to different DRBs. Accordingly, the first device determines, via the core network (e.g., via the indication information from the core network device), or via the compression end device (e.g., via the indication information from the compression end device), or via the first device itself (e.g., via parsing the received packet format information), whether more than one packet type (ethernet IP packets and ethernet non-IP packets) are included in the PDU session.

Optionally, the first device is an access network device.

Alternatively, the compression end device may be a terminal device or a network device.

Alternatively, the step S210 may specifically be:

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

the first information includes at least one of:

the compression capability of the compression end 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 comprises an Ethernet IP packet and/or an Ethernet non-IP packet, packet parsing information, first indication information from the compression end device, and second indication information from the second device.

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

whether the compression end device supports EHC, whether the compression end device supports RoHC, whether the compression end device supports compression of ethernet IP packets, whether the compression end device supports compression of IP packets, and whether the compression end device supports both EHC and RoHC compression.

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

ethernet IP packets, ethernet non-IP packets.

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

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

Optionally, the content indicated by the second indication information is acquired 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 (Session Management Function, SMF) entity, and the third device is a policy control function (Policy Control function, PCF) entity or a Data Network (DN) entity or a terminal device.

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

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

if the compression end device supports ethernet packet 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 compression of the IP packet, or the compression end device does not support compression of the ethernet IP packet, 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 packet header is not compressed for the first DRB;

If the compression end device supports compression of an IP packet or the compression end device supports compression of an ethernet IP packet, the first device configures the EHC parameter and the RoHC parameter 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 compression of ethernet non-IP packets, or the compression end device supports compression of ethernet IP packets, the first device configures the RoHC parameter for the first DRB, or the first device configures the RoHC parameter and the EHC parameter indicating that the packet header is not compressed for the first DRB;

if the compression end device supports compression of an IP packet or the compression end device supports compression of an ethernet IP packet, and an ethernet IP packet and/or an ethernet non-IP packet exists in an 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 an IP packet or the compression end device supports compression of an ethernet IP packet, and the PDU session corresponds to an ethernet IP packet and an ethernet non-IP packet, the first device configures the EHC parameter and the RoHC parameter 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, the first device configures the EHC parameter for the first DRB, which indicates that the packet header is not compressed, or the first device does not configure the EHC compression parameter 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 indicating that the packet header is not compressed for the first DRB, or the first device does not configure the EHC parameter for the first DRB, or the first device configures the EHC parameter indicating that the packet header is not compressed for the first DRB;

if the first device does not expect the compression end device to perform RoHC compression, the first device configures the RoHC parameter indicating that the packet header is not compressed for the first DRB, 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 maps with the 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 that the EHC parameter and the RoHC parameter can be configured for the first DRB according to the first information, if the first device does not expect the compression end device to perform EHC compression, the first device configures the EHC parameter indicating that the packet header is not compressed for the first DRB, or the first device does not configure the EHC parameter for the first DRB;

Even if it is determined that the EHC parameter and the RoHC parameter can be configured for the first DRB according to the first information, if the first device does not expect the compression end device to perform RoHC compression, the first device configures the RoHC parameter indicating that the packet header is not compressed for the first DRB, 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 maps only the ethernet non-IP packet corresponding to the PDU session, the first device configures the EHC parameter for the first DRB only, or the first device configures the EHC parameter and a RoHC parameter indicating that the packet header is not compressed for the first DRB;

if there are an ethernet IP packet and an ethernet non-IP packet in the ethernet payload corresponding to the PDU session, and the first DRB maps the ethernet IP packet in the ethernet payload corresponding to the PDU session, the first device configures the EHC parameter and the RoHC parameter for the first DRB;

if there are an ethernet IP packet and an ethernet non-IP packet in the ethernet payload corresponding to the PDU session, and the first DRB maps the ethernet non-IP packet in the ethernet payload corresponding to the PDU session, the first device configures the EHC parameter only for the first DRB, or the first device configures the EHC parameter and a RoHC parameter indicating that the packet header is not compressed for the first DRB;

If the compression end device does not support simultaneous compression of RoHC and EHC, the first device configures only 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 that the packet header is not compressed.

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

the second information includes at least one of:

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

Optionally, the packet parsing 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 comprises an IP packet header or not;

whether the Ethernet packet corresponding to the PDU session comprises an IP packet.

Optionally, the compression end device obtains the data packet analysis information by analyzing the higher layer packet received on the first DRB.

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

The compression end equipment analyzes the high-layer packet received on the first DRB to determine whether at least one of an Ethernet packet, an IP packet, an Ethernet IP packet and an Ethernet non-IP packet exists in a packet format and/or an Ethernet load corresponding to the PDU session;

if the compression end device supports compression of the IP packet and EHC, the compression end device analyzes the higher layer packet received on the first DRB to determine whether at least one of an Ethernet packet, an IP packet, an Ethernet IP packet and an Ethernet non-IP packet exists in the Ethernet load corresponding to the PDU session;

if the compression end device supports the compression of the Ethernet IP packet, the compression end device analyzes the high-layer packet received on the first DRB to determine whether at least one of the Ethernet packet, the IP packet, the Ethernet IP packet and the Ethernet non-IP packet exists in the Ethernet load corresponding to the PDU session;

if the compression information only includes the EHC parameter configured for the first DRB, the compression end device only analyzes the ethernet packet header of the higher layer packet received on the first DRB, to determine whether there is an ethernet packet in the ethernet load corresponding to the PDU session;

if the compression information includes the EHC parameter and the RoHC parameter configured for the first DRB, the compression end device analyzes an ethernet packet header and an IP packet header of a higher layer packet received on the first DRB, and determines whether at least one of an ethernet packet, an IP packet, an ethernet IP packet, and an ethernet non-IP packet exists in an ethernet load corresponding to the PDU session.

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

if the compression information comprises the RoHC parameter and the EHC parameter, the compression end device compresses the Ethernet IP packet 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 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 compresses only one of an IP header and an ethernet header;

if the compression information includes two of the RoHC parameter and the EHC parameter and is configured to be non-compressed, the compression end device does not compress the IP header and the ethernet header;

if the unconfigured compression information comprises two of the RoHC parameter and the EHC parameter, the compression end device does not compress the IP header and the ethernet header;

if the Ethernet load corresponding to the PDU session has a non-IP packet and an IP packet, the compression end device compresses an Ethernet IP packet with an Ethernet frame header and an IP packet header, and compresses the Ethernet non-IP packet with the Ethernet frame header;

if the Ethernet load corresponding to the PDU session has an IP packet, the compression end device compresses the IP packet header and the Ethernet frame header respectively; specifically, the Ethernet IP packet is compressed into an Ethernet frame header and an IP packet header, and the Ethernet non-IP packet is compressed into an Ethernet frame header;

If the Ethernet load corresponding to the PDU session does not have an IP packet, the compression end device only compresses the Ethernet frame head of the Ethernet packet;

if the Ethernet load corresponding to the PDU session has non-IP and IP packet headers, the compression end device compresses the IP packet header and the Ethernet frame header respectively; specifically, the Ethernet IP packet is compressed into an Ethernet frame header and an IP packet header, and the Ethernet non-IP packet is compressed into an Ethernet frame header;

if the Ethernet load corresponding to the PDU session has an IP packet header, the compression end device compresses the Ethernet frame header and the IP packet header respectively; specifically, the Ethernet IP packet is compressed into an Ethernet frame header and an IP packet header, and the Ethernet non-IP packet is compressed into an Ethernet frame header;

if the Ethernet load corresponding to the PDU session does not have the IP packet header, 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 header may also be referred to as an ethernet header.

Optionally, in an embodiment of the present application, the compression end device determines whether to compress the ethernet 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 with the PDU session of the ethernet type, that is, effectively configures compression parameters for the PDU session of the ethernet type, thereby avoiding the problem that IP packet header compression is not supported, and simultaneously avoiding the problem that unnecessary resource efficiency of the air interface is reduced.

The wireless communication method 200 according to the embodiment of the present application is described in detail below by way of specific embodiments.

In embodiment 1, a first device is taken as a gNB, and a compression end device is taken as a UE for illustration. Specifically, as shown in fig. 3, the gNB may configure the UE with compressed configuration information including EHC parameters and/or RoHC parameters configured for DRB 1 mapped with the ethernet type PDU session.

Optionally, in embodiment 1, as shown in fig. 3, the gNB receives 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 compression of Ethernet IP packets, whether the UE supports compression of IP packets, and whether the UE supports compression of both the RoHC and the EHC.

Optionally, in embodiment 1, as shown in fig. 3, the gNB receives indication information 2 sent by the SMF entity, where the indication information 2 is used to indicate whether a packet type corresponding to the PDU session is an ethernet non-IP type or an ethernet IP type, or the indication information 2 is used to indicate whether an ethernet IP packet and/or an ethernet non-IP packet exists in an 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 the DRB 1 according to the first information. Wherein the first information may be at least one of: the content indicated by the indication information 1 and the content indicated by the indication information 2.

Specifically, in example 1,

1) The gNB maps the Ethernet type PDU session described above to DRB 1.

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

Alternatively, in embodiment 1, as shown in fig. 3, the UE receives the compressed configuration information configured for DRB 1.

Alternatively, 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:

UE compression capability), the compression configuration information (whether RoHC parameters for IP compression are configured or not), packet parsing information (the compression end parses the received higher layer packet, determines whether the packet type is ethernet non-IP type or ethernet IP type), and indication information 3 (from the gNB or core network device, such as SMF entity).

Optionally, in embodiment 1, if the UE supports EHC and IP compression, or ethernet IP compression, the UE parses a higher layer packet each time the UE receives the higher layer packet, and determines whether at least one of the following exists in the ethernet load corresponding to the PDU session of the ethernet type: ethernet packets, IP packets, ethernet non-IP packets, ethernet IP packets.

Optionally, in embodiment 1, the indication information 3 is used to indicate whether at least one of the following exists in the ethernet packet type and/or the ethernet payload corresponding to the PDU session of the ethernet type: ethernet packets, IP packets, ethernet non-IP packets, ethernet IP packets.

Further, if it is determined that an IP packet exists in the ethernet payload corresponding to the PDU session of the ethernet type or is an ethernet IP packet, 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 taken as a gNB, and the compression end device is taken as a UE for illustration. Specifically, as shown in fig. 4, the gNB may configure the UE with compressed configuration information including EHC parameters and/or RoHC parameters configured for DRB 1 mapped with the ethernet type PDU session.

Optionally, in embodiment 2, as shown in fig. 4, the gNB receives 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 learns, from the PCF entity or the DN entity, indication information c, where the indication information c is used to indicate whether a packet type corresponding to the PDU session is an Ethernet non-IP type or an Ethernet IP type, or the indication information c is used to indicate whether an Ethernet IP packet and/or an Ethernet non-IP packet (non-IP over ethernet+ip over Ethernet) exists in an Ethernet load corresponding to the PDU session.

In embodiment 2, as shown in fig. 4, the gNB receives indication information b sent by the SMF entity, where the indication information b is used to indicate whether a 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 an ethernet IP packet and/or an ethernet non-IP packet exists in an 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 the DRB 1 according to the first information. Wherein the first information may be at least one of: the content indicated by the indication information a, and the content indicated by the indication information b, the packet format information (gNB self-parses the received higher layer packet to determine the packet format information, where the packet format information includes whether the packet type is an ethernet non-IP type, an ethernet IP type, or whether an ethernet IP packet exists).

Specifically, in example 2,

1) Even though the PDU session is of the Ethernet type, the gNB maps the Ethernet IP packet and the Ethernet non-IP packet to different DRBs, respectively. Accordingly, the EHC parameters and RoHC parameters are configured only for DRBs that map ethernet IP packets, and for DRBs that map ethernet non-IP packets.

Optionally, the gNB does not further distinguish whether the ethernet packet is loaded with IP packets when mapping DRBs and PDU sessions. Accordingly, the gNB determines the UE compression capability support according to the indication information a, and/or configures EHC parameters and RoHC parameters for the DRB 1 after determining that there are IP and ethernet non-IP packets according to the indication information b, otherwise configures EHC parameters only for the DRB 1.

For example, UE capability does not support IP compression, or IP ethernet compression, EHC parameters are configured only for DRB 1.

For example, the UE capability supports IP compression or supports compression of IP over Ethernet, and the indication information b indicates that an Ethernet IP packet and/or an Ethernet non-IP packet exists in the Ethernet payload corresponding to the PDU session, and then EHC parameters and RoHC parameters are configured for DRB 1.

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

Alternatively, in embodiment 2, as shown in fig. 4, the UE receives the compressed configuration information configured for DRB 1. The PDU session map as configured for ethernet type is in DRB 1.

Alternatively, 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:

UE compression capability, the compression configuration information (whether RoHC parameters for IP compression are configured or not), packet parsing information (the compression end parses the received higher layer packet, determines whether the packet type is ethernet non-IP type or ethernet IP type), and indicates information d (from the gNB or core network device, such as SMF entity).

Optionally, in embodiment 2, if the UE supports EHC and IP compression, or ethernet IP compression, the UE parses a higher layer packet each time the UE receives the higher layer packet, and determines whether at least one of the following exists in the ethernet load corresponding to the PDU session of the ethernet type: ethernet packets, IP packets, ethernet non-IP packets, ethernet IP packets.

Optionally, in embodiment 2, the indication information d is used to indicate whether at least one of the following exists in the packet type and/or the ethernet payload corresponding to the PDU session of the ethernet type: ethernet packets, IP packets, ethernet non-IP packets, ethernet IP packets.

Further, if it is determined that an IP packet header or an ethernet IP packet exists in the ethernet payload 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 compresses only the ethernet header.

Alternatively, in embodiment 2, if only the EHC parameter is configured for DRB 1 and no RoHC parameter is configured, the UE only parses the Ethernet packet header and does not further parse the IP packet header. If the RoCH parameter and the EHC parameter are configured for the DRB 1, the UE analyzes the Ethernet packet header and the IP packet header respectively every time a high-layer packet is received, and determines whether the IP packet header exists or not. If the packet exists, the Ethernet packet header and the IP packet header are respectively compressed, otherwise, only the Ethernet packet header is compressed.

The method embodiments of the present application are described in detail above with reference to fig. 2 to 4, and the apparatus embodiments of the present application are described in detail below with reference to fig. 5 to 9, it being understood that the apparatus embodiments and the method embodiments correspond to each other, and similar descriptions may refer to the method embodiments.

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

a processing unit 310, configured to configure EHC parameters and/or RoHC parameters for a first DRB, where the first DRB has an ethernet type PDU session mapped thereon;

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

Optionally, the processing unit 310 is specifically configured to:

the EHC parameter and/or the RoHC parameter are configured for the first DRB according to first information, wherein,

the first information includes at least one of:

the compression capability of the compression end 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 comprises an Ethernet IP packet and/or an Ethernet non-IP packet, packet analysis information, first indication information from the compression end device and second indication information from the second device.

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

ethernet IP packets, ethernet non-IP packets.

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

the compression capability of the compression end device, the packet type corresponding to the PDU session, and whether an Ethernet IP packet and/or an Ethernet non-IP packet exists in the Ethernet load corresponding to the PDU session.

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

and the packet type corresponding to the PDU session, and whether an Ethernet IP packet and/or an Ethernet non-IP packet exist 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, 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 higher layer packet:

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

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 compression of the IP packet, or the compression end device does not support compression of the ethernet IP packet, the processing unit 310 configures the EHC parameter only for the first DRB, or the processing unit 310 configures the EHC parameter and the RoHC parameter indicating that the packet 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 310 configures the EHC parameter and the RoHC parameter 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 compression of ethernet non-IP packets, or the compression end device supports compression of ethernet IP packets, the processing unit 310 configures the RoHC parameter for the first DRB, or the processing unit 310 configures the RoHC parameter and the EHC parameter indicating that the packet header is not compressed for the first DRB;

if the compression end device supports compression of an IP packet or the compression end device supports compression of an ethernet IP packet, and there is an ethernet IP packet and/or an ethernet non-IP packet in the ethernet load corresponding to the PDU session, the processing 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 ethernet IP packets and ethernet non-IP packets, the processing unit 310 configures the EHC parameter and the RoHC parameter for the first DRB;

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 that indicates that the packet header is not compressed, or the processing unit 310 does not configure the EHC compression parameter for the first DRB;

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 that indicates that the packet 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 for the first DRB that indicates 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 310 configures the RoHC parameter indicating that the packet header is not compressed for the first DRB, 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 maps with the 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 maps only the ethernet non-IP packet corresponding to the PDU session, the processing unit 310 configures the EHC parameter for only the first DRB, or the processing unit 310 configures the EHC parameter and the RoHC parameter indicating that the packet header is not compressed for the first DRB;

If there are an ethernet IP packet and an ethernet non-IP packet in the ethernet payload corresponding to the PDU session, and the first DRB maps the ethernet IP packet in the ethernet payload corresponding to the PDU session, the processing unit 310 configures the EHC parameter and the RoHC parameter for the first DRB;

if there are an ethernet IP packet and an ethernet non-IP packet in the ethernet payload corresponding to the PDU session, and the first DRB maps with the ethernet non-IP packet in the ethernet payload corresponding to the PDU session, the processing unit 310 configures the EHC parameter only for the first DRB, or the processing unit 310 configures the EHC parameter and the RoHC parameter indicating that the packet header is not compressed for the first DRB;

if the compression end device does not support RoHC and EHC simultaneous compression, the processing unit 310 configures only 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 or the RoHC parameter indicates that the packet 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.

Alternatively, in some embodiments, the communication unit may be a communication interface or transceiver, or an input/output interface of a communication chip or a system on a chip. The 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 a terminal device in the embodiment of the method of the present application, and the foregoing and other operations and/or functions of each unit in the wireless communication device 300 are respectively for implementing the corresponding flow of the first device in the method 200 shown in fig. 2, and are not repeated herein for brevity.

Fig. 6 shows a schematic block diagram of a wireless communication device 400 according to an embodiment of the application. The wireless communication device 400 is a compression end device, as shown in fig. 6, the wireless communication device 400 includes:

a communication unit 410, configured to receive compression information sent by a first device, where the compression information includes EHC parameters and/or RoHC parameters configured for a first DRB, and the first DRB has an ethernet type PDU session mapped thereon;

the processing unit 420 is configured to compress ethernet headers of data packets 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 second information, where the second information includes at least one of the following:

Optionally, the processing unit 420 is further configured to obtain the packet parsing information by parsing a higher layer packet received on the first DRB.

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

the processing unit 420 analyzes the higher layer packet received on the first DRB to determine whether at least one of an ethernet packet, an IP packet, an ethernet IP packet, and an ethernet non-IP packet exists in the packet format and/or the ethernet load corresponding to the PDU session;

If the compression end device supports compression of the IP packet and EHC, the processing unit 420 determines whether at least one of an ethernet packet, an IP packet, an ethernet IP packet, and an ethernet non-IP packet exists in the ethernet load corresponding to the PDU session by parsing the higher layer packet received on the first DRB;

if the compression end device supports compression of the ethernet IP packet, the processing unit 420 determines whether at least one of the ethernet packet, the IP packet, the ethernet IP packet, and the ethernet non-IP packet exists in the ethernet load corresponding to the PDU session by analyzing the higher layer packet received on the first DRB;

if the compression information only includes the EHC parameter configured for the first DRB, the processing unit 420 only analyzes the ethernet packet header of the higher layer packet received on the first DRB, to determine whether there is an ethernet packet in the ethernet payload corresponding to the PDU session;

if the compression information includes the EHC parameter and the RoHC parameter configured for the first DRB, the processing unit 420 determines whether at least one of an ethernet packet, an IP packet, an ethernet IP packet, and an ethernet non-IP packet exists in the ethernet payload corresponding to the PDU session by parsing the ethernet packet header and the IP packet header of the higher layer packet received on the first DRB.

Optionally, the processing unit 420 compresses ethernet headers of data packets 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 an ethernet IP header and an 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 an IP header and an ethernet 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 compresses only one of the IP header and the ethernet header;

if the compression information includes two of the RoHC parameter and the EHC parameter and is configured to be non-compressed, the processing unit 420 does not compress the IP header and the ethernet 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 header;

if there are non-IP packets and IP packets in the ethernet payload corresponding to the PDU session, the processing unit 420 compresses ethernet IP packets with ethernet headers and IP headers, and compresses ethernet non-IP packets with ethernet headers;

if there is an IP packet in the ethernet payload 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 payload corresponding to the PDU session, the processing unit 420 only compresses the ethernet header of the ethernet packet;

if there are non-IP and IP headers in the ethernet payload corresponding to the PDU session, the processing unit 420 compresses the IP header and the ethernet header, respectively;

if there is an IP header in the ethernet payload corresponding to the PDU session, the processing unit 420 compresses the ethernet frame header and the IP header, respectively;

if the ethernet payload corresponding to the PDU session does not include an IP header, 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 header and/or the IP packet header according to the second information.

Optionally, the first device is an access network device.

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

It should be understood that the wireless communication device 400 according to the embodiment of the present application may correspond to a network device in the embodiment of the method of the present application, and the foregoing and other operations and/or functions of each unit in the wireless communication device 400 are respectively for implementing the corresponding flow of the compression end device in the method 200 shown in fig. 2, and are not repeated herein for brevity.

Fig. 7 is a schematic block diagram of a communication device 500 according to an embodiment of the present application. The communication device 500 shown in fig. 7 comprises a processor 510, from which the processor 510 may call and run a computer program to implement the method in an embodiment of the application.

Optionally, as shown in fig. 7, the communication device 500 may further comprise a memory 520. Wherein the processor 510 may call and run a computer program from the memory 520 to implement the method in an embodiment of the application.

Wherein the memory 520 may be a separate device from the processor 510 or may be integrated into 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, and in particular, may send information or data to other devices, or receive information or data sent by other devices.

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

Optionally, the communication device 500 may be specifically a first device in the embodiment of the present application, and the communication device 500 may implement a corresponding flow implemented by the first device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the communication device 500 may be specifically a compression end device in the embodiment of the present application, and the communication device 500 may implement a corresponding flow implemented by the compression end device in each method in the embodiment of the present application, which is not described herein for brevity.

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

Optionally, as shown in fig. 8, the apparatus 600 may further comprise a memory 620. Wherein the processor 610 may call and run a computer program from the memory 620 to implement the method in an embodiment of the application.

The memory 620 may be a separate device from the processor 610 or may be integrated into the processor 610.

Optionally, the apparatus 600 may further comprise an input interface 630. The processor 610 may control the input interface 630 to communicate with other devices or chips, and in particular, may acquire information or data sent by the other devices or chips.

Optionally, the apparatus 600 may further comprise an output interface 640. Wherein the processor 610 may control the output interface 640 to communicate with other devices or chips, and in particular, may output information or data to other devices or chips.

Optionally, the apparatus may be applied to the first device in the embodiment of the present application, and the apparatus may implement a corresponding flow implemented by the first device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the apparatus may be applied to the compression end device in the embodiment of the present application, and the apparatus may implement a corresponding flow implemented by the compression end device in each method of the embodiment of the present application, which is not described herein for brevity.

Alternatively, the device according to the embodiment of the present application may be a chip. For example, a system-on-chip or a system-on-chip, etc.

Fig. 9 is a schematic block diagram of a communication system 700 provided in 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.

The terminal device 710 may be configured to implement the corresponding function implemented by the compression end device in the above method, and the network device 720 may be configured to implement the corresponding function implemented by the compression end device or the first device in the above method, which are not described herein for brevity.

It should be appreciated that the processor of an embodiment of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be embodied directly in the execution of a hardware decoding processor, or in the execution of a combination of hardware and software modules in a decoding processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

It will be appreciated that the memory in embodiments of the application may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (Double Data Rate SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and Direct RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that the above memory is illustrative but not restrictive, and for example, the memory in the embodiments of the present application may be Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), direct RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

The embodiment of the application also provides a computer readable storage medium for storing a computer program.

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 a computer to execute a corresponding flow implemented by the first device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the computer readable storage medium may be applied to the compression end device in the embodiment of the present application, and the computer program causes a computer to execute a corresponding flow implemented by the compression end device in each method of the embodiment of the present application, which is not described herein for brevity.

The embodiment of the application also provides a computer program product comprising computer program instructions.

Optionally, the computer program product may be applied to the first device in the embodiment of the present application, and the computer program instructions cause the computer to execute a corresponding flow implemented by the first device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the computer program product may 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 flow implemented by the compression end device in each method of the embodiment of the present application, which is not described herein for brevity.

The embodiment of the application also provides a computer program.

Optionally, the computer program may be applied to the first device in the embodiment of the present application, and when the computer program runs on a computer, the computer is caused to execute a corresponding flow implemented by the first device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the computer program may be applied to the compression end device in the embodiment of the present application, and when the computer program runs on a computer, the computer is caused to execute a corresponding flow implemented by the compression end device in each method in the embodiment of the present application, which is not described herein for brevity.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

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

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. For such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of wireless communication, comprising:

the method comprises the steps that first equipment configures Ethernet header compression EHC parameters and/or robustness packet header compression RoHC parameters for a first Data Radio Bearer (DRB), wherein an Ethernet type Protocol Data Unit (PDU) session is mapped on the first DRB;

the first device sends compression information to a compression end device, wherein the compression information comprises the EHC parameter and/or the RoHC parameter;

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.

2. The method of claim 1, wherein the first device configures EHC parameters and/or RoHC parameters for the first DRB, comprising:

The first information includes at least one of:

the compression capability of the compression end device, the packet type corresponding to the PDU session, whether the Ethernet load corresponding to the PDU session is an Internet Protocol (IP) packet, whether the PDU session comprises an Ethernet IP packet and/or an Ethernet non-IP packet, packet analysis information, first indication information from the compression end device and second indication information from the second device.

3. The method of claim 2, wherein the compression capability of the compression end device comprises at least one of:

whether the compression end device supports EHC, whether the compression end device supports RoHC, whether the compression end device supports compression of Ethernet IP packets, whether the compression end device supports compression of IP packets, and whether the compression end device supports EHC and RoHC compression or not.

4. A method according to claim 2 or 3, wherein the packet type corresponding to the PDU session comprises at least one of:

ethernet IP packets, ethernet non-IP packets.

5. The method according to any one of claims 2 to 4, wherein the first indication information is used to indicate at least one of:

And the compression capability of the compression end equipment, the packet type corresponding to the PDU session, and whether an Ethernet IP packet and/or an Ethernet non-IP packet exists in the Ethernet load corresponding to the PDU session.

6. The method according to any one of claims 2 to 5, wherein the second indication information is used to indicate at least one of:

and the packet type corresponding to the PDU session, and whether an Ethernet IP packet and/or an Ethernet non-IP packet exists in the Ethernet load corresponding to the PDU session.

7. The method according to any one of claims 2 to 6, wherein the content indicated by the second indication information is acquired by the second device from a third device.

8. The method of 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 a terminal device.

9. The method according to any one of claims 2 to 8, further comprising:

the first device obtains at least one of the following by parsing the received higher layer packet:

10. The method according to any of claims 2 to 9, wherein the first device configures the EHC parameter and/or the RoHC parameter for the first DRB according to first information, comprising one of:

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 an IP packet, or the compression end device does not support compression of an ethernet non-IP packet, or the compression end device supports compression of an ethernet IP packet, the first device configures the RoHC parameter for the first DRB, or the first device configures the RoHC parameter and the EHC parameter indicating that a packet header is not compressed 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, the first device configures the EHC parameter indicating that the packet header is not compressed for the first DRB, or the first device does not configure the EHC compression 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 maps only the ethernet non-IP packet corresponding to the PDU session, the first device configures the EHC parameter for the first DRB only, or the first device configures the EHC parameter and the RoHC parameter indicating that the packet header is not compressed for the first DRB;

if there are an ethernet IP packet and an ethernet non-IP packet in the ethernet load corresponding to the PDU session, and the first DRB maps the ethernet IP packet 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 there are an ethernet IP packet and an ethernet non-IP packet in the ethernet payload corresponding to the PDU session, and the first DRB maps the ethernet non-IP packet in the ethernet payload corresponding to the PDU session, 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 packet header is not compressed for the first DRB;

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

11. The method according to any of claims 1 to 10, wherein the first device is an access network device.

12. A method of wireless communication, comprising:

the method comprises the steps that compression end equipment receives compression information sent by first equipment, wherein the compression information comprises Ethernet header compression EHC parameters and/or robustness packet header compression RoHC parameters configured for a first Data Radio Bearer (DRB), and an Ethernet type Protocol Data Unit (PDU) session is mapped on the first DRB;

if the PDU session corresponds to an Ethernet IP packet and an Ethernet non-IP packet, mapping or configuring the Ethernet IP packet and the Ethernet non-IP packet to different DRB;

13. The method according to claim 12, wherein the method further comprises:

The compression end device determines a packet format corresponding to the PDU session according to the second information, wherein,

the second information includes at least one of:

14. The method of claim 13, wherein the compression capability of the compression end device comprises at least one of:

whether the compression end device supports EHC, whether the compression end device supports RoHC, whether the compression end device supports compression of Ethernet IP packets, whether the compression end device supports compression of Internet protocol IP packets, and whether the compression end device supports both EHC and RoHC compression or not.

15. The method according to claim 13 or 14, wherein the packet parsing information and/or the third indication information comprises at least one of:

and whether the Ethernet packet corresponding to the PDU session comprises an IP packet or not.

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

and the compression end equipment acquires the data packet analysis information by analyzing the high-layer packet received on the first DRB.

17. The method according to any one of claims 13 to 16, wherein the compression end device determines, according to the second information, a packet format corresponding to the PDU session, including one of the following:

if the compression end device supports the compression of the Ethernet IP packet, the compression end device analyzes the higher layer packet received on the first DRB to determine whether at least one of the Ethernet packet, the IP packet, the Ethernet IP packet and the Ethernet non-IP packet exists in the Ethernet load corresponding to the PDU session;

If the compression information only includes the EHC parameter configured for the first DRB, the compression end device only analyzes an ethernet packet header of a higher layer packet received on the first DRB, and determines whether an ethernet packet exists in an ethernet load corresponding to the PDU session;

18. The method according to any one of claims 12 to 17, wherein the compression end device compresses, according to the compression information, an ethernet header of a data packet corresponding to the PDU session, including one of the following:

if the compression information includes the RoHC parameter and the EHC parameter, the compression end device compresses an ethernet IP header and an 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 an IP header and an ethernet header;

if the compression information includes two of the RoHC parameters and the EHC parameters and is configured to be non-compressed, the compression end device does not compress an IP header and an ethernet header;

if the unconfigured compression information comprises two of the RoHC parameters and the EHC parameters, the compression end device does not compress an IP header and an ethernet header;

if the Ethernet load corresponding to the PDU session has a non-IP packet and an IP packet, the compression end device compresses an Ethernet IP packet into an Ethernet frame header and an IP packet header, and compresses the Ethernet non-IP packet into the Ethernet frame header;

if the Ethernet load corresponding to the PDU session has an IP packet, the compression end device compresses an IP packet header and an Ethernet frame header respectively;

if the Ethernet load corresponding to the PDU session has a non-IP header and an IP header, the compression end device compresses the IP header and the Ethernet frame header respectively;

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

and if the Ethernet load corresponding to the PDU session does not have the IP packet header, the compression end equipment only compresses the Ethernet frame header of the Ethernet packet.

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

and the compression end equipment determines whether to compress the Ethernet frame header and/or the IP packet header according to the second information.

20. The method according to any of claims 12 to 19, wherein the first device is an access network device.

21. A wireless communication device, wherein the wireless communication device is a first device, the wireless communication device comprising:

a processing unit, configured to configure an ethernet header compression EHC parameter and/or a robustness header compression RoHC parameter for a first data radio bearer DRB, where an ethernet type protocol data unit PDU session is mapped on the first DRB;

a communication unit, configured to send compression information to a compression end device, where the compression information includes the EHC parameter and/or the RoHC parameter;

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.

22. The device according to claim 21, characterized in that said processing unit is specifically configured to:

configuring the EHC parameter and/or the RoHC parameter for the first DRB according to first information, wherein,

the first information includes at least one of:

23. The apparatus of claim 22, wherein the compression capability of the compression end apparatus comprises at least one of:

24. The apparatus according to claim 22 or 23, wherein the packet type corresponding to the PDU session comprises at least one of:

Ethernet IP packets, ethernet non-IP packets.

25. The apparatus according to any one of claims 22 to 24, wherein the first indication information is used to indicate at least one of:

26. The apparatus according to any one of claims 22 to 25, wherein the second indication information is used to indicate at least one of:

27. The apparatus according to any one of claims 22 to 26, wherein the content indicated by the second indication information is acquired by the second apparatus from a third apparatus.

28. The device of claim 27, 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 a terminal device.

29. The apparatus according to any one of claims 22 to 28, wherein the processing unit is further configured to obtain at least one of the following by parsing the received higher layer packet:

30. The apparatus according to any of claims 22 to 29, wherein the processing unit configures the EHC parameter and/or the RoHC parameter for the first DRB according to first information, including one of:

if the compression end device supports ethernet packet header compression, the processing unit configures the EHC parameter and the RoHC parameter for the first DRB;

if the compression end device does not support compression of the IP packet, or the compression end device does not support compression of the ethernet IP packet, the processing unit configures the EHC parameter only for the first DRB, or the processing unit configures the EHC parameter and the RoHC parameter indicating that the packet header is not compressed for the first DRB;

if the compression end device supports compression of an IP packet or the compression end device supports compression of an ethernet IP packet, the processing unit configures the EHC parameter and the RoHC parameter 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 an IP packet, or the compression end device does not support compression of an ethernet non-IP packet, or the compression end device supports compression of an ethernet IP packet, the processing unit configures the RoHC parameter for the first DRB, or the processing unit configures the RoHC parameter and the EHC parameter indicating that a packet header is not compressed for the first DRB;

If the compression end device supports compression of an IP packet or the compression end device supports compression of an ethernet IP packet, and an ethernet IP packet and/or an ethernet non-IP packet exists in an 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 an IP packet or the compression end device supports compression of an ethernet IP packet, and the PDU session corresponds to the ethernet IP packet and an ethernet non-IP packet, the processing unit configures the EHC parameter and the RoHC parameter for the first DRB;

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 packet header is not compressed for the first DRB, or the processing unit does not configure the EHC compression parameter 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 packet header is not compressed for the first DRB, or the processing unit does not configure the EHC parameter for the first DRB, or the processing unit configures the EHC parameter indicating that the packet 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 configures the RoHC parameter indicating that the packet header is not compressed for the first DRB, or the processing unit 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 the ethernet IP packet corresponding to the PDU session, the processing unit 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 maps only the ethernet non-IP packet corresponding to the PDU session, the processing unit configures the EHC parameter for the first DRB only, or the processing unit configures the EHC parameter and the RoHC parameter indicating that the packet header is not compressed for the first DRB;

if there are an ethernet IP packet and an ethernet non-IP packet in the ethernet load corresponding to the PDU session, and the first DRB maps the ethernet IP packet 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 there are an ethernet IP packet and an ethernet non-IP packet in the ethernet payload corresponding to the PDU session, and the first DRB maps the ethernet non-IP packet in the ethernet payload corresponding to the PDU session, the processing unit configures the EHC parameter only for the first DRB, or the processing unit configures the EHC parameter and the RoHC parameter indicating that the packet header is not compressed for the first DRB;

If the compression end device does not support simultaneous compression of RoHC and EHC, 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 packet header is not compressed.

31. The apparatus according to any of claims 21 to 30, wherein the first apparatus is an access network apparatus.

32. A wireless communication device, wherein the wireless communication device is a compression end device, the wireless communication device comprising:

a communication unit, configured to receive compression information sent by a first device, where the compression information includes an ethernet header compression EHC parameter and/or a robustness header compression RoHC parameter configured for a first data radio bearer DRB, and an ethernet type protocol data unit PDU session is mapped on the first DRB;

and the processing unit is used for compressing the Ethernet frame header of the data packet corresponding to the PDU session according to the compression information.

33. The apparatus of claim 32, wherein the processing unit is further configured to determine a packet format corresponding to the PDU session based on the second information, wherein,

the second information includes at least one of:

34. The apparatus of claim 33, wherein the compression capability of the compression end apparatus comprises at least one of:

35. The apparatus according to claim 33 or 34, wherein the packet parsing information and/or the third indication information comprises at least one of:

36. The apparatus of any of claims 33 to 35, wherein the processing unit is further configured to obtain the packet parsing information by parsing higher layer packets received on the first DRB.

37. The apparatus according to any one of claims 33 to 36, wherein the processing unit determines, from the second information, a packet format corresponding to the PDU session, comprising one of:

the processing unit analyzes the higher layer packet received on the first DRB to determine whether at least one of an Ethernet packet, an IP packet, an Ethernet IP packet and an Ethernet non-IP packet exists in a packet format and/or an Ethernet load corresponding to the PDU session;

if the compression end device supports compression of the IP packet and EHC, the processing unit analyzes the higher layer packet received on the first DRB, and determines whether at least one of an ethernet packet, an IP packet, an ethernet IP packet, and an ethernet non-IP packet exists in the ethernet load corresponding to the PDU session;

if the compression end device supports compression of the ethernet IP packet, the processing unit analyzes the higher layer packet received on the first DRB, to determine whether at least one of the ethernet packet, the IP packet, the ethernet IP packet, and the ethernet non-IP packet exists in the ethernet load corresponding to the PDU session;

If the compression information only includes the EHC parameter configured for the first DRB, the processing unit only analyzes an ethernet packet header of a higher layer packet received on the first DRB, and determines whether an ethernet packet exists in an ethernet load corresponding to the PDU session;

if the compression information includes the EHC parameter and the RoHC parameter configured for the first DRB, the processing unit analyzes an ethernet packet header and an IP packet header of a higher layer packet received on the first DRB, and determines whether at least one of an ethernet packet, an IP packet, an ethernet IP packet, and an ethernet non-IP packet exists in an ethernet load corresponding to the PDU session.

38. The apparatus according to any one of claims 32 to 37, wherein the processing unit compresses ethernet headers of data packets corresponding to the PDU session according to the compression information, comprising one of:

if the compression information includes the RoHC parameter and the EHC parameter, the processing unit compresses an ethernet IP header and an 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 an IP header and an ethernet 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 compresses only one of an IP header and an ethernet header;

if the compression information includes two of the RoHC parameter and the EHC parameter and is configured to be non-compressed, the processing unit does not compress an IP header and an ethernet header;

if the unconfigured compression information comprises two of the RoHC parameters and the EHC parameters, the processing unit does not compress the IP header and the ethernet header;

if the Ethernet load corresponding to the PDU session has a non-IP packet and an IP packet, the processing unit compresses an Ethernet IP packet into an Ethernet frame header and an IP packet header, and compresses the Ethernet frame header into the Ethernet non-IP packet;

if the Ethernet load corresponding to the PDU session has an IP packet, the processing unit compresses an IP packet header and an Ethernet frame header respectively;

if the Ethernet load corresponding to the PDU session does not have an IP packet, the processing unit only compresses the Ethernet frame head of the Ethernet packet;

if the Ethernet load corresponding to the PDU session has a non-IP packet header and an IP packet header, the processing unit compresses the IP packet header and the Ethernet frame header respectively;

if the Ethernet load corresponding to the PDU session has an IP packet header, the processing unit compresses the Ethernet frame header and the IP packet header respectively;

And if the Ethernet load corresponding to the PDU session does not have the IP packet header, the processing unit only compresses the Ethernet frame header of the Ethernet packet.

39. The apparatus according to any one of claims 33 to 38, wherein the processing unit is further configured to determine whether to compress an ethernet header and/or an IP header based on the second information.

40. The apparatus of any one of claims 32 to 39, wherein the first apparatus is an access network apparatus.

41. A terminal device, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and run the computer program stored in the memory, to perform the method according to any of claims 1 to 11.

42. A network device, comprising: a processor and a memory for storing a computer program, the processor being for invoking and running the computer program stored in the memory, performing the method of any of claims 12 to 20.

43. An apparatus, comprising: a processor for calling and running a computer program from a memory, causing a device in which the apparatus is installed to perform the method of any one of claims 1 to 11.

44. An apparatus, comprising: a processor for calling and running a computer program from a memory, causing a device in which the apparatus is installed to perform the method of any of claims 12 to 20.

45. A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 11.

46. A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 12 to 20.