Indication of change to or validity of a license

The method improves licensing management by using an application server, functionality exposure server, and licensing server to authenticate and allocate resources within cellular networks, addressing the challenge of inconsistent licensing and resource allocation in existing systems.

WO2024237829A1PCT designated stage expired Publication Date: 2024-11-21TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
PCT/SE2023/050493
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-17
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

Current licensing systems for applications are not standardized, making it difficult to consistently and predictably manage licenses for both internal and external resources, particularly in cellular communication networks, where resource allocation and quality-of-service classification are complex.

Method used

A method involving an application server, a functionality exposure server, and a licensing server that authenticates user equipment, derives network identifiers, and generates license messages to allocate resources and manage subscription changes, using standardized interfaces to ensure valid licenses and resource allocation within cellular communication networks.

Benefits of technology

This solution provides a standardized and predictable licensing system that ensures valid resource allocation and quality-of-service classification, enabling efficient management of licenses and resource allocation in cellular communication networks, enhancing the consistency and reliability of licensing across multiple applications.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure SE2023050493_21112024_PF_FP_ABST
    Figure SE2023050493_21112024_PF_FP_ABST
Patent Text Reader

Abstract

It is provided a method performed by an application server device (3). The method comprises: authenticating a user equipment, UE (2), by the application server device communicating with the UE for authenticating a user interacting with a UE part of an application (35) on the UE, corresponding to an application server part (37) of the application on the application server; deriving a network identifier being an identifier of the UE to a cellular communication network (9) comprising a functionality exposure server device (4) for the UE; transmitting an application license request to the functionality exposure server device, the application license request comprising the network identifier and an identifier of the application; and receiving an application license message from the functionality exposure server device, the application license message indicating that there is a valid license for the UE for the application.
Need to check novelty before this filing date? Find Prior Art

Description

INDICATION OF CHANGE TO OR VALIDITY OF A LICENSETECHNICAL FIELD

[0001] The present disclosure relates to a method performed by a system, a method performed by an application server device, a method performed by a functionality exposure server device, a method performed by a licensing server, an application server device, a functionality exposure server device, a licensing server, computer programs, computer program products.BACKGROUND

[0002] Many applications today make use of licenses for various purposes. The applications can be implemented partly on an application server device and partly in a user equipment UE, such as a smartphone, in the form of what is commonly referred to as an app. The licenses can be used for internal purposes, such as keeping track of subscription status, subscription tier, etc. for each user. Each application implements its own architecture for providing suitable licensing.

[0003] It would be of great benefit if licenses could also be applied for resources external to the application. Furthermore, it would be beneficial if also internal licensing could be provided in a consistent and predictable manner for multiple applications.SUMMARY

[0004] One object is to improve how licensing is provided for an application server device for resources internal and / or external to the application server device.

[0005] According to a first aspect, it is provided a method performed by a system comprising an application server device, a functionality exposure server device, and a licensing server device. The method comprises: authenticating a User Equipment, UE, by the application server, communicating with the UE, for authenticating a user interacting with a UE part of an application on the UE, corresponding to an application server part of the application on the application server device; deriving, by the application server device, a network identifier being an identifier of the UE to a cellular communication network comprising the functionality exposure server device;transmitting, by the application server device, an application license request to the functionality exposure server device, the application license request comprising the network identifier and an identifier of the application; generating, by the functionality exposure server device, an exposure license request based on the application license request; transmitting, by the functionality exposure server device, the exposure license request to the licensing server device; determining, by the licensing server device, that there is a valid license corresponding to the exposure license request; transmitting, by the licensing server device, an exposure license message to the functionality exposure server device, the exposure license message indicating that there is a valid license corresponding to the exposure license request; generating, by the functionality exposure server device, an application license message based on the exposure license message, the application license message indicating that there is a valid license for the UE for the application; and transmitting, by the functionality exposure server device, the application license message to the application server device.

[0006] According to a second aspect, it is provided a method performed by an application server device. The method comprises: authenticating a user equipment, UE, by the application server device communicating with the UE for authenticating a user interacting with a UE part of an application on the UE, corresponding to an application server part of the application on the application server; deriving a network identifier being an identifier of the UE to a cellular communication network comprising a functionality exposure server device for the UE; transmitting an application license request to the functionality exposure server device, the application license request comprising the network identifier and an identifier of the application; and receiving an application license message from the functionality exposure server device, the application license message indicating that there is a valid license for the UE for the application.

[0007] The deriving a network identifier may comprise receiving the network identifier from the UE.

[0008] The deriving a network identifier may comprise performing a lookup of the network identifier for the UE based on another identifier associated with the UE.

[0009] The application license message may comprise an indication of a right of resource allocation in the cellular communication network, in which case the method comprises: coordinating with the UE and the functionality exposure server device to perform the resource allocation for UE communication relating to the application.

[0010] Resources allocated through the resource allocation may comprise a network slice of the cellular communication network.[oon] Resources allocated through the resource allocation may comprise a use of a quality-of-service classification in the cellular communication network.

[0012] Resources allocated through the resource allocation may comprise localisation of the UE in the cellular communication network.

[0013] The method may further comprise: transmitting an application subscription request to the functionality exposure server device, the application subscription request comprising the identifier of the application, the application subscription request indicating that any change to a licence for the application should be notified to the application server device by the functionality exposure server device; and receiving, from the functionality exposure server device, an application notification of a change to a licence for the application.

[0014] According to a third aspect, it is provided an application server device comprising: processing circuitry; and a memory storing instructions that, when executed by the processing circuitry, cause the application server device to: authenticate a user equipment, UE, by the application server device communicating with the UE for authenticating a user interacting with a UE part of an application on the UE, corresponding to an application server part of the application on the application server; transmit an application license request to the functionality exposure server device, the application license request comprising the network identifier and an identifier of the application; and receive an application license message from the functionality exposure server device, the application license message indicating that there is a valid license for the UE for the application.

[0015] The instructions to derive a network identifier may comprise instructions that, when executed by the processing circuitry, cause the application server device to receive the network identifier from the UE.

[0016] The instructions to derive a network identifier may comprise instructions that, when executed by the processing circuitry, cause the communication enabler to perform a lookup of the network identifier for the UE based on another identifier associated with the UE.

[0017] The application license message may comprise an indication of a right of resource allocation in the cellular communication network, and the instructions comprise instructions that, when executed by the processing circuitry, cause the application server device to coordinate with the UE and the functionality exposure server device to perform the resource allocation for UE communication relating to the application.

[0018] Resources allocated through the resource allocation may comprise a network slice of the cellular communication network.

[0019] Resources allocated through the resource allocation may comprise a use of a quality-of-service classification in the cellular communication network.

[0020] Resources allocated through the resource allocation may comprise localisation of the UE in the cellular communication network.

[0021] The instructions may comprise instructions that, when executed by the processing circuitry, cause the application server device to: transmit an application subscription request to the functionality exposure server device, the application subscription request comprising the identifier of the application, the application subscription request indicating that any change to a licence for the application should be notified to the application server device by the functionality exposure server device; and receive, from the functionality exposure server device, an application notification of a change to a licence for the application.

[0022] According to a fourth aspect, it is provided a computer program. The computer program comprises computer program code which, when executed on an application server device causes the application server device to: authenticate a user equipment, UE, by the application server device communicating with the UE for authenticating a user interacting with a UE part of an application on the UE, corresponding to an application server part of the application on the application server; derive a network identifier being an identifier of the UE to a cellular communication network comprising a functionality exposure server device for the UE; transmit an application license request to the functionality exposure server device, the application license request comprising the network identifier and an identifier of the application; and receive an application license message from the functionality exposure server device, the application license message indicating that there is a valid license for the UE for the application.

[0023] According to a fifth aspect, it is provided a computer program product comprising a computer program according to the fourth aspect and a computer readable means comprising non-transitory memory in which the computer program is stored.

[0024] According to a sixth aspect, it is provided a method performed by a functionality exposure server device. The method comprises: receiving an application license request from an application server, the application comprising a network identifier being an identifier of a user equipment, UE, to a cellular communication network comprising the functionality exposure server device and an identifier of an application of the application server device; generating an exposure license request based on the application license request, the exposure license request comprising the identifier of the application; transmitting the exposure license request to a licensing server device; receiving an exposure license message from the licensing server device, the exposure license message indicating that there is a valid license corresponding to the exposure license request; generating an application license message based on the exposure license message, the application license indicating that there is a valid license for the UE for the application; and transmitting the application license message to the application server device.

[0025] The application license request may comprise a license key, indicating a requested right of resource allocation in the cellular communication network, wherein the exposure license message comprises an indication of a right of resource allocation in accordance with the license key. In this case, the generating the exposure application license message comprises including the indication of a right of resource allocation. Furthermore, the method then comprises: coordinating with the application server device to perform the resource allocation for UE communication relating to the application.

[0026] Resources allocated through the resource allocation may comprise a network slice of the cellular communication network.

[0027] Resources allocated through the resource allocation may comprise a use of a quality-of-service classification in the cellular communication network.

[0028] Resources allocated through the resource allocation may comprise localisation of the UE in the cellular communication network.

[0029] The method may further comprise: receiving an application subscription request from the application server device, the application subscription request comprising the identifier of the application, the application subscription request indicating that any change to a licence for the application should be notified to the application server device by the functionality exposure server device; transmitting an exposure subscription request to the licensing server device, the exposure subscription request indicating that any change to a licence for the application should be notified to the functionality exposure server device by the licensing server device, the exposure subscription request being based on the application, the exposure subscription request comprising the identifier of the application; and receiving, from the licensing server device, an exposure notification of a change to a licence for the application; and transmitting, to the application server device, based on the exposure notification, an application notification of the change to the licence for the application.

[0030] According to a seventh aspect, it is provided a functionality exposure server device comprising: processing circuitry; and a memory storing instructions that, whenexecuted by the processing circuitry, cause the functionality exposure server device to: receive an application license request from an application server device, the application license request comprising a network identifier being an identifier of a user equipment, UE, to a cellular communication network comprising the functionality exposure server device and an identifier of an application of the application server device; generate an exposure license request based on the application license request, the exposure license request comprising the identifier of the application; transmit the exposure license request to a licensing server device; receive an exposure license message from the licensing server device, the exposure license message indicating that there is a valid license corresponding to the exposure license request; generate an application license message based on the exposure license message, the application license message indicating that there is a valid license for the UE for the application; and transmit the application license message to the application server device.

[0031] The application license request may comprise a license key, indicating a requested right of resource allocation in the cellular communication network, wherein the exposure license message comprises an indication of a right of resource allocation in accordance with the license key. In this case, the instructions to generate the exposure application license message comprise instructions that, when executed by the processing circuitry, cause the functionality exposure server device to include the indication of a right of resource allocation. Also, the instructions then comprise instructions that, when executed by the processing circuitry, cause the functionality exposure server device to coordinate with the application server device to perform the resource allocation for UE communication relating to the application.

[0032] Resources allocated through the resource allocation may comprise a network slice of the cellular communication network.

[0033] Resources allocated through the resource allocation may comprise a use of a quality-of-service classification in the cellular communication network.

[0034] Resources allocated through the resource allocation may comprise localisation of the UE in the cellular communication network.

[0035] The functionality exposure server may further comprise instructions that, when executed by the processing circuitry, cause the functionality exposure server device to: receive an application subscription request from the application server device, the application subscription request comprising the identifier of the application, the application subscription request indicating that any change to a licence for the application should be notified to the application server device by the functionality exposure server device; transmit an exposure subscription request to the licensing server device, the exposure subscription request indicating that any change to a licence for the application should be notified to the functionality exposure server device by the licensing server device, the exposure subscription request being based on the application subscription request, the exposure subscription request comprising the identifier of the application; receive, from the licensing server device, an exposure notification of a change to a licence for the application; and transmit, to the application server device, based on the exposure notification, an application notification of the change to the licence for the application.

[0036] According to an eighth aspect, it is provided a computer program comprising computer program code which, when executed on a functionality exposure server device causes the functionality exposure server device to: receive an application license request from an application server device, the application license request comprising a network identifier being an identifier of a user equipment, UE, to a cellular communication network comprising the functionality exposure server device and an identifier of an application of the application server device; generate an exposure license request based on the application license request, the exposure license request comprising the identifier of the application; transmit the exposure license request to a licensing server device; receive an exposure license message from the licensing server device, the exposure license message indicating that there is a valid license corresponding to the exposure license request; generate an application license message based on the exposure license message, the application license message indicating that there is a valid license for the UE for the application; and transmit the application license message to the application server device.

[0037] According to a ninth aspect, it is provided a computer program product comprising a computer program according to the eighth aspect and a computer readable means comprising non-transitory memory in which the computer program is stored.

[0038] According to a tenth aspect, it is provided a method performed by a licensing server device. The method comprises: receiving an exposure license request from a functionality exposure server device, the exposure license request comprising the identifier of an application; determining that there is a valid license corresponding to the exposure license request; and transmitting an exposure license message to the functionality exposure server device, the exposure license message indicating that there is a valid license corresponding to the exposure license request.

[0039] The method may comprise: receiving an exposure subscription request from the functionality exposure server device, the exposure subscription request comprising the identifier of the application, the exposure subscription request indicating that any change to a licence for the application should be notified to the functionality exposure server device by the licensing server device; determining that a change has occurred to a licence for the application; and transmitting, to the functionality exposure server device, an exposure notification of the change to the licence for the application.

[0040] According to an eleventh aspect, it is provided a licensing server device for providing a license. The licensing server device comprises: processing circuitry; and a memory storing instructions that, when executed by the processing circuitry, cause the licensing server device to: receive an exposure license request from a functionality exposure server device, the exposure license request comprising the identifier of an application; determine that there is a valid license corresponding to the exposure license request; and transmit an exposure license message to the functionality exposure server device, the exposure license message indicating that there is a valid license corresponding to the exposure license request.

[0041] The instructions may comprise instructions that, when executed by the processing circuitry, cause the licensing server device to: receive an exposure subscription request from the functionality exposure server device, the exposure subscription request comprising the identifier of the application, the exposuresubscription request indicating that any change to a licence for the application should be notified to the functionality exposure server device by the licensing server device; determine that a change has occurred to a licence for the application; and transmit, to the functionality exposure server device, an exposure notification of the change to the licence for the application.

[0042] According to a twelfth aspect, it is provided a computer program for providing a license, the computer program comprising computer program code which, when executed on a licensing server device causes the licensing server device to: receive an exposure license request from a functionality exposure server device, the exposure license request comprising the identifier of an application; determine that there is a valid license corresponding to the exposure license request; and transmit an exposure license message to the functionality exposure server device, the exposure license message indicating that there is a valid license corresponding to the exposure license request.

[0043] According to a thirteenth aspect, it is provided a computer program product comprising a computer program according to the twelfth aspect and a computer readable means comprising non-transitory memory in which the computer program is stored.

[0044] Generally, all terms used in the claims are to be interpreted according to their ordinary meaning in the technical field, unless explicitly defined otherwise herein. All references to "a / an / the element, apparatus, component, means, step, etc." are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any method disclosed herein do not have to be performed in the exact order disclosed, unless explicitly stated.BRIEF DESCRIPTION OF THE DRAWINGS

[0045] Aspects and embodiments are now described, by way of example, with reference to the accompanying drawings, in which:

[0046] Fig 1 is a schematic diagram illustrating an environment in which embodiments presented herein can be applied;

[0047] Fig 2 is a schematic diagram illustrating application architecture that can be applied in the environment of Fig 1;

[0048] Figs 3A-C are swimlane diagrams illustrating embodiments of methods for supporting provisioning of a license, that can be applied in the environment of Fig 1;

[0049] Fig 4 is a schematic diagram illustrating components of the application server device, the functionality exposure server device, and the licensing server device of Fig 1 according to one embodiment;

[0050] Fig 5 is a schematic diagram showing functional modules of the application server device of Fig 1 according to one embodiment;

[0051] Fig 6 is a schematic diagram showing functional modules of the functionality exposure server device of Fig 1 according to one embodiment;

[0052] Fig 7 is a schematic diagram showing functional modules of the licensing server device of Fig 1 according to one embodiment; and

[0053] Fig 8 shows one example of a computer program product comprising computer readable means.DETAILED DESCRIPTION

[0054] The aspects of the present disclosure will now be described more fully hereinafter with reference to the accompanying drawings, in which certain embodiments of the invention are shown. These aspects may, however, be embodied in many different forms and should not be construed as limiting; rather, these embodiments are provided by way of example so that this disclosure will be thorough and complete, and to fully convey the scope of all aspects of invention to those skilled in the art. Like numbers refer to like elements throughout the description.

[0055] According to embodiments presented herein, a license server device is provided that exposes its services through a functionality exposure server device. Thisallows an application server device to exploit the functionality of the licensing server device through standardised interfaces via the functionality exposure server device. Moreover, a license provided by licensing server device can define right external to a requesting application, e.g. to access or gain priority access resources within a cellular communication network.

[0056] Fig 1 is a schematic diagram illustrating an environment in which embodiments presented herein can be applied. A cellular communication network 9 comprises a core network 13 and one or more radio network nodes 12.

[0057] The cellular communication network 9 may e.g. comply with any one or a combination of 5G NR (New Radio), 6G, LTE (Long Term Evolution), LTE Advanced, W-CDMA (Wideband Code Division Multiplex), EDGE (Enhanced Data Rates for GSM (Global System for Mobile communication) Evolution), GPRS (General Packet Radio Service), CDMA2000 (Code Division Multiple Access 2000), or any other current or future wireless network, as long as the principles described hereinafter are applicable. Resources in the cellular communication network 9 can be selectively allocated. For instance the cellular communication network 9 can support network slices, where each slice can be defined to have specific characteristics, e.g. in terms of bandwidth, latency, etc. Another resource aspect of the cellular communication network is quality-of-service (QoS), where a UE that awarded a higher priority QoS is provided with higher priority for its communication compared to lower priority QoS.

[0058] The radio network nodes 12 are in the form of radio base stations being g Node Bs, also known as gNBs. The radio network node 1 could also be in the form of eNode Bs, Node Bs, BTSs (Base Transceiver Stations) and / or BSSs (Base Station Subsystems), etc. The radio network node 1 provides radio connectivity over a wireless interface to instances of user equipment (UE) 2. The term UE is also known as mobile communication terminal, wireless terminal, mobile terminal, user terminal, user agent, wireless terminal, machine-to-machine device etc., and can be, for example, what today are commonly known as a mobile phone, a smartphone, an internet-of-things (loT) device, or a tablet / laptop with wireless connectivity. The loT device maybe a vehicle, a TV, an electricity meter, a wearable such as a smart watch, a smart speaker, a medical device, a camera, a virtual reality / augmented reality (VR / AR) headset, a homeautomation device like a smart thermostat, a smart light device or other sensor or actuator.

[0059] An application server device 3 is provided as a server computer that is capable of communicating with the core network 13, as well as with the UE 2 via the cellular communication network 9 as a whole.

[0060] Only selected parts of the core network 13 are illustrated in Fig 1 to focus on embodiments presented herein. Specifically, there are a number of server devices 5, 5’ that are part of the core network 13. These server devices 5, 5’ can provide services that are of interest to the application server device 3, such as localisation, billing, etc. One server device that is of interest to embodiments presented herein is a license server 5.

[0061] The license server device 5 maintains licenses for use by one or more application server device 3 and optionally for other entities, such as other entities of the core network 13 e.g. for managing subscriber licenses.

[0062] In practice, the licenses can be in the form of a license key file containing all license keys available for a set of features.

[0063] When requested, the license server device 5 can look up the status of a particular license for a particular application of an application server device 3. It is to be noted that the licensing server device 5 itself does not need to perform any enforcement based on the license status, but it provides all necessary information to the application server device 3, which is the entity that is responsible for any license related enforcement.

[0064] A functionality exposure server device 4 forms part of the core network 13 and exposes services of the server devices 5, 5’ to entities outside the core network 13, such as for the application server device 3. The functionality exposure server device 4 and the server devices 5, 5’, forms part of an architecture that is sometimes called service base architecture (SBA). In a 5G network, the functionality exposure server device 4 can be implemented as a network exposure function (NEF). In an LTE network, the functionality exposure server device 4 can be implemented as a service capability exposure function (SCEF). The interface between the application server device 3 and thefunctionality exposure server device 4 is denoted Naf. The interface between the functionality exposure server device 4 and the licensing server device 5 is denoted Nlic.

[0065] By exposing the functionality of the licensing server device 5 using the functionality exposure server device 4, any application that can reach the functionality exposure server device 4 can also make use of the licensing server device 5 by means of standardised interfaces.

[0066] Applications of the application server device 3 can simplify their license management activities by exploiting the common interface to request and report the usage of licenses, as described in more detail below.

[0067] A system 1 is defined to comprise the application server device 3, the functionality exposure server device 4 and the licensing server device 5.

[0068] Fig 2 is a schematic diagram illustrating application architecture that can be applied in the environment of Fig 1. An application 35 is provided that comprises a UE part 36 that is performed on the UE 2 and an application server part 37 that is performed on the application server device 3. The UE part 36 of the application 35 is commonly referred to as an app. The UE part 36 and the application server part 37 communicate with each other using internet protocol (IP) traffic, e.g. over the cellular communication network 9 and / or a wide area network such as the Internet.

[0069] Figs 3A-C are swimlane diagrams illustrating embodiments of methods for supporting provisioning of a license, that can be applied in the environment of Fig 1. The swimlane diagrams can be considered to comprise flow charts, in the separate vertical swimlanes, for methods in the application server device 3, functionality exposure server device 4 and the licensing server device 5. Selected communication between the various entities is also shown. Communication between the UE 2 and the application server device 3 occurs based on IP communication, over the cellular communication network 9 and / or via a wide area network such as the Internet. Communication between the application server device 3 and the functionality exposure server device 4 can occur over the Naf interface, which can be provided on top of IP communication. Communicationbetween the functionality exposure server device 4 and the licensing server device 5 can occur via the Nlic interface, which can be provided on top of IP communication.

[0070] The UE 2 and the application server device 3 cooperate, in an authenticate step 340 by the UE 2 and in an interacting authenticate step 41 in the application server device 3, to authenticate the UE 2. This is achieved by communicating authentication data 20 between the UE 2 and the application server device 3 for authenticating a user 7. The user 7 interacts with a UE part 36 of an application 35 on the UE 2, corresponding to an application server part 37 of the application 35 on the application server device 3, as illustrated in Fig 2 and described above. A first identifier is obtained in this way, where the first identifier is an identifier of the user 7 and / or the UE 2. This authentication can e.g. be an authentication of the UE 2 and / or the user 7, e.g. using biometric identification by the UE 2 or using a passcode (e.g. password or numerical sequence). This authentication does not need to be an authentication with the cellular communication network 9. Nevertheless, in one embodiment, this authentication results in the UE 2 providing its subscription permanent identifier (SUPI)), which is an identifier associated with the UE 2 for its interaction with the cellular communication network 9. This authentication results in an authenticated user 7 and / or UE 2 for the application 35.

[0071] The application server device 3 determines, on occasion, when it needs to request a license, after which the rest of the procedure of Fig 3A is performed. This can occur e.g. every time a user starts a new session in the app on the UE (the UE part 36 of the application 35) to communicate with the application server part 37 of the application. Alternatively or additionally, a license is requested periodically, e.g. once a day, once an hour, etc.

[0072] In a derive network ID step 42, the application server device 3 derives a network identifier being an identifier of the UE to a cellular communication network 9 comprising the functionality exposure server device 4. The network identifier can be derived based on the first identifier, being an identity of the UE or the user that is used in the authenticate step 41. The network identifier can e.g. be in the form of a SUPI.

[0073] Inone embodiment, the network identifier is derived simply by receiving the network identifier from the UE, e.g. the SUPI forming part of the authentication data 20.

[0074] In one embodiment, the network identifier comprises is derived by performing a lookup of the network identifier for the UE based on another identifier associated with the UE. The lookup can be performed by consulting a lookup table, or other database, that is located locally with the application server device 3, or that is remotely located.

[0075] In a transmit application license request step 44, the application server device 3 transmits an application license request 21 to the functionality exposure server device 4. The application license request 21 (denoted Nnef_LicenseRequest) comprises the network identifier and an identifier of the application 35. Optionally, the application license request 21 also comprises a license key. The license key indicates a requested right of resource allocation in the cellular communication network 9. In other words, the license key is an identifier key or activation code associated with one or more network features for which an associated license gives the right to use.

[0076] In a receive application license request step 142, the functionality exposure server device 4 receives the application license request 21 from the application server device 3.

[0077] In a generate exposure license request step 144, the functionality exposure server device 4 generates an exposure license request 22 based on the application license request 21. The exposure license request 22 (denoted Nlic_LicenseRequest) can include the identifier of the application 35 and optionally the license key, from the application license request 21. The exposure license request 22 can also include a request identifier.

[0078] In a transmit exposure license request step 145, the functionality exposure server device 4 transmits the exposure license request 22 to the licensing server device 5-

[0079] In a receive exposure license request step 241, the licensing server device 5 receives the exposure license request 22 from the functionality exposure server device 4. The exposure license request 22 comprises the identifier of the application 35.

[0080] In a determine license step 242, the licensing server device 5 determines whether there is a valid license corresponding to the exposure license request 22, i.e. the licensing server device 5 obtains a license status of any license(s) corresponding to the exposure license request 22.

[0081] The license can define a particular service level for the application, and can be differentiated between different service levels in different tiers, e.g. for gold, silver and bronze tiers of user subscriptions. A higher tier can then imply higher priority in the network, e.g. through a low-latency and / or high bandwidth network slice, or a higher priority QoS classification. Another type of resource that can be defined by the license is access to a localisation service within the cellular communication network 9. A license can include its validity time.

[0082] Alternatively or additionally, the license defines licenses internal to the application, e.g. by containing explicit or implicit answers to the questions “does a particular user have permission to use the application? If so, what is their subscription tier?”

[0083] If a license has expired, this information is recorded as a result of the license query. If a license is valid, but there has reached its maximum capacity, this information is recorded as a result of the license query.

[0084] The license can be a data item that defines the rights that are awarded by the license. The license can be signed by the licensing server device 5 or other entity that the application server device 3 can trust, e.g. through a public key infrastructure (PKI).

[0085] In a transmit exposure license message step 244, the licensing server device 5 transmits an exposure license message 24 to the functionality exposure server device 4 The exposure license message 24 indicates the result of the determine license step 242. For instance, when there is a valid license, the exposure license message 24 indicates that there is a valid license corresponding to the exposure license request 22. When novalid license is found, the exposure license message comprises an indication that no license is found. The exposure license message 24 (denoted Nlic_LicenseRequestResponse) includes the license status and optionally the request identifier, and the identifier of the application 35.

[0086] In a receive exposure license message step 146, the functionality exposure server device 4 receives the exposure license message 24 from the licensing server device 5.

[0087] In a generate application license message step 148, the functionality exposure server device 4 generates an application license message 25 based on the exposure license message 24. The application license message 25 indicates the same license status that the exposure license message 24 indicates. For instance, when the exposure license message 24 indicates that there is a valid license for the UE 2 for the application 35, this is also indicated by the application license message 25, when the exposure license message 24 indicates that there is no valid license, this is also indicated by the application license message 25, etc. The application license message 25 (denoted Nnef_LicenseRequestResponse) can include the network identifier and the identifier of the application 35 and optionally the license key.

[0088] In a transmit application license message step 150, the functionality exposure server device 4 transmits the application license message 25 to the application server device 3.

[0089] In a receive application license response step 46, the application server device 3 receives the application license message 25 from the functionality exposure server device 4.

[0090] If the application license message 25 indicates a valid license, the application server device 3 acts according to the rights awarded by the license. When the license is a data item that is cryptographically signed, the application server device 3 can verify the integrity of the license by validating the cryptographic signature using a public key of the licensing server device 5 or other (by the application server device 3) trusted entity that applied the cryptographic signature.

[0091] If the application license message 25 indicates an expired license or insufficient capacity, the application server device 3 can deny service for the UE 2 (hard enforcement), or alternatively provide the service, e.g. with a warning message (soft enforcement).

[0092] Looking now to Fig 3B, only new or modified steps compared to Fig 3A will be described. In this embodiment, the exposure license message 24 and the application license message 25 comprise an indication of a right of resource allocation in the cellular communication network 9.

[0093] There are corresponding coordinate resource allocation steps 342, 48, and 152 in the UE 2, application server device 3, and functionality exposure server device 4, respectively.

[0094] In the coordinate resource allocation step 48 of the application server device 3, the application server device 3 coordinates with the UE 2 and the functionality exposure server device 4 to perform the resource allocation for UE communication relating to the application 35.

[0095] In the coordinate resource allocation step 342 of the UE 2, the UE 2 performs suitable procedures to implement and / or utilise the resource allocation.

[0096] In the coordinate resource allocation of the functionality exposure server device 4, the functionality exposure server device 4 coordinates with the application server device 3 to perform the resource allocation for UE communication relating to the application 35. The functionality exposure server device 4 also interacts with other nodes of the core network 13 to perform the allocation of the resources. The network identifier (e.g. SUPI) can be used here when needed for the allocation of the resources.

[0097] In this embodiment, earlier, the application license request 21 comprises a license key. The license key indicates a requested right of resource allocation in the cellular communication network 9. Furthermore, when the there is a valid license corresponding to the application license request, the exposure license message 24 comprises an indication of a right of resource allocation in accordance with the license key

[0098] The generate application license message step 148 then comprises including the indication of a right of resource allocation (from the exposure license message 24) in the application license message 25.

[0099] Resources allocated through the resource allocation can be any resource that is beneficial for the application.

[0100] In one embodiment, resources allocated through the resource allocation comprise a network slice of the cellular communication network 9.

[0101] Alternatively or additionally, resources allocated through the resource allocation comprise a use of a QoS classification in the cellular communication network 9-

[0102] Alternatively or additionally, resources allocated through the resource allocation comprise localisation of the UE in the cellular communication network 9.

[0103] Looking now to Fig 3C, this illustrates subscription and notification of license changes, that can be added to embodiments illustrated by Fig 3A and / or Fig 3B. This implements a publish-subscribe pattern. The steps of the upper part of Fig 3C, above the three dots, can be performed at any time in relation to the steps illustrated in Figs 3A-B. The steps of the lower part of Fig 3D, can be performed asynchronously, after the steps of the upper part of Fig 3C, whenever a license change is determined.

[0104] In a transmit application subscription request step 40, the application server device 3 transmits an application subscription request 30 to the functionality exposure server device 4. The application subscription request 30 (denoted Nnef_Lsmanagement_Subscribe) comprises the identifier of the application 35. The application subscription request 30 indicates that any change(s) to a licence / license for the application 35 should be notified to the application server device 3 by the functionality exposure server device 4.

[0105] In a receive application subscription request 140, the functionality exposure server device 4 receives the application subscription request 30 from the application server device 3.

[0106] In a transmit exposure subscription request step 141, the functionality exposure server device 4 transmits an exposure subscription request 32 to the licensing server device 5. The exposure subscription request 32 comprises the identifier of the application 35 received in the application subscription request 30. The exposure subscription request 32 indicates that any change(s) to a license / licenses for the application 35 should be notified to the functionality exposure server device 4 by the licensing server device 5. The exposure subscription request 32 (denoted Nlic_Lsmanagement_Subscribe) is based on the application subscription request 30. The exposure subscription request 32 comprises the identifier of the application 35.

[0107] In a receive exposure subscription request step 240, the licensing server device 5 receives an exposure subscription request 32 from the functionality exposure server device 4. The exposure subscription request 32 comprises the identifier of the application 35. The exposure subscription request 32 indicates that any change to a licence for the application 35 should be notified to the functionality exposure server device 4 by the licensing server device 5.

[0108] Although not shown, the licensing server device 5 and the functionality exposure server device 4 confirms the subscription back to the application server device 3-

[0109] At a later time, after a license change has occurred, a determine license change step 246 is triggered. In the determine license change step 246, the licensing server device 5 determines that a change has occurred to a licence for the application 35.

[0110] Here follows a set of examples of license changes that can be detected and form part of a notification as a notification type:

[0111] License expired (LS_EXPIRED): The license has expired. The license expiration date indicates that the license is expired. The license status is set to expired.

[0112] License valid (LS_VALID): The license became valid. Reasons for this change include that the license is ready for use, that an expired license became valid, or that a not-found license became available.

[0113] License is removed from the license server (LS_REMOVED).

[0114] License capacity change (LS_CAPACITY_CHANGE): The total available capacity units have changed.

[0115] License activation and / or expiration date change (LS_DATE_CHANGE): The activation and / or the expiration date of the license has changed without changing the license status (e.g. the license is still valid).

[0116] In a transmit exposure notification step 248, the licensing server device 5 transmits, to the functionality exposure server device 4, an exposure notification 33 of the change to the licence for the application 35. The exposure notification 33 (denoted Nlic_License_Notify) comprises the identifier of the application 35, a notification type and license information.

[0117] In a receive exposure notification step 154, the functionality exposure server device 4 receives, from the licensing server device 5, the exposure notification 33 of a change to a licence for the application 35.

[0118] In a transmit application notification step 156, the functionality exposure server device 4 transmits, to the application server device 3, based on the exposure notification 33, an application notification 34 of the change to the licence for the application. The application notification 34 (denoted Nnef_License_Notify) comprises the identifier of the application 35, a notification type and license information of the received exposure notification 33.

[0119] In a receive application notification step 50, the application server device 3 receives, from the functionality exposure server device 4, the application notification 34 of a change to a licence for the application 35.

[0120] Based on the type of notification received from the licensing server device 5 (via the functionality exposure server device 4), the application server device 3 takes proper action on the associated network service (or service level agreement) which affects the UE part 36 of the application 35. Alternatively or additionally, the applicationserver device 3 takes internal action with respect to UE part 36 of the application 35, e.g. blocking access due to an expired license.

[0121] When applicable, the application server device 3 can release a license and associated network services. The application server device 3 then frees a license to update the capacity. All resources that were allocated to the license (e.g. for a particular UE), e.g. slice or QoS, terminates and the license capacity is made available again. This is triggered by the application server device 3 to avoid a situation where licenses and related services are allocated even if the UE part 36 of the application 35 is not running.

[0122] When the UE part 36 of the application starts again, the application server device 3 starts the process again (see Fig 3A-B) to request a license to allow at UE part 36 of the application 35 to use the services according to the license (as before).

[0123] The termination message (not shown) (denoted Nnef_LSmanagement_Terminate)is transmitted from the application server device 3 to the functionality exposure server device 4 and from the functionality exposure server device 4 to the licensing server device 5 (then denoted Nlic_LSmanagement_Terminate). The termination message comprises the identifier of the application, a request identifier, a license type and a quantity. The license server responds to the functionality exposure server device 4 with a message (denoted Nlic_LSmanagement_TerminateResponse) that comprises the identifier of the application, the request identifier, the license type and the quantity, which is forwarded by the functionality exposure server device 4 to the application server device 3 (then denoted Nnef_LSmanagement_TerminateResponse).

[0124] Embodiments presented herein can be implemented by the following additions to specifications by the 3GPP (third generation partnership project).

[0125] A new REST (Representation State Transfer) interface is defined to integrate the license server interface NLic according to the SBA specification.

[0126] A new method is added on the NEF (i.e. functionality exposure server device 4) interface.

[0127] The change(s) to the NEF (i.e. functionality exposure server device 4) events can be incorporated in the specification 3GPP TS 29.517 V 2.0.0 (2022-12): 5G System; Application Function Event Exposure Service; Stage 3 (release 18) or later.

[0128] An enumeration NFType represents the different types of network functions that can be found in the 5G core network. The enumeration NFType is extended to include access to the licensing server device 5. Specifically, an additional table entry is added in Table 6.1.6.3.3-1 of the specification 3GPP TS 29.510 V18.2.0 (2023-03) Network Function Repository Services; Stage 3 (Release 18), or later.Table 1: Addition to enumeration NFType

[0129] New methods are defined for the application server device 3 to receive notification on change of status of licenses, to enable application server devices 3 to receive notifications on license change for a license key for which a subscription has been requested.Table 2: Nnef_LSmanagement Service Operations

[0130] NLic_Lsmanagement_Notify is the notification of the license changes from the licensing server device 5 to the functionality exposure server device 4 that shall forward the notification.Table 3: Nlic_LSmanagement Service Operations

[0131] For license termination, a message from the functionality exposure server device 4 to the NEF (i.e. the functionality exposure server device 4) and from NEF to the licensing server device 5 is provided for termination of dangling licenses.

[0132] This also, in turn, disables any feature associated with the subscriber if there is any associated with the request id.Table 4: Nnef_Lsmanagement Service OperationsTable 5: Nlic_Lsmanagement Service Operations

[0133] Using embodiments presented herein, the functionality exposure server device 4 provides a standard way for applications to interact with the core network functions. In this way, the applications can access license state and can optionally also be notified of licenses status changes used by each subscription. The solution can be extended in the future to support new use cases like the expansions of existing license to match the need of running application (in term of services requested or quality of service).

[0134] It is provided a flexible way to manage licenses of application features and / or network feature associated with applications. Licenses can be defined that are associated with core network features like slicing, QOS and / or other premium features of the network, creating a direct connection with the subscriptions.

[0135] By integrating the license server with the cellular communication network architecture, the services offered by the core network can be provided as premium services by the network operator to the application provider in a flexible manner.

[0136] Fig 4 is a schematic diagram illustrating components of the application server device 3, the functionality exposure server device 4, and the licensing server device 5 of Fig 1 according to one embodiment. Processing circuitry 60 is provided using any combination of one or more of a suitable central processing unit (CPU), graphics processing unit (GPU), multiprocessor, neural processing unit (NPU), microcontroller, digital signal processor (DSP), etc. capable of executing software instructions 67 stored in a memory 64, which can thus be a computer program product. The processing circuitry 60 could alternatively be implemented using an application specific integrated circuit (ASIC), field programmable gate array (FPGA), etc. The processing circuitry 60 can be configured to execute embodiments of the methods described with reference to Figs 3A-C above.

[0137] The memory 64 can be any combination of random-access memory (RAM) and / or read-only memory (ROM). The memory 64 also comprises non-transitory persistent storage, which, for example, can be any single one or combination of magnetic memory, optical memory, solid-state memory or even remotely mounted memory.

[0138] A data memory 66 is also provided for reading and / or storing data during execution of software instructions in the processing circuitry 60. The data memory 66 can be any combination of RAM and / or ROM.

[0139] An I / O interface 62 is provided for communicating with external and / or internal entities, e.g. based on Ethernet, optical fibre connections and / or suitable wireless connections.

[0140] Fig 5 is a schematic diagram showing functional modules of the application server device 3 of Fig 1 according to one embodiment. The modules are implemented using software instructions such as a computer program executing in the application server device 3. Alternatively or additionally, the modules are implemented usinghardware, such as any one or more of an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or discrete logical circuits. The modules correspond to the steps in the methods illustrated in Figs 3A-C.

[0141] An app. (application) sub. (subscription) req. (request) transmitter 70 corresponds to step 40. An obtainer 71 corresponds to step 41. An ID deriver 72 corresponds to step 42. An app. lie. (license) req. transmitter 74 corresponds to step 44. An app. lie. msg. (message) receiver 76 corresponds to step 44. A resource allocation coordinator 78 corresponds to step 48. An app. not. (notification) receiver 80 corresponds to step 50.

[0142] Fig 6 is a schematic diagram showing functional modules of the functionality exposure server device 4 of Fig 1 according to one embodiment. The modules are implemented using software instructions such as a computer program executing in the functionality exposure server device 4. Alternatively or additionally, the modules are implemented using hardware, such as any one or more of an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or discrete logical circuits. The modules correspond to the steps in the methods illustrated in Figs 3A-C.

[0143] An app. sub. Req. receiver 170 corresponds to step 140. An app. lie. req. receiver 172 corresponds to step 142. An exp. (exposure) lie. req. generator 174 corresponds to step 144. An exp. lie. req. transmitter 175 corresponds to step 145. An exp. lie. msg. receiver 176 corresponds to step 146. An app. lie. msg. generator 178 corresponds to step 148. An app. lie. msg. transmitter 180 corresponds to step 150. A resource allocation coordinator 182 corresponds to step 152. An exp. not. receiver 184 corresponds to step 154. An app. not. transmitter 186 corresponds to step 156.

[0144] Fig 7 is a schematic diagram showing functional modules of the licensing server device 5 of Fig 1 according to one embodiment. The modules are implemented using software instructions such as a computer program executing in the licensing server device 5. Alternatively or additionally, the modules are implemented using hardware, such as any one or more of an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or discrete logical circuits. The modules correspond to the steps in the methods illustrated in Figs 3A-C.

[0145] An exp. sub. req. receiver 270 corresponds to step 240. An exp. lie. req. receiver 271 corresponds to step 241. A license determiner 272 corresponds to step 242. An exp. lie. msg. transmitter 274 corresponds to step 244. A license change determiner 276 corresponds to step 246. An exp. not. transmitter 278 corresponds to step 248.

[0146] Fig 8 shows one example of a computer program product 90 comprising computer readable means. On this computer readable means, a computer program 91 can be stored in a non-transitory memory. The computer program can cause processing circuitry to execute a method according to embodiments described herein. In this example, the computer program product 90 is in the form of a removable solid-state memory, e.g. a Universal Serial Bus (USB) drive. As explained above, the computer program product could also be embodied in a memory of a device, such as the computer program product 64 of Fig 4. While the computer program 91 is here schematically shown as a section of the removable solid-state memory, the computer program can be stored in any way which is suitable for the computer program product, such as another type of removable solid-state memory, or an optical disc, such as a CD (compact disc), a DVD (digital versatile disc) or a Blu-Ray disc.

[0147] The aspects of the present disclosure have mainly been described above with reference to a few embodiments. However, as is readily appreciated by a person skilled in the art, other embodiments than the ones disclosed above are equally possible within the scope of the invention, as defined by the appended patent claims. Thus, while various aspects and embodiments have been disclosed herein, other aspects and embodiments will be apparent to those skilled in the art. The various aspects and embodiments disclosed herein are for purposes of illustration and are not intended to be limiting, with the true scope being indicated by the following claims.

Claims

CLAIMS i. A method performed by a system (i) comprising an application server device (3), a functionality exposure server device (4), and a licensing server device (5), the method comprising: authenticating (41) a User Equipment, UE, (2), by the application server device (3), communicating with the UE, (2) for authenticating a user interacting with a UE part (36) of an application (35) on the UE, corresponding to an application server part (37) of the application (35) on the application server device (3); deriving (42), by the application server device (3), a network identifier being an identifier of the UE to a cellular communication network (9) comprising the functionality exposure server device (4); transmitting (44), by the application server device (3), an application license request (21) to the functionality exposure server device (4), the application license request (21) comprising the network identifier and an identifier of the application (35); generating (144), by the functionality exposure server device (4), an exposure license request (22) based on the application license request (21); transmitting (145), by the functionality exposure server device (4), the exposure license request (22) to the licensing server device (5); determining (242), by the licensing server device (5), that there is a valid license corresponding to the exposure license request (22); transmitting (244), by the licensing server device (5), an exposure license message (24) to the functionality exposure server device (4), the exposure license message (24) indicating that there is a valid license corresponding to the exposure license request (22); generating (148), by the functionality exposure server device (4), an application license message (25) based on the exposure license message (24), the application license message (25) indicating that there is a valid license for the UE (2) for the application (35); and transmitting (150), by the functionality exposure server device (4), the application license message (25) to the application server device (3).

2. A method performed by an application server device (3), the method comprising: authenticating (41) a user equipment, UE, (2) by the application server device (3) communicating with the UE (2) for authenticating a user interacting with a UE part (36) of an application (35) on the UE, corresponding to an application server part (37) of the application (35) on the application server (3); deriving (42) a network identifier being an identifier of the UE to a cellular communication network (9) comprising a functionality exposure server device (4) for the UE; transmitting (44) an application license request (21) to the functionality exposure server device (4), the application license request (21) comprising the network identifier and an identifier of the application (35); and receiving (46) an application license message (25) from the functionality exposure server device (4), the application license message (25) indicating that there is a valid license for the UE (2) for the application (35).

3. The method according to claim 2, wherein the deriving (42) a network identifier comprises receiving the network identifier from the UE.

4. The method according to claim 2, wherein the deriving (42) a network identifier comprises performing a lookup of the network identifier for the UE based on another identifier associated with the UE.

5. The method according to any one of claims 2 to 4, wherein the application license message (25) comprises an indication of a right of resource allocation in the cellular communication network (9), and the method comprises: coordinating (48) with the UE (2) and the functionality exposure server device (4) to perform the resource allocation for UE communication relating to the application (35).

6. The method according to claim 5, wherein resources allocated through the resource allocation comprise a network slice of the cellular communication network (9).

7. The method according to claim 5 or 6, wherein resources allocated through the resource allocation comprise a use of a quality-of-service classification in the cellular communication network (9).

8. The method according to any one of claims 5 to 7, wherein resources allocated through the resource allocation comprise localisation of the UE in the cellular communication network (9).

9. The method according to any one of claims 2 to 8, further comprising: transmitting (40) an application subscription request (30) to the functionality exposure server device (4), the application subscription request (30) comprising the identifier of the application (35), the application subscription request (30) indicating that any change to a licence for the application (35) should be notified to the application server device (3) by the functionality exposure server device (4); and receiving (50), from the functionality exposure server device (4), an application notification (34) of a change to a licence for the application (35).

10. An application server device (3) comprising: processing circuitry (60); and a memory (64) storing instructions (67) that, when executed by the processing circuitry, cause the application server device (3) to: authenticate a user equipment, UE, (2) by the application server device (3) communicating with the UE (2) for authenticating a user interacting with a UE part (36) of an application (35) on the UE, corresponding to an application server part (37) of the application (35) on the application server (3); transmit an application license request (21) to the functionality exposure server device (4), the application license request (21) comprising the network identifier and an identifier of the application (35); and receive an application license message (25) from the functionality exposure server device (4), the application license message (25) indicating that there is a valid license for the UE (2) for the application (35).

11. The application server device (3) according to claim 10, wherein the instructions to derive a network identifier comprise instructions (67) that, when executed by theprocessing circuitry, cause the application server device (3) to receive the network identifier from the UE.

12. The application server device (3) according to claim 10, wherein the instructions to derive a network identifier comprise instructions (67) that, when executed by the processing circuitry, cause the communication enabler (1) to perform a lookup of the network identifier for the UE based on another identifier associated with the UE.

13. The application server device (3) according to any one of claims 10 to 12, wherein the application license message (25) comprises an indication of a right of resource allocation in the cellular communication network (9), and the instructions comprise instructions (67) that, when executed by the processing circuitry, cause the application server device (3) to coordinate with the UE (2) and the functionality exposure server device (4) to perform the resource allocation for UE communication relating to the application (35).

14. The application server device (3) according to claim 13, wherein resources allocated through the resource allocation comprise a network slice of the cellular communication network (9).

15. The application server device (3) according to claim 13 or 14, wherein resources allocated through the resource allocation comprise a use of a quality-of-service classification in the cellular communication network (9).

16. The application server device (3) according to any one of claims 13 to 15, wherein resources allocated through the resource allocation comprise localisation of the UE in the cellular communication network (9).

17. The application server device (3) according to any one of claims 10 to 16, wherein the instructions comprising instructions (67) that, when executed by the processing circuitry, cause the application server device (3) to: transmit an application subscription request (30) to the functionality exposure server device (4), the application subscription request (30) comprising the identifier of the application (35), the application subscription request (30) indicating that any change to a licence for the application (35) should be notified to the application serverdevice (3) by the functionality exposure server device (4); and receive, from the functionality exposure server device (4), an application notification (34) of a change to a licence for the application (35).

18. A computer program (67, 91), the computer program comprising computer program code which, when executed on an application server device (3) causes the application server device (3) to: authenticate a user equipment, UE, (2) by the application server device (3) communicating with the UE (2) for authenticating a user interacting with a UE part (36) of an application (35) on the UE, corresponding to an application server part (37) of the application (35) on the application server (3); derive a network identifier being an identifier of the UE to a cellular communication network (9) comprising a functionality exposure server device (4) for the UE; transmit an application license request (21) to the functionality exposure server device (4), the application license request (21) comprising the network identifier and an identifier of the application (35); and receive an application license message (25) from the functionality exposure server device (4), the application license message (25) indicating that there is a valid license for the UE (2) for the application (35).

19. A computer program product (64, 90) comprising a computer program according to claim 18 and a computer readable means comprising non-transitory memory in which the computer program is stored.

20. A method performed by a functionality exposure server device (4), the method comprising: receiving (142) an application license request (21) from an application server device (3), the application license request (21) comprising a network identifier being an identifier of a user equipment, UE, (2) to a cellular communication network (9) comprising the functionality exposure server device (4) and an identifier of an application (35) of the application server device (3); generating (144) an exposure license request (22) based on the application license request (21), the exposure license request (22) comprising the identifier of theapplication (35); transmitting (145) the exposure license request (22) to a licensing server device (5); receiving (146) an exposure license message (24) from the licensing server device (5), the exposure license message (24) indicating that there is a valid license corresponding to the exposure license request (22); generating (148) an application license message (25) based on the exposure license message (24), the application license message (25) indicating that there is a valid license for the UE (2) for the application (35); and transmitting (150) the application license message (25) to the application server device (3).

21. The method according to claim 20, wherein the application license request (21) comprises a license key, indicating a requested right of resource allocation in the cellular communication network (9), wherein the exposure license message (24) comprises an indication of a right of resource allocation in accordance with the license key; wherein the generating (148) the exposure application license message (25) comprises including the indication of a right of resource allocation; the method comprising: coordinating (152) with the application server device (3) to perform the resource allocation for UE communication relating to the application (35).

22. The method according to claim 21, wherein resources allocated through the resource allocation comprise a network slice of the cellular communication network (9).

23. The method according to claim 21 or 22, wherein resources allocated through the resource allocation comprise a use of a quality-of-service classification in the cellular communication network (9).

24. The method according to any one of claims 21 to 23, wherein resources allocated through the resource allocation comprise localisation of the UE in the cellular communication network (9).

25. The method according to any one of claims 20 to 24, further comprising: receiving (140) an application subscription request (30) from the application server device (3), the application subscription request (30) comprising the identifier of the application (35), the application subscription request (30) indicating that any change to a licence for the application (35) should be notified to the application server device (3) by the functionality exposure server device (4); transmitting (141) an exposure subscription request (32) to the licensing server device (5), the exposure subscription request (32) indicating that any change to a licence for the application (35) should be notified to the functionality exposure server device (4) by the licensing server device (5), the exposure subscription request (32) being based on the application subscription request (30), the exposure subscription request (32) comprising the identifier of the application (35); and receiving (154), from the licensing server device (5), an exposure notification (33) of a change to a licence for the application (35); and transmitting (156), to the application server device (3), based on the exposure notification (33), an application notification (34) of the change to the licence for the application.

26. A functionality exposure server device (4) comprising: processing circuitry (60); and a memory (64) storing instructions (67) that, when executed by the processing circuitry, cause the functionality exposure server device (4) to: receive an application license request (21) from an application server device (3), the application license request (21) comprising a network identifier being an identifier of a user equipment, UE, (2) to a cellular communication network (9) comprising the functionality exposure server device (4) and an identifier of an application (35) of the application server device (3); generate an exposure license request (22) based on the application license request (21), the exposure license request (22) comprising the identifier of the application (35); transmit the exposure license request (22) to a licensing server device (5); receive an exposure license message (24) from the licensing server device (5), the exposure license message (24) indicating that there is a valid license corresponding to the exposure license request (22);generate an application license message (25) based on the exposure license message (24), the application license message (25) indicating that there is a valid license for the UE (2) for the application (35); and transmit the application license message (25) to the application server device (3).

27. The functionality exposure server device (4) according to claim 26, wherein the application license request (21) comprises a license key, indicating a requested right of resource allocation in the cellular communication network (9), wherein the exposure license message (24) comprises an indication of a right of resource allocation in accordance with the license key; wherein the instructions to generate the exposure application license message (25) comprise instructions (67) that, when executed by the processing circuitry, cause the functionality exposure server device (4) to include the indication of a right of resource allocation; and wherein the instructions comprise instructions (67) that, when executed by the processing circuitry, cause the functionality exposure server device (4) to coordinate with the application server device (3) to perform the resource allocation for UE communication relating to the application (35).

28. The functionality exposure server device (4) according to claim 27, wherein resources allocated through the resource allocation comprise a network slice of the cellular communication network (9).

29. The functionality exposure server device (4) according to claim 27 or 28, wherein resources allocated through the resource allocation comprise a use of a quality-of- service classification in the cellular communication network (9).

30. The functionality exposure server device (4) according to any one of claims 27 to29, wherein resources allocated through the resource allocation comprise localisation of the UE in the cellular communication network (9).

31. The functionality exposure server device (4) according to any one of claims 26 to30, further comprising instructions (67) that, when executed by the processing circuitry, cause the functionality exposure server device (4) to:receive an application subscription request (30) from the application server device (3), the application subscription request (30) comprising the identifier of the application (35), the application subscription request (30) indicating that any change to a licence for the application (35) should be notified to the application server device (3) by the functionality exposure server device (4); transmit an exposure subscription request (32) to the licensing server device (5), the exposure subscription request (32) indicating that any change to a licence for the application (35) should be notified to the functionality exposure server device (4) by the licensing server device (5), the exposure subscription request (32) being based on the application subscription request (30), the exposure subscription request (32) comprising the identifier of the application (35); receive, from the licensing server device (5), an exposure notification (33) of a change to a licence for the application (35); and transmit, to the application server device (3), based on the exposure notification (33), an application notification (34) of the change to the licence for the application.

32. A computer program (67, 91) comprising computer program code which, when executed on a functionality exposure server device (4) causes the functionality exposure server device (4) to: receive an application license request (21) from an application server device (3), the application license request (21) comprising a network identifier being an identifier of a user equipment, UE, (2) to a cellular communication network (9) comprising the functionality exposure server device (4) and an identifier of an application (35) of the application server device (3); generate an exposure license request (22) based on the application license request (21), the exposure license request (22) comprising the identifier of the application (35); transmit the exposure license request (22) to a licensing server device (5); receive an exposure license message (24) from the licensing server device (5), the exposure license message (24) indicating that there is a valid license corresponding to the exposure license request (22); generate an application license message (25) based on the exposure license message (24), the application license message (25) indicating that there is a valid licensefor the UE (2) for the application (35); and transmit the application license message (25) to the application server device (3).

33. A computer program product (64, 90) comprising a computer program according to claim 32 and a computer readable means comprising non-transitory memory in which the computer program is stored.

34. A method performed by a licensing server device (5), the method comprising: receiving (241) an exposure license request (22) from a functionality exposure server device (4), the exposure license request (22) comprising the identifier of an application (35); determining (242) that there is a valid license corresponding to the exposure license request (22); and transmitting (244) an exposure license message (24) to the functionality exposure server device (4), the exposure license message (24) indicating that there is a valid license corresponding to the exposure license request (22).

35. The method according to claim 34, the method comprising: receiving (240) an exposure subscription request (32) from the functionality exposure server device (4), the exposure subscription request (32) comprising the identifier of the application (35), the exposure subscription request (32) indicating that any change to a licence for the application (35) should be notified to the functionality exposure server device (4) by the licensing server device (5); determining (246) that a change has occurred to a licence for the application (35); and transmitting (248), to the functionality exposure server device (4), an exposure notification (33) of the change to the licence for the application (35).

36. A licensing server device (5) for providing a license, the licensing server device (5) comprising: processing circuitry (60); and a memory (64) storing instructions (67) that, when executed by the processing circuitry, cause the licensing server device (5) to: receive an exposure license request (22) from a functionality exposure serverdevice (4), the exposure license request (22) comprising the identifier of an application (35); determine that there is a valid license corresponding to the exposure license request (22); and transmit an exposure license message (24) to the functionality exposure server device (4), the exposure license message (24) indicating that there is a valid license corresponding to the exposure license request (22).

37. The licensing server device (5) according to claim 36, wherein the instructions comprises instructions (67) that, when executed by the processing circuitry, cause the licensing server device (5) to: receive an exposure subscription request (32) from the functionality exposure server device (4), the exposure subscription request (32) comprising the identifier of the application (35), the exposure subscription request (32) indicating that any change to a licence for the application (35) should be notified to the functionality exposure server device (4) by the licensing server device (5); determine that a change has occurred to a licence for the application (35); and transmit, to the functionality exposure server device (4), an exposure notification (33) of the change to the licence for the application (35).

38. A computer program (67, 91) for providing a license, the computer program comprising computer program code which, when executed on a licensing server device (5) causes the licensing server device (5) to: receive an exposure license request (22) from a functionality exposure server device (4), the exposure license request (22) comprising the identifier of an application (35); determine that there is a valid license corresponding to the exposure license request (22); and transmit an exposure license message (24) to the functionality exposure server device (4), the exposure license message (24) indicating that there is a valid license corresponding to the exposure license request (22).39- A computer program product (64, 90) comprising a computer program according to claim 38 and a computer readable means comprising non-transitory memory in which the computer program is stored.

Citation Information

Patent Citations

  • Electronic License Management

    US20110289003A1

  • Subscription service of apps in the mobile market

    US20140236846A1

  • Systems and methods for application-friendly protocol data unit (PDU) session management

    US20180192471A1