WO2022170213A1 - Data-centric communication and computing system architecture - Google Patents

Data-centric communication and computing system architecture Download PDF

Info

Publication number
WO2022170213A1
WO2022170213A1 PCT/US2022/015528 US2022015528W WO2022170213A1 WO 2022170213 A1 WO2022170213 A1 WO 2022170213A1 US 2022015528 W US2022015528 W US 2022015528W WO 2022170213 A1 WO2022170213 A1 WO 2022170213A1
Authority
WO
WIPO (PCT)
Prior art keywords
function
control
data
controller
plane
Prior art date
Application number
PCT/US2022/015528
Other languages
French (fr)
Inventor
Zongrui DING
Qian Li
Geng Wu
Original Assignee
Intel Corporation
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 Intel Corporation filed Critical Intel Corporation
Publication of WO2022170213A1 publication Critical patent/WO2022170213A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/78—Architectures of resource allocation
    • H04L47/781—Centralised allocation of resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/04—Network management architectures or arrangements
    • H04L41/044—Network management architectures or arrangements comprising hierarchical management structures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/04—Network management architectures or arrangements
    • H04L41/052—Network management architectures or arrangements using standardised network management architectures, e.g. telecommunication management network [TMN] or unified network management architecture [UNMA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities

Definitions

  • Various embodiments generally may relate to the field of wireless communications.
  • some embodiments may relate to data-centric communication and computing system architectures.
  • the innovative Optical and Wireless Network (I0WN) Global Forum (GF) is working on a data centric communication and computing system architecture.
  • Embodiments of the present disclosure are directed to data-centric computing and communication infrastructure and system (DIS) architectures.
  • Figure 1 illustrates an example of a data-centric computing and communication infrastructure and system (DIS) architecture in accordance with various embodiments.
  • DIS data-centric computing and communication infrastructure and system
  • Figure 2 illustrates a service an functional view of a DIS architecture in accordance with various embodiments.
  • Figure 3 schematically illustrates a wireless network in accordance with various embodiments.
  • Figure 4 schematically illustrates components of a wireless network in accordance with various embodiments.
  • Figure 5 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • Figures 6, 7, and 8 depict examples of procedures for practicing the various embodiments discussed herein.
  • embodiments of the present disclosure are directed to a data-centric computing and communication infrastructure and system (DIS) architecture.
  • DIS data-centric computing and communication infrastructure and system
  • Control plane is comprised of a function-dedicated computing (FDC) controller, data plane controller, function-dedicated network (FDN) controller, all-photonics network (APN) controller.
  • FDC function-dedicated computing
  • FDN function-dedicated network
  • API all-photonics network
  • User plane is comprised of a function dedicated computing function, data plane function, functional dedicated network function, APN
  • Compute plane functions include: FDN controller, function-dedicated computing function.
  • Data plane functions include: data plane controller, data plane function.
  • Communication plane functions include: FDN controller, Function dedicated network function, APN controller and APN.
  • the infrastructure orchestrator is part of management plane functions
  • o Service expose function is used to expose services provided by the DIS, and allow external users to request and use services provided by the DIS.
  • FIG. 1 The system architecture showed in Figure 1 focuses on high level functional blocks. To provide further details, a system diagram showing both service and functions is showed in Figure 2, where a Control and Management Service Mesh is used to provide service interfaces for control and management plane functions.
  • a service exposure function for cloud and a service exposure function for device and access network are introduced to expose DIS service and enable CSP, device and access networks to use DIS and APN services.
  • multiple control services are defined as shown in Figure 2.
  • the control services can be held by one or multiple control functions, e.g., services provided by the FDC controller can reside in a single FDC controller function or be split into FDC formation control function, FDC resource control function, FDC service control function, FDC monitoring and telemetry control function.
  • the interfaces among control functions are service based interfaces, e.g., each control function expose its services to the other control functions, control functions request for each other’s services.
  • control plane functions may include one or more functions to: form/configure the data processing pipeline, form function dedicated computing functions, form function dedicated network function, control resources and services, perform monitoring and collect telemetry data, control data sharing services, control data processing, control data analytics services, control data security, privacy and integrity.
  • the user plane provides a data pipeline service. User data processing and movement are confined within the user plane.
  • the management plane functions may include one or more functions to: deploy/onboard new services, provision for new services, monitor performance, manage system failures, optimize system performance, orchestrate system resources
  • Figures 3-5 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.
  • FIG. 3 illustrates a network 300 in accordance with various embodiments.
  • the network 300 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems.
  • 3GPP technical specifications for LTE or 5G/NR systems 3GPP technical specifications for LTE or 5G/NR systems.
  • the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3GPP systems, or the like.
  • the network 300 may include a UE 302, which may include any mobile or non-mobile computing device designed to communicate with a RAN 304 via an over-the-air connection.
  • the UE 302 may be communicatively coupled with the RAN 304 by a Uu interface.
  • the UE 302 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, loT device, etc.
  • the network 300 may include a plurality of UEs coupled directly with one another via a sidelink interface.
  • the UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.
  • the UE 302 may additionally communicate with an AP 306 via an over-the-air connection.
  • the AP 306 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 304.
  • the connection between the UE 302 and the AP 306 may be consistent with any IEEE 802.11 protocol, wherein the AP 306 could be a wireless fidelity (Wi-Fi®) router.
  • the UE 302, RAN 304, and AP 306 may utilize cellular-WLAN aggregation (for example, LWA/LWIP).
  • Cellular- WLAN aggregation may involve the UE 302 being configured by the RAN 304 to utilize both cellular radio resources and WLAN resources.
  • the RAN 304 may include one or more access nodes, for example, AN 308.
  • AN 308 may terminate air-interface protocols for the UE 302 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and LI protocols. In this manner, the AN 308 may enable data/voice connectivity between CN 320 and the UE 302.
  • the AN 308 may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network, which may be referred to as a CRAN or virtual baseband unit pool.
  • the AN 308 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc.
  • the AN 308 may be a macrocell base station or a low power base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.
  • the RAN 304 may be coupled with one another via an X2 interface (if the RAN 304 is an LTE RAN) or an Xn interface (if the RAN 304 is a 5G RAN).
  • the X2/Xn interfaces which may be separated into control/user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc.
  • the ANs of the RAN 304 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 302 with an air interface for network access.
  • the UE 302 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 304.
  • the UE 302 and RAN 304 may use carrier aggregation to allow the UE 302 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell.
  • a first AN may be a master node that provides an MCG and a second AN may be secondary node that provides an SCG.
  • the first/second ANs may be any combination of eNB, gNB, ng-eNB, etc.
  • the RAN 304 may provide the air interface over a licensed spectrum or an unlicensed spectrum.
  • the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCells/Scells.
  • the nodes Prior to accessing the unlicensed spectrum, the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol.
  • LBT listen-before-talk
  • the UE 302 or AN 308 may be or act as a RSU, which may refer to any transportation infrastructure entity used for V2X communications.
  • An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE.
  • an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs.
  • the RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic.
  • the RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN communications services.
  • the components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.
  • the RAN 304 may be an LTE RAN 310 with eNBs, for example, eNB 312.
  • the LTE RAN 310 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc.
  • the LTE air interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation/ detection at the UE.
  • the LTE air interface may operating on sub-6 GHz bands.
  • the RAN 304 may be an NG-RAN 314 with gNBs, for example, gNB 316, or ng-eNBs, for example, ng-eNB 318.
  • the gNB 316 may connect with 5G-enabled UEs using a 5G NR interface.
  • the gNB 316 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface.
  • the ng-eNB 318 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface.
  • the gNB 316 and the ng-eNB 318 may connect with each other over an Xn interface.
  • the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 314 and a UPF 348 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN314 and an AMF 344 (e.g., N2 interface).
  • NG-U NG user plane
  • N3 interface e.g., N3 interface
  • N-C NG control plane
  • the NG-RAN 314 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data.
  • the 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS similar to the LTE air interface.
  • the 5G-NR air interface may not use a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking.
  • the 5G-NR air interface may operating on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz.
  • the 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS/SSS/PBCH.
  • the 5G-NR air interface may utilize BWPs for various purposes.
  • BWP can be used for dynamic adaptation of the SCS.
  • the UE 302 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 302, the SCS of the transmission is changed as well.
  • Another use case example of BWP is related to power saving.
  • multiple BWPs can be configured for the UE 302 with different amount of frequency resources (for example, PRBs) to support data transmission under different traffic loading scenarios.
  • a BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 302 and in some cases at the gNB 316.
  • a BWP containing a larger number of PRBs can be used for scenarios with higher traffic load.
  • the RAN 304 is communicatively coupled to CN 320 that includes network elements to provide various functions to support data and telecommunications services to customers/subscribers (for example, users of UE 302).
  • the components of the CN 320 may be implemented in one physical node or separate physical nodes.
  • NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 320 onto physical compute/storage resources in servers, switches, etc.
  • a logical instantiation of the CN 320 may be referred to as a network slice, and a logical instantiation of a portion of the CN 320 may be referred to as a network sub-slice.
  • the CN 320 may be an LTE CN 322, which may also be referred to as an EPC.
  • the LTE CN 322 may include MME 324, SGW 326, SGSN 328, HSS 330, PGW 332, and PCRF 334 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the LTE CN 322 may be briefly introduced as follows.
  • the MME 324 may implement mobility management functions to track a current location of the UE 302 to facilitate paging, bearer activation/ deactivation, handovers, gateway selection, authentication, etc.
  • the SGW 326 may terminate an SI interface toward the RAN and route data packets between the RAN and the LTE CN 322.
  • the SGW 326 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3 GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
  • the SGSN 328 may track a location of the UE 302 and perform security functions and access control. In addition, the SGSN 328 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 324; MME selection for handovers; etc.
  • the S3 reference point between the MME 324 and the SGSN 328 may enable user and bearer information exchange for inter-3 GPP access network mobility in idle/active states.
  • the HSS 330 may include a database for network users, including subscription-related information to support the network entities’ handling of communication sessions.
  • the HSS 330 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • An S6a reference point between the HSS 330 and the MME 324 may enable transfer of subscription and authentication data for authentic ating/authorizing user access to the LTE CN 320.
  • the PGW 332 may terminate an SGi interface toward a data network (DN) 336 that may include an application/content server 338.
  • the PGW 332 may route data packets between the LTE CN 322 and the data network 336.
  • the PGW 332 may be coupled with the SGW 326 by an S5 reference point to facilitate user plane tunneling and tunnel management.
  • the PGW 332 may further include a node for policy enforcement and charging data collection (for example, PCEF).
  • the SGi reference point between the PGW 332 and the data network 3 36 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services.
  • the PGW 332 may be coupled with a PCRF 334 via a Gx reference point.
  • the PCRF 334 is the policy and charging control element of the LTE CN 322.
  • the PCRF 334 may be communicatively coupled to the app/content server 338 to determine appropriate QoS and charging parameters for service flows.
  • the PCRF 332 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI.
  • the CN 320 may be a 5GC 340.
  • the 5GC 340 may include an AUSF 342, AMF 344, SMF 346, UPF 348, NSSF 350, NEF 352, NRF 354, PCF 356, UDM 358, and AF 360 coupled with one another over interfaces (or “reference points”) as shown.
  • Functions of the elements of the 5GC 340 may be briefly introduced as follows.
  • the AUSF 342 may store data for authentication of UE 302 and handle authentication- related functionality.
  • the AUSF 342 may facilitate a common authentication framework for various access types.
  • the AUSF 342 may exhibit an Nausf service-based interface.
  • the AMF 344 may allow other functions of the 5GC 340 to communicate with the UE 302 and the RAN 304 and to subscribe to notifications about mobility events with respect to the UE 302.
  • the AMF 344 may be responsible for registration management (for example, for registering UE 302), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization.
  • the AMF 344 may provide transport for SM messages between the UE 302 and the SMF 346, and act as a transparent proxy for routing SM messages.
  • AMF 344 may also provide transport for SMS messages between UE 302 and an SMSF.
  • AMF 344 may interact with the AUSF 342 and the UE 302 to perform various security anchor and context management functions.
  • AMF 344 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 304 and the AMF 344; and the AMF 344 may be a termination point of NAS (Nl) signaling, and perform NAS ciphering and integrity protection.
  • AMF 344 may also support NAS signaling with the UE 302 over an N3 IWF interface.
  • the SMF 346 may be responsible for SM (for example, session establishment, tunnel management between UPF 348 and AN 308); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 348 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 344 over N2 to AN 308; and determining SSC mode of a session.
  • SM may refer to management of a PDU session, and a PDU session or “session” may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 302 and the data network 336.
  • the UPF 348 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 336, and a branching point to support multi-homed PDU session.
  • the UPF 348 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform uplink traffic verification (e.g., SDF- to-QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering.
  • UPF 348 may include an uplink classifier to support routing traffic flows to a data network.
  • the NSSF 350 may select a set of network slice instances serving the UE 302.
  • the NSSF 350 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed.
  • the NSSF 350 may also determine the AMF set to be used to serve the UE 302, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 354.
  • the selection of a set of network slice instances for the UE 302 may be triggered by the AMF 344 with which the UE 302 is registered by interacting with the NSSF 350, which may lead to a change of AMF.
  • the NSSF 350 may interact with the AMF 344 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown). Additionally, the NSSF 350 may exhibit an Nnssf service-based interface.
  • the NEF 352 may securely expose services and capabilities provided by 3GPP network functions for third party, internal exposure/re-exposure, AFs (e.g., AF 360), edge computing or fog computing systems, etc.
  • AFs e.g., AF 360
  • the NEF 352 may authenticate, authorize, or throttle the AFs.
  • NEF 352 may also translate information exchanged with the AF 360 and information exchanged with internal network functions. For example, the NEF 352 may translate between an AF-Service-Identifier and an internal 5GC information.
  • NEF 352 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 352 as structured data, or at a data storage NF using standardized interfaces.
  • the stored information can then be re-exposed by the NEF 352 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 352 may exhibit an Nnef service-based interface.
  • the NRF 354 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 354 also maintains information of available NF instances and their supported services.
  • the terms “instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 354 may exhibit the Nnrf service-based interface.
  • the PCF 356 may provide policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior.
  • the PCF 356 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 358.
  • the PCF 356 exhibit an Npcf service-based interface.
  • the UDM 358 may handle subscription-related information to support the network entities’ handling of communication sessions, and may store subscription data of UE 302. For example, subscription data may be communicated via an N8 reference point between the UDM 358 and the AMF 344.
  • the UDM 358 may include two parts, an application front end and a UDR.
  • the UDR may store subscription data and policy data for the UDM 358 and the PCF 356, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 302) for the NEF 352.
  • the Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 358, PCF 356, and NEF 352 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR.
  • the UDM may include a UDM- FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions.
  • the UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management.
  • the UDM 358 may exhibit the Nudm service-based interface.
  • the AF 360 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control.
  • the 5GC 340 may enable edge computing by selecting operator/3 rd party services to be geographically close to a point that the UE 302 is attached to the network. This may reduce latency and load on the network.
  • the 5GC 340 may select a UPF 348 close to the UE 302 and execute traffic steering from the UPF 348 to data network 336 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 360. In this way, the AF 360 may influence UPF (re)selection and traffic routing.
  • the network operator may permit AF 360 to interact directly with relevant NFs. Additionally, the AF 360 may exhibit an Naf service-based interface.
  • the data network 336 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application/content server 338.
  • FIG. 4 schematically illustrates a wireless network 400 in accordance with various embodiments.
  • the wireless network 400 may include a UE 402 in wireless communication with an AN 404.
  • the UE 402 and AN 404 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein.
  • the UE 402 may be communicatively coupled with the AN 404 via connection 406.
  • the connection 406 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6GHz frequencies.
  • the UE 402 may include a host platform 408 coupled with a modem platform 410.
  • the host platform 408 may include application processing circuitry 412, which may be coupled with protocol processing circuitry 414 of the modem platform 410.
  • the application processing circuitry 412 may run various applications for the UE 402 that source/sink application data.
  • the application processing circuitry 412 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations
  • the protocol processing circuitry 414 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 406.
  • the layer operations implemented by the protocol processing circuitry 414 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.
  • the modem platform 410 may further include digital baseband circuitry 416 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 414 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symboFbit metric determination, multi-antenna port precoding/decoding, which may include one or more of space-time, space-frequency or spatial coding, reference signal generation/ detection, preamble sequence generation and/or decoding, synchronization sequence generation/ detection, control channel signal blind decoding, and other related functions.
  • PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symboFbit metric determination, multi-antenna port precoding/decoding, which may
  • the modem platform 410 may further include transmit circuitry 418, receive circuitry 420, RF circuitry 422, and RF front end (RFFE) 424, which may include or connect to one or more antenna panels 426.
  • the transmit circuitry 418 may include a digital-to-analog converter, mixer, intermediate frequency (IF) components, etc.
  • the receive circuitry 420 may include an analog-to-digital converter, mixer, IF components, etc.
  • the RF circuitry 422 may include a low-noise amplifier, a power amplifier, power tracking components, etc.
  • RFFE 424 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc.
  • transmit/receive components may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mmWave or sub-6 gHz frequencies, etc.
  • the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc.
  • the protocol processing circuitry 414 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components.
  • a UE reception may be established by and via the antenna panels 426, RFFE 424, RF circuitry 422, receive circuitry 420, digital baseband circuitry 416, and protocol processing circuitry 414.
  • the antenna panels 426 may receive a transmission from the AN 404 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 426.
  • a UE transmission may be established by and via the protocol processing circuitry 414, digital baseband circuitry 416, transmit circuitry 418, RF circuitry 422, RFFE 424, and antenna panels 426.
  • the transmit components of the UE 404 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 426.
  • the AN 404 may include a host platform 428 coupled with a modem platform 430.
  • the host platform 428 may include application processing circuitry 432 coupled with protocol processing circuitry 434 of the modem platform 430.
  • the modem platform may further include digital baseband circuitry 436, transmit circuitry 438, receive circuitry 440, RF circuitry 442, RFFE circuitry 444, and antenna panels 446.
  • the components of the AN 404 may be similar to and substantially interchangeable with like-named components of the UE 402.
  • the components of the AN 408 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.
  • Figure 5 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • Figure 5 shows a diagrammatic representation of hardware resources 500 including one or more processors (or processor cores) 510, one or more memory/storage devices 520, and one or more communication resources 530, each of which may be communicatively coupled via a bus 540 or other interface circuitry.
  • node virtualization e.g., NFV
  • a hypervisor 502 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 500.
  • the processors 510 may include, for example, a processor 512 and a processor 514.
  • the processors 510 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.
  • CPU central processing unit
  • RISC reduced instruction set computing
  • CISC complex instruction set computing
  • GPU graphics processing unit
  • DSP such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.
  • the memory/storage devices 520 may include main memory, disk storage, or any suitable combination thereof.
  • the memory/storage devices 520 may include, but are not limited to, any type of volatile, non-volatile, or semi-volatile memory such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.
  • DRAM dynamic random access memory
  • SRAM static random access memory
  • EPROM erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • Flash memory solid-state storage, etc.
  • the communication resources 530 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 504 or one or more databases 506 or other network elements via a network 508.
  • the communication resources 530 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.
  • Instructions 550 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 510 to perform any one or more of the methodologies discussed herein.
  • the instructions 550 may reside, completely or partially, within at least one of the processors 510 (e.g., within the processor’s cache memory), the memory/storage devices 520, or any suitable combination thereof.
  • any portion of the instructions 550 may be transferred to the hardware resources 500 from any combination of the peripheral devices 504 or the databases 506.
  • the memory of processors 510, the memory/storage devices 520, the peripheral devices 504, and the databases 506 are examples of computer-readable and machine -readable media.
  • the electronic device(s), network(s), system(s), chip(s) or component(s), or portions or implementations thereof, of Figures 3-5, or some other figure herein may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof.
  • process 600 may include, at 605, providing a management plane function based on management plane function information, the management plane function including an infrastructure orchestrator for a data- centric communication and computing infrastructure (DIS) system.
  • DIS data- centric communication and computing infrastructure
  • the process further includes, at 610, providing a control plane function based on control plane function information, the control plane function including: a function dedicated compute (FDC) controller, a data plane controller, a function-dedicated network (FDN) controller, or an all-photonics network (APN) controller.
  • the process further includes, at 615, providing a user plane function based on the user plane function information, the user plane function including: an FDC function, a data plane function, an FDN function, or an APN function.
  • the process 700 includes, at 705, Providing a management plane function that includes an infrastructure orchestrator for a data-centric communication and computing infrastructure (DIS) system.
  • the process further includes, at 710, providing a control plane function that includes: a function dedicated compute (FDC) controller, a data plane controller, a function-dedicated network (FDN) controller, or an all-photonics network (APN) controller.
  • the process further includes, at 715, providing a user plane function that includes: an FDC function, a data plane function, an FDN function, or an APN function.
  • the process further includes, at 720, providing a compute plane function that includes an FDN controller or FDC function.
  • the process further includes, at 725, providing a data plane function and a data plane controller.
  • the process 800 includes, at 805, providing a management plane function that includes an infrastructure orchestrator for the DIS system.
  • the process further includes, at 810, providing a plurality of control plane functions in communication with the infrastructure orchestrator via a control and management services mesh and that include: a function dedicated compute (FDC) controller, a data plane controller, a function-dedicated network (FDN) controller, or an all-photonics network (APN) controller.
  • the process further includes, at 815, providing a plurality of user plane functions in communication with the plurality of control plane functions and that include: an FDC function, a data plane function, an FDN function, or an APN function.
  • the process further includes, at 820, providing a compute plane function that includes an FDN controller or FDC function.
  • the process further includes, at 825, providing a data plane function and a data plane controller.
  • At least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below.
  • the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below.
  • circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.
  • Example 1 may include a data-centric computing and communication infrastructure and system (DIS) architecture (e.g., as shown in Figure 1 and/or Figure 2) comprising one or more of the following components: o Management plane, control plane, user plane, compute plane, data plane and communication plane o Control plane is comprised by FDC (function dedicated compute) controller, Data plane controller, FDN (function dedicated network) controller, APN (allphotonics network) controller o User plane is comprised by Function dedicated computing function, data plane function, functional dedicated network function, APN o Compute plane functions include: FDN controller, Function dedicated computing function o Data plane functions include: Data plane controller, Data plane function o Communication plane functions include: FDN controller, Function dedicated network function, APN controller and APN o The infrastructure orchestrator is part of management plane functions.
  • DIS data-centric computing and communication infrastructure and system
  • Example 2 may include Control and Management Service Mesh is used to provide service interfaces for control and management plane functions.
  • Control and Management Service Mesh is used to provide service interfaces for control and management plane functions.
  • Each control and management function expose its services to the other control and management functions; and/or o Control and management functions request for each other’s services.
  • Example 3 may include a service exposure function for cloud and a service exposure function for device and access network.
  • the service expose function is used to expose DIS service and enable CSP, device and access networks to use DIS and APN services.
  • Example 4 may include control Plane services include: form/configure the data processing pipeline, form function dedicated computing functions, form function dedicated network function, control resources and services, perform monitoring and collect telemetry data, control data sharing services, control data processing, control data analytics services, control data security, privacy and integrity.
  • control Plane services include: form/configure the data processing pipeline, form function dedicated computing functions, form function dedicated network function, control resources and services, perform monitoring and collect telemetry data, control data sharing services, control data processing, control data analytics services, control data security, privacy and integrity.
  • Example 5 may include user plane provide data pipeline service. User data processing and movement are confined within user plane.
  • Example 6 may include management Plane services include: deploy/onboard new services, provision for new services, monitor performance, manage system failures, optimize system performance, orchestrate system resources.
  • Example 7 may include the control services are held by one or multiple control functions, for example, including one or more of the following features: o Services provided by the FDC controller can reside in a single FDC controller function or be split into FDC formation control function, FDC resource control function, FDC service control function, FDC monitoring and telemetry control function or a combination of them. o Services provided by the Data plane controller can reside in a single Data plane controller function or be split into Data sharing control, data processing control, data analytics control, data security control, or a combination of them. o Services provided by the FDN controller can reside in a single FDN controller function or be split into FDN formation control function, FDN resource control function, FDN service control function, FDN monitoring and telemetry control function or a combination of them.
  • APN controller can reside in a single APN controller function or be split into dynamic/static path control, bandwidth control, route control, monitoring/telemetry, or a combination of them.
  • the interfaces among control functions are service based interfaces, e.g., each control function expose its services to the other control functions, control functions request for each other’s services.
  • Example XI includes an apparatus comprising: memory to store management plane function information, control plane function information, and user plane function information; and processing circuitry, coupled with the memory, to: provide a management plane function based on the management plane function information, the management plane function including an infrastructure orchestrator for a data- centric communication and computing infrastructure (DIS) system; provide a control plane function based on the control plane function information, the control plane function including: a function dedicated compute (FDC) controller, a data plane controller, a function-dedicated network (FDN) controller, or an all-photonics network (APN) controller; and provide a user plane function based on the user plane function information, the user plane function including: an FDC function, a data plane function, an FDN function, or an APN function.
  • FDC function dedicated compute
  • FDN function-dedicated network
  • API all-photonics network
  • Example X2 includes the apparatus of example XI or some other example herein, wherein the processing circuitry is further to provide a compute plane function that includes an FDN controller or FDC function.
  • Example X3 includes the apparatus of example XI or some other example herein, wherein the processing circuitry is further to provide a data plane function or a data plane controller.
  • Example X4 includes the apparatus of example XI or some other example herein, wherein the processing circuitry is further to provide a communication plane function that includes an FDN controller, an FDN function, an APN controller, or an APN function.
  • Example X5 includes the apparatus of example XI or some other example herein, wherein the processing circuitry is further to provide a control and management service mesh that provides service interfaces for the control plane function and management plane function.
  • Example X6 includes the apparatus of example XI or some other example herein, wherein the processing circuitry is further to provide a service exposure function that is to expose a DIS service or an APN service.
  • Example X7 includes the apparatus of example XI or some other example herein, wherein the processing circuitry is further to provide a control plane service that includes a service to: form or configure a data processing pipeline; form a function-dedicated computing function; form a function-dedicated network function; control resources and services; perform monitoring and collect telemetry data; control data sharing services; control data processing; control data analytics services; or control data security, privacy and integrity.
  • Example X8 includes the apparatus of example XI or some other example herein, wherein the processing circuitry is further to provide a user plane data pipeline service.
  • Example X9 includes the apparatus of any of examples X1-X8, wherein the processing circuitry is further to provide a management plane service that includes a service to: deploy or onboard new services; provision new services; monitor performance; manage system failures; optimize system performance; or orchestrate system resources.
  • a management plane service that includes a service to: deploy or onboard new services; provision new services; monitor performance; manage system failures; optimize system performance; or orchestrate system resources.
  • Example X10 includes the apparatus of any of examples XI -X9, wherein the processing circuitry is further to provide a control plane service that includes: a service provided by an FDC controller that resides in a single FDC controller function or that is split into: an FDC formation control function, an FDC resource control function, an FDC service control function, an FDC monitoring and telemetry control function, or combinations thereof; a service provided by a data plane controller that resides in a single data plane controller function or that is split into: a data sharing control function, a data processing control function, a data analytics control function, a data security control function, or combinations thereof; a service provided by an FDN controller that resides in a single FDN controller function or that is split into: an FDN formation control function, an FDN resource control function, an FDN service control function, an FDN monitoring and telemetry control function, or combinations thereof; or a service provided by an APN controller that resides in a single APN controller function or that is split into: a dynamic or static path control
  • Example XI 1 includes one or more computer-readable media storing instructions that, when executed by one or more processors, cause a computing device to: provide a management plane function that includes an infrastructure orchestrator for a data-centric communication and computing infrastructure (DIS) system; provide a control plane function that includes: a function dedicated compute (FDC) controller, a data plane controller, a function-dedicated network (FDN) controller, or an allphotonics network (APN) controller; provide a user plane function that includes: an FDC function, a data plane function, an FDN function, or an APN function; provide a compute plane function that includes an FDN controller or FDC function; and provide a data plane function and a data plane controller.
  • DIS data-centric communication and computing infrastructure
  • FDC function dedicated compute
  • FDN function-dedicated network
  • API allphotonics network
  • Example X12 includes the one or more computer-readable media of example XI 1 or some other example herein, wherein the media further stores instructions to provide a communication plane function that includes an FDN controller, an FDN function, an APN controller, or an APN function.
  • Example XI 3 includes the one or more computer-readable media of example XI 1 or some other example herein, wherein the media further stores instructions to provide a control and management service mesh that provides service interfaces for the control plane function and management plane function.
  • Example X14 includes the one or more computer-readable media of example XI 1 or some other example herein, wherein the media further stores instructions to provide a service exposure function that is to expose a DIS service or an APN service.
  • Example X15 includes the one or more computer-readable media of example XI 1 or some other example herein, wherein the media further stores instructions to provide a control plane service that includes a service to: form or configure a data processing pipeline; form a function-dedicated computing function; form a function-dedicated network function; control resources and services; perform monitoring and collect telemetry data; control data sharing services; control data processing; control data analytics services; or control data security, privacy and integrity.
  • a control plane service that includes a service to: form or configure a data processing pipeline; form a function-dedicated computing function; form a function-dedicated network function; control resources and services; perform monitoring and collect telemetry data; control data sharing services; control data processing; control data analytics services; or control data security, privacy and integrity.
  • Example X16 includes the one or more computer-readable media of example XI 1 or some other example herein, wherein the media further stores instructions to provide a user plane data pipeline service.
  • Example X17 includes the one or more computer-readable media of any of examples XI 1 -XI 6, wherein the media further stores instructions to provide a management plane service that includes a service to: deploy or onboard new services; provision new services; monitor performance; manage system failures; optimize system performance; or orchestrate system resources.
  • a management plane service that includes a service to: deploy or onboard new services; provision new services; monitor performance; manage system failures; optimize system performance; or orchestrate system resources.
  • Example XI 8 includes the one or more computer-readable media of any of examples XI 1 -XI 7, wherein the media further stores instructions to provide a control plane service that includes: a service provided by an FDC controller that resides in a single FDC controller function or that is split into: an FDC formation control function, an FDC resource control function, an FDC service control function, an FDC monitoring and telemetry control function, or combinations thereof; a service provided by a data plane controller that resides in a single data plane controller function or that is split into: a data sharing control function, a data processing control function, a data analytics control function, a data security control function, or combinations thereof; a service provided by an FDN controller that resides in a single FDN controller function or that is split into: an FDN formation control function, an FDN resource control function, an FDN service control function, an FDN monitoring and telemetry control function, or combinations thereof; or a service provided by an APN controller that resides in a single APN controller function or that is split into:
  • Example XI 9 includes one or more computer-readable media storing instructions that, when executed by one or more processors, cause a data-centric communication and computing infrastructure (DIS) system to: provide a management plane function that includes an infrastructure orchestrator for the DIS system; provide a plurality of control plane functions in communication with the infrastructure orchestrator via a control and management services mesh and that include: a function dedicated compute (FDC) controller, a data plane controller, a function-dedicated network (FDN) controller, or an all-photonics network (APN) controller; provide a plurality of user plane functions in communication with the plurality of control plane functions and that include: an FDC function, a data plane function, an FDN function, or an APN function; provide a compute plane function that includes an FDN controller or FDC function; and provide a data plane function and a data plane controller.
  • FDC function dedicated compute
  • FDN function-dedicated network
  • API all-photonics network
  • Example X20 includes the one or more computer-readable media of example XI 9 or some other example herein, wherein the media further stores instructions to provide a communication plane function that includes an FDN controller, an FDN function, an APN controller, or an APN function.
  • Example X21 includes the one or more computer-readable media of example XI 9 or some other example herein, wherein the media further stores instructions to provide a service exposure function that is to expose a DIS service or an APN service.
  • Example X22 includes the one or more computer-readable media of example XI 9 or some other example herein, wherein the media further stores instructions to provide a control plane service that includes a service to: form or configure a data processing pipeline; form a function-dedicated computing function; form a function-dedicated network function; control resources and services; perform monitoring and collect telemetry data; control data sharing services; control data processing; control data analytics services; or control data security, privacy and integrity.
  • Example X23 includes the one or more computer-readable media of example XI 9 or some other example herein, wherein the media further stores instructions to provide a user plane data pipeline service.
  • Example X24 includes the one or more computer-readable media of any of examples X19-X23, wherein the media further stores instructions to provide a management plane service that includes a service to: deploy or onboard new services; provision new services; monitor performance; manage system failures; optimize system performance; or orchestrate system resources.
  • a management plane service that includes a service to: deploy or onboard new services; provision new services; monitor performance; manage system failures; optimize system performance; or orchestrate system resources.
  • Example Z01 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-X24, or any other method or process described herein.
  • Example Z02 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1- X24, or any other method or process described herein.
  • Example Z03 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1- X24, or any other method or process described herein.
  • Example Z04 may include a method, technique, or process as described in or related to any of examples 1- X24, or portions or parts thereof.
  • Example Z05 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1- X24, or portions thereof.
  • Example Z06 may include a signal as described in or related to any of examples 1- X24, or portions or parts thereof.
  • Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1- X24, or portions or parts thereof, or otherwise described in the present disclosure.
  • PDU protocol data unit
  • Example Z08 may include a signal encoded with data as described in or related to any of examples 1- X24, or portions or parts thereof, or otherwise described in the present disclosure.
  • Example Z09 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1- X24, or portions or parts thereof, or otherwise described in the present disclosure.
  • PDU protocol data unit
  • Example Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1- X24, or portions thereof.
  • Example Z11 may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1- X24, or portions thereof.
  • Example Z12 may include a signal in a wireless network as shown and described herein.
  • Example Z13 may include a method of communicating in a wireless network as shown and described herein.
  • Example Z14 may include a system for providing wireless communication as shown and described herein.
  • Example Z15 may include a device for providing wireless communication as shown and described herein.
  • Enhancement CDM Content COTS Commercial C-RNTI Cell Delivery Network Off-The-Shelf RNTI CDMA Code- CP Control Plane, CS Circuit Division Multiple Cyclic Prefix, Switched Access 40 Connection 75 CSAR Cloud Service
  • Gateway Function 45 Premise 80 Interference CHF Charging Equipment Measurement
  • CID Cell-ID (e.g., CQI Channel CSI-RSRP CSI positioning method) 50 Quality Indicator 85 reference signal CIM Common CPU CSI processing received power Information Model unit, Central CSI-RSRQ CSI CIR Carrier to Processing Unit reference signal Interference Ratio C/R received quality CK Cipher Key 55 Command/Resp 90 CSI-SINR CSI CM Connection onse field bit signal-to-noise and Management, CRAN Cloud Radio interference
  • Conditional Access ratio Mandatory Network, Cloud CSMA Carrier Sense CMAS Commercial 60 RAN 95 Multiple Access Mobile Alert Service CRB Common CSMA/CA CSMA CMD Command Resource Block with collision CMS Cloud CRC Cyclic avoidance Management System Redundancy Check CSS Common CO Conditional 65 CRI Channel-State 100 Search Space, CellOptional Information specific Search CoMP Coordinated Resource Space Multi-Point Indicator, CSI-RS CTF Charging CORESET Control Resource Trigger Function Resource Set 70 Indicator 105 CTS Clear-to-Send CW Codeword 35 DSL Domain ECSP Edge
  • GSM EDGE for Mobile Speed Downlink RAN
  • GGSN Gateway GPRS GTP GPRS 75 HSPA High Speed Support Node Tunneling Protocol Packet Access GLONASS GTP-UGPRS HSS Home
  • NodeB Number 95 IAB Integrated distributed unit HHO Hard Handover Access and GNSS Global HLR Home Location Backhaul Navigation Satellite Register ICIC Inter-Cell
  • LADN Local Control Group Area Data Network (protocol MCOT Maximum LBT Listen Before 50 layering context) 85 Channel Talk MAC Message Occupancy
  • Multimedia Gap Length MGRP Measurement 35 Access Communication Gap Repetition CHannel 70 s Period MPUSCH MTC MU-MIMO Multi MIB Master Physical Uplink Shared User MIMO Information Block, Channel MWUS MTC Management 40 MPLS MultiProtocol wake-up signal, MTC
  • CHannel Subscriber ISDN NE-DC NR-E- MPDCCH MTC Number UTRA Dual Physical Downlink 60 MT Mobile Connectivity Control Terminated, Mobile 95 NEF Network CHannel Termination Exposure Function MPDSCH MTC MTC Machine -Type NF Network Physical Downlink Communication Function Shared 65 s NFP Network CHannel mMTCmassive MTC, 100 Forwarding Path MPRACH MTC massive NFPD Network Physical Random Machine -Type Forwarding Path
  • N-PoP Network Point NR New Radio, Multiplexing of Presence Neighbour Relation OFDMA
  • Narrowband MIB 55 Function Frequency Division
  • PDCP Packet Data 65 PNFR Physical PSSCH Physical Convergence Protocol Network Function 100 Sidelink Shared
  • SI -MME SI for Division indication the control plane Multiple Access SFTD Space- Sl-U SI for the user 65 SCG Secondary Cell 100 Frequency Time plane Group Diversity, SFN
  • Subscriber 65 Information 100 Subscriber Identity
  • TPC Transmit Power UDP User Datagram Control 70 Protocol UTRA UMTS 35 VoIP Voice-over-IP,
  • VNFMVNF Manager For the purposes of the present document, the following terms and definitions are applicable to the examples and embodiments discussed herein.
  • circuitry refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality.
  • FPD field-programmable device
  • FPGA field-programmable gate array
  • PLD programmable logic device
  • CPLD complex PLD
  • HPLD high-capacity PLD
  • DSPs digital signal processors
  • the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality.
  • the term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.
  • processor circuitry refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data.
  • Processing circuitry may include one or more processing cores to execute instructions and one or more memory structures to store program and data information.
  • processor circuitry may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and/or any other device capable of executing or otherwise operating computerexecutable instructions, such as program code, software modules, and/or functional processes.
  • Processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, or the like.
  • the one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators.
  • CV computer vision
  • DL deep learning
  • application circuitry and/or “baseband circuitry” may be considered synonymous to, and may be referred to as, “processor circuitry.”
  • interface circuitry refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices.
  • interface circuitry may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component interfaces, network interface cards, and/or the like.
  • user equipment or “UE” as used herein refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network.
  • user equipment or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc.
  • user equipment or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface.
  • network element refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services.
  • network element may be considered synonymous to and/or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and/or the like.
  • computer system refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” and/or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” and/or “system” may refer to multiple computer devices and/or multiple computing systems that are communicatively coupled with one another and configured to share computing and/or networking resources.
  • appliance refers to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide a specific computing resource.
  • program code e.g., software or firmware
  • a “virtual appliance” is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or otherwise is dedicated to provide a specific computing resource.
  • resource refers to a physical or virtual device, a physical or virtual component within a computing environment, and/or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, workload units, and/or the like.
  • a “hardware resource” may refer to compute, storage, and/or network resources provided by physical hardware element(s).
  • a “virtualized resource” may refer to compute, storage, and/or network resources provided by virtualization infrastructure to an application, device, system, etc.
  • network resource or “communication resource” may refer to resources that are accessible by computer devic es/sys terns via a communications network.
  • system resources may refer to any kind of shared entities to provide services, and may include computing and/or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.
  • channel refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream.
  • channel may be synonymous with and/or equivalent to “communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and/or any other like term denoting a pathway or medium through which data is communicated.
  • link refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.
  • instantiate refers to the creation of an instance.
  • An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.
  • Coupled may mean two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements indirectly contact each other but still cooperate or interact with each other, and/or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other.
  • directly coupled may mean that two or more elements are in direct contact with one another.
  • communicatively coupled may mean that two or more elements may be in contact with one another by a means of communication including through a wire or other interconnect connection, through a wireless communication channel or link, and/or the like.
  • information element refers to a structural element containing one or more fields.
  • field refers to individual contents of an information element, or a data element that contains content.
  • SMTC refers to an SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.
  • SSB refers to an SS/PBCH block.
  • Primary Cell refers to the MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure.
  • Primary SCG Cell refers to the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure for DC operation.
  • Secondary Cell refers to a cell providing additional radio resources on top of a Special Cell for a UE configured with CA.
  • Secondary Cell Group refers to the subset of serving cells comprising the PSCell and zero or more secondary cells for a UE configured with DC.
  • Secondary Cell refers to the primary cell for a UE in RRC CONNECTED not configured with CA/DC there is only one serving cell comprising of the primary cell.
  • serving cell refers to the set of cells comprising the Special Cell(s) and all secondary cells for a UE in RRC CONNECTED configured with CA/.
  • Special Cell refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term “Special Cell” refers to the Pcell.

Landscapes

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

Abstract

Various embodiments herein provide techniques for data-centric communication and computing infrastructure (DIS) system architectures.　In one embodiment, An apparatus comprising: memory to store management plane function information, control plane function information, and user plane function information; and processing circuitry, coupled with the memory, to: provide a management plane function based on the management plane function 10 information, the management plane function including an infrastructure orchestrator for a data-centric communication and computing infrastructure (DIS) system; provide a control plane function based on the control plane function information, the control plane function including: a function dedicated compute (FDC) controller, a data plane controller, a function-dedicated network (FDN) controller, or an all-photonics network 15 (APN) controller; and provide a user plane function based on the user plane function information, the user plane function including: an FDC function, a data plane function, an FDN function, or an APN function.

Description

D ATA-CENTRIC COMMUNICATION AND COMPUTING SYSTEM ARCHITECTURE
CROSS REFERENCE TO RELATED APPLICATION
The present application claims priority to U.S. Provisional Patent Application No. 63/147,123, which was filed February 8, 2021.
FIELD
Various embodiments generally may relate to the field of wireless communications. For example, some embodiments may relate to data-centric communication and computing system architectures.
BACKGROUND
The Innovative Optical and Wireless Network (I0WN) Global Forum (GF) is working on a data centric communication and computing system architecture. Embodiments of the present disclosure are directed to data-centric computing and communication infrastructure and system (DIS) architectures.
BRIEF DESCRIPTION OF THE DRAWINGS
Embodiments will be readily understood by the following detailed description in conjunction with the accompanying drawings. To facilitate this description, like reference numerals designate like structural elements. Embodiments are illustrated by way of example and not by way of limitation in the figures of the accompanying drawings.
Figure 1 illustrates an example of a data-centric computing and communication infrastructure and system (DIS) architecture in accordance with various embodiments.
Figure 2 illustrates a service an functional view of a DIS architecture in accordance with various embodiments.
Figure 3 schematically illustrates a wireless network in accordance with various embodiments.
Figure 4 schematically illustrates components of a wireless network in accordance with various embodiments.
Figure 5 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Figures 6, 7, and 8 depict examples of procedures for practicing the various embodiments discussed herein.
DETAILED DESCRIPTION
The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of the present document, the phrases “A or B” and “A/B” mean (A), (B), or (A and B).
As introduced above, embodiments of the present disclosure are directed to a data-centric computing and communication infrastructure and system (DIS) architecture. An example of such an architecture in accordance with various embodiments is illustrated in Figure 1. Among other things, this architecture:
• Categorizes management plane, control plane, user plane, compute plane, data plane and communication plane. o Control plane is comprised of a function-dedicated computing (FDC) controller, data plane controller, function-dedicated network (FDN) controller, all-photonics network (APN) controller. o User plane is comprised of a function dedicated computing function, data plane function, functional dedicated network function, APN o Compute plane functions include: FDN controller, function-dedicated computing function. o Data plane functions include: data plane controller, data plane function. o Communication plane functions include: FDN controller, Function dedicated network function, APN controller and APN. o The infrastructure orchestrator is part of management plane functions
• Introduce interfaces among control plane functions. o The interfaces allow control plane functions to use each other’s services. For instance, the APN controller can use data plane controller services for data analytics on telemetry data. o In Figure 1, only interfaces between neighbor control functions are shown. But the system shall also support interfaces among all control functions.
• Introduce service exposure function. o Service expose function is used to expose services provided by the DIS, and allow external users to request and use services provided by the DIS.
The system architecture showed in Figure 1 focuses on high level functional blocks. To provide further details, a system diagram showing both service and functions is showed in Figure 2, where a Control and Management Service Mesh is used to provide service interfaces for control and management plane functions.
A service exposure function for cloud and a service exposure function for device and access network are introduced to expose DIS service and enable CSP, device and access networks to use DIS and APN services. Within the control plane, multiple control services are defined as shown in Figure 2. The control services can be held by one or multiple control functions, e.g., services provided by the FDC controller can reside in a single FDC controller function or be split into FDC formation control function, FDC resource control function, FDC service control function, FDC monitoring and telemetry control function. The interfaces among control functions are service based interfaces, e.g., each control function expose its services to the other control functions, control functions request for each other’s services.
In this example, control plane functions may include one or more functions to: form/configure the data processing pipeline, form function dedicated computing functions, form function dedicated network function, control resources and services, perform monitoring and collect telemetry data, control data sharing services, control data processing, control data analytics services, control data security, privacy and integrity.
In this example, the user plane provides a data pipeline service. User data processing and movement are confined within the user plane. The management plane functions may include one or more functions to: deploy/onboard new services, provision for new services, monitor performance, manage system failures, optimize system performance, orchestrate system resources
SYSTEMS AND IMPLEMENTATIONS
Figures 3-5 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.
Figure 3 illustrates a network 300 in accordance with various embodiments. The network 300 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems. However, the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3GPP systems, or the like.
The network 300 may include a UE 302, which may include any mobile or non-mobile computing device designed to communicate with a RAN 304 via an over-the-air connection. The UE 302 may be communicatively coupled with the RAN 304 by a Uu interface. The UE 302 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, loT device, etc.
In some embodiments, the network 300 may include a plurality of UEs coupled directly with one another via a sidelink interface. The UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.
In some embodiments, the UE 302 may additionally communicate with an AP 306 via an over-the-air connection. The AP 306 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 304. The connection between the UE 302 and the AP 306 may be consistent with any IEEE 802.11 protocol, wherein the AP 306 could be a wireless fidelity (Wi-Fi®) router. In some embodiments, the UE 302, RAN 304, and AP 306 may utilize cellular-WLAN aggregation (for example, LWA/LWIP). Cellular- WLAN aggregation may involve the UE 302 being configured by the RAN 304 to utilize both cellular radio resources and WLAN resources.
The RAN 304 may include one or more access nodes, for example, AN 308. AN 308 may terminate air-interface protocols for the UE 302 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and LI protocols. In this manner, the AN 308 may enable data/voice connectivity between CN 320 and the UE 302. In some embodiments, the AN 308 may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network, which may be referred to as a CRAN or virtual baseband unit pool. The AN 308 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 308 may be a macrocell base station or a low power base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.
In embodiments in which the RAN 304 includes a plurality of ANs, they may be coupled with one another via an X2 interface (if the RAN 304 is an LTE RAN) or an Xn interface (if the RAN 304 is a 5G RAN). The X2/Xn interfaces, which may be separated into control/user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc.
The ANs of the RAN 304 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 302 with an air interface for network access. The UE 302 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 304. For example, the UE 302 and RAN 304 may use carrier aggregation to allow the UE 302 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell. In dual connectivity scenarios, a first AN may be a master node that provides an MCG and a second AN may be secondary node that provides an SCG. The first/second ANs may be any combination of eNB, gNB, ng-eNB, etc.
The RAN 304 may provide the air interface over a licensed spectrum or an unlicensed spectrum. To operate in the unlicensed spectrum, the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCells/Scells. Prior to accessing the unlicensed spectrum, the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol.
In V2X scenarios the UE 302 or AN 308 may be or act as a RSU, which may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by: a UE may be referred to as a “UE-type RSU”; an eNB may be referred to as an “eNB -type RSU”; a gNB may be referred to as a “gNB-type RSU”; and the like. In one example, an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic. The RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN communications services. The components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.
In some embodiments, the RAN 304 may be an LTE RAN 310 with eNBs, for example, eNB 312. The LTE RAN 310 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation/ detection at the UE. The LTE air interface may operating on sub-6 GHz bands.
In some embodiments, the RAN 304 may be an NG-RAN 314 with gNBs, for example, gNB 316, or ng-eNBs, for example, ng-eNB 318. The gNB 316 may connect with 5G-enabled UEs using a 5G NR interface. The gNB 316 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 318 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface. The gNB 316 and the ng-eNB 318 may connect with each other over an Xn interface.
In some embodiments, the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 314 and a UPF 348 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN314 and an AMF 344 (e.g., N2 interface).
The NG-RAN 314 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data. The 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS similar to the LTE air interface. The 5G-NR air interface may not use a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking. The 5G-NR air interface may operating on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS/SSS/PBCH.
In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, BWP can be used for dynamic adaptation of the SCS. For example, the UE 302 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 302, the SCS of the transmission is changed as well. Another use case example of BWP is related to power saving. In particular, multiple BWPs can be configured for the UE 302 with different amount of frequency resources (for example, PRBs) to support data transmission under different traffic loading scenarios. A BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 302 and in some cases at the gNB 316. A BWP containing a larger number of PRBs can be used for scenarios with higher traffic load.
The RAN 304 is communicatively coupled to CN 320 that includes network elements to provide various functions to support data and telecommunications services to customers/subscribers (for example, users of UE 302). The components of the CN 320 may be implemented in one physical node or separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 320 onto physical compute/storage resources in servers, switches, etc. A logical instantiation of the CN 320 may be referred to as a network slice, and a logical instantiation of a portion of the CN 320 may be referred to as a network sub-slice.
In some embodiments, the CN 320 may be an LTE CN 322, which may also be referred to as an EPC. The LTE CN 322 may include MME 324, SGW 326, SGSN 328, HSS 330, PGW 332, and PCRF 334 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the LTE CN 322 may be briefly introduced as follows.
The MME 324 may implement mobility management functions to track a current location of the UE 302 to facilitate paging, bearer activation/ deactivation, handovers, gateway selection, authentication, etc.
The SGW 326 may terminate an SI interface toward the RAN and route data packets between the RAN and the LTE CN 322. The SGW 326 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3 GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
The SGSN 328 may track a location of the UE 302 and perform security functions and access control. In addition, the SGSN 328 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 324; MME selection for handovers; etc. The S3 reference point between the MME 324 and the SGSN 328 may enable user and bearer information exchange for inter-3 GPP access network mobility in idle/active states.
The HSS 330 may include a database for network users, including subscription-related information to support the network entities’ handling of communication sessions. The HSS 330 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc. An S6a reference point between the HSS 330 and the MME 324 may enable transfer of subscription and authentication data for authentic ating/authorizing user access to the LTE CN 320.
The PGW 332 may terminate an SGi interface toward a data network (DN) 336 that may include an application/content server 338. The PGW 332 may route data packets between the LTE CN 322 and the data network 336. The PGW 332 may be coupled with the SGW 326 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 332 may further include a node for policy enforcement and charging data collection (for example, PCEF). Additionally, the SGi reference point between the PGW 332 and the data network 3 36 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services. The PGW 332 may be coupled with a PCRF 334 via a Gx reference point.
The PCRF 334 is the policy and charging control element of the LTE CN 322. The PCRF 334 may be communicatively coupled to the app/content server 338 to determine appropriate QoS and charging parameters for service flows. The PCRF 332 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI.
In some embodiments, the CN 320 may be a 5GC 340. The 5GC 340 may include an AUSF 342, AMF 344, SMF 346, UPF 348, NSSF 350, NEF 352, NRF 354, PCF 356, UDM 358, and AF 360 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the 5GC 340 may be briefly introduced as follows.
The AUSF 342 may store data for authentication of UE 302 and handle authentication- related functionality. The AUSF 342 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 340 over reference points as shown, the AUSF 342 may exhibit an Nausf service-based interface.
The AMF 344 may allow other functions of the 5GC 340 to communicate with the UE 302 and the RAN 304 and to subscribe to notifications about mobility events with respect to the UE 302. The AMF 344 may be responsible for registration management (for example, for registering UE 302), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 344 may provide transport for SM messages between the UE 302 and the SMF 346, and act as a transparent proxy for routing SM messages. AMF 344 may also provide transport for SMS messages between UE 302 and an SMSF. AMF 344 may interact with the AUSF 342 and the UE 302 to perform various security anchor and context management functions. Furthermore, AMF 344 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 304 and the AMF 344; and the AMF 344 may be a termination point of NAS (Nl) signaling, and perform NAS ciphering and integrity protection. AMF 344 may also support NAS signaling with the UE 302 over an N3 IWF interface.
The SMF 346 may be responsible for SM (for example, session establishment, tunnel management between UPF 348 and AN 308); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 348 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 344 over N2 to AN 308; and determining SSC mode of a session. SM may refer to management of a PDU session, and a PDU session or “session” may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 302 and the data network 336.
The UPF 348 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 336, and a branching point to support multi-homed PDU session. The UPF 348 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform uplink traffic verification (e.g., SDF- to-QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 348 may include an uplink classifier to support routing traffic flows to a data network.
The NSSF 350 may select a set of network slice instances serving the UE 302. The NSSF 350 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed. The NSSF 350 may also determine the AMF set to be used to serve the UE 302, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 354. The selection of a set of network slice instances for the UE 302 may be triggered by the AMF 344 with which the UE 302 is registered by interacting with the NSSF 350, which may lead to a change of AMF. The NSSF 350 may interact with the AMF 344 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown). Additionally, the NSSF 350 may exhibit an Nnssf service-based interface.
The NEF 352 may securely expose services and capabilities provided by 3GPP network functions for third party, internal exposure/re-exposure, AFs (e.g., AF 360), edge computing or fog computing systems, etc. In such embodiments, the NEF 352 may authenticate, authorize, or throttle the AFs. NEF 352 may also translate information exchanged with the AF 360 and information exchanged with internal network functions. For example, the NEF 352 may translate between an AF-Service-Identifier and an internal 5GC information. NEF 352 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 352 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 352 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 352 may exhibit an Nnef service-based interface. The NRF 354 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 354 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 354 may exhibit the Nnrf service-based interface.
The PCF 356 may provide policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior. The PCF 356 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 358. In addition to communicating with functions over reference points as shown, the PCF 356 exhibit an Npcf service-based interface.
The UDM 358 may handle subscription-related information to support the network entities’ handling of communication sessions, and may store subscription data of UE 302. For example, subscription data may be communicated via an N8 reference point between the UDM 358 and the AMF 344. The UDM 358 may include two parts, an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 358 and the PCF 356, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 302) for the NEF 352. The Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 358, PCF 356, and NEF 352 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR. The UDM may include a UDM- FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management. In addition to communicating with other NFs over reference points as shown, the UDM 358 may exhibit the Nudm service-based interface.
The AF 360 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control.
In some embodiments, the 5GC 340 may enable edge computing by selecting operator/3rd party services to be geographically close to a point that the UE 302 is attached to the network. This may reduce latency and load on the network. To provide edge-computing implementations, the 5GC 340 may select a UPF 348 close to the UE 302 and execute traffic steering from the UPF 348 to data network 336 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 360. In this way, the AF 360 may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 360 is considered to be a trusted entity, the network operator may permit AF 360 to interact directly with relevant NFs. Additionally, the AF 360 may exhibit an Naf service-based interface.
The data network 336 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application/content server 338.
Figure 4 schematically illustrates a wireless network 400 in accordance with various embodiments. The wireless network 400 may include a UE 402 in wireless communication with an AN 404. The UE 402 and AN 404 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein.
The UE 402 may be communicatively coupled with the AN 404 via connection 406. The connection 406 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6GHz frequencies.
The UE 402 may include a host platform 408 coupled with a modem platform 410. The host platform 408 may include application processing circuitry 412, which may be coupled with protocol processing circuitry 414 of the modem platform 410. The application processing circuitry 412 may run various applications for the UE 402 that source/sink application data. The application processing circuitry 412 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations
The protocol processing circuitry 414 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 406. The layer operations implemented by the protocol processing circuitry 414 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.
The modem platform 410 may further include digital baseband circuitry 416 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 414 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symboFbit metric determination, multi-antenna port precoding/decoding, which may include one or more of space-time, space-frequency or spatial coding, reference signal generation/ detection, preamble sequence generation and/or decoding, synchronization sequence generation/ detection, control channel signal blind decoding, and other related functions.
The modem platform 410 may further include transmit circuitry 418, receive circuitry 420, RF circuitry 422, and RF front end (RFFE) 424, which may include or connect to one or more antenna panels 426. Briefly, the transmit circuitry 418 may include a digital-to-analog converter, mixer, intermediate frequency (IF) components, etc.; the receive circuitry 420 may include an analog-to-digital converter, mixer, IF components, etc.; the RF circuitry 422 may include a low-noise amplifier, a power amplifier, power tracking components, etc.; RFFE 424 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc. The selection and arrangement of the components of the transmit circuitry 418, receive circuitry 420, RF circuitry 422, RFFE 424, and antenna panels 426 (referred generically as “transmit/receive components”) may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mmWave or sub-6 gHz frequencies, etc. In some embodiments, the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc.
In some embodiments, the protocol processing circuitry 414 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components.
A UE reception may be established by and via the antenna panels 426, RFFE 424, RF circuitry 422, receive circuitry 420, digital baseband circuitry 416, and protocol processing circuitry 414. In some embodiments, the antenna panels 426 may receive a transmission from the AN 404 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 426.
A UE transmission may be established by and via the protocol processing circuitry 414, digital baseband circuitry 416, transmit circuitry 418, RF circuitry 422, RFFE 424, and antenna panels 426. In some embodiments, the transmit components of the UE 404 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 426.
Similar to the UE 402, the AN 404 may include a host platform 428 coupled with a modem platform 430. The host platform 428 may include application processing circuitry 432 coupled with protocol processing circuitry 434 of the modem platform 430. The modem platform may further include digital baseband circuitry 436, transmit circuitry 438, receive circuitry 440, RF circuitry 442, RFFE circuitry 444, and antenna panels 446. The components of the AN 404 may be similar to and substantially interchangeable with like-named components of the UE 402. In addition to performing data transmission/reception as described above, the components of the AN 408 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.
Figure 5 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, Figure 5 shows a diagrammatic representation of hardware resources 500 including one or more processors (or processor cores) 510, one or more memory/storage devices 520, and one or more communication resources 530, each of which may be communicatively coupled via a bus 540 or other interface circuitry. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 502 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 500.
The processors 510 may include, for example, a processor 512 and a processor 514. The processors 510 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.
The memory/storage devices 520 may include main memory, disk storage, or any suitable combination thereof. The memory/storage devices 520 may include, but are not limited to, any type of volatile, non-volatile, or semi-volatile memory such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.
The communication resources 530 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 504 or one or more databases 506 or other network elements via a network 508. For example, the communication resources 530 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.
Instructions 550 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 510 to perform any one or more of the methodologies discussed herein. The instructions 550 may reside, completely or partially, within at least one of the processors 510 (e.g., within the processor’s cache memory), the memory/storage devices 520, or any suitable combination thereof. Furthermore, any portion of the instructions 550 may be transferred to the hardware resources 500 from any combination of the peripheral devices 504 or the databases 506. Accordingly, the memory of processors 510, the memory/storage devices 520, the peripheral devices 504, and the databases 506 are examples of computer-readable and machine -readable media.
EXAMPLE PROCEDURES
In some embodiments, the electronic device(s), network(s), system(s), chip(s) or component(s), or portions or implementations thereof, of Figures 3-5, or some other figure herein, may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof. One such process is depicted in Figure 6. For example, process 600 may include, at 605, providing a management plane function based on management plane function information, the management plane function including an infrastructure orchestrator for a data- centric communication and computing infrastructure (DIS) system. The process further includes, at 610, providing a control plane function based on control plane function information, the control plane function including: a function dedicated compute (FDC) controller, a data plane controller, a function-dedicated network (FDN) controller, or an all-photonics network (APN) controller. The process further includes, at 615, providing a user plane function based on the user plane function information, the user plane function including: an FDC function, a data plane function, an FDN function, or an APN function.
Another such process is illustrated in Figure 7. In this example, the process 700 includes, at 705, Providing a management plane function that includes an infrastructure orchestrator for a data-centric communication and computing infrastructure (DIS) system. The process further includes, at 710, providing a control plane function that includes: a function dedicated compute (FDC) controller, a data plane controller, a function-dedicated network (FDN) controller, or an all-photonics network (APN) controller. The process further includes, at 715, providing a user plane function that includes: an FDC function, a data plane function, an FDN function, or an APN function. The process further includes, at 720, providing a compute plane function that includes an FDN controller or FDC function. The process further includes, at 725, providing a data plane function and a data plane controller.
Another such process is illustrated in Figure 8. In this example, the process 800 includes, at 805, providing a management plane function that includes an infrastructure orchestrator for the DIS system. The process further includes, at 810, providing a plurality of control plane functions in communication with the infrastructure orchestrator via a control and management services mesh and that include: a function dedicated compute (FDC) controller, a data plane controller, a function-dedicated network (FDN) controller, or an all-photonics network (APN) controller. The process further includes, at 815, providing a plurality of user plane functions in communication with the plurality of control plane functions and that include: an FDC function, a data plane function, an FDN function, or an APN function. The process further includes, at 820, providing a compute plane function that includes an FDN controller or FDC function. The process further includes, at 825, providing a data plane function and a data plane controller.
For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.
EXAMPLES
Example 1 may include a data-centric computing and communication infrastructure and system (DIS) architecture (e.g., as shown in Figure 1 and/or Figure 2) comprising one or more of the following components: o Management plane, control plane, user plane, compute plane, data plane and communication plane o Control plane is comprised by FDC (function dedicated compute) controller, Data plane controller, FDN (function dedicated network) controller, APN (allphotonics network) controller o User plane is comprised by Function dedicated computing function, data plane function, functional dedicated network function, APN o Compute plane functions include: FDN controller, Function dedicated computing function o Data plane functions include: Data plane controller, Data plane function o Communication plane functions include: FDN controller, Function dedicated network function, APN controller and APN o The infrastructure orchestrator is part of management plane functions. Example 2 may include Control and Management Service Mesh is used to provide service interfaces for control and management plane functions. In some embodiments of Example 2: o Each control and management function expose its services to the other control and management functions; and/or o Control and management functions request for each other’s services.
Example 3 may include a service exposure function for cloud and a service exposure function for device and access network. In some embodiments of Example 3: o The service expose function is used to expose DIS service and enable CSP, device and access networks to use DIS and APN services.
Example 4 may include control Plane services include: form/configure the data processing pipeline, form function dedicated computing functions, form function dedicated network function, control resources and services, perform monitoring and collect telemetry data, control data sharing services, control data processing, control data analytics services, control data security, privacy and integrity.
Example 5 may include user plane provide data pipeline service. User data processing and movement are confined within user plane.
Example 6 may include management Plane services include: deploy/onboard new services, provision for new services, monitor performance, manage system failures, optimize system performance, orchestrate system resources.
Example 7 may include the control services are held by one or multiple control functions, for example, including one or more of the following features: o Services provided by the FDC controller can reside in a single FDC controller function or be split into FDC formation control function, FDC resource control function, FDC service control function, FDC monitoring and telemetry control function or a combination of them. o Services provided by the Data plane controller can reside in a single Data plane controller function or be split into Data sharing control, data processing control, data analytics control, data security control, or a combination of them. o Services provided by the FDN controller can reside in a single FDN controller function or be split into FDN formation control function, FDN resource control function, FDN service control function, FDN monitoring and telemetry control function or a combination of them. o Services provided by the APN controller can reside in a single APN controller function or be split into dynamic/static path control, bandwidth control, route control, monitoring/telemetry, or a combination of them. o The interfaces among control functions are service based interfaces, e.g., each control function expose its services to the other control functions, control functions request for each other’s services.
Example XI includes an apparatus comprising: memory to store management plane function information, control plane function information, and user plane function information; and processing circuitry, coupled with the memory, to: provide a management plane function based on the management plane function information, the management plane function including an infrastructure orchestrator for a data- centric communication and computing infrastructure (DIS) system; provide a control plane function based on the control plane function information, the control plane function including: a function dedicated compute (FDC) controller, a data plane controller, a function-dedicated network (FDN) controller, or an all-photonics network (APN) controller; and provide a user plane function based on the user plane function information, the user plane function including: an FDC function, a data plane function, an FDN function, or an APN function.
Example X2 includes the apparatus of example XI or some other example herein, wherein the processing circuitry is further to provide a compute plane function that includes an FDN controller or FDC function.
Example X3 includes the apparatus of example XI or some other example herein, wherein the processing circuitry is further to provide a data plane function or a data plane controller.
Example X4 includes the apparatus of example XI or some other example herein, wherein the processing circuitry is further to provide a communication plane function that includes an FDN controller, an FDN function, an APN controller, or an APN function.
Example X5 includes the apparatus of example XI or some other example herein, wherein the processing circuitry is further to provide a control and management service mesh that provides service interfaces for the control plane function and management plane function.
Example X6 includes the apparatus of example XI or some other example herein, wherein the processing circuitry is further to provide a service exposure function that is to expose a DIS service or an APN service. Example X7 includes the apparatus of example XI or some other example herein, wherein the processing circuitry is further to provide a control plane service that includes a service to: form or configure a data processing pipeline; form a function-dedicated computing function; form a function-dedicated network function; control resources and services; perform monitoring and collect telemetry data; control data sharing services; control data processing; control data analytics services; or control data security, privacy and integrity.
Example X8 includes the apparatus of example XI or some other example herein, wherein the processing circuitry is further to provide a user plane data pipeline service.
Example X9 includes the apparatus of any of examples X1-X8, wherein the processing circuitry is further to provide a management plane service that includes a service to: deploy or onboard new services; provision new services; monitor performance; manage system failures; optimize system performance; or orchestrate system resources.
Example X10 includes the apparatus of any of examples XI -X9, wherein the processing circuitry is further to provide a control plane service that includes: a service provided by an FDC controller that resides in a single FDC controller function or that is split into: an FDC formation control function, an FDC resource control function, an FDC service control function, an FDC monitoring and telemetry control function, or combinations thereof; a service provided by a data plane controller that resides in a single data plane controller function or that is split into: a data sharing control function, a data processing control function, a data analytics control function, a data security control function, or combinations thereof; a service provided by an FDN controller that resides in a single FDN controller function or that is split into: an FDN formation control function, an FDN resource control function, an FDN service control function, an FDN monitoring and telemetry control function, or combinations thereof; or a service provided by an APN controller that resides in a single APN controller function or that is split into: a dynamic or static path control function, a bandwidth control function, a route control function, a monitoring or telemetry function, or combinations thereof.
Example XI 1 includes one or more computer-readable media storing instructions that, when executed by one or more processors, cause a computing device to: provide a management plane function that includes an infrastructure orchestrator for a data-centric communication and computing infrastructure (DIS) system; provide a control plane function that includes: a function dedicated compute (FDC) controller, a data plane controller, a function-dedicated network (FDN) controller, or an allphotonics network (APN) controller; provide a user plane function that includes: an FDC function, a data plane function, an FDN function, or an APN function; provide a compute plane function that includes an FDN controller or FDC function; and provide a data plane function and a data plane controller.
Example X12 includes the one or more computer-readable media of example XI 1 or some other example herein, wherein the media further stores instructions to provide a communication plane function that includes an FDN controller, an FDN function, an APN controller, or an APN function.
Example XI 3 includes the one or more computer-readable media of example XI 1 or some other example herein, wherein the media further stores instructions to provide a control and management service mesh that provides service interfaces for the control plane function and management plane function.
Example X14 includes the one or more computer-readable media of example XI 1 or some other example herein, wherein the media further stores instructions to provide a service exposure function that is to expose a DIS service or an APN service.
Example X15 includes the one or more computer-readable media of example XI 1 or some other example herein, wherein the media further stores instructions to provide a control plane service that includes a service to: form or configure a data processing pipeline; form a function-dedicated computing function; form a function-dedicated network function; control resources and services; perform monitoring and collect telemetry data; control data sharing services; control data processing; control data analytics services; or control data security, privacy and integrity.
Example X16 includes the one or more computer-readable media of example XI 1 or some other example herein, wherein the media further stores instructions to provide a user plane data pipeline service.
Example X17 includes the one or more computer-readable media of any of examples XI 1 -XI 6, wherein the media further stores instructions to provide a management plane service that includes a service to: deploy or onboard new services; provision new services; monitor performance; manage system failures; optimize system performance; or orchestrate system resources.
Example XI 8 includes the one or more computer-readable media of any of examples XI 1 -XI 7, wherein the media further stores instructions to provide a control plane service that includes: a service provided by an FDC controller that resides in a single FDC controller function or that is split into: an FDC formation control function, an FDC resource control function, an FDC service control function, an FDC monitoring and telemetry control function, or combinations thereof; a service provided by a data plane controller that resides in a single data plane controller function or that is split into: a data sharing control function, a data processing control function, a data analytics control function, a data security control function, or combinations thereof; a service provided by an FDN controller that resides in a single FDN controller function or that is split into: an FDN formation control function, an FDN resource control function, an FDN service control function, an FDN monitoring and telemetry control function, or combinations thereof; or a service provided by an APN controller that resides in a single APN controller function or that is split into: a dynamic or static path control function, a bandwidth control function, a route control function, a monitoring or telemetry function, or combinations thereof.
Example XI 9 includes one or more computer-readable media storing instructions that, when executed by one or more processors, cause a data-centric communication and computing infrastructure (DIS) system to: provide a management plane function that includes an infrastructure orchestrator for the DIS system; provide a plurality of control plane functions in communication with the infrastructure orchestrator via a control and management services mesh and that include: a function dedicated compute (FDC) controller, a data plane controller, a function-dedicated network (FDN) controller, or an all-photonics network (APN) controller; provide a plurality of user plane functions in communication with the plurality of control plane functions and that include: an FDC function, a data plane function, an FDN function, or an APN function; provide a compute plane function that includes an FDN controller or FDC function; and provide a data plane function and a data plane controller.
Example X20 includes the one or more computer-readable media of example XI 9 or some other example herein, wherein the media further stores instructions to provide a communication plane function that includes an FDN controller, an FDN function, an APN controller, or an APN function.
Example X21 includes the one or more computer-readable media of example XI 9 or some other example herein, wherein the media further stores instructions to provide a service exposure function that is to expose a DIS service or an APN service. Example X22 includes the one or more computer-readable media of example XI 9 or some other example herein, wherein the media further stores instructions to provide a control plane service that includes a service to: form or configure a data processing pipeline; form a function-dedicated computing function; form a function-dedicated network function; control resources and services; perform monitoring and collect telemetry data; control data sharing services; control data processing; control data analytics services; or control data security, privacy and integrity.
Example X23 includes the one or more computer-readable media of example XI 9 or some other example herein, wherein the media further stores instructions to provide a user plane data pipeline service.
Example X24 includes the one or more computer-readable media of any of examples X19-X23, wherein the media further stores instructions to provide a management plane service that includes a service to: deploy or onboard new services; provision new services; monitor performance; manage system failures; optimize system performance; or orchestrate system resources.
Example Z01 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-X24, or any other method or process described herein.
Example Z02 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1- X24, or any other method or process described herein.
Example Z03 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1- X24, or any other method or process described herein.
Example Z04 may include a method, technique, or process as described in or related to any of examples 1- X24, or portions or parts thereof.
Example Z05 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1- X24, or portions thereof.
Example Z06 may include a signal as described in or related to any of examples 1- X24, or portions or parts thereof. Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1- X24, or portions or parts thereof, or otherwise described in the present disclosure.
Example Z08 may include a signal encoded with data as described in or related to any of examples 1- X24, or portions or parts thereof, or otherwise described in the present disclosure.
Example Z09 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1- X24, or portions or parts thereof, or otherwise described in the present disclosure.
Example Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1- X24, or portions thereof.
Example Z11 may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1- X24, or portions thereof.
Example Z12 may include a signal in a wireless network as shown and described herein.
Example Z13 may include a method of communicating in a wireless network as shown and described herein.
Example Z14 may include a system for providing wireless communication as shown and described herein.
Example Z15 may include a device for providing wireless communication as shown and described herein.
Any of the above-described examples may be combined with any other example (or combination of examples), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.
Abbreviations
Unless used differently herein, terms, definitions, and abbreviations may be consistent with terms, definitions, and abbreviations defined in 3GPP TR 21.905 vl6.0.0 (2019-06). For the purposes of the present document, the following abbreviations may apply to the examples and embodiments discussed herein. 3GPP Third AP Application BRAS Broadband
Generation 35 Protocol, Antenna Remote Access
Partnership Port, Access Point 70 Server
Project API Application BSS Business
4G Fourth Programming Interface Support System
Generation APN Access Point BS Base Station
5G Fifth 40 Name BSR Buffer Status
Generation ARP Allocation and 75 Report
5GC 5G Core Retention Priority BW Bandwidth network ARQ Automatic BWP Bandwidth Part
AC Repeat Request C-RNTI Cell
Application 45 AS Access Stratum Radio Network Client ASP 80 Temporary
ACK Application Service Identity
Acknowledgem Provider CA Carrier ent Aggregation,
ACID 50 ASN.l Abstract Syntax Certification
Application Notation One 85 Authority Client Identification AUSF Authentication CAPEX CAPital AF Application Server Function Expenditure Function AWGN Additive CBRA Contention
AM Acknowledged 55 White Gaussian Based Random
Mode Noise 90 Access
AMB R Aggregate BAP Backhaul CC Component
Maximum Bit Rate Adaptation Protocol Carrier, Country
AMF Access and BCH Broadcast Code, Cryptographic
Mobility 60 Channel Checksum
Management BER Bit Error Ratio 95 CCA Clear Channel
Function BFD Beam Assessment
AN Access Failure Detection CCE Control
Network BLER Block Error Channel Element
ANR Automatic 65 Rate CCCH Common
Neighbour Relation BPSK Binary Phase 100 Control Channel Shift Keying CE Coverage
Enhancement CDM Content COTS Commercial C-RNTI Cell Delivery Network Off-The-Shelf RNTI CDMA Code- CP Control Plane, CS Circuit Division Multiple Cyclic Prefix, Switched Access 40 Connection 75 CSAR Cloud Service
CFRA Contention Free Point Archive Random Access CPD Connection CSI Channel-State CG Cell Group Point Descriptor Information CGF Charging CPE Customer CSI-IM CSI
Gateway Function 45 Premise 80 Interference CHF Charging Equipment Measurement
Function CPICHCommon Pilot CSI-RS CSI
CI Cell Identity Channel Reference Signal
CID Cell-ID (e.g., CQI Channel CSI-RSRP CSI positioning method) 50 Quality Indicator 85 reference signal CIM Common CPU CSI processing received power Information Model unit, Central CSI-RSRQ CSI CIR Carrier to Processing Unit reference signal Interference Ratio C/R received quality CK Cipher Key 55 Command/Resp 90 CSI-SINR CSI CM Connection onse field bit signal-to-noise and Management, CRAN Cloud Radio interference
Conditional Access ratio Mandatory Network, Cloud CSMA Carrier Sense CMAS Commercial 60 RAN 95 Multiple Access Mobile Alert Service CRB Common CSMA/CA CSMA CMD Command Resource Block with collision CMS Cloud CRC Cyclic avoidance Management System Redundancy Check CSS Common CO Conditional 65 CRI Channel-State 100 Search Space, CellOptional Information specific Search CoMP Coordinated Resource Space Multi-Point Indicator, CSI-RS CTF Charging CORESET Control Resource Trigger Function Resource Set 70 Indicator 105 CTS Clear-to-Send CW Codeword 35 DSL Domain ECSP Edge
CWS Contention Specific Language. Computing Service
Window Size Digital 70 Provider
D2D Device-to- Subscriber Line EDN Edge
Device DSLAM DSL Data Network
DC Dual 40 Access Multiplexer EEC Edge
Connectivity, Direct DwPTS Enabler Client Current Downlink Pilot 75 EECID Edge
DCI Downlink Time Slot Enabler Client
Control E-LAN Ethernet Identification
Information 45 Local Area Network EES Edge
DF Deployment E2E End-to-End Enabler Server
Flavour ECCA extended clear 80 EESID Edge
DL Downlink channel Enabler Server
DMTF Distributed assessment, Identification
Management Task 50 extended CCA EHE Edge Force ECCE Enhanced Hosting Environment
DPDK Data Plane Control Channel 85 EGMF Exposure
Development Kit Element, Governance DM-RS, DMRS Enhanced CCE Management
Demodulation 55 ED Energy Function
Reference Signal Detection EGPRS DN Data network EDGE Enhanced 90 Enhanced DNN Data Network Datarates for GSM GPRS Name Evolution EIR Equipment
DNAI Data Network 60 (GSM Evolution) Identity Register Access Identifier EAS Edge eLAA enhanced
Application Server 95 Licensed Assisted
DRB Data Radio EASID Edge Access,
Bearer Application Server enhanced LAA
DRS Discovery 65 Identification EM Element
Reference Signal ECS Edge Manager
DRX Discontinuous Configuration Server 100 eMBB Enhanced
Reception Mobile
Broadband EMS Element 35 E-UTRA Evolved FCCH Frequency
Management System UTRA 70 Correction CHannel eNB evolved NodeB, E-UTRAN Evolved FDD Frequency E-UTRAN Node B UTRAN Division Duplex
EN-DC E- EV2X Enhanced V2X FDM Frequency
UTRA-NR Dual 40 F1AP Fl Application Division
Connectivity Protocol 75 Multiplex
EPC Evolved Packet Fl-C Fl Control FDMA Frequency
Core plane interface Division Multiple
EPDCCH Fl-U Fl User plane Access enhanced 45 interface FE Front End
PDCCH, enhanced FACCH Fast 80 FEC Forward Error
Physical Associated Control Correction
Downlink Control CHannel FFS For Further
Cannel FACCH/F Fast Study
EPRE Energy per 50 Associated Control FFT Fast Fourier resource element Channel/Full 85 Transformation
EPS Evolved Packet rate feLAA further
System FACCH/H Fast enhanced Licensed
EREG enhanced REG, Associated Control Assisted enhanced resource 55 Channel/Half Access, further element groups rate 90 enhanced LAA
ETSI European FACH Forward Access FN Frame Number
Telecommunica Channel FPGA Field- tions Standards FAUSCH Fast Programmable Gate
Institute 60 Uplink Signalling Array
ETWS Earthquake and Channel 95 FR Frequency
Tsunami Warning FB Functional Range
System Block FQDN Fully eUICC embedded FBI Feedback Qualified Domain
UICC, embedded 65 Information Name
Universal FCC Federal 100 G-RNTI GERAN
Integrated Circuit Communications Radio Network Card Commission Temporary
Identity GERAN GSM Global System 70 HSDPA High
GSM EDGE for Mobile Speed Downlink RAN, GSM EDGE Communication Packet Access
Radio Access s, Groupe Special HSN Hopping
Network 40 Mobile Sequence Number
GGSN Gateway GPRS GTP GPRS 75 HSPA High Speed Support Node Tunneling Protocol Packet Access GLONASS GTP-UGPRS HSS Home
GLObal'naya Tunnelling Protocol Subscriber Server
NAvigatsionnay 45 for User Plane HSUPA High a Sputnikovaya GTS Go To Sleep 80 Speed Uplink Packet Sistema (Engl.: Signal (related Access Global Navigation to WUS) HTTP Hyper Text
Satellite GUMMEI Globally Transfer Protocol
System) 50 Unique MME HTTPS Hyper gNB Next Identifier 85 Text Transfer Protocol Generation NodeB GUTI Globally Secure (https is gNB-CU gNB- Unique Temporary http/ 1.1 over centralized unit, Next UE Identity SSL, i.e. port 443)
Generation 55 HARQ Hybrid ARQ, I-Block
NodeB Hybrid 90 Information centralized unit Automatic Block gNB-DU gNB- Repeat Request ICCID Integrated distributed unit, Next HANDO Handover Circuit Card
Generation 60 HFN HyperFrame Identification
NodeB Number 95 IAB Integrated distributed unit HHO Hard Handover Access and GNSS Global HLR Home Location Backhaul Navigation Satellite Register ICIC Inter-Cell
System 65 HN Home Network Interference
GPRS General Packet HO Handover 100 Coordination Radio Service HPLMN Home ID Identity,
GPSI Generic Public Land Mobile identifier
Public Subscription Network
Identifier IDFT Inverse Discrete 35 IMPI IP Multimedia ISO International Fourier Private Identity 70 Organisation for
Transform IMPU IP Multimedia Standardisation IE Information PUblic identity ISP Internet Service element IMS IP Multimedia Provider IBE In-Band 40 Subsystem IWF Interworking- Emission IMSI International 75 Function IEEE Institute of Mobile I-WLAN Electrical and Subscriber Interworking
Electronics Identity WLAN Engineers 45 loT Internet of Constraint IEI Information Things 80 length of the Element IP Internet convolutional
Identifier Protocol code, USIM IEIDL Information Ipsec IP Security, Individual key Element 50 Internet Protocol kB Kilobyte (1000
Identifier Data Security 85 bytes) Length IP-CAN IP- kbps kilo-bits per IETF Internet Connectivity Access second Engineering Task Network Kc Ciphering key Force 55 IP-M IP Multicast Ki Individual
IF Infrastructure IPv4 Internet 90 subscriber
IM Interference Protocol Version 4 authentication
Measurement, IPv6 Internet key
Intermodulation Protocol Version 6 KPI Key , IP Multimedia 60 IR Infrared Performance Indicator IMC IMS IS In Sync 95 KQI Key Quality Credentials IRP Integration Indicator IMEI International Reference Point KSI Key Set Mobile ISDN Integrated Identifier
Equipment 65 Services Digital ksps kilo-symbols Identity Network 100 per second IMGI International ISIM IM Services KVM Kernel Virtual mobile group identity Identity Module Machine LI Layer 1 35 LTE Long Term 70 Broadcast and (physical layer) Evolution Multicast Ll-RSRP Layer 1 LWA LTE-WLAN Service reference signal aggregation MBSFN received power LWIP LTE/WLAN Multimedia
L2 Layer 2 (data 40 Radio Level 75 Broadcast link layer) Integration with multicast L3 Layer 3 IPsec Tunnel service Single
(network layer) LTE Long Term Frequency LAA Licensed Evolution Network Assisted Access 45 M2M Machine -to- 80 MCC Mobile Country LAN Local Area Machine Code Network MAC Medium Access MCG Master Cell
LADN Local Control Group Area Data Network (protocol MCOT Maximum LBT Listen Before 50 layering context) 85 Channel Talk MAC Message Occupancy
LCM LifeCycle authentication code Time Management (security/encryption MCS Modulation and
LCR Low Chip Rate context) coding scheme LCS Location 55 MAC-A MAC 90 MDAF Management Services used for Data Analytics
LCID Logical authentication Function Channel ID and key MDAS Management
LI Layer Indicator agreement Data Analytics LLC Logical Link 60 (TSG T WG3 context) 95 Service Control, Low Layer MAC-IMAC used for MDT Minimization of Compatibility data integrity of Drive Tests LPLMN Local signalling messages ME Mobile PLMN (TSG T WG3 context) Equipment LPP LTE 65 MANO 100 MeNB master eNB Positioning Protocol Management MER Message Error LSB Least and Orchestration Ratio Significant Bit MBMS MGL Measurement
Multimedia Gap Length MGRP Measurement 35 Access Communication Gap Repetition CHannel 70 s Period MPUSCH MTC MU-MIMO Multi MIB Master Physical Uplink Shared User MIMO Information Block, Channel MWUS MTC Management 40 MPLS MultiProtocol wake-up signal, MTC
Information Base Label Switching 75 WUS MIMO Multiple Input MS Mobile Station NACK Negative Multiple Output MSB Most Acknowledgement MLC Mobile Significant Bit NAI Network Location Centre 45 MSC Mobile Access Identifier MM Mobility Switching Centre 80 NAS Non-Access Management MSI Minimum Stratum, Non- Access MME Mobility System Stratum layer Management Entity Information, NCT Network
MN Master Node 50 MCH Scheduling Connectivity MNO Mobile Information 85 Topology Network Operator MSID Mobile Station NC-JT NonMO Measurement Identifier coherent Joint Object, Mobile MSIN Mobile Station Transmission
Originated 55 Identification NEC Network MPBCH MTC Number 90 Capability
Physical Broadcast MSISDN Mobile Exposure
CHannel Subscriber ISDN NE-DC NR-E- MPDCCH MTC Number UTRA Dual Physical Downlink 60 MT Mobile Connectivity Control Terminated, Mobile 95 NEF Network CHannel Termination Exposure Function MPDSCH MTC MTC Machine -Type NF Network Physical Downlink Communication Function Shared 65 s NFP Network CHannel mMTCmassive MTC, 100 Forwarding Path MPRACH MTC massive NFPD Network Physical Random Machine -Type Forwarding Path
Descriptor NFV Network NPRACH 70 S-NNSAI Single-
Functions Narrowband NSSAI
Virtualization Physical Random NSSF Network Slice
NFVI NFV Access CHannel Selection Function
Infrastructure 40 NPUSCH NW Network
NFVO NFV Narrowband 75 NWUSNarrowband
Orchestrator Physical Uplink wake-up signal,
NG Next Shared CHannel Narrowband WUS
Generation, Next Gen NPSS Narrowband NZP Non-Zero
NGEN-DC NG- 45 Primary Power
RAN E-UTRA-NR Synchronization 80 O&M Operation and
Dual Connectivity Signal Maintenance
NM Network NSSS Narrowband ODU2 Optical channel
Manager Secondary Data Unit - type 2
NMS Network 50 Synchronization OFDM Orthogonal
Management System Signal 85 Frequency Division
N-PoP Network Point NR New Radio, Multiplexing of Presence Neighbour Relation OFDMA
NMIB, N-MIB NRF NF Repository Orthogonal
Narrowband MIB 55 Function Frequency Division
NPBCH NRS Narrowband 90 Multiple Access
Narrowband Reference Signal OOB Out-of-band
Physical NS Network OOS Out of
Broadcast Service Sync
CHannel 60 NSA Non-Standalone OPEX OPerating
NPDCCH operation mode 95 Expense
Narrowband NSD Network OSI Other System
Physical Service Descriptor Information
Downlink NSR Network OSS Operations
Control CHannel 65 Service Record Support System
NPDSCH NSSAINetwork Slice 100 OTA over-the-air
Narrowband Selection PAPR Peak-to-
Physical Assistance Average Power
Downlink Information Ratio
Shared CHannel PAR Peak to PDN Packet Data POC PTT over
Average Ratio 35 Network, Public Cellular
PBCH Physical Data Network 70 PP, PTP Point- to-
Broadcast Channel PDSCH Physical Point
PC Power Control, Downlink Shared PPP Point-to-Point
Personal Channel Protocol
Computer 40 PDU Protocol Data PRACH Physical
PCC Primary Unit 75 RACH
Component Carrier, PEI Permanent PRB Physical Primary CC Equipment resource block
PCell Primary Cell Identifiers PRG Physical
PCI Physical Cell 45 PFD Packet Flow resource block
ID, Physical Cell Description 80 group Identity P-GW PDN Gateway ProSe Proximity
PCEF Policy and PHICH Physical Services, Charging hybrid-ARQ indicator Proximity-
Enforcement 50 channel Based Service
Function PHY Physical layer 85 PRS Positioning
PCF Policy Control PLMN Public Land Reference Signal Function Mobile Network PRR Packet
PCRF Policy Control PIN Personal Reception Radio and Charging Rules 55 Identification Number PS Packet Services Function PM Performance 90 PSBCH Physical
PDCP Packet Data Measurement Sidelink Broadcast
Convergence PMI Precoding Channel
Protocol, Packet Matrix Indicator PSDCH Physical
Data Convergence 60 PNF Physical Sidelink Downlink Protocol layer Network Function 95 Channel
PDCCH Physical PNFD Physical PSCCH Physical
Downlink Control Network Function Sidelink Control
Channel Descriptor Channel
PDCP Packet Data 65 PNFR Physical PSSCH Physical Convergence Protocol Network Function 100 Sidelink Shared
Record Channel
PSCell Primary SCell PSS Primary RAB Radio Access Link Control
Synchronization 35 Bearer, Random 70 layer
Signal Access Burst REC AM RLC
PSTN Public Switched RACH Random Access Acknowledged Mode
Telephone Network Channel RLC UM RLC
PT-RS Phase-tracking RADIUS Remote Unacknowledged reference signal 40 Authentication Dial 75 Mode
PTT Push-to-Talk In User Service RLF Radio Link
PUCCH Physical RAN Radio Access Failure
Uplink Control Network RLM Radio Link
Channel RAND RANDom Monitoring
PUSCH Physical 45 number (used for 80 RLM-RS
Uplink Shared authentication) Reference
Channel RAR Random Access Signal for RLM
QAM Quadrature Response RM Registration
Amplitude RAT Radio Access Management
Modulation 50 Technology 85 RMC Reference
QCI QoS class of RAU Routing Area Measurement Channel identifier Update RMSI Remaining
QCL Quasi coRB Resource block, MSI, Remaining location Radio Bearer Minimum
QFI QoS Flow ID, 55 RBG Resource block 90 System
QoS Flow group Information
Identifier REG Resource RN Relay Node
QoS Quality of Element Group RNC Radio Network
Service Rel Release Controller
QPSK Quadrature 60 REQ REQuest 95 RNL Radio Network
(Quaternary) Phase RF Radio Layer
Shift Keying Frequency RNTI Radio Network
QZSS Quasi-Zenith RI Rank Indicator Temporary
Satellite System RIV Resource Identifier
RA-RNTI Random 65 indicator value 100 ROHC RObust Header
Access RNTI RE Radio Link Compression REC Radio Link RRC Radio Resource Control, Radio Control, Radio Resource Control 35 S-RNTI SRNC 70 SCS Subcarrier layer Radio Network Spacing
RRM Radio Resource Temporary SCTP Stream Control
Management Identity Transmission
RS Reference S-TMSI SAE Protocol
Signal 40 Temporary Mobile 75 SDAP Service Data
RSRP Reference Station Adaptation
Signal Received Identifier Protocol,
Power SA Standalone Service Data
RSRQ Reference operation mode Adaptation Signal Received 45 SAE System 80 Protocol layer
Quality Architecture SDL Supplementary
RSSI Received Signal Evolution Downlink Strength SAP Service Access SDNF Structured Data
Indicator Point Storage Network
RSU Road Side Unit 50 SAPD Service Access 85 Function RSTD Reference Point Descriptor SDP Session Signal Time SAPI Service Access Description Protocol difference Point Identifier SDSF Structured Data
RTP Real Time SCC Secondary Storage Function Protocol 55 Component Carrier, 90 SDU Service Data
RTS Ready-To-Send Secondary CC Unit RTT Round Trip SCell Secondary Cell SEAF Security Time SCEF Service Anchor Function
Rx Reception, Capability Exposure SeNB secondary eNB Receiving, Receiver 60 Function 95 SEPP Security Edge S1AP SI Application SC-FDMA Single Protection Proxy Protocol Carrier Frequency SFI Slot format
SI -MME SI for Division indication the control plane Multiple Access SFTD Space- Sl-U SI for the user 65 SCG Secondary Cell 100 Frequency Time plane Group Diversity, SFN
S-GW Serving SCM Security and frame timing Gateway Context difference
Management SFN System Frame SoC System on Chip Signal based
Number SON Self-Organizing Reference
SgNB Secondary gNB Network Signal Received
SGSN Serving GPRS SpCell Special Cell Power
Support Node 40 SP-CSI-RNTISemi- 75 SS-RSRQ
S-GW Serving Persistent CSI RNTI Synchronization
Gateway SPS Semi-Persistent Signal based
SI System Scheduling Reference
Information SQN Sequence Signal Received
SI-RNTI System 45 number 80 Quality
Information RNTI SR Scheduling SS-SINR
SIB System Request Synchronization
Information Block SRB Signalling Signal based Signal
SIM Subscriber Radio Bearer to Noise and
Identity Module 50 SRS Sounding 85 Interference Ratio
SIP Session Reference Signal SSS Secondary
Initiated Protocol SS Synchronization Synchronization
SiP System in Signal Signal
Package SSB Synchronization SSSG Search Space
SL Sidelink 55 Signal Block 90 Set Group
SLA Service Level SSID Service Set SSSIF Search Space
Agreement Identifier Set Indicator
SM Session SS/PBCH Block SST Slice/Service
Management SSBRI SS/PBCH Types
SMF Session 60 Block Resource 95 SU-MIMO Single
Management Function Indicator, User MIMO
SMS Short Message Synchronization SUL Supplementary
Service Signal Block Uplink
SMSF SMS Function Resource TA Timing
SMTC SSB-based 65 Indicator 100 Advance, Tracking
Measurement Timing SSC Session and Area
Configuration Service TAC Tracking Area
SN Secondary Continuity Code
Node, Sequence SS-RSRP TAG Timing
Number 70 Synchronization 105 Advance Group TAI TPMI Transmitted UDSF Unstructured
Tracking Area Precoding Matrix Data Storage Network
Identity Indicator Function
TAU Tracking Area TR Technical UICC Universal
Update 40 Report 75 Integrated Circuit
TB Transport Block TRP, TRxP Card
TBS Transport Block Transmission UL Uplink
Size Reception Point UM
TBD To Be Defined TRS Tracking Unacknowledge
TCI Transmission 45 Reference Signal 80 d Mode
Configuration TRx Transceiver UML Unified
Indicator TS Technical Modelling Language
TCP Transmission Specifications, UMTS Universal
Communication Technical Mobile
Protocol 50 Standard 85 Telecommunica
TDD Time Division TTI Transmission tions System
Duplex Time Interval UP User Plane
TDM Time Division Tx Transmission, UPF User Plane
Multiplexing Transmitting, Function
TDMATime Division 55 Transmitter 90 URI Uniform
Multiple Access U-RNTI UTRAN Resource Identifier
TE Terminal Radio Network URL Uniform
Equipment Temporary Resource Locator
TEID Tunnel End Identity URLLC Ultra¬
Point Identifier 60 UART Universal 95 Reliable and Low
TFT Traffic Flow Asynchronous Latency
Template Receiver and USB Universal Serial
TMSI Temporary Transmitter Bus
Mobile UCI Uplink Control USIM Universal
Subscriber 65 Information 100 Subscriber Identity
Identity UE User Equipment Module
TNL Transport UDM Unified Data USS UE-specific
Network Layer Management search space
TPC Transmit Power UDP User Datagram Control 70 Protocol UTRA UMTS 35 VoIP Voice-over-IP,
Terrestrial Radio Voice-over- Internet
Access Protocol
UTRAN VPLMN Visited
Universal Public Land Mobile
Terrestrial Radio 40 Network Access VPN Virtual Private
Network Network
UwPTS Uplink VRB Virtual Pilot Time Slot Resource Block
V2I Vehicle-to- 45 WiMAX
Infrastruction Worldwide
V2P Vehicle-to- Interoperability
Pedestrian for Microwave
V2V Vehicle-to- Access
Vehicle 50 WLANWireless Local
V2X Vehicle-to- Area Network everything WMAN Wireless
VIM Virtualized Metropolitan Area
Infrastructure Manager Network VL Virtual Link, 55 WPANWireless VLAN Virtual LAN, Personal Area Network Virtual Local Area X2-C X2-Control
Network plane
VM Virtual X2-U X2-User plane
Machine 60 XML extensible
VNF Virtualized Markup
Network Function Language
VNFFG VNF XRES Expected user
Forwarding Graph RESponse VNFFGD VNF 65 XOR exclusive OR
Forwarding Graph ZC Zadoff-Chu Descriptor ZP Zero Power
VNFMVNF Manager For the purposes of the present document, the following terms and definitions are applicable to the examples and embodiments discussed herein.
The term “circuitry” as used herein refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.
The term “processor circuitry” as used herein refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data. Processing circuitry may include one or more processing cores to execute instructions and one or more memory structures to store program and data information. The term “processor circuitry” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and/or any other device capable of executing or otherwise operating computerexecutable instructions, such as program code, software modules, and/or functional processes. Processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, or the like. The one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators. The terms “application circuitry” and/or “baseband circuitry” may be considered synonymous to, and may be referred to as, “processor circuitry.”
The term “interface circuitry” as used herein refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term “interface circuitry” may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component interfaces, network interface cards, and/or the like. The term “user equipment” or “UE” as used herein refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network. The term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term “user equipment” or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface.
The term “network element” as used herein refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services. The term “network element” may be considered synonymous to and/or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and/or the like.
The term “computer system” as used herein refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” and/or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” and/or “system” may refer to multiple computer devices and/or multiple computing systems that are communicatively coupled with one another and configured to share computing and/or networking resources.
The term “appliance,” “computer appliance,” or the like, as used herein refers to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide a specific computing resource. A “virtual appliance” is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or otherwise is dedicated to provide a specific computing resource.
The term “resource” as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, and/or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, workload units, and/or the like. A “hardware resource” may refer to compute, storage, and/or network resources provided by physical hardware element(s). A “virtualized resource” may refer to compute, storage, and/or network resources provided by virtualization infrastructure to an application, device, system, etc. The term “network resource” or “communication resource” may refer to resources that are accessible by computer devic es/sys terns via a communications network. The term “system resources” may refer to any kind of shared entities to provide services, and may include computing and/or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.
The term “channel” as used herein refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream. The term “channel” may be synonymous with and/or equivalent to “communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and/or any other like term denoting a pathway or medium through which data is communicated. Additionally, the term “link” as used herein refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.
The terms “instantiate,” “instantiation,” and the like as used herein refers to the creation of an instance. An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.
The terms “coupled,” “communicatively coupled,” along with derivatives thereof are used herein. The term “coupled” may mean two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements indirectly contact each other but still cooperate or interact with each other, and/or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other. The term “directly coupled” may mean that two or more elements are in direct contact with one another. The term “communicatively coupled” may mean that two or more elements may be in contact with one another by a means of communication including through a wire or other interconnect connection, through a wireless communication channel or link, and/or the like.
The term “information element” refers to a structural element containing one or more fields. The term “field” refers to individual contents of an information element, or a data element that contains content.
The term “SMTC” refers to an SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.
The term “SSB” refers to an SS/PBCH block. The term “a “Primary Cell” refers to the MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure.
The term “Primary SCG Cell” refers to the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure for DC operation.
The term “Secondary Cell” refers to a cell providing additional radio resources on top of a Special Cell for a UE configured with CA.
The term “Secondary Cell Group” refers to the subset of serving cells comprising the PSCell and zero or more secondary cells for a UE configured with DC. The term “Serving Cell” refers to the primary cell for a UE in RRC CONNECTED not configured with CA/DC there is only one serving cell comprising of the primary cell.
The term “serving cell” or “serving cells” refers to the set of cells comprising the Special Cell(s) and all secondary cells for a UE in RRC CONNECTED configured with CA/.
The term “Special Cell” refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term “Special Cell” refers to the Pcell.

Claims

CLAIMS What is claimed is:
1. An apparatus comprising: memory to store management plane function information, control plane function information, and user plane function information; and processing circuitry, coupled with the memory, to: provide a management plane function based on the management plane function information, the management plane function including an infrastructure orchestrator for a data- centric communication and computing infrastructure (DIS) system; provide a control plane function based on the control plane function information, the control plane function including: a function dedicated compute (FDC) controller, a data plane controller, a function-dedicated network (FDN) controller, or an all-photonics network (APN) controller; and provide a user plane function based on the user plane function information, the user plane function including: an FDC function, a data plane function, an FDN function, or an APN function.
2. The apparatus of claim 1, wherein the processing circuitry is further to provide a compute plane function that includes an FDN controller or FDC function.
3. The apparatus of claim 1, wherein the processing circuitry is further to provide a data plane function or a data plane controller.
4. The apparatus of claim 1, wherein the processing circuitry is further to provide a communication plane function that includes an FDN controller, an FDN function, an APN controller, or an APN function.
5. The apparatus of claim 1, wherein the processing circuitry is further to provide a control and management service mesh that provides service interfaces for the control plane function and management plane function.
6. The apparatus of claim 1, wherein the processing circuitry is further to provide a service exposure function that is to expose a DIS service or an APN service.
42
7. The apparatus of claim 1, wherein the processing circuitry is further to provide a control plane service that includes a service to: form or configure a data processing pipeline; form a function-dedicated computing function; form a function-dedicated network function; control resources and services; perform monitoring and collect telemetry data; control data sharing services; control data processing; control data analytics services; or control data security, privacy and integrity.
8. The apparatus of claim 1, wherein the processing circuitry is further to provide a user plane data pipeline service.
9. The apparatus of any of claims 1-8, wherein the processing circuitry is further to provide a management plane service that includes a service to: deploy or onboard new services; provision new services; monitor performance; manage system failures; optimize system performance; or orchestrate system resources.
10. The apparatus of any of claims 1-9, wherein the processing circuitry is further to provide a control plane service that includes: a service provided by an FDC controller that resides in a single FDC controller function or that is split into: an FDC formation control function, an FDC resource control function, an FDC service control function, an FDC monitoring and telemetry control function, or combinations thereof; a service provided by a data plane controller that resides in a single data plane controller function or that is split into: a data sharing control function, a data processing control function, a data analytics control function, a data security control function, or combinations thereof; a service provided by an FDN controller that resides in a single FDN controller function or that is split into: an FDN formation control function, an FDN resource control function, an FDN service control function, an FDN monitoring and telemetry control function, or combinations thereof; or a service provided by an APN controller that resides in a single APN controller function or that is split into: a dynamic or static path control function, a bandwidth control function, a route control function, a monitoring or telemetry function, or combinations thereof.
11. One or more computer-readable media storing instructions that, when executed by one or more processors, cause a computing device to:
43 provide a management plane function that includes an infrastructure orchestrator for a data-centric communication and computing infrastructure (DIS) system; provide a control plane function that includes: a function dedicated compute (FDC) controller, a data plane controller, a function-dedicated network (FDN) controller, or an allphotonics network (APN) controller; provide a user plane function that includes: an FDC function, a data plane function, an FDN function, or an APN function; provide a compute plane function that includes an FDN controller or FDC function; and provide a data plane function and a data plane controller.
12. The one or more computer-readable media of claim 11, wherein the media further stores instructions to provide a communication plane function that includes an FDN controller, an FDN function, an APN controller, or an APN function.
13. The one or more computer-readable media of claim 11, wherein the media further stores instructions to provide a control and management service mesh that provides service interfaces for the control plane function and management plane function.
14. The one or more computer-readable media of claim 11, wherein the media further stores instructions to provide a service exposure function that is to expose a DIS service or an APN service.
15. The one or more computer-readable media of claim 11, wherein the media further stores instructions to provide a control plane service that includes a service to: form or configure a data processing pipeline; form a function-dedicated computing function; form a function-dedicated network function; control resources and services; perform monitoring and collect telemetry data; control data sharing services; control data processing; control data analytics services; or control data security, privacy and integrity.
16. The one or more computer-readable media of claim 11, wherein the media further stores instructions to provide a user plane data pipeline service.
17. The one or more computer-readable media of any of claims 11-16, wherein the media further stores instructions to provide a management plane service that includes a service to:
44 deploy or onboard new services; provision new services; monitor performance; manage system failures; optimize system performance; or orchestrate system resources.
18. The one or more computer-readable media of any of claims 11-17, wherein the media further stores instructions to provide a control plane service that includes: a service provided by an FDC controller that resides in a single FDC controller function or that is split into: an FDC formation control function, an FDC resource control function, an FDC service control function, an FDC monitoring and telemetry control function, or combinations thereof; a service provided by a data plane controller that resides in a single data plane controller function or that is split into: a data sharing control function, a data processing control function, a data analytics control function, a data security control function, or combinations thereof; a service provided by an FDN controller that resides in a single FDN controller function or that is split into: an FDN formation control function, an FDN resource control function, an FDN service control function, an FDN monitoring and telemetry control function, or combinations thereof; or a service provided by an APN controller that resides in a single APN controller function or that is split into: a dynamic or static path control function, a bandwidth control function, a route control function, a monitoring or telemetry function, or combinations thereof.
19. One or more computer-readable media storing instructions that, when executed by one or more processors, cause a data-centric communication and computing infrastructure (DIS) system to: provide a management plane function that includes an infrastructure orchestrator for the DIS system; provide a plurality of control plane functions in communication with the infrastructure orchestrator via a control and management services mesh and that include: a function dedicated compute (FDC) controller, a data plane controller, a function-dedicated network (FDN) controller, or an all-photonics network (APN) controller; provide a plurality of user plane functions in communication with the plurality of control plane functions and that include: an FDC function, a data plane function, an FDN function, or an APN function; provide a compute plane function that includes an FDN controller or FDC function; and provide a data plane function and a data plane controller.
20. The one or more computer-readable media of claim 19, wherein the media further stores instructions to provide a communication plane function that includes an FDN controller, an FDN function, an APN controller, or an APN function.
21. The one or more computer-readable media of claim 19, wherein the media further stores instructions to provide a service exposure function that is to expose a DIS service or an APN service.
22. The one or more computer-readable media of claim 19, wherein the media further stores instructions to provide a control plane service that includes a service to: form or configure a data processing pipeline; form a function-dedicated computing function; form a function-dedicated network function; control resources and services; perform monitoring and collect telemetry data; control data sharing services; control data processing; control data analytics services; or control data security, privacy and integrity.
23. The one or more computer-readable media of claim 19, wherein the media further stores instructions to provide a user plane data pipeline service.
24. The one or more computer-readable media of any of claims 19-23, wherein the media further stores instructions to provide a management plane service that includes a service to: deploy or onboard new services; provision new services; monitor performance; manage system failures; optimize system performance; or orchestrate system resources.
PCT/US2022/015528 2021-02-08 2022-02-07 Data-centric communication and computing system architecture WO2022170213A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202163147123P 2021-02-08 2021-02-08
US63/147,123 2021-02-08

Publications (1)

Publication Number Publication Date
WO2022170213A1 true WO2022170213A1 (en) 2022-08-11

Family

ID=82742559

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/US2022/015530 WO2022170214A1 (en) 2021-02-08 2022-02-07 Congestion control for remote direct-memory access (rdma) in next-generation cellular networks
PCT/US2022/015528 WO2022170213A1 (en) 2021-02-08 2022-02-07 Data-centric communication and computing system architecture

Family Applications Before (1)

Application Number Title Priority Date Filing Date
PCT/US2022/015530 WO2022170214A1 (en) 2021-02-08 2022-02-07 Congestion control for remote direct-memory access (rdma) in next-generation cellular networks

Country Status (2)

Country Link
KR (1) KR20230153401A (en)
WO (2) WO2022170214A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024081642A1 (en) * 2022-10-12 2024-04-18 Intel Corporation Pipelining services in next-generation cellular networks

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012107361A2 (en) * 2011-02-10 2012-08-16 Xvd Technology Holdings Limited Real time distribution of layered communication using publish-subscribe data-centric middleware
WO2019214830A1 (en) * 2018-05-11 2019-11-14 Huawei Technologies Co., Ltd. Control plane entity and management plane entity for exchaning network slice instance data for analytics
US20200367089A1 (en) * 2013-10-08 2020-11-19 Alef Mobitech Inc. Systems and methods for providing mobility aspects to applications in the cloud

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115941616A (en) * 2017-12-15 2023-04-07 微软技术许可有限责任公司 Multi-path RDMA transport
US10713212B2 (en) * 2018-05-21 2020-07-14 Microsoft Technology Licensing Llc Mobile remote direct memory access
US10944660B2 (en) * 2019-02-08 2021-03-09 Intel Corporation Managing congestion in a network
US11188345B2 (en) * 2019-06-17 2021-11-30 International Business Machines Corporation High performance networking across docker containers

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012107361A2 (en) * 2011-02-10 2012-08-16 Xvd Technology Holdings Limited Real time distribution of layered communication using publish-subscribe data-centric middleware
US20200367089A1 (en) * 2013-10-08 2020-11-19 Alef Mobitech Inc. Systems and methods for providing mobility aspects to applications in the cloud
WO2019214830A1 (en) * 2018-05-11 2019-11-14 Huawei Technologies Co., Ltd. Control plane entity and management plane entity for exchaning network slice instance data for analytics

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
KATSUHIKO KAWAZOE: "What’s IOWN? - Change the World", NTT TECHNICAL REVIEW, vol. 18, no. 2, 1 February 2020 (2020-02-01), pages 17 - 26, XP055957537 *
SHIGERU IWASHINA , YOSUKE ARAGANE , KUNUHIKO MINAMIHATA , KATSUSHI SHINDO , MASAKATSU FUJIWARA: "Initiatives to Achieve the IOWN (Innovative Optical and Wireless Network) Concept", NTT TECHNICAL REVIEW, vol. 18, no. 2, 1 February 2020 (2020-02-01), pages 27 - 31, XP055957532 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024081642A1 (en) * 2022-10-12 2024-04-18 Intel Corporation Pipelining services in next-generation cellular networks

Also Published As

Publication number Publication date
WO2022170214A1 (en) 2022-08-11
KR20230153401A (en) 2023-11-06

Similar Documents

Publication Publication Date Title
US11910433B2 (en) Physical uplink shared channel (PUSCH) transmission scheduling for new radio (NR)
US20230037090A1 (en) Per-panel power control operation for uplink in 5g systems
US20240178973A1 (en) Switching between physical downlink control channel (pdcch) monitoring configurations of search space set groups (sssgs)
WO2022155488A1 (en) Enhanced frequency hopping mechanisms for reduced capability (redcap) devices
WO2022174070A1 (en) Performance measurements for edge computing applications
EP4255092A1 (en) Personal internet of things network element communication with 5g system and other personal internet of things network elements
US20230155781A1 (en) User equipment behavior and requirements for positioning measurement without gap
US20240155503A1 (en) Spatial relationship and power control configuration for uplink transmissions
US20240172272A1 (en) Msg3 physical uplink shared channel (pusch) repetition requests
WO2023069653A1 (en) User equipment (ue) switching between networks using measurement gaps
WO2023044025A1 (en) Using physical random access channel (prach) to identify multiple features and combinations of features
WO2022170213A1 (en) Data-centric communication and computing system architecture
EP4197253A1 (en) User equipment positioning measurement period for new radio systems
US20230163916A1 (en) Techniques for ue positioning measurement in rrc_inactive or rrc_idle
US20240188097A1 (en) Default beam operations for uplink transmissions
EP4236457A1 (en) Scheduling restriction for l1-rsrp measurement for cell with different pci
US20240147470A1 (en) Flexible uplink control information (uci) transmission with physical uplink shared channel (pusch)
EP4236439A1 (en) User equipment behavior when pre-configured measurement gap is changed
US20240155589A1 (en) Techniques for channel state information reference signal (csi-rs) transmission
US20240146454A1 (en) Enhanced mapping for control channel transmission based on polar code
US20240178939A1 (en) Techniques for multi-transmission-reception point (trp) based uplink channel transmission
WO2023158726A1 (en) Techniques for a positioning reference signal measurement with a measurement gap
WO2023069742A1 (en) Transmission configuration indicator (tci) chain enhancements for new radio systems
WO2023137211A1 (en) Techniques to avoid inter-symbol interference during tci state switching in high-speed train deployments
WO2023069743A1 (en) Bandwidth part switching delay derivation

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: 22750550

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: 22750550

Country of ref document: EP

Kind code of ref document: A1