CN102790781B - The M2M system of a kind of middleware, band sector application middleware and application process thereof - Google Patents
The M2M system of a kind of middleware, band sector application middleware and application process thereof Download PDFInfo
- Publication number
- CN102790781B CN102790781B CN201110127550.6A CN201110127550A CN102790781B CN 102790781 B CN102790781 B CN 102790781B CN 201110127550 A CN201110127550 A CN 201110127550A CN 102790781 B CN102790781 B CN 102790781B
- Authority
- CN
- China
- Prior art keywords
- middleware
- platform
- sector application
- message
- protocol
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Landscapes
- Computer And Data Communications (AREA)
Abstract
The invention discloses a kind of middleware, the M2M system of band sector application middleware and application process thereof, wherein, middleware is the interactive unit between sector application and M2M platform, for controlling interacting message between sector application and M2M platform and protocol adaptation.M2M platform accesses sector application by middleware.Adopt the present invention, by middleware newly-increased between M2M platform and sector application, for the sector application in M2M system provides unified interface and application protocol adaptation.
Description
Technical field
The present invention relates to M2M technology, particularly relate to a kind of middleware, the M2M system of band sector application middleware and application process thereof.
Background technology
The concept of Internet of Things proposed in 1999.At that time based on the Internet, radio-frequency (RF) identification (RFID, Radio Frequency Identification) technology, EPC standard, on the basis of computer internet, utilize RFID technique, wireless data communication technology etc., construct the Internet in kind that realizes global Item Information Real-Time Sharing---Internet of things, is called for short Internet of Things.M2M system is the main forms of current Internet of Things present stage, and M2M is the abbreviation of Machine-to-Machine, refers to the wireless communications industry service type towards intelligent terminal machine, comprises machine-machine, machine-people, people-machine three kinds of application modes.And a typical M2M system is made up of the link such as transducer (or watch-dog), M2M terminal, cellular mobile communication networks, terminal management platform and terminal software upgrading server, OSS, sector application system.Internet-of-things terminal connects Sensor Network network layers and transport network layer in Internet of Things, realizes image data and the equipment to network layer transmission data.Which is responsible the several functions such as data acquisition, preliminary treatment, encryption, transmission.Wherein, described EPC is for providing the unique identification to physical world object, and it is identified by computer network and accesses single body, as using IP address to identify in the Internet, organizing with communicating.The final goal of EPC system is each single product foundation whole world, open identification standard.
Internet of Things applies the application layer be in Internet of Things, embody the effect of Internet of Things and be worth place, but in prior art, M2M platform in M2M system be that interface (hereinafter referred to as A interface) by sector application is connected between sector application, as shown in Figure 1, the M2M platform formulated due to different operators and the interface (hereinafter referred to as A interface) of sector application differ widely, even if the sector application of application vendor same, also to affix one's name at the M2M platform lower of different operators, therefore, application vendor needs the A interface protocol understanding each operator one by one, and realize the same sector application under different operators M2M platform for different A interface protocol.There is following limitation and deficiency in this M2M system architecture implementation of prior art:
Even 1 same sector application, the M2M platform development industry applications out for different operators are different, and incompatible each other, but are but the same sector applications of identical function at application.
2, the sector application that A interface relates to logs in authentication, endpoint registration, log in, alarm, reporting of the events such as statistics, message encryption/deciphering, terminal information inquiry, the flow processs such as message content parsing, little with concrete application layer business relations, it all application is all same processing procedure, sector application is mutual except what realize that concrete business also will consider with M2M platform, and the change of A interface can have influence on the business of sector application, need the realization of application layer should be separated with A Interface realization, not by the impact of the change of A interface, but these needs cannot be realized at present.
3, manufacturer is except debugging concrete application layer business, also to understand the A interface protocol that each operator formulates one by one, and and the uniting and adjustment of M2M platform, because A Interface Flowchart is various, message assembling/resolve complicated, and be unfavorable for directly carrying out application layer business development, need to do once to encapsulate, but these needs cannot be realized at present.
4, cannot be linked into the M2M platform of other operator for the sector application of a certain operator A Interface realization, a sector application can not access the M2M platform of multiple operator simultaneously.If the same sector application of the direct supplier (SP) of mobile internet service content application service is wanted to provide service to the user of multiple operator, need to realize respectively the version under different operators M2M platform, then dispose respectively.
Summary of the invention
In view of this, main purpose of the present invention is the M2M system and the application process thereof that provide a kind of middleware, band sector application middleware, by middleware newly-increased between M2M platform and sector application, for the sector application in M2M system provides unified interface and application protocol adaptation.
For achieving the above object, technical scheme of the present invention is achieved in that
A kind of middleware, described middleware is the interactive unit between sector application and M2M platform, for controlling interacting message between sector application and M2M platform and protocol adaptation.
Wherein, described middleware controls interacting message between sector application and M2M platform and protocol adaptation comprises: receive message that M2M platform sends or receive by service interface the message that sector application sends, be transmitted to described sector application or described M2M platform according to the type of described message after carrying out protocol adaptation.
Wherein, described middleware also for received by service interface sector application send message after, or carry out before protocol adaptation sends to described sector application, described message being converted to the message format of specifying according to the communication mode of middleware and sector application according to the type of described message.
Wherein, described middleware comprises Messenger and protocol adaptor; Wherein,
Described Messenger, for receiving service interface messages by service interface from sector application, after being converted into the service interface messages of specifying message format, sends to described protocol adaptor according to the communication mode of middleware and sector application; After also for the communication mode according to middleware and sector application the service interface messages received being converted to the service interface messages of specifying message format, send to sector application by service interface;
Described protocol adaptor, for carrying out protocol adaptation according to the protocol type in the service interface messages after conversion to the service interface messages after conversion, and send to M2M platform after the service interface messages after described conversion being converted to the interface message meeting interaction protocol between sector application and M2M platform; Also for carrying out protocol adaptation to the message received from M2M platform, and after by described message conversion being service interface messages according to interaction protocol between sector application and M2M platform, send to described Messenger;
Described service interface messages is the message that Messenger is sent by the described sector application that service interface receives; Described interface message is the message of the described M2M platform transmission that protocol adaptor receives.
Wherein, described middleware also comprises controller, for managing the life cycle of described protocol adaptor and described Messenger, dispose descriptor dynamic creation protocol adaptor in middleware initialization or run duration controller by reading, during middleware initialization, controller disposes descriptor dynamic creation Messenger by reading.
Wherein, described service interface is specially the interface supporting to meet interaction protocol intersection between sector application and different agreement M2M platform.
With a M2M system for sector application middleware, this system comprises middleware according to any one of claim 1 to 7 and M2M platform; Wherein, sector application is accessed by described M2M platform by described middleware.
Wherein, in described system, when described middleware specifies multiple deployment descriptor to create multiple protocol adaptor respectively, be linked into the mode of the M2M platform of multiple different agreement by multiple protocol adaptor respectively, support that a sector application is accessed by the M2M platform of multiple different agreement by described middleware simultaneously.
With a M2M system application method for sector application middleware, the method comprises: time mutual between sector application and M2M platform, controls interacting message between described sector application and described M2M platform and protocol adaptation by the middleware between sector application and M2M platform.
Wherein, on down direction, the interacting message between the described sector application of described control and described M2M platform and protocol adaptation comprise:
The service interface that middleware provides is called in sector application, receives service interface messages by service interface from sector application; According to the protocol type in service interface messages, protocol adaptation is carried out to service interface messages, and send to M2M platform after described service interface messages being converted to the interface message meeting interaction protocol between sector application and M2M platform.
Wherein, on up direction, the interacting message between the described sector application of described control and described M2M platform and protocol adaptation comprise:
Middleware receives the message that M2M platform sends, and carries out protocol adaptation to the message received, and after by described message conversion being service interface messages according to interaction protocol between sector application and M2M platform, sends to sector application by service interface.
Middleware of the present invention is the interactive unit between sector application and M2M platform, for controlling interacting message between sector application and M2M platform and protocol adaptation.M2M platform accesses sector application by middleware.Adopt the present invention, by middleware newly-increased between M2M platform and sector application, for the sector application in M2M system provides unified interface and application protocol adaptation, thus solve the problems referred to above of prior art.
Accompanying drawing explanation
Fig. 1 is the structural representation of the M2M system of prior art;
Fig. 2 is the structural representation of a M2M system example of the present invention;
Fig. 3 is the downstream message flow chart of a system application method example of the present invention;
Fig. 4 is the upstream message flow chart of another system application method example of the present invention.
Embodiment
Basic thought of the present invention is: middleware is the interactive unit between sector application and M2M platform, for controlling interacting message between sector application and M2M platform and protocol adaptation.M2M platform accesses sector application by middleware.
A kind of middleware, mainly comprises following content:
Middleware is the interactive unit between sector application and M2M platform, for controlling interacting message between sector application and M2M platform and protocol adaptation.
Further, middleware controls interacting message between sector application and M2M platform and protocol adaptation comprises: receive message that M2M platform sends or receive by service interface the message that sector application sends, send to sector application or M2M platform according to protocol type after carrying out protocol adaptation.Here, protocol type can be operator protocol type.
Concrete, middleware is when the service interface that industry application call middleware provides, service interface messages is received from sector application by service interface, according to the protocol type in service interface messages, protocol adaptation is carried out to service interface messages, and send to M2M platform after described service interface messages being converted to the interface message meeting interaction protocol between sector application and M2M platform.
Concrete, middleware is when middleware receives the message of M2M platform transmission, protocol adaptation is carried out to the message received, and after by described message conversion being service interface messages according to interaction protocol between sector application and M2M platform, sends to sector application by service interface.
Further, middleware controls also comprising of interacting message between sector application and M2M platform and protocol adaptation: receive message that M2M platform sends or the message that sector application sends, send to sector application or M2M platform according to protocol type after carrying out protocol adaptation; To received message that sector application sends by service interface after, or carry out before protocol adaptation sends to sector application, message being converted to the message format of specifying according to the communication mode of middleware and sector application according to protocol type.
Concrete, middleware is at least made up of Messenger and protocol adaptor; Wherein, Messenger, for receiving service interface messages by service interface from sector application, after being converted into the service interface messages of specifying message format, sends to described protocol adaptor according to the communication mode of middleware and sector application.The protocol type that protocol adaptor is used in the service interface messages after according to conversion carries out protocol adaptation to the service interface messages after conversion, and sends to M2M platform after the service interface messages after described conversion being converted to the interface message meeting interaction protocol between sector application and M2M platform.
Concrete, middleware is at least made up of Messenger and protocol adaptor; Wherein, Messenger, after the service interface messages received being converted to the service interface messages of specifying message format, sends to sector application by service interface for the communication mode according to middleware and sector application.Protocol adaptor, for carrying out protocol adaptation to the message received from M2M platform, and after by described message conversion being service interface messages according to interaction protocol between sector application and M2M platform, sends to described Messenger.
Further, middleware also comprises controller, for managing the life cycle of described protocol adaptor and described Messenger, dispose descriptor dynamic creation protocol adaptor in middleware initialization or run duration controller by reading, during middleware initialization, controller disposes descriptor dynamic creation Messenger by reading.
Further, described service interface is specially the interface supporting to meet interaction protocol intersection between sector application and different agreement M2M platform.
With a M2M system for sector application middleware, mainly comprise following content:
This system comprises above-mentioned middleware and M2M platform; Wherein, M2M platform accesses sector application by middleware.
Further, in system, when middleware specifies multiple deployment descriptor to create multiple protocol adaptor respectively, be linked into the mode of the M2M platform of multiple different agreement by multiple protocol adaptor respectively, support that a sector application is accessed by the M2M platform of multiple different agreement by described middleware simultaneously.
Here, middleware that should be newly-increased between the sector application of M2M platform, it is general middleware, encapsulation is implemented to the interface between the M2M platform of different operators and sector application, part irrelevant with the embody rule layer service of sector application in encapsulation A interface, the difference of A interface between M2M platform and sector application between different operators can be masked, support that a sector application accesses the mutual of multiple different operators M2M platform and terminal carrying out service stream and management flow simultaneously, thus can provide unified to the application layer of sector application, simply, easy-to-use service interface.By being supplied to unified, simple, the easy-to-use service interface of sector application, make sector application only need pay close attention to the exploitation of concrete service application aspect, simplify the development cost of M2M system, improve development efficiency and code reusability, the M2M platform of accessible multiple operator after sector application primary development, and when the service interface that middleware provides remains unchanged, even if the A interface between M2M platform and sector application changes, M2M system does not need to make any amendment yet.
Further, operated by terminal management by the interactive operation of middleware between M2M platform and sector application, a few part such as business datum transparent transmission, terminal affair notify, station association data inquiry forms.
Further, by Middleware implementation, this unification provided for the application layer of sector application, simple, easy-to-use service interface.Up direction is that M2M platform is to sector application, down direction is that M2M platform is arrived in sector application, then service interface messages divides upstream message (M2M platform is to the message of sector application) and downstream message (sector application is to the message of M2M platform) two kinds, and therefore the middleware both sides that are connected with sector application be namely client are also service ends.In service interface messages, often kind of message has corresponding response message, execution result must be had according to the operation that actual conditions have, in this case response mode is divided into returning immediately and returns with time delay, immediately under echo plex mode, the other side returns results after receiving message immediately, under time delay echo plex mode, need not return results immediately after the other side receives message, but response message to be returned immediately represent and receive message, message receiver needs to wait for that the time configured just can send a message in addition to message sender after arriving, and request returns result; Some message does not need to return result, as terminal affair reports notice, but will return response message yet and represents and receive message; If middleware sends certain hour after message to sector application, as 5 seconds do not receive response message, then needing resend message, exceed certain sending times, then no longer sending as do not received response message yet 3 times.
Further, based on the A interface that middleware is formulated by each operator, the service interface opened to sector application layer comprises the intersection of A interface support operation between all operators.Have part terminal operation in service interface, event notice, station association data inquiry etc. operates in the A interface protocol of some operator formulation and may not support, needs M2M platform in addition to the support of middleware open interface, or is designated the operation do not supported.Message in service interface must comprise operator protocol type, and for distinguishing the M2M platform mutual with sector application, when sector application sends message toward terminal, middleware also needs to decide to be issued to which M2M platform by operator protocol type.
Further, middleware with dynamic link library, stand-alone utility, the modes such as jar bag are issued, but be not limited only to this, with connection-oriented transmission control protocol (TCP), the modes such as Internet service (Web Service) expose service interface to sector application.Under different communication mode, message format can be different, but it is the same for comprising information; For the ease of expanding internal transmission of messages, the message format of XML format also all can be adopted.Sector application side direction middleware provides deployment descriptor, and to realize sector application access M2M platform, middleware provides service for sector application layer.Dispose descriptor and comprise operator protocol type, M2M platform IP address/port, sector application IP address/port, the information that sector application access M2M platform needs.Dispose the access that descriptor corresponds to a M2M platform, provide multiple deployment descriptor then to achieve a sector application and access multiple M2M platform simultaneously for one.
Further, middleware is by a controller, and one or more protocol adaptor, a Messenger forms.
Here, the life cycle management of protocol adaptor and Messenger is responsible for by described controller, when middleware is loaded execution by disposing descriptor dynamic creation protocol adaptor and Messenger; When middleware is stopped operation, give notice so that do front corresponding operating out of service to protocol adaptor.
Here, described protocol adaptor achieves one and specifies the A interface protocol of operator, by from Messenger, the A interface message that converted to equity by the service interface messages of the service interface of Middleware implementation sends to M2M platform; The A interface message received from M2M platform is converted to equity, be transmitted to Messenger by the service interface messages of the service interface of Middleware implementation.
Here, described Messenger is responsible for accessing sector application in many ways, be responsible for the interacting message between middleware and sector application, when receiving the message of sector application, after being converted to the message of XML format, according to operator protocol type in message, message is given the protocol adaptor of specifying operator; When after the message receiving the XML format that protocol adaptor sends, be converted to the message format of specifying according to the communication mode with sector application and be transmitted to sector application.
With a M2M system application method for sector application middleware, the method mainly comprises following content:
Time mutual between sector application and M2M platform, control interacting message between described sector application and described M2M platform and protocol adaptation by the middleware between sector application and M2M platform.
Further, on down direction, the interacting message between described control sector application and M2M platform and protocol adaptation specifically comprise:
The service interface that middleware provides is called in sector application, receives service interface messages by service interface from sector application; According to the protocol type in service interface messages, protocol adaptation is carried out to service interface messages, and send to M2M platform after described service interface messages being converted to the interface message meeting interaction protocol between sector application and M2M platform.
Further, on up direction, the interacting message between described control sector application and M2M platform and protocol adaptation specifically comprise:
Middleware receives the message that M2M platform sends, and carries out protocol adaptation to the message received, and after by described message conversion being service interface messages according to interaction protocol between sector application and M2M platform, sends to sector application by service interface.
Further, described service interface is specially the interface supporting to meet interaction protocol intersection between sector application and different agreement M2M platform.
Further, when the controller of the middleware life cycle to protocol adaptor and Messenger manages, the method also comprises: dispose descriptor dynamic creation protocol adaptor in middleware initialization or run duration controller by reading, during middleware initialization, controller disposes descriptor dynamic creation Messenger by reading.
Further, in the downstream direction, the method also comprises: the service interface that middleware provides is called in sector application, and the service interface messages that the Messenger to middleware sends is downstream message; After downstream message from sector application is converted to the downstream message of XML format by described Messenger, according to the operator protocol type in described message, described message is sent to the protocol adaptor of specifying operator; Protocol adaptor sends to M2M platform after the downstream message of the XML format from described Messenger being converted to the A interface message of equity.
Further, in the upstream direction, the method also comprises: the A interface message received from M2M platform is converted to service interface messages that is reciprocity, XML format and is transmitted to Messenger by the protocol adaptor of middleware; Described service interface messages is upstream message; Messenger, by the upstream message of the XML format from protocol adaptor, is transmitted to sector application after being converted to the message format of specifying according to the communication mode of middleware and sector application.
Be described in further detail below in conjunction with the enforcement of accompanying drawing to technical scheme.
System example a: sector application accesses two M2M platforms (M2M platform 1 and M2M platform 2) by middleware simultaneously.As shown in Figure 2, due to needs access two M2M platforms, therefore, the middleware of system comprises two protocol adaptors (protocol adaptor 1 and protocol adaptor 2), in addition, also comprise in this middleware: a Messenger and a controller.
Concrete, for middleware, it also comprises following content:
The modes such as a, middleware can adopt dynamic link library, stand-alone utility, jar bag are issued, but are not limited only to this.Middleware runs to be needed to dispose descriptor.
B, middleware run duration are connected with sector application with M2M platform, middleware initialization or run duration controller dispose descriptor dynamic creation protocol adaptor by reading, and support the mode dynamic creation by order or control desk and unloading protocol adaptor; But a system can only have a Messenger, and can only create by reading deployment descriptor by controller during middleware initialization.Protocol adaptor is linked into the identity of sector application some access informations that M2M platform needs to specify, and these information are placed in the independent configuration of each protocol adaptor.If specify multiple deployment descriptor to allow controller to create multiple protocol adaptor, so a middleware just can be linked into multiple different M2M platform by multiple protocol adaptor simultaneously.
C, middleware provides unified service interface for sector application, sector application need not consider the difference of different operators A interface, middleware is supported to be connected from multiple different M2M platform, the service interface that middleware is called in sector application to be provided produces service interaction and terminal management from the terminal in different M2M platform, that is, by the service interface that middleware provides, support that a sector application accesses the mutual of the M2M platform of the multiple different operators terminal carrying out service stream corresponding with in M2M platform and management flow simultaneously, middleware is received and is sent to sector application by service interface from after the terminal management stream of different M2M platform and business datum conversion.
D, middleware from bringing into operation automatically and M2M platform connect, if having login authentication in A interface, heartbeat message, then protocol adaptor logs in M2M platform automatically, maintains heartbeat message after login.If message needs to use certain cipher mode in session, as encryptions such as 3DES, RAS, MD5, then complete the operations such as the encryption of message in session and session key update by protocol adaptor.When protocol adaptor is unloaded, if publish message in A interface, then to publish rear ability to M2M platform out of service for protocol adaptor.
Middleware services interface is called in e, sector application, and when service interface messages is downstream message, middleware Transformation Service interface message is that the A interface message of functional equivalence is initiated to call to M2M platform; In like manner, when M2M platform has upstream message (when service interface messages is upstream message), the service interface messages that the A interface message received is converted to functional equivalence is sent to sector application by middleware.Here it is to be noted: in the service interface that middleware is provided, had to definition, but the operation that actual M2M platform is not supported, after sector application is called to middleware initiation, middleware directly returns the operation do not supported; Have definition in the service interface that middleware provides, the event notice that actual M2M platform is not supported, middleware can not send the event notice of this type to sector application.
Method example one: service interface messages is downstream message.As shown in Figure 3, this method example comprises the following steps:
Step 101, sector application send downstream message to Messenger.
Step 102, Messenger return reception response message to sector application.
Step 103, Messenger carry out format conversion to downstream message.
The message of XML format after conversion is sent to protocol adaptor by step 104, Messenger.
The message conversion of XML format is A interface message by step 105, protocol adaptor.
A interface message after conversion is sent to M2M platform by step 106, protocol adaptor.
Step 107, M2M platform return reception response message to protocol adaptor.
Step 108, be assembled into T interface message at M2M platform.
Here, T interface herein refers to the interface of M2M platform and M2M terminal communication, does not repeat.
T interface message is sent to terminal by step 109, M2M platform.
Step 110, terminal return and receive response message to M2M platform.
Concrete, if downstream message is terminal parameter configuration messages, then performs flow process based on M2M systematic difference and comprise following content:
The service interface initiating terminal parameter configuration that a1, sector application provide to middleware for it is called.
After the Messenger of b1, middleware receives terminal parameter configuration messages, the reception response message that one receives terminal parameter configuration messages is responded immediately to sector application, then reception response message is converted to XML format, is distributed to the protocol adaptor of corresponding operator protocol type according to operator protocol type in message.
The message conversion received is the A interface message of functional equivalence and initiates to call to M2M platform by the protocol adaptor of c1, middleware.
The response receiving message responded by d1, M2M platform to protocol adaptor, issue terminal parameter configuration-direct to terminal.
E1, terminal immediately execution parameter configure backward M2M platform and return execution result.
F1, M2M platform is to protocol adaptor transmitting terminal parameter configuration result notification message.
G1, protocol adaptor are responded immediately after receiving message and are received response message, then receipt message format conversion are the middleware services interface message of XML format and send to Messenger.
After XML format message being changed again with the communication modes of sector application, sector application is sent to after h1, Messenger receive message.
I1, sector application are responded after receiving message and are received response, then do the process of service layer by the message received.
Method example two: service interface messages is upstream message.As shown in Figure 4, this method example comprises the following steps:
Step 201, terminal send T interface message to M2M platform.
Step 202, M2M platform return response message to terminal.
Step 203, in M2M platform assembling A interface message.
A interface message is sent to protocol adaptor by step 204, M2M platform.
Step 205, protocol adaptor return response message to M2M platform.
Step 206, carry out messaging protocol conversion at protocol adaptor.
The message of XML format after format conversion is sent to Messenger by step 207, protocol adaptor.
Step 208, Messenger return and receive response message to protocol adaptor.
Step 209, carry out message format conversion at Messenger.
Upstream message after conversion is sent to sector application by step 210, Messenger.
Step 211, sector application return response message to Messenger.
Concrete, if upstream message is terminal affair reporting message, then performs flow process based on M2M systematic difference and comprise following content:
A2, terminal are to M2M platform initiating terminal reporting events.
By A interface, reporting events is sent to the protocol adaptor of middleware after b2, M2M platform receives terminal affair reporting message.
The terminal affair reporting message received is converted to the reporting events message of the XML format of equity in middleware services interface by c2, protocol adaptor, is then transmitted to the Messenger of middleware.
D2, Messenger send to sector application after being converted to specified format according to the communication mode with sector application.
After e2, sector application receive terminal affair reporting message, to middleware transmission and reception response, do the process in service layer.
Here it is to be noted: terminal herein all refers to M2M terminal, and sector application all refers to M2M sector application, does not repeat.
The above, be only preferred embodiment of the present invention, be not intended to limit protection scope of the present invention.
Claims (10)
1. a middleware, is characterized in that, described middleware is the interactive unit between sector application and M2M platform, for controlling interacting message between sector application and M2M platform and protocol adaptation; Described middleware is at least made up of Messenger and protocol adaptor, described middleware also comprises controller, for managing the life cycle of described protocol adaptor and described Messenger, dispose descriptor dynamic creation protocol adaptor in middleware initialization or run duration controller by reading, during middleware initialization, controller disposes descriptor dynamic creation Messenger by reading.
2. middleware according to claim 1, it is characterized in that, described middleware controls interacting message between sector application and M2M platform and protocol adaptation comprises: receive message that M2M platform sends or receive by service interface the message that sector application sends, be transmitted to described sector application or described M2M platform according to the type of described message after carrying out protocol adaptation.
3. middleware according to claim 2, it is characterized in that, described middleware also for received by service interface sector application send message after, or carry out before protocol adaptation sends to described sector application, described message being converted to the message format of specifying according to the communication mode of middleware and sector application according to the type of described message.
4. middleware according to claim 3, is characterized in that, described middleware comprises Messenger and protocol adaptor; Wherein,
Described Messenger, for receiving service interface messages by service interface from sector application, after being converted into the service interface messages of specifying message format, sends to described protocol adaptor according to the communication mode of middleware and sector application; After also for the communication mode according to middleware and sector application the service interface messages received being converted to the service interface messages of specifying message format, send to sector application by service interface;
Described protocol adaptor, for carrying out protocol adaptation according to the protocol type in the service interface messages after conversion to the service interface messages after conversion, and send to M2M platform after the service interface messages after described conversion being converted to the interface message meeting interaction protocol between sector application and M2M platform; Also for carrying out protocol adaptation to the message received from M2M platform, and after by described message conversion being service interface messages according to interaction protocol between sector application and M2M platform, send to described Messenger;
Described service interface messages is the message that Messenger is sent by the described sector application that service interface receives; Described interface message is the message of the described M2M platform transmission that protocol adaptor receives.
5. the middleware according to any one of claim 2 to 4, is characterized in that, described service interface is specially the interface supporting to meet interaction protocol intersection between sector application and different agreement M2M platform.
6. the M2M system with sector application middleware, is characterized in that, this system comprises middleware according to any one of claim 1 to 5 and M2M platform; Wherein, sector application is accessed by described M2M platform by described middleware.
7. system according to claim 6, it is characterized in that, in described system, when described middleware specifies multiple deployment descriptor to create multiple protocol adaptor respectively, be linked into the mode of the M2M platform of multiple different agreement by multiple protocol adaptor respectively, support that a sector application is accessed by the M2M platform of multiple different agreement by described middleware simultaneously.
8. the M2M system application method with sector application middleware, it is characterized in that, the method comprises: time mutual between sector application and M2M platform, controls interacting message between described sector application and described M2M platform and protocol adaptation by the middleware between sector application and M2M platform; Described middleware is at least made up of Messenger and protocol adaptor, described middleware also comprises controller, for managing the life cycle of described protocol adaptor and described Messenger, dispose descriptor dynamic creation protocol adaptor in middleware initialization or run duration controller by reading, during middleware initialization, controller disposes descriptor dynamic creation Messenger by reading.
9. method according to claim 8, is characterized in that, on down direction, the interacting message between the described sector application of described control and described M2M platform and protocol adaptation comprise:
The service interface that middleware provides is called in sector application, receives service interface messages by service interface from sector application; According to the protocol type in service interface messages, protocol adaptation is carried out to service interface messages, and send to M2M platform after described service interface messages being converted to the interface message meeting interaction protocol between sector application and M2M platform.
10. method according to claim 8, is characterized in that, on up direction, the interacting message between the described sector application of described control and described M2M platform and protocol adaptation comprise:
Middleware receives the message that M2M platform sends, and carries out protocol adaptation to the message received, and after by described message conversion being service interface messages according to interaction protocol between sector application and M2M platform, sends to sector application by service interface.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110127550.6A CN102790781B (en) | 2011-05-17 | 2011-05-17 | The M2M system of a kind of middleware, band sector application middleware and application process thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110127550.6A CN102790781B (en) | 2011-05-17 | 2011-05-17 | The M2M system of a kind of middleware, band sector application middleware and application process thereof |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102790781A CN102790781A (en) | 2012-11-21 |
| CN102790781B true CN102790781B (en) | 2015-10-28 |
Family
ID=47156081
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110127550.6A Active CN102790781B (en) | 2011-05-17 | 2011-05-17 | The M2M system of a kind of middleware, band sector application middleware and application process thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102790781B (en) |
Families Citing this family (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102938770B (en) * | 2012-11-22 | 2015-11-25 | 亚信科技（中国）有限公司 | A kind of method and relevant apparatus, system realizing multi-protocols message unified interface |
| CN103051426B (en) * | 2013-01-22 | 2015-12-23 | 中兴通讯股份有限公司 | The sending method of a kind of data or signaling and device |
| CN103107953B (en) * | 2013-03-11 | 2016-03-02 | 华为技术有限公司 | The communication means of M2M, device and system |
| CN104253763A (en) * | 2013-06-30 | 2014-12-31 | 上海贝尔股份有限公司 | Method for realizing data transmission in gateway equipment of ubiquitous network and gateway equipment using method |
| CN104660547B (en) * | 2013-11-18 | 2019-06-28 | 北京四维图新科技股份有限公司 | A kind of service platform for realizing telecommunication |
| CN104484849B (en) * | 2014-12-26 | 2018-07-27 | 同方威视技术股份有限公司 | Customs tests place system and method |
| CN104917758A (en) * | 2015-05-21 | 2015-09-16 | 浪潮集团有限公司 | Method for realizing conversion of socket protocol connection into other protocol connection |
| CN106899560B (en) * | 2015-12-18 | 2019-12-31 | 美的集团股份有限公司 | Method for automatic intercommunication of different protocols of Internet of things and Internet of things terminal |
| CN105915500A (en) * | 2015-12-22 | 2016-08-31 | 美的集团股份有限公司 | Method, protocol conversion service end and Internet of things terminal for conversion of different Internet of things protocols |
| CN106534187A (en) * | 2016-12-13 | 2017-03-22 | 广东沅朋网络科技有限公司 | Unified management method and system for multi-type wireless data transmission terminal |
| CN109688047B (en) * | 2018-12-07 | 2021-07-23 | 中国建设银行股份有限公司 | Message adaptation method, device and storage medium based on XML |
| CN112311567B (en) * | 2019-07-26 | 2022-04-05 | 华为技术有限公司 | Communication method and device |
| CN110704207B (en) * | 2019-09-11 | 2021-04-27 | 口碑(上海)信息技术有限公司 | Data processing method and device of business application middleware and storage medium |
| CN115834735A (en) * | 2021-09-17 | 2023-03-21 | 青岛海尔科技有限公司 | Communication method, device, medium and product between cloud and Internet of things equipment |
| CN115665269A (en) * | 2022-10-18 | 2023-01-31 | 哈尔滨工程大学 | Communication method between distributed heterogeneous languages based on TCP communication protocol |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101719960A (en) * | 2009-12-01 | 2010-06-02 | 中国电信股份有限公司 | Communication device and cdma terminal |
| CN101895441A (en) * | 2010-07-21 | 2010-11-24 | 中兴通讯股份有限公司 | Service debugging device and method for JAVA application of terminal of Internet of things |
| CN102136933A (en) * | 2010-09-30 | 2011-07-27 | 华为技术有限公司 | Equipment management method, middleware and machine communication platform, equipment and system |
-
2011
- 2011-05-17 CN CN201110127550.6A patent/CN102790781B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101719960A (en) * | 2009-12-01 | 2010-06-02 | 中国电信股份有限公司 | Communication device and cdma terminal |
| CN101895441A (en) * | 2010-07-21 | 2010-11-24 | 中兴通讯股份有限公司 | Service debugging device and method for JAVA application of terminal of Internet of things |
| CN102136933A (en) * | 2010-09-30 | 2011-07-27 | 华为技术有限公司 | Equipment management method, middleware and machine communication platform, equipment and system |
Non-Patent Citations (1)
| Title |
|---|
| 基于ESB的M2M平台通信模块的设计与实现;陈满;《中国优秀硕士学位论文全文数据库（电子期刊） 信息科技辑》;20110315(第3期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102790781A (en) | 2012-11-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102790781B (en) | The M2M system of a kind of middleware, band sector application middleware and application process thereof | |
| KR101964532B1 (en) | Enhanced operations between service layer and management layer in an m2m system by allowing the execution of a plurality of commands on a plurality of devices | |
| CA2495639C (en) | System and method for triggering a provisioning event | |
| WO2018059137A1 (en) | Internet of things terminal access device and method, and computer storage medium | |
| KR101850879B1 (en) | Service enabler function | |
| US20090282130A1 (en) | Resource sharing via close-proximity wireless communication | |
| AU2010244906B2 (en) | Method and System for Provisioning Terminal Parameters and Terminal Management Apparatus | |
| CN102710593B (en) | Method, device and system for publishing message in graph mashup | |
| CN113411215B (en) | Time-sensitive network centralized user configuration method and system based on OPC UA | |
| EP3286936B1 (en) | Device and method for adding a service | |
| US20100217852A1 (en) | Wireless Terminal Device and Server Therefor | |
| EP3163798B1 (en) | Method for processing request messages in wireless communication system, and device for same | |
| CN102647705A (en) | Method and system for mobile terminal parameter configuration | |
| US20170279688A1 (en) | Method, device and system for providing device application software management service in internet of things | |
| CN103370921A (en) | Method for naming sensor devices in a local network, service gateway and remote management server | |
| WO2010127531A1 (en) | Apparatus, web service component and method based on web service | |
| CN111435947A (en) | Electronic message control | |
| CN113254103A (en) | Application function implementation method and device and storage medium | |
| CN101192936A (en) | A method, system and user terminal for establishing access connection | |
| US20100318966A1 (en) | Method for starting sca-based waveform application in component start order | |
| US10750356B2 (en) | Configuration management method, apparatus, and system for terminal in internet of things | |
| GB2580420A (en) | Electronic message adaptation | |
| Li et al. | Efficient oneM2M protocol conversion platform based on NB-IoT access | |
| US8943125B2 (en) | Method of handling step execution result in software and application control management object | |
| US9571583B2 (en) | Method of communicating between two devices |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |