A security information discovery method, security information configuration method and device

By using broadcast or multicast messages to obtain security domain information in the home network, the problem of multiple interactions and security domain distinction when new devices join is solved, and convenient device discovery and network joining is achieved.

CN115866022BActive Publication Date: 2024-11-26GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP LTD
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
CN202211472013.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-01-17
Publication Date
2024-11-26
Estimated Expiration
2040-01-17

AI Technical Summary

Technical Problem

In a home network, new devices require multiple device interactions when joining, and it is difficult to distinguish the security domains under multiple security domains, which affects the efficiency of devices joining the network.

Method used

Through the first device, broadcast or multicast messages are sent to the second device in the network, request security domain information, and receive feedback security domain resource representations to obtain security domain identification ID and name, display it to the user, and realize convenient device discovery and Join the Internet.

Benefits of technology

This improves the efficiency of devices joining the network, and users can easily discover and join the required security domains, simplifying the network configuration process.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115866022B_ABST
    Figure CN115866022B_ABST
Patent Text Reader

Abstract

The present invention discloses a security information discovery method, a security information configuration method, a device, a chip, a computer-readable storage medium, a computer program product and a computer program. The method includes: a first device sends a broadcast or multicast message to M second devices in the network; M is an integer greater than or equal to 1; wherein the broadcast or multicast message includes a request for performing security domain discovery; the first device receives a representation of security domain resources fed back by N second devices; wherein N is an integer greater than or equal to 1 and less than or equal to M; the first device obtains L security domain information based on the representation of the security domain resources fed back by the N second devices, and displays the L security domain information; wherein L is an integer greater than or equal to 1; the security domain information includes: a security domain identification ID and a security domain name.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of the PCT international patent application PCT / CN2020 / 072866 with an application date of January 17, 2020, which entered the Chinese national phase with Chinese patent application number 202080093347.9 and the invention name being “A security information discovery method, security information configuration method and device”. Technical Field

[0002] The present invention relates to the field of information processing technology, and in particular to a security information discovery method, a security information configuration method, a device, a chip, a computer-readable storage medium, a computer program product, and a computer program. Background Art

[0003] In the related art, when a user's device enters and connects to a home network, it can discover the master device and other devices in the network (such as controlled devices or IoT (Internet of Things) devices in the home network). Furthermore, the user's device determines that the other device is configured for the master device by comparing the relevant information of the security domains of the two devices; then the user's device will request the master device to configure and enter the home network. It can be seen that if a newly added device wants to discover the security domain in the network, it needs to go through multiple device interactions, and it is difficult to distinguish the security domains when there are multiple security domains in the same network, which will affect the efficiency of new devices joining the home network. Summary of the invention

[0004] To solve the above technical problems, embodiments of the present invention provide a security information discovery method, a security information configuration method, a device, a chip, a computer-readable storage medium, a computer program product, and a computer program.

[0005] In a first aspect, a security information discovery method is provided, comprising:

[0006] The first device sends a broadcast or multicast message to M second devices in the network; M is an integer greater than or equal to 1; wherein the broadcast or multicast message includes a request for performing security domain discovery;

[0007] The first device receives representations of security domain resources fed back by N second devices; wherein N is an integer greater than or equal to 1 and less than or equal to M;

[0008] The first device obtains L security domain information based on the representation of the security domain resources fed back by the N second devices, and displays the L security domain information; wherein L is an integer greater than or equal to 1; the security domain information includes: a security domain identification ID and a security domain name.

[0009] In a second aspect, a security information discovery method is provided, comprising:

[0010] The second device receives a broadcast or multicast message sent by the first device in the network; wherein the broadcast or multicast message includes a request for performing security domain discovery;

[0011] The second device feeds back a representation of the security domain resources to the first device; the representation of the security domain resources includes security domain information, and the security domain information includes: a security domain identification ID and a security domain name.

[0012] In a third aspect, a security information configuration method is provided, comprising:

[0013] The third device generates security domain information, where the security domain information includes at least: a security domain identification ID and a security domain name;

[0014] The third device configures security domain information for at least one second device included in the network.

[0015] In a fourth aspect, a first device is provided, including:

[0016] The first communication unit sends a broadcast or multicast message to M second devices in the network; M is an integer greater than or equal to 1; wherein the broadcast or multicast message includes a request for performing security domain discovery; and receives a representation of security domain resources fed back by the N second devices; wherein N is an integer greater than or equal to 1 and less than or equal to M;

[0017] The first processing unit obtains L security domain information based on the representation of the security domain resources fed back by the N second devices, and displays the L security domain information; wherein L is an integer greater than or equal to 1; the security domain information includes: a security domain identification ID and a security domain name.

[0018] In a fifth aspect, a second device is provided, including:

[0019] A second communication unit receives a broadcast or multicast message sent by a first device in the network; wherein the broadcast or multicast message includes a request for performing security domain discovery; and feeds back a representation of security domain resources to the first device; the representation of the security domain resources includes security domain information, and the security domain information includes: a security domain identification ID and a security domain name.

[0020] In a sixth aspect, a third device is provided, including:

[0021] The third processing unit generates security domain information, wherein the security domain information includes at least: a security domain identification ID and a security domain name;

[0022] The third communication unit configures security domain information for at least one second device included in the network.

[0023] In a seventh aspect, a device is provided, comprising: a processor and a memory for storing a computer program that can be run on the processor,

[0024] The memory is used to store computer programs, and the processor is used to call and run the computer program stored in the memory to execute the steps of the above-mentioned method.

[0025] In an eighth aspect, a chip is provided, comprising: a processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes the aforementioned method.

[0026] In a ninth aspect, a computer-readable storage medium is provided, wherein the computer-readable storage medium is used to store a computer program, wherein the computer program enables a computer to execute the steps of the aforementioned method.

[0027] In a tenth aspect, a computer program product is provided, comprising computer program instructions, which enable a computer to execute the aforementioned method.

[0028] In an eleventh aspect, a computer program is provided, wherein the computer program enables a computer to execute the method as described above.

[0029] By adopting the above solution, when the first device enters the network, the device can support broadcast / multicast requests to discover the security domain resource representations fed back by multiple second devices, so that the first device can easily discover and obtain the security domain information existing in the network after entering the network. Then, the client can present the discovered security domain to the user, thereby ensuring the efficiency of the first device joining the network and discovering the security domain. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Figure 1-1 is a schematic diagram of a communication system architecture provided by an embodiment of the present invention;

[0031] Figure 1-2 It is a flow chart of a method for configuring OBT and activating other devices;

[0032] Figure 1-3 It is a schematic diagram of the structure of the architecture of OBT and other equipment;

[0033] Figure 2 A schematic diagram of a security information discovery method provided by an embodiment of the present invention;

[0034] Figure 3 A schematic diagram of a security information discovery method provided by an embodiment of the present invention Figure 2 ;

[0035] Figure 4 A schematic diagram of a security information configuration method provided by an embodiment of the present invention;

[0036] Figure 5 A schematic diagram of a system processing flow provided by an embodiment of the present invention;

[0037] Figure 6 A schematic diagram of a system processing flow provided by an embodiment of the present invention Figure 2 ;

[0038] Figure 7 A schematic diagram 1 showing security domains provided in an embodiment of the present invention;

[0039] Figure 8 A schematic diagram of a system processing flow provided by an embodiment of the present invention Figure 3 ;

[0040] Fig. 9 A schematic diagram of a system processing flow provided by an embodiment of the present invention Figure 4 ;

[0041] Fig.10 Schematic diagram of security domain provided by an embodiment of the present invention Figure 2 ;

[0042] Fig.11 A schematic diagram of a system processing flow provided by an embodiment of the present invention Figure 5 ;

[0043] Fig.12 A schematic diagram of a system processing flow provided by an embodiment of the present invention Figure 6 ;

[0044] Fig.13 Schematic diagram of security domain provided by an embodiment of the present invention Figure 3 ;

[0045] Figure 14 to Figure 16 A schematic diagram of the structure of three devices provided in the embodiments of the present invention;

[0046] Fig.17 A schematic diagram of the structure of a communication device provided in an embodiment of the present invention;

[0047] Fig.18 It is a schematic block diagram of a chip provided in an embodiment of the present application. DETAILED DESCRIPTION

[0048] In order to enable a more detailed understanding of the features and technical contents of the embodiments of the present invention, the implementation of the embodiments of the present invention is described in detail below in conjunction with the accompanying drawings. The attached drawings are for reference only and are not intended to limit the embodiments of the present invention.

[0049] The following will describe the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0050] The technical solutions of the embodiments of the present application can be applied to various communication systems, for example: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system or 5G system, etc.

[0051] For example, the communication system 100 used in the embodiment of the present application can be as follows: Figure 1-1As shown. The communication system 100 may include a network device 110, which may be a device that communicates with a UE 120 (or referred to as a communication terminal device, terminal device). The network device 110 may provide communication coverage for a specific geographical area, and may communicate with a UE located in the coverage area. Optionally, the network device 110 may be a network device (Base Transceiver Station, BTS) in a GSM system or a CDMA system, or a network device (NodeB, NB) in a WCDMA system, or an evolved network device (Evolutional Node B, eNB or eNodeB) in an LTE system, or a wireless controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the network device may be a mobile switching center, a relay station, an access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, a network side device in a 5G network, or a network device in a future evolved public land mobile network (Public Land Mobile Network, PLMN), etc.

[0052] In IoT related technologies, devices need to be activated before they can operate in the network or interact with other devices. The first step in activating a device is to configure device ownership. The legitimate user uses an activation tool (OBT) to establish device ownership using an owner transfer method (OTMs). After ownership is established, the OBT is used to configure the device, ultimately enabling the device to operate normally and interact with other devices. For example, see Figure 1-2 , which may include:

[0053] ⑴ The activation tool (OBT) discovers the devices that need to be configured in the network;

[0054] (2) The method of transferring the equipment to be configured back to its supported owner;

[0055] ⑶OBT establishes a secure connection with the device to be configured according to the selected owner transfer method;

[0056] (4) OBT configures its own ID to the deviceowneruuid attribute of / oic / sec / doxm of the device to establish the owner identity of the device;

[0057] ⑸OBT checks the security credential types supported by the device to be configured, such as symmetric keys, asymmetric keys, certificates, etc.;

[0058] ⑹OBT selects a suitable symmetric security credential;

[0059] ⑺OBT configures the selected symmetric security credentials to the device's / oic / sec / cred resource;

[0060] ⑻OBT assigns the device to be configured to the CMS key management service. CMS is usually a part of OBT. Considering the scalability and modular design, CMS can also be deployed separately as a service.

[0061] ⑼OBT configures its own ID to the owneruuid attribute of / oic / sec / doxm of the device and sets the owner of the / doxm resource;

[0062] ⑽OBT configures its own ID (CMS ID) to the owneruuid attribute of / oic / sec / cred of the device, and sets the owner of the / oic / sec / cred resource;

[0063] ⑾OBT configures the credentials used to establish a secure connection with CMS to the device's / oic / sec / cred resource;

[0064] ⑿OBT / CMS changes the device status to the business configuration status;

[0065] ⒀OBT / CMS configures the credentials used to establish a secure LAN connection with other devices to the device's / oic / sec / cred resource;

[0066] ⒁OBT / CMS changes the status of the equipment to normal working status.

[0067] The structure of the / oic / sec / doxm resource is:

[0068]

[0069] The OBT is the master of the network and can configure the interconnection between the client devices and the server devices in the network. After configuration, the OBT is the owner of the configured device. For example, Figure 1-3 As shown, this is a scenario for application in a home:

[0070] ①Mom installs the Client APP. As shown in the picture, the client application (APP) is installed on the mother's mobile phone;

[0071] ②Mom creates families and various user roles such as admin, family, guest, etc.

[0072] ③Mom discovers and configures the IoT device - DR-Bulb;

[0073] ④Mom can control DR-Bulb;

[0074] ⑤Dad installs the Client APP, as shown in the figure, the client application (APP) is installed on Dad’s mobile phone;

[0075] ⑥Mom's APP discovers Dad's APP, configures Dad's APP, and grants it family permissions, so that Dad can also control DR-Bulb;

[0076] ⑦Mom can also grant Dad "admin" privileges, so Dad can also configure and manage DR-Bulb;

[0077] ⑧For a new device, such as LR-Bulb, configure it in the same way as DR-Bulb;

[0078] ⑨For a new Client APP, configure its roles and permissions in the same way as Dad.

[0079] After Dad installs the APP in step 5 above, he opens the APP and connects to the home network, and can find Mom's APP and DR-Bulb in the network. Further, Dad's APP obtains the deviceuuid and devowneruuid in the doxm resources of the two respectively. By comparison, it can be concluded that: for Mom's APP, the deviceuuid and devowneruuid in the doxm resources are the same, then Mom's APP is OBT; for DR-Bulb, the deviceuuid and devowneruuid in the doxm resources are different, then DR-Bulb is a Client device or a Server device. At the same time, compare the devowneruuid of DR-Bulb with the deviceuuid of Mom's APP. If the two are the same, it is considered that DR-Bulb is configured by Mom's APP. After that, Dad's APP can find Mom's APP to request configuration into the home network, and then proceed to step 6.

[0080] If Dad's APP also wants to configure a new device as an OBT to enter the home network, Mom's APP can configure Dad's APP as a slave OBT, and Mom's APP as the master OBT. After that, the device configured by Dad can also access the home network and interconnect with DR-Bulb. In a security domain network, there is only one master OBT, but there can be multiple slave OBTs.

[0081] In the existing solution, multiple device interactions are required to discover the security domain in the network. In addition, it is difficult to distinguish the security domains when there are multiple security domains in the same network, especially when the security domain includes master and slave OBTs.

[0082] It should be understood that the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is only a description of the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0083] In order to enable a more detailed understanding of the features and technical contents of the embodiments of the present invention, the implementation of the embodiments of the present invention is described in detail below in conjunction with the accompanying drawings. The attached drawings are for reference only and are not intended to limit the embodiments of the present invention.

[0084] The embodiment of the present invention provides a security information discovery method, such as Figure 2 As shown, including:

[0085] Step 21: The first device sends a broadcast or multicast message to M second devices in the network; M is an integer greater than or equal to 1; wherein the broadcast or multicast message includes a request for performing security domain discovery;

[0086] Step 22: The first device receives representations of security domain resources fed back by N second devices; wherein N is an integer greater than or equal to 1 and less than or equal to M;

[0087] Step 23: The first device obtains L security domain information based on the representation of the security domain resources fed back by the N second devices, and displays the L security domain information; wherein L is an integer greater than or equal to 1; the security domain information includes: a security domain identification ID and a security domain name.

[0088] The embodiment of the present invention also provides a security information discovery method, such as Figure 3 As shown, including:

[0089] Step 31: The second device receives a broadcast or multicast message sent by the first device in the network; wherein the broadcast or multicast message includes a request for performing security domain discovery;

[0090] Step 32: The second device feeds back security domain resources to the first device; the security domain resources include security domain information, and the security domain information includes: a security domain identification ID and a security domain name.

[0091] The embodiment of the present invention provides a security information configuration method, such as Figure 4 As shown, including:

[0092] Step 41: The third device generates security domain information, where the security domain information at least includes: a security domain identification ID and a security domain name;

[0093] Step 42: The third device configures security domain information for at least one second device included in the network.

[0094] The aforementioned first device and third device may be terminal devices with client apps installed, such as smart phones, tablet computers, etc. The second device may be any controlled device in the Internet of Things or home network, or an IoT device, etc. It should also be noted that the first device, the third device, and the second device are all devices in the same network environment.

[0095] The solution provided by this embodiment is described below with reference to various examples:

[0096] In one example,

[0097] The security domain information only includes the security domain identifier (ID, Identity) and the security domain name. In other words, in this example, the security domain discoverability is not limited, or it is understood that all IoT second devices under the same network are discoverable devices.

[0098] Specifically, if Figure 5 As shown, it may include:

[0099] Step 51: After the third device is activated, the third device generates security domain information; in this example, the security domain information includes: a security domain identifier (ID) and a security domain name.

[0100] The method for generating the security domain identifier may be: the third device generates a Hash value according to its own root CA certificate, and uses the Hash value as the security domain ID.

[0101] The method of generating the security domain name may be: automatic generation.

[0102] Alternatively, the method for generating a security domain name can be: after generating a security domain ID, the third device can generate and display a prompt message, and the prompt message is used to request the user to set a security domain name; after receiving the user's setting, the third device obtains the security domain name.

[0103] Then, the representation of the security domain secDomain resource of the third device (that is, the aforementioned OBT) can be as follows:

[0104]

[0105] In this example, the third device may be the mother's device (such as a mobile phone); a client APP may be installed in the third device, and the third device may be configured and processed through the client APP, as follows:

[0106] A security domain resource may be added to the third device to configure and manage the security domain to which the device belongs.

[0107] The representation of security domain resources may include a corresponding Uniform Resource Identifier (URI), a resource type title, a resource type ID, an interface, and a description of related functions, such as shown in Table 1:

[0108]

[0109] Table 1

[0110] The attribute representation of the security domain resource may include a security domain ID and a security domain name, as shown in Table 2 below:

[0111]

[0112]

[0113] Table 2

[0114] Step 52: In the network where the third device is located, there are M second devices, or controllable devices, and the third device activates and configures the M second devices (for example, controllable devices or IoT devices); wherein M is an integer greater than or equal to 1.

[0115] The method of activating and configuring the at least one second device may be as follows: Figure 1-2 The method shown will not be repeated here.

[0116] Step 53: The third device obtains the security domain information configured by itself from the security domain resource (secDomain resource) representation, and the third device configures the security domain information for the M second devices included in the network.

[0117] The way in which the third device configures the M second devices may be to send a third instruction to the second device to configure the security domain ID and the security domain name to the M second devices:

[0118]

[0119] Correspondingly, any one of the M second devices receives a third instruction sent by a third device in the network; wherein the third device is a device capable of configuring security domain resources; and the third instruction includes security domain information.

[0120] Then, the M second devices configure their own security domain information based on the received third instruction to obtain a representation of the security domain resources.

[0121] At this point, the configuration of the security domain information of the M controllable devices or the M second devices included in the network where the third device is located is completed.

[0122] Step 54: The first device enters the network, and the first device sends a broadcast or multicast message to M second devices in the network; M is an integer greater than or equal to 1; wherein the broadcast or multicast message includes a request for performing security domain discovery;

[0123] The broadcast or multicast message is used for security domain discovery, and the specific content may be: RETRIEVE / oic / sec / secDomain.

[0124] Step 55: Each of the M second devices receives a broadcast or multicast message sent by a first device in the network, and the second device feeds back a representation of security domain resources to the first device;

[0125] The representation of the security domain resource includes security domain information, and the security domain information includes: a security domain identification ID and a security domain name.

[0126] The broadcast or multicast message includes a request for executing security domain discovery.

[0127] Step 56: The first device receives representations of security domain resources (ie, Resource representations) fed back by N second devices;

[0128] Among them, in this example, N=M, that is, since the security domain information set in this example does not limit the security domain discoverability, all devices are discoverable. Therefore, this step is specifically as follows: the first device receives the representation of the security domain resources fed back by M second devices.

[0129] Step 57: The first device obtains L security domain information based on the representation of the security domain resources fed back by the N second devices. In this example, the first device obtains at least one security domain information based on the representation of the security resources fed back by N (or M in this example) second devices. L can be 1. At this point, the first device side can display the names of the L security domains contained in the current network.

[0130] Furthermore, the following steps may be included:

[0131] Step 58: The first device obtains endpoint information of the N second devices.

[0132] Specific ways to obtain endpoint information include:

[0133] The first device sends a first instruction to the N second devices, and receives endpoint information fed back by the N second devices; wherein the first instruction is used to obtain the endpoint information of the second device; correspondingly, the second device receives the first instruction sent by the first device, and feeds back endpoint information to the first device; wherein the first instruction is used to obtain the endpoint information of the second device.

[0134] Alternatively, methods for obtaining endpoint information may include:

[0135] The first device obtains the endpoint information of the N second devices from the network side.

[0136] The first device may send a first instruction to the N second devices respectively to obtain endpoint information; the specific instruction may be: RETRIEVE / res?rt=secDomain.

[0137] In this example, the endpoint information includes at least one of the following:

[0138] The IP address of the second device and the port number of the second device.

[0139] Step 59: The first device sends a second instruction to the N second devices according to the endpoint information of the N second devices, and receives device information fed back by the N second devices; wherein the second instruction is used to obtain the device information of the second device.

[0140] Correspondingly, the second device receives the second instruction sent by the first device, and feeds back device information to the first device.

[0141] The second instruction may be: RETRIEVE / oic / d.

[0142] Furthermore, the device information may at least include: device type, ID, etc. Of course, it may also include more other contents, which are not exhaustively listed in this example.

[0143] Step 510: The first device displays the security domain name included in the security domain information corresponding to the L security domains, and the device information of the second device corresponding to each of the security domains.

[0144] That is, the first device may obtain N security domain information according to the representation of the security domain resources fed back by the N second devices; extract L security domain identifiers from the N security domain information, wherein the L security domain identifiers are all different;

[0145] The security domain names corresponding to the L security domain identifiers are displayed, and based on the device information fed back by the N second devices, the corresponding device information is displayed under each of the L security domain names.

[0146] Further, the aforementioned method of determining the L security domain identifiers may be: extracting a security domain identifier included in the N security domain information, comparing the extracted security domain identifier with the remaining security domain identifiers in pairs to determine whether the security domain identifiers are the same; if they are the same as the remaining security domain identifiers, then determining that the N security domain information obtains 1 security domain identifier, that is, there is one security domain in the network;

[0147] Alternatively, if there is a difference with the remaining security domain identifiers, the different security domain identifiers are placed in another set, and the currently extracted security domain identifier is first used as one of the L security domain identifiers; then, the above processing is repeated from another set until security domain identifiers that are different from each other are obtained.

[0148] Based on the above steps, the user can also view the L security domain names and at least one device information corresponding to each security domain name through the display interface (such as a display screen) of the first device;

[0149] Then the user can select a target security domain to join through the interactive interface of the first device, so that the first device joins the selected target security domain.

[0150] For example, suppose that in a home network, the third device, that is, Mom's mobile phone APP, acts as an OBT (activation tool), which first activates and configures itself, which may include configuring its own security domain information. A home network may include multiple IoT devices, such as three second devices, called Device1, Device2, and Device3. Then the third device, as OBT, configures the three devices respectively and sets the security domain information. At this point, OBT and Device1, Device2, and Device3 form a security domain network in the home.

[0151] Afterwards, the first device (such as the father's device, Dad's mobile phone APP) discovers and enters the home network by using the client APP installed on it. The first device can act as a client in the network, discover the controllable device (that is, the second device) through the client APP installed on it, and find the security domain corresponding to the controllable device (that is, the second device).

[0152] Take the third device as the mother's mobile phone as OBT, the network is the home network, the network contains three second devices, namely Device 1, Device 2, and Device 3, and the first device is Dad's client APP as an example. Figure 6 This embodiment is described by way of example, and the specific operation steps are as follows:

[0153] 1.OBT self-activation;

[0154] 2.OBT generates a hash value based on its own root CA certificate and uses it as the security domain ID. After that, it requests the user to set a security domain name and whether it is discoverable. After setting, the secDomain resource format of OBT is:

[0155]

[0156] 3. There are devices Device1, Device2 and Device3 in the network. OBT activates and configures the three devices according to the above method.

[0157] 4.OBT obtains the security domain information of its own configuration from the secDomain resource (that is, the representation of the security domain resource).

[0158] 5. OBT configures the security domain information of Device1, Device2, and Device3, and sends the following third instruction to the device:

[0159]

[0160] Set the uuid and name of the security domain to Device1, Device2, and Device3.

[0161] 6. Dad's client APP enters the network and sends broadcast / multicast messages to other devices in the network:

[0162] RETRIEVE / oic / sec / secDomain; performs security domain discovery.

[0163] 7. After receiving the request message, Device 1, Device 2, and Device 3 return the secDomain resource (representation of the security domain resource) to Dad's client APP.

[0164] 8. Dad's client can get secDomain resources (representation of security domain resources) returned from Device1, Device2, and Device3

[0165] Get its security domain information.

[0166] 9. Optionally, Dad's client further sends a first instruction to Device1, Device2 and Device3 respectively to obtain their endpoint information:

[0167] RETRIEVE / res? rt=secDomain; get the IP address and port number of the device. Alternatively, Dad's client obtains the endpoint information of the response messages of Device1, Device2 and Device3 from the network layer.

[0168] 10. Dad's client sends a second instruction to Device1, Device2 and Device3 respectively to obtain their device information based on the obtained endpoint information: RETRIEVE / oic / d; and obtains device information such as device type and ID.

[0169] 11. Dad's client presents the obtained network security domain information and the device information of each device under the security domain to user Dad (such as Figure 7 As shown), Dad can choose to add the client of this Dad to the security domain according to the needs of device interaction.

[0170] Another example is different from the above example in that the security domain information of this example also includes: security domain discoverability.

[0171] The security domain discoverability is used to characterize whether the security domain information corresponding to the second device can be discovered by other devices. It can specifically be a 1-bit value. For example, when it is set to the first value, it represents that it cannot be discovered, that is, it is true, and when it is set to the second value, it represents that it can be discovered, that is, it is false. Among them, the first value can be 1, and the second value can be 0; or vice versa, the first value is 0, and the second value is 1. Of course, other settings can also be used, which are not exhaustive in this example, as long as it can represent that the security domain discoverability is true or false.

[0172] That is to say, a security domain resource is added to the device to configure and manage the security domain to which the device belongs, as shown in Table 3.

[0173]

[0174] Table 3

[0175] The attributes of the security domain resource are shown in Table 4, which can be expressed as:

[0176]

[0177] Table 4

[0178] Specifically, if Figure 8 As shown, it may include:

[0179] Step 81: After the third device is activated, the third device generates security domain information; in this example, the security domain information includes: a security domain identifier (ID), a security domain name, and security domain discoverability.

[0180] The method for generating the security domain identifier may be: the third device generates a Hash value according to its own root CA certificate, and uses the Hash value as the security domain ID.

[0181] The method of generating the security domain name may be: automatic generation.

[0182] Alternatively, the method for generating a security domain name can be: after generating a security domain ID, the third device can generate and display a prompt message, and the prompt message is used to request the user to set a security domain name; after receiving the user's setting, the third device obtains the security domain name.

[0183] The security domain discoverability may be set according to user needs.

[0184] Then, the representation of the security domain secDomain resource of the third device (that is, the aforementioned OBT) can be as follows:

[0185]

[0186] Step 82: Same as step 52, no further details will be given.

[0187] Step 83: The third device obtains the security domain information configured by itself from the representation of the security domain resource (secDomain resource), and the third device configures the security domain information for the M second devices included in the network.

[0188] The third device may configure the M second devices by sending a third instruction to each of the second devices respectively to configure the security domain ID and the security domain name to the M second devices.

[0189] The difference from step 53 in the above example is that the third device can set the security domain discoverability of the second device to true or false according to the actual situation, that is, the content of the third instruction sent to each second device can be different. For example, if it is set to true, it is as follows:

[0190]

[0191]

[0192] If set to false, it will look like this:

[0193]

[0194] Correspondingly, any one of the M second devices receives a third instruction sent by a third device in the network; wherein the third device is a device capable of configuring security domain resources; and the third instruction includes security domain information.

[0195] Then, the M second devices configure their own security domain information based on the received third instruction to obtain a representation of the security domain resources.

[0196] At this point, the configuration of the security domain information of the M controllable devices or the M second devices included in the network where the third device is located is completed.

[0197] Step 84: The same as step 54 in the above example, and will not be described again.

[0198] Step 85: Each of the M second devices receives a broadcast or multicast message sent by the first device in the network;

[0199] Then, each of the second devices determines whether the security domain discoverability in the representation of the security domain resource stored in itself is true;

[0200] If the security domain discoverability is true, the second device feeds back a representation of the security domain resources; otherwise, the second device does not feed back a representation of the security domain resources.

[0201] The broadcast or multicast message includes a request for executing security domain discovery.

[0202] Step 86: The first device receives the representation of the security domain resource fed back by N second devices whose security domain discoverability is true among the M second devices;

[0203] In this example, N can be equal to M, or N can be less than M.

[0204] Step 87: The first device obtains L security domain information based on the representation of the security domain resources fed back by the N second devices. In this example, the first device obtains at least one security domain information based on the representation of the security resources fed back by the N second devices. L can be 1. At this point, the first device side can display the L security domain names contained in the current network.

[0205] Further,

[0206] Step 88 to step 810 are the same as step 58 to step 510 in the above example and will not be repeated here.

[0207] For example, suppose that in a home network, Mom's mobile phone APP (that is, the third device) acts as an OBT, then it first activates and configures itself. The network has three second devices called Device1, Device2, and Device3. OBT configures the three devices respectively and sets the security domain information. At this point, OBT and Device1, Device2, and Device3 form a security domain network in the home. Afterwards, Dad's mobile phone APP (that is, the first device) enters the home network. As a client, Dad's mobile phone APP discovers controllable devices and finds their corresponding security domains. The overall process is as follows: Fig. 9 As shown, the specific steps include:

[0208] 1.OBT self-activation

[0209] 2.OBT generates a hash value based on its own root CA certificate and uses it as the security domain ID. After that, it requests the user to set a security domain name and whether it is discoverable. After setting, the secDomain resource format of OBT is:

[0210]

[0211] 3. There are devices Device1, Device2 and Device3 in the network. OBT activates and configures the three devices according to the above method.

[0212] 4.OBT obtains the security domain information of its own configuration from the secDomain resource.

[0213] 5. OBT configures the security domain information of Device1 and Device2 and sends the following instructions to the devices:

[0214]

[0215] Set the security domain's uuid, name, and discoverability into the device.

[0216] 6.OBT configures the security domain information of Device3 and sends the following command to the device:

[0217]

[0218]

[0219] Set the security domain's uuid, name, and discoverability into the device.

[0220] 7. Dad's client APP enters the network and sends a broadcast / multicast message to other devices in the network: RETRIEVE

[0221] / oic / sec / secDomain, performs security domain discovery.

[0222] 8. After receiving the request message, Device 1 and Device 2 determine that the "discoverable" attribute value is true and return the secDomain resource to the client.

[0223] 9. After receiving the request message, Device 3 determines that the value of the "discoverable" attribute is false and does not respond to the client's request.

[0224] 10. Dad's client can obtain its security domain information from the secDomain resources returned by Device1 and Device2. Since Device3 does not return the secDomain resource, Dad's client cannot obtain Device3's security domain information.

[0225] 11. Optionally, Dad's client further sends a first instruction to Device1 and Device2 respectively to obtain their endpoint information:

[0226] RETRIEVE / res? rt=secDomain, get the IP address and port number of the device. Alternatively, the client obtains the endpoint information of the response message of Device1 and Device2 from the network layer.

[0227] 12. Based on the obtained endpoint information, the client sends the second instruction to Device1 and Device2 to obtain their device information:

[0228] RETRIEVE / oic / d to obtain device information such as device type and ID.

[0229] 13. The client presents the obtained network security domain information and the device information of each device under the security domain to the user Dad (such as Fig.10 As shown), Dad can choose to add this client to the security domain based on the needs of device interaction.

[0230] The last example is different from the previous example in that there may be two or more third devices in this example, each of which may set its own security domain, and the security domains set by different third devices may be the same or different;

[0231] Correspondingly, if the third device has a different security domain, it can set corresponding security domain information (including security domain identification, security domain name, and security domain discoverability) for some of the M second devices to which it is connected.

[0232] After the first device is connected to the network, it can obtain M security domain resources from M second devices respectively, and then determine and display L security domains, and finally determine the security domain to be added. In this example, L can be greater than or equal to 2.

[0233] Combine the following Fig.11 To explain this example in detail:

[0234] Step 1101: Each of two or more third devices generates security domain information.

[0235] Specifically, each third device executes the aforementioned step 81, and the order in which different third devices execute is not limited, that is, any third device can execute first, and ultimately all can generate their own corresponding security domain information; in this example, the security domain information includes: security domain identification (ID), security domain name, and security domain discoverability.

[0236] I will not go into details here.

[0237] Step 1102: Then, each third device activates and configures M second devices; the processing of each third device is the same as step 82 and will not be repeated here.

[0238] Step 1103: Among two or more third devices, each of the third devices obtains the security domain information configured by itself from the representation of the security domain resource (secDomain resource), and each of the third devices configures the security domain information for one or more second devices included in the network.

[0239] The difference from the previous step is that in this step, the second devices configured by different third devices are different. For example, the first third device is configured with second devices 1 and 2; then the second third device will not be configured with second devices 1 and 2, but with second devices 3, 4 and 5. No more exhaustive enumeration is given. In addition, there is no pre-set correspondence between which third device can configure which second device, and the third device that is first connected to (or accessed) the second device is the corresponding configuration device. For example, the first third device is first connected to the second device 1 and configured, and the second third device is then connected to the second device 1 and will not (or cannot) configure the second device 1 again.

[0240] The manner in which the third device configures each second device may be the same as the aforementioned step 83, which will not be described in detail.

[0241] Correspondingly, any one of the M second devices receives a third instruction sent by a third device in the network; wherein the third device is a device capable of configuring security domain resources; and the third instruction includes security domain information. Then, based on the received third instruction, the M second devices configure their own security domain information and obtain a representation of the security domain resources.

[0242] At this point, the configuration of the security domain information of the M controllable devices or the M second devices included in the network where the third device is located is completed.

[0243] Step 1104 to step 1106: are the same as step 84 to step 86 in the above example and will not be described again.

[0244] Step 1107: The first device obtains L security domain information based on the representation of the security domain resources fed back by the N second devices. In this example, the first device obtains at least one security domain information based on the representation of the security resources fed back by the N second devices. L can be an integer greater than or equal to 2. At this point, the first device side can display the L security domain names contained in the current network.

[0245] Furthermore, the following steps may be included:

[0246] Step 1108 - Step 1110 are the same as Step 88 - Step 810 in the aforementioned example and will not be repeated here.

[0247] The difference may be that the first device determines L security domains existing in the network where the first device is located according to the security domain ID included in the security domain resource fed back by each of the N second devices.

[0248] Specifically, the first device determines whether the security domain IDs contained in the representations of the security domain resources fed back by any two second devices are the same, and if they are different, saves them as different security domain IDs, and compares them respectively, and finally obtains L security domain IDs that are different from each other in the current network; displays the security domain names corresponding to the L security domain IDs; and displays the device information of one or more second devices corresponding to each security domain name. L is greater than or equal to 2.

[0249] Then, the user selects a target security domain to join from the L security domain names currently displayed.

[0250] Further,

[0251] In this example, a security domain resource is added to the device to configure and manage the security domain to which the device belongs. The attribute representation of the security domain resource is the same as Tables 3 and 4 in the above examples and will not be repeated here.

[0252] For example, assuming that in a home network, Mom's mobile phone APP acts as OBT 1 (that is, a third device, or called the main OBT), it will first self-activate and configure itself. Son's mobile phone APP also acts as OBT 2 (which can be understood as another third device, or called a slave OBT), self-activates and configures itself. The network has two second devices, Device 1 and Device 2. Mom's mobile phone APP and Son's mobile phone APP configure the two devices respectively and set the security domain information. At this point, Mom's mobile phone APP (OBT1) and Device 1, Son's mobile phone APP (OBT2) and Device 2 respectively form two independent security domain networks in the home.

[0253] After that, Dad's mobile phone APP enters the home network. As a client, Dad's mobile phone APP discovers controllable devices and finds their corresponding security domains.

[0254] Combine the following Fig.12 To explain this example in detail:

[0255] 1. Mom's mobile app is self-activated, generates a hash value based on its own root CA certificate, and uses the value as the security domain ID. After that, it requests the user to set a security domain name and whether it is discoverable. After setting, the secDomain resource format of Mom's mobile app is:

[0256]

[0257] 2. Son's mobile app is self-activated, generates a hash value based on its own root CA certificate, and uses the value as the security domain ID. After that, it requests the user to set a security domain name and whether it is discoverable. After setting, the secDomain resource format of Son's mobile app is:

[0258]

[0259] 3. There are devices Device1 and Device2 in the network, and Mom’s mobile APP and Son’s mobile APP are as mentioned above. Figure 1-2 The method activates and configures both devices.

[0260] 4. Mom’s mobile app obtains its own configured security domain information from the secDomain resource.

[0261] 5. Mom's mobile app configures the security domain information of Device 1 and sends the following third instruction to the device:

[0262] UPDATE / oic / sec / secDomain

[0263]

[0264] Set the security domain's uuid, name, and discoverability into the device.

[0265] 6. Son’s mobile app configures the security domain information of Device2 and sends the following third instruction to the device:

[0266]

[0267] Set the security domain's uuid, name, and discoverability into the device.

[0268] 7. Dad's client APP enters the network and sends broadcast / multicast messages to other devices in the network:

[0269] RETRIEVE / oic / sec / secDomain? discoverable=true

[0270] Perform security domain discovery.

[0271] 8. After receiving the request message, Device 1 and Device 2 determine that the "discoverable" attribute value is true and return the secDomain resource to the client.

[0272] 9. Dad's client can obtain its security domain information from the secDomain resources returned by Device1 and Device2.

[0273] 10. Optionally, Dad's client further sends instructions to Device1 and Device2 to obtain their endpoint information: RETRIEVE

[0274] / res? rt=secDomain, get the IP address and port number of the device. Alternatively, the client obtains the endpoint information of the response message of Device1 and Device2 from the network layer.

[0275] 11. Based on the obtained endpoint information, the client sends instructions to Device1 and Device2 to obtain their device information:

[0276] RETRIEVE / oic / d

[0277] Get device information such as device type and ID.

[0278] 12. The client compares the sdids of the two security domains to see if they are consistent. If they are inconsistent, they are considered to be two different security domains.

[0279] 13. The client presents the obtained network security domain information and the device information of each device under the security domain to the user Dad. Dad can choose to add this client to a security domain according to the needs of device interaction. Fig.13 As shown, the names of the two security domains, my home and my room, and the devices included in each security domain are displayed respectively.

[0280] It can be seen that by adopting the above-mentioned solution, when the first device enters the network, by enabling the device to support broadcast / multicast requests to discover the security domain resource representations fed back by multiple second devices, the first device can easily discover and obtain the security domain information existing in the network after entering the network, and then the client can present the discovered security domain to the user.

[0281] An embodiment of the present invention provides a first device, such as Fig.14 As shown, including:

[0282] The first communication unit 1401 sends a broadcast or multicast message to M second devices in the network; M is an integer greater than or equal to 1; wherein the broadcast or multicast message includes a request for performing security domain discovery; receives a representation of security domain resources fed back by N second devices; wherein N is an integer greater than or equal to 1 and less than or equal to M;

[0283] The first processing unit 1402 obtains L security domain information based on the representation of the security domain resources fed back by the N second devices, and displays the L security domain information; wherein L is an integer greater than or equal to 1; the security domain information includes: a security domain identification ID and a security domain name.

[0284] The embodiment of the present invention further provides a second device, such as Fig.15 As shown, including:

[0285] The second communication unit 1501 receives a broadcast or multicast message sent by a first device in the network; wherein the broadcast or multicast message includes a request for performing security domain discovery; and feeds back security domain resources to the first device; the security domain resources include security domain information, and the security domain information includes: a security domain identification ID and a security domain name.

[0286] The embodiment of the present invention provides a third device, such as Fig.16 As shown, including:

[0287] The third processing unit 1601 generates security domain information, where the security domain information at least includes: a security domain identification ID and a security domain name;

[0288] The third communication unit 1602 configures security domain information for at least one second device included in the network.

[0289] The aforementioned first device and third device may be terminal devices with client apps installed, such as smart phones, tablet computers, etc. The second device may be any controlled device in the Internet of Things or home network, or an IoT device, etc. It should also be noted that the first device, the third device, and the second device are all devices in the same network environment.

[0290] The solution provided by this embodiment is described below with reference to various examples:

[0291] In one example,

[0292] The security domain information only includes the security domain identifier (ID, Identity) and the security domain name. In other words, in this example, the security domain discoverability is not limited, or it is understood that all IoT second devices under the same network are discoverable devices.

[0293] Specifically, this may include:

[0294] After being activated, the third processing unit 1601 of the third device generates security domain information; in this example, the security domain information includes: a security domain identification (ID) and a security domain name.

[0295] In the network where the third device is located, there are M second devices, or controllable devices, and the third communication unit 1602 of the third device activates and configures the M second devices (for example, controllable devices or IoT devices); wherein M is an integer greater than or equal to 1.

[0296] The third processing unit 1601 of the third device obtains the security domain information configured by itself from the security domain resource (secDomain resource) representation, and the third communication unit 1602 of the third device configures the security domain information for the M second devices included in the network.

[0297] Correspondingly, the second communication unit 1501 of any one of the M second devices receives a third instruction sent by a third device in the network; wherein the third device is a device capable of configuring security domain resources; and the third instruction includes security domain information.

[0298] The second device also includes: a second processing unit 1502, which configures its own security domain information based on the received third instruction to obtain a representation of security domain resources.

[0299] The first device enters the network, and the first communication unit 1401 of the first device sends a broadcast or multicast message to M second devices in the network; M is an integer greater than or equal to 1; wherein the broadcast or multicast message includes a request for performing security domain discovery.

[0300] The second communication unit 1501 of each of the M second devices receives a broadcast or multicast message sent by a first device in the network, and feeds back a representation of the security domain resources to the first device;

[0301] The representation of the security domain resource includes security domain information, and the security domain information includes: a security domain identification ID and a security domain name.

[0302] The first communication unit 1401 of the first device receives the representations of security domain resources (ie, Resource representations) fed back by N second devices;

[0303] In this example, N=M.

[0304] The first processing unit 1402 of the first device acquires L security domain information based on the representation of the security domain resources fed back by the N second devices.

[0305] The first communication unit 1401 of the first device obtains the endpoint information of the N second devices.

[0306] Specific ways to obtain endpoint information include:

[0307] The first communication unit 1401 of the first device sends a first instruction to the N second devices, and receives endpoint information fed back by the N second devices; wherein the first instruction is used to obtain the endpoint information of the second device; correspondingly, the second communication unit 1501 of the second device receives the first instruction sent by the first device, and feeds back endpoint information to the first device; wherein the first instruction is used to obtain the endpoint information of the second device.

[0308] Alternatively, methods for obtaining endpoint information may include:

[0309] The first communication unit 1401 of the first device obtains the endpoint information of the N second devices from the network side.

[0310] In this example, the endpoint information includes at least one of the following:

[0311] The IP address of the second device and the port number of the second device.

[0312] The first communication unit 1401 of the first device sends a second instruction to the N second devices according to the endpoint information of the N second devices, and receives device information fed back by the N second devices; wherein the second instruction is used to obtain the device information of the second device.

[0313] Correspondingly, the second communication unit 1501 of the second device receives the second instruction sent by the first device, and feeds back device information to the first device.

[0314] Furthermore, the device information may at least include: device type, ID, etc. Of course, it may also include more other contents, which are not exhaustively listed in this example.

[0315] The first processing unit 1402 of the first device displays the security domain name included in the security domain information corresponding to the L security domains, and the device information of the second device corresponding to each of the security domains.

[0316] Based on the above steps, the user can also view L security domain names and at least one device information corresponding to each security domain name through a display interface (such as a display screen); then the user can select a target security domain to join through the interactive interface of the first device, so that the first device joins the selected target security domain.

[0317] Another example is different from the above example in that the security domain information of this example also includes: security domain discoverability.

[0318] The security domain discoverability is used to characterize whether the security domain information corresponding to the second device can be discovered by other devices. It can specifically be a 1-bit value. For example, when it is set to the first value, it represents that it cannot be discovered, that is, it is true, and when it is set to the second value, it represents that it can be discovered, that is, it is false. Among them, the first value can be 1, and the second value can be 0; or vice versa, the first value is 0, and the second value is 1. Of course, other settings can also be used, which are not exhaustive in this example, as long as it can represent that the security domain discoverability is true or false.

[0319] Specifically, this may include:

[0320] After the third device is activated, the third processing unit generates security domain information; in this example, the security domain information includes: a security domain identification (ID), a security domain name, and security domain discoverability.

[0321] The third device obtains the security domain information configured by itself from the representation of the security domain resource (secDomain resource), and the third communication unit of the third device configures the security domain information for the M second devices included in the network.

[0322] Correspondingly, the second communication unit of any one of the M second devices receives a third instruction sent by a third device in the network; wherein the third device is a device capable of configuring security domain resources; and the third instruction includes security domain information.

[0323] Then, the second processing units of the M second devices configure their own security domain information based on the received third instruction to obtain a representation of the security domain resources.

[0324] At this point, the configuration of the security domain information of the M controllable devices or the M second devices included in the network where the third device is located is completed.

[0325] The second communication unit of each of the M second devices receives a broadcast or multicast message sent by a first device in the network;

[0326] Then, the second processing unit of each of the second devices determines whether the security domain discoverability in the representation of the security domain resource stored in the second device is true;

[0327] If the security domain discoverability is true, the second communication unit of the second device feeds back the representation of the security domain resources; otherwise, the representation of the security domain resources is not fed back.

[0328] The broadcast or multicast message includes a request for executing security domain discovery.

[0329] The first communication unit of the first device receives the representation of the security domain resource fed back by N second devices whose security domain discoverability is true among the M second devices;

[0330] In this example, N can be equal to M, or N can be less than M.

[0331] The first processing unit of the first device obtains L security domain information based on the representation of the security domain resources fed back by the N second devices. In this example, the first device obtains at least one security domain information based on the representation of the security resources fed back by the N second devices. L can be 1. At this point, the first device side can display the L security domain names contained in the current network.

[0332] The remaining processing is the same as the previous example and will not be repeated here.

[0333] The last example is different from the previous example in that there may be two or more third devices in this example, each of which may set its own security domain, and the security domains set by different third devices may be the same or different;

[0334] Correspondingly, if the third device has a different security domain, it can set corresponding security domain information (including security domain identification, security domain name, and security domain discoverability) for some of the M second devices to which it is connected.

[0335] After the first device is connected to the network, it can obtain M security domain resources from M second devices respectively, and then determine and display L security domains, and finally determine the security domain to be added. In this example, L can be greater than or equal to 2.

[0336] Specifically, in two or more third devices, the third processing unit of each third device generates security domain information. Then, each third device activates and configures M second devices through the third communication unit.

[0337] Among two or more third devices, the third communication unit of each of the third devices obtains the security domain information configured by itself from the representation of the security domain resource (secDomain resource), and configures the security domain information for one or more second devices included in the network.

[0338] Correspondingly, the second communication unit of any one of the M second devices receives a third instruction sent by a third device in the network.

[0339] The first processing unit of the first device obtains L security domain information based on the representation of the security domain resources fed back by the N second devices. In this example, the first device obtains at least one security domain information based on the representation of the security resources fed back by the N second devices. L can be an integer greater than or equal to 2. At this point, the first device side can display the L security domain names contained in the current network.

[0340] The other processing of this example is the same as that of the previous example and will not be described in detail.

[0341] It can be seen that by adopting the above-mentioned solution, when the first device enters the network, by enabling the device to support broadcast / multicast requests to discover the security domain resource representations fed back by multiple second devices, the first device can easily discover and obtain the security domain information existing in the network after entering the network, and then the client can present the discovered security domain to the user.

[0342] Fig.17 It is a schematic structural diagram of a communication device 1700 provided in an embodiment of the present invention. The communication device in this embodiment may specifically be one of the first device, the second device and the third device in the aforementioned embodiments. Fig.17 The communication device 1700 shown includes a processor 1710. The processor 1710 can call and run a computer program from a memory to implement the method in the embodiment of the present invention.

[0343] Optionally, Fig.17 As shown, the communication device 1700 may further include a memory 1720. The processor 1710 may call and run a computer program from the memory 1720 to implement the method in the embodiment of the present invention.

[0344] The memory 1720 may be a separate device independent of the processor 1710 , or may be integrated into the processor 1710 .

[0345] Alternatively, if Fig.17 As shown, the communication device 1700 may further include a transceiver 1730, and the processor 1710 may control the transceiver 1730 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.

[0346] The transceiver 1730 may include a transmitter and a receiver. The transceiver 1730 may further include an antenna, and the number of antennas may be one or more.

[0347] Optionally, the communication device 1700 may implement the corresponding processes implemented by the network device in the various methods of the embodiments of the present invention, which will not be described in detail here for the sake of brevity.

[0348] Fig.18 is a schematic structural diagram of a chip according to an embodiment of the present invention. Fig.18 The chip 1800 shown includes a processor 1810, which can call and run a computer program from a memory to implement the method in the embodiment of the present invention.

[0349] Alternatively, if Fig.18 As shown, the chip 1800 may further include a memory 1820. The processor 1810 may call and run a computer program from the memory 1820 to implement the method in the embodiment of the present invention.

[0350] The memory 1820 may be a separate device independent of the processor 1810 , or may be integrated into the processor 1810 .

[0351] Optionally, the chip 1800 may further include an input interface 1830. The processor 1810 may control the input interface 1830 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0352] Optionally, the chip 1800 may further include an output interface 1840. The processor 1810 may control the output interface 1840 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0353] Optionally, the chip can be applied to one of the first device, the second device, and the third device in the embodiments of the present invention, and the chip can implement the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present invention. For the sake of brevity, they will not be repeated here.

[0354] It should be understood that the chip mentioned in the embodiment of the present invention can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0355] It should be understood that the processor of the embodiment of the present invention may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by the hardware integrated logic circuit in the processor or the instruction in the form of software. The above processor can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present invention can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiment of the present invention can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor can be combined to perform. The software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0356] It can be understood that the memory in the embodiment of the present invention can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0357] It should be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory in the embodiment of the present invention may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiment of the present invention is intended to include but not limited to these and any other suitable types of memory.

[0358] An embodiment of the present invention further provides a computer-readable storage medium for storing a computer program.

[0359] Optionally, the computer-readable storage medium can be applied to the network device or terminal device in the embodiments of the present invention, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present invention. For the sake of brevity, they are not repeated here.

[0360] An embodiment of the present invention further provides a computer program product, including computer program instructions.

[0361] Optionally, the computer program product can be applied to the network device or terminal device in the embodiments of the present invention, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present invention. For the sake of brevity, they are not repeated here.

[0362] An embodiment of the present invention also provides a computer program.

[0363] Optionally, the computer program may be applied to a network device or a terminal device in an embodiment of the present invention. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device in each method of the embodiment of the present invention. For the sake of brevity, they are not described here.

[0364] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0365] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0366] In the several embodiments provided by the present invention, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0367] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0368] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0369] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present invention, which should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims

1. A security information discovery method, comprising: The first device sends a broadcast or multicast message to M second devices in the network; M is an integer greater than or equal to 1; wherein the broadcast or multicast message includes a request for performing security domain discovery; The first device receives a representation of a security domain resource fed back by N second devices whose security domain discoverability is true among the M second devices; wherein the representation of the security domain resource includes security domain information, and the security domain information includes: a security domain identification ID, a security domain name, and wherein N is an integer greater than or equal to 1 and less than or equal to M; Among them, the security domain discoverability is used to characterize whether the security domain information corresponding to the second device can be discovered by other devices; when the security domain discoverability is a first value, the security domain discoverability characterizes that it cannot be discovered, and the security domain discoverability is true; when the security domain discoverability is a second value, the security domain discoverability characterizes that it can be discovered, and the security domain discoverability is false.

2. The method according to claim 1, wherein: The first device obtains L security domain information based on the representation of the security domain resources fed back by the N second devices, and displays the L security domain information; wherein L is an integer greater than or equal to 1.

3. The method according to claim 1, wherein: The security domain information in the representation of the security domain resource stored by the second device further includes: The security domain discoverability.

4. The method according to any one of claims 1 to 3, wherein: The method further comprises: The first device sends a first instruction to the N second devices, and receives endpoint information fed back by the N second devices; wherein the first instruction is used to obtain the endpoint information of the second device; or, The first device obtains the endpoint information of the N second devices from the network side.

5. The method according to claim 4, wherein: The endpoint information includes at least one of the following: The IP address of the second device and the port number of the second device.

6. The method according to claim 4 or 5, wherein: The method further comprises: The first device sends a second instruction to the N second devices according to the endpoint information of the N second devices, and receives device information fed back by the N second devices; wherein the second instruction is used to obtain the device information of the second device.

7. The method according to claim 6, wherein: The method further comprises: The first device determines L security domains existing in the network where the first device is located according to the security domain ID contained in the representation of the security domain resource fed back by each of the N second devices.

8. The method according to claim 2, wherein: When displaying the L security domain information, the method further includes: The first device displays the security domain name included in the security domain information corresponding to the L security domains, and the device information of the second device corresponding to each of the security domains.

9. A security information discovery method, comprising: The second device receives a broadcast or multicast message sent by the first device in the network; wherein the broadcast or multicast message includes a request for performing security domain discovery; The second device feeds back a representation of the security domain resource to the first device; the representation of the security domain resource includes security domain information, and the security domain information includes: a security domain identification ID and a security domain name; The second device feeding back the representation of the security domain resource to the first device includes: The second device determines whether the security domain discoverability in the representation of the security domain resource stored by itself is true; If the security domain discoverability is true, the second device feeds back a representation of the security domain resource; otherwise, the second device does not feed back a representation of the security domain resource; Among them, the security domain discoverability is used to characterize whether the security domain information corresponding to the second device can be discovered by other devices; when the security domain discoverability is a first value, the security domain discoverability characterizes that it cannot be discovered, and the security domain discoverability is true; when the security domain discoverability is a second value, the security domain discoverability characterizes that it can be discovered, and the security domain discoverability is false.

10. The method according to claim 9, wherein: The method further comprises: The second device receives a third instruction sent by a third device in the network; wherein the third device is a device capable of configuring security domain resources; and the third instruction includes security domain information.

11. The method according to claim 9, wherein: The security domain information in the representation of the security domain resource stored by the second device further includes: The security domain discoverability.

12. The method according to any one of claims 9 to 11, wherein: The method further comprises: The second device receives the first instruction sent by the first device, and feeds back endpoint information to the first device; wherein the first instruction is used to obtain the endpoint information of the second device.

13. The method according to claim 12, wherein: The endpoint information includes at least one of the following: The IP address of the second device and the port number of the second device.

14. The method according to claim 12 or 13, wherein: The method further comprises: The second device receives the second instruction sent by the first device, and feeds back device information to the first device; wherein the second instruction is used to obtain the device information of the second device.

15. A security information configuration method, comprising: The third device generates security domain information, where the security domain information includes at least: a security domain identification ID and a security domain name; The third device configures security domain information for at least one second device included in the network; Among them, the security domain information also includes: security domain discoverability, the security domain discoverability is used to characterize whether the security domain information corresponding to the second device can be discovered by other devices; when the security domain discoverability is a first value, the security domain discoverability characterizes that it cannot be discovered, and the security domain discoverability is true; when the security domain discoverability is a second value, the security domain discoverability characterizes that it can be discovered, and the security domain discoverability is false.

16. A first device, comprising: A first communication unit sends a broadcast or multicast message to M second devices in the network; M is an integer greater than or equal to 1; wherein the broadcast or multicast message includes a request for performing security domain discovery; receiving a representation of security domain resources fed back by N second devices whose security domain discoverability is true among the M second devices; the representation of the security domain resources includes security domain information, and the security domain information includes: a security domain identification ID, a security domain name, and wherein N is an integer greater than or equal to 1 and less than or equal to M; Among them, the security domain discoverability is used to characterize whether the security domain information corresponding to the second device can be discovered by other devices; when the security domain discoverability is a first value, the security domain discoverability characterizes that it cannot be discovered, and the security domain discoverability is true; when the security domain discoverability is a second value, the security domain discoverability characterizes that it can be discovered, and the security domain discoverability is false.

17. The first device according to claim 16, further comprising: The first processing unit obtains L security domain information based on the representation of the security domain resources fed back by the N second devices, and displays the L security domain information; wherein L is an integer greater than or equal to 1.

18. The first device according to claim 16, wherein: The security domain information in the representation of the security domain resource stored by the second device further includes: The security domain discoverability.

19. The first device according to any one of claims 16 to 18, wherein: The first communication unit sends a first instruction to the N second devices, and receives endpoint information fed back by the N second devices; wherein the first instruction is used to obtain the endpoint information of the second device; or, The endpoint information of the N second devices is obtained from the network side.

20. The first device according to claim 19, wherein: The endpoint information includes at least one of the following: The IP address of the second device and the port number of the second device.

21. The first device according to claim 19 or 20, wherein: The first communication unit sends a second instruction to the N second devices according to the endpoint information of the N second devices, and receives device information fed back by the N second devices; wherein the second instruction is used to obtain the device information of the second device.

22. The first device according to claim 17, wherein: The first processing unit determines L security domains existing in the network where the first device is located according to the security domain ID contained in the representation of the security domain resource fed back by each of the N second devices.

23. The first device according to claim 17 or 22, wherein: When displaying the L security domain information, the first processing unit displays the security domain names included in the security domain information corresponding to the L security domains, and the device information of the second device corresponding to each of the security domains.

24. A second device, comprising: The second communication unit receives a broadcast or multicast message sent by a first device in the network; wherein the broadcast or multicast message includes a request for performing security domain discovery; and feeds back a representation of security domain resources to the first device; the representation of the security domain resources includes security domain information, and the security domain information includes: a security domain identification ID and a security domain name; Wherein, the second device further includes: a second processing unit, determining whether the security domain discoverability in the representation of the security domain resource stored in the self-storage is true; The second communication unit, if the security domain discoverability is true, the second device feeds back the representation of the security domain resource; otherwise, the second device does not feed back the representation of the security domain resource; Among them, the security domain discoverability is used to characterize whether the security domain information corresponding to the second device can be discovered by other devices; when the security domain discoverability is a first value, the security domain discoverability characterizes that it cannot be discovered, and the security domain discoverability is true; when the security domain discoverability is a second value, the security domain discoverability characterizes that it can be discovered, and the security domain discoverability is false.

25. The second device according to claim 24, wherein: The second communication unit receives a third instruction sent by a third device in the network; wherein the third device is a device capable of configuring security domain resources; and the third instruction includes security domain information.

26. The second device according to claim 24, wherein: The security domain information in the representation of the security domain resource stored by the second device further includes: The security domain discoverability.

27. The second device according to any one of claims 24 to 26, wherein: The second communication unit receives a first instruction sent by the first device and feeds back endpoint information to the first device; wherein the first instruction is used to obtain the endpoint information of the second device.

28. The second device according to claim 27, wherein: The endpoint information includes at least one of the following: The IP address of the second device and the port number of the second device.

29. The second device according to claim 27 or 28, wherein: The second communication unit receives a second instruction sent by the first device and feeds back device information to the first device; wherein the second instruction is used to obtain the device information of the second device.

30. A third device, comprising: The third processing unit generates security domain information, wherein the security domain information includes at least: a security domain identification ID and a security domain name; A third communication unit configures security domain information for at least one second device included in the network; Among them, the security domain information also includes: security domain discoverability, the security domain discoverability is used to characterize whether the security domain information corresponding to the second device can be discovered by other devices; when the security domain discoverability is a first value, the security domain discoverability characterizes that it cannot be discovered, and the security domain discoverability is true; when the security domain discoverability is a second value, the security domain discoverability characterizes that it can be discovered, and the security domain discoverability is false.

31. An apparatus comprising: a processor and a memory for storing a computer program capable of being executed on the processor, The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the steps of the method as described in any one of claims 1 to 15.

32. A chip, comprising: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 15.

33. A computer-readable storage medium, the computer-readable storage medium being used to store a computer program, the computer program causing a computer to execute the steps of the method according to any one of claims 1 to 15.

Citation Information

Patent Citations

  • Access control method as well as equipment and system

    CN103152361A

  • Method of establishing networking terminal safety domain and system thereof

    CN105577623A

  • Network discovery

    CN107113703A

  • Resource allocation method and network equipment

    CN107153565A

  • Cross-security-domain communication method, a server and a readable storage medium

    CN109981725A