Method and apparatus for wireless communication

Abstract

Ethernet Header Compression (EHC) is implemented for use with data sent within a non-access stratum (NAS) control plane of a wireless communication network. In one aspect, a wireless communication device sends a signal to the wireless communication network indicating that the wireless communication device supports EHC for data transmission on the control plane. The device obtains a response from the wireless communication network indicating that the wireless communication network supports EHC for data transmission on the control plane. The device then sends an Ethernet packet to the wireless communication network on the control plane using EHC. The wireless communication device can be configured to send a request to the wireless communication network to use EHC before sending an Ethernet packet compressed using EHC. Only when the request is authorized does the device send a compressed Ethernet packet. In another aspect, a complementary EHC feature is provided within a network component of the wireless communication network.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority based on the following applications: non-provisional application serial number 17 / 215,542 filed with the United States Patent and Trademark Office on March 29, 2021, and provisional patent application serial number 63 / 004,326 filed with the United States Patent and Trademark Office on April 2, 2020, which are assigned to the assignee of this application and are incorporated herein by reference as if fully set forth below and for all applicable purposes. Technical Field

[0003] Generally speaking, the technology discussed herein relates to wireless communication networks, and more specifically, to Ethernet header compression. Background Art

[0004] Wireless communication networks are widely deployed to provide various wireless communication services, such as telephony, video, data, messaging, broadcast, etc. Some wireless communication networks provide transmission of Ethernet data packets. Ethernet header compression (EHC) is a process that reduces the size of many Ethernet packets by compressing or suppressing the header portion of the packet. Summary of the invention

[0005] A brief summary of one or more aspects of the present disclosure is provided below to provide a basic understanding of these aspects. This summary is not an exhaustive review of all expected features of the present disclosure, and is neither intended to identify the key or important elements of all aspects of the present disclosure, nor is it intended to describe the scope of any or all aspects of the present disclosure. Its sole purpose is to provide some concepts of one or more aspects of the present disclosure in a simplified form as a preface to a more detailed description provided later.

[0006] In one aspect of the present disclosure, a wireless communication device is provided, comprising: a transceiver; and a processor coupled to the transceiver, wherein the processor is configured to: send a signal to a wireless communication network indicating that the wireless communication device supports Ethernet Header Compression (EHC) for data transmission on a control plane; obtain a response from the wireless communication network indicating that the wireless communication network supports EHC for data transmission on the control plane; and communicate with the wireless communication network on the control plane using the EHC.

[0007] In another aspect of the present disclosure, a method for wireless communication used by a wireless communication device is provided. The method includes: sending a signal to a wireless communication network indicating that the wireless communication device supports EHC for data transmission on a control plane; obtaining a response from the wireless communication network indicating that the wireless communication network supports EHC for data transmission on the control plane; and communicating with the wireless communication network on the control plane using EHC.

[0008] In another aspect of the present disclosure, a network component of a wireless communication network is provided. The network component includes: a network interface; and a processor coupled to the network interface, wherein the processor is configured to: obtain a signal from a wireless communication device indicating that the wireless communication device supports an EHC for data transmission on a control plane; send a response to the wireless communication device indicating that the wireless communication network supports the EHC for data transmission on the control plane; and communicate with the wireless communication device on the control plane using the EHC.

[0009] In another aspect of the present disclosure, a method for wireless communication used by a network component of a wireless communication network is provided. The method includes: obtaining a signal from a wireless communication device indicating that the wireless communication device supports an EHC for data transmission on a control plane; sending a response to the wireless communication device indicating that the wireless communication network supports the EHC for data transmission on the control plane; and communicating with the wireless communication device on the control plane using the EHC. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 is a diagram illustrating an exemplary wireless communication network.

[0011] Figure 2 is a diagram illustrating exemplary protocol stacks for user plane and control plane of various devices of a wireless communication network.

[0012] Figure 3 is a diagram illustrating an example of a network architecture including selected non-access stratum (NAS) control plane components.

[0013] Figure 4 is a diagram showing an example of communication using a protocol data unit (PDU) session.

[0014] Figure 5 is a flow chart of an exemplary method performed by a user equipment (UE) for negotiating with components of a core network to use EHC for data transmission on a NAS control plane.

[0015] Figure 6is a flow chart of an example method performed by a network component in communication with a UE to enable and perform EHC for data transmission over a NAS control plane.

[0016] Figure 7 is a signaling diagram illustrating exemplary signaling for enabling and performing data transfer with EHC on a NAS control plane.

[0017] Figure 8 Included are data format diagrams showing exemplary formats for 5G mobility management information elements (IEs) and 5G session management IEs.

[0018] Fig. 9 A data format diagram is included showing an exemplary format for an Ethernet packet having an Ethernet header and having the Ethernet header suppressed using EHC.

[0019] Fig.10 is a block diagram illustrating an example of a hardware implementation for a NAS core network node employing a processing system.

[0020] Fig.11 is a block diagram illustrating an example of a hardware implementation for a UE employing a processing system.

[0021] Fig.12 is a flow chart of an exemplary method used by a network component of a wireless communication network for use with control plane data transmission utilizing an EHC.

[0022] Fig.13 is a flow chart of an exemplary method for use by a wireless communication device of a wireless communication network for use with control plane data transmission utilizing an EHC.

[0023] Fig.14 is a block diagram illustrating an example of a network component of a wireless communication network having a processor configured to perform certain functions related to control plane data transmission utilizing an EHC.

[0024] Fig.15 is a block diagram illustrating an example of a wireless communication device of a wireless communication network having a processor configured to perform certain functions related to control plane data transmission utilizing an EHC.

[0025] Fig.16 is a block diagram illustrating an example of a core network of a wireless communication network having various components configured to perform or control certain functions related to control plane data transmission utilizing an EHC.

[0026] Fig.17is a block diagram illustrating an example of a wireless communication device of a wireless communication network having various components configured to perform or control certain functions related to control plane data transmission utilizing an EHC.

[0027] Fig.18 is a flow chart of an exemplary method for use by a wireless communication device of a wireless communication network.

[0028] Fig.19 is a flow chart of another exemplary method for use by a wireless communication device of a wireless communication network.

[0029] Fig. 20 is a flow chart of an exemplary method for use by a network component of a wireless communication network.

[0030] Fig.21 is a flow chart of another exemplary method for use by a network component of a wireless communication network.

[0031] Fig. 22 is a block diagram illustrating an example of a hardware implementation of network components of a wireless communication network.

[0032] Fig.23 is a block diagram illustrating an example of a hardware implementation for a wireless communication device. DETAILED DESCRIPTION

[0033] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations, and is not intended to represent the only configuration in which the concepts described herein may be implemented. For the purpose of providing a thorough understanding of various aspects, the detailed description includes specific details. However, it will be apparent to those skilled in the art that these concepts may be implemented without these specific details. In some instances, well-known structures and components are shown in the form of block diagrams in order to avoid blurring such concepts. Within the scope of the present disclosure, some or all of the features shown may be omitted in a particular implementation, and some of the features shown may not be required for the implementation of all embodiments.

[0034] Although various aspects and embodiments are described in this application by the description of some examples, it will be understood by those skilled in the art that additional implementations and use cases may be generated in many different arrangements and scenarios. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, embodiments and / or uses can be generated via integrated chip embodiments and other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial devices, retail / purchase devices, medical devices, devices that enable artificial intelligence (AI), etc.). Although some examples may or may not be specifically for use cases or applications, there may be a variety of applicable scopes for the described innovations. Implementations may have a range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some actual settings, the devices incorporating the described aspects and features may also necessarily include additional components and features for the implementation and implementation of the claimed and described embodiments. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The innovations described herein are intended to be implemented in a variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc., having different sizes, shapes, and configurations.

[0035] Various aspects of the present disclosure provide various apparatuses, methods, and systems for implementing Ethernet Header Compression (EHC) for use with Ethernet data packets sent via a control plane of a wireless communication network. Control plane Ethernet data packets may be sent, for example, by a user equipment (UE) handset or other mobile device. In this regard, the UE may be configured to request or otherwise negotiate with a network component of the wireless communication network to use EHC for data sent via the control plane. Assuming that the network component allows the use of EHC for Ethernet data packets sent via the control plane, the UE may send data within the Ethernet data packet on the control plane while using EHC to reduce the amount of data to be sent. This may be used to reduce data transmission latency or achieve other goals.

[0036] In an illustrative example, the UE notifies the wireless communication network that the UE supports EHC for data transmission on the control plane, and then receives a response from the wireless communication network indicating that the wireless communication network also supports EHC for data transmission on the control plane. The UE then sends a signal to the wireless communication network to request the use of EHC for data transmission on the control plane. Only if the request is authorized does the UE send compressed Ethernet packets on the control plane. Therefore, in some examples, a two-stage process is provided in which the UE first determines whether the wireless communication network supports EHC for data transmission on the control plane, and if the EHC feature is supported, the UE then requests the use of the EHC feature before actually sending any compressed Ethernet packets with data on the control plane.

[0037] In another example, a complementary EHC feature or function is provided within a network component of a wireless communication network. For example, the network component receives a notification from a UE that the UE supports EHC for data transmission on a control plane, and sends a response to the UE indicating that the wireless communication network also supports EHC for data transmission on the control plane. The network component then receives a signal from the UE requesting that the EHC be used for data transmission on the control plane. The network component authorizes the use, and then receives an Ethernet packet with a compressed header from the UE on the control plane. The network component may also send an Ethernet packet with a compressed header to the UE on the control plane. In some examples, the network component may include a mobility management function (AMF) and one or more session management functions (SMFs). Among other functions, the AMF selects a specific SMF, which then selects the field length of a context identification (ID) field for use with the EHC for a protocol data unit (PDU) session for a specific Ethernet stream.

[0038] In the illustrative examples herein, the wireless communication network is configured according to the 3rd Generation Partnership Project (3GPP) New Radio (NR) specification, which is generally referred to as 5G. The ability to transmit data on the control plane of the 5G network may also be referred to as control plane Internet of Things (IoT) optimization or cellular Internet of Things (CIoT) optimization, but it is not limited to use with IoT devices and is applicable to a wide variety of UEs or other wireless communication devices.

[0039] Before discussing EHC in more detail, an overview of a wireless communication system in which one of multiple UEs may be used is provided. The various concepts presented throughout the present disclosure may be implemented across various telecommunication systems, network architectures, and communication standards. Referring now to the figure, a schematic diagram of a radio access network (RAN) 100 is provided as a non-limiting illustrative example. RAN 100 may implement any suitable one or more radio access technologies (RAN) to provide radio access to UEs. As an example, RAN 100 may operate according to the 3GPP NR specification commonly referred to as 5G. As another example, RAN 100 may operate under a mix of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) (which is commonly referred to as LTE) standards. 3GPP refers to this hybrid RAN as the next generation RAN or NG-RAN. In another example, RAN 100 may operate according to both LTE and 5G NR standards. Of course, many other examples may be utilized within the scope of the present disclosure.

[0040] The geographic area covered by the RAN 100 may be divided into multiple cellular areas (cells), which may be uniquely identified by a UE based on an identity broadcast from an access point or base station over the geographic area. Figure 1 Macro cells 102, 104, and 106, and small cells 108 are shown, each of which may include one or more sectors (not shown). A sector is a sub-area of ​​a cell. All sectors within a cell are served by the same base station. A radio link within a sector may be identified by a single logical identifier belonging to the sector. In a cell divided into sectors, multiple sectors within a cell may be formed by antenna groups, where each antenna is responsible for communicating with a UE in a portion of the cell.

[0041] Typically, a corresponding base station (BS) serves each cell. Broadly speaking, a base station is a network element in the RAN that is responsible for radio transmission and reception to or from UEs in one or more cells. A BS may also be referred to by those skilled in the art as a base transceiver station (BTS), a wireless base station, a wireless transceiver, a transceiver functional unit, a basic service set (BSS), an extended service set (ESS), an access point (AP), a Node B (NB), an evolved Node B (eNB), a gNodeB (gNB), or some other appropriate term.

[0042] exist Figure 1In the example, two base stations 110 and 112 are shown in cells 102 and 104; and a third base station 114 is shown as controlling a remote radio head (RRH) 116 in a cell 106. That is, the base station may have an integrated antenna, or may be connected to an antenna or RRH via a feeder cable. In the example shown, cells 102, 104, and 106 may be referred to as macro cells, because base stations 110, 112, and 114 support cells with large sizes. In addition, base station 118 is shown in a small cell 108 (e.g., a micro cell, a micro cell, a femto cell, a home base station, a home node B, a home evolved node B, etc.), which may overlap with one or more macro cells. In this example, cell 108 may be referred to as a small cell, because base station 118 supports a cell with a relatively small size. Cell size setting may be done based on system design and component constraints. It is to be understood that RAN 100 may include any number of wireless base stations and cells. In addition, relay nodes may be deployed to extend the size or coverage area of ​​a given cell. Base stations 110, 112, 114, 118 provide wireless access points to the core network for any number of mobile devices.

[0043] Figure 1 Also included is a quadcopter or drone 120 that can be configured to act as a base station. That is, in some examples, the cell may not necessarily be stationary, and the geographic area of ​​the cell may move depending on the location of a mobile base station (such as a quadcopter 120).

[0044] Typically, a base station may include a backhaul interface for communicating with a backhaul portion of a network (not shown). The backhaul may provide a link between the base station and a core network (not shown), and in some examples, the backhaul may provide interconnection between respective base stations. The core network may be part of a wireless communication system and may be independent of the RAN used in a radio access network. Various types of backhaul interfaces may be employed, such as a direct physical connection, a virtual network, or a similar interface using any appropriate transport network.

[0045] The RAN 100 is shown as supporting wireless communications for multiple mobile devices. Mobile devices are generally referred to as UEs in the standards and specifications published by 3GPP, but may also be referred to as mobile stations (MS), user stations, mobile units, user units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile user stations, access terminals (ATs), mobile terminals, wireless terminals, remote terminals, handsets, terminals, user agents, mobile clients, clients, or some other appropriate terminology by those skilled in the art. A UE may be a device that provides access to network services to a user. In an example where the RAN 100 operates according to both LTE and 5G NR standards, the UE may be an eUTRAN dual-connectivity (EN-DC) UE that is capable of simultaneously connecting to an LTE base station and an NR base station to receive data packets from both the LTE base station and the NR base station.

[0046] In this document, a "mobile" device does not necessarily need to have the ability to move, but can be stationary. The term mobile device or mobile device refers broadly to a wide variety of devices and technologies. A UE may include multiple hardware structural components that are sized, shaped, and arranged to facilitate communication; these components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc. that are electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile stations, cellular phones (mobile phones), smart phones, session initiation protocol (SIP) phones, laptops, personal computers (PCs), notebooks, netbooks, smartbooks, tablet devices, personal digital assistants (PDAs), and various embedded systems (e.g., corresponding to IoT). A mobile device may also be a car or other means of transportation, a remote sensor or actuator, a robot or robotic device, a satellite radio unit, a global positioning system (GPS) device, a target tracking device, a drone, a multi-wing aircraft, a quadcopter, a remote control device, a consumer device and / or a wearable device (e.g., glasses, wearable cameras, virtual reality devices, smart watches, health or fitness trackers), digital audio players (e.g., MP3 players), cameras, game consoles, and the like. The mobile device may also be a digital home or smart home device, such as home audio, video and / or multimedia equipment, appliances, vending machines, smart lighting, home security systems, smart meters, and the like. The mobile device may also be a smart energy device, a security device, a solar panel or solar array, municipal infrastructure equipment that controls electricity (e.g., smart grid), lighting, water, etc.; industrial automation and enterprise equipment; logistics controllers; agricultural equipment; military defense equipment, vehicles, aircraft, ships and weapons, and the like. In addition, the mobile device may provide connected medicine or remote medical support (e.g., health care at a distance). Telemedicine devices may include telemedicine monitoring devices and telemedicine management devices, whose communications may be given priority processing or priority access compared to other types of information, for example, in terms of priority access for the transmission of critical service data, and / or in terms of the associated QoS for the transmission of critical service data.

[0047] Within RAN 100, cells may include UEs that may communicate with one or more sectors of each cell. For example, UEs 122 and 124 may communicate with base station 110; UEs 126 and 128 may communicate with base station 112; UEs 130 and 132 may communicate with base station 114 via RRH 116; UE 134 may communicate with base station 118; and UE 136 may communicate with mobile base station 120. Here, each base station 110, 112, 114, 118, and 120 may be configured to provide an access point to a core network (not shown) for all UEs in the corresponding cell.

[0048] In another example, a mobile network node (e.g., quadcopter 120) can be configured to function as a UE. For example, quadcopter 120 can operate within cell 102 by communicating with base station 110. In some aspects of the present disclosure, two or more UEs (e.g., UE 126 and UE 128) can communicate with each other using peer-to-peer (P2P) or sidelink signals 127 without relaying the communication through a base station (e.g., base station 112).

[0049] Wireless communication between RAN 100 and UE (e.g., UE 122 or 124) can be described as utilizing an air interface. Transmissions from a base station (e.g., base station 110) to one or more UEs (e.g., UE 122 or 124) over the air interface can be referred to as downlink (DL) transmissions. According to certain aspects of the present disclosure, the term downlink can refer to point-to-multipoint transmissions at a network node originating from a scheduling entity (further described below; e.g., base station 110). Another way to describe the scheme can be to use the term broadcast channel multiplexing. Transmissions from a UE (e.g., UE 122) to a base station (e.g., base station 110) can be referred to as uplink (UL) transmissions. According to further aspects of the present disclosure, the term uplink can refer to point-to-point transmissions originating from a scheduled entity (e.g., UE 122).

[0050] For example, DL transmissions may include unicast or broadcast transmissions of control information and / or traffic information (e.g., user data traffic) from a base station (e.g., base station 110) to one or more UEs (e.g., UEs 122 and 124), while UL transmissions may include transmissions of control information and / or traffic information originating from a UE (e.g., UE 122). In addition, uplink and / or downlink control information and / or traffic information may be time-divided into frames, subframes, time slots, and / or symbols. As used herein, a symbol may refer to a time unit in which each carrier in an orthogonal frequency division multiplexing (OFDM) waveform carries one resource element (RE). A time slot may carry 7 or 14 OFDM symbols. A subframe may refer to a duration of 1 ms. Multiple subframes or time slots may be grouped together to form a single frame or radio frame. Of course, these definitions are not required, and any appropriate scheme for organizing waveforms may be utilized, and the various time divisions of waveforms may have any appropriate duration.

[0051] The air interface in the RAN 100 may utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication of various devices. For example, the 5G NR specification provides multiple access for UL or reverse link transmissions from UEs 122 and 124 to base station 110, and multiplexing of DL or forward link transmissions from base station 110 to UEs 122 and 124 using OFDM with a cyclic prefix. In addition, for UL transmissions, the 5G NR specification provides support for discrete Fourier transform spread OFDM (DFT-s-OFDM) with a cyclic prefix (CP) (also known as single carrier FDMA (SC-FDMA)). However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes, and may be provided using time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource extension multiple access (RSMA), or other appropriate multiple access schemes. Furthermore, multiplexing of DL transmissions from base station 110 to UEs 122 and 124 may be provided using time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), OFDM, sparse code multiplexing (SCM), or other suitable multiplexing schemes.

[0052] Further, the air interface in RAN 100 can also use one or more duplex algorithms. Duplex refers to a point-to-point communication link, in which two endpoints can communicate with each other in two directions. Full-duplex means that two endpoints can communicate with each other at the same time. Half-duplex means that at a certain time, only one endpoint can send information to the other endpoint. In a wireless link, a full-duplex channel usually relies on the physical isolation of the transmitter and the receiver and suitable interference elimination techniques. Full-duplex simulation is frequently implemented for wireless links by using frequency division duplex (FDD) or time division duplex (TDD). In FDD, transmissions in different directions operate at different carrier frequencies. In TDD, transmissions in different directions on a given channel are separated from each other using time division multiplexing. That is, at some times, the channel is dedicated to transmission in one direction, and at other times, the channel is dedicated to transmission in another direction, wherein the direction can change very quickly (e.g., several times per time slot).

[0053] In the RAN 100, the ability of a UE to communicate while moving (independent of its location) is referred to as mobility. Various physical channels between the UE and the RAN are typically established, maintained, and released under the control of an access and mobility management function (AMF), which may include a security context management function (SCMF) that manages security contexts for both control plane and user plane functions and a security anchor function (SEAF) that performs authentication. In various aspects of the present disclosure, the RAN 100 may utilize DL-based mobility or UL-based mobility to implement mobility and switching (i.e., the UE's connection is switched from one radio channel to another). In a network configured for DL-based mobility, during a call with a scheduling entity, or at any other time, the UE may monitor various parameters of the signal from its serving cell and various parameters of neighboring cells. Based on the quality of these parameters, the UE may maintain communication with one or more of the neighboring cells. During this time, if the UE moves from one cell to another, or if the signal quality from a neighboring cell exceeds the signal quality from the serving cell for a given amount of time, the UE may perform a switch or handover from the serving cell to the neighboring (target) cell. For example, UE 124 may move from a geographic area corresponding to its serving cell 102 to a geographic area corresponding to a neighbor cell 106. When the signal strength or quality from neighbor cell 106 exceeds the signal strength or quality of its serving cell 102 for a given amount of time, UE 124 may send a report message indicating this condition to its serving base station 110. In response, UE 124 may receive a handover command, and the UE may perform a handover to cell 106.

[0054] In a network configured for UL-based mobility, the network may utilize a UL reference signal from each UE to select a serving cell for each UE. In some examples, base stations 110, 112, and 114 / 116 may broadcast unified synchronization signals (e.g., a unified primary synchronization signal (PSS), a unified secondary synchronization signal (SSS), and a unified physical broadcast channel (PBCH)). UEs 122, 124, 126, 128, 130, and 132 may receive these unified synchronization signals, derive carrier frequency and subframe / time slot timing based on these synchronization signals, and send an uplink pilot or reference signal in response to the derived timing. The uplink pilot signal sent by a UE (e.g., UE 124) may be received simultaneously by two or more cells (e.g., base stations 110 and 114 / 116) within RAN 100. Each of these cells may measure the strength of the pilot signal, and the RAN (e.g., one or more of base stations 110 and 114 / 116 and / or a central node in the core network) may determine a serving cell for UE 124. As UE 124 moves through RAN 100, the network may continue to monitor the uplink pilot signals sent by UE 124. When the signal strength or quality of the pilot signal measured by the neighboring cell exceeds the signal strength or quality measured by the serving cell, RAN 100 may handover UE 124 from the serving cell to the neighboring cell with or without notifying UE 124.

[0055] Although the synchronization signals sent by base stations 110, 112 and 114 / 116 may be uniform, the synchronization signals may not identify a specific cell, but rather identify a region of multiple cells operating on the same frequency and / or using the same timing. The use of regions in a 5G network or other next generation communication network implements an uplink-based mobility framework and improves the efficiency of both the UE and the network because the number of mobility messages that need to be exchanged between the UE and the network can be reduced.

[0056] In various implementations, the air interface in the RAN 100 may utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum typically provides exclusive use of a portion of the spectrum by virtue of a mobile network operator purchasing a license from a government regulator. Unlicensed spectrum provides shared use of a portion of the spectrum without the need for a government-authorized license. Although some technical rules generally still need to be followed to access the unlicensed spectrum, in general, any operator or device can gain access. Shared spectrum may fall between licensed spectrum and unlicensed spectrum, where some technical rules or restrictions may be required to access the spectrum, but the spectrum may still be shared by multiple operators and / or multiple RATs. For example, a license holder for a portion of the licensed spectrum may provide licensed shared access (LSA) to share the spectrum with other parties (e.g., with appropriate licensee-determined conditions to obtain access).

[0057] In order to achieve a low block error rate (BLER) for transmissions on the RAN 100 while still achieving very high data rates, channel coding may be used. That is, wireless communications may typically utilize appropriate error-correcting block codes. In a typical block code, an information message or sequence is segmented into code blocks (CBs), and an encoder (e.g., CODEC) at the transmitting device then mathematically adds redundancy to the information message. Utilizing this redundancy in the encoded information message may improve the reliability of the message, thereby enabling correction of any bit errors that may occur due to noise.

[0058] In early 5G NR specifications, quasi-cyclic low-density parity check (LDPC) with two different basemaps is used to encode user data traffic: one basemap is used for large code blocks and / or high code rates, and the other basemap is used otherwise. Polar coding is used to encode control information and the physical broadcast channel (PBCH) based on nested sequences. For these channels, puncturing, shortening, and repetition are used for rate matching.

[0059] Those skilled in the art will appreciate that various aspects of the present disclosure may be implemented using any suitable channel code. Various implementations of base stations and UEs may include appropriate hardware and capabilities (e.g., encoders, decoders, or CODECs) to utilize one or more of these channel codes for wireless communication.

[0060] In some examples, access to the air interface may be scheduled, wherein a scheduling entity (e.g., a base station) allocates resources (e.g., time-frequency resources) for communication between some or all devices and apparatuses within its service area or cell. Within the present disclosure, as further discussed below, a scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities. That is, for scheduled communications, a UE or scheduled entity utilizes resources allocated by the scheduling entity.

[0061] Base stations are not the only entities that can be used as scheduling entities. That is, in some examples, a UE can be used as a scheduling entity that schedules resources for one or more scheduled entities (e.g., one or more other UEs). In other examples, sidelink signals can be used between UEs without necessarily relying on scheduling or control information from a base station. For example, UE 138 is shown communicating with UEs 140 and 142. In some examples, UE 138 is being used as a scheduling entity or primary sidelink device, while UEs 140 and 142 can be used as scheduled entities or non-primary (e.g., auxiliary) sidelink devices. In another example, a UE can be used as a scheduling entity in a device-to-device (D2D), peer-to-peer (P2P), or vehicle-to-vehicle (V2V) network and / or in a mesh network. In the mesh network example, UEs 140 and 142 can optionally communicate directly with each other in addition to communicating with scheduling entity 138. Depending on the specific application, for example, in Figure 1 The radio protocol architecture of a RAN, such as the RAN 100 shown in FIG. 5 , may take various forms.

[0062] exist Figure 2 An exemplary protocol stack or radio protocol architecture for the user and control planes of 5G is shown in FIG.

[0063] like Figure 2 As shown, the protocol architecture 200 for UE and base station is shown as having three layers: layer 1, layer 2 and layer 3. Layer 1 (L1 layer) 202 is the lowest layer and implements various physical layer signal processing functions. The L1 layer will be referred to as the physical layer 206 in this article. Layer 2 (L2 layer) 208 is located above the physical layer 206 and is responsible for the link between the UE and the base station on the physical layer 206. In the user plane, the L2 layer 208 includes: a medium access control (MAC) sublayer 210, a radio link control (RLC) sublayer 212, a packet data convergence protocol (PDCP) 214 sublayer, and a service data adaptation protocol (SDAP) sublayer 216, which terminate at the base station on the network side. Although not shown, the UE may have several upper layers located above the L2 layer 208, including at least one network layer (e.g., an IP layer and a user data protocol (UDP) layer) that terminates at the user plane function (UPF) on the network side.

[0064] The SDAP sublayer 216 provides mapping between 5G core (5GC) QoS flows and data radio bearers, and performs QoS flow ID marking in both downlink and uplink packets. The PDCP sublayer 214 provides packet sequence numbering, ordered delivery of packets, retransmission of PDCP protocol data units (PDUs), and delivery of upper layer data packets to lower layers. The PDCP sublayer 214 also provides header compression for upper layer data packets to reduce radio transmission overhead, provides security by encrypting data packets, and provides integrity protection for data packets. The RLC sublayer 212 provides segmentation and reassembly of upper layer data packets, error correction by automatic repeat request (ARQ), and sequence numbering independent of PDCP sequence numbering. The MAC sublayer 210 provides multiplexing between logical channels and transport channels. The MAC sublayer 210 is also responsible for allocating various radio resources (e.g., resource blocks) in a cell between UEs and for HARQ operations. The physical layer 206 is responsible for sending and receiving data (e.g., within a time slot) on a physical channel.

[0065] In the control plane, the radio protocol architecture for the UE and base station is essentially the same for the physical layer 206 and the L2 layer 208, except that in many systems there is no header compression functionality for the control plane. As will be explained, systems and methods for negotiating and performing Ethernet header compression within the control plane are provided herein. Figure 2 The control plane of the 5G RAN also includes a radio resource control (RRC) sublayer 218 in layer 3 (Layer 3) 220. The L3 layer 22- also includes a non-access stratum (NAS) component 222. The RRC sublayer 218 is responsible for establishing and configuring signaling radio bearers (SRBs) and data radio bearers (DRBs) between the UE and the base station, paging initiated by the 5GC or NG-RAN, and broadcasting of system information related to the access stratum (AS) and NAS. The RRC sublayer 218 is also responsible for QoS management, mobility management (e.g., handover, cell selection, inter-RAT mobility), UE measurement and reporting, and security functions. The user plane portion of L3 220 may also include an Internet Protocol (IP) component not shown.

[0066] Figure 2 A protocol stack diagram 224 illustrating communication between corresponding protocol stack components of the UE 226 and the gNB 228 within the user plane is also provided. As shown via the protocol stack diagram 224, various user plane components of layers L1 and L2 of the UE 226 can communicate with corresponding components of the gNB 228 on the user plane. Figure 2A protocol stack diagram 230 illustrating communications between components of UE 226, gNB 228, and NG core component 232 within the control plane is also provided. As shown, various control plane components of layers L1 and L2 of UE 226 can communicate with corresponding components of gNB 228 over the control plane. In addition, layer 3 NAS components of UE 226 can communicate with corresponding NAS components of NG core 232 while bypassing gNB 228. An exemplary NAS core component is a core access and mobility management function (AMF) component, which will be referred to below. Figure 3 and Figure 4 Describe AMF. Figure 2 For the purpose of this, it is worth noting that the UE can communicate directly with the NG core components via NAS control plane signaling within L3. This can include using EHC to transport Ethernet packets via the control plane, which will be explained further.

[0067] Figure 3 and Figure 4 304 is a diagram illustrating an example of a network architecture 300 of a next generation (e.g., 5G or NR) communication network. The network architecture 300 may include one or more UEs 302, a next generation (e.g., 5G or NR) wireless RAN 304, and a next generation (e.g., 5G or NR) core network 306. In these examples, it is assumed that any signal path between the UE 302 and the core network 306 passes between these entities via the RAN 304, as represented by the illustrated signal path passing through the RAN 304. Here, the RAN 304 may be described above and in Figure 1 RAN 100 is shown in FIG. In the following description, when reference is made to the RAN 304 or actions performed by the RAN 304, it will be understood that such reference refers to one or more network nodes (e.g., gNBs) in the RAN 304, which are communicatively coupled to the core network 306 via, for example, one or more backhaul connections.

[0068] Both user plane and control plane functions may be supported by UE 302, RAN 304, and core network 306. The user plane carries user data traffic, while the control plane primarily carries signaling. As described in detail below, at least some Ethernet packet data traffic may be carried in the control plane using Ethernet data compression. Figure 3 and Figure 4 304 and the core network 306 are shown as being via a control plane node 308, which may be implemented, for example, in a RAN network node (e.g., a gNB) or distributed among two or more RAN network nodes (e.g., gNBs).

[0069] The wireless RAN 304 may be, for example, a 5G RAN, such as an NR RAN or an evolved E-UTRAN (i.e., an E-UTRAN having the same interface as the NRRAN but enhanced to be naturally connected to the next-generation core network 306). In other examples, the RAN 304 may be a next-generation wireless local area network (WLAN), a next-generation fixed broadband Internet access network, or other types of next-generation radio access networks that utilize next-generation RATs to access the next-generation core network 306.

[0070] The core network 306 may include, for example, an AMF 310, a session management function (SMF) 312, a policy control function (PCF) 314, an application function (AF) 316, a user plane infrastructure 318, and a UPF 320. In some examples, the AF 316 may be located outside the core network 306, i.e., within the network of an application service provider. The AMF 310 provides mobility management, authentication, and authorization for the UE 302, while the SMF 312 handles signaling related to a protocol data unit (PDU) session involving the UE 302 and allocates an IP address to the UE 302. Each PDU session may include one or more data flows (e.g., IP, Ethernet, and / or unstructured data flows), each of which is associated with a specific application. The AF 316 provides information about the data flows to the PCF 314 (which is responsible for policy control) in order to support corresponding QoS for each data flow. Thus, AF 316 and PCF 314 may provide flow information defining data flows and policy information (eg, QoS information) associated with the data flows to SMF 312 to configure one or more QoS flows within each PDU session.

[0071] The user plane infrastructure 318 facilitates routing of PDUs to and from the UE 302 via the RAN 304. The PDUs may include, for example, IP packets, Ethernet frames, and other unstructured data (i.e., machine type communications (MTC)). The UPF 320 is connected to the user plane infrastructure 318 to provide connectivity to an external data network 322. In addition, the UPF 320 may be communicatively coupled to the SMF 312 to enable the SMF 312 to configure a user plane connection on the core network 306.

[0072] In order to establish a PDU session with an external data network (DN) 322 via a next generation (5G) core network 306 and a next generation RAN 304, the UE 302 may send a PDU session establishment request message to the next generation core network 306 via the next generation RAN 304. The PDU session establishment request message may include a capability set of the UE 302. In some examples, the capability set may include an Ethernet header compression capability of the UE.

[0073] AMF 310 and / or SMF 312 may process the PDU session establishment request message based on the following: capability set, UE profile, network policy, flow information, and other factors. Then, AMF 310 and / or SMF 312 may establish a PDU connection for a PDU session between UE 302 and an external data network (DN) 322 on RAN 304 and core network 306 via user plane infrastructure 318. A PDU session may include one or more data flows and may be served by one or more UPFs 320 (only one of which is shown for convenience). Examples of data flows include, but are not limited to, IP flows, Ethernet flows, and unstructured data flows.

[0074] AMF 310 and / or SMF 312 may also use one or more of a capability set, a UE profile, a network policy, flow information, and other factors to select a QoS to be associated with one or more data volumes within a PDU session. For example, AMF 310 and / or SMF 312 may select one or more QoS parameters (e.g., a guaranteed bit rate (GBR) and / or a specific QoS class identifier (QCI)) for one or more data flows within a PDU session.

[0075] Figure 4 3 is a diagram illustrating an example of communication between a UE 302 and one or more external data networks 322 using multiple PDU sessions. Figure 4 In the example shown in , UE 302 actively participates in two PDU sessions 402a and 402b. Each PDU session 402a and 402b is a logical context in UE 302 that enables communication between a local endpoint (e.g., a web browser) in the UE and a remote endpoint (e.g., a web server in a remote host), and each PDU connection may include one or more data streams (e.g., IP, Ethernet, and / or unstructured data streams).

[0076] exist Figure 4In the example shown in , PDU session 402a is served by UPF 320a and includes two IP flows 404a and 404b, each of which terminates at a first external data network 322a (external data network 1) associated with a different IP address (IP1 and IP2) of UE 302. PDU session 402b also includes two IP flows 404c and 404d, each of which is associated with a different IP address (IP3 and IP4) of UE 302. However, IP flow 404c is served by UPF 320b and terminates at a second external data network 322b (external data network 2), while IP flow 404d is served by local UPF 320c and terminates at a local endpoint of the second external data network 322c (local external data network 2). Session management contexts (e.g., utilizing software defined networking (SDN) and signaling routing) for PDU session 402a and PDU session 402b are provided in SMF 312. The user plane context (eg, QoS, tunneling, etc.) for the PDU session 402a is provided in the UPF 320a, while the user plane context for the PDU session 402b is provided in the UPF 320b and the local UPF 320c.

[0077] Further information about the core network and its components can be found in the following document: ETSI TS124501 V15.0.0 (2018-07) 5G, Non-Access-Stratum (NAS) protocol for 5G System (5GS), Stage 3 (3GPP TS24.501 Version 15.0.0 Release 15). It should be noted that the core network described therein does not provide data transmission on the control plane (while also providing EHC, the feature described in this article).

[0078] Figure 5 is used by Figure 1-Figure 4 5. The present invention is a flow chart of a method for use by a UE or other wireless communication device in a network of a core network configured to allow Ethernet packet transmission through its control plane.

[0079] Starting from box 502, the UE initiates a registration process with the AMF of the network by sending a mobility management registration request message, which includes a bit set to indicate the UE's support for EHC for data transmission on the control plane of the wireless communication network. For 5G Mobility Management (5GMM), the registration request message may include an information element (IE) specifying capabilities, and a bit within the IE may be set to one value (e.g., 1) to indicate that the UE has EHC capability and set to another value (e.g., 0) to indicate that the UE does not have EHC capability. It should be noted here that a separate bit (not shown) in the IE of the registration request message may also be set to indicate support for IP packet header compression (IPHC). Therefore, in one example, the 5G MM standard may be drafted or revised to define a modified IE that includes a traditional IPHC capability bit and a new EHC capability bit.

[0080] At block 504, the UE receives a registration accept message from the AMF (assuming the registration is accepted), which includes an indicator indicating that the wireless communication core network supports EHC for data transmission on the control plane (assuming also that the network does support EHC for data transmission on the control plane). For 5G MM, the IE of the registration accept message may include a bit set by the AMF to indicate EHC capability. (Similarly, a separate bit in the IE (not shown) may be set to indicate support for header compression of IP packets.)

[0081] At box 506, the UE initiates a PDU session management (SM) process with the SMF of the network by sending a PDU session establishment / modification request message to the SMF of the network, which requests the use of EHC for data transmission on the control plane and includes a request for a field length of the EHC context ID field of 7 bits or 15 bits. For 5G SM, the context ID can be a parameter of the compressed header that identifies the packet stream associated with each compressed data stream. During the actual transmission of the compressed data, the context ID is sent instead of the compressed header. In one example, the 5G SM standard may be drafted or revised to define a new IE in the PDU session establishment / modification request message for the UE to request EHC for the PDU session and request a specific context ID field length. If the session management function SMF accepts the EHC for the PDU session, it responds with the context ID length in the PDU session establishment / modification accept / command message.

[0082] At block 508, the UE receives a PDU session management response generated by the SMF, the response including an indication of acceptance of using the EHC for data transmission on the control plane, the indication including a selected (negotiated) field length for the context ID field of 7 or 15 bits. It should be noted that the indication of acceptance is for a specific Ethernet flow, wherein a specific Ethernet flow refers to an Ethernet packet exchange between a specific Ethernet source-destination address pair.

[0083] At block 510, the UE then uses Ethernet packets to transmit data for a specific Ethernet flow on the control plane of the core network, while performing EHC using the selected (negotiated) 7 or 15 bit length of the context ID field. Figure 4 For example, an Ethernet packet may be sent from UE 302 to UPF 320 through AMF 310 and SMF 312, and then to external network 322. In other examples, an Ethernet packet may be sent from UE 302 to control plane node 308 through AMF 310. A different context ID is used for each specific Ethernet flow.

[0084] Figure 6 is used by Figure 1-Figure 4 600 is a flow chart of a method used by a core network to allow Ethernet packet transmission by a UE through a control plane.

[0085] Starting from block 602, the AMF receives a mobility management registration request from a UE, the request including a bit set to indicate the UE's support for EHC for data transmission on the control plane of the wireless communication network. Figure 5 As explained, this bit may be set together with the IE of the Mobility Management Registration Request.

[0086] At box 604, the AMF selects an SMF procedure for use with the request and then sends a registration accept message to the UE (assuming the registration is accepted) that includes an indicator indicating that the wireless communication core network supports EHC for data transmission on its control plane (again assuming that the core network does support EHC for data transmission on its control plane).

[0087] At box 606, the SMF of the core network receives a request for PDU session management from the UE (via a PDU Session Establishment / Modification Request message), wherein the request message includes a request to use EHC for data transmission on the control plane and includes a request for a field length for the EHC Context ID field of 7 or 15 bits.

[0088] At box 608, the SMF selects a specific context ID field length (7 or 15 bits) and sends a PDU session management response to the UE, which includes an indication of acceptance of using EHC for data transmission on the control plane, including the selected (negotiated) field length for the context ID field.

[0089] At block 610, the AMF, SMF or other control plane component or node of the core network receives data for a specific Ethernet flow from the UE on the control plane in an Ethernet packet with a compressed or suppressed header according to the selected (negotiated) context ID field length of 7 or 15 bits. As mentioned, a different context ID is used for each specific Ethernet flow.

[0090] Figure 7 700 is a signaling or timing diagram illustrating exemplary signaling for notifying and negotiating EHC for a PDU session. At 702, the UE 302 may generate and send a mobility management registration request message including a bit set to notify that the UE has EHC capabilities for data transmission on the control plane. The mobility management registration request message may be routed to the AMF 310 via the RAN 304. At 704, the AMF 310 responds by selecting an SMF, and then at 706, sends a mobility management registration request acceptance including a bit set to confirm that the AMF and other components of the core network have EHC capabilities. At 708, the UE 302 generates and sends a PDU session establishment request message having a request for the length of the EHC context ID field. As mentioned, the request for the length may be within an IE of the PDU session establishment request message. The PDU session establishment request message may be routed to the selected SMF 312 via the RAN 304 and the AMF 310.

[0091] At 710, the SMF 312 responds by selecting a length for the Context ID field (e.g., 7 bits or 15 bits), and then, at 712, sends a PDU Session Establishment Ack to the UE 302, the Ack including the selected length for the Context ID field. The PDU Session Establishment Ack may be routed to the UE 302 via the AMF 310 and the RAN 304. At 714, the UE 203 sends an Ethernet packet on the control plane of the core network when employing EHC and using the selected EHC Context ID field length for the Context ID provided with the packet. Figure 7 In an example of , an Ethernet packet is sent on a control plane of a core network when EHC is employed and when a selected EHC context ID field length for a context ID provided with the packet is used. Figure 7In the example of FIG. 1 , an Ethernet packet is sent to UPF 320 (via RAN 304, AMF 310, and selected SMF 312), which may forward the packet to an external network such as Figure 4 In other examples, Ethernet packets may be sent to other components of the core network. It should be noted that the establishment and processing of the PDU session is not involved. Figure 4 Additional components of the core network 306. Figure 7 The intent is to highlight the various functions and operations that are particularly relevant to EHC negotiation, while omitting other details of the actual core network.

[0092] Figure 8 An exemplary 5G MM Capability IE 800 is shown including a bit 804 that may be set by the UE to provide a MM component of the core network such as Figure 7 The AMF 310 of the core network informs the UE that it is configured for EHC for data sent on the control plane of the core network. This bit is referred to as the "EHC CP" bit in the figure because it indicates the UE's support for EHC for control plane data packet transmission. Figure 8 In the specific example of IE 800, the third bit within octet 3 of IE 800 is used as the EHC CP bit (where the applicable 3GPP 5G MM standard is specified, so the core network recognizes this bit as indicating UE support for control plane EHC), but other bit positions within IE 800 may alternatively be specified within the standard. In some examples, an IE with a bit set to "1" may be included Figure 7 In the 5G MM Registration Request sent from the UE to the AMF 310 at 702. Various other parts of IE800 such as its 5G MM Capability IE Indicator (IEI) may be the same as the previous version of the corresponding 3GPP 5G MM standard.

[0093] Figure 8 Also shown is an exemplary 5G SM Capability IE 804 including bits 806 that may be set by the UE to provide a SM component of the core network such as Figure 7The SMF 312 of the core network informs the UE that it is configured for EHC for data sent on the control plane of the core network and that the UE is requesting a field length for the EHC context ID (of 7 bits or 15 bits). This bit is referred to in the figure as the "EHC FL CP" bit because it is used to request the field length (FL) of the context ID of the EHC for control plane (CP) data packet transmission. In this example, by requesting the SMF to provide the field length of the context ID for the EHC, the UE is also thereby signaling to the SMF that it is requesting the use of EHC (because otherwise, the EHC context ID would not be required). In this way, the UE does not have to provide an indicator requesting the use of EHC and a separate indicator requesting the field length of the context ID for the EHC within its request for session management.

[0094] exist Figure 8 In the specific example of , the third bit within the 3rd byte of the IE is 806, which is used as the EHC FL CP bit (where the applicable 3GPP 5G SM standard is specified, so the core network recognizes this bit as indicating that the UE supports control plane EHC and the UE is requesting a context ID field length), but other bit positions within the IE 806 may be specified within the standard. In some examples, an IE with a bit set to "1" may be included Figure 7 708 of 5G SM PDU Session Establishment Request sent from the UE to the SMF 312. Various other parts of IE 806, such as its 5G MM Capability IE Indicator (IEI), may be the same as previous versions of the corresponding 3GPP 5G SM standard. As already explained, if the SMF 312 agrees to enable EHC for packets sent on the control plane of the core network, the SMF 312 responds to the PDU Session Establishment Request from the UE by selecting a length for the Context ID field, and then sends a PDU Session Establishment Confirmation to the UE, which includes the selected (negotiated) length for the Context ID field.

[0095] Fig. 9An exemplary format for an initial complete (uncompressed) Ethernet packet 900 sent by a UE on the control plane of a core network is shown, wherein the initial packet includes an uncompressed Ethernet header. For example, the initial packet may be the first packet in a sequence of packets for a current PDU session for a particular Ethernet stream. The complete (uncompressed) packet 900 includes an F / C bit 902 in its first octet, which indicates whether the packet is complete or uncompressed. Since the packet 900 is a complete packet, the bit may be set to indicate a complete packet by, for example, setting the bit value to "1". The packet 900 also includes a context ID for the control plane EHC, which may be 7 bits or 15 bits (as selected by the SMF). If the field length of the context ID for the control plane EHC is 7 bits, the entire context ID 904 is stored or encoded using the remaining 7 bits of the first octet. If the field length of the context ID for the control plane EHC is 15 bits, the remaining portion of the context ID for the control plane EHC 906 is stored or encoded using the eight bits of the second octet. A control plane Ethernet packet header 908 is then provided, followed by the first portion of a control plane Ethernet packet payload 910, and any padding that may be included, for a particular Ethernet flow (eg, data).

[0096] Fig. 9 Also shown is an exemplary format for a subsequent compressed Ethernet packet 912 sent by the UE on the control plane of the core network, wherein the subsequent packet omits the Ethernet header (thereby compressing or suppressing the header). For example, the subsequent packet may be the second packet in a sequence of packets for the current PDU session for a particular Ethernet stream. The compressed packet format 912 also includes an F / C bit 902 in its first octet, which indicates whether the packet is complete or uncompressed. Since the packet 912 is a compressed packet, the bit can be set to indicate a compressed packet by, for example, setting the bit value to "0". The packet 912 also includes the same context ID for the control plane EHC as the initial uncompressed packet 902. Similarly, if the field length of the context ID for the control plane EHC is 7 bits, the entire context ID 904 is stored or encoded using the remaining 7 bits of the first octet of the packet. If the field length for the context ID is 15 bits, the remaining portion of the context ID 906 is stored or encoded using the 8 bits of the second octet. The control plane Ethernet packet header 908 is then omitted. Instead, the next portion 914 of the packet 912 provides the next (second) portion of the control plane Ethernet packet payload being sent for the particular Ethernet flow (eg, data) and any padding that may be included.

[0097] Fig. 9Also shown is an exemplary format for a subsequent return or feedback Ethernet packet 916 sent back to the UE on the control plane of the core network. For example, a feedback packet may be sent (by a receiving device) to reply to the first packet 902 of a packet sequence for the current PDU session for a particular Ethernet stream in order to confirm the receipt of the first packet 902. The feedback packet format 916 includes a return bit (R) 918 within its first octet, indicating that the packet is a feedback packet. The packet 916 also includes a context ID for the control plane EHC that is the same as the forward packet 902. Similarly, if the field length of the context ID for the control plane EHC is 7 bits, the entire context ID 904 is stored or encoded using the remaining 7 bits of the first octet of the packet. If the field length for the context ID is 15 bits, the remaining portion of the context ID 906 is stored or encoded using the 8 bits of the second octet. For the return packet, the header and payload are not included.

[0098] Fig.10 1000 is a block diagram illustrating an example of a hardware implementation for a core network 1000 employing a processing system 1014. For example, the core network may correspond to the core network 1000 described above with reference to Figure 3 , Figure 4 and / or Figure 7 A network including AMF and SMF components is shown and described.

[0099] The core network 1000 may be implemented using a processing system 1014 including one or more processors 1004. Examples of processors 1004 include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout the present disclosure. In various examples, the core network 1000 may be configured to perform any one or more of the functions described herein. That is, the processor 1004 as utilized in the core network 1000 may be used to implement any one or more of the processes and procedures described herein.

[0100] In this example, the processing system 1014 can be implemented using a bus architecture (which is generally represented by bus 1002). Depending on the specific application and overall design constraints of the processing system 1014, the bus 1002 may include any number of interconnecting buses and bridges. The bus 1002 connects various circuits including one or more processors (which are generally represented by processor 1004), memory 1005, and computer-readable media (which are generally represented by computer-readable media 1006). The bus 1002 may also connect various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not described again. The bus interface 1008 provides an interface (or wireless communication interface or transceiver) between the bus 1002 and the network interface 1010. The network interface 1010 provides a unit for communicating with various other devices (such as UE) on a transmission medium. Depending on the nature of the device, a user interface 1012 (e.g., a keypad, a display, a touch screen, a speaker, a microphone, a joystick) may also be provided. Of course, such a user interface 1012 is optional and may be omitted in some examples.

[0101] The processor 1004 is responsible for managing the bus 1002 and general processing, which includes executing software stored on the computer-readable medium 1006. Software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language or other terms. The software, when executed by the processor 1004, causes the processing system 1014 to perform the various functions described below for any particular device. The computer-readable medium 1006 and the memory 1005 can also be used to store data manipulated by the processor 1004 when executing the software.

[0102] Computer readable medium 1006 may be a non-transitory computer readable medium. For example, non-transitory computer readable media include magnetic storage devices (e.g., hard disks, floppy disks, tapes), optical disks (e.g., compact disks (CDs) or digital versatile disks (DVDs)), smart cards, flash memory devices (e.g., card, stick or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. Computer readable medium 1006 may be located in processing system 1014, outside processing system 1014, or distributed among multiple entities including processing system 1014. Computer readable medium 1006 may be embodied in a computer program product. For example, a computer program product may include a computer readable medium in a packaging material. In some examples, computer readable medium 1006 may be part of memory 1005. Those skilled in the art will recognize how to best implement the described functionality presented throughout this disclosure depending on the particular application and the overall design constraints imposed on the overall system.

[0103] In some aspects of the present disclosure, processor 1004 may include circuits configured for various functions. In some core networks, different functions may be performed by different components or nodes within the network, and thus separate processors may be provided within different nodes to perform different functions. For convenience and generality, Fig.10 The processor 1004 is shown as having a set of processing components or circuits, such as mobility management and session management components. In an actual system, these processing components or circuits may be provided in separate nodes.

[0104] exist Fig.10 In an example of, the processor 1004 may include a mobility management circuit 1042 configured for use with a control plane EHC. The mobility management circuit 1042 may be configured to receive and process a mobility management registration request received from a UE, wherein the request includes an indication that the UE is configured for a control plane EHC. Among other tasks, the mobility management circuit 1042 may also select a specific SMF for use with the UE. The mobility management circuit 1042 may also be configured to execute mobility management software 1052 included on the computer-readable medium 1006 to implement one or more functions described herein, including supporting functions for mobility management for a control plane EHC.

[0105] The processor 1004 may also include a session management circuit 1044 configured for use with the control plane EHC. The session management circuit 1044 may be configured to receive and process a PDU session establishment request message from the UE. The PDU session establishment request message may contain a set of capabilities of the UE. The capability set may include, for example, an indication that the UE is configured for the control plane EHC. The PDU session establishment request message may also include a request for a field length of a context ID for use with the control plane EHC. The session management circuit 1044 may process the PDU session establishment request message based on UE capabilities, UE profiles (maintained at a specific core network node or retrieved from another core network node), UE subscription information, network policies, flow information, and other factors. The session management circuit 1044 may then establish a PDU connection between the UE and an external data network on the NG RAN via an NG core network that allows and supports EHC. The session management circuitry 1044 may also be configured to execute session management software 1054 included on the computer-readable medium 1006 to implement one or more functions described herein, including functions to support session management for control plane EHCs.

[0106] The processor 1004 may also include a control plane Ethernet header compression / decompression circuit 1046 configured to compress at least some Ethernet packets sent by the core network 1000 via the control plane and / or decompress at least some Ethernet packets received by the core network 1000. The Ethernet header compression / decompression circuit 1046 may also be configured to execute Ethernet header compression / decompression software 1056 included on the computer-readable medium 1006 to implement one or more functions described herein, including supporting compression / decompression of Ethernet headers within Ethernet packets sent via the control plane of the core network. To facilitate EHC, the control plane Ethernet header compression / decompression circuit 1046 may store context IDs 1007 in a portion of the memory 1005 for various Ethernet flows.

[0107] Fig.11 1 is a diagram illustrating an example of a hardware implementation for an exemplary UE 1100 employing a processing system 1114 including one or more processors 1104. For example, the UE may correspond to the UE described above in Figure 1 , Figure 3 , Figure 4 and / or Figure 7 Any UE among the UEs shown in .

[0108] The processing system 1114 can be used with Fig.101014 is substantially the same as the processing system 1014 shown in 1010, including a bus interface 1108, a bus 1102, a memory 1105, a processor 1104, and a computer-readable medium 1106. In addition, the UE 1100 may include a user interface 1112 and a transceiver 1110 for communicating with various other devices over a transmission medium (e.g., an air interface for communicating with a base station). The processor 1104 as utilized in the UE 1100 may be used to implement any one or more of the processes described herein.

[0109] In some aspects of the present disclosure, the processor 1104 may include circuits configured for various functions. For example, the processor 1104 may include a mobility management circuit 1142 configured for use with the control plane EHC. The mobility management circuit 1142 may be configured to generate a mobility management registration request and send it to a core network node (such as Fig.10 The core network 1000 of the present invention includes a request for the UE to be configured for the control plane EHC. The mobility management circuit 1142 may also be configured to execute the mobility management software 1152 included on the computer-readable medium 1106 to implement one or more functions described herein, including supporting the mobility management for the control plane EHC.

[0110] The processor 1104 may also include a session management circuit 1144 configured for use with the control plane EHC. The session management circuit 1144 may be configured to generate a PDU session establishment request message and send it to a core network node (such as Fig.10 core network 1000). As explained above, the PDU session establishment request message may include a set of capabilities of the UE, such as an indication that the UE is configured for control plane EHC. The PDU session establishment request message may also include a request for a field length of a context ID for use with the control plane EHC. The session management circuit 1144 may process a PDU session establishment confirmation received from the core network, which is used to confirm the establishment of a PDU connection between the UE and an external data network on the NG RAN via an NG core network that allows and supports EHC. The session management circuit 1144 may also be configured to execute session management software 1154 included on the computer-readable medium 1106 to implement one or more functions described herein, including supporting session management functions for control plane EHC.

[0111] The processor 1104 may also include a control plane Ethernet header compression / decompression circuit 1146 configured to compress at least some Ethernet packets sent on the control plane and / or decompress at least some Ethernet packets received on the control plane of the core network. The Ethernet header compression / decompression circuit 1146 may also be configured to execute Ethernet header compression / decompression software 1156 included on the computer-readable medium 1106 to implement one or more functions described herein, including supporting compression / decompression of Ethernet headers within Ethernet packets sent via the control plane of the core network. To facilitate EHC, the control plane Ethernet header compression / decompression circuit 1146 may store context IDs 1107 within a portion of the memory 1105 for various Ethernet flows.

[0112] Fig.12 1200 is a flowchart of a method for use by a network component of a wireless communication network. In some examples, the method can be described above and in Fig.10 1000, a processor or a processing system, or any suitable means for performing the functions described. In some examples, the network components and UEs (such as Fig.11 In some examples, the network components include separate individual components or nodes (such as separate AMF and SMF nodes), and Fig.12 At least some of the functions, processes or operations may be performed by Fig.12 It is executed by different components or nodes in the entire network components mentioned in the specification.

[0113] At box 1202, the network component obtains a signal from a wireless communication device via a wireless communication network, the signal indicating that the wireless communication device supports EHC for data transmission on the control plane. (In this article, "obtaining" broadly covers, for example, generating, obtaining, receiving, retrieving, or performing any other suitable corresponding action.) At box 1204, the network component sends a response to the wireless communication device, the response indicating that the wireless communication network supports EHC for data transmission on the control plane. At box 1206, the network component performs data transmission of Ethernet packets with the wireless communication device on the control plane when performing EHC.

[0114] In some aspects, Fig.12The network component referred to in is a mobility management component (e.g., AMF), and the signal obtained from the wireless communication device is a mobility management registration request message from the UE, which includes an indication of the UE's support for EHC for data transmission on the control plane of the wireless communication network. In some aspects, the response indicating that the wireless communication network supports EHC for data transmission on the control plane is a mobility management registration accept message sent by the AMF to the UE. In some aspects, the network component is a session management component (e.g., SMF), and the signal obtained from the wireless communication device is a session establishment request from the UE, which includes an indication of the UE's support for EHC for data transmission on the control plane of the wireless communication network. In some aspects, the response indicating that the wireless communication network supports EHC for data transmission on the control plane is a session establishment confirmation message sent by the SMF to the UE.

[0115] In some aspects, the SMF performs various session management operations to initiate data transmission, such as selecting a field length for the context ID field. Once a data transmission session is established using the selected field length, data transmission of Ethernet packets can be performed on the control plane when performing EHC.

[0116] Fig.13 1300 is a flowchart of a method for use by a wireless communication device of a wireless communication network. In some examples, the method can be described above and in Fig.11 UE 1100 shown in FIG. 1 , by a processor or processing system, or by any suitable unit for performing the functions described. In some examples, the wireless communication device communicates with a wireless network component, such as a wireless network component in FIG. Fig.10 The wireless network components shown in , which include a core network with separate individual components or nodes (such as separate AMF and SMF nodes).

[0117] At block 1302, the wireless communication device sends a signal to the wireless communication network indicating that the wireless communication device supports EHC for data transmission on the control plane. At block 1304, the wireless communication device obtains a response from the wireless communication network indicating that the wireless communication network supports EHC for data transmission on the control plane. At block 1306, the wireless communication device performs data transmission of Ethernet packets with the wireless communication network on the control plane when performing EHC.

[0118] In some respects, Fig.13The wireless communication network mentioned in includes a mobility management component (e.g., AMF), and the signal sent to the wireless communication network is a mobility management registration request message, which includes an indication of the UE's support for EHC for data transmission on the control plane of the wireless communication network. In some aspects, the response obtained from the wireless communication network indicating that the network supports EHC for data transmission on the control plane is a mobility management registration acceptance message received by the UE from the AMF. In some aspects, the wireless communication network includes a session management component (e.g., SMF), and the signal sent to the wireless communication network is a session establishment request, which includes an indication of the UE's support for EHC for data transmission on the control plane of the wireless communication network. In some aspects, the response obtained from the wireless communication network is a session establishment confirmation message sent by the SMF to the UE. In some aspects, the wireless communication device relies on the SMF to perform session management operations to initiate data transmission, such as selecting a field length for the context ID field. Once a data transmission session is established using the selected field length, data transmission of Ethernet packets can be performed on the control plane when performing EHC.

[0119] Fig.14 1 is a block diagram illustrating a network component 1400 of a wireless communication network. The network component 1400 includes a network interface 1402 (such as a wireless communication interface or a transceiver) and a processor 1404. The processor 1404 is configured or equipped to: obtain a signal from a wireless communication device (such as a UE) indicating that the wireless communication device supports EHC for data transmission on the control plane; send a response to the wireless communication device indicating that the wireless communication network supports EHC for data transmission on the control plane; and perform data transmission of Ethernet packets with the wireless communication device on the control plane when performing EHC.

[0120] Fig.15 1 is a block diagram illustrating a wireless communication device 1500 for use in a wireless communication network. The wireless communication device 1500 includes a transceiver 1502 and a processor 1504. The processor 1504 is configured or equipped to: send a signal to the wireless communication network indicating that the wireless communication device supports Ethernet Header Compression (EHC) for data transmission on the control plane; obtain a response from the wireless communication network indicating that the wireless communication network supports EHC for data transmission on the control plane; and perform data transmission of Ethernet packets with the wireless communication network on the control plane when performing EHC.

[0121] Fig.16is a block diagram illustrating components of a core network 1600 of a wireless communication network. The core network 1600 includes a network interface 1602 (e.g., a wireless transceiver) and various processing components or controllers connected or coupled to the network interface 1602 and / or to each other. A receiving component or controller 1604 is configured to receive and decode a signal from a wireless communication device (such as a UE), the signal including an indicator indicating that the wireless communication device supports EHC for data transmission on the control plane of the wireless communication network. A response component or controller 1606 is configured to generate and send a response to the wireless communication device, the response indicating that the wireless communication network supports EHC for data transmission on the control plane of the wireless communication network (assuming that the wireless communication network does support EHC for control plane data transmission). A data transmission component or controller 1608 is configured to perform or control data transmission of Ethernet packets with the wireless communication device on the control plane of the wireless communication network when performing EHC.

[0122] Fig.17 is a block diagram illustrating components of a wireless communication device 1700, such as a UE. The wireless communication device 1700 includes a wireless transceiver 1702 and various processing components or controllers connected or coupled to the wireless transceiver 1702 and / or to each other. A capability advertising component or controller 1704 is configured to generate and send a signal to a wireless communication network, the signal indicating that the wireless communication device supports EHC for data transmission on a control plane of the wireless communication network. A receiving component or controller 1706 is configured to receive and decode a response from the wireless communication network, the response indicating that the wireless communication network supports EHC for data transmission on the control plane. A data transmission component or controller 1708 is configured to perform or control data transmission of Ethernet packets with the wireless communication network on the control plane of the wireless communication network when performing EHC.

[0123] In some aspects, means for performing various functions described herein are provided. For example, an apparatus may be provided, comprising: means for obtaining a signal from a wireless communication device via a wireless communication network (such as receiving component 1602), the signal indicating that the wireless communication device supports EHC for data transmission on a control plane; means for sending a response to the wireless communication device (such as AMF 310, mobility management circuit 1042, or response component 1606), the response indicating that the wireless communication network supports EHC for data transmission on the control plane; and means for performing data transmission of Ethernet packets with the wireless communication device on the control plane when performing EHC (such as control plane Ethernet header compression / decompression circuit 1046 or data transmission component 1608).

[0124] As another example, an apparatus is provided, comprising: a unit (such as a capability advertisement component 1704) for sending a signal to a wireless communication network, the signal indicating that the wireless communication device supports EHC for data transmission on a control plane; a unit (such as a mobility management circuit 1142 or a receiving component 1706) for obtaining a response from the wireless communication network, the response indicating that the wireless communication network supports EHC for data transmission on the control plane; and a unit (such as a control plane Ethernet header compression / decompression circuit 1146 or a data transmission component 1708) for performing data transmission of Ethernet packets with the wireless communication network on the control plane when performing EHC.

[0125] Several aspects of wireless communication networks have been presented with reference to exemplary implementations. As those skilled in the art will readily appreciate, various aspects described throughout this disclosure may be extended to other telecommunication systems, network architectures and communication standards.

[0126] For example, various aspects may be implemented in other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile (GSM). Various aspects may also be extended to systems defined by the Third Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Evolution Data Optimized (EV-DO). Other examples may be implemented in systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunication standard, network architecture, and / or communication standard employed will depend on the specific application and the overall design constraints imposed on the system.

[0127] Fig.18 1800 is a flowchart of a method for use by a wireless communication device of a wireless communication network. In some examples, the method can be described above and in Fig.11 UE 1100 shown in FIG. Fig.23 The wireless communication device 2300 shown in FIG. 2300 is executed by a processor or a processing system, or by any suitable unit for performing the functions described. In some examples, the wireless communication device is connected to a wireless network component (such as a wireless network component). Fig.11 The wireless network components shown in or discussed below Fig. 22 The wireless network components shown in FIG. 1 communicate with each other.

[0128] At box 1802, the wireless communication device sends a signal to the wireless communication network indicating that the wireless communication device supports EHC for data transmission on the control plane. In some aspects, this is achieved by sending a mobility management registration request message that includes an indication of support for EHC for data transmission on the control plane. At box 1804, the wireless communication device obtains a response from the wireless communication network indicating that the wireless communication network supports EHC for data transmission on the control plane. In some aspects, this is achieved by receiving an indication of support for EHC within a mobility management registration accept message. At box 1806, the wireless communication device communicates with the wireless communication network on the control plane using EHC. In some aspects, the wireless communication device communicates with the wireless communication network on the control plane using EHC by sending at least one Ethernet packet compressed using EHC to the wireless communication network on the control plane. In some aspects, the wireless communication device communicates with the wireless communication network on the control plane using EHC by receiving at least one Ethernet packet compressed using EHC from the wireless communication network on the control plane. As explained above, and as discussed below Fig.19 As outlined in , before a wireless communication device communicates with a wireless communication network on a control plane using an EHC, in some aspects the wireless communication device requests to use the EHC for data transmission on the control plane.

[0129] Fig.19 1900 is a flowchart of a method for use by a wireless communication device of a wireless communication network. In some examples, the method can be described above and in Fig.11 UE 1100 shown in FIG. Fig.23 The wireless communication device 2300 shown in FIG. 2300 is executed by a processor or a processing system, or by any suitable unit for performing the functions described. In some examples, the wireless communication device is connected to a wireless network component (such as a wireless network component). Fig.11 The wireless network components shown in or discussed below Fig. 22 The wireless network components shown in FIG. 1 communicate with each other.

[0130] At box 1902, the wireless communication device sends a mobility management registration request message to the wireless communication network, the message including an indication of support for EHC for data transmission on the control plane. At box 1904, the wireless communication device receives a mobility management registration acceptance message from the wireless communication network, the message indicating that the wireless communication network supports EHC for data transmission on the control plane. At box 1906, the wireless communication device sends a request signal to the wireless communication network within a PDU session establishment request message or a PDU session modification message, the request signal including a request for using EHC for data transmission on the control plane. At box 1908, the wireless communication device obtains an indication of acceptance of using EHC for data transmission on the control plane from the SMF of the wireless communication network. At box 1910, the wireless communication device communicates with the wireless communication network on the control plane using EHC by sending or receiving Ethernet packets compressed using EHC.

[0131] Fig. 20 2000 is a flowchart of a method for use by a network component of a wireless communication network. In some examples, the method can be described above and in Fig.10 The core network 1000 shown in FIG. Fig. 22 The network component 2200 shown in FIG. 1 is executed by a processor or a processing system, or by any suitable means for performing the functions described. In some examples, the network component is associated with a UE or other wireless communication device (such as Fig.11 UE 1100 or the one discussed below Fig.23 The wireless communication device 2300 communicates with each other.

[0132] At box 2002, a network component obtains a signal from a wireless communication device indicating that the wireless communication device supports EHC for data transmission on a control plane. In some aspects, the signal is a mobility management registration request message that includes an indication of support for EHC for data transmission on a control plane. At box 2004, the network component sends a response to the wireless communication device indicating that the wireless communication network supports EHC for data transmission on a control plane. In some aspects, the response is sent within a mobility management registration accept message. At box 2006, the network component communicates with the wireless communication device on a control plane using EHC. In some aspects, the network component communicates with the wireless communication device on a control plane using EHC by sending at least one Ethernet packet compressed using EHC to the wireless communication device on the control plane. In some aspects, the network component communicates with the wireless communication device on a control plane using EHC by receiving at least one Ethernet packet compressed using EHC from the wireless communication device on the control plane. As explained above, and as discussed below Fig.21 As outlined in , before a network component communicates with a wireless communication network on a control plane using an EHC, in some aspects a wireless communication device requests use of the EHC for data transmission on the control plane.

[0133] Fig.21 2100 is a flowchart of a method for use by a network component of a wireless communication network. In some examples, the method may be described above and in Fig.10 The core network 1000 shown in FIG. Fig. 22 The network component 2200 shown in FIG. 1 is executed by a processor or a processing system, or by any suitable means for performing the functions described. In some examples, the network component is associated with a UE or other wireless communication device (such as Fig.11 UE 1100 or the one discussed below Fig.23 The wireless communication device 2300 communicates with each other.

[0134] At box 2102, the network component receives a mobility management registration request message from the wireless communication device, the message including an indication of support for EHC for data transmission on the control plane. At box 2104, the network component sends a mobility management registration accept message to the wireless communication device, indicating that the wireless communication network supports EHC for data transmission on the control plane. At box 2106, the network component obtains a signal from the wireless communication device within a PDU session establishment request message or a PDU session modification message, the signal including a request for using EHC for data transmission on the control plane. At 2108, the network component sends an indication of acceptance of using EHC for data transmission on the control plane to the wireless communication device, which can be generated by the SMF of the wireless communication network. At box 2110, the network component communicates with the wireless communication device on the control plane using EHC by sending or receiving Ethernet packets compressed using EHC.

[0135] Fig. 22 2200 is a block diagram illustrating an example of a hardware implementation for a network component 2200 employing a processing system 2214. For example, the network component may correspond to the network component including the above reference Figure 3 , Figure 4 and / or Figure 7 Components of a network of AMF and SMF components are shown and described.

[0136] The network component 2200 can be implemented using a processing system 2214 including one or more processors 2204. Examples of processors 2204 include microprocessors, microcontrollers, DSPs, FPGAs, PLDs, state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout the present disclosure. In various examples, the network component 2200 can be configured to perform any one or more of the network component functions described herein. That is, the processor 2204 as utilized in the network component 2200 can be used to implement any one or more of the processes and procedures described herein with respect to the operation of the network component.

[0137] The overall architecture of the processing system 2214 may be similar to that in Fig.10 The processing system 1014 shown in , includes a bus interface 2208, a bus 2202, a memory 2205, a processor 2204 and a computer-readable medium 2206. In addition, the network component 2200 may include a user interface 2212 and a transceiver 2210 for communicating with various other devices (e.g., UE) over a transmission medium. Fig. 22 , the transceiver 2210 is shown as including one or more receivers 2213 and one or more transmitters, which are connected to one or more antennas 2211.

[0138] The processor 2204 is responsible for managing the bus 2202 and general processing, which includes the execution of software stored on the computer-readable medium 2206. The software, when executed by the processor 2204, causes the processing system 2214 to perform the various functions described below for any particular device. The computer-readable medium 2206 and the memory 2205 may also be used to store data manipulated by the processor 2204 when executing the software.

[0139] Computer readable medium 2206 may be a non-transitory computer readable medium. Computer readable medium 2206 may be located in processing system 2214, external to processing system 2214, or distributed across multiple entities including processing system 2214. Computer readable medium 2206 may be embodied in a computer program product. For example, a computer program product may include a computer readable medium in packaging materials. In some examples, computer readable medium 2206 may be part of memory 2205.

[0140] In some aspects of the present disclosure, processor 2204 may include circuits configured for various functions. In some network components, different functions may be performed by different components or nodes within the network, and thus separate processors may be provided within different nodes to perform different functions. For convenience and generality, Fig. 22 The processor 2204 is shown as having a set of processing components, controllers or circuits.

[0141] exist Fig. 22 In an example of , the processor 2204 may include a circuit 2240 configured to receive and process a signal indicating that the wireless communication device (such as a UE) supports EHC for data transmission on the control plane. The processor 2204 may also include a circuit 2242 configured to generate and send an indication that the wireless communication network (of which the network component 2220 is a component) supports EHC for data transmission on the control plane. The processor 2204 may also include a circuit 2244 configured to communicate with the wireless communication device using EHC for data transmission on the control plane (CP) by, for example, sending and receiving wireless signals using the transceiver 2210. As already explained, the communication may include receiving Ethernet packets compressed using EHC from the UE and sending Ethernet packets compressed using EHC to the UE.

[0142] In some aspects, circuit 2240 is a unit for obtaining a signal from a wireless communication device indicating that the wireless communication device supports EHC for data transmission on a control plane, circuit 2242 is a unit for sending a response to the wireless communication device indicating that the wireless communication network supports EHC for data transmission on the control plane, and circuit 2244 is a unit for communicating with the wireless communication device on the control plane using EHC.

[0143] exist Fig. 22 In an example of , the computer-readable medium 2206 may include code 2250 for receiving and processing a signal indicating that the wireless communication device supports EHC for data transmission on the control plane. The computer-readable medium 2206 may also include code 2252 for generating and sending an indication that the wireless communication network (of which the network component 2220 is a component) supports EHC for data transmission on the control plane. The computer-readable medium 2206 may also include code 2254 for communicating with the wireless communication device using the EHC for data transmission on the control plane.

[0144] Fig.23 2304. Figure 1 , Figure 3 , Figure 4 and / or Figure 7 Any UE among the UEs shown in .

[0145] The overall architecture of the processing system 2314 may be similar to that in Fig. 22 , including a bus interface 2308, a bus 2302, a memory 2305, a processor 2304, and a computer-readable medium 2306. In addition, the wireless communication device 2300 may include a user interface 2312 and a transceiver 2310 for communicating with various other devices over a transmission medium (e.g., an air interface for communicating with network components). The processor 2304 as utilized in the wireless communication device 2300 may be used to implement any one or more of the processes described herein with respect to the operation of the wireless communication device.

[0146] In some aspects of the present disclosure, the processor 2304 may include circuits configured for various functions. For example, the processor 2304 may include circuits configured to send a signal to a wireless communication network (such as to a Figure 2Circuit 2342 may be configured to send a signal to the wireless communication device that supports EHC for data transmission on the control plane to the network component 2200 of the wireless communication device. Circuit 2342 may be configured to obtain a response from the wireless communication network indicating that the wireless communication network supports EHC for data transmission on the control plane. Circuit 2344 may be configured to communicate with the wireless communication network on the control plane using EHC by, for example, sending and receiving wireless signals using transceiver 2310. As already explained, communication may include sending Ethernet packets compressed using EHC to the network component and receiving Ethernet packets compressed using EHC from the network component.

[0147] In some aspects, circuit 2340 is a unit for sending a signal to a wireless communication network indicating that the wireless communication device supports EHC for data transmission on a control plane, circuit 2342 is a unit for obtaining a response from the wireless communication network indicating that the wireless communication network supports EHC for data transmission on a control plane, and circuit 2344 is a unit for communicating with the wireless communication network on a control plane using EHC.

[0148] exist Fig.23 In an example of , the computer-readable medium 2306 may include code 2350 for sending a signal to the wireless communication network indicating that the wireless communication device supports EHC for data transmission on the control plane. The computer-readable medium 2306 may also include code 2352 for obtaining a response from the wireless communication network indicating that the wireless communication network supports EHC for data transmission on the control plane. The computer-readable medium 2306 may also include code 2354 for communicating with the wireless communication network using the EHC for data transmission on the control plane.

[0149] The following provides an overview of examples of the present disclosure.

[0150] Example 1: A wireless communication device comprising: a transceiver; and a processor coupled to the transceiver, wherein the processor is configured to: send a signal to a wireless communication network indicating that the wireless communication device supports EHC for data transmission on a control plane; obtain a response from the wireless communication network indicating that the wireless communication network supports EHC for data transmission on the control plane; and communicate with the wireless communication network on the control plane using EHC.

[0151] Example 2: A wireless communication device according to Example 1, wherein the processor is further configured to: send the signal as a mobility management registration request message, the mobility management registration request message including an indication of support for EHC for data transmission on the control plane.

[0152] Example 3: The wireless communication device of Example 1 or 2, wherein the processor is further configured to obtain the response from the wireless communication network within a mobility management registration accept message.

[0153] Example 4: A wireless communication device according to Example 1, 2 or 3, wherein the processor is further configured to: send a request signal to the wireless communication network, the request signal including a request to use the EHC for data transmission on the control plane.

[0154] Example 5: A wireless communication device according to Example 1, 2, 3 or 4, wherein the processor is further configured to: send the request signal within a PDU session establishment request message.

[0155] Example 6: A wireless communication device according to Example 1, 2, 3 or 4, wherein the processor is further configured to: send the request signal within a PDU session modification message.

[0156] Example 7: A wireless communication device according to Example 1, 2, 3, 4, 5 or 6, wherein the processor is further configured to: send Ethernet packets compressed using EHC on the control plane to communicate with the wireless communication network.

[0157] Example 8: A wireless communication device according to Example 1, 2, 3, 4, 5, 6 or 7, wherein the processor is further configured to: receive Ethernet packets compressed using EHC on the control plane to communicate with the wireless communication network.

[0158] Example 9: A method for wireless communication used by a wireless communication device, the method comprising: sending a signal to a wireless communication network indicating that the wireless communication device supports EHC for data transmission on a control plane; obtaining a response from the wireless communication network indicating that the wireless communication network supports EHC for data transmission on the control plane; and communicating with the wireless communication network on the control plane using EHC.

[0159] Example 10: The method of Example 9, wherein sending the signal comprises sending a mobility management registration request message, the mobility management registration request message comprising an indication of support for EHC for data transmission on the control plane.

[0160] Example 11: The method of Example 9 or 10, wherein obtaining the response from the wireless communication network comprises receiving an indication of support for EHC within a mobility management registration accept message.

[0161] Example 12: The method according to Example 9, 10 or 11 further includes: sending a request signal to the wireless communication network, the request signal including a request for using the EHC for data transmission on the control plane.

[0162] Example 13: A method according to Example 9, 10, 11 or 12, wherein the request signal includes a PDU session establishment request message.

[0163] Example 14: A method according to Example 9, 10, 11 or 12, wherein the request signal includes a protocol data unit (PDU) session modification message.

[0164] Example 15: A method according to Example 9, 10, 11, 12 or 13, wherein communicating with the wireless communication network includes: sending Ethernet packets compressed using EHC to the wireless communication network on the control plane.

[0165] Example 16: A method according to Example 9, 10, 11, 12, 13, 14 or 15, wherein communicating with the wireless communication network includes: receiving Ethernet packets compressed using EHC from the wireless communication network on the control plane.

[0166] Example 17: A network component of a wireless communication network, the network component comprising: a network interface; and a processor coupled to the network interface, wherein the processor is configured to: obtain a signal from a wireless communication device indicating that the wireless communication device supports Ethernet Header Compression (EHC) for data transmission on a control plane; send a response to the wireless communication device indicating that the wireless communication network supports EHC for data transmission on the control plane; and communicate with the wireless communication device on the control plane using the EHC.

[0167] Example 18: A network component according to Example 17, wherein the processor is further configured to: obtain the signal as a mobility management registration request message, the mobility management registration request message including an indication of support for EHC for data transmission on the control plane.

[0168] Example 19: The network component of Example 17 or 18, wherein the processor is further configured to send the response to the wireless communication device within a mobility management registration accept message.

[0169] Example 20: A network component according to Example 17, 18 or 19, wherein the processor is further configured to: obtain a request signal from the wireless communication device, the request signal comprising a request to use the EHC for data transmission on the control plane.

[0170] Example 21: A network component according to Example 17, 18, 19 or 20, wherein the processor is further configured to: obtain the request signal within a protocol data unit (PDU) session establishment request message.

[0171] Example 22: A network component according to Example 17, 18, 19 or 20, wherein the processor is further configured to: obtain a signal including a request to use the EHC for data transmission within a protocol data unit (PDU) session modification message.

[0172] Example 23: A network component according to Example 17, 18, 19, 20, 21 or 22, wherein the processor is further configured to: send Ethernet packets compressed using EHC on the control plane to communicate with the wireless communication device.

[0173] Example 24: A network component according to Examples 17, 18, 19, 20, 21, 22 or 23, wherein the processor is further configured to: receive Ethernet packets compressed using EHC on the control plane to communicate with the wireless communication device.

[0174] Example 25: A method for wireless communication used by a network component of a wireless communication network, the method comprising: obtaining a signal from a wireless communication device indicating that the wireless communication device supports EHC for data transmission on a control plane; sending a response to the wireless communication device indicating that the wireless communication network supports EHC for data transmission on the control plane; and communicating with the wireless communication device on the control plane using the EHC.

[0175] Example 26: The method of Example 25, wherein obtaining the signal comprises receiving a mobility management registration request message including an indication of support for EHC for data transmission on the control plane.

[0176] Example 27: The method according to Example 25 or 26 further includes: obtaining a request signal from the wireless communication device, the request signal including a request for using the EHC for data transmission on the control plane.

[0177] Example 28: The method of Example 25, 26 or 27 further includes: sending an indication of acceptance of use of the EHC to the wireless communication device.

[0178] Example 29: The method of Example 25, 26, 27, or 28, wherein communicating with the wireless communication device on the control plane using EHC comprises sending Ethernet packets compressed using EHC on the control plane.

[0179] Example 30: A method according to Examples 25, 26, 27, 28 or 29, wherein communicating with the wireless communication device on the control plane using EHC includes: receiving Ethernet packets compressed using EHC on the control plane.

[0180] In the present disclosure, the word "exemplary" is used to mean "serving as an example, instance or illustration". Any implementation or aspect described herein as "exemplary" is not necessarily to be construed as being preferred or having advantages over other aspects of the present disclosure. Likewise, the term "aspect" does not require that all aspects of the present disclosure include the discussed features, advantages or modes of operation. The term "coupling" is used herein to refer to a direct coupling or an indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, objects A and C may still be considered to be coupled to each other, even if they are not physically directly in contact with each other. For example, a first object may be coupled to a second object, even if the first object has never been physically directly in contact with the second object. The terms "circuit" and "electronic circuit" are used in a broad sense, and are intended to include both hardware implementations of electronic devices and conductors (wherein these electronic devices and conductors, when connected and configured, enable the functions described in the present disclosure to be performed, and there is no limitation on the type of electronic circuit) and software implementations of information and instructions (wherein these information and instructions, when executed by a processor, enable the functions described in the present disclosure to be performed).

[0181] Can Figure 1-23 One or more of the components, steps, features and / or functions shown in the present invention may be rearranged and / or combined into a single component, step, feature or function, or may be embodied in several components, steps or functions. In addition, additional elements, components, steps and / or functions may be added without departing from the novel features disclosed herein. Figure 1 , 2 , 3, 4, 7, 10, 11, 14, 15, 16, 17, 22 and 23. The devices, equipment and / or components shown in the embodiments may be configured to perform one or more of the methods, features or steps described herein. The algorithms described herein may also be implemented in software and / or embedded in hardware.

[0182] It is understood that the specific order or hierarchy of steps in the disclosed methods is an illustration of exemplary processes. It is understood that the specific order or hierarchy of steps in these methods may be rearranged based on design preferences. The accompanying method claims present elements of the various steps in an example order and are not meant to be limited to the specific order or hierarchy presented unless expressly recited therein.

[0183] The previous description is provided to enable any person skilled in the art to implement the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the various aspects shown herein, but are given the full scope consistent with the language of the claims, wherein unless explicitly stated otherwise, reference to an element in the singular form is not intended to mean "one and only one", but to refer to "one or more". Unless otherwise explicitly stated, the term "some" refers to one or more. The phrase "at least one" referring to a list of items refers to any combination of those items, including a single member. As an example, "at least one of a, b, or c" is intended to cover: a; b; c; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure are expressly incorporated herein by reference, and are intended to be included in the claims, wherein these structural and functional equivalents are known or will be known to those skilled in the art. In addition, no disclosure herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly recorded in the claims.

Claims

1. A wireless communication device, comprising: Transceiver; as well as a processor coupled to the transceiver, wherein the processor is configured to: Sending a mobility management registration request signal to the wireless communication network for indicating that the wireless communication device supports Ethernet header compression (EHC) for data transmission on a control plane; obtaining, from the wireless communication network, a mobility management registration response indicating that the wireless communication network supports the EHC for data transmission on the control plane; sending a session establishment request signal including a request for a field length of an EHC context ID to the wireless communication network; obtaining, from the wireless communication network, a session establishment confirmation including an indication of the field length for the EHC context ID; and Data compressed using the EHC is transmitted to the wireless communication network on the control plane, the data including the EHC context ID configured according to the field length.

2. The wireless communication device according to claim 1, wherein: Each of the first uncompressed data packet and one or more subsequent compressed data packets includes the EHC context ID.

3. The wireless communication device according to claim 1, wherein: The processor is also configured to send the data compressed using the EHC to an external data network of the wireless communication network via an access and mobility management function AMF, a session management function SMF, and a user plane function UPF.

4. The wireless communication device according to claim 1, wherein: The processor is further configured to: sending a first portion of data compressed using EHC to a first external data network of the wireless communication network via an access and mobility management function AMF, a session management function SMF and a first user plane function UPF; as well as A second portion of the data compressed using the EHC is sent to a second external data network of the wireless communication network via the AMF, the SMF, and the second UPF, wherein the second portion of the data is sent using a different context ID.

5. The wireless communication device according to claim 1, wherein: The processor is further configured to send the session establishment request signal within a protocol data unit (PDU) session establishment request message.

6. The wireless communication device according to claim 1, wherein: The processor is further configured to send the session establishment request signal within a protocol data unit (PDU) session modification message.

7. The wireless communication device according to claim 1, wherein: The processor is further configured to send the data as Ethernet packets compressed using EHC.

8. The wireless communication device according to claim 1, wherein: The field length is 7 or 15 bits.

9. A method for wireless communication used by a wireless communication device, the method comprising: Sending a mobility management registration request signal to the wireless communication network for indicating that the wireless communication device supports Ethernet header compression (EHC) for data transmission on a control plane; obtaining, from the wireless communication network, a mobility management registration response indicating that the wireless communication network supports the EHC for data transmission on the control plane; sending a session establishment request signal including a request for a field length of an EHC context ID to the wireless communication network; obtaining, from the wireless communication network, a session establishment confirmation including an indication of the field length for the EHC context ID; and Data compressed using the EHC is transmitted to the wireless communication network on the control plane, the data including the EHC context ID configured according to the field length.

10. The method according to claim 9, wherein: Each of the first uncompressed data packet and one or more subsequent compressed data packets includes the EHC context ID.

11. The method according to claim 9, wherein: The sending of data compressed using EHC includes sending the data compressed using EHC to an external data network of the wireless communication network via an access and mobility management function AMF, a session management function SMF, and a user plane function UPF.

12. The method according to claim 9, wherein sending the data compressed using the EHC comprises: sending a first portion of data compressed using EHC to a first external data network of the wireless communication network via an access and mobility management function AMF, a session management function SMF and a first user plane function UPF; as well as A second portion of the data compressed using the EHC is sent to a second external data network of the wireless communication network via the AMF, the SMF, and the second UPF, wherein the second portion of the data is sent using a different context ID.

13. The method according to claim 9, wherein: The session establishment request signal includes a protocol data unit (PDU) session establishment request message.

14. The method according to claim 9, wherein: The session establishment request signal includes a protocol data unit (PDU) session modification message.

15. The method according to claim 9, wherein: The transmitting the data compressed using the EHC includes transmitting the data as Ethernet packets compressed using the EHC.

16. The method according to claim 9, wherein: The field length is 7 or 15 bits.

17. A network component of a wireless communication network, the network component comprising: Network interface; as well as a processor coupled to the network interface, wherein the processor is configured to: obtaining, from a wireless communication device, a mobility management registration request signal indicating that the wireless communication device supports Ethernet header compression (EHC) for data transmission on a control plane; sending, to the wireless communication device, a mobility management registration response indicating that the wireless communication network supports the EHC for data transmission on the control plane; obtaining, from the wireless communication device, a session establishment request signal including a request for a field length of an EHC context ID; sending a session establishment confirmation including an indication of a selected field length for the EHC context ID to the wireless communication device; and Data compressed using EHC is obtained from the wireless communication device on the control plane, the data including the EHC context ID configured according to the selected field length.

18. The network component of claim 17, wherein: Each of the first uncompressed data packet and one or more subsequent compressed data packets includes the EHC context ID.

19. The network component of claim 17, wherein: The processor is further configured to obtain the data compressed using the EHC from the wireless communication device via an access and mobility management function (AMF).

20. The network component of claim 19, wherein: The processor is further configured to obtain the data within at least two Ethernet flows having different context IDs.

21. The network component of claim 17, wherein: The processor is further configured to obtain the session establishment request signal in a protocol data unit (PDU) session establishment request message.

22. The network component of claim 17, wherein: The processor is further configured to obtain the session establishment request signal in a protocol data unit (PDU) session modification message.

23. The network component of claim 17, wherein: The processor is further configured to obtain the data as Ethernet packets compressed using EHC.

24. The network component of claim 17, wherein: The field length is 7 or 15 bits.

25. A method for wireless communication used by a network component of a wireless communication network, the method comprising: obtaining, from a wireless communication device, a mobility management registration request signal indicating that the wireless communication device supports Ethernet header compression (EHC) for data transmission on a control plane; sending, to the wireless communication device, a mobility management registration response indicating that the wireless communication network supports the EHC for data transmission on the control plane; obtaining, from the wireless communication device, a session establishment request signal including a request for a field length of an EHC context ID; sending a session establishment confirmation including an indication of a selected field length for the EHC context ID to the wireless communication device; and Data compressed using EHC is obtained from the wireless communication device on the control plane, the data including the EHC context ID configured according to the selected field length.

26. The method according to claim 25, wherein: Each of the first uncompressed data packet and one or more subsequent compressed data packets includes the EHC context ID.

27. The method according to claim 25, wherein: The obtaining of the data compressed using the EHC comprises: obtaining the data compressed using the EHC from the wireless communication device via an access and mobility management function AMF.

28. The method according to claim 27, wherein: The data is obtained within at least two Ethernet flows having different context IDs.

29. The method according to claim 25, wherein: The obtaining of data compressed using the EHC includes obtaining the data as Ethernet packets compressed using the EHC.

30. The method of claim 25, wherein: The field length is 7 or 15 bits.

Images