Convida Wireless, LLC

Iot Holdings, Inc.

Interdigital Patent Holdings, Inc.

Drnc Holdings, Inc.

Nicholas J Podias

Chunxuan Ye

Qing Li

Michael F Starsinic

Dale N Seed

Paul L Russell, Jr

Rocco Di Girolamo

Jean-Louis Gauvreau

Hongkun Li

Guang Lu

Chonggang Wang

Ana Lucia Pinheiro

Quang Ly

Zhuo Chen

William Robert Flynn, Iv

Rocco DiGirolamo

Donald Alfred Fleck

Richard P Gorman

Catalina Mihaela Mladin

Prabhakar Chitrapu

Arty Chandra

Alpaslan Demir

Gregory S Sternberg

Ana Lucia A Pinheiro

John L Tomici

Athmane X Touag

Alexander Reznik

Shamim Akbar Rahman

Martino M Freda

Lijun Dong

Yogendra C Shah

Inhyok Cha

Vinod Kumar Choyi

Scott C Hergenhan

Ashish Gupta

John Cartmell

Kushanava Laha

Debjani Majumder

Reeteshkumar Varshney

Aravind Kamarajugadda

Onkarnath Upadhyay

Kenneth F Lynch

Paul Russell

Rohit Kumar

William R Flynn Iv

Jr Paul L Russel

William Robert Iv Flynn

Jr Paul L Russell

Paul L Russel

Alpaslan Y Demir

Current discovery mechanisms lack capabilities, such as capabilities related to permissions associated with a given registrant for example. In an example embodiment, a registrant of a service layer can communicate with a network node that hosts the service layer. The network node may receive a discovery request for a resource from the registrant. The discovery may request include various context. For example, the context of the discovery request may be indicative of an operation that the registrant intends to perform on the resource, a role that the registrant intends to assume if the registrant accesses the resource, a location in which the registrant intends to access the resource, or a subscription plan that the registrant intends to use if the registrant accesses the resource. Based on the context of the discovery request, the network node may determine whether one or more resources at the service layer satisfy the discovery request.

Permission based resource and service discovery

A network node is configured to initiate a first authentication and key establishment procedure with a machine to machine (M2M) device. The network node is configured to determine a key agreement between the network node and the M2M device using the first authentication and key establishment procedure. The network node is configured to initiate a second authentication and key establishment procedure with an M2M server. The network node is configured to receive a request from the M2M server for the key agreement to be used to communicate with the M2M device using the second authentication and key establishment procedure. The network node is configured to send the key agreement to the M2M server using the second authentication and key establishment procedure.

Interface of an M2M server with the 3GPP core network

The present application is at least directed to an MM gateway apparatus. The apparatus includes a non-transitory memory having instructions stored thereon for service layer online charging of a service layer event. The apparatus also includes a processor operably coupled to the non-transitory memory configured to execute a set of instructions. One of the instructions includes sending, to a service layer charging function of an MM server, a service layer rating request message for the service layer online charging of the service layer event detected by the MM gateway. The service layer event is triggered by an application registered to the MM gateway and that performs a read or write operation on a resource of the MM gateway. Another one of the instructions includes receiving, from the service layer charging function of the MM server, a rating response including the calculated amount of service units required for the MM gateway to process the service layer event. The resource is a uniquely addressable element having a Universal Resource Identifier (URI) and is a representation that can be manipulated via RESTful Create, Retrieve, Update, and Delete requests.

Methods of enabling flexible charging in M2M IoT service layer

A method of accessing services affiliated with a service provider is disclosed. An issuer performs a bootstrap procedure with the at least one discovered service provider. The issuer performs a discovery procedure to determine available service capability layers (SCLs) supported by the at least one discovered service provider. The issuer transmits a domain name system-based service discovery (DNS-SD) query from the issuer to a DNS-SD M2M service discovery function (MSDF) server. The DNS-SD MSDF server is provisioned with SCL discovery records. The DNS-SD MSDF server is registered with a public DNS registrar entity. The SCL discovery records include, for each SCL, a type of M2M service capabilities supported by each SCL and a class of M2M services supported by each SCL. The issuer receives SCL discovery records from the DNS-SD MSDF server in response to the DNS-SD query.

Method and apparatus for accessing services affiliated with a discovered service provider

Systems, methods, and instrumentalities are disclosed to propagate announcement and de-announcement of a resource across one or more networks. A first entity, which may be a hosting service capability layer (SCL), may receive a request from an issuer to announce a resource. The first entity may create a representation of the resource. The representation may be referred to as an announced resource. The first entity may send an announce resource request to a second entity (e.g., an announced-to SCL), which may be registered with the first entity. The announce resource request may be sent over an mId interface. The first entity may receive a first response from the second entity over the mId interface indicating that the second entity created the announced resource.

Machine-to-machine (M2M) interface procedures for announce and de-announce of resources

The present application is at least directed to an apparatus on a network. The apparatus includes a non-transitory memory having instructions stored thereon for online charging of an event. The apparatus also includes a processor that is operably coupled to the non-transitory memory. The processor is configured to execute the instructions of receiving, from an M2M gateway, a rating request message for service layer online charging. The processor is also configured to execute the instructions of determining a rating scheme to charge for the event. The processor is further configured to execute the instructions of calculating an amount of service units based on the rating request message and determined rating scheme. The processor is even further configured to execute the instructions of sending, to the M2M gateway, a rating response based upon the calculated amount of service units.

Methods of enabling flexible charging in M2M IOT service layer

A machine-to-machine (M2M) gateway (GW) includes reachability, addressing, and repository (RAR) capability. The GW maintains a local mapping table and local device application repository, performs data aggregation, address/name translation, provides event reporting and establishes GW reachability and wake-up time. The GW supports requests from M2M applications or other capabilities within the GW, and from a network and application (N&A) domain RAR. The GW may include an M2M device and M2M gateway management (MDGM) capability that receives management requests for an M2M device and functions as a network proxy. The MDGM accepts and processes requests from the N&A domain on behalf of the M2M device and performs management functions of the M2M device on behalf of the N&A domain. The MDGM may request the N&A domain for permission to interact with the M2M device, initiate an interaction for device management tasks with the M2M device, and report to the N&A domain.

Machine-to-machine (M2M) gateway (GW) and method for M2M registration

The present application is directed to a method for registering with a service layer. The method includes the step of forming a registration group of one or more applications. The method also includes a step of receiving a request to join the registration group, from the one or more applications based upon a review of criteria. The method also includes a step of receiving a registration preference from the one or more applications. Further, the method includes the step of performing service discovery on a network based upon the registration preference of the one or more applications in the registration group. The present application is also directed to a device for registering with a service layer. The present application is further directed to a computer-implemented method for moving from a current service layer to a new service layer.

Registration management in the service layer

Method and apparatus for supporting machine-to-machine (M2M) communications in a hierarchical network architecture including an M2M gateway are disclosed. An M2M entity, (such as M2M device, M2M gateway, or M2M network entity), may perform a service capability discovery procedure to discover an M2M service capability entity that may provide an M2M service capability, and register with the discovered M2M service capability entity. The address or identity of the service capability entity may be pre-configured or obtained from the dispatcher server. The M2M entity may indicate a support M2M service identifier and receive an identity or address of the M2M service capability entity mapping the service identifier. The gateway may advertise M2M service identifiers supported by the gateway so that the M2M device may access the gateway if there is a match. The address of M2M service capability entities may be obtained from the core network.

Method and apparatus for supporting machine-to-machine communications

A method and apparatus are described for accessing services affiliated with a service provider. A first discovery procedure may be performed to discover at least one service provider, and a bootstrap procedure may be performed with the at least one discovered service provider. A second discovery procedure may then be performed to determine available service capability layers (SCLs) supported by the at least one discovered service provider. The first discovery procedure may include transmitting a service provider discovery request including information for querying a record database to determine matching service provider discovery records, and receiving a service provider discovery response including a service discovery function record list that matches queries in the service provider discovery request. At least one service provider from the service discovery function record list may be selected to bootstrap with. Various versions of the second discovery procedure are described.

Machine-to-machine gateway architecture and functionality, wherein the machine-to-machine gateway includes a reachability, addressing, and repository (RAR) entity

An M2M Server may be integrated into a 3GPP network. A network node, for example a Serving General Packet Radio Service (GPRS) Support Node (SGSN) may include a dedicated interface with a M2M server. The interface may be called a GM2M interface. The interface may be a logical interface internal to the network node. The node may receive subscriber data and control data, wherein the control data facilitates a network control procedure and the subscriber data identifies a device involved in the network control procedure. The node may determine that the device involved in the network control procedure is a machine to machine device based on the subscriber data. The node may also send the control data to a machine to machine server using a message sent via a dedicated interface with the machine to machine server.

The implementation of Local IP Access (LIPA), 'Extended' LIPA (ELIPA), and Selected IP Traffic Offload (SIPTO) for the design of a 'Converged Gateway' (CGW) are disclosed. The gateway system may provide various features such as femtocell access to local networks, public Internet, and private service provider networks.

Extended local IP access for a converged gateway in a hybrid network

Growing community of inventors

Brooklyn, NY, United States of America

Nicholas J Podias