Provisioning

From Wikipedia, the free encyclopedia
  (Redirected from Service provisioning)
Jump to: navigation, search
For other uses, see Provisioning (disambiguation).

In telecommunication, provisioning is the process of preparing and equipping a network to allow it to provide (new) services to its users. In National Security/Emergency Preparedness telecommunications services, "provisioning" equates to "initiation" and includes altering the state of an existing priority service or capability.[1]

Network provisioning or service mediation are terms referring to provisioning of the customer’s services to the network elements, mostly used in the telecommunication industry. It requires the existence of networking equipment and depends on network planning and design.

In a modern signal infrastructure employing information technology at all levels, there is no possible distinction between telecommunications services and "higher level" infrastructure. Accordingly, provisioning configures any required systems, provides users with access to data and technology resources, and refers to all enterprise-level information resource management involved.

Provisioning is typically managed by a CIO, and necessarily involves human resources and IT departments cooperating to:

  • give users access to data repositories or grant authorization to systems, network applications and databases based on a unique user identity, and
  • appropriate for their use of hardware resources, such as computers, mobile phones and pagers.

As its most central responsibility, the provisioning process monitors access rights and privileges to ensure the security of an enterprise's resources and user privacy. As a secondary responsibility, it ensures compliance and minimizes the vulnerability of systems to penetration and abuse. As a tertiary responsibility, it tries to reduce the amount of custom configuration using boot image control and other methods that radically reduce the number of different configurations involved.

"Provisioning" often appears in the context of virtualization, orchestration, utility computing, cloud computing, and open configuration concepts and projects. For instance, the OASIS Provisioning Services Technical Committee (PSTC) defines an XML-based framework for exchanging user, resource, and service provisioning information, e.g. SPML (Service Provisioning Markup Language) for "managing the provisioning and allocation of identity information and system resources within and between organizations".

Once provisioned, the process of SysOpping ensures that services are maintained to the expected standards. Provisioning thus refers only to the setup or startup part of the service operation, and SysOpping to the ongoing responsibility.

Network provisioning[edit]

The services which are assigned to the customer in the customer relationship management (CRM) have to be provisioned on the network element which is enabling the service and allows the customer to actually use the service. The relation between a service configured in the CRM and a service on the network elements is not necessarily a 1:1 relation. Some services can be enabled by more than one network element, e.g. the Microsoft Media Server (mms://) service.

During the provisioning, the service mediation device translates the service and the corresponding parameters of the service to one or more services/parameters on the network elements involved. The algorithm used to translate a system service into network services is called provisioning logic.

Electronic invoice feeds from your carriers can be automatically downloaded directly into the core of the telecom expense management (TEM) software and it will immediately conduct an audit of each single line item charge all the way down to the User Support and Operations Center (USOC) level. The provisioning software will capture each circuit number provided by all of your carriers and if bills outside of the contracted rate an exception rule will trigger a red flag and notify the pre-established staff member to review the billing error.

Server provisioning[edit]

Server provisioning is a set of actions to prepare a server with appropriate systems, data and software, and make it ready for network operation. Typical tasks when provisioning a server are: select a server from a pool of available servers, load the appropriate software (operating system, device drivers, middleware, and applications), appropriately customize and configure the system and the software to create or change a boot image for this server, and then change its parameters, such as IP address, IP Gateway to find associated network and storage resources (sometimes separated as resource provisioning) to audit the system. By auditing the system, you ensure OVAL compliance with limit vulnerability, ensure compliance, or install patches. After these actions, you restart the system and load the new software. This makes the system ready for operation. Typically an internet service provider (ISP) or Network Operations Center will perform these tasks to a well-defined set of parameters, for example, a boot image that the organization has approved and which uses software it has license to. Many instances of such a boot image create a virtual dedicated host.

There are many software products available to automate the provisioning of servers, services and end-user devices. Examples: HP Server Automation, IBM Tivoli Provisioning Manager, Redhat Kickstart, xCAT, HP Insight CMU, etc. Middleware and applications can be installed either when the operating system is installed or afterwards by using an Application Service Automation tool. Further questions are addressed in academia such as when provisioning should be issued and how many servers are needed in multi-tier,[2] or multi-service applications.[3]

In cloud computing servers may be provisioned via a web user interface or an application programming interface. One of the unique things about cloud computing is how rapidly and easily this can be done. Monitoring software can be used to trigger automatic provisioning when existing resources become too heavily stressed.[4]

In short, server provisioning configures servers based on resource requirements. The use of a hardware or software component (e.g. single/dual processor, RAM, HDD, RAID controller, a number of LAN cards, applications, OS, etc.) depends on the functionality of the server, such as ISP, virtualization, NOS, or voice processing. Server redundancy depends on the availability of servers in the organization. Critical applications have less downtime when using cluster servers, RAID, or a mirroring system.

Service used by most larger scale centers in part to avoid this. Additional resource provisioning may be done per service.[5]

User provisioning[edit]

Further information: User provisioning software

User provisioning refers to the creation, maintenance and deactivation of user objects and user attributes, as they exist in one or more systems, directories or applications, in response to automated or interactive business processes. User provisioning software may include one or more of the following processes: change propagation, self-service workflow, consolidated user administration, delegated user administration, and federated change control. User objects may represent employees, contractors, vendors, partners, customers or other recipients of a service. Services may include electronic mail, inclusion in a published user directory, access to a database, access to a network or mainframe, etc. User provisioning is a type of identity management software, particularly useful within organizations, where users may be represented by multiple objects on multiple systems.

Self-service provisioning for cloud computing services[edit]

On-demand self-service is described by the National Institute of Standards and Technology (NIST) as an essential characteristic of Cloud computing.[6] The self-service nature of cloud computing lets end users obtain and remove cloud services―including applications, the infrastructure supporting the applications,[7] and configuration―[8] themselves without requiring the assistance of an IT staff member.[9] The automatic self-servicing may target different application goals and constraints (e.g. deadlines and cost),[10][11] as well as handling different application architectures (e.g., bags-of-tasks and workflows).[12] Cloud users can obtain cloud services through a cloud service catalog or a self-service portal.[13] Because business users can obtain and configure cloud services themselves, this means IT staff can be more productive and gives them more time to manage cloud infrastructures.[14]

However one problem of cloud service provisioning is that it is not instantaneous. A cloud VM can be acquired at any time by the user, but it may take up to several minutes for the acquired VM to be ready to use. The VM startup time is dependent on factors, such as image size, VM type, data center location, number of VMs, etc.[15] Cloud providers have different VM startup performance.

Mobile subscriber provisioning[edit]

Mobile subscriber provisioning refers to the setting up of new services, such as GPRS, MMS and Instant Messaging for an existing subscriber of a mobile phone network, and any gateways to standard Internet chat or mail services. The network operator typically sends these settings to the subscriber's handset using SMS text services or HTML, and less commonly WAP, depending on what the mobile operating systems can accept.

A general example of provisioning is with data services. A mobile user who is using his or her device for voice calling may wish to switch to data services in order to read emails or browse the Internet. The mobile device's services are "provisioned" and thus the user is able to stay connected through push emails and other features of smartphone services.

Device management systems can benefit end-users by incorporating plug and play data services, supporting whatever device the end-user is using.[citation needed]. Such a platform can automatically detect devices in the network, sending them settings for immediate and continued usability.[citation needed] The process is fully automated, keeping the history of used devices and sending settings only to subscriber devices which were not previously set. One method of managing mobile updates is to filter IMEI/IMSI pairs.[citation needed] Some operators report activity of 50 over-the-air settings update files per second.[citation needed]

Mobile content provisioning[edit]

This refers to delivering mobile content, such as mobile internet to a mobile phone, agnostic of the features of said device. These may include operating system type and versions, Java version, browser version, screen form factors, audio capabilities, language settings and a plethora of other characteristics. As of April 2006, an estimated 5000 permutations are relevant. Mobile content provisioning facilitates a common user experience, though delivered on widely different handsets.

Internet access provisioning[edit]

When getting a user / customer online, beyond user provisioning and network provisioning, the client system must be configured. This process may include many steps, depending on the connection technology in question (DSL, Cable, Fibre, etc.). The possible steps are:

  • modem configuration
  • authentication with network
  • install drivers
  • setup Wireless LAN
  • secure operating system (primarily for Windows only)
  • configure browser provider-specifics
  • e-mail provisioning (create mailboxes and aliases)
  • e-mail configuration in client systems
  • install additional support software
  • install add-on packages purchased by the customer
  • etc.

There are four approaches to provisioning an internet access:

  • Hand out manuals. Manuals are a great help for experienced users, but inexperienced users will need to call the support hotline several times until all internet services are accessible. Every unintended change in the configuration, by user mistake or due to a software error, results in additional calls.
  • On-site setup by a technician. Sending a technician on-site is the most reliable approach from the provider’s point of view, as the person ensures that the internet access is working, before leaving the customer’s premises. This advantage comes at high costs – either for the provider or the customer, depending on the business model. Furthermore it is inconvenient for customers, as they have to wait until they get an installation appointment and because they need to take a day off from work. For repairing an internet connection on-site or phone support will be needed again.
  • Server-side remote setup. Server-side modem configuration uses a protocol called TR-069. It is widely established and reliable. At the current stage it can only be used for modem configuration. Protocol extensions are discussed, but not yet practically implemented, particularly because most client devices and applications do not support them yet. All other steps of the provisioning process are left to the user, typically causing lots of rather long calls to the support hotline.
  • Installation CD. Also called a "client-side self-service installation" CD, it can cover the entire process from modem configuration to setting up client applications, including home networking devices. The software typically acts autonomously, i.e. it doesn’t need an online connection and an expensive backend infrastructure. During such an installation process the software usually also install diagnosis and self-repair applications that support customers in case of problems, avoiding costly hotline calls. Such client-side applications also open completely new possibilities for marketing, cross- and up-selling. Such solutions come from highly specialised companies or directly from the provider’s development department.

References[edit]

  1. ^  This article incorporates public domain material from the General Services Administration document "Federal Standard 1037C".
  2. ^ Bhuvan Urgaonkar, Prashant Shenoy, Abhishek Chandra, Pawan Goyal and Timothy Wood. Agile dynamic provisioning of multi-tier Internet applications. ACM Transactions on Autonomous and Adaptive Systems 3(1), March 2008.
  3. ^ Jiang Dejun, Guillaume Pierre and Chi-Hung Chi. Autonomous Resource Provisioning for Multi-Service Web Applications. In Proceedings of the 19th International World-Wide Web conference, April 2010.
  4. ^ Amies A, Sanchez J, Vernier D, and Zheng X D, 2011. Monitor services in the cloud IBM developerWorks, February 15.
  5. ^ He, Sijin; L. Guo, Y. Guo, M. Ghanem,. Improving Resource Utilisation in the Cloud Environment Using Multivariate Probabilistic Models. 2012 2012 IEEE 5th International Conference on Cloud Computing (CLOUD). pp. 574–581. doi:10.1109/CLOUD.2012.66. ISBN 978-1-4673-2892-0. 
  6. ^ Mell, Peter; Grance, Timothy. "The NIST definition of cloud computing", Special Publication 800-145, National Institute of Standards and Technology
  7. ^ He, Sijin; L. Guo; Y. Guo; C. Wu; M. Ghanem; R. Han. Elastic Application Container: A Lightweight Approach for Cloud Resource Provisioning. 2012 IEEE 26th International Conference on Advanced Information Networking and Applications (AINA). pp. 15–22. doi:10.1109/AINA.2012.74. ISBN 978-1-4673-0714-7. 
  8. ^ Perera, David. "The real obstacle to federal cloud computing", Fierce Government IT, July 12, 2012
  9. ^ MSV, Janakiram. "Top 10 reasons why startups should consider cloud". Cloud Story, July 20, 2012
  10. ^ Mao, Ming; M. Humphrey (2011). "Auto-scaling to minimize cost and meet application deadlines in cloud workflows". Proceedings of 2011 International Conference for High Performance Computing, Networking, Storage and Analysis (SC2011). doi:10.1145/2063384.2063449. ISBN 978-1-4503-0771-0. 
  11. ^ Mao, Ming; M. Humphrey (2013). "Scaling and Scheduling to Maximize Application Performance within Budget Constraints in Cloud Workflows". Proceedings of the 2013 IEEE 27th International Symposium on Parallel and Distributed Processing(IPDPS2013): 67–78. doi:10.1109/IPDPS.2013.61. ISBN 978-0-7695-4971-2. 
  12. ^ Mao, Ming; J. Li and M. Humphrey (2010). 2010 11th IEEE/ACM International Conference on Grid Computing (Grid2010). pp. 41–48. doi:10.1109/GRID.2010.5697966. ISBN 978-1-4244-9347-0. 
  13. ^ Onisick, Joe. "Five steps to building a private cloud," Network Computing, July 23, 2012 [1]
  14. ^ Cowie, Jason. "How to make private cloud initiatives matter to your CEO", The Data Center Journal, July 17, 2012
  15. ^ Mao, Ming; M. Humphrey (2012). "A Performance Study on the VM Startup Time in the Cloud". Proceedings of 2012 IEEE 5th International Conference on Cloud Computing (Cloud2012): 423. doi:10.1109/CLOUD.2012.103. ISBN 978-1-4673-2892-0. 

External links[edit]

Customer provisioning at DMOZ

Identity provisioning