WO2010127508A1 - 通过网关设备进行设备管理的方法、装置及设备管理服务器 - Google Patents

通过网关设备进行设备管理的方法、装置及设备管理服务器 Download PDF

Info

Publication number
WO2010127508A1
WO2010127508A1 PCT/CN2009/071711 CN2009071711W WO2010127508A1 WO 2010127508 A1 WO2010127508 A1 WO 2010127508A1 CN 2009071711 W CN2009071711 W CN 2009071711W WO 2010127508 A1 WO2010127508 A1 WO 2010127508A1
Authority
WO
WIPO (PCT)
Prior art keywords
gateway device
device management
terminal
gateway
address
Prior art date
Application number
PCT/CN2009/071711
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 华为技术有限公司
Priority to EP09844260A priority Critical patent/EP2421197A4/en
Priority to CN200980151721XA priority patent/CN102246464A/zh
Priority to PCT/CN2009/071711 priority patent/WO2010127508A1/zh
Publication of WO2010127508A1 publication Critical patent/WO2010127508A1/zh
Priority to US13/291,829 priority patent/US20120059924A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50Service provisioning or reconfiguring
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/45Network directories; Name-to-address mapping
    • H04L61/4557Directories for hybrid networks, e.g. including telephone numbers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00Indexing scheme associated with group H04L61/00
    • H04L2101/60Types of network addresses
    • H04L2101/618Details of network addresses
    • H04L2101/65Telephone numbers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5058Service discovery by the service manager

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method, an apparatus, and a device management server for device management through a gateway device. Background technique
  • 0MA Open Mobile Alliance
  • DM Device Management
  • the third party may be a DMA (Device Management Authority) such as a mobile operator, a service provider, or an information management department of the partner.
  • the DMA needs to establish a DM session between the DMS (Device Management Server) and the DMC (Device Management Client) when operating the terminal (Management Object). .
  • the DM session must be initiated by the DMC to initiate a connection request to the DMS using the pre-configured account, but cannot be initiated by the DMS. Therefore, when the network side needs to establish a DM session, the DMS needs to send a DM notification message to the DMC, triggering The DMC initiates a connection request to the DMS to establish a DM management session.
  • the current DM notification technology is only applicable to the case where the terminal address is fixed and directly reachable.
  • the DMS can use the wireless application protocol push technology to send the designated mobile phone number pre-configured in the DMS.
  • the DM notification message is implemented to send a DM notification message to the DMC on the designated mobile phone, thereby completing the DM notification process.
  • the user terminal may need to access the external network through the gateway device. Due to the address shielding effect of the gateway and the mobility of the terminal, for example, the terminal may change its belonging.
  • the network makes the DMS unable to perform device management (such as software/firmware upgrade, virus database update, etc.) on the terminal in time under the condition of the existing DM notification technology, which ultimately affects the user experience.
  • the embodiment of the invention provides a method, a device and a device management server for device management through a gateway device, which implements device management of the terminal by the DMS through the gateway device.
  • a gateway device which implements device management of the terminal by the DMS through the gateway device.
  • An embodiment of the present invention provides a method for device management by using a gateway device, including: receiving a registration message, where the registration message carries a terminal identifier and an address of a gateway device; and performing, by using the terminal identifier, an address of the gateway device Associated storage;
  • An embodiment of the present invention provides a method for device management by using a gateway device, including: sending a registration message to a device management server, where the registration message carries an address of the gateway device and a terminal identifier, so that the device management server The address of the gateway device is associated with the terminal identifier, and when the device management server sends the device management notification, the device management notification message is sent to the gateway device according to the stored gateway address; and the gateway device performs corresponding processing according to the device management notification message.
  • An embodiment of the present invention provides a device management server, including:
  • a first receiving module configured to receive a registration message, where the registration message carries a terminal identifier, an address of a gateway device;
  • An association module configured to associate the terminal identifier and the address of the gateway device, and an acquiring module, configured to acquire an address of the gateway device according to the association record, and a first sending module, configured to The address of the gateway device sends a device management notification message to the gateway device, so that the gateway device performs corresponding processing according to the device management notification message.
  • An embodiment of the present invention provides an apparatus for performing device management by using a gateway device, including: a second sending module, configured to send a registration message to a device management server, where the registration message carries an address of the gateway device and a terminal identifier, so that The device management server associates the address of the gateway device with the terminal identifier, and sends a device management notification message to the gateway device according to the stored gateway address when the device management server sends the device management notification; Manage notification messages for processing accordingly.
  • a second sending module configured to send a registration message to a device management server, where the registration message carries an address of the gateway device and a terminal identifier, so that The device management server associates the address of the gateway device with the terminal identifier, and sends a device management notification message to the gateway device according to the stored gateway address when the device management server sends the device management notification; Manage notification messages for processing accordingly.
  • a method, a device, and a device management server for performing device management by using a gateway device where the device management server sends the device management notification message when the device management server is to perform device management on the terminal
  • the device is sent to the gateway device to which the terminal belongs, and the gateway device performs corresponding processing according to the device management notification message, so that the device management server can perform device management on the terminal through the gateway device.
  • FIG. 1 is a flow chart of a method for device management by a gateway device according to an embodiment of the present invention
  • FIG. 2 is a flow chart of a method for device management by a gateway device according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of a method for device management by a gateway device according to an embodiment of the present invention
  • FIG. 4 is a schematic diagram of a method for device management by a gateway device according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of a method for device management by a gateway device according to an embodiment of the present invention.
  • FIG. 6 is a structural diagram of a device management server according to an embodiment of the present invention.
  • FIG. 7 is a structural diagram of an apparatus for device management by a gateway device according to an embodiment of the present invention.
  • FIG. 8 is a structural diagram of an apparatus for device management by a gateway device according to an embodiment of the present invention.
  • FIG. 9 is a structural diagram of an apparatus for device management by a gateway device according to an embodiment of the present invention.
  • a device management method performed by a gateway device includes:
  • the method for performing device management by using the gateway device by performing association storage on the terminal identifier in the received registration message and the address of the gateway device to which the terminal belongs, when device management needs to be performed on a terminal, according to The association record, the address of the gateway device to which the managed terminal belongs is obtained, and the device management notification message is sent to the gateway device according to the address, so that after the gateway device receives the device management notification message, according to the The device management notification message performs a corresponding processing operation, so that the device device can be implemented on the terminal by using the gateway device.
  • Reason the method for performing device management by using the gateway device according to the embodiment of the present invention, by performing association storage on the terminal identifier in the received registration message and the address of the gateway device to which the terminal belongs, when device management needs to be performed on a terminal, according to The association record, the address of the gateway device to which the managed terminal belongs is obtained, and the device management notification message is sent to the gateway device according to the address, so that after the gateway device receives the device management notification message, according to
  • an embodiment of the present invention provides a method for device management by using a gateway device, including:
  • the device management server sends a registration message to the device management server, where the registration message carries the address of the gateway device and the terminal identifier, so that the device management server associates the address of the gateway device with the terminal identifier, and sends the information to the device management server.
  • the device management notification is sent, the device management notification message is sent to the gateway according to the stored gateway address, so that the gateway device performs corresponding processing according to the device management notification message.
  • a method for performing device management by using a gateway device where the device sends a registration message to the device management server, where the registration message carries the address of the gateway device and the terminal device identifier of the gateway device, so that when The device management server needs to obtain the gateway address according to the registration message, and send the device management notification message to the gateway device, so that the gateway device according to the device
  • the device management notification message performs corresponding operations, so that the device management server can perform device management on the terminal through the gateway device.
  • an embodiment of the present invention provides a method for device management by using a gateway device, including the following steps:
  • the terminal sends a request message to the gateway device to join the personal network.
  • the gateway device authenticates the terminal, and after the authentication is passed, returns an acknowledgement message to the terminal to join the personal network; the acknowledgement message that agrees to join the personal network carries the address of the gateway device.
  • the terminal sends a registration message to the DMS, where the registration message carries an identifier of the terminal, an address of the gateway device, and an identity (such as a key) information used by the DMS to perform authentication and authentication on the terminal.
  • the registration message carries an identifier of the terminal, an address of the gateway device, and an identity (such as a key) information used by the DMS to perform authentication and authentication on the terminal.
  • the terminal may send the registration message directly to the DMS, or may send the registration message to the DMS through the gateway device, and send the registration message by the terminal through any other path.
  • the registration message may be carried in multiple message formats, such as a DM session message or a short message.
  • An example of some of the message content carried by the DM session message is given below: ⁇ SyncBody>
  • the entire registration message is encapsulated in the ⁇ Alert> element in the message body initiated by the DMC of the terminal to the DMS.
  • the ⁇ Item>/ ⁇ Meta>/ ⁇ Type> child element takes the value of Rever sed-Doma in-Name: org. openmobi lea 11 iance.
  • the ⁇ Item>/ ⁇ Data>/ ⁇ Destination>/ ⁇ PNEID> sub-element and the ⁇ 1 em> / ⁇ Da ta > / ⁇ Addr ess > sub-element carry the identifier of the terminal and The address of the gateway device to which the terminal belongs.
  • the terminal identifier and the address of the gateway device to which the terminal belongs may also be used as the basic information of the terminal, and are carried in the extended packet of the DMC to the DMS in the form of the extended Devlnf 0 M0, for example:
  • the /Devlnfo/Devld node carries the terminal identifier
  • the /DevInfo/Not iAddr node is the extended Dev Info M0 node, which carries the address of the gateway device to which the terminal belongs.
  • the identity (such as the key) information used by the DMS to authenticate the terminal may be carried by the ⁇ Cred> element in the header according to the standard DM format, and details are not described herein.
  • the DMS receives the registration message, associates the terminal identifier in the registration message with an address of the gateway device, and stores the associated record, where the associated record may be stored in the following form:
  • the terminal identifier can be used as an index entry of the table.
  • the DMS first queries whether the existing association record contains the terminal identifier in the registration message, and the association of the terminal identifier is already stored. Recording, and the address of the gateway device in the associated record is the same as the address of the gateway device in the registration message, and the registration message is no longer stored in association; when the address of the gateway device in the associated record and the gateway in the registration message If the address of the device is different, it means that the terminal may replace the associated gateway device, and the DMS replaces the address of the gateway device in the existing associated record by using the address of the gateway device in the registration message; The terminal identifier in the registration message is not included, and the DMS adds a new association record to the table. Therefore, when the terminal sends the registration message again after changing the gateway device, the DMS only needs to store the address of the gateway device after the change, and does not need to store the terminal identifier again, thereby reducing the operation.
  • the gateway When device management is performed on the terminal, according to the address of the gateway device, the gateway is used. The device sends a device management notification message.
  • the DMS obtains, according to the terminal identifier (such as ME 1: 493005100592800) in the associated record, an address of the gateway device to which the managed terminal belongs (such as MS I SDN: 1 3912345678), and according to the address of the gateway device.
  • Sending a device management notification message to the gateway device since the address of the gateway device in this embodiment is in the form of a mobile phone number, the device management notification message may be sent by using a short message bearer.
  • the device management notification message carries a terminal identifier (ie, IMEI: 493005100592800); the terminal identifier may be carried in an extension field reserved in the device management notification message header or in a custom field in the message body.
  • the DMS may only send a device management notification message to the gateway device, where the message carries The terminal identifiers of the multiple terminals, thereby saving signaling overhead of the DMS to the gateway device.
  • the gateway device After receiving the device management notification message, the gateway device performs notification target analysis to determine that the notification target of the device management notification is the managed terminal.
  • the gateway device determines, according to the terminal identifier (ie, IMEI: 493005100592800) carried in the device management notification message, that the notification target of the device management notification is the managed terminal.
  • the terminal identifier ie, IMEI: 493005100592800
  • the gateway device forwards the device management notification to the managed terminal.
  • the managed terminal receives the device management notification message, and establishes a DM session with the DMS, so that the DMS performs a management operation on the managed terminal.
  • the communication between the terminal and the gateway device can be implemented by various short-range wireless or wired communication technologies.
  • the terminal sends a registration message to the DMS, so that the DMS acquires the association record of the terminal and the address of the gateway device to which the terminal belongs.
  • the device management is performed according to the association record.
  • the notification is sent to the gateway device to which the managed terminal belongs, and is forwarded to the managed terminal by the gateway device, and the managed terminal establishes a DM session with the DMS according to the device management notification, and accepts a management operation performed by the DMS, thereby Implemented equipment management service
  • the device manages the device through the gateway device.
  • the embodiment of the present invention provides another method for device management by using a gateway device, including the following steps:
  • the terminal joins a personal network to which the gateway device belongs.
  • the gateway device sends a registration message to the DMS, where the registration message carries at least one terminal identifier, an address of the gateway device, and an identity (such as a key) information used by the DMS to perform authentication and authentication on the gateway device.
  • the registration message carries at least one terminal identifier, an address of the gateway device, and an identity (such as a key) information used by the DMS to perform authentication and authentication on the gateway device.
  • An example of some of the message content carried by the DM session message is given below: ⁇ SyncBody>
  • the entire registration message is encapsulated in the ⁇ Alert> element in the message body initiated by the DMS in the gateway device.
  • the ⁇ Item>/ ⁇ Meta>/ ⁇ Type> ⁇ element takes a value of Reversed-Domain-Name: org. openmobi lea 11 iance.
  • the address element, and the ⁇ 11613 ⁇ 4>/ ⁇ 0& &>/ ⁇ 068 11 ⁇ 2 ⁇ 01> sub-element carries a device identification list of a plurality of terminals including the gateway device (in this embodiment, the terminal 1 and the terminal identifier of the terminal 2) , ⁇ 6111>/ ⁇ 0&1&>/ (1 ( ⁇ 633> sub-element carries the DM notification address (ie gateway address) common to all terminals; in addition, the identity (such as key) information can be based on the standard DM format
  • the ⁇ Cr ed> element in the header is carried.
  • the DMS receives the registration message, associates the terminal identifier in the registration message with an address of the gateway device to which the terminal belongs, and stores the association record, where the associated record may be stored in the following form:
  • the terminal identifier can be used as an index entry of the table.
  • the DMS first queries whether the existing association record contains the terminal identifiers in the registration message, if the terminal identifier is already stored.
  • the registration message is not stored in association;
  • the address of the gateway device in the associated record is different from the address of the gateway device in the registration message, it means that the terminal may replace the associated gateway device, and the DMS replaces the existing association with the address of the gateway device in the registration message.
  • the address of the gateway device in the record if the terminal identifier in the registration message is not included in the existing association record, the DMS adds a new association record to the table. Therefore, when the terminal sends the registration message again after changing the gateway device, the DMS only needs to store the address of the gateway device after the change, and does not need to store the terminal identifier again, thereby reducing the operation.
  • the DMS When device management is to be performed on the terminal, the DMS sends a device management notification message according to the address of the gateway device.
  • the device management notification is performed on the terminal 1 and the terminal 2, and the DMS obtains the terminal 1 and the terminal 2 according to the terminal identifiers IMEI: 493005100592800 and IMEI: 493005100592801 in the associated record.
  • the address of the gateway device is MSISDN: 1 3912345678); since the terminal 1 and the terminal 2 belong to the same gateway device, the DMS only needs to send a device management notification message to the gateway device, where the device management notification message carries the terminal 1 and the identifier of the terminal 2: IMEI: 493005100592800 and IMEI: 493005100592801); the identifiers of the terminal 1 and the terminal 1 may be carried in an extension field reserved in the device management notification message header or in a custom field in the message body. .
  • the gateway device After receiving the device management notification, the gateway device performs notification target analysis to determine that the notification target of the device management notification is the terminal 1 and the terminal 2.
  • the gateway device determines that the notification target of the device management notification is the terminal 1 and the terminal 2 according to the identifiers of the terminal 1 and the terminal 2 (ie, IMEI: 493005100592800 and IMEI: 493005100592801) carried therein.
  • the gateway device forwards the device management notification to the terminal 1 and the terminal 2.
  • the terminal 1 and the terminal 2 receive the device management notification message, and establish a DM session with the DMS, so that the DMS performs management operations on the terminal 1 and the terminal 2.
  • the communication between the terminal and the gateway device can be through various short-range wireless or wired Communication technology to achieve.
  • the gateway device sends a registration message to the DMS, so that the DMS acquires the association record of the address of the gateway device and the identifier of the subordinate terminal, and when the DMS wants to perform device management on the subordinate terminal, according to the association. Recording, sending a device management notification to the gateway device, and forwarding, by the gateway device, the subordinate terminal, the subordinate terminal establishing a DM session with the DMS according to the device management notification, and accepting a management operation performed by the DMS, Thereby, the device management server implements device management on the terminal through the gateway device.
  • an embodiment of the present invention provides another method for device management by using a gateway device, including the following steps:
  • the terminal joins a personal network to which the gateway device belongs.
  • the gateway device maps the device management operation that can be implemented by the subordinate terminal as management object data to its own management tree structure.
  • the terminal may be one or more. In the embodiment of the present invention, two are described as an example. If the terminal itself supports the standard DM management object data structure, the data can be synchronized by using a short-distance connection technology between the terminal and the gateway device (such as USB cable, WiFi, Bluetooth, etc.) (for example, using OMA Da ta)
  • the Synchroni protocol directly maps the management objects on the terminal to the management tree of the gateway device. If the terminal does not support the standard DM management object data structure, it can connect to the short-distance connection between the terminal and the gateway device (such as USB). Cable, WiFi, Bluetooth, etc., convert the device management operations that can be implemented by the terminal into corresponding management objects and map them to the management tree of the gateway device.
  • the software list and the corresponding version number installed on the terminal are provided to the gateway device, and then the gateway device translates into a standard DM management object data structure according to the standard DM management object syntax rule, and then added to the management tree. Below a node.
  • the gateway device can determine whether the terminal supports the standard DM management object data structure according to the terminal capability information indicated when the terminal joins the personal network in step 501.
  • the gateway device sends a registration message to the DMS.
  • the registration message carries the identifiers of the terminal 1 and the terminal 2, the address of the gateway device, and the identity used by the DMS to authenticate the gateway device (eg, Further, the registration message may further include the identification information that the terminal 1 and the terminal 1 manage the object mapping to the gateway device; the registration message may be carried in multiple message formats, such as DM session messages or short messages, etc.
  • DM session messages An example of part of the message content carried by the DM session message is given below:
  • the entire registration message is encapsulated in an ⁇ Alert>;in the message body of the DMC actively initiated by the DMS in the gateway device.
  • the ⁇ Item>/ ⁇ Meta>/ ⁇ Type> sub-element takes the value of Reversed-Domain-Name: org. openmobi leal 1 iance.
  • the ⁇ 11613 ⁇ 4>/ ⁇ 0& &>/ ⁇ 068 11 ⁇ 2 ⁇ 01> sub-element carries a list of device IDs for multiple terminals, including the gateway device, and the ⁇ Item>/ ⁇ Data>/ ⁇ Address> sub-element It carries the DM notification address (that is, the gateway address) common to all terminals.
  • identity (such as key) information can be carried by the ⁇ Cred> element in the header according to the standard DM format.
  • the mapped attribute in the ⁇ Itera>/ ⁇ Data>/ ⁇ Destination>/ ⁇ PNEID> sub-element is true ("true,") or false ("false"), Indicates whether the M0 data of the terminal is mapped in the management tree of the gateway device.
  • the DMS receives the registration message, associates the identifiers of the terminal 1 and the terminal 2 in the registration message with the address of the gateway to which the terminal belongs, and stores the associated record. Correspondingly, the DMS further stores the terminal. 1 and the terminal 2 management object is mapped to the identification information of the gateway device.
  • the associated record may be stored in the form of a table as follows:
  • the terminal identifier can be used as an index entry of the table.
  • the DMS first queries whether the existing association record contains the terminal identifiers in the registration message, if the terminal identifier is already stored.
  • the address of the gateway device is the same as the address of the gateway device in the registration message, the registration message is not stored in association; when the address of the gateway device in the association record is in the registration message.
  • Means that the terminal may replace the associated gateway device, and the DMS replaces the address of the gateway device and the management object mapping identifier in the existing association record by using the address of the gateway device and the management object mapping identifier in the registration message respectively;
  • the associated record does not include the terminal identifier in the registration message, and the DMS adds a new associated record to the table. Therefore, when the terminal sends the registration message again after changing the gateway device, the DMS only needs to store the address of the gateway device after the change, and does not need to store the terminal identifier again, thereby
  • the device management of the terminal 1 and the terminal 2 is performed as an example.
  • the DMS obtains the terminal identifiers IMEI: 493005100592800 and IMEI: 493005100592801 in the associated record.
  • the address of the gateway device to which the terminal 1 and the terminal 2 belong is MS I SDN: 1 3912345678.
  • the DMS Since the terminal 1 and the terminal 2 belong to one gateway device, the DMS only needs to send a device management notification to the gateway device; Whether the M0 mapping identifier (in the present embodiment is t rue ) is: The M0 data management object of the terminal 1 and the terminal 2 has been mapped to the management tree of the gateway device, so the DMS only needs to directly establish the device with the gateway device. By managing the session, device management operations can be performed on the terminals of the gateway device. Therefore, the device management notification message may directly adopt an existing device management notification message format without carrying any terminal identifier, and may also carry the identifier of the gateway device in an extension field reserved in the device management notification message header or In the custom field in the message body.
  • the M0 mapping identifier in the present embodiment is t rue
  • the gateway device After receiving the device management notification, the gateway device performs notification target analysis to determine that the notification target of the device management notification is the gateway device.
  • the gateway device may determine that the notification target of the device management notification is the gateway according to the device management notification message that does not carry any terminal identifier (that is, an existing device management notification message format) or only a gateway device identifier.
  • the device management notification message adopts the existing DM notification message format
  • the notification target of the device management notification is the gateway device by default; when the device management notification message carries the gateway device identifier, according to the device
  • the gateway device identifier determines that the notification target of the device management notification is the gateway device.
  • the gateway device establishes a DM session with the DMS, and receives the pair of gateway devices sent by the DMS. Mapping M0 data operation commands of terminal 1 and terminal 2.
  • the DMS first requests the gateway device to acquire the terminal 1 and the terminal 2 mapped on the gateway device according to the identification information that the M0 data information of the terminal 1 and the terminal 2 in the association record has been mapped in the management tree of the gateway device.
  • M0 data information and then according to the M0 data information (such as software version information), decide to perform corresponding management operations (such as software upgrade), and send operation commands (including related M0 data information, such as a new version of the software program) to the gateway. device.
  • the gateway device performs corresponding management operations on the terminal 1 and the terminal 2 according to the operation command.
  • the gateway device utilizes the device management data mapped by the terminal 1 and the terminal 2 on the gateway device, the gateway device performs corresponding management operations on the terminal 1 and the terminal 2. For example, if the terminal itself supports the standard DM management object data structure, the gateway device may synchronize the M0 data information changed after the DMS operation (for example, using the OMA Da ta Synchroni za ti on protocol) to the terminal by means of data synchronization. Then, the terminal implements corresponding device management operations according to the changed M0 data information. If the terminal does not support the standard DM management object data structure, the gateway device can convert the M0 data information changed after the DMS operation into a device management operation command that the terminal can understand, and then send it to the corresponding terminal. For example, the new version of the software package in the M0 data information is sent to the terminal by the private download and installation command that the terminal can parse, thereby instructing the terminal to implement the corresponding device management operation.
  • the gateway device may synchronize the M0 data information changed after the
  • the gateway device sends a registration message to the DMS, so that the DMS acquires the association record of the address of the gateway device and the identifier of the subordinate terminal, and when the DMS wants to perform device management on the subordinate terminal, according to the association. Recording, sending the device management notification to the gateway device, thereby establishing a device management session with the gateway device, and then the gateway device receiving the management object data of the managed terminal sent by the device management server The operation command performs a corresponding management operation on the managed terminal according to the operation command, thereby implementing the management operation of the device by the device management server through the gateway device.
  • the embodiment of the present invention provides a device management server, including: a first receiving module 601, configured to receive a registration message, where the registration message carries a terminal identifier, The address of the gateway device; the registration message may be sent by the gateway device or may be sent by the terminal; the association module 602 is configured to: the terminal identifier in the registration message received by the first receiving module 601, the address of the gateway device Perform association storage;
  • the obtaining module 603 is configured to obtain, according to the association record obtained by the association module 602, an address of the gateway device to which the terminal belongs when performing device management on the terminal;
  • the first sending module 604 is configured to send a device management notification message to the gateway device according to the address of the gateway device obtained by the obtaining module 603, so that the gateway device performs corresponding processing according to the device management notification message.
  • the device management server provided by the embodiment of the present invention associates the terminal identifier in the received registration message with the address of the gateway device to which the terminal belongs, and when the device management needs to be performed on a terminal, according to the associated record, Obtaining an address of the gateway device to which the managed terminal belongs, and sending a device management notification message to the gateway device according to the address, so that the gateway device receives the device management notification message, and performs corresponding processing, thereby
  • the device management server implements device management on the terminal through the gateway device.
  • an embodiment of the present invention provides a device for performing device management by using a gateway device, including:
  • the second sending module 701 is configured to send a registration message to the device management server, where the registration message carries the address of the gateway device and the terminal identifier, so that the device management server associates the address of the gateway device with the terminal identifier. And sending, by the device management server, the device management notification message to the gateway device according to the stored address of the gateway device; and causing the gateway device to perform corresponding processing according to the device management notification message.
  • An embodiment of the present invention provides an apparatus for performing device management by using a gateway device.
  • the device for performing device management by using a gateway device may be a gateway device or a terminal, and sending a registration message to the device management server, where the registration is performed.
  • the message carries the address of the gateway device and the terminal identifier of the gateway device, so that when the device management server needs to perform device management on the gateway device, the address of the gateway device can be obtained according to the registration message.
  • the device management notification message is sent to the gateway device, and the gateway device performs corresponding processing according to the device management notification message, thereby implementing device management on the terminal by using the gateway device.
  • an apparatus for performing device management by using a gateway device may further include:
  • the second receiving module 702 is configured to receive a device management notification message sent by the device management server, where the device management notification message carries the managed terminal identifier.
  • the forwarding module 703 is configured to send the device management notification message to the managed terminal according to the managed terminal identifier, so that the managed terminal establishes a session with the device management server according to the device management notification message. Thereby accepting the management of the device management server.
  • the device for performing device management by using the gateway device may be a gateway device, receiving a device management notification message sent by the device management server, and sending the device management notification message
  • the device is forwarded to the terminal, and the terminal establishes a session with the device management server, and accepts management of the device management server, so that the device management server performs device management on the terminal through the gateway device.
  • the embodiment of the present invention provides an apparatus for performing device management by using a gateway device, which includes:
  • a third receiving module 802 configured to receive a device management notification message sent by the device management server, where the session establishing module 803 is configured to establish a session with the device management server according to the device management notification message, and accept the device management server The operation of the mapped management object;
  • the management operation module 804 is configured to perform corresponding operations on the terminal corresponding to the management object according to the operation.
  • An embodiment of the present invention provides an apparatus for performing device management by using a gateway device.
  • the device for performing device management by using a gateway device may be a gateway device, and sending a registration message to the device management server, where the registration message carries a gateway device.
  • the address of the gateway device, and the device identifier of the gateway device when the device management server needs to perform device management on the device of the gateway device, the device can obtain the address of the gateway device according to the registration message, and manage the device.
  • the gateway device is configured to establish a device management session with the gateway device, and the gateway device accepts, by the device management server, an operation of the management object mapped thereto, according to the operation command
  • the managed terminal performs corresponding operations, thereby implementing the device management server to perform device management on the terminal through the gateway device.
  • the device for performing device management by using a gateway device includes:
  • the fourth receiving module 902 is configured to receive a device management notification message sent by the gateway device.
  • the session establishing module 903 is configured to establish a session with the device management server according to the device management notification message, and receive a management operation of the device management server.
  • An embodiment of the present invention provides an apparatus for performing device management by using a gateway device, where the device that performs device management by using the gateway device may be a terminal, and sends a registration message to the device management server, where the registration message carries the terminal identifier and the gateway.
  • An address of the device so that the device management server can send the device management notification message to the gateway device according to the registration message, and the gateway device forwards the message to the terminal device; after receiving the device management notification message, the terminal manages the notification message according to the device.
  • multiple DMSs may provide DM services for different terminals and gateway devices, and each DMS is uniquely identified by a server identifier.
  • the terminal or gateway device In order to be able to connect to the DMS and accept the corresponding DM service, the terminal or gateway device must be configured locally with a legitimate account corresponding to the server ID of the corresponding DMS. Since the DM management account configured by the terminal and the gateway device may be different, the DMS that can connect and accept the DM service is different. In some cases, no DM management is configured on the terminal or the gateway device. Account.
  • the DM account configuration status of the gateway device and the terminal may be selected, and then one or several embodiments are selected from the technical solutions provided by the embodiments of the present invention to perform device management notification.
  • Variations that can be easily conceived by those skilled in the art in light of the embodiments of the present invention are intended to be within the scope of the present invention.
  • a person skilled in the art can understand that all or part of the steps of implementing the above embodiments may be performed by a program to instruct related hardware, and the program may be stored in a computer readable storage medium such as a ROM/RAM or a disk. Or a CD or the like.

Description

通过网关设备进行设备管理的方法、 装置及设
备管理服务器 技术领域
本发明涉及通信技术领域, 尤其涉及一种通过网关设备进行设备管理的 方法、 装置及设备管理服务器。 背景技术
0MA ( Open Mobile Alliance, 开放移动联盟) DM ( Device Management, 设备管理)是由开放移动联盟设备管理工作组制定的设备管理统一规范, 可 用于第三方通过无线网络管理和设置无线网络终端, 所述第三方可以是移动 运营商、 业务提供商、 合作方的信息管理部门等 DMA ( Device Management Authority, 设备管理授权者)。
现有技术中, DMA要对终端 MO (Management Object, 管理对象) 进行 操作时, 需要在 DMS (Device Management Server, 设备管理服务器) 与 DMC (Device Management Client, 设备管理客户端)之间建立 DM会话。 所述 DM 会话必须由 DMC使用预先配置的帐号向 DMS发起连接请求来建立, 而不能反 过来由 DMS发起, 因此, 当网络侧需要建立 DM会话时, 需要由 DMS发送 DM 通知消息给 DMC, 触发 DMC向 DMS发起连接请求, 从而建立 DM管理会话。
目前的 DM通知技术仅适用于终端地址固定不变且直接可达的情形, 比如 当终端为用户的手机时, DMS可以使用无线应用协议推送技术, 通过向预先配 置于 DMS中的指定手机号码发送 DM通知消息, 实现将 DM通知消息发送到指 定手机上的 DMC, 从而完成 DM通知过程。
然而, 在某些领域中用户终端可能需要通过网关设备才能接入外部网络, 由于网关的地址屏蔽作用以及终端的移动性, 比如终端有可能会变更其所属 的网络, 使得在现有 DM通知技术的条件下, 从而导致 DMS不能及时对终端进 行设备管理 (比如软件 /固件升级、 病毒库更新等), 最终影响用户体验。
发明内容
本发明实施例提供了一种通过网关设备进行设备管理的方法、 装置及设 备管理服务器, 实现了 DMS 通过网关设备对终端进行设备管理。 为实现上述 目的, 本发明实施例釆用以下技术方案:
本发明实施例提供了一种通过网关设备进行设备管理的方法, 包括: 接收登记消息, 所述登记消息携带有终端标识、 网关设备的地址; 对所述终端标识、 所述网关设备的地址进行关联存储;
根据所述关联记录, 获取所述网关设备的地址;
根据所述网关设备的地址, 向所述网关设备发送设备管理通知消息, 以 便网关设备根据所述设备管理通知消息进行相应处理。
本发明实施例提供了一种通过网关设备进行设备管理的方法, 包括: 向设备管理服务器发送登记消息, 所述登记消息中携带有网关设备的地 址、 终端标识, 以便于设备管理服务器对所述网关设备的地址和终端标识进 行关联存储, 并在设备管理服务器发送设备管理通知时, 根据存储的网关地 址向网关设备发送设备管理通知消息; 使得网关设备根据所述设备管理通知 消息进行相应处理。
本发明实施例提供了一种设备管理服务器, 包括:
第一接收模块, 用于接收登记消息, 所述登记消息携带有终端标识、 网 关设备的地址;
关联模块, 用于对所述终端标识、 所述网关设备的地址进行关联存储; 获取模块, 用于根据所述关联记录, 获取所述网关设备的地址; 第一发送模块, 用于根据所述网关设备的地址, 向所述网关设备发送设 备管理通知消息, 以便网关设备根据所述设备管理通知消息进行相应处理。 本发明实施例提供了一种通过网关设备进行设备管理的装置, 包括: 第二发送模块, 用于向设备管理服务器发送登记消息, 所述登记消息中 携带有网关设备的地址、 终端标识, 以便于设备管理服务器对所述网关设备 的地址和终端标识进行关联存储, 并在设备管理服务器发送设备管理通知时, 根据存储的网关地址向网关设备发送设备管理通知消息; 使得网关设备根据 所述设备管理通知消息进行相应处理。
本发明实施例提供的一种通过网关设备进行设备管理的方法、 装置及设 备管理服务器, 通过当所述设备管理服务器要对终端进行设备管理时, 所述 设备管理服务器将所述设备管理通知消息发送给所述终端所属的网关设备, 由所述网关设备根据所述设备管理通知消息进行相应的处理, 以便可以实现 设备管理服务器通过网关设备对终端进行设备管理。 附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案, 下面将对实 施例或现有技术描述中所需要使用的附图作简单地介绍, 显而易见地, 下面 描述中的附图仅仅是本发明的一些实施例, 对于本领域普通技术人员来讲, 在不付出创造性劳动性的前提下, 还可以根据这些附图获得其它的附图。
图 1 为本发明实施例提供的一种通过网关设备进行设备管理的方法的流 程图;
图 2 为本发明实施例提供的一种通过网关设备进行设备管理的方法的流 程图;
图 3 为本发明实施例提供的一种通过网关设备进行设备管理的方法的示 意图;
图 4 为本发明实施例提供的一种通过网关设备进行设备管理的方法的示 意图;
图 5 为本发明实施例提供的一种通过网关设备进行设备管理的方法的示 意图;
图 6为本发明实施例提供的一种设备管理服务器的结构图;
图 7 为本发明实施例提供的一种通过网关设备进行设备管理的装置的结 构图;
图 8 为本发明实施例提供的一种通过网关设备进行设备管理的装置的结 构图;
图 9 为本发明实施例提供的一种通过网关设备进行设备管理的装置的结 构图。
具体实施方式
下面将结合本发明实施例中的附图, 对本发明实施例中的技术方案进行 清楚、 完整地描述, 显然, 所描述的实施例仅仅是本发明一部分实施例, 而 不是全部的实施例。 基于本发明中的实施例, 本领域普通技术人员在没有做 出创造性劳动前提下所获得的所有其它实施例, 都属于本发明保护的范围。
如图 1所示, 本发明实施例提供的一种通过网关设备进行设备管理方法, 包括:
101、 接收登记消息, 所述登记消息携带有终端标识、 网关设备的地址;
102、 对所述终端标识、 所述网关设备的地址进行关联存储;
103、 根据所述关联记录, 获取所述网关设备的地址;
104、根据所述网关设备的地址,向所述网关设备发送设备管理通知消息, 以便网关设备根据所述设备管理通知消息进行相应处理。
本发明实施例提供的通过网关设备进行设备管理的方法, 通过对接收到 的登记消息中的终端标识及所述终端所属网关设备的地址进行关联存储, 当 需要对某终端进行设备管理时, 根据所述关联记录, 获取所述被管理终端所 属网关设备的地址, 根据所述地址, 向所述网关设备发送设备管理通知消息, 从而使所述网关设备接收到所述设备管理通知消息后, 根据所述设备管理通 知消息进行相应的处理操作, 以便可以实现通过网关设备对终端进行设备管 理。
如图 2所示, 本发明实施例提供一种通过网关设备进行设备管理的方法, 包括:
201、 向设备管理服务器发送登记消息, 所述登记消息中携带有网关设备 的地址、 终端标识, 以便于设备管理服务器对所述网关设备的地址和终端标 识进行关联存储, 并在设备管理服务器发送设备管理通知时, 根据存储的网 关地址向网关发送设备管理通知消息, 使得网关设备根据所述设备管理通知 消息进行相应处理。
本发明实施例提供的一种通过网关设备进行设备管理的方法, 通过向设 备管理服务器发送登记消息, 所述登记消息中携带有网关设备的地址、 所述 网关设备下属终端标识, 使得当所述设备管理服务器需要对所述网关设备下 属设备如终端进行设备管理时, 能够根据所述登记消息获取所述网关地址, 将所述设备管理通知消息发给所述网关设备, 从而使得网关设备根据所述设 备管理通知消息进行相应操作, 以便可以实现设备管理服务器通过网关设备 对终端进行设备管理。
如图 3所示, 本发明实施例提供一种通过网关设备进行设备管理的方法, 包括如下步骤:
301、 终端向网关设备发送加入个人网络的请求消息。
302、 网关设备对终端进行鉴权, 并在鉴权通过后, 向终端返回同意加入 个人网络的确认消息; 所述同意加入个人网络的确认消息携带有所述网关设 备的地址。
303、 终端向 DMS发送登记消息, 所述登记消息携带有终端的标识、 所述 网关设备的地址以及用于 DMS 对所述终端进行鉴权认证的身份(如密钥)信 息。
在实施本步骤时, 终端既可以将登记消息直接发送给 DMS , 也可以经过网 关设备将登记消息发送到 DMS,以及由终端通过其它任何路径将登记消息发送 到 DMS; 所述登记消息可采用多种消息格式进行承载, 如 DM会话消息或短消 息等。 下面给出一种釆用 DM会话消息进行承载的部分消息内容示例: <SyncBody>
<Alert>
<CmdID>2</CmdID>
<Data>1226</Data> <!— Generic Alert — >
<Item>
<Meta>
<Type xmlns=" syncml: met inf " >
Rever sed-Doma in-Name:
org. openmobi lea 11 iance. notif icaton
</Type>
<Format xmlns=" syncml: met inf ">xml</Format>
<Mark xmlns=" syncml: met inf " >cr i t ica 1</Mark> <!―
Optional ― >
</Meta>
<Data>
<! Notification Destination and Address ― > <Destination>
<PNEID>IMEI: 493005100592800</PNEID>
</Dest ination>
<Address>MSISDN: 13912345678 </Address>
</Data>
</Item>
</Alert> </SyncBody>
其中, 整个登记消息被封装在终端的 DMC 向 DMS 主动发起的消息体中的 <Alert>元素 中 。 具体地, <Item>/<Meta>/<Type>子元素取值为 Rever sed-Doma in-Name: org. openmobi lea 11 iance. not if icaton, 表明了 此 <Item〉数据项 用 于登记终端 所属 网 关设备的地址 , 而 <Item>/<Data>/<Destination>/<PNEID> 子 元 素 和 < 1 em> / <Da t a > / < Addr e s s >子元素中则分别携带了终端的标识和终端所属 网关设备的地址。 类似地 , 上述终端标识和终端所属网关设备的地址也可 以作为终端的基本信息, 以扩展的 Devlnf 0 M0形式携带在 DMC向 DMS主动 发起的数据包中, 例如:
<SyncBody>
<Replace>
<CmdID>3</CmdID>
<Item>
<SourceXLocURI>. /Devlnf o/DevId</LocURIX/Source> <Meta>
<Format xmlns= syncral: met inf ' >chr</Format> <Type xmlns= syncral: met inf ' >te t/plain</Type>
</Meta>
<Data>IMEI: 493005100592800</Data>
</Item>
<Item>
<SourceXLocURI>. /Devlnf o/Not iAddr</LocURI></Source> <Meta>
<Format xmlns=/ syncral: met inf ' >chr</Format> <Type xmlns=/ syncral: metinf' >te t/ lain</Type> </Meta>
<Data> MSI SDN: 13912345678 </Da ta>
</ I tem>
</Replace> <SyncBody>
其中, . /Devlnfo/Devld 节点携带终端标识 , 而. /DevInfo/Not iAddr 节 点为扩展的 Dev Info M0节点, 携带了终端所属网关设备的地址。 此外, 用于 DMS对终端进行鉴权认证的身份(如密钥 )信息则可根据标准 DM格式由消息 头中的 <Cred〉元素携带, 此处不再赘述。
304、 DMS接收所述登记消息, 对所述登记消息中的终端标识及网关设备 的地址进行关联, 并存储所述关联记录, 所述关联记录可釆用如下表格的形 式存储:
Figure imgf000010_0001
其中终端标识可作为表格的索引项, 当 DMS接收登记消息时, 首先通过 索引项查询是否已存在现有关联记录中包含所述登记消息中的终端标识, 若 已存储有所述终端标识的关联记录, 且所述关联记录中网关设备的地址与登 记消息中网关设备的地址相同时, 则不再对所述登记消息进行关联存储; 当 所述关联记录中网关设备的地址与登记消息中网关设备的地址不同时, 则意 味着终端可能更换了所属的网关设备, DMS使用所述登记消息中的网关设备的 地址替换该现有关联记录中的网关设备的地址; 若在现有关联记录中未包含 所述登记消息中的终端标识, DMS在表格中添加新的关联记录。 从而当终端在 变更了所属网关设备后, 再次发送登记消息时, DMS只需要对变更之后的网关 设备的地址进行存储, 而不必再对终端标识进行再次存储, 从而减少了操作。
305、 当要对终端进行设备管理时, 根据所述网关设备的地址向所述网关 设备发送设备管理通知消息。
具体的, DMS根据所述关联记录中的终端标识(如 ME 1: 493005100592800 ), 获取所述被管理终端所属网关设备的地址 (如 MS I SDN: 1 3912345678 ), 并根据 所述网关设备的地址向所述网关设备发送设备管理通知消息。 由于本实施例 中网关设备的地址为手机号码的形式, 因此所述设备管理通知消息可采用短 消息承载发送。 所述设备管理通知消息携带有终端标识 ( 即 IMEI : 493005100592800 ); 所述终端标识可携带于所述设备管理通知消息头中 预留的扩展字段中或消息体中的自定义字段中。 当 DMS 需要同时对多个终端 进行管理时, 若根据所述关联记录获取的多个终端所属网关设备的地址相同 时, DMS可仅向所述网关设备发送一条设备管理通知消息, 该消息中携带所述 多个终端的终端标识, 从而节约 DMS到网关设备的信令开销。
306、 网关设备收到所述设备管理通知消息后, 进行通知目标分析, 以确 定所述设备管理通知的通知目标为所述被管理终端。
具体的, 网关设备根据所述设备管理通知消息携带的终端标识 (即 IMEI : 493005100592800 ), 确定所述设备管理通知的通知目标为所述被管理终 端。
307、 网关设备将所述设备管理通知转发给所述被管理终端。
308、 所述被管理终端接收所述设备管理通知消息, 与 DMS建立 DM会话, 以便于 DMS对所述被管理终端进行管理操作。
在本实施例中, 终端与网关设备的通讯可以通过各种短距离无线或有线 通讯技术来实现。
在本发明实施例中, 由终端向 DMS发送登记消息, 使得 DMS获取终端与 其所属网关设备的地址的关联记录, 当 DMS要对终端进行设备管理时, 根据 所述关联记录, 将所述设备管理通知发送给被管理终端所属网关设备, 由所 述网关设备转发给所述被管理终端, 所述被管理终端根据所述设备管理通知 同 DMS建立 DM会话, 接受 DMS对其进行的管理操作, 从而实现了设备管理服 务器通过网关设备对终端进行设备管理。
如图 4所示, 本发明实施例提供了另一种通过网关设备进行设备管理的方 法, 包括如下步骤:
401、 终端加入网关设备所属的个人网络。
402、 网关设备向 DMS发送登记消息, 所述登记消息携带有至少一个终端 标识、 网关设备的地址以及用于 DMS 对网关设备进行鉴权认证的身份(如密 钥)信息; 所述登记消息可采用多种消息格式进行承载, 如 DM会话消息或短 消息等。 下面给出一种采用 DM会话消息进行承载的部分消息内容示例: <SyncBody>
<Alert>
<CmdID>2</CmdID>
<Data>1226</Data> <!— Generic Alert --〉
<Item>
<Meta>
<Type xmlns=" syncml: met inf " >
Rever sed-Doma in-Name:
org. openmobi lea 11 iance. notif icaton
</Type>
<Format xmlns=" syncml: met inf " >xml</Format>
<Mark xmlns=" syncml: met inf " >cr i t ica 1</Mark> <!―
Optional ― >
</Meta>
<Data>
<! Notification Destination and Address 一- > <Destination>
<PNEID>IMEI: 493005100592800</PNEID> <PNEID>IMEI: 493005100592801</PNEID>
</Dest ination>
<Address>MSISDN: 13912345678 </Address>
</Data>
</Item>
</Alert> </SyncBody>
其中, 整个登记消息被封装在网关设备中的 DMC向 DMS主动发起的消息 体中的 <Alert> ¾素中。 具体地, <Item>/<Meta>/<Type>~^元素取值为 Reversed- Domain- Name: org. openmobi lea 11 iance. notif icaton , 表明此 < I tem〉数据项用于登记终端的通知地址, 而<1161¾>/<0& &>/<068 1½^01〉子 元素携带了包括网关设备在内的多个终端的设备标识列表(本实施例中为终 端 1, 终端 2的终端标识), <^6111〉/<0&1&>/ (1(^633>子元素则携带了所有终 端公共的 DM通知地址(即网关地址); 此外, 身份(如密钥)信息则可根据 标准 DM格式由消息头中的 <Cr ed>元素携带。
403、 DMS接收所述登记消息, 对所述登记消息中的终端标识及所述终端 所属网关设备的地址进行关联, 并存储所述关联记录, 所述关联记录可采用 如下表格的形式存储:
Figure imgf000013_0001
其中终端标识可作为表格的索引项, 当 DMS接收登记消息时, 首先通过 索引项查询是否已存在现有关联记录中包含所述登记消息中的各终端标识, 若已存储有所述终端标识的关联记录, 且所述关联记录中网关设备的地址与 登记消息中网关设备的地址相同时, 则不再对所述登记消息进行关联存储; 当所述关联记录中网关设备的地址与登记消息中网关设备的地址不同时, 则 意味着终端可能更换了所属的网关设备, DMS使用所述登记消息中的网关设备 的地址替换该现有关联记录中的网关设备的地址; 若在现有关联记录中未包 含所述登记消息中的终端标识, DMS在表格中添加新的关联记录。 从而当终端 在变更了所属网关设备后, 再次发送登记消息时, DMS只需要对变更之后的网 关设备的地址进行存储, 而不必再对终端标识进行再次存储, 从而减少了操 作。
404、当要对终端进行设备管理时, DMS根据网关设备的地址发送设备管理 通知消息。
其体的, 本实施例中以同时要对终端 1和终端 2进行设备管理通知为例 , DMS 根据所述关联记录中 的终端标识 IMEI : 493005100592800 和 IMEI : 493005100592801 , 获取所述终端 1 和终端 2 所属网关设备的地址 MSISDN: 1 3912345678 ) ;由于终端 1和终端 2同属于一个网关设备, 因此 DMS 只需向所述网关设备发送一条设备管理通知消息, 所述设备管理通知消息携 带有 所述终端 1 和 终端 2 的 标识 IMEI: 493005100592800 和 IMEI : 493005100592801 ); 所述终端 1和终端 1的标识可携带于所述设备管理 通知消息头中预留的扩展字段中或消息体中的自定义字段中。
405、 网关设备收到所述设备管理通知后, 进行通知目标分析, 以确定所 述设备管理通知的通知目标为所述终端 1和终端 2。
具体的, 网关设备根据其中携带的终端 1 和终端 2 的标识 (即 IMEI : 493005100592800和 IMEI: 493005100592801 ), 确定所述设备管理通知 的通知目标为所述终端 1和终端 2。
406、 网关设备将所述设备管理通知转发给所述终端 1和终端 2。
407、 所述终端 1和终端 2接收所述设备管理通知消息, 与 DMS建立 DM 会话, 以便于 DMS对所述终端 1和终端 2进行管理操作。
在本实施例中, 终端与网关设备的通讯可以通过各种短距离无线或有线 通讯技术来实现。
在本发明实施例中, 由网关设备向 DMS发送登记消息, 使得 DMS获取网 关设备的地址和其所下属终端标识的关联记录, 当 DMS要对其所下属终端进 行设备管理时, 根据所述关联记录, 将设备管理通知发送给所述网关设备, 由所述网关设备转发给所述下属终端, 所述下属终端根据所述设备管理通知 同 DMS建立 DM会话, 接受 DMS对其进行的管理操作, 从而实现了设备管理服 务器通过网关设备对终端进行设备管理。
如图 5 所示, 本发明实施例提供了另一种通过网关设备进行设备管理的 方法, 包括如下步骤:
501、 终端加入网关设备所属的个人网络。
502、 网关设备将对下属终端所能实施的设备管理操作作为管理对象数据 映射到自身的管理树结构中。
所述终端可以为 1个或多个, 在本发明实施例中, 以两个为例进行描述。 其中, 若终端本身支持标准的 DM管理对象数据结构, 则可通过终端与网关设 备间的短距离连接技术(如 USB线缆、 WiFi、 蓝牙等), 采用数据同步的方式 (如采用 OMA Da ta Synchroni za t ion协议) 直接将终端上的管理对象映射到 网关设备的管理树中; 若终端不支持标准的 DM管理对象数据结构, 则可通过 终端与网关设备间的短距离连接技术(如 USB线缆、 WiFi、 蓝牙等), 将终端 所能实施的设备管理操作转换为相应的管理对象映射到网关设备的管理树 中。 比如将终端上所安装的软件列表及相应的版本号等信息提供给网关设备, 再由网关设备按照标准的 DM管理对象语法规则翻译为标准的 DM管理对象数 据结构, 然后添加到管理树中的某个节点之下。 在实施本步骤过程中, 网关 设备可根据步骤 501 中终端加入个人网络时所指示的终端能力信息判断终端 是否支持标准的 DM管理对象数据结构。
503、 网关设备向 DMS发送登记消息。 所述登记消息携带有终端 1和终端 2的标识、 网关设备的地址以及用于 DMS对网关设备进行鉴权认证的身份(如 密钥)信息; 进一步地, 所述登记消息中还可以包括所述终端 1和终端 1管 理对象映射至所述网关设备的标识信息; 所述登记消息可釆用多种消息格式 进行承载, 如 DM会话消息或短消息等。 下面给出一种采用 DM会话消息进行 承载的部分消息内容示例:
<SyncBody>
<Alert>
<CmdID>2</CmdID>
<Data>1226</Data> <!— Generic Alert --〉
<Item>
<Meta>
<Type xmlns=" syncml: met inf " >
Rever sed-Doma in-Name:
org. openmobi lea 11 iance. not if icaton
</Type>
<Format xmlns=" syncml: met inf " >xml</Format>
<Mark xmlns=" syncml: met inf " >cr i t ica 1</Mark> <!―
Optional —― >
</Meta>
<Data>
<! Notification Destination and Address ― >
<Destination>
<PNEID mapped=true>IMEI: 493005100592800</PNEID> <PNEID mapped=true>IMEI: 493005100592801</PNEID>
</Dest ination>
<Address>MSISDN: 13912345678 </Address>
</Data> </Item>
</Alert>
</SyncBody>
其中, 整个登记消息被封装在网关设备中的 DMC向 DMS主动发起的消息 体中的 <Alert>;^素中。 具体地, <Item>/<Meta>/<Type>子元素取值为 Reversed- Domain- Name: org. openmobi leal 1 iance. notif icaton, 表明了此 < I tem〉数据项用于登记终端的通知地址; 而<1161¾>/<0& &>/<068 1½^01〉子 元素携带 了 包括网 关设备在 内 的多 个终端的设备标识列表, <Item>/<Data>/<Address〉子元素则携带了所有终端公共的 DM通知地址 (即 网关地址)。 此外, 身份(如密钥)信息则可根据标准 DM格式由消息头中的 <Cred〉元素携带。 另夕卜, 可选地, ^<Itera>/<Data>/<Destination>/<PNEID> 子元素中的 mapped属性, 取值为 true ( "真,,) 或 false ( "假" ) , 用于表 明是否在网关设备的管理树中映射了该终端的 M0数据。
504、 DMS接收所述登记消息, 对所述登记消息中的终端 1和终端 2的标 识及所述终端所属网关的地址进行关联, 并存储所述关联记录; 相应的, DMS 还存储所述终端 1和终端 2管理对象映射至所述网关设备的标识信息。 所述 关联记录可采用如下表格的形式存储:
Figure imgf000017_0001
其中终端标识可作为表格的索引项, 当 DMS接收登记消息时 , 首先通过 索引项查询是否已存在现有关联记录中包含所述登记消息中的各终端标识, 若已存储有所述终端标识的关联记录, 且所述关联记录中网关设备的地址与 登记消息中网关设备的地址相同时, 则不再对所述登记消息进行关联存储; 当所述关联记录中网关设备的地址与登记消息中网关设备的地址不同时, 则 意味着终端可能更换了所属的网关设备, DMS使用所述登记消息中的网关设备 的地址和管理对象映射标识分别替换该现有关联记录中的网关设备的地址和 管理对象映射标识; 若在现有关联记录中未包含所述登记消息中的终端标识, DMS在表格中添加新的关联记录。从而当终端在变更了所属网关设备后, 再次 发送登记消息时, DMS只需要对变更之后的网关设备的地址进行存储, 而不必 再对终端标识进行再次存储, 从而减少了操作。
505、 当要对终端进行设备管理时, 在本实施例中以同时要对终端 1和终 端 2 进行设备管理为例, DMS 根据所述关联记录中的终端标识 IMEI : 493005100592800和 IMEI : 493005100592801 , 获取所述终端 1和终端 2 所属网关设备的地址 MS I SDN: 1 3912345678 , 由于终端 1和终端 2同属于一个 网关设备, 因此 DMS 只需向所述网关设备发送一条设备管理通知; 又根据关 联记录中的 M0是否映射标识(在本实施例中为 t rue )即: 终端 1和终端 2的 M0数据管理对象已被映射到该网关设备的管理树中, 所以 DMS只需要与网关 设备直接建立设备管理会话, 就能够对网关设备下属的终端进行设备管理操 作。 因此所述设备管理通知消息可直接采用现有的设备管理通知消息格式而 不携带任何终端标识, 当然也可以将网关设备的标识携带于所述设备管理通 知消息头中预留的扩展字段中或消息体中的自定义字段中。
506、 网关设备收到所述设备管理通知后, 进行通知目标分析以便确定所 述设备管理通知的通知目标为所述网关设备。
具体的, 网关设备可以根据所述设备管理通知消息中不携带任何终端标 识 (即现有的设备管理通知消息格式) 或仅携带网关设备标识, 确定所述设 备管理通知的通知目标为所述网关设备; 或当所述设备管理通知消息采用现 有的 DM通知消息格式时,默认所述设备管理通知的通知目标为所述网关设备; 当所述设备管理通知消息携带有网关设备标识时, 根据所述网关设备标识确 定所述设备管理通知的通知目标为所述网关设备。
507、 网关设备与 DMS建立 DM会话, 并接收 DMS发送的对网关设备上所 映射的终端 1和终端 2的 M0数据操作命令。
在会话中, DMS根据关联记录中终端 1和终端 2的 M0数据信息已被映射 在网关设备的管理树中的标识信息, 首先向网关设备请求获取在网关设备上 映射的终端 1和终端 2的 M0数据信息, 然后根据所述 M0数据信息 (如软件 版本信息) 决定执行相应的管理操作 (如软件升级), 并将操作命令 (包括相 关 M0数据信息, 如新版本的软件程序)发送到网关设备。
508、 网关设备根据所述操作命令, 对终端 1和终端 2进行相应的管理操 作。
如网关设备利用终端 1和终端 2在所述网关设备映射的设备管理数据, 网关设备对终端 1和终端 2进行相应的管理操作。 比如, 若终端本身支持标 准的 DM管理对象数据结构, 则网关设备可采用数据同步的方式将经过 DMS操 作后改变的 M0数据信息同步 (如釆用 OMA Da ta Synchroni za t i on 协议)到 终端上, 然后终端根据改变后的 M0数据信息实施相应的设备管理操作。 若终 端不支持标准的 DM管理对象数据结构, 则网关设备可将经过 DMS操作后改变 的 M0数据信息转换为终端所能够理解的设备管理操作命令, 然后发送到相应 的终端。 比如将 M0数据信息中的新版本软件包用终端能够解析的私有的下载 和安装命令发送到终端 , 从而指示终端实施相应的设备管理操作。
在本发明实施例中, 由网关设备向 DMS发送登记消息 , 使得 DMS获取网 关设备的地址和其所下属终端标识的关联记录, 当 DMS要对其所下属终端进 行设备管理时, 根据所述关联记录, 将所述设备管理通知发送给所述网关设 备, 从而与所述网关设备建立设备管理会话, 进而所述网关设备接收所述设 备管理服务器发送的对所述被管理终端的管理对象数据的操作命令, 根据所 述操作命令对所述被管理终端进行相应的管理操作, 从而实现了设备管理服 务器通过网关设备对终端进行管理操作。
如图 6所示, 本发明实施例提供了一种设备管理服务器, 包括: 第一接收模块 601, 用于接收登记消息, 所述登记消息携带有终端标识、 网关设备的地址; 所述登记消息可以为网关设备发送也可以为终端所发送; 关联模块 602,用于对所述第一接收模块 601接收的登记消息中的终端标 识、 所述网关设备的地址进行关联存储;
获取模块 603 , 用于当要对终端进行设备管理时, 根据所述关联模块 602 得到的关联记录, 获取所述终端所属网关设备的地址;
第一发送模块 604, 用于根据所述获取模块 603获得的网关设备的地址, 向所述网关设备发送设备管理通知消息 , 以便网关设备根据所述设备管理通 知消息进行相应处理。
本发明实施例提供的设备管理服务器, 通过对接收到的登记消息中的终 端标识及所述终端所属网关设备的地址进行关联存储, 当需要对某终端进行 设备管理时, 根据所述关联记录, 可以获得所述被管理终端所属网关设备的 地址, 根据所述地址, 向所述网关设备发送设备管理通知消息, 使所述网关 设备接收到所述设备管理通知消息后, 进行相应的处理, 从而实现了设备管 理服务器通过网关设备对终端进行设备管理。
如图 7 所示, 本发明实施例提供了一种通过网关设备进行设备管理的装 置, 包括:
第二发送模块 701, 用于向设备管理服务器发送登记消息, 所述登记消息 中携带有网关设备的地址、 终端标识, 以便于设备管理服务器对所述网关设 备的地址和终端标识进行关联存储, 并在设备管理服务器发送设备管理通知 时, 根据存储的网关设备的地址向网关设备发送设备管理通知消息; 使得网 关设备根据所述设备管理通知消息进行相应处理。
本发明实施例提供了一种通过网关设备进行设备管理的装置, 所述通过 网关设备进行设备管理的装置可以为网关设备, 也可以为终端, 通过向设备 管理服务器发送登记消息, 在所述登记消息中携带有网关设备的地址以及所 述网关设备下属终端标识, 使得当所述设备管理服务器需要向所述网关设备 下属设备进行设备管理时, 能够根据所述登记消息获取所述网关设备的地址, 将设备管理通知消息发给所述网关设备, 由所述网关设备根据所述设备管理 通知消息进行相应处理, 从而实现了通过网关设备对终端进行设备管理。
仍然如图 7 所示, 本发明实施例提供的一种通过网关设备进行设备管理 的装置, 还可以包括:
第二接收模块 702, 用于接收设备管理服务器发送的设备管理通知消息, 所述设备管理通知消息携带有被管理终端标识;
转发模块 703 , 用于根据所述被管理终端标识, 将所述设备管理通知消息 发送给所述被管理终端, 以便于所述被管理终端根据所述设备管理通知消息 同设备管理服务器建立会话, 从而接受所述设备管理服务器的管理。
本发明实施例提供的通过网关设备进行设备管理的装置, 所述通过网关 设备进行设备管理的装置可以为网关设备, 通过接收设备管理服务器发送的 设备管理通知消息, 并将所述设备管理通知消息转发给终端, 由所述终端同 设备管理服务器建立会话, 接受所述设备管理服务器的管理, 从而实现了设 备管理服务器通过网关设备对终端进行设备管理。
如图 8所示, 本发明实施例提供一种通过网关设备进行设备管理的装置, 除了包括第二发送模块 701以外, 还包括:
第三接收模块 802, 用于接收设备管理服务器发送的设备管理通知消息; 会话建立模块 803, 用于根据所述设备管理通知消息, 同设备管理服务器 建立会话, 接受所述设备管理服务器对其上映射的管理对象的操作;
管理操作模块 804, 用于根据所述操作, 对所述管理对象对应的终端进行 相应的操作。
本发明实施例提供一种通过网关设备进行设备管理的装置, 所述通过网 关设备进行设备管理的装置可以为网关设备, 通过向设备管理服务器发送登 记消息, 在所述登记消息中携带有网关设备的地址、 所述网关设备下属终端 标识, 使得当所述设备管理服务器需要对所述网关设备下属设备进行设备管 理时, 能够根据所述登记消息获取所述网关设备的地址, 将所述设备管理通 知发给所述网关设备, 从而与所述网关设备建立设备管理会话, 进而所述网 关设备接受所述设备管理服务器发送的对其上映射的管理对象的操作, 根据 所述操作命令对所述被管理终端进行相应的操作 , 从而实现了设备管理服务 器通过网关设备对终端进行设备管理。
如图 9 所示, 本发明实施例提供的通过网关设备进行设备管理的装置, 除了包括第二发送模块 701以外, 还包括:
第四接收模块 902, 用于接收网关设备发送的设备管理通知消息; 会话建立模块 903, 用于根据所述设备管理通知消息, 同设备管理服务器 建立会话, 接收所述设备管理服务器的管理操作。
本发明实施例提供一种通过网关设备进行设备管理的装置, 所述通过网 关设备进行设备管理的装置可以为终端, 通过向设备管理服务器发送登记消 息, 所述登记消息中携带有终端标识以及网关设备的地址, 使得设备管理服 务器能够根据所述登记消息, 将设备管理通知消息发送给网关设备, 由网关 设备转发给终端; 终端接收到所述设备管理通知消息后, 根据所述设备管理 通知消息, 同设备管理服务器建立会话, 接收所述设备管理服务器的管理操 作, 从而实现了设备管理服务器通过网关设备对终端进行设备管理。
需要说明的是, 在部署实际的 DM系统时, 可能由多个 DMS为不同的终端 和网关设备提供 DM服务, 每一个 DMS由一个服务器标识来唯一标识。 终端或 网关设备为了能够连接 DMS并接受相应的 DM服务, 必须在本地配置有与相应 DMS的服务器标识相对应的合法账户。 由于终端和网关设备所配置的 DM管理 账户情况可能各不相同, 所能够连接并接受 DM服务的 DMS也就各不一样, 在 某些情况下, 终端或网关设备上甚至并没有配置任何 DM管理账户。 因此, 在 不同的 DM账户配置条件下 , 可根据网关设备和终端的 DM账户配置状况, 然 后再从本发明实施例提供的技术方案中选择某一种或几种实施例进行设备管 理通知, 此为本领域技术人员根据本发明实施例所公开的内容能轻易想到的 变化, 理应在本发明的保护范围之内。 本领域普通技术人员可以理解实现上述实施例方法中的全部或部分步骤 是可以通过程序来指令相关的硬件完成, 所述的程序可以存储于计算机可读 存储介质中, 如 R0M/RAM、 磁碟或光盘等。
以上所述, 仅为本发明的具体实施方式, 但本发明的保护范围并不局限 于此, 任何熟悉本技术领域的技术人员在本发明揭露的技术范围内, 可轻易 想到变化或替换, 都应涵盖在本发明的保护范围之内。 因此, 本发明的保护 范围应所述以权利要求的保护范围为准。

Claims

权利 要求 书
1、 一种通过网关设备进行设备管理的方法, 其特征在于, 包括:
接收登记消息, 所述登记消息携带有终端标识、 网关设备的地址; 对所述终端标识、 所述网关设备的地址进行关联存储;
根据所述关联记录, 获取所述网关设备的地址;
根据所述网关设备的地址, 向所述网关设备发送设备管理通知消息, 以便 网关设备根据所述设备管理通知消息进行相应处理。
2、根据权利要求 1所述的通过网关设备进行设备管理的方法,其特征在于, 所述对所述终端标识、 所述网关设备的地址进行关联存储的步骤具体还包括: 若已存储有所述终端标识的关联记录,当所述关联记录中网关设备的地址与 登记消息中网关设备的地址相同时, 则不再对所述登记消息进行关联存储; 当 所述关联记录中网关设备的地址与登记消息中网关设备的地址不同时, 用登记 消息中网关设备的地址替换所述关联记录中网关设备的地址。
3、根据权利要求 1所述的通过网关设备进行设备管理的方法,其特征在于, 所述向所述网关设备发送设备管理通知消息的步 之后, 还包括:
网关设备接收所述设备管理通知消息, 所述设备管理通知消息携带有被管 理终端标识;
根据所述被管理终端标识, 网关设备将所述设备管理通知消息转发至所述 被管理终端, 以便于所述被管理终端根据所述设备管理通知消息同设备管理服 务器建立会话, 从而接受所述设备管理服务器的管理。
4、 根据权利要求 1所述的通过网关设备进行设备管理通知的方法, 其特征 在于, 所述向所述网关设备发送设备管理通知消息的步骤之后, 还包括:
网关设备接收所述设备管理通知消息;
根据所述设备管理通知消息, 网关设备同设备管理服务器建立会话, 接收 所述设备管理服务器对网关设备上映射的终端管理对象的操作;
根据所述操作, 对所述终端管理对象对应的终端进行相应的操作。
5、 根据权利要求 1所述的通过网关设备进行设备管理通知的方法, 其特征 在于, 所述接收登记消息的步骤具体包括:
接收网关设备发送的登记消息或者接收终端发送的登记消息。
6、 一种通过网关设备进行设备管理的方法, 其特征在于, 包括:
向设备管理服务器发送登记消息, 所述登记消息中携带有网关设备的地址、 终端标识, 以便于设备管理服务器对所述网关设备的地址和终端标识进行关联 存储, 并在设备管理服务器发送设备管理通知时, 根据存储的网关设备的地址 向网关设备发送设备管理通知消息; 使得网关设备根据所述设备管理通知消息 进行相应处理。
7、 一种设备管理服务器, 其特征在于, 包括:
第一接收模块, 用于接收登记消息, 所述登记消息携带有终端标识、 网关 设备的地址;
关联模块, 用于对所述终端标识、 所述网关设备的地址进行关联存储; 获取模块, 用于根据所述关联记录, 获取所述网关设备的地址;
第一发送模块, 用于根据所述网关设备的地址, 向所述网关设备发送设备 管理通知消息, 以便网关设备根据所述设备管理通知消息进行相应处理。
8、 一种通过网关设备进行设备管理的装置, 其特征在于, 包括:
第二发送模块, 用于向设备管理服务器发送登记消息, 所述登记消息中携 带有网关设备的地址、 终端标识, 以便于设备管理服务器对所述网关设备的地 址和终端标识进行关联存储, 并在设备管理服务器发送设备管理通知消息时, 根据存储的网关设备的地址向网关设备发送设备管理通知消息; 使得网关设备 根据所述设备管理通知消息进行相应处理。
9、根据权利要求 8所述的通过网关设备进行设备管理的装置,其特征在于, 还包括:
第二接收模块, 用于接收设备管理服务器发送的设备管理通知消息, 所述 设备管理通知消息携带有被管理终端标识; 转发模块, 用于根据所述被管理终端标识, 将所述设备管理通知消息发送 给所述被管理终端, 以便于所述被管理终端根据所述设备管理通知消息同设备 管理服务器建立会话, 从而接受所述设备管理服务器的管理。
10、 根据权利要求 8 所述的通过网关设备进行设备管理的装置, 其特征在 于, 还包括:
第三接收模块, 用于接收设备管理服务器发送的设备管理通知消息; 会话建立模块, 用于根据所述设备管理通知消息, 同设备管理服务器建立 会话, 接受所述设备管理服务器对网关设备上映射的终端管理对象的操作; 管理操作模块, 用于根据所述操作, 对所述终端管理对象对应的终端进行 相应的操作。
11、 根据权利要求 8至 10任意一项所述的通过网关设备进行设备管理的装 置, 其特征在于, 所述通过网关设备进行设备管理的装置为网关设备。
12、 根据权利要求 8 所述的通过网关设备进行设备管理的装置, 其特征在 于, 还包括:
第四接收模块, 用于接收网关设备发送的设备管理通知消息;
会话建立模块, 用于根据所述设备管理通知消息, 同设备管理服务器建立 会话, 接收所述设备管理服务器的管理操作。
1 3、 根据权利要求 8或 12所述的通过网关设备进行设备管理的装置, 其特 征在于, 所述通过网关设备进行设备管理的装置为终端。
PCT/CN2009/071711 2009-05-08 2009-05-08 通过网关设备进行设备管理的方法、装置及设备管理服务器 WO2010127508A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP09844260A EP2421197A4 (en) 2009-05-08 2009-05-08 METHOD AND APPARATUS FOR PERFORMING DEVICE MANAGEMENT BY GATEWAY DEVICE AND CORRESPONDING DEVICE MANAGEMENT SERVER
CN200980151721XA CN102246464A (zh) 2009-05-08 2009-05-08 通过网关设备进行设备管理的方法、装置及设备管理服务器
PCT/CN2009/071711 WO2010127508A1 (zh) 2009-05-08 2009-05-08 通过网关设备进行设备管理的方法、装置及设备管理服务器
US13/291,829 US20120059924A1 (en) 2009-05-08 2011-11-08 Method and apparatus for performing device management through a gateway device, and device management server

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2009/071711 WO2010127508A1 (zh) 2009-05-08 2009-05-08 通过网关设备进行设备管理的方法、装置及设备管理服务器

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/291,829 Continuation US20120059924A1 (en) 2009-05-08 2011-11-08 Method and apparatus for performing device management through a gateway device, and device management server

Publications (1)

Publication Number Publication Date
WO2010127508A1 true WO2010127508A1 (zh) 2010-11-11

Family

ID=43049927

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/071711 WO2010127508A1 (zh) 2009-05-08 2009-05-08 通过网关设备进行设备管理的方法、装置及设备管理服务器

Country Status (4)

Country Link
US (1) US20120059924A1 (zh)
EP (1) EP2421197A4 (zh)
CN (1) CN102246464A (zh)
WO (1) WO2010127508A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103118376A (zh) * 2011-11-16 2013-05-22 华为终端有限公司 向终端下发通知消息的方法、服务器、网关及系统
EP2740244B1 (en) * 2011-08-05 2020-07-01 BlackBerry Limited Character enablement in short message service
US10924895B2 (en) 2013-01-22 2021-02-16 Blackberry Limited Enhancing short message service addressing and routing

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101505550B (zh) * 2008-02-04 2012-08-22 华为技术有限公司 设备管理的方法和终端、装置、系统
GB2473019B (en) * 2009-08-27 2015-10-21 Wireless Data Services Ltd Device management
KR102059643B1 (ko) * 2012-07-06 2019-12-26 삼성전자주식회사 디바이스 관리 방법과 서버, 시스템 및 모바일 장치
US8838836B1 (en) 2013-06-25 2014-09-16 Actiontec Electronics, Inc. Systems and methods for sharing digital information between mobile devices of friends and family using multiple LAN-based embedded devices
US9525991B2 (en) 2013-06-25 2016-12-20 Actiontec Electronics, Inc. Systems and methods for sharing digital information between mobile devices of friends and family using embedded devices
CN104699491A (zh) * 2013-12-06 2015-06-10 中兴通讯股份有限公司 一种应用程序的升级处理方法及终端设备
US11689414B2 (en) * 2017-11-10 2023-06-27 International Business Machines Corporation Accessing gateway management console
CN111630816B (zh) * 2018-02-27 2022-06-03 村田机械株式会社 网关装置、通信系统、以及自动仓库系统
DE102020130231A1 (de) * 2020-11-16 2022-05-19 Workaround Gmbh Verfahren zur Steuerung eines tragbaren Benutzergerätes, tragbares Benutzergerät sowie Steuerungssystem
CN113422814A (zh) * 2021-06-16 2021-09-21 青岛易来智能科技股份有限公司 设备控制指令的发送方法和系统、存储介质及电子装置
CN114500341A (zh) * 2021-12-28 2022-05-13 福建升腾资讯有限公司 广域网下的终端实时管控方法及管控服务端

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100661006B1 (ko) * 2005-12-28 2006-12-22 주식회사 케이티 홈네트워크 단말 관리 시스템 및 그 방법
CN101268620A (zh) * 2005-09-21 2008-09-17 Lg电子株式会社 用于管理设备管理对象的设备管理系统和方法
WO2008154067A1 (en) * 2007-06-15 2008-12-18 Mformation Technologies Inc. System and method for automatic detection and reporting of the mapping between device identity and network address in wireless networks

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7515549B2 (en) * 2005-06-07 2009-04-07 Cisco Technology, Inc. Managing devices across NAT boundaries

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101268620A (zh) * 2005-09-21 2008-09-17 Lg电子株式会社 用于管理设备管理对象的设备管理系统和方法
KR100661006B1 (ko) * 2005-12-28 2006-12-22 주식회사 케이티 홈네트워크 단말 관리 시스템 및 그 방법
WO2008154067A1 (en) * 2007-06-15 2008-12-18 Mformation Technologies Inc. System and method for automatic detection and reporting of the mapping between device identity and network address in wireless networks

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2421197A4 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2740244B1 (en) * 2011-08-05 2020-07-01 BlackBerry Limited Character enablement in short message service
CN103118376A (zh) * 2011-11-16 2013-05-22 华为终端有限公司 向终端下发通知消息的方法、服务器、网关及系统
CN103118376B (zh) * 2011-11-16 2016-03-09 华为终端有限公司 向终端下发通知消息的方法、服务器、网关及系统
US10924895B2 (en) 2013-01-22 2021-02-16 Blackberry Limited Enhancing short message service addressing and routing

Also Published As

Publication number Publication date
EP2421197A4 (en) 2012-06-27
EP2421197A8 (en) 2012-04-11
US20120059924A1 (en) 2012-03-08
EP2421197A1 (en) 2012-02-22
CN102246464A (zh) 2011-11-16

Similar Documents

Publication Publication Date Title
WO2010127508A1 (zh) 通过网关设备进行设备管理的方法、装置及设备管理服务器
CN109842906B (zh) 一种通信的方法、装置及系统
US9247018B2 (en) Method and apparatus for cooperation between push devices
JP2023109789A (ja) ローカルエリアネットワーク(lan)をサポートする方法および装置
WO2019029525A1 (zh) 网络功能信息的管理方法及相关设备
US11750411B2 (en) Method of and devices for supporting selective forwarding of messages in a network of communicatively coupled communication devices
US9781579B2 (en) Method and device for realizing terminal WIFI talkback
US20100103851A1 (en) System for enabling communication over a wireless intermittently connected network
WO2017147772A1 (zh) 一种消息传输方法及核心网接口设备
WO2020224559A1 (zh) 群组管理方法、装置及系统
WO2010130174A1 (zh) 一种实现本地访问控制的方法及相应的通信系统
JP2017528074A5 (zh)
EP2309799A1 (en) A route optimization method and system
CN106576285B (zh) 一种apn配置方法、用户设备和配置服务器
WO2020073577A1 (en) Method and apparatus for supporting event monitoring
WO2012113329A1 (zh) 一种设备管理方法及装置
WO2022193086A1 (zh) 一种通信方法、通信装置和通信系统
WO2015070763A1 (zh) X2接口的自建立方法及装置
JP2018533853A (ja) 移動無線通信ネットワークに移動端末の接続を確立するための方法、及び無線アクセスネットワーク構成要素
US20240008117A1 (en) Dual-connection device enabling service advertisement and discovery of services between networks, user device and system
WO2018101452A1 (ja) 通信方法および中継装置
CN115499894A (zh) 网络切片调整方法、装置及设备
CN114980074A (zh) 基于虚拟局域网的数据通信方法、装置、设备及介质
CN116746214A (zh) 在电信网络与网关设备之间移动的ue的pdu会话连续性
KR102015413B1 (ko) 로컬 네트워크에서의 인터페이스 설정장치 및 방법

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 200980151721.X

Country of ref document: CN

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

Ref document number: 09844260

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2009844260

Country of ref document: EP