PORTABILITY OF CONFIGURATION POLICIES FOR SERVICE MESH-BASED COMPOSITE APPLICATIONS

TECHNICAL FIELD

[0001] The present disclosure relates generally to communications, and more particularly to portability of configuration policies for service mesh-based composite applications.

BACKGROUND

[0002] In cloud environments, the microservice architecture has caused the disaggregation of monolithic applications into several components or elements. Each component needs to somehow be managed in an efficient and consistent way as part of a composite application. In terms of service to service communication, it is important to support several requirements related to service exposure management: i. fine grained traffic control management, ii. Secure exposure mechanisms (authentication, authorization and encryption), and iii. observability for service auditing (request tracing and logging).

[0003] The need for service exposure adds complexity to the development and configuration process of applications deployed in cloud environments. The Service Mesh pattern has been proposed as a way to decouple concerns of the application developer from the system/application operator to manage service to service communication. This decoupling means that the lifecycle of the components of a Service Mesh that enable service exposure can be managed by the system/application operator without coordinating with the application developer. In other words, the configuration of the exposure of a cloud native application should not affect the application code as such.

[0004] Service mesh constitutes a configurable communication platform that allows cloud-native service exposure by taking care of granular security management, progressive service delivery, dynamic request routing, resilient communication and consistent observability. A generic service mesh platform is realized as a dedicated infrastructure layer on top of the deployed microservices. It can include a control plane and a data plane. The data plane can include a set of intelligent and lightweight proxies deployed together with the microservice instances. These proxies are in charge of mediating and controlling network-based communication between microservices, for example, service discovery, health checking, routing, load balancing, authentication/authorization and observability. The control plane manages and configures the proxies and other components for traffic routing, policy enforcement and telemetry collection.

SUMMARY

[0005] According to some embodiments, a method of operating a first network node in a communications network that includes a second network node is provided. The first network node can be configured to provide a first service mesh and the second network node can be configured to provide a second service mesh. The method can include determining to transmit a configuration policy associated with a service to the second service mesh. The method can further include determining an exposure level associated with the second service mesh relative to the first service mesh. The method can further include transmitting the configuration policy to the second service mesh based on the exposure level.

[0006] According to other embodiments, a first network node is provided. The first network node can be configured to operate in a wireless communication network that includes a second network node. The first network node can be configured to provide a first service mesh and the second network node can be configured to provide a second service mesh. The first network node can include processing circuitry and memory coupled to the processing circuitry. The memory can have instructions stored therein that are executable by the processing circuitry to cause the first network node to perform operations. The operations can include determining to transmit a configuration policy associated with a service to the second service mesh. The operations can further include determining an exposure level associated with the second service mesh relative to the first service mesh. The operations can further include transmitting the configuration policy to the second service mesh based on the exposure level.

[0007] According to other embodiments, a first network node is provided. The first network node can be configured to operate in a wireless communication network that includes a second network node. The first network node can be configured to provide a first service mesh and the second network node can be configured to provide a second service mesh. The first network node can be adapted to perform operations. The operations can include determining to transmit a configuration policy associated with a service to the second service mesh. The operations can further include determining an exposure level associated with the second service mesh relative to the first service mesh. The operations can further include transmitting the configuration policy to the second service mesh based on the exposure level.

[0008] According to other embodiments, a computer program is provided. The computer program can include program code to be executed by processing circuitry of a first network node configured to operate in a wireless communication network that includes a second network node. The first network node can be configured to provide a first service mesh and the second network node can be configured to provide a second service mesh. Execution of the program code can cause the first network node to perform operations. The operations can include determining to transmit a configuration policy associated with a service to the second service mesh. The operations can further include determining an exposure level associated with the second service mesh relative to the first service mesh. The operations can further include transmitting the configuration policy to the second service mesh based on the exposure level.

[0009] According to other embodiments, a computer program product is provided. The computer program product can include a non-transitory storage medium including program code to be executed by processing circuitry of a first network node configured to operate in a wireless communication network that includes a second network node. The first network node can be configured to provide a first service mesh and the second network node can be configured to provide a second service mesh. Execution of the program code can cause the first network node to perform operations. The operations can include determining to transmit a configuration policy associated with a service to the second service mesh. The operations can further include determining an exposure level associated with the second service mesh relative to the first service mesh. The operations can further include transmitting the configuration policy to the second service mesh based on the exposure level.

[0010] According to other embodiments, a method of operating a first network node in a communications network that includes a second network node is provided. The first network node can be configured to provide a destination service mesh and the second network node can be configured to provide a dependent service mesh. The method can include receiving a set of configuration policies associated with a service from a third network node of the communications network that is configured to provide a source service mesh. The method can further include normalizing the set of configuration policies based on characteristics of the destination service mesh. The method can further include transmitting a configuration policy of the set of configuration policies to the dependent service mesh.

[0011] According to other embodiments, a first network node is provided. The first network node can be configured to operate in a wireless communication network that includes a second network node. The first network node can be configured to provide a destination service mesh and the second network node can be configured to provide a dependent service mesh. The first network node can include processing circuitry and memory coupled to the processing circuitry. The memory can have instructions stored therein that are executable by the processing circuitry to cause the first network node to perform operations. The operations can include receiving a set of configuration policies associated with a service from a third network node of the communications network that is configured to provide a source service mesh. The operations can further include normalizing the set of configuration policies based on characteristics of the destination service mesh. The operations can further include transmitting a configuration policy of the set of configuration policies to the dependent service mesh.

[0012] According to other embodiments, a first network node is provided. The first network node can be configured to operate in a wireless communication network that includes a second network node. The first network node can be configured to provide a destination service mesh and the second network node can be configured to provide a dependent service mesh. The first network node can be adapted to perform operations. The operations can include receiving a set of configuration policies associated with a service from a third network node of the communications network that is configured to provide a source service mesh. The operations can further include normalizing the set of configuration policies based on characteristics of the destination service mesh. The operations can further include transmitting a configuration policy of the set of configuration policies to the dependent service mesh. [0013] According to other embodiments, a computer program is provided. The computer program can include program code to be executed by processing circuitry of a first network node configured to operate in a wireless communication network that includes a second network node. The first network node can be configured to provide a destination service mesh and the second network node can be configured to provide a dependent service mesh. Execution of the program code can cause the first network node to perform operations. The operations can include receiving a set of configuration policies associated with a service from a third network node of the communications network that is configured to provide a source service mesh. The operations can further include normalizing the set of configuration policies based on characteristics of the destination service mesh. The operations can further include transmitting a configuration policy of the set of configuration policies to the dependent service mesh.

[0014] According to other embodiments, a computer program product is provided. The computer program product can include a non-transitory storage medium including program code to be executed by processing circuitry of a first network node configured to operate in a wireless communication network that includes a second network node. The first network node can be configured to provide a destination service mesh and the second network node can be configured to provide a dependent service mesh. Execution of the program code can cause the first network node to perform operations. The operations can include receiving a set of configuration policies associated with a service from a third network node of the communications network that is configured to provide a source service mesh. The operations can further include normalizing the set of configuration policies based on characteristics of the destination service mesh. The operations can further include transmitting a configuration policy of the set of configuration policies to the dependent service mesh.

[0015] Various embodiments described herein add support for automated migration of application context data where its exposure is handled by a service mesh. In some embodiments, service mesh capabilities are expanded to support automated migration of context of composite applications between different administrative domains, which can increase the portability of configuration policies for service meshbased composite applications.

BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate certain non-limiting embodiments of inventive concepts. In the drawings: [0017] FIG. 1 is a schematic diagram illustrating an example of a service mesh architecture;

[0018] FIG. 2 is a block diagram illustrating an example of a multi-cluster single-mesh deployment model;

[0019] FIG. 3 is a block diagram illustrating an example of a multi-cluster multi-mesh deployment model;

[0020] FIG. 4 is a block diagram illustrating an example of an Istio service mesh architecture;

[0021] FIG. 5 is a block diagram illustrating an example of different exposure levels between administrative domains;

[0022] FIG. 6 is a block diagram illustrating an example of an apparatus for managing configuration policy portability in a service mesh according to some embodiments of inventive concepts;

[0023] FIG. 7 is a flow chart illustrating an example of porting services between multi-cluster multi-mesh service meshes according to some embodiments of inventive concepts;

[0024] FIG. 8 is a flow chart illustrating an example of operations performed by a source service mesh to provide configuration policies to a destination service mesh according to some embodiments of inventive concepts;

[0025] FIG. 9 is a flow chart illustrating an example of operations performed by a destination service mesh to receive configuration policies from a source service mesh according to some embodiments of inventive concepts;

[0026] FIG. 10 is a flow chart illustrating an example of operations performed by a destination service mesh to propagate configuration policies to a dependent service mesh according to some embodiments of inventive concepts;

[0027] FIG. 11 is a flow chart illustrating an example of operations performed by a dependent service mesh to receive configuration policies from a destination service mesh according to some embodiments of inventive concepts;

[0028] FIG. 12 is a block diagram illustrating an example of a wireless device (“UE”) according to some embodiments of inventive concepts;

[0029] FIG. 13 is a block diagram illustrating an example of a network node according to some embodiments of inventive concepts;

[0030] FIG. 14 is a block diagram illustrating an example of another network node according to some embodiments of inventive concepts; [0031] FIGS. 15-16 are flow charts illustrating examples of operations performed by a network node configured to provide a service mesh according to some embodiments of inventive concepts.

[0032] FIG. 17 is a block diagram of a wireless network in accordance with some embodiments;

[0033] FIG. 18 is a block diagram of a user equipment in accordance with some embodiments

[0034] FIG. 19 is a block diagram of a virtualization environment in accordance with some embodiments;

[0035] FIG. 20 is a block diagram of a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments;

[0036] FIG. 21 is a block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments;

[0037] FIG. 22 is a block diagram of methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments;

[0038] FIG. 23 is a block diagram of methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments;

[0039] FIG. 24 is a block diagram of methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments; and

[0040] FIG. 25 is a block diagram of methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.

DETAILED DESCRIPTION

[0041] Inventive concepts will now be described more fully hereinafter with reference to the accompanying drawings, in which examples of embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of present inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present/used in another embodiment.

[0042] The following description presents various embodiments of the disclosed subject matter. These embodiments are presented as teaching examples and are not to be construed as limiting the scope of the disclosed subject matter. For example, certain details of the described embodiments may be modified, omitted, or expanded upon without departing from the scope of the described subject matter.

[0043] Deployment models for a service mesh’s control plane are described below. There are some open-source tools that address mesh-based service exposure, such as Istio and Linkerd. Linkerd may be stable and has been accepted by the Cloud Native Computing Foundation. Istio has a growing community which allows fast iteration. Some tools are focused on central cloud, however, Istio has recently started to address challenges related to multi-cluster and multi-mesh scenarios. Istio is considering different control plane models for service meshes that can span among multiple clusters and multiple networks, as well as consider interactions among multiple service meshes. The different deployment models for the control plane starting to be supported by Istio Service Mesh are: multi-cluster, singlemesh scenario (“MCSM”); multi-cluster, replicated-mesh scenario (“MCRM”); multicluster, and multi-mesh scenario (“MCMM”).

[0044] FIG. 2 illustrates an example of a MCSM that includes a shared control plane that combines multiple clusters into a single managed unit. This scenario may be most suited for clusters that are configured together, and they may be seen as a single administrative domain (e.g., part of the same organization). There are two main cases of network setup: single network and multi-network. In a single network example, a single Istio control plane can be shared across all clusters with a flat network via direct access over a virtual private network (“VPN”). In this example, all service instances can reach each other directly via sidecard-proxy to sidecard-proxy communication. In a multi-network example, a single Istio control plane can be shared among multiple clusters using Istio Gateways, a standalone proxy. Service instances can reach each other through one or more Istio Gateways (zero VPN). In this example, partitioned service discovery can be used to provide application consumers a different view of service endpoints based on which network related information can be shared with a particular service consumer.

[0045] A MCRM can provide support for high availability requirements by having replicated control planes. In this example, several clusters in different availability zones have identical Istio control plane instances. Cross-cluster shared root certificate authority (“CA”) and local cluster CA are needed to handle secure exposure.

[0046] FIG. 3 illustrates an example of a MCMM. In a MCMM, each service mesh is an individual administrative domain and exposure is managed separately by independent mesh control planes that belong to different administrative domains (e.g. different organizations).

[0047] Partitioned service discovery can be used to allow inter-mesh communication based on ServiceEntries configured in the domains’ domain name systems (“DNSs”) hosting services with dependencies on services running in an external domain. Ingress service access can be done via the local DNS, End-point Discovery Service (“EDS”)-based Ingress Gateway and/ or Server Name Indication (“SNI”)-based routing. Egress service access can be done via an Egress Gateway and/or a CoreDNS server. Every service that needs to be accessed from a different mesh needs a ServiceEntry in that remote mesh. VirtualServices can also be defined for accessing external services.

[0048] Assuming Istio Gateways of each domain can reach each other, mutual TLS can be used to secure the inter-domain service communication. In terms of trust between the different domains, a scalable architecture proposes that each domain has a local root CA and via a process where the trust bundles of each domain are exchanged, identity federation is performed. After that, configuration of local policies can be specified for even external service identities.

[0049] Configuration policies of a service mesh will be described below. Some of the Service Mesh technologies rely on policy-based configurations for service exposure. FIG. 4 illustrates an example of Istio’s architecture in which all architectural components are involved in one way or another with the policy-based configuration of the service mesh. However, Istio can support different kinds of policies based on the different capabilities it has, including, for example: traffic management policies; authentication policies; authorization policies; audit (telemetry) policies; and service discovery policies. [0050] Continuing with Istio’s architecture, in terms of policy management, Galley 420a-b can allow validation, ingestion, processing and distribution of configuration policies. A Pilot 430a-b can watch the configuration storage, translate high-level policies into component-level policies in a platform agnostic way, and propagate them to the sidecard proxies 442a-b, 444a-b during runtime upon configuration update. In terms of policy enforcement, the Sidecard Proxies 442a-b, 444a-b can enforce fine-grained traffic control as well as access control and rate limiting. Mixer 450a-b can assist the enforcement of access control and usage policies across the service mesh (e.g., telemetry-related policies). Citadel 460a-b can be used to enforce security policies based on service identity.

[0051] In some examples, Istio can be designed to give support for intent-based configuration policy definition, by translating high-level statements into low-level or component-level configuration policies. However, the service mesh architecture can also be configured to support configuration policy updates in a smoother way via a configuration policy registry.

[0052] An administrative domain (also referred to as a trust domain or security domain) is an abstract representation of the ownership boundaries of an information system based on the assessment of administration rights or trust/security limits.

[0053] The different deployment models of the Service Mesh’ control plane that were presented above could be used as basis to support isolation between different administrative domains (e.g., administrative domain 410a and administrative domain 410b). There are different purposes when defining administrative domains, for example, isolation between different applications inside the same organization, isolation of different development teams inside the same organization, or isolation between different organizations.

[0054] Isolation of administrative domains can be achieved in different ways. Hard Isolation defines physical boundaries based on physical clusters or physical nodes typically having associated an independent network. Soft Isolation strategies define logical or virtual boundaries (sometimes called Secure Virtual Premise) by using trusted computing, access control and secure communication (e.g. by using Kubernetes namespaces or virtual clusters where each namespace could have associated either an independent network or where some/all of these namespaces could rely on a fully connected network). [0055] When a cloud platform is offered as a service, including a managed Service Mesh, by, for example a web-scale provider, there is, at least, a two-tier operation system for the configuration of policies of the service mesh. In the first level, the platform provider, more specifically the platform operation agent, configures different policies based on knowledge of the topology of the underlying platform. In the second level, the platform tenant, specifically the application operator agent, is also given certain permissions to configure policies related to the applications whose exposure is handled by the service mesh.

[0056] At the platform level, there should be a platform operator that could belong to the organization providing the platform-as-a-service (“PaaS”). Platform tenants share the same underlying platform. In this case, the platform provider will have automated tools for deploying a service mesh instance (control + data plane) per platform tenant. The platform operator could have the rights to specify certain policies for the service mesh of each platform tenant (e.g., policies for configuring the DNS address or the service mesh ingress/egress gateways addresses, for configuring address for the public key infrastructure (“PKI”), providing key pairs for the security manager component, role-based access control (“RBAC”) for allowing the application on top of service mesh to operate and manage its mesh by limiting permissions to a specific namespace).

[0057] At the software level, each platform tenant (e.g., application provider) could be subscribed to more than one PaaS provider (e.g., for the purpose of extending geographical reachability or coverage of distributed application(s), or for allowing HA by having different availability zones in case of a disruption or increase of load in a particular cluster). The application provider can be subscribed to a platform aggregator and make use of federated service meshes to manage exposure of a multi-party composite application. The application operator has a more limited scope of administration which is constrained by the boundaries of its administrative domain. In some examples, the platform operator is the one that assigns the rights to the application operators for managing or controlling certain policies that are more related to the application configuration.

[0058] FIG. 5 illustrates an example of internal exposure, partner exposure, and external exposure. It is possible for a composite application that is made up by a set of micro-services, to have components belonging to multiple administrative domains 510a-c. In this example, service exposure is not limited to a single internal domain but to other domains as well. A set of administrative domains 510a-b can form an alliance (referred to here as partner exposure domain), for example, when service meshes are federated in a way that they can all be managed and operated using the same application program interface (“API”) 530. Security mechanisms may need to be more demanding when dealing with exposure of APIs 540 to external domains 510c compared to APIs 530 of partner domains 510b (e.g., when exposing services to competitors). At the same, service exposure to partner domains 510b can be more security demanding when compared to exposure to APIs 520 of the internal domain 510a.

[0059] Exposure to internal domain can occur when a single-party composite application is a composite application where its components are all running inside the same administrative domain at the software level. This example can be based on the MCSM or the MCRM. For example, exposure to internal domain can occur in a composite application that is provided by the same organization in different availability zones.

[0060] Exposure to an external domain can occur when a multi-party composite application is a composite application where its components are running in different administrative domains (at the software level). This case can be supported by the MCMM. For example, exposure to an external domain can occur in a composite application where at least one of its components is run by another administrative domain.

[0061] Current implementations of Service Mesh do not offer support for application portability. One aspects of a Service Mesh is that it is flexible, which can allow dynamic configuration of different capabilities of the mesh based on policies. These configuration policies can be related to a particular application service and they can be part of the context of an application that needs to be ported. Support of portability of application context can be relevant for different examples.

[0062] In some examples, support of portability of application context can be relevant to support UE Mobility where a service needs to be migrated between different edge locations. The migration allows to follow the mobility pattern of the service consumer(s) to keep the best possible service experience.

[0063] In additional or alternative examples, support of portability of application context can be relevant when a Service Provider sells an application’s rights to another Service Provider, the application requires to be migrated/ported to another execution environment without impacting the availability of the service (e.g., from an on-premises cloud A to an on-premises cloud B).

[0064] In additional or alternative examples, support of portability of application context can be relevant when a Service Provider that is using a public cloud provider A (e.g. Google Cloud) as underlying execution environment wants to instead use another public cloud provider B (e.g. Amazon) without impacting the availability of the service.

[0065] In additional or alternative examples, support of portability of application context can be relevant, when two or more Service Providers create an alliance and decide to aggregate or federate underlying distributed cloud platform (including federation of service meshes) without impacting availability of the service.

[0066] In additional or alternative examples, support of portability of application context can be relevant, when considering the case of an elastic Service Mesh that scales horizontally the underlying service execution environment on-the-fly based on resource demand without impacting availability of the exposed services.

[0067] In these examples, cloud-based services together with their context- related data need to somehow be migrated/ported between different isolation domains in a way that the service experience is not impacted.

[0068] In some embodiments, some of the different administrative hierarchies that could be involved in the operation of the different layers part of a federated distributed cloud system where service exposure is handled based on Service Meshes can be identified. In additional or alternative embodiments, how different trust domains (e.g., internal/external) can affect the process can be analyzed. In additional or alternative embodiments, how support for application portability can be aware of the different deployment models for the service mesh’ control plane can be analyzed.

[0069] In some embodiments, a process and/or apparatus are provided that are capable of supporting application portability, more specifically portability of configuration policies related to a service mesh in charge of managing application exposure. The process and apparatus may not rely on a central component, instead the process and apparatus may handle migration of policy-based configuration data in a peer to peer way and on a publish/subscribe approach. The process can be aware of the different administrative hierarchies (e.g., platform and application) and administrative domain levels (e.g., internal and external) that can be involved in the operation and management of a cloud-based distributed system where exposure of the applications relies on Service Mesh. The process can also be compatible with composite configuration policies which are usually registered in a coupled or aggregated way.

[0070] In additional or alternative embodiments, a process can support different deployment models for the service mesh control plane, for example, the MCRM and the MCMM by adding awareness of the different administrative hierarchies and domains that could influence the portability of configuration policies in a proper way. The process can also support composite applications, whether the different integrating components are provided by single or multiple administrative domains.

[0071] In additional or alternative embodiments, configuration policies that can be migrated can include authentication rules, authorization rules, service discovery rules, and traffic management rules.

[0072] FIG. 6 illustrates an example of a policy configuration apparatus 610 for managing configuration policy portability in a service mesh. The components of policy configuration apparatus 610 can be part of the configuration module illustrated in FIG. 1, that belongs to the control plane of each service mesh involved in a process for portability of configuration policies.

[0073] In this example, an application registry 620 can include information of each composite application, including its topology. A platform registry 630 can keep information regarding the topology of the distributed cloud-based platform. A configuration registry 640 can store registered configuration policies as part of the service mesh operation. A configuration server 640 can be in charge of allowing specification of configuration policies and their transformation from intent-based high- level to component-based low-level. A configuration scheduler 650 can be in charge of handling modifications in the applied configuration policies part of the service mesh in a smooth and proper way. A SM-to-SM sender/publisher 670 and a SM-to-SM receiver/subscriber 680 can allow communication among service meshes in a peer-to- peer way and/or under a publish/subscribe approach.

[0074] A configuration manager 690 can implement the process depicted in FIG. 7 for porting a service Sp from a source service mesh SMs to a destination SMd. At block 710, the process includes identifying and preparing configuration policies related to service (“Sp”) in a source service mesh (“SMs”) and transmitting the adapted policies to the destination service mesh (“SMd”). At block 720, the process includes considering what needs to be done in the destination domain SMd. Once ported policies are received in SMd, the process transforms once more the configuration policies based on the context of PDd in such a way that they can be integrated in that new domain. At block 730, the process includes evaluating and propagating effects of the ported configuration policies to all dependent service meshes SMj(s). At block 740, the process includes each SMj identifying and transforming dependent policies upon ported Sp related policies.

[0075] In some embodiments, the process provides support for automated application portability across different cloud platforms, more specifically supporting the migration of service context data, for example, configuration policies of the Service Mesh. In additional or alternative embodiments, a process or an apparatus is provided that is aware of the different administrative hierarchies, domains, and ways to operate and configure Service Mesh-based exposure for multi-domain composite applications. [0076] In some embodiments, adding support for automated migration of application context data where its exposure is handled by a Service Mesh allows application portability for the different use-cases. Additional or alternative embodiments, allow the extension of the Service Mesh capabilities in order to support automated migration of context of composite applications between different administrative domains including configuration policies. Additional or alternative embodiments, support different deployment models of service-mesh based applications and take information related to administrative hierarchies and exposure levels to evaluate the portability strategy to apply. Additional or alternative embodiments, support operation of exposure of composite services based on composite configuration policies.

[0077] FIG. 12 is a block diagram illustrating elements of a wireless device UE 1200 (also referred to as a mobile terminal, a mobile communication terminal, a wireless communication device, a wireless terminal, mobile device, a wireless communication terminal, user equipment, UE, a user equipment node/terminal/device, etc.) configured to provide wireless communication according to embodiments of inventive concepts. (Wireless device 1200 may be provided, for example, as discussed below with respect to wireless device 4110 of FIG. 17, UE 4200 of FIG. 18, UEs 4491, 4492 of FIG. 20, and/or UE 4530 of FIG. 21 , each of which should be considered interchangeable in references thereto unless otherwise noted.) As shown, wireless device UE may include an antenna 1207 (e.g., corresponding to antenna 4111 of FIG. 17), and transceiver circuitry 1201 (also referred to as a transceiver, e.g., corresponding to interface 4114 of FIG. 17) including a transmitter and a receiver configured to provide uplink and downlink radio communications with a base station(s) (e.g., corresponding to network node 4160 of FIG. 17, also referred to as a RAN node) of a radio access network. Wireless device UE may also include processing circuitry 1203 (also referred to as a processor, e.g., corresponding to processing circuitry 4120 of FIG. 17) coupled to the transceiver circuitry, and memory circuitry 1205 (also referred to as memory, e.g., corresponding to device readable medium 4130 of FIG. 17) coupled to the processing circuitry. The memory circuitry 1205 may include computer readable program code that when executed by the processing circuitry 1203 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 1203 may be defined to include memory so that separate memory circuitry is not required. Wireless device UE 1200 may also include an interface (such as a user interface) coupled with processing circuitry 1203, and/or wireless device UE may be incorporated in a vehicle. [0078] As discussed herein, operations of wireless device UE 1200 may be performed by processing circuitry 1203 and/or transceiver circuitry 1201. For example, processing circuitry 1203 may control transceiver circuitry 1201 to transmit communications through transceiver circuitry 1201 over a radio interface to a radio access network node (also referred to as a base station) and/or to receive communications through transceiver circuitry 1201 from a RAN node over a radio interface. Moreover, modules may be stored in memory circuitry 1205, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 1203, processing circuitry 1203 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to wireless devices).

[0079] FIG. 13 is a block diagram illustrating elements of a network node 1300 (also referred to as a network node, base station, eNodeB/eNB, gNodeB/gNB, etc.) of a network configured to provide cellular communication according to embodiments of inventive concepts (network node 1300 may be provided, for example, as discussed below with respect to network node 4160 of FIG. 17, base stations 4412a, 4412b, 4412c of FIG. 20, and/or base station 4520 of FIG. 21, each of which should be considered interchangeable in references thereto unless otherwise noted. The network node 1300 can include the policy configuration apparatus 610 or a portion of the policy configuration apparatus 610 such that the network node 1300 can provide a service mesh as part of a service-mesh based composite application. Network node 1300 may be referred to herein as radio access network (“RAN”) node 1300, however, network node 1300 is not intended to be limited to being a RAN node as those may be strictly understood (e.g., in view of 3GPP). Network node 1300 is intended to cover any compute device/resource in a wireless communication network including, for example, an edge compute node.

[0080] As shown, the RAN node 1300 may include transceiver circuitry 1301 (also referred to as a transceiver, e.g., corresponding to portions of interface 4190 of FIG. 17) including a transmitter and a receiver configured to provide uplink and downlink radio communications with mobile terminals. The RAN node 1300 may include network interface circuitry 1307 (also referred to as a network interface, e.g., corresponding to portions of interface 4190 of FIG. 17) configured to provide communications with other nodes (e.g., with other base stations) of the RAN and/or core network CN. The network node may also include processing circuitry 1303 (also referred to as a processor, e.g., corresponding to processing circuitry 4170 of FIG. 17) coupled to the transceiver circuitry, and memory circuitry 1305 (also referred to as memory, e.g., corresponding to device readable medium 4180 of FIG. 17) coupled to the processing circuitry. The memory circuitry 1305 may include computer readable program code that when executed by the processing circuitry 1303 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 1303 may be defined to include memory so that a separate memory circuitry is not required.

[0081] As discussed herein, operations of the RAN node 1300 may be performed by processing circuitry 1303, network interface 1307, and/or transceiver 1301. For example, processing circuitry 1303 may control transceiver 1301 to transmit downlink communications through transceiver 1301 over a radio interface to one or more mobile terminals UEs and/or to receive uplink communications through transceiver 1301 from one or more mobile terminals UEs over a radio interface. Similarly, processing circuitry 1303 may control network interface 1307 to transmit communications through network interface 1307 to one or more other network nodes and/or to receive communications through network interface from one or more other network nodes. Moreover, modules may be stored in memory 1305, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 1303, processing circuitry 1303 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to RAN nodes).

[0082] According to some other embodiments, a network node may be implemented as a core network node without a transceiver. In such embodiments, transmission to a wireless device UE may be initiated by the network node so that transmission to the wireless device is provided through a network node including a transceiver (e.g., through a base station or RAN node). According to embodiments where the network node is a RAN node including a transceiver, initiating transmission may include transmitting through the transceiver.

[0083] FIG. 14 is a block diagram illustrating elements of a network node 1400 of a communication network configured to provide cellular communication according to embodiments of inventive concepts. The network node 1400 can include the policy configuration apparatus 610 or a portion of the policy configuration apparatus 610 such that the network node 1400 can provide a service mesh as part of a servicemesh based composite application. Network node 1400 may be referred to herein as core network (“CN”) node 1400 (e.g., an SMF node, an AMF node, etc.), however, network node 1400 is not intended to be limited to being a CN node as those may be strictly understood (e.g., in view of 3GPP). Network node 1400 is intended to cover any compute device/resource in a wireless communication network including, for example, an edge compute node.

[0084] As shown, the CN node 1400 may include network interface circuitry 1407 (also referred to as a network interface) configured to provide communications with other nodes of the core network and/or the radio access network RAN. The CN node may also include a processing circuitry 1403 (also referred to as a processor) coupled to the network interface circuitry, and memory circuitry 1405 (also referred to as memory) coupled to the processing circuitry. The memory circuitry 1405 may include computer readable program code that when executed by the processing circuitry 1403 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 1403 may be defined to include memory so that a separate memory circuitry is not required.

[0085] As discussed herein, operations of the CN node may be performed by processing circuitry 1403 and/or network interface circuitry 1407. For example, processing circuitry 1403 may control network interface circuitry 1407 to transmit communications through network interface circuitry 1407 to one or more other network nodes and/or to receive communications through network interface circuitry from one or more other network nodes. Moreover, modules may be stored in memory 1405, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 1403, processing circuitry 1403 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to core network nodes).

[0086] According to some other embodiments, a network node may be implemented as an edge compute node with (as illustrated in FIG. 13, for example as part of a RAN node) or without a transceiver (as illustrated in FIG. 14, for example as part of a CN node or connected to a RAN node). The edge compute node can include the policy configuration apparatus 610 or a portion of the policy configuration apparatus 610 such that the edge compute node and/or an edge cloud can provide a service mesh as part of a service-mesh based composite application.

[0087] In terms of exposure, there are two levels of complexity when talking about the different components that can integrate a distributed and composite application. In some embodiments, in the case of exposure to internal domain (e.g., the case of a single-party composite application), a process can take care of updating intra-dependent policies. In additional or alternative embodiments, in the case of exposure to external domain (e.g., the case of a multi-party composite application) the process can take care of updating inter-dependent policies and it will also generate events notifying any updates, then the inter-dependent policies will need to be updated by an external party. Identifying which internal/external elements a particular application component depends on can delimit the different environments/domains that may need to be updated upon configuration changes in a given domain.

[0088] Administrative hierarchies are discussed below. Distributed cloud resources can be shared among different administrative domains by, for example, slicing resources, and allocating them to different domains (e.g., organization or development teams). Then, there can be different hierarchies based on the different service models that can coexist in a cloud environment, i.e. laaS, PaaS, SaaS. Being aware of the different hierarchies of operation or administration of the exposure of multi-party composite services that are cloud-based can be useful. A platform operator may have broader permissions and higher priorities on the policies that are defined in a system. Whereas applications running on top of the platform may be operated by another actor(s). These actors tend to have a more limited permissioned role and their policies may have a lower governance level. Since policies may collide, there is a need for resolving or performing reconciliation of policies, so being aware of the administrative hierarchies could help to handle given collisions.

[0089] Deployment models are discussed below. Information around which deployment model for the control plane of the service mesh(es) can be used for management of the service mesh. Whether the control planes are independent or not, may affect the mechanism to perform portability/migration of the configuration policies related to the application. The migration of a service may need to be done on-the-fly. The strategy applied for migration of the configuration policies related to the service mesh-based exposure of an application can be affected by the deployment model of the control plane of the service mesh. Configuration policies can be either duplicated in or migrated to the destination service mesh.

[0090] As mentioned above, FIG. 7 describes a process for dealing with application portability for multi-domain composite applications, whose exposure is handled by a set of distributed service meshes under different exposure levels, administrative hierarchies, and deployment models.

[0091] In some examples, a multi-domain composite application Ap can include a set of micro-services {Sai, Sbm... , Sxy}. Each of these micro-services can be provided by a software provider x (here called software-level domain x, SDx) and hosted by a platform provider y (here denoted as platform-level domain y, PDy). Each of the micro-services including Ap belongs to different administrative domains at both platform and software levels.

[0092] In some embodiments, a software provider a is subscribed to a platform provider p with different availability zones (AZ), {PDpi, PDpj, ...}. Initially, Sai is hosted in PDi but it needs to be ported from its original location to another location hosted by domain PDj. Both PDi and PDj belong to the same administrative domain (the one for PD p) but in different AZ. PDi relies on service mesh SMi and PDj on SMj for handling service exposure. SMi and SMj constitute a replica of a particular service mesh. This embodiment can be supported by the MCRM deployment model.

[0093] In additional or alternative embodiments, a software provider b is instead subscribed to different platform providers {q, r, ...}, each of them representing independent administrative domains {PDm, PDn, ...}. Initially, Sbm is hosted in PDm but let’s assume that it needs to be ported from its original location to another location hosted by domain PDn. PDm relies on service mesh SMm and PDn on SMn for handling service exposure and they constitute independent service meshes. This embodiment can be supported by the MCMM deployment model.

[0094] In additional or alternative embodiments, when dealing with a complex multi-domain composite application, a process can take care of identifying what exposure level(s) it is dealing with, what deployment models the service mesh relies on, and what administrative hierarchies are involved to perform an appropriate mechanism for porting configuration policies between these domains.

[0095] In some embodiments, per multi-domain composite application, there is a description file including information about the application topology with the dependencies among their different micro-services, including what service mesh is hosting each of those services. In additional or alternative embodiments, per distributed cloud platform, there is a description file with information about the cloud topology with the dependencies among their different service meshes, including in which physical locations they are instantiated and their discovery information to reach each other. In additional or alternative embodiments, upon service portability request, the requester can include information regarding how the source mesh can discover and reach the destination mesh.

[0096] FIG. 8 illustrates an example of porting configuration policies of Sp from source service mesh SMs. Block 805 indicates that the PDs relies on SMs for handling service exposure in that domain. At block 810, SMs receives a request for porting configuration polices related to Sp from there to SMd. At block 820, the SMs looks at its policy configuration registry and identifies all configuration policies that are directly related to Sp, which may need to be ported to SMd, and makes a copy of them, denoted in block 825 as Pps = {Pp1, ... , Ppm}.

[0097] Based on these identified policies, at block 835, the SMs prepares the identified policies before them to be ported to SMd. Some service mesh technologies (e.g., Istio) have started to design support for operators to specify configuration policies as high-level user intent which get converted to a lower-level, for example, component-level policies. During this automated process, some of the policies are aggregated or coupled together (e.g., on additive config policies). For example, the SMs can perform disaggregation and/or decoupling of policies before porting them. Some of these policies may also need to be duplicated to remain in both domains, especially in cases relying on multi-cluster replicated-mesh. Then, these transformed policies are split into two subsets, where Pps* are the ones that need to remain in SMs and Ppsd the ones that need to be ported to SMd. At block 840, policies in Pps* are scheduled for update in SMs. At block 845, the SMs can proceed to port policies Ppsd to the destination domain without de-configuring the source domain.

[0098] At block 850, the SMs evaluates what is the relation between SMs and SMd by looking at topology information regarding the source cloud platform. If they are dependent, it means the exposure level in between them is internal, whereas if they are independent, the exposure level in between is external and needs to be dealt more carefully. At block 855, in case the exposure level is internal (left branch) the SMs proceeds to transmit the policies in Ppsd to SMd so that they are replicated there. Information to be transmitted also includes information regarding topology of the composite application Sp belongs to, Ap. Transmission can be performed in a peer to peer way based on the discovery information provided by the portability requester or based on information regarding the cloud platform topology.

[0099] At block 860, in case the exposure level is external (right branch), the SMs may be more careful so that policies can be ported in a more secure and compatible way. Then, based on Ppsd, the method applies required abstraction transformations in which a particular policy is put in higher-level terms to, for example reduce unnecessary complexity and/or too detailed information or to hide away information that need to be kept private. Now, at block 865, the configuration policies are ready to be transmitted to SMd so that they are migrated there. At block 870, the Ppsd is transmitted along with information regarding topology of the composite application Sp belongs to, Ap. Transmission may be performed in a peer to peer way based on the discovery information provided by the portability requester.

[0100] FIG. 9 is a flow chart illustrating an example of operations performed by a destination service mesh to receive configuration policies from a source service mesh. The PDd can rely on SMd for service exposure management in that domain. At blocks 905 and 910, the SMd receives information from SMs regarding configuration policies to port, Ppsd, together with information regarding composite application topology, Ap related to Sp. At block 915, based on Ppsd, the SMd identifies which of these policies need to be transformed (at block 920) in such a way that they can be integrated in the new service mesh based on SMd’s topology, configuration and requirements. When this is identified, at block 920, the SMd applies required transformations such as policy translation or conversions into an accepted format. This can be useful when SMs and SMd rely on different service mesh technology implementations.

[0101] The SMd may apply additional transformations before they are actually integrated in SMd. At block 925, the SMd identifies which policies need to be normalized based on SMd’s topology, configuration and requirements. At block 930, the SMd applies the required normalization to those policies such as concretization in which policies are converted from high-level to component-level. Another possible normalization to apply is reconciliation which is applied when a particular policy generates collision with an existing policy in SMd; this can be done considering administration hierarchy between colliding policies to sort that out. Another normalization could be deduplication which identifies comparing with existing policies which are redundant and eliminates them. Another one could be applying coupling/aggregation considering existing policies, in which the ones that belong to the same kind and have the same effect are somehow put together.

[0102] After those transformations, at block 935 the SMd generates a set of policies denoted Ppd. These are ready to be integrated into SMd. So, at block 945, the SMd schedules their creation in its configuration registry. After this, at block 950, the SMd proceeds to propagate the effects of porting configuration policies related to Sp and their required updates to all dependent service meshes based on information regarding topology of the composite application, Ap.

[0103] FIG. 10 is a flow chart illustrating an example of operations performed by a destination service mesh to propagate configuration policies to a dependent service mesh.

[0104] Here, the SMd relies on information regarding topology of the composite application, Ap, to realize which service meshes are related to Sp. Also, dependent service meshes may include the source mesh, SMs, and/or the destination mesh, SMd. Furthermore, it can be assumed that each dependent domain PDj relies on a service mesh SMj for handling exposure of its services.

[0105] At block 1020, the SMd begins a loop to perform blocks 1025, 1030, 1035, (1040 or 1045, 1050, and 1055), and 1060 for each dependent service mesh SMj. At block 1025, the SMd identifies which policy updates in Ppd may affect configuration policies in SMj, which are denoted at block 1030 as Ppdj. At block 1035, based on internal information regarding topology of the distributed cloud platform, the SMd evaluates its relation to SMj. If SMj belongs to the same administrative domain, the exposure level is internal and then the method just proceeds, at block 1040, to transmit Ppdj to SMj in order to notify or propagate effects of porting Sp’s policies. Transmitted information also includes application topology information, Ap. To reach SMj, SMd could make use of internal information regarding topology of its distributed cloud platform PDj or external information provided as part of Ap regarding service discovery among service relations. Communication between SMd and SMj can be performed on a peer-to-peer way or based on a publish/subscribe approach where dependent SMs subscribe for getting updates from other SMs.

[0106] If SMj belongs to another independent domain, the exposure level is external, thus at block 1045 the SMd applies on Ppdj abstraction transformations to eliminate unnecessary complexities and/or hide private information. The resultant policies are denoted in block 1050 as Ppdj. At block 1055, SMd transmits Ppdj to SMj together with Ap information. To reach SMj, SMd could make use of external information provided as part of Ap regarding service discovery among service relations. Communication between SMd and SMj can be performed on a peer-to-peer way or based on a publish/subscribe approach where dependent SMs subscribe for getting updates from other SMs. At block 1060, the SMd determines whether to end the loop started in block 1020 based on whether all SMj have been evaluated.

[0107] FIG. 11 is a flow chart illustrating an example of operations performed by a dependent service mesh to receive configuration policies from a destination service mesh. It can be assumed that PDj relies on SMj for service exposure management in that domain. Ab blocks 1105 and 1110, the SMj receives information from SMd regarding relevant updates in configuration, Ppdj, together with information regarding composite application topology, Ap related to Sp.

[0108] At block 1115, SMj identifies which of the policies in SMj’s configuration registry may depend on Ppdj, making a copy of them. At block 1120, these policies are denoted as Ppjd. At block 1125, the SMj applies required transformations such as policy decoupling and/or disaggregation. Then, these transformed policies are split into two subsets, where Ppj are the ones that need to remain unchanged in SMj and Ppjd* the ones that need to be updated in SMj.

[0109] The SMj can apply additional transformations before they are actually updated in SMj. At block 1135, the SMj identifies which policies need to be normalized based on SMj’s topology, configuration and requirements. At block 1130, the SMj applies required normalization to those policies such as concretization in which policies are converted from high-level to component-level. Another possible normalization to apply is reconciliation which is applied when a particular policy generates collision with an existing policy in SMj; this can be done considering administration hierarchy between colliding policies to sort that out. Another normalization could be deduplication which identifies comparing with existing policies which are redundant and eliminates them. Another one could be applying coupling/aggregation considering existing policies, in which the ones that belong to the same kind and have the same effect are somehow put together.

[0110] After those transformations are applied, at block 1140 and 1145, the SMj generates a set of policies denoted Pjd. These are ready to be updated in SMj, so at block 1150, the SMj schedules their update in its configuration registry.

[0111] Operations of the a network node (implemented using the structure of the block diagram of FIG. 13 will now be discussed with reference to the flow charts of FIGS. 15-16 according to some embodiments of inventive concepts. For example, modules may be stored in memory 1305 of FIG. 13, and these modules may provide instructions so that when the instructions of a module are executed by respective network node processing circuitry 1303, processing circuitry 1303 performs respective operations of the flow charts. Although, FIG. 13 is described below in regard to a RAN node, any suitable network node that is configured to provide a service mesh can perform the operations.

[0112] FIG. 15 is a flow chart illustrating an example of operations performed by a first network node configured to provide a service mesh according to some embodiments of inventive concepts. The first network node can be configured to operate in a communications network that includes a second network node. The first network node can be configured to provide a first service mesh and the second network node configured to provide a second service mesh. Exemplary first network nodes include, for example, network node 1300 of FIG. 13; network node 1400 of FIG. 14; network node 4160 of FIG. 17; base station 4412a, 4412b, and 4412c of FIG. 20, and base station 4520 of FIG. 21. Exemplary second network nodes include, for example, network node 1300 of FIG. 13; network node 1400 of FIG. 14; network node 4160 of FIG. 17; base station 4412a, 4412b, and 4412c of FIG. 20, and base station 4520 of FIG. 21.

[0113] At block 1510, processing circuitry 1303 determines to transmit a configuration policy associated with a service to the second service mesh. In some embodiments, the configuration policy includes a second subset of configuration policies. Determining to transmit the configuration policy can include generating a copy of configuration policies directly related to the service in a configuration registry of the first service mesh; splitting the copy of configuration policies into a first subset of configuration policies that will remain on the first service mesh and the second subset of configuration policies that will be provided to the second service mesh; and updating the configuration policies in the configuration registry based on the first subset of configuration policies.

[0114] In additional or alternative embodiments, the first service mesh is a source service mesh and the second service mesh is a destination service mesh. Determining to transmit the configuration policy can include receiving a request to migrate the service from the source service mesh to the destination service mesh. [0115] In additional or alternative embodiments, the first service mesh is a destination service mesh and the second service mesh is a dependent service mesh. Determining to transmit the configuration policy can include receiving the configuration policy from a third network node of the communications network that is configured to provide a source service mesh. In additional or alternative embodiments, the source service mesh and the destination service mesh are from different administrative domains. Receiving the configuration policy from the third network node can include receiving an encrypted version of the configuration policy and generating the configuration policy based on decrypting the encrypted version of the configuration policy. In additional or alternative embodiments, receiving the configuration policy from the third network node can include receiving a set of configuration policies from the third network node (as illustrated in block 1610 of FIG. 16 described below) and normalizing the set of configuration policies based on characteristics of the destination service mesh (as illustrated in block 1620 of FIG. 16 described below). In additional or alternative embodiments, normalizing the set of configuration policies based on characteristics of the destination service mesh includes at least one of concretizing, reconciling, deduplicating, and decoupling the set of configuration policies based on at least one of a topology, configuration, or requirements of the destination service mesh. In additional or alternative embodiments, receiving the configuration policy from the third network node includes registering the configuration policy for creation in a configuration registry of the destination service mesh. [0116] At block 1520, processing circuitry 1303 determines an exposure level associated with the second service mesh relative to the first service mesh. In some embodiments, determining the exposure level includes determining that the exposure level is an internal exposure level based on the first service mesh and the second service mesh being part of an administrative domain. In additional or alternative embodiments, determining the exposure level includes determining that the exposure level is an external exposure level based on the first service mesh and the second service mesh being part of different administrative domains.

[0117] In additional or alternative embodiments, determining the exposure level includes determining that the exposure level is an external exposure level based on the first service mesh and the second service mesh being part of different types of service mesh implementations and or different types of service mesh technologies. [0118] At block 1530, processing circuitry 1303 transmits, via network interface 1307, the configuration policy to the second service mesh based on the exposure level. In some examples, transmitting the configuration policy to the second service mesh based on the exposure level can include selecting or changing a way that the configuration policy is packaged (e.g., encrypted or not) for transmission depending on a value of the exposure level. In additional or alternative examples, transmitting the configuration policy to the second service mesh based on the exposure level can include selecting or changing content of the configuration policy depending on the value of the exposure level. In some embodiments, the exposure level is an internal exposure level and transmitting the configuration policy to the second service mesh based on the exposure level includes transmitting the configuration policy to the second service mesh without encrypting the configuration policy and/or without performing an abstraction transformation on the configuration policy. In additional or alternative embodiments, the exposure level is an external exposure level and transmitting the configuration policy to the second service mesh based on the exposure level includes generating an encrypted version of the configuration policy and transmitting the encrypted version of the configuration policy to the second service mesh.

[0119] In additional or alternative embodiments, the exposure level is an external level and transmitting the configuration policy to the second service mesh based on the exposure level includes generating a policy-migrated version of the configuration policy based on the different types of service mesh implementations and transmitting the policy-migrated version of the configuration policy to the second service mesh.

[0120] In additional or alternative embodiments, the first service mesh is a destination service mesh and the second service mesh is a dependent service mesh. Transmitting the configuration policy to the dependent service mesh can include propagating the configuration policy to dependent service meshes (as illustrated in block 1630 of FIG. 16 described below). In additional or alternative embodiments, the dependent service mesh is a plurality of dependent service meshes. Transmitting the configuration policy to the dependent service mesh can include determining, for each dependent service mesh of the plurality of dependent service meshes, an applicable version of the configuration policy and propagating, to each dependent service mesh of the plurality of dependent service meshes, their applicable version of the configuration policy.

[0121] FIG. 16 is a flow chart illustrating an example of operations performed by a first network node configured to provide a destination mesh according to some embodiments of inventive concepts. The first network node can be configured to operate in a communications network that includes a second network node The first network node can be configured to provide the destination service mesh and the second network node can be configured to provide a dependent service mesh. Exemplary first network nodes include, for example, network node 1300 of FIG. 13; network node 1400 of FIG. 14; network node 4160 of FIG. 17; base station 4412a, 4412b, and 4412c of FIG. 20, and base station 4520 of FIG. 21. Exemplary second network nodes include, for example, network node 1300 of FIG. 13; network node 1400 of FIG. 14; network node 4160 of FIG. 17; base station 4412a, 4412b, and 4412c of FIG. 20, and base station 4520 of FIG. 21.

[0122] At block 1610, processing circuitry 1303 receives, via network interface 1307, a set of configuration policies associated with a service from a third network node configured to provide a source service mesh. In some embodiments, the source service mesh and the destination service mesh are implemented using different service mesh technologies. Receiving the set of configuration policies from the third network node includes receiving a non-translated version of the configuration policy and generating the configuration policy by performing policy translation on the nontranslated version of the configuration policy based on the different service mesh technologies. [0123] At block 1620, processing circuitry 1303 normalizes the set of configuration policies based on characteristics of the destination service mesh. In some embodiments, normalizing the set of configuration policies based on characteristics of the destination service mesh includes at least one of concretizing, reconciling, deduplicating, and decoupling the set of configuration policies based on at least one of a topology, configuration, or requirements of the destination service mesh. In additional or alternative embodiments, receiving the set of configuration policies from the third network node includes registering the configuration policy for creation in a configuration registry of the destination service mesh.

[0124] At block 1630, processing circuitry 1303 transmits, via network interface 1307, a configuration policy of the set of configuration policies to the dependent service mesh. In some embodiments, the dependent service mesh is a plurality of dependent service meshes. Transmitting the configuration policy to the dependent service mesh can include determining, for each dependent service mesh of the plurality of dependent service meshes, an applicable version of the configuration policy and propagating, to each dependent service mesh of the plurality of dependent service meshes, their applicable version of the configuration policy.

[0125] In additional or alternative embodiments, some of the operations discussed above in regard to FIG. 15 can be implemented with the operations of FIG. 16.

[0126] In additional or alternative embodiments, the communications network is a 5th generation, 5G, network. In additional or alternative embodiments, the service is a service of a multi-domain composite application, whose exposure is handled by a set of distributed service meshes under different exposure levels, administrative hierarchies, and deployment models.

[0127] Various operations from the flow chart of FIGS. 15-16 may be optional with respect to some embodiments of network nodes and related methods. For example, in regard to Embodiment 1, described below, operations of blocks 1610, 1620, and 1630 of FIG. 16 may be optional. In regard to Embodiment 13, described below operations of blocks 1510, 1520, and 1530 of FIG. 15 may be optional.

[0128] Example embodiments are discussed below.

[0129] Embodiment 1. A method of operating a first network node in a communications network that includes a second network node, the first network node configured to provide a first service mesh and the second network node configured to provide a second service mesh, the method comprising: determining (1510) to transmit a configuration policy associated with a service to the second service mesh; determining (1520) an exposure level associated with the second service mesh relative to the first service mesh; and transmitting (1530) the configuration policy to the second service mesh based on the exposure level.

[0130] Embodiment 2. The method of Embodiment 1 , wherein the configuration policy comprises a second subset of configuration policies, wherein determining to transmit the configuration policy comprises: generating a copy of configuration policies directly related to the service in a configuration registry of the first service mesh; splitting the copy of configuration policies into a first subset of configuration policies that will remain on the first service mesh and the second subset of configuration policies that will be provided to the second service mesh; and updating the configuration policies in the configuration registry based on the first subset of configuration policies.

[0131] Embodiment 3. The method of any of Embodiments 1-2, wherein determining the exposure level comprises determining that the exposure level is an internal exposure level based on the first service mesh and the second service mesh being part of an administrative domain, wherein transmitting the configuration policy to the second service mesh based on the exposure level comprises transmitting the configuration policy to the second service mesh without performing an abstraction transformation on the configuration policy.

[0132] Embodiment 4. The method of any of Embodiments 1-2, wherein determining the exposure level comprises determining that the exposure level is an external exposure level based on the first service mesh and the second service mesh being part of different administrative domains, wherein transmitting the configuration policy to the second service mesh based on the exposure level comprises: generating an encrypted version of the configuration policy; and transmitting the encrypted version of the configuration policy to the second service mesh.

[0133] Embodiment 5. The method of any of Embodiments 1-2, wherein determining the exposure level comprises determining that the exposure level is an external exposure level based on the first service mesh and the second service mesh being part of different types of service mesh implementations, wherein transmitting the configuration policy to the second service mesh based on the exposure level comprises: generating a policy-migrated version of the configuration policy based on the different types of service mesh implementations; and transmitting the policy-migrated version of the configuration policy to the second service mesh.

[0134] Embodiment 6. The method of any of Embodiments 1-5, wherein the first service mesh is a source service mesh, wherein the second service mesh is a destination service mesh, and wherein determining to transmit the configuration policy comprises receiving a request to migrate the service from the source service mesh to the destination service mesh.

[0135] Embodiment 7. The method of any of Embodiments 1-5, wherein the first service mesh is a destination service mesh, wherein the second service mesh is a dependent service mesh; wherein determining to transmit the configuration policy comprises receiving the configuration policy from a third network node of the communications network that is configured to provide a source service mesh, and wherein transmitting the configuration policy to the dependent service mesh comprises propagating the configuration policy to dependent service meshes.

[0136] Embodiment s. The method of Embodiment 7, wherein the dependent service mesh is part of a plurality of dependent service meshes, wherein transmitting the configuration policy to the dependent service mesh comprises: determining, for each dependent service mesh of the plurality of dependent service meshes, an applicable version of the configuration policy; and propagating, to each dependent service mesh of the plurality of dependent service meshes, their applicable version of the configuration policy. [0137] Embodiment 9. The method of any of Embodiments 7-8, wherein the source service mesh and the destination service mesh are from different administrative domains, wherein receiving the configuration policy from the third network node comprises: receiving an encrypted version of the configuration policy; and generating the configuration policy based on decrypting the encrypted version of the configuration policy.

[0138] Embodiment 10. The method of any of Embodiments 7-9, wherein the source service mesh and the destination service mesh are implemented using different service mesh technologies, wherein receiving the configuration policy from the third network node comprises: receiving a non-translated version of the configuration policy; and generating the configuration policy by performing policy translation on the non-translated version of the configuration policy based on the different service mesh technologies.

[0139] Embodiment 11. The method of any of Embodiments 7-10, wherein receiving the configuration policy from the third network node comprises: receiving (1610) a set of configuration policies from the third network node; and normalizing (1620) the set of configuration policies based on characteristics of the destination service mesh.

[0140] Embodiment 12. The method of Embodiment 11, wherein normalizing the set of configuration policies based on characteristics of the destination service mesh comprises at least one of concretizing, reconciling, deduplicating, and decoupling the set of configuration policies based on at least one of a topology, configuration, or requirements of the destination service mesh.

[0141] Embodiment 13. The method of any of Embodiments 7-12, wherein receiving the configuration policy from the third network node comprises registering the configuration policy for creation in a configuration registry of the destination service mesh.

[0142] Embodiment 14. The method of any of Embodiments 1-13, wherein the communications network is a 5th generation, 5G, network, and wherein the service is a service of a multi-domain composite application, whose exposure is handled by a set of distributed service meshes under different exposure levels, administrative hierarchies, and deployment models.

[0143] Embodiment 15. A method of operating a first network node in a communications network that includes a second network node, the first network node configured to provide a destination service mesh and the second network node configured to provide a dependent service mesh, the method comprising: receiving (1610) a set of configuration policies associated with a service from a third network node of the communications network that is configured to provide a source service mesh; normalizing (1620) the set of configuration policies based on characteristics of the destination service mesh; and transmitting (1630) a configuration policy of the set of configuration policies to the dependent service mesh.

[0144] Embodiment 16. The method of Embodiment 15, wherein the dependent service mesh is part of a plurality of dependent service meshes, wherein transmitting the configuration policy to the dependent service mesh comprises: determining, for each dependent service mesh of the plurality of dependent service meshes, an applicable version of the configuration policy; and propagating, to each dependent service mesh of the plurality of dependent service meshes, their applicable version of the configuration policy.

[0145] Embodiment 17. The method of any of Embodiments 15-16, wherein the source service mesh and the destination service mesh are from different administrative domains, wherein receiving the set of configuration policies from the third network node comprises: receiving an encrypted version of the configuration policy; and generating the configuration policy based on decrypting the encrypted version of the configuration policy.

[0146] Embodiment 18. The method of any of Embodiments 15-17, wherein the source service mesh and the destination service mesh are implemented using different service mesh technologies, wherein receiving the set of configuration policies from the third network node comprises: receiving a non-translated version of the configuration policy; and generating the configuration policy by performing policy translation on the non-translated version of the configuration policy based on the different service mesh technologies.

[0147] Embodiment 19. The method of Embodiment 15, wherein normalizing the set of configuration policies based on characteristics of the destination service mesh comprises at least one of concretizing, reconciling, deduplicating, and decoupling the set of configuration policies based on at least one of a topology, configuration, or requirements of the destination service mesh.

[0148] Embodiment 20. The method of any of Embodiments 15-19, wherein receiving the set of configuration policies from the third network node comprises registering the configuration policy for creation in a configuration registry of the destination service mesh.

[0149] Embodiment 21. The method of any of Embodiments 15-20 further comprising: determining (1520) an exposure level associated with the dependent service mesh relative to the destination service mesh, wherein transmitting the configuration policy to the dependent service mesh comprises transmitting the configuration policy to the dependent service mesh based on the exposure level.

[0150] Embodiment 22. The method of Embodiment 21, wherein determining the exposure level comprises determining that the exposure level is an internal exposure level based on the destination service mesh and the dependent service mesh being part of an administrative domain, wherein transmitting the configuration policy to the dependent service mesh based on the exposure level comprises transmitting the configuration policy to the dependent service mesh without performing an abstraction transformation on the configuration policy.

[0151] Embodiment 23. The method of Embodiment 21, wherein determining the exposure level comprises determining that the exposure level is an external exposure level based on the destination service mesh and the dependent service mesh being part of different administrative domains, wherein transmitting the configuration policy to the dependent service mesh based on the exposure level comprises: generating an encrypted version of the configuration policy; and transmitting the encrypted version of the configuration policy to the dependent service mesh.

[0152] Embodiment 24. The method of Embodiment 21, wherein determining the exposure level comprises determining that the exposure level is an external exposure level based on the destination service mesh and the dependent service mesh being part of different types of service mesh implementations, wherein transmitting the configuration policy to the dependent service mesh based on the exposure level comprises: generating a policy-migrated version of the configuration policy based on the different types of service mesh implementations; and transmitting the policy-migrated version of the configuration policy to the dependent service mesh.

[0153] Embodiment 25. The method of any of Embodiments 15-24, wherein the configuration policy comprises a second subset of configuration policies, wherein determining to transmit the configuration policy comprises: generating a copy of configuration policies directly related to the service in a configuration registry of the destination service mesh; splitting the copy of configuration policies into a first subset of configuration policies that will remain on the destination service mesh and the second subset of configuration policies that will be provided to the dependent service mesh; and updating the configuration policies in the configuration registry based on the first subset of configuration policies.

[0154] Embodiment 26. The method of any of Embodiments 15-25, wherein the communications network is a 5 ^th generation, 5G, network, and wherein the service is a service of a multi-domain composite application, whose exposure is handled by a set of distributed service meshes under different exposure levels, administrative hierarchies, and deployment models.

[0155] Embodiment 27. A first network node (1300, 1400) configured to operate in a wireless communication network that includes a second network node, the first network node configured to provide a first service mesh and the second network node configured to provide a second service mesh, the first network node comprising: processing circuitry (1303, 1403); and memory (1305, 1405) coupled to the processing circuitry and having instructions stored therein that are executable by the processing circuitry to cause the first network node to perform operations comprising: determining (1510) to transmit a configuration policy associated with a service to the second service mesh; determining (1520) an exposure level associated with the second service mesh relative to the first service mesh; and transmitting (1530) the configuration policy to the second service mesh based on the exposure level.

[0156] Embodiment 28. A first network node (1300, 1400) configured to operate in a wireless communication network that includes a second network node, the first network node configured to provide a first service mesh and the second network node configured to provide a second service mesh, the first network node comprising: processing circuitry (1303, 1403); and memory (1305, 1405) coupled to the processing circuitry and having instructions stored therein that are executable by the processing circuitry to cause the first network node to perform operations comprising any of the operations of Embodiments 1-14.

[0157] Embodiment 29. A first network node (1300, 1400) configured to operate in a wireless communication network that includes a second network node, the first network node configured to provide a first service mesh and the second network node configured to provide a second service mesh, the first network node adapted to perform operations comprising: determining (1510) to transmit a configuration policy associated with a service to the second service mesh; determining (1520) an exposure level associated with the second service mesh relative to the first service mesh; and transmitting (1530) the configuration policy to the second service mesh based on the exposure level. [0158] Embodiment 30. A first network node (1300, 1400) configured to operate in a wireless communication network that includes a second network node, the first network node configured to provide a first service mesh and the second network node configured to provide a second service mesh, the first network node adapted to perform operations comprising any of the operations of Embodiments 1-14. [0159] Embodiment 31. A computer program comprising program code to be executed by processing circuitry (1303, 1403) of a first network node (1300, 1400) configured to operate in a wireless communication network that includes a second network node, the first network node configured to provide a first service mesh and the second network node configured to provide a second service mesh, whereby execution of the program code causes the first network node to perform operations comprising: determining (1510) to transmit a configuration policy associated with a service to the second service mesh; determining (1520) an exposure level associated with the second service mesh relative to the first service mesh; and transmitting (1530) the configuration policy to the second service mesh based on the exposure level.

[0160] Embodiment 32. A computer program comprising program code to be executed by processing circuitry (1303, 1403) of a first network node (1300, 1400) configured to operate in a wireless communication network that includes a second network node, the first network node configured to provide a first service mesh and the second network node configured to provide a second service mesh, whereby execution of the program code causes the first network node to perform operations comprising any of the operations of Embodiments 1-14.

[0161] Embodiment 33. A computer program product comprising a non- transitory storage medium including program code to be executed by processing circuitry (1303, 1403) of a first network node (1300, 1400) configured to operate in a wireless communication network that includes a second network node, the first network node configured to provide a first service mesh and the second network node configured to provide a second service mesh, whereby execution of the program code causes the first network node to perform operations comprising: determining (1510) to transmit a configuration policy associated with a service to the second service mesh; determining (1520) an exposure level associated with the second service mesh relative to the first service mesh; and transmitting (1530) the configuration policy to the second service mesh based on the exposure level.

[0162] Embodiment 34. A computer program product comprising a non- transitory storage medium including program code to be executed by processing circuitry (1303, 1403) of a first network node (1300, 1400) configured to operate in a wireless communication network that includes a second network node, the first network node configured to provide a first service mesh and the second network node configured to provide a second service mesh, whereby execution of the program code causes the first network node to perform operations comprising any of the operations of Embodiments 1-14.

[0163] Embodiment 35. A first network node (1300, 1400) configured to operate in a wireless communication network that includes a second network node, the first network node configured to provide a destination service mesh and the second network node configured to provide a dependent service mesh, the first network node comprising: processing circuitry (1303, 1403); and memory (1305, 1405) coupled to the processing circuitry and having instructions stored therein that are executable by the processing circuitry to cause the first network node to perform operations comprising: receiving (1610) a set of configuration policies associated with a service from a third network node of the communications network that is configured to provide a source service mesh; normalizing (1620) the set of configuration policies based on characteristics of the destination service mesh; and transmitting (1630) a configuration policy of the set of configuration policies to the dependent service mesh.

[0164] Embodiment 36. A first network node (1300, 1400) configured to operate in a wireless communication network that includes a second network node, the first network node configured to provide a destination service mesh and the second network node configured to provide a dependent service mesh, the first network node comprising: processing circuitry (1303, 1403); and memory (1305, 1405) coupled to the processing circuitry and having instructions stored therein that are executable by the processing circuitry to cause the first network node to perform operations comprising any of the operations of Embodiments 15-26.

[0165] Embodiment 37. A first network node (1300, 1400) configured to operate in a wireless communication network that includes a second network node, the first network node configured to provide a destination service mesh and the second network node configured to provide a dependent service mesh, the first network node adapted to perform operations comprising: receiving (1610) a set of configuration policies associated with a service from a third network node of the communications network that is configured to provide a source service mesh; normalizing (1620) the set of configuration policies based on characteristics of the destination service mesh; and transmitting (1630) a configuration policy of the set of configuration policies to the dependent service mesh.

[0166] Embodiment 38. A first network node (1300, 1400) configured to operate in a wireless communication network that includes a second network node, the first network node configured to provide a destination service mesh and the second network node configured to provide a dependent service mesh, the first network node adapted to perform operations comprising any of the operations of Embodiments 15-26.

[0167] Embodiment 39. A computer program comprising program code to be executed by processing circuitry (1303, 1403) of a first network node (1300, 1400) configured to operate in a wireless communication network that includes a second network node, the first network node configured to provide a destination service mesh and the second network node configured to provide a dependent service mesh, whereby execution of the program code causes the first network node to perform operations comprising: receiving (1610) a set of configuration policies associated with a service from a third network node of the communications network that is configured to provide a source service mesh; normalizing (1620) the set of configuration policies based on characteristics of the destination service mesh; and transmitting (1630) a configuration policy of the set of configuration policies to the dependent service mesh.

[0168] Embodiment 40. A computer program comprising program code to be executed by processing circuitry (1303, 1403) of a first network node (1300, 1400) configured to operate in a wireless communication network that includes a second network node, the first network node configured to provide a destination service mesh and the second network node configured to provide a dependent service mesh, whereby execution of the program code causes the first network node to perform operations comprising any of the operations of Embodiments 15-26.

[0169] Embodiment 41. A computer program product comprising a non- transitory storage medium including program code to be executed by processing circuitry (1303, 1403) of a first network node (1300, 1400) configured to operate in a wireless communication network that includes a second network node, the first network node configured to provide a destination service mesh and the second network node configured to provide a dependent service mesh, whereby execution of the program code causes the first network node to perform operations comprising: receiving (1610) a set of configuration policies associated with a service from a third network node of the communications network that is configured to provide a source service mesh; normalizing (1620) the set of configuration policies based on characteristics of the destination service mesh; and transmitting (1630) a configuration policy of the set of configuration policies to the dependent service mesh.

[0170] Embodiment 42. A computer program product comprising a non- transitory storage medium including program code to be executed by processing circuitry (1303, 1403) of a first network node (1300, 1400) configured to operate in a wireless communication network that includes a second network node, the first network node configured to provide a destination service mesh and the second network node configured to provide a dependent service mesh, whereby execution of the program code causes the first network node to perform operations comprising any of the operations of Embodiments 15-26.

[0171] Explanations are provided below for various abbreviations/acronyms used in the present disclosure. Abbreviation Explanation

SM Service Mesh

MCSM Multi-Cluster, Single-Mesh

MCRM Multi-Cluster, Replicated-Mesh

MCMM Multi-Cluster, Multi-Mesh laaS Infrastructure as a Service

PaaS Platform as a Service

SaaS Software as a Service

DNS Domain Name System

PKI Public Key Infrastructure

RBAC Role- Based Access Control

AZ Availability Zone

HA High Availability

SNI Service Name Indicator

GW Gateway

API Application Program Interface

A Application

S Service

PD Platform Domain

SD Software Domain

AD Administrative Domain

[0172] References are described below

W. Li, Y. Lemieux, J. Gao och Y. Han, ’’Service Mesh: Challenges, State of the Art, and Future Research Opportunities,” San Francisco East Bay, CA, USA, 2019.

Istio, ’’What is Istio?,” 2019. [Online], Available: https://istio.io/docs/concepts/what-is-istio/. [Anvand September 2019],

Linkerd, ’’Linkerd Overview,” 2019. [Online], Available: https://linkerd.io/2/overview/. [Anvand September 2019],

Istio, ’’Istio Deployment Models,” 2019. [Online], Available: https://istio.io/docs/ops/deployment/deployment-models/. [Anvand 15 Sep 2019],

ViaSat, ’’Federated, Policy-driven Service Meshes for Distributed Sofware Systems”. US Patent US 9,519,520 B2, 13 Dec 2016. [0173] Additional explanation is provided below.

[0174] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.

[0175] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0176] FIG. 17 illustrates a wireless network in accordance with some embodiments.

[0177] Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in FIG. 17. For simplicity, the wireless network of FIG. 17 only depicts network 4106, network nodes 4160 and 4160b, and WDs 4110, 4110b, and 4110c (also referred to as mobile terminals). In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node 4160 and wireless device (WD) 4110 are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network.

[0178] The wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.

[0179] Network 4106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

[0180] Network node 4160 and WD 4110 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.

[0181] As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Yet further examples of network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.

[0182] In FIG. 17, network node 4160 includes processing circuitry 4170, device readable medium 4180, interface 4190, auxiliary equipment 4184, power source 4186, power circuitry 4187, and antenna 4162. Although network node 4160 illustrated in the example wireless network of FIG. 17 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node 4160 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 4180 may comprise multiple separate hard drives as well as multiple RAM modules). [0183] Similarly, network node 4160 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node 4160 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeB’s. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, network node 4160 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium 4180 for the different RATs) and some components may be reused (e.g., the same antenna 4162 may be shared by the RATs). Network node 4160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 4160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 4160.

[0184] Processing circuitry 4170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 4170 may include processing information obtained by processing circuitry 4170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

[0185] Processing circuitry 4170 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 4160 components, such as device readable medium 4180, network node 4160 functionality. For example, processing circuitry 4170 may execute instructions stored in device readable medium 4180 or in memory within processing circuitry 4170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 4170 may include a system on a chip (SOC).

[0186] In some embodiments, processing circuitry 4170 may include one or more of radio frequency (RF) transceiver circuitry 4172 and baseband processing circuitry 4174. In some embodiments, radio frequency (RF) transceiver circuitry 4172 and baseband processing circuitry 4174 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 4172 and baseband processing circuitry 4174 may be on the same chip or set of chips, boards, or units [0187] In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry 4170 executing instructions stored on device readable medium 4180 or memory within processing circuitry 4170. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 4170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 4170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 4170 alone or to other components of network node 4160, but are enjoyed by network node 4160 as a whole, and/or by end users and the wireless network generally.

[0188] Device readable medium 4180 may comprise any form of volatile or nonvolatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or nonvolatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 4170. Device readable medium 4180 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 4170 and, utilized by network node 4160. Device readable medium 4180 may be used to store any calculations made by processing circuitry 4170 and/or any data received via interface 4190. In some embodiments, processing circuitry 4170 and device readable medium 4180 may be considered to be integrated.

[0189] Interface 4190 is used in the wired or wireless communication of signalling and/or data between network node 4160, network 4106, and/or WDs 4110. As illustrated, interface 4190 comprises port(s)/terminal(s) 4194 to send and receive data, for example to and from network 4106 over a wired connection. Interface 4190 also includes radio front end circuitry 4192 that may be coupled to, or in certain embodiments a part of, antenna 4162. Radio front end circuitry 4192 comprises filters 4198 and amplifiers 4196. Radio front end circuitry 4192 may be connected to antenna 4162 and processing circuitry 4170. Radio front end circuitry may be configured to condition signals communicated between antenna 4162 and processing circuitry 4170. Radio front end circuitry 4192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 4192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 4198 and/or amplifiers 4196. The radio signal may then be transmitted via antenna 4162.

Similarly, when receiving data, antenna 4162 may collect radio signals which are then converted into digital data by radio front end circuitry 4192. The digital data may be passed to processing circuitry 4170. In other embodiments, the interface may comprise different components and/or different combinations of components.

[0190] In certain alternative embodiments, network node 4160 may not include separate radio front end circuitry 4192, instead, processing circuitry 4170 may comprise radio front end circuitry and may be connected to antenna 4162 without separate radio front end circuitry 4192. Similarly, in some embodiments, all or some of RF transceiver circuitry 4172 may be considered a part of interface 4190. In still other embodiments, interface 4190 may include one or more ports or terminals 4194, radio front end circuitry 4192, and RF transceiver circuitry 4172, as part of a radio unit (not shown), and interface 4190 may communicate with baseband processing circuitry 4174, which is part of a digital unit (not shown).

[0191] Antenna 4162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 4162 may be coupled to radio front end circuitry 4192 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 4162 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omnidirectional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna 4162 may be separate from network node 4160 and may be connectable to network node 4160 through an interface or port.

[0192] Antenna 4162, interface 4190, and/or processing circuitry 4170 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 4162, interface 4190, and/or processing circuitry 4170 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.

[0193] Power circuitry 4187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 4160 with power for performing the functionality described herein. Power circuitry 4187 may receive power from power source 4186. Power source 4186 and/or power circuitry 4187 may be configured to provide power to the various components of network node 4160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 4186 may either be included in, or external to, power circuitry 4187 and/or network node 4160. For example, network node 4160 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 4187. As a further example, power source 4186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 4187. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.

[0194] Alternative embodiments of network node 4160 may include additional components beyond those shown in FIG. 17 that may be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node 4160 may include user interface equipment to allow input of information into network node 4160 and to allow output of information from network node 4160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 4160.

[0195] As used herein, wireless device (WD) refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customerpremise equipment (CPE), a vehicle-mounted wireless terminal device, etc. A WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to- infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (loT) scenario, a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node. The WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the WD may be a UE implementing the 3GPP narrow band internet of things (NB-loT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

[0196] As illustrated, wireless device 4110 includes antenna 4111, interface 4114, processing circuitry 4120, device readable medium 4130, user interface equipment 4132, auxiliary equipment 4134, power source 4136 and power circuitry 4137. WD 4110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 4110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD 4110.

[0197] Antenna 4111 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 4114. In certain alternative embodiments, antenna 4111 may be separate from WD 4110 and be connectable to WD 4110 through an interface or port. Antenna 4111 , interface 4114, and/or processing circuitry 4120 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna 4111 may be considered an interface.

[0198] As illustrated, interface 4114 comprises radio front end circuitry 4112 and antenna 4111. Radio front end circuitry 4112 comprise one or more filters 4118 and amplifiers 4116. Radio front end circuitry 4112 is connected to antenna 4111 and processing circuitry 4120, and is configured to condition signals communicated between antenna 4111 and processing circuitry 4120. Radio front end circuitry 4112 may be coupled to or a part of antenna 4111. In some embodiments, WD 4110 may not include separate radio front end circuitry 4112; rather, processing circuitry 4120 may comprise radio front end circuitry and may be connected to antenna 4111. Similarly, in some embodiments, some or all of RF transceiver circuitry 4122 may be considered a part of interface 4114. Radio front end circuitry 4112 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 4112 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 4118 and/or amplifiers 4116. The radio signal may then be transmitted via antenna 4111. Similarly, when receiving data, antenna 4111 may collect radio signals which are then converted into digital data by radio front end circuitry 4112. The digital data may be passed to processing circuitry 4120. In other embodiments, the interface may comprise different components and/or different combinations of components.

[0199] Processing circuitry 4120 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD 4110 components, such as device readable medium 4130, WD 4110 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 4120 may execute instructions stored in device readable medium 4130 or in memory within processing circuitry 4120 to provide the functionality disclosed herein.

[0200] As illustrated, processing circuitry 4120 includes one or more of RF transceiver circuitry 4122, baseband processing circuitry 4124, and application processing circuitry 4126. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry 4120 of WD 4110 may comprise a SOC. In some embodiments, RF transceiver circuitry 4122, baseband processing circuitry 4124, and application processing circuitry 4126 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry 4124 and application processing circuitry 4126 may be combined into one chip or set of chips, and RF transceiver circuitry 4122 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry 4122 and baseband processing circuitry 4124 may be on the same chip or set of chips, and application processing circuitry 4126 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry 4122, baseband processing circuitry 4124, and application processing circuitry 4126 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry 4122 may be a part of interface 4114. RF transceiver circuitry 4122 may condition RF signals for processing circuitry 4120.

[0201] In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry 4120 executing instructions stored on device readable medium 4130, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 4120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 4120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 4120 alone or to other components of WD 4110, but are enjoyed by WD 4110 as a whole, and/or by end users and the wireless network generally.

[0202] Processing circuitry 4120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 4120, may include processing information obtained by processing circuitry 4120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 4110, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. [0203] Device readable medium 4130 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 4120. Device readable medium 4130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 4120. In some embodiments, processing circuitry 4120 and device readable medium 4130 may be considered to be integrated. [0204] User interface equipment 4132 may provide components that allow for a human user to interact with WD 4110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 4132 may be operable to produce output to the user and to allow the user to provide input to WD 4110. The type of interaction may vary depending on the type of user interface equipment 4132 installed in WD 4110. For example, if WD 4110 is a smart phone, the interaction may be via a touch screen; if WD 4110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment 4132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 4132 is configured to allow input of information into WD 4110, and is connected to processing circuitry 4120 to allow processing circuitry 4120 to process the input information. User interface equipment 4132 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 4132 is also configured to allow output of information from WD 4110, and to allow processing circuitry 4120 to output information from WD 4110. User interface equipment 4132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 4132, WD 4110 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.

[0205] Auxiliary equipment 4134 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 4134 may vary depending on the embodiment and/or scenario.

[0206] Power source 4136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD 4110 may further comprise power circuitry 4137 for delivering power from power source 4136 to the various parts of WD 4110 which need power from power source 4136 to carry out any functionality described or indicated herein. Power circuitry 4137 may in certain embodiments comprise power management circuitry. Power circuitry 4137 may additionally or alternatively be operable to receive power from an external power source; in which case WD 4110 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry 4137 may also in certain embodiments be operable to deliver power from an external power source to power source 4136. This may be, for example, for the charging of power source 4136. Power circuitry 4137 may perform any formatting, converting, or other modification to the power from power source 4136 to make the power suitable for the respective components of WD 4110 to which power is supplied.

[0207] FIG. 18 illustrates a user Equipment in accordance with some embodiments.

[0208] FIG. 18 illustrates one embodiment of a UE in accordance with various aspects described herein. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).

Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE 42200 may be any UE identified by the 3rd Generation Partnership Project (3GPP), including a NB-loT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE 4200, as illustrated in FIG. 18, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term WD and UE may be used interchangeable. Accordingly, although FIG. 18 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.

[0209] In FIG. 18, UE 4200 includes processing circuitry 4201 that is operatively coupled to input/output interface 4205, radio frequency (RF) interface 4209, network connection interface 4211, memory 4215 including random access memory (RAM) 4217, read-only memory (ROM) 4219, and storage medium 4221 or the like, communication subsystem 4231 , power source 4213, and/or any other component, or any combination thereof. Storage medium 4221 includes operating system 4223, application program 4225, and data 4227. In other embodiments, storage medium 4221 may include other similar types of information. Certain UEs may utilize all of the components shown in FIG. 18, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc. [0210] In FIG. 18, processing circuitry 4201 may be configured to process computer instructions and data. Processing circuitry 4201 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 4201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

[0211] In the depicted embodiment, input/output interface 4205 may be configured to provide a communication interface to an input device, output device, or input and output device. UE 4200 may be configured to use an output device via input/output interface 4205. An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from UE 4200. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. UE 4200 may be configured to use an input device via input/output interface 4205 to allow a user to capture information into UE 4200. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

[0212] In FIG. 18, RF interface 4209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface 4211 may be configured to provide a communication interface to network 4243a. Network 4243a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 4243a may comprise a Wi-Fi network. Network connection interface 4211 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface 4211 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.

[0213] RAM 4217 may be configured to interface via bus 4202 to processing circuitry 4201 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM 4219 may be configured to provide computer instructions or data to processing circuitry 4201 . For example, ROM 4219 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium 4221 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable readonly memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium 4221 may be configured to include operating system 4223, application program 4225 such as a web browser application, a widget or gadget engine or another application, and data file 4227. Storage medium 4221 may store, for use by UE 4200, any of a variety of various operating systems or combinations of operating systems.

[0214] Storage medium 4221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium 4221 may allow UE 4200 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium 4221 , which may comprise a device readable medium. [0215] In FIG. 18, processing circuitry 4201 may be configured to communicate with network 4243b using communication subsystem 4231. Network 4243a and network 4243b may be the same network or networks or different network or networks. Communication subsystem 4231 may be configured to include one or more transceivers used to communicate with network 4243b. For example, communication subsystem 4231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.11 , CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter 4233 and/or receiver 4235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 4233 and receiver 4235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

[0216] In the illustrated embodiment, the communication functions of communication subsystem 4231 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem 4231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 4243b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 4243b may be a cellular network, a Wi-Fi network, and/or a near-field network. Power source 4213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 4200.

[0217] The features, benefits and/or functions described herein may be implemented in one of the components of UE 4200 or partitioned across multiple components of UE 4200. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem 4231 may be configured to include any of the components described herein. Further, processing circuitry 4201 may be configured to communicate with any of such components over bus 4202. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 4201 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry 4201 and communication subsystem 4231. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.

[0218] FIG. 19 illustrates a virtualization environment in accordance with some embodiments.

[0219] FIG. 19 is a schematic block diagram illustrating a virtualization environment 4300 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).

[0220] In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 4300 hosted by one or more of hardware nodes 4330. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.

[0221] The functions may be implemented by one or more applications 4320 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications 4320 are run in virtualization environment 4300 which provides hardware 4330 comprising processing circuitry 4360 and memory 4390. Memory 4390 contains instructions 4395 executable by processing circuitry 4360 whereby application 4320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

[0222] Virtualization environment 4300, comprises general-purpose or specialpurpose network hardware devices 4330 comprising a set of one or more processors or processing circuitry 4360, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory 4390-1 which may be non-persistent memory for temporarily storing instructions 4395 or software executed by processing circuitry 4360. Each hardware device may comprise one or more network interface controllers (NICs) 4370, also known as network interface cards, which include physical network interface 4380. Each hardware device may also include non-transitory, persistent, machine-readable storage media 4390-2 having stored therein software 4395 and/or instructions executable by processing circuitry 4360. Software 4395 may include any type of software including software for instantiating one or more virtualization layers 4350 (also referred to as hypervisors), software to execute virtual machines 4340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

[0223] Virtual machines 4340 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 4350 or hypervisor. Different embodiments of the instance of virtual appliance 4320 may be implemented on one or more of virtual machines 4340, and the implementations may be made in different ways.

[0224] During operation, processing circuitry 4360 executes software 4395 to instantiate the hypervisor or virtualization layer 4350, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 4350 may present a virtual operating platform that appears like networking hardware to virtual machine 4340.

[0225] As shown in FIG. 19, hardware 4330 may be a standalone network node with generic or specific components. Hardware 4330 may comprise antenna 43225 and may implement some functions via virtualization. Alternatively, hardware 4330 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) 43100, which, among others, oversees lifecycle management of applications 4320.

[0226] Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0227] In the context of NFV, virtual machine 4340 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of virtual machines 4340, and that part of hardware 4330 that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 4340, forms a separate virtual network elements (VNE).

[0228] Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines 4340 on top of hardware networking infrastructure 4330 and corresponds to application 4320 in FIG. 19. [0229] In some embodiments, one or more radio units 43200 that each include one or more transmitters 43220 and one or more receivers 43210 may be coupled to one or more antennas 43225. Radio units 43200 may communicate directly with hardware nodes 4330 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.

[0230] In some embodiments, some signalling can be effected with the use of control system 43230 which may alternatively be used for communication between the hardware nodes 4330 and radio units 43200.

[0231] FIG. 20 illustrates a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments. [0232] With reference to FIG. 20, in accordance with an embodiment, a communication system includes telecommunication network 4410, such as a 3GPP- type cellular network, which comprises access network 4411 , such as a radio access network, and core network 4414. Access network 4411 comprises a plurality of base stations 4412a, 4412b, 4412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 4413a, 4413b, 4413c. Each base station 4412a, 4412b, 4412c is connectable to core network 4414 over a wired or wireless connection 4415. A first UE 4491 located in coverage area 4413c is configured to wirelessly connect to, or be paged by, the corresponding base station 4412c. A second UE 4492 in coverage area 4413a is wirelessly connectable to the corresponding base station 4412a. While a plurality of UEs 4491, 4492 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 4412.

[0233] Telecommunication network 4410 is itself connected to host computer 4430, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. Host computer 4430 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections 4421 and 4422 between telecommunication network 4410 and host computer 4430 may extend directly from core network 4414 to host computer 4430 or may go via an optional intermediate network 4420. Intermediate network 4420 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 4420, if any, may be a backbone network or the Internet; in particular, intermediate network 4420 may comprise two or more subnetworks (not shown).

[0234] The communication system of FIG. 20 as a whole enables connectivity between the connected UEs 4491 , 4492 and host computer 4430. The connectivity may be described as an over-the-top (OTT) connection 4450. Host computer 4430 and the connected UEs 4491, 4492 are configured to communicate data and/or signaling via OTT connection 4450, using access network 4411, core network 4414, any intermediate network 4420 and possible further infrastructure (not shown) as intermediaries. OTT connection 4450 may be transparent in the sense that the participating communication devices through which OTT connection 4450 passes are unaware of routing of uplink and downlink communications. For example, base station 4412 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 4430 to be forwarded (e.g., handed over) to a connected UE 4491. Similarly, base station 4412 need not be aware of the future routing of an outgoing uplink communication originating from the UE 4491 towards the host computer 4430.

[0235] FIG. 21 illustrates a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments.

[0236] Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to FIG. 21. In communication system 4500, host computer 4510 comprises hardware 4515 including communication interface 4516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 4500. Host computer 4510 further comprises processing circuitry 4518, which may have storage and/or processing capabilities. In particular, processing circuitry 4518 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer 4510 further comprises software 4511 , which is stored in or accessible by host computer 4510 and executable by processing circuitry 4518. Software 4511 includes host application 4512. Host application 4512 may be operable to provide a service to a remote user, such as UE 4530 connecting via OTT connection 4550 terminating at UE 4530 and host computer 4510. In providing the service to the remote user, host application 4512 may provide user data which is transmitted using OTT connection 4550.

[0237] Communication system 4500 further includes base station 4520 provided in a telecommunication system and comprising hardware 4525 enabling it to communicate with host computer 4510 and with UE 4530. Hardware 4525 may include communication interface 4526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 4500, as well as radio interface 4527 for setting up and maintaining at least wireless connection 4570 with UE 4530 located in a coverage area (not shown in FIG. 21) served by base station 4520. Communication interface 4526 may be configured to facilitate connection 4560 to host computer 4510. Connection 4560 may be direct or it may pass through a core network (not shown in FIG. 21) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware 4525 of base station 4520 further includes processing circuitry 4528, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station 4520 further has software 4521 stored internally or accessible via an external connection.

[0238] Communication system 4500 further includes UE 4530 already referred to. Its hardware 4535 may include radio interface 4537 configured to set up and maintain wireless connection 4570 with a base station serving a coverage area in which UE 4530 is currently located. Hardware 4535 of UE 4530 further includes processing circuitry 4538, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE 4530 further comprises software 4531, which is stored in or accessible by UE 4530 and executable by processing circuitry 4538. Software 4531 includes client application 4532. Client application 4532 may be operable to provide a service to a human or non-human user via UE 4530, with the support of host computer 4510. In host computer 4510, an executing host application 4512 may communicate with the executing client application 4532 via OTT connection 4550 terminating at UE 4530 and host computer 4510. In providing the service to the user, client application 4532 may receive request data from host application 4512 and provide user data in response to the request data. OTT connection 4550 may transfer both the request data and the user data. Client application 4532 may interact with the user to generate the user data that it provides.

[0239] It is noted that host computer 4510, base station 4520 and UE 4530 illustrated in FIG. 21 may be similar or identical to host computer 4430, one of base stations 4412a, 4412b, 4412c and one of UEs 4491 , 4492 of FIG. 20, respectively. This is to say, the inner workings of these entities may be as shown in FIG. 21 and independently, the surrounding network topology may be that of FIG. 20.

[0240] In FIG. 21, OTT connection 4550 has been drawn abstractly to illustrate the communication between host computer 4510 and UE 4530 via base station 4520, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from UE 4530 or from the service provider operating host computer 4510, or both. While OTT connection 4550 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network). [0241] Wireless connection 4570 between UE 4530 and base station 4520 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments may improve the performance of OTT services provided to UE 4530 using OTT connection 4550, in which wireless connection 4570 forms the last segment. More precisely, the teachings of these embodiments may improve the random access speed and/or reduce random access failure rates and thereby provide benefits such as faster and/or more reliable random access.

[0242] A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring OTT connection 4550 between host computer 4510 and UE 4530, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection 4550 may be implemented in software 4511 and hardware 4515 of host computer 4510 or in software 4531 and hardware 4535 of UE 4530, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 4550 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 4511, 4531 may compute or estimate the monitored quantities. The reconfiguring of OTT connection 4550 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 4520, and it may be unknown or imperceptible to base station 4520. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer 4510’s measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software 4511 and 4531 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 4550 while it monitors propagation times, errors etc.

[0243] FIG. 22 illustrates methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments

[0244] FIG. 22 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGS. 20-21. For simplicity of the present disclosure, only drawing references to FIG. 22 will be included in this section. In step 4610, the host computer provides user data. In substep 4611 (which may be optional) of step 4610, the host computer provides the user data by executing a host application. In step 4620, the host computer initiates a transmission carrying the user data to the UE. In step 4630 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 4640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0245] FIG. 23 illustrates methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.

[0246] FIG. 23 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGS. 20-21. For simplicity of the present disclosure, only drawing references to FIG. 23 will be included in this section. In step 4710 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step 4720, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 4730 (which may be optional), the UE receives the user data carried in the transmission.

[0247] FIG. 24 illustrates methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments

[0248] FIG. 24 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGS. 20-21. For simplicity of the present disclosure, only drawing references to FIG. 24 will be included in this section. In step 4810 (which may be optional), the UE receives input data provided by the host computer.

Additionally or alternatively, in step 4820, the UE provides user data. In substep 4821 (which may be optional) of step 4820, the UE provides the user data by executing a client application. In substep 4811 (which may be optional) of step 4810, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep 4830 (which may be optional), transmission of the user data to the host computer. In step 4840 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

[0249] FIG. 25 illustrates methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments

[0250] FIG. 25 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGS. 20-21. For simplicity of the present disclosure, only drawing references to FIG. 25 will be included in this section. In step 4910 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 4920 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 4930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0251] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), specialpurpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

[0252] The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

[0253] Further definitions and embodiments are discussed below.

[0254] In the above-description of various embodiments of present inventive concepts, it is to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of present inventive concepts. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which present inventive concepts belong. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0255] When an element is referred to as being "connected", "coupled", "responsive", or variants thereof to another element, it can be directly connected, coupled, or responsive to the other element or intervening elements may be present. In contrast, when an element is referred to as being "directly connected", "directly coupled", "directly responsive", or variants thereof to another element, there are no intervening elements present. Like numbers refer to like elements throughout. Furthermore, "coupled", "connected", "responsive", or variants thereof as used herein may include wirelessly coupled, connected, or responsive. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. Well-known functions or constructions may not be described in detail for brevity and/or clarity. The term "and/or" (abbreviated 7”) includes any and all combinations of one or more of the associated listed items.

[0256] It will be understood that although the terms first, second, third, etc. may be used herein to describe various elements/operations, these elements/operations should not be limited by these terms. These terms are only used to distinguish one element/operation from another element/operation. Thus a first element/operation in some embodiments could be termed a second element/operation in other embodiments without departing from the teachings of present inventive concepts. The same reference numerals or the same reference designators denote the same or similar elements throughout the specification.

[0257] As used herein, the terms "comprise", "comprising", "comprises", "include", "including", "includes", "have", "has", "having", or variants thereof are open- ended, and include one or more stated features, integers, elements, steps, components or functions but does not preclude the presence or addition of one or more other features, integers, elements, steps, components, functions or groups thereof. Furthermore, as used herein, the common abbreviation "e.g.", which derives from the Latin phrase "exempli gratia," may be used to introduce or specify a general example or examples of a previously mentioned item, and is not intended to be limiting of such item. The common abbreviation "i.e.", which derives from the Latin phrase "id est," may be used to specify a particular item from a more general recitation.

[0258] Example embodiments are described herein with reference to block diagrams and/or flowchart illustrations of computer-implemented methods, apparatus (systems and/or devices) and/or computer program products. It is understood that a block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions that are performed by one or more computer circuits. These computer program instructions may be provided to a processor circuit of a general purpose computer circuit, special purpose computer circuit, and/or other programmable data processing circuit to produce a machine, such that the instructions, which execute via the processor of the computer and/or other programmable data processing apparatus, transform and control transistors, values stored in memory locations, and other hardware components within such circuitry to implement the functions/acts specified in the block diagrams and/or flowchart block or blocks, and thereby create means (functionality) and/or structure for implementing the functions/acts specified in the block diagrams and/or flowchart block(s).

[0259] These computer program instructions may also be stored in a tangible computer-readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instructions which implement the functions/acts specified in the block diagrams and/or flowchart block or blocks. Accordingly, embodiments of present inventive concepts may be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc.) that runs on a processor such as a digital signal processor, which may collectively be referred to as "circuitry," "a module" or variants thereof.

[0260] It should also be noted that in some alternate implementations, the functions/acts noted in the blocks may occur out of the order noted in the flowcharts. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functional ity/acts involved. Moreover, the functionality of a given block of the flowcharts and/or block diagrams may be separated into multiple blocks and/or the functionality of two or more blocks of the flowcharts and/or block diagrams may be at least partially integrated. Finally, other blocks may be added/inserted between the blocks that are illustrated, and/or blocks/operations may be omitted without departing from the scope of inventive concepts. Moreover, although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

[0261] Many variations and modifications can be made to the embodiments without substantially departing from the principles of the present inventive concepts. All such variations and modifications are intended to be included herein within the scope of present inventive concepts. Accordingly, the above disclosed subject matter is to be considered illustrative, and not restrictive, and the examples of embodiments are intended to cover all such modifications, enhancements, and other embodiments, which fall within the spirit and scope of present inventive concepts. Thus, to the maximum extent allowed by law, the scope of present inventive concepts are to be determined by the broadest permissible interpretation of the present disclosure including the examples of embodiments and their equivalents, and shall not be restricted or limited by the foregoing detailed description.