WO2015149530A1

WO2015149530A1 - M2m application service method, device and system

Info

Publication number: WO2015149530A1
Application number: PCT/CN2014/092973
Authority: WO
Inventors: 邵伟翔
Original assignee: 中兴通讯股份有限公司
Priority date: 2014-03-31
Filing date: 2014-12-03
Publication date: 2015-10-08
Also published as: CN104954347A

Abstract

Disclosed are an M2M application service method, device and system, the system comprising: an application entity configured to provide an end-to-end application logic; a general service entity configured to provide a general service function of an M2M environment, the general service entity comprising at least one service module, and each service module comprising one or more services; and an underlying network service entity configured to provide service for the general service entity. Based on the M2M application service system in a service-oriented architecture, the present invention further facilitates managing terminals of different internet of things in a centralized manner and providing M2M service.

Description

M2M application service method, device and system

Technical field

The present invention relates to the field of communications, and in particular, to an M2M application service method, apparatus, and system.

Background technique

The Internet of Things is an important part of the new generation of information technology. Its English name is “The Internet of things”. As the name suggests, the Internet of Things is the Internet that connects things to things. The ITU Internet Report issued by the International Telecommunication Union (ITU) defines the Internet of Things as follows: information sensing through two-dimensional code reading devices, radio frequency identification (RFID) devices, infrared sensors, global positioning systems, and laser scanners. Equipment, a network that connects any item to the Internet in accordance with a contracted agreement for information exchange and communication to enable intelligent identification, location, tracking, monitoring, and management.

The concept of M2M is often introduced in the Internet of Things, which can be explained as Man to Man, Man to Machine, Machine to Machine. In essence, the interaction between people and machines, machines and machines is mostly to achieve information exchange between people. The M2M network is the main form of the current IoT network. The M2M network includes a machine-to-machine communication network, a human-to-machine communication network, and a machine-to-human communication network. The devices of the M2M network mainly include an M2M terminal, an M2M gateway, and an M2M server.

1 is a schematic diagram of an Internet of Things system according to the related art. As shown in FIG. 1, an Internet of Things can be classified into a private Internet of Things (generally providing services to a single institution), and a public Internet of Things (based on the Internet to provide a public or large user community). Service), community Internet of Things (providing services to an associated "community" or community), etc. At the same time, the Internet of Things has a large number of applications in different industries, including intelligent agriculture, smart grid, intelligent transportation, intelligent logistics, smart medical, smart home and so on. In particular, each of these industries deploys their own specialized Internet of Things including corresponding professional IoT/M2M devices such as terminals, gateways, and servers.

The public IoT system in the related art is based on a module architecture, which is not conducive to the unified management and provision of M2M services for telecom operators as public IoT service providers for various IoT terminals.

Summary of the invention

An embodiment of the present invention provides an M2M application service method, apparatus, and system, so as to at least solve the public IoT system in the related art, which is disadvantageous for a telecommunication operator to perform unified management of terminals of various Internet of Things as a public IoT service provider. Provide questions about M2M services.

According to an aspect of the present invention, an M2M application service system is provided, comprising: an application entity configured to provide end-to-end application logic; a general service entity configured to provide a general service function of an M2M environment, wherein the universal service entity At least one service module is included, each of the service modules including one or more services; and an underlying network service entity configured to provide services to the universal service entity.

Preferably, the service module comprises: a service exposure module configured to expose a service to the application entity; a network service utilization module configured to use a service of the underlying network service entity; and a remote service exposure module configured to be The M2M environment connects to external services.

Preferably, the service module comprises at least one of the following: a service service module or an orchestration module, configured to provide one of the following services: a service service, a terminal management service, a data exchange service, a data storage service, a group management service, and a location service. Terminal and/or application loading module, configured to provide terminal and/or application loading service; accounting module, set to provide one of the following services: accounting service, billing service; infrastructure module, set to provide the following services A: an authorization service, a security service, an authentication service; a subscription management module configured to provide a subscription management service; a message brokering module or an adaptation module configured to provide a protocol to adapt the service of the underlying network service entity and/or other M2M environment Service.

According to another aspect of the present invention, an M2M application service method is provided, comprising: responding to an M2M service of a general service entity consumed by an application entity, wherein the M2M service comprises at least one of the following: a service service, a terminal management service, and a data. An exchange service, a data storage service, a group management service, a location service; a service of an underlying network service entity and/or a service of another M2M environment is invoked according to the M2M service.

Preferably, the M2M service further includes at least one of the following: a terminal and/or an application loading service, a subscription management service, an authorization service, a security service, an authentication service, a billing service, and a billing service.

Preferably, the information used by the M2M service includes at least one of the following: an M2M request identifier for identifying the message request information, an M2M request initiator for identifying an originating object, and an M2M terminal identifier for identifying the M2M. Terminal; M2M service identifier for identifying M2M service; M2M external identifier for M2M service provider identification external network domain, including underlying network or other domain M2M service provider; application identifier for identifying application entity; service subscription Identifier, used for M2M service provider binding application, M2M terminal, service, subscription relationship between common service entities; service capability identifier, used to identify service capability or operation; An identifier for identifying event information; management object information, including management data and a general structure thereof that can map an external management data model; management command information, including a method for executing a management process or executing a command or a remote procedure call; transmitting information, Contains execution content indicating initialization and management data transfer; group information, including group resource content; location policy information, including method for acquiring and managing geographic location information of the M2M node; M2M node information, including an application entity running on the node And general service entity information; scheduling information, including scheduling time period and/or scheduling repetition period; remote universal service entity information, representing a remote universal service entity registered in the local general service entity; terminal information, representing the shared content of the terminal Terminal capability information, used to manage the capabilities of the terminal; event log information, used to record the event log of the terminal.

Preferably, the service service comprises at least one of the following service capabilities or operations: accepting an application request, acquiring a service capability, and acquiring a service service.

Preferably, the terminal management service is used to provide services managed by the terminal, including at least one of the following: terminal configuration, terminal diagnosis and/or monitoring, terminal firmware management, and terminal topology management.

Preferably, the data exchange service is configured to provide an application with data exchange under a service subscription relationship, wherein the data exchange service provides at least one service capability or operation: exchange data based on a publishing manner, subscription-based manner Exchange data, exchange data based on the request response method.

Preferably, the subscription management service is configured to maintain a subscription relationship and/or a role, wherein the subscription management service provides at least one of the following service capabilities or operations: verifying the service service, and obtaining the authorization.

Preferably, the application and/or terminal loading service comprises at least one of the following service capabilities or operations: maintenance terminal template, maintenance terminal and/or application credentials, terminal and/or application discovery, policy, terminal and/or application registration .

Preferably, the authorization service is configured to provide a service capability or operation that can be used to authorize the requester, including at least one of the following service capabilities or operations: authorization service capability or operation.

Preferably, the billing service comprises at least one of the following service capabilities or operations: initiating event collection, stopping event collection, and collecting statistics.

According to still another aspect of the present invention, an M2M application service apparatus is provided, comprising: a response module, configured to respond to an M2M service of a general service entity consumed by an application entity, wherein the M2M service comprises at least one of: a service service, a terminal management service, a data exchange service, a data storage service, a group management service, a location service, and a service module, configured to invoke a service of the underlying network service entity and/or a service of another M2M environment according to the M2M service.

Through an embodiment of the present invention, an application entity is configured to provide end-to-end application logic; a general service entity is configured to provide a general service function of an M2M environment, the universal service entity includes at least one service module, and each service module includes one or more And the underlying network service entity, set to serve the generic service entity. The service-oriented architecture-based M2M application service system is more conducive to unified management and provision of M2M services for terminals of different Internet of Things.

DRAWINGS

The drawings described herein are intended to provide a further understanding of the invention, and are intended to be a part of the invention. In the drawing:

1 is a schematic diagram of an Internet of Things system according to the related art;

2 is a block diagram of an M2M application service system according to an embodiment of the present invention;

3 is a structural block diagram of a preferred general service entity in accordance with an embodiment of the present invention;

4 is a flowchart of an M2M application service method according to an embodiment of the present invention;

FIG. 5 is a flowchart of a preferred M2M application service method according to an embodiment of the present invention;

FIG. 6 is a structural block diagram of an M2M application service device according to an embodiment of the present invention.

detailed description

The invention will be described in detail below with reference to the drawings in conjunction with the embodiments. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.

In the following embodiments, the M2M terminal may be a mobile terminal (for example, a mobile phone, a tablet, etc.), or may be another type of terminal as long as it can access the Internet of Things. The operating system running on the terminal is also various types of systems, for example, the currently widely used Android system, or the Windows operating system, the iOS system, etc., but is not limited thereto. Devices can be servers, various types of gateways, or other types of devices.

The terminal or device may include a storage medium, and program units stored in the storage medium may be used to perform the methods described in the following embodiments. The terminal or device may also include a processor that is configurable to execute the program elements described above. It is to be expected that the methods or apparatus described below can be implemented by program units.

In the following embodiments, other Internet of Things domains (or other M2M environments) described below may be private Internet of Things that provide services to a single institution, other public Internet of Things, community Internet of Things. At the same time, it is also possible that the Internet of Things has a large number of applications in different industries, including intelligent agriculture, smart grid, intelligent transportation, intelligent logistics, smart medical, smart home and so on.

In the following embodiments, a service-oriented architecture reference model is employed. In the service-oriented architecture reference model, a service is a mechanism that grants access to one or more functions or methods, accessing the specified interface and maintaining the service description. Constraints are consistent with the strategy.

According to an embodiment of the present invention, an M2M application service system is provided. The layered model of the M2M network mainly includes an application layer, a general service layer, and an underlying network service layer, and the corresponding functional architecture mainly includes an application entity, a general service entity, and an underlying network service entity.

2 is an architectural diagram of an M2M application service system according to an embodiment of the present invention. As shown in FIG. 2, the M2M application service system includes: an application entity 1, a general service entity 2, and an underlying network service entity 3. The application entity 1 is configured to provide end-to-end application logic; the universal service entity 2 is configured to provide a general service function of the M2M environment, the universal service entity 2 includes at least one service module, and each service module includes one or more Service; the underlying network service entity 3, set to serve the generic service entity 2.

Through the embodiment of the invention, a service-oriented architecture M2M application service system is realized, which is more conducive to the unified management of the IoT terminals and the provision of M2M services by the public Internet of Things.

In an embodiment of the present invention, the application entity 1 provides end-to-end application logic, and may be located in an M2M terminal, an M2M gateway, and an M2M server. The universal service entity 2 provides a general service function of the M2M environment and can be located in the M2M terminal, the M2M gateway, and the M2M server. The underlying network service entity 3 provides services for the general service entity. Preferably, the constrained M2M terminal does not include a generic service entity.

In the embodiment of the present invention, the M2M application service system based on the service oriented architecture can be applied to the infrastructure domain of the public Internet of Things service provider. The universal service entity 2 can be considered as a set of service modules, and the service module is an entity that includes one or more services, and the universal service entity provides a service execution environment for the M2M application. When the general service entity is on the network service side, its M2M server is equivalent to the M2M service publishing platform. In particular, in a cloud computing or network function virtualization (NFV) environment, a generic service entity can be deployed on a virtual machine or as a virtual network function; the generic service entity 2 provides an M2M platform and service functions.

In an embodiment of the present invention, the service module of the universal service entity 2 may include: a service exposure module 20 configured to expose a service to an application entity; and a network service utilization module 22 configured to use the underlying network service entity 3 Service; remote service exposure module 24, set to connect externally from other M2M environments service. Preferably, other M2M environments include, but are not limited to, a private Internet of Things, a community Internet of Things, an industry Internet of Things, and the like.

3 is a structural block diagram of a preferred general service entity according to an embodiment of the present invention. As shown in FIG. 3, the service module of the universal service entity 2 further includes at least one of the following: a service service module (also referred to as a orchestration module) 26, which is set. To provide one of the following services: a service service, a terminal management service, a data exchange service, a data storage service, a group management service, a location service; a terminal and/or application loading module 28, configured to provide terminal and/or application loading services; The accounting module 210 is configured to provide one of the following services: a billing service, a billing service, and an infrastructure module 212 configured to provide one of the following services: an authorization service, a security service, an authentication service, and an order management module 214 configured to A subscription management service is provided; a message brokering module (also referred to as an adaptation module) 216 is provided to provide services for adapting the services of the underlying network service entity and/or other M2M environments.

Preferably, the service module in the universal service entity 2 can implement communication through a WEB service mode, and the specific technology can adopt a service bus.

According to an embodiment of the present invention, an M2M application service method is also provided.

FIG. 4 is a flowchart of an M2M application service method according to an embodiment of the present invention. As shown in FIG. 4, the method includes steps S402 to S404.

Step S402, responding to the M2M service of the general service entity consumed by the application entity.

Preferably, the foregoing M2M service includes, but is not limited to, at least one of the following: a service service, a terminal management service, a data exchange service, a data storage service, a group management service, and a location service.

Step S404, invoking a service of the underlying network service entity and/or a service of another M2M environment according to the M2M service.

Through the embodiment of the present invention, a service-oriented architecture M2M application service method is implemented, which is more conducive to the unified management of the IoT terminals and the provision of M2M services by the public Internet of Things.

In an embodiment of the present invention, the foregoing M2M service further includes at least one of the following: a terminal and/or an application loading service, a subscription management service, an authorization service, a security service, an authentication service, a billing service, and a billing service.

In a preferred embodiment of the embodiment of the present invention, the information used by the M2M service includes at least one of the following:

(1) an M2M request identifier, which is used to identify the message request information;

(2) The M2M request initiator is used to identify the originating object;

(3) M2M terminal identifier, which is used to identify the M2M terminal;

(4) M2M service identifier for identifying the M2M service;

(5) M2M external identifier, used by the M2M service provider to identify the external network domain, including the underlying network or other domain M2M service providers;

(6) an application identifier for identifying an application entity; a service subscription identifier for an M2M service provider binding application, an M2M terminal, a service, and a subscription relationship between the general service entities;

(7) Service capability identifiers used to identify service capabilities or operations;

(8) an event identifier for identifying event information;

(9) management object information, including management data and its general structure can map an external management data model;

(10) Management command information, including a method indicating an execution management process or an execution command or a remote procedure call;

(11) transmitting information, including execution content indicating initialization and management data transfer; group information, including group resource content;

(12) location policy information, including a method for acquiring and managing geographic location information of the M2M node;

(13) M2M node information, including application entities and general service entity information running on the node;

(14) scheduling information, including a scheduling time period and/or a scheduling repetition period;

(15) Remote universal service entity information, representing a remote universal service entity registered with the local general service entity;

(16) terminal information, representing shared content of the terminal; terminal capability information, for managing the capabilities of the terminal;

(17) Event log information, used to record the event log of the terminal.

Preferably, the above service service may be a service arranged according to a process.

In an embodiment of the present invention, the foregoing service service includes at least one of the following service capabilities or operations: accepting an application request, acquiring a service capability, and acquiring a service service.

Preferably, the above-mentioned service capability or operation accepting the application request needs to input at least one of the following information: an M2M request identifier, an initiator, an application identifier, a service subscription identifier, an M2M external identifier, and the like.

Preferably, the service capability or operation accepting the application request returns at least one of the following: whether the initiator authenticates, whether the initiator has a service subscription, whether the initiator has an authorized service capability or operation, and the like.

Preferably, the foregoing service capability or operation for acquiring the service capability needs to input at least one of the following information: an operation request or the like. Further, the service capability or operation for acquiring the service capability returns at least one of the following: a service capability identifier, a service capability cannot be determined from the operation request, and the like.

Preferably, the foregoing service capability or operation for acquiring a service service needs to input at least one of the following information: a service capability identifier and the like. Further, the service capability or operation of acquiring the service service returns at least one of the following information: an M2M service identifier, the M2M service does not exist in the service capability, and the like.

In an embodiment of the present invention, the data exchange service is configured to provide an application with data exchange under a service subscription relationship, where the data exchange service provides at least one service capability or operation: a release based exchange Data, subscription-based exchange data, and exchange data based on request response.

Preferably, the above-mentioned exchange mode based exchange mode supports synchronous or asynchronous operations. Subscription-based exchange data supports asynchronous operations, including subscribing to all or subscribing to topics. The exchange data based on the request response mode supports synchronous or asynchronous operations.

In an embodiment of the present invention, the terminal management service is used to provide various terminal management services, including at least one of the following: terminal configuration, terminal diagnosis and/or monitoring, terminal firmware management, and terminal topology management.

Preferably, the service capability or operation of the terminal management service needs to input at least one of the following: an initiator, an M2M terminal identifier, an M2M service identifier, a service capability identifier, an M2M external identifier, management object information, management command information, Group information, scheduling information, terminal information, terminal capability information, and the like.

Preferably, the service capability or operation of the terminal management service returns at least one of the following: processing terminal management (by authorization and conforming to the subscription relationship), not handling terminal management (no subscription relationship or failure to pass authorization or billing).

In an embodiment of the embodiments of the present invention, the subscription management service is used to maintain a subscription relationship and/or a role.

Preferably, the above subscription management service provides at least one of the following service capabilities or operations: verifying the service service, obtaining the authorization, and the like.

Preferably, the service capability or operation of the verification service service requires input of at least one of the following information: an M2M service identifier, a service subscription identifier, and the like.

Preferably, the service capability or operation of the verification service service returns at least one of the following information: whether the service exists, whether the service has a subscription relationship, or the like.

Preferably, obtaining the authorized service capability or operation requires inputting at least one of the following information: an M2M service identifier, a service subscription identifier, a service capability identifier, and the like.

Preferably, the acquired service capability or operation returns at least one of the following: a role policy, a presence of a role, and the like.

In an embodiment of the embodiments of the present invention, the application and/or terminal loading service includes at least one of the following service capabilities or operations: maintaining a terminal template, maintaining a terminal and/or an application's credentials, terminal and/or application discovery, policy, Terminal and / or application registration, etc.

Preferably, the above application and/or terminal loading service maintains a mapping relationship between the M2M external identifier and/or the M2M terminal identifier and the underlying network identifier or other domain servant identifier.

Preferably, the service capability or operation of the application and/or the terminal loading service needs to input at least one of the following information: an M2M request identifier, an initiator, an M2M terminal identifier, an M2M service identifier, an M2M external identifier, an application identifier. , service subscription identifier, management object information, group information, location policy information, M2M node information, remote universal service entity information, terminal information, and the like.

Preferably, the service capability or operation of the application and/or the terminal loading service returns at least one of the following: whether the terminal and/or the application are loaded, whether the terminal and/or the application are registered, the credentials of the terminal and/or the application, and the underlying network identifier. , other domain service provider identifiers, etc.

In an embodiment of the present invention, the authorization service is used to provide a service capability or operation that can be used to authorize the requester, including at least one of the following service capabilities or operations: authorization service capability or operation, and the like.

Preferably, the service capability or operation of the authorization service requires input of at least one of the following: an initiator, an application identifier, a service subscription identifier.

Preferably, the service capability or operation of the authorization service returns at least one of the following: whether the initiator is authenticated, whether the service subscription relationship exists, whether the service capability is authorized, or the like.

In an embodiment of the embodiments of the present invention, the billing service includes at least one of the following service capabilities or operations: initiating event collection, stopping event collection, collecting statistics, and the like.

Preferably, the service capability or operation of the billing service requires input of at least one of the following: an M2M request identifier, an event identifier, an application identifier, a service subscription identifier, a service result, event log information.

Preferably, the service capability or operation of the accounting service returns at least one of the following: whether to start event collection, whether to stop event collection, event collection results, statistical collection results, and the like.

In an embodiment of the present invention, the terminal management service is used to provide services managed by the terminal, including at least one of the following: terminal configuration, terminal diagnosis and/or monitoring, terminal firmware management, and terminal topology management.

The above method of the embodiment of the present invention will be described below in conjunction with a preferred embodiment of the present invention.

FIG. 5 is a flowchart of a preferred M2M application service method according to an embodiment of the present invention. As shown in FIG. 5, the method includes steps S502 to S5.

Step S502: The application entity sends an M2M application service message to the universal service entity, and the M2M service required to be consumed includes at least one of the following: a service service, a terminal management service, a data exchange service, a data storage service, a group management service, and a location service. Contains one of the following parameters: M2M request identifier, initiator, M2M external identifier, application identifier, service subscription identifier, and so on. The generic service entity accepts the application request.

Step S504, the service service of the general service entity acquires the service capability.

Step S506, the service service of the universal service entity sends a verification service service message to the subscription service, including one of the following parameters: a service identifier, a service subscription identifier, and the like.

Step S508, the service service of the universal service entity sends an authorization service capability request message to the authorization service, and includes one of the following parameters: a service identifier, a service subscription identifier, and the like.

Step S510, the authorization service of the universal service entity sends an acquisition authorization message to the subscription service, including one of the following parameters: a service capability identifier, a service subscription identifier, etc.; and obtains corresponding authorization information, and then returns the authorized service capability to the service service. .

Step S512, the service service of the universal service entity invokes the application and the terminal loading service, and includes one of the following parameters: an M2M request identifier, an initiator, an M2M terminal identifier, an M2M external identifier, an M2M service identifier, an application identifier, and a service. Order identifier, management object information, group information, location policy information, M2M node information, remote general service entity information, terminal information, etc., and return other domain service provider identifiers or underlying network identifiers, policies, and the like.

Step S514, the service service of the universal service entity performs protocol adaptation.

Step S516, the service service of the universal service entity sends a startup event collection message to the accounting service, including one of the following parameters: an M2M request identifier, an event identifier, a service subscription identifier, an application identifier, and the like. The accounting service returns a launch event collection response.

Step S518, the service service of the universal service entity sends the service packet adapted by the remote protocol to the other Internet of Things domain or the underlying network. Other IoT domains or underlying networks return processing results.

Step S520: The service service of the universal service entity sends a stop event collection message to the billing service, including one of the following parameters: an M2M request identifier, an event identifier, a service subscription identifier, an application identifier, a service result, and the like. The accounting service returns a stop event collection response and accounting information.

Subsequent steps: The service service of the generic service entity returns the processing result of the M2M application service to the application entity.

According to an embodiment of the present invention, an M2M application service device is provided.

FIG. 6 is a structural block diagram of an M2M application service device according to an embodiment of the present invention. As shown in FIG. 6, the device includes a response module 602 and a service module 604. The response module 602 is configured to respond to the M2M service of the universal service entity consumed by the application entity, where the M2M service includes at least one of the following: a service service, a terminal management service, a data exchange service, a data storage service, a group management service, and a location. Service; service module 604, configured to invoke services of the underlying network service entity and/or services of other M2M environments in accordance with the M2M service.

Through the embodiment of the invention, an M2M application service device oriented to a service architecture is realized, which is more conducive to the unified management of the IoT terminals and the provision of M2M services by the public Internet of Things.

The device may implement the foregoing method in the embodiment of the present invention, and the specific process is not described herein.

From the above description, it can be seen that the present invention achieves the following technical effects: the service-oriented architecture-based M2M application service method, device and system are more conducive to unified management and provision of M2M services for terminals of different Internet of Things.

It will be apparent to those skilled in the art that the various modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. Perform the steps shown or described, or separate them into individual integrated circuit modules, or Multiple of these modules or steps are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.

The above description is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Industrial applicability

As described above, an M2M application service method, apparatus, and system provided by the embodiments of the present invention have the following beneficial effects: facilitating unified management and providing M2M services for terminals of different Internet of Things.

Claims

An M2M application service system, comprising:

Application entity, set to provide end-to-end application logic;

a generic service entity, configured to provide a generic service function of an M2M environment, wherein the universal service entity includes at least one service module, each of the service modules including one or more services;

An underlying network service entity, configured to provide services to the generic service entity.
The system of claim 1 wherein said service module comprises:

a service exposure module configured to expose a service to the application entity;

a network service utilization module configured to use a service of the underlying network service entity;

The remote service exposes the module and is set up to connect to external services from other M2M environments.
The system of claim 1 or 2, wherein the service module comprises at least one of:

A service service module or an orchestration module, configured to provide one of the following services: a service service, a terminal management service, a data exchange service, a data storage service, a group management service, and a location service;

a terminal and/or application loading module configured to provide terminal and/or application loading services;

A billing module, set to provide one of the following services: billing service, billing service;

The infrastructure module is set to provide one of the following services: authorization service, security service, and authentication service;

An order management module configured to provide subscription management services;

The message brokering module or the adapting module is configured to provide a protocol to adapt the services of the underlying network service entity and/or services of other M2M environments.
An M2M application service method, including:

Responding to the M2M service of the general service entity consumed by the application entity, where the M2M service includes at least one of the following: a service service, a terminal management service, a data exchange service, a data storage service, a group management service, and a location service;

The services of the underlying network service entity and/or services of other M2M environments are invoked according to the M2M service.
The method of claim 4, wherein the M2M service further comprises at least one of: terminal and/or application loading service, subscription management service, authorization service, security service, authentication service, accounting service, charging service .
The method according to claim 4 or 5, wherein the information used by the M2M service comprises at least one of the following:

An M2M request identifier, which is used to identify the message request information;

The M2M request initiator is used to identify the originating object;

M2M terminal identifier, used to identify the M2M terminal;

M2M service identifier for identifying the M2M service;

M2M external identifier for the M2M service provider to identify the external network domain, including the underlying network or other domain M2M service provider;

An application identifier that identifies the application entity;

Service subscription identifier for the subscription relationship between the M2M service provider binding application, the M2M terminal, the service, and the general service entity;

Service capability identifier, used to identify service capabilities or operations;

An event identifier for identifying event information;

Management object information, including management data and its general structure can map external management data model;

Management command information, including methods for performing a management process or executing a command or a remote procedure call;

Transmitting information, including execution content indicating initialization and management of data transfer;

Group information, including group resource content;

Location policy information, including a method for obtaining and managing geographic location information of an M2M node;

M2M node information, including application entities and general service entity information running on the node;

Scheduling arrangement information, including scheduling time period and/or scheduling repetition period;

The remote universal service entity information represents a remote universal service entity registered in the local universal service entity;

Terminal information, representing the shared content of the terminal;

Terminal capability information, used to manage the capabilities of the terminal;

Event log information, used to record the event log of the terminal.
The method of claim 4, wherein the business service comprises at least one of a service capability or an operation of accepting an application request, acquiring a service capability, and obtaining a business service.
The method according to claim 4, wherein the terminal management service is used to provide terminal managed services, including at least one of: terminal configuration, terminal diagnosis and/or monitoring, terminal firmware management, terminal topology management.
The method according to claim 4, wherein said data exchange service is configured to provide an application with data exchange under a service subscription relationship, wherein

The data exchange service provides at least one of the following service capabilities or operations: exchange-based exchange data, subscription-based exchange data, and request response-based exchange data.
The method of claim 5, wherein the subscription management service is for maintaining a subscription relationship and/or role, wherein

The subscription management service provides at least one of the following service capabilities or operations: verifying the service service, and obtaining the authorization.
The method of claim 5 wherein said application and/or terminal loading service comprises at least one of the following service capabilities or operations:

Maintenance of terminal templates, maintenance terminals and/or application credentials, terminal and/or application discovery, policies, terminals and/or application registration.
The method of claim 5, wherein the authorization service is for providing a service capability or operation that is authorized to be used by the requester, including at least one of the following service capabilities or operations: authorizing the service capability or operation.
The method of claim 5 wherein said billing service comprises at least one of the following service capabilities or operations: initiating event collection, stopping event collection, and collecting statistics.
An M2M application service device, comprising:

The response module is configured to respond to the M2M service of the universal service entity consumed by the application entity, where the M2M service includes at least one of the following: a service service, a terminal management service, a data exchange service, a data storage service, a group management service, and a location service. ;

The service module is configured to invoke a service of the underlying network service entity and/or a service of another M2M environment according to the M2M service.