WO2019128734A1 - 一种物联网设备接入网络的方法、装置和系统 - Google Patents

一种物联网设备接入网络的方法、装置和系统 Download PDF

Info

Publication number
WO2019128734A1
WO2019128734A1 PCT/CN2018/121089 CN2018121089W WO2019128734A1 WO 2019128734 A1 WO2019128734 A1 WO 2019128734A1 CN 2018121089 W CN2018121089 W CN 2018121089W WO 2019128734 A1 WO2019128734 A1 WO 2019128734A1
Authority
WO
WIPO (PCT)
Prior art keywords
server
cloud gateway
internet
address
gateway server
Prior art date
Application number
PCT/CN2018/121089
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 EP18894082.9A priority Critical patent/EP3709603A4/en
Publication of WO2019128734A1 publication Critical patent/WO2019128734A1/zh
Priority to US16/899,362 priority patent/US20200304563A1/en

Links

Images

Classifications

    • 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/10—Protocols in which an application is distributed across nodes in the 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/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2854—Wide area networks, e.g. public data networks
    • H04L12/2856—Access arrangements, e.g. Internet access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5076—Update or notification mechanisms, e.g. DynDNS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
    • H04L63/0272—Virtual private networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1073—Registration or de-registration
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/16—Gateway arrangements

Definitions

  • the present application relates to the field of IT technologies, and in particular, to a method, device and system for an Internet of Things device to access a network.
  • the Internet of Things is an important part of the new generation of information technology, and an important stage of development in the information age.
  • the Internet of Things is the Internet connected by objects. It has two meanings: First, the core and foundation of the Internet of Things is still the Internet, which is an extended and expanded network based on the Internet. Second, it extends and extends to any goods and articles. Information exchange and communication between.
  • the Internet of Things is widely used in the convergence of networks through communication-aware technologies such as intelligent sensing and recognition technologies. It is also called the third wave of the development of the world information industry after computers and the Internet.
  • the IoT device has a communication address in the network and accesses the Internet of Things through the cloud gateway server. Because the address (IP or domain name) of the cloud gateway server connected to the IoT device needs to be changed because of installing, moving, or testing the IoT device, or adjusting the cloud gateway server, you need to manually reconfigure the IoT device.
  • the address of the cloud gateway server, and the cloud gateway server address configuration error may occur due to human error operation, causing the IoT device to fail to access the network.
  • the embodiment of the present invention provides a method, a device, and a system for accessing a network of an Internet of Things device, which are used to solve the problem that the cloud gateway server address configuration may be incorrect due to the address of the cloud gateway server corresponding to the artificially configured Internet of Things device, resulting in the Internet of Things.
  • an Internet of Things system in a first aspect, includes a registration server and a plurality of cloud gateway servers, and the registration server has a communication connection with the Internet of Things device.
  • the registration server configures a correspondence between an identifier of the Internet of Things device and an address of the cloud gateway server, and receives, by the communication connection, a first server address query request sent by the Internet of Things device, where the first server address query request is carried
  • the identifier of the Internet of Things device the registration server queries the address of the first cloud gateway server corresponding to the identifier of the Internet of Things device according to the corresponding relationship, and returns a first server address query response to the Internet of Things device
  • the first server address query response carries the address of the first cloud gateway server, and the address of the first cloud gateway server is used to indicate that the IoT device establishes a communication connection with the first cloud gateway server;
  • the first cloud gateway server is configured to establish a communication connection with the IoT device.
  • the embodiment of the present invention records the correspondence between the identifier of the Internet of Things device and the address of the cloud gateway server in the registration server, and the Internet of Things device obtains the address of the cloud gateway server corresponding to the Internet of Things device through the connection with the registration server.
  • the address of the cloud gateway server required for accessing the network is obtained by the IoT device through the unified registration server. Therefore, the address of the cloud gateway server is not required to be configured in the IoT device, thereby avoiding the possibility of manually configuring the cloud gateway server address.
  • the resulting access failure reduces the production complexity of IoT devices.
  • the registration server is further configured to update the corresponding relationship, where the updated cloud gateway server corresponding to the Internet of Things device is a second cloud gateway server of the plurality of cloud gateway servers;
  • the first cloud gateway server is further configured to send a notification message to the IoT device, where the notification message is used to indicate that the cloud gateway server corresponding to the Internet of Things device changes.
  • the registration server is further configured to receive a second server address query request sent by the IoT device, where the second server address query request carries an identifier of the IoT device;
  • the registration server is further configured to query the updated correspondence according to the identifier of the Internet of Things device, and determine that the updated cloud gateway server corresponding to the Internet of Things device is the second cloud gateway server;
  • the registration server is further configured to return a second server address query response to the IoT device, where the second server address query response carries an address of the second cloud gateway server, and an address of the second cloud gateway server And configured to indicate that the IoT device establishes a communication connection with the second cloud gateway server;
  • the second cloud gateway server is configured to establish a communication connection with the IoT device.
  • the Internet of Things system also includes at least one storage client having an address of a registration server configured thereon. Since the address of the registration server is configured in the IoT device, the IoT device can establish a communication connection with the registration server, and obtain the address of the cloud gateway server required to access the network from the registration server, thereby eliminating the need to configure the cloud in the IoT device.
  • the address of the gateway server which reduces the production complexity of IoT devices.
  • the cloud gateway server connected to the IoT device changes, there is no need to manually configure the address of the new cloud gateway server, thereby avoiding the configuration error that may be caused by manual processing.
  • the second cloud since the address of the updated second cloud gateway server is recorded in the registration server, when the first cloud gateway server is closed and the Internet of Things device cannot access the network, the second cloud is recorded in the registration server.
  • the address of the gateway server the IoT device can obtain the address of the second cloud gateway server from the registration server, and access the network through the second cloud gateway server.
  • a method for accessing a network by an Internet of Things device is provided.
  • the Internet of Things device and the registration server perform functions in the foregoing Internet of Things system.
  • a registration server comprising:
  • a configuration unit configured to configure a correspondence between an identifier of the IoT device and an address of the cloud gateway server
  • connection establishing unit configured to establish a communication connection with the Internet of Things device, wherein the address of the registration server is configured in the Internet of Things device;
  • a receiving unit configured to receive, by using the communication connection, a first server address query request sent by the Internet of Things device, where the first server address query request carries an identifier of the Internet of Things device;
  • a querying unit configured to query an address of the first cloud gateway server corresponding to the identifier of the Internet of Things device according to the correspondence relationship configured by the configuration unit;
  • a sending unit configured to return a first server address query response to the IoT device, where the first server address query response carries an address of the first cloud gateway server obtained by querying by the query unit, the first cloud
  • the address of the gateway server is used to indicate that the IoT device establishes a communication connection with the first cloud gateway server.
  • the configuration unit is further configured to update the corresponding relationship, where the updated cloud gateway server corresponding to the Internet of Things device is a second cloud gateway server of the plurality of cloud gateway servers.
  • the receiving unit is further configured to receive a second server address query request sent by the object network device, where the second server address query request carries an identifier of the IoT device;
  • the query unit is further configured to query the updated correspondence according to the identifier of the Internet of Things device, and determine that the updated cloud gateway server corresponding to the Internet of Things device is the second cloud gateway server;
  • the sending unit is further configured to: return a second server address query response to the IoT device, where the second server address query response carries an address of the second cloud gateway server obtained by querying by the query unit, The address of the second cloud gateway server is used to indicate that the IoT device establishes a communication connection with the second cloud gateway server.
  • an embodiment of the present invention further provides a registration server, where the registration server is a physical server, and has the function of implementing the registration server in the foregoing aspects.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the registration server includes a transceiver and a processor, wherein the processor is configured to invoke a set of program code to perform the method as described in the second aspect.
  • a computer storage medium for storing computer software instructions for use by the registration server of the above aspects, comprising a program designed to perform the above aspects.
  • FIG. 1 is a schematic structural diagram of an Internet of Things system according to an embodiment of the present invention.
  • FIG. 2 is a schematic flowchart of a method for an Internet of Things device to access a network according to an embodiment of the present invention
  • FIG. 3 is a schematic flowchart of another method for accessing a network by an Internet of Things device according to an embodiment of the present invention
  • FIG. 4 is a schematic diagram of a logical structure of a registration server according to an embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of hardware of a registration server according to an embodiment of the present invention.
  • the IoT device cannot determine the address of the cloud gateway server connected when the IoT device is initialized during the manufacturing process.
  • the cloud gateway server address of the IoT device is manually configured, There may be cases where the IoT device cannot access the network due to human error configuration.
  • the IoT device connected to one cloud gateway server is switched to another cloud gateway server as a whole, the original cloud gateway server cannot be stopped before the IoT device fails to complete the handover.
  • FIG. 1 is a schematic structural diagram of an Internet of Things system according to an embodiment of the present invention.
  • the Internet of Things system 100 includes a registration server 101 and a plurality of cloud gateway servers 102, and the Internet of Things device 103 accesses through the cloud gateway server 102. To the Internet of Things.
  • the address of the registration server 101 is configured in the Internet of Things device 103 when the IoT device 103 is manufactured or before the IoT device 103 is used for the first time, and the address of the registration server 101 may be an IP address or a domain name.
  • the registration server 101 stores the correspondence between the identifier of the Internet of Things device 103 and the address of the cloud gateway server 102.
  • the correspondence may be configured by the Internet of Things provider, or may be configured by the portal interface that the user logs in to the registration server.
  • the identifier of the Internet of Things device 103 recorded in the corresponding relationship may uniquely identify an IoT device.
  • an embodiment of the present invention provides a method for an Internet of Things device to access a network, including:
  • Step 201 Configure an address of the registration server in the Internet of Things device.
  • Step 202 Configure a correspondence between the identifier of the Internet of Things device and the address of the cloud gateway server in the registration server.
  • Step 203 After the IoT device is started, establish a communication connection with the registration server according to the address of the configured registration server.
  • Step 204 The IoT device sends a first server address query request to the registration server, where the first server address query request carries the identifier of the IoT device.
  • Step 205 After receiving the first server address query request, the registration server queries the corresponding relationship of the record, and determines the first cloud gateway server corresponding to the Internet of Things device according to the identifier of the Internet of Things device. And returning, to the IoT device, a first server address query response, where the first server address query response carries the determined address of the first cloud gateway server corresponding to the Internet of Things device.
  • Step 206 The IoT device receives the first server address query response, obtains an address of the first cloud gateway server, establishes a connection with the first cloud gateway server, and accesses the Internet of Things.
  • step 201 there is no order relationship between step 201 and step 202, and step 202 can be performed before step 201.
  • the embodiment of the present invention records the correspondence between the identifier of the Internet of Things device and the address of the cloud gateway server in the registration server, and the Internet of Things device obtains the address of the cloud gateway server corresponding to the Internet of Things device through the connection with the registration server.
  • the address of the cloud gateway server required for accessing the network is obtained by the IoT device through the unified registration server. Therefore, the address of the cloud gateway server is not required to be configured in the IoT device, thereby avoiding the possibility of manually configuring the cloud gateway server address.
  • the resulting access failure reduces the production complexity of IoT devices.
  • the embodiment shown in FIG. 2 shows a method for the first access to the network by the IoT device. Further, since the IoT device may adjust the cloud gateway server due to installation, movement, testing, or deployment, the device needs to be changed.
  • the address of the connected cloud gateway server the embodiment of the present invention provides a method for the Internet of Things device to access the network after the address of the cloud gateway server of the Internet of Things device is changed.
  • a method for accessing a network by another IoT device includes:
  • Step 301 The IoT device establishes a connection with the first cloud gateway server, and accesses the network through the first cloud gateway server.
  • Step 302 The registration server updates the cloud gateway server corresponding to the IoT device to a second cloud gateway server, and updates the identifier of the Internet of Things device and the address of the second cloud gateway server to the corresponding relationship.
  • Step 303 The first cloud gateway server sends a notification message to the IoT device, where the notification message is used to instruct the IoT device to update the cloud gateway server address.
  • the notification message may be used as a denial of access message, where the deny access message is used to indicate that the first cloud gateway server denies the IoT device from accessing the network.
  • Step 304 The IoT device receives the notification message, determines that the cloud gateway server needs to be updated, sends a second server address query request to the registration server, and the second server address query request carries the IoT device.
  • Step 305 The registration server receives the second server address query request, and determines that the cloud gateway server corresponding to the Internet of Things device is the second cloud gateway server, and obtains the second cloud according to the updated correspondence. The address of the gateway server.
  • Step 306 The registration server returns a second server address query response to the IoT device, and the second server address query response carries an address of the second cloud gateway server.
  • Step 307 The IoT device receives the server query response, establishes a connection with the second cloud gateway server according to the address of the second cloud gateway server, and accesses the network by using the second cloud gateway server.
  • step 301 there is no order relationship between step 301 and step 302, and step 302 can be performed before step 301.
  • the address of the cloud gateway server connected to the Internet of Things (IoT) access network is dynamically obtained by the IoT device access registration server, so that the IoT device can be operated for the first time or the cloud gateway server fails to connect.
  • the cloud gateway server connected to the IoT device changes, there is no need to manually configure the address of the new cloud gateway server, thereby avoiding the configuration error that may be caused by manual processing.
  • the IoT device connected to the cloud gateway server is switched to another cloud gateway server as a whole, the original cloud gateway server cannot be stopped before the handover is completed.
  • the address of the updated second cloud gateway server is recorded in the registration server, when the first cloud gateway server is closed and the IoT device cannot access the network, the second is recorded in the registration server.
  • the IoT device can obtain the address of the second cloud gateway server from the registration server, and access the network through the second cloud gateway server.
  • the embodiment of the present invention further provides a registration server 400, where the registration server 400 includes:
  • the configuration unit 401 is configured to configure a correspondence between an identifier of the Internet of Things device and an address of the cloud gateway server;
  • connection establishing unit 402 configured to establish a communication connection with the Internet of Things device, where the address of the registration server is configured in the Internet of Things device;
  • the receiving unit 403 is configured to receive, by using the communication connection, a first server address query request sent by the Internet of Things device, where the first server address query request carries an identifier of the Internet of Things device;
  • the querying unit 404 is configured to query, according to the correspondence relationship configured by the configuration unit 401, an address of the first cloud gateway server corresponding to the identifier of the Internet of Things device;
  • the sending unit 405 is configured to return a first server address query response to the IoT device, where the first server address query response carries the address of the first cloud gateway server obtained by the query unit 404, where the The address of the cloud gateway server is used to indicate that the IoT device establishes a communication connection with the first cloud gateway server.
  • the configuration unit 401 is further configured to update the corresponding relationship, where the updated cloud gateway server corresponding to the Internet of Things device is a second cloud gateway server of the plurality of cloud gateway servers.
  • the receiving unit 403 is further configured to receive a second server address query request sent by the Internet of Things device, where the second server address query request carries an identifier of the Internet of Things device;
  • the query unit 404 is further configured to query the updated correspondence according to the identifier of the Internet of Things device, and determine that the updated cloud gateway server corresponding to the Internet of Things device is the second cloud gateway server;
  • the sending unit 405 is further configured to: return a second server address query response to the IoT device, where the second server address query response carries an address of the second cloud gateway server that is obtained by the query unit 404, The address of the second cloud gateway server is used to indicate that the IoT device establishes a communication connection with the second cloud gateway server.
  • the embodiment of the present application further provides a schematic diagram of a hardware structure of a registration server.
  • the registration server 500 includes a transceiver 501, a processor 502, and a memory 503.
  • the transceiver 501 and the memory 503 are both coupled to the processor. 502 connection, it should be noted that the connection manner between the parts shown in FIG. 5 is only one possible example, and the transceiver 501 and the memory 503 are both connected to the processor 502, and the transceiver 501 and the memory are connected. There is no connection between 503, or it may be other possible connection methods.
  • the memory 503 stores a set of programs
  • the processor 502 is configured to call the program stored in the memory 503 to execute the foregoing method of registering the server in the method for accessing the network of the Internet of Things system and the Internet of Things device shown in FIG. 1 to FIG. Features.
  • the processor 502 may be a central processing unit (English: central processing unit, abbreviated: CPU), a network processor (English: network processor, abbreviated: NP) or a combination of a CPU and an NP.
  • CPU central processing unit
  • NP network processor
  • the memory 501 may include a volatile memory (English: volatile memory), such as a random access memory (English: random-access memory, abbreviation: RAM); the memory 501 may also include a non-volatile memory (English: non-volatile memory) For example, flash memory (English: flash memory), hard disk (English: hard disk drive, abbreviated: HDD) or solid state drive (English: solid-state drive, abbreviation: SSD); the memory 401 may also include the above types of memory The combination.
  • a volatile memory English: volatile memory
  • RAM random access memory
  • non-volatile memory English: non-volatile memory
  • flash memory English: flash memory
  • hard disk English: hard disk drive, abbreviated: HDD
  • SSD solid state drive
  • the memory 401 may also include the above types of memory The combination.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computing Systems (AREA)
  • Business, Economics & Management (AREA)
  • Multimedia (AREA)
  • General Business, Economics & Management (AREA)
  • Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • General Health & Medical Sciences (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种物联网设备接入网络的方法、装置和系统，所述系统包括注册服务器和多个云网关服务器，云网关服务器为物联网设备提供网络接入服务，所述注册服务器中记录物联网设备的标识与云网关服务器的地址的对应关系，所述物联网设备通过与注册服务器的连接获取所述物联网设备对应的云网关服务器的地址，建立与云网关服务器的连接。其中，由于物联网设备通过统一的注册服务器获取接入网络所需要的云网关服务器的地址，因此，无需在物联网设备中配置云网关服务器的地址，从而避免了人工错误配置云网关服务器地址可能引起的接入失败，降低了物联网设备的生产复杂度。

Description

一种物联网设备接入网络的方法、装置和系统
本申请要求于2017年12月28日提交中国专利局、申请号为201711453817.4、发明名称为“一种物联网设备接入网络的方法、装置和系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及IT技术领域，特别涉及一种物联网设备接入网络的方法、装置和系统。
背景技术
物联网(Internet of things，IoT)是新一代信息技术的重要组成部分，也是信息化时代的重要发展阶段。物联网就是物物相连的互联网，包含两层意思：其一，物联网的核心和基础仍然是互联网，是在互联网基础上的延伸和扩展的网络；其二，延伸和扩展到了任何物品与物品之间，进行信息交换和通信。物联网通过智能感知以及识别技术等通信感知技术，广泛应用于网络的融合中，也因此被称为继计算机、互联网之后世界信息产业发展的第三次浪潮。
物联网设备在网络中具备通信地址，通过云网关服务器接入到物联网。由于可能会因为安装、移动或者测试物联网设备，或者调整云网关服务器等原因，导致需要变更物联网设备连接的云网关服务器的地址(IP或域名)，因此需要人工重新配置物联网设备对应的云网关服务器的地址，同时可能存在由于人为错误操作使得云网关服务器地址配置错误，导致物联网设备接入网络失败。
发明内容
本申请实施例提供一种物联网设备接入网络的方法、装置和系统，用以解决由于人工配置物联网设备对应的云网关服务器的地址可能带来的云网关服务器地址配置错误，导致物联网设备接入网络失败的问题。
本申请实施例提供的具体技术方案如下：
第一方面，提供一种物联网系统，所述物联网系统包括注册服务器和多个云网关服务器，所述注册服务器与物联网设备之间存在通信连接，
所述注册服务器配置物联网设备的标识与云网关服务器的地址的对应关系，通过所述通信连接，接收所述物联网设备发送的第一服务器地址查询请求，所述第一服务器地址查询请求携带所述物联网设备的标识；所述注册服务器根据所述对应关系，查询所述物联网设备的标识对应的第一云网关服务器的地址，并向所述物联网设备返回第一服务器地址查询响应，所述第一服务器地址查询响应携带所述第一云网关服务器的地址，所述第一云网关服务器的地址用于指示所述物联网设备与所述第一云网关服务器建立通信连接；
所述第一云网关服务器，用于建立与所述物联网设备之间的通信连接。
本发明实施例通过在注册服务器中记录物联网设备的标识与云网关服务器的地址的对应关系，所述物联网设备通过与注册服务器的连接获取所述物联网设备对应的云网 关服务器的地址，建立与云网关服务器的连接。其中，由于物联网设备通过统一的注册服务器获取接入网络所需要的云网关服务器的地址，因此，无需在物联网设备中配置云网关服务器的地址，从而避免了人工错误配置云网关服务器地址可能引起的接入失败，降低了物联网设备的生产复杂度。
进一步的，所述注册服务器，还用于更新所述对应关系，其中，所述物联网设备对应的更新后的云网关服务器为所述多个云网关服务器中的第二云网关服务器；
所述第一云网关服务器，还用于向所述物联网设备发送通知消息，所述通知消息用于指示所述物联网设备对应的云网关服务器发生改变。
所述注册服务器，还用于接收所述物联网设备发送的第二服务器地址查询请求，所述第二服务器地址查询请求携带所述物联网设备的标识；
所述注册服务器，还用于根据所述物联网设备的标识，查询更新后的所述对应关系，确定所述物联网设备对应的更新后的云网关服务器为第二云网关服务器；
所述注册服务器，还用于向所述物联网设备返回第二服务器地址查询响应，所述第二服务器地址查询响应携带所述第二云网关服务器的地址，所述第二云网关服务器的地址用于指示所述物联网设备与所述第二云网关服务器建立通信连接；
所述第二云网关服务器，用于建立与所述物联网设备之间的通信连接。
所述物联网系统还包括至少一个存储客户端，所述存储客户端上配置有注册服务器的地址。由于在物联网设备中配置注册服务器的地址，从而使得物联网设备可以与注册服务器建立通信连接，从注册服务器获取接入网络所需要的云网关服务器的地址，从而无需在物联网设备中配置云网关服务器的地址，从而降低了物联网设备的生产复杂度。
当物联网设备连接的云网关服务器发生改变时，也无需人工配置新的云网关服务器的地址，避免了由于人工处理可能带来的配置错误的问题。本发明实施例中，由于在注册服务器中记录了更新后的第二云网关服务器的地址，当第一云网关服务器关闭，物联网设备无法接入网络时，由于注册服务器中记录了第二云网关服务器的地址，物联网设备可以从注册服务器获取第二云网关服务器的地址，通过第二云网关服务器接入到网络中。
第二方面，提供一种物联网设备接入网络的方法，在第二方面的方法中，所述物联网设备和注册服务器执行前述物联网系统中的功能。
第三方面，提供了一种注册服务器，所述注册服务器包括：
配置单元，用于配置物联网设备的标识与云网关服务器的地址的对应关系；
连接建立单元，用于建立与物联网设备之间的通信连接，其中，所述物联网设备中配置有所述注册服务器的地址；
接收单元，用于通过所述通信连接，接收所述物联网设备发送的第一服务器地址查询请求，所述第一服务器地址查询请求携带所述物联网设备的标识；
查询单元，用于根据所述配置单元配置的所述对应关系，查询所述物联网设备的标识对应的第一云网关服务器的地址；
发送单元，用于向所述物联网设备返回第一服务器地址查询响应，所述第一服务器地址查询响应携带所述查询单元查询得到的所述第一云网关服务器的地址，所述第一云网关服务器的地址用于指示所述物联网设备与所述第一云网关服务器建立通信连接。
所述配置单元，还用于更新所述对应关系，其中，所述物联网设备对应的更新后的云网关服务器为所述多个云网关服务器中的第二云网关服务器。
所述接收单元，还用于接收所述物联网设备发送的第二服务器地址查询请求，所述第二服务器地址查询请求携带所述物联网设备的标识；
所述查询单元，还用于根据所述物联网设备的标识，查询更新后的所述对应关系，确定所述物联网设备对应的更新后的云网关服务器为第二云网关服务器；
所述发送单元，还用于向所述物联网设备返回第二服务器地址查询响应，所述第二服务器地址查询响应携带所述查询单元查询得到的所述第二云网关服务器的地址，所述第二云网关服务器的地址用于指示所述物联网设备与所述第二云网关服务器建立通信连接。
第四方面，本发明实施例还提供了一种注册服务器，所述注册服务器为物理服务器，具有实现上述各方面中注册服务器的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，注册服务器包括收发器和处理器，其中，处理器用于调用一组程序代码，以执行如第二方面中所述的方法。
第五方面，提供了一种计算机存储介质，用于储存为上述方面所述的注册服务器所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
附图说明
图1为本发明实施例中的物联网系统的结构示意图；
图2为本发明实施例提供的一种物联网设备接入网络的方法流程示意图；
图3为本发明实施例提供的另一种物联网设备接入网络的方法流程示意图；
图4为本发明实施例提供的一种注册服务器的逻辑结构示意图；
图5为本发明实施例提供的一种注册服务器的硬件结构示意图。
具体实施方式
下面将结合附图对本申请作进一步描述。
物联网中可能存在大量的分布广泛的云网关服务器，物联网设备在制造过程中无法确定物联网设备初始化时连接的云网关服务器的地址，当采用人工配置物联网设备的云网关服务器地址时，可能会出现由于人为的错误配置导致物联网设备无法正常接入网络的情况。另外，在连接到某个云网关服务器的物联网设备整体切换到另一个云网关服务器时，在物联网设备没有完成切换前，原云网关服务器不能停止运行。
如图1所示，为本发明实施例提供的一种物联网系统结构示意图，所示物联网系统100包括注册服务器101以及多个云网关服务器102，物联网设备103通过云网关服务器102接入到物联网。
在制造物联网设备103时或者在首次使用物联网设备103之前，在物联网设备103中配置注册服务器101的地址，所述注册服务器101的地址可以是IP地址或者域名。
注册服务器101中存储物联网设备103的标识与云网关服务器102的地址的对应关系，所述对应关系可以由物联网提供商配置，也可以由用户登录注册服务器对外呈现的 portal界面进行配置。所述对应关系中记录的物联网设备103的标识可以唯一标识出某个物联网设备。
如图2所示，本发明实施例提供了一种物联网设备接入网络的方法，包括：
步骤201：在物联网设备中配置注册服务器的地址。
步骤202：在注册服务器中配置物联网设备的标识与云网关服务器的地址的对应关系。
步骤203：物联网设备启动后，根据配置的注册服务器的地址，建立与注册服务器之间的通信连接。
步骤204：物联网设备向注册服务器发送第一服务器地址查询请求，所述第一服务器地址查询请求携带所述物联网设备的标识。
步骤205：所述注册服务器在接收到所述第一服务器地址查询请求后，查询记录的所述对应关系，根据所述物联网设备的标识，确定所述物联网设备对应的第一云网关服务器的地址，向所述物联网设备返回第一服务器地址查询响应，所述第一服务器地址查询响应携带确定的所述物联网设备对应的第一云网关服务器的地址。
步骤206：所述物联网设备接收所述第一服务器地址查询响应，获取所述第一云网关服务器的地址，建立与所述第一云网关服务器的连接，从而接入到物联网中。
需要说明的是，步骤201和步骤202之间不存在顺序关系，步骤202可以在步骤201前执行。
本发明实施例通过在注册服务器中记录物联网设备的标识与云网关服务器的地址的对应关系，所述物联网设备通过与注册服务器的连接获取所述物联网设备对应的云网关服务器的地址，建立与云网关服务器的连接。其中，由于物联网设备通过统一的注册服务器获取接入网络所需要的云网关服务器的地址，因此，无需在物联网设备中配置云网关服务器的地址，从而避免了人工错误配置云网关服务器地址可能引起的接入失败，降低了物联网设备的生产复杂度。
图2所示的实施例给出了物联网设备首次接入网络的方法，进一步的，由于物联网设备可能会因为安装、移动、测试或部署调整云网关服务器等原因，导致需要变更物联网设备连接的云网关服务器的地址，本发明实施例提供了一种在物联网设备的云网关服务器的地址发生改变后，物联网设备接入网络的方法。
如图3所示，为本发明实施例提供的另一种物联网设备接入网络的方法，所述方法包括：
步骤301：所述物联网设备建立与第一云网关服务器之间的连接，通过第一云网关服务器接入网络；
步骤302：注册服务器将与所述物联网设备对应的云网关服务器更新为第二云网关服务器，将所述物联网设备的标识与所述第二云网关服务器的地址更新到所述对应关系。
步骤303：所述第一云网关服务器向所述物联网设备下发通知消息，所述通知消息用于指示所述物联网设备更新云网关服务器地址。
具体的，所述通知消息可用为拒绝接入消息，所述拒绝接入消息用于表示所述第一云网关服务器拒绝所述物联网设备接入网络。
步骤304：物联网设备接收所述通知消息，确定需要更新接入的云网关服务器，向所述注册服务器发送第二服务器地址查询请求，所述第二服务器地址查询请求携带所述物联网设备的标识；
步骤305：所述注册服务器接收所述第二服务器地址查询请求，根据更新后的所述对应关系，确定所述物联网设备对应的云网关服务器为第二云网关服务器，获取所述第二云网关服务器的地址。
步骤306：所述注册服务器向所述物联网设备返回第二服务器地址查询响应，所述第二服务器地址查询响应携带所述第二云网关服务器的地址。
步骤307：所述物联网设备接收所述服务器查询响应，根据所述第二云网关服务器的地址，建立与所述第二云网关服务器的连接，通过所述第二云网关服务器接入网络。
需要说明的是，步骤301和步骤302之间不存在顺序关系，步骤302可以在步骤301前执行。
如上所述，物联网设备接入网络所连接的云网关服务器的地址，是物联网设备访问注册服务器动态获取的，从而使得物联网设备在首次运行或者云网关服务器连接失败的情况下，均可以通过访问注册服务器来获取最新的云网关服务器的地址，从而保证物联网设备可以成功的接入到物联网中。由于采用统一的注册服务器，物联网设备配置更加简单，只需要配置了注册服务器的地址即可，无需在物联网设备中配置云网关服务器的地址，降低了物联网设备的生产复杂度，进一步的，当物联网设备连接的云网关服务器发生改变时，也无需人工配置新的云网关服务器的地址，避免了由于人工处理可能带来的配置错误的问题。更进一步的，现有技术中，当云网关服务器连接的物联网设备整体切换到另一个云网关服务器时，在没有完成切换前，原云网关服务器不能停止运行。而本发明实施例中，由于在注册服务器中记录了更新后的第二云网关服务器的地址，当第一云网关服务器关闭，物联网设备无法接入网络时，由于注册服务器中记录了第二云网关服务器的地址，物联网设备可以从注册服务器获取第二云网关服务器的地址，通过第二云网关服务器接入到网络中。
与前述各实施例相对应，本发明实施例还提供了一种注册服务器400，所述注册服务器400包括：
配置单元401，用于配置物联网设备的标识与云网关服务器的地址的对应关系；
连接建立单元402，用于建立与物联网设备之间的通信连接，其中，所述物联网设备中配置有所述注册服务器的地址；
接收单元403，用于通过所述通信连接，接收所述物联网设备发送的第一服务器地址查询请求，所述第一服务器地址查询请求携带所述物联网设备的标识；
查询单元404，用于根据所述配置单元401配置的所述对应关系，查询所述物联网设备的标识对应的第一云网关服务器的地址；
发送单元405，用于向所述物联网设备返回第一服务器地址查询响应，所述第一服务器地址查询响应携带所述查询单元404查询得到的所述第一云网关服务器的地址，所述第一云网关服务器的地址用于指示所述物联网设备与所述第一云网关服务器建立通信连接。
所述配置单元401，还用于更新所述对应关系，其中，所述物联网设备对应的更新 后的云网关服务器为所述多个云网关服务器中的第二云网关服务器。
所述接收单元403，还用于接收所述物联网设备发送的第二服务器地址查询请求，所述第二服务器地址查询请求携带所述物联网设备的标识；
所述查询单元404，还用于根据所述物联网设备的标识，查询更新后的所述对应关系，确定所述物联网设备对应的更新后的云网关服务器为第二云网关服务器；
所述发送单元405，还用于向所述物联网设备返回第二服务器地址查询响应，所述第二服务器地址查询响应携带所述查询单元404查询得到的所述第二云网关服务器的地址，所述第二云网关服务器的地址用于指示所述物联网设备与所述第二云网关服务器建立通信连接。
基于同一发明构思，参阅图5所示，本申请实施例还提供了注册服务器硬件结构示意图，注册服务器500，包括收发器501、处理器502和存储器503，收发器501、存储器503均与处理器502连接，需要说明的是图5所示的各部分之间的连接方式仅为一种可能的示例，也可以是，收发器501与存储器503均与处理器502连接，且收发器501与存储器503之间没有连接，或者，也可以是其他可能的连接方式。
其中，存储器503中存储一组程序，处理器502用于调用存储器503中存储的程序，以执行前述图1至图4所示的物联网系统和物联网设备接入网络的方法中注册服务器的功能。
在图5中，处理器502可以是中央处理器(英文：central processing unit，缩写：CPU)，网络处理器(英文：network processor，缩写：NP)或者CPU和NP的组合。
存储器501可以包括易失性存储器(英文：volatile memory)，例如随机存取存储器(英文：random-access memory，缩写：RAM)；存储器501也可以包括非易失性存储器(英文：non-volatile memory)，例如快闪存储器(英文：flash memory)，硬盘(英文：hard disk drive，缩写：HDD)或固态硬盘(英文：solid-state drive，缩写：SSD)；存储器401还可以包括上述种类的存储器的组合。
以上实施例仅用以说明本发明的技术方案，而非对其限制；尽管参照前述实施例对本发明进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本发明各实施例技术方案的保护范围。

Claims (10)

  1. 一种物联网系统，其特征在于，包括注册服务器和多个云网关服务器，所述注册服务器与物联网设备之间存在通信连接，
    所述注册服务器，用于配置物联网设备的标识与云网关服务器的地址的对应关系；
    所述注册服务器，还用于通过所述通信连接，接收所述物联网设备发送的第一服务器地址查询请求，所述第一服务器地址查询请求携带所述物联网设备的标识；
    所述注册服务器，还用于根据所述对应关系，查询所述物联网设备的标识对应的第一云网关服务器的地址，并向所述物联网设备返回第一服务器地址查询响应，所述第一服务器地址查询响应携带所述第一云网关服务器的地址，所述第一云网关服务器的地址用于指示所述物联网设备与所述第一云网关服务器建立通信连接；
    所述第一云网关服务器，用于建立与所述物联网设备之间的通信连接。
  2. 如权利要求1所述的系统，其特征在于，
    所述注册服务器，还用于更新所述对应关系，其中，所述物联网设备对应的更新后的云网关服务器为所述多个云网关服务器中的第二云网关服务器；
    所述第一云网关服务器，还用于向所述物联网设备发送通知消息，所述通知消息用于指示所述物联网设备对应的云网关服务器发生改变。
  3. 如权利要求2所述的系统，其特征在于，
    所述注册服务器，还用于接收所述物联网设备发送的第二服务器地址查询请求，所述第二服务器地址查询请求携带所述物联网设备的标识；
    所述注册服务器，还用于根据所述物联网设备的标识，查询更新后的所述对应关系，确定所述物联网设备对应的更新后的云网关服务器为所述第二云网关服务器；
    所述注册服务器，还用于向所述物联网设备返回第二服务器地址查询响应，所述第二服务器地址查询响应携带所述第二云网关服务器的地址，所述第二云网关服务器的地址用于指示所述物联网设备与所述第二云网关服务器建立通信连接；
    所述第二云网关服务器，用于建立与所述物联网设备之间的通信连接。
  4. 一种物联网设备接入网络的方法，其特征在于，包括：
    注册服务器配置物联网设备的标识与云网关服务器的地址的对应关系；
    所述注册服务器建立与物联网设备之间的通信连接，所述物联网设备中配置有所述注册服务器的地址；
    所述注册服务器通过所述通信连接，接收所述物联网设备发送的第一服务器地址查询请求，所述第一服务器地址查询请求携带所述物联网设备的标识；
    所述注册服务器根据所述对应关系，查询所述物联网设备的标识对应的第一云网关服务器的地址，并向所述物联网设备返回第一服务器地址查询响应，所述第一服务器地址查询响应携带所述第一云网关服务器的地址，所述第一云网关服务器的地址用于指示所述物联网设备与所述第一云网关服务器建立通信连接。
  5. 如权利要求4所述的方法，其特征在于，在所述物联网设备与所述第一云网关服务器建立通信连接之后，所述方法还包括
    所述注册服务器更新所述对应关系，其中，所述物联网设备对应的更新后的云网关服务器为所述多个云网关服务器中的第二云网关服务器。
  6. 如权利要求5所述的方法，其特征在于，所述注册服务器更新所述对应关系之后，所述方法还包括：
    所述注册服务器接收所述物联网设备发送的第二服务器地址查询请求，所述第二服务器地址查询请求携带所述物联网设备的标识；
    所述注册服务器根据所述物联网设备的标识，查询更新后的所述对应关系，确定所述物联网设备对应的更新后的云网关服务器为第二云网关服务器；
    所述注册服务器向所述物联网设备返回第二服务器地址查询响应，所述第二服务器地址查询响应携带所述第二云网关服务器的地址，所述第二云网关服务器的地址用于指示所述物联网设备与所述第二云网关服务器建立通信连接。
  7. 如权利要求5所述的方法，其特征在于，所述注册服务器更新所述对应关系之后，所述方法还包括：
    所述第一云网关服务器向所述物联网设备发送通知消息，所述通知消息用于指示所述物联网设备对应的云网关服务器发生改变。
  8. 一种注册服务器，其特征在于，包括：
    配置单元，用于配置物联网设备的标识与云网关服务器的地址的对应关系；
    连接建立单元，用于建立与物联网设备之间的通信连接，其中，所述物联网设备中配置有所述注册服务器的地址；
    接收单元，用于通过所述通信连接，接收所述物联网设备发送的第一服务器地址查询请求，所述第一服务器地址查询请求携带所述物联网设备的标识；
    查询单元，用于根据所述配置单元配置的所述对应关系，查询所述物联网设备的标识对应的第一云网关服务器的地址；
    发送单元，用于向所述物联网设备返回第一服务器地址查询响应，所述第一服务器地址查询响应携带所述查询单元查询得到的所述第一云网关服务器的地址，所述第一云网关服务器的地址用于指示所述物联网设备与所述第一云网关服务器建立通信连接。
  9. 如权利要求8所述的注册服务器，其特征在于，
    所述配置单元，还用于更新所述对应关系，其中，所述物联网设备对应的更新后的云网关服务器为所述多个云网关服务器中的第二云网关服务器。
  10. 如权利要求9所述的注册服务器，其特征在于，
    所述接收单元，还用于接收所述物联网设备发送的第二服务器地址查询请求，所述第二服务器地址查询请求携带所述物联网设备的标识；
    所述查询单元，还用于根据所述物联网设备的标识，查询更新后的所述对应关系，确定所述物联网设备对应的更新后的云网关服务器为第二云网关服务器；
    所述发送单元，还用于向所述物联网设备返回第二服务器地址查询响应，所述第二服务器地址查询响应携带所述查询单元查询得到的所述第二云网关服务器的地址，所述第二云网关服务器的地址用于指示所述物联网设备与所述第二云网关服务器建立通信连接。
PCT/CN2018/121089 2017-12-28 2018-12-14 一种物联网设备接入网络的方法、装置和系统 WO2019128734A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP18894082.9A EP3709603A4 (en) 2017-12-28 2018-12-14 METHOD FOR ALLOWING AN INTERNET OF OBJECTS DEVICE TO ACCESS A NETWORK, DEVICE, AND SYSTEM
US16/899,362 US20200304563A1 (en) 2017-12-28 2020-06-11 Method for accessing network by internet of things device, apparatus, and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711453817.4A CN108322506A (zh) 2017-12-28 2017-12-28 一种物联网设备接入网络的方法、装置和系统
CN201711453817.4 2017-12-28

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/899,362 Continuation US20200304563A1 (en) 2017-12-28 2020-06-11 Method for accessing network by internet of things device, apparatus, and system

Publications (1)

Publication Number Publication Date
WO2019128734A1 true WO2019128734A1 (zh) 2019-07-04

Family

ID=62893910

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/121089 WO2019128734A1 (zh) 2017-12-28 2018-12-14 一种物联网设备接入网络的方法、装置和系统

Country Status (4)

Country Link
US (1) US20200304563A1 (zh)
EP (1) EP3709603A4 (zh)
CN (1) CN108322506A (zh)
WO (1) WO2019128734A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113014459A (zh) * 2019-12-20 2021-06-22 西门子（中国）有限公司 智能家居系统的网关恢复方法及装置
CN114338774A (zh) * 2021-12-31 2022-04-12 深圳Tcl新技术有限公司 物联网设备的管理方法、装置、计算机设备和存储介质

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108322506A (zh) * 2017-12-28 2018-07-24 华为技术有限公司 一种物联网设备接入网络的方法、装置和系统
CN110798329A (zh) * 2018-08-01 2020-02-14 中兴通讯股份有限公司 物联网网关接入方法、设备以及存储介质
CN111083179B (zh) * 2018-10-19 2023-02-17 北京奇虎科技有限公司 物联网云平台、基于物联网云平台的设备交互方法及装置
CN109348523A (zh) * 2018-11-06 2019-02-15 海信集团有限公司 一种切换平台的方法及设备
CN109257239A (zh) * 2018-11-22 2019-01-22 福建福诺移动通信技术有限公司 一种基于tcp高可用物联网网关数据交互系统及方法
CN110213102B (zh) * 2019-06-03 2022-06-21 深圳绿米联创科技有限公司 设备控制方法、装置、电子设备及存储介质
CN110351388B (zh) * 2019-07-31 2022-02-22 南京三满互联网络科技有限公司 一种基于物联网络架构系统的应用方法
CN112583616B (zh) * 2019-09-29 2022-08-26 海信电子科技(武汉)有限公司 一种物联网设备、物联网平台及其接入物联网平台的方法
CN111817933B (zh) * 2020-07-08 2022-03-11 山东有人物联网股份有限公司 一种工业物联网云平台接入系统及其通信方法
CN112202877B (zh) * 2020-09-29 2023-04-18 中移（杭州）信息技术有限公司 网关联动方法、网关、云服务器及用户终端
CN112311866B (zh) * 2020-10-26 2023-04-07 东南大学 面向服务的新型物联网体系结构
CN112565334B (zh) * 2020-11-04 2022-10-25 深圳市宏电技术股份有限公司 物联网设备的接入方法、装置及mqtt网关
CN112751750B (zh) * 2020-12-16 2023-04-07 华人运通(上海)云计算科技有限公司 一种网关地址配置系统及方法
CN112804730B (zh) * 2021-01-25 2023-09-08 Oppo广东移动通信有限公司 设备互联方法、装置、服务器、智能设备及存储介质
CN112445601B (zh) * 2021-01-29 2021-05-11 红石阳光（北京）科技股份有限公司 一种基于智慧大脑的物联网综合管理平台及管理方法
CN113472859B (zh) * 2021-06-12 2023-09-19 广州鲁邦通智能科技有限公司 一种基于Azure IoT Hub解决设备就近连接的方法和系统
CN113507531A (zh) * 2021-06-15 2021-10-15 山东伏羲智库互联网研究院 物联网标识解析方法、边缘网关、电子设备及存储介质
CN114584461B (zh) * 2022-02-24 2024-03-01 上海材料研究所有限公司 一种支持多平台物联网设备的无线数据记录传输方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020040397A1 (en) * 2000-10-02 2002-04-04 Samsung Electronics Co., Ltd. IP based network system and networking method thereof
US20120059932A1 (en) * 2010-09-02 2012-03-08 Samsung Electronics Co., Ltd. Applying home network technologies to a wide area network
CN103370111A (zh) * 2012-10-31 2013-10-23 华为技术有限公司 发送云服务器地址的方法、设备
CN108322506A (zh) * 2017-12-28 2018-07-24 华为技术有限公司 一种物联网设备接入网络的方法、装置和系统

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103139871B (zh) * 2011-11-25 2016-05-11 上海贝尔股份有限公司 一种在泛在传感器网络中用于支持多家乡的方法
CN106797407B (zh) * 2014-10-03 2020-04-14 瑞典爱立信有限公司 物联系统中的唯一标识符的动态生成
KR102251309B1 (ko) * 2016-01-12 2021-05-12 삼성전자주식회사 무선 통신 시스템에서 전자 장치 설치 장치 및 방법

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020040397A1 (en) * 2000-10-02 2002-04-04 Samsung Electronics Co., Ltd. IP based network system and networking method thereof
US20120059932A1 (en) * 2010-09-02 2012-03-08 Samsung Electronics Co., Ltd. Applying home network technologies to a wide area network
CN103370111A (zh) * 2012-10-31 2013-10-23 华为技术有限公司 发送云服务器地址的方法、设备
CN108322506A (zh) * 2017-12-28 2018-07-24 华为技术有限公司 一种物联网设备接入网络的方法、装置和系统

Non-Patent Citations (1)

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

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113014459A (zh) * 2019-12-20 2021-06-22 西门子（中国）有限公司 智能家居系统的网关恢复方法及装置
CN114338774A (zh) * 2021-12-31 2022-04-12 深圳Tcl新技术有限公司 物联网设备的管理方法、装置、计算机设备和存储介质

Also Published As

Publication number Publication date
US20200304563A1 (en) 2020-09-24
EP3709603A1 (en) 2020-09-16
EP3709603A4 (en) 2020-12-30
CN108322506A (zh) 2018-07-24

Similar Documents

Publication Publication Date Title
WO2019128734A1 (zh) 一种物联网设备接入网络的方法、装置和系统
US11095524B2 (en) Component detection and management using relationships
US11070431B2 (en) System and method for network validation architecture for clustered and federated storage systems
JP7014887B2 (ja) Ｐｄｕタイプ設定方法、ｕｅポリシー設定方法、および関連エンティティ
US9923978B2 (en) Automated network service discovery and communication
US20080091812A1 (en) Automatic proxy registration and discovery in a multi-proxy communication system
EP3200434A2 (en) Domain name resolution
WO2021088254A1 (zh) 一种用户态网络文件系统双栈访问方法、装置及设备
CN114025021B (zh) 一种跨Kubernetes集群的通信方法、系统、介质和电子设备
US10841157B2 (en) Dynamic network discovery service for system deployment and validation
US20150305008A1 (en) Method and apparatus for updating information regarding specific resource in wireless communication system
US8924519B2 (en) Automated DNS configuration with local DNS server
JP2013502635A (ja) 通信システムにおけるデバイス管理をサポートするためにゲートウェイ機能を制御する技術
CN110213331B (zh) 业务请求的处理方法、终端设备、电子设备及存储介质
JP2006526939A (ja) Ｄｈｃｐサーバおよびルータの複数インターフェイスの同期構成のためのシステムおよび方法
EP3726786A1 (en) Method and apparatus for transmitting application programming interface (api) request
CN110855488B (zh) 一种虚拟机接入方法及装置
WO2019052058A1 (zh) 一种域名重定向方法和系统
US9417887B2 (en) Method and apparatus for bootstrapping gateway in device management system
US11012304B1 (en) Networking device replacement system
US20240039923A1 (en) Method and apparatus for deploying network device, device, system, and storage medium
CN116781564B (zh) 一种容器云平台的网络检测方法、系统、介质和电子设备
EP3709571A1 (en) Device management clustering
US8543678B2 (en) Synchronization method for NAT static port forwarding objects in redundant configurations
US10776384B1 (en) Method, server and system for criteria-based assured replication

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: 18894082

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2018894082

Country of ref document: EP

Effective date: 20200610

NENP Non-entry into the national phase

Ref country code: DE