Mechanisms for Data-Centric Computing and Communication Infrastructures

Abstract

An apparatus and system for providing functions and processes in a data-centric infrastructure (DCI) are described. The logical architecture includes an infrastructure orchestration function and a controller. The interaction between the infrastructure orchestration function and the controller includes a function request to create or release a logical computing node, or to modify a logical computing node via adding or removing at least one of a function-dedicated computing (FDC) function, a data plane (DP) function, or a function-dedicated network (FDN) function to the logical computing node. The controller configures the FDC / DP / FDN function and sends a response indicating completion of the operation performed by the controller with respect to the function request.

Description

[Technical field]

[0001] This application claims the benefit of priority to U.S. Provisional Patent Application No. 63 / 184,442, filed May 3, 2021, which is incorporated by reference in its entirety.

[0002] Embodiments relate to next generation wireless communications, and more particularly, some embodiments relate to a next generation (NG) infrastructure level orchestration framework. [Background technology]

[0003] The use and complexity of Next Generation (NG) or New Radio (NR) wireless systems, including 5G networks and beginning to include sixth generation (6G) networks in particular, is increasing due to both the increasing number of types of device user equipment (UE) using network resources and the amount of data and bandwidth being used by various applications, such as video streaming, running on those UEs. With the enormous increase in the number and variety of communication devices, the corresponding network environment, including routers, switches, bridges, gateways, firewalls, and load balancers, is becoming increasingly complex. As might be expected, with the emergence of any new technology comes a multitude of problems. [Brief description of the drawings]

[0004] In the figures, which are not necessarily drawn to scale, like reference numbers may describe like components in different figures. Like reference numbers with different subscripts may represent different instances of like components. The figures generally illustrate various embodiments discussed herein by way of example, and not by way of limitation.

[0005] [Figure 1A] 1 illustrates a network architecture in accordance with some aspects.

[0006] [Figure 1B]1 illustrates a non-roaming 5G system architecture in accordance with some aspects.

[0007] [Figure 1C] 1 illustrates a non-roaming 5G system architecture in accordance with some aspects.

[0008] [Diagram 2] 1 illustrates a block diagram of a communication device according to some embodiments.

[0009] [Diagram 3] 1 illustrates a high-level architecture for a Data Centric Infrastructure (DCI) in accordance with some embodiments.

[0010] [Figure 4] 1 illustrates a system architecture according to some embodiments.

[0011] [Diagram 5] 1 illustrates logical computing node formation according to some embodiments.

[0012] [Figure 6] 1 illustrates a subscription notification model according to some embodiments.

[0013] [Figure 7] 1 illustrates a logical computing node reconfiguration in accordance with some embodiments.

[0014] [Figure 8] 1 illustrates adding new Function Dedicated Computing (FDC) / Data Plane (DP) functionality to an existing logical computing node, according to some embodiments.

[0015] [Figure 9] 1 illustrates removing FDC / DP functionality from an existing logical computing node according to some embodiments.

[0016] [Figure 10] 1 illustrates logical computing node release in accordance with some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0017] The following description and drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice the embodiments. Other embodiments may incorporate structural, logical, electrical, processing, and other changes. Portions and features of some embodiments may be included in, or substituted for, portions and features of other embodiments. The claimed embodiments encompass all available equivalents of those claims.

[0018] 1A illustrates a network architecture according to some aspects. Network 140A includes 3GPP LTE / 4G and NG network functions that may be extended to 6G functions. Thus, although 5G is mentioned, it should be understood that this should be extended to 6G structures, systems and functions as possible. Network functions may be implemented as separate network elements on dedicated hardware, as software instances running on dedicated hardware, and / or as virtualized functions instantiated on a suitable platform, such as dedicated hardware or a cloud infrastructure.

[0019] Network 140A is shown to include user equipment (UE) 101 and UE 102. UE 101 and 102 are shown as smartphones (e.g., handheld touchscreen mobile computing devices capable of connecting to one or more cellular networks), but may also include any mobile or non-mobile computing devices, such as portable (laptop) or desktop computers, wireless handsets, drones, or any other computing device that includes a wired and / or wireless communication interface. UE 101 and 102 may be collectively referred to herein as UE 101, which may be used to perform one or more of the techniques disclosed herein.

[0020] Any of the wireless links described herein (e.g., used in network 140A or any other illustrated network) may operate according to any exemplary wireless communication technology and / or standard. Any spectrum management scheme may be used, including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (LSA) at 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz and other frequencies, and Spectrum Access System (SAS) at 3.55-3.7 GHz and other frequencies). Different single carrier or orthogonal frequency domain multiplexing (OFDM) modes (CP-OFDM, SC-FDMA, SC-OFDM, Filter Bank Based Multicarrier (FBMC), OFDMA, etc.), particularly 3GPP® NR, may be used by assigning OFDM carrier data bit vectors to corresponding symbol resources.

[0021] In some aspects, any of the UEs 101 and 102 may include an Internet of Things (IoT) UE or a Cellular IoT (CIoT) UE that may include a network access layer designed for low-power IoT applications utilizing short-lived UE connections. In some aspects, any of the UEs 101 and 102 may include a Narrowband (NB) IoT UE (e.g., enhanced NB-IoT (eNB-IoT) UE and additional enhanced (FeNB-IoT) UE, etc.). The IoT UE may utilize technologies such as Public Land Mobile Network (PLMN), Proximity Based Services (ProSe) or Device-to-Device (D2D) communications, sensor networks, or Machine-to-Machine (M2M) or Machine-Type Communications (MTC) to exchange data with an MTC server or device over the IoT network. The M2M or MTC exchange of data may be a machine-initiated exchange of data. The IoT network includes interconnecting IoT UEs that may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. The IoT UE may perform background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network. In some aspects, either of the UEs 101 and 102 may include an enhanced MTC (eMTC) UE or a further enhanced MTC (FeMTC) UE.

[0022] The UEs 101 and 102 may be configured to be connected, e.g., communicatively coupled, to a Radio Access Network (RAN) 110. The RAN 110 may be, e.g., an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN. The RAN 110 may include one or more gNBs, one or more of which may be implemented by multiple units.

[0023] Each of the gNBs may implement protocol entities in the 3GPP protocol stack, where the layers are considered to be layered from lowest to highest, in that order: physical layer (PHY), medium access control (MAC), radio link control (RLC), packet data convergence control (PDCP), and radio resource control (RRC) / service data adaptation protocol (SDAP) (for control plane / user plane). The protocol layers of each gNB may be distributed to different units, namely, a central unit (CU), at least one distributed unit (DU), and a remote radio head (RRH). The CU may provide functions such as control of the transfer of user data and may provide mobility control, radio access network sharing, positioning, and session management, except for functions exclusively assigned to the DU.

[0024] The higher protocol layers (PDCP and RRC for the control plane / PDCP and SDAP for the user plane) may be implemented in the CU, and the RLC and MAC layers may be implemented in the DU. The PHY layer may be split, with the higher PHY layers also implemented in the DU, while the lower PHY layers are implemented in the RRH. The CU, DU and RRH may be implemented by different manufacturers, but may still be connected by appropriate interfaces between them. The CU may be connected by multiple DUs.

[0025] The interfaces within the gNB include E1 and fronthaul (F)F1 interfaces. The E1 interface may be between the CU control plane (gNB-CU-CP) and the CU user plane (gNB-CU-UP), and thus may support the exchange of signaling information between the control plane and the user plane via the E1AP service. The E1 interface may separate the radio network layer and the transport network layer, and may enable the exchange of UE-related and non-UE-related information. The E1AP service may be a non-UE-related service for the entire E1 interface instance between the gNB-CU-CP and the gNB-CU-UP with a non-UE-related signaling connection for a single UE and a UE-related service, which is associated with the UE-related signaling connection maintained for the UE.

[0026] The F1 interface may be disposed between the CU and the DU. The CU may control the operation of the DU over the F1 interface. As the signaling in the gNB is divided into control plane and user plane signaling, the F1 interface may be divided into an F1-C interface for control plane signaling between the gNB-DU and the gNB-CU-CP, and an F1-U interface for user plane signaling between the gNB-DU and the gNB-CU-UP, which support the separation of the control plane and the user plane. The F1 interface may separate the radio network and the transport network layers and may enable the exchange of UE-related and non-UE-related information. In addition, the F2 interface may be between the lower and higher parts of the NR PHY layer. The F2 interface may also be separated into F2-C and F2-U interfaces based on the control plane and user plane functions.

[0027] UEs 101 and 102 utilize connections 103 and 104, respectively, each of which includes a physical communication interface or layer (described in further detail below), which in this example are illustrated as air interfaces enabling communicative coupling and may align with cellular communication protocols such as Global System for Mobile Communications (GSM) protocol, Code Division Multiple Access (CDMA) network protocol, Push-to-Talk (PTT) protocol, PTT over Cellular (POC) protocol, Universal Mobile Telecommunications System (UMTS) protocol, 3GPP Long Term Evolution (LTE) protocol, 5G protocol, 6G protocol, etc.

[0028] In an aspect, the UEs 101 and 102 may further exchange communication data directly via the ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a sidelink (SL) interface that includes one or more logical channels, including, but not limited to, a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), a physical sidelink discovery channel (PSDCH), a physical sidelink broadcast channel (PSBCH), and a physical sidelink feedback channel (PSFCH).

[0029] The UE 102 is shown as configured to access an access point (AP) 106 via a connection 107. The connection 107 may include, for example, a local wireless connection, such as a connection conforming to any IEEE 802.11 protocol, according to which the AP 106 may include a Wireless Fidelity (WiFi) router. In this example, the AP 106 is shown as connected to the Internet without being connected to a core network of a wireless system (described in more detail below).

[0030] The RAN 110 may include one or more access nodes that enable the connections 103 and 104. These access nodes (AN) may be referred to as base stations (BS), NodeBs, evolved NodeBs (eNBs), next generation NodeBs (gNBs), RAN nodes, etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). In some aspects, the communication nodes 111 and 112 may be transmit / receive points (TRPs). When the communication nodes 111 and 112 are NodeBs (e.g., eNBs or gNBs), the one or more TRPs may function within the communication cell of the NodeB. The RAN 110 may include one or more RAN nodes for providing a macrocell, e.g., a macro RAN node 111, and one or more RAN nodes for providing a femtocell or picocell (e.g., a cell having a smaller coverage area, a smaller user capacity, or a higher bandwidth compared to a macrocell), e.g., a low power (LP) RAN node 112.

[0031] Either of the RAN nodes 111 and 112 may implement an air interface protocol. termination and may be the first point of contact to the UEs 101 and 102. In some aspects, any of the RAN nodes 111 and 112 may perform various logical functions for the RAN 110, including, but not limited to, radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and radio network controller (RNC) functions such as mobility management. In one example, any of the nodes 111 and / or 112 may be a gNB, eNB, or another type of RAN node.

[0032] The RAN 110 is shown as communicatively coupled to a core network (CN) 120 via an S1 interface 113. In an aspect, the CN 120 may be an Evolved Packet Core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN (e.g., as shown with reference to Figures 1B-1C). In this aspect, the S1 interface 113 is divided into two parts: an S1-U interface 114 that carries traffic data between the RAN nodes 111 and 112 and a Serving Gateway (S-GW) 122, and an S1-Mobility Management Entity (MME) interface 115 that is a signaling interface between the RAN nodes 111 and 112 and an MME 121.

[0033] In this aspect, the CN 120 includes an MME 121, an S-GW 122, a Packet Data Network (PDN) Gateway (P-GW) 123, and a Home Subscriber Server (HSS) 124. The MME 121 may be similar in function to the control plane of a legacy Serving General Packet Radio Service (GPRS) Support Node (SGSN). The MME 121 may manage mobility aspects during access such as gateway selection and tracking area list management. The HSS 124 may include a database of network users including subscription related information to support the handling of communication sessions of network entities. The CN 120 may include one or several HSSs 124 depending on the number of mobile subscribers, equipment capacity, organization of the network, etc. For example, the HSS 124 may provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependency, etc.

[0034] The S-GW 122 transmits the S1 interface 113 to the RAN 110. termination death Well , routes data packets between RAN 110 and CN 120 vinegarIn addition, the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and may also provide an anchor for inter-3GPP mobility. Other roles of the S-GW 122 may include lawful interception, charging, and some policy enforcement.

[0035] The P-GW123 provides an SGi interface to the PDN. termination The P-GW 123 may route data packets between the CN 120 and external networks, such as a network including an application server 184 (alternatively referred to as an application function (AF)) via an Internet Protocol (IP) interface 125. The P-GW 123 may also communicate data to other external networks 131A, which may include the Internet, an IP Multimedia Subsystem (IPS) network, and other networks. In general, the application server 184 may be an element providing applications (e.g., UMTS Packet Service (PS) domain, LTE PS data services, etc.) using IP bearer resources with the core network. In this aspect, the P-GW 123 is shown as communicatively coupled to the application server 184 via the IP interface 125. The application server 184 may also be configured to support one or more communication services (e.g., Voice over Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) of the UEs 101 and 102 via the CN 120.

[0036] The P-GW 123 may further be a policy enforcement and charging data collection node. The Policy and Charging Rules Function (PCRF) 126 is the policy and charging control element of the CN 120. In a non-roaming scenario, in some aspects, there may be a single PCRF in a Home Public Land Mobile Network (HPLMN) associated with the UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with local breakout of traffic, there may be two PCRFs associated with the UE's IP-CAN session, namely, a Home PCRF (H-PCRF) in the HPLMN and a Visited PCRF (V-PCRF) in a Visited Public Land Mobile Network (VPLMN). The PCRF 126 may be communicatively coupled to the application server 184 via the P-GW 123.

[0037] In some aspects, the communication network 140A may be an IoT network or a 5G or 6G network including a 5G New Radio network that employs communication in licensed (5G NR) and unlicensed (5G NR-U) spectrum. One of the current enablers of IoT is Narrowband IoT (NB-IoT). Operation in the unlicensed spectrum may include Dual Connectivity (DC) operation in the unlicensed spectrum and standalone LTE systems, according to which LTE-based technologies operate exclusively in the unlicensed spectrum without the use of an "anchor" in the licensed spectrum, called MuLTEFire. Additional enhanced operation of LTE systems in licensed as well as unlicensed spectrum is expected in future releases and 5G systems. Such enhanced operation may include techniques for sidelink resource allocation and UE processing behavior for NR sidelink V2X communications.

[0038] The NG system architecture (or 6G system architecture) may include a RAN 110 and a 5G Core Network (5GC) 120. The NG-RAN 110 may include multiple nodes such as a gNB and an NG-eNB. The CN 120 (e.g., 5G Core Network / 5GC) may include an Access and Mobility Function (AMF) and / or a User Plane Function (UPF). The AMF and UPF may be communicatively coupled to the gNB and the NG-eNB via an NG interface. More specifically, in some aspects, the gNB and the NG-eNB may be connected to the AMF by an NG-C interface and to the UPF by an NG-U interface. The gNB and the NG-eNB may be coupled to each other via an Xn interface.

[0039] In some aspects, the NG system architecture may use reference points between various nodes. In some aspects, each of the gNB and the NG-eNB may be implemented as a base station, a mobile edge server, a small cell, a home eNB, and so on. In some aspects, the gNB may be a master node (MN) and the NG-eNB may be a secondary node (SN) in the 5G architecture.

[0040] FIG. 1B illustrates a non-roaming 5G system architecture according to some aspects. In particular, FIG. 1B illustrates a 5G system architecture 140B in a reference point representation, which may be extended to a 6G system architecture. More specifically, a UE 102 can communicate with a RAN 110 and one or more other 5GC network entities. The 5G system architecture 140B includes a number of network functions (NFs), such as an AMF 132, a session management function (SMF) 136, a policy control function (PCF) 148, an application function (AF) 150, a UPF 134, a network slice selection function (NSSF) 142, an authentication server function (AUSF) 144, and a unified data management (UDM) / home subscriber server (HSS) 146.

[0041] The UPF 134 may provide a connection to the data network (DN) 152, which may include, for example, operator services, Internet access, or third-party services. The AMF 132 may be used to manage access control and mobility, and may also include a network slice selection function. The AMF 132 may provide UE-based authentication, authorization, mobility management, etc., and may be independent of the access technology. The SMF 136 may be configured to set up and manage various sessions according to network policies. Thus, the SMF 136 may be responsible for session management and assignment of IP addresses to the UE. The SMF 136 may also select and control the UPF 134 for data forwarding. The SMF 136 may be associated with a single session of the UE 101 or multiple sessions of the UE 101. That is, the UE 101 may have multiple 5G sessions. A different SMF may be assigned to each session. The use of different SMFs may allow each session to be managed separately. As a result, the functionality of each session may be independent of each other.

[0042] The UPF 134 can be deployed in one or more configurations according to the desired service type and can be connected with a data network. The PCF 148 can be configured to provide a policy framework with network slicing, mobility management, and roaming (similar to a PCRF in a 4G communication system). The UDM can be configured to store subscriber profiles and data (similar to an HSS in a 4G communication system).

[0043] The AF 150 may provide information on packet flows to the PCF 148, which is responsible for policy control to support the desired QoS. The PCF 148 may set mobility and session management policies for the UE 101. To this end, the PCF 148 may use the packet flow information to determine appropriate policies for appropriate operation of the AMF 132 and SMF 136. The AUSF 144 may store data for UE authentication.

[0044] In some aspects, the 5G system architecture 140B includes multiple IP multimedia core network subsystem entities, such as an IP multimedia subsystem (IMS) 168B, as well as a call session control function (CSCF). More specifically, the IMS 168B includes a CSCF, which can operate as a Proxy CSCF (P-CSCF) 162BE, a Serving CSCF (S-CSCF) 164B, an Emergency CSCF (E-CSCF) (not shown in FIG. 1B), or an Interrogate CSCF (I-CSCF) 166B. The P-CSCF 162B can be configured to be the first point of contact for the UE 102 in the IM subsystem (IMS) 168B. The S-CSCF 164B can be configured to handle session states in the network, and the E-CSCF can be configured to handle certain aspects of the emergency session, such as routing the emergency request to the correct emergency center or PSAP. The I-CSCF 166B can be configured to act as a contact point within the operator's network for all IMS connections destined for the network operator's subscribers or roaming subscribers currently located within the network operator's service area. In some aspects, the CSCF 166B can be connected to another IP multimedia network 170B, e.g., an IMS operated by a different network operator.

[0045] In some aspects, the UDM / HSS 146 may even be coupled to an application server (AS) 160B, which may include a telephony application server (TAS) or another application server. The AS 160B may be coupled to the IMS 168B via the S-CSCF 164B or the I-CSCF 166B.

[0046] The reference point representation indicates that interactions may exist between corresponding NF services. For example, FIG. 1B shows the following reference points N1 (between UE 102 and AMF 132), N2 (between RAN 110 and AMF 132), N3 (between RAN 110 and UPF 134), N4 (between SMF 136 and UPF 134), N5 (between PCF 148 and AF 150, not shown), N6 (between UPF 134 and DN 152), N7 (between SMF 136 and PCF 148, not shown), N8 (between UDM 146 and AMF 132, not shown), N9 (between two UPFs 134, not shown), N10 (between UDM 146 and SMF 136, not shown), 1B shows N11 (between AMF 132 and SMF 136, not shown), N12 (between AUSF 144 and AMF 132, not shown), N13 (between AUSF 144 and UDM 146, not shown), N14 (between two AMFs 132, not shown), N15 (between PCF 148 and AMF 132 in case of a non-roaming scenario, or between PCF 148, visited network and AMF 132 in case of a roaming scenario, not shown), N16 (between two SMFs, not shown), and N22 (between AMF 132 and NSSF 142, not shown). Other reference point representations not shown in FIG. 1B can also be used.

[0047] 1C illustrates a 5G system architecture 140C and a service-based representation. In addition to the network entities illustrated in FIG. 1B, the system architecture 140C can also include a network publication function (NEF) 154 and a network repository function (NRF) 156. In some aspects, the 5G system architecture can be service-based, and the interactions between network functions can be represented by corresponding point-to-point reference points Ni or service-based interfaces.

[0048] In some aspects, as shown in Figure 1C, a service-based representation can be used to represent network functions in the control plane that allow other authorized network functions to access those services. In this regard, the 5G system architecture 140C can include the following service-based interfaces: Namf 158H (service-based interface indicated by AMF 132), Nsmf 158I (service-based interface indicated by SMF 136), Nnef 158B (service-based interface indicated by NEF 154), Npcf 158D (service-based interface indicated by PCF 148), Nudm 158E (service-based interface indicated by UDM 146), Naf 158F (service-based interface indicated by AF 150), Nnrf 158C (service-based interface indicated by NRF 156), Nnssf 158A (service-based interface indicated by NSSF 142), and Nausf 158G (service-based interface indicated by AUSF 144). Other service-based interfaces not shown in FIG. 1C (eg, Nudr, N5g-eir, and Nudsf) can also be used.

[0049] The NR-V2X architecture may support reliable, low-latency sidelink communications with a variety of traffic patterns, including periodic and aperiodic communications with random packet arrival times and sizes. The techniques disclosed herein can be used to support high reliability in distributed communication systems with dynamic topologies, including sidelink NR V2X communication systems.

[0050] FIG. 2 illustrates a block diagram of a communication device according to some embodiments. The communication device 200 may be a dedicated network equipment such as a dedicated computer, a personal or laptop computer (PC), a UE such as a tablet PC or smartphone, an eNB, software running on a server to configure the server to operate as a network device, a virtual device, or any machine capable of executing (sequentially or otherwise) instructions that specify actions to be taken by the machine. For example, the communication device 200 may be implemented as one or more of the devices illustrated in FIG. 1A through FIG. 1C. It is noted that the communications described herein may be encoded prior to transmission by transmitting entities (e.g., UE, gNB) for reception by the receiving entity (e.g., gNB, UE) and decoded after reception by the receiving entity.

[0051] As described herein, examples may include or operate on logic or multiple components, modules, or mechanisms. Modules and components are tangible entities (e.g., hardware) capable of performing certain operations and may be configured or arranged in a certain manner. In an example, a circuit may be configured in a certain manner (e.g., internally or with respect to an external entity such as another circuit) as a module. In an example, all or a portion of one or more computer systems (e.g., standalone, client, or server computer systems) or one or more hardware processors may be configured by firmware or software (e.g., instructions, application parts, or applications) as modules that operate to perform certain operations. In an example, the software may reside on a machine-readable medium. In an example, the software, when executed by the underlying hardware of a module, causes the hardware to perform certain operations.

[0052] Thus, the terms "module" (and "component") are understood to encompass tangible entities that are physically constructed entities and that are specifically configured (e.g., hardwired) or temporarily (e.g., transiently) configured (e.g., programmed) to operate in a particular manner or to perform some or all of the operations described herein. Considering an example in which modules are temporarily configured, each of the modules need not be instantiated at any one time. For example, if the modules have a general-purpose hardware processor that is configured using software, the general-purpose hardware processor may be configured as different modules at different times. Thus, the software may configure the hardware processor, for example, to configure a particular module at one time and another module at a different time.

[0053] The communication device 200 may include a hardware processor (or equivalent processing circuitry) 202 (e.g., a central processing unit (CPU), a GPU, a hardware processor core, or any combination thereof), a main memory 204, and a static memory 206, some or all of which may be in communication with each other via an interlink (e.g., a bus) 208. The main memory 204 may include any or all of removable and non-removable storage, volatile memory, or non-volatile memory. The communication device 200 may further include a display unit 210, such as a video display, an alphanumeric input device 212 (e.g., a keyboard), and a user interface (UI) navigation device 214 (e.g., a mouse). In one example, the display unit 210, the input device 212, and the UI navigation device 214 may be touch screen displays. The communication device 200 may additionally include a storage device (e.g., a drive unit) 216, a signal generating device 218 (e.g., a speaker), a network interface device 220, and one or more sensors, such as a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensor. The communication device 200 may further include an output controller, such as a serial (e.g., Universal Serial Bus (USB)), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection for communication with or control of one or more peripheral devices (e.g., a printer, a card reader, etc.).

[0054] The storage device 216 may include a non-transitory machine-readable medium 222 (hereinafter simply referred to as a machine-readable medium) having stored thereon one or more data structures or sets of instructions 224 (e.g., software) embodied or utilized by any one or more of the techniques or functions described herein. The instructions 224 may reside, completely or at least partially, within the main memory 204, within the static memory 206, and / or within the hardware processor 202 during their execution by the communications device 200. While the machine-readable medium 222 is illustrated as a single medium, the term "machine-readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and / or associated caches and servers) configured to store one or more instructions 224.

[0055] The term "machine-readable medium" may include any medium capable of storing, encoding, or carrying instructions for execution by communication device 200 and causing communication device 200 to perform any one or more of the techniques of this disclosure, or any medium capable of storing, encoding, or carrying data structures used by or associated with such instructions. Non-limiting examples of machine-readable media may include solid-state memories, and optical and magnetic media. Specific examples of machine-readable media may include non-volatile memory such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM)) and flash memory devices, magnetic disks such as internal hard disks and removable disks, optical disks, random access memory (RAM), and CD-ROM and DVD-ROM disks.

[0056] The instructions 224 may further be transmitted or received over a communications network using a transmission medium 226 via a network interface device 220 utilizing any one of a number of wireless local area network (WLAN) transport protocols (e.g., Frame Relay, Internet Protocol (IP), Transmission Control Protocol (TCP), User Datagram Protocol (UDP), Hypertext Transfer Protocol (HTTP), etc.). Exemplary communications networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), a mobile telephone network (e.g., a cellular network), a plain old telephone (POTS) network, and a wireless data network. Communications over the network may include one or more different protocols, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi, the IEEE 802.16 family of standards known as WiMax, the IEEE 802.15.4 family of standards, the Long Term Evolution (LTE) family of standards, the Universal Mobile Telecommunications System (UMTS) family of standards, peer-to-peer (P2P) networks, Next Generation (NG) / Fifth Generation (5G) standards, among others. In one example, the network interface device 220 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jack) or one or more antennas to connect to the transmission medium 226.

[0057] It is noted that the term "circuitry" as used herein refers to or includes a portion of hardware components configured to provide a described functionality, such as electronic circuits, logic circuits, processors (shared, dedicated, or groups), and / or memories (shared, dedicated, or groups), application specific integrated circuits (ASICs), field programmable devices (FPDs) (e.g., field programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high capacity PLDs (HCPLDs), structured ASICs, or programmable SoCs), digital signal processors (DSPs), etc. In some embodiments, a 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 program code used to perform the functions 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.

[0058] The term "processor circuitry" or "processor" as used herein therefore refers to, is a part of, or includes circuitry capable of sequentially and automatically performing a series of arithmetic or logical operations, or recording, storing, and / or transmitting digital data. The term "processor circuitry" or "processor" may refer to one or more application processors, one or more baseband processors, physical central processing units (CPUs), single or multi-core processors, and / or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and / or functional processes.

[0059] Any of the wireless links described herein may be based on Global System for Mobile Communications (GSM) wireless communication technology, General Packet Radio Service (GPRS) wireless communication technology, Enhanced Data Rates for GSM Evolution (EDGE) wireless communication technology, and / or Third Generation Partnership Project (3GPP) wireless communication technology, such as Universal Mobile Telecommunications System (UMTS), Freedom of Multimedia Access (FOMA), 3GPP Long Term Evolution (LTE), 3GPP Long Term Evolution Advanced (LTE-Advanced), Code Division Multiple Access 2000 (CDMA2000), Cellular Digital Packet Data (CDPD), Mobitex, 3G (3G-LTE), LTE-LTE, LTE- ... 3G), Circuit Switched Data (CSD), High Speed ​​Circuit Switched Data (HSCSD), Universal Mobile Telecommunications System (3rd Generation) (UMTS (3G)), Wideband Code Division Multiple Access (Universal Mobile Telecommunications System) (W-CDMA (UMTS)), High Speed ​​Packet Access (HSPA), High Speed ​​Downlink Packet Access (HSDPA) High Speed ​​Uplink Packet Access (HSUPA), High Speed ​​Packet Access Plus (HSPA+), Universal Mobile Telecommunications System-Time Division Duplex (UMTS-TDD), Time Division Code Division Multiple Access (TD-CDMA), Time Division Synchronous Code Division Multiple Access (TD-SCDMA), 3rd Generation Partnership Project Release 8 (Pre-4th Generation) (3GPP®) Rel. 8 (Pre-4G), 3GPP(registered trademark) Rel. 9 (3rd Generation Partnership Project Release 9), 3GPP(registered trademark) Rel. 10 (3rd Generation Partnership Project Release 10), 3GPP(registered trademark) Rel. 11 (3rd Generation Partnership Project Release 11), 3GPP(registered trademark) Rel. 12 (3rd Generation Partnership Project Release 12), 3GPP(registered trademark) Rel. 13 (3rd Generation Partnership Project Release 13), 3GPP(registered trademark) Rel.14 (3rd Generation Partnership Project Release 14), 3GPP® Rel. 15 (3rd Generation Partnership Project Release 15), 3GPP® Rel. 16 (3rd Generation Partnership Project Release 16), 3GPP® Rel. 17 (3rd Generation Partnership Project Release 17) and subsequent releases (Rel. 18, Rel. 19, etc.), 3GPP® 5G, 5G, 5G New Radio (5G NR), 3GPP® 5G New Radio, 3GPP® LTE Extra, LTE Advanced Pro, LTE Licensed Assisted Access (LAA), MuLTEFire, UMTS Terrestrial Radio Access (UTRA), Evolved UMTS Terrestrial Radio Access (E-UTRA), Long Term Evolution Advanced (4th Generation) (LTE-Advanced (4G)), cdmaOne (2G), Code Division Multiple Access 2000 (3rd Generation) (CDMA2000 (3G)), Evolution Data Optimized or Evolution Data Only (EV-DO), Advanced Mobile Phone System (1st Generation) (AMPS (1G)), Total Access Communication System / Enhanced Total Access Communication System (TACS / ETACS), Digital AMPS (2nd Generation) (D-AMPS (2G)), Push-to-Talk (PTT), Mobile Telephone System (MTS), Improved Mobile Telephone System (IMT), Advanced Mobile Telephone System (AMTS), OLT (Offentlig Landmobil Telefoni in Norwegian, Public Land Mobile Telephony), MTD (Mobiltelefonisystem in Swedish)Also known as the abbreviation for D, or Mobile Telephony System D), Public Automated Land Mobile (Autotel / PALM), ARP (Autoradiopuhelin, "car radio phone" in Finnish), NMT (Nordic Mobile Telephony), the high capacity version of NTT (Nippon Telegraph and Telephone) (Hicap), Cellular Digital Packet Data (CDPD), Mobitex, DataTAC, Integrated Digital Enhanced Network (iDEN), Personal Digital Cellular (PDC), Circuit Switched Data (CSD), Personal Handy Phone System (PHS), Broadband Integrated Digital Enhanced Network (WiDEN), iBurst, Unlicensed Mobile Access (UMA), 3GPP® Generic Access Network, or GAN standard, and is commonly known as Zigbee®, Bluetooth®(r), Wireless Gigabit Alliance (WiGig) standard, mmWavestandards (wireless systems operating from 10-300 GHz, and above WiGig, IEEE 802.11ad, IEEE 802.11ay, etc.), technologies operating above 300 GHz and in the THz bands, (3GPP® / LTE based or IEEE 802.11p or IEEE 802.11bd and other) Vehicle-to-Vehicle (V2V) and Vehicle-to-X (V2X) and Vehicle-to-Infrastructure (V2I) and Infrastructure-to-Vehicle (I2V) communication technologies, DSRC (Dedicated for Short Range Communications) communication systems such as 3GPP® Cellular V2X, Intelligent Transport Systems and others (typically operating at 5850 MHz to 5925 MHz or above (typically up to 5935 MHz following the proposed changes in CEPT Report 71)), European ITS- It may operate according to any one or more of the following wireless communication technologies and / or standards, including, but not limited to, G5 systems (i.e., a European flavor of IEEE 802.11p-based DSRC, including ITS-G5A (i.e., ITS-G5 operation in the European ITS frequency bands dedicated to ITS for safety-related applications in the frequency range 5.875 GHz to 5.905 GHz), ITS-G5B (i.e., operation in the European ITS frequency bands dedicated to ITS non-safety applications in the frequency range 5.855 GHz to 5.875 GHz), ITS-G5C (i.e., operation of ITS applications in the frequency range 5.470 GHz to 5.725 GHz)), DSRC in Japan in the 700 MHz bands (715 MHz to 725 MHz inclusive), IEEE 802.11bd-based systems, etc.

[0060] The aspects described herein may be used in the context of any spectrum management scheme, including dedicated licensed spectrum, unlicensed spectrum, licensed exempt spectrum, (licensed) shared spectrum (such as LSA=Licensed Shared Access in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz and further frequencies, and SAS=Spectrum Access System / CBRS=Citizen Broadband Radio System in 3.55-3.7 GHz and further frequencies).Suitable spectrum bands include IMT (International Mobile Telecommunications) spectrum and bands with national allocations (450-470 MHz, 902-928 MHz (note: allocated, for example, to the United States (FCC Part 15)), 863-868.6 MHz (note: allocated, for example, to the European Union (ETSI EN300 220)), 915.9-929.7 MHz (note: allocated, for example, to Japan), 917-923.5 MHz (note: allocated, for example, to South Korea), 755-779 MHz and 779-787 MHz (note: allocated, for example, to China), 790-960 MHz, 1710-2025 MHz, 2110-2200 MHz, 2300-2400 MHz, 2.4-2.4835 GHz (note: this is an ISM band with global availability and is used by the Wi-Fi technology family (11b / g / n / ax) and also B 5.15-5.25 GHz, and 5.25-5.35 GHz, 5.47-5.725 GHz and 5.725-5.85 GHz bands (Note: allocated, for example, in the United States for Citizens Broadband Wireless Service), 2500-2690 MHz, 698-790 MHz, 610-790 MHz, 3400-3600 MHz, 3400-3800 MHz, 3800-4200 MHz, 3.55-3.7 GHz (Note: allocated, for example, in the United States for Citizens Broadband Wireless Service), 5.15-5.25 GHz, and 5.25-5.35 GHz, 5.47-5.725 GHz and 5.725-5.85 GHz bands (Note: allocated, for example, in the United States for Citizens Broadband Wireless Service (FCC part 15), consisting of four U-NII bands totaling 500 MHz of spectrum), 5.725-5.875 GHz (NOTE: allocated, for example, to the EU (ETSI EN301 893)), 5.47-5.65 GHz (NOTE: allocated, for example, to South Korea), 5925-7125 MHz and 5925-6425 MHz (NOTE: under consideration in the US and EU, respectively, it is expected that next generation Wi-Fi systems will include 6 GHz spectrum as an operating band, but as of December 2017, Wi-Fi systems are not yet permitted in this band).The legislation is expected to expire in the 2019-2020 timeframe), IMT-Advanced spectrum, IMT-2020 spectrum (expected to include 3600-3800 MHz, 3800-4200 MHz, 3.5 GHz band, 700 MHz band, and bands within the 24.25-86 GHz band, etc.), spectrum made available under the FCC's "Spectrum Frontier" 5G initiative (including 27.5-28.35 GHz, 29.1-29.25 GHz, 31-31.3 GHz, 37-38.6 GHz, 38.6-40 GHz, 42-42.5 GHz, 57-64 GHz, 71-76 GHz, 81-86 GHz, and 92-94 GHz, etc.), This includes other types of spectrum / bands such as 57-64 / 66 GHz (Note: this band has a near-global designation for Multi-Gigabit Wireless Systems (MGWS) / WiGig), including the 5.9 GHz ITS (Intelligent Transport Systems) band (typically 5.85-5.925 GHz), and 63-64 GHz, which includes the bands currently allocated to WiGig such as WiGiBand 1 (57.24-59.40 GHz), WiGiBand 2 (59.40-61.56 GHz), WiGiBand 3 (61.56-63.72 GHz), and WiGiBand 4 (63.72-65.88 GHz). In the United States (FCC part 15), a total of 14 GHz of spectrum is allocated, while the EU (ETSI EN302 567 and ETSI EN301 217-2 for fixed P2P) allocates a total of 9 GHz of spectrum, including bands currently allocated to automotive radar applications such as the 70.2 GHz-71 GHz band, any band between 65.88 GHz and 71 GHz, 76-81 GHz, and future bands including 94-300 GHz and above. Furthermore, schemes can be used based secondarily on bands such as TV white space bands (typically below 790 MHz), with the 400 MHz and 700 MHz bands being promising candidates in particular. In addition to cellular applications, specific applications for vertical markets can be addressed, such as PMSE (programming and special events), medical, health, surgery, automotive, low latency, drones, and other applications.

[0061] The aspects described herein may also implement hierarchical application of the scheme, for example, by introducing a hierarchical prioritization of usage (e.g., low / medium / high priority, etc.) for different types of users based on prioritized access to spectrum (e.g., highest priority for tier-1 users, followed by tier-2, then tier-3 users, etc., etc.).

[0062] The aspects described herein may also be applied to different single carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, Filter Bank Based Multi-Carrier (FBMC), OFDMA, etc.), particularly to 3GPP NR (New Radio), by allocating OFDM carrier data bit vectors to corresponding symbol resources.

[0063] 5G networks extend beyond traditional mobile broadband services to provide a variety of new services such as Internet of Things (IoT), industrial control, autonomous driving, and mission-critical communications, which may have requirements for ultra-low latency, ultra-high reliability, and high data capacity due to safety and performance concerns. Some of the features in this document are defined on the network side, such as AP, eNB, NR, or gNB (note that this term is typically used in the context of 3GPP 5G or 6G communication systems, etc.). Nevertheless, a UE may play this role as well and operate as an AP, eNB, or gNB, i.e., some or all of the features defined for the network equipment may be implemented by the UE.

[0064] As mentioned above, next generation architectures are further planned. Figure 3 shows a high-level architecture for Data Centric Infrastructure (DCI) according to some embodiments. In particular, Figure 3 shows the DCI architecture defined by Innovative Optical and Wireless Networks (IOWN) Global Forum (GF). The DCI architecture can help provide various classes of data with different levels of requirements (e.g., volume, speed / latency, computing workload / energy consumption, scalability and elasticity, fiber capacity, data management) to be efficiently and flexibly provided to meet customer demands.

[0065] The DCI architecture is a distributed, end-to-end architecture that spans cloud, edge, and customer premises. Heterogeneous Computing and Networking environmentto applications. Data processing and storage functions, such as filtering, aggregation, event mediation, and shared object / database storage, can be located at desired locations. Support for function-specific computing allows service providers to easily add computing resources to perform specialized computing tasks, such as image AI inference, time-sensitive data processing, network function virtualization (NFV), and databases. The DCI subsystem exposes service interfaces to application functional nodes for applications, such as CPSs and AICs. Application developers can then build applications that leverage the functions and features provided by the DCI and open APNs. The infrastructure orchestrator is the central management function of the DCI, which controls infrastructure resources and exposes a single management interface. The application orchestrator is the central manager of the application system, which controls multiple application processes, i.e., microservices for the application. When the application orchestrator deploys an application process on the IOWN system, the application orchestrator calls the API of the infrastructure orchestrator to generate a runtime environment, e.g., a logical node.

[0066] A function-specific computing (FDC) function is formed by computing resources for performing dedicated computing tasks such as AI training acceleration, video processing, etc. FDC can be formed with distributed computing resources and can be configured for each workload requirement. Both resource-level FDC and service-level FDC can be formed. A data plane function provides a fabric for connecting distributed physical computing resources to form an FDC function.

[0067] The Data Plane (DP) function exposes services for data exchange, shared data access, and data coherence between FDC functions both within and between data centers. The services should provide a common data plane that allows different types of computing functions to exchange data. At the intra-data center level, FDC functions exchange data through a Reconfigurable High Speed ​​Interconnect and Shared Memory (RHISM). At the inter-data center level, a Function Dedicated Network (FDN) that matches traffic types and QoS requirements connects the data centers, and FDN NICs exchange data through the FDN. The FDN function is a network (e.g., optical network) built on top of an open APN that provides dedicated connections between endpoints to support different traffic and QoS requirements.

[0068] The FDC controller, DP controller and FDN controller are control plane functions that configure and control the FDC function, DP function and FDN function, respectively. Telemetry collection (at various destination points at various geographic distance locations) is also part of the FDC / DP / FDN controller functions. Telemetry may monitor network quality information including latency, jitter and bandwidth of each lightpath in real time (with associated APIs). Other control and management plane functions may be defined for control and management services such as control for data analysis, control for data sharing, infrastructure orchestration, system operation automation, etc. Service-based interfaces (SBIs) are used to connect the control and management plane functions. Service exposure functions are defined to expose IOWN system services to external users.

[0069] Use cases enabled by 5G aspects of the DCI architecture include enhanced mobile broadband (eMBB), ultra-reliable low latency communications (uRLLC), massive machine type communications (mMTC), and high speed fixed wireless access (FWA). Potential 6G capabilities of the DCI architecture include integrated satellite and terrestrial communications, THz communications, AI powered by ubiquitous computing, and data-in networks, and highly distributed flat networks.

[0070] FIG. 4 illustrates a system architecture according to some embodiments. In the logical system architecture of FIG. 4, as above, FDC functions represent physical computing units such as CPUs, xPUs, accelerators, etc. DP functions represent physical data storage and sharing units such as devices, memories, or caches. FDN functions represent interconnect network functions running on top of optical networks. Examples of such interconnect network functions include Peripheral Component Interconnect Express (PCIe) devices, Compute Express Link (CXL) devices, Ethernet devices, Remote Direct Memory Access (RDMA) devices, etc. The FDC / DP / FDN controller is a control engine that controls its serving FDC / DP / FDN functions. FDC may run on a CPU or on an infrastructure processing unit (IPU). The infrastructure orchestration function orchestrates the FDC / DP / FDN functions in the infrastructure to establish / maintain / update logical computing nodes to meet service requirements. An infrastructure orchestration function instance may run on a CPU or an IPU.

[0071] FIG. 5 illustrates logical computing node formation, according to some embodiments. Specifically, FIG. 5 illustrates an example of a process for distributed computing node formation (or creation). In operation 1, an infrastructure service consumer sends an infrastructure service request to an infrastructure orchestration function. Examples of infrastructure service consumers include container runtimes, virtual machine runtimes, operating systems, application microservices, etc. The infrastructure service request may include two types of information: Type 1: FDC function type (e.g., CPU, xPU, FPGA, accelerator) 、 Amount, duration Information about ;Type 2: Workload oh and its service requirements Information about Upon receiving the second type of information, the infrastructure orchestration functionality translates the workload and service requirements into FDC types, quantities, durations, and the like.

[0072] Operations 2 and 3 include the infrastructure orchestration function sending a computing and data resource discovery and status inquiry message to the FDC / DP / FDN controller. The FDC / DP / FDN controller responds to the inquiry. This inquiry / response enables the infrastructure orchestration function to discover resource availability and status of the FDC / DP / FDN functions in the infrastructure.

[0073] FIG. 6 illustrates a subscription notification model according to some embodiments. In particular, FIG. 6 illustrates an alternative embodiment in which infrastructure orchestration functions may subscribe to status updates from FDC / DP / FDN controllers. Operations 2 and 3 are performed periodically (i.e., FDC / DP / FDN availability and status changes or not are sent at a predefined periodicity). Alternatively, updates may be sent only in response to changes in FDC / DP / FDN availability and status. In embodiments in which infrastructure orchestration functions have up-to-date information regarding FDC / DP / FDC functions and status, operations 2 and 3 may be omitted from the logical node formation process.

[0074] In operation 4 of Figure 5, the infrastructure orchestration function selects and schedules FDC / DP / FDN functions, and generates a logical computing node structure and a logical computing node ID. The logical computing node structure may include: one or more central processing units and their identities / address spaces, one or more assisting processing units and their identities / address spaces, one or more memory devices and their identities / address spaces.

[0075] In operation 5, the infrastructure orchestration function sends a resource request to the FDC / DP / FDN controller. In operation 6, the FDC / DP / FDN controller then sends the assigned FDC / DP / FDN function index Along with In operation 7, the infrastructure orchestration function responds to the assigned FDC / DP / FDN function. Usage statusOperation 7 is particularly useful when there are multiple infrastructure orchestration function instances, e.g., in situations where there are conflicting resource requirements between multiple infrastructure orchestration function instances. The three-step process may prevent such conflicts. In operation 7, the confirmation message may also include configuration information to the FDC / DP / FDN function.

[0076] In operation 8, the FDC / DP / FDN controller configures the FDC / DP / FDN function after receiving the confirmation. In operation 9, the FDC / DP / FDN controller returns a configuration complete response indicating that the FDC / DP / FDN function has been configured. Along with , responding to infrastructure orchestration functions.

[0077] In operation 10, the infrastructure orchestration function responds to an infrastructure service consumer's infrastructure service request. The infrastructure service request response message to the infrastructure service request may include information regarding the allocated logical computing node structure, addresses, configuration, and node IDs.

[0078] In operation 11, the infrastructure service consumer executes a computing workload using the assigned logical computing nodes indicated by the infrastructure service request response. deployment and boot do.

[0079] Thus, the infrastructure service consumer requests logical computing node generation via the DCI service publishing function. The DCI service publishing function then forwards the generation request to the DCI infrastructure orchestrator. The DCI infrastructure orchestrator identifies a controller that can process the request and sends the request to the selected controller. The controller then identifies a DCI cluster that can hold the logical computing node and sends the generation request to the logical computing node. Once the logical computing node is generated, a completion message is sent back to the infrastructure service consumer. The controller will also register the generated logical computing node with the logical computing node. The completion message may include the specification of the generated logical computing node, logical computing node address information, and logical computing node administrator information.

[0080] 7 illustrates a logical computing node reconfiguration according to some embodiments. An infrastructure service consumer (operation 1a) or an infrastructure orchestration function (operation 1b) sends a reconfiguration request to an FDC / DP / FDN controller. The reconfiguration request may include configuration parameters. In operation 2, the FDC / DP / FDN controller configures the FDC / DP / FDN function based on the reconfiguration request. The FDC / DP / FDN controller then responds to the infrastructure orchestration function (operation 3a) or the infrastructure service consumer (operation 3b) indicating that the reconfiguration is completed.

[0081] 8 illustrates adding a new FDC / DP function to an existing logical computing node, according to some embodiments. An infrastructure orchestration function may decide in operation 0 to add one or more new FDC / DP / FDN functions to an existing logical computing node. The decision may result from one or more new workload requests or service requests, for example, from an infrastructure service consumer, or from telemetry and performance status reports from an FDC / DP / FDN controller.

[0082] The operations in Fig. 8 are similar to those in the logical computing node formation process. That is, in operation 1, the infrastructure orchestration function sends a resource request to the FDC / DP / FDN controller to add a new FDC / DP / FDN function. In operation 2, the FDC / DP / FDN controller then sends the allocated new FDC / DP / FDN function index to the FDC / DP / FDN controller. Along with In operation 3, the infrastructure orchestration function confirms use on the allocated new FDC / DP / FDN function. The confirmation message also includes configuration information for the new FDC / DP / FDN function. In operation 4, the FDC / DP / FDN controller configures the new FDC / DP / FDN function after receiving the confirmation. In operation 5, the FDC / DP / FDN controller returns a configuration complete response indicating that the new FDC / DP / FDN function has been configured. Along with , and responds to the infrastructure orchestration function.

[0083] 9 illustrates removing FDC / DP functionality from an existing logical computing node according to some embodiments. An infrastructure orchestration function may determine in operation 0 to remove one or more existing FDC / DP / FDN functionality from an existing logical computing node. The decision may result from one or more new workload requests or service requests, for example, from an infrastructure service consumer, or telemetry and performance status reports from an FDC / DP / FDN controller.

[0084] The operations in Fig. 9 are similar to those in the logical computing node formation process. That is, in operation 1, the infrastructure orchestration function sends a removal request to the FDC / DP / FDN controller to remove an existing FDC / DP / FDN function. The removal request may include information such as the targeted FDC / DP function ID and the updated logical node structure after removal. Alternatively or in addition, the removal request may include: FDC / DP controller, Decide which FDC / DP functions should be removed and how the logical compute nodes should be organized after removal. to make Therefore, the logical computing node Service goals related to In operation 2, the FDC / DP / FDN controller then interacts with the FDC / DP / FDN functionality to perform the removal operation and, if appropriate, reconfigures the remaining FDC / DP / FDN functionality. In operation 3, the FDC / DP / FDN controller returns a removal complete response indicating that the FDC / DP / FDN functionality has been removed. Along with , responding to infrastructure orchestration functions.

[0085] FIG. 10 illustrates logical computing node release, according to some embodiments. The infrastructure orchestration function may decide to remove an FDC / DP / FDN function from an existing logical computing node in operation 0. The decision may be based on, for example, a workload execution completion notification received from an infrastructure service consumer. Thus, in operation 1, the infrastructure orchestration function sends a release request to the FDC / DP / FDN controller to release the existing FDC / DP / FDN function. The release request may include information such as the targeted FDC / DP function ID and the updated logical node structure after removal. Alternatively or in addition, the release request may include: FDC / DP controller, Decide which FDC / DP functions to release and how to organize the logical computing nodes after release. to make For of , to the logical computing node Service goals related to In operation 2, the FDC / DP / FDN controller then interacts with the FDC / DP / FDN function to perform the release operation and reconfigures the remaining FDC / DP / FDN functions, if appropriate. In operation 3, the FDC / DP / FDN controller returns a release completion response indicating that the FDC / DP / FDN function has been released. Along with Response to infrastructure orchestration functions. Similar to Figure 9, in Figure 10, one or more of the various FDC / DP / FDN functions are removed / released from the existing logical computing nodes. However, in Figure 9, the logical computing nodes are retained, whereas in Figure 10, the logical computing nodes are removed (i.e., not retained in the orchestrator and controller records).

[0086] Although the embodiments have been described with reference to certain exemplary embodiments, it will be apparent that various modifications and changes may be made to these embodiments without departing from the broader scope of the present disclosure. Thus, the specification and drawings should be regarded in an illustrative and not restrictive sense. The accompanying drawings, which form a part of this application, show, by way of example and not limitation, specific embodiments in which the subject matter may be practiced. The illustrated embodiments are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of the present disclosure. Thus, this detailed description should not be construed in a limiting sense, and the scope of the various embodiments is defined solely by the appended claims, including the full scope of equivalents to which such claims are entitled.

[0087] The subject matter may be referred to herein by the term "embodiments", individually and / or collectively, merely for convenience and without the intention of intentionally limiting the scope of the present application to any single inventive concept when more than one inventive concept is actually disclosed. Thus, although multiple specific embodiments are shown and described herein, it should be understood that any configuration intended to achieve the same purpose may be substituted for the multiple specific embodiments shown. The present disclosure is intended to cover any and all adaptations or variations of the various embodiments. Combinations of the above embodiments, as well as other embodiments not specifically described herein, will be apparent to one of ordinary skill in the art upon reviewing the above description.

[0088] In this document, the terms "a" or "an" are used to include one or more than one, as is common in patent documents, independent of any other instances or uses of "at least one" or "one or more." In this document, the term "or" is used to refer to a non-exclusive, or "A or B" is used to include "A but not B," "B but not A," and "A and B," unless otherwise stated. In this document, the terms "including" and "in which" are used as the plain-language equivalents of the respective terms "comprising" and "wherein." Also, in the following claims, the terms "including" and "comprising" are open-ended, i.e., a system, UE, article, composition, formula, or process that includes multiple elements in addition to those recited after such terms in a claim is still considered to be within the scope of that claim. Moreover, in the following claims, the terms "first," "second," and "third," etc. are used merely as labels and are not intended to impose numerical requirements on their objects.

[0089] The Abstract of the present disclosure is provided in accordance with 37 C.FR §1.72(b), which requires that the Abstract enable the reader to quickly ascertain the nature of the technical disclosure. The Abstract is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the above Detailed Description, it may be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure should not be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter consists of less than all features of a single disclosed embodiment. Accordingly, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment. (Other possible items) (Item 1) Decode the function request from the infrastructure orchestration function, In a data-centric infrastructure (DCI), based on the function request, configure at least one of a function-dedicated computing (FDC) function, a data plane (DP) function, or a function-dedicated network (FDN) function; After configuration of the at least one of the FDC function, the DP function, or the FDN function, encode a response for transmission to the infrastructure orchestration function indicating completion of the function request. A processing circuit configured as described above; and a memory configured to store the function requests; A controller apparatus in a logical computing architecture comprising: (Item 2) the FDC function represents a physical computing unit; The DP function represents a physical data storage and sharing unit; The FDN function represents an interconnection network function executed on top of an optical network. Item 1. A controller device according to item 1. (Item 3) 2. The controller apparatus of claim 1, wherein the processing circuitry is further configured to collect telemetry data. (Item 4) 2. The controller apparatus of claim 1, wherein the processing circuitry is further configured to establish, maintain, and update logical computing nodes to meet service requirements through configuration of the at least one of the FDC function, the DP function, or the FDN function. (Item 5) To form a logical computing node in the DCI, the processing circuitry is further configured to decode computing and data resource discovery and status inquiry messages from the infrastructure orchestration function, the messages comprising: FDC feature type, amount, and duration, or Workloads and service requirements translated into said FDC function types, quantities, and durations 2. The controller apparatus of claim 1, wherein the request received by the infrastructure orchestration function includes information about the infrastructure orchestration function. (Item 6) The controller apparatus of item 5, wherein the processing circuitry is further configured to encode a response to the infrastructure orchestration function in response to receiving the message, the response indicating discovery resource availability and the status of FDC, DP, and FDN functions in the DCI to fulfill the FDC function type, amount, and duration for the creation of the logical computing node. (Item 7) the processing circuitry further decodes computing and data resource requests from the infrastructure orchestration function to implement the FDC, DP and FDN functions; 7. The controller apparatus of claim 6, configured to encode a computing and data resource response including an index of each of the FDC, DP and FDN functions for transmission to the infrastructure orchestration function in response to the computing and data resource request. (Item 8) 8. The controller apparatus of claim 7, wherein the processing circuitry is further configured to decode a confirmation of use of the FDC, DP, and FDN functions from the infrastructure orchestration function in response to the computing and data resource response, the confirmation being received in response to a resource request conflicting between multiple infrastructure orchestration function instances. (Item 9) In response to the computing and data resource request, the processing circuitry further: configuring said FDC, DP and FDN functions; and configured to encode a computing and data resource completion message indicating the completion of configuration of the FDC, DP, and FDN functions for transmission by the infrastructure orchestration function of the structure, addresses, configuration, and node identities of the logical computing nodes for transmission to the infrastructure orchestration function after completion of configuration of the FDC, DP, and FDN functions; 8. A controller device according to item 7. (Item 10) The processing circuitry further comprises: Decoding from the infrastructure orchestration function availability and status subscriptions of FDC, DP and FDN functions in the DCI; and 2. The controller apparatus of claim 1, configured to periodically encode the availability and status of FDC, DP and FDN functions in the DCI for transmission to the infrastructure orchestration function. (Item 11) To reconfigure logical computing nodes in the DCI, the processing circuitry further comprises: decode a reconfiguration request from one of an infrastructure service consumer or the infrastructure orchestration function, the reconfiguration request including reconfiguration parameters for the logical computing node; Reconstructing FDC, DP, and FDN functions based on the reconstruction parameters; and 2. The controller apparatus of claim 1, configured to encode a reconfiguration response indicating that reconfiguration of the logical computing node is complete for transmission to the one of the infrastructure service consumer or the infrastructure orchestration function. (Item 12) To add a logical computing node in the DCI to the at least one of the FDC function, DP function, or FDN function, the processing circuitry further: decode, based on at least one of a new workload or service request from an infrastructure service consumer or telemetry and performance status reports from the controller, an addition request from the infrastructure orchestration function to add the at least one of an FDC function, a DP function, or an FDN function; Adding the at least one of the FDC function, the DP function, or the FDN function based on the addition request; and 2. The controller apparatus of claim 1, configured to encode a completion message indicating that the addition of the at least one of the FDC function, DP function, or FDN function is complete for transmission to the infrastructure orchestration function after the addition of the at least one of the FDC function, DP function, or FDN function. (Item 13) To remove the at least one of the FDC functionality, the DP functionality, or the FDN functionality from a logical computing node in the DCI, the processing circuitry further comprises: decode, from the infrastructure orchestration function, a removal request to remove the at least one of the FDC function, DP function, or FDN function based on at least one of a new workload or service request from an infrastructure service consumer or telemetry and performance status reports from the controller; removing the at least one of the FDC function, the DP function, or the FDN function based on the removal request; and 2. The controller apparatus of claim 1, configured to encode, for transmission to the infrastructure orchestration function after removal of the at least one of the FDC function, the DP function, or the FDN function, a completion message indicating that the removal of the at least one of the FDC function, the DP function, or the FDN function is complete. (Item 14) Item 14. The controller apparatus of item 13, wherein the removal request comprises at least one of an identification of at least one of an FDC or DP function targeted for removal, or an updated logical node structure after completion of removal of the at least one of the FDC function, DP function, or FDN function. (Item 15) the removal request comprises a service goal on the logical computing node; Item 14. The controller apparatus of item 13, wherein the processing circuitry is further configured to determine which of the at least one of the FDC function, DP function, or FDN function should be removed and an organization of the logical computing node after completion of removal of the at least one of the FDC function, DP function, or FDN function. (Item 16) To release a logical computing node from the DCI, the processing circuitry further comprises: decode a release request from the infrastructure orchestration function to release the at least one of the FDC function, the DP function, or the FDN function based on a workload execution completion notification from an infrastructure service consumer; reconfiguring FDC, DP, and FDN functions based on the release request to release the at least one of the FDC function, DP function, or FDN function, and the logical computing node; and 2. The controller apparatus of claim 1, configured to encode a completion message indicating that the release of the at least one of the FDC function, DP function, or FDN function has been completed and the logical computing node has been released, for transmission to the infrastructure orchestration function after the release of the at least one of the FDC function, DP function, or FDN function. (Item 17) encoding, for transmission to a controller, a function request for at least one of forming or releasing a logical computing node in a data centric infrastructure (DCI) or for modifying the logical computing node by at least one of adding or removing at least one of a function dedicated computing (FDC) function, a data plane (DP) function, or a function dedicated network (FDN) function to the logical computing node; a processing circuit configured to, in response to transmitting the function request, decode a function response from the controller indicating completion of an operation performed by the controller with respect to the function request; and a memory configured to store the function requests; Infrastructure orchestration capabilities equipment. (Item 18) The processing circuitry: configured to decode an infrastructure service request for creating a logical computing node in the DCI from an infrastructure service consumer; The infrastructure service request: FDC feature type, amount, and duration, or With workload and service requirements; the processing circuitry, in response to determining that the infrastructure service request comprises the workload and service requirements, converts the workload and service requirements into the FDC function type, quantity, and duration; and 18. The infrastructure orchestration function of claim 17, configured to communicate with the controller such that the controller configures the at least one of the FDC, DP or FDN functions in the logical computing node to provide the FDC function type, amount, and duration. (Item 19) 2. A method for controlling a data-centric infrastructure (DCI) comprising: storing instructions for execution by one or more processors of a controller in a data-centric infrastructure (DCI), the one or more processors causing the instructions, when executed, to: Decode a function request for a logical compute node from an infrastructure orchestration function; Configure at least one of a function-dedicated computing (FDC) function, a data plane (DP) function, or a function-dedicated network (FDN) function in the logical computing node based on the function request; and configuring the controller, after configuration of the at least one of the FDC function, the DP function, or the FDN function, to encode a response for transmission to the infrastructure orchestration function indicating completion of the function request. A non-transitory computer-readable storage medium. (Item 20) the FDC function represents a physical computing unit; The DP function represents a physical data storage and sharing unit; The FDN function represents an interconnection network function that runs on top of an optical network; 20. The non-transitory computer-readable storage medium of item 19.

Claims

1. A controller device in a logical computing architecture, comprising: Receive a function request from an infrastructure orchestration function; Based on the function requirements, configure at least one of a function-dedicated computing (FDC) function, a data plane (DP) function, or a function-dedicated network (FDN) function in a data-centric infrastructure (DCI); sending a response to the infrastructure orchestration function indicating completion of the function request after configuration of the at least one of the FDC function, the DP function, or the FDN function. A processing circuit for configuring the apparatus so as to a memory configured to store the function requests; Equipped with In forming logical computing nodes in the DCI, the processing circuitry further configures the device to receive computing and data resource discovery and status inquiry messages from the infrastructure orchestration function, the messages varying according to requests received by the infrastructure orchestration function, the requests including: the type, amount, and duration of said FDC function; or Workload and service requirements to be translated into types, quantities, and durations of said FDC functions. Including information about the device.

2. the FDC function represents a physical computing unit; The DP facility represents a physical data storage and sharing unit; The FDN function represents an interconnection network function performed on top of an optical network.

2. The apparatus of claim 1.

3. The device of claim 1 , wherein the processing circuitry is further configured to collect telemetry data.

4. 2. The apparatus of claim 1, wherein the processing circuitry is further configured to establish, maintain, and update the logical computing nodes to meet service requirements through configuration of the at least one of the FDC function, the DP function, or the FDN function.

5. 2. The apparatus of claim 1, wherein the processing circuitry further configures the apparatus to send a response to the infrastructure orchestration function in response to receiving the message, the response indicating availability and status of resources of the FDC function, the DP function, and the FDN function in the DCI that fulfill a type, amount, and duration of the FDC function for the creation of the logical computing node.

6. the processing circuitry further receives, from the infrastructure orchestration function, computing and data resource requests for implementing the FDC function, the DP function, and the FDN function; The apparatus of claim 5, configured to send a computing and data resource response to the infrastructure orchestration function in response to the computing and data resource request, the computing and data resource response including an index of each of the FDC capability, the DP capability, and the FDN capability.

7. 7. The apparatus of claim 6, wherein the processing circuitry further configures the apparatus to receive from the infrastructure orchestration function a confirmation of utilization of the FDC function, the DP function, and the FDN function in response to the computing and data resource response, the confirmation being received in response to a resource request conflicting among multiple infrastructure orchestration function instances.

8. In response to the computing and data resource request, the processing circuitry further: configuring the FDC function, the DP function and the FDN function; and configuring the device such that after completion of configuration of the FDC function, the DP function, and the FDN function, the infrastructure orchestration function sends a computing and data resource completion message indicating the completion of configuration of the FDC function, the DP function, and the FDN function to the infrastructure orchestration function to transmit the structure, address, configuration, and node identity of the logical computing node; 7. The apparatus of claim 6.

9. The processing circuitry further comprises: Receive a subscription to the availability and status of the FDC function, the DP function, and the FDN function in the DCI from the infrastructure orchestration function; and The apparatus of claim 1 , configured to periodically transmit to the infrastructure orchestration function the availability and status of the FDC function, the DP function and the FDN function in the DCI.

10. A controller device in a logical computing architecture, comprising: Receive a function request from an infrastructure orchestration function; Based on the function requirements, configure at least one of a function-dedicated computing (FDC) function, a data plane (DP) function, or a function-dedicated network (FDN) function in a data-centric infrastructure (DCI); sending a response to the infrastructure orchestration function indicating completion of the function request after configuration of the at least one of the FDC function, the DP function, or the FDN function. A processing circuit for configuring the apparatus so as to a memory configured to store the function requests; Equipped with The processing circuitry further comprises: Receive a subscription to the availability and status of the FDC function, the DP function, and the FDN function in the DCI from the infrastructure orchestration function; and The device is configured to periodically transmit to the infrastructure orchestration function the availability and status of the FDC function, the DP function and the FDN function in the DCI.

11. In reconfiguring the logical computing nodes in the DCI, the processing circuitry further comprises: receiving a reconfiguration request from one of an infrastructure service consumer or the infrastructure orchestration function, the reconfiguration request including reconfiguration parameters for the logical computing node; reconfiguring the FDC function, the DP function, and the FDN function based on the reconfiguration parameters; and 9. The apparatus of claim 1, further comprising: a reconfiguration response to the one of the infrastructure service consumer or the infrastructure orchestration function indicating that a reconfiguration of the logical computing node is complete.

12. A controller device in a logical computing architecture, comprising: Receive a function request from an infrastructure orchestration function; Based on the function requirements, configure at least one of a function-dedicated computing (FDC) function, a data plane (DP) function, or a function-dedicated network (FDN) function in a data-centric infrastructure (DCI); sending a response to the infrastructure orchestration function indicating completion of the function request after configuration of the at least one of the FDC function, the DP function, or the FDN function. A processing circuit for configuring the apparatus so as to a memory configured to store the function requests; Equipped with In reconfiguring the logical computing nodes in the DCI, the processing circuitry further comprises: receiving a reconfiguration request from one of an infrastructure service consumer or the infrastructure orchestration function, the reconfiguration request including reconfiguration parameters for the logical computing node; reconfiguring the FDC function, the DP function, and the FDN function based on the reconfiguration parameters; and 23. The apparatus of claim 22, further comprising: an infrastructure service consumer configured to: transmit a reconfiguration response to the one of the infrastructure service consumer or the infrastructure orchestration function indicating that reconfiguration of the logical computing node is complete.

13. In adding the at least one of the FDC function, the DP function, or the FDN function to the logical computing node in the DCI, the processing circuitry further comprises: receiving an addition request from the infrastructure orchestration function to add the at least one of the FDC function, the DP function, or the FDN function based on at least one of a new workload or service request from an infrastructure service consumer or telemetry and performance status reports from the controller; Adding the at least one of the FDC function, the DP function, or the FDN function based on the addition request; and 9. The apparatus of claim 1, further comprising: after the addition of the at least one of the FDC function, the DP function, or the FDN function, the apparatus is configured to send a completion message to the infrastructure orchestration function indicating that the addition of the at least one of the FDC function, the DP function, or the FDN function is complete.

14. In removing the at least one of the FDC function, the DP function, or the FDN function from the logical computing node in the DCI, the processing circuitry further comprises: receiving, from the infrastructure orchestration function, a removal request to remove the at least one of the FDC function, the DP function, or the FDN function based on at least one of a new workload or service request from an infrastructure service consumer or telemetry and performance status reports from the controller; removing the at least one of the FDC function, the DP function, or the FDN function based on the removal request; and 9. The apparatus of claim 1, further comprising: after removal of the at least one of the FDC function, the DP function, or the FDN function, the apparatus is configured to send a completion message to the infrastructure orchestration function indicating that the removal of the at least one of the FDC function, the DP function, or the FDN function is complete.

15. 15. The apparatus of claim 14, wherein the removal request includes at least one of an identification of at least one of an FDC function, a DP function, or an FDN function targeted for removal, or an updated logical computing node structure after completion of removal of the at least one of the FDC function, the DP function, or the FDN function.

16. A controller device in a logical computing architecture, comprising: Receive a function request from an infrastructure orchestration function; Based on the function requirements, configure at least one of a function-dedicated computing (FDC) function, a data plane (DP) function, or a function-dedicated network (FDN) function in a data-centric infrastructure (DCI); sending a response to the infrastructure orchestration function indicating completion of the function request after configuration of the at least one of the FDC function, the DP function, or the FDN function. A processing circuit for configuring the apparatus so as to a memory configured to store the function requests; Equipped with In removing the at least one of the FDC function, the DP function, or the FDN function from a logical computing node in the DCI, the processing circuitry further comprises: receiving, from the infrastructure orchestration function, a removal request to remove the at least one of the FDC function, the DP function, or the FDN function based on at least one of a new workload or service request from an infrastructure service consumer or telemetry and performance status reports from the controller; removing the at least one of the FDC function, the DP function, or the FDN function based on the removal request; and configuring the apparatus to, after removal of the at least one of the FDC function, the DP function, or the FDN function, send a completion message to the infrastructure orchestration function indicating that the removal of the at least one of the FDC function, the DP function, or the FDN function is complete; 11. The apparatus of claim 1, wherein the removal request includes at least one of an identification of at least one of an FDC function, a DP function, or an FDN function targeted for removal, or an updated logical computing node structure after completion of removal of the at least one of the FDC function, the DP function, or the FDN function.

17. the removal request includes a service goal for the logical computing node; 15. The apparatus of claim 14, wherein the processing circuitry further configures the apparatus to determine which of the at least one of the FDC function, the DP function, or the FDN function should be removed and an organization of the logical computing nodes after completion of removal of the at least one of the FDC function, the DP function, or the FDN function.

18. A controller device in a logical computing architecture, comprising: Receive a function request from an infrastructure orchestration function; Based on the function requirements, configure at least one of a function-dedicated computing (FDC) function, a data plane (DP) function, or a function-dedicated network (FDN) function in a data-centric infrastructure (DCI); sending a response to the infrastructure orchestration function indicating completion of the function request after configuration of the at least one of the FDC function, the DP function, or the FDN function. A processing circuit for configuring the apparatus so as to a memory configured to store the function requests; Equipped with In removing the at least one of the FDC function, the DP function, or the FDN function from a logical computing node in the DCI, the processing circuitry further comprises: receiving, from the infrastructure orchestration function, a removal request to remove the at least one of the FDC function, the DP function, or the FDN function based on at least one of a new workload or service request from an infrastructure service consumer or telemetry and performance status reports from the controller; removing the at least one of the FDC function, the DP function, or the FDN function based on the removal request; and configuring the apparatus to, after removal of the at least one of the FDC function, the DP function, or the FDN function, send a completion message to the infrastructure orchestration function indicating that the removal of the at least one of the FDC function, the DP function, or the FDN function is complete; the removal request includes a service goal for the logical computing node; The processing circuitry further configures the device to determine which of the at least one of the FDC function, the DP function, or the FDN function should be removed and an organization of the logical computing nodes after completion of removal of the at least one of the FDC function, the DP function, or the FDN function.

19. In releasing the logical computing node from the DCI, the processing circuitry further comprises: receiving a release request from the infrastructure orchestration function to release the at least one of the FDC function, the DP function, or the FDN function based on a workload execution completion notification from an infrastructure service consumer; reconfiguring the FDC function, the DP function, and the FDN function based on the release request, and releasing the at least one of the FDC function, the DP function, or the FDN function and the logical computing node; and 2. The apparatus of claim 1, further configured to: after the release of the at least one of the FDC function, the DP function, or the FDN function, send a completion message to the infrastructure orchestration function indicating that the release of the at least one of the FDC function, the DP function, or the FDN function is complete and the logical computing node has been released.

20. An infrastructure orchestration function device, comprising: sending a function request to a controller for at least one of creating or releasing a logical computing node in a data-centric infrastructure (DCI) or modifying the logical computing node by at least one of adding or removing at least one of a function-dedicated computing (FDC) function, a data plane (DP) function, or a function-dedicated network (FDN) function to the logical computing node; a processing circuit further configuring the apparatus to: receive, in response to sending the function request, from the controller a function response indicating completion of an operation associated with the function request performed by the controller; and a memory configured to store the function request; The processing circuitry further comprises: configured to receive an infrastructure service request from an infrastructure service consumer to create the logical computing node in the DCI; The infrastructure service request: the type, amount, and duration of said FDC function; or Includes workload and service requirements, the processing circuitry, in response to determining that the infrastructure service request includes the workload and service requirements, converts the workload and service requirements into a type, amount, and duration of the FDC function; and the controller configures the at least one of the FDC function, the DP function, or the FDN function in the logical computing node to configure the device to communicate with the controller to provide a type, amount, and duration of the FDC function; Device.

21. In a data-centric infrastructure (DCI), one or more processors of a controller receiving a function request for a logical compute node from an infrastructure orchestration function; configuring at least one of a function-dedicated computing (FDC) function, a data plane (DP) function, or a function-dedicated network (FDN) function in the logical computing node based on the function request; and sending a response to the infrastructure orchestration function indicating completion of the function request after configuration of the at least one of the FDC function, the DP function, or the FDN function. A computer program comprising: The computer program further causes the one or more processors, in forming the logical computing nodes in the DCI, to execute a procedure for receiving computing and data resource discovery and status inquiry messages from the infrastructure orchestration function, the messages varying according to requests received by the infrastructure orchestration function, the requests including: the type, amount, and duration of said FDC function; or Workload and service requirements to be translated into the type, amount, and duration of said FDC functions A computer program containing information about.

22. the FDC function represents a physical computing unit; The DP facility represents a physical data storage and sharing unit; The FDN function represents an interconnection network function that runs on top of an optical network.

22. A computer program according to claim 21.

23. A non-transitory computer readable storage medium storing a computer program according to claim 21 or 22.

Images