Integrity protection in a communication network

Abstract

Embodiments provide a procedure between nodes in a home network for generating appropriate integrity check data in a container information element (IE) which accounts for which data in the container IE is to be integrity protected. More particularly, embodiments herein include a method performed by a communication device. The method comprises receiving, from a home network of the communication device, a container information element that includes header data, device configuration data, and integrity check data. In some embodiments, the container information element indicates which data in the container information element is included in integrity protected data that is integrity protected by the integrity check data. The method also comprises using the integrity check data to check an integrity of the integrity protected data indicated by the container information element.

Description

[0001] INTEGRITY PROTECTION IN A COMMUNICATION NETWORK

[0002] TECHNICAL FIELD

[0003] The present application relates generally to the field of wireless communication networks, and more specifically to techniques for integrity protection in a communication network. BACKGROUND

[0004] A communication device subscribes to receive communication service from a communication network referred to as the device’s home network. The home network stores data related to provision of communication service to the communication device. For example, in some types of communication systems, the home network stores routing indicator data and / or default configured network slice selection assistance information (NSSAI). In this context, the home network may trigger a parameter update procedure to update the communication device with that data, e.g., as the data dynamically change over time. See, e.g., the User Equipment (UE) Parameter Update (UPU) procedure specified in 3rdGeneration Partnership Project (3GPP) Technical Specification (TS) 23.502 v18.2.0.

[0005] In these and other cases where the home network updates the communication device with device configuration data, the home network heretofore integrity protects the device configuration data before transmitting it to the communication device. This safeguards the device configuration data against tampering by a man-in-the-middle attack.

[0006] This legacy operation can be enhanced by introducing device acknowledgement of the device configuration data. With this enhancement, the home network can request the communication device to send an acknowledgement back to the home network, acknowledging receipt of the device configuration data. The home network may do so by encapsulating the device configuration data into a container information element (IE) and including its request for acknowledgement within header data of the container IE. In circumstances such as these where header data accompanies the device configuration data, integrity protecting also the header data would safeguard the header data from tampering as well. Challenges exist for realizing header data integrity protection though in a way that accommodates backwards compatibility with legacy communication devices and network nodes that are not configured for header data integrity protection.

[0007] SUMMARY

[0008] According to some embodiments herein, a container information element (IE) that includes device configuration data for a communication device indicates which data in the container IE is integrity protected. The container IE may for example indicate whether header data in the container IE is integrity protected, e.g., in addition to the device configuration data. Equipped with knowledge of which data is integrity protected, the communication device may correspondingly check the integrity of that data, e.g., by calculating a message authentication code (MAC) as a function of that data.

[0009] Some embodiments herein advantageously facilitate integrity protection of header data in a way that accommodates backwards compatibility with legacy communication devices and network nodes that are not configured for header data integrity protection. For example, if a legacy network node in the home network is not configured to integrity protect the header data, the container IE will not indicate the header data is integrity protected, so a communication device can fall back to checking the integrity of only the device configuration data, even though the communication device itself may support header data integrity protection. Finally, if both the communication device and the home network support header data integrity protection, the communication device may check the integrity of both the device configuration data and the header data, based on the container IE indicating that both the device configuration data and the header data are integrity protected.

[0010] Some embodiments herein also provide a procedure between nodes in the home network for generating appropriate integrity check data in the container IE which accounts for which data in the container IE is to be integrity protected.

[0011] More particularly, embodiments herein include a method performed by a communication device. The method comprises receiving, from a home network of the communication device, a container information element that includes header data, device configuration data, and integrity check data. In some embodiments, the container information element indicates which data in the container information element is included in integrity protected data that is integrity protected by the integrity check data. The method also comprises using the integrity check data to check an integrity of the integrity protected data indicated by the container information element.

[0012] In some embodiments, the header data in the container information element indicates which data in the container information element is included in integrity protected data that is integrity protected by the integrity check data.

[0013] In some embodiments, the container information element indicates which data in the container information element is included in integrity protected data by indicating whether the header data is included in integrity protected data.

[0014] In some embodiments, the integrity protected data includes at least the device configuration data, and the container information element indicates which data in the container information element is included in integrity protected data by indicating whether the integrity protected data also includes the header data.

[0015] In some embodiments, the container information element includes an indicator that indicates whether the integrity protected data includes the header data. In some embodiments, a first possible value of the indicator indicates that the integrity protected data includes the header data and a second possible value of the indicator indicates that the integrity protected data does not include the header data. In some embodiments, the indicator explicitly indicates whether the integrity protected data includes the header data. In some embodiments, the indicator implicitly indicates whether the integrity protected data includes the header data by indicating whether the home network is capable of integrity protecting the header data. In some embodiments, the indicator is included in the header data.

[0016] In some embodiments, the container information element is configurable to include an indicator which indicates that the integrity protected data includes the header data. In some embodiments, inclusion of the indicator in the container information element indicates that the integrity protected data includes the header data and exclusion of the indicator from the container information element indicates that the integrity protected data does not include the header data. In some embodiments, the indicator explicitly indicates that integrity protected data includes the header data. In some embodiments, the indicator implicitly indicates that the integrity protected data includes the header data by indicating that the home network is capable of integrity protecting the header data. In some embodiments, the container information element is configurable to include the indicator in the header data.

[0017] In some embodiments, the container information element indicates which data in the container information element is integrity protected data by indicating a type or version of integrity protection applied to the container information element. In some embodiments, different types or versions of integrity protection integrity protect at least some different data in the container information element. In some embodiments, a first type or version of integrity protection integrity protects the device configuration data but not the header data, and a second type or version of integrity protection integrity protects both the device configuration data and the header data.

[0018] In some embodiments, using the integrity check data comprises generating integrity check match data as a function of the integrity protected data indicated by the container information element. In some embodiments, using the integrity check data comprises performing a comparison of the integrity check match data to the integrity check data included in the container information element. In some embodiments, using the integrity check data comprises determining whether or not the integrity of the integrity protected data is intact based on the comparison. In some embodiments, the integrity protected data includes at least the device configuration data, and generating integrity check match data as a function of the integrity protected data comprises, based on the container information element indicating that the header data is integrity protected data, generating the integrity check match data as a function of the device configuration data and the header data. In some embodiments, the integrity protected data includes at least the device configuration data. In some embodiments, generating integrity check match data as a function of the integrity protected data comprises, if the container information element indicates that the integrity protected data includes the header data, generating the integrity check match data as a function of the device configuration data and the header data. In other embodiments, generating integrity check match data as a function of the integrity protected data comprises, if the container information element indicates that the integrity protected data does not include the header data, generating the integrity check match data as a function of the device configuration data but not as a function of the header data.

[0019] In some embodiments, the integrity check match data is a message authentication code, MAC.

[0020] In some embodiments, the device configuration data includes steering of roaming information. In some embodiments, the steering of roaming information comprises information for encouraging the communication device to roam to a preferred roamed-to-network indicated by the home network.

[0021] In some embodiments, the device configuration data includes a set of one or more device parameters. In some embodiments, the set of one or more device parameters includes a parameter that indicates default configured network slice selection assistance information, NSSAI. In other embodiments, the set of one or more device parameters alternatively or additionally includes a parameter that indicates routing indicator data.

[0022] In some embodiments, the device configuration data includes User Equipment, UE, Parameter Update, UPU, data.

[0023] In some embodiments, said receiving comprises receiving the container information element from a first core network node in the home network. In some embodiments, said receiving comprises receiving the container information element via a second core network node in a serving network of the communication device, by receiving a downlink control plane message from the first core network node. In some embodiments, the downlink control plane message includes the container information element. In some embodiments, the downlink control plane message is a downlink non-access stratum transport message. In some embodiments, the second core network node implements an access and mobility function, AMF.

[0024] In some embodiments, the method further comprises providing user data, and forwarding the user data to a host computer via the transmission to a base station.

[0025] Other embodiments herein include a method performed by a network node in a home network of a communication device. The method comprises generating a container information element to include header data, device configuration data, and integrity check data, and to indicate which data in the container information element is included in integrity protected data that is integrity protected by the integrity check data. The method also comprises transmitting the container information element to the communication device.

[0026] In some embodiments, the header data in the container information element indicates which data in the container information element is included in integrity protected data that is integrity protected by the integrity check data.

[0027] In some embodiments, the container information element indicates which data in the container information element is included in integrity protected data by indicating whether the header data is integrity protected data.

[0028] In some embodiments, the integrity protected data includes at least the device configuration data, and the container information element indicates which data in the container information element is included in integrity protected data by indicating whether the integrity protected data also includes the header data.

[0029] In some embodiments, the container information element includes an indicator that indicates whether the integrity protected data includes the header data, the container information element includes an indicator that indicates whether the integrity protected data includes the header data. In some embodiments, a first possible value of the indicator indicates that the integrity protected data includes the header data and a second possible value of the indicator indicates that the integrity protected data does not include the header data. In some embodiments, wherein the indicator explicitly indicates whether the integrity protected data includes the header data. In some embodiments, the indicator implicitly indicates whether the integrity protected data includes the header data by indicating whether the home network is capable of integrity protecting the header data. In some embodiments, the indicator is included in the header data.

[0030] In some embodiments, the container information element is configurable to include an indicator which indicates that the integrity protected data includes the header data. In some embodiments, inclusion of the indicator in the container information element indicates that the integrity protected data includes the header data and exclusion of the indicator from the container information element indicates that the integrity protected data does not include the header data. In some embodiments, the indicator explicitly indicates that integrity protected data includes the header data. In some embodiments, the indicator implicitly indicates that the integrity protected data includes the header data by indicating that the home network is capable of integrity protecting the header data. In some embodiments, the container information element is configurable to include the indicator in the header data.

[0031] In some embodiments, the container information element indicates which data in the container information element is integrity protected data by indicating a type or version of integrity protection applied to the container information element. In some embodiments, different types or versions of integrity protection integrity protect at least some different data in the container information element. In some embodiments, a first type or version of integrity protection integrity protects the device configuration data but not the header data, and a second type or version of integrity protection integrity protects both the device configuration data and the header data. In some embodiments, the device configuration data includes steering of roaming information. In some embodiments, the steering of roaming information comprises information for encouraging the communication device to roam to a preferred roamed-to-network indicated by the home network.

[0032] In some embodiments, the device configuration data includes a set of one or more device parameters. In some embodiments, the device configuration data includes a set of one or more device parameters. In some embodiments, the set of one or more device parameters includes a parameter that indicates default configured network slice selection assistance information, NSSAI. In other embodiments, the set of one or more device parameters alternatively or additionally includes a parameter that indicates routing indicator data.

[0033] In some embodiments, the device configuration data includes User Equipment, UE, Parameter Update, UPU, data.

[0034] In some embodiments, the network node is a first core network node in the home network. In some embodiments, the first core network node implements a unified data management, UDM, function.

[0035] In some embodiments, said transmitting comprises transmitting the container information element via a second core network node in a serving network of the communication device, by transmitting a downlink control plane message to the communication device. In some embodiments, the downlink control plane message includes the container information element. In some embodiments, the downlink control plane message is a downlink non-access stratum transport message. In some embodiments, the second core network node implements an access and mobility function, AMF.

[0036] In some embodiments, the method further comprises transmitting, to another network node in the home network, a request for the another network node to integrity protect the integrity protected data by generating the integrity check data, wherein the request includes the integrity protected data. In some embodiments, the method further comprises receiving the integrity check data from the another network node in response to the request. In some embodiments, the method further comprises making a decision about which data in the container information element to integrity protect as integrity protected data. In some embodiments, the method further comprises generating the request to include the integrity protected data according to the decision. In some embodiments, the decision is made to integrity protect data that includes the header data if both the communication device and the home network have capability to handle the header data being integrity protected. In some embodiments, the method further comprises receiving capability signaling from the communication device indicating whether the communication device has the capability to handle the header data being integrity protected. In some embodiments, the request explicitly indicates that the header data is to be integrity protected in addition to the device configuration data. In some embodiments, the another network node is an authentication server.

[0037] In some embodiments, the method further comprises generating the header data to indicates which data in the container information element is integrity protected data that is integrity protected by the integrity check data.

[0038] Other embodiments herein include a method performed by a network node in a home network of a communication device. The method comprises transmitting, to an authentication server in the home network, a request for the authentication server to generate integrity check data that integrity protects integrity protected data comprising both device configuration data and header data to be included in a container information element. In some embodiments, the request includes the integrity protected data. The method also comprises receiving the integrity check data in response to the request.

[0039] In some embodiments, the header data indicates which data in the container information element is integrity protected data that is integrity protected by the integrity check data.

[0040] In some embodiments, the container information element indicates which data in the container information element is integrity protected data by indicating whether the header data is integrity protected data.

[0041] In some embodiments, the container information element indicates which data in the container information element is integrity protected data by indicating whether the integrity protected data also includes the header data.

[0042] In some embodiments, the container information element includes an indicator that indicates whether the header data is integrity protected data. In some embodiments, a first possible value of the indicator indicates that the header data is integrity protected data and a second possible value of the indicator indicates that the header data is not integrity protected data. In some embodiments, the indicator explicitly indicates whether the header data is integrity protected data. In some embodiments, the indicator implicitly indicates whether the header data is integrity protected data by indicating whether the home network is capable of integrity protecting the header data. In some embodiments, the indicator is included in the header data.

[0043] In some embodiments, the container information element is configurable to include an indicator which indicates that the header data is integrity protected data. In some embodiments, inclusion of the indicator in the container information element indicates that the header data is integrity protected data and exclusion of the indicator from the container information element indicates that the header data is not integrity protected data. In some embodiments, the indicator explicitly indicates that the header data is integrity protected data. In some embodiments, the indicator implicitly indicates that the header data is integrity protected data by indicating that the home network is capable of integrity protecting the header data. In some embodiments, the container information element is configurable to include the indicator in the header data.

[0044] In some embodiments, the container information element indicates which data in the container information element is integrity protected data by indicating a type or version of integrity protection applied to the container information element. In some embodiments, different types or versions of integrity protection integrity protect at least some different data in the container information element. In some embodiments, a first type or version of integrity protection integrity protects the device configuration data but not the header data, and wherein a second type or version of integrity protection integrity protects both the device configuration data and the header data.

[0045] In some embodiments, the device configuration data includes steering of roaming information. In some embodiments, the steering of roaming information comprises information for encouraging the communication device to roam to a preferred roamed-to-network indicated by the home network.

[0046] In some embodiments, the device configuration data includes a set of one or more device parameters. In some embodiments, the set of one or more device parameters includes a parameter that indicates default configured network slice selection assistance information, NSSAI. In other embodiments, the set of one or more device parameters alternatively or additionally includes a parameter that indicates routing indicator data.

[0047] In some embodiments, the device configuration data includes User Equipment, UE, Parameter Update, UPU, data.

[0048] In some embodiments, the network node is a first core network node in the home network. In some embodiments, the first core network node implements a unified data management, UDM, function.

[0049] In some embodiments, the request explicitly indicates that the header data is to be integrity protected in addition to the device configuration data.

[0050] In some embodiments, the method further includes obtaining user data, and forwarding the user data to a host computer or a communication device.

[0051] Other embodiments herein include a method performed by an authentication server in a home network of a communication device. The method comprises receiving, from a network node in the home network, a request for the authentication server to generate integrity check data that integrity protects integrity protected data comprising both device configuration data and header data to be included in a container information element. In some embodiments, the request includes the integrity protected data. The method also comprises generating the integrity check data according to the request. The method also comprises transmitting the integrity check data to the network node in response to the request.

[0052] In some embodiments, the header data indicates which data in the container information element is integrity protected data that is integrity protected by the integrity check data. In some embodiments, the container information element indicates which data in the container information element is integrity protected data by indicating whether the header data is integrity protected data.

[0053] In some embodiments, the container information element indicates which data in the container information element is integrity protected data by indicating whether the integrity protected data also includes the header data.

[0054] In some embodiments, the container information element includes an indicator that indicates whether the header data is integrity protected data. In some embodiments, a first possible value of the indicator indicates that the header data is integrity protected data and a second possible value of the indicator indicates that the header data is not integrity protected data. In some embodiments, the indicator explicitly indicates whether the header data is integrity protected data. In some embodiments, the indicator implicitly indicates whether the header data is integrity protected data by indicating whether the home network is capable of integrity protecting the header data. In some embodiments, the indicator is included in the header data.

[0055] In some embodiments, the container information element is configurable to include an indicator which indicates that the header data is integrity protected data. In some embodiments, inclusion of the indicator in the container information element indicates that the header data is integrity protected data and exclusion of the indicator from the container information element indicates that the header data is not integrity protected data. In some embodiments, the indicator explicitly indicates that the header data is integrity protected data. In some embodiments, the indicator implicitly indicates that the header data is integrity protected data by indicating that the home network is capable of integrity protecting the header data. In some embodiments, the container information element is configurable to include the indicator in the header data.

[0056] In some embodiments, the container information element indicates which data in the container information element is integrity protected data by indicating a type or version of integrity protection applied to the container information element. In some embodiments, different types or versions of integrity protection integrity protect at least some different data in the container information element. In some embodiments, a first type or version of integrity protection integrity protects the device configuration data but not the header data, and a second type or version of integrity protection integrity protects both the device configuration data and the header data.

[0057] In some embodiments, the device configuration data includes steering of roaming information, wherein the steering of roaming information comprises information for encouraging the communication device to roam to a preferred roamed-to-network indicated by the home network. In some embodiments, the device configuration data includes a set of one or more device parameters. In some embodiments, the set of one or more device parameters includes a parameter that indicates default configured network slice selection assistance information, NSSAI. In other embodiments, the set of one or more device parameters alternatively or additionally includes a parameter that indicates routing indicator data.

[0058] In some embodiments, the device configuration data includes User Equipment, UE, Parameter Update, UPU, data.

[0059] In some embodiments, the network node is a first core network node in the home network. In some embodiments, the first core network node implements a unified data management, UDM, function.

[0060] In some embodiments, the request explicitly indicates that the header data is to be integrity protected in addition to the device configuration data.

[0061] Embodiments herein also include corresponding apparatus, computer programs, and carriers of those computer programs.

[0062] BRIEF DESCRIPTION OF THE DRAWINGS

[0063] Figure 1 shows an exemplary network architecture where the invention is realized.

[0064] Figure 2 shows a flow diagram for an exemplary method (e.g., procedure) performed by a communication device, according to various embodiments of the present disclosure.

[0065] Figure 3 shows a UPU procedure according to some embodiments.

[0066] Figure 4 shows one example of the enhanced UPU Header.

[0067] Figure 5 shows one example as a UE parameters update transparent container.

[0068] Figure 6 shows a UPU procedure according to some embodiments where a home network lacks the capability to integrity protect the UPU header.

[0069] Figure 7 shows a UPU procedure according to some embodiments where the UE lacks the capability to integrity protect the UPU header.

[0070] Figure 8 shows a flow diagram for an exemplary method (e.g., procedure) performed by the communication device.

[0071] Figure 9 shows a flow diagram for an exemplary method (e.g., procedure) performed by a network node.

[0072] Figure 10 shows a flow diagram for an exemplary method (e.g., procedure) performed by an authentication server.

[0073] Figure 11 shows the communication device as implemented in accordance with one or more embodiments.

[0074] Figure 12 shows the network node as implemented in accordance with one or more embodiments.

[0075] Figure 13 shows the authentication server as implemented in accordance with one or more embodiments. Figure 14 shows an example of a communication system in accordance with some embodiments.

[0076] Figure 15 shows the UE in accordance with some embodiments.

[0077] Figure 16 shows the network node in accordance with some embodiments.

[0078] Figure 17 shows a block diagram of a host in accordance with various embodiments.

[0079] Figure 18 shows a block diagram illustrating a virtualization environment in which functions implemented by some embodiments is virtualized.

[0080] DETAILED DESCRIPTION

[0081] Figure 1 shows a communication device 12 according to some embodiments. The communication device 12 has a home communication network 10H, also referred to simply as a home network 10H. The communication device 12 in this regard may have a subscription to receive communication service from the home network 10H. At any given time, though, the communication device 12 is served by a serving communication network 10S, also referred to simply as a serving network 10S. The serving network 10S may or may not be the same network as the home network 10H. The serving network 10S may for example be a visited communication network to which the communication device 12 has roamed under a roaming agreement between the home network 10H and the serving network 10S.

[0082] As shown, the communication device 12 receives device configuration data 14 from the home network 10H. The communication device 12 in particular receives the device configuration data 14 from a network node 16H in the home network 10H, e.g., from a core network node such as a node implementing a Unified Data Management (UDM) function.

[0083] In some embodiments, the device configuration data 14 includes a set of one or more device parameters, e.g., with which the communication device 12 is to be configured by the home network 10H. For example, the set of one or more device parameters may include a parameter that indicates default configured network slice selection assistance information (NSSAI) and / or a parameter that indicates routing indicator data. In one such embodiment, the device configuration data 14 includes User Equipment (UE) Parameter Update (UPU) data, e.g., as specified by 3rd Generation Partnership Project (3GPP) TS 23.502 V18.2.0 and 33.501 V18.2.0.

[0084] In other embodiments, the device configuration data 14 includes steering of roaming (SOR) information. SOR information in this regard comprises information for encouraging the communication device 12 to roam to a preferred roamed-to-network indicated by the home network 10H. The SOR information may for example comprise a list of preferred Public Land Mobile Network (PLMN) I access technology combinations that is preferred by the home network 10H.

[0085] Regardless of the particular type of the device configuration data 14, the home network 10H transmits the device configuration data 14 to the communication device 12 within a container information element (IE) 18. The container IE 18 may be referred to as a transparent container IE which is transparent in the sense that it is to be transparently forwarded to the communication device 12 by the serving network 10S, e.g., forwarded to the communication device 12 without modification and / or without inspection. For example, as shown, the container IE 18 is to be transparently forwarded to the communication device 12 by the serving network 10S, e.g., via a core network node such as a node implementing an Access and Mobility Function (AMF). In these and other embodiments, for instance, the device configuration data 14 may be communicated from the home network 10H to the communication device 12 via a Non- Access Stratum (NAS) transport procedure. In this case, the communication device 12 may receive the device configuration data 14 via the serving network 10S, by receiving the container IE 18 in a Payload container Information Element (IE) of a downlink NAS transport message.

[0086] The container IE 18 however also includes header data 20. The header data 20 is data in a header of the container IE 18 which encapsulates or supplements the device configuration data 14 as the payload. The header data 20 may for example include data which indicates whether or not the home network 10H requests acknowledgement of the device configuration data 14, and / or data which indicates whether the communication device 12 is to re-register after being configured with the device configuration data 14. Generally, though, the header data 20 may include instructions for how the communication device 12 is to behave during or after the procedure for configuring the communication device 12 with the device configuration data 14.

[0087] The container IE 18 further includes integrity check data 22. The integrity check data 22 integrity protects some data in the container IE 18, referred to as integrity protected data 24. The integrity check data 32 in this regard is usable by the communication device 12 to check the integrity of whatever data in the container IE 18 is integrity protected. The integrity check data 32 may for example be a message authentication code (MAC) computed over the integrity protected data 24 within the container IE 18, e.g., where a MAC may also be referred to as a message integrity code (MIC), message digest, checksum, error detection code, or hash. In some embodiments, the integrity check data 32 is computed based on a security key, e.g., KAUSF, generated during primary authentication of the communication device 12 to the home network 10H.

[0088] Notably, some embodiments herein provide in-band signaling that indicates which data in the container IE 18 is integrity protected. The container IE 18 itself thereby indicates which data in the container IE 18 forms the integrity protected data 24 that is integrity protected by the integrity check data 22. Figure 1 shows one example of this in-band signaling as being an integrity protected data indicator 26, e.g., included in the header data 20, indicating which data in the container IE 18 is included in the integrity protected data 24. Regardless, by indicating which data is integrity protected, the container IE 18 advantageously enables dynamic adaptation or flexible configuration of which data is integrity protected, e.g., on a container IE by container IE basis.

[0089] For example, the container IE 18 may enable dynamic adaptation or flexible configuration of whether the header data 20 (or at least a part thereof) is integrity protected. In this case, then, the container IE 18 indicates whether the integrity protected data 24 includes the header data 20. In embodiments where the integrity protected data 24 includes the device configuration data 14 always or by default, this amounts to the container IE 18 indicating whether the integrity protected data 24 also includes the header data 20. For example, the integrity protected data indicator 26 (e.g., in the header data 20) may indicate whether the integrity protected data 24 includes the header data 20.

[0090] As one example implementation which exploits such an integrity protected data indicator 26 in the container IE 18, a first possible value of the indicator 26 (e.g., 1) may indicate that the integrity protected data 24 includes the header data 20 and a second possible value of the indicator 26 (e.g., 0) indicates that the integrity protected data 24 does not include the header data 20.

[0091] As another example implementation, by contrast, the container IE 18 may be configurable to include an integrity protected data indicator 26 which indicates that the integrity protected data 24 includes the header data 20, and the indicator’s inclusion or exclusion signals whether the integrity protected data 24 includes the header data 20. In particular, inclusion of the integrity protected data indicator 26 in the container IE 18 indicates that the integrity protected data 24 includes the header data 20, whereas exclusion of the integrity protected data indicator 26 from the container IE 18 indicates that the integrity protected data 24 does not include the header data 20.

[0092] As yet another example implementation, the container IE 18 may indicate a type or version of integrity protection applied to the container IE 18, where different types or versions of integrity protection integrity protect at least some different data in the container IE 18. For instance, a first type or version of integrity protection integrity protects the device configuration data 14 but not the header data 20, whereas a second type or version of integrity protection integrity protects both the device configuration data 14 and the header data 20.

[0093] In any implementation, though, the container IE 18 (e.g., via the integrity protected data indicator 26) may in some embodiments explicitly indicate which data is included in the integrity protected data 24, e.g., by explicitly indicating whether the integrity protected data 24 includes the header data 20. Or, in other embodiments, the container IE 18 (e.g., via the integrity protected data indicator 26) implicitly indicates which data is included in the integrity protected data 24. The container IE 18 may for instance explicitly indicate that the home network 10H is capable of integrity protecting the header data 20, yet this explicitly signaled capability of the home network 10H implicitly indicates that the integrity protected data 24 in the container IE 18 includes the header data 20. In fact, in these embodiments, the container IE 18 may indicate whether the home network 10H is capable of integrity protecting the header data 20, as part of a capability exchange or negotiation with the communication device 12, e.g., the communication device 12 may likewise indicate to the home network 10H whether the communication device 12 is capable of handling header data integrity protection.

[0094] No matter the particular way that the container IE 18 indicates which data is integrity protected, the possibility to dynamically adapt or flexibly configure which data is integrity protected may advantageously accommodate different circumstances under which different data is integrity protected, such as the case may be for accommodating different communication device or home network capabilities or versions. For example, by indicating which data is integrity protected, the container IE 18 facilitates integrity protection of the header data 20 in a way that accommodates backwards compatibility with legacy communication devices and network nodes that are not configured for header data integrity protection.

[0095] More particularly in this regard, in some embodiments, if a legacy network node in the home network 10H is not configured to integrity protect the header data 20, any container IE 18 transmitted by that legacy network node will not indicate the header data 20 is integrity protected, e.g., the container IE will not include any integrity protected data indicator 26. In this case, then, even if the communication device 12 itself supports header data integrity protection, the communication device 12 will understand that the header data 20 in the container IE 18 received from this legacy network node is not integrity protected, so the communication device 12 will fall back to checking the integrity of only the device configuration data 14. Or, if both the communication device 12 and the home network 10H support header data integrity protection, the communication device 12 may check the integrity of both the device configuration data 14 and the header data 20, based on the container IE 18 indicating that both the device configuration data 14 and the header data 20 are integrity protected.

[0096] Embodiments herein thereby enable the communication device 12 to appropriately check the integrity of whatever data in the container IE 18 is actually integrity protected, in a way that accommodates whatever capability the home network 10 has in that regard. In fact, ambiguity that would otherwise occur regarding which data in the container IE 18 is integrity protected would jeopardize the accuracy of the communication device’s integrity check, because otherwise the communication device might compute its integrity check with the wrong data as input. Embodiments herein thereby facilitate integrity check accuracy even in a context where the data that is integrity protected may vary, e.g., depending on communication device or home network capabilities or versions.

[0097] Figure 2 illustrates additional details of how the communication device 12 performs its integrity check in dependence on which data the container IE 18 indicates is integrity protected. In this example, the integrity protected data 24 includes at least the device configuration data 14, e.g., according to legacy operation. If the integrity protected data 24 also includes the header data 20, the container IE 18 will indicate such, e.g., via integrity protected data indicator 26 in the header data 20.

[0098] In this context, Figure 2 shows that the communication device 12 determines whether the container IE 18 indicates the integrity protected data 24 includes the header data 20 (Block 100). If the integrity protected data 24 does not include the header data 20 (NO at Block 100), the communication device generates integrity check match data as a function of the device configuration data 14 (not as a function of the header data 20) (Block 120). Where the integrity check match data is a MAC, for instance, this may involve computing a MAC with the device configuration data 14 as input (not the header data 20). Otherwise, if the integrity protected data 24 does include the header data 20 (YES at Block 100), the communication device generates integrity check match data as a function of the device configuration data 14 and the header data 20, e.g., by computing a MAC with the device configuration data 14 and header data 20 as input (Block 110).

[0099] Either way, the communication device 12 thereafter performs a comparison of the integrity check match data to the integrity check data 22 included in the container IE 18 (Block 130). If the integrity check match data matches the integrity check data 22 (YES at Block 140), the communication device 12 deems the integrity protected data 24 as having its integrity intact (Block 150). But if the integrity check match data does not match the integrity check data 22 (NO at Block 140), the communication device 12 deems the integrity protected data 24 as having its integrity compromised (Block 160).

[0100] Note that, in some embodiments, the network node 16H which transmits the container IE 18 itself computes the integrity check data 22 included in the container IE 18. In other embodiments, though, such as where the network node 16H lacks the security key (e.g., KAUSF) for computing the integrity check data 22, the network node 16H may request another network node to compute the integrity check data 22.

[0101] As shown in Figure 1, for example, the network node 16H transmits a request 30 to an authentication server 32, requesting the authentication server 32 to integrity protect the integrity protected data 24 by generating the integrity check data 22. The network node 16H in this regard includes the integrity protected data 24 in the request 30, so that the authentication server 32 can generate the integrity check data 22 as a function of that integrity protected data 24.

[0102] The network node 16H may for example include in the request 30 whatever data is to be integrity protected, e.g., so as to exclude any data that is not to be integrity protected. In other embodiments, by contrast, the network node 16H may include in the request signaling that indicates which data is to be integrity protected.

[0103] In either case, the network node 16H in some embodiments decides which data in the container IE 18 is to be integrity protected and then generates the request 30 accordingly, e.g., to include whatever data the network node 16H decides is to form the integrity protected data 24. For example, the network node 16H may decide to integrity protect data that includes the header data 20 if both the communication device 12 and the home network 10H have capability to handle the header data 20 being integrity protected. The network node 16H may for instance be informed about the communication device’s capability in this regard by receiving capability signaling from the communication device 12 indicating whether the communication device 23 has the capability to handle the header data 20 being integrity protected. Otherwise, if the communication device 12 and the home network 10H do not both have capability to handle the header data 20 being integrity protected, the network node 16H may decide to integrity protect data that excludes the header data 20, e.g., by integrity protecting only the device configuration data 14, not the header data 20.

[0104] In any event, provided with the data to be integrity protected, the authentication server 32 correspondingly generates the integrity check data 22 according to the request 30. The authentication server 32 may for instance compute the integrity check data 22 (e.g., as a MAC) using the integrity protected data 24 as input, along with a security key (e.g., KAUSF) at the authentication server 32. In some embodiments, for example, the authentication server 32 forms an input to a key derivation function (KDF) from a set of input parameters, where the set of input parameters includes at least the integrity protected data 24 included in the request 30, calculates an output of the KDF with the formed input, and generates the integrity check data 22 from the output of the KDF.

[0105] Some embodiments herein are applicable in the following context where the device configuration data 14 includes a UPU parameter list, the header data 20 is the UPU header, the integrity check data 22 is a MAC, the home network 10H is a 5G network, the network node 16H in the home network 10H implements a UDM, the authentication server 32 implements an authentication server function (ALISF), and the serving network 10S is represented by an Access and Mobility Function (AMF). Some embodiments herein are thereby applicable to the UPU procedure as otherwise specified by 3GPP TS 23.502 V18.2.0 and 33.501 V18.2.0. In these examples, the UPU parameter list is integrity protected as a baseline, and the UPU header may or may not be integrity protected as well, depending on whether the UE and the network have that capability. In some embodiments, for example, the UPU Header is included as input to the MAC calculation from Rel-18 onwards. UPU procedure where UE and network both have header protection capability

[0106] Figure 3 shows the UPU procedure according to some embodiments where both the UE 12 and the home network are capable of handling integrity protection of the UPU header 20 in addition to the UPU parameter list 14.

[0107] Step 0: In case the UE 12 supports inclusion of the UPU Header 20 in the MAC calculation (i.e. , UE is of Rel-18 or later) the UE 12 will send its capability to the UDM 16H. That is, the UE 12 indicates to the network its capabilities for supporting header protection within UPU MAC. This may be done in any number of different ways, e.g., See, Nokia, et al., “Enhancement in UPU procedure to protect UPU header-AII 3 solutions,” 3GPP TSG-SA3 Meeting #111 , S3-232522, Berlin, Germany, 22 -26 May 2023.

[0108] Step 1: Upon reception of the UE capability indication to support UPU Header protection, the UDM 16H may store the indication (i.e., in the Unified Data Repository, UDR).

[0109] Step 2: The UDM 16H detects a trigger to initiate a UPU procedure for the UE 12.

[0110] Step 3: In case the UDM 16H stores an indication for the UE 12 that the UE 12 supports inclusion of the UPU Header 20 in the MAC calculation, the UDM 16H shall create an enhanced UPU Header 20, e.g., as otherwise specified by Figure 9.11.3.53A.6 of TS 24.501.

[0111] Figure 4 shows one example of the enhanced UPU Header 20. The UPU data type field has a value of “0” to represent the container IE 18 as sent from the network to the UE 12 (whereas a value of “1” represents a container IE sent from the UE to the network, for sending an acknowledgment to the network). The ACK field has a value indicating whether or not the network requests acknowledgement of the container IE 18 sent to the UE 12. The REG field indicates whether the UE 12 is to re-register after being configured with the UPU parameters. Notably, embodiments herein introduce a NW_CAP bit of the UPU Header 20. The NW_CAP bit may take the place of a bit that would otherwise remain spare, e.g., so that one of the otherwise spare bits is used to indicate the network capability to support UPU Header protection to the UE 12. Here, the NW_CAP bit exemplifies the integrity protected data indicator 26 in Figure 1, e.g., where NW_CAP = 0 explicitly indicates that the network (NW) has the capability to integrity protect the UPU Header 20 and thereby implicitly indicates that the UPU Header 20 is indeed integrity protected. In some embodiments, this effects a negotiation or exchange of capabilities between the UE and NW regarding support for UPU header protection.

[0112] The UDM 16H then transmits a request to the AUSF 32 to protect the UPU parameter list 14 and the enhanced UPU Header 20 in the MAC calculation. For this, the UDM 16H includes in a Nausf_UPUProtection_Protect Request the enhanced UPU Header 20 and an indication to the AUSF 32 to generate the MAC 22 using the (enhanced) UPU header 20. The Nausf_UPUProtection_Protect Request exemplifies the request 30 in Figure 1. Note that the explicit indication to the AUSF 32 to generate the MAC 22 using the (enhanced) UPU header 20 may be helpful so that the AUSF 32 is not required to understand the content of the UPU Header 20.

[0113] Step 4: The ALISF 32 generates MAC 22 for the UPU parameter list 14 and the (enhanced) UPU Header 20. Here, the MAC 22 exemplifies the integrity check data 22 in Figure 1. The MAC 22 may be generated based on a key Kausf generated during primary authentication of the UE 12. Because the Kausf is kept at the AUSF 32, the 16H UDM uses the Nausf_UPU Protection service to get the MAC 22 from the AUSF 32.

[0114] Step 5: The AUSF 32 provides the MAC 22 including the (enhanced) UPU Header 20 to the UDM 16H.

[0115] Step 6: The UDM 16H generates a UPU transparent container 18 including the (enhanced) UPU Header 20 and the UPU parameter list 14. The UPU transparent container 18 exemplifies the container IE 18 in Figure 1. Figure 5 shows one example as a UE parameters update transparent container (called UPU container), as otherwise specified in clause 9.11.3.53A of 3GPP TS 24.501 V18.3.0. As shown, the UPU Header is included in Octet 4 of the UPU transparent container 18. The MAC 22 from the AUSF 32 is included in Octets 5-20 as UPU-MAC-IAUSF. And the UE parameters update list 14 is included in Octets 23*-n*.

[0116] Regardless, the UDM 16H then sends the UPU transparent container 18 (containing the UE parameters update list 14, the enhanced UPU Header 20, and MACC 22) to the AMF, in order to transparently convey the UE parameters update list 14 to the UE 12.

[0117] Step 7: The AMF provides the received UPU Transparent container 18 from the UDM 16H to the UE 12.

[0118] Step 8: Then, when the UE 12 receives a UPU transparent container 18, it shall inspect the UE parameters update header 20 to see if the NW_CAP bit is set. In case the bit is set, the UE 12 shall include the (enhanced) UPU Header 20 in the MAC verification.

[0119] Step 9: The UE 12 completes the UPU procedure as in the baseline. If the MAC verification is successful, the UE 12 will accept the UPU data 14. If requested to do so by the network, the UE 12 will also send an integrity protected acknowledgement (ACK) back to the network.

[0120] Notably, by including the UPU Header 20 in the MAC calculation, these embodiments safeguard against a malicious entity in the path between UDM 16H and UE 12 modifying the contents of the UPU Header 20, e.g., to maliciously remove the network’s request that the UE send the UPU ACK back to the UDM 16H or the requirement that the UE initiates re-registration after reception of the UPU parameter list.

[0121] UPU procedure where NW lacks header protection capability

[0122] Figure 6 shows the UPU procedure according to some embodiments where the home network 10H lacks the capability to integrity protect the UPU header 20.

[0123] In this case, the UE 12 sends its capability to the UDM 16H (Step 0), but since the network 10H is of previous release, the UE indication is ignored in the UDM 16H (step 1) and the network 10H acts according to the legacy baseline approach (steps 2-7), i.e., the UDM 16H ignores the UE indication and does not set the NW_CAP bit in the (enhanced) UPU Header 20 and does not request the ALISF 32 to include the UPU header 20 in the MAC calculation.

[0124] In the UE side, the Rel-18 UE checks the UPU header 20 received within the UPU Transparent container 18, and since it does not include the NW_CAP, then the UE 12 verifies the MAC as in the baseline, i.e., without using the UPU Header 20. UPU procedure where UE lacks header protection capability

[0125] Figure 7 shows the UPU procedure according to some embodiments where the UE 12 lacks the capability to integrity protect the UPU header 20.

[0126] In this case, the UE 12 does not support the capability to protect the MAC using the UPU Header 20 and therefore does not send its capability to the UDM 16H and the UDM 16H does not store any UE capability indication from the UE 12 (Step 0-1). When the UDM 16H has the need to initiate an UPU procedure (Step 2), since there is no UE indication stored for the UE 12 it does not request the AUSF 32 to include the UPU header 20 in the MAC calculation (Step 3).

[0127] The rest of the UPU procedure is then executed as in the baseline (step 4-9). The UPU header 20 in this case may include the new NW_CAP indication or not. Since the UE 12 does not support this capability, the UE 12 will ignore this bit within the UPU header 20 if set.

[0128] Consider now how embodiments herein may accommodate or account for different alternatives for how the UE signals its capability to handle header integrity protection.

[0129] In a first alternative, if the UE 12 supports the Rel-18 feature of adding UPU Header in the UPU MAC, it will indicate it to the network in the ACK of the first run of UPU (which is performed without UPU header protection). If UE supports header protection as indicated by the Header_Protection bit in the ACK, the UDM includes the header along with the data in the next UPU data. Accordingly, the UE 12 expects the network to apply this in the following UPU messages. Some embodiments accommodate this first alternative even if the network side (UDM / AUSF) is not enhanced to support Rel-18, e.g., if the network (UDM) is of Rel-17. In that case, the UE will gather that the network is not enhanced to add the UPU Header 20 in the UPU MAC and will correspondingly calculate its MAC for verification from only the UE parameters update list 14.

[0130] In a second alternative, the UE 12 provides a new capability indication that it supports enhanced UPU header protection. For example, the UE 12 may provide the capability indication as an IE within the registration request in the 5GS. The AMF then provides the indication to the UDM 16H during AMF registration in UDM and UDM stores the indication for future use. Based on this indication from the UE 12, the UDM 16H includes the UPU header in the UPU packet protection. If the UE 12 does not support the feature, though, the UDM 16H shall not include the UPU header in the UPU packet protected.

[0131] In a third alternative, a HoPU procedure is used, e.g., as described in International Application Publication No. WO 2023006349A1.

[0132] In any alternative, some embodiments avoid a gap that the UE would not know the capability (version) of the network (AUSF / UDM).

[0133] Note that some embodiments herein advantageously prove resource efficient, in that they avoid a different alternative where a Rel-18 UDM would always sends both protected and unprotected headers. In this alternative, the UDM would be required to create MACs including and not including the header for every UPU procedure, which would be a waste in resources.

[0134] Generally, then, some embodiments herein define a capability indication that can be sent from the network to the UE 12 indicating if the network 10H supports the new feature of adding the UPU Header 20 in the UPU MAC. The UE may thereby receive a UE parameter update containing an indication that the network supports including the UPU header in the integrity protection of the UE parameter update. The indication can be included in the UPU header itself. Regardless, based on that indication, the UE verifies the integrity protection of the UE parameter update including the UPU header.

[0135] Some embodiments presuppose that the UE 12 has provided its capabilities for supporting header protection within UPU MAC. In this case, altogether a UPU Header protection capability negotiation between the UE and the network can be achieved. The same principles can be applied to other future capability negotiation needs in the context of UPU or steering of roaming (SoR).

[0136] Some embodiments may be advantageous in that the indication reuses existing lEs and / or a UE with lower version will not interpret the indicator, providing backwards compatibility.

[0137] In view of the modifications and variations herein, Figure 8 depicts a method performed by a communication device 12 in accordance with particular embodiments. The method includes receiving, from a home network 10H of the communication device 12, a container information element 18 that includes header data 20, device configuration data 14, and integrity check data 22 (Block WW100). The container information element 18 indicates which data in the container information element 18 is included in integrity protected data 24 that is integrity protected by the integrity check data 22. The method also includes using the integrity check data 22 to check an integrity of the integrity protected data 24 indicated by the container information element 18 (Block WW110).

[0138] In some embodiments, the header data in the container information element indicates which data in the container information element is included in integrity protected data that is integrity protected by the integrity check data.

[0139] In some embodiments, the container information element indicates which data in the container information element is included in integrity protected data by indicating whether the header data is included in integrity protected data. In some embodiments, the integrity protected data includes at least the device configuration data. The container information element indicates which data in the container information element is included in integrity protected data by indicating whether the integrity protected data also includes the header data.

[0140] In some embodiments, the container information element includes an indicator that indicates whether the integrity protected data includes the header data. A first possible value of the indicator indicates that the integrity protected data includes the header data and a second possible value of the indicator indicates that the integrity protected data does not include the header data.

[0141] In some embodiments, the indicator explicitly indicates whether the integrity protected data includes the header data. In some embodiments, the indicator implicitly indicates whether the integrity protected data includes the header data by indicating whether the home network is capable of integrity protecting the header data.

[0142] In some embodiments, the indicator is included in the header data.

[0143] In some embodiments, the container information element is configurable to include an indicator which indicates that the integrity protected data includes the header data. The inclusion of the indicator in the container information element indicates that the integrity protected data includes the header data and exclusion of the indicator from the container information element indicates that the integrity protected data does not include the header data.

[0144] In some embodiments, the indicator explicitly indicates that integrity protected data includes the header data.

[0145] In some embodiments, the indicator implicitly indicates that the integrity protected data includes the header data by indicating that the home network is capable of integrity protecting the header data.

[0146] In some embodiments, the container information element is configurable to include the indicator in the header data.

[0147] In some embodiments, the container information element indicates which data in the container information element is integrity protected data by indicating a type or version of integrity protection applied to the container information element. Different types or versions of integrity protection integrity protect at least some different data in the container information element.

[0148] In some embodiments, a first type or version of integrity protection integrity protects the device configuration data but not the header data. A second type or version of integrity protection integrity protects both the device configuration data and the header data.

[0149] In some embodiments, using (Block WW110) the integrity check data comprises generating integrity check match data as a function of the integrity protected data indicated by the container information element; performing a comparison of the integrity check match data to the integrity check data included in the container information element; and determining whether or not the integrity of the integrity protected data is intact based on the comparison.

[0150] In some embodiments, the integrity protected data includes at least the device configuration data. The generating integrity check match data as a function of the integrity protected data comprises, based on the container information element indicating that the header data is integrity protected data, generating the integrity check match data as a function of the device configuration data and the header data.

[0151] In some embodiments, the integrity protected data includes at least the device configuration data. The generating integrity check match data as a function of the integrity protected data comprises if the container information element indicates that the integrity protected data includes the header data, generating the integrity check match data as a function of the device configuration data and the header data; or if the container information element indicates that the integrity protected data does not include the header data, generating the integrity check match data as a function of the device configuration data but not as a function of the header data.

[0152] In some embodiments, the integrity check match data is a message authentication code (MAC).

[0153] In some embodiments, the device configuration data includes steering of roaming information. The steering of roaming information comprises information for encouraging the communication device to roam to a preferred roamed-to-network indicated by the home network

[0154] In some embodiments, the device configuration data includes a set of one or more device parameters. The set of one or more device parameters includes a parameter that indicates default configured network slice selection assistance information, NSSAI; and / or a parameter that indicates routing indicator data.

[0155] In some embodiments, the device configuration data includes User Equipment, UE, Parameter Update (UPU) data.

[0156] In some embodiments, the receiving (Block WW100) comprises receiving the container information element from a first core network node in the home network. In some embodiments, the first core network node implements a unified data management (UDM) function.

[0157] In some embodiments, the receiving (Block WW100) comprises receiving the container information element via a second core network node in a serving network of the communication device, by receiving a downlink control plane message from the first core network node. The downlink control plane message includes the container information element. In some embodiments, the downlink control plane message is a downlink non-access stratum transport message. In some embodiments, the second core network node implements an access and mobility function (AMF). In some embodiments, the method performed by the communication device 12 further comprises providing user data; and forwarding the user data to a host computer via the transmission to a base station.

[0158] Figure 9 depicts a method performed by a network node 16H in a home network 10H of a communication device 12 in accordance with other particular embodiments. The method includes generating a container information element 18 to include header data 20, device configuration data 14, and integrity check data 22, and to indicate which data in the container information element 18 is included in integrity protected data 24 that is integrity protected by the integrity check data 22 (Block WW200) . The method also includes transmitting the container information element 18 to the communication device 12 (Block WW210).

[0159] In some embodiments, the method includes transmitting, to another network node 32 in the home network 10H, a request 30 for the another network node 32 to integrity protect the integrity protected data 24 by generating the integrity check data 22 (Block WW220). In some embodiments, the request includes the integrity protected data.

[0160] In some embodiments, the method includes receiving the integrity check data 22 from the another network node 32 in response to the request 30 (Block WW230).

[0161] In some embodiments, the method includes making a decision about which data in the container information element to integrity protect as integrity protected data. The method also includes generating the request to include the integrity protected data according to the decision.

[0162] In some embodiments, the decision is made to integrity protect data that includes the header data if both the communication device and the home network have capability to handle the header data being integrity protected.

[0163] In some embodiments, the method includes receiving capability signaling from the communication device indicating whether the communication device has the capability to handle the header data being integrity protected (Block WW260).

[0164] In some embodiments, the request explicitly indicates that the header data is to be integrity protected in addition to the device configuration data.

[0165] In some embodiments, the another network node is an authentication server.

[0166] In some embodiments, the method includes generating the header data to indicate which data in the container information element is integrity protected data that is integrity protected by the integrity check data (Block WW270).

[0167] The corresponding embodiments for the method performed by the communication device 12 are also applicable for the method performed by the network node 16H in the home network 10H of the communication device 12.

[0168] Figure 10 depicts a method performed by an authentication server 32 in a home network 10H of a communication device 12 in accordance with other particular embodiments. The method includes receiving, from a network node 16H in the home network 10H, a request 30 for the authentication server 32 to generate integrity check data 22 that integrity protects integrity protected data 24 comprising both device configuration data 14 and header data 20 to be included in a container information element 18 (Block WW400). The method also includes generating the integrity check data 22 according to the request 30 (Block WW410). The method also includes transmitting the integrity check data 22 to the network node 16H in response to the request 30 (Block WW420).

[0169] The corresponding embodiments for the methods performed by the communication device 12 and the network node 16H are also applicable for the method performed by the authentication server 32 in a home network 10H of a communication device 12.

[0170] Note that, for any of the methods herein, the steps of the method may be performed in any order unless otherwise indicated.

[0171] Embodiments herein also include corresponding apparatuses. Embodiments herein for instance include a communication device 12 configured to perform any of the steps of any of the embodiments described above for the communication device 12.

[0172] Embodiments also include a communication device 12 comprising processing circuitry and power supply circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the communication device 12. The power supply circuitry is configured to supply power to the communication device 12.

[0173] Embodiments further include a communication device 12 comprising processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the communication device 12. In some embodiments, the communication device 12 further comprises communication circuitry.

[0174] Embodiments further include a communication device 12 comprising processing circuitry and memory. The memory contains instructions executable by the processing circuitry whereby the communication device 12 is configured to perform any of the steps of any of the embodiments described above for the communication device 12.

[0175] Embodiments moreover include a user equipment (UE). The UE comprises an antenna configured to send and receive wireless signals. The UE also comprises radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the communication device 12. In some embodiments, the UE also comprises an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry. The UE may comprise an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry. The UE may also comprise a battery connected to the processing circuitry and configured to supply power to the UE. Embodiments herein also include a network node 16H configured to perform any of the steps of any of the embodiments described above for the network node 16H.

[0176] Embodiments also include a network node 16H comprising processing circuitry and power supply circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the network node 16H. The power supply circuitry is configured to supply power to the network node 16H.

[0177] Embodiments further include a network node 16H comprising processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the network node 16H. In some embodiments, the network node 16H further comprises communication circuitry.

[0178] Embodiments further include a network node 16H comprising processing circuitry and memory. The memory contains instructions executable by the processing circuitry whereby the network node 16H is configured to perform any of the steps of any of the embodiments described above for the network node 16H.

[0179] Embodiments herein further include an authentication server 32 configured to perform any of the steps of any of the embodiments described above for the authentication server 32.

[0180] Embodiments also include an authentication server 32 comprising processing circuitry and power supply circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the authentication server 32. The power supply circuitry is configured to supply power to the authentication server 32.

[0181] Embodiments further include an authentication server 32 comprising processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the authentication server 32. In some embodiments, the authentication server 32 further comprises communication circuitry.

[0182] Embodiments further include an authentication server 32 comprising processing circuitry and memory. The memory contains instructions executable by the processing circuitry whereby the authentication server 32 is configured to perform any of the steps of any of the embodiments described above for the authentication server 32.

[0183] More particularly, the apparatuses described above may perform the methods herein and any other processing by implementing any functional means, modules, units, or circuitry. In one embodiment, for example, the apparatuses comprise respective circuits or circuitry configured to perform the steps shown in the method figures. The circuits or circuitry in this regard may comprise circuits dedicated to performing certain functional processing and / or one or more microprocessors in conjunction with memory. For instance, the circuitry may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory may include program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In embodiments that employ memory, the memory stores program code that, when executed by the one or more processors, carries out the techniques described herein.

[0184] Figure 11 for example illustrates a communication device 12 as implemented in accordance with one or more embodiments. As shown, the communication device 12 includes processing circuitry YY110 and communication circuitry YY120. The communication circuitry YY120 (e.g., radio circuitry) is configured to transmit and / or receive information to and / or from one or more other nodes, e.g., via any communication technology. Such communication may occur via one or more antennas that are either internal or external to the communication device YY100. The processing circuitry YY110 is configured to perform processing described above, e.g., in Figure 8, such as by executing instructions stored in memory YY130. The processing circuitry YY110 in this regard may implement certain functional means, units, or modules.

[0185] Figure 12 illustrates a network node 16H as implemented in accordance with one or more embodiments. As shown, the network node 16H includes processing circuitry YY210 and communication circuitry YY220. The communication circuitry YY220 is configured to transmit and / or receive information to and / or from one or more other nodes, e.g., via any communication technology. The processing circuitry YY210 is configured to perform processing described above, e.g., in Figure 9 and / or Figure 10, such as by executing instructions stored in memory YY230. The processing circuitry YY210 in this regard may implement certain functional means, units, or modules.

[0186] Figure 13 illustrates an authentication server 32 as implemented in accordance with one or more embodiments. As shown, the authentication server 32 includes processing circuitry YY310 and communication circuitry YY320. The communication circuitry YY320 is configured to transmit and / or receive information to and / or from one or more other nodes, e.g., via any communication technology. The processing circuitry YY310 is configured to perform processing described above, e.g., in Figure 10, such as by executing instructions stored in memory YY330. The processing circuitry YY310 in this regard may implement certain functional means, units, or modules.

[0187] Those skilled in the art will also appreciate that embodiments herein further include corresponding computer programs.

[0188] A computer program comprises instructions which, when executed on at least one processor of an apparatus, cause the apparatus to carry out any of the respective processing described above. A computer program in this regard may comprise one or more code modules corresponding to the means or units described above.

[0189] Embodiments further include a carrier containing such a computer program. This carrier may comprise one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

[0190] In this regard, embodiments herein also include a computer program product stored on a non-transitory computer readable (storage or recording) medium and comprising instructions that, when executed by a processor of an apparatus, cause the apparatus to perform as described above.

[0191] Embodiments further include a computer program product comprising program code portions for performing the steps of any of the embodiments herein when the computer program product is executed by a computing device. This computer program product may be stored on a computer readable recording medium.

[0192] Figure 14 shows an example of a communication system QQ100 in accordance with some embodiments.

[0193] In the example, the communication system QQ100 includes a telecommunication network QQ102 that 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, such as network nodes QQ110a and QQ110b (one or more of which may be generally referred to as network nodes QQ110), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network QQ102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network QQ102 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 QQ102, including one or more network nodes QQ110 and / or core network nodes QQ108.

[0194] Examples of an ORAN network node include an open radio unit (0-Rll), an open distributed unit (0-Dll), an open central unit (O-CU), including an O-CU control plane (O-CU- CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1, F1, W1, E1 , E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes QQ110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may be generally referred to as UEs QQ112) to the core network QQ106 over one or more wireless connections.

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

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

[0197] In the depicted example, the core network QQ106 connects the network nodes QQ110 to one or more hosts, such as host QQ116. 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 QQ106 includes one more core network nodes (e.g., core network node QQ108) 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 QQ108. 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 (ALISF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0198] The host QQ116 may be under the ownership or control of a service provider other than an operator or provider of the access network QQ104 and / or the telecommunication network QQ102, and may be operated by the service provider or on behalf of the service provider. The host QQ116 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.

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

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

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

[0202] In the example, 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 network nodes (e.g., network node QQ110b). In some examples, the hub QQ114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub QQ114 may be a broadband router enabling access to the core network QQ106 for the UEs. As another example, the hub QQ114 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 QQ110, or by executable code, script, process, or other instructions in the hub QQ114. As another example, the hub QQ114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub QQ114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub QQ114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub QQ114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub QQ114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0203] The hub QQ114 may have a constant / persistent or intermittent connection to the network node QQ110b. The hub QQ114 may also allow for a different communication scheme and / or schedule between the hub QQ114 and UEs (e.g., UE QQ112c and / or QQ112d), and between the hub QQ114 and the core network QQ106. In other examples, the hub QQ114 is connected to the core network QQ106 and / or one or more UEs via a wired connection. Moreover, the hub QQ114 may be configured to connect to an M2M service provider over the access network QQ104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes QQ110 while still connected via the hub QQ114 via a wired or wireless connection. In some embodiments, the hub QQ114 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 QQ110b. In other embodiments, the hub QQ114 may be a nondedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node QQ110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0204] Figure 15 shows a UE QQ200 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 IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, 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 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB- loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0205] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0206] The UE QQ200 includes processing circuitry QQ202 that is operatively coupled via a bus QQ204 to an input / output interface QQ206, a power source QQ208, a memory QQ210, a communication interface QQ212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure QQ2. 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.

[0207] The processing circuitry QQ202 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 QQ210. The processing circuitry 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 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 QQ202 may include multiple central processing units (CPUs).

[0208] In the example, the input / output interface QQ206 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 QQ200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

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

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

[0211] The memory QQ210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The IIICC may for example be an embedded IIICC (elllCC), integrated IIICC (illlCC) or a removable IIICC commonly known as ‘SIM card.’ The memory QQ210 may allow the UE QQ200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory QQ210, which may be or comprise a device-readable storage medium.

[0212] The processing circuitry QQ202 may be configured to communicate with an access network or other network using the communication interface QQ212. The communication interface QQ212 may comprise one or more communication subsystems and may include or be 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 a network node in an access network). Each transceiver may include a transmitter QQ218 and / or a receiver QQ220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, 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 be implemented separately.

[0213] In the illustrated embodiment, communication functions of the communication interface QQ212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0214] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface QQ212, 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). As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0215] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not 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 TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (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 QQ200 shown in Figure QQ2.

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

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

[0218] Figure 16 shows a network node QQ300 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, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0219] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0220] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cel l / 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).

[0221] The network node QQ300 includes a processing circuitry QQ302, a memory QQ304, a communication interface QQ306, and a power source QQ308. The network node QQ300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node QQ300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 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., a same antenna QQ310 may be shared by different RATs). The network node QQ300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node QQ300.

[0222] The processing circuitry QQ302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node QQ300 components, such as the memory QQ304, to provide network node QQ300 functionality.

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

[0224] The memory QQ304 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry QQ302. The memory QQ304 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 QQ302 and utilized by the network node QQ300. The memory QQ304 may be used to store any calculations made by the processing circuitry QQ302 and / or any data received via the communication interface QQ306. In some embodiments, the processing circuitry QQ302 and memory QQ304 is integrated.

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

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

[0227] The antenna QQ310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna QQ310 may be coupled to the radio frontend circuitry QQ318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna QQ310 is separate from the network node QQ300 and connectable to the network node QQ300 through an interface or port.

[0228] The antenna QQ310, communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna QQ310, the communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment. The power source QQ308 provides power to the various components of network node QQ300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source QQ308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node QQ300 with power for performing the functionality described herein. For example, the network node QQ300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source QQ308. As a further example, the power source QQ308 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.

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

[0230] Figure 17 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Figure 14, in accordance with various aspects described herein. As used herein, the host QQ400 may be or comprise various combinations 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 QQ400 may provide one or more services to one or more UEs.

[0231] The host QQ400 includes processing circuitry QQ402 that is operatively coupled via a bus QQ404 to an input / output interface QQ406, a network interface QQ408, a power source QQ410, and a memory QQ412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 15 and 16, such that the descriptions thereof are generally applicable to the corresponding components of host QQ400.

[0232] The memory QQ412 may include one or more computer programs including one or more host application programs QQ414 and data QQ416, which may include user data, e.g., data generated by a UE for the host QQ400 or data generated by the host QQ400 for a UE. Embodiments of the host QQ400 may utilize only a subset or all of the components shown. The host application programs QQ414 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), MPEG, VP9) and audio codecs (e.g., FLAG, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs QQ414 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 QQ400 may select and / or indicate a different host for over- the-top services for a UE. The host application programs QQ414 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 (MPEG- DASH), etc.

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

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

[0235] Hardware QQ504 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 QQ506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs QQ508a and QQ508b (one or more of which may be generally referred to as VMs QQ508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer QQ506 may present a virtual operating platform that appears like networking hardware to the VMs QQ508.

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

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

[0238] Hardware QQ504 may be implemented in a standalone network node with generic or specific components. Hardware QQ504 may implement some functions via virtualization. Alternatively, hardware QQ504 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 QQ510, which, among others, oversees lifecycle management of applications QQ502. In some embodiments, hardware QQ504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system QQ512 which may alternatively be used for communication between hardware nodes and radio units.

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

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

Claims

CLAIMS1. A method performed by a communication device (12), the method comprising: receiving (WW100), from a home network (10H) of the communication device (12), a container information element (18) that includes header data (20), device configuration data (14), and integrity check data (22), wherein the container information element (18) indicates which data in the container information element (18) is included in integrity protected data (24) that is integrity protected by the integrity check data (22); and using (WW110) the integrity check data (22) to check an integrity of the integrity protected data (24) indicated by the container information element.

2. The method of claim 1 , wherein using (WW110) the integrity check data (22) comprises: generating integrity check match data as a function of the integrity protected data (24) indicated by the container information element (18); performing a comparison of the integrity check match data to the integrity check data (22) included in the container information element (18); and determining whether or not the integrity of the integrity protected data (24) is intact based on the comparison.

3. The method of any of claims 1-2, wherein said receiving (WW100) comprises receiving the container information element (18) from a first core network node in the home network.

4. The method of any of claims 1-3, wherein said receiving (WW100) comprises receiving the container information element (18) via a second core network node in a serving network of the communication device (12), by receiving a downlink control plane message from the first core network node, wherein the downlink control plane message includes the container information element (18).

5. A method performed by a network node (16H) in a home network (10H) of a communication device (12), the method comprising: generating (WW200) a container information element (18) to include header data (20), device configuration data (14), and integrity check data (22), and to indicate which data in the container information element (18) is included in integrity protected data (24) that is integrity protected by the integrity check data (22); and transmitting (WW210) the container information element (18) to the communication device (12).

6. The method of claim 5, wherein the network node is a first core network node in the home network.

7. The method of any of claims 5-6, wherein said transmitting (WW210) comprises transmitting the container information element (18) via a second core network node in a serving network of the communication device (12), by transmitting a downlink control plane message to the communication device (12), wherein the downlink control plane message includes the container information element (18).

8. The method of any of claims 5-7, further comprising: transmitting (WW220), to another network node in the home network (10H), a request for the another network node to integrity protect the integrity protected data (24) by generating the integrity check data (22), wherein the request includes the integrity protected data (24); and receiving (WW230) the integrity check data (22) from the another network node in response to the request.

9. The method of claim 8, further comprising: making a decision about which data in the container information element (18) to integrity protect as integrity protected data (24); and generating the request to include the integrity protected data (24) according to the decision.

10. The method of claim 9, further comprising receiving (WW260) capability signaling from the communication device (12) indicating whether the communication device (12) has the capability to handle the header data (20) being integrity protected.

11. The method of any of claims 8-10, wherein the another network node is an authentication server (32).

12. The method of claim 5, further comprising generating (WW270) the header data (20) to indicate which data in the container information element (18) is integrity protected data (24) that is integrity protected by the integrity check data (22).

13. A method performed by an authentication server (32) in a home network (10H) of a communication device (12), the method comprising:receiving (WW400), from a network node (16H) in the home network (10H), a request (30) for the authentication server (32) to generate integrity check data (22) that integrity protects integrity protected data (24) comprising both device configuration data (14) and header data (20) to be included in a container information element (18), wherein the request (30) includes the integrity protected data (24); generating (WW410) the integrity check data (22) according to the request (30); and transmitting (WW420) the integrity check data (22) to the network node (16H) in response to the request (30).

14. The method of claim 13, wherein the network node (16H) is a first core network node in the home network (10H).

15. A communication device (12) configured to perform the method of any of claims 1-4.

16. A computer program comprising instructions which, when executed by at least one processor of a communication device (12), causes the communication device (12) to perform the method of any of claims 1-4.

17. A network node (16H) configured to perform the method of any of claims 5-12.

18. A computer program comprising instructions which, when executed by at least one processor of a network node (16H), causes the network node (16H) to perform the method of any of claims 5-12.

19. An authentication server (32) configured to perform the method of any of claims 13-14.

20. A computer program comprising instructions which, when executed by at least one processor of an authentication server (32), causes the authentication server (32) to perform the method of any of claims 13-14.

Images