Measurements for enterprise using OAM group identifier

Abstract

A method performed by a management service consumer in a wireless communication network includes receiving a request to obtain measurement data, wherein the request includes a group identifier associated with a group of network resources for which measurement data is requested, identifying a network resource associated with the group identifier, and transmitting a measurement data request to a management service producer in the wireless communication network that is associated with the network resource. The measurement data request requests that the management service producer provide first measurement data associated with the identified network resource.

Description

MEASUREMENTS FOR ENTERPRISE USING OAM GROUP IDENTIFIERTECHNICAL FIELD

[0001] The present disclosure relates to wireless communication systems, and in particular to methods for obtaining enterprise measurement data in wireless communication systems.BACKGROUND

[0002] A simplified wireless communication system is illustrated in Figure 1A. The system includes a UE 100 that communicates with one or more access nodes 210, 220 using radio connections 107, 108. The access nodes 210, 220 are connected to a core network node 106. The access nodes 210-220 are part of a radio access network 105.

[0003] For wireless communication systems pursuant to 3GPP Evolved Packet System, EPS (also referred to as Long Term Evolution, LTE, or 4G) standard specifications, such as specified in 3GPP TS 36.300 and related specifications, the access nodes 220, 220 correspond typically to an Evolved NodeB (eNB) and the core network node 106 corresponds typically to either a Mobility Management Entity (MME) and / or a Serving Gateway (SGW). The eNB is part of the radio access network (RAN) 105, which in this case is the E-UTRAN (Evolved Universal Terrestrial Radio Access Network), while the MME and SGW are both part of the EPC (Evolved Packet Core network).

[0004] For wireless communication systems pursuant to 3GPP 5G System, 5GS (also referred to as New Radio, NR, or 5G) standard specifications, such as specified in 3GPP TS 38.300 and related specifications, the access nodes 103-104 correspond typically to a 5G NodeB (gNB) and the network node 106 corresponds typically to either an Access and Mobility Management Function (AMF) and / or a User Plane Function (UPF). The gNB is part of the radio access network 100, which in this case is the NG-RAN (Next Generation Radio Access Network), while the AMF and UPF are both part of the 5G Core Network (5GC).

[0005] It is expected that 5G will support many new scenarios and use cases and will be an enabler for the Internet of Things (loT). It is expected that NG systems will provide connectivity to a wide range of new devices such as sensors, smart wearables, vehicles, machines, etc. Flexibility would be then a key property in NG Systems. This isreflected in the security requirement for network access that are mandating the support of alternative authentication methods and different types of credentials than the usual AKA credentials pre-provisioned by the operator and securely stored in the UICC. This would allow factory owners or enterprises to leverage their own identity and credential management systems for authentication and access network security.

[0006] Figure IB illustrates an example 5G system architecture. As shown in Figure IB, functional entities (e.g., AMF, SMF, etc.) are connected to a logical communication bus. The Access and Mobility Management Function (AMF) communicates with the radio access network (RAN) and one or more user equipments (UE), and the session management function (SMF) communicates with the user plane function (UPF). This way of modelling the system is also known as “service-based architecture.”

[0007] The various functions illustrated in Figure IB will now be described.

[0008] The Access and Mobility Management function (AMF) supports termination of non-access stratum (NAS signalling), NAS ciphering and integrity protection, registration management, connection management, mobility management, access authentication and authorization, security context management.

[0009] The Session Management function (SMF) supports session management (session establishment, modification, release), UE IP address allocation and management, DHCP functions, termination of NAS signalling related to session management, downlink (DL) data notification, and traffic steering configuration for user plane function (UPF) for proper traffic routing.

[0010] The User plane function (UPF) supports packet routing and forwarding, packet inspection, QoS handling, acts as external PDU session point of interconnect to Data Network (DN), and is an anchor point for intra- and inter-RAT mobility.

[0011] The Policy Control Function (PCF) supports unified policy framework, providing policy rules to CP functions, and access subscription information for policy decisions in UDR.

[0012] The Authentication Server Function (AUSF) acts as an authentication server.

[0013] The Unified Data Management (UDM) supports generation of Authentication and Key Agreement (AKA) credentials, user identification handling, access authorization, and subscription management.

[0014] The Application Function (AF) supports application influence on traffic routing, accessing NEF, and interaction with policy framework for policy control.

[0015] The Network Exposure function (NEF) supports exposure of capabilities and events, secure provision of information from external application to 3GPP network, and translation of internal / external information.

[0016] The NF Repository function (NRF) supports service discovery function and maintains the network function (NF) profile and available NF instances.

[0017] The Network Slice Selection Function (NSSF) supports selection of the Network Slice instances to serve the UE, determining the allowed NSSAI, and determining the AMF set to be used to serve the UE.

[0018] In 5G networks, 0AM (Operations, Administration, and Maintenance) refers to various functions that manage, control and maintain the network infrastructure, which helps to ensure the effective delivery of services to end users. Some of the functions of 0AM in 5G include network monitoring and management, fault detection and diagnosis, configuration management, performance optimization and security management.

[0019] In the interaction between an enterprise that uses network services and a mobile network operator (MNO), the enterprise relies on the MNO to fulfill service requirements of the enterprise. The service requirements and the expected performance of the network are documented in a service level agreement. An enterprise may utilize a network slice to obtain services that are suitable for the needs of the enterprise in terms of data rate, throughput, latency, and other requirements.

[0020] The MNO configures the network so that the service requirements of the enterprise can be met, and the performance of the service can be monitored to avoid degradation of the quality of service. The performance information if needed may be provided to the enterprise.

[0021] Observability procedures for a network are typically specified in the relevant wireless communication standard along with standardized measurements and key performance indicators (KPIs). Some examples of standardized measurements are shown in Table 1.

[0022] Table 1 - Examples of measurements and filters

[0023] From Table 1, it can be observed that a measurement that is produced by a node can have subgroups that are identified with a filter. In a network slicing scenario, the filter used would typically be the single network slices selection assistance information (SNSSAI) and in a 5G virtual network (VN) scenario, the filter used would be the InternalGroupId.SUMMARY

[0024] Some embodiments described herein enable more flexible management of network resources by defining 0AM groups that can be used by an enterprise to manage various resources across a network. For example, a method performed by a management service consumer in a wireless communication network according to some embodiments includes receiving a request to obtain measurement data, wherein the request includes a group identifier associated with a group of network resources for which measurement data is requested, identifying a network resource associated with the group identifier, and transmitting a measurement data request to a management service producer in the wireless communication network that is associated with the network resource. The measurement data request requests that the management service producer provide first measurement data associated with the identified network resource.

[0025] The request may be received from an enterprise operator and the method may further include receiving, from the management service producer, a measurement data response containing the first measurement data, and transmitting the first measurement data to the enterprise operator.

[0026] The group of network resources may include one or more UEs, virtual network groups, S-NSSAIs, rating groups, service identifiers, and / or application identifiers.

[0027] The method may further include receiving, from the enterprise operator, a group setup request requesting setup of a measurement group, wherein the group setuprequest identifies a plurality of network resources, establishing a group identifier associated with the plurality of network resources, and transmitting a setup response to the enterprise entity, the setup response including the group identifier.

[0028] The method may further include notifying a network function of an association between the group identifier and at least one of the plurality of network resources.

[0029] The network function may include at least one of a unified data management, UDM, function, a network slice selection function and / or a policy control function.

[0030] The management service producer may include at least one of a user plane function, an access and mobility management function, or a session management function.

[0031] The method may further include notifying the management service producer of the association between the group identifier and at least one of the plurality of network resources.

[0032] The management service consumer may include an operations, administration and maintenance (0AM) group handler.

[0033] The group identifier may be associated with a plurality of different types of network resources including UEs, virtual network groups, S -NS SAI, rating groups, service identifiers, and / or application identifiers.

[0034] The measurement data request may include the group identifier, and the measurement data request may request measurement data for resources associated with the group identifier.

[0035] The management service consumer may be implemented in an open radio access network, ORAN, network node, and in some embodiments as a logical function in the ORAN node.

[0036] In some embodiments, the management service consumer may be implemented as part of a Service Management and Orchestration, SMO, framework of an ORAN telecommunication system.

[0037] In some embodiments, the management service consumer may be implemented as an rApp in aNon-Real Time RAN Intelligent Controller within an ORAN telecommunication system.

[0038] A method performed by an enterprise operator according to some embodiments includes transmitting, to a management service consumer, a request to obtain first measurement data, wherein the request includes a group identifier associated with agroup of network resources for which measurement data is requested, and receiving a measurement data response containing the first measurement data.

[0039] The measurement data response may be received from the management service consumer. In some embodiments, the measurement data response may be received from a management service producer that generates measurement data associated with at least one of the network resources associated with the group identifier.

[0040] The method may further include transmitting, to the management service consumer, a group setup request requesting setup of a measurement group, wherein the group setup request identifies a plurality of network resources, and receiving a setup response from the management service consumer, the setup response including the group identifier.

[0041] A method performed by a management service producer in a wireless communication network according to some embodiments includes receiving a request from a management service consumer for measurement data, wherein the request includes a group identifier associated with a group of network resources for which measurement data is requested, identifying a network resource associated with the group identifier, obtaining first measurement data associated with the network resource, and transmitting a measurement response, the measurement response including the first measurement data.

[0042] The measurement response may be transmitted to the management service consumer.

[0043] The request may identify an enterprise operator, and the measurement response may be transmitted to the enterprise operator.

[0044] The management service producer may be implemented in an open radio access network (ORAN) network node, and in some embodiments as a logical function in the ORAN node.

[0045] In some embodiments, the management service producer may be implemented as part of a Service Management and Orchestration framework of an ORAN telecommunication system.

[0046] In some embodiments, the management service producer may be implemented as an rApp in aNon-Real Time RAN Intelligent Controller within an ORAN telecommunication system.

[0047] A network node according to some embodiments includes processing circuitry configured to perform any of the operations described above and power supply circuitry configured to supply power to the processing circuitry. Some embodiments provide a network node adapted to perform any of the operations described above.BRIEF DESCRIPTION OF THE DRAWINGS

[0048] Figure 1A illustrates simplified wireless communication system.

[0049] Figure IB illustrates an example 5G system architecture.

[0050] Figure 2 illustrates a procedure for setting up an 0AM group according to some embodiments.

[0051] Figure 3 illustrates a message flow between an MnS consumer and an MnS producer for setting up an 0AM group according to some embodiments.

[0052] Figure 4 illustrates message flows in a process for obtaining measurements by 0AM group according to some embodiments.

[0053] Figure 5 illustrates message flows in a process for obtaining measurements by 0AM group according to further embodiments.

[0054] Figure 6 illustrates a method performed by a management service consumer in a wireless communication network according to some embodiments.

[0055] Figure 7 illustrates a method performed by an enterprise operator according to some embodiments.

[0056] Figure 8 illustrates a method performed by a management service producer in a wireless communication network according to some embodiments.

[0057] Figure 9 shows an example of a communication system in accordance with some embodiments.

[0058] Figure 10 shows a UE in accordance with some embodiments.

[0059] Figure 11 shows a network node in accordance with some embodiments.

[0060] Figure 12 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.DETAILED DESCRIPTION

[0061] An enterprise may utilize many different resources, such as assets and / or services, within a communication network. Such assets and / or services may include UEs, VN groups, network slices (S-NSSAI), rating groups, and applications. The 3GPP standard documents do not describe how an enterprise can obtain measurements associated with the various resources associated with a single enterprise. This is particularly true in cases in which the enterprise does not have its own 5G VN group (and associated InternalGroupID) or its own dedicated network slice (S-NSSAI).

[0062] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. In particular, some embodiments introduce the concept of an 0AM group that allows an enterprise to manage various resources within a network. That is, an enterprise can utilize multiple resources from a network operator, such as one or more shared network slices, internet of things (loT) devices, non-public networks (NPNs) and 5G VN groups. All of these resources together make up the service provided by the network operator to the enterprise. The enterprise would like to have a single view of the service performance measurements, KPIs, and fault notifications associated with these resources.

[0063] To allow the desired granularity of measurements, KPIs and fault notifications to be on an enterprise service level, some embodiments introduce a new group identifier that may be used by 0AM to manage the measurements, KPIs and fault notifications related to a single enterprise.

[0064] That is, some embodiments introduce new group identifier that can be used to group together all resources belonging to the same enterprise, such as subscribers / UEs, S- NSSAIs, 5G VNs, NPNs etc. The group identifier may allow the management system to observe the performance of the packet data unit (PDU) sessions for that group independent of how network slices are shared or simultaneously used.

[0065] Certain embodiments described herein may provide one or more technical advantages. In particular, certain embodiments described herein may improve the ability of a network to provide customized measurement data to an enterprise user of the network.

[0066] The existence of the new group identifier may make it possible for the 0AM system to have more flexibility in setting up measurements and for the management service (MnS) consumer to filter measurements on a group level.

[0067] The MnS consumer may obtain measurements based on the enterprise requirements, and the MnS producer may avoid producing measurements that are not required by the enterprise. This may result in decreased signaling and processing requirements.

[0068] Moreover, the enterprise may be able to obtain better knowledge about the performance of the resources it uses.

[0069] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0070] For an enterprise to obtain measurements that are relevant to its services and their usage, there is a need to have a flexible way of configuring measurements in a 5GS.An enterprise can have several types of resources and services allocated to the enterprise for use at any one time. Some embodiments provide a new OAM group that can be associated to groups of UEs, 5G VN groups, Network slices, Applications, and other resources.

[0071] Figure 2 illustrates a procedure for setting up an OAM group. As shown therein, an enterprise 10 transmits a group setup request 202 to an MnS consumer 20. The MnS consumer 20 may be an OAM group handler in a 5GS core network. The group setup request 202 may identify the resources that the enterprise 10 wants included in the OAM group.

[0072] The OAM group handler 20 may set up an OAM group by connecting the OAM group to a number of resources, such as UEs in the UDM network function (NF), 5G VN group(s) in the UDM NF, S-NSSAI (s) in the NSSF, and rating group(s), service id(s), and / or application id(s) in the PCF.

[0073] The MnS consumer 20 informs the enterprise 10 that OAM group has been set up via a group setup response 204.

[0074] To set up the OAM group, the MnS consumer 20 may contact one or more network functions that are associated with or that are responsible for managing the resources identified in the group setup request 202. For example, referring to Figure 3, the MnS consumer 20 may send a message, such as a FeasibilityCheckAndReservationJob request 302 to an MnS producer 30 that is associated with or responsible for managing a resource that is identified in the group setup request 202.

[0075] The MnS consumer 20 may store the OAM group identifier as a filter to be used for obtaining measurements. For example, Table 2 illustrates an example of the use of the OAM group identifier as a measurement filter.

[0076] Table 2 - Examples of measurements and filters

[0077] In some embodiments, the MnS consumer 20 and / or the MnS producer 30 may be implemented in an one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in a telecommunication network that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization).

[0078] A network node acting as an MnS consumer 20 and / or an MnS producer 30 may support an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an MnS consumer 20 and / or MnS producer 30 may be a logical node in a physical node. Furthermore, an MnS consumer 20 and / or MnS producer 30 may be implemented in a virtualization environment in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration (SMO) Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies. In some embodiments, the MnS consumer 20 and / or MnS producer 30 may be implemented as a logical function within an SMO. Moreover, in some embodiments, the MnS consumer 20 and / or MnS producer 30 may be implemented as an rApp in aNon-Real Time RAN Intelligent Controller (Non-RT RIC) within an SMO in ORAN implementation.

[0079] Figure 4 illustrates message flows in a process for obtaining measurements by 0AM group. After an 0AM group has been set up, the enterprise 10 sends a measurement request 402 to an MnS consumer 20. The measurement request 402 identifies the 0AM group for which measurements are requested and may identify particular measurements to be provided in response to the request. The MnS consumer first determines the resources that are associated with the 0AM group indicated in the measurement request 402, and then determines which MnS producers 30A, 30B, 30C are associated with the identified resources. For example, the MnS producers may include a UPF, an AMF, an SMF, or other network function.

[0080] Once the relevant MnS producers 30A, 30B, 30C have been identified, the MnS consumer sends measurement requests 404a, 404b, 404c, respectively, to the identified MnS producers 30A, 30B, 30C. In some embodiments, The measurement requests 404a, 404b, 404c may identify the resources for which measurements are needed. In some embodiments, the measurement requests 404a, 404b, 404c may identify the 0AM group for which measurements are requested. The measurement requests 404a, 404b, 404c may further identify the measurements needed from the individual MnS producers 30A, 30B, 30C.

[0081] In response to the measurement requests, the MnS producers 30A, 30B ,30C, obtain the requested measurement data and transmit the measurement data back to the MnS consumer 20 in respective measurement responses 406a, 406b, 406c. In some embodiments, the MnS producers 30A, 30B ,30C may transmit measurement data to the MnS consumer 20 periodically in response to the measurement requests 404a, 404b, 404c.

[0082] The MnS consumer 20 collects the measurement data and transmits the measurement data to the enterprise 10 in a measurement response 408. When the measurement data is provided periodically, the MnS consumer 20 may the measurement data and transmit the measurement data to the enterprise 10 periodically in multiple measurement responses 408.

[0083] Figure 5 illustrates message flows in a process for obtaining measurements by 0AM group according to further embodiments. After an 0AM group has been set up, the enterprise 10 sends a measurement request 502 to an MnS consumer 20. The measurement request 502 identifies the 0AM group for which measurements are requested and may identify particular measurements to be provided in response to the request. The MnS consumer first determines the resources that are associated with the 0AM group indicated in the measurement request 502, and then determines which MnS producers 30A, 30B, 30C are associated with the identified resources. For example, the MnS producers may include a UPF, an AMF, an SMF, or other network function.

[0084] Once the relevant MnS producers 30A, 30B, 30C have been identified, the MnS consumer sends measurement requests 504a, 504b, 504c, respectively, to the identified MnS producers 30A, 30B, 30C. The measurement requests 504a, 504b, 504c may identify the enterprise 10 and may, for example, include a network address, internet protocol address or other address of the enterprise 10.

[0085] In some embodiments, the measurement requests 504a, 504b, 504c may identify the resources for which measurements are needed. In some embodiments, the measurement requests 504a, 504b, 504c may identify the 0AM group for whichmeasurements are requested. The measurement requests 504a, 504b, 504c may further identify the measurements needed from the individual MnS producers 30A, 30B, 30C.

[0086] In response to the measurement requests, the MnS producers 30A, 30B ,30C, obtain the requested measurement data and transmit the measurement data directly to the enterprise 10 in respective measurement responses 506a, 506b, 506c. In some embodiments, the MnS producers 30A, 30B, 30C may transmit measurement data to the enterprise 10 periodically in response to the measurement requests 504a, 504b, 504c.

[0087] Figure 6 illustrates a method performed by a management service consumer in a wireless communication network. The method includes receiving (block 602) a request (402, 502) to obtain measurement data. The he request includes a group identifier associated with a group of network resources for which measurement data is requested. The method further includes identifying (block 604) a network resource associated with the group identifier, and transmitting (block 606) a measurement data request (404, 504) to a management service producer (30) in the wireless communication network that is associated with the network resource. The measurement data request requests that the management service producer provide first measurement data associated with the identified network resource.

[0088] The request may be received from an enterprise operator and the method may further include receiving, from the management service producer, a measurement data response (406) containing the first measurement data, and transmitting (808) the first measurement data to the enterprise operator.

[0089] The group of network resources may include one or more user equipment (UE), virtual network groups, single network slice selection assistance information (S- NSSAI), rating groups, service identifiers, and / or application identifiers.

[0090] The may further include receiving, from the enterprise operator, a group setup request (202) requesting setup of a measurement group. The group setup request identifies a plurality of network resources, and the method further includes establishing a group identifier associated with the plurality of network resources, and transmitting a setup response (204) to the enterprise entity, the setup response including the group identifier.

[0091] The method may further include notifying a network function of an association between the group identifier and at least one of the plurality of network resources.

[0092] The network function may include at least one of a unified data management, UDM, function, a network slice selection function, NSSF, and / or a policy control function, PCF.

[0093] The management service producer may include at least one of a user plane function, UPF, an access and mobility management function, AMF, or a session management function, SMF.

[0094] The method may further include notifying the management service producer of the association between the group identifier and at least one of the plurality of network resources.

[0095] The management service consumer may be an operations, administration and maintenance (0AM), group handler.

[0096] The group identifier may be associated with a plurality of different types of network resources including UEs, virtual network groups, S-NSSAI, rating groups, service identifiers, and / or application identifiers.

[0097] The measurement data request may include the group identifier, and the measurement data request may request measurement data for resources associated with the group identifier.

[0098] Figure 7 illustrates a method performed by an enterprise operator. The method includes transmitting (block 702), to a management service consumer, a request (402, 502) to obtain first measurement data. The request includes a group identifier associated with a group of network resources for which measurement data is requested. The method further includes receiving (block 704) a measurement data response (406, 506) containing the first measurement data.

[0099] The measurement data response may be received from the management service consumer.

[0100] In some embodiments, the measurement data response may be received from a management service producer that generates measurement data associated with at least one of the network resources associated with the group identifier.

[0101] The method may further include transmitting, to the management service consumer, a group setup request (202) requesting setup of a measurement group. The group setup request identifies a plurality of network resources, and the method further includes receiving a setup response (204) from the management service consumer, the setup response including the group identifier.

[0102] Figure 8 illustrates a method performed by a management service producer in a wireless communication network. The method includes receiving (block 802) a request (404, 504) from a management service consumer for measurement data. The request includes a group identifier associated with a group of network resources for which measurement datais requested, and the method further includes identifying (block 804) a network resource associated with the group identifier, obtaining (block 806) first measurement data associated with the network resource, and transmitting (block 808) a measurement response (404, 504), the measurement response including the first measurement data.

[0103] The measurement response may be transmitted to the management service consumer.

[0104] In some embodiments, the request identifies an enterprise operator, and the measurement response is transmitted to the enterprise operator.

[0105] Figure 9 shows an example of a communication system 900 in accordance with some embodiments.

[0106] In the example, the communication system 900 includes a telecommunication network 902 that includes an access network 904, such as a radio access network (RAN), and a core network 906, which includes one or more core network nodes 908. The access network 904 includes one or more access network nodes, such as network nodes 910a and 910b (one or more of which may be generally referred to as network nodes 910), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non- 3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 902 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 902 that supports an ORAN specification (e.g., a specification published by the O- RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 902, including one or more network nodes 910 and / or core network nodes 908.

[0107] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, anopen fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 02 interface defined by the O- RAN Alliance or comparable technologies. The network nodes 910 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 912a, 912b, 912c, and 912d (one or more of which may be generally referred to as UEs 912) to the core network 906 over one or more wireless connections.

[0108] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 900 may include any number of wired or wireless networks, network nodes, UEs, 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. The communication system 900 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0109] The UEs 912 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 910 and other communication devices. Similarly, the network nodes 910 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 912 and / or with other network nodes or equipment in the telecommunication network 902 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 902.

[0110] In the depicted example, the core network 906 connects the network nodes 910 to one or more host computing systems, such as host 916. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 906 includes one more core network nodes (e.g., core network node 908) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptionsthereof are generally applicable to the corresponding components of the core network node 908. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).[oni] The host 916 may be under the ownership or control of a service provider other than an operator or provider of the access network 904 and / or the telecommunication network 902. The host 916 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0112] As a whole, the communication system 900 of Figure 9 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0113] In some examples, the telecommunication network 902 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 902 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 902. For example, the telecommunications network 902 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB)services to other UEs, and / or Massive Machine Type Communication (mMTC)ZMassive loT services to yet further UEs.

[0114] In some examples, the UEs 912 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 904 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 904. Additionally, a UE may be configured for operating in single- or multi-RAT or multistandard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi -radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0115] In the example, the hub 914 communicates with the access network 904 to facilitate indirect communication between one or more UEs (e.g., UE 912c and / or 912d) and network nodes (e.g., network node 910b). In some examples, the hub 914 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 914 may be a broadband router enabling access to the core network 906 for the UEs. As another example, the hub 914 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 910, or by executable code, script, process, or other instructions in the hub 914. As another example, the hub 914 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 914 may be a content source. For example, for a UE that is a VR device, display, loudspeaker, or other media delivery device, the hub 914 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 914 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 914 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0116] The hub 914 may have a constant / persistent or intermittent connection to the network node 910b. The hub 914 may also allow for a different communication scheme and / or schedule between the hub 914 and UEs (e.g., UE 912c and / or 912d), and between the hub 914 and the core network 906. In other examples, the hub 914 is connected to the core network 906 and / or one or more UEs via a wired connection. Moreover, the hub 914 may beconfigured to connect to an M2M service provider over the access network 904 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 910 while still connected via the hub 914 via a wired or wireless connection. In some embodiments, the hub 914 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 910b. In other embodiments, the hub 914 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 910b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0117] Figure 10 shows a UE 1000 in accordance with some embodiments. The UE 1000 presents additional details of some embodiments of the UE 912 of Figure 1. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage / playback device, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), an Augmented Reality (AR) or Virtual Reality (VR) device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB- loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0118] A UE may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a 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).

[0119] The UE 1000 includes processing circuitry 1002 that is operatively coupled via a bus 1004 to an input / output interface 1006, a power source 1008, a memory 1010, acommunication interface 1012, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 10. 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.

[0120] The processing circuitry 1002 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1010. The processing circuitry 1002 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, 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 1002 may include multiple central processing units (CPUs).

[0121] In the example, the input / output interface 1006 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include 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. An input device may allow a user to capture information into the UE 1000. Examples of an input device 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, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0122] In some embodiments, the power source 1008 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 1008 may further include power circuitry for delivering power from the power source 1008 itself, and / or an external power source, to the various parts of the UE 1000 via input circuitry or aninterface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1008. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1008 to make the power suitable for the respective components of the UE 1000 to which power is supplied.

[0123] The memory 1010 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 1010 includes one or more application programs 1014, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1016. The memory 1010 may store, for use by the UE 1000, any of a variety of various operating systems or combinations of operating systems.

[0124] The memory 1010 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), 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 tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 1010 may allow the UE 1000 to access instructions, application programs and 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 as or in the memory 1010, which may be or comprise a device-readable storage medium.

[0125] The processing circuitry 1002 may be configured to communicate with an access network or other network using the communication interface 1012. The communication interface 1012 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1022. The communication interface 1012 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wirelesscommunication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 1018 and / or a receiver 1020 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1018 and receiver 1020 may be coupled to one or more antennas (e.g., antenna 1022) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0126] In the illustrated embodiment, communication functions of the communication interface 1012 may include cellular communication, Wi-Fi communication, LPWAN communication, 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. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0127] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1012, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0128] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0129] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limitedto, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 1000 shown in Figure 10.

[0130] As yet another specific example, in an loT scenario, a UE 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 UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0131] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0132] Figure 11 shows a network node 1100 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodesinclude, 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)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0133] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may 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, distributed units (e.g., in an O- RAN access node) 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).

[0134] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, 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), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0135] The network node 1100 includes a processing circuitry 1102, a memory 1104, a communication interface 1106, and a power source 1108. The network node 1100 may be composed of multiple physically separate components (e.g., aNodeB 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 the network node 1100 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 NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 1100 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1104 for different RATs) and some components may be reused (e.g., a same antenna 1110 may be shared by different RATs). The network node 1100 may also include multiple sets ofthe various illustrated components for different wireless technologies integrated into network node 1100, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) 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 1100.

[0136] The processing circuitry 1102 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 1100 components, such as the memory 1104, to provide network node 1100 functionality.

[0137] In some embodiments, the processing circuitry 1102 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1102 includes one or more of radio frequency (RF) transceiver circuitry 1112 and baseband processing circuitry 1114. In some embodiments, the radio frequency (RF) transceiver circuitry 1112 and the baseband processing circuitry 1114 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 1112 and baseband processing circuitry 1114 may be on the same chip or set of chips, boards, or units.

[0138] The memory 1104 may comprise any form of volatile or non-volatile 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 non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 1102. The memory 1104 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 1102 and utilized by the network node 1100. The memory 1104 may be used to store any calculations made by the processing circuitry 1102 and / or any data received via the communication interface 1106. In some embodiments, the processing circuitry 1102 and memory 1104 is integrated.

[0139] The communication interface 1106 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 1106 comprises port(s) / terminal(s) 1116 to send and receive data, for example to and from a network over a wired connection. The communication interface 1106 also includes radio front-end circuitry 1118 that may be coupled to, or in certain embodiments a part of, the antenna 1110. Radio front-end circuitry 1118 comprises filters 1120 and amplifiers 1122. The radio front-end circuitry 1118 may be connected to an antenna 1110 and processing circuitry 1102. The radio front-end circuitry may be configured to condition signals communicated between antenna 1110 and processing circuitry 1102. The radio front-end circuitry 1118 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 1118 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1120 and / or amplifiers 1122. The radio signal may then be transmitted via the antenna 1110. Similarly, when receiving data, the antenna 1110 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1118. The digital data may be passed to the processing circuitry 1102. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0140] In certain alternative embodiments, the network node 1100 does not include separate radio front-end circuitry 1118, instead, the processing circuitry 1102 includes radio front-end circuitry and is connected to the antenna 1110. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1112 is part of the communication interface 1106. In still other embodiments, the communication interface 1106 includes one or more ports or terminals 1116, the radio front-end circuitry 1118, and the RF transceiver circuitry 1112, as part of a radio unit (not shown), and the communication interface 1106 communicates with the baseband processing circuitry 1114, which is part of a digital unit (not shown).

[0141] The antenna 1110 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 1110 may be coupled to the radio front-end circuitry 1118 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 1110 is separate from the network node 1100 and connectable to the network node 1100 through an interface or port.

[0142] The antenna 1110, communication interface 1106, and / or the processing circuitry 1102 may be configured to perform any receiving operations and / or certainobtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 1110, the communication interface 1106, and / or the processing circuitry 1102 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0143] The power source 1108 provides power to the various components of network node 1100 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1108 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1100 with power for performing the functionality described herein. For example, the network node 1100 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1108. As a further example, the power source 1108 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0144] Embodiments of the network node 1100 may include additional components beyond those shown in Figure 11 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, the network node 1100 may include user interface equipment to allow input of information into the network node 1100 and to allow output of information from the network node 1100. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1100. In some embodiments providing a core network node, such as core network node 108 of FIG. 9, some components, such as the radio front-end circuitry 1118 and the RF transceiver circuitry 1112 may be omitted.

[0145] Figure 12 is a block diagram illustrating a virtualization environment 1200 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 any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality isimplemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1200 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 1200 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface. Virtualization may facilitate distributed implementations of a network node, UE, core network node, or host.

[0146] Applications 1202 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0147] Hardware 1204 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1206 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1208a and 1208b (one or more of which may be generally referred to as VMs 1208), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 1206 may present a virtual operating platform that appears like networking hardware to the VMs 1208.

[0148] The VMs 1208 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1206. Different embodiments of the instance of a virtual appliance 1202 may be implemented on one or more of VMs 1208, and the implementations may be made in different ways. 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.

[0149] In the context of NFV, a VM 1208 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 the VMs 1208, and that part of hardware 1204 that executes that VM, be ithardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 1208 on top of the hardware 1204 and corresponds to the application 1202.

[0150] Hardware 1204 may be implemented in a standalone network node with generic or specific components. Hardware 1204 may implement some functions via virtualization. Alternatively, hardware 1204 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1210, which, among others, oversees lifecycle management of applications 1202. In some embodiments, hardware 1204 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes 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. In some embodiments, some signaling can be provided with the use of a control system 1212 which may alternatively be used for communication between hardware nodes and radio units.

[0151] Although the computing devices described herein (e.g., UEs, network nodes) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information 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. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. Inanother example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0152] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry 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 non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0153] REFERENCES[1] 3GPP TS 28.531 Management and orchestration; Provisioning, 18.1.0, 2023-01-06[2] 3GPP TS 28.541 Management and orchestration; 5GNetwork Resource Model (NRM); Stage 2 and stage 3, 18.4.1, 2023-01-13[3] 3GPP TS 28.622 Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS), 18.1.0, 2023-01- 11

Claims

Claims1. A method performed by a management service consumer in a wireless communication network, comprising: receiving (602) a request (402, 502) to obtain measurement data, wherein the request includes a group identifier associated with a group of network resources for which measurement data is requested; identifying (604) a network resource associated with the group identifier; and transmitting (606) a measurement data request (404, 504) to a management service producer (30) in the wireless communication network that is associated with the network resource, the measurement data request requesting that the management service producer provide first measurement data associated with the identified network resource.

2. The method of Claim 1 wherein the request was received from an enterprise operator, the method further comprising: receiving, from the management service producer, a measurement data response (406) containing the first measurement data; and transmitting (408) the first measurement data to the enterprise operator.

3. The method of any previous Claim, wherein the group of network resources includes one or more user equipment, UE, virtual network groups, single network slice selection assistance information, S-NSSAI, rating groups, service identifiers, and / or application identifiers.

4. The method of any previous Claim, further comprising: receiving, from the enterprise operator, a group setup request (202) requesting setup of a measurement group, wherein the group setup request identifies a plurality of network resources; establishing a group identifier associated with the plurality of network resources; and transmitting a setup response (204) to the enterprise entity, the setup response including the group identifier.

5. The method of Claim 4, further comprising notifying a network function of anassociation between the group identifier and at least one of the plurality of network resources.

6. The method of Claim 5, wherein the network function comprises at least one of a unified data management, UDM, function, a network slice selection function, NSSF, and / or a policy control function, PCF.

7. The method of any previous Claim, wherein the management service producer comprises at least one of a user plane function, UPF, an access and mobility management function, AMF, or a session management function, SMF.

8. The method of any previous Claim, further comprising: notifying the management service producer of the association between the group identifier and at least one of the plurality of network resources.

9. The method of any previous Claim, wherein the management service consumer comprises an operations, administration and maintenance, OAM, group handler.

10. The method of any previous Claim, wherein the group identifier is associated with a plurality of different types of network resources including UEs, virtual network groups, S-NSSAI, rating groups, service identifiers, and / or application identifiers.

11. The method of any previous Claim, wherein the measurement data request includes the group identifier, and wherein the measurement data request requests measurement data for resources associated with the group identifier.

12. The method of any previous Claim, wherein the management service consumer is implemented in an open radio access network, ORAN, network node.

13. The method of Claim 12, wherein the management service consumer is implemented as a logical function in the ORAN node.

14. The method of Claim 12, wherein the management service consumer is implemented as part of a Service Management and Orchestration, SMO, framework of an ORAN telecommunication system.

15. The method of Claim 12, wherein the management service consumer is implemented as an rApp in aNon-Real Time RAN Intelligent Controller, Non-RT RIC, within an ORAN telecommunication system.

16. A method performed by an enterprise operator, comprising: transmitting (702), to a management service consumer, a request (402, 502) to obtain first measurement data, wherein the request includes a group identifier associated with a group of network resources for which measurement data is requested; and receiving (704) a measurement data response (406, 506) containing the first measurement data.

17. The method of Claim 16, wherein the measurement data response is received from the management service consumer.

18. The method of Claim 16, wherein the measurement data response is received from a management service producer that generates measurement data associated with at least one of the network resources associated with the group identifier.

19. The method of any of Claims 16 to 18, further comprising: transmitting, to the management service consumer, a group setup request (202) requesting setup of a measurement group, wherein the group setup request identifies a plurality of network resources; and receiving a setup response (204) from the management service consumer, the setup response including the group identifier.

20. A method performed by a management service producer in a wireless communication network, comprising: receiving (802) a request (404, 504) from a management service consumer for measurement data, wherein the request includes a group identifier associated with a group of network resources for which measurement data is requested; identifying (804) a network resource associated with the group identifier; obtaining (806) first measurement data associated with the network resource; and transmitting (808) a measurement response (404, 504), the measurement responseincluding the first measurement data.

21. The method of Claim 20, wherein the measurement response is transmitted to the management service consumer.

22. The method of Claim 20, wherein the request identifies an enterprise operator, and wherein the measurement response is transmitted to the enterprise operator.

23. The method of any of Claims 20 to 22, wherein the management service producer is implemented in an open radio access network, ORAN, network node.

24. The method of Claim 23, wherein the management service producer is implemented as a logical function in the ORAN node.

25. The method of Claim 23, wherein the management service producer is implemented as part of a Service Management and Orchestration, SMO, framework of an ORAN telecommunication system.

26. The method of Claim 23, wherein the management service producer is implemented as an rApp in aNon-Real Time RAN Intelligent Controller, Non-RT RIC, within an ORAN telecommunication system.

27. A network node comprising: processing circuitry configured to perform any of the steps of any of Claims 1 to 26; and power supply circuitry configured to supply power to the processing circuitry.

28. A network node adapted to perform operations according to any of Claims 1 to 26.

Images