CN104954412B - The firmware management method, apparatus and generic service entity of internet-of-things terminal - Google Patents
The firmware management method, apparatus and generic service entity of internet-of-things terminal Download PDFInfo
- Publication number
- CN104954412B CN104954412B CN201410127491.6A CN201410127491A CN104954412B CN 104954412 B CN104954412 B CN 104954412B CN 201410127491 A CN201410127491 A CN 201410127491A CN 104954412 B CN104954412 B CN 104954412B
- Authority
- CN
- China
- Prior art keywords
- terminal
- message
- firmware management
- internet
- service
- 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
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/50—Service provisioning or reconfiguring
Abstract
The invention discloses a kind of firmware management method, apparatus of internet-of-things terminal and generic service entities, wherein the firmware management method of internet-of-things terminal includes: to receive the terminal firmware management service message from application entity；It is application entity according to terminal firmware management service message, the M2M terminal of M2M terminal and/or other Internet of Things domains to res gentium networked domain carries out firmware management.Through the invention, it solves the problems, such as the unified management of publicly-owned Internet of Things and the M2M terminal of other Internet of Things, realizes the unified management of the M2M terminal to publicly-owned Internet of Things and other Internet of Things.
Description
Technical field
The present invention relates to the communications fields, firmware management method, apparatus in particular to a kind of internet-of-things terminal and logical
Use service entities.
Background technique
Internet of Things is the important component of generation information technology, and English name is: " The Internet of
things".As its name suggests, Internet of Things is exactly the internet that object is connected with object.The ITU interconnection of International Telecommunication Union's publication
Net report, Internet of Things has been done as given a definition: by two dimensional code identify equipment, radio frequency identification (RFID) device, infrared inductor,
The information sensing devices such as global positioning system and laser scanner are connected any article with internet by the agreement of agreement,
Information exchange and communication are carried out, to realize a kind of network of Weigh sensor, positioning, tracking, monitoring and management.
The concept that a M2M is often introduced in Internet of Things can be construed to as people to people (Man to Man), people to machine
Device (Man to Machine), machine to machine (Machine to Machine).In essence, in people and machine, machine
The interaction of device and machine is largely to realize interpersonal information exchange.M2M network is the master of Internet of Things at this stage
The form of expression is wanted, M2M network includes machine to machine communication network, people and machine communication network and machine and people's communication network
Network.The equipment of M2M network mainly includes M2M terminal, M2M gateway, M2M server.
Fig. 1 be according to the schematic diagram of the Internet of things system of the relevant technologies, as shown in Figure 1, Internet of Things can be classified as it is privately owned
Internet of Things (generally faces and provides service inside single institution), and publicly-owned Internet of Things (is based on internet to the public or large-scale user group
Body provides service), community's Internet of Things (providing service to one associated " community " or group of mechanism) etc..Internet of Things at this stage simultaneously
Net has a large amount of application, including reading intelligent agriculture, smart grid, intelligent transportation, Intelligent logistics, intelligent medical, intelligence in different industries
Energy household etc..Specifically, it includes that corresponding profession Internet of Things/M2M is set that these industries, which all respectively dispose its professional Internet of Things,
Standby such as terminal, gateway and server platform device.
Provider of the telecom operators as public Communications service is also as public affairs when it provides Internet of Things/M2M service
There is the role of Internet of Things service provider.It is existing for the terminal of the professional Internet of Things of privately owned Internet of Things, community's Internet of Things and every profession and trade
Telecom operators lacked the implementation unified terminal management of effective technology means as res gentium the Internet services quotient and realized service stage.
Summary of the invention
It can not be to the end of publicly-owned Internet of Things and other Internet of Things domains as res gentium the Internet services quotient for telecom operators
The problem of end unified management, the present invention provides a kind of firmware management method, apparatus of internet-of-things terminal and generic service entity,
At least to solve the above problems.
According to an aspect of the invention, there is provided a kind of firmware management method of internet-of-things terminal, comprising: reception comes from
The terminal firmware management service message of application entity；It is the application entity according to the terminal firmware management service message, it is right
The M2M terminal of res gentium networked domain and/or the M2M terminal of other Internet of Things domains carry out firmware management.
Preferably, the information that the terminal firmware management service message carries includes at least one of: M2M request mark
Symbol, M2M request promoter, M2M terminal identifier, M2M service identifier, M2M foreign identifiers, application identifier, service are ordered
Purchase identifier, M2M end message, M2M group information, schedule information.
Preferably, the message exchange pattern that the terminal firmware management service message uses includes at least one of: hair
Cloth subscribing mode, comprising: the subscription terminal management event message from the application entity is received, according to the application entity
Issue terminal firmware management message carries out firmware management to M2M terminal, returns to terminal management event notice to the application entity
Message；Request response modes, comprising: the terminal firmware management service message request message from the application entity is received, to
The application entity returns to terminal firmware management service message response message；Unidirectional request mode, comprising: receive and answered from described
With the terminal firmware management service message request message of entity；Request and multiple response modes, comprising: receive and come from the application
The terminal firmware management service message request message of entity repeatedly returns to terminal firmware management service message to the application entity
Response message；The request callback mode, comprising: receive the terminal firmware management service message request from the application entity
Message, to the processing result of application entity readjustment terminal firmware management.
Preferably, the corresponding service operations of the terminal firmware management service message or service ability include it is following at least it
One: obtaining terminal firmware Mirror Info, download terminal firmware image, installing terminal firmware image, downloading and installing terminal firmware
Mirror image deletes terminal firmware mirror image.
It preferably, is M2M terminal of the application entity to res gentium networked domain according to terminal firmware management service message
And/or it includes: to be carried according to the terminal firmware management service message that the M2M terminal of other Internet of Things domains, which carries out firmware management,
M2M foreign identifiers and/or M2M terminal identifier, the identifier of Internet of Things domain where obtaining M2M terminal；According to the mark
Symbol is that the application entity carries out firmware management to M2M terminal.
Preferably, the Internet of Things domain includes: the res gentium networked domain, other described Internet of Things domains；According to the mark
Knowing symbol is the application entity to the bottom-layer network that the progress firmware management of M2M terminal includes: according to the res gentium networked domain
Bottom-layer network identifier is that the application entity carries out the M2M terminal in the underlying network service entity of the bottom-layer network
Firmware management；Alternatively, according to other Internet of Things identifiers of other Internet of Things domains, be the application entity to it is described other
M2M terminal in Internet of Things domain carries out firmware management.
It preferably, is M2M of the application entity to res gentium networked domain according to the terminal firmware management service message
It includes: to provide for the terminal firmware management service message that the M2M terminal of terminal and/or other Internet of Things domains, which carries out firmware management,
Service, wherein the services package includes at least one of: authorization service, billed services.
It preferably, is M2M of the application entity to res gentium networked domain according to the terminal firmware management service message
It includes: to carry out to the terminal firmware management service message that the M2M terminal of terminal and/or other Internet of Things domains, which carries out firmware management,
Protocol adaptation；Firmware management is carried out to M2M terminal according to the agreement that adaptation obtains.
Preferably, the agreement includes at least one of: scalable message and presentation agreement XMPP, message queue telemetering
Transmit the client device wide area network management agreement of MQTT, terminal management protocol OMA DM of Open Mobile Alliance, Broadband Forum
The lightweight machine to machine agreement OMA LightweightM2M of series of canonical BBF CWMP, Open Mobile Alliance.
According to another aspect of the present invention, a kind of firmware management device of internet-of-things terminal is provided, comprising: receive mould
Block, for receiving the terminal firmware management service message from application entity；Management module, for according to the terminal firmware pipe
Reason service message is the application entity, the M2M terminal of M2M terminal and/or other Internet of Things domains to res gentium networked domain into
Row firmware management.
Preferably, the information that the terminal firmware management service message carries includes at least one of: M2M request mark
Symbol, M2M request promoter, M2M terminal identifier, M2M service identifier, M2M foreign identifiers, application identifier, service are ordered
Purchase identifier, M2M end message, M2M group information, schedule information.
Preferably, the message exchange pattern that the terminal firmware management service message uses includes at least one of: hair
Cloth subscribing mode, comprising: the subscription terminal management event message from the application entity is received, according to the application entity
Issue terminal firmware management message carries out firmware management to M2M terminal, returns to terminal management event notice to the application entity
Message；Request response modes, comprising: the terminal firmware management service message request message from the application entity is received, to
The application entity returns to terminal firmware management service message response message；Unidirectional request mode, comprising: receive and answered from described
With the terminal firmware management service message request message of entity；Request and multiple response modes, comprising: receive and come from the application
The terminal firmware management service message request message of entity repeatedly returns to terminal firmware management service message to the application entity
Response message；The request callback mode, comprising: receive the terminal firmware management service message request from the application entity
Message, to the processing result of application entity readjustment terminal firmware management.
Preferably, the corresponding service operations of the terminal firmware management service message or service ability include it is following at least it
One: obtaining terminal firmware Mirror Info, download terminal firmware image, installing terminal firmware image, downloading and installing terminal firmware
Mirror image deletes terminal firmware mirror image.
Preferably, the management module includes: acquiring unit, for being carried according to the terminal firmware management service message
M2M foreign identifiers and/or M2M terminal identifier, obtain M2M terminal where Internet of Things domain identifier；Administrative unit is used
According to the identifier be the application entity to M2M terminal carry out firmware management.
Preferably, the Internet of Things domain includes: the res gentium networked domain, other described Internet of Things domains；The management is single
Member is the application entity to the bottom for the bottom-layer network identifier according to the bottom-layer network of the res gentium networked domain
M2M terminal in the underlying network service entity of layer network carries out firmware management；Or for according to other described Internet of Things domains
Other Internet of Things identifiers, be the application entity in other described Internet of Things domains M2M terminal carry out firmware management.
Preferably, the management module is also used to provide service for the terminal firmware management service message, wherein described
Service includes at least one of: authorization service, billed services.
Preferably, the management module includes: adaptation unit, for assisting to the terminal firmware management service message
View adaptation；Administrative unit, the agreement for being obtained according to adaptation carry out firmware management to M2M terminal.
According to another aspect of the present invention, a kind of publicly-owned internet of things equipment is provided, which is characterized in that including any of the above-described
Device.
According to another aspect of the present invention, a kind of generic service entity is provided, is located at res gentium networked domain, including above-mentioned
Any device.
Through the invention, the terminal firmware management service message from application entity is received, is taken according to terminal firmware management
Business message is application entity, and the M2M terminal of M2M terminal and/or other Internet of Things domains to res gentium networked domain carries out firmware pipe
Reason solves the problems, such as the unified management of publicly-owned Internet of Things and the M2M terminal of other Internet of Things, realizes to publicly-owned Internet of Things and its
The unified management of the M2M terminal of his Internet of Things.
Detailed description of the invention
The drawings described herein are used to provide a further understanding of the present invention, constitutes part of this application, this hair
Bright illustrative embodiments and their description are used to explain the present invention, and are not constituted improper limitations of the present invention.In the accompanying drawings:
Fig. 1 is the schematic diagram according to the Internet of things system of the relevant technologies；
Fig. 2 is the flow chart of the firmware management method of internet-of-things terminal according to an embodiment of the present invention；
Fig. 3 is the structural block diagram of the firmware management device of internet-of-things terminal according to an embodiment of the present invention；
Fig. 4 is the schematic diagram according to the preferred M2M network of inventive embodiments；
Fig. 5 is the structural block diagram for preferably servicing exposed component according to the present invention；
Fig. 6 is the flow chart of the firmware management method of the preferred internet-of-things terminal of example according to the present invention；And
Fig. 7 is the flow diagram of the firmware management method of preferred internet-of-things terminal according to embodiments of the present invention.
Specific embodiment
Hereinafter, the present invention will be described in detail with reference to the accompanying drawings and in combination with Examples.It should be noted that not conflicting
In the case of, the features in the embodiments and the embodiments of the present application can be combined with each other.
In the examples below, M2M terminal can be mobile terminal (for example, mobile phone, tablet computer etc.), be also possible to it
The terminal of his type, as long as it has access to Internet of Things.The operating system run in terminal also and is various types
System, for example, the Android system or Windows operating system that are widely used at present, iOS system etc., but not
It is limited to this.Equipment can be server, all kinds of gateways, be also possible to other kinds of equipment.
The terminal or equipment may include storage medium, and the program unit stored in storage medium can be used to execute following
Method described in embodiment.The terminal or equipment can also include processor, which can be used for executing above-mentioned journey
Sequence unit.It is contemplated that method or device discussed below can be realized by program unit.
In the examples below, other following Internet of Things domains, which can be, provides the privately owned of service towards single institution inside
Internet of Things, other publicly-owned Internet of Things, community's Internet of Things.It is also possible to be that Internet of Things in different industries has a large amount of application, wrap
Include reading intelligent agriculture, smart grid, intelligent transportation, Intelligent logistics, intelligent medical, smart home etc..
According to embodiments of the present invention, a kind of firmware management method of internet-of-things terminal is provided.
Fig. 2 is the flow chart of the firmware management method of internet-of-things terminal according to an embodiment of the present invention, as shown in Fig. 2, should
Method includes step S202 to step S204.
Step S202 receives the terminal firmware management service message from application entity.
Step S204 is application entity according to terminal firmware management service message, to the M2M terminal of res gentium networked domain
And/or the M2M terminal of other Internet of Things domains carries out firmware management.
Through the embodiment of the present invention, the unified management of publicly-owned Internet of Things and the M2M terminal of other Internet of Things is solved the problems, such as,
Realize the unified management of the M2M terminal to publicly-owned Internet of Things and other Internet of Things.
In an embodiment of the embodiment of the present invention, it is preferable that the information that terminal firmware management service message carries
Including at least following one or any combination: M2M request identifier, M2M request promoter, M2M terminal identifier, M2M service
Identifier, M2M foreign identifiers, application identifier, service order identifier, M2M end message, M2M group information, scheduling peace
Arrange information.
In an embodiment of the embodiment of the present invention, message exchange pattern that terminal firmware management service message uses
Including but not limited at least one of:
(1) publish-subscribe model, comprising: the subscription terminal management event message from application entity is received, according to application
The issue terminal firmware management message of entity carries out firmware management to M2M terminal, and it is logical to return to terminal management event to application entity
Know message.
(2) response modes are requested, comprising: the terminal firmware management service message request message from application entity is received,
Terminal firmware management service message response message is returned to application entity.
(3) unidirectional request mode, comprising: receive the terminal firmware management service message request message from application entity.
(4) request and multiple response modes, comprising: receive the terminal firmware management service message request from application entity
Message repeatedly returns to terminal firmware management service message response message to application entity.
(5) request callback mode, comprising: the terminal firmware management service message request message from application entity is received,
To the processing result of application entity readjustment terminal firmware management.
In an embodiment of the embodiment of the present invention, the corresponding service operations of terminal firmware management service message or clothes
Business ability includes but is not limited at least one of: obtaining terminal firmware Mirror Info, download terminal firmware image, installing terminal
Firmware image, downloading and installing terminal firmware image delete terminal firmware mirror image.
Message is managed by terminal firmware, above-mentioned service operations or service ability may be implemented.In practical applications, may be used
To carry corresponding instruction in messages, by executing instruction carry out firmware management.For example, download terminal firmware image, downloading
And installing terminal firmware image etc..
It is application entity according to terminal firmware management service message in an embodiment of the embodiment of the present invention, it is right
It may include: according to terminal that the M2M terminal of res gentium networked domain and/or the M2M terminal of other Internet of Things domains, which carry out firmware management,
The M2M foreign identifiers and/or M2M terminal identifier that firmware management service message carries, obtain Internet of Things domain where M2M terminal
Identifier；It is that application entity carries out firmware management to M2M terminal according to the identifier.
In a preferred embodiment of the embodiment of the present invention, Internet of Things domain includes: res gentium networked domain, other Internet of Things
Domain.Preferably, carrying out firmware management to M2M terminal for application entity according to identifier includes: according to res gentium networked domain
The bottom-layer network identifier of bottom-layer network, be application entity to the M2M terminal in the underlying network service entity of bottom-layer network into
Row firmware management；Alternatively, being application entity in other Internet of Things domains according to other Internet of Things identifiers of other Internet of Things domains
M2M terminal carry out firmware management.
It is application entity according to terminal firmware management service message in an embodiment of the embodiment of the present invention, it is right
It includes: for terminal firmware pipe that the M2M terminal of res gentium networked domain and/or the M2M terminal of other Internet of Things domains, which carry out firmware management,
It manages service message and service is provided, wherein the service includes but is not limited at least one of: authorization service, billed services.
Preferably, authorization service authorizes the service ability or operation that can be used for providing to requestor, including following
At least one service ability or operation: authorization service ability or operation.
Preferably, billed services comprise at least one of the following service ability or operation: starting event collection, stopping event are received
Collection, statistical collection.
It is application entity according to terminal firmware management service message in a preferred embodiment of the embodiment of the present invention
It includes: to terminal firmware that the M2M terminal of M2M terminal and/or other Internet of Things domains to res gentium networked domain, which carries out firmware management,
Management service message carries out protocol adaptation；Firmware management is carried out to M2M terminal according to the agreement that adaptation obtains.
Preferably, above-mentioned agreement includes but is not limited at least one of: scalable message and presentation agreement (XMPP) disappear
Cease the client device that (MQTT), the terminal management protocol (OMA DM) of Open Mobile Alliance, Broadband Forum are transmitted in queue telemetering
The lightweight machine to machine agreement (OMA of wide area network management agreement series of canonical (BBF CWMP), Open Mobile Alliance
LightweightM2M).
According to embodiments of the present invention, a kind of firmware management device of internet-of-things terminal is provided, it is of the invention real to realize
Apply the above method of example.
Fig. 3 is the structural block diagram of the firmware management device of internet-of-things terminal according to an embodiment of the present invention, as shown in figure 3,
The device includes: receiving module 302 and management module 304, wherein receiving module 302, for receiving the end from application entity
Hold firmware management service message；Management module 304 is connected with receiving module 302, for according to terminal firmware management service report
Text is application entity, and the M2M terminal of M2M terminal and/or other Internet of Things domains to res gentium networked domain carries out firmware management.
Through the embodiment of the present invention, the unified management of publicly-owned Internet of Things and the M2M terminal of other Internet of Things is solved the problems, such as,
Realize the unified management of the M2M terminal to publicly-owned Internet of Things and other Internet of Things.
In an embodiment of the embodiment of the present invention, the information that terminal firmware management service message carries includes following
At least one: M2M request identifier, M2M request promoter, M2M terminal identifier, M2M service identifier, M2M outer logo
Symbol, application identifier, service order identifier, M2M end message, M2M group information, schedule information.
In an embodiment of the embodiment of the present invention, message exchange pattern that terminal firmware management service message uses
Including but not limited at least one of:
(1) publish-subscribe model, comprising: the subscription terminal management event message from application entity is received, according to application
The issue terminal firmware management message of entity carries out firmware management to M2M terminal, and it is logical to return to terminal management event to application entity
Know message.
(2) response modes are requested, comprising: the terminal firmware management service message request message from application entity is received,
Terminal firmware management service message response message is returned to application entity.
(3) unidirectional request mode, comprising: receive the terminal firmware management service message request message from application entity.
(4) request and multiple response modes, comprising: receive the terminal firmware management service message request from application entity
Message repeatedly returns to terminal firmware management service message response message to application entity.
(5) request callback mode, comprising: the terminal firmware management service message request message from application entity is received,
To the processing result of application entity readjustment terminal firmware management.
Based on above-mentioned preferred interacting message mode, receiving module 302 can receive message under above-mentioned each mode.
In an embodiment of the embodiment of the present invention, the corresponding service operations of terminal firmware management service message or clothes
Business ability includes at least one of: obtaining terminal firmware Mirror Info, download terminal firmware image, installing terminal firmware mirror
Picture, downloading and installing terminal firmware image delete terminal firmware mirror image.
Preferably, above-mentioned service operations or service ability can be used as instruction or information is carried in above-mentioned terminal firmware pipe
It manages in service message, management module 304 can carry out firmware management to M2M terminal according to above-metioned instruction or information.
In an embodiment of the embodiment of the present invention, management module 304 may include: acquiring unit, be used for basis
The M2M foreign identifiers and/or M2M terminal identifier that terminal firmware management service message carries, obtain Internet of Things where M2M terminal
The identifier of domain；Administrative unit, for being that application entity carries out firmware management to M2M terminal according to the identifier.
In a preferred embodiment of the embodiment of the present invention, above-mentioned Internet of Things domain include: res gentium networked domain, other
Internet of Things domain.Administrative unit can be used for the bottom-layer network identifier according to the bottom-layer network of res gentium networked domain, real for application
Body carries out firmware management to the M2M terminal in the underlying network service entity of the bottom-layer network；Or for according to other Internet of Things
Other Internet of Things identifiers of domain are that application entity carries out firmware management to the M2M terminal in other Internet of Things domains.
In a preferred embodiment of the embodiment of the present invention, management module 304 is also used to as terminal firmware management clothes
Business message provides service, which includes at least one of: authorization service, billed services.
In an embodiment of the embodiment of the present invention, management module 304 may include: adaptation unit, for end
Firmware management service message is held to carry out protocol adaptation；Administrative unit, the agreement for being obtained according to adaptation consolidate M2M terminal
Part management.
Preferably, above-mentioned agreement includes but is not limited at least one of: scalable message and presentation agreement (XMPP) disappear
Cease the client device that (MQTT), the terminal management protocol (OMA DM) of Open Mobile Alliance, Broadband Forum are transmitted in queue telemetering
The lightweight machine to machine agreement (OMA of wide area network management agreement series of canonical (BBF CWMP), Open Mobile Alliance
LightweightM2M).
According to embodiments of the present invention, a kind of generic service entity is provided, is located at res gentium networked domain, including the present invention is in fact
Apply any of the above-described device of example.
It is according to the present invention, provide a kind of publicly-owned internet of things equipment, including any of the above-described device of the embodiment of the present invention.It should
Publicly-owned internet of things equipment can be the other equipment in M2M terminal, M2M gateway and Internet of Things, or the telecommunications on basis is set
It is standby.
Preferably, above-mentioned publicly-owned internet of things equipment includes processor and storage device, and storage device, which can store, to be had
The program unit of the function of the above-mentioned apparatus of the embodiment of the present invention, processor can execute the program unit.
The preferred embodiment of the embodiment of the present invention is described below.
In the preferred embodiment, as shown in figure 4, the hierarchical mode in M2M network mainly includes application layer, generic service
Layer, underlying network service layer, corresponding function structure mainly includes application entity, generic service entity, underlying network service
Entity.
Application entity provides the application logic of end-to-end scheme, can be in M2M terminal, M2M gateway, M2M server.
Generic service entity provides the generic service function of M2M environment, can be in M2M terminal, M2M gateway, M2M server.Bottom
Layer network service entities provide service for generic service entity.
Preferably, controlled M2M terminal does not include generic service entity.
M2M network in the preferred embodiment is based on Service-Oriented Architecture Based.In Service-oriented Architecture Reference Model, service
Be it is a kind of authorize the right of one or more functions or the mechanism of method of accessing, access is simultaneously kept using defined interface and service
The constraint of description and strategy are consistent.M2M network based on Service-Oriented Architecture Based can be adapted for res gentium the Internet services quotient's
Infrastructure domain, wherein generic service entity may be considered one group of serviced component, and generic service entity provides for M2M application
Service execution scenarios.
Referring to Fig. 4, the infrastructure domain of res gentium the Internet services quotient includes that application entity, generic service entity (can also claim
For M2M service execution scenarios.When specifically generic service entity is in network service side, place M2M server is equivalent to
M2M service issuance platform), underlying network service entity.
Generic service entity includes at least one of following serviced component: servicing exposure component 10, terminal management component
20, service subscription component 30, billing component 40, network service utilize component 50, infrastructure component 60, remote service exposure group
Part 70.Above-mentioned various components are described below.
Exposure component 10 is serviced, for servicing to application entity exposure.The service exposure component 10 of the preferred embodiment
The receiving module 302 being equivalent in the above embodiment of the present invention below carries out the preferred embodiment for servicing exposure component 10
Description.
Fig. 5 is the structural block diagram for preferably servicing exposed component according to the present invention, as shown in figure 5, the component includes: to receive
Module 12, for receiving the terminal firmware management service message from application entity；Sending module 14, for being sent out to application entity
Send response or notice or readjustment.
Preferably, receiving module 12 includes with one of lower unit: the receiving unit 122 that gives out information subscribes to message sink list
First 124, request message receiving unit 126.Wherein, give out information receiving module 122, for receiving the publication from application entity
Terminal firmware management service message.Message reception units 124 are subscribed to, for receiving the subscription terminal conduit from application entity
Manage event message.Request message receiving unit 126, for receiving the terminal firmware management service message request from application entity
Message.
Preferably, sending module 14 one of comprises the following modules: notification message transmission unit 142, response message send single
Member 144, readjustment message sending unit 146.Wherein, notification message sending module 142, for sending terminal management to application entity
Event notification message.Response message transmission unit 144 disappears for sending terminal firmware management service message response to application entity
Breath.Message sending unit 146 is adjusted back, for the processing result to application entity readjustment terminal firmware management.
Terminal management component 20 is equivalent to the management module 304 of the embodiment of the present invention, for providing one of following service:
Terminal management business service, terminal management adaptation services.The service logic of terminal management business service realization terminal management.Terminal
Manage adaptation services maintenance M2M foreign identifiers and/or M2M terminal identifier and bottom-layer network identifier or other domain service providers
The mapping relations of identifier, according to the agreement that bottom-layer network identifier or other domain service provider identifier identification terminals are supported,
To the adaptation for the agreement that terminal firmware management service message is supported.
Service order component 30, for providing the service of order, safeguard service order relations.
Billing component 40, for providing book keeping operation, billing of services.
Network service utilizes component 50, for using the service of underlying network service entity.
Infrastructure component 60 provides one of effectiveness service, including following service: safety, authorization, certification etc..
Remote service exposes component 70, for connecting external service from other M2M environment.Other M2M environment can be with
Lower at least one: privately owned Internet of Things, community's Internet of Things, industry Internet of Things etc..
In practical applications, the serviced component in generic service entity realizes communication, particular technique by WEB service mode
Service bus can be used.
Fig. 6 is the flow chart of the firmware management method of the preferred internet-of-things terminal of example according to the present invention, as shown in fig. 6,
The method comprising the steps of S602 to step S604.
Step S602, generic service entity receive the terminal firmware management service message from application entity.
Preferably, the information that terminal firmware management service message carries includes: M2M request identifier, M2M request initiation
Person, M2M terminal identifier, M2M service identifier, M2M foreign identifiers, application identifier, service order identifier, M2M are whole
Client information, M2M group information, schedule information etc..
Wherein, M2M request identifier is for identifying the message request information.M2M requests promoter for identifying initiation pair
As initiating object can be following one: individual, gateway, server, application, service, serviced component etc..M2M terminal identifier
For identifying M2M terminal.M2M service identifier for identifying M2M service, in the preferred embodiment for terminal management service or
Terminal firmware management service.M2M foreign identifiers for M2M service provider identify external network domain, including bottom-layer network or other
Internet of Things/service provider.Application identifier is for identifying application entity.Service order identifier for M2M service provider binding application,
M2M terminal, service, the order relations between generic service entity.M2M end message includes the management information of M2M terminal, includes
Following one: management object, administration order, terminal capability, terminal labels, terminal type, terminal model.M2M group information packet
Containing following one: group name, number of members, members list, member type, group policy, member's access control right.Scheduling peace
Arranging information includes following one: scheduling periods, scheduling repetition period.
Step S604, generic service entity are application entity to other M2M environment according to terminal firmware management service message
Or the terminal of bottom-layer network carries out firmware management.
Preferably, the terminal firmware management service message is using following message switch mode with reference to before the embodiment of the present invention
The mode stated, details are not described herein for particular content.
Preferably, it is solid one of the corresponding following service operations of terminal firmware management service message or service ability: to obtain terminal
Part Mirror Info, download terminal mirror image firmware, installing terminal mirror image firmware, downloading and installing terminal firmware image delete terminal
Firmware image etc..
Preferably, generic service entity is that application entity carries out firmware pipe to terminal according to terminal firmware management service message
Reason include: generic service entity according to the combination of M2M foreign identifiers and M2M terminal identifier or in which one of, obtain bottom
Network identifier or other domain service provider identifiers (being completed by the terminal management component of generic service entity) and according to underlying network
Network identifier, (being realized by network service using component) carry out firmware management to the terminal in underlying network service entity；Or
Person's generic service entity is according to other domain service provider identifiers, and (being realized by remote service exposure component) is to other M2M environment
In terminal carry out firmware management.
Preferably, generic service entity is that application entity carries out firmware pipe to terminal according to terminal firmware management service message
Reason, which includes: generic service entity, provides one of following service: authorization service, billed services for terminal firmware management service message.
Preferably, generic service entity is that application entity carries out firmware pipe to terminal according to terminal firmware management service message
Reason includes: generic service entity according to one of the terminal firmware management service message progress protocol adaptation, including following agreement:
XMPP(scalable message and agreement is presented), MQTT(message queue telemetering transmission), the terminal conduit of OMA DM(Open Mobile Alliance
Manage agreement), the client device wide area network management agreement series of canonical of BBF CWMP(Broadband Forum), OMA
The lightweight machine to machine agreement of LightweightM2M(Open Mobile Alliance) etc..
Further, XMPP protocol is adapted to one of described terminal firmware management service message, including following message: obtaining eventually
End firmware information service operations be mapped as XMPP obtain nodal information relevant operation (including obtain node, obtain node parameter, obtain
Take node orders etc.), the operation of download terminal firmware service is mapped as XMPP execution node orders, and (parameter includes executing terminal to support
Download terminal firmware operation), installing terminal firmware service operation be mapped as XMPP execute node orders (parameter include execute end
Hold the installing terminal firmware operation supported), it downloads and the operation of installing terminal firmware service is mapped as XMPP and executes node orders (ginseng
Number includes executing the downloading and installing terminal firmware operation that terminal is supported) etc..
Further, it one of terminal firmware management service message, including following message described in MQTT protocol adaptation: obtains eventually
End firmware information service operations are mapped as MQTT and give out information (parameter includes obtaining the operation of terminal firmware information), and download terminal is solid
Part service operations are mapped as MQTT and give out information (parameter includes download terminal firmware operation), and the operation of installing terminal firmware service is reflected
It penetrates and gives out information (parameter includes installing terminal firmware operation) for MQTT, download and the operation of installing terminal firmware service is mapped as
MQTT gives out information (parameter includes downloading and installing terminal firmware operation), and MQTT subscribes to message (subscribing to terminal management event),
MQTT notification message (notice terminal management event) etc..
Further, it one of terminal firmware management service message, including following message described in OMA DM protocol adaptation: obtains
Terminal firmware information service operation is mapped as OMA DM order (firmware update manages object-acquisition state), download terminal firmware
Service operations are mapped as OMA DM order (firmware update manages object-downloading), and the operation of installing terminal firmware service is mapped as
OMA DM order (firmware update manages object-update), is downloaded and the operation of installing terminal firmware service is mapped as OMA DM order
(firmware update management object-downloading simultaneously updates) etc..
Below with reference to example, which is described in detail, though it is foreseeable that the preferred embodiment
It is not limited to following methods.
Fig. 7 is the flow diagram of the firmware management method of preferred internet-of-things terminal according to embodiments of the present invention, such as Fig. 7
It is shown, the method comprising the steps of S702 to step S716.
Step S702, application entity send terminal firmware management service report to the service of generic service entity exposure component 10
Text.
Preferably, terminal firmware management service message includes one of following parameter: M2M request identifier, promoter, M2M
Terminal identifier, M2M service identifier, M2M foreign identifiers, application identifier, service order identifier, M2M end message,
M2M group information, schedule information etc..
Preferably, message exchange pattern can be following one: publish-subscribe model, request response modes, unidirectional request
Mode, request callback mode, request and multiple response modes.
Preferably, the operation of terminal firmware management service message corresponding with service or service ability can be following one: obtain
Terminal firmware Mirror Info, download terminal firmware image, installing terminal firmware image, downloading and installing terminal firmware image are deleted
Except terminal firmware mirror image etc..
Step S704, the service of generic service entity expose component 10 to the 20 forwarding terminal firmware management of terminal management component
Service message.
Step S706, the terminal management component 20 of generic service entity sends verification service to service order component 30 and disappears
Breath.
Preferably, verification service message includes one of following parameter: service identifier, service order identifier etc..
Step S708, the terminal management component 20 of generic service entity sends authorization service operation to infrastructure component 60
Message.
Preferably, authorization service operation information includes one of following parameter: service identifier, service order identifier etc..
Step S710, the infrastructure component 60 of generic service entity is sent to service order component 30 obtains authorization.
Preferably, obtain in authorization comprising one of following parameter: promoter, application identifier, service identifier, service are ordered
Purchase identifier etc.；And corresponding authorization message is obtained, service operations or the service energy of authorization are then returned to terminal management component
Power.
The terminal management component 20 of step S712, generic service entity are sharp to remote service exposure component 70 or network service
Terminal firmware management service message is sent with component 50.
Preferably, terminal firmware management service message includes one of following parameter: M2M request identifier, M2M terminal iidentification
Symbol, other domain service provider identifiers or bottom-layer network identifier, service order identifier, application identifier, M2M end message,
M2M group information, schedule information etc..
Step S714, the remote service exposure component 70 of generic service entity or network service call other using component 50
Internet of Things domain or bottom-layer network.
Step S716, other Internet of Things domains or bottom-layer network by the remote service of generic service entity exposure component 70 or
Network service sends the processing result logout of terminal firmware management service using component 50 to billing component 40.
Since terminal firmware management service message may be implemented comprising the firmware management to multiple terminals or according to scheduling
Firmware management to terminal, thus generic service entity to application entity return there are diversified forms, including respond or notify or
Readjustment.
It can be seen from the above description that the present invention realizes following technical effect: solving publicly-owned Internet of Things and its
The unified management problem of the M2M terminal of his Internet of Things realizes the unification of the M2M terminal to publicly-owned Internet of Things and other Internet of Things
Management.
Obviously, those skilled in the art should be understood that each module of the above invention or each step can be with general
Computing device realize that they can be concentrated on a single computing device, or be distributed in multiple computing devices and formed
Network on, optionally, they can be realized with the program code that computing device can perform, it is thus possible to which they are stored
It is performed by computing device in the storage device, and in some cases, it can be to be different from shown in sequence execution herein
Out or description the step of, perhaps they are fabricated to each integrated circuit modules or by them multiple modules or
Step is fabricated to single integrated circuit module to realize.In this way, the present invention is not limited to any specific hardware and softwares to combine.
The foregoing is only a preferred embodiment of the present invention, is not intended to restrict the invention, for the skill of this field
For art personnel, the invention may be variously modified and varied.All within the spirits and principles of the present invention, made any to repair
Change, equivalent replacement, improvement etc., should all be included in the protection scope of the present invention.
Claims (17)
1. a kind of firmware management method of internet-of-things terminal characterized by comprising
Receive the terminal firmware management service message from application entity；
According to the terminal firmware management service message be the application entity, to the M2M terminal of res gentium networked domain and/or its
The M2M terminal of his Internet of Things domain carries out firmware management；
Wherein, the information that the terminal firmware management service message carries includes at least one of: M2M request identifier, M2M
Request promoter, M2M terminal identifier, M2M service identifier, M2M foreign identifiers, application identifier, service order mark
Symbol, M2M end message, M2M group information, schedule information.
2. the method according to claim 1, wherein the message that the terminal firmware management service message uses is handed over
Mold changing formula includes at least one of:
Publish-subscribe model, comprising: the subscription terminal management event message from the application entity is received, according to the application
The issue terminal firmware management message of entity carries out firmware management to M2M terminal, returns to terminal conduit director to the application entity
Part notification message；
Request response modes, comprising: the terminal firmware management service message request message from the application entity is received, to institute
It states application entity and returns to terminal firmware management service message response message；
Unidirectional request mode, comprising: receive the terminal firmware management service message request message from the application entity；
Request and multiple response modes, comprising: receive the terminal firmware management service message request from the application entity and disappear
Breath repeatedly returns to terminal firmware management service message response message to the application entity；
Request callback mode, comprising: the terminal firmware management service message request message from the application entity is received, to institute
State the processing result of application entity readjustment terminal firmware management.
3. the method according to claim 1, wherein the corresponding service behaviour of the terminal firmware management service message
Make or service ability includes at least one of: it is solid to obtain terminal firmware Mirror Info, download terminal firmware image, installing terminal
Part mirror image, downloading and installing terminal firmware image delete terminal firmware mirror image.
4. the method according to claim 1, wherein being that the application is real according to terminal firmware management service message
Body carries out firmware management to the M2M terminal of res gentium networked domain and/or the M2M terminal of other Internet of Things domains
The M2M foreign identifiers and/or M2M terminal identifier carried according to the terminal firmware management service message, obtain M2M
The identifier of Internet of Things domain where terminal；
It is that the application entity carries out firmware management to M2M terminal according to the identifier.
5. according to the method described in claim 4, it is characterized in that, the Internet of Things domain includes: the res gentium networked domain, institute
State other Internet of Things domains；It is that the application entity includes: to the progress firmware management of M2M terminal according to the identifier
It is the application entity to the underlying network according to the bottom-layer network identifier of the bottom-layer network of the res gentium networked domain
M2M terminal in the underlying network service entity of network carries out firmware management；Or
It is the application entity in other described Internet of Things domains according to other Internet of Things identifiers of other Internet of Things domains
M2M terminal carry out firmware management.
6. the method according to claim 1, wherein being described answer according to the terminal firmware management service message
Carrying out firmware management to the M2M terminal of res gentium networked domain and/or the M2M terminal of other Internet of Things domains with entity includes:
Service is provided for the terminal firmware management service message, wherein the services package includes at least one of: authorization service,
Billed services.
7. method according to claim 1 or 6, which is characterized in that according to the terminal firmware management service message be institute
State application entity includes: to the M2M terminal progress firmware management of the M2M terminal and/or other Internet of Things domains of res gentium networked domain
Protocol adaptation is carried out to the terminal firmware management service message；
Firmware management is carried out to M2M terminal according to the agreement that adaptation obtains.
8. the method according to the description of claim 7 is characterized in that the agreement includes at least one of: scalable message
With terminal management protocol OMA DM, the Broadband Forum that agreement XMPP, message queue telemetering transmission MQTT, Open Mobile Alliance is presented
Client device wide area network management agreement series of canonical BBF CWMP, Open Mobile Alliance lightweight machine to machine agreement
OMA LightweightM2M。
9. a kind of firmware management device of internet-of-things terminal characterized by comprising
Receiving module, for receiving the terminal firmware management service message from application entity；
Management module, for being the application entity according to the terminal firmware management service message, to res gentium networked domain
The M2M terminal of M2M terminal and/or other Internet of Things domains carries out firmware management；
Wherein, the information that the terminal firmware management service message carries includes at least one of: M2M request identifier, M2M
Request promoter, M2M terminal identifier, M2M service identifier, M2M foreign identifiers, application identifier, service order mark
Symbol, M2M end message, M2M group information, schedule information.
10. device according to claim 9, which is characterized in that the message that the terminal firmware management service message uses
Switch mode includes at least one of:
Publish-subscribe model, comprising: the subscription terminal management event message from the application entity is received, according to the application
The issue terminal firmware management message of entity carries out firmware management to M2M terminal, returns to terminal conduit director to the application entity
Part notification message；
Request response modes, comprising: the terminal firmware management service message request message from the application entity is received, to institute
It states application entity and returns to terminal firmware management service message response message；
Unidirectional request mode, comprising: receive the terminal firmware management service message request message from the application entity；
Request and multiple response modes, comprising: receive the terminal firmware management service message request from the application entity and disappear
Breath repeatedly returns to terminal firmware management service message response message to the application entity；
Request callback mode, comprising: the terminal firmware management service message request message from the application entity is received, to institute
State the processing result of application entity readjustment terminal firmware management.
11. device according to claim 9, which is characterized in that the corresponding service of the terminal firmware management service message
Operation or service ability include at least one of: obtaining terminal firmware Mirror Info, download terminal firmware image, installing terminal
Firmware image, downloading and installing terminal firmware image delete terminal firmware mirror image.
12. device according to claim 9, which is characterized in that the management module, comprising:
Acquiring unit, M2M foreign identifiers and/or M2M terminal for being carried according to the terminal firmware management service message
Identifier, the identifier of Internet of Things domain where obtaining M2M terminal；
Administrative unit, for being that the application entity carries out firmware management to M2M terminal according to the identifier.
13. device according to claim 12, which is characterized in that the Internet of Things domain include: the res gentium networked domain,
Other described Internet of Things domains；The administrative unit,
It is the application entity to the bottom for the bottom-layer network identifier according to the bottom-layer network of the res gentium networked domain
M2M terminal in the underlying network service entity of layer network carries out firmware management；Or
It is the application entity to other described Internet of Things for other Internet of Things identifiers according to other Internet of Things domains
M2M terminal in domain carries out firmware management.
14. device according to claim 9, which is characterized in that the management module is also used to as the terminal firmware pipe
It manages service message and service is provided, wherein the services package includes at least one of: authorization service, billed services.
15. the device according to claim 9 or 14, which is characterized in that the management module includes:
Adaptation unit, for carrying out protocol adaptation to the terminal firmware management service message；
Administrative unit, the agreement for being obtained according to adaptation carry out firmware management to M2M terminal.
16. a kind of publicly-owned internet of things equipment characterized by comprising device described in any one of claim 9 to 15.
17. a kind of generic service entity is located at res gentium networked domain characterized by comprising any in claim 9 to 15
Device described in.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410127491.6A CN104954412B (en) | 2014-03-31 | 2014-03-31 | The firmware management method, apparatus and generic service entity of internet-of-things terminal |
| PCT/CN2014/092974 WO2015149531A1 (en) | 2014-03-31 | 2014-12-03 | Internet of things terminal firmware management method, device and general service entity |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410127491.6A CN104954412B (en) | 2014-03-31 | 2014-03-31 | The firmware management method, apparatus and generic service entity of internet-of-things terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104954412A CN104954412A (en) | 2015-09-30 |
| CN104954412B true CN104954412B (en) | 2019-01-04 |
Family
ID=54168763
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410127491.6A Active CN104954412B (en) | 2014-03-31 | 2014-03-31 | The firmware management method, apparatus and generic service entity of internet-of-things terminal |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN104954412B (en) |
| WO (1) | WO2015149531A1 (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11044593B2 (en) * | 2015-12-03 | 2021-06-22 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and devices for managing constrained devices |
| US10310832B2 (en) | 2016-02-19 | 2019-06-04 | Intel Corporation | Internet-of-things device blank |
| US11146449B2 (en) | 2016-02-19 | 2021-10-12 | Intel Corporation | Network architecture for internet-of-things device |
| CN110809262B (en) * | 2019-11-08 | 2023-09-01 | 杭州海兴电力科技股份有限公司 | COAP protocol-based operation and maintenance management method for Internet of things equipment |
| US10827329B1 (en) | 2020-02-26 | 2020-11-03 | At&T Mobility Ii Llc | Facilitation of dynamic edge computations for 6G or other next generation network |
| US11418933B2 (en) | 2020-03-19 | 2022-08-16 | At&T Mobility Ii Llc | Facilitation of container management for internet of things devices for 5G or other next generation network |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102291430A (en) * | 2011-06-28 | 2011-12-21 | 中国联合网络通信集团有限公司 | Method for processing allocation information of Internet of things, Internet of things platform and system |
| CN102801544A (en) * | 2011-05-25 | 2012-11-28 | 中兴通讯股份有限公司 | Method and system for unified terminal management under Internet of things architecture |
| CN103227813A (en) * | 2013-03-21 | 2013-07-31 | 重庆电子工程职业学院 | Automatic long-distance updating system and method for family Internet of Things system |
-
2014
- 2014-03-31 CN CN201410127491.6A patent/CN104954412B/en active Active
- 2014-12-03 WO PCT/CN2014/092974 patent/WO2015149531A1/en active Application Filing
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102801544A (en) * | 2011-05-25 | 2012-11-28 | 中兴通讯股份有限公司 | Method and system for unified terminal management under Internet of things architecture |
| CN102291430A (en) * | 2011-06-28 | 2011-12-21 | 中国联合网络通信集团有限公司 | Method for processing allocation information of Internet of things, Internet of things platform and system |
| CN103227813A (en) * | 2013-03-21 | 2013-07-31 | 重庆电子工程职业学院 | Automatic long-distance updating system and method for family Internet of Things system |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2015149531A1 (en) | 2015-10-08 |
| CN104954412A (en) | 2015-09-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104954412B (en) | The firmware management method, apparatus and generic service entity of internet-of-things terminal | |
| CN104967650B (en) | Third party's electricity business platform is unified dissemination method | |
| CN102202089B (en) | machine to machine framework | |
| AU2006201516B2 (en) | Service delivery platform | |
| CA2840511C (en) | Systems, methods, and/or apparatus for enabling communication between devices using different communication protocols | |
| CN103220325B (en) | For the method and system for managing nextport hardware component NextPort in cloud computing environment | |
| US20220208319A1 (en) | Multi-services application gateway and system employing the same | |
| CN101626363B (en) | Convergence service device and system, and convergence service establishing and using methods | |
| CN106797392A (en) | The issue and discovery of M2M IOT services | |
| CN105450435A (en) | Equipment application software management service method, device and system for the Internet of Things | |
| CN101365120B (en) | Data centralized management method for network video monitoring system | |
| EP2621243B1 (en) | Method and system for configuring and managing third party software, and management server | |
| JP2018120537A (en) | Information processing system, method for controlling information processing system, and program therefor | |
| CA2606193A1 (en) | Method for providing wireless application privilege management | |
| WO2015184879A1 (en) | Terminal topology management service method, device, and system for internet of things | |
| CN106899560A (en) | The method and internet-of-things terminal of a kind of automatic intercommunication of Internet of Things different agreement | |
| CN105282118B (en) | Control resource Notification of Changes message method and device | |
| Alhuseini et al. | 5G service value chain and network slicing framework using ecosystem modeling, agile delivery, and user-story automation | |
| US20100241716A1 (en) | System for interconnecting manifold entities across a real-time Meshed Information Exchange network | |
| US10750356B2 (en) | Configuration management method, apparatus, and system for terminal in internet of things | |
| CN105472647A (en) | Internet of things equipment troubleshooting service method, device and system | |
| CN101365121B (en) | System configuring information modifying and storing method used by network video monitoring system | |
| CN104598974A (en) | Method and system capable of realizing offline resource accurate reservation and digital entertainment demand system | |
| CN104954347A (en) | M2M application service method, device thereof and system thereof | |
| US9241029B2 (en) | Open application interface for complex systems |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |