WO2015149531A1 - 物联网终端的固件管理方法、装置及通用服务实体 - Google Patents

物联网终端的固件管理方法、装置及通用服务实体 Download PDF

Info

Publication number
WO2015149531A1
WO2015149531A1 PCT/CN2014/092974 CN2014092974W WO2015149531A1 WO 2015149531 A1 WO2015149531 A1 WO 2015149531A1 CN 2014092974 W CN2014092974 W CN 2014092974W WO 2015149531 A1 WO2015149531 A1 WO 2015149531A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
service
message
firmware management
internet
Prior art date
Application number
PCT/CN2014/092974
Other languages
English (en)
French (fr)
Inventor
邵伟翔
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2015149531A1 publication Critical patent/WO2015149531A1/zh

Links

Images

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

Definitions

  • the present invention relates to the field of communications, and in particular to a firmware management method, apparatus, and general service entity for an Internet of Things terminal.
  • the Internet of Things is an important part of the new generation of information technology. Its English name is “The Internet of things”. As the name suggests, the Internet of Things is the Internet that connects things to things.
  • the ITU Internet Report issued by the International Telecommunication Union (ITU) defines the Internet of Things as follows: two-dimensional code recognition equipment, radio frequency identification (RFID) devices, infrared sensors, An information sensing device such as a global positioning system and a laser scanner that connects any item to the Internet in accordance with a contracted agreement for information exchange and communication to realize a network for intelligent identification, location, tracking, monitoring, and management.
  • the concept of M2M is often introduced in the Internet of Things, which can be explained as Man to Man, Man to Machine, Machine to Machine. In essence, the interaction between people and machines, machines and machines is mostly to achieve information exchange between people.
  • the M2M network is the main form of expression of the Internet of Things at this stage.
  • the M2M network includes a machine-to-machine communication network, a human-to-machine communication network, and a machine-to-human communication network.
  • the devices of the M2M network mainly include an M2M terminal, an M2M gateway, and an M2M server.
  • FIG. 1 is a schematic diagram of an Internet of Things system according to the related art.
  • an Internet of Things can be classified into a private Internet of Things (generally providing services to a single institution), and a public Internet of Things (based on the Internet to provide a public or large user community). Service), community Internet of Things (providing services to an associated "community" or community), etc.
  • the Internet of Things has a large number of applications in different industries, including intelligent agriculture, smart grid, intelligent transportation, intelligent logistics, smart medical, smart home and so on.
  • each of these industries deploys their own specialized Internet of Things including corresponding professional IoT/M2M devices such as terminals, gateways, and servers.
  • telecom operators As a provider of public communication services, telecom operators also act as public IoT service providers when they provide IoT/M2M services. For private Internet of Things, community Internet of Things, and professional Internet of Things terminals in various industries, telecom operators as public IoT service providers lack effective technical means to implement unified terminal management and implement services.
  • the present invention provides a method, a device, and a general service entity for firmware management of an Internet of Things terminal, in a manner that the service provider of the Internet of Things and other Internet of Things domains cannot be uniformly managed by the telecommunication operator as a public IoT service provider. At least solve the above problem.
  • a firmware management method for an Internet of Things terminal includes: receiving a terminal firmware management service message from an application entity; and using the terminal firmware management service message as the application entity,
  • the M2M terminal of the public Internet of Things domain and/or the M2M terminal of other Internet of Things domain perform firmware management.
  • the information carried by the terminal firmware management service message includes at least one of the following: an M2M request identifier, an M2M request initiator, an M2M terminal identifier, an M2M service identifier, an M2M external identifier, an application identifier, and a service subscription identifier. , M2M terminal information, M2M group information, scheduling information.
  • the message exchange mode used by the terminal firmware management service message includes at least one of the following: a subscription subscription mode, including: receiving a subscription terminal management event message from the application entity, according to a publishing terminal firmware management message pair of the application entity
  • the M2M terminal performs firmware management, and returns a terminal management event notification message to the application entity.
  • the request response mode includes: receiving a terminal firmware management service message request message from the application entity, and returning a terminal firmware management service to the application entity.
  • the one-way request mode includes: receiving a terminal firmware management service message request message from the application entity; requesting and multiple response modes, including: receiving a terminal firmware management service message from the application entity Returning a terminal firmware management service message response message to the application entity multiple times; the request callback mode includes: receiving a terminal firmware management service message request message from the application entity, and calling back to the application entity The processing result of terminal firmware management.
  • the service operation or service capability corresponding to the terminal firmware management service message includes at least one of: obtaining terminal firmware image information, downloading a terminal firmware image, installing a terminal firmware image, downloading and installing a terminal firmware image, and deleting a terminal firmware image.
  • Firmware management of the M2M terminal of the public IoT domain and/or the M2M terminal of the other Internet of Things domain by the application entity according to the terminal firmware management service message includes: the M2M external identifier carried according to the terminal firmware management service message And/or an M2M terminal identifier, obtaining an identifier of an Internet of Things domain where the M2M terminal is located; and performing firmware management on the M2M terminal for the application entity according to the identifier.
  • the Internet of Things domain includes: the public Internet of Things domain, the other Internet of Things domain; performing firmware management on the M2M terminal for the application entity according to the identifier includes: according to the underlying network of the public Internet of Things domain An underlying network identifier, the M2M terminal in the underlying network service entity of the underlying network by the application entity Performing firmware management on the end; or performing firmware management on the M2M terminals in the other Internet of Things domain for the application entity according to other IoT identifiers of the other Internet of Things domain.
  • Performing firmware management for the M2M terminal of the public IoT domain and/or the M2M terminal of the other Internet of Things domain by the application entity according to the terminal firmware management service message includes: providing a service for the terminal firmware management service message, where The service includes at least one of the following: an authorization service, a billing service.
  • Performing firmware management on the M2M terminal of the public IoT domain and/or the M2M terminal of the other Internet of Things domain by the application entity according to the terminal firmware management service message includes: performing protocol adaptation on the terminal firmware management service message Firmware management of the M2M terminal according to the protocol obtained by the adaptation.
  • the protocol includes at least one of the following: an extensible message and a presentation protocol XMPP, a message queue telemetry transmission MQTT, an Open Mobile Alliance terminal management protocol OMA DM, a broadband forum client device WAN management protocol series specification BBF CWMP, an Open Mobile Alliance Lightweight machine to machine protocol OMA LightweightM2M.
  • a firmware management apparatus for an Internet of Things terminal, comprising: a receiving module configured to receive a terminal firmware management service message from an application entity; and a management module configured to be based on the terminal firmware
  • the management service message is the application entity, and performs firmware management on the M2M terminal of the public Internet of Things domain and/or the M2M terminal of other Internet of Things domain.
  • the information carried by the terminal firmware management service message includes at least one of the following: an M2M request identifier, an M2M request initiator, an M2M terminal identifier, an M2M service identifier, an M2M external identifier, an application identifier, and a service subscription identifier. , M2M terminal information, M2M group information, scheduling information.
  • the message exchange mode used by the terminal firmware management service message includes at least one of the following: a subscription subscription mode, including: receiving a subscription terminal management event message from the application entity, according to a publishing terminal firmware management message pair of the application entity
  • the M2M terminal performs firmware management, and returns a terminal management event notification message to the application entity.
  • the request response mode includes: receiving a terminal firmware management service message request message from the application entity, and returning a terminal firmware management service to the application entity.
  • the one-way request mode includes: receiving a terminal firmware management service message request message from the application entity; requesting and multiple response modes, including: receiving a terminal firmware management service message from the application entity Returning a terminal firmware management service message response message to the application entity multiple times; the request callback mode includes: receiving a terminal firmware management service message request message from the application entity, and calling back to the application entity The processing result of terminal firmware management.
  • the service operation or service capability corresponding to the terminal firmware management service message includes at least one of: obtaining terminal firmware image information, downloading a terminal firmware image, installing a terminal firmware image, downloading and installing a terminal firmware image, and deleting a terminal firmware image.
  • the management module includes: an obtaining unit, configured to acquire an identifier of an Internet of Things domain where the M2M terminal is located according to the M2M external identifier and/or the M2M terminal identifier carried in the terminal firmware management service message; Firmware management of the M2M terminal for the application entity according to the identifier.
  • the Internet of Things domain includes: the public Internet of Things domain, the other Internet of Things domain; the management unit is configured to be an application entity pair according to an underlying network identifier of an underlying network of the public Internet of Things domain
  • the M2M terminal in the underlying network service entity of the underlying network performs firmware management; or is configured to refer to the M2M terminal in the other Internet of Things domain by the application entity according to other IoT identifiers of the other Internet of Things domain Perform firmware management.
  • the management module is further configured to provide a service for the terminal firmware management service message, where the service includes at least one of the following: an authorization service and a billing service.
  • the management module includes: an adaptation unit configured to perform protocol adaptation on the terminal firmware management service message; and a management unit configured to perform firmware management on the M2M terminal according to the adapted protocol.
  • a public IoT device including any of the above devices.
  • a generic service entity is provided that is located in a public Internet of Things domain, including any of the devices described above.
  • the embodiment of the present invention receives a terminal firmware management service message from an application entity, and performs firmware management on an M2M terminal of a public IoT domain and/or an M2M terminal of another Internet of Things domain according to the terminal firmware management service message as an application entity. It solves the unified management problem of the M2M terminal of the public IoT and other Internet of Things, and realizes the unified management of the M2M terminal of the public IoT and other Internet of Things.
  • FIG. 1 is a schematic diagram of an Internet of Things system according to the related art
  • FIG. 2 is a flowchart of a firmware management method of an Internet of Things terminal according to an embodiment of the present invention
  • FIG. 3 is a structural block diagram of a firmware management apparatus of an Internet of Things terminal according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of a preferred M2M network in accordance with an embodiment of the invention.
  • FIG. 5 is a block diagram showing the structure of a preferred service exposure component in accordance with the present invention.
  • FIG. 6 is a flowchart of a preferred firmware management method for an Internet of Things terminal according to an embodiment of the present invention.
  • FIG. 7 is a schematic flowchart diagram of a firmware management method of a preferred Internet of Things terminal according to an embodiment of the present invention.
  • the M2M terminal may be a mobile terminal (for example, a mobile phone, a tablet, etc.), or may be another type of terminal as long as it can access the Internet of Things.
  • the operating system running on the terminal is also various types of systems, for example, the currently widely used Android system, or the Windows operating system, the iOS system, etc., but is not limited thereto.
  • Devices can be servers, various types of gateways, or other types of devices.
  • the terminal or device may include a storage medium, and program units stored in the storage medium may be used to perform the methods described in the following embodiments.
  • the terminal or device may also include a processor that is configurable to execute the program elements described above. It is to be expected that the methods or apparatus described below can be implemented by program units.
  • the other Internet of Things domains described below may be private Internet of Things that provide services to a single institution, other public Internet of Things, community Internet of Things.
  • the Internet of Things has a large number of applications in different industries, including intelligent agriculture, smart grid, intelligent transportation, intelligent logistics, smart medical, smart home and so on.
  • a firmware management method for an Internet of Things terminal is provided.
  • FIG. 2 is a flowchart of a firmware management method of an Internet of Things terminal according to an embodiment of the present invention. As shown in FIG. 2, the method includes steps S202 to S204.
  • Step S202 receiving a terminal firmware management service message from an application entity.
  • Step S204 Perform firmware management on the M2M terminal of the public Internet of Things domain and/or the M2M terminal of the other Internet of Things domain according to the terminal firmware management service message as the application entity.
  • the unified management problem of the M2M terminals of the public Internet of Things and other Internet of Things is solved, and the unified management of the M2M terminals of the public Internet of Things and other Internet of Things is realized.
  • the information carried by the terminal firmware management service message includes at least one or any combination of the following: an M2M request identifier, an M2M request initiator, an M2M terminal identifier, and an M2M service identifier. , M2M external identifier, application identifier, service subscription identifier, M2M terminal information, M2M group information, scheduling information.
  • the message exchange mode used by the terminal firmware management service message includes, but is not limited to, at least one of the following:
  • (1) Publishing a subscription mode comprising: receiving a subscription terminal management event message from the application entity, performing firmware management on the M2M terminal according to the publishing terminal firmware management message of the application entity, and returning a terminal management event notification message to the application entity.
  • (2) Requesting a response mode comprising: receiving a terminal firmware management service message request message from the application entity, and returning a terminal firmware management service message response message to the application entity.
  • a one-way request mode comprising: receiving a terminal firmware management service message request message from an application entity.
  • the request and the multiple response mode include: receiving a terminal firmware management service message request message from the application entity, and returning a terminal firmware management service message response message to the application entity multiple times.
  • Requesting a callback mode comprising: receiving a terminal firmware management service message request message from the application entity, and calling back, to the application entity, a processing result of the terminal firmware management.
  • the service operation or service capability corresponding to the terminal firmware management service packet includes, but is not limited to, at least one of the following: acquiring terminal firmware image information, downloading terminal firmware image, installing terminal firmware image, and downloading And install the terminal firmware image and delete the terminal firmware image.
  • the terminal firmware management message Through the terminal firmware management message, the above service operation or service capability can be realized.
  • the corresponding instructions can be carried in the message, and the firmware management can be performed by executing the instruction. For example, download the terminal firmware image, download and install the terminal firmware image, and so on.
  • performing firmware management on the M2M terminal of the public IoT domain and/or the M2M terminal of the other Internet of Things domain may include: managing according to the terminal firmware M2M external identifier and/or M2M terminal identifier carried in the service packet, obtained An identifier of the Internet of Things domain where the M2M terminal is located; according to the identifier, firmware management is performed on the M2M terminal for the application entity.
  • the Internet of Things domain includes: a public Internet of Things domain, and other Internet of Things domains.
  • performing firmware management on the M2M terminal for the application entity according to the identifier comprises: performing firmware management on the M2M terminal in the underlying network service entity of the underlying network for the application entity according to the underlying network identifier of the underlying network of the public Internet of Things domain; Alternatively, firmware management of M2M terminals in other IoT domains for application entities based on other IoT identifiers of other IoT domains.
  • the firmware management of the M2M terminal of the public Internet of Things domain and/or the M2M terminal of the other Internet of Things domain is performed according to the terminal firmware management service message as an application entity, including: for terminal firmware management service.
  • the message provides a service, wherein the service includes but is not limited to at least one of the following: an authorization service, a billing service.
  • the authorization service is arranged to provide a service capability or operation that is authorized to be used by the requester, including at least one of the following service capabilities or operations: authorization service capability or operation.
  • the billing service comprises at least one of the following service capabilities or operations: initiating event collection, stopping event collection, and collecting statistics.
  • the firmware management of the M2M terminal of the public IoT domain and/or the M2M terminal of the other Internet of Things domain is performed by the application entity according to the terminal firmware management service message, including: terminal firmware management service The message is adapted by the protocol; the firmware management of the M2M terminal is performed according to the protocol obtained by the adaptation.
  • the foregoing protocol includes but is not limited to at least one of the following: Extensible Messaging and Presentation Protocol (XMPP), Message Queuing Telemetry Transmission (MQTT), Open Mobile Alliance Terminal Management Protocol (OMA DM), broadband forum client device WAN Management Protocol Series Specification (BBF CWMP), Open Mobile Alliance's Lightweight Machine to Machine Protocol (OMA LightweightM2M).
  • XMPP Extensible Messaging and Presentation Protocol
  • MQTT Message Queuing Telemetry Transmission
  • OMA DM Open Mobile Alliance Terminal Management Protocol
  • BBF CWMP broadband forum client device WAN Management Protocol Series Specification
  • OMA LightweightM2M Open Mobile Alliance's Lightweight Machine to Machine Protocol
  • a firmware management apparatus for an Internet of Things terminal is provided to implement the foregoing method of the embodiment of the present invention.
  • the apparatus includes: a receiving module 302 and a management module 304, wherein the receiving module 302 is configured to receive from an application entity.
  • Terminal firmware management service message ; management module 304, connected to the receiving module 302, set as root
  • the application entity performs firmware management on the M2M terminal of the public IoT domain and/or the M2M terminal of other Internet of Things domain.
  • the unified management problem of the M2M terminals of the public Internet of Things and other Internet of Things is solved, and the unified management of the M2M terminals of the public Internet of Things and other Internet of Things is realized.
  • the information carried by the terminal firmware management service packet includes at least one of the following: an M2M request identifier, an M2M request initiator, an M2M terminal identifier, an M2M service identifier, and an M2M external identifier. , application identifier, service subscription identifier, M2M terminal information, M2M group information, scheduling information.
  • the message exchange mode used by the terminal firmware management service message includes, but is not limited to, at least one of the following:
  • (1) Publishing a subscription mode comprising: receiving a subscription terminal management event message from the application entity, performing firmware management on the M2M terminal according to the publishing terminal firmware management message of the application entity, and returning a terminal management event notification message to the application entity.
  • (2) Requesting a response mode comprising: receiving a terminal firmware management service message request message from the application entity, and returning a terminal firmware management service message response message to the application entity.
  • a one-way request mode comprising: receiving a terminal firmware management service message request message from an application entity.
  • the request and the multiple response mode include: receiving a terminal firmware management service message request message from the application entity, and returning a terminal firmware management service message response message to the application entity multiple times.
  • Requesting a callback mode comprising: receiving a terminal firmware management service message request message from the application entity, and calling back, to the application entity, a processing result of the terminal firmware management.
  • the receiving module 302 can receive messages in the various modes described above.
  • the service operation or service capability corresponding to the terminal firmware management service message includes at least one of the following: acquiring terminal firmware image information, downloading the terminal firmware image, installing the terminal firmware image, and downloading and installing the terminal. Firmware image, delete terminal firmware image.
  • the foregoing service operation or service capability may be carried in the terminal firmware management service message as an instruction or information, and the management module 304 may perform firmware management on the M2M terminal according to the foregoing instruction or information.
  • the management module 304 may include: an obtaining unit, configured to acquire an Internet of Things domain where the M2M terminal is located according to the M2M external identifier and/or the M2M terminal identifier carried in the terminal firmware management service message. An identifier; a management unit configured to perform firmware management on the M2M terminal for the application entity according to the identifier.
  • the foregoing Internet of Things domain includes: a public Internet of Things domain and other Internet of Things domains.
  • the management unit may be configured to perform firmware management on the M2M terminal in the underlying network service entity of the underlying network according to the underlying network identifier of the underlying network of the public IoT domain; or set to other based on other IoT domains IoT identifier for firmware management of M2M terminals in other IoT domains for application entities.
  • the management module 304 is further configured to provide a service for the terminal firmware management service message, where the service includes at least one of the following: an authorization service and a billing service.
  • the management module 304 may include: an adaptation unit configured to perform protocol adaptation on the terminal firmware management service message; and a management unit configured to perform the M2M terminal according to the adapted protocol.
  • Firmware management configured to perform protocol adaptation on the terminal firmware management service message; and a management unit configured to perform the M2M terminal according to the adapted protocol.
  • the foregoing protocol includes but is not limited to at least one of the following: Extensible Messaging and Presentation Protocol (XMPP), Message Queuing Telemetry Transmission (MQTT), Open Mobile Alliance Terminal Management Protocol (OMA DM), broadband forum client device WAN Management Protocol Series Specification (BBF CWMP), Open Mobile Alliance's Lightweight Machine to Machine Protocol (OMA LightweightM2M).
  • XMPP Extensible Messaging and Presentation Protocol
  • MQTT Message Queuing Telemetry Transmission
  • OMA DM Open Mobile Alliance Terminal Management Protocol
  • BBF CWMP broadband forum client device WAN Management Protocol Series Specification
  • OMA LightweightM2M Open Mobile Alliance's Lightweight Machine to Machine Protocol
  • a universal service entity is provided, which is located in a public Internet of Things domain, and includes any of the foregoing devices in the embodiments of the present invention.
  • a public Internet of Things device including any of the foregoing devices in the embodiments of the present invention.
  • the public IoT device can be an M2M terminal, an M2M gateway, and other devices in the Internet of Things, or a basic telecommunications device.
  • the public IoT device comprises a processor and a storage device
  • the storage device may store a program unit having the function of the device of the embodiment of the present invention
  • the processor may execute the program unit.
  • the layered model in the M2M network mainly includes an application layer, a general service layer, and an underlying network service layer
  • the corresponding functional architecture mainly includes an application entity, a general service entity, and an underlying network service. entity.
  • the application entity provides application logic of the end-to-end solution, which can be located in the M2M terminal, the M2M gateway, and the M2M server.
  • the general service entity provides the general service function of the M2M environment and can be located in the M2M terminal, the M2M gateway, and the M2M server.
  • the underlying network service entity provides services to the generic service entity.
  • the constrained M2M terminal does not include a generic service entity.
  • the M2M network in this preferred embodiment is based on a service oriented architecture.
  • a service is a mechanism that grants access to one or more functions or methods, accessing the specified interface and maintaining consistency with the constraints and policies of the service description.
  • the M2M network based on the service oriented architecture can be applied to the infrastructure domain of the public IoT service provider, wherein the general service entity can be regarded as a set of service components, and the general service entity provides a service execution environment for the M2M application.
  • the infrastructure domain of the public Internet of Things service provider includes an application entity and a general service entity (also referred to as an M2M service execution environment.
  • a general service entity also referred to as an M2M service execution environment.
  • the M2M server is equivalent to the M2M service. Publishing platform), the underlying network service entity.
  • the generic service entity includes at least one of the following service components: a service exposure component 10, a terminal management component 20, a service subscription component 30, a billing component 40, a network service utilization component 50, an infrastructure component 60, and a remote service exposure component 70. .
  • a service exposure component 10 a service exposure component 10
  • a terminal management component 20 a service subscription component 20
  • a billing component 40 a billing component 40
  • a network service utilization component 50 a network service utilization component 50
  • an infrastructure component 60 an infrastructure component 60
  • a remote service exposure component 70 a remote service exposure component
  • the service exposure component 10 is configured to expose services to the application entity.
  • the service exposure component 10 of the preferred embodiment is equivalent to the receiving module 302 of the above-described embodiments of the present invention, and a preferred embodiment of the service exposure component 10 is described below.
  • the component includes: a receiving module 12 configured to receive a terminal firmware management service message from an application entity; and a sending module 14 configured to The application entity sends a response or notification or callback.
  • the receiving module 12 includes one of the following units: a publish message receiving unit 122, a subscription message receiving unit 124, and a request message receiving unit 126.
  • the publishing message receiving module 122 is configured to receive the publishing terminal firmware management service message message from the application entity.
  • the subscription message receiving unit 124 is configured to receive a subscription terminal management event message from the application entity.
  • the request message receiving unit 126 is configured to receive a terminal firmware management service message request message from the application entity.
  • the sending module 14 includes one of the following modules: a notification message transmitting unit 142, a response message transmitting unit 144, and a callback message transmitting unit 146.
  • the notification message sending module 142 is configured to send a terminal management event notification message to the application entity.
  • the response message sending unit 144 is configured to send the terminal solid to the application entity.
  • the callback message sending unit 146 is configured to call back the processing result of the terminal firmware management to the application entity.
  • the terminal management component 20 which is equivalent to the management module 304 of the embodiment of the present invention, is configured to provide one of the following services: a terminal management service service, and a terminal management adaptation service.
  • the terminal management service service implements the service logic of the terminal management.
  • the terminal management adaptation service maintains a mapping relationship between the M2M external identifier and/or the M2M terminal identifier and the underlying network identifier or other domain service provider identifier, and identifies the protocol supported by the terminal according to the underlying network identifier or other domain service provider identifier. Adaptation of the protocol supporting the terminal firmware management service message.
  • the service ordering component 30 is configured to provide a subscription service and maintain a service subscription relationship.
  • the accounting component 40 is configured to provide billing and billing services.
  • the network service utilization component 50 is configured to use the services of the underlying network service entity.
  • the infrastructure component 60 provides utility services, including one of the following services: security, authorization, authentication, and the like.
  • the remote service exposure component 70 is configured to connect external services from other M2M environments.
  • Other M2M environments can be at least one of the following: private Internet of Things, community Internet of Things, industry Internet of Things, and the like.
  • the service components in the general service entity implement communication through the WEB service mode, and the specific technology can adopt the service bus.
  • FIG. 6 is a flowchart of a preferred firmware management method for an Internet of Things terminal according to an embodiment of the present invention. As shown in FIG. 6, the method includes steps S602 to S604.
  • Step S602 The universal service entity receives the terminal firmware management service message from the application entity.
  • the information carried by the terminal firmware management service message includes: an M2M request identifier, an M2M request initiator, an M2M terminal identifier, an M2M service identifier, an M2M external identifier, an application identifier, a service subscription identifier, and an M2M terminal.
  • Information M2M group information, scheduling information, etc.
  • the M2M request identifier is set to identify the message request information.
  • the M2M request initiator is set to identify the originating object, and the originating object may be one of the following: an individual, a gateway, a server, an application, a service, a service component, and the like.
  • the M2M terminal identifier is set to identify the M2M terminal.
  • the M2M service identifier is set to identify the M2M service, which in the preferred embodiment is a terminal management service or a terminal firmware management service.
  • the M2M external identifier is set to the M2M service provider identity external network domain, including the underlying network or other Internet of Things/service provider.
  • the application identifier is set to identify the application entity.
  • the service subscription identifier is set to the subscription relationship between the M2M service provider binding application, the M2M terminal, the service, and the general service entity.
  • the M2M terminal information includes management information of the M2M terminal, and includes the following One: management object, management command, terminal capability, terminal tag, terminal type, terminal model.
  • the M2M group information includes one of the following: group name, number of members, member list, member type, group policy, and member access control rights.
  • the scheduling information includes one of the following: a scheduling time period, a scheduling repetition period.
  • Step S604 The universal service entity performs firmware management on the terminal of the other M2M environment or the underlying network for the application entity according to the terminal firmware management service message.
  • the terminal firmware management service message uses the following message exchange mode to refer to the foregoing mode of the embodiment of the present invention, and details thereof are not described herein again.
  • the terminal firmware management service message corresponds to one of the following service operations or service capabilities: obtaining terminal firmware image information, downloading terminal image firmware, installing terminal image firmware, downloading and installing terminal firmware image, deleting terminal firmware image, and the like.
  • the general service entity performs firmware management on the terminal for the application entity according to the terminal firmware management service message, and the general service entity obtains the underlying network identifier or other according to one or a combination of the M2M external identifier and the M2M terminal identifier.
  • a domain service provider identifier (completed by the terminal management component of the generic service entity) and firmware management of the terminal in the underlying network service entity (via the network service utilization component) according to the underlying network identifier; or the generic service entity according to other domains
  • the service provider identifier implemented by the remote service exposure component, performs firmware management on terminals in other M2M environments.
  • the general service entity performs firmware management on the terminal for the application entity according to the terminal firmware management service message.
  • the universal service entity provides one of the following services for the terminal firmware management service message: an authorization service and a billing service.
  • the general service entity performs firmware management on the terminal for the application entity according to the terminal firmware management service message, including: the universal service entity performs protocol adaptation according to the terminal firmware management service message, and includes one of the following protocols: XMPP (extensible Message and Presentation Protocol), MQTT (Message Queue Telemetry Transport), OMA DM (Open Mobile Alliance Terminal Management Protocol), BBF CWMP (Broadband Forum Client Device WAN Management Protocol Series Specification), OMA LightweightM2M (Open Mobile Alliance Light Volume machine to machine protocol) and so on.
  • XMPP extensible Message and Presentation Protocol
  • MQTT Message Queue Telemetry Transport
  • OMA DM Open Mobile Alliance Terminal Management Protocol
  • BBF CWMP Broadband Forum Client Device WAN Management Protocol Series Specification
  • OMA LightweightM2M Open Mobile Alliance Light Volume machine to machine protocol
  • the XMPP protocol adapts the terminal firmware management service message, and includes one of the following messages: acquiring a terminal firmware information service operation mapping to XMPP acquisition node information related operations (including acquiring a node, acquiring a node parameter, acquiring a node command, etc.)
  • the download terminal firmware service operation maps to an XMPP execution node command (parameters include download terminal firmware operations supported by the execution terminal), and the installation terminal firmware service operation maps to an XMPP execution node command (parameters include installation terminal firmware operations supported by the execution terminal), and downloads And install the terminal firmware service
  • the operation maps to the XMPP execution node command (parameters include downloading and installing terminal firmware operations supported by the terminal).
  • the MQTT protocol adapts the terminal firmware management service message, including one of the following messages: obtaining a terminal firmware information service operation mapping into an MQTT publishing message (parameters include obtaining terminal firmware information operations), and downloading a terminal firmware service operation mapping to MQTT publishes messages (parameters include download terminal firmware operations), installs terminal firmware service operations maps to MQTT publish messages (parameters include install terminal firmware operations), downloads and installs terminal firmware service operations maps to MQTT publish messages (parameters include downloading and installing terminals) Firmware operation), MQTT subscription message (subscribing to terminal management event), MQTT notification message (notifying terminal management event), etc.
  • the OMA DM protocol adapts the terminal firmware management service message, including one of the following messages: obtaining a terminal firmware information service operation mapping into an OMA DM command (firmware update management object-acquisition status), downloading a terminal firmware service operation mapping For OMA DM commands (firmware update management object - download), install terminal firmware service operations mapped to OMA DM commands (firmware update management object - update), download and install terminal firmware service operations mapped to OMA DM commands (firmware update management object - Download and update) and so on.
  • FIG. 7 is a schematic flowchart of a firmware management method of a preferred Internet of Things terminal according to an embodiment of the present invention. As shown in FIG. 7, the method includes steps S702 to S716.
  • Step S702 the application entity sends a terminal firmware management service message to the service exposure component 10 of the universal service entity.
  • the terminal firmware management service message includes one of the following parameters: M2M request identifier, initiator, M2M terminal identifier, M2M service identifier, M2M external identifier, application identifier, service subscription identifier, M2M terminal information , M2M group information, scheduling information, and so on.
  • the message exchange mode may be one of the following: a publish subscription mode, a request response mode, a one-way request mode, a request callback mode, a request, and a multiple response mode.
  • the terminal firmware management service message corresponding to the service operation or service capability may be one of the following: obtaining terminal firmware image information, downloading the terminal firmware image, installing the terminal firmware image, downloading and installing the terminal firmware image, deleting the terminal firmware image, and the like.
  • Step S704 the service exposure component 10 of the universal service entity forwards the terminal firmware management service message to the terminal management component 20.
  • Step S706 the terminal management component 20 of the general service entity sends a verification service message to the service subscription component 30.
  • the verification service message contains one of the following parameters: a service identifier, a service subscription identifier, and the like.
  • Step S708 the terminal management component 20 of the generic service entity sends an authorization service operation message to the infrastructure component 60.
  • the authorization service operation message includes one of the following parameters: a service identifier, a service subscription identifier, and the like.
  • step S710 the infrastructure component 60 of the generic service entity sends an acquisition authorization to the service subscription component 30.
  • the acquisition authorization includes one of the following parameters: an initiator, an application identifier, a service identifier, a service subscription identifier, etc.; and obtains corresponding authorization information, and then returns an authorized service operation or service capability to the terminal management component.
  • Step S712 the terminal management component 20 of the universal service entity sends a terminal firmware management service message to the remote service exposure component 70 or the network service utilization component 50.
  • the terminal firmware management service message includes one of the following parameters: an M2M request identifier, an M2M terminal identifier, another domain service provider identifier or an underlying network identifier, a service subscription identifier, an application identifier, M2M terminal information, M2M group information, scheduling information, and the like.
  • Step S714 the remote service exposure component 70 or the network service utilization component 50 of the generic service entity invokes other Internet of Things domains or the underlying network.
  • step S716 the other Internet of Things domain or the underlying network transmits the processing result event record of the terminal firmware management service to the accounting component 40 through the remote service exposure component 70 or the network service utilization component 50 of the general service entity.
  • the terminal firmware management service message may contain firmware management for multiple terminals or implement firmware management of the terminal according to scheduling
  • the generic service entity returns to the application entity in various forms, including responses or notifications or callbacks.
  • the embodiment of the present invention achieves the following technical effects: solving the unified management problem of the public Internet of Things and other Internet of Things M2M terminals, and realizing the M2M terminal for the public Internet of Things and other Internet of Things. Unified management.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across multiple computing devices.
  • they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from this
  • the steps shown or described are performed sequentially, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated into a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the firmware management method, apparatus, and general service entity of the Internet of Things terminal provided by the embodiments of the present invention have the following beneficial effects: solving the unified management problem of the public Internet of Things and other Internet of Things M2M terminals, and realizing the public ownership Unified management of M2M terminals for the Internet of Things and other Internet of Things.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本发明公开了一种物联网终端的固件管理方法、装置及通用服务实体，其中，物联网终端的固件管理方法包括：接收来自应用实体的终端固件管理服务报文；根据终端固件管理服务报文为应用实体，对公有物联网域的M2M终端和/或其他物联网域的M2M终端进行固件管理。通过本发明，解决了公有物联网和其他物联网的M2M终端的统一管理问题，实现了对公有物联网和其他物联网的M2M终端的统一管理。

Description

物联网终端的固件管理方法、装置及通用服务实体 技术领域
本发明涉及通信领域，具体而言，涉及一种物联网终端的固件管理方法、装置及通用服务实体。
背景技术
物联网是新一代信息技术的重要组成部分，其英文名称是：“The Internet of things”。顾名思义，物联网就是物与物相连的互联网。国际电信联盟(International telecommunication union，简称为ITU)发布的ITU互联网报告，对物联网做了如下定义：通过二维码识别设备、射频识别(Radio Frequency Identification，简称为RFID)装置、红外感应器、全球定位系统和激光扫描器等信息传感设备，按约定的协议，把任何物品与互联网相连接，进行信息交换和通信，以实现智能化识别、定位、跟踪、监控和管理的一种网络。
物联网中经常会引入一个M2M的概念，可以解释成为人到人(Man to Man)、人到机器(Man to Machine)、机器到机器(Machine to Machine)。从本质上而言，在人与机器、机器与机器的交互，大部分是为了实现人与人之间的信息交互。M2M网络是物联网现阶段的主要表现形式，M2M网络包括机器到机器通信网络、人与机器通信网络以及机器与人通信网络。M2M网络的设备主要包括M2M终端、M2M网关、M2M服务器。
图1是根据相关技术的物联网系统的示意图，如图1所示，物联网可以分类为私有物联网(一般面向单一机构内部提供服务)，公有物联网(基于互联网向公众或大型用户群体提供服务)，社区物联网(向一个关联的“社区”或机构群体提供服务)等。同时现阶段物联网在不同行业有大量的应用，包括智能农业、智能电网、智能交通、智能物流、智能医疗、智能家居等等。特别的是，这些行业都各自部署其专业物联网包括相应的专业物联网/M2M设备如终端、网关以及服务器等平台设备。
电信运营商作为公共通讯服务的提供商，在其提供物联网/M2M服务时也是作为公有物联网服务商的角色。针对私有物联网、社区物联网以及各行业的专业物联网的终端，现阶段电信运营商作为公有物联网服务商缺乏有效技术手段实施统一终端管理并实现服务。
发明内容
针对电信运营商作为公有物联网服务商无法对公有物联网和其他物联网域的终端统一管理的问题，本发明实施例提供了一种物联网终端的固件管理方法、装置及通用服务实体，以至少解决上述问题。
根据本发明的一个实施例，提供了一种物联网终端的固件管理方法，包括：接收来自应用实体的终端固件管理服务报文；根据所述终端固件管理服务报文为所述应用实体，对公有物联网域的M2M终端和/或其他物联网域的M2M终端进行固件管理。
所述终端固件管理服务报文携带的信息包括以下至少之一：M2M请求标识符、M2M请求发起者、M2M终端标识符、M2M服务标识符、M2M外部标识符、应用标识符、服务订购标识符、M2M终端信息、M2M群组信息、调度安排信息。
所述终端固件管理服务报文使用的消息交换模式包括以下至少之一：发布订阅模式，包括：接收来自所述应用实体的订阅终端管理事件消息，根据所述应用实体的发布终端固件管理消息对M2M终端进行固件管理，向所述应用实体返回终端管理事件通知消息；请求响应模式，包括：接收来自所述应用实体的终端固件管理服务报文请求消息，向所述应用实体返回终端固件管理服务报文响应消息；单向请求模式，包括：接收来自所述应用实体的终端固件管理服务报文请求消息；请求和多次响应模式，包括：接收来自所述应用实体的终端固件管理服务报文请求消息，多次向所述应用实体返回终端固件管理服务报文响应消息；所述请求回调模式，包括：接收来自所述应用实体的终端固件管理服务报文请求消息，向所述应用实体回调终端固件管理的处理结果。
所述终端固件管理服务报文对应的服务操作或服务能力包括以下至少之一：获取终端固件镜像信息、下载终端固件镜像、安装终端固件镜像、下载并安装终端固件镜像、删除终端固件镜像。
根据终端固件管理服务报文为所述应用实体对公有物联网域的M2M终端和/或其他物联网域的M2M终端进行固件管理包括：根据所述终端固件管理服务报文携带的M2M外部标识符和/或M2M终端标识符，获取M2M终端所在物联网域的标识符；根据所述标识符为所述应用实体对M2M终端进行固件管理。
所述物联网域包括：所述公有物联网域、所述其他物联网域；根据所述标识符为所述应用实体对M2M终端进行固件管理包括：根据所述公有物联网域的底层网络的底层网络标识符，为所述应用实体对所述底层网络的底层网络服务实体中的M2M终 端进行固件管理；或者，根据所述其他物联网域的其他物联网标识符，为所述应用实体对所述其他物联网域中的M2M终端进行固件管理。
根据所述终端固件管理服务报文为所述应用实体对公有物联网域的M2M终端和/或其他物联网域的M2M终端进行固件管理包括：为所述终端固件管理服务报文提供服务，其中所述服务包括以下至少之一：授权服务、记账服务。
根据所述终端固件管理服务报文为所述应用实体对公有物联网域的M2M终端和/或其他物联网域的M2M终端进行固件管理包括：对所述终端固件管理服务报文进行协议适配；根据适配得到的协议对M2M终端进行固件管理。
所述协议包括以下至少之一：可扩展消息和呈现协议XMPP、消息队列遥测传输MQTT、开放移动联盟的终端管理协议OMA DM、宽带论坛的客户端设备广域网管理协议系列规范BBF CWMP、开放移动联盟的轻量级机器到机器协议OMA LightweightM2M。
根据本发明的另一实施例，提供了一种物联网终端的固件管理装置，包括：接收模块，设置为接收来自应用实体的终端固件管理服务报文；管理模块，设置为根据所述终端固件管理服务报文为所述应用实体，对公有物联网域的M2M终端和/或其他物联网域的M2M终端进行固件管理。
所述终端固件管理服务报文携带的信息包括以下至少之一：M2M请求标识符、M2M请求发起者、M2M终端标识符、M2M服务标识符、M2M外部标识符、应用标识符、服务订购标识符、M2M终端信息、M2M群组信息、调度安排信息。
所述终端固件管理服务报文使用的消息交换模式包括以下至少之一：发布订阅模式，包括：接收来自所述应用实体的订阅终端管理事件消息，根据所述应用实体的发布终端固件管理消息对M2M终端进行固件管理，向所述应用实体返回终端管理事件通知消息；请求响应模式，包括：接收来自所述应用实体的终端固件管理服务报文请求消息，向所述应用实体返回终端固件管理服务报文响应消息；单向请求模式，包括：接收来自所述应用实体的终端固件管理服务报文请求消息；请求和多次响应模式，包括：接收来自所述应用实体的终端固件管理服务报文请求消息，多次向所述应用实体返回终端固件管理服务报文响应消息；所述请求回调模式，包括：接收来自所述应用实体的终端固件管理服务报文请求消息，向所述应用实体回调终端固件管理的处理结果。
所述终端固件管理服务报文对应的服务操作或服务能力包括以下至少之一：获取终端固件镜像信息、下载终端固件镜像、安装终端固件镜像、下载并安装终端固件镜像、删除终端固件镜像。
所述管理模块包括：获取单元，设置为根据所述终端固件管理服务报文携带的M2M外部标识符和/或M2M终端标识符，获取M2M终端所在物联网域的标识符；管理单元，设置为根据所述标识符为所述应用实体对M2M终端进行固件管理。
所述物联网域包括：所述公有物联网域、所述其他物联网域；所述管理单元，设置为根据所述公有物联网域的底层网络的底层网络标识符，为所述应用实体对所述底层网络的底层网络服务实体中的M2M终端进行固件管理；或者设置为根据所述其他物联网域的其他物联网标识符，为所述应用实体对所述其他物联网域中的M2M终端进行固件管理。
所述管理模块，还设置为为所述终端固件管理服务报文提供服务，其中所述服务包括以下至少之一：授权服务、记账服务。
所述管理模块包括：适配单元，设置为对所述终端固件管理服务报文进行协议适配；管理单元，设置为根据适配得到的协议对M2M终端进行固件管理。
根据本发明的另一实施例，提供了一种公有物联网设备，包括上述任一装置。
根据本发明的另一实施例，提供了一种通用服务实体，位于公有物联网域，包括上述任一装置。
通过本发明实施例，接收来自应用实体的终端固件管理服务报文，根据终端固件管理服务报文为应用实体，对公有物联网域的M2M终端和/或其他物联网域的M2M终端进行固件管理，解决了公有物联网和其他物联网的M2M终端的统一管理问题，实现了对公有物联网和其他物联网的M2M终端的统一管理。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是根据相关技术的物联网系统的示意图；
图2是根据本发明实施例的物联网终端的固件管理方法的流程图；
图3是根据本发明实施例的物联网终端的固件管理装置的结构框图；
图4是根据发明实施例优选的M2M网络的示意图；
图5是根据本发明优选的服务暴露组件的结构框图；
图6是根据本发明实施例优选的物联网终端的固件管理方法的流程图；以及
图7是根据本发明实施例优选的物联网终端的固件管理方法的流程示意图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
在以下实施例中，M2M终端可以是移动终端(例如，手机、平板电脑等)，也可以是其他类型的终端，只要其能够接入到物联网即可。终端上运行的操作系统也而已是各种类型的系统，例如，目前被广泛使用的安卓系统，或者是Windows操作系统、iOS系统等，但是并不限于此。设备可以是服务器、各类网关，也可以是其他类型的设备。
该终端或设备可以包括存储介质，存储介质中存储的程序单元可以用来执行以下实施例中所描述的方法。该终端或设备还可以包括处理器，该处理器可以设置为执行上述程序单元。可以预料的是，以下所描述的方法或者装置可以通过程序单元来实现。
在以下实施例中，下述的其他物联网域可以是面向单一机构内部提供服务的私有物联网，其他公有物联网、社区物联网。同时，也可以是物联网在不同行业有大量的应用，包括智能农业、智能电网、智能交通、智能物流、智能医疗、智能家居等。
根据本发明实施例，提供了一种物联网终端的固件管理方法。
图2是根据本发明实施例的物联网终端的固件管理方法的流程图，如图2所示，该方法包括步骤S202至步骤S204。
步骤S202，接收来自应用实体的终端固件管理服务报文。
步骤S204，根据终端固件管理服务报文为应用实体，对公有物联网域的M2M终端和/或其他物联网域的M2M终端进行固件管理。
通过本发明实施例，解决了公有物联网和其他物联网的M2M终端的统一管理问题，实现了对公有物联网和其他物联网的M2M终端的统一管理。
在本发明实施例的一个实施方式中，优选地，终端固件管理服务报文携带的信息至少包括以下之一或任意组合：M2M请求标识符、M2M请求发起者、M2M终端标识符、M2M服务标识符、M2M外部标识符、应用标识符、服务订购标识符、M2M终端信息、M2M群组信息、调度安排信息。
在本发明实施例的一个实施方式中，终端固件管理服务报文使用的消息交换模式包括但不限于以下至少之一：
(1)发布订阅模式，包括：接收来自应用实体的订阅终端管理事件消息，根据应用实体的发布终端固件管理消息对M2M终端进行固件管理，向应用实体返回终端管理事件通知消息。
(2)请求响应模式，包括：接收来自应用实体的终端固件管理服务报文请求消息，向应用实体返回终端固件管理服务报文响应消息。
(3)单向请求模式，包括：接收来自应用实体的终端固件管理服务报文请求消息。
(4)请求和多次响应模式，包括：接收来自应用实体的终端固件管理服务报文请求消息，多次向应用实体返回终端固件管理服务报文响应消息。
(5)请求回调模式，包括：接收来自应用实体的终端固件管理服务报文请求消息，向应用实体回调终端固件管理的处理结果。
在本发明实施例的一个实施方式中，终端固件管理服务报文对应的服务操作或服务能力包括但不限于以下至少之一：获取终端固件镜像信息、下载终端固件镜像、安装终端固件镜像、下载并安装终端固件镜像、删除终端固件镜像。
通过终端固件管理报文，可以实现上述的服务操作或服务能力。在实际应用中，可以在报文中携带相应的指令，通过执行指令进行固件管理。例如，下载终端固件镜像、下载并安装终端固件镜像等。
在本发明实施例的一个实施方式中，根据终端固件管理服务报文为应用实体，对公有物联网域的M2M终端和/或其他物联网域的M2M终端进行固件管理可以包括：根据终端固件管理服务报文携带的M2M外部标识符和/或M2M终端标识符，获取 M2M终端所在物联网域的标识符；根据该标识符为应用实体对M2M终端进行固件管理。
在本发明实施例的一个优选实施方式中，物联网域包括：公有物联网域、其他物联网域。优选地，根据标识符为应用实体对M2M终端进行固件管理包括：根据公有物联网域的底层网络的底层网络标识符，为应用实体对底层网络的底层网络服务实体中的M2M终端进行固件管理；或者，根据其他物联网域的其他物联网标识符，为应用实体对其他物联网域中的M2M终端进行固件管理。
在本发明实施例的一个实施方式中，根据终端固件管理服务报文为应用实体，对公有物联网域的M2M终端和/或其他物联网域的M2M终端进行固件管理包括：为终端固件管理服务报文提供服务，其中该服务包括但不限于以下至少之一：授权服务、记账服务。
优选地，授权服务，设置为提供向请求者授权可以使用的服务能力或操作，包括以下至少一种服务能力或操作：授权服务能力或操作。
优选地，记账服务包括以下至少一种服务能力或操作：启动事件收集、停止事件收集、统计收集。
在本发明实施例的一个优选实施方式中，根据终端固件管理服务报文为应用实体对公有物联网域的M2M终端和/或其他物联网域的M2M终端进行固件管理包括：对终端固件管理服务报文进行协议适配；根据适配得到的协议对M2M终端进行固件管理。
优选地，上述协议包括但不限于以下至少之一：可扩展消息和呈现协议(XMPP)、消息队列遥测传输(MQTT)、开放移动联盟的终端管理协议(OMA DM)、宽带论坛的客户端设备广域网管理协议系列规范(BBF CWMP)、开放移动联盟的轻量级机器到机器协议(OMA LightweightM2M)。
根据本发明实施例，提供了一种物联网终端的固件管理装置，用以实现本发明实施例的上述方法。
图3是根据本发明实施例的物联网终端的固件管理装置的结构框图，如图3所示，该装置包括：接收模块302和管理模块304，其中，接收模块302，设置为接收来自应用实体的终端固件管理服务报文；管理模块304，与接收模块302相连接，设置为根 据终端固件管理服务报文为应用实体，对公有物联网域的M2M终端和/或其他物联网域的M2M终端进行固件管理。
通过本发明实施例，解决了公有物联网和其他物联网的M2M终端的统一管理问题，实现了对公有物联网和其他物联网的M2M终端的统一管理。
在本发明实施例的一个实施方式中，终端固件管理服务报文携带的信息包括以下至少之一：M2M请求标识符、M2M请求发起者、M2M终端标识符、M2M服务标识符、M2M外部标识符、应用标识符、服务订购标识符、M2M终端信息、M2M群组信息、调度安排信息。
在本发明实施例的一个实施方式中，终端固件管理服务报文使用的消息交换模式包括但不限于以下至少之一：
(1)发布订阅模式，包括：接收来自应用实体的订阅终端管理事件消息，根据应用实体的发布终端固件管理消息对M2M终端进行固件管理，向应用实体返回终端管理事件通知消息。
(2)请求响应模式，包括：接收来自应用实体的终端固件管理服务报文请求消息，向应用实体返回终端固件管理服务报文响应消息。
(3)单向请求模式，包括：接收来自应用实体的终端固件管理服务报文请求消息。
(4)请求和多次响应模式，包括：接收来自应用实体的终端固件管理服务报文请求消息，多次向应用实体返回终端固件管理服务报文响应消息。
(5)请求回调模式，包括：接收来自应用实体的终端固件管理服务报文请求消息，向应用实体回调终端固件管理的处理结果。
基于上述优选的消息交互模式，接收模块302可以在上述各个模式下接收消息。
在本发明实施例的一个实施方式中，终端固件管理服务报文对应的服务操作或服务能力包括以下至少之一：获取终端固件镜像信息、下载终端固件镜像、安装终端固件镜像、下载并安装终端固件镜像、删除终端固件镜像。
优选地，上述的服务操作或服务能力可以作为指令或信息携带在上述终端固件管理服务报文中，管理模块304可以根据上述指令或信息对M2M终端进行固件管理。
在本发明实施例的一个实施方式中，管理模块304可以包括：获取单元，设置为根据终端固件管理服务报文携带的M2M外部标识符和/或M2M终端标识符，获取M2M终端所在物联网域的标识符；管理单元，设置为根据该标识符为应用实体对M2M终端进行固件管理。
在本发明实施例的一个优选实施方式中，上述物联网域包括：公有物联网域、其他物联网域。管理单元，可以设置为根据公有物联网域的底层网络的底层网络标识符，为应用实体对该底层网络的底层网络服务实体中的M2M终端进行固件管理；或者设置为根据其他物联网域的其他物联网标识符，为应用实体对其他物联网域中的M2M终端进行固件管理。
在本发明实施例的一个优选实施方式中，管理模块304，还设置为为终端固件管理服务报文提供服务，该服务包括以下至少之一：授权服务、记账服务。
在本发明实施例的一个实施方式中，管理模块304可以包括：适配单元，设置为对终端固件管理服务报文进行协议适配；管理单元，设置为根据适配得到的协议对M2M终端进行固件管理。
优选地，上述协议包括但不限于以下至少之一：可扩展消息和呈现协议(XMPP)、消息队列遥测传输(MQTT)、开放移动联盟的终端管理协议(OMA DM)、宽带论坛的客户端设备广域网管理协议系列规范(BBF CWMP)、开放移动联盟的轻量级机器到机器协议(OMA LightweightM2M)。
根据本发明实施例，提供了一种通用服务实体，位于公有物联网域，包括本发明实施例上述任一装置。
根据本发明实施例，提供了一种公有物联网设备，包括本发明实施例上述任一装置。该公有物联网设备可以是M2M终端、M2M网关，以及物联网中的其他设备，或者基础的电信设备。
优选地，上述公有物联网设备包括处理器以及存储装置，存储装置可以存储具备本发明实施例的上述装置的功能的程序单元，处理器可以执行该程序单元。
下面对本发明实施例的优选实施方式进行描述。
该优选实施方式中，如图4所示，在M2M网络的分层模型主要包括应用层、通用服务层、底层网络服务层，其对应的功能架构主要包括应用实体、通用服务实体、底层网络服务实体。
应用实体提供端到端方案的应用逻辑，可以位于M2M终端、M2M网关、M2M服务器中。通用服务实体提供M2M环境的通用服务功能，可以位于M2M终端、M2M网关、M2M服务器中。底层网络服务实体为通用服务实体提供服务。
优选地，受约束的M2M终端不包含通用服务实体。
该优选实施方式中的M2M网络基于面向服务架构。面向服务架构参考模型中，服务是一种授予访问一个或更多功能的权利或方法的机制，访问使用规定的接口并保持和服务描述的约束和策略相一致。基于面向服务架构的M2M网络可以适用于公有物联网服务商的基础设施域，其中通用服务实体可以认为是一组服务组件，通用服务实体为M2M应用提供了服务执行环境。
参照图4，公有物联网服务商的基础设施域包括应用实体、通用服务实体(也可称为M2M服务执行环境。特别的是通用服务实体处于网络服务侧时，其所在M2M服务器相当于M2M服务发布平台)、底层网络服务实体。
通用服务实体包括以下服务组件中的至少一种：服务暴露组件10、终端管理组件20、服务订阅组件30、记账组件40、网络服务利用组件50、基础设施组件60、远端服务暴露组件70。下面对上述各个组件进行描述。
服务暴露组件10，设置为向应用实体暴露服务。该优选实施方式的服务暴露组件10相当于本发明上述实施例中的接收模块302，下面对服务暴露组件10的优选实施方式进行描述。
图5是根据本发明实施例服务暴露组件的结构框图，如图5所示，该组件包括：接收模块12，设置为接收来自应用实体的终端固件管理服务报文；发送模块14，设置为向应用实体发送响应或通知或回调。
优选地，接收模块12包括以下单元之一：发布消息接收单元122、订阅消息接收单元124、请求消息接收单元126。其中，发布消息接收模块122，设置为接收来自应用实体的发布终端固件管理服务报文消息。订阅消息接收单元124，设置为接收来自应用实体的订阅终端管理事件消息。请求消息接收单元126，设置为接收来自应用实体的终端固件管理服务报文请求消息。
优选地，发送模块14包括以下模块之一：通知消息发送单元142、响应消息发送单元144、回调消息发送单元146。其中，通知消息发送模块142，设置为向应用实体发送终端管理事件通知消息。响应消息发送单元144，设置为向应用实体发送终端固 件管理服务报文响应消息。回调消息发送单元146，设置为向应用实体回调终端固件管理的处理结果。
终端管理组件20，相当于本发明实施例的管理模块304，设置为提供以下服务之一：终端管理业务服务、终端管理适配服务。终端管理业务服务实现终端管理的服务逻辑。终端管理适配服务维护M2M外部标识符和/或M2M终端标识符与底层网络标识符或其他域服务商标识符的映射关系，根据底层网络标识符或者其他域服务商标识符识别终端支持的协议，对终端固件管理服务报文进行支持的协议的适配。
服务订购组件30，设置为提供订购服务，维护服务订购关系。
记账组件40，设置为提供记账、计费服务。
网络服务利用组件50，设置为使用底层网络服务实体的服务。
基础设施组件60，提供效用服务，包括以下服务之一：安全、授权、认证等。
远端服务暴露组件70，设置为从其他M2M环境连接外部服务。其他M2M环境可以是以下至少一种：私有物联网、社区物联网、行业物联网等。
在实际应用中，通用服务实体中的服务组件通过WEB服务方式实现通讯，具体技术可以采用服务总线。
图6是根据本发明实施例优选的物联网终端的固件管理方法的流程图，如图6所示，该方法包括步骤S602至步骤S604。
步骤S602，通用服务实体接收来自应用实体的终端固件管理服务报文。
优选地，终端固件管理服务报文携带的信息包括：M2M请求标识符、M2M请求发起者、M2M终端标识符、M2M服务标识符、M2M外部标识符、应用标识符、服务订购标识符、M2M终端信息、M2M群组信息、调度安排信息等。
其中，M2M请求标识符设置为标识该报文请求信息。M2M请求发起者设置为标识发起对象，发起对象可以是以下之一：个人、网关、服务器、应用、服务、服务组件等。M2M终端标识符设置为标识M2M终端。M2M服务标识符设置为标识M2M服务，该优选实施方式中为终端管理服务或终端固件管理服务。M2M外部标识符设置为M2M服务商标识外部网络域，包括底层网络或其他物联网/服务商。应用标识符设置为标识应用实体。服务订购标识符设置为M2M服务商绑定应用、M2M终端、服务、通用服务实体之间的订购关系。M2M终端信息包含M2M终端的管理信息，包含以下 之一：管理对象、管理命令、终端能力、终端标签、终端类型、终端模型。M2M群组信息包含以下之一：群组名称、成员数、成员列表、成员类型、群组策略、成员访问控制权利。调度安排信息包含以下之一：调度时间周期、调度重复周期。
步骤S604，通用服务实体根据终端固件管理服务报文为应用实体对其他M2M环境或底层网络的终端进行固件管理。
优选地，所述终端固件管理服务报文使用以下消息交换模式参考本发明实施例前述的模式，其具体内容在此不再赘述。
优选地，终端固件管理服务报文对应以下服务操作或服务能力之一：获取终端固件镜像信息、下载终端镜像固件、安装终端镜像固件、下载并安装终端固件镜像、删除终端固件镜像等。
优选地，通用服务实体根据终端固件管理服务报文为应用实体对终端进行固件管理包括：通用服务实体根据M2M外部标识符和M2M终端标识符的组合或其中之一，得到底层网络标识符或其他域服务商标识符(由通用服务实体的终端管理组件完成)并根据底层网络标识符，(通过网络服务利用组件实现)对底层网络服务实体中的终端进行固件管理；或者通用服务实体根据其他域服务商标识符，(通过远端服务暴露组件实现)对其他M2M环境中的终端进行固件管理。
优选地，通用服务实体根据终端固件管理服务报文为应用实体对终端进行固件管理包括：通用服务实体为终端固件管理服务报文提供以下服务之一：授权服务、记账服务。
优选地，通用服务实体根据终端固件管理服务报文为应用实体对终端进行固件管理包括：通用服务实体根据所述终端固件管理服务报文进行协议适配，包括以下协议之一：XMPP(可扩展消息和呈现协议)、MQTT(消息队列遥测传输)、OMA DM(开放移动联盟的终端管理协议)、BBF CWMP(宽带论坛的客户端设备广域网管理协议系列规范)、OMA LightweightM2M(开放移动联盟的轻量级机器到机器协议)等。
进一步地，XMPP协议适配所述终端固件管理服务报文，包括以下消息之一：获取终端固件信息服务操作映射为XMPP获取节点信息相关操作(包括获取节点、获取节点参数、获取节点命令等)，下载终端固件服务操作映射为XMPP执行节点命令(参数包括执行终端支持的下载终端固件操作)，安装终端固件服务操作映射为XMPP执行节点命令(参数包括执行终端支持的安装终端固件操作)，下载并安装终端固件服务 操作映射为XMPP执行节点命令(参数包括执行终端支持的下载并安装终端固件操作)等。
进一步地，MQTT协议适配所述终端固件管理服务报文，包括以下消息之一：获取终端固件信息服务操作映射为MQTT发布消息(参数包括获取终端固件信息操作)，下载终端固件服务操作映射为MQTT发布消息(参数包括下载终端固件操作)，安装终端固件服务操作映射为MQTT发布消息(参数包括安装终端固件操作)，下载并安装终端固件服务操作映射为MQTT发布消息(参数包括下载并安装终端固件操作)，MQTT订阅消息(订阅终端管理事件)，MQTT通知消息(通知终端管理事件)等。
进一步地，OMA DM协议适配所述终端固件管理服务报文，包括以下消息之一：获取终端固件信息服务操作映射为OMA DM命令(固件更新管理对象－获取状态)，下载终端固件服务操作映射为OMA DM命令(固件更新管理对象－下载)，安装终端固件服务操作映射为OMA DM命令(固件更新管理对象－更新)，下载并安装终端固件服务操作映射为OMA DM命令(固件更新管理对象－下载并更新)等。
下面结合实例，对该优选实施方式进行详细描述，可以预见的是该优选实施方式并不限于下述的方法。
图7是根据本发明实施例优选的物联网终端的固件管理方法的流程示意图，如图7所示，该方法包括步骤S702至步骤S716。
步骤S702，应用实体向通用服务实体的服务暴露组件10发送终端固件管理服务报文。
优选地，终端固件管理服务报文包含以下参数之一：M2M请求标识符、发起者、M2M终端标识符、M2M服务标识符、M2M外部标识符、应用标识符、服务订购标识符、M2M终端信息、M2M群组信息、调度安排信息等。
优选地，消息交换模式可以是以下之一：发布订阅模式、请求响应模式、单向请求模式、请求回调模式、请求和多次响应模式。
优选地，终端固件管理服务报文对应服务操作或服务能力可以是以下之一：获取终端固件镜像信息、下载终端固件镜像、安装终端固件镜像、下载并安装终端固件镜像、删除终端固件镜像等。
步骤S704，通用服务实体的服务暴露组件10向终端管理组件20转发终端固件管理服务报文。
步骤S706、通用服务实体的终端管理组件20向服务订购组件30发送校验服务消息。
优选地，校验服务消息包含以下参数之一：服务标识符、服务订购标识符等。
步骤S708、通用服务实体的终端管理组件20向基础设施组件60发送授权服务操作消息。
优选地，授权服务操作消息包含以下参数之一：服务标识符、服务订购标识符等。
步骤S710，通用服务实体的基础设施组件60向服务订购组件30发送获取授权。
优选地，获取授权中包含以下参数之一：发起者、应用标识符、服务标识符、服务订购标识符等；并得到相应的授权信息，然后向终端管理组件返回授权的服务操作或服务能力。
步骤S712，通用服务实体的终端管理组件20向远端服务暴露组件70或网络服务利用组件50发送终端固件管理服务报文。
优选地，终端固件管理服务报文包含以下参数之一：M2M请求标识符、M2M终端标识符、其他域服务商标识符或底层网络标识符、服务订购标识符、应用标识符、M2M终端信息、M2M群组信息、调度安排信息等。
步骤S714，通用服务实体的远端服务暴露组件70或网络服务利用组件50调用其他物联网域或底层网络。
步骤S716，其他物联网域或底层网络通过通用服务实体的远端服务暴露组件70或网络服务利用组件50向记账组件40发送终端固件管理服务的处理结果事件记录。
由于终端固件管理服务报文可能包含对多个终端的固件管理或根据调度来实施对终端的固件管理，因此通用服务实体向应用实体返回存在多种形式，包括响应或通知或回调。
从以上的描述中，可以看出，本发明实施例实现了如下技术效果：解决了公有物联网和其他物联网的M2M终端的统一管理问题，实现了对公有物联网和其他物联网的M2M终端的统一管理。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所 组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
如上所述，本发明实施例提供的物联网终端的固件管理方法、装置及通用服务实体，具有以下有益效果：解决了公有物联网和其他物联网的M2M终端的统一管理问题，实现了对公有物联网和其他物联网的M2M终端的统一管理。

Claims (19)

  1. 一种物联网终端的固件管理方法，包括：
    接收来自应用实体的终端固件管理服务报文；
    根据所述终端固件管理服务报文为所述应用实体，对公有物联网域的M2M终端和/或其他物联网域的M2M终端进行固件管理。
  2. 根据权利要求1所述的方法，其中，所述终端固件管理服务报文携带的信息包括以下至少之一：M2M请求标识符、M2M请求发起者、M2M终端标识符、M2M服务标识符、M2M外部标识符、应用标识符、服务订购标识符、M2M终端信息、M2M群组信息、调度安排信息。
  3. 根据权利要求1所述的方法，其中，所述终端固件管理服务报文使用的消息交换模式包括以下至少之一：
    发布订阅模式，包括：接收来自所述应用实体的订阅终端管理事件消息，根据所述应用实体的发布终端固件管理消息对M2M终端进行固件管理，向所述应用实体返回终端管理事件通知消息；
    请求响应模式，包括：接收来自所述应用实体的终端固件管理服务报文请求消息，向所述应用实体返回终端固件管理服务报文响应消息；
    单向请求模式，包括：接收来自所述应用实体的终端固件管理服务报文请求消息；
    请求和多次响应模式，包括：接收来自所述应用实体的终端固件管理服务报文请求消息，多次向所述应用实体返回终端固件管理服务报文响应消息；
    请求回调模式，包括：接收来自所述应用实体的终端固件管理服务报文请求消息，向所述应用实体回调终端固件管理的处理结果。
  4. 根据权利要求1所述的方法，其中，所述终端固件管理服务报文对应的服务操作或服务能力包括以下至少之一：获取终端固件镜像信息、下载终端固件镜像、安装终端固件镜像、下载并安装终端固件镜像、删除终端固件镜像。
  5. 根据权利要求1所述的方法，其中，根据终端固件管理服务报文为所述应用实体对公有物联网域的M2M终端和/或其他物联网域的M2M终端进行固件管理包括：
    根据所述终端固件管理服务报文携带的M2M外部标识符和/或M2M终端标识符，获取M2M终端所在物联网域的标识符；
    根据所述标识符为所述应用实体对M2M终端进行固件管理。
  6. 根据权利要求5所述的方法，其中，所述物联网域包括：所述公有物联网域、所述其他物联网域；根据所述标识符为所述应用实体对M2M终端进行固件管理包括：
    根据所述公有物联网域的底层网络的底层网络标识符，为所述应用实体对所述底层网络的底层网络服务实体中的M2M终端进行固件管理；或者
    根据所述其他物联网域的其他物联网标识符，为所述应用实体对所述其他物联网域中的M2M终端进行固件管理。
  7. 根据权利要求1所述的方法，其中，根据所述终端固件管理服务报文为所述应用实体对公有物联网域的M2M终端和/或其他物联网域的M2M终端进行固件管理包括：
    为所述终端固件管理服务报文提供服务，其中所述服务包括以下至少之一：授权服务、记账服务。
  8. 根据权利要求1或7所述的方法，其中，根据所述终端固件管理服务报文为所述应用实体对公有物联网域的M2M终端和/或其他物联网域的M2M终端进行固件管理包括：
    对所述终端固件管理服务报文进行协议适配；
    根据适配得到的协议对M2M终端进行固件管理。
  9. 根据权利要求8所述的方法，其中，所述协议包括以下至少之一：可扩展消息和呈现协议XMPP、消息队列遥测传输MQTT、开放移动联盟的终端管理协议OMA DM、宽带论坛的客户端设备广域网管理协议系列规范BBF CWMP、开放移动联盟的轻量级机器到机器协议OMA LightweightM2M。
  10. 一种物联网终端的固件管理装置，包括：
    接收模块，设置为接收来自应用实体的终端固件管理服务报文；
    管理模块，设置为根据所述终端固件管理服务报文为所述应用实体，对公有物联网域的M2M终端和/或其他物联网域的M2M终端进行固件管理。
  11. 根据权利要求10所述的装置，其中，所述终端固件管理服务报文携带的信息包括以下至少之一：M2M请求标识符、M2M请求发起者、M2M终端标识符、M2M服务标识符、M2M外部标识符、应用标识符、服务订购标识符、M2M终端信息、M2M群组信息、调度安排信息。
  12. 根据权利要求10所述的装置，其中，所述终端固件管理服务报文使用的消息交换模式包括以下至少之一：
    发布订阅模式，包括：接收来自所述应用实体的订阅终端管理事件消息，根据所述应用实体的发布终端固件管理消息对M2M终端进行固件管理，向所述应用实体返回终端管理事件通知消息；
    请求响应模式，包括：接收来自所述应用实体的终端固件管理服务报文请求消息，向所述应用实体返回终端固件管理服务报文响应消息；
    单向请求模式，包括：接收来自所述应用实体的终端固件管理服务报文请求消息；
    请求和多次响应模式，包括：接收来自所述应用实体的终端固件管理服务报文请求消息，多次向所述应用实体返回终端固件管理服务报文响应消息；
    请求回调模式，包括：接收来自所述应用实体的终端固件管理服务报文请求消息，向所述应用实体回调终端固件管理的处理结果。
  13. 根据权利要求10所述的装置，其中，所述终端固件管理服务报文对应的服务操作或服务能力包括以下至少之一：获取终端固件镜像信息、下载终端固件镜像、安装终端固件镜像、下载并安装终端固件镜像、删除终端固件镜像。
  14. 根据权利要求10所述的装置，其中，所述管理模块，包括：
    获取单元，设置为根据所述终端固件管理服务报文携带的M2M外部标识符和/或M2M终端标识符，获取M2M终端所在物联网域的标识符；
    管理单元，设置为根据所述标识符为所述应用实体对M2M终端进行固件管理。
  15. 根据权利要求14所述的装置，其中，所述物联网域包括：所述公有物联网域、所述其他物联网域；所述管理单元，
    设置为根据所述公有物联网域的底层网络的底层网络标识符，为所述应用实体对所述底层网络的底层网络服务实体中的M2M终端进行固件管理；或者
    设置为根据所述其他物联网域的其他物联网标识符，为所述应用实体对所述其他物联网域中的M2M终端进行固件管理。
  16. 根据权利要求10所述的装置，其中，所述管理模块，还设置为为所述终端固件管理服务报文提供服务，其中所述服务包括以下至少之一：授权服务、记账服务。
  17. 根据权利要求10或16所述的装置，其中，所述管理模块包括：
    适配单元，设置为对所述终端固件管理服务报文进行协议适配；
    管理单元，设置为根据适配得到的协议对M2M终端进行固件管理。
  18. 一种公有物联网设备，包括：权利要求10至17中任一项所述的装置。
  19. 一种通用服务实体，位于公有物联网域，包括：权利要求10至17中任一项所述的装置。
PCT/CN2014/092974 2014-03-31 2014-12-03 物联网终端的固件管理方法、装置及通用服务实体 WO2015149531A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410127491.6A CN104954412B (zh) 2014-03-31 2014-03-31 物联网终端的固件管理方法、装置及通用服务实体
CN201410127491.6 2014-03-31

Publications (1)

Publication Number Publication Date
WO2015149531A1 true WO2015149531A1 (zh) 2015-10-08

Family

ID=54168763

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/092974 WO2015149531A1 (zh) 2014-03-31 2014-12-03 物联网终端的固件管理方法、装置及通用服务实体

Country Status (2)

Country Link
CN (1) CN104954412B (zh)
WO (1) WO2015149531A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017143238A1 (en) * 2016-02-19 2017-08-24 Atif Hussein Network architecture for internet-of-things device
CN110809262A (zh) * 2019-11-08 2020-02-18 杭州海兴电力科技股份有限公司 一种基于coap协议的物联网设备运维管理方法
US10809995B2 (en) 2016-02-19 2020-10-20 Intel Corporation Internet-of-things device blank
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

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108293062B (zh) * 2015-12-03 2021-08-24 瑞典爱立信有限公司 用于管理受限设备的方法和设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102291430A (zh) * 2011-06-28 2011-12-21 中国联合网络通信集团有限公司 物联网配置信息处理方法、物联网平台及系统
CN102801544A (zh) * 2011-05-25 2012-11-28 中兴通讯股份有限公司 一种物联网架构下统一终端管理的方法和系统
CN103227813A (zh) * 2013-03-21 2013-07-31 重庆电子工程职业学院 一种家庭物联网系统自动远程更新系统及方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102801544A (zh) * 2011-05-25 2012-11-28 中兴通讯股份有限公司 一种物联网架构下统一终端管理的方法和系统
CN102291430A (zh) * 2011-06-28 2011-12-21 中国联合网络通信集团有限公司 物联网配置信息处理方法、物联网平台及系统
CN103227813A (zh) * 2013-03-21 2013-07-31 重庆电子工程职业学院 一种家庭物联网系统自动远程更新系统及方法

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017143238A1 (en) * 2016-02-19 2017-08-24 Atif Hussein Network architecture for internet-of-things device
CN109479067A (zh) * 2016-02-19 2019-03-15 英特尔公司 用于物联网设备的网络架构
US10809995B2 (en) 2016-02-19 2020-10-20 Intel Corporation Internet-of-things device blank
US11146449B2 (en) 2016-02-19 2021-10-12 Intel Corporation Network architecture for internet-of-things device
CN109479067B (zh) * 2016-02-19 2022-01-07 英特尔公司 用于物联网设备的网络架构
US11269608B2 (en) 2016-02-19 2022-03-08 Intel Corporation Internet-of-things device blank
US11687331B2 (en) 2016-02-19 2023-06-27 Intel Corporation Internet-of-things device blank
CN110809262A (zh) * 2019-11-08 2020-02-18 杭州海兴电力科技股份有限公司 一种基于coap协议的物联网设备运维管理方法
CN110809262B (zh) * 2019-11-08 2023-09-01 杭州海兴电力科技股份有限公司 一种基于coap协议的物联网设备运维管理方法
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
US11310642B2 (en) 2020-02-26 2022-04-19 At&T Intellectual Property I, L.P. 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

Also Published As

Publication number Publication date
CN104954412A (zh) 2015-09-30
CN104954412B (zh) 2019-01-04

Similar Documents

Publication Publication Date Title
KR101964532B1 (ko) 복수의 디바이스들 상에서 복수의 명령들의 실행을 허용하는 것에 의해 강화되는, m2m 시스템에서의 서비스 레이어와 관리 레이어 사이의 동작들
WO2015149531A1 (zh) 物联网终端的固件管理方法、装置及通用服务实体
WO2016033987A1 (zh) 物联网的设备应用软件管理服务方法、装置及系统
CA2840511C (en) Systems, methods, and/or apparatus for enabling communication between devices using different communication protocols
US8117297B2 (en) System and method of device-to-server registration
EP3485656A1 (en) Subscription and notification service
KR101980475B1 (ko) M2m 서비스를 추가하기 위한 디바이스 및 방법
US20200326989A1 (en) Building pool-based m2m service layer through nfv
JP2018139144A (ja) サービスイネーブラ機能
EP2621243B1 (en) Method and system for configuring and managing third party software, and management server
US9425982B2 (en) Server and method for providing device management service and device receiving the device management service
KR101401799B1 (ko) 디바이스 관리 서비스를 브로드밴드 통신 모듈이 없는전자기기에 제공하는 시스템 및 방법
WO2015184879A1 (zh) 物联网的终端拓扑管理服务方法、装置及系统
US10750356B2 (en) Configuration management method, apparatus, and system for terminal in internet of things
WO2016033985A1 (zh) 物联网的设备故障排除服务方法、装置及系统
CN111164951B (zh) 基于服务能力要求和偏好的服务注册
WO2015149530A1 (zh) M2m应用服务方法、装置及系统
EP2987343A1 (en) Method and network node for managing device-related data and method and communication device for communicating with the network node
AU2014271225A1 (en) An integration system
KR20150000377A (ko) M2m 시스템에서 정보 제공을 선택적으로 제어하는 방법 및 장치

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14888105

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase
122 Ep: pct application non-entry in european phase

Ref document number: 14888105

Country of ref document: EP

Kind code of ref document: A1