GB2534576A

GB2534576A - Deferred service provisioning and withdrawal based on user equipment capabilities

Info

Publication number: GB2534576A
Application number: GB1501358.4A
Authority: GB
Inventors: Titcombe Steven; Azzopardi Daniel
Original assignee: Vodafone IP Licensing Ltd
Current assignee: Vodafone IP Licensing Ltd
Priority date: 2015-01-27
Filing date: 2015-01-27
Publication date: 2016-08-03
Also published as: GB201501358D0

Abstract

Apparatus and method for operating network infrastructure to control the provisioning of a network-provided functionality to a user equipment of a user having a subscription to a cellular telecommunications network is disclosed. The method comprises receiving, at the network infrastructure an instruction to provision a network-provided functionality to a user, updating a functionality entitlement and capability database to indicate that the user subscription is entitled to the functionality and checking the database to see if a user equipment of the user is capable of supporting the network-provided functionality. If the user equipment is capable of supporting the network-provided functionality, the network infrastructure is configured to provide the functionality to the user. If the user equipment is not or is not known to be capable of supporting the network-provided functionality, then configuration of the network infrastructure is deferred.

Description

DEFERRED SERVICE PROVISIONING AND WITHDRAWAL BASED ON USER

EQUIPMENT CAPABILITIES

FIELD OF THE INVENTION

[1] The present application relates to a system and method for provisioning services to user equipment in a mobile network.

BACKGROUND

[2] The use of portable electronic devices for wireless data and voice communications using a cellular telecommunications network, such as one operating in accordance with the 3G or 4G Long Term Evolution/ Long Term Evolution -Advanced (LTE/LTE-Advanced) telecommunications standards, has proliferated in recent years.

[3] Cellular telecommunications network operators provide access to wireless communications using the network by end users taking a subscription with the operator for data and voice communication services. The operators typically provide a user with a Universal Integrated Circuit Card (UICC) (typically a Subscriber Identity Module (SIM) card) that securely stores the international mobile subscriber identity (IMSI) field and the related key used to identify and authenticate subscribers on mobile telephony devices to the home location register (HLR) on the cellular telecommunications network.

[4] To access the subscribed network services, the user must insert the UICC into a wireless cellular network-enabled electronic device, such as a portable phone (e.g. a smartphone), tablet device, wireless dongle, laptop, etc, known collectively as the "user equipment", that then communicates with the cellular telecommunications network using the appropriately-enabled telecommunications protocols for that network and user equipment to perform voice and data plane communications therewith.

[5] Generally, current cellular telecommunications network infrastructure is provided by operators and arranged to provide user equipment with access to a Radio Access Network (RAN) via radio link to one of a network of base stations providing cellular radio coverage over a geographical area. The base stations of a RAN are coupled to a Core Network (CN) of the network operator that manages data -1 -traffic in communication with outside resources accessible e.g. via the Internet and routes voice calls for example via a Public Switched Telephone Network (PSTN) [6] Cellular telecommunications network providers typically provide a variety of different functionalities to subscribers to enhance their user experience and enable a Greater flexibility of use and interaction. The functionalities may be conceived of as "products", or they may better be considered as "services". For example, a number of "basic" functionalities are typically provided, which may include, amongst others, voice communications by cellular telephony, data communications, Short Messaging Service (SMS), and Multimedia Messaging Service (MMS) In addition, a number of more technically "advanced" functionalities may be provided, which may include, amongst others, Voice Over WFi (VoWiFi) or Voice Over Long Term Evolution (VoLTE).

[7] The ON typically includes a Home Location Register (HLR) which is a server resource storing, among others, International Mobile Equipment Identity (IMEI) numbers set by user equipment manufacturers and used to uniquely identify the subscribers' user equipment used during the process of registering devices to a user subscription on the network. The HLR is also configured to perform Automatic Device Detection (ADD), a technical service performed by the HLR when the subscriber's IMEI is found to be different to the IMEI value previously stored in the HLR in which case the HLR is updated. The ON typically also includes an Over The Air" (OTA) server that is used to apply network operator settings to the subscriber's user equipment (by "over the air" updates), based on the IMEI of the device (stored in the HLR). The OTA server may be used by the ON to communicate with the user equipment to configure it for use in the network and for interoperation to support the network-provided functionalities, [8] The functionalities a cellular telecommunications network operator provides to a user may be selected based on the subscription package a user elects. For example, some packages may include 4G services and VoWiFi or VoLTE. Typically, these functionalities are bundled together and a user is automatically provided with them through the network in use, whether or not the subscriber actually wants to use them, [9] There are broadly two ways in which provisioning of functionalities to subscribers in mobile networks is triggered: (i) by selecting a price plan on a billing system or (ii) selecting a product/service functionality from the product catalogue. -2 -

User selection of functionalities in this way is typically then communicated to the cellular telecommunications operators network infrastructure by the Customer Relationship Manager (CRM) system or agent that manages the billing system or orders through the product catalogue.

[10] As mentioned above, the price plan or product are ones based on customer choice and often have additional products and services which are "bundled in", which the customer may know nothing about and cannot use unless their device is capable of using them. For example, VoLTE or VoWiFi may be bundled in.

[11] On receiving these orders for network-provided functionalities, the network operator must provide resources such as infrastructure, bandwidth and hardware and software resources and configure the network infrastructure to provision the procured services to the appropriate subscribers and to support the potential end-user demand for these functionalities [12] In some cases, however, users may have purchased a price plan having bundled functionalities and the network is configured to provide the user those functionalities, despite the user still using user equipment to access the network that may not have the capabilities necessary to support the provisioning of those network-provided functionalities. For example, a user may have a subscription for 4G data services including VoWiFi and VoLTE, but may be using a non-4G compatible smartphone that is not capable of supporting 4G data communications or VoWiFi and VoLTE. In addition, a user may remove the UICC from a user equipment that is capable of supporting the bundled network-provided functionalities and insert it into another phone that does not have such capabilities (for example, the user may have damaged his or her smartphone and may revert to using an older phone).

[13] Thus in these situations the network operator typically configures the network infrastructure to provide network-enabled functionalities that are not being used by subscribers using user equipment that does not have the capability to do so. This can lead to a wasteful overprovisioning of resources by the network operators, that is inefficient and sub-optimal [14] In addition, the configuring of the network infrastructure to provide network-provided functionalities to users using user equipment that is not capable of supporting those functionalities can inadvertently cause the network to operate ineffectively for that end user. This can even lead to the network-provided functionalities that the user equipment does actually support to stop being provided

-

to the end user, causing the user equipment and network to appear to behave incorrectly, denying the subscriber access to functionalities they are expecting to be able to use.

[15] For example, the standards for VoLTE state that the VoLTE-enabled subscriber's Call Forward supplementary services are removed from the HLR and are controlled instead from the IP Multimedia Subsystem (IMS) multimedia telephony service (1v1MTEL) Application Server. Such a design requires the subscriber to have a VoLTE-capable user equipment in order to change their Call Forward settings from their handset. The problem arises when the subscriber is provisioned with VoLTE but does not use a VoLTE-capable user equipment -at this point the subscriber becomes unable to manage their Call Forward supplementary services from their user equipment (a fundamental expectation of the subscriber). In addition, the IMS network capacity is limited and placing an additional burden on IMS network by dedicating resources to service end users that will never use those services can lead to an unnecessary and 'wasteful use of those resources that can lead to an adverse effect on the user experience of other subscribers.

[16] Thus, by configuring the network infrastructure to provide subscribers with functionalities that the end user cannot use until they purchase a user equipment with the right capabilities, this is resource-inefficient and wasteful to network operators who must unnecessarily provide resource that goes unused, or allocate portions of limited network resource that provide these functionalities to service end users who are not capable of using those functionalities. This may lead to a degraded user experience to subscribers who are using these services. Also there could be unintended consequences in that a user equipment that is not capable of using these "bundled-in" products that are provisioned by the network could behave incorrectly.

[17] It is in this context that the present invention has been devised. SUMMARY OF THE INVENTION [18] Viewed from one aspect, the present invention provides method of operating network infrastructure to control the provisioning of a network-provided functionality to a mobile device of a user having a subscription to a cellular telecommunications network, comprising: receiving, at the network infrastructure, an instruction to provision a network-provided functionality to a user having a subscription to the cellular telecommunications network; updating a functionality entitlement and -4 -capability database to indicate that said user subscription is entitled to said network-provided functionality; checking the functionality entitlement and capability database whether or not a user equipment of the user is capable of supporting the network-provided functionality; and if the functionality entitlement and capability database indicates that the user equipment is capable of supporting the network-provided functionality, then: causing the network infrastructure to be configured to provide the network-provided functionality to the user; or if the user equipment is not or is not known to be capable of supporting the network-provided functionality, then: deferring causing the network infrastructure to be configured to provide the network-provided functionality to the user.

[19] In embodiments, the method further comprises, if the user equipment is not capable of supporting the network-provided functionality, then: not causing the network infrastructure to be configured to provide the network-provided functionality to the user; or preventing the network infrastructure from being configured to provide the network-provided functionality to the user.

[20] In embodiments, the method further comprises: retrieving an International Mobile Equipment Identity, NEI, number for the subscribed user's user equipment; determining, based on the IMEI, whether or not that user equipment can support the network-provided functionality; and updating the functionality entitlement and capability database to indicate whether or not the user equipment is capable of supporting the network-provided functionality. Optionally, the method further comprises: for a plurality of network-provided functionalities, determining for different types of user equipment whether or not the user equipment is capable of supporting each network-provided functionality; and using said determination to update the functionality entitlement and capability database. Optionally, the method further comprises receiving the International Mobile Equipment Identity and Software Version (IMEISV) that identifies the user equipment and its software version. This allows the capabilities provided to the device by the current software version to he taken into account [21] In embodiments, the method further comprises: if the functionality entitlement and capability database indicates that the user equipment is capable of supporting the network-provided functionality, then: updating an inventory database to indicate that the user is provisioned with the network-provided functionality; and if the functionality entitlement and capability database indicates that the user equipment is -5 -not capable of supporting the network-provided functionality, then: updating an inventory database to indicate that the provision of the network-provided functionality to the user is deferred. Optionally, the method further comprises: on receiving, at the network infrastructure, the instruction to provision a network-provided functionality to a user having a subscription to the cellular telecommunications network, checking the inventory database to determine the status of the provision of the network-provided functionality to the user; and only proceeding to check and update the functionality entitlement and capability database to provision or defer the provision of the network-provided functionality if the inventory database indicates that the user is not already provisioned with the network-provided functionality or that the provision of the network-provided functionality to the user is not already deferred.

[22] In embodiments, the network provided functionality is selected from the group comprising 4G data services, VoLTE, VoWIFI.

[23] In embodiments, the instruction to provision a network-provided functionality to a user is received from a customer relationship management (CRM) system or a CRM agent [24] In embodiments, the method s executed by a provisioning system in the network infrastructure, [25] In embodiments, the functionality entitlement and capability database is maintained by an Over The Air (OTA) server in the core network that, in use, provides updates to user equipment. In alternative embodiments, the OTA server plays no role in building or maintaining the functionality entitlement and capability database. This can instead be performed directly by a functionality entitlement and capability server. The OTA server can send the functionality entitlement and capability server a subscriber's IMEISV (International Mobile Equipment Identity Software Version) number, and from this it will determine the capabilities of the user equipment, rather than being advised of the subscriber's user equipment capabilities from the OTA server based upon the IMEI value.

[26] In embodiments, the method further comprises: on receiving a notification that an International Mobile Equipment Identity (IMEI) number for the subscribed user's user equipment has changed, indicative of the user having inserted the Universal Integrated Circuit Card (UICC) corresponding to the user's subscription into a different user equipment: determining, based on the new!MEI, whether or not that user equipment can support the network-provided functionality; checking and, if -6 -necessary, changing the indication in the functionality entitlement and capability database whether or not the user equipment is capable of supporting the network-provided functionality; and checking the indication in the functionality entitlement and capability database whether or not the user subscription is entitled to said network-provided functionality.

[27] Optionally, the method further comprises, if the functionality entitlement and capability database indicates that the user subscription is entitled to said network-provided functionality and the functionality entitlement and capability database is updated to change the user equipment to being capable of supporting the network-provided functionality, then: causing the network infrastructure to be configured to provide the deferred network-provided functionality to the user. Optionally, the method further comprises, updating an inventory database to indicate that the user is provisioned with the network-provided functionality.

[28] Optionally, the method further comprises, if the functionality entitlement and capability database indicates that the user subscription is entitled to said network-provided functionality and the functionality entitlement and capability database is updated to change the user equipment to being not capable of supporting the network-provided functionality, then: causing the network infrastructure to stop and defer providing the network-provided functionality to the user. Optionally, the method further comprises, updating an inventory database to indicate that the provision of the network-provided functionality to the user is deferred.

[29] In embodiments, if another notification that an International Mobile Equipment Identity (IMEI) number for the subscribed user's user equipment has changed is received before the network-provided service is provisioned or deferred pursuant. to the first change of user equipment, the method further comprises waiting until all changes to provision or defer network-provided service pursuant to the first change of user equipment are completed before proceeding with determining and implementing further necessary changes to the provisioned network-provided services pursuant to the second change of user equipment.

[30] Optionally, the method further comprises, further comprising, if the functionality entitlement and capability database indicates that the user subscription is entitled to said network-provided functionality, taking no further action.

[31] Optionally, the method further comprises counting the number of times a user changes user equipment, and if the number of times a user changes user equipment in a given time period exceeds a threshold value, the method further comprises freezing any further changes to provision or stop provisioning network-provided functionalities to the user for a freeze period.

[32] In embodiments, determining, based on the new IMEI, whether or not that user equipment can support the network-provided functionality comprises: attempting to identify the manufacturer and model of the new user equipment based on the new IMF': determining, based on a functional capabilities table for the manufacturer and model of the user equipment, whether or not that user equipment can support the network-provided functionality.

[33] In embodiments, if a user equipment is not known to be capable of supporting the network-provided functionality, this is recorded in the functionality entitlement and capability database, and wherein indications where it is not known that a user equipment is capable of supporting the network-provided functionality are handled as if the user equipment were not capable of supporting the network-provided functionality.

[34] In embodiments, the method further comprises: receiving, at the network infrastructure, an instruction to stop provisioning a network-provided functionality to a user having a subscription to the cellular telecommunications network; updating a functionality entitlement and capability database to indicate that said user subscription is not entitled to said network-provided functionality; checking the functionality entitlement and capability database whether or not a user equipment of the user is capable of supporting the network-provided functionality; and causing the network infrastructure to be configured to stop providing the network-provided functionality to the user. Optionally, the method further comprises updating an inventory database to indicate that the network-provided functionality not provided to the user.

[35] Viewed from another aspect, the present invention provides a provisioning system for controlling the provisioning of a network-provided functionality to a mobile device of a user having a subscription to a cellular telecommunications network, said provisioning system being configured to: receive an instruction to provision a network-provided functionality to a user having a subscription to the cellular telecommunications network; update a functionality entitlement and capability database to indicate that said user subscription is entitled to said network-provided functionality; check the functionality entitlement and capability database whether or -8 -not a user equipment of the user is capable of supporting the network-provided functionality; and if the functionality entitlement and capability database indicates that the user equipment is capable of supporting the network-provided functionality, then: cause the network infrastructure to be configured to provide the network-provided functionality to the user; or if the user equipment is not or is not known to be capable of supporting the network-provided functionality, then: defer causing the network infrastructure to be configured to provide the network--provided functionality to the user.

[36] In embodiments, the provisioning system is further configured to, if the user equipment is not capable of supporting the network-provided functionality, then: not cause the network infrastructure to be configured to provide the network-provided functionality to the user; or prevent the network infrastructure from being configured to provide the network-provided functionality to the user.

[37] In embodiments, the provisioning system is further configured to: retrieve an International Mobile Equipment Identity, IMEI, number for the subscribed user's user equipment; determine, based on the!MEI, whether or not that user equipment can support the network-provided functionality; and update the functionality entitlement and capability database to indicate whether or not the user equipment is capable of supporting the network-provided functionality.

[38] In embodiments, the provisioning system is further configured to: for a plurality of network-provided functionalities, determine for different types of user equipment whether or not the user equipment is capable of supporting each network-provided functionality, and use said determination to update the functionality entitlement and capability database.

[39] In embodiments, the provisioning system is further configured to: if the functionality entitlement and capability database indicates that the user equipment is capable of supporting the network-provided functionality, then: update an inventory database to indicate that the user is provisioned with the network-provided functionality; and if the functionality entitlement and capability database indicates that the user equipment is not capable of supporting the network-provided functionality, then: update an inventory database to indicate that the provision of the network-provided functionality to the user is deferred.

[40] In embodiments, the provisioning system is further configured to: on receipt, at the network infrastructure; of the instruction to provision a network-provided -9 -functionality to a user having a subscription to the cellular telecommunications network, check the inventory database to determine the status of the provision of the network-provided functionality to the user; and only proceed to check and update the functionality entitlement and capability database to provision or defer the provision of the network-provided functionality if the inventory database indicates that the user is not already provisioned with the network-provided functionality or that the provision of the network-provided functionality to the user is not already deferred.

[41] In embodiments, the network provided functionality is selected from the group comprising: 4G data services, Vol_TE, VoWIFI.

[42] In embodiments, the instruction to provision a network-provided functionality to a user is received from a customer relationship management (CRM) system or a CRM agent.

[43] In embodiments, the functionality entitlement and capability database is maintained by an Over The Air (OTA) server in the core network that, in use, provides updates to user equipment. In alternative embodiments, the OTA server plays no role in building or maintaining the functionality entitlement and capability database. This can instead be performed directly by a functionality entitlement and capability server. The OTA server can send the functionality entitlement and capability server a subscriber's IMEISV (International Mobile Equipment Identity Software Version) number, and from this it will determine the capabilities of the user equipment, rather than being advised of the subscriber's user equipment capabilities from the OTA server based upon the IMEI value.

[44] In embodiments, the provisioning system is further configured to: on receipt of a notification that an International Mobile Equipment Identity (IMEI) number for the subscribed user's user equipment has changed, indicative of the user having inserted the Universal Integrated Circuit Card (UICC) corresponding to the user's subscription into a different user equipment: determine, based on the new IMEI, whether or not that user equipment can support the network-provided functionality; check and, if necessary, change the indication in the functionality entitlement and capability database whether or not the user equipment is capable of supporting the network-provided functionality; and check the indication in the functionality entitlement and capability database whether or not the user subscription is entitled to said network-provided functionality.

[45] In embodiments; the provisioning system is further configured to, if the functionality entitlement and capability database indicates that the user subscription is entitled to said network-provided functionality and the functionality entitlement and capability database is updated to change the user equipment to being capable of supporting the network-provided functionality, then: cause the network infrastructure to he configured to provide the deferred network-provided functionality to the user. Optionally, the provisioning system is further configured to update an inventory database to indicate that the user is provisioned with the network-provided functionality.

[46] Optionally, the provisioning system is further configured to, if the functionality entitlement and capability database indicates that the user subscription is entitled to said network-provided functionality and the functionality entitlement and capability database is updated to change the user equipment to being not capable of supporting the network--provided functionality, then: cause the network infrastructure to stop and defer providing the network-provided functionality to the user. Optionally, the provisioning system is further configured to update an inventory database to indicate that the provision of the network-provided functionality to the user is deferred.

[47] In embodiments, if another notification that an International Mobile Equipment Identity (IMEI) number for the subscribed user's user equipment has changed is received before the network-provided service is provisioned or deferred pursuant to the first change of user equipment, the provisioning system is further configured to wait until all changes to provision or defer network-provided service pursuant to the first change of user equipment are completed before proceeding to determine and implement further necessary changes to the provisioned network--provided services pursuant to the second change of user equipment.

[48] In embodiments, the provisioning system is further configured to, if the functionality entitlement and capability database indicates that the user subscription is entitled to said network-provided functionality, take no further action.

[49] In embodiments, the provisioning system is further configured to count the number of times a user changes user equipment, and if the number of times a user changes user equipment in a given time period exceeds a threshold value, the provisioning system is further configured to freeze any further changes to provision or stop provisioning network-provided functionalities to the user for a freeze period.

-11 - [50] In embodiments; to determine, based on the new Ifv1EI, whether or not that user equipment can support the network-provided functionality, the provisioning system is configured to: attempt to identify the manufacturer and model of the new user equipment based on the new NEI; determine, based on a function-al capabilities table for the manufacturer and model of the user equipment, whether or not that user equipment can support the network-provided functionality.

[51] In embodiments, if a user equipment is not known to be capable of supporting the network-provided functionality, the provisioning system is configured to record this in the functionality entitlement and capability database, arid wherein the provisioning system is configured to handle indications where it is not known that a user equipment is capable of supporting the network-provided functionality as if the user equipment were not capable of supporting the network-provided functionality.

[52] In embodiments, the provisioning system is further configured to: receive; at the network infrastructure, an instruction to stop provisioning a network-provided functionality to a user having a subscription to the cellular telecommunications network; update a functionality entitlement and capability database to indicate that said user subscription is not entitled to said network-provided functionality; check the functionality entitlement and capability database whether or not a user equipment of the user is capable of supporting the network-provided functionality; and cause the network infrastructure to be configured to stop providing the network-provided functionality to the user.

[53] Optionally, the provisioning system is further configured to update an inventory database to indicate that the network-provided functionality not provided to the user.

[54] In accordance with the present invention, the network infrastructure is configured to check, prior to causing the network to provide an end user with one or more functionalities, whether or not the user equipment is capable of supporting those network-provided functionalities. If the user equipment is capable, then the network infrastructure proceeds with the provisioning of the functionalities. If the device is not capable, then the network infrastructure defers or suspends provisioning of these functionalities. A provisioning deferred flag can be indicated in an inventory database. For example, the network may he configured the automatically provide the end user with the more "basic" mobile network services (e.g. Voice, data, SIMS; MMS) and to only check whether the handset is capable of -12-supporting the more technically advanced products (such as VoLTE and VoWiFi). In fact, the functionalities (products and services) that the present invention is intended to be able to check for the UE capabilities before causing the network infrastructure to provision or defer provisioning is not limited to the above mentioned functionalities. In fact; the invention is also usable to check UE capabilities for VILTE and ViWifi and any network services that are device dependent including those not yet developed or commercially available.

[55] If a user whose provisioning of a network-provided functionality has been deferred because their user equipment did not have the necessary capabilities, then at a later time buys a user equipment does have the necessary capabilities for supporting the deferred functionality, the network automatically detects the change of user equipment, determines whether or not that new equipment then has the requisite capabilities:, and, having so determined, then proceeds to provision the functionality. This may be achieved, when the user's UICC is inserted into the new user equipment, by the HLR automatically detecting this through the ADD procedure and it notifies the OTA server which then: (i) checks whether the subscriber's provisioning of that functionality was previously deferred, (ii) check whether the new user equipment is capable of supporting that functionality, (Hi) if the new user equipment does have the necessary capabilities, then the network infrastructure is triggered to provide the deferred functionality.

[56] To determine the functional capabilities of user equipment, the network infrastructure builds up a database of functional capabilities based on device IMEI allocated by handset or equipment manufacturers as new models are brought to market. As new models are released; information about the functionalities supported by those models is obtained from the manufacturers and used to update the database.

[57] By the present invention, instead of the network infrastructure provisioning network-provided functionalities immediately based on a selected price plan on the billing system or product from the product catalogue, now also only completes the provisioning of a given functionality if or when the UICC is inserted into a user equipment that is capable of supporting the network-provided functionality.

[58] This will lead to an increased efficiency of resource utilisation and prevent overprovisioning of hardware and software resources by the network operator, and due to an increasing number of different user equipment capabilities and network- -13 -enabled functionalities, this mechanism to controlling the provisioning of functionalities to end-users could become indispensable in the future.

[59] The invention allows the network capability/capacity to reflect better the scale actually required by taking into account access user equipment capabilities rather than simply the product/service (bundle) purchased. It also provides a solution to unintended service consequences where a user equipment that is not capable of using these "bundled-in" products could behave incorrectly as described above [60] Within the scope of this application it is expressly envisaged that the various aspects, embodiments, examples and alternatives set out in the preceding paragraphs, in the claims and/or in the following description and drawings, and in particular the individual features thereof, may be taken independently or in any combination. Features described in connection with one aspect or embodiment of the invention are applicable to all aspects or embodiments, unless such features are incompatible.

BRIEF DESCRIPTION OF THE DRAWINGS

[61] Certain preferred embodiments will now be described, by way of example only, with reference to the accompanying drawings, in which: [62] Figures 1 A and 1B together show a message sequence chart setting out the procedure for adding of a network-provided functionality to a user's subscription and the configuring of the network infrastructure to provide or defer provisioning of that service in accordance with an embodiment of the invention; [63] Figures 2A and 2B together show a message sequence chart setting out the procedure for removing the provisioning or deferred provisioning of a network-provided functionality from a user's subscription in accordance with an embodiment of the invention; [64] Figures 3A and 3B together show a message sequence chart setting out the procedure for, on detection of the insertion of a subscriber's UICC into a different user equipment, checking that new user equipment's capabilities and configuring the network infrastructure to provision or defer the provisioning of network-provided functionalities in accordance with an embodiment of the invention; and [65] Figure 4 is a schematic drawing illustrating components of the cellular telecommunications network and network infrastructure for providing the controlling of the provision of network-provided functionalities to end user subscribers in accordance with aspects of the present invention. -14-

DETAILED DESCRIPTION OF THE EMBODIMENTS

[66] The detailed description set forth below in connection with the appended drawings is intended as a description of presently preferred embodiments of the invention, and is not intended to represent the only forms in which the present invention may be practised. It is to be understood that the same or equivalent functions may be accomplished by different embodiments that are intended to be encompassed within the spirit and scope of the invention Furthermore, terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that apparatuses and method steps that comprises a list of elements or steps does not include only those elements but may include other elements or steps not expressly listed or inherent. An element or step proceeded by "comprises...a" does not, without more constraints, preclude the existence of additional identical elements or steps that comprises the element or step.

[67] Figure 4 shows a schematic of a network topology for implementing aspects of the present invention in accordance with an embodiment.

[68] The apparatus 100 for controlling the provision of network-provided functionalities to end user subscribers includes a RAN 110 comprising plural base stations arranged as a cellular network in radio communication with a user equipment 120, in this case a smartphone, into which a UICC that securely stores the international mobile subscriber identity (IMSI) field and the related key used to identify and authenticate the user's subscription to the HLR 130 in the CN of the cellular telecommunications network. The HLR 130 also identifies and stores the IMEI that uniquely identifies the user's equipment 120 that is communicated to the HLR 130 by the user equipment on registration.

[69] The HLR 130 is communicatively coupled in the CN to "Over The Air" (OTA) server 140 that is used to apply network operator settings to the subscriber's user equipment (by "over the air" updates), based on the IMEI of the device (stored in the HLR). The OTA server 140 may be used by the CN to communicate with the user equipment 120 to configure it for use in the network and, as will be explained below, for interoperation to support the network-provided functionalities.

[70] The OTA server 140 is communicatively coupled to a service entitlement and capability server (SECS) 150 (also known as a functionality entitlement and capability server), a logical entity that, as will be explained below, is required in the -15 management of the "Deferred P oning" of network-enabled functionalities to end user subscribers.

[71] The SECS 150 is communicatively coupled to provisioning system 160 that manages the configuration of network infrastructure elements 190A, 190B, 1900 to cause the network elements 190A, 190B, 190C to provide network-provided functionalities to end user subscribers 120.

[72] The provisioning system 160 is communicatively coupled to the CRM system 170 to receive orders therefrom for individual products/services (functionalities) or bundles thereof that have been selected by a user (e.g. via the CRM agent) for provision by the network under their subscription.

[73] The CRM system 170 is communicatively coupled to a product inventory system 180 that maintains a record of the products and services (functionalities) that the network infrastructure is providing to an end user under their subscription [74] It should be rioted that in the embodiment 100 shown in Figure 4, the HLR 130, OTA Server 140, Service Entitlement and Capability Server 150, Provisioning System 160, CRM System 170 and Product Inventory System 180 intercommunicate and functionally interact with the help of one or more middleware systems that sit between the respective platforms and broker functionality and instructions passing between these elements using, for example, Remote Procedure Calls and CORBA, etc, that serves to allow the different platforms and systems to interoperate effectively. This middleware, however, is included for illustrative purposes only and is in no way instrumental or necessary to enabling the present invention. Indeed, the system could be configured such that one or more of the above components intercommunicate directly, without the assistance of middleware servers.

[75] Further, in the embodiment 100, the service entitlement and capability server 150, OTA server 140 and provisioning system 160 are shown as separate components of the system 100. However, while these functionally separate elements can be abstracted and conceptualised as logically separate modules, they may be more integrated in their deployment and interaction. For example, the service entitlement and capability server 150 may be physically integrated as part of OTA server 140. In addition, the provisioning system 160 may also be partly or completely integrated with the service entitlement and capability server 150 and/or OTA server 140. In addition, while one or more of the components of the network infrastructure shown in the embodiment 100 of Figure 4 are in the Core Network, CN, of the cellular telecommunications network, many of the components may be not strictly part of the core network and instead may be part of the network operators enterprise network that communicate with the other components using secure connections on, for example, the Internet In addition, the logical components of the embodiment 100 shown in Figure 4 may not necessarily he instantiated and implemented in a single server device. Instead, they may be implemented across one or more servers that intercommunicate to execute the functions of those logical components in a distributed manner, or they may be implemented in a virtual server environment spread across one or more server farms or in the cloud.

[76] The operation of the system 100 shown in Figure 100 to control the provisioning of network-provided functionalities to end user subscribers in accordance with embodiments will now be described with reference to Figures 1A, 113, 2A, 2B, 3A and 3B.

[77] Procedure Adding the Network-Provided Functionality "A" e.g. "VoLTE" [78] With reference first to Figures 1A and 1B, the procedure for adding a network-provided functionality "product' indicated as "A" and ordered by a user using the control system 100 will now be described. In this case, the product is Voice over LTENoice over 4G.

[79] At the start of this procedure, product A's status for the subscriber in the CRM system 170 and Product Inventory System 180 = "Null" That means that the "asset' (i.e. the product/service functionality provisioning in actuality by the network infrastructure) is not "complete" (i.e. being provided) or not "deferred" (i.e. the user is not already entitled to the asset through his existing subscription though its provisioning is deferred) This start condition can be checked to avoid duplication of services.

[80] Also, at the start of the procedure the subscriber's user equipment Service Capability status for Product A in SECS 150 = Any i.e. TRUE, FALSE, UNKNOWN.

[81] In step 11: the CRM agent submits an order to Add product "A" to the Provisioning System 160, [82] In step 12: the Provisioning System 160 calls the new Middleware service "Apply product to the Service Entitlement & Capability Server" (for product "A").

[83] In step 13: on receipt of the Middleware service "Apply product to the Service Entitlement & Capability Server" (for product "A"), the Service Entitlement & Capability Server 150 forces the subscriber's "Entitled to Commercial Product A" -17-parameter to TRUE and then checks the "Existing Service Capability" parameter for Product A. [84] IF 'Existing Service Capability" parameter for Product "A" = TRUE then the system 100 follows Path A (shown in Figure 1A).

[85] Alternatively, IF "Existing Service Capability" parameter for Product "A" = FALSE or UNKNOWN then the system 100 follows Path B (shown in Figure 1 B) [86] Note: For any individual Product, the result of UNKNOWN may be treated as TRUE or FALSE.

[87] Referring now to Figure 1A in which the"Existing Service Capability" parameter for Product "A" = TRUE, in step 14A: The Service Entitlement & Capability Server 150 returns the result "Proceed to provision technical services" (for Product "A'').

[88] In step 15A: Upon receipt of the result 'Proceed to provision technical services" (for Product "A"), the Provisioning System 160 will configure the network infrastructure elements 190A, 1906, 190C to provision the technical services for Product "A" and, on completion the Provisioning System 160 will return "Success (complete)" the CRM system 170 (or the CRM System 170 will change the product's asset status to "Asset complete").

[89] In step 16A: Upon receipt of the result "Order Success (complete)", CRM system 170 will change asset status to "Asset complete" (in Product Inventory System 180).

[90] Step 17A: Provisioning System 160 will update the Inventory database (in Product Inventory System 180) that the assetised status of the product "A" is "Asset complete" [91] Referring now to Figure 16 in which the "Existing Service Capability" parameter for Product "A" = FALSE or UNKNOWN, in. step 14B: the Service Entitlement & Capability Server 150 returns the result "Defer the provisioning of technical services" (for Product "A").

[92] In step 156: Upon receipt of the result "Defer the provisioning of technical services" (for Product "A"), the Provisioning System 160 will return "Order Success (deferred)" to the CRM System 170 (whilst the Provisioning System 160 will change asset status of Product "A" to "Asset deferred").

[93] In step 16B: Upon receipt of the result "Order Success (deferred)", CRM system 170 will change asset status to "Asset deferred". -18

[94] In step 17B: Provisioning System 150 will update Inventory database that the assetised status of the product is now 'Asset deferred" (in Product Inventory System 180).

[95] In this way, when the network infrastructure is configured to check, prior to causing the network to provide an end user with one or more functionalities, whether or not the user equipment is capable of supporting those network-provided functionalities. If the user equipment is capable, then the network infrastructure proceeds with the provisioning of the functionalities. If the device is not capable, then the network infrastructure defers or suspends provisioning of these functionalities. A provisioning deferred flag can be indicated in an inventory database.

[96] Procedure for Removing the Network-Provided Functionality "A" [97] With reference now to Figures 2A and 2B, the procedure for removing a network-provided functionality "product" indicated as "A" as ordered by a user using the control system 100 will now be described. In this case, the product is again Voice over LTE/Voice over 4G.

[98] At the start of this procedure, product A's status in CRM System 170 and the Product Inventory System 180 = "Asset complete" or "Asset deferred", i.e. not "NULL".

[99] Also, the subscriber's user equipment "Service Capability" for Product "A" Any i.e. TRUE, FALSE. UNKNOWN.

[100] In step 21 (not shown): the CRM agent submits an order for "Remove product A" to CRM System 170.

[101] In step 22: Upon receipt of an order to Remove product "A", the CRM System 170 will check the assetised status of product "A"; [102] If Product A's status in the CRM System 170 = "Asset deferred", then the CRM system 170 submits an order to Provisioning System 160 to Delete the deferred product (or Provisioning System 160 performs the function to Delete the deferred product). This is described below in Path A (as shown in Figure 2A).

[103] Alternatively, if Product A's status in CRM System 170 = "Asset complete" then CRM system 170 submits and order to Provisioning System 160 to Delete the completed product (Provisioning System 160 preforms the function to Delete the completed product). This is described below in Path B (as shown in Figure 2B) -19- [104] Referring to both Figures 2A and 2B, in step 23A and 23B: on receipt of the order to Delete the deferred product the Provisioning System 160 calls the Middieware service "Remove Product from Service Entitlement & Capability Server".

[105] In step 24A and 248: On receipt of the new Middieware service "Remove Product from Service Entitlement & Capability Server' the Service Entitlement & Capability Server 150 forces the "Entitled to Commercial Product A" parameter to FALSE and returns the result to Provisioning System 160.

[106] Referring only now to Figure 2A, in step 25A: Provisioning System 160 shall return success to CRiv1 system 170 (or Provisioning System 160 shall set the assetised product status to NULL).

[107] Referring only now to Figure 2B, in step 256: the Provisioning System 160 shall configure the network infrastructure elements 190A, 1906, 190C to delete the technical product from the network and Provisioning System 160 shall return success to CRM system 170 (or the Provisioning System 160 shall set the assetised product status to NULL).

[108] In step 26A and 26B (not shown): on receipt of success response, CRM system 170 shall set the assetised product status to NULL.

[109] Procedure on Detection that a Subscriber has inserted their UICC into a New or Different User Equipment (in Respect of one or more Products "A", B" "X" etc) [110] With reference now to Figures 3A and 3B, the procedure for' controlling the provisioning and de-provisioning of functionalities (Products "A", B" .... "X" etc) on detection that a subscriber has inserted their UICC into a new or different user equipment will now be described. In this case, Product "A" is again Voice over LTE/Voice over 4G.

[111] At the start of this procedure, the Product status (for Products "A", B" .... "X" etc) in CRM System 170 = Any i.e. NULL, "Asset complete" or "Asset deferred", and the service capability for Products "A": "B" "X" etc) in SECS 150 = Any i.e. TRUE, FALSE, UNKNOWN.

[112] In step 31 (not shown): the user inserts UICC into a [different] user equipment (e.g. a different smartphone) and allows the device to register on the network.

[113] In step 32: If the HLR 130 determines that the handset's!MEI value is different / new, the HLR will invoke the "Automatic Device detection" (ADD) supplementary service to call the existing Middieware service "TerminalChangeTriager".

-20 - [114] In step 33: the Middleware will notify the "Over The Air" (OTA) terminal management server 140 of the subscriber's new IMEI value.

[115] In step 34: On receipt of the IMEI value, the OTA terminal management server will attempt to identify the handset manufacturer /model and, if the handset manufacturer and model is known, will refer to the new "service capabilities" table and will return a TRUE/FALSE/UNKOWN value for each of the Products "A", B". _."X" to Middleware. To determine the functional capabilities of user equipment, the network infrastructure (in this case, OTA Server 140 and SECS 150) builds up a database of functional capabilities based on device IMEI allocated by handset or equipment manufacturers as new models are brought to market. As new models are released, information about the functionalities supported by those models is obtained from the manufacturers and used to update the SECS database.

[116] In step 35: Middleware will forward the handset's "Service Capabilities" results for each of the products "A", "B".. "X' to the Service Entitlement & Capability Server 150.

[117] In step 36: on receipt of the subscriber's user equipment "Service Capabilities" results for each of the products "A", "B".... "X", the Service Entitlement & Capability Server 150 will update the subscriber's Current Service Capabilities list for each Product and take the following actions: [118] Where the Service Capability is changed from either FALSE or UNKNOWN to TRUE and where the Commercial Product is TRUE (i.e. the subscriber is entitled to be provided that functionality) then the SECS 150 calls the Middleware service "Apply Deferred Product". This is described below in relation to Path A (as shown in see Figure 3A).

[119] Where the Service Capability is changed from TRUE to either FALSE or UNKNOWN and where the Commercial Product is TRUE (i.e. the subscriber is entitled to be provided that functionality) then the SECS 150 calls the tVliddleware service "Withdraw Technical Product". This is described below in relation to Path B (as shown in see Figure 3B).

[120] Where the Service Capability is changed fro TRUE to either FALSE or UNKNOWN and where the Commercial Product is FALSE (i.e. the subscriber is not entitled to be provided that functionality) then take no further action.

-21 - [121] Wnere the Service Capability is changed from TRUE to either FALSE or UNKNOWN and where the Commercial Product is FALSE (i.e. the subscriber is not entitled to be provided that functionality) then take no further action.

[122] As before, for any individual Product, the result of UNKNOWN may be treated as TRUE or FALSE.

[123] Referring now to Figure 3A only, in step 37A: the Middleware service "Apply Deferred Product" will notify the CRM system 170.

[124] In step 38A: Upon receipt of the Middleware service "Apply Deferred Product", CRM system 170 shall ensure that the assetised product status is "Complete deferred" before submitting an order for "Add deferred product A" to Provisioning system 160 (whilst CRM system 170 shall ensure that the assetised product status is "Complete deferred" before submitting an order for "Add deferred product A" to Provisioning system 160).

[125] In step 39A: the Provisioning system 160 provisions the technical product and returns success result to CRM system 170.

[126] In step 40A: Upon receipt of the success result,CRM system 170 will change the assestised product status to "Asset complete".

[127] Step 41A (not shown): CRM system 170 will update Inventory system 180 that the assetised status of the product is "Asset complete" [128] In this way, functionality that a subscriber is entitled to that has been deferred from being provisioned due to the use by the user of a user equipment not having the requisite functional capabilities, can be subsequently provisioned to the user when it is detected that the user has inserted the UICC into a different user equipment that does have the requisite capabilities.

[129] Referring now to Figure 3B only, in step 37B: the Middleware service "WithdrawTechnicaProduct" will notify the CRM system 170 [130] In step 38B: Upon receipt of the Middleware service "VVithdrawTechnicalProduct", the CRM system 170 shall verify that the status of the product is "Assetised (deferred)" before submitting a new order to the Provisioning System 160 to withdraw the technical product (whilst the CRM system 170 shall verify that the status of the product is "Asset deferred' before attempting to withdraw the technical product).

[131] In step 39B: the Provisioning system 160 shall withdraw the technical product and return the success result to CRM system 170.

-22 - [132] In step 40B: upon receipt of the success result, CRM system 170 will change the assestised product status to "Asset deferred".

[133] Step 41B (not shown): the CRM system 170 will update Inventory management system 180 that the assetised status of the product is "Asset deferred" [134] In alternative embodiments, the OTA server 140 plays no role in building or maintaining the functionality entitlement and capability database. This can instead be performed directly by a service entitlement arid capability server 160. The OTA server 140 can send the service entitlement and capability server 150 a subscriber's IMEISV (International Mobile Equipment Identity Software Version) number, and from this it will determine the capabilities of the user equipment, rather than being advised of the subscriber's user equipment capabilities from the OTA server 140 based upon the IMEI value.

[135] The revised implementation is simpler because it requires no changes to be made to the OTA server 140 arid advantageous because the design also makes use of the "SoftwareVersion" component of the IMEISV to further determine the true capabilities of the device.

[136] In this alternative embodiment, the Service Entitlement & Capability Server 150 is configured to hold the IMEI ranges associated with each DeviceType, The Service Entitlement & Capability Server 150 is primed to hold the known capabilities (with respect to all the Products where handset capability is significant) for all of the various DeviceType_SoftwareVersion_ID values. The Service Entitlement & Capability Server 150 will also be primed to hold the entire subscriber list with the corresponding IMEISV value (obtained from the HLR).

[137] Then, whenever a device manufacturer introduces a new DeviceType then a new IMEI range(s) will need to be configured and a new DeviceType_SoftwareVersion_ID will need to be assigned and configured with its list of known capabilities. Whenever a device manufacturer introduces a new software version for an existing DeviceType then a new DeviceType_SoftwareVersion_ID value will need to be assigned and configured with its list of known capabilities. Whenever a device manufacturer changes the capabilities of an existing device using a method that does not result in a change to the SoftwareVersion component of the IMEISV, the Service Entitlement & Capability Server 150 will need to be updated to reflect the revision to the capabilities of the existing DeviceType_SoftwareVersion_ID value. In this scenario, the Service -23 -Entitlement & Capability Server 150 shall automatically apply the capability change to all affected subscriptions with that particular DeviceType_SoftwareVersion_ID providing that the affected subscription is not changed whilst in the "handset change freeze" state (and shall use a scheduling mechanism to ensure that all the changes for all the affected subscriptions are not submitted to the CRM system 170 at once).

[138] In this alternative embodiment, the procedure for adding and removing functionalities would be the same as shown in Figures 1A, 1 B, 2A and 2B. However, the procedure on detection that a subscriber has inserted their UICC into a new or different user equipment would be different from that shown in Figure 3A and 3B, as follows.

[139] In step 33: the Middleware notifies the Service Entitlement & Capability Server 150 (rather than the OTA server) of the subscriber's MSISDN and new IMEISV value.

[140] In step 34: on receipt of the MSISDN value, the Service Entitlement & Capability Server 150 creates a new subscriber record if one does not already exist. On receipt of the new IMEISV value, the Service Entitlement & Capability Server 150 will store the IMEISV value and will attempt to identify the handset manufacturer/model/software version and, if the handset manufacturer and model and software version is known, will refer to the new "service capabilities" table and will return a TRUE/FALSE/UNKOWN value for each of the Products "A", "B" [141] Step 35 is then omitted.

[142] Exception conditions: [143] The above mode of operation can operate smoothly in normal use conditions. However, there are certain modes of use that present exception conditions: i.e. when user equipment changes are being made too quickly, and when there are too many User Equipment changes being made. These situations merit being handled differently from that described above by the network infrastructure, otherwise problems may arise in that the network provisioning of services may become mismatched with that which the user expects, leading to unexpected modes of operation, and it also may be difficult to bring the network configuration into accordance with the capabilities of a user equipment being used at any one time. These exception conditions will be described in more detail below.

[144] Procedure when User equipment changes made too quickly -24 - [145] If the subscriber changes their handset (i.e. user equipment) and this handset change results in the initiation of one or more product status changes between "Asset complete" and "Asset deferred" then a problem may occur if the subscriber changes their handset again before ail of the other product changes have been complete. To guard against any such problems occurring, in embodiments, the Service Entitlement & Capability Server 150 shall be configured such that it does not initiate any of the next set of product status changes until all product status changes from the previous handset change have been completed and will be ignored entirely if another handset change is made before the first product state change is issued by the Service Entitlement & Capability Server 150.

[146] Too many User Equipment changes being made [147] If the subscribers are allowed to make excessive handset (i.e. user equipment) changes (say more than 5) in a given period (say 24 hours) then the provisioning system 160 and various network elements 190A, 190B, 190C may become overloaded with provisioning / deprovisioning requests. To prevent any concerted "Denial of Service attack" overloading the provisioning systems 160 and various network elements 190A, 190B, 190C, the Service Entitlement & Capability Server 150 shall count the quantity of IMEI changes made over a given period. When the limit is exceed, the Service Entitlement & Capability Server 150 shall continue to update the "Next Service Capability" column but will from this point until the end of the period shall take no further action to modify the status of the products i.e. the "Existing Service Capability" column shall remain frozen.

[148] The system 100 may inform the Fraud and Security team of the network operator of the potential fraudulent manipulation of the IMEI on the user's subscription. The Fraud and Security team can reset the "freezing" if no untoward fraudulent activity is present.

[149] If a commercial product is added to a subscriber whilst in the "handset change freeze" state, the Service Entitlement & Capability Server 150 shall update the commercial product column and shall return "Proceed to provision technical services" (thus allowing the technical product to be provisioned) and shall also force the "Existing Service Capability"=TRUE for the particular product.

[150] If a commercial product is removed from a subscriber whilst in the "handset change freeze" state, the Service Entitlement & Capability Server 150 shall update the Commercial Product column and return the appropriate response.

-25 - [151] At the end of the freeze" period, the service capabilities of the subscriber's handset (recorded in the "Next Service Capability' column) will be used by the Service Entitlement & Capability Server 150 to determine the product status changes required for the start of the next period. The change counter shall be reset to zero. To ensure that the Service Entitlement & Capability Server 150 does not create a "wave" of product changes for all those subscribers that made too many handset changes in the previous period then the 24 hours in the day shall be divided into four quarters to make 96 different start periods (the particular start period used by any subscriber will be determined by the last two digits of the subscriber's MSISDN with the exception that MSISDNs ending with the digits '93 or 94', '95 or 96', '97 or 98' and '99 or 00' will share the periods 93, 94, 95 and 96 respectively).

[152] MSISDN=447748328799 (Period=96 i.e. the period which starts at 23:45:00 in day 1 and ends at 23:44:59 in day 2), Current change count=x [153] Product [154] Entitled to Commercial Product r x155 Existing Ti [156] Next i Service Capability i I Service Capability i i [157] "A" [ 58] TRUE i t159i FALSE 01 [161] "B" [162] FALSE 63]] TRUE 1 M64] I [165] "C" [166] TRUE 71 FALSE. 1 [168] J -' - [169] The description of the preferred embodiments of the present invention has been presented for purposes of illustration and description, but is not intended to be exhaustive or to limit the invention to the forms disclosed. It will be appreciated by those skilled in the art that changes could be made to the embodiments described above without departing from the broad inventive concept thereof. It is understood, therefore, that this invention is not limited to the particular embodiment disclosed, but covers modifications within the scope of the present invention as defined by the appended claims.

-26 -

Claims

CLAIMSA method of operating network infrastructure to control the provisioning of a network-provided functionality to a mobile device of a user having a subscription to a cellular telecommunications network, comprising: receiving, at the network infrastructure, an instruction to provision a network-provided functionality to a user having a subscription to the cellular telecommunications network; updating a functionality entitlement and capability database to indicate that said user subscription is entitled to said network-provided functionality; checking the functionality entitlement and capability database whether or not a user equipment of the user is capable of supporting the network-provided functionality; and if the functionality entitlement and capability database indicates that the user equipment is capable of supporting the network-provided functionality, then: causing the network infrastructure to be configured to provide the network-provided functionality to the user; or if the user equipment is not or is not known to be capable of supporting the network-provided functionality, then: deferring causing the network infrastructure to be configured to provide the network-provided functionality to the user.
2. A method as claimed in claim 1, further comprising, if the user equipment is not capable of supporting the network-provided functionality, then: not causing the network infrastructure to be configured to provide the network-provided functionality to the user; or preventing the network infrastructure from being configured to provide the network-provided functionality to the user.
3. A method as claimed in claim 1 or 2, further comprising: -27 -retrieving an International Mobile Equipment Identity, IMEI, number, optionally an International Mobile Equipment Identity and Software Version, IMEISV, number for the subscribed user's user equipment; determining; based on the IMEI; whether or not that user equipment can support the network-provided functionality; and updating the functionality entitlement and capability database to indicate whether or not the user equipment is capable of supporting the network-provided functionality.
4. A method as claimed in claim 3; further comprising; for a plurality of network-provided functionalities, determining for different types of user equipment whether or not the user equipment is capable of supporting each network--provided functionality, and using said determination to update the functionality entitlement and capability database.
5. A method as claimed in any preceding claim, further comprising: if the functionality entitlement and capability database indicates that the user equipment is capable of supporting the network-provided functionality, then: updating an inventory database to indicate that the user is provisioned with the network-provided functionality; and if the functionality entitlement and capability database indicates that the user equipment is not capable of supporting the network-provided functionality, then: updating an inventory database to indicate that the provision of the network-provided functionality to the user is deferred.
6. A method as claimed in claim 5, further comprising: on receiving, at the network infrastructure, the instruction to provision a network--provided functionality to a user having a subscription to the cellular telecommunications network, checking the inventory database to determine the status of the provision of the network--provided functionality to the user; and only proceeding to check and update the functionality entitlement and capability database to provision or defer the provision of the network-provided functionality if the inventory database indicates that the user is not already -28 -provisioned with the network-provided functionality or that the provision of the network-provided functionality to the user is not already deferred.
7. A method as claimed in any preceding claim, wherein the network provided functionality is selected from the group comprising: 4G data services, VoLTE, VoVVIFI.
8. A method as claimed in any preceding claim, wherein the instruction to provision a network-provided functionality to a user is received from a customer relationship management (CRM) system or a CRM agent.
9. A method as claimed in any preceding claim, wherein the method is executed by a provisioning system in the network infrastructure.
10. A method as claimed in any preceding claim, wherein the functionality entitlement and capability database is maintained by an Over The Air (OTA) server in the core network that, in use, provides updates to user equipment.
11. A method as claimed in any preceding claim, further comprising: on receiving a notification that an International Mobile Equipment Identity (IMEI) number for the subscribed users user equipment has changed, indicative of the user having inserted the Universal Integrated Circuit Card (UICC) corresponding to the user's subscription into a different user equipment: determining, based on the new IMEI, whether or not that user equipment can support the network-provided functionality; checking and, if necessary, changing the indication in the functionality entitlement and capability database whether or not the user equipment is capable of supporting the network-provided functionality; and checking the indication in the functionality entitlement and capability database whether or not the user subscription is entitled to said network-provided functionality.
12. A method as claimed in claim 11, further comprising, if the functionality entitlement and capability database indicates that the user subscription is entitled to said network-provided functionality and the functionality entitlement and capability database is updated to change the user equipment to being capable of supporting the network-provided functionality, then: causing the network infrastructure to be configured to provide the deferred network-provided functionality to the user.

-29 -
13. A method as claimed in claim 12, further comprising updating an inventory database to indicate that the user is provisioned with the network-provided functionality.
14. A method as claimed in claim 11, further comprising, if the functionality entitlement and capability database indicates that the user subscription is entitled to said network-provided functionality and the functionality entitlement and capability database is updated to change the user equipment to being riot capable of supporting the network-provided functionality, then: causing the network infrastructure to stop and defer providing the network-provided functionality to the user.
15. A method as claimed in claim 14, further comprising updating an inventory database to indicate that the provision of the network-provided functionality to the user is deferred.
16. A method as claimed in any of claims 12 to 15, wherein f another notification that an International Mobile Equipment Identity WEI) number for the subscribed user's user equipment has changed is received before the network-provided service is provisioned or deferred pursuant to the first change of user equipment, the method further comprises waiting until all changes to provision or defer network-provided service pursuant to the first change of user equipment are completed before proceeding with determining and implementing further necessary changes to the provisioned network-provided services pursuant to the second change of user equipment.
17. A method as claimed in any of claims 11 to 16, further comprising, if the functionality entitlement and capability database indicates that the user subscription is entitled to said network-provided functionality, taking no further action.
18. A method as claimed in any of claims 11 to 17, further comprising courting the number of times a user changes user equipment, and if the number of times a user changes user equipment in a given time period exceeds a threshold value, the method further comprises freezing any further changes to provision or stop provisioning network-provided functionalities to the user for a freeze period.
A method as claimed in any of claims 11 to 18, wherein determining, based on the new IMEI, whether or not that user equipment can support the network-provided functionality comprises: -30 -attempting to identify the manufacturer and model of the new user equipment based on the newliVIEI; determining, based on a functional capabilities table for the manufacturer and model of the user equipment, whether or not that user equipment can support the network-provided functionality.
20. A method as claimed in any preceding claim, wherein if a user equipment is not known to be capable of supporting the network-provided functionality, this is recorded in the functionality entitlement and capability database, and wherein indications where it is not known that a user equipment is capable of supporting the network-provided functionality are handled as if the user equipment were not capable of supporting the network-provided functionality.
21. A method as clamed in any preceding claim, further comprising receiving, at the network infrastructure, an instruction to stop provisioning a network-provided functionality to a user having a subscription to the cellular telecommunications network; updating a functionality entitlement and capability database to indicate that said user subscription is not entitled to said network-provided functionality; checking the functionality entitlement and capability database whether or not a user equipment of the user is capable of supporting the network-provided functionality; and causing the network infrastructure to be configured to stop providing the network-provided functionality to the user.
22. A method as claimed in claim 21, further comprising updating an inventory database to indicate that the network-provided functionality not provided to the user.
23. A provisioning system for controlling the provisioning of a network-provided functionality to a mobile device of a user having a subscription to a cellular telecommunications network, said provisioning system being configured to: receive an instruction to provision a network-provided functionality to a user having a subscription to the cellular telecommunications network; update a functionality entitlement and capability database to indicate that said user subscription is entitled to said network-provided functionality; -31 -check the functionality entitlement and capability database whether or not a user equipment of the user is capable of supporting the network-provided functionality; and if the functionality entitlement and capability database indicates that the user equipment is capable of supporting the network-provided functionality, then: cause the network infrastructure to be configured to provide the network-provided functionality to the user; or if the user equipment is not or is not known to be capable of supporting the network-provided functionality, then: defer causing the network infrastructure to be configured to provide the network-provided functionality to the user.
24. A provisioning system as claimed in claim 23, further configured to, if the user equipment is not capable of supporting the network-provided functionality, then: not cause the network infrastructure to be configured to provide the network-provided functionality to the user; or prevent the network infrastructure from being configured to provide the network-provided functionality to the user.
25. A provisioning system as claimed in claim 23 or 24; further configured to: retrieve an International Mobile Equipment Identity, IMEI, number for the subscribed user's user equipment; determine, based on the IMEI, whether or not that user equipment can support the network-provided functionality; and update the functionality entitlement and capability database to indicate whether or not the user equipment is capable of supporting the network-provided functionality.
26. A provisioning system as claimed in claim 25, further configured to: -32 -for a plurality of network-provided functionalities, determine for different types of user equipment whether or not the user equipment is capable of supporting each network-provided functionality, and use said determination to update the functionality entitlement and capability database.
27. A provisioning system as claimed in any of claims 23 to 26, further configured to: if the functionality entitlement and capability database indicates that the user equipment is capable of supporting the network-provided functionality, then: update an inventory database to indicate that the user is provisioned with the network-provided functionality; and if the functionality entitlement and capability database indicates that the user equipment is not capable of supporting the network-provided functionality, then: update an inventory database to indicate that the provision of the network-provided functionality to the user is deferred.
28. A provisioning system as claimed in claim 27, further configured to: on receipt, at the network infrastructure, of the instruction to provision a network-provided functionality to a user having a subscription to the cellular telecommunications network, check the inventory database to determine the status of the provision of the network-provided functionality to the user; and only proceed to check and update the functionality entitlement and capability database to provision or defer the provision of the network-provided functionality if the inventory database indicates that the user is not already provisioned with the network--provided functionality or that the provision of the network--provided functionality to the user is not already deferred.
29. A provisioning system as claimed in any of claims 23 to 28, wherein the network provided functionality is selected from the group comprising: 4G data services, VoLTE; VoVVIFI.
30. A provisioning system as claimed in any of claims 23 to 29, wherein the instruction to provision a network-provided functionality to a user is received from a customer relationship management (CRM) system or a ORM agent.

-33 -
31. A provisioning system as claimed in any of claims 23 to 30, wherein the functionality entitlement and capability database is maintained by an Over The Air (OTA) server in the core network that, in use, provides updates to user equipment.
32. A provisioning system as claimed in any of claims 23 to 31, further configured to: on receipt of a notification that an International Mobile Equipment Identity (IMEI) number, optionally an International Mobile Equipment Identity and Software Version, IMEISV, number for the subscribed user's user equipment has changed, indicative of the user having inserted the Universal Integrated Circuit Card (UICC) corresponding to the user's subscription into a different user equipment: determine, based on the new IMEI, whether or not hat user equipment can support the network-provided functionality; check and, if necessary, change the indication in the functionality entitlement and capability database whether or not the user equipment is capable of supporting the network-provided functionality; and check the indication in the functionality entitlement and capability database whether or not the user subscription is entitled to said network-provided functionality.
33. A provisioning system as claimed in claim 32, further configured to, if the functionality entitlement and capability database indicates that the user subscription is entitled to said network-provided functionality and the functionality entitlement and capability database is updated to change the user equipment to being capable of supporting the network-provided functionality, then: cause the network infrastructure to be configured to provide the deferred network-provided functionality to the user.
34. A provisioning system as claimed in claim 33, further configured to update an inventory database to indicate that the user is provisioned with the network-provided functionality.
35. A provisioning system as claimed in claim 34, further configured to, if the functionality entitlement and capability database indicates that the user subscription is entitled to said network-provided functionality and the functionality entitlement and capability database is updated to change the user equipment to being not capable of supporting the network-provided functionality, then: -34 -cause the network infrastructure to stop and defer providing the network-provided functionality to the user.
36. A provisioning system as claimed in claim 35, further configured to update an inventory database to indicate that the provision of the network-provided functionality to the user is deferred.
37. A provisioning system as daimed in any of claims 33 to 36, wherein if another notification that an international Mobile Equipment Identity (IMEI) number for the subscribed user's user equipment has changed is received before the network-provided service is provisioned or deferred pursuant to the first change of user equipment, the provisioning system is further configured to wait until all changes to provision or defer network-provided service pursuant to the first change of user equipment are completed before proceeding to determine and implement further necessary changes to the provisioned network-provided services pursuant to the second change of user equipment.
38. A provisioning system as claimed in any of claims 32 to 37, further configured to, if the functionality entitlement and capability database indicates that the user subscription is entitled to said network-provided functionality, take no further action.
39. A provisioning system as claimed in any of claims 32 to 38, further configured to count the number of times a user changes user equipment, and if the number of times a user changes user equipment in a given time period exceeds a threshold value, the provisioning system is further configured to freeze any further changes to provision or stop provisioning network-provided functionalities to the user for a freeze period.
40. A provisioning system as claimed in any of claims 32 to 39, wherein to determine, based on the new!MEI, whether or not that user equipment can support the network-provided functionality, the provisioning system is configured to: attempt to identify the manufacturer and model of the new user equipment based on the new IMEI; determine, based on a functional capabilities table for the manufacturer and model of the user equipment, whether or not that user equipment can support the network-provided functionality.

-35 -
41. A provisioning system as claimed in any of claims 23 to 40, wherein if a user equipment is not known to be capable of supporting the network-provided functionality, the provisioning system is configured to record this in the functionality entitlement and capability database, and wherein the provisioning system is configured to handle indications where it is not known that a user equipment is capable of supporting the network-provided functionality as if the user equipment were not capable of supporting the network-provided functionality.
42. A provisioning system as claimed in any of claims 23 to 41, further configured to: receive, at the network infrastructure, an instruction to stop provisioning a network-provided functionality to a user having a subscription to the cellular telecommunications network; update a functionality entitlement and capability database to indicate that said user subscription is not entitled to said network-provided functionality; check the functionality entitlement and capability database whether or not a user equipment of the user is capable of supporting the network-provided functionality: and cause the network infrastructure to be configured to stop providing the network-provided functionality to the user.
43. A provisioning system as claimed in claim 42, further configured to update an inventory database to indicate that the network--provided functionality not provided to the user.-36 -