Mobility when supporting AEAD algorithms in 3GPP system

Abstract

A method performed by a User Equipment (UE) comprises sending a registration request to a target core network node, the registration request comprising at least one of UE support for one or more Authenticated Encryption with Associated Data (AEAD) algorithms, one or more UE supported AEAD options, and one or more UE supported AEAD modes, and determining at least one of a network selected AEAD algorithm, a network selected AEAD option, and a network selected AEAD mode.

Description

MOBILITY WHEN SUPPORTING AEAD ALGORITHMS IN 3GPP SYSTEMTECHNICAL FIELD

[0001] The present disclosure relates generally to signaling capabilities and selected parameters.BACKGROUND

[0002] An Authenticated Encryption with Associated Data (AEAD) algorithm can be used in two different modes:

[0003] Encrypt and authenticate:• Encrypt-then-Medium Access Control (MAC) (EtM)• Some AEAD algorithms are using one key but other AEAD algorithms can use two keys (both options should be allowed)• Authenticate:• MAC (no encryption)• Only using one key for integrity protection

[0004] Depending on the AEAD algorithm instantiation, the AEAD algorithm can also be used as an only encryption algorithm.

[0005] The 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 23.501 describes the 5G network architecture. The User Equipment (UE) is a mobile device used by the user to wirelessly access the network. The radio access network (RAN) function or base station called Next Generation Node B (gNB) is responsible for providing wireless radio communication to the UE and connecting the UE to the core network. The core network function called Access and Mobility Management Function (AMF) is responsible for handling the mobility of the UE, among other responsibilities. Another core network function called Session Management Function (SMF) is responsible for handling the session and traffic steering of the UE, among other responsibilities. Yet another core network function called User Plane Function (UPF) is responsible for interconnecting to data network, packet routing and forwarding, among other responsibilities.

[0006] The RAN in 5G (called NG- RAN) has another type of base station called ng-eNB. This is an evolved LTE eNB connected to a 5G Core.

[0007] The UE interacts with the ng-eNB or the gNB over-the-air using radio interface. The radio interface traffic comprises both control plane traffic and user plane traffic. The radio control plane is also called RRC (Radio Resource Control). The ng-eNB or the gNB in turn interacts with the AMF using the interface called the N2. The interface between the AMF andthe SMF is called the Nil. Similarly, ng-eNB or the gNB and the UPF interact using the interface called the N3. There is no direct interface between the ng-eNB or gNB and the SMF, therefore, they interact via the AMF.

[0008] Figure (FIG.) 1 illustrates a simplified 5G network. In FIG. 1, the gNB is connected to AMF. FIG. 2 illustrates a simplified 5G network. In FIG. 2, the ng-eNB is connected to AMF.

[0009] FIG. 3 illustrates a simplified 5G network. In FIG. 3 the gNB is acting as a master node in Dual Connectivity. The gNB is connected to the AMF via the N2 interface. The NG- eNB is acting as the secondary node in Dual Connectivity and is connected to the gNB via the Xn interface.

[0010] FIG. 4 illustrates a simplified 5G network. In FIG. 4, the ng-eNB is acting as a master node in Dual Connectivity. The ng-eNB is connected to the AMF via the N2 interface. The gNB is acting as the secondary node in Dual Connectivity and is connected to the ng-eNB via the Xn interface.

[0011] The logical aspect between the UE and the AMF is referred to as non-access stratum (NAS) and that between the UE and the gNB is referred to as access stratum (AS).Correspondingly, the security of communication (control plane and user plane, if applicable) are referred to as NAS security and AS security, respectively. The AS security comprises confidentiality and integrity protection of both the control plane (i.e., the RRC) and the user plane traffic. The radio bearers in AS that carry control planes or the RRC messages are called signaling radio bearers (SRB). Similarly, the radio bearer in AS that carries user plane messages is called data radio bearer (DRB).

[0012] In the 5G system, the AS security is mandatory for the RRC but it is optional for the user plane. It means that that both the confidentiality and the integrity protection will be activated for the RRC, however, the confidentiality and the integrity protection are optional to use for the user plane.

[0013] A UE indicates its security capability to the network in 5G system according to the following scheme. A Registration Request message is sent by the UE to the AMF in order for the UE to register in the network. Registration Request message is defined in TS 24.501, in clause 8.2.6.

[0014] Registration Request message is mapped to initial Message in step 1 in FIG. 5.

[0015] The UE indicates its support of security algorithms for encryption and integrity protection in Registration Request message to the AMF in core network.

[0016] Allocated algorithm identifiers. Indication of supported security algorithms over Uu interface (UE -> AMF).

[0017] TS 33.501, clause 5.11.1, defines the already allocated algorithm identifier values.

[0018] NEA4 -> NEA7 defined in TS 33.501, which corresponds to 5G-EA4-> 5G-EA7 defined in TS 24.501, are currently not occupied (not assigned to any particular algorithm) and NIA4 -> NIA7defined in TS 33.501, which corresponds to 5G-EI4-> 5G-EI7 defined in TS 24.501, are currently not occupied (not assigned to any particular algorithm).

[0019] But other SAGE 256-bit algorithms, which are not AEAD algorithms, will most likely be introduced in 5GS already in Rel-19 and they will probably be allocated to the currently unused NEA4-NEA7 and NIA4-NIA7, or at least some of these currently unused code points. If this is the case then CT1 needs to extend the UE Security Capability IE adding new code points, for example NEA8-NEA15 and NIA8-NIA15. It is more likely that any of NEA8-NEA16 and NIA8-NIA15 will be used instead to indicate UE support of AEAD algorithms to the network.

[0020] CT1 could also specify a new IE in Registration Request for UE indicating UE supported AEAD algorithms and UE supported AEAD mode.

[0021] Indication of supported security algorithms over N2 interface (AMF -> gNB).

[0022] N2 interface in TS 38.413 has already been extended in 3GPP specifications as 16 code points are reserved for integrity algorithm indication and 16 code points are reserved for encryption algorithm indication.

[0023] On N2 interface it is possible to indicate UE support of 16 different integrity algorithms and 16 different encryption algorithms, see TS 38.413, see clause 9.3.1.86 UE Security Capabilities.

[0024] Indication of supported security algorithms over Xn interface (source gNB <-> target gNB).

[0025] Xn interface in TS 38.423 has already been extended in 3GPP specifications as 16 code points are reserved for integrity algorithm indication and 16 code points are reserved for encryption algorithm indication.

[0026] On Xn interface it is possible to indicate UE support of 16 different integrity algorithms and 16 different encryption algorithms, see TS 38.423, see clause 9.2.3.49 UE Security Capabilities.

[0027] AMF indicates the selected security algorithm to the UE in 5G system.

[0028] When the AMF receives the Registration Request message from the UE, then the AMF needs to select the security algorithm to be used for encryption of NAS messages sent between AMF and UE; and select the security algorithm to be used for integrity protection of NAS messages sent between AMF and UE.

[0029] This is described in TS 33.501, clause 6.7.2. The AMF needs to select an algorithm which is supported both by UE and AMF. FIG. 6 illustrates a NAS Security Mode Command procedure.

[0030] A gNB indicates the selected security algorithm to the UE in 5G system.

[0031] When the AMF receives the Registration Request message from the UE, then the AMF needs to map the supported security algorithms which the UE indicated in the IE (Information Element) named “UE security capability” included in Registration Request message to the IE named “UE security capability” on N2 interface to the gNB.

[0032] When the gNB receives the IE named “UE security capability” on N2 interface from the AMF, then the gNB needs to select the security algorithm to be used for encryption of AS messages sent between gNB and UE; and select the security algorithm to be used for integrity protection of AS messages sent between gNB and UE.

[0033] Each legacy gNB is configured via network management with lists of algorithms which are allowed for usage. There is one list for integrity algorithms, and one for ciphering algorithms. These lists shall be ordered according to a priority decided by the operator. When AS security context is to be established in the gNB, the AMF shall send the UE 5G security capabilities to the gNB. The gNB shall choose the ciphering algorithm which has the highest priority from its configured list and is also present in the UE 5G security capabilities.

[0034] This above is described in TS 33.501, clause 6.7.4 and 6.7.3. The gNB needs to select an algorithm which is supported both by UE and gNB. FIG. 7 illustrates an AS Security Mode Command Procedure.BRIEF DESCRIPTION OF THE DRAWINGS

[0035] The drawings illustrate selected embodiments of the disclosed subject matter.

[0036] FIG. 1 illustrates a simplified 5G network.

[0037] FIG. 2 illustrates a simplified 5G network.

[0038] FIG. 3 illustrates a simplified 5G network.

[0039] FIG. 4 illustrates a simplified 5G network.

[0040] FIG. 5 illustrates a signal flow that includes signaling between a UE and an AMF.

[0041] FIG. 6 illustrates a NAS Security Mode Command procedure.

[0042] FIG. 7 illustrates an AS Security Mode Command Procedure.

[0043] FIG. 8 illustrates a signal flow related to an N2 interface.

[0044] FIG. 9 illustrates a signal flow related to an Xn interface.

[0045] FIG. 10 illustrates a signal flow related to an N2 interface.

[0046] FIG. 11 illustrates a signal flow related to an N14 interface.

[0047] FIG. 12 illustrates a signal flow related to an Xn interface.

[0048] FIG. 13 illustrates an example of a communication system.

[0049] FIG. 14 illustrates an example UE.

[0050] FIG. 15 illustrates an example network node.

[0051] FIG. 16 illustrates an example host.

[0052] FIG. 17 illustrates an example virtualization environment.

[0053] FIG. 18 illustrates an example host.DETAILED DESCRIPTION

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

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

[0056] There currently exist certain challenge(s). In 3GPP, separate algorithms for encryption and integrity protection have been specified so far, where two different security keys are generated and used i.e. a first security key for encryption and a second security key for integrity protection.

[0057] It may be considered to support AEAD algorithms in 5G system, RAN nodes gNB or ng- eNB and in core network node AMF.

[0058] It may also be considered to support AEAD algorithms in 6G system.

[0059] A dedicated authenticated encryption (AE) algorithm can be a single primitive for both encryption and integrity, using only a single key (e.g., Encrypt-then-MAC (EtM)). But an AE algorithm can still be used as only encryption algorithm or as an only integrity algorithm. Both a 128 or a 256 bit key length can be used with a dedicated AE algorithm and both options should be allowed.

[0060] UE indicates its support of one or several AEAD algorithms in a Registration Request message to the AMF in core network.

[0061] The UE also indicates its support of AEAD options to the AMF in the core network. Onepotential AEAD option could be UE supported AEAD modes:■ Single AEAD algorithm used for encryption and integrity protection,■ single AEAD algorithm used for encryption only,■ single AEAD algorithm used for integrity protection only.

[0062] Potential options how to achieve this are described in previous applications. But there can be other AEAD options then AEAD mode as well, which are not further described herein.

[0063] In this disclosure, the following problems have been identified with the existing specifications in 3GPP:It is not specified in 3GPP specifications how the UE supported AEAD algorithms and / or UE supported AEAD modes, and / or additional UE supported AEAD options, are transferred between network nodes on N2, Xn, N14 interfaces, at mobility.It is not specified in 3GPP specifications how the selected AEAD algorithm and / or selected AEAD mode and / or additional selected AEAD options, are transferred between network nodes on N2, Xn, N14 interfaces, at mobility.The above problems apply also to a ng-eNB connected to a 5GC.

[0064] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. When a UE is supporting AEAD algorithms, UE indicates its UE capabilities as UE support of AEAD algorithms and / or UE support of AEAD options and / or UE support of AEAD modes, in Registration Request message to the AMF in core network, as described in previous applications.

[0065] In existing systems, it is not specified how the UE capabilities as described above are transferred between network nodes in 5G system and how the selected parameters are transferred between network nodes in 5G system. The embodiments in this disclosure describe how to extend the network interfaces in order for the network to be able to transfer parameters between network nodes at mobility. These parameters are:

[0066] -UE capabilities as UE support of AEAD algorithms and / or UE support of AEAD options and / or UE support of AEAD modes;

[0067] -network selected AEAD algorithm and / or AEAD options and / or AEAD mode.

[0068] The following procedures are considered:• Initial Context Setup procedure• Xn handover• N2 handoverMobility registrationDual Connectivity

[0069] Solutions are proposed in order to support new AEAD algorithms and / or new AEAD options and / or new AEAD modes in UE and network. The following extensions are proposed: Extensions to N2 interface when Initial Context Setup is requested from AMF to gNB or ng-eNB Extensions to Xn interface at Xn handoverExtensions to N2 interface and N14 interface at N2 HOExtensions to N14 interface at Mobility registration Extensions to Xn interface for Dual Connectivity

[0070] Certain embodiments may provide one or more of the following technical advantages. Network interfaces are extended in order to transport the UE capability for UE supported AEAD algorithms and / or UE supported AEAD options and / or UE supported AEAD modes, in between network nodes at mobility as Initial context setup in RAN, Xn handover, N2 handover, Mobility registration and Dual Connectivity.

[0071] Initial Context Setup over N2 interface

[0072] Embodiment 1 - Extend N2 interface (Initial Context Setup Request message)

[0073] This embodiment describes how to extend N2 interface with new code points for UE supported AEAD algorithms and / or UE supported AEAD options and / or UE supported AEAD modes, when Initial Context Setup Request procedure is initiated by AMF to gNB or ng-eNB as shown in step 3 of FIG. 8.

[0074] Initial Context Setup Request message is specified in TS 38.413.

[0075] 1. UE registers to the 5G network and indicates its support of AEAD algorithms and the supported AEAD modes in Registration Request message. 2. AMF may initiate Authentication procedure and / or NAS Security Mode Command procedure to establish security between UE and AMF. 3. The AMF initiates Initial Context Setup procedure with gNB or ng- eNB over N2 interface and includes UE support of AEAD algorithms and / or UE supported AEAD options and / or UE supported AEAD modes to the gNB or ng-eNB. The N2 interface may need to be extended to support these new indications. Initial Context Setup Request message is specified in TS 38.413. 4. The gNB or ng-eNB initiates AS SMC (AS Security Mode Command) procedure with UE, with the selected AEAD algorithm, selected AEAD options and selected AEAD mode. No DRB’s with the UE is established.

[0076] Mobility - Xn handover

[0077] Embodiment 2 - Extend Xn interface (Handover Request / Handover Request Acknowledge messages)

[0078] This embodiment describes how to extend Xn interface with new code points for UEsupported AEAD algorithms and / or UE supported AEAD options and / or UE supported AEAD modes when handover (Handover Request / Handover Request Acknowledge messages) is initiated by source gNB or source ng-eNB, to target gNB or target ng-eNB as described in steps 1, 2, and 3 in FIG. 9. Handover Request and Handover Request Acknowledge messages are specified in TS 38.423. Handover command (HO Command) or RRC Connection Reconfiguration message or RRC Reconfiguration message is specified in TS 38.331.

[0079] 1. Source gNB or source ng-eNB initiates Handover Request message with target gNB or ng-eNB and indicates in Handover Request message the UE supported AEAD algorithms, UE supported AEAD options and UE supported AEAD modes. The Xn interface may be extended to support these new indications. 2. Target gNB or target ng-eNB selects an AEAD algorithm, selects AEAD options and selects AEAD mode to be used with UE and indicates to the UE the selected AEAD algorithm, the selected AEAD option and the selected AEAD mode to be used with the target gNB or target ng-eNB in Handover Request Acknowledge message. The Xn interface may be extended to support these new indications. 3. Source gNB or source ng-eNB indicates the selected AEAD algorithm and / or the selected AEAD option and / or the selected AEAD mode received in previous step from target gNB or target ng-eNB to the UE in handover command or RRC Connection Reconfiguration / RRC Reconfiguration message. 4.UE activates the selected AEAD algorithm and / or the selected AEAD option and / or the selected AEAD mode with target ng-eNB.

[0080] Mobility N2 HO - N14 interface and N2 interfaces

[0081] Embodiment 3 - Extend N14 (Forward relocation request / response) and N2 interfaces (Handover Required / Handover Command / Handover Request / Handover Request Acknowledge messages) N14 is the reference point between two AMFs.

[0082] This embodiment describes how to extend N14 interface (Forward Relocation Request / Response messages) and N2 interface (Handover Required / Handover Command messages and Handover Request / Handover Request Acknowledge messages) when handover is initiated by source gNB or source ng-eNB to a target gNB or a target ng-eNB via source AMF and via target AMF, as described in steps 2-7 in FIG. 10. Forward Relocation Request and Forward Relocation Response messages are specified in TS 38.413. Handover Required and Handover Command messages are specified in TS 38.413. Handover Request and Handover Request Acknowledge messages are specified in TS 38.423. Hand over command (HO Command) or RRC Connection Reconfiguration message or RRC Reconfiguration message is specified in TS 38.331.1. Source ng-eNB / gNB initiates Handover Required message with source AMF over N2interface. 2. Source AMF initiates Forward Relocation Request message with target AMF and includes the UE supported AEAD algorithms and / or UE supported AEAD options and / or UE supported AEAD modes in Forward Relocation Request message, if stored in source AMF, to the target AMF. 3. Target AMF initiates Handover Request message to Target gNB or Target ng-eNB and includes the UE supported AEAD algorithms and / or UE supported AEAD options and / or UE supported AEAD modes received in Forward Relocation Request message, into the Handover Request message, to the Target gNB or Target ng-eNB. 4. Target gNB or Target ng-eNB selects the AEAD algorithm and / or AEAD options and / or AEAD mode and indicates to the UE the selected AEAD algorithm and / or selected AEAD options and / or selected AEAD mode in the Handover Request Acknowledge message. 5. Target AMF forwards the selected AEAD algorithm and / or selected AEAD options and / or selected AEAD mode received in previous step from target gNB or target ng-eNB to the source AMF in Forward Relocation Response message. 6. Source AMF forwards the selected AEAD algorithm and / or selected AEAD options and / or selected AEAD mode received in previous step from target AMF to the source gNB or source ng-eNB in Handover Command message. 7. Source gNB or source ng- eNB forwards the selected AEAD algorithm and / or selected AEAD options and / or selected AEAD mode received in previous step from source AMF to the UE. 8. UE activates the selected AEAD algorithm and / or the selected AEAD options and / or selected AEAD mode with the target gNB or target ng-eNB.

[0083] Mobility registration update - N14 interface

[0084] Embodiment 4 - Extend N14 interface (Context retrieval request / response)

[0085] N14 is the reference point between two AMFs.

[0086] This embodiment describes how to extend N14 interface (Context retrieval request / response messages) with new code points for UE supported AEAD algorithms and / or UE supported AEAD options and / or UE supported AEAD modes, at mobility registration from source AMF to target AMF as described in steps 2 and 3 in FIG. 11.

[0087] 1. UE registers to the 5G network and includes UE supported AEAD algorithms, and / or UE supported AEAD options and / or UE supported AEAD modes into Registration Request message. 2. Target AMF contacts Source AMF including the complete Registration Request. 3. The Source AMF provides the UE supported AEAD algorithms, and / or UE supported AEAD options and / or UE supported AEAD modes, if stored, and if Registration Request is successfully authenticated, to the Target AMF. 4. The Target AMF initiates NAS Security Mode Command with UE including the replayed UE supported AEAD algorithms, and / or replayed UE supported AEAD options and / or replayed UE supported AEAD modes. Ifcomplete Registration Request was not successfully integrity protected then AMF requests UE to resend Registration Request including UE supported AEAD algorithms, and / or UE supported AEAD options and / or UE supported AEAD modes.

[0088] Dual connectivity

[0089] Embodiment 5 - Extend Xn interface (SN Addition Request / Response messages)

[0090] This embodiment describes how to extend Xn interface (SN Addition Request / Response messages) with new code points for UE supported AEAD algorithms and / or UE supported AEAD options and / or UE supported AEAD modes, at Dual Connectivity as described in steps 2- 4 in FIG. 12. SN Addition Request (S-NODE addition Request) and SN Addition Response (S- NODE addition Response) messages are specified in TS 38.423.

[0091] 1. If MN receives UE supported AEAD algorithms, and / or UE supported AEAD options and / or UE supported AEAD modes, then the MN shall indicate to SN the supported AEAD algorithms, and / or UE supported AEAD options and / or UE supported AEAD modes. 2.Master Node (MN) in Dual Connectivity (i.e. a gNB or a ng-eNB), initiates SN Addition / Modification procedure with Secondary Node (SN) (i.e. a gNB or a ng-eNB) and includes UE supported AEAD algorithms, and / or UE supported AEAD options and / or UE supported AEAD modes to the SN. 3. SN selects an AEAD algorithm, AEAD options and an AEAD mode among the UE supported AEAD algorithms, UE supported AEAD options and UE supported AEAD modes and the SN decides to activate the AEAD algorithm, AEAD options and AEAD mode with the UE. SN sends SN Addition / Modification Response including the selected AEAD algorithm, selected AEAD options and the selected AEAD mode to the MN, to indicate to UE to activate the AEAD algorithm in the selected AEAD mode with selected AEAD options. 4. Master Node (SN) in Dual Connectivity (LTE eNB) initiates RRC Reconfiguration procedure with UE and forwards the selected AEAD algorithm, selected AEAD options and the selected AEAD mode to the UE. 5. UE activates the indicated AEAD algorithm, selected AEAD options, and indicated AEAD mode with the SN.

[0092] FIG. 13 shows an example of a communication system 1300 in accordance with some embodiments.

[0093] In the example, the communication system 1300 includes a telecommunication network 1302 that includes an access network 1304, such as a Radio Access Network (RAN), and a core network 1306, which includes one or more core network nodes 1308. The access network 1304 includes one or more access network nodes, such as network nodes 1310A and 1310B (one or more of which may be generally referred to as network nodes 1310), 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 1302 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 1302 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 1302, including one or more network nodes 1310 and / or core network nodes 1308.

[0094] Examples of an ORAN network node include an Open Radio Unit (O-RU), an Open Distributed Unit (O-DU), an Open Central Unit (O-CU), including an O-CU Control Plane (O- CU-CP) or an O-CU User Plane (O-CU-UP), a RAN intelligent controller (near-real time or non- real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, 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 O-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes 1310 facilitate direct or indirect connection of User Equipment (UE), such as by connecting UEs 1312A, 1312B, 1312C, and 1312D (one or more of which may be generally referred to as UEs 1312) to the core network 1306 over one or more wireless connections.

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

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

[0097] In the depicted example, the core network 1306 connects the network nodes 1310 to one or more hosts, such as host 1316. 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 1306 includes one more core network nodes (e.g., core network node 1308) 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 1308. 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 (SIDE), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0098] The host 1316 may be under the ownership or control of a service provider other than an operator or provider of the access network 1304 and / or the telecommunication network 1302, and may be operated by the service provider or on behalf of the service provider. The host 1316 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0099] As a whole, the communication system 1300 of FIG. 13 enables connectivity between theUEs, network nodes, and hosts. In that sense, the communication system 1300 may be configured to operate according to predefined rules or procedures, such as specific standards thatinclude, 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.

[0100] In some examples, the telecommunication network 1302 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunication network 1302 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1302. For example, the telecommunication network 1302 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.

[0101] In some examples, the UEs 1312 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 1304 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1304. 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).

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

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

[0104] FIG. 14 shows a UE 1400 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, 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, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3GPP, including a Narrowband Internet of Things (NB-IoT) UE, a Machine Type Communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0105] A UE may support Device-to-Device (D2D) communication, for example byimplementing 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).

[0106] The UE 1400 includes processing circuitry 1402 that is operatively coupled via a bus 1404 to an input / output interface 1406, a power source 1408, memory 1410, a communication interface 1412, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIG. 14. 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.

[0107] The processing circuitry 1402 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 1410. The processing circuitry 1402 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 1402 may include multiple Central Processing Units (CPUs).

[0108] In the example, the input / output interface 1406 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 1400. 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 sensormay 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.

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

[0110] The memory 1410 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 1410 includes one or more application programs 1414, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1416. The memory 1410 may store, for use by the UE 1400, any of a variety of various operating systems or combinations of operating systems.

[0111] The memory 1410 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 (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as a ‘SIM card.’ The memory 1410 may allow the UE 1400 to access instructions, application programs, and the like stored on transitoryor 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 1410, which may be or comprise a device-readable storage medium.

[0112] The processing circuitry 1402 may be configured to communicate with an access network or other network using the communication interface 1412. The communication interface 1412 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1422. The communication interface 1412 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 1418 and / or a receiver 1420 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1418 and receiver 1420 may be coupled to one or more antennas (e.g., the antenna 1422) and may share circuit components, software, or firmware, or alternatively be implemented separately.

[0113] In the illustrated embodiment, communication functions of the communication interface 1412 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 / Internet 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.

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

[0115] As another example, a UE comprises an actuator, a motor, or a switch related to acommunication 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.

[0116] 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 item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 1400 shown in FIG. 14.

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

[0118] 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 thedrone’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.

[0119] FIG. 15 shows a network node 1500 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, 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).

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

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

[0122] The network node 1500 includes processing circuitry 1502, memory 1504, a communication interface 1506, and a power source 1508. The network node 1500 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 1500 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 multipleNodeBs. 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 1500 may be configured to support multiple RATs. In such embodiments, some components may be duplicated (e.g., separate memory 1504 for different RATs) and some components may be reused (e.g., a same antenna 1510 may be shared by different RATs). The network node 1500 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1500, 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 1500.

[0123] The processing circuitry 1502 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 1500 components, such as the memory 1504, to provide network node 1500 functionality.

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

[0125] The memory 1504 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 1502. The memory 1504 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 1502 and utilized by the network node 1500. The memory 1504 may be used to store any calculations made by the processing circuitry 1502 and / or any data received via the communication interface 1506. In some embodiments, the processingcircuitry 1502 and the memory 1504 are integrated.

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

[0127] In certain alternative embodiments, the network node 1500 does not include separate radio front-end circuitry 1518; instead, the processing circuitry 1502 includes radio front-end circuitry and is connected to the antenna 1510. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1512 is part of the communication interface 1506. In still other embodiments, the communication interface 1506 includes the one or more ports or terminals 1516, the radio front-end circuitry 1518, and the RF transceiver circuitry 1512 as part of a radio unit (not shown), and the communication interface 1506 communicates with the baseband processing circuitry 1514, which is part of a digital unit (not shown).

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

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

[0130] The power source 1508 provides power to the various components of the network node 1500 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1508 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1500 with power for performing the functionality described herein. For example, the network node 1500 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 1508. As a further example, the power source 1508 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.

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

[0132] FIG. 16 is a block diagram of a host 1600, which may be an embodiment of the host 1316 of FIG. 13, in accordance with various aspects described herein. As used herein, the host 1600 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 1600 may provide one or more services to one or more UEs.

[0133] The host 1600 includes processing circuitry 1602 that is operatively coupled via a bus 1604 to an input / output interface 1606, a network interface 1608, a power source 1610, and memory 1612. 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 FIG.s 14 and 15, such that the descriptions thereof are generallyapplicable to the corresponding components of the host 1600.

[0134] The memory 1612 may include one or more computer programs including one or more host application programs 1614 and data 1616, which may include user data, e.g. data generated by a UE for the host 1600 or data generated by the host 1600 for a UE. Embodiments of the host 1600 may utilize only a subset or all of the components shown. The host application programs 1614 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), Moving Picture Experts Group (MPEG), VP9) and audio codecs (e.g., Free Lossless Audio Codec (FLAC), 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 1614 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 1600 may select and / or indicate a different host for Over-The-Top (OTT) services for a UE. The host application programs 1614 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.

[0135] FIG. 17 is a block diagram illustrating a virtualization environment 1700 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 1700 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 1700 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.

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

[0137] Hardware 1704 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 1706 (also referred to as hypervisors or VM Monitors (VMMs)), provide VMs 1708A and 1708B (one or more of which may be generally referred to as VMs 1708), and / or perform any of the functions, features, and / or benefits described in relation with some embodiments described herein. The virtualization layer 1706 may present a virtual operating platform that appears like networking hardware to the VMs 1708.

[0138] The VMs 1708 comprise virtual processing, virtual memory, virtual networking, or interface and virtual storage, and may be run by a corresponding virtualization layer 1706. Different embodiments of the instance of a virtual appliance 1702 may be implemented on one or more of the VMs 1708, 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.

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

[0140] The hardware 1704 may be implemented in a standalone network node with generic or specific components. The hardware 1704 may implement some functions via virtualization. Alternatively, the hardware 1704 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 1710, which, among others, oversees lifecycle management of the applications 1702. In some embodiments, the hardware 1704 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupledto 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 1712 which may alternatively be used for communication between hardware nodes and radio units.

[0141] FIG. 18 shows a communication diagram of a host 1802 communicating via a network node 1804 with a UE 1806 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as the UE 1312A of FIG. 13 and / or the UE 1400 of FIG. 14), the network node (such as the network node 1310A of FIG. 13 and / or the network node 1500 of FIG. 15), and the host (such as the host 1316 of FIG. 13 and / or the host 1600 of FIG. 16) discussed in the preceding paragraphs will now be described with reference to FIG. 18.

[0142] Like the host 1600, embodiments of the host 1802 include hardware, such as a communication interface, processing circuitry, and memory. The host 1802 also includes software, which is stored in or is accessible by the host 1802 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 1806 connecting via an OTT connection 1850 extending between the UE 1806 and the host 1802. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 1850.

[0143] The network node 1804 includes hardware enabling it to communicate with the host 1802 and the UE 1806. The connection 1860 may be direct or pass through a core network (like the core network 1306 of FIG. 13) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

[0144] The UE 1806 includes hardware and software, which is stored in or accessible by the UE 1806 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via the UE 1806 with the support of the host 1802. In the host 1802, an executing host application may communicate with the executing client application via the OTT connection 1850 terminating at the UE 1806 and the host 1802. In providing the service to the 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 1850 may transfer both the request data and the user data. The UE’s client application may interact with the user to generate the user data that it provides to the host application through the OTT connection1850.

[0145] The OTT connection 1850 may extend via the connection 1860 between the host 1802 and the network node 1804 and via a wireless connection 1870 between the network node 1804 and the UE 1806 to provide the connection between the host 1802 and the UE 1806. The connection 1860 and the wireless connection 1870, over which the OTT connection 1850 may be provided, have been drawn abstractly to illustrate the communication between the host 1802 and the UE 1806 via the network node 1804, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0146] As an example of transmitting data via the OTT connection 1850, in step 1808, the host 1802 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 1806. In other embodiments, the user data is associated with a UE 1806 that shares data with the host 1802 without explicit human interaction. In step 1810, the host 1802 initiates a transmission carrying the user data towards the UE 1806. The host 1802 may initiate the transmission responsive to a request transmitted by the UE 1806. The request may be caused by human interaction with the UE 1806 or by operation of the client application executing on the UE 1806. The transmission may pass via the network node 1804 in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1812, the network node 1804 transmits to the UE 1806 the user data that was carried in the transmission that the host 1802 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1814, the UE 1806 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1806 associated with the host application executed by the host 1802.

[0147] In some examples, the UE 1806 executes a client application which provides user data to the host 1802. The user data may be provided in reaction or response to the data received from the host 1802. Accordingly, in step 1816, the UE 1806 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE 1806. Regardless of the specific manner in which the user data was provided, the UE 1806 initiates, in step 1818, transmission of the user data towards the host 1802 via the network node 1804. In step 1820, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 1804 receives user data from the UE 1806 and initiates transmission of the received user data towards the host 1802. In step 1822, the host 1802 receives the user data carried in the transmission initiated by the UE 1806.

[0148] One or more of the various embodiments improve the performance of OTT services provided to the UE 1806 using the OTT connection 1850, in which the wireless connection 1870 forms the last segment. More precisely, the teachings of these embodiments may improve the e.g., data rate, latency, power consumption, etc. and thereby provide benefits such as e.g., reduced user waiting time, relaxed restriction on file size, improved content resolution, better responsiveness, extended battery lifetime, etc.

[0149] In an example scenario, factory status information may be collected and analyzed by the host 1802. As another example, the host 1802 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 1802 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 1802 may store surveillance video uploaded by a UE. As another example, the host 1802 may store or control access to media content such as video, audio, VR, or AR which it can broadcast, multicast, or unicast to UEs. As other examples, the host 1802 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing, and / or transmitting data.

[0150] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency, and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 1850 between the host 1802 and the UE 1806 in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection 1850 may be implemented in software and hardware of the host 1802 and / or the UE 1806. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1850 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or by supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 1850 may include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not directly alter the operation of the network node 1804. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency, and the like by the host 1802. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1850 whilemonitoring propagation times, errors, etc.

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

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

[0153] 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

CLAIMS:

1. A method performed by a User Equipment (UE) comprising: sending a registration request to a target core network node, the registration request comprising at least one of UE support for one or more Authenticated Encryption with Associated Data (AEAD) algorithms, one or more UE supported AEAD options, and one or more UE supported AEAD modes; determining at least one of a network selected AEAD algorithm, a network selected AEAD option, and a network selected AEAD mode.

2. The method of claim 1, wherein signaling comprises: signaling the UE capabilities in a Registration Request message to an Access & Mobility Management Function, AMF, node.

3. The method of claim 1, wherein signaling and / or determining comprises one or more of: Initial Context Setup procedure; Xn handover; N2 handover; mobility registration; and dual connectivity.

4. The method of claim 1 , wherein determining the at least one of a network selected AEAD algorithm, a network selected AEAD option, and a network selected AEAD mode comprises receiving an AS Security Mode Command from a gNB or a ng-eNB.

5. The method of claim 1, wherein determining the at least one of a network selected AEAD algorithm, a network selected AEAD option, and a network selected AEAD mode comprises receiving an Non Access Stratum, NAS, Security Mode Command from a target AMF.

6. The method of claim 1, wherein determining the at least one of: a network selected AEAD algorithm; a network selected AEAD option; and a network selected AEAD mode comprises: receiving a Handover Command from a source gNB or a source ng-eNB.

7. The method of claim 1, wherein determining the at least one of: a network selected AEAD algorithm; a network selected AEAD option; and a network selected AEAD mode comprises: receiving a Radio Resource Control, RRC, Reconfiguration Request from a Master Node in Dual Connectivity.

8. A method performed by a network node, comprising:determining UE capabilities as at least one of UE support of AEAD algorithms, UE support of AEAD options, and UE support of AEAD modes; and signaling at least one of a network selected AEAD algorithm, a network selected AEAD option, and a network selected AEAD mode.

9. The method of claim 8, wherein the network node is an Access & Mobility Management Function, AMF, node; and the determining comprises receiving the UE capabilities in a Registration Request message.

10. The method of claim 8, wherein signaling and / or determining comprises one or more of: Initial Context Setup procedure; Xn handover; N2 handover; mobility registration; and dual connectivity.

11. The method of claim 8, wherein the network node comprises a gNB or a ng-eNB; and signaling the at least one of: a network selected AEAD algorithm; a network selected AEAD option; and a network selected AEAD mode comprises: signaling an AS Security Mode Command.

12. The method of claim 8, wherein the network node comprises a target AMF; and signaling the at least one of: a network selected AEAD algorithm; a network selected AEAD option; and a network selected AEAD mode comprises: signaling an NAS Security Mode Command.

13. The method of claim 8, wherein the network node comprises a source gNB or a source ng- eNB; and signaling the at least one of: a network selected AEAD algorithm; a network selected AEAD option; and a network selected AEAD mode comprises: signaling a Handover Command.

14. The method of claim 8, wherein the network node comprises a Master Node in Dual Connectivity; and signaling the at least one of: a network selected AEAD algorithm; a network selected AEAD option; and a network selected AEAD mode comprises: signaling a RRC Reconfiguration Request.

Images