# US 2015/0148009 A1 · Secure deployment of terminals in a wireless network

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

- Number: US 2015/0148009 A1
- Document ID: US20150148009A1
- Status: Published application
- Kind: A1
- Application number: 14/411,432
- Filed: 2013-06-25
- Published: 2015-05-28
- Earliest claimed: 2012-06-29
- Assignees: Neul Ltd.
- Applicants: Neul Ltd
- Inventors: William Webb
- Web page: https://patentgrep.com/patent/US20150148009A1

## CPC

- H04W 12/04: Key management, e.g. using generic bootstrapping architecture [GBA]
- H04L 9/32: including means for verifying the identity or authority of a user of the system {or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials}
- H04L 9/321: {involving a third party or a trusted authority}
- H04L 9/3213: {using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807)}
- H04L 9/3228: {One-time or temporary data, i.e. information which is sent for every authentication or authorization, e.g. one-time-password, one-time-token or one-time-key}
- H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)}
- H04L 63/0853: {using an additional device, e.g. smartcard, SIM or a different communication terminal (cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234)}
- H04L 63/0884: {by delegation of authentication, e.g. a proxy authenticates an entity to be authenticated on behalf of this entity vis-à-vis an authentication entity}
- H04W 12/06: Authentication
- G06F 21/70: Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer
- H04L 2209/80: Wireless
- H04W 4/70: Services for machine-to-machine communication [M2M] or machine type communication [MTC]
- H04W 12/71: Hardware identity
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- 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

A method for securely deploying a communication device in a communication network, the method comprising: storing a device identity and an associated token in the network; receiving, in the network, a device identity, a token and an indication of a data routing point; determining whether the received device identity and the received token correspond with a device identity and associated token stored by the network; and, if so, determining that the communication device corresponding to the received device identity has been validly deployed in the network and storing the data routing point as a destination to which data associated with the validly deployed communication device should be routed by the network.

## Claims

### Claim 1

A method for securely deploying a communication device in a communication network, the method comprising:
storing a device identity and an associated token in the network;
receiving, in the network, a device identity, a token and an indication of a data routing point;
determining whether the received device identity and the received token correspond with a device identity and associated token stored by the network;
and, if so:
determining that the communication device corresponding to the received device identity has been validly deployed in the network; and
storing the data routing point as a destination to which data associated with the validly deployed communication device should be routed by the network.

### Claim 2 (depends on 1)

A method as claimed in claim 1, comprising the network only communicating with a communication device if it is determined to have been validly deployed in the network.

### Claim 3 (depends on 1)

A method as claimed in claim 1, comprising storing, in the network, authentication data associated with a device identity.

### Claim 4 (depends on 3)

A method as claimed in claim 3, comprising only marking the authentication data as being available for use if the communication device corresponding to the associated device identity is determined to have been validly deployed in the network.

### Claim 5 (depends on 3)

A method as claimed in claim 3, comprising, when the communication device corresponding to the associated device identity is determined to have been validly deployed in the network, deriving an authentication key from the authentication data for use in communicating with that communication device.

### Claim 6 (depends on 5)

A method as claimed in claim 5, comprising the network authenticating a communication with the validly deployed communication device by means of the authentication key.

### Claim 7 (depends on 1)

A method as claimed in claim 1, comprising storing, in a communication device, a device identity corresponding to that communication device.

### Claim 8 (depends on 1)

A method as claimed in claim 1, comprising storing, in a communication device, authentication data associated with the device identity of that communication device.

### Claim 9 (depends on 1)

A method as claimed in claim 1, comprising forwarding a device identity and an associated token to a third party.

### Claim 10 (depends on 9)

A method as claimed in claim 9, comprising the third party, when it has determined that a communication device has been successfully deployed in the network, forwarding the device identity and associated token corresponding to that device to the network.

### Claim 11 (depends on 9)

A method as claimed in claim 9, comprising storing a device identity on a communication device prior to deploying that device in the network.

### Claim 12 (depends on 11)

A method as claimed in claim 11, comprising not storing, on the communication device, the token associated with the stored device identity.

### Claim 13 (depends on 11)

A method as claimed in claim 11, comprising, prior to deploying a communication device in the network, reading the device identity stored on that communication device.

### Claim 14 (depends on 1)

A method as claimed in claim 1, comprising:
generating a record code for a communication device prior to deploying that communication device in the network; and
storing the record code in association with the device identity of that communication device.

### Claim 15 (depends on 14)

A method as claimed in claim 14, comprising the third party determining that the communication device has been successfully deployed when the record code is returned to it.

### Claim 16 (depends on 15)

A method as claimed in claim 15, comprising the third party, when a record code is returned to it, forwarding the device identity associated with that record code to the network.

### Claim 17 (depends on 15)

A method as claimed in claim 15, comprising the third party, when a record code is returned to it, forwarding the token associated with the device identity associated with that record code to the network.

### Claim 18 (depends on 10)

A method as claimed in claim 10, comprising the third party, when it has determined that a communication device has been successfully deployed in the network, forwarding an indication of a data routing point for that communication device to the network.

### Claim 19 (depends on 18)

A method as claimed in claim 18, comprising the third party storing indication of the data routing point.

### Claim 20 (depends on 18)

A method as claimed in claim 18, comprising the third party receiving an indication of the data routing point from the successfully deployed communication device.

### Claim 21 (depends on 18)

A method as claimed in claim 18, comprising an indication of the data routing point being entered into the successfully deployed communication device by a user.

### Claim 22 (depends on 1)

A method as claimed in claim 1, wherein the indication of the data routing point comprises one or more of a network address, an IP address, a client portal in the network, an email address, a postal address, a telephone number or a twitter account.

### Claim 23

A network apparatus for determining that a communication device has been securely deploying in a communication network, the apparatus being configured to:
store a device identity and an associated token;
receive a device identity, a token and an indication of a data routing point;
determine whether the received device identity and the received token correspond with a device identity and associated token stored by the apparatus;
and, if so:
determine that the communication device corresponding to the received device identity has been validly deployed in the network; and
store the data routing point as a destination to which data associated with the validly deployed communication device should be routed by the network.

### Claim 24

(canceled)

### Claim 25

(canceled)
