WO2022038008A1 - Établissement de sécurité pour réseaux non publics en 5g - Google Patents

Établissement de sécurité pour réseaux non publics en 5g Download PDF

Info

Publication number
WO2022038008A1
WO2022038008A1 PCT/EP2021/072333 EP2021072333W WO2022038008A1 WO 2022038008 A1 WO2022038008 A1 WO 2022038008A1 EP 2021072333 W EP2021072333 W EP 2021072333W WO 2022038008 A1 WO2022038008 A1 WO 2022038008A1
Authority
WO
WIPO (PCT)
Prior art keywords
npn
network
msk
amf
authentication
Prior art date
Application number
PCT/EP2021/072333
Other languages
English (en)
Inventor
Noamen BEN HENDA
Henrik NORRMANN
David Castellanos Zamora
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2022038008A1 publication Critical patent/WO2022038008A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/04—Key management, e.g. using generic bootstrapping architecture [GBA]
    • H04W12/041—Key generation or derivation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/085—Access point devices with remote components

Definitions

  • the present application relates generally to the field of wireless communication networks, and more specifically to establish and/or maintain security credentials (e.g., encryption keys) that a user equipment (UE) can use when accessing a non-public network (NPN).
  • security credentials e.g., encryption keys
  • 5G fifth generation
  • NR New Radio
  • 3GPP Third-Generation Partnership Project
  • MTC machine type communication
  • URLCC ultralow latency critical communications
  • D2D side-link device-to-device
  • 3GPP security standardization working group SA3 specified the security -related features for Release 15 (Rel-15) of the 5G System (5GS) in 3GPP TS 33.501 (vl5.5.0).
  • 5GS includes many new features (e.g., as compared to earlier 4G/LTE systems) that required introduction of new security mechanisms.
  • 5GS seamlessly integrates non-3GPP access (e.g., via wireless LAN) together with 3GPP access (e.g., NR and/or LTE).
  • a user equipment e.g., wireless device
  • RAT radio access technology
  • 3GPP Rel-16 also specifies support for Non-Public Networks (NPN) that are for non- public use. This is described in 3GPP TS 23.501 (vl6.5.0).
  • NPN Non-Public Networks
  • An example NPN is a factory or other industrial facility that deploys its own 5GS to provide connectivity for both equipment and workers.
  • NPNs can be deployed as a Stand-alone Non-Public Network (SNPN) when not relying on network functions provided by a public land mobile network (PLMN).
  • An SNPN is identified by a PLMN ID and network ID (NID) broadcast in SIB1.
  • An SNPN-capable UE supports the SNPN access mode. When the UE is set to operate in SNPN access mode, the UE only selects and registers with SNPNs. When the UE is not set to operate in SNPN access mode, the UE performs normal PLMN selection procedures. UEs operating in SNPN access mode only (re)select cells within the selected/registered SNPN and a cell can only be considered as suitable if the PLMN and NID broadcast by the cell matches the selected/registered SNPN.
  • NPNs can be deployed as a Public Network Integrated (PNI) NPN when relying on functions provided by a PLMN.
  • PNI-NPNs Closed Access Groups (CAGs) identify groups of subscribers who are permitted to access one or more cells associated with the CAG.
  • a CAG is identified by a CAG identifier broadcast in SIB1.
  • a CAG-capable UE can be configured with the following per PLMN:
  • CAG-only indication if the UE is only allowed to access 5GS via CAG cells.
  • the UE checks the suitability of CAG cells based on the Allowed CAG list provided by upper layers.
  • the UE is configured with a CAG-only indication
  • only CAG Member Cells can be suitable.
  • a non-suitable cell can be acceptable though if the UE is configured with a CAG-only indication for one of the PLMN broadcast by the cell.
  • the Rel-16 enhancements specified for SNPNs include updates to the primary authentication procedures used by UEs. 3GPP is currently working on further enhancements to NPN supporting Rel-17. This architectural study work is captured in 3GPP TR 23.700-07 (v0.4.0).
  • the Rel-17 work objectives include enhanced UE authentication procedures that allow UEs to be authenticated by an external entity to the SNPN. However, currently there are no mechanisms by which the UE can establish security keys with the network based on default UE credentials, i.e., when the UE does not have existing credentials in relation to the SNPN.
  • exemplary embodiments of the present disclosure address these and other security -related problems, issues, and/or difficulties for NPNs, thereby enabling the otherwise- advantageous deployment of NPNs based on 5GS.
  • Some embodiments of the present disclosure include methods (e.g., procedures) for a UE (e.g., wireless device) to establish security keys for communication with an NPN, such as a standalone NPN.
  • These exemplary methods can include sending, to an access and mobility management function (AMF) associated with the NPN, a registration request that includes a first indication that the UE is onboarding to NPN.
  • AMF access and mobility management function
  • These exemplary methods can also include performing an authentication procedure, with a default credential server (DCS) external to the NPN, to obtain a master session key (MSK).
  • the authentication procedure can be performed without involvement of an authentication support function (AUSF) in the NPN.
  • the authentication procedure can be a network-slice-specific authentication and authorization (NSSAA) procedure.
  • NSSAA network-slice-specific authentication and authorization
  • These exemplary methods can also include, based on receiving a second indication from the AMF, deriving security keys for communication between the UE and the NPN based on the MSK.
  • sending the registration request can be based on determining that the UE does not have credentials needed for primary authentication with the NPN (e.g., via an AUSF in the NPN).
  • the registration request can also include a network slice identifier (S-NSSAI) related to onboarding and/or information associated with a subscription concealed identifier (SUCI) associated with the UE.
  • S-NSSAI network slice identifier
  • SUCI subscription concealed identifier
  • the second indication from the AMF can be any of the following:
  • these exemplary methods can also include, based on not receiving the second indication from the AMF, refraining from deriving the security keys based on the MSK. For example, if the UE does not receive the SMC message from the AMF within the predetermined duration, the UE can refrain from deriving the security keys based on the MSK.
  • deriving security keys based on the MSK can include deriving a first security key (KAMF) for communication between the UE and the AMF based on the MSK, and deriving one or more second security keys based on KAMF.
  • the UE can derive KA F based on the MSK according to one of the following operations:
  • a freshness parameter received as the second indication from the AMF, can be used as an additional input to the one-way key derivation function
  • Other embodiments include methods (e.g., procedures) for an AMF associated with an NPN (e.g., SNPN) to establish security keys for communication between a UE and the NPN.
  • NPN e.g., SNPN
  • These exemplary methods can include receiving, from the UE, a registration request that includes a first indication that the UE is onboarding to the NPN. These exemplary methods can also include determining that a NSSAA procedure should be used for this UE instead of a primary authentication procedure with the NPN. These exemplary methods can also include sending, to the UE, a second indication the UE should derive security keys for communication between the UE and the NPN based on a MSK obtained by the UE from a DCS external to the NPN.
  • the second indication can be any of the following:
  • the registration request can also include a network slice identifier (S-NSSAI) related to onboarding and/or a SUCI associated with the UE.
  • S-NSSAI network slice identifier
  • the SUCI is not associated with any subscriptions to the NPN.
  • determining that the NSSAA procedure should be used can be based on the first indication, the SUCI, and/or the S-NSSAI.
  • these exemplary methods can also include selecting an NSSAA function (NSSAAF) in the NPN based on the S-NSSAI and performing the NSSAA procedure with the selected NSSAAF to obtain the MSK.
  • NSSAAF NSSAA function
  • performing the NSSAA procedure can include sending, to the NSSAF, an authentication request for the UE and receiving the MSK from the AMF.
  • the authentication request can include a UE identifier.
  • determining that the NSSAA procedure should be used is based on a subscription permanent identifier (SUPI) associated with the UE.
  • the AMF can obtain the SUPI based on the SUCI included in the registration request and can include the SUPI as the UE identifier in the authentication request.
  • SUPI subscription permanent identifier
  • these exemplary methods can also include deriving a first security key (KAMF) for communication between the UE and the AMF based on the MSK.
  • KAMF first security key
  • the AMF can derive KAMF based on the MSK according to on one of the following operations:
  • a freshness parameter sent to the UE as the second indication, can be used as an additional input to the one-way key derivation function.
  • Other embodiments include methods (e.g., procedures) for an NSSAAF associated with an NPN (e.g., SNPN) to establish security keys for communication between a UE and the NPN.
  • NPN e.g., SNPN
  • These exemplary methods can include receiving, from an AMF associated with the NPN, an authentication request for the UE.
  • the authentication request can include a UE identifier, such as a SUPI associated with the UE.
  • These exemplary methods can also include selecting a DCS external to the NPN based on the UE identifier.
  • These exemplary methods can also include obtaining, from the DCS, a MSK for communication between the UE and the NPN.
  • These exemplary methods can also include sending the MSK to the AMF.
  • the UE identifier can include a network access identifier (NAI) that points to the selected DCS and/or a unique UE identifier used when obtaining the MSK from the DCS.
  • NAI network access identifier
  • the UE identifier is not associated with any subscriptions to the NPN.
  • the NSSAAF can select the DCS external to the NPN based on the UE identifier not being associated with any subscriptions to the NPN.
  • Other embodiments include methods e.g., procedures) for establishing security keys for communication between a UE and an NPN (e.g., SNPN). These exemplary methods can be performed by a DCS external to the NPN.
  • These exemplary methods can include receiving, from a NSSAAF associated with the NPN, a request for authentication of the UE. These exemplary methods can also include performing an authentication procedure, with the UE, to obtain a MSK for communication between the UE and the NPN. These exemplary methods can also include sending the MSK to the NSSAF.
  • the authentication procedure can be an extensible authentication procedure (EAP). In some embodiments, the authentication procedure can be performed without involvement of an authentication support function (AUSF) in the NPN.
  • EAP extensible authentication procedure
  • AUSF authentication support function
  • Other embodiments include UEs, AMFs, NSSAAFs, or DCS’s (or network nodes hosting the same) that are configured to perform the operations corresponding to any of the exemplary methods described herein.
  • Other embodiments include non-transitory, computer-readable media storing computer-executable instructions that, when executed by processing circuitry, configure such UEs, AMFs, NSSAAFs, or DCS’s to perform operations corresponding to any of the exemplary methods described herein.
  • FIGS 1-2 illustrate various aspects of an exemplary 5G network architecture.
  • Figure 3 shows an exemplary hierarchy of security keys in a 5G network.
  • Figure 4 shows a high-level view of a security key hierarchy that excludes keys from outside an extensible authentication protocol (EAP) realm.
  • EAP extensible authentication protocol
  • Figure 5 shows a signal flow diagram of an exemplary network slice specific authentication and authorization (NSSAA) procedure that results in key establishment, according to various embodiments of the present disclosure.
  • Figure 6 illustrates an exemplary method (e.g., procedure) for a user equipment (UE), according to various embodiments of the present disclosure.
  • NSSAA network slice specific authentication and authorization
  • Figure 7 illustrates an exemplary method (e.g., procedure) for an access and mobility management function (AMF) associated with a non-public network (NPN), according to various embodiments of the present disclosure.
  • AMF access and mobility management function
  • NPN non-public network
  • Figure 8 illustrates an exemplary method (e.g., procedure) for an NSSAA function associated with an NPN, according to various embodiments of the present disclosure.
  • Figure 9 illustrates an exemplary method (e.g., procedure) for a default credential server (DCS) external to an NPN, according to various embodiments of the present disclosure.
  • DCS credential server
  • Figure 10 illustrates a wireless network, according to various embodiments of the present disclosure.
  • FIG. 11 shows an exemplary embodiment of a UE, in accordance with various aspects described herein.
  • Figure 12 is a block diagram illustrating an exemplary virtualization environment usable for implementation of various embodiments of network nodes or NFs described herein.
  • Figures 13-14 are block diagrams of various exemplary communication systems and/or networks, according to various embodiments of the present disclosure.
  • Figures 15-18 are flow diagrams of exemplary methods (e.g., procedures) for transmission and/or reception of user data, according to various embodiments of the present disclosure.
  • Radio Access Node As used herein, a “radio access node” (or equivalently “radio network node,” “radio access network node,” or “RAN node”) can be any node in a radio access network (RAN) of a cellular communications network that operates to wirelessly transmit and/or receive signals.
  • RAN radio access network
  • a radio access node examples include, but are not limited to, a base station (c.g, a New Radio (NR) base station (gNB) in a 3GPP Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP LTE network), base station distributed components (e.g., CU and DU), a high-power or macro base station, a low-power base station (e.g., micro, pico, femto, or home base station, or the like), an integrated access backhaul (IAB) node (or component thereof such as MT or DU), a transmission point, a remote radio unit (RRU or RRH), and a relay node.
  • a base station c.g, a New Radio (NR) base station (gNB) in a 3GPP Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP LTE network
  • base station distributed components e.g., CU
  • a “core network node” is any type of node in a core network.
  • Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a serving gateway (SGW), a Packet Data Network Gateway (P-GW), etc.
  • a core network node can also be a node that implements a particular core network function (NF), such as an access and mobility management function (AMF), a session management function (AMF), a user plane function (UPF), a Service Capability Exposure Function (SCEF), or the like.
  • NF core network function
  • AMF access and mobility management function
  • AMF session management function
  • UPF user plane function
  • SCEF Service Capability Exposure Function
  • Wireless Device As used herein, a “wireless device” (or “WD” for short) is any type of device that has access to (i.e., is served by) a cellular communications network by communicate wirelessly with network nodes and/or other wireless devices. Communicating wirelessly can involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. Unless otherwise noted, the term “wireless device” is used interchangeably herein with “user equipment” (or “UE” for short).
  • a wireless device include, but are not limited to, smart phones, mobile phones, cell phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback appliances, wearable devices, wireless endpoints, mobile stations, tablets, laptops, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart devices, wireless customer-premise equipment (CPE), mobile-type communication (MTC) devices, Internet-of-Things (loT) devices, vehicle-mounted wireless terminal devices, mobile terminals (MTs), etc.
  • VoIP voice over IP
  • PDAs personal digital assistants
  • MTC mobile-type communication
  • LME mobile-mounted equipment
  • MTC mobile-type communication
  • MTC Internet-of-Things
  • MTs mobile terminals
  • Radio Node can be either a “radio access node” (or equivalent term) or a “wireless device.”
  • Network Node is any node that is either part of the radio access network (e.g., a radio access node or equivalent term) or of the core network (e.g., a core network node discussed above) of a cellular communications network.
  • a network node is equipment capable, configured, arranged, and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the cellular communications network, to enable and/or provide wireless access to the wireless device, and/or to perform other functions (e.g., administration) in the cellular communications network.
  • node can be any type of node that is capable of operating in or with a wireless network (including a RAN and/or a core network), including a radio access node (or equivalent term), core network node, or wireless device.
  • a wireless network including a RAN and/or a core network
  • radio access node or equivalent term
  • core network node or wireless device.
  • Service refers generally to a set of data, associated with one or more applications, that is to be transferred via a network with certain specific delivery requirements that need to be fulfilled in order to make the applications successful.
  • component refers generally to any component needed for the delivery of a service.
  • RANs e.g., E-UTRAN, NG-RAN, or portions thereof such as eNBs, gNBs, base stations (BS), etc.
  • CNs e.g., EPC, 5GC, or portions thereof, including all type of links between RAN and CN entities
  • cloud infrastructure with related resources such as computation, storage.
  • each component can have a “manager”, which is an entity that can collect historical information about utilization of resources as well as provide information about the current and the predicted future availability of resources associated with that component (e.g., a RAN manager).
  • WCDMA Wide Band Code Division Multiple Access
  • WiMax Worldwide Interoperability for Microwave Access
  • UMB Ultra Mobile Broadband
  • GSM Global System for Mobile Communications
  • functions and/or operations described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and/or network nodes.
  • the term “cell” is used herein, it should be understood that (particularly with respect to 5G NR) beams may be used instead of cells and, as such, concepts described herein apply equally to both cells and beams.
  • 3 GPP is currently working on further enhancements to NPN supporting Rel-17.
  • Rel-17 work is enhanced UE authentication procedures that allow UEs to be authenticated by an external entity to the SNPN.
  • the UE can establish security keys with the network based on default UE credentials, i.e., when the UE does not have existing credentials in relation to the NPN. This is discussed in more detail after the following description of various aspects of the 5G System (5GS).
  • 5GS 5G System
  • 5GS consists of an Access Network (AN) and a Core Network (CN).
  • the AN provides UEs connectivity to the CN, e.g., via base stations such as gNBs or ng-eNBs described below.
  • the CN includes a variety of Network Functions (NF) that provide a wide range of different functionalities such as session management, connection management, charging, authentication, etc.
  • NF Network Functions
  • FIG. 1 illustrates a high-level view of an exemplary 5G network architecture, consisting of a Next Generation RAN (NG-RAN) 199 and a 5G Core (5GC) 198.
  • NG-RAN 199 can include one or more gNodeB’s (gNBs) connected to the 5GC via one or more NG interfaces, such as gNBs 100, 150 connected via interfaces 102, 152, respectively. More specifically, gNBs 100, 150 can be connected to one or more Access and Mobility Management Functions (AMFs) in the 5GC 198 via respective NG-C interfaces. Similarly, gNBs 100, 150 can be connected to one or more User Plane Functions (UPFs) in 5GC 198 via respective NG-U interfaces.
  • AMFs Access and Mobility Management Functions
  • UPFs User Plane Functions
  • NFs User Plane Functions
  • NFs network functions
  • each of the gNBs can be connected to each other via one or more Xn interfaces, such as Xn interface 140 between gNBs 100 and 150.
  • the radio technology for the NG-RAN is often referred to as “New Radio” (NR).
  • NR New Radio
  • each of the gNBs can support frequency division duplexing (FDD), time division duplexing (TDD), or a combination thereof.
  • FDD frequency division duplexing
  • TDD time division duplexing
  • Each of the gNBs can serve a geographic coverage area including one or more cells and, in some cases, can also use various directional beams to provide coverage in the respective cells.
  • NG-RAN 199 is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL).
  • RNL Radio Network Layer
  • TNL Transport Network Layer
  • the NG-RAN architecture i.e., the NG-RAN logical nodes and interfaces between them, is defined as part of the RNL.
  • NG, Xn, Fl the NG-RAN interface
  • the TNL provides services for user plane transport and signaling transport.
  • each gNB is connected to all 5GC nodes within an “AMF Region” which is defined in 3GPP TS 23.501 (vl5.5.0). If security protection for CP and UP data on TNL of NG-RAN interfaces is supported, NDS/IP (3GPP TS 33.401 (vl5.8.0) shall be applied.
  • the NG RAN logical nodes shown in Figure 1 include a Central Unit (CU or gNB-CU) and one or more Distributed Units (DU or gNB-DU).
  • gNB 100 includes gNB-CU 110 and gNB-DUs 120 and 130.
  • CUs e.g., gNB-CU 110
  • a DU e.g., gNB-DUs 120, 130
  • each of the CUs and DUs can include various circuitry needed to perform their respective functions, including processing circuitry, transceiver circuitry (e.g., for communication), and power supply circuitry.
  • a gNB-CU connects to one or more gNB-DUs over respective Fl logical interfaces, such as interfaces 122 and 132 shown in Figure 1.
  • a gNB-DU can be connected to only a single gNB-CU.
  • the gNB-CU and connected gNB-DU(s) are only visible to other gNBs and the 5GC as a gNB. In other words, the Fl interface is not visible beyond gNB-CU.
  • SBA Service Based Architecture
  • NFs Network Functions
  • HTTP/REST Hyper Text Transfer Protocol/Representational State Transfer
  • APIs application programming interfaces
  • the various services are self-contained functionalities that can be changed and modified in an isolated manner without affecting other services.
  • This SBA model also adopts principles like modularity, reusability, and self-containment of NFs, which can enable deployments to take advantage of the latest virtualization and software technologies.
  • the services in 5GC can be stateless, such that the business logic and data context are separated.
  • the services can store their context externally in a proprietary database. This can facilitate various cloud infrastructure features like auto-scaling or auto-healing.
  • 5GC services can be composed of various “service operations”, which are more granular divisions of overall service functionality.
  • the interactions between service consumers and producers can be of the type “request/response” or “subscribe/notify”.
  • Figure 2 shows an exemplary non-roaming 5G reference architecture with service-based interfaces and various 3GPP-defined NFs. The operations of some of the NFs shown in Figure 2 can be summarized as follows:
  • Application Function interacts with the 5GC to provision information to the network operator and to subscribe to certain events happening in operator's network.
  • An AF offers applications for which service is delivered in a different layer (i.e., transport layer) than the one in which the service has been requested (i.e., signaling layer), the control of flow resources according to what has been negotiated with the network.
  • An AF communicates dynamic session information to PCF (via N5 interface), including description of media to be delivered by transport layer.
  • PCF Policy Control Function
  • Npcf interface supports unified policy framework to govern the network behavior, via providing PCC rules (e.g., on the treatment of each service data flow that is under PCC control) to the SMF via the N7 reference point.
  • PCF provides policy control decisions and flow based charging control, including service data flow detection, gating, QoS, and flow-based charging (except credit management) towards the SMF.
  • the PCF receives session and media related information from the AF and informs the AF of traffic (or user) plane events.
  • UPF User Plane Function
  • SMF packet inspection and different enforcement actions
  • PDN packet data network
  • the N9 reference point is for communication between two UPFs.
  • Session Management Function interacts with the decoupled traffic (or user) plane, including creating, updating, and removing Protocol Data Unit (PDU) sessions and managing session context with the User Plane Function (UPF), e.g., for event reporting.
  • SMF Session Management Function
  • PDU Protocol Data Unit
  • UPF User Plane Function
  • SMF performs data flow detection (based on filter definitions included in PCC rules), online and offline charging interactions, and policy enforcement.
  • Charging Function (CHF, with Nchf interface) is responsible for converged online charging and offline charging functionalities. It provides quota management (for online charging), re-authorization triggers, rating conditions, etc. and is notified about usage reports from the SMF. Quota management involves granting a specific number of units (e.g., bytes, seconds) for a service. CHF also interacts with billing systems. Access and Mobility Management Function (AMF 220, with Namf interface) terminates the RAN CP interface and handles all mobility and connection management of UEs (similar to MME in EPC). AMFs communicate with UEs (e.g., UE 210) via the N1 reference point and with the RAN (e.g., NG-RAN) via the N2 reference point.
  • AMF 220 Access and Mobility Management Function
  • Network Exposure Function (NEF, with Nnef interface)acts as the entry point into operator's network, by securely exposing to AFs the network capabilities and events provided by 3GPP NFs and by providing ways for the AF to securely provide information to 3GPP network.
  • NEF provides a service that allows an AF to provision specific subscription data (e.g., expected UE behavior) for various UEs.
  • Network Repository Function provides service registration and discovery, enabling NFs to identify appropriate services available from other NFs.
  • Network Slice Selection Function enables other NFs (e.g., AMF) to identify a network slice instance that is appropriate for a UE’s desired service.
  • a “network slice” is a logical partition of a 5G network that provides specific network capabilities and characteristics, e.g., in support of a particular service.
  • a network slice instance is a set of NF instances and the required network resources (e.g., compute, storage, communication) that provide the capabilities and characteristics of the network slice.
  • NSSAAF 230 Network Slice Specific Authentication and Authorization Function
  • AAA-S AAA Server
  • AAA-P AAA proxy
  • AUSF Authentication Server Function
  • HPLMN home network
  • Location Management Function supports various functions related to determination of UE locations, including location determination for a UE and obtaining any of the following: DL location measurements or a location estimate from the UE; UL location measurements from the NG RAN; and non-UE associated assistance data from the NG RAN.
  • Unified Data Management function supports generation of 3GPP authentication credentials, user identification handling, access authorization based on subscription data, and other subscriber-related functions.
  • the UDM uses subscription data (including authentication data) stored in the 5GC unified data repository (UDR).
  • the UDR supports storage and retrieval of policy data by the PCF, as well as storage and retrieval of application data by NEF.
  • Communication links between the UE and a 5G network can be grouped in two different strata.
  • the UE communicates with the CN over the Non-Access Stratum (NAS), and with the AN over the Access Stratum (AS). All the NAS communication takes place between the UE and the AMF via the NAS protocol (N1 interface in Figure 2).
  • Security for the communications over this these strata is provided by the NAS protocol (for NAS) and the PDCP protocol (for AS).
  • 3 GPP Rel-16 introduces a new feature called authentication and key management for applications (AKMA) that is based on 3GPP user credentials in 5G, including the Internet of Things (loT) use case. More specifically, AKMA leverages the user’s AKA (Authentication and Key Agreement) credentials to bootstrap security between the UE and an application function (AF), which allows the UE to securely exchange data with an application server.
  • the AKMA architecture can be considered an evolution of GBA (Generic Bootstrapping Architecture) specified for 5GC in 3GPP Rel-15 and is further specified in 3GPP TS 33.535 (vl6.0.0).
  • GBA Generic Bootstrapping Architecture
  • Rel-16 AKMA also utilizes an anchor function for authentication and key management for applications (AAnF). This function is shown in Figure 2 with Naanf interface. In general, AAnF interacts with AUSFs and maintains UE AKMA contexts to be used for subsequent bootstrapping requests, e.g., by application functions. At a high level, AAnF is similar to a bootstrapping server function (BSF) defined for Rel-15 GBA.
  • BSF bootstrapping server function
  • 3GPP TS 33.501 (vl6.3.0) specifies these keys in the organized hierarchy shown in Figure 3. At the top is the long-term key part of the authentication credential and stored in the SIM card on the UE side and in the UDM/ARPF in the UE’s Home Public Land Mobile Network (HPLMN).
  • HPLMN Home Public Land Mobile Network
  • KAUSF the second level key in the hierarchy. This key is not intended to leave the HPLMN and is used to secure the exchange of information between UE and HPLMN, such as for the provisioning of parameters to the UE from UDM in HPLMN. More precisely, KAUSF is used for integrity protection of messages delivered from HPLMN to UE. As described in 3GPP TS 33.501 (vl6.3.0), such new features include the Steering of Roaming (SoR) and the UDM parameter delivery procedures.
  • SoR Steering of Roaming
  • KAUSF is used to derive another key, KSEAF, that is sent to the serving PLMN.
  • KSEAF another key
  • the serving PLMN key is then used to derive the subsequent NAS and AS protection keys.
  • These lower level keys together with other security parameters constitute what is defined in 3 GPP TS 33.501 (v 16.3.0) as the 5 G security context.
  • KAUSF is not part of the UE’s 5G security context that resides in the UE’s serving PLMN.
  • NPNs can be deployed as Stand-alone NPNs (SNPN) when they do not rely on network functions provided by a PLMN. Alternately, NPNs can be deployed as Public Network Integrated NPNs (PNI-NPNs) when they rely on functions provided by a PLMN.
  • SNPN Stand-alone NPNs
  • PNI-NPNs Public Network Integrated NPNs
  • Rel-16 enhancements specified for SNPNs include updates to the primary authentication procedures used by UEs to add support for any key-generating extensible authentication protocol (EAP) methods.
  • Figure 4 shows a high-level view of a key hierarchy that excludes keys from outside the EAP-protocol realm.
  • KAUSF is derived from authentication credentials that are specific to the EAP method. More specifically, KAUSF is derived from an extended master session key (EMSK) resulting from EAP procedures.
  • EMSK extended master session key
  • 3GPP is currently working on further enhancements to NPN supporting Rel-17.
  • UE authentication procedures that allow UEs to be authenticated by an external entity to the SNPN.
  • This architectural study work is captured in 3GPP TR 23.700-07 (v0.4.0), and is based on the following terminology:
  • Default UE credentials Information that the UE have before the actual onboarding procedure to make it uniquely identifiable and verifiably secure.
  • DCS Default Credential Server
  • NPN credentials Information that the UE uses for authentication to access an NPN, which may be 3GPP credentials or non-3GPP credentials.
  • Onboarding Network The network providing initial registration and/or access to the UE for UE Onboarding.
  • Provisioning Server The server that provisions the authenticated/authorized UE with the subscription data and optionally other configuration information.
  • Subscription Owner The entity that stores and as result of the UE Onboarding procedures provide the subscription data and optionally other configuration information via the PS to the UE.
  • UE Onboarding Provisioning of information, to a UE and within the network, required for the UE to get authorized access and connectivity to an NPN.
  • Unique UE identifier Identifying the UE in the network and the DCS and is assigned and configured by the DCS.
  • One of the use cases of delegated authentication is UE onboarding.
  • the onboarding network relies on an external DCS to grant temporary access and connectivity to UEs for onboarding.
  • the UE can use the new credentials to access the target NPN.
  • DCS is required to support the AAA-S functionality.
  • new features requiring authentication services to assume support for AAA functionalities and protocols, due to their wide use and deployment. This would simplify integration and pave the way for wider adoption.
  • Embodiments of the present disclosure address these and other problems, issues, and/or difficulties by providing techniques that facilitate establishment of security keys between a UE and a network based on execution of Network Slice Specific Authentication and Authorization (NSSAA) procedures using an external entity such as the DCS acting as AAA-S and without any involvement from the AUSF.
  • NSSAA Network Slice Specific Authentication and Authorization
  • Such embodiments can provide various benefits and/or advantages. For example, such techniques enable establishment of security keys for the protection of CP and UP traffic, but without impacting the UE’ s primary authentication procedure. Furthermore, such embodiments can reuse existing network procedures, thereby minimizing and/or reducing impact on new signaling and specification changes.
  • the external authenticating entity e.g., DCS
  • DCS external authenticating entity
  • embodiments utilize a Network Slice Specific Authentication (NSSA) procedure described in 3GPP TS 33.501 (vl6.3.0) section 16.3, in which the DCS assumes the role of AAA-S.
  • NSSA Network Slice Specific Authentication
  • embodiments utilize a key generating EAP method during the NSSA EAP procedure that results in establishment of an MSK key between the AMF and the UE.
  • embodiments use the MSK to derive the necessary keys for the protection of the CP and UP traffic.
  • Figure 5 shows a signal flow diagram of an exemplary NSSA procedure that results in key establishment, according to various exemplary embodiments of the present disclosure. Although the operations shown in Figure 5 are given numerical labels, these are meant to facilitate explanation and do not imply any strict temporal order of the operations, unless specifically noted otherwise.
  • the UE sends a Registration Request message to the AMF.
  • the UE includes an onboarding indication within the Registration Request. It is assumed here that the UE does not have credentials to be used for primary authentication with the network but rather only default credential that can be used for authentication via DCS.
  • the UE additionally may include requested Single Network Slice Selection Assistance Information (S-NSSAI) including an S-NSSAI related to onboarding.
  • S-NSSAI identifies a network slice and includes a Slice/Service type (SST), which refers to the expected Network Slice behavior in terms of features and services.
  • SST Slice/Service type
  • the S-NSSAI includes a Slice Differentiator (SD) that differentiates among multiple Network Slices having the same SST.
  • SD Slice Differentiator
  • the S-NSSAI may be associated with a PLMN (e.g., PLMN ID) and have network-specific values or have standard values.
  • An S-NSSAI can used by a UE in an access network of the PLMN with which the S-NSSAI is associated.
  • the network determines that primary authentication should be bypassed for this UE and that a network slice specific authentication and authorization (NSSAA) procedure is to be used instead following completion of UE Registration.
  • the network may also bypass other procedures such as AMF registration in UDM, since the onboarding UE is not a subscriber of the onboarding network.
  • the AMF sends a Registration Accept message and the UE optionally responds with the Registration Complete message.
  • the AMF initiates the NSSAA procedure with an NSSAAF of the onboarding network as defined in 3GPP TS 23.502 (vl6.5.0) and 33.501 (vl6.3.0).
  • the NSSAAF selects the appropriate external AAA-S acting as DCS based on the UE’s SUPI used during the onboarding procedure.
  • the SUPI used during onboarding procedures can be in NAI format and the realm of the SUPI can point to a specific DCS.
  • An exemplary SUPI according to these embodiments is UEid@UEvendorl .com, which would result in NSSAAF selecting a DCS corresponding to “UEvendorl”.
  • the SUPI used during the onboarding procedure can also be used as a “UEid” during the NSSAA procedure between the UE and the DCS/ AAA-S.
  • an EAP authentication procedure is performed between the UE and the DCS endorsing the role of the AAA-S through the AMF.
  • Conventional NSSAA procedures do not include generation of key material between the UE and the AAA-S.
  • the DCS upon a successful authentication in operation 4b, the DCS derives the MSK key and sends it to the AMF via the NSSAAF in operation 4c (so long as the EAP method used in DCS is key generating).
  • the AMF uses the received MSK to derive KAMF and triggers an NAS security mode command (SMC) procedure to establish and activate NAS security based on the newly derived KAMF.
  • SMC NAS security mode command
  • the AMF sends an NAS SMC message that optionally includes an indication that the UE should derive KAMF from the MSK resulting from the EAP run.
  • the UE derives KAMF from the MSK and activates NAS security based on the newly derived KAMF and further information received in the NAS SMC downlink message.
  • Figure 5 operation 2 can be realized in various ways according to various embodiments.
  • the onboarding indication provided by the UE during registration can be used by the AMF to bypass primary authentication for the UE and execute NSSAA procedures instead.
  • the UE can include a special NS SAI in the Registration Request that is dedicated for onboarding procedures and can also be used by the AMF for this purpose.
  • the network can be preconfigured to act on specific values from the SUCI signaled by the UE such as a particular routing indicator or a particular range of domain names in the SUPI in case it is in NAI format.
  • the AMF may take the decision to bypass primary authentication and execute NSSAA for a given UE based on a combination of the presence of the onboarding indication and the home network id of the SUPI/SUCI belonging to a DCS.
  • KAMF can be taken directly from the MSK, e.g., as the 256 most significant bytes of MSK.
  • KAMF can be derived from the MSK using a one-way function, e.g., the Key Derivation Function (KDF) specified in 3GPP TS 33.220 (v 16.1.0) and commonly used in 3GPP security mechanisms. This derivation can optionally use a freshness parameter (e.g., counter or nonce) as an additional input.
  • KDF Key Derivation Function
  • This derivation can optionally use a freshness parameter (e.g., counter or nonce) as an additional input.
  • both the AMF and the UE must perform the same operations for KAMF derivation in 5a and 5c, respectively.
  • Figure 5 operation 5b can be realized in various ways according to various embodiments.
  • the indication in the NAS SMC message can be explicit, e.g., a Boolean value indicating whether or not the UE should derive KAMF from the latest MSK resulting from a successful NSSA procedure.
  • the indication can be a freshness parameter (e.g., counter or nonce) used in the derivation, as described above.
  • no explicit indication is included in the NAS SMC message, i.e., the indication is implicit.
  • the UE retains the MSK (or the material used to derive the MSK) until an SMC message is received after the completion of the NSSA procedure, which triggers the UE to derive the keys using the MSK. If no NAS SMC is received after a predetermined duration, the UE disposes of the MSK and proceeds without activating NAS security.
  • the indication is based on whether or not the UE received the NAS SMC message (e.g., in Figure 5 operation 5b) within the predetermined duration after completion of the NSSA procedure.
  • Figures 6-9 depict exemplary methods (e.g., procedures) performed by a UE, an AMF, an NSSAAF, and a DCS, respectively.
  • various features of the operations described below correspond to various embodiments described above.
  • the exemplary methods shown in Figures 6-9 can be complementary to each other such that some or all of them can be used cooperatively to provide benefits, advantages, and/or solutions to problems described herein.
  • the exemplary methods are illustrated in Figures 6-9 by specific blocks in particular orders, the operations corresponding to the blocks can be performed in different orders than shown and can be combined and/or divided into blocks having different functionality than shown.
  • Optional blocks and/or operations are indicated by dashed lines.
  • Figure 6 illustrates an exemplary method (e.g., procedure) for a UE to establish security keys for communication with a non-public network (NPN), according to various embodiments of the present disclosure.
  • NPN non-public network
  • the exemplary method shown in Figure 6 can be performed by a UE (e.g., wireless device) described herein with reference to other figures.
  • the NPN can be a Stand-alone Non-Public Network (SNPN).
  • SNPN Stand-alone Non-Public Network
  • the exemplary method can include the operations of block 610, where the UE can send, to an AMF associated with the NPN, a registration request that includes a first indication that the UE is onboarding to NPN.
  • the exemplary method can also include the operations of block 620, where the UE can perform an authentication procedure, with a DCS external to the NPN, to obtain a master session key (MSK).
  • MSK master session key
  • the authentication procedure can be performed without involvement of an AUSF in the NPN.
  • the authentication procedure can be a network-slice-specific authentication and authorization (NSSAA) procedure.
  • NSSAA network-slice-specific authentication and authorization
  • the exemplary method can also include the operations of block 630, where the UE can, based on receiving a second indication from the AMF, derive security keys for communication between the UE and the NPN based on the MSK.
  • sending the registration request in block 610 is based on the operations of sub-block 611, where the UE determines that it (i.e., the UE) does not have credentials needed for primary authentication with the NPN (e.g., via an AUSF in the NPN).
  • the registration request can also include a S-NSSAI related to onboarding and/or a SUCI associated with the UE
  • the second indication from the AMF can be any of the following:
  • the exemplary method can also include the operations of block 640, where the UE can, based on not receiving the second indication from the AMF, refrain from deriving the security keys based on the MSK. For example, if the UE does not receive the SMC message from the AMF within the predetermined duration, the UE can refrain from deriving the security keys based on the MSK.
  • deriving security keys based on the MSK in block 630 can include the operations of sub-blocks 631-632, where the UE can, based on the MSK, derive a first security key (KAMF) for communication between the UE and the AMF and derive one or more second security keys based on KAMF.
  • KAMF first security key
  • An example of this key arrangement is illustrated in Figure 3, discussed above.
  • the UE can derive KA F based on the MSK in sub-block 632 according to one of the following operations: • taking a most-significant portion of the MSK as KAMF; or
  • a freshness parameter received as the second indication from the AMF, can be used as an additional input to the one-way key derivation function.
  • Figure 7 illustrates an exemplary method (e.g., procedure) for an AMF associated with an NPN to establish security keys for communication between a UE and the NPN, according to various embodiments of the present disclosure.
  • the exemplary method shown in Figure 7 can be performed by an AMF such as described elsewhere herein.
  • the NPN can be an SNPN.
  • the exemplary method can include the operations of block 710, where the AMF can receive, from the UE, a registration request that includes a first indication that the UE is onboarding to the NPN.
  • the exemplary method can also include the operations of block 720, where the AMF can determine that an NSSAA procedure should be used for this UE instead of a primary authentication procedure with the NPN.
  • the exemplary method can also include the operation of block 760, where the AMF can send, to the UE, a second indication the UE should derive security keys for communication between the UE and the NPN based on a MSK obtained by the UE from a DCS external to the NPN.
  • the second indication can be any of the following:
  • the registration request can also include a network slice identifier (S-NSSAI) related to onboarding and/or a SUCI associated with the UE.
  • S-NSSAI network slice identifier
  • the SUCI is not associated with any subscriptions to the NPN.
  • determining that the NSSAA procedure should be used can be based on the first indication, the SUCI, and/or the S-NSSAI, any of which may be included in the registration request.
  • the exemplary method can also include the operations of blocks 730-740, where the AMF can select an NSSAAF in the NPN based on the S-NSSAI and perform the NSSAA procedure with the selected NSSAAF to obtain the MSK.
  • performing the NSSAA procedure in block 740 can include the operations of sub-blocks 741-742.
  • the AMF can send, to the NSSAF, an authentication request for the UE.
  • the authentication request can include a UE identifier.
  • the AMF can receive the MSK from the AMF.
  • determining that the NSSAA procedure should be used is based on a SUPI associated with the UE.
  • the AMF can obtain the SUPI based on the SUCI included in the registration request (e.g., received in block 710).
  • the AMF can include the SUPI as the UE identifier in the authentication request sent in sub-block 741.
  • the exemplary method can also include the operations of block 750, where the AMF can, based on the MSK, derive a first security key (KAMF) for communication between the UE and the AMF.
  • the AMF can derive the first security key (KAMF) based on the MSK according to on one of the following operations:
  • a freshness parameter sent to the UE as the second indication (e.g., in block 760), can be used as an additional input to the one-way key derivation function.
  • Figure 8 illustrates an exemplary method (e.g., procedure) for an NSSAAF associated with an NPN to establish security keys for communication between a UE and the NPN, according to various embodiments of the present disclosure.
  • the exemplary method shown in Figure 8 can be performed by an NSSAAF such as described elsewhere herein.
  • the NPN can be an SNPN.
  • the exemplary method can include the operations of block 810, where the NSSAAF can receive, from an AMF associated with the NPN, an authentication request for the UE.
  • the authentication request can include a UE identifier, such as a SUPI associated with the UE.
  • the exemplary method can also include the operations of block 820, where the NSSAAF can select a DCS external to the NPN based on the UE identifier.
  • the exemplary method can also include the operation of block 830, where the NSSAAF can obtain, from the DCS, a MSK for communication between the UE and the NPN.
  • the exemplary method can also include the operations of block 840, where the NSSAAF can send the MSK to the AMF.
  • the UE identifier (e.g., SUPI) can include a network access identifier (NAI) that points to the selected DCS and/or a unique UE identifier used when obtaining the MSK from the DCS.
  • the UE identifier (e.g., SUPI) is not associated with any subscriptions to the NPN.
  • the NSSAAF can select the DCS external to the NPN (e.g., in block 820) based on the UE identifier not being associated with any subscriptions to the NPN.
  • Figure 9 illustrates an exemplary method (e.g., procedure) for establishing security keys for communication between a UE and an NPN, according to various embodiments of the present disclosure.
  • the exemplary method shown in Figure 9 can be performed by a DCS external to the NPN, such as described elsewhere herein.
  • the NPN can be an SNPN.
  • the exemplary method can include the operations of block 910, where the DCS can receive a request for authentication of the UE from a NSSAAF associated with the NPN.
  • the exemplary method can also include the operations of block 920, where the DCS can perform an authentication procedure, with the UE, to obtain a MSK for communication between the UE and the NPN.
  • the exemplary method can also include the operation of block 930, where the DCS can send the MSK to the NSSAAF.
  • the authentication procedure can be an extensible authentication procedure (EAP). In some embodiments, the authentication procedure can be performed without involvement of an AUSF in the NPN.
  • EAP extensible authentication procedure
  • a wireless network such as the example wireless network illustrated in Figure 10.
  • the wireless network of Figure 10 only depicts network 1006, network nodes 1060 and 1060b, and WDs 1010, 1010b, and 1010c.
  • a wireless network can further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device.
  • network node 1060 and wireless device (WD) 1010 are depicted with additional detail.
  • the wireless network can provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network.
  • the wireless network can comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system.
  • the wireless network can be configured to operate according to specific standards or other types of predefined rules or procedures.
  • particular embodiments of the wireless network can implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • WLAN wireless local area network
  • WiMax Worldwide Interoperability for Microwave Access
  • Bluetooth Z-Wave and/or ZigBee standards.
  • Network 1006 can comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.
  • PSTNs public switched telephone networks
  • WANs wide-area networks
  • LANs local area networks
  • WLANs wireless local area networks
  • wired networks wireless networks, metropolitan area networks, and other networks to enable communication between devices.
  • Network node 1060 and WD 1010 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network.
  • the wireless network can comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that can facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • 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)).
  • APs access points
  • BSs base stations
  • eNBs evolved Node Bs
  • gNBs NR NodeBs
  • Base stations can be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and can then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station can be a relay node or a relay donor node controlling a relay.
  • a network node can also include one or more (or all) parts of a distributed radio base station such as centralized digital units 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 can also be referred to as nodes in a distributed antenna system (DAS).
  • DAS distributed antenna system
  • network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • transmission points transmission nodes
  • MCEs multi-cell/multicast coordination entities
  • core network nodes e.g., MSCs, MMEs
  • O&M nodes e.g., OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.
  • network nodes can represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.
  • network node 1060 includes processing circuitry 1070, device readable medium 1080, interface 1090, auxiliary equipment 1084, power source 1086, power circuitry 1087, and antenna 1062.
  • network node 1060 illustrated in the example wireless network of Figure 10 can represent a device that includes the illustrated combination of hardware components, other embodiments can comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods and/or procedures disclosed herein.
  • network node 1060 can comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 1080 can comprise multiple separate hard drives as well as multiple RAM modules).
  • network node 1060 can be composed of multiple physically separate components (e.g., a NodeB component and an RNC component, or a BTS component and a BSC component, etc.), which can each have their own respective components.
  • network node 1060 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components can be shared among several network nodes.
  • a single RNC can control multiple NodeB’ s.
  • each unique NodeB and RNC pair can in some instances be considered a single separate network node.
  • network node 1060 can be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • Network node 1060 can also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1060, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies can be integrated into the same or different chip or set of chips and other components within network node 1060.
  • Processing circuitry 1070 can be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 1070 can include processing information obtained by processing circuitry 1070 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.
  • processing information obtained by processing circuitry 1070 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.
  • Processing circuitry 1070 can 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 various functionality of network node 1060, either alone or in conjunction with other network node 1060 components (e.g., device readable medium 1080). Such functionality can include any of the various wireless features, functions, or benefits discussed herein.
  • processing circuitry 1070 can execute instructions stored in device readable medium 1080 or in memory within processing circuitry 1070.
  • processing circuitry 1070 can include a system on a chip (SOC).
  • SOC system on a chip
  • instructions (also referred to as a computer program product) stored in medium 1080 can include instructions that, when executed by processing circuitry 1070, can configure network node 1060 to perform operations corresponding to various exemplary methods (e.g., procedures) described herein.
  • processing circuitry 1070 can include one or more of radio frequency (RF) transceiver circuitry 1072 and baseband processing circuitry 1074.
  • radio frequency (RF) transceiver circuitry 1072 and baseband processing circuitry 1074 can be on separate chips (or sets of chips), boards, or units, such as radio units and digital units.
  • part or all of RF transceiver circuitry 1072 and baseband processing circuitry 1074 can be on the same chip or set of chips, boards, or units
  • processing circuitry 1070 executing instructions stored on device readable medium 1080 or memory within processing circuitry 1070.
  • some or all of the functionality can be provided by processing circuitry 1070 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner.
  • processing circuitry 1070 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 1070 alone or to other components of network node 1060 but are enjoyed by network node 1060 as a whole, and/or by end users and the wireless network generally.
  • Device readable medium 1080 can 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 can be used by processing circuitry 1070.
  • 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
  • Device readable medium 1080 can store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 1070 and, utilized by network node 1060.
  • Device readable medium 1080 can be used to store any calculations made by processing circuitry 1070 and/or any data received via interface 1090.
  • processing circuitry 1070 and device readable medium 1080 can be considered to be integrated.
  • Interface 1090 is used in the wired or wireless communication of signaling and/or data between network node 1060, network 1006, and/or WDs 1010. As illustrated, interface 1090 comprises port(s)/terminal(s) 1094 to send and receive data, for example to and from network 1006 over a wired connection. Interface 1090 also includes radio front end circuitry 1092 that can be coupled to, or in certain embodiments a part of, antenna 1062. Radio front end circuitry 1092 comprises filters 1098 and amplifiers 1096. Radio front end circuitry 1092 can be connected to antenna 1062 and processing circuitry 1070. Radio front end circuitry can be configured to condition signals communicated between antenna 1062 and processing circuitry 1070.
  • Radio front end circuitry 1092 can receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 1092 can convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1098 and/or amplifiers 1096. The radio signal can then be transmitted via antenna 1062. Similarly, when receiving data, antenna 1062 can collect radio signals which are then converted into digital data by radio front end circuitry 1092. The digital data can be passed to processing circuitry 1070. In other embodiments, the interface can comprise different components and/or different combinations of components.
  • network node 1060 may not include separate radio front end circuitry 1092, instead, processing circuitry 1070 can comprise radio front end circuitry and can be connected to antenna 1062 without separate radio front end circuitry 1092.
  • processing circuitry 1070 can comprise radio front end circuitry and can be connected to antenna 1062 without separate radio front end circuitry 1092.
  • all or some of RF transceiver circuitry 1072 can be considered a part of interface 1090.
  • interface 1090 can include one or more ports or terminals 1094, radio front end circuitry 1092, and RF transceiver circuitry 1072, as part of a radio unit (not shown), and interface 1090 can communicate with baseband processing circuitry 1074, which is part of a digital unit (not shown).
  • Antenna 1062 can include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • Antenna 1062 can be coupled to radio front end circuitry 1090 and can be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • antenna 1062 can comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz.
  • An omni-directional antenna can be used to transmit/receive radio signals in any direction
  • a sector antenna can be used to transmit/receive radio signals from devices within a particular area
  • a panel antenna can be a line of sight antenna used to transmit/receive radio signals in a relatively straight line.
  • the use of more than one antenna can be referred to as MIMO.
  • antenna 1062 can be separate from network node 1060 and can be connectable to network node 1060 through an interface or port.
  • Antenna 1062, interface 1090, and/or processing circuitry 1070 can be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals can be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 1062, interface 1090, and/or processing circuitry 1070 can be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals can be transmitted to a wireless device, another network node and/or any other network equipment.
  • Power circuitry 1087 can comprise, or be coupled to, power management circuitry and can be configured to supply the components of network node 1060 with power for performing the functionality described herein. Power circuitry 1087 can receive power from power source 1086. Power source 1086 and/or power circuitry 1087 can be configured to provide power to the various components of network node 1060 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 1086 can either be included in, or external to, power circuitry 1087 and/or network node 1060.
  • network node 1060 can be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 1087.
  • power source 1086 can comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 1087. The battery can provide backup power should the external power source fail.
  • Other types of power sources such as photovoltaic devices, can also be used.
  • network node 1060 can include additional components beyond those shown in Figure 10 that can be responsible 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.
  • network node 1060 can include user interface equipment to allow and/or facilitate input of information into network node 1060 and to allow and/or facilitate output of information from network node 1060. This can allow and/or facilitate a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 1060.
  • a wireless device e.g., WD 1010
  • a wireless device can be configured to transmit and/or receive information without direct human interaction.
  • a WD can be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network.
  • Examples of a WD include, but are not limited to, smart phones, mobile phones, cell phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback appliances, wearable devices, wireless endpoints, mobile stations, tablets, laptops, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart devices, wireless customer-premise equipment (CPE), mobile-type communication (MTC) devices, Internet-of-Things (loT) devices, vehicle-mounted wireless terminal devices, etc.
  • VoIP voice over IP
  • PDAs personal digital assistants
  • LME laptop-embedded equipment
  • CPE wireless customer-premise equipment
  • MTC mobile-type communication
  • LoT Internet-of-Things
  • a WD can support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and can in this case be referred to as a D2D communication device.
  • D2D device-to-device
  • V2V vehicle-to-vehicle
  • V2I vehicle-to-infrastructure
  • V2X vehicle-to-everything
  • a WD can represent a machine or other device that performs monitoring and/or measurements and transmits the results of such monitoring and/or measurements to another WD and/or a network node.
  • the WD can in this case be a machine-to-machine (M2M) device, which can in a 3GPP context be referred to as an MTC device.
  • M2M machine-to-machine
  • the WD can be a UE implementing the 3 GPP narrow band internet of things (NB-IoT) standard.
  • NB-IoT narrow band internet of things
  • machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g., refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.).
  • a WD can represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • a WD as described above can represent the endpoint of a wireless connection, in which case the device can be referred to as a wireless terminal. Furthermore, a WD as described above can be mobile, in which case it can also be referred to as a mobile device or a mobile terminal.
  • wireless device 1010 includes antenna 1011, interface 1014, processing circuitry 1020, device readable medium 1030, user interface equipment 1032, auxiliary equipment 1034, power source 1036 and power circuitry 1037.
  • WD 1010 can include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 1010, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies can be integrated into the same or different chips or set of chips as other components within WD 1010.
  • Antenna 1011 can include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 1014.
  • antenna 1011 can be separate from WD 1010 and be connectable to WD 1010 through an interface or port.
  • Antenna 1011, interface 1014, and/or processing circuitry 1020 can be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals can be received from a network node and/or another WD.
  • radio front end circuitry and/or antenna 1011 can be considered an interface.
  • interface 1014 comprises radio front end circuitry 1012 and antenna 1011.
  • Radio front end circuitry 1012 comprise one or more filters 1018 and amplifiers 1016.
  • Radio front end circuitry 1014 is connected to antenna 1011 and processing circuitry 1020 and can be configured to condition signals communicated between antenna 1011 and processing circuitry 1020.
  • Radio front end circuitry 1012 can be coupled to or a part of antenna 1011.
  • WD 1010 may not include separate radio front end circuitry 1012; rather, processing circuitry 1020 can comprise radio front end circuitry and can be connected to antenna 1011.
  • some or all of RF transceiver circuitry 1022 can be considered a part of interface 1014.
  • Radio front end circuitry 1012 can receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 1012 can convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1018 and/or amplifiers 1016. The radio signal can then be transmitted via antenna 1011. Similarly, when receiving data, antenna 1011 can collect radio signals which are then converted into digital data by radio front end circuitry 1012. The digital data can be passed to processing circuitry 1020. In other embodiments, the interface can comprise different components and/or different combinations of components.
  • Processing circuitry 1020 can 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 WD 1010 functionality either alone or in combination with other WD 1010 components, such as device readable medium 1030.
  • 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 WD 1010 functionality either alone or in combination with other WD 1010 components, such as device readable medium 1030.
  • Such functionality can include any of the various wireless features or benefits discussed herein.
  • processing circuitry 1020 can execute instructions stored in device readable medium 1030 or in memory within processing circuitry 1020 to provide the functionality disclosed herein. More specifically, instructions (also referred to as a computer program product) stored in medium 1030 can include instructions that, when executed by processor 1020, can configure wireless device 1010 to perform operations corresponding to various exemplary methods (e.g., procedures) described herein. As illustrated, processing circuitry 1020 includes one or more of RF transceiver circuitry 1022, baseband processing circuitry 1024, and application processing circuitry 1026. In other embodiments, the processing circuitry can comprise different components and/or different combinations of components. In certain embodiments processing circuitry 1020 of WD 1010 can comprise a SOC.
  • RF transceiver circuitry 1022, baseband processing circuitry 1024, and application processing circuitry 1026 can be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry 1024 and application processing circuitry 1026 can be combined into one chip or set of chips, and RF transceiver circuitry 1022 can be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry 1022 and baseband processing circuitry 1024 can be on the same chip or set of chips, and application processing circuitry 1026 can be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry 1022, baseband processing circuitry 1024, and application processing circuitry 1026 can be combined in the same chip or set of chips.
  • RF transceiver circuitry 1022 can be a part of interface 1014.
  • RF transceiver circuitry 1022 can condition RF signals for processing circuitry 1020.
  • processing circuitry 1020 executing instructions stored on device readable medium 1030, which in certain embodiments can be a computer-readable storage medium.
  • some or all of the functionality can be provided by processing circuitry 1020 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner.
  • processing circuitry 1020 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 1020 alone or to other components of WD 1010, but are enjoyed by WD 1010 as a whole, and/or by end users and the wireless network generally.
  • Processing circuitry 1020 can be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 1020, can include processing information obtained by processing circuitry 1020 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 1010, 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.
  • Device readable medium 1030 can be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 1020.
  • Device readable medium 1030 can include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., 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 can be used by processing circuitry 1020.
  • processing circuitry 1020 and device readable medium 1030 can be considered to be integrated.
  • User interface equipment 1032 can include components that allow and/or facilitate a human user to interact with WD 1010. Such interaction can be of many forms, such as visual, audial, tactile, etc. User interface equipment 1032 can be operable to produce output to the user and to allow and/or facilitate the user to provide input to WD 1010. The type of interaction can vary depending on the type of user interface equipment 1032 installed in WD 1010. For example, if WD 1010 is a smart phone, the interaction can be via a touch screen; if WD 1010 is a smart meter, the interaction can be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected).
  • usage e.g., the number of gallons used
  • a speaker that provides an audible alert
  • User interface equipment 1032 can include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 1032 can be configured to allow and/or facilitate input of information into WD 1010 and is connected to processing circuitry 1020 to allow and/or facilitate processing circuitry 1020 to process the input information. User interface equipment 1032 can include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 1032 is also configured to allow and/or facilitate output of information from WD 1010, and to allow and/or facilitate processing circuitry 1020 to output information from WD 1010.
  • User interface equipment 1032 can include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 1032, WD 1010 can communicate with end users and/or the wireless network and allow and/or facilitate them to benefit from the functionality described herein.
  • Auxiliary equipment 1034 is operable to provide more specific functionality which may not be generally performed by WDs. This can comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 1034 can vary depending on the embodiment and/or scenario.
  • Power source 1036 can, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, can also be used.
  • WD 1010 can further comprise power circuitry 1037 for delivering power from power source 1036 to the various parts of WD 1010 which need power from power source 1036 to carry out any functionality described or indicated herein.
  • Power circuitry 1037 can in certain embodiments comprise power management circuitry. Power circuitry 1037 can additionally or alternatively be operable to receive power from an external power source; in which case WD 1010 can be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry 1037 can also in certain embodiments be operable to deliver power from an external power source to power source 1036. This can be, for example, for the charging of power source 1036. Power circuitry 1037 can perform any converting or other modification to the power from power source 1036 to make it suitable for supply to the respective components of WD 1010.
  • Figure 11 illustrates one embodiment of a UE in accordance with various aspects described herein.
  • a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE can 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).
  • a UE can represent a device that is not intended for sale to, or operation by, an end user but which can be associated with or operated for the benefit of a user (e.g., a smart power meter).
  • UE 1100 can be any UE identified by the 3 rd Generation Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • UE 1100 is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3 rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards.
  • 3GPP 3 rd Generation Partnership Project
  • the term WD and UE can be used interchangeable. Accordingly, although Figure 11 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.
  • UE 1100 includes processing circuitry 1101 that is operatively coupled to input/output interface 1105, radio frequency (RF) interface 1109, network connection interface 1111, memory 1115 including random access memory (RAM) 1117, read-only memory (ROM) 1119, and storage medium 1121 or the like, communication subsystem 1131, power source 1133, and/or any other component, or any combination thereof.
  • Storage medium 1121 includes operating system 1123, application program 1125, and data 1127. In other embodiments, storage medium 1121 can include other similar types of information.
  • Certain UEs can utilize all of the components shown in Figure 11, or only a subset of the components. The level of integration between the components can vary from one UE to another UE. Further, certain UEs can contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • processing circuitry 1101 can be configured to process computer instructions and data.
  • Processing circuitry 1101 can be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above.
  • the processing circuitry 1101 can include two central processing units (CPUs). Data can be information in a form suitable for use by a computer.
  • input/output interface 1105 can be configured to provide a communication interface to an input device, output device, or input and output device.
  • UE 1100 can be configured to use an output device via input/output interface 1105.
  • An output device can use the same type of interface port as an input device.
  • a USB port can be used to provide input to and output from UE 1100.
  • the output device can be 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.
  • UE 1100 can be configured to use an input device via input/output interface 1105 to allow and/or facilitate a user to capture information into UE 1100.
  • the input device can 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 presencesensitive display can include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor can be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof.
  • the input device can be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.
  • RF interface 1109 can be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna.
  • Network connection interface 1111 can be configured to provide a communication interface to network 1143a.
  • Network 1143a can encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • network 1143a can comprise a Wi-Fi network.
  • Network connection interface t i l l can be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like.
  • Network connection interface 1111 can implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions can share circuit components, software or firmware, or alternatively can be implemented separately.
  • RAM 1117 can be configured to interface via bus 1102 to processing circuitry 1101 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers.
  • ROM 1119 can be configured to provide computer instructions or data to processing circuitry 1101.
  • ROM 1119 can be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory.
  • Storage medium 1121 can be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives.
  • memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives.
  • storage medium 1121 can be configured to include operating system 1123; application program 1125 such as a web browser application, a widget or gadget engine or another application; and data file 1127.
  • Storage medium 1121 can store, for use by UE 1100, any of a variety of various operating systems or combinations of operating systems.
  • application program 1125 can include executable program instructions (also referred to as a computer program product) that, when executed by processor 1101, can configure UE 1100 to perform operations corresponding to various exemplary methods (e.g., procedures) described herein.
  • Storage medium 1121 can be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, 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 microDIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof.
  • RAID redundant array of independent disks
  • HD-DVD high-density digital versatile disc
  • HDDS holographic digital data storage
  • DIMM external mini-dual in-line memory module
  • SDRAM synchronous dynamic random access memory
  • SIM/RUIM removable user identity
  • Storage medium 1121 can allow and/or facilitate UE 1100 to access computer-executable instructions, application programs or 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 can be tangibly embodied in storage medium 1121, which can comprise a device readable medium.
  • processing circuitry 1101 can be configured to communicate with network 1143b using communication subsystem 1131.
  • Network 1143a and network 1143b can be the same network or networks or different network or networks.
  • Communication subsystem 1131 can be configured to include one or more transceivers used to communicate with network 1143b.
  • communication subsystem 1131 can be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.11, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like.
  • RAN radio access network
  • Each transceiver can include transmitter 1133 and/or receiver 1135 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 1133 and receiver 1135 of each transceiver can share circuit components, software or firmware, or alternatively can be implemented separately.
  • the communication functions of communication subsystem 1131 can include 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.
  • communication subsystem 1131 can include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication.
  • Network 1143b can encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • network 1143b can be a cellular network, a Wi-Fi network, and/or a near- field network.
  • Power source 1113 can be configured to provide alternating current (AC) or direct current (DC) power to components of UE 1100.
  • communication subsystem 1131 can be configured to include any of the components described herein.
  • processing circuitry 1101 can be configured to communicate with any of such components over bus 1102.
  • any of such components can be represented by program instructions stored in memory that when executed by processing circuitry 1101 perform the corresponding functions described herein.
  • the functionality of any of such components can be partitioned between processing circuitry 1101 and communication subsystem 1131.
  • the non-computationally intensive functions of any of such components can be implemented in software or firmware and the computationally intensive functions can be implemented in hardware.
  • FIG 12 is a schematic block diagram illustrating a virtualization environment 1200 in which functions implemented by some embodiments can be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which can include virtualizing hardware platforms, storage devices and networking resources.
  • virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) 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 (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).
  • a node e.g., a virtualized base station or a virtualized radio access node
  • a device e.g., a UE, a wireless device or any other type of communication device
  • some or all of the functions described herein can be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 1200 hosted by one or more of hardware nodes 1230. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node can be entirely virtualized.
  • the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node)
  • the network node can be entirely virtualized.
  • the functions can be implemented by one or more applications 1220 (which can alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Applications 1220 are run in virtualization environment 1200 which provides hardware 1230 comprising processing circuitry 1260 and memory 1290.
  • Memory 1290 contains instructions 1295 executable by processing circuitry 1260 whereby application 1220 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.
  • Virtualization environment 1200 can include general-purpose or special-purpose network hardware devices (or nodes) 1230 comprising a set of one or more processors or processing circuitry 1260, which can be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors.
  • Each hardware device can comprise memory 1290-1 which can be non-persistent memory for temporarily storing instructions 1295 or software executed by processing circuitry 1260.
  • instructions 1295 can include program instructions (also referred to as a computer program product) that, when executed by processing circuitry 1260, can configure hardware node 1220 to perform operations corresponding to various exemplary methods (e.g., procedures) described herein. Such operations can also be attributed to virtual node(s) 1220 that is/are hosted by hardware node 1230.
  • Each hardware device can comprise one or more network interface controllers (NICs) 1270, also known as network interface cards, which include physical network interface 1280.
  • NICs network interface controllers
  • Each hardware device can also include non-transitory, persistent, machine-readable storage media 1290-2 having stored therein software 1295 and/or instructions executable by processing circuitry 1260.
  • Software 1295 can include any type of software including software for instantiating one or more virtualization layers 1250 (also referred to as hypervisors), software to execute virtual machines 1240 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.
  • Virtual machines 1240 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and can be run by a corresponding virtualization layer 1250 or hypervisor. Different embodiments of the instance of virtual appliance 1220 can be implemented on one or more of virtual machines 1240, and the implementations can be made in different ways.
  • processing circuitry 1260 executes software 1295 to instantiate the hypervisor or virtualization layer 1250, which can sometimes be referred to as a virtual machine monitor (VMM).
  • VMM virtual machine monitor
  • Virtualization layer 1250 can present a virtual operating platform that appears like networking hardware to virtual machine 1240.
  • hardware 1230 can be a standalone network node with generic or specific components.
  • Hardware 1230 can comprise antenna 12225 and can implement some functions via virtualization.
  • hardware 1230 can be part of a larger cluster of hardware (e.g., such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) 12100, which, among others, oversees lifecycle management of applications 1220.
  • CPE customer premise equipment
  • NFV network function virtualization
  • NFV can 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.
  • virtual machine 1240 can be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each of virtual machines 1240, and that part of hardware 1230 that executes that virtual machine be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 1240, forms a separate virtual network elements (VNE).
  • VNE virtual network elements
  • VNF Virtual Network Function
  • one or more radio units 12200 that each include one or more transmitters 12220 and one or more receivers 12210 can be coupled to one or more antennas 12225.
  • Radio units 12200 can communicate directly with hardware nodes 1230 via one or more appropriate network interfaces and can 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. Nodes arranged in this manner can also communicate with one or more UEs, such as described elsewhere herein.
  • control system 12230 can alternatively be used for communication between the hardware nodes 1230 and radio units 12200.
  • a communication system includes telecommunication network 1310, such as a 3GPP-type cellular network, which comprises access network 1311, such as a radio access network, and core network 1314.
  • Access network 1311 comprises a plurality of base stations 1312a, 1312b, 1312c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 1313a, 1313b, 1313c.
  • Each base station 1312a, 1312b, 1312c is connectable to core network 1314 over a wired or wireless connection 1315.
  • a first UE 1391 located in coverage area 1313c can be configured to wirelessly connect to, or be paged by, the corresponding base station 1312c.
  • a second UE 1392 in coverage area 1313a is wirelessly connectable to the corresponding base station 1312a. While a plurality of UEs 1391, 1392 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the
  • Telecommunication network 1310 is itself connected to host computer 1330, which can be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm.
  • Host computer 1330 can be under the ownership or control of a service provider or can be operated by the service provider or on behalf of the service provider.
  • Connections 1321 and 1322 between telecommunication network 1310 and host computer 1330 can extend directly from core network 1314 to host computer 1330 or can go via an optional intermediate network 1320.
  • Intermediate network 1320 can be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 1320, if any, can be a backbone network or the Internet; in particular, intermediate network 1320 can comprise two or more sub-networks (not shown).
  • the communication system of Figure 13 as a whole enables connectivity between the connected UEs 1391, 1392 and host computer 1330.
  • the connectivity can be described as an over-the-top (OTT) connection 1350.
  • Host computer 1330 and the connected UEs 1391, 1392 are configured to communicate data and/or signaling via OTT connection 1350, using access network 1311, core network 1314, any intermediate network 1320 and possible further infrastructure (not shown) as intermediaries.
  • OTT connection 1350 can be transparent in the sense that the participating communication devices through which OTT connection 1350 passes are unaware of routing of uplink and downlink communications.
  • base station 1312 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 1330 to be forwarded (e.g., handed over) to a connected UE 1391. Similarly, base station 1312 need not be aware of the future routing of an outgoing uplink communication originating from the UE 1391 towards the host computer 1330.
  • host computer 1410 comprises hardware 1415 including communication interface 1416 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 1400.
  • Host computer 1410 further comprises processing circuitry 1418, which can have storage and/or processing capabilities.
  • processing circuitry 1418 can comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Host computer 1410 further comprises software 1411, which is stored in or accessible by host computer 1410 and executable by processing circuitry 1418.
  • Software 1411 includes host application 1412.
  • Host application 1412 can be operable to provide a service to a remote user, such as UE 1430 connecting via OTT connection 1450 terminating at UE 1430 and host computer 1410. In providing the service to the remote user, host application 1412 can provide user data which is transmitted using OTT connection 1450.
  • Communication system 1400 can also include base station 1420 provided in a telecommunication system and comprising hardware 1425 enabling it to communicate with host computer 1410 and with UE 1430.
  • Hardware 1425 can include communication interface 1426 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 1400, as well as radio interface 1427 for setting up and maintaining at least wireless connection 1470 with UE 1430 located in a coverage area (not shown in Figure 14) served by base station 1420.
  • Communication interface 1426 can be configured to facilitate connection 1460 to host computer 1410. Connection 1460 can be direct, or it can pass through a core network (not shown in Figure 14) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system.
  • hardware 1425 of base station 1420 can also include processing circuitry 1428, which can comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Base station 1420 also includes software 1421 stored internally or accessible via an external connection.
  • software 1421 can include program instructions (also referred to as a computer program product) that, when executed by processing circuitry 1428, can configure base station 1420 to perform operations corresponding to various exemplary methods (e.g., procedures) described herein.
  • Communication system 1400 can also include UE 1430 already referred to, whose hardware 1435 can include radio interface 1437 configured to set up and maintain wireless connection 1470 with a base station serving a coverage area in which UE 1430 is currently located.
  • Hardware 1435 of UE 1430 can also include processing circuitry 1438, which can comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • UE 1430 also includes software 1431, which is stored in or accessible by UE 1430 and executable by processing circuitry 1438.
  • Software 1431 includes client application 1432.
  • Client application 1432 can be operable to provide a service to a human or non-human user via UE 1430, with the support of host computer 1410.
  • an executing host application 1412 can communicate with the executing client application 1432 via OTT connection 1450 terminating at UE 1430 and host computer 1410.
  • client application 1432 can receive request data from host application 1412 and provide user data in response to the request data.
  • OTT connection 1450 can transfer both the request data and the user data.
  • Client application 1432 can interact with the user to generate the user data that it provides.
  • Software 1431 can also include program instructions (also referred to as a computer program product) that, when executed by processing circuitry 1438, can configure UE 1430 to perform operations corresponding to various exemplary methods (e.g., procedures) described herein.
  • host computer 1410, base station 1420 and UE 1430 illustrated in Figure 14 can be similar or identical to host computer 1330, one of base stations 1312a, 1312b, 1312c and one of UEs 1391, 1392 of Figure 13, respectively.
  • the inner workings of these entities can be as shown in Figure 14 and independently, the surrounding network topology can be that of Figure 13.
  • OTT connection 1450 has been drawn abstractly to illustrate the communication between host computer 1410 and UE 1430 via base station 1420, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure can determine the routing, which it can be configured to hide from UE
  • OTT connection 1450 the network infrastructure can further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • Wireless connection 1470 between UE 1430 and base station 1420 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to UE 1430 using OTT connection 1450, in which wireless connection 1470 forms the last segment.
  • the exemplary embodiments disclosed herein can improve flexibility for the network to monitor end- to-end quality-of-service (QoS) of data flows, including their corresponding radio bearers, associated with data sessions between a user equipment (UE) and another entity, such as an OTT data application or service external to the 5G network.
  • QoS quality-of-service
  • a measurement procedure can be provided for the purpose of monitoring data rate, latency and other network operational aspects on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring OTT connection 1450 can be implemented in software 1411 and hardware 1415 of host computer 1410 or in software
  • sensors can be deployed in or in association with communication devices through which OTT connection 1450 passes; the sensors can participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 1411, 1431 can compute or estimate the monitored quantities.
  • the reconfiguring of OTT connection 1450 can include message format, retransmission settings, preferred routing etc.,- the reconfiguring need not affect base station 1420, and it can be unknown or imperceptible to base station 1420. Such procedures and functionalities can be known and practiced in the art.
  • measurements can involve proprietary UE signaling facilitating host computer 1410’s measurements of throughput, propagation times, latency and the like.
  • the measurements can be implemented in that software 1411 and 1431 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 1450 while it monitors propagation times, errors, etc.
  • FIG. 15 is a flowchart illustrating an exemplary method and/or procedure implemented in a communication system, in accordance with some embodiments.
  • the communication system includes a host computer, a base station and a UE which, in some exemplary embodiments, can be those described with reference to other figures herein. For simplicity of the present disclosure, only drawing references to Figure 15 will be included in this section.
  • the host computer provides user data.
  • substep 1511 (which can be optional) of step 1510, the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE.
  • step 1530 the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step 1540 the UE executes a client application associated with the host application executed by the host computer.
  • FIG 16 is a flowchart illustrating an exemplary method and/or procedure implemented in a communication system, in accordance with some embodiments.
  • the communication system includes a host computer, a base station and a UE which can be those described with reference to other figures herein. For simplicity of the present disclosure, only drawing references to Figure 16 will be included in this section.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE.
  • the transmission can pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step 1630 (which can be optional), the UE receives the user data carried in the transmission.
  • FIG 17 is a flowchart illustrating an exemplary method and/or procedure implemented in a communication system, in accordance with some embodiments.
  • the communication system includes a host computer, a base station and a UE which can be those described with reference to other figures herein. For simplicity of the present disclosure, only drawing references to Figure 17 will be included in this section.
  • step 1710 the UE receives input data provided by the host computer. Additionally or alternatively, in step 1720, the UE provides user data.
  • substep 1721 (which can be optional) of step 1720, the UE provides the user data by executing a client application.
  • substep 1711 (which can be optional) of step 1710, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer.
  • the executed client application can further consider user input received from the user.
  • the UE initiates, in substep 1730 (which can be optional), transmission of the user data to the host computer.
  • step 1740 of the method the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.
  • FIG. 18 is a flowchart illustrating an exemplary method and/or procedure implemented in a communication system, in accordance with some embodiments.
  • the communication system includes a host computer, a base station and a UE which can be those described with reference to other figures herein. For simplicity of the present disclosure, only drawing references to Figure 18 will be included in this section.
  • the base station receives user data from the UE.
  • the base station initiates transmission of the received user data to the host computer.
  • step 1830 (which can be optional)
  • the host computer receives the user data carried in the transmission initiated by the base station.
  • the term unit can have conventional meaning in the field of electronics, electrical devices and/or electronic devices and can include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses.
  • Each virtual apparatus may comprise a number of these functional units.
  • These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processor (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 (RAM), cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes 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.
  • the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.
  • device and/or apparatus can be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of a device or apparatus, instead of being hardware implemented, be implemented as a software module such as a computer program or a computer program product comprising executable software code portions for execution or being run on a processor.
  • functionality of a device or apparatus can be implemented by any combination of hardware and software.
  • a device or apparatus can also be regarded as an assembly of multiple devices and/or apparatuses, whether functionally in cooperation with or independently of each other.
  • devices and apparatuses can be implemented in a distributed fashion throughout a system, so long as the functionality of the device or apparatus is preserved. Such and similar principles are considered as known to a skilled person.
  • Example embodiments of the techniques and apparatus described herein include, but are not limited to, the following enumerated embodiments: Al .
  • AMF access and mobility management function
  • MSK master session key
  • the registration request also includes one or more of the following: a network slice identifier (S-NSSAI) related to onboarding; and information associated with a subscription permanent identifier (SUPI) of the UE.
  • S-NSSAI network slice identifier
  • SUPI subscription permanent identifier
  • the second indication from the AMF is one of the following: an explicit indication, received in a security mode command (SMC) message from the AMF, of whether or not the UE should derive security keys from the MSK; a freshness parameter received in the SMC message from the AMF; or an implicit indication based on receiving the SMC message from the AMF within a predetermined duration after obtaining the MSK.
  • SMC security mode command
  • deriving security keys based on the MSK comprises: based on the MSK, deriving a first security key (KAMF) for communication between the UE and the AMF; and deriving one or more second security keys based on KAMF.
  • KAMF first security key
  • deriving KA F based on the MSK comprises one of the following operations: taking a most-significant portion of the MSK as KAMF; or applying a one-way key derivation function to the MSK to generate KAMF.
  • A10 The method of any of embodiments A1-A9, wherein the authentication procedure is performed without involvement of an authentication support function (AUSF) in the NPN.
  • AUSF authentication support function
  • a method for an access and mobility management function (AMF) associated with a non-public network (NPN), for establishing security keys for communication between a user equipment (UE) and the NPN, the method comprising: receiving, from the UE, a registration request that includes a first indication that the UE is onboarding to the NPN; determining that a network-slice-specific authentication and authorization (NSSAA) procedure should be used for this UE instead of a primary authentication procedure with the NPN; and sending, to the UE, a second indication the UE should derive security keys for communication between the UE and the NPN based on a master session key (MSK) obtained by the UE from a default credential server (DCS) external to the NPN.
  • MSK master session key
  • DCS default credential server
  • the registration request also includes one or more of the following: a network slice identifier (S-NSSAI) related to onboarding; and information associated with a subscription permanent identifier (SUPI) of the UE.
  • S-NSSAI network slice identifier
  • SUPI subscription permanent identifier
  • determining that the NSSAA procedure should be used is based on one or more of the following: the first indication, the information associated with the SUPI, and the S-NSSAI; and the method further comprises: selecting a NSSAA function (NSSAAF) in the NPN based on the S-NSSAI; and performing the NSSAA procedure with the selected NSSAAF to obtain the MSK.
  • NSSAAF NSSAA function
  • performing the NSSA procedure comprises: sending, to the NSSAF, an authentication request for the UE, wherein the authentication request includes the SUPI of the UE; receiving the MSK from the AMF.
  • deriving KAMF based on the MSK comprises one of the following operations: taking a most-significant portion of the MSK as KA F; or applying a one-way key derivation function to the MSK to generate KAMF.
  • BIO The method of any of embodiments B1-B9, wherein the second indication is one of the following: an explicit indication, sent in a security mode command (SMC) message to the UE, of whether or not the UE should derive security keys from the MSK; a freshness parameter sent in the SMC message to the UE; or an implicit indication based on the UE receiving the SMC message from the AMF within a predetermined duration after the UE obtains the MSK from the DCS. Cl .
  • SMC security mode command
  • NSSAAF non-public network
  • NPN non-public network
  • the method comprising: receiving, from an access and mobility management function (AMF) associated with the NPN, an authentication request for the UE, wherein the authentication request includes a subscription permanent identifier (SUPI) associated with the UE; selecting a default credential server (DCS) external to the NPN based on the SUPI; obtaining, from the DCS, a master session key (MSK) for communication between the UE and the NPN; and sending the MSK to the AMF.
  • AMF access and mobility management function
  • SUPI subscription permanent identifier
  • DCS default credential server
  • MSK master session key
  • the SUPI includes one or more of the following: a network access identifier (NAI) that points to the selected DCS; and a unique UE identifier used when obtaining the MSK from the DCS.
  • NAI network access identifier
  • NSSAAF network-slice-specific authentication and authorization function
  • a user equipment configured to establish security keys for communication with a non-public network (NPN), the UE comprising: radio interface circuitry configured to communicate with an access and mobility management function (AMF) associated with the NPN and with a default credential server (DCS) external to the NPN; and processing circuitry operably coupled to the radio interface circuitry, whereby the processing circuitry and radio interface circuitry are configured to perform operations corresponding to any of the methods of embodiments A1-A10.
  • AMF access and mobility management function
  • DCS default credential server
  • a user equipment configured to establish security keys for communication with a non-public network (NPN), the UE being arranged to perform operations corresponding to any of the methods of embodiments A1-A10.
  • NPN non-public network
  • a non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of a user equipment (UE), configure the UE to perform operations corresponding to any of the methods of embodiments A1-A10.
  • UE user equipment
  • a computer program product comprising computer-executable instructions that, when executed by processing circuitry of a user equipment (UE), configure the UE to perform operations corresponding to any of the methods of embodiments A1-A10.
  • UE user equipment
  • AMF access and mobility management function associated with a non-public network (NPN)
  • NPN non-public network
  • the AMF comprising: interface circuitry configured to communicate with user equipment (UEs) and with a network-slice-specific authentication and authorization function (NSSAAF) associated with the NPN; and processing circuitry operably coupled to the interface circuitry, whereby the processing circuitry and interface circuitry are configured to perform operations corresponding to any of the methods of embodiments Bl -BIO.
  • UEs user equipment
  • NSSAAF network-slice-specific authentication and authorization function
  • a non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry associated with an access and mobility management function (AMF) of a non-public network (NPN), configure the AMF to perform operations corresponding to any of the methods of embodiments Bl -B10.
  • a computer program product comprising computer-executable instructions that, when executed by processing circuitry associated with an access and mobility management function (AMF) of a non-public network (NPN), configure the AMF to perform operations corresponding to any of the methods of embodiments Bl -B10.
  • AMF access and mobility management function
  • NPN non-public network
  • NSSAAF network-slice-specific authentication and authorization function associated with a non-public network
  • AMF access and mobility management function
  • DCS default credential server
  • NSSAAF network-slice-specific authentication and authorization function associated with a non-public network (NPN), the NSSAAF being arranged to perform operations corresponding to any of the methods of embodiments C1-C3.
  • a non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry associated with a network-slice-specific authentication and authorization function (NSSAAF) of a non-public network (NPN), configure the NSSAAF to perform operations corresponding to any of the methods of embodiments Cl- C3.
  • NSSAAF network-slice-specific authentication and authorization function
  • NPN non-public network
  • a computer program product comprising computer-executable instructions that, when executed by processing circuitry associated with a network-slice-specific authentication and authorization function (NSSAAF) of a non-public network (NPN), configure the NSSAAF to perform operations corresponding to any of the methods of embodiments C1-C3. Hl .
  • NSSAAF network-slice-specific authentication and authorization function
  • NPN non-public network
  • a default credential server configured to establishing security keys for communication between a user equipment (UE) and a non-public network (NPN), the DCS being external to the NPN and comprising: interface circuitry configured to communicate with user equipment (UEs) and with a network-slice-specific authentication and authorization function (NSSAAF) associated with the NPN; and processing circuitry operably coupled to the interface circuitry, whereby the processing circuitry and interface circuitry are configured to perform operations corresponding to any of the methods of embodiments D1-D3.
  • DCS credential server
  • UEs user equipment
  • NSSAAF network-slice-specific authentication and authorization function
  • a default credential server configured to establishing security keys for communication between a user equipment (UE) and a non-public network (NPN), the DCS being external to the NPN and being further arranged to perform operations corresponding to any of the methods of embodiments D1-D3.
  • a non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry associated with a default credential server (DCS) external to a non-public network (NPN), configure the DCS to perform operations corresponding to any of the methods of embodiments D1-D3.
  • DCS default credential server
  • NPN non-public network
  • a computer program product comprising computer-executable instructions that, when executed by processing circuitry associated with a default credential server (DCS) external to a non-public network (NPN), configure the DCS to perform operations corresponding to any of the methods of embodiments D1-D3.
  • DCS default credential server
  • NPN non-public network

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Selon certains modes de réalisation concernent des procédés permettant à un équipement utilisateur (UE) d'établir des clés de sécurité pour une communication avec un réseau non public (NPN). De tels procédés consistent à envoyer à une fonction de gestion d'accès et de mobilité (AMF) associée au NPN, une demande d'enregistrement qui comprend une première indication selon laquelle l'UE est intégré au NPN. De tels procédés consistent à effectuer une procédure d'authentification, avec un serveur de justificatif d'identité par défaut (DCS) externe au NPN, pour obtenir une clé de session maîtresse (MSK) et, sur la base de la réception d'une seconde indication provenant de l'AMF, dériver des clés de sécurité pour une communication entre l'UE et le NPN sur la base de la MSK. D'autres modes de réalisation comprennent des procédés complémentaires pour une AMF, un DCS et une fonction d'authentification et d'autorisation spécifique de tranche de réseau (NSSAAF), ainsi que des UE et des noeuds de réseau ou des fonctions conçus pour mettre en oeuvre de tels procédés.
PCT/EP2021/072333 2020-08-17 2021-08-11 Établissement de sécurité pour réseaux non publics en 5g WO2022038008A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202063066433P 2020-08-17 2020-08-17
US63/066433 2020-08-17

Publications (1)

Publication Number Publication Date
WO2022038008A1 true WO2022038008A1 (fr) 2022-02-24

Family

ID=77431302

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2021/072333 WO2022038008A1 (fr) 2020-08-17 2021-08-11 Établissement de sécurité pour réseaux non publics en 5g

Country Status (1)

Country Link
WO (1) WO2022038008A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023246649A1 (fr) * 2022-06-24 2023-12-28 华为技术有限公司 Procédé de communication, appareil de communication et système de communication
WO2024066991A1 (fr) * 2022-09-28 2024-04-04 华为技术有限公司 Procédé et appareil de transfert cellulaire
WO2024083103A1 (fr) * 2022-10-21 2024-04-25 Telefonaktiebolaget Lm Ericsson (Publ) Procédé et appareil d'authentification

Non-Patent Citations (7)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 16)", vol. SA WG2, no. V16.5.1, 6 August 2020 (2020-08-06), pages 1 - 594, XP051925869, Retrieved from the Internet <URL:ftp://ftp.3gpp.org/Specs/archive/23_series/23.502/23502-g51.zip 23502-g51.docx> [retrieved on 20200806] *
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on enhanced support of non-public networks (Release 17)", no. V0.4.0, 19 June 2020 (2020-06-19), pages 1 - 158, XP051924077, Retrieved from the Internet <URL:ftp://ftp.3gpp.org/Specs/archive/23_series/23.700-07/23700-07-040.zip 23700-07-040_rm.docx> [retrieved on 20200619] *
3GPP TR 23.700-07
3GPP TS 23.501
3GPP TS 23.502
3GPP TS 33.501
INTEL: "Solution to UE onboarding and provisioning for non-public networks", vol. SA WG3, no. e-meeting; 20200817 - 20200828, 7 August 2020 (2020-08-07), XP051916230, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_sa/WG3_Security/TSGS3_100e/Docs/S3-201699.zip S3-201699.docx> [retrieved on 20200807] *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023246649A1 (fr) * 2022-06-24 2023-12-28 华为技术有限公司 Procédé de communication, appareil de communication et système de communication
WO2024066991A1 (fr) * 2022-09-28 2024-04-04 华为技术有限公司 Procédé et appareil de transfert cellulaire
WO2024083103A1 (fr) * 2022-10-21 2024-04-25 Telefonaktiebolaget Lm Ericsson (Publ) Procédé et appareil d'authentification

Similar Documents

Publication Publication Date Title
US20220159460A1 (en) Non-public network authentication in 5g
US11399281B2 (en) Authentication server function selection in authentication and key management
US11082844B2 (en) Methods for authentication and key management in a wireless communications network and related apparatuses
EP4040825B1 (fr) Gestion de multiples procédures d&#39;authentification dans la 5g
WO2022038008A1 (fr) Établissement de sécurité pour réseaux non publics en 5g
US20230232356A1 (en) Storage of network slice authorization status
WO2021209379A1 (fr) Poussée de fonction de serveurs d&#39;authentification (ausf) de contenus d&#39;authentification et de gestion de clés (akma)
US20230292125A1 (en) Security establishment for non-public networks
US20240080664A1 (en) Routing indicator retrival for akma
US20240064510A1 (en) User equipment (ue) identifier request
US20240073691A1 (en) Indication of Provisioning Protocol for Credentials to Access a Non-Public Network
US20240064129A1 (en) A Method and Function for Accessing a Non-Public Network
US20240196355A1 (en) Recovery from Errors during Network Slice Specific Authentication and Authorization (NSSAA)
US20240137765A1 (en) Authentication and Authorization of Servers and Clients in Edge Computing
US20240107297A1 (en) Key Derivation for Communication
EP4320895A1 (fr) Récupération après d&#39;erreurs pendant une authentification et une autorisation spécifiques à une tranche de réseau (nssaa)
WO2023110097A1 (fr) Admission de tranche de réseau sécurisée dynamique

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21758374

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21758374

Country of ref document: EP

Kind code of ref document: A1