WO2012167659A1 - Procédé et dispositif de communication de données dans un protocole d'applications contraintes - Google Patents

Procédé et dispositif de communication de données dans un protocole d'applications contraintes Download PDF

Info

Publication number
WO2012167659A1
WO2012167659A1 PCT/CN2012/073539 CN2012073539W WO2012167659A1 WO 2012167659 A1 WO2012167659 A1 WO 2012167659A1 CN 2012073539 W CN2012073539 W CN 2012073539W WO 2012167659 A1 WO2012167659 A1 WO 2012167659A1
Authority
WO
WIPO (PCT)
Prior art keywords
option information
request
via option
proxy node
response
Prior art date
Application number
PCT/CN2012/073539
Other languages
English (en)
Chinese (zh)
Inventor
陈显锋
卞永刚
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2012167659A1 publication Critical patent/WO2012167659A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network

Definitions

  • CoAP Constrained Application Protocol
  • M2M machine to machine
  • the functions of these machines are relatively simple.
  • the general processor has only 8 bits, the storage space is small, the complex transmission protocol is not supported, and the data transmission rate is also low.
  • CoAP provides a request/response interaction model that supports embedded resource discovery, including key web page concepts such as the Unique Resources Identifier (URI) and content type.
  • URI Unique Resources Identifier
  • CoAP nodes can be used as a proxy node. Agent functions are always supported on nodes between subnets and associated nodes on restricted networks and external networks.
  • the CoAP supports subscription. If the subscription request initiated by the terminal passes through the proxy node, the proxy node needs to save the state relationship between the session between the terminal and the proxy node and the session with the proxy node. During the subscription process, the proxy node needs to record the address of the terminal, the token option information between the terminal and the proxy node, the address of the server, the token option information between the proxy node and the server.
  • the proxy node needs to process the session state and record session related data, and the proxy node usually serves many CoAP terminals and servers, the proxy nodes are different.
  • the proxy node that stores multiple session states and records session-related data is processed faster than the proxy node that stores a session state and records session-related data, so the former can handle the same time period.
  • the number of subscriptions is less than the latter.
  • the server storage capacity increases.
  • the performance of the server as a proxy node is limited.
  • the increase in the storage capacity reduces the number of subscriptions that can be simultaneously stored. , causing communication delay or failure to send.
  • An aspect of the present invention provides a method for data communication in a restricted application protocol CoAP, the method comprising: receiving a request sent by a terminal; and performing the request according to whether a proxy node stores a parameter and a state of a session corresponding to the request.
  • the path records the processing of the Via option information, wherein the Via option information is used to record the request path and the response route; the processed request is sent.
  • Another aspect of the present invention provides a method for data communication in a restricted application protocol CoAP, the method comprising: generating a request carrying Via option information, and the Via option information is used to record a request path and a response. Routing; sending a request to the proxy node to facilitate processing of the Via option information for the request based on whether the proxy node will store the parameters and status of the session corresponding to the request; and receiving a response based on the request sent by the proxy node.
  • a method for data communication in a restricted application protocol CoAP comprising: receiving a request sent by a proxy node from a terminal; generating a response carrying Via option information based on the request, where the Via option The information is used to record the request path and the response route; send a response to the proxy node, so that the proxy node processes the Via option information according to whether the proxy node has stored the parameter and state of the session corresponding to the request, and sends the response to the terminal. The processed response.
  • An aspect of the present invention provides an apparatus for restricted application protocol CoAP data communication, the apparatus comprising: a receiving module, configured to receive a request sent by a terminal, and a processing module, configured to: according to whether the device will store the request corresponding to the session Parameter and status, processing the request path Via option information, wherein the Via option information is used to record the request path and the response route; and the sending module is configured to send the processed request.
  • a server for data communication in a restricted application protocol CoAP comprising: a receiving module, configured to receive a request sent by a proxy node from a terminal; and a generating module, configured to generate, according to the request a response carrying the Via option information, wherein the Via option information is used to record the request path and the response route; and the sending module is configured to send a response to the proxy node, so that the proxy node stores the parameter of the session corresponding to the request according to whether the proxy node has stored the request And the status, the response of the Via option information is processed, and the processed response is sent to the terminal.
  • FIG. 4 is a schematic diagram of an example of data communication in a restricted application protocol CoAP in accordance with another embodiment of the present invention.
  • FIG. 7 is a schematic diagram of an example of data communication in a restricted application protocol CoAP in accordance with an embodiment of the present invention.
  • 8 is a flow diagram of another method of data communication in a restricted application protocol CoAP in accordance with an embodiment of the present invention.
  • FIG. 9 is a flow diagram of yet another method of data communication in a restricted application protocol CoAP in accordance with an embodiment of the present invention.
  • FIG. 10 is a block diagram of an apparatus for data communication in a restricted application protocol CoAP, in accordance with an embodiment of the present invention.
  • Figure 11 is a block diagram of an apparatus for data communication in a restricted application protocol CoAP in accordance with another embodiment of the present invention.
  • FIG. 12 is a block diagram of a terminal for data communication in a restricted application protocol CoAP, in accordance with an embodiment of the present invention.
  • 13 is a block diagram of a server for data communication in a restricted application protocol CoAP, in accordance with an embodiment of the present invention.
  • FIG. 1 is a flow diagram of a method 100 of data communication in a restricted application protocol CoAP, in accordance with an embodiment of the present invention.
  • the request sent by the terminal may be a request directly from the terminal, or may be a request sent by the terminal sent by the other proxy node. Specifically, the proxy node can directly receive the request sent by the terminal, or can receive the request sent by the terminal from another proxy node.
  • the embodiment of the present invention allows the proxy node to be divided into a stateless proxy node and a stateful proxy node according to whether the proxy node stores the parameters and state of the session corresponding to the current request in the CoAP, and may exist simultaneously on the transmission path of the same session.
  • a session includes requests and responses.
  • the proxy node that stores the parameters and status of the session and the proxy node that stores the parameters and status of the session when processing the response of one session are referred to as stateful agents in the session.
  • the proxy node judges that it will act as a stateful proxy node or a stateless proxy node can be judged by the following method. For example, setting an identifier in a configuration file of the proxy node, the proxy node determining to act as a stateful proxy node or a stateless proxy node by identifying the identifier, and the identifier may be changed by manual configuration, so that the proxy node changes the role; The size of the allocated memory space is determined.
  • the proxy node will act as a stateful proxy, and vice versa as a stateless proxy; how the proxy node determines that it acts as a stateful proxy or a stateless proxy is not
  • the problem solved by the invention is merely exemplified herein.
  • the proxy node When in the session, the proxy node does not store the parameters and status of the session corresponding to the request when processing the request, or when the proxy node processes the response, the proxy node does not store the request corresponding to the response.
  • Session parameter or state ie this proxy node is a stateless proxy node.
  • the stateless proxy node adds Via option information to the request to send a request to the server.
  • the proxy node When in the session, the proxy node will store the parameters and status of the session corresponding to the request when processing the request; or when the proxy node processes the response, the proxy node has stored the request corresponding to the response Session parameter or state, ie this proxy node is a stateful proxy node.
  • the stateful proxy node stores the Via option information in the request and deletes the Via option information in the request.
  • the Via option is used to record the request path and response route.
  • the assignment carried by the Via option is called Via option information.
  • the Via option is defined by the Type Length Value (TLV, Type Length Value) field as shown in Table 1 below.
  • the Via option information as a string can be the address of the Proxy through which the request passes, and can be a URI, an IP address, or a unique device number.
  • the Via option information is routable, that is, according to the assignment and The corresponding device implements communication, and it is known from the above that there is no default value for the Via option.
  • C/E It is one of the attributes of the Via option.
  • C means that the node on the CoAP path must understand the option and handle it accordingly.
  • E means that the node on the CoAP path can not understand the option and does not handle it accordingly.
  • the Via option information when the Via option information includes multiple address information, the Via option information can be implemented in the following two ways.
  • the embodiment of the present invention takes the second implementation as an example, and the newly added address information is sequentially placed on the above.
  • the uppermost address information is referred to as first Via option information
  • the lowermost address information is referred to as second Via option information.
  • the stateless proxy node adds Via option information carrying the address of the proxy node to the request.
  • the stateful proxy node and the stateless proxy node are allowed to exist simultaneously on the transmission path of the same session, and the routing information of the path in the protocol packet is extracted and deleted by the stateful proxy node, and then changed.
  • the routing information of the local storage path is such that the load of the requested Via option information is as small as possible, and the routing information carried in the protocol packet is shortened, thereby improving the efficiency of using the proxy node resource, thereby reducing the consumption of the transmission and reducing the transmission.
  • step 350 is directly executed.
  • the routing information of the path in the protocol packet is deleted by the stateful proxy node, and the routing information of the path in the protocol packet is deleted, and the routing information carried in the protocol packet is shortened. This improves the efficiency of proxy node resource usage and reduces communication delays or interruptions caused by busy or faulty proxy nodes.
  • the terminal or proxy node no longer adds its own address to the Via option information, which is added by the proxy node of the next hop of the path, thereby further reducing the consumption of the transmission resources of the proxy node.
  • a hop in the path is taken as an example.
  • the path can have multiple hops, where the proxy nodes are stateless proxy nodes or stateful proxy nodes, respectively.
  • Adjacent proxy nodes in a multi-hop path may be consecutive stateless proxy nodes, or may be consecutive stateful proxy nodes, or they may alternate. This embodiment of the present invention is not limited thereto.
  • the addresses used by the Via option information of the stateless proxy node and the stateful proxy node are uniform. That is, when the stateless proxy node uses the requested source address as the added Via option information, the stateful proxy node adds the requested source address to the stored Via option information, as shown in example 300. Or when the stateless proxy node uses the address of the proxy node as the Via option information, the stateful proxy node uses the address of the proxy node as the Via option information after deleting the Via option information in the request, as shown in example 200. vice versa.
  • FIG. 4 is a schematic diagram of an example 400 of data communication in a restricted application protocol CoAP, in accordance with another embodiment of the present invention.
  • the proxy node receiving the response can be a stateless proxy node or a stateful proxy node.
  • the response includes information such as token option information, and/or terminal information.
  • the stateful proxy node and the stateless proxy node are allowed to exist simultaneously on the transmission path of the same session, and the routing information of the path in the protocol packet is extracted and deleted by the stateful proxy node, and then changed.
  • the routing information of the local storage path shortens the routing information carried in the protocol packets, thereby improving the efficiency of using the proxy node resources.
  • FIG. 5 is a schematic diagram of an example 500 of data communication in a restricted application protocol CoAP, in accordance with another embodiment of the present invention.
  • FIG. 5 illustrates another embodiment implementation.
  • the server or proxy node Before sending a response, the server or proxy node first sends the top Via option information in the message (the first Via option information). )delete.
  • the proxy node receiving the response can be a stateless proxy node or a stateful proxy node.
  • the proxy node that deletes the top Via option information (first Via option information) in the response may be a stateless proxy node or a stateful proxy node.
  • the proxy node deletes the stored session parameters after the session ends, including the Via option information.
  • the end of the session represents the end of the subscription, and the method for determining the end of the subscription may be to add a validity period to the subscription, or be displayed by the subscriber. End the subscription by answering.
  • the stateful proxy node and the stateless proxy node are allowed to exist simultaneously on the transmission path of the same session, and the routing information of the path in the protocol packet is extracted and deleted by the stateful proxy node, and then changed.
  • the routing information of the local storage path shortens the routing information carried in the protocol packets, thereby improving the efficiency of using the proxy node resources and reducing communication delays or interruptions caused by busy or faulty proxy nodes.
  • the server or proxy node no no longer adds its own address to the Via option information, which is joined by the proxy node at the next hop of the path.
  • the embodiment of Figure 6 is another alternative to the stateful proxy node implementation of the embodiment of Figures 4 and 5.
  • the server or stateful proxy node When the server or stateful proxy node returns a response to the client, it will try to skip the stateless proxy node. Only when the skip fails will the proxy node passing the request be returned in the original path.
  • an attempt flag indicating an attempt is added, with a bit of 1 indicating that the stateless proxy node has been attempted to be skipped, and a 0 indicating that it is attempting to skip the stateless proxy node, where the attempt to identify the bit is attempted.
  • the method is merely an example and may be expressed in any other way.
  • FIG. 6 is a schematic diagram of an example 600 of data communication in a restricted application protocol CoAP, in accordance with another embodiment of the present invention.
  • the response may be sent successfully by an acknowledgment (ACK) response to the acknowledgment request CON;
  • ACK acknowledgment response to the acknowledgment request CON;
  • the use of the attempt flag in the above embodiment is merely an example of an attempt to skip the implementation of the stateless proxy node, and the present invention is not limited thereto.
  • Other implementations may, for example, send a response directly to the device corresponding to the lowest one (second Via option information) in the response by determining that there are multiple Via option information.
  • Fig. 6 The embodiment in Fig. 6 can be applied in the following scenario example. Assume that the proxy node through which the request passes and the session state information stored by each proxy node for the request are:
  • the server When the server processes the return response, it tries to skip the stateless proxy node ProxyE and tries to send the response directly to the ProxyD. Only when the direct transmission fails, it will be sent to the ProxyE, and the ProxyE will forward the response to the ProxyD. The ProxyD also tries to skip the stateless proxy.
  • the node ProxyC directly attempts to send a response to the ProxyB, and only forwards it via the ProxyC when the response is unsuccessful.
  • the stateful proxy node and the stateless proxy node are allowed to exist simultaneously on the transmission path of the same session, and the routing information of the path in the protocol packet is extracted and deleted by the stateful proxy node, and then changed.
  • the routing information of the local storage path is shortened in the protocol packet. The routing information carried, thereby improving the efficiency of the use of the proxy node resources, and reducing the communication delay or interruption caused by the busy or faulty proxy node.
  • FIG. 7 is a schematic diagram of an example of data communication in a restricted application protocol CoAP in accordance with an embodiment of the present invention.
  • ProxyA is a stateless proxy node
  • ProxyB is a stateful proxy node
  • the addresses of Client, ProxyA, ProxyB, and Server are respectively:
  • the URI of the client is: coap: ⁇ clientsensor.example/clientl
  • the communication address is: 192.0.2.2
  • the communication address of ProxyA is: 192.0.2.1
  • ProxyB's mailing address is: 192.1.2.1
  • the URI of the server is: coap ://server. sensor. example/Server 1
  • the ProxyA does not store the parameter and the status of the requested session. It adds the Via option information carrying the address to the request, and places it on the Via option information of the terminal:
  • ProxyB is a stateful proxy node, which first stores the Via option information in the request locally, and then deletes the requested Via option information in step 703 in the request, and adds its own address as the new Via option information:
  • step 706-710 sending a response of the server based on the request of step 701 to the terminal.
  • the server sends an asynchronous notification message to the terminal.
  • the asynchronous notification message can be one of the multiple responses to the current request.
  • the Server first extracts the Via option information and the Token option letter in the request of the obtaining step 705.
  • the message generates a response carrying the Via option information and the Token option information:
  • ProxyB according to the message type (Type): 200 discovery is a response message, according to the Token option information to find the locally stored session information, and extract the previously stored Via option information from the session information.
  • the ProxyA parses the response forwarded from the ProxyB. According to the Token option information, the local session information is not found, and the response is forwarded to the terminal client according to the routing information extracted from the Via option.
  • the response information at this time is:
  • steps 708, 710, 712, 714 and 716 are acknowledgements returned after receiving the response.
  • FIG. 8 is a flow diagram of another method 800 of data communication in a restricted application protocol CoAP in accordance with an embodiment of the present invention. This method is done by the terminal.
  • Via option information is used to record the request path and the response route.
  • the URI of the server is: coap: ⁇
  • the URI of the server.sensor.example/ServerlClient is: coap: ⁇ clientsensor.example/clientl
  • the communication address is: 192.0.2.2, and the Via option information of the own address is generated. Via: 192.0.2.2
  • proxy node through which the request passes and the session state information stored by each proxy node for the request are:
  • the passed stateless proxy node ProxyA does not store the session state of the request, it adds the Via option information carrying its own address in the request, and places it on the Via option information of the terminal:
  • the passed stateful proxy node ProxyB first stores the previous Via option information locally, then deletes the previous Via option information in the request and adds the Via option information with its own address: Via: 192.1.2.1
  • the server first extracts the address carried by the Via option information of the stateful proxy node and the Token option information:
  • the stateful proxy node ProxyB finds the response message according to the message type (Type): 200, finds the locally stored session information according to TokenlD, and extracts the previously stored Via option information from the session information.
  • the stateless proxy node ProxyA resolves the response forwarded from the stateful proxy node ProxyB. According to TokenlD, the corresponding session information is not found locally, and the response is forwarded to the terminal according to the routing information extracted from the Via option.
  • the response information at this time is:
  • the stateful proxy node and the stateless proxy node are allowed to exist simultaneously on the transmission path of the same session, and the routing information of the path in the protocol packet is extracted and deleted by the stateful proxy node, and then changed.
  • the routing information of the local storage path shortens the routing information carried in the protocol packets, thereby improving the efficiency of using the proxy node resources and reducing communication delays or interruptions caused by busy or faulty proxy nodes.
  • FIG. 9 is a flow diagram of yet another method 900 of data communication in a restricted application protocol CoAP in accordance with an embodiment of the present invention. This method is done by the server.
  • method 900 of Figure 9 it includes:
  • the stateless proxy node or stateful proxy node refers to the method of Figure 1 for the method of sending a request to the server.
  • the URI of the client is: coap: ⁇ sensor.
  • the address of the client/client is: 192.0.2.2, which generates the Via option information with its own address.
  • proxy node through which the request passes and the session state information stored by each proxy node for the request are:
  • the passed stateful proxy node ProxyB first stores the previous Via option information locally, then deletes the previous Via option information in the request and adds the Via option information with its own address: Via: 192.1.2.1
  • the server receives the request and stores the Via option information.
  • the server first extracts the address carried by the Via option information of the stateful proxy node ProxyB and
  • the stateful proxy node ProxyB finds the response message according to the message type (Type): 200, finds the locally stored session information according to TokenlD, and extracts the previously stored Via option information from the session information.
  • the stateless proxy node ProxyA resolves the response forwarded from the stateful proxy node ProxyB. According to TokenlD, the corresponding session information is not found locally, and the response is forwarded to the terminal according to the routing information extracted from the Via option.
  • the response information at this time is:
  • the stateful proxy node and the stateless proxy node are allowed to exist simultaneously on the transmission path of the same session, and the routing information of the path in the protocol packet is extracted and deleted by the stateful proxy node, and then changed.
  • the routing information of the local storage path shortens the routing information carried in the protocol packets, thereby improving the efficiency of using the proxy node resources and reducing communication delays or interruptions caused by busy or faulty proxy nodes.
  • FIG. 10 is a block diagram of an apparatus for data communication in a restricted application protocol CoAP, in accordance with an embodiment of the present invention.
  • the apparatus of FIG. 10 may be a proxy node in a CoAP, including a receiving module 1010, a processing module 1020, and a sending module 1030.
  • the receiving module 1010 is configured to receive a request sent by the terminal.
  • the request includes token option information, server address information, and the like.
  • the token option information is used to associate the request with the response, ie the token option information for the request and the corresponding response is the same.
  • the processing module 1020 is configured to perform processing of the Via option information on the request according to whether the device stores the parameters and status of the session corresponding to the request, where the Via option information is used to record the request path and the response route.
  • the sending module 1030 is configured to send the processed request.
  • Embodiments of the present invention allow a proxy node to be divided into a stateless proxy node and a stateful proxy node according to whether the device (proxy node) stores the state and parameters of the session corresponding to the current request in the CoAP, and may be on the transmission path of the same session. simultaneously exist.
  • a session includes requests and responses.
  • the proxy node that stores the parameters and status of the session and the proxy node that stores the parameters and status of the session when processing the response of one session are referred to as stateful agents in the session.
  • a node referred to as a stateful proxy node; similarly, when processing a request for that session
  • a proxy node that does not store the parameters and status of the session and a proxy node that does not store the parameters and status of the session when processing the response of the session is referred to as a stateless proxy node in the session, referred to as a stateless proxy node.
  • the parameters of the session include token option information, Via option information, etc., and the state of the session includes establishment, establishment, and termination. Whether the proxy node is a stateful proxy node or a stateless proxy node is defined for one session.
  • the proxy node judges that it will act as a stateful proxy node or a stateless proxy node can be judged by the following method.
  • the identifier bit is set in the configuration file of the proxy node, and the proxy node determines to act as a stateful proxy node or a stateless proxy node by identifying the identifier bit, and the identifier bit can be changed by manual configuration, so that the proxy node changes the role; It can be determined by the size of the allocated memory space.
  • the proxy node will act as a stateful proxy, and vice versa as a stateless proxy; how the proxy node determines itself to act as a stateful proxy or stateless
  • the agent is not a problem solved by the present invention, and is merely exemplified herein.
  • the stateless proxy node When the stateless proxy node adds Via option information to the request in the session, it sends a request to the server. When in this session, the stateful proxy node stores the Via option information in the request and deletes the Via option information in the request.
  • the processing module 1020 is specifically configured to: when the device does not store the parameter and the status of the session corresponding to the request, add the Via option information to the request; the sending module 1030 is specifically configured to send the added a request for the Via option information; or the processing module 1020 is specifically configured to: when the device stores the parameters and status of the session corresponding to the request, store the Via option information in the request, and delete the Via in the request. Option information; the sending module 1030 is specifically configured to send a request to delete the Via option information.
  • the Via record option referred to as the Via option, is used to record the request path and response route.
  • the assignment carried by the Via option is called Via option information.
  • the Via option is defined by the Type Length Value (TLV, Type Length Value) field as shown in Table 1.
  • the Via option information can be the address of the Proxy through which the request passes, and can be a URI, an IP address, or a unique device number.
  • the Via option information is routable, that is, according to the assignment and The corresponding device implements communication, and it is known from the above that there is no default value for the Via option.
  • C/E is one of the attributes of the Via option.
  • C means that the node on the CoAP path must understand the option and handle it accordingly.
  • E means that the node on the CoAP path can not understand the option and does not handle it accordingly.
  • the Via option information when the Via option information includes multiple address information, the Via option information can be implemented in the following two ways.
  • the newly added address information is placed in the order.
  • the first address information is called the second Via option information
  • the last address information is called the first Via option information.
  • the embodiment of the present invention takes the second implementation as an example, and the newly added address information is sequentially placed on the above.
  • the uppermost address information is referred to as first Via option information
  • the lowermost address information is referred to as second Via option information.
  • the processing module 1020 uses the source address of the request as an increase.
  • the Via option information or if the device is to store parameters and states of the session corresponding to the request, the processing module 1020 adds the source address of the request to the stored Via option information; or
  • the processing module 102 uses the address of the device as the added Via option. Information; or if the device is to store the parameters and status of the session corresponding to the request, the processing module 1020 adds the address of the device to delete the Via option information after deleting the Via option information in the request. After the request.
  • the stateful proxy node and the stateless proxy node are allowed to exist simultaneously on the transmission path of the same session, and the routing information of the path in the protocol packet is extracted and deleted by the stateful proxy node, and then changed.
  • the routing information of the local storage path shortens the routing information carried in the protocol packets, thereby improving the efficiency of using the proxy node resources and reducing communication delays or interruptions caused by busy or faulty proxy nodes.
  • 11 is a block diagram of an apparatus for data communication in a restricted application protocol CoAP, in accordance with another embodiment of the present invention.
  • the receiving module 1101, the processing module 1102, and the sending module 1103 of the device can perform the functions of the receiving module 1010, the processing module 1020, and the sending module 1030 of the device 1000, and can also perform more functions, as shown in the following description.
  • the device further includes a determining module 1104 and a lookup module 1105.
  • the apparatus when the receiving module 1101 receives the request from the terminal (i.e., receives a request directly from the terminal) and when the request uses the source address of the request as Via option information, the apparatus further includes a determining module 1104.
  • the determining module 1104 is configured to: when the first Via option information and the requested source address are inconsistent, modify the first Via option information to the requested source address.
  • the receiving module 1101 is further configured to: receive, by the terminal, a response based on the request from the server, to send the response to the terminal;
  • the sending module 1103 is further configured to delete the first Via option information carried in the response when the device does not store the parameter and the status of the session corresponding to the request. Transmitting, to the device corresponding to the first Via option information in the remaining Via option information, to the device corresponding to the first Via option information in the remaining Via option information; or when the response carries the Via option information, the sending module 1103 is further used to When the device does not store the parameter and status of the session corresponding to the request, deleting the first Via option information in the response, and sending a response that deletes the first Via option information to the first Via The device corresponding to the option information.
  • the device when the response does not carry the Via option information, and the device has stored the parameters and status of the session corresponding to the request, the device further includes a searching module 1105.
  • the searching module 1105 is configured to search, according to the token option information in the response, locally stored Via option information corresponding to the token option information; and the processing module 1102 is further configured to: according to the token option The stored Via option information found by the information is added to the response, and the first Via option information in the added Via option information is deleted; the sending module 1103 is further configured to send a response after deleting the first Via option information to The device corresponding to the first Via option information; or
  • the device When the response carries one of the Via option information, and the device has stored the parameters and status of the session corresponding to the request, the device further includes a lookup module 1105.
  • the searching module 1105 is configured to search, according to the token option information carried in the response, the stored Via option information corresponding to the token option information.
  • the processing module 1102 is further configured to delete the carried in the response. Via option information; adding Via option information corresponding to the token option information found according to the token option information to the response that deletes the Via option information; the sending module 1103 is further configured to join the lookup The response after the Via option information corresponding to the token option information is sent to the device corresponding to the first Via option information in the Via option information corresponding to the token option information.
  • the sending module selects the second Via option information of the stored Via option information as the Via option information of the response, and The response is sent to the device corresponding to the second Via option information.
  • the stateful proxy node and the stateless proxy node are allowed to exist simultaneously on the transmission path of the same session, and the routing information of the path in the protocol packet is deleted by the stateful proxy node, and changed to local.
  • the routing information of the storage path shortens the routing information carried in the protocol packets, thereby improving the efficiency of using the proxy node resources and reducing communication delays or interruptions caused by busy or faulty proxy nodes.
  • Figure 12 is a block diagram of a terminal for data communication in a restricted application protocol CoAP, in accordance with another embodiment of the present invention.
  • the terminal of FIG. 12 performs the functions of a terminal in CoAP, and the terminal includes a generating module 1210 transmitting module 1220 and a receiving module 1230.
  • the generating module 1210 generates a request to carry the path record Via option information, wherein the Via option information is used to record the request path and the response route.
  • the sending module 1220 sends a request to the proxy node, so that the proxy node performs the processing of the Via option information according to whether the proxy node stores the parameter and the state corresponding request of the session corresponding to the current request.
  • the receiving module 1230 receives a response sent by the proxy node based on the request.
  • the terminal implements the method 800.
  • the stateful proxy node and the stateless proxy node are allowed to exist simultaneously on the transmission path of the same session, and the routing information of the path in the protocol packet is extracted and deleted by the stateful proxy node, and then changed.
  • the routing information of the local storage path shortens the routing information carried in the protocol packets, thereby improving the efficiency of using the proxy node resources and reducing communication delays or interruptions caused by busy or faulty proxy nodes.
  • the server includes a receiving module 1310, a generating module 1320, and a sending module 1330.
  • the receiving module 1310 receives the request sent by the proxy node from the terminal.
  • the generating module 1320 generates a response carrying the Via option information based on the request, where the Via option information is used to record the request path and the response route.
  • the sending module 1330 sends a response to the proxy node, so that the proxy node processes the Via option information according to whether the proxy node has stored the parameter and state of the session corresponding to the request, and sends the processed response to the terminal.
  • the server implements the method 900.
  • the stateful proxy node and the stateless proxy node are allowed to exist simultaneously on the transmission path of the same session, and the routing information of the path in the protocol packet is extracted and deleted by the stateful proxy node, and then changed.
  • the routing information of the local storage path shortens the routing information carried in the protocol packets, thereby improving the efficiency of using the proxy node resources and reducing communication delays or interruptions caused by busy or faulty proxy nodes.
  • the CoAP terminal in the foregoing embodiment of the present invention may be a mobile terminal, such as a mobile device such as various mobile phones, notebooks, PDAs, or a fixed terminal, such as a PC.
  • the proxy node in the above embodiment of the present invention may be a network device in a network, or may be a device such as a computer.
  • the server in the above embodiment of the present invention may be a server.
  • the functional modules of the above-mentioned embodiments of the present invention may be functional modules that are executed in the processor of the above device, and the present invention is not limited thereto.
  • modules and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware or a combination of computer software and electronic hardware. Whether such functions are performed in hardware or software depends on the functionality described for the particular application of the technical solution, but such implementation should not be considered to be beyond the scope of the present invention.
  • the disclosed systems, devices, and methods may be implemented in other ways.
  • the device embodiments described above are merely illustrative
  • the division of the modules is only a logical function division, and the actual implementation may have another division manner, for example, multiple modules or components may be combined or may be integrated into another system, or some features may be ignored. Or not.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or module, and may be in an electrical, mechanical or other form.
  • the modules described as separate components may or may not be physically separate.
  • the components displayed as modules may or may not be physical modules, that is, may be located in one place, or may be distributed to multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the objectives of the solution of the embodiment.
  • each functional module in each embodiment of the present invention may be integrated into one processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.
  • the functions, if implemented in the form of software functional modules and sold or used as separate products, may be stored in a computer readable storage medium.
  • the technical solution of the present invention which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: a U disk, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like, which can store program codes. .

Abstract

Les modes de réalisation de la présente invention portent sur un procédé et un dispositif de communication de données dans un protocole d'applications contraintes (CoAP). Le procédé consiste à : recevoir une requête envoyée par un terminal ; traiter les informations d'option Via pour la requête selon si un nœud mandataire stocke ou non les paramètres et l'état de la session correspondant à la requête, les informations d'option Via étant utilisées pour enregistrer la route de requête et la route de réponse ; envoyer la requête traitée. La solution étant suscitée, le nœud mandataire sans état peut être mis en œuvre, le nœud mandataire à états et le nœud mandataire sans état peuvent exister simultanément sur le chemin de transmission de la même session, le nœud mandataire à états extrait et supprime ensuite les informations de route du chemin dans le message de protocole, et stocke localement les informations de route du chemin à la place de manière à raccourcir les informations de route contenues dans le message de protocole. En conséquence, le taux d'utilisation des ressources du nœud mandataire est augmenté, et le retard ou l'interruption de communication provoqués par l'occupation ou la défaillance du nœud mandataire sont réduits.
PCT/CN2012/073539 2011-07-14 2012-04-05 Procédé et dispositif de communication de données dans un protocole d'applications contraintes WO2012167659A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2011101970321A CN102882906A (zh) 2011-07-14 2011-07-14 受限应用协议中数据通信的方法和装置
CN201110197032.1 2011-07-14

Publications (1)

Publication Number Publication Date
WO2012167659A1 true WO2012167659A1 (fr) 2012-12-13

Family

ID=47295455

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/073539 WO2012167659A1 (fr) 2011-07-14 2012-04-05 Procédé et dispositif de communication de données dans un protocole d'applications contraintes

Country Status (2)

Country Link
CN (1) CN102882906A (fr)
WO (1) WO2012167659A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110808950A (zh) * 2019-09-25 2020-02-18 西安广和通无线软件有限公司 消息处理方法、装置、计算机设备和存储介质

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105227525B (zh) * 2014-06-17 2018-07-13 阿尔卡特朗讯 用于基于信令的物联网设备的ip通信方法与设备
CN104917828B (zh) * 2015-05-28 2018-04-27 重庆邮电大学 一种基于节点休眠和路由维护的CoAP协议代理缓存方法
CN106656730A (zh) * 2015-10-30 2017-05-10 西门子公司 一种通信方法、装置和系统
CN107104925A (zh) * 2016-02-22 2017-08-29 西门子公司 用于安全通信的方法、装置及系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050259633A1 (en) * 2004-05-18 2005-11-24 Fujitsu Limited Communication path control program and communication path control device in computer network system
CN101124785A (zh) * 2005-03-04 2008-02-13 思科技术公司 用于网络可达性检测的系统和方法
CN101252410A (zh) * 2008-04-10 2008-08-27 中国电子科技集团公司第三十研究所 一种减少ip路由协议带宽占用量的方法
CN102014129A (zh) * 2010-11-22 2011-04-13 华为技术有限公司 一种在CoAP网络中注册的方法及装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7746796B2 (en) * 2006-09-29 2010-06-29 Cisco Technology, Inc. Directed echo requests and reverse traceroute
CN101212418B (zh) * 2006-12-31 2010-05-12 华为技术有限公司 背靠背用户代理及其传输信息的方法
US7693060B2 (en) * 2007-10-12 2010-04-06 Cisco Technology, Inc. Method and apparatus for a reservation reflector function in routers

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050259633A1 (en) * 2004-05-18 2005-11-24 Fujitsu Limited Communication path control program and communication path control device in computer network system
CN101124785A (zh) * 2005-03-04 2008-02-13 思科技术公司 用于网络可达性检测的系统和方法
CN101252410A (zh) * 2008-04-10 2008-08-27 中国电子科技集团公司第三十研究所 一种减少ip路由协议带宽占用量的方法
CN102014129A (zh) * 2010-11-22 2011-04-13 华为技术有限公司 一种在CoAP网络中注册的方法及装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110808950A (zh) * 2019-09-25 2020-02-18 西安广和通无线软件有限公司 消息处理方法、装置、计算机设备和存储介质
CN110808950B (zh) * 2019-09-25 2022-06-28 西安广和通无线软件有限公司 消息处理方法、装置、计算机设备和存储介质

Also Published As

Publication number Publication date
CN102882906A (zh) 2013-01-16

Similar Documents

Publication Publication Date Title
KR102056416B1 (ko) 무선 네트워크에서 디바이스들 간의 터널 다이렉트 링크 설정(tdls) 세션을 확립하는 방법들 및 장치들
US8261339B2 (en) Dynamic network tunnel endpoint selection
JP5847191B2 (ja) コンテンツ共有を行う中間ノード及びコンテンツリクエスト端末並びにそれらのコンテンツ共有方法
US10313402B2 (en) Single pass load balancing and session persistence in packet networks
US9392081B2 (en) Method and device for sending requests
WO2011137792A1 (fr) Procédé et appareil permettant la coopération entre des dispositifs push
WO2021143239A1 (fr) Procédé et appareil de commande de routage, dispositif électronique et support de stockage
RU2464722C2 (ru) Способ, устройство и система для распределения сообщений
EP2466856A1 (fr) Procédé de réalisation de service et système de service
WO2013044671A1 (fr) Procédé d'accès internet, terminal et support de stockage
WO2013107137A1 (fr) Serveur, terminal et procédé d'obtention de cycle de rythme cardiaque
JP2022550165A (ja) ローミング・シグナリング・メッセージ送信方法、関連するデバイス、および通信システム
WO2012167659A1 (fr) Procédé et dispositif de communication de données dans un protocole d'applications contraintes
WO2011160587A1 (fr) Procédé et système de connexion d'un terminal à double pile à des réseaux
WO2019201072A1 (fr) Procédé de gestion de planification de service cdn, et serveur cdn
WO2012034414A1 (fr) Procédé et système de traitement de services de poste à poste (p2p)
WO2012088934A1 (fr) Procédé et dispositif de commutation pour filtrer des messages
WO2017161866A1 (fr) Procédé et dispositif de connexion à un réseau
CN114244850B (zh) 数据包处理方法、装置、计算机设备和存储介质
WO2022179218A1 (fr) Procédé et appareil de communication
CN108713336B (zh) 用户设备标识与信息中心联网请求的相关性
WO2012088828A1 (fr) Procédé, système et routeur de passerelle d'accès pour maintenance de table
JP4013920B2 (ja) 通信システム、通信装置及びその動作制御方法並びにプログラム
WO2012136094A1 (fr) Procédé et système de maîtrise de surcharge dans un réseau poste à poste
WO2015135124A1 (fr) Procédé et appareil de transfert d'informations

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12797250

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12797250

Country of ref document: EP

Kind code of ref document: A1