WO2020063709A1 - 用于以太网数据的通信方法和装置 - Google Patents

用于以太网数据的通信方法和装置 Download PDF

Info

Publication number
WO2020063709A1
WO2020063709A1 PCT/CN2019/108019 CN2019108019W WO2020063709A1 WO 2020063709 A1 WO2020063709 A1 WO 2020063709A1 CN 2019108019 W CN2019108019 W CN 2019108019W WO 2020063709 A1 WO2020063709 A1 WO 2020063709A1
Authority
WO
WIPO (PCT)
Prior art keywords
data packet
ethernet
terminal device
ethernet data
network device
Prior art date
Application number
PCT/CN2019/108019
Other languages
English (en)
French (fr)
Inventor
徐小英
黄曲芳
曾清海
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP19868002.7A priority Critical patent/EP3849148B1/en
Priority to JP2021516888A priority patent/JP7210710B2/ja
Priority to CA3114267A priority patent/CA3114267A1/en
Publication of WO2020063709A1 publication Critical patent/WO2020063709A1/zh
Priority to US17/213,970 priority patent/US20210219173A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0094—Indication of how sub-channels of the path are allocated
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0014—Three-dimensional division
    • H04L5/0016—Time-frequency-code
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0466—Wireless resource allocation based on the type of the allocated resource the resource being a scrambling code
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/04—Protocols for data compression, e.g. ROHC

Definitions

  • the present application relates to the field of communications, and more particularly, to a communication method and apparatus for Ethernet data.
  • Ethernet is a local area network communication technology.
  • Current industrial scenarios use wired Ethernet to transmit data.
  • data transmitted based on Ethernet communication technology can be referred to simply as Ethernet data.
  • Ethernet data can also be transmitted through wireless communication.
  • the console sends instructions to the machine equipment through the wireless network, and the machine equipment performs corresponding actions and reports its own status information to the server based on the received instructions.
  • the present application provides a communication method and device for Ethernet data, which can perform wireless communication of Ethernet data.
  • a communication method for Ethernet data including:
  • the terminal device receives downlink control information DCI from a network device, the DCI is scrambled by using a first wireless network temporary identifier RNTI, the first RNTI is an RNTI for an Ethernet data packet, and the DCI includes an instruction for carrying the Ethernet Information of time-frequency resources of network data packets;
  • the method for processing Ethernet data in the embodiment of the present application can scramble DCI through an RNTI specifically for Ethernet data, which can reduce interference to terminal devices other than terminal devices that need to receive other types of data. It realizes the transmission of Ethernet data in wireless networks, and also improves the transmission performance of Ethernet data.
  • the receiving, by the terminal device, the Ethernet data packet from the network device includes:
  • a system information block SIB from the network device on a time-frequency resource indicated by the DCI, and the SIB includes the Ethernet data packet.
  • the first RNTI is an RNTI for an Ethernet data packet of a broadcast type or a multicast type.
  • the DCI includes first information, and the first information is used to indicate that the data packet scheduled by the DCI is a broadcast type Ethernet data packet or a multicast type Ethernet data packet.
  • the packet header of the Ethernet data packet does not include a broadcast type media intervention control MAC address.
  • the method further includes:
  • the terminal device sends a media intervention control MAC address associated with the terminal device to the network device.
  • the sending, by the terminal device, the MAC address to the network device includes:
  • the terminal device sends a non-access stratum NAS message to the network device, and the NAS message includes the MAC address.
  • the method further includes:
  • the terminal device receives a request message from the network device, and the request message is used to request the MAC address associated with the terminal device.
  • the sending, by the terminal device, the MAC address to the network device includes:
  • the terminal device When the MAC address associated with the terminal device changes, the terminal device sends the changed MAC address to the network device.
  • the method further includes:
  • compression capability information is used to indicate N types of Ethernet compression capabilities supported by the terminal device, where N is an integer greater than or equal to 1;
  • the terminal device decompresses the Ethernet data packet, wherein the Ethernet data packet is generated based on a parameter of the first Ethernet compression capability.
  • the Ethernet data packet includes a first header, the first header includes a first context identifier, and the first context identifier is used to identify the first context information; the method further includes :
  • the decompressing the Ethernet data packet by the terminal device includes:
  • the terminal device decompresses the Ethernet data packet according to the first context information.
  • a communication method for Ethernet data includes:
  • the network device sends downlink control information DCI to the terminal device.
  • the DCI is scrambled using a first wireless network temporary identifier RNTI.
  • the first RNTI is an RNTI for an Ethernet data packet.
  • the DCI includes an instruction for carrying the Ethernet.
  • the network device sends the Ethernet data packet to the terminal device on the time-frequency resource.
  • the sending, by the network device, the Ethernet data packet to the terminal device includes:
  • the network device sends a system information block SIB to the terminal device on the time-frequency resource, and the SIB includes the Ethernet data packet.
  • the first RNTI is an RNTI for a broadcast type or a multicast type Ethernet data packet.
  • the DCI includes first information, and the first information is used to indicate that the data packet scheduled by the DCI is a broadcast type Ethernet data packet or a multicast type Ethernet data packet.
  • the network device is an access network device, and a public service quality Qos flow is established between the access network device and the core network device;
  • the method further includes:
  • the network device receives the Ethernet data packet from the public Qos stream.
  • the method further includes:
  • the network device receives a media intervention control MAC address associated with the terminal device from the terminal device.
  • the receiving, by the network device, the MAC address from the terminal device includes:
  • the network device receives a non-access stratum NAS message from the terminal device, and the NAS message includes the MAC address.
  • the method further includes:
  • the network device sends a request message to the terminal device, where the request message is used to request the MAC address associated with the terminal device.
  • the method further includes:
  • the network device Sending, by the network device, compression configuration information to the terminal device, where the compression configuration information is used to indicate a parameter of a first Ethernet compression capability, and the N types of Ethernet compression capabilities include the first Ethernet compression capability;
  • the network device generates the Ethernet data packet according to the parameter of the first Ethernet compression capability.
  • the Ethernet data packet includes a first header, the first header includes a first context identifier, and the first context identifier is used to identify the first context information.
  • a communication method for Ethernet data includes:
  • the terminal device receives a system information block SIB from a network device, the SIB includes an Ethernet data packet;
  • the method for processing Ethernet data packets provided in the embodiments of the present application can send a broadcast-type Ethernet data packet through the SIB to efficiently notify the terminal device to receive the Ethernet data packet and improve transmission efficiency.
  • the method further includes:
  • the terminal device Receiving, by the terminal device, a paging message from the network device, the paging message includes indication information, and the indication information is used to indicate that the SIB includes the Ethernet data packet.
  • the sending mechanism of the paging message can be effectively used, that is, the terminal device receives the paging message within a period of time to detect whether there is a message for itself, reducing the design complexity. , Can also improve the reliability of the terminal device receiving data packets.
  • the method includes:
  • the terminal device receives downlink control information DCI from the network device, the DCI is scrambled by using a first wireless network temporary identifier RNTI, the first RNTI is an RNTI for an Ethernet data packet, and the DCI includes an instruction for indicating Carries information of time-frequency resources of the Ethernet data packet.
  • the DCI includes first information
  • the first information is used to indicate that the data packet scheduled by the DCI is a broadcast type Ethernet data packet or a multicast type Ethernet data packet.
  • the packet header of the Ethernet data packet does not include a broadcast-type media intervention control MAC address.
  • the method further includes:
  • the terminal device sends a media intervention control MAC address associated with the terminal device to the network device.
  • the sending, by the terminal device, the MAC address to the network device includes:
  • the terminal device sends a non-access stratum NAS message to the network device, and the NAS message includes the MAC address.
  • the method further includes:
  • the terminal device receives a request message from the network device, and the request message is used to request the MAC address associated with the terminal device.
  • the sending, by the terminal device, the MAC address to the network device includes:
  • the terminal device When the MAC address associated with the terminal device changes, the terminal device sends the changed MAC address to the network device.
  • the method further includes:
  • compression capability information is used to indicate N types of Ethernet compression capabilities supported by the terminal device, where N is an integer greater than or equal to 1;
  • the terminal device decompresses the Ethernet data packet, wherein the Ethernet data packet is generated based on a parameter of the first Ethernet compression capability.
  • the Ethernet data packet includes a first header, the first header includes a first context identifier, and the first context identifier is used to identify the first context information; the method further includes :
  • the decompressing the Ethernet data packet by the terminal device includes:
  • the terminal device decompresses the Ethernet data packet according to the first context information.
  • a communication method for Ethernet data includes:
  • the network device generates a system information block SIB, where the SIB includes an Ethernet data packet;
  • the network device sends the SIB.
  • the method further includes:
  • the network device sends a paging message to the terminal device, where the paging message includes indication information, and the indication information is used to indicate that the SIB includes the Ethernet data packet.
  • the method includes:
  • the network device sends downlink control information DCI to the terminal device, the DCI is scrambled with a first wireless network temporary identifier RNTI, the first RNTI is an RNTI for an Ethernet data packet, and the DCI includes an instruction for indicating Carries information of time-frequency resources of the Ethernet data packet.
  • the DCI includes first information, and the first information is used to indicate that the data packet scheduled by the DCI is a broadcast type Ethernet data packet or a multicast type Ethernet data packet.
  • the packet header of the Ethernet data packet does not include a broadcast type media intervention control MAC address.
  • the method further includes:
  • the receiving, by the network device, the media intervention control MAC address associated with the terminal device from the terminal device includes:
  • the network device receives a non-access stratum NAS message from the terminal device, and the NAS message includes the MAC address.
  • the method further includes:
  • the network device sends a request message to the terminal device, where the request message is used to request the MAC address associated with the terminal device.
  • the method further includes:
  • the network device Sending, by the network device, compression configuration information to the terminal device, where the compression configuration information is used to indicate a parameter of a first Ethernet compression capability, and the N types of Ethernet compression capabilities include the first Ethernet compression capability;
  • the network device generates the Ethernet data packet according to the parameter of the first Ethernet compression capability.
  • the Ethernet data packet includes a first header, the first header includes a first context identifier, and the first context identifier is used to identify the first context information.
  • a communication method for Ethernet data includes:
  • the terminal device receives a request message from a network device, the request message is used to request a media intervention control MAC address associated with the terminal device;
  • the sending, by the terminal device, the MAC address to the network device includes:
  • the terminal device sends a non-access stratum NAS message, and the NAS message includes the MAC address.
  • the network device can send the terminal device with the request information for requesting the MAC address of the terminal device, so that the terminal device can report the MAC address to the network device in time.
  • the network The device can learn the MAC address of the terminal device in time, thereby facilitating data transmission.
  • a communication method for Ethernet data includes:
  • the network device sends a request message to the terminal device, where the request message is used to request a media intervention control MAC address associated with the terminal device;
  • the network device receives the MAC address from the terminal device.
  • the receiving, by the network device, the MAC address from the terminal device includes:
  • the network device receives a non-access stratum NAS message from the terminal device, and the NAS message includes the MAC address.
  • a communication method for Ethernet data includes:
  • the terminal device sends the changed MAC address to the network device.
  • the terminal device sending the changed MAC address to the network device includes:
  • the terminal device sends a non-access stratum NAS message, and the NAS message includes the changed MAC address.
  • a communication method for Ethernet data includes:
  • the access network device receives the Ethernet data packet sent by the core network device from the public quality of service Qos flow;
  • the access network device sends the Ethernet data packet in a broadcast mode or a multicast mode.
  • an apparatus for Ethernet data for performing a method in any possible implementation manner in any of the foregoing aspects.
  • the apparatus includes a unit for performing a method in any one of the possible implementation manners of the foregoing aspects.
  • the apparatus includes a transceiver, a memory, and a processor.
  • the transceiver, the memory, and the processor communicate with each other through an internal connection path.
  • the memory is used to store instructions.
  • the processor is used to execute the instructions stored in the memory to control the receiver to receive signals and to control the transmitter to send signals. And when the processor executes the instructions stored in the memory, the processor is caused to execute the method in any one of the possible implementation manners in any of the foregoing aspects.
  • a computer program product includes computer program code that, when the computer program code is executed by a computer, causes the computer to execute the methods in the above aspects.
  • a computer-readable medium for storing a computer program, the computer program including instructions for performing the methods in the above aspects.
  • a chip including a processor, configured to call and execute instructions stored in the memory from a memory, so that a communication device installed with the chip executes the methods in the above aspects.
  • another chip including: an input interface, an output interface, a processor, and a memory.
  • the input interface, the output interface, the processor, and the memory are connected through an internal connection path.
  • the processor is configured to execute code in the memory, and when the code is executed, the processor is configured to execute the methods in the foregoing aspects.
  • FIG. 1 is a schematic structural diagram of a mobile communication system applicable to an embodiment of the present application.
  • FIG. 2 is another schematic structural diagram of a mobile communication system applicable to an embodiment of the present application.
  • FIG. 3 is a schematic diagram of an EtherCAT frame according to an embodiment of the present application.
  • FIG. 4 is a schematic interaction diagram of a communication method for Ethernet data according to an embodiment of the present application.
  • FIG. 5 is a schematic diagram of a frame format of a first Ethernet data packet according to an embodiment of the present application.
  • FIG. 6 is a schematic diagram of a frame format of a second Ethernet data packet according to an embodiment of the present application.
  • FIG. 7 is a schematic diagram of a frame format of a data packet for carrying feedback information according to an embodiment of the present application.
  • FIG. 8 is a schematic interaction diagram of another communication method for Ethernet data according to an embodiment of the present application.
  • FIG. 9 is a schematic interaction diagram of another communication method for Ethernet data according to an embodiment of the present application.
  • FIG. 10 is a schematic interaction diagram of another communication method for Ethernet data according to an embodiment of the present application.
  • FIG. 11 is a schematic interaction diagram of another communication method for Ethernet data according to an embodiment of the present application.
  • FIG. 12 is a schematic interaction diagram of another communication method for Ethernet data according to an embodiment of the present application.
  • FIG. 13 is a transition diagram of an Ethernet compressed state according to an embodiment of the present application.
  • FIG. 14 is an apparatus for Ethernet data provided by an embodiment of the present application.
  • FIG. 15 is another apparatus for Ethernet data provided by an embodiment of the present application.
  • GSM global mobile communication
  • CDMA code division multiple access
  • WCDMA broadband code division multiple access
  • GPRS general packet radio service
  • LTE long term evolution
  • FDD frequency division duplex
  • TDD Time Division Duplex
  • UMTS Universal Mobile Telecommunications System
  • WiMAX Global Interoperability for Microwave Access
  • the network device in the embodiment of the present application may be a device for communicating with a terminal device.
  • the network equipment may be a global mobile communication (GSM) system or a base station (BTS) in code division multiple access (CDMA), or a broadband code division multiple access (wideband code division multiple access, WCDMA) base station (NodeB, NB), can also be evolved base station (evolved NodeB, eNB or eNodeB) in the LTE system, or a cloud radio access network (cloud radio access network (CRAN) scenario; or the network device may be a relay station, an access point, an in-vehicle device, a wearable device, a network device in a future 5G network, or a network device in a future evolved PLMN network;
  • the network device may also be a core network device, where the core network device may be a control plane and user plane (CU) network element, or a control plane function network element CU in a CU separation scenario.
  • -CP for example,
  • the terminal device in the embodiments of the present application may refer to user equipment, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or
  • the user device may also be a robot, an operation arm, or the like, which is not limited in this embodiment of the present application.
  • the terminal device or the network device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer.
  • This hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and a memory (also called main memory).
  • the operating system may be any one or more computer operating systems that implement business processing through processes, such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a windows operating system.
  • This application layer contains applications such as browsers, address books, word processing software, and instant messaging software.
  • the embodiment of the present application does not specifically limit the specific structure of the execution subject of the method provided by the embodiment of the present application, as long as the program that records the code of the method provided by the embodiment of the application can be run to provide the program according to the embodiment of the application.
  • the communication may be performed by using the method described above.
  • the method execution subject provided in the embodiments of the present application may be a terminal device or a network device, or a function module in the terminal device or the network device that can call a program and execute the program.
  • various aspects or features of the application may be implemented as a method, apparatus, or article of manufacture using standard programming and / or engineering techniques.
  • article of manufacture encompasses a computer program accessible from any computer-readable device, carrier, or medium.
  • computer-readable media may include, but are not limited to: magnetic storage devices (eg, hard disks, floppy disks, or magnetic tapes, etc.), optical disks (eg, compact discs (CD), digital versatile discs (DVD) Etc.), smart cards and flash memory devices (for example, erasable programmable read-only memory (EPROM), cards, sticks or key drives, etc.).
  • various storage media described herein may represent one or more devices and / or other machine-readable media used to store information.
  • machine-readable medium may include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instruction (s) and / or data.
  • FIG. 1 is a schematic structural diagram of a mobile communication system applicable to an embodiment of the present application.
  • FIG. 1 is a mobile communication system of a ring network.
  • the mobile communication system includes a control device 110, an access network device 120, and at least one terminal device (such as a terminal device 131 to a terminal device 134 in FIG. 1). ).
  • the terminal device 131 and the terminal device 134 are wirelessly connected to the access network device 120.
  • the terminal device 132 and the terminal device 133 are connected to the access network device 120 through the terminal device 131 and the terminal device 134.
  • the terminal may be Device 131 or terminal device 134 is understood as a transit device.
  • the transmission path of the downlink data may be access network device 120—terminal device 131—terminal device 132, terminal device 131 can be understood as a transit device, or the transmission path of downlink data can also be access network device 120—terminal device 134—terminal device 133—terminal device 132, and terminal device 134 and terminal device 133 can be understood as transit devices.
  • the access network device 120 is connected to the control device 110 in a wireless or wired manner.
  • the control device 110 and the access network device 120 may be separate physical devices, or may be a function of the control device 110 and the access network device.
  • the logical functions of 120 are integrated on the same physical device, and may also be a physical device that integrates part of the functions of the control device 110 and part of the functions of the access network device 120.
  • the terminal equipment can be fixed or removable.
  • FIG. 1 is only a schematic diagram, and the communication system may further include other network devices, such as a wireless relay device and a wireless backhaul device, which are not shown in FIG. 1.
  • the embodiments of the present application do not limit the number of control devices, access network devices, and terminal devices included in the mobile communication system.
  • FIG. 2 is another schematic structural diagram of a mobile communication system applicable to an embodiment of the present application.
  • FIG. 2 is a star-shaped mobile communication system including a control device 210, an access network device 220, and at least one terminal device (such as the terminal device 231 to the terminal device 234 in FIG. 2). ).
  • the access network device 220 is connected to any terminal device in a wireless manner, and the access network device 220 is connected to the control device 210 in a wireless or wired manner.
  • the control device 210 and the access network device 220 may be separate physical devices, or the functions of the control device 210 and the logical functions of the access network device 220 may be integrated on the same physical device, or they may be one Some functions of the control device 210 and some functions of the access network device 220 are integrated on the physical device.
  • the terminal equipment can be fixed or removable.
  • FIG. 2 is only a schematic diagram, and the communication system may further include other network devices, such as a wireless relay device and a wireless backhaul device, which are not shown in FIG. 2. The embodiments of the present application do not limit the number of control devices, access network devices, and terminal devices included in the mobile communication system.
  • the technical solution provided in the embodiments of the present application aims at how to transmit Ethernet data in a wireless network. Based on this, the embodiments of the present application mainly describe the method for transmitting Ethernet data in a wireless network from the following four aspects:
  • the second aspect is how to transmit broadcast or multicast Ethernet data
  • MAC media access control
  • the fourth aspect is how the network equipment locates and searches for the terminal equipment.
  • EtherCAT frame is taken as an example to briefly introduce the Ethernet frame format.
  • FIG. 3 shows a schematic diagram of an EtherCAT frame.
  • the frame format of the EtherCAT frame includes an Ethernet frame header area, an EtherCAT header area, an EtherCAT data area, and a Frame Check Sequence (FCS) area.
  • the Ethernet frame header area includes the destination address, source address, and frame type. Among them, the destination address is the MAC address of the receiver, the source address is the MAC address of the sender, and the MAC address is also called the physical address.
  • the frame type is used to identify the data field. Included high-level agreements.
  • the EtherCAT header area includes EtherCAT data length, reserved bits, and type.
  • the EtherCAT data area includes a 2-byte data header and a data area of 44 to 1498 bytes.
  • the data area consists of one or more EtherCAT sub-messages, each of which corresponds to an independent device and slave storage area.
  • the FCS area is used to verify the integrity of the frame during transmission.
  • Table 1 describes the definition of each field in the Ethernet frame header area
  • Table 2 describes the definition of each field in the EtherCAT header area
  • Table 3 describes the definition of each field in each sub-message in the EtherCAT data area.
  • EtherCAT data length EtherCAT data area length, that is, the sum of all sub-message lengths Types of 1: indicates communication with the slave station; the rest are reserved
  • the destination address, source address, frame type, and fields in the EtherCAT header area in the EtherCAT frame shown in FIG. 3 are all repeated transmission contents.
  • the data length can be derived based on the information of the payload part of the data packet. In fact, it may not be necessary to transmit during the transmission process.
  • the first 7 bytes are called a preamble, and the content is a hexadecimal number 0xAA.
  • the last 1 byte is a frame start identifier 0xAB, which marks the beginning of the Ethernet frame.
  • Preamble characters are used to synchronize the receiving end and prepare to receive data frames.
  • the indefinite length data field is a 4-byte frame check sequence (FCS). This is the content required for transmission in the Ethernet and does not need to be carried in the wireless system transmission process.
  • the transmission between the terminal device and the network device is taken as an example, and as an example and not limitation, at least one of the following contents may be referred to as context information or static information:
  • the compressed Ethernet data mentioned in the embodiments of the present application refers to removing the context information from the data packet, or the compressed Ethernet data refers to information that reduces other fields in the Ethernet data packet except the data area. In order to achieve the purpose of compressing Ethernet data.
  • Ethernet data packet in the embodiment of the present application refers to a data packet carried in an ethertype session.
  • Ethernet data also refers to an ethertype session. Data.
  • the EtherCAT frame format is taken as an example above to briefly introduce the Ethernet frame format.
  • the context information of the embodiment of the present application is described below based on various frame formats.
  • Frame format 1 Ethernet 802.3 raw frame format
  • Table 4 shows the fields in the Ethernet 802.3 raw frame format.
  • the context information may include a destination MAC address, a source MAC address, and a type field.
  • the total length is the length of the data part, which can be derived from the length of the data part, and does not need to be carried during the transmission process.
  • Frame format 2 Ethernet 802.3 SAP type frame format
  • Table 5 shows the fields in the Ethernet 802.3 SAP frame format.
  • the Ethernet 802.3 SAP type frame format the two bytes of 0xFFFF in the Ethernet 802.3 raw frame are changed to DSAP and SSAP of 1 byte each.
  • a 1-byte "control" field is added to form 802.2 Logical Link Control (LLC) header.
  • LLC provides connectionless (LLC type 1) and connection-oriented (LLC type 2) network services. Among them, LLC1 is used in Ethernet, and LLC2 is used in IBM network environment system network architecture (SNA) network environment.
  • SNA IBM network environment system network architecture
  • the newly added 802.2LLC header includes two service access points: source service access point (SSAP) and destination service access point (DSAP). They are used to identify the type of upper layer data carried by the Ethernet frame.
  • SSAP source service access point
  • DSAP destination service access point
  • the hexadecimal number 0x06 represents IP protocol data
  • the hexadecimal number 0xE0 represents Novell type protocol data
  • the hexadecimal number 0xF0 represents IBM NetBIOS type protocol data.
  • the 1-byte "Control" field is basically not used (generally set to 0x03, indicating that the 802.2 unnumbered data format is used for connectionless services).
  • the context information may include a destination MAC address, a source MAC address, a DSAP, an SSAP field, and a control field.
  • the total length can be derived from the length of the data part, and it is not necessary to carry it.
  • Frame format 3 Ethernet 802.3 SNAP type frame format
  • Table 6 shows the fields in the Ethernet 802.3 SNAP frame format. Among them, the main difference between the Ethernet 802.3 SNAP type frame format and the Ethernet 802.3 SAP type frame format is:
  • the contents of the DSAP and SSAP fields of 2 bytes are fixed, and the value is 0xAA in hexadecimal.
  • the SNAP field is added, which consists of the following two items:
  • OTI ID Organizationally Unique Identifier
  • the 2-byte "type” field is used to identify the type of upper-layer data carried by the Ethernet frame.
  • the context information may include a destination MAC address, a source MAC address, a DSAP, an SSAP field, a control field, an OUI ID field, and a type field.
  • Frame format 4 Ethernet II frame format
  • Table 7 shows the fields in the Ethernet II frame format.
  • Ethernet II frame format the minimum length is 64 bytes (6 + 6 + 2 + 46 + 4) and the maximum length is 1518 bytes (6 + 6 + 2 + 1500 + 4).
  • the first 12 bytes identify the source node's MAC address and the destination node's MAC address respectively.
  • the next two bytes identify the type of upper-layer data carried by the Ethernet packet.
  • the hexadecimal number 0x0800 represents IP protocol data
  • the hexadecimal number 0x809B represents AppleTalk protocol data
  • the hexadecimal number 0x8138 represents Novell type protocol. Data, etc.
  • the context information may include a destination MAC address, a source MAC address, and a type field.
  • Frame format 5 ethernet frame format
  • the context information may include a destination MAC address, a source MAC address, a type field, and a type field of an EtherCAT header area.
  • the length field of the EtherCAT header area is the length of all sub-messages, which can be derived from the total length of the message fields.
  • the context information may include the destination MAC address, source MAC address, type field, VLAN tag, and EtherCAT header area.
  • the type field, or the context information may include a destination MAC address, a source MAC address, and a type field. It can be understood that according to the implementation optimization, the sending end can directly delete the VLAN tag, and it does not need to be stored or sent to the receiving end as part of the context information.
  • the context information may include a destination MAC address, a source MAC address, a type field, and a type field in the EetherCAT header area.
  • Frame format 6 802.1Q type frame format
  • the context information may include a destination MAC address, a source MAC address, a VLAN-1 field, and a type field, or the context information may include a destination MAC address, a source MAC address, and a field type.
  • Frame format 7 802.1Q-in-Q frame format
  • the context information may include a destination MAC address, a source MAC address, a VLAN-1 field, a VLAN-2 field, and a type field, or the context information may include a destination MAC address, a source MAC address, and a type field.
  • Frame format 8 802.3 type frame format
  • Table 10 shows the fields in the 802.3 type frame format.
  • the context information may include a destination MAC address, a source MAC address, and a length / type field.
  • the value of the length field is 0x0000-0x05DC, which is variable. If it is a length field, it is derivable information and need not be carried during transmission. For other values of this field, it has special meaning, which indicates the type of a frame. As static information, it can be used as context information, and it does not need to be carried during transmission.
  • FIG. 4 is a schematic interaction diagram of a communication method 300 for Ethernet data according to an embodiment of the present application.
  • Method 300 explains how to compress and process Ethernet data from the perspective of uplink transmission.
  • the terminal device reports its own Ethernet compression capability to the network device, and the network device configures one or more Ethernet compression capabilities for the terminal device based on the Ethernet compression capability of the terminal device, and the terminal device is based on The Ethernet compression capability configured by the network device compresses the Ethernet data, and sends the compressed data packet to the network device.
  • the terminal device sends compression capability information to the network device, where the compression capability information is used to indicate N types of Ethernet compression capabilities supported by the terminal device, where N is an integer greater than or equal to 1.
  • the Ethernet compression capability indicates the ability of the terminal device to compress Ethernet data. Specifically, the Ethernet compression capability indicates whether the terminal device can compress the Ethernet data, and if the Ethernet data can be compressed, which types of Ethernet can be compressed? Frame format.
  • the compression capability information may include information used to indicate that the compression capability supported by the terminal device is the Ethernet compression capability. In fact, since the terminal The device supports only one type of Ethernet compression capability. Although the compression capability information does not clearly indicate the type of Ethernet compression capability, for a network device, after receiving the compression capability information, it can be sure that the terminal device should It only supports one type of Ethernet compression capability. As for which type of Ethernet compression capability is supported, network devices can know or do not need to know, and will not affect other behaviors of network devices.
  • the compression capability information may include information used to indicate N types of Ethernet frame formats supported by the terminal device.
  • an Ethernet compression capability can correspond to one Ethernet frame format
  • a terminal device reporting N types of Ethernet compression capabilities indicates that the terminal device can compress N Ethernet frame formats.
  • the Ethernet frame format may be indicated by a frame format identifier for identifying the Ethernet frame format.
  • Ethernet frame format in the 802.3 protocol can include Ethernet 802.3 raw, Ethernet 802.3 SAP or Ethernet 802.3 SNAP, etc .;
  • 3 represents 802.1ad (or 802.1Q-In-Q) or vlan stacking Ethernet frame format
  • the network device sends compression configuration information to the terminal device, where the compression configuration information is used to indicate a parameter of the first Ethernet compression capability, and the N types of Ethernet compression capabilities include the first Ethernet compression capability.
  • the compression configuration information can be understood as the information that the network device enables the Ethernet compression capability for the terminal device. After receiving the compression configuration information, the terminal device knows that it can compress the Ethernet data.
  • the network equipment can configure the terminal equipment with Ethernet compression capability based on the performance requirements of the system on the data. For example, if the system does not require high data latency, the compression configuration information can be used to enable the terminal device to enable the Ethernet compression capability. Further, the terminal device can be instructed to enable several types of Ethernet compression capability. If the delay requirement is high, the compression configuration information can be used to enable the terminal device to disable the Ethernet compression capability.
  • the network device can configure the Ethernet compression capability according to the device granularity, bearer granularity, logical channel granularity, or QoS flow granularity.
  • the compression configuration information is information for all bearers of the terminal device. That is, all bearers of the terminal device use the Ethernet compression capability configured by the compression configuration information.
  • the compression configuration information is information carried by a terminal device. That is, the Ethernet compression capability of each bearer of the terminal device is independently configured, and one compression configuration information corresponds to one bearer.
  • the compression configuration information is information for a part of the bearers of all bearers of the terminal device. That is, the compression capability of the Ethernet carried by part of the terminal equipment is the same, and one compression configuration information corresponds to the partial bearer.
  • the compression configuration information is information for one logical channel of the terminal device. That is, the Ethernet compression capability of each logical channel is independently configured.
  • the compression configuration information is information for a quality of service (Qos) stream for a terminal device. That is, the Ethernet compression capability of each Qos stream is independently configured.
  • Qos quality of service
  • the compression configuration information is not only used to indicate the parameters of the first Ethernet compression capability. If the network device configures the terminal device to compress data using multiple Ethernet compression capabilities, the compression configuration information may also be used to indicate the multiple In the ether compression capability, other parameters of the ether compression capability other than the first ether compression capability. The parameters of the other ether compression capability are similar to the parameters of the first ether compression capability. For simplicity, the embodiment of the present application uses the first ether compression capability. The parameters of the capacity are taken as an example to explain the parameters of the Ethernet compression capacity.
  • the compression configuration information may further include instructing the terminal device to perform compression only on an Ethernet frame data packet whose upper layer data type is a non-IP protocol type carried in the Ethernet frame.
  • the terminal device may also optionally indicate this capability when reporting.
  • the compression configuration information may further include instructing the terminal device to only compress an Ethernet frame data packet whose upper layer data type is an IP protocol type carried in the Ethernet frame.
  • the terminal device may also optionally indicate this capability when reporting.
  • the terminal device receives the Ethernet compression configuration information, it also receives a header compression (ROHC) compression configuration information.
  • a header compression (ROHC) compression configuration information.
  • IP header compression is preferred.
  • the terminal device may also report whether it supports the capability of performing ROHC and Ethernet head compression at the same time.
  • the network device can indicate whether the terminal enables the ROHC and Ethernet header compression functions at the same time according to the capabilities of the terminal.
  • the parameter of the first Ethernet compression capability includes an enable parameter, and the enable parameter is used to instruct the terminal device to use the first Ethernet compression capability.
  • the enable parameter may be a boolean indication information.
  • the first value indicates that the terminal device can use the first Ethernet compression capability, and the second value indicates that the terminal device cannot.
  • Use the first Ethernet compression capability if the first Ethernet compression capability is one of the multiple types of Ethernet compression capabilities supported by the terminal device, and the enable parameter can indicate that the terminal device can or cannot use all the Ethernet compression capabilities Capability, the enable parameter may also be a boolean indication information.
  • the first value indicates that the terminal device can use the first Ethernet compression capability, and the second value indicates that the terminal device cannot use the first Ethernet compression capability.
  • the enable parameter can also instruct the terminal device to close or release or deconfigure the Ethernet compression capability. For example, after the terminal device turns on the Ethernet compression capability, the network device instructs the terminal device to disable the Ethernet compression capability.
  • the enable parameter can indicate that the terminal device can compress Ethernet data. As for which Ethernet compression is used, Capabilities may require additional parameter indications.
  • the parameter of the first Ethernet compression capability includes a frame format parameter for indicating a first frame format, where the first frame format is a frame format of a first Ethernet data packet.
  • the terminal device can know, based on the frame format parameter, that the Ethernet data generated based on the first frame format can be compressed.
  • the parameters of the first Ethernet compression capability may not include the enabling parameters, and the terminal device and the network device can negotiate.
  • the frame format parameter in the compression configuration information indicates the frame format that the terminal device can compress. In this way, the terminal device can only It is determined through the frame format parameter that the Ethernet data generated based on the first frame format can be compressed.
  • the embodiment of the present application also provides a possible implementation manner: the parameter of the first Ethernet compression capability further includes an instruction for indicating the first Algorithm parameters of the compression algorithm in one frame format.
  • each frame format corresponds to at least one compression algorithm, and multiple frame formats may also correspond to the same compression algorithm.
  • the compression algorithm is used to indicate how to compress the first frame format, or the compression algorithm can indicate which fields in the first frame format can be compressed, or the compression algorithm indicates that the Which fields in the first frame format are used as context information.
  • each compression algorithm can correspond to a compression protocol.
  • the compression protocol specifically describes the specification information of the compression algorithm, such as the definition of the compression format.
  • the configuration information received by the terminal device indicates which fields in the first frame format can be removed and sent directly. For example, in uplink transmission, the source address field information of the Ethernet packet header is deleted and sent.
  • the parameters of the first Ethernet compression capability may include at least one of a frame format parameter, a compression protocol parameter, or an algorithm parameter.
  • the parameters of the first Ethernet compression capability include any one of two parameters, which compression algorithm is adopted for each frame format may be prescribed by the protocol: if the parameters of the first Ethernet compression capability include the above-mentioned frame format parameters If the terminal device knows that the first frame format is used to compress the Ethernet data, it can directly obtain the compression algorithm corresponding to the first frame format parameter based on the protocol. If the parameters of the first Ethernet compression capability include algorithm parameters, the terminal device knows Algorithm parameters can be obtained based on the protocol specifications for the first frame format corresponding to the algorithm parameters. If the parameters of the first Ethernet compression capability include the compression protocol parameters, the terminal device can determine the compression protocol parameters and can obtain the frame format corresponding to the protocol specifications. Compression algorithm.
  • the terminal device In S330, the terminal device generates a first Ethernet data packet according to the parameter of the first Ethernet compression capability.
  • the terminal device uses the parameter of the first Ethernet compression capability to compress the Ethernet data, that is, remove the context information (or static information) of the Ethernet data, thereby generating a compressed first Ethernet data packet.
  • the first Ethernet data packet may be a PDCP layer data packet or an Ethernet data packet compressed by other protocol layers, which is not limited in this embodiment of the present application.
  • the first Ethernet data packet may also be an application layer (or upper layer) of a terminal device, a service data application protocol (SDAP), and a radio link control (RLC). Or MAC layer packets.
  • the terminal device sends the first Ethernet data packet to the network device.
  • the network device decompresses the first Ethernet data packet.
  • the network device In order to interact with other devices, the network device needs to continue to encapsulate the first Ethernet data packet. Therefore, the network device needs to restore the first Ethernet data packet to an uncompressed data packet. In other words, the terminal device needs to be The removed context information is added to the first Ethernet data packet, and a header area of the first Ethernet data packet is restored, thereby completing decompression of the first Ethernet data packet.
  • the terminal device reports its own Ethernet compression capability to the network device, and the network device configures one or more types of the terminal device based on the Ethernet compression capability of the terminal device.
  • Ethernet compression capability and the terminal device compresses the Ethernet data based on the Ethernet compression capability configured by the network device, and sends the compressed data packet to the network device.
  • the network device start the terminal device to use the Ethernet compression capability, it also It enables terminal equipment and network equipment to transmit compressed Ethernet data in a wireless network, which can effectively reduce the waste of resources.
  • the embodiment of the present application may not require step S310, that is, the network device does not need to configure the Ethernet compression capability for the terminal device based on the compression capability information received from the terminal device, and may directly configure the Ethernet compression capability for the terminal device.
  • the network device may know, through an uncompressed Ethernet data packet sent by the terminal device, that the terminal device only supports one type of Ethernet compression capability, and the terminal device may not be required to report The Ethernet compression capability supported by itself, the network device may send the compression configuration information to the terminal device based on the performance requirements of the system on the data to indicate the only Ethernet compression capability supported by the terminal device.
  • the network device may be an access network device or a core network device.
  • the terminal device described in the embodiment of the present application receives information from a network device (for example, network device A).
  • the terminal device may directly interact with the network device A to receive information.
  • the information may be considered as the network device.
  • the information generated by A may also be information obtained by network device A from other network devices (for example, recorded as network device B1), and then network device A forwards or transparently transmits the information to the terminal device.
  • the information can be considered It is generated by the network device B1 or the network device C1, where the network device B1 receives information from the network device C1.
  • the network device receives information from a terminal device.
  • the terminal device can directly interact with the network device A, and the network device A directly receives information from the terminal device. It may be that the terminal device sends information to other network devices (for example, network device B1), and network device B1 sends the information directly to network device A or sends the information to network device A through other network devices (for example, network device C1).
  • network device B1 sends the information directly to network device A or sends the information to network device A through other network devices (for example, network device C1).
  • the network devices are respectively an access network device and a core network device, as an example and not a limitation, a description will be given of transmission paths of compression configuration information and compression capability information.
  • the network device is an access network device.
  • the access network device generates the compression configuration information.
  • Access network equipment obtains compression configuration information from other equipment
  • a possible transmission path for compressed configuration information AMF network element ⁇ UPF network element ⁇ access network device ⁇ terminal device.
  • the compressed configuration information can be generated by the AMF network element. It can be understood that the access network device
  • the compression configuration information is received from the AMF network element or the UPF network element, and the UPF network element forwards or transparently transmits the compression configuration information generated by the AMF network element to the access network device.
  • Another possible transmission path for compressed configuration information SMF network element ⁇ UPF network element ⁇ access network device ⁇ terminal device. In this case, the compressed configuration information can be generated by the SMF network element.
  • the access network The device receives the compression configuration information from the SMF network element or the UPF network element, and the UPF network element forwards or transparently transmits the compression configuration information generated by the SMF network element to the access network device.
  • Another possible transmission path for compressed configuration information UPF network element ⁇ access network device ⁇ terminal device.
  • the compressed configuration information can be generated by the UPF network element.
  • the access network device is from the UPF network.
  • the meta receives compression configuration information.
  • one possible transmission path of compression capability information is: terminal device ⁇ access network device; if the device generating the compression configuration information is a core network device, the access network device may The compression capability information is sent to the core network equipment.
  • the network device is a core network device
  • the terminal device receives information from the network device, and the network device receives information from the terminal device. It can be understood that the UPF network element communicates with the terminal device through the core network device to transmit information,
  • the UPF network element generates the compression configuration information.
  • UPF network element ⁇ access network device ⁇ terminal device.
  • the UPF network element obtains the compression configuration information from other devices.
  • AMF network element ⁇ UPF network element ⁇ access network device ⁇ terminal device Another possible transmission path for compressed configuration information: SMF network element ⁇ UPF network element ⁇ access network Device ⁇ Terminal device.
  • terminal device When the network device is a UPF network element, one possible transmission path of compression capability information: terminal device ⁇ access network device ⁇ UPF network element; another possible transmission path of compression capability information: terminal device ⁇ access Network access equipment-AMF network element-SMF network element-UPF network element.
  • any two devices may transmit compression configuration information through different signaling.
  • the AMF network element may send the compression configuration information to the UPF network element through non-access-stratum (NAS) signaling, where the NAS signaling may be a registration response message, a protocol data unit (protocol data unit, PDU) session establishment.
  • the AMF network element may also send the compression configuration information to the terminal device through the access network device through NAS signaling.
  • the access device sends compression configuration information to the terminal device through RRC signaling or PDCP control signaling.
  • a UPF network element may send compression configuration information to a terminal device through other devices through compression signaling in an Ethernet data packet.
  • the first Ethernet data packet does not include context information (in order to facilitate the distinction and understanding, it is recorded as the first context information), but in order to enable the network device to obtain the first context information to facilitate the network device Decompress the first Ethernet data packet.
  • the first Ethernet data packet includes a first header, the first header includes a first context identifier, and the first context identifier is used to identify the first context information. as well as,
  • the method also includes:
  • the network device decompressing the first Ethernet data packet includes:
  • the network device decompresses the first Ethernet data packet according to the first context information.
  • the network device obtains the first context identifier from the first header of the first Ethernet data packet, and obtains the context information corresponding to the first context identifier (that is, the first context information) based on the first context identifier. ) Therefore, the first Ethernet data packet is decompressed based on the first context information, where the first context information may be context information of different frame formats listed above and not listed above.
  • the first context identifier is located in a field of the first packet header (for convenience of distinguishing and understanding, it is denoted as field 1), that is, field 1 is used to carry the first context identifier.
  • the first header may further include other fields, and each field carries corresponding content.
  • the first header further includes at least one of the following fields.
  • a field for indicating whether the first Ethernet data packet is compressed (for convenience of distinction and understanding, it is denoted as field 2), where field 2 indicates that the first Ethernet data packet is compressed.
  • a field for indicating the compression configuration identifier of the frame format of the first Ethernet data packet (for convenience of distinguishing and understanding, it is recorded as field 3).
  • a field for indicating a cyclic redundancy check (cyclic redundancy check, CRC) (for the convenience of distinguishing and understanding, it is recorded as field 4).
  • the terminal device can determine which fields the first packet header includes according to field 5, that is, determine the format of the first header, and thus read the content of each field according to the determined format of the first header.
  • FIG. 5 is a schematic diagram of a frame format of a first Ethernet data packet according to an embodiment of the present application.
  • the first Ethernet data packet includes a data area and a header (that is, a first header) area.
  • the first header area includes at least four fields, that is, field 1, field 2, field 3, and field. 4.
  • Field 1 carries a first context identifier
  • field 2 carries information used to indicate that the first Ethernet data packet is compressed
  • field 3 carries a compression configuration identifier
  • field 4 carries a CRC.
  • the network device can further obtain the corresponding context information through the context identifier, which can effectively ensure that the network device successfully decompresses the Ethernet data. package.
  • the network device may obtain the context information corresponding to the first context identifier based on the first context identifier. Specifically, the network device may obtain the context information from the first context identifier and the first context information based on the first context identifier. The first context information is obtained in a first correspondence relationship between the two.
  • the embodiments of the present application provide various possible implementation manners. The following describes the specific manner in which the network device obtains the first correspondence relationship.
  • the network device obtains the first correspondence relationship from the terminal device. That is, the terminal device generates the first correspondence relationship, and sends the first correspondence relationship to the network device.
  • the time sequence in which the terminal device sends the first correspondence may be before the first Ethernet data packet is generated, or after the first Ethernet data packet is generated, as long as the network device decompresses the first Just send the Ethernet packet to the network device.
  • the terminal device sends a correspondence relationship between the context identifier and the context information to the network device, and the correspondence relationship includes the first correspondence relationship.
  • the correspondence relationship indicates a correspondence relationship between at least one context identifier and at least one context information, and each context identifier corresponds to one context information.
  • the following uses the first correspondence relationship as an example to describe the manner in which the terminal device sends the correspondence relationship.
  • the terminal device may send the first correspondence relationship to the network device through various forms of signaling, such as radio resource control (radio resource control (RRC) signaling, non-access layer). (non-access-stratum, NAS) signaling or application layer signaling for Ethernet header compression.
  • RRC radio resource control
  • non-access layer non-access layer
  • NAS non-access-stratum
  • a network device may correspond to multiple terminal devices, which means that a destination MAC address can correspond to multiple source MAC addresses.
  • the destination MAC address and source MAC address belong to the context information.
  • the source MAC address and the destination MAC address are not exactly the same.
  • a network device corresponds to two terminal devices (terminal device A and terminal device B).
  • terminal device A and terminal device B For the same frame format, there will be two context information.
  • One context information includes the MAC addresses of the network device and terminal device A, and the other context The information includes the MAC addresses of the network device and the terminal device B.
  • a context identifier can be generated in a frame format. For example, if frame format 1 corresponds to two context identifiers and frame format 2 corresponds to two context identifiers, the two context identifiers in frame format 1 may be 0 and 1, and the two context identifiers in frame format 2 may also be 0 and 1. 1.
  • the terminal device sends to the network device Information for indicating a frame format (ie, a first frame format) corresponding to the first correspondence relationship.
  • the network device can know that the first correspondence relationship is for the correspondence relationship of the first frame format, and store the above-mentioned context identifier for saving the number of bits.
  • the first frame format and the first correspondence may be carried in the same information or in different information, which is not limited in the embodiment of the present application.
  • the terminal device can also carry a correspondence relationship in the header of the uncompressed Ethernet data packet when sending the uncompressed Ethernet data packet, and the correspondence relationship represents the uncompressed Ethernet data packet.
  • the context information and corresponding context identifier of the frame format of the data packet In this way, the network device can obtain the corresponding relationship from the uncompressed Ethernet data packet and store it. In this way, if a subsequent terminal device sends a frame format and the uncompressed
  • the compressed Ethernet data packet has the same frame format as the Ethernet data packet, and the network device can directly obtain the context information of the compressed Ethernet data packet based on the correspondence stored in advance, and then successfully decompress the Ethernet data packet.
  • the terminal device sends a second Ethernet data packet to the network device, and the second Ethernet data packet includes a second header, and the second header Including the first correspondence.
  • the correspondence relationship other than the first correspondence relationship may also be carried by an uncompressed Ethernet data packet.
  • the second header further includes a frame format of the second Ethernet data packet, and the frame format of the second Ethernet data packet is similar to the frame format of the second Ethernet data packet.
  • the frame format (ie, the first frame format) of the first Ethernet data packet is the same.
  • FIG. 6 is a schematic diagram of a frame format of a second Ethernet data packet according to an embodiment of the present application.
  • the frame format of the second Ethernet data packet is a frame format of an uncompressed data packet.
  • the second Ethernet data packet includes a data area and a header (that is, a second header) area.
  • the header area includes at least field 1 and field 5, where field 1 carries the first context identifier and field 5 carries the first context information.
  • the second may further include at least one of field 2, field 3, or field 5, where field 2 carries information used to indicate that the second Ethernet data packet is not compressed, and field 3 carries A compression configuration identifier indicating a frame format of the second Ethernet data packet.
  • Field 4 carries a CRC.
  • the network device and the terminal device are required to jointly maintain the correspondence between the context identifier and the context information.
  • the present invention provides a possible implementation manner:
  • the network device sends first instruction information to the terminal device, where the first instruction information is used to indicate the maximum number of context information generated by the terminal device.
  • the network device obtains the first correspondence relationship from a pre-stored correspondence between at least one context information and at least one context identifier based on the first context identifier, where each context information corresponds to a context identifier.
  • the pre-stored correspondence relationship may be prescribed by a system or a protocol, or may be generated in advance by a network device.
  • the system or protocol can configure M context information for different compressible frame formats, or the network device can generate M context information based on different compressible frame formats, and for the convenience of query and identification, for Each context information is configured with a corresponding context identifier.
  • a related feedback mode is set for whether the network device successfully receives the first correspondence relationship and whether the first Ethernet data packet is successfully decompressed.
  • the method further includes:
  • the terminal device receives feedback mode information, and the feedback mode information includes any one of the following: a positive acknowledgement (ACK) feedback mode, a negative acknowledgement (NACK) feedback mode, or a no feedback mode.
  • ACK positive acknowledgement
  • NACK negative acknowledgement
  • the ACK feedback mode indicates that if the network device successfully receives the first correspondence relationship, the network device sends feedback information to the terminal device. Conversely, if the network device does not successfully receive the first correspondence relationship, the network device does not send feedback. Information, if the terminal device does not receive the feedback information within a preset time period, it is considered that the network device has not successfully received the first correspondence relationship.
  • the NACK feedback mode indicates that if the network device does not successfully receive the first correspondence relationship, the network device sends feedback information to the terminal device. Conversely, if the network device successfully receives the first correspondence relationship, the network device does not send feedback. Information, if the terminal device does not receive the feedback information within a preset time period, it is considered that the network device successfully receives the first correspondence relationship.
  • the non-feedback mode indicates that after sending the first correspondence, the terminal device does not pay attention to whether the network device successfully receives the first correspondence, and does not need to receive feedback information sent by the network device.
  • the ACK feedback mode indicates that if the network device successfully decompresses the first Ethernet data packet, the network device sends feedback information to the terminal device. Conversely, if the network device does not successfully decompress the first Ethernet data packet, then The network device does not send feedback information, and the terminal device does not receive the feedback information within a preset time, it is considered that the network device has not successfully decompressed the first Ethernet data packet.
  • the NACK feedback mode indicates that if the network device does not successfully decompress the first Ethernet data packet, the network device sends feedback information to the terminal device. Conversely, if the network device successfully decompresses the first Ethernet data packet, then The network device does not send feedback information, and the terminal device does not receive the feedback information within a preset time, it is considered that the network device successfully decompresses the first Ethernet data packet.
  • the non-feedback mode indicates that after sending the first Ethernet data packet, the terminal device does not care whether the network device successfully decompresses the first Ethernet data packet and does not need to receive feedback information sent by the network device.
  • the terminal device may receive other parameters about the no-feedback mode from the configuration information of the network device, such as N and M.
  • N represents the number of times that the sending end (for example, the terminal device) sends a non-compressed data packet to start the compressed mode
  • M represents the length of time that the sending end (for example, the terminal device) can send the compressed data packet. Send in compressed mode all the time, reset the above information after the timer expires.
  • the method further includes:
  • the network device sends first feedback information to the terminal device, and the first feedback information is used to instruct the network device to successfully receive the first correspondence relationship.
  • the first feedback information may include at least one of the following: the first context identifier or ACK information.
  • the first feedback information may further include a sequence of the second Ethernet data packet.
  • the network device can also be instructed to successfully receive the first correspondence.
  • a data packet for carrying feedback information may be independently designed.
  • the first feedback information is carried in a load domain of a data packet sent by a network device.
  • FIG. 7 is a schematic diagram of a frame format of a data packet for carrying feedback information according to an embodiment of the present application.
  • the data packet includes a packet header and a payload area.
  • the packet header may include at least a field for indicating whether the data packet is a data packet of a data type or a data packet of control information, that is, D / C, where: D indicates data, C indicates control information, and includes a type field.
  • the type field may be a field used to indicate the feedback information of Ethernet compression, and R indicates a reserved field; the load area is to carry feedback information (for example, the first feedback information )Area.
  • the method further includes:
  • the network device sends second feedback information to the terminal device, and the second feedback information is used to instruct the network device to successfully decompress the first Ethernet data packet.
  • the second feedback information may include at least one of the following: a sequence of the first Ethernet data packet or ACK information.
  • a data packet for carrying feedback information may be independently designed.
  • the second feedback information is carried in a load domain of a data packet sent by a network device.
  • the frame format of the data packet used to carry the feedback information reference may be made to the description in FIG. 7. For brevity, details are not described herein again.
  • the terminal device may send indication information to the network device to indicate resetting the compression context.
  • the instruction information is used to instruct the network device to delete the context information stored in the network device. It can also be understood that both parties need to renegotiate the compression context information.
  • entity refers to a logical entity, which is implemented in the form of a logical instance, and is specifically implemented in software.
  • entity refers to a logical entity, which is implemented in the form of a logical instance, and is specifically implemented in software.
  • the function of the entity It is assumed that the embodiments of the present application may include a PDCP entity and a compression / decompression entity.
  • S310 and / or S320 may be implemented on the PDCP entity
  • S330 and / or S350 may be implemented on the compression / decompression entity.
  • the PDCP entity After executing the S310 and / or S320, the PDCP entity starts the compression / decompression entity, generates an Ethernet data packet, and sends the Ethernet data packet to the compression / decompression entity of the network device, so that the network device performs the decompression function.
  • the embodiments of the present application may all be implemented on a PDCP entity.
  • the embodiments of the present application are all implemented in a compression / decompression entity.
  • the process of compressing and processing Ethernet data in the embodiment of the present application has been described from the perspective of uplink transmission.
  • the process of compressing and processing Ethernet data in the embodiment of the present application will be described from the perspective of downlink transmission.
  • the Ethernet data packets and the like are distinguished by the third and fourth.
  • the first, second, third, and fourth, etc. are not used to limit their order, and from the downlink, the third and fourth here can be replaced by the first and second.
  • FIG. 8 is a schematic interaction diagram of a communication method 400 for Ethernet data according to an embodiment of the present application.
  • the terminal device reports its own Ethernet compression capability to the network device, and the network device configures one or more Ethernet compression capabilities for the terminal device based on the Ethernet compression capability of the terminal device, and the network device is based on the configured
  • the Ethernet compression capability compresses the Ethernet data and sends the compressed data packets to the terminal device.
  • the terminal device sends compression capability information to the network device, where the compression capability information is used to indicate N types of Ethernet compression capabilities supported by the terminal device, where N is an integer greater than or equal to 1.
  • the network device sends and receives compression configuration information to the terminal device, where the compression configuration information is used to indicate a parameter of a third Ethernet compression capability, and the N types of Ethernet compression capabilities include the third Ethernet compression capability.
  • the network device enables the Ethernet compression information for the terminal device.
  • the role of the compression configuration information is slightly different from the specific role of the compression configuration information in uplink transmission. That is, the terminal device receives the compression configuration information. After enabling the Ethernet compression capability, make sure that the network device will send compressed Ethernet data packets in the future, and which Ethernet compression capabilities will be used to compress the Ethernet data packets, in order to be able to decompress the compressed Ethernet data sent by the network device. compression.
  • the terminal device enables the Ethernet compression capability, which means that the terminal device can decompress the received compressed Ethernet data.
  • a function entity may also be configured for the compression or decompression function. Based on the compression configuration information, the received Ethernet data packet may be directly completed based on the decompression function entity.
  • the parameter of the third Ethernet compression capability includes an enable parameter, and the enable parameter is used to instruct the terminal device to use the third Ethernet compression capability.
  • enabling parameters For the description of the enabling parameters, refer to the description of the enabling parameters in S320 in method 300.
  • the parameter of the third Ethernet compression capability includes a frame format parameter for indicating a third frame format
  • the third frame format is a frame format of a third Ethernet data packet.
  • the terminal device can know, based on the frame format parameter, that the network device can compress the Ethernet data generated based on the third frame format.
  • the parameter of the third Ethernet compression capability may not include the enabling parameter, and the terminal device and the network device can negotiate.
  • the frame format parameter in the compression configuration information indicates the frame format that the network device can compress. In this way, the terminal device can only It is determined through the frame format parameter that the Ethernet data generated based on the third frame format can be decompressed.
  • the parameter of the third Ethernet compression capability further includes an algorithm parameter used to indicate a compression algorithm of the third frame format.
  • the configuration information received by the terminal device indicates which fields in the third frame format have been removed.
  • the network device In S430, the network device generates a third Ethernet data packet according to the parameter of the third Ethernet compression capability.
  • the network device uses the parameter of the third Ethernet compression capability to compress the Ethernet data, that is, the context information of the Ethernet data packet is removed, thereby generating a compressed third Ethernet data packet.
  • the first Ethernet data packet transmitted in the uplink and the third Ethernet data packet transmitted in the downlink may be Ethernet data packets at the PDCP layer or Ethernet data packets at other protocol layers. There are no restrictions on this.
  • the network device sends the third Ethernet data packet to the terminal device.
  • the terminal device decompresses the third Ethernet data packet.
  • the terminal device needs to restore the third Ethernet data packet to an uncompressed data packet.
  • the context information removed by the network device needs to be added to the third Ethernet data packet to restore the third Ethernet data packet. Header area of the network data packet, thereby completing decompression for the third Ethernet data packet.
  • the terminal device reports its own Ethernet compression capability to the network device, and the network device configures one or more types of the terminal device based on the Ethernet compression capability of the terminal device.
  • the Ethernet compression capability can enable the terminal device to enable the decompression function of the Ethernet data packet.
  • the terminal device sends the compressed data packet to the network device. It can enable terminal equipment and network equipment to transmit compressed Ethernet data in a wireless network, and can effectively reduce signaling overhead.
  • the third Ethernet data packet includes a third header
  • the first The three-packet header includes a third context identifier, which is used to identify the third context information
  • the method also includes:
  • the terminal device decompressing the third Ethernet data packet includes:
  • the terminal device decompresses the third Ethernet data packet according to the third context information.
  • the terminal device obtains the third context identifier from the third header of the third Ethernet data packet, and obtains the context information corresponding to the third context identifier (that is, the third context information) based on the third context identifier. ) Therefore, the third Ethernet data packet is decompressed based on the third context information, where the third context information may be context information of different frame formats listed above and not listed above.
  • the embodiment of the present application further adds a context identifier for identifying the context information to the header of the Ethernet data packet to further enable the terminal device to obtain the corresponding context information through the context identifier, which can effectively ensure that the terminal device successfully decompresses the Ethernet data. package.
  • the terminal device may obtain the context information corresponding to the third context identifier based on the third context identifier. Specifically, the terminal device may obtain the context information from the third context identifier and the third context information based on the third context identifier.
  • the third context information is obtained in a third correspondence relationship between them.
  • the embodiments of the present application provide various possible implementation manners. In the following, the specific manner in which the terminal device obtains the third correspondence relationship is briefly described.
  • the terminal device acquires the third correspondence relationship from the network device. That is, the network device generates the third correspondence relationship, and sends the third correspondence relationship to the terminal device.
  • the network device sends a correspondence relationship between the context identifier and the context information to the terminal device, and the correspondence relationship includes the third correspondence relationship.
  • the correspondence relationship indicates a correspondence relationship between at least one context identifier and at least one context information, and each context identifier corresponds to one context information.
  • the following uses the third correspondence relationship as an example to describe a manner in which the network device sends the correspondence relationship.
  • the network device may send the third correspondence to the terminal device through various forms of signaling, for example, radio resource control (radio resource control (RRC) signaling).
  • RRC radio resource control
  • the network device sends to the terminal device.
  • Information indicating a frame format (ie, a third frame format) corresponding to the third correspondence relationship In this way, the terminal device can know that the third correspondence relationship is for the correspondence relationship of the third frame format, and store the above-mentioned context identifier for saving the number of bits.
  • the third frame format and the third correspondence may be carried in the same information or in different information, which is not limited in the embodiment of the present application.
  • the network device can also carry a corresponding relationship in the header of the uncompressed Ethernet data packet when sending the uncompressed Ethernet data packet.
  • the uncompressed Ethernet indicated by the correspondence relationship Context information and corresponding context identifier of the frame format of the network data packet.
  • the terminal device can obtain the corresponding relationship from the uncompressed Ethernet data packet and store it.
  • a subsequent network device sends a frame format and the The compressed Ethernet data packet has the same frame format as the compressed Ethernet data packet.
  • the terminal device can directly obtain the context information of the compressed Ethernet data packet based on the correspondence stored in advance, and then successfully decompress the Ethernet data packet.
  • the network device sends a fourth Ethernet data packet to the terminal device, where the fourth Ethernet data packet includes a fourth header, and the fourth header
  • the network device sends a fourth Ethernet data packet to the terminal device, where the fourth Ethernet data packet includes a fourth header, and the fourth header
  • the third correspondence relationship is included.
  • the fourth packet header further includes a frame format of the fourth Ethernet data packet, and the frame format of the fourth Ethernet data packet is similar to the frame format of the fourth Ethernet data packet.
  • the frame format (ie, the third frame format) of the third Ethernet data packet is the same.
  • the network device and the terminal device are required to jointly maintain the correspondence between the context identifier and the context information.
  • the present invention provides a possible implementation manner:
  • the network device sends first instruction information to the terminal device, where the first instruction information is used to indicate the maximum number of context information generated by the terminal device.
  • the terminal device obtains the third correspondence relationship from a pre-stored correspondence between at least one context information and at least one context identifier based on the third context identifier, where each context information corresponds to one context identifier.
  • the pre-stored correspondence relationship may be prescribed by the system or protocol, or may be generated in advance by the terminal device.
  • the system or protocol can configure M context information for different compressible frame formats, or the terminal device can generate M context information based on different compressible frame formats, and, for convenience of query and identification, for Each context information is configured with a corresponding context identifier.
  • a relevant feedback mode is set for whether the terminal device successfully receives the third correspondence relationship and whether the third Ethernet data packet is successfully decompressed.
  • the method further includes:
  • the network device sends feedback mode information, and the feedback mode information includes any of the following: a positive acknowledgement (ACK) feedback mode, a negative acknowledgement (NACK) feedback mode, or a no feedback mode.
  • ACK positive acknowledgement
  • NACK negative acknowledgement
  • the feedback mode information may be configuration information sent by a network device.
  • the ACK feedback mode indicates that if the terminal device successfully receives the third correspondence relationship, the terminal device sends feedback information to the network device. Conversely, if the terminal device does not successfully receive the third correspondence relationship, the terminal device does not send feedback. Information, if the network device does not receive the feedback information within a preset time period, it is considered that the terminal device has not successfully received the third correspondence relationship.
  • the NACK feedback mode indicates that if the terminal device does not successfully receive the third correspondence relationship, the terminal device sends feedback information to the network device. Conversely, if the terminal device successfully receives the third correspondence relationship, the terminal device does not send feedback. Information, if the network device does not receive the feedback information within a preset time period, it is considered that the terminal device successfully receives the third correspondence relationship.
  • the non-feedback mode indicates that after sending the third correspondence relationship, the network device does not pay attention to whether the terminal device successfully receives the third correspondence relationship and does not need to receive feedback information sent by the terminal device.
  • the terminal device may receive other parameters about the no-feedback mode from the configuration information of the network device, such as N and M.
  • N represents the number of times that the sender (for example, a network device) sends an uncompressed packet to start the compressed mode
  • M represents the length of time that the sender (for example, a network device) can send a compressed packet after the compressed mode is started. Send in compressed mode all the time, reset the above information after the timer expires.
  • the ACK feedback mode indicates that if the terminal device successfully decompresses the third Ethernet data packet, the terminal device sends feedback information to the network device. Conversely, if the terminal device does not successfully decompress the third Ethernet data packet, then The terminal device does not send feedback information, and the network device does not receive the feedback information within a preset time period, it is considered that the terminal device has not successfully decompressed the third Ethernet data packet.
  • the NACK feedback mode indicates that if the terminal device does not successfully decompress the third Ethernet data packet, the terminal device sends feedback information to the network device. Conversely, if the terminal device successfully decompresses the third Ethernet data packet, then The terminal device does not send feedback information, and the network device does not receive the feedback information within a preset time, it is considered that the terminal device successfully decompresses the third Ethernet data packet.
  • the non-feedback mode indicates that after sending the third Ethernet data packet, the network device does not pay attention to whether the terminal device successfully decompresses the third Ethernet data packet and does not need to receive feedback information sent by the terminal device.
  • the following uses the ACK feedback mode as an example to describe the process of sending feedback information to the terminal device from the terminal device's reception of the third correspondence relationship and the terminal device's decompression of the third Ethernet data. .
  • the method further includes:
  • the terminal device sends third feedback information to the network device, and the third feedback information is used to indicate that the terminal device successfully receives the third correspondence relationship.
  • the third feedback information may include at least one of the following: the third context identifier or ACK information.
  • the third feedback information may further include a sequence of the fourth Ethernet data packet. In this way, it can also indicate that the terminal device successfully receives the third correspondence relationship.
  • a data packet for carrying feedback information may be independently designed.
  • the third feedback information is carried in a load field of a data packet sent by the terminal device.
  • the frame format of the data packet used to carry the feedback information reference may be made to the description of FIG. 7 above. For brevity, details are not described herein again.
  • the method further includes:
  • the terminal device sends fourth feedback information to the network device, and the fourth feedback information is used to instruct the terminal device to successfully decompress the third Ethernet data packet.
  • the fourth feedback information may include at least one of the following: a sequence of the third Ethernet data packet or ACK information.
  • a data packet for carrying feedback information may be independently designed.
  • the fourth feedback information is carried in a load domain of a data packet sent by the terminal device.
  • the frame format of the data packet used to carry the feedback information reference may be made to the description in FIG. 7. For brevity, details are not described herein again.
  • the steps in the embodiments of the present application can be implemented on one functional entity or multiple entities.
  • the entity refers to a logical entity and is implemented in the form of a logical instance.
  • the function of this entity is realized by software. It is assumed that the embodiment of the present application may include a PDCP entity and a compression / decompression entity.
  • S410 and / or S420 may be implemented on the PDCP entity, and S430 and / or S450 may be implemented on the compression / decompression entity.
  • the PDCP entity After executing S410 and / or S420, the PDCP entity starts the compression / decompression entity, generates an Ethernet data packet, and sends the Ethernet data packet to the compression / decompression entity of the terminal device, so that the terminal device performs the decompression function.
  • the embodiments of the present application may all be implemented on a PDCP entity.
  • the embodiments of the present application are all implemented in a compression / decompression entity.
  • FIG. 9 is a schematic interaction diagram of a communication method 500 for Ethernet data according to an embodiment of the present application.
  • the receiving end may be a terminal device and the sending end is a network device; or, the receiving end is a network device and the sending end is a terminal device.
  • the sending end generates a fifth Ethernet data packet, where the fifth Ethernet data packet includes a fifth header, the fifth header includes a fifth context identifier, and the fifth context identifier is used to identify the fifth context information;
  • the sending end sends a fifth Ethernet data packet to the receiving end.
  • the receiving end obtains the fifth context information according to the fifth context identifier.
  • the receiving end decompresses the fifth Ethernet data packet according to the fifth context information.
  • the sending end can effectively reduce the waste of resources by sending the compressed Ethernet data packet (for example, the fifth Ethernet data packet) to the receiving end, and Adding a context identifier for identifying the context information to the header of the Ethernet data packet enables the receiving end to obtain the corresponding context information through the context identification, which effectively guarantees the probability that the receiving end successfully decompresses the Ethernet data packet.
  • the compressed Ethernet data packet for example, the fifth Ethernet data packet
  • Adding a context identifier for identifying the context information to the header of the Ethernet data packet enables the receiving end to obtain the corresponding context information through the context identification, which effectively guarantees the probability that the receiving end successfully decompresses the Ethernet data packet.
  • the sending end sends a corresponding relationship between the following identifier and the context information to the receiving end, and the corresponding relationship includes a fifth correspondence between the fifth context identifier and the fifth context identifier.
  • the sending end sends a sixth Ethernet data packet to the receiving end, the sixth Ethernet data packet includes a sixth header, and the sixth header includes a correspondence between the fifth context identifier and the fifth context information .
  • the uncompressed Ethernet data packet (for example, the sixth Ethernet data packet) carries the corresponding relationship, which can reduce signaling overhead and save resources.
  • the sixth packet header further includes indication information for indicating a type of a frame format of the sixth Ethernet data packet, and a type of the frame format of the sixth Ethernet data packet is the same as that of the fifth Ethernet data packet.
  • the type of frame format is the same.
  • the system can be made to establish at least one context identifier for each frame format, and identify context information in each frame format. , Can save the number of bits occupied by the context identifier.
  • the method further includes:
  • the receiving end sends fifth feedback information to the sending end, and the fifth feedback information is used to indicate that the receiving end successfully receives the corresponding relationship.
  • the fifth feedback information includes: a context identifier in the correspondence relationship.
  • the fifth feedback information includes a fifth context identifier in the fifth corresponding relationship.
  • the method further includes:
  • the receiving end sends sixth feedback information to the sending end, and the sixth feedback information is used to indicate that the receiving end successfully decompresses the fifth data packet.
  • the sending end is a terminal device, and the receiving end is a network device; and, the method further includes:
  • the sending end sends compression capability information to the receiving end, where the compression capability information is used to indicate N types of Ethernet compression capabilities supported by the sending end, where N is an integer greater than or equal to 1;
  • the receiving end sends compression configuration information to the receiving end, where the compression configuration information is used to indicate a parameter of a fifth ether compression capability, and the N types of ether compression capabilities include the fifth ether compression capability; and,
  • the sending end generates a fifth Ethernet data packet, including:
  • the sending end generates the fifth Ethernet data packet according to the parameter of the fifth Ethernet compression capability.
  • the sending end is a network device
  • the receiving end is a terminal device
  • the method further includes:
  • the receiving end sends compression capability information to the transmitting end, where the compression capability information is used to indicate N types of Ethernet compression capabilities supported by the receiving end, where N is an integer greater than or equal to 1;
  • the sending end sends compression configuration information to the receiving end, where the compression configuration information is used to indicate a parameter of a fifth ether compression capability, and the N types of ether compression capabilities include the fifth ether compression capability; and,
  • the sending end generates a fifth Ethernet data packet, including:
  • the sending end generates the fifth Ethernet data packet according to the parameter of the fifth Ethernet compression capability.
  • the receiving end is a network device
  • the transmitting end is a terminal device.
  • the method in this embodiment of the present application may refer to the method 300.
  • the fifth Ethernet data packet in the method 500 may correspond to the first Ethernet data packet in the method 300
  • the fifth header in the method 500 may correspond to the first header in the method 300
  • the fifth context identifier in the method 500 may be used to identify the fifth context identifier in the method 500.
  • the fifth context information in method 500 may correspond to the first context information in method 300, and the fifth correspondence in method 500 may correspond to the first correspondence in method 300, method
  • the sixth Ethernet data packet in 500 may correspond to the second Ethernet data packet in method 300, the sixth header in method 500 may correspond to the second header in method 300, and the fifth feedback information in method 500 may correspond to method
  • the first feedback information in 300 and the sixth feedback information in method 500 may correspond to the second feedback information in method 300.
  • the receiving end may be a terminal device and the sending end may be a network device.
  • the fifth Ethernet data packet in method 500 may correspond to the third Ethernet data packet in method 400
  • the fifth header in method 500 may correspond to the third header in method 400
  • the fifth context identifier in method 500 May correspond to the third context identifier in method 400
  • the fifth context information in method 500 may correspond to the third context information in method 400
  • the fifth correspondence in method 500 may correspond to the third correspondence in method 400.
  • the sixth Ethernet data packet in 500 may correspond to the fourth Ethernet data packet in method 400
  • the sixth header in method 500 may correspond to the fourth header in method 400
  • the fifth feedback information in method 500 may correspond to method The third feedback information in 400
  • the sixth feedback information in method 500 may correspond to the fourth feedback information in method 400.
  • the sender is in the initialization state.
  • the initialization state indicates that the sender has configured the related Ethernet compression / decompression function.
  • the receiving end may send an Ethernet compression initialization instruction.
  • the receiver After receiving the instruction, the receiver starts preparing the Ethernet compression / decompression function. For example, an initialization indication is added to a PDCP subheader or Ethernet compression signaling, MAC signaling, RRC signaling, or NAS signaling. It can be understood that the subsequent Ethernet data packets received by the receiving end need to be processed through the decompression function. The Ethernet packet sent by the sender needs to be processed by the compression function.
  • the sending end sends an uncompressed Ethernet data packet, where the uncompressed Ethernet data packet can carry the context information that needs to be stored by the receiving end.
  • the sender does not establish context information
  • the sending end and the receiving end are out of synchronization
  • the sender transitions from the initialized state to the compressed state when any of the following events occur:
  • the receiving end may send an Ethernet compression start instruction.
  • the receiving end starts the Ethernet compression / decompression function.
  • a PDCP subheader or Ethernet compression signaling, MAC signaling, RRC signaling, NAS signaling is added with a start indication. It can be understood that the subsequent Ethernet data packets received by the receiving end need to be processed through the decompression function. The Ethernet packet sent by the sender needs to be processed by the compression function.
  • the sender After determining to send the compressed Ethernet data packet, the sender sends the compressed Ethernet data packet.
  • the receiving end may send an Ethernet compression suspend instruction, and after receiving the instruction, the sending end performs a suspension of the Ethernet compression behavior.
  • an Ethernet compression suspend instruction For example, a PDCP subheader or Ethernet compression signaling, MAC signaling, RRC signaling, NAS signaling is added with an Ethernet compression suspension indication.
  • the receiving end may send an Ethernet compression recovery instruction, and after receiving the instruction, the receiving end resumes the Ethernet compression behavior.
  • an Ethernet compression recovery indication is added to a PDCP subheader or Ethernet compression signaling, MAC signaling, RRC signaling, and NAS signaling.
  • the sender changes from the compression pending state to the initialization state.
  • the terminal when the terminal receives an instruction to reset the Ethernet compression cache, the terminal resets the context information of the Ethernet compression cache.
  • an Ethernet compression buffer reset indication is added to a PDCP subheader or Ethernet compression signaling, MAC signaling, RRC signaling, or NAS signaling.
  • it is used to resynchronize the contexts of both parties when a terminal handover occurs.
  • the second aspect describes a solution on how to transmit broadcast type or multicast type Ethernet data packets.
  • two types of transmission of broadcast type or multicast type Ethernet data are provided.
  • the mode of the package ie, mode A and mode B.
  • mode A an RNTI for a broadcast type or multicast type Ethernet data packet is proposed, and a network device sends a broadcast type Ethernet data packet based on the RNTI; in mode B, a system message block (system information (blocks, SIB) to send broadcast Ethernet packets.
  • SIB system information
  • Broadcast mode When sending a data packet based on the broadcast method, the data packet is sent from a single source to all hosts on the shared Ethernet, and all hosts receiving the data packet must receive and process the data packet.
  • the length of the MAC address of a broadcast type Ethernet packet is 48 bits, each bit value is 1, and when displayed in hexadecimal, it is FF-FF-FF-FF-FF- FF.
  • Multicast mode When a data packet is sent based on the multicast mode, the data packet is sent from the source device to a group of hosts.
  • the multicast mode can be understood as a selective broadcast mode.
  • a host belonging to a group is assigned a multicast address. The host listens to a specific multicast address, and receives and processes packets whose destination MAC address is the multicast MAC address.
  • an Ethernet data packet sent in a broadcast mode may be referred to as a broadcast type Ethernet data packet
  • an Ethernet data packet sent in a multicast manner may be referred to as a multicast type Ethernet.
  • the Ethernet data packets sent in unicast mode are called unicast Ethernet packets.
  • the RNTI for Ethernet packets of broadcast type can be referred to as the RNTI of the broadcast type
  • the RNTI for Ethernet packets of the multicast type can be referred to as the RNTI of the multicast type
  • the unicast Ethernet data can be referred
  • the RNTI of a packet is simply referred to as a unicast RNTI, and the two descriptions can be replaced with each other.
  • broadcast-type or multicast-type data packets need to be sent to multiple terminal devices, for ease of description, any one of the multiple terminal devices is used as an example to describe the embodiment of the present application.
  • Network equipment sends broadcast Ethernet packets based on RNTI for broadcast or multicast Ethernet packets
  • Mode A may be applicable to a scenario where the terminal device is in a connected state.
  • FIG. 10 is a schematic interaction diagram of a communication method 600 for Ethernet data according to an embodiment of the present application.
  • the network device sends downlink control information DCI to the terminal device.
  • the DCI is scrambled with a first wireless network temporary identifier (RNTI).
  • the first RNTI is an RNTI for an Ethernet data packet, and the DCI It includes information used to indicate the time-frequency resources carrying the Ethernet data packet.
  • the network device sends the Ethernet data packet to the terminal device.
  • the terminal device receives the Ethernet data packet from the network device based on the time-frequency resources indicated by the DCI.
  • the first RNTI may be an RNTI of a non-unicast type.
  • the first RNTI may be directed to a multicast type Ethernet data packet, may also be directed to a broadcast type Ethernet data packet, or may be directed to another type of Ethernet data packet, which is not limited in the embodiment of the present application.
  • the scheduling information ie, DCI
  • the scheduling information for scheduling unicast type Ethernet data packets is scrambled with a second RNTI, a first RNTI is newly introduced, and the non-unicast type Ethernet is scrambled with the first RNTI.
  • the DCI of the packet is scrambled with the packet.
  • the first RNTI may be used to scramble the DCI that schedules a non-unicast type Ethernet data packet.
  • the terminal device is detecting and receiving the After the DCI, it can be confirmed that the Ethernet data packets scheduled by the DCI will receive the Ethernet data packets on the time-frequency resources indicated by the DCI.
  • the first RNTI is dedicated to receiving a non-unicast type Ethernet data packet, and can be understood as an identifier of a terminal device in the signal information between the terminal device and the network device.
  • This identifier can be pre-configured on the terminal device, it can be agreed by the protocol, or it can be received by the terminal device from the network device.
  • the identifier For the case where the identifier is an agreement, only terminal devices supporting the Ethernet type use the identifier to receive downlink scheduling information (for example, DCI); for the case where the identifier is configured, only the terminal device receiving the identifier receives the identifier for receiving Downlink scheduling information; for a case where the identifier is received by a terminal device from a network device, the terminal device receives the identifier through a dedicated or broadcast message.
  • downlink scheduling information for example, DCI
  • the terminal device receiving the identifier receives the identifier for receiving Downlink scheduling information
  • the terminal device receives the identifier through a dedicated or broadcast message.
  • the first RNTI is an RNTI for an Ethernet data packet of a broadcast type or a multicast type.
  • the broadcast type RNTI for example, RNTI1
  • RNTI2 a multicast-type RNTI
  • the terminal device can receive both the DCI scrambled with RNTI 1 and the DCI scrambled with RNTI 2 and determine the type of the Ethernet data packet based on the scrambled identifier, that is, the broadcast type or the multicast type Ethernet data. package.
  • Other types of Ethernet packets can be transmitted and received in the same way.
  • RNTI there are multiple types of RNTI reserved in the system.
  • a network device sends an Ethernet data packet, it can select a corresponding one from the reserved RNTI based on the type of the Ethernet data packet.
  • the RNTI of the packet type scrambles the DCI.
  • a broadcast type RNTI for example, RNTI1
  • RNTI2 RNTI2
  • RNTI2 RNTI2
  • the content related to the first RNTI is described from the broadcast-type RNTI and the multicast-type RNTI.
  • the first RNTI is a broadcast type RNTI
  • the first RNTI is a broadcast-type RNTI
  • a terminal device in a cell in the broadcast range monitors the DCI scrambled by the first RNTI. After receiving the DCI, it will receive it on the time-frequency resource indicated by the DCI. Ethernet packets.
  • the first RNTI is a broadcast-type RNTI
  • the MAC address in the broadcast-type Ethernet packet is fixed, for example, FF-FF-FF-FF-FF-FF, in this case, it is not necessary to add this broadcast type MAC address to the data packet. Therefore, the embodiment of the present application provides a possible implementation manner:
  • the first RNTI is an RNTI for a broadcast-type Ethernet data packet, and the packet header of the Ethernet data packet does not include a broadcast-type media intervention control MAC address.
  • the DCI includes first information, and the first information is used to indicate that the data packet scheduled by the DCI is a broadcast type Ethernet data packet.
  • the first RNTI is a multicast type RNTI
  • At least one multicast type RNTI can be configured for the terminal devices of at least one group, and the terminal devices of one group correspond to one multicast type RNTI. If the first RNTI is a multicast-type RNTI, a terminal device in a group corresponding to the first RNTI monitors the first RNTI. After receiving the DCI, it will receive Ethernet on the time-frequency resource indicated by the DCI. Network packets.
  • the DCI includes first information, and the first information is used to indicate that the data packet scheduled by the DCI is a multicast type Ethernet data packet.
  • the communication method for Ethernet data in the embodiment of the present application through a scrambled DCI specifically targeted at a broadcast type or a multicast type RNTI, can reduce other than the terminal equipment that needs to receive the broadcast type or the multicast type.
  • the interference of terminal equipment improves the transmission performance of Ethernet data.
  • the Ethernet data packet when the Ethernet data packet is a multicast type Ethernet data packet, if the multicast MAC address corresponds to the RNTI, that is, if the terminal device can determine the multicast address according to the multicast type RNTI
  • the header of the Ethernet data packet may not include the MAC address of the multicast type.
  • an RNTI is set for each multicast group to scramble the DCI where the scheduling information of the data packet of at least one terminal device in each multicast group is located. In this way, the terminal devices in the multicast group can The RNTI corresponding to the multicast group determines the multicast group corresponding to the RNTI so that the MAC address may not be carried in the header of the Ethernet data packet.
  • a public network in order to facilitate the access network device to identify which type of Ethernet data packet is received from the core network device, a public network can be established between the access network device and the core network device.
  • a quality of service (QoS) flow is a Qos flow used to carry broadcast-type or multicast-type Ethernet data packets.
  • QoS quality of service
  • the public Qos flow is a Qos flow used to carry broadcast-type or multicast-type Ethernet data packets.
  • the network device is an Ethernet data packet received from the public Qos stream, it is considered that the received Ethernet data packet needs the network device to send to the terminal device through broadcast or multicast.
  • the time-frequency resource carrying the Ethernet data packet may not be indicated in the DCI
  • the first RNTI is used to scramble the DCI
  • the time-frequency resource carrying the Ethernet data packet is indicated through the SIB.
  • the terminal device The Ethernet data packet is received according to the DCI and SIB.
  • the terminal device may send feedback information to the network device. How to send feedback information is an example and not a limitation.
  • the terminal device may control the physical uplink shared channel (PUSCH) or physical uplink according to a pre-configured sequence.
  • the channel (physical uplink, control channel, PUCCH) and other uplink channels send feedback.
  • the pre-configured order has two meanings:
  • the terminal device will occupy a sending feedback resource and send feedback information after receiving the Ethernet data packet.
  • the feedback resource may be determined in any of the following ways:
  • the terminal device obtains the feedback resource according to the location mapping of the wireless frame where the Ethernet data packet is located; or,
  • the terminal device obtains the feedback resource according to the location mapping of the initial radio frame where the Ethernet data packet is located; or,
  • the terminal device obtains the feedback resource according to the location mapping of the ending radio frame where the Ethernet data packet is located; or,
  • the terminal device is mapped according to the control channel element (control channel element, CCE) position of the DCI used for scheduling the Ethernet data packet.
  • control channel element control channel element, CCE
  • Network equipment sends broadcast type Ethernet packets via SIB
  • FIG. 11 is a schematic interaction diagram of a communication method 700 for Ethernet data according to an embodiment of the present application.
  • the network device sends a paging message, where the paging message includes indication information, and the indication information is used to indicate that the SIB includes the Ethernet data packet.
  • the indication information is used to indicate that the type of the SIB is a SIB type including an Ethernet data packet; or the indication information is used to notify a terminal device that the network device sends an Ethernet data packet in the SIB.
  • the network device In S710, the network device generates a SIB, and the SIB includes an Ethernet data packet.
  • the SIB may also indicate an Ethernet frame format, a virtual network label, and / or a service virtual network label.
  • the network device sends the SIB to the terminal device.
  • the network device may not send the instruction information or send the instruction information in a paging message, and the terminal device may directly receive the SIB message.
  • the communication method for Ethernet data provided in the embodiment of the present application sends a broadcast-type Ethernet data packet through the SIB to efficiently notify the terminal device to receive the Ethernet data packet, thereby improving transmission efficiency.
  • the sending mechanism of the paging message can be effectively used, that is, the terminal device receives the paging message within a period of time to detect whether there is a message for itself, which reduces the design.
  • the complexity can also improve the reliability of data packets received by the terminal device.
  • the MAC addresses in broadcast Ethernet packets are fixed.
  • the FF-FF-FF-FF-FF-FF-FF mentioned above It is not necessary to add this broadcast type MAC address in the data packet. Therefore, the embodiment of the present application provides a possible implementation manner:
  • the header of the Ethernet data packet does not include a broadcast-type media intervention control MAC address.
  • mode B in the same way as A, if the network device is an access network device, a public Qos flow can be established between the access network device and the core network device. If the access network device receives the public Qos flow, , It is considered that the received Ethernet data packet needs to be sent by the network device to the terminal device in a broadcast or multicast manner. In addition, in order for the network device to know whether the terminal device successfully received the Ethernet data packet, the terminal device can send feedback information to the network device. For details on how to send the feedback information, refer to the related description in Mode A. For simplicity, I won't repeat them here.
  • Mode A and Mode B may be used in combination.
  • the network device sends downlink control information DCI to the terminal device.
  • the DCI is scrambled with a first wireless network temporary identifier RNTI.
  • the first RNTI is an RNTI for an Ethernet data packet, and the DCI includes an instruction for carrying the Ethernet data packet.
  • the network device sends a SIB to the terminal device, and the SIB includes the Ethernet data packet;
  • the terminal device receives the SIB from the network device based on the time-frequency resources indicated by the DCI. That is, in this way, Ethernet data packets can be carried through the SIB.
  • the first RNTI reference may be made to the description of the first RNTI in Mode A, and details are not described herein again.
  • the third aspect proposes a scheme of how to report the MAC address.
  • the third aspect may be used in combination with at least one of the first aspect or the second aspect, or may be used alone.
  • the terminal device may send the MAC address in three cases, and the three cases are described separately below.
  • the terminal device reports the MAC address after receiving the request information sent by the network device
  • FIG. 12 is a schematic interaction diagram of a communication method 800 for Ethernet data according to an embodiment of the present application.
  • the network device sends a request message for requesting a media intervention control MAC address associated with the terminal device
  • the terminal device sends a MAC address to the network device. .
  • the MAC address associated with the terminal device may include the MAC address of the terminal device itself, or the MAC addresses of other terminal devices connected to the terminal device by wire or wirelessly.
  • a terminal device associated with the terminal device is an associated terminal.
  • the terminal device needs to report the MAC address associated with the terminal device, because, for example, in a network system shown in FIG. 1, one terminal device may be connected to multiple terminal devices.
  • the terminal device 131 is not only connected to the terminal device. 132 connection, but also with other terminal devices.
  • Terminal device 132 and other terminal devices need terminal device 131 to forward data for it.
  • terminal devices 131 also needs to report the MAC addresses of other terminal devices connected to it to the network device.
  • the network device may be an access network device or a core network device.
  • the access network device may send dedicated RRC signaling to request the terminal device to report the MAC address used by the terminal device; if the network device is a core network device, Then the core network device can send a dedicated NAS signaling requesting the terminal device to report the MAC address used.
  • the request information may be a MAC type identification query request of the terminal device.
  • the network device can send the terminal device with the request information for the MAC address of the terminal device, so that the terminal device can report the MAC address to the network device in time.
  • the network device can learn the MAC address of the terminal device in time, thereby facilitating data transmission.
  • the terminal device sends a non-access stratum NAS message, and the NAS message includes the response information.
  • the MAC address of the terminal device can be reported to the network device (for example, the core network device) through the NAS message.
  • the core network device can report the received MAC The address is sent to the access network device.
  • the NAS message may be a tracking area update (TAU) or a PDU session establishment request.
  • the terminal device may report the MAC address to the core network device through a service request message or a PDN connection establishment request message.
  • the core network device may send the received MAC address to the access network device.
  • the terminal device changes the MAC address to the network device.
  • the network card of an Ethernet device connected to a terminal device through a wire is replaced, the MAC address is generally changed. In this way, the terminal device needs to update the MAC address. Therefore, the replaced MAC address needs to be reported to the network device.
  • the terminal device periodically reports the MAC address associated with the terminal device
  • the period for periodically reporting may be configured by a network device through a timer, or may be configured by a terminal device through a timer.
  • the terminal device can report the MAC address to the network device through dedicated RRC signaling or dedicated NAS signaling.
  • the MAC address is indicated in a location area update message (tracking area update (TAU)).
  • TAU tracking area update
  • the newly added MAC address is indicated in the TAU request message.
  • the fourth aspect describes how the network device locates and searches for the terminal device.
  • the network device sends a paging message to the terminal device, where the paging message carries the MAC address of the terminal device that needs to be paged, and the terminal device can determine whether to receive the MAC address from the received paging message. For its own MAC address or whether it is the MAC address of another terminal device connected to the terminal device, specifically, the terminal device can determine whether the received MAC address matches the MAC address provided or assigned by a higher layer. If they match, then When the MAC address is transferred to a higher layer, the terminal device initiates an RRC connection establishment request or a connection restoration request, or the terminal device notifies other terminal devices to initiate an RRC connection establishment request or a connection restoration request.
  • the second aspect is used in combination with the first aspect.
  • the broadcast type or multicast type Ethernet data packet described in the second aspect may be the third Ethernet data packet in the method 400 in the first aspect, or may be sent in the method 500.
  • the fifth Ethernet packet in the case where the end is a network device.
  • the first aspect describes how to compress and process Ethernet data packets
  • the second aspect explains that if the Ethernet data packet is a broadcast type or multicast type Ethernet data packet, it can be passed through the second aspect.
  • Mode A and Mode B send the Ethernet data packet.
  • the third aspect is used in combination with the first aspect.
  • the terminal device reports the MAC address.
  • the network device is sending an Ethernet data packet (for example, the third Ethernet data packet in method 400).
  • the fifth Ethernet data packet when the sending end of the method 500 is a network device
  • the reported MAC address is carried in the context information corresponding to the Ethernet data packet, and the corresponding context carried in the Ethernet data packet
  • the context identifier of the information; or, the reported MAC address is carried in the Ethernet data packet (for example, the fourth Ethernet data packet in method 400 or the sixth Ethernet data packet when the sending end is a network device in method 500) )in.
  • the third aspect is used in combination with the second aspect.
  • the terminal device reports the MAC address.
  • the network device will report the MAC address when sending broadcast or multicast Ethernet packets. The address is carried in an Ethernet packet.
  • the third aspect is used in combination with the second aspect and the first aspect.
  • the broadcast type or multicast type Ethernet data packet may be the third Ethernet data packet or the fourth Ethernet data packet in the method 400 in the first aspect. It may be the fifth Ethernet data packet or the sixth Ethernet data packet when the sending end is a network device in the method 500.
  • the Ethernet data packet is the third Ethernet data packet in the method 400 or the fifth Ethernet data packet when the sending end of the method 500 is a network device
  • the reported MAC address may be carried in the corresponding Ethernet data packet.
  • the context information and the context identifier of the corresponding context information carried in the Ethernet data packet; in the case where the Ethernet data packet is the fourth Ethernet data packet in method 400 or the sending end of method 500 is a network device, for six Ethernet data packets, the reported MAC address can be carried in the Ethernet data packet.
  • the fourth aspect is used in combination with the first aspect, the second aspect, or the third aspect, and can be used to find a terminal in any scenario of the first aspect, the second aspect, or the third aspect when the network device is in an abnormal situation. device.
  • the communication method for Ethernet data according to the embodiment of the present application is described in detail above with reference to FIG. 1 to FIG. 13.
  • the communication method for Ethernet data according to the embodiment of the application is described in detail below with reference to FIGS. 14 to 15. Device.
  • FIG. 14 shows an apparatus 1400 for Ethernet data according to an embodiment of the present application.
  • the apparatus 1400 may be a terminal device or a chip in the terminal device.
  • the apparatus 1400 may be a network device or a chip in the network device.
  • the device 1400 includes a transceiver unit 1410 and a processing unit 1420.
  • the apparatus 1400 is configured to execute each process and step corresponding to a terminal device in the foregoing method 300.
  • the transceiver unit 1410 is configured to receive compression configuration information from a network device, where the compression configuration information is used to indicate a parameter of a first Ethernet compression capability; and the processing unit 1420 is configured to generate a parameter according to the parameter of the first Ethernet compression capability.
  • a first Ethernet data packet; the transceiver unit 1410 is further configured to send the first Ethernet data packet to the network device.
  • the transceiver unit 1410 is further configured to send compression capability information to the network device, where the compression capability information is used to indicate N types of Ethernet compression capabilities supported by the device, and the N types of Ethernet compression capabilities include In the first Ethernet compression capability, N is an integer greater than or equal to 1.
  • the parameter of the first Ethernet compression capability includes an enable parameter, and the enable parameter is used to instruct the device to use the first Ethernet compression capability.
  • the parameters of the first Ethernet compression capability include: a frame format parameter indicating a first frame format, or an algorithm parameter indicating a compression algorithm of the first frame format, where the first frame format is Frame format of the first Ethernet data packet.
  • the first Ethernet data packet includes a first header
  • the first header includes a first context identifier
  • the first context identifier is used to identify the first context information.
  • the transceiver unit 1410 is further configured to: send a first correspondence between the first context identifier and the first context information to the network device.
  • the transceiver unit 1410 is further configured to send a second Ethernet data packet to the network device, where the second Ethernet data packet includes a second header, and the second header includes the first corresponding packet. relationship.
  • the second header further includes a frame format of the second Ethernet data packet, and a frame format of the second Ethernet data packet is the same as a frame format of the first Ethernet data packet.
  • the transceiver unit 1410 is further configured to send a correspondence between the context identifier and the context information to the network device, where the correspondence includes the first correspondence.
  • the transceiver unit 1410 is further configured to receive first feedback information from the network device, where the first feedback information is used to indicate that the network device successfully receives the first correspondence relationship.
  • the first feedback information includes: the first context identifier.
  • the transceiver unit 1410 is further configured to receive second feedback information from the network device, where the second feedback information is used to instruct the network device to successfully decompress the first Ethernet data packet.
  • the apparatus 1400 is configured to execute each process and step corresponding to the network device in the foregoing method 300.
  • the transceiver unit 1410 is configured to send compression configuration information to a terminal device, where the compression configuration information is used to indicate a parameter of a first Ethernet compression capability, and receive a first Ethernet data packet, where the first Ethernet data packet is based on The parameters of the first Ethernet compression capability are generated; the processing unit 1420 is configured to: decompress the first Ethernet data packet.
  • the transceiver unit 1410 is further configured to receive compression capability information from the terminal device, where the compression capability information is used to indicate N types of Ethernet compression capabilities supported by the terminal device, and the N types of Ethernet compression capabilities Including the first Ethernet compression capability, N is an integer greater than or equal to 1.
  • the parameter of the first Ethernet compression capability includes an enable parameter, and the enable parameter is used to instruct the terminal device to use the first Ethernet compression capability.
  • the parameters of the first Ethernet compression capability include a frame format parameter indicating a first frame format and / or an algorithm parameter indicating a compression algorithm of the first frame format, and the first frame format is the first Frame format of an Ethernet packet.
  • the first Ethernet data packet includes a first header, the first header includes a first context identifier, and the first context identifier is used to identify the first context information; and the processing unit 1420 further And configured to: obtain the first context information according to the first context identifier; and decompress the first Ethernet data packet according to the first context information.
  • the transceiver unit 1410 is further configured to receive a first correspondence between the first context identifier and the first context information from the terminal device.
  • the transceiver unit 1410 is further configured to receive a second Ethernet data packet from the terminal device, the second Ethernet data packet includes a second header, and the second header includes the first corresponding packet. relationship.
  • the second header further includes a frame format of the second Ethernet data packet, and a frame format of the second Ethernet data packet is the same as a frame format of the first Ethernet data packet.
  • the transceiver unit 1410 is further configured to: receive a correspondence between a context identifier and context information from the terminal device, where the correspondence includes the first correspondence.
  • the transceiver unit 1410 is further configured to send first feedback information to the terminal device, where the first feedback information is used to indicate that the apparatus successfully receives the first correspondence relationship.
  • the first feedback information includes: the first context identifier.
  • the transceiver unit 1410 is further configured to send second feedback information to the terminal device, where the second feedback information is used to indicate that the device successfully decompresses the first Ethernet data packet.
  • the apparatus 1400 is configured to execute each process and step corresponding to a terminal device in the foregoing method 400.
  • the transceiver unit 1410 is configured to receive compression configuration information from a network device, where the compression configuration information is used to indicate a parameter of a third Ethernet compression capability, to receive a third Ethernet data packet from the network device, and the third Ethernet The data packet is generated based on the parameter of the third Ethernet compression capability; the processing unit 1420 is configured to: decompress the third Ethernet data packet.
  • the transceiver unit 1410 is further configured to send compression capability information to the network device, where the compression capability information is used to indicate N types of Ethernet compression capabilities supported by the device, and the N types of Ethernet compression capabilities include In the third Ethernet compression capability, N is an integer greater than or equal to 1.
  • the parameter of the third Ethernet compression capability includes an enable parameter, and the enable parameter is used to instruct the device to use the third Ethernet compression capability.
  • the parameters of the third Ethernet compression capability include: a frame format parameter indicating a third frame format, or an algorithm parameter indicating a compression algorithm of a third frame format, the third frame format is A frame format of the third Ethernet data packet.
  • the third Ethernet data packet includes a third header, the third header includes a third context identifier, and the third context identifier is used to identify third context information; and the processing unit 1420 further And configured to: obtain the third context information according to the third context identifier; and decompress the third Ethernet data packet according to the third context information.
  • the transceiver unit 1410 is further configured to: receive a third correspondence relationship between the third context identifier and the third context information from the network device.
  • the transceiver unit 1410 is further configured to receive a fourth Ethernet data packet from the network device, the fourth Ethernet data packet includes a fourth header, and the fourth header includes the third corresponding header. relationship.
  • the fourth header further includes a frame format of the fourth Ethernet data packet, and a frame format of the fourth Ethernet data packet is the same as a frame format of the third Ethernet data packet.
  • the transceiver unit 1410 is further configured to: receive a correspondence between a context identifier and context information from the network device, where the correspondence includes the third correspondence.
  • the transceiver unit 1410 is further configured to send third feedback information to the network device, where the third feedback information is used to indicate that the apparatus successfully receives the third correspondence relationship.
  • the third feedback information includes: the third context identifier.
  • the transceiver unit 1410 is further configured to send fourth feedback information to the network device, where the fourth feedback information is used to indicate that the device successfully decompresses the third Ethernet data packet.
  • the apparatus 1400 is configured to execute each process and step corresponding to a network device in the foregoing method 400.
  • the transceiver unit 1410 is configured to: send the compression configuration information to the terminal device, where the compression configuration information is used to indicate a parameter of the third Ethernet compression capability; and the processing unit 1420 is configured to: A third Ethernet data packet; the transceiver unit 1410 is further configured to send the third Ethernet data packet to the terminal device.
  • the transceiver unit 1410 is further configured to receive compression capability information from the terminal device, where the compression capability information is used to indicate N types of Ethernet compression capabilities supported by the terminal device, and the N types of Ethernet compression capabilities Including the third Ethernet compression capability, N is an integer greater than or equal to 1.
  • the parameter of the third Ethernet compression capability includes an enable parameter, and the enable parameter is used to instruct the terminal device to use the third Ethernet compression capability.
  • the parameter of the third Ethernet compression capability includes a frame format parameter indicating a third frame format and / or an algorithm parameter indicating a compression algorithm of the third frame format, and the third frame format is the first Frame format for three Ethernet packets.
  • the third Ethernet data packet includes a third header
  • the third header includes a third context identifier
  • the third context identifier is used to identify the third context information.
  • the transceiver unit 1410 is further configured to: send a third correspondence relationship between the third context identifier and the third context information to the terminal device.
  • the transceiver unit 1410 is further configured to send a fourth Ethernet data packet to the terminal device, the fourth Ethernet data packet includes a fourth header, and the fourth header includes the third corresponding packet. relationship.
  • the fourth header further includes a frame format of the fourth Ethernet data packet, and a frame format of the fourth Ethernet data packet is the same as a frame format of the third Ethernet data packet.
  • the transceiver unit 1410 is further configured to send a correspondence between the context identifier and the context information to the terminal device, where the correspondence includes the third correspondence.
  • the transceiver unit 1410 is further configured to receive third feedback information from the terminal device, where the third feedback information is used to indicate that the terminal device successfully receives the third correspondence relationship.
  • the third feedback information includes: the third context identifier.
  • the transceiver unit 1410 is further configured to receive fourth feedback information from the terminal device, where the fourth feedback information is used to instruct the terminal device to successfully decompress the third Ethernet data packet.
  • the device 1400 is configured to execute various processes and steps corresponding to the sending end in the foregoing method 500.
  • the processing unit 1420 is configured to generate a fifth Ethernet data packet, where the fifth Ethernet data packet includes a fifth header, the fifth header includes a fifth context identifier, and the fifth context identifier is used to identify a fifth Context information; the transceiver unit 1410 is configured to: send a fifth Ethernet data packet to the receiving end.
  • the transceiver unit 1410 is further configured to send a correspondence between the following identifier and the context information to the receiving end, where the correspondence includes the fifth context identifier and the first context identifier of the fifth context identifier. Five correspondences.
  • the transceiver unit 1410 is further configured to: send a sixth Ethernet data packet to the receiving end, the sixth Ethernet data packet includes a sixth header, and the sixth header includes the fifth context A correspondence relationship with the fifth context information is identified.
  • the sixth packet header further includes indication information used to indicate a type of a frame format of the sixth Ethernet data packet, and a type of the frame format of the sixth Ethernet data packet is the same as the fifth Ethernet data packet.
  • the type of frame format of the network packet is the same.
  • the transceiver unit 1410 is further configured to receive fifth feedback information from the receiving end, where the fifth feedback information is used to indicate that the receiving end successfully receives the corresponding relationship.
  • the fifth feedback information includes: a context identifier in the corresponding relationship.
  • the transceiver unit 1410 is further configured to receive sixth feedback information from the receiving end, where the sixth feedback information is used to indicate that the receiving end successfully decompresses the fifth data packet.
  • the device is a terminal device, and the receiving end is a network device; and the transceiver unit 1410 is further configured to:
  • the transceiver unit 1410 is further configured to send compression capability information to the receiving end, where the compression capability information is used to indicate N types of Ethernet compression capabilities supported by the device, and the N types of Ethernet compression capabilities include In the fifth ether compression capability, N is an integer greater than or equal to 1.
  • the device is a network device, and the receiving end is a terminal device; and the transceiver unit 1410 is further configured to send the compression configuration information to the receiving end, where the compression configuration information is used to indicate a fifth Parameters of ether compression capacity;
  • the transceiver unit 1410 is further configured to receive compression capability information from the receiving end, where the compression capability information is used to indicate N types of Ethernet compression capabilities supported by the receiving end, and the N types of Ethernet compression capabilities Including the fifth ether compression capability, N is an integer greater than or equal to 1.
  • the device 1400 is configured to execute each process and step corresponding to the receiving end in the foregoing method 500.
  • the transceiver unit 1410 is configured to receive a fifth Ethernet data packet, where the fifth Ethernet data packet includes a fifth header, the fifth header includes a fifth context identifier, and the fifth context identifier is used to identify a fifth Context information; the processing unit 1420 is configured to: obtain the fifth context information according to the fifth context identifier; the processing unit 1420 is further configured to: decompress the fifth Ethernet data according to the fifth context information package.
  • the transceiver unit 1410 is further configured to: receive a correspondence between a context identifier and context information, where the correspondence includes a fifth correspondence between the fifth context identifier and the fifth context identifier; and
  • the processing unit 1420 is specifically configured to obtain the fifth context information according to the fifth context identifier and the fifth correspondence relationship.
  • the transceiver unit 1410 is further configured to receive a sixth Ethernet data packet, where the sixth Ethernet data packet includes a sixth header, and the sixth header includes the fifth context identifier and the fifth context.
  • the processing unit 1420 is specifically configured to obtain the fifth context information according to the fifth context identifier and the fifth corresponding relationship.
  • the sixth packet header further includes indication information used to indicate a type of a frame format of the sixth Ethernet data packet, and a type of the frame format of the sixth Ethernet data packet is the same as the fifth Ethernet data packet.
  • the type of frame format of the network packet is the same.
  • the transceiver unit 1410 is further configured to send fifth feedback information, where the fifth feedback information is used to indicate that the device successfully receives the corresponding relationship.
  • the fifth feedback information includes: a context identifier in the corresponding relationship.
  • the transceiver unit 1410 is further configured to send sixth feedback information, where the sixth feedback information is used to indicate that the device successfully decompresses the fifth data packet.
  • the device is a network device, and the sending end is a terminal device; and the transceiver unit 1410 is further configured to:
  • the transceiver unit 1410 is further configured to receive compression capability information from the sending end, where the compression capability information is used to indicate N types of Ethernet compression capabilities supported by the sending end, and the N types of Ethernet compression capabilities Including the fifth ether compression capability, N is an integer greater than or equal to 1.
  • the device is a terminal device, and the transmitting end is a network device; and the transceiver unit 1410 is further configured to receive compression configuration information from the transmitting end, where the compression configuration information is used to indicate a fifth A parameter of the Ethernet compression capability, wherein the fifth Ethernet data packet is generated based on the parameter of the fifth Ethernet compression capability.
  • the transceiver unit 1410 is further configured to receive compression capability information from the sending end, where the compression capability information is used to indicate N types of Ethernet compression capabilities supported by the sending end, and the N types of Ethernet compression capabilities Including the fifth ether compression capability, N is an integer greater than or equal to 1.
  • the apparatus 1400 is configured to execute each process and step corresponding to a terminal device in the foregoing method 600.
  • the transceiver unit 1410 is configured to receive downlink control information DCI from a network device.
  • the DCI is scrambled by using a first wireless network temporary identifier RNTI.
  • the first RNTI is an RNTI for an Ethernet data packet.
  • Information indicating time-frequency resources carrying the Ethernet data packet; the transceiver unit 1410 is further configured to: receive the Ethernet data packet from the network device on the time-frequency resource indicated by the DCI.
  • the transceiver unit 1410 is specifically configured to receive a system information block SIB from the network device on the time-frequency resource indicated by the DCI, where the SIB includes the Ethernet data packet.
  • the first RNTI is an RNTI for a broadcast type or multicast type Ethernet data packet.
  • the DCI includes first information, and the first information is used to indicate that the data packet scheduled by the DCI is a broadcast type Ethernet data packet or a multicast type Ethernet data packet.
  • the packet header of the Ethernet data packet does not include a broadcast type media intervention control MAC address.
  • the transceiver unit 1410 is further configured to send a media intervention control MAC address associated with the device to the network device.
  • the transceiver unit 1410 is specifically configured to send a non-access stratum NAS message to the network device, where the NAS message includes the MAC address.
  • the transceiver unit 1410 is further configured to receive a request message from the network device, where the request message is used to request the MAC address associated with the device.
  • the transceiver unit 1410 is further configured to: when the MAC address associated with the device changes, send the changed MAC address to the network device.
  • the transceiver unit 1410 is further configured to send compression capability information to the network device, where the compression capability information is used to indicate N types of Ethernet compression capabilities supported by the device, where N is an integer greater than or equal to ;
  • the apparatus further includes: The processing unit 1420 is configured to decompress the Ethernet data packet, where the Ethernet data packet is generated based on a parameter of the first Ethernet compression capability.
  • the Ethernet data packet includes a first header, the first header includes a first context identifier, and the first context identifier is used to identify the first context information; and the transceiver unit 1410 is further configured to: Obtaining the first context information by using the first context identifier; and the processing unit 1420 is specifically configured to: decompress the Ethernet data packet according to the first context information.
  • the apparatus 1400 is configured to execute each process and step corresponding to the network device in the foregoing method 600.
  • the transceiver unit 1410 is configured to send downlink control information DCI to a terminal device.
  • the DCI is scrambled by using a first wireless network temporary identifier RNTI.
  • the first RNTI is an RNTI for an Ethernet data packet.
  • Information indicating the time-frequency resource carrying the Ethernet data packet; the transceiver unit 1410 is further configured to send the Ethernet data packet to the terminal device on the time-frequency resource.
  • the transceiver unit 1410 is specifically configured to send a system information block SIB to the terminal device on the time-frequency resource, where the SIB includes the Ethernet data packet.
  • the first RNTI is an RNTI for a broadcast type or a multicast type Ethernet data packet.
  • the DCI includes first information, and the first information is used to indicate that the data packet scheduled by the DCI is a broadcast type Ethernet data packet or a multicast type Ethernet data packet.
  • the apparatus is an access network device, and a public service quality Qos flow is established between the access network device and the core network device; and the transceiver unit 1410 is further configured to: from the public Qos flow Receiving the Ethernet data packet.
  • the transceiver unit 1410 is further configured to receive, from the terminal device, a media intervention control MAC address associated with the terminal device.
  • the transceiver unit 1410 is specifically configured to receive a non-access stratum NAS message from the terminal device, where the NAS message includes the MAC address.
  • the transceiver unit 1410 is further configured to send a request message to the terminal device, where the request message is used to request the MAC address associated with the terminal device.
  • the transceiver unit 1410 is further configured to receive compression capability information from the terminal device, where the compression capability information is used to indicate N types of Ethernet compression capabilities supported by the terminal device, where N is greater than or equal to 1 An integer; sending compression configuration information to the terminal device, where the compression configuration information is used to indicate a parameter of the first Ethernet compression capability, the N types of Ethernet compression capabilities include the first Ethernet compression capability; the device further includes: The processing unit 1420 is configured to generate the Ethernet data packet according to the parameter of the first Ethernet compression capability.
  • the Ethernet data packet includes a first header, the first header includes a first context identifier, and the first context identifier is used to identify the first context information.
  • the apparatus 1400 is configured to execute each process and step corresponding to a terminal device in the foregoing method 700.
  • the transceiver unit 1410 is configured to receive a system information block SIB from a network device, where the SIB includes an Ethernet data packet; and the processing unit 1420 is configured to obtain the Ethernet data packet from the SIB.
  • the transceiver unit 1410 is further configured to receive a paging message from the network device, where the paging message includes indication information, and the indication information is used to indicate that the SIB includes the Ethernet data packet.
  • the transceiver unit 1410 is further configured to receive downlink control information DCI from the network device, the DCI is scrambled by using a first wireless network temporary identifier RNTI, and the first RNTI is for an Ethernet data packet. RNTI, the DCI includes information for indicating a time-frequency resource carrying the Ethernet data packet.
  • the DCI includes first information, and the first information is used to indicate that the data packet scheduled by the DCI is a broadcast type Ethernet data packet or a multicast type Ethernet data packet.
  • the packet header of the Ethernet data packet does not include a broadcast type media intervention control MAC address.
  • the transceiver unit 1410 is further configured to send a media intervention control MAC address associated with the device to the network device.
  • the transceiver unit 1410 is specifically configured to send a non-access stratum NAS message to the network device, where the NAS message includes the MAC address.
  • the transceiver unit 1410 is further configured to receive a request message from the network device, where the request message is used to request the MAC address associated with the device.
  • the transceiver unit 1410 is specifically configured to: when the MAC address associated with the device changes, send the changed MAC address to the network device.
  • the transceiver unit 1410 is further configured to send compression capability information to the network device, where the compression capability information is used to indicate N types of Ethernet compression capabilities supported by the device, where N is an integer greater than or equal to 1.
  • the compression configuration information is used to indicate a parameter of a first Ethernet compression capability, the N types of Ethernet compression capabilities including the first Ethernet compression capability; and the processing unit 1420 It is also used to decompress the Ethernet data packet, wherein the Ethernet data packet is generated based on a parameter of the first Ethernet compression capability.
  • the Ethernet data packet includes a first header, the first header includes a first context identifier, and the first context identifier is used to identify the first context information; and the transceiver unit 1410 is further configured to: Obtaining the first context information by using the first context identifier; and the processing unit 1420 is specifically configured to: decompress the Ethernet data packet according to the first context information.
  • the apparatus 1400 is configured to execute each process and step corresponding to a network device in the foregoing method 700.
  • the processing unit 1420 is configured to generate a system information block SIB, where the SIB includes an Ethernet data packet; and the transceiver unit 1410 is configured to send the SIB.
  • the transceiver unit 1410 is further configured to send a paging message to the terminal device, where the paging message includes indication information, and the indication information is used to indicate that the SIB includes the Ethernet data packet.
  • the transceiver unit 1410 is further configured to send downlink control information DCI to the terminal device, where the DCI is scrambled with a first wireless network temporary identifier RNTI, and the first RNTI is for an Ethernet data packet.
  • RNTI the DCI includes information for indicating a time-frequency resource carrying the Ethernet data packet.
  • the DCI includes first information, and the first information is used to indicate that the data packet scheduled by the DCI is a broadcast type Ethernet data packet or a multicast type Ethernet data packet.
  • the packet header of the Ethernet data packet does not include a broadcast type media intervention control MAC address.
  • the transceiver unit 1410 is further configured to receive, from the terminal device, a media intervention control MAC address associated with the terminal device.
  • the transceiver unit 1410 is specifically configured to receive a non-access stratum NAS message from the terminal device, where the NAS message includes the MAC address.
  • the transceiver unit 1410 is further configured to send a request message to the terminal device, where the request message is used to request the MAC address associated with the terminal device.
  • the transceiver unit 1410 is further configured to receive compression capability information from the terminal device, where the compression capability information is used to indicate N types of Ethernet compression capabilities supported by the terminal device, where N is greater than or equal to 1 Integer
  • the processing unit 1420 is further configured to: : Generating the Ethernet data packet according to a parameter of the first Ethernet compression capability.
  • the Ethernet data packet includes a first header, the first header includes a first context identifier, and the first context identifier is used to identify the first context information.
  • the apparatus 1400 is configured to execute each process and step corresponding to a terminal device in the foregoing method 800.
  • the transceiver unit 1410 is configured to receive a request message from a network device, where the request message is used to request a media intervention control MAC address associated with the device; the transceiver unit 1410 is further configured to: send the MAC to the network device address.
  • the transceiver unit 1410 is specifically configured to send a non-access stratum NAS message, where the NAS message includes the MAC address.
  • the apparatus 1400 is configured to execute each process and step corresponding to the network device in the foregoing method 800.
  • the sending and receiving unit 1410 is configured to send a request message to the terminal device, where the request message is used to request a media intervention control MAC address associated with the terminal device; the sending and receiving unit 1410 is further configured to receive the terminal device from the terminal device. MAC address.
  • the transceiver unit 1410 is specifically configured to receive a non-access stratum NAS message from the terminal device, where the NAS message includes the MAC address.
  • the device 1400 here is embodied in the form of a functional unit.
  • the term "unit” herein may refer to an application-specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a proprietary processor, or a group of processors) for executing one or more software or firmware programs. Processors, etc.) and memory, merge logic, and / or other suitable components that support the functions described.
  • ASIC application-specific integrated circuit
  • processor such as a shared processor, a proprietary processor, or a group of processors
  • processors such as a shared processor, a proprietary processor, or a group of processors
  • memory merge logic, and / or other suitable components that support the functions described.
  • the device 1400 may be specifically a terminal device or a network device (as a sending end or a receiving end respectively) in the foregoing embodiment, and the device 1400 may be used to execute the foregoing method embodiment
  • the processes and / or steps corresponding to the terminal device or the network device are not repeated here in order to avoid repetition.
  • the apparatus 1400 of each of the foregoing solutions has a function of implementing corresponding steps performed by a terminal device or a network device (as a sending end or a receiving end, respectively) in the foregoing method; the functions may be implemented by hardware, or may be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions; for example, the transmitting unit may be replaced by a transmitter, the receiving unit may be replaced by a receiver, and other units, such as a determining unit, may be replaced by a processor and executed separately. Sending and receiving operations and related processing operations in various method embodiments.
  • the device in FIG. 14 may also be a chip or a chip system, for example, a system on chip (SoC).
  • the receiving unit and the transmitting unit may be the transceiver circuit of the chip, which is not limited herein.
  • FIG. 15 shows another apparatus 1500 for Ethernet data provided by an embodiment of the present application.
  • the device 1500 includes a processor 1510, a transceiver 1520, and a memory 1530.
  • the processor 1510, the transceiver 1520, and the memory 1530 communicate with each other through an internal connection path.
  • the memory 1530 is used to store instructions.
  • the processor 1510 is used to execute the instructions stored in the memory 1530 to control the transceiver 1520 to send signals and / Or receive a signal.
  • the apparatus 1500 is configured to execute each process and step corresponding to a terminal device in the foregoing method 300.
  • the transceiver 1520 is configured to receive compression configuration information from a network device, where the compression configuration information is used to indicate a parameter of a first Ethernet compression capability; and the processor 1510 is configured to: according to the parameter of the first Ethernet compression capability Generating a first Ethernet data packet; the transceiver 1520 is further configured to: send the first Ethernet data packet to the network device.
  • the apparatus 1500 is configured to execute each process and step corresponding to the network device in the foregoing method 300.
  • the transceiver 1520 is configured to send compression configuration information to a terminal device, where the compression configuration information is used to indicate a parameter of a first Ethernet compression capability, and receive a first Ethernet data packet, where the first Ethernet data packet is based on The first Ethernet compression capability parameter is generated; the processor 1510 is configured to: decompress the first Ethernet data packet.
  • the apparatus 1500 is configured to execute each process and step corresponding to a terminal device in the foregoing method 400.
  • the transceiver 1520 is configured to receive compression configuration information from a network device, where the compression configuration information is used to indicate a parameter of a third Ethernet compression capability, to receive a third Ethernet data packet from the network device, and the third Ethernet The data packet is generated based on the parameter of the third Ethernet compression capability; the processor 1510 is configured to: decompress the third Ethernet data packet.
  • the apparatus 1500 is configured to execute each process and step corresponding to a network device in the foregoing method 400.
  • the transceiver 1520 is configured to send compression configuration information to a terminal device, where the compression configuration information is used to indicate a parameter of a third Ethernet compression capability; and the processor 1510 is configured to generate, according to the parameter of the third Ethernet compression capability, A third Ethernet data packet; the transceiver 1520 is further configured to: send the third Ethernet data packet to the terminal device.
  • the device 1500 is configured to execute various processes and steps corresponding to the sending end in the foregoing method 500.
  • the processor 1510 is configured to generate a fifth Ethernet data packet, where the fifth Ethernet data packet includes a fifth header, the fifth header includes a fifth context identifier, and the fifth context identifier is used to identify a fifth Context information; the transceiver 1520 is configured to: send a fifth Ethernet data packet to the receiving end.
  • the device 1500 is configured to execute various processes and steps corresponding to the receiving end in the foregoing method 500.
  • the transceiver 1520 is configured to receive a fifth Ethernet data packet, where the fifth Ethernet data packet includes a fifth header, the fifth header includes a fifth context identifier, and the fifth context identifier is used to identify a fifth Context information; the processor 1510 is configured to: obtain the fifth context information according to the fifth context identifier; the processor 1510 is further configured to: decompress the fifth Ethernet data according to the fifth context information package.
  • the apparatus 1500 is configured to execute each process and step corresponding to a terminal device in the foregoing method 600.
  • the transceiver 1520 is configured to receive downlink control information DCI from a network device, the DCI is scrambled by using a first wireless network temporary identifier RNTI, the first RNTI is an RNTI for an Ethernet data packet, and the DCI includes Information indicating the time-frequency resource carrying the Ethernet data packet; the transceiver 1520 is further configured to: receive the Ethernet data packet from the network device on the time-frequency resource indicated by the DCI.
  • the apparatus 1500 is configured to execute each process and step corresponding to the network device in the foregoing method 600.
  • the transceiver 1520 is configured to send downlink control information DCI to a terminal device, where the DCI is scrambled with a first wireless network temporary identifier RNTI, the first RNTI is an RNTI for an Ethernet data packet, and the DCI includes Information indicating time-frequency resources carrying the Ethernet data packet; the transceiver 1520 is further configured to send the Ethernet data packet to the terminal device on the time-frequency resource.
  • the apparatus 1500 is configured to execute each process and step corresponding to a terminal device in the foregoing method 700.
  • the transceiver 1520 is configured to receive a system information block SIB from a network device, where the SIB includes an Ethernet data packet; and the processor 1510 is configured to: obtain the Ethernet data packet from the SIB.
  • the apparatus 1500 is configured to execute each process and step corresponding to a network device in the foregoing method 700.
  • the processor 1510 is configured to generate a system information block SIB, where the SIB includes an Ethernet data packet; and the transceiver 1520 is configured to: send the SIB.
  • the apparatus 1500 is configured to execute each process and step corresponding to a terminal device in the foregoing method 800.
  • the transceiver 1520 is configured to receive a request message from a network device, where the request message is used to request a media intervention control MAC address associated with the device; the transceiver 1520 is further configured to send the MAC to the network device address.
  • the apparatus 1500 is configured to execute each process and step corresponding to the network device in the foregoing method 800.
  • the transceiver 1520 is configured to send a request message to the terminal device, where the request message is used to request a media intervention control MAC address associated with the terminal device; the transceiver 1520 is further configured to receive the terminal device from the terminal device MAC address.
  • the disclosed systems, devices, and methods may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the unit is only a logical function division.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not implemented.
  • 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.
  • 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.
  • 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.
  • 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 disks, mobile hard disks, read-only memories (ROMs), random access memories (RAMs), magnetic disks or compact discs and other media that can store program codes .

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供了一种用于以太网数据的通信方法和装置，本申请实施例提出了一种新的无线网络临时标识RNTI(例如，第一RNTI)，该第一RNTI是针对以太网数据包的RNTI，该方法包括：终端设备从网络设备接收采用该第一RNTI加扰的下行控制信息DCI，在该终端设备在该DCI所指示的时频资源上从该网络设备接收该以太网数据包。这样，通过一个专门针对以太网数据包的RNTI加扰DCI，可以减少对需要接收其他类型的数据的终端设备以外的其他终端设备的干扰，不仅实现了在无线网络中传输以太网数据，也提高了以太网数据的传输性能。

Description

用于以太网数据的通信方法和装置
本申请要求于2018年9月28日提交中国专利局、申请号为201811142736.7、申请名称为“用于以太网数据的通信方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，更具体地，涉及用于以太网数据的通信方法和装置。
背景技术
以太网是一种局域网通信技术，目前的工业场景使用有线的以太网传输数据，这里，可以将基于以太网通信技术传输的数据简称为以太网数据。此外，无线通信的快速发展，为未来工厂对于传输的灵活性、移动性、多样性和改造性提供了无限可能。因此，在工业场景中，也可以通过无线通信实现以太网数据的传输。例如,控制台通过无线网络向机器设备发送指令，机器设备基于接收到的指令执行相应动作以及上报自身的状态信息给服务器
因此，如何在无线网络中进行以太网数据的通信，已成为亟需解决的问题。
发明内容
本申请提供一种用于以太网数据的通信方法和装置，能够进行以太网数据的无线通信。
第一方面，提供了一种用于以太网数据的通信方法，所述方法包括：
终端设备从网络设备接收下行控制信息DCI，所述DCI采用第一无线网络临时标识RNTI加扰，所述第一RNTI是针对以太网数据包的RNTI，所述DCI包括用于指示承载所述以太网数据包的时频资源的信息；
所述终端设备在所述DCI所指示的时频资源上从所述网络设备接收所述以太网数据包。
因此，本申请实施例的用于处理以太网数据的方法，通过一个专门针对以太网数据的RNTI加扰DCI，可以减少对需要接收其他类型的数据的终端设备以外的其他终端设备的干扰，不仅实现了在无线网络中传输以太网数据，也提高了以太网数据的传输性能。
在一种可能的实现方式中，所述终端设备从所述网络设备接收所述以太网数据包，包括：
所述终端设备在所述DCI所指示的时频资源上从所述网络设备接收系统信息块SIB，所述SIB包括所述以太网数据包。
在一种可能的实现方式中，所述第一RNTI是针对广播类型或组播类型的以太数据包的RNTI。
在一种可能的实现方式中，所述DCI包括第一信息，所述第一信息用于指示所述DCI调度的数据包为广播类型的以太网数据包或组播类型的以太网数据包。
在一种可能的实现方式中，当所述以太数据包是广播类型的以太网数据包时，所述以太网数据包的包头中不包括广播类型的媒体介入控制MAC地址。
这样，通过广播类型的以太网数据包中删除广播类型的MAC地址，可以有效地节省资源。
在一种可能的实现方式中，所述方法还包括：
所述终端设备向所述网络设备发送与所述终端设备关联的媒体介入控制MAC地址。
在一种可能的实现方式中，所述终端设备向所述网络设备发送所述MAC地址，包括：
所述终端设备向所述网络设备发送非接入层NAS消息，所述NAS消息包括所述MAC地址。
在一种可能的实现方式中，所述方法还包括：
所述终端设备从所述网络设备接收请求消息，所述请求消息用于请求与所述终端设备关联的所述MAC地址。
在一种可能的实现方式中，所述终端设备向所述网络设备发送所述MAC地址，包括：
当与所述终端设备关联的MAC地址发生变化，则所述终端设备向所述网络设备发送变化后的所述MAC地址。
在一种可能的实现方式中，所述方法还包括：
所述终端设备向所述网络设备发送压缩能力信息，所述压缩能力信息用于指示所述终端设备支持的N种以太压缩能力，N为大于或等于1的整数；
所述终端设备从所述网络设备接收压缩配置信息，所述压缩配置信息用于指示第一以太压缩能力的参数，所述N种以太压缩能力包括所述第一以太压缩能力；以及，
所述终端设备解压缩所述以太网数据包，其中，所述以太网数据包是基于所述第一以太网压缩能力的参数生成的。
在一种可能的实现方式中，所述以太网数据包包括第一包头，所述第一包头包括第一上下文标识，所述第一上下文标识用于标识第一上下文信息；所述方法还包括：
所述终端设备根据所述第一上下文标识，获取所述第一上下文信息；以及，
所述终端设备解压缩所述以太网数据包，包括：
所述终端设备根据所述第一上下文信息，解压缩所述以太网数据包。
第二方面，提供了一种用于以太网数据的通信方法，其特征在于，所述方法包括：
网络设备向终端设备发送下行控制信息DCI，所述DCI采用第一无线网络临时标识RNTI加扰，所述第一RNTI是针对以太网数据包的RNTI，所述DCI包括用于指示承载所述以太网数据包的时频资源的信息；
所述网络设备在所述时频资源上向所述终端设备发送所述以太网数据包。
在一种可能的实现方式中，所述网络设备向所述终端设备发送所述以太网数据包，包括：
所述网络设备在所述时频资源上向所述终端设备发送系统信息块SIB，所述SIB包括所述以太网数据包。
在一种可能的实现方式中，所述第一RNTI是针对广播类型或组播类型的以太网数据 包的RNTI。
在一种可能的实现方式中，所述DCI包括第一信息，所述第一信息用于指示所述DCI调度的数据包为广播类型的以太网数据包或组播类型的以太网数据包。
在一种可能的实现方式中，所述网络设备为接入网设备，所述接入网设备与核心网设备之间建立有公共服务质量Qos流；以及，
所述方法还包括：
所述网络设备从所述公共Qos流接收所述以太网数据包。
在一种可能的实现方式中，所述方法还包括：
所述网络设备从所述终端设备接收与所述终端设备关联的媒体介入控制MAC地址。
在一种可能的实现方式中，所述网络设备从所述终端设备接收所述MAC地址，包括：
所述网络设备从所述终端设备接收非接入层NAS消息，所述NAS消息包括所述MAC地址。
在一种可能的实现方式中，所述方法还包括：
所述网络设备向所述终端设备发送请求消息，所述请求消息用于请求与所述终端设备关联的所述MAC地址。
在一种可能的实现方式中，所述方法还包括：
所述网络设备从所述终端设备接收压缩能力信息，所述压缩能力信息用于指示所述终端设备支持的N种以太压缩能力，N为大于或等于1的整数；
所述网络设备向所述终端设备发送压缩配置信息，所述压缩配置信息用于指示第一以太压缩能力的参数，所述N种以太压缩能力包括所述第一以太压缩能力；
所述网络设备根据所述第一以太压缩能力的参数，生成所述以太网数据包。
在一种可能的实现方式中，所述以太网数据包包括第一包头，所述第一包头包括第一上下文标识，所述第一上下文标识用于标识第一上下文信息。
第三方面，提供了一种用于以太网数据的通信方法，其特征在于，所述方法包括：
终端设备从网络设备接收系统信息块SIB，所述SIB包括以太网数据包；
所述终端设备从所述SIB中获取所述以太数据包。
因此，本申请实施例提供的用于处理以太网数据包的方法，通过SIB发送广播类型的以太网数据包，可以高效地通知终端设备接收以太网数据包，提高传输效率。
在一种可能的实现方式中，所述方法还包括：
所述终端设备从所述网络设备接收寻呼消息，所述寻呼消息包括指示信息，所述指示信息用于指示所述SIB包括所述以太网数据包。
这样，通过在寻呼消息中添加指示信息，可以有效地利用寻呼消息的发送机制，即，终端设备在周期性时间段内接收寻呼消息检测是否有针对自己的消息，降低了设计复杂度，也能提高终端设备接收数据包的可靠性。
在一种可能的实现方式中，所述方法包括：
所述终端设备从所述网络设备接收下行控制信息DCI，所述DCI采用第一无线网络临时标识RNTI加扰，所述第一RNTI是针对以太网数据包的RNTI，所述DCI包括用于指示承载所述以太网数据包的时频资源的信息。
在一种可能的实现方式中，所述DCI包括第一信息，
所述第一信息用于指示所述DCI调度的数据包为广播类型的以太网数据包或组播类型的以太网数据包。
在一种可能的实现方式中，其特征在于，当所述以太数据包是广播类型的以太网数据包时，所述以太网数据包的包头中不包括广播类型的媒体介入控制MAC地址。
这样，通过广播类型的以太网数据包中删除广播类型的MAC地址，可以有效地节省资源。
在一种可能的实现方式中，所述方法还包括：
所述终端设备向所述网络设备发送与所述终端设备关联的媒体介入控制MAC地址。
在一种可能的实现方式中，所述终端设备向所述网络设备发送所述MAC地址，包括：
所述终端设备向所述网络设备发送非接入层NAS消息，所述NAS消息包括所述MAC地址。
在一种可能的实现方式中，所述方法还包括：
所述终端设备从所述网络设备接收请求消息，所述请求消息用于请求与所述终端设备关联的所述MAC地址。
在一种可能的实现方式中，所述终端设备向所述网络设备发送所述MAC地址，包括：
当与所述终端设备关联的MAC地址发生变化，则所述终端设备向所述网络设备发送变化后的所述MAC地址。
在一种可能的实现方式中，所述方法还包括：
所述终端设备向所述网络设备发送压缩能力信息，所述压缩能力信息用于指示所述终端设备支持的N种以太压缩能力，N为大于或等于1的整数；
所述终端设备从所述网络设备接收压缩配置信息，所述压缩配置信息用于指示第一以太压缩能力的参数，所述N种以太压缩能力包括所述第一以太压缩能力；以及，
所述终端设备解压缩所述以太网数据包，其中，所述以太网数据包是基于所述第一以太网压缩能力的参数生成的。
在一种可能的实现方式中，所述以太网数据包包括第一包头，所述第一包头包括第一上下文标识，所述第一上下文标识用于标识第一上下文信息；所述方法还包括：
所述终端设备根据所述第一上下文标识，获取所述第一上下文信息；以及，
所述终端设备解压缩所述以太网数据包，包括：
所述终端设备根据所述第一上下文信息，解压缩所述以太网数据包。
第四方面，提供了一种用于以太网数据的通信方法，其特征在于，所述方法包括：
网络设备生成系统信息块SIB，所述SIB包括以太网数据包；
网络设备发送所述SIB。
在一种可能的实现方式中，所述方法还包括：
所述网络设备向所述终端设备发送寻呼消息，所述寻呼消息包括指示信息，所述指示信息用于指示所述SIB包括所述以太网数据包。
在一种可能的实现方式中，所述方法包括：
所述网络设备向所述终端设备发送下行控制信息DCI，所述DCI采用第一无线网络临时标识RNTI加扰，所述第一RNTI是针对以太网数据包的RNTI，所述DCI包括用于指示承载所述以太网数据包的时频资源的信息。
在一种可能的实现方式中，所述DCI包括第一信息，所述第一信息用于指示所述DCI调度的数据包为广播类型的以太网数据包或组播类型的以太网数据包。
在一种可能的实现方式中，当所述以太数据包是广播类型的以太网数据包时，所述以太网数据包的包头中不包括广播类型的媒体介入控制MAC地址。
在一种可能的实现方式中，所述方法还包括：
所述网络设备从所述终端设备接收所述终端设备关联的媒体介入控制MAC地址。
在一种可能的实现方式中，所述网络设备从所述终端设备接收所述终端设备关联的媒体介入控制MAC地址，包括：
所述网络设备从所述终端设备接收非接入层NAS消息，所述NAS消息包括所述MAC地址。
在一种可能的实现方式中，所述方法还包括：
所述网络设备向所述终端设备发送请求消息，所述请求消息用于请求与所述终端设备关联的所述MAC地址。
在一种可能的实现方式中，所述方法还包括：
所述网络设备从所述终端设备接收压缩能力信息，所述压缩能力信息用于指示所述终端设备支持的N种以太压缩能力，N为大于或等于1的整数；
所述网络设备向所述终端设备发送压缩配置信息，所述压缩配置信息用于指示第一以太压缩能力的参数，所述N种以太压缩能力包括所述第一以太压缩能力；
所述网络设备根据所述第一以太压缩能力的参数，生成所述以太网数据包。
在一种可能的实现方式中，所述以太网数据包包括第一包头，所述第一包头包括第一上下文标识，所述第一上下文标识用于标识第一上下文信息。
第五方面，提供了一种用于以太网数据的通信方法，其特征在于，所述方法包括：
终端设备从网络设备接收请求消息，所述请求消息用于请求与所述终端设备关联的媒体介入控制MAC地址；
所述终端设备向所述网络设备发送所述MAC地址。
在一种可能的实现方式中，所述终端设备向所述网络设备发送所述MAC地址，包括：
所述终端设备发送非接入层NAS消息，所述NAS消息包括所述MAC地址。
因此，本申请实施例的用于处理以太网数据的方法，网络设备通过向终端设备发送用于请求终端设备的MAC地址的请求信息，能够使得终端设备及时向网络设备上报MAC地址，这样，网络设备能够及时获知终端设备的MAC地址，从而便于数据的传输。
第六方面，提供了一种用于以太网数据的通信方法，其特征在于，所述方法包括：
网络设备向终端设备发送请求消息，所述请求消息用于请求与所述终端设备关联的媒体介入控制MAC地址；
所述网络设备从所述终端设备接收所述MAC地址。
在一种可能的实现方式中，所述网络设备从所述终端设备接收所述MAC地址，包括：
所述网络设备从所述终端设备接收非接入层NAS消息，所述NAS消息包括所述MAC地址。
第七方面，提供了一种用于以太网数据的通信方法，其特征在于，所述方法包括：
在与终端设备关联的媒体介入控制MAC地址发生变化的情况下，所述终端设备向网 络设备发送变化后的MAC地址。
在一种可能的实现方式中，所述终端设备向网络设备发送变化后的MAC地址，包括：
所述终端设备发送非接入层NAS消息，所述NAS消息包括所述变化后的MAC地址。
第八方面，提供了一种用于以太网数据的通信方法，其特征在于，所述方法包括：
接入网设备接收核心网设备从公共服务质量Qos流发送的以太网数据包；
所述接入网设备通过广播方式或组播方式发送所述以太网数据包。
第九方面，提供了一种用于以太网数据的装置，用于执行上述任一方面中任意可能的实现方式中的方法。具体地，该装置包括用于执行上述任一方面中的任一种可能的实现方式中的方法的单元。
第十方面，提供了另一种用于以太网数据的装置，该装置包括：收发器、存储器和处理器。其中，该收发器、该存储器和该处理器通过内部连接通路互相通信，该存储器用于存储指令，该处理器用于执行该存储器存储的指令，以控制接收器接收信号，并控制发送器发送信号，并且当该处理器执行该存储器存储的指令时，使得该处理器执行上述任一方面中的任一种可能的实现方式中的方法。
第十一方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序代码，当所述计算机程序代码被计算机运行时，使得所述计算机执行上述各方面中的方法。
第十二方面，提供了一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行上述各方面中的方法的指令。
第十三方面，提供了一种芯片，包括处理器，用于从存储器中调用并运行所述存储器中存储的指令，使得安装有所述芯片的通信设备执行上述各方面中的方法。
第十四方面，提供另一种芯片，包括：输入接口、输出接口、处理器和存储器，所述输入接口、输出接口、所述处理器以及所述存储器之间通过内部连接通路相连，所述处理器用于执行所述存储器中的代码，当所述代码被执行时，所述处理器用于执行上述各方面中的方法。
附图说明
图1是适用于本申请实施例的移动通信系统的架构示意图。
图2是适用于本申请实施例的移动通信系统的另一架构示意图。
图3是本申请实施例的EtherCAT帧的示意性图。
图4是本申请实施例的用于以太网数据的通信方法的示意性交互图。
图5是本申请实施例的第一以太网数据包的帧格式的示意性图。
图6是本申请实施例的第二以太网数据包的帧格式的示意性图。
图7是本申请实施例的用于携带反馈信息的数据包的帧格式的示意图。
图8是本申请实施例的另一用于以太网数据的通信方法的示意性交互图。
图9是本申请实施例的另一用于以太网数据的通信方法的示意性交互图。
图10是本申请实施例的另一用于以太网数据的通信方法的示意性交互图。
图11是本申请实施例的另一用于以太网数据的通信方法的示意性交互图。
图12是本申请实施例的另一用于以太网数据的通信方法的示意性交互图。
图13是本申请实施例的以太压缩状态的转化图。
图14是本申请实施例提供的用于以太网数据的装置。
图15是本申请实施例提供的另一用于以太网数据的装置。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通信(global system for mobile communications，GSM)系统、码分多址(code division multiple access，CDMA)系统、宽带码分多址(wideband code division multiple access，WCDMA)系统、通用分组无线业务(general packet radio service，GPRS)、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、通用移动通信系统(universal mobile telecommunication system，UMTS)、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)通信系统、未来的第五代(5th generation，5G)系统或新无线(new radio，NR)等。
本申请实施例中的网络设备可以是用于与终端设备通信的设备。该网络设备可以是全球移动通信(global system for mobile communications，GSM)系统或码分多址(code division multiple access，CDMA)中的基站(base transceiver station，BTS)，也可以是宽带码分多址(wideband code division multiple access，WCDMA)系统中的基站(NodeB，NB)，还可以是LTE系统中的演进型基站(evolved NodeB，eNB或eNodeB)，还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器；或者，该网络设备可以为中继站、接入点、车载设备、可穿戴设备以及未来5G网络中的网络设备或者未来演进的PLMN网络中的网络设备等；或者，该网络设备还可以是核心网设备，其中，核心网设备可以是控制面和用户面(control plane and users plane，CU)网元，也可以是CU分离场景中的控制面功能网元CU-CP，例如，会话管理功能实体(session management function，SMF)或接入管理功能(access and mobility management function，AMF)网元或用户面功能(user plane function，UPF)网元等。
本申请实施例中的终端设备可以指用户设备、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置，也可以是机器人、操作臂等，本申请实施例对此并不限定。
在本申请实施例中，终端设备或网络设备包括硬件层、运行在硬件层之上的操作系统层，以及运行在操作系统层上的应用层。该硬件层包括中央处理器(central processing unit，CPU)、内存管理单元(memory management unit，MMU)和内存(也称为主存)等硬件。该操作系统可以是任意一种或多种通过进程(process)实现业务处理的计算机操作系统，例如，Linux操作系统、Unix操作系统、Android操作系统、iOS操作系统或windows操作系统等。该应用层包含浏览器、通讯录、文字处理软件、即时通信软件等应用。并且，本申请实施例并未对本申请实施例提供的方法的执行主体的具体结构特别限定，只要能够通过运行记录有本申请实施例的提供的方法的代码的程序，以根据本申请实施例提供的方法进行通信即可，例如，本申请实施例提供的方法的执行主体可以是终端设备或网络设备，或者，是终端设备或网络设备中能够调用程序并执行程序的功能模块。
另外，本申请的各个方面或特征可以实现成方法、装置或使用标准编程和/或工程技 术的制品。本申请中使用的术语“制品”涵盖可从任何计算机可读器件、载体或介质访问的计算机程序。例如，计算机可读介质可以包括，但不限于:磁存储器件(例如，硬盘、软盘或磁带等)，光盘(例如，压缩盘(compact disc，CD)、数字通用盘(digital versatile disc，DVD)等)，智能卡和闪存器件(例如，可擦写可编程只读存储器(erasable programmable read-only memory，EPROM)、卡、棒或钥匙驱动器等)。另外，本文描述的各种存储介质可代表用于存储信息的一个或多个设备和/或其它机器可读介质。术语“机器可读介质”可包括但不限于，无线信道和能够存储、包含和/或承载指令和/或数据的各种其它介质。
图1是适用于本申请实施例的移动通信系统的架构示意图。如图1所示，图1是环状组网的移动通信系统，该移动通信系统包括控制设备110、接入网设备120和至少一个终端设备(如图1中的终端设备131至终端设备134)。终端设备131和终端设备134通过无线方式与接入网设备120连接。终端设备132和终端设备133通过终端设备131和终端设备134与接入网设备120连接，对于需要在接入网设备120和终端设备132或终端设备133之间传输数据的场景中，可以将终端设备131或终端设备134理解为中转设备，例如，若接入网设备需要发送下行数据至终端设备132，下行数据的传输路径可以为接入网设备120—终端设备131—终端设备132，终端设备131即可以理解为中转设备，或者，下行数据的传输路径也可以为接入网设备120—终端设备134—终端设备133—终端设备132，终端设备134和终端设备133可以理解为中转设备。接入网设备120通过无线或有线方式与控制设备110连接，其中，控制设备110与接入网设备120可以是独立的不同的物理设备，也可以是将控制设备110的功能与接入网设备120的逻辑功能集成在同一个物理设备上，还可以是一个物理设备上集成了部分控制设备110的功能和部分的接入网设备120的功能。终端设备可以是固定位置的，也可以是可移动的。图1只是示意图，该通信系统中还可以包括其它网络设备，如还可以包括无线中继设备和无线回传设备，在图1中未画出。本申请的实施例对该移动通信系统中包括的控制设备、接入网设备和终端设备的数量不做限定。
图2是适用于本申请实施例的移动通信系统的另一架构示意图。如图2所示，图2是星型组网的移动通信系统，该移动通信系统包括控制设备210、接入网设备220和至少一个终端设备(如图2中的终端设备231至终端设备234)。接入网设备220通过无线方式与任一个终端设备连接，接入网设备220通过无线或有线方式与控制设备210连接。其中，控制设备210与接入网设备220可以是独立的不同的物理设备，也可以是将控制设备210的功能与接入网设备220的逻辑功能集成在同一个物理设备上，还可以是一个物理设备上集成了部分控制设备210的功能和部分的接入网设备220的功能。终端设备可以是固定位置的，也可以是可移动的。图2只是示意图，该通信系统中还可以包括其它网络设备，如还可以包括无线中继设备和无线回传设备，在图2中未画出。本申请的实施例对该移动通信系统中包括的控制设备、接入网设备和终端设备的数量不做限定。
需要说明的是，本申请实施例中的“至少一个”表示“一个或多个”，两种描述可以替换。
如背景技术所述，本申请实施例提供的技术方案的目的在于如何在无线网络中传输以太网数据。基于此，本申请实施例主要从以下4个方面阐述了在无线网络中传输以太网数据的方法：
第一方面，如何压缩处理以太网数据；
第二方面，如何传输广播类型或组播类型的以太网数据；
第三方面，终端设备如何上报目的媒体介入控制(media access control，MAC)地址；
第四方面，网络设备如何定位寻找终端设备。
应理解，上述4个方面中每个方面的实施例不仅可以单独使用，任意2个或3个或4个方面的实施例都可以结合使用，本申请实施例不做任何限定。
以下，为了便于描述，首先，对上述每个方面的实施例进行详细说明。其次，针对上述2个或3和或4个方面相结合的实施例做一详细说明。
下面，结合图3至图7，对第一方面的实施例进行详细说明。
首先，为了便于理解，以EtherCAT帧为例，对以太网帧格式做一简单介绍。
图3所示为EtherCAT帧的示意性图。如图3所示，在EtherCAT帧的帧格式中，包括以太网帧头区域、EtherCAT头区域、EtherCAT数据区域和帧校验序列(Frame Check Sequence，FCS)区域。以太网帧头区域包括目的地址、源地址、帧类型，其中，目的地址是接收方的MAC地址，源地址是发送方的MAC地址，MAC地址也叫物理地址，帧类型用于标识数据字段中包含的高层协议。EtherCAT头区域包括EtherCAT数据长度、保留位和类型。EtherCAT数据区域包括2个字节的数据头和44～1498字节的数据区，数据区由一个或多个EtherCAT子报文组成，每个子报文对应独立的设备和从站存储区。FCS区域用于校验传输过程中帧的完整性。
表1描述了以太网帧头区域中各个字段的定义，表2描述了EtherCAT头区域中各个字段的定义，表3描述了EtherCAT数据区域每个子报文中各个字段的定义。
表1
名称 含义
目的地址 接收方MAC地址
源地址 发送方MAC地址
帧类型 0x88A4
表2
名称 含义
EtherCAT数据长度 EtherCAT数据区长度，即，所有子报文长度的总和
类型 1：表示与从站通信；其余保留
表3
名称 含义
命令 寻址方式和读写方式
索引 帧编码
地址区 从站地址
长度 报文数据区长度
R 保留位
M 后续报文标志
状态位 中断到来标志
数据区 子报文数据结构，用户定义
WKC 工作计数器
在普通的以太网业务的点到点的传输过程中，对于使用相同帧格式封装的多个数据包，多个数据包中会存在大量重复传输的内容，即，意味着这些大量重复传出的内容在多次传输过程中是不会发生变化的。例如，图3所示的EtherCAT帧中的目的地址、源地址、帧类型以及EtherCAT头区域的字段等都是重复传输的内容。此外，数据长度可以根据根据数据包的负荷部分(payload)的信息推导得出，实际上在传输过程中也可以不需要传输。此外，在每种格式的以太网帧的开始处都有64比特(8字节)的前导字符。其中，前7个字节称为前同步码(Preamble)，内容是16进制数0xAA，最后1字节为帧起始标志符0xAB，它标识着以太网帧的开始。前导字符的作用是使接收端进行同步并做好接收数据帧的准备。在不定长的数据字段后是4个字节的帧校验序列(frame check sequence，FCS)，这个是在以太网内传输所需要的内容，在无线系统传输过程不需要携带。
因此，在本申请实施例中，以终端设备和网络设备之间的传输为例，作为示例而非限定，可以将以下至少一项内容称为上下文信息或静态信息：
在终端设备和网络设备之间多次传输的数据包中不会发生变化的内容；或，能够根据数据包的负荷部分(payload)的信息推导得出的其他字段信息。
自然地，本申请实施例所说的压缩以太网数据指的是在数据包中去掉上下文信息，或者说，压缩以太网数据指的是减少以太网数据包中除数据区域以外的其他字段的信息，以实现压缩以太数据的目的。
应理解，本申请实施例的以太网数据包指的是承载在以太类型的会话(ethertype session)中的数据包，同理，以太网数据也指的是承载在以太类型的会话(ethertype session)中的数据。
上述以EtherCAT帧格式为例，对以太网帧格式做了简单介绍，下面，基于各种不同帧格式，对本申请实施例的上下文信息进行说明。
帧格式1：Ethernet 802.3 raw类型的帧格式
表4所示为Ethernet 802.3 raw类型的帧格式中的各个字段。作为示例而非限定，上下文信息可以包括目的MAC地址、源MAC地址和类型字段。其中，总长度就是数据部分的长度，可以从数据部分长度中推导得出，在传输过程不需要携带。
表4
Figure PCTCN2019108019-appb-000001
帧格式2：Ethernet 802.3 SAP类型的帧格式
表5
Figure PCTCN2019108019-appb-000002
表5所示为Ethernet 802.3 SAP类型的帧格式中的各个字段。在Ethernet 802.3 SAP类型的帧格式中，将Ethernet 802.3 raw帧中2个字节的0xFFFF变为各1个字节的DSAP和SSAP，同时增加了1个字节的"控制"字段，构成了802.2逻辑链路控制(Logical Link Control，LLC)的首部。LLC提供了无连接(LLC类型1)和面向连接(LLC类型2)的网络服务。其中，LLC1是应用于以太网中，而LLC2应用在IBM网络环境system network architecture，SNA)网络环境中。新增的802.2 LLC首部包括两个服务访问点：源服务访问点(source service accessing point，SSAP)和目标服务访问点(destination service access point，DSAP)。它们用于标识以太网帧所携带的上层数据类型，例如，16进制数0x06代表IP协议数据，16进制数0xE0代表Novell类型协议数据，16进制数0xF0代表IBM NetBIOS类型协议数据等。1个字节的"控制"字段，则基本不使用(一般被设为0x03，指明采用无连接服务的802.2无编号数据格式)。
在Ethernet 802.3 SAP类型的帧格式中，作为示例而非限定，上下文信息可以包括目的MAC地址、源MAC地址、DSAP、SSAP字段和控制字段。其中，总长度可以从数据部分长度中推导得出，同样不需要携带。
帧格式3：Ethernet 802.3 SNAP类型的帧格式
表6
Figure PCTCN2019108019-appb-000003
表6所示为Ethernet 802.3 SNAP类型的帧格式中的各个字段。其中，Ethernet 802.3 SNAP类型的帧格式和Ethernet 802.3 SAP类型的帧格式的主要区别在于：
第一，2个字节的DSAP和SSAP字段内容被固定下来，其值为16进制数0xAA。
第二，1个字节的"控制"字段内容被固定下来，其值为16进制数0x03。
第三，增加了SNAP字段，由下面两项组成：
新增了3个字节的组织唯一标识符(organizationally unique identifier，OUI ID)字段，其值通常等于MAC地址的前3字节，即网络适配器厂商代码；
2个字节的"类型"字段用来标识以太网帧所携带的上层数据类型。
在Ethernet 802.3 SNAP类型的帧格式中，作为示例而非限定，上下文信息可以包括目的MAC地址、源MAC地址、DSAP、SSAP字段、控制字段、OUI ID字段和类型字段。
帧格式4：Ethernet II类型的帧格式
表7
6字节 6字节 2字节 46-1500字节 4字节
目标MAC地址 源MAC地址 类型 数据 FCS
表7所示为Ethernet II类型的帧格式中的各个字段。在Ethernet II类型的帧格式中，最小长度为64字节(6+6+2+46+4)，最大长度为1518字节(6+6+2+1500+4)。其中前12字节分别标识出发送数据包的源节点MAC地址和接收数据包的目标节点MAC地址。接下来的2个字节标识出以太网数据包所携带的上层数据类型，如16进制数0x0800代表IP协议数据，16进制数0x809B代表AppleTalk协议数据，16进制数0x8138代表Novell类型协议数据等。
在Ethernet II类型的帧格式中，作为示例而非限定，上下文信息可以包括目的MAC地址、源MAC地址和类型字段。
帧格式5：ethernet类型的帧格式
参考图3，对于基本的EtherCAT帧，上下文信息可以包括目的MAC地址、源MAC地址、类型字段和EtherCAT头区域的类型字段。其中，EtherCAT头区域的长度字段是所有子报文的长度，可以从报文字段的总长度中推导得出。
对于基本的EtherCAT帧且带虚拟局域网(virtual local area network，VLAN)标签的帧格式，作为示例而非限定，上下文信息可以包括目的MAC地址、源MAC地址、类型字段、VLAN标签和EtherCAT头区域的类型字段，或，上下文信息可以包括目的MAC地址、源MAC地址、类型字段。可以理解，根据实现优化，发送端可以将VLAN标签直接删除，不必作为上下文信息中的一部分进行存储或发送给接收端。
对于有用户数据包协议(user datagram protocol，UDP)或IP的EtherCAT帧，作为示例而非限定，上下文信息可以包括目的MAC地址、源MAC地址、类型字段和EetherCAT头区域的类型字段。
帧格式6：802.1Q类型的帧格式
表8
Figure PCTCN2019108019-appb-000004
表8所示为802.1Q类型的帧格式中的各个字段。作为示例而非限定，上下文信息可以包括目的MAC地址、源MAC地址、VLAN-1字段和类型字段，或，上下文信息可以包括目的MAC地址、源MAC地址和字段类型。
帧格式7：802.1Q-in-Q类型的帧格式
表9
Figure PCTCN2019108019-appb-000005
表9所示为802.1Q-in-Q类型的帧格式中的各个字段。作为示例而非限定，上下文信息可以包括目的MAC地址、源MAC地址、VLAN-1字段、VLAN-2字段和类型字段，或者，上下文信息可以包括目的MAC地址、源MAC地址和类型字段。
帧格式8：802.3类型的帧格式
表10
6字节 6字节 2字节 46-1498字节 4字节
目标MAC地址 源MAC地址 长度/类型 数据 FCS
表10所示为802.3类型的帧格式中的各个字段。作为示例而非限定，上下文信息可以包括目的MAC地址、源MAC地址、长度/类型字段。其中，长度字段的值范围0x0000-0x05DC，是可变的。若是长度字段则属于可推导的信息，不用在传输过程中携带。而对于该字段的其他值有特殊的含义，表征一种帧的类型，作为静态信息，可以作为上下文信息，不用在传输过程中携带。
上述对各种不同帧格式的上下文信息做了说明，应理解，上述列举的8种帧格式以及对应的上下文信息仅是示意性说明，不应对本申请实施例构成限定，任何帧格式以及对应的上下文信息都在本申请实施例的保护范围内。
图4是本申请实施例的用于以太网数据的通信方法300的示意性交互图。方法300是从上行传输的角度对如何压缩处理以太网数据的过程做了说明。
在该实施例中，终端设备通过向网络设备上报自身的以太压缩能力，该网络设备基于该终端设备的以太压缩能力为该终端设备配置一种或多种以太压缩能力，并且，该终端设备基于该网络设备配置的以太压缩能力对以太网数据压缩，向该网络设备发送压缩后的数据包。
下面，对方法300的各个步骤进行说明。
在S310中，终端设备向网络设备发送压缩能力信息，该压缩能力信息用于指示该终端设备支持的N种以太压缩能力，N为大于或等于1的整数。
这里，以太压缩能力表示的是终端设备压缩以太网数据的能力，具体说，以太压缩能力表示终端设备是否可以对以太网数据压缩，并且，若可以压缩以太网数据，可以压缩哪些类型的以太网帧格式。
在一种可能的实现方式中，若终端设备目前仅支持一种以太压缩能力，则该压缩能力信息可以包括用于指示该终端设备支持的压缩能力为以太压缩能力的信息，实际上，由于终端设备仅支持一种以太压缩能力，虽然该压缩能力信息中未明确指示以太压缩能力是哪些类型的，但是，对于网络设备来说，在接收到该压缩能力信息后，可以确知该终端设备应该是仅支持一种以太压缩能力，至于支持哪种以太压缩能力，网络设备可以知道也可以不用知道，并不会影响网络设备的其他行为。
在另一种可能的实现方式中，该压缩能力信息可以包括用于指示该终端设备支持的N种以太网帧格式的信息。
也就是说，一种以太压缩能力可以对应一种以太网帧格式，终端设备上报N种以太压 缩能力表示该终端设备可以对N种以太网帧格式进行压缩。
具体实现中，可以通过用于标识以太网帧格式的帧格式标识来指示以太网帧格式。
例如：
1表示802.3协议中的以太网帧格式。802.3协议中的以太网帧格式可以包括Ethernet 802.3 raw、Ethernet 802.3 SAP或Ethernet 802.3 SNAP等；
2表示802.1Q的以太网帧格式；
3表示802.1ad(或，802.1Q-In-Q)或vlan stacking的以太网帧格式；
4表示PROFINET的以太网帧格式；
5表示EtherCAT的以太网帧格式；
6表示Profisafe的以太网帧格式。
在S320中，该网络设备向该终端设备发送压缩配置信息，该压缩配置信息用于指示第一以太压缩能力的参数，该N种以太压缩能力包括该第一以太压缩能力。
这里，该压缩配置信息可以理解为网络设备为终端设备开启以太压缩能力的信息，终端设备在接收到该压缩配置信息后，确知能够压缩以太网数据。
由于压缩数据会比较浪费时延，因此，在该步骤中，网络设备可以基于系统对数据的性能要求，为终端设备配置以太压缩能力。例如，若系统对数据的时延要求不高，则可以通过该压缩配置信息使得终端设备开启以太压缩能力，进一步地，可以指示该终端设备可以开启几种以太压缩能力；若系统对数据的时延要求较高，则可以通过该压缩配置信息使得终端设备禁止开启以太压缩能力。
关于网络设备对该以太压缩能力的配置，网络设备可针对设备粒度、承载粒度、逻辑信道粒度或Qos流粒度进行以太压缩能力的配置。
例如，压缩配置信息是针对终端设备的所有承载的信息。即，终端设备的所有承载都使用该压缩配置信息配置的以太压缩能力。
再例如，压缩配置信息是针对终端设备的一个承载的信息。即，终端设备的每个承载的以太压缩能力都是独立配置的，一个压缩配置信息对应一个承载。
再例如，压缩配置信息是针对终端设备的所有承载中的部分承载的信息。即，终端设备的部分承载的以太压缩能力是相同的，一个压缩配置信息对应部分承载。
再例如，压缩配置信息是针对终端设备的一个逻辑信道的信息。即，每个逻辑信道的以太压缩能力都是独立配置的。
再例如，压缩配置信息是针对终端设备的一个服务质量(quality of service，Qos)流的信息。即，每个Qos流的以太压缩能力都是独立配置的。
应理解，该压缩配置信息不仅用于指示该第一以太压缩能力的参数，若该网络设备配置该终端设备可以使用多种以太压缩能力压缩数据，该压缩配置信息也可以用于指示该多个以太压缩能力中除该第一以太压缩能力以外的其他以太压缩能力的参数，其他以太压缩能力的参数与该第一以太压缩能力的参数类似，为了简洁，本申请实施例以该第一以太压缩能力的参数为例做以太压缩能力的参数做一说明。
在一种可能的实现方式中，该压缩配置信息还可以包括指示终端设备只针对以太网帧中携带的上层数据类型为非IP协议类型的以太帧数据包进行压缩。终端设备在上报时也可选指示该能力。
在一种可能的实现方式中，该压缩配置信息还可包括指示终端设备只针对以太网帧中携带的上层数据类型为IP协议类型的以太帧数据包进行压缩。终端设备在上报时也可选指示该能力。
在一种可能的实现方式中，若终端设备接收到以太压缩配置信息，还接收到的头压缩(robust header compression，ROHC)压缩配置信息。可选地，若终端设备同时不支持ROHC压缩和以太压缩，那么优选做IP头压缩。可选地，终端设备也可以上报是否支持同时做ROHC和以太头压缩的能力。网络设备可根据终端的能力指示终端是否同时使能ROHC和以太头压缩功能。
在一种可能的实现方式中，该第一以太压缩能力的参数包括使能参数，该使能参数用于指示该终端设备使用该第一以太压缩能力。
其中，该第一以太压缩能力可以是该终端设备唯一支持的一种以太压缩能力(此种情况下，N＝1)，也可以是该终端设备支持的多种以太压缩能力中的一种(此种情况下，N大于1)。
具体而言，若该终端设备仅支持一种以太压缩能力，该使能参数可以是布尔型指示信息，第一取值表示终端设备可以使用第一以太压缩能力，第二取值表示终端设备不能使用第一以太压缩能力；若该第一以太压缩能力是该终端设备支持的多种以太压缩能力中的一种，并且，该使能参数可以指示该终端设备可以使用或不能使用所有的以太压缩能力，该使能参数也可以是布尔型指示信息，第一取值表示终端设备可以使用第一以太压缩能力，第二取值表示终端设备不能使用第一以太压缩能力。
应理解，虽然本申请实施例仅描述了终端设备可以使用以太压缩能力的方案，但是，并不影响该使能参数实际存在的另一个指示含义，即，指示终端设备不可以使用以太压缩能力。此外，使能参数也可以指示终端设备关闭或释放或去配置以太压缩能力，例如，终端设备开启以太压缩能力之后，网络设备指示该终端设备关闭以太压缩能力。
若终端设备支持的多种以太压缩能力中，并且，网络设备配置该终端设备可以使用其中部分以太压缩能力，则该使能参数可以表示该终端设备可以压缩以太网数据，至于具体使用哪些以太压缩能力可能还需要其他参数指示。
因此，在一种可能的实现方式中，该第一以太压缩能力的参数包括用于指示第一帧格式的帧格式参数，该第一帧格式为第一以太网数据包的帧格式。
这样，终端设备可以基于该帧格式参数确知可以对基于该第一帧格式生成的以太网数据进行压缩。
当然，该第一以太网压缩能力的参数可以不包括使能参数，终端设备和网络设备可以协商，压缩配置信息中的帧格式参数即表示终端设备可以压缩的帧格式，这样，终端设备可以仅通过帧格式参数确定可以对基于该第一帧格式生成的以太网数据进行压缩。
为了使得该终端设备确知需要对该第一帧格式中的哪些字段可以压缩，本申请实施例还提供了一种可能的实现方式：该第一以太压缩能力的参数还包括用于指示该第一帧格式的压缩算法的算法参数。
具体而言，每种帧格式都对应至少一种压缩算法，多种帧格式也可以对应同一种压缩算法。以该第一帧格式为例，压缩算法用于指示如何对该第一帧格式压缩，或者说，压缩算法可以指示该第一帧格式中的哪些字段可以被压缩，或者说，压缩算法指示将该第一帧 格式中的哪些字段的内容作为上下文信息。
在标准协议中，每种压缩算法可以对应一种压缩协议，压缩协议中具体描述了压缩算法的规范信息，例如，压缩格式定义等。
一种可能的指示压缩算法的配置方式，终端设备接收的配置信息中指示该第一帧格式中的哪些字段的内容可以去掉后直接发送。例如，在上行传输中，将以太数据包头的源地址字段信息删除进行发送。
需要说明的是，第一以太压缩能力的参数可以包括帧格式参数、压缩协议参数或算法参数中的至少一个。对于该第一以太压缩能力的参数包括两个参数中的任一个的情况，每种帧格式采用哪种压缩算法可以是协议规定好的：若该第一以太压缩能力的参数包括上述帧格式参数，终端设备确知使用该第一帧格式压缩以太数据，可以直接基于协议规定获取该第一帧格式参数对应的压缩算法；若该第一以太压缩能力的参数包括算法参数，终端设备取确知算法参数，可以基于协议规定获取该算法参数对应的第一帧格式；若该第一以太压缩能力的参数包括压缩协议参数，终端设备取确知压缩协议参数，可以基于协议规定获取该帧格式对应的压缩算法。
在S330中，该终端设备根据该第一以太压缩能力的参数，生成第一以太网数据包。
也就是说，终端设备使用该第一以太压缩能力的参数，压缩以太网数据，即，去掉以太网数据的上下文信息(或者，静态信息)，从而生成压缩后的第一以太网数据包。
需要说明的是，第一以太网数据包可以是PDCP层数据包，也可以是其他协议层压缩的以太网数据包，本申请实施例对此不做任何限定。例如，该第一以太网数据包也可以是终端设备的应用层(或者叫高层，upper layer)、服务数据适用协议(service data adaptation protocol，SDAP)、无线链路控制(radio link control，RLC)或MAC层的数据包。
在S340中，该终端设备向该网络设备发送该第一以太网数据包。
在S350中，该网络设备解压缩该第一以太网数据包。
为了与其他设备交互，网络设备需要对该第一以太网数据包继续封装，因此，网络设备需要将该第一以太网数据包恢复为未压缩前的数据包，换句话说，需要将终端设备去掉的上下文信息添加至该第一以太网数据包中，恢复该第一以太网数据包的头部区域，从而完成针对该第一以太网数据包的解压缩。
因此，本申请实施例提供的用于以太网数据的通信方法，终端设备通过向网络设备上报自身的以太压缩能力，网络设备基于该终端设备的以太压缩能力为该终端设备配置一种或多种以太压缩能力，并且，该终端设备基于该网络设备配置的以太压缩能力对以太网数据压缩，向网络设备发送压缩后的数据包，不仅提出了网络设备启动终端设备使用以太压缩能力的方式，也能够使得终端设备和网络设备在无线网络中传输压缩的以太网数据，可以有效地减少资源的浪费。
作为示例而非限定，本申请实施例可以不需要步骤S310，即，网络设备不需要基于从终端设备接收到的压缩能力信息配置为终端设备配置以太压缩能力，可以直接为终端设备配置以太压缩能力。例如，对于终端设备仅支持一种以太压缩能力的情况，网络设备可以通过终端设备发送的未压缩的以太网数据包获知该终端设备仅支持的一种以太压缩能力，可以不需要该终端设备上报自己支持的以太压缩能力，网络设备可以基于系统对数据的性能要求向该终端设备发送压缩配置信息指示该终端设备唯一支持的以太压缩能力。
在本申请实施例中，网络设备可以是接入网设备或核心网设备。其中，本申请实施例所说的终端设备从网络设备(例如，网络设备A)接收信息，可以是终端设备与该网络设备A直接交互，接收信息，这种情况，可以认为信息是该网络设备A生成的，也可以是网络设备A从其他网络设备(例如，记为网络设备B1)获取到的信息，进而网络设备A将信息转发或透传给该终端设备，这种情况，可以认为信息是网络设备B1或网络设备C1生成的，其中，网络设备B1从网络设备C1中接收信息。同理，本申请实施例所说的网络设备(例如，网络设备A)从终端设备接收信息，可以是终端设备与该网络设备A直接交互，该网络设备A直接从该终端设备接收信息，也可以是该终端设备将信息发送给其他网络设备(例如，网络设备B1)，网络设备B1将信息直接发送给网络设备A或通过其他网络设备(例如，网络设备C1)发送给网络设备A。
下面，以网络设备分别为接入网设备和核心网设备，作为示例而非限定，对压缩配置信息以及压缩能力信息的传输途径做一说明。
1、该网络设备为接入网设备。
A、接入网设备生成该压缩配置信息
压缩配置信息的传输途径：接入网设备→终端设备。
B、接入网设备从其他设备获取压缩配置信息
压缩配置信息的一种可能的传输途径：AMF网元→UPF网元→接入网设备→终端设备，这种情况下，压缩配置信息可以是AMF网元生成的，可以理解，接入网设备从AMF网元或UPF网元接收压缩配置信息，UPF网元将AMF网元生成的压缩配置信息转发或透传给接入网设备。压缩配置信息的另一种可能的传输途径：SMF网元→UPF网元→接入网设备→终端设备，这种情况下，压缩配置信息可以是SMF网元生成的，可以理解，接入网设备从SMF网元或UPF网元接收压缩配置信息，UPF网元将SMF网元生成的压缩配置信息转发或透传给接入网设备。压缩配置信息的另一种可能的传输途径：UPF网元→接入网设备→终端设备，这种情况下，压缩配置信息可以是UPF网元生成的，可以理解，接入网设备从UPF网元接收压缩配置信息。
在网络设备为接入网设备的情况下，压缩能力信息的一种可能的传输途径：终端设备→接入网设备；若生成压缩配置信息的设备是核心网设备，接入网设备可以将该压缩能力信息发送给核心网设备。
2、该网络设备为核心网设备
由于核心网设备较多，以UPF网元作为举例，其他核心网设备的情况与之类似，为了简洁，不再赘述。终端设备从网络设备接收信息，网络设备从终端设备接收信息，可以理解为UPF网元通过核心网设备与终端设备通信以传输信息，
A、UPF网元生成该压缩配置信息
压缩配置信息的一种可能的传输途径：UPF网元→接入网设备→终端设备。
B、UPF网元从其他设备获取该压缩配置信息
压缩配置信息的一种可能的传输途径：AMF网元→UPF网元→接入网设备→终端设备；压缩配置信息的另一种可能的传输途径：SMF网元→UPF网元→接入网设备→终端设备。
在网络设备为UPF网元的情况下，压缩能力信息的一种可能的传输途径：终端设备 →接入网设备→UPF网元；压缩能力信息的另一种可能的传输途径：终端设备→接入网设备-AMF网元-SMF网元-UPF网元。
在上述压缩配置信息的各种传输途径中，任意两个设备之间可以通过不同信令传输压缩配置信息。例如，AMF网元可通过非接入层(non-access-stratum,NAS)信令向UPF网元发送所述压缩配置信息，其中，NAS信令可以是注册响应消息、协议数据单元(protocol data unit，PDU)会话建立。再例如，AMF网元也可以通过NAS信令通过接入网设备向终端设备发送压缩配置信息。再例如，接入设备通过RRC信令或PDCP控制信令向终端设备发送压缩配置信息。再例如，UPF网元可以通过以太网数据包中的压缩信令通过其他设备向终端设备发送压缩配置信息。
基于上文可知，该第一以太网数据包中不包括上下文信息(为了便于区分和理解，记为第一上下文信息)，但是，为了能够使得网络设备获取该第一上下文信息以便于该网络设备解压缩该第一以太网数据包，本申请实施例提供了一种可能的实现方式：
该第一以太网数据包包括第一包头，该第一包头包括第一上下文标识，该第一上下文标识用于标识该第一上下文信息。以及，
该方法还包括：
该网络设备根据该第一上下文标识，获取该第一上下文信息；以及，
该网络设备解压缩该第一以太网数据包，包括：
该网络设备根据该第一上下文信息，解压缩该第一以太网数据包。
也就是说，该网络设备从该第一以太网数据包的第一包头中获得该第一上下文标识，基于该第一上下文标识获取该第一上下文标识对应的上下文信息(即，第一上下文信息)，从而，基于该第一上下文信息解压缩该第一以太网数据包，其中，该第一上下文信息可以是上文所列举以及未列举到的不同帧格式的上下文信息。该第一上下文标识位于该第一包头的一个字段(为了便于区分与理解，记为字段1)中，即，字段1用于携带该第一上下文标识。
作为示例而非限定，该第一包头还可以包括其他字段，每个字段携带对应的内容。
作为示例而非限定，该第一包头还包括以下至少一种字段。
1、用于指示该第一太网数据包是否被压缩的字段(为了便于区分与理解，记为字段2)，其中，字段2指示该第一以太网数据包被压缩。
2、用于指示该第一以太网数据包的帧格式的压缩配置标识的字段(为了便于区分与理解，记为字段3)。
3、用于指示循环冗余校验(cyclic redundancy check,CRC)的字段(为了便于区分与理解，记为字段4)。
4、用于指示该包头是否包含有上述字段1、字段2、字段3和字段4的一个或多个的字段(为了便于区分与理解，记为字段5)。这样，终端设备可以根据字段5确定该第一包头包括哪些字段，即，确定该第一包头的格式，从而，根据确定的该第一包头的格式读取各个字段的内容。
作为示例而非限定，图5所示为本申请实施例的第一以太网数据包的帧格式的示意性图。如图5所示，该第一以太网数据包包括数据区域和包头(即，第一包头)区域，该第一包头区域至少包括4个字段，即，字段1、字段2、字段3和字段4，字段1携带第一 上下文标识，字段2携带用于指示该第一以太网数据包被压缩的信息，字段3携带压缩配置标识，字段4携带CRC。
因此，本申请实施例通过在以太网数据包的包头中添加用于标识上下文信息的上下文标识，进一步使得网络设备通过上下文标识获取对应的上下文信息，可以有效地保证网络设备成功解压缩以太网数据包。
如上所述，网络设备可以基于第一上下文标识获取该第一上下文标识对应的上下文信息，具体而言，该网络设备可以基于该第一上下文标识，从该第一上下文标识和该第一上下文信息之间的第一对应关系中获取该第一上下文信息。其中，针对该网络设备获取该第一对应关系的方式，本申请实施例提供了各种可能的实现方式，下面，对该网络设备获取该第一对应关系的具体方式进行说明。
方式1
在该方式1中，网络设备从终端设备获取该第一对应关系。也就是说，该终端设备会生成该第一对应关系，并且，将该第一对应关系发送给该网络设备。
其中，该终端设备发送该第一对应关系的时间顺序，可以在生成该第一以太网数据包之前，也可以在生成该第一以太网数据包之后，只要在该网络设备解压缩该第一以太网数据包之前发送给该网络设备即可。
在一种可能的实现方式中，该终端设备向该网络设备发送上下文标识和上下文信息之间的对应关系，该对应关系包括该第一对应关系。其中，该对应关系表示至少一个上下文标识和至少一个上下文信息的对应关系，每个上下文标识对应一个上下文信息。
下面，以该第一对应关系为例，对终端设备发送对应关系的方式进行说明。
在一种可能的实现方式中，终端设备可以通过各种形式的信令将该第一对应关系发送给该网络设备，例如，无线资源控制(radio resource control，RRC)信令、非接入层(non-access-stratum,NAS)信令或以太头压缩的应用层的信令。
在该方式中，该对应关系中除该第一对应关系中的其他对应关系也可以通过该信令携带，或者，该其他对应关系可以通过其他信令携带，本申请实施例不限于此。
在实际的工业场景中，一个网络设备可能对应多个终端设备，这就意味着，一个目的MAC地址可以对应多个源MAC地址，一般情况下，目的MAC地址和源MAC地址都属于上下文信息中的内容，那么，针对同一个帧格式，即使压缩的帧格式的字段相同，但是，源MAC地址和目的MAC地址也是不完全相同的。例如，一个网络设备对应两个终端设备(终端设备A和终端设备B)，对于同一个帧格式，会有两个上下文信息，一个上下文信息包括网络设备和终端设备A的MAC地址，另一个上下文信息包括网络设备和终端设备B的MAC地址。此外，为上下文信息配置上下文标识时，对于所有的上下文信息，可以为一个上下文信息配置一个上下文标识，任意两个上下文标识都不同，但是，这样做的话，会占用较多的比特数。为了减少比特数，可以生成一个帧格式下的上下文标识。例如，若帧格式1对应两个上下文标识，帧格式2对应两个上下文标识，则帧格式1中的两个上下文标识可以是0和1，帧格式2中两个上下文标识也可以是0和1。
因此，为了节省上下文标识占用的比特数，可以生成针对每个帧格式的多个上下文信息，以该第一对应关系为例，在一种可能的实现方式中，该终端设备向该网络设备发送用于指示对应于该第一对应关系的帧格式(即，第一帧格式)的信息。这样，网络设备可以 确知该第一对应关系是针对该第一帧格式的对应关系，存储上述节省比特数的上下文标识。
其中，该第一帧格式和该第一对应关系可以承载于同一个信息，也可以承载于不同信息中，本申请实施例对此不做限定。
从节省信令的角度考虑，终端设备也可以在发送未压缩的以太网数据包时，在该未压缩的以太网数据包的包头中携带一个对应关系，该对应关系表示该未压缩的以太网数据包的帧格式的上下文信息和对应的上下文标识，这样，网络设备可以从该未压缩的以太网数据包中获取该对应关系并存储，这样，若后续终端设备发送一个帧格式和该未压缩的以太网数据包的帧格式相同的压缩后的以太网数据包，网络设备可以直接基于提前存储的对应关系获取压缩后的以太网数据包的上下文信息，进而成功解压缩以太网数据包。
因此，针对该第一对应关系，在另一种可能的实现方式中，该终端设备向该网络设备发送第二以太网数据包，该第二以太网数据包包括第二包头，该第二包头包括该第一对应关系。
在该方式中，该对应关系中除该第一对应关系中的其他对应关系也可以通过未压缩的以太网数据包携带。
同理，为了节省上下文标识占用的比特数，在一种可能的实现方式中，该第二包头还包括该第二以太网数据包的帧格式，该第二以太网数据包的帧格式与该第一以太网数据包的帧格式(即，第一帧格式)相同。
作为示例而非限定，图6所示为本申请实施例的第二以太网数据包的帧格式的示意性图。如图6所示，该第二以太网数据包的帧格式是未压缩的数据包的帧格式，该第二以太网数据包包括数据区域和包头(即，第二包头)区域，该第二包头区域至少包括字段1和字段5，其中，字段1携带该第一上下文标识，字段5携带该第一上下文信息。可选地，该第二包括还可以包括字段2、字段3或字段5中的至少一个，其中，字段2携带用于指示该第二以太网数据包未被压缩的信息，字段3携带用于指示该第二以太网数据包的帧格式的压缩配置标识，字段4携带CRC。
在该方式1中，需要网络设备和终端设备共同维护上下文标识和上下文信息之间的对应关系，考虑到终端设备的缓存能力，为了避免终端设备生成的对应关系超出该终端设备的缓存能力，本申请实施例还提供了一种可能的实现方式：
该网络设备向该终端设备发送第一指示信息，该第一指示信息用于指示所述终端设备生成上下文信息的最大个数。
方式2
网络设备基于该第一上下文标识，从预存的至少一个上下文信息和至少一个上下文标识之间的对应关系中获取该第一对应关系，其中，每个上下文信息对应一个上下文标识。
在该方式2中，预存的对应关系可以是系统或协议规定的，也可以是网络设备提前生成的。可以这么理解，系统或协议可以为不同的能够压缩的帧格式配置M个上下文信息，或者，网络设备可以基于不同的能够压缩的帧格式生成M个上下文信息，并且，为了便于查询和标识，为每个上下文信息配置一个对应的上下文标识。
以上，对本申请实施例的对应关系做了详细说明，下面，对本申请实施例涉及的针对相关信息的反馈做一说明。
在本申请实施例中，针对该网络设备是否成功接收该第一对应关系和是否成功解压缩该第一以太网数据包都设置了相关反馈模式。
在一种可能的实现方式中，该方法还包括：
该终端设备接收反馈模式信息，该反馈模式信息包括以下任一种：正确应答(acknowledgement，ACK)反馈模式、否定应答(negative acknowledgment，NACK)反馈模式或无反馈模式。
以网络设备对该第一对应关系的接收情况为例，对上述3种反馈模式做一说明。
ACK反馈模式表示：若网络设备成功接收该第一对应关系，则该网络设备向该终端设备发送反馈信息，相反地，若网络设备未成功接收该第一对应关系，则该网络设备不发送反馈信息，该终端设备在预设时长内未接收到该反馈信息，则认为该网络设备未成功接收该第一对应关系。
NACK反馈模式表示：若网络设备未成功接收该第一对应关系，则该网络设备向该终端设备发送反馈信息，相反地，若网络设备成功接收该第一对应关系，则该网络设备不发送反馈信息，该终端设备在预设时长内未接收到该反馈信息，则认为该网络设备成功接收该第一对应关系。
无反馈模式表示：该终端设备在发送该第一对应关系后，不关注该网络设备是否成功接收该第一对应关系，不需要接收该网络设备发送的反馈信息。
同理，以网络设备对该第一以太网数据包的解压缩情况为例，对上述3种反馈模式做一说明。
ACK反馈模式表示：若网络设备成功解压缩该第一以太网数据包，则该网络设备向该终端设备发送反馈信息，相反地，若网络设备未成功解压缩该第一以太网数据包，则该网络设备不发送反馈信息，该终端设备在预设时长内未接收到该反馈信息，则认为该网络设备未成功解压缩该第一以太网数据包。
NACK反馈模式表示：若网络设备未成功解压缩该第一以太网数据包，则该网络设备向该终端设备发送反馈信息，相反地，若网络设备成功解压缩该第一以太网数据包，则该网络设备不发送反馈信息，该终端设备在预设时长内未接收到该反馈信息，则认为该网络设备成功解压缩该第一以太网数据包。
无反馈模式表示：该终端设备在发送该第一以太网数据包后，不关注该网络设备是否成功解压缩该第一以太网数据包，不需要接收该网络设备发送的反馈信息。
对于无反馈模式，可选地，终端设备可以从网络设备的配置信息中接收关于无反馈模式的其他参数，例如，N和M。其中，N表示发送端(例如，终端设备)发送非压缩数据包启动压缩模式的次数，M表示发送端(例如，终端设备)启动压缩模式后可以发送压缩数据包的时长，在定时器未超时时使用压缩模式发送，在定时器超时后复位压缩上文信息。
下面，以ACK反馈模式为例，分别从网络设备对该第一对应关系的接收情况和该网络设备对该第一以太网数据的解压缩情况，对该网络设备发送反馈信息的过程做一说明。
网络设备针对该第一对应关系的接收情况
在一种可能的实现方式中，所述方法还包括：
该网络设备向该终端设备发送第一反馈信息，该第一反馈信息用于指示该网络设备成 功接收该第一对应关系。
作为示例而非限定，该第一反馈信息可以包括以下至少一种内容：该第一上下文标识或ACK信息。
在一种可能的实现方式中，若该第一对应关系携带在第二以太网数据包的第二包头中，则该第一反馈信息中还可以包括该第二以太网数据包的序列。这种方式，也能指示该网络设备成功接收该第一对应关系。
在本申请实施例中，可以独立设计一个用于携带反馈信息的数据包，对于该第一反馈信息来说，将该第一反馈信息携带在网络设备发送的数据包的负载域。
图7所示为本申请实施例的用于携带反馈信息的数据包的帧格式的示意图。如图7所示，该数据包包括包头和负载区域，其中，包头可以至少包括用于指示该数据包是数据类型的数据包还是控制信息的数据包的字段，即，D/C，其中，D表示数据，C表示控制信息，包括类型字段，例如，该类型字段可以是用于指示以太压缩的反馈信息的字段，R表示预留字段；负载区域是携带反馈信息(例如，第一反馈信息)的区域。
网络设备针对该第一以太网数据包的解压缩情况
在一种可能的实现方式中，所述方法还包括：
该网络设备向该终端设备发送第二反馈信息，该第二反馈信息用于指示该网络设备成功解压缩该第一以太网数据包。
作为示例而非限定，该第二反馈信息可以包括以下至少一种内容：该第一以太网数据包的序列或ACK信息。
在本申请实施例中，可以独立设计一个用于携带反馈信息的数据包，对于该第二反馈信息来说，将该第二反馈信息携带在网络设备发送的数据包的负载域。其中，对于该用于携带反馈信息的数据包的帧格式可以参考图7的描述，为了简洁，此处不再赘述。
在本申请实施例中，在一种可能的实现方式中，终端设备可以向网络设备发送用于指示复位压缩上下文的指示信息。指示信息用于指示网络设备删除该网络设备中存储的上下文信息，也可以理解为双方要重新协商压缩上下文信息。
需要说明的是，本申请实施例的步骤可以在一个功能实体上实现，也可以在多个实体上实现，其中，实体(entity)是指逻辑实体，以逻辑实例的形式实现，具体通过软件实现该实体的功能。假设，本申请实施例可以包括PDCP实体以及压缩/解压缩实体，一种可能的实现方式中，S310和/或S320可以在PDCP实体上实现，S330和/或S350可以在压缩/解压缩实体上实现，PDCP实体在执行S310和/或S320之后，开启压缩/解压缩实体，生成以太网数据包，并将以太网数据包发送给网络设备的压缩/解压缩实体，使网络设备执行解压缩功能。在另一种可能的实现方式中，本申请实施例可以都在PDCP实体上实现。在另一种可能的实现方式中，本申请实施例都在压缩/解压缩实体实现。
以上，从上行传输的角度对本申请实施例压缩处理以太网数据的过程做了说明。下面，从下行传输的角度对本申请实施例压缩处理以太网数据的过程继续做说明。在以下实施例中为了区分与以上实施例中的以太压缩能力的参数，以太数据包等，以第三和第四加以区分。第一、第二、第三和第四等并非用于限制其顺序，且从下行来看，这里的第三和第四可以替换为第一和第二。
图8是本申请实施例的用于以太网数据的通信方法400的示意性交互图。
在该实施例中，终端设备通过向网络设备上报自身的以太压缩能力，网络设备基于终端设备的以太压缩能力为该终端设备配置一种或多种以太压缩能力，并且，该网络设备基于配置的以太压缩能力对以太网数据压缩，向终端设备发送压缩后的数据包。
下面，对方法400的各个步骤进行说明。
在S410中，终端设备向网络设备发送压缩能力信息，所述压缩能力信息用于指示所述终端设备支持的N种以太压缩能力，N为大于或等于1的整数。
其中，针对S410的描述可以参考方法300中针对S310的描述，为了简洁，不再赘述。
在S420中，该网络设备向该终端设备发送接收压缩配置信息，该压缩配置信息用于指示第三以太压缩能力的参数，该N种以太压缩能力包括该第三以太压缩能力。
这里，可以理解为网络设备为终端设备开启以太压缩能力的信息，该压缩配置信息的作用与上行传输中该压缩配置信息的具体作用有一点区别，即，该终端设备在接收到该压缩配置信息后，开启以太压缩能力，确知该网络设备后续会发送压缩的以太网数据包，以及会使用哪些以太压缩能力压缩以太网数据包，以便于能够对网络设备发送的压缩的以太网数据进行解压缩。
这里需要强调的是，该终端设备开启以太压缩能力，表示该终端设备可以对接收到的压缩的以太网数据进行解压缩。实际处理中，也可能会为压缩或解压缩功能配置功能实体，基于该压缩配置信息，可以直接将接收到的以太网数据包基于解压缩功能实体完成。
下面，对该第三以太压缩能力的参数进行简单说明。
在一种可能的实现方式中，该第三以太压缩能力的参数包括使能参数，该使能参数用于指示该终端设备使用该第三以太压缩能力。
其中，关于使能参数的描述可以参考方法300中S320中关于使能参数的描述。
在一种可能的实现方式中，该第三以太压缩能力的参数包括用于指示第三帧格式的帧格式参数，该第三帧格式为第三以太网数据包的帧格式。
这样，终端设备可以基于该帧格式参数确知网络设备可以对基于该第三帧格式生成的以太网数据进行压缩。
当然，该第三以太网压缩能力的参数可以不包括使能参数，终端设备和网络设备可以协商，压缩配置信息中的帧格式参数即表示网络设备可以压缩的帧格式，这样，终端设备可以仅通过帧格式参数确定可以对基于该第三帧格式生成的以太网数据进行解压缩。
在一种可能的实现方式中：该第三以太压缩能力的参数还包括用于指示该第三帧格式的压缩算法的算法参数。
其中，关于该算法参数的描述可以参考上行传输中对算法参数的描述，此处为了简洁，不再赘述。
需要强调的是，对于下行传输，在一种可能的指示压缩算法的配置方式中，终端设备接收的配置信息中指示该第三帧格式中的哪些字段的内容已经去掉。
在S430中，该网络设备根据该第三以太压缩能力的参数，生成第三以太网数据包。
即，该网络设备使用该第三以太压缩能力的参数，压缩以太网数据，即，去掉以太网数据包的上下文信息，从而生成压缩后的第三以太网数据包。
应理解，同上行传输的第一以太网数据包，下行传输的第三以太网数据包可以是PDCP层的以太网数据包，也可以是其他协议层的以太网数据包，本申请实施例对此不做任何限 定。
在S440中，所述网络设备向所述终端设备发送所述第三以太网数据包。
在S450中，所述终端设备解压缩所述第三以太网数据包。
即，终端设备需要将该第三以太网数据包恢复为未压缩前的数据包，换句话说，需要将网络设备去掉的上下文信息添加至该第三以太网数据包中，恢复该第三以太网数据包的头部区域，从而完成针对该第三以太网数据包的解压缩。
因此，本申请实施例提供的用于以太网数据的通信方法，终端设备通过向网络设备上报自身的以太压缩能力，网络设备基于该终端设备的以太压缩能力为该终端设备配置一种或多种以太压缩能力，可以使得终端设备开启对以太网数据包的解压缩功能，并且，该终端设备向网络设备发送压缩后的数据包，不仅提出了网络设备启动终端设备使用以太压缩能力的方式，也能够使得终端设备和网络设备在无线网络中传输压缩的以太网数据，并且，可以有效地减少信令开销。
为了能够使得终端设备获取上下文信息以便于该终端设备解压缩该第三以太网数据包，本申请实施例提供了一种可能的实现方式：该第三以太网数据包包括第三包头，该第三包头包括第三上下文标识，该第三上下文标识用于标识第三上下文信息；以及，
该方法还包括：
该终端设备根据该第三上下文标识，获取该第三上下文信息；以及，
该终端设备解压缩该第三以太网数据包，包括：
该终端设备根据该第三上下文信息，解压缩该第三以太网数据包。
也就是说，该终端设备从该第三以太网数据包的第三包头中获得该第三上下文标识，基于该第三上下文标识获取该第三上下文标识对应的上下文信息(即，第三上下文信息)，从而，基于该第三上下文信息解压缩该第三以太网数据包，其中，该第三上下文信息可以是上文所列举以及未列举到的不同帧格式的上下文信息。
其中，针对下行传输的第三以太网数据包的第三包头的描述可以参考上文针对上行传输的第一以太网数据包的第一包头的描述，为了简洁，此处不再赘述。
因此，本申请实施例通过在以太网数据包的包头中添加用于标识上下文信息的上下文标识，进一步使得终端设备通过上下文标识获取对应的上下文信息，可以有效地保证终端设备成功解压缩以太网数据包。
如上所述，终端设备可以基于第三上下文标识获取该第三上下文标识对应的上下文信息，具体而言，该终端设备可以基于该第三上下文标识，从该第三上下文标识和该第三上下文信息之间的第三对应关系中获取该第三上下文信息。其中，针对该终端设备获取该第三对应关系的方式，本申请实施例提供了各种可能的实现方式，下面，对该终端设备获取该第三对应关系的具体方式进行简单说明。
方式3
在该方式3中，终端设备从网络设备获取该第三对应关系。也就是说，该网络设备会生成该第三对应关系，并且，将该第三对应关系发送给该终端设备。
在一种可能的实现方式中，该网络设备向该终端设备发送上下文标识和上下文信息之间的对应关系，该对应关系包括该第三对应关系。其中，该对应关系表示至少一个上下文标识和至少一个上下文信息的对应关系，每个上下文标识对应一个上下文信息。
下面，以该第三对应关系为例，对网络设备发送对应关系的方式进行说明。
在一种可能的实现方式中，网络设备可以通过各种形式的信令将该第三对应关系发送给该终端设备，例如，无线资源控制(radio resource control，RRC)信令。
第三为了节省上下文标识占用的比特数，可以生成针对每个帧格式的多个上下文信息，以该第三对应关系为例，在一种可能的实现方式中，该网络设备向该终端设备发送用于指示对应于该第三对应关系的帧格式(即，第三帧格式)的信息。这样，终端设备可以确知该第三对应关系是针对该第三帧格式的对应关系，存储上述节省比特数的上下文标识。
其中，该第三帧格式和该第三对应关系可以承载于同一个信息，也可以承载于不同信息中，本申请实施例对此不做限定。
从节省信令的角度考虑，网络设备也可以在发送未压缩的以太网数据包时，在该未压缩的以太网数据包的包头中携带一个对应关系，该对应关系表示的该未压缩的以太网数据包的帧格式的上下文信息和对应的上下文标识，这样，终端设备可以从该未压缩的以太网数据包中获取该对应关系并存储，这样，若后续网络设备发送一个帧格式和该未压缩的以太网数据包的帧格式相同的压缩后的以太网数据包，终端设备可以直接基于提前存储的对应关系获取压缩后的以太网数据包的上下文信息，进而成功解压缩以太网数据包。
因此，针对该第三对应关系，在另一种可能的实现方式中，该网络设备向该终端设备发送第四以太网数据包，该第四以太网数据包包括第四包头，该第四包头包括该第三对应关系。
在该方式中，该对应关系中除该第三对应关系中的其他对应关系也可以通过未压缩的以太网数据包携带。
同理，为了节省上下文标识占用的比特数，在一种可能的实现方式中，该第四包头还包括该第四以太网数据包的帧格式，该第四以太网数据包的帧格式与该第三以太网数据包的帧格式(即，第三帧格式)相同。
其中，对于下行传输的第四以太网数据包的第四包头的描述可以参考方法300中针对上行传输的第二以太网数据包的第二包头的描述，为了简洁，此处不再描述。
在该方式1中，需要网络设备和终端设备共同维护上下文标识和上下文信息之间的对应关系，考虑到终端设备的缓存能力，为了避免终端设备生成的对应关系超出该终端设备的缓存能力，本申请实施例还提供了一种可能的实现方式：
该网络设备向该终端设备发送第一指示信息，该第一指示信息用于指示所述终端设备生成上下文信息的最大个数。
方式4
终端设备基于该第三上下文标识，从预存的至少一个上下文信息和至少一个上下文标识之间的对应关系中获取该第三对应关系，其中，每个上下文信息对应一个上下文标识。
在该方式2中，预存的对应关系可以是系统或协议规定的，也可以是终端设备提前生成的。可以这么理解，系统或协议可以为不同的能够压缩的帧格式配置M个上下文信息，或者，终端设备可以基于不同的能够压缩的帧格式生成M个上下文信息，并且，为了便于查询和标识，为每个上下文信息配置一个对应的上下文标识。
以上，对本申请实施例的对应关系做了详细说明，下面，对本申请实施例涉及的针对 相关信息的反馈做一说明。
在本申请实施例中，针对该终端设备是否成功接收该第三对应关系和是否成功解压缩该第三以太网数据包都设置了相关反馈模式。
在一种可能的实现方式中，该方法还包括：
网络设备发送反馈模式信息，该反馈模式信息包括以下任一种：正确应答(acknowledgement，ACK)反馈模式、否定应答(negative acknowledgment，NACK)反馈模式或无反馈模式。
作为示例而非限定，该反馈模式信息可以是网络设备发送的配置信息。
以终端设备对该第三对应关系的接收情况为例，对上述3种反馈模式做一说明。
ACK反馈模式表示：若终端设备成功接收该第三对应关系，则该终端设备向该网络设备发送反馈信息，相反地，若终端设备未成功接收该第三对应关系，则该终端设备不发送反馈信息，该网络设备在预设时长内未接收到该反馈信息，则认为该终端设备未成功接收该第三对应关系。
NACK反馈模式表示：若终端设备未成功接收该第三对应关系，则该终端设备向该网络设备发送反馈信息，相反地，若终端设备成功接收该第三对应关系，则该终端设备不发送反馈信息，该网络设备在预设时长内未接收到该反馈信息，则认为该终端设备成功接收该第三对应关系。
无反馈模式表示：该网络设备在发送该第三对应关系后，不关注该终端设备是否成功接收该第三对应关系，不需要接收该终端设备发送的反馈信息。
对于无反馈模式，可选地，终端设备可以从网络设备的配置信息中接收关于无反馈模式的其他参数，例如，N和M。其中，N表示发送端(例如，网络设备)发送非压缩数据包启动压缩模式的次数，M表示发送端(例如，网络设备)启动压缩模式后可以发送压缩数据包的时长，在定时器未超时时使用压缩模式发送，在定时器超时后复位压缩上文信息。
同理，以终端设备对该第三以太网数据包的解压缩情况为例，对上述3种反馈模式做一说明。
ACK反馈模式表示：若终端设备成功解压缩该第三以太网数据包，则该终端设备向该网络设备发送反馈信息，相反地，若终端设备未成功解压缩该第三以太网数据包，则该终端设备不发送反馈信息，该网络设备在预设时长内未接收到该反馈信息，则认为该终端设备未成功解压缩该第三以太网数据包。
NACK反馈模式表示：若终端设备未成功解压缩该第三以太网数据包，则该终端设备向该网络设备发送反馈信息，相反地，若终端设备成功解压缩该第三以太网数据包，则该终端设备不发送反馈信息，该网络设备在预设时长内未接收到该反馈信息，则认为该终端设备成功解压缩该第三以太网数据包。
无反馈模式表示：该网络设备在发送该第三以太网数据包后，不关注该终端设备是否成功解压缩该第三以太网数据包，不需要接收该终端设备发送的反馈信息。
下面，以ACK反馈模式为例，分别从终端设备对该第三对应关系的接收情况和该终端设备对该第三以太网数据的解压缩情况，对该终端设备发送反馈信息的过程做一说明。
终端设备针对该第三对应关系的接收情况
在一种可能的实现方式中，所述方法还包括：
该终端设备向该网络设备发送第三反馈信息，该第三反馈信息用于指示该终端设备成功接收该第三对应关系。
作为示例而非限定，该第三反馈信息可以包括以下至少一种内容：该第三上下文标识或ACK信息。
在一种可能的实现方式中，若该第三对应关系携带在第四以太网数据包的第四包头中，则该第三反馈信息中还可以包括该第四以太网数据包的序列。这种方式，也能指示该终端设备成功接收该第三对应关系。
在本申请实施例中，可以独立设计一个用于携带反馈信息的数据包，对于该第三反馈信息来说，将该第三反馈信息携带在终端设备发送的数据包的负载域。其中，针对用于携带反馈信息的数据包的帧格式的描述可以参考上文关于图7的描述，为了简洁，此处不再赘述。
终端设备针对该第三以太网数据包的解压缩情况
在一种可能的实现方式中，所述方法还包括：
该终端设备向该网络设备发送第四反馈信息，该第四反馈信息用于指示该终端设备成功解压缩该第三以太网数据包。
作为示例而非限定，该第四反馈信息可以包括以下至少一种内容：该第三以太网数据包的序列或ACK信息。
在本申请实施例中，可以独立设计一个用于携带反馈信息的数据包，对于该第四反馈信息来说，将该第四反馈信息携带在终端设备发送的数据包的负载域。其中，对于该用于携带反馈信息的数据包的帧格式可以参考图7的描述，为了简洁，此处不再赘述。
同理，与上行传输类似，本申请实施例的步骤可以在一个功能实体上实现，也可以在多个实体上实现，其中，实体(entity)是指逻辑实体，以逻辑实例的形式实现，具体通过软件实现该实体的功能。假设，本申请实施例可以包括PDCP实体以及压缩/解压缩实体，一种可能的实现方式中，S410和/或S420可以在PDCP实体上实现，S430和/或S450可以在压缩/解压缩实体上实现，PDCP实体在执行S410和/或S420之后，开启压缩/解压缩实体，生成以太网数据包，并将以太网数据包发送给终端设备的压缩/解压缩实体，使终端设备执行解压缩功能。在另一种可能的实现方式中，本申请实施例可以都在PDCP实体上实现。在另一种可能的实现方式中，本申请实施例都在压缩/解压缩实体实现。
以上，分别从上行传输和下行传输的角度对本申请实施例压缩处理以太网数据的过程做了说明。下面，从接收端和发送端的角度下行传输的角度对本申请实施例压缩处理以太网数据的过程继续做说明。
图9是本申请实施例的用于以太网数据的通信方法500的示意性交互图。
在该方法中，接收端可以为终端设备，发送端为网络设备；或者，接收端为网络设备，发送端为终端设备。
S510，发送端生成第五以太网数据包，该第五以太网数据包包括第五包头，该第五包头包括第五上下文标识，该第五上下文标识用于标识第五上下文信息；
S520，该发送端向接收端发送第五以太网数据包；
S530，该接收端根据该第五上下文标识，获取该第五上下文信息；
S540该接收端根据该第五上下文信息解压缩该第五以太网数据包。
因此，本申请实施例的用于以太网数据的通信方法，发送端通过向接收端发送压缩后的以太网数据包(例如，第五以太网数据包)，可以有效地减少资源的浪费，并且，在以太网数据包的包头中添加用于标识上下文信息的上下文标识，可以使得接收端通过上下文标识获取对应的上下文信息，有效地保证了接收端成功解压缩以太网数据包的概率。
可选地，该发送端向该接收端发送下文标识与上下文信息之间的对应关系，该对应关系包括该第五上下文标识和该第五上下文标识的第五对应关系。
可选地，该发送端向该接收端发送第六以太网数据包，该第六以太网数据包包括第六包头，该第六包头包括该第五上下文标识与该第五上下文信息的对应关系。
因此，通过未压缩的以太网数据包(例如，第六以太网数据包)携带对应关系，能够减少信令开销，节省资源。
可选地，该第六包头还包括用于指示该第六以太网数据包的帧格式的类型的指示信息，该第六以太网数据包的帧格式的类型与该第五以太网数据包的帧格式的类型相同。
因此，通过在未压缩的以太网数据包(例如，第六以太网数据包)中携带帧格式，可以使得系统建立针对每个帧格式的至少一个上下文标识，在每个帧格式中标识上下文信息，能够节省上下文标识占用的比特数。
可选地，该方法还包括：
该接收端向该发送端发送第五反馈信息，该第五反馈信息用于指示该接收端成功接收该对应关系。
可选地，该第五反馈信息包括：该对应关系中的上下文标识。
其中，该第五反馈信息包括针对该第五对应关系中的第五上下文标识。
可选地，该方法还包括：
该接收端向该发送端发送第六反馈信息，该第六反馈信息用于指示该接收端成功解压缩该第五数据包。
可选地，该发送端为终端设备，该接收端为网络设备；以及，该方法还包括：
该发送端向该接收端发送压缩能力信息，该压缩能力信息用于指示该发送端支持的N种以太压缩能力，N为大于或等于1的整数；
该接收端向该接收端发送压缩配置信息，该压缩配置信息用于指示第五以太压缩能力的参数，该N种以太压缩能力包括该第五以太压缩能力；以及，
该发送端生成第五以太网数据包，包括：
该发送端根据该第五以太压缩能力的参数，生成该第五以太网数据包。
可选地，该发送端为网络设备，该接收端为终端设备；以及，该方法还包括：
该接收端向该发送端发送压缩能力信息，该压缩能力信息用于指示该接收端支持的N种以太压缩能力，N为大于或等于1的整数；
该发送端向该接收端发送压缩配置信息，该压缩配置信息用于指示第五以太压缩能力的参数，该N种以太压缩能力包括该第五以太压缩能力；以及，
该发送端生成第五以太网数据包，包括：
该发送端根据该第五以太压缩能力的参数，生成该第五以太网数据包。
在上行传输中，接收端为网络设备，发送端为终端设备，本申请实施例的方法可以参 考方法300，为了简洁，此处不再赘述。其中，方法500中的第五以太网数据包可以对应方法300中的第一以太网数据包，方法500中的第五包头可以对应方法300中的第一包头，方法500中的第五上下文标识可以对应方法300中的第一上下文标识，方法500中的第五上下文信息可以对应方法300中的第一上下文信息，方法500中的第五对应关系可以对应方法300中的第一对应关系，方法500中的第六以太网数据包可以对应方法300中的第二以太网数据包，方法500中的第六包头可以对应方法300中的第二包头，方法500中的第五反馈信息可以对应方法300中的第一反馈信息，方法500中的第六反馈信息可以对应方法300中的第二反馈信息。
在下行传输中，接收端可以为终端设备，发送端为网络设备，本申请实施例的方法可以参考方法400，为了简洁，此处不再赘述。其中，方法500中的第五以太网数据包可以对应方法400中的第三以太网数据包，方法500中的第五包头可以对应方法400中的第三包头，方法500中的第五上下文标识可以对应方法400中的第三上下文标识，方法500中的第五上下文信息可以对应方法400中的第三上下文信息，方法500中的第五对应关系可以对应方法400中的第三对应关系，方法500中的第六以太网数据包可以对应方法400中的第四以太网数据包，方法500中的第六包头可以对应方法400中的第四包头，方法500中的第五反馈信息可以对应方法400中的第三反馈信息，方法500中的第六反馈信息可以对应方法400中的第四反馈信息。
下面，从接收端和发送端的角度，通过图13所示的以太压缩状态的转化图，对本申请实施例的发送压缩数据包和发送未压缩的数据包之间的行为转换做一说明。
1、发送端处于初始化状态，初始化状态表示发送端已经配置好了相关以太压缩/解压缩功能。
可选地，在发送端压缩启动前，接收端可以发送以太压缩初始化指示。接收端接收到该指示后开始准备以太压缩/解压缩功能。例如，在PDCP的子头或以太压缩信令、MAC信令、RRC信令、NAS信令中增加一个初始化指示。可以理解，接收端后续收到的以太网数据包，需要经由解压缩功能处理。发送端发送的以太网数据包需要经由压缩功能处理。
2、作为示例而非限定，在发生以下任一事件时，发送端发送未压缩的以太网数据包，其中，在未压缩的以太网数据包中可以携带需要接收端存储的上下文信息。
可选地，发送端未建立上下文信息
可选地，发送端与接收端处于失步状态
3、作为示例而非限定，在发生以下任一事件时，发送端从初始化状态转化为压缩状态：
可选地，在发送端压缩启动前，接收端可以发送以太压缩启动指示。接收端接收到该指示信息后，启动以太压缩/解压缩功能。例如，在PDCP的子头或以太压缩信令、MAC信令、RRC信令、NAS信令中增加一个启动指示。可以理解，接收端后续收到的以太网数据包，需要经由解压缩功能处理。发送端发送的以太网数据包需要经由压缩功能处理。
4、在确定发送压缩的以太网数据包后，发送端发送压缩的以太网数据包。
4A、压缩挂起状态
在这个过程中，可选地，接收端可以发送以太压缩挂起指示，发送端在接收到该指示后，进行暂停以太压缩行为。例如，在PDCP的子头或以太压缩信令、MAC信令、RRC 信令、NAS信令中增加一个以太压缩挂起指示。
可选地，接收端可以发送以太压缩恢复指示，接收端在接收到该指示后，恢复以太压缩行为。例如，在PDCP的子头或以太压缩信令、MAC信令、RRC信令、NAS信令中增加一个以太压缩恢复指示。
可选地，若发送端未接收到以太压缩恢复指示，发送端便从压缩挂起状态转化为初始化状态。
5、在发生以下任一事件时，发送端从压缩状态转化为初始化状态：
可选的，在终端接收到以太压缩缓存复位指示，终端进行复位以太压缩缓存的上下文信息。例如，在PDCP的子头或以太压缩信令、MAC信令、RRC信令、NAS信令中增加一个以太压缩缓存复位指示。例如，在终端发生切换时用于重新同步双方的上下文。
以上，结合图3至图9，对第一方面的实施例做了详细说明。下面，结合图10和图11，对本申请实施例的第二方面的实施例进行详细说明。
如前所述，第二方面描述的是关于如何传输广播类型或组播类型的以太网数据包的方案，在本申请实施例中，提供了两种传输广播类型或组播类型的以太网数据包的方式(即，方式A和方式B)。在方式A中，提出了一个针对广播类型或组播类型的以太网数据包的RNTI，网络设备基于该RNTI发送广播类型的以太网数据包；在方式B中，提出了在系统消息块(system information blocks，SIB)中发送广播类型的以太网数据包。这两种方式可以结合使用，也可以单独使用。此外，第二方面的实施例可以和第一方面的实施例相结合，第二方面的实施例也可以单独使用，本申请实施例不限于此。
为了便于理解，首先，对本申请实施例涉及的发送数据的广播方式和组播方式做一说明。
广播方式：基于广播方式发送数据包时，数据包从单一的源发送到共享以太网上的所有主机，所有收到该数据包的主机都要接收并处理该数据包。作为示例而非限定，广播类型的以太网数据包的MAC地址的长度为48位，每位的取值都为1，以十六进制显示时则为FF-FF-FF-FF-FF-FF。
组播方式：基于组播方式发送数据包时，数据包从源设备发送到一组主机，可以将组播方式理解为具有选择性的广播方式。在组播方式中，属于一组的主机都被分配了一个组播地址，主机侦听特定组播地址，接收并处理目的MAC地址为该组播MAC地址的数据包。
在本申请实施例中，为了描述简洁，可以将采用广播方式发送的以太网数据包称为广播类型的以太网数据包，将采用组播方式发送的以太网数据包称为组播类型的以太网数据包，将采用单播方式发送的以太网数据包称为单播类型的以太网数据包。此外，可以将针对广播类型的以太网数据包的RNTI简称为广播类型的RNTI，将针对组播类型的以太网数据包的RNTI简称为组播类型的RNTI，将针对单播类型的以太网数据包的RNTI简称为单播类型的RNTI，两种描述可以互相替换。
此外，由于广播类型或组播类型的数据包需要被发送至多个终端设备，为了便于描述，以多个终端设备中的任一个终端设备为例，对本申请实施例进行说明。
下面，结合图10和图11分别对上述两种方式进行说明。
方式A
网络设备基于针对广播类型或组播类型的以太网数据包的RNTI发送广播类型的以太网数据包
作为示例而非限定，方式A可以适用于终端设备处于连接态的场景。
图10所示为本申请实施例的用于以太网数据的通信方法600的示意性交互图。
在S610中，网络设备向终端设备发送下行控制信息DCI，该DCI采用第一无线网络临时标识(radio network temporary identifier，RNTI)加扰，该第一RNTI是针对以太网数据包的RNTI，该DCI包括用于指示承载该以太网数据包的时频资源的信息。
在S620中，该网络设备向该终端设备发送该以太网数据包。
在S630中，该终端设备根据在该DCI所指示的时频资源上，从该网络设备接收该以太网数据包。
在一种可能的实现方式中，该第一RNTI可以是针对非单播类型的RNTI。例如，该第一RNTI可以是针对组播类型的以太网数据包，也可以是针对广播类型的以太网数据包，也可以是针对其他类型的以太网数据包，本申请实施例不做限定。实现中，例如，用于调度单播类型的以太网数据包的调度信息(即，DCI)采用第二RNTI加扰，新引入第一RNTI，采用该第一RNTI加扰非单播类型的以太数据包的DCI。
具体而言，网络设备需要调度非单播类型的以太网数据包时，可以采用该第一RNTI对调度非单播类型的以太网数据包的DCI进行加扰，终端设备在检测并接收到该DCI后，可以确知该DCI调度的数据包以太网数据包，都会在该DCI所指示的时频资源上接收该以太网数据包。
在本申请实施例中，该第一RNTI专用于接收非单播类型以太网数据包，可以理解为在终端设备和网络设备之间的信号信息内部的一种终端设备的标识。这个标识可以是预配置在终端设备上的，也可以是协议约定的，也可以是终端设备从网络设备接收的。对于该标识是协议约定的情况，只有支持以太网类型的终端设备使用该标识接收下行调度信息(例如，DCI)；对于该标识是配置的情况，只有接收到该标识的终端设备使用该标识接收下行调度信息；对于该标识是终端设备从网络设备接收的情况，终端设备通过专用或广播消息来接收该标识。
在一种可能的实现方式中，该第一RNTI是针对广播类型或组播类型的以太数据包的RNTI。
具体而言，若网络设备需要发送广播类型的以太网数据包，则采用广播类型的RNTI(例如，RNTI1)加扰指示该以太网数据包的时频资源的DCI；若网络设备需要发送组播类型的以太网数据包，则采用组播类型的RNTI(例如，RNTI2)加扰指示该以太网数据包的时频资源的DCI。终端设备可以接收同时接收利用RNTI 1加扰的DCI和利用RNTI 2加扰的DCI，并基于加扰标识，确定以太数据包的类型，即是广播类型的以太数据包还是组播类型的以太数据包。其它类型的以太数据包可以采用相同的方式进行传输和接收。
作为示例而非限定，在实现中，系统中会存在预留的多种类型的RNTI，网络设备在发送以太网数据包时，可以基于以太网数据包的类型，从预留的RNTI中选择对应数据包类型的RNTI对DCI加扰。例如，若是广播类型的以太网数据包，则可以从预留的RNTI中选择广播类型的RNTI(例如，RNTI1)加扰指示该以太网数据包的时频资源的DCI；若是组播类型的以太网数据包，则可以从预存的RNTI中选择组播类型的RNTI(例如， RNTI2)加扰指示该以太网数据包的时频资源的DCI。
下面，分别从广播类型的RNTI和组播类型的RNTI，对该第一RNTI涉及的内容进行说明。
该第一RNTI为广播类型的RNTI
若该第一RNTI为广播类型的RNTI，则在广播范围内的小区的终端设备监听该第一RNTI加扰的DCI，在接收到该DCI后，都会去该DCI所指示的时频资源上接收以太网数据包。
由于该第一RNTI是广播类型的RNTI，并且，一般情况下，广播类型的以太网包中的MAC地址都是固定不变的，例如，上文所说FF-FF-FF-FF-FF-FF，这种情况下，可以没必要在数据包中添加这个广播类型的MAC地址。因此，本申请实施例提供了一种可能的实现方式：
该第一RNTI是针对广播类型的以太网数据包的RNTI，该以太网数据包的包头中不包括广播类型的媒体介入控制MAC地址。
这样，通过广播类型的以太网数据包中删除广播类型的MAC地址，可以有效地节省资源。
在一种可能的实现方式中，该DCI包括第一信息，该第一信息用于指示该DCI调度的数据包为广播类型的以太网数据包。
该第一RNTI为组播类型的RNTI
对于组播类型的RNTI，可以为至少一个组的终端设备配置至少一个组播类型的RNTI，一个组的终端设备对应一个组播类型的RNTI。若该第一RNTI为组播类型的RNTI，对应该第一RNTI的一个组内的终端设备监听该第一RNTI，在接收到该DCI后，都会去该DCI所指示的时频资源上接收以太网数据包。
在一种可能的实现方式中，该DCI包括第一信息，该第一信息用于指示该DCI调度的数据包为组播类型的以太网数据包。
因此，本申请实施例的用于以太网数据的通信方法，通过一个专门针对广播类型或组播类型的RNTI加扰DCI，可以减少对需要接收该广播类型或组播类型的终端设备以外的其他终端设备的干扰，提高了以太网数据的传输性能。
在本申请实施例中，当以太网数据包是组播类型的以太网数据包时，若组播MAC地址和RNTI对应，即，若终端设备可以根据组播类型的RNTI确定出组播地址时，以太网数据包的包头中可以不包括组播类型的MAC地址。例如，针对每个组播组设置一个RNTI，用于加扰每个组播组内的至少一个终端设备的数据包的调度信息所在的DCI，这样，组播组内的终端设备可以根据该组播组对应的RNTI，确定该RNTI对应的组播组，进而可以不在以太网数据包的包头中携带MAC地址。
在网络设备为接入网的情况下，为了便于接入网设备识别从核心网设备接收到的以太网数据包是哪种类型的，可以在接入网设备与核心网设备之间建立一个公共服务质量(quality of service，Qos)流，该公共Qos流是用于携带广播类型或组播类型的以太网数据包的Qos流。实现过程中，若网络设备是从该公共Qos流中接收到的以太网数据包，则认为接收到的该以太网数据包需要该网络设备通过广播方式或组播方式发送给终端设备。
在本申请实施例中，可以不需要在DCI中指示携带该以太网数据包的时频资源，采用 该第一RNTI加扰DCI，通过SIB指示携带该以太网数据包的时频资源，终端设备根据该DCI和SIB接收该以太网数据包。
为了使得网络设备确知该终端设备是否成功接收到该以太网数据包，该终端设备可以向网络设备发送反馈信息。具体如何发送反馈信息，作为示例而非限定，终端设备在接收该以太网数据包后，可以按预先配置好的顺序，在物理上行共享信道(physical uplink shared channel，PUSCH)或物理上行链路控制信道(physical uplink control channel，PUCCH)等上行信道发送反馈。
其中，预先配置好的顺序，有两种含义：
第一种含义：无论该终端设备的信息是否出现在该广播类型或组播类型的以太网数据包中，该终端设备都会在接收到该以太网数据包之后占用一份发送反馈资源发送反馈信息。
第二种含义：只有该终端设备的信息出现在该广播类型或组播类型的以太网数据包，该终端设备才会在接收到该以太网数据包之后占用一份发送反馈资源发送反馈信息。
这里，反馈资源的确定方式可以是以下任一种：
终端设备根据以太网数据包所在的无线帧的位置映射得到该反馈资源；或者，
终端设备根据以太网数据包所在的起始无线帧的位置映射得到该反馈资源；或者，
终端设备根据以太网数据包所在的结束无线帧的位置映射得到该反馈资源；或者，
终端设备根据调度以太网数据包所使用的DCI的控制信道单元(control channel element，CCE)位置映射的。
方式B
网络设备通过SIB发送广播类型的以太网数据包
图11所示为本申请实施例的用于以太网数据的通信方法700的示意性交互图。
在S701中，网络设备发送寻呼消息，该寻呼消息包括指示信息，该指示信息用于指示该SIB包括该以太网数据包。
换句话说，该指示信息用于指示该SIB的类型为包括以太网数据包的SIB类型；或者，该指示信息用于通知终端设备该网络设备在SIB中发送以太网数据包。
在S710中，该网络设备生成SIB，该SIB包括以太网数据包。
作为示例而非限定，SIB中还可以指示以太网帧格式、虚拟网络标签和/或业务虚拟网络标签。
在S720中，网络设备向该终端设备发送该SIB。
作为示例而非限定，网络设备可以不用发送该指示信息，也可以不用在寻呼消息中发送该指示信息，终端设备直接接收SIB消息即可。
因此，本申请实施例提供的用于以太网数据的通信方法，通过SIB发送广播类型的以太网数据包，可以高效地通知终端设备接收以太网数据包，提高传输效率。
此外，通过在寻呼消息中添加该第三信息，可以有效地利用寻呼消息的发送机制，即，终端设备在周期性时间段内接收寻呼消息检测是否有针对自己的消息，降低了设计复杂度，也能提高终端设备接收数据包的可靠性。
同方式A中的描述，一般情况下，广播类型的以太网包中的MAC地址都是固定不变的，例如，上文所说FF-FF-FF-FF-FF-FF，这种情况下，可以不需要在数据包中添加这个 广播类型的MAC地址。因此，本申请实施例提供了一种可能的实现方式：
该以太网数据包的包头中不包括广播类型的媒体介入控制MAC地址。
这样，通过广播类型的以太网数据包中删除广播类型的MAC地址，可以有效地节省资源。
在方式B中，同方式A，若网络设备为接入网设备，可以在接入网设备与核心网设备之间建立一个公共Qos流，若接入网设备是从该公共Qos流中接收到的以太网数据包，则认为接收到的该以太网数据包需要该网络设备通过广播方式或组播方式发送给终端设备。此外，为了使得网络设备确知该终端设备是否成功接收到该以太网数据包，该终端设备可以向网络设备发送反馈信息，具体如何发送反馈信息，可以参考方式A中的相关描述，为了简洁，此处不再赘述。
在本申请实施例中，可以结合使用方式A和方式B。例如：
网络设备向终端设备发送下行控制信息DCI，该DCI采用第一无线网络临时标识RNTI加扰，该第一RNTI是针对以太网数据包的RNTI，该DCI包括用于指示承载所述以太网数据包的时频资源的信息；
该网络设备向该终端设备发送SIB，该SIB包括该以太网数据包；
该终端设备根据在该DCI所指示的时频资源上，从该网络设备接收该SIB。也就是说，在这种方式中，可以通过SIB携带以太网数据包。其中，关于该第一RNTI的描述可以参考方式A中对于第一RNTI的描述，此处不再赘述。
以上，结合图10至图11，对第二方面的实施例进行详细说明。下面，结合图12对本申请实施例的第三方面的实施例进行详细说明。
第一方面中已经明确指出，以太网数据包中需要携带终端设备的MAC地址，这样，便于正确传输以太网数据包。因此，对于网络设备来说，需要及时获知与该网络设备通信连接的终端设备的MAC地址。第三方面提出了如何上报MAC地址的方案。第三方面可以与第一方面或第二方面中的至少一个结合使用，也可以单独使用。
在本申请实施例中，终端设备可以在3种情况下发送MAC地址，下面，分别对3种情况分别阐述。
情况1
终端设备在接收到网络设备发送的请求信息后上报MAC地址
图12所示为本申请实施例的用于以太网数据的通信方法800的示意性交互图。
在810中，网络设备发送请求消息，该请求消息用于请求与该终端设备关联的媒体介入控制MAC地址；
在S820中，该终端设备向该网络设备发送MAC地址。。
其中，与终端设备关联的MAC地址，可以包括终端设备本身的MAC地址，也可以包括与该终端设备有线或无线连接的其他终端设备的MAC地址，为了区别起见，可以将该终端设备为转接终端，将与该终端设备关联的终端设备为关联终端。该终端设备需要上报与该终端设备关联的MAC地址，原因在于，在例如图1所示的组网系统中，一个终端设备可能会与多个终端设备连接，例如，终端设备131不仅与终端设备132连接，还与其他终端设备连接，终端设备132和其他终端设备需要终端设备131为其转发数据，作为终端设备132和其他终端设备的转接设备，为了可以正确传输以太网数据包，终端设备131 也需要与其连接的其他终端设备的MAC地址上报给网络设备。
该网络设备可以是接入网设备或核心网设备。作为示例而非限定，若该网络设备是接入网设备，则接入网设备可以发送专用RRC信令，请求终端设备上报该终端设备所使用的MAC地址；若该网络设备是核心网设备，则核心网设备可以发送专用NAS信令，请求终端设备上报所使用的MAC地址。可以理解，请求信息可以是终端设备的MAC类型的标识查询请求。
因此，本书申请实施例的用于以太网数据的通信方法，网络设备通过向终端设备发送用于请求终端设备的MAC地址的请求信息，能够使得终端设备及时向网络设备上报MAC地址，这样，网络设备能够及时获知终端设备的MAC地址，从而便于数据的传输。
关于上报MAC地址的方式，在一种可能的实现方式中，该终端设备发送非接入层NAS消息，该NAS消息包括该响应信息。
即，终端设备注册到移动网络，并启用NAS安全保护后，可以通过NAS消息上报终端设备的MAC地址给网络设备(例如，核心网设备)，可选地，核心网设备可以将接收到的MAC地址发送给接入网设备。例如，NAS消息可以是跟踪区域更新(tracking area updating，TAU)或PDU会话建立请求等。
在另一种可能的实现方式中，终端设备可以通过业务请求消息或PDN连接建立请求消息将MAC地址上报给核心网设备。可选地，核心网设备可以将接收到的MAC地址发送给接入网设备。
情况2
在与终端设备关联的媒体介入控制MAC地址发生变化的情况下，该终端设备向网络设备变化后的MAC地址。
例如，通过有线连接到终端设备的以太网设备的网卡更换了，那么MAC地址一般会发生更改，这样终端设备需要更新MAC地址，因此，需要将更换的MAC地址上报给网络设备。
关于上报MAC地址的方式，可以参考情况1的相关描述，为了简洁，此处不再赘述。
情况3
终端设备周期性上报与该终端设备关联的MAC地址
作为示例而非限定，周期性上报的时长可以是网络设备通过定时器配置的，也可以是终端设备自己通过定时器配置的。
终端设备可以通过专用的RRC信令上报或专用的NAS信令将MAC地址上报给网络设备。
例如，在位置区更新消息(tracking Area update，TAU)中指示MAC地址。再例如，在TAU请求消息中指示新增的MAC地址。
以上，对第三方面的实施例做了详细描述，下面，对本申请实施例的第四方面的实施例进行详细描述。
如前所述，第四方面描述的是网络设备如何定位寻找终端设备。在第四方面中，网络设备向终端设备发送寻呼消息，该寻呼消息中携带需要被寻呼的终端设备的MAC地址，该终端设备可以根据接收到的寻呼消息中的MAC地址确定是否为自己的MAC地址或者是否为与该终端设备连接的其他终端设备的MAC地址，具体来说，该终端设备可以判断接收 到的MAC地址是否和高层提供或分配的MAC地址匹配，若匹配,则将MAC地址转给高层，该终端设备发起RRC连接建立请求或连接恢复请求，或者，该终端设备通知其他终端设备发起RRC连接建立请求或连接恢复请求。
以上，对本申请实施例涉及的4个方面做了详细描述，上述4个方面的实施例可以单独使用，也可以相互结合使用。下面，对关于结合使用4个方面中至少一个方面的情况进行说明。
第二方面与第一方面结合使用，第二方面描述的广播类型或组播类型的以太网数据包可以是第一方面中方法400中的第三以太网数据包，也可以是方法500中发送端为网络设备的情况下的第五以太网数据包。可以这么理解，第一方面阐述的是如何压缩处理以太网数据包，第二方面阐述的是若该以太网数据包为广播类型或组播类型的以太网数据包，则可以通过第二方面中的方式A和方式B发送该以太网数据包。
第三方面与第一方面结合使用，在第三方面中，终端设备上报了MAC地址，在第一方面中，网络设备在发送以太网数据包(例如，方法400中的第三以太网数据包或方法500发送端为网络设备的情况下的第五以太网数据包)时，将上报的MAC地址携带在以太网数据包对应的上下文信息中，并且，在以太网数据包中携带的对应上下文信息的上下文标识；或者，将上报的MAC地址携带在以太网数据包(例如，方法400中的第四以太网数据包或方法500中发送端为网络设备的情况下的第六以太网数据包)中。
第三方面与第二方面结合使用，在第三方面中，终端设备上报了MAC地址，在第二方面中，网络设备在发送广播类型或组播类型的以太网数据包时，将上报的MAC地址携带在以太网数据包中。
第三方面与第二方面、第一方面结合使用，广播类型或组播类型的以太网数据包可以是第一方面中方法400中的第三以太网数据包或第四以太网数据包，也可以是方法500中发送端为网络设备的情况下的第五以太网数据包或第六以太网数据包。在以太网数据包是方法400中的第三以太网数据包或方法500发送端为网络设备的情况下的第五以太网数据包时，可以将上报的MAC地址携带在以太网数据包对应的上下文信息中，并且，在以太网数据包中携带的对应上下文信息的上下文标识；在以太网数据包是方法400中的第四以太网数据包或方法500发送端为网络设备的情况下的第六以太网数据包时，可以将上报的MAC地址携带在以太网数据包中。
第四方面与第一方面、第二方面或第三方面结合使用，可以在网络设备处于异常情况时，在第一方面、第二方面或第三方面的任一种场景中，用于寻找终端设备。
应理解，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
上文中结合图1至图13，详细描述了根据本申请实施例的用于以太网数据的通信方法，下面将结合图14至图15，详细描述根据本申请实施例的用于以太网数据的装置。
图14示出了本申请实施例提供的用于以太网数据的装置1400，该装置1400可以是终端设备，也可以为终端设备中的芯片。该装置1400可以是网络设备，也可以为网络设备中的芯片。该装置1400包括：收发单元1410和处理单元1420。
在一种可能的实现方式中，装置1400用于执行上述方法300中终端设备对应的各个流程和步骤。
该收发单元1410用于：从网络设备接收压缩配置信息，所述压缩配置信息用于指示第一以太压缩能力的参数；该处理单元1420用于：根据所述第一以太压缩能力的参数，生成第一以太网数据包；所述收发单元1410还用于：向所述网络设备发送所述第一以太网数据包。
可选地，所述收发单元1410还用于：向所述网络设备发送压缩能力信息，所述压缩能力信息用于指示所述装置支持的N种以太压缩能力，所述N种以太压缩能力包括所述第一以太压缩能力，N为大于或等于1的整数。
可选地，所述第一以太压缩能力的参数包括使能参数，所述使能参数用于指示所述装置使用所述第一以太压缩能力。
可选地，所述第一以太压缩能力的参数包括：用于指示第一帧格式的帧格式参数，或，用于指示第一帧格式的压缩算法的算法参数，所述第一帧格式为第一以太网数据包的帧格式。
可选地，所述第一以太网数据包包括第一包头，所述第一包头包括第一上下文标识，所述第一上下文标识用于标识第一上下文信息。
可选地，所述收发单元1410还用于：向所述网络设备发送所述第一上下文标识与所述第一上下文信息之间的第一对应关系。
可选地，所述收发单元1410还用于：向所述网络设备发送第二以太网数据包，所述第二以太网数据包包括第二包头，所述第二包头包括所述第一对应关系。
可选地，所述第二包头还包括所述第二以太网数据包的帧格式，所述第二以太网数据包的帧格式与所述第一以太网数据包的帧格式相同。
可选地，所述收发单元1410还用于：向所述网络设备发送上下文标识和上下文信息之间的对应关系，所述对应关系包括所述第一对应关系。
可选地，所述收发单元1410还用于：从所述网络设备接收第一反馈信息，所述第一反馈信息用于指示所述网络设备成功接收所述第一对应关系。
可选地，所述第一反馈信息包括：所述第一上下文标识。
可选地，所述收发单元1410还用于：从所述网络设备接收第二反馈信息，所述第二反馈信息用于指示所述网络设备成功解压缩所述第一以太网数据包。
在另一种可能的实现方式中，装置1400用于执行上述方法300中网络设备对应的各个流程和步骤。
该收发单元1410用于：向终端设备发送压缩配置信息，所述压缩配置信息用于指示第一以太压缩能力的参数，接收第一以太网数据包，所述第一以太网数据包是基于所述第一以太网压缩能力的参数生成的；该处理单元1420用于：解压缩所述第一以太网数据包。
可选地，所述收发单元1410还用于：从所述终端设备接收压缩能力信息，所述压缩能力信息用于指示所述终端设备支持的N种以太压缩能力，所述N种以太压缩能力包括所述第一以太压缩能力，N为大于或等于1的整数。
可选地，所述第一以太压缩能力的参数包括使能参数，所述使能参数用于指示所述终端设备使用所述第一以太压缩能力。
可选地，所述第一以太压缩能力的参数包括用于指示第一帧格式的帧格式参数和/或用于指示第一帧格式的压缩算法的算法参数，所述第一帧格式为第一以太网数据包的帧格 式。
可选地，所述第一以太网数据包包括第一包头，所述第一包头包括第一上下文标识，所述第一上下文标识用于标识第一上下文信息；以及，所述处理单元1420还用于：根据所述第一上下文标识，获取所述第一上下文信息；根据所述第一上下文信息，解压缩所述第一以太网数据包。
可选地，所述收发单元1410还用于：从所述终端设备接收所述第一上下文标识与所述第一上下文信息之间的第一对应关系。
可选地，所述收发单元1410还用于：从所述终端设备接收第二以太网数据包，所述第二以太网数据包包括第二包头，所述第二包头包括所述第一对应关系。
可选地，所述第二包头还包括所述第二以太网数据包的帧格式，所述第二以太网数据包的帧格式与所述第一以太网数据包的帧格式相同。
可选地，所述收发单元1410还用于：从所述终端设备接收上下文标识和上下文信息之间的对应关系，所述对应关系包括所述第一对应关系。
可选地，所述收发单元1410还用于：向所述终端设备发送第一反馈信息，所述第一反馈信息用于指示所述装置成功接收所述第一对应关系。
可选地，所述第一反馈信息包括：所述第一上下文标识。
可选地，所述收发单元1410还用于：向所述终端设备发送第二反馈信息，所述第二反馈信息用于指示所述装置成功解压缩所述第一以太网数据包。
在另一种可能的实现方式中，装置1400用于执行上述方法400中终端设备对应的各个流程和步骤。
该收发单元1410用于：从网络设备接收压缩配置信息，所述压缩配置信息用于指示第三以太压缩能力的参数，从所述网络设备接收第三以太网数据包，所述第三以太网数据包是基于所述第三以太网压缩能力的参数生成的；该处理单元1420用于：解压缩所述第三以太网数据包。
可选地，所述收发单元1410还用于：向所述网络设备发送压缩能力信息，所述压缩能力信息用于指示所述装置支持的N种以太压缩能力，所述N种以太压缩能力包括所述第三以太压缩能力，N为大于或等于1的整数。
可选地，所述第三以太压缩能力的参数包括使能参数，所述使能参数用于指示所述装置使用所述第三以太压缩能力。
可选地，所述第三以太压缩能力的参数包括：用于指示第三帧格式的帧格式参数，或，用于指示第三帧格式的压缩算法的算法参数，所述第三帧格式为所述第三以太网数据包的帧格式。
可选地，所述第三以太网数据包包括第三包头，所述第三包头包括第三上下文标识，所述第三上下文标识用于标识第三上下文信息；以及，所述处理单元1420还用于：根据所述第三上下文标识，获取所述第三上下文信息；根据所述第三上下文信息，解压缩所述第三以太网数据包。
可选地，所述收发单元1410还用于：从所述网络设备接收所述第三上下文标识与所述第三上下文信息之间的第三对应关系。
可选地，所述收发单元1410还用于：从所述网络设备接收第四以太网数据包，所述 第四以太网数据包包括第四包头，所述第四包头包括所述第三对应关系。
可选地，所述第四包头还包括所述第四以太网数据包的帧格式，所述第四以太网数据包的帧格式与所述第三以太网数据包的帧格式相同。
可选地，所述收发单元1410还用于：从所述网络设备接收上下文标识和上下文信息之间的对应关系，所述对应关系包括所述第三对应关系。
可选地，所述收发单元1410还用于：向所述网络设备发送第三反馈信息，所述第三反馈信息用于指示所述装置成功接收所述第三对应关系。
可选地，所述第三反馈信息包括：所述第三上下文标识。
可选地，所述收发单元1410还用于：向所述网络设备发送第四反馈信息，所述第四反馈信息用于指示所述装置成功解压缩所述第三以太网数据包。
在另一种可能的实现方式中，装置1400用于执行上述方法400中网络设备对应的各个流程和步骤。
该收发单元1410用于：向终端设备发送压缩配置信息，所述压缩配置信息用于指示第三以太压缩能力的参数；该处理单元1420用于：根据所述第三以太压缩能力的参数，生成第三以太网数据包；该收发单元1410还用于：向所述终端设备发送所述第三以太网数据包。
可选地，所述收发单元1410还用于：从所述终端设备接收压缩能力信息，所述压缩能力信息用于指示所述终端设备支持的N种以太压缩能力，所述N种以太压缩能力包括所述第三以太压缩能力，N为大于或等于1的整数。
可选地，所述第三以太压缩能力的参数包括使能参数，所述使能参数用于指示所述终端设备使用所述第三以太压缩能力。
可选地，所述第三以太压缩能力的参数包括用于指示第三帧格式的帧格式参数和/或用于指示第三帧格式的压缩算法的算法参数，所述第三帧格式为第三以太网数据包的帧格式。
可选地，所述第三以太网数据包包括第三包头，所述第三包头包括第三上下文标识，所述第三上下文标识用于标识第三上下文信息。
可选地，所述收发单元1410还用于：向所述终端设备发送所述第三上下文标识与所述第三上下文信息之间的第三对应关系。
可选地，所述收发单元1410还用于：向所述终端设备发送第四以太网数据包，所述第四以太网数据包包括第四包头，所述第四包头包括所述第三对应关系。
可选地，所述第四包头还包括所述第四以太网数据包的帧格式，所述第四以太网数据包的帧格式与所述第三以太网数据包的帧格式相同。
可选地，所述收发单元1410还用于：向所述终端设备发送上下文标识和上下文信息之间的对应关系，所述对应关系包括所述第三对应关系。
可选地，所述收发单元1410还用于：从所述终端设备接收第三反馈信息，所述第三反馈信息用于指示所述终端设备成功接收所述第三对应关系。
可选地，所述第三反馈信息包括：所述第三上下文标识。
可选地，所述收发单元1410还用于：从所述终端设备接收第四反馈信息，所述第四反馈信息用于指示所述终端设备成功解压缩所述第三以太网数据包。
在另一种可能的实现方式中，装置1400用于执行上述方法500中发送端对应的各个流程和步骤。
该处理单元1420用于：生成第五以太网数据包，所述第五以太网数据包包括第五包头，所述第五包头包括第五上下文标识，所述第五上下文标识用于标识第五上下文信息；该收发单元1410用于：向接收端发送第五以太网数据包。
可选地，所述收发单元1410还用于：向所述接收端发送下文标识与上下文信息之间的对应关系，所述对应关系包括所述第五上下文标识和所述第五上下文标识的第五对应关系。
可选地，所述收发单元1410还用于：向所述接收端发送第六以太网数据包，所述第六以太网数据包包括第六包头，所述第六包头包括所述第五上下文标识与第五上下文信息的对应关系。
可选地，所述第六包头还包括用于指示所述第六以太网数据包的帧格式的类型的指示信息，所述第六以太网数据包的帧格式的类型与所述第五以太网数据包的帧格式的类型相同。
可选地，所述收发单元1410还用于：从所述接收端接收第五反馈信息，所述第五反馈信息用于指示所述接收端成功接收所述对应关系。
可选地，所述第五反馈信息包括：所述对应关系中的上下文标识。
可选地，所述收发单元1410还用于：从所述接收端接收第六反馈信息，所述第六反馈信息用于指示所述接收端成功解压缩所述第五数据包。
可选地，所述装置为终端设备，所述接收端为网络设备；以及，所述收发单元1410还用于：
从所述接收端接收压缩配置信息，所述压缩配置信息用于指示第五以太压缩能力的参数；根据所述第五以太压缩能力的参数，生成所述第五以太网数据包。
可选地，所述收发单元1410还用于：向所述接收端发送压缩能力信息，所述压缩能力信息用于指示所述装置支持的N种以太压缩能力，所述N种以太压缩能力包括所述第五以太压缩能力，N为大于或等于1的整数。
可选地，所述装置为网络设备，所述接收端为终端设备；以及，所述收发单元1410还用于：向所述接收端发送压缩配置信息，所述压缩配置信息用于指示第五以太压缩能力的参数；
根据所述第五以太压缩能力的参数，生成所述第五以太网数据包。
可选地，所述收发单元1410还用于：从所述接收端接收压缩能力信息，所述压缩能力信息用于指示所述接收端支持的N种以太压缩能力，所述N种以太压缩能力包括所述第五以太压缩能力，N为大于或等于1的整数。
在另一种可能的实现方式中，装置1400用于执行上述方法500中接收端对应的各个流程和步骤。
该收发单元1410用于：接收第五以太网数据包，所述第五以太网数据包包括第五包头，所述第五包头包括第五上下文标识，所述第五上下文标识用于标识第五上下文信息；该处理单元1420用于：根据所述第五上下文标识，获取所述第五上下文信息；该处理单元1420还用于：根据所述第五上下文信息解压缩所述第五以太网数据包。
可选地，所述收发单元1410还用于：接收上下文标识与上下文信息之间的对应关系，所述对应关系包括所述第五上下文标识和所述第五上下文标识的第五对应关系；以及，所述处理单元1420具体用于：根据所述第五上下文标识和所述第五对应关系，获取所述第五上下文信息。
可选地，所述收发单元1410还用于：接收第六以太网数据包，所述第六以太网数据包包括第六包头，所述第六包头包括所述第五上下文标识与第五上下文信息的对应关系；所述处理单元1420具体用于：根据所述第五上下文标识和所述第五对应关系，获取所述第五上下文信息。
可选地，所述第六包头还包括用于指示所述第六以太网数据包的帧格式的类型的指示信息，所述第六以太网数据包的帧格式的类型与所述第五以太网数据包的帧格式的类型相同。
可选地，所述收发单元1410还用于：发送第五反馈信息，所述第五反馈信息用于指示所述装置成功接收所述对应关系。
可选地，所述第五反馈信息包括：所述对应关系中的上下文标识。
可选地，所述收发单元1410还用于：发送第六反馈信息，所述第六反馈信息用于指示所述装置成功解压缩所述第五数据包。
可选地，所述装置为网络设备，所述发送端为终端设备；以及，所述收发单元1410还用于：
向所述发送端发送压缩配置信息，所述压缩配置信息用于指示第五以太压缩能力的参数，其中，所述第五以太网数据包是基于所述第五以太压缩能力的参数生成的。
可选地，所述收发单元1410还用于：从所述发送端接收压缩能力信息，所述压缩能力信息用于指示所述发送端支持的N种以太压缩能力，所述N种以太压缩能力包括所述第五以太压缩能力，N为大于或等于1的整数。
可选地，所述装置为终端设备，所述发送端为网络设备；以及，所述收发单元1410还用于：从所述发送端接收压缩配置信息，所述压缩配置信息用于指示第五以太压缩能力的参数，其中，所述第五以太网数据包是基于所述第五以太压缩能力的参数生成的。
可选地，所述收发单元1410还用于：从所述发送端接收压缩能力信息，所述压缩能力信息用于指示所述发送端支持的N种以太压缩能力，所述N种以太压缩能力包括所述第五以太压缩能力，N为大于或等于1的整数。
在另一种可能的实现方式中，装置1400用于执行上述方法600中终端设备对应的各个流程和步骤。
该收发单元1410用于：从网络设备接收下行控制信息DCI，所述DCI采用第一无线网络临时标识RNTI加扰，所述第一RNTI是针对以太网数据包的RNTI，所述DCI包括用于指示承载所述以太网数据包的时频资源的信息；该收发单元1410还用于：在所述DCI所指示的时频资源上从所述网络设备接收所述以太网数据包。
可选地，所述收发单元1410具体用于：在所述DCI所指示的时频资源上从所述网络设备接收系统信息块SIB，所述SIB包括所述以太网数据包。
可选地，所述第一RNTI是针对广播类型或组播类型的以太数据包的RNTI。
可选地，所述DCI包括第一信息，所述第一信息用于指示所述DCI调度的数据包为 广播类型的以太网数据包或组播类型的以太网数据包。
可选地，当所述以太数据包是广播类型的以太网数据包时，所述以太网数据包的包头中不包括广播类型的媒体介入控制MAC地址。
可选地，所述收发单元1410还用于：向所述网络设备发送与所述装置关联的媒体介入控制MAC地址。
可选地，所述收发单元1410具体用于：向所述网络设备发送非接入层NAS消息，所述NAS消息包括所述MAC地址。
可选地，所述收发单元1410还用于：从所述网络设备接收请求消息，所述请求消息用于请求与所述装置关联的所述MAC地址。
可选地，所述收发单元1410还用于：当与所述装置关联的MAC地址发生变化，向所述网络设备发送变化后的所述MAC地址。
可选地，所述收发单元1410还用于：向所述网络设备发送压缩能力信息，所述压缩能力信息用于指示所述装置支持的N种以太压缩能力，N为大于或等于1的整数；
从所述网络设备接收压缩配置信息，所述压缩配置信息用于指示第一以太压缩能力的参数，所述N种以太压缩能力包括所述第一以太压缩能力；以及，所述装置还包括：处理单元1420，用于解压缩所述以太网数据包，其中，所述以太网数据包是基于所述第一以太网压缩能力的参数生成的。
可选地，所述以太网数据包包括第一包头，所述第一包头包括第一上下文标识，所述第一上下文标识用于标识第一上下文信息；所述收发单元1410还用于：根据所述第一上下文标识，获取所述第一上下文信息；以及，所述处理单元1420具体用于：根据所述第一上下文信息，解压缩所述以太网数据包。
在另一种可能的实现方式中，装置1400用于执行上述方法600中网络设备对应的各个流程和步骤。
该收发单元1410用于：向终端设备发送下行控制信息DCI，所述DCI采用第一无线网络临时标识RNTI加扰，所述第一RNTI是针对以太网数据包的RNTI，所述DCI包括用于指示承载所述以太网数据包的时频资源的信息；该收发单元1410还用于：在所述时频资源上向所述终端设备发送所述以太网数据包。
可选地，所述收发单元1410具体用于：在所述时频资源上向所述终端设备发送系统信息块SIB，所述SIB包括所述以太网数据包。
可选地，所述第一RNTI是针对广播类型或组播类型的以太网数据包的RNTI。
可选地，所述DCI包括第一信息，所述第一信息用于指示所述DCI调度的数据包为广播类型的以太网数据包或组播类型的以太网数据包。
可选地，所述装置为接入网设备，所述接入网设备与核心网设备之间建立有公共服务质量Qos流；以及，所述收发单元1410还用于：从所述公共Qos流接收所述以太网数据包。
可选地，所述收发单元1410还用于：从所述终端设备接收与所述终端设备关联的媒体介入控制MAC地址。
可选地，所述收发单元1410具体用于：从所述终端设备接收非接入层NAS消息，所述NAS消息包括所述MAC地址。
可选地，所述收发单元1410还用于：向所述终端设备发送请求消息，所述请求消息用于请求与所述终端设备关联的所述MAC地址。
可选地，所述收发单元1410还用于：从所述终端设备接收压缩能力信息，所述压缩能力信息用于指示所述终端设备支持的N种以太压缩能力，N为大于或等于1的整数；向所述终端设备发送压缩配置信息，所述压缩配置信息用于指示第一以太压缩能力的参数，所述N种以太压缩能力包括所述第一以太压缩能力；所述装置还包括：处理单元1420，用于根据所述第一以太压缩能力的参数，生成所述以太网数据包。
可选地，所述以太网数据包包括第一包头，所述第一包头包括第一上下文标识，所述第一上下文标识用于标识第一上下文信息。
在另一种可能的实现方式中，装置1400用于执行上述方法700中终端设备对应的各个流程和步骤。
该收发单元1410用于：从网络设备接收系统信息块SIB，所述SIB包括以太网数据包；该处理单元1420用于：从所述SIB中获取所述以太数据包。
可选地，所述收发单元1410还用于：从所述网络设备接收寻呼消息，所述寻呼消息包括指示信息，所述指示信息用于指示所述SIB包括所述以太网数据包。
可选地，所述收发单元1410还用于：从所述网络设备接收下行控制信息DCI，所述DCI采用第一无线网络临时标识RNTI加扰，所述第一RNTI是针对以太网数据包的RNTI，所述DCI包括用于指示承载所述以太网数据包的时频资源的信息。
可选地，所述DCI包括第一信息，所述第一信息用于指示所述DCI调度的数据包为广播类型的以太网数据包或组播类型的以太网数据包。
可选地，当所述以太数据包是广播类型的以太网数据包时，所述以太网数据包的包头中不包括广播类型的媒体介入控制MAC地址。
可选地，所述收发单元1410还用于：向所述网络设备发送与所述装置关联的媒体介入控制MAC地址。
可选地，所述收发单元1410具体用于：向所述网络设备发送非接入层NAS消息，所述NAS消息包括所述MAC地址。
可选地，所述收发单元1410还用于：从所述网络设备接收请求消息，所述请求消息用于请求与所述装置关联的所述MAC地址。
可选地，所述收发单元1410具体用于：当与所述装置关联的MAC地址发生变化，向所述网络设备发送变化后的所述MAC地址。
可选地，所述收发单元1410还用于：向所述网络设备发送压缩能力信息，所述压缩能力信息用于指示所述装置支持的N种以太压缩能力，N为大于或等于1的整数；从所述网络设备接收压缩配置信息，所述压缩配置信息用于指示第一以太压缩能力的参数，所述N种以太压缩能力包括所述第一以太压缩能力；以及，所述处理单元1420还用于：解压缩所述以太网数据包，其中，所述以太网数据包是基于所述第一以太网压缩能力的参数生成的。
可选地，所述以太网数据包包括第一包头，所述第一包头包括第一上下文标识，所述第一上下文标识用于标识第一上下文信息；所述收发单元1410还用于：根据所述第一上下文标识，获取所述第一上下文信息；以及，所述处理单元1420具体用于：根据所述第 一上下文信息，解压缩所述以太网数据包。
在另一种可能的实现方式中，装置1400用于执行上述方法700中网络设备对应的各个流程和步骤。
该处理单元1420用于：生成系统信息块SIB，所述SIB包括以太网数据包；该收发单元1410用于：发送所述SIB。
可选地，所述收发单元1410还用于：向所述终端设备发送寻呼消息，所述寻呼消息包括指示信息，所述指示信息用于指示所述SIB包括所述以太网数据包。
可选地，所述收发单元1410还用于：向所述终端设备发送下行控制信息DCI，所述DCI采用第一无线网络临时标识RNTI加扰，所述第一RNTI是针对以太网数据包的RNTI，所述DCI包括用于指示承载所述以太网数据包的时频资源的信息。
可选地，所述DCI包括第一信息，所述第一信息用于指示所述DCI调度的数据包为广播类型的以太网数据包或组播类型的以太网数据包。
可选地，当所述以太数据包是广播类型的以太网数据包时，所述以太网数据包的包头中不包括广播类型的媒体介入控制MAC地址。
可选地，所述收发单元1410还用于：从所述终端设备接收所述终端设备关联的媒体介入控制MAC地址。
可选地，所述收发单元1410具体用于：从所述终端设备接收非接入层NAS消息，所述NAS消息包括所述MAC地址。
可选地，所述收发单元1410还用于：向所述终端设备发送请求消息，所述请求消息用于请求与所述终端设备关联的所述MAC地址。
可选地，所述收发单元1410还用于：从所述终端设备接收压缩能力信息，所述压缩能力信息用于指示所述终端设备支持的N种以太压缩能力，N为大于或等于1的整数；
向所述终端设备发送压缩配置信息，所述压缩配置信息用于指示第一以太压缩能力的参数，所述N种以太压缩能力包括所述第一以太压缩能力；所述处理单元1420还用于：根据所述第一以太压缩能力的参数，生成所述以太网数据包。
可选地，所述以太网数据包包括第一包头，所述第一包头包括第一上下文标识，所述第一上下文标识用于标识第一上下文信息。
在另一种可能的实现方式中，装置1400用于执行上述方法800中终端设备对应的各个流程和步骤。
该收发单元1410用于：从网络设备接收请求消息，所述请求消息用于请求与所述装置关联的媒体介入控制MAC地址；该收发单元1410还用于：向所述网络设备发送所述MAC地址。
可选地，所述收发单元1410具体用于：发送非接入层NAS消息，所述NAS消息包括所述MAC地址。
在另一种可能的实现方式中，装置1400用于执行上述方法800中网络设备对应的各个流程和步骤。
收发单元1410，用于向终端设备发送请求消息，所述请求消息用于请求与所述终端设备关联的媒体介入控制MAC地址；所述收发单元1410还用于：从所述终端设备接收所述MAC地址。
可选地，所述收发单元1410具体用于：从所述终端设备接收非接入层NAS消息，所述NAS消息包括所述MAC地址。
应理解，这里的装置1400以功能单元的形式体现。这里的术语“单元”可以指应用特有集成电路(application specific integrated circuit，ASIC)、电子电路、用于执行一个或多个软件或固件程序的处理器(例如共享处理器、专有处理器或组处理器等)和存储器、合并逻辑电路和/或其它支持所描述的功能的合适组件。在一个可选例子中，本领域技术人员可以理解，装置1400可以具体为上述实施例中的终端设备或网络设备(分别作为发送端或接收端)，装置1400可以用于执行上述方法实施例中与终端设备或网络设备对应的各个流程和/或步骤，为避免重复，在此不再赘述。
上述各个方案的装置1400具有实现上述方法中终端设备或网络设备(分别作为发送端或接收端)执行的相应步骤的功能；所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块；例如发送单元可以由发射机替代，接收单元可以由接收机替代，其它单元，如确定单元等可以由处理器替代，分别执行各个方法实施例中的收发操作以及相关的处理操作。
在本申请的实施例，图14中的装置也可以是芯片或者芯片系统，例如：片上系统(system on chip，SoC)。对应的，接收单元和发送单元可以是该芯片的收发电路，在此不做限定。
图15示出了本申请实施例提供的另一用于以太网数据的装置1500。该装置1500包括处理器1510、收发器1520和存储器1530。其中，处理器1510、收发器1520和存储器1530通过内部连接通路互相通信，该存储器1530用于存储指令，该处理器1510用于执行该存储器1530存储的指令，以控制该收发器1520发送信号和/或接收信号。
在一种可能的实现方式中，装置1500用于执行上述方法300中终端设备对应的各个流程和步骤。
其中，该收发器1520用于：从网络设备接收压缩配置信息，所述压缩配置信息用于指示第一以太压缩能力的参数；该处理器1510用于：根据所述第一以太压缩能力的参数，生成第一以太网数据包；所述收发器1520还用于：向所述网络设备发送所述第一以太网数据包。
在另一种可能的实现方式中，装置1500用于执行上述方法300中网络设备对应的各个流程和步骤。
该收发器1520用于：向终端设备发送压缩配置信息，所述压缩配置信息用于指示第一以太压缩能力的参数，接收第一以太网数据包，所述第一以太网数据包是基于所述第一以太网压缩能力的参数生成的；该处理器1510用于：解压缩所述第一以太网数据包。
在另一种可能的实现方式中，装置1500用于执行上述方法400中终端设备对应的各个流程和步骤。
该收发器1520用于：从网络设备接收压缩配置信息，所述压缩配置信息用于指示第三以太压缩能力的参数，从所述网络设备接收第三以太网数据包，所述第三以太网数据包是基于所述第三以太网压缩能力的参数生成的；该处理器1510用于：解压缩所述第三以太网数据包。
在另一种可能的实现方式中，装置1500用于执行上述方法400中网络设备对应的各 个流程和步骤。
该收发器1520用于：向终端设备发送压缩配置信息，所述压缩配置信息用于指示第三以太压缩能力的参数；该处理器1510用于：根据所述第三以太压缩能力的参数，生成第三以太网数据包；该收发器1520还用于：向所述终端设备发送所述第三以太网数据包。
在另一种可能的实现方式中，装置1500用于执行上述方法500中发送端对应的各个流程和步骤。
该处理器1510用于：生成第五以太网数据包，所述第五以太网数据包包括第五包头，所述第五包头包括第五上下文标识，所述第五上下文标识用于标识第五上下文信息；该收发器1520用于：向接收端发送第五以太网数据包。
在另一种可能的实现方式中，装置1500用于执行上述方法500中接收端对应的各个流程和步骤。
该收发器1520用于：接收第五以太网数据包，所述第五以太网数据包包括第五包头，所述第五包头包括第五上下文标识，所述第五上下文标识用于标识第五上下文信息；该处理器1510用于：根据所述第五上下文标识，获取所述第五上下文信息；该处理器1510还用于：根据所述第五上下文信息解压缩所述第五以太网数据包。
在另一种可能的实现方式中，装置1500用于执行上述方法600中终端设备对应的各个流程和步骤。
该收发器1520用于：从网络设备接收下行控制信息DCI，所述DCI采用第一无线网络临时标识RNTI加扰，所述第一RNTI是针对以太网数据包的RNTI，所述DCI包括用于指示承载所述以太网数据包的时频资源的信息；该收发器1520还用于：在所述DCI所指示的时频资源上从所述网络设备接收所述以太网数据包。
在另一种可能的实现方式中，装置1500用于执行上述方法600中网络设备对应的各个流程和步骤。
该收发器1520用于：向终端设备发送下行控制信息DCI，所述DCI采用第一无线网络临时标识RNTI加扰，所述第一RNTI是针对以太网数据包的RNTI，所述DCI包括用于指示承载所述以太网数据包的时频资源的信息；该收发器1520还用于：在所述时频资源上向所述终端设备发送所述以太网数据包。
在另一种可能的实现方式中，装置1500用于执行上述方法700中终端设备对应的各个流程和步骤。
该收发器1520用于：从网络设备接收系统信息块SIB，所述SIB包括以太网数据包；该处理器1510用于：从所述SIB中获取所述以太数据包。
在另一种可能的实现方式中，装置1500用于执行上述方法700中网络设备对应的各个流程和步骤。
该处理器1510用于：生成系统信息块SIB，所述SIB包括以太网数据包；该收发器1520用于：发送所述SIB。
在另一种可能的实现方式中，装置1500用于执行上述方法800中终端设备对应的各个流程和步骤。
该收发器1520用于：从网络设备接收请求消息，所述请求消息用于请求与所述装置关联的媒体介入控制MAC地址；该收发器1520还用于：向所述网络设备发送所述MAC 地址。
在另一种可能的实现方式中，装置1500用于执行上述方法800中网络设备对应的各个流程和步骤。
收发器1520，用于向终端设备发送请求消息，所述请求消息用于请求与所述终端设备关联的媒体介入控制MAC地址；所述收发器1520还用于：从所述终端设备接收所述MAC地址。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (44)

  1. 一种用于以太网数据的通信方法，其特征在于，所述方法包括：
    终端设备从网络设备接收下行控制信息DCI，所述DCI采用第一无线网络临时标识RNTI加扰，所述第一RNTI是针对以太网数据包的RNTI，所述DCI包括用于指示承载所述以太网数据包的时频资源的信息；
    所述终端设备在所述DCI所指示的时频资源上从所述网络设备接收所述以太网数据包。
  2. 根据权利要求1所述的方法，其特征在于，所述终端设备从所述网络设备接收所述以太网数据包，包括：
    所述终端设备在所述DCI所指示的时频资源上从所述网络设备接收系统信息块SIB，所述SIB包括所述以太网数据包。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一RNTI是针对广播类型或组播类型的以太数据包的RNTI。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，所述DCI包括第一信息，所述第一信息用于指示所述DCI调度的数据包为广播类型的以太网数据包或组播类型的以太网数据包。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备向所述网络设备发送与所述终端设备关联的媒体介入控制MAC地址。
  6. 根据权利要求5所述的方法，其特征在于，所述终端设备向所述网络设备发送所述MAC地址，包括：
    所述终端设备向所述网络设备发送非接入层NAS消息，所述NAS消息包括所述MAC地址。
  7. 根据权利要求5或6所述的方法，其特征在于，所述方法还包括：
    所述终端设备从所述网络设备接收请求消息，所述请求消息用于请求与所述终端设备关联的所述MAC地址。
  8. 根据权利要求5或6所述的方法，其特征在于，所述终端设备向所述网络设备发送所述MAC地址，包括：
    当与所述终端设备关联的MAC地址发生变化，则所述终端设备向所述网络设备发送变化后的所述MAC地址。
  9. 根据权利要求1至8中任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备向所述网络设备发送压缩能力信息，所述压缩能力信息用于指示所述终端设备支持的N种以太压缩能力，N为大于或等于1的整数；
    所述终端设备从所述网络设备接收压缩配置信息，所述压缩配置信息用于指示第一以太压缩能力的参数，所述N种以太压缩能力包括所述第一以太压缩能力；以及，
    所述终端设备解压缩所述以太网数据包，其中，所述以太网数据包是基于所述第一以太网压缩能力的参数生成的。
  10. 根据权利要求9所述的方法，其特征在于，所述以太网数据包包括第一包头，所 述第一包头包括第一上下文标识，所述第一上下文标识用于标识第一上下文信息；所述方法还包括：
    所述终端设备根据所述第一上下文标识，获取所述第一上下文信息；以及，
    所述终端设备解压缩所述以太网数据包，包括：
    所述终端设备根据所述第一上下文信息，解压缩所述以太网数据包。
  11. 一种用于以太网数据的通信方法，其特征在于，所述方法包括：
    网络设备向终端设备发送下行控制信息DCI，所述DCI采用第一无线网络临时标识RNTI加扰，所述第一RNTI是针对以太网数据包的RNTI，所述DCI包括用于指示承载所述以太网数据包的时频资源的信息；
    所述网络设备在所述时频资源上向所述终端设备发送所述以太网数据包。
  12. 根据权利要求11所述的方法，其特征在于，所述网络设备向所述终端设备发送所述以太网数据包，包括：
    所述网络设备在所述时频资源上向所述终端设备发送系统信息块SIB，所述SIB包括所述以太网数据包。
  13. 根据权利要求11或12所述的方法，其特征在于，所述第一RNTI是针对广播类型或组播类型的以太网数据包的RNTI。
  14. 根据权利要求11至13中任一项所述的方法，其特征在于，所述DCI包括第一信息，所述第一信息用于指示所述DCI调度的数据包为广播类型的以太网数据包或组播类型的以太网数据包。
  15. 根据权利要求11至14中任一项所述的方法，其特征在于，所述网络设备为接入网设备，所述接入网设备与核心网设备之间建立有公共服务质量Qos流；以及，
    所述方法还包括：
    所述网络设备从所述公共Qos流接收所述以太网数据包。
  16. 根据权利要求11至15中任一项所述的方法，其特征在于，所述方法还包括：
    所述网络设备从所述终端设备接收与所述终端设备关联的媒体介入控制MAC地址。
  17. 根据权利要求16所述的方法，其特征在于，所述网络设备从所述终端设备接收所述MAC地址，包括：
    所述网络设备从所述终端设备接收非接入层NAS消息，所述NAS消息包括所述MAC地址。
  18. 根据权利要求16或17所述的方法，其特征在于，所述方法还包括：
    所述网络设备向所述终端设备发送请求消息，所述请求消息用于请求与所述终端设备关联的所述MAC地址。
  19. 根据权利要求11至18中任一项所述的方法，其特征在于，所述方法还包括：
    所述网络设备从所述终端设备接收压缩能力信息，所述压缩能力信息用于指示所述终端设备支持的N种以太压缩能力，N为大于或等于1的整数；
    所述网络设备向所述终端设备发送压缩配置信息，所述压缩配置信息用于指示第一以太压缩能力的参数，所述N种以太压缩能力包括所述第一以太压缩能力；
    所述网络设备根据所述第一以太压缩能力的参数，生成所述以太网数据包。
  20. 根据权利要求19所述的方法，其特征在于，所述以太网数据包包括第一包头， 所述第一包头包括第一上下文标识，所述第一上下文标识用于标识第一上下文信息。
  21. 一种用于以太网数据的装置，其特征在于，所述装置包括：
    收发单元，用于从网络设备接收下行控制信息DCI，所述DCI采用第一无线网络临时标识RNTI加扰，所述第一RNTI是针对以太网数据包的RNTI，所述DCI包括用于指示承载所述以太网数据包的时频资源的信息；
    所述收发单元还用于：在所述DCI所指示的时频资源上从所述网络设备接收所述以太网数据包。
  22. 根据权利要求21所述的装置，其特征在于，所述收发单元具体用于：
    在所述DCI所指示的时频资源上从所述网络设备接收系统信息块SIB，所述SIB包括所述以太网数据包。
  23. 根据权利要求21或22所述的装置，其特征在于，所述第一RNTI是针对广播类型或组播类型的以太数据包的RNTI。
  24. 根据权利要求21至23中任一项所述的装置，其特征在于，所述DCI包括第一信息，所述第一信息用于指示所述DCI调度的数据包为广播类型的以太网数据包或组播类型的以太网数据包。
  25. 根据权利要求21至24中任一项所述的装置，其特征在于，所述收发单元还用于：
    向所述网络设备发送与所述装置关联的媒体介入控制MAC地址。
  26. 根据权利要求25所述的装置，其特征在于，所述收发单元具体用于：
    向所述网络设备发送非接入层NAS消息，所述NAS消息包括所述MAC地址。
  27. 根据权利要求25或26所述的装置，其特征在于，所述收发单元还用于：
    从所述网络设备接收请求消息，所述请求消息用于请求与所述装置关联的所述MAC地址。
  28. 根据权利要求25或26所述的装置，其特征在于，所述收发单元还用于：
    当与所述装置关联的MAC地址发生变化，向所述网络设备发送变化后的所述MAC地址。
  29. 根据权利要求21至28中任一项所述的装置，其特征在于，所述收发单元还用于：
    向所述网络设备发送压缩能力信息，所述压缩能力信息用于指示所述装置支持的N种以太压缩能力，N为大于或等于1的整数；
    从所述网络设备接收压缩配置信息，所述压缩配置信息用于指示第一以太压缩能力的参数，所述N种以太压缩能力包括所述第一以太压缩能力；以及，
    所述装置还包括：
    处理单元，用于解压缩所述以太网数据包，其中，所述以太网数据包是基于所述第一以太网压缩能力的参数生成的。
  30. 根据权利要求29所述的装置，其特征在于，所述以太网数据包包括第一包头，所述第一包头包括第一上下文标识，所述第一上下文标识用于标识第一上下文信息；所述收发单元还用于：
    根据所述第一上下文标识，获取所述第一上下文信息；以及，
    所述处理单元具体用于：
    根据所述第一上下文信息，解压缩所述以太网数据包。
  31. 一种用于以太网数据的装置，其特征在于，所述装置包括：
    收发单元，用于向终端设备发送下行控制信息DCI，所述DCI采用第一无线网络临时标识RNTI加扰，所述第一RNTI是针对以太网数据包的RNTI，所述DCI包括用于指示承载所述以太网数据包的时频资源的信息；
    所述收发单元还用于：在所述时频资源上向所述终端设备发送所述以太网数据包。
  32. 根据权利要求31所述的装置，其特征在于，所述收发单元具体用于：
    在所述时频资源上向所述终端设备发送系统信息块SIB，所述SIB包括所述以太网数据包。
  33. 根据权利要求31或32所述的装置，其特征在于，所述第一RNTI是针对广播类型或组播类型的以太网数据包的RNTI。
  34. 根据权利要求31至33中任一项所述的装置，其特征在于，所述DCI包括第一信息，
    所述第一信息用于指示所述DCI调度的数据包为广播类型的以太网数据包或组播类型的以太网数据包。
  35. 根据权利要求31至34中任一项所述的装置，其特征在于，所述装置为接入网设备，所述接入网设备与核心网设备之间建立有公共服务质量Qos流；以及，所述收发单元还用于：
    从所述公共Qos流接收所述以太网数据包。
  36. 根据权利要求31至35中任一项所述的装置，其特征在于，所述收发单元还用于：
    从所述终端设备接收与所述终端设备关联的媒体介入控制MAC地址。
  37. 根据权利要求36所述的装置，其特征在于，所述收发单元具体用于：
    从所述终端设备接收非接入层NAS消息，所述NAS消息包括所述MAC地址。
  38. 根据权利要求36或37所述的装置，其特征在于，所述收发单元还用于：
    向所述终端设备发送请求消息，所述请求消息用于请求与所述终端设备关联的所述MAC地址。
  39. 根据权利要求31至38中任一项所述的装置，其特征在于，所述收发单元还用于：
    从所述终端设备接收压缩能力信息，所述压缩能力信息用于指示所述终端设备支持的N种以太压缩能力，N为大于或等于1的整数；
    向所述终端设备发送压缩配置信息，所述压缩配置信息用于指示第一以太压缩能力的参数，所述N种以太压缩能力包括所述第一以太压缩能力；
    所述装置还包括：
    处理单元，用于根据所述第一以太压缩能力的参数，生成所述以太网数据包。
  40. 根据权利要求39所述的装置，其特征在于，所述以太网数据包包括第一包头，所述第一包头包括第一上下文标识，所述第一上下文标识用于标识第一上下文信息。
  41. 一种用于以太网数据的装置，其特征在于，包括处理器，用于从存储器中调用并运行所述存储器中存储的指令，使得所述装置执行如权利要求1至10任一项所述的方法。
  42. 一种用于以太网数据的装置，其特征在于，包括处理器，用于从存储器中调用并运行所述存储器中存储的指令，使得所述装置执行如权利要求11至20任一项所述的方法。
  43. 一种计算机存储介质，用于存储程序，该程序被处理器调用时，如权利要求1至 10任一项所述的方法被执行。
  44. 一种计算机存储介质，用于存储程序，该程序被处理器调用时，如权利要求11至20中任一项所述的方法被执行。
PCT/CN2019/108019 2018-09-28 2019-09-26 用于以太网数据的通信方法和装置 WO2020063709A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP19868002.7A EP3849148B1 (en) 2018-09-28 2019-09-26 Communication method and apparatus for ethernet data
JP2021516888A JP7210710B2 (ja) 2018-09-28 2019-09-26 イーサネット（登録商標）データの通信方法及び装置
CA3114267A CA3114267A1 (en) 2018-09-28 2019-09-26 Communication method and apparatus for ethernet data
US17/213,970 US20210219173A1 (en) 2018-09-28 2021-03-26 Communication Method and Apparatus for Ethernet Data

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811142736.7A CN110972282B (zh) 2018-09-28 2018-09-28 用于以太网数据的通信方法和装置
CN201811142736.7 2018-09-28

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/213,970 Continuation US20210219173A1 (en) 2018-09-28 2021-03-26 Communication Method and Apparatus for Ethernet Data

Publications (1)

Publication Number Publication Date
WO2020063709A1 true WO2020063709A1 (zh) 2020-04-02

Family

ID=69949847

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/108019 WO2020063709A1 (zh) 2018-09-28 2019-09-26 用于以太网数据的通信方法和装置

Country Status (6)

Country Link
US (1) US20210219173A1 (zh)
EP (1) EP3849148B1 (zh)
JP (1) JP7210710B2 (zh)
CN (1) CN110972282B (zh)
CA (1) CA3114267A1 (zh)
WO (1) WO2020063709A1 (zh)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020077543A1 (zh) * 2018-10-16 2020-04-23 Oppo广东移动通信有限公司 一种处理帧头的方法及装置、通信设备
WO2020155115A1 (zh) * 2019-02-01 2020-08-06 Oppo广东移动通信有限公司 一种头压缩的处理方法及装置、通信设备
JP6926158B2 (ja) * 2019-08-09 2021-08-25 シャープ株式会社 端末装置、基地局装置、および通信方法
WO2021253432A1 (zh) * 2020-06-19 2021-12-23 Oppo广东移动通信有限公司 无线通信方法、压缩端和解压缩端
WO2022027691A1 (zh) * 2020-08-07 2022-02-10 华为技术有限公司 一种通信方法及装置
CN117082565A (zh) * 2022-05-09 2023-11-17 维沃移动通信有限公司 数据传输方法、信息发送方法、终端及网络侧设备

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015142469A2 (en) * 2014-03-20 2015-09-24 Intel IP Corporation Methods, systems, and devices for modulation and coding scheme signaling for common control channel
WO2016145371A2 (en) * 2015-03-11 2016-09-15 Phluido, Inc. Distributed radio access network with adaptive fronthaul

Family Cites Families (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9094943B2 (en) 2008-09-19 2015-07-28 Qualcomm Incorporated Network and mobile device initiated quality of service
US8867355B2 (en) * 2009-07-14 2014-10-21 Broadcom Corporation MoCA multicast handling
CN102647768B (zh) * 2011-02-18 2014-06-18 电信科学技术研究院 基于lte-lan的报文转发方法及装置
US20130039291A1 (en) * 2011-08-12 2013-02-14 Research In Motion Limited Design on Enhanced Control Channel for Wireless System
CN103634882A (zh) * 2012-08-27 2014-03-12 电信科学技术研究院 一种无线网络临时标识的传输方法和设备
WO2014110773A1 (zh) * 2013-01-17 2014-07-24 华为技术有限公司 一种数据包处理方法和装置
GB2510358A (en) * 2013-01-31 2014-08-06 Eip Configuring layer 2 data compression between a UE and base station in LTE.
US9622233B1 (en) * 2014-06-16 2017-04-11 Sprint Spectrum L.P. Dynamic use of orthogonal coding to manage control channel capacity
CN104079488B (zh) * 2014-07-22 2017-03-29 武汉虹信通信技术有限责任公司 基于以太网二层头压缩的传输设备及方法
US10219310B2 (en) 2014-12-12 2019-02-26 Alcatel Lucent WiFi boost with LTE IP anchor
WO2016105568A1 (en) * 2014-12-23 2016-06-30 Interdigital Patent Holdings, Inc. Methods for wifi integration in cellular systems
WO2016152912A1 (ja) 2015-03-26 2016-09-29 株式会社Ｎｔｔドコモ 通信システムおよび通信方法
US9979557B2 (en) * 2015-08-10 2018-05-22 Hughes Network Systems, Llc Carrier grade Ethernet layer 2 over layer 3 satellite backbones (L2oL3SB)
JP6776243B2 (ja) * 2015-08-11 2020-10-28 京セラ株式会社 通信方法、基地局及び無線端末
TWI751147B (zh) * 2016-03-30 2022-01-01 美商內數位專利控股公司 無線傳輸/接收單元及其執行方法
CN107426785A (zh) 2016-05-23 2017-12-01 中国移动通信有限公司研究院 一种数据传输方法及装置
CN106358317B (zh) * 2016-09-21 2019-07-09 深圳震有科技股份有限公司 一种实现lte空中接口组播的方法和系统
US11191007B2 (en) * 2016-09-28 2021-11-30 Idac Holdings, Inc. Methods and systems for beamformed system information transmission
EP3599789B1 (en) 2017-03-22 2024-02-14 Sony Group Corporation Terminal device, base station device, communication method, and storage medium
US10855814B2 (en) * 2017-10-20 2020-12-01 Comcast Cable Communications, Llc Non-access stratum capability information
US11863983B2 (en) * 2018-08-20 2024-01-02 Apple Inc. Provisioning of VLAN IDs in 5G systems

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015142469A2 (en) * 2014-03-20 2015-09-24 Intel IP Corporation Methods, systems, and devices for modulation and coding scheme signaling for common control channel
WO2016145371A2 (en) * 2015-03-11 2016-09-15 Phluido, Inc. Distributed radio access network with adaptive fronthaul

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
See also references of EP3849148A4
VIVO: "Ll impacts on DL/UL intra-UE prioritization/multiplexing", 3GPP TSG RAN MEETING #81, RP-181660, 13 September 2018 (2018-09-13), XP051512940 *
ZTE: "Clarification of NRS presence", 3GPP TSG RAN WG1 MEETING #88BIS, RL-1705482, 7 April 2017 (2017-04-07), XP051250938 *

Also Published As

Publication number Publication date
JP7210710B2 (ja) 2023-01-23
CN110972282A (zh) 2020-04-07
EP3849148A4 (en) 2021-10-27
US20210219173A1 (en) 2021-07-15
CA3114267A1 (en) 2020-04-02
JP2022501921A (ja) 2022-01-06
CN110972282B (zh) 2022-05-24
EP3849148B1 (en) 2024-08-21
EP3849148A1 (en) 2021-07-14

Similar Documents

Publication Publication Date Title
WO2020063707A1 (zh) 用于以太网数据的通信方法和装置
WO2020063709A1 (zh) 用于以太网数据的通信方法和装置
EP3852403A1 (en) Communication method and apparatus
JP5904347B2 (ja) データ通信方法、装置、およびシステム
RU2767321C1 (ru) Способ и устройство для беспроводной связи
WO2014026370A1 (zh) 数据传输方法及装置
WO2022205234A1 (zh) 一种通信方法及装置
EP3860075B1 (en) Ethernet frame header compression processing method, device and chip and computer program
WO2021244356A1 (zh) 数据传输方法及装置
WO2021087923A1 (zh) 一种传输信息的方法和装置
WO2012110004A1 (zh) 基于lte-lan的报文转发方法及装置
WO2023015420A1 (zh) 数据传输方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19868002

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 3114267

Country of ref document: CA

Ref document number: 2021516888

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019868002

Country of ref document: EP

Effective date: 20210406