WO2020261181A1 - Transport de pdu à base ethernet pour dispositifs à connecter à un cœur 5g convergent par l'intermédiaire de réseaux d'accès filaire (wans) - Google Patents

Transport de pdu à base ethernet pour dispositifs à connecter à un cœur 5g convergent par l'intermédiaire de réseaux d'accès filaire (wans) Download PDF

Info

Publication number
WO2020261181A1
WO2020261181A1 PCT/IB2020/056033 IB2020056033W WO2020261181A1 WO 2020261181 A1 WO2020261181 A1 WO 2020261181A1 IB 2020056033 W IB2020056033 W IB 2020056033W WO 2020261181 A1 WO2020261181 A1 WO 2020261181A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdu
ethernet
header
network
transport
Prior art date
Application number
PCT/IB2020/056033
Other languages
English (en)
Inventor
Changzheng WU
David Ian Allan
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2020261181A1 publication Critical patent/WO2020261181A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2854—Wide area networks, e.g. public data networks
    • H04L12/2856—Access arrangements, e.g. Internet access

Definitions

  • the present disclosure relates generally to the transport of Protocol Data Units (PDUs), and more particularly, to Ethernet-based PDU transport methods for devices to connect to converged 5G Core networks through a Wireline Access Network (WAN).
  • PDUs Protocol Data Units
  • WAN Wireline Access Network
  • the Third Generation Partnership Project has defined both a 3GPP architecture and an untrusted non-3GPP architecture in for 5G phase 1 (release 15) in 3GPP TS 23.501 vf10:“5G System Architecture Accesses,” and in 3GPP TS 23.502vf10: “5G System Procedures.”
  • the 3GPP is also defining 5G phase 2 (release 16) including wireline and trusted non-3GPP access.
  • FIG. 1 illustrates type cases for 5G-RG devices (i.e. , both 5GC-capable and non-5GC capable), behind 5G-RG connected to 5GC through wireline access.
  • BBF BroadBand Forum
  • WAN Wireline Access Network
  • BBF SD-407 5G Fixed Mobile Convergence Study https://wiki. broadband- forum. org/display/BBF/SD-407+5G+Fixed+Mobile+Convergence+Study
  • both the 5G-RG (or 5G CPE), and the devices connected from behind the 5G-RG, are considered by both the 3GPP and the BBF.
  • Figure 2 illustrates how both 5G-RG, and devices behind the 5G-RG, are typically connected to 5GC through wireline access.
  • PDU transport related items are raised as key issues by both the 3GPP in TR23.716, and the BBF in SD-420.
  • Such key issues include, for example:
  • BBF TR-101 “Migration to Ethernet-Based Broadband Aggregation,” Issue 2 is a reference on Ethernet based wireline access network architecture.
  • the 5G PDU transport will have key 5G characteristics as defined in 3GPP TS 23.501 vf10:“5G System Architecture Accesses” to consider. These include:
  • PDU types i.e. , IP PDU type, Ethernet PDU type, and Unstructured PDU type
  • NAS Non-Access Stratum
  • VLAN Virtual Local Area Network
  • BBF SD-407 fails to provide a further flexible design or a comprehensive solution. It also fails to provide a design for a common architecture for both NAS signaling and PDU data transport while simultaneously supporting both 5G-RG and the devices behind 5G-RG.
  • Ethernet over Ethernet Currently, there is no direct Ethernet over Ethernet solution provided. In the IETF, a GRE tunnel over Ethernet, described in IETF RFC:“GRE Tunnel Bonding Protocol,” provides a GRE level aggression for fixed and mobile dual connection cases.
  • IP level transport Some proposals do exist for IP level PDU transport. For example, one solution uses IKE/IPSEC or TLS. [0008] Methods are required that are designed to support 5G PDU transport through Ethernet based wireline access network to a converged 5G core. Additionally, the 5G PDU transport method will be required to support:
  • IP PDU type IP PDU type, Ethernet PDU type, and Unstructured PDU type
  • 5G-RG and devices behind 5G-RG which may or may not be 5GC capable;
  • TR-23.716 raises the User Plane transport issue as issue #6. However, the discussion in TR-23.716 does not provide a solution for this issue. The discussion in TR-23.716 only indicates that the BBF will be responsible to specify how NAS messages are transported.
  • Embodiments of the present disclosure provide an Ethernet-based method for 5G PDU transport over wireline access network with which an end device, such as a user equipment (UE), for example, can use to connect to a converged 5G Core (5GC) network via the WAN.
  • an end device such as a user equipment (UE)
  • UE user equipment
  • 5GC converged 5G Core
  • the present disclosure provides an Ethernet-based method, implemented by a user equipment (UE), for transporting Protocol Data Units (PDUs) over a Wireline Access Network (WAN).
  • the method comprises receiving, at a PDU Transport layer executing on the UE, a PDU from a PDU Application layer executing on the UE, wherein the PDU is one of an Ethernet PDU and a non-Ethernet PDU, generating a PDU adaptation header, generating a PDU Ethernet packet comprising the PDU adaptation header based on whether the PDU is an Ethernet PDU or a non- Ethernet PDU, and sending the PDU Ethernet packet in an Ethernet frame to an Access Gateway Function (AGF).
  • AMF Access Gateway Function
  • the present disclosure also provides an Ethernet-based method, implemented by an Access Gateway Function (AGF) executing at a base station, for transporting Protocol Data Units (PDUs) to user equipment (UE) over a Wireline Access Network (WAN).
  • AGF Access Gateway Function
  • the method comprises receiving, at a PDU Transport layer of the AGF, a PDU from a PDU Application layer executing on the AGF, wherein the PDU is one of an Ethernet PDU and a non-Ethernet PDU, generating a PDU adaptation header, generating a PDU Ethernet packet comprising the PDU adaptation header based on whether the PDU is an Ethernet PDU or a non- Ethernet PDU, and sending the PDU Ethernet packet in an Ethernet frame to the UE.
  • AGF Access Gateway Function
  • a user equipment in a wireless communication network comprises an interface circuit configured for communication with one or more serving cells the wireless communication network, and a processing circuit.
  • the processing circuit is configured to receive, at a PDU Transport layer executing on the UE, a PDU from a PDU Application layer executing on the UE, wherein the PDU is one of an Ethernet PDU and a non-Ethernet PDU, generate a PDU adaptation header, generate a PDU Ethernet packet comprising the PDU adaptation header based on whether the PDU is an Ethernet PDU or a non-Ethernet PDU, and send the PDU Ethernet packet in an Ethernet frame to an Access Gateway Function (AGF).
  • AMF Access Gateway Function
  • the present disclosure provides a network node in a serving cell of the wireless communication network.
  • the network node which may be a base station, for example, comprises an interface circuit configured for communication with one or more serving cells the wireless communication network and a processing circuit.
  • the processing circuit is configured to receive, at a PDU T ransport layer of the AGF, a PDU from a PDU Application layer executing on the AGF, wherein the PDU is one of an Ethernet PDU and a non-Ethernet PDU, generate a PDU adaptation header, generate a PDU Ethernet packet comprising the PDU adaptation header based on whether the PDU is an Ethernet PDU or a non-Ethernet PDU, and send the PDU Ethernet packet in an Ethernet frame to the UE.
  • the present disclosure also provide corresponding non-transitory computer readable media, circuitry, and computer program products configured to perform the methods described herein according to the present embodiments.
  • Figure 1 is a functional block diagram illustrating how the 5G-RG, as well as both 5GC-capable and non-5GC capable devices behind the 5G-RG, typically connect to the 5GC via wireline access.
  • Figure 2 is a functional block diagram illustrating the 5G-RG and devices behind 5G-RG connected to the 5GC via wireline access.
  • Figure 3 is a functional block diagram illustrating a network configured according to one embodiment of the present disclosure.
  • Figure 4 is a functional block diagram illustrating a network configuration for 5G- RG, and 3GPP devices behind the 5G-RG, according to one embodiment of the present disclosure.
  • Figure 5 is a functional block diagram illustrating a PDU transport multiplex architecture for 5G-RG, and 3GPP devices behind the 5G-RG, according to one embodiment of the present disclosure.
  • Figure 6 is a functional block diagram illustrating a multiple PDU architecture according to one embodiment of the present disclosure, where multiple different types of PDU transport usage are present for an end device, such as a UE.
  • FIG. 7 is a functional block diagram illustrating multiple Quality of Service (QoS) bearers and a QoS multiplex architecture according to one embodiment of the present disclosure, with each data bearer having one or more QoS Flow multiplex for given PDU session.
  • QoS Quality of Service
  • FIG. 8 is a functional block diagram illustrating an end device (e.g., a UE) and an Access Gateway Function (AGF) executing on a network node, each configured with a two-layer model including a PDU Application layer and a PDU Transport layer according to one embodiment of the present disclosure.
  • AMF Access Gateway Function
  • Figures 9A and 9B are functional block diagrams illustrating the PDU payloads of an Ethernet-type PDU packet and a non-Ethernet-type PDU packet, respectively, according to one embodiment of the present disclosure.
  • Figures 10A-10B illustrate an Ethernet-type PDU packet and a non-Ethernet-type PDU packet according to one embodiment of the present disclosure.
  • Figure 1 1 illustrates a PDU Ethernet packet formed according to one
  • Figure 12 illustrates a PDU Ethernet packet on a network where a 5G-RG functions as an end device according to one embodiment of the present disclosure.
  • Figure 13 illustrates a PDU Ethernet packet on a network where a non-3GPP device is behind an 5G-RG according to one embodiment of the present disclosure.
  • Figure 14 illustrates a PDU Ethernet packet on a network where a 3GPP device uses non-Ethernet type PDU according to one embodiment of the present disclosure.
  • Figure 15 illustrates a PDU Ethernet packet on a network where a 3GPP device uses Ethernet PDU usage type, and where the 3GPP device has one or more sub devices behind it according to one embodiment of the present disclosure.
  • Figure 16 is a flow diagram illustrating a method, implemented at an end device such as a UE, for example, for transporting PDU Ethernet packets according to one embodiment of the present disclosure.
  • Figure 17 is a flow diagram illustrating a method, implemented at an AGF executing at a network node, such as a base station, for example, for transporting PDU Ethernet packets according to one embodiment of the present disclosure.
  • Figure 18 is a schematic block diagram of an exemplary end device, such as a UE, configured according to one embodiment of the present disclosure.
  • Figure 19 is a functional block diagram of an exemplary end device, such as a UE, configured according to one embodiment of the present disclosure.
  • Figure 20 is a schematic block diagram of an exemplary 5G-RG device, such as a network node, configured according to one embodiment of the present disclosure.
  • Figure 21 is a functional block diagram of an exemplary 5G-RG device, such as a network node, configured according to one embodiment of the present disclosure.
  • Figure 22 is a functional block diagram of an end device, such as a UE, configured according to one embodiment of the present disclosure.
  • Figure 23 is a functional block diagram of a 5G-RG device, such as a network node, configured according to one embodiment of the present disclosure.
  • Figure QQ1 illustrates an exemplary wireless network according to one embodiment of the present disclosure.
  • Figure QQ2 illustrates a UE configured according to one embodiment of the present disclosure.
  • Figure QQ3 is a schematic block diagram illustrating a virtualization environment in which functions implemented by some embodiments of the present disclosure may be virtualized.
  • Figure QQ4 illustrates a telecommunication network connected via an intermediate network to a host computer according to one embodiment of the present disclosure.
  • Figure QQ5 illustrates a host computer communicating via a base station with a UE over a partially wireless connection in accordance with some embodiments of the present disclosure.
  • Figure QQ6 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • Figure QQ7 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • Figure QQ8 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • Figure QQ9 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • Figure 1 illustrates a wireless communication network 10 according to the NR standard currently being developed by Third Generation Partnership Project (3GPP).
  • 3GPP Third Generation Partnership Project
  • the wireless communication network 10 comprises one or more base stations 100 providing service to user equipment (UEs) 200 in respective cells 20 of the wireless communication network 10.
  • the base stations 100 are also referred to as Evolved NodesBs (eNBs) and gNodeBs (gNBs) in 3GPP standards.
  • eNBs Evolved NodesBs
  • gNBs gNodeBs
  • a typical wireless communication network 10 comprises many cells 20 served by many base stations 100.
  • One feature of NR networks is the ability of the base stations 100 to transmit and/or receive on multiple beams 30 in the same cell 20.
  • Figure 1 illustrates two beams 30, although the number of beams 30 in a cell 20 may be different.
  • the UEs 200 may comprise any type of equipment capable of communicating with the base station 100 over a wireless communication channel.
  • the UEs 200 may comprise cellular telephones, smart phones, laptop computers, notebook computers, tablets, machine-to-machine (M2M) devices (also known as machine type communication (MTC) devices), embedded devices, wireless sensors, or other types of wireless end user devices capable of communicating over wireless communication networks 10.
  • M2M machine-to-machine
  • MTC machine type communication
  • embedded devices embedded devices
  • wireless sensors or other types of wireless end user devices capable of communicating over wireless communication networks 10.
  • an end device such as a user equipment (UE) or a 5G-RG functioning as an end device, for example
  • UE user equipment
  • 5G-RG functioning as an end device
  • the present disclosure provides an Ethernet PDU method and a PDU Ethernet header.
  • the PDU header facilitates Ethernet tunneling of a PDU payload.
  • embodiments of the present disclosure also leverages and extends the Shim method by adding an extended Shim header in an Ethernet part of the PDU payload.
  • the present embodiments provide a common PDU adaption design for both the Ethernet and the Shim methods to support concerned 5G characteristics.
  • Such characteristics include, but are not limited to, multiple PDU sessions, multiple QoS bearers, 5G QoS flow mapping and control (e.g. reflective QoS), and multiple PDU types (Ethernet, Unstructured and IP type PDU).
  • the common PDU adaption design further supports PDU transport both for data and NAS signaling, as well as device relay and multiple device multiplex, where the devices that are behind a 5G-RG include both 3GPP devices (i.e. , 5GC-capable devices) and non-3GPP devices (i.e., non 5GC-capable devices).
  • 3GPP devices i.e. , 5GC-capable devices
  • non-3GPP devices i.e., non 5GC-capable devices
  • the Ethernet based PDU transport of the present disclosure can operate with the existing VLAN tag model, which is defined in BBF TR-101 :“Migration to Ethernet-Based Broadband Aggregation, Issue 2,” for VLAN routing isolation.
  • the VLAN tag model can also be applied to 3GPP devices behind a 5G-RG.
  • the present embodiments can support multiple QoS bearers for PDU transport.
  • Network architectures according to the present embodiments are illustrated in Figures 4-7. As seen in these figures, the architectures can support multiple devices behind a 5G-RG. Additionally, the architectures can support roaming scenarios in which one or more roaming 3GPP devices can connect to a separate Access Function
  • the architectures of the present embodiments include the following nodes:
  • an end device e.g., a 5G-RG device or a 3GPP device communicatively
  • a relay node e.g., a 5G-RG device
  • Figure 4 is a functional block diagram illustrating a PDU multiplex architecture of the present embodiments showing a 5G-RG device, multiple AGF communicatively connected to corresponding 5G Cores (5GCs), a plurality of 3GPP devices behind the 5G-RG, and one or more non-3GPP devices behind the 5G-RG.
  • 5GCs 5G Cores
  • FIG. 5 is a functional block diagram illustrating the PDU transport multiplex architecture of the present disclosure for 5G-RG devices, and for 3GPP devices behind the 5G-RG devices.
  • the AGF can identify the 3GPP and 5G-RG devices by their respective Media Access Control (MAC) addresses.
  • MAC Media Access Control
  • the MAC address of the 5G-RG and a relay flag is also provided.
  • FIG. 6 is a functional block diagram illustrating a multiple PDU architecture according to another embodiment of the present disclosure.
  • This embodiment provides an end device, such as a 5G-RG device or a 3GPP device connected to the 5G-RG device, with the ability to transport PDU payloads to an AGF in four different ways.
  • the present embodiments can identify multiple PDUs by the PDU usage type.
  • PDU data can also be identified by a PDU session ID.
  • a VLAN ID tag model can also be applied according to the embodiment of Figure 6.
  • multiple PDUs can be identified by a VLAN ID (i.e., the C-VID in a C-tag model) or multiple VLAN IDs (i.e., the S-VID in an S-tag mode) can be applied to identify the multiple PDUs on a per-PDU basis.
  • FIG. 7 is a functional block diagram illustrating multiple QoS bearers and a QoS multiplex architecture.
  • multiple QoS bearers are supported and shown with each data bearer having one or more QoS Flows multiplexed for given PDU session.
  • each QoS bearer is marked by a VLAN priority, while the NAS signaling has a default bearer. More particularly, a signaling bearer is configured for NAS signaling.
  • embodiments of the present disclosure define a two-layer model. These layers are a PDU Application layer and a PDU Transport layer, and may be provided in an end device or the AGF.
  • the PDU Application layer is configured to provide a PDU payload and PDU control information to the PDU Transport layer.
  • the PDU Transport layer processes the PDU payload according to the present embodiments, and sends the PDU payload in a PDU Ethernet packet to another device.
  • the PDU Transport layer is configured to receive a PDU payload from the PDU Transport layer of another device, process the PDU payload according to the present embodiments, and send the processed PDU payload to the PDU Application layer.
  • the PDU control information is used by the PDU Transport layer to process and transport the PDU payload according to the present embodiments.
  • the PDU payload may belong to PDU data of any PDU types as defined by 3GPP standard. These are the IP type PDU, the Ethernet type PDU, and the
  • the PDU payload may comprise the NAS signaling to be transported.
  • the PDU payload processed according to the present disclosure can have different formats.
  • Figure 9A illustrates a PDU payload for an Ethernet type PDU according to one embodiment.
  • the PDU payload of this embodiment includes an Ethernet header.
  • Figure 9B illustrates a PDU payload for a non-Ethernet PDU according to one embodiment.
  • Such non-Ethernet type PDUs include, for example, an IP packet, Unstructured data, and NAS signaling.
  • the PDU Transport layer is configured to process, transmit, and receive a PDU-supported Ethernet packet (referred to herein as “PDU Ethernet packet”) for a PDU payload. Moreover, the PDU Transport layer is configured to perform its functions using either of the following two methods, each of which has a common PDU adaption design.
  • Shim method In this method, the present embodiments insert a PDU adaption header of a shim header behind an Ethernet header of a PDU payload;
  • Ethernet PDU method insert a PDU adaption header of an Ethernet PDU header in front of an Ethernet packet of a PDU payload to provide an Ethernet PDU tunnel for the Ethernet packet.
  • Ethernet PDU header includes a standard Ethernet header and a PDU header.
  • the PDU Transport layer of the present embodiments has an underlying Ethernet transport sub-layer.
  • This sub-layer is configured to transport an Ethernet frame (referred to herein as a“PDU Ethernet frame”) carrying PDU Ethernet packets on the Ethernet based access network as defined in BBF TR-101 :“Migration to Ethernet-Based Broadband Aggregation,” Issue 2.
  • the PDU Transport layer is also configured for VLAN processing as well.
  • the PDU Transport layer inserts a PDU adaption header of a Shim header behind the Ethernet header of PDU payload.
  • the values in the Shim header are populated as follows:
  • PDUid The PDUid value is set to the PDU session id. In cases where PDU usage indicates NAS signaling transport, however, the PDUid value is not present.
  • QFinfo The QFInfo value is set to the QoS Flow information. However, in cases where PDU usage indicates NAS signaling transport, the QFinfo value is not present.
  • SMAC Address Field This field contains the Source MAC address.
  • the PDU Transport layer uses the SMAC address for relay operations in cases where a 3GPP device is connected behind a 5G-RG device.
  • DMAC Address Field This field contains the Destination MAC address.
  • the PDU Transport layer uses the DMAC address for relay operations in cases where a 3GPP device is connected behind a 5G-RG device.
  • PDU Usage Flags The PDU Usage Flags are set to indicate the PDU usage value.
  • Ethertype Field The Ethertype Field is set to the Ethertype value contained in the original Ethernet header.
  • the Ethertype values in the original Ethertype header are assigned by (IANA) and can be any value so long as the values respectively indicate:
  • Figures 10A and 10B illustrate how PDU Ethernet packets are generated according to one embodiment of the present disclosure.
  • Figure 10A illustrates the format of a PDU Ethernet packet generated for an Ethernet type PDU.
  • the PDU payload of Figure 10A is an Ethernet type PDU
  • the PDU payload already has an Ethernet header (i.e., Ethernet (Shim), DMAC, SMAC).
  • the PDU T ransport layer simply inserts the PDU adaption header of the Shim header behind the Ethernet header of PDU payload.
  • FIG 10B illustrates the format of a PDU Ethernet packet generated for a non- Ethernet PDU type.
  • the PDU payload is of a non-Ethernet PDU type
  • there is no Ethernet header i.e., Ethernet (Shim), DMAC, SMAC). Therefore, the PDU Transport layer of the present disclosure first generates and adds an Ethernet header to the non-Ethernet PDU type PDU payload, and constructs an Ethernet packet for the PDU payload.
  • the PDU adaption header of a Shim header is then inserted by the PDU Transport layer behind the newly-generated Ethernet header of the PDU payload.
  • the PDU Transport layer sets the following values in the Ethernet header when it adds the Ethernet header.
  • Ethertype Field The Ethertype Field is set to one of the following values:
  • SMAC address Field The SMAC address is set to the MAC address of the node hosting the PDU Transport layer.
  • a node may be, for example, an end device or and an AGF.
  • the DMAC address is set to the MAC address of the destination node or the broadcast MAC address.
  • a PDU adaption header of an Ethernet PDU header is added in front of the Ethernet packet of the PDU payload, thereby providing an Ethernet PDU tunnel for the Ethernet packet.
  • the Ethernet PDU header includes both a standard Ethernet header and a PDU header.
  • values in the PDU header part of the Ethernet PDU header are set as follows:
  • PDUid The PDUid value is set to the PDU session id. In cases where the PDU usage flag indicates NAS signaling transport, however, the PDUid value is not present.
  • QFinfo The QFInfo value is set to the QoS Flow information. In cases where PDU usage indicates NAS signaling transport, the QFinfo value is not present.
  • PDU Usage Flags The PDU Usage Flags are set to indicate the PDU usage value.
  • PDU type Field The PDY type Field is set to a value indicating‘Raw Ethernet.” [0074] The values in the Ethernet header part of the Ethernet PDU header are set as follows:
  • This field contains the MAC address of the node
  • Ethernet header e.g. the 5G-RG device.
  • DMAC Address Field This field contains the MAC address of the AGF or the broadcast MAC address.
  • Ethertype Field The Ethertype Field is set to a value indicating that an Ethernet PDU is inside.
  • FIG. 1 1 illustrates the structure of the Ethernet PDU packet generated according to the Ethernet PDU method.
  • the PDU payload is not an Ethernet packet. Therefore, generating the Ethernet PDU packet in this method is similar to generating an Ethernet PDU packet according to the previously described Shim method for a non-Ethernet PDU type.
  • the PDU Transport layer adds an Ethernet header in front of the PDU payload and constructs an Ethernet packet for the PDU payload.
  • the PDU Transport layer sets the values of the Ethernet header as follows:
  • Ethertype Field The Ethertype Field is set to one of the following values:
  • SMAC address Field The SMAC address is set to the MAC address of the node hosting the PDU Transport layer.
  • a node may be, for example, an end device or and an AGF.
  • the DMAC address is set to the MAC address of the destination node or the broadcast MAC address. Relay operation on a relayed PDU Ethernet packet
  • the 5G-RG device configures the 5G-RG device to function as a relay node for one or more 3GPP devices that are connected to it.
  • the relay node processes the PDU adaption header as follows when the PDU Ethernet packet traverses the relay node.
  • the relay node processes the PDU adaption header as follows when the PDU Ethernet packet traverses the relay node.
  • the relay node the relay node:
  • the relay node binds the 3GPP device MAC
  • the reference MAC address can be, for example, the SMAC address in the Ethernet header when using the Shim method, or in the inner Ethernet header when using the Ethernet PDU method.
  • the relay node locates the reference MAC address from the DMAC address of the corresponding header. The relay node will then recover the MAC address of the 3GPP device from the relay node MAC address based on the stored binding of the reference MAC address and the MAC address of the 3GPP device.
  • the relay node sets the SMAC address in the Shim header to its own MAC address.
  • the relay node is configured to intercept other fields in the PDU adaption header. For example, in cases where the relay node knows the PDUid, the relay node can tag different S-VID for the Ethernet frame for the 3GPP device(s) connected behind the 5G-RG device functioning as the relay node. Additionally, in some embodiments, the relay node is configured to re calculate the CRC. [0078] In at least one embodiment of the present disclosure, a 3GPP device connected behind a 5G-RG device is configured to establish an Ethernet type PDU. In these cases, the 3GPP device can function as a relay node for one or more sub-devices connected behind the 3GPP device. Therefore, according to embodiments of the present disclosure, both the 3GPP device and 5G-RG device can be configured to function as relay nodes.
  • the present disclosure also provides a common PDU adaption design defined to support multiple PDU transport. This includes, but is not limited to, PDU NAS signaling transport, PDU data transport, and multiple PDU session support for PDU data transport.
  • the present disclosure configures the PDU adaption header to include a PDU usage flag.
  • the PDU usage flags which are defined in more detail later, control the handling of the PDU Ethernet packet by the PDU
  • the PDU usage flag ensures that the PDU Transport layer will handle the PDU Ethernet packet in a manner that corresponds to the value of the PDU usage flag).
  • embodiments of the present disclosure support the multiple different PDU types defined in 3GPP TS 23.501 vf10:“5G System
  • the PDU Types supported by the embodiments of the present disclosure include IP type PDU, Ethernet type PDU, and Unstructured type PDU.
  • IP type PDU IP type PDU
  • Ethernet type PDU Ethernet type
  • Unstructured type PDU different types of PDU payloads are uniformly processed as Ethernet before transport.
  • embodiments of the present disclosure include the PDUid field in the PDU Adaption header.
  • the PDUid field carries a value that identifies the PDU data of a PDU session.
  • the multiple PDU method described herein is suitable to operate with Ethernet transport sub-layer isolation (e.g., by using VLAN tagging).
  • embodiments of the present disclosure also provide a common PDU transport method capable of supporting both PDU data and NAS signaling.
  • the present disclosure defines the following field values.
  • Ethernet payload A field set to NAS signaling, which will be transported directly over Ethernet, or NAS signaling over Ethernet (NASoE); and
  • Ethernet type A field set to either an EAPoL value for NAS signaling over EAP, or to an NASoE value (i.e.,“Ethertype for NAS signaling over Ethernet (NASoE)”) to indicate NAS signaling over Ethernet.
  • EAPoL value for NAS signaling over EAP
  • NASoE value i.e.,“Ethertype for NAS signaling over Ethernet (NASoE)
  • the present disclosure sets the PDU usage flag to indicate NAS signaling.
  • the PDU usage flag is set to NAS signaling, the PDUid and the QFinfo fields, as previously stated, are not used. Thus, they are not set by the PDU T ransport layer of the present embodiments.
  • Embodiments of the present disclosure also support multiple QoS bearers (QB) for both PDU NAS signaling transport and PDU data transport.
  • QB QoS bearers
  • the PDU T ransport layer is configured to set different VLAN priority values for the Ethernet frames.
  • the VLAN priority value can be tagged along with the VLAN ID value tagged in the S-tag, C-tag model defined in BBF TR-101 :“Migration to Ethernet-Based Broadband Aggregation,” Issue 2.
  • the VLAN priority value can be tagged even when the VLAN ID value (or zero value) is not tagged. This is because the VLAN priority value is typically tagged at the beginning by the end device and usually remains unchanged throughout processing.
  • the present embodiments set a VLAN priority value for the Ethernet frame carrying the PDU data according to a“QoS flow to QoS bearer (QFB) mapping.”
  • QFB QoS bearer
  • Such a mapping links a QFI to a bearer ID (i.e. VLAN priority), and stores the links in a QFB mapping table that is managed by the PDU Application layer.
  • the PDU Application layer provides both a bearer ID and QFB mapping via the PDU control information, as well as the PDU data to the PDU Transport layer.
  • the PDU Transport layer sets the provided VLAN priority values for the Ethernet frame.
  • the present disclosure also defines a QFinfo field in the PDU adaption header.
  • the QFinfo field supports QoS flow multiplex, and controls the QoS flow on a QoS bearer, which is tagged by a VLAN priority value as defined in 3GPP TS37.324vf10:“Service data adaption protocol:
  • embodiments of the present disclosure also provide an entire SDAP protocol as defined in 3GPP TS37.324vf10:“Service data adaption protocol: SDAP.”
  • embodiments of the present disclosure support the following QoS flow functions.
  • the QFinfo field in the PDU adaption header comprises a QFI.
  • the QFI is which is used to identify a given QoS Flow in a QoS flow multiplex case.
  • one embodiment sets the QFinfo field in PDU adaption header to contain a value that indicates either a Reflective QoS Indication (RQI) or a Reflective QoS flow to DRB mapping Indication (RDI) in a downlink PDU Ethernet packet to indicate reflective QoS.
  • RQI Reflective QoS Indication
  • RDI DRB mapping Indication
  • the PDU Transport layer provides the QFB mapping to the PDU Application layer via the PDU control information.
  • the PDU Application layer will release the mapping, and then indicate the end of the QFB mapping to the PDU Transport layer via the PDU control information.
  • the QFinfo field in the PDU adaption header may have a C-flag in the uplink PDU Ethernet packet indicating the end of the QFB mapping.
  • the PDU Transport layer indicates the end via PDU control
  • the common PDU adaption design of the present disclosure supports a multiple devices model.
  • a multiple devices model In one such model:
  • a 5G-RG device functions as an end device for non-Ethernet type PDU in
  • a 5G-RG device functions as an end device for non-3GPP devices connected behind it. In these cases, there are multiple devices including the 5G-RG device and multiple non-3GPP devices using the 5G-RG device as a relay node.
  • One or more 3GPP devices are behind a 5G-RG device in cases where
  • the 5G-RG device may provide separate access approaches for the 3GPP devices and non-3GPP devices.
  • the 5G-RG device may provide this support, for example, by using different Wi-Fi SSIDs (e.g., a private SSID and a public SSID).
  • a 5GC-capable device can operate as a non-3GPP device behind a 5G-RG.
  • the 5G-RG device of the present embodiments is also configured to establish an Ethernet type PDU for an Ethernet-based non-3GPP device before the non-3GPP device can be connected to the 5GC.
  • the 5G-RG device can provide an Ethernet relay function for a 3GPP device behind the 5G-RG device before the 5G-RG device can establish its own PDU session to 5GC.
  • the 5G-RG is configured to set a relay flag during processing in the PDU Transport layer for an Ethernet frame received from a 3GPP device associated access (e.g. via a public SSID).
  • a 3GPP device operating according to the present embodiments is configured to establish an Ethernet type PDU.
  • the 3GPP device functions as relay node for one or more sub-devices behind the 3GPP device, in which the sub-devices are non-3GPP capable devices (i.e., non-3GPP devices).
  • 5G-RG device acting as an end device for non-Ethernet type PDU is configured to establish an Ethernet type PDU.
  • a 3GPP device operating according to the present embodiments is configured to establish an Ethernet type PDU.
  • the 3GPP device functions as relay node for one or more sub-devices behind the 3GPP device, in which the sub-devices are non-3GPP capable devices (i.e., non-3GPP devices).
  • Figure 12 is a functional block diagram illustrating a PDU Ethernet packet on a network model.
  • the 5G-RG device sets the following fields in the outer Ethernet header.
  • 5G-RG device acting as an end device for nonSGPP devices behind the 5G-RG device
  • the present embodiments also configure a 5G-RG device to function as an end device for an Ethernet type PDU.
  • a 5G-RG device can be multiple Ethernet- based non-3GPP devices behind the 5G-RG device. All the non-3GPP devices, as well as the 5G-RG device, share the same Ethernet type PDU of the 5G-RG device, which are identified by the 5G-RG MAC address present in the PDU adaption header in the PDU Transport layer.
  • Figure 13 is a functional block diagram illustrating a PDU Ethernet packet on a network model.
  • each 3GPP device behind a 5G-RG device has an individual identifier in the AGF.
  • each 3GPP device will also be identified in the AGF by the corresponding 5G-RG device to which it is attached. Such identification can be used according to the present embodiments for charging, or for location and control purposes, for example.
  • a network operator may not want all 5G-RG devices to provide publicly available services. In these cases, the network operator may allow only some of the 5G-RG devices accessible to the public to provide relay function for 3GPP devices behind it. In these cases, the 5G-RG devices must provide their respective MAC addresses to be authenticated when they perform relay procedures for the 3GPP devices to the 5GC.
  • each 3GPP device is identified by its MAC address present in the PDU Transport layer. According to the present embodiments, the MAC address can be:
  • the PDU Transfer layer is configured according to the present embodiments to utilize the relay flag to determine whether an end device behind the 5G- RG device is a 3GPP device. If not, the end device is treated as a non-3GPP device for an Ethernet type PDU.
  • Figure 14 is a functional block diagram illustrating a PDU Ethernet packet on a network model for a 3GPP device utilizing a non-Ethernet type PDU.
  • a 3GPP device uses an Ethernet type PDU.
  • the 3GPP device can function as a relay device for any sub-devices that are behind the 3GPP device.
  • Such devices can include, for example, non-3GPP devices.
  • Each sub-device behind a 3GPP device is identified by its MAC address present in the PDU Transport layer. Further, each 3GPP device is also identified by its 5G-RG MAC address present in the PDU adaption header in PDU Transport layer.
  • Figure 15 is a functional block diagram illustrating a PDU Ethernet packet on a network model for 3GPP devices using an Ethernet PDU usage type and with one or more sub-devices behind it.
  • the Ethernet transport sub-layer is used to transport Ethernet frames carrying PDU payloads on an Ethernet-based access network as defined in BBF TR-101 :“Migration to Ethernet-Based Broadband
  • IEEE Std 802 IEEE Standard for Local and Metropolitan Area Networks:
  • IEEE Std 802.1 Q IEEE Standard for Local and metropolitan area networks-- Bridges and Bridged Networks, 2014
  • IEEE Std 802.1 P IEEE Standard for Local and metropolitan area networks: AN Layer 2 QoS/CoS Protocol for Traffic Prioritization
  • IEEE Std 802.1 ad IEEE Standard for Local and Metropolitan Area Networks— Virtual Bridged Local Area Networks— Provider Bridges.
  • the Ethernet transport sub-layer is configured to provide services and interface functions so that an upper PDU Ethernet packet received from the PDU Transport layer can be constructed as an Ethernet frame so it can be communicated over the WAN between the end device and the AGF.
  • the Ethernet transport sub-layer includes wireline layer 1 and the underlying MAC of layer 2. In at least one embodiment, the Ethernet transport sub-layer will also support VLAN.
  • the end device To Initiate Ethernet communications, the end device first sends an Ethernet broadcast frame with the destination MAC address (i.e., the DMAC address) set to OXfffff.
  • the Ethernet broadcast frame traverses the Ethernet-based layer network before arriving at the AGF. Additionally, the Ethernet broadcast frame may have VLAN tagged for routing isolation. The AGF will answer the Ethernet broadcast frame so that the Ethernet communications can continue with both MAC address as endpoints.
  • Ethernet communications both the end device and the AGF will handle the PDU Ethernet packet, as will be described in more detail later. Further, an Ethernet frame with new Ethertype defined according to the present embodiments is able to traverse legacy access networks when the VLAN is used.
  • embodiments of the present disclosure can apply a C-tag model in a user port between the 5G-RG device and an access network node, especially in the case of NAS signaling transport.
  • per-user C-VID can be linked to the wireline users (the 5G-RG of the wireline) in the AGF.
  • the 5G-RG MAC address can be bound to the C-VID in the record in the AGF, as previously stated.
  • the same C-VID can be used for the Ethernet frame.
  • an S-tag model can be applied to support VLAN level isolation for Ethernet frames carrying the PDU data of multiple PDU sessions.
  • different S-VIDs can be tagged for Ethernet frames carrying the PDU data of different PDU sessions.
  • the 5G-RG device is configured according to the present disclosure to apply VLAN tags for the 3GPP device. This includes, for example, applying a C-tag model for a PDU session transport for the 3GPP device, and applying a C-tag or an S-tag model for the Ethernet frames carrying PDU data of multiple PDU sessions.
  • the 5G-RG device can apply an S-tag model on a per- PDU session basis for the 3GPP devices since the 5G-RG device functioning as a relay node can intercept and operate on the PDU adaption header as previously stated.
  • a 5G-RG device can tag different S-VIDs for different Ethernet frames carrying PDU data of different PDU sessions for the 3GPP devices.
  • each 3GPP device may have its own C-VID and its own AGF, especially considering that each 3GPP device may be associated with a different Public Land Mobile Network (PLMN).
  • PLMN Public Land Mobile Network
  • the 3GPP devices could be assigned, according to the present embodiments, their own C-VIDs using a DHCP method. For example, before a 3GPP device can communicate to an AGF, it can send a DHCP message with an option/60 or option125 extension including its PLMN ID so that a different C-VID may be assigned to the 3GPP device. Once the C-VID is received, the 3GPP device will communicate with its AGF and be routed using its own assigned C-VID.
  • the present embodiments tag the VLAN priority value for an Ethernet frame received from a 3GPP device (as well as from a 5G-RG device when it functions as an end device). Such tagging occurs even in cases where the VLAN ID is not applied. The VLAN priority value will generally remain unchanged.
  • the VLAN priority is mandatory for multiple QoS bearer support.
  • VLAN ID tagging is mandatory in the Shim method for Ethernet PDU type transport where the DMAC in the Ethernet header is set to the MAC address of any destination that is different from the AGF.
  • the VLAN is used to provide L2 routing/isolation so that the Ethernet frame can arrive at the correct AGF.
  • Embodiments of the present disclosure provide the following nodes:
  • the AGF is configured to support the previously described Ethernet PDU method for Ethernet-based PDU transport, in which an Ethernet PDU header is added in front of an Ethernet packet of a PDU payload.
  • the AGF is also configured to support the previously described Shim method for Ethernet-based PDU transport, in which a Shim header is inserted behind the Ethernet header.
  • the AGF node is further configured is able to receive PDU Ethernet packets from an end device. More particularly, according to the present embodiments, the AGF node is configured to:
  • the AGF is configured to process a relay flag set in the PDU adaption header, which indicates the relay case.
  • the AGF is configured to extract the PDU payload according to the PDU Ethernet packet definition for NAS signaling transport, and determine the end device MAC address.
  • the AGF is configured according to the present embodiments to support multiple PDUs for the data type PDU (i.e., the IP type PDU, the Ethernet type PDU, and the Unstructured type PDU).
  • the PDU Transport layer extracts the PDU payload according to PDU Ethernet packet definition for the corresponding PDU type, and identifies the PDU session via the PDUid field located in the PDU adaption header.
  • the PDU Application layer is also configured to determine if the relay is or is not permitted via the 5G-RG MAC address.
  • the PDU Application layer may determine if the 3GPP device is allowed to perform such access, for example, according to a roaming agreement.
  • the AGF is also configured to provide an interface to the PDU Application layer to send the PDU payload.
  • the PDU control information may include: a MAC address, a relay node MAC address, a PDU session ID, QoS Flow information (e.g., QFI, RQI, RDI, bearer ID), PDU usage flags, and a relay flag.
  • the AGF is configured to: • set the SMAC and DMAC to the opposite value from those received previously in a PDU Ethernet packet;
  • the AGF is configured to provide:
  • End device (5G-RG acting as end device, or 3GPP device behind 5G-RG)
  • the end device is configured to support an adaption header design, and use one of the two methods for PDU transport: i.e., the Shim method and the Ethernet PDU method.
  • the end device is also configured to send PDU Ethernet packets responsive to a PDU Application layer request.
  • the end device is able to provide an interface to the PDU Application layer to send the PDU payload.
  • the end device is also configured to construct PDU Ethernet packets from PDU payloads, as well as PDU control information submitted from the PDU Application layer.
  • the PDU control information may include: a MAC address, a PDU session ID, QoS Flow information (QFI, bearer ID), and PDU usage.
  • the end device is also configured to:
  • the end device is configured to:
  • the end device is also configured to support reflective QoS control ,as stated previously. Particularly, the end device finds the QFI/RQI/RDI in the PDU adaption header, and the bearer ID from the received Ethernet frame. So obtained, the end device provides the QFI/RQI/RDI and the bearer ID, as well as the extracted/restored PDU payload, to the PDU Application layer for reflective QoS control.
  • Relay node (5G-RG acting as relay node)
  • the 5G-RG device is also configured to implement relay functionality on a relayed PDU Ethernet packet.
  • the relay node support for VLAN tag model was previously described.
  • 5G-RG devices support both the Shim method and the Ethernet PDU method.
  • the 5G-RG will establish an Ethernet type PDU for an Ethernet-based non-3GPP device before the Ethernet-based non-3GPP device can be connected to 5GC.
  • the 5G-RG will provide an Ethernet relay function for a 3GPP device behind the 5G-RG before the latter can establish its own PDU session to 5GC.
  • the shim header format is defined as follows:
  • the Flags bitmap is defined as follows:
  • the QFinfo bitmap for downlink PDU transport is defined as follows:
  • QFI QoS Flow Identity
  • RQI Reflective QoS Indication, 1 bit
  • RDI Reflective QoS flow to DRB mapping Indication, 1 bit: the RDI bit indicates whether QoS flow to DRB mapping rule should be updated.
  • the QFinfo bitmap for uplink PDU transport is defined as follows:
  • the C bit indicates it is used to indicate the end of QoS to bearer mapping for the QoS Flow (identified by the QFI) and the PDU payload part should be ignored.
  • the PDU header format is defined as follows.
  • PDUtype (2 octets): indicates that the inner payload in the PDU header is raw Ethernet.
  • the Flags bitmap is defined as follows.
  • Ethertype values will be used. Note that the values require the assignment from IANA.
  • PDUtype used in PDU header to indicate inner payload is raw Ethernet.
  • the embodiments of the present disclosure are configured to:
  • Figure 16 illustrates an exemplary method 300 performed by an end device 200 according to an embodiment.
  • method 300 is an Ethernet-based method, by an end device, for transporting Protocol Data Units (PDUs) over a Wireline Access Network (WAN).
  • PDUs Protocol Data Units
  • WAN Wireline Access Network
  • method 300 comprises receiving, at a PDU Transport layer executing on the end device, a PDU from a PDU Application layer executing on the end device, wherein the PDU is one of an Ethernet PDU and a non-Ethernet PDU (box 302).
  • the method further comprises generating a PDU adaptation header (box 302), and generating a PDU Ethernet packet comprising the PDU adaptation header based on whether the PDU is an Ethernet PDU or a non-Ethernet PDU (box 304).
  • the method then calls for sending the PDU Ethernet packet in an Ethernet frame to an Access Gateway Function (AGF) (box 308).
  • AMF Access Gateway Function
  • the PDU comprises a PDU payload and PDU control information associated with transporting the PDU Ethernet packet to the AGF.
  • the PDU payload comprises payload data for the PDU Ethernet packet, an Ethertype indicator, a Source Media Access Control (SMAC) address, and a Destination Media Access Control (DMAC) address.
  • SMAC Source Media Access Control
  • DMAC Destination Media Access Control
  • the PDU payload comprises one of an IP type PDU, an Unstructured type PDU, and NAS signaling to transport.
  • generating the PDU Ethernet packet comprises inserting the PDU adaptation header of a Shim header behind an Ethernet header of the PDU payload.
  • method 300 further comprises setting a PDU usage flag of the Shim header to indicate one of NAS signaling transport, IP type PDU, and Unstructured type PDU.
  • method 300 further comprises setting a PDU ID of the Shim header to a PDU session ID, setting a QFInfo field of the Shim header to QoS Flow information, and setting respective first and second flags in the Shim header to indicate that the PDU ID and the QFInfo fields are present.
  • method 300 further comprises not setting the PDU ID and the QFInfo fields, and instead, setting the respective first and second flags to indicate that the PDU ID and the QFInfo fields are not present in the Shim header.
  • method 300 further comprises setting an SMAC field of the Shim header to the SMAC address when the SMAC address is present in the PDU payload, and setting the DMAC field of the Shim header to the DMAC address when the DMAC address is present in the PDU payload.
  • the Ethertype field of the Shim header may be set to the Ethertype indicator to indicate one of NAS signaling transport, IP type PDU, and Unstructured type PDU.
  • the QFInfo field comprises a bitmap for uplink PDU transport. When it does, it comprises a first set of bits indicating an end of QoS to bearer mapping for a QoS Flow, and a second set of bits indicating that the PDU payload should be ignored.
  • generating the PDU Ethernet packet comprises inserting the Ethernet header in front of the PDU payload, and generating the PDU Ethernet packet for the Ethernet header. Additionally, a PDU usage flag of the Ethernet header is set to indicate one of NAS signaling transport, IP type PDU, and Unstructured type PDU.
  • an Ethertype field of the Ethernet header is set based on the PDU usage flag.
  • an SMAC field of the Ethernet header may be set to the MAC address of the end device, and a DMAC field of the Ethernet header may be set to one of a destination MAC address and a broadcast MAC address.
  • generating the PDU Ethernet packet comprises inserting the PDU adaptation header of an Ethernet PDU header in front of an Ethernet packet of the PDU payload.
  • the PDU adaptation header comprises an Ethernet header and a PDU header.
  • a PDU usage flag in the PDU header is set to indicate one of NAS signaling transport, IP type PDU, and Unstructured type PDU.
  • a PDU ID field is set to a PDU session ID
  • a QFInfo field is set to the QoS Flow information.
  • an SMAC field in the Ethernet header is set to a MAC address of a node operating the Ethernet header
  • a DMAC field in the Ethernet header is set to a MAC address of one of the AGF and a broadcast MAC address.
  • an Ethertype field is set to a value indicating one of Shim, NAS signaling over Ethernet (NASoE), Unstructured type PDU over Ethernet, and Ethernet PDU is present.
  • the PDU usage flag indicates handling of the PDU Ethernet packet to the PDU Transport layer.
  • the PDU Transport layer processes the PDU payload as an Ethernet payload regardless of whether the PDU payload is an IP type PDU, an Ethernet type PDU, or an Unstructured type PDU.
  • the PDU ID field identifies PDU data of a DPU session.
  • the end device comprises a Third Generation Partnership Project (3GPP) device identified by a MAC address known to the PDU Transport layer.
  • 3GPP Third Generation Partnership Project
  • the PDU Transport layer of the present embodiments is configured to generate the PDU adaptation header according to one of a Shim method and an Ethernet PDU method.
  • Sending the PDU Ethernet packet in the Ethernet frame to the AGF can be performed responsive to receiving a request to send the PDU Ethernet packet from the PDU Application layer.
  • the PDU control information comprises one or more of a MAC address, a PDU session ID, QoS Flow information, and PDU usage information.
  • a VLAN priority to a bearer ID can be set to support multiple QoS bearers.
  • FIG 17 illustrates an exemplary method 400 performed by a base station 100. More particularly, method 400 is an Ethernet-based method, implemented by an Access Gateway Function (AGF) executing at a base station, for transporting Protocol Data Units (PDUs) to an end device over a Wireline Access Network (WAN).
  • AMF Access Gateway Function
  • WAN Wireline Access Network
  • method 400 comprises receiving, at a PDU Transport layer of the AGF, a PDU from a PDU Application layer executing on the AGF, wherein the PDU is one of an Ethernet PDU and a non-Ethernet PDU (box 402).
  • PDU Transport layer receives the PDU
  • method 400 calls for generating a PDU adaptation header (box 404), generating a PDU Ethernet packet comprising the PDU adaptation header based on whether the PDU is an Ethernet PDU or a non-Ethernet PDU (box 406), and sending the PDU Ethernet packet in an Ethernet frame to the end device (box 408).
  • the PDU comprises a PDU payload and PDU control information associated with transporting the PDU Ethernet packet to the end device.
  • the PDU payload comprises payload data for the PDU Ethernet packet, an Ethertype indicator, a Source Media Access Control (SMAC) address, and a Destination Media Access Control (DMAC) address.
  • SMAC Source Media Access Control
  • DMAC Destination Media Access Control
  • the PDU payload comprises one of an IP type PDU, an Unstructured type PDU, and NAS signaling to transport.
  • generating the PDU Ethernet packet comprises inserting the PDU adaptation header of a Shim header behind an Ethernet header of the PDU payload.
  • method 400 further comprises setting a PDU usage flag of the Shim header to indicate one of NAS signaling transport, IP type PDU, and Unstructured type PDU.
  • a PDU ID of the Shim header is set to a PDU session ID
  • a QFInfo field of the Shim header is set to QoS Flow information
  • first and second flags in the Shim header are set to indicate, respectively, that the PDU ID and the QFInfo fields are present.
  • the PDU usage flag indicates NAS signaling transport
  • the PDU ID and the QFInfo fields are not set. Instead, the first and second flags are set to indicate that the PDU ID and the QFInfo fields, respectively, are not present in the Shim header.
  • an SMAC field of the Shim header can be set to the SMAC address.
  • the DMAC field of the Shim header can be set to the DMAC address.
  • an Ethertype field of the Shim header is set to the Ethertype indicator to indicate one of NAS signaling transport, IP type PDU, and
  • the QFInfo field comprises a bitmap for uplink PDU transport.
  • a first set of bits in the QFinfo field indicates an end of QoS to bearer mapping for a QoS Flow
  • a second set of bits in the QFinfo field indicates that the PDU payload should be ignored.
  • generating the PDU Ethernet packet comprises inserting the Ethernet header in front of the PDU payload, and generating the PDU Ethernet packet for the Ethernet header.
  • a PDU usage flag of the Ethernet header is set to indicate one of NAS signaling transport, IP type PDU, and Unstructured type PDU.
  • an Ethertype field of the Ethernet header is set based on the PDU usage flag.
  • an SMAC field of the Ethernet header is set to the MAC address of the end device, and a DMAC field of the Ethernet header is set to one of a destination MAC address and a broadcast MAC address.
  • generating the PDU Ethernet packet comprises inserting the PDU adaptation header of an Ethernet PDU header in front of an Ethernet packet of the PDU payload.
  • the PDU adaptation header comprises an Ethernet header and a PDU header.
  • a PDU usage flag in the PDU header is set to indicate one of NAS signaling transport, IP type PDU, and Unstructured type PDU.
  • the method further comprises setting, in the PDU header a PDU ID field to a PDU session ID and a QFInfo field to QoS Flow information.
  • a PDU ID field and a QFInfo field in the PDU header are not set. Instead, first and second flags in the PDU header are set to indicate, respectively, that the PDU ID field and the QFInfo field are not present in the PDU header.
  • an SMAC field the Ethernet header is set to a MAC address of a node operating the Ethernet header
  • a DMAC field the Ethernet header is set to a MAC address of one of the AGF and a broadcast MAC address.
  • an Ethertype field the Ethernet header is set to a value indicating one of Shim, NAS signaling over Ethernet (NASoE), Unstructured type PDU over Ethernet, and Ethernet PDU is present.
  • the PDU Ethernet packet is received from the end device.
  • method 400 further comprises relaying the PDU Ethernet packet based on a relay flag included in the PDU adaptation header.
  • method 400 further includes determining the MAC addresses of both the end device and a network node operating under 5G-RG.
  • method 400 further comprises identifying the end device based on the MAC address included in the PDU Ethernet packet.
  • the PDU usage flag indicates handling of the PDU Ethernet packet to the PDU Transport layer.
  • method 400 further comprises determining the MAC addresses of both the end device and a network node operating under 5G-RG.
  • method 400 further comprises extracting the PDU payload according to PDU Ethernet packet definition for NAS signaling transport, and determining the MAC address for the end device.
  • the PDU Transport layer processes the PDU payload as an Ethernet payload regardless of whether the PDU payload is an IP type PDU, and Ethernet type PDU, or an Unstructured type PDU.
  • a PDU session may be identified, according to the present embodiments, based on the PDU ID field in the PDU adaptation header.
  • a bearer may also be identified via VLAN priority for PDU data transport and for PDU NAS signaling transport.
  • the QFInfo field comprises a bitmap for downlink PDU transport, and indicates one of a QoS Flow Identity (QFI) indicating a maximum number of flows, a Reflective QoS Indication (RQI) indicating whether NAS should be informed that SDF to QoS flow mapping rules have been updated, and a Reflective QoS flow to DRB mapping Indication (RDI) indicating whether QoS flow to DRB mapping rules should be updated.
  • QFI QoS Flow Identity
  • RQI Reflective QoS Indication
  • RDI Reflective QoS flow to DRB mapping Indication
  • a flag in the PDU adaptation header of the PDU Ethernet packet received from the end device is identified, and an end of QoS to bearer mapping for a QoS Flow based on the flag is indicated to the PDU Application layer at the AGF.
  • the PDU Ethernet packet received from the end device is sent to the PDU Application layer at the AGF responsive to receiving a request for the PDU Ethernet packet from the PDU Application layer.
  • the processing of a received PDU Ethernet packet may be performed according to one of a Shim method and an Ethernet PDU method based on the processing method used to process a previously received PDU Ethernet packet.
  • the network node functions as a relay node.
  • the PDU control information comprises one or more of a MAC address, a PDU session ID, QoS Flow information, and PDU usage information.
  • An apparatus can perform any of the methods herein described by implementing any functional means, modules, units, or circuitry.
  • the apparatuses comprise respective circuits or circuitry configured to perform the steps shown in the method figures.
  • the circuits or circuitry in this regard may comprise circuits dedicated to performing certain functional processing and/or one or more
  • the circuitry may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processors (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory may include program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.
  • the memory stores program code that, when executed by the one or more processors, carries out the techniques described herein.
  • FIG. 18 illustrates network node 500 formed as a gateway device (e.g., a computer server) in accordance with one or more embodiments.
  • a gateway device e.g., a computer server
  • the present embodiments are not limited to the network node being a gateway device. Rather, in accordance with the present disclosure, the network node can comprise any computing device suitable for transporting PDUs over a WAN.
  • Network node 500 comprises an interface circuit 502, a processing circuit 504, and memory 506 configured to store a computer program 508.
  • the interface circuit 502 is configured to transmit and receive data packets over an Ethernet-based network and may comprise, for example, one or more interface cards configured to perform that function.
  • the processing circuit 504 controls the overall operation of the network node 500 and processes the data packets transmitted to or received by the network node 500. Such processing includes the PDUs received from, and sent to, a PDU application layer, as previously described.
  • the processing circuit 504 may comprise one or more microprocessors, hardware, firmware, or a combination thereof.
  • Memory 506 comprises both volatile and non-volatile memory for storing computer program code and data needed by the processing circuit 504 for operation.
  • Memory 506 may comprise any tangible, non-transitory computer-readable storage medium for storing data including electronic, magnetic, optical, electromagnetic, or semiconductor data storage.
  • Memory 506 stores a computer program 508 comprising executable instructions that configure the processing circuit 504 to implement method 500 according to Figure 17 as described herein.
  • the computer program 508 in this regard may comprise one or more code modules corresponding to the means or units described above.
  • computer program instructions and configuration information are stored in a non-volatile memory, such as a ROM, erasable programmable read only memory (EPROM) or flash memory.
  • Temporary data generated during operation may be stored in a volatile memory, such as a random access memory (RAM).
  • computer program 508 for configuring the processing circuit 504 as herein described may be stored in a removable memory, such as a portable compact disc, portable digital video disc, or other removable media.
  • the computer program 508 may also be embodied in a carrier such as an electronic signal, optical signal, radio signal, or computer readable storage medium.
  • FIG. 19 illustrates some functional modules executing on network node 500 in accordance with one or more embodiments.
  • the network node 500 in this embodiment executes a plurality of modules including a receiving module 510, a PDU processing module 512, and a sending module 514.
  • the various modules 510, 512 and 514 can be implemented by hardware and/or by software code that is executed by a processor or processing circuit.
  • the receiving module 510 is configured to receive, at a PDU Transport layer executing on the network node 500, a PDU from a PDU Application layer executing on the network node 500, wherein the PDU is one of an Ethernet PDU and a non-Ethernet PDU.
  • the PDU processing module 512 is configured to process the PDU received from and sent to a PDU Application layer executing on the network node 500. More particularly, the PDU processing module 512 configures the network node 500 with a PDU Transport layer configured to process PDUs, as previously described.
  • the sending module 514 is configured to send a PDU Ethernet packet in an Ethernet frame to an end device.
  • Figure 20 illustrates an end device 600 formed as a user equipment (UE) in accordance with one or more embodiments.
  • UE user equipment
  • the present embodiments are not limited to the end device 600 being a UE. Rather, in accordance with the present disclosure, the end device can comprise any computing device suitable for transporting PDUs over a WAN, such as a network node executing an AGF, for example.
  • End device 600 comprises one or more antennas 602, an interface circuit 604, a processing circuit 606, and a memory 508 configured to store a computer program 510.
  • the interface circuit 604 is configured to transmit and receive data packets over an Ethernet-based network and may comprise, for example, one or more interface cards configured to perform that function. Additionally, the interface circuit 604 is configured to communicate data and signals to a network via the one or more antennas 602.
  • the processing circuit 606 controls the overall operation of the end device 600 and processes the data packets transmitted to or received by the end device 600. Such processing includes the PDUs received from, and sent to, a PDU application layer, as previously described.
  • the processing circuit 606 may comprise one or more
  • microprocessors hardware, firmware, or a combination thereof.
  • Memory 608 comprises both volatile and non-volatile memory for storing computer program code and data needed by the processing circuit 606 for operation.
  • Memory 608 may comprise any tangible, non-transitory computer-readable storage medium for storing data including electronic, magnetic, optical, electromagnetic, or semiconductor data storage.
  • Memory 608 stores a computer program 610 comprising executable instructions that configure the processing circuit 606 to implement method 300 according to Figure 16 as described herein.
  • the computer program 610 in this regard may comprise one or more code modules corresponding to the means or units described above.
  • computer program instructions and configuration information are stored in a non-volatile memory, such as a ROM, erasable programmable read only memory (EPROM) or flash memory.
  • Temporary data generated during operation may be stored in a volatile memory, such as a random access memory (RAM).
  • computer program 610 for configuring the processing circuit 606 as herein described may be stored in a removable memory, such as a portable compact disc, portable digital video disc, or other removable media.
  • the computer program 610 may also be embodied in a carrier such as an electronic signal, optical signal, radio signal, or computer readable storage medium.
  • Figure 21 illustrates some functional modules executing on end device 600 in accordance with one or more embodiments.
  • the end device 600 in this embodiment executes a plurality of modules including a receiving module 612, a PDU processing module 614, and a sending module 616.
  • the various modules 612, 614 and 616 can be implemented by hardware and/or by software code that is executed by a processor or processing circuit.
  • the receiving module 612 is configured to receive, at a PDU Transport layer executing on the end device 600, a PDU from a PDU Application layer executing on the end device 600, wherein the PDU is one of an Ethernet PDU and a non-Ethernet PDU.
  • the PDU processing module 614 is configured to process the PDU received from and sent to a PDU Application layer executing on the end device 600. More particularly, the PDU processing module 614 configures the end device 600 with a PDU Transport layer configured to process PDUs, as previously described.
  • the sending module 616 is configured to send a PDU Ethernet packet in an Ethernet frame to an AGF executing on a gateway device, such as network node 500, for example.
  • the processing circuit 504 of a network node 500 could have units, modules, or circuits configured to carry out methods described herein.
  • the processing circuit 504 in this embodiment comprises receiving unit 520, a PDU processing unit 522, and a sending unit 524.
  • the various unit 520, 522 and 524 can be implemented by hardware and/or by software code that is executed by a processor or processing circuit.
  • the receiving unit 520 is configured to receive a PDU from a PDU Application layer executing on the network node 500, wherein the PDU is one of an Ethernet PDU and a non-Ethernet PDU.
  • the PDU processing unit 522 is configured to process the PDU received from and sent to a PDU Application layer executing on the network node 500. More particularly, the PDU processing unit 522 configures the network node 500 with a PDU Transport layer configured to process PDUs, as previously described. This includes, but is not limited to, generating a PDU adaptation header, and generating a PDU Ethernet packet comprising the PDU adaptation header based on whether the received PDU is an Ethernet PDU or a non-Ethernet PDU.
  • the sending unit 524 is configured to send a PDU Ethernet packet in an Ethernet frame to an end device.
  • the processing circuit 606 of an end device 600 could have units, modules, or circuits configured to carry out methods described herein.
  • the processing circuit 606 in this embodiment comprises receiving unit 620, a PDU processing unit 622, and a sending unit 624.
  • 622 and 624 can be implemented by hardware and/or by software code that is executed by a processor or processing circuit.
  • the receiving unit 620 is configured to receive a PDU from a PDU Application layer executing on the end device 600, wherein the PDU is one of an Ethernet PDU and a non-Ethernet PDU.
  • the PDU processing unit 622 is configured to process the PDU received from and sent to a PDU Application layer executing on the end device 600.
  • the PDU processing unit 622 configures the end device 600 with a PDU Transport layer configured to process PDUs, as previously described. This includes, but is not limited to, generating a PDU adaptation header, and generating a PDU Ethernet packet comprising the PDU adaptation header based on whether the received PDU is an Ethernet PDU or a non-Ethernet PDU.
  • the sending unit 624 is configured to send a PDU Ethernet packet in an Ethernet frame to a network node 500.
  • a computer program comprises instructions which, when executed on at least one processor of an apparatus, cause the apparatus to carry out any of the respective processing described above.
  • a computer program in this regard may comprise one or more code modules corresponding to the means or units described above.
  • Embodiments further include a carrier containing such a computer program.
  • This carrier may comprise one of an electronic signal, optical signal, radio signal, or computer readable storage medium.
  • embodiments herein also include a computer program product stored on a non-transitory computer readable (storage or recording) medium and comprising instructions that, when executed by a processor of an apparatus, cause the apparatus to perform as described above.
  • Embodiments further include a computer program product comprising program code portions for performing the steps of any of the embodiments herein when the computer program product is executed by a computing device.
  • This computer program product may be stored on a computer readable recording medium.
  • a wireless network such as the example wireless network illustrated in Figure QQ1 .
  • the wireless network of Figure QQ1 only depicts network QQ106, network nodes QQ160 and QQ160b, and WDs QQ1 10, QQ1 10b, and QQ1 10c.
  • a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device.
  • network node QQ160 and wireless device (WD) QQ1 10 are depicted with additional detail.
  • the wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network.
  • the wireless network may comprise and/or interface with any type of
  • Network QQ106 may comprise one or more backhaul networks, core networks, and/or wireless networks or other similar type of system.
  • the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures.
  • particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), Narrowband Internet of Things (NB-loT), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.1 1 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.
  • Network QQ106 may comprise one or more backhaul networks, core networks,
  • IP networks public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.
  • PSTNs public switched telephone networks
  • WANs wide-area networks
  • LANs local area networks
  • WLANs wireless local area networks
  • wired networks wireless networks, metropolitan area networks, and other networks to enable communication between devices.
  • Network node QQ160 and WD QQ1 10 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network.
  • the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network.
  • network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).
  • APs access points
  • BSs base stations
  • eNBs evolved Node Bs
  • gNBs NR NodeBs
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • RRUs remote radio units
  • RRHs Remote Radio Heads
  • Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
  • DAS distributed antenna system
  • network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • transmission points transmission nodes
  • MCEs multi-cell/multicast coordination entities
  • core network nodes e.g., MSCs, MMEs
  • O&M nodes e.g., OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.
  • network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.
  • network node QQ160 includes processing circuitry QQ170, device readable medium QQ180, interface QQ190, auxiliary equipment QQ184, power source QQ186, power circuitry QQ 187, and antenna QQ162.
  • network node QQ160 illustrated in the example wireless network of Figure QQ1 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components.
  • a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein.
  • components of network node QQ160 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium QQ180 may comprise multiple separate hard drives as well as multiple RAM modules).
  • network node QQ160 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • network node QQ160 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeB’s.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • network node QQ160 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • some components may be duplicated (e.g., separate device readable medium QQ180 for the different RATs) and some components may be reused (e.g., the same antenna QQ162 may be shared by the RATs).
  • Network node QQ160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node QQ160.
  • Processing circuitry QQ170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node.
  • processing circuitry QQ170 may include processing information obtained by processing circuitry QQ170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • Processing circuitry QQ170 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node QQ160 components, such as device readable medium QQ180, network node QQ160 functionality.
  • processing circuitry QQ170 may execute instructions stored in device readable medium QQ180 or in memory within processing circuitry QQ170.
  • processing circuitry QQ170 may include a system on a chip (SOC).
  • processing circuitry QQ170 may include one or more of radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174.
  • radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units.
  • part or all of RF transceiver circuitry QQ172 and baseband processing circuitry QQ174 may be on the same chip or set of chips, boards, or units
  • processing circuitry QQ170 executing instructions stored on device readable medium QQ180 or memory within processing circuitry QQ170.
  • some or all of the functionality may be provided by processing circuitry QQ170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner.
  • processing circuitry QQ170 can be configured to perform the described functionality.
  • the benefits provided by such functionality are not limited to processing circuitry QQ170 alone or to other components of network node QQ160, but are enjoyed by network node QQ160 as a whole, and/or by end users and the wireless network generally.
  • Device readable medium QQ180 may comprise any form of volatile or non volatile computer readable memory including, without limitation, persistent storage, solid- state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry QQ170.
  • volatile or non volatile computer readable memory including, without limitation, persistent storage, solid- state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-vol
  • Device readable medium QQ180 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry QQ170 and, utilized by network node QQ160.
  • Device readable medium QQ180 may be used to store any calculations made by processing circuitry QQ170 and/or any data received via interface QQ190.
  • processing circuitry QQ170 and device readable medium QQ180 may be considered to be integrated.
  • Interface QQ190 is used in the wired or wireless communication of signalling and/or data between network node QQ160, network QQ106, and/or WDs QQ1 10. As illustrated, interface QQ190 comprises port(s)/terminal(s) QQ194 to send and receive data, for example to and from network QQ106 over a wired connection. Interface QQ190 also includes radio front end circuitry QQ192 that may be coupled to, or in certain embodiments a part of, antenna QQ162. Radio front end circuitry QQ192 comprises filters QQ198 and amplifiers QQ196. Radio front end circuitry QQ192 may be connected to antenna QQ162 and processing circuitry QQ170.
  • Radio front end circuitry may be configured to condition signals communicated between antenna QQ162 and processing circuitry QQ170.
  • Radio front end circuitry QQ192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection.
  • Radio front end circuitry QQ192 may convert the digital data into a radio signal having the appropriate channel and bandwidth fields using a combination of filters QQ198 and/or amplifiers QQ196. The radio signal may then be transmitted via antenna QQ162.
  • antenna QQ162 may collect radio signals which are then converted into digital data by radio front end circuitry QQ192.
  • the digital data may be passed to processing circuitry QQ170.
  • the interface may comprise different components and/or different combinations of components.
  • network node QQ160 may not include separate radio front end circuitry QQ192, instead, processing circuitry QQ170 may comprise radio front end circuitry and may be connected to antenna QQ162 without separate radio front end circuitry QQ192.
  • processing circuitry QQ170 may comprise radio front end circuitry and may be connected to antenna QQ162 without separate radio front end circuitry QQ192.
  • all or some of RF transceiver circuitry QQ172 may be considered a part of interface QQ190.
  • interface QQ190 may include one or more ports or terminals QQ194, radio front end circuitry QQ192, and RF transceiver circuitry QQ172, as part of a radio unit (not shown), and interface QQ190 may communicate with baseband processing circuitry QQ174, which is part of a digital unit (not shown).
  • Antenna QQ162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna QQ162 may be coupled to radio front end circuitry QQ190 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna QQ162 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to
  • antenna QQ162 may be separate from network node QQ160 and may be connectable to network node QQ160 through an interface or port.
  • Antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.
  • Power circuitry QQ187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node QQ160 with power for performing the functionality described herein. Power circuitry QQ187 may receive power from power source QQ186. Power source QQ186 and/or power circuitry QQ187 may be configured to provide power to the various components of network node QQ160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source QQ186 may either be included in, or external to, power circuitry QQ187 and/or network node QQ160.
  • network node QQ160 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry QQ187.
  • power source QQ186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry QQ187. The battery may provide backup power should the external power source fail.
  • Other types of power sources such as photovoltaic devices, may also be used.
  • network node QQ160 may include additional components beyond those shown in Figure QQ1 that may be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein.
  • network node QQ160 may include user interface equipment to allow input of information into network node QQ160 and to allow output of information from network node QQ160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node QQ160.
  • wireless device refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices.
  • the term WD may be used interchangeably herein with user equipment (UE).
  • Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air.
  • a WD may be configured to transmit and/or receive information without direct human interaction.
  • a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network.
  • Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE) a vehicle-mounted wireless terminal device, etc.
  • VoIP voice over IP
  • PDA personal digital assistant
  • PDA personal digital assistant
  • a wireless cameras a gaming console or device
  • a music storage device a playback appliance
  • a wearable terminal device a wireless endpoint
  • a mobile station a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (L
  • a WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to- everything (V2X) and may in this case be referred to as a D2D communication device.
  • D2D device-to-device
  • a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node.
  • the WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device.
  • M2M machine-to-machine
  • the WD may be a UE implementing the 3GPP narrow band internet of things (NB-loT) standard.
  • NB-loT narrow band internet of things
  • machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g.
  • a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • a WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal.
  • a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.
  • wireless device QQ1 10 includes antenna QQ1 1 1 , interface QQ1 14, processing circuitry QQ120, device readable medium QQ130, user interface equipment QQ132, auxiliary equipment QQ134, power source QQ136 and power circuitry QQ137.
  • WD QQ1 10 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD QQ1 10, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, NB-loT, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD QQ1 10.
  • Antenna QQ1 1 1 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface QQ1 14.
  • antenna QQ1 1 1 may be separate from WD QQ1 10 and be connectable to WD QQ1 10 through an interface or port.
  • Antenna QQ1 1 1 , interface QQ1 14, and/or processing circuitry QQ120 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD.
  • radio front end circuitry and/or antenna QQ1 1 1 may be considered an interface.
  • interface QQ1 14 comprises radio front end circuitry QQ1 12 and antenna QQ1 1 1 .
  • Radio front end circuitry QQ1 12 comprise one or more filters QQ1 18 and amplifiers QQ1 16.
  • Radio front end circuitry QQ1 14 is connected to antenna QQ1 1 1 and processing circuitry QQ120, and is configured to condition signals communicated between antenna QQ1 1 1 and processing circuitry QQ120.
  • Radio front end circuitry QQ1 12 may be coupled to or a part of antenna QQ1 1 1.
  • WD QQ1 10 may not include separate radio front end circuitry QQ1 12; rather, processing circuitry QQ120 may comprise radio front end circuitry and may be connected to antenna QQ1 1 1 .
  • Radio front end circuitry QQ1 12 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry QQ1 12 may convert the digital data into a radio signal having the appropriate channel and bandwidth fields using a combination of filters QQ1 18 and/or amplifiers QQ1 16. The radio signal may then be transmitted via antenna QQ1 1 1 . Similarly, when receiving data, antenna QQ1 1 1 may collect radio signals which are then converted into digital data by radio front end circuitry QQ1 12.
  • the digital data may be passed to processing circuitry QQ120.
  • the interface may comprise different components and/or different combinations of components.
  • Processing circuitry QQ120 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD QQ1 10 components, such as device readable medium QQ130, WD QQ1 10 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein.
  • processing circuitry QQ120 may execute instructions stored in device readable medium QQ130 or in memory within processing circuitry QQ120 to provide the functionality disclosed herein.
  • processing circuitry QQ120 includes one or more of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126.
  • the processing circuitry may comprise different components and/or different combinations of components.
  • processing circuitry QQ120 of WD QQ1 10 may comprise a SOC.
  • RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be on separate chips or sets of chips.
  • part or all of baseband processing circuitry QQ124 and application processing circuitry QQ126 may be combined into one chip or set of chips, and RF transceiver circuitry QQ122 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry QQ122 and baseband processing circuitry QQ124 may be on the same chip or set of chips, and application processing circuitry QQ126 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be combined in the same chip or set of chips.
  • RF transceiver circuitry QQ122 may be a part of interface QQ1 14.
  • RF transceiver circuitry QQ122 may condition RF signals for processing circuitry QQ120.
  • processing circuitry QQ120 executing instructions stored on device readable medium QQ130, which in certain embodiments may be a computer-readable storage medium.
  • some or all of the functionality may be provided by processing circuitry QQ120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner.
  • processing circuitry QQ120 can be configured to perform the described functionality.
  • Processing circuitry QQ120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry QQ120, may include processing information obtained by processing circuitry QQ120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD QQ1 10, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • Device readable medium QQ130 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry QQ120.
  • Device readable medium QQ130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry QQ120.
  • processing circuitry QQ120 and device readable medium QQ130 may be considered to be integrated.
  • User interface equipment QQ132 may provide components that allow for a human user to interact with WD QQ1 10. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment QQ132 may be operable to produce output to the user and to allow the user to provide input to WD QQ1 10. The type of interaction may vary depending on the type of user interface equipment QQ132 installed in WD QQ1 10.
  • WD QQ1 10 is a smart phone
  • the interaction may be via a touch screen
  • WD QQ1 10 is a smart meter
  • the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected).
  • User interface equipment QQ132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment QQ132 is configured to allow input of information into WD QQ1 10, and is connected to processing circuitry QQ120 to allow processing circuitry QQ120 to process the input information.
  • User interface equipment QQ132 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment QQ132 is also configured to allow output of information from WD QQ1 10, and to allow processing circuitry QQ120 to output information from WD QQ1 10. User interface equipment QQ132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment QQ132, WD QQ1 10 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.
  • Auxiliary equipment QQ134 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment QQ134 may vary depending on the embodiment and/or scenario.
  • Power source QQ136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used.
  • WD QQ1 10 may further comprise power circuitry QQ137 for delivering power from power source QQ136 to the various parts of WD QQ1 10 which need power from power source QQ136 to carry out any functionality described or indicated herein.
  • Power circuitry QQ137 may in certain embodiments comprise power management circuitry.
  • Power circuitry QQ137 may additionally or alternatively be operable to receive power from an external power source; in which case WD QQ1 10 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry QQ137 may also in certain embodiments be operable to deliver power from an external power source to power source QQ136. This may be, for example, for the charging of power source QQ136. Power circuitry QQ137 may perform any formatting, converting, or other modification to the power from power source QQ136 to make the power suitable for the respective components of WD QQ1 10 to which power is supplied.
  • Figure QQ2 illustrates one embodiment of a UE in accordance with various aspects described herein.
  • a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).
  • a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
  • UE QQ2200 may be any UE identified by the 3rd Generation Partnership Project (3GPP), including a NB-loT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • UE QQ200 is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards.
  • 3GPP 3rd Generation Partnership Project
  • the term WD and UE may be used interchangeable. Accordingly, although Figure QQ2 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.
  • UE QQ200 includes processing circuitry QQ201 that is operatively coupled to input/output interface QQ205, radio frequency (RF) interface QQ209, network connection interface QQ21 1 , memory QQ215 including random access memory (RAM) QQ217, read-only memory (ROM) QQ219, and storage medium QQ221 or the like, communication subsystem QQ231 , power source QQ233, and/or any other component, or any combination thereof.
  • Storage medium QQ221 includes operating system QQ223, application program QQ225, and data QQ227. In other embodiments, storage medium QQ221 may include other similar types of information.
  • Certain UEs may utilize all of the components shown in Figure QQ2, or only a subset of the components.
  • the level of integration between the components may vary from one UE to another UE.
  • certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • processing circuitry QQ201 may be configured to process computer instructions and data.
  • Processing circuitry QQ201 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.);
  • the processing circuitry QQ201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.
  • input/output interface QQ205 may be configured to provide a communication interface to an input device, output device, or input and output device.
  • UE QQ200 may be configured to use an output device via input/output interface QQ205.
  • An output device may use the same type of interface port as an input device.
  • a USB port may be used to provide input to and output from UE QQ200.
  • the output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • UE QQ200 may be configured to use an input device via input/output interface QQ205 to allow a user to capture information into UE QQ200.
  • the input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like.
  • the presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof.
  • the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.
  • RF interface QQ209 may be configured to provide a
  • Network connection interface QQ21 1 may be configured to provide a communication interface to network QQ243a.
  • Network QQ243a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • network QQ243a may comprise a Wi-Fi network.
  • Network connection interface QQ21 1 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like.
  • Network connection interface QQ21 1 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.
  • RAM QQ217 may be configured to interface via bus QQ202 to processing circuitry QQ201 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers.
  • ROM QQ219 may be configured to provide computer instructions or data to processing circuitry QQ201 .
  • ROM QQ219 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory.
  • Storage medium QQ221 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives.
  • storage medium QQ221 may be configured to include operating system QQ223, application program QQ225 such as a web browser application, a widget or gadget engine or another application, and data file QQ227.
  • Storage medium QQ221 may store, for use by UE QQ200, any of a variety of various operating systems or combinations of operating systems.
  • Storage medium QQ221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof.
  • RAID redundant array of independent disks
  • HD-DVD high-density digital versatile disc
  • HDDS holographic digital data storage
  • DIMM external mini-dual in-line memory module
  • SDRAM synchronous dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • smartcard memory such as a subscriber identity module or a
  • Storage medium QQ221 may allow UE QQ200 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium QQ221 , which may comprise a device readable medium.
  • processing circuitry QQ201 may be configured to communicate with network QQ243b using communication subsystem QQ231 .
  • Network QQ243a and network QQ243b may be the same network or networks or different network or networks.
  • Communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with network QQ243b.
  • communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.QQ2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like.
  • RAN radio access network
  • Each transceiver may include transmitter QQ233 and/or receiver QQ235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter QQ233 and receiver QQ235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.
  • the communication functions of communication subsystem QQ231 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field
  • communication subsystem QQ231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication.
  • Network QQ243b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • network QQ243b may be a cellular network, a Wi-Fi network, and/or a near-field network.
  • Power source QQ213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE QQ200.
  • the features, benefits and/or functions described herein may be implemented in one of the components of UE QQ200 or partitioned across multiple components of UE QQ200. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware.
  • communication subsystem QQ231 may be configured to include any of the components described herein.
  • processing circuitry QQ201 may be configured to
  • FIG. 1 is a schematic block diagram illustrating a virtualization environment QQ300 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is
  • some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments QQ300 hosted by one or more of hardware nodes QQ330. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.
  • the functions may be implemented by one or more applications QQ320 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • applications QQ320 which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.
  • Applications QQ320 are run in virtualization environment QQ300 which provides hardware QQ330 comprising processing circuitry QQ360 and memory QQ390.
  • Memory QQ390 contains instructions QQ395 executable by processing circuitry QQ360 whereby application QQ320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.
  • Virtualization environment QQ300 comprises general-purpose or special- purpose network hardware devices QQ330 comprising a set of one or more processors or processing circuitry QQ360, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors.
  • processors or processing circuitry QQ360 which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors.
  • Each hardware device may comprise memory QQ390-1 which may be non-persistent memory for temporarily storing instructions QQ395 or software executed by processing circuitry QQ360.
  • Each hardware device may comprise one or more network interface controllers (NICs) QQ370, also known as network interface cards, which include physical network interface QQ380.
  • NICs network interface controllers
  • Each hardware device may also include non-transitory, persistent, machine-readable storage media QQ390-2 having stored therein software QQ395 and/or instructions executable by processing circuitry QQ360.
  • Software QQ395 may include any type of software including software for instantiating one or more virtualization layers QQ350 (also referred to as
  • hypervisors software to execute virtual machines QQ340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.
  • Virtual machines QQ340 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ350 or hypervisor. Different embodiments of the instance of virtual appliance QQ320 may be implemented on one or more of virtual machines QQ340, and the implementations may be made in different ways.
  • processing circuitry QQ360 executes software QQ395 to instantiate the hypervisor or virtualization layer QQ350, which may sometimes be referred to as a virtual machine monitor (VMM).
  • Virtualization layer QQ350 may present a virtual operating platform that appears like networking hardware to virtual machine QQ340.
  • hardware QQ330 may be a standalone network node with generic or specific components. Hardware QQ330 may comprise antenna QQ3225 and may implement some functions via virtualization. Alternatively, hardware QQ330 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) QQ3100, which, among others, oversees lifecycle management of applications QQ320.
  • CPE customer premise equipment
  • NFV network function virtualization
  • NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
  • virtual machine QQ340 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non- virtualized machine.
  • Each of virtual machines QQ340, and that part of hardware QQ330 that executes that virtual machine be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines QQ340, forms a separate virtual network elements (VNE).
  • VNE virtual network elements
  • VNF Virtual Network Function
  • one or more radio units QQ3200 that each include one or more transmitters QQ3220 and one or more receivers QQ3210 may be coupled to one or more antennas QQ3225.
  • Radio units QQ3200 may communicate directly with hardware nodes QQ330 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
  • control system QQ3230 which may alternatively be used for communication between the hardware nodes QQ330 and radio units QQ3200.
  • Figure QQ4 illustrates a telecommunication network connected via an
  • a communication system includes telecommunication network QQ410, such as a 3GPP- type cellular network, which comprises access network QQ41 1 , such as a radio access network, and core network QQ414.
  • Access network QQ41 1 comprises a plurality of base stations QQ412a, QQ412b, QQ412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area QQ413a, QQ413b, QQ413c.
  • Each base station QQ412a, QQ412b, QQ412c is connectable to core network QQ414 over a wired or wireless connection QQ415.
  • a first UE QQ491 located in coverage area QQ413c is configured to wirelessly connect to, or be paged by, the corresponding base station QQ412c.
  • a second UE QQ492 in coverage area QQ413a is wirelessly connectable to the corresponding base station QQ412a. While a plurality of UEs QQ491 , QQ492 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station QQ412.
  • Telecommunication network QQ410 is itself connected to host computer QQ430, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm.
  • Host computer QQ430 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider.
  • Connections QQ421 and QQ422 between telecommunication network QQ410 and host computer QQ430 may extend directly from core network QQ414 to host computer QQ430 or may go via an optional intermediate network QQ420.
  • Intermediate network QQ420 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network QQ420, if any, may be a backbone network or the Internet; in particular, intermediate network QQ420 may comprise two or more sub networks (not shown).
  • the communication system of Figure QQ4 as a whole enables connectivity between the connected UEs QQ491 , QQ492 and host computer QQ430.
  • the connectivity may be described as an over-the-top (OTT) connection QQ450.
  • Host computer QQ430 and the connected UEs QQ491 , QQ492 are configured to
  • OTT connection QQ450 may be transparent in the sense that the participating communication devices through which OTT connection QQ450 passes are unaware of routing of uplink and downlink communications.
  • base station QQ412 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer QQ430 to be forwarded (e.g., handed over) to a connected UE QQ491.
  • base station QQ412 need not be aware of the future routing of an outgoing uplink communication originating from the UE QQ491 towards the host computer QQ430.
  • FIG. QQ5 illustrates host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments
  • host computer QQ510 comprises hardware QQ515 including communication interface QQ516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system QQ500.
  • Host computer QQ510 further comprises processing circuitry QQ518, which may have storage and/or processing capabilities.
  • processing circuitry QQ518 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Host computer QQ510 further comprises software QQ51 1 , which is stored in or accessible by host computer QQ510 and executable by processing circuitry QQ518.
  • Software QQ51 1 includes host application QQ512.
  • Host application QQ512 may be operable to provide a service to a remote user, such as UE QQ530 connecting via OTT connection QQ550 terminating at UE QQ530 and host computer QQ510. In providing the service to the remote user, host application QQ512 may provide user data which is transmitted using OTT connection QQ550.
  • Communication system QQ500 further includes base station QQ520 provided in a telecommunication system and comprising hardware QQ525 enabling it to
  • Hardware QQ525 may include communication interface QQ526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of
  • Communication interface QQ526 may be configured to facilitate connection QQ560 to host computer QQ510.
  • Connection QQ560 may be direct or it may pass through a core network (not shown in Figure QQ5) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system.
  • hardware QQ525 of base station QQ520 further includes processing circuitry QQ528, which may comprise one or more programmable processors, application- specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Base station QQ520 further has software QQ521 stored internally or accessible via an external connection.
  • Communication system QQ500 further includes UE QQ530 already referred to.
  • Its hardware QQ535 may include radio interface QQ537 configured to set up and maintain wireless connection QQ570 with a base station serving a coverage area in which UE QQ530 is currently located.
  • Hardware QQ535 of UE QQ530 further includes processing circuitry QQ538, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • UE QQ530 further comprises software QQ531 , which is stored in or accessible by UE QQ530 and executable by processing circuitry QQ538.
  • Software QQ531 includes client application QQ532.
  • Client application QQ532 may be operable to provide a service to a human or non-human user via UE QQ530, with the support of host computer QQ510.
  • an executing host application QQ512 may communicate with the executing client application QQ532 via OTT connection QQ550 terminating at UE QQ530 and host computer QQ510.
  • client application QQ532 may receive request data from host application QQ512 and provide user data in response to the request data.
  • OTT connection QQ550 may transfer both the request data and the user data.
  • Client application QQ532 may interact with the user to generate the user data that it provides.
  • host computer QQ510, base station QQ520 and UE QQ530 illustrated in Figure QQ5 may be similar or identical to host computer QQ430, one of base stations QQ412a, QQ412b, QQ412c and one of UEs QQ491 , QQ492 of Figure QQ4, respectively.
  • the inner workings of these entities may be as shown in Figure QQ5 and independently, the surrounding network topology may be that of Figure QQ4.
  • OTT connection QQ550 has been drawn abstractly to illustrate the communication between host computer QQ510 and UE QQ530 via base station QQ520, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from UE QQ530 or from the service provider operating host computer QQ510, or both. While OTT connection QQ550 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • Wireless connection QQ570 between UE QQ530 and base station QQ520 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to UE QQ530 using OTT connection QQ550, in which wireless connection QQ570 forms the last segment.
  • the teachings of these embodiments may improve the transport of Protocol Data Units (PDUs) over a Wireline Access Network (WAN) and thereby provide benefits that include, but are not limited to:
  • PDUs Protocol Data Units
  • WAN Wireline Access Network
  • IP PDU type IP PDU type
  • Ethernet PDU type Unstructured PDU type
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring OTT connection QQ550 may be implemented in software QQ51 1 and hardware QQ515 of host computer QQ510 or in software QQ531 and hardware QQ535 of UE QQ530, or both.
  • sensors may be deployed in or in association with communication devices through which OTT connection QQ550 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software QQ51 1 , QQ531 may compute or estimate the monitored quantities.
  • the reconfiguring of OTT connection QQ550 may include message format,
  • measurements may involve proprietary UE signaling facilitating host computer QQ510’s measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that software QQ51 1 and QQ531 causes messages to be transmitted, in particular empty or‘dummy’ messages, using OTT connection QQ550 while it monitors propagation times, errors etc.
  • Figure QQ6 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures QQ4 and QQ5. For simplicity of the present disclosure, only drawing references to Figure QQ6 will be included in this section.
  • step QQ610 the host computer provides user data.
  • substep QQ61 1 (which may be optional) of step QQ610, the host computer provides the user data by executing a host application.
  • step QQ620 the host computer initiates a transmission carrying the user data to the UE.
  • step QQ630 the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step QQ640 the UE executes a client application associated with the host application executed by the host computer.
  • FIG. QQ7 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures QQ4 and QQ5. For simplicity of the present disclosure, only drawing references to Figure QQ7 will be included in this section.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • step QQ720 the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step QQ730 (which may be optional), the UE receives the user data carried in the transmission.
  • Figure QQ8 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures QQ4 and QQ5. For simplicity of the present disclosure, only drawing references to Figure QQ8 will be included in this section.
  • step QQ810 (which may be optional) the UE receives input data provided by the host computer. Additionally or alternatively, in step QQ820, the UE provides user data.
  • substep QQ821 (which may be optional) of step QQ820, the UE provides the user data by executing a client application.
  • substep QQ81 1 (which may be optional) of step QQ810, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep QQ830 (which may be optional), transmission of the user data to the host computer. In step QQ840 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.
  • Figure QQ9 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures QQ4 and QQ5.
  • the base station receives user data from the UE.
  • the base station initiates transmission of the received user data to the host computer.
  • the host computer receives the user data carried in the transmission initiated by the base station.
  • any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses.
  • Each virtual apparatus may comprise a number of these functional units.
  • These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein.
  • the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.
  • the term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • A1 An Ethernet-based method, implemented by an end device, for transporting Protocol Data Units (PDUs) over a Wireline Access Network (WAN), the method comprising:
  • a PDU Transport layer executing on the end device, a PDU from a PDU Application layer executing on the end device, wherein the PDU is one of an Ethernet PDU and a non-Ethernet PDU;
  • AMF Function
  • the PDU payload comprises:
  • SMAC Source Media Access Control
  • DMAC Destination Media Access Control
  • the PDU payload comprises one of:
  • generating the PDU Ethernet packet comprises inserting the PDU adaptation header of a Shim header behind an Ethernet header of the PDU payload.
  • A7 The method of any of embodiments A5-A6 wherein when the PDU usage flag indicates either the IP type PDU or the Unstructured type PDU, the method further comprises:
  • A8 The method of any of embodiments A5-A7 wherein when the PDU usage flag indicates NAS signaling transport, the method further comprises:
  • A1 1 The method of any of embodiments A5-A10 wherein the QFInfo field comprises a bitmap for uplink PDU transport, and wherein a first set of bits indicates an end of QoS to bearer mapping for a QoS Flow, and wherein a second set of bits indicates that the PDU payload should be ignored.
  • generating the PDU Ethernet packet comprises:
  • A16 The method of any of embodiments A1 -A4 wherein when the PDU is an Ethernet PDU, generating the PDU Ethernet packet comprises inserting the PDU adaptation header of an Ethernet PDU header in front of an Ethernet packet of the PDU payload.
  • A17 The method of embodiment A16 wherein the PDU adaptation header comprises an Ethernet header and a PDU header.
  • A19 The method of any of embodiments A16-A18 wherein when the PDU usage flag indicates either the IP type PDU or the Unstructured type PDU, the method further comprises setting, in the PDU header:
  • A20 The method of any of embodiments A16-A18 wherein when the PDU usage flag indicates NAS signaling transport, the method further comprises:
  • an SMAC field to a MAC address of a node operating the Ethernet header; and a DMAC field to a MAC address of one of the AGF and a broadcast MAC address.
  • NASoE NAS signaling over Ethernet
  • Ethernet PDU is present.
  • A23 The method of any of the preceding embodiments wherein the PDU usage flag indicates handling of the PDU Ethernet packet to the PDU T ransport layer.
  • A24 The method of any of the preceding embodiments further comprising the PDU Transport layer processing the PDU payload as an Ethernet payload regardless of whether the PDU payload is an IP type PDU, and Ethernet type PDU, or an Unstructured type PDU.
  • A25 The method of any of the preceding embodiments wherein the PDU ID field identifies PDU data of a DPU session.
  • the end device comprises a Third Generation Partnership Project (3GPP) device identified by a MAC address known to the PDU Transport layer.
  • 3GPP Third Generation Partnership Project
  • A27 The method of any of the preceding embodiments further comprising generating the PDU adaptation header according to one of a Shim method and an Ethernet PDU method.
  • sending the PDU Ethernet packet in the Ethernet frame to the AGF comprises sending the PDU Ethernet packet responsive to receiving a request to send the PDU Ethernet packet from the PDU Application layer.
  • the PDU control information comprises one or more of a MAC address, a PDU session ID, QoS Flow information, and PDU usage information.
  • An Ethernet-based method implemented by an Access Gateway Function (AGF) executing at a base station, for transporting Protocol Data Units (PDUs) to an end device over a Wireline Access Network (WAN), the method comprising:
  • SMAC Source Media Access Control
  • DMAC Destination Media Access Control
  • the PDU payload comprises one of:
  • Unstructured type PDU B1 1 .
  • the QFInfo field comprises a bitmap for uplink PDU transport, and wherein a first set of bits indicates an end of QoS to bearer mapping for a QoS Flow, and wherein a second set of bits indicates that the PDU payload should be ignored.
  • generating the PDU Ethernet packet comprises inserting the PDU adaptation header of an Ethernet PDU header in front of an Ethernet packet of the PDU payload.
  • an SMAC field to a MAC address of a node operating the Ethernet header; and a DMAC field to a MAC address of one of the AGF and a broadcast MAC address.
  • NASoE NAS signaling over Ethernet
  • Ethernet PDU is present.
  • invention B24 further comprising determining the MAC addresses of both the end device and a network node operating under 5G-RG.
  • B33 The method of any of the Group B embodiments further comprising identifying a bearer via VLAN priority for PDU data transport and for PDU NAS signaling transport.
  • B34 The method of any of the Group B embodiments wherein the QFInfo field comprises a bitmap for downlink PDU transport, and indicates one of:
  • QFI QoS Flow Identity
  • RQI Reflective QoS Indication
  • RDI Reflective QoS flow to DRB mapping Indication
  • mapping for a QoS Flow based on the flag.
  • any of the Group B embodiments further comprising processing a received PDU Ethernet packet according to one of a Shim method and an Ethernet PDU method based on the processing method used to process a previously received PDU Ethernet packet.
  • the PDU control information comprises one or more of a MAC address, a PDU session ID, QoS Flow information, and PDU usage information.
  • GROUP C EMBODIMENTS End Device apparatus claims
  • An end device in a wireless communication network comprising: an interface circuit configured for communication with one or more serving cells the wireless communication network; and
  • a processing circuit configured to:
  • AMF Function
  • An end device in a wireless communication network the end device being configured to:
  • ATF Access Gateway Function
  • the end device of embodiment C3 configured to perform any one of the methods of embodiments A2-A30.
  • a computer program comprising executable instructions that, when executed by a processing circuit in an end device in a wireless communication network, causes the end device to perform any one of the methods of embodiments A2-A30.
  • C6. A carrier containing a computer program of embodiment C5, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.
  • a wireless device comprising:
  • processing circuitry configured to perform any of the steps of any of the Group A embodiments.
  • power supply circuitry configured to supply power to the wireless device.
  • a wireless device comprising:
  • processing circuitry and memory
  • the memory containing instructions executable by the processing circuitry whereby the wireless device is configured to perform any of the steps of any of the Group A embodiments.
  • a user equipment comprising:
  • an antenna configured to send and receive wireless signals
  • radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry;
  • processing circuitry being configured to perform any of the steps of any of the Group A embodiments
  • an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry
  • an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry
  • C1 A computer program comprising instructions which, when executed by at least one processor of a wireless device, causes the wireless device to carry out the steps of any of the Group A embodiments.
  • a carrier containing the computer program of embodiment C1 1 wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.
  • a network node in a serving cell of the wireless communication network comprising:
  • an interface circuit configured for communication with one or more serving cells the wireless communication network
  • a processing circuit configured to:
  • a PDU Transport layer of the AGF receives, at a PDU Transport layer of the AGF, a PDU from a PDU Application layer executing on the AGF, wherein the PDU is one of an Ethernet PDU and a non-Ethernet PDU;
  • a network node in a wireless communication network the network node being configured to:
  • the network node of embodiment D3 configured to perform any one of the methods of embodiments B2-B39.
  • a computer program comprising executable instructions that, when executed by a processing circuit in a network node in a wireless communication network, causes the base station to perform any one of the methods of embodiments B2-B39.
  • a base station configured to perform any of the steps of any of the Group B embodiments.
  • a base station comprising:
  • processing circuitry configured to perform any of the steps of any of the Group B embodiments
  • a base station comprising:
  • the processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the base station is configured to perform any of the steps of any of the Group B embodiments.
  • D1 A computer program comprising instructions which, when executed by at least one processor of a base station, causes the base station to carry out the steps of any of the Group B embodiments.
  • a carrier containing the computer program of embodiment C1 1 wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.
  • a communication system including a host computer comprising:
  • processing circuitry configured to provide user data
  • a communication interface configured to forward the user data to a cellular network
  • UE user equipment
  • the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.
  • the communication system of the pervious embodiment further including the base station.
  • the UE is configured to communicate with the base station.
  • the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data
  • the UE comprises processing circuitry configured to execute a client application associated with the host application.
  • E5. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:
  • the host computer initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments.
  • a user equipment configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to perform any of the previous 3 embodiments.
  • a communication system including a host computer comprising:
  • processing circuitry configured to provide user data
  • a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE),
  • UE user equipment
  • the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of the Group A embodiments.
  • the cellular network further includes a base station configured to communicate with the UE.
  • the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data
  • the UE’s processing circuitry is configured to execute a client application
  • the host computer initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A embodiments.
  • a communication system including a host computer comprising:
  • a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of the Group A embodiments.
  • UE user equipment
  • the communication system of the previous 2 embodiments further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.
  • the processing circuitry of the host computer is configured to execute a host application
  • the UE’s processing circuitry is configured to execute a client application
  • the processing circuitry of the host computer is configured to execute a host application, thereby providing request data
  • the UE’s processing circuitry is configured to execute a client application
  • the host computer receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.
  • a communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.
  • UE user equipment
  • the communication system of the previous embodiment further including the base station.
  • the processing circuitry of the host computer is configured to execute a host application
  • the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.
  • the host computer receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.
  • E-SMLC Evolved-Serving Mobile Location Centre
  • ECGI Evolved CGI
  • IEEE Std 802 IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture, 2014.
  • IEEE Std 802.1 Q IEEE Standard for Local and metropolitan area networks-Bridges and Bridged Networks, 2014
  • IEEE Std 802.1 P IEEE Standard for Local and metropolitan area networks: AN Layer 2 QoS/CoS Protocol for Traffic Prioritization
  • IEEE Std 802.1 ad IEEE Standard for Local and Metropolitan Area Networks— Virtual Bridged Local Area Networks— Provider Bridges

Landscapes

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

Abstract

L'invention concerne un procédé basé sur Ethernet pour transporter des unités de données de protocole (PDU) sur un réseau d'accès filaire (WAN). Les PDU sont communiquées entre un dispositif d'extrémité et une fonction de passerelle d'accès (AGF). Le dispositif d'extrémité peut être un équipement utilisateur (UE) compatible 3GPP ou non compatible 3GPP. L'AGF peut être exécuté sur un nœud de réseau, tel qu'un 5G-RG, reliant de manière communicante le dispositif d'extrémité à un 5GC. Dans certains cas, l'AGF et/ou le dispositif d'extrémité peuvent fonctionner comme un nœud de relais pour un autre dispositif.
PCT/IB2020/056033 2019-06-27 2020-06-25 Transport de pdu à base ethernet pour dispositifs à connecter à un cœur 5g convergent par l'intermédiaire de réseaux d'accès filaire (wans) WO2020261181A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNPCT/CN2019/093267 2019-06-27
CN2019093267 2019-06-27

Publications (1)

Publication Number Publication Date
WO2020261181A1 true WO2020261181A1 (fr) 2020-12-30

Family

ID=71784334

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2020/056033 WO2020261181A1 (fr) 2019-06-27 2020-06-25 Transport de pdu à base ethernet pour dispositifs à connecter à un cœur 5g convergent par l'intermédiaire de réseaux d'accès filaire (wans)

Country Status (1)

Country Link
WO (1) WO2020261181A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016124152A1 (fr) * 2015-02-05 2016-08-11 Mediatek Inc. Procédé et appareil de routage lwa de pdu
WO2019047197A1 (fr) * 2017-09-11 2019-03-14 Telefonaktiebolaget Lm Ericsson (Publ) Procédé et système pour intégrer un accès fixe dans un cœur 5g convergé

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016124152A1 (fr) * 2015-02-05 2016-08-11 Mediatek Inc. Procédé et appareil de routage lwa de pdu
WO2019047197A1 (fr) * 2017-09-11 2019-03-14 Telefonaktiebolaget Lm Ericsson (Publ) Procédé et système pour intégrer un accès fixe dans un cœur 5g convergé

Non-Patent Citations (19)

* Cited by examiner, † Cited by third party
Title
"5G Fixed Mobile Convergence Study", BBF SD-407, Retrieved from the Internet <URL:https://wiki.broadband-forum.org/display/BBF/SD-407+5G+Fixed+Mobile+Convergence+Study>
"5G NAS protocol", 3GPP TS24.501VF10
"5G NGAP protocol for N2 interface", 3GPP TS38.413VF10
"5G policy and charging control framework", 3GPP TS 23.503VF10
"5G System Architecture Accesses", 3GPP TS 23.501 VF10
"5G System Architecture Accesses", 3GPP TS 23.501VF10
"5G System Procedures", 3GPP TS 23.502VF10
"GRE Tunnel Bonding Protocol", IETF RFC
"IEEE Standard for Local and metropolitan area networks: AN Layer 2 QoS/CoS Protocol for Traffic Prioritization", IEEE STD 802.1 P
"IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture", IEEE STD 802, 2014
"IEEE Standard for Local and metropolitan area networks-Bridges and Bridged Networks", IEEE STD 802.1Q, 2014
"IEEE Standard for Local and Metropolitan Area Networks--Virtual Bridged Local Area Networks --- Provider Bridges", IEEE STD 802.1AD
"IEEE Standard for Local and Metropolitan Area Networks--Virtual Bridged Local Area Networks---Provider Bridges", IEEE STD 802.1AD
"Migration to Ethernet-Based Broadband Aggregation", BBF TR-101
"Migration to Ethernet-Based Broadband Aggregation, Issue 2", BBF TR-101
"Service data adaption protocol: SDAP", 3GPP TS37.324VF10
"Wireless and Wireline Convergence for 5G System Architecture", 3GPP TR23.716VG00
BBF SD-407 5G FIXED MOBILE CONVERGENCE STUDY, Retrieved from the Internet <URL:https://wiki.broadband-forum.org/display/BBF/SD-407+5G+Fixed+Mobile+Convergence+Study>
BBF SD-420 5G FIXED MOBILE CONVERGENCE STUDY, Retrieved from the Internet <URL:https://wiki.broadband-forum.org/pages/viewpage.action?spaceKey=BBF&title=SD-420+R1bis+5G+Fixed+Mobile+Convergence+Study>

Similar Documents

Publication Publication Date Title
AU2018370453B2 (en) Notification control over RAN interfaces
EP3997929B1 (fr) Informations de mappage pour liaison terrestre à accès intégré
EP3753302A1 (fr) Procede pour permettre a des noeuds d&#39;acces et de raccordement integres (iab) nouvelle radio (nr) de fonctionner dans des cellules non autonomes (nsa)
US11616602B2 (en) Segment concatenation in radio link control status reports
EP3847844B1 (fr) Transport de flux de données sur des réseaux cellulaires
US20210399834A1 (en) Method to manage downlink data delivery status
CN115065440B (zh) 避免通过5g nas传输来传输的信令的多次重传
WO2021006789A2 (fr) Informations de mise en correspondance pour accès et backhaul intégrés
US20220377595A1 (en) Mapping Information for Integrated Access and Backhaul
US11606693B2 (en) Application of integrity protection in a wireless communication network
US20230007565A1 (en) Defailt path assignment in iab networks
EP4154581A1 (fr) Demande de stockage d&#39;informations pour une pluralité de cellules
US20220158973A1 (en) Data network name (dnn) manipulation
US20220131774A1 (en) Data volume reporting in 5gs
WO2020261181A1 (fr) Transport de pdu à base ethernet pour dispositifs à connecter à un cœur 5g convergent par l&#39;intermédiaire de réseaux d&#39;accès filaire (wans)
WO2019158772A1 (fr) Sélection d&#39;amf pour un équipement d&#39;utilisateur situé en arrière-plan d&#39;un équipement de locaux d&#39;abonné
US20230412688A1 (en) Methods and apparatuses for providing header compression protocol reset

Legal Events

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

Ref document number: 20745284

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20745284

Country of ref document: EP

Kind code of ref document: A1