202a or 202b can include tests designed to components and functionalities within the specific cell site, functionalities with another cell site (e.g., adjacency testing), and/or end-to tend testing.

In various embodiments, the RAN shown in this example is implemented using software and is configured to test and ensure one or more O-RAN components (e.g., the RRU or CSR, in the cell sites are performing in compliance with O-RAN standards). Various tests or test suites can be configured into a RAN to cause target components in the cell sites to be run under preset test conditions. A goal of such a test or test suite in the RAN is to verify that individual components in the cell sites can handle expected traffic and functionality. In some embodiments, tests in the RAN are run continuously on a preset or configured frequency to ensure the above-mentioned types of testing of the specific cell sites are in compliance with the O-RAN standards continuously.

As shown FIG. 2, the cell sites 202a and 202b are connected, via the transport layer 206, to a data center 204 configured to host one or more CUs, and one or more UPFs (user plane functions) implementing at least one user plane layer, and/or any other components. In one embodiment, the data center 204 is referred to as a breakout edge data center (BEDC). In general, the data center 204 is configured to accommodate the distributed nature of various functions in the example system architecture 200 of a 5G O-RAN. In that embodiment, the BEDC hosts various 5G network functions (NFs) that have low latency requirement. In that embodiment, the BEDC provides internet peering for general 5G service and enterprise customer-specific private network service.

Shown in this example is a storage 2042 configured to store various (Cloud-native Network Functions) CNFs and artifacts for facilitating implementations of the DUs and CUs in the example system architecture 200 of the 5G O-RAN. Examples of the storage 2042 can include Amazon S3, GitHub, Harbor and/or any other storage services.

In some embodiments, such as shown in FIG. 2, the data center 204 can include one or more Kubernetes (also known as K8S) configured to facilitate automation of deployment, scaling, and management of various software/applications deployed within the data center 204 and/or within one or more cell sites operatively communicating with the data center 204 through the transport layer 206.

5G Core 208 can be implemented such that it is physically distributed across data centers or located at a central national data center (NDC) and/or regional data center (RDC). In this example, 5G core 208 performs various core functions of the 5G network. In implementations, 5G core 208 can include an O-RAN core implementing various 5G services and/or functions such as: network resource management components; policy management components; subscriber management components; packet control components; and/or any other 5G functions or services. Individual components may communicate on a bus, thus allowing various components of 5G core 208 to communicate with each other directly. Implementations 5G core 208 can involve additional other components.

Network resource management components can include: Network Repository Function (NRF) and Network Slice Selection Function (NSSF). NRF can allow 5G network functions (NFs) to register and discover each other via a standards-based application programming interface (API). NSSF can be used by AMF to assist with the selection of a network slice that will serve a particular UE.

Policy management components can include: Charging Function (CHF) and Policy Control Function (PCF). CHF allows charging services to be offered to authorized network functions. A converged online and offline charging can be supported. PCF allows for policy control functions and the related 5G signaling interfaces to be supported.

Subscriber management components can include: Unified Data Management (UDM) and Authentication Server Function (AUSF). UDM can allow for generation of authentication vectors, user identification handling, NF registration management, and retrieval of UE individual subscription data for slice selection. AUSF performs authentication with UE.

Packet control components can include: Access and Mobility Management Function (AMF) and Session Management Function (SMF). AMF can receive connection and session related information from UE and is responsible for handling connection and mobility management tasks. SMF is responsible for interacting with the decoupled data plane, creating updating and removing Protocol Data Unit (PDU) sessions, and managing session context with the User Plane Function (UPF).

In one O-RAN implementation, DUs, CUs, 5G core 208 and/or any other components in that O-RAN, is implemented virtually as software being executed by general-purpose computing equipment, such as those in one or more data centers. Therefore, depending on needs, the functionality of a DU, CU, and/or 5G 208 core may be implemented locally to each other and/or specific functions of any given component can be performed by physically separated server systems (e.g., at different server farms). For example, some functions of a CU may be located at a same server facility as where the DU is executed, while other functions are executed at a separate server system. In some embodiments, DUs may be partially or fully added to cloud-based cellular network components. Such cloud-based cellular network components may be executed as specialized software executed by underlying general-purpose computer servers. Cloud-based cellular network components may be executed on a third-party cloud-based computing platform. For instance, a separate entity that provides a cloud-based computing platform may have the ability to devote additional hardware resources to cloud-based cellular network components or implement additional instances of such components when requested.

In implementations, Kubernetes (K8S), or some other container orchestration platform, can be used to create and destroy the logical DU, CU, 5G core units and subunits as needed for the O-RAN to function properly. Kubernetes allows for container deployment, scaling, and management. As an example, if cellular traffic increases substantially in a region, an additional logical DU or components of a DU may be deployed in a data center near where the traffic is occurring without any new hardware being deployed. (Rather, processing and storage capabilities of the data center would be devoted to the needed functions.) When the need for the logical DU or subcomponents of the DU is no longer needed, Kubernetes can allow for removal of the logical DU. Kubernetes can also be used to control the flow of data (e.g., messages) and inject a flow of data to various components. This arrangement can allow for the modification of nominal behavior of various layers.

In implementations, the deployment, scaling, and management of such virtualized components can be managed by an orchestrator (such as Kubernetes) in the 5G core 208. The orchestrator can trigger various software processes executed by underlying computer hardware. In implementations, the one or more management functions (managing the 5G core 208, and/or the example system architecture 200 in general) can be implemented in the 5G core 208, for example through a M-Plane. The M-Plane can be configured to facilitate monitoring of O-RAN and determining the amount and location at which cellular network functions should be deployed to meet or attempt to meet service level agreements (SLAs) across slices of the cellular network.

In various implementations, the orchestrator can allow for the instantiation of new cloud-based components of the example system architecture 200 of the 5G O-RAN. As an example, to instantiate a new DU, the orchestrator can perform a pipeline of calling the DU code from a software repository incorporated as part of, or separate from, cellular network 120; pulling corresponding configuration files (e.g., helm charts); creating Kubernetes nodes/pods; loading DU containers; configuring the DU; and activating other support functions (e.g., Prometheus, instances/connections to test tools).

In some implementations, a network slice functions as a virtual network operating on example system architecture 200 of the 5G O-RAN. In those implementations, example system architecture 200 of the 5G O-RAN is shared with some number of other network slices, such as hundreds or thousands of network slices. Communication bandwidth and computing resources of the underlying physical network can be reserved for individual network slices, thus allowing the individual network slices to reliably meet particular SLA levels and parameters. By controlling the location and amount of computing and communication resources allocated to a network slice, the SLA attributes for UE on the network slice can be varied on different slices. A network slice can be configured to provide sufficient resources for a particular application to be properly executed and delivered (e.g., gaming services, video services, voice services, location services, sensor reporting services, data services, etc.). However, resources are not infinite, so allocation of an excess of resources to a particular UE group and/or application may be desired to be avoided. Further, a cost may be attached to cellular slices: the greater the amount of resources dedicated, the greater the cost to the user; thus optimization between performance and cost is desirable.

Particular network slices may only be reserved in particular geographic regions. For instance, a first set of network slices may be present at a given RU and a given DU, a second set of network slices, which may only partially overlap or may be wholly different than the first set, may be reserved at the given RU and the given DU.

Further, particular cellular network slices may include some number of defined layers. Each layer within a network slice may be used to define QoS parameters and other network configurations for particular types of data. For instance, high-priority data sent by a UE may be mapped to a layer having relatively higher QoS parameters and network configurations than lower-priority data sent by the UE that is mapped to a second layer having relatively less stringent QoS parameters and different network configurations.

In some embodiments, the 5G core 208 implements a O-RAN ZTP (zero touch provisioning) layer. In general, in those embodiments, the O-RAN ZTP layer is configured to facilitate automation of the deployment workflow within the example system architecture 200 of the 5G O-RAN. ZTP is commonly known as automated deployment of software (new or updates) to various components in a system with as little human intervention as possible. In the context of example system architecture 200 of the 5G O-RAN, ZTP means automated deployment of software (new or updates) to hardware and/or software components such as RUS, CSRs, DUs, CUs, and various modules in the 5G core 208 with little human intervention.

For example, without an engineer having to be present at a specific cell site such as 202a or 202b, O-RAN ZTP can facilitate automatic updates of an RU with the latest RU software, updates of a DU with the latest DU software and/or changing from one vendor's RU/DU to another vendor's RU/DU. It should be understood the O-RAN ZTP layer is referred to a set of components that work together to facilitate automatic deployment of software in the example system architecture 200 of the 5G O-RAN with little human intervention. Thus, although, the O-RAN ZTP layer is shown being implemented in the 5G core 208 in FIG. 2, it is merely illustrative. That is, the O-RAN ZTP in accordance with the present disclosure is not intended to be limited to components implemented a core of the O-RAN in accordance with the present disclosure. In some other examples, one or more components of the O-RAN ZTP can be implemented in, for example, CUs or DUs in the O-RAN in accordance with the present disclosure. For instance, as will be described below, adaptors configured to communicate with devices or components of different vendors for ZTP operations can be implemented in CUs or DUs.

Also shown in FIG. 2 is a NOC 210 (Network Operation Center). In some embodiments, the NOC 210 is implemented on a general-purpose computing device. In those embodiments, one or more interfaces are implemented in the NOC 210. In those embodiments, the interfaces represent virtual dashboards that can facilitate automatic deployment of software to various components in the example system architecture 200 of the 5G O-RAN. For instance, an interface is provided in the NOC 210 to enable an operator to initiate on or more BOTs 212 to automate the performance of health check tasks, as described herein. The NOC 210 can also be used by an operator to set a schedule to update one or more network services in the 5G core 208. As another illustration, an interface is provided in the NOC 210 to enable the operator to push software to a specific component in a cell site (such as 202a or 202b) or in a data center (such as 204) to configure or update the component. As another example, an interface is provided in the NOC 210 to enable an operator to provision one or more C-RAN components.

One or more requests can be generated by the NOC 210 to instigate the deployment of the software as scheduled or intended by the operator. The request(s) can be received by the O-RAN ZTP layer, which in turn can generate one or more commands to deploy the software to the component. Although one NOC 210 is shown in this example, this is not intended to be limiting. More than one NOCs are typically deployed in the example system architecture 200 of the 5G O-RAN. In some implementations, a given NOC may be provided by a vendor to the 5G O-RAN. For instance, the vendor may be a software develop that provides components or services to the example system architecture 200 of a 5G O-RAN. In that instance, the given NOC is a computing device or system on a premise of the software developer.

Components such as RUs, DUs, CUs, the orchestrator, O-RAN ZTP layer, interfaces in the NOC 210, and/or any other components in the 5G core 208 may include various software components communicating with each other, handling large volumes of data traffic, and be able to properly respond to changes in the network. In order to ensure not only the functionality and interoperability of such components, but also the ability to respond to changing network conditions and the ability to meet or perform above vendor specifications, significant testing must be performed.

Example Hybrid Cellular Network System

FIG. 3 illustrates an embodiment of hybrid cellular network system 300 that includes hybrid use of local and remote DUs in communication with a cloud computing platform that hosts the cellular network core. System 300 can include: local data center (LDC) 311; cloud radio access networks (CRANs 355), which may also be referred to herein as light BSs 355; distributed radio access networks (DRANs 318)), which may also be referred to herein as full BSs 318; VLAN connections 320; edge data center (EDC) 330; CU 129; and 5G core 139, which are executed on cloud computing platform 128. In system 300, some base stations, referred to as DRAN or “full base stations,” have DUs implemented locally at each BS. In contrast, a CRAN is a “light base station” that includes structure (e.g., structures 355) and a local radio unit (e.g., RUs 350), but a DU implemented remotely at a geographically separated LDC. In system 300, either CRAN/light BSs 355 or DRAN/full BSs 318 may be referred to as a cell site.

LDC 311 can serve to host DU host server system 329, which can host multiple DUs 331 which are remote from corresponding light base stations 355. For example, DU 331-1 can perform the DU functionality for light base station 355-1. DUs with DU host server system 329 can communicate with each other as needed.

LDC 311 can be connected with EDC 330. In some embodiments, LDC 370 and EDC 330 may be co-located in a same data center or are relatively near each other, such as within 250 meters. EDC 330 can include multiple routers, such as routers 335, and can serve as a hub for multiple DRANs 318 and one or more LDCs 311. EDC 330 may be so named because it primarily handles the routing of data and does not host any RAN or cellular core functions. In a cloud-computing cellular network implementation at least some components, such as CU 129 and functions of 5G core 139, may be hosted on cloud computing platform 128. EDC 330 may serve as the past point over which the cellular network operator maintains physical control; higher-level functions of CU 129 and 5G core 139 can be executed in the cloud. In other embodiments, CU 129 and 5G core 139 may be hosted using hardware maintained by the cellular network provider, which may be in the same or a different data center from EDC 330.

DRANs 318, which include on-site DUs 316, may connect with the cellular network through EDC 330. A DRAN, such as DRAN 318-1, can include: RU 313-1; router 335-1; DU 316-1; and structure 323-1. Router 335-1 may have a connection to a high bandwidth communication link with EDC 330. Router 335-1 may route data between DU 316-1 and EDC 330 and between DU 316-1 and RU 313-1. In some embodiments, RU 313-1 and one or more antennas are mounted to structure 323-1, while router 335-1 and DU 316-1 are housed at a base of structure 323-1. DRAN 318-2 functions similarly to DRAN 318-1. While two DRANs 318 and two CRANs 355 are illustrated in FIG. 3, it should be understood that these numbers of BSs are merely for exemplary purposes; in other embodiments, the number of each type of BS may be greater or fewer.

While encoded radio data is transmitted via the fiber optic connections 340 between CRANs 355 and LDC 370, connection 320-1 between DRAN 318 and EDC 330 may occur over a fiber network. For example, while the connection between CRANs BS 355-1 and LDC 370 can be understood as a dedicated point-to-point communication link on which addressing is not necessary, DRAN 318-1 may operate on a fiber network on which addressing is required. Multiprotocol label switching (MPLS) segment routing (SR) may be used to perform routing over a network (e.g., fiber optic network) between DRAN 318-1 and EDC 330. Such segment routing can allow for network nodes to steer packetized data based on a list of instructions carried in the packet header. This arrangement allows for the source from where the packet originated to define a route through one or more nodes that will be taken to cause the packet to arrive at its destination. Use of SR can help ensure network performance guarantees and can allow for network resources to be efficiently used. Other DRANs may use the same types of communication link as DRAN 318-1. While MPLS SR can be used for the network connection between DRANs 318 and EDC 330, it should be understood that other protocols and non-fiber-based networks can be used for connections 320.

For communications across connection 320-1, a virtual local area network (VLAN) may be established between DU 316-1 and EDC 330, when a fiber network that may also be used by other entities is used. The encryption of this VLAN helps ensure the security of the data transmitted over the fiber network.

Since CRANs 355 are relatively close to LDC 370, typically in a dense urban environment, use of a dedicated point-to-point fiber connection can be relatively straight-forward to install or obtain (e.g., from a network provider that has available dark fiber or fiber on which bandwidth can be reserved). However, in a less dense environment, where DRANs 318 can be used, a point-to-point fiber connection may be cost-prohibitive or otherwise unavailable. As such, the fiber network on which MPLS SR is performed and the VLAN connection is established can be used instead. Further, the total amount of upstream and/or downstream data from a CRAN to an LDC may be significantly greater than the amount of upstream and/or downstream data from a DU of a DRAN to EDC 337, thus requiring a dedicated fiber optic connection to satisfy the bandwidth requirements of CRANs.

Real-world implementations of system 300 can include many (e.g., thousands) of BSs and many CUs. BSs can include one or more antennas that allow RUs to communicate wirelessly with UEs (not shown). RUs can represent an edge of cellular network where data is transitioned to RF for wireless communication. The radio access technology (RAT) used by an RU may be 5G NR, or some other RAT.

Example System to Facilitate C-RAN Using ZTP Operations

FIG. 4 illustrates an example system 400 that can facilitate C-RAN operations within a telecommunication network, such as the ones shown in FIG. 1, FIG. 2, or FIG. 3, in accordance with some embodiments. In this example, the system 400 includes a site management component 414, an inventory management component 404, a workflow engine 402, a workflow management component 406, a network management component 408, a user interface 410, a validation engine 412, and/or any other components. As also shown, the various components in the example system 400 are operable to communicate with individual cell sites 416A, 416B, 416C, 416N.

In various embodiments, the site management component 414 is configured to manage hardware and/or software deployed at each individual cell site, for example 416A, 416B, 416C, 416N. In some embodiments, the site management component 414 is configured to configure hardware on individual cell sites according to instructions provided to the site management component 414. In some embodiments, the site management component 414 is configured to boot strap network devices, upgrade network operating system (NOS), configure VLANS across the individual cell sites, and perform operations relating to C-RAN provisioning. According to some configurations, the site management component 414 may include one or more BOTs that are configured to automatically perform one or more RU tasks. In some embodiments, the site management component 414 is configured to connect servers or hosts via selected network topology across the individual cell sites. In some embodiments, the site management component 414 is configured to deploy virtual infrastructure management (VIM) into a workload-ready state. In some embodiments, the site management component 414 comprises a bare metal orchestrator (BMO) provided by Dell.

In various embodiments, the site management component 414 is configured to manage and/or distribute workloads and/or data to individual cell sites. In some embodiments, the site management component 414 is configured to onboard, view, and manage a virtual infrastructure across the individual cell sites. In some embodiments, the site management component 414 comprises Telco Cloud Automation (TCA) orchestrator provided by VMWare.

In various embodiments, the inventory management component 404 is configured to facilitate dynamic network inventory for one or more networks provided by the individual cell sites. In some embodiments, the inventory management component 404 provides a comprehensive, end-to-end view of the resources to plan the deployment of new infrastructure for the individual cell sites and as well as to manage capacity. This facilitates delivering dynamic services like 5G, including network slicing. In some embodiments, the inventory management component 404 is configured to provide a unified, dynamic view of hybrid resources and services across multiple domains to streamline operations and reduce complexity. In those embodiments, the inventory management component 404 provides auto-discovery and federation capabilities using graph database technology to model and visualize complex, dynamic networks, enabling automated workflows, such as the ZTP workflows. In some embodiments, the inventory management component 404 comprises a Blue Planet Inventory (BPI) system provided by Blueplanet.

In various embodiments, the workflow engine 402 is configured to facilitate ZTP operations in one or more workflows to be carried out across the cell sites and/or on a core network. The workflow may involve automating one or more jobs to set up and/or verify one or more components on the core network to be ready for deploying network functionalities on the core network. The workflow may involve setting up one or more servers on the core network and/or in the individual cell sites for cell site deployment. The workflow may involve pushing software to update one or more components in the cell sites, and/or any other operations. The workflow may involve changing from using components provided by one vendor to another vendor. In various embodiments, the workflow engine 402 comprises a Cisco Business Process Automation Service (BPA).

In various embodiments, the workflow management component 406 is configured to manage one or more workflows to be carried out by the workflow engine 402. The workflow management by the workflow management component 406 may involve managing a workflow for configuring one or more servers on the core network, one or more distributed units (DU) in the core network, one or more radio access network (RAN) in the individual cell sites, one or more virtual clusters in the core network, one or more network functions in the core network, performing RAN vendor swapping, C-RAN provisioning workflows, and/or any other workflows.

In various embodiments, the network management component 406 is configured to manage one or more network components and/or devices on a core network. The network management may involve managing and identifying devices connected to the core network—for example, for the Domain Name System (DNS), Dynamic Host Configuration Protocol (DHCP), IP address management (collectively, “DDI”), and/or any other services. The network management may involve reserving and/or assigning one or more internet/intranet addresses for one or more components in the core network and/or individual cell sites. In various embodiments, the network management component comprises a system provided by Infoblox.

In various embodiments, the user interface 410 is provided to facilitate a user to monitor a progress of different operations. For example, the user interface 410 may be used to view data associated with one more RU tasks performed by one or mor BOTs. The user interface 410 may also bue used to view data associated with ZTP operations facilitated by the workflow engine 402, verify one or more results of the workflow managed by the workflow management component 406, check one or more statuses of individual cell sites, check a status of a network function on the core network, and/or any other services. In various embodiments, the user interface 410 includes a graphical user interface (GUI) depicting information about components (e.g., RUs, DUs, CSRs, . . . ) across one or more sites, a success/failure of a ZTP operation or workflow carried out to an individual cell sites, and/or whether or there is an issue with the ZTP operation and/or the workflow.

The validation engine 412 is configured to perform one or more validation tasks for the ZTP operations facilitated by the workflow engine 402. The validation may involve validating whether one or more servers are ready on the core network for deploying individual cell sites, validating whether one or more DU/RAN are deployable before their deployment, validating operations performed during deployment, validating connections, and/or validating whether they are ready after their deployment.

In some examples, checks/validations are performed for workflows associated with RU workflows, computer host provisioning (CHP) workflows, virtual server management provisioning (VSMP) workflows (e.g., VMware vCenter provisioning (VCP)), node-pool creation (NPC) workflows, distributed unit instantiation (DUI) workflows, radio access network (RAN) initiation workflows, RAN swapping workflows, C-RAN workflows, and/or other workflows For instance, for a CHP workflow, checks may be performed to ensure that data is ready for a CHP. As used herein, CHP may be referred to as provisioning a hardware server. For instance, individual CHPs available for the core network may be provided by different manufacturer such that the core network may be regarded as a hybrid cloud network. In that instance, provisioning a particular CHP may involve following provisioning procedures for that CHP as provided by a manufacturer of that CHP.

In that instance, a validation according to the provisioning procedures for that CHP may be performed as part of a Pre-CHP provisioning for that CHP. In various embodiments, this validation may involve collecting data from the workflow engine 302, the network management component 308, the site management component 314, the inventory management component 304, and/or any other components. For instance, for setting the particular CHP, information regarding the CHP should be ready in the network management component, one or more software should be ready in the inventory management component for deployment for that CHP, and/or any other checks. In some examples, when switching from one vendor to another, a different CHP provisioning workflow may be performed (e.g., provision a first type of computer host for one vendor and a second type of computer host for another vendor).

In various embodiments, different validation flows may be implemented for different ZTP operations and/or ZTP workflow. As mentioned above, in various embodiments, pre-CHP and post-CHP validation flows are implemented to facilitate CHP on the core network and/or in the individual cell sites. In various embodiments, a pre-site management component and post site management component validation flows are implemented to facilitate site management component provisioning in the example system 100. In various embodiments, a post cloud service router (CSR) validation is performed to facilitate CSR provisioning. As used herein, a CSR may be referred to one or more components enabling routing, VPN, Firewall, High-Availability, IP SLA, AVC, WAN Opt, and/or any other network services on the core network and/or in the individual cell sites. In various embodiments, a post DU and a port RAN validation are performed to facilitate DU and RAN provisioning.

FIG. 5A illustrates an example process 500 for setting up, provisioning, and operating a O-RAN such as the example system architectures of an 5G O-RAN shown in FIGS. 1-3. In the process 500, O-RAN ZTP technologies are employed to facilitate each step in the process 500. According to some configurations, a ZTP orchestrator (ZTPO) such as workflow engine 402 and/or workflow management component 406 manages different ZTP workflows. The example process 500 is shown to help understand how the O-RAN ZTP technologies in accordance with the present disclosure helps running of an O-RAN in accordance with the present disclosure. It should be understood the steps shown in FIG. 5A, while sequential, is not intended to be limited to the specific sequence shown in FIG. 5A. In some other examples, relevant sequences for the process 500 may be different from that shown in FIG. 5A.

In some examples, the ZTPO can use various ZTP technologies in an O-RAN to 1) install/update/swap network hardware components (such as RUs) in cell sites, 2) install/update/swap network functionality components (such as DUs, CUs, orchestrator, and/or any other networking components in the O-RAN) in data centers, and/or any other operations without someone needing to configure those components locally where they are located. For example, a new or replacement device can be sent to a cell site, physically installed and powered up by a locally present employee, who is not required to have IT skills. In some examples, the replacement devices can be from different vendors that are configured to operate in the O-RAN. This is when the ZTPO can use ZTP technologies to automatically carry out the software installation, updates, the configuration of the device, and connect the device to the O-RAN.

In the example process 500 for setting up, provisioning, and operating an O-RAN in accordance with the present disclosure, at electronic processor 502, a network environment is typically set up. At 502, operations such as setting up various network function components (for example, those mentioned above) in one or more data centers is performed to facilitate the operation of the O-RAN. For example, this may involve implementing network function components according to one or more design specifications for the O-RAN, pre-CSR integration of the various network function components, emulating DUs for the O-RAN for setting up the network environment using the various network function components, implementing one or more transport tools, and/or any other operations. During this stage, a ZTP layer can be implemented, for example such as the O-RAN ZTP layer shown in FIG. 2.

At 504, a cell site can be set up in the network environment set up at 502. For example, in the 5G context shown in FIG. 2, this may involve installing one or more RUs in the cell site, laying cables in the cell site, configurating one or more CSRs for the cell sites, making connections from the RUs to the CSRs, making connections from the cell site to a core network in the network environment, making connections between the cell site and any other cell sites, and/or any other operations. During this stage, functions or services can be automatically provisioned or commissioned on various components.

For instance, after an RU device is installed in the cell site (such as cell site 202a or 202b shown in FIG. 2) and powered up for the first time, a communication address can be automatically assigned to the RU device. Then, a BOT, or some other component in the O-RAN ZTP layer can automatically configure the RU device through the communication address assigned to the RU device. For example, a BOT can connect to a CSR at a site that is connected to the RU and can obtain the assigned communication address, obtain the MAC address (e.g., from the RU and/or from the inventory management 404 component), determine a current software version for the RU, determine whether to update the current RU software to a new version, reboot the RU, perform one or more health checks for the RU, and update data associated with the RU within one or more components, such as within inventory management component 404. As another example, a CSR implemented in the cell site can be automatically integrated into the network environment according to a network specification configured with the O-RAN ZTP layer after the CSR is ready to function in the network environment. A BOT may also perform one or more other health checks to determine whether the installed components of the cell site are operating correctly. For example, a BOT, such as BOT 212 may perform one or more connectivity tests between different components of the cell site and/or connection between one or more components of the cell site and one or more components external to the cell site.

At 506, continuous integration and continuous deployment (CI/CD) of various network function components are carried out in the network environment set up at 502. CI/CD is a set of practices that enable how software, in this case, O-RAN software, is installed and updated. CI or Continuous Integration is the practice of merging all developers working code to a shared mainline several times at a frequency. Every merge is typically validated before merging to uncover any issues. CD or Continuous Delivery/Deployment is the practice in which software developers produce reliable software in short cycles that can be released (delivered) at any time, which can then be deployed at a frequency. As a result, any software can be released much faster, more frequently and reliably into O-RAN. The benefit of CD is more predictable deployments that can happen on demand without waiting for an “official” upgrade cycle—this is now thing of the past.

Examples of CI/CD at 506 can include infrastructure deployment or update including the following components: networking stack, computing stack, storage stack, monitoring stack, security stack, core network functions. In some embodiments, the CI/CD at 506 can include Cloud-Native Network Functions (CNF) deployment and update. For instance, a CNF is deployed onto one or more CUs using control tools. In some embodiments, the CI/CD at 506 can include deploying a specific application or tool for a specific CNF. In some embodiments, changes to various network function components are deployed in the network environment continuously. In implementations, a ZTP workflow is used to facilitate the aforementioned CI/CD operations. In some configurations, the ZTP workflow is deployed within the O-RAN ZTP layer shown in FIG. 2. In that implementation, the ZTP workflow defines various stages through which software code is retrieved from a source code repository, is built into corresponding artifacts (e.g., micro-services, network functions), is tested using predefine tests, and is deployed in the network environment after successful results of the testing.

At 508, a cell site is updated, for example, with latest software or configuration. This may be triggered at a preset frequency configured at the ZTP layer in the network environment. For instance, a cadence such as every week may be set to update software deployed on the components in the cell site, such as RUs, DUs, CSRs, and/or any other components. In some examples, one or more BOTs configured to perform health check tasks is configured to run on a predetermined schedule and/or in response to some other condition. Running the BOT helps to ensure that components installed at a cell site are operating correctly.

Operations at 508 can also involve configuring or provisioning devices or components newly installed in the cell site—e.g., replacement or new devices. In some examples, the operations at 508 can involve swapping one or devices or components provided by one vendor to devices or components provided by another vendor. Similar to operations at 504, in such situations, software can be pushed to the newly installed devices or components by the ZTP layer once they are live in the network environment.

In implementations, operations involved in 504 may be referred to as “day 0” operations. Operations involved in 502 may be referred to as “day 1” operations. Operations involved in 506 may be referred to as “day 2” operations. Operations involved in 508 may be referred to as “day 3” operations. The numerical references in these operations do not necessarily indicate that these operations have to happen in a time sequence. As shown in FIG. 5A, operations in the example process 500 can happen in any sequence. For example, after a day “0” operation in 504 happens, the process 500 can proceed to 502 to push a specific configuration that involves components in the “day 0” operation to a core network (such as the 5G core 208 shown in FIG. 2), and then proceed to 508 to update another cell site (e.g., to configure that cell site to be connected to the cell site set up in the day 0 operation). Other scenarios are contemplated. According to some examples, the workflow engine 502 can orchestrate deployment of cell sites in parallel. For instance, the workflow engine 502 may coordinate the ZTPO workflows for the deployment of two, three, ten, a hundred cell sites, and the like at the same time.

FIG. 5B illustrates another example process 550 showing an example of how ZTP and CI/CD are facilitated in an O-RAN in accordance with the present disclosure. Process 550 illustrates the ZTP and CI/CD in the O-RAN in accordance with the present disclosure from a perspective of O-RAN operation cycles.

At 552, an activity or operation at a cell site triggers an automation in the ZTP layer of the O-RAN. For example, this may involve a replacement of a RU device in the cell site is brought online by a personnel present at the cell site. Once the RU device is online, a BOT may determine that the RU device needs a software update and/or the RU device may generate a request for software update, e.g., security patch, and configuration of the RU device, and such a request may be received by the ZTPO in the ZTP layer in the O-RAN. In some embodiments, the ZTPO in the ZTP layer may be configured to monitor activities across cell sites in the network environment and the automation is triggered by the ZTPO once the replacement RU device is detected to be online.

At 554, lower-level network (e.g., radio network or RAN) CI/CD can be carried out. In some situations, the operations in 554 are triggered by one or more activities at 552. For example, as illustration, after the replacement RU device is brought online and configured by the ZTP layer in the O-RAN, one or more components in a CSR, DU and/or CU is to be configured to record the replacement RU device. In that example, the ZTP layer in the O-RAN can trigger such a configuration so the lower-level network is updated to incorporate the replacement RU into the O-RAN. In some situations, the lower-level network CI/CD at 554 is independent of the activities at cell sites. For instance, the software developers for particular types of CSR, DU or CU can set a CI/CD pipeline and schedule deployment of their latest software on the CSR, DU or CU at a preset frequency (e.g., nightly or weekly).

At 556, network service CI/CD is performed. In some situations, the CI/CD operations in 556 are triggered by one or more operations or changes in at 554. For example, as illustration, after software is deployed at the lower network level at 554, one or more network services are updated based on the deployment of the software. For instance, without limitation, in the context of 5G, various 5G network services can be updated after the underlying RAN in the 5G O-RAN are updated. In some situations, the CI/CD operations in 556 are independent of operations or changes at 554. For example, software developers of the core network services for the 5G O-RAN can set up a schedule to release their software to update the core network services on a regular basis.

At 558, operations control the ZTP in the O-RAN are performed. Examples of these operations can include scheduling release of software to update O-RAN components, instantiating a DU or CU, provisioning an RU or CSR in a cell site, performing a vendor RAN swap, and/or any other operations. In some examples, the operations at 558 are performed using a NOC such as the NOC 210 shown in FIG. 2. It should be understood although process 550 is illustrated so far from 552 to 558 in sequence, this is not intended to limit the O-RAN ZTP technologies in accordance with the present disclosure to a bottom up or top-down approach. In a top-down approach, ZTP is instigated, for example, at 558 and software is pushed to the core network, lower network level, and/or cell sites through the workflow engine 402 in the ZTP layer in the O-RAN. In a bottom-up approach, ZTP request is generated, for example, by a component at a cell site or data center, and software is pushed to that component through the workflow engine 302 in the ZTP layer in the O-RAN. In various embodiments, a ZTP request is configured for instigating one or more ZTP operations in the O-RAN.

In some situations, ZTP can be carried out by a third-party vendor to update its components in the O-RAN in a mixture of bottom-up and top-down approach. For instance, the third-party vendor may ship a router device to a cell site, which is installed by a technician on the cell site. Once the router device is live, it generates its status information to a management server of the third-party vendor for configuration of the router. In that example, the third-party vendor dynamically configures the router according to specifications or requirements of the O-RAN where the router is installed. In this way, a mixture of bottom-up and top-down ZTP is used to configure the router.

Example C-RAN System

FIG. 6 illustrates an embodiment of cellular network system 600 that depicts a C-RAN, in accordance with aspects of the invention. As illustrated, system 600 can include: cloud computing platform 602: data center 610; and base stations 620 (which may be referred to as a cell site). In system 600, base stations 620, includes structures 624, and radio units 622. In the C-RAN system 600, the DUs 616 are implemented remotely at a geographically separated data center 610.

Data center 610 can serve to host DU host server system 614, which can host multiple DUs 616 which are remote from corresponding base stations 620. For example, DU 616A can perform the DU functionality for base station 620A, DU 616B can perform the DU functionality for base station 620B, DU 616S can perform the DU functionality for base station 620S, and the like. In other examples, the association of a DU 616 with a RU in a base station can be changed. For instance, an association may change in response to some event/condition (e.g., a new DU is provisioned within the DU host server system 614. In some examples, the DU host system 614 may be referred to as a BBU hotel. DUs with DU host server system 614 can communicate with each other as needed.

According to some examples, the data center 610 may comprise one or more local data centers (LDCs) and/or one or more edge data centers (EDCs). Data center 610 can include multiple routers, such as routers 610, and can serve as a hub for base stations 620. In a cloud-computing cellular network implementation at least some components, such as CUs 608 and functions of 5G core 606, may be hosted on cloud computing platform 602 where higher-level functions of CU 608 and 5G core 606 can be executed in the cloud. In other embodiments, CU 608 and 5G core 606 may be hosted using hardware maintained by the cellular network provider, which may be in the same or a different data center from data center 610. While CUs 608 are illustrated within cloud computing platform 602, some/all of the CUs 608 may be located at a different location, such as at data center 610.

In some examples, encoded radio data is transmitted (e.g., via fiber optic connections 340 between BSs 620 and data center 610. According to some configurations, the connections between BSs 620 and data center 610 can be dedicated point-to-point communication links or a network on which addressing is used. Multiprotocol label switching (MPLS) segment routing (SR) may be used to perform routing over a network (e.g., fiber optic network). Such segment routing can allow for network nodes to steer packetized data based on a list of instructions carried in the packet header. This arrangement allows for the source from where the packet originated to define a route through one or more nodes that will be taken to cause the packet to arrive at its destination. Use of SR can help ensure network performance guarantees and can allow for network resources to be efficiently used. While MPLS SR can be used for network connections, it should be understood that other protocols and non-fiber-based networks can be used for connections between BSs 620 and data center 610. Real-world implementations of system 600 can include many (e.g., thousands) of BSs, and many DUs and CUs. BSs can include one or more antennas that allow RUs to communicate wirelessly with UEs (not shown). RUs can represent an edge of cellular network where data is transitioned to RF for wireless communication. The radio access technology (RAT) used by an RU may be 5G NR, or some other RAT.

In contrast to traditional cell-based network infrastructures that includes centralized processing, C-RAN breaks the base station into different parts. The RUs 622 are part of the BS 620, but the DUs 616 are aggregated at a central location (e.g., within a DU host server system 614). Moving the DUs 616 to data center 610 help a provider manage these functions provided by the DUs. Centralizing the DUs provides advantages, such as case of maintenance, resource virtualization, higher processing power, joint processing, radio sharing, increased data security, less power consumption, scalability, and the like. In some examples, one or more of the CUS may be co-located with one or more of the DUs 616 or hosted at a different data center. The actual split between DUs and RUs may be different depending on the specific use-case and implementation.

As illustrated, the DUs 616 can be shared by the different base stations 620. According to some configurations, pooling the DUs can reduce the number of DUs needed compared to traditional architectures. Additionally, the cost of network operation can be reduced since energy consumption is reduced compared to the traditional RAN architecture. DUs 614 within DU host server system 614 can also be added, upgraded, and removed more easily, thereby improving scalability and casing network maintenance.

FIG. 7 illustrates an example of a communications system 700 for deploying software from different vendors within a cellular network, according to various embodiments. In the illustrated example, the system 700 includes, among other components, multiple software/application/service vendors 702 (hereinafter “vendors 702”), a service management platform 704, a workflow engine 402 that includes a deployment engine 708, one or more production environments 710 established on a production cellular network, and one or more repositories (e.g., a repository for artifacts 714). Additional or alternative components may be included in the system 700. Various components of the system 700 are in communication with each other for data transmission.

In some embodiments, the service vendors 702 may be third-party service providers that provide physical devices and/or software/applications/services to be used within a production environment 710 (e.g., one or more cell sites). In some cases, the vendors can employ Continuous Integration and Continuous Deployment (CI/CD) methodologies. As a brief example, developers of a service vendor 702 may use a version control system to manage source codes of the new application or service, set up repositories and branches to enable code versioning, and configure a selected CI tool to automatically trigger builds when code changes are pushed to the repository.

IBuild scripts or configuration files (e.g., YAML) can be generated and defined to specify the required build steps, dependencies, and environment configurations. Unit tests are incorporated into the CI pipeline to verify the correctness and functionality of individual components or units within the new application or new service. Static code analysis tools may be used to analyze code quality, identify potential issues, and enforce coding standards. Once the new application or new service is built, the complied code and any required dependencies may be packaged into an artifact in a deployable format. A version number may be assigned to the generated artifact. Relevant metadata and documentation may be included in the artifact. The metadata may include details like the artifact name, version, release notes, licensing information, authorship, and any other pertinent information that helps consumers of the artifact understand its purpose, usage, and deployment. In some embodiments, the artifact generation process may be automated within the CI/CD pipeline. After successfully building and packaging the new application or new service, the artifact can be automatically generated and versioned.

Generally, an artifact refers to a packaged and versioned software component or set of files that are ready for deployment to a target environment, such as to one or more production environments 710 within a cellular network 712, and contains the necessary files, configurations, dependencies, and any other resources required to execute the software application or service in the target environment. The artifact may take various forms such as binary packages, archive files, container images (Docker images or images), configuration files, database scripts, and so on. The images encapsulate the application code, dependencies, and configurations in a portable and self-contained unit that can be deployed and run on container platforms. In some embodiments, a service may include multiple artifacts, and each artifact within the application service may contribute to a certain functionality of the application service. In some embodiments, the application service provided by the service vendor is a Software as a Service (SaaS) application.

The service management platform 704 can act as an intermediary between the vendors 702 and the deployment engine 708. The service management platform 704 is configured to receive to-be-deployed services and artifacts associated with the services from the service vendors 702, push the received services and artifacts to the workflow engine 402, and facilitate communication, integration, and control over the services provided by the service vendors 702. In some embodiments, the service management platform 704 is an Application Programming Interface (API) management platform, such as Google Cloud Platform (Apigee), Azure API Management, etc.

Within the workflow engine 402, the deployment engine 708 is responsible for receiving and responding to requests to deploy artifacts within a production environment 710. As discussed briefly above, the request may be a request to install, modify, and/or swap out an already installed artifact that was provided by a different vendor. In some cases, the artifacts are tested within a test environment using a testing system (not shown) prior to deployment within the production environment 710. The test environment can provide the necessary infrastructure, resources, and configurations to simulate the production environment 710.

According to some configurations, the workflow engine 402, and/or the deployment engine 708 accesses the repository for artifacts 714. The repository 714 can be an artifactory and act as a centralized location for storing and managing the validated/trusted services and their associated artifacts. The repository 714 may facilitate version control, access control, and easy retrieval of the validated/trusted services. The automated deployment system 706 is further configured to push the validated/trusted services to the production environments 710 of the cellular network 712 for deployment of the validated/trusted services in the production environments 710. The tested and validated services can be made available to users/clients on the production cellular network. The repository 714 can store various data such as, but not limited to classification rules, vendor profiles, service profile, artifact profiles, inventory of class identifiers, and so on.

In some embodiments, the deployment engine 708 is executed on a virtual private cloud (VPC) of the cloud-computing platform. A VPC provides a logically isolated section of the cloud infrastructure where the automated deployment engine 708 can operate. The deployment engine 708 can take advantage of the virtualization, on-demand resource provisioning, and network isolation provided by the VPC to allow for testing and deployment activities in a flexible and scalable environment.

The streamlined process with deployment of artifacts by the automated deployment engine 708 provides advantages with respect to efficiency, scalability, accuracy, and reliability. The automated deployment engine 708 can streamline the overall deployment workflow, eliminate manual steps, and reduce errors and inconsistencies. The deployment engine 708 in communication with the workflow engine 402 can handle the management and deployment of a large volumes of artifacts within different production environments 610.

FIG. 8 is a flow diagram illustrating an example method 800 for performing an automated cell site health check, according to various embodiments. The method 800 may be implemented by one or more components included in the systems described herein. In some configurations, the method 800 is implemented by one or more BOTs. Depending on the implementation, the method 800 may include additional, fewer, or alternative steps performed in various orders or in parallel.

At 802, the BOT is initiated. In some examples, a request is received from NOC 210 to initiate the health check automation BOT. In other examples, the health check automation BOT is automatically triggered (e.g., by the workflow engine 402) based on an occurrence of one or more events and/or according to a schedule.

At 804, the BOT connects to the cell site. In some examples, the BOT establishes a connection with the CSR at the cell site. In other examples, the BOT may establish a connection with some other component in order to communicate with one or more of the components installed at the cell site.

At 806, one or more health operations are determined. In some examples, the health check operations may be preconfigured (e.g., a script, a workflow, . . . ). In other examples, a user may enter the health check operations to perform using a user interface by selecting one or more user interface elements and/or entering information using some other mechanism (e.g., text or voice). As discussed above, the one or more health operations may be related to one or more of the components installed at the cell site. In some examples, the health operations can include, but are not limited to, connection tests (e.g., between different components of the cell site as well as connection with the components located outside of the cell site), programmatically obtaining a serial number from a component, checking operation of computing components at the cell site, checking Kubernates (K8s) worker node status or status of other computing devices, checking port status of different components, determining configuration information from a component, as well as other checks/tests associated with one or more of the components of a cell site.

At 808, one or more health checks are performed. As discussed above, the BOT can be configured to determine if a component is reachable, what version of software does the component have installed, what is the status of the component, what are other configuration parameters of the component, and the like.

At 810, health data is obtained. As discussed above, the health data may include data relating to results obtained from one or more tests, configuration data, status data, and the like. In some examples, the health data may be obtained directly from one or more of the components installed at the cell site, from the performance of one or more tests, and/or from some other device/component, such as the inventory management component 404.

FIG. 9 is a flow diagram illustrating an example method 900 for performing health tasks, according to various embodiments. The method 900 may be implemented by one or more components, such as a BOT 212, included in the systems described herein. Depending on the implementation, the method 900 may include additional, fewer, or alternative steps performed in various orders or in parallel.

At 904, the health check operations/workflows to perform are determined. In some examples, the workflow engine 402 may communicate with the workflow management system 406, and/or the inventory management system 404, and/or one or more BOTs to identify the workflows/operations to perform. For instance, the workflow engine 402 may access vendor profiles from repository 614 to identify the workflows to deploy hardware/software associated with a vendor. In some cases, different workflows can be associated with the different vendors. In this way, the workflow engine 402 can access and orchestrate the execution of the workflows for that particular vendor and/or the type of operation desired to perform. The workflows/operations may identify the artifact(s) to deploy. As discussed above, the repository 714 may include tested artifacts from different vendors that are approved to deploy within a production environment. For example, a vendor may have artifacts within the repository 614 for CSRs, DUs, CUs, RUs, and the like.

At 906, the health check workflows/operations are performed. As discussed above, different health check operations may be performed. For instance, the operations may involve testing the configuration of one or more components of the cell site (e.g., RU, DU, . . . ), testing a connection between different components of the cell site, testing a connection between a component installed at a cell site and a component external from the cell site, obtaining status information for one or more components, obtaining configuration information from one or more of the components, obtaining identifying information from one or more of the components, and the like.

In FIG. 10, a validation and fallout handling method 1000 is provided in accordance with some embodiments. It will be described with references to figures described herein. The operations of method 1000 presented below are intended to be illustrative. In some embodiments, method 1000 may be accomplished with one or more additional operations not described and/or without one or more of the operations discussed. Additionally, the order in which the operations of method 1000 are illustrated in FIG. 10 and described below is not intended to be limiting.

In some embodiments, method 1000 may be implemented by a device including one or more of the processors, such as the ones shown in FIG. 1 The device may include a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information. The device may execute some or all of the operations of method 1000 in response to instructions stored electronically on an electronic storage medium. The device may include one or more components configured through hardware, firmware, and/or software to be designed for execution of one or more of the operations of method 1000.

At 1002, a workflow is started. As discussed above, a workflow may be a stage in a pipeline for performing RU tasks. In other examples, a workflow may be associated with performing other operations. According to some examples, a workflow may be associated with changing one or more components from one vendor to another vendor, setting up devices in a core network of the O-RAN (e.g., within a cloud environment) as well as setting up devices in individual cell sites facilitating the O-RAN. In various examples, workflows managed by the workflow engine 402 and/or workflow management component 406 may include but are not limited to RU workflows, computer host provisioning (CHP) workflows, virtual server management provisioning (VSMP) workflows (e.g., VMware vCenter provisioning (VCP)), node-pool creation (NPC) workflows, distributed unit instantiation (DUI) workflows, radio access network (RAN) initiation workflows, vendor RAN swapping workflows, C-RAN provisioning workflows, and/or other workflows. According to some embodiments, the workflows may be completed in a specified order, such as CHP workflow before execution a VSMP workflow, and the like.

At 1004, a pre-check validation can be performed by the validation engine 412. As discussed above, individual validation apps may be developed for different types of validation flows or pipelines. In various embodiments, the validation apps are configured with intelligence to handle corresponding validation flows. In various example, validation apps are developed for pre-checks for different ones of the workflows (e.g., RU, CHP, VCP, NPC, DUI, RAN, . . . ). In some examples, a validation worker places validation information regarding the execution of the validation job onto a message queue. The validation information may indicate whether the pre-check passed or did not pass.

At 1006, a determination is made as to whether the pre-check validation passed. When the pre-check validation passes, the process flows to 1008. When the pre-check validation does not pass, the process flows to 1-10 for fallout handling.

At 1008, the workflow is monitored. As discussed above, the validation engine 412, the workflow engine 402, or some other device/component may monitor the operations performed to determine whether the operations completed successfully. In some examples, a timeout is specified that indicates how long the execution of the operations associated with the current stage are allowed to take before an error is generated. For example, one stage may have a timeout of ten minutes, another stage may have a timeout of fifteen minutes, and the like. In this way, an error is detected in the stage in situations when the workflow is not progressing through the operations for the stage.

At 1010, fallout handling is performed. As discussed above, according to some embodiments, a fallout engine (not shown), the workflow engine 402, and/or some other device component performs fallout operations for the different points in the workflows (e.g., pre-check, monitoring performance of the ZTP operations for the stage, and post-check). When the fallout engine pauses the workflow (e.g., a hard fallout), then, after determining that the issue/error has been resolved, the fallout engine cause the workflow to resume at a point in the workflow prior to the occurrence of the error.

At 1014, a post-check is performed. As discussed above, the validation engine 412 may perform a post-check validation to determine whether the workflow performed the operations successfully.

At 1016, a determination is made as to whether the post-check validation passed. When the post-check validation passes, the process flows to 1016. When the post-check validation does not pass, the process flows to 1010.

At 1018, a determination is made as to whether there are more stages/workflows. When there are more stages, the process flows to 1004. When there are not more stages, the process ends and returns to processing other actions.

The system and other components in the systems 100, 200, 300, 400, 600, 700 described above may include a computer system that further includes computer hardware and software that form special-purpose network circuitry to implement various embodiments such as communication, calculation, artifact validation, functional testing, test environment configuration, and so on. FIG. 11 is a schematic diagram illustrating an example of computer system 1100. The computer system 1100 is a simplified computer system that can be used to implement various embodiments described and illustrated herein. A computer system 1100 as illustrated in FIG. 11 may be incorporated into devices such as a portable electronic device, mobile phone, server grade machines, or other device as described herein. FIG. 11 provides a schematic illustration of one embodiment of a computer system 1100 that can perform some or all of the steps of the methods and workflows provided by various embodiments. It should be noted that FIG. 11 is meant only to provide a generalized illustration of various components, any or all of which may be utilized as appropriate. FIG. 11, therefore, broadly illustrates how individual system elements may be implemented in a relatively separated or relatively more integrated manner.

The computer system 1100 is shown including hardware elements that can be electrically coupled via a bus 1105, or may otherwise be in communication, as appropriate. The hardware elements may include one or more processors 1110, including without limitation one or more general-purpose processors and/or one or more special-purpose processors such as digital signal processing chips, graphics acceleration processors, and/or the like; one or more input devices 1115, which can include without limitation a mouse, a keyboard, a camera, and/or the like; and one or more output devices 1120, which can include without limitation a display device, a printer, and/or the like.

The computer system 1100 may further include and/or be in communication with one or more non-transitory storage devices 1125, which can include, without limitation, local and/or network accessible storage, and/or can include, without limitation, a disk drive, a drive array, an optical storage device, a solid-state storage device, such as a random access memory (“RAM”), and/or a read-only memory (“ROM”), which can be programmable, flash-updateable, and/or the like. Such storage devices may be configured to implement any appropriate data stores, including without limitation, various file systems, database structures, and/or the like.

The computer system 1100 might also include a communications subsystem 1130, which can include without limitation a modem, a network card (wireless or wired), an infrared communication device, a wireless communication device, and/or a chipset such as a Bluetooth™ device, a 602.11 device, a WiFi device, a WiMax device, cellular communication facilities, etc., and/or the like. The communications subsystem 1130 may include one or more input and/or output communication interfaces to permit data to be exchanged with a network such as the network described below to name one example, other computer systems, television, and/or any other devices described herein. Depending on the desired functionality and/or other implementation concerns, a portable electronic device or similar device may communicate image and/or other information via the communications subsystem 1130. In other embodiments, a portable electronic device, e.g., the first electronic device, may be incorporated into the computer system 1100, e.g., an electronic device as an input device 1115. In some embodiments, the computer system 1100 will further include a working memory 1135, which can include a RAM or ROM device, as described above.

The computer system 1100 also can include software elements, shown as being currently located within the working memory 1135, including an operating system 1160, device drivers, executable libraries, and/or other code, such as one or more application programs 1165, which may include computer programs provided by various embodiments, and/or may be designed to implement methods, and/or configure systems, provided by other embodiments, as described herein. Merely by way of example, one or more procedures described with respect to the methods discussed above, such as those described in relation to FIG. 11, might be implemented as code and/or instructions executable by a computer and/or a processor within a computer; in an aspect, then, such code and/or instructions can be used to configure and/or adapt a general purpose computer or other device to perform one or more operations in accordance with the described methods.

A set of these instructions and/or code may be stored on a non-transitory computer-readable storage medium, such as the storage device(s) 1125 described above. In some cases, the storage medium might be incorporated within a computer system, such as computer system 1100. In other embodiments, the storage medium might be separate from a computer system e.g., a removable medium, such as a compact disc, and/or provided in an installation package, such that the storage medium can be used to program, configure, and/or adapt a general-purpose computer with the instructions/code stored thereon. These instructions might take the form of executable code, which is executable by the computer system 1100 and/or might take the form of source and/or installable code, which, upon compilation and/or installation on the computer system 1100 e.g., using any of a variety of generally available compilers, installation programs, compression/decompression utilities, etc., then takes the form of executable code.

It will be apparent that substantial variations may be made in accordance with specific requirements. For example, customized hardware might also be used, and/or particular elements might be implemented in hardware, software including portable software, such as applets, etc., or both. Further, connection to other computing devices such as network input/output devices may be employed.

As mentioned above, in one aspect, some embodiments may employ a computer system such as the computer system 1100 to perform methods in accordance with various embodiments of the technology. According to a set of embodiments, some or all of the operations of such methods are performed by the computer system 1100 in response to processor 1110 executing one or more sequences of one or more instructions, which might be incorporated into the operating system 1160 and/or other code, such as an application program 1165, contained in the working memory 1135. Such instructions may be read into the working memory 1135 from another computer-readable medium, such as one or more of the storage device(s) 1125. Merely by way of example, execution of the sequences of instructions contained in the working memory 1135 might cause the processor(s) 1110 to perform one or more procedures of the methods described herein. Additionally or alternatively, portions of the methods described herein may be executed through specialized hardware.

The terms “machine-readable medium” and “computer-readable medium,” as used herein, refer to any medium that participates in providing data that causes a machine to operate in a specific fashion. In an embodiment implemented using the computer system 1100, various computer-readable media might be involved in providing instructions/code to processor(s) 1110 for execution and/or might be used to store and/or carry such instructions/code. In many implementations, a computer-readable medium is a physical and/or tangible storage medium. Such a medium may take the form of a non-volatile media or volatile media. Non-volatile media include, for example, optical and/or magnetic disks, such as the storage device(s) 1125. Volatile media include, without limitation, dynamic memory, such as the working memory 1135.

Common forms of physical and/or tangible computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, solid state drive, or any other magnetic medium, a CD-ROM, any other optical medium, punchcards, papertape, any other physical medium with patterns of holes, a RAM, a PROM, EPROM, a FLASH-EPROM, any other memory chip or cartridge, or any other medium from which a computer can read instructions and/or code.

Various forms of computer-readable media may be involved in carrying one or more sequences of one or more instructions to the processor(s) 1110 for execution. Merely by way of example, the instructions may initially be carried on a magnetic disk and/or optical disc of a remote computer. A remote computer might load the instructions into its dynamic memory and send the instructions as signals over a transmission medium to be received and/or executed by the computer system