CN112740730B

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

Info

Publication number: CN112740730B
Application number: CN201880097274.3A
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-04-04
Anticipated expiration: 2038-09-29
Also published as: TW202021416A; CN112740730A; WO2020062181A1

Abstract

The embodiment of the application provides a wireless communication method, terminal equipment and access network equipment, which can realize header compression of Ethernet PDU carrying VLAN headers and not carrying VLAN headers. The method comprises the following steps: the method comprises the steps that terminal equipment receives first information sent by access network equipment, wherein the first information is used for indicating that first SDAP equipment correspondingly processes a data packet of an Ethernet frame structure comprising a VLAN header or indicating that the first SDAP equipment correspondingly processes a data packet of an Ethernet frame structure not comprising the VLAN header; the terminal device maps, to the first SDAP device, a packet of an Ethernet frame structure including a VLAN header or a packet of an Ethernet frame structure not including a VLAN header, according to the first information.

Description

Wireless communication method, terminal equipment and access network equipment

Technical Field

The embodiments of the present application relate to the field of communications, and in particular, to a wireless communication method, a terminal device, and an access network device.

Background

In a Long Term Evolution (LTE) system, a type of a Protocol Data Unit (PDU) session is an 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 is supported, 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 is corresponding to an IPv4 data packet (packets) and/or IPv6 packets; when the PDU Session type is Ethernet, the PDU Session corresponds to the Ethernet frame structure (frames).

In LTE and NR systems, a Public Network system, i.e., a Public Land Network based on a Public Land Mobile Network (PLMN), is generally deployed. Meanwhile, in some scenarios, such as office, home, factory, etc., in order to enable more secure and effective management, a local network is usually configured by a local user or administrator, and only authorized users who can access the local network have access rights.

In a scenario where a public Network system and a Local Network coexist, when a PDU session is an Ethernet frame, the Ethernet PDU may carry a Virtual Local Area Network (VLAN) header or may not carry a VLAN header, and corresponding Ethernet frame structures are different. The header compression algorithms used for the two PDUs are different during header compression. Therefore, how to implement header compression of Ethernet PDUs carrying VLAN headers and not carrying VLAN headers is an urgent 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 terminal equipment can map a Data packet of an Ethernet frame structure including a VLAN header or a Data packet of the Ethernet frame structure not including the VLAN header to Service Data Adaptation Protocol (SDAP) equipment, so that header compression of Ethernet PDUs carrying the VLAN header and not carrying the VLAN header can be realized.

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

the method comprises the steps that terminal equipment receives first information sent by access network equipment, wherein the first information is used for indicating that first SDAP equipment of the terminal equipment correspondingly processes a data packet of an Ethernet frame structure comprising a VLAN header or indicating that the first SDAP equipment correspondingly processes a data packet of an Ethernet frame structure not comprising the VLAN header;

and the terminal equipment maps the data packet of the Ethernet frame structure comprising the VLAN header or the data packet of the Ethernet frame structure not comprising the VLAN header to first SDAP equipment of the terminal equipment according to the first information.

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

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

the method comprises the steps that access network equipment sends first information to terminal equipment, wherein the first information is used for indicating that first SDAP equipment of the terminal equipment correspondingly processes a data packet of an Ethernet frame structure comprising a VLAN header or indicating that the first SDAP equipment of the terminal equipment correspondingly processes a data packet of an Ethernet frame structure not comprising the VLAN header.

In a third aspect, a terminal device is provided, configured to perform the method in the first aspect or any implementation manner thereof.

Specifically, the terminal device includes a functional module configured to execute the method in the first aspect or its implementation manner.

In a fourth aspect, an access network device is provided for executing the method in the second aspect or its implementation manners.

In particular, the access network device comprises functional modules for performing the methods of the second aspect or its implementations.

In a fifth aspect, a terminal device is provided that includes a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory to execute the method in the first aspect or each implementation manner thereof.

In a sixth aspect, an access network device is provided that includes a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory, and executing the method of the second aspect or each implementation mode thereof.

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

Specifically, the chip includes: a processor configured to call and run the computer program from the memory, so that the device on which the chip is installed performs the method in any one of the first aspect to the second aspect or the implementation manners thereof.

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

In a ninth aspect, there is provided a computer program product comprising computer program instructions to cause a computer to perform the method of any one of the first to second aspects or implementations thereof.

A tenth aspect provides a computer program that, when run on a computer, causes the computer to perform the method of any one of the first to second aspects or implementations thereof.

Through the technical scheme, the terminal equipment can map the data packet of the Ethernet frame structure comprising the VLAN header or the data packet of the Ethernet frame structure not comprising the VLAN header to the SDAP equipment, so that header compression of the Ethernet PDU carrying the VLAN header and not carrying the VLAN header can be realized.

Further, the end device may map the packet of the ethernet frame structure including the VLAN header or the packet of the ethernet frame structure not including the VLAN header to the SDAP device based on the configuration of the access network device.

Drawings

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

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

Fig. 3 is a schematic flow chart of another wireless communication method provided in an embodiment of the present application.

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

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

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

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

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

Detailed Description

Technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application without making any creative effort belong to the protection scope of the present application.

The technical scheme of the embodiment of the application can be applied to various communication systems, for example: a Global System for Mobile communications (GSM) System, a Code Division Multiple Access (CDMA) System, a Wideband Code Division Multiple Access (WCDMA) System, a General Packet Radio Service (GPRS), a Long Term Evolution (Long Term Evolution, LTE) System, an LTE Frequency Division Duplex (FDD) System, an LTE Time Division Duplex (TDD), a Universal Mobile Telecommunications System (UMTS), a Worldwide Interoperability for Microwave Access (WiMAX) communication System, or a 5G System.

Illustratively, a communication system 100 applied in the embodiment of the present application is shown in fig. 1. The communication system 100 may include a terminal device 110, and the terminal device 110 may be located within the coverage area of an access network device 120. As used herein, "terminal equipment" includes, but is not limited to, connections via wireline, such as Public Switched Telephone Network (PSTN), digital Subscriber Line (DSL), digital cable, direct cable connection; and/or another data connection/network; and/or via a Wireless interface, such as for a cellular Network, a 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 another terminal device arranged to receive/transmit communication signals; and/or Internet of Things (IoT) devices. A terminal device arranged to communicate over a wireless interface may be referred to as a "wireless communication terminal", "wireless terminal" or "mobile terminal". Examples of mobile terminals include, but are not limited to, satellite or cellular telephones; personal Communications Systems (PCS) terminals that may combine cellular radiotelephones with data processing, facsimile, and data Communications capabilities; PDAs that may include radiotelephones, pagers, internet/intranet access, web browsers, notepads, calendars, and/or Global Positioning System (GPS) receivers; and conventional laptop and/or palmtop receivers or other electronic devices that include a radiotelephone transceiver. Terminal Equipment 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 phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with Wireless communication capability, a computing device or other processing device connected to a Wireless modem, a vehicle mounted 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, a 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. Optionally, the Access Network device 120 may be a Base Transceiver Station (BTS) in a GSM system or a CDMA system, a Base Station (NodeB, NB) in a WCDMA system, an evolved Node B (eNB or eNodeB) in an LTE system, or a wireless controller in a Cloud Radio Access Network (CRAN), or the Network device may be a Mobile switching center, a relay Station, an Access point, a vehicle-mounted 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 Public Land Mobile Network (PLMN) for future evolution, or the like.

The wireless communication system 100 also includes 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 (AMF), which is responsible for Access and Mobility Management and has functions of authenticating, switching, updating location, and the like for a user. Also for example, the Session Management Function (SMF) is responsible for Session Management, including establishment, modification, release, and the like of a Packet Data Unit (PDU) Session. For another example, a 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 another system.

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

In this 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 transmission power, and are suitable for providing high-rate data transmission services.

It should be understood that a header compression and decompression function is introduced into a Packet Data Convergence Protocol (PDCP) Protocol to support different Data Radio Bearers (DRBs) and different header compression and header compression parameters are used according to configured header compression configuration (profile). The PDCP uses a Robust information header compression (ROHC) protocol, and supported header compression protocols (protocols) and profiles (profiles) are shown in table 1 below. Specifically, as shown in table 1 below, the compression object of the different header compression configurations may be at least one of Real-time Transport Protocol (RTP), IP, user Datagram Protocol (UDP), encapsulated Security Payload (ESP), and No compression (No compression), and the compression policy may specifically be an RFC (Request For messages) series file as shown in table 1 below.

TABLE 1

Configuration identification	Compression object (Usage)	Compression strategy (Reference)
			0x0000	Without 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 embodiments of the present application may be used in a public land network or a local network.

Wherein, the public land network can be a public land network based on PLMN.

The local network may also be referred to as a local area network or a private network, and is generally disposed in an office setting, a home setting, or a factory, and can be managed more efficiently and safely, and a local user or manager typically lays out the local network. Typically, authorized access-capable users have access to the local network.

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

Optionally, the local network may use an unlicensed frequency band for communication, or may share a licensed frequency band with a 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 (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 are shared.

Optionally, in this embodiment 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 are shared.

It should be noted that, 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, when a PDU session is Ethernet frames, the Ethernet PDU may or may not carry a VLAN header, and corresponding Ethernet frame structures are different. The header compression algorithms used for the two PDUs are different during header compression. At present, no distinguishing process is performed for this scenario, so header compression of Ethernet PDUs carrying VLAN headers and Ethernet PDUs not carrying VLAN headers cannot be achieved. Based on the above problem, the present application proposes a method for compressing and configuring Ethernet frame headers.

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

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

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

s210, a terminal device receives first information sent by an access network device, where the first information is used to indicate that a first SDAP device of the terminal device correspondingly processes a data packet of an ethernet frame structure including a VLAN header or indicate that the first SDAP device of the terminal device correspondingly processes a data packet of an ethernet frame structure not including a VLAN header;

s220, the terminal device maps the data packet of the ethernet frame structure including the VLAN header or the data packet of the ethernet frame structure not including the VLAN header to a first SDAP device of the terminal device according to the first information.

Optionally, in this embodiment of the application, the terminal device may also receive the first information sent by the core network device, that is, the core network device may directly configure the first information for the terminal device, and the core network device may be, for example, an AMF device or a UPF device. Similarly, the following description of the access network device applies equally to the core network device. The following is specifically described by taking an example that the terminal device receives the first information from the access network device.

It should be noted that the first SDAP device is disposed on the terminal device side. Meanwhile, the present application is described by taking only the first SDAP device deployed on the terminal device side as an example, and other SDAP devices deployed on the terminal device side are also applicable.

It should be further noted that, the first SDAP device correspondingly processes mapping Quality of Service Flow (QoS Flow) to Data Radio Bearer (DRB).

Optionally, in this embodiment of the present application, a first SDAP device of the terminal device delivers the mapped data packet to a first PDCP device of the terminal device;

the first PDCP device of the terminal device performs header compression on a data packet including a VLAN header by adopting a header compression mode corresponding to the VLAN header, or performs header compression on a data packet not including the VLAN header by adopting a header compression mode corresponding to the VLAN header.

It should be noted that the first PDCP device is disposed at the terminal device side. Meanwhile, the present application only takes the first PDCP device deployed at the terminal device side as an example for description, and other PDCP devices deployed at the terminal device side are also applicable.

Optionally, in this embodiment of the present application, the first Information may be Radio Resource Control (RRC) signaling or System Information Block (SIB) Information.

Specifically, the first information includes first indication information for the first SDAP device to process a packet of an ethernet frame structure including a VLAN header or indicating that the first SDAP device to process a packet of an ethernet frame structure not including a VLAN header. Further, the terminal device maps, to the first SDAP device, a packet of an ethernet frame structure that includes a VLAN header or a packet of an ethernet frame structure that does not include a VLAN header according to the first indication information.

Optionally, if the first information is RRC signaling, the first indication information may be carried in DRB configuration information, for example, a DRB-ToAddMod message, and occupy 1bit (bit) resource.

Optionally, if the first information is RRC signaling, the first indication information may be carried in the SDAP configuration information and occupy 1bit of resources, and the SDAP configuration information may be, for example, an SDAP-Config message.

Optionally, in this embodiment of the present application, the terminal device may extend the DRB identifier from 1 to 32 to 1 to 64.

It should be noted that, extending the DRB identifier from 1 to 32 to 1 to 64 can satisfy the requirement of identifying the data packet of the ethernet frame structure including the VLAN header and the data packet of the ethernet frame structure not including the VLAN header.

Optionally, in this embodiment of the present application, the first information may further include first PDCP configuration information, where the first PDCP configuration information is used to configure a packet of an ethernet frame structure including a VLAN header to support a header compression configuration of a VLAN, and/or the first PDCP configuration information is used to configure a packet of an ethernet frame structure not including a VLAN header to support a header compression configuration of a VLAN.

That is, the access network device configures header compression profile that supports the VLAN header for a packet of an ethernet frame structure including the VLAN header, and configures header compression profile that does not support the VLAN header for a packet of an ethernet frame structure that does not include the VLAN header.

Specifically, the terminal device may perform header compression or decompression for supporting a VLAN on a packet of an ethernet frame structure including a VLAN header and/or perform header compression or decompression for not supporting a VLAN on a packet of an ethernet frame structure not including a VLAN header according to the first PDCP configuration information.

Optionally, in this embodiment of the present application, the first information includes first SDAP configuration information, where the first SDAP configuration information is used to configure a first default DRB and/or a second default DRB, the first default DRB is used to map a packet of an ethernet frame structure that includes a VLAN header, and the second default DRB is used to map a packet of an ethernet frame structure that does not include a VLAN header.

It should be noted that the first default DRB or the second default DRB may be an original default DRB stored in the terminal device side, that is, the access network device may only newly configure one default DRB, and certainly, the access network device may also configure two new default DRBs.

Optionally, the first SDAP configuration information is for all the SDAP devices on the terminal device side.

Specifically, the terminal device maps, to the first SDAP device, a packet of an ethernet frame structure including a VLAN header or a packet of an ethernet frame structure not including a VLAN header according to the first SDAP configuration information and the VLAN-related information.

For example, the first default DRB is configured at the first SDAP device, the end device maps the data packets of the ethernet frame structure including the VLAN header to the first SDAP device.

For another example, if the first default DRB is configured at the first SDAP device, the terminal device maps the data packet of the ethernet frame structure including the VLAN header to the first SDAP device; and/or the terminal device maps the data packet of the Ethernet frame structure without the VLAN header to other DRBs or one of other DRBs corresponding to the same PDU-session, which can map the data packet of the Ethernet frame structure with the VLAN header, or the terminal device maps the data packet of the Ethernet frame structure without the VLAN header to the original default DRB stored at the terminal device side.

For another example, if the second default DRB is configured at the first SDAP device, the end device maps the data packet of the ethernet frame structure without the VLAN header to the first SDAP device.

For another example, if the second default DRB is configured at the first SDAP device, the terminal device maps the data packet of the ethernet frame structure without the VLAN header to the first SDAP device; and/or the terminal device maps the data packet of the Ethernet frame structure including the VLAN header to other DRBs or one of other DRBs corresponding to the same PDU-session, which can map the data packet of the Ethernet frame structure not including the VLAN header, or the terminal device maps the data packet of the Ethernet frame structure including the VLAN header to the original default DRB stored at the terminal device side.

For another example, if the first default DRB is configured at the first SDAP device and the second default DRB is configured at the second SDAP device, the terminal device may map the data packet of the ethernet frame structure including the VLAN header to the first SDAP device, or map the data packet of the ethernet frame structure not including the VLAN header to the second SDAP device.

It should be noted that the first SDAP device and the second SDAP device are the same device and correspond to different PDCP entities;

or the first SDAP device and the second SDAP device are different devices.

Optionally, the VLAN related information is a mapping relationship between a QoS FloW identifier and a VLAN, or is ethernet PDU information including VLAN information. The VLAN related information may be preconfigured, may be notified by the network side, or may be obtained by interaction between user layers.

Optionally, as an example, if a first default DRB is configured at the first SDAP device and the first default DRB is used to map data packets of an ethernet frame structure including VLAN headers, the terminal device maps the QoS data flow to the DRB according to a first rule,

the first rule is to perform header compression of an Ethernet frame structure supporting VLAN on the first default DRB, and select a DRB not supporting VLAN to perform header compression of an Ethernet frame structure not supporting VLAN.

Alternatively, as another example, if a second default DRB is configured at the first SDAP device and the second default DRB is used to map data packets of ethernet frame structure that do not include VLAN headers, the terminal device maps the QoS data flow to the DRB according to a second rule,

the second rule is to perform header compression of the ethernet frame structure that does not support the VLAN on the second default DRB, and select one DRB that supports the VLAN to perform header compression of the ethernet frame structure that supports the VLAN.

Optionally, as another example, if the first SDAP device is configured with a first default DRB for mapping data packets of the ethernet frame structure that include the VLAN header or a second default DRB for mapping data packets of the ethernet frame structure that do not include the VLAN header, the terminal device maps the QoS data stream to the DRB according to a third rule,

the third rule is that one DRB supporting VLAN is selected as an alternative for header compression of an ethernet frame structure supporting VLAN, and one DRB not supporting VLAN is selected as an alternative for header compression of an ethernet frame structure not supporting VLAN.

In the above example, the terminal device may have a mapping relationship between the uplink QoS Flow and the DRB, or may not have a mapping relationship between the uplink QoS Flow and the DRB.

Optionally, in this embodiment of the application, before receiving the first information, the terminal device reports support capabilities for header compression and header compression of an entire ethernet frame structure, or reports support capabilities for header compression and header compression of an ethernet header and a data field, respectively, to indicate whether the terminal device supports header compression of an ethernet frame structure and/or header compression of an ethernet frame structure of a VLAN header.

It should be noted that the information reported by the terminal device is used to assist the access network device to determine the first information.

Therefore, in this embodiment of the present application, the terminal device may map the packet of the Ethernet frame structure including the VLAN header or the packet of the Ethernet frame structure not including the VLAN header to the SDAP device, thereby achieving header compression of the Ethernet PDU carrying the VLAN header and the Ethernet PDU not carrying the VLAN header.

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

s310, the access network device sends first information to the terminal device, where the first information is used to indicate that the first SDAP device of the terminal device correspondingly processes a data packet of an ethernet frame structure that includes a VLAN header or indicate that the first SDAP device of the terminal device correspondingly processes a data packet of an ethernet frame structure that does not include a VLAN header.

Optionally, in this embodiment of the present application, the core network device may also send the first information, that is, the core network device may directly configure the first information for the terminal device, and the core network device may be, for example, an AMF device or an UPF device. Similarly, the following description of the access network device applies equally to the core network device. The following is specifically described by taking an example that the access network device sends the first information.

Optionally, in this embodiment of the present application, the first information includes first indication information, where the first indication information is used for the first SDAP device to correspondingly process a packet of an ethernet frame structure that includes a VLAN header or indicates that the first SDAP device to correspondingly process a packet of an ethernet frame structure that does not include a VLAN header.

Optionally, the first information is RRC signaling or SIB information.

Optionally, if the first information is an RRC signaling, the first indication information is carried in DRB configuration information or SDAP configuration information. For example, the first indication information occupies 1-bit resource.

Optionally, the access network device extends the DRB identity from 1 to 32 to 1 to 64.

Optionally, in this embodiment of the present application, the first information further includes first PDCP configuration information, where the first PDCP configuration information is used to configure the terminal device to configure the data packet of the ethernet frame structure including the VLAN header to support a header compression configuration of the VLAN, and/or the first PDCP configuration information is used to configure the data packet of the ethernet frame structure not including the VLAN header to support a header compression configuration of the VLAN.

Optionally, in this embodiment of the present application, the first information includes first SDAP configuration information, where the first SDAP configuration information is used to configure a first default DRB and/or a second default DRB, the first default DRB is used to map data packets of an ethernet frame structure that includes a VLAN header, and the second default DRB is used to map data packets of an ethernet frame structure that does not include a VLAN header.

Optionally, the VLAN related information is a mapping relationship between a QoS Flow identifier and a VLAN, or is ethernet PDU information including VLAN information. The VLAN related information may be preconfigured, or notified by the network side, or obtained by interaction between user layers.

Optionally, in this embodiment of the application, before the access network device sends the first information, the access network device receives, by the terminal device, support capabilities for header compression and header compression of an entire ethernet frame structure, or reports support capabilities for header compression and header compression of an ethernet header and a data field, respectively, where the support capabilities are used to indicate 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.

It should be noted that the terminal device may report, in a capability reporting manner, the support capabilities for header compression and header compression of the whole ethernet frame structure, or report the support capabilities for header compression and header compression of the ethernet header and the data field, respectively.

Optionally, in this embodiment, before the access network device sends the first information, the access network device determines the first information according to at least one of a user capability, a QoS data flow, and a VLAN indication, where the user capability is used to indicate 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, and the VLAN indication is used to indicate whether an ethernet frame structure of a PDU session data flow includes a VLAN field.

Optionally, the user capability is reported by the terminal device, and the VLAN indicator is obtained from a core network device.

For example, the VLAN designation is acquired by an Access network device through a User Plane Function (UPF) device or an Access and Mobility Management Function (AMF) device.

Optionally, in this embodiment of the present application, the access network device determines a service mapping and configuration criterion according to information such as user capability, qoS, VLAN indication, and the like, and configures the SDAP configuration and the PDCP configuration of each DRB. The DRB is configured to map only one Ethernet frame type, i.e. either an Ethernet frame type containing a VLAN header or a type not containing Ethernet frames.

For example, traffic mapping and configuration criteria include, but are not limited to, the following:

data flows of the same or similar QoS characteristics can be mapped into one DRB;

the data flow corresponding to the Ethernet frame containing the VLAN header cannot be mapped to the same DRB with the data flow corresponding to the Ethernet frame not containing the VLAN header;

data flows mapped to different ports of the same PDU session cannot be mapped to one DRB.

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

Fig. 4 shows a schematic block diagram of a terminal device 400 according to an embodiment of the application. As shown in fig. 4, the terminal apparatus 400 includes:

a communication unit 410, configured to receive first information sent by an access network device, where the first information is used to indicate that a first SDAP device of the terminal device correspondingly processes a packet of an ethernet frame structure that includes a VLAN header or indicate that the first SDAP device of the terminal device correspondingly processes a packet of an ethernet frame structure that does not include a VLAN header;

a processing unit 420, configured to map, according to the first information, a packet of an ethernet frame structure including a VLAN header or a packet of an ethernet frame structure not including a VLAN header to a first SDAP device of the terminal device.

Optionally, the processing unit 420 is further configured to:

controlling a first SDAP device of the terminal device to deliver the mapped data packet to a first PDCP device of the terminal device;

and controlling the first PDCP equipment of the terminal equipment to perform header compression on the data packet including the VLAN header by adopting a header compression mode corresponding to the VLAN header, or performing header compression on the data packet not including the VLAN header by adopting a header compression mode not including the VLAN header.

Optionally, the first information includes first indication information, where the first indication information is used to indicate that the first SDAP device of the terminal device correspondingly processes a packet of an ethernet frame structure that includes a VLAN header or indicate that the first SDAP device of the terminal device correspondingly processes a packet of an ethernet frame structure that does not include a VLAN header;

the processing unit 420 is specifically configured to:

and mapping the data packet of the Ethernet frame structure comprising the VLAN header or the data packet of the Ethernet frame structure not comprising the VLAN header to a first SDAP device of the terminal device according to the first indication information.

Optionally, the first information is RRC signaling or SIB information.

Optionally, if the first information is an RRC signaling, the first indication information is carried in DRB configuration information or SDAP configuration information.

Optionally, the first indication information occupies 1-bit resource.

Optionally, the processing unit 420 is further configured to extend the DRB flag from 1 to 32 to 1 to 64.

Optionally, the first information further includes first PDCP configuration information, where the first PDCP configuration information is used to configure, with header compression that supports VLAN, a packet of an ethernet frame structure that includes a VLAN header, and/or the first PDCP configuration information is used to configure, with header compression that does not support VLAN, a packet of an ethernet frame structure that does not include a VLAN header.

Optionally, the first information includes first SDAP configuration information, the first SDAP configuration information is used to configure a first default DRB and/or a second default DRB, the first default DRB is used to map data packets of an ethernet frame structure that include a VLAN header, and the second default DRB is used to map data packets of an ethernet frame structure that do not include a VLAN header;

the processing unit 420 is specifically configured to:

and mapping the data packet of the Ethernet frame structure comprising the VLAN header or the data packet of the Ethernet frame structure not comprising the VLAN header to first SDAP equipment of the terminal equipment according to the first SDAP configuration information and the VLAN related information.

Optionally, the VLAN related information is mapping relationship between QoS Flow identifiers and VLANs, or is ethernet PDU information including VLAN information. The VLAN related information may be preconfigured, or notified by the network side, or obtained by interaction between user layers.

Optionally, if a first default DRB is configured at the first SDAP device of the terminal device, and the first default DRB is used for mapping the data packet of the ethernet frame structure including the VLAN header, the processing unit 420 is further configured to map the QoS data stream to the DRB according to a first rule,

Optionally, if a second default DRB is configured at the first SDAP device of the terminal device, and the second default DRB is used to map the data packet of the ethernet frame structure without the VLAN header, the processing unit 420 is further configured to map the QoS data stream to the DRB according to a second rule,

the second rule is to perform header compression of an ethernet frame structure that does not support VLAN on the second default DRB, and select one DRB that supports VLAN to perform header compression of an ethernet frame structure that supports VLAN.

Optionally, if a first default DRB or a second default DRB is configured at the first SDAP device of the terminal device, and the first default DRB is used to map the data packets of the ethernet frame structure including the VLAN header, and the second default DRB is used to map the data packets of the ethernet frame structure not including the VLAN header, the processing unit 420 is further configured to map the QoS data stream to the DRB according to a third rule,

the third rule is that one DRB supporting VLAN is selected to be replaced to perform header compression of the Ethernet frame structure supporting VLAN, and one DRB not supporting VLAN is selected to be performed header compression of the Ethernet frame structure not supporting VLAN.

Optionally, before the communication unit 410 receives the first information, the communication unit 410 is further configured to report support capabilities of header compression and header compression of an entire ethernet frame structure, or report support capabilities of header compression and header compression of an ethernet header and a data field, respectively, and indicate whether the terminal device supports header compression of an ethernet frame structure and/or header compression of an ethernet frame structure of a VLAN header.

It should be understood that the terminal device 400 according to the embodiment of the present application may correspond to a terminal device in the embodiment of the method of the present application, and the above and other operations and/or functions of each unit in the terminal device 400 are respectively for implementing a corresponding flow of the terminal device in the method 200 shown in fig. 2, and are not described herein again for brevity.

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

a communication unit 510, configured to send first information to a terminal device, where the first information is used to indicate that a first SDAP device of the terminal device correspondingly processes a data packet of an ethernet frame structure that includes a VLAN header or indicate that the first SDAP device of the terminal device correspondingly processes a data packet of an ethernet frame structure that does not include a VLAN header.

Optionally, the first information includes first indication information, where the first indication information is used for the first SDAP device to correspondingly process a packet of an ethernet frame structure that includes a VLAN header or indicates that the first SDAP device to correspondingly process a packet of an ethernet frame structure that does not include a VLAN header.

Optionally, the first information is RRC signaling or SIB information.

Optionally, the first indication information occupies 1-bit resource.

Optionally, the access network device 500 further includes:

a processing unit 520, configured to extend the DRB flag from 1 to 32 to 1 to 64.

Optionally, the first information further includes first PDCP configuration information, where the first PDCP configuration information is used to configure that the terminal device adopts a header compression configuration supporting VLAN for a packet of an ethernet frame structure including a VLAN header, and/or the first PDCP configuration information is used to configure that the terminal device adopts a header compression configuration not supporting VLAN for a packet of an ethernet frame structure not including a VLAN header.

Optionally, the first information includes first SDAP configuration information, where the first SDAP configuration information is used to configure a first default DRB and/or a second default DRB, the first default DRB is used to map data packets of an ethernet frame structure that includes a VLAN header, and the second default DRB is used to map data packets of an ethernet frame structure that does not include a VLAN header.

Optionally, before the communication unit 510 sends the first information, the communication unit 510 is further configured to receive a support capability of header compression and header compression of an entire ethernet frame structure reported by the terminal device, or report a support capability of header compression and header compression of an ethernet header and a data field, respectively, to indicate 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.

Optionally, before the communication unit 510 sends the first information, the access network device 500 further includes:

a processing unit 520, configured to determine the first information according to at least one of a user capability, a QoS data flow, and a VLAN indication, where the user capability is used to indicate 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, and the VLAN indication is used to indicate whether an ethernet frame structure of a PDU session data flow includes a VLAN field.

It should be understood that the access network device 500 according to the embodiment of the present application may correspond to an access network device in the embodiment of the method of the present application, and the above and other operations and/or functions of each unit in the access network device 500 are respectively for implementing a corresponding flow of the access network device in the method 300 shown in fig. 3, and are not described herein again for brevity.

Fig. 6 is a schematic structural diagram of a communication device 600 according to an embodiment of the present application. The communication device 600 shown in fig. 6 comprises a processor 610, and the processor 610 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. 6, the communication device 600 may further include a memory 620. From the memory 620, the processor 610 may call and run a computer program to implement the method in the embodiment of the present 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. 6, the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, and specifically, may transmit information or data to the other devices or receive information or data transmitted by the other devices.

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

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

Optionally, the communication device 600 may specifically be a mobile terminal/terminal device in this embodiment, and the communication device 600 may implement a corresponding process implemented by the mobile terminal/terminal device in each method in this embodiment, which is not described herein again for brevity.

Fig. 7 is a schematic structural diagram of a chip of an embodiment of the present application. The chip 700 shown in fig. 7 includes a processor 710, and the processor 710 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in fig. 7, the chip 700 may further include a memory 720. From the memory 720, the processor 710 can call and run a computer program to implement the method in the embodiment of the present application.

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 further 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 transmitted 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 the 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 process implemented by the access network device in each method in the embodiment of the present application, and for brevity, details are not described here again.

Optionally, the chip may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, and for brevity, details are not described here again.

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

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

The terminal device 810 may be configured to implement the corresponding function implemented by the terminal device in the foregoing method, and the access network device 820 may be configured to implement the corresponding function implemented by the access network device in the foregoing method, which is not described herein again for brevity.

It should be understood that the processor of the embodiments 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 performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The Processor may be a general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, or discrete hardware components. The various methods, steps, and logic blocks disclosed 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 directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.

It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of example, but not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), dynamic Random Access Memory (DRAM), synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), double Data Rate Synchronous Dynamic random access memory (DDR SDRAM), enhanced Synchronous SDRAM (ESDRAM), synchronous link SDRAM (SLDRAM), and Direct Rambus 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 memories are exemplary but not limiting illustrations, for example, the memories in the embodiments of the present application may also be Static Random Access Memory (SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (enhanced SDRAM, ESDRAM), synchronous Link DRAM (SLDRAM), direct Rambus RAM (DR RAM), and the like. That is, the memory in the 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 the 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 enables the computer to execute the corresponding process implemented by the access network device in each method in the embodiment of the present application, which is not described herein again for brevity.

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

Embodiments of the present application also provide a computer program product, including 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 instruction enables the computer to execute a corresponding process implemented by the access network device in each method of the embodiment of the present application, which is not described herein again for brevity.

Optionally, the computer program product may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program instruction causes the computer to execute a corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein again 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 enabled to execute a corresponding process implemented by the access network device in each method in the embodiment of the present application, and for brevity, details are not described here again.

Optionally, the computer program may be applied to the mobile terminal/terminal device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein again 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 implementation. 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 is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed 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 can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

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

The functions may be stored in a computer-readable storage medium if they are implemented in the form of software functional units and sold or used as separate products. Based on such understanding, the technical solutions of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by 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 wireless communication method is characterized in that when a Protocol Data Unit (PDU) session is an Ethernet frame, one Ethernet PDU carries a Virtual Local Area Network (VLAN) header, the other Ethernet PDU does not carry the VLAN header, and header compression algorithms used by the two Ethernet PDUs are different, the method comprises the following steps:

the method comprises the steps that terminal equipment receives first information sent by access network equipment, wherein the first information is used for indicating that first Service Data Adaptation Protocol (SDAP) equipment of the terminal equipment correspondingly processes a data packet of an Ethernet frame structure comprising a VLAN (virtual local area network) header or indicating that the first SDAP equipment correspondingly processes a data packet of an Ethernet frame structure not comprising the VLAN header;

the terminal equipment maps the data packet of the Ethernet frame structure comprising the VLAN header or the data packet of the Ethernet frame structure not comprising the VLAN header to first SDAP equipment of the terminal equipment according to the first information;

the first SDAP equipment of the terminal equipment delivers the mapped data packet to first Packet Data Convergence Protocol (PDCP) equipment of the terminal equipment;

and the first PDCP equipment of the terminal equipment performs header compression on the data packet including the VLAN header by adopting a header compression mode corresponding to the VLAN header, and performs header compression on the data packet not including the VLAN header by adopting a header compression mode corresponding to the VLAN header.

2. The method according to claim 1, wherein the first information includes first indication information indicating that the first SDAP device of the terminal device processes the data packet of the Ethernet frame structure including the VLAN header or indicating that the first SDAP device of the terminal device processes the data packet of the Ethernet frame structure not including the VLAN header;

the terminal device maps, according to the first information, a packet of an ethernet frame structure including a VLAN header or a packet of an ethernet frame structure not including a VLAN header to a first SDAP device of the terminal device, including:

and the terminal equipment maps the data packet of the Ethernet frame structure comprising the VLAN header or the data packet of the Ethernet frame structure not comprising the VLAN header to first SDAP equipment of the terminal equipment according to the first indication information.

3. The method of claim 2, wherein the first information is Radio Resource Control (RRC) signaling or System Information Block (SIB) information.

4. The method of claim 3, wherein the first indication information is carried in DRB configuration information or SDAP configuration information if the first information is RRC signaling.

5. The method of claim 4, wherein the first indication information occupies 1-bit resource.

6. The method according to any one of claims 2 to 5, further comprising:

the terminal equipment expands the DRB identification from 1-32 to 1-64.

7. The method according to any one of claims 2 to 5, wherein the first information further comprises first PDCP configuration information, wherein the first PDCP configuration information is used for enabling the data packet of the Ethernet frame structure including the VLAN header to adopt a header compression configuration supporting VLAN, and/or the first PDCP configuration information is used for enabling the data packet of the Ethernet frame structure not including the VLAN header to adopt a header compression configuration not supporting VLAN.

8. The method of claim 1, wherein the first information comprises first SDAP configuration information, wherein the first SDAP configuration information is used to configure a first default DRB for mapping data packets of an Ethernet frame structure that include VLAN headers and/or a second default DRB for mapping data packets of an Ethernet frame structure that do not include VLAN headers;

and the terminal equipment maps the data packet of the Ethernet frame structure comprising the VLAN header or the data packet of the Ethernet frame structure not comprising the VLAN header to first SDAP equipment of the terminal equipment according to the first SDAP configuration information and the VLAN related information.

9. The method of claim 8, wherein the VLAN related information is a mapping of a quality of service (QoS) data flow identifier to a VLAN or Ethernet PDU information including VLAN information.

10. The method of any of claims 2-5 and 8-9, wherein if a first default DRB is configured at a first SDAP device of the end device and the first default DRB is used to map packets of an ethernet frame structure that include VLAN headers, the method further comprises:

the terminal device maps the QoS data flow to the DRB according to a first rule,

11. The method of any of claims 2-5 and 8-9, wherein if a second default DRB is configured at the first SDAP device of the end device and the second default DRB is used to map packets of the ethernet frame structure that do not include a VLAN header, the method further comprises:

the terminal device maps the QoS data flow to the DRB according to a second rule,

12. The method of any of claims 2-5 and 8-9, wherein if a first default DRB or a second default DRB is configured at a first SDAP device of the end device, and the first default DRB is used for mapping data packets of an ethernet frame structure that include VLAN headers, the second default DRB is used for mapping data packets of an ethernet frame structure that do not include VLAN headers, the method further comprising:

the terminal device maps the QoS data flow to the DRB according to a third rule,

13. The method according to any of claims 1 to 5 and 8, 9, wherein before the terminal device receives the first information, the method further comprises:

the terminal device reports support capabilities for header compression and header compression of an entire ethernet frame structure, or reports support capabilities for header compression and header compression of an ethernet header and a data field, respectively, and is used for indicating whether the terminal device supports header compression of an ethernet frame structure and/or supports header compression of an ethernet frame structure of a VLAN header.

14. A wireless communication method is characterized in that when a Protocol Data Unit (PDU) session is an Ethernet frame, one Ethernet PDU carries a Virtual Local Area Network (VLAN) header, the other Ethernet PDU does not carry the VLAN header, and header compression algorithms used by the two Ethernet PDUs are different, the method comprises the following steps:

the method comprises the steps that access network equipment sends first information to terminal equipment, wherein the first information is used for indicating that first Service Data Adaptation Protocol (SDAP) equipment of the terminal equipment correspondingly processes a data packet of an Ethernet frame structure comprising a Virtual Local Area Network (VLAN) header or indicating that first SDAP equipment of the terminal equipment correspondingly processes a data packet of an Ethernet frame structure not comprising a VLAN header, so that the terminal equipment maps the data packet of the Ethernet frame structure comprising the VLAN header or the data packet of the Ethernet frame structure not comprising the VLAN header to the first SDAP equipment of the terminal equipment according to the first information; enabling a first SDAP device of the terminal device to deliver the mapped data packet to a first Packet Data Convergence Protocol (PDCP) device of the terminal device; and enabling the first PDCP device of the terminal device to perform header compression on the data packet including the VLAN header in a header compression mode corresponding to the VLAN header, and performing header compression on the data packet not including the VLAN header in a header compression mode corresponding to the VLAN header.

15. The method of claim 14, wherein the first information comprises first indication information indicating that the first SDAP device of the terminal device is handling packets with an Ethernet frame structure that include VLAN headers or indicating that the first SDAP device of the terminal device is handling packets with an Ethernet frame structure that does not include VLAN headers.

16. The method of claim 15, wherein the first information is Radio Resource Control (RRC) signaling or System Information Block (SIB) information.

17. The method of claim 16, wherein the first indication information is carried in Data Radio Bearer (DRB) configuration information or SDAP configuration information if the first information is RRC signaling.

18. The method of claim 17, wherein the first indication information occupies 1-bit resource.

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

the access network equipment expands the DRB identification from 1-32 to 1-64.

20. The method according to any one of claims 15 to 18, wherein the first information further comprises first packet data convergence protocol, PDCP, configuration information for configuring the terminal device to adopt a VLAN-capable header compression configuration for packets of an ethernet frame structure including a VLAN header, and/or to adopt a VLAN-incapable header compression configuration for packets of an ethernet frame structure not including a VLAN header.

21. The method of claim 14, wherein the first information comprises first SDAP configuration information, wherein the first SDAP configuration information is used to configure a first default DRB for mapping data packets of an Ethernet frame structure that include VLAN headers and/or a second default DRB for mapping data packets of an Ethernet frame structure that do not include VLAN headers.

22. The method of claim 21 wherein the VLAN related information is a mapping of a quality of service QoS data flow identifier to a VLAN or ethernet PDU information including VLAN information.

23. The method according to any of claims 14 to 18 and 21, 22, wherein before the access network device sends the first information, the method further comprises:

and the access network equipment receives the support capability of the whole header compression and the header compression of the Ethernet frame structure reported by the terminal equipment, or respectively reports the support capability of the header compression and the header compression 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 supports the header compression of the Ethernet frame structure of the VLAN header.

24. The method according to any of claims 14 to 18 and 21, 22, wherein before the access network device sends the first information, the method further comprises:

the access network equipment determines the first information according to at least one of user capability, qoS data flow and VLAN indication, wherein the user capability is used for indicating whether the terminal equipment supports header compression of an Ethernet frame structure and/or header compression of the Ethernet frame structure of a VLAN header, and the VLAN indication is used for indicating whether the Ethernet frame structure of the PDU session data flow comprises a VLAN domain.

25. The method of claim 24, wherein the user capabilities are reported by the end device, and wherein the VLAN designation is obtained from a core network device.

26. A terminal device, wherein when a protocol data unit PDU session is an Ethernet frame, one Ethernet PDU carries a VLAN header, and another Ethernet PDU does not carry a VLAN header, and two Ethernet PDUs use different header compression algorithms, the terminal device comprising:

a communication unit, configured to receive first information sent by an access network device, where the first information is used to indicate that a first service data adaptation protocol SDAP device of the terminal device correspondingly processes a data packet of an ethernet frame structure that includes a VLAN header of a virtual local area network or indicate that a first SDAP device of the terminal device correspondingly processes a data packet of an ethernet frame structure that does not include a VLAN header;

a processing unit, configured to map, according to the first information, a packet of an ethernet frame structure including a VLAN header or a packet of an ethernet frame structure not including a VLAN header to a first SDAP device of the terminal device;

the processing unit is further to:

controlling a first SDAP device of the terminal device to deliver the mapped data packet to a first Packet Data Convergence Protocol (PDCP) device of the terminal device;

and controlling the first PDCP equipment of the terminal equipment to perform header compression on the data packet including the VLAN header by adopting a header compression mode corresponding to the VLAN header, and performing header compression on the data packet not including the VLAN header by adopting a header compression mode not including the VLAN header.

27. The terminal device of claim 26, wherein the first information comprises first indication information indicating that the first SDAP device of the terminal device handles packets with an ethernet frame structure that includes a VLAN header or indicating that the first SDAP device of the terminal device handles packets with an ethernet frame structure that does not include a VLAN header;

the processing unit is specifically configured to:

28. The terminal device of claim 27, wherein the first information is Radio Resource Control (RRC) signaling or System Information Block (SIB) information.

29. The terminal device of claim 28, wherein if the first information is RRC signaling, the first indication information is carried in DRB configuration information or SDAP configuration information.

30. The terminal device of claim 29, wherein the first indication information occupies 1-bit resource.

31. The terminal device of any of claims 27 to 30, wherein the processing unit is further configured to extend the DRB identity from 1 to 32 to 1 to 64.

32. A terminal device according to any one of claims 27 to 30, wherein the first information further comprises first PDCP configuration information for configuring data packets of an ethernet frame structure including a VLAN header with header compression that supports VLAN and/or configuring data packets of an ethernet frame structure not including a VLAN header with header compression that does not support VLAN.

33. The terminal device of claim 26, wherein the first information comprises first SDAP configuration information configured to configure a first default DRB for mapping ethernet frame structured packets that include VLAN headers and/or a second default DRB for mapping ethernet frame structured packets that do not include VLAN headers;

the processing unit is specifically configured to:

34. The end-point device of claim 33, wherein the VLAN-related information is a mapping of a quality-of-service QoS data flow identifier to a VLAN or ethernet PDU information comprising VLAN information.

35. The end-point device of any of claims 27-30 and 33-34, wherein if a first default DRB is configured at a first SDAP device of the end-point device and the first default DRB is used to map data packets of an ethernet frame structure including VLAN headers, the processing unit is further configured to map QoS data flows to DRBs according to a first rule,

the first rule is to perform header compression on the first default DRB for an Ethernet frame structure supporting VLAN, and select a DRB which does not support VLAN to perform header compression on the Ethernet frame structure which does not support VLAN.

36. The end-point device of any of claims 27-30 and 33-34, wherein if a second default DRB is configured at the first SDAP device of the end-point device and the second default DRB is used to map data packets of ethernet frame structure that do not include VLAN headers, the processing unit is further configured to map QoS data flows to DRBs according to a second rule,

and the second rule is to perform header compression on the second default DRB of the Ethernet frame structure which does not support the VLAN, and select one DRB which supports the VLAN to perform header compression on the Ethernet frame structure which supports the VLAN.

37. The end-point device of any of claims 27-30 and 33-34, wherein if a first default DRB or a second default DRB is configured at a first SDAP device of the end-point device, and the first default DRB is used to map packets of ethernet frame structure that include VLAN headers, the second default DRB is used to map packets of ethernet frame structure that do not include VLAN headers, the processing unit is further configured to map QoS data flows to DRBs according to a third rule,

and the third rule is that one DRB which supports VLAN is selected as the head compression of the Ethernet frame structure which supports VLAN, and one DRB which does not support VLAN is selected as the head compression of the Ethernet frame structure which does not support VLAN.

38. The terminal device according to any one of claims 26 to 30 and 33, 34, wherein before the communication unit receives the first information, the communication unit is further configured to report support capabilities for header compression and header compression of an ethernet frame structure as a whole, or report support capabilities for header compression and header compression of an ethernet header and a data field, respectively, for indicating whether the terminal device supports header compression of an ethernet frame structure and/or header compression of an ethernet frame structure of a VLAN header.

39. An access network device, when a Protocol Data Unit (PDU) session is an Ethernet frame, one Ethernet PDU carries a Virtual Local Area Network (VLAN) header, the other Ethernet PDU does not carry a VLAN header, and two Ethernet PDUs use different header compression algorithms, the access network device comprising:

a communication unit, configured to send first information to a terminal device, where the first information is used to indicate that a first service data adaptation protocol SDAP device of the terminal device correspondingly processes a data packet of an ethernet frame structure including a virtual local area network VLAN header or indicate that a first SDAP device of the terminal device correspondingly processes a data packet of an ethernet frame structure not including a VLAN header, so that the terminal device maps, according to the first information, the data packet of the ethernet frame structure including the VLAN header or the data packet of the ethernet frame structure not including the VLAN header to the first SDAP device of the terminal device; enabling a first SDAP device of the terminal device to deliver the mapped data packet to a first Packet Data Convergence Protocol (PDCP) device of the terminal device; and enabling the first PDCP device of the terminal device to perform header compression on the data packet including the VLAN header in a header compression mode corresponding to the VLAN header, and performing header compression on the data packet not including the VLAN header in a header compression mode corresponding to the VLAN header.

40. The access network device of claim 39, wherein the first information comprises first indication information indicating that the first SDAP device of the terminal device handles packets with Ethernet frame structures that include VLAN headers or indicating that the first SDAP device of the terminal device handles packets with Ethernet frame structures that do not include VLAN headers.

41. The access network device of claim 40, wherein the first information is Radio Resource Control (RRC) signaling or System Information Block (SIB) information.

42. The access network device of claim 41, wherein if the first information is RRC signaling, the first indication information is carried in DRB configuration information or SDAP configuration information.

43. The access network device of claim 42, wherein the first indication information occupies 1-bit resource.

44. The access network device according to any of claims 40 to 43, wherein the access network device further comprises:

a processing unit for extending the DRB identification from 1-32 to 1-64.

45. The access network device according to any one of claims 40 to 43, wherein the first information further comprises first PDCP configuration information, the first PDCP configuration information being used for configuring the terminal device to adopt a VLAN-capable header compression configuration for the Ethernet frame structure data packets including VLAN headers, and/or the first PDCP configuration information being used for adopting a VLAN-incapable header compression configuration for the Ethernet frame structure data packets not including VLAN headers.

46. The access network device of claim 39, wherein the first information comprises first SDAP configuration information configured to configure a first default DRB for mapping Ethernet frame structured packets that include VLAN headers and/or a second default DRB for mapping Ethernet frame structured packets that do not include VLAN headers.

47. The access network device of claim 46, wherein the VLAN related information is a mapping of a quality of service (QoS) data flow identifier to a VLAN or Ethernet PDU information including VLAN information.

48. The access network device according to any one of claims 39 to 43 and 46, 47, wherein before the communication unit sends the first information, the communication unit is further configured to receive support capabilities of header compression and header compression of an ethernet frame structure as a whole, reported by the terminal device, or report support capabilities of header compression and header compression of an ethernet header and a data field, respectively, for indicating whether the terminal device supports header compression of an ethernet frame structure and/or header compression of an ethernet frame structure of a VLAN header.

49. The access network device according to any of claims 39 to 43 and 46, 47, wherein before the communication unit sends the first information, the access network device further comprises:

and the processing unit is used for determining the first information according to at least one of user capability, qoS data flow and VLAN indication, wherein the user capability is used for indicating whether the terminal equipment supports header compression of an Ethernet frame structure and/or header compression of the Ethernet frame structure of a VLAN header, and the VLAN indication is used for indicating whether the Ethernet frame structure of the PDU session data flow comprises a VLAN domain.

50. The AN device of claim 49, wherein the user capabilities are reported by the UE, and the VLAN indicator is obtained from a core network device.

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

52. An access network device, comprising: a processor and a memory for storing a computer program, the processor being configured to invoke and execute the computer program stored in the memory to perform the method of any of claims 14 to 25.

53. A chip, comprising: a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any one of claims 1 to 13.

54. A chip, comprising: a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any one of claims 14 to 25.

55. A computer-readable storage medium for storing a computer program which causes a computer to perform the method of any one of claims 1 to 13.

56. A computer-readable storage medium for storing a computer program which causes a computer to perform the method of any one of claims 14 to 25.