WO2015032155A1 - 一种物联网异构标识解析方法与系统 - Google Patents
一种物联网异构标识解析方法与系统 Download PDFInfo
- Publication number
- WO2015032155A1 WO2015032155A1 PCT/CN2013/089849 CN2013089849W WO2015032155A1 WO 2015032155 A1 WO2015032155 A1 WO 2015032155A1 CN 2013089849 W CN2013089849 W CN 2013089849W WO 2015032155 A1 WO2015032155 A1 WO 2015032155A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- heterogeneous
- iot
- parsing
- identification
- internet
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 25
- 230000007246 mechanism Effects 0.000 claims abstract description 21
- 230000014509 gene expression Effects 0.000 claims description 3
- 230000000977 initiatory effect Effects 0.000 abstract 1
- 238000004458 analytical method Methods 0.000 description 21
- 238000011160 research Methods 0.000 description 6
- 238000011161 development Methods 0.000 description 4
- 230000008520 organization Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 238000006243 chemical reaction Methods 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 230000001419 dependent effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- JXTHEWSKYLZVJC-UHFFFAOYSA-N naptalam Chemical compound OC(=O)C1=CC=CC=C1C(=O)NC1=CC=CC2=CC=CC=C12 JXTHEWSKYLZVJC-UHFFFAOYSA-N 0.000 description 1
- 230000001737 promoting effect Effects 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
- 238000012108 two-stage analysis Methods 0.000 description 1
Classifications
-
- 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/30—Managing network names, e.g. use of aliases or nicknames
- H04L61/3005—Mechanisms for avoiding name conflicts
-
- 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/09—Mapping addresses
- H04L61/10—Mapping addresses of different types
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/08—Protocols for interworking; Protocol conversion
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/22—Parsing or analysis of headers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2101/00—Indexing scheme associated with group H04L61/00
- H04L2101/30—Types of network names
-
- 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/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
Definitions
- the invention belongs to the technical field of the Internet of Things, and particularly relates to an Internet of Things heterogeneous identifier analysis method, and a system using the same. Background technique
- the Internet of Things which is closely connected with the real physical world, will be far more important than the current Internet.
- the object identification in the Internet of Things will become a more important information resource than the Internet domain name. Therefore, the identification of items in the Internet of Things is difficult to follow the domain name management model allocated by the global unified agency in the Internet, and will be independently allocated and managed by multiple countries or institutions using different coding standards.
- the coding system for item identification mainly includes the EPC (Electric Product Code) code proposed by EPCglobal in the United States, the uCode (Ubiquitous Code) code proposed by the Japanese uID Center, and the Telecommunications Technology Association (TTA).
- the identification protocol corresponding to each item identification is also different.
- EPC encoding, mRFID Code encoding, OID encoding, and CPC encoding all use DNS as their identification resolution protocol
- uCode encoding uses a DNS-like proprietary identification resolution protocol
- Handle encoding uses a Handle System that is completely different from DNS as its identity resolution. Protocol, and Ecode coding has not explicitly adopted which resolution protocol, and the new Internet of Things identifier code in the future may also adopt a new custom proprietary identity resolution protocol.
- the IoT identifiers are not only heterogeneous conflicts at the coding level, but also the heterogeneous identifier resolution protocol conflicts at the corresponding resolution protocol level. As a result, the IoT identifiers using different identifier resolution protocols cannot be uniformly parsed.
- IoT applications At present, most of the Internet of Things applications in the world are closed-loop applications in specific industries or enterprises. Generally, a specific IoT identification coding rule and an identification resolution protocol are adopted, and each relies on a dedicated IoT application, thereby causing existing objects. Networked applications often cannot communicate directly with each other, which not only affects the user experience, but also restricts the scale development of Internet of Things applications. Therefore, for the heterogeneous identification coding conflict problem and the heterogeneous identification resolution protocol conflict problem existing in the Internet of Things, an IoT identification analysis system compatible with any heterogeneous item identification code and any heterogeneous item identification and resolution protocol is implemented. It is of great significance that IoT applications provide universal IoT identification and parsing functions to promote the scale development of various IoT applications.
- the current IoT identification coding system includes various IoT identification codes such as EPC, uCode, mRFID Code, Handle OID, CPC, etc., and the identification resolution protocols corresponding to each item identification are also different.
- IoT ID resolution protocols There are currently three types of IoT ID resolution protocols, namely the DNS protocol, the DNS-like protocol, and the Handle System protocol.
- a new custom IoT ID resolution protocol may appear in the future.
- the existing Internet of Things ID resolution system only supports a single IoT identification code and an ID resolution protocol, and cannot be fully compatible with other IoT identification codes and identification analysis protocols.
- the US EPCglobal proposed that the ONS (Object Name Service) is based entirely on the existing DNS protocol in the Internet, which only supports the resolution of EPC encoding; the UID Center of Japan proposes ucodeRP (ucode Resolution Protocol).
- the proprietary resolution protocol similar to the DNS protocol also supports the parsing of uCode encoding.
- the Handle encoding proposed by the international organization DONA adopts the Handle System protocol different from DNS, which is completely incompatible with the DNS protocol and only supports the parsing of Handle encoding.
- the RNS name service system is a further refinement of the patent ZL200810239867.7.
- a two-stage IoT identification mechanism is proposed.
- the mechanism designs the IoT logo as a two-stage structure of standard code and article code, and divides the IoT identification into two logical parts: standard code parsing and item code parsing.
- the former is responsible for parsing the standard code into a DNS parsing protocol.
- the conversion rule information is identified, by which the item code is converted into a domain name identifier conforming to the DNS resolution protocol, and then the latter can be parsed into a network address corresponding to the Internet of Things identifier.
- the University of Helsinki in Finland builds the DIALOG (Distributed Information Architectures for collaborative LOGistics) system based on the ID@URI mechanism.
- the system divides the Internet of Things identifier into two parts, ID and URI, separated by the identifier "@", where the URI part is based on DNS.
- the protocol is parsed, and the ID part format is specified by the administrator of the field. It only needs to be unique within a given URI to ensure the global uniqueness of the entire IoT logo.
- the ID@URI mechanism uses the existing DNS resolution service. Since this mechanism is completely dependent on the DNS resolution protocol, it is also unable to support the heterogeneous IoT identity resolution protocol of other non-DNS protocols.
- the basic idea is to identify the isomers by means of identification code conversion rule analysis, two-stage analysis, OID analysis or URI analysis.
- the networked identification code is converted into an IoT identification code that follows a specific resolution protocol (such as the DNS protocol), and then the transformed IoT identification code is parsed by a specific resolution protocol, thereby implementing compatible analysis of the heterogeneous IoT identification code.
- the existing solution can only provide parsing for IoT heterogeneous identifiers that follow the specific IoT identification protocol, but cannot resolve different IoT identifiers.
- the IoT heterogeneous logo of the protocol provides compatible parsing support, so the existing research results only partially solve the heterogeneous conflict problem of IoT ID resolution. Summary of the invention
- the existing IoT ID resolution method can only support a specific IoT ID resolution protocol.
- the IoT ID resolution protocol corresponding to the identifier must be predicted in advance, and the corresponding support is adopted.
- the Internet of Things ID resolver of the Internet of Things ID resolution protocol can access the corresponding IoT heterogeneous identifier resolution service to realize the analysis of the IoT heterogeneous identity, which will bring inconvenience to the Internet of Things users.
- IoT users will have difficulty in realizing IoT identification based on their unfamiliar IoT heterogeneous identification protocols.
- the present invention intends to provide a general IoT identification method for IoT applications using any heterogeneous Internet of Things identification resolution protocols (such as DNS, ONS, ucodeRP, Handle System, and custom protocols).
- the IoT user can provide an interpretation mechanism for any heterogeneous IoT identification protocol, so that the Internet of Things users can complete the analysis of various IoT heterogeneous identification protocols based on a common IoT identification module.
- Query which can provide a unified resolution portal for future IoT users.
- the present invention adopts the following technical solutions:
- An IoT heterogeneous identifier parsing method includes the following steps: 1) According to the resolution protocol followed by the IoT heterogeneous identification, a unique standard identification code is assigned to it;
- step 1) binding and registering the standard identifier in step 1) and the heterogeneous identifier resolution protocol in step 2) in the standard identifier resolution server;
- step 1) converting the standard identification code of step 1) into a unified identifier of the Internet of Things based on a specific IoT heterogeneous identifier resolution protocol according to a preset standard identification code resolution protocol;
- the IoT heterogeneous identifier parser initiates the IoT identifier parsing query according to the IoT unified compatible identifier according to step 4), and sends the IoT identifier to the specific standard identifier parsing server based on the corresponding IoT heterogeneous identifier parsing protocol;
- the standard identifier parsing server returns the heterogeneous identifier parsing protocol rule corresponding to the IoT heterogeneous identifier bound to the standard identifier to the IoT heterogeneous identifier parser according to the IoT unified compatible identifier in step 4);
- the IoT heterogeneous identifier parser converts the IoT heterogeneous identifier into an IoT unified compatible identifier based on the corresponding IoT heterogeneous identifier resolution protocol according to the heterogeneous identifier resolution protocol rule obtained in step 6);
- the IoT heterogeneous identifier parser initiates the IoT heterogeneous identity analysis query to the specific IoT heterogeneous identity resolution server according to the corresponding IoT heterogeneous identity resolution protocol according to the IoT unified compatible identifier generated in step 7);
- the IoT heterogeneous identity resolution server returns the registration information corresponding to the IoT heterogeneous identity to the IoT heterogeneous identity resolver according to the IoT unified compatible identifier generated in step 7).
- An Internet of Things heterogeneous identification and resolution system comprising a standard identification code resolution server, an Internet of Things heterogeneous identity resolver, and an Internet of Things heterogeneous identity resolution server;
- the standard identifier resolution server is configured to store and provide a standard identification code and a binding relationship with a heterogeneous identifier resolution protocol rule corresponding to the IoT heterogeneous identifier;
- the IoT heterogeneous identifier parser is configured to initiate an IoT heterogeneous identity parsing query to a specific standard identification code parsing server according to the IoT unified compatible identifier converted by the standard identification code, and parse the server according to the standard identification code.
- the heterogeneous identity resolution protocol rules convert the IoT heterogeneous identity into an IoT unified compatible identifier based on an IoT heterogeneous identity resolution protocol, and then initiate an IoT identity analysis query to a specific IoT heterogeneous identity resolution server;
- the IoT heterogeneous identifier resolution server is configured to return the registration information corresponding to the IoT heterogeneous identifier to the IoT heterogeneous identifier parser according to the IoT unified compatible identifier converted by the IoT heterogeneous identifier.
- the above method and system are an IoT heterogeneous identifier parsing query scheme based on different parsing protocols.
- the present invention also provides an IoT heterogeneous identifier that can handle different encoding rules and can also handle different parsing protocols.
- the resolution scheme is as follows:
- An IoT heterogeneous identifier parsing method includes the following steps: 1) According to the coding rules and resolution protocols followed by the IoT heterogeneous identification, a unique standard identification code is assigned to it;
- a description mechanism that can be identified and processed by the IoT heterogeneous identifier parser is established, and based on the description mechanism, the encoding rule and the parsing protocol corresponding to the IoT heterogeneous identifier respectively generate heterogeneous identifier encoding Rules and heterogeneous identity resolution protocol rules;
- step 1) binding and registering the standard identification code in step 1), the heterogeneous identification coding rule in step 2), and the heterogeneous identification resolution protocol rule in the standard identifier resolution server;
- step 1) converting the standard identification code of step 1) into a standard compatible identifier of the Internet of Things based on a specific IoT heterogeneous identifier resolution protocol according to a preset standard identification code encoding rule and a standard identification code resolution protocol;
- the IoT heterogeneous identifier parser initiates the IoT heterogeneous identifier parsing query according to the IoT unified compatible identifier according to step 4) and the corresponding standard identifier resolving server according to the corresponding IoT identification parsing protocol;
- the standard identification code parsing server returns the heterogeneous identifier encoding rules corresponding to the IoT heterogeneous identifier bound to the standard identification code and the heterogeneous to the IoT heterogeneous identifier parser according to the IoT unified compatible identifier in step 4) Identification protocol rules;
- the IoT heterogeneous identity resolver converts the IoT heterogeneous identity into a unified Internet of Things based on a specific IoT heterogeneous identity resolution protocol according to the heterogeneous identity coding rules and heterogeneous identity resolution protocol rules obtained in step 6) Compatible logo;
- the IoT heterogeneous identifier parser initiates the IoT identifier parsing query according to the IoT unified compatible identifier generated by step 7) and the corresponding IoT heterogeneous identifier parsing server based on the corresponding IoT identifier resolution protocol;
- the IoT heterogeneous identity resolution server returns the registration information corresponding to the IoT heterogeneous identity to the IoT heterogeneous identity resolver according to the IoT unified compatible identifier generated in step 7).
- An Internet of Things heterogeneous identification and resolution system comprising a standard identification code resolution server, an Internet of Things heterogeneous identity resolver, and an Internet of Things heterogeneous identity resolution server;
- the standard identifier resolution server is configured to store and provide a standard identification code and a heterogeneous identifier encoding rule and a heterogeneous identifier resolution protocol rule corresponding to the IoT heterogeneous identifier thereof;
- the IoT heterogeneous identifier parser is configured to initiate an IoT heterogeneous identity parsing query to a specific standard identification code parsing server according to the IoT unified compatible identifier converted by the standard identification code, and parse the server according to the standard identification code.
- the heterogeneous identification coding rules and the heterogeneous identification resolution protocol rules convert the IoT heterogeneous identifier into an IoT unified compatible identifier based on an Internet of Things identifier resolution protocol, and then initiate the Internet of Things to a specific IoT heterogeneous identity resolution server.
- Heterogeneous identifier resolution query ;
- the IoT heterogeneous identifier resolution server is configured to return the registration information corresponding to the IoT heterogeneous identifier to the IoT heterogeneous identifier parser according to the IoT unified compatible identifier converted by the IoT heterogeneous identifier.
- the registration information of step 9) may be the corresponding address of the Internet of Things information server, Or other IoT heterogeneous identifiers corresponding to them.
- the IoT unified compatible identifier converted by the standard identification code may include the following fields: a protocol name, a server entry address following the protocol, a server port number, and a standard identification code converted by an encoding rule. , and parsing protocol query types.
- the Internet of Things unified compatible identifier converted by the IoT heterogeneous identifier may include the following fields: a protocol name, a server entry address following the protocol, a server port number, and a content converted by the encoding rule.
- Networked heterogeneous identity, and resolution protocol query types may include the following fields: a protocol name, a server entry address following the protocol, a server port number, and a content converted by the encoding rule.
- the invention provides a special description mechanism for the parsing protocol adopted by the IoT heterogeneous identifier, correspondingly forms a heterogeneous identifier resolution protocol rule, and binds the rule to the corresponding IoT heterogeneous identifier to participate in IoT ID resolution process. Then, an IoT unified compatible identifier with embedded IoT identification protocol protocol information is proposed.
- the IoT parsing query through the standard identification code can not only obtain the heterogeneous identification coding rules corresponding to the IoT heterogeneous identifier, but more importantly, , can also obtain the corresponding heterogeneous identity resolution protocol rules.
- IoT heterogeneous identifiers can be converted into IoT unified compatible identifiers containing IoT identification protocol information (such as resolution protocol name, resolution server entry address, resolution server port, resolution protocol query type, etc.).
- IoT identification protocol information such as resolution protocol name, resolution server entry address, resolution server port, resolution protocol query type, etc.
- the IoT heterogeneous identifier parser can initiate the correct IoT identification query based on the IoT identification protocol protocol corresponding to the IoT heterogeneous identifier by interpreting the IoT identification protocol information contained in the IoT unified compatible identifier.
- the IoT ID resolution service provider can provide a unified parsing query platform entry for various IoT heterogeneous identifiers based on different coding rules and different resolution protocols;
- IoT ID resolver For the IoT ID resolver, it can use only one IoT heterogeneous identifier parser to implement IoT heterogeneous identity parsing queries based on different encoding rules and different resolution protocols. Install different IoT heterogeneous identifier parsers for different IoT heterogeneous identifiers;
- the IoT heterogeneous identifier resolution method compatible with different coding rules and different resolution protocols can help achieve equal interconnection of various IoT heterogeneous identification applications, thereby promoting the Internet of Things across the domain. Interoperability is achieved within.
- FIG. 1 is a schematic diagram of EPC ONS analysis of the Internet of Things heterogeneous identifier resolution system of Embodiment 1.
- FIG. 2 is a schematic diagram of Handle analysis of the Internet of Things heterogeneous identifier resolution system of Embodiment 2. detailed description The present invention will be described in detail below by way of specific embodiments and the accompanying drawings.
- the IoT heterogeneous identifier resolution process of this embodiment is shown in FIG. 1 . It is assumed that the EPC code 123456789 is to be parsed, and the standard identification code 001 is given thereto (this is an example, the invention is not limited thereto, and other standard identification code formats may also be used), and the standard identification code is encoded according to its default standard identification code. And the standard identification code resolution protocol rules are converted to the Internet of Things.
- the IoT heterogeneous identifier parser converts the standard identification code into the IoT unified compatible identifier based on a specific IoT identification protocol according to its preset standard identification code encoding rule and standard identification code resolution protocol.
- the IoT heterogeneous identifier parser initiates a parsing request to the corresponding standard identifier resolving server according to the IoT unified compatible identifier.
- the standard identification code parsing server returns the isomorphic identifier encoding rule and the heterogeneous identifier parsing protocol rule corresponding to the EPC code 123456789 to the IoT heterogeneous identifier parser.
- the description mechanism used by the rules must be identifiable and handled by the IoT heterogeneous identity resolver. For example, a regular expression can be used as a description mechanism, or a standard format such as XML or JSON can be used as the description mechanism.
- the IoT heterogeneous identity resolver initiates a resolution request to the ONS resolution server based on the IoT unified compatible identifier.
- ONS:// indicates the resolution protocol name
- the embodiment is the ONS resolution protocol
- epcons.cn indicates the server entry address following the ONS protocol
- :53 indicates the server port number
- the ONS parsing server returns the registration information corresponding to the IoT heterogeneous identifier to the IoT heterogeneous identifier parser (IoT information server address 1).
- the IoT heterogeneous identifier parser interacts with the Internet of Things information server 1 according to the obtained IoT information server address.
- the IoT heterogeneous identifier resolution process of this embodiment is shown in FIG. 2 .
- the Handle code 10.123/456 is to be parsed, and the standard identification code 002 is assigned to it.
- the IoT heterogeneous identifier parser converts the standard identification code into the IoT unified compatible identifier based on a specific IoT identification protocol according to its preset standard identification code encoding rule and standard identification code resolution protocol.
- the meaning of each field in the IoT Unified Compatibility Identifier is the same as in Embodiment 1.
- the IoT heterogeneous identifier parser sends a parsing request to the corresponding standard identification code parsing server according to the IoT unified compatible identifier.
- the standard identification code parsing server returns the Handle code 10.123/456 corresponding heterogeneous identity coding rules and heterogeneous identity resolution protocol rules to the IoT heterogeneous identity parser.
- the IoT heterogeneous identifier resolver converts the IoT heterogeneous identifier into an IoT unified compatible identifier based on the Handle System resolution protocol according to the heterogeneous identifier encoding rule and the heterogeneous identifier resolution protocol rule; for example, Handle coding
- the meaning of each field in the IoT unified compatible identifier is the same as that in Embodiment 1.
- the IoT heterogeneous identity parser initiates a resolution request to the Handle System resolution server based on the IoT unified compatible identifier.
- the Handle System resolution server returns the registration information corresponding to the IoT heterogeneous identifier to the IoT heterogeneous identifier resolver (IoT Information Server Address 2).
- the IoT heterogeneous identifier parser interacts with the Internet of Things information server 2 according to the obtained IoT information server address.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Computer And Data Communications (AREA)
- Communication Control (AREA)
Abstract
Description
Claims
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/894,666 US10257160B2 (en) | 2013-09-09 | 2013-12-18 | Method and system for resolving internet of things heterogeneous identifiers |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201310407613.2 | 2013-09-09 | ||
CN201310407613.2A CN103491145B (zh) | 2013-09-09 | 2013-09-09 | 一种物联网异构标识解析方法与系统 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2015032155A1 true WO2015032155A1 (zh) | 2015-03-12 |
Family
ID=49831098
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2013/089849 WO2015032155A1 (zh) | 2013-09-09 | 2013-12-18 | 一种物联网异构标识解析方法与系统 |
Country Status (3)
Country | Link |
---|---|
US (1) | US10257160B2 (zh) |
CN (1) | CN103491145B (zh) |
WO (1) | WO2015032155A1 (zh) |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105184734A (zh) * | 2015-10-15 | 2015-12-23 | 中国科学院计算机网络信息中心 | 基于数字信号处理技术的物联网异构标识生成方法 |
CN111401486A (zh) * | 2019-01-02 | 2020-07-10 | 中国移动通信有限公司研究院 | 一种物联网标识的识别方法、装置及终端设备 |
CN111400348A (zh) * | 2020-03-25 | 2020-07-10 | 贵阳块数据城市建设有限公司 | 一种多种标识编码规则的异构数据处理方法 |
CN112398809A (zh) * | 2020-09-29 | 2021-02-23 | 曙光网络科技有限公司 | 协议规则转换方法、装置、计算机设备和存储介质 |
CN112866375A (zh) * | 2021-01-14 | 2021-05-28 | 国网上海市电力公司 | 一种编码解析系统和方法 |
CN113676555A (zh) * | 2021-09-24 | 2021-11-19 | 迈迪信息技术有限公司 | 一种多级码池的兼容平台以及方法 |
US20220321523A1 (en) * | 2020-09-28 | 2022-10-06 | China Internet Network Information Center | Identifier resolution method and apparatus for the internet of things |
Families Citing this family (38)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103929499B (zh) * | 2014-05-05 | 2017-06-20 | 中国科学院计算机网络信息中心 | 一种物联网异构标识识别方法和系统 |
CN105635063B (zh) * | 2014-10-31 | 2019-04-12 | 腾讯科技(上海)有限公司 | 物联网通信协议配置方法和装置 |
US9900382B2 (en) * | 2015-02-18 | 2018-02-20 | Anna Mazor | Promotion of internet-of-things (IOT) connectivity |
US10673959B2 (en) * | 2015-03-25 | 2020-06-02 | Intel Corporation | Accessing service of Internet of Things |
US10140191B2 (en) * | 2015-07-24 | 2018-11-27 | Accenture Global Services Limited | System for development of IoT system architecture |
CN105224598B (zh) * | 2015-08-31 | 2018-11-27 | 中国互联网络信息中心 | 一种基于动态特征的异构物联网标识识别方法及系统 |
US10887397B2 (en) | 2016-07-28 | 2021-01-05 | Citrix Systems, Inc. | System and method for controlling internet of things devices using namespaces |
CN107888539A (zh) * | 2016-09-29 | 2018-04-06 | 中兴通讯股份有限公司 | 物联网终端接入装置及方法 |
CN107888642A (zh) * | 2016-09-30 | 2018-04-06 | 中国电子科技集团公司信息科学研究院 | 一种标识解析装置、标识解析系统及标识解析方法 |
US10582016B2 (en) * | 2016-10-21 | 2020-03-03 | Intelligent Platforms, Llc | First device with an embedded gateway to support a second communications protocol |
CN106792468B (zh) * | 2016-12-27 | 2019-08-16 | 广州中国科学院计算机网络信息中心 | 机器通信中标识发现的方法与系统 |
CN107147754B (zh) * | 2017-07-13 | 2018-06-29 | 中联惠众信息技术(北京)有限公司 | 一种物联网标识的编码方法及系统 |
CN110022289B (zh) * | 2018-01-10 | 2022-07-05 | 北龙中网(北京)科技有限责任公司 | 数据传输方法、装置及系统 |
CN108460604B (zh) * | 2018-02-07 | 2022-06-24 | 中国科学院计算机网络信息中心 | 一种基于标识服务的工业用大麻追溯系统及方法 |
CN109451083B (zh) * | 2018-09-11 | 2021-10-26 | 东华大学 | 航天结构件工业物联标识高可靠解析系统 |
CN109684450B (zh) * | 2018-12-20 | 2023-07-14 | 中国科学院沈阳自动化研究所 | 一种基于语义化标识的工业网络数据分发服务系统及方法 |
CN110366147B (zh) * | 2019-05-28 | 2022-03-18 | 杭州电力设备制造有限公司 | 泛在物联网室内分布共享系统监测方法及间隔布点法 |
CN112217765B (zh) * | 2019-07-10 | 2023-06-30 | 深圳市中兴微电子技术有限公司 | 报文解析方法和装置 |
CN110601876A (zh) * | 2019-08-20 | 2019-12-20 | 西安向南网络信息科技有限公司 | 一种智能物联网平台 |
CN110737530B (zh) * | 2019-09-25 | 2023-06-16 | 网络通信与安全紫金山实验室 | 一种提升handle标识解析系统收包能力的方法 |
CN110995664B (zh) * | 2019-11-15 | 2021-10-08 | 国网河南省电力公司信息通信公司 | 基于区块链的物联网异构标识解析系统及方法 |
CN111241549B (zh) * | 2020-01-08 | 2022-11-15 | 广州中国科学院计算机网络信息中心 | 一种异构标识体系下的可信解析方法 |
CN111614507B (zh) * | 2020-04-01 | 2021-11-05 | 西安电子科技大学 | 一种网络协议特征识别方法 |
CN111641717B (zh) * | 2020-06-01 | 2022-11-11 | 重庆高开清芯智联网络科技有限公司 | 一种物联网系统内节点数据的管理方法 |
CN111723885B (zh) * | 2020-06-22 | 2024-05-14 | 重庆忽米网络科技有限公司 | 一种工业互联网企业标识交互系统及其实现方法 |
CN111846458B (zh) * | 2020-07-14 | 2021-09-28 | 欧力德(苏州)物流系统工程有限公司 | 一种全自动纸箱裹包系统及其使用方法 |
CN112260872B (zh) * | 2020-10-22 | 2022-03-04 | 北京理工大学 | 一种基于字符串匹配的标识异构识别方法及系统 |
CN114697378B (zh) * | 2020-12-25 | 2024-05-28 | 航天信息股份有限公司 | 一种网站访问方法、装置、设备及介质 |
CN112822307B (zh) * | 2021-03-02 | 2022-08-12 | 中国互联网络信息中心 | 一种网络标识数据的处理方法及装置 |
CN112800803B (zh) * | 2021-04-09 | 2021-07-30 | 腾讯科技(深圳)有限公司 | 图形码识别方法、装置、设备及存储介质 |
CN113297431B (zh) * | 2021-05-28 | 2023-10-24 | 北京邮电大学 | 工业互联网标识解析系统的多体系异构标识兼容方法 |
CN113507531A (zh) * | 2021-06-15 | 2021-10-15 | 山东伏羲智库互联网研究院 | 物联网标识解析方法、边缘网关、电子设备及存储介质 |
CN113553305B (zh) * | 2021-07-30 | 2024-07-30 | 国网数字科技控股有限公司 | 一种工业互联网标识处理方法及装置 |
CN114240451B (zh) * | 2021-11-15 | 2022-05-17 | 国网电子商务有限公司 | 一种产品溯源方法及装置 |
CN114490679A (zh) * | 2021-12-22 | 2022-05-13 | 山东浪潮工业互联网产业股份有限公司 | 一种基于标识解析的数据治理方法、装置、设备及介质 |
CN114710572A (zh) * | 2022-03-31 | 2022-07-05 | 深圳奇迹智慧网络有限公司 | 数据处理方法、装置及计算机存储介质 |
CN115665226B (zh) * | 2022-12-05 | 2023-04-11 | 东南大学 | 一种物联网多编码标识跨域统一映射方法及系统 |
CN116320090B (zh) * | 2023-03-10 | 2023-10-03 | 国家工业信息安全发展研究中心 | 一种多标识编码与handle标识码转换的系统及方法 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101751432A (zh) * | 2008-12-19 | 2010-06-23 | 中国科学院计算机网络信息中心 | 一种物联网寻址方法与系统 |
CN102571732A (zh) * | 2010-12-30 | 2012-07-11 | 中国移动通信集团公司 | 一种处理传感器协议信息的方法、装置和系统 |
CN102694849A (zh) * | 2012-05-14 | 2012-09-26 | 中国科学院计算机网络信息中心 | 物联网资源信息获取方法、终端设备及系统 |
CN103117881A (zh) * | 2013-02-27 | 2013-05-22 | 中国电子器材总公司 | 一种物联网资源管理系统 |
-
2013
- 2013-09-09 CN CN201310407613.2A patent/CN103491145B/zh active Active
- 2013-12-18 WO PCT/CN2013/089849 patent/WO2015032155A1/zh active Application Filing
- 2013-12-18 US US14/894,666 patent/US10257160B2/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101751432A (zh) * | 2008-12-19 | 2010-06-23 | 中国科学院计算机网络信息中心 | 一种物联网寻址方法与系统 |
CN102571732A (zh) * | 2010-12-30 | 2012-07-11 | 中国移动通信集团公司 | 一种处理传感器协议信息的方法、装置和系统 |
CN102694849A (zh) * | 2012-05-14 | 2012-09-26 | 中国科学院计算机网络信息中心 | 物联网资源信息获取方法、终端设备及系统 |
CN103117881A (zh) * | 2013-02-27 | 2013-05-22 | 中国电子器材总公司 | 一种物联网资源管理系统 |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105184734A (zh) * | 2015-10-15 | 2015-12-23 | 中国科学院计算机网络信息中心 | 基于数字信号处理技术的物联网异构标识生成方法 |
CN111401486A (zh) * | 2019-01-02 | 2020-07-10 | 中国移动通信有限公司研究院 | 一种物联网标识的识别方法、装置及终端设备 |
CN111401486B (zh) * | 2019-01-02 | 2023-11-28 | 中国移动通信有限公司研究院 | 一种物联网标识的识别方法、装置及终端设备 |
CN111400348A (zh) * | 2020-03-25 | 2020-07-10 | 贵阳块数据城市建设有限公司 | 一种多种标识编码规则的异构数据处理方法 |
CN111400348B (zh) * | 2020-03-25 | 2023-08-08 | 贵阳块数据城市建设有限公司 | 一种多种标识编码规则的异构数据处理方法 |
US20220321523A1 (en) * | 2020-09-28 | 2022-10-06 | China Internet Network Information Center | Identifier resolution method and apparatus for the internet of things |
US11700227B2 (en) * | 2020-09-28 | 2023-07-11 | China Internet Network Information Center | Identifier resolution method and apparatus for the internet of things |
CN112398809A (zh) * | 2020-09-29 | 2021-02-23 | 曙光网络科技有限公司 | 协议规则转换方法、装置、计算机设备和存储介质 |
CN112866375A (zh) * | 2021-01-14 | 2021-05-28 | 国网上海市电力公司 | 一种编码解析系统和方法 |
CN112866375B (zh) * | 2021-01-14 | 2024-01-23 | 国网上海市电力公司 | 一种编码解析系统和方法 |
CN113676555A (zh) * | 2021-09-24 | 2021-11-19 | 迈迪信息技术有限公司 | 一种多级码池的兼容平台以及方法 |
Also Published As
Publication number | Publication date |
---|---|
US10257160B2 (en) | 2019-04-09 |
CN103491145B (zh) | 2015-05-20 |
CN103491145A (zh) | 2014-01-01 |
US20160182446A1 (en) | 2016-06-23 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2015032155A1 (zh) | 一种物联网异构标识解析方法与系统 | |
TWI475863B (zh) | 使用快取之安全資源名稱解析 | |
CN102882990B (zh) | 一种无线传感器网络标识解析方法 | |
Cheshire et al. | DNS-based service discovery | |
EP3043273A1 (en) | Systems and methods for ontological searching in an iot environment | |
WO2013170616A1 (zh) | 物联网资源信息获取方法、终端设备及系统 | |
Newton et al. | Registration data access protocol (rdap) query format | |
AU2010263076B2 (en) | Characterizing unregistered domain names | |
CN103037030B (zh) | 支持域名组dns解析的方法和系统 | |
CN101924799A (zh) | 一种对域名进行信息查询的方法和系统 | |
CN112929464A (zh) | 标识解析方法、装置、系统、动态适配器及可读存储介质 | |
Cheshire et al. | RFC 6763: DNS-based service discovery | |
CN103546593A (zh) | 基于ip与非ip的无线传感器网络节点标识符解析方法 | |
Daigle | Domain-based application service location using URIs and the dynamic delegation discovery service (DDDS) | |
Ayoub et al. | DNS for IoT: a survey | |
KR101700197B1 (ko) | 장치 관리를 위한 노드의 주소 표현 방법 및 이를 위한 장치 | |
US8296853B2 (en) | Method and system for authenticating a user | |
Tian et al. | RNS-a public resource name service platform for the internet of things | |
JP2015095903A (ja) | 複数プロビジョニング・オブジェクトのオペレーション | |
Hoffman | Representing dns messages in json | |
US20170310781A1 (en) | Object Information Processing Method and Apparatus, and ORS Application Gateway | |
CN102521757A (zh) | 基于智能终端的商户会员卡一键申请方法 | |
CN103903036A (zh) | 一种大容量、易更新的二维码系统 | |
Kong et al. | A model supporting any product code standard for the resource addressing in the internet of things | |
CN117749761B (zh) | 基于工业互联网标识的标识解析方法和装置、设备和介质 |
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: 13893023 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14894666 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC ( EPO FORM 1205A DATED 15/06/2016 ) |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 13893023 Country of ref document: EP Kind code of ref document: A1 |