WO2012068835A1 - 一种在CoAP网络中注册的方法及装置 - Google Patents
一种在CoAP网络中注册的方法及装置 Download PDFInfo
- Publication number
- WO2012068835A1 WO2012068835A1 PCT/CN2011/074006 CN2011074006W WO2012068835A1 WO 2012068835 A1 WO2012068835 A1 WO 2012068835A1 CN 2011074006 W CN2011074006 W CN 2011074006W WO 2012068835 A1 WO2012068835 A1 WO 2012068835A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- coap
- registration
- message
- registration information
- header field
- Prior art date
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/04—Protocols specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- 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
Definitions
- the invention relates to a method and a device for registering in a CoAP network, and belongs to the technical field of network communication.
- IOT Internet of Things, the Internet of Things (IoT), as a new generation of information technology, are receiving more and more attention from various industries. Different countries and standards organizations have different interpretations of their specific meanings.
- IOT is defined as a dynamic global network infrastructure with self-organizing capabilities based on standard and interoperable communication protocols, where physical and virtual "objects" have identity, physical attributes, virtual characteristics, and intelligent interfaces. And seamlessly integrate with the information network; or, it is an information sensing device such as radio frequency identification (RFID), infrared sensor, global positioning system, laser scanner, etc., to connect any object to the Internet according to the agreed protocol.
- RFID radio frequency identification
- RFID infrared sensor
- laser scanner etc.
- Information exchange and communication are carried out to realize a network for intelligently identifying, locating, tracking, monitoring and managing objects.
- CoRE Constrained RESTful
- Environments Restricted Representational State Transfer Environment
- CoAP Constrained Application Protocol
- restricted application layer protocol The basic features of CoAP include binary protocol, RESTFUL style and devices mainly used for low power consumption and low processing power.
- the function of reporting the IP address through the CoAP is not involved when the terminal is powered on or the IP address changes.
- the server or the platform cannot obtain the online status of the terminal in time, and the terminal or the platform cannot obtain the online status of the terminal in time.
- the CoAP message sent to the terminal is correctly delivered.
- the embodiment of the invention provides a method and a device for registering in a CoAP network.
- the IP address of the terminal supporting the CoAP changes, the current IP address of the terminal can be registered in the server or platform in the network in time.
- a method of registering in a CoAP network including:
- the carrying the registration information includes carrying the registration information by using one or more of the extended CoAP and the corresponding header field, the extended header field, the message body, or the uniform resource identifier URI;
- a device registered in a CoAP network comprising:
- a registration information receiving unit configured to receive a CoAP message carrying the registration information, where the carrying registration information includes any one of the extended CoAP and the corresponding header field, the extended header field, the message body, or the uniform resource identifier URI.
- the carrying registration information includes any one of the extended CoAP and the corresponding header field, the extended header field, the message body, or the uniform resource identifier URI.
- the registration unit is configured to determine whether the CoAP message received by the registration information receiving unit is sent by the subscription user, and if the determination result is yes, the registration information is stored, otherwise the registration request corresponding to the CoAP message is rejected.
- the CoAP message carrying the registration information is sent, so that the terminal can register in the server or platform in the network in time.
- the current IP address of the terminal so that the server or the platform can obtain the online status of the terminal in time, and ensure that the CoAP message sent to the terminal identifier can be correctly delivered.
- 1 is a signaling flowchart of registering a CoAP-enabled terminal on a registration server in a network according to an embodiment of the present invention
- FIG. 2 is a method for implementing registration in a CoAP network by extending a CoAP protocol and a corresponding header field according to an embodiment of the present invention
- FIG. 3 is a schematic diagram of a method for implementing registration by extending a new header field in a CoAP network according to an embodiment of the present invention
- FIG. 4 is a method for implementing registration by carrying a registration information in a message body in a CoAP network according to an embodiment of the present invention
- FIG. 5 is a method for implementing registration by carrying a registration information by using a URI in a CoAP network according to an embodiment of the present invention
- FIG. 6 is a schematic structural diagram of an apparatus registered in a CoAP network according to an embodiment of the present invention.
- the present invention The method for registering in the CoAP network proposed by the embodiment can be registered in the network in time.
- the terminal acting as the CoAP registrant initiates a registration request to the server or platform in the network as the registration server after triggering the registration event. After the registration server determines, the result is returned to the CoAP registrant through the response.
- the specific method includes: receiving a CoAP message carrying registration information, where the carrying the registration information includes carrying the registration information by using one or more of an extended CoAP and a corresponding header field, an extended header field, a message body, or a URI; Determining whether the CoAP message is sent by the subscription user, and if the determination result is yes, storing the registration information, otherwise rejecting the registration request corresponding to the CoAP message.
- M2M Machine To The machine, machine information
- the M2M terminal is the registration requesting party that initiates the registration, and the server or the platform in the network serves as the receiver of the registration request, and the M2M terminal sends the CoAP message carrying the registration information by extending the CoAP protocol and the corresponding header field.
- the method specifically includes:
- Step 21 When the IP address of the M2M terminal in the CoAP network changes, the CoAP registration event is triggered.
- IP address of the M2M terminal changes, a new IP address needs to be reported to the server or platform in the CoAP network. Otherwise, the status cannot be recognized by the server or the platform. Therefore, when the IP address of the M2M terminal changes, for example, power on, a CoAP registration event is triggered.
- Step 22 Send a CoAP message carrying the registration information, where the carrying the registration information includes passing the registration information through the extended CoAP and the corresponding header field.
- the M2M terminal sends a CoAP message to the server or the platform.
- the CoAP message includes the CoAP and the corresponding header field, where the extended CoAP has a CODE field value of 5.
- the message is a registration request.
- the extended header fields include Identity, Expires, and Contact, and their Type types are 10, 11, and 12, respectively.
- the identity of the CoAP registration is carried by the Identity header field and the value is Sensor@M2M.COM.
- the duration of the CoAP registration is carried in the Expires header field, and the value is 7200, which means 7200 seconds.
- the IP address and port of the CoAP registrant pass the Contact header field. Carry, the value is 192.168.0.1:61616.
- the specific message format can be:
- Step 23 Determine, according to the identity identifier in the registration information, whether the CoAP message carrying the registration information is sent by the subscription user, and if the determination result is yes, the registration information is stored, and the registration success response is returned, otherwise the CoAP message is rejected. Registration request.
- the server or the platform in the CoAP network After receiving the CoAP message carrying the registration information, the server or the platform in the CoAP network determines whether the M2M terminal that initiated the registration is a subscription user of the CoAP network according to the identity identifier in the CoAP message, and if so, stores the received registration information. And returning a registration success response to the M2M terminal, and if not, rejecting the M2M registration request.
- the message structure of the returned registration success response can be:
- the M2M terminal acts as the registration requesting party that initiates the registration, and the server or platform in the network serves as the receiver of the registration request, and the M2M terminal sends the CoAP message carrying the registration information by extending the new header field, as shown in the figure.
- the method specifically includes:
- steps 31 and 33 are similar to steps 21 and 23 in the embodiment shown in FIG. 2, and details are not described herein again.
- Step 32 Send a CoAP message carrying the registration information, where the carrying the registration information includes passing the registration information through the extended header field.
- the M2M terminal sends a CoAP message to the server or the platform, and the CoAP message includes a header field that extends the registration information, where the extended header field includes Identity, Expires, and Contact, and the Type types are respectively For 10, 11 and 12.
- the identity of the CoAP registration is carried by the Identity header field and the value is Sensor@M2M.COM.
- the duration of the CoAP registration is carried in the Expires header field, and the value is 7200, which means 7200 seconds.
- the IP address and port of the CoAP registrant pass the Contact header field. Carry, the value is 192.168.0.1:61616.
- the specific message format can be:
- the M2M terminal acts as the registration requesting party that initiates the registration
- the server or platform in the network serves as the receiver of the registration request
- the M2M terminal sends the CoAP message carrying the registration information by means of the message body carrying the registration information, as shown in the figure.
- the method specifically includes:
- steps 41 and 43 are similar to steps 21 and 23 in the embodiment shown in FIG. 2, and details are not described herein again.
- Step 42 Send a CoAP message carrying the registration information, where the carrying the registration information includes carrying the registration information in the CoAP message body.
- the M2M terminal sends a CoAP message to the server or the platform, and the CoAP message includes carrying the registration information in the CoAP message body, where the registration information includes three fields: Identity, Expires, and Contact.
- the value of Identity is Sensor@M2M.COM; the value of Expires is 7200, which means 7200 seconds; the value of Contact is 192.168.0.1:61616.
- the specific message format can be:
- the M2M terminal acts as the registration requesting party that initiates the registration, and the server or platform in the network serves as the receiver of the registration request, and the M2M terminal sends the CoAP message carrying the registration information by means of the URI carrying the registration information, as shown in FIG. 5.
- the method specifically includes:
- steps 51 and 53 are similar to steps 21 and 23 in the embodiment shown in FIG. 2, and details are not described herein again.
- Step 52 Send a CoAP message carrying the registration information, where the carrying the registration information includes carrying the registration information in a URI of the CoAP message.
- the M2M terminal sends a CoAP message to the server or platform.
- the URI of the CoAP message includes three fields: Identity, Expires, and Contact.
- Identity is Sensor@M2M.COM; the value of Expires is 7200, which means 7200 seconds; the value of Contact is 192.168.0.1:61616.
- the specific message format can be:
- the present invention sends the CoAP message carrying the registration information, so that the M2M terminal can register the current IP address of the M2M terminal in a server or platform in the network in time, thereby the server or The platform can obtain the online status of the M2M terminal in time, and ensure that the CoAP message sent to the M2M terminal identifier can be correctly delivered.
- the storage medium may be a magnetic disk, an optical disk, or a read-only storage memory (Read-Only) Memory, ROM) or Random Access Memory (RAM).
- An apparatus for registering in a CoAP network includes a registration information receiving unit 61 and a registration unit 62, and the registration information receiving unit 61 is configured to receive a CoAP message carrying the registration information.
- Carrying the registration information includes carrying the registration information through the extended CoAP and any one or more of the corresponding header field, the extended header field, the message body or the uniform resource identifier URI; the registration unit 62 is configured to determine the registration information receiving unit. If the received CoAP message is sent by the subscription user, if the result of the determination is yes, the registration information is stored, otherwise the registration request corresponding to the CoAP message is rejected.
- the extended CoAP and the corresponding header field, the extended header field, the message body, and the URI respectively include adding a registration request message in the CoAP, and adding an identity in the corresponding header field. , registration duration, IP address and port.
- determining in the registration unit 62, a determining subunit, configured to determine, according to the identity identifier, whether the CoAP message is sent by the subscription user.
- the apparatus can further include an response response unit for returning a response response, the response response including a registration success message and a corresponding identity.
- the device registered in the CoAP network provided by the embodiment of the present invention is configured to be able to register in the network in time when the IP address of the M2M terminal changes in the network supporting the CoAP, so that the server or the platform can obtain the M2M terminal in time.
- the online status ensures that the CoAP message sent to the M2M terminal identifier can be correctly delivered. .
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Telephonic Communication Services (AREA)
Abstract
一种在CoAP网络中注册的方法及装置,其中的方法包括接收携带注册信息的受限应用层协议CoAP消息,所述携带注册信息包括将注册信息通过扩展的CoAP及相应的头域、扩展的头域、消息体或统一资源标识URI中的任意一种或几种携带;判断所述CoAP消息是否为签约用户发送,判断结果为是,则存储所述注册信息,否则拒绝所述CoAP消息对应的注册请求。本发明通过发送携带注册信息的CoAP消息,使该终端能够及时的在网络中的服务器或平台注册该终端当前的IP地址,从而服务器或平台可以及时获得该终端的在线状态,并保证了发送给该终端标识的CoAP消息能够正确送达。
Description
本申请要求了2010年11月22日提交的、申请号为
201010557274.2、发明名称为“一种在CoAP网络中注册的方法及装置”的中国申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本发明涉及一种在CoAP网络中注册的方法及装置,属于网络通信技术领域。
发明背景
IOT(Internet of
Things,物联网)作为新一代的信息技术,越来越受到各行业的关注,不同的国家和标准组织对它们的具体含义都有不同的阐述。例如将IOT定义为一个动态的全球网络基础设施,并且具有基于标准和互操作通信协议的自组织能力,其中物理的和虚拟的“物”具有身份标识、物理属性、虚拟的特性和智能的接口,并与信息网络无缝整合;或者,是一种通过射频识别(RFID)、红外感应器、全球定位系统、激光扫描器等信息传感设备,按约定的协议把任何物体与互联网相连接,并进行信息交换和通信,以实现对物体的智能化识别、定位、跟踪、监控和管理的网络。
目前业界的各大标准组织也正在制定IOT相关的标准协议,例如工程任务组IETF专门成立了一个CoRE(Constrained RESTful
Environments,受限的表述性状态转移式环境)工作组,其任务之一就是设计一种适合能力受限的IP网络的应用层协议,即CoAP(Constrained
Application
Protocol,受限应用层协议)。CoAP的基本特点包括二进制协议、RESTFUL风格和主要用于低功耗、低处理能力的设备。但目前已经完成制定的基本机制中,对于当终端在开机或IP地址发生变化时,如何通过CoAP上报IP地址的功能还没有涉及。
现有技术中,当支持CoAP的终端在开机或IP地址发生变化时,无法即时在网络中的服务器或平台注册当前的IP地址,导致服务器或平台无法及时获得该终端的在线状态,也无法保证发送给该终端的CoAP消息正确送达。
发明内容
本发明的实施例提供了一种在CoAP网络中注册的方法及装置,当支持CoAP的终端的IP地址发生变化时,能够及时的在网络中的服务器或平台注册该终端当前的IP地址。
一种在CoAP网络中注册的方法,包括:
接收携带注册信息的CoAP消息,所述携带注册信息包括将注册信息通过扩展的CoAP及相应的头域、扩展的头域、消息体或统一资源标识URI中的任意一种或几种携带;
判断所述CoAP消息是否为签约用户发送,判断结果为是,则存储所述注册信息,否则拒绝所述CoAP消息对应的注册请求。
一种在CoAP网络中注册的装置,包括:
注册信息接收单元,用于接收携带注册信息的CoAP消息,所述携带注册信息包括将注册信息通过扩展的CoAP及相应的头域、扩展的头域、消息体或统一资源标识URI中的任意一种或几种携带;
注册单元,用于判断注册信息接收单元接收到的所述CoAP消息是否为签约用户发送,判断结果为是,则存储所述注册信息,否则拒绝所述CoAP消息对应的注册请求。
由上述本发明的实施例提供的技术方案可以看出,当支持CoAP的终端的IP地址发生变化时,通过发送携带注册信息的CoAP消息,使该终端能够及时的在网络中的服务器或平台注册该终端当前的IP地址,从而服务器或平台可以及时获得该终端的在线状态,并保证了发送给该终端标识的CoAP消息能够正确送达。
附图简要说明
为了更清楚地说明本发明实施例的技术方案,下面将对实施例描述中所需要使用的附图作简单地介绍,显而易见地,下面描述中的附图仅仅是本发明的一些实施例,对于本领域普通技术人员来讲,在不付出创造性劳动性的前提下,还可以根据这些附图获得其他的附图。
图1为本发明的实施例提供的支持CoAP的终端在网络中的注册服务器上注册的信令流程图;
图2为本发明的实施例提供的在CoAP网络中通过扩展CoAP协议及相应头域实现注册的方法;
图3为本发明的实施例提供的在CoAP网络中通过扩展新的头域实现注册的方法;
图4为本发明的实施例提供的在CoAP网络中通过消息体携带注册信息实现注册的方法;
图5为本发明的实施例提供的在CoAP网络中通过URI携带注册信息实现注册的方法;
图6为本发明的实施例提供的在CoAP网络中注册的装置的结构示意图。
实施本发明的方式
下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚、完整地描述,显然,所描述的实施例仅仅是本发明一部分实施例,而不是全部的实施例。基于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。
在支持CoAP的网络中,当终端的IP地址发生变化时,由于CoAP的基本机制中没有关于IP地址发生变化时的应对策略,并且也无法通过CoAP以外的现有技术完注册,因此本发明的实施例提出的在CoAP网络中注册的方法能够及时在网络中注册,如图1所示,作为CoAP注册方的终端在触发注册事件后,向作为注册服务器的网络中的服务器或平台发起注册请求,注册服务器经过判断后将结果通过应答响应返回给CoAP注册方。具体的方法包括接收携带注册信息的CoAP消息,所述携带注册信息包括将注册信息通过扩展的CoAP及相应的头域、扩展的头域、消息体或URI中的任意一种或几种携带;判断所述CoAP消息是否为签约用户发送,判断结果为是,则存储所述注册信息,否则拒绝所述CoAP消息对应的注册请求。为了更清楚的说明该方法的技术方案,下面以M2M(Machine
to
Machine,机器信息)终端为例,通过具体的实施例并结合说明书附图作进一步说明。需要说明的是,以下的实施例虽然采用了不同的技术特征解决了本发明提出的技术问题,但这些实施例都是在同一发明构思下的不同实现方法,并且任何支持CoAP的除M2M以外的终端也都能应用该方法实现注册功能。
实施例一
在本实施例中,M2M终端作为发起注册的注册请求方,网络中的服务器或平台作为注册请求的受理方,并且M2M终端通过扩展CoAP协议及相应头域的方式发送携带注册信息的CoAP消息,如图2所示,该方法具体包括:
步骤21,当CoAP网络中的M2M终端的IP地址发生变化时,触发CoAP注册事件。
当M2M终端的IP地址发生变化时,需要在CoAP网络中向服务器或平台上报新的IP地址,否则不能被服务器或平台识别其状态。因此当M2M终端的IP地址发生变化时,例如开机,就会触发CoAP注册事件。
步骤22,发送携带注册信息的CoAP消息,所述携带注册信息包括将注册信息通过扩展的CoAP及相应的头域。
触发CoAP注册事件后,M2M终端向服务器或平台发送一个CoAP消息,在这个CoAP消息中包括了将注册信息通过扩展的CoAP及相应的头域,其中扩展的CoAP的CODE字段值为5,表示该消息为注册请求,扩展的头域包括Identity、Expires和Contact,并且其Type类型分别为10、11和12。其中CoAP注册的身份标识通过Identity头域携带,值为Sensor@M2M.COM;CoAP注册的时长通过Expires头域携带,值为7200,表示7200秒;CoAP注册方的IP地址和端口通过Contact头域携带,值为192.168.0.1:61616。具体的消息格式可以为:
Ver:1
T:0
OC:4
CODE:5=REGISTER(扩展)
Transaction ID:1234
Option Delta:9=URI
Length:12
Option Value:/Registration
Option Delta:1=9+1=Identity(扩展)
Length:14
Option Value:Sensor@M2M.COM
Option Delta:1=9+1+1=Expires(扩展)
Length:4
Option Value:7200
Option Delta:1=9+1+1+1=IP Address(扩展)
Length:17
Option Value:192.168.0.1:61616
步骤23,根据注册信息中的身份标识判断携带所述注册信息的CoAP消息是否为签约用户发送,判断结果为是,则存储所述注册信息,并返回注册成功响应,否则拒绝所述CoAP消息对应的注册请求。
CoAP网络中的服务器或平台接收到携带注册信息的CoAP消息后,会根据CoAP消息中的身份标识判断发起注册的M2M终端是否为该CoAP网络的签约用户,如果是,则存储接收的注册信息,并向该M2M终端返回注册成功响应,如果不是,则拒绝该M2M的注册请求。其中返回的注册成功响应的消息结构可以为:
Ver:1
T:2
OC:0
CODE:80=200 OK
Transaction ID:1234
实施例二
在本实施例中,M2M终端作为发起注册的注册请求方,网络中的服务器或平台作为注册请求的受理方,并且M2M终端通过扩展新的头域的方式发送携带注册信息的CoAP消息,如图3所示,该方法具体包括:
其中,步骤31和33的实现过程与图2所示实施例中步骤21和23类似,这里不再赘述。
步骤32,发送携带注册信息的CoAP消息,所述携带注册信息包括将注册信息通过扩展的头域。
触发CoAP注册事件后,M2M终端向服务器或平台发送一个CoAP消息,在这个CoAP消息中包括了将注册信息通过扩展的头域,其中扩展的头域包括Identity、Expires和Contact,并且其Type类型分别为10、11和12。其中CoAP注册的身份标识通过Identity头域携带,值为Sensor@M2M.COM;CoAP注册的时长通过Expires头域携带,值为7200,表示7200秒;CoAP注册方的IP地址和端口通过Contact头域携带,值为192.168.0.1:61616。具体的消息格式可以为:
Ver:1
T:0
OC:4
CODE:2=POST
Transaction ID:1234
Option Delta:9=URI
Length:12
Option Value:/Registration
Option Delta:1=9+1=Identity(扩展)
Length:14
Option Value:Sensor@M2M.COM
Option Delta:1=9+1+1=Expires(扩展)
Length:4
Option Value:7200
Option Delta:1=9+1+1+1=IP Address(扩展)
Length:17
Option Value:192.168.0.1:61616
实施例三
在本实施例中,M2M终端作为发起注册的注册请求方,网络中的服务器或平台作为注册请求的受理方,并且M2M终端通过消息体携带注册信息的方式发送携带注册信息的CoAP消息,如图4所示,该方法具体包括:
其中,步骤41和43的实现过程与图2所示实施例中步骤21和23类似,这里不再赘述。
步骤42,发送携带注册信息的CoAP消息,所述携带注册信息包括将注册信息携带在CoAP消息体中。
触发CoAP注册事件后,M2M终端向服务器或平台发送一个CoAP消息,在这个CoAP消息中包括了将注册信息携带在CoAP消息体中,其中注册信息包括三个字段:Identity、Expires和Contact。其中Identity的值为Sensor@M2M.COM;Expires的值为7200,表示7200秒;Contact的值为192.168.0.1:61616。具体的消息格式可以为:
Ver:1
T:0
OC:1
CODE:2=POST
Transaction ID:1234
Option Delta:9=URI
Length:12
Option Value:/Registration
Payloads:
Identity= Sensor@M2M.COM;
Expires= 7200;
Contact= 192.168.0.1:61616;
实施例四
在本实施例中,M2M终端作为发起注册的注册请求方,网络中的服务器或平台作为注册请求的受理方,并且M2M终端通过URI携带注册信息的方式发送携带注册信息的CoAP消息,如图5所示,该方法具体包括:
其中,步骤51和53的实现过程与图2所示实施例中步骤21和23类似,这里不再赘述。
步骤52,发送携带注册信息的CoAP消息,所述携带注册信息包括将注册信息携带在CoAP消息的URI中。
触发CoAP注册事件后,M2M终端向服务器或平台发送一个CoAP消息,在这个CoAP消息的URI中包括了三个字段:Identity、Expires和Contact。其中Identity的值为Sensor@M2M.COM;Expires的值为7200,表示7200秒;Contact的值为192.168.0.1:61616。具体的消息格式可以为:
Ver:1
T:0
OC:1
CODE:2=POST
Transaction ID:1234
Option Delta:9=URI
Length:12
Option Value:/Registration?Identity=
Sensor@M2M.COM& Expires= 7200 &Contact= 192.168.0.1:61616
Payloads:
本发明在支持CoAP的M2M终端的IP地址发生变化时,通过发送携带注册信息的CoAP消息,使该M2M终端能够及时的在网络中的服务器或平台注册该M2M终端当前的IP地址,从而服务器或平台可以及时获得该M2M终端的在线状态,并保证了发送给该M2M终端标识的CoAP消息能够正确送达。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程,是可以通过计算机程序来指令相关的硬件来完成,所述的程序可存储于一计算机可读取存储介质中,该程序在执行时,可包括如上述各方法的实施例的流程。其中,所述的存储介质可为磁碟、光盘、只读存储记忆体(Read-Only
Memory,ROM)或随机存储记忆体(Random Access Memory,RAM)等。
本发明的实施例提供的一种在CoAP网络中注册的装置,如图6所示,包括注册信息接收单元61和注册单元62,注册信息接收单元61用于接收携带注册信息的CoAP消息,所述携带注册信息包括将注册信息通过扩展的CoAP及相应的头域、扩展的头域、消息体或统一资源标识URI中的任意一种或几种携带;注册单元62用于判断注册信息接收单元61接收到的所述CoAP消息是否为签约用户发送,判断结果为是,则存储所述注册信息,否则拒绝所述CoAP消息对应的注册请求。
进一步地,在所述注册信息发送单元61中,扩展的CoAP及相应的头域、扩展的头域、消息体和URI分别包括在CoAP中增加注册请求消息,在相应的头域中增加身份标识、注册时长、IP地址和端口。
以及,在注册单元62中包括判断子单元,用于根据所述身份标识判断所述CoAP消息是否为签约用户发送。
另外,该装置还可以包括应答响应单元,用于返回应答响应,所述应答响应包括注册成功消息及相应的身份标识。
本发明的实施例提供的在CoAP网络中注册的装置用于在支持CoAP的网络中,当M2M终端的IP地址发生变化时,能够及时在网络中注册,从而服务器或平台可以及时获得该M2M终端的在线状态,并保证了发送给该M2M终端标识的CoAP消息能够正确送达。。
上述装置中包含的各单元的处理功能的具体实现可参考方法实施例部分的描述,在此不再重复描述。
以上所述,仅为本发明较佳的具体实施方式,但本发明的保护范围并不局限于此,任何熟悉本技术领域的技术人员在本发明揭露的技术范围内,可轻易想到的变化或替换,都应涵盖在本发明的保护范围之内。因此,本发明的保护范围应该以权利要求的保护范围为准。
Claims (10)
- 一种在CoAP网络中注册的方法,其特征在于,包括:接收携带注册信息的受限应用层协议CoAP消息,所述携带注册信息包括将注册信息通过扩展的CoAP及相应的头域、扩展的头域、消息体或统一资源标识URI中的任意一种或几种携带;判断所述CoAP消息是否为签约用户发送,判断结果为是,则存储所述注册信息,否则拒绝所述CoAP消息对应的注册请求。
- 根据权利要求1所述的方法,其特征在于,所述扩展的CoAP及相应的头域包括在CoAP中增加注册请求消息,在相应的头域中增加身份标识、注册时长、IP地址和端口。
- 根据权利要求1所述的方法,其特征在于,在所述扩展的头域、消息体和URI中分别包括身份标识、注册时长、IP地址和端口。
- 根据权利要求1所述的方法,其特征在于,所述判断包括:根据所述身份标识判断所述CoAP消息是否为签约用户发送。
- 根据权利要求1至4任意一项所述的方法,其特征在于,该方法还包括:返回应答响应,所述应答响应包括注册成功消息及相应的身份标识。
- 一种在CoAP网络中注册的装置,其特征在于,包括:注册信息接收单元,用于接收携带注册信息的受限应用层协议CoAP消息,所述携带注册信息包括将注册信息通过扩展的CoAP及相应的头域、扩展的头域、消息体或统一资源标识URI中的任意一种或几种携带;注册单元,用于判断注册信息接收单元接收到的所述CoAP消息是否为签约用户发送,判断结果为是,则存储所述注册信息,否则拒绝所述CoAP消息对应的注册请求。
- 根据权利要求6所述的装置,其特征在于,在所述注册信息发送单元中,所述扩展的CoAP及相应的头域包括在CoAP中增加注册请求消息,在相应的头域中增加身份标识、注册时长、IP地址和端口。
- 根据权利要求6所述的装置,其特征在于,在所述注册信息发送单元中,所述头域、消息体和URI分别包括身份标识、注册时长、IP地址和端口。
- 根据权利要求6所述的装置,其特征在于,在注册单元中包括:判断子单元,用于根据所述身份标识判断所述CoAP消息是否为签约用户发送。
- 根据权利要求6至9任意一项所述的装置,其特征在于,该装置还包括:应答响应单元,用于返回应答响应,所述应答响应包括注册成功消息及相应的身份标识。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2010105572742A CN102014129B (zh) | 2010-11-22 | 2010-11-22 | 一种在CoAP网络中注册的方法及装置 |
CN201010557274.2 | 2010-11-22 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2012068835A1 true WO2012068835A1 (zh) | 2012-05-31 |
Family
ID=43844140
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2011/074006 WO2012068835A1 (zh) | 2010-11-22 | 2011-05-12 | 一种在CoAP网络中注册的方法及装置 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN102014129B (zh) |
WO (1) | WO2012068835A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109996219A (zh) * | 2018-01-02 | 2019-07-09 | 中国移动通信有限公司研究院 | 一种物联网鉴权方法、网络设备及终端 |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102882906A (zh) * | 2011-07-14 | 2013-01-16 | 华为技术有限公司 | 受限应用协议中数据通信的方法和装置 |
WO2013038230A1 (en) * | 2011-09-12 | 2013-03-21 | Nokia Corporation | Methods and apparatus for launching an application identified by a sensor |
CN103166931A (zh) * | 2011-12-15 | 2013-06-19 | 华为技术有限公司 | 一种安全传输数据方法,装置和系统 |
WO2014101069A1 (zh) * | 2012-12-27 | 2014-07-03 | 华为技术有限公司 | 一种m2m业务消息传输的方法,设备和系统 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1708082A (zh) * | 2004-06-10 | 2005-12-14 | 国际商业机器公司 | 会议电话呼叫初始化的系统和方法 |
WO2007099295A2 (en) * | 2006-02-28 | 2007-09-07 | Orange Sa | System and method for controlling network access |
US20090161154A1 (en) * | 2007-12-20 | 2009-06-25 | Canon Kabushiki Kaisha | Communication device and method of controlling the same |
US20100150071A1 (en) * | 2008-12-11 | 2010-06-17 | Fujitsu Limited | Radio network system |
CN101790148A (zh) * | 2009-01-22 | 2010-07-28 | 华为技术有限公司 | 注册备份数据处理方法、装置及系统 |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101043701B (zh) * | 2006-03-23 | 2012-03-21 | 华为技术有限公司 | 一种ip多媒体子系统为移动电路域用户提供注册和呼叫接续的方法及其系统 |
-
2010
- 2010-11-22 CN CN2010105572742A patent/CN102014129B/zh not_active Expired - Fee Related
-
2011
- 2011-05-12 WO PCT/CN2011/074006 patent/WO2012068835A1/zh active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1708082A (zh) * | 2004-06-10 | 2005-12-14 | 国际商业机器公司 | 会议电话呼叫初始化的系统和方法 |
WO2007099295A2 (en) * | 2006-02-28 | 2007-09-07 | Orange Sa | System and method for controlling network access |
US20090161154A1 (en) * | 2007-12-20 | 2009-06-25 | Canon Kabushiki Kaisha | Communication device and method of controlling the same |
US20100150071A1 (en) * | 2008-12-11 | 2010-06-17 | Fujitsu Limited | Radio network system |
CN101790148A (zh) * | 2009-01-22 | 2010-07-28 | 华为技术有限公司 | 注册备份数据处理方法、装置及系统 |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109996219A (zh) * | 2018-01-02 | 2019-07-09 | 中国移动通信有限公司研究院 | 一种物联网鉴权方法、网络设备及终端 |
CN109996219B (zh) * | 2018-01-02 | 2022-05-06 | 中国移动通信有限公司研究院 | 一种物联网鉴权方法、网络设备及终端 |
Also Published As
Publication number | Publication date |
---|---|
CN102014129A (zh) | 2011-04-13 |
CN102014129B (zh) | 2013-08-28 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2012068835A1 (zh) | 一种在CoAP网络中注册的方法及装置 | |
CN111711659B (zh) | 远程管理终端方法和装置、设备及其存储介质 | |
WO2014101023A1 (zh) | 一种防止业务非法访问的方法和装置 | |
US7853703B1 (en) | Methods and apparatuses for identification of device presence | |
RU2005127418A (ru) | Интерфейс поставщиков служб устройств | |
WO2011127714A1 (zh) | 一种数字家庭网络设备的跨网关互联方法 | |
WO2019109957A1 (zh) | 基于esb的服务提供方法、装置、设备及可读存储介质 | |
WO2020042464A1 (zh) | 数据交互方法、装置、设备及可读存储介质 | |
WO2017074034A1 (ko) | 이종 시스템에서 상호연동에 대한 방법 및 장치 | |
WO2014112754A1 (ko) | 웹 서비스 푸시 방법 및 이를 수행하는 웹 서비스 푸시 서버 및 웹 서비스 제공 서버 | |
WO2018036168A1 (zh) | 数据处理任务执行方法、装置、执行服务器和存储介质 | |
WO2018000978A1 (zh) | 一种数据备份方法及终端 | |
WO2016140416A1 (en) | Method and apparatus for establishing a connection between devices | |
WO2020009537A1 (ko) | 리소스 관리 방법 및 장치 | |
WO2013024986A2 (ko) | 네트워크 식별자 위치판단 시스템 및 그 방법 | |
WO2018113315A1 (zh) | 物联网定位方法、云端服务器、智能终端及智能硬件 | |
WO2015199271A1 (en) | Method and system for sharing files over p2p | |
EP2403220B1 (en) | Apparatus and method for controlling peripheral in wireless communication system | |
WO2017000178A1 (zh) | 一种建立交互关系的方法以及交互装置 | |
WO2018068587A1 (zh) | 支付位置通知方法及系统、服务器 | |
WO2013023469A1 (zh) | 接入管理方法、装置和系统 | |
WO2013026299A1 (zh) | 一种地址解析方法、装置及信息传输方法 | |
WO2017000210A1 (zh) | 一种信息交互处理方法、系统及终端 | |
JP3809429B2 (ja) | 管理装置及びその制御方法 | |
JP2002324052A (ja) | 無線端末の認証方法、無線基地局及び通信システム |
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: 11842647 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 11842647 Country of ref document: EP Kind code of ref document: A1 |