PER-ENTERPRISE SUBSCRIBER DATA MANAGEMENT IN A MULTI-TENANT NETWORK ENVIRONMENT

Provided herein are techniques to provide per-enterprise subscriber data management (SDM) in multi-tenant network environment. In one instance, a method may include obtaining, by an SDM system, input information indicating SDM services requested for an enterprise entity in which the input information includes a multi-tenancy service attribute for the enterprise entity and indicates whether subscriber data for is to be provided on-premise for the enterprise entity. The method may further include identifying a particular SDM service of the SDM system for storing the subscriber data, deploying the particular SDM service via the SDM system, and deploying one or more on-premise SDM services at each of one or more on-premise locations of the enterprise entity for storing the subscriber data based on determining that the subscriber data is to be provided on-premise for the enterprise entity.

TECHNICAL FIELD

The present disclosure relates to network equipment and services.

BACKGROUND

Networking architectures have grown increasingly complex in communication environments. In particular, mobile communication networks have grown substantially as end users become increasingly connected to mobile network environments. As the number of mobile users increases, efficient management of communication resources and of users becomes more critical.

DETAILED DESCRIPTION

Overview

Provided herein are techniques through which per-enterprise subscriber data management services may be provided for multiple enterprise entities in a multi-tenant network environment. In at least one embodiment, a computer-implemented method is provided that may include obtaining, by a subscriber data management (SDM) system, input information indicating SDM services requested for an enterprise entity, wherein the input information includes a multi-tenancy service attribute for the enterprise entity and indicates whether subscriber data for the enterprise entity is to be provided on-premise for the enterprise entity; identifying, based on the multi-tenancy service attribute included in the input information, a particular SDM service of the SDM system for storing the subscriber data for the enterprise entity from a plurality of SDM service options provided by the SDM system; deploying the particular SDM service via the SDM system for storing the subscriber data for the enterprise entity; and deploying one or more on-premise SDM services at each of one or more on-premise locations of the enterprise entity for storing the subscriber data based on determining that the subscriber data is to be provided on-premise for the enterprise entity.

Example Embodiments

Managing multi-tenancy provisioning and storage for subscriber data (e.g., Subscriber Identity Module (SIM) subscriptions) for large numbers (e.g., millions) of subscribers is complex. Typically, large-scale, and correspondingly expensive, subscriber data systems are often dedicated for a single service, such as a consumer (public) cellular mobility network in which all SIM-related subscription and authentication data belongs to and is the responsibility of a single service owner/service provider.

In contrast, a private Fifth Generation (5G)-as-a-Service (5GaaS) offering can support many different partners/service providers and/or end customers (e.g., enterprise entities) that each may have a few hundred to tens of thousands of subscribers/SIMs. For example, a 5GaaS offering/system can be provided by a 5GaaS provider in which the 5GaaS provider may sell/lease Third Generation Partnership Project (3GPP) 5G cellular service to a number of service partners or providers, each of which may in turn sell or otherwise provide 5G cellular service to a number of enterprise entities. In some instances, the 5GaaS provider may also provide 5G cellular service directly to one or more enterprise entities.

The subscriber data for each of different “SIM-sets” that belong to different end customers or enterprise entities (e.g., SIM data for a set of enterprise managed subscribers/wireless devices) are to be accessible only by the ‘owner’ of a given SIM-set in the course of regular operations.

There can be many multi-tenancy considerations, such as managing multi-tenancy credentials, potentially logical and/or physical partitioning of storage and subscriber data, and/or the like that can result in a complex undertaking to provide subscriber data management (SDM) functionality for a 5GaaS offering that is to serve to multiple service partners/providers and multiple enterprise entities.

Further, pre-deploying multiple instances of SDM functionality can be costly and operationally complex. It can also be inefficient, as such pre-deployment of SDM functionality is often based on market forecasts estimating a number of enterprise customers to which a 5GaaS may serve, which can change based on the number of service providers (and their forecasts) regarding the number of enterprise customers that are expected to be served. Thus, it would be advantageous to provide effective techniques through which to address and facilitate different multi-tenancy aspects for subscriber/SIM data provisioning and storage while reducing the service per subscriber cost-to-operate SDM services for multi-tenancy environments involving multiple service partners/providers and multiple enterprises.

Embodiments provided herein may provide a multi-tenant cloud-hosted mobility service via a SDM system that facilitates allocating storage for SDM services or functionality in a manner that ensures subscription data separation between enterprise entities of the mobility service while offering service providers and/or enterprise entities the ability to determine where (in the cloud and/or on-premise) they may want the subscriber data to be stored. Further, embodiments herein may provide capabilities via any combination of Application Programming Interfaces (APIs) and/or Graphical User Interfaces (GUIs) for a managed service partner or provider and/or an enterprise entity (customer) to provide input information regarding enterprise preferences regarding where and in what manner subscription data is to be maintained (e.g., based on various use case scenarios and as constrained by choices offered/available for input and/or selection) in order facilitate per-enterprise subscriber data management in a multi-tenant network environment.

Referring toFIG.1,FIG.1is a block diagram of a system100that may facilitate per-enterprise subscriber data management for a multi-tenant network environment, according to an example embodiment. System100may include a subscriber data management (SDM) provisioning system102that can interface with a number of enterprise networks, such as enterprise networks130-1, and130-2, thru130-N, each of which is considered to be operated by a different corresponding enterprise entity (e.g., business entity, government entity, educational entity, combinations thereof, etc.). Also shown inFIG.1are a number of wireless devices, each of which may be considered to be managed by an enterprise entity operating each enterprise network130-1-130-N. For example, wireless devices132-1may be managed by the enterprise entity operating enterprise network130-1, wireless devices132-2may be managed by the enterprise operating enterprise network130-2, etc. As referred to herein, the terms ‘enterprise entity’ and ‘enterprise’ can be used interchangeably.

SDM provisioning system102may include any combination of GUI and/or API (GUI/API) input logic104, SDM model determination logic106, and SDM deployment logic to facilitate allocating storage via one or more SDM services110provided via SDM provisioning system102and, in some instances, on-premise SDM services provided for one or more enterprise networks/enterprise entities (not shown inFIG.1, discussed in further detail below), in order to store subscriber data for one or more enterprise entities, such an any enterprise entities operating any of enterprise networks130-1-130-N. In at least one embodiment, the subscriber data stored via SDM services discussed for embodiments herein may include SIM data for one or more subscribers/wireless devices that may be managed by the enterprise entities in which the SIM data can enable wireless devices of a corresponding enterprise entity to connect to a private 5G (P5G) cellular network implemented via a corresponding enterprise site/location for the enterprise network of the corresponding enterprise entity.

In some embodiments, SDM provisioning system102may be considered a multi-tenant cloud-hosted mobility service in which SDM services110may facilitate various SDM service options that can be considered cloud-hosted SDM services such that any subscriber (SIM) data provisioned/stored/managed via SDM services110may be considered for any combination of enterprise entities and/or service providers may be accessible via any of enterprise networks130-1-130-N.

In various embodiments, subscriber or SIM data for each of one or more subscribers/wireless devices managed by an enterprise entity and may include any combination of an International Mobile Subscriber Identity (IMSI), a Subscription Permanent Identifier (SUPI), a Subscription Concealed Identifier (SUCI), an Integrated Circuit Card Identifier (ICCID) ICCID, security algorithms, authentication/security key(s), etc. along with network identifier metadata that may a Public Land Mobile Network Identifier (PLMN-ID), an Access Point Name (APN) and/or Data Network Name (DNN) for session establishment, operating frequencies, etc. specific to one or more networks to which a subscriber/wireless device is authorized to attach (e.g., a P5G enterprise wireless network for one or more enterprise sites, a public mobile network, etc.).

In accordance with embodiments herein, 5GaaS offerings may include any P5G cellular network discussed herein, which may involve providing any combination of 5G cellular services and, in some instances, may also involve providing Fourth Generation (4G)/Long Term Evolution (LTE) cellular services. Different 4G/LTE/5G cellular offerings may utilize different types of SDM services for facilitating authentication/authorization of subscribers/wireless devices for connection to a given P5G cellular network of a given enterprise. SDM services that may be provided for a 4G/LTE cellular service can involve allocating storage for storing subscriber (SIM) data via an SDM service implemented as a 3GPP Home Subscriber Server (HSS), whereas, SDM services that may be provided for a 5G (or next Generation (nG)) cellular service can involve allocating storage for storing subscriber (SIM) data for an SDM service implemented as a 3GPP Unified Data Management (UDM) entity and Unified Data Repository (UDR) (UDM/UDR). Accordingly, any SDM service discussed for embodiments herein may be implemented as any combination of a 3GPP HSS and/or 3GPP UDM/UDR for storing subscriber (SIM) data and providing SDM services, which may be inclusive as any combination of authentication services, authorization services, and/or any other applicable 3GPP HSS/UDM/UDR service that may be provided for any subscribers/wireless devices of any enterprise entity and/or combination of providers/enterprise entities.

In various embodiments, SDM services110provided via SDM provisioning system102can facilitate providing various SDM service options that may be available for, supported by, or otherwise provided by SDM provisioning system, such as service-wide SDM services112, provider-specific SDM services114, and enterprise-specific SDM services116, each of which may include storage that can be allocated for utilization/storing subscriber data for each of one or more service providers and/or enterprise entities. In various embodiments, the terms ‘storage’, ‘memory element’, and/or any variation thereof may be inclusive of any suitable volatile and/or non-volatile memory item (e.g., magnetic hard disk drive, solid state hard drive, semiconductor storage device, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM), application specific integrated circuit (ASIC), etc.), non-transitory tangible media, non-transitory computer readable storage media software, logic (fixed logic, hardware logic, programmable logic, analog logic, digital logic), hardware, and/or in any other suitable component, device, element, and/or object as may be appropriate that may be used to store, manage, provide, and/or otherwise facilitate the storage of subscriber/SIM data for one or more subscribers/wireless devices. Although not shown inFIG.1, it is to be understood that SDM services110can also include any compute resources (e.g., hardware processors, logic, etc.) that may facilitate implementing any combination of HSS/UDM/UDR services.

In at least one embodiment, service-wide SDM services112can include SDM services that can be utilized to serve any combination of different service providers and different enterprise entities with subscriber data (SIM sets) for each service provider/enterprise being stored via storage provided via the service-wide SDM storage services112.

In at least one embodiment, provider-specific SDM services114can include SDM services that can be utilized to serve any combination of different enterprise entities that may be associated with the same service partner or provider. For example, a particular service provider (‘Service Provider123’) may be an authorized reseller of a 5GaaS offering/functionality facilitated via SDM provisioning system102such that the particular service provider or partner can sell or lease such functionality to multiple enterprise entities in which subscriber data for each of the multiple entities can be stored/serviced via a particular provider-specific SDM service provided via SDM provisioning system102. Thus, multiple different instances of provider-specific SDM services114may be provided via SDM provisioning system102with each particular instance of a given provider-specific SDM service serving/hosting subscriber data (SIM sets) for each of multiple different enterprises that have contracted services via a same particular service provider/partner (e.g., Enterprise1, Enterprise2, and Enterprise3, each contracting services from Service Provider123, can have their associated subscriber data stored via a particular provider-specific SDM service that is to provide SDM services to only Service Provider123).

In at least one embodiment, enterprise-specific SDM services116can include SDM services that are individually provided for each of a given enterprise entity or a given service provider and enterprise entity in which each enterprise-specific SDM service that is provided for each of a given enterprise may be isolated, physically and/or logically, from SDM services provided for other enterprise entities. Thus, multiple different instances of enterprise-specific SDM services116may be provided via SDM provisioning system with each particular instance of a given enterprise-specific SDM service serving/hosting subscriber data (a SIM set) for a given enterprise entity or a given combination of a service provider and enterprise entity, if applicable that is isolated, physically and/or logically from all other SDM services and SIM sets provided via SDM provisioning system for other enterprise entities and service providers (e.g., service-wide SDM services, provider-specific SDM services, and other enterprise-specific SDM services provided for other enterprise entities).

Different SDM services may be desired by an enterprise and/or provider for a variety of reasons/purposes. For example, selection of a given SDM service may be dependent on an enterprise/service provider desire for complete data isolation for security, country or industry regulatory reasons and/or data sovereignty reasons. Conversely, no conditions may exist that involve a need for data isolation. In some instances, using service provider instances of SDM services may be desirable for management, simplified troubleshooting (e.g., logs could be configured to include the provider/partner name along with other data), and/or other efficiencies. In still some instances, a particular SDM service may be desired to limit exposure to internal service failures by not sharing. In still some instances, a particular SDM service may be desired because a particular industry vertical is to utilize separation but not between enterprises in that vertical. Other variations can be envisioned

Broadly during operation, SDM provisioning system102may apply/utilize GUI/API input logic104, SDM model determination logic106, and SDM deployment logic108to facilitate service provider and/or enterprise provisioning to a given SDM service type based on provider and/or enterprise inputs140. For example, a service provider or enterprise entity can provide inputs140via GUI/API input logic104that include various input information including SDM model input information142, enterprise input information144, and on-premise input information146.

In various embodiments, provider/enterprise inputs140can include any combination of selections (e.g., radio button selections or the like) of available SDM services, selection of a multi-tenancy service attribute (discussed in further detail below), alpha-numeric inputs (e.g., number or size of subscriber data records to be provided/serviced for a given enterprise entity), and/or any other inputs that may be utilized via one or more GUIs and/or APIs that may facilitate providing/obtaining various input information in order to facilitate various operations of SDM provisioning system102in accordance with embodiments herein.

In some embodiments, SDM model input information142may be provided (e.g., input) for a given service provider involving SDM service for a given enterprise entity that can include a multi-tenancy service attribute that identifies whether the service provider is to be provided independent, provider-specific SDM services114or if the service provider can make use of service-wide SDM services112. For example, SDM model input information142provided for a given service provider and a given enterprise entity including a multi-tenancy service attribute of ‘Shared’ (or similar attribute/indication) can be used to indicate that provider-specific SDM services114are to be utilized to serve subscriber data for the given service provider and enterprise entity. In another example, SDM model input information142provided for a given service provider for a given enterprise entity including a multi-tenancy service attribute of ‘None’ (or similar attribute/indication, such as ‘service-wide’, ‘service’ etc.) can be used to indicate that there is no multi-tenancy service preference for the service provider/enterprise entity, such that the service attribute indicates that service-wide SDM services112can be utilized to serve subscriber data for the given service provider and enterprise entity.

In some embodiments, SDM model input information142provided for a given enterprise entity may include a multi-tenancy service attribute of ‘Unique’ (or similar attribute/indication) that can be used to indicate that enterprise-specific SDM services116are to be utilized to serve subscriber data for the given enterprise entity (and potentially for a given service provider, if applicable). Similar to the ‘Shared’ and ‘None’ multi-tenancy service attributes discussed above, in some embodiments, SDM model input information142can be used to indicate whether an enterprise entity can utilize provider-specific SDM services114or global, service-wide SDM services112.

Enterprise input information144can include any combination of location information, subscriber data record number or size information, ephemeral information, security information, jurisdictional information, and/or the like. In various embodiments, location information can include, but not be limited to, address information, region information, corporate site identifying information for an enterprise (with an internal mapping utilized to correlate sites to location), and/or the like. In various embodiments, enterprise input ephemeral information may be used to indicate one or more periods of time (e.g., time of day, specific days, etc.) associated with a ‘life’ certain subscriber data for a given enterprise entity, such that the subscriber data may be considered to be expired after expiration of the period(s) of time and/or may need to be updated. In various embodiments, security information may be used to indicate security access types for a given service provider and/or enterprise entity. Regarding security access types, in some instances a given subscriber may only be served at a specific enterprise site or subset of enterprise sites. In such instances, security access could be used to control which enterprise sites are to have subscriber data for the given subscriber. Hence, the sizing of an enterprise site provided SDM service and whether anything is deployed there can be impacted by various security access aspects. In various embodiments, jurisdictional information may be used to indicate data privacy and/or geo-political considerations that may impact SDM services provided for a given service provider/enterprise entity.

On-premise input information146can include an indication (Yes or No) that identifies whether subscriber data for a given enterprise entity is to be provided for one or more on-premise SDM services for one or more on-premise locations or ‘sites’ of a given enterprise entity. In some embodiments, on-premise input information146can include location/site identifying information such as Internet Protocol (IP) address information, Fully Qualified Domain Name (FQDN) information, specific location information, such as address, etc., region information, and/or any other identifying information that can be used to identify the one or more on-premise locations/sites at which subscriber data is to be provided for SDM services of a given enterprise network for the enterprise entity. In some embodiments, location/site identifying information for a given enterprise entity can be included in enterprise information144.

The SDM model input information142and, in particular, the multi-tenancy service attribute, along with the enterprise input information144, and on-premise input information146for a given service provider/enterprise entity can be passed from GUI/API input logic104to SDM model determination logic106in order to identify an appropriate (e.g., cloud-hosted) SDM service provided via SDM provisioning system102to utilize for serving subscriber data for the enterprise entity and, if applicable one or more on-premise (e.g., enterprise-hosted) SDM services for one or more enterprise locations/site to utilize for serving subscriber data the enterprise entity. Once identified, SDM deployment logic108can facilitate deploying SDM service instances and allocating storage for the subscriber data for the enterprise entity via the identified SDM service instance(s) at the desired scale (e.g., number/size of subscriber data records) and deployment locations (e.g., cloud-hosted via SDM provisioning system102and, if applicable, enterprise-hosted) in accordance with embodiments herein.

Consider various examples of different SDM services that may be provided for different service providers/enterprise entities based on various service provider/enterprise inputs that can be provided for SDM provisioning system102as shown viaFIG.2, which is a block diagram illustrating a system100′ in which different SDM services can be provided via SDM provisioning system102for each of: an enterprise1that is operating an enterprise1network230in which a P5G cellular network is provided for each of a site232and a site234; a service provider1that has contracted with an enterprise2to provide a P5G cellular network at a site242of an enterprise2network240; and a service provider2that has contracted with an enterprise3to provide a P5G cellular network at a site252of an enterprise3network250.

Various example details illustrated forFIG.2are discussed herein with reference to each of respectiveFIGS.3A,3B,4,5A, and5B, each of which are respective message sequence diagrams illustrating various respective example operations300,400, and500that may be performed to facilitate per-enterprise subscriber data management in a multi-tenant network environment, according to various example embodiments.

For example, each ofFIGS.3A and3B,FIG.4, andFIGS.5A and5Binclude SDM provisioning system102including GUI/API input logic104, SDM model determination logic106, and SDM deployment logic108and also includes SDM services110that can be provisioned to provide appropriate SDM services based on various input information discussed for each ofFIGS.3A-3B,FIG.4, andFIGS.5A-5Bin which different SDM service options may be identified based on the input information. For each ofFIGS.2,3A-3B,4, and5A-5B, it is assumed that all network elements (e.g., servers, cables, etc.) and network connectivity has been provided for system100′ and each of enterprise1network230, enterprise2network240, and enterprise3network25such that SDM provisioning system102can interface with each of the enterprise networks and, if applicable, SDM service(s) to be utilized at one or more site(s) of the enterprise networks.

With reference toFIGS.3A and3Binvolving operations300,FIGS.3A and3Bfurther include an enterprise1input system302and enterprise1network230. In various embodiments, enterprise1input system302include any combination of a computer/terminal, gateway, etc. that may facilitate providing displaying, selecting, inputting, and/or otherwise interacting with GUI information provided by SDM provisioning system102to facilitate enterprise1(e.g., a network administrator or the like) providing input information to SDM provisioning system102via GUI/API input logic104.

As shown at304, consider that a GUI is provided for enterprise1input system via GUI/API input logic104that indicates various SDM service options that can be facilitated via SDM provisioning system102. It is to be understood that the enterprise can analyze its desired use cases, number of subscriber data records, etc. in order to determine selections/input information to be provided to SDM provisioning system102. Further, it is to be understood that the GUI can include any user interface features, fields, radio buttons, selection buttons, etc. as may be understood in the art that can be used to facilitate inputting/receiving indications of SDM service options in accordance with any embodiments herein. Other inputs may be provided in some instances. For example, other input information can be provided for setting up radio access networks, non-SDM components, etc. for facilitating P5G on-prem cellular network(s) for an enterprise.

As shown at306, consider that enterprise1provides input information including SDM model input information that identifies enterprise1and includes a multi-tenancy service attribute set to ‘Unique’ that indicates that enterprise-specific SDM services are to be utilized to serve subscriber data for enterprise1. Further, the input information provided at306can include enterprise input information for enterprise1including size information that identifies site232at which 20000 subscriber data records are to be serviced and site234at which 20000 subscriber data records are to be serviced (thus, 40000 total subscriber records are to be serviced for enterprise1), location information indicating North America, and ephemeral information set to ‘No’ indicating that there is to be no expiration/life associated with the subscriber data managed for enterprise1. Further, the input information provided at306can include on-premise input information set to ‘Yes’ that indicates that the subscriber data for enterprise1is to be provided for SDM services at each of site232and234of enterprise1network230. Other input information and/or enterprise1data can be provided at306, such as security information, jurisdictional information, etc. in accordance with embodiments herein.

The input information is obtained by GUI/API input logic104and provided to SDM model determination logic106, as shown at308via a deployment model request message. As shown at310, SDM model determination logic106identifies, based in the input information and, in particular, the multi-tenancy service attribute that is set to ‘Unique’, that an enterprise-specific (cloud) hosted SDM service is to be utilized from the different SDM services110service options available via SDM provisioning system102in order serve the subscriber data for enterprise1. The SDM model determination logic106can further identify at310, based on the on-premise input information set to ‘Yes’ that the subscriber data for enterprise1is to be provided for an on-premise SDM service provided at each of site232and234of enterprise1network230.

Based on identifying the SDM services to be utilized for enterprise1at310, SDM model determination logic106can trigger SDM deployment logic108, as shown at312, to provide the identified SDM services. For example, based on the triggering, SDM deployment logic108can determine whether an enterprise-specific SDM service is already deployed/allocated for enterprise1and also determine that on-premise SDM services are to be utilized for site232and234, as shown at313.

Continuing toFIG.3B, to provide the identified SDM services, as shown at314and318, SDM deployment logic108can facilitate deployment of an enterprise1(cloud) hosted SDM service204(as shown inFIG.2) for storing the subscriber data for enterprise1via SDM services110by creating or allocating storage space for the enterprise1(cloud) hosted SDM service204, which may include instantiating, as generally illustrated at318, the corresponding enterprise1(cloud) hosted SDM service204(e.g., as any of a 3GPP HSS/UDM/UDR) via any combination of compute/storage resources of SDM provisioning system102/SDM services110for storing the subscriber data for enterprise1. It is to be understood that deployment of the enterprise1(cloud) hosted SDM service204can involve any operations now known in the art or hereinafter developed for providing any combination of HSS/UDM/UDR services at the desired scale. As shown at316a,a response can be provided to SDM deployment logic indicating the allocation request for the enterprise1(cloud) hosted SDM service204for enterprise1was received. Thereafter, upon completion of the instantiation/allocation of storage for the enterprise1(cloud) hosted SDM service204, an indication of successful completion of the instantiation/allocation of the storage/enterprise1(cloud) hosted SDM service204is provided to SDM deployment logic108, as shown at316b.

Further to provide the identified SDM services, as shown at320, SDM deployment logic108can also facilitate deployment of each of an enterprise1on-premise SDM service204-1and204-2for storing for the subscriber data for enterprise1to which corresponding responses can be provided at322aand322bindicating successful completion of the instantiation/allocation of the enterprise1on-premise SDM services204-1and204-2at each of site232and234for enterprise1network230. It is to be understood that deployment of the enterprise1on-premise SDM services204-1and204-1can involve any operations now known in the art or hereinafter developed for providing any combination of HSS/UDM/UDR services at the desired scale and deployment locations/sites.

Upon completing instantiation/allocation of the enterprise-specific SDM service204and each of the enterprise1on-premise SDM service204-1and204-2a message can be provided to GUI/API input logic104indicating that the SDM services for enterprise1are ready for use, as shown at324, in which such information can be provided to the enterprise1input system302.

Any subscribers/wireless devices managed by enterprise1, such as any of wireless devices236shown inFIG.2may connect to any P5G on-prem cellular network for any of site232and234using either the enterprise-specific (cloud) hosted SDM service204and corresponding subscriber data or enterprise1on-premise SDM services204-1or204-2(as appropriate) and corresponding subscriber data for registration and session establishment based on a subscription identifier for each wireless device236(e.g., IMSI, SUPI, etc.) and potentially on-premise specific configurations that may be configured for site232and/or234. For example, in some instances, subscription identifying information, such as specific IMSIs/SUPIs, etc. for certain enterprise subscribers for an enterprise could be used to steer registration/session establishment for the subscribers to utilize the enterprise-specific (cloud) hosted SDM service204even if subscription data for the subscribers is present in an on-premise SDM service.

Next, considerFIG.4involving operations400in whichFIG.4further includes a provider1input system402. In various embodiments, provider1input system402include any combination of a computer/terminal, gateway, etc. that may facilitate providing displaying. selecting, inputting, and/or otherwise interacting with GUI information provided by SDM provisioning system102to facilitate enterprise1(e.g., a network administrator or the like) providing input information to SDM provisioning system102via GUI/API input logic104.

As shown at404, consider that a GUI is provided for provider1input system via GUI/API input logic104that indicates various SDM service options that can be facilitated via SDM provisioning system102. It is to be understood that the enterprise can analyze its desired use cases, number of subscriber data records, etc. in order to determine selections/input information to be provided to SDM provisioning system102.

As shown at406, consider that provider1provides input information including SDM model input information that identifies enterprise2and includes a multi-tenancy service attribute set to ‘Shared’ and identifying service provider1that indicates that provider-specific SDM services for service provider1are to be utilized to serve subscriber data for enterprise2. Further, the input information provided at406can include enterprise input information for enterprise2including size information that identifies 40000 subscriber data records are to be serviced for enterprise2, location information indicating North America, and ephemeral information set to ‘No’ indicating that there is to be no expiration/life associated with the subscriber data managed for enterprise2. Further, the input information provided at606can include on-premise input information set to ‘No’ indicating that the subscriber data for enterprise1is not to be provided for SDM services at an enterprise site242of enterprise2network240. Other input information and/or enterprise2data can be provided at406, such as security information, jurisdictional information, etc. in accordance with embodiments herein.

The input information is obtained by GUI/API input logic104and provided to SDM model determination logic106, as shown at408via a deployment model request message. As shown at410, SDM model determination logic106identifies, based in the input information and, in particular, the multi-tenancy service attribute that is set to ‘Shared’ and identifies service provider1, that a (cloud-hosted) provider-specific SDM service is to be utilized from the different SDM services110service options available via SDM provisioning system102in order serve the subscriber data for enterprise2. The SDM model determination logic106further identifies that Role-Based Access Control (RBAC) for multitenancy is to be utilized for the provider-specific SDM service.

If the decision is made by a provider/partner to use a provider-specific SDM service across multiple enterprises, that means that RBAC is needed across that service to ensure that a particular enterprise can only view/act on the subscription data that it owns. The provider/partner can see the data of all the enterprises with which they may have a relationship (e.g., be partnered with). RBAC is access control based on user credentials that determines which action(s) can be taken on which data sets. The user credentials can be mapped to a role as part of the system configuration.

Based on identifying the SDM services to be utilized for enterprise2at408, SDM model determination logic106can trigger SDM deployment logic108, as shown at412, to provide the identified SDM service. For example, based on the triggering, SDM deployment logic108can determine whether a provider-specific SDM service is already deployed/allocated for service provider1and also determine whether storage space is available in the provider-specific SDM service for the 40000 enterprise2subscriber data records, as shown at413.

For the example ofFIG.4, consider that a provider1SDM service212(as shown inFIG.2) has already been provided/deployed via SDM services110such that to provide the identified provider-specific SDM service, as shown at414and418, SDM deployment logic108can facilitate reserving or otherwise allocating storage space of the provider1SDM service212for storing the subscriber data for enterprise2, shown inFIG.2as enterprise2subscriber data214. The operations performed by the SDM deployment logic108can include determining whether space is available in the provider1SDM service212to facilitate storage of the 40000 enterprise2subscriber data records. In some embodiments, the determination at413may result in determining that there is not currently enough space available in the provider's SDM service to facilitate storing an amount of subscriber data records (e.g., by tracking/monitoring space availability of the provider1SDM service212, by querying SDM services112regarding available space of the provider1SDM service, etc.). In such embodiments, the operations at414may include increasing the available space for the provider1SDM service212to facilitate storage of the 40000 enterprise2subscriber data records.

As shown at416a,a response can be provided to SDM deployment logic indicating the request for reserving storage space for the provider1SDM service212for the subscriber data for enterprise2was received. Thereafter, upon completion of the reservation of storage space for the subscriber data (at418) via enterprise2subscriber data214for provider1SDM service212, an indication of successful completion of the reservation is provided to SDM deployment logic108. as shown at416band a message can be provided to the GUI/API input logic104, as shown at420, indicating that the SDM services for enterprise2are ready for use.

Any subscribers/wireless devices managed by enterprise2, such as any of wireless devices246shown inFIG.2may connect to the P5G on-prem cellular network for site242of enterprise2network240using the provider1SDM service212and corresponding enterprise2subscriber data214.

Next, considerFIGS.5A and5B, involving operations500in whichFIGS.5A and5Bfurther include a provider2input system502and enterprise3network250. In various embodiments, provider2input system502include any combination of a computer/terminal, gateway, etc. that may facilitate providing displaying, selecting, inputting, and/or otherwise interacting with GUI information provided by SDM provisioning system102to facilitate enterprise1(e.g., a network administrator or the like) providing input information to SDM provisioning system102via GUI/API input logic104.

As shown at504, consider that a GUI is provided for provider2input system via GUI/API input logic104that indicates various SDM service options that can be facilitated via SDM provisioning system102. It is to be understood that the enterprise can analyze its desired use cases, number of subscriber data records, etc. in order to determine selections/input information to be provided to SDM provisioning system102.

As shown at506, consider that provider2provides input information including SDM model input information that identifies enterprise3and includes a multi-tenancy service attribute set to ‘None’ or ‘Service’ that indicates that service-wide SDM services112are to be utilized to serve subscriber data for enterprise3. Further, the input information provided at506can include enterprise input information for enterprise3including size information that identifies site252at which 40000 subscriber data records are to be serviced, location information indicating North America, and ephemeral information set to ‘No’ indicating that there is to be no expiration/life associated with the subscriber data managed for enterprise3. Further, the input information provided at506can include on-premise input information set to ‘Yes’ that indicates that the subscriber data for enterprise1is to be provided for SDM services site252of enterprise3network250. Other input information and/or enterprise3data can be provided at506, such as security information, jurisdictional information, etc. in accordance with embodiments herein.

The input information is obtained by GUI/API input logic104and provided to SDM model determination logic106, as shown at508via a deployment model request message. As shown at510, SDM model determination logic106identifies, based in the input information and, in particular, the multi-tenancy service attribute that is set to ‘None’ or ‘Service’, that the service-wide SDM services110and RBAC-based multitenancy are to be utilized from the different SDM services110service options available via SDM provisioning system102in order serve the subscriber data for enterprise3. The SDM model determination logic106can further identify at510, based on the on-premise input information set to ‘Yes’ that the subscriber data for enterprise1is to be provided for an on-premise SDM service provided at site252of enterprise3network250.

Based on identifying the SDM services to be utilized for enterprise1at510, SDM model determination logic106can trigger SDM deployment logic108, as shown at512, to provide the identified SDM services. For example, based on the triggering, SDM deployment logic108can determine that storage space is available via the service-wide SDM services112for storing the enterprise3subscriber data and also determine that on-premise SDM services are to be utilized for site252, as shown at513.

To provide the identified SDM services, as shown at514and518forFIG.5B, SDM deployment logic108can facilitate reserving or otherwise allocating storage space of the service-wide SDM services112for storing the subscriber data for enterprise3, shown inFIG.2as enterprise3subscriber data220. The operations performed by the SDM deployment logic108can include determining whether space is available in the service-wide SDM services112to facilitate storage of the 40000 enterprise3subscriber data records. In some embodiments, the determination at513may result in determining that there is not currently enough space available in the service-wide SDM services to facilitate storing an amount of subscriber data records. In such embodiments, the operations at514may include increasing the available space for the service-wide SDM services112to facilitate storage of the 40000 enterprise3subscriber data records. As shown at516a,a response can be provided to SDM deployment logic indicating the request for reserving storage space for the service-wide SDM services for the subscriber data for enterprise3was received. Thereafter, upon completion of the reservation of storage space for the subscriber data (at518) via enterprise3subscriber data220for the service-wide SDM services112, an indication of successful completion of the reservation is provided to SDM deployment logic108. as shown at516b.

Further to provide the identified SDM services, as shown at520, SDM deployment logic108can also facilitate deployment of each of an enterprise3on-premise SDM service222for storing for the subscriber data for enterprise3to which corresponding responses can be provided at522aand522bindicating successful completion of the instantiation/allocation of the enterprise3on-premise SDM service222at site252for enterprise3network250. It is to be understood that deployment of the enterprise1on-premise SDM service222can involve any operations now known in the art or hereinafter developed for providing any combination of HSS/UDM/UDR services at the desired scale and deployment locations/sites.

Upon completing instantiation/allocation of the enterprise3subscriber data220for the service-wide SDM services112and the enterprise3on-premise SDM service222a message can be provided to GUI/API input logic104indicating that the SDM services for enterprise1are ready for use, as shown at524, in which such information can be provided to the provider2input system502.

Any subscribers/wireless devices managed by enterprise3, such as any of wireless devices256shown inFIG.2may connect to the P5G on-prem cellular network for site252using either the system-wide SDM services112and corresponding enterprise3subscriber data220or the enterprise3on-premise SDM service222and corresponding subscriber data for registration and session establishment based on a subscription identifier for each wireless device236(e.g., IMSI, SUPI, etc.) and potentially on-premise specific configurations that may be configured for site252.

It is to be understood that the example operations discussed forFIGS.3A,3B,4,5A, and5B can be extended to encompass other SDM models. Once the ability to deploy different SDM complexes/services is possible, as enabled by embodiments herein, it may be possible to select/provide other SDM solution implementations that can be tailored to different use cases (e.g., simplified SDM services for some use cases, full-feature consumer mobile SP-style SDM services for other use cases, etc.).

Referring toFIG.6,FIG.6is a flowchart depicting a method according to an example embodiment. In at least one embodiment, method600may be associated with techniques that may be utilized to facilitate per-enterprise subscriber data management in a multi-tenant network environment, according to an example embodiment. In various embodiments, method600may be performed by a computing device or combination of computing devices as discussed for embodiments herein, such as SDM provisioning system102.

As shown at602, the method may include obtaining, by a subscriber data management (SDM) system (e.g., SDM provisioning system102), input information indicating SDM services requested for an enterprise entity in which the input information includes a multi-tenancy service attribute for the enterprise entity and indicates whether subscriber data for is to be provided on-premise for the enterprise entity.

At604, the method may include identifying, based on the multi-tenancy service attribute included in the input information, a particular SDM service of the SDM system for storing the subscriber data for the enterprise entity from a plurality of SDM service options provided by the SDM system. At606, the method may include deploying the particular SDM service via the SDM system for storing the subscriber data for the enterprise entity. At608, the method may include deploying one or more on-premise SDM services at each of one or more on-premise locations of the enterprise entity for storing the subscriber data based on determining that the subscriber data is to be provided on-premise for the enterprise entity.

Accordingly, embodiments herein may provide the granularity of multi-tenancy for SDM services along with different use-type(s), location(s), scale, life, etc. to facilitate different SDM services based on different SDM service options that may be identified by a service provider and/or enterprise entity such that, at provisioning time, logic provided via SDM provisioning system102can identify corresponding patterns or SDM services to be provided to service subscriber data for a given service provider/enterprise entity. Upon identifying the patterns, SDM services, etc., the corresponding SDM services can be deployed utilizing any network function (e.g., HSS/UDM/UDR) deployment techniques via SDM provisioning system102. In some instances, embodiments herein may enable other actions to be performed for SDM services, such as freezing-in-place, deleting, migrating, etc. SDM services and/or subscriber data for one or more SDM deployments.

Thus, embodiments herein may facilitate a multi-tenant cloud hosted mobility service that can ensure subscription data separation between enterprises/customers of a given SDM service whilst offering the enterprises/customers the ability to determine where they wish the subscriber data to be maintained/serviced. Therefore, in various embodiments, a capability, in the form of GUIs/APIs for a managed service partner or provider, can be provided to determine where an enterprise customer's subscription data can be held in which the determination can be based on a combination of use-case preferences and/or enterprise customer preferences constrained by the choices or SDM service options provided via SDM provisioning system102.

Referring toFIG.7,FIG.7illustrates a hardware block diagram of a computing device700that may perform functions associated with operations discussed herein in connection with the techniques depicted inFIGS.1,2,3A,3B,4,5A,5B, and6. In various embodiments, a computing device, apparatus, or system such as computing device700or any combination of computing devices700, may be configured as any entity/entities as discussed for the techniques depicted in connection with operations illustrated/discussed for various embodiments herein, such as, SDM provisioning system102, enterprise1input system302, provider1input system402, provider2input system and/or any other network function, element, and/or system discussed for any embodiments herein.

In at least one embodiment, the computing device700may be any apparatus that may include one or more processor(s)702, one or more memory element(s)704, storage706, a bus508, one or more network processor unit(s)730interconnected with one or more network input/output (I/O) interface(s)732, one or more I/O interface(s)716, and control logic720. In various embodiments, instructions associated with logic for computing device700can overlap in any manner and are not limited to the specific allocation of instructions and/or operations described herein.

For embodiments in which computing device700may be implemented as any device capable of wireless communications (e.g., a gNB, a wireless device, etc.), computing device700may further include at least one baseband processor or modem710, one or more radio RF transceiver(s)712(e.g., any combination of RF receiver(s) and RF transmitter(s)), one or more antenna(s) or antenna array(s)714.

In at least one embodiment, processor(s)702is/are at least one hardware processor configured to execute various tasks, operations and/or functions for computing device700as described herein according to software and/or instructions configured for computing device700. Processor(s)702(e.g., a hardware processor) can execute any type of instructions associated with data to achieve the operations detailed herein. In one example, processor(s)702can transform an element or an article (e.g., data, information) from one state or thing to another state or thing. Any of potential processing elements, microprocessors, digital signal processor, baseband signal processor, modem, PHY, controllers, systems, managers, logic, and/or machines described herein can be construed as being encompassed within the broad term ‘processor’.

In at least one embodiment, memory element(s)704and/or storage706is/are configured to store data, information, software, and/or instructions associated with computing device700, and/or logic configured for memory element(s)704and/or storage706. For example, any logic described herein (e.g., control logic720) can, in various embodiments, be stored for computing device700using any combination of memory element(s)704and/or storage706. Note that in some embodiments, storage706can be consolidated with memory element(s)704(or vice versa) or can overlap/exist in any other suitable manner.

In at least one embodiment, bus708can be configured as an interface that enables one or more elements of computing device700to communicate in order to exchange information and/or data. Bus708can be implemented with any architecture designed for passing control, data and/or information between processors, memory elements/storage, peripheral devices, and/or any other hardware and/or software components that may be configured for computing device700. In at least one embodiment, bus708may be implemented as a fast kernel-hosted interconnect, potentially using shared memory between processes (e.g., logic), which can enable efficient communication paths between the processes.

In various embodiments, network processor unit(s)730may enable communication between computing device700and other systems, entities, etc., via network I/O interface(s)732(wired and/or wireless) to facilitate operations discussed for various embodiments described herein. In various embodiments, network processor unit(s)730can be configured as a combination of hardware and/or software, such as one or more Ethernet driver(s) and/or controller(s) or interface cards, Fibre Channel (e.g., optical) driver(s) and/or controller(s), wireless receivers/transmitters/transceivers, baseband processor(s)/modem(s), and/or other similar network interface driver(s) and/or controller(s) now known or hereafter developed to enable communications between computing device700and other systems, entities, etc. to facilitate operations for various embodiments described herein. In various embodiments, network I/O interface(s)732can be configured as one or more Ethernet port(s), Fibre Channel ports, any other I/O port(s), and/or antenna(s)/antenna array(s) now known or hereafter developed. Thus, the network processor unit(s)730and/or network I/O interface(s)732may include suitable interfaces for receiving, transmitting, and/or otherwise communicating data and/or information (wired and/or wirelessly) in a network environment.

For embodiments in which computing device700is implemented as a wireless device or any apparatus capable of wireless communications, the RF transceiver(s)712may perform RF transmission and RF reception of wireless signals via antenna(s)/antenna array(s)714, and the baseband processor or modem710performs baseband modulation and demodulation, etc. associated with such signals to enable wireless communications for computing device700.

In one form, a computer-implemented method is provided that may include obtaining. by a subscriber data management (SDM) system, input information indicating SDM services requested for an enterprise entity, wherein the input information includes a multi-tenancy service attribute for the enterprise entity and indicates whether subscriber data for the enterprise entity is to be provided on-premise for the enterprise entity; identifying, based on the multi-tenancy service attribute included in the input information, a particular SDM service of the SDM system for storing the subscriber data for the enterprise entity from a plurality of SDM service options provided by the SDM system; deploying the particular SDM service via the SDM system for storing the subscriber data for the enterprise entity; and deploying one or more on-premise SDM services at each of one or more on-premise locations of the enterprise entity for storing the subscriber data based on determining that the subscriber data is to be provided on-premise for the enterprise entity.

In one instance, based on the multi-tenancy service attribute indicating a unique SDM service for storing the subscriber data for the enterprise entity, the deploying includes providing the particular SDM service that is a physically or logically isolated SDM service that is to serve only the subscriber data for the enterprise entity. In one instance, based on the multi-tenancy service attribute indicating a shared SDM service for the subscriber data for the enterprise entity, the deploying includes providing the particular SDM service that is a shared SDM service that is to serve the enterprise entity and one or more other different enterprise entity for a same service provider.

In one instance, based on the multi-tenancy service attribute indicating system that there is no multi-tenancy SDM service preference for the enterprise entity, the deploying includes providing the particular SDM service that is to serve the enterprise entity and any other different enterprise entity for any service providers.

In one instance, the input information further indicates a number of subscribers associated with the subscriber data for the enterprise entity. In one instance, providing the particular SDM service via the SDM system includes allocating or increasing storage for the subscriber data for the enterprise entity via the particular SDM service of the plurality of SDM services of the SDM system based on the number of subscribers indicated in the input information. In one instance, the input information further indicates an expiration time for the subscriber data for the enterprise entity. In one instance, the input information further indicates on-premise location information for the one or more on-premise locations of the enterprise entity at which the subscriber data is to be provided for one or more on-premise SDM services of the enterprise entity. In one instance, the subscriber data is Subscriber Identification Module (SIM) data for a plurality of subscribers of the enterprise entity. In one instance, the input information is obtained via at least one of a graphical user interface (GUI) or an application programming interface (API).

Accordingly, embodiments herein may facilitate cost-effective techniques for providing SDM services via a variety of possible SDM service options that can provide for achieving multi-tenancy by logically and/or physically separating enterprise entities to SDM service instances, when needed, that may be specific to the services/preferences of the enterprise entities and/or service providers. The feature set of a specific SDM service instance (e.g., enterprise-specific, provider-specific, service-wide, etc.) may, in some instances, be implemented as a reduced set of features with less complexity, as may be appropriate for the given SDM service(s) to be used by a given enterprise entity/service provider. Such factors may facilitate reduced costs for infrastructure, licensing, and/or day-to-day operations. Additionally, the day-to-day access management for a given SDM service can be simplified given the scope of the SDM service provided for a customer, enterprise, and/or service provider/partner. Additionally, embodiments herein may facilitate reducing the impact of configuration errors when setting up/providing access management hierarchies in comparison to the manual configuration processes that are often utilized for other SDM scenarios.

Variations and Implementations

Each example embodiment disclosed herein has been included to present one or more different features. However, all disclosed example embodiments are designed to work together as part of a single larger system or method. This disclosure explicitly envisions compound embodiments that combine multiple previously discussed features in different example embodiments into a single system or method.