WO2020038443A1 - Procédé et dispositif de communication de pontage - Google Patents

Procédé et dispositif de communication de pontage Download PDF

Info

Publication number
WO2020038443A1
WO2020038443A1 PCT/CN2019/102039 CN2019102039W WO2020038443A1 WO 2020038443 A1 WO2020038443 A1 WO 2020038443A1 CN 2019102039 W CN2019102039 W CN 2019102039W WO 2020038443 A1 WO2020038443 A1 WO 2020038443A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource
communication protocol
identifier
virtual server
bridge
Prior art date
Application number
PCT/CN2019/102039
Other languages
English (en)
Chinese (zh)
Inventor
唐海
Original Assignee
Oppo广东移动通信有限公司
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 Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Publication of WO2020038443A1 publication Critical patent/WO2020038443A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/26—Special purpose or proprietary protocols or architectures
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45504—Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4604—LAN interconnection over a backbone network, e.g. Internet, Frame Relay
    • H04L12/462—LAN interconnection over a bridge based backbone
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08—Protocols for interworking; Protocol conversion
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/18—Multiprotocol handlers, e.g. single devices capable of handling multiple protocols

Definitions

  • Embodiments of the present application relate to the field, and more particularly, to a method and device for bridge communication.
  • the bridge device can realize the conversion between different protocols, so that the communication between the devices using different protocols can be realized.
  • the bridge device can create a virtual OCF server for the OCF device, so that the OCF client can communicate with the virtual OCF server through the OCF protocol, and the virtual OCF server can communicate with the OCF server.
  • Non-OCF devices communicate with non-OCF protocols, so that communication between OCF devices and non-OCF devices can be achieved.
  • the embodiments of the present application provide a method and device for bridge communication, which can reduce the number of endpoints in the bridge device and reduce the complexity of the device bridge communication.
  • a bridge communication method including: a bridge device receiving a resource discovery request message sent by a first communication protocol client; the bridge device sending a resource discovery response message to the first communication protocol client,
  • the resource discovery response message includes information of a first communication protocol virtual server, and the information of the first communication protocol virtual server includes a uniform resource identifier of a platform resource, a uniform resource identifier of an equipment resource, and an endpoint, wherein the first The endpoint of the communication protocol virtual server is the same as the endpoint of the bridging device.
  • the uniform resource identifier of the platform resource of the first communication protocol virtual server is different from the uniform resource identifier of the platform resource of the bridging device.
  • the uniform resource identifier of the device resource of the communication protocol virtual server is different from the uniform resource identifier of the device resource of the bridge device.
  • a bridge communication method including: a first communication protocol client sends a resource discovery request message to a bridge device; the first communication protocol client receives a resource discovery response message sent by the bridge device,
  • the resource discovery response message includes information of a first communication protocol virtual server, and the information of the first communication protocol virtual server includes a uniform resource identifier of a platform resource, a uniform resource identifier of an equipment resource, and an endpoint, wherein the first The endpoint of the communication protocol virtual server is the same as the endpoint of the bridging device.
  • the uniform resource identifier of the platform resource of the first communication protocol virtual server is different from the uniform resource identifier of the platform resource of the bridging device.
  • the uniform resource identifier of the device resource of the communication protocol virtual server is different from the uniform resource identifier of the device resource of the bridge device.
  • a bridge communication method including: the bridge device receives a device registration request message sent by a second communication protocol device; and the bridge device creates a first communication protocol virtual server for the second communication protocol device Wherein the endpoint of the first communication protocol virtual server is the same as the endpoint of the bridging device, the uniform resource identifier of the platform resource of the first communication protocol virtual server and the uniform resource identifier of the platform resource of the bridging device Different identifiers, the uniform resource identifier of the device resource of the first communication protocol virtual server is different from the uniform resource identifier of the device resource of the bridge device.
  • a bridge communication method including: a bridge device receiving a resource discovery request message sent by a first communication protocol client; the bridge device sending a resource discovery response message to the first communication protocol client,
  • the resource discovery response message includes information of a pre-created proxy service resource and a first communication protocol virtual server, and the information of the pre-created proxy service resource and the first communication protocol virtual server includes a uniform resource identifier of a platform resource, a device A uniform resource identifier and endpoint of the resource, wherein the endpoint of the first communication protocol virtual server is the same as the endpoint of the bridge device, and the uniform resource identifier of the proxy service resource is the same as the platform resource of the bridge device
  • the resource identifier and the uniform resource identifier of the device resource are different;
  • the bridge device receives a resource operation request message sent by the first communication protocol client, and the resource operation request message includes a platform resource of the proxy service resource Uniform resource identifier and device resource A source identifier, and the resource operation request message further includes a
  • a bridge communication method including: a first communication protocol client sends a resource discovery request message to a bridge device; the first communication protocol client receives a resource discovery response message sent by the bridge device,
  • the resource discovery response message includes information of a pre-created proxy service resource and a first communication protocol virtual server, and the information of the pre-created proxy service resource and the first communication protocol virtual server includes a uniform resource identifier of a platform resource, a device The uniform resource identifier and endpoint of the resource, where the endpoint of the first communication protocol virtual server is the same as the endpoint of the bridge device, and the uniform resource identifier of the proxy service resource is the same as the platform resource of the bridge device
  • the resource identifier and the uniform resource identifier of the device resource are different;
  • the first communication protocol client sends a resource operation request message to the bridge device, and the resource operation request message includes the platform resource of the proxy service resource Uniform Resource Identifier and Uniform Resource for Device Resources Identifier, the resource operation request message further includes target identification
  • a bridge communication method including: the bridge device receives a device registration request message sent by a second communication protocol device; the bridge device creates a first communication protocol virtual server for the second communication protocol device And a proxy service resource, wherein the endpoint of the first communication protocol virtual server is the same as the endpoint of the bridge device, the uniform resource identifier of the proxy service resource and the uniform resource identifier of the platform resource of the bridge device, The uniform resource identifiers of the device resources are all different, and the proxy service resource is used to proxy a request of the first communication protocol client to the first communication protocol virtual server.
  • a bridging device for performing the method described in any of the optional implementation manners in the first aspect or the third aspect.
  • the bridging device includes a functional module for performing the method described in any one of the optional implementation manners of the first aspect, the third aspect, the fourth aspect, or the sixth aspect.
  • a first communication protocol device is provided, which is configured to perform the method described in the foregoing second aspect or any optional implementation manner in the fourth aspect.
  • the bridging device includes a functional module for performing the method described in the second aspect or any optional implementation manner of the fifth aspect.
  • a bridge device including a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory to execute the methods in the implementation manners of the first aspect, the third aspect, the fourth aspect, or the sixth aspect.
  • a first communication protocol device including a processor and a memory.
  • the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the foregoing second aspect or the implementation manners in the fifth aspect.
  • a chip for implementing the method in any possible implementation manner in the first aspect or the third aspect.
  • the chip includes a processor for invoking and running a computer program from the memory, so that the device installed with the chip executes any possible one of the first aspect, the third aspect, the fourth aspect, or the sixth aspect described above. Method in implementation.
  • a chip for implementing the method in any of the possible implementation manners in the second aspect or the fourth aspect.
  • the chip includes a processor for invoking and running a computer program from the memory, so that the device installed with the chip executes the method in any possible implementation manner in the second aspect or the fifth aspect described above.
  • a computer-readable storage medium for storing a computer program that causes a computer to execute any possible implementation manner of the first aspect, the third aspect, the fourth aspect, or the sixth aspect described above. Method.
  • a computer-readable storage medium for storing a computer program that causes a computer to execute the method in any of the possible implementation manners of the second aspect or the fifth aspect described above.
  • a computer program product including computer program instructions that cause a computer to execute any of the possible implementation manners in the first aspect, the third aspect, the fourth aspect, or the sixth aspect described above. method.
  • a computer program product including computer program instructions that cause a computer to execute the method in any of the possible implementation manners of the second aspect or the fifth aspect described above.
  • a seventeenth aspect provides a computer program that, when run on a computer, causes the computer to execute the method in any of the possible implementation manners of the first aspect, the third aspect, the fourth aspect, or the sixth aspect described above.
  • a computer program is provided that, when run on a computer, causes the computer to perform the method in any of the possible implementations of the second or fifth aspect described above.
  • the endpoints of all the virtual server end on the bridge device are the same as the endpoints of the bridge device.
  • the number of endpoints on the bridge device will be reduced, which can reduce the maintenance cost of the endpoint by the bridge device.
  • the platform resources and device resources of the virtual server no longer use fixed uniform resource identifiers.
  • the unified resource identifiers of the platform resources of the virtual server and the unified resources of the platform resources of the bridge device are used.
  • the identifiers are set differently, and the uniform resource identifier of the device resource of the virtual server and the uniform resource identifier of the device resource of the bridge device are set differently.
  • the endpoint is related to the communication channel. After the endpoint is reduced, the communication channel between the client established by the bridge device and the bridge device will be reduced. The reduction of the communication channel can reduce the resource overhead, and the bridge device only needs to maintain one communication channel. Reduce the communication complexity of bridge devices.
  • FIG. 1 is a schematic diagram of communication between a bridge device and an OCF device according to an embodiment of the present application.
  • FIG. 2 is a schematic flowchart of a bridge communication method according to an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of another bridge communication method according to an embodiment of the present application.
  • FIG. 4 is a schematic flowchart of another bridge communication method according to an embodiment of the present application.
  • FIG. 5 is a schematic flowchart of another bridge communication method according to an embodiment of the present application.
  • FIG. 6 is a schematic flowchart of another bridge communication method according to an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of another bridge communication method according to an embodiment of the present application.
  • FIG. 8 is a schematic block diagram of a bridge device according to an embodiment of the present application.
  • FIG. 9 is a schematic block diagram of a first communication protocol device according to an embodiment of the present application.
  • FIG. 10 is a schematic block diagram of another bridge device according to an embodiment of the present application.
  • FIG. 11 is a schematic block diagram of another bridge device according to an embodiment of the present application.
  • FIG. 12 is a schematic block diagram of another first communication protocol device according to an embodiment of the present application.
  • FIG. 13 is a schematic block diagram of another bridge device according to an embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • FIG. 15 is a schematic structural diagram of a chip according to an embodiment of the present application.
  • FIG. 16 is a schematic block diagram of a communication system according to an embodiment of the present application.
  • the bridge device can realize the conversion between different protocols, so that the communication between the devices using different protocols can be realized.
  • the bridge device can create a virtual OCF server for the OCF device, so that the OCF client can communicate with the virtual OCF server through the OCF protocol, and the virtual OCF server can communicate with the non-OCF device through the non-OCF protocol. This allows communication between OCF devices and non-OCF devices.
  • the bridge device can also implement conversion between any multiple communication protocol devices.
  • the bridge device can implement communication between a restricted application protocol (CoAP) device and a Bluetooth device, and can also implement communication between a wifi device and a zigbee device.
  • CoAP restricted application protocol
  • the communication protocols in the embodiments of the present application may also be other protocols generated for unifying the Internet of Things.
  • the bridge device may only support communication between two different communication protocol devices, and may also support communication between multiple different communication protocol devices at the same time.
  • OCF is an emerging technology standard organization for the Internet of Things application layer. In order to achieve true interconnection of all things, OCF hopes to formulate a unified Internet of Things standard, to achieve safe and reliable device discovery and connection mechanisms across different operating systems and platforms.
  • OCF provides a universal representational state transfer (Restful) architecture for IoT applications, devices, and platforms.
  • OCF's Restful architecture characterizes IoT entities and their service capabilities as OCF resources.
  • all physical entities can be described as resources and exposed to the outside world in the form of resources.
  • the state of the entity is described by resource representation.
  • Each resource has its own uniform resource identifier (URI ) And the types of interfaces that can be supported.
  • the entity that provides the resource is the OCF server, and the entity that accesses the resource is the OCF client.
  • the mobile application of the smartphone that obtains the indoor environment status data is an OCF client
  • the sensor that monitors the indoor environment status data is an OCF server.
  • the business interaction between the OCF client and the OCF server is achieved through the operation methods of creating, reading, updating, deleting, or notifying these OCF resources.
  • OCF resources include: resource URI, resource type, interface, etc.
  • resource URI resource URI
  • resource type resource type
  • interface etc.
  • specific definitions are as follows.
  • Resource URI It is identified by "href” in the OCF resource characterization and provides the address of the OCF server resource. The value of "href” is a specific resource URI. The OCF client accesses the resources of the OCF server through the resource URI.
  • Resource type It is represented by "rt" in OCF resource characterization, which indicates the type of resource.
  • OCF To facilitate the discovery of OCF equipment and resources, OCF also defines core resources that are supported by OCF equipment.
  • OCF core resources include platform resources and device resources.
  • a platform resource can include one or more OCF device instances.
  • Platform resources are host resources for device instance resources.
  • Device resources are used to describe the common information of all OCF device instance resources on a platform resource.
  • Platform resource Provides information about the platform to which the OCF device belongs.
  • the URI of the platform resource is fixed to "/ oic / p", and the resource type of the platform resource is "oic.wk.p”.
  • Device resource Provides information about specific OCF devices.
  • the URI of the device resource is fixed at "/ oic / d”
  • the resource type of the device resource is "oic.wk.d”.
  • the resource type of the device resource may also include one or more resource types related to device characteristics.
  • the resource type of the bridge device includes “oic.wk.d” and “oic.d.bridge”, which means that this device supports the bridge resource type.
  • the resource type of the lamp includes “oic.wk.d” and “oic.d.light”, which indicates that the device supports the resource type of the lamp.
  • each OCF server needs to have an endpoint.
  • Each OCF device must be associated with at least one endpoint for sending and receiving messages.
  • the endpoint can be understood as the communication address of the communication protocol, which is used by the OCF device to exchange messages.
  • the endpoint can be an IP address and a UDP port number.
  • the OCF client may send a resource operation request message to the OCF server.
  • the resource operation request message may carry a resource operation method.
  • the resource operation method may be, for example, operations such as creating a resource, reading a resource, updating a resource, or deleting a resource.
  • the OCF server may return a resource operation response message to the OCF client, and the resource operation response message carries a representation of the requested resource.
  • Non-OCF devices refer to IoT devices that do not support the OCF standard protocol. For example, zigbee devices, z-wave devices, Bluetooth devices, etc., connecting non-OCF devices to the OCF system can realize communication between non-OCF devices and OCF devices, and expand the scope of interconnection and interoperability of IoT devices.
  • OCF defines a device bridging communication mechanism.
  • OCF bridging devices communication between OCF devices and non-OCF devices can be realized.
  • the OCF bridge device can map a non-OCF device to a virtual OCF server and perform conversion between the OCF protocol and the non-OCF protocol, so that the OCF client can communicate with the non-OCF device, thereby realizing communication between the OCF device and the non-OCF device.
  • the OCF bridge device can map a non-OCF device to a virtual OCF server 1 and a non-OCF device to a virtual OCF server 2.
  • the client can communicate with the virtual OCF server 1 and the virtual OCF server 2 through the OCF protocol, and the bridge device can convert the request from the OCF client to a non-OCF protocol instruction and send it to the non-OCF device 1 and the non-OCF device 2.
  • the URIs of the platform resources and device resources of the virtual OCF server 1, virtual OCF server 2, and the bridge device are the same.
  • the URIs of the platform resources of the virtual OCF server 1 and the virtual OCF server 2 are "/ oic / p"
  • the URIs of the device resources are "/ oic / d”.
  • virtual OCF server 1 and virtual OCF server 2 must have their own endpoints.
  • OCF bridge devices, virtual OCF server 1, and virtual OCF server 2 have different endpoints. As shown in FIG. 1, the endpoint of the OCF bridge device is endpoint 1, the endpoint of virtual OCF server 1 is endpoint 2, and the endpoint of virtual OCF server 2 is endpoint 3.
  • the endpoint of the bridge device can be "coap: // [fe80 :: b1d6]: 44444"
  • the endpoint of the virtual OCF server 1 can be "coap: // [2001: db8: b :: c2e5]: 11111"
  • the endpoint of the virtual OCF server 2 can be "coap: // [2001: db8: b :: c2e5]: 22222".
  • the following uses the non-OCF device 1 as a light and the non-OCF device 2 as an oven as an example to describe the resource characterization of the bridge device, the virtual OCF server 1 and the virtual OCF server 2.
  • the following resource characterization is only an example, and does not limit the embodiments of the present application.
  • the URI of the platform resource of the bridge device is "/ oic / p"
  • the resource type of the platform resource is "oic.wk.p”
  • the interface of the platform resource is "oic.if.r” and “oic.if.baseline”
  • the endpoint of the platform resource is "coap: // [fe80 :: b1d6]: 44444".
  • the URI of the device resource of the bridge device is "/ oic / d"
  • the resource type of the device resource is "oic.wk.d” and “oic.d.bridge”
  • the interface of the device resource is "oic.if.r” and “Oic.if.baseline”
  • the endpoint of the device resource is "coap: // [fe80 :: b1d6]: 44444".
  • the resource representation of the virtual OCF server 1 is as follows:
  • the platform resource URI of the virtual OCF server 1 is "/ oic / p", the resource type of the platform resource is “oic.wk.p”, and the interface of the platform resource is "oic.if.r” and “oic.if.” baseline ", the endpoint of the platform resource is” coap: // [2001: db8: b :: c2e5]: 11111 ".
  • the device resource URI of the virtual OCF server 1 is "/ oic / d"
  • the resource type of the device resource is "oic.wk.d” and “oic.d.light”
  • the interface of the device resource is "oic.if.” r “and” oic.if.baseline ", the endpoint of the device resource is” coap: // [2001: db8: b :: c2e5]: 11111 ".
  • the device instance resource URI of virtual OCF server 1 is "/ myLightSwitch", the resource type of the device instance resource is “oic.r.switch.binary”, and the interface of the device instance resource is "oic.if.a” and “oic .if.baseline ", the endpoint of the device instance resource is” coap: // [2001: db8: b :: c2e5]: 11111 ".
  • the resource representation of the virtual OCF server 2 is as follows:
  • the platform resource URI of the virtual OCF server 2 is "/ oic / p", the resource type of the platform resource is “oic.wk.p”, and the interface of the platform resource is "oic.if.r” and “oic.if.” baseline ", the endpoint of the platform resource is” coap: // [2001: db8: b :: c2e5]: 22222 ".
  • the URI of the device resource of the virtual OCF service 2 is "/ oic / d"
  • the resource type of the device resource is "oic.wk.d” and “oic.d.oven”
  • the interface of the device resource is "oic.if.r” "And” oic.if.baseline ", the endpoint of the device resource is” coap: // [2001: db8: b :: c2e5]: 22222 ".
  • the device instance resource URI of the virtual OCF server 2 is "/ myOven"
  • the resource type of the device instance resource is "oic.r.switch.binary” and “oic.r.temperature”
  • the interface of the device instance resource is "oic” .if.a “and” oic.if.baseline "
  • the endpoint of the device instance resource is" coap: // [2001: db8: b :: c2e5]: 22222 ".
  • each virtual OCF server mapped on the bridge device has its own endpoint, and the endpoint of the virtual OCF server is different from the endpoint of the bridge device.
  • the OCF bridge device needs to maintain a large number of endpoints, which results in a higher cost of endpoint maintenance.
  • the endpoints are related to the transmission protocol. The more endpoints, the higher the communication complexity of the device.
  • IP Internet protocol
  • UDP user datagram protocol
  • the embodiments of the present application provide a method for bridging communication, which can reduce the maintenance cost of endpoints and reduce the complexity of device communication.
  • the method for bridging communication in the embodiment of the present application is described in detail below with reference to FIG. 2. As shown in FIG. 2, the method includes steps S210-S220.
  • the bridge device receives a resource discovery request message sent by the first communication protocol client.
  • the first communication protocol client may mean that the client can communicate with the bridge device through the first communication protocol.
  • the first communication protocol client may be a client in the Internet of Things.
  • the resource discovery request message can be used to discover all resources on the bridge device.
  • the resource discovery request message may be used to discover resource information of all virtual servers on the bridge device.
  • the bridge device when the bridge device receives the resource discovery request message sent by the first communication protocol client, it may send related information of all the first communication protocol virtual servers on the bridge device to the first communication protocol client.
  • the embodiment of the present application does not specifically limit the first communication protocol and the second communication protocol, as long as the first communication protocol and the second communication protocol are two different protocols.
  • the first communication protocol may be a communication protocol in the Internet of Things
  • the second communication protocol is a communication protocol in a non-Internet of Things.
  • the first communication protocol may be a zigbee protocol
  • the second communication protocol may be a Bluetooth protocol.
  • the first communication protocol may be an OCF protocol
  • the second communication protocol may be a non-OCF protocol. That is, the first communication protocol client may be an OCF client, the second communication protocol device may be a non-OCF device, and the first communication protocol virtual server may be a virtual OCF server.
  • the non-OCF protocol may be zigbee, z-wave, or Bluetooth.
  • the bridge device When the bridge device creates the first communication protocol virtual server for the second communication protocol device, it can create platform resources, device resources, and endpoints for the second communication protocol device. In order to reduce the communication complexity, the bridging device may set the same endpoint for the created virtual server, and distinguish the different second communication protocol devices through different URIs of platform resources and device resources.
  • the following uses the first communication protocol as the OCF protocol as an example to describe the resource information and endpoint information of the bridge device and the virtual OCF server.
  • the platform resource URI of the virtual OCF server no longer uses the fixed "/ oic / p", and the device resource of the virtual OCF server no longer uses the fixed "/ oic / d".
  • the virtual OCF server can use platform resource and device resource URIs different from the bridge device.
  • the embodiments of the present application may not specifically limit them.
  • the bridge device may number the created virtual OCF server, and add the number sequence to the URI of the platform and device resources of the virtual OCF server, so that different platform resources and device resources can be distinguished by the URI.
  • the bridge resource can add the device identifier of the non-OCF device to the mapped resource of the platform resource and device resource of the virtual OCF server.
  • Device identification so that different platform resources and device resources can be distinguished by the device identification of non-OCF devices.
  • the device identifier of the non-OCF device 1 is "light_device_id", and the server mapped by the non-OCF device 1 on the bridge device is the virtual OCF server 1, and the URI of the platform resource of the virtual OCF server 1 can be "/ di / light_device_id / oic / p ", the URI of the device resource of the virtual OCF server 1 may be” / di / light_device_id / oic / d ".
  • the device identifier of the non-OCF device 2 is "/ di / oven_device_id", and the server mapped by the non-OCF device 2 on the bridge device is the virtual OCF server 2.
  • the URI of the platform resource of the virtual OCF server 2 can be "/ di / oven_device_id / oic / d ", the URI of the device resource of the virtual OCF server 2 may be” / di / oven_device_id / oic / d ".
  • the bridge device may send relevant information of all virtual servers on the bridge device to the first communication protocol client.
  • the bridge device sends a resource discovery response message to the first communication protocol client, and the resource discovery response message includes information of the first communication protocol virtual server.
  • the information of the first communication protocol virtual server includes a URI of an endpoint platform resource and / or a device resource URI of the first communication protocol virtual server.
  • the information of the first communication protocol virtual server may further include an interface and a resource type of the first communication protocol virtual server.
  • the information of the virtual OCF server includes the endpoint of the virtual OCF server, the URI of the platform resource, and / or the URI of the device resource.
  • the URI of the platform resource and / or the URI of the device resource please refer to the description above. To avoid repetition, details are not described here.
  • the information of the virtual OCF server further includes at least one of the following information: the interface and resource type of the virtual OCF server.
  • the interface of the virtual OCF server may be, for example, "oic.if.baseline”.
  • the resource type of the platform resource of the virtual OCF server may be, for example, "oic.wk.p".
  • the resource types of the device resources may be, for example, “oic.wk.d” and “oic.d.light”.
  • the resource types of the device resources may be, for example, "oic.wk.d” and "oic.d.oven".
  • the endpoints of all virtual server ends on the bridge device are the same as the endpoints of the bridge device.
  • the number of endpoints on the bridge device will be reduced, which can reduce the maintenance cost of the bridge device to the endpoint.
  • the platform resources and device resources of the virtual server no longer use fixed URIs. Instead, the URIs of the platform resources of the virtual server and the URIs of the platform resources of the bridge device are set to be different. The URI of the device resource at the end and the URI of the device resource of the bridge device are set differently.
  • the number of endpoints in the bridge device can be reduced, and thus the communication complexity of the bridge device can be reduced.
  • the endpoint is used for transmission at the network layer.
  • the endpoint is related to the communication channel. After the endpoint on the bridge device is reduced, the communication channel between the client and the bridge device established by the bridge device will be reduced.
  • the reduction of the communication channel can reduce resources Overhead, reducing the complexity of the network layer. And the bridge device only needs to maintain one communication channel, so that the communication complexity of the bridge device can be reduced.
  • a bridge device when it establishes a communication channel, it can establish a transmission channel according to a transmission protocol. For example, for a client using the COAP protocol, the communication channel between the client established by the bridge device and the bridge device is established based on the COAP protocol.
  • the resources of the first communication protocol virtual server further include a device instance resource
  • the resource response message may include a URI of the device instance resource
  • the bridge device may receive a resource operation request message sent by the first communication protocol client, and the resource operation request message includes the URI of the device instance resource of the first communication protocol virtual server.
  • the URI of the device instance resource is used to identify the device requested by the first communication protocol client.
  • the bridge device may receive a resource operation request message sent by the OCF client.
  • the resource operation request message may include a URI of a device instance resource of the virtual OCF server, and the URI of the instance resource is used to identify the device requested by the OCF client.
  • the resource operation request message may further include at least one of the following information: an interface of the device instance resource, a resource type of the device instance resource, a resource operation method, and an attribute value of the device instance resource.
  • the interface of the device instance resource can be “oic.if.a” and “oic.if.baseline”
  • the resource type of the device instance resource can be “oic.r.switch.binary” ".
  • the interface of the device instance resource can be "oic.if.a” and “oic.if.baseline”
  • the resource type of the device instance resource can be "oic.r.switch.binary” and "Oic.r.temperature”.
  • the resource operation method includes at least one of the following methods: creating a resource, reading a resource, updating a resource, and deleting a resource.
  • the attribute value of the device instance resource refers to the operation data of the resource.
  • the property value "value" of the device instance resource can be "true” or "false”.
  • the property value is "true” it means that the light is turned on. Turn off the lights.
  • the bridge device may determine the second communication protocol device requested by the first communication protocol client according to the URI of the device instance resource. Then, the operation request message may be converted into a protocol message of the first communication protocol device, and the converted protocol message is sent to the first communication protocol device.
  • the protocol message may also be a device instruction of the second communication protocol device.
  • the bridge device can convert the resource operation request message into a device instruction of the non-OCF device 1, and send the converted device instruction to Non-OCF equipment 1.
  • the bridge device can convert the resource operation request message into a device instruction of the non-OCF device 2, and send the converted device instruction to the non-OCF Device 2.
  • the device identifier may be added to the URI of the instance resource of the first communication protocol virtual server.
  • the information of the first communication protocol virtual server may be created by the bridge device, or may be obtained by the bridge device from other devices.
  • the method in FIG. 2 may further include: the bridge device receives the connection establishment request message sent by the second communication protocol device, and the bridge device creates a first communication protocol virtual server for the second communication protocol device.
  • the bridging device can create a first communication protocol virtual server for the second communication protocol device, realize the conversion between the first communication protocol and the second communication protocol, and establish the first communication protocol device. And a second communication protocol device.
  • the device identifier can uniquely identify a non-OCF device, and the device identifier can identify a non-OCF device.
  • connection establishment request message may be a device registration request message, or may be another message for establishing a connection with the bridge device.
  • FIG. 3 is a schematic flowchart of another bridge communication method according to an embodiment of the present application.
  • the method in FIG. 3 includes steps S310-S320.
  • the first communication protocol client sends a resource discovery request message to the bridge device.
  • the resource discovery request message can be used to discover resources on the bridge device.
  • the resource discovery request message may be used to discover resource information of all virtual servers on the bridge device.
  • the first communication protocol client may mean that the client can communicate with the bridge device through the first communication protocol.
  • the first communication protocol may be a communication protocol in the Internet of Things.
  • the first communication protocol may be an OCF protocol.
  • the first communication protocol client receives a resource discovery response message sent by the bridge device, and the resource discovery response message includes information of the first communication protocol virtual server created by the bridge device.
  • the information of the first communication protocol virtual server includes an endpoint of the first communication protocol virtual server, a URI of a platform resource, a URI of a device resource, and the like.
  • the endpoint of the first communication protocol virtual server is the same as the endpoint of the bridging device, the uniform resource identifier of the platform resource of the first communication protocol virtual server and the uniform resource identifier of the platform resource of the bridging device
  • the uniform resource identifier of the device resource of the first communication protocol virtual server is different from the uniform resource identifier of the device resource of the bridging device
  • the first communication protocol is different from the second communication protocol.
  • the information of the first communication protocol virtual server may further include an interface and a resource type of the first communication protocol virtual server.
  • the embodiment of the present application does not specifically limit the first communication protocol and the second communication protocol, as long as the first communication protocol and the second copper communication protocol are two different protocols.
  • the first communication protocol may be a communication protocol in the Internet of Things
  • the second communication protocol is a communication protocol in a non-Internet of Things.
  • the first communication protocol is the zigbee protocol
  • the second communication protocol is the Bluetooth protocol.
  • the first communication protocol may be an OCF protocol
  • the second communication protocol may be a non-OCF protocol. That is, the first communication protocol client may be an OCF client, the second communication protocol device may be a non-OCF device, and the first communication protocol virtual server may be a virtual OCF server.
  • the non-OCF protocol may be zigbee, z-wave, or Bluetooth.
  • the bridge device When the bridge device creates the first communication protocol virtual server for the second communication protocol device, it can create platform resources, device resources, and endpoints for the second communication protocol device. In order to reduce the communication complexity, the bridging device may set the same endpoint for the created virtual server, and distinguish the different second communication protocol devices through different URIs of platform resources and device resources.
  • the following uses the first communication protocol as the OCF protocol as an example to describe the resource information and endpoint information of the bridge device and the virtual OCF server.
  • the platform resource URI of the virtual OCF server no longer uses the fixed "/ oic / p", and the device resource of the virtual OCF server no longer uses the fixed "/ oic / d".
  • the virtual OCF server can use platform resource and device resource URIs different from the bridge device.
  • the embodiments of the present application may not specifically limit them.
  • the URIs of the platform resources and device resources of the virtual OCF server can be numbered in sequence, that is, the URIs of the platform resources and device resources of the virtual OCF server include the numbering sequence, so that different platform resources and devices can be distinguished by the URI. Resources.
  • the URIs of the platform resources and device resources of the virtual OCF server include device identifiers of non-OCF devices. Since different non-OCF devices have different device identifiers, different platforms can be distinguished by device identifiers of non-OCF devices Resources and equipment resources.
  • the device identifier of the non-OCF device 1 is "light_device_id", and the server mapped by the non-OCF device 1 on the bridge device is the virtual OCF server 1, and the URI of the platform resource of the virtual OCF server 1 can be "/ di / light_device_id / oic / p ", the URI of the device resource of the virtual OCF server 1 may be” / di / light_device_id / oic / d ".
  • the device identifier of the non-OCF device 2 is "/ di / oven_device_id", and the server mapped by the non-OCF device 2 on the bridge device is the virtual OCF server 2.
  • the URI of the platform resource of the virtual OCF server 2 can be "/ di / oven_device_id / oic / d ", the URI of the device resource of the virtual OCF server 2 may be” / di / oven_device_id / oic / d ".
  • the resource response message may include information about resources of all virtual OCF server ends on the bridge device.
  • the OCF client After receiving the resource response message, the OCF client can select the resources of the virtual OCF server that you want to operate.
  • the endpoints of all virtual server ends on the bridge device are the same as the endpoints of the bridge device.
  • the number of endpoints on the bridge device will be reduced, which can reduce the maintenance cost of the bridge device to the endpoint.
  • the platform resources and device resources of the virtual server no longer use fixed URIs. Instead, the URIs of the platform resources of the virtual server and the URIs of the platform resources of the bridge device are set to be different. The URI of the device resource at the end and the URI of the device resource of the bridge device are set differently.
  • the number of endpoints in the bridge device can be reduced, and thus the communication complexity of the bridge device can be reduced.
  • the endpoint is used for transmission at the network layer.
  • the endpoint is related to the communication channel. After the endpoint on the bridge device is reduced, the communication channel between the client and the bridge device established by the bridge device will be reduced.
  • the reduction of the communication channel can reduce resources Overhead, reducing the complexity of the network layer. And the bridge device only needs to maintain one communication channel, so that the communication complexity of the bridge device can be reduced.
  • the URI of the platform resource and the device resource of the first communication protocol virtual server includes the device identification of the second communication protocol device.
  • the device identifiers of the second communication protocol devices can distinguish different platform resources and device resources.
  • the resources of the first communication protocol virtual server also include device instance resources
  • the resource response message may also include the URI of the device instance resource.
  • the first communication protocol client may select the platform resource and device resource to be accessed according to the platform resource and device resource information carried in the response message, and may For device instance resource information, select the device instance resource that you want to operate.
  • the first communication protocol client may select the second communication that it wants to operate according to the information carried in the resource response message. Protocol device, and then the first communication protocol client may send a resource operation request message to the first communication protocol virtual server corresponding to the selected second communication protocol device.
  • the resource operator request message includes the URI of the device instance resource.
  • the resource operation request message may further include at least one of the following information: an interface of the device instance resource, a resource type of the device instance resource, a resource operation method, and an attribute value of the device instance resource.
  • the interface of the device instance resource can be “oic.if.a” and “oic.if.baseline”
  • the resource type of the device instance resource can be “oic.r.switch.binary” ".
  • the interface of the device instance resource can be "oic.if.a” and “oic.if.baseline”
  • the resource type of the device instance resource can be "oic.r.switch.binary” and "Oic.r.temperature”.
  • the resource operation method includes at least one of the following methods: creating a resource, reading a resource, updating a resource, and deleting a resource.
  • the attribute value of the device instance resource refers to the operation data of the resource.
  • the property value "value" of the device instance resource can be "true” or "false”.
  • the property value is "true” it means that the light is turned on. Turn off the lights.
  • FIG. 4 is a schematic flowchart of another bridge device communication method according to an embodiment of the present application.
  • the method of FIG. 4 includes steps S410-S420.
  • the method in FIG. 4 can be used in combination with the methods in FIGS. 2 and 3.
  • the method in FIG. 4 can be used in combination with the methods in FIGS. 2 and 3.
  • FIG. 4 For a detailed description of the method in FIG. 4, reference may be made to the description in the methods in FIG. 2 and FIG. 3 above. To avoid repetition, details are not described herein.
  • the bridge device receives a device registration request message sent by the second communication protocol device.
  • the device registration request message may also be a connection establishment request message.
  • connection establishment request message may include a device identifier of the second communication protocol device.
  • the bridge device creates a first communication protocol virtual server for the second communication protocol device, wherein the endpoint of the first communication protocol virtual server is the same as the endpoint of the bridge device, and the first communication protocol
  • the uniform resource identifier of the platform resource of the virtual server is different from the uniform resource identifier of the platform resource of the bridge device.
  • the uniform resource identifier of the device resource of the first communication protocol virtual server and the device resource of the bridge device are different. Uniform resource identifiers are different.
  • the bridge device creates information of the first communication protocol virtual server.
  • the information of the first communication protocol virtual server includes a uniform resource identifier of the platform resource and a uniform resource identifier of the device resource. Breaks and endpoints.
  • FIG. 5 is a schematic flowchart of another bridge device communication method according to an embodiment of the present application.
  • the method in FIG. 5 includes steps S510-S550.
  • the bridge device receives a resource discovery request message sent by the first communication protocol client.
  • the resource discovery request message is mainly used to discover resources on the bridge device.
  • the resource discovery request message may be used to discover resource information of all virtual servers on the bridge device.
  • the first communication protocol client may mean that the client can communicate with the bridge device through the first communication protocol.
  • the first communication protocol may be a protocol in the Internet of Things.
  • the first communication protocol may be an OCF protocol.
  • the bridging device sends a resource discovery response message to the first communication protocol client, and the resource discovery response message includes information of a pre-created proxy service resource and information of the first communication protocol virtual server.
  • the endpoint of the first communication protocol virtual server is the same as the endpoint of the bridge device, the uniform resource identifier of the proxy service resource, the uniform resource identifier of the platform resource of the bridge device, and the uniform resource of the device resource
  • the identifiers are all different.
  • the first communication protocol virtual server may be a server mapped by the second communication protocol device on the bridge device, and the first communication protocol is different from the second communication protocol.
  • the embodiment of the present application does not specifically limit the first communication protocol and the second communication protocol, as long as the first communication protocol and the second communication protocol are two different protocols.
  • the first communication protocol may be a communication protocol in the Internet of Things
  • the second communication protocol is a communication protocol in a non-Internet of Things.
  • the first communication protocol is the zigbee protocol
  • the second communication protocol is the Bluetooth protocol.
  • the first communication protocol may be an OCF protocol
  • the second communication protocol may be a non-OCF protocol. That is, the first communication protocol client may be an OCF client, the second communication protocol device may be a non-OCF device, and the first communication protocol virtual server may be a virtual OCF server.
  • the non-OCF protocol may be zigbee, z-wave, or Bluetooth.
  • the resource discovery response message may include information about all the proxy service resources on the bridge device and information about the resources of the first communication protocol virtual server.
  • a bridge device can include one proxy service resource, or it can include multiple proxy service resources.
  • the proxy service resource is used to proxy a request for a resource on the first communication protocol virtual server.
  • the proxy service resource can proxy requests for all resources of the first communication protocol virtual server on the bridge device.
  • one of the proxy service resources may proxy a request for a part of the first communication protocol virtual server resource on the bridge device.
  • the proxy service resource may be created by the bridge device before leaving the factory, or it may be created by the bridge device after receiving the connection establishment request message sent by the second communication protocol device.
  • connection establishment request message may be a device registration request message.
  • the information of the proxy service resource may include URI information of the proxy service resource, and the URI of the proxy service resource is different from the device resource and the platform resource of the bridge device.
  • the URI of the proxy service resource is "/ proxyservice".
  • the URI of the proxy service resource is different from the URI of the bridge device's platform resource "/ oic / p" and also the URI of the bridge device's device resource "/ oic / d". different.
  • the information of the first communication protocol virtual server includes endpoint information, and the endpoint is the same as the endpoint of the bridge device.
  • the endpoint of the bridge device is "coap: // [fe80 :: b1d6]: 44444"
  • the endpoint of the first communication protocol virtual server is also "coap: // [fe80 :: b1d6]: 44444".
  • the information of the proxy service resource may further include at least one of the following information: the resource type and interface of the proxy service resource.
  • the resource type of the proxy service resource can be "oic.r.proxyservice”.
  • the interface of the proxy service resource can be "oic.if.a”.
  • the information of the first communication protocol virtual server may further include at least one of the following information: the URI of the platform resource of the first communication protocol virtual server, the URI of the device resource, the resource type, the interface, and the target identifier.
  • the device resource of the first communication protocol virtual server may use the same URI as the device resource of the bridge device, or may use a URI different from the URI of the device resource of the bridge device.
  • the URI of the platform resource of the first communication protocol virtual server may be the same URI as the platform resource of the bridge device, or may be a URI different from the URI of the device resource of the bridge device.
  • the first communication protocol may be an OCF protocol.
  • the first communication protocol virtual server may be an OCF virtual server, and the first communication protocol client may be an OCF client.
  • the URI of the platform resource and the device resource of the virtual OCF server can be fixed URIs.
  • the URI of the platform resource of the virtual OCF server is "/ oic / p”
  • the URI of the device resource is "/ oic / d”.
  • the URI of the platform resource and the URI of the device resource of the virtual OCF server may include device identifiers of non-OCF devices.
  • the URI of the platform resource of virtual OCF server 1 can be "/ di / light_device_id / oic / p ”
  • the URI of the device resource of the virtual OCF server 1 may be“ / di / light_device_id / oic / d ”.
  • the device identifier of the non-OCF device 2 is "/ di / oven_device_id", and the server mapped by the non-OCF device 2 on the bridge device is the virtual OCF server 2.
  • the URI of the platform resource of the virtual OCF server 2 can be "/ di / oven_device_id / oic / d ", the URI of the device resource of the virtual OCF server 2 may be” / di / oven_device_id / oic / d ".
  • the target identifier may be a device identifier of the second communication protocol device.
  • the first communication protocol client may select a second communication protocol device that it wants to operate according to the target identifier.
  • the bridge device receives a resource operation request message sent by the first communication protocol client, and the resource operation request message includes a uniform resource identifier of the platform resource of the proxy service resource and a uniform resource identifier of the device resource, and the resource operation
  • the request message also includes a target identifier, which is used to identify the second communication protocol device that the proxy service resource operates on.
  • the proxy service resource on the bridge device After the proxy service resource on the bridge device receives the resource operation request sent by the first communication protocol client, it can determine the second communication protocol that the first communication protocol client wants to operate according to the target identifier carried in the resource operation request message. device.
  • the resource operation request message further includes at least one of the following information: the URI of the device instance resource of the first communication protocol virtual server, the resource operation method, and the payload.
  • the URI of the device instance resource of the virtual OCF server can be, for example, "/ myLightSwitch” or "/ myOven".
  • the URI of the device instance resource of the virtual OCF server may further include the device identifier of the non-OCF device, and the device identifier of the non-OCF device 1 is "light_device_id", then the URI of the device instance resource of the virtual OCF server 1 is "/ di / light_device_id / myLightSwitch ".
  • the device identifier of the non-OCF device 2 is "oven_device_id"
  • the URI of the device instance resource of the virtual OCF server 2 is "/ di / oven_device_id / myOven”.
  • the resource operation method may include at least one of the following methods: creating a resource, reading a resource, updating a resource, and deleting a resource.
  • Payload refers to the operational data on the resource.
  • the payload “payload” can be ⁇ "value”: true ⁇ , or the payload can be ⁇ value “: false ⁇ .
  • the operation indicated by the payload is" true “, it means that the light is turned on.
  • the operation indicated by the load is "false”, the light is turned off.
  • the load “payload” may be ⁇ "setvalue”: 25 ⁇ , and the operation indicated by the load may indicate that the temperature is adjusted to 25 ° C.
  • the bridge device converts the resource operation request message into a protocol message of the second communication protocol device.
  • the bridge device sends the converted protocol message to the second communication protocol device.
  • the bridge device may convert the resource operation request message into a protocol message of the second communication protocol device, and send the converted protocol message to the second communication protocol device.
  • the protocol message may also be a device instruction of the second communication protocol device.
  • the target identifier may be a device identifier of the second communication protocol device.
  • the device identifier of the non-OCF device 1 is "light_device_id”
  • the device identifier of the non-OCF device 2 is "oven_device_id”.
  • the server mapped from the non-OCF device 1 on the bridge device is the virtual OCF server 1
  • the server mapped from the non-OCF device 2 on the bridge device is the virtual OCF server 2.
  • the proxy service resource can proxy requests for resources on the virtual OCF server 1 and the virtual OCF server 2.
  • the target identifier included in the resource operation request message is "light_device_id"
  • the target identifier included in the resource operation request message is "light_device_id”
  • the bridge device may convert the operation request message into a device instruction of the non-OCF device 1 and send it to the non-OCF device 1.
  • the target identifier included in the resource operation request message is "oven_device_id"
  • the bridge device may convert the operation request message into a device instruction of the non-OCF device 2 and send it to the non-OCF device 2.
  • the target identifier can also be the URI of the device instance resource.
  • the endpoints of all virtual server ends on the bridge device are the same as the endpoints of the bridge device, and the number of endpoints on the bridge device will be reduced, which can reduce the maintenance cost of the bridge device to the endpoint.
  • the URI of the proxy service resource is different from the URI of the platform resource of the bridging device and the URI of the device resource.
  • the client can send a request message to the proxy service resource and carry the target identifier in the request message to identify the device requesting the proxy operation. In this way, the client can operate the resources on the virtual server through proxy service resources.
  • the number of endpoints in the bridge device can be reduced, and thus the communication complexity of the bridge device can be reduced.
  • the endpoint is used for transmission at the network layer.
  • the endpoint is related to the communication channel. After the endpoint on the bridge device is reduced, the communication channel between the client and the bridge device established by the bridge device will be reduced.
  • the reduction of the communication channel can reduce resources Overhead, reducing the complexity of the network layer. And the bridge device only needs to maintain one communication channel, so that the communication complexity of the bridge device can be reduced.
  • the information of the first communication protocol virtual server may be created by the bridge device, or may be obtained by the bridge device from other devices.
  • the information of the proxy service resource may be created by the bridge device, or may be obtained by the bridge device from other devices.
  • the method further includes: the bridge device receives a device registration request message sent by the second communication protocol device, and the bridge device creates a first communication protocol virtual server for the second communication protocol device.
  • the device registration request message may include a device identifier of the second communication protocol device.
  • the bridge device may create a first communication protocol virtual server for the second communication protocol device, and the endpoint of the first communication protocol virtual server is the same as the endpoint of the bridge device.
  • the bridge device may create a proxy service resource for the second communication protocol device after receiving the registration request message sent by the device of the second communication protocol device, and the proxy service resource can proxy the second communication protocol device. Operation request.
  • FIG. 6 is a schematic flowchart of another bridge communication method according to an embodiment of the present application.
  • the method of FIG. 6 includes steps S610-S630.
  • the first communication protocol client sends a resource discovery request message to the bridge device.
  • the resource discovery request message is mainly used to discover resources on the bridge device.
  • the first communication protocol client may mean that the client can communicate with the bridge device through the first communication protocol.
  • the client can be a client in the Internet of Things.
  • the first communication protocol may be a communication protocol in the Internet of Things.
  • the first communication protocol may be an OCF protocol.
  • the first communication protocol client receives a resource discovery response message sent by the bridge device.
  • the resource discovery response message includes information of the proxy service resource and information of the first communication protocol virtual server.
  • the endpoint of the first communication protocol virtual server is the same as the endpoint of the bridge device, the uniform resource identifier of the proxy service resource, the uniform resource identifier of the platform resource of the bridge device, and the uniform resource of the device resource
  • the identifiers are all different.
  • the first communication protocol virtual server may be a server mapped by the second communication protocol device on the bridge device, and the first communication protocol is different from the second communication protocol.
  • the embodiment of the present application does not specifically limit the first communication protocol and the second communication protocol, as long as the first communication protocol and the second communication protocol are two different protocols.
  • the first communication protocol is the zigbee protocol
  • the second communication protocol is the Bluetooth protocol.
  • the first communication protocol may be an OCF protocol
  • the second communication protocol may be a non-OCF protocol. That is, the first communication protocol client may be an OCF client, the second communication protocol device may be a non-OCF device, and the first communication protocol virtual server may be a virtual OCF server.
  • the non-OCF protocol may be zigbee, z-wave, or Bluetooth.
  • the resource discovery response message may include information about all the proxy service resources on the bridge device and information about the resources of the first communication protocol virtual server.
  • a bridge device can include one proxy service resource, or it can include multiple proxy service resources.
  • the proxy service resource is used to proxy a request for a resource on the first communication protocol virtual server.
  • the proxy service resource can proxy requests for all resources of the first communication protocol virtual server on the bridge device.
  • one of the proxy service resources may proxy a request for a part of the first communication protocol virtual server resource on the bridge device.
  • the proxy service resource may be created by the bridge device before leaving the factory, or it may be created by the bridge device after receiving the connection establishment request message sent by the second communication protocol device.
  • connection establishment request message may be a device registration request message.
  • the information of the proxy service resource includes the URI information of the proxy service resource.
  • the URI of the proxy service resource is different from the device resource and the platform resource of the bridge device.
  • the URI of the proxy service resource is "/ proxyservice".
  • the URI of the proxy service resource is different from the URI of the bridge device's platform resource "/ oic / p" and also the URI of the bridge device's device resource "/ oic / d". different.
  • the information of the first communication protocol virtual server includes endpoint information, and the endpoint is the same as the endpoint of the bridge device.
  • the information of the first communication protocol virtual server includes the endpoint information of the first communication protocol virtual server. For example, when the endpoint of the bridge device is "coap: // [fe80 :: b1d6]: 44444", the information of the first communication protocol virtual server is The endpoint is also "coap: // [fe80 :: b1d6]: 44444".
  • the information of the proxy service resource may further include at least one of the following information: the resource type and interface of the proxy service resource.
  • the resource type of the proxy service resource can be "oic.r.proxyservice”.
  • the interface of the proxy service resource can be "oic.if.a”.
  • the information of the first communication protocol virtual server may further include at least one of the following information: the URI of the platform resource of the first communication protocol virtual server, the URI of the device resource, the resource type, the interface, and the target identifier.
  • the device resource of the first communication protocol virtual server may use the same URI as the device resource of the bridge device, or may use a URI different from the URI of the device resource of the bridge device.
  • the URI of the platform resource of the first communication protocol virtual server may be the same URI as the platform resource of the bridge device, or may be a URI different from the URI of the device resource of the bridge device.
  • the first communication protocol may be an OCF protocol.
  • the first communication protocol virtual server may be an OCF virtual server, and the first communication protocol client may be an OCF client.
  • the URI of the platform resource and the device resource of the virtual OCF server can be fixed URIs.
  • the URI of the platform resource of the virtual OCF server is "/ oic / p”
  • the URI of the device resource is "/ oic / d”.
  • the URI of the platform resource and the URI of the device resource of the virtual OCF server may include device identifiers of non-OCF devices.
  • the URI of the platform resource of virtual OCF server 1 can be "/ di / light_device_id / oic / p ”
  • the URI of the device resource of the virtual OCF server 1 may be“ / di / light_device_id / oic / d ”.
  • the device identifier of the non-OCF device 2 is "/ di / oven_device_id", and the server mapped by the non-OCF device 2 on the bridge device is the virtual OCF server 2.
  • the URI of the platform resource of the virtual OCF server 2 can be "/ di / oven_device_id / oic / d ", the URI of the device resource of the virtual OCF server 2 may be” / di / oven_device_id / oic / d ".
  • the target identifier may be a device identifier of the second communication protocol device.
  • the first communication protocol client may select a second communication protocol device that it wants to operate according to the target identifier.
  • the first communication protocol client sends a resource operation request message to the bridge device.
  • the resource operation request message includes the URI of the platform resource of the proxy service resource and the URI of the device resource.
  • the resource operation request message further includes the target identifier. The target identifier is used to identify a second communication protocol device that the proxy service resource operates on.
  • the first communication protocol client After the first communication protocol client receives the resource response message, it may select the second communication protocol device that it wants to operate, add the target identifier of the second communication protocol device to the resource operation request message, and provide the The proxy service resource sends the resource operation request message.
  • the device identifier of non-OCF device 1 is "light_device_id”
  • the device identifier of non-OCF device 2 is "oven_device_id”.
  • the server mapped from the non-OCF device 1 on the bridge device is the virtual OCF server 1
  • the server mapped from the non-OCF device 2 on the bridge device is the virtual OCF server 2.
  • the proxy service resource can proxy requests for resources on the virtual OCF server 1 and the virtual OCF server 2.
  • the OCF client When the OCF client wants to perform a resource operation on the non-OCF device 1, it may send a resource operation request message to the proxy service resource.
  • the target identifier included in the resource operation request message may be "light_device_id".
  • the OCF client When the OCF client wants to perform resource operations on the non-OCF device 2, it may send a resource operation request message to the proxy service resource.
  • the target identifier included in the resource operation request message may be "light_device_id".
  • the target identifier can also be the URI of the device instance resource.
  • the endpoints of all the first communication protocol virtual server ends on the bridge device are the same as the endpoints of the bridge device, and the number of endpoints on the bridge device will be reduced, which can reduce the maintenance cost of the bridge device to the endpoint.
  • the URI of the proxy service resource is different from the URI of the platform resource of the bridge device and the URI of the device resource.
  • the first communication protocol client can send a request message to the proxy service resource, and the target message is carried in the request message to identify the requesting proxy. Operating second communication protocol device. In this way, the first communication protocol client can operate the resources on the first communication protocol virtual server through proxy service resources.
  • the number of endpoints in the bridge device can be reduced, and thus the communication complexity of the bridge device can be reduced.
  • the endpoint is used for transmission at the network layer.
  • the endpoint is related to the communication channel. After the endpoint on the bridge device is reduced, the communication channel between the client and the bridge device established by the bridge device will be reduced.
  • the reduction of the communication channel can reduce resources Overhead, reducing the complexity of the network layer. And the bridge device only needs to maintain one communication channel, so that the communication complexity of the bridge device can be reduced.
  • FIG. 7 is a schematic flowchart of another bridge device communication method according to an embodiment of the present application.
  • the method of FIG. 7 includes steps S710-S720.
  • the method in FIG. 7 can be used in combination with the methods in FIGS. 5 and 6.
  • the method in FIG. 7 refer to the descriptions in the methods in FIG. 5 and FIG. 6 above.
  • the bridge device receives a device registration request message sent by the second communication protocol device.
  • the device registration request message may also be a connection establishment request message.
  • connection establishment request message may include a device identifier of the second communication protocol device.
  • the bridge device creates a first communication protocol virtual server and a proxy service resource for the second communication protocol device, wherein the endpoint of the first communication protocol virtual server is the same as the endpoint of the bridge device, and
  • the uniform resource identifier of the proxy service resource is different from the uniform resource identifier of the platform resource of the bridge device and the uniform resource identifier of the device resource, and the proxy service resource is used to proxy the first communication protocol client to the first communication protocol client.
  • a communication protocol request from the virtual server is used to proxy the first communication protocol client to the first communication protocol client.
  • the bridge device creates information of the first communication protocol virtual server.
  • the information of the first communication protocol virtual server includes a uniform resource identifier of the platform resource and a uniform resource identifier of the device resource. Breaks and endpoints.
  • the bridging device creates information for creating the proxy service resource.
  • the information for creating the proxy service resource includes the uniform resource identifier of the platform resource, the uniform resource identifier of the device resource, and the endpoint.
  • FIG. 8 is a schematic block diagram of a bridge device according to an embodiment of the present application.
  • the bridge device 800 of FIG. 8 includes a communication unit 810.
  • the communication unit 810 is configured to receive a resource discovery request message sent by a first communication protocol client.
  • the communication unit 810 is further configured to send a resource discovery response message to the first communication protocol client, where the resource discovery response message includes a unified resource of a platform resource of the first communication protocol virtual server created by the bridging device.
  • the resource discovery response message includes a unified resource of a platform resource of the first communication protocol virtual server created by the bridging device.
  • Identifier, uniform resource identifier and endpoint of the device resource wherein the endpoint of the first communication protocol virtual server is the same as the endpoint of the bridge device, and the uniform resource identifier of the platform resource of the first communication protocol virtual server Different from the uniform resource identifier of the platform resource of the bridge device, the uniform resource identifier of the device resource of the first communication protocol virtual server is different from the uniform resource identifier of the device resource of the bridge device.
  • the communication unit 810 is further configured to receive a device registration request message sent by the second communication protocol device.
  • the bridge device 800 further includes a processing unit, configured to create the first communication protocol virtual server for the second communication protocol device.
  • the unified resource identifier of the platform resource and the device resource of the first communication protocol virtual server includes the device identification of the second communication protocol device.
  • the uniform resource identifier of the device instance resource of the first communication protocol virtual server includes the device identification of the second communication protocol device
  • the communication unit 810 is further configured to receive a resource sent by the first communication protocol client.
  • An operation request message where the resource operation request message includes a uniform resource identifier of a device instance resource of the first communication protocol virtual server; the processing unit is further configured to convert the resource operation request message into the second communication A protocol message of the protocol device; the communication unit 810 is further configured to send the protocol message to the second communication protocol device.
  • the first communication protocol is an OCF protocol.
  • FIG. 9 is a schematic block diagram of a first communication protocol device according to an embodiment of the present application.
  • the first communication protocol device may be, for example, an OCF device.
  • the first communication protocol device 900 of FIG. 9 includes a communication unit 910.
  • the communication unit 910 is configured to send a resource discovery request message to the bridge device.
  • the communication unit 910 is further configured to receive a resource discovery response message sent by the bridge device, where the resource discovery response message includes a platform resource of the first communication protocol virtual server created by the bridge device of the first communication protocol virtual server.
  • Uniform resource identifier, uniform resource identifier and endpoint of device resource wherein the endpoint of the first communication protocol virtual server is the same as the endpoint of the bridge device, and the unified resource of platform resources of the first communication protocol virtual server
  • the identifier is different from the uniform resource identifier of the platform resource of the bridge device, and the uniform resource identifier of the device resource of the first communication protocol virtual server is different from the uniform resource identifier of the device resource of the bridge device.
  • the unified resource identifier of the platform resource and the device resource of the first communication protocol virtual server includes the device identification of the second communication protocol device.
  • the uniform resource identifier of the device instance resource of the first communication protocol virtual server includes the device identifier of the second communication protocol device
  • the communication unit 910 is further configured to send a resource operation request message to the bridge device
  • the resource operation request message includes a uniform resource identifier of a device instance resource of the first communication protocol virtual server, and the uniform resource identifier of the device instance resource is used to identify the first communication protocol virtual server to perform The second communication protocol device in operation.
  • the first communication protocol is an OCF protocol.
  • FIG. 10 is a schematic block diagram of another bridge device according to an embodiment of the present application.
  • the bridge device 1000 of FIG. 10 includes a communication unit 1010 and a processing unit 1020.
  • the communication unit 1010 is configured to receive a device registration request message sent by a second communication protocol device.
  • a processing unit 1020 is configured to create a first communication protocol virtual server for the second communication protocol device, wherein an endpoint of the first communication protocol virtual server is the same as an endpoint of the bridge device, and the first communication protocol
  • the uniform resource identifier of the platform resource of the virtual server is different from the uniform resource identifier of the platform resource of the bridge device.
  • the uniform resource identifier of the device resource of the first communication protocol virtual server and the device resource of the bridge device are different. Uniform resource identifiers are different.
  • FIG. 11 is a schematic block diagram of another bridge device according to an embodiment of the present application.
  • the bridge device 1100 in FIG. 11 includes a communication unit 1110 and a processing unit 1120.
  • the communication unit 1110 is configured to receive a resource discovery request message sent by a first communication protocol client.
  • the communication unit 1110 is further configured to send a resource discovery response message to the first communication protocol client, where the resource discovery response message includes information of a pre-created proxy service resource and a unified platform resource of the first communication protocol virtual server.
  • the resource discovery response message includes information of a pre-created proxy service resource and a unified platform resource of the first communication protocol virtual server.
  • a resource identifier, a uniform resource identifier and an endpoint of a device resource wherein the endpoint of the first communication protocol virtual server is the same as the endpoint of the bridge device, and the uniform resource identifier of the proxy service resource is the same as the bridge device
  • the unified resource identifier of the platform resource and the unified resource identifier of the device resource are different.
  • the communication unit 1110 is further configured to receive a resource operation request message sent by the first communication protocol client to the bridge device, where the resource operation request message includes a uniform resource identifier and a platform resource of the proxy service resource and A uniform resource identifier of a device resource, and the resource operation request message further includes a target identifier, where the target identifier is used to identify a second communication protocol device on which the proxy service resource operates, the first communication protocol and the The second communication protocol is different.
  • the processing unit 1120 is configured to convert the resource operation request message into a protocol message of the second communication protocol device.
  • the communication unit 1110 is further configured to send the protocol message to the second communication protocol device.
  • the resource discovery response message further includes at least one of the following information: a resource type and an interface of the proxy service resource.
  • the resource operation request message includes at least one of the following information: a URI of a device instance resource of the first communication protocol virtual server, a resource operation method, and a payload.
  • the first communication protocol is an OCF protocol.
  • FIG. 12 is a schematic block diagram of another first communication protocol device according to an embodiment of the present application.
  • the first communication protocol device may be, for example, an OCF device.
  • the first communication protocol device 1200 of FIG. 12 includes a communication unit 1210.
  • the communication unit 1210 is configured to send a resource discovery request message to the bridge device.
  • the communication unit 1210 is further configured to receive a resource discovery response message sent by the bridge device, where the resource discovery response message includes a pre-created proxy service resource and a uniform resource identifier of the platform resource of the first communication protocol virtual server and a device.
  • the resource discovery response message includes a pre-created proxy service resource and a uniform resource identifier of the platform resource of the first communication protocol virtual server and a device.
  • a uniform resource identifier and endpoint of the resource wherein the endpoint of the first communication protocol virtual server is the same as the endpoint of the bridge device, and the uniform resource identifier of the proxy service resource is the same as the platform resource of the bridge device
  • the resource identifier and the uniform resource identifier of the device resource are different.
  • the communication unit 1210 is further configured to send a resource operation request message to the proxy service resource, where the resource operation request message includes a target identifier, and the resource operation request message includes a uniform resource identifier of a platform resource of the proxy service resource Identifier and a uniform resource identifier of a device resource, the target identifier is used to identify a second communication protocol device on which the proxy service resource operates, and the first communication protocol is different from the second communication protocol.
  • the resource discovery response message further includes at least one of the following information: a resource type and an interface of the proxy service resource.
  • the resource operation request message includes at least one of the following information: a URI of a device instance resource of the first communication protocol virtual server, a resource operation method, and a payload.
  • the first communication protocol may be an OCF protocol.
  • FIG. 13 is a schematic block diagram of another bridge device according to an embodiment of the present application.
  • the bridge device 1300 of FIG. 13 includes a communication unit 1310 and a processing unit 1320.
  • the communication unit 1310 is configured to receive a device registration request message sent by a second communication protocol device.
  • a processing unit 1320 configured to create a first communication protocol virtual server and a proxy service resource for the second communication protocol device, wherein an endpoint of the first communication protocol virtual server is the same as an endpoint of the bridge device, and The uniform resource identifier of the proxy service resource is different from the uniform resource identifier of the platform resource of the bridge device and the uniform resource identifier of the device resource, and the proxy service resource is used to proxy the first communication protocol client to the first communication protocol client.
  • FIG. 14 is a schematic structural diagram of a communication device 1400 according to an embodiment of the present application.
  • the communication device 1400 shown in FIG. 14 includes a processor 1410, and the processor 1410 can call and run a computer program from a memory to implement the method in the embodiment of the present application.
  • the communication device 1400 may further include a memory 1420.
  • the processor 1410 may call and run a computer program from the memory 1420 to implement the method in the embodiment of the present application.
  • the memory 1420 may be a separate device independent of the processor 1410, or may be integrated in the processor 1410.
  • the communication device 1400 may further include a transceiver 1430, and the processor 1410 may control the transceiver 1430 to communicate with other devices, and specifically, may send information or data to other devices, or receive other Information or data sent by the device.
  • the processor 1410 may control the transceiver 1430 to communicate with other devices, and specifically, may send information or data to other devices, or receive other Information or data sent by the device.
  • the transceiver 1430 may include a transmitter and a receiver.
  • the transceiver 1430 may further include an antenna, and the number of antennas may be one or more.
  • the communication device 1400 may specifically be a network device according to an embodiment of the present application, and the communication device 1400 may implement a corresponding process implemented by a network device in each method of the embodiments of the present application. .
  • the communication device 1400 may specifically be a mobile terminal / terminal device in the embodiment of the present application, and the communication device 1400 may implement a corresponding process implemented by the mobile terminal / terminal device in each method in the embodiments of the present application, for the sake of simplicity , Will not repeat them here.
  • FIG. 15 is a schematic structural diagram of a chip according to an embodiment of the present application.
  • the chip 1500 shown in FIG. 15 includes a processor 1510, and the processor 1510 can call and run a computer program from a memory to implement the method in the embodiment of the present application.
  • the chip 1500 may further include a memory 1520.
  • the processor 1510 may call and run a computer program from the memory 1520 to implement the method in the embodiment of the present application.
  • the memory 1520 may be a separate device independent of the processor 1510, or may be integrated in the processor 1510.
  • the chip 1500 may further include an input interface 1530.
  • the processor 1510 may control the input interface 1530 to communicate with other devices or chips. Specifically, the processor 1510 may obtain information or data sent by other devices or chips.
  • the chip 1500 may further include an output interface 1540.
  • the processor 1510 may control the output interface 1540 to communicate with other devices or chips. Specifically, the processor 1510 may output information or data to the other devices or chips.
  • the chip may be applied to the network device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the chip may be applied to the network device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the chip can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the chip can implement the corresponding process implemented by the mobile terminal / terminal device in each method of the embodiments of the present application. For simplicity, here No longer.
  • the chip mentioned in the embodiments of the present application may also be referred to as a system-level chip, a system chip, a chip system or a system-on-chip.
  • FIG. 16 is a schematic block diagram of a communication system 1600 according to an embodiment of the present application. As shown in FIG. 16, the communication system 1600 includes a bridge device 1610 and a first communication protocol device 1620.
  • the bridging device 1610 may be used to implement the corresponding functions implemented by the bridging device in the above method, and the first communication protocol device 1620 may be used to implement the corresponding functions implemented by the device in the above method. More details.
  • the processor in the embodiment of the present application may be an integrated circuit chip and has a signal processing capability.
  • each step of the foregoing method embodiment may be completed by using an integrated logic circuit of hardware in a processor or an instruction in a form of software.
  • the above processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (Field, Programmable Gate Array, FPGA), or other Programming logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA off-the-shelf programmable gate array
  • Various methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the steps of the method disclosed in combination with the embodiments of the present application may be directly implemented by a hardware decoding processor, or may be performed by using a combination of hardware and software modules in the decoding processor.
  • the software module may be located in a mature storage medium such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, and the like.
  • the storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the foregoing method in combination with its hardware.
  • the memory in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), and an electronic memory. Erase programmable read-only memory (EPROM, EEPROM) or flash memory.
  • the volatile memory may be Random Access Memory (RAM), which is used as an external cache.
  • RAM Static Random Access Memory
  • DRAM Dynamic Random Access Memory
  • Synchronous Dynamic Random Access Memory Synchronous Dynamic Random Access Memory
  • SDRAM double data rate synchronous dynamic random access memory
  • Double SDRAM, DDR SDRAM enhanced synchronous dynamic random access memory
  • Enhanced SDRAM, ESDRAM synchronous connection dynamic random access memory
  • Synchronous DRAM Synchronous Dynamic Random Access Memory
  • Enhanced SDRAM Enhanced SDRAM, ESDRAM
  • synchronous connection dynamic random access memory Synchrobus RAM, SLDRAM
  • Direct Rambus RAM Direct Rambus RAM
  • the memory in the embodiment of the present application may also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (Double SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct RAMbus RAM, DR RAM) and so on. That is, the memories in the embodiments of the present application are intended to include, but not limited to, these and any other suitable types of memories.
  • An embodiment of the present application further provides a computer-readable storage medium for storing a computer program.
  • the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the network device in each method in the embodiment of the present application. For simplicity, here No longer.
  • the computer-readable storage medium may be applied to the mobile terminal / terminal device in the embodiment of the present application, and the computer program causes the computer to execute a corresponding process implemented by the mobile terminal / terminal device in each method in the embodiment of the present application.
  • the computer program causes the computer to execute a corresponding process implemented by the mobile terminal / terminal device in each method in the embodiment of the present application.
  • An embodiment of the present application further provides a computer program product, including computer program instructions.
  • the computer program product can be applied to the network device in the embodiment of the present application, and the computer program instruction causes the computer to execute a corresponding process implemented by the network device in each method in the embodiment of the present application. More details.
  • the computer program product can be applied to a mobile terminal / terminal device in the embodiments of the present application, and the computer program instructions cause the computer to execute a corresponding process implemented by the mobile terminal / terminal device in each method in the embodiments of the present application
  • the computer program instructions cause the computer to execute a corresponding process implemented by the mobile terminal / terminal device in each method in the embodiments of the present application
  • I will not repeat them here.
  • the embodiment of the present application also provides a computer program.
  • the computer program may be applied to a network device in the embodiment of the present application.
  • the computer program When the computer program is run on a computer, the computer is caused to execute a corresponding process implemented by the network device in each method in the embodiment of the present application. , Will not repeat them here.
  • the computer program may be applied to a mobile terminal / terminal device in the embodiment of the present application.
  • the computer program When the computer program is run on a computer, the computer executes each method in the embodiment of the application by the mobile terminal / terminal device. The corresponding processes are not repeated here for brevity.
  • the disclosed systems, devices, and methods may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the unit is only a logical function division.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, which may be electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objective of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each of the units may exist separately physically, or two or more units may be integrated into one unit.
  • the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of this application is essentially a part that contributes to the existing technology or a part of the technical solution can be embodied in the form of a software product.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in the embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory) ROM, random access memory (Random Access Memory, RAM), magnetic disks or optical disks and other media that can store program codes .

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • Computer And Data Communications (AREA)

Abstract

La présente invention concerne, selon des modes de réalisation, un procédé et un dispositif de communication de pontage, qui peuvent réduire le nombre de points d'extrémité dans un dispositif de pontage et réduire la complexité de la communication de pontage de dispositif. Ledit procédé comprend les étapes suivantes : le dispositif de pontage reçoit un message de requête de découverte de ressources envoyé par un premier client de protocole de communication ; le dispositif de pontage envoie un message de réponse de découverte de ressources au premier client de protocole de communication, le message de réponse de découverte de ressources comprenant des informations concernant un premier serveur virtuel de protocole de communication, le point d'extrémité du premier serveur virtuel de protocole de communication étant le même que le point d'extrémité du dispositif de pontage, l'identifiant de ressource uniforme d'une ressource de plateforme du premier serveur virtuel de protocole de communication étant différent de l'identifiant de ressource uniforme d'une ressource de plateforme du dispositif de pontage, et l'identifiant de ressource uniforme d'une ressource de dispositif du premier serveur virtuel de protocole de communication étant différent de l'identifiant de ressource uniforme d'une ressource de dispositif du dispositif de pontage.
PCT/CN2019/102039 2018-08-24 2019-08-22 Procédé et dispositif de communication de pontage WO2020038443A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810974172.7A CN110858838B (zh) 2018-08-24 2018-08-24 桥接通信的方法和设备
CN201810974172.7 2018-08-24

Publications (1)

Publication Number Publication Date
WO2020038443A1 true WO2020038443A1 (fr) 2020-02-27

Family

ID=69592820

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/102039 WO2020038443A1 (fr) 2018-08-24 2019-08-22 Procédé et dispositif de communication de pontage

Country Status (2)

Country Link
CN (1) CN110858838B (fr)
WO (1) WO2020038443A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022247525A1 (fr) * 2021-05-28 2022-12-01 杭州萤石软件有限公司 Procédé de gestion de dispositif de l'internet des objets, et procédé de réglage de ressource de dispositif dans un dispositif de l'internet des objets

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111885103B (zh) * 2020-06-12 2024-05-14 视联动力信息技术股份有限公司 资源处理方法、服务器、电子设备及存储介质
CN115486038B (zh) * 2020-07-14 2024-05-03 Oppo广东移动通信有限公司 物联网配置方法、装置、计算机设备及存储介质
KR102628107B1 (ko) * 2020-12-29 2024-01-23 에이치디씨랩스 주식회사 Ocf 기반의 프로토콜 및 레거시 프로토콜을 병용하는 월패드 장치 및 방법

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102186164A (zh) * 2011-02-18 2011-09-14 华为技术有限公司 操作设备资源的方法和管理装置
CN107046537A (zh) * 2017-04-01 2017-08-15 上海润欣科技股份有限公司 一种基于DNS‑SD的OCF客户端对AllJoyn服务的发现方法
US20180063879A1 (en) * 2016-08-29 2018-03-01 Electronics And Telecommunications Research Institute Apparatus and method for interoperation between internet-of-things devices

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104904165B (zh) * 2013-01-04 2018-02-16 日本电气株式会社 控制装置、通信系统以及隧道端点的控制方法
NO341411B1 (no) * 2013-03-04 2017-10-30 Cisco Tech Inc Virtuelle endepunkter i videokonferanser
US10623240B2 (en) * 2016-08-25 2020-04-14 Intel Corporation IoT solution sizing
US10904824B2 (en) * 2016-09-02 2021-01-26 Intel Corporation Virtual private network

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102186164A (zh) * 2011-02-18 2011-09-14 华为技术有限公司 操作设备资源的方法和管理装置
US20180063879A1 (en) * 2016-08-29 2018-03-01 Electronics And Telecommunications Research Institute Apparatus and method for interoperation between internet-of-things devices
CN107046537A (zh) * 2017-04-01 2017-08-15 上海润欣科技股份有限公司 一种基于DNS‑SD的OCF客户端对AllJoyn服务的发现方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
OCF BRIDGING SPECIFICATION, 31 December 2016 (2016-12-31) *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022247525A1 (fr) * 2021-05-28 2022-12-01 杭州萤石软件有限公司 Procédé de gestion de dispositif de l'internet des objets, et procédé de réglage de ressource de dispositif dans un dispositif de l'internet des objets

Also Published As

Publication number Publication date
CN110858838A (zh) 2020-03-03
CN110858838B (zh) 2021-03-09

Similar Documents

Publication Publication Date Title
WO2020038443A1 (fr) Procédé et dispositif de communication de pontage
US8767737B2 (en) Data center network system and packet forwarding method thereof
US11811899B2 (en) IPv4/IPv6 bridge
WO2017148308A1 (fr) Procédé, appareil et système servant à accéder à un réseau par un dispositif de l'internet des objets
CN112398817B (zh) 数据发送的方法及设备
US7836164B2 (en) Extensible network discovery subsystem
US20130346591A1 (en) Clientless Cloud Computing
US9548923B2 (en) System and method for utilizing a unique identifier while registering a device in a network
KR20140012673A (ko) Ｎｆｃ 피어 투 피어 통신 환경에서 인터넷 프로토콜(ｉｐ) 데이터 통신을 제공하는 방법 및 시스템
US10499311B2 (en) Method and apparatus for implementing network sharing
US8472420B2 (en) Gateway device
US11799827B2 (en) Intelligently routing a response packet along a same connection as a request packet
WO2016086659A1 (fr) Procédé, dispositif et système de transmission de messages de service
JP2017208797A (ja) 不均一ネットワークにまたがる統合されたデータ・ネットワーキング
CN111107119A (zh) 基于云存储系统的数据访问方法、装置、系统及存储介质
JP2011229093A (ja) ネットワーク装置
CN110430478B (zh) 组网通信方法、装置、终端设备及存储介质
US20230045914A1 (en) Method and apparatus for controlling device in internet of things, and gateway device and storage medium
US11750716B2 (en) Methods for publishing resource, and gateway
JP2015170041A (ja) 通信装置、通信システム、通信方法およびプログラム
WO2017054733A1 (fr) Procédé et dispositif de traitement pour un hébergement et une commutation de stockage
US10091637B2 (en) Providing information to a service in a communication network
WO2024001549A1 (fr) Procédé de configuration d'adresse et dispositif électronique
JP6539497B2 (ja) 通信中継システム、デバイス収容端末、サーバ側コンピュータ、プログラム、及び通信中継方法
WO2016106598A1 (fr) Procédé et appareil de sélection de réseau d'accès

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

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

Country of ref document: EP

Kind code of ref document: A1