# US 2016/0366716 A1 · Enabling different device triggering aspects in a machine to machine communication system

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

- Number: US 2016/0366716 A1
- Document ID: US20160366716A1
- Status: Published application
- Kind: A1
- Application number: 15/118,068
- Filed: 2015-02-10
- Published: 2016-12-15
- Earliest claimed: 2014-02-10
- Assignees: Zte Corporation
- Applicants: Zte Corporation
- Inventors: Rajesh Bhalla
- Web page: https://patentgrep.com/patent/US20160366716A1

## CPC

- H04W 76/14: Direct-mode setup
- H04L 61/106: across networks, e.g. mapping telephone numbers to data network addresses
- H04W 4/70: Services for machine-to-machine communication [M2M] or machine type communication [MTC]
- H04L 67/12: specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- 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)

## Abstract

In a machine to machine (M2M) communication system, a request for a service targeted to a common service entity (CSE) with a CSE-ID is received from an underlying network, a M2M device which is associated with the CSE ID for the service request is identified using a M2M external identifier (M2M-Ext-ID). Provisioning operations for a pre-provisioned M2M-Ext-ID and a dynamic M2M-Ext-ID are performed at different domains from each other.

## Claims

### Claim 1

A method for facilitating Machine-to-Machine (M2M) communication, the method comprising:
receiving a request for a service targeted to a common service entity (CSE) with a CSE-ID from an underlying network, wherein the CSE comprises one or more service functions that are common to multiple M2M services;
identifying an M2M device associated with the CSE-ID for the service request using an M2M external identifier (M2M-Ext-ID) associated with the M2M device; and
performing provisioning operations for at least one of a pre-provisioned M2M-Ext-ID and a dynamic M2M-Ext-ID at different domains from each other.

### Claim 2 (depends on 1)

The method of claim 1, wherein the performing of the provisioning operations including:
provisioning, for a pre-provisioned M2M-Ext-ID, the M2M-Ext-ID along with an associated CSE-ID at an infrastructure node in an infrastructure domain; and
provisioning, for a dynamic M2M-Ext-ID, the M2M-Ext-ID at a M2M device hosting the CSE in a field domain.

### Claim 3 (depends on 1)

The method of claim 1, further including:
mapping the M2M-Ext-ID to an underlying network specific identifier.

### Claim 4 (depends on 3)

The method of claim 3, further including:
maintaining the association among the CSE-ID, the M2M-Ext-ID and the underlying network specific identifier.

### Claim 5 (depends on 1)

The method of claim 1, wherein the M2M-Ext-ID provisioned in the field domain is transferred to an IN-CSE.

### Claim 6

An apparatus for facilitating Machine-to-Machine (M2M) communication, the apparatus comprising:
a receiving module receiving a request for a service targeted to a common service entity (CSE) with a CSE-ID from an underlying network;
an identifying module that identifies a M2M device associated with the CSE ID for the service request using a M2M external identifier (M2M-Ext-ID); and
a provisioning module that performs provisioning operations for a pre-provisioned M2M-Ext-ID and a dynamic M2M-Ext-ID at different domains from each other.

### Claim 7 (depends on 6)

The apparatus of claim 6, the provisioning module provisions, for a pre-provisioned M2M-Ext-ID, the M2M-Ext-ID along with an associated CSE-ID at an infrastructure node in an infrastructure domain and provisions, for a dynamic M2M-Ext-ID, the M2M-Ext-ID at a M2M device hosting the CSE in a field domain.

### Claim 8 (depends on 6)

The apparatus of claim 6, wherein the underlying network maps the M2M-Ext-ID to the underlying network specific identifier allocated to the M2M device.

### Claim 9 (depends on 6)

The apparatus of claim 6, wherein the CSE at the M2M device does not recognize the M2M-Ext-ID assigned to the M2M device.

### Claim 10 (depends on 6)

The apparatus of claim 6, the M2M-Ext-ID provisioned in the field domain is transferred to an IN-CSE during a CSE registration.

### Claim 11

A method for facilitating Machine-to-Machine (M2M) communication, the method comprising:
receiving a request from an underlying network for a device triggering service;
identifying a remote entity to which the triggering is routed using a Trigger-Recipient-ID attributed received with the request; and
performing provisioning operations for at least one of a pre-provisioned M2M-Ext-ID and a dynamic M2M-Ext-ID at different domains from each other.

### Claim 12 (depends on 11)

The method of claim 11, the performing of the provisioning operations including:
provisioning, for a pre-provisioned M2M-Ext-ID, the Trigger-Recipient-ID at an infrastructure node in an infrastructure domain; and
provisioning, for a dynamic M2M-Ext-ID, the Trigger-Recipient-ID at a M2M device hosting a common service entity (CSE) in a field domain.

### Claim 13 (depends on 12)

The method of claim 12, the performing of the provisioning operations further including:
provisioning the M2M-Ext-ID and an associated CSE-ID at the infrastructure node.

### Claim 14 (depends on 12)

The method of claim 12, wherein the Trigger-Recipient-ID provisioned in the field domain is transferred to an IN-CSE.

### Claim 15

An apparatus for facilitating Machine-to-Machine (M2M) communication, the apparatus comprising:
a receiving module that receives a request from an underlying network for a device triggering service;
an identifying module that identifies a remote entity to which the triggering is routed using a Trigger-Recipient-ID; and
a provisioning module that performs provisioning operations for a pre-provisioned M2M-Ext-ID and a dynamic M2M-Ext-ID at different domains from each other.

### Claim 16 (depends on 15)

The apparatus of claim 15, the provisioning module provisions, for a pre-provisioned M2M-Ext-ID, the Trigger-Recipient-ID at an infrastructure node in an infrastructure domain and provisions, for a dynamic M2M-Ext-ID, the Trigger-Recipient-ID at a M2M device hosting a common service entity (CSE) in a field domain.

### Claim 17 (depends on 16)

The apparatus of claim 16, wherein the provisioning module further provisions the M2M-Ext-ID and an associated CSE-ID at the infrastructure node.

### Claim 18 (depends on 16)

The apparatus of claim 16, wherein the Trigger-Recipient-ID provisioned in the field domain is transferred to an IN-CSE.

### Claim 19 (depends on 1, 2, 3, 4, 5, 11, 12, 13, 14)

A computer program product having code stored thereon, the code, when executed, causing a processor to implement a method described in any one of claims 1-5 and 11-14.
