CN112868249B

CN112868249B - Wireless communication method, terminal equipment and access network equipment

Info

Publication number: CN112868249B
Application number: CN201880097263.5A
Authority: CN
Inventors: 刘建华; 卢前溪; 尤心
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2018-09-29
Filing date: 2018-09-29
Publication date: 2023-08-25
Anticipated expiration: 2038-09-29
Also published as: TW202041064A; WO2020062176A1; CN112868249A

Abstract

The embodiment of the application provides a wireless communication method, terminal equipment and access network equipment, wherein the access network equipment can configure various header compression configurations for one DRB, so that when data packets with VLAN (virtual local area network) headers and Ethernet frame structures without VLAN headers are mapped in one DRB at the same time, header compression or decompression can be performed based on the various header compression configurations, and header compression efficiency is improved. The method comprises the following steps: the method comprises the steps that terminal equipment receives first configuration information sent by access network equipment, wherein the first configuration information is used for configuring multiple header compression configurations for a first DRB; and the terminal equipment 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

The embodiment of the application relates to the field of communication, and more particularly relates to a wireless communication method, terminal equipment and access network equipment.

Background

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

In LTE and NR systems, public network systems, i.e. public land networks based on public land mobile networks (Public Land Mobile Network, PLMN), are typically deployed. Meanwhile, in some scenarios, for example, in office, home, factory, etc., in order to enable safe and effective management, a local network is usually laid out by a local user or manager, and only authorized users with access rights to the local network.

In the coexistence scenario of the public network system and the local network, when the PDU session is Ethernet frames, the Ethernet PDU may carry a virtual local area network (Virtual Local Area Network, VLAN) header, or may not carry a VLAN header, and the corresponding Ethernet frame structures are different. The header compression algorithm used for the two PDUs is different during header compression. Therefore, how to implement header compression of Ethernet PDUs carrying VLAN headers and not carrying VLAN headers is a problem to be solved.

Disclosure of Invention

The embodiment of the application provides a wireless communication method, terminal equipment and access network equipment, wherein the access network equipment can configure a plurality of header compression configurations for one data radio bearer (Data Radio Bearer, DRB), so that when a data packet with a VLAN (virtual local area network) header and an Ethernet frame structure without the VLAN header is mapped in one DRB, header compression or decompression can be performed based on the plurality of header compression configurations, and header compression efficiency is improved.

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

the method comprises the steps that terminal equipment receives first configuration information sent by access network equipment, wherein the first configuration information is used for configuring multiple header compression configurations for a first DRB;

and the terminal equipment performs header compression or decompression on the first DRB according to the first configuration information.

Alternatively, 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, there is provided a wireless communication method comprising:

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

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

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

In a third aspect, a terminal device is provided for performing the method in the first aspect or each implementation manner thereof.

Specifically, the terminal device comprises functional modules for performing the method of the first aspect or its implementation manner.

In a fourth aspect, an access network device is provided for performing the method of the second aspect or implementations thereof.

In particular, the access network device comprises functional modules for performing the method of the second aspect or implementations thereof described above.

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

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

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

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

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

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

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

By the technical scheme, the access network device can configure multiple header compression configurations for the first DRB, so that header compression or decompression can be performed based on the multiple header compression configurations when the data packets of the Ethernet frame structure including the VLAN headers and the Ethernet frame structure not including the VLAN headers are mapped in the first DRB at the same time, and header compression efficiency is improved.

Drawings

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

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

Fig. 3 is a schematic view of V domain provided according to an embodiment of the present application.

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

Fig. 5 is a schematic view of still another V-domain provided according to an embodiment of the present application.

Fig. 6 is a schematic view of still another V-domain provided according to an embodiment of the present application.

Fig. 7 is a schematic flow chart diagram of another wireless communication method provided in accordance with 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 provided according to an embodiment of the present application.

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

Fig. 12 is a schematic block diagram of a communication system provided in accordance with an embodiment of the present application.

Detailed Description

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

The technical scheme of the embodiment of the application can be applied to various communication systems, such as: global system for mobile communications (Global System of Mobile communication, GSM), code division multiple access (Code Division Multiple Access, CDMA), wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) systems, general packet radio service (General Packet Radio Service, GPRS), long term evolution (Long Term Evolution, LTE) systems, LTE frequency division duplex (Frequency Division Duplex, FDD) systems, LTE time division duplex (Time Division Duplex, TDD), universal mobile telecommunications system (Universal Mobile Telecommunication System, UMTS), worldwide interoperability for microwave access (Worldwide Interoperability for Microwave Access, wiMAX) communication systems, or 5G systems, and the like.

An exemplary communication system 100 to which embodiments of the present application may be applied is shown in fig. 1. The communication system 100 may include a terminal device 110, which terminal device 110 may be located within the coverage area of an access network device 120. "terminal device" as used herein includes, but is not limited to, a connection via a wireline, such as via a public-switched telephone network (Public Switched Telephone Networks, PSTN), a digital subscriber line (Digital Subscriber Line, DSL), a digital cable, a direct cable connection; and/or another data connection/network; and/or via a wireless interface, e.g., for a cellular network, a wireless local area network (Wireless Local Area Network, WLAN), a digital television network such as a DVB-H network, a satellite network, an AM-FM broadcast transmitter; and/or means of the other terminal device arranged to receive/transmit communication signals; and/or internet of things (Internet of Things, ioT) devices. Terminal devices arranged to communicate over a wireless interface may be referred to as "wireless communication terminals", "wireless terminals" or "mobile terminals". Examples of mobile terminals include, but are not limited to, satellites or cellular telephones; a personal communications system (Personal Communications System, PCS) terminal that may combine a cellular radiotelephone with data processing, facsimile and data communications capabilities; a PDA that can include a radiotelephone, pager, internet/intranet access, web browser, organizer, calendar, and/or a global positioning system (Global Positioning System, GPS) receiver; and conventional laptop and/or palmtop receivers or other electronic devices that include a radiotelephone transceiver. A terminal device may refer to an access terminal, user Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a 5G network or a terminal device in a future evolved PLMN, 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 referred to as a communication terminal, terminal). Access network device 120 may provide communication coverage for a particular geographic area and may communicate with terminal devices located within the coverage area. Alternatively, the access network device 120 may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, a base station (NodeB, NB) in a WCDMA system, an evolved base station (Evolutional Node B, eNB or eNodeB) in an LTE system, or a radio controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the network device may be a mobile switching center, a relay station, an access point, a vehicle device, a wearable device, a hub, a switch, a bridge, a router, a network-side device in a 5G network, or a network device in a future evolved public land mobile network (Public Land Mobile Network, PLMN), etc.

The wireless communication system 100 further comprises a core network device 130 in communication with the access network device. Alternatively, the core network device 130 may be a 5G core network device, for example, an access and mobility management function (Access and Mobility Management Function, AMF), responsible for access and mobility management, having functions of authentication, handover, location update, etc. for a user. As another example, a session management function (Session Management Function, SMF) is responsible for session management, including establishment, modification, release, etc. of Packet Data Unit (PDU) sessions. As another example, a user plane function (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.

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

In the embodiment of the present application, an access network device provides a service 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, where the cell may be a cell corresponding to the network device (for example, a base station), and the cell may belong to a macro base station or a base station corresponding to a Small cell (Small cell), where the Small cell may include: urban cells (Metro cells), micro cells (Micro cells), pico cells (Pico cells), femto cells (Femto cells) and the like, and the small cells have the characteristics of small coverage area and low transmitting power and are suitable for providing high-rate data transmission services.

It should be appreciated that the packet data convergence protocol (Packet Data Convergence Protocol, PDCP) protocol incorporates header compression and decompression functionality for supporting the use of different header compression and header compression parameters for different data radio bearers (Data Radio Bearer, DRBs) according to a configured header compression configuration (profile). PDCP uses a robust header compression (Robust information header compression, ROHC) protocol, supported header compression protocols (protocols) and configurations (profiles) as shown in table 1 below. Specifically, as shown in table 1 below, the compression objects of the different header compression configurations may be at least one of Real-time transmission protocol (Real-time Transport Protocol, RTP), IP, user datagram protocol (User Datagram Protocol, UDP), encapsulation security load (Encapsulating Security Payload, ESP), no compression (No compression), and the compression policy may be specifically RFC (Request For Comments) series files as shown in table 1 below.

TABLE 1

Configuration identification	Compression object (Usage)	Compression strategy (Reference)
			0x0000	Non-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	RFC 3843，RFC 4815
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

Alternatively, the embodiment of the application can be used in a scenario where a public land network or a local network or a public network system and a local network coexist.

Wherein the public land network may be a PLMN-based public land network.

The local network may also be referred to as a local area network or a private network, which is typically arranged in an office scenario, a home scenario, a factory, where a more efficient and secure management may be achieved, typically with local users or administrators laying out the local network. Typically, authorized users that are able to access have access to the local network.

The local network may or may not be managed or governed by the public land network.

Alternatively, the local network may communicate using unlicensed bands, or may share licensed bands with the public land network.

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

Alternatively, in the embodiment of the present application, the public land network and the local network may share a core network, and the access network is independent; alternatively, the access networks may be shared, while the core networks are independent; alternatively, the access network and the core network may be shared; alternatively, neither the access network nor the core network is common.

Alternatively, in embodiments of the present application, multiple or multiple local networks may share a core network, while the access networks are independent; alternatively, the access networks may be shared, while the core networks are independent; alternatively, the access network and the core network may be shared; alternatively, neither the access network nor the core network is common.

It should be noted that, in the public network system, and/or the local network scenario, and/or the scenario where 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 may not carry a VLAN header, and the corresponding Ethernet frame structures are different. The header compression algorithm used for the two PDUs is different during header compression. At present, no distinction processing is performed for this scenario, so header compression of Ethernet PDUs carrying VLAN headers and not carrying VLAN headers cannot be realized. Based on the above problems, the present 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, but may be a core network device. Correspondingly, the processing layers of the terminal device and the network device may be PDCP layers, or other entities or layers.

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

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

s210, the terminal equipment receives first configuration information sent by the access network equipment, wherein the first configuration information is used for configuring various header compression configurations for a first DRB;

and S220, the terminal equipment performs header compression or decompression on the first DRB according to the first configuration information.

Alternatively, 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, where the core network device may be, for example, an AMF device or a UPF device. The following description regarding access network devices applies equally to core network devices. The following will specifically describe an example in which the terminal device receives the first configuration information from the access network device.

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 embodiment of the present application.

Optionally, in an embodiment of the present application, the plurality of head compression configurations includes at least two of the following head compression configurations:

header compression configuration of the ethernet frame structure including VLAN headers,

header compression configuration of ethernet frame structures that do not include VLAN headers,

header compression configuration of ethernet frame structure header,

the ethernet frame structure serves a header compression configuration of the data units (service data unit, SDU).

Alternatively, in the embodiment of the present application, header compression configuration may be performed on the header and the data field of the ethernet frame structure, respectively.

For example, the access network device configures the header of the ethernet frame structure not to perform header compression configuration, or configures the header of the ethernet frame structure and the data field to perform header compression configuration for the first DRB, or configures the header compression configuration of the ethernet frame structure including VLAN headers for the first DRB. The terminal device performs header compression or decompression on the header and the data field of the ethernet frame structure, or performs header compression or decompression on the whole ethernet frame structure, respectively, according to the configuration.

For another example, the access network device configures a header of the ethernet frame structure and the data field for the first DRB to perform header compression configuration, or does not configure a header compression configuration for the header of the ethernet structure for the first DRB, or configures a header compression configuration for the ethernet structure with or without VLAN headers for the first DRB. The terminal device performs header compression or decompression on the header and the data field of the ethernet frame structure, or performs header compression or decompression on the whole ethernet frame structure, respectively, according to the configuration.

Optionally, in an embodiment of the present application, the terminal device maps a plurality of data packets in the first DRB, where the plurality of data packets includes 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. That is, the terminal device maps an ethernet frame structure including a VLAN header and an ethernet frame structure not including a VLAN header in the first DRB, and at this time, the terminal device may header compress or decompress the header and the data field of the ethernet frame structure, respectively.

Optionally, in an embodiment of the present application, the terminal device maps a plurality of data packets in the first DRB, where the plurality of data packets includes 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. That is, the terminal device maps an ethernet frame structure including the VLAN header and an ethernet frame structure not including the VLAN header in the first DRB, and at this time, the terminal device may header compress or decompress the ethernet frame structure as a whole.

Optionally, the terminal device may determine, according to the VLAN indication, a packet of the ethernet frame structure having a VLAN header and/or a packet of the ethernet frame structure not having a VLAN header in the plurality of packets.

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

Specifically, in the embodiment of the present application, the PDCP device of the terminal device, or the PDU device of the terminal device, or the RLC device of the terminal device, or the new sublayer in the 5G network performs header compression or decompression on the plurality of data packets mapped to the first DRB.

Hereinafter, header compression or decompression of a plurality of data packets mapped to the first DRB by the PDCP device of the terminal device will be specifically described as an example.

Alternatively, as an example one, the PDCP device of the terminal device performs header compression or decompression on the plurality of data packets in such a manner that the ethernet frame structure header is not subjected to header compression. In this case, the compression method of the data field is not limited.

Alternatively, as an example two, the PDCP device of the terminal device performs header compression or decompression of an ethernet frame structure including a VLAN header on a packet having the ethernet frame structure of the VLAN header and performs header compression or decompression of an ethernet frame structure not including the VLAN header on a packet having the ethernet frame structure not having the VLAN header according to the VLAN indication.

Further, in the second example, the terminal device configures a first PDU of the first PDCP device to carry first indication information, where the first indication information is used to indicate to an opposite end of the first PDCP device that the first PDU is header-compressed in a header compression manner including a VLAN header or header-compressed in a header compression manner not including a 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 this example. Similarly, the first PDU may be any PDU in the first PDCP device.

Optionally, in the second example, the first indication information is carried on 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 field occupying 1bit, where the V field is located in one R bit of 3R bits reserved in the first PDU, and in the V field, definition 1 indicates that the first PDU is header-compressed in a header compression manner including a VLAN header, and definition 0 indicates that the first PDU is header-compressed in a header compression manner not including a VLAN header. The opposite end of the first PDCP device may learn, according to the V domain, a header compression manner of the first PDU, and further perform a corresponding decompression.

For another example, as shown in fig. 4, the terminal device adds a V field of 1Oct after the PDCP SN and before the data in the first PDU, in the V field, definition 1 indicates that the first PDU is header-compressed in a header compression manner including VLAN headers, and definition 0 indicates that the first PDU is header-compressed in a header compression manner not including VLAN headers. The opposite end of the first PDCP device may learn, according to the V domain, a header compression manner of the first PDU, and further perform a corresponding decompression.

It should be understood that in fig. 3 and 4, PDCP SN may refer to PDCP Sequence Number (SN), oct may refer to unit byte length, MAC may refer to medium access control (Media Access Control, MAC), PDCP SN (cont.) represents consecutive PDCP SNs, and MAC-I (cont.) represents consecutive MACs.

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

Further, in the second example, the terminal device configures a first PDU of the first RLC device to carry first indication information, where the first indication information is used to indicate that an opposite end of the first RLC device performs header compression in a header compression manner including a VLAN header or performs header compression in a header compression manner not including a VLAN header.

Correspondingly, the opposite end of the first RLC device informs the PDCP device of the local entity in a manner of adopting or not adopting VLAN header compression correspondingly.

It should be noted that the first RLC device may be any RLC device serving the first DRB in the terminal device, that is, any RLC device serving the first DRB in the terminal device satisfies this example. Similarly, the first PDU may be any one of the PDUs in the first RLC device.

Similarly, as in fig. 3 and fig. 4, the first PDU of the first RLC device may be added with indication information for indicating the compression mode of the first PDU of the first RLC device at the opposite end of the first RLC device, which is not described herein for brevity.

Alternatively, as an example three, the terminal device transmits, in the first PDCP device, the PDU header-compressed in the header compression manner including the VLAN header, and transmits, in the second PDCP device, the PDU header-compressed in the header compression manner not including the VLAN header.

In the third example, the first PDCP device and the second PDCP device are configured by an access network device through RRC signaling.

Optionally, as a fourth example, the PDCP device of the terminal device performs header compression or decompression on a packet of the ethernet frame structure without a VLAN header in the plurality of packets by adopting a manner of constructing a virtual VLAN;

and the PDCP equipment of the terminal equipment performs header compression or decompression on the data packet with the Ethernet frame structure with the VLAN headers in the plurality of data packets according to the VLAN mode.

It should be noted that, at this time, the network side may only configure one header compression and decompression method and parameters including VLAN sub-header.

Further, in the fourth example, the terminal device configures a first PDU of the first PDCP device to carry first indication information, where the first indication information is used to indicate that an opposite end of the first PDCP device performs header compression in a header compression manner of a virtual VLAN header or performs header compression in a header compression manner of a non-virtual VLAN header.

Optionally, in this example four, the first indication information is carried on 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 field occupying 1bit, where the V field is located in one R bit of 3R bits reserved in the first PDU, and in the V field, definition 1 indicates that the first PDU is header-compressed by using a header compression manner of a virtual VLAN header, and definition 0 indicates that the first PDU is header-compressed by not using a header compression manner of a virtual VLAN header. The opposite end of the first PDCP device may learn, according to the V domain, a header compression manner of the first PDU, and further perform a corresponding decompression.

For another example, as shown in fig. 6, the terminal device adds a V field of 1Oct after the PDCP SN and before the data in the first PDU, where in the V field, definition 1 indicates that the first PDU is header-compressed by using the header compression method of the virtual VLAN header, and definition 0 indicates that the first PDU is header-compressed by not using the header compression method of the virtual VLAN header. The opposite end of the first PDCP device may learn, according to the V domain, a header compression manner of the first PDU, and further perform a corresponding decompression.

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

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

Further, in the fourth example, the terminal device configures a first PDU of the first RLC device to carry first indication information, where the first indication information is used to indicate that the opposite end of the first RLC device performs header compression in a header compression manner of a virtual VLAN header or performs header compression in a header compression manner of a virtual VLAN header not.

Similarly, as shown in fig. 5 and fig. 6, the first PDU of the first RLC device may be added to indicate whether the first PDU of the first RLC device at the opposite end of the first RLC device is the indication information for adding the compression mode of the virtual VLAN, which is not described herein for brevity.

Optionally, in the embodiment of the present application, before the terminal device receives the first configuration information, the terminal device acquires first information through data Flow information interaction performed between layers, where the first information includes at least one of a packet identifier corresponding to a plurality of packets mapped to the first DRB, a packet arrangement sequence, a packet transmission time, whether the packets include a VLAN identifier, a QoS data Flow (Flow) corresponding to the packets, and a VLAN indication of a QoS data Flow corresponding to the packets.

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

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

Optionally, in the embodiment of the present application, before the terminal device receives the first configuration information, the terminal device reports a capability of supporting header compression and header decompression of the ethernet frame structure as a whole, or reports a capability of supporting header compression and header decompression of the ethernet header and the data field, respectively, for indicating whether the terminal device supports header compression of the ethernet frame structure and/or supports header compression of the ethernet frame structure of the VLAN header.

It should be understood that the supporting capability reported by the terminal device is used for determining the first configuration information by the access network device or the 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 when the first DRB maps a data packet with an ethernet frame structure including a VLAN header and a data packet without a VLAN header at the same time, the terminal device may perform header compression or decompression based on the multiple header compression configurations, thereby improving header compression efficiency.

Fig. 7 is a schematic flow chart diagram of a wireless communication method 300 according to an embodiment of the application, as shown in fig. 3, the method 300 may include the following:

s310, the access network device sends first configuration information to the terminal device, wherein the first configuration information is used for configuring multiple header compression configurations for the first DRB.

Alternatively, 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, where the core network device may be, for example, an AMF device or a UPF device. The following description regarding access network devices applies equally to core network devices. The following specifically describes an example in which the access network device sends the first configuration information.

Header compression configuration of ethernet frame structure header,

header compression configuration of the ethernet frame structure SDU.

Optionally, in an embodiment of the present application, the access network device maps a plurality of data packets in the first DRB, where the plurality of data packets includes 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.

Optionally, the access network device determines, according to the VLAN indication, a packet of the ethernet frame structure with a VLAN header and/or a packet of the ethernet frame structure without a VLAN header in the plurality of packets.

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

Specifically, in the embodiment of the present application, the PDCP device of the access network device, or the PDU device of the access network device, or the RLC device of the access network device, or the new sublayer in the 5G network performs header compression or decompression on the plurality of data packets mapped to the first DRB.

Hereinafter, header compression or decompression of a plurality of data packets mapped to the first DRB by the PDCP device of the access network device will be specifically described.

Alternatively, as an example one, the PDCP device of the access network device performs header compression or decompression on the plurality of data packets in such a way that the ethernet frame structure header is not subjected to header compression.

Alternatively, as an example two, the PDCP device of the access network device performs header compression or decompression of an ethernet frame structure including a VLAN header on a packet having the ethernet frame structure of the VLAN header and performs header compression or decompression of an ethernet frame structure not including the VLAN header on a packet having the ethernet frame structure not having the VLAN header according to the VLAN indication.

Further, in the second example, the access network device configures a first PDU of the first PDCP device to carry first indication information, where the first indication information is used to indicate that an opposite end of the first PDCP device performs header compression by using a header compression manner including a VLAN header or performs header compression by using a header compression manner not including a VLAN header.

Further, in the second example, the access network device configures a first PDU of the first RLC device to carry first indication information, where the first indication information is used to indicate that an opposite end of the first RLC device performs header compression in a header compression manner including a VLAN header or performs header compression in a header compression manner not including a VLAN header.

Optionally, as a third example, the PDCP device of the access network device performs header compression or decompression on a packet of the ethernet frame structure without a VLAN header in the plurality of packets by adopting a manner of constructing a virtual VLAN;

and the PDCP equipment of the access network equipment performs header compression or decompression on the data packets with the Ethernet frame structure with VLAN headers in the plurality of data packets according to the VLAN mode.

Further, in the third example, the access network device configures a first PDU of the first PDCP device to carry first indication information, where the first indication information is used to indicate that an opposite end of the first PDCP device performs header compression in a header compression manner of a virtual VLAN header or performs header compression in a header compression manner of a non-virtual VLAN header.

Further, in the third example, the access network device configures a first PDU of the first RLC device to carry first indication information, where the first indication information is used to indicate that the opposite end of the first RLC device performs header compression in a header compression manner of a virtual VLAN header or performs header compression in a header compression manner of a virtual VLAN header not.

Optionally, in this example three, the first indication information is carried on 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 first information, where the first information includes at least one of a packet identifier corresponding to a plurality of packets mapped to the first DRB, a packet arrangement sequence, a packet transmission time, a packet, a QoS data flow corresponding to a packet, and a VLAN indication of a QoS data flow corresponding to a packet.

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

Optionally, in the embodiment of the present application, the access network device receives the capability of supporting header compression and header decompression of the whole ethernet frame structure reported by the terminal device, or receives the capability of supporting header compression and header decompression of the ethernet header and the data field reported by the terminal device respectively, which is used for indicating whether the terminal device supports header compression of the ethernet frame structure and/or supports header compression of the ethernet frame structure of the VLAN header.

Alternatively, in the embodiment of the present application, header compression configuration may be performed on the header and the data field of the ethernet frame structure, respectively. In the specific configuration, reference may be made to a reporting manner of the supporting capability of the terminal device.

Alternatively, in the embodiment of the present application, the header compression configuration may be performed on the whole ethernet frame structure. In the specific configuration, reference may be made to a reporting manner of the supporting capability of the terminal device.

For example, if the supporting capability of header compression and header decompression of the whole ethernet frame structure is reported by the terminal device, the access network device configures the header of the ethernet frame structure for the first DRB without performing header compression configuration, or configures the header of the ethernet structure and the data field with or without supporting header compression configuration of the ethernet structure for the first DRB, or configures the header compression configuration of the ethernet structure with or without supporting VLAN headers for the first DRB. Correspondingly, the terminal device performs header compression or decompression on the header and the data field of the Ethernet frame structure according to the configuration, or performs header compression or decompression on the whole Ethernet frame structure.

For another example, if the terminal device reports the supporting capability of header compression and header decompression of the ethernet header and the data field, the access network device configures header compression configuration for the first DRB and header compression configuration for the ethernet frame structure and header compression configuration for the data field, or configures header compression configuration for the first DRB and header compression configuration for the ethernet structure, or configures support or non-support for the first DRB and header compression configuration for the ethernet structure including VLAN headers. Correspondingly, the terminal device performs header compression or decompression on the header and the data field of the Ethernet frame structure according to the configuration, or performs header compression or decompression on the whole Ethernet frame structure.

It should be understood that the steps in the wireless communication method 300 may refer to corresponding steps in the wireless communication method 200, and are not described herein for brevity.

Fig. 8 shows a schematic block diagram of a terminal device 400 according to an embodiment of the application. As shown in fig. 8, the terminal apparatus 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 a first DRB;

and a processing unit 420, configured to perform header compression or decompression on the first DRB according to the first configuration information.

Optionally, the plurality of head compression configurations includes at least two of the following head compression configurations:

header compression configuration of the ethernet frame structure including the VLAN header of the virtual local area network,

header compression configuration of ethernet frame structure header,

header compression configuration of the ethernet frame structure SDU.

Optionally, the processing unit 420 is further configured to:

mapping a plurality of data packets in the first DRB, wherein the plurality of data packets comprise data packets with an Ethernet frame structure with VLAN headers and data packets without VLAN headers;

and the PDCP equipment controlling the terminal equipment determines the data packet with the Ethernet frame structure with the VLAN word head and/or the data packet without the Ethernet frame structure with the VLAN word head in the plurality of data packets according to the VLAN indication.

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 performed between layers.

Optionally, the processing unit 420 is specifically configured to:

the PDCP equipment controlling the terminal equipment performs header compression or decompression on the plurality of data packets in a mode that the header of the Ethernet frame structure does not perform header compression.

Optionally, the processing unit 420 is specifically configured to:

and the PDCP equipment controlling the terminal equipment performs header compression or decompression of the Ethernet frame structure comprising the VLAN header on the data packet with the Ethernet frame structure comprising the VLAN header according to the VLAN indication, and performs header compression or decompression of the Ethernet frame structure not comprising the VLAN header on the data packet without the Ethernet frame structure comprising the VLAN header.

Optionally, the processing unit 420 is further configured to:

the first PDU of the first PDCP equipment is configured to carry first indication information, and the first indication information is used for indicating that the opposite end of the first PDCP equipment performs header compression in a header compression mode comprising VLAN headers or performs header compression in a header compression mode not comprising VLAN headers.

Optionally, the processing unit 420 is further configured to:

the first PDU of the first RLC equipment is configured to carry first indication information, and the first indication information is used for indicating that the opposite end of the first PDU is subjected to header compression by adopting a header compression mode comprising VLAN headers or is subjected to header compression by adopting a header compression mode not comprising VLAN headers.

Optionally, the processing unit 420 is specifically configured to:

the PDCP equipment of the terminal equipment is controlled to carry out header compression or decompression on the data packets of the Ethernet frame structure without VLAN headers in the plurality of data packets in a mode of constructing a virtual VLAN;

and the PDCP equipment controlling the terminal equipment performs header compression or decompression on the data packets with the Ethernet frame structure with VLAN headers in the plurality of data packets according to the VLAN mode.

Optionally, the processing unit 420 is further configured to:

the first PDU of the first PDCP equipment is configured to carry first indication information, and the first indication information is used for indicating that the opposite end of the first PDCP equipment performs header compression in a header compression mode of a virtual VLAN (virtual VLAN) header or performs header compression in a header compression mode of a virtual VLAN header not adopted.

Optionally, the processing unit 420 is further configured to:

The first PDU of the first RLC equipment is configured to carry first indication information, wherein the first indication information is used for indicating that the opposite end of the first RLC equipment performs header compression in a header compression mode of a virtual VLAN (virtual VLAN) header or performs header compression in a header compression mode of a virtual VLAN header not adopted.

Optionally, the first indication information is carried on 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 performed between layers, where the first information includes at least one of a data packet identifier, a data packet arrangement sequence, a data packet transmission time, whether the data packet includes 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, where the data packet corresponds to the plurality of data packets mapped to the first DRB;

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

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 a capability of supporting header compression and header decompression for the whole ethernet frame structure, or report a capability of supporting header compression and header decompression for the ethernet header and the data field, respectively, for indicating whether the terminal device supports header compression for the ethernet frame structure and/or header compression for the ethernet frame structure for 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 embodiment of the method of the present application, and the foregoing and other operations and/or functions of each unit in the terminal device 400 are respectively for implementing the corresponding flow of the terminal device in the method 200 shown in fig. 2, and are not described herein for brevity.

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

a communication unit 510, 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.

header compression configuration of ethernet frame structure header,

header compression configuration of 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, where the plurality of data packets includes 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 the PDCP device of the access network device to determine, according to the VLAN indication, a packet of the ethernet frame structure with a VLAN header and/or a packet of the ethernet frame structure without a VLAN header in the plurality of packets.

Optionally, the processing unit 520 is further configured to:

the PDCP equipment controlling the access network equipment performs header compression or decompression on the plurality of data packets in a mode that the header of the Ethernet frame structure does not perform header compression.

Optionally, the processing unit 520 is further configured to:

and the PDCP equipment controlling the access network equipment performs header compression or decompression of the Ethernet frame structure comprising the VLAN header on the data packet with the Ethernet frame structure comprising the VLAN header according to the VLAN indication, and performs header compression or decompression of the Ethernet frame structure not comprising the VLAN header on the data packet without the Ethernet frame structure comprising the VLAN header.

Optionally, the processing unit 520 is further configured to:

The PDCP equipment controlling the access network equipment adopts a mode of constructing a virtual VLAN to carry out header compression or decompression on the data packet of the Ethernet frame structure without VLAN headers in the plurality of data packets;

and the PDCP equipment controlling the access network equipment performs header compression or decompression on the data packets with the Ethernet frame structure with VLAN headers in the plurality of data packets according to the VLAN mode.

Optionally, the processing unit 520 is further configured to:

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

and determining the first configuration information according to first information, wherein the first information comprises at least one of data packet identifiers corresponding to a plurality of data packets mapped to the first DRB, data packet arrangement sequence, data packet transmission time, data packets, qoS data flows corresponding to the data packets and VLAN indications of the QoS data flows corresponding to the data packets.

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

the communication unit 510 is further configured to receive a capability of supporting header compression and header decompression of the ethernet frame structure as a whole, where the capability is reported by the terminal device, and is used to indicate whether the terminal device supports header compression of the ethernet frame structure and/or whether the terminal device supports header compression of the ethernet frame structure with VLAN headers;

the processing unit 520 is further configured to configure the header of the ethernet frame structure not to perform header compression configuration, or to configure the header of the ethernet frame structure and the data field to perform header compression configuration for the first DRB, or to configure the header compression configuration for the first DRB to support or not support the ethernet frame structure including VLAN headers.

the communication unit 510 is further configured to receive the supporting capability of header compression and header decompression of the ethernet header and the data field reported by the terminal device, and indicate whether the terminal device supports header compression of the ethernet frame structure and/or whether the terminal device supports header compression of the ethernet frame structure of the VLAN header;

the processing unit 520 is further configured to perform header compression configuration for the header and the data field of the ethernet frame structure, or not configure header compression configuration for the header of the ethernet structure for the first DRB, or configure header compression configuration for the ethernet structure with or without VLAN headers for the first DRB.

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 embodiment of the method of the present application, and the foregoing and other operations and/or functions of each unit in the access network device 500 are respectively for implementing the corresponding flow of the access network device in the method 300 shown in fig. 7, and are not described herein for brevity.

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

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

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

Optionally, 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 in particular, may send information or data to other devices, or receive information or data sent by other devices.

The transceiver 630 may include a transmitter and a receiver, among others. Transceiver 630 may further include antennas, the number of which may be one or more.

Optionally, the communication device 600 may be specifically an access network device according to the embodiment of the present application, and the communication device 600 may implement a corresponding flow implemented by the access network device in each method according to the embodiment of the present application, which is not described herein for brevity.

Optionally, the communication device 600 may be specifically a mobile terminal/terminal device according to an embodiment of the present application, and the communication device 600 may implement corresponding processes implemented by the mobile terminal/terminal device in each method according to the embodiment of the present application, which are not described herein for brevity.

Fig. 11 is a schematic structural view of a chip of 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, chip 700 may also include memory 720. Wherein the processor 710 may call and run a computer program from the memory 720 to implement the method in an embodiment of the application.

Wherein the memory 720 may be a separate device from the processor 710 or may be integrated into the processor 710.

Optionally, the chip 700 may also include an input interface 730. The processor 710 may control the input interface 730 to communicate with other devices or chips, and in particular, may obtain information or data sent by 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, and in particular, may output information or data to other devices or chips.

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

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

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

Fig. 12 is a schematic block diagram of a communication system 800 provided by 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 functions implemented by the terminal device in the above method, and the access network device 820 may be used to implement the corresponding functions implemented by the access network device in the above method, which are not described herein for brevity.

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

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

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

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

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

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

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

Optionally, the computer program product may be applied to the access network device in the embodiment of the present application, and the computer program instructions cause the computer to execute corresponding flows implemented by the access network device in the methods in the embodiments of the present application, which are not described herein for brevity.

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

The embodiment of the application also provides a computer program.

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

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

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

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

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

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

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

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

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

Claims

1. A method of wireless communication, comprising:

the method comprises the steps that terminal equipment receives first configuration information sent by access network equipment, wherein the first configuration information is used for configuring various header compression configurations for a first Data Radio Bearer (DRB);

the terminal equipment performs header compression or decompression on the first DRB according to the first configuration information;

wherein the plurality of head compression configurations includes at least two of the following head compression configurations:

header compression configuration of ethernet frame structure header,

the ethernet frame structure serves the header compression configuration of the data units SDU.

2. The method according to claim 1, wherein the method further comprises:

The terminal equipment maps a plurality of data packets in the first DRB, wherein the plurality of data packets comprise data packets with an Ethernet frame structure with VLAN (virtual local area network) headers and data packets without VLAN headers;

and the packet data convergence protocol PDCP equipment of the terminal equipment determines the data packet with the VLAN character head Ethernet frame structure and/or the data packet without the VLAN character head Ethernet frame structure in the plurality of data packets according to the VLAN indication.

3. The method according to claim 2, wherein the VLAN indication is indicated by the access network device or is obtained by the terminal device through data flow information interaction between layers.

4. A method according to claim 2 or 3, wherein the terminal device header-compresses or decompresses the first DRB according to the first configuration information, comprising:

the PDCP device of the terminal device performs header compression or decompression on the plurality of data packets in a manner that header of an ethernet frame structure does not perform header compression.

5. A method according to claim 2 or 3, wherein the terminal device header-compresses or decompresses the first DRB according to the first configuration information, comprising:

And the PDCP equipment of the terminal equipment performs header compression or decompression of the Ethernet frame structure comprising the VLAN header on the data packet with the Ethernet frame structure comprising the VLAN header according to the VLAN indication, and performs header compression or decompression of the Ethernet frame structure not comprising the VLAN header on the data packet without the Ethernet frame structure comprising the VLAN header.

6. The method of claim 5, wherein the method further comprises:

the terminal equipment configures a first protocol data unit PDU of a first PDCP equipment to carry first indication information, wherein the first indication information is used for indicating the opposite end of the first PDCP equipment that the first PDU is subjected to header compression in a header compression mode comprising VLAN headers or in a header compression mode not comprising VLAN headers.

7. The method of claim 5, wherein the method further comprises:

the terminal equipment configures a first PDU of a first Radio Link Control (RLC) device to carry first indication information, wherein the first indication information is used for indicating the opposite end of the first RLC device that the first PDU is subjected to header compression in a header compression mode comprising VLAN headers or in a header compression mode not comprising VLAN headers.

8. A method according to claim 2 or 3, wherein the terminal device header-compresses or decompresses the first DRB according to the first configuration information, comprising:

the PDCP equipment of the terminal equipment adopts a mode of constructing a virtual VLAN to carry out header compression or decompression on the data packet of the Ethernet frame structure without VLAN headers in the plurality of data packets;

and the PDCP equipment of the terminal equipment performs header compression or decompression on the data packet with the Ethernet frame structure with the VLAN header in the plurality of data packets according to the VLAN mode.

9. The method of claim 8, wherein the method further comprises:

the terminal equipment configures a first PDU of a first PDCP equipment to carry first indication information, wherein the first indication information is used for indicating that the opposite end of the first PDCP equipment performs header compression in a header compression mode of a virtual VLAN (virtual VLAN) header or performs header compression in a header compression mode of a virtual VLAN header not adopted.

10. The method of claim 8, wherein the method further comprises:

the terminal equipment configures a first PDU of a first Radio Link Control (RLC) device to carry first indication information, wherein the first indication information is used for indicating that the opposite end of the first RLC device performs header compression in a header compression mode of a virtual VLAN (virtual VLAN) header or performs header compression in a header compression mode of a virtual VLAN header not adopted.

11. The method of claim 6, wherein the step of providing the first layer comprises,

the first indication information is carried on a reserved bit position in the first PDU; or alternatively

The first indication information is carried in a newly added bit field in the first PDU.

12. A method according to any of claims 1 to 3, characterized in that before the terminal device receives the first configuration information, the method further comprises:

the terminal equipment acquires first information through data flow information interaction performed between layers, wherein the first information comprises at least one of data packet identifiers corresponding to a plurality of data packets mapped to the first DRB, data packet arrangement sequence, data packet transmission time and VLAN indications of QoS data flows corresponding to the data packets, and whether the data packets comprise VLAN identifiers or not;

the terminal equipment sends the first information to the access network equipment, wherein the first information is used for determining the first configuration information by the access network equipment or core network equipment; or alternatively

The terminal equipment sends the first information to core network equipment, wherein the first information is used for determining the first configuration information by the core network equipment.

13. A method according to any of claims 1 to 3, characterized in that before the terminal device receives the first configuration information, the method further comprises:

and the terminal equipment reports the supporting capability of header compression and header decompression of the whole Ethernet frame structure, or respectively reports the supporting capability of header compression and header decompression of the Ethernet header and the data field, and is used for indicating whether the terminal equipment supports the header compression of the Ethernet frame structure and/or whether the terminal equipment supports the header compression of the Ethernet frame structure of the VLAN header.

14. A method of wireless communication, comprising:

the access network equipment sends first configuration information to the terminal equipment, wherein the first configuration information is used for configuring various header compression configurations for a first Data Radio Bearer (DRB);

header compression configuration of ethernet frame structure header,

15. The method of claim 14, wherein the method further comprises:

The access network equipment maps a plurality of data packets in the first DRB, wherein the plurality of data packets comprise data packets with an Ethernet frame structure with VLAN (virtual local area network) headers and data packets without VLAN headers;

and the packet data convergence protocol PDCP equipment of the access network equipment determines the data packet with the VLAN character head Ethernet frame structure and/or the data packet without the VLAN character head Ethernet frame structure in the plurality of data packets according to the VLAN indication.

16. The method of claim 15, wherein the VLAN indication is indicated by a core network device or is obtained by reporting by the access network device through a terminal device.

17. The method according to claim 15 or 16, characterized in that the method further comprises:

the PDCP device of the access network device performs header compression or decompression on the multiple data packets in a manner that header of an ethernet frame structure does not perform header compression.

18. The method according to claim 15 or 16, characterized in that the method further comprises:

and the PDCP equipment of the access network equipment performs header compression or decompression of the Ethernet frame structure comprising the VLAN header on the data packet with the Ethernet frame structure comprising the VLAN header according to the VLAN indication, and performs header compression or decompression of the Ethernet frame structure not comprising the VLAN header on the data packet without the Ethernet frame structure comprising the VLAN header.

19. The method of claim 18, wherein the method further comprises:

the access network device configures a first protocol data unit PDU of a first PDCP device to carry first indication information, wherein the first indication information is used for indicating the opposite end of the first PDCP device that the first PDU is subjected to header compression in a header compression mode comprising VLAN headers or in a header compression mode not comprising VLAN headers.

20. The method of claim 18, wherein the method further comprises:

the access network device configures a first PDU of a first Radio Link Control (RLC) device to carry first indication information, wherein the first indication information is used for indicating an opposite end of the first RLC device that the first PDU is subjected to header compression in a header compression mode comprising VLAN headers or in a header compression mode not comprising VLAN headers.

21. The method according to claim 15 or 16, characterized in that the method further comprises:

the PDCP equipment of the access network equipment adopts a mode of constructing a virtual VLAN to carry out header compression or decompression on the data packet of the Ethernet frame structure without VLAN headers in the plurality of data packets;

And the PDCP equipment of the access network equipment performs header compression or decompression on the data packet with the Ethernet frame structure with the VLAN headers in the plurality of data packets according to the VLAN mode.

22. The method of claim 21, wherein the method further comprises:

the access network device configures a first PDU of a first PDCP device to carry first indication information, wherein the first indication information is used for indicating that the opposite end of the first PDCP device performs header compression in a header compression mode of a virtual VLAN (virtual VLAN) header or performs header compression in a header compression mode of a virtual VLAN header not adopted.

23. The method of claim 21, wherein the method further comprises:

the access network device configures a first PDU of a first RLC device to carry first indication information, wherein the first indication information is used for indicating that the opposite end of the first RLC device performs header compression in a header compression mode of a virtual VLAN (virtual VLAN) header or performs header compression in a header compression mode of a virtual VLAN header not adopted.

24. The method of claim 19, wherein the step of determining the position of the probe comprises,

25. The method according to any of claims 14 to 16, 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 at least one of a packet identifier corresponding to a plurality of packets mapped to the first DRB, a packet arrangement sequence, a packet transmission time, a packet, a QoS data flow corresponding to the packet, and a VLAN indication of the QoS data flow corresponding to the packet.

26. The method of claim 25, wherein the first information is reported by the terminal device or the first information is indicated by a core network device.

27. The method according to any of claims 14 to 16, wherein before the access network device sends the first configuration information, the method further comprises:

the access network equipment receives the supporting capability of header compression and header decompression of the whole Ethernet frame structure reported by the terminal equipment and is used for indicating whether the terminal equipment supports the header compression of the Ethernet frame structure and/or whether the terminal equipment supports the header compression of the Ethernet frame structure of VLAN (virtual local area network) headers;

The access network device configures the header of the Ethernet frame structure for the first DRB without performing header compression configuration, or respectively performs header compression configuration for the header of the Ethernet structure and the data field which are supported or not supported by the first DRB, or configures the header compression configuration for the Ethernet structure which is supported or not supported by the first DRB, or configures the header compression configuration for the Ethernet structure which contains VLAN headers which is supported or not supported by the first DRB.

28. The method according to any of claims 14 to 16, wherein before the access network device sends the first configuration information, the method further comprises:

the access network device receives the supporting capability of header compression and header decompression of the Ethernet header and the data field, which are respectively reported by the terminal device, and is used for indicating whether the terminal device supports header compression of an Ethernet frame structure and/or whether the terminal device supports header compression of an Ethernet frame structure of a VLAN header;

the access network device performs header compression configuration for the header and the data field of the first DRB configured ethernet frame structure, or does not configure header compression configuration for the header of the ethernet structure for the first DRB, or configures header compression configuration for the ethernet structure with or without supporting VLAN headers for the first DRB.

29. 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;

header compression configuration of ethernet frame structure header,

30. The terminal device of claim 29, wherein the processing unit is further configured to:

and the Packet Data Convergence Protocol (PDCP) equipment controlling the terminal equipment determines the data packet with the VLAN character head Ethernet frame structure and/or the data packet without the VLAN character head Ethernet frame structure in the plurality of data packets according to the VLAN indication.

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

32. Terminal device according to claim 30 or 31, wherein the processing unit is specifically configured to:

and the PDCP equipment controlling the terminal equipment performs header compression or decompression on the plurality of data packets in a mode that the header of the Ethernet frame structure does not perform header compression.

33. Terminal device according to claim 30 or 31, wherein the processing unit is specifically configured to:

and controlling the PDCP equipment of the terminal equipment to perform header compression or decompression of the Ethernet frame structure comprising the VLAN header on the data packet with the Ethernet frame structure comprising the VLAN header according to the VLAN indication, and performing header compression or decompression of the Ethernet frame structure not comprising the VLAN header on the data packet without the Ethernet frame structure comprising the VLAN header.

34. The terminal device of claim 33, wherein the processing unit is further configured to:

the method comprises the steps that a first protocol data unit PDU of a first PDCP device is configured to carry first indication information, wherein the first indication information is used for indicating the opposite end of the first PDCP device that the first PDU is subjected to header compression in a header compression mode comprising VLAN headers or in a header compression mode not comprising VLAN headers.

35. The terminal device of claim 33, wherein the processing unit is further configured to:

the method comprises the steps of configuring a first PDU of a first Radio Link Control (RLC) device to carry first indication information, wherein the first indication information is used for indicating the opposite end of the first RLC device that the first PDU is subjected to header compression in a header compression mode comprising VLAN headers or in a header compression mode not comprising VLAN headers.

36. Terminal device according to claim 30 or 31, wherein the processing unit is specifically configured to:

controlling PDCP equipment of the terminal equipment to perform header compression or decompression on the data packets of the Ethernet frame structure without VLAN headers in the plurality of data packets in a mode of constructing virtual VLAN;

and controlling the PDCP equipment of the terminal equipment to perform header compression or decompression on the data packet with the Ethernet frame structure with the VLAN headers in the plurality of data packets according to the VLAN mode.

37. The terminal device of claim 36, wherein the processing unit is further configured to:

the method comprises the steps that a first PDU of a first PDCP device is configured to carry first indication information, wherein the first indication information is used for indicating that the opposite end of the first PDCP device performs header compression in a header compression mode of a virtual VLAN (virtual VLAN) header or performs header compression in a header compression mode of a virtual VLAN header not adopted.

38. The terminal device of claim 36, wherein the processing unit is further configured to:

the method comprises the steps of configuring a first PDU of a first Radio Link Control (RLC) device to carry first indication information, wherein the first indication information is used for indicating that the opposite end of the first RLC device performs header compression in a header compression mode of a virtual VLAN (virtual VLAN) header or performs header compression in a header compression mode of a virtual VLAN header not adopted.

39. The terminal device of claim 34, wherein the terminal device,

40. The terminal device according to any of the claims 29 to 31, characterized in that, before the communication unit receives the first configuration information,

the processing unit is further configured to obtain first information through data flow information interaction performed between layers, where the first information includes at least one of a data packet identifier corresponding to a plurality of data packets mapped to the first DRB, a data packet arrangement sequence, a data packet transmission time, and whether the data packet includes 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 for determining the first configuration information by the access network device or a core network device; or alternatively

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

41. A terminal device according to any of claims 29 to 31, wherein before the communication unit receives the first configuration information, the communication unit is further configured to report a capability of supporting header compression and header decompression for the whole ethernet frame structure, or to report a capability of supporting header compression and header decompression for the ethernet header and the data field, respectively, for indicating whether the terminal device supports header compression for the ethernet frame structure and/or header compression for the ethernet frame structure for the VLAN header.

42. An access network device, comprising:

a communication unit, configured to send first configuration information to a terminal device, where the first configuration information is used to configure multiple header compression configurations for a first data radio bearer DRB;

header compression configuration of ethernet frame structure header,

43. The access network device of claim 42, 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 a data packet without an ethernet frame structure with a VLAN header;

the processing unit is further configured to control the packet data convergence protocol PDCP device of the access network device to determine, according to the VLAN indication, a data packet of the ethernet frame structure having a VLAN header and/or a data packet of the ethernet frame structure not having a VLAN header in the plurality of data packets.

44. The access network device of claim 43, wherein the VLAN indication is indicated by a core network device or is obtained by the access network device via a terminal device report.

45. The access network device of claim 43 or 44, wherein the processing unit is further configured to:

and the PDCP equipment controlling the access network equipment performs header compression or decompression on the plurality of data packets in a mode that the header of the Ethernet frame structure does not perform header compression.

46. The access network device of claim 43 or 44, wherein the processing unit is further configured to:

and the PDCP equipment controlling the access network equipment performs header compression or decompression of the Ethernet frame structure comprising the VLAN headers on the data packet with the Ethernet frame structure comprising the VLAN headers according to the VLAN indication, and performs header compression or decompression of the Ethernet frame structure not comprising the VLAN headers on the data packet without the Ethernet frame structure comprising the VLAN headers.

47. The access network device of claim 46, wherein the processing unit is further configured to:

48. The access network device of claim 46, wherein the processing unit is further configured to:

49. The access network device of claim 43 or 44, wherein the processing unit is further configured to:

the PDCP equipment of the access network equipment is controlled to carry out header compression or decompression on the data packets of the Ethernet frame structure without VLAN headers in the plurality of data packets in a mode of constructing a virtual VLAN;

and controlling the PDCP equipment of the access network equipment to perform header compression or decompression on the data packet with the Ethernet frame structure with the VLAN headers in the plurality of data packets according to the VLAN mode.

50. The access network device of claim 49, wherein the processing unit is further configured to:

51. The access network device of claim 49, wherein the processing unit is further configured to:

52. The access network device of claim 47, wherein,

53. The access network device of any of claims 43-44, wherein the processing unit is further configured to, prior to the communication unit transmitting the first configuration information:

54. The access network device of claim 53, wherein the first information is reported by the terminal device or the first information is indicated by a core network device.

55. An access network device as recited in any one of claims 43-44, wherein, prior to the communication unit transmitting the first configuration information,

the communication unit is further configured to receive a supporting capability of header compression and header decompression for the whole ethernet frame structure reported by the terminal device, and is configured to instruct whether the terminal device supports header compression of the ethernet frame structure and/or whether the terminal device supports header compression of the ethernet frame structure of a 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 header of the ethernet frame structure and the data field with or without performing header compression configuration for the first DRB, or configure the header compression configuration of the ethernet frame structure with or without supporting the VLAN header for the first DRB.

56. An access network device as recited in any one of claims 43-44, wherein, prior to the communication unit transmitting the first configuration information,

The communication unit is further configured to receive the supporting capability of header compression and header decompression of the ethernet header and the data field, which are reported by the terminal device, and indicate whether the terminal device supports header compression of the ethernet frame structure and/or whether the terminal device supports header compression of the ethernet frame structure of the VLAN header;

the processing unit is further configured to perform header compression configuration for the header and the data field of the ethernet frame structure respectively, or not configure header compression configuration for the header of the ethernet structure for the first DRB, or configure header compression configuration for the ethernet structure with or without supporting VLAN headers for the first DRB.

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

58. An access network device, comprising: a processor and a memory for storing a computer program, the processor being for invoking and running the computer program stored in the memory, performing the method of any of claims 14 to 28.

59. A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any one of claims 1 to 13.

60. A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any of claims 14 to 28.

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

62. A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 14 to 28.