WO2020143013A1

WO2020143013A1 - Method and apparatus for processing query request, computer device and storage medium

Info

Publication number: WO2020143013A1
Application number: PCT/CN2019/071277
Authority: WO
Inventors: 唐海
Original assignee: Oppo广东移动通信有限公司
Priority date: 2019-01-11
Filing date: 2019-01-11
Publication date: 2020-07-16
Also published as: CN110753921A; CN110753921B

Abstract

The present application relates to a method and apparatus for processing a query request, a computer device and a storage medium. The method comprises: after receiving a device query request sent by a third-party device, an RCD firstly detecting whether a shadow device exists in itself, and if so, choosing to directly send device information of the shadow device to the third-party device, or not to respond, and the shadow device responding to the third-party device instead. After the RCD detects a shadow device of which resource synchronization with it has been established, when processing the request of the third-party device, no matter which processing means is used, the RCD always provides the device information of the shadow device to the third-party device, thus when performing a subsequent control process, the third-party device always acquires the device information of the shadow device no matter whether from the RCD or the shadow device, such that the third-party device can only control the shadow device, and the problem of the third-party device selecting the RCD is avoided, enabling human-computer interaction to be more intelligent, and greatly improving service quality.

Description

Query request processing method, device, computer equipment and storage medium

Technical field

The present application relates to the field of Internet of Things technology, and in particular, to a query request processing method, device, computer equipment, and storage medium.

Background technique

With the development of the Internet of Things and smart home technology and industry, intelligent household appliances begin to enter the lives of ordinary residents, and intelligent household appliances can be divided into ordinary devices (Normal Devices, ND) and resource-constrained devices (Resource Constrained Device, RCD). Ordinary equipment refers to equipment with strong capabilities in processing speed, continuous work, networking, etc. Resource-restricted equipment is relatively lacking in hardware resources compared to ordinary equipment, resulting in poor business processing capabilities and endurance. Resource-constrained devices may periodically go to sleep (saving power) in the network, or fail to process large numbers of business requests in real time.

In order to ensure that the RCD can process the control request of the third-party device in time, a device identical to the RCD can be generated on the router or cloud and other devices according to the RCD resource backup, that is, the shadow device (shadow device), which can fully represent the shadow device The RCD receives the control request or response message of the third-party device, and the shadow device and the RCD keep the resources synchronized.

For example, if the configuration terminal (Mediator) configures the RCD (light) as a shadow device, Light can complete the registration process of the shadow device on the cloud platform, and complete the resource synchronization between light and light shadow device during the registration process. When the third-party device modifies the state of light shadow device, it indirectly completes the operation of light. In the process, after receiving the control request of the third-party device, light may send the request to RCD first. After completing the operation of the control request, RCD returns a response message to light shadow device, light shadow device completes the modification of resources.

However, after the RCD establishes the shadow device, the third-party device can discover both the RCD and the shadow device, but the third-party device cannot operate the RCD and can only operate the shadow device. If the user selects the RCD, the RCD will return an error message. Unnecessary troubles for users, resulting in unintelligent human-computer interaction and reduced service quality.

Summary of the invention

Based on this, it is necessary for third parties to discover RCD and Shadow devices at the same time after establishing the shadow device in the RCD, but the third party devices cannot operate RCD, only the shadow device. If the user selects RCD, RCD will An error message will be returned, causing unnecessary troubles to the user, resulting in unsmart human-computer interaction, a technical problem that reduces the quality of service, and provides a processing method, device, computer equipment, and storage medium for query requests.

In a first aspect, an embodiment of the present invention provides a method for processing a query request. The method includes:

Receiving a device query request; the device query request includes a device type;

Detecting whether there is a shadow device in the resource-restricted device corresponding to the device type;

If yes, the device query request is processed according to the device information of the shadow device.

In one of the embodiments, the processing of the device query request according to the device information of the shadow device includes:

Configuring resources through the shadow device to obtain device information of the shadow device;

Send a first response message to a third-party device according to the device information of the shadow device; the first response message includes device information of the shadow device.

In one of the embodiments, the device information of the shadow device includes an identification ID and/or port information of the shadow device.

In one embodiment, the device information of the shadow device further includes at least one of device type, interface information, software and hardware version information, and supported languages.

In one of the embodiments, the first response message further includes operable resource information of the shadow device.

In one of the embodiments, the operational resource information includes at least one of a uniform resource identifier URI of the operational resource, interface information of the operational resource, and a resource type of the operational resource.

In one of the embodiments, before configuring resources through the shadow device and obtaining device information of the shadow device, the method further includes:

Detect whether the shadow device is established in the cloud;

If the shadow device is established in the cloud, a step of configuring resources through the shadow device and acquiring device information of the shadow device is performed.

In one of the embodiments, the processing the device query request according to the device information of the shadow device includes: discarding the device query request.

In one of the embodiments, the processing of the device query request according to the device information of the shadow device includes: sending a second response message to a third-party device; the second response message is used to indicate the resource There are shadow devices for restricted devices.

In one of the embodiments, the detecting whether the resource-restricted device corresponding to the device type has a shadow device includes:

Obtaining a shadow device generation indicator bit in the shadow device configuration resource parameter;

Detecting whether a shadow device exists in the resource-restricted device corresponding to the device type according to the indication bit generated by the shadow device.

In a second aspect, an embodiment of the present invention provides a method for processing a query request. The method includes:

Sending a response message according to the device query request; the response message includes device information of the shadow device of the resource-restricted device corresponding to the device type.

In one of the embodiments, the reply message further includes operable resource information of the shadow device.

In a third aspect, an embodiment of the present invention provides a method for processing a query request. The method includes:

Send a device query request; the device query request includes the device type;

Receiving a response message sent by the resource limited device corresponding to the device type and/or the shadow device of the resource limited device; the response message includes device information of the shadow device of the resource limited device corresponding to the device type.

According to a fourth aspect, an embodiment of the present invention provides an apparatus for processing a query request. The apparatus includes:

The first receiving module is used to receive a device query request; the device query request includes a device type;

A detection module, configured to detect whether a shadow device exists in the resource-restricted device corresponding to the device type;

The response module is configured to process the device query request according to the device information of the shadow device if there is a shadow device in the resource-restricted device.

According to a fifth aspect, an embodiment of the present invention provides an apparatus for processing a query request. The apparatus includes:

A second receiving module, configured to receive a device query request; the device query request includes a device type;

The first sending module is configured to send a response message according to the device query request; the response message includes device information of the shadow device of the resource-restricted device corresponding to the device type.

According to a sixth aspect, an embodiment of the present invention provides an apparatus for processing a query request. The apparatus includes:

The second sending module is used to send a device query request; the device query request includes a device type;

A third receiving module, configured to receive a response message sent by the resource-restricted device corresponding to the device type and/or the shadow device of the resource-restricted device; the response message includes the resource-restricted device corresponding to the device type Device information for shadow devices.

According to a seventh aspect, an embodiment of the present invention provides a computer device, including a memory and a processor, where the memory stores a computer program, and when the processor executes the computer program, any of the above first to third aspects is implemented Item of the method.

In an eighth aspect, an embodiment of the present invention provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the method according to any one of the first to third aspects above is implemented A step of.

An embodiment of the present application provides a query request processing method, apparatus, computer equipment, and storage medium. After receiving a device query request sent by a third-party device, the RCD detects whether there is a shadow device. The three-party device sends the device information of the shadow device, or does not respond, and the shadow device responds to the third-party device. In this method, when the RCD detects that a shadow device synchronized with its resources has been established, when processing the device query request of the third-party device, regardless of the processing method, it is based on the device information of the shadow device to the third-party device. In this way, when the third-party device performs the subsequent control process, whether the response obtained from the RCD or the shadow device is about the device information of the shadow device, the third-party device can only control the shadow device, avoiding the third-party device The trouble of choosing RCD makes the human-computer interaction more intelligent and greatly improves the service quality.

BRIEF DESCRIPTION

FIG. 1 is an application environment diagram of a query request processing method provided by an embodiment;

2 is an internal structure diagram of a third-party device provided by an embodiment;

FIG. 3 is a schematic diagram of a method for processing a query request provided by an embodiment;

4 is a schematic flowchart of a method for processing a query request according to an embodiment;

FIG. 5 is a schematic process diagram of a method for processing a query request according to an embodiment;

6 is a schematic flowchart of a method for processing a query request according to an embodiment;

7 is a schematic flowchart of a method for processing a query request according to an embodiment;

8 is a schematic flowchart of a method for processing a query request according to an embodiment;

9 is a schematic flowchart of a query request processing method provided by an embodiment;

10 is a structural block diagram of a query request processing device provided by an embodiment;

11 is a structural block diagram of a query request processing device provided by an embodiment;

12 is a structural block diagram of a query request processing device provided by an embodiment;

13 is a structural block diagram of a query request processing device provided by an embodiment;

FIG. 14 is a structural block diagram of an apparatus for processing a query request according to an embodiment.

detailed description

In order to make the purpose, technical solutions and advantages of the present application more clear, the following describes the present application in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application, and are not used to limit the present application.

This application provides a method for processing query requests, which can be applied to the application environment shown in FIG. 1, including resource-constrained devices (Resource, Constrained Device, RCD), shadow devices (Shadow device), and third-party devices, where , RCD, Shadow device and third-party devices can communicate with each other, and the communication method can be wireless communication, such as: WIFi, infrared communication or 3G, 4G, 5G, etc., this embodiment does not limit this. Among them, the RCD may be an intelligent household appliance with limited resources, such as lamps and air conditioners, or an intelligent terminal, such as a mobile phone or a PAD. The resources of the Shadow device and the resources of the RCD are completely synchronized. The Shadow device can be set in the cloud or on other devices in the same local area network as the RCD. The embodiment of the present application does not limit the specific type of Shadow device. The third-party device may be a server or other processing devices, which is not limited in this embodiment. As shown in FIG. 2, the above server may include a processor, a memory, a network interface, and a database connected through a system bus. Among them, the processor of the server is used to provide computing and control capabilities. The memory of the server includes non-volatile storage media and internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The database of the server is used to query the data of the processing method of the request. The server's network interface is used to communicate with other external devices through a network connection. When the computer program is executed by the processor, a query request processing method is realized.

In practical applications, taking the resource-restricted device as light, the shadow device as light, shadow device, and the shadow device built in the cloud as an example, as shown in Figure 3, the configuration device (Mediator) Send the address information to establish the lightshadowdevice and the necessary information to access the address information, for example: the necessary information can include the address of the cloud platform, the access token of the cloud platform (access token), the uniform resource identifier of the lightshadowdvice ( Uniform Resource Identifier (URI) and so on. That is, Mediator registers a light shadow device for light in the cloud. After the establishment is complete, all resources of light and light shadow are synchronized. Then, the third-party device sends a request to change the working state of light to light shadow device, light shadow device receives After the request is received, the request is sent to light, and light changes the working state, and feeds back a completion message to light shadow device, which means that light shadow has completed the modification of light. However, after the RCD device establishes shadow device, there are two devices with the same resource in the network, but these two devices with the same resource have different device IDs, and the operation of one of the resources produces the same Operation result. After the RCD establishes the shadow device, generally only the shadow device needs to interact with the third party, which means that the third party should not directly operate the RCD. In addition to the device discovery resources on the RCD, third-party devices cannot access any resources of the RCD. However, the third-party devices can discover both the RCD device and the shadow device, but they can only operate the shadow device and cannot operate the RCD device. If the user selects the RCD and performs the operation, the RCD will return an error message. Based on this, the embodiments of the present application provide a query request processing method, device, computer device, and storage medium, which are designed to solve the above-mentioned shadow established in the RCD. After device, the third-party device can discover both RCD and Shadow device, but the third-party device cannot operate RCD, only the shadow device. If the user selects RCD, the RCD will return an error message, bringing unnecessary Trouble, resulting in unintelligent human-computer interaction, which reduces the technical problems of service quality.

The technical solutions of the present application and how the technical solutions of the present application solve the above technical problems will be described in detail below through the embodiments and the accompanying drawings. The following specific embodiments may be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. It should be noted that the method for processing query requests provided by the embodiments of the present application will describe each embodiment with different execution bodies. The execution bodies in FIG. 4 and FIG. 7 are resource-constrained devices, and the execution in FIG. 8 The main body is a shadow device, and the executive body of FIG. 9 is a third-party device. The execution subject of each embodiment may also be a query request processing device, where the device may implement part or all of the resource update through software, hardware, or a combination of software and hardware.

To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be described clearly and completely in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments It is a part of the embodiments of the present invention, but not all the embodiments.

The following describes each embodiment in which the execution subject is RCD.

In one embodiment, FIG. 4 provides a method for processing a query request. This embodiment involves detecting whether a shadow device exists after receiving the device query request from the RCD, and querying a third-party device based on the detection result. The specific process of requesting a response. As shown in Figure 4, the method includes:

S101. Receive a device query request; the device query request includes a device type.

In this embodiment, the device query request represents a request for acquiring or modifying RCD resources sent by a third-party device, where the device query request includes the device type, that is, the device type including the RCD. The third-party device may be a terminal device, such as a mobile phone, a PAD, a personal computer, etc., or a computer device or a server, etc., which is not limited in this embodiment. The way in which the third-party device sends the device query request may be to send the multicast message in the local area network where the RCD is located, or it may be another way, which is not limited in this embodiment. Illustratively, taking the RCD device as light as an example, in an actual application, the RCD receiving device query request may be that light receives a device query request sent by a third-party device in the local area network.

S102: Detect whether a shadow device exists in the resource-restricted device corresponding to the device type.

In this step, the shadow device (shadow device) indicates that a device identical to the RCD is generated on other devices according to the resource backup of the RCD. The newly generated device, that is, the shadow device can completely send requests and receive responses on behalf of the RCD. Among them, the shadow device and RCD keep resources in sync. The shadow device may be installed in the cloud or in the same local area network as the RCD, which is not limited in this embodiment. In practical applications, based on the device query request received by the RCD in step S101 above, it is detected whether the RCD corresponding to the device type carried in the device query request has a shadow device. The RCD can detect whether there is a shadow device by detecting whether There is information storing the shadow device. If the information of the shadow device is stored, it indicates that there is a shadow device in the RCD.

It should be noted here that the device query request sent by the third-party device can only be received by the RCD corresponding to the device type carried in the request. Of course, if the shadow device and the RCD are in the same local area network, the third-party device sends multicast. The request, so in addition to the RCD, the shadow device can also receive the request. For example, if the device query request includes rt=oic.d.light, it indicates that the device type is light.

S103: If there is a shadow device, process the device query request according to the device information of the shadow device.

Based on the above step S102, the RCD detects that there is a shadow device, and responds to the device query request according to the device information of the shadow device. Illustratively, the RCD response method may be not to respond, or to return the device information of the shadow device to the third-party device, or to feed back the message that the shadow device exists to the third-party device, etc. This embodiment does not do this. limited. Among them, the RCD response to the third-party device may be in the form of unicast. It should be noted that the case where the RCD does not respond is based on the fact that the RCD and the corresponding shadow device are located in the same local area network. Because the shadow device also receives the device query request sent by the third-party device, in this case, the shadow device It will return its own device information to the third-party device, so that the third-party device can make subsequent control requests based on the device information of the shadow device.

This embodiment provides a method for processing a query request. After receiving a device query request sent by a third-party device, the RCD detects whether a shadow device exists, and if so, chooses to directly send the device information of the shadow device to the third-party device or Without answering, the shadow device answers to the third-party device. In this method, after detecting that a shadow device synchronized with its resources has been established, the RCD processes the device query request of the third-party device, no matter which processing method, it gives the third-party device the device information based on the shadow device In this way, when the third-party device performs the subsequent control process, whether the response obtained from the RCD or the shadow device is about the device information of the shadow device, the third-party device can only control the shadow device, avoiding the third party The device chooses the trouble of RCD, which makes the human-computer interaction more intelligent and greatly improves the service quality.

In step S103 in the above embodiment, there are three ways for the RCD to respond to the device query request sent by the third-party device according to the device information of the shadow device. The three response methods are described in detail below.

In the first way, a possible implementation manner of the above S103 includes: configuring resources through a shadow device to obtain device information of the shadow device; sending a first response message to a third-party device according to the device information of the shadow device; The first response message includes device information of the shadow device.

In this embodiment, the shadow device configuration resources are used for resource-limited devices to register shadow devices and save them in the RCD. After detecting the existence of a shadow device, RCD first obtains the device information of the shadow device from the shadow device configuration resource, and then sends a first response message to the third-party device, where the first response message includes the device information of the shadow device, where RCD The method of sending the first response message to the third-party device may be by wireless communication, such as Wi-Fi, infrared communication, or 3G, 4G, 5G, etc., which is not limited in this embodiment.

Optionally, the device information of the shadow device includes identification ID and/or port information of the shadow device. Optionally, the device information of the shadow device further includes at least one of device type, interface information, software and hardware version information, and supported languages. The identification ID of the shadow device represents the identity credential information of the shadow device, where the identification ID may be a number, a letter, or a combination of numbers and letters, which is not limited in this embodiment. Among them, the port information represents the IP address and port address of the shadow device. The device information of the shadow device may also include: device type, interface information, hardware and software version information, supported languages, etc., when the RCD sends the device information of the shadow device to the third-party device, it may be one of the above enumerations, or it may be There are many, this embodiment does not limit this.

In this embodiment, the RCD can obtain the shadow device ID, port information (IP address+port) through the shadow device configuration resource, and may also carry the device type, interface information, software and hardware version information, supported language, and other information of the shadow device .

Optionally, the above-mentioned first response message further includes operable resource information of the shadow device. Optionally, the operational resource information includes at least one of a uniform resource identifier URI of the operational resource, interface information of the operational resource, and a resource type of the operational resource.

Among them, the first response message includes the operable resource information of the shadow device, for example: the URI of the operable resource, the interface information of the operable resource and the resource type of the operable resource, etc., where URI represents the character of the resource name, It can be a number, a letter, or a combination of numbers and letters, which is not limited in this embodiment.

In the second manner, another implementable manner of the foregoing S103 includes: discarding the device query request.

In this embodiment, after detecting the presence of a shadow device, the RCD discards the device query request, which means that it does not respond to the device query request of the third-party device.

In a third manner, another possible implementation manner of the foregoing S103 includes: sending a second response message to a third-party device; the second response message is used to indicate that the resource-restricted device has a shadow device.

In this embodiment, the RCD sends a second response message to the third-party device, where the second response message is used to indicate that there is a shadow device in the RCD, and the way in which the RCD sends the second response message to the third-party device may be through wireless communication Sending by way of, such as Wi-Fi, infrared communication or 3G, 4G, 5G, etc., this embodiment does not limit this. It should be understood that the second response message here is just a message indicating that there is a shadow device, and does not contain any information of the shadow device.

Exemplarily, as shown in FIG. 5, it is a complete schematic diagram of the three RCD devices responding to the third-party device provided in this embodiment. In this schematic diagram, it is set that the RCD has created a shadow device, and both the RCD and the shadow device are in In the same local area network, in this way, the request sent by the third-party device in the multicast group will be received by both the RCD and the shadow device. specifically:

S1: The third-party device sends a multicast device query request in the local area network. For example, if the RCD is "light", the request sent by the third-party device is a device discovery request to obtain a "light" type device.

S2: After the resource-restricted device receives the device discovery request message, it first checks whether there is a shadow device.

The inspection method is, for example, to detect whether there is a shadow device configuration resource itself, and if so, to detect the parameters of the shadow device configuration resource: the shadow device generates an indication bit. If the indication bit is true, it indicates that the device has a shadow device, and vice versa There is no shadow device. If there is a shadow device, the shadow device ID and port information can be obtained through the shadow device configuration resource. It may also carry the device type of the shadow device, device interface information, software and hardware version information, and language support information. The port information includes the device's transmission protocol (such as coaps+TCP, coaps, etc.), IP address, and port number. It is also possible to obtain operational resource information corresponding to the shadow device. The operable resource information may include: URI of operable resource, interface information of operable resource, resource type of operable resource, etc.

After the RCD determines that it has a shadow device, it can choose any of the following S3, S4, and S5 to answer the third-party device.

S3: The RCD sends a first response message to the third-party device in a unicast manner, where the first response message carries the port information, ID, device type, interface information, software and hardware version information, supported language, etc. of the shadow device .

S4: The RCD discards the request without responding.

S5: The RCD sends a second response message to the third-party device in a unicast manner, where the second response message is used to indicate that there is a shadow device, but the response message does not include any information of the shadow device.

S6: While the above S3, S4, or S5 is performed, the shadow device will return a response message containing its device information to the third-party device.

The three RCD devices provided in the above embodiments respond to the third-party device. No matter which answering method, the third-party device receives the device information of the shadow device. In this way, when the third-party device performs the subsequent control process, Only the shadow device can be controlled, which avoids the trouble of the third-party device choosing RCD, makes the human-computer interaction more intelligent, and greatly improves the quality of service.

Considering that when the shadow device is established in the cloud, the multicast request sent by the third-party device in the local area network where the RCD is located, the shadow device cannot receive it. In this case, the RCD needs to use "send the first response containing the shadow device information." "Message" in this way to respond to third-party devices, before that, the RCD needs to determine whether the shadow device is built in the cloud. In one of the embodiments, this embodiment provides a method for processing a query request. This embodiment involves It is the specific process of RCD detecting whether the shadow device is built in the cloud and responding to the third-party device according to the detection result. As shown in FIG. 6, the method further includes:

S201: Detect whether the shadow device is established in the cloud.

In this embodiment, the RCD detects whether the shadow device is established in the cloud. For example, the RCD method for detecting the shadow device is established in the cloud may be that the RCD queries the registered address of the shadow device to belong to the address of the local area network. If it is not, it indicates that the shadow device is established In the cloud; if it is, it means that the shadow device is built in the local area network. Of course, the RCD can also be determined by directly querying whether the registered address of the shadow device belongs to the cloud address. For example, it can also be established by adding a shadow device to the configuration resource. The indication bit of the location determines whether the shadow device is established in the cloud according to the indication bit, which is not limited in this embodiment.

S202: If the shadow device is established in the cloud, perform a step of configuring resources through the shadow device to obtain device information of the shadow device.

Based on the above S201, the RCD detects that the shadow device is established in the cloud, and the resource-constrained device configures resources through the shadow device to obtain device information of the shadow device, so as to send the first response message including the shadow device information to the third-party device.

This embodiment provides a method for processing a query request. After detecting that the shadow device is established in the cloud, the RCD configures resources through the shadow device to obtain the device information of the shadow device, so as to send the device information of the shadow device to a third-party device In order to enable the third-party device to carry out the subsequent control process according to the device information of the shadow device, it avoids the trouble of the third-party device choosing RCD, makes the human-computer interaction more intelligent, and greatly improves the service quality.

In addition, when the shadow device is built on other devices in the local area network, the RCD can either use the "send the first response message containing the shadow device information" to answer the third-party device, or it can use the "discard the request without responding." "Or "send a second response message to a third-party device that already has a shadow device" to answer the third-party device.

In some scenarios, the RCD in step S102 may be determined according to the way of configuring resource parameters when detecting whether there is a shadow device. The embodiments of the present application provide a method for processing a query request, which involves the RCD according to the shadow device. The specific process of generating an indication bit in the configuration resource parameter to determine whether there is a shadow device itself, as shown in FIG. 7, the above S102 includes:

S301. Obtain a shadow device generation indicator bit in a shadow device configuration resource parameter.

In this embodiment, the shadow device configuration resource is used to register a shadow device for a resource-constrained device, where the shadow device generates a parameter whose indication bit is the shadow device configuration resource, which indicates whether the shadow device exists in the RCD. It should be understood that before detecting the indication bit generated by the shadow device, the RCD first detects whether there is a shadow device configuration resource itself, and if so, detects the parameter of the shadow device configuration resource: the shadow device generates the indication bit.

S302: Detect whether a shadow device exists in the resource-restricted device corresponding to the device type according to the indication bit generated by the shadow device.

Based on the above-mentioned step S301, the shadow device acquired by the RCD generates an indication bit, and detects whether there is a shadow device according to the indication bit, where the detection method may be that the RCD determines whether there is a shadow device according to the display content of the indication bit, for example, RCD The shadow device configuration resource is /oic/Shadow/conf as an example. RCD can check the attribute of sgi (indicating bit) in the /oic/Shadow/conf resource. If sgi is true, it means there is a shadow device on the device, otherwise There is no shadow device.

This embodiment provides a method for processing a query request. The RCD obtains the indication bit generated by the shadow device, and determines whether there is a shadow device through the indication bit, which makes the detection result of the shadow device more accurate and effectively ensures that subsequent third-party devices pass the shadow The process by which the device controls the RCD state.

The following describes each embodiment in which the execution subject is a shadow device. It should be noted that part of the content involved in the following embodiments has been described in the above embodiments where the execution subject is the RCD, and the repeated content will not be repeated.

In one embodiment, FIG. 8 provides a method for processing a query request. This embodiment relates to a specific process in which a shadow device sends a response message after receiving a device query request sent by a third-party device. As shown in FIG. 8, the method includes:

S401. Receive a device query request; the device query request includes a device type.

In this embodiment, the shadow device receives a device query request, and the device query request includes the device type. It should be noted here that in a method for processing a query request provided by an embodiment of the present application, due to a device sent by a third-party device When the query request is sent in the local local area in a multicast form, the premise that the shadow device can receive the device query request is that the shadow device is established in the local area network sent by the third-party device. If the shadow device is established in the cloud, the shadow device receives Unable to find the device query request.

S402. Send a response message according to the device query request; the response message includes device information of the shadow device of the resource-restricted device corresponding to the device type.

Based on the device query request received by the shadow device in step S401 above, the shadow device sends a reply message to the third-party device, where the reply message includes device information of the shadow device, so that subsequent third-party devices send the shadow device a shadow device based on the device information Send RCD control request. The shadow device, device information, and response message have been described in the foregoing embodiment, and this embodiment will not repeat them here.

This embodiment provides a method for processing a query request. The shadow device feeds back a response message including device information according to the received device query request sent by the third-party device. In this way, after the third-party device receives the device information of the shadow device The state of the RCD device can only be controlled by sending a control request to the shadow device, which avoids the trouble that the third-party device chooses RCD, makes the human-computer interaction more intelligent, and greatly improves the quality of service.

Optionally, the above response message also includes operable resource information of the shadow device. Optionally, the operational resource information includes at least one of a uniform resource identifier URI of operational resources, interface information of operational resources, and a resource type of operational resources. Among them, the response message includes the operable resource information of the shadow device, for example: the URI of the operable resource, the interface information of the operable resource, and the resource type of the operable resource. Among them, the URI represents the character of the resource name, which can It is a number, a letter, or a combination of numbers and letters, which is not limited in this embodiment.

The following describes embodiments in which the execution subject is a third-party device. It should be noted that part of the content involved in the following embodiments has been described in the above embodiments where the execution subject is and the execution subject is a shadow device, and duplicate content will not be repeated.

In one of the embodiments, as shown in FIG. 9, this embodiment provides a method for processing a query request, which involves a third-party device sending a device query request, and receiving or responding to a response from the shadow device according to the device query request. For the specific process of the message, the method includes:

S501: Send a device query request; the device query request includes a device type.

In this embodiment, the third-party device sends a device query request, and the device query request includes the device type. Referring to FIG. 5 above, the third-party device sends the device query request in the form of multicast. Among them, the device query request and the third-party device have been described in the above embodiment, and this embodiment will not repeat them here.

S502: Receive a response message sent by a resource-restricted device corresponding to the device type and/or a shadow device of the resource-restricted device; the response message includes device information of the shadow device of the resource-restricted device corresponding to the device type .

In this step, based on the device query request sent by the third-party device, the RCD and/or its shadow device corresponding to the device type carried in the request will feed back a response message to the third-party device, and the third-party device receives the response message. Wherein, the response message fed back by the RCD and/or its shadow device includes device information of the shadow device, and then the third-party device receives the RCD and/or its shadow device to send the response message.

This embodiment provides a method for processing a query request. After the third-party device sends the device query request, the response message sent by the corresponding RCD and/or its shadow device includes the device information of the shadow device. In this way, the third-party device After receiving the device information of the shadow device, when the third-party device performs the subsequent control process, it can only control the shadow device, avoiding the trouble of the third-party device selecting the RCD, making the human-computer interaction more intelligent, and greatly improving the quality of service.

Optionally, the above response message also includes operable resource information of the shadow device. Optionally, the operational resource information includes at least one of a uniform resource identifier URI of the operational resource, interface information of the operational resource, and a resource type of the operational resource. Among them, the response message includes the operable resource information of the shadow device, for example: the URI of the operable resource, the interface information of the operable resource, and the resource type of the operable resource. Among them, the URI represents the character of the resource name, which can It is a number, a letter, or a combination of numbers and letters, which is not limited in this embodiment.

It should be understood that although the steps in the flowcharts of FIGS. 2-9 are displayed in order according to the arrows, the steps are not necessarily executed in the order indicated by the arrows. Unless clearly stated in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least some of the steps in FIGS. 2-9 may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same time, but may be executed at different times. These sub-steps or stages The execution order of is not necessarily sequential, but may be executed in turn or alternately with at least a part of other steps or sub-steps or stages of other steps.

In one embodiment, as shown in FIG. 10, an embodiment of the present application provides a query request processing apparatus, including: a first receiving module 10, a first detecting module 11, and a response module 12, wherein,

The first receiving module 10 is configured to receive a device query request; the device query request includes a device type;

The first detection module 11 is configured to detect whether there is a shadow device in the resource-restricted device corresponding to the device type;

The response module 12 is configured to process the device query request according to device information of the shadow device if there is a shadow device in the resource-restricted device.

The device for processing query requests provided by the above embodiments is similar in implementation principle and technical effect to the above method embodiments, and will not be repeated here.

In one embodiment, the above-mentioned response module 12 is specifically configured to configure resources of the shadow device to obtain device information of the shadow device; send a first response message to a third-party device according to the device information of the shadow device; The first response message includes device information of the shadow device.

In one of the embodiments, as shown in FIG. 11, an embodiment of the present application provides an apparatus for processing a query request, the apparatus further includes: a second detection module 13, wherein,

The second detection module 13 is used to detect whether the shadow device is established in the cloud;

The response module 12 is used for the step of configuring resources through the shadow device and acquiring device information of the shadow device if the shadow device is established in the cloud.

In one of the embodiments, the above-mentioned response module 12 is also used to discard the device query request.

In one of the embodiments, the above-mentioned response module 12 is further configured to send a second response message to a third-party device; the second response message is used to indicate that the resource-restricted device has a shadow device.

In one of the embodiments, as shown in FIG. 12, an embodiment of the present application provides a query request processing apparatus. The first detection module 11 includes: an acquisition unit 111 and a detection unit 112, wherein,

The obtaining unit 111 is configured to obtain a shadow device generation indicator bit in the shadow device configuration resource parameter;

The detecting unit 112 is configured to detect whether a shadow device exists in the resource-restricted device corresponding to the device type according to the indication bit generated by the shadow device.

In one of the embodiments, as shown in FIG. 13, an embodiment of the present application provides an apparatus for processing a query request, the apparatus includes: a second receiving module 14 and a first sending module 15, wherein,

The second receiving module 14 is configured to receive a device query request; the device query request includes a device type;

The first sending module 15 is configured to send a reply message according to the device query request; the reply message includes device information of the shadow device of the resource-restricted device corresponding to the device type.

In one of the embodiments, as shown in FIG. 14, an embodiment of the present application provides an apparatus for processing a query request, the apparatus includes: a second sending module 16 and a third receiving module 17, wherein,

The second sending module 16 is used to send a device query request; the device query request includes a device type;

The third receiving module 17 is configured to receive a response message sent by the resource limited device corresponding to the device type and/or the shadow device of the resource limited device; the response message includes the resource limited device corresponding to the device type Device information for your shadow device.

For the specific limitation of the query request processing device, please refer to the above limitation on the query request processing method, which will not be repeated here. Each module in the above query request processing device may be implemented in whole or in part by software, hardware, or a combination thereof. The above modules may be embedded in the hardware form or independent of the processor in the computer device, or may be stored in the memory in the computer device in the form of software so that the processor can call and execute the operations corresponding to the above modules.

In one embodiment, a computer device is provided. The computer device may be a server, and an internal structure diagram thereof may be as shown in FIG. 2 above. The computer device includes a processor, memory, network interface, and database connected by a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The database of the computer device is used to store the processing data of the query request. The network interface of the computer device is used to communicate with external terminals through a network connection. When the computer program is executed by the processor, a query request processing method is realized.

Those skilled in the art may understand that the structure shown in FIG. 2 above is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer equipment to which the solution of the present application is applied. The specific computer equipment It may include more or less components than shown in the figures, or combine certain components, or have a different arrangement of components.

In one embodiment, a computer device is provided, which includes a memory and a processor, and a computer program is stored in the memory, and the processor implements the following steps when the processor executes the computer program:

Or, the processor implements the following steps when executing the computer program:

Receive a device query request; the query request includes the device type;

Sending a response message according to the query request; the response message includes device information of the shadow device of the resource-restricted device corresponding to the device type.

Send a device query request; the query request includes the device type;

A computer device provided by the foregoing embodiment has similar implementation principles and technical effects as the foregoing method embodiment, and details are not described herein again.

In one embodiment, a computer-readable storage medium is provided on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

Alternatively, when the computer program is executed by the processor, the following steps are realized:

Receive a device query request; the query request includes the device type;

Send a device query request; the query request includes the device type;

The computer-readable storage medium provided by the foregoing embodiment has similar implementation principles and technical effects as the foregoing method embodiment, and will not be repeated here.

A person of ordinary skill in the art may understand that all or part of the processes in the method of the above embodiments may be completed by instructing relevant hardware through a computer program, and the computer program may be stored in a non-volatile computer readable storage In the medium, when the computer program is executed, the process of the foregoing method embodiments may be included. Wherein, any reference to the memory, storage, database or other media used in the embodiments provided in this application may include non-volatile and/or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous chain (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

The technical features of the above embodiments can be arbitrarily combined. In order to simplify the description, all possible combinations of the technical features in the above embodiments are not described. However, as long as there is no contradiction in the combination of these technical features, they should be It is considered as the scope described in this specification. The above-mentioned embodiments only express several implementation manners of the present application, and their descriptions are more specific and detailed, but they should not be construed as limiting the scope of the invention patent. It should be noted that, for those of ordinary skill in the art, without departing from the concept of the present application, a number of modifications and improvements can also be made, which all fall within the protection scope of the present application. Therefore, the protection scope of the patent of this application shall be subject to the appended claims.

Claims

A query request processing method, characterized in that the method includes:

Receiving a device query request; the device query request includes a device type;

Detecting whether there is a shadow device in the resource-restricted device corresponding to the device type;

If yes, the device query request is processed according to the device information of the shadow device.
The method according to claim 1, wherein the processing of the device query request according to the device information of the shadow device includes:

Configuring resources through the shadow device to obtain device information of the shadow device;

Send a first response message to a third-party device according to the device information of the shadow device; the first response message includes device information of the shadow device.
The method according to claim 2, wherein the device information of the shadow device includes an identification ID and/or port information of the shadow device.
The method according to claim 3, wherein the device information of the shadow device further includes at least one of device type, interface information, software and hardware version information, and supported languages.
The method according to any one of claims 2-4, wherein the first response message further includes operable resource information of the shadow device.
The method according to claim 5, wherein the operable resource information includes at least one of a uniform resource identifier URI of the operable resource, interface information of the operable resource, and a resource type of the operable resource.
The method according to any one of claims 2-4, wherein, before configuring the resource through the shadow device and acquiring device information of the shadow device, the method further comprises:

Detect whether the shadow device is established in the cloud;

If the shadow device is established in the cloud, a step of configuring resources through the shadow device and acquiring device information of the shadow device is performed.
The method according to claim 1, wherein the processing of the device query request according to the device information of the shadow device includes:

Discard the device query request.
The method according to claim 1, wherein the processing of the device query request according to the device information of the shadow device includes:

Sending a second response message to a third-party device; the second response message is used to indicate that a shadow device exists in the resource-restricted device.
The method according to any one of claims 1 to 4, wherein the detecting whether a shadow device exists in the resource-restricted device corresponding to the device type includes:

Obtain the shadow device generation indicator bit in the shadow device configuration resource parameter;

Detecting whether a shadow device exists in the resource-restricted device corresponding to the device type according to the indication bit generated by the shadow device.
A query request processing method, characterized in that the method includes:

Receiving a device query request; the device query request includes a device type;

Sending a response message according to the device query request; the response message includes device information of the shadow device of the resource-restricted device corresponding to the device type.
The method according to claim 11, wherein the device information of the shadow device includes an identification ID and/or port information of the shadow device.
The method according to claim 12, wherein the device information of the shadow device further includes at least one of device type, interface information, software and hardware version information, and supported languages.
The method according to any one of claims 11-13, wherein the response message further includes information on operable resources of the shadow device.
The method according to claim 14, wherein the operable resource information includes at least one of a uniform resource identifier URI of the operable resource, interface information of the operable resource, and a resource type of the operable resource.
A query request processing method, characterized in that the method includes:

Send a device query request; the device query request includes the device type;

Receiving a response message sent by the resource limited device corresponding to the device type and/or the shadow device of the resource limited device; the response message includes device information of the shadow device of the resource limited device corresponding to the device type.
The method according to claim 16, wherein the device information of the shadow device includes an identification ID and/or port information of the shadow device.
The method according to claim 17, wherein the device information of the shadow device further includes at least one of device type, interface information, software and hardware version information, and supported languages.
The method according to any one of claims 16 to 18, wherein the response message further includes operable resource information of the shadow device.
The method according to claim 19, wherein the operable resource information includes at least one of a uniform resource identifier URI of the operable resource, interface information of the operable resource, and a resource type of the operable resource.
An inquiry request processing device, characterized in that the device comprises:

The first receiving module is used to receive a device query request; the device query request includes a device type;

A first detection module, configured to detect whether a shadow device exists in the resource-restricted device corresponding to the device type;

The response module is configured to process the device query request according to the device information of the shadow device if there is a shadow device in the resource-restricted device.
An inquiry request processing device, characterized in that the device comprises:

A second receiving module, configured to receive a device query request; the device query request includes a device type;

The first sending module is configured to send a response message according to the device query request; the response message includes device information of the shadow device of the resource-restricted device corresponding to the device type.
An inquiry request processing device, characterized in that the device includes:

The second sending module is used to send a device query request; the device query request includes a device type;

A third receiving module, configured to receive a response message sent by the resource-restricted device corresponding to the device type and/or the shadow device of the resource-restricted device; the response message includes the resource-restricted device corresponding to the device type Device information for shadow devices.
A computer device includes a memory and a processor, and the memory stores a computer program, wherein the processor executes the computer program to implement the steps of the method according to any one of claims 1 to 20.
A computer-readable storage medium on which a computer program is stored, characterized in that, when the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 20 are implemented.