WO2012130048A1 - 设备管理系统中对网关进行初始化的方法及装置 - Google Patents
设备管理系统中对网关进行初始化的方法及装置 Download PDFInfo
- Publication number
- WO2012130048A1 WO2012130048A1 PCT/CN2012/072408 CN2012072408W WO2012130048A1 WO 2012130048 A1 WO2012130048 A1 WO 2012130048A1 CN 2012072408 W CN2012072408 W CN 2012072408W WO 2012130048 A1 WO2012130048 A1 WO 2012130048A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- server
- gateway
- information
- initialization
- module
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/4401—Bootstrapping
- G06F9/4416—Network booting; Remote initial program loading [RIPL]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/04—Network management architectures or arrangements
- H04L41/046—Network management architectures or arrangements comprising network management agents or mobile agents therefor
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0876—Aspects of the degree of configuration automation
- H04L41/0886—Fully automatic configuration
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/0213—Standardised network management protocols, e.g. simple network management protocol [SNMP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/0233—Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/04—Network management architectures or arrangements
- H04L41/052—Network management architectures or arrangements using standardised network management architectures, e.g. telecommunication management network [TMN] or unified network management architecture [UNMA]
Definitions
- the present invention relates to a device management (DM) technology, and in particular, to a method and apparatus for initializing a gateway in a DM system.
- DM device management
- the DM system provides a low-cost solution for third-party management and setting of terminal devices, such as managing and setting environment and configuration information in various functional objects of the mobile terminal, and solving problems encountered during use of the terminal devices.
- the device management operation of software and firmware installation and upgrade of the terminal device by the server in the wireless network (OTA, Over the Air) mode provides more personalized and personalized services, and improves the use of the terminal device. user experience.
- a third party can provide a server for an operator, service provider, or partner.
- the DM system includes a server and a terminal device, wherein the server is configured to send a management command to the terminal device through the device management interface; and the terminal device is configured to receive a management command from the server, and execute The received management command.
- the terminal device sets the client and management object (MO, Management Object) on its own.
- the client parses the received management command and instructs the management object to execute the management command.
- the management object is stored in a tree structure, and each of the branches can be regarded as an interface for the server to manage the terminal device for forwarding the management commands in the terminal device.
- These administrative commands can be a get command, a replace command, an execute command, a copy command, or a delete command.
- a device management method for a terminal device in a local area network through a gateway wherein the server and the gateway are in compliance with the DM specification, the server can manage the gateway through the DM protocol, and the gateway can also pass the DM protocol. Or other device management protocols to manage terminal devices.
- the gateway the information of the terminal device under the control of the local area network can be saved, and the server manages the terminal device indirectly through the management gateway.
- the gateway is a terminal device for the server, and the gateway is the terminal device under the gateway.
- a server, so the gateway is called a proxy server.
- the gateway acts as a proxy server to perform DM on the terminal device
- the server needs to initialize the gateway, and the gateway needs to perform initialization process on the terminal device for subsequent device management.
- the "bootstrap” process refers to the process of having the device have the ability to initiate a management session with the DM server. Devices that are not initialized cannot directly communicate with the server for DM sessions.
- the first initialization method Before the gateway and the terminal device are shipped from the factory, the initialization process is completed; the second initialization mode: setting a function card (Smartcard) storing the initialization information, and the terminal device physically connects the smartcard with itself. Obtain initialization information from the Smartcard, and use the obtained initialization information to complete the initialization process;
- Smartcard function card
- the third initialization mode the server obtains the terminal device identifier, such as the terminal device number or address, and then sends the initialization information to the terminal device having the terminal device identifier, and the terminal device uses the received initialization information to complete the initialization process, where the terminal The device identifier is sent to the server when the user who uses the terminal device actively registers, or is sent to the server when the terminal device just accesses the mobile network where the server is located, and the server can determine the terminal device according to the identifier of the terminal device;
- the fourth initialization mode the terminal device supports Hypertext Transfer Protocol over Secure Socket Layer (HTTPs) protocol, and the terminal device accesses the server through the HTTPS protocol acquisition method using a uniform resource identifier (URL, Uniform resource locator) to obtain initialization.
- HTTPs Hypertext Transfer Protocol over Secure Socket Layer
- the first method is to initialize the gateway before leaving the factory.
- the terminal device under the jurisdiction of the gateway accepts device management of multiple servers, it cannot set the corresponding server for the gateway before leaving the factory. Initialize the settings, so you need to use the last three initialization methods.
- the terminal device obtains the initialization information, it completes the initialization process itself, and does not involve how the gateway completes the initialization. Therefore, how the gateway completes the initialization process in the device management system is still an urgent problem to be solved.
- Embodiments of the present invention provide a method for initializing a gateway in a device management system, which can enable a gateway to complete an initialization process.
- Embodiments of the present invention provide an apparatus for initializing a gateway in a device management system, which enables a gateway to complete an initialization process.
- a method for initializing a gateway in a device management system comprising:
- the gateway acquires server information saved by the terminal device from the terminal device;
- the gateway determines the target server according to the obtained server information, and initiates an initialization request; the gateway performs initialization according to the initialization information received from the target server.
- An apparatus for initializing a gateway in a device management system comprising: acquiring a module, determining a mode a block initialization request module, a receiving module, and an initialization module, wherein the obtaining module is configured to receive server information from the terminal device and send the information to the determining module, and the determining module is configured to determine the target server according to the acquired server information, and notify the initialization request Module
- An initialization requesting module configured to initiate an initialization request according to the notification of the determining module, and a receiving module, configured to receive initialization information sent by the target server;
- a device for initializing a gateway in a device management system comprising: a saving module and a transceiver module, wherein
- the saving module is configured to save the server information
- the transceiver module is configured to send the server information saved by the saving module to the gateway.
- the gateway obtains the saved server information from the terminal device, determines the target server according to the acquired server information, and obtains the initialization information from the target server, and then initializes the obtained initialization information. Therefore, in the embodiment of the present invention, the initialization process of the gateway is simplified by the terminal, and the initialization path of the gateway is enriched, so that the gateway completes the initialization process.
- FIG. 1 is a schematic structural view of a prior art DM system
- FIG. 3 is a schematic structural diagram of a system for initializing a gateway according to an embodiment of the present invention
- FIG. 4 is a schematic structural diagram of an apparatus for initializing a gateway according to an embodiment of the present invention
- FIG. 5 is a schematic diagram of initializing a gateway according to an embodiment of the present invention
- Schematic diagram of the device two
- FIG. 8 is a schematic diagram of a DMAcc structure on a terminal device according to an embodiment of the present invention
- FIG. 9 is a schematic diagram of a DMAcc structure comparison on a gateway and a terminal device according to an embodiment of the present invention.
- the gateway Before the device management process exists in the presence of the gateway as a proxy server, a total of three initialization processes are required, including: the initialization process of the terminal device by the server, the initialization process of the terminal device by the gateway, and the initialization process of the gateway by the server.
- the embodiment of the invention provides a process for the server to initialize the gateway.
- the gateway acquires the saved server information from the terminal device, determines the target server according to the acquired server information, and obtains the initialization information of the corresponding target server from the target server, and then initializes the obtained initialization information.
- the initialization process causes the gateway to complete the initialization process.
- the gateway when the gateway initiates the initialization request, the gateway may directly interact with the target server, or may be assisted by the terminal device.
- the initializing information is sent to the target server, and the initialization result by using the information causes the gateway to switch from the initial state to the device management session state, and performs device management on the terminal device.
- Step 201 The gateway acquires server information stored by the terminal device from the terminal device.
- the stored server information is server information that the terminal device has initialized.
- the server information acquired from the terminal device is part of the DM account object (DMAcc, DM Account MO) of the corresponding server of the terminal device, and the DMAcc of the corresponding server stores the server on the terminal device.
- DMAcc DM account object
- Specific settings such as the server identifier, the address of the terminal device accessing the server, the user name or password, etc.
- the DMAcc of the corresponding server is sent to the terminal device or the terminal device before the terminal device is initialized before being initialized.
- Each server will correspond to a DMAcc on the terminal device;
- the server information may be a server identifier and corresponding initialization address information, or may be server identification information.
- Step 202 The gateway determines the target server according to the obtained server information, and initiates an initialization request.
- the target server to be initialized is also determined according to the server identification information that has been initialized by itself, that is, the gateway compares the acquired server information with the server information stored by itself, and obtains the obtained server information.
- the server information the server corresponding to the server information for removing the server information stored by itself is determined as the target server;
- a link with the target server may be established according to the target server identifier and the corresponding initialized address information, and an initialization request is directly sent to the determined target server through the link;
- the terminal device may also initiate an initialization request to the determined target server.
- the determined target server identifier needs to be sent to the terminal device.
- the gateway information may be further sent, and the gateway information may be provided to the terminal device by other entities, such as other terminal devices or other gateways, where the gateway information includes the gateway identifier and the gateway address information, and may be carried in the first notification message, and the terminal may be sent.
- the device After receiving the determined target server identifier, the device sends the gateway information to the target server that has the target server identifier, and the gateway information may be carried in the second notification message, and the target server needs to have the gateway information after receiving the gateway information.
- the gateway performs an initialization process;
- Step 203 The gateway receives the initialization information sent by the target server, and uses the initialization information to perform an initialization process.
- the acquired server information includes a server identifier
- Determining the target server according to the obtained server information includes: the gateway compares the acquired server identifier with the server identifier stored by the gateway, and removes the server information corresponding to the server identifier stored in the acquired server identifier.
- the server is determined to be the target server.
- the determining the target server according to the acquired server information includes: the gateway compares the acquired server address information with the server address information stored by itself, and the obtained server address information is included. The server corresponding to the server information for removing the server address information stored therein is determined as the target server.
- FIG. 3 is a schematic structural diagram of a system for initializing a gateway according to an embodiment of the present invention, including a terminal device, a target server, and a gateway, where
- a terminal device configured to send the saved server information to the gateway, and send an initialization request to the target server according to the target server information and/or the gateway information sent by the gateway;
- a gateway configured to determine a target server according to the acquired server information, initiate an initialization request to the target server, or send a target server identifier and/or gateway information to the terminal device, and receive the target service.
- the initialization information sent by the server is initialized;
- the target server is configured to accept an initialization request initiated by the gateway or the terminal device, and send initialization information to the gateway according to the initialization request.
- the gateway is further configured to determine the target server according to the server information stored by the gateway itself.
- the broken line indicates that the wireless connection is used between the terminal device, the gateway, and the target server.
- the terminal device, the gateway, and the target server may be connected in a wired or wireless manner, which is not limited herein.
- the device is also a gateway, and includes: an obtaining module, a determining module initialization request module, a receiving module, and an initialization module, where
- An obtaining module configured to receive server information from the terminal device, and send the information to the determining module;
- a determining module configured to determine a target server according to the obtained server information, and notify the initialization request module
- An initialization requesting module configured to initiate an initialization request according to the notification of the determining module, and a receiving module, configured to receive initialization information sent by the target server;
- an initialization module configured to initialize according to the received initialization information.
- the determining module is further configured to determine the target server according to the server information stored by the gateway itself.
- the initialization request module further includes a first initialization request module, configured to initiate a connection to an address in the initialization address information of the target server, requesting initialization information.
- the initialization request module further includes a second initialization request module, configured to The target server information is sent to the terminal device.
- FIG. 5 is a schematic structural diagram of a device for initializing a gateway according to an embodiment of the present disclosure, that is, a terminal device, including: a storage module and a transceiver module, where
- the transceiver module is configured to send the server information saved by the save module to the gateway.
- the saving module further includes a first saving submodule, configured to save initial address information of the target server;
- the transceiver module further includes a first transceiver sub-module, configured to send initial address information of the target server saved by the first save sub-module to the gateway.
- the transceiver module further includes a second transceiver sub-module for receiving the target server information sent by the gateway and sending an initialization request to the target server.
- the server information saved by the terminal device may be one or two or more, which is not limited herein.
- the server information saved by the gateway may be one or two or more, which is not limited herein.
- the gateway confirms the target server it can also be determined as one or two or more, which are all performed by the above method.
- Step 601 The initialization process has been completed between the terminal device and the target server.
- the terminal device sets DMAcc for the target server, and in the DMAcc, saves the target server identifier and corresponding initialization address information, such as the identifier of the target server and the initialized URL, that have completed the initialization process;
- the address of the server identified as 1234 is stored in the initialization process, and the terminal device or gateway that meets the initialization condition can obtain the command through HTTPs.
- the identified server performs the obtaining operation and obtains the initialization information from the server.
- the server name "testsever”, the URL address "www.abc.com” and the URL address for obtaining the initialization information "www.abc.” are also included. Com/bootstrap ";
- Step 602 The terminal device establishes a connection with the gateway, and the gateway sends a DM session to the terminal device, and obtains all the server identifiers that have been initialized;
- the gateway may also initiate other types of information interaction with the terminal device, such as a Dynamic Host Configuration Protocol (DHCP);
- DHCP Dynamic Host Configuration Protocol
- step 601 if the DM session is sent, in step 601, the initialization process of the terminal device for the gateway needs to be completed, and if it is other forms of information interaction, it is not required;
- the gateway obtains the DMAcc corresponding to the server through the obtaining command in the DM session, and cannot acquire all the DMAccs due to the rights protection, but can obtain part of the DMAcc, including but not Limited to the server ID.
- Step 603 The gateway compares the obtained server identifier that is initialized with a server identifier that has been initialized, and determines a server identifier that is not initialized, that is, a server identifier of the target server.
- the DMAcc of the gateway includes the server information identified as 123 and the server information identified as 456, but the obtained server information is the server information of the identifier 789, and then the gateway compares and determines An initialization request is sent to the server identified as 789, so that the server identifiable 789 is used to proxy the terminal device DM;
- Step 605 The gateway initiates an HTTPs request to the initial address of the target server.
- the target server authenticates the gateway and can perform the DM proxy management terminal device, and then sends the initialization information of the target server to the gateway, and the gateway completes the reception.
- Step 701 The initialization process has been completed between the terminal device and the target server.
- Step 702 The terminal device establishes a connection with the gateway, and the gateway sends a DM session to the terminal device to obtain all the server identifiers that have been initialized.
- the gateway may also initiate other types of information interaction with the terminal device, such as a dynamic host configuration protocol (DHCP).
- DHCP dynamic host configuration protocol
- step 601 if the DM session is sent, in step 601, the initialization process of the terminal device for the gateway needs to be completed, and if it is other forms of information interaction, it is not required;
- the gateway obtains the DMAcc corresponding to the server through the obtaining command in the DM session, and cannot acquire all the DMAccs due to the rights protection, but can obtain part of the DMAcc, including but not Limited to the server ID.
- Step 703 The gateway completes the obtained server identifier for initializing and completing the existing one.
- the initialized server identifier is compared to determine the server identifier that is not initialized, that is, the server identifier of the target server;
- Step 704 The gateway initiates a DM session to the terminal device, and notifies the terminal device of the server identifier and the gateway information of the target server.
- the gateway information may be the public network identifier of the gateway and/or the public network address
- the used DM session is the first notification message that is set, that is, the server identifier and the gateway information of the target server are carried in the first notification message.
- the gateway determines that it needs to send an initialization request to the server with the identifier 789 by comparing, and sends the first notification message to the terminal device:
- Step 705 After receiving the server identifier and gateway information of the target server, the terminal device initiates a DM session to the target server, and sends the gateway information to the target server.
- the terminal determines, according to the notification message, that the gateway sends an initialization request to the target server with the identifier 789, and determines the gateway information, and the terminal generates a second notification message, which carries the gateway information and sends the information to the gateway.
- the target server, the second notification message is:
- Step 706 After receiving the second notification message, the target server confirms that the gateway having the gateway information carried by the message initiates an initialization request, and then sends a target to the gateway after authenticating the gateway to be legal and can perform the DM proxy management terminal device.
- the initialization information of the server after the gateway receives the initialization process, acts as a proxy server of the target server, and performs proxy DM on the terminal device.
- the embodiment of the present invention provides a method for detecting, by a gateway, a difference between server information that has been initialized by a terminal device under control, thereby determining server information to be initialized, and performing a corresponding server initialization method according to the information, thereby
- the server corresponding to the proxy can perform DM management on the terminal device.
- the gateway may directly initiate to the corresponding server, or may be initiated by the terminal device.
- the method, system, and apparatus provided by the embodiments of the present invention simplify the process of initializing the gateway with the multiple servers when the terminal device performs DM management by multiple servers, thereby avoiding that the gateway cannot determine the server to be initialized.
- the real-time selection and initialization process during use reduces the burden on the gateway.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Computing Systems (AREA)
- Health & Medical Sciences (AREA)
- Automation & Control Theory (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Small-Scale Networks (AREA)
Abstract
本发明公开了一种设备管理系统中对网关进行初始化的方法及装置,其中,该方法包括:网关从终端设备获取该终端设备保存的服务器信息;网关根据所获取的服务器信息确定目标服务器,发起初始化请求;网关根据从目标服务器接收的初始化信息,进行初始化。本发明使得网关在使用过程中完成初始化过程。
Description
设备管理系统中对网关进行初始化的方法及装置
本申请要求于 2011 年 3 月 30 日提交中国专利局、 申请号为 201110078464.0、 发明名称为 "设备管理系统中对网关进行初始化的方法及装 置"的中国专利申请的优先权, 其全部内容通过引用结合在本申请中。
技术领域
本发明涉及设备管理 (DM, Device Management )技术, 特别涉及一种 DM系统中对网关进行初始化的方法及装置。
背景技术
目前, 已经制定了 DM统一规范。 DM系统提供了一种低成本方案, 用于 第三方管理和设置终端设备,如管理和设置移动终端各个功能对象中的环境和 配置信息,解决这些终端设备在使用过程中遇到的问题。举一个例子进行说明, 通过无线网络(OTA, Over the Air )方式由服务器对终端设备进行软件和固件 的安装及升级等设备管理操作,提供更加人性化和个性化的服务,提高使用终 端设备的用户体验。 在这里, 第三方可以为运营商、 业务提供商或合作方提供 的服务器。 图 1为现有技术 DM系统的结构示意图, 该 DM系统包括服务器及终端 设备, 其中, 服务器, 用于通过设备管理接口向终端设备发送管理命令; 终端设备, 用于从服务器接收管理命令, 执行该接收的管理命令。 终端设备在自身设置了客户端及管理对象( MO, Management Object )。 客户端解析该接收的管理命令, 指示管理对象执行该管理命令。 管理对象釆用 树形结构存储,其中的每一个树枝都可以被认为是一个服务器对终端设备进行 管理的接口, 用于在终端设备中转发这些管理命令。这些管理命令可以为获取 命令、 替换命令、 执行命令、 复制命令或删除命令等。
随着技术的发展, 还存在服务器通过网关 (GW, Gateway )对局域网内 终端设备进行设备管理方法, 其中,服务器和网关都符合 DM规范,服务器可 以通过 DM协议管理网关, 网关也可以通过 DM协议或其他设备管理协议管 理终端设备。 在网关中, 可以保存局域网内所管辖终端设备的信息, 服务器通 过管理网关, 间接对终端设备管理, 此时网关对于服务器来说, 就是一个终端 设备, 而网关对于网关下的终端设备, 则是一个服务器, 因此网关称为代理服 务器。
在网关作为代理服务器对终端设备进行 DM之前,服务器需要对网关进行 初始化过程,网关需要对终端设备进行初始化过程,以便进行后续的设备管理。
初始化(Bootstrap )过程是指, 使得设备具备能够与 DM服务器发起管 理会话的能力的过程。 没有进行初始化的设备无法与服务器直接进行 DM会 话。
对于目前的 DM规范, 有四种进行初始化的方式, 以下分别进行说明。 第一种初始化方式: 在网关和终端设备出厂前, 就已经完成初始化过程; 第二种初始化方式: 设置存储有初始化信息的功能卡(Smartcard ), 终端 设备将该 Smartcard与自身进行物理连接后, 从 Smartcard上获取初始化信息, 釆用所获取的初始化信息完成初始化过程;
第三种初始化方式: 服务器获取终端设备标识, 比如终端设备号码或地 址, 然后将初始化信息发送给具有该终端设备标识的终端设备, 终端设备釆用 所接收的初始化信息完成初始化过程,这里的终端设备标识是使用该终端设备 的用户主动注册时发送给服务器的,或者终端设备刚接入到服务器所在的移动 网络时发送给服务器的, 服务器根据该终端设备标识就可以确定终端设备;
第四种初始化方式:终端设备支持超文本传输( HTTPs, Hypertext Transfer Protocol over Secure Socket Layer )协议, 终端设备通过 HTTPS协议获取方式 使用统一资源标识符( URL , Uniform resource locator )访问服务器, 获取到初 始化信息, 釆用所获取的初始化信息完成初始化过程。 以上四种初始化方式中, 第一种方式为出厂前对网关进行初始化方式,但 是如果网关所管辖的终端设备接受多个服务器的设备管理时,并无法在出厂前 为网关设置对应这所有服务器的初始化设置, 因此, 就需要釆用后三种初始化 方式。 但是, 后三种初始化方式中, 都是终端设备获取到初始化信息后, 自身 完成初始化过程, 而不涉及网关如何完成初始化。 因此, 网关如何在设备管理系统中完成初始化过程,仍然是一个亟待解决 的问题。
发明内容
本发明实施例提供一种设备管理系统中对网关进行初始化的方法,该方法 能够使得网关完成初始化过程。
本发明实施例提供一种设备管理系统中对网关进行初始化的装置,该装置 能够使得网关完成初始化过程。
本发明的技术方案是这样实现的:
一种设备管理系统中对网关进行初始化的方法, 该方法包括:
网关从终端设备获取该终端设备保存的服务器信息;
网关根据所获取的服务器信息确定目标服务器, 发起初始化请求; 网关根据从目标服务器接收的初始化信息, 进行初始化。
一种设备管理系统中对网关进行初始化的装置, 包括: 获取模块、 确定模
块初始化请求模块、 接收模块及初始化模块, 其中, 获取模块, 用于从终端设备接收服务器信息, 发送给确定模块; 确定模块, 用于根据所获取的服务器信息, 确定目标服务器, 并通知初始 化请求模块;
初始化请求模块, 用于根据所述确定模块的通知, 发起初始化请求; 接收模块, 用于接收目标服务器发送的初始化信息;
初始化模块, 用于根据接收的所述初始化信息进行初始化。 一种设备管理系统中对网关进行初始化的装置, 包括: 保存模块及收发模 块, 其中,
保存模块, 用于保存服务器信息; 收发模块, 用于将保存模块保存的服务器信息发送给网关。
本发明实施例网关从终端设备获取所保存的服务器信息,根据所获取的服 务器信息确定目标服务器,从目标服务器获取初始化信息后, 釆用所获取的初 始化信息进行初始化。 因此, 本发明实施例通过终端辅助简化网关的初始化过 程, 丰富网关的初始化途径, 使得网关完成初始化过程。 附图说明
图 1为现有技术 DM系统的结构示意图;
图 3为本发明实施例提供的对网关进行初始化的系统结构示意图; 图 4为本发明实施例提供的对网关进行初始化的装置一结构示意图; 图 5为本发明实施例提供的对网关进行初始化的装置二结构示意图;
图 8为本发明实施例提供的在终端设备上的 DMAcc结构示意图; 图 9为本发明实施例提供的在网关上和在终端设备上的 DMAcc结构比较 示意图。
具体实施方式
为使本发明的目的、技术方案及优点更加清楚明白, 以下参照附图并举实 施例, 对本发明作进一步详细说明。
在存在网关作为代理服务器的情况下进行设备管理过程之前,一共需要三 个初始化过程, 包括: 服务器对终端设备进行初始化过程, 网关对终端设备进 行初始化过程,及服务器对网关进行初始化过程。 本发明实施例就提供一种服 务器对网关进行初始化过程。
具体地, 网关从终端设备获取所保存的服务器信息,根据所获取的服务器 信息确定目标服务器,从目标服务器获取对应目标服务器的初始化信息后, 釆 用所获取的初始化信息进行初始化。
始化途径, 使得网关完成初始化过程。
在本发明实施例中, 网关在发起初始化请求时, 可以与目标服务器交互可 以直接进行, 或者由终端设备辅助进行。
在本发明实施例中, 进行初始化为目标服务器下发初始化信息, 通过这些 信息进行的初始化结果使得网关由初始状态转换到设备管理会话状态,对终端 设备进行设备管理。
为:
步骤 201、 网关从终端设备获取该终端设备所存储的服务器信息; 在本步骤中,所存储的服务器信息就是终端设备已经进行初始化的服务器 信息;
在该步骤中, 从终端设备获取的服务器信息就是终端设备对应服务器的 DM帐户对象(DMAcc, DM Account MO ) 中的部分信息, 在该对应服务器 的 DMAcc中, 保存了服务器在该终端设备上的特定设置, 比如服务器标识、 该终端设备访问该服务器的地址、 用户名或密码等, 该对应服务器的 DMAcc 在终端设备进行初始化之前,由该对应服务器发送给终端设备或终端设备出厂 前就设置好, 每一个服务器都会在终端设备上对应一个 DMAcc;
在该步骤中,服务器信息可以为服务器标识和对应的初始化地址信息, 或 者, 为服务器标识信息。
步骤 202、 网关根据所获取的服务器信息确定目标服务器, 发起初始化请 求;
在本步骤中,在确定目标服务器时,还根据自身已经初始化的服务器标识 信息,确定要进行初始化的目标服务器,也就是网关将所获取的服务器信息与 自身存储的服务器信息进行比较,将所获取的服务器信息中的, 去除自身存储 的服务器信息的服务器信息所对应的服务器确定为目标服务器;
在本步骤中,在确定目标服务器后, 可以根据目标服务器标识和对应的初 始化地址信息建立与目标服务器之间的链路,通过链路直接向确定的目标服务 器发起初始化请求;
在本步骤中,在确定目标服务器后,也可以通过终端设备向确定的目标服 务器发起初始化请求,这时,就需要向终端设备发送所确定的目标服务器标识,
还可以进一步发送网关信息, 该网关信息也可以由其他实体, 比如其他终端设 备或其他网关, 提供给终端设备, 网关信息包括网关标识和网关地址信息, 可 以携带在第一通知消息中发送, 终端设备接收到该所确定的目标服务器标识 后, 向具有该目标服务器标识的目标服务器发送网关信息, 该网关信息可以携 带在第二通知消息中发送,目标服务器接收到后要为具有该网关信息的网关进 行初始化过程;
步骤 203、 网关接收到目标服务器发送的初始化信息, 釆用该初始化信息 进行初始化过程。
在该实施例中, 如果所获取的服务器信息包括服务器标识;
所述根据所获取的服务器信息确定目标服务器包括:网关将所获取的服务 器标识与自身存储的服务器标识进行比较,将所获取的服务器标识中的, 去除 自身存储的服务器标识的服务器信息所对应的服务器确定为目标服务器。
如果所获取的服务器信息包括服务器地址信息;所述根据所获取的服务器 信息确定目标服务器包括:网关将所获取的服务器地址信息与自身存储的服务 器地址信息进行比较,将所获取的服务器地址信息中的, 去除自身存储的服务 器地址信息的服务器信息所对应的服务器确定为目标服务器。
图 3为本发明实施例提供的对网关进行初始化的系统结构示意图,包括终 端设备、 目标服务器和网关, 其中,
终端设备, 用于将保存的服务器信息发送给网关,根据网关发送的目标服 务器信息和 /或网关信息向目标服务器发送初始化请求;
网关, 用于根据所获取的服务器信息, 确定目标服务器, 向目标服务器发 起初始化请求或向终端设备发送目标服务器标识和 /或网关信息, 接收目标服
务器发送的初始化信息, 进行初始化;
目标服务器, 用于接受网关或终端设备发起的初始化请求,根据初始化请 求向网关发送初始化信息。
在该实施例中, 所述网关, 还用于根据网关自身存储的服务器信息, 确定 目标服务器。
在图 3中,折线表示了终端设备、网关及目标服务器之间都釆用无线连接。 其他实施例中, 终端设备、 网关及目标服务器两两之间可以釆用有线或无线的 方式连接, 此处不再限定。
图 4为本发明实施例提供的对网关进行初始化的装置一结构示意图,该装 置也就是网关, 包括: 获取模块、 确定模块初始化请求模块、 接收模块及初始 化模块, 其中,
获取模块, 用于从终端设备接收服务器信息, 发送给确定模块;
确定模块, 用于根据所获取的服务器信息, 确定目标服务器, 并通知初始 化请求模块;
初始化请求模块, 用于根据所述确定模块的通知, 发起初始化请求; 接收模块, 用于接收目标服务器发送的初始化信息;
初始化模块, 用于根据接收的所述初始化信息进行初始化。
在该实施例中, 所述确定模块, 还用于根据网关自身存储的服务器信息, 确定目标服务器。
在该实施例中, 所述初始化请求模块, 还包括第一初始化请求模块, 用于 向所述目标服务器的初始化地址信息中的地址发起连接, 请求初始化信息。
在该实施例中, 所述初始化请求模块, 还包括第二初始化请求模块, 用于
向终端设备发送目标服务器信息。
图 5为本发明实施例提供的对网关进行初始化的装置二结构示意图,也就 是终端设备, 包括: 保存模块及收发模块, 其中,
保存模块, 用于保存服务器信息;
收发模块, 用于将保存模块保存的服务器信息发送给网关。
在该实施例中, 所述保存模块还包括第一保存子模块, 用于保存目标服务 器的初始化地址信息;
所述收发模块还包括第一收发子模块,用于将第一保存子模块保存的目标 服务器的初始化地址信息发送给网关。
在该实施例中, 收发模块还包括第二收发子模块, 用于接收网关发送的目 标服务器信息和, 向目标服务器发送初始化请求。
在上述过程中, 终端设备所保存的服务器信息可以为一个,也可以为两个 及以上, 这里不再限定。 网关所保存的服务器信息可以为一个, 也可以为两个 及以上, 这里不限定。 在网关确认目标服务器时, 也可以确定为一个或两个及 以上, 都是釆用上述方法进行的。
以下举两个具体实施例说明本发明实施例。 体步骤为:
步骤 601、 终端设备和目标服务器之间已经完成了初始化过程;
在该步骤中, 终端设备针对该目标服务器设置了 DMAcc , 在 DMAcc中, 保存了已经完成了初始化过程的目标服务器标识及对应的初始化地址信息,比 如目标服务器的标识和初始化的 URL;
举一个例子, 如图 8所示, 在终端设备设置的 DMAcc中, 保存了一个标 识为 1234的服务器在初始化过程中的地址, 符合初始化条件的终端设备或网 关都可以通过 HTTPs获取命令向具有该标识的服务器进行获取操作, 从服务 器中获取到初始化信息, 在图 8 中, 还包括服务器的名称 "testsever" , URL 地 址 " www. abc.com " 以 及 获 取 初 始 化 信 息 的 URL 地 址 "www. abc . com/bootstrap ";
步骤 602、 终端设备与网关建立连接, 网关向终端设备发送 DM会话, 获 取所有已经进行初始化的服务器标识;
在本步骤中, 网关也可以发起和终端设备其他形式的信息交互, 比如动态 主机配置协议(DHCP, Dynamic Host Configuration Protocol )等;
在本步骤中, 如果发送 DM会话, 则在步骤 601中, 需要完成终端设备针 对网关的初始化过程, 如果是其他形式的信息交互, 则不需要;
在本步骤中, 如果釆用 DM会话, 则网关通过 DM会话中的获取命令, 获取服务器对应的 DMAcc, 获取时由于权限保护, 无法获取全部的 DMAcc, 但是可以获取部分的 DMAcc, 其中包括但不限于服务器标识。
步骤 603、 网关将所获取到的进行初始化的服务器标识与自身已有的完成 初始化的服务器标识进行比较, 确定未进行初始化的服务器标识,也就是目标 服务器的服务器标识;
在本步骤中, 如图 9所示, 比如网关的 DMAcc包括了标识为 123的服务 器信息及标识为 456的服务器信息,但是获取到的服务器信息为标识 789的服 务器信息, 则网关比较后, 确定需要向标识为 789的服务器发送初始化请求, 以便替代标识为 789的服务器对终端设备进行代理 DM;
步骤 604、 网关向终端设备获取目标服务器的初始化地址信息; 在本步骤中, 网关向终端设备发送目标服务器的标识, 终端设备返回给网 关该目标服务器的初始化地址信息;
步骤 605、 网关向目标服务器的初始化地址发起 HTTPs请求, 目标服务 器接收到该请求后,认证该网关合法且可以进行 DM代理管理终端设备后, 向 网关发送目标服务器的初始化信息, 网关接收到后完成初始化,作为目标服务 器的代理服务器, 对终端设备进行代理设备管理;
在本步骤中, 目标服务器如何认证网关的过程可以釆用现有技术进行, 这 里不再赘述。 体步骤为:
步骤 701、 终端设备和目标服务器之间已经完成了初始化过程;
步骤 702、 终端设备与网关建立连接, 网关向终端设备发送 DM会话, 获 取所有已经进行初始化的服务器标识;
在本步骤中, 网关也可以发起和终端设备其他形式的信息交互, 比如动态 主机西己置协议 ( DHCP, Dynamic Host Configuration Protocol )等;
在本步骤中, 如果发送 DM会话, 则在步骤 601中, 需要完成终端设备针 对网关的初始化过程, 如果是其他形式的信息交互, 则不需要;
在本步骤中, 如果釆用 DM会话, 则网关通过 DM会话中的获取命令, 获取服务器对应的 DMAcc, 获取时由于权限保护, 无法获取全部的 DMAcc, 但是可以获取部分的 DMAcc, 其中包括但不限于服务器标识。
步骤 703、 网关将所获取到的进行初始化的服务器标识与自身已有的完成
初始化的服务器标识进行比较, 确定未进行初始化的服务器标识,也就是目标 服务器的服务器标识;
步骤 704、 网关向终端设备发起 DM会话, 向终端设备通知目标服务器的 服务器标识及网关信息;
在本步骤中, 网关信息可以为网关的公网标识和 /或公网地址,釆用的 DM 会话为设置的第一通知消息,即在第一通知消息中携带目标服务器的服务器标 识及网关信息;
例如, 网关通过比较得知确定需要向标识为 789 的服务器发送初始化请 求, 则向终端设备发送第一通知消息为:
<Alert>
<Data>2345</Data>
<Item>
<Data>ServerID=789</Data>
<Data>Gateway Address=213.14.12.156和 /或 Gw ID=Gwl234</Data> </Item>
</Alert>
步骤 705、 终端设备接收到目标服务器的服务器标识及网关信息后, 向目 标服务器发起 DM会话, 将网关信息发送给目标服务器;
在本步骤中, 比如终端接收到通知消息后, 根据该通知消息确定网关要向 标识为 789的目标服务器发送初始化请求, 同时确定网关信息, 终端生成第二 通知消息, 携带有网关信息, 发送给目标服务器, 该第二通知消息为:
<Alert>
<Data>2346</Data>
<Item>
<Data>Gateway Address=213.14.12.156和 /或 Gw ID=Gwl234</Data> </Item>
</Alert>
步骤 706、 目标服务器接收到该第二通知消息后, 确认具有该消息携带的 网关信息的网关发起初始化请求,则当认证该网关为合法的且可以进行 DM代 理管理终端设备后, 向网关发送目标服务器的初始化信息, 网关接收到后完成 初始化过程, 作为目标服务器的代理服务器, 对终端设备进行代理 DM。
可以看出,本发明实施例提供了一种由网关检测与所管辖终端设备已经进 行了初始化的服务器信息差别,从而确定要进行初始化的服务器信息并根据该 信息进行对应的服务器的初始化方法,从而可以代理所对应的服务器对终端设 备进行 DM管理。在进行对应的服务器的初始化过程中,可以由网关直接向该 对应的服务器发起, 也可以由终端设备辅助发起。
因此, 本发明实施例提供的方法、 系统及装置简化了终端设备由多个服务 器进行 DM管理时, 网关分别与这多个服务器进行初始化的过程,避免了网关 无法确定要进行初始化的服务器,在使用过程中进行实时选择并进行初始化过 程, 降低了网关的负担。
以上所述仅为本发明的较佳实施例而已, 并不用以限制本发明, 凡在本发 明的精神和原则之内, 所做的任何修改、 等同替换、 改进等, 均应包含在本发 明保护的范围之内。
Claims
1、 一种设备管理系统中对网关进行初始化的方法, 其特征在于, 该方法 包括:
网关从终端设备获取该终端设备保存的服务器信息;
网关根据所获取的服务器信息确定目标服务器, 发起初始化请求; 网关根据从目标服务器接收的初始化信息, 进行初始化。
2、 如权利要求 1所述的方法, 其特征在于, 在网关从终端设备获取该终 端设备保存的服务器信息之前, 所述方法还包括:
所述目标服务器完成对终端设备的初始化,所述网关完成对终端设备的初 始化。
3、 如权利要求 1所述的方法, 其特征在于,
在所述发起初始化请求之前,还包括: 网关从终端设备获取目标服务器的 初始化地址信息;
所述发起初始化请求为:
网关向所述目标服务器的初始化地址信息中的地址发起连接,请求初始化 信息。
4、 如权利要求 1所述的方法, 其特征在于, 所述发起初始化请求包括: 网关向终端设备发送目标服务器信息;
在所述发起初始化请求之后, 该方法还包括:
终端设备根据目标服务器信息向目标服务器发送第二初始化请求; 所述第二初始化请求包括网关信息。
5、 如权利要求 4所述的方法, 其特征在于, 所述网关向终端设备发送目 标服务器信息时, 所述网关还向终端设备发送网关信息。
6、 如权利要求 1、 3或 4所述的方法, 其特征在于, 所获取的服务器信息 包括服务器标识;
所述根据所获取的服务器信息确定目标服务器包括:网关将所获取的服务 器标识与自身存储的服务器标识进行比较,将所获取的服务器标识中的, 去除 自身存储的服务器标识的服务器信息所对应的服务器确定为目标服务器。
7、 如权利要求 1、 3或 4所述的方法, 其特征在于, 所获取的服务器信息 包括服务器地址信息;
所述根据所获取的服务器信息确定目标服务器包括:网关将所获取的服务 器地址信息与自身存储的服务器地址信息进行比较,将所获取的服务器地址信 息中的,去除自身存储的服务器地址信息的服务器信息所对应的服务器确定为 目标服务器。
8、 一种设备管理系统中对网关进行初始化的装置, 其特征在于, 包括: 获取模块、 确定模块初始化请求模块、 接收模块及初始化模块, 其中,
获取模块, 用于从终端设备接收服务器信息, 发送给确定模块; 确定模块, 用于根据所获取的服务器信息, 确定目标服务器, 并通知初始 化请求模块;
初始化请求模块, 用于根据所述确定模块的通知, 发起初始化请求; 接收模块, 用于接收目标服务器发送的初始化信息;
初始化模块, 用于根据接收的所述初始化信息进行初始化。
9、 如权利要求 8所述的装置, 其特征在于, 所述确定模块, 还用于根据 网关自身存储的服务器信息, 确定目标服务器。
10、 如权利要求 8或 9所述的装置, 其特征在于, 所述初始化请求模块, 包括第一初始化请求模块,用于向所述目标服务器的初始化地址信息中的地址 发起连接, 请求初始化信息。
11、 如权利要求 8或 9所述的装置, 其特征在于, 所述初始化请求模块, 包括第二初始化请求模块, 用于向终端设备发送目标服务器信息。
12、 一种设备管理系统中对网关进行初始化的装置, 其特征在于, 包括: 保存模块及收发模块, 其中, 保存模块, 用于保存服务器信息; 收发模块, 用于将保存模块保存的服务器信息发送给网关。
13、 如权利要求 12所述的装置, 其特征在于, 所述保存模块还包括第一 保存子模块, 用于保存目标服务器的初始化地址信息; 所述收发模块还包括第一收发子模块,用于将第一保存子模块保存的目标 服务器的初始化地址信息发送给网关。
14、 如权利要求 12所述的装置, 其特征在于, 收发模块还包括第二收发子 模块, 用于接收网关发送的目标服务器信息, 向目标服务器发送初始化请求。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP12763114.1A EP2693691B1 (en) | 2011-03-30 | 2012-03-16 | Method and apparatus for initializing gateway in device management system |
US14/041,133 US9417887B2 (en) | 2011-03-30 | 2013-09-30 | Method and apparatus for bootstrapping gateway in device management system |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201110078464.0 | 2011-03-30 | ||
CN2011100784640A CN102724050A (zh) | 2011-03-30 | 2011-03-30 | 设备管理系统中对网关进行初始化的方法及装置 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/041,133 Continuation US9417887B2 (en) | 2011-03-30 | 2013-09-30 | Method and apparatus for bootstrapping gateway in device management system |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2012130048A1 true WO2012130048A1 (zh) | 2012-10-04 |
Family
ID=46929430
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2012/072408 WO2012130048A1 (zh) | 2011-03-30 | 2012-03-16 | 设备管理系统中对网关进行初始化的方法及装置 |
Country Status (4)
Country | Link |
---|---|
US (1) | US9417887B2 (zh) |
EP (1) | EP2693691B1 (zh) |
CN (1) | CN102724050A (zh) |
WO (1) | WO2012130048A1 (zh) |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103888289B (zh) * | 2014-02-20 | 2017-05-17 | 下一代互联网关键技术和评测北京市工程研究中心有限公司 | 一种网关的管控方法、网关、管控设备与系统 |
US9923764B2 (en) * | 2014-11-19 | 2018-03-20 | Parallel Wireless, Inc. | HealthCheck access point |
CN106330401A (zh) * | 2016-08-30 | 2017-01-11 | 中兴长天信息技术(南昌)有限公司 | 一种用于物联网的lora无线通信网络终端设备快速初始化的方法 |
CN106534364B (zh) * | 2016-12-15 | 2019-11-08 | 新奥科技发展有限公司 | 一种网关恢复出厂设置的方法及网关 |
WO2020193280A1 (en) * | 2019-03-28 | 2020-10-01 | Inventio Ag | Method and system for commissioning of a communication gateway |
US20230342163A1 (en) * | 2022-04-24 | 2023-10-26 | Vmware, Inc. | Distribution of bootstrap management for application monitoring |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6490617B1 (en) * | 1998-06-09 | 2002-12-03 | Compaq Information Technologies Group, L.P. | Active self discovery of devices that participate in a network |
CN101127631A (zh) * | 2006-08-15 | 2008-02-20 | 华为技术有限公司 | 针对网络中设备实现配置管理的方法及系统 |
CN101540996A (zh) * | 2009-04-17 | 2009-09-23 | 深圳华为通信技术有限公司 | 设备管理的终端及其发起管理会话的方法 |
CN101771556A (zh) * | 2008-12-11 | 2010-07-07 | 华为终端有限公司 | 一种实现dm设备关联的方法、系统和设备 |
Family Cites Families (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6507589B1 (en) | 1998-04-30 | 2003-01-14 | Openwave Systems Inc. | Method and apparatus for routing between network gateways and service centers |
JP2001092707A (ja) * | 1999-09-24 | 2001-04-06 | Nec Corp | 情報処理システム、構造化文書処理システム、その更新方法及びその更新プログラムを記録した記録媒体 |
EP1360820B1 (de) * | 2001-02-13 | 2009-09-23 | Siemens Aktiengesellschaft | Verfahren und anordnung zum ermitteln der virtuellen adresse eines endgerätes |
JP2004272632A (ja) * | 2003-03-10 | 2004-09-30 | Sony Corp | 情報処理装置、および情報処理方法、並びにコンピュータ・プログラム |
FI116426B (fi) * | 2003-05-02 | 2005-11-15 | Nokia Corp | Laitteenhallinnan aloittaminen hallintapalvelimen ja asiakkaan välillä |
KR100501334B1 (ko) * | 2003-08-04 | 2005-07-18 | 삼성전자주식회사 | 씬 클라이언트 방식을 개선한 홈 미디어 게이트웨이의멀티미디어 데이터 처리장치 및 그 방법 |
US7734737B2 (en) * | 2005-05-26 | 2010-06-08 | Nokia Corporation | Device management with configuration information |
JP4644738B2 (ja) * | 2005-12-02 | 2011-03-02 | エルジー エレクトロニクス インコーポレイティド | ブロードキャストチャネルを利用した装置管理方法 |
CN101183968A (zh) | 2006-11-14 | 2008-05-21 | 中兴通讯股份有限公司 | 一种网关设备注册及自动配置方法 |
US8498265B2 (en) * | 2006-12-14 | 2013-07-30 | Nokia Corporation | Enabling settings provisioning process in WiMAX networks |
US7886139B2 (en) * | 2007-02-23 | 2011-02-08 | International Business Machines Corporation | Method to enable firmware to boot a system from an ISCSI device |
US8311042B2 (en) * | 2007-06-15 | 2012-11-13 | Mformation | System and method for automatic detection and reporting of the mapping between device identity and network address in wireless networks |
US20090254641A1 (en) * | 2008-04-02 | 2009-10-08 | Inventec Corporation | Network card capable of remote boot and method thereof |
US8321654B2 (en) * | 2008-05-20 | 2012-11-27 | Alcatel Lucent | Methods for initial bootstrap during activation and initial configuration of user terminals in network |
US8667564B1 (en) * | 2008-09-24 | 2014-03-04 | Sprint Communications Company L.P. | Mobile internet protocol V6 SIP proxy bootstrapping |
WO2010041347A1 (en) * | 2008-10-10 | 2010-04-15 | Telefonaktiebolaget L M Ericsson (Publ) | Gateway apparatus, authentication server, control method thereof and computer program |
US20100205420A1 (en) * | 2009-02-09 | 2010-08-12 | Inventec Corporation | System and method for realizing remote test on computer apparatus without storage device |
US8255677B2 (en) * | 2009-07-06 | 2012-08-28 | Intel Corporation | Initializing femtocells |
US20110047253A1 (en) * | 2009-08-19 | 2011-02-24 | Samsung Electronics Co. Ltd. | Techniques for controlling gateway functionality to support device management in a communication system |
GB2473019B (en) * | 2009-08-27 | 2015-10-21 | Wireless Data Services Ltd | Device management |
JP4966393B2 (ja) * | 2010-03-25 | 2012-07-04 | 株式会社東芝 | 端末機器 |
US10051074B2 (en) * | 2010-03-29 | 2018-08-14 | Samsung Electronics Co, Ltd. | Techniques for managing devices not directly accessible to device management server |
US20120191769A1 (en) * | 2011-01-25 | 2012-07-26 | Microsoft Corporation | Site-aware distributed file system access from outside enterprise network |
-
2011
- 2011-03-30 CN CN2011100784640A patent/CN102724050A/zh active Pending
-
2012
- 2012-03-16 EP EP12763114.1A patent/EP2693691B1/en active Active
- 2012-03-16 WO PCT/CN2012/072408 patent/WO2012130048A1/zh active Application Filing
-
2013
- 2013-09-30 US US14/041,133 patent/US9417887B2/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6490617B1 (en) * | 1998-06-09 | 2002-12-03 | Compaq Information Technologies Group, L.P. | Active self discovery of devices that participate in a network |
CN101127631A (zh) * | 2006-08-15 | 2008-02-20 | 华为技术有限公司 | 针对网络中设备实现配置管理的方法及系统 |
CN101771556A (zh) * | 2008-12-11 | 2010-07-07 | 华为终端有限公司 | 一种实现dm设备关联的方法、系统和设备 |
CN101540996A (zh) * | 2009-04-17 | 2009-09-23 | 深圳华为通信技术有限公司 | 设备管理的终端及其发起管理会话的方法 |
Non-Patent Citations (1)
Title |
---|
See also references of EP2693691A4 * |
Also Published As
Publication number | Publication date |
---|---|
EP2693691A1 (en) | 2014-02-05 |
US9417887B2 (en) | 2016-08-16 |
EP2693691A4 (en) | 2014-05-28 |
CN102724050A (zh) | 2012-10-10 |
US20140032892A1 (en) | 2014-01-30 |
EP2693691B1 (en) | 2016-05-18 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
KR102478442B1 (ko) | Pdu 유형 설정 방법, ue 정책 설정 방법 및 관련 엔티티 | |
US11039381B2 (en) | SMF selection based on supported DNN | |
JP2022101651A5 (zh) | ||
US11032743B1 (en) | Methods and apparatus for supporting devices of different types using a residential gateway | |
US8447843B2 (en) | System, method and computer program product for identifying, configuring and accessing a device on a network | |
WO2014048236A1 (zh) | 终端的注册方法及装置 | |
JP2007228602A5 (zh) | ||
WO2018191854A1 (zh) | 接入固定网络的方法和接入网关网元 | |
WO2012130048A1 (zh) | 设备管理系统中对网关进行初始化的方法及装置 | |
KR102258608B1 (ko) | 홈 네트워크 서비스를 제공하기 위한 장치 및 그 방법 | |
US20150106517A1 (en) | System and method for delayed device registration on a network | |
WO2015096344A1 (zh) | App获取终端的mac地址的方法及系统 | |
WO2014166210A1 (zh) | 客户端、服务器、远程用户拨号认证能力协商方法及系统 | |
US8213364B2 (en) | Method for releasing a high rate packet data session | |
JP2023165679A (ja) | 機器をリモートで管理するための装置、方法及びそのためのプログラム | |
WO2013189398A2 (zh) | 应用数据推送方法、装置及系统 | |
WO2014135102A1 (zh) | Wlan用户管理方法、装置及系统 | |
CN112311766B (zh) | 一种用户证书的获取方法及装置、终端设备 | |
WO2013185696A2 (zh) | 一种数据处理的方法与设备 | |
WO2013029507A1 (zh) | 管理会话建立方法、用户驻地设备及自动配置服务器 | |
WO2011120365A1 (zh) | 多穴终端建立连接的方法和系统 | |
WO2014110917A1 (zh) | 会话边界控制器地址的获取方法及装置 | |
WO2012139463A1 (zh) | 终端设备的初始化方法及装置 | |
WO2011017921A1 (zh) | 一种访问拜访地服务提供商的系统及方法 | |
WO2008055448A1 (fr) | Procédé, appareil et système d'acquisition d'informations d'accès d'un terminal utilisateur |
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: 12763114 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: 2012763114 Country of ref document: EP |