WO2021237527A1 - 信息处理方法及装置、设备、计算机存储介质 - Google Patents

信息处理方法及装置、设备、计算机存储介质 Download PDF

Info

Publication number
WO2021237527A1
WO2021237527A1 PCT/CN2020/092685 CN2020092685W WO2021237527A1 WO 2021237527 A1 WO2021237527 A1 WO 2021237527A1 CN 2020092685 W CN2020092685 W CN 2020092685W WO 2021237527 A1 WO2021237527 A1 WO 2021237527A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
identity information
security domain
resource
discovery request
Prior art date
Application number
PCT/CN2020/092685
Other languages
English (en)
French (fr)
Inventor
茹昭
罗朝明
Original Assignee
Oppo广东移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to PCT/CN2020/092685 priority Critical patent/WO2021237527A1/zh
Priority to KR1020227045047A priority patent/KR20230016652A/ko
Priority to CN202080093549.3A priority patent/CN114982203A/zh
Priority to EP20937418.0A priority patent/EP4149060B1/en
Priority to JP2022572547A priority patent/JP2023533134A/ja
Priority to CN202211476242.9A priority patent/CN115834202B/zh
Publication of WO2021237527A1 publication Critical patent/WO2021237527A1/zh
Priority to US17/991,405 priority patent/US20230089609A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H04L12/2807—Exchanging configuration information on appliance services in a home automation network
    • H04L12/2809—Exchanging configuration information on appliance services in a home automation network indicating that an appliance service is present in a home automation network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/20—Network architectures or network communication protocols for network security for managing network security; network security policies in general
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
    • H04L65/611—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for multicast or broadcast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
    • H04L65/612—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security
    • H04W12/086—Access security using security domains
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H04L2012/2847—Home automation networks characterised by the type of home appliance used
    • H04L2012/285—Generic home appliances, e.g. refrigerators

Definitions

  • This application relates to the technical field of the Internet of Things, and in particular to an information processing method and device, equipment, and computer storage medium.
  • IOT Internet of Things
  • a first device such as a client
  • second devices such as a server
  • each second device that receives the discovery request The device will respond to the discovery request and return its own resource list to the first device.
  • the first device will receive multiple resource lists returned by the second device, and the received resource list is likely to include information that the first device does not expect (for example, the second device that cannot be controlled by the first device returns The list of resources); in this way, information redundancy is caused, and the data processing efficiency of the first device is reduced.
  • the embodiments of the present application provide an information processing method and device, equipment, and computer storage medium.
  • an embodiment of the present application provides an information processing method applied to a first device, and the method includes:
  • the first discovery request information is used to request target resources of a target device that matches the first identity information;
  • an embodiment of the present application provides an information processing method applied to a second device, and the method includes:
  • the first discovery request information includes first identity information of the first security domain; the first discovery request information is used to request target resources of a target device that matches the first identity information;
  • an embodiment of the present application provides an information processing device, an application and a first device, and the information processing device includes:
  • the first obtaining unit is configured to obtain the first identity information of the first security domain
  • a first processing unit configured to obtain first discovery request information based on the first identity information; the first discovery request information is used to request target resources of a target device that matches the first identity information;
  • the first transceiver unit is configured to send the first discovery request information.
  • an embodiment of the present application provides an information processing device, which is applied to a second device, and the information processing device includes:
  • the second transceiving unit is configured to receive first discovery request information; the first discovery request information includes first identity information of the first security domain; the first discovery request information is used to discover a match with the first identity information The target resource of the target device;
  • the second processing unit is configured to determine whether to send the target resource based on the first identity information.
  • an embodiment of the present application provides a device, the device including: a first transceiver, a first processor, and a first memory storing a computer program;
  • the first processor is configured to implement communication with another device through the transceiver; wherein,
  • the first processor is further configured to execute the steps of the information processing method described in the first aspect when running the computer program stored in the first memory in conjunction with the first transceiver.
  • an embodiment of the present application provides a device, the device including: a second transceiver, a second processor, and a second memory storing a computer program;
  • the second processor is configured to implement communication with another device through the transceiver; wherein,
  • the second processor is further configured to execute the steps of the information processing method in the second aspect when running the computer program stored in the second memory in conjunction with the second transceiver.
  • an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, and the computer program is executed by a first processor to implement the steps of the method described in the first aspect; or; the computer program The steps of the method described in the second aspect are executed by the second processor.
  • the first device obtains the first identity information of the first security domain; obtains the first discovery request information based on the first identity information; The first discovery request information is used to request a target resource of a target device that matches the first identity information; and the first discovery request information is sent. That is, the first discovery request information is only used to request the target resource stored in the target device that matches the first security domain. In this way, the information received by the first device is all related to the first security domain (that is, the first identity information). ) The target resource of the matched target device; in this way, the redundancy of information is reduced, and the processing efficiency of the first device is improved.
  • FIG. 1 is a schematic diagram of an application scenario of an exemplary discovery process provided by an embodiment of the application
  • Figure 2 is a schematic diagram of a network structure provided by an embodiment of the application.
  • FIG. 3 is a schematic diagram 1 of the flow of an information processing method provided by an embodiment of this application.
  • FIG. 4 is a schematic diagram 2 of the flow of an information processing method provided by an embodiment of this application.
  • FIG. 5 is a third schematic flowchart of an information processing method provided by an embodiment of this application.
  • FIG. 6 is a fourth flowchart of an information processing method provided by an embodiment of this application.
  • FIG. 7 is a schematic diagram of an application scenario of an information processing method provided by an embodiment of this application.
  • FIG. 8 is a schematic diagram 1 of a device discovery or resource discovery process provided by an embodiment of this application.
  • FIG. 9 is a second schematic diagram of a device discovery or resource discovery process provided by an embodiment of this application.
  • FIG. 10 is a third schematic diagram of a device discovery or resource discovery process according to an embodiment of this application.
  • FIG. 11 is a schematic diagram 1 of the structural composition of an information processing device provided by an embodiment of this application.
  • FIG. 12 is a second schematic diagram of the structural composition of an information processing device provided by an embodiment of this application.
  • FIG. 13 is a schematic diagram 1 of a first device hardware structure provided by an embodiment of this application.
  • FIG. 14 is a second schematic diagram of the hardware structure of a second device provided by an embodiment of the application.
  • the well-known resource oic/res resource can be used as the default discovery mechanism.
  • the application scenario may include multiple server devices (including the refrigerator 11, the light 12, and the temperature sensor 13 as shown in FIG. 1) and a client device (as shown in FIG. 1).
  • the smartphone shown is 14).
  • the specific discovery process is as follows:
  • Each server device can update the discoverable resources to the local /oic/res resource of the server, that is, every time a new discoverable resource is instantiated on the server device, The instantiated resource needs to be updated to the local /oic/res resource of the server device.
  • the client device can send a retrieval (RETRIEVE) request to the /oic/res resources of multiple server devices.
  • RETRIEVE retrieval
  • the client device can use query conditions in the RETRIEVE request to limit the discovered objects.
  • the query conditions can be limited based on resource types, interfaces, or attributes.
  • the server device receiving the RETRIEVE request responds to the request and returns the resource list saved in the /oic/res resource.
  • the resource list received by the client device may contain information that the client device does not expect, such as a resource list returned by a server device that is not in the same security domain as the client device, or a server device that is not controlled by the client device List of returned resources, etc. In this way, information redundancy is caused, and the data processing efficiency of the client device is reduced.
  • FIG. 2 is a schematic diagram of a network structure 200 to which the embodiment of the application is applicable.
  • the network structure 200 includes a client device 210 and a server device 220.
  • the client device 210 refers to a device that accesses resources
  • the server device refers to a device that provides resources.
  • the client device has the function of querying and controlling other devices, and the server device can be queried and controlled by other devices; that is, in the network structure 200 provided by the implementation of this application, any device that has the function of querying and controlling other devices Devices can be used as client devices.
  • any device that can be queried and controlled can be used as a server device.
  • a device such as a light bulb
  • a device that implements a certain basic function can only be used as a server and provided to the client for query and control. It does not need to control or query other devices.
  • the client device 210 and the server device 220 involved in the embodiments of this application include, but are not limited to, smart phones, tablets, laptops, wearable devices, in-vehicle devices, smart home devices, smart security devices, etc.
  • Smart home devices include but are not limited to smart air conditioners, refrigerators, smart door locks, smart lamps, etc.
  • Smart security devices include but are not limited to smoke and gas alarm devices, infrared probes, infrared fences, etc.
  • Figure 2 exemplarily shows one client device 210 and two server devices 220.
  • the network structure may include multiple client devices and other numbers of server devices. Not limited.
  • FIG. 3 is a schematic diagram 1 of the flow of an information processing method provided by an embodiment of the present application.
  • the execution subject of the information processing method is a first device, and the first device may be the client device 210 shown in FIG. 2.
  • the information processing method includes the following.
  • Step 310 Obtain the first identity information of the first security domain.
  • the security domain can also be referred to as a security domain network, which is a specific Internet of Things network.
  • the security domain network has an independent security protocol (or security mechanism), and IoT devices in the same security domain network can interconnect, communicate, discover each other, and transmit instructions to each other. It is understandable that two devices that are not in the same security domain network are restricted by the security protocol in the security domain network, and therefore cannot mutually access the Internet of Things devices in the other's security domain network.
  • the related information of the security domain to which each device belongs can be configured by the user, or can be configured by other devices (for example, an Internet of Things server), which is not limited in the embodiment of the present application.
  • the relevant information of the security domain to which the device belongs includes at least the identity information of the security domain; here, the identity information of the security domain can identify the security domain.
  • the identity information of the security domain may include identification information of the security domain and/or name information of the security domain.
  • the first identity information may include identification information of the first security domain and/or name information of the first security domain.
  • the first security domain may be the security domain to which the first device belongs; the first security domain may also be any security domain except the security domain to which the first device belongs.
  • a security domain is not limited.
  • Step 320 Obtain first discovery request information based on the first identity information; the first discovery request information is used to request a target resource of a target device that matches the first identity information;
  • the first device may construct the first discovery request information based on the first identity information; that is, the first discovery request information carries the first identity information, which is used to request the network and the first discovery request information. A target resource stored in a target device whose identity information matches.
  • the first device adds the security domain-based filter condition to the first discovery request information, so that only the device that receives the first discovery request information and the identity information of the security domain matches the first identity information will respond to the first discovery request information.
  • Discovery request information thereby avoiding that all devices in the network that have received the discovery request information return a resource list, leading to the problem of information redundancy.
  • the discovery of the target resource of the target device that matches the first identity information through the first discovery request in this embodiment of the application can have two meanings: first, the first device accesses the local area network for the first time or starts the device discovery mechanism When the first discovery request is used to discover the target device in the local area network that matches the first identity information, and the target resource stored in each target device; second, the first device may be started when the location of the device in the local area network is known In the resource discovery mechanism, the target resource stored in the known device in the local area network is discovered through the first discovery request. That is, the first discovery request in the embodiment of the present application can be used to realize device discovery in the network, and can also realize resource discovery in the network.
  • Step 330 Send the first discovery request information.
  • the first device may send the first discovery request information to at least one second device.
  • the second device may be the server device 220 and the server device 230 shown in FIG. 2.
  • the first device may send the first discovery request information to at least one second device in a broadcast or multicast manner.
  • the first device sending the first discovery request information to at least one second device in a broadcast or multicast manner may be executed when the first device accesses the local area network for the first time or starts the device discovery mechanism.
  • the first device may also send the first discovery request information to the at least one second device in a unicast manner.
  • the first device sending the first discovery request information in a unicast manner may be executed when the address of the second device is known.
  • the first device obtains the first identity information of the first security domain; further, based on the first identity information, the first discovery request information is obtained; the first discovery request information is used After requesting to match the target resource of the target device with the first identity information; sending the first discovery request information. That is, the first discovery request information is only used to request the target resource stored in the target device that matches the first security domain. In this way, the information received by the first device is all related to the first security domain (that is, the first identity information). ) The target resource of the matched target device; in this way, the redundancy of information is reduced, and the processing efficiency of the first device is improved.
  • the implementation process of obtaining the first identity information of the first security domain is:
  • the identity information of the security domain to which the first device belongs is determined as the first identity information of the first security domain.
  • the first security domain may be the security domain to which the first device belongs
  • the first identity information is the identity information of the security domain to which the first device belongs.
  • the first device can view the locally configured security domain resource, that is, the security domain information stored in the /oic/sec/sdi resource, and find the first identity information in the security domain information.
  • the first identity information may be security domain identification information and/or security domain name information of the security domain to which the first device belongs.
  • the first device determines the identity information of the security domain to which the first device belongs as the first identity information of the first security domain, and constructs the first discovery request information. In this way, by directly using the identity information of the security domain to which one belongs as the first identity information to construct the first discovery request information, it is possible to accurately discover devices in the same security domain as the first device, that is, devices that can communicate with the first device. Improve discovery efficiency.
  • the implementation process of obtaining the first identity information of the first security domain is:
  • the setting instruction includes identity information of a specific security domain
  • the first device can obtain the setting instruction input by the user through any type of input module, and respond to the received setting instruction, and include the identity information of the specific security domain carried in the setting instruction, Set as the first identity information of the first security domain, that is, the first identity information may be the identity information of any security domain entered by the user.
  • the identity information of a specific security domain input by the user may be security domain identification information of any security domain, and/or security domain name information.
  • the first device constructs the first discovery request information based on the first identity information.
  • the first device can construct the first discovery request information based on the identity information of any security domain entered by the user to discover the target information of the target device that matches the entered security domain, that is, the information that the user expects to obtain; device discovery is improved, And the flexibility of resource discovery.
  • step 320 the following steps are further included before obtaining the first discovery request information based on the first identity information in step 320 :
  • Step 311 Obtain the privacy identifier of the security domain to which the first device belongs.
  • Step 312 If the privacy identifier indicates that the resource of the first device is a private resource, then generating and presenting confirmation information; the confirmation information is used to confirm whether discovery is based on the identity information of the security domain;
  • Step 313 Receive feedback information for the confirmation information.
  • step 320 obtains the first discovery request information based on the first identity information, which can be implemented through step 320':
  • Step 320' If the feedback information indicates discovery based on the identity information of the security domain, construct first discovery request information based on the first identity information.
  • the security domain information of each device may also include a privacy identifier priv.
  • the privacy identifier can be used to indicate the visibility of the security domain information in the device, and can also be understood as the visibility of the security domain resources.
  • the privacy identifier priv of a device When the privacy identifier priv of a device is set to "false", it is considered that the security domain resources of the device are visible, so that the security domain information of the device is disclosed in the /oic/res resource of the device (specifically, it can be the identity of the security domain) information).
  • the privacy flag priv of a device When the privacy flag priv of a device is set to "true”, the security domain resource of the device is considered to be an invisible resource, so that the security domain information of the device is not disclosed in the /oic/res resource of the device (specifically, it can be Security domain identity information).
  • the first device may first check whether its privacy identifier indicates that the security domain resource of the first device is an invisible resource.
  • the security domain resource of the first device is an invisible resource, there may be a risk of resource leakage when performing device discovery and resource discovery. Therefore, when the privacy identifier indicates that the resource of the first device is an invisible resource, it is also necessary to confirm to the user whether to perform discovery based on the security domain.
  • the first device may present confirmation information to the user through the interactive interface of the display device to inquire whether to perform device discovery or resource discovery based on the security domain.
  • the first device waits for the feedback information input by the user after outputting the confirmation information. If the received feedback information is used to indicate discovery based on the identity information of the security domain, the first discovery request information is obtained based on the first identity information. In this way, the security of data transmission is improved.
  • steps 311 to 313 may be executed before step 310, may also be executed after step 310, or may be executed simultaneously with step 310.
  • steps 311 to 313 may be executed before step 310, may also be executed after step 310, or may be executed simultaneously with step 310.
  • the embodiments of this application are not limited here.
  • step 320 obtains the first discovery request information based on the first identity information, including:
  • URI uniform resource identifier
  • the first discovery request information is constructed.
  • the first device may determine the request address and the URI corresponding to the requested target resource according to the user's device discovery or resource discovery requirements after determining the first identity information of the first security domain. Further, the first discovery request information is constructed according to the URI of the target resource, the request address, and the first identity information.
  • the request address may be a multicast address.
  • the request address may also be a unicast address.
  • the request address can be determined according to the user's device discovery or resource discovery requirements. If the user needs to request all devices in the LAN, the requested address can be a multicast address. When the user knows the address of part of the device and needs to request the resource of that part of the device, he can directly use the address of the part of the device as the request address.
  • the information processing method provided by the embodiment of the present application is described in detail above with reference to FIGS. 3 and 4 from the perspective of the first device.
  • the following describes in detail the information processing method provided by the embodiment of the present application from the perspective of the second device with reference to FIG. 5 and FIG.
  • the method used for information processing It should be understood that the description on the first device side and the description on the second device side correspond to each other, and similar descriptions can be referred to above. To avoid repetition, details are not repeated here.
  • FIG. 5 is a schematic diagram of the third flow of an information processing method provided by an embodiment of the present application.
  • the execution subject of the information processing method is a second device, and the second device may be the server device 220 or the server device 230 shown in FIG. 2.
  • the information processing method includes the following.
  • Step 510 Receive first discovery request information; the first discovery request information includes the first identity information of the first security domain; the first discovery request information is used to discover the target resource of the target device that matches the first identity information;
  • the second device receives the first discovery request information sent by the first device.
  • the second device receives the first discovery request information sent by the first device and forwarded by other devices.
  • Step 520 Determine whether to send the target resource based on the first identity information.
  • the first discovery request information is used to request the target resource stored in the target device that matches the first identity information.
  • the second device can parse out the first identity information of the first security domain from the first discovery request information, and determine itself based on the first identity information Whether it matches with the first identity information, if it matches, respond to the first discovery request information and determine to send its own target resource; if it does not match, then do not respond to the first discovery request information and determine not to send its own target resource.
  • the second device matches the first identity information carried in the first discovery request information can it respond to the first discovery request information and return the target resource in the second device.
  • the information received by the first device is the target resource of the target device that matches the first security domain (that is, the first identity information); in this way, the redundancy of the information is reduced and the processing efficiency of the first device is improved.
  • the implementation process of determining whether to send the target resource of the second device based on the first identity information is:
  • Step 5201 Obtain resource description information of the second device.
  • the resource description information of the second device may be attribute information in the /oic/res resource of the second device.
  • Step 5202 Determine whether the resource description information of the second device includes the second identity information; the second identity information is the identity information of the security domain to which the second device belongs;
  • the second identity information may include identification information of the security domain to which the second device belongs and/or name information of the security domain to which the second device belongs.
  • the second device may search for the identification information of the security domain to which the second device belongs and/or the name information of the security domain to which the second device belongs from the attribute information of the /oic/res resource.
  • the second device when the first identity information is the identification information of the first security domain, the second device needs to obtain the identification information of the security domain to which it belongs to match the first identity information.
  • the first identity information is the name information of the first security domain
  • the second device needs to obtain the name information of the security domain to which the second device belongs to match the first identity information.
  • the first identity information is the identification information and name information of the first security domain
  • the second device needs to obtain the identification information and name information of the security domain to which the second device belongs to match the first identity information.
  • the identity information is matched, which is not limited here in the embodiment of the present application.
  • Step 5203 If the resource description information of the second device includes the second identity information, and the second identity information matches the first identity information, determine the target resource to be sent.
  • the second identity information matches the first identity information, it can be considered that the security domain of the second device and the security domain of the first device are the same security domain, and the second device responds to the first discovery request information, that is, the second device obtains The first discovers the target resource to be requested in the request information, and sends the target resource.
  • Step 5204 If the resource description information of the second device includes the second identity information, and the second identity information does not match the first identity information, it is determined not to send the target resource.
  • the second identity information does not match the first identity information, it can be considered that the security domain of the second device is not the same security domain as the security domain of the first device, and the second device does not respond to the first discovery request information, that is, the second device does not respond to the first discovery request information.
  • the device does not send the target resource.
  • Step 5205 If the resource description information of the second device does not include the second identity information, it is determined not to send the target resource.
  • the resource description information of the second device does not include the second identity information, which may be caused by two situations: Case 1, the second device does not implement security domain resources, or the second device is not configured with security domain information; Case 2, The privacy flag in the security domain information of the second device is set to "true". In the above two cases, the second device and the first device cannot realize device discovery or resource discovery based on the security domain. Therefore, when the second identity information is included in the resource description information of the second device, the second device can determine that it is not In response to the first discovery request message, the target resource is not sent.
  • the method further includes the following steps:
  • the second device After the second device determines that the second identity information matches the first identity information, it can determine that it is the target device. After determining to send the target resource, the second device executes a response to the first discovery request information, that is, obtains the target resource required in the first discovery request, and sends the target resource to the first device.
  • the second device sends the target resource to the first device in a unicast manner.
  • the second device matches the first identity information carried in the first discovery request information can it respond to the first discovery request information and return the target resource in the second device.
  • the information received by the first device is the target resource of the target device that matches the first security domain (that is, the first identity information); in this way, the redundancy of the information is reduced and the processing efficiency of the first device is improved.
  • server devices in the local area network 700, namely device 1, device 2, and device 3, and one client device.
  • Device 1, Device 2, and Device 3 form a multicast group named "All Nodes", where the multicast address of the "All Nodes" multicast group includes: multicast service address: ff02::158, port information 5683.
  • An example of the /oic/res resource of device 1 is as follows (ignoring the list of common resources):
  • An example of the /oic/res resource of device 2 is as follows (ignoring the list of common resources):
  • the client device accesses the local area network 700 for the first time or the client device starts the device discovery mechanism, refer to the device discovery or resource discovery flow diagram 1 shown in FIG. 8.
  • the operation flow of the client device includes the following steps:
  • Step 1 The client device (ie, the first device) checks its own security domain information, and obtains the identity information of the security domain to which the client device belongs.
  • the identity information of the security domain to which the client belongs is security domain identification information (sduuid); for example, the sduuid of the client device is 12345678-1234-1234-1234-123412341234.
  • the identity information of the security domain to which the client belongs may also be security domain name information (sdname).
  • sdname security domain name information
  • the sdname of the client device is Alice’s Home.
  • sduuid and sdname can also be used as the identity information of the security domain to which the client belongs.
  • Step 2 The client device (ie, the first device) constructs the first discovery request information based on the identity information obtained in step 1, and the first discovery request may be sent in a multicast manner.
  • the client device when the client device needs to perform device discovery, it can join the "all nodes" multicast group shown in FIG. All devices send the first discovery request, and the URI of the requested resource is "/oic/res".
  • the first discovery request information may be constructed based on the Constrained Application Protocol (CoAP).
  • CoAP Constrained Application Protocol
  • the client device can be based on the multicast address ([ff02::158]:5683), The target resource oic/res and the sduuid value of the security domain to which the client device belongs construct the first discovery request information.
  • the first discovery request information may be:
  • Step 3 Device 1, device 2, and device 3 receive the first discovery request information, and parse out the target resource (i.e. /oic/res resource) indicated by the first discovery request information and the filter condition (i.e. the security of the client device Domain identity information), and then device 1, device 2, and device 3 determine whether there are sduuid and/or sdname attributes in the attributes of their/oic/res resources (that is, second identity information).
  • the target resource i.e. /oic/res resource
  • the filter condition i.e. the security of the client device Domain identity information
  • the first identity information carried in the first discovery request information sent by the client device is sduuid
  • device 1, device 2, and device 3 determine whether their /oic/res resources have the sduuid attribute.
  • the first identity information carried in the first discovery request information sent by the client device is the sdname
  • the device 1, the device 2, and the device 3 determine whether their /oic/res resources have the sduuid attribute.
  • the first identity information carried in the first discovery request information sent by the client device is sduuid and sdname
  • device 1, device 2, and device 3 determine whether their /oic/res resources have sduuid and sdname attributes.
  • Step 4a After receiving the first discovery request information, the device 1 checks that the attribute information of its/oic/res resource includes the sduuid and/or sdname attributes.
  • the sduuid value of device 1 is "12345678-1234-1234-1234-123412341234", and the value of sdname is "Alice's Home", which matches the sduuid and/or sdname value in the first discovery request.
  • step 5a
  • Step 5a Device 1 returns the /oic/res resource to the client device through unicast.
  • device 1 returns the resource list "links" in the /oic/res resource, which specifically includes:
  • Step 4b After receiving the first discovery request information, the device 2 checks that the attribute information of its/oic/res resource includes the sduuid and/or sdname attributes.
  • the sduuid value of device 2 is "dc70373c-1e8d-4fb3-962e-017eaa863989", and the sdname value is "Bob's Home", which does not match the sduuid and/or sdname values in the first discovery request information.
  • step 5b is performed.
  • Step 5b The device 2 determines that it does not respond to the first discovery request information, that is, it does not send the /oic/res resource.
  • Step 4c After receiving the first discovery request information, the device 3 checks that there is no sduuid and sdname attributes in the attribute information of its/oic/res resource.
  • Step 5c The device 3 determines that it does not respond to the first discovery request information, that is, it does not send the /oic/res resource.
  • steps 4a, 4b, and 4c can be performed at the same time.
  • the client device receives the resource list returned by all discoverable devices in the same security domain as the client device in the local area network 700, and can display it to the user through an interactive interface for subsequent control.
  • the information received by the client device is the device resource of the device that matches the security domain to which the client belongs; in this way, the redundancy of the information is reduced and the processing efficiency of the client device is improved.
  • the client device that is, the first device described above performs LAN device discovery or The operation process of resource discovery includes the following steps:
  • Step 1 The client device receives the setting instruction input by the user on the interactive interface, and the setting instruction is used to set the first identity information of the first security domain.
  • the user can set the identity information of any security domain as a filter condition for device discovery. That is, the user can input the identity information of any security domain to form the first discovery request information, and discover the device in the same security domain as the security domain through the first discovery request information.
  • the client device may receive the security domain identification information entered by the user on the interactive interface to construct the first discovery request information.
  • the user enters the security domain identification information duuid in the interactive interface of the client device as "12345678-1234- 1234-1234-123412341234".
  • the client device may receive the security domain name information input by the user on the interactive interface to construct the first discovery request information.
  • the user inputs the security domain name information on the interactive interface of the client device as "Alice's Home".
  • Step 2 The client device constructs a first discovery request message based on the first identity information obtained in step 1; and sends the first discovery request information in a multicast manner in the local area network 700.
  • the client device can use the multicast address ([ff02::158]:5683), the target resource oic/ res, and the name information of the security domain to which the client device belongs, and the sdname value constructs the first discovery request information.
  • the first discovery request information may be:
  • Step 3 Device 1, device 2, and device 3 receive the first discovery request information, and parse out the target resource (ie /oic/res resource) and filter condition (ie, the first identity information of the first security domain set by the user), Furthermore, device 1, device 2, and device 3 determine whether there are sduuid and/or sdname attributes (that is, second identity information) in the attributes of their /oic/res resources.
  • target resource ie /oic/res resource
  • filter condition ie, the first identity information of the first security domain set by the user
  • Step 4a After receiving the first discovery request information, the device 1 checks that the attribute information of its/oic/res resource includes the sduuid and/or sdname attributes.
  • the sduuid value of device 1 is "12345678-1234-1234-1234-123412341234", and the value of sdname is "Alice's Home", which matches the sduuid and/or sdname value in the first discovery request.
  • step 5a
  • Step 5a Device 1 returns the /oic/res resource to the client device through unicast.
  • device 1 returns the resource list "links" in the oic/res resource, which specifically includes:
  • Step 4b After receiving the first discovery request information, the device 2 checks that the attribute information of its/oic/res resource includes the sduuid and/or sdname attributes.
  • the sduuid value of device 2 is "dc70373c-1e8d-4fb3-962e-017eaa863989", and the sdname value is "Bob's Home", which does not match the sduuid and/or sdname values in the first discovery request information.
  • step 5b is performed.
  • Step 5b The device 2 determines that it does not respond to the first discovery request information, that is, it does not send the /oic/res resource.
  • Step 4c After receiving the first discovery request information, the device 3 checks that there is no sduuid and sdname attributes in the attribute information of its/oic/res resource.
  • Step 5c The device 3 determines that it does not respond to the first discovery request information, that is, it does not send the /oic/res resource.
  • steps 4a, 4b, and 4c can be performed at the same time.
  • the client device receives the resource list returned by all discoverable devices in the same security domain as the client device in the local area network 700, and can display it to the user for subsequent control. In this way, the redundancy of information is reduced, and the processing efficiency of the client device is improved.
  • the client device that is, the first device described above performs LAN device discovery or The operation process of resource discovery includes the following steps:
  • Step 1 The client device (ie, the first device) checks its own security domain information, and obtains the identity information of the security domain to which the client device belongs.
  • the identity information of the security domain to which the client belongs is security domain identification information (sduuid); for example, the sduuid of the client device is 12345678-1234-1234-1234-123412341234.
  • the identity information of the security domain to which the client belongs may also be security domain name information (sdname).
  • sdname security domain name information
  • the sdname of the client device is Alice’s Home.
  • sduuid and sdname can also be used as the identity information of the security domain to which the client belongs.
  • Step 2 The client device checks the privacy identifier in its own security domain information, that is, the value of the priv attribute.
  • the confirmation message is used to ask the user whether to perform device discovery based on the identity information of the security domain And/or resource discovery.
  • Step 4 The client device receives feedback information input by the user, and the feedback information indicates discovery based on the identity information of the security domain.
  • Step 5 The client device constructs first discovery request information based on the identity information obtained in step 1, and the first discovery request may be sent in a multicast manner.
  • the first discovery request information may be:
  • Step 6 Device 1, device 2, and device 3 receive the first discovery request information, and parse out the target resource (ie /oic/res resource) indicated by the first discovery request information, and filter conditions (ie, the security of the client device Domain identity information), and then device 1, device 2, and device 3 determine whether there are sduuid and/or sdname attributes in the attributes of their/oic/res resources (that is, second identity information).
  • target resource ie /oic/res resource
  • filter conditions ie, the security of the client device Domain identity information
  • the first identity information carried in the first discovery request information sent by the client device is sduuid
  • device 1, device 2, and device 3 determine whether their /oic/res resources have the sduuid attribute.
  • the first identity information carried in the first discovery request information sent by the client device is the sdname
  • the device 1, the device 2, and the device 3 determine whether their /oic/res resources have the sduuid attribute.
  • the first identity information carried in the first discovery request information sent by the client device is sduuid and sdname
  • device 1, device 2, and device 3 determine whether their /oic/res resources have sduuid and sdname attributes.
  • Step 7a After receiving the first discovery request information, the device 1 checks that the attribute information of its/oic/res resource includes the sduuid and/or sdname attributes.
  • the sduuid value of device 1 is "12345678-1234-1234-1234-123412341234", and the value of sdname is "Alice's Home", which matches the sduuid and/or sdname value in the first discovery request.
  • step 8a is performed.
  • Step 8a Device 1 returns the /oic/res resource to the client device in a unicast manner.
  • device 1 returns the resource list "links" in the /oic/res resource, which specifically includes:
  • Step 7b After receiving the first discovery request information, the device 2 checks that the attribute information of its/oic/res resource includes the sduuid and/or sdname attributes.
  • the sduuid value of device 2 is "dc70373c-1e8d-4fb3-962e-017eaa863989", and the sdname value is "Bob's Home", which does not match the sduuid and/or sdname values in the first discovery request information.
  • step 8b is performed.
  • Step 8b The device 2 determines that it does not respond to the first discovery request information, that is, it does not send the /oic/res resource.
  • Step 7c After receiving the first discovery request information, the device 3 checks that there is no sduuid and sdname attributes in the attribute information of its/oic/res resource.
  • step 8c is performed.
  • Step 8c The device 3 determines that it does not respond to the first discovery request information, that is, it does not send the /oic/res resource.
  • steps 7a, 7b, and 7c can be performed at the same time.
  • the client device receives the resource list returned by all discoverable devices in the same security domain as the client device in the local area network 700, and can display it to the user for subsequent control. In this way, the redundancy of information is reduced, and the processing efficiency of the client device is improved.
  • an embodiment of the present application provides an information processing device, which can be applied to the first device described above.
  • the information processing device includes:
  • the first obtaining unit 1101 is configured to obtain the first identity information of the first security domain
  • the first processing unit 1102 is configured to obtain first discovery request information based on the first identity information; the first discovery request information is used to request a target resource of a target device that matches the first identity information;
  • the first transceiver unit 1103 is configured to send the first discovery request information.
  • the first obtaining unit 1101 is further configured to determine the identity information of the security domain to which the first device belongs as the first identity information of the first security domain.
  • the first obtaining unit 1101 obtains a setting instruction;
  • the setting instruction includes identity information of a specific security domain;
  • the first processing unit 1102 is configured to respond to the setting instruction and determine the first identity information of the first security domain by using the identity information of the specific security domain.
  • the first obtaining unit 1101 is configured to obtain the privacy identifier of the security domain to which the first device belongs;
  • the first processing unit 1102 is configured to generate and present confirmation information if the privacy identifier indicates that the resource of the first device is a private resource; the confirmation information is used to confirm whether discovery is based on the identity information of the security domain;
  • the first transceiver unit 1103 is configured to receive feedback information for the confirmation information
  • the first processing unit 1102 is configured to, if the feedback information indicates discovery based on the identity information of the security domain, construct the first discovery request information based on the first identity information.
  • the first transceiving unit 1103 is configured to send the first discovery request information to at least one second device.
  • the first identity information includes identification information of the first security domain and/or name information of the first security domain.
  • the first obtaining unit 1101 is configured to obtain the resource uniform identifier of the target resource and the request address;
  • the first processing unit 1102 is configured to construct the first discovery request information based on the resource uniform identifier of the target resource, the request address, and the first identity information.
  • the request address is a multicast address.
  • an embodiment of the present application provides an information processing device, which can be applied to the second device described above.
  • the information processing device includes:
  • the second transceiving unit 1201 is configured to receive first discovery request information; the first discovery request information includes first identity information of the first security domain; the first discovery request information is used for discovering and the first identity information The target resource of the matched target device;
  • the second processing unit 1202 is configured to determine whether to send the target resource based on the first identity information.
  • the second processing unit 1202 is further configured to determine whether the resource description information of the second device includes second identity information; the second identity information is the identity of the security domain to which the second device belongs Information; if the resource description information includes the second identity information, and the second identity information matches the first identity information, it is determined to send the target resource.
  • the second processing unit 1202 is further configured to determine that if the resource description information includes the second identity information, and the second identity information does not match the first identity information, Send the target resource.
  • the second processing unit 1202 is further configured to determine not to send the target resource if the resource description information of the second device does not include the second identity information.
  • the information processing device further includes a second acquiring unit
  • the second processing unit 1202 is configured to determine that the second device is the target device
  • a second acquiring unit configured to acquire the target resource in the second device
  • the second transceiver unit 1201 is configured to send the target resource to the first device.
  • the application embodiment also provides a device.
  • the first device shown in FIG. 13 includes: a first transceiver 1301, a first processor 1302, and a first memory 1303 storing a computer program;
  • the first transceiver 1301, the first processor 1302, and the first memory 1303 communicate through a first communication bus 1304;
  • the first processor is configured to implement communication with another device through the first transceiver 1301; wherein,
  • the first processor 1302 runs the computer program stored in the first memory 1303, it executes the following steps: obtain the first identity information of the first security domain; and obtain the first identity information based on the first identity information.
  • Discovery request information the first discovery request information is used to request the target resource of the target device that matches the first identity information
  • the first transceiver 1301 when running the computer program stored in the first memory 1303 , Perform the following steps: send the first discovery request information.
  • the first processor 1302 when the first processor 1302 runs the computer program stored in the first memory 1303, it executes the following steps: Determine the identity information of the security domain to which the first device belongs as the first The first identity information of the security domain.
  • the first processor 1302 when the first processor 1302 runs the computer program stored in the first memory 1303, it executes the following steps: obtaining a setting instruction; the setting instruction includes identity information of a specific security domain; and responding to the Setting instructions, and determining the first identity information of the first security domain with the identity information of the specific security domain.
  • the first processor 1302 when the first processor 1302 runs the computer program stored in the first memory 1303, it performs the following steps: obtain the privacy identifier of the security domain to which the first device belongs; if the privacy identifier indicates If the resource of the first device is a private resource, then confirmation information is generated and presented; the confirmation information is used to confirm whether discovery is based on the identity information of the security domain; receiving feedback information for the confirmation information; if the feedback information Instructing to perform discovery based on the identity information of the security domain, then construct the first discovery request information based on the first identity information.
  • the first transceiver 1301 when the first transceiver 1301 runs the computer program stored in the first memory 1303, it performs the following steps: sending the first discovery request information to at least one second device.
  • the first identity information includes identification information of the first security domain and/or name information of the first security domain.
  • the following steps are performed: obtain the resource uniform identifier URI of the target resource, and the request address; resources based on the target resource A uniform identifier, the request address, and the first identity information construct the first discovery request information.
  • the requested address is a multicast address.
  • the application embodiment also provides a device.
  • a device Refer to the schematic diagram of the hardware structure of a second device shown in FIG. 13.
  • the second device shown in FIG. 14 includes: a second transceiver 1401, a second processor 1402, and a second memory 1403 storing a computer program;
  • the second transceiver 1401, the second processor 1402, and the second memory 1403 communicate through a second communication bus 1404;
  • the second processor 1402 is configured to implement communication with another device through the second transceiver 1401; wherein,
  • the second transceiver 140 when running the computer program stored in the second memory 1403, executes the following steps: receiving first discovery request information; the first discovery request information includes the first identity information of the first security domain The first discovery request information is used to request target resources of a target device that matches the first identity information;
  • the second processor 1402 runs the computer program stored in the second memory 1403, it executes the following steps: based on the first identity information, determine whether to send the target resource.
  • the second processor 1402 when the second processor 1402 runs the computer program stored in the second memory 1403, it may also perform the following steps: obtain the resource description information of the second device; determine the resource description Whether the information includes second identity information; the second identity information is the identity information of the security domain to which the second device belongs; if the resource description information includes the second identity information, and the second identity information If it matches the first identity information, it is determined to send the target resource.
  • the second processor 1402 when running the computer program stored in the second memory 1403, may also perform the following steps: if the resource description information includes the second identity information, and If the second identity information does not match the first identity information, it is determined not to send the target resource.
  • the second processor 1402 when the second processor 1402 runs the computer program stored in the second memory 1403, it may also perform the following steps: if the resource description information does not include the second identity information, It is determined not to send the target resource.
  • the second processor 1402 when the second processor 1402 runs the computer program stored in the second memory 1403, it may also perform the following steps: determine that the second device is the target device, and obtain the The target resource in the second device;
  • the second transceiver 1401 executes the following steps when running the computer program stored in the second memory 1403: sending the target resource to the first device.
  • first memory and the second memory in this embodiment may be volatile memory or non-volatile memory, and may also include both volatile and non-volatile memory.
  • non-volatile memory can be Read Only Memory (ROM), Programmable Read-Only Memory (PROM), Erasable Programmable Read-Only Memory (Erasable Programmable Read-Only Memory) , EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Ferromagnetic Random Access Memory (FRAM), Flash Memory, Magnetic Surface Memory , CD-ROM, or CD-ROM (Compact Disc Read-Only Memory, CD-ROM); magnetic surface memory can be disk storage or tape storage.
  • the volatile memory may be a random access memory (Random Access Memory, RAM), which is used as an external cache.
  • RAM Random Access Memory
  • SRAM static random access memory
  • SSRAM synchronous static random access memory
  • dynamic random access memory dynamic random access memory
  • DRAM Dynamic Random Access Memory
  • SDRAM Synchronous Dynamic Random Access Memory
  • DDRSDRAM Double Data Rate Synchronous Dynamic Random Access Memory
  • ESDRAM Double Data Rate Synchronous Dynamic Random Access Memory
  • ESDRAM Enhanced Synchronous Dynamic Random Access Memory
  • SLDRAM synchronous connection dynamic random access memory
  • SLDRAM synchronous connection dynamic random access memory
  • DDRRAM direct memory bus random access memory
  • DRRAM Direct Rambus Random Access Memory
  • the embodiment of the present application also provides a computer storage medium, which is specifically a computer-readable storage medium.
  • Computer instructions are stored thereon.
  • the computer storage medium is located in the terminal, when the computer instructions are executed by the processor, any step in the information processing method described in the embodiment of the present application is implemented.
  • the size of the sequence numbers of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not correspond to the embodiments of the present application.
  • the implementation process constitutes any limitation.
  • the disclosed system, device, and method can be implemented in other ways.
  • the device embodiments described above are merely illustrative, for example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of this application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disks or optical disks and other media that can store program codes. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Computer Security & Cryptography (AREA)
  • Automation & Control Theory (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例提供一种信息处理方法，应用于第一设备，所述方法包括：获取第一安全域的第一身份信息；基于所述第一身份信息，得到第一发现请求信息；所述第一发现请求信息用于请求与所述第一身份信息匹配的目标设备的目标资源；发送所述第一发现请求信息。本申请实施例同时还提供一种信息处理装置、设备和计算机存储介质。

Description

信息处理方法及装置、设备、计算机存储介质 技术领域
本申请涉及物联网技术领域，尤其涉及一种信息处理方法及装置、设备、计算机存储介质。
背景技术
物联网(Internet of things，IOT)是新一代信息技术的重要组成部分。IOT是按约定的协议，把任何IOT设备与互联网相连接，进行信息交换和通信，以实现对设备的智能化识别、定位、跟踪、监控和管理的一种网络。
随着IOT技术的普及，部分需要相互协作的IOT设备往往需要进行设备发现，以及设备资源的发现。目前，用于物联网设备及设备资源发现方法中，第一设备(例如客户端)可以向局域网中的多个第二设备(例如服务端)发送发现请求，接收到发现请求的每个第二设备都会响应该发现请求，向第一设备返回自己的资源列表。
这样，第一设备会接收到多个第二设备返回的资源列表，在收到的资源列表中很有可能包括第一设备并不期望的信息(例如，第一设备无法控制的第二设备返回的资源列表)；如此，造成信息冗余，降低了第一设备的数据处理效率。
发明内容
本申请实施例提供了一种信息处理方法及装置、设备、计算机存储介质。
第一方面，本申请实施例提供一种信息处理方法，应用于第一设备，所述方法包括：
获取第一安全域的第一身份信息；
基于所述第一身份信息，得到第一发现请求信息；所述第一发现请求信息用于请求与所述第一身份信息匹配的目标设备的目标资源；
发送所述第一发现请求信息。
第二方面，本申请实施例提供一种信息处理方法，应用于第二设备，所述方法包括：
接收第一发现请求信息；所述第一发现请求信息包括第一安全域的第一身份信息；所述第一发现请求信息用于请求与所述第一身份信息匹配的目标设备的目标资源；
基于所述第一身份信息，确定是否发送所述目标资源。
第三方面，本申请实施例提供一种信息处理装置，应用与第一设备，所述信息处理装置包括：
第一获取单元，配置为获取第一安全域的第一身份信息；
第一处理单元，配置为基于所述第一身份信息，得到第一发现请求信息；所述第一发现请求信息用于请求与所述第一身份信息匹配的目标设备的目标资源；
第一收发单元，配置为发送所述第一发现请求信息。
第四方面，本申请实施例提供一种信息处理装置，应用于第二设备，所述信息处理装置包括：
第二收发单元，配置为接收第一发现请求信息；所述第一发现请求信息包括第一安全域的第一身份信息；所述第一发现请求信息用于发现与所述第一身份信息匹配的目标 设备的目标资源；
第二处理单元，配置为基于所述第一身份信息，确定是否发送所述目标资源。
第五方面，本申请实施例提供一种设备，所述设备包括：第一收发器、第一处理器和存储有计算机程序的第一存储器；
所述第一收发器、所述第一处理器和所述第一存储器之间通过第一通信总线进行通信；
所述第一处理器，配置为通过所述收发器实现与另一设备的通信；其中，
所述第一处理器，还配置为结合所述第一收发器，运行所述第一存储器中存储的所述计算机程序时，执行第一方面所述信息处理方法的步骤。
第六方面，本申请实施例提供一种设备，所述设备包括：第二收发器、第二处理器和存储有计算机程序的第二存储器；
所述第二收发器、所述第二处理器和所述第二存储器之间通过第二通信总线进行通信；
所述第二处理器，配置为通过所述收发器实现与另一设备的通信；其中，
所述第二处理器，还配置为结合所述第二收发器，运行所述第二存储器中存储的所述计算机程序时，执行所述第二方面信息处理方法的步骤。
第七方面，本申请实施例提供一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被第一处理器执行实现第一方面所述方法的步骤；或者；所述计算机程序被第二处理器执行第二方面所述方法的步骤。
本申请实施例提供的信息处理方法及装置、设备、计算机存储介质，其中，第一设备获取第一安全域的第一身份信息；基于所述第一身份信息，得到第一发现请求信息；所述第一发现请求信息用于请求与所述第一身份信息匹配的目标设备的目标资源；发送所述第一发现请求信息。也就是说，第一发现请求信息仅用于请求与第一安全域匹配的目标设备中存储的目标资源，这样，第一设备接收到的信息都是与第一安全域(即第一身份信息)匹配的目标设备的目标资源；如此，降低信息的冗余度，提高第一设备的处理效率。
附图说明
图1为本申请实施例提供的一种示例性的发现过程的应用场景示意图；
图2为本申请实施例提供的一种网络结构示意图；
图3为本申请实施例提供的一种信息处理方法流程示意图一；
图4为本申请实施例提供的一种信息处理方法流程示意图二；
图5为本申请实施例提供的一种信息处理方法流程示意图三；
图6为本申请实施例提供的一种信息处理方法流程示意图四；
图7为本申请实施例提供的一种信息处理方法的应用场景示意图；
图8为本申请实施例提供的一种设备发现或资源发现流程示意图一；
图9为本申请实施例提供的一种设备发现或资源发现流程示意图二；
图10为本申请实施例提供的一种设备发现或资源发现流程示意图三；
图11为本申请实施例提供的一种信息处理装置结构组成示意图一；
图12为本申请实施例提供的一种信息处理装置结构组成示意图二；
图13为本申请实施例提供的一种第一设备硬件结构组成示意图一；
图14为本申请实施例提供的一种第二设备硬件结构组成示意图二。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请实施方式作进一步地详细描述，所附附图仅供参考说明之用，并非用来限定本发明实施例。
需要说明的是，本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别不同对象，而不是用于描述特定顺序。此外，术语“包括”和“具有”以及它们任何变形，意图在于覆盖不排他的包含。例如包含了一系列步骤或单元的过程、方法、系统、产品或设备没有限定于已列出的步骤或单元，而是可选地还包括没有列出的步骤或单元，或可选地还包括对于这些过程、方法、产品或设备固有的其他步骤或单元。
实际应用中，可以使用信息公开(well known)资源oic/res资源作为默认的发现机制。参见图1所示的发现过程的应用场景示意图，该应用场景可以包括多个服务端设备(包括如图1所示的冰箱11、电灯12以及温度传感器13)和一客户端设备(如图1所示的智能手机14)。具体发现过程如下：
(1)每个服务端设备都可以将可发现的资源更新到该服务端本地的/oic/res资源中，也就是说，每次在服务端设备上实例化新的可发现资源时，都需要把该实例化资源更新到服务端设备本地的/oic/res资源。
(2)为了发现多个服务端设备上的资源或资源类型，客户端设备可以向多个服务端设备的/oic/res资源发出检索(RETRIEVE)请求。另外，客户端设备可以在RETRIEVE请求中使用查询条件来限定发现的对象，查询条件可以基于资源类型，接口或属性进行限定。
(3)接收RETRIEVE请求的服务端设备响应该请求，返回/oic/res资源中保存的资源列表。
也就是说，只要接收到RETRIEVE请求的服务端设备都需要响应该请求，向客户端设备返回其资源列表。客户端设备接收到的资源列表中，可能包含客户端设备并不期望的信息，例如与客户端设备不是同一安全域的服务端设备返回的资源列表，或者不受客户端设备控制的服务端设备返回的资源列表等。如此，造成信息冗余，降低了客户端设备的数据处理效率。
基于此，本申请实施例提供一种信息处理方法及设备、计算机存储介质，图2为本申请实施例适用的一种网络结构200示意图。参考图2，所述网络结构200包括客户端设备210以及服务端设备220。其中，客户端设备210是指访问资源的设备，服务端设备是指提供资源的设备。应理解，客户端设备具有查询和控制其他设备的功能，服务端设备能够被其他设备查询和控制；也就是说，本申请实施提供的网络结构200中，任何具有查询和控制其他设备的功能的设备都可以作为客户端设备，同时，任何能够被查询和被控制的设备，都可以作为服务端设备。需要说明的是，实现某项最基本功能的设备(例如灯泡)可以只做服务端，提供给客户端进行查询和控制，本身无控制或者查询其他设备的需求。
本申请实施例所涉及的客户端设备210和服务端设备220包括但不限于智能手机，平板，笔记本电脑，可穿戴设备，车载设备，智能家居设备，智能安防设备等。智能家居设备包括但不限于智能空调、冰箱、智能门锁、智能灯具等，智能安防设备包括但不限于烟气燃气报警设备、红外探头、红外栅栏等。
图2示例性地示出了一个客户端设备210和两个服务端设备220，可选地，该网络结构可以包括多个客户端设备，以及其它数量的服务端设备，本申请实施例对此不做限定。
应理解，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和 /或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
图3是本申请实施例提供的一种信息处理方法流程示意图一，该信息处理方法的执行主体为第一设备，第一设备可以是图2所示的客户端设备210。该信息处理方法包括以下内容。
步骤310、获取第一安全域的第一身份信息。
这里，安全域，也可以称为安全域网络，安全域网络是一种具体的物联网的网络。安全域网络具有独立的安全协议(或安全机制)，在同一安全域网络中的物联网设备可以互联、互通、互相发现以及相互传输指令。可以理解的是，不在同一安全域网络的两个设备，由于受到安全域网络中的安全协议限制，因此无法相互访问对方安全域网络内的物联网设备。
其中，各个设备所属安全域的相关信息可以由用户进行配置，也可以由其他设备(例如物联网服务器)进行配置，本申请实施例这里不做限定。
在本申请提供的实施例中，设备所属安全域的相关信息至少包括安全域的身份信息；这里，安全域的身份信息能够标识该安全域。
在一种可能的实现方式中，安全域的身份信息可以包括安全域的标识信息和/或安全域的名称信息。应理解，本申请实施例中，第一身份信息可以包括第一安全域的标识信息和/或第一安全域的名称信息。
在本申请提供的实施例中，第一安全域可以是第一设备所属的安全域；第一安全域也可以是除第一设备所属安全域外，任意一个安全域，本申请实施例这里对第一安全域不做限定。
步骤320、基于第一身份信息，得到第一发现请求信息；第一发现请求信息用于请求与第一身份信息匹配的目标设备的目标资源；
在本申请提供的实施例中，第一设备可以基于第一身份信息构建第一发现请求信息；也就是说，在第一发现请求信息中携带了第一身份信息，用于请求网络中与第一身份信息匹配的目标设备中存储的目标资源。这样，第一设备通过在第一发现请求信息加入基于安全域的过滤条件，使得只有接收到该第一发现请求信息，且安全域的身份信息与第一身份信息匹配的设备才会响应第一发现请求信息，从而避免了网络中所有接收到发现请求信息的设备都返回资源列表，导致信息冗余的问题。
需要说明的是，本申请实施例中通过第一发现请求来发现与第一身份信息匹配目标设备的目标资源，可以包含两层含义：第一、第一设备首次接入局域网或者启动设备发现机制时，通过第一发现请求来发现局域网中与第一身份信息匹配的目标设备，以及每个目标设备中存储的目标资源；第二，第一设备在已知局域网中设备位置的情况下或者启动资源发现机制时，通过第一发现请求来发现局域网中已知设备中存储的目标资源。即，本申请实施例中的第一发现请求，既可以用于实现网络中的设备发现，也可以实现网络中的资源发现。
步骤330、发送第一发现请求信息。
在一种可能的实现方式中，第一设备可以向至少一个第二设备发送第一发现请求信息。这里，第二设备是可以是图2所示的服务端设备220，以及服务端设备230。
在一种可能的实现方式中，第一设备可以通过广播或者多播的方式向至少一个第二设备发送第一发现请求信息。这里，第一设备通过广播或者多播方式向至少一个第二设备发送第一发现请求信息，可以是在第一设备首次接入局域网或者启动设备发现机制时执行。
在一种可能的实现方式中，第一设备也可以通过单播的方式向至少一个第二设备发送第一发现请求信息。这里，第一设备通过单播方式发送第一发现请求信息，可以是在已知第二设备的地址的情况下执行的。
由此可见，本申请实施例提供的信息处理方法中，第一设备获取第一安全域的第一身份信息；进而，基于第一身份信息，得到第一发现请求信息；第一发现请求信息用于请求与所述第一身份信息匹配目标设备的目标资源；发送所述第一发现请求信息。也就是说，第一发现请求信息仅用于请求与第一安全域匹配的目标设备中存储的目标资源，这样，第一设备接收到的信息都是与第一安全域(即第一身份信息)匹配的目标设备的目标资源；如此，降低信息的冗余度，提高第一设备的处理效率。
基于前述实施例，步骤310中、获取第一安全域的第一身份信息的具体实现方式有多种，下面详细介绍其中的两种实现方式：方式一和方式二。如下：
方式一
在一种可能的实现方式中，获取第一安全域的第一身份信息的实现过程为：
将第一设备所属安全域的身份信息，确定为第一安全域的第一身份信息。
可以理解的是，第一安全域可以是第一设备所属安全域，第一身份信息即为第一设备所属安全域的身份信息。
在本申请提供的实施例中，第一设备可以查看本地配置的安全域资源，即/oic/sec/sdi资源中存储的安全域信息，并在安全域信息中查找到第一身份信息。这里，第一身份信息可以是第一设备所属安全域的安全域标识信息和/或安全域名称信息。
进一步，第一设备将第一设备所属安全域的身份信息确定为第一安全域的第一身份信息，并构建第一发现请求信息。这样，直接将自身所属安全域的身份信息作为第一身份信息来构建第一发现请求信息，可以准确发现与第一设备处于同一安全域的设备，即能够与第一设备互联互通的设备，以提高发现效率。
方式二
在一种可能的实现方式中，获取第一安全域的第一身份信息的实现过程为：
获取设置指令；所述设置指令包括特定安全域的身份信息；
响应所述设置指令，并将所述特定安全域的身份信息确定所述第一安全域的第一身份信息。
在本申请提供的实施例中，第一设备可以通过任意类型的输入模组来获取用户输入的设置指令，并响应接收到的设置指令，并将设置指令中携带的特定安全域的身份信息，设置为第一安全域的第一身份信息，即第一身份信息可以是用户输入的任意一个安全域的身份信息。
需要说明的是，用户输入的特定安全域的身份信息可以是任意安全域的安全域标识信息，和/或安全域名称信息。
进一步，第一设备在确定了第一身份信息之后，基于该第一身份信息构建第一发现请求信息。这样，第一设备可以基于用户输入的任意安全域的身份信息构建第一发现请求信息，以发现与输入的安全域匹配的目标设备的目标信息，即用户期望得到的信息；提高了设备发现，以及资源发现的灵活性。
在一种可能的实现方式中，作为一个实施例，参考图4所示的一种信息处理方法流程示意图二，在步骤320基于第一身份信息，得到第一发现请求信息之前，还包括以下步骤：
步骤311、获取第一设备所属安全域的隐私标识；
步骤312、若隐私标识指示第一设备的资源为私有资源，则生成并呈现确认信息；确认信息用于确认是否基于安全域的身份信息进行发现；
步骤313、接收针对确认信息的反馈信息；
相应的，步骤320基于所述第一身份信息，得到第一发现请求信息，可以通过步骤320’实现：
步骤320’、若反馈信息指示基于安全域的身份信息进行发现，则基于第一身份信息，构建第一发现请求信息。
这里，每个设备的安全域信息还可以包括隐私标识priv。该隐私标识可以用于指示设备中安全域信息的可见性，也可以理解为是安全域资源的可见性。
当一设备的隐私标识priv设置为“false”时，则认为该设备的安全域资源可见，这样在该设备的/oic/res资源中公开该设备的安全域信息(具体可以是安全域的身份信息)。当一设备的隐私标识priv设置为“true”时，则认为该设备的安全域资源为不可见资源，这样在该设备的/oic/res资源中不公开该设备的安全域信息(具体可以是安全域的身份信息)。
在本身申请提供的实施例中，在第一设备进行设备发现或者资源发现之前，第一设备可以先检查自己的隐私标识是否指示第一设备的安全域资源为不可见资源。当第一设备的安全域资源为不可见资源时，进行设备发现和资源发现可能会有资源泄露的风险。因此，当隐私标识指示第一设备的资源为不可见资源时，还需要向用户进行确认是否执行基于安全域的发现。
在一种可能的实现方式中，第一设备可以通过显示装置的交互界面向用户呈现确认信息，以询问是否基于安全域进行设备发现或资源发现。
这里，第一设备在输出确认信息之后，等待用户输入的反馈信息。若接收到的反馈信息用于指示基于安全域的身份信息进行发现，则基于第一身份信息，得到第一发现请求信息。如此，提高了数据传输的安全性。
需要说明的是，步骤311至步骤313可以在步骤310之前执行，也可以在步骤310之后执行，也可以与步骤310同时执行。本申请实施例这里不做限定。
在一种可能的实现方式中，步骤320基于第一身份信息，得到第一发现请求信息，包括：
获取目标资源的资源统一标识符(Uniform Resource Identifier，URI)，以及请求地址；
基于目标资源的资源统一标识符，请求地址，以及第一身份信息，构建所述第一发现请求信息。
这里，第一设备可以在确定了第一安全域的第一身份信息之后，根据用户的设备发现或资源发现的需求，确定请求地址，以及请求的目标资源对应的URI。进一步，根据目标资源的URI，请求地址，以及第一身份信息构建第一发现请求信息。
在一种可能的实现方式中，请求地址可以是多播地址。
在另一种可能的实现方式中，请求地址也可以是单播地址。
这里，请求地址可以根据用户的设备发现或资源发现需求进行确定。若用户需要请求局域网内的所有设备，则请求地址可以为多播地址。当用户已知部分设备的地址时，需要对更该部分设备的资源进行请求，则可以直接将该部分设备的地址作为请求地址。
上文结合图3和图4，从第一设备的角度详细描述了本申请实施例提供的信息处理方法，下文结合图5和图6，从第二设备的角度详细描述本申请实施例提供的用于信息处理的方法。应理解，第一设备侧的描述与第二设备侧的描述相互对应，相似的描述可以参见上文，为避免重复，此处不再赘述。
图5是本申请实施例提供的一种信息处理方法流程示意图三，该信息处理方法的执 行主体为第二设备，第二设备可以是图2所示的服务端设备220或者服务端设备230。该信息处理方法包括以下内容。
步骤510、接收第一发现请求信息；第一发现请求信息包括第一安全域的第一身份信息；第一发现请求信息用于发现与第一身份信息匹配的目标设备的目标资源；
在一种可能的实现方式中，第二设备接收第一设备发送的第一发现请求信息。
在另一种可能的实现方式中，第二设备接收其他设备转发的第一设备发送的第一发现请求信息。
步骤520、基于第一身份信息，确定是否发送目标资源。
这里，第一发现请求信息用于请求与第一身份信息匹配的目标设备中存储的目标资源。本申请实施例中，第二设备在接收到第一发现请求信息之后，可以从第一发现请求信息中解析出第一安全域的第一身份信息，并基于该第一身份信息，来确定自己是否与第一身份信息匹配，若匹配则响应该第一发现请求信息，确定发送自己的目标资源，若不匹配，则不响应该第一发现请求信息，确定不发送自己的目标资源。
也就是说，第二设备与第一发现请求信息中携带的第一身份信息匹配，才能够响应第一发现请求信息，返回第二设备中的目标资源。这样，第一设备接收到的信息都是与第一安全域(即第一身份信息)匹配的目标设备的目标资源；如此，降低信息的冗余度，提高第一设备的处理效率。
在一种可能的实现方式中，参考图6所示的一种信息处理方法流程示意图四，基于第一身份信息，确定是否发送第二设备的目标资源的实现过程为：
步骤5201、获取第二设备的资源描述信息。
在本申请提供的实施例中，第二设备的资源描述信息可以是第二设备的/oic/res资源中的属性信息。
步骤5202、判断第二设备的资源描述信息中是否包括第二身份信息；第二身份信息为第二设备所属安全域的身份信息；
可以理解的是，判断第二身份信息与第一身份信息是否匹配，即确定第二设备的安全域是否与第一发现请求信息中携带的第一安全域为同一安全域。
这里，第二身份信息可以包括第二设备所属安全域的标识信息和/或第二设备所属安全域的名称信息。在本申请提供的实施例中，第二设备可以从/oic/res资源的属性信息中查找第二设备所属安全域的标识信息和/或第二设备所属安全域的名称信息。
需要说明的是，当第一身份信息为第一安全域的标识信息时，第二设备则需要获取自身所属安全域的标识信息，来与第一身份信息进行匹配。当第一身份信息为第一安全域的名称信息时，第二设备则需要获取第二设备所属安全域的名称信息，来与第一身份信息进行匹配。当第一身份信息为第一安全域的标识信息和名称信息时，则第二设备则需要获取第二设备所属安全域的标识信息和名称信息，来与第一身份信息进行匹配，在该情况下，可以在标识信息与名称信息都匹配时，才确定第二身份信息与第一身份信息匹配；也可以在标识信息与名称信息中的任意一个匹配时，就确定第二身份信息与第一身份信息匹配，本申请实施例例这里不做限定。
步骤5203、若第二设备的资源描述信息中包括第二身份信息，且第二身份信息与第一身份信息匹配，则确定发送目标资源。
这里，第二身份信息与第一身份信息匹配，则可以认为第二设备的安全域与第一设备的安全域为同一安全域，则第二设备响应第一发现请求信息，即第二设备获取第一发现请求信息中所要请求的目标资源，并发送该目标资源。
步骤5204、若第二设备的资源描述信息中包括第二身份信息，且第二身份信息 与第一身份信息不匹配，则确定不发送目标资源。
这里，第二身份信息与第一身份信息不匹配，则可以认为第二设备的安全域与第一设备的安全域不是同一安全域，则第二设备不响应第一发现请求信息，即第二设备不发送目标资源。
步骤5205、若第二设备的资源描述信息中不包括第二身份信息，则确定不发送目标资源。
这里，第二设备的资源描述信息中不包括第二身份信息，可能是两种情况导致的：情况一，第二设备未实现安全域资源，或者第二设备未配置安全域信息；情况二，第二设备的安全域信息中隐私标识设置为“true”。在以上两种情况下，第二设备和第一设备无法实现基于安全域的设备发现或资源发现，因此，在第二设备的资源描述信息中包括第二身份信息时，第二设备可以确定不响应第一发现请求信息，即不发送目标资源。
在一种可能的实现方式中，步骤5203确定发送目标资源之后，还包括以下步骤：
确定第二设备为目标设备，并获取第二设备中目标资源；
向第一设备发送目标资源。
这里，第二设备判断第二身份信息与第一身份信息匹配后，则可确定自己是目标设备。第二设备在确定发送目标资源之后，执行对第一发现请求信息的响应，即获取第一发现请求中所要求的目标资源，并将目标资源发送给第一设备。
可选地，第二设备通过单播方式向第一设备发送目标资源。
综上所述，本申请提供的信息处理方法中，第二设备与第一发现请求信息中携带的第一身份信息匹配，才能够响应第一发现请求信息，返回第二设备中的目标资源。这样，第一设备接收到的信息都是与第一安全域(即第一身份信息)匹配的目标设备的目标资源；如此，降低信息的冗余度，提高第一设备的处理效率。
下面结合实际应用场景对本申请实施例提供的数据处理方法进行详细描述。
参考图7所示的应用场景示意图，局域网700中有三个服务端设备，分别为设备1、设备2和设备3，以及一个客户端设备。
设备1、设备2和设备3构成名称为“所有节点”的多播组，其中，该“所有节点”多播组多播地址包括：多播服务地址：ff02::158，端口信息5683。
在图7中，设备1与客户端设备在同一安全域中，且设备1的安全域信息配置为可发现(即设备1的安全域信息中隐私标识sdi.priv＝false)。设备1的/oic/res资源示例如下(忽略通用资源的列表)：
Figure PCTCN2020092685-appb-000001
设备2与客户端设备不在同一安全域中，且设备2的安全域信息配置为可发现(即设备2的安全域信息中隐私标识sdi.priv＝false)。设备2的/oic/res资源示例如下(忽略通用资源的列表)：
Figure PCTCN2020092685-appb-000002
设备3的安全域信息的配置为不可见(即设备3安全域信息中的隐私标识sdi.priv＝true)。或者，设备3没有配置安全域资源/oic/sec/sdi资源。
基于图7所示的应用场景，在一种示例中，在客户端设备首次接入局域网700中或者客户端设备启动设备发现机制时，参考图8所示的设备发现或资源发现流程示意图一，客户端设备(即上文所述的第一设备)进行局域网设备发现或资源发现的操作流程包括以下步骤：
步骤1、客户端设备(即第一设备)查看自身的安全域信息，获取客户端设备所属安全域的身份信息。
可选地，客户端所属安全域的身份信息为安全域标识信息(sduuid)；例如，客户端设备的sduuid为12345678-1234-1234-1234-123412341234。
可选地，客户端所属安全域的身份信息还可以为安全域名称信息(sdname)。例如，客户端设备的sdname为Alice’s Home。
可选地，还可以将sduuid和sdname同时作为客户端所属安全域的身份信息。
步骤2、客户端设备(即第一设备)基于步骤1获取的身份信息构建第一发现请求信息，第一发现请求可以通过多播方式发送。
在本申请提供的实施例中，客户端设备需要进行设备发现的时候可以加入图7所示的“所有节点”多播组；客户端设备通过多播方式给“所有节点”多播组中的所有设备发送第一发现请求，请求的资源的URI为"/oic/res"。
在本申请提供的实施例中，第一发现请求信息可以基于约束应用协议(The Constrained Application Protocol，CoAP)来构建。
这里，以客户端获取sduuid作为其所属安全域的身份信息为例，说明第一发现请求信息的构建过程，具体地，客户端设备可以根据多播地址([ff02::158]:5683)，目标资源oic/res，以及客户端设备所属安全域的sduuid值构建第一发现请求信息。第一发现请求信息可以为：
RETRIEVE coap://[ff02::158]:5683/oic/res？sduuid＝"12345678-1234-1234
-1234-123412341234"。
步骤3、设备1、设备2和设备3收到第一发现请求信息，解析出第一发现请求信 息所指示的目标资源(即/oic/res资源)，以及过滤条件(即客户端设备所属安全域的身份信息)，进而设备1、设备2和设备3判断自身/oic/res资源的属性中是否有sduuid和/或sdname属性(即第二身份信息)。
这里，当客户端设备发送的第一发现请求信息中携带的第一身份信息为sduuid时，设备1、设备2和设备3则判断自身/oic/res资源是否有sduuid属性。当客户端设备发送的第一发现请求信息中携带的第一身份信息为sdname时，设备1、设备2和设备3则判断自身/oic/res资源是否有sduuid属性。另外，当客户端设备发送的第一发现请求信息中携带的第一身份信息为sduuid和sdname时，则设备1、设备2和设备3判断自身/oic/res资源是否有sduuid和sdname属性。
步骤4a、设备1接收到第一发现请求信息后，查看自身/oic/res资源的属性信息中包括sduuid和/或sdname属性。
并且设备1的sduuid值为“12345678-1234-1234-1234-123412341234”，sdname的值为“Alice’s Home”，与第一发现请求中的sduuid和/或sdname值匹配。
进一步，执行步骤5a。
步骤5a、设备1通过单播方式向客户端设备返回/oic/res资源。
其中，设备1返回/oic/res资源中的资源列表“links”，具体包括：
Figure PCTCN2020092685-appb-000003
步骤4b、设备2接收到第一发现请求信息后，查看自身/oic/res资源的属性信息中包括sduuid和/或sdname属性。
并且设备2的sduuid值为“dc70373c-1e8d-4fb3-962e-017eaa863989”，sdname值为“Bob’s Home”，与第一发现请求信息中的sduuid和/或sdname值不匹配。
进一步，执行步骤5b。
步骤5b、设备2确定不响应第一发现请求信息，即不发送/oic/res资源。
步骤4c、设备3接收到第一发现请求信息后，查看自身/oic/res资源的属性信息中没有sduuid和sdname属性。
进一步，执行步骤5c。
步骤5c、设备3确定不响应第一发现请求信息，即不发送/oic/res资源。
需要说明的是，步骤4a、4b和4c可以同时执行。
进一步，客户端设备收到局域网700中与自己处于同一安全域的所有可发现设备返回的资源列表，可以通过交互界面展示给用户并进行后续控制。这样，客户端设备接收到的信息都是与客户端所属安全域匹配的设备的设备资源；如此，降低信息的冗余度，提高客户端设备的处理效率。
基于图7所示的应用场景，在另一种示例中，参考图9所示的设备发现或资源发现流程示意图二，客户端设备(即上文所述的第一设备)进行局域网设备发现或资源发现的操作流程包括以下步骤：
步骤1、客户端设备在交互界面接收用户输入的设置指令，设置指令用于设置第一安全域的第一身份信息。
可以理解的是，用户可以设置任意安全域的身份信息，作为设备发现的过滤条件。即用户可以通过输入任意安全域的身份信息，以构成第一发现请求信息，通过第一发现请求信息来发现与该安全域为同一安全域的设备。
可选地，客户端设备可以接收用户在交互界面输入的安全域标识信息，来构建第一发现请求信息，例如，用户在客户端设备的交互界面输入安全域标识信息duuid为“12345678-1234-1234-1234-123412341234”。
可选地，客户端设备可以接收用户在交互界面输入的安全域名称信息，来构建第一发现请求信息，例如，用户在客户端设备的交互界面输入安全域名称信息为“Alice’s Home”。
步骤2、客户端设备基于步骤1获取的第一身份信息构建第一发现请求消息；并在局域网700中通过多播方式发送该第一发现请求信息。
这里，以用户设置sdname为“Alice’s Home”为例，说明第一发现请求信息的构建过程，具体地，客户端设备可以根据多播地址([ff02::158]:5683)，目标资源oic/res，以及客户端设备所属安全域的名称信息，sdname值构建第一发现请求信息。第一发现请求信息可以为：
RETRIEVE coap://[ff02::158]:5683/oic/res？sdname＝"Alice’s Home"。
步骤3、设备1、设备2和设备3收到第一发现请求信息，解析出目标资源(即/oic/res资源)和过滤条件(即用户设置的第一安全域的第一身份信息)，进而设备1、设备2和设备3判断自身/oic/res资源的属性中是否有sduuid和/或sdname属性(即第二身份信息)。
步骤4a、设备1接收到第一发现请求信息后，查看自身/oic/res资源的属性信息中包括sduuid和/或sdname属性。
并且设备1的sduuid值为“12345678-1234-1234-1234-123412341234”，sdname的值为“Alice’s Home”，与第一发现请求中的sduuid和/或sdname值匹配。
进一步，执行步骤5a。
步骤5a、设备1通过单播的方式向客户端设备返回/oic/res资源。
其中，设备1返回oic/res资源中的资源列表“links”，具体包括：
Figure PCTCN2020092685-appb-000004
步骤4b、设备2接收到第一发现请求信息后，查看自身/oic/res资源的属性信息中包括sduuid和/或sdname属性。
并且设备2的sduuid值为“dc70373c-1e8d-4fb3-962e-017eaa863989”，sdname值为“Bob’s Home”，与第一发现请求信息中的sduuid和/或sdname值不匹配。
进一步，执行步骤5b。
步骤5b、设备2确定不响应第一发现请求信息，即不发送/oic/res资源。
步骤4c、设备3接收到第一发现请求信息后，查看自身/oic/res资源的属性信息中没有sduuid和sdname属性。
进一步，执行步骤5c。
步骤5c、设备3确定不响应第一发现请求信息，即不发送/oic/res资源。
需要说明的是，步骤4a、4b和4c可以同时执行。
进一步，客户端设备收到局域网700中与自己处于同一安全域的所有可发现设备返回的资源列表，可以展示给用户并进行后续控制。如此，降低信息的冗余度，提高客户端设备的处理效率。
基于图7所示的应用场景，在又一种示例中，参考图10所示的设备发现或资源发现流程示意图三，客户端设备(即上文所述的第一设备)进行局域网设备发现或资源发现的操作流程包括以下步骤：
步骤1、客户端设备(即第一设备)查看自身的安全域信息，获取客户端设备所属安全域的身份信息。
可选地，客户端所属安全域的身份信息为安全域标识信息(sduuid)；例如，客户端设备的sduuid为12345678-1234-1234-1234-123412341234。
可选地，客户端所属安全域的身份信息还可以为安全域名称信息(sdname)。例如，客户端设备的sdname为Alice’s Home。
可选地，还可以将sduuid和sdname同时作为客户端所属安全域的身份信息。
步骤2、客户端设备查看自身的安全域信息中的隐私标识，即priv属性值。
步骤3、若客户端设备的sdi.priv＝true，则生成确认信息，并通过客户端设备的交互界面向用户呈现确认信息，确认信息用于向用户询问是否基于安全域的身份信息进行设备发现和/或资源发现。
步骤4、客户端设备接收用户输入的反馈信息，反馈信息指示基于安全域的身份信息进行发现。
步骤5、客户端设备基于步骤1获取的身份信息构建第一发现请求信息，第一发现请求可以通过多播方式发送。
这里，以客户端获取sduuid作为其所属安全域的身份信息为例，第一发现请求信息可以为：
RETRIEVE coap://[ff02::158]:5683/oic/res？sduuid＝"12345678-1234-1234
-1234-123412341234"。
步骤6、设备1、设备2和设备3收到第一发现请求信息，解析出第一发现请求信息所指示的目标资源(即/oic/res资源)，以及过滤条件(即客户端设备所属安全域的身份信息)，进而设备1、设备2和设备3判断自身/oic/res资源的属性中是否有sduuid和/或sdname属性(即第二身份信息)。
这里，当客户端设备发送的第一发现请求信息中携带的第一身份信息为sduuid时，设备1、设备2和设备3则判断自身/oic/res资源是否有sduuid属性。当客户端设备发送的第一发现请求信息中携带的第一身份信息为sdname时，设备1、设备2和设备3则判断自身/oic/res资源是否有sduuid属性。另外，当客户端设备发送的第一发现请求信息中携带的第一身份信息为sduuid和sdname时，则设备1、设备2和设备3判断自身/oic/res资源是否有sduuid和sdname属性。
步骤7a、设备1接收到第一发现请求信息后，查看自身/oic/res资源的属性信息中包括sduuid和/或sdname属性。
并且设备1的sduuid值为“12345678-1234-1234-1234-123412341234”，sdname的值为“Alice’s Home”，与第一发现请求中的sduuid和/或sdname值匹配。
进一步，执行步骤8a。
步骤8a、设备1通过单播的方式向客户端设备返回/oic/res资源。
其中，设备1返回/oic/res资源中的资源列表“links”，具体包括：
Figure PCTCN2020092685-appb-000005
Figure PCTCN2020092685-appb-000006
步骤7b、设备2接收到第一发现请求信息后，查看自身/oic/res资源的属性信息中包括sduuid和/或sdname属性。
并且设备2的sduuid值为“dc70373c-1e8d-4fb3-962e-017eaa863989”，sdname值为“Bob’s Home”，与第一发现请求信息中的sduuid和/或sdname值不匹配。
进一步，执行步骤8b。
步骤8b、设备2确定不响应第一发现请求信息，即不发送/oic/res资源。
步骤7c、设备3接收到第一发现请求信息后，查看自身/oic/res资源的属性信息中没有sduuid和sdname属性。
进一步，执行步骤8c。
步骤8c、设备3确定不响应第一发现请求信息，即不发送/oic/res资源。
需要说明的是，步骤7a、7b和7c可以同时执行。
进一步，客户端设备收到局域网700中与自己处于同一安全域的所有可发现设备返回的资源列表，可以展示给用户并进行后续控制。如此，降低信息的冗余度，提高客户端设备的处理效率。
基于前述实施例，本申请实施例提供一种信息处理装置，该信息处理装置可以应用于上文所述的第一设备中，如图11所示，信息处理装置包括：
第一获取单元1101，配置为获取第一安全域的第一身份信息；
第一处理单元1102，配置为基于所述第一身份信息，得到第一发现请求信息；所述第一发现请求信息用于请求与所述第一身份信息匹配的目标设备的目标资源；
第一收发单元1103，配置为发送所述第一发现请求信息。
在本申请提供的实施例中，第一获取单元1101，还配置为将所述第一设备所属安全域的身份信息，确定为所述第一安全域的第一身份信息。
在本申请提供的实施例中，第一获取单元1101，获取设置指令；所述设置指令包括特定安全域的身份信息；
第一处理单元1102，配置为响应设置指令，并将所述特定安全域的身份信息确定所述第一安全域的第一身份信息。
在本申请提供的实施例中，第一获取单元1101，配置为获取所述第一设备所属安全域的隐私标识；
第一处理单元1102，配置为若所述隐私标识指示所述第一设备的资源为私有资源，则生成并呈现确认信息；所述确认信息用于确认是否基于安全域的身份信息进行发现；
第一收发单元1103，配置为接收针对所述确认信息的反馈信息；
第一处理单元1102，配置为若所述反馈信息指示基于安全域的身份信息进行发现，则基于所述第一身份信息，构建所述第一发现请求信息。
在本申请提供的实施例中，第一收发单元1103，配置为向至少一个第二设备发送所述第一发现请求信息。
在本申请提供的实施例中，第一身份信息包括所述第一安全域的标识信息和/或所述 第一安全域的名称信息。
在本申请提供的实施例中，第一获取单元1101，配置为获取目标资源的资源统一标识符，以及请求地址；
第一处理单元1102，配置为基于目标资源的资源统一标识符，所述请求地址，以及所述第一身份信息，构建所述第一发现请求信息。
在本申请提供的实施例中，所述请求地址为多播地址。
基于前述实施例，本申请实施例提供一种信息处理装置，该信息处理装置可以应用于上文所述的第二设备中，如图12所示，信息处理装置包括：
第二收发单元1201，配置为接收第一发现请求信息；所述第一发现请求信息包括第一安全域的第一身份信息；所述第一发现请求信息用于发现与所述第一身份信息匹配的目标设备的目标资源；
第二处理单元1202，配置为基于所述第一身份信息，确定是否发送所述目标资源。
在一些实施例中，第二处理单元1202，还配置为判断所述第二设备的资源描述信息中是否包括第二身份信息；所述第二身份信息为所述第二设备所属安全域的身份信息；若所述资源描述信息中包括所述第二身份信息，且所述第二身份信息与所述第一身份信息匹配，则确定发送所述目标资源。
在一些实施例中，第二处理单元1202，还配置为若所述资源描述信息中包括所述第二身份信息，且所述第二身份信息与所述第一身份信息不匹配，则确定不发送所述目标资源。
在一些实施例中，第二处理单元1202，还配置为若所述第二设备的资源描述信息中不包括所述第二身份信息，则确定不发送所述目标资源。
在一些实施例中，所述信息处理装置还包括第二获取单元；
第二处理单元1202，配置为确定所述第二设备为所述目标设备；
第二获取单元，配置为获取所述第二设备中的所述目标资源；
第二收发单元1201，配置为向第一设备发送所述目标资源。
基于前述实施例，申请实施例还提供一种设备，参考图13所示的一种第一设备的硬件结构组成示意图。图13所示的第一设备包括：第一收发器1301、第一处理器1302和存储有计算机程序的第一存储器1303；
所述第一收发器1301、所述第一处理器1302和所述第一存储器1303之间通过第一通信总线1304进行通信；
所述第一处理器，配置为通过所述第一收发器1301实现与另一设备的通信；其中，
所述第一处理器1302，运行所述第一存储器1303中存储的所述计算机程序时，执行以下步骤：获取第一安全域的第一身份信息；基于所述第一身份信息，得到第一发现请求信息；所述第一发现请求信息用于请求与所述第一身份信息匹配的目标设备的目标资源；第一收发器1301，运行所述第一存储器1303中存储的所述计算机程序时，执行以下步骤：发送所述第一发现请求信息。
在一些实施例中，第一处理器1302运行所述第一存储器1303中存储的所述计算机程序时，执行以下步骤：将所述第一设备所属安全域的身份信息，确定为所述第一安全域的第一身份信息。
在一些实施例中，第一处理器1302运行所述第一存储器1303中存储的所述计算机程序时，执行以下步骤：获取设置指令；所述设置指令包括特定安全域的身份信息；响应所述设置指令，并将所述特定安全域的身份信息确定所述第一安全域的第一身份信息。
在一些实施例中，第一处理器1302运行所述第一存储器1303中存储的所述计算机程序时，执行以下步骤：获取所述第一设备所属安全域的隐私标识；若所述隐私标识指示所述第一设备的资源为私有资源，则生成并呈现确认信息；所述确认信息用于确认是否基于安全域的身份信息进行发现；接收针对所述确认信息的反馈信息；若所述反馈信息指示基于安全域的身份信息进行发现，则基于所述第一身份信息，构建所述第一发现请求信息。
在一些实施例中，第一收发器1301运行所述第一存储器1303中存储的所述计算机程序时，执行以下步骤：向至少一个第二设备发送所述第一发现请求信息。
在一些实施例中，第一身份信息包括所述第一安全域的标识信息和/或所述第一安全域的名称信息。
在一些实施例中，第一收发器1301运行所述第一存储器1303中存储的所述计算机程序时，执行以下步骤：获取目标资源的资源统一标识符URI，以及请求地址；基于目标资源的资源统一标识符，所述请求地址，以及所述第一身份信息，构建所述第一发现请求信息。
在一些实施例中，所述请求地址为多播地址。
基于前述实施例，申请实施例还提供一种设备，参考图13所示的一种第二设备的硬件结构组成示意图。图14所示的第二设备包括：第二收发器1401、第二处理器1402和存储有计算机程序的第二存储器1403；
所述第二收发器1401、所述第二处理器1402和所述第二存储器1403之间通过第二通信总线1404进行通信；
所述第二处理器1402，配置为通过所述第二收发器1401实现与另一设备的通信；其中，
第二收发器1401，运行所述第二存储器1403中存储的所述计算机程序时，执行以下步骤：接收第一发现请求信息；所述第一发现请求信息包括第一安全域的第一身份信息；所述第一发现请求信息用于请求与所述第一身份信息匹配的目标设备的目标资源；
所述第二处理器1402，运行所述第二存储器1403中存储的所述计算机程序时，执行以下步骤：基于所述第一身份信息，确定是否发送所述目标资源。
在一些实施例中，第二处理器1402，运行所述第二存储器1403中存储的所述计算机程序时，还可以执行以下步骤：获取所述第二设备的资源描述信息；判断所述资源描述信息中是否包括第二身份信息；所述第二身份信息为所述第二设备所属安全域的身份信息；若所述资源描述信息中包括所述第二身份信息，且所述第二身份信息与所述第一身份信息匹配，则确定发送所述目标资源。
在一些实施例中，第二处理器1402，运行所述第二存储器1403中存储的所述计算机程序时，还可以执行以下步骤：若所述资源描述信息中包括所述第二身份信息，且所述第二身份信息与所述第一身份信息不匹配，则确定不发送所述目标资源。
在一些实施例中，第二处理器1402，运行所述第二存储器1403中存储的所述计算机程序时，还可以执行以下步骤：若所述资源描述信息中不包括所述第二身份信息，则确定不发送所述目标资源。
在一些实施例中，第二处理器1402，运行所述第二存储器1403中存储的所述计算机程序时，还可以执行以下步骤：确定所述第二设备为所述目标设备，并获取所述第二设备中所述目标资源；
第二收发器1401，运行所述第二存储器1403中存储的所述计算机程序时，执行以下步骤：向第一设备发送所述目标资源。
应理解，本实施例中的第一存储器和第二存储器可以是易失性存储器或非易失性存储器，也可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read Only Memory，ROM)、可编程只读存储器(Programmable Read-Only Memory，PROM)、可擦除可编程只读存储器(Erasable Programmable Read-Only Memory，EPROM)、电可擦除可编程只读存储器(Electrically Erasable Programmable Read-Only Memory，EEPROM)、磁性随机存取存储器(Ferromagnetic Random Access Memory，FRAM)、快闪存储器(Flash Memory)、磁表面存储器、光盘、或只读光盘(Compact Disc Read-Only Memory，CD-ROM)；磁表面存储器可以是磁盘存储器或磁带存储器。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static Random Access Memory，SRAM)、同步静态随机存取存储器(Synchronous Static Random Access Memory，SSRAM)、动态随机存取存储器(Dynamic Random Access Memory，DRAM)、同步动态随机存取存储器(Synchronous Dynamic Random Access Memory，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate Synchronous Dynamic Random Access Memory，DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced Synchronous Dynamic Random Access Memory，ESDRAM)、同步连接动态随机存取存储器(SyncLink Dynamic Random Access Memory，SLDRAM)、直接内存总线随机存取存储器(Direct Rambus Random Access Memory，DRRAM)。本申请实施例描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提供了一种计算机存储介质，具体为计算机可读存储介质。其上存储有计算机指令，作为第一种实施方式，在计算机存储介质位于终端时，该计算机指令被处理器执行时实现本申请实施例上述信息处理方法中的任意步骤。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (18)

  1. 一种信息处理方法，其中，应用于第一设备，所述方法包括：
    获取第一安全域的第一身份信息；
    基于所述第一身份信息，得到第一发现请求信息；所述第一发现请求信息用于请求与所述第一身份信息匹配的目标设备的目标资源；
    发送所述第一发现请求信息。
  2. 根据权利要求1所述的方法，其中，所述获取第一安全域的第一身份信息，包括：
    将所述第一设备所属安全域的身份信息，确定为所述第一安全域的第一身份信息。
  3. 根据权利要求1所述的方法，其中，所述获取第一安全域的第一身份信息，包括：
    获取设置指令；所述设置指令包括特定安全域的身份信息；
    响应所述设置指令，并将所述特定安全域的身份信息确定所述第一安全域的第一身份信息。
  4. 根据权利要求1-3任一项所述的方法，其中，所述基于所述第一身份信息，得到第一发现请求信息之前，还包括：
    获取所述第一设备所属安全域的隐私标识；
    若所述隐私标识指示所述第一设备的资源为私有资源，则生成并呈现确认信息；所述确认信息用于确认是否基于安全域的身份信息进行发现；
    接收针对所述确认信息的反馈信息；
    所述基于所述第一身份信息，得到第一发现请求信息，包括：
    若所述反馈信息指示基于安全域的身份信息进行发现，则基于所述第一身份信息，构建所述第一发现请求信息。
  5. 根据权利要求1-4任一项所述的方法，其中，所述发送所述第一发现请求信息，包括：
    向至少一个第二设备发送所述第一发现请求信息。
  6. 根据权利要求1-5任一项所述的方法，其中，第一身份信息包括所述第一安全域的标识信息和/或所述第一安全域的名称信息。
  7. 根据权利要求1-6任一项所述的方法，其中，所述基于所述第一身份信息，得到第一发现请求信息，包括：
    获取目标资源的资源统一标识符URI，以及请求地址；
    基于目标资源的资源统一标识符，所述请求地址，以及所述第一身份信息，构建所述第一发现请求信息。
  8. 根据权利要求7所述的方法，其中，所述请求地址为多播地址。
  9. 一种信息处理方法，其中，应用于第二设备，所述方法包括：
    接收第一发现请求信息；所述第一发现请求信息包括第一安全域的第一身份信息；所述第一发现请求信息用于请求与所述第一身份信息匹配的目标设备的目标资源；
    基于所述第一身份信息，确定是否发送所述目标资源。
  10. 根据权利要求9所述的方法，其中，所述基于所述第一身份信息，确定是否发送所述目标资源，包括：
    获取所述第二设备的资源描述信息；
    判断所述资源描述信息中是否包括第二身份信息；所述第二身份信息为所述第二设备所属安全域的身份信息；
    若所述资源描述信息中包括所述第二身份信息，且所述第二身份信息与所述第一身份信息匹配，则确定发送所述目标资源。
  11. 根据权利要求10所述的方法，其中，所述方法还包括：
    若所述资源描述信息中包括所述第二身份信息，且所述第二身份信息与所述第一身份信息不匹配，则确定不发送所述目标资源。
  12. 根据权利要求10所述的方法，其中，所述方法还包括：
    若所述资源描述信息中不包括所述第二身份信息，则确定不发送所述目标资源。
  13. 根据权利要求9-12任一项所述的方法，其中，所述确定发送所述目标资源之后，还包括：
    确定所述第二设备为所述目标设备，并获取所述第二设备中所述目标资源；
    向第一设备发送所述目标资源。
  14. 一种信息处理装置，其中，应用与第一设备，所述信息处理装置包括：
    第一获取单元，配置为获取第一安全域的第一身份信息；
    第一处理单元，配置为基于所述第一身份信息，得到第一发现请求信息；所述第一发现请求信息用于请求与所述第一身份信息匹配的目标设备的目标资源；
    第一收发单元，配置为发送所述第一发现请求信息。
  15. 一种信息处理装置，其中，应用于第二设备，所述信息处理装置包括：
    第二收发单元，配置为接收第一发现请求信息；所述第一发现请求信息包括第一安全域的第一身份信息；所述第一发现请求信息用于发现与所述第一身份信息匹配的目标设备的目标资源；
    第二处理单元，配置为基于所述第一身份信息，确定是否发送所述目标资源。
  16. 一种设备，其中，所述设备包括：第一收发器、第一处理器和存储有计算机程序的第一存储器；
    所述第一收发器、所述第一处理器和所述第一存储器之间通过第一通信总线进行通信；
    所述第一处理器，配置为通过所述第一收发器实现与另一设备的通信；其中，
    所述第一处理器，还配置为结合所述第一收发器，运行所述第一存储器中存储的所述计算机程序时，执行权利要求1至8任一项所述方法的步骤。
  17. 一种设备，其中，所述设备包括：第二收发器、第二处理器和存储有计算机程序的第二存储器；
    所述第二收发器、所述第二处理器和所述第二存储器之间通过第二通信总线进行通信；
    所述第二处理器，配置为通过所述第二收发器实现与另一设备的通信；其中，
    所述第二处理器，还配置为结合所述第二收发器，运行所述第二存储器中存储的所述计算机程序时，执行权利要求9至13任一项所述方法的步骤。
  18. 一种计算机可读存储介质，其中，其上存储有计算机程序，所述计算机程序被第一处理器执行实现权利要求1至8任一项所述方法的步骤；或者；所述计算机程序被第二处理器执行9至13任一项所述方法的步骤。
PCT/CN2020/092685 2020-05-27 2020-05-27 信息处理方法及装置、设备、计算机存储介质 WO2021237527A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
PCT/CN2020/092685 WO2021237527A1 (zh) 2020-05-27 2020-05-27 信息处理方法及装置、设备、计算机存储介质
KR1020227045047A KR20230016652A (ko) 2020-05-27 2020-05-27 정보 처리 방법 및 장치, 기기, 컴퓨터 저장 매체
CN202080093549.3A CN114982203A (zh) 2020-05-27 2020-05-27 信息处理方法及装置、设备、计算机存储介质
EP20937418.0A EP4149060B1 (en) 2020-05-27 2020-05-27 Information processing method and apparatus, and device and computer storage medium
JP2022572547A JP2023533134A (ja) 2020-05-27 2020-05-27 情報処理方法及び装置、機器、コンピュータ記憶媒体
CN202211476242.9A CN115834202B (zh) 2020-05-27 2020-05-27 信息处理方法及装置、设备、计算机存储介质
US17/991,405 US20230089609A1 (en) 2020-05-27 2022-11-21 Method and apparatus for processing information, and device and computer storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/092685 WO2021237527A1 (zh) 2020-05-27 2020-05-27 信息处理方法及装置、设备、计算机存储介质

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/991,405 Continuation US20230089609A1 (en) 2020-05-27 2022-11-21 Method and apparatus for processing information, and device and computer storage medium

Publications (1)

Publication Number Publication Date
WO2021237527A1 true WO2021237527A1 (zh) 2021-12-02

Family

ID=78745503

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/092685 WO2021237527A1 (zh) 2020-05-27 2020-05-27 信息处理方法及装置、设备、计算机存储介质

Country Status (6)

Country Link
US (1) US20230089609A1 (zh)
EP (1) EP4149060B1 (zh)
JP (1) JP2023533134A (zh)
KR (1) KR20230016652A (zh)
CN (2) CN115834202B (zh)
WO (1) WO2021237527A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230216810A1 (en) * 2020-10-09 2023-07-06 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Information processing method and apparatus, and storage medium

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4149060B1 (en) * 2020-05-27 2024-05-29 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Information processing method and apparatus, and device and computer storage medium

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1705947A (zh) * 2003-10-24 2005-12-07 微软公司 服务发现及发布
CN101860474A (zh) * 2009-04-08 2010-10-13 中兴通讯股份有限公司 基于对等网络的资源信息处理方法及对等网络
CN105144636A (zh) * 2013-02-25 2015-12-09 高通股份有限公司 用于异构物联网（IoT）设备的适应性且可扩展的通用纲要
US20160006822A1 (en) * 2014-07-01 2016-01-07 Cable Television Laboratories, Inc. Service discovery within multi-link networks
CN105338510A (zh) * 2015-09-23 2016-02-17 深圳市黑目云网络有限公司 近距离场景下的设备发现方法及系统

Family Cites Families (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101431713B (zh) * 2007-11-09 2010-07-14 中国移动通信集团公司 一种资源访问方法及设备
CN101582882B (zh) * 2008-10-10 2011-04-20 华为技术有限公司 一种接入方法、网络系统和装置
US8627076B2 (en) * 2011-09-30 2014-01-07 Avaya Inc. System and method for facilitating communications based on trusted relationships
WO2013189059A1 (zh) * 2012-06-21 2013-12-27 华为技术有限公司 报文处理方法、装置、主机和网络系统
CN108512870B (zh) * 2017-02-27 2020-10-23 华为技术有限公司 接入物联网平台的方法、物联网平台和物联网设备
CN107196906A (zh) * 2017-03-31 2017-09-22 山东超越数控电子有限公司 一种安全域网络接入控制方法及系统
WO2019075317A1 (en) * 2017-10-12 2019-04-18 Convida Wireless, Llc INTERWORKING SERVICE FOR THE INTERNET OF RESTOUS OBJECTS
CN110418311B (zh) * 2018-04-28 2021-08-31 华为技术有限公司 一种基于多个终端的互联方法、装置及终端
CN108769009B (zh) * 2018-05-28 2021-01-19 深圳和而泰数据资源与云技术有限公司 数据通信方法、智能设备及智能网关
CN110830990B (zh) * 2018-08-09 2021-04-20 华为技术有限公司 一种身份信息的处理方法、装置及存储介质
CN110874804B (zh) * 2018-08-30 2023-07-21 阿里巴巴(上海)有限公司 资源获取处理方法、装置和系统
CN110380963B (zh) * 2019-01-17 2021-07-06 重庆邮电大学 一种高效快收敛的邻居发现方法
CN110516942A (zh) * 2019-08-15 2019-11-29 平安普惠企业管理有限公司 资源申请方法、装置、设备及计算机可读存储介质
CN110635942B (zh) * 2019-09-02 2022-11-04 上海商米科技集团股份有限公司 设备发现方法、物联网设备、物联网服务器
CN110620817A (zh) * 2019-09-17 2019-12-27 安徽华速达电子科技有限公司 一种物联网设备快速连接方法及其系统
CN110717337A (zh) * 2019-09-29 2020-01-21 北京声智科技有限公司 信息处理方法、装置、计算设备和存储介质
EP4080843B1 (en) * 2020-01-17 2024-10-30 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Security information discovery method, security information configuration method, and device
EP4149060B1 (en) * 2020-05-27 2024-05-29 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Information processing method and apparatus, and device and computer storage medium

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1705947A (zh) * 2003-10-24 2005-12-07 微软公司 服务发现及发布
CN101860474A (zh) * 2009-04-08 2010-10-13 中兴通讯股份有限公司 基于对等网络的资源信息处理方法及对等网络
CN105144636A (zh) * 2013-02-25 2015-12-09 高通股份有限公司 用于异构物联网（IoT）设备的适应性且可扩展的通用纲要
US20160006822A1 (en) * 2014-07-01 2016-01-07 Cable Television Laboratories, Inc. Service discovery within multi-link networks
CN105338510A (zh) * 2015-09-23 2016-02-17 深圳市黑目云网络有限公司 近距离场景下的设备发现方法及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4149060A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230216810A1 (en) * 2020-10-09 2023-07-06 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Information processing method and apparatus, and storage medium
US11991093B2 (en) * 2020-10-09 2024-05-21 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Information processing method and apparatus, and storage medium

Also Published As

Publication number Publication date
CN115834202A (zh) 2023-03-21
KR20230016652A (ko) 2023-02-02
EP4149060A1 (en) 2023-03-15
EP4149060B1 (en) 2024-05-29
US20230089609A1 (en) 2023-03-23
EP4149060A4 (en) 2023-07-12
JP2023533134A (ja) 2023-08-02
CN114982203A (zh) 2022-08-30
CN115834202B (zh) 2024-11-01

Similar Documents

Publication Publication Date Title
US20230089609A1 (en) Method and apparatus for processing information, and device and computer storage medium
WO2019042110A1 (zh) 一种订阅发布方法及服务器
US7292579B2 (en) Processing operations associated with resources on a local network
WO2019024676A1 (zh) 一种基于联盟链的链外数据访问方法和系统
US20180063879A1 (en) Apparatus and method for interoperation between internet-of-things devices
US10057208B2 (en) Visibility control for domain name system service discovery
CN113452592B (zh) 混合云架构下的跨云数据访问方法及装置
WO2017007783A1 (en) Wide area service discovery for internet of things
KR101701158B1 (ko) 홈 네트워크의 장치에 대한 원격 접속 제공 방법 및 시스템
JP2004252974A (ja) ホームネットワークデバイスへの効率的なアクセスが可能な制御ポイントサーバシステム及びそのための方法
US20180034923A1 (en) Device discovery framework
WO2021056738A1 (zh) 分布式系统nat穿透方法、装置、设备及存储介质
US20230045914A1 (en) Method and apparatus for controlling device in internet of things, and gateway device and storage medium
US20210383016A1 (en) Systems and methods for obtaining anonymized information derived from data obtained from external data providers
US8051157B2 (en) Discovery apparatus and method
US20190182356A1 (en) Data networking method in data-centric network system and apparatus implementing same
WO2021253244A1 (zh) 资源发布方法、装置、网关、云平台及计算机存储介质
WO2018032705A1 (zh) 用于提供无线接入点信息包的方法与设备
JP4886027B2 (ja) ネットワークでディスカバリーを実行する装置、システムおよびその方法
CN116320059A (zh) 楼宇协议数据处理方法、装置及系统
US20050050180A1 (en) Method of automatically determining device's nickname, and method of solving redundant nicknames for devices in network and network system thereof
US20090276496A1 (en) Systems, methods and computer program products for building a user's buddy list through public group membership
JP2022162518A (ja) 機器のレスポンスを用いて対象機器情報を決定するプログラム、装置及び方法、並びにデータベース構築装置
CN118140497A (zh) 订阅权限信息处理方法、装置、计算机设备及存储介质
Oosterhaven et al. A review of reference architectures enabling the Internet of Things

Legal Events

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

Ref document number: 20937418

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022572547

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 202217070656

Country of ref document: IN

ENP Entry into the national phase

Ref document number: 20227045047

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2020937418

Country of ref document: EP

Effective date: 20221209

NENP Non-entry into the national phase

Ref country code: DE