# US 2014/0157434 A1 · System and method for accessing a service

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2014/0157434 A1
- Document ID: US20140157434A1
- Status: Published application
- Kind: A1
- Application number: 13/980,849
- Filed: 2011-01-24
- Published: 2014-06-05
- Earliest claimed: 2011-01-24
- Assignees: Hewlett Packard Enterprise Development LP
- Inventors: David Andrew Graves
- Web page: https://patentgrep.com/patent/US20140157434A1

## CPC

- H04L 63/102: {Entity profiles}
- G06F 21/335: {for accessing specific resources, e.g. using Kerberos tickets}
- H04L 63/101: {Access control lists [ACL]}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

According to one example of the present invention, there is provided, a method of accessing a service. The method comprising: receiving, from a requesting user, a request for a number of accessing users to have access to the service, generating service access data associated with the service, providing, to the requesting user, the generated service access data for distribution to the accessing users, receiving, from an accessing user, service access data, determining, based in part on the received service access data, whether the service can be provided, and where it is so determined, providing the service to the accessing.

## Claims

### Claim 1

A method of accessing a service, comprising:
receiving, from a requesting user, a request for a number of accessing users to have access to the service;
generating service access data associated with the service;
providing, to the requesting user, the generated service access data for distribution to the accessing users;
receiving, from an accessing user, service access data;
determining, based in part on the received service access data, whether the service can be provided; and
where it is so determined, providing the service to the accessing.

### Claim 2 (depends on 1)

The method of claim 1, wherein the step of receiving further comprises receiving a service access level with which the accessing users are to have access to the service.

### Claim 3 (depends on 2)

The method of claim 2, wherein the step of generating service access data generates service access data associated with the requested service access level.

### Claim 4 (depends on 3)

The method of claim 3, wherein the step of receiving a request further comprises:
receiving a request including a first request for a first number of accessing users to have access to the service with a first service access level, and a second request for a second number of accessing users to have access to the service with a second service access level;
and wherein the step of generating service access data further comprises:
generating a first portion of service access data in response to the first request, and a second portion of service access data in response to the second request.

### Claim 5 (depends on 1)

The method of claim 1, wherein the step of providing the service further comprises providing the service with the service access level associated with the received service access data.

### Claim 6 (depends on 1)

The method of claim 1, wherein the step of generating service access data generates service access data based, in part, on a characteristic of the requesting user.

### Claim 7 (depends on 1)

The method of claim 1, wherein the step of determining whether the service can be provided further comprises determining whether the number of accessing users already given access to the service does not exceed the number of users in the received request.

### Claim 8 (depends on 1)

The method of claim 1, further comprising, where it is determined that access to the service can be provided, creating an account for the accessing user, the account including authentication data to be used for authenticating the accessing user prior to providing access to the accessing user on subsequent attempts to access the service.

### Claim 9 (depends on 1)

The method of claim 1, further comprising allocating resources, based on the requested number of accessing users, to ensure that the service can be provided to the requested number of accessing users.

### Claim 10

A system for accessing a service provided by a service management system, comprising:
a service control access module to:
receive, from a user, a request to access the service, the service request including service access data, the service access data having been previously provided to the user in response to a request for a number of users to have access to the service;
determine, based in part on the received service access data, whether the service can be provided;
create an account, where it is so determined, for the accessing user, the account including authentication data to be used for authenticating the accessing user in response to a subsequent request to access the service; and
provide the user access to the service on the service management system.

### Claim 11 (depends on 10)

The system of claim 10, wherein the service control access module is further arranged to:
receive a request, from a requesting user, for a number of users to be given access to the service;
generate service access data associated with the service; and
provide the generated service access data to the requesting user.

### Claim 12 (depends on 11)

The system of claim 11, wherein the service control access module is further arranged to:
receive a request including a first request for a first number fiber of accessing users to have access to the service with a first service access level and a second request for a second number of accessing users to have access to the service with a second service access level; and
generating a first portion of service access data in response to the first request, and a second portion of service access data in response to the second request.

### Claim 13

The system of 11, wherein the service control access module is further arranged to:
receive a request including a service access level associated with the users to be given access to the service, and
generate service access data based, in part, on the received service access level.

### Claim 14 (depends on 13)

The system of claim 13, wherein the service control access module is further arranged to provide the service to the user with the service access level associated with the received service access data.

### Claim 15 (depends on 11)

The system of claim 11, wherein the service control access module is further arranged to:
determine whether the service can be provided by determining whether the number of users already been given access to the service is less than the number of users in the received request.

### Claim 16 (depends on 11)

The system of claim 11, wherein the service control access module further comprises an authentication module to provide access to the service to users who provide authentication data stored in a user account.

### Claim 17

A tangible, machine-readable medium that stores machine-readable instructions executable by a processor to provide a method of accessing to a service, the tangible, machine-readable medium comprising:
machine readable instructions that, when executed by the processor, receive, from an accessing user, a request to access a service, the service request including service access data, the service access data having been previously provided to a requesting user in response to a request from the requesting user for a number of accessing users to have access to the service with an associated service access level;
machine-readable instructions that, when executed by the processor:
determine, based in part on the received service access data, whether the service can be provided;
create an account, where it is so determined, for the accessing user, the account including authentication data to be used for authenticating the accessing user in response to a subsequent request to access the service; and
provide to the accessing user access to the service.
