WO2022170213A1 - Architecture de communication et de système informatique centrée sur les données - Google Patents

Architecture de communication et de système informatique centrée sur les données 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
English (en)
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/fr

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.

Abstract

La présente invention concerne, selon divers modes de réalisation, des techniques pour des architectures de système de communication et d'infrastructure informatique (DIS) centrées sur les données.　Dans un mode de réalisation, un appareil selon l'invention comporte: une mémoire servant à stocker des informations de fonction de plan de gestion, des informations de fonction de plan de commande, et des informations de fonction de plan d'utilisateur; et une circuiterie de traitement, couplée à la mémoire, servant à: mettre en place une fonction de plan de gestion d'après les informations de fonction de plan de gestion, la fonction de plan de gestion comprenant un orchestrateur d'infrastructure pour un système de communication et d'infrastructure informatique (DIS) centrées sur les données; mettre en place une fonction de plan de commande d'après les informations de fonction de plan de commande, la fonction de plan de commande comprenant: un contrôleur de calcul dédié à la fonction (FDC), un contrôleur de plan de données, un contrôleur de réseau dédié à la fonction (FDN), ou un contrôleur de réseau entièrement photonique (APN); et mettre en place une fonction de plan d'utilisateur d'après les informations de fonction de plan d'utilisateur, la fonction de plan d'utilisateur comprenant: une fonction FDC, une fonction de plan de données, une fonction FDN, ou une fonction APN.
PCT/US2022/015528 2021-02-08 2022-02-07 Architecture de communication et de système informatique centrée sur les données WO2022170213A1 (fr)

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 (fr) 2022-08-11

Family

ID=82742559

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/US2022/015528 WO2022170213A1 (fr) 2021-02-08 2022-02-07 Architecture de communication et de système informatique centrée sur les données
PCT/US2022/015530 WO2022170214A1 (fr) 2021-02-08 2022-02-07 Gestion de congestion pour accès direct à la mémoire à distance (rdma) dans des réseaux cellulaires de prochaine génération

Family Applications After (1)

Application Number Title Priority Date Filing Date
PCT/US2022/015530 WO2022170214A1 (fr) 2021-02-08 2022-02-07 Gestion de congestion pour accès direct à la mémoire à distance (rdma) dans des réseaux cellulaires de prochaine génération

Country Status (2)

Country Link
KR (1) KR20230153401A (fr)
WO (2) WO2022170213A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024081642A1 (fr) * 2022-10-12 2024-04-18 Intel Corporation Services de traitement en pipeline dans des réseaux cellulaires de prochaine génération

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012107361A2 (fr) * 2011-02-10 2012-08-16 Xvd Technology Holdings Limited Distribution en temps réel de communication en couches à l'aide d'un intergiciel centré sur les données de publication-abonnement
WO2019214830A1 (fr) * 2018-05-11 2019-11-14 Huawei Technologies Co., Ltd. Entité de plan de commande et entité de plan de gestion pour échanger des données d'instance de tranche de réseau à des fins d'analyse
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
CN109936510B (zh) * 2017-12-15 2022-11-15 微软技术许可有限责任公司 多路径rdma传输
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 (fr) * 2011-02-10 2012-08-16 Xvd Technology Holdings Limited Distribution en temps réel de communication en couches à l'aide d'un intergiciel centré sur les données de publication-abonnement
US20200367089A1 (en) * 2013-10-08 2020-11-19 Alef Mobitech Inc. Systems and methods for providing mobility aspects to applications in the cloud
WO2019214830A1 (fr) * 2018-05-11 2019-11-14 Huawei Technologies Co., Ltd. Entité de plan de commande et entité de plan de gestion pour échanger des données d'instance de tranche de réseau à des fins d'analyse

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 (fr) * 2022-10-12 2024-04-18 Intel Corporation Services de traitement en pipeline dans des réseaux cellulaires de prochaine génération

Also Published As

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

Similar Documents

Publication Publication Date Title
US11902985B2 (en) Default PDSCH beam setting and PDCCH prioritization for multi panel reception
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
EP4316115A1 (fr) Commutation entre des configurations de surveillance de canaux physiques de contrôle descendant (pdcch) de groupes d'ensembles d'espaces de recherche (sssg)
WO2022155488A1 (fr) Mécanismes de saut de fréquence améliorés pour dispositifs à capacité réduite (redcap)
EP4255092A1 (fr) Communication d'élément de réseau de l'internet des objets personnel avec un système 5g et d'autres éléments de réseau de l'internet des objets personnel
WO2023069653A1 (fr) Commutation d'équipement utilisateur (ue) entre des réseaux au moyen d'intervalles de mesure
WO2023044025A1 (fr) Utilisation d'un canal d'accès aléatoire physique (prach) pour identifier de multiples caractéristiques et combinaisons de caractéristiques
WO2022240750A1 (fr) Configuration de relations spatiales et de commande de puissance pour des transmissions en liaison montante
WO2022170213A1 (fr) Architecture de communication et de système informatique centrée sur les données
WO2022235962A1 (fr) Requêtes de répétitions de canal physique partagé de liaison montante (pusch) de msg3
WO2022035514A1 (fr) Période de mesure de positionnement d'équipement utilisateur pour de nouveaux systèmes radio
US20230163916A1 (en) Techniques for ue positioning measurement in rrc_inactive or rrc_idle
US20240155503A1 (en) Spatial relationship and power control configuration for uplink transmissions
EP4236457A1 (fr) Restriction de planification pour mesure l1-rsrp pour cellule à pci différent
US20240147470A1 (en) Flexible uplink control information (uci) transmission with physical uplink shared channel (pusch)
EP4236439A1 (fr) Comportement d'équipement utilisateur lors d'une modification d'intervalle de mesure préconfiguré
US20240155589A1 (en) Techniques for channel state information reference signal (csi-rs) transmission
US20230155781A1 (en) User equipment behavior and requirements for positioning measurement without gap
US20240146454A1 (en) Enhanced mapping for control channel transmission based on polar code
WO2023158726A1 (fr) Techniques pour une mesure de signal de référence de positionnement avec un intervalle de mesure
WO2023069742A1 (fr) Perfectionnements de chaînes d'indicateur de configuration de transmission (tci) pour de nouveaux systèmes radio
WO2023137211A1 (fr) Techniques pour éviter une interférence entre symboles pendant une commutation d'état tci dans des déploiements de train à grande vitesse
WO2022240862A1 (fr) Opérations sur faisceaux par défaut pour transmissions en liaison montante
WO2022174070A1 (fr) Mesures de performances pour applications d'informatique en périphérie

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