Dynamic Secure Network Slice Admission

A method for authenticating a wireless communications device to a network slice of a communications network is provided. The wireless communications device has one or more attributes associated with it, at least one of the one or more attributes fulfilling an attribute-based access policy of the network slice. The method is performed by a slice manager of the communications network and comprises sending a secret key to the wireless communications device, sending an encrypted access key to the wireless communications device, the encrypted access key being encrypted using the access policy, such that a secret key generated based at least one attribute that fulfill the attribute-based access policy can decrypt the encrypted access key.

TECHNICAL FIELD

The present disclosure relates in general to a method for authenticating a wireless communications device to a network slice of a communications network, the method being performed by a slice manager, a method performed by a wireless communications device, for authenticating the wireless communications device to a network slice of a communications network, and corresponding slice manager, wireless device and computer program (products).

BACKGROUND

Network slicing enables the partitioning of multiple virtual networks on a single physical networking infrastructure. A network slice represents an independent virtualized instance defined by allocation of a subset of the available network resources. Typically, network slices are tailored to meet specific requirements of a set of applications and services.

A fundamental challenge with shared infrastructures is to provide traffic isolation and guarantee appropriate resources to fulfil the required service needs. 3GPP TS 23.501 V17.0.0 (2021 March) specifies the network slicing framework to address this challenge where slice identification and selection in the RAN and core network domains is based on the Single Network Slice Selection Assistance Information (S-NSSAI). A 5G network slice is identified by a S-NSSAI value and defined within a PLMN (associated with a PLMN Identifier).

The network, based on local policies, subscription changes and/or UE mobility may change the set of Network Slice(s) to which the UE is registered and provide the UE with a new Registration Area and/or Allowed NSSAI and the mapping of this Allowed NSSAI to HPLMN S-NSSAIs, for each Access Type over which the UE is registered. In addition, the network may provide the UE with Configured NSSAI for the Serving PLMN, the associated mapping information, and the rejected S-NSSAIs.

It is possible according to 3GPP TS 23.501 V17.0.0 (2021 March) in clause 5.15.5.2.2, that the set of Network Slices for a UE can be changed at any time while the UE is registered with a network, and such change may be initiated by the network, or by the UE. Particularly, the network may perform such a change over each Access Type during a Registration procedure or trigger a notification towards the UE of the change of the Network Slices using a UE Configuration Update procedure as specified in TS 23.502 V17.0.0 (2021 March), clause 4.2.4. UE configuration includes the Access and Mobility Management related parameters decided and provided by the AMF and the UE Policy provided by the Policy Control Function, PCF. When the AMF wants to change the UE configuration for access and mobility management related parameters, it initiates the procedure defined in clause 4.2.4.2.

However, there is a need for an improved handling of authorization of a UE to a network slice.

SUMMARY

It would be advantageous to achieve solutions overcoming, or at least alleviating, the above-mentioned drawbacks. In particular, it would be desirable to enable dynamic management and authorization of wireless communications devices to a network slice, thereby facilitating for a wireless communications device to join a network slice on-demand. Thus, there is a need for an improved way for a wireless device to securely join a network slice.

By a wireless communications device joining a network slice on-demand it may be meant that the UE is dynamically caused to join a network slice in response to a trigger or event. One example could be that a new network slice is created.

It has been realized that existing solutions do not allow a user to have on-demand access to a network slice. Specifically, there are no solutions for transitioning a device to a dynamically created or on-demand created network slice. It is a challenge to ensure secure and efficient distribution of access keys related to such network slices.

To better address one or more of these concerns, methods and devices as defined in the independent claims are provided. Preferable embodiments are defined in the dependent claims.

According to a first aspect, a method for authenticating a wireless communications device to a network slice of a communications network is provided. The method is performed by a slice manager of the communications network. The wireless communications device has one or more attributes associated with it. At least one of the one or more attributes fulfil an attribute-based access policy of the network slice. The method comprises sending a secret key to the wireless communications device. The method further comprises sending an encrypted access key to the wireless communications device. The encrypted access key is encrypted using the access policy, such that the secret key generated based at least one attribute that fulfil the attribute-based access policy can decrypt the encrypted access key.

A network slice may represent an virtualized instance defined by allocation of a subset of available network resources, as defined in 3GPP TS 23.502 v.17.0.0. (2021 March). A network slice may be a temporary network slice, i.e., a network slice created for a limited period of time, or a dynamically created network slice, i.e., a network slice created on-demand (for example in response to an event or trigger).

A slice manager may be any device(s) or function capable of performing an embodiment the method according to the first aspect. For example, the method may be implemented in a network function of the communications network.

The term wireless communications device may be used interchangeably with wireless device. In some examples, a wireless communications device may be called a user equipment, UE. Further examples of a wireless communications device will be described in the detailed description.

An attribute may be any type of property associated with a wireless communications device. As non-limiting examples, meta-data, a token, a credential, a text string, or a key-value pair may be considered an attribute.

An attribute-based access policy may be an access policy controlling access of wireless communications devices to a network slice based on one or more attributes which are associated with the wireless communications devices. An attribute-based access policy may be achieved by an access structure over a set of attributes. In general, an access policy may be defined as requirements that specify what is required in order to access information. In the example of an attribute-based access policy, the requirements are based on attributes, and only wireless devices having certain attributes associated with them may access encrypted information encrypted using or based on the access policy.

The secret key may be generated based on the one or more attributes associated with the wireless communications device such that the secret key may be used to decrypt an access key encrypted using an access policy which the one or more attributes fulfil. As an illustrative example only, an access policy may be a function of attributes and the access policy, and if that function returns true the access policy is considered to be fulfilled or satisfied.

By receiving a secret key generated based on the one or more attributes associated with the wireless communications device, the wireless communications device may decrypt an encrypted access key for the network slice to obtain the access key and subsequently authenticate to the network slice using the access key. In this way, only wireless communications devices having a secret key generated based on one or more attributes that fulfil the attribute-based access policy for the network slice may decrypt the encrypted access key and authenticate to the network slice. This allows for sending, or broadcasting, the encrypted access key to a plurality of wireless communications devices without unintended wireless communications devices (i.e. devices not having an attribute(s) fulfilling the access policy) being able to decrypt the access key and thus authenticate to the network slice. In this way, a plurality of wireless communications devices may be transitioned to a network slice in a secure way.

Further, this decreases the need for a specific configuration update for each wireless communications device that is to be transitioned to a network slice, as the encrypted access key may be distributed to wireless communications devices via broadcast, thus decreasing the communications resources needed. As the respective secret key for each wireless communications device may be distributed some time before the wireless communications device is to be transferred to the network slice, this further decreases the communications resources needed at the time the wireless communications device is to be transferred.

The method facilitates distribution of keys related to network slices.

This may be particularly beneficial in case of an emergency. In emergencies, there is a risk that the communications network gets overloaded as many users may try to use their communications devices at the same time (for example, to find safety or to reach friends and family). This overload may result in that communications are limited. In an emergency, a network slice dedicated to prioritized network traffic may be created to prioritize traffic associated with the first responders. For example, firefighters, police, ambulance personnel, and other first responders may have a prioritized need for their wireless communications devices to work in order to perform their duties. Thus, an emergency network slice may be created, to which the devices of first responders may be transitioned using the solutions described herein. As these solutions may enable transitioning of a plurality of wireless communications devices to a network slice using relatively little communications resources, the wireless communications devices may be transitioned to the network slice even in case of an emergency where the network is of risk at being overloaded.

According to an embodiment, the method may further comprise generating the secret key using the one or more attributes associated with the wireless communication device. By using the one or more attributes associated with the wireless communications device, the secret key may be generated such that it may decrypt an encrypted message encrypted using an access policy which the one or more attributes fulfils.

According to an embodiment, the method may further comprise generating the access key, and encrypting the access key using the attribute-based access policy.

According to an embodiment, the access key may be generated in response to the network slice being created, e.g. generated, configured, setup or made available for use. In an example, the slice manager may receive a notification that the network slice is generated or created, and in response to the notification generate the access key. Generating the access key in response to the network slice being created is advantageous in that the access key may be generated specifically for the network slice.

According to an embodiment, the method may further comprise determining an attribute-based access policy for the network slice. The determination may be based on information received by the slice manager specifying what attributes associated with a wireless communications device should give the associated wireless communications device access to the access key, i.e., be able to decrypt the encrypted access key, and thereby to authenticate to and access the network slice.

According to an embodiment, the method may further comprise receiving a request from the wireless communications device for the secret key. The request may comprise the one or more attributes associated with the wireless communications device.

According to an embodiment, the method may further comprise verifying that the one or more attributes associated with the wireless communications device originate from a trusted application of the wireless communications device. In this way, the slice manager may verify that the attributes are indeed associated with the wireless communications device, thereby decreasing the risk that the wireless communications device receives a secret key based on attributes not associated with it. In other words, the slice manager may verify the one or more attributes associated with the wireless communications device.

According to an embodiment, the method may further comprise generating a secret master key and a corresponding public key for the slice manager, wherein the secret key is generated using the secret master key and the one or more attributes associated with the wireless communications device, and wherein the public key is available to the wireless communications devices.

According to an embodiment, the secret key may be generated using attribute-based encryption. The attribute-based encryption may, for example, be cipher-text attribute-based encryption or key-policy attribute-based encryption.

According to an embodiment, the encrypted access key is encrypted using attribute-based encryption. The attribute-based encryption may, for example, be cipher-text attribute-based encryption or key-policy attribute-based encryption.

By using attribute-based encryption, an encrypted access key may be sent to a plurality of wireless communications devices, and only the wireless communications devices having one or more attributes fulfilling an access policy of the encrypted access key may decrypt it. In this way, an access key may be distributed to a plurality of wireless communications devices in a relatively secure way.

According to an embodiment, the method may further comprise sending a device-specific secret key to each of a plurality of wireless communications devices, each of the plurality of wireless communications devices having one or more attributes associated with it, wherein each device-specific secret key is generated based on the one or more attributes associated with each wireless communications device. The method further comprises sending an encrypted access key to the plurality of wireless communications devices, the encrypted access key being encrypted using the access policy, such that a device-specific secret key generated based on at least one attribute that fulfil the attribute-based access policy can decrypt the encrypted access key.

According to a second aspect, a method performed by a wireless communications device, for authenticating the wireless communications device to a network slice of a communications network is provided. The wireless communications device has one or more attributes associated with it. The at least one of the one or more attributes fulfils an attribute-based access policy of the network slice. The method comprises receiving a secret key generated based on the one or more attributes. The method further comprises receiving an encrypted access key for the network slice. The encrypted access key being encrypted using the attribute-based access policy such that a secret key generated based at least one attribute that fulfill the attribute-based access policy can decrypt the encrypted access key. The method further comprises decrypting the encrypted access key using the secret key to obtain the access key. The method further comprises authenticating the wireless communications device to the network slice using the access key.

In general, all benefits and explanations described with reference to the first aspect and any embodiments of the first aspect apply also for embodiments of the second aspect, and vice versa.

By receiving a secret key generated based on the one or more attributes associated with the wireless communications device, the wireless communications device may decrypt an encrypted access key for the network slice to obtain the access key and thus authenticate to the network slice. In this way, only wireless communications devices having a secret key generated based on one or more attributes that fulfil the attribute-based access policy for the network slice may decrypt the encrypted access key. This allows for sending, or broadcasting, the encrypted access key to a plurality of wireless communications devices without unintended wireless communications devices (i.e. devices not having an attribute(s) fulfilling the access policy) being able to decrypt the access key and thus authenticate to the network slice. In this way, a plurality of wireless communications devices may be transitioned to a network slice in a relatively secure way.

This method may facilitate for transition of a wireless communications device to a network slice. Further, distribution of keys related to network slices are facilitated.

According to an embodiment, the network slice may be a dynamically created network slice or a temporary network slice. By dynamically created it may be meant that the network slice is created in response to an event or a trigger. This could, in some examples, mean that the network slice is created after the wireless communications device has registered to the network. By a temporary network slice, it may be meant a network slice created for a limited time period. For example, a temporary network slice may be an emergency network slice created in response to an emergency, which may benefit from a network slice which network traffic is prioritized.

According to an embodiment, the method may further comprise receiving a notification to authenticate to the network slice and an identifier of the network slice. The notification may, for example, be a request or an invitation to authenticate to the network slice. The identifier may, for example, be comprised in the notification. By receiving a notification to authenticate to the network slice, the wireless communications device may be caused to authenticate to the network slice using the decrypted access key and the identifier. In some examples, the notification may be received by a plurality of wireless communications devices, and in those examples only the wireless communications devices that have been able to decrypt the encrypted access key will be able to decrypt the encrypted access key and subsequently authenticate to, or join, the network slice.

According to an embodiment, the method may further comprise establishing a secure connection with a slice manager of the communications network, wherein the secret key is received from the slice manager using the secure connection. By establishing a secure connection with a slice manager of the communications network, the secret key may be securely received by the wireless communications device.

According to an embodiment, the method may further comprise transmitting the one or more attributes associated with the wireless communications device to a slice manager of the communications network. By transmitting the one or more attributes associated with the wireless communications device, the secret key may be generated based on the transmitted one or more attributes. In some examples, the secret key may be generated by the slice manager.

According to an embodiment, the one or more attributes associated with the wireless communications device may be stored by a trusted entity of the wireless communications device, wherein the trusted entity is trusted by a slice manager of the communications network. In this way, the slice manager may generate the secret key based on attributes originating from a trusted entity, thereby decreasing the risk that the secret key is generated based on incorrect attributes. Since the secret key is generated based on trusted attributes, the risk that a wireless device receives a secret key based on incorrect attributes in decreased, and thus the risk that a wireless device is able to decrypt an access key it shouldn't be able to decrypt is decreased. For example, the attributes may be provisioned on a SIM of the wireless device.

According to an embodiment, the trusted entity comprises an application of the wireless communications device. An application may be any type of software running on the wireless device, such as a trusted device-native application or a trusted downloaded application, or an application accessible to the wireless device, for example over the Internet or over device-to-device communication.

According to an embodiment, the at least one attribute associated with the wireless communications device is indicative of a role associated with a user of the wireless communications device. In this embodiment, the role may be verified via the trusted entity.

According to an embodiment, the at least one attribute associated with the wireless communications device comprises a position of the wireless communications device. In this embodiment, the position may be verified via the trusted entity.

According to an embodiment, the encrypted access key is encrypted using attribute-based encryption.

According to a third aspect, a slice manager for authentication of a first wireless communications device to a network slice is provided. The slice manager comprises a processor, and a memory coupled to the processor, wherein the memory stores instructions that when executed by the processor causes the processor to perform operations according to an embodiment of the method according to the first aspect.

According to a fourth aspect, a computer program product is provided. The computer program product comprises a non-transitory computer readable storage medium comprising computer readable instructions embodied in the medium that when executed by a processor of a slice manager causes the processor to perform operations according to any of the methods of the first aspect.

According to a fifth aspect, a wireless communications device for authenticating to a network slice of a communications network is provided. The wireless communications device comprises a processor; and a memory coupled to the processor, wherein the memory stores instructions that when executed by the processor cause the processor to perform operations according to any of the methods of the second aspect.

According to a sixth aspect, a computer program product is provided. The computer program product comprises a non-transitory computer readable storage medium comprising computer readable instructions embodied in the medium that when executed by a processor of a wireless communications device causes the processor to perform operations according to any of the methods of the second aspect.

According to a seventh aspect, a computer program comprising instructions which, when the program is executed by a computer, cause the computer to carry out the steps of any of the methods of the first aspect and the second aspect.

According to an eight aspect, a method implemented in a communication system including a host computer, a base station and a wireless communications device is provided. The method comprises at the host computer, providing user data, and at the host computer, initiating a transmission carrying the user data to the wireless communications device via a network slice, wherein the wireless communications device has been authenticated to the network slice using any of the methods of the second aspect.

According to an embodiment, the method further comprises at the wireless communications device, receiving the user data from the base station.

According to a ninth aspect, a communication system including a host computer is provided. The communication system comprises processing circuitry configured to provide user data, and a communication interface configured to forward user data to a wireless network for transmission to a wireless communications device authenticated to a network slice, wherein the wireless communications device comprises a radio interface and processing circuitry, the processing circuitry configured to authenticate the wireless communications device to the network slice using any of the methods of the second aspect.

According to an embodiment, the communication system further includes the wireless communications device.

According to an embodiment, the cellular network further includes a base station configured to communicate with the wireless communications device.

According to an embodiment, the processing circuitry of the host computer is configured to execute a host application providing the user data, and the processing circuitry of the wireless communications device is configured to execute a client application associated with the host application and receiving or requesting the user data via the client application.

Further advantages and features of the present disclosure will become apparent upon reading the following detailed description in view of the drawings briefly described below.

DETAILED DESCRIPTION

Exemplary embodiments briefly summarized above will now be described more fully with reference to the accompanying drawings. These descriptions are provided by way of example to explain the subject matter to those skilled in the art and should not be construed as limiting the scope of the subject matter to only the embodiments described herein. More specifically, examples are provided below that illustrate the operation of various embodiments according to the advantages discussed above.

Furthermore, the following terms are used throughout the description given below: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. Some examples of a radio access node include, but are not limited to, a base station (e.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.Core Network Node: As used herein, 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.Wireless Device: As used herein, a “wireless device” or “wireless communications device” (“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). Some examples of 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 (IoT) devices, vehicle-mounted wireless terminal devices, mobile terminals (MTs), etc.Radio Node: As used herein, a “radio node” can be either a “radio access node” (or equivalent term) or a “wireless device.”Network Node: As used herein, a “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. Functionally, 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: As used herein, the term “node” (without any prefix) 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.Service: As used herein, the term “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: As used herein, the term “component” refers generally to any component needed for the delivery of a service. Examples of component are 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), and cloud infrastructure with related resources such as computation, storage. In general, 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).

Note that the description given herein focuses on a 3GPP cellular communications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is generally used. However, the concepts disclosed herein are not limited to a 3GPP system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from the concepts, principles, and/or embodiments described herein.

In addition, 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. Furthermore, although 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.

At a high level, the 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.

Communication links between the UE and a 5G network (AN and CN) 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. Security for the communications over this these strata is provided by the NAS protocol (for NAS) and PDCP (for AS).

FIG.1Aillustrates a high-level view of an exemplary 5G network architecture, consisting of a Next Generation RAN (NG-RAN)199and a 5G Core (5GC)198. NG-RAN199can include one or more gNodeB's (gNBs) connected to the 5GC via one or more NG interfaces, such as gNBs100,150connected via interfaces102,152, respectively. More specifically, gNBs100,150can be connected to one or more Access and Mobility Management Functions (AMFs) in the 5GC198via respective NG-C interfaces. Similarly, gNBs100,150can be connected to one or more User Plane Functions (UPFs) in 5GC198via respective NG-U interfaces. Various other network functions (NFs) can be included in the 5GC198, as described in more detail below.

In addition, the gNBs can be connected to each other via one or more Xn interfaces, such as Xn interface140between gNBs100and150. The radio technology for the NG-RAN is often referred to as “New Radio” (NR). With respect the NR interface to UEs, each of the gNBs can support frequency division duplexing (FDD), time division duplexing (TDD), or a combination thereof. Each of the gNBs can serve a geographic coverage area including one more cells and, in some cases, can also use various directional beams to provide coverage in the respective cells.

NG-RAN199is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL). The NG-RAN architecture, i.e., the NG-RAN logical nodes and interfaces between them, is defined as part of the RNL. For each NG-RAN interface (NG, Xn, F1) the related TNL protocol and the functionality are specified. The TNL provides services for user plane transport and signaling transport. In some exemplary configurations, each gNB is connected to all 5GC nodes within an “AMF Region” which is defined in 3GPP TS 23.501 (v15.5.0). If security protection for CP and UP data on TNL of NG-RAN interfaces is supported, NDS/IP (3GPP TS 33.401 (v15.8.0) shall be applied.

The NG RAN logical nodes shown inFIG.1A(and described in 3GPP TS 38.401 (v15.6.0) and 3GPP TR 38.801 (v14.0.0) include a Central Unit (CU or gNB-CU) and one or more Distributed Units (DU or gNB-DU). For example, gNB100includes gNB-CU110and gNB-DUs120and130. CUs (e.g., gNB-CU110) are logical nodes that host higher-layer protocols and perform various gNB functions such controlling the operation of DUs. A DU (e.g., gNB-DUs120,130) is a decentralized logical node that hosts lower layer protocols and can include, depending on the functional split option, various subsets of the gNB functions. As such, 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 F1 logical interfaces, such as interfaces122and132shown inFIG.1A. However, 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 F1 interface is not visible beyond gNB-CU.

Another change in 5GS (e.g., in 5GC) is that traditional peer-to-peer interfaces and protocols found in earlier-generation networks are modified and/or replaced by a Service Based Architecture (SBA) in which Network Functions (NFs) provide one or more services to one or more service consumers. This can be done, for example, by Hyper Text Transfer Protocol/Representational State Transfer (HTTP/REST) application programming interfaces (APIs). In general, 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. For example, the services can store their context externally in a proprietary database. This can facilitate various cloud infrastructure features like auto-scaling or auto-healing. Furthermore, 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”.

FIG.1Bshows an exemplary non-roaming 5G reference architecture with service-based interfaces and various 3GPP-defined NFs within the Control Plane (CP). These include the following NFs, with additional details provided for those most relevant to the present disclosure:Application Function (AF, with Naf interface) 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.Policy Control Function (PCF, with 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.User Plane Function (UPF)— supports handling of user plane traffic based on the rules received from SMF, including packet inspection and different enforcement actions (e.g., event detection and reporting). UPFs communicate with the RAN (e.g., NG-RNA) via the N3 reference point, with SMFs (discussed below) via the N4 reference point, and with an external packet data network (PDN) via the N6 reference point. The N9 reference point is for communication between two UPFs.Session Management Function (SMF, with Nsmf interface) 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. For example, 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, 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 via the N1 reference point and with the RAN (e.g., NG-RAN) via the N2 reference point. An AMF may be co-located with a Security Anchor Function (SEAF, not shown) that holds a root (or anchor) key for a visited network.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. For example, NEF provides a service that allows an AF to provision specific subscription data (e.g., expected UE behavior) for various UEs.Network Repository Function (NRF) with Nnrf interface—provides service registration and discovery, enabling NFs to identify appropriate services available from other NFs.Network Slice Selection Function (NSSF) with Nnssf interface—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. The NSSF enables other NFs (e.g., AMF) to identify a network slice instance that is appropriate for a UE's desired service.Network Slice Specific Authentication and Authorization Function (NSSAAF) supports network slice-specific authentication and authorization with a AAA Server (AAA-S). If the AAA-S belongs to a third party, the NSSAAF may contact the AAA-S via a AAA proxy (AAA-P).Authentication Server Function (AUSF) with Nausf interface—based in a user's home network (HPLMN), it performs user authentication and computes security key materials for various purposes.Network Data Analytics Function (NWDAF) with Nnwdaf interface—provides network analytics information (e.g., statistical information of past events and/or predictive information) to other NFs on a network slice instance level.Location Management Function (LMF) with Nlmf interface—supports various functions related to determination of UE locations, including location determination (in some examples called position) 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.

The Unified Data Management (UDM) function supports generation of 3GPP authentication credentials, user identification handling, access authorization based on subscription data, and other subscriber-related functions. To provide this functionality, the UDM uses subscription data (including authentication data) stored in the 5GC unified data repository (UDR). In addition to the UDM, the UDR supports storage and retrieval of policy data by the PCF, as well as storage and retrieval of application data by NEF.

The UDM may include, or be co-located with, an Authentication Credential Repository and Processing Function (ARPF) that stores long-term security credentials for subscribers. The UDM may also include, or be co-located with, a Subscription Identifier De-concealing Function (SIDF) that maps between different subscriber identifiers.

The NRF allows every NF to discover the services offered by other NFs, and Data Storage Functions (DSF) allow every NF to store its context. In addition, the NEF provides exposure of capabilities and events of the 5GC to AFs within and outside of the 5GC. For example, NEF provides a service that allows an AF to provision specific subscription data (e.g., expected UE behavior) for various UEs.

As mentioned above, 3GPP Rel-16 introduces a new AKMA feature that is based on 3GPP user credentials in 5G, including the IoT use case. More specifically, AKMA leverages the user's AKA credentials to bootstrap security between the UE and an AF, which allows the UE to securely exchange data with an application server. The AKMA architecture can be considered an evolution of Generic Bootstrapping Architecture (GBA) specified for 5GC in Rel-15 and is further specified in 3GPP TS 33.535 (v.16.2.0).

In addition to the NEF, AUSF, and AF shown inFIG.1Band described above, AKMA also utilizes an anchor function for authentication and key management for applications (AAnF). This function is shown inFIG.1Bwith 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.

As mentioned above, 3GPP has introduced a dedicated procedure called network slice-specific authentication and authorization (NSSAA) to authenticate and authorize the UE when it requests access to a specific network slice identified by an S-NSSAI.FIG.2shows an exemplary signal flow diagram that illustrates a relationship between primary authentication and NSSAA. In particular,FIG.2shows signaling between a UE, an AMF/SEAF, an ARPF/UDM, an NSSAAFR, an AAA-S, and (optionally) an AAA proxy (AAA-P). The procedure shown inFIG.3is further defined in 3GPP TS 23.501 (v16.8.0) section 5.15.10, 3GPP TS 23.502 (v16.8.0) section 4.2.9, and 3GPP TS 33.501 (v16.5.0) section 16.

In operation 1, the UE sends a registration request including an NSSAI to the AMF/SEAF. In operation 2, the UE, AMF/SEAF, and ARPF/UDM perform a primary authentication of the UE. In operation 3, the AMF/SEAF determines if the network slice identified by NSSAI requires a slice-specific authentication of the UE. In operation 4, the AMF/SEAF sends a registration accept message to the UE, which responds with a registration complete message. In operation 5, the UE and AAA-S run an EAP-based authentication via AMF (EAP Authenticator) and NSSAAF (service defined in TS 29.526). In operation 6, the AMF/SEAF sends a UE configuration update message to the UE after completing of the NSSAA. Although not shown inFIG.2, the AAA-S may request the NSSAA Re-authentication or revocation for an S-NSSAI which had been previously successfully authenticated/authorized.

After a successful or unsuccessful NSSAA procedure, the AMF retains the authentication and authorization status for the UE (in the UE context) for the specific S-NSSAI of the HPLMN while the UE remains RM-REGISTERED in the PLMN. In this manner, the AMF is not required to execute a new NSSAA procedure for the UE at every Periodic Registration Update or Mobility Registration procedure between UE and PLMN. The NSSAA status of each S-NSSAI, if any is stored, is also transferred between AMFs as part of the UE context when the AMF changes.

FIG.3shows an overview of a system300implementing a method for authenticating a wireless device to a network slice according to some embodiments.

The system300comprises a plurality of wireless communications devices800a,800b,800c,800d. The communications devices are registered to a communications network, for example via a network node1100. In some examples the wireless communications device800a,800b,800c,800dmay be registered to or authenticated to a network slice, for example by using the method described with reference toFIG.2. In the example with the network slice, it is not necessary that the communications devices are all authenticated to the same network slice. It is a sufficient prerequisite that the communications devices800a,800b,800c,800dcan reach the slice manager900.

Each wireless communications device800may have one or more attributes850a,850b,850cassociated with them. In this example wireless communications device800ahas attribute A850aassociated with it, the wireless communications device800bhas attribute B850bassociated with it, the wireless communications device800chas attributes A and C850cassociated with it, and wireless communications device800dhas no attribute associated with it.

An attribute may, for example, be any type of property associated with a wireless communications device. As non-limiting examples, meta-data, a token, a credential, a text string, a tag, an identifier, a location of the wireless communications device, a position of the wireless communications device, or a key-value pair may be considered an attribute. An attribute may, for example, be indicative of a role of a user of the wireless communications device, or a position of the wireless communications device.

In the communications network there is a network slice1200. The network slice may have been dynamically created or may be considered a temporary network slice, i.e. a network slice created to be used for a limited amount of time. The network slice as an access policy1210associated with it. In this example the access policy requires that the wireless communications devices should be associated with the attribute A. That is, any wireless communications device that should be able to decrypt the encrypted access key, and thereby authenticating to the network slice, must have, at least, the attribute A associated with it.

It is assumed in this example that the wireless communications device800a,800b,800c,800dare be registered to the communications network, but none of them are yet authenticated to the network slice.

The slice manager900may send a respective secret key to some or all of the wireless communications devices800a,800b,800c,800d. The sending may be performed independently to each wireless communications device, for example in response to a request from the wireless communications device. A secret key for a wireless communications device may be generated based on the one or more attributes associated with the wireless communications device. In this example wireless communications devices800a,800band800chave received a respective secret key, inFIG.3indicated by the key symbol. The secret key for device800ahas been generated based on attribute850aA, and the secret key for device800bhas been generated based on attribute850bB, and the secret key for device800chas been generated based on attribute850cA and C. Wireless communications device800c, which has no attribute associated with it, has not received a secret key. Alternatively, the wireless communications device800cmay receive a key generated based on no attributes.

In order to enable the desired wireless communications devices800a,800chaving attribute A to join the network slice1200, the slice manager900sends an encrypted access key for the network slice1200. The encrypted access key has been encrypted based on the access policy1210associated with the network slice1200, such that only a secret key generated based on one or more attributes that fulfil or satisfies the access policy can decrypt the access key. In this example, since the access policy1210requires the attribute A, only wireless devices800aand800ccan decrypt the encrypted access key using their respective secret keys.

The access key may be encrypted using attribute-based encryption (ABE). The access key may be encrypted using a public key or public parameters associated with the slice manager and the access policy.

The respective secret keys may be generated using attribute-based encryption. The secret key for a wireless communications device may be generated based on a master key associated with the slice manager and the attributes associated with the wireless communications device.

In order to cause the wireless communications devices800a,800b,800c,800dto attempt to join or authenticate to the network slice1200, a network function, such as an AMF or AUSF may send a notification to the wireless communications devices to authenticate to the network slice1200. The notification may alternatively be sent to the wireless communications devices from another server or function.

The notification may comprise information needed for the wireless communications devices to request to join the network slice, such as information identifying the network slice, for example an identifier, such as a NSSAI.

The wireless communications device may, in response to the notification to join the network slice, attempt to join the network slice. Since only wireless communications devices800aand800care able to decrypt the access key, these are the only wireless communications devices that can successfully authenticate to the network slice.

FIG.4shows a method400for authenticating a wireless device800to a network slice according to some embodiments.FIG.4shows a wireless device800, also called a wireless communications device, an AMF/AUSF1000,1050and a slice manager900. Specifics of the wireless device800and the slice manager900will be described with reference toFIGS.11and12.

The wireless communications device, denoted WD inFIG.4, may be registered405to a communications network. The wireless communications device has one or more attributes associated405with it, as will be described with reference toFIG.11.

In step410the wireless communications device establishes a connection410with the slice manager900. This connection could be initiated by either the wireless communications device800, the slice manager900or by another function in the network. The connection between the wireless communications device800and the slice manager900may be a secure connection. As a non-limiting example, the secure connection may be a TLS connection.

In step420the slice manager900generates or obtains a secret key for the wireless device800. The secret key is based on the one or more attributes associated with the wireless communications device. The one or more attributes may in some examples be received by the slice manager900from the wireless device800. In other examples the one or more attributes are available to the slice manager900from a server (for example through an API), a network function or stored locally to the slice manager. After the secret key has been generated, the slice manager900transmits the secret key to the wireless device, for example, over the secure connection.

In step430the slice manager receives a notification indicating that a network slice has been created. The notification may be received from a network function of the communications network or from an operator of the network. In response to the network slice being created by an operator, the operator may notify the slice manager900of a created network slice and optionally indicate to the slice manager900that one or more wireless devices800are to be transferred to the created network slice. The notification may comprise information needed for the slice manager to generate or obtain an access key for the network slice and information related to an access policy of the network slice. Such information may, for example, be an IP address of a service provider or server where the slice manager can access the access key, an access policy, information identifying a group of wireless devices that should be transferred, a role of users of a wireless device that should be transferred, or a capability). The information may correspond to the attributes of wireless communications devices that the operator or a service provider of the network slice wishes to transfer to the created network slice, for example, “wireless devices having attribute A”.

In response to the notification received in step430, the slice manager may obtain an access key for the network slice, for example, by generating the access key or by receiving it in association with the notification. In any event, the slice manager encrypts the access key based on an attribute-based access policy for the network slice. The slice manager900then sends the encrypted access key to a plurality of wireless communications device, including the wireless communications device800. The plurality of wireless communications device may, for example, be wireless communications devices connected to the slice manager, wireless communications devices registered or authenticated to a first network slice, different from the created network slice, wireless communications devices in a specific geographical area, or any other group of wireless communications devices.

The AMF1000or AUSF1050may also have been notified of the created network slice and may send a notification or message to the wireless device800to request to join the network slice. The notification or message may comprise the information needed for the wireless device800to request to join the network slice. The steps for joining the network slice may, for example, be the ones shown inFIG.5,FIG.6orFIG.7.

In step460, the wireless communications device800decrypts the encrypted access key, given that the one or more attributes associated with the wireless communications device800fulfil the access policy. The wireless communications device800may then use the decrypted access key and the information received in the notification or message from the AUSF/AMF and request to join the network slice (for example, as described with reference toFIG.5,FIG.6orFIG.7).

FIG.5shows a method for authenticating a wireless communications device800to a network slice using an attribute associated with the wireless device800according to some embodiments. In steps 0a and 0b the wireless communications device800is authenticated to or registered to a communications network. The communications network could, for example, be a 5G network, or another type of communications network. The wireless communications device has one or more attributes associated with it in step 0b. In this example the attribute associated with the wireless communications device is the attribute “Firefighter”. The attribute, “Firefighter”, is in this example considered to be indicative of a role of a user of the wireless device. In step 0c, the slice manager creates a master key for the slice manager and defines a public key associated with it. In step 0d a connection is established between the slice manager900and the wireless communications device800. The establishment may be initiated either from the slice manager900, the wireless communications device800or by another entity or service, such as a network function in the communications network or an application server.

In step 2a the slice manager900generates a secret key for the wireless communications device800based on the one or more attributes associated with the wireless communications device, in this example “Firefighter”. The one or more attributes could be received by the slice manager from another entity or function, such as from the wireless communications device800or a network function in the communications network in step 1a. In some examples, the slice manager900may determine or associate the attributes to the wireless communications device in step 1a.

In step 3 the slice manager900sends the secret key to the wireless communications device800. The secret key may, for example, be sent over the connection established in step 0d. In any event, the secret key should be sent securely to the wireless communications device, and the person skilled in the art is aware of methods for secure transfer of a secret key.

In step 4 the slice manager900receives an indication that an access key for a network slice is to be distributed, for example in response to that the network slice has been created. In step 5 the slice manager900generates an access key for the network slice. In other examples, the slice manager900may instead obtain the access key from a key generator accessible to the slice manager900. In step 5, the slice manager900encrypts the access key. The access key may be encrypted using an access policy of the network slice, such that only a secret key generated based on one or more attributes that fulfil or satisfies the access policy can decrypt the encrypted access key to obtain the access key. In this example, the access key may be encrypted using a policy defining that only wireless devices having the attribute “firefighters” should be able to decrypt the encrypted access key.

The encrypted access key is sent by the slice manager900to one or more wireless devices800in step 7. The encrypted access key is received by the wireless device800in step 7.

The wireless device800receives a message to join a network slice in step 8. The message could alternatively be called a notification. The message or notification may be received from, for example, an AMF1000of the communications network, or from another entity or function. The message or notification may be received by a plurality of wireless communications devices, regardless of the attributes associated with each of them.

In step 9, a wireless device800having a secret key generated based on one or more attributes that fulfil or satisfies the access policy of the network slice decrypts the encrypted access key to obtain the access key.

In step 10, the wireless device800having the access key can join the network slice by authenticating to the network slice using the access key, for example, as will be described with reference toFIG.7.

FIG.6shows a method for authenticating a wireless communications device to a network slice using a position attribute associated with the wireless communications device according to some embodiments. The method shown inFIG.6is similar to the method described with reference toFIG.5, and the method ofFIG.6may comprise steps from the method ofFIG.5, and vice versa. Since the method ofFIG.6comprise many of the same steps as the method described with reference toFIG.5, only differences will be described.

In step 1b the slice manager900may assign, i.e. associate, attributes to a wireless communications device. In this example, the attributes comprise a position of the wireless communications device. The position could, for example, be obtained from a network function, such as LMF, of the communications network to which the wireless communications device800is registered, or it could be obtained from the wireless communications device800, for example from a trusted application of the wireless communications device. In this example, the slice manager also associates the attribute “Firefighter” with the wireless communications device. In step 2b the slice manager generates a secret key for the wireless communications device800based on the attributes, similarly to step 2a of the method described with reference toFIG.5.

FIG.7shows a method for authenticating a wireless device to a network slice using an access key according to some embodiments. The access key may be obtained by any of the methods described with reference toFIG.3,4,5, or6. The method described with reference is an exemplary authentication method. Other methods may be used for authentication a wireless communications device to a network slice using an access key. The method described below with reference toFIG.7may, for example, be used for step 10 ofFIGS.5and6.

In step 11, the AMF1000sends a message, for example a NAS Message, to a plurality of wireless communications devices, including the wireless communications device800with an indication to join a network slice. The message could, for example, be sent to all or almost all wireless communications devices in a location. The message may further comprise an identifier of the network slice. The identifier may, for example, be a NSSAI.

In step 12, the wireless device800sends a response message, for example a NAS Message to the AMF to join the network slice.

In step 13, the AMF sends an authentication request, for example a AuthN Request to an AAA server of the communications network. In some examples, the slice manager may implement AAA functionality for the network slice (see for example 3GPP TR 33.813 V16.0.0 (2020 July)).

In step 14 the wireless communications device800authenticates to the AUSF using the access key.

In step 15, upon successful authentication of the wireless device, the AUSF sends a message, such as a EAP success message, to the AMF for the wireless device.

In step 16, a success message, for example a NAS Message EAP Success, is sent to the wireless communications device from the AMF. Thus, the wireless communications device is successfully authenticated and authorized to join the temporary network, step 17.

According to some embodiment, the slice manager may be distributed over a plurality of entities, the different entities together may be operative to implement embodiments of the slice manager as described herein in a collaborative manner. An example is shown inFIG.8. In the example shown inFIG.8, the distribution of the device specific secret key, i.e. steps 0-3 as described above with reference toFIGS.5and6, is performed with a first slice manager900a. The first slice manager then sends the necessary parameters, for example the public key, to a second slice manager900b. In some examples, the attributes of the access policy are accessible to the first slice manager, and in those examples the attributes or an access policy may be sent from the first slice manager900ato the second slice manager900b.

The notification of the creation of the network slice may be received by the second slice manager900b, which may then generate an access key, encrypt the access key, and send the access key to one or more wireless devices800. This corresponds to steps 4-7 as described above with reference toFIGS.5and6.

The second slice manager900bmay transmit the access key to a third slice manager900c, which may be included in the steps for authenticating a wireless device to a network slice. In other words, it may be included in the steps for a wireless device to join the network slice. This may correspond to steps 8 or 10 described with reference toFIGS.5and6, or to some of the steps described with reference toFIG.7.

In a specific example where the network slice is used as an emergency network slice, the following setup could be used. In the examples with “firefighters” as described above with reference toFIGS.5and6, the first slice manager900acould be connected with a fire station and receiving information of an emergency. The first slice manager900athen creates a secret key for a wireless device associated with the attribute “firefighter” and sends the public parameters to a second slice manager. The second slice manager could, for example, be a unit on the emergency location belonging to an operator, set up during or before the emergency. The second slice manger900bcreates an access key for a network slice and encrypts it using the public key and an access policy for the network slice. The encrypted access key is then sent to a plurality of wireless communications device800. The second slice manager900bthen sends the access key to a third slice manager900c. The third slice manager could be an identity provider in the operator's network. The third slice manager could then be used during authentication of wireless communications device. In this way, a group of wireless communications devices associated with firefighters, or other emergency personnel, could be transitioned to an emergency network slice (which network traffic could be prioritized over other network traffic in an area).

FIG.9is a flow diagram of a method M900performed by a slice manager according to an embodiment. The method M900comprises sending S910secret key to a wireless communications device and sending S950an encrypted access key to the wireless communications device, the encrypted access key being encrypted using the access policy, such that a secret key generated based at least one attribute that fulfil the attribute-based access policy can decrypt the encrypted access key. Optionally, the method further comprises receiving S920a notification of a created network slice. The method M900may further comprise generating S930the access key. The method may further comprise encrypting S940the access key. The method shown inFIG.9is an overview of the method and further details are disclosed in embodiments of the methods described herein, for examples with reference toFIGS.4-8.

FIG.10is a flow diagram of a method M1000performed by a wireless communications device according to some embodiments. The method comprises receiving S1030a secret key generated based on one or more attributes associated with the wireless communications device and receiving S1040an encrypted access key for the network slice, the encrypted access key being encrypted using the attribute-based access policy. The method further comprises decrypting S1050the encrypted access key using the secret key to obtain the access key and authenticating S1040the wireless communications device to the network slice using the access key. Optionally, the method may further comprise stablishing S1010a secure connection with a slice manager of a communications network and transmitting S1020the one or more attributes associated with the wireless communications device to a slice manager of the communications network. The flow chart shown inFIG.10is an overview of the method and further details are disclosed in embodiments of the methods described herein, for examples with reference toFIGS.4-8.

FIG.11is a block diagram of elements of a wireless communications device800according to some embodiments. The wireless communications device in this example has a processor810, a memory820, an RF front end, a transceiver, a modem or similar, and power amplifier(s)830and an antenna840. The wireless communications device800may, for example, be a smart phone, a tablet, a wearable device, or another communications device capable of transmitting and receiving data wirelessly. Further examples of a wireless communications device are described above. Generally, the communications device is capable of authenticating or being registered to a communications network.

The wireless communications device800may have one or more attributes associated with it. The wireless communications device800may have a trusted device-native application or a trusted downloaded application that can be used for storing the associated attributes and/or for performing parts of the method. In some examples the wireless communications device800may retrieve the associated attributes from a server, such as from a cloud service or an API or a server. In some examples the wireless communications device800may retrieve the associated attributes via device-to-device communications. In other embodiments the attributes associated with the wireless communications device800are not accessible to the wireless communications device but are handled by an application or function elsewhere.

In the example where the one or more attributes comprise a position of the device, the position may, for example, be obtained from the communications network or from a positioning function of the wireless communication device.

FIG.12is a block diagram of elements of a slice manager that are configured according to some embodiments. The slice manager comprises a network interface910, a processor920and a memory930, and is configured to perform at least a subset of the steps of the methods described herein.

The slice manager may, for example, be implemented in one or more physical devices, in one or more functions of a communications network, or in one or more application servers.

Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). 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).

Further examples of 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. As another example, a network node can be a virtual network node as described in more detail below. More generally, however, 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.

InFIG.13, network node1060includes processing circuitry1070, device readable medium1080, interface1090, auxiliary equipment1084, power source1086, power circuitry1087, and antenna1062. Although network node1060illustrated in the example wireless network ofFIG.16can 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. Moreover, while the components of network node1060are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node can comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium1080can comprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node1060can 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. In certain scenarios in which network node1060comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components can be shared among several network nodes. For example, a single RNC can control multiple NodeB's. In such a scenario, each unique NodeB and RNC pair, can in some instances be considered a single separate network node. In some embodiments, network node1060can be configured to support multiple radio access technologies (RATs). In such embodiments, some components can be duplicated (e.g., separate device readable medium1080for the different RATs) and some components can be reused (e.g., the same antenna1062can be shared by the RATs). Network node1060can also include multiple sets of the various illustrated components for different wireless technologies integrated into network node1060, 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 node1060.

Processing circuitry1070can 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 node1060, either alone or in conjunction with other network node1060components (e.g., device readable medium1080). Such functionality can include any of the various wireless features, functions, or benefits discussed herein.

For example, processing circuitry1070can execute instructions stored in device readable medium1080or in memory within processing circuitry1070. In some embodiments, processing circuitry1070can include a system on a chip (SOC). As a more specific example, instructions (also referred to as a computer program product) stored in medium1080can include instructions that, when executed by processing circuitry1070, can configure network node1060to perform operations corresponding to various exemplary methods (e.g., procedures) described herein.

In some embodiments, processing circuitry1070can include one or more of radio frequency (RF) transceiver circuitry1072and baseband processing circuitry1074. In some embodiments, radio frequency (RF) transceiver circuitry1072and baseband processing circuitry1074can be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry1072and baseband processing circuitry1074can be on the same chip or set of chips, boards, or units.

In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device can be performed by processing circuitry1070executing instructions stored on device readable medium1080or memory within processing circuitry1070. In alternative embodiments, some or all of the functionality can be provided by processing circuitry1070without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry1070can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry1070alone or to other components of network node1060but are enjoyed by network node1060as a whole, and/or by end users and the wireless network generally.

Device readable medium1080can 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 circuitry1070. Device readable medium1080can 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 circuitry1070and, utilized by network node1060. Device readable medium1080can be used to store any calculations made by processing circuitry1070and/or any data received via interface1090. In some embodiments, processing circuitry1070and device readable medium1080can be considered to be integrated.

Interface1090is used in the wired or wireless communication of signaling and/or data between network node1060, network1006, and/or WDs1010. As illustrated, interface1090comprises port(s)/terminal(s)1094to send and receive data, for example to and from network1006over a wired connection. Interface1090also includes radio front end circuitry1092that can be coupled to, or in certain embodiments a part of, antenna1062. Radio front end circuitry1092comprises filters1098and amplifiers1096. Radio front end circuitry1092can be connected to antenna1062and processing circuitry1070. Radio front end circuitry can be configured to condition signals communicated between antenna1062and processing circuitry1070. Radio front end circuitry1092can receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry1092can convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters1098and/or amplifiers1096. The radio signal can then be transmitted via antenna1062. Similarly, when receiving data, antenna1062can collect radio signals which are then converted into digital data by radio front end circuitry1092. The digital data can be passed to processing circuitry1070. In other embodiments, the interface can comprise different components and/or different combinations of components.

In certain alternative embodiments, network node1060may not include separate radio front end circuitry1092, instead, processing circuitry1070can comprise radio front end circuitry and can be connected to antenna1062without separate radio front end circuitry1092. Similarly, in some embodiments, all or some of RF transceiver circuitry1072can be considered a part of interface1090. In still other embodiments, interface1090can include one or more ports or terminals1094, radio front end circuitry1092, and RF transceiver circuitry1072, as part of a radio unit (not shown), and interface1090can communicate with baseband processing circuitry1074, which is part of a digital unit (not shown).

Antenna1062can include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna1062can be coupled to radio front end circuitry1090and can be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna1062can 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, and a panel antenna can be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna can be referred to as MIMO. In certain embodiments, antenna1062can be separate from network node1060and can be connectable to network node1060through an interface or port.

Antenna1062, interface1090, and/or processing circuitry1070can 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, antenna1062, interface1090, and/or processing circuitry1070can 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 circuitry1087can comprise, or be coupled to, power management circuitry and can be configured to supply the components of network node1060with power for performing the functionality described herein. Power circuitry1087can receive power from power source1086. Power source1086and/or power circuitry1087can be configured to provide power to the various components of network node1060in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source1086can either be included in, or external to, power circuitry1087and/or network node1060. For example, network node1060can 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 circuitry1087. As a further example, power source1086can comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry1087. 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.

Alternative embodiments of network node1060can include additional components beyond those shown inFIG.13that 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. For example, network node1060can include user interface equipment to allow and/or facilitate input of information into network node1060and to allow and/or facilitate output of information from network node1060. This can allow and/or facilitate a user to perform diagnostic, maintenance, repair, and other administrative functions for network node1060.

Furthermore, various network functions (NFs, e.g., UDM, AAnF, AUSF, etc.) described herein can be implemented with and/or hosted by different variants of network node1060, including those variants described above.

In some embodiments, a wireless device (WD, e.g., WD1010) can be configured to transmit and/or receive information without direct human interaction. For instance, 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 (IoT) devices, vehicle-mounted wireless terminal devices, etc.

A WD can support device-to-device (D2D) communication, for example by implementing a 3GPP 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. As yet another specific example, in an Internet of Things (IoT) scenario, 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. As one particular example, the WD can be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard. Particular examples of such 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.). In other scenarios, 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.

As illustrated, wireless device1010includes antenna1011, interface1014, processing circuitry1020, device readable medium1030, user interface equipment1032, auxiliary equipment1034, power source1036and power circuitry1037. WD1010can include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD1010, 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 WD1010.

Antenna1011can include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface1014. In certain alternative embodiments, antenna1011can be separate from WD1010and be connectable to WD1010through an interface or port. Antenna1011, interface1014, and/or processing circuitry1020can 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. In some embodiments, radio front end circuitry and/or antenna1011can be considered an interface.

As illustrated, interface1014comprises radio front end circuitry1012and antenna1011. Radio front end circuitry1012comprise one or more filters1018and amplifiers1016. Radio front end circuitry1014is connected to antenna1011and processing circuitry1020and can be configured to condition signals communicated between antenna1011and processing circuitry1020. Radio front end circuitry1012can be coupled to or a part of antenna1011. In some embodiments, WD1010may not include separate radio front end circuitry1012; rather, processing circuitry1020can comprise radio front end circuitry and can be connected to antenna1011. Similarly, in some embodiments, some or all of RF transceiver circuitry1022can be considered a part of interface1014. Radio front end circuitry1012can receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry1012can convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters1018and/or amplifiers1016. The radio signal can then be transmitted via antenna1011. Similarly, when receiving data, antenna1011can collect radio signals which are then converted into digital data by radio front end circuitry1012. The digital data can be passed to processing circuitry1020. In other embodiments, the interface can comprise different components and/or different combinations of components.

Processing circuitry1020can 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 WD1010functionality either alone or in combination with other WD1010components, such as device readable medium1030. Such functionality can include any of the various wireless features or benefits discussed herein.

For example, processing circuitry1020can execute instructions stored in device readable medium1030or in memory within processing circuitry1020to provide the functionality disclosed herein. More specifically, instructions (also referred to as a computer program product) stored in medium1030can include instructions that, when executed by processor1020, can configure wireless device1010to perform operations corresponding to various exemplary methods (e.g., procedures) described herein.

As illustrated, processing circuitry1020includes one or more of RF transceiver circuitry1022, baseband processing circuitry1024, and application processing circuitry1026. In other embodiments, the processing circuitry can comprise different components and/or different combinations of components. In certain embodiments processing circuitry1020of WD1010can comprise a SOC. In some embodiments, RF transceiver circuitry1022, baseband processing circuitry1024, and application processing circuitry1026can be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry1024and application processing circuitry1026can be combined into one chip or set of chips, and RF transceiver circuitry1022can be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry1022and baseband processing circuitry1024can be on the same chip or set of chips, and application processing circuitry1026can be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry1022, baseband processing circuitry1024, and application processing circuitry1026can be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry1022can be a part of interface1014. RF transceiver circuitry1022can condition RF signals for processing circuitry1020.

Processing circuitry1020can 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 circuitry1020, can include processing information obtained by processing circuitry1020by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD1010, 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 medium1030can 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 circuitry1020. Device readable medium1030can 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 circuitry1020. In some embodiments, processing circuitry1020and device readable medium1030can be considered to be integrated.

User interface equipment1032can include components that allow and/or facilitate a human user to interact with WD1010. Such interaction can be of many forms, such as visual, audial, tactile, etc. User interface equipment1032can be operable to produce output to the user and to allow and/or facilitate the user to provide input to WD1010. The type of interaction can vary depending on the type of user interface equipment1032installed in WD1010. For example, if WD1010is a smart phone, the interaction can be via a touch screen; if WD1010is 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). User interface equipment1032can include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment1032can be configured to allow and/or facilitate input of information into WD1010and is connected to processing circuitry1020to allow and/or facilitate processing circuitry1020to process the input information. User interface equipment1032can 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 equipment1032is also configured to allow and/or facilitate output of information from WD1010, and to allow and/or facilitate processing circuitry1020to output information from WD1010. User interface equipment1032can 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 equipment1032, WD1010can communicate with end users and/or the wireless network and allow and/or facilitate them to benefit from the functionality described herein.

Power source1036can, 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. WD1010can further comprise power circuitry1037for delivering power from power source1036to the various parts of WD1010which need power from power source1036to carry out any functionality described or indicated herein. Power circuitry1037can in certain embodiments comprise power management circuitry. Power circuitry1037can additionally or alternatively be operable to receive power from an external power source; in which case WD1010can 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 circuitry1037can also in certain embodiments be operable to deliver power from an external power source to power source1036. This can be, for example, for the charging of power source1036. Power circuitry1037can perform any converting or other modification to the power from power source1036to make it suitable for supply to the respective components of WD1010.

InFIG.14, UE1100includes processing circuitry1101that is operatively coupled to input/output interface1105, radio frequency (RF) interface1109, network connection interface1111, memory1115including random access memory (RAM)1117, read-only memory (ROM)1119, and storage medium1121or the like, communication subsystem1131, power source1133, and/or any other component, or any combination thereof. Storage medium1121includes operating system1123, application program1125, and data1127. In other embodiments, storage medium1121can include other similar types of information. Certain UEs can utilize all of the components shown inFIG.17, 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.

InFIG.14, processing circuitry1101can be configured to process computer instructions and data. Processing circuitry1101can 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. For example, the processing circuitry1101can include two central processing units (CPUs). Data can be information in a form suitable for use by a computer.

In the depicted embodiment, input/output interface1105can be configured to provide a communication interface to an input device, output device, or input and output device. UE1100can be configured to use an output device via input/output interface1105. An output device can use the same type of interface port as an input device. For example, a USB port can be used to provide input to and output from UE1100. 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. UE1100can be configured to use an input device via input/output interface1105to allow and/or facilitate a user to capture information into UE1100. 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 presence-sensitive 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. For example, the input device can be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

InFIG.14, RF interface1109can be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface1111can be configured to provide a communication interface to network1143a. Network1143acan 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. For example, network1143acan comprise a Wi-Fi network. Network connection interface1111can 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 interface1111can 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.

RAM1117can be configured to interface via bus1102to processing circuitry1101to 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. ROM1119can be configured to provide computer instructions or data to processing circuitry1101. For example, ROM1119can 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 medium1121can 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.

In one example, storage medium1121can be configured to include operating system1123; application program1125such as a web browser application, a widget or gadget engine or another application; and data file1127. Storage medium1121can store, for use by UE1100, any of a variety of various operating systems or combinations of operating systems. For example, application program1125can include executable program instructions (also referred to as a computer program product) that, when executed by processor1101, can configure UE1100to perform operations corresponding to various exemplary methods (e.g., procedures) described herein.

InFIG.14, processing circuitry1101can be configured to communicate with network1143busing communication subsystem1131. Network1143aand network1143bcan be the same network or networks or different network or networks. Communication subsystem1131can be configured to include one or more transceivers used to communicate with network1143b. For example, communication subsystem1131can 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. Each transceiver can include transmitter1133and/or receiver1135to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter1133and receiver1135of each transceiver can share circuit components, software or firmware, or alternatively can be implemented separately.

In the illustrated embodiment, the communication functions of communication subsystem1131can 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. For example, communication subsystem1131can include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network1143bcan 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. For example, network1143bcan be a cellular network, a Wi-Fi network, and/or a near-field network. Power source1113can be configured to provide alternating current (AC) or direct current (DC) power to components of UE1100.

The features, benefits and/or functions described herein can be implemented in one of the components of UE1100or partitioned across multiple components of UE1100. Further, the features, benefits, and/or functions described herein can be implemented in any combination of hardware, software, or firmware. In one example, communication subsystem1131can be configured to include any of the components described herein. Further, processing circuitry1101can be configured to communicate with any of such components over bus1102. In another example, any of such components can be represented by program instructions stored in memory that when executed by processing circuitry1101perform the corresponding functions described herein. In another example, the functionality of any of such components can be partitioned between processing circuitry1101and communication subsystem1131. In another example, 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.

The functions can be implemented by one or more applications1220(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. Applications1220are run in virtualization environment1200which provides hardware1230comprising processing circuitry1260and memory1290. Memory1290contains instructions1295executable by processing circuitry1260whereby application1220is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

Virtualization environment1200can include general-purpose or special-purpose network hardware devices (or nodes)1230comprising a set of one or more processors or processing circuitry1260, 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 memory1290-1which can be non-persistent memory for temporarily storing instructions1295or software executed by processing circuitry1260. For example, instructions1295can include program instructions (also referred to as a computer program product) that, when executed by processing circuitry1260, can configure hardware node1220to perform operations corresponding to various exemplary methods (e.g., procedures) described herein. Such operations can also be attributed to virtual node(s)1220that is/are hosted by hardware node1230.

Each hardware device can comprise one or more network interface controllers (NICs)1270, also known as network interface cards, which include physical network interface1280. Each hardware device can also include non-transitory, persistent, machine-readable storage media1290-2having stored therein software1295and/or instructions executable by processing circuitry1260. Software1295can include any type of software including software for instantiating one or more virtualization layers1250(also referred to as hypervisors), software to execute virtual machines1240as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

Virtual machines1240, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and can be run by a corresponding virtualization layer1250or hypervisor. Different embodiments of the instance of virtual appliance1220can be implemented on one or more of virtual machines1240, and the implementations can be made in different ways.

During operation, processing circuitry1260executes software1295to instantiate the hypervisor or virtualization layer1250, which can sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer1250can present a virtual operating platform that appears like networking hardware to virtual machine1240.

As shown inFIG.15, hardware1230can be a standalone network node with generic or specific components. Hardware1230can comprise antenna12225and can implement some functions via virtualization. Alternatively, hardware1230can 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 applications1220.

In the context of NFV, virtual machine1240can 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 machines1240, and that part of hardware1230that 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 machines1240, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines1240on top of hardware networking infrastructure1230and corresponds to application1220inFIG.15.

In some embodiments, one or more radio units12200that each include one or more transmitters12220and one or more receivers12210can be coupled to one or more antennas12225. Radio units12200can communicate directly with hardware nodes1230via 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.

In some embodiments, some signaling can be performed via control system12230, which can alternatively be used for communication between the hardware nodes1230and radio units12200.

Furthermore, various network functions (NFs, e.g., UDM, AMF, AUSF, AAA-S, etc.) described herein can be implemented with and/or hosted by different variants of hardware1230, including those variants described above.

With reference toFIG.16, in accordance with an embodiment, a communication system includes telecommunication network1310, such as a 3GPP-type cellular network, which comprises access network1311, such as a radio access network, and core network1314. Access network1311comprises a plurality of base stations1312a,1312b,1312c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area1313a,1313b,1313c. Each base station1312a,1312b,1312cis connectable to core network1314over a wired or wireless connection1315. A first UE1391located in coverage area1313ccan be configured to wirelessly connect to, or be paged by, the corresponding base station1312c. A second UE1392in coverage area1313ais wirelessly connectable to the corresponding base station1312a. While a plurality of UEs1391,1392are 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 network1310is itself connected to host computer1330, 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 computer1330can 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. Connections1321and1322between telecommunication network1310and host computer1330can extend directly from core network1314to host computer1330or can go via an optional intermediate network1320. Intermediate network1320can be one of, or a combination of more than one of, a public, private or hosted network; intermediate network1320, if any, can be a backbone network or the Internet; in particular, intermediate network1320can comprise two or more sub-networks (not shown).

The communication system ofFIG.16as a whole enables connectivity between the connected UEs1391,1392and host computer1330. The connectivity can be described as an over-the-top (OTT) connection1350. Host computer1330and the connected UEs1391,1392are configured to communicate data and/or signaling via OTT connection1350, using access network1311, core network1314, any intermediate network1320and possible further infrastructure (not shown) as intermediaries. OTT connection1350can be transparent in the sense that the participating communication devices through which OTT connection1350passes are unaware of routing of uplink and downlink communications. For example, base station1312may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer1330to be forwarded (e.g., handed over) to a connected UE1391. Similarly, base station1312need not be aware of the future routing of an outgoing uplink communication originating from the UE1391towards the host computer1330.

Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference toFIG.17. In communication system1400, host computer1410comprises hardware1415including communication interface1416configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system1400. Host computer1410further comprises processing circuitry1418, which can have storage and/or processing capabilities. In particular, processing circuitry1418can 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 computer1410further comprises software1411, which is stored in or accessible by host computer1410and executable by processing circuitry1418. Software1411includes host application1412. Host application1412can be operable to provide a service to a remote user, such as UE1430connecting via OTT connection1450terminating at UE1430and host computer1410. In providing the service to the remote user, host application1412can provide user data which is transmitted using OTT connection1450.

Communication system1400can also include base station1420provided in a telecommunication system and comprising hardware1425enabling it to communicate with host computer1410and with UE1430. Hardware1425can include communication interface1426for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system1400, as well as radio interface1427for setting up and maintaining at least wireless connection1470with UE1430located in a coverage area (not shown inFIG.17) served by base station1420. Communication interface1426can be configured to facilitate connection1460to host computer1410. Connection1460can be direct, or it can pass through a core network (not shown inFIG.17) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware1425of base station1420can also include processing circuitry1428, 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 station1420also includes software1421stored internally or accessible via an external connection. For example, software1421can include program instructions (also referred to as a computer program product) that, when executed by processing circuitry1428, can configure base station1420to perform operations corresponding to various exemplary methods (e.g., procedures) described herein.

Communication system1400can also include UE1430already referred to, whose hardware1435can include radio interface1437configured to set up and maintain wireless connection1470with a base station serving a coverage area in which UE1430is currently located. Hardware1435of UE1430can also include processing circuitry1438, 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.

UE1430also includes software1431, which is stored in or accessible by UE1430and executable by processing circuitry1438. Software1431includes client application1432. Client application1432can be operable to provide a service to a human or non-human user via UE1430, with the support of host computer1410. In host computer1410, an executing host application1412can communicate with the executing client application1432via OTT connection1450terminating at UE1430and host computer1410. In providing the service to the user, client application1432can receive request data from host application1412and provide user data in response to the request data. OTT connection1450can transfer both the request data and the user data. Client application1432can interact with the user to generate the user data that it provides. Software1431can also include program instructions (also referred to as a computer program product) that, when executed by processing circuitry1438, can configure UE1430to perform operations corresponding to various exemplary methods (e.g., procedures) described herein.

As an example, host computer1410, base station1420and UE1430illustrated inFIG.17can be similar or identical to host computer1330, one of base stations1312a-cand one of UEs1391-1392ofFIG.16, respectively. This is to say, the inner workings of these entities can be as shown inFIG.17and independently, the surrounding network topology can be that shown inFIG.16.

InFIG.17, OTT connection1450has been drawn abstractly to illustrate the communication between host computer1410and UE1430via base station1420, 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 UE1430or from the service provider operating host computer1410, or both. While OTT connection1450is active, 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 connection1470between UE1430and base station1420is 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 UE1430using OTT connection1450, in which wireless connection1470forms the last segment. More precisely, 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. These and other advantages can facilitate more timely design, implementation, and deployment of 5G/NR solutions. Furthermore, such embodiments can facilitate flexible and timely control of data session QoS, which can lead to improvements in capacity, throughput, latency, etc. that are envisioned by 5G/NR and important for the growth of OTT services.

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. There can further be an optional network functionality for reconfiguring OTT connection1450between host computer1410and UE1430, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection1450can be implemented in software1411and hardware1415of host computer1410or in software1431and hardware1435of UE1430, or both. In embodiments, sensors (not shown) can be deployed in or in association with communication devices through which OTT connection1450passes; 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 software1411,1431can compute or estimate the monitored quantities. The reconfiguring of OTT connection1450can include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station1420, and it can be unknown or imperceptible to base station1420. Such procedures and functionalities can be known and practiced in the art. In certain embodiments, measurements can involve proprietary UE signaling facilitating host computer1410's measurements of throughput, propagation times, latency and the like. The measurements can be implemented in that software1411and1431causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection1450while it monitors propagation times, errors, etc.

FIG.19is a flowchart illustrating an exemplary method and/or procedure implemented in a communication system, in accordance with one embodiment. 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 toFIG.16will be included in this section. In step1610of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step1620, 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. In step1630(which can be optional), the UE receives the user data carried in the transmission.

FIG.20is a flowchart illustrating an exemplary method and/or procedure implemented in a communication system, in accordance with one embodiment. 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 toFIG.20will be included in this section. In step1710(which can be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step1720, the UE provides user data. In substep1721(which can be optional) of step1720, the UE provides the user data by executing a client application. In substep1711(which can be optional) of step1710, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application can further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep1730(which can be optional), transmission of the user data to the host computer. In step1740of 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.21is a flowchart illustrating an exemplary method and/or procedure implemented in a communication system, in accordance with one embodiment. 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 toFIG.21will be included in this section. In step1810(which can be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step1820(which can be optional), the base station initiates transmission of the received user data to the host computer. In step1830(which can be optional), the host computer receives the user data carried in the transmission initiated by the base station.

In addition, certain terms used in the present disclosure, including the specification, drawings and exemplary embodiments thereof, can be used synonymously in certain instances, including, but not limited to, e.g., data and information. It should be understood that, while these words and/or other words that can be synonymous to one another, can be used synonymously herein, that there can be instances when such words can be intended to not be used synonymously. Further, to the extent that the prior art knowledge has not been explicitly incorporated by reference herein above, it is explicitly incorporated herein in its entirety. All publications referenced are incorporated herein by reference in their entireties.