CN106134159B - Enhance distributive resources list - Google Patents

Enhance distributive resources list Download PDF

Info

Publication number
CN106134159B
CN106134159B CN201580013351.9A CN201580013351A CN106134159B CN 106134159 B CN106134159 B CN 106134159B CN 201580013351 A CN201580013351 A CN 201580013351A CN 106134159 B CN106134159 B CN 106134159B
Authority
CN
China
Prior art keywords
resource
node
endpoint
message payload
network
Prior art date
Legal status (The legal status 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 status listed.)
Expired - Fee Related
Application number
CN201580013351.9A
Other languages
Chinese (zh)
Other versions
CN106134159A (en
Inventor
董丽君
王重钢
黛尔·N·希德
李庆光
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Convida Wireless LLC
Original Assignee
Convida Wireless LLC
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 Convida Wireless LLC filed Critical Convida Wireless LLC
Publication of CN106134159A publication Critical patent/CN106134159A/en
Application granted granted Critical
Publication of CN106134159B publication Critical patent/CN106134159B/en
Expired - Fee Related legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/104Peer-to-peer [P2P] networks
    • H04L67/1061Peer-to-peer [P2P] networks using node-based peer discovery mechanisms
    • H04L67/1065Discovery involving distributed pre-established resource-based relationships among peers, e.g. based on distributed hash tables [DHT] 
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/45Network directories; Name-to-address mapping
    • H04L61/4541Directories for service discovery
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/51Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • Computer And Data Communications (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Computing Systems (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

Accoding to exemplary embodiment, enhancing distributive resources list provides resource lookup ability, without knowing the uniform resource identifier of resource.For example, Resource TOC node can receive message payload from endpoint.Message payload includes registration request or resource lookup request.Resource TOC node can determine keyword associated with message payload.Keyword may include parameter and value associated with parameter.After determining keyword, keyword can be applied to hash function to generate the map information of the mark with peers catalogue.Based on map information, message payload can be transmitted to peers catalogue by Resource TOC.Resource TOC can receive response from peers catalogue, allow to response appropriate being supplied to request endpoint.

Description

Enhance distributive resources list
Cross reference to related applications
This application claims the excellent of the U.S. Provisional Patent Application Serial No. No.61/951,141 submitted on March 11st, 2014 It first weighs, entire contents are expressly incorporated herein by reference.
Background technique
Resource constraint node and network constitute the pith of Machine To Machine (M2M) and Internet of Things (IoT) system.Interconnection Net engineering task force (IETF) constraint RESTful environment (CoRE) working group (IETE CoRE) has developed CoRE resource mesh It records (RD).Fig. 1 shows the example of CoRE Resource TOC framework and CoRE Resource TOC provides the Web that Resource TOC is supported Interface enables Web server to find Resource TOC.In addition, web interface allows Web server to register, safeguard, check and delete Except resource description.IETF is also defined can be in conjunction with the link attribute that Resource TOC uses.
With reference to Fig. 1, the Resource TOC 100 in CoRE RD framework is illustrated.Resource TOC 100 is in other Web services Device --- commonly referred to as endpoint such as endpoint 102 --- resources bank of the associated Web link of the resource of trustship.Endpoint can refer to The associated Web server of portal, a physical node can be with trustship one or more endpoint as a result,.It can be in various M2M/IoT Trustship endpoint in equipment.Resource TOC 100 be endpoint 102 realize RESTful (representative state transfer) sets of interfaces to register and The set (referred to as Resource TOC item) of maintaining webs link.Interface also makes Resource TOC verification item, and make client (such as Client 104) from Resource TOC 100 search resource.Resource typically refers to the unique, addressable entity in RESTful framework.End Point also functions as client, therefore, the trusteeship customer end also in M2M/IoT equipment.
Resource TOC item referring still to Fig. 1, on 102 Active Registration of endpoint and maintenance Resource TOC 100.These are soft State and need be periodically flushed.Endpoint 102 has registration, updates and delete the interface of specified Resource TOC item.In addition, can make Format is linked with CoRE, finds Resource TOC.Resource TOC, such as Resource TOC 100, can actively discover from Resource TOC 100 Web link, and they are added to Resource TOC item.Resource TOC 100 can also actively discover Web link to test Demonstrate,prove existing Resource TOC item.Format is linked using CoRE, the Web link for finding to be stored in Resource TOC 100 is provided Lookup interface.
Fig. 2 shows the current techniques of the resource registering in CoRE Resource TOC framework.With reference to Fig. 1 and 2, endpoint 102 is used Registration interface 106 registers its resource.202, registration interface 106 receives POST from endpoint 102.Format is linked according to CoRE, POST can be included in the list of the resource to be added to catalogue in message payload.POST can also include instruction endpoint 102 title, the inquiry string parameter in domain associated with endpoint 102 and registration lifetime phase.In this example, in addition to endpoint names All parameters are optional.Then, Resource TOC 100 creates new resources or updates the existing resource in Resource TOC and return to it Position (204).According to the example, when with 106 refresh registration of registration interface, the received position of Resource TOC 100.By In the period that lifetime parameter indicates, the endpoint resources in Resource TOC 100 is made to keep effective.Endpoint 102 uses registration interface 106 or more new interface be responsible for refreshing item within the period.
Continue background example referring to figs. 1 to 3, for the resource for using Resource TOC 100 to find its registration, can provide and look into Look for interface 108.Interface 108 is searched to 104 given example of client to interact with RD 100, such as realizes " GET " method.Example Property URI template is/{+rd-lookup-base }/{ lookup-type }? d, ep, gp, et, rt, page, count, resource-param}.Exemplary parameter includes:
● rd-lookup-base:=RD searches collection of functions path (pressure).This is the path that RD searches collection of functions, one In a little situations, as long as possible, RD will be worth " rd-lookup " for the variable.
● lookup-type:=(" d ", " ep ", " res ", " gp ") (pressure).The variable is used to the type for selecting to search With execution (such as domain, endpoint or resource).
● ep:=endpoint (optional).For endpoint, group and resource lookup.
● the domain d:=(optional).For domain, group, endpoint and resource lookup.
● page:=pages (optional).Parameter cannot be used, count parameter is not necessarily to.From comprising since index (page * counting) " counting " result page in result set return the result.
● count:=counts (optional).As a result counting can be limited to the parameter value.It in some cases, if should Parameter is not present, then using the specific default value of RD embodiment.
● rt:=resource type (optional).For group, endpoint and resource lookup.
● et:=endpoint type (optional).For group, endpoint and resource lookup.
● resource-param:=link attribute parameter (optional).The parameter can indicate such as in 6690 " Core of RFC Link attribute defined in 4.1 chapters and sections of Link Format ".For resource lookup.
Fig. 3 shows the current techniques for the resource lookup in CoRE Resource TOC framework.As indicated, 302, client 104 search Resource TOC (rt) parameter.In this example, client 104 just attempt be found to have temperature resource type (such as temperature Spend sensor) resource.Resource type is set to temperature as a result,.304, as indicated, the return of RD 100 has URI " coap: the resource of //node1/temp ".
It concentrates such as the Resource TOC 100 specified in CoRE Resource TOC framework.The Resource TOC of concentration lacks across interconnection The scalability of net.For example, certain clients may only want to access the resource in their local domains.Do not influencing other clients In the case where, pooling of resources catalogue does not support this location resource allocation yet.Therefore, it is proposed to distributive resources list.
Fig. 4 shows the example distributed Resource TOC DRD 400 in exemplary DRD framework.The distribution proposed Resource TOC framework provides to enable with the interface of distributed hash table and defining how using distributed hash table ability point Cloth Resource TOC.The Resource TOC of participation constitutes distributive resources list covering.The distributive resources list (DRD) proposed Framework provides REST interface identical with pooling of resources catalogue.Endpoint can be the one or more constraint application protocols of operation (CoAP) server, and the physical node of the REST operation (such as POST, GET) in DRD can be used.Endpoint can also serve as visitor Family end.Endpoint can be referred to as CoAP client as a result,.Traditional or common HTTP client is also required to access and stores in DRD Resource.As indicated, the various nodes in DRD framework include endpoint (EP) 402, peer device (P) 404, HTTP Proxy (HP) 406, HTTP client 408 and CoAP client 410.As indicated, endpoint 402 is resident in " node " above and is assisted using CoAP The entity of communication is discussed, thus, it is possible to be referred to as CoAP endpoint.CoAP endpoint can be the source or destination of CoAP message.Peer device 404 be all standing member node, can forward the message to destination along the path by the covering.Some peer devices are also Serve as HTTP Proxy 406.In other words, other than serving as peer device, node acts also as the agency for protocol conversion.HTTP Agency 406 can run HTTP and CoAP agreement, and execute conversion between the two.HTTP client 408 is using HTTP Message, Xiang Zhiding Resource TOC issue the client of request.CoAP client 410 is using CoAP message, Xiang Zhiding resource mesh Record issues the CoAP entity of request.
Fig. 5 shows the current techniques of the resource registering in distributive resources list 400.For example, in resource registering, It includes CoAP POST message of the Resources list with by its resource registering that 502, EP 402a, which send (in payload of message), Into distributive resources list 400.EP 402 is done so, and makes it possible to find its resource.Work as peer device, for example, the first equity Equipment 404a (operation distributed hashing table algorithm covers distributive resources list is added) receives registration message, will be in external source CoAP URI hash under CoAP registration structure be stored in distributed hash table (504).Effective load of CoAP registration Lotus is stored as the value in covering.506, after obtaining distributed hash table ACK message from the second peer device 404b, the first equity Equipment 404a sends EP 402a (508) for CoAP ACK message to indicate the resource registering to distributive resources list In 400.
At 502, POST request includes the inquiry string parameter for indicating the title of EP 402a, for uniquely identifying EP 402a.Endpoint names setting has different alternatives.A kind of method is the MAC Address of hashing device to generate endpoint names. Another method is using commonname.
For example, referring still to Figure 4 and 5, if the endpoint with title " 9996172 " is want a temerature resource It is registered in distributive resources list 400 with a lights resource description, endpoint, which is sent, has URI " coap: //overlay- 1.com/proxy-1/.well-known/core? the POST request of ep=9996172 ".Resource description includes having in message It imitates in load.The example of registration message is as follows:
Req:POST coap: //overlay-1.com/proxy-1/.well-known/core? ep=9996172
Payload:
</temperature-1>;Lt=41;Rt=" Temperature ";If=" sensor ",
</light-2>;Lt=41;Rt=" LightLux ";If=" sensor "
It therefore, is coap applied to the keyword of hash function: //overlay-1.com/proxy-1/.well- Known/core? ep=9996172 determines that the second peer device 404b (P2) is the peer device for storing the value.At second pair Etc. the value that stores on equipment 404b be payload.
The current techniques of resource discovering in distributive resources list 400 are shown with reference to Fig. 6, Fig. 6.Distributive resources list 400 support to merge to obtain the address information of resource by extracting the map information between CoAP URIs and node ID s.Tool Body, 602, CoAP GET request is sent distributive resources list 400 by endpoint (such as client 410a in Fig. 6), The URI information of resource including request.Handle the distributive resources list peer device (peer device in Fig. 6 of the request 404c) distributed hash table is executed to the hash of CoAP URI to search.Then, distributed hash table searches the value for being responsible for resource Peer device (the peer device 404b in Fig. 6).606, storage value is returned to peer device by destination peer device 404b 404c.608, content (such as storage value) is sent back client 410, also referred to as endpoint 410a by peer device 404c.
For example, as specified herein, if client 410a wants to be found to have URI:coap: //overlay-1.com/ Proxy-1/.well-knwn/core? the resource of ep=9996172, peer device 404c receive GET request, and to mapping URI to peer device 404b uses hash function.Therefore, peer device 404c forwards requests to peer device 404b.It is right Etc. equipment 404b the payload of resource is returned into peer device 404c, in turn, peer device 404c returns payload Back to client 410a.
Summary of the invention
As described above, CoRE Resource TOC includes centralized resource catalogue, so that concentrating CoRE Resource TOC.People's will of the present invention Convergence directory cannot simultaneously effective be accessed by client and cannot effectively extend IoT system or M2M network by knowing.This Outside, it is appreciated that in addition to other shortcomings, above-mentioned distributive resources list also limits registration ability and search capacity.
This document describes the method, apparatus and system for enhancing distributive resources list (DRD).In exemplary embodiment In, the node in distributive resources list network, such as Resource TOC node receive message payload from endpoint.Message is effective Load may include registration request or resource lookup request.After receiving message payload, Resource TOC server can be true Fixed keyword associated with message payload.Keyword can have parameter and value associated with parameter.It is closed determining After key word, keyword is applied to hash function to generate map information associated with peers catalogue.Believed based on mapping Message payload can be transmitted to peers catalogue by breath, Resource TOC server.After transmitting message payload, money Source directory node can be received from each peers catalogue and be responded.These responses can indicate the storage at peers catalogue The position of resource or content.After receipt of a response, Resource TOC node can be by combining these responses to generate final response. Final response can be transmitted to the request endpoint that can be Web server by Resource TOC node.Final response may include hash Parameter.
The general introduction is provided to be introduced in simplified form by the selection of the concept further described in detailed description below.This is general The key features or essential features for being not used in the theme that mark requires are stated, without come the range that limits the theme of requirement.In addition, It is required that theme be not limited to solve the imperfect limitation of mention any or institute in any a part of the disclosure.
Detailed description of the invention
It provides described below, can be more fully understood from the example in conjunction with attached drawing, in which:
Fig. 1 is the system diagram for showing constraint RESTful environment (CoRE) Resource TOC framework;
Fig. 2 is the exemplary flow chart for showing the resource registering in CoRE Resource TOC framework;
Fig. 3 is the exemplary flow chart for showing the resource lookup in CoRE Resource TOC framework;
Fig. 4 is the system diagram for showing example distributed Resource TOC framework;
Fig. 5 is the exemplary flow chart for showing the resource registering of the distributive resources list shown in Fig. 4;
Fig. 6 is the exemplary flow chart for showing the Resource TOC of the distributive resources list shown in Fig. 4;
Fig. 7 is the flow chart of the resource registering from endpoint of use storage auxiliary mechanism accoding to exemplary embodiment;
Fig. 8 is the process of the resource registering from another endpoint of use storage auxiliary mechanism accoding to exemplary embodiment Figure;
Fig. 9 is the flow chart of light (lights) the group registration in storage auxiliary mechanism accoding to exemplary embodiment;
Figure 10 is the flow chart of pressure (pressure) the group registration in storage auxiliary mechanism accoding to exemplary embodiment;
Figure 11 is the flow chart of the resource lookup in storage supplementary embodiments accoding to exemplary embodiment;
Figure 12 is the flow chart of another resource lookup in storage supplementary embodiments accoding to exemplary embodiment;
Figure 13 is the flow chart of the another resource lookup in storage supplementary embodiments accoding to exemplary embodiment;
Figure 14 is the flow chart of the another resource lookup in storage supplementary embodiments accoding to exemplary embodiment;
Figure 15 is the exemplary flow chart of resource registering accoding to exemplary embodiment;
Figure 16 is another exemplary flow chart of resource registering according to another exemplary embodiment;
Figure 17 is the flow chart of light (lights) group registration accoding to exemplary embodiment;
Figure 18 is the flow chart of pressure (pressure) group registration accoding to exemplary embodiment;
Figure 19 is the exemplary process of resource lookup of reference guarantee (ensured) embodiment accoding to exemplary embodiment Figure;
Figure 20 is the exemplary flow chart of another resource lookup of reference guarantee embodiment accoding to exemplary embodiment;
Figure 21 is the exemplary flow chart of another resource lookup of reference guarantee embodiment accoding to exemplary embodiment;
Figure 22 A can be achieved on the example machine of one or more disclosed embodiments to machine (M2M) or Internet of Things (IoT) system diagram of communication system;
Figure 22 B is the system diagram of workable exemplary architecture in the M2M/IoT communication system shown in Figure 22 A;
Figure 22 C is that workable exemplary M2M/IoT terminal or gateway are in the communication system shown in Figure 22 A System figure;And
Figure 22 D is the exemplary computing system block diagram for embodying the communication system various aspects of Figure 22 A.
Specific embodiment
Following detailed descriptions are provided to show exemplary embodiment and not limit the scope of the invention, application or match It sets.Without departing from the spirit and scope of the present invention, it can be made in terms of the function of element and arrangement and step Various changes.
Terms used herein " overlay network " refer to the network constructed on the top of another network.In overlay network Node can be considered as by the virtual or logical link connection in basic network, and each link corresponds to path.For example, distributed system System, such as reciprocity (P2P) network can be considered as overlay network, because their node is run on upper internet.As used herein , the node as " ownership place Resource TOC (RD) " refers to when EP wants to register its resource, and first for endpoint (EP) connects Node.Ownership place RD also refers to the first point of contact when client wants find resource, for client.As it is used herein, Node as " storage RD " can refer to storage resource registration entries and ownership place RD forwards the discovery request of client to it Peer device.As it is used herein, unless otherwise indicated, the node as " responsible RD " refers in resource registering message All possible keywords on the RD of peer device that is obtained using hash function.As it is used herein, unless otherwise indicated, Node as " core is responsible for RD ", which refers to, to be responsible for as ownership place RD to its first point of contact for forwarding resource discovering to request One in RDs.
Accoding to exemplary embodiment, enhancing distributive resources list can support resource lookup, without knowing as described herein The uniform resource identifier (URI) of road resource.In one example, multiple copies of resource description are stored in multiple resource mesh It records in (RD), herein referred as equity RD.In another embodiment as described herein, referred to as referring to guarantee (RE) embodiment In, registration message is sent only one equity RD by ownership place peer device, and by the ground of storage resource and its relevant information Inform other equities RD in location.
It is typically referenced to the distributive resources list framework illustrated in Fig. 4, embodiment as described herein realizes advanced distribution Formula resource lookup.In one example, client does not need to know resource URI in advance to find and retrieve resource.For example, client End can request and search the resource of the specified inquiry based on link parameter to their ownership place RD.In other words, distributed Resource TOC can return to the resource for meeting the inquiry based on link parameter to client.
In the exemplary embodiment, storage auxiliary (SA) embodiment can be known as, provide resource in multiple peer devices The redundant copy of registration.Recognize that cost associated with the storage of these data reduces when data storage capacities increase, by This, peer device can effectively be equipped with data storage capacities.As described in detail below, crucial by the possibility in the value of resource Hash function is used on word and/or parameter, be can choose peer device and is stored for data.Selected peer device can make With their storage capacity, storage resource registration.In some cases, it is assumed that application be expressed as a hash function of H () with In all Resource TOC peer devices, unified and distributed hashing space is generated.
For convenience, as it is used herein, unless otherwise indicated, reciprocity RD can be referred to as peer device.Client energy Each lookup keyword/parameter, the parameter of such as following citings are specified, but is not limitation:
D: domain
Ep: endpoint
Gp: group name
Et: endpoint type
Rt: resource type
Lt: resource longevity phase
If: interface
For further example, it is following be the resource that can be registered to one or more RD peer devices proposed and they Payload example, but be not limitation:
1.ep=9996172
Payload:</temperature-1>;Lt=41;Rt=" temperature ";If=" sensor ",
</temperature-2>;Lt=41;Rt=" LightLux ";If=" sensor "
2.ep=9234571
Payload:</Temp-1>;Rt=" temperature ";If=" gateway "
3.gp=lights
Payload:<coap: //host1:port1>;Ep=" node1 ";D=" domain1 "
<coap://host1:port 1>;Ep=" node2 ";D=" domain1 "
4.gp=pressure
Payload<coap: //host2:port 2>;Ep=" node2 ";D=" domain1 "
In the exemplary embodiment, specified endpoint can search directory service by obtaining candidate IP address in various ways Device.For example, in some cases, each equity RD at least has following basic RD resources :/rd >;Rt=" core.rd ";</ rd-lookup>;Rt=" core.rd-lookup ";And</rd-group>;Rt=" core.rd-group ".Such as this paper institute It states, resource interface can be used in endpoint, by its resource registering to its ownership place RD.The interface can receive POST from port. POST may include as the message payload in CoRE link format, be added to the Resources list of catalogue.POST may be used also Comprising inquiring string parameter.In some cases, instead of only hashing the title of endpoint or group, reciprocity RD can be answered hash function To contain all parameters and their value in the payload of resource (such as the description of resource link format).It is dissipated in application After array function, ownership place RD can obtain the address for being responsible for the peer device for the resource that storage has identical parameters.Pass through as a result, It can be sent resource payload to using by the large storage capacity and its relevant low cost, ownership place RD of peer device The peer device of hash.As described above, there are four exemplary resources and payload, it is described herein exemplary to further describe SA is realized.It include that the example of the resource registering of EP 9996172 of EP 702 is shown as in Fig. 4 by description first.
Fig. 7-21 (described below) shows each embodiment of the method and apparatus for management and retrieval resource.At these In figure, each step or operation are shown as being executed by one or more endpoints, client and/or peer device.It will be appreciated that at this A little endpoint, client and/or peer devices shown in figure can indicate the logic entity in communication network and may be implemented At software (such as computer executable instructions), it is stored in the memory of the node of the network and is executed on reason device at which, Node may include one in the generic structure of Figure 22 C or 22D described below.That is, method shown in Fig. 7-21 can be with Software form (such as computer executable instructions) are implemented as, in network node node or department of computer science as shown in Figure 22 C or 22D It is stored in the memory of system, which executes step as shown in the figure when the processor execution by node. It shall yet further be noted that under the control of the computer executable instructions (such as software) of the processor and its execution of node, by the logical of node Letter circuit (respectively such as the circuit 34 or 97 of Figure 22 C and 22D) executes these any transmission shown in figure and receiving step.
Referring now to Figure 7, exemplary network 700 include EP 702 and peer device 1,3,5 and 11 (P1, P3, P5, and P11).It should be understood that the model that describes and be not used in the limitation disclosure of the simplified example network 700 in order to published subject It encloses.In addition to or instead of network such as network 700, embodiment described herein can also be realized using other equipment, system and configuration, And all these embodiments are contemplated that as within the scope of this disclosure.It will be appreciated by repeated reference in different figures Number indicates same or similar feature in figure.
As indicated, the example according to shown in, there is title 9996172 in 704, EP 702 and by its resource registering to work For the P1 of its ownership place RD.Can explain to include link format in payload and determination and the registration phase in 706, P1 Associated keyword/parameter are as follows:
Ep=9996172
Lt=41
Rt=" temperature "
Rt=" LightLux "
If=" sensor "
Above-mentioned keyword/parameter may be used as the keyword for being applied to hash function.When application hash function, according to As a result the example includes P3, P5 and P11.Registration message is forwarded to P3, P5 respectively in 708a, 708b and 708c, P1 as a result, And P7.Confirmation is simultaneously returned to P1 (in 710a-c) by each storage payload of P3, P5 and P7.It can be combined in 712, P1 These confirmation responses.714, response confirmation, P1 response EP 702.In some cases, different keywords lead to registration message It is forwarded to same equity RD.For example, by hash lt=41 or if=" sensor ", the result of two hash can indicate P5 It should be peers catalogue.Similarly, when " and when rt=" LightLux ", two dissipate hash rt=' temperature The result of column can indicate that P11 should be peers catalogue.
Referring now to Figure 8, exemplary network 800 includes the EP 9234571 and peer device 3,2 for being shown as EP 802, 11, and 6 (P3, P2, P11 and P6).It should be understood that description and not of the simplified example network 800 in order to disclosed theme It limits the scope of the present disclosure.In addition to or instead of network such as network 800, can also be realized using other equipment, system and configuration Embodiment as described herein, and all these embodiments can be expected within the scope of this disclosure.
As indicated, the example according to shown in, EP 802 has title 9234571 and 804, by its resource registering to work For the P3 of its ownership place RD.Can explain to include link format in payload and determination is related to registration in 806, P3 Keyword/parameter of connection is:
Ep=9234571
Rt=" temperature "
If=" gateway "
Above-mentioned keyword may be used as the input of hash function.When application hash function, according to example, as a result include P2, P11 and P5.Registration message is forwarded to P2, P11 and P5 respectively in 808a, 808b and 808c, P3 as a result,.P2, P11 and P5 Each storage payload and confirmation is returned to P3 (in 810a-c).These confirmations can be combined in 812, P3 to ring It answers.814, response confirmation, P3 response EP 802.
Referring now to Figure 9, accoding to exemplary embodiment, proposing " lights " group registration example.As indicated, exemplary network 900 include EP 902, the management node being also discussed further below and peer device 1,3,6 and 2 (P1, P3, P6 and P2).It answers Understand, simplified example network 900 in order to published subject description and do not limit the scope of the present disclosure.In addition to or replace Outside network such as network 900, embodiment as described herein can also be realized using other equipment, system and configuration, and own These embodiments can be expected within the scope of this disclosure.
As indicated, the example according to shown in, management node (EP 902) is used to configuration group.It is belonged in 904, EP 902 Ground RD (P1) issues request.Request indicates optional domain belonging to the title and the group of the group of creation.Registration message can also include Belong to the list of the endpoint of the group.Can explain to include link format in payload and determination and the note in 906, P1 Associated keyword/the parameter of volume is:
Gp=light
Ep=" node1 "
D=" domain1 "
Ep=" node2 "
Above-mentioned keyword/parameter may be used as the input of hash function.When application hash function, according to the example, knot Fruit includes P1, P3, P6 and P2.Registration message is forwarded to P3, P6 and P2 respectively in 908a, 908b and 908c, P1 as a result,.Cause It stores payload for peer device P3, P6 and P2 and confirmation is returned to P1 (in 910a-c).Because P1 is pair of hash Etc. one in equipment, 907, also can store registration message.These confirmation responses can be combined in 912, P3.914, ring It should confirm, P3 response EP 902.
Referring now to Figure 10, accoding to exemplary embodiment, proposing " Pressure " group registration example.As indicated, exemplary Network 1000 includes EP 1002, the management node being also discussed further below and peer device 1,3,6 and 2 (P1, P3, P6 and P2).It should be understood that simplified example network 1000 in order to published subject description and do not limit the scope of the present disclosure.It removes Or network such as network 1000 is replaced, it can also realize embodiment as described herein using other equipment, system and configuration, and And all these embodiments can be expected within the scope of this disclosure.
As indicated, the example according to shown in, management node (EP 902) is used to configuration group.It is returned in 1004, EP 1002 Possession RD (P1) issues request.Request indicates optional domain belonging to the title and the group of the group of creation.Registration message can also wrap Include the list for belonging to the endpoint of the group.Interpretable in 1006, P1 includes link format in payload and determination and this Registering associated keyword/parameter is:
Gp=pressure
D=" domain1 "
Ep=" node2 "
Above-mentioned keyword/parameter may be used as the input of hash function.When application hash function, according to the example, knot Fruit includes P1, P3, P6 and P2.Registration message is forwarded to P3, P6 and P2 respectively in 1008a, 1008b and 1008c, P1 as a result,. Because peer device P3, P6 and P2 store payload and will confirm that back to P1 (in 1010a-c).Because P1 is hash One in peer device, 1007, it also can store registration message.These confirmation responses can be combined in 1012, P3.? 914, respond the confirmation, P3 response EP 1002.
For example, after above with reference to described in Fig. 7-10, executing distributed resource and group registration, reciprocity RDs can be deposited Storage citing propose rather than limitation table 1 (hereafter) shown in information.
Table 1: Resource TOC content example
In some cases, above-mentioned resource and group register method make via it is above-mentioned existing search (it was found that) interface, look into Look for (it was found that) resource and group.It is searched turning now to resource and group, by background, client sends resource lookup to its ownership place RD Request.Resource lookup request can the desired lookup type and parameter found in given client end.Ownership place RD can analyze the request And extract the specified keyword of client.In the exemplary embodiment, hash function is applied to these keys by ownership place RD Word come calculate storage resource registration reciprocity RD.Keyword can use AND or OR connection.For example, can be crucial by AND connection Word, because each (RDS pointed out after application hash function) same resource registering of storage of final RD, and can will ask It asks and is forwarded to one of which.Ownership place RD can be randomly or based on certain contextual informations, and such as destination RD's is negative It carries or the bandwidth between ownership place RD and destination RD picks up destination RD.When the resource distribution for being likely to meet specified request It, can be by OR concatenated key when on redundancy RD.Therefore, ownership place RD may need to forward requests to all redundancy RD with Receive the engagement collection (joint set) of resource.
Ownership place RD can determine the reciprocity RD that the request should forward.After ownership place RD receives response from reciprocity RD, The look-up table of the complete list comprising resource is generated as a result, being not necessarily to duplication, and the list can be returned to requesting client.
Propose example below resource is shown and group is searched according to each exemplary embodiment.With reference to Figure 11, show Including GET/rd-lookup/res? the example of rt=" temperature " AND it=" gateway " search request.Figure 11 shows It out include client 1102, the exemplary network 1100 of ownership place RD 1104 and peer device 11 (P11).It should be understood that simplification is shown Example property network 1100 in order to published subject description and do not limit the scope of the present disclosure.In addition to or instead of network such as network 1100, embodiment as described herein can also be realized using other equipment, system and configuration, and all these embodiments can To be expected within the scope of this disclosure.
As indicated, resource lookup request is sent ownership place RD 1104 by client 1102 1106.Client 1102 Go for the resource for meeting rt=" temperature " He it=" gateway " simultaneously.1108, ownership place RD will be hashed Function is applied to the both keyword pointed out in the request.When application hash function when, according to example, as a result include P11 and P6.In in illustrative aspect, ownership place RD 1104 can choose shown in one in RD (P11 and P6) it is complete to obtain Resource lookup result.In the example shown, HRD selects P11, and 1110, sends P11 for search request.1112, Response associated with the request is returned to ownership place RD 1104 by P11.1114, response is forwarded to by ownership place RD 1104 Client 1102.
With reference to Figure 12, show including GET/rd-lookup/res? rt=" LightLux " OR it=" gateway " The example of request.Figure 12 shows the example including client 1202, ownership place RD 1204 and peer device 11 (P11) and 6 (P6) Property network 1200.It should be understood that simplified example network 1200 in order to published subject description and do not limit the disclosure Range.In addition to or instead of network such as network 1200, reality as described herein can also be realized using other equipment, system and configuration Example is applied, and all these embodiments can be expected within the scope of this disclosure.
As indicated, resource lookup request is sent ownership place RD 1204 by client 1202 1206.Client 1202 Go for the resource for meeting rt=" LightLux " or it=" gateway ".1208, ownership place RD is by hash function application In the both keyword pointed out in the request.Because the needs of ownership place RD 1104 forward requests to OR concatenated key Two RD (P11 and P6) pointed out obtain complete resource lookup result.As a result, in the example shown, HRD asks lookup It asks and is sent to P11 (in 1210a) and P6 (in 1210b).Respectively in 1212a and 1212b, response associated with the request is returned Back to ownership place RD 1204.1214, ownership place RD 1204 can combine received response.In addition, 1214, ownership place RD It can be with combined result, so that eliminating duplicate answer.1216, ownership place RD sends the combination response as complete lookup result To client 1202, thus meet search request.
Referring now to Figure 13, showing including GET/rd-lookup/gp? the example of d=" domain1 " search request.Figure 13 show the exemplary network 1300 including client 1302, ownership place RD 1304 and peer device 1 (P1).It should be understood that simplifying Exemplary network 1300 in order to published subject description and do not limit the scope of the present disclosure.In addition to or instead of network such as net Outside network 1300, embodiment as described herein, and all these implementations can also be realized using other equipment, system and configuration Example can be expected within the scope of this disclosure.
As indicated, resource lookup request is sent ownership place RD 1304 by client 1302 1306.Client 1302 Wish to obtain the group for meeting d=" domain1 ".1308, hash function is applied in request (d=by ownership place RD " domain1 ") in the keyword pointed out.It as a result include P1 according to example when application hash function.In the example shown, 1310, search request is sent P1 by ownership place RD 1304.Response associated with the request is returned in 1312, P11 Ownership place RD 1304.1314, response is forwarded to client 1302 by ownership place RD 1304.
Referring now to Figure 14, showing including GET/rd-lookup/gp? the example of ep=" node2 " search request.Figure 14 show the exemplary network 1400 including client 1402, ownership place RD 1404 and peer device 2 (P2).It should be understood that simplifying Exemplary network 1400 in order to published subject description and do not limit the scope of the present disclosure.In addition to or instead of network such as net Network 1400 can also realize embodiment as described herein, and all these embodiments using other equipment, system and configuration It can be expected within the scope of this disclosure.
As indicated, resource lookup request is sent ownership place RD 1404 by client 1402 1406.Client 1402 Wish to obtain group wherein with endpoint (node2).1408, hash function is applied in request (ep=by ownership place RD " node2 ") in the keyword pointed out.It as a result include the P2 as node 2 according to example when application hash function.Shown Example in, 1410, search request is sent P2 by ownership place RD 1404.It is answered in 1412, P1 by associated with the request It answers and returns to ownership place RD 1404.1414, response is forwarded to client 1402 by ownership place RD 1404.
It is being known as referring in the another exemplary embodiment for ensureing (RE) embodiment, reciprocity RD saves the reference of storage RD (reference), rather than storage resource itself.
Referring now to Figure 15, show exemplary network 700, including EP 702 and peer device 1,3,5 and 11 (P1, P3, P5 and P11).As indicated, the example according to shown in, has title 9996172 in 1504, EP 702 and arrives its resource registering P1 as its ownership place RD.Can explain to include link format in payload and determination and the note in 1506, P1 Associated keyword/the parameter of volume is as follows:
Ep=9996172
Lt=41
Rt=" temperature "
Rt=" LightLux "
If=" sensor "
Above-mentioned keyword/parameter may be used as the keyword applied to hash function.When application hash function, according to showing As a result example includes P3, P5 and P11.In addition, the example according to shown in, can choose registration message in 1506, P1 will be forwarded to One (P3, P5 or P11) in three result RD.Registration message is forwarded to selected peer device (P3) in 1508, P1.? 1510, P3 storage payload and it will confirm that and return to P1.Inform that P5 and P11 registration disappears respectively in 1514a and 1514b, P1 Breath is stored at P3.In 1516a and 1516b, in the case where suitably referring to following resource lookup, P5 and P11 store the ground of P3 respectively Location.In 1512, P1 response EP 702, thus meet resource request.
Referring now to Figure 16, show exemplary network 800, including EP 702 and peer device 1,3,5 and 11 (P3, P2, P11 and P6).As indicated, the example according to shown in, in 1604, EP 802 by its resource registering to the P3 as its ownership place RD. Can explain to include link format and determination keyword/ginseng associated with the registration in payload in 1606, P3 Number is as follows:
Ep=9234571
Rt=" temperature "
If=" gateway "
Above-mentioned keyword/parameter may be used as the keyword applied to hash function.When application hash function, according to showing As a result example includes P2, P11 and P6.In addition, the example according to shown in, can choose registration message in 1606, P3 will be forwarded to One (P2, P11 or P6) in three result RD.Registration message is forwarded to selected peer device (P2) in 1608, P3.? 1610, P2 storage payload and it will confirm that and return to P3.Inform that P11 and P6 registration disappears respectively in 1614a and 1614b, P3 Breath is stored at P2.In 1616a and 1616b, under the suitably referring to searched for Future, P11 and P6 store P2 respectively Address.In 1612, P1 response EP 802, thus meet resource request.
Referring now to Figure 17, accoding to exemplary embodiment, proposing " lights " group registration example.As indicated, exemplary web Network 900 includes EP 902, the management node being also discussed further below and peer device 1,3,6 and 2 (P1, P3, P6 and P2). Its ownership place RD (P1) is issued in 1704, EP 902 and is requested.Request indicates optional belonging to the title and the group of the group of creation Domain.Registration message can also include the list for belonging to the endpoint of the group.Can explain to include in payload in 1706, P1 It links format and determination keyword/parameter associated with the registration is:
Gp=lights
Ep=" node1 "
D=" domain1 "
Ep=" node2 "
Above-mentioned keyword/parameter may be used as the input of hash function.When application hash function, according to the example, knot Fruit includes P1, P3, P6 and P2.As indicated, registration storage is arrived itself by P1 1708, such as disappeared with saving used in forwarding registration Network bandwidth in breath.The resource registering for the parameter being responsible for including each peer device can be stored in P1 in 1712a-c, P1 Middle informing P3, P6 and P2.In 1714a-c, under the suitably referring to searched for Future, P3, P6 and P2 can store P1 Address.1710, it is as a result sent to EP 902.
Referring now to Figure 18, accoding to exemplary embodiment, proposing " pressure " group registration example.As indicated, exemplary Network 1800 includes EP 1802 and peer device 1 and 11.It should be understood that simplified example network 1800 is in order to published subject Description and do not limit the scope of the present disclosure.In addition to or instead of network such as network 1800, other equipment, system can also be used Embodiment as described herein is realized with configuration, and all these embodiments can be expected within the scope of this disclosure.
1804, peer device P1 can receive a group registration request.1806, hash function can be arrived a group resource impact Reciprocity RD P11, P1 and P2.Registration storage can be saved into the network being used in forwarding registration message to oneself in 1808, P1 Bandwidth.Resource registering can be stored in P1 in 1810, P1 and inform P11.As indicated, because P2 has been apprised of in the address of P1 (1804) do not need to inform P2 at 1810.1812, under the suitably referring to searched for Future, P11 can be deposited Store up the address of P1.
In the exemplary embodiment, after the distributed resource and group registration described in the examples described above occurs, reciprocity RD can With information shown in storage table 2 (hereafter).
Table 2: the exemplary resources directory content example in exemplary RE embodiment
Search embodiment turning now to resource and group, in a further exemplary embodiment, client can by resource and Group search request is sent to its ownership place RD.Ownership place RD can be determined and be corresponded to by the way that hash function is applied to parameter The responsible equity RD for the parameter specified in request.In one example, only one parameter includes and ownership place RD in the request Responsible RD can be forwarded this request to.Responsible RD can search for rd or rd- based on lookup type specified in the request Group catalogue.Responsible RD can also forward requests to each RD listed in referring to classification.Ownership place RD can be from responsible RD With collect all responses referring to the RD in classification and return result to client.In another exemplary, have multiple Parameter includes in the request and by " AND " Connecting quantity.In this case, ownership place RD can forward requests to each negative Blame one (core is responsible for RD) in RD.Core, which is responsible for RD, can apply in other parameters by hash function and can determine There are other to be responsible for RD.Core is responsible for RD and can forward requests to other being responsible for RD, can also be additionally implemented for referring in classification The request of list.Core, which is responsible for RD, to find out the engagement collection of RD in the reference classification of all responsible RD.Then, core is negative Duty RD can forward this request to the engagement collection of RD.Core is responsible for RD and can collect all responses and return to them to return The response can be returned to client by possession RD, in turn, ownership place RD.
In another exemplary, in the request comprising multiple parameters and by " OR " Connecting quantity.In such case Under, ownership place RD can forward requests to one (core is responsible for RD) in responsible RD.Core, which is responsible for RD, can will hash letter Number is applied to other parameters and can determine that other are responsible for RD.Core be responsible for RD can forward requests to other be responsible for RD, wherein the request referring to the list in classification can be additionally implemented for.Core, which is responsible for RD, can emit the reference of all responsible RD The superset (super set) of RD in classification.Then, core, which is responsible for RD, can forward requests to the superset of RD.It can collect All responses and ownership place RD is returned to, in turn, response is returned to client by ownership place RD.
Referring now to Figure 19, showing including GET/rd-lookup/res? rt=" temperature " AND it=" The example of gateway " search request.Figure 19 shows exemplary network 1900, including client 1902, ownership place RD 1904 And peer device 11,6,1 and 2.It should be understood that simplified example network 1900 is in order to the description of published subject and unlimited The scope of the present disclosure processed.In addition to or instead of network such as network 1900, this can also be realized using other equipment, system and configuration Literary the embodiment described, and all these embodiments can be expected within the scope of this disclosure.
As indicated, resource lookup request is sent ownership place RD 1904 by client 1902 1906.Client 1902 Go for the resource for meeting rt=" temperature " He it=" gateway " simultaneously.1908, ownership place RD 1904 can Responsible RD is obtained so that both keyword is applied to hash function, the example according to shown in is P11 and P6.Ownership place RD 1904, which can choose one of which as core, is responsible for RD.In the example shown, ownership place RD 1904 selects P11 simultaneously And correspondingly forwarding request (1910).As indicated, hash function can be applied to other parameters by P11, and can determine P6 is also responsible for RD.P6 is transmitted the request in 1912, P11, and will include (additional) referring to list request in the request. In this example, if P6 does not find any matching resource, 1914, the address of P2 and P1 are returned into P11.It is true in 1916, P11 Determining P1 and P2 includes engagement collection (at two referring in list).In 1918a and 1918b, then, P11 can turn request respectively It is dealt into P1 and P2.As indicated, the example according to shown in, in 1920a, " will can not look for if P1 does not find any matching resource To " response.The example according to shown in, P2 find matching resource, and are returned to P11 (in 1920b).1922, then, Resource can be returned to ownership place RD 1904 by P11, and in turn, ownership place RD 1904 sends the reply to client 1902 (1924).
Referring now to Figure 20, showing including GET/rd-lookup/res? rt=" LightLux " OR it=" The example of gateway " search request.Figure 20 shows exemplary network 2000, including client 2002, ownership place RD 2004 And peer device 11,6,1,2 and 3.It should be understood that simplified example network 2000 in order to disclosed theme description and It is not intended to be limited to the scope of the present disclosure.In addition to or instead of network such as network 2000, other equipment, system and configuration can also be used Realize embodiment as described herein, and all these embodiments can be expected within the scope of this disclosure.
As indicated, resource lookup request is sent ownership place RD 2004 by client 2002 2006.Client 2002 Go for the resource for meeting rt=" LightLux " or it=" gateway ".2008, ownership place RD 2004 can be by two A keyword is applied to hash function to obtain responsible RD, is P11 and P6 in the example shown.Ownership place RD 2004 can be with Selecting one of which to be responsible for RD as core (is in the example shown P11).Hash function can be applied to it by P11 His parameter, and can determine that P6 is also responsible for RD.Request is occurred in 2012, P11 to arrive P6, and can also be added referring to column Table.2014, if P6 does not find any matching resource, the address of P2 and P1 are returned into P11.2016, according to shown in Example, P11 can determine that P1, P2 and P3 are two supersets referring to list.In 2018a-2018c, then, P11 can will be asked It asks and is forwarded to P1, P2 and P3 respectively.In 2018a, if P1 does not find any matching resource, " not finding " response can be returned. In 2018b and 2018c, P2 and P3 find matching resource, and are returned to P11.P11 can splice all matching resources simultaneously And they are returned into ownership place RD 2004 (2020), in turn, ownership place RD 2004 sends the reply to client 2002 (2022).
Figure 21 shows another exemplary resource lookup example 4 accoding to exemplary embodiment.In this exemplary embodiment, Client 2012 can execute a group lookup.Is client 2012 by GET/rd-lookup/gp 2106? ep=" node2 " request It is sent to ownership place RD 2014.As indicated, client 2012 wishes to obtain group wherein with endpoint (node2).2108, Keyword (ep=" node2 ") can be applied to hash function to obtain corresponding RD by ownership place RD 2014, be shown shown in It is P2 in example.2110, ownership place RD 2014 can forward requests to P2.P2 can be such that P1 is stored in referring in classification. Therefore, P1 can be forwarded requests in 2112, P2.2114, according to shown example, P1 find matching resource and by they Return to P2.Response can be returned to ownership place RD 2014 in 2116, P2, in turn, ownership place RD 2014 sends out response It is sent to client 2012 (2116).
As a result, as described in entire above disclosure, node can determine that with from the received message payload of endpoint Associated one or more keyword.Endpoint can be configured as Web server, M2M equipment or gateway to operate.Node It may include processor, memory and telecommunication circuit.Node can be connected to communication network, and node via its telecommunication circuit It may include the computer executable instructions stored in the memory of node, when being executed by the processor of node, make node Realize various operations.In one example, message payload includes registration request.Node can be by one or more keywords Map information is generated applied to hash function.As described above, map information may include peers LIST SERVER extremely A few mark.Node can be based on map information, and message payload is transmitted to one or more peers catalogues and is taken Business device.Node can receive at least one response from one or more peers LIST SERVERs.At least one response can be with Indicate the position of resource.Meanwhile as described in detail above, at least one received response, node (such as Resource TOC service are based on Device) final response can be transmitted to endpoint.One of multiple keywords associated with message payload may include at least One parameter and at least one value associated at least one parameter.At least one parameter may include domain, endpoint, group name, Endpoint type, resource type, resource longevity phase or interface.In an example as detailed above, at least one parameter is multiple Parameter, and at least one value is multiple values, and hash function is applied to each parameter and value in registration request.In addition, message One or more peers LIST SERVERs that payload is transmitted to can be multiple peers LIST SERVERs, point Not Cun Chu message payload and node how many equity money can be determined based on how many parameter in message payload Source directory server is in the multiple peers LIST SERVER.As an alternative, as described in detail above, message payload quilt One for storing message payload that the one or more peers LIST SERVERs being transmitted to can be selection is right Equal Resource TOCs server, node can will be transmitted to multiple peers catalogues to the reference of the peers catalogue of selection Server, so that the storage of multiple peers catalogues has the reference of the peers catalogue of storage message payload to this.It will Understand that registration request may include the title and resource description of endpoint.
In another example, message payload includes resource lookup request, and associated with message payload One or more keywords include one or more parameters.Resource lookup request may include searching type and one or more ginsengs Number.In one example, if being connected with each other parameter using the first logical connector (such as AND), node is effective by message Load is transmitted to multiple peers LIST SERVERs.Multiple how many parameters that can be based on are in message payload.Another In example, as described in detail above, if being connected with each other parameter using the second logical connector (such as OR), node is by message Payload is transmitted to only one peers LIST SERVER.The one or more that message payload is sent to as a result, Peers LIST SERVER, which can be, travels to other peers catalogues indicated by map information for resource lookup request One peers LIST SERVER of the selection of server.
Figure 22 A is can wherein to realize the example machine of one or more open embodiments to machine (M2M), Internet of Things (IoT) or the figure of all things on earth net (WoT) communication system 10.Generally, M2M technology provides the building module for IoT/WoT, and And any M2M equipment, M2M gateway or M2M service platform can be the component of IoT/WoT and IoT/WoT service layer etc..Fig. 7- Client, terminal, peer device or Resource TOC shown in any one of 21 may include the node of communication system, such as Node shown in Figure 22 A-D.
As shown in FIG. 22 A, M2M/IoT/WoT communication system 10 includes communication network 12.Communication network 12 can be solid Determine network (for example, Ethernet, Fiber, ISDN, PLC etc.) or wireless network (for example, WLAN, honeycomb etc.) or heterogeneous network Network.For example, communication network 12 can be from providing the contents such as voice, data, video, message, broadcast to multiple users Multiple access nets are constituted.For example, one or more channel access methods, such as CDMA can be used in communication network 12 (CDMA), time division multiple acess (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA) etc..This Outside, communication network 12 may include other networks, such as core network, internet, sensor network, industrial control network, a domain Net, fusion personal network, satellite network, home network or enterprise network.
As shown in FIG. 22 A, M2M/IoT/WoT communication system 10 may include infrastructure domain and field domain.Technological facilities domain The network side and field domain for referring to end-to-end M2M deployment are generally referred in the subsequent Local Area Network of M2M gateway.Field domain and basis Facility domain may include multiple and different nodes (for example, server, gateway, equipment) of network.For example, field domain may include M2M Gateway 14 and terminal device 18.It will be appreciated that can on demand include any number of in M2M/IoT/WoT communication system 10 M2M gateway 14 and M2M terminal device 18.Each of M2M gateway 14 and M2M terminal device 18 can be configured to Data are sent and received via communication network 12 or direct radio link.M2M gateway 14 allows wireless M2M equipment (such as cellular and non-cellular) and fixed network M2M equipment (such as PLC) pass through the operator of such as communication network 12 Network is communicated by direct radio link.For example, M2M equipment 18 can be via communication network 12 or direct radio Link come collect data and to M2M using 20 or M2M equipment 18 send data.M2M equipment 18 can also apply 20 or M2M from M2M Equipment 18 receives data.In addition, it is as described below, data and signal can be sent using 20 to M2M via M2M service layer 22, and Receive from it data and signal.M2M equipment 18 and gateway 14 can be communicated via various networks, and the network is for example including honeycomb Formula, WLANWPAN (for example, Zigbee, 6LoWPAN, bluetooth), direct radio link and wired.Exemplary M2M equipment packet Include but be not limited to plate, smart phone, Medical Devices, temperature and weather monitor, the automobile of connection, intelligence instrument, game control Platform, personal digital assistant, health and body-building monitor processed, lamp, thermostat, garage door and other activated apparatus, safety equipment and Intelligent socket.
With reference to Figure 22 B, the shown M2M service layer 22 in field domain is M2M using 20, M2M gateway 14 and M2M terminal Equipment 18 and communication network 12 provide service.It will be appreciated that M2M service layer can apply with any number of M2M on demand, M2M net Equipment 14, M2M terminal device 18 and communication network 12 is closed to communicate.M2M service layer 22 can be by one or more servers, calculating Machine etc. is realized.M2M service layer 22, which provides, is suitable for the service that M2M terminal device 18, M2M gateway 14 and M2M apply 20 Ability.Can realize the function of M2M service layer 22 in many ways, for example, as network server, in cellular core net In network, it is medium in cloud.
M2M service layer 22 shown in being similar to, there are M2M service layer 22' in technological facilities domain.M2M service layer 22' is M2M application 20' and underlying communication network 12' in technological facilities domain provide service.M2M service layer 22' is also the M2M in field domain Gateway 14 and M2M terminal device 18 provide service.It will be appreciated that M2M service layer 22' can be answered with any number of M2M With, M2M gateway and M2M terminal equipment in communication.M2M service layer 22' can pass through different service providers and service layer It interacts.M2M can be realized by one or more servers, computer, virtual machine (for example, cloud/calculating/storage group etc.) etc. Service layer 22'.
Referring still to Figure 22 B, M2M service layer 22 and 22' provide the utilizable one group of core clothes of different application and field Business delivery capability.These service ability enable M2M to interact with equipment using 20 and 20' and execute function, such as data Collection, data analysis, equipment management, safety, charging, service/device discovery etc..Substantially, these service ability, which eliminate, answers With the burden for realizing these functions, therefore simplifies application and development and reduce cost and Time To Market.Service layer 22 and 22' are also Enable M2M using 20 and 20' by with the various networks 12 that are connected of service and 12' of service layer 22 and 22' offer into Row communication.
M2M is using the application that 20 and 20' may include in various industries, such as, but not limited to, transport, health and health care, connection Net family, energy management, assets tracking and safety and monitoring.As described above, across the equipment of this system, gateway and other The M2M service layer of server support such as data collection, equipment management, safety, charging, location tracking/geography fence, equipment/ Integrated etc the function of service discovery and legacy system, and these functions are supplied to M2M as service and apply 20 and 20'.
In general, service layer (SL), service layer 22 shown in such as Figure 22 A and 22B and 22' are defined through one group of application Programming interface (API) and bottom-layer network interface support the software middleware layer of value-added service ability.ETSI M2M and oneM2M Both frameworks both define service layer.The service layer of ETSI M2M is referred to as service capabilities layer (SCL).It can be in ETSI M2M frame SCL is realized in a variety of different nodes of structure.For example, can be in M2M equipment (wherein it is referred to as equipment SCL (DSCL)), net It closes and realizes clothes in (wherein it is referred to as gateway SCL (GSCL)) and/or network node (wherein it is referred to as network SCL (NSCL)) The example of business layer.OneM2M service layer supports one group of public service function (CSF) (i.e. service ability).One of one group of CSF or It is multiple it is certain types of instantiation be referred to as public service entity (CSE), CSE can trustship on different types of network node (such as infrastructure node, intermediate node, specific application node).Third generation partner program (3GPP) also has been defined Framework for Internet of Things Network Communication (MTC).In the architecture, service layer and its service ability provided are taken as service ability A part of business device (SCS) is implemented.No matter it is embodied in DSCL, GSCL or NSCL of ETSI M2M framework, is embodied in In the service capability server (SCS) of 3GPPMTC framework, it is embodied in the CSF or CSE of oneM2M framework and is still embodied in network Some other node in, the example of service layer can include with one or more of network server, computer and other Calculate the logic entity (such as software, computer executable instructions etc.) executed on the isolated node of equipment or node or conduct A part of one or more existing nodes is implemented.As an example, can with it is described below in Figure 22 C or It is run on the network node (such as server, computer, gateway, equipment or similar) of the generic structure illustrated in Figure 22 D The form of software realizes service layer or the example of its component (such as AS/SCS 100).
In addition, methods and functions described herein can be implemented as using Service-Oriented Architecture Based (SOA) and/or towards money A part of the M2M network of source framework (ROA), to access service, such as above-mentioned network and application management service.
Figure 22 C is example hardware/software architecture block diagram of the node of network, client shown in such as Fig. 7-21 End, terminal, peer device or Resource TOC may be operative to the M2M service in M2M network shown in such as Figure 22 A and 22B Device, gateway, equipment or other nodes.As shown in Figure 22 C, node 30 may include processor 32, transceiver 34, send/connect Receive element 36, speaker/microphone 38, keypad 40, display/touch tablet 42, non-removable memory 44, removable Storage Device 46, power supply 48, global positioning system (GPS) chipset 50 and other peripheral equipments 52.Node 30 can also include communication electricity Road, such as transceiver 34 and transmission/receiving element 36.It should be understood that node 30 may include any sub-portfolio of aforementioned components and It is still consistent with embodiment.The node, which can be, realizes the functional node of Resource TOC as described herein.
Processor 32 can be general processor, application specific processor, conventional processors, digital signal processor (DSP), more A microprocessor, one or more microprocessors associated with DSP core, controller, microcontroller, specific integrated circuit (ASIC), field programmable gate array (FPGA) circuit, the integrated circuit (IC) of any other type, state machine etc..Processor 32 executable Signal codings, power supply control, input/output processing and/or enable node 30 in wireless environment at data processing Any other function of middle operation.Processor 32 can be coupled to transceiver 34, and transceiver 34 can be coupled to transmission/reception member Part 36.Although processor 32 and transceiver 34 are portrayed as independent assembly by Figure 22 C, it will be appreciated that can be by 32 He of processor Transceiver 34 is integrated in together in Electronic Packaging or chip.Processor 32 can be performed application layer program (for example, browser) and/or Radio access layer (RAN) program and/or communication.Safety operation can be performed in processor 32, such as in access layer and/or answers With certification, security key agreement and/or the Password Operations on layer.
As shown in fig. 22 c, processor 32 is coupled to its telecommunication circuit (such as transceiver 34 and transmission/receiving element 36).Processor 32 can control the telecommunication circuit by executing computer executable instructions, to promote node 30 via its company The network being connected to is communicated with other nodes.Specifically, processor 32 can control the telecommunication circuit, to execute in (example herein Step is sent and received described in such as Fig. 7-21) and in the claims.Although Figure 22 C describes processor 32 and transceiver 34 For isolated component, it will be appreciated that processor 32 and transceiver 34 can be integrated in together in Electronic Packaging or chip.
Transmission/receiving element 36 can be configured to send signal to other nodes, including M2M server, gateway, equipment etc. Or receive from it signal.For example, in embodiment, transmission/receiving element 36 can be arranged to send and/or receive RF letter Number antenna.Transmission/receiving element 36 can support various networks and air interface, WLAN, WPAN, honeycomb etc..Implementing In example, transmission/receiving element 36 can be arranged to send and/or receive transmitter/detection of IR, UV or visible light signal Device.In another embodiment, transmission/receiving element 36 can be configured to send and receive both RF and optical signal.It will be recognized Be any combination that transmission/receiving element 36 can be configured to send and/or receive wirelessly or non-wirelessly signal.
In addition, though transmission/receiving element 36 is portrayed as discrete component in Figure 22 C, but node 30 may include any Transmission/receiving element 36 of number.More specifically, MIMO technology can be used in node 30.Therefore, in embodiment, node 30 can Including two or more transmission/receiving elements 36 (for example, mutiple antennas) for sending and receiving wireless signal.
Transceiver 34 can be configured to be modulated to by the signal sent by transmission/receiving element 36, and to by sending out Give/signal that receives of receiving element 36 demodulated.As described above, node 30 can have multi-mode ability.Thus, for example receiving Hair device 34 may include multiple for enabling node 30 to be communicated via multiple RAT of such as UTRA and IEEE802.11 Transceiver.
Processor 32 can suitably be deposited from any kind of of such as non-removable memory 44 and/or removable memory 46 Reservoir access information and wherein storing data.Non-removable memory 44 may include random access memory (RAM), read-only deposit The memory storage device of reservoir (ROM), hard disk or any other type.Removable memory 46 may include subscriber identity module (SIM) card, memory stick, secure digital (SD) storage card etc..In other embodiments, processor 32 can be from such as server or family With physically the memory access information storage on node 30 and wherein storing data of computer.Processor 32 Control display or lamp light mode, image or color on indicator 42 be can be configured to reflect UE (for example, see GUI 1400) state, especially with the basic network of UE communication, using or other service.Processor 32 can be received from power supply 38 Electric power, and can be configured to the distribution of other components into node 30 and/or control power.Power supply 48 can be for section Any appropriate equipment of 30 power supply of point.For example, power supply 48 may include one or more dry cells (for example, ni-Cd (NiCd), nickel zinc (NiZn), nickel metal hydride (NiMH), lithium ion (Li ion) etc.), solar battery, fuel cell etc..
Processor 32 can also be coupled to GPS chip group 50, be configured to provide the current location about node 30 Location information (such as longitude and latitude).It should be understood that node 30 can obtain position letter by any location determining method appropriate It ceases still consistent with embodiment.
Processor 32 can further be coupled to other peripheral hardwares 52, may include providing supplementary features, function and/or wired Or one or more software and/or hardware modules of wireless connectivity.For example, peripheral hardware 52 may include accelerometer, electronic guide Needle, satellite transceiver, sensor, digital camera (for photo or video), the port universal serial bus (USB), vibration Equipment, television transceiver, Earphone with microphone, module, frequency modulation (FM) radio unit, digital music player, media player, view Frequency game player module, Internet-browser etc..
Figure 22 D is the block diagram of exemplary computing system 90, which can be used to realize one or more of network A node, client, peer device and Resource TOC shown in such as Fig. 7-21, may be operative in such as Figure 22 A and 22B Shown in M2M server, gateway, equipment or other nodes in M2M network.Computing system 90 may include computer or service Device, and can mainly by that can be controlled using software as the computer-readable instruction of form, no matter where or pass through which kind of hand Section stores or accesses such software.Such computer-readable instruction can be performed to promote in central processing unit (CPU) 91 Computing system 90 is set to work.In many known work stations, server and personal computer, central processing unit 91 It is realized by being referred to as the one-chip CPU of microprocessor.In other machines, central processing unit 91 may include multiple processors. Coprocessor 81 is the optional processor different from host CPU 91, executes additional function or assists CPU91.CPU91 and/or association Processor 81 can receive, generate and handle data related with the E2EM2M service open system and method for layer conversation are used for, It such as receives session certificate and is authenticated based on the session certificate.
In operation, CPU91 is obtained, is decoded and execute instruction, and via the master data transfer path of computer, system Bus 80 transmits information to its source and transmits information from other sources.Component in such system bus connection computing system 90, And define the medium for being used for data exchange.System bus 80 generally includes data line for sending data, for sending address Address wire and for send interrupt and be used for operating system bus control line.The example of such system bus 80 is PCI (peripheral component interconnection) bus.
The memory devices for being coupled to system bus 80 include random access memory (RAM) 82 and read-only memory (ROM)93.Such memory includes the circuit for allowing to store and retrieve information.ROM93 is generally comprised cannot be light easily modified Storing data.The data being stored in RAM82 can be read or be changed by CPU91 or other hardware devices.To RAM82 and/or The access of ROM93 can be controlled by Memory Controller 92.Memory Controller 92 can provide when executing an instruction will virtually Location is converted into the address translation feature of physical address.Memory Controller 92 can also be provided the process isolation in system and will be The memory protection function that system process and consumer process are isolated.Therefore, the program run in the flrst mode only may have access to by The memory of the virtual address space mapping of its own processor;In its virtual address space that cannot access another processor Memory, unless having been set up the Memory Sharing between processor.
In addition, computing system 90 may include peripheral controls 83, it is responsible for the command communication of CPU91 to such as beating Print machine 94, keyboard 84, mouse 95 and disc driver 85 peripheral equipment.
The display 86 controlled by display controller 96 is used to show the visual output generated by computing system 90.This Class visual output may include text, figure, animated graphics and video.The video display based on CRT can be used, be based on The flat-panel monitor of LCD realizes display 86 based on the flat-panel monitor of gaseous plasma or touch screen.Display control Device 96 includes electronic building brick needed for generation is sent to the vision signal of display 86.
In addition, computing system 90 may include telecommunication circuit, such as network adapter 97, can be used to that system will be calculated System 90 is connected to the external communication network of the network 12 of such as Figure 22 A and Figure 22 B, so that computing system 90 can be with the network Other nodes communication.Telecommunication circuit individually or combines CPU 91, can be used to execute this paper (such as Fig. 7-21) and right is wanted Step is sent and received described in asking.
It will be appreciated that can be with the computer executable instructions that are stored on computer readable storage medium (that is, program generation Code) form come embody method described herein and process any one, and when by such as computer, server, M2M When the machine executable instructions such as terminal device, M2M gateway, the instruction execution and/or realize system as described herein, method and Process.Specifically, it can be realized in the form of such computer executable instructions in step described above, operation or function It is any.Computer readable storage medium includes the volatibility realized with any method or technique for storing for information and non-volatile Property, both removable and irremovable media, but such computer readable storage medium does not include signal.It is computer-readable to deposit Storage media includes but is not limited to RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storages, cassette, tape, magnetic disk storage or other magnetic storage apparatus or storage period can be used to The other physical mediums hoping information and being accessed by computer.
When describing the preferred embodiment of theme of the disclosure, as shown in the figure, specific art is used for the sake of being illustrated Language.It is, however, required that the theme of protection is not intended to be limited to the specific term selected in this way, and it should be understood that each specific member Part includes all technical equivalents operated in a similar manner to realize similar purpose.
Here is the list of initialism related with the service level technology in the foregoing description of being likely to occur.Unless otherwise Illustrate, initialism used herein refers to following corresponding term:
CoAP constrains application protocol
CoRE constrains RESTful environment
DHT distributed hash table
DRD distributive resources list
EP endpoint
HTTP hypertext transfer protocol
IETF Internet Engineering Task group
IoT Internet of Things
M2M Machine To Machine
MAC medium access control
RD Resource TOC
RE is referring to security mechanism
SA stores auxiliary mechanism
URI uniform resource identifier
This written description uses examples to disclose the present invention, including optimal mode, and also makes those skilled in the art Member can practice the present invention, the method including manufacturing and using any equipment or system and executing any combination.Of the invention Patentable range is defined by the claims, and may include the other examples that those skilled in the art expects.Such as Other such examples of fruit have the structural detail of the literal language different from claim, or if other such examples include Literal language with claim is without the equivalent structural elements of substantive difference, then such other examples intention falls into claim In the range of.

Claims (9)

1. a kind of node including processor, memory and telecommunication circuit, the node are connected to communication via its telecommunication circuit Network, the node further comprises the computer executable instructions stored in the memory of the node, when by the section When the processor of point executes described instruction, make the node:
Determine that one or more keywords associated with message payload, the message payload are received from endpoint , the message payload include it is no instruction resource uniform resource identifier (URI) in the case where with the resource Associated resource lookup request;
One or more of keywords are applied to hash function to generate map information, the map information includes equity money At least one mark of source directory server;
Based on the map information, the message payload is transmitted to one or more peers LIST SERVERs;
At least one response is received from one or more of peers LIST SERVERs, at least one response instruction exists The content of the resource stored on one or more of peers LIST SERVERs;And
Based at least one received response, final response is transmitted to the endpoint, so as to the URI's of no resource In the case of retrieve the content of the resource,
Wherein, one of multiple keywords associated with the message payload include one or more parameters.
2. node as described in claim 1, wherein one or more of parameter instructions field, endpoint, group name, endpoint type, Resource type, resource longevity phase or interface.
3. node as described in claim 1, wherein the resource lookup request includes searching type and one or more ginsengs Number.
4. node as described in claim 1, wherein one or more of parameters are multiple parameters, and wherein, the meter Calculation machine executable instruction further makes node:
If being connected with each other the parameter using the first logical connector, the message payload is transmitted to multiple equities Resource TOC server, the multiple is to be based on how many parameter in the message payload;And
If being connected with each other the parameter using the second logical connector, the message payload is transmitted to only one pair Equal Resource TOCs server.
5. node as described in claim 1, wherein one or more of equities that the message payload is sent to Resource TOC server is a peers LIST SERVER of selection, and the peers LIST SERVER of the selection will be described Resource lookup request travels to the other peers LIST SERVER indicated by the map information.
6. node as described in claim 1, wherein the endpoint is configured to as Web server, machine-to-machine equipment Or gateway operates.
7. a kind of method, comprising:
One or more keywords associated with message payload are determined by Resource TOC server, the message effectively carries Lotus be it is received from endpoint, the message payload include it is no instruction resource uniform resource identifier (URI) feelings Resource lookup request associated with the resource under condition;
One or more of keywords are applied to hash function to generate map information, the map information includes equity money At least one mark of source directory server;
Based on the map information, the message payload is transmitted to one or more peers LIST SERVERs;
At the Resource TOC server, at least one from one or more of peers LIST SERVERs is received Response, at least one described response indicate in the resource stored on one or more of peers LIST SERVERs Hold;And
Based at least one received response, final response is transmitted to the endpoint, so as to the URI's of no resource In the case of retrieve the content of the resource,
Wherein, one of multiple keywords associated with the message payload include at least one parameter or with it is described extremely Few at least one associated value of a parameter.
8. the method for claim 7, wherein described at least one parameter instructions field, endpoint, group name, endpoint type, money Source Type, resource longevity phase or interface.
9. the method for claim 7, wherein the resource lookup request includes searching type and one or more ginsengs Number.
CN201580013351.9A 2014-03-11 2015-03-11 Enhance distributive resources list Expired - Fee Related CN106134159B (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US201461951141P 2014-03-11 2014-03-11
US61/951,141 2014-03-11
PCT/US2015/019942 WO2015138596A1 (en) 2014-03-11 2015-03-11 Enhanced distributed resource directory

Publications (2)

Publication Number Publication Date
CN106134159A CN106134159A (en) 2016-11-16
CN106134159B true CN106134159B (en) 2019-09-20

Family

ID=52991939

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201580013351.9A Expired - Fee Related CN106134159B (en) 2014-03-11 2015-03-11 Enhance distributive resources list

Country Status (6)

Country Link
US (1) US20150264134A1 (en)
EP (1) EP3117587B1 (en)
JP (1) JP6397044B2 (en)
KR (1) KR101972932B1 (en)
CN (1) CN106134159B (en)
WO (1) WO2015138596A1 (en)

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11051149B2 (en) * 2014-09-25 2021-06-29 Telefonaktiebolaget Lm Ericsson (Publ) Device mobility with CoAP
US9661080B2 (en) 2014-10-21 2017-05-23 Helium Systems, Inc. Systems and methods for smart device networking with an endpoint and a bridge
JP6511535B2 (en) * 2015-03-02 2019-05-15 コンヴィーダ ワイヤレス, エルエルシー Network and application management using service layer capabilities
US10069938B1 (en) * 2015-03-30 2018-09-04 EMC IP Holding Company LLC Returning identifiers in default query responses
US20180302290A1 (en) * 2015-10-16 2018-10-18 Convida Wireless, Llc Coap enhancements to enable an autonomic control plane
US20170126542A1 (en) * 2015-10-28 2017-05-04 Futurewei Technologies, Inc. ICN Based Distributed Resource Directory for IoT Resource Discovery and Routing
KR101792399B1 (en) 2016-03-21 2017-11-01 전자부품연구원 Method and System for Retrieving IoT/M2M Resource
CN107872486B (en) * 2016-09-28 2020-06-02 华为技术有限公司 Communication method and device
US10664278B2 (en) 2017-08-17 2020-05-26 Huawei Technologies Co., Ltd. Method and apparatus for hardware acceleration in heterogeneous distributed computing
US11432127B2 (en) * 2017-10-20 2022-08-30 Telefonaktiebolaget Lm Ericsson (Publ) Methods of providing and obtaining access to IoT resources
KR102035905B1 (en) * 2017-11-29 2019-10-24 전자부품연구원 Method for Mapping Device Data to Server Resource in IoT Environment and Gateway applying the same
US10499189B2 (en) 2017-12-14 2019-12-03 Cisco Technology, Inc. Communication of data relating to endpoint devices
US11381947B2 (en) * 2018-04-06 2022-07-05 Telefonaktiebolaget Lm Ericsson (Publ) Thing description to resource directory mapping
CN109446439B (en) * 2018-09-30 2022-09-06 青岛海尔科技有限公司 Resource directory selection method, device, system and storage medium
WO2020093318A1 (en) * 2018-11-08 2020-05-14 Oppo广东移动通信有限公司 Resource query processing method and apparatus, and computer device and storage medium
CN115334146A (en) * 2018-12-11 2022-11-11 Oppo广东移动通信有限公司 Resource publishing method, device, equipment and storage medium of Internet of things
US11363104B2 (en) 2018-12-18 2022-06-14 Hewlett Packard Enterprise Development Lp Subscription based directory services for IOT devices
GB2582737B (en) * 2019-02-01 2021-07-14 Arm Ip Ltd Device registration mechanism

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102667776A (en) * 2009-10-27 2012-09-12 莱克萨利德股份公司 Method and system for processing information of a stream of information

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6898633B1 (en) * 2000-10-04 2005-05-24 Microsoft Corporation Selecting a server to service client requests
JP2005151244A (en) * 2003-11-17 2005-06-09 Ntt Docomo Inc Content storage support system
US8880664B1 (en) * 2004-07-26 2014-11-04 Cisco Technology, Inc. Method and apparatus for generating a network profile and device profile
US7774380B2 (en) * 2007-12-21 2010-08-10 International Business Machines Corporation Technique for finding rest resources using an n-ary tree structure navigated using a collision free progressive hash
US20100235469A1 (en) * 2009-03-11 2010-09-16 Morris Robert P Method And System For Providing Access To Resources Related To A Locatable Resource
WO2011137189A1 (en) * 2010-04-27 2011-11-03 Cornell Research Foundation System and methods for mapping and searching objects in multidimensional space
JP5684671B2 (en) * 2011-08-05 2015-03-18 日本電信電話株式会社 Condition retrieval data storage method, condition retrieval database cluster system, dispatcher, and program
FI125252B (en) * 2011-12-07 2015-08-14 Arm Finland Oy A method, device, and system for managing a web service
WO2013123445A1 (en) * 2012-02-17 2013-08-22 Interdigital Patent Holdings, Inc. Smart internet of things services
US8635373B1 (en) * 2012-09-22 2014-01-21 Nest Labs, Inc. Subscription-Notification mechanisms for synchronization of distributed states

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102667776A (en) * 2009-10-27 2012-09-12 莱克萨利德股份公司 Method and system for processing information of a stream of information

Also Published As

Publication number Publication date
JP6397044B2 (en) 2018-09-26
EP3117587A1 (en) 2017-01-18
KR101972932B1 (en) 2019-04-29
JP2017517046A (en) 2017-06-22
WO2015138596A1 (en) 2015-09-17
US20150264134A1 (en) 2015-09-17
EP3117587B1 (en) 2020-11-11
CN106134159A (en) 2016-11-16
KR20160130483A (en) 2016-11-11

Similar Documents

Publication Publication Date Title
CN106134159B (en) Enhance distributive resources list
US10404601B2 (en) Load balancing in the internet of things
CN106797409B (en) Server for device location registration in internet of things (IOT)
KR102046700B1 (en) Message bus service directory
CN106797392B (en) Publication and discovery of M2M-IOT services
EP2721787B1 (en) Principal-identity-domain based naming scheme for information centric networks
EP2994831B1 (en) Method and apparatus for the virtualization of resources using a virtualization broker and context information
US10979879B2 (en) Mechanisms for resource-directory to resource-directory communications
US10798779B2 (en) Enhanced CoAP group communications with selective responses
Ganz et al. Context-aware management for sensor networks
KR20160146978A (en) Search engine optimization for resource directory
Ahmed et al. Resource and service discovery in large-scale multi-domain networks
CN109478153A (en) Message in the communication of machine to machine service layer redirects
Li et al. Supporting efficient machine-to-machine communications in the future mobile internet
Rodrigues et al. Zigzag: A middleware for service discovery in future internet
Mihailovic Liberalising deployment of internet of things devices and services in large scale environments
WO2018132557A1 (en) Dynamic protocol switching
Rodrigues Data Storage Solutions for the Federation of Sensor Networks
Zhu et al. Service Discovery Architecture and Protocol Design for Pervasive Computing
Kemerlis et al. A Review in Efficient Mobile Object Tracking Techniques
McMahon Discovery of Delay-Tolerant Networking Endpoint Elements
Chen et al. Naming and Discovery in Mobile Systems
Flathagen et al. Web services and service discovery
Flathagen et al. Interoperable service discovery: experiments at Combined Endeavor 2009

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant
CF01 Termination of patent right due to non-payment of annual fee
CF01 Termination of patent right due to non-payment of annual fee

Granted publication date: 20190920