Quality of service for mission-critical client using mission-critical gateway ue

Abstract

Various embodiments of the present disclosure provide a method for an MC client device to inform the MC service server that the MC client device is connected to an MC gateway UE and thus is capable of having QoS managed by the MC service server via the MC gateway UE. The MC client device can send a message to the MC service server that includes an indication, such as a flag, an IP address of the MC gateway UE, or an MC gateway UE identifier, that indicates to the MC service server that the MC client device is connected to the MC gateway UE. The MC service server verifies with the MC gateway UE whether the MC client device is connected to the MC gateway UE, and then sends a request to the network for network resources (e.g., for QoS management) for the MC gateway UE to use for the MC client device.

Description

[0001] QUALITY OF SERVICE FOR MISSION-CRITICAL CLIENT USING MISSION-CRITICAL GATEWAY UE

[0002] TECHNICAL FIELD

[0003] The present disclosure relates to providing Quality of Service management for Mission-Critical (MC) devices that are connected via an MC Gateway User Equipment (UE) in a wireless communication system.

[0004] BACKGROUND

[0005] Mission-Critical (MC) communication services are essential for the work performed by public safety users e.g. police officers, paramedics and fire brigades. The MC service requires advanced preferential handling compared to normal telecommunication services, including the handling of prioritized MC calls for emergency and imminent threats. One important concept to achieve the needed preferential handling in communication services is Quality of Service (QoS) in a communication network. QoS refers to methods to manage and improve the performance, reliability, and efficiency of networks and services. QoS involves prioritizing and regulating network traffic to guarantee a certain level of performance or quality for specific types of data or applications. This can be achieved through various methods such as packet prioritization, bandwidth allocation, and congestion management.

[0006] One common method to differentiate QoS for different users is by providing different service subscriptions. As an example, a police officer may use a device with a mobile broadband subscription with better QoS settings compared with a commercial end-user. This could give the police officer's device better capabilities to get the communication services in case of network congestion.

[0007] A communication network design for a Mission-Critical user may include a variety of network access technologies. One part of a communication network is the radio access network (e.g. Third Generation Partnership Program (3GPP) based mobile broadband networks, Wi-Fi networks or even direct user device-to-device communication with or without relay capabilities). Besides the radio access network, the communication network also requires different transport networks, packet core networks and service networks. The QoS in a communication service is measured from a user end-to-end perspective, meaning that the QoS is needed in all network parts, as well as end-user devices, server hardware, routers, applications, and other components that are used in the communication service path.

[0008] MC networks may also utilize different network access technologies due to performance, capacity, availability and resilience requirements. An MC end user device (e.g., the MC client device) may switch between different access networks due to unforeseen incidents (e.g. lack of network coverage, damaged, sabotaged network infrastructure). Furthermore, different access networks may use different network addresses to route the traffic to the correct devices involved in the communication. In packet-based networks, e.g. Internet Protocol (IP) network, the IP address and the ports (used to identify the correct application on the addressed device) are keys to set up the right QoS for a specific service. When multiple access networks are used it is common to use Network Address Translation (NAT) functions to support routing capabilities across a multitude of networks that use different address domains.

[0009] For managing QoS in a 3GPP-based mobile broadband network, the request for network resources is sent from a communication server Application Function (AF), which could be an MC Service server (see ref 3GPP TS 23.280) or a P-CSCF in an IP multimedia Subsystem (IMS) see reference 3GPP TS 23.228, to the Policy and Control Function (PCF) in a 5G core network or to the Policy and Charging Control Function (PCRF) in a 4G core network.

[0010] The concept of gateway User Equipment (UE) functionality for MC services is introduced in 3GPP Release- 18 (see ref 3GPP TS 23.280 clause 11 and e.g. Figure 11.2.0-2 and Figure 11.2.1-1) to enable non-3GPP MC client devices to receive MC services via a so-called MC gateway UE. The MC gateway UE provides several functionalities to a non-3GPP device including delivery MC services with needed QoS via 3GPP network. In such scenarios, the MC client device uses a non-3GPP access network (e.g., Wi-Fi) to connect to the MC gateway UE, where the latter uses the 3GPP access network to establish the connection to the 3GPP core on behalf of the non-3GPP device.

[0011] The MC gateway UE can support multiple non-3GPP devices. For this purpose, it provides each non-3GPP device a dedicated local IP address to identify and route the MC media and signaling towards the corresponding MC client device. Hence, the MC gateway UE uses its own IP address to communicate with the 3GPP network and utilizes the previously described NAT functions to support routing towards the corresponding non-3GPP device behind it.

[0012] It shall be noted that in a 3GPP network the PCF (or PCRF) is not always aware whether other access network technologies are used in conjunction with the 3GPP-based network. The requested resources with certain QoS may only be relevant to part of the access network or not relevant at all if other access networks have been chosen. Hence, the ability to manage network resources is still an area for improvement.

[0013] SUMMARY

[0014] Various embodiments of the present disclosure provide a method for an MC client device to inform the MC service server that the MC client device is connected to an MC gateway UE and thus is capable of having QoS managed by the MC service server via the MC gateway UE. The MC client device can send a message to the MC service server that includes an indication, such as a flag, an IP address of the MC gateway UE, or an MC gateway UE identifier, that indicates to the MC service server that the MC client device is connected to the MC gateway UE. The MC service server verifies with the MC gateway UE whether the MC client device is connected to the MC gateway UE, and then sends a request to the network for network resources (e.g., for QoS management) for the MC gateway UE to use for the MC client device.

[0015] In an embodiment, a method is provided that is performed by an MC client device for indicating to an MC service server that the MC client device is connected to an MC gateway UE, where the method comprises providing a message to the MC service server, wherein the message comprises an indication that the MC client device is connected to the MC gateway UE.

[0016] In an embodiment, the MC client device is not a Third Generation Partnership Program (3GPP) enabled device.

[0017] In an embodiment, the indication comprises at least one of a flag, an IP address of the MC gateway UE, or an MC gateway UE identifier or a combination thereof. In an embodiment, the providing the message to the MC service server is in response to establishing a connection with the MC gateway UE.

[0018] In an embodiment, an MC client device is provided that is configured to indicate to an MC service server that the MC client device is connected to an MC gateway UE. The MC client device comprises processing circuitry configured to provide a message to the MC service server, wherein the message comprises an indication that the MC client device is connected to the MC gateway UE.

[0019] In an embodiment, a method is provided that is performed by an MC service server for authorizing an MC client device connected to an MC gateway UE to request MC services. The method includes receiving a message from the MC client device via the MC gateway UE, wherein the message comprises an indication that the MC client device is connected to the MC gateway UE.

[0020] In an embodiment, the MC client device is not a Third Generation Partnership Program, 3GPP, enabled device.

[0021] In an embodiment, the indication comprises at least one of a flag, an IP address of the MC gateway UE, or an MC gateway UE identifier or a combination thereof.

[0022] In an embodiment, the receiving the message from the MC client device is subsequent to the MC gateway UE performing MC service authentication and authorization with the MC service server.

[0023] In an embodiment, the method further comprises providing a request to the MC gateway UE to verify the MC client device is served by the MC gateway UE and receiving a validation response from the MC gateway UE.

[0024] In an embodiment, the method further comprises authorizing the MC client device (102) to use the MC gateway UE, where the MC client device may be identified by a MC service ID of the user that uses the MC client device (102)

[0025] In an embodiment, the method further comprises providing a request for network resources for the MC gateway UE to serve the MC client device to receive a predefined Quality of Service, QoS, level.

[0026] In an embodiment, the request for network resources is provided to at least one of a Policy and Control Function, PCF, in a 5G core network or a Policy and Charging Control Function, PCRF, in a 4G core network.

[0027] In an embodiment, an MC service server is provided that is configured to authorize an MC client device connected to an MC gateway UE to request MC services, where the MC service server includes processing circuitry configured to receive a message from the MC client device via the MC gateway UE, wherein the message comprises an indication that the MC client device is connected to the MC gateway UE.

[0028] In an embodiment, a computer-readable medium is provided the comprises instructions which, when executed on at least one processor, cause the at least one processor to carry out the methods described above.

[0029] In an embodiment, a carrier containing the computer program described above, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer-readable medium.

[0030] Certain embodiments may provide one or more of the following technical advantage(s). A method for a deterministic decision in the MC system to identify the need for 3GPP based network resources in a multitude of different network access types. Hence, MC users which are capable of receiving MC services via different access networks including 3GPP access (e.g., MC gateway UE) can leverage off the QoS for MC communication, provided via 3GPP networks.

[0031] BRIEF DESCRIPTION OF THE DRAWINGS

[0032] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0033] Figure 1 shows an example of a Mission-Critical (MC) system and MC client devices in a wireless communication system according to some embodiments of the present disclosure;

[0034] Figure 2 shows an example of a message sequence chart for indicating to an MC service server that the MC client device is connected to an MC gateway User Equipment (UE) in accordance with some embodiments of the present disclosure;

[0035] Figure 3 shows an example of a communication system in accordance with some embodiments of the present disclosure;

[0036] Figure 4 shows a UE in accordance with some embodiments of the present disclosure;

[0037] Figure 5 shows a network node in accordance with some embodiments of the present disclosure;

[0038] Figure 6 is a block diagram of a host, which may be an embodiment of the host of Figure 3, in accordance with various aspects of the present disclosure described herein; and

[0039] Figure 7 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments of the present disclosure may be virtualized.

[0040] DETAILED DESCRIPTION

[0041] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

[0042] 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.

[0043] There currently exist certain challenge(s). The Quality of Service (QoS) functionality in current Mission- Critical (MC) systems, does not know if network resources should be requested in the Third Generation Partnership Program (3GPP) based network in case a multitude of different access network technologies are used. An MC service server according to 3GPP does not know if an MC client device uses a 3GPP-based access network only, or in combination with other access network technologies or not utilizing 3GPP access network technology at all.

[0044] Existing technologies utilize either subscription related information to determine the correct QoS or which type of 3GPP-based access network that the MC client device (e.g., one used by an MC end user) is currently using. If multiple access technologies are used the MC service server cannot determine if 3GPP based access network is part of the network access

[0045] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. The proposed solution defines a method for the MC client device to inform the MC service server in the MC System that an MC gateway User Equipment (UE) in a 3GPP access network is used and, in that case, the MC user device provides an indication (e.g., flag, Internet Protocol (IP) address of the MC gateway UE, MC gateway UE identifier or a combination of these) to the MC service server to request resources with required QoS in the 3GPP based network. In this way the MC service server can decide to send correct details to the Policy Control Function (PCF) in the 5GCore network.

[0046] Various embodiments of the present disclosure provide a method for an MC client device to inform the MC service server that the MC client device is connected to an MC gateway UE and thus is capable of having QoS managed by the MC service server via the MC gateway UE. The MC client device can send a message to the MC service server that includes an indication, such as a flag, an IP address of the MC gateway UE, or an MC gateway UE identifier, that indicates to the MC service server that the MC client device is connected to the MC gateway UE. The MC service server verifies with the MC gateway UE whether the MC client device is connected to the MC gateway UE, and then sends a request to the network for network resources (e.g., for QoS management in order to receive a predefined QoS level) for the MC gateway UE to use for the MC client device.

[0047] Certain embodiments may provide one or more of the following technical advantage(s). A method for a deterministic decision in the MC system to identify the need for 3GPP-based network resources in a multitude of different network access types. Hence, MC users that are capable of receiving MC services via different access networks including 3GPP access (e.g., MC gateway UE) can leverage off the QoS for MC communication, provided via 3GPP networks.

[0048] Figure 1

[0049] Figure 1 illustrates a number of MC clients using different types of access networks to use the service from an MC service server 112. The different MC client access can be described as the following.

[0050] MC client type A: This MC client is installed on a non-3GPP client device 102 (or a device that currently does not have 3GPP access enabled). The MC client device 102 uses a connection to an MC gateway UE 104 which is accessing the MC service server 112 via a 3GPP network 114. Hence, the MC gateway UE 104 is a 3GPP device i.e. a User Equipment (UE).

[0051] MC client type B: This MC client is installed on a 3GPP device 106 i.e. a UE and has direct connection towards the 3GPP network 114, which also means that quality of service can be controlled by the 3GPP network 114 all the way from the MC service server 112 to the MC client device 106 on the 3GPP device.

[0052] MC client type C: This MC client is installed on a non-3GPP device 108 and uses Wi-Fi radio access. Furthermore, the 3GPP core network is used for network authentication and authorization. The quality of service of the radio access cannot be controlled by the 3GPP network 114 since the radio access uses a Wi-Fi network, which is not part of 3GPP. MC client type D: This MC client 110 uses an access network to the MC system that is outside the scope of 3GPP Radio and core network. One example of such access is a fiber access network. The quality of service of the access network cannot be controlled by the 3GPP network.

[0053] To enable Quality of Service in the access network, the MC service server 112 uses Rx (reference to 3GPP TS 29.214) in a 4G network and Rx, N5 or N33 (reference to 3GPP TS 29.513) in a 5G network. The Rx terminates in the Policy and Charging Rules Function (PCRF) in a 4G network and in a PCF in a 5G network.

[0054] The MC system comprises of an MC service server 112 (as described in 3GPP TS 23.280), and a SIP (Session Initiation Protocol) core which could be an IMS network (as defined in 3GPP TS 23.228).

[0055] In an SIP based network, the MC client may include a P-Access-Network-Info header (as defined in RFC 3455) in the SIP messages. The MC client may use this header to relay information about the access technology to proxies and application servers that are providing services. The serving proxy or MC service server may then use this information to optimize services for the MC client. For example, to request network resources based on the access network type. However, in the context of the different client types defined above, the MC system may not be able to differentiate the MC client type A and C based on the P-Access-Network-Info header, since MC client type A and C may include the same information in the P-Access-Network-Info header (e.g., Wi-Fi access).

[0056] As explained above the MC service server 112 may request resources for the 3GPP access network for MC client of type A and B, but shall not request resources for MC clients of type C or D.

[0057] Furthermore, the MC service server 112 can determine the IP network used by the MC clients by the IP address of the MC clients. Based on the IP network an MC client uses, the MC service server 112 may choose to request resources (i.e. QoS) on the mentioned reference points (Rx, N5 or N33). QoS determination based on IP access network is sufficient to conclude that the MC service server 112 shall not request resources for MC client 110 of type D, which uses an IP network that is not part of the 3GPP network domain.

[0058] The MC client device 102 that uses an MC gateway UE 104 may use the same IP network as MC clients 106 of type B and client 108 of type C. As a consequence of this the MC service server 112 cannot determine to request resources or not based on IP network used for MC client type A, B and C.

[0059] The invention proposes a method for an MC client device 102(type A) that uses an MC gateway UE 104 to inform the MC service server 112 of the usage of the MC gateway UE 104 so that the MC service server 112 can determine that the MC client device 102 uses a 3GPP network 114 and due to that can request resources (QoS).

[0060] Figure 2

[0061] The message sequence chart of Figure 2 illustrates some of the methods of the present disclosure.

[0062] In an optional embodiment, at step 202, the MC gateway UE 104 connects to the 3GPP network 114 (either attaches to the Evolved Packet System (EPS), or registers to the 5GS) in which the 3GPP network authenticates and authorizes the MC gateway UE 104 to use the network. This is done according to 3GPP TS 33.401 and 3GPP TS 33.501.

[0063] In another optional embodiment at step 204, the MC gateway UE 104 acting as an MC UE performs MC service authentication and authorization towards the MC service server 112 according to 3GPP TS 33.180. In an optional step 206, the non-3GPP MC client device 102 selects and establishes the connection towards an appropriate MC gateway UE 104.

[0064] In step 208, the MC client device 102 sends, to the MC service server 112 an indication that the MC client device 102 is connected to the MC gateway UE 104. In an embodiment, the packets (e.g., Session Initiation Protocol (SIP) Register message or a SIP publish message) sent from the MC client device 102 indicates usage of the MC gateway UE 104 by providing e.g. flag, Internet Protocol (IP) address of the MC gateway UE 104, MC gateway UE identifier or a combination thereof.

[0065] At optional step 210, the MC service server 112 may verify the correctness of the information sent in step 208 by sending a request to the MC gateway UE to know whether it supports the MC client as indicated in the flag, IP address of the MC gateway UE, MC gateway UE identifier or a combination of these sent in step 208. The verifying message includes the identifier of the MC client device 102.

[0066] At optional step 212, the MC gateway UE 104 may send a validation response to the MC service server 112 indicating whether the MC client device 102 is accepted and connected to the MC gateway UE 104.

[0067] Once validated, optionally at step 214, the MC service server 112 checks whether the MC gateway UE 104 is capable of supporting the MC client device 102 in terms of its capacity to support a further (or new) MC user and its capability to provide the requested MC service (e.g., Mission-Critical Push To Talk (MCPTT), Mission-Critical Video (MCVideo) or Mission-Critical Data (MCData)). Once the MC gateway UE 104 is capable of supporting the requested MC client device 102, the MC service server 112 authorizes the MC client device 102 to use the corresponding MC gateway UE 104.

[0068] Optionally, as step 216, the MC service server 112 requests 3GPP resources from the 3GPP network 114 (either the EPS or 5GS) for the MC gateway UE 104 on behalf of the MC client device 102 to serve.

[0069] Figure 3

[0070] Figure 3 shows an example of a communication system 300 in accordance with some embodiments.

[0071] In the example, the communication system 300 includes a telecommunication network 302 that includes an access network 304, such as a Radio Access Network (RAN), and a core network 306, which includes one or more core network nodes 308. The access network 304 includes one or more access network nodes, such as network nodes 310A and 310B (one or more of which may be generally referred to as network nodes 310), or any other similar Third Generation Partnership Project (3GPP) access nodes or non-3GPP Access Points (APs). 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 302 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 302 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 302, including one or more network nodes 310 and / or core network nodes 308. 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 A1, F1, W1, E1, E2, X2, Xn interface, an open 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 0-2 interface defined by the 0-RAN Alliance or comparable technologies. The network nodes 310 facilitate direct or indirect connection of User Equipment (UE), such as by connecting UEs 312A, 312B, 3120, and 312D (one or more of which may be generally referred to as UEs 312) to the core network 306 over one or more wireless connections.

[0072] 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 300 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 300 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0073] The UEs 312 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 310 and other communication devices. Similarly, the network nodes 310 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 312 and / or with other network nodes or equipment in the telecommunication network 302 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 302.

[0074] In the depicted example, the core network 306 connects the network nodes 310 to one or more hosts, such as host 316. 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 306 includes one more core network nodes (e.g., core network node 308) 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 descriptions thereof are generally applicable to the corresponding components of the core network node 308. 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).

[0075] The host 316 may be under the ownership or control of a service provider other than an operator or provider of the access network 304 and / or the telecommunication network 302, and may be operated by the service provider or on behalf of the service provider. The host 316 may host a variety of applications to provide one or more service. Examples of such applications include Mission Critical systems, 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.

[0076] As a whole, the communication system 300 of Figure 3 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 300 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 Second, Third, Fourth, or Fifth Generation (2G, 3G, 4G, or 5G) standards, or any applicable future generation standard (e.g., Sixth Generation (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.

[0077] In some examples, the telecommunication network 302 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunication network 302 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 302. For example, the telecommunication network 302 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) / massive Internet of Things (loT) services to yet further UEs.

[0078] In some examples, the UEs 312 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 304 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 304. Additionally, a UE may be configured for operating in single- or multi-Radio Access Technology (RAT) or multi-standard mode. For example, a UE may operate with any one or combination of WiFi, New Radio (NR), and LTE, i.e. being configured for Multi-Radio Dual Connectivity (MR-DC), such as Evolved UMTS Terrestrial RAN (E- UTRAN) NR - Dual Connectivity (EN-DC).

[0079] In the example, a hub 314 communicates with the access network 304 to facilitate indirect communication between one or more UEs (e.g., UE 312C and / or 312D) and network nodes (e.g., network node 310B). In some examples, the hub 314 may be a controller, router, content source and analytics, a MC gateway UE 104 or any of the other communication devices described herein regarding UEs. For example, the hub 314 may be a broadband router enabling access to the core network 306 for the UEs. As another example, the hub 314 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 310, or by executable code, script, process, or other instructions in the hub 314. As another example, the hub 314 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 314 may be a content source. For example, for a UE that is a Virtual Reality (VR) headset, display, loudspeaker or other media delivery device, the hub 314 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 314 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 314 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0080] The hub 314 may have a constant / persistent or intermittent connection to the network node 31 OB. The hub 314 may also allow for a different communication scheme and / or schedule between the hub 314 and UEs (e.g., UE 312C and / or 312D), and between the hub 314 and the core network 306. In other examples, the hub 314 is connected to the core network 306 and / or one or more UEs via a wired connection. Moreover, the hub 314 may be configured to connect to a Machine-to-Machine (M2M) service provider over the access network 304 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 310 while still connected via the hub 314 via a wired or wireless connection. In some embodiments, the hub 314 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 310B. In other embodiments, the hub 314 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and the network node 310B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0081] Figure 4

[0082] Figure 4 shows a UE 400 in accordance with some embodiments. 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, MC client device 102, MC gateway UE 104, a smart phone, mobile phone, cell phone, Voice over Internet Protocol (VoIP) phone, wireless local loop phone, desktop computer, Personal Digital Assistant (PDA), wireless camera, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, Laptop Embedded Equipment (LEE), Laptop Mounted Equipment (LME), smart device, wireless Customer Premise Equipment (CPE), vehicle, vehiclemounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3GPP, including a Narrowband Internet of Things (NB-loT) UE, a Machine Type Communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0083] A UE may support Device-to-Device (D2D) communication, for example by implementing a 3GPP 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).

[0084] The UE 400 includes processing circuitry 402 that is operatively coupled via a bus 404 to an input / output interface 406, a power source 408, memory 410, a communication interface 412, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 4. 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.

[0085] The processing circuitry 402 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 410. The processing circuitry 402 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 402 may include multiple Central Processing Units (CPUs).

[0086] In the example, the input / output interface 406 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 400. 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.

[0087] In some embodiments, the power source 408 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 408 may further include power circuitry for delivering power from the power source 408 itself, and / or an external power source, to the various parts of the UE 400 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 408. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 408 to make the power suitable for the respective components of the UE 400 to which power is supplied.

[0088] The memory 410 may be or be configured to include memory such as Random Access Memory (RAM), Read Only Memory (ROM), Programmable ROM (PROM), Erasable PROM (EPROM), Electrically EPROM (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 410 includes one or more application programs 414, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 416. The memory 410 may store, for use by the UE 400, any of a variety of various operating systems or combinations of operating systems.

[0089] The memory 410 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 RAM (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a tamper resistant module in the form of a Universal Integrated Circuit Card (UICC) including one or more Subscriber Identity Modules (SIMs), such as a Universal SIM (USIM) and / or Internet Protocol Multimedia Services Identity Module (ISIM), other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUlCC), integrated UICC (IUICC) or a removable UICC commonly known as a ‘SIM card.' The memory 410 may allow the UE 400 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 410, which may be or comprise a device-readable storage medium.

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

[0091] In the illustrated embodiment, communication functions of the communication interface 412 may include cellular communication, WiFi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, NFC, 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 according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband CDMA (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, Transmission Control Protocol / lnternet Protocol (TCP / IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), Quick User Datagram Protocol Internet Connection (QUIC), Hypertext Transfer Protocol (HTTP), and so forth.

[0092] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 412, 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).

[0093] 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.

[0094] A UE, when in the form of an loT device, may be a device for use in one or more application domains, these domains comprising, but not limited to, 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 television, 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 head-mounted display for Augmented Reality (AR) or VR, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or itemtracking 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 400 shown in Figure 4.

[0095] 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-loT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship, an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0096] 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.

[0097] Figure 5

[0098] Figure 5 shows a network node 500 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 nodes include, but are not limited to, MC service server 112, APs (e.g., radio APs), Base Stations (BSs) (e.g., radio BSs, Node Bs, evolved Node Bs (eNBs), NR Node Bs (gNBs)), and O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0099] 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 RRUs 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).

[0100] Other examples of network nodes include multiple Transmission Point (multi-TRP) 5G access nodes, MultiStandard Radio (MSR) equipment such as MSR BSs, network controllers such as Radio Network Controllers (RNCs) or BS 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).

[0101] The network node 500 includes processing circuitry 502, memory 504, a communication interface 506, and a power source 508. The network node 500 may be composed of multiple physically separate components (e.g., a NodeB component and an 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 500 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 500 may be configured to support multiple RATs. In such embodiments, some components may be duplicated (e.g., separate memory 504 for different RATs) and some components may be reused (e.g., a same antenna 510 may be shared by different RATs). The network node 500 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 500, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, Long Range Wide Area Network (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 the network node 500.

[0102] The processing circuitry 502 may comprise a combination of one or more of a microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, 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 500 components, such as the memory 504, to provide network node 500 functionality.

[0103] In some embodiments, the processing circuitry 502 includes a System on a Chip (SOC). In some embodiments, the processing circuitry 502 includes one or more of Radio Frequency (RF) transceiver circuitry 512 and baseband processing circuitry 514. In some embodiments, the RF transceiver circuitry 512 and the baseband processing circuitry 514 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 the RF transceiver circuitry 512 and the baseband processing circuitry 514 may be on the same chip or set of chips, boards, or units.

[0104] The memory 504 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, RAM, 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 502. The memory 504 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 502 and utilized by the network node 500. The memory 504 may be used to store any calculations made by the processing circuitry 502 and / or any data received via the communication interface 506. In some embodiments, the processing circuitry 502 and the memory 504 are integrated.

[0105] The communication interface 506 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 506 comprises port(s) / terminal(s) 516 to send and receive data, for example to and from a network over a wired connection. The communication interface 506 also includes radio front-end circuitry 518 that may be coupled to, or in certain embodiments a part of, the antenna 510. The radio front-end circuitry 518 comprises filters 520 and amplifiers 522. The radio front-end circuitry 518 may be connected to the antenna 510 and the processing circuitry 502. The radio front-end circuitry 518 may be configured to condition signals communicated between the antenna 510 and the processing circuitry 502. The radio front-end circuitry 518 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 518 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of the filters 520 and / or the amplifiers 522. The radio signal may then be transmitted via the antenna 510. Similarly, when receiving data, the antenna 510 may collect radio signals which are then converted into digital data by the radio front-end circuitry 518. The digital data may be passed to the processing circuitry 502. In other embodiments, the communication interface 506 may comprise different components and / or different combinations of components.

[0106] In certain alternative embodiments, the network node 500 does not include separate radio front-end circuitry 518; instead, the processing circuitry 502 includes radio front-end circuitry and is connected to the antenna 510. Similarly, in some embodiments, all or some of the RF transceiver circuitry 512 is part of the communication interface 506. In still other embodiments, the communication interface 506 includes the one or more ports or terminals 516, the radio front-end circuitry 518, and the RF transceiver circuitry 512 as part of a radio unit (not shown), and the communication interface 506 communicates with the baseband processing circuitry 514, which is part of a digital unit (not shown). The antenna 510 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 510 may be coupled to the radio front-end circuitry 518 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 510 is separate from the network node 500 and connectable to the network node 500 through an interface or port.

[0107] The antenna 510, the communication interface 506, and / or the processing circuitry 502 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node 500. Any information, data, and / or signals may be received from a UE, another network node, and / or any other network equipment. Similarly, the antenna 510, the communication interface 506, and / or the processing circuitry 502 may be configured to perform any transmitting operations described herein as being performed by the network node 500. Any information, data, and / or signals may be transmitted to a UE, another network node, and / or any other network equipment.

[0108] The power source 508 provides power to the various components of the network node 500 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 508 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 500 with power for performing the functionality described herein. For example, the network node 500 may be connectable to an external power source (e.g., the power grid or an electricity outlet) via input circuitry or an interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 508. As a further example, the power source 508 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.

[0109] Embodiments of the network node 500 may include additional components beyond those shown in Figure 5 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 500 may include user interface equipment to allow input of information into the network node 500 and to allow output of information from the network node 500. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 500.

[0110] Figure 6

[0111] Figure 6 is a block diagram of a host 600, which may be an embodiment of the host 316 of Figure 3, in accordance with various aspects described herein. As used herein, the host 600 may be or comprise various combinations of hardware and / or software including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 600 may provide one or more services to one or more UEs.

[0112] The host 600 includes processing circuitry 602 that is operatively coupled via a bus 604 to an input / output interface 606, a network interface 608, a power source 610, and memory 612. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 4 and 5, such that the descriptions thereof are generally applicable to the corresponding components of the host 600. The memory 612 may include one or more computer programs including one or more host application programs 614 and data 616, which may include user data, e.g. data generated by a UE for the host 600 or data generated by the host 600 for a UE. Embodiments of the host 600 may utilize only a subset or all of the components shown. The host application programs 614 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (WC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), Moving Picture Experts Group (MPEG), VP9) and audio codecs (e.g., Free Lossless Audio Codec (FLAG), Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, and heads-up display systems). The host application programs 614 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 600 may select and / or indicate a different host for Over-The-Top (OTT) services for a UE. The host application programs 614 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (DASH or MPEG-DASH), etc.

[0113] Figure 7

[0114] Figure 7 is a block diagram illustrating a virtualization environment 700 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 is implemented 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 700 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 700 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.

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

[0116] Hardware 704 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 706 (also referred to as hypervisors or VM Monitors (VMMs)), provide VMs 708A and 708B (one or more of which may be generally referred to as VMs 708), and / or perform any of the functions, features, and / or benefits described in relation with some embodiments described herein. The virtualization layer 706 may present a virtual operating platform that appears like networking hardware to the VMs 708. The VMs 708 comprise virtual processing, virtual memory, virtual networking, or interface and virtual storage, and may be run by a corresponding virtualization layer 706. Different embodiments of the instance of a virtual appliance 702 may be implemented on one or more of the VMs 708, 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.

[0117] In the context of NFV, a VM 708 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 708, and that part of the hardware 704 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs 708, 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 708 on top of the hardware 704 and corresponds to the application 702.

[0118] The hardware 704 may be implemented in a standalone network node with generic or specific components. The hardware 704 may implement some functions via virtualization. Alternatively, the hardware 704 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 710, which, among others, oversees lifecycle management of the applications 702. In some embodiments, the hardware 704 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 RAN or a base station. In some embodiments, some signaling can be provided with the use of a control system 712 which may alternatively be used for communication between hardware nodes and radio units.

[0119] Some Embodiments

[0120] Some of the embodiments described above may be summarized in the following manner:

[0121] 1. A method performed by a Mission-Critical, MC, client device (102) for indicating to an MC service server (112) that the MC client device (102) is connected to an MC gateway User Equipment, UE, (104) the method comprising: providing (208) a message to the MC service server (112), wherein the message comprises an indication that the MC client device (102) is connected to the MC gateway UE (104).

[0122] 2. The method of embodiment 1, wherein the MC client device (102) is not a Third Generation Partnership Program, 3GPP, enabled device.

[0123] 3. The method of any one of embodiment 1 to 2, wherein the indication comprises at least one of a flag, an IP address of the MC gateway UE (104), or an MC gateway UE identifier or a combination thereof. 4. The method of any one of embodiment 1 to 3, wherein the providing the message to the MC service server (112) is in response to establishing (206) a connection with the MC gateway UE (104).

[0124] 5. A Mission-Critical, MC, client device (102) configured to indicate to an MC service server (112) that the MC client device (102) is connected to an MC gateway User Equipment, UE, (104) the MC client device (102) comprising processing circuitry configured to: provide (208) a message to the MC service server (112), wherein the message comprises an indication that the MC client device is connected to the MC gateway UE (104).

[0125] 6. The MC client device of embodiment 5, wherein the processing circuitry is further configured to perform the method of any one of embodiment 2 to 4.

[0126] 7. A method performed by a Mission-Critical, MC, service server (112) for authorizing an MC client device (102) connected to an MC gateway User Equipment, UE, (104) to request MC services, the method comprising: receiving (208) a message from the MC client device (102) via the MC gateway UE (104), wherein the message comprises an indication that the MC client device (102) is connected to the MC gateway UE (104).

[0127] 8. The method of embodiment 7, wherein the MC client device (102) is not a Third Generation Partnership Program, 3GPP, enabled device.

[0128] 9. The method of any one of embodiment 7 to 8, wherein the indication comprises at least one of a flag, an IP address of the MC gateway UE (104), or an MC gateway UE identifier or a combination thereof.

[0129] 10. The method of any one of embodiment 7 to 9, wherein the receiving the message from the MC client device (102) is subsequent to the MC gateway UE (104) performing (204) MC service authentication and authorization with the MC service server (112).

[0130] 11. The method of any one of embodiment 7 to 10, further comprising: providing (210) a request to the MC gateway UE (104) to verify the MC client device (102) is served by the MC gateway UE (104); and receiving (212) a validation response from the MC gateway UE (104).

[0131] 12. The method of any one of embodiment 7 to 11 further comprising: authorizing (214) the MC client device (102) to use the MC gateway UE (104).

[0132] 13. The method of any one of embodiment 7 to 12 further comprising: providing (216) a request for network resources to receive a predefined Quality of Service, QoS, level for the MC gateway UE (104) to serve the MC client device (102).

[0133] 14. The method of embodiment 13, wherein the request for network resources is provided to at least one of a Policy and Control Function, PCF, in a 5G core network or a Policy and Charging Control Function, PCRF, in a 4G core network.

[0134] 15. A Mission-Critical, MC, service server (112) configured to authorize an MC client device (102) connected to an MC gateway User Equipment, UE, (104) to request MC services, the MC service server (112) comprising processing circuitry configured to: receive (208) a message from the MC client device (102) via the MC gateway UE (104), wherein the message comprises an indication that the MC client device (102) is connected to the MC gateway UE (104).

[0135] 16. The MC service server (112) of embodiment 15, wherein the processing circuitry is further configured to perform the method of any one of embodiment 8 to 14.

[0136] 17. A computer-readable medium comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any one of embodiment 1 to 16.

[0137] 18. A carrier containing the computer program of embodiment 17, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer-readable medium.

[0138] Although the computing devices described herein (e.g., UEs, network nodes, hosts) 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. In another 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.

[0139] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored 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 hardwired 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.

[0140] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.

Claims

CLAIMS1. A method performed by a Mission-Critical, MC, client device (102) for indicating to an MC service server (112) that the MC client device (102) is connected to an MC gateway User Equipment, UE, (104) the method comprising: providing (208) a message to the MC service server (112), wherein the message comprises an indication that the MC client device (102) is connected to the MC gateway UE (104).

2. The method of claim 1, wherein the MC client device (102) is not a Third Generation Partnership Program, 3GPP, enabled device.

3. The method of any one of claim 1 to 2, wherein the indication comprises at least one of a flag, an IP address of the MC gateway UE (104), or an MC gateway UE identifier or a combination thereof.

4. The method of any one of claim 1 to 3, wherein the providing the message to the MC service server (112) is in response to establishing (206) a connection with the MC gateway UE (104).

5. A Mission-Critical, MC, client device (102) configured to indicate to an MC service server (112) that the MC client device (102) is connected to an MC gateway User Equipment, UE, (104) the MC client device (102) comprising processing circuitry configured to: provide (208) a message to the MC service server (112), wherein the message comprises an indication that the MC client device is connected to the MC gateway UE (104).

6. The MC client device of claim 5, wherein the processing circuitry is further configured to perform the method of any one of claim 2 to 4.

7. A method performed by a Mission-Critical, MC, service server (112) for authorizing an MC client device (102) connected to an MC gateway User Equipment, UE, (104) to request MC services, the method comprising: receiving (208) a message from the MC client device (102) via the MC gateway UE (104), wherein the message comprises an indication that the MC client device (102) is connected to the MC gateway UE (104).

8. The method of claim 7, wherein the MC client device (102) is not a Third Generation Partnership Program, 3GPP, enabled device.

9. The method of any one of claim 7 to 8, wherein the indication comprises at least one of a flag, an IP address of the MC gateway UE (104), or an MC gateway UE identifier or a combination thereof.

10. The method of any one of claim 7 to 9, wherein the receiving the message from the MC client device (102) is subsequent to the MC gateway UE (104) performing (204) MC service authentication and authorization with the MC service server (112).

11. The method of any one of claim 7 to 10, further comprising: providing (210) a request to the MC gateway UE (104) to verify the MC client device (102) is served by the MC gateway UE (104); and receiving (212) a validation response from the MC gateway UE (104).

12. The method of any one of claim 7 to 11 further comprising: authorizing (214) the MC client device (102) to use the MC gateway UE (104).

13. The method of any one of claim 7 to 12 further comprising: providing (216) a request for network resources to receive a predefined Quality of Service, QoS, level for the MC gateway UE (104) to serve the MC client device (102).

14. The method of claim 13, wherein the request for network resources is provided to at least one of a Policy and Control Function, PCF, in a 5G core network or a Policy and Charging Control Function, PCRF, in a 4G core network.

15. A Mission-Critical, MC, service server (112) configured to authorize an MC client device (102) connected to an MC gateway User Equipment, UE, (104) to request MC services, the MC service server (112) comprising processing circuitry configured to: receive (208) a message from the MC client device (102) via the MC gateway UE (104), wherein the message comprises an indication that the MC client device (102) is connected to the MC gateway UE (104).

16. The MC service server (112) of claim 15, wherein the processing circuitry is further configured to perform the method of any one of claim 8 to 14.

17. A computer-readable medium comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any one of claim 1 to 16.

18. A carrier containing the computer program of claim 17, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer-readable medium.

Images