CN110858838A

CN110858838A - Method and apparatus for bridging communications

Info

Publication number: CN110858838A
Application number: CN201810974172.7A
Authority: CN
Inventors: 唐海
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2018-08-24
Filing date: 2018-08-24
Publication date: 2020-03-03
Anticipated expiration: 2038-08-24
Also published as: WO2020038443A1; CN110858838B

Abstract

The embodiment of the application provides a method and equipment for bridging communication, which can reduce the number of endpoints in bridging equipment and reduce the complexity of bridging communication of the equipment. The method comprises the following steps: the method comprises the steps that bridging equipment receives a resource discovery request message sent by a first communication protocol client; the bridge device sends a resource discovery response message to the first communication protocol client, wherein the resource discovery response message includes information of the first communication protocol virtual server, an endpoint of the first communication protocol virtual server is the same as an endpoint of the bridge device, a uniform resource identifier of a platform resource of the first communication protocol virtual server is different from a uniform resource identifier of a platform resource of the bridge device, and a uniform resource identifier of a device resource of the first communication protocol virtual server is different from a uniform resource identifier of a device resource of the bridge device.

Description

Method and apparatus for bridging communications

Technical Field

Embodiments of the present invention relate to the field, and in particular, to a method and an apparatus for bridging communication.

Background

With the development of technology, the internet of things has attracted wide attention worldwide as one of the important directions for the development of the future information network field. However, different manufacturers use different ecological chain protocols at present, so that products produced by different manufacturers cannot communicate with each other, and real object interconnection cannot be achieved.

The bridging device can realize conversion between different protocols, so that communication between devices adopting different protocols can be realized. Taking an Open Connectivity Foundation (OCF) device as an example, the bridge device may create a virtual OCF service end for the OCF device, so that the OCF client may communicate with the virtual OCF service end through an OCF protocol, and the virtual OCF service end may communicate with a non-OCF device through a non-OCF protocol, so as to implement communication between the OCF device and the non-OCF device.

At present, communication systems have higher and higher requirements for communication, and how to reduce communication complexity of a bridge device in a process of realizing communication between devices of two different protocols becomes an urgent problem to be solved.

Disclosure of Invention

The embodiment of the invention provides a method and a device for reducing the number of endpoints in bridging equipment and reducing the complexity of bridging communication of the equipment.

In a first aspect, a method for bridging communication is provided, including: the method comprises the steps that bridging equipment receives a resource discovery request message sent by a first communication protocol client; the bridge device sends a resource discovery response message to the first communication protocol client, where 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 a device resource, and an endpoint, where 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 platform resource of the first communication protocol virtual server 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.

In a second aspect, a method of bridging communications is provided, 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, where 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 a device resource, and an endpoint, where 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 platform resource of the first communication protocol virtual server 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.

In a third aspect, a method for bridging communication is provided, including: the bridging device receives a device registration request message sent by the second communication protocol device; the bridge device creates 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, a uniform resource identifier of a platform resource of the first communication protocol virtual server is different from a uniform resource identifier of a platform resource of the bridge device, and a uniform resource identifier of a device resource of the first communication protocol virtual server is different from a uniform resource identifier of a device resource of the bridge device.

In a fourth aspect, a method of bridging communications is provided, comprising: the method comprises the steps that bridging equipment receives a resource discovery request message sent by a first communication protocol client; the bridge device sends a resource discovery response message to the first communication protocol client, wherein the resource discovery response message comprises pre-created proxy service resources and information of a first communication protocol virtual server, and the pre-created proxy service resources and the information of the first communication protocol virtual server comprise a uniform resource identifier of a platform resource, a uniform resource identifier of a device resource and an endpoint, 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 resources is different from the uniform resource identifier of the platform resource of the bridge device and the uniform resource identifier of the device resource; the bridge device receives a resource operation request message sent by the first communication protocol client, wherein the resource operation request message comprises a uniform resource identifier of a platform resource of the proxy service resource and a uniform resource identifier of a device resource, and the resource operation request message also comprises a target identifier, and the target identifier is used for identifying a second communication protocol device operated by the proxy service resource; the bridging device converts the resource operation request message into a protocol message of the second communication protocol device; the bridge device sends the protocol message to the second communication protocol device.

In a fifth aspect, a method for bridging communications is provided, 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, wherein the resource discovery response message comprises pre-created proxy service resources and information of a first communication protocol virtual service end, and the pre-created proxy service resources and the information of the first communication protocol virtual service end comprise uniform resource identifiers of platform resources, uniform resource identifiers of device resources and end points, wherein the end points of the first communication protocol virtual service end are the same as the end points of the bridge device, and the uniform resource identifiers of the proxy service resources are different from the uniform resource identifiers of the platform resources and the uniform resource identifiers of the device resources of the bridge device; the first communication protocol client sends a resource operation request message to the bridge device, wherein the resource operation request message includes a uniform resource identifier of a platform resource of the proxy service resource and a uniform resource identifier of a device resource, and the resource operation request message also includes a target identifier, and the target identifier is used for identifying a second communication protocol device operated by the proxy service resource.

In a sixth aspect, a method of bridging communications is provided, comprising: the bridging device receives a device registration request message sent by 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 an endpoint of the first communication protocol virtual server is the same as an endpoint of the bridge device, a uniform resource identifier of the proxy service resource is different from a uniform resource identifier of a platform resource of the bridge device and a uniform resource identifier of a device resource, and the proxy service resource is used for proxying a request of a first communication protocol client to the first communication protocol virtual server.

A seventh aspect provides a bridging device, configured to perform the method in any optional implementation manner of the first aspect or the third aspect. In particular, the bridging device comprises functional modules for performing the method described in any of the optional implementations of the first, third, fourth or sixth aspect above.

In an eighth aspect, a first communication protocol device is provided, which is configured to perform the method described in any optional implementation manner of the second aspect or the fourth aspect. In particular, the bridging device comprises functional modules for performing the method described in any of the optional implementations of the second or fifth aspect above.

In a ninth aspect, a bridging device is provided that includes a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory, and executing the method in each implementation manner in the first aspect, the third aspect, the fourth aspect, or the sixth aspect.

In a tenth aspect, a first communication protocol device is provided that includes a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory to execute the method in each implementation manner in the second aspect or the fifth aspect.

In an eleventh aspect, a chip is provided for implementing the method in any possible implementation manner of the first or third aspect. In particular, the chip comprises a processor for calling and running a computer program from a memory, such that a device in which the chip is installed performs the method of any possible implementation of the above first, third, fourth or sixth aspect.

In a twelfth aspect, a chip is provided for implementing the method in any possible implementation manner of the second or fourth aspect. In particular, the chip comprises a processor for calling and running a computer program from a memory, such that a device in which the chip is installed performs the method of any possible implementation manner as described above in the second or fifth aspect.

In a thirteenth aspect, a computer-readable storage medium is provided for storing a computer program for causing a computer to perform the method of any possible implementation manner of the first, third, fourth or sixth aspect.

In a fourteenth aspect, a computer-readable storage medium is provided for storing a computer program, which causes a computer to execute the method in any possible implementation manner of the second or fifth aspect.

In a fifteenth aspect, a computer program product is provided, comprising computer program instructions to cause a computer to perform the method of any possible implementation of the first, third, fourth or sixth aspect described above.

In a sixteenth aspect, there is provided a computer program product comprising computer program instructions for causing a computer to perform the method of any possible implementation of the second or fifth aspect.

A seventeenth aspect provides a computer program that, when run on a computer, causes the computer to perform the method of any possible implementation of the first, third, fourth or sixth aspect described above.

In an eighteenth aspect, there is provided a computer program which, when run on a computer, causes the computer to perform the method of any possible implementation of the second or fifth aspect described above.

According to the technical scheme, the endpoints of all the virtual servers on the bridge device are the same as those of the bridge device, and compared with the traditional scheme, the number of the endpoints on the bridge device is reduced, so that the maintenance cost of the bridge device for the endpoints can be reduced. In order to distinguish different platform resources and device resources, the platform resources and the device resources of the virtual server do not use fixed uniform resource identifiers, but the uniform resource identifiers of the platform resources of the virtual server and the uniform resource identifiers of the platform resources of the bridge device are set to be different, and the uniform resource identifiers of the device resources of the virtual server and the uniform resource identifiers of the device resources of the bridge device are set to be different.

The end points are related to the communication channels, after the end points are reduced, the communication channels between the client side and the bridging device, which are established by the bridging device, are reduced, the expense of resources can be reduced due to the reduction of the communication channels, and the bridging device only needs to maintain one communication channel, so that the communication complexity of the bridging device can be reduced.

Drawings

Fig. 1 is a schematic diagram of a bridge device and an OCF device according to an embodiment of the present disclosure.

Fig. 2 is a schematic flow chart of a method for bridging communications according to an embodiment of the present application.

Fig. 3 is a schematic flow chart of another method for bridging communications according to an embodiment of the present application.

Fig. 4 is a schematic flow chart of another method for bridging communications according to an embodiment of the present application.

Fig. 5 is a schematic flow chart of another method for bridging communications according to an embodiment of the present application.

Fig. 6 is a schematic flow chart of another method for bridging communications according to an embodiment of the present application.

Fig. 7 is a schematic flow chart of another method for bridging communications according to an embodiment of the present application.

Fig. 8 is a schematic block diagram of a bridging device provided in 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 provided in an embodiment of the present application.

Fig. 11 is a schematic block diagram of another bridge device provided in an embodiment of the present application.

Fig. 12 is a schematic block diagram of another first communication protocol device provided in an embodiment of the present application.

Fig. 13 is a schematic block diagram of another bridge device provided in 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 provided in 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.

Detailed Description

The technical solution in the embodiments of the present invention will be described below with reference to the accompanying drawings.

With the development of technology, the internet of things has attracted wide attention worldwide as one of the important directions for the development of the future information network field. However, different manufacturers use different ecological chain protocols (which may also be referred to as communication protocols) at present, so that products produced by different manufacturers cannot communicate with each other, and real interconnection of everything cannot be achieved.

The bridging device can realize conversion between different protocols, so that communication between devices adopting different protocols can be realized. Taking the OCF device as an example, the bridge device may create a virtual OCF server for the OCF device, so that the OCF client may communicate with the virtual OCF server through an OCF protocol, and the virtual OCF server may communicate with the non-OCF device through a non-OCF protocol, so as to implement communication between the OCF device and the non-OCF device.

The embodiment of the present application only takes the OCF protocol as an example, and the bridge device may also implement conversion between any multiple communication protocol devices. For example, the bridge device may implement communication between a restricted application protocol (CoAP) device and a bluetooth device, and may also implement communication between a wifi device and a zigbee (zigbee) device.

Optionally, the communication protocol in the embodiment of the present application may also be another protocol generated to unify the internet of things.

Alternatively, the bridge device may support communication between only two different communication protocol devices, or may simultaneously support communication between multiple different communication protocol devices.

For convenience of description, the following description will be made by taking OCF as an example.

The OCF is an emerging technical standard organization of an Internet of things application layer, and in order to realize real internet of everything, the OCF hopes to establish a uniform Internet of things standard, realize spanning different operating systems and platforms, and realize safe and reliable equipment discovery and connection mechanisms.

The OCF provides a general representation state transfer (Restful) architecture for applications, devices and platforms of the internet of things, and the Restful architecture of the OCF represents entities of the internet of things and service capabilities thereof as OCF resources. Under the restful architecture, all physical entities can be described as resources, exposed to the outside world in the form of resources, and the states of the entities are described by resource characterizations, each resource having its own Uniform Resource Identifier (URI) and interface types that can be supported. The entity providing the resources is an OCF server, and the entity accessing the resources is an OCF client. For example, the mobile application program of the smart phone for acquiring the indoor environment state data is an OCF client, and the sensor for monitoring the indoor environment state data is an OCF server. The service interaction between the OCF client and the OCF server is realized by creating, reading, updating, deleting or notifying the OCF resources through the operation methods.

Characterization of OCF resources includes: resource URI, resource type, interface, etc., as defined below.

Resource URI: and the OCF resource representation is identified by 'href' to provide the address of the OCF server side resource. The value of "href" is a specific resource URI through which the OCF client accesses the resources of the OCF server.

Resource type: denoted by "rt" in the characterization of OCF resources, indicates the type of resource.

Interface: denoted by "if" in the OCF resource guarantee, provides a view of the resource and a response to the resource support.

In order to facilitate the discovery of OCF devices and resources, OCF also defines core resources that are supported by both OCF devices. The OCF core resources include platform resources and device resources, and a platform resource may include one or more OCF device instances. The platform resources are host resources of the device instance resources, and the device resources are used for describing common information of all OCF device instance resources on one platform resource.

The following describes resource characterization of platform resources and device resources:

platform resources: and providing related information of the platform to which the OCF equipment belongs, wherein the URI of the platform resource is fixed to be '/oic/p ', and the resource type of the platform resource is ' oic.

Equipment resources: and providing related information of specific OCF equipment, wherein the URI of the equipment resource is fixed to be '/oic/d ', and the resource type of the equipment resource is ' oic. The resource types of the device resources may also include one or more resource types that are related to device characteristics. For example, the resource types of the bridging device include "oic.wk.d" and "oic.d.bridge", indicating that this device supports the bridging resource type. Also for example, the resource types of the lamp include "ic.wk.d" and "ic.d.light", indicating that this device supports the resource types of the lamp.

In addition, since the OCF standard protocol uses CoAP to carry OCF messages in the transport layer, each OCF server needs to have an endpoint in order to implement communication between an OCF client and an OCF server. Each OCF device must associate at least one endpoint for sending and receiving messages. The endpoints may be understood as communication addresses of communication protocols used for exchanging messages by OCF devices. For example, for the CoAP protocol, the endpoints may be IP addresses and UDP port numbers.

The OCF client may send a resource operation request message to the OCF server, where the resource operation request message may carry a resource operation method, and the resource operation method may be, for example, operations such as creating a resource, reading a resource, updating a resource, and deleting a resource. The OCF server side can return a resource operation response message to the OCF client side, and the resource operation response message carries the representation of the requested resource.

At present, a plurality of non-OCF devices exist in the application of the Internet of things, and the non-OCF devices refer to the Internet of things devices which do not support an OCF standard protocol. For example, zigbee equipment, z-wave equipment, bluetooth equipment, etc. by accessing non-OCF equipment into the OCF system, communication between the non-OCF equipment and the OCF equipment can be realized, and the range of interconnection and interworking between internet of things equipment is expanded.

In order to access the OCF device into the OCF system, the OCF defines a device bridging communication mechanism, and communication between the OCF device and a non-OCF device can be realized through the OCF bridging device. The OCF bridging device can map the non-OCF device into a virtual OCF server and convert an OCF protocol and the non-OCF protocol, so that the OCF client can communicate with the non-OCF device, and further communication between the OCF device and the non-OCF device is realized.

The manner of communication between an OCF device and a non-OCF device is described below with reference to fig. 1.

The OCF bridging device may map the non-OCF device to the virtual OCF server 1, and map the non-OCF device to the 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 of the OCF client into a non-OCF protocol instruction and send the non-OCF protocol instruction to the non-OCF device 1 and the non-OCF device 2.

Because the platform resources and the device resources of the OCF device all adopt fixed URIs, the platform resources and the device resources of the virtual OCF server 1, the virtual OCF server 2, and the bridge device all have the same URIs. That is, the URI of the platform resource of the virtual OCF server 1 and the URI of the platform resource of the virtual OCF server 2 are both "/oic/p", and the URI of the device resource are both "/oic/d". In order to distinguish different platform resources and device resources, the virtual OCF server 1 and the virtual OCF server 2 must have their own endpoints, and the endpoints of the OCF bridge device, the virtual OCF server 1, and the virtual OCF server 2 are different. As shown in fig. 1, the endpoint of the OCF bridge device is endpoint 1, the endpoint of the virtual OCF service end 1 is endpoint 2, and the endpoint of the virtual OCF service end 2 is endpoint 3.

For example, the end point of the bridging device may be "coap:// [ fe80:: b1d 6: 44444", the end point of the virtual OCF service port 1 may be "coap:// [2001: db8: b:: c2e 5: 11111", and the end point of the virtual OCF service port 2 may be "coap:// [2001: db8: b:: c2e 5: 22222".

The resource characterization of the bridge device, the virtual OCF server 1 and the virtual OCF server 2 is described below by taking the non-OCF device 1 as a light (light) and the non-OCF device 2 as an oven (oven). The following resource characterization is merely an example and does not limit the embodiments of the present application.

The resources of the bridging device are characterized as follows:

the URI of the platform resource of the bridging device is "/oic/p", the resource type of the platform resource is "oic.wk.p", the interfaces of the platform resource are "oic.if.r" and "oic.if.baseline", and the endpoints of the platform resource are "coach:// [ fe80:: b1d 6: 44444".

The URI of the device resource of the bridging device is '/oic/d', the resource types of the device resource are 'oic.wk.d' and 'oic.d.bridge', the interfaces of the device resource are 'oic.if.r' and 'oic.if.base', and the endpoints of the device resource are 'coach:// [ fe80:: b1d 6:44444'.

The resources of the virtual OCF server 1 are characterized as follows:

the URI of the platform resource of the virtual OCF server 1 is "/oic/p", the resource type of the platform resource is "oic. wk.p", the interfaces of the platform resource are "oic. if.r" and "oic. if.baseline", and the end points of the platform resource are "coach:// [2001: db8: b:: c2e 5: 11111".

The URI of the equipment resource of the virtual OCF server 1 is "/oic/d", the resource types of the equipment resource are "oic.wk.d" and "oic.d.light", the interfaces of the equipment resource are "oic.if.r" and "oic.if.baseline", and the end point of the equipment resource is "coach:// [2001: db8: b:: c2e 5: 11111".

The URI of the device instance resource of the virtual OCF server 1 is "/myLightSwitch", the resource type of the device instance resource is "oic.r.switch.binary", the interfaces of the device instance resource are "oic.if.a" and "oic.if.baseline", and the end point of the device instance resource is "coach:// [2001: db8: b:: c2e 5: 11111".

The resources of the virtual OCF server 2 are characterized as follows:

the URI of the platform resource of the virtual OCF server 2 is "/oic/p", the resource type of the platform resource is "oic. wk.p", the interfaces of the platform resource are "oic. if.r" and "oic. if.base", and the end points of the platform resource are "coach:// [2001: db8: b:: c2e 5: 22222".

The URI of the device resource of the virtual OCF service 2 is "/oic/d", the resource types of the device resource are "oic.wk.d" and "oic.d.oven", the interfaces of the device resource are "oic.if.r" and "oic.if.baseline", and the endpoints of the device resource are "coach:// [2001: db8: b:: c2e 5: 22222".

The URI of the device instance resource of the virtual OCF server 2 is "/myOven", the resource types of the device instance resource are "oic.r.switch.binary" and "oic.r.temperature", the interfaces of the device instance resource are "oic.if.a" and "oic.if.base", and the endpoints of the device instance resource are "coach:/[ 2001: db8: b:: c2e5]: 22222".

As shown in fig. 1, in the conventional scheme, in order to distinguish different platform resources and device resources, each virtual OCF server mapped on the bridge device has its own endpoint, and the endpoint of the virtual OCF server is different from that of the bridge device. When a bridge device connects a large number of non-OCF devices, the OCF bridge device needs to maintain a large number of endpoints, which results in a large cost for maintaining the endpoints. Second, endpoints are related to transport protocols, the more endpoints, the higher the communication complexity of the device. For example, for the CoAP protocol, the more endpoints, the more Internet Protocol (IP) addresses and User Datagram Protocol (UDP) port numbers are allocated, and the difficulty of sending a request message by an OCF client to be associated with a correct endpoint increases, thereby increasing the complexity of communication.

The embodiment of the application provides a method for bridging communication, which can reduce the maintenance cost of an endpoint and reduce the complexity of equipment communication.

The method for bridging communication according to 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 210-220.

In step 210, the bridging device receives a resource discovery request message sent by a first communication protocol client.

The first communication protocol client may mean that the client may communicate with the bridge device via the first communication protocol. The first communication protocol client may be a client in the internet of things.

The resource discovery request message may be used to discover all resources on the bridging device. For example, the resource discovery request message may be used to discover resource information of all virtual servers on the bridge device.

Optionally, when receiving the resource discovery request message sent by the first communication protocol client, the bridge device may send the relevant information of all the first communication protocol virtual servers on the bridge device to the first communication protocol client.

The first communication protocol and the second communication protocol are not particularly limited in this embodiment of the application, as long as the first communication protocol and the second communication protocol are two different protocols. For example, the first communication protocol may be a communication protocol in the internet of things, and the second communication protocol may be a communication protocol in a non-internet of things. As another example, the first communication protocol may be a zigbee protocol and the second communication protocol may be a Bluetooth protocol. Alternatively, the first communication protocol may be an OCF protocol and 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.

Alternatively, the non-OCF protocol may be zigbee, z-wave, Bluetooth, or the like.

When creating the first communication protocol virtual server for the second communication protocol device, the bridge device may create a platform resource, a device resource, and an endpoint for the second communication protocol device. In order to reduce the communication complexity, the bridge device may set the same endpoint for the created virtual server, and distinguish different second communication protocol devices by the difference between the URIs of the platform resource and the device resource.

The following describes resource information and endpoint information of the bridge device and the virtual OCF server, taking the first communication protocol as an OCF protocol as an example.

When the end point of the bridging device is "coach:// [ fe80:: b1d 6:: 44444", the end points of the virtual OCF service end created by the bridging device for all non-OCF devices are "coach:// [ fe80:: b1d 6:: 44444".

The URI of the platform resource of the virtual OCF server does not use fixed "/oic/p", and the equipment resource of the virtual OCF server does not use fixed "/oic/d". The virtual OCF server may use URIs of platform resources and device resources that are different from the bridge device.

For the condition of the URI of the platform resource and the device resource used by the virtual OCF server, the embodiment of the present application may not be specifically limited.

For example, the bridge device may number the created virtual OCF server, and add the number to the URIs of the platform resources and the device resources of the virtual OCF server sequentially, so that different platform resources and device resources may be distinguished by the URIs.

For another example, when the bridge device creates the virtual OCF service end for the non-OCF device, the bridge device may add the device identifier of the non-OCF device to the URI of the device resource and the platform resource of the mapped virtual OCF service end, and since different non-OCF devices have different device identifiers, different platform resources and different device resources may be distinguished by the device identifiers of the non-OCF devices.

Specifically, the device identifier of the non-OCF device 1 is "light _ device _ id", and the service end mapped by the non-OCF device 1 on the bridge device is the virtual OCF service end 1, so that the URI of the platform resource of the virtual OCF service end 1 may be "/di/light _ device _ id/oic/p", and the URI of the device resource of the virtual OCF service end 1 may be "/di/light _ device _ id/oic/d". The device identifier of the non-OCF device 2 is "/di/open _ device _ id", the service end mapped by the non-OCF device 2 on the bridge device is the virtual OCF service end 2, the URI of the platform resource of the virtual OCF service end 2 may be "/di/open _ device _ id/oic/d", and the URI of the device resource of the virtual OCF service end 2 may be "/di/open _ device _ id/oic/d".

After receiving the resource discovery request message sent by the first communication protocol client, the bridge device may send the relevant information of all the virtual servers on the bridge device to the first communication protocol client.

In step 220, the bridge device sends a resource discovery response message to the first communication protocol client, where 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 URI of a device resource of the first communication protocol virtual server.

Optionally, 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.

Taking OCF as an example, the information of the virtual OCF server includes an endpoint of the virtual OCF server, a URI of a platform resource and/or a URI of an equipment resource.

For the specific situation of the end point of the virtual OCF server, the URI of the platform resource and/or the URI of the device resource, reference may be made to the above description, and in order to avoid repetition, details are not described here again.

In addition, the information of the virtual OCF server further includes at least one of the following information: interface and resource type of virtual OCF server.

The interface of the virtual OCF server may be "oic. The resource type of the platform resource of the virtual OCF server may be "oic. For the virtual OCF server 1, the resource types of the device resources may be "oic.wk.d" and "oic.d.light", for example. For the virtual OCF server 2, the resource types of the device resources may be, for example, "oic.wk.d" and "oic.d.oven".

According to the technical scheme, the endpoints of all the virtual servers on the bridge device are the same as those of the bridge device, and compared with the traditional scheme, the number of the endpoints on the bridge device is reduced, so that the maintenance cost of the bridge device for the endpoints can be reduced. In order to distinguish different platform resources and device resources, the platform resources and the device resources of the virtual server do not use fixed URIs any more, but 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, and the URIs of the device resources of the virtual server and the URIs of the device resources of the bridge device are set to be different.

By adopting the communication method of the embodiment of the application, the number of endpoints in the bridging device can be reduced, so that the communication complexity of the bridging device can be reduced.

Specifically, the endpoint is used for transmission of the network layer, the endpoint is related to a communication channel, and after the number of endpoints on the bridge device is reduced, the communication channel between the client and the bridge device, which is established by the bridge device, is reduced, and the reduction of the communication channel can reduce the overhead of resources and reduce the complexity of the network layer. And the bridging device only needs to maintain one communication channel, so that the communication complexity of the bridging device can be reduced.

It should be understood that the bridge device may establish the transmission channel according to a transmission protocol when establishing the communication channel. For example, for a client using the coach protocol, the communication channel between the client and the bridge device established by the bridge device is established based on the coach protocol.

Optionally, the resource of the first communication protocol virtual server further includes a device instance resource, and 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, where the resource operation request message includes a URI of a 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.

For example, the bridging device may receive a resource operation request message sent by the OCF client, where the resource operation request message may include a URI of an instance resource of the device 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: the interface of the equipment instance resource, the resource type of the equipment instance resource, the resource operation method and the attribute value of the equipment instance resource.

For example, for the virtual OCF server 1, the interfaces of the device instance resource may be "oic.if.a" and "oic.if.baseline", and the resource type of the device instance resource may be "oic.r.switch.binary".

For the virtual OCF server 2, the interfaces of the device instance resource may be "oic.if.a" and "oic.if.baseline", and the resource types of the device instance resource may be "oic.r.switch.binary" and "oic.r.temperature".

The resource operation method comprises at least one of the following methods: creating resources, reading resources, updating resources, and deleting resources.

The attribute values of the device instance resource refer to the operational data on the resource.

Taking "light" as an example, the attribute value "of the device instance resource may be" true "or" false ", which indicates to turn on the light when the attribute value is" true ", and to turn off the light when the attribute value is" false ".

Taking "oven" as an example, when the attribute value "setvalue" is 25, it may mean that the temperature is adjusted to 25 ℃.

After receiving the resource operation request message, the bridge device may determine, according to the URI of the device instance resource, the second communication protocol device requested by the first communication protocol client. The operation request message may then be converted into a protocol message of the first communication protocol device and the converted protocol message may be transmitted to the first communication protocol device.

Optionally, the protocol message may also be a device instruction of the second communication protocol device.

For example, when the URI of the resource operation request message is the URI of the device instance resource of the virtual OCF server 1, the bridge device may convert the resource operation request message into a device instruction of the non-OCF device 1, and send the converted device instruction to the non-OCF device 1. When the URI of the resource operation request message is the URI of the device instance resource of the virtual OCF server 2, the bridge device may 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.

Optionally, when the bridge device creates the first communication protocol virtual server, the bridge device may also add a device identifier to the URI of the instance resource of the first communication protocol virtual server.

Optionally, 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.

Optionally, before step 210, the method of fig. 2 may further include: the bridge device receives a 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. After receiving the connection establishment request message, the bridge device may create a first communication protocol virtual server for the second communication protocol device, implement conversion between the first communication protocol and the second communication protocol, and establish a connection between the first communication protocol device and the second communication protocol device.

The device identification may uniquely identify the non-OCF device, from which the non-OCF device may be identified.

Alternatively, the 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 flow chart of another method for bridging communications according to an embodiment of the present application. The method of fig. 3 comprises steps 310-320.

In step 310, the first communication protocol client sends a resource discovery request message to the bridge device.

The resource discovery request message may be used to discover resources on the bridging device. For example, 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 may communicate with the bridge device via the first communication protocol.

Optionally, the first communication protocol may be a communication protocol in the internet of things. For example, the first communication protocol may be an OCF protocol.

In step 320, the first communication protocol client receives a resource discovery response message sent by the bridge device, where 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 the platform resource, a URI of the device resource, and the like. 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 platform resource of the first communication protocol 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 is different from the uniform resource identifier of the device resource of the bridge device, and the first communication protocol is different from the second communication protocol.

The first communication protocol and the second communication protocol are not particularly limited in this embodiment of the application, as long as the first communication protocol and the second communication protocol are two different protocols. For example, the first communication protocol may be a communication protocol in the internet of things, and the second communication protocol may be a communication protocol in a non-internet of things. As another example, the first communication protocol is a zigbee protocol and the second communication protocol is a Bluetooth protocol. Alternatively, the first communication protocol may be an OCF protocol and 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.

When the endpoints of the bridge device are "coach:// [ fe80:: b1d 6: 44444", the endpoints of the virtual OCF server are "coach:// [ fe80:: b1d 6: 44444".

For example, the URIs of the platform resources and the device resources of the virtual OCF server may be numbered sequentially, that is, the URIs of the platform resources and the device resources of the virtual OCF server include a numbering sequence, so that different platform resources and device resources may be distinguished by the URIs.

For another example, the URIs of the platform resources and the device resources of the virtual OCF server include device identifiers of non-OCF devices, and different non-OCF devices have different device identifiers, so that different platform resources and different device resources can be distinguished by the device identifiers of the non-OCF devices.

Optionally, the resource response message may include information of resources of all virtual OCF servers on the bridge device.

After receiving the resource response message, the OCF client may select the resource of the virtual OCF server that wants to perform the operation.

Optionally, the platform resource of the first communication protocol virtual server and the URI of the device resource both include the device identifier of the second communication protocol device.

Different second communication protocol devices have different device identifications, so that different platform resources and device resources can be distinguished by the device identifications of the second communication protocol devices.

In addition, the resource of the first communication protocol virtual server also includes a device instance resource, and the resource response message also includes a URI of the device instance resource. After receiving the resource response message sent by the bridge device, the first communication protocol client may select the platform resource and the device resource that are desired to be accessed according to the information of the platform resource and the device resource carried in the response message, and may select the device instance resource that is desired to be operated according to the information of the device instance resource on the platform resource.

Optionally, before the first communication protocol client sends the resource operation request message to the first communication protocol virtual server, the first communication protocol client may select, according to information carried in the resource response message, a second communication protocol device that is desired to be operated, and then the first communication protocol client may send the resource operation request message to the first communication protocol virtual server corresponding to the selected second communication protocol device. Wherein, the resource operator request message includes the URI of the device instance resource.

Optionally, the resource operation request message may further include at least one of the following information: the interface of the equipment instance resource, the resource type of the equipment instance resource, the resource operation method and the attribute value of the equipment instance resource.

Fig. 4 is a schematic flowchart of another method for bridging device communication according to an embodiment of the present application. The method of FIG. 4 includes steps 410-420.

The method of fig. 4 may be used in combination with the methods of fig. 2 and fig. 3, and the specific description in the method of fig. 4 may refer to the description in the methods of fig. 2 and fig. 3, and is not repeated here to avoid repetition.

In step 410, 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.

Optionally, the connection establishment request message may include a device identifier of the second communication protocol device.

In step 420, the bridge device creates a first communication protocol virtual server for the second communication protocol device, where an endpoint of the first communication protocol virtual server is the same as an endpoint of the bridge device, a uniform resource identifier of a platform resource of the first communication protocol virtual server is different from a uniform resource identifier of a platform resource of the bridge device, and a uniform resource identifier of a device resource of the first communication protocol virtual server is different from a uniform resource identifier of a device resource of the bridge device.

In the process of creating the first communication protocol virtual server, the bridge device creates information of the first communication protocol virtual server, where the information of the first communication protocol virtual server includes a uniform resource identifier of a platform resource, a uniform resource identifier of a device resource, and an endpoint.

Fig. 5 is a schematic flowchart of another method for bridging device communication according to an embodiment of the present application. The method of fig. 5 comprises step 510-550.

In step 510, the bridging device receives a resource discovery request message sent by a first communication protocol client.

The resource discovery request message is primarily used to discover resources on the bridging device. For example, the resource discovery request message may be used to discover resource information of all virtual servers on the bridge device.

A first communication protocol client may refer to a client that may communicate with a bridge device via a first communication protocol.

Optionally, the first communication protocol may be a protocol in the internet of things. For example, the first communication protocol may be an OCF protocol.

In step 520, the bridge device sends a resource discovery response message to the first communication protocol client, where the resource discovery response message includes information of the 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, 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.

Optionally, the first communication protocol virtual server may be a server mapped on the bridge device for the second communication protocol device, and the first communication protocol is different from the second communication protocol.

Optionally, the resource discovery response message may include information of all proxy service resources on the bridge device and information of resources of the first communication protocol virtual server.

One proxy service resource may be included on one bridge device, or a plurality of proxy service resources may be included on one bridge device. The proxy service resource is used for proxying the request of the resource on the first communication protocol virtual server. For the case where the bridge device includes a proxy service resource, the proxy service resource may proxy a request for resources of all first communication protocol virtual servers on the bridge device. For the case where the bridge device includes multiple proxy service resources, one of the proxy service resources may proxy a request for resources of a portion of the first communication protocol virtual server on the bridge device.

The proxy service resource may be created by the bridge device before shipment, or may be created by the bridge device after receiving the connection establishment request message sent by the second communication protocol device.

Alternatively, the 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, where the URI of the proxy service resource is different from both the device resource of the bridge device and the URI of the platform resource.

For example, the URI of the proxy service resource is "/proxyservice", which is different from the URI "/oic/p" of the platform resource of the bridge device and also different from the URI "/oic/d" of the device resource of the bridge device.

The information of the first communication protocol virtual server includes endpoint information, the endpoint being the same as the endpoint of the bridge device.

For example, when the endpoint of the bridge device is "coach:// [ fe80:: b1d 6:: 44444", the endpoint of the first communication protocol virtual service is also "coach:// [ fe80:: b1d 6: 44444".

Optionally, the information of the proxy service resource may further include at least one of the following information: resource type and interface of the proxy service resource. For example, the resource type of the proxy service resource may be "oic. The interface of the proxy service resource may be "oic.

Optionally, 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 equipment resource, the resource type, the interface and the target identifier.

Optionally, the device resource of the first communication protocol virtual server may use a URI that is the same as the URI of the device resource of the bridge device, or may use a URI that is 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 as the URI of the platform resource of the bridge device, or may be a different URI from the URI of the device resource of the bridge device.

Optionally, 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.

Taking OCF as an example, the URI of the platform resource of the virtual OCF server and the URI of the device resource may adopt fixed URIs. For example, the URI of the platform resource of the virtual OCF server is "/oic/p", and the URI of the device resource is "/oic/d".

Or, the URI of the platform resource of the virtual OCF server and the URI of the device resource may include a device identifier of the non-OCF device. For example, the device identifier of the non-OCF device 1 is "light _ device _ id", and the service end mapped by the non-OCF device 1 on the bridge device is the virtual OCF service end 1, the URI of the platform resource of the virtual OCF service end 1 may be "/di/light _ device _ id/oic/p", and the URI of the device resource of the virtual OCF service end 1 may be "/di/light _ device _ id/oic/d". The device identifier of the non-OCF device 2 is "/di/open _ device _ id", the service end mapped by the non-OCF device 2 on the bridge device is the virtual OCF service end 2, the URI of the platform resource of the virtual OCF service end 2 may be "/di/open _ device _ id/oic/d", and the URI of the device resource of the virtual OCF service end 2 may be "/di/open _ device _ id/oic/d".

The target identification may be a device identification of the second communication protocol device. After receiving the resource response message, the first communication protocol client may select a second communication protocol device that wants to operate according to the target identifier.

In step 530, the bridge device receives a resource operation request message sent by the first communication protocol client, where the resource operation request message includes a uniform resource identifier of a platform resource of the proxy service resource and a uniform resource identifier of the device resource, and the resource operation request message also includes a target identifier, where the target identifier is used to identify a second communication protocol device in which the proxy service resource operates.

After receiving the resource operation request sent by the first communication protocol client, the proxy service resource on the bridge device may determine, according to the target identifier carried in the resource operation request message, the second communication protocol device that the first communication protocol client wants to operate.

The resource operation request message further comprises at least one of the following information: URI of device instance resource of first communication protocol virtual server, resource operation method and load.

Taking OCF as an example, the URI of the device instance resource of the virtual OCF server may be "/myLightSwitch", or "/myOven", for example. For another example, the URI of the device instance resource of the virtual OCF service end may further include a device identifier of a non-OCF device, where the device identifier of the non-OCF device 1 is "light _ device _ id", and then the URI of the device instance resource of the virtual OCF service end 1 is "/di/light _ device _ id/mylight switch". The device identifier of the non-OCF device 2 is "open _ device _ id", and the URI of the device instance resource of the virtual OCF server 2 is "/di/open _ device _ id/myOven".

The resource operation method may include at least one of the following methods: creating resources, reading resources, updating resources, and deleting resources.

The payload refers to the operational data for the resource.

Taking "light" as an example, the load "payload" may be { "value": true, or the payload may be { value ": false }. When the operation indicated by the load is "true", it indicates that the lamp is turned on, and when the operation indicated by the load is "false", it indicates that the lamp is turned off.

For example, the load "payload" may be { "setvalue": 25, the load indicating operation may indicate that the temperature is adjusted to 25 deg.c.

In step 540, the bridge device converts the resource operation request message into a protocol message of the second communication protocol device.

In step 550, the bridge device sends the converted protocol message to the second communication protocol device.

After determining the second communication protocol device corresponding to the target identifier, 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 target identification may be a device identification of the second communication protocol device.

For example, the device identification of the non-OCF device 1 is "light _ device _ id", and the device identification of the non-OCF device 2 is "open _ device _ id". The service end of the non-OCF device 1 mapped on the bridge device is a virtual OCF service end 1, and the service end of the non-OCF device 2 mapped on the bridge device is a virtual OCF service end 2. The proxy service resource may proxy requests for resources on virtual OCF server 1 and virtual OCF server 2.

When the target identifier included in the resource operation request message is "light _ device _ id", it indicates that the OCF client requests to operate the resource on the virtual OCF server 1. The bridge device may convert the operation request message into a device instruction of the non-OCF device 1 and transmit the device instruction to the non-OCF device 1.

When the target identifier included in the resource operation request message is "open _ device _ id", it indicates that the OCF client requests to operate the resource on the virtual OCF server 2. The bridge device may convert the operation request message into a device instruction of the non-OCF device 2 and transmit to the non-OCF device 2.

Since the URI of the device instance resource can uniquely identify a second communication protocol device, the target identification may also be the URI of the device instance resource.

In the technical solution provided in the embodiment of the present application, the endpoints of all the virtual servers on the bridge device are the same as the endpoints of the bridge device, and the number of the endpoints on the bridge device is reduced, so that the maintenance cost of the endpoints by the bridge device can be reduced. The URI of the proxy service resource is different from both the URI of the platform resource of the bridge device and the URI of the device resource, and the client can send a request message to the proxy service resource, and the request message carries a target identifier for identifying the device requesting the proxy operation. Thus, the client can operate the resources on the virtual server through the proxy service resources.

Optionally, 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. Likewise, the information of the proxy service resource may be created by the bridge device or obtained by the bridge device from other devices.

Prior to step 510, the method further comprises: 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.

Optionally, 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, the endpoint of the first communication protocol virtual server being the same as the endpoint of the bridge device.

Optionally, 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, where the proxy service resource is capable of proxying the operation request for the second communication protocol device.

Fig. 6 is a schematic flow chart of another method for bridging communications according to an embodiment of the present application. The method of fig. 6 includes steps 610-630.

In step 610, the first communication protocol client sends a resource discovery request message to the bridge device.

The resource discovery request message is primarily used to discover resources on the bridging device.

A first communication protocol client may refer to a client that may communicate with a bridge device via a first communication protocol. The client can be a client in the internet of things.

Optionally, the first communication protocol may be a communication protocol in the internet of things, for example, the first communication protocol may be an OCF protocol.

In step 620, the first communication protocol client receives the resource discovery response message sent by the bridge device. The resource discovery response message comprises information of the proxy service resource and information of the first communication protocol virtual server.

The first communication protocol and the second communication protocol are not particularly limited in this embodiment of the application, as long as the first communication protocol and the second communication protocol are two different protocols. For example, the first communication protocol is a zigbee protocol and the second communication protocol is a bluetooth protocol. Alternatively, the first communication protocol may be an OCF protocol and 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 information of the proxy service resource comprises URI information of the proxy service resource, and the URI of the proxy service resource is different from the URI of the equipment resource and the URI of the platform resource of the bridging equipment.

The information of the first communication protocol virtual server includes endpoint information of the first communication protocol virtual server, for example, when the endpoint of the bridge device is "coach:// [ fe80:: b1d 6:: 44444", the endpoint of the first communication protocol virtual server is also "coach:// [ fe80:: b1d 6:: 44444".

In step 630, the first communication protocol client sends a resource operation request message to the bridge device, where the resource operation request message includes the URI of the platform resource of the proxy service resource and the URI of the device resource, and the resource operation request message also includes a target identifier, where the target identifier is used to identify a second communication protocol device in which the proxy service resource operates.

After receiving the resource response message, the first communication protocol client may select a second communication protocol device that wants to perform an operation, add the target identifier of the second communication protocol device in the resource operation request message, and send the resource operation request message to the proxy service resource capable of acting on the operation.

Taking OCF as an example, the device identifier of the non-OCF device 1 is "light _ device _ id", and the device identifier of the non-OCF device 2 is "open _ device _ id". The service end of the non-OCF device 1 mapped on the bridge device is a virtual OCF service end 1, and the service end of the non-OCF device 2 mapped on the bridge device is a virtual OCF service end 2. The proxy service resource may proxy requests for resources on virtual OCF server 1 and virtual OCF server 2.

When the OCF client wants to perform a resource operation on the non-OCF device 1, a resource operation request message may be sent to the proxy service resource. The target identifier included in the resource operation request message may be "light _ device _ id".

When the OCF client wants to perform a resource operation on the non-OCF device 2, a resource operation request message may be sent to the proxy service resource. The target identifier included in the resource operation request message may be "light _ device _ id".

In the technical solution provided in the embodiment of the present application, the endpoints of all the first communication protocol virtual servers on the bridge device are the same as the endpoints of the bridge device, and the number of the endpoints on the bridge device is reduced, so that the maintenance cost of the endpoint by the bridge device can be reduced. The URI of the proxy service resource is different from both the URI of the platform resource of the bridge device and the URI of the device resource, and the first communication protocol client may send a request message to the proxy service resource, and the request message carries a target identifier for identifying the second communication protocol device requesting the proxy operation. The first communication protocol client can operate the resource on the first communication protocol virtual server through the proxy service resource.

Fig. 7 is a schematic flowchart of another method for bridging device communication according to an embodiment of the present application. The method of FIG. 7 comprises steps 710-720.

The method of fig. 7 may be used in combination with the methods of fig. 5 and fig. 6, and the specific description in the method of fig. 7 may refer to the description in the methods of fig. 5 and fig. 6, and is not repeated here to avoid repetition.

In step 710, the bridge device receives a device registration request message sent by the second communication protocol device.

In step 720, the bridge device creates a first communication protocol virtual server and a proxy service resource for the second communication protocol device, where an endpoint of the first communication protocol virtual server is the same as an endpoint of the bridge device, a uniform resource identifier of the proxy service resource is different from both a uniform resource identifier of a platform resource of the bridge device and a uniform resource identifier of a device resource, and the proxy service resource is used for proxying a request of a first communication protocol client to the first communication protocol virtual server.

In addition, the bridge device creates information for creating the proxy service resource in the process of creating the proxy service resource, wherein the information for creating the proxy service resource comprises a uniform resource identifier of the platform resource, a uniform resource identifier of the device resource and an endpoint.

Fig. 8 is a schematic block diagram of a bridging device provided in an embodiment of the present application. The bridging device 800 of fig. 8 includes a communication unit 810.

A communication unit 810, 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 uniform resource identifier of a platform resource of a first communication protocol virtual server created by the bridge device, a uniform resource identifier of a device resource, and an endpoint, where 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 platform resource of the first communication protocol virtual server 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.

Optionally, the communication unit 810 is further configured to receive a device registration request message sent by the second communication protocol device. The bridging device 800 further comprises a processing unit configured to create the first communication protocol virtual server for the second communication protocol device.

Optionally, the platform resource of the first communication protocol virtual server and the uniform resource identifier of the device resource both include a device identifier of the second communication protocol device.

Optionally, the uniform resource identifier of the device instance resource of the first communication protocol virtual server includes a device identifier of a second communication protocol device, and the communication unit 810 is further configured to receive a resource operation request message sent by a first communication protocol client, where the resource operation request message includes the uniform resource identifier of the device instance resource of the first communication protocol virtual server; the processing unit is further used for converting the resource operation request message into a protocol message of the second communication protocol device; a communication unit 810, further configured to send the protocol message to the second communication protocol device.

Optionally, the first communication protocol is an OCF protocol.

Fig. 9 is a schematic block diagram of a structure of a first communication protocol device according to an embodiment of the present application, where the first communication protocol device 900 of fig. 9 includes a communication unit 910.

A communication unit 910, configured to send a resource discovery request message to a 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 uniform resource identifier of a platform resource of a first communication protocol virtual server created by the bridge device of the first communication protocol virtual server, a uniform resource identifier of a device resource, and an endpoint, where 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 platform resource of the first communication protocol virtual server 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.

Optionally, the uniform resource identifier of the device instance resource of the first communication protocol virtual server includes a device identifier of a second communication protocol device, and the communication unit 910 is further configured to send a resource operation request message to the bridge device, where the resource operation request message includes the uniform resource identifier of the 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 second communication protocol device operated by the first communication protocol virtual server.

Optionally, the first communication protocol is an OCF protocol.

Fig. 10 is a schematic block diagram of another bridge device provided in an embodiment of the present application. The bridging device 1000 of fig. 10 comprises a communication unit 1010 and a processing unit 1020.

A communication unit 1010, configured to receive a device registration request message sent by a second communication protocol device.

A processing unit 1020, configured to create a first communication protocol virtual server for the second communication protocol device, where an endpoint of the first communication protocol virtual server is the same as an endpoint of the bridge device, a uniform resource identifier of a platform resource of the first communication protocol virtual server is different from a uniform resource identifier of a platform resource of the bridge device, and a uniform resource identifier of a device resource of the first communication protocol virtual server is different from a uniform resource identifier of a device resource of the bridge device.

Fig. 11 is a schematic block diagram of another bridge device provided in an embodiment of the present application. The bridging device 1100 of fig. 11 comprises a communication unit 1110 and a processing unit 1120.

A communication unit 1110, 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, a uniform resource identifier of a platform resource of the first communication protocol virtual server, a uniform resource identifier of a device resource, and an endpoint, 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 different from both the uniform resource identifier of the platform resource of the bridge device and the uniform resource identifier of the device resource.

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 of 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 in which the proxy service resource operates, and the first communication protocol is different from the second communication protocol.

A processing unit 1120, 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.

Optionally, the resource discovery response message further includes at least one of the following information: a resource type of the proxy service resource, and an interface.

Optionally, the resource operation request message includes at least one of the following information: the URI of the equipment instance resource of the first communication protocol virtual server, the resource operation method and the load.

Optionally, the first communication protocol is an OCF protocol.

Fig. 12 is a schematic block diagram of another first communication protocol device provided in an embodiment of the present application. The first communication protocol apparatus 1200 of fig. 12 includes a communication unit 1210.

A communication unit 1210 configured to send a resource discovery request message to a bridging 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, a uniform resource identifier of a platform resource of a first communication protocol virtual server, a uniform resource identifier of a device resource, and an endpoint, 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 different from both the uniform resource identifier of the platform resource of the bridge device and the uniform resource identifier of the device resource.

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, the resource operation request message includes a uniform resource identifier of a platform resource of the proxy service resource and a uniform resource identifier of a device resource, the target identifier is used to identify a second communication protocol device in which the proxy service resource operates, and the first communication protocol is different from the second communication protocol.

Optionally, 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.

Optionally, the first communication protocol may be an OCF protocol.

Fig. 13 is a schematic block diagram of another bridge device provided in an embodiment of the present application. The bridging device 1300 of fig. 13 includes a communication unit 1310 and a processing unit 1320.

A communication unit 1310, 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, where an endpoint of the first communication protocol virtual server is the same as an endpoint of the bridge device, a uniform resource identifier of the proxy service resource is different from a uniform resource identifier of a platform resource of the bridge device and a uniform resource identifier of a device resource, and the proxy service resource is used to proxy a request of the first communication protocol client to the first communication protocol virtual server.

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.

Optionally, as shown in fig. 14, the communication device 1400 may further include a memory 1420. From memory 1420, processor 1410 may invoke and execute a computer program to implement the methods of the embodiments of the present application.

The memory 1420 may be a separate device from the processor 1410, or may be integrated into the processor 1410.

Optionally, as shown in fig. 14, 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 in particular, may transmit information or data to other devices or receive information or data transmitted by other devices.

The transceiver 1430 may include a transmitter and a receiver, among others. The transceiver 1430 may further include antennas, and the number of antennas may be one or more.

Optionally, the communication device 1400 may specifically be a network device in the embodiment of the present application, and the communication device 1400 may implement a corresponding procedure implemented by the network device in each method in the embodiment of the present application, and for brevity, details are not described here again.

Optionally, 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 embodiment of the present application, and for brevity, details are not described here again.

Fig. 15 is a schematic structural diagram of a chip of 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.

Optionally, as shown in fig. 15, the chip 1500 may further include a memory 1520. From the memory 1520, the processor 1510 can call and execute a computer program to implement the method in the embodiment of the present application.

The memory 1520 may be a separate device from the processor 1510 or may be integrated into the processor 1510.

Optionally, the chip 1500 may also include an input interface 1530. The processor 1510 can control the input interface 1530 to communicate with other devices or chips, and in particular, can obtain information or data transmitted by other devices or chips.

Optionally, the chip 1500 may also include an output interface 1540. The processor 1510 may control the output interface 1540 to communicate with other devices or chips, and in particular, may output information or data to the other devices or chips.

Optionally, 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 in the embodiment of the present application, and for brevity, details are not described here again.

Optionally, the chip may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, and for brevity, no further description is given here.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip or a system-on-chip, etc.

Fig. 16 is a schematic block diagram of a communication system 1600 provided in 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 bridge device 1610 may be configured to implement corresponding functions implemented by the bridge device in the foregoing method, and the first communication protocol device 1620 may be configured to implement corresponding functions implemented by devices in the foregoing method, which is not described herein again for brevity.

It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The 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 (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. 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 connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.

It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of example, but not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), Double Data rate Synchronous Dynamic random access memory (DDR SDRAM), Enhanced Synchronous SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and direct memory bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that the above memories are exemplary but not limiting illustrations, for example, the memories in the embodiments of the present application may also be Static Random Access Memory (SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (enhanced SDRAM, ESDRAM), Synchronous Link DRAM (SLDRAM), Direct Rambus RAM (DR RAM), and the like. That is, the memory in the embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

The embodiment of the application also provides a computer readable storage medium for storing the computer program.

Optionally, the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the network device in each method in the embodiment of the present application, which is not described herein again for brevity.

Optionally, 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 enables the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.

Embodiments of the present application also provide a computer program product comprising computer program instructions.

Optionally, the computer program product may be applied to the network device in the embodiment of the present application, and the computer program instructions enable the computer to execute corresponding processes implemented by the network device in the methods in the embodiment of the present application, which are not described herein again for brevity.

Optionally, the computer program product may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in the methods in the embodiment of the present application, which are not described herein again for brevity.

The embodiment of the application also provides a computer program.

Optionally, the computer program may be applied to the network device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute the corresponding process implemented by the network device in each method in the embodiment of the present application, and for brevity, details are not described here again.

Optionally, the computer program may be applied to the mobile terminal/terminal device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A method of bridging communications, comprising:

the method comprises the steps that bridging equipment receives a resource discovery request message sent by a first communication protocol client;

the bridge device sends a resource discovery response message to the first communication protocol client, where 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 a device resource, and an endpoint, where 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 platform resource of the first communication protocol virtual server 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.

2. The method according to claim 1, wherein the uniform resource identifier of the platform resource and the uniform resource identifier of the device resource of the first communication protocol virtual server each include a device identifier of the second communication protocol device.

3. The method according to claim 1 or 2, wherein the uniform resource identifier of the device instance resource of the first communication protocol virtual server comprises a device identification of the second communication protocol device, the method further comprising:

the bridge device receives a resource operation request message sent by the first communication protocol client, wherein the resource operation request message comprises a uniform resource identifier of a device instance resource of the first communication protocol virtual server;

the bridging device converts the resource operation request message into a protocol message of the second communication protocol device;

the bridge device sends the protocol message to the second communication protocol device.

4. The method according to any one of claims 1-3, further comprising:

the bridge device receives a device registration request message sent by a second communication protocol device;

and the bridging equipment creates the first communication protocol virtual server for the second communication protocol equipment.

5. The method according to any of claims 1-4, wherein the first communication protocol is the open connection Foundation OCF protocol.

6. A method of bridging communications, comprising:

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, where 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 a device resource, and an endpoint, where 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 platform resource of the first communication protocol virtual server 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.

7. The method according to claim 6, wherein the uniform resource identifier of the platform resource and the uniform resource identifier of the device resource of the first communication protocol virtual server each include a device identifier of the second communication protocol device.

8. The method according to claim 4 or 5, wherein the uniform resource identifier of the device instance resource of the first communication protocol virtual server comprises a device identification of the second communication protocol device, the method further comprising:

the first communication protocol client sends a resource operation request message to the bridge device, where 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 second communication protocol device operated by the first communication protocol virtual server.

9. The method according to any of claims 6-8, wherein the first communication protocol is the open connection foundation OCF protocol.

10. A method of bridging communications, comprising:

the bridging device receives a device registration request message sent by the second communication protocol device;

the bridge device creates 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, a uniform resource identifier of a platform resource of the first communication protocol virtual server is different from a uniform resource identifier of a platform resource of the bridge device, and a uniform resource identifier of a device resource of the first communication protocol virtual server is different from a uniform resource identifier of a device resource of the bridge device.

11. A method of bridging communications, comprising:

the bridge device sends a resource discovery response message to the first communication protocol client, wherein the resource discovery response message includes pre-created proxy service resources and information of a first communication protocol virtual server, and the pre-created proxy service resources and information of the first communication protocol virtual server include a uniform resource identifier of a platform resource, a uniform resource identifier of a device resource and an endpoint, 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 resources is different from both the uniform resource identifier of the platform resource of the bridge device and the uniform resource identifier of the device resource;

the bridge device receives a resource operation request message sent by the first communication protocol client, wherein the resource operation request message comprises a uniform resource identifier of a platform resource of the proxy service resource and a uniform resource identifier of a device resource, and the resource operation request message also comprises a target identifier, and the target identifier is used for identifying a second communication protocol device operated by the proxy service resource;

12. The method of claim 11, wherein the resource discovery response message further comprises at least one of the following information: a resource type and an interface of the proxy service resource.

13. The method according to claim 11 or 12, wherein the resource operation request message comprises at least one of the following information: the uniform resource identifier of the device instance resource of the first communication protocol virtual server, the resource operation method and the load.

14. The method according to any of claims 11-13, wherein the first communication protocol is an open connection foundation OCF protocol.

15. A method of bridging communications, comprising:

the first communication protocol client receives a resource discovery response message sent by the bridge device, wherein the resource discovery response message comprises pre-created proxy service resources and information of a first communication protocol virtual server, and the information of the proxy service resources and the information of the first communication protocol virtual server comprises a uniform resource identifier of a platform resource, a uniform resource identifier of a device resource and an endpoint, 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 resources is different from the uniform resource identifier of the platform resource of the bridge device and the uniform resource identifier of the device resource;

the first communication protocol client sends a resource operation request message to the bridge device, wherein the resource operation request message includes a uniform resource identifier of a platform resource of the proxy service resource and a uniform resource identifier of a device resource, and the resource operation request message also includes a target identifier, and the target identifier is used for identifying a second communication protocol device operated by the proxy service resource.

16. The method of claim 15, wherein the resource discovery response message further comprises at least one of the following information: a resource type and an interface of the proxy service resource.

17. The method according to claim 15 or 16, wherein the resource operation request message comprises at least one of the following information: the uniform resource identifier of the device instance resource of the first communication protocol virtual server, the resource operation method and the load.

18. The method according to any of claims 15-17, wherein the first communication protocol is an open connection foundation OCF protocol.

19. A method of bridging communications, comprising:

the bridge device creates 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, a uniform resource identifier of the proxy service resource is different from a uniform resource identifier of a platform resource of the bridge device and a uniform resource identifier of a device resource, and the proxy service resource is used for proxying a request of a first communication protocol client to the first communication protocol virtual server.

20. A bridging device, comprising:

the communication unit is used for receiving a resource discovery request message sent by a first communication protocol client;

the communication unit is further configured to send a resource discovery response message to the first communication protocol client, where the resource discovery response message includes a uniform resource identifier of a platform resource of a first communication protocol virtual server created by the bridge device, a uniform resource identifier of a device resource, and an endpoint, where 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 platform resource of the first communication protocol virtual server 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.

21. The bridging device according to claim 20, wherein the uniform resource identifier of the platform resource of the first communication protocol virtual server and the uniform resource identifier of the device resource each include a device identifier of the second communication protocol device.

22. The bridging device according to claim 20 or 21, wherein the uniform resource identifier of the device instance resource of the first communication protocol virtual server comprises a device identification of the second communication protocol device,

the communication unit: the resource operation request message comprises a uniform resource identifier of the equipment instance resource of the first communication protocol virtual server;

the bridge device further comprises a processing unit, configured to convert the resource operation request message into a protocol message of the second communication protocol device;

the communication unit: and is further configured to send the protocol message to the second communication protocol device.

23. The bridging device of any one of claims 20-22, wherein the communication unit is further configured to:

receiving a device registration request message sent by a second communication protocol device;

the bridge device further includes a processing unit configured to create the first communication protocol virtual server for the second communication protocol device.

24. The bridging device of any one of claims 20-23, wherein the first communication protocol is an Open Connection Foundation (OCF) protocol.

25. A first communication protocol device, comprising:

a communication unit, configured to send a resource discovery request message to a bridge device;

the communication unit is further configured to receive a resource discovery response message sent by the bridge device, where the resource discovery response message includes a uniform resource identifier of a platform resource of a first communication protocol virtual server created by the bridge device, a uniform resource identifier of a device resource, and an endpoint, where 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 platform resource of the first communication protocol virtual server 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.

26. The apparatus according to claim 25, wherein the uniform resource identifier of the platform resource of the first communication protocol virtual server and the uniform resource identifier of the device resource each include a device identifier of the second communication protocol device.

27. The device according to claim 25 or 26, wherein the uniform resource identifier of the device instance resource of the first communication protocol virtual server comprises a device identification of the second communication protocol device,

the communication unit: the method further includes sending a resource operation request message to the bridge device, where 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 second communication protocol device operated by the first communication protocol virtual server.

28. The device according to any of claims 25-27, wherein the first communication protocol is an open connection foundation OCF protocol.

29. A bridging device, comprising:

the communication unit is used for receiving a device registration request message sent by the second communication protocol device;

a processing unit, configured to create a first communication protocol virtual server for the second communication protocol device, where an endpoint of the first communication protocol virtual server is the same as an endpoint of the bridge device, a uniform resource identifier of a platform resource of the first communication protocol virtual server is different from a uniform resource identifier of a platform resource of the bridge device, and a uniform resource identifier of a device resource of the first communication protocol virtual server is different from a uniform resource identifier of a device resource of the bridge device.

30. A bridging device, comprising:

the communication unit 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, a uniform resource identifier of a platform resource of the first communication protocol virtual server, a uniform resource identifier of a device resource, and an endpoint, 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 different from both the uniform resource identifier of the platform resource of the bridge device and the uniform resource identifier of the device resource;

the communication unit is further configured to receive a resource operation request message sent by the first communication protocol client, where the resource operation request message includes a uniform resource identifier of 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 in which the proxy service resource operates;

the processing unit is used for converting the resource operation request message into a protocol message of the second communication protocol device;

31. The bridging device of claim 30, wherein 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.

32. The bridging device according to claim 30 or 31, wherein the resource operation request message includes at least one of the following information: the uniform resource identifier of the device instance resource of the first communication protocol virtual server, the resource operation method and the load.

33. The bridging device of any one of claims 30-32, wherein the first communication protocol is an Open Connection Foundation (OCF) protocol.

34. A first communication protocol device, comprising:

the communication unit is further configured to receive a resource discovery response message sent by the bridge device, where the resource discovery response message includes information of a pre-created proxy service resource, a uniform resource identifier of a platform resource of a first communication protocol virtual server, a uniform resource identifier of a device resource, and an endpoint, 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 different from both the uniform resource identifier of the platform resource of the bridge device and the uniform resource identifier of the device resource;

the communication unit is further configured to send a resource operation request message to the bridge device, where the resource operation request message includes a uniform resource identifier of 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 in which the proxy service resource operates.

35. The apparatus of claim 34, wherein the resource discovery response message further comprises at least one of the following information: a resource type and an interface of the proxy service resource.

36. The device according to claim 34 or 35, wherein the resource operation request message comprises at least one of the following information: the uniform resource identifier of the device instance resource of the first communication protocol virtual server, the resource operation method and the load.

37. The device of any one of claims 34-36, wherein the first communication protocol is an Open Connection Foundation (OCF) protocol.

38. A bridging device, comprising:

the processing unit is configured to create a first communication protocol virtual server and a proxy service resource for the second communication protocol device, where an endpoint of the first communication protocol virtual server is the same as an endpoint of the bridge device, a uniform resource identifier of the proxy service resource is different from a uniform resource identifier of a platform resource of the bridge device and a uniform resource identifier of a device resource, and the proxy service resource is used to proxy a request of the first communication protocol client to the first communication protocol virtual server.

39. A bridging device, comprising: a processor and a memory for storing a computer program, the processor being configured to invoke and execute the computer program stored in the memory to perform the method of any of claims 1 to 5.

40. A first communication protocol device, comprising: a processor and a memory for storing a computer program, the processor being configured to invoke and execute the computer program stored in the memory to perform the method of any of claims 6 to 9.

41. A bridging device, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and execute the computer program stored in the memory to perform the method of claim 10.

42. A bridging device, comprising: a processor and a memory for storing a computer program, the processor being configured to invoke and execute the computer program stored in the memory to perform the method of any of claims 11 to 14.

43. A first communication protocol device, comprising: a processor and a memory for storing a computer program, the processor being configured to invoke and execute the computer program stored in the memory to perform the method of any of claims 15 to 18.

44. A bridging device, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and execute the computer program stored in the memory to perform the method of claim 19.

45. A chip, comprising: a processor for calling and running a computer program from a memory so that a terminal device in which the chip is installed performs the method of any one of claims 1 to 5.

46. A chip, comprising: a processor for calling and running a computer program from a memory so that a terminal device in which the chip is installed performs the method of any one of claims 6 to 9.

47. A chip, comprising: a processor for calling and running a computer program from a memory so that a terminal device in which the chip is installed performs the method of claim 10.

48. A chip, comprising: a processor for calling and running a computer program from a memory so that a terminal device in which the chip is installed performs the method of any one of claims 11 to 14.

49. A chip, comprising: a processor for calling and running a computer program from a memory so that a terminal device in which the chip is installed performs the method of any one of claims 15 to 18.

50. A chip, comprising: a processor for calling and running a computer program from a memory so that a terminal device in which the chip is installed performs the method of claim 19.

51. A computer-readable storage medium for storing a computer program which causes a computer to perform the method of any one of claims 1 to 5.

52. A computer-readable storage medium for storing a computer program which causes a computer to perform the method of any one of claims 6 to 9.

53. A computer-readable storage medium for storing a computer program which causes a computer to perform the method of claim 10.

54. A computer-readable storage medium for storing a computer program which causes a computer to perform the method of any one of claims 11 to 14.

55. A computer-readable storage medium for storing a computer program which causes a computer to perform the method of any one of claims 15 to 18.

56. A computer-readable storage medium for storing a computer program which causes a computer to perform the method of claim 19.

57. A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 5.

58. A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 6 to 9.

59. A computer program product comprising computer program instructions for causing a computer to perform the method of claim 10.

60. A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 11 to 14.

61. A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 15 to 18.

62. A computer program product comprising computer program instructions for causing a computer to perform the method of claim 19.

63. A computer program, characterized in that the computer program causes a computer to perform the method according to any of claims 1-5.

64. A computer program, characterized in that the computer program causes a computer to perform the method according to any of claims 6 to 9.

65. A computer program, characterized in that the computer program causes a computer to perform the method as claimed in claim 10.

66. A computer program, characterized in that the computer program causes a computer to perform the method according to any of claims 10 to 13.

67. A computer program, characterized in that the computer program causes a computer to perform the method according to any of claims 15-18.

68. A computer program, characterized in that the computer program causes a computer to perform the method of claim 19.