WO2020062176A1 - Wireless communication method, terminal device, and network device - Google Patents

Abstract

Embodiments of the present application provide a wireless communication method, a terminal device, and an access network device. The access network device can configure a plurality of header compression configurations for one DRB, such that when data packet having Ethernet frame structures carrying and not carrying a VLAN header, header compression or decompression can be performed according to the plurality of header compression configurations, thereby improving the header compression efficiency. The method comprises: a terminal device receives first configuration information sent by an access network device, the first configuration information being used for configuring a plurality of header compression configurations for a first DRB; the terminal device performs header compression or decompression on the first DRB according to the first configuration information.

Description

Wireless communication method, terminal equipment and access network equipment Technical field

Embodiments of the present application relate to the field of communications, and more specifically, to a wireless communication method, a terminal device, and an access network device.

Background technique

In a Long Term Evolution (LTE) system, the protocol data unit (PDU) session type is the Internet Protocol (IP) type, but in the fifth generation of mobile communication technology, it is a new air interface. In the (5-Generation New Radio, 5G NR) system, not only IP types are supported, but also Ethernet (Ethernet) types are introduced. For the PDU layer, when the PDU Session type is IPv4 or IPv6 or IPv4v6, the PDU session corresponds to IPv4 packets and / or IPv6 packets; when the PDU Session type is Ethernet, the PDU session corresponds to It is an Ethernet frame structure (frames).

In the LTE and NR systems, a public network system is generally deployed, that is, a public land network based on a Public Land Mobile Network (Public Land Mobile Network, PLMN). At the same time, in some scenarios, such as in offices, homes, factories, etc., in order to enable more secure and effective management, the local network is usually deployed by local users or administrators. Only authorized and accessible users have access to Local network permissions.

In the scenario where the public network system and the local network coexist, when the PDU session is Ethernet frames, the Ethernet PDU may carry the Virtual Local Area Network (VLAN) header, or it may not carry the VLAN header, and the corresponding Ethernet frame Structure is different. In the header compression process, the header compression algorithms used by these two types of PDUs are different. Therefore, how to realize the compression of Ethernet PDU headers with and without the VLAN header is an urgent problem.

Summary of the Invention

The embodiments of the present application provide a wireless communication method, a terminal device, and an access network device. The access network device may configure multiple head compression configurations for a data radio bearer (DRB), so that in one DRB When mapping data packets with an Ethernet frame structure that carries a VLAN header and no VLAN header at the same time, header compression or decompression can be performed based on multiple header compression configurations to improve header compression efficiency.

In a first aspect, a wireless communication method is provided. The method includes:

The terminal device receives first configuration information sent by the access network device, where the first configuration information is used to configure multiple header compression configurations for the first DRB;

The terminal device performs header compression or decompression on the first DRB according to the first configuration information.

Optionally, in the embodiment of the present application, the terminal device may also receive the first configuration information sent by the core network device.

In a second aspect, a wireless communication method is provided. The method includes:

The access network device sends first configuration information to the terminal device, where the first configuration information is used to configure multiple header compression configurations for the first DRB.

It should be noted that the method can be applied in a scenario of a public network system, and / or a local network scenario, and / or a scenario in which a public network system and a local network coexist.

Optionally, in the embodiment of the present application, the core network device may also send the first configuration information to the terminal device.

According to a third aspect, a terminal device is provided to execute the method in the first aspect or the implementations thereof.

Specifically, the terminal device includes a functional module for executing the method in the above-mentioned first aspect or each implementation manner thereof.

According to a fourth aspect, an access network device is provided, which is configured to execute the method in the foregoing second aspect or each implementation manner thereof.

Specifically, the access network device includes a functional module for executing the method in the second aspect or the implementation manners thereof.

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

According to a sixth aspect, an access network device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the second aspect or the implementations thereof.

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

Specifically, the chip includes a processor for invoking and running a computer program from a memory, so that a device installed with the chip executes any one of the first aspect to the second aspect described above or implementations thereof. method.

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

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

In a tenth aspect, a computer program is provided that, when run on a computer, causes the computer to execute the method in any one of the first to second aspects described above or in its implementations.

Through the above technical solution, the access network device can configure multiple header compression configurations for the first DRB, so that when the first DRB is simultaneously mapped with a data packet of an Ethernet frame structure including a VLAN header and a VLAN header You can perform header compression or decompression based on multiple header compression configurations to improve header compression efficiency.

BRIEF DESCRIPTION OF THE DRAWINGS

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

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

FIG. 3 is a schematic diagram of a V domain according to an embodiment of the present application.

FIG. 4 is a schematic diagram of another V-domain according to an embodiment of the present application.

FIG. 5 is a schematic diagram of still another V-domain according to an embodiment of the present application.

FIG. 6 is a schematic diagram of still another V-domain according to an embodiment of the present application.

FIG. 7 is a schematic flowchart of another wireless communication method according to an embodiment of the present application.

FIG. 8 is a schematic block diagram of a terminal device according to an embodiment of the present application.

FIG. 9 is a schematic block diagram of an access network device according to an embodiment of the present application.

FIG. 10 is a schematic block diagram of a communication device according to an embodiment of the present application.

FIG. 11 is a schematic block diagram of a chip according to an embodiment of the present application.

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

detailed description

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, but not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by a person of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

The technical solutions of the embodiments of the present application can be applied to various communication systems, for example, a Global System for Mobile (GSM) system, a Code Division Multiple Access (CDMA) system, and a Wideband Code Division Multiple Access (Wideband Code Division Multiple Access) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system or 5G system, etc.

Exemplarily, the communication system 100 applied in the embodiment of the present application is shown in FIG. 1. The communication system 100 may include a terminal device 110, and the terminal device 110 may be located within the coverage of the access network device 120. As the "terminal equipment" used herein includes, but is not limited to, connection via wired lines, such as via Public Switched Telephone Networks (PSTN), Digital Subscriber Line (DSL), digital cable, direct cable connection ; And / or another data connection / network; and / or via a wireless interface, such as for cellular networks, Wireless Local Area Networks (WLAN), digital television networks such as DVB-H networks, satellite networks, AM- FM broadcast transmitter; and / or another terminal device configured to receive / transmit communication signals; and / or Internet of Things (IoT) devices. A terminal device configured to communicate through a wireless interface may be referred to as a “wireless communication terminal”, a “wireless terminal”, or a “mobile terminal”. Examples of mobile terminals include, but are not limited to, satellite or cellular phones; personal communications systems (PCS) terminals that can combine cellular radiotelephones with data processing, facsimile, and data communications capabilities; can include radiotelephones, pagers, Internet / internal PDA with network access, web browser, notepad, calendar, and / or Global Positioning System (GPS) receiver; and conventional laptop and / or palm-type receivers or others including radiotelephone transceivers Electronic device. A terminal device can refer to an access terminal, user equipment (User Equipment), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or User device. The access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Processing (PDA), and wireless communication. Functional handheld devices, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in 5G networks, or terminal devices in future evolved PLMNs, etc.

The communication system 100 may include an access network device 120, and the access network device 120 may be a device that communicates with a terminal device 110 (or a communication terminal or a terminal). The access network device 120 may provide communication coverage for a specific geographic area, and may communicate with terminal devices located within the coverage area. Optionally, the access network device 120 may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, or a base station (NodeB, NB) in a WCDMA system, or may be an evolved type in an LTE system. Base station (Evolutionary Node B, eNB or eNodeB), or a wireless controller in a Cloud Radio Access Network (CRAN), or the network device may be a mobile switching center, relay station, access point, or vehicle equipment , Wearables, hubs, switches, bridges, routers, network-side devices in 5G networks, or network devices in public land mobile networks (PLMN) that are evolving in the future.

The wireless communication system 100 further includes a core network device 130 that communicates with an access network device. Optionally, the core network device 130 may be a 5G core network device, such as an access and mobility management function (AMF), which is responsible for access and mobility management, and has user authentication and handover. , Location updates, and more. For another example, the Session Management Function (SMF) is responsible for session management, including the establishment, modification, and release of packet data unit (PDU) sessions. As another example, the user plane function (UPF) is responsible for forwarding user data. The core network device may be a core network device of an LTE system or other systems.

Optionally, the 5G system or the 5G network may also be referred to as a New Radio (NR) system or an NR network.

In the embodiment of the present application, an access network device provides services for a cell, and a terminal device communicates with a network device through a transmission resource (for example, a frequency domain resource or a spectrum resource) used by the cell, and the cell may be a network device The corresponding cell (for example, a base station) can belong to a macro base station or a small cell (small cell). Here, the small cell can include: urban cell, micro cell, pico cell (Pico cells), femto cells (Femto cells), etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

It should be understood that the Packet Data Convergence Protocol (PDCP) protocol introduces header compression and decompression functions to support different data radio bearers (DRB), according to the configured header compression profile. Use different header compression and header compression parameters. PDCP uses Robust Information Header Compression (ROHC) protocol. The supported header compression protocols and profiles are shown in Table 1 below. Specifically, as shown in Table 1 below, the compression objects of different header compression configurations may be Real-time Transport Protocol (RTP), IP, User Datagram Protocol (UDP), and encapsulated security payload ( At least one of Encapsulating Security Payload (ESP) and No compression (Compression). The compression strategy can be a series of RFC (Request For Comments) files as shown in Table 1 below.

Table 1

Configuration ID	Compression Object (Usage)	Compression Strategy (Reference)
0x0000	No compression	RFC 5795
0x0001	RTP / UDP / IP	RFC 3095, RFC 4815
0x0002	UDP / IP	RFC 3095, RFC 4815
0x0003	ESP / IP	RFC 3095, RFC 4815
0x0004	IP	RFC3843, RFC4815
0x0006	TCP / IP	RFC 6846
0x0101	RTP / UDP / IP	RFC 5225
0x0102	UDP / IP	RFC 5225
0x0103	ESP / IP	RFC 5225
0x0104	IP	RFC 5225

Optionally, the embodiments of the present application may be used in a scenario in which a public land network or a local network or a public network system and a local network coexist.

The public land network may be a PLMN-based public land network.

The local network can also be called a local area network or a private network. This local network is usually deployed in office scenarios, home scenarios, and factories to achieve more effective and secure management. Usually, there are local users or administrators to deploy the local network. Generally, authorized and accessible users have the right to access the local network.

The local network may or may not be managed or administered by a public land network.

Alternatively, the local network may use an unlicensed frequency band for communication, or may share the licensed frequency band with a public land network.

Alternatively, the local network may be a network belonging to the 3GPP category. The core network of the local network may be a core network of NR or LTE, and the local network may access the core network through an NR access network, an LTE access network, or wireless fidelity (Wifi).

Optionally, in the embodiment of the present application, the public land network and the local network may share the core network, and the access network is independent; or, the access network may be shared, and the core network is independent; or, the access network may be shared Access network and core network; or, access network and core network are not shared.

Optionally, in the embodiment of the present application, multiple or multiple local networks may share the core network and the access network is independent; or, the access network may be shared and the core network is independent; or they may be shared The access network and the core network; or both the access network and the core network are not shared.

It should be noted that, in a public network system, and / or a local network scenario, and / or a scenario in which the public network system and the local network coexist, when the PDU session is Ethernet frames, the Ethernet PDU may carry a VLAN header, or it may Does not carry the VLAN header, the corresponding Ethernet frame structure is different. In the header compression process, the header compression algorithms used by these two types of PDUs are different. However, at this stage, no distinction is made in this scenario. Therefore, compression of Ethernet PDUs that carry a VLAN header and those that do not. Based on the above problems, this application proposes a method for Ethernet frame header compression configuration.

It should be understood that, in the embodiment of the present application, the network-side entity is not limited to the access network device, and may also be a core network device. Correspondingly, the processing layer of the terminal device and the network device may be a PDCP layer, or may be another entity or layer.

It should also be understood that, in the embodiments of the present application, a PDCP device may also be referred to as a PDCP layer, and an RLC device may also be referred to as an RLC layer.

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

S210: The terminal device receives first configuration information sent by the access network device, where the first configuration information is used to configure multiple header compression configurations for the first DRB;

S220. The terminal device performs header compression or decompression on the first DRB according to the first configuration information.

Optionally, in the embodiment of the present application, the terminal device may also receive the first configuration information sent by the core network device, that is, the core network device may directly configure the first configuration information for the terminal device, and the core network device For example, it can be an AMF device or a UPF device. Similarly, the following descriptions about the access network equipment are also applicable to the core network equipment. The following uses the terminal device to receive the first configuration information from the access network device as an example for detailed description.

It should be noted that the first DRB may be any DRB in the terminal device, that is, any DRB in the terminal device satisfies the embodiments of the present application.

Optionally, in the embodiment of the present application, the multiple header compression configurations include at least two of the following header compression configurations:

Header compression configuration for Ethernet frame structure including VLAN header,

Header compression configuration for Ethernet frame structure without VLAN header,

Header compression configuration for the Ethernet frame structure header,

Header compression configuration for the Ethernet frame structure service data unit (SDU).

Optionally, in the embodiment of the present application, header compression and data domain configuration of the Ethernet frame structure may be performed separately.

For example, the access network device configures the header of the Ethernet frame structure for the first DRB without performing header compression configuration, or configures the first DRB with or without the Ethernet structure header and the data domain to perform header compression configuration separately, Alternatively, the first DRB is configured to support or not support the header compression configuration of the Ethernet structure, or the first DRB is configured to support or not support the header compression configuration of the Ethernet structure including the VLAN header. The terminal device performs header compression or decompression on the header and data domain of the Ethernet frame structure or header compression or decompression of the entire Ethernet frame structure according to the above configuration.

For another example, the access network device configures a header compression configuration for the first DRB of the Ethernet frame structure and a data domain, or does not configure a header compression configuration for the Ethernet structure header for the first DRB, or, A header compression configuration for the Ethernet structure is configured for the first DRB, or a header compression configuration for the Ethernet structure containing a VLAN header is supported or not supported for the first DRB. The terminal device performs header compression or decompression on the header and data domain of the Ethernet frame structure or header compression or decompression of the entire Ethernet frame structure according to the above configuration.

Optionally, in the embodiment of the present application, the terminal device maps multiple data packets in the first DRB, and the multiple data packets include a data packet having an Ethernet frame structure with a VLAN header and a data packet without a VLAN header. Ethernet frame structure of data packets. That is, the terminal device maps the Ethernet frame structure including the VLAN header and the Ethernet frame structure not including the VLAN header in the first DRB. At this time, the terminal device can separately Header compression or decompression with the data field.

Optionally, in the embodiment of the present application, the terminal device maps multiple data packets in the first DRB, and the multiple data packets include a data packet having an Ethernet frame structure with a VLAN header and a data packet without a VLAN header. Ethernet frame structure of data packets. That is, the terminal device maps the Ethernet frame structure including the VLAN header and the Ethernet frame structure not including the VLAN header in the first DRB. At this time, the terminal device can perform the header of the entire Ethernet frame structure. Compression or decompression.

Optionally, the terminal device may determine, according to the VLAN indication, a data packet with an Ethernet frame structure having a VLAN header and / or a data packet with an Ethernet frame structure having no VLAN header.

The VLAN indication is indicated by the access network device, or the VLAN indication is obtained by the terminal device through data flow information interaction between layers.

Specifically, in the embodiment of the present application, it may be a PDCP device of the terminal device, or a PDU device of the terminal device, or an RLC device of the terminal device, or a newly-added sublayer pair in the 5G network is mapped to the first Multiple packets of DRB are header compressed or decompressed.

In the following, the PDCP device of the terminal device performs header compression or decompression on multiple data packets mapped to the first DRB as an example for specific description.

Optionally, as an example 1, the PDCP device of the terminal device adopts a manner that the header of the Ethernet frame structure does not perform header compression, and performs header compression or decompression on the multiple data packets. It should be noted that, at this time, the compression method of the data domain is not limited.

Optionally, as an example two, the PDCP device of the terminal device performs header compression or decompression of the Ethernet frame structure data packet including the VLAN header according to the VLAN instruction, and Header compression or decompression of an Ethernet frame structure data packet that does not include a VLAN header is performed on a data packet that does not have a VLAN header.

Further, in the second example, the first PDU configured by the terminal device to carry the first PDCP device carries first indication information, and the first indication information is used to indicate to the opposite end of the first PDCP device that the first PDU is adopted. The header compression method including the VLAN header is used for header compression or the header compression method is used for the header compression without including the VLAN header.

It should be noted that the first PDCP device may be any PDCP device serving the first DRB in the terminal device, that is, any PDCP device serving the first DRB in the terminal device satisfies the requirement. Examples. Similarly, the first PDU may be any one of the first PDCP devices.

Optionally, in the second example, the first indication information is carried in a reserved bit position in the first PDU; or the first indication information is carried in a newly added bit field in the first PDU. .

For example, as shown in FIG. 3, the terminal device defines a V domain occupying 1 bit, and the V domain is located in one of the three R bits reserved in the first PDU. In the V domain, a definition of 1 means that The first PDU is header compressed using a header compression method including a VLAN header. A definition of 0 indicates that the first PDU is header compressed using a header compression method that does not include a VLAN header. The opposite end of the first PDCP device can learn the header compression mode of the first PDU according to the V domain, and then perform corresponding decompression.

As another example, as shown in FIG. 4, the terminal device adds a 10-octet V domain after the PDCP SN and before the data in the first PDU. In the V domain, a definition of 1 indicates that the first PDU uses a VLAN word The header compression method of the header performs header compression. A definition of 0 indicates that the first PDU uses the header compression method that does not include a VLAN header to perform header compression. The opposite end of the first PDCP device can learn the header compression mode of the first PDU according to the V domain, and then perform corresponding decompression.

It should be understood that in FIG. 3 and FIG. 4, the PDCP SN may refer to a PDCP sequence number (SN), Oct may refer to a unit byte length, and MAC may refer to Media Access Control (MAC). PDCP SN (cont.) Indicates continuous PDCP SN, and MAC-I (cont.) Indicates continuous MAC.

It should be noted that the opposite end of the first PDCP device may be a PDCP device located in an access network device.

Further, in the second example, the terminal device configures a first PDU of a first RLC device to carry first instruction information, where the first instruction information is used to indicate that a peer end of the first RLC device adopts the first PDU. The header compression method that includes a VLAN header is used for header compression or the header compression method that does not include a VLAN header is used for header compression.

Correspondingly, the opposite end of the first RLC device tells the corresponding PDCP device of the local entity whether the VLAN header compression is used or not.

It should be noted that the first RLC device may be any RLC device in the terminal device serving the first DRB, that is, any RLC device in the terminal device serving the first DRB satisfies the requirement. Examples. Similarly, the first PDU may be any PDU in the first RLC device.

Similarly, the first PDU of the first RLC device may also be added with the indication information indicating the compression mode of the first PDU of the first RLC device at the opposite end of the first RLC device as shown in FIG. 3 and FIG. 4. For the sake of brevity, I won't repeat them here.

Optionally, as an example three, the terminal device transmits a PDU that uses the header compression method including a VLAN header in the first PDCP device to perform header compression, and transmits the PDU that uses the header compression that does not include a VLAN header in the second PDCP device. Way to perform header compressed PDU.

It should be noted that, in the third example, the first PDCP device and the second PDCP device are configured by the access network device through RRC signaling.

Optionally, as an example four, the PDCP device of the terminal device uses a way of constructing a virtual VLAN to perform header compression or decompression on the data packet of the Ethernet frame structure without a VLAN header in the multiple data packets;

The PDCP device of the terminal device performs header compression or decompression on the data packet of the Ethernet frame structure having the VLAN header in the multiple data packets according to the VLAN mode.

It should be noted that at this time, the network side can be configured with only one header compression and decompression method and parameter including a VLAN subheader.

Further, in the fourth example, the terminal device configures the first PDPDU of the first PDCP device to carry first instruction information, and the first instruction information is used to indicate that the opposite end of the first PDCP device adopts the first PDU. The header compression method of the virtual VLAN header performs header compression or the header compression method without the virtual VLAN header performs header compression.

It should be noted that the first PDCP device may be any PDCP device serving the first DRB in the terminal device, that is, any PDCP device serving the first DRB in the terminal device satisfies the requirement. Examples. Similarly, the first PDU may be any one of the first PDCP devices.

Optionally, in the fourth example, the first indication information is carried in a reserved bit position in the first PDU; or the first indication information is carried in a newly added bit field in the first PDU. .

For example, as shown in FIG. 5, the terminal device defines a V domain occupying 1 bit. The V domain is located in one of the three R bits reserved in the first PDU. In the V domain, a definition of 1 means that The first PDU is header compressed by using a virtual VLAN header compression method. A definition of 0 indicates that the first PDU is header compressed without using a virtual VLAN header compression method. The opposite end of the first PDCP device can learn the header compression mode of the first PDU according to the V domain, and then perform corresponding decompression.

As another example, as shown in FIG. 6, the terminal device adds a 10-oct V domain after the PDCP SN and before the data in the first PDU. In the V domain, a definition of 1 indicates that the first PDU uses a virtual VLAN word. The header compression method of the header performs header compression. A definition of 0 indicates that the first PDU is header compression that does not use the virtual VLAN header header compression method. The opposite end of the first PDCP device can learn the header compression mode of the first PDU according to the V domain, and then perform corresponding decompression.

It should be understood that in FIG. 5 and FIG. 6, PDCP and SN may refer to a PDCP sequence number, and Oct may refer to a unit byte length.

It should be noted that when the peer end of the first PDCP performs decompression, the corresponding virtual VLAN information is removed. The opposite end of the first PDCP device may be a PDCP device located in an access network device.

Further, in the fourth example, the terminal device configures a first PDU of a first RLC device to carry first instruction information, where the first instruction information is used to indicate that a peer end of the first RLC device adopts the first PDU. The header compression method of the virtual VLAN header performs header compression or the header compression method without the virtual VLAN header performs header compression.

Correspondingly, the opposite end of the first RLC device tells the corresponding PDCP device of the local entity whether the VLAN header compression is used or not.

It should be noted that the first RLC device may be any RLC device in the terminal device serving the first DRB, that is, any RLC device in the terminal device serving the first DRB satisfies the requirement. Examples. Similarly, the first PDU may be any PDU in the first RLC device.

Similarly, the first PDU of the first RLC device may be added as shown in FIG. 5 and FIG. 6 to indicate whether the first PDU of the first RLC device at the opposite end of the first RLC device is a virtual VLAN. The indication information of the compression method is omitted here for brevity.

Optionally, in the embodiment of the present application, before the terminal device receives the first configuration information, the terminal device obtains first information through data flow information interaction between layers, where the first information includes mapping to the first The data packet ID, data packet arrangement order, data packet transmission time, whether the data packet includes a VLAN ID, the data packet corresponding QoS data flow (Flow), and the data packet corresponding QoS data flow VLAN At least one of the instructions.

Further, the terminal device sends the first information to the access network device, where the first information is used by the access network device or the core network device to determine the first configuration information, or

The terminal device sends the first information to the core network device, where the first information is used by the core network device to determine the first configuration information.

Optionally, in the embodiment of the present application, before the terminal device receives the first configuration information, the terminal device reports support capabilities for the overall header compression and decompression of the Ethernet frame structure, or separately reports Ethernet The header and data field header compression and decompression support capabilities are used to indicate whether the terminal device supports header compression of the Ethernet frame structure and / or whether it supports header compression of the Ethernet frame structure of the VLAN header.

It should be understood that the support capability reported by the terminal device is used to determine the first configuration information by an access network device or a core network device.

Therefore, in the embodiment of the present application, the access network device may configure multiple header compression configurations for the first DRB, so that the first DRB is mapped with an Ethernet frame structure including a VLAN header and not including a VLAN header. When a data packet is received, the terminal device can perform header compression or decompression based on various header compression configurations to improve header compression efficiency.

FIG. 7 is a schematic flowchart of a wireless communication method 300 according to an embodiment of the present application. As shown in FIG. 3, the method 300 may include the following content:

S310. The access network device sends first configuration information to the terminal device, where the first configuration information is used to configure multiple header compression configurations for the first DRB.

Optionally, in the embodiment of the present application, the core network device may also send the first configuration information, that is, the core network device may directly configure the first configuration information for the terminal device, and the core network device may be an AMF device, for example. , Or UPF device. Similarly, the following descriptions about the access network equipment are also applicable to the core network equipment. The following uses the access network device to send the first configuration information as an example for detailed description.

It should be noted that the first DRB may be any DRB in the terminal device, that is, any DRB in the terminal device satisfies the embodiments of the present application.

Optionally, in the embodiment of the present application, the multiple header compression configurations include at least two of the following header compression configurations:

Header compression configuration for Ethernet frame structure including VLAN header,

Header compression configuration for Ethernet frame structure without VLAN header,

Header compression configuration for the Ethernet frame structure header,

Header compression configuration for the Ethernet frame structure SDU.

Optionally, in the embodiment of the present application, the access network device maps multiple data packets in the first DRB. The multiple data packets include a data packet with an Ethernet frame structure having a VLAN header and no VLAN. A packet with an Ethernet frame structure at the beginning.

Optionally, the access network device determines, according to the VLAN indication, a data packet with an Ethernet frame structure having a VLAN header and / or a data packet with an Ethernet frame structure having no VLAN header in the plurality of data packets.

Optionally, the VLAN indication is indicated by the core network device, or the VLAN indication is obtained by the access network device through a terminal device report.

Specifically, in the embodiment of the present application, it may be a PDCP device of the access network device, or a PDU device of the access network device, or an RLC device of the access network device, or a newly-added sublayer in the 5G network. Header compression or decompression of a plurality of data packets mapped to the first DRB.

In the following, the PDCP device of the access network device performs header compression or decompression on the multiple data packets mapped to the first DRB as an example for detailed description.

Optionally, as an example 1, the PDCP device of the access network device uses the Ethernet frame structure header without header compression to perform header compression or decompression on the multiple data packets.

Optionally, as an example two, the PDCP device of the access network device performs header compression or decompression of the Ethernet frame structure data packet including the VLAN header according to the VLAN instruction. , And perform header compression or decompression of the Ethernet frame structure data packet without the VLAN header on the data packet of the Ethernet frame structure without the VLAN header.

Further, in the second example, the first PDU configured by the access network device to carry the first PDCP device carries first indication information, where the first indication information is used to indicate the first end of the first PDCP device to the first PDU. For header compression using a header compression method including a VLAN header or for header compression using a header compression method that does not include a VLAN header.

Further, in the second example, the first PDU of the first RLC device configured by the access network device to carry the first instruction information is used to indicate the opposite end of the first RLC device to the first PDU. For header compression using a header compression method including a VLAN header or for header compression using a header compression method that does not include a VLAN header.

Optionally, in the second example, the first indication information is carried in a reserved bit position in the first PDU; or the first indication information is carried in a newly added bit field in the first PDU. .

Optionally, as an example three, the PDCP device of the access network device uses a way of constructing a virtual VLAN to perform header compression or decompression on the data packet of the Ethernet frame structure without a VLAN header in the multiple data packets;

The PDCP device of the access network device performs header compression or decompression on the data packet of the Ethernet frame structure having the VLAN header in the multiple data packets according to the VLAN mode.

Further, in the third example, the first PDU configured by the access network device to carry the first PDCP device carries first instruction information, where the first instruction information is used to indicate the first end of the first PDCP device to the first PDU. Head compression using the virtual VLAN header compression method or head compression using the virtual VLAN header compression method.

Further, in the third example, the first PDU of the first RLC device configured by the access network device to carry the first instruction information is used to indicate the opposite end of the first RLC device to the first PDU. Head compression using the virtual VLAN header compression method or head compression using the virtual VLAN header compression method.

Optionally, in the third example, the first indication information is carried in a reserved bit position in the first PDU; or the first indication information is carried in a newly added bit field in the first PDU. .

Optionally, in the embodiment of the present application, before the access network device sends the first configuration information, the access network device determines the first configuration information according to the first information, and the first information includes a mapping to the first configuration information. Whether a VLAN identifier is included in a VLAN indication of multiple data packets of a DRB, a data packet arrangement order, a data packet transmission time, a data packet, a QoS data flow corresponding to the data packet, and a QoS data flow corresponding to the data packet At least one.

Optionally, the first information is reported by the terminal device, or the first information is indicated by a core network device.

Optionally, in the embodiment of the present application, the access network device receives the support for the head compression and decompression of the overall Ethernet frame structure reported by the terminal device, or receives the Ethernet report separately reported by the terminal device. The header and data field header compression and decompression support capabilities are used to indicate whether the terminal device supports header compression of the Ethernet frame structure and / or whether it supports header compression of the Ethernet frame structure of the VLAN header.

Optionally, in the embodiment of the present application, header compression and data domain configuration of the Ethernet frame structure may be performed separately. For specific configuration, you can refer to the support capability reporting method of the terminal device.

Optionally, in the embodiment of the present application, header compression configuration may be performed on the entirety of the Ethernet frame structure. For specific configuration, you can refer to the support capability reporting method of the terminal device.

For example, if the terminal device reports support for the overall header compression and decompression of the Ethernet frame structure, the header of the access network device that configures the Ethernet frame structure for the first DRB does not perform header compression configuration, or, Configure the first DRB to support or not support the Ethernet structure header and data domain to perform header compression configuration separately, or configure the first DRB to support or not support the Ethernet structure header compression configuration, or for the first DRB The configuration supports or does not support header compression configuration for Ethernet structures with VLAN headers. Correspondingly, the terminal device performs header compression or decompression on the header and data domain of the Ethernet frame structure or header compression or decompression of the entire Ethernet frame structure according to the above configuration.

As another example, if the terminal device separately reports support for header compression and decompression of the header and data domain of the Ethernet header, the access network device configures the header and data domain of the Ethernet frame structure for the first DRB separately. Header compression configuration, or not configuring a header compression configuration for the Ethernet structure header for the first DRB, or configuring a header compression configuration for the Ethernet structure for the first DRB, or configuring support for the first DRB or Header compression configuration for Ethernet structures with VLAN headers is not supported. Correspondingly, the terminal device performs header compression or decompression on the header and data domain of the Ethernet frame structure or header compression or decompression of the entire Ethernet frame structure according to the above configuration.

It should be understood that, for the steps in the wireless communication method 300, reference may be made to the corresponding steps in the wireless communication method 200. For brevity, details are not described herein again.

Therefore, in the embodiment of the present application, the access network device may configure multiple header compression configurations for the first DRB, so that the first DRB is mapped with an Ethernet frame structure including a VLAN header and not including a VLAN header. When a data packet is received, the terminal device can perform header compression or decompression based on various header compression configurations to improve header compression efficiency.

FIG. 8 shows a schematic block diagram of a terminal device 400 according to an embodiment of the present application. As shown in FIG. 8, the terminal device 400 includes:

A communication unit 410, configured to receive first configuration information sent by an access network device, where the first configuration information is used to configure multiple header compression configurations for the first DRB;

The processing unit 420 is configured to perform header compression or decompression on the first DRB according to the first configuration information.

Optionally, the multiple header compression configurations include at least two of the following header compression configurations:

Header compression configuration for Ethernet frame structure including virtual LAN VLAN header,

Header compression configuration for Ethernet frame structure without VLAN header,

Header compression configuration for the Ethernet frame structure header,

Header compression configuration for the Ethernet frame structure SDU.

Optionally, the processing unit 420 is further configured to:

Mapping a plurality of data packets in the first DRB, the plurality of data packets including a data packet of an Ethernet frame structure with a VLAN header and a data packet of an Ethernet frame structure without a VLAN header;

The PDCP device controlling the terminal device determines, according to the VLAN instruction, a data packet with an Ethernet frame structure with a VLAN header and / or a data packet with an Ethernet frame structure without a VLAN header.

Optionally, the VLAN indication is indicated by the access network device, or the VLAN indication is obtained by the terminal device through data flow information interaction between layers.

Optionally, the processing unit 420 is specifically configured to:

The PDCP device controlling the terminal device adopts a manner that the header of the Ethernet frame structure does not perform header compression, and performs header compression or decompression on the multiple data packets.

Optionally, the processing unit 420 is specifically configured to:

The PDCP device controlling the terminal device performs header compression or decompression of the Ethernet frame structure data packet including the VLAN header on the data packet of the Ethernet frame structure having the VLAN header according to the VLAN instruction, and The data packet of the Ethernet frame structure performs header compression or decompression of the Ethernet frame structure without the VLAN header.

Optionally, the processing unit 420 is further configured to:

The first PDU configured with the first PDCP device carries first instruction information, where the first instruction information is used to indicate that the opposite end of the first PDCP device uses the header compression method including a VLAN header to perform header compression. Or the header compression is performed by using a header compression method that does not include a VLAN header.

Optionally, the processing unit 420 is further configured to:

The first PDU configured with the first RLC device carries first instruction information, and the first instruction information is used to indicate that the peer end of the first RLC device uses the header compression method including a VLAN header to perform header compression. Or the header compression is performed by using a header compression method that does not include a VLAN header.

Optionally, the processing unit 420 is specifically configured to:

The PDCP device controlling the terminal device adopts a method of constructing a virtual VLAN to perform header compression or decompression on the data packets of the Ethernet frame structure without a VLAN header in the multiple data packets;

The PDCP device controlling the terminal device performs header compression or decompression of the data packet of the Ethernet frame structure having the VLAN header in the multiple data packets according to the VLAN mode.

Optionally, the processing unit 420 is further configured to:

The first PDU configured with the first PDCP device carries first instruction information, where the first instruction information is used to indicate that the peer end of the first PDCP device uses the header compression method of the virtual VLAN header to perform header compression. Or header compression that does not use the virtual VLAN header compression method.

Optionally, the processing unit 420 is further configured to:

The first PDU configured with the first RLC device carries first instruction information, where the first instruction information is used to indicate that the opposite end of the first RLC device is that the first PDU is header compressed using a virtual VLAN header header compression method. Or header compression that does not use the virtual VLAN header compression method.

Optionally, the first indication information is carried in a reserved bit position in the first PDU; or the first indication information is carried in a newly added bit field in the first PDU.

Optionally, before the communication unit 410 receives the first configuration information,

The processing unit 420 is further configured to obtain first information through data flow information interaction between layers, where the first information includes a data packet identifier, a data packet arrangement order, and a data packet corresponding to a plurality of data packets mapped to the first DRB. Transmission time, whether the data packet includes at least one of a VLAN identifier, a QoS data flow corresponding to the data packet, and a VLAN indication of the QoS data flow corresponding to the data packet;

The communication unit 410 is further configured to send the first information to the access network device, where the first information is used by the access network device or the core network device to determine the first configuration information; or

The communication unit 410 is further configured to send the first information to a core network device, where the first information is used by the core network device to determine the first configuration information.

Optionally, before the communication unit 410 receives the first configuration information, the communication unit 410 is further configured to report support capabilities for header compression and decompression of the overall Ethernet frame structure, or report the Ethernet header and The data field header compression and decompression support capabilities are used to indicate whether the terminal device supports header compression of the Ethernet frame structure and / or whether it supports header compression of the Ethernet frame structure of the VLAN header.

It should be understood that the terminal device 400 according to the embodiment of the present application may correspond to the terminal device in the method embodiment of the present application, and the above and other operations and / or functions of each unit in the terminal device 400 are respectively for implementing the method shown in FIG. 2. The corresponding processes of the terminal equipment in 200 are not repeated here for brevity.

FIG. 9 shows a schematic block diagram of an access network device 500 according to an embodiment of the present application. As shown in FIG. 9, the access network device 500 includes:

The communication unit 510 is configured to send first configuration information to the terminal device, where the first configuration information is used to configure multiple header compression configurations for the first DRB.

Optionally, the multiple header compression configurations include at least two of the following header compression configurations:

Header compression configuration for Ethernet frame structure including VLAN header,

Header compression configuration for Ethernet frame structure without VLAN header,

Header compression configuration for the Ethernet frame structure header,

Header compression configuration for the Ethernet frame structure SDU.

Optionally, the access network device 500 further includes:

A processing unit 520, configured to map a plurality of data packets in the first DRB, the plurality of data packets including a data packet having an Ethernet frame structure with a VLAN header and a data packet having an Ethernet frame structure without a VLAN header ;

The processing unit 520 is further configured to control a PDCP device of the access network device to determine, according to a VLAN instruction, a data packet with an Ethernet frame structure having a VLAN header in the multiple data packets and / or an Ethernet without a VLAN header. Frame structured packets.

Optionally, the VLAN indication is indicated by the core network device, or the VLAN indication is obtained by the access network device through a terminal device report.

Optionally, the processing unit 520 is further configured to:

The PDCP device controlling the access network device adopts a manner that the header of the Ethernet frame structure does not perform header compression, and performs header compression or decompression on the multiple data packets.

Optionally, the processing unit 520 is further configured to:

The PDCP device controlling the access network device performs compression or decompression of the Ethernet frame structure including the VLAN header on the data packet of the Ethernet frame structure having the VLAN header according to the VLAN instruction, and performs no compression on the Ethernet frame structure including the VLAN header. The data packet of the Ethernet frame structure of the header performs header compression or decompression of the Ethernet frame structure without the VLAN header.

Optionally, the processing unit 520 is further configured to:

The first PDU configured with the first PDCP device carries first instruction information, where the first instruction information is used to indicate that the opposite end of the first PDCP device uses the header compression method including a VLAN header to perform header compression. Or use header compression without the VLAN header.

Optionally, the processing unit 520 is further configured to:

The first PDU configured with the first RLC device carries first instruction information, and the first instruction information is used to indicate that the peer end of the first RLC device uses the header compression method including a VLAN header to perform header compression. Or the header compression is performed by using a header compression method that does not include a VLAN header.

Optionally, the processing unit 520 is further configured to:

The PDCP device controlling the access network device adopts a method of constructing a virtual VLAN to perform header compression or decompression on the data packet of the Ethernet frame structure without a VLAN header in the multiple data packets;

The PDCP device controlling the access network device performs header compression or decompression on the data packet of the Ethernet frame structure having the VLAN header in the multiple data packets according to the VLAN mode.

Optionally, the processing unit 520 is further configured to:

The first PDU configured with the first PDCP device carries first instruction information, where the first instruction information is used to indicate that the peer end of the first PDCP device uses the header compression method of the virtual VLAN header to perform header compression. Or header compression that does not use the virtual VLAN header compression method.

Optionally, the processing unit 520 is further configured to:

The first PDU configured with the first RLC device carries first instruction information, where the first instruction information is used to indicate that the opposite end of the first RLC device is that the first PDU is header compressed using a virtual VLAN header header compression method. Or header compression that does not use the virtual VLAN header compression method.

Optionally, the first indication information is carried in a reserved bit position in the first PDU; or the first indication information is carried in a newly added bit field in the first PDU.

Optionally, before the communication unit 510 sends the first configuration information, the processing unit 520 is further configured to:

The first configuration information is determined according to the first information, and the first information includes a data packet identifier, a data packet arrangement order, a data packet transmission time, a data packet, and a data packet corresponding to a plurality of data packets mapped to the first DRB. Whether the VLAN indication of the QoS data flow and the QoS data flow corresponding to the data packet includes at least one of the VLAN identifiers.

Optionally, the first information is reported by the terminal device, or the first information is indicated by a core network device.

Optionally, before the communication unit 510 sends the first configuration information,

The communication unit 510 is further configured to receive the support for the header compression and decompression of the overall Ethernet frame structure reported by the terminal device, and to indicate whether the terminal device supports the header compression and / or the VLAN of the Ethernet frame structure. Header compression of the Ethernet frame structure of the header;

The processing unit 520 is further configured to configure the header of the Ethernet frame structure for the first DRB without performing head compression configuration, or configure the first DRB to support or not support the header configuration of the Ethernet structure header and the data domain respectively. Alternatively, the first DRB is configured to support or not support the header compression configuration of the Ethernet structure, or the first DRB is configured to support or not support the header compression configuration of the Ethernet structure including the VLAN header.

Optionally, before the communication unit 510 sends the first configuration information,

The communication unit 510 is further configured to receive support for the header compression and decompression of the Ethernet header and the data domain reported by the terminal device, respectively, and to indicate whether the terminal device supports the header compression of the Ethernet frame structure and / or whether Supports header compression for Ethernet frame structure with VLAN header;

The processing unit 520 is further configured to configure the header and data fields of the Ethernet frame structure for the first DRB to perform header compression configuration separately, or not to configure the header compression configuration for the Ethernet structure header for the first DRB, or, The first DRB configuration is directed to a head compression configuration of an Ethernet structure, or the first DRB configuration supports or does not support a head compression configuration of an Ethernet structure including a VLAN header.

It should be understood that the access network device 500 according to the embodiment of the present application may correspond to the access network device in the method embodiment of the present application, and the above and other operations and / or functions of each unit in the access network device 500 are respectively The corresponding process of the access network device in the method 300 shown in FIG. 7 is implemented. For brevity, details are not described herein again.

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

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

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

Optionally, as shown in FIG. 10, the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, and specifically, may send information or data to other devices, or receive other Information or data sent by the device.

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

Optionally, the communication device 600 may specifically be an access network device according to the embodiment of the present application, and the communication device 600 may implement a corresponding process implemented by the access network device in each method of the embodiment of the present application. For simplicity, in This will not be repeated here.

Optionally, the communication device 600 may specifically be a mobile terminal / terminal device in the embodiment of the present application, and the communication device 600 may implement the corresponding process implemented by the mobile terminal / terminal device in each method in the embodiments of the present application. , Will not repeat them here.

FIG. 11 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 700 shown in FIG. 11 includes a processor 710, and the processor 710 may call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 11, the chip 700 may further include a memory 720. The processor 710 may call and run a computer program from the memory 720 to implement the method in the embodiment of the present application.

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

Optionally, the chip 700 may further include an input interface 730. The processor 710 may control the input interface 730 to communicate with other devices or chips. Specifically, the processor 710 may obtain information or data sent by the other devices or chips.

Optionally, the chip 700 may further include an output interface 740. The processor 710 may control the output interface 740 to communicate with other devices or chips. Specifically, the processor 710 may output information or data to the other devices or chips.

Optionally, the chip can be applied to the access network device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the access network device in each method of the embodiment of the present application. To repeat.

Optionally, the chip can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the chip can implement the corresponding process implemented by the mobile terminal / terminal device in each method of the embodiments of the present application. For simplicity, here No longer.

It should be understood that the chip mentioned in the embodiments of the present application may also be referred to as a system-level chip, a system chip, a chip system or a system-on-chip.

FIG. 12 is a schematic block diagram of a communication system 800 according to an embodiment of the present application. As shown in FIG. 12, the communication system 800 includes a terminal device 810 and an access network device 820.

The terminal device 810 may be used to implement the corresponding function implemented by the terminal device in the foregoing method, and the access network device 820 may be used to implement the corresponding function implemented by the access network device in the foregoing method. For simplicity, in This will not be repeated here.

It should be understood that the processor in the embodiment of the present application may be an integrated circuit chip and has a signal processing capability. In the implementation process, each step of the foregoing method embodiment may be completed by using an integrated logic circuit of hardware in a processor or an instruction in a form of software. The above processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (Field, Programmable Gate Array, FPGA), or other Programming logic devices, discrete gate or transistor logic devices, discrete hardware components. Various methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed. 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 combination with the embodiments of the present application may be directly implemented by a hardware decoding processor, or may be performed by using a combination of hardware and software modules in the decoding processor. The software module may be located in a mature storage medium such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, and the like. The storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the foregoing method in combination with its hardware.

It can be understood that the memory in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), and an electronic memory. Erase programmable read-only memory (EPROM, EEPROM) or flash memory. The volatile memory may be Random Access Memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (Synchlink DRAM, SLDRAM ) And direct memory bus random access memory (Direct Rambus RAM, DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

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

An embodiment of the present application further provides a computer-readable storage medium for storing a computer program.

Optionally, the computer-readable storage medium may be applied to an access network device in the embodiments of the present application, and the computer program causes a computer to execute a corresponding process implemented by the access network device in each method in the embodiments of the present application. Concise, I won't repeat them here.

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

An embodiment of the present application further provides a computer program product, including computer program instructions.

Optionally, the computer program product can be applied to an access network device in the embodiment of the present application, and the computer program instruction causes a computer to execute a corresponding process implemented by the access network device in each method in the embodiment of the present application, for the sake of simplicity , Will not repeat them here.

Optionally, the computer program product can be applied to a mobile terminal / terminal device in the embodiments of the present application, and the computer program instructions cause the computer to execute a corresponding process implemented by the mobile terminal / terminal device in each method in the embodiments of the present application, For brevity, I will not repeat them here.

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

Optionally, the computer program may be applied to an access network device in the embodiment of the present application, and when the computer program is run on a computer, the computer is caused to execute a corresponding method implemented by the access network device in each method in the embodiment of the present application. For the sake of brevity, we will not repeat them here.

Optionally, the computer program may be applied to a mobile terminal / terminal device in the embodiment of the present application. When the computer program is run on a computer, the computer executes each method in the embodiment of the application by the mobile terminal / terminal device. The corresponding processes are not repeated here for brevity.

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

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments, and are not repeated here.

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

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objective of the solution of this embodiment.

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

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

The above is only a specific implementation of this application, but the scope of protection of this application is not limited to this. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in this application. It should be covered by the protection scope of this application. Therefore, the protection scope of this application shall be subject to the protection scope of the claims.

Claims (70)

1. A wireless communication method, comprising:

   The terminal device receives first configuration information sent by the access network device, where the first configuration information is used to configure multiple header compression configurations for the first data radio bearer DRB;

   The terminal device performs header compression or decompression on the first DRB according to the first configuration information.
2. The method according to claim 1, wherein the plurality of header compression configurations include at least two of the following header compression configurations:

   Header compression configuration for Ethernet frame structure including virtual LAN VLAN header,

   Header compression configuration for Ethernet frame structure without VLAN header,

   Header compression configuration for the Ethernet frame structure header,

   Header compression configuration of the Ethernet frame structure service data unit SDU.
3. The method according to claim 2, further comprising:

   The terminal device maps multiple data packets in the first DRB, the multiple data packets include a data packet with an Ethernet frame structure with a VLAN header and a data packet with an Ethernet frame structure without a VLAN header ;

   The PDCP device of the terminal device's packet data convergence protocol determines, according to the VLAN indication, a data packet with an Ethernet frame structure having a VLAN header and / or data with an Ethernet frame structure without a VLAN header in the plurality of data packets. package.
4. The method according to claim 3, wherein the VLAN indication is indicated by the access network device, or the VLAN indication is obtained by the terminal device through data flow information interaction performed between layers.
5. The method according to claim 3 or 4, wherein the terminal device performs header compression or decompression on the first DRB according to the first configuration information, comprising:

   The PDCP device of the terminal device adopts a manner that the header of the Ethernet frame structure does not perform header compression, and performs header compression or decompression on the multiple data packets.
6. The method according to claim 3 or 4, wherein the terminal device performs header compression or decompression on the first DRB according to the first configuration information, comprising:

   The PDCP device of the terminal device performs header compression or decompression of the Ethernet frame structure data packet including the VLAN header on the data packet of the Ethernet frame structure having the VLAN header according to the VLAN instruction, and the data packet without the VLAN header. The data packet of the Ethernet frame structure performs header compression or decompression of the Ethernet frame structure without the VLAN header.
7. The method according to claim 6, further comprising:

   The terminal device configures a first protocol data unit PDU of the first PDCP device to carry first instruction information, where the first instruction information is used to indicate that a peer end of the first PDCP device adopts a VLAN including a VLAN. The header compression method performs header compression or the header compression method does not include a VLAN header.
8. The method according to claim 6, further comprising:

   A first PDU configured by the terminal device to configure a first radio link control RLC device carries first instruction information, where the first instruction information is used to indicate that the first end of the first RLC device is configured to include the first PDU. The header compression method of the VLAN header performs header compression or the header compression method does not include the VLAN header.
9. The method according to claim 3 or 4, wherein the terminal device performs header compression or decompression on the first DRB according to the first configuration information, comprising:

   The PDCP device of the terminal device adopts a method of constructing a virtual VLAN to perform header compression or decompression on the data packet of the Ethernet frame structure without the VLAN header in the multiple data packets;

   The PDCP device of the terminal device performs header compression or decompression on a data packet with an Ethernet frame structure having a VLAN header in the multiple data packets in a VLAN manner.
10. The method according to claim 9, further comprising:

    The terminal device configures a first PDU of a first PDCP device to carry first instruction information, where the first instruction information is used to indicate that the first end of the first PDCP device is a virtual PDU header using a virtual VLAN header. The header compression method performs header compression or the header compression method does not use a virtual VLAN header to perform header compression.
11. The method according to claim 9, further comprising:

    A first PDU configured by the terminal device to configure a first radio link control RLC device carries first instruction information, where the first instruction information is used to indicate that a peer end of the first RLC device uses virtual information The header compression method of the VLAN header performs header compression or the header compression method of the virtual VLAN header is not used.
12. The method according to claim 7, 8, 10 or 11, wherein:

    The first indication information is carried at a reserved bit position in the first PDU; or

    The first indication information is carried in a newly added bit field in the first PDU.
13. The method according to any one of claims 1 to 12, wherein before the terminal device receives the first configuration information, the method further comprises:

    The terminal device obtains first information through data flow information interaction between layers, where the first information includes a data packet identifier, a data packet arrangement sequence, and a data packet transmission corresponding to a plurality of data packets mapped to the first DRB. Time, whether the data packet includes at least one of a VLAN identifier, a QoS data flow corresponding to the data packet, and a VLAN indication of the QoS data flow corresponding to the data packet;

    Sending, by the terminal device, the first information to the access network device, where the first information is used by the access network device or the core network device to determine the first configuration information; or

    The terminal device sends the first information to a core network device, where the first information is used by the core network device to determine the first configuration information.
14. The method according to any one of claims 1 to 13, wherein before the terminal device receives the first configuration information, the method further comprises:

    The terminal device reports support capabilities for header compression and decompression of the overall Ethernet frame structure, or reports support capabilities for header compression and decompression of the Ethernet header and data domain, respectively, for indicating whether the terminal device Supports header compression of the Ethernet frame structure and / or whether it supports header compression of the Ethernet frame structure of the VLAN header.
15. A wireless communication method, comprising:

    The access network device sends first configuration information to the terminal device, where the first configuration information is used to configure multiple header compression configurations for the first data radio bearer DRB.
16. The method according to claim 15, wherein the plurality of header compression configurations include at least two of the following header compression configurations:

    Header compression configuration for Ethernet frame structure including virtual LAN VLAN header,

    Header compression configuration for Ethernet frame structure without VLAN header,

    Header compression configuration for the Ethernet frame structure header,

    Header compression configuration of the Ethernet frame structure service data unit SDU.
17. The method according to claim 16, further comprising:

    The access network device maps multiple data packets in the first DRB, where the multiple data packets include a data packet with an Ethernet frame structure having a VLAN header and an Ethernet frame structure without a VLAN header. data pack;

    The packet data convergence protocol PDCP device of the access network device determines, according to a VLAN instruction, a data packet having an Ethernet frame structure with a VLAN header and / or an Ethernet frame structure without a VLAN header in the plurality of data packets. Packet.
18. The method according to claim 17, wherein the VLAN indication is indicated by a core network device, or the VLAN indication is obtained by the access network device through a terminal device report.
19. The method according to claim 17 or 18, further comprising:

    The PDCP device of the access network device adopts a manner that the header of the Ethernet frame structure does not perform header compression, and performs header compression or decompression on the multiple data packets.
20. The method according to claim 17 or 18, further comprising:

    The PDCP device of the access network device performs header compression or decompression of the Ethernet frame structure data packet including the VLAN header on the data packet of the Ethernet frame structure including the VLAN header, and The data packet of the Ethernet frame structure with the prefix is compressed or decompressed in the Ethernet frame structure without the VLAN header.
21. The method according to claim 20, further comprising:

    The access network device configures a first protocol data unit PDU of a first PDCP device to carry first instruction information, where the first instruction information is used to indicate that a peer end of the first PDCP device uses the first PDU. The header compression method including the VLAN header is used for header compression or the header compression method is used for the header compression without including the VLAN header.
22. The method according to claim 20, further comprising:

    The first PDU configured by the access network device to configure the first radio link control RLC device carries first instruction information, where the first instruction information is used to indicate that the first end of the first RLC device is the first PDU. Head compression using a header compression method including a VLAN header or head compression using a header compression method that does not include a VLAN header.
23. The method according to claim 17 or 18, further comprising:

    The PDCP device of the access network device adopts a method of constructing a virtual VLAN to perform header compression or decompression on a data packet of an Ethernet frame structure without a VLAN header in the multiple data packets;

    The PDCP device of the access network device performs header compression or decompression on a data packet with an Ethernet frame structure having a VLAN header in the multiple data packets in a VLAN manner.
24. The method according to claim 23, further comprising:

    The first PDU configured by the access network device to carry the first PDCP device carries first instruction information, where the first instruction information is used to indicate that the first end of the first PDCP device uses a virtual VLAN word. The header compression method performs header compression or the header compression method without using the virtual VLAN header performs header compression.
25. The method according to claim 23, further comprising:

    The first PDU of the first RLC device configured by the access network device carries first instruction information, where the first instruction information is used to indicate that the first PDU of the peer end of the first RLC device uses a virtual VLAN word. The header compression method performs header compression or the header compression method without using the virtual VLAN header performs header compression.
26. The method according to claim 21, 22, 24 or 25, wherein:

    The first indication information is carried at a reserved bit position in the first PDU; or

    The first indication information is carried in a newly added bit field in the first PDU.
27. The method according to any one of claims 15 to 26, wherein before the access network device sends the first configuration information, the method further comprises:

    The access network device determines the first configuration information according to first information, where the first information includes a data packet identifier, a data packet arrangement order, and a data packet transmission corresponding to a plurality of data packets mapped to the first DRB. Whether at least one of a VLAN identifier is included in a time, a data packet, a QoS data flow corresponding to the data packet, and a VLAN indication of the QoS data flow corresponding to the data packet.
28. The method according to claim 27, wherein the first information is reported by the terminal device, or the first information is indicated by a core network device.
29. The method according to any one of claims 15 to 28, wherein before the access network device sends the first configuration information, the method further comprises:

    Receiving, by the access network device, the capability of supporting header compression and decompression of the overall Ethernet frame structure reported by the terminal device, and indicating whether the terminal device supports header compression and / or support of the Ethernet frame structure Header compression for Ethernet frame structure with VLAN header;

    The access network device configures the header of the Ethernet frame structure for the first DRB without performing header compression configuration, or configures the first DRB with or without the Ethernet structure header and the data domain to perform header compression configuration respectively Or, configure the first DRB to support or not support the header compression configuration of the Ethernet structure, or configure the first DRB to support or not support the header compression configuration of the Ethernet structure including the VLAN header.
30. The method according to any one of claims 15 to 28, wherein before the access network device sends the first configuration information, the method further comprises:

    Receiving, by the access network device, the support capabilities for header compression and decompression of the Ethernet header and data domain reported by the terminal device, respectively, for indicating whether the terminal device supports header compression and / or Ethernet frame structure Whether to support header compression of the Ethernet frame structure of the VLAN header;

    The access network device configures a header compression configuration of the Ethernet frame structure header and a data domain for the first DRB, or does not configure a header compression configuration for the Ethernet structure header for the first DRB, or Configure a header compression configuration for the Ethernet structure for the first DRB, or configure a header compression configuration for the Ethernet structure containing a VLAN header for the first DRB.
31. A terminal device, comprising:

    A communication unit, configured to receive first configuration information sent by an access network device, where the first configuration information is used to configure multiple header compression configurations for a first data radio bearer DRB;

    A processing unit, configured to perform header compression or decompression on the first DRB according to the first configuration information.
32. The terminal device according to claim 31, wherein the plurality of header compression configurations include at least two of the following header compression configurations:

    Header compression configuration for Ethernet frame structure including virtual LAN VLAN header,

    Header compression configuration for Ethernet frame structure without VLAN header,

    Header compression configuration for the Ethernet frame structure header,

    Header compression configuration of the Ethernet frame structure service data unit SDU.
33. The terminal device according to claim 32, wherein the processing unit is further configured to:

    Mapping a plurality of data packets in the first DRB, the plurality of data packets including a data packet of an Ethernet frame structure with a VLAN header and a data packet of an Ethernet frame structure without a VLAN header;

    The PDCP device that controls the packet data convergence protocol of the terminal device determines, according to a VLAN instruction, a data packet having an Ethernet frame structure with a VLAN header and / or an Ethernet frame structure without a VLAN header in the multiple data packets. data pack.
34. The terminal device according to claim 33, wherein the VLAN indication is indicated by the access network device, or the VLAN indication is obtained by the terminal device through data flow information interaction performed between layers. .
35. The terminal device according to claim 33 or 34, wherein the processing unit is specifically configured to:

    The PDCP device controlling the terminal device adopts a manner that the header of the Ethernet frame structure does not perform header compression, and performs header compression or decompression on the multiple data packets.
36. The terminal device according to claim 33 or 34, wherein the processing unit is specifically configured to:

    The PDCP device controlling the terminal device performs header compression or decompression of the Ethernet frame structure data packet including the VLAN header on the data packet of the Ethernet frame structure having the VLAN header according to the VLAN instruction, and the data packet without the VLAN character. The data packet of the Ethernet frame structure of the header performs header compression or decompression of the Ethernet frame structure without the VLAN header.
37. The terminal device according to claim 36, wherein the processing unit is further configured to:

    The first protocol data unit PDU configured with the first PDCP device carries first instruction information, where the first instruction information is used to indicate that a peer end of the first PDCP device adopts a header including a VLAN header. The head compression is performed by the compression method or the head compression is performed by the header compression method that does not include a VLAN header.
38. The terminal device according to claim 36, wherein the processing unit is further configured to:

    The first PDU configured with the first radio link control RLC device carries first instruction information, and the first instruction information is used to indicate that the first PDU of the peer end of the first RLC device adopts a VLAN header. The header compression method performs header compression or the header compression method does not include a VLAN header.
39. The terminal device according to claim 33 or 34, wherein the processing unit is specifically configured to:

    The PDCP device controlling the terminal device adopts a method of constructing a virtual VLAN to perform header compression or decompression on the data packet of the Ethernet frame structure without a VLAN header in the multiple data packets;

    The PDCP device controlling the terminal device performs header compression or decompression on the data packets of the Ethernet frame structure having the VLAN header in the multiple data packets in a VLAN manner.
40. The terminal device according to claim 39, wherein the processing unit is further configured to:

    The first PDU configured with the first PDCP device carries first instruction information, where the first instruction information is used to instruct a peer end of the first PDCP device that the first PDU is performed by using a header compression method of a virtual VLAN header. Header compression or header compression without using the virtual VLAN header.
41. The terminal device according to claim 39, wherein the processing unit is further configured to:

    The first PDU configured with the first radio link control RLC device carries first indication information, where the first indication information is used to indicate that the first PDU of the opposite end of the first RLC device is a virtual VLAN header. The header compression method performs header compression or the header compression method does not use a virtual VLAN header to perform header compression.
42. The terminal device according to claim 37, 38, 40 or 41, wherein:

    The first indication information is carried at a reserved bit position in the first PDU; or

    The first indication information is carried in a newly added bit field in the first PDU.
43. The terminal device according to any one of claims 31 to 42, wherein before the communication unit receives the first configuration information,

    The processing unit is further configured to obtain first information through data flow information interaction between layers, where the first information includes a packet identifier corresponding to a plurality of data packets mapped to the first DRB, a data packet arrangement order, A data packet transmission time, whether the data packet includes at least one of a VLAN identifier, a QoS data flow corresponding to the data packet, and a VLAN indication of the QoS data flow corresponding to the data packet;

    The communication unit is further configured to send the first information to the access network device, where the first information is used by the access network device or the core network device to determine the first configuration information; or

    The communication unit is further configured to send the first information to a core network device, where the first information is used by the core network device to determine the first configuration information.
44. The terminal device according to any one of claims 31 to 43, wherein before the communication unit receives the first configuration information, the communication unit is further configured to report a header of the entire Ethernet frame structure. Support for compression and decompression, or reporting support for header compression and decompression of the Ethernet header and data domain, respectively, for indicating whether the terminal device supports header compression and / or support of the Ethernet frame structure Header compression for the Ethernet frame structure of the VLAN header.
45. An access network device, comprising:

    The communication unit is configured to send first configuration information to the terminal device, where the first configuration information is used to configure multiple header compression configurations for the first data radio bearer DRB.
46. The access network device according to claim 45, wherein the multiple header compression configurations include at least two of the following header compression configurations:

    Header compression configuration for Ethernet frame structure including virtual LAN VLAN header,

    Header compression configuration for Ethernet frame structure without VLAN header,

    Header compression configuration for the Ethernet frame structure header,

    Header compression configuration of the Ethernet frame structure service data unit SDU.
47. The access network device according to claim 46, wherein the access network device further comprises:

    A processing unit, configured to map a plurality of data packets in the first DRB, where the plurality of data packets include a data packet with an Ethernet frame structure with a VLAN header and data with an Ethernet frame structure without a VLAN header package;

    The processing unit is further configured to control a packet data convergence protocol PDCP device of the access network device to determine, according to a VLAN indication, a data packet having an Ethernet frame structure with a VLAN header in the plurality of data packets and / or a packet without A packet with an Ethernet frame structure with a VLAN header.
48. The access network device according to claim 47, wherein the VLAN indication is indicated by a core network device, or the VLAN indication is obtained by the access network device through a terminal device report.
49. The access network device according to claim 47 or 48, wherein the processing unit is further configured to:

    The PDCP device controlling the access network device performs header compression or decompression on the multiple data packets in a manner that the header of the Ethernet frame structure does not perform header compression.
50. The access network device according to claim 47 or 48, wherein the processing unit is further configured to:

    The PDCP device controlling the access network device performs, according to the VLAN instruction, compression or decompression of an Ethernet frame structure data packet including a VLAN header in a data packet having a VLAN header and The data packet of the Ethernet frame structure with the VLAN header performs the header compression or decompression of the Ethernet frame structure without the VLAN header.
51. The access network device according to claim 50, wherein the processing unit is further configured to:

    The first protocol data unit PDU configured with the first PDCP device carries first instruction information, where the first instruction information is used to indicate that a peer end of the first PDCP device adopts a header including a VLAN header. The head compression is performed by the compression method or the head compression is performed by the header compression method that does not include a VLAN header.
52. The access network device according to claim 50, wherein the processing unit is further configured to:

    The first PDU configured with the first radio link control RLC device carries first instruction information, and the first instruction information is used to indicate that the first PDU of the peer end of the first RLC device adopts a VLAN header. The header compression method performs header compression or the header compression method does not include a VLAN header.
53. The access network device according to claim 47 or 48, wherein the processing unit is further configured to:

    The PDCP device controlling the access network device adopts a method of constructing a virtual VLAN to perform header compression or decompression on the data packet of the Ethernet frame structure without the VLAN header in the multiple data packets;

    The PDCP device controlling the access network device performs header compression or decompression on the data packets of the Ethernet frame structure having the VLAN header in the multiple data packets in a VLAN manner.
54. The access network device according to claim 53, wherein the processing unit is further configured to:

    The first PDU configured with the first PDCP device carries first instruction information, where the first instruction information is used to instruct a peer end of the first PDCP device that the first PDU is performed by using a header compression method of a virtual VLAN header. Header compression or header compression without using the virtual VLAN header.
55. The access network device according to claim 53, wherein the processing unit is further configured to:

    The first PDU configured with the first radio link control RLC device carries first indication information, where the first indication information is used to indicate that the first PDU of the opposite end of the first RLC device is a virtual VLAN header. The header compression method performs header compression or the header compression method does not use a virtual VLAN header to perform header compression.
56. The access network device according to claim 51, 52, 54 or 55, wherein:

    The first indication information is carried at a reserved bit position in the first PDU; or

    The first indication information is carried in a newly added bit field in the first PDU.
57. The access network device according to any one of claims 45 to 56, wherein before the communication unit sends the first configuration information, the processing unit is further configured to:

    Determining the first configuration information according to the first information, where the first information includes a data packet identifier corresponding to a plurality of data packets mapped to the first DRB, a data packet arrangement order, a data packet transmission time, a data packet, and data Whether at least one of a VLAN identifier is included in the VLAN indication of the QoS data stream corresponding to the packet and the QoS data stream corresponding to the data packet.
58. The access network device according to claim 57, wherein the first information is reported by the terminal device, or the first information is indicated by a core network device.
59. The access network device according to any one of claims 45 to 58, wherein before the communication unit sends the first configuration information,

    The communication unit is further configured to receive the support capability of the overall header compression and decompression of the Ethernet frame structure reported by the terminal device, and used to indicate whether the terminal device supports the header compression and / or whether the Ethernet frame structure is supported. Supports header compression for Ethernet frame structure with VLAN header;

    The processing unit is further configured to configure the header of the Ethernet frame structure for the first DRB without performing header compression configuration, or configure the first DRB to support or not support header compression for the Ethernet structure header and data domain respectively. Configure, or configure, for the first DRB, a header compression configuration that supports or does not support an Ethernet structure, or configure, for the first DRB, whether the header compression configuration of an Ethernet structure that includes a VLAN header is supported or not.
60. The access network device according to any one of claims 45 to 58, wherein before the communication unit sends the first configuration information,

    The communication unit is further configured to receive support capabilities for header compression and decompression of an Ethernet header and a data domain reported by the terminal device, respectively, and is used to indicate whether the terminal device supports header compression of an Ethernet frame structure and / Or whether the Ethernet frame structure header compression of the VLAN header is supported;

    The processing unit is further configured to configure header compression and data domain configuration of the first DRB for the first DRB, respectively, or configure header compression configuration for the Ethernet structure header for the first DRB, or Configure a header compression configuration for the first DRB for the Ethernet structure, or configure a header compression configuration for the first DRB that supports or does not support the Ethernet structure with a VLAN header.
61. A terminal device includes a processor and a memory, where the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, and execute any one of claims 1 to 14. The method of one item.
62. An access network device, comprising: a processor and a memory, where the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, and execute claims 15 to 30 The method of any one of.
63. A chip, comprising: a processor, configured to call and run a computer program from a memory, so that a device having the chip installed executes the method according to any one of claims 1 to 14.
64. A chip, comprising: a processor, configured to call and run a computer program from a memory, so that a device having the chip installed executes the method according to any one of claims 15 to 30.
65. A computer-readable storage medium, which is used for storing a computer program, which causes a computer to execute the method according to any one of claims 1 to 14.
66. A computer-readable storage medium, which is used for storing a computer program that causes a computer to execute the method according to any one of claims 15 to 30.
67. A computer program product, comprising computer program instructions that cause a computer to execute the method according to any one of claims 1 to 14.
68. A computer program product, comprising computer program instructions that cause a computer to execute the method according to any one of claims 15 to 30.
69. A computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 14.
70. A computer program, wherein the computer program causes a computer to execute the method according to any one of claims 15 to 30.

Images