Relay connections in communication networks

Abstract

A user equipment (UE) performs a method including preparing an announcement message for transmission, the announcement message including an indication of the user equipment's ability to act as a relay in a UE-UE (U2U) connection and, responsive to determining that the UE is connected to a wireless communication network, an indication that a network-based security protocol is available to establish security for the U2U connection.

Description

[Background technology]

[0001] A 5G Nearby Services (ProSe) UE-Network Relay is a user equipment (UE) that provides functionality to support network connectivity for (one or more) 5G ProSe remote UEs. The architecture of such connectivity is shown in Figure 1.

[0002] Both can be used for 5G ProSe UE-network relay authorization and security establishment on the PC5 interface. The UP-based procedure uses a UP connection to 5G PKMF in 5GC, while the CP-based procedure uses a ProSe-certified vehicle via a NAS procedure toward AMF and AUSF in 5GC.

[0003] The high-level security flow for UE-Network Relay is shown in Figures 2 and 3. Figure 2 shows the UP-based authorization and secure link establishment procedure. Figure 3 shows the CP-based authorization and secure link establishment procedure.

[0004] Currently, 3GPP is researching support for UE-UE relays. The 5G ProSe UE-UE relay is a UE that provides functionality to support connectivity between 5G ProSe UEs (U2U). See the exemplary architecture in Figure 4.

[0005] In UE-UE relay use cases, one or more (or all) of the source UE, target UE, and UE-UE relay may be either within or outside of 3GPP coverage. [Overview of the project]

[0006] The subject matter to be disclosed was developed in consideration of several shortcomings of existing systems, including the following:

[0007] 3GPP has not yet determined how connections between source UEs and target UEs via UE-UE relays should be established, and / or how the security of such connections should be established. UE-UE relays, as relay entities, have many similarities to UE-network relays. It is expected that the security procedures for setting up a UE's PC5 connection to a UE-UE relay may be very similar to the procedures for setting up a UE's PC5 connection to a UE-network relay, for example, the procedures shown above in Figures 2 and 3.

[0008] However, the procedures specified for UE-Network Relays require that the UE-Network Relay be connected to a 5GC network and utilize the services / functions provided by the network to implement the necessary security procedures. These procedures may be referred to herein as network-based security.

[0009] One problem associated with this is that UE-UE relays can be either within or outside of 3GPP coverage, meaning they may or may not be connected to the network.

[0010] Therefore, in the case of UE-UE relays, it is unclear how, if, and when network-based authentication and authorization procedures can be used for PC5 connectivity security between the UE and the UE-UE relay, and / or how to select the appropriate method if multiple security methods are available.

[0011] Some aspects of this disclosure and their embodiments may provide solutions to these or other problems. Embodiments of the subject matter disclosed propose that a UE-UE relay can announce, for a given UE-UE relay service, whether a network-based security method is supported and available, based on the connectivity status of that UE-UE relay toward the network.

[0012] As an addition or alternative, if two or more methods are supported, a UE-UE relay may announce the preference for the UE-UE relay that supports one particular security method.

[0013] Some embodiments may offer (one or more) technical advantages that provide an obvious, robust, and reliable method for selecting a security method in a UE-UE relay scenario.

[0014] In some embodiments of the disclosed subject matter, a method performed by user equipment includes preparing an announcement message for transmission, the announcement message comprising (a) an instruction of the user equipment's ability to act as a relay in a UE-UE (U2U) connection, and (b) an instruction that, in response to a determination that the UE is connected to a wireless communication network, a network-based security protocol is available to establish security for the U2U connection. The method further includes transmitting the announcement message.

[0015] In some of the relevant embodiments, the UE periodically determines the status of its connection to the wireless communication network.

[0016] In some related embodiments, the UE determines the status of its connection to the wireless network upon receiving a discovery message from another UE.

[0017] In some relevant embodiments, the indication that a network-based security protocol is available is omitted from the notification message in response to a determination that the UE is not connected to a wireless communication network.

[0018] In some relevant embodiments, the indication that a network-based security protocol is available is included in the list of available security protocols for establishing security for a U2U connection. In some such embodiments, the list of available security protocols includes an indication of the priority of the available security protocols for establishing security for a U2U connection. In some such embodiments, the available security protocols for establishing security for a U2U connection include one or more peer-to-peer based security protocols.

[0019] In some related embodiments, the notification message is broadcast to enable discovery of the UE by one or more other UEs.

[0020] In some of the relevant embodiments, the notification message is sent in response to the receipt of a discovery message from another UE.

[0021] In some related embodiments, the method further includes sending a discovery key request message to a core network node and, in response, receiving a relay service code that authorizes the UE to act as a relay in a U2U connection.

[0022] In some of the relevant embodiments, the notification message includes instructions for a relay service code.

[0023] In some relevant embodiments, the discovery key request message further includes an indication of the UE's ability to act as a relay in a U2U connection.

[0024] In some related embodiments, the method further includes establishing a U2U connection with a source UE and a target UE. In some such embodiments, establishing the U2U connection includes receiving, from one or more of the source UE and the target UE, a connection request message including an indication of a selected security protocol for establishing security for the U2U connection.

[0025] In some embodiments of the disclosed subject matter, a method performed by a first user equipment (UE) includes detecting an announcement message transmitted by a second UE, the announcement message including an indication of the capabilities of the second UE to act as a relay in a U2U connection and an indication that a network-based security protocol is available for establishing security for the U2U connection in response to a determination that the second UE is connected to a wireless communication network, and establishing a U2U connection with a target UE via the second UE acting as a relay.

[0026] In some related embodiments, establishing the U2U connection includes transmitting, to the second UE, a connection request message including an indication of a selected security protocol for establishing security for the U2U connection.

[0027] In some related embodiments, the indication that a network-based security protocol is available is included within a list of available security protocols for establishing security for the U2U connection.

[0028] In some related embodiments, the list of available security protocols includes an indication of the priority of the available security protocols for establishing security for the U2U connection.

[0029] In some relevant embodiments, the available security protocols for establishing security for a U2U connection include one or more peer-to-peer based security protocols.

[0030] In some relevant embodiments, the notification message is broadcast by the second UE to enable discovery by the second UE.

[0031] In some related embodiments, the method further includes sending a discovery message and, in response, receiving an announcement message from a second UE.

[0032] In some relevant embodiments, the method further includes sending a discovery key request message to a core network node and, in response, receiving a relay service code that authorizes the first UE to act as either a source UE or a target UE in a U2U connection. In some such embodiments, the discovery key request message further includes an indication of the first UE's ability to act as either a source UE or a target UE in a U2U connection.

[0033] The drawings illustrate selected embodiments of the subject matter disclosed. In the drawings, similar reference numerals indicate similar features. [Brief explanation of the drawing]

[0034] [Figure 1] This figure shows a reference architecture for 5G ProSe Layer 3 UE-Network Relay. [Figure 2] This diagram shows the authorization and secure PC5 link establishment procedure for 5G ProSe UE-Network Relay. [Figure 3] This figure shows the 5G ProSe UE-Network Relay Security Procedure, which involves setting up a Network ProSe security context while establishing a PC5 link. [Figure 4]This figure shows an exemplary architecture for UE-UE relays. [Figure 5] This figure shows the processing and / or signaling flow according to several embodiments of the disclosed subject matter. [Figure 6] This figure shows the processing and / or signaling flow according to several embodiments of the disclosed subject matter. [Figure 7] This is a flowchart illustrating the method in several embodiments of the disclosed subject matter. [Figure 8] This is a flowchart illustrating the method in several embodiments of the disclosed subject matter. [Figure 9] This figure shows an example of a communication system according to several embodiments of the disclosed subject matter. [Figure 10] This figure shows the UE according to several embodiments of the disclosed subject matter. [Figure 11] This figure shows a network node according to several embodiments of the disclosed subject matter. [Figure 12] This is a block diagram of the host. [Figure 13] This block diagram shows a virtualization environment where functions implemented by several embodiments can be virtualized. [Figure 14] This is a communication diagram of a host communicating with a UE via a network node over a partial wireless connection, according to several embodiments of the disclosed subject matter. [Modes for carrying out the invention]

[0035] Next, some of the embodiments intended herein will be described more thoroughly with reference to the accompanying drawings. These embodiments are provided, by example, to convey the scope of the subject to those skilled in the art.

[0036] Figure 5 shows the processing and / or signaling flow for network-based security when one or more of the source UE, UE-UE relay, and target UE are in coverage, according to an embodiment of the subject matter disclosed.

[0037] 0. 5G ProSe source UE / target UE and UE-UE relays are provisioned with Discovery Security Material and / or PRUK while they are in coverage.

[0038] 1. Discovery procedures for UE-UE relays are performed by the 5G ProSe source UE using discovery parameters and discovery security materials based on the relay service code for the UE-UE relay. If the UE-UE relay is under 3GPP coverage, it will also indicate in the discovery notification message whether network-based relay service authentication and authorization are supported for the UE-UE relay.

[0039] 2. If the discovered UE-UE relay supports network-based relay service authentication and authorization, the 5G ProSe source UE sends an initial request message for network-based security. For example, the initial request message may contain the ProSe relay user key (PRUK) ID or subscription confidentiality identifier (SUCI), the relay service code (RSC) of the 5G ProSe UE-UE relay service, and the K for the 5G ProSe UE-UE relay. NRP It may include a Direct Communication Request (DCR) that includes freshness parameter 1.

[0040] 3. The 5G ProSe UE-UE relay has a PRUK ID or SUCI, RSC, and K in 5GC. NRP Send a key request message that includes freshness parameter 1.

[0041] Note: 5GC NF and internal signaling are not described here for the sake of brevity. Security procedures similar to those for 5G ProSe communication via 5G ProSe layer 3 UE-network relay defined in TS33.503 can be reused.

[0042] 4. The 5GC sends a key response message containing the freshness parameter 2 to the 5G ProSe UE-UE relay. NRP K NRP

[0043] 5a. The 5G ProSe UE-UE relay derives the session key (K NRP ) from K NRP-SESS and then derives the confidentiality key (NRPEK) (if applicable) and the integrity key (NRPIK) based on the PC5 security policy as specified in TS33.536 v17.1.0. The �G ProSe UE-UE relay sends a direct security mode command message to the 5G ProSe source UE and includes the freshness parameter 2 of K NRP in that message.

[0044] 5b. The 5G ProSe source UE derives K NRP from the PRUK, RSC, and freshness parameter 1 of the 5G ProSe source UE and the received freshness parameter 2 of K NRP and then derives the session key (K NRP ), the confidentiality key (NRPEK) (if applicable), and the integrity key (NRPIK) in the same manner as the 5G ProSe UE-UE relay based on the PC5 security policy and processes the direct security mode command. The successful verification of the direct security mode command ensures that the 5G ProSe source UE permits the 5G ProSe UE-UE relay to provide the UE-UE relay service. <XXXXXX><XXXXXX><XXXXXX>​​5c. The 5G ProSe source UE responds to the 5G ProSe UE-UE relay with a direct security mode completion message.

[0046] 5d. Upon receiving a Direct Security Mode Completion message, the 5G ProSe UE-UE relay shall verify the Direct Security Mode Completion message. Successful verification of the Direct Security Mode Completion message assures the 5G ProSe UE-UE relay that the 5G ProSe source UE is permitted to obtain UE-UE relay services.

[0047] 6. The 5G ProSe source UE and 5G ProSe UE-UE relay continue with the rest of the procedure for UE-UE relay service over a secure PC5 link.

[0048] 7. Steps 1-6 are repeated to establish PC5 security between the 5G ProSe target UE and the 5G ProSe UE-UE relay.

[0049] 8. 5G ProSe source UEs and 5G ProSe target UEs can establish end-to-end security via 5G ProSe UE-UE relay. Details of this are not described in this solution.

[0050] Figure 6 shows a processing and / or signaling flow for discovery according to an embodiment of the subject matter disclosed. The processing and / or signaling flow may be utilized in steps 0 and / or 1 described above with respect to Figure 5.

[0051] 1-4. When a 5G ProSe UE-UE relay is in coverage, the UE-UE relay sends a discovery key request message to the 5G DDNMF in the HPLMN of the UE-UE relay in order to obtain permission for the relay service code to be announced and to obtain the relevant security materials.

[0052] Furthermore, UE-UE relay shall include the UE-UE relay capability of the UE-UE relay, which includes the security methods supported for U2U relay (e.g., network-based security, peer-to-peer-based security, etc.). UE-UE relay capability may also include the supported hops of the U2U relay, Layer 2 or Layer 3 U2U relay, which a (monitoring / announcing) UE can perform in a U2U relay procedure for an directed U2U RSC, for example, as a source UE, a target UE, a U2U relay UE, or a combination of these roles.

[0053] U2U relay capability is permitted and negotiated during the discovery key request procedure.

[0054] When a 5-10.5G ProSe source UE or target UE is in coverage, the UE sends a discovery key request message to the 5G DDNMF in the HPLMN of the UE-UE relay in order to obtain permission for the relay service code to be announced and to obtain the relevant security material.

[0055] Furthermore, the UE shall include its UE-UE relay capability during the discovery key request.

[0056] U2U relay capability is permitted and negotiated during the discovery key request procedure.

[0057] 11. The ProSe 5G UE-UE relay periodically sends relay notification messages to its vicinity, informing of the availability of the ProSe 5G UE-UE relay as a UE-UE relay.

[0058] In the notification message, the ProSe 5G UE-UE relay will include the ProSe 5G UE-UE relay user information ID, relay service code (RSC), a list of UEs reachable by that relay, and also the available security methods for U2U relay (e.g., network-based security, peer-to-peer-based security, etc.).

[0059] The 5G ProSe UE-UE relay shall periodically check the connectivity status of the 5G ProSe UE-UE relay with the network, or upon receiving a solicitation message (discovery message from another UE). If connectivity with the network is available, the UE-UE relay shall include network-based security as an available security method for U2U relay in its announcement message. Otherwise, the UE-UE relay shall remove network-based security from the available security methods for U2U relay in its announcement message.

[0060] Furthermore, if multiple security methods are available for a U2U relay, the UE-UE relay may announce the preference for which UE-UE relay supports which security method, for example, by listing the available security methods in order.

[0061] 12. The 5G ProSe (source or target) UE discovers the UE-UE relay.

[0062] Based on the available security methods for U2U relays announced by the UE-UE relay, the 5G ProSe (source or target) UE determines that the security method will be used to establish a PC5 link with the UE-UE relay and will perform the security establishment procedure with the UE-UE relay.

[0063] Figure 7 shows a method according to several embodiments. Method VV1 can be implemented by a UE or a wireless device (for example, UE QQ112 or UE QQ200, which will be described later with reference to Figures QQ1 and QQ2, respectively). In one embodiment, the UE is configured or configurable as a U2U relay (for example, the UE has the ability to act as a relay between a source UE and a target UE in a U2U relay connection). In some respects, Method VV1 can correspond to one or more signalings of the UE-UE relay in Figure 5 and the “Notification UE (A-UE, also known as U2U relay)” in Figure 6.

[0064] This method begins in step VV102, when the UE communicates with the core network node to obtain permission, for example, to act as a relay in a U2U connection.

[0065] For example, step VV102 may include the UE sending a discovery key request message to the core network node and, in response, receiving a relay service code that authorizes the UE to act as a relay in the U2U connection. The discovery key request message may further include instructions regarding the UE's ability to act as a relay in the U2U connection.

[0066] In some embodiments, step VV102 may correspond to step 0 described above with respect to Figure 5, and / or steps 1 and 4 described above with respect to Figure 6.

[0067] In step VV104, the UE prepares an announcement message for transmission. The announcement message includes an indication of the user equipment's ability to act as a relay in the U2U connection, and an indication that a network-based security protocol is available to establish security for the U2U connection, in response to the determination that the UE is connected to a wireless communication network. Conversely, the indication that a network-based security protocol is available may be omitted from the announcement message in response to the determination that the UE is not connected to a wireless communication network (e.g., outside of coverage).

[0068] For example, a UE may determine the status of its connectivity to a wireless communication network periodically, or upon receiving discovery messages from another UE, such as a monitoring UE wishing to establish a U2U connection as a source UE or target UE (for example, in response to such reception).

[0069] The notification message may include a list of available security protocols for establishing security for a U2U connection, such as network-based security protocols (e.g., UP-based or CP-based security establishment procedures) or peer-to-peer-based security protocols as described above. The available security protocols may be related to priority, for example, by the use of an index or order of presentation indicating that one security protocol takes precedence over another. For example, network-based security may take precedence over peer-to-peer-based security, and vice versa. Within network-based security protocols, UP-based security procedures may take precedence over CP-based security procedures (and vice versa). One or more of the available security protocols may be set as the default, for example, as specified in a previous configuration by a node in the wireless communication network, or in a radio technical specification implemented by the UE.

[0070] The notification message may further include instructions for the relay service code received in step VV102.

[0071] In step VV106, the UE sends an announcement message. For example, the announcement message may be broadcast to enable discovery of the UE by one or more other UEs (e.g., those UEs that are nearby and capable of detecting the announcement message), or it may be sent in response to receiving a discovery message from another UE.

[0072] In some embodiments, steps VV104 and VV106 may correspond to steps 11a and 11b described above with respect to Figure 6.

[0073] In step VV108, the UE establishes a U2U relay connection between the source UE and the target UE. For example, the UE may receive a connection request message from one or more of the source UE and target UE, which may contain instructions for a selected security protocol for establishing security for the U2U connection. Step VV108 may correspond to step 2 and subsequent steps described above with respect to Figure 5.

[0074] Figure 8 shows a method according to a particular embodiment. Method VV2 can be implemented by a UE or a wireless device (for example, UE QQ112 or UE QQ200, which will be described later with reference to Figures QQ1 and QQ2, respectively). In one embodiment, the UE is configured or configurable as a source UE or target UE in a U2U relay connection (for example, the UE has the ability to act as a source UE or target UE in a U2U relay connection via a U2U relay). In some respects, Method VV2 can correspond to one or more signalings of the source UE and / or target UE in Figure 5 and the “monitoring UE (M-UE, also known as source UE, target UE)” in Figure 6. Method VV2 can be read together with Method VV1, which presents a corresponding method in U2U relays in some respects.

[0075] This method begins in step VV202, when the UE communicates with the core network node to obtain permission to act, for example, as a source UE or target UE in a U2U connection.

[0076] For example, step VV202 may include the UE sending a discovery key request message to the core network node and, in response, receiving a relay service code that authorizes the UE to act as either a source UE or a target UE in a U2U connection. The discovery key request message may further include instructions regarding the UE's ability to act as either a source UE or a target UE in a U2U connection.

[0077] In some embodiments, step VV202 may correspond to step 0 described above with respect to Figure 5, and / or steps 5 and 10 described above with respect to Figure 6.

[0078] In step VV204, the UE detects an announcement message sent by the second UE. The announcement message includes an indication of the second UE's ability to act as a relay in the U2U connection and an indication that a network-based security protocol is available to establish security for the U2U connection, in response to the determination that the second UE is connected to a wireless communication network.

[0079] The notification message may include a list of available security protocols for establishing security for a U2U connection, such as network-based security protocols (e.g., UP-based or CP-based security establishment procedures) or peer-to-peer-based security protocols as described above. The available security protocols may be related to priority, for example, by the use of an index or order of presentation indicating that one security protocol takes precedence over another. For example, network-based security may take precedence over peer-to-peer-based security, and vice versa. Within network-based security protocols, UP-based security procedures may take precedence over CP-based security procedures (and vice versa). One or more of the available security protocols may be set as the default, for example, as specified in a previous configuration by a node in the wireless communication network, or in a radio technical specification implemented by the UE.

[0080] The notification message may further include instructions for a relay service code that allows the second UE to act as a relay in the U2U connection (for example, as received in step VV102 of Method VV1 described above).

[0081] The notification message may be broadcast to enable the discovery of a second UE by one or more other UEs (for example, UEs performing method VV2), or it may be sent in response to the receipt of a discovery message from a UE performing method VV2 or a different UE.

[0082] In some embodiments, step VV204 may correspond to step 12 described above with respect to Figure 6.

[0083] In step VV206, the UE establishes a U2U connection with the target UE via a second UE acting as a relay. For example, step VV206 may include the UE sending a connection request message to the second UE containing instructions for a selected security protocol for establishing security for the U2U connection. Step VV206 may correspond to step 2 and subsequent steps described above with respect to Figure 5.

[0084] Figure 9 shows an example of the QQ100 communication system according to several embodiments.

[0085] In this example, the communication system QQ100 includes a communication network QQ102 which includes an access network QQ104, such as a radio access network (RAN), and a core network QQ106, which includes one or more core network nodes QQ108. The access network QQ104 includes one or more access network nodes (one or more of which may commonly be referred to as network nodes QQ110), such as network nodes QQ110a and QQ110b, or any other similar Third Generation Partnership Project (3GPP) access nodes or non-3GPP access points. Network nodes QQ110 facilitate direct or indirect connections of user equipment (UEs), such as by connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may commonly be referred to as UE QQ112) to the core network QQ106 over one or more radio connections.

[0086] Exemplary wireless communication over a wireless connection involves transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information without using wires, cables, or other material conductors. Furthermore, in different embodiments, the communication system QQ100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that can facilitate or participate in the communication of data and / or signals, whether via a wired or wireless connection. The communication system QQ100 may include and / or interface with any type of communication, telecommunication, data, cellular, wireless network, and / or other similar types of systems.

[0087] UE QQ112 may be any of a wide variety of communication devices, including a wireless device configured, set up, and / or operable to communicate wirelessly with network node QQ110 and other communication devices. Similarly, network node QQ110 may be configured, capable, set up, and / or operable to communicate directly or indirectly with UE QQ112 and / or with other network nodes or devices in communication network QQ102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in communication network QQ102.

[0088] In the illustrated example, the core network QQ106 connects network node QQ110 to one or more hosts, such as host QQ116. These connections may be direct or indirect, via one or more intermediate networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network QQ106 includes one or more core network nodes (e.g., core network node QQ108) structured with hardware and software components. The characteristics of these components may be substantially similar to those described for the UE, network nodes, and / or hosts, and therefore their descriptions are generally applicable to the corresponding components of core network node QQ108. An exemplary core network node includes one or more of the following functions: 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 Protected Proxy (SEPP), Network Exposure Function (NEF), and / or User Plane Function (UPF).

[0089] Host QQ116 may be owned or controlled by a service provider other than the operator or provider of the access network QQ104 and / or the communication network QQ102, and may be operated by or on behalf of the service provider. Host QQ116 may host a variety of applications to provide one or more services. Examples of such applications include providing live and / or pre-recorded audio / video content, data collection services, analytical functions, social media, functions for controlling or, in some cases, interacting with remote devices, functions for alarms and surveillance centers, or any other such functions performed by the server.

[0090] Overall, the QQ100 communication system in Figure 9 enables connectivity between the UE, network nodes, and hosts. In this sense, the communication system may be configured to operate according to predefined rules or procedures, including, but not limited to, any other suitable wireless communication standards, such as GSM (Global System for Mobile Communications), 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 IEEE 802.11 standard (WiFi), and / or any other suitable wireless communication standards such as global interoperability for microwave access (WiMAX), Bluetooth, Z-Wave, near-field communications (NFC) ZigBee, LiFi, and / or LoRa and Sigfox, or any low-power wide area network (LPWAN) standards.

[0091] In some examples, the communication network QQ102 is a cellular network that implements 3GPP standardized features. Therefore, the communication network QQ102 may support network slicing to provide different logical networks to different devices connected to the communication network QQ102. For example, the communication network QQ102 may provide ultra-high reliability low latency communication (URLLC) services to some UEs while providing extended mobile broadband (eMBB) services to other UEs, and / or also provide massive machine-type communication (mMTC) / massive IoT services to further UEs.

[0092] In some examples, UE QQ112 is configured to transmit and / or receive information without direct human interaction. For example, the UE may be designed to transmit information to access network QQ104 on a predetermined schedule when triggered by an internal or external event, or in response to a request from access network QQ104. Furthermore, the UE may be configured to operate in single, multi-RAT, or multi-standard modes. For example, the UE may operate with one or a combination of Wi-Fi, NR (New Radio), and LTE, i.e., E-UTRAN (Enhanced UMTS Terrestrial Radio Access Network) New Radio-Dual Connectivity (EN-DC), or multi-radio dual connectivity (MR-DC).

[0093] In the example shown in Figure 9, the hub QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UE QQ112c and / or QQ112d) and a network node (e.g., network node QQ110b). In some examples, the hub QQ114 may be a controller, a router, a content source and analysis node, or any other communication device described herein with respect to the UE. For example, the hub QQ114 may be a broadband router that enables access to the core network QQ106 for the UE. In another example, the hub QQ114 may be a controller that sends commands or instructions to one or more actuators in the UE. The commands or instructions may be received from the UE, the network node QQ110, or by executable code, scripts, processes, or other instructions in the hub QQ114. In yet another example, the hub QQ114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, can perform data analysis or other processing. As another example, the hub QQ114 can be a content source. For example, for a UE that is a VR headset, display, loudspeaker, or other media distribution device, the hub QQ114 can retrieve VR assets, video, audio, or other media or data related to sensory information via network nodes, which the hub QQ114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In yet another example, the hub QQ114 acts as a proxy server or orchestrator for the UE, particularly when one or more of the UEs are low-energy IoT devices.

[0094] Hub QQ114 may have always-on / persistent or intermittent connections to network node QQ110b. Hub QQ114 may also enable different communication methods and / or schedules between Hub QQ114 and UEs (e.g., UE QQ112c and / or QQ112d), and between Hub QQ114 and the core network QQ106. In other examples, Hub QQ114 connects to the core network QQ106 and / or one or more UEs via a wired connection. Furthermore, Hub QQ114 may be configured to connect to an M2M service provider on the access network QQ104 and / or another UE via a direct connection. In some scenarios, a UE may establish a wireless connection with network node QQ110 while still being connected via wired or wireless connections through Hub QQ114. In some embodiments, the hub QQ114 may be a dedicated hub, i.e., a hub whose primary function is to route communication from the UE to the network node QQ110b and from the network node QQ110b to the UE. In other embodiments, the hub QQ114 may be a non-dedicated hub, i.e., a device that can operate to route communication between the UE and the network node QQ110b, but can also operate as a communication start point and / or end point for several data channels.

[0095] Figure 10 shows the UE QQ200 in several embodiments. As used herein, UE refers to a device that is capable of, configured, and / or operable of communicating wirelessly with network nodes and / or other UEs. Examples of UEs include, but are not limited to, smartphones, mobile phones, cell phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptop computers, laptop embedded devices (LEEs), laptop mounted devices (LMEs), smart devices, wireless customer premises equipment (CPEs), and vehicle-mounted or vehicle-embedded / integrated wireless devices. Other examples include any UE identified by the Third Generation Partnership Project (3GPP), including narrowband Internet of Things (NB-IoT) UEs, machine-type communications (MTC) UEs, and / or enhanced MTC (eMTC) UEs.

[0096] A UE may support device-to-device (D2D) communication by implementing 3GPP standards 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 does not necessarily have a user in the sense of a human user who owns and / or operates the associated device. Instead, a UE may represent a device (e.g., a smart sprinkler controller) that is intended to be sold to or operated by a human user, but may not be associated with a particular human user, or may not be associated with a particular human user in the first place. Alternatively, a UE may represent a device (e.g., a smart electricity meter) that is not intended to be sold to or operated by an end user, but may be associated with or operate for the benefit of a user.

[0097] UE QQ200 includes a processing circuit QQ202 operably coupled via bus QQ204 to an input / output interface QQ206, a power supply QQ208, a memory QQ210, a communication interface QQ212, and / or any other components, or any combination thereof. Some UEs may utilize all or a subset of the components shown in Figure 10. The level of integration between components may vary from UE to UE. Furthermore, some UEs may include multiple instances of components, such as multiple processors, memories, transceivers, transmitters, and receivers.

[0098] The processing circuit QQ202 may be configured to process instructions and data and to implement any sequential state machine capable of executing instructions stored in memory QQ210 as a machine-readable computer program. The processing circuit QQ202 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 with appropriate firmware, a microprocessor or digital signal processor (DSP) with appropriate software, one or more stored computer programs, a general-purpose processor, or any combination of the above. For example, the processing circuit QQ202 may include multiple central processing units (CPUs). The processing circuit QQ202 may be capable of providing UE QQ200 functionality either on its own or in conjunction with other UE QQ200 components, such as memory QQ210. For example, the processing circuit QQ202 may be configured to cause UE QQ202 to perform the method described with reference to one or more of Figures VV1 and VV2.

[0099] In this example, the input / output interface QQ206 may be configured to provide an input device, an output device, or one or more interfaces to one or more input and / or output devices. Examples of output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, emitters, smart cards, other output devices, or any combination thereof. Input devices may allow a user to capture information to the UE QQ200. Examples of input devices include touch-sensitive or presence-sensitive displays, cameras (e.g., digital cameras, digital video cameras, webcams, etc.), microphones, sensors, mice, trackballs, directional pads, trackpads, scroll wheels, smart cards, etc. Presence-sensitive displays may include capacitive or resistive touch sensors for detecting user input. Sensors may include, for example, accelerometers, gyroscopes, tilt sensors, force sensors, magnetometers, light sensors, proximity sensors, biosensors, or any combination thereof. Output devices may use the same type of interface port as input devices. For example, a Universal Serial Bus (USB) port may be used to provide input and output devices.

[0100] In some embodiments, the power supply QQ208 is structured as a battery or battery pack. Other types of power sources may be used, such as an external power source (e.g., an electrical outlet), a photovoltaic device, or a battery. The power supply QQ208 may further include a power circuit for distributing power from the power supply QQ208 itself and / or an external power source via an interface such as an input circuit or power cable. Distributing power may, for example, be for charging the power supply QQ208. The power circuit may perform any formatting, conversion, or other modifications to the power from the power supply QQ208 to make that power suitable for each component of the UE QQ200 to which it is supplied.

[0101] Memory QQ210 may be memory, or configured to contain 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, or flash drives. For example, memory QQ210 may contain one or more application programs QQ214, such as an operating system, web browser application, widget, gadget engine, or other application, and corresponding data QQ216. Memory QQ210 may store any of a variety of operating systems or combinations of operating systems for use by the UE QQ200.

[0102] The QQ210 memory can be configured to include several physical drive units, such as a redundant array of independent disks (RAID), flash memory, USB flash drives, external hard disk drives, thumb drives, pen drives, key drives, high-density digital versatile disk (HD-DVD) optical drives, internal hard disk drives, Blu-ray optical drives, holographic digital data storage (HDDS) optical drives, external mini dual in-line memory modules (DIMMs), synchronous dynamic random access memory (SDRAM), external microDIMM SDRAM, smart card memory such as a tamper-proof module in the form of a universal integrated circuit card (UICC) containing one or more subscriber identification modules (SIMs) such as USIM and / or ISIM, other memory, or any combination thereof. The UICC may be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly known as a "SIM card". Memory QQ210 may enable UE QQ200 to access instructions, application programs, etc., stored in temporary or non-temporary memory media, to offload data, or to upload data. Products such as products utilizing communication systems may be tangibly embodied as or within memory QQ210, and memory QQ210 may be a device-readable storage medium or may contain a device-readable storage medium.

[0103] The processing circuit QQ202 may be configured to communicate with an access network or other networks using the communication interface QQ212. The communication interface QQ212 may comprise one or more communication subsystems, including or communicatively coupled to an antenna QQ222. The communication interface QQ212 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 network node in the access network). Each transceiver may include a transmitter QQ218 and / or a receiver QQ220 suitable for providing network communication (e.g., optical, electrical, frequency-allocated, etc.). Furthermore, the transmitter QQ218 and receiver QQ220 may be coupled to one or more antennas (e.g., antenna QQ222), and may share circuit components, software, or firmware, or alternatively, may be implemented separately.

[0104] In some embodiments, the communication functions of the communication interface QQ212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication such as the use of the Global Positioning System (GPS) to determine location, other similar communication functions, or any combination thereof. Communication may be implemented in accordance with one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMAX, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), etc.

[0105] Regardless of the sensor type, a UE may provide the output of data captured by its sensors to network nodes via a wireless connection through the UE's communication interface QQ212. The data captured by the UE's sensors may be communicated to network nodes via another UE through a wireless connection. The output may be periodic (e.g., once every 15 minutes if reporting detected temperature), in response to a triggering event (e.g., an alarm is sent when humidity is detected), in response to a request (e.g., a user-initiated request), random (e.g., to equalize the load from reports from several sensors), or a continuous stream (e.g., a live video feed of a patient).

[0106] As another example, the UE may include an actuator, motor, or switch relating to a communication interface configured to receive radio input from a network node via a wireless connection. In response to the received radio input, the state of the actuator, motor, or switch may change. For example, the UE may include a motor that adjusts the control surface or rotor of a drone in flight according to the received input, or controls a robotic arm that performs a medical procedure according to the received input.

[0107] A UE, in the form of an Internet of Things (IoT) device, can be a device for use in one or more application areas, which include, but are not limited to, urban wearable technology, augmented industrial applications, and healthcare. Non-limiting examples of such IoT devices are devices that are connected refrigerators or freezers, TVs, connected lighting devices, energy meters, robotic vacuum cleaners, voice-controlled smart speakers, home security cameras, motion detectors, thermostats, smoke detectors, door / window sensors, flood / humidity sensors, electric door locks, connected doorbells, air conditioning systems such as heat pumps, autonomous vehicles, surveillance systems, weather monitoring devices, vehicle parking monitoring devices, electric vehicle charging stations, smartwatches, fitness trackers, head-mounted displays for augmented reality (AR) or virtual reality (VR), wearables for haptic augmentation or perceptual augmentation, water sprinklers, animal or product tracking devices, sensors for monitoring plants or animals, industrial robots, unmanned aerial vehicles (UAVs), and any kind of medical device such as a heart rate monitor or remotely controlled surgical robot, or devices embedded in them. The UE in the form of an IoT device includes, in addition to the other components described with respect to the UE QQ200 shown in Figure 10, circuitry and / or software depending on the intended application of the IoT device.

[0108] In another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurement and transmits the results of such monitoring and / or measurement to another UE and / or network node. In this case, the UE could be an M2M device, which is sometimes called an MTC device in a 3GPP context. In one specific example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, the UE may represent a vehicle, such as a car, bus, truck, ship, and airplane, or other equipment capable of monitoring its operational status and / or reporting on its operational status, or performing other functions related to its operation.

[0109] In practice, any number of UEs can be used together for a single use case. For example, the first UE may be the drone itself, or integrated within the drone, providing the drone's speed information (obtained through a speed sensor) to the second UE, which is the remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (for example, by controlling an actuator) to increase or decrease the drone's speed. The first and / or second UEs may also include two or more of the functions described above. For example, the UE may have sensors and actuators and handle the communication of data about both the speed sensor and the actuator.

[0110] Figure 11 shows a network node QQ300 according to several embodiments. As used herein, a network node refers to a device that is configured, set up, and / or operable to communicate directly or indirectly with UEs in a communication network and / or with other network nodes or devices. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points) and base stations (BSs) (e.g., radio base stations, node Bs, evolved node Bs (eNBs), and NR node Bs (gNBs)).

[0111] Base stations can be categorized based on the amount of coverage they provide (or, in other words, the base station's transmit power level), and are therefore sometimes called femto base stations, pico base stations, micro base stations, or macro base stations, depending on the amount of coverage they provide. A base station can be a relay node or relay donor node that controls relays. Network nodes can also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or remote radio unit (RRU), sometimes called a remote radio head (RRH). 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 are sometimes called nodes in a distributed antenna system (DAS).

[0112] Other examples of network nodes include multiple transmit point (multi-TRP) 5G access nodes, MSR equipment such as multi-standard radio (MSR) BS, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base station transceiver stations (BTSs), transmit points, transmit nodes, multi-cell / multicast coordinated entities (MCEs), operation and maintenance (O&M) nodes, operation support system (OSS) nodes, self-organizing network (SON) nodes, positioning nodes (e.g., evolved serving mobile location centers (E-SMLCs)), and / or drive test minimization (MDT).

[0113] Network node QQ300 includes a processing circuit QQ302, memory QQ304, communication interface QQ306, and power supply QQ308, and / or any other components, or any combination thereof. Network node QQ300 can be assembled from multiple physically distinct components (e.g., node B components and RNC components, or BTS components and BSC components), each of which may have its own respective components. In some scenarios where network node QQ300 has multiple distinct components (e.g., BTS components and BSC components), one or more of the distinct components may be shared among several network nodes. For example, a single RNC may control multiple node Bs. In such a scenario, each unique node B-RNC pair may, in some cases, be considered a single distinct network node. In some embodiments, network node QQ300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory QQ304 for different RATs), and some components may be reused (e.g., the same antenna QQ310 may be shared by different RATs). Network node QQ300 may also include multiple sets of various shown components for different radio technologies, such as GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, radio frequency identification (RFID), or Bluetooth radio technologies, integrated into network node QQ300. These radio technologies may be integrated into the same or different chips or sets of chips, and other components within network node QQ300.

[0114] The processing circuit QQ302 may include one or more combinations of microprocessors, controllers, central processing units, digital signal processors, application-specific integrated circuits, field-programmable gate arrays, or any other suitable computing devices, resources, or combinations of hardware, software, and / or encoded logic, which are capable of operating to provide network node QQ300 functionality, either alone or in combination with other network node QQ300 components such as memory QQ304.

[0115] In some embodiments, the processing circuit QQ302 includes a system-on-a-chip (SOC). In some embodiments, the processing circuit QQ302 includes one or more of the radio frequency (RF) transceiver circuit QQ312 and the baseband processing circuit QQ314. In some embodiments, the radio frequency (RF) transceiver circuit QQ312 and the baseband processing circuit QQ314 may be on separate chips (or sets of chips), boards, or units such as radio and digital units. In alternative embodiments, some or all of the RF transceiver circuit QQ312 and the baseband processing circuit QQ314 may be on the same chip or set of chips, board, or unit.

[0116] Memory QQ304 may include, but is not limited to, any form of volatile or non-volatile computer-readable memory, including persistent storage, solid memory, remote-mount memory, magnetic media, optical media, random-access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disks), removable storage media (e.g., flash drives, compact discs (CDs), or digital video discs (DVDs)), and / or any other volatile or non-volatile, non-temporary device-readable and / or computer-executable memory devices that store information, data, and / or instructions that can be used by the processing circuit QQ302. Memory QQ304 may store any suitable instructions, data, or information, including other instructions, that can be executed by the processing circuit QQ302 and utilized by the network node QQ300, including applications that include one or more computer programs, software, logic, rules, code, and tables. Memory QQ304 may be used to store calculations performed by the processing circuit QQ302 and / or data received via the communication interface QQ306. In some embodiments, the processing circuit QQ302 and memory QQ304 are integrated.

[0117] The communication interface QQ306 is used in wired or wireless signaling and / or data between network nodes, access networks, and / or UEs. As shown, the communication interface QQ306 includes (one or more) ports / (one or more) terminals QQ316 for sending and receiving data to and from the network, for example, over a wired connection. The communication interface QQ306 also includes a wireless front-end circuit QQ318, which is coupled to or, in some embodiments, may be part of the antenna QQ310. The wireless front-end circuit QQ318 includes a filter QQ320 and an amplifier QQ322. The wireless front-end circuit QQ318 may be connected to the antenna QQ310 and the processing circuit QQ302. The wireless front-end circuit may be configured to adjust signals communicated between the antenna QQ310 and the processing circuit QQ302. The wireless front-end circuit QQ318 may receive digital data to be sent to other network nodes or UEs via the wireless connection. The wireless front-end circuit QQ318 can convert digital data into a radio signal with appropriate channel and bandwidth parameters using a combination of filter QQ320 and / or amplifier QQ322. The radio signal can then be transmitted via antenna QQ310. Similarly, when receiving data, antenna QQ310 can collect a radio signal, which is then converted into digital data by the wireless front-end circuit QQ318. The digital data can then be passed to processing circuit QQ302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0118] In some alternative embodiments, the network node QQ300 does not include a separate radio front-end circuit QQ318; instead, the processing circuit QQ302 includes the radio front-end circuit and is connected to the antenna QQ310. Similarly, in some embodiments, all or part of the RF transceiver circuit QQ312 is part of the communication interface QQ306. In yet another embodiment, the communication interface QQ306, as part of a radio unit (not shown), includes one or more ports or terminals QQ316, the radio front-end circuit QQ318, and the RF transceiver circuit QQ312, and the communication interface QQ306 communicates with a baseband processing circuit QQ314, which is part of a digital unit (not shown).

[0119] Antenna QQ310 may include one or more antennas or antenna arrays configured to transmit and / or receive radio signals. Antenna QQ310 may be coupled to the radio front-end circuit QQ318 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna QQ310 is separate from the network node QQ300 and can be connected to the network node QQ300 through an interface or port.

[0120] The antenna QQ310, the communication interface QQ306, and / or the processing circuit QQ302 may be configured to perform any receiving operations and / or certain acquisition operations as described herein as being performed by a network node. Any information, data, and / or signals may be received from the UE, another network node, and / or any other network equipment. Similarly, the antenna QQ310, the communication interface QQ306, and / or the processing circuit QQ302 may be configured to perform any transmitting operations as described herein as being performed by a network node. Any information, data, and / or signals may be transmitted to the UE, another network node, and / or any other network equipment.

[0121] Power supply QQ308 provides power to the various components of network node QQ300 in a form suitable for each component (for example, at the voltage and current levels required for each respective component). Power supply QQ308 may further include, or be coupled to, a power management circuit for supplying power to the components of network node QQ300 to perform the functions described herein. For example, network node QQ300 may be connectable to an external power source (e.g., a power grid, an electrical outlet) via an input circuit or interface such as an electrical cable, thereby the external power source powers the power circuit of power supply QQ308. As a further example, power supply QQ308 may include a power source in the form of a battery or battery pack, connected to or integrated into the power circuit. The battery may provide backup power in the event of an external power failure.

[0122] Embodiments of the network node QQ300 may include additional components other than those shown in Figure 11 to provide several aspects of the network node's functionality, including any of the functions described herein and / or functions necessary to support the subject matter described herein. For example, the network node QQ300 may include user interface equipment for enabling the input of information to and from the network node QQ300. This may enable a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node QQ300.

[0123] Figure 12 is a block diagram of host QQ400, which may be one embodiment of host QQ116 in Figure 9, according to various aspects described herein. Host QQ400 as used herein may be a variety of combinations of hardware and / or software, including standalone servers, blade servers, cloud implementation servers, distributed servers, virtual machines, containers, or processing resources in a server farm. Host QQ400 may provide one or more services to one or more UEs.

[0124] The host QQ400 includes a processing circuit QQ402 operably coupled to an input / output interface QQ406, a network interface QQ408, a power supply QQ410, and memory QQ412 via a bus QQ404. Other embodiments may include other components. The characteristics of these components may be substantially the same as those described with respect to the devices in previous figures, such as Figures QQ2 and QQ3, and therefore their descriptions are generally applicable to the corresponding components of the host QQ400.

[0125] Memory QQ412 may include one or more computer programs, including one or more host application programs QQ414 and data QQ416, where data QQ416 may include user data, for example, data generated by the UE for host QQ400, or data generated by host QQ400 for the UE. Embodiments of host QQ400 may utilize only a subset or all of the components shown. Host application program QQ414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Multipurpose Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementation forms of the UE (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application program QQ414 can also provide user authentication and license checks, and can periodically report health, root, and content availability to a central node, such as devices in the core network or devices at the edge of the core network. Thus, the host QQ400 can select and / or direct different hosts for over-the-top services for the UE. The host application program QQ414 can support various protocols, including HTTP Live Streaming (HLS), Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), and Dynamic Adaptive Streaming over HTTP (MPEG-DASH).

[0126] Figure 13 is a block diagram showing a virtualized environment QQ500 in which functions implemented by several embodiments can be virtualized. In this context, virtualization means creating a virtual version of an apparatus or device, which may include virtualizing hardware platforms, storage devices, and networking resources. The virtualization used herein may apply to any device or its components described herein 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 functionality described herein may be implemented as virtual components, executed by one or more virtual machines (VMs) implemented in one or more virtualized environments QQ500 hosted by one or more hardware nodes, such as network nodes, UEs, core network nodes, or hardware computing devices acting as hosts. Furthermore, in embodiments in which the virtual nodes do not require wireless connectivity (e.g., core network nodes or hosts), the nodes may be fully virtualized.

[0127] Application QQ502 (which may alternatively be referred to as a software instance, virtual appliance, network function, virtual node, virtual network function, etc.) runs in the virtualized environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0128] Hardware QQ504 includes processing circuits, memory for storing software and / or instructions executable by the hardware processing circuits, and / or other hardware devices described herein, such as network interfaces and input / output interfaces. The software is executed by the processing circuits to instantiate one or more virtualization layers QQ506 (also called a hypervisor or virtual machine monitor (VMM)), providing VM QQ508a and QQ508b (one or more of which are commonly referred to as VM QQ508), and / or may implement any of the functions, features, and / or benefits described with respect to some embodiments described herein. The virtualization layer QQ506 may present VM QQ508 with a virtual operating platform that appears to be networking hardware.

[0129] VM QQ508 features virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and may be powered by the corresponding virtualization layer QQ506. Different embodiments of the virtual appliance QQ502 may be implemented on one or more VM QQ508s, and the implementation may be carried out in different ways. Hardware virtualization is referred to as network function virtualization (NFV) in several contexts. NFV can be used to consolidate many types of network equipment onto industry-standard high-volume server hardware, physical switches, and physical storage, which may reside in data centers and customer premises equipment.

[0130] In the context of NFV, a VM QQ508 can be a software implementation of a physical machine, where programs run as if they were running on a physical, non-virtualized machine. Each VM QQ508 and its portion of the hardware QQ504 on which it runs, whether dedicated hardware for that VM and / or hardware shared by that VM with other VMs in the VM, form a separate virtual network element. Furthermore, in the context of NFV, the virtual network function is responsible for handling specific network functions running in one or more VM QQ508s on the hardware QQ504, and corresponds to the application QQ502.

[0131] Hardware QQ504 can be implemented in a standalone network node with general or specific components. Hardware QQ504 can implement some functions through virtualization. Alternatively, Hardware QQ504 may be part of a larger cluster of hardware (such as in a data center or CPE) where many hardware nodes cooperate and are managed via management and orchestration QQ510, which oversees the lifecycle management of applications QQ502. In some embodiments, Hardware QQ504 is coupled to one or more radio units, each including one or more transmitters and one or more receivers, which may be coupled to one or more antennas. The radio units may communicate directly with other hardware nodes via one or more suitable network interfaces and may be used in combination with virtual components to provide a virtual node with radio capabilities, such as a radio access node or base station. In some embodiments, some signaling may be provided using a control system QQ512, which may be used alternatively for communication between hardware nodes and radio units.

[0132] Figure 14 shows a communication diagram of host QQ602 communicating with UE QQ606 via network node QQ604 over a partial wireless connection, according to several embodiments. Next, exemplary implementations of various embodiments of the UEs (such as UE QQ112a in Figure 9 and / or UE QQ200 in Figure 10), network nodes (such as network node QQ110a in Figure 9 and / or network node QQ300 in Figure 11), and hosts (such as host QQ116 in Figure 9 and / or host QQ400 in Figure 12), as described in the previous paragraph, will be described with reference to Figure 14.

[0133] Similar to the host QQ400, embodiments of the host QQ602 include hardware such as a communication interface, processing circuitry, and memory. The host QQ602 also includes software that is stored in or accessible by the host QQ602 and executable by the processing circuitry. The software includes a host application that may be capable of operating to serve a remote user, such as a UE QQ606 connected via an over-the-top (OTT) connection QQ650 extending between the UE QQ606 and the host QQ602. When serving a remote user, the host application may provide user data transmitted using the OTT connection QQ650.

[0134] Network node QQ604 includes hardware that enables network node QQ604 to communicate with host QQ602 and UE QQ606. Connectivity QQ660 can be direct or traverse one or more other intermediate networks, such as a core network (similar to core network QQ106 in Figure 9) and / or one or more public networks, private networks, or hosted networks. For example, the intermediate network could be a backbone network or the internet.

[0135] The UE QQ606 includes hardware and software that is stored in or accessible by the UE QQ606 and executable by the UE's processing circuitry. The software includes client applications, such as a web browser or operator-specific “app,” which may be capable of operating to serve human or non-human users through the UE QQ606, with the support of the host QQ602. On the host QQ602, the running host application may communicate with the running client application via the UE QQ606 and the OTT connection QQ650, which terminates on the host QQ602. When serving a user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection QQ650 may transfer both the request data and the user data. The UE's client application may interact with the user to generate user data that the UE's client application provides to the host application via the OTT connection QQ650.

[0136] The OTT connection QQ650 may extend via connection QQ660 between host QQ602 and network node QQ604, and via radio connection QQ670 between network node QQ604 and UE QQ606, in order to provide connectivity between host QQ602 and UE QQ606. The connections QQ660 and radio connection QQ670, which the OTT connection QQ650 may provide, are depicted abstractly to illustrate communication between host QQ602 and UE QQ606 via network node QQ604, without explicit reference to the intermediary devices and the precise routing of messages through these devices.

[0137] As an example of transmitting data via an OTT connection QQ650, in step QQ608, host QQ602 provides user data, which may be done by running a host application. In some embodiments, the user data relates to a specific human user interacting with UE QQ606. In other embodiments, the user data relates to UE QQ606 sharing data with host QQ602 without explicit human interaction. In step QQ610, host QQ602 initiates a transmission to carry user data toward UE QQ606. Host QQ602 may initiate a transmission in response to a request sent by UE QQ606. The request may be triggered by human interaction with UE QQ606 or by the operation of a client application running on UE QQ606. The transmission may proceed through network node QQ604, as taught in the embodiments described throughout this disclosure. Accordingly, in step QQ612, network node QQ604 transmits the user data carried in the transmission initiated by host QQ602 to UE QQ606, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ614, UE QQ606 receives the user data carried in the transmission, which may be done by a client application running on UE QQ606 related to a host application run by host QQ602.

[0138] In some examples, UE QQ606 runs a client application that provides user data to host QQ602. User data may be provided in response to or in reaction to data received from host QQ602. Thus, in step QQ616, UE QQ606 may provide user data, which may be done by running a client application. When providing user data, the client application may further consider user input received from the user via the input / output interface of UE QQ606. Regardless of the particular format in which the user data is provided, UE QQ606 initiates the transmission of the user data to host QQ602 via network node QQ604 in step QQ618. In step QQ620, in accordance with the teachings of embodiments described throughout this disclosure, network node QQ604 receives user data from UE QQ606 and initiates the transmission of the received user data to host QQ602. In step QQ622, host QQ602 receives user data carried in a transmission initiated by UE QQ606.

[0139] One or more of the various embodiments improve the performance of OTT services provided to UE QQ606 by using an OTT connection QQ650 in which the wireless connection QQ670 forms the final segment. More precisely, the teachings of these embodiments may improve the security of the connection.

[0140] In an exemplary scenario, factory status information may be collected and analyzed by the host QQ602. As another example, the host QQ602 may process audio and video data that may be extracted from the UE for use in creating maps. As yet another example, the host QQ602 may collect and analyze real-time data to help control vehicle congestion (e.g., control traffic signals). As yet another example, the host QQ602 may store surveillance video uploaded by the UE. As yet another example, the host QQ602 may store or control access to media content, such as video, audio, VR, or AR, which the host QQ602 can broadcast, multicast, or unicast to the UE. As yet another example, the host QQ602 may be used for energy pricing, remote control of non-time-constrained electrical loads to balance generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, extracting, storing, analyzing, and / or transmitting data.

[0141] In some embodiments, measurement procedures may be provided for the purpose of monitoring data rate, latency, and other factors, which are improved by one or more embodiments. Further optional network functions may be provided for reconfiguring the OTT connection QQ650 between host QQ602 and UE QQ606 in response to variations in measurement results. Measurement procedures and / or network functions for reconfiguring the OTT connection may be implemented in the software and hardware of host QQ602 and / or UE QQ606. In some embodiments, sensors (not shown) may be deployed in or in relation to other devices through which the OTT connection QQ650 passes, and the sensors may participate in the measurement procedures by supplying values ​​of the monitored quantities exemplified above, or values ​​of other physical quantities that the software can calculate or estimate the monitored quantities of. Reconfiguring the OTT connection QQ650 may include message formatting, retransmission settings, preferred routing, etc., and the reconfiguration does not require direct modification of the operation of network node QQ604. Such procedures and functions are known and practiced in the art. In some embodiments, the measurements may involve proprietary UE signaling by the host QQ602 to facilitate measurements such as throughput, propagation time, and latency. The measurements may be implemented in which software uses an OTT-connected QQ650 to cause messages, particularly empty or "dummy" messages, to be sent while monitoring propagation time, errors, etc.

[0142] The computing devices described herein (e.g., UEs, network nodes, hosts) may include the shown combinations of hardware components, but other embodiments may comprise computing devices with different combinations of components. It should be understood that these computing devices may comprise any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. The determining, calculating, retrieving, or similar operations described herein may be performed by processing circuits, which may process information by, for example, converting retrieved information to other information, comparing the retrieved or converted information to information stored in a network node, and / or performing one or more operations based on the retrieved or converted information and as a result of the decisions made by the processing. Furthermore, although components are illustrated as a single box located within a larger box, or as a single box nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that constitute a single shown component, and functions may be separated between the distinct components. For example, a communication interface may be configured to include any of the components described herein, and / or the functions of those components may be separated between the processing circuit and the communication interface. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware, while the computationally intensive functions may be implemented in hardware.

[0143] In some embodiments, some or all of the functions described herein may be provided by a processing circuit that executes instructions stored in memory, which in some embodiments may be a computer program product in the form of a non-temporary computer-readable storage medium. In alternative embodiments, some or all of the functions may be provided by a processing circuit without executing instructions stored in a separate or individual device-readable storage medium, such as in a hardwired manner. In any of those particular embodiments, whether or not it executes instructions stored in a non-temporary computer-readable storage medium, the processing circuit may be configured to perform the functions described. The benefits provided by such functions are enjoyed by the processing circuit alone, or by the computing device as a whole, but not limited to other components of the computing device, and / or generally by the end user and the wireless network.

Claims

1. A method performed by a user device (UE), Preparing an announcement message for transmission, the announcement message comprising: (a) an instruction on the user equipment's ability to act as a relay in a UE-UE (U2U) connection; and (b) an instruction, in response to the determination that the UE is connected to a wireless communication network, that a network-based security protocol is available to establish security for the U2U connection. Sending the aforementioned notification message Methods that include...

2. The method according to claim 1, wherein the UE periodically determines the connection status of the UE to the wireless communication network.

3. The method according to claim 1, wherein the UE determines the connection status of the UE to the wireless communication network when it receives a discovery message from another UE.

4. The method according to claim 1, wherein the instruction that a network-based security protocol is available is omitted from the notification message in response to a determination that the UE is not connected to the wireless communication network.

5. The method according to claim 1, wherein the instruction that a network-based security protocol is available is included in the list of available security protocols for establishing security for the U2U connection.

6. The method according to claim 5, wherein the list of available security protocols includes instructions for prioritizing the available security protocols for establishing security for the U2U connection.

7. The method according to claim 5, wherein the available security protocols for establishing security for the U2U connection include one or more peer-to-peer based security protocols.

8. The method according to claim 1, wherein the notification message is broadcast to enable discovery of the UE by one or more other UEs.

9. The method according to claim 1, wherein the notification message is transmitted in response to the receipt of a discovery message from another UE.

10. The method according to claim 1, further comprising sending a discovery key request message to a core network node and, in response, receiving a relay service code that authorizes the UE to act as a relay in a U2U connection.

11. The method according to claim 10, wherein the notification message includes an instruction for the relay service code.

12. The method according to claim 10, wherein the discovery key request message further includes an instruction on the ability of the UE to act as a relay in a U2U connection.

13. The method according to claim 1, further comprising establishing a U2U connection with a source UE and a target UE.

14. The method according to claim 13, wherein establishing the U2U connection includes receiving a connection request message from one or more of the source UE and the target UE, which includes instructions for a selected security protocol for establishing the security for the U2U connection.

15. A method performed by a first user device (UE), Detecting an announcement message transmitted by a second UE, wherein the announcement message includes an instruction indicating the second UE's ability to act as a relay in a U2U connection, and an instruction indicating that a network-based security protocol is available to establish security for the U2U connection, in response to a determination that the second UE is connected to a wireless communication network. Based on the instructions contained in the notification message, select a security protocol for establishing security for the U2U connection, To establish a U2U connection with the target UE via the second UE acting as a relay and Methods that include...

16. The method of claim 15, wherein establishing the U2U connection includes sending a connection request message to the second UE, which includes instructions for a selected security protocol for establishing the U2U connection.

17. The method according to claim 15, wherein the instruction that a network-based security protocol is available is included in the list of available security protocols for establishing security for the U2U connection.

18. The method according to claim 17, wherein the list of available security protocols includes instructions for prioritizing the available security protocols for establishing security for the U2U connection.

19. The method according to claim 17, wherein the available security protocol for establishing security for the U2U connection includes one or more peer-to-peer based security protocols.

20. The method according to claim 15, wherein the notification message is broadcast by the second UE to enable discovery of the second UE.

21. The method according to claim 15, further comprising sending a discovery message and, in response, receiving the notification message from the second UE.

22. The method according to claim 15, further comprising sending a discovery key request message to a core network node and, in response, receiving a relay service code that authorizes the first UE to act as either a source UE or a target UE in a U2U connection.

23. The method according to claim 22, wherein the discovery key request message further includes an instruction on the ability of the first UE to act as a source UE or a target UE in a U2U connection.

24. A user device configured to perform the method described in any one of claims 1 to 23.

25. A user device comprising a processing circuit and a memory collectively configured to perform the method described in any one of claims 1 to 23.

Images