WO2020062181A1 - Wireless communication method, and terminal device and access network device - Google Patents

Abstract

Provided are a wireless communication method, a terminal device, and an access network device, which can implement header compression of Ethernet PDUs carrying a VLAN header and not carrying a VLAN header. The method comprises: a terminal device receiving first information sent by an access network device, wherein the first information is used to indicate that a first SDAP device correspondingly processes a data packet of an Ethernet frame structure including a VLAN header or indicates that the first SDAP device correspondingly processes a data packet of an Ethernet frame structure not including the VLAN header; and the terminal device mapping 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 according to the first information.

Description

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

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

Background technique

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

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

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

Summary of the Invention

The embodiments of the present application provide a wireless communication method, a terminal device, and an access network device. The terminal device may send a packet of an Ethernet frame structure including a VLAN header or a packet of an Ethernet frame structure not including a VLAN header. It is mapped to Service Data Adaptation Protocol (SDAP) equipment, so that the compression of Ethernet PDU headers with and without the VLAN header can be implemented.

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

The terminal device receives first information sent by the access network device, and the first information is used to indicate that the first SDAP device of the terminal device correspondingly processes an Ethernet frame structured data packet including a VLAN header or indicates the first The SDAP device correspondingly processes the data packet of the Ethernet frame structure without the VLAN header;

According to the first information, the terminal device maps a data packet of an Ethernet frame structure including a VLAN header or a data packet of an Ethernet frame structure not including a VLAN header to a first SDAP device of the terminal device.

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

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

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 an Ethernet frame structured data packet including a VLAN header or indicates that the terminal The first SDAP device of the device correspondingly processes the data packet of the Ethernet frame structure that does not include the VLAN header.

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

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

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

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

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

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

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

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

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

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

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

Through the above technical solution, the terminal device can map 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 SDAP device. Compression of Ethernet PDU headers carrying VLAN headers.

Further, the terminal device may map 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 SDAP device based on the configuration of the access network device.

BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

FIG. 4 is a schematic block diagram of a terminal device 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 according to an embodiment of the present application.

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

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

detailed description

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

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

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

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

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

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

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

It should be understood that the Packet Data Convergence Protocol (PDCP) protocol introduces header compression and decompression functions for supporting different data radio bearers (DRBs), and compresses the profile according to the configured header. Use different header compression and header compression parameters. PDCP adopts Robust Information Header Compression (ROHC) protocol. The supported header compression protocols (protocols) and profiles are shown in Table 1 below. Specifically, as shown in Table 1 below, the compression objects of different header compression configurations may be Real-time Transport Protocol (RTP), IP, User Datagram Protocol (UDP), and encapsulated security payload ( _{Encapsulating Securit y Pa y load, ESP} ), uncompressed (no compression) of at least one, particularly compression strategy may be as follows RFC (Request For Comments) documents shown in the series.

Table 1

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

Optionally, the embodiments of the present application may be applied to a public land network or a local network.

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

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

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

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

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

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

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

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

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

It should also be understood that, in the embodiments of the present application, the SDAP device may also be called a PDCP layer, and the PDCP device may also be called a PDCP layer.

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

S210. The terminal device receives first information sent by the access network device, where the first information is used to indicate that the first SDAP device of the terminal device correspondingly processes an Ethernet frame structured data packet including a VLAN header or indicates that the terminal The first SDAP device of the device correspondingly processes the data packet of the Ethernet frame structure excluding the VLAN header;

S220. According to the first information, the terminal device maps a data packet of an Ethernet frame structure including a VLAN header or a data packet of an Ethernet frame structure not including a VLAN header to a first SDAP device of the terminal device.

Optionally, in the embodiment of the present 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. For example, the core network device may It is an AMF device, or a UPF device. Similarly, the following descriptions about the access network equipment are also applicable to the core network equipment. The following uses the terminal device to receive the first information from the access network device as an example for detailed description.

It should be noted that the first SDAP device is arranged on the terminal device side. Meanwhile, this application only uses the first SDAP device deployed on the terminal device side as an example for description, and other SDAP devices deployed on the terminal device side are also applicable.

It should also be noted that the first SDAP device correspondingly processes the mapping of the quality of service data flow (Service Flow, QoS Flow) to the data radio bearer (DRB).

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

The first PDCP device of the terminal device uses the header compression method corresponding to the VLAN header for the data packet including the VLAN header, or uses the header compression method without the VLAN header for the data packet not including the VLAN header. Perform header compression.

It should be noted that the first PDCP device is arranged on the terminal device side. Meanwhile, this application only uses the first PDCP device deployed on the terminal device side as an example for description, and other PDCP devices deployed on the terminal device side are also applicable.

Optionally, in the 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, and the first indication information is used for the first SDAP device to correspondingly process a data packet including an Ethernet frame structure including a VLAN header or to instruct the first SDAP device to correspondingly process the A packet with an Ethernet frame structure that does not include a VLAN header. Further, according to the first instruction information, the terminal device maps a data packet of an Ethernet frame structure including a VLAN header or a data packet of an Ethernet frame structure not including a VLAN header to the first SDAP device.

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

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

Optionally, in the 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 meet the identification requirements of data packets with Ethernet frame structure including the VLAN header and data packets with Ethernet frame structure not including the VLAN header. .

Optionally, in the 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 data packet of an Ethernet frame structure including a VLAN header to support a VLAN. Header compression configuration, and / or, the first PDCP configuration information is used to configure a data packet of an Ethernet frame structure that does not include a VLAN header to a header compression configuration that does not support VLAN.

In other words, the access network device is configured to support the header compression profile of the VLAN header for the data packet of the Ethernet frame structure including the VLAN header, and not configured for the data packet of the Ethernet frame structure that does not include the VLAN header. Supports header compression profile for VLAN headers.

Specifically, the terminal device may, according to the first PDCP configuration information, compress or decompress a data packet supporting an Ethernet frame structure including a VLAN header, and / or, an Ethernet without a VLAN header. Packets in the network frame structure do not support VLAN header compression or decompression.

Optionally, in the 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, and the first default DRB is used for Map the data packet of the Ethernet frame structure including the VLAN header, and the second default DRB is used to map the data packet of the Ethernet frame structure not including the VLAN header.

It should be noted that the first default DRB or the second default DRB may be the original default DRB stored on the terminal device side, that is, the access network device may only newly configure a default DRB. Of course, the access network device You can also configure two new default DRBs.

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

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

For example, if the first default DRB is configured at the first SDAP device, the terminal device maps a data packet of an Ethernet frame structure including a VLAN header to the first SDAP device.

As another example, if the first SDAP device is configured with the first default DRB, the terminal device maps an Ethernet frame structure packet including a VLAN header to the first SDAP device; and / or, the terminal device will A packet of an Ethernet frame structure that does not include a VLAN header is mapped to another DRB or one of other DRBs corresponding to the same PDU-session that can be mapped to a packet of an Ethernet frame structure that includes a VLAN header, or the terminal device will The data packet of the Ethernet frame structure excluding the VLAN header is mapped to the original default DRB stored on the terminal device side.

For another example, if the second default DRB is configured at the first SDAP device, the terminal device maps a data packet of an Ethernet frame structure that does not include a 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 a data packet of an Ethernet frame structure that does not include a VLAN header to the first SDAP device; and / or, the terminal device Map an Ethernet frame structured packet including a VLAN header to other DRBs or one of other DRBs corresponding to the same PDU-session that can be mapped to other Ethernet frame structured packets without a VLAN header, or the terminal device Map the data packet of the Ethernet frame structure including the VLAN header to the original default DRB stored on the terminal device side.

For another example, if the first SDAP device is configured with the first default DRB, and the second SDAP device is configured with the second default DRB, the terminal device may map an Ethernet frame structured data packet including a VLAN header to The first SDAP device may also map a data packet of an Ethernet frame structure that does not include a 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 Ethernet PDU information including VLAN information. The VLAN-related information may be pre-configured, may be notified by the network side, or may be obtained by interaction between user layers.

Optionally, as an example, if the first SDAP device is configured with a first default DRB, and the first default DRB is used to map a data packet of an Ethernet frame structure including a VLAN header, the terminal device according to the first Rules map QoS data flows to DRBs,

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

Optionally, as another example, if a second default DRB is configured at the first SDAP device, and the second default DRB is used to map a data packet of an Ethernet frame structure that does not include a VLAN header, the terminal device is based on The second rule maps the QoS data flow to the DRB,

The second rule is to perform header compression on an Ethernet frame structure that does not support VLAN for the second default DRB, and select a DRB that supports VLAN to perform header compression on an Ethernet frame structure that supports VLAN.

Optionally, as still another example, if the first SDAP device is configured with a first default DRB or a second default DRB, and the first default DRB is used to map a data packet of an Ethernet frame structure including a VLAN header, The second default DRB is used to map an Ethernet frame structured data packet that does not include a VLAN header, and the terminal device maps the QoS data flow to the DRB according to a third rule,

The third rule is to select another DRB that supports VLAN as the header compression for the Ethernet frame structure that supports VLAN, and select another DRB that does not support the VLAN to perform the header compression for the Ethernet frame structure that does not support VLAN.

It should be noted that, in the above example, the terminal device may have a mapping relationship between uplink QoS Flow and DRB, or there may be no mapping relationship between uplink QoS Flow and DRB.

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

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

Therefore, in the embodiment of the present application, the terminal device can map 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 SDAP device, so that the VLAN can be carried. Headers and Ethernet PDU headers without the VLAN header are compressed.

Further, the terminal device may map 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 SDAP device based on the configuration of the access network device.

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

S310. The access network device sends first information to the terminal device, where the first information is used to indicate that the first SDAP device of the terminal device correspondingly processes an Ethernet frame structured data packet including a VLAN header or indicates that the terminal device The first SDAP device correspondingly processes an Ethernet frame structured data packet that does not include a VLAN header.

Optionally, in the 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. The core network device may be an AMF device, or UPF equipment. Similarly, the following descriptions about the access network equipment are also applicable to the core network equipment. The following uses the access network device to send the first information as an example for detailed description.

Optionally, in the embodiment of the present application, the first information includes first indication information, and the first indication information is used by the first SDAP device to correspondingly process a data packet or an indication of an Ethernet frame structure including a VLAN header. The first SDAP device correspondingly processes a data 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 RRC signaling, the first indication information is carried in DRB configuration information or SDAP configuration information. For example, the first indication information occupies a 1-bit resource.

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

Optionally, in the embodiment of the present application, the first information further includes first PDCP configuration information, and the first PDCP configuration information is used to configure the terminal device to configure a data packet of an Ethernet frame structure including a VLAN header as Supports VLAN header compression configuration, and / or, the first PDCP configuration information is used by the terminal device to configure a data packet of an Ethernet frame structure that does not include a VLAN header to not support VLAN header compression configuration.

Optionally, in the 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, and the first default DRB is used for Map the data packet of the Ethernet frame structure including the VLAN header, and the second default DRB is used to map the data packet of the Ethernet frame structure not including the VLAN header.

Optionally, the VLAN related information is a mapping relationship between a QoS flow ID and a VLAN, or Ethernet PDU information including VLAN information. The VLAN-related information may be pre-configured, may be notified by the network side, or may be obtained by interaction between user layers.

Optionally, in the embodiment of the present application, before the access network device sends the first information, the access network device receives the support capability of the header compression and decompression of the overall Ethernet frame structure reported by the terminal device. Or, report support for the header compression and decompression of the Ethernet header and the data domain, respectively, to indicate whether the terminal device supports Ethernet frame structure header compression and / or whether it supports the VLAN header Ethernet frame structure Head compression.

It should be noted that the terminal device may report the support for header compression and decompression of the overall Ethernet frame structure in the form of capability reporting, or report header compression and decompression of the Ethernet header and data domain, respectively. Support capabilities.

Optionally, in the embodiment of the present application, 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. Wherein, the user capability is used to indicate whether the terminal device supports header compression of the Ethernet frame structure and / or whether it supports header compression of the Ethernet frame structure of the VLAN header, and the VLAN indication is used to indicate the Ethernet of the PDU session data stream. Whether the frame structure includes a VLAN domain.

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

For example, the VLAN indication is acquired by the access network device through a user plane function (UPF) device or an access and mobility management function (AMF) device.

Optionally, in the embodiment of the present application, the access network device determines service mapping and configuration criteria according to information such as user capabilities, QoS, and VLAN indication, and configures SDAP configuration and PDCP configuration of each DRB. The configured DRB maps and processes only one type of Ethernet frame, that is, an Ethernet frame type that includes a VLAN header, or a type that does not include an Ethernet frame.

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

Data flows with the same or similar QoS characteristics can be mapped into a DRB;

The data flow corresponding to the Ethernet frame with the VLAN header cannot be mapped to the same DRB as the data flow corresponding to the Ethernet frame without the VLAN header;

Data flows mapped to different ports of the same PDU session cannot be mapped to a DRB.

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

Therefore, in the embodiment of the present application, the terminal device can map 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 SDAP device, so that the VLAN can be carried Headers and Ethernet PDU headers without the VLAN header are compressed.

Further, the terminal device may map 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 SDAP device based on the configuration of the access network device.

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

The communication unit 410 is configured to receive first information sent by an access network 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 including a VLAN header. Or instructing the first SDAP device of the terminal device to correspondingly process a data packet of an Ethernet frame structure that does not include a VLAN header;

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

Optionally, the processing unit 420 is further configured to:

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

The first PDCP device controlling the terminal device performs header compression on a packet including a VLAN header by using a header compression method corresponding to the VLAN header, or applies a header that does not include a VLAN header to a data packet that does not include the VLAN header. The compression method performs header compression.

Optionally, the first information includes first indication information, and the first indication information is used to indicate that the first SDAP device of the terminal device correspondingly processes an Ethernet frame structured data packet including a VLAN header or Instructing the first SDAP device of the terminal device to correspondingly process a data 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 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 according to the first instruction information.

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

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

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

Optionally, the processing unit 420 is further configured to extend the DRB identifier 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 use a VLAN header compression configuration for a data packet of an Ethernet frame structure including a VLAN header, and / or The first PDCP configuration information is used to use a header compression configuration that does not support a VLAN for a data 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, and the first default DRB is used to map including a VLAN word A data packet with an Ethernet frame structure of the header, and the second default DRB is used to map a data packet with an Ethernet frame structure that does not include a VLAN header;

The processing unit 420 is specifically configured to:

Mapping 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 of the terminal device according to the first SDAP configuration information and VLAN related information device.

Optionally, the VLAN related information is a mapping relationship between a QoS flow identifier and a VLAN, or Ethernet PDU information including VLAN information. The VLAN-related information may be pre-configured, may be notified by the network side, or may be obtained by interaction between user layers.

Optionally, if the first SDAP device of the terminal device is configured with a first default DRB, and the first default DRB is used to map a data packet of an Ethernet frame structure including a VLAN header, the processing unit 420 And is further configured to map the QoS data flow to the DRB according to the first rule,

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

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 a data packet of an Ethernet frame structure that does not include a VLAN header, the processing unit 420 is also used to map the QoS data flow to the DRB according to the second rule,

The second rule is to perform header compression on the second default DRB for an Ethernet frame structure that does not support VLAN, and select a DRB that supports VLAN for header compression for an Ethernet frame structure that supports VLAN.

Optionally, if the first SDAP device of the terminal device is configured with a first default DRB or a second default DRB, and the first default DRB is used to map a data packet of an Ethernet frame structure including a VLAN header, The second default DRB is used to map a data packet of an Ethernet frame structure that does not include a VLAN header, and the processing unit 420 is further configured to map a QoS data flow to the DRB according to a third rule,

The third rule is to select another DRB that supports VLAN as the header compression of the Ethernet frame structure that supports VLAN, and select another DRB that does not support the VLAN to perform the header compression of the Ethernet frame structure that does not support VLAN.

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

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

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

The communication unit 510 is configured to send first information to a terminal device, where the first information is used to indicate that the first SDAP device of the terminal device correspondingly processes an Ethernet frame structured data packet including a VLAN header or indicates 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, and the first indication information is used by the first SDAP device to correspondingly process an Ethernet frame structure packet including a VLAN header or to indicate that the first SDAP device corresponds to Processes packets of the Ethernet frame structure that do not include the VLAN header.

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

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

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

Optionally, the access network device 500 further includes:

The processing unit 520 is configured to expand the DRB identifier from 1 to 32 to 1 to 64.

Optionally, the first information further includes first PDCP configuration information, and the first PDCP configuration information is used to configure the terminal device to use a VLAN header-compressed data packet for the Ethernet frame structure of the terminal device. Configuration, and / or, the first PDCP configuration information is used by the terminal device to adopt a header compression configuration that does not support a VLAN of a data packet of an Ethernet frame structure.

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, and the first default DRB is used to map including a VLAN word The second default DRB is used to map a data packet 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 Ethernet PDU information including VLAN information. The VLAN-related information may be pre-configured, may be notified by the network side, or may be obtained by interaction between user layers.

Optionally, before the communication unit 510 sends the first information, the communication unit 510 is further configured to receive a support capability of the overall header compression and decompression of the Ethernet frame structure reported by the terminal device, or To report support for header compression and decompression of the Ethernet header and data domain, respectively, for indicating whether the terminal device supports header compression of the Ethernet frame structure and / or whether it supports the Ethernet frame structure of the VLAN header Head compression.

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, wherein the user capability is used to indicate whether the terminal device supports a header of an Ethernet frame structure Compression and / or header compression of an Ethernet frame structure that supports a VLAN header that indicates whether the Ethernet frame structure used to indicate a PDU session data stream includes a VLAN domain.

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

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

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 includes a processor 610, and the processor 610 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

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

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

Optionally, as shown in FIG. 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 send information or data to other devices, or receive other Information or data sent by the device.

The transceiver 630 may include a transmitter and a receiver. The transceiver 630 may further include 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 process implemented by the access network device in each method of the embodiment of the present application. For simplicity, in This will not be repeated here.

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

FIG. 7 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 700 shown in FIG. 7 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. 7, the chip 700 may further include a memory 720. The processor 710 may call and run a computer program from the memory 720 to implement the method in the embodiment of the present application.

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

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

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

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

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

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

FIG. 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 used to implement the corresponding function implemented by the terminal device in the foregoing method, and the access network device 820 may be used to implement the corresponding function implemented by the access network device in the foregoing method. For simplicity, in This will not be repeated here.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims (62)

A wireless communication method, comprising: The terminal device receives first information sent by the access network device, and the first information is used to indicate that the first service data adaptation protocol SDAP device of the terminal device correspondingly processes an Ethernet frame structure including a virtual local area network VLAN header. A data packet or an instruction indicating that the first SDAP device correspondingly processes a data packet of an Ethernet frame structure that does not include a VLAN header; According to the first information, the terminal device maps a data packet of an Ethernet frame structure including a VLAN header or a data packet of an Ethernet frame structure not including a VLAN header to a first SDAP device of the terminal device. The method according to claim 1, further comprising: The first SDAP device of the terminal device submits the mapped data packet to the first packet data convergence protocol PDCP device of the terminal device; The first PDCP device of the terminal device performs header compression on a packet including a VLAN header by using a header compression method corresponding to the VLAN header, or uses a header compression on a data packet that does not include the VLAN header without the corresponding VLAN header. Way to perform header compression. The method according to claim 1 or 2, wherein the first information includes first instruction information, and the first instruction information is used to indicate that the first SDAP device of the terminal device correspondingly processes a VLAN. The data packet of the Ethernet frame structure with the prefix or the first SDAP device instructing the terminal device to process the data packet of the Ethernet frame structure without the VLAN header correspondingly; Mapping, by the terminal device, a data packet of an Ethernet frame structure including a VLAN header or a data packet of an Ethernet frame structure not including a VLAN header to the first SDAP device of the terminal device according to the first information, include: According to the first instruction information, the terminal device maps a data packet of an Ethernet frame structure including a VLAN header or a data packet of an Ethernet frame structure not including a VLAN header to a first SDAP device of the terminal device. . The method according to claim 2, wherein the first information is radio resource control RRC signaling, or system information block SIB information. The method according to claim 4, wherein if the first information is RRC signaling, the first indication information is carried in data radio bearer DRB configuration information or SDAP configuration information. The method according to claim 5, wherein the first indication information occupies a 1-bit resource. The method according to any one of claims 3 to 6, wherein the method further comprises: The terminal device extends the DRB identity from 1 to 32 to 1 to 64. The method according to any one of claims 3 to 7, wherein the first information further includes first PDCP configuration information, and the first PDCP configuration information is used to use an Ethernet frame including a VLAN header. The structured data packet adopts a header compression configuration that supports VLAN, and / or, the first PDCP configuration information is used to use a data packet of an Ethernet frame structure that does not include a VLAN header to adopt a header compression configuration that does not support VLAN. The method according to claim 1 or 2, wherein the first information includes first SDAP configuration information, and the first SDAP configuration information is used to configure a first default DRB and / or a second default DRB, and The first default DRB is used to map data packets of an Ethernet frame structure including 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; Mapping, by the terminal device, a data packet of an Ethernet frame structure including a VLAN header or a data packet of an Ethernet frame structure not including a VLAN header to the first SDAP device of the terminal device according to the first information, include: And mapping, by the terminal device, 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 terminal device according to the first SDAP configuration information and VLAN-related information. First SDAP device. The method according to claim 9, wherein the VLAN related information is a mapping relationship between a quality of service QoS data flow identifier and a VLAN, or Ethernet PDU information including VLAN information. The method according to any one of claims 3 to 10, wherein if a first SDAP device of the terminal device is configured with a first default DRB, and the first default DRB is used for mapping including a VLAN word Data packet of the Ethernet frame structure of the header, the method further includes: The terminal device maps the QoS data flow to the DRB according to the first rule, The first rule is to perform header compression on the first default DRB for an Ethernet frame structure that supports VLAN, and select a DRB that does not support VLAN to perform header compression for an Ethernet frame structure that does not support VLAN. The method according to any one of claims 3 to 10, wherein if a second default DRB is configured at a first SDAP device of the terminal device, and the second default DRB is used for mapping not including a VLAN A data packet with a prefixed Ethernet frame structure, the method further includes: The terminal device maps the QoS data flow to the DRB according to a second rule, The second rule is to perform header compression on the second default DRB for an Ethernet frame structure that does not support VLAN, and select a DRB that supports VLAN for header compression for an Ethernet frame structure that supports VLAN. The method according to any one of claims 3 to 10, wherein if the first SDAP device of the terminal device is configured with a first default DRB or a second default DRB, and the first default DRB is used For mapping a data packet of an Ethernet frame structure including a VLAN header, the second default DRB is used to map a data packet of an Ethernet frame structure not including a VLAN header, and the method further includes: The terminal device maps the QoS data flow to the DRB according to a third rule, The third rule is to select another DRB that supports VLAN as the header compression for the Ethernet frame structure that supports VLAN, and select another DRB that does not support the VLAN to perform the header compression for the Ethernet frame structure that does not support VLAN. The method according to any one of claims 1 to 13, wherein before the terminal device receives the first information, the method further comprises: The terminal device reports support capabilities for header compression and decompression of the overall Ethernet frame structure, or reports support capabilities for header compression and decompression of the Ethernet header and data domain, respectively, for indicating whether the terminal device Supports header compression of the Ethernet frame structure and / or whether it supports header compression of the Ethernet frame structure of the VLAN header. A wireless communication method, comprising: The access network device sends first information to the terminal device, where the first information is used to indicate that the first service data adaptation protocol SDAP device of the terminal device correspondingly processes data of an Ethernet frame structure including a virtual local area network VLAN header. The packet or the first SDAP device instructing the terminal device correspondingly processes a data packet of an Ethernet frame structure that does not include a VLAN header. The method according to claim 15, wherein the first information includes first indication information, and the first indication information is used to indicate that the first SDAP device of the terminal device correspondingly processes a VLAN header. The data packet of the Ethernet frame structure or the first SDAP device instructing the terminal device correspondingly processes the data packet of the Ethernet frame structure that does not include a VLAN header. The method according to claim 16, wherein the first information is radio resource control RRC signaling, or system information block SIB information. The method according to claim 17, wherein if the first information is RRC signaling, the first indication information is carried in data radio bearer DRB configuration information or SDAP configuration information. The method according to claim 18, wherein the first indication information occupies a 1-bit resource. The method according to any one of claims 16 to 19, wherein the method further comprises: The access network device extends the DRB identity from 1 to 32 to 1 to 64. The method according to any one of claims 16 to 20, wherein the first information further comprises first packet data convergence protocol PDCP configuration information, and the first PDCP configuration information is used to configure the terminal device Adopting a header compression configuration that supports a VLAN with a data packet of an Ethernet frame structure including a VLAN header, and / or, the first PDCP configuration information is used for an Ethernet frame structure in which the terminal device does not include a VLAN header The data packet adopts a header compression configuration that does not support VLAN. The method according to claim 15, wherein the first information includes first SDAP configuration information, and the first SDAP configuration information is used to configure a first default DRB and / or a second default DRB, and the first A default DRB is used to map data packets of an Ethernet frame structure including 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. The method according to claim 22, wherein the VLAN-related information is a mapping relationship between a quality of service QoS data flow identifier and a VLAN, or Ethernet PDU information including VLAN information. The method according to any one of claims 15 to 23, wherein before the access network device sends the first information, the method further comprises: Receiving, by the access network device, the support capabilities for the overall header compression and decompression of the Ethernet frame structure reported by the terminal device, or reporting support capabilities for header compression and decompression of the Ethernet header and data domain, It is used to indicate whether the terminal device supports header compression of the Ethernet frame structure and / or whether it supports header compression of the Ethernet frame structure of a VLAN header. The method according to any one of claims 15 to 24, wherein before the access network device sends the first information, the method further comprises: 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, wherein the user capability is used to indicate whether the terminal device supports a header of an Ethernet frame structure. Compression and / or header compression of an Ethernet frame structure that supports a VLAN header that indicates whether the Ethernet frame structure used to indicate a PDU session data stream includes a VLAN domain. The method according to claim 25, wherein the user capability is reported by the terminal device, and the VLAN indication is obtained from a core network device. A terminal device, comprising: The communication unit is configured to receive first information sent by an access network device, where the first information is used to indicate that the first service data adaptation protocol SDAP device of the terminal device correspondingly processes an Ethernet including a virtual LAN VLAN header The data packet of the frame structure or the first SDAP device instructing the terminal device to process the data packet of the Ethernet frame structure not including the VLAN header; A processing unit, configured to map, according to the first information, a data packet of an Ethernet frame structure including a VLAN header or a data packet of an Ethernet frame structure not including a VLAN header to a first SDAP device of the terminal device . The terminal device according to claim 27, wherein the processing unit is further configured to: A first SDAP device controlling the terminal device to deliver the mapped data packet to a first packet data convergence protocol PDCP device of the terminal device; The first PDCP device controlling the terminal device performs header compression on a packet including a VLAN header by using a header compression method corresponding to the VLAN header, or applies a header that does not include a VLAN header to a data packet that does not include the VLAN header. The compression method performs header compression. The terminal device according to claim 27 or 28, wherein the first information includes first indication information, and the first indication information is used to instruct the first SDAP device of the terminal device to correspondingly process includes The data packet of the Ethernet frame structure of the VLAN header or the first SDAP device instructing the terminal device to process the data packet of the Ethernet frame structure not including the VLAN header; The processing unit is specifically configured to: And mapping 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 according to the first instruction information. The terminal device according to claim 29, wherein the first information is radio resource control RRC signaling or system information block SIB information. The terminal device according to claim 30, wherein if the first information is RRC signaling, the first indication information is carried in data radio bearer DRB configuration information or SDAP configuration information. The terminal device according to claim 31, wherein the first indication information occupies a 1-bit resource. The terminal device according to any one of claims 29 to 32, wherein the processing unit is further configured to expand a DRB identifier from 1 to 32 to 1 to 64. The terminal device according to any one of claims 29 to 33, wherein the first information further includes first PDCP configuration information, and the first PDCP configuration information is used for an Ethernet including a VLAN header The data packet of the frame structure adopts a header compression configuration that supports VLAN, and / or, the first PDCP configuration information is used for the data packet of the Ethernet frame structure that does not include a VLAN header to adopt a header compression configuration that does not support VLAN. The terminal device according to claim 27 or 28, wherein the first information includes first SDAP configuration information, and 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 including 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; The processing unit is specifically configured to: Mapping 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 of the terminal device according to the first SDAP configuration information and VLAN related information device. The terminal device according to claim 35, wherein the VLAN-related information is a mapping relationship between a quality of service QoS data flow identifier and a VLAN, or Ethernet PDU information including VLAN information. The terminal device according to any one of claims 29 to 36, characterized in that if a first SDAP device of the terminal device is configured with a first default DRB, and the first default DRB is used for mapping including a VLAN A data packet with a prefixed Ethernet frame structure, the processing unit is further configured to map a QoS data stream to a DRB according to a first rule, The first rule is to perform header compression on the first default DRB for an Ethernet frame structure that supports VLAN, and select a DRB that does not support VLAN to perform header compression for an Ethernet frame structure that does not support VLAN. The terminal device according to any one of claims 29 to 36, wherein if a second default DRB is configured at a first SDAP device of the terminal device, and the second default DRB is used for mapping without including A data packet with an Ethernet frame structure in a VLAN header, the processing unit is further configured to map a QoS data flow to a DRB according to a second rule, The second rule is to perform header compression on the second default DRB for an Ethernet frame structure that does not support VLAN, and select a DRB that supports VLAN for header compression for an Ethernet frame structure that supports VLAN. The terminal device according to any one of claims 29 to 36, wherein if a first SDAP device of the terminal device is configured with a first default DRB or a second default DRB, and the first default DRB The second default DRB is used to map a data packet of an Ethernet frame structure including a VLAN header, and the second default DRB is used to map a data packet of an Ethernet frame structure that does not include a VLAN header. The processing unit is further configured to: Map QoS data flow to DRB, The third rule is to select another DRB that supports VLAN as the header compression for the Ethernet frame structure that supports VLAN, and select another DRB that does not support the VLAN to perform the header compression for the Ethernet frame structure that does not support VLAN. The terminal device according to any one of claims 27 to 39, wherein before the communication unit receives the first information, the communication unit is further configured to report a header compression of the entire Ethernet frame structure Support for decompression of header compression, or reporting support for header compression and decompression of Ethernet headers and data domains, respectively, used to indicate whether the terminal device supports header compression of the Ethernet frame structure and / or VLAN Header header compression of the Ethernet frame structure. An access network device, comprising: The communication unit is configured to send first information to the terminal device, where the first information is used to indicate that the first service data adaptation protocol SDAP device of the terminal device correspondingly processes an Ethernet frame structure including a virtual local area network VLAN header. The data packet or the first SDAP device instructing the terminal device correspondingly processes a data packet of an Ethernet frame structure that does not include a VLAN header. The access network device according to claim 41, wherein the first information includes first indication information, and the first indication information is used to instruct the corresponding processing of the first SDAP device of the terminal device to include: The data packet of the Ethernet frame structure of the VLAN header or the first SDAP device instructing the terminal device to process the data packet of the Ethernet frame structure not including the VLAN header. The access network device according to claim 42, wherein the first information is radio resource control RRC signaling or system information block SIB information. The access network device according to claim 43, wherein if the first information is RRC signaling, the first indication information is carried in data radio bearer DRB configuration information or SDAP configuration information. The access network device according to claim 44, wherein the first indication information occupies a 1-bit resource. The access network device according to any one of claims 42 to 45, wherein the access network device further comprises: Processing unit for expanding the DRB identification from 1 to 32 to 1 to 64. The access network device according to any one of claims 42 to 46, wherein the first information further includes first PDCP configuration information, and the first PDCP configuration information is used to configure the terminal device to The data packet of the Ethernet frame structure including the VLAN header adopts a header compression configuration that supports the VLAN, and / or, the first PDCP configuration information is used for data of the Ethernet frame structure that the terminal device does not include the VLAN header. The packet uses a header compression configuration that does not support VLAN. The access network device according to claim 41, wherein the first information includes first SDAP configuration information, and 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 including 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. The access network device according to claim 48, wherein the VLAN related information is a mapping relationship between a quality of service QoS data flow identifier and a VLAN, or Ethernet PDU information including VLAN information. The access network device according to any one of claims 41 to 49, wherein before the communication unit sends the first information, the communication unit is further configured to receive a pair reported by the terminal device. Supports the overall header compression and decompression support of the Ethernet frame structure, or reports the support for header compression and decompression of the Ethernet header and data domain, respectively, to indicate whether the terminal device supports the Ethernet frame structure. Header compression and / or header compression for the Ethernet frame structure of the VLAN header. The access network device according to any one of claims 41 to 50, wherein before the communication unit sends the first information, the access network device further comprises: A processing unit, configured to determine the first information according to at least one of a user capability, a QoS data flow, and a VLAN indication, wherein the user capability is used to indicate whether the terminal device supports header compression of an Ethernet frame structure And / or whether header compression of the Ethernet frame structure of a VLAN header is supported, the VLAN indication is used to indicate whether the Ethernet frame structure of the PDU session data stream includes a VLAN domain. The access network device according to claim 51, wherein the user capability is reported by the terminal device, and the VLAN indication is obtained from a core network device. A terminal device includes a processor and a memory, where the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, and execute any one of claims 1 to 14. The method of one item. An access network device, comprising: a processor and a memory, where the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, and execute claims 15 to 26 The method of any one of. A chip, comprising: a processor, configured to call and run a computer program from a memory, so that a device having the chip installed executes the method according to any one of claims 1 to 14. A chip, comprising: a processor, configured to call and run a computer program from a memory, so that a device having the chip installed executes the method according to any one of claims 15 to 26. A computer-readable storage medium, which is used for storing a computer program, which causes a computer to execute the method according to any one of claims 1 to 14. A computer-readable storage medium, for storing a computer program, which causes a computer to execute the method according to any one of claims 15 to 26. A computer program product, comprising computer program instructions that cause a computer to execute the method according to any one of claims 1 to 14. A computer program product, comprising computer program instructions that cause a computer to execute the method according to any one of claims 15 to 26. A computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 14. A computer program, wherein the computer program causes a computer to execute the method according to any one of claims 15 to 26.

Images