WO2024108374A1 - 配置设备的方法及装置 - Google Patents
配置设备的方法及装置 Download PDFInfo
- Publication number
- WO2024108374A1 WO2024108374A1 PCT/CN2022/133415 CN2022133415W WO2024108374A1 WO 2024108374 A1 WO2024108374 A1 WO 2024108374A1 CN 2022133415 W CN2022133415 W CN 2022133415W WO 2024108374 A1 WO2024108374 A1 WO 2024108374A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- rcac
- information
- certificate center
- identifier
- certificate
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 171
- 230000008569 process Effects 0.000 claims abstract description 47
- 238000012795 verification Methods 0.000 claims description 38
- 238000009941 weaving Methods 0.000 claims description 28
- 230000015654 memory Effects 0.000 claims description 23
- 238000004590 computer program Methods 0.000 claims description 21
- 238000007726 management method Methods 0.000 description 42
- 238000010586 diagram Methods 0.000 description 8
- 239000004744 fabric Substances 0.000 description 7
- 238000004891 communication Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 5
- 101001121408 Homo sapiens L-amino-acid oxidase Proteins 0.000 description 4
- 102100026388 L-amino-acid oxidase Human genes 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 101100233916 Saccharomyces cerevisiae (strain ATCC 204508 / S288c) KAR5 gene Proteins 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 101100012902 Saccharomyces cerevisiae (strain ATCC 204508 / S288c) FIG2 gene Proteins 0.000 description 2
- 101150053844 APP1 gene Proteins 0.000 description 1
- 101100189105 Homo sapiens PABPC4 gene Proteins 0.000 description 1
- 102100039424 Polyadenylate-binding protein 4 Human genes 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
Definitions
- the present application relates to the field of communication technology, and more specifically, to a method and apparatus for configuring a device.
- the present application provides a method and apparatus for configuring a device.
- the following introduces various aspects involved in the embodiments of the present application.
- a method for configuring a device comprising: a first device verifies a root certification center certificate RCAC of a second device through a certificate center, wherein the certificate center is capable of determining the legitimacy of the RCAC.
- a method for configuring a device including: a second device receives ninth information sent by a first device, wherein the ninth information is used to request a root certification center certificate RCAC of the second device; and the second device sends tenth information to the first device, wherein the tenth information is used to indicate the RCAC.
- a device for configuring a device comprising: a verification unit for verifying a root certification center certificate RCAC of a second device through a certificate center, wherein the certificate center is capable of determining the legitimacy of the RCAC.
- a device for configuring a device comprising: a receiving unit for receiving ninth information sent by a first device, wherein the ninth information is used to request a root certification center certificate RCAC of the device; and a sending unit for sending tenth information to the first device, wherein the tenth information is used to indicate the RCAC.
- an apparatus for configuring a device comprising a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory to execute the method described in the first aspect.
- a device for configuring a device comprising a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory to execute the method described in the second aspect.
- an apparatus for configuring a device comprising a processor for calling a program from a memory to execute the method described in the first aspect.
- an apparatus for configuring a device comprising a processor for calling a program from a memory to execute the method described in the second aspect.
- a chip comprising a processor for calling a program from a memory so that a device equipped with the chip executes the method described in the first aspect.
- a chip comprising a processor for calling a program from a memory so that a device equipped with the chip executes the method described in the second aspect.
- a computer-readable storage medium on which a program is stored, wherein the program enables a computer to execute the method described in the first aspect.
- a computer-readable storage medium on which a program is stored, wherein the program enables a computer to execute the method described in the second aspect.
- a computer program product comprising a program, wherein the program enables a computer to execute the method described in the first aspect.
- a computer program product comprising a program, wherein the program enables a computer to execute the method described in the second aspect.
- a computer program is provided, wherein the computer program enables a computer to execute the method described in the first aspect.
- a computer program is provided, wherein the computer program enables a computer to execute the method described in the second aspect.
- the first device can verify the root certification center certificate RCAC of the second device through the certificate center, thereby reducing the risk of being attacked during the configuration process and avoiding the problem of sensitive data leakage of the ecological platform.
- FIG. 1 is an example diagram of an application scenario of an embodiment of the present application.
- FIG2 is a schematic flow chart of a method for configuring a device in an embodiment of the present application. .
- FIG3 is a schematic flowchart of a method for configuring a device provided in one embodiment of the present application.
- FIG. 4 is a schematic flowchart of a method for configuring a device provided in another embodiment of the present application.
- FIG5 is a schematic flowchart of a method for configuring a device provided in yet another embodiment of the present application.
- FIG6 is a schematic flowchart of a method for configuring a device provided in yet another embodiment of the present application.
- FIG. 7 is a schematic structural diagram of an apparatus for configuring a device according to an embodiment of the present application.
- FIG8 is a schematic structural diagram of an apparatus for configuring a device provided in another embodiment of the present application.
- FIG. 9 is a schematic structural diagram of a device provided in an embodiment of the present application.
- FIG1 is an example diagram of an application scenario 100 of an embodiment of the present application.
- the application scenario 100 may include a network 110, and a terminal device 112 and a terminal device 130 are located in (the coverage range of) the network 110.
- the terminal device 112 may perform data transmission with the terminal device 130.
- the terminal device 112 may be a management device of the network 110, and the terminal device 112 may configure the terminal device 130 into the network 110 (i.e., establish a connection with the network 110).
- the terminal device 130 may be further configured in other networks.
- the application scenario 100 may also include a network 120, and the terminal device 122 and the terminal device 130 are located in (within the coverage range of) the network 120. It can be seen that the terminal device 130 may be located in both the network 110 and the network 120.
- the terminal device 122 may perform data transmission with the terminal device 130.
- the terminal device 122 may be a management device of the network 120, and the terminal device 122 may configure the terminal device 130 in the network 120 (i.e., establish a connection with the network 120).
- Network 110 and network 120 can provide services to terminal devices within their coverage, for example, establish network connections with terminal devices within their coverage, and perform data transmission between multiple terminal devices within their coverage.
- Network 110 and network 120 can be fabric networks.
- Network 110 and network 120 can be called ecological networks or ecological platforms.
- FIG1 exemplarily shows two networks and three terminal devices.
- the application scenario 100 may include more or fewer networks or terminal devices, which is not limited in the embodiments of the present application.
- the embodiments of the present application are not limited to the system architecture shown in FIG1 , and the technical solutions of the embodiments of the present application can be applied to various system architectures, which is not limited in the embodiments of the present application.
- the terminal device 112 or the terminal device 122 in the embodiment of the present application may also be referred to as a management device, a user device, etc.
- the terminal device 112 may be a device with administrator privileges in the network 110 (i.e., a management device), and the terminal device 122 may also be a device with administrator privileges in the network 120.
- the terminal device 112 or the terminal device 122 may be a mobile phone, a tablet computer (Pad), a laptop computer, a PDA, a wearable device, etc.
- the terminal device 130 in the embodiment of the present application may also be referred to as a node device, a user device, etc.
- the terminal device 130 may be a lighting, door lock, blinds, television, HVAC system, security sensor and controller, gateway, etc.
- the terminal device 130 may establish a connection with the network 110 and the network 120, and perform data transmission with the terminal device 112 in the network 110 and the terminal device 122 in the network 120.
- the process of the terminal device 112 configuring the terminal device 130 to the network 110 can be called the first network configuration; when the terminal device 122 configures the terminal device 130 to the network 120, the terminal device 130 has established a connection with the network 110, then the process of the terminal device 122 configuring the terminal device 130 to the network 120 can be called the second network configuration.
- the second network configuration does not specifically refer to the second network configuration, and all non-first network configurations except the first network configuration can be called the second network configuration. The process of the second network configuration is described below in conjunction with FIG2 .
- management device A is a configurator in ecological network A, and has administrator privileges in ecological network A.
- Management device B is a configurator in ecological network B, and has administrator privileges in ecological network B.
- the user device has established a connection with ecological network A.
- Ecological network A and ecological network B can correspond to different ecological manufacturers.
- ecological network A can correspond to Google's ecological A
- ecological network B can correspond to Huawei's ecological B.
- method 200 may include the following steps:
- a user turns on a configuration mode of a user device.
- the user may input an operation instruction to the management device A to start a related application (APP) in the management device A and enable the APP to perform a configuration mode (of the user device).
- APP related application
- Management device A generates a configuration token OT.
- the APP in the management device A can generate an Onboarding Token (OT).
- OTP Onboarding Token
- the actions performed by the management device A can all be performed by the APP of the management device A.
- Management device A sends a configuration start instruction to the user equipment.
- the instruction may carry the configuration token generated in S202 .
- S204 The user equipment enters a configuration discovery mode.
- S205 The user equipment sends a response message to the management equipment A.
- Management device A sends a configuration token to management device B.
- management device A may send the configuration token generated in S202 to management device B via email, voice, or the like.
- Management device B discovers the user equipment.
- Management device B uses the configuration token to establish a secure connection with the user device.
- This secure connection can be a password authenticated session establishment (PASE) connection.
- PASE password authenticated session establishment
- the management device B authenticates the certification declaration (CD) of the user device.
- management device B creates an identifier for ecological network B.
- the management device B creates a network identifier (fabricID) for the ecological network B.
- fabricID network identifier
- the user device sends a certificate signing request (CSR) to the management device B.
- CSR certificate signing request
- the user device may be a desk lamp (bulb), and the user device may send a certificate request CSR.bulb to the management device B.
- the user device may be a desk lamp (bulb), and the user device may send a certificate request CSR.bulb to the management device B.
- management device B sends the network identification and CSR to the certificate authority (CA).
- CA certificate authority
- CA may refer to the authentication center (or certificate issuing center) corresponding to the ecological network B.
- the management device B may send CSR.bulb and fabricID to CA to request a device certificate.
- CA sends the device certificate to management device B.
- the device certificate may refer to the device certificate corresponding to the ecological network B.
- the CA may send B.OC.bulb (device certificate) to the management device B.
- the management device B configures the user equipment.
- Management device B can configure the device certificate B.OC.bulb and access control permission ACL.Bulb.B.APP1 to the user device (bulb).
- the device certificate corresponding to the ecological network B may be determined based on the root certificate authority certificate (RCAC) of the ecological manufacturer corresponding to the ecological network B.
- the RCAC may include multiple formats.
- the format of RCAC in the X.509 standard can be as follows:
- Matter TLV format of RCAC can be as follows:
- ecosystem A (management device A in it) has the network configuration password (such as configuration token, etc.) of the user device and shares it with management device B in ecosystem B.
- network configuration password such as configuration token, etc.
- ecosystem A (management device A in it) can launch a man-in-the-middle attack to eavesdrop on the communication between management device B and the user device and obtain the secret data of ecosystem B.
- management device A can create a virtual intermediate device and modify the network configuration password and related data sent to management device B so that management device B establishes a connection with the intermediate device (rather than the user device).
- a connection can be established between the intermediate device and the user device, so that management device A can eavesdrop on the communication between management device B and the user device and obtain the secret data of ecosystem B. Therefore, the existing secondary network configuration process is at risk of being attacked, and the problem of sensitive data leakage of the ecological platform may occur.
- the present application proposes a method and apparatus for configuring a device, which can improve the security of the network configuration process.
- the embodiments of the present application are described in detail below in conjunction with Figures 3 to 6.
- FIG3 is a schematic flow chart of a method for configuring a device according to an embodiment of the present application.
- the method 300 shown in FIG3 may include step S310, which is as follows:
- the first device verifies the RCAC of the second device through the certificate center.
- the first device may be a management device (such as a commissioner) in a network (such as ecosystem B).
- the second device may be a user device.
- the certificate center can determine the legitimacy of the RCAC.
- the certificate center can be a blockchain, a cloud, an authentication center (such as the authentication center in Figure 2) or other servers.
- the certificate center can be a distributed compliance ledger (DCL).
- DCL distributed compliance ledger
- the RCAC of each ecological manufacturer can be stored in a common certificate center.
- the certificate center can take security measures so that the RCAC it stores can only be queried and cannot be tampered with.
- the storage method of RCAC in the certificate center will be described in combination with Tables 1 to 6.
- method 300 may further include step S320, which is as follows:
- S320 The first device determines whether the current configuration is a secondary network distribution.
- the first device may perform the above step S310.
- the RCAC of the second device is verified to be legal in the above step S310, the second device is subjected to secondary network distribution, which can reduce the risk of being attacked during the configuration process and improve the security of the network configuration process.
- the first device may determine whether the current configuration is a secondary network distribution; when the current configuration is a secondary network distribution, the first device may verify the RCAC of the second device through a certificate center.
- Method 1 Determine whether the current configuration is a secondary network configuration according to whether the second device has configured a weaving network.
- the first device can send the fifth information to the second device, and the fifth information can be used to request the weaving network identifier of the second device; if the second device has been configured with a weaving network, the second device can send the sixth information to the first device; if the second device is not configured with a weaving network, the second device may not send the sixth information to the first device; accordingly, if the first device receives the sixth information sent by the second device, the first device can determine that the current configuration is a secondary network distribution; if the first device does not receive the sixth information sent by the second device, the first device can determine that the current configuration is a primary network distribution; wherein the sixth information can be used to indicate the weaving network identifier.
- the second device may send the sixth information to the first device regardless of whether the woven network is configured. At this time, the second device may indicate different return values through the sixth information to indicate whether it has configured the woven network.
- the second device Before sending the sixth information, the second device can use the first private key to sign the weaving network identifier (or return value) carried by the sixth information to obtain the identification information.
- the first device can use the first public key to verify the identification information to obtain the weaving network identifier in the identification information.
- the first public key can correspond to the first private key.
- Method 2 determining whether the current configuration is a secondary network distribution according to the first attribute value of the second device.
- the first device may send seventh information to the second device, and the seventh information may be used to request the first attribute value of the second device; after receiving the seventh information, the second device may send eighth information to the first device, and the eighth information may be used to indicate the first attribute value.
- the first device may determine whether it is a secondary network configuration based on the value of the first attribute value. For example, if the first attribute value is a non-zero value, the first device may determine that the current configuration is a secondary network configuration; if the first attribute value is zero, the first device may determine that the current configuration is a first network configuration.
- the second device Before sending the eighth information, the second device may use the second private key to sign the first attribute value to obtain the attribute information. Accordingly, after the first device receives the eighth information, the first device may use the second public key to verify the attribute information to obtain the first attribute value in the attribute information.
- the second public key may correspond to the second private key.
- the first device may obtain the RCAC of the second device.
- the method 300 may further include steps S330 and S340, which are as follows:
- S330 The first device sends ninth information to the second device.
- the ninth information may be used to request the RCAC of the second device.
- S340 The second device sends tenth information to the first device.
- the tenth information may be used to indicate the RCAC of the second device.
- the second device may also use the third private key to sign the RCAC to obtain the RCAC information.
- the tenth information may include the RCAC information.
- the first device may verify the RCAC information using the third public key to determine that the RCAC information includes the RCAC.
- the third public key may correspond to the third private key.
- the first device can verify the RCAC of the second device through the certificate center. For example, the first device can verify the RCAC of the second device through the RCAC stored in the certificate center.
- the first device can verify the RCAC of the second device through multiple methods, as follows:
- Method 1 Determine whether to configure the second device according to the RCAC of the second device.
- the first device may look up the RCAC in the certificate authority.
- the certificate center may include a third syntax, which may include a manufacturer syntax and/or a syntax constructed for recording RCAC, and the third syntax may include a field for recording RCAC.
- the certificate center may include a database corresponding to the third syntax, which may be defined based on a data structure of the third syntax, and the RCAC of each ecological manufacturer may be stored in a field for recording RCAC in the database.
- an RCAC syntax (schema) may be added to the DCL, and the RCAC syntax is used to store the root CA certificate of the ecosystem vendor.
- the structure of the RCAC syntax may be as shown in Table 1 below.
- a TrustRootCertificate field may be added to the vendor syntax of the DCL.
- the vendor syntax and the added TrustRootCertificate field may be as shown in Table 2 below.
- the first device may search for the RCAC of the second device in the RCAC syntax or the manufacturer syntax (or in a database corresponding to the syntax).
- the first device can determine that the second device is bound to an illegal ecological platform.
- the first device may output first information, and the first information may be used to inquire the user whether to continue to configure the second device. Further, if the user instructs to continue to configure the second device, the first device may trigger the configuration process of the second device.
- the first device can trigger the configuration process of the second device.
- the method 400 includes steps S401 to S408 , which are specifically as follows:
- the configurator discovers the user equipment and establishes a PASE connection with the user equipment.
- S402 The configurator configures basic information of the user equipment.
- the time of the user device For example, the time of the user device, the area where the user device is located, etc.
- the configurator authenticates the legitimacy of the user device.
- the configurator determines whether the current configuration is a secondary network configuration.
- the configurator can determine whether the user equipment has been configured with Fabric, and if so, determine that the current configuration is a secondary network configuration.
- S405 The configurator obtains the RCAC of the user equipment.
- the configurator can read the RCAC that has been configured on the user device.
- the configurator searches for RCAC in the DCL.
- the configurator may connect to the DCL and search the DCL for the RCAC obtained from the user device.
- the configurator may prompt the user that the user device may be bound to an illegal ecological platform and ask the user whether to continue configuring the user device.
- S408 The configurator configures the user equipment.
- the configurator can initiate a CSR request to configure the NOC for the user device.
- the configurator may initiate a CSR request to configure the NOC for the user equipment.
- the first device may further verify the RCAC of the second device through a manufacturer identifier corresponding to the RCAC in the certificate center.
- the first device can search for the manufacturer identifier corresponding to RCAC in the certificate center; the first device can also obtain the manufacturer identifier of the second device; further, the first device can compare the manufacturer identifier of the second device (i.e., the manufacturer identifier corresponding to the RCAC of the second device) with the manufacturer identifier corresponding to RCAC (found in the certificate center), and verify the RCAC of the second device (or verify the manufacturer identifier corresponding to the RCAC of the second device) based on the comparison result.
- the manufacturer identifier of the second device i.e., the manufacturer identifier corresponding to the RCAC of the second device
- the manufacturer identifier corresponding to RCAC found in the certificate center
- the certificate center may include a fourth grammar, the fourth grammar includes a manufacturer grammar and/or a grammar constructed for recording RCAC, and the fourth grammar includes a field for recording RCAC and a field for recording a manufacturer identifier.
- the certificate center may include a database corresponding to the fourth grammar, the database may be defined based on a data structure of the fourth grammar, the RCAC of the second device may be stored in a field for recording RCAC in the database, and the manufacturer identifier corresponding to the RCAC of each ecological manufacturer may be stored in a field for recording the manufacturer identifier in the database.
- a field for storing the vendor ID corresponding to the RCAC (such as a VendorID field) may be added to the RCAC syntax in Table 1.
- the structure of the modified RCAC syntax may be as shown in Table 3 below.
- the first device may search for the vendor identifier corresponding to RCAC in the RCAC syntax (or in a database corresponding to the syntax).
- the first device may search for the vendor identifier corresponding to RCAC (such as the VendorID field) in the vendor syntax (or in a database corresponding to the syntax).
- the first device may determine that the second device is bound to an illegal ecological platform.
- the first device may also output second information, and the second information may be used to inquire the user whether to continue to configure the second device. Further, when the user instructs to continue to configure the second device, the first device may trigger the configuration process of the second device.
- the first device can trigger the configuration process of the second device. For example, the first device can initiate a certificate signing request (CSR) request to configure a node operational certificate (NOC) for the second device.
- CSR certificate signing request
- NOC node operational certificate
- the method 500 includes steps S501 to S511 , which are specifically as follows:
- the configurator discovers a user equipment and establishes a PASE connection with the user equipment.
- S502 The configurator configures basic information of the user equipment.
- the time of the user device For example, the time of the user device, the area where the user device is located, etc.
- S503 The configurator authenticates the legitimacy of the user equipment.
- the configurator determines whether the current configuration is a secondary network configuration.
- the configurator can determine whether the user equipment has been configured with Fabric, and if so, determine that the current configuration is a secondary network configuration.
- S505 The configurator obtains the RCAC of the user equipment.
- the configurator can read the RCAC that has been configured on the user device.
- the configurator searches for RCAC in the DCL.
- the configurator may connect to the DCL and search the DCL for the RCAC obtained from the user device.
- the configurator may prompt the user that the user device may be bound to an illegal ecological platform and ask the user whether to continue configuring the user device.
- the configurator can initiate a CSR request to configure the NOC for the user device.
- the configurator finds the RCAC in the DCL and then executes S508.
- the configurator obtains the manufacturer identification (VID) of the user equipment.
- the configurator searches the DCL for the manufacturer ID corresponding to the RCAC.
- the configurator compares the VID of the user equipment with the manufacturer identifier corresponding to the RCAC (found in the DCL) to see if they are consistent.
- the configurator can prompt the user device that it may be bound to an illegal ecological platform and ask the user whether to continue configuring the user device.
- S511 The configurator configures the user equipment.
- the configurator can initiate a CSR request to configure the NOC for the user device.
- the configurator can initiate a CSR request to configure the NOC for the user equipment.
- Method 2 Determine whether to configure the second device according to the identifier of the RCAC of the second device.
- the first device may determine the identification of the RCAC. For example, the first device may read the identification of the RCAC from the RCAC of the second device.
- the identification of the RCAC may include at least one of the following: the subject of the RCAC (subject field), the public key of the RCAC and the subject key identifier (subject key identifier) of the RCAC.
- the first device may look up the identification of the RCAC in the certificate center.
- the certificate center may include a first syntax, and the first syntax may include a field for recording the identification of the RCAC.
- the certificate center may include a database corresponding to the first syntax, and the identification of the RCAC of each ecological manufacturer may be stored in the field for recording the identification of the RCAC in the database.
- the RCACSubject field may be added to the vendor syntax of DCL, as shown in Table 4 below.
- an RCACPubKey field may also be added to the manufacturer syntax of DCL, as shown in Table 5 below.
- the RCACSubjectKeyID field can be added to the vendor syntax of the DCL, as shown in Table 6 below.
- the first device may search for the identifier of RCAC in the manufacturer's grammar (or in a database corresponding to the grammar).
- the first device can determine that the second device is bound to an illegal ecological platform.
- the first device may output third information, and the third information may be used to ask the user whether to continue to configure the second device. Further, if the user instructs to continue to configure the second device, the first device may trigger the configuration process of the second device.
- the first device may trigger the configuration process of the second device.
- the first device may further verify the RCAC of the second device through a manufacturer identifier corresponding to the identifier of the RCAC in the certificate center.
- the first device can search for the manufacturer identifier corresponding to the RCAC identifier in the certificate center; the first device can obtain the manufacturer identifier of the second device; further, the first device can compare the manufacturer identifier of the second device with the manufacturer identifier corresponding to the RCAC identifier (found in the certificate center), and verify the RCAC of the second device (or verify the manufacturer identifier corresponding to the RCAC identifier of the second device) based on the comparison result.
- the certificate center may include a second syntax, and the second syntax may include a field for recording the RCAC identifier and a field for recording the manufacturer identifier.
- the certificate center may include a database corresponding to the second syntax, and the database may be defined based on the data structure of the second syntax.
- the identifier of the RCAC of each ecological manufacturer may be stored in the field for recording the RCAC identifier in the database, and the manufacturer identifier corresponding to the identifier of the RCAC of each ecological manufacturer may be stored in the field for recording the manufacturer identifier in the database.
- the vendor identifier corresponding to the RCAC identifier may be stored in a field for recording the vendor identifier (such as the VendorID field) in Tables 4 to 6.
- the first device may search for the vendor identifier corresponding to the RCAC identifier in the RCAC syntax (or in a database corresponding to the syntax).
- the first device may determine that the second device is bound to an illegal ecological platform.
- the first device may also output fourth information, and the fourth information may be used to inquire the user whether to continue to configure the second device. Further, when the user instructs to continue to configure the second device, the first device may trigger the configuration process of the second device.
- the first device can trigger the configuration process of the second device. For example, the first device can initiate a certificate signing request (CSR) request to configure a node operational certificate (NOC) for the second device.
- CSR certificate signing request
- NOC node operational certificate
- the method 600 includes steps S601 to S612 , which are specifically as follows:
- the configurator discovers a user equipment and establishes a PASE connection with the user equipment.
- S602 The configurator configures basic information of the user equipment.
- the time of the user device For example, the time of the user device, the area where the user device is located, etc.
- S603 The configurator authenticates the legitimacy of the user equipment.
- the configurator determines whether the current configuration is a secondary network configuration.
- the configurator can determine whether the user equipment has been configured with Fabric, and if so, determine that the current configuration is a secondary network configuration.
- S605 The configurator obtains the RCAC of the user equipment.
- the configurator can read the RCAC that has been configured on the user device.
- S606 The configurator obtains the identifier of the RCAC.
- the configurator may extract the identity of the RCAC from the RCAC.
- the configurator searches for the identifier of RCAC in the DCL.
- the configurator may connect to the DCL and search the DCL for the identifier of the RCAC obtained from the user device.
- S608 The configurator does not find the identifier of the RCAC in the DCL.
- the configurator may prompt the user that the user device may be bound to an illegal ecological platform and ask the user whether to continue configuring the user device.
- the configurator can initiate a CSR request to configure the NOC for the user device.
- the configurator finds the identifier of the RCAC in the DCL and then executes S609.
- S609 The configurator obtains the manufacturer identification (VID) of the user equipment.
- VIP manufacturer identification
- the configurator searches the DCL for the manufacturer ID corresponding to the RCAC.
- the configurator compares the VID of the user equipment with the manufacturer ID corresponding to the RCAC (found in the DCL) to see if they are consistent.
- the configurator can prompt the user device that it may be bound to an illegal ecological platform and ask the user whether to continue configuring the user device.
- S612 The configurator configures the user equipment.
- the configurator can initiate a CSR request to configure the NOC for the user device.
- the configurator can initiate a CSR request to configure the NOC for the user equipment.
- the first device can verify the root certification center certificate RCAC of the second device through the certificate center, thereby reducing the risk of being attacked during the configuration process and avoiding the problem of sensitive data leakage of the ecological platform.
- Fig. 7 is a schematic structural diagram of an apparatus for configuring a device provided in an embodiment of the present application. As shown in Fig. 7, the apparatus 700 includes a verification unit 710, which is specifically as follows:
- the verification unit 710 is used to verify the root certification center certificate RCAC of the second device through a certificate center, and the certificate center can determine the legitimacy of the RCAC.
- the apparatus 700 further includes a determination unit 720, configured to determine whether the current configuration is a secondary network distribution; wherein the verification unit 710 is specifically configured to verify the RCAC of the second device through the certificate center when the current configuration is a secondary network distribution.
- the verification unit 710 is specifically configured to: verify the RCAC of the second device through the RCAC stored in the certificate center.
- the verification unit 710 is specifically used to: search for the RCAC in the certificate center; if the certificate center does not include the RCAC, determine that the second device is bound to an illegal ecological platform.
- the verification unit 710 is also used to: if the certificate center does not include the RCAC, output first information, and the first information is used to ask the user whether to continue configuring the second device; the device 700 also includes a trigger unit 730, which is used to: trigger the configuration process of the second device when the user instructs to continue configuring the second device.
- the apparatus 700 further includes a trigger unit 730, configured to trigger a configuration process of the second device if the certificate center includes the RCAC.
- a trigger unit 730 configured to trigger a configuration process of the second device if the certificate center includes the RCAC.
- the verification unit 710 is further configured to: if the certificate center includes the RCAC, verify the RCAC of the second device through a manufacturer identifier corresponding to the RCAC in the certificate center.
- the verification unit 710 is specifically used to: search for the manufacturer identifier of the RCAC in the certificate center; if the certificate center includes the RCAC, and the manufacturer identifier of the second device is inconsistent with the manufacturer identifier corresponding to the RCAC in the certificate center, it is determined that the second device is bound to an illegal ecological platform.
- the device 700 also includes an output unit 740, which is used to: if the certificate center includes the RCAC, and the manufacturer identifier of the second device is inconsistent with the manufacturer identifier corresponding to the RCAC in the certificate center, then output second information, and the second information is used to ask the user whether to continue configuring the second device; the device 700 also includes a trigger unit 730, which is used to: trigger the configuration process of the second device when the user instructs to continue configuring the second device.
- an output unit 740 which is used to: if the certificate center includes the RCAC, and the manufacturer identifier of the second device is inconsistent with the manufacturer identifier corresponding to the RCAC in the certificate center, then output second information, and the second information is used to ask the user whether to continue configuring the second device
- the device 700 also includes a trigger unit 730, which is used to: trigger the configuration process of the second device when the user instructs to continue configuring the second device.
- the apparatus 700 further includes a trigger unit 730, configured to trigger a configuration process of the second device if the certificate center includes the RCAC and the manufacturer identifier of the second device is consistent with the manufacturer identifier corresponding to the RCAC.
- a trigger unit 730 configured to trigger a configuration process of the second device if the certificate center includes the RCAC and the manufacturer identifier of the second device is consistent with the manufacturer identifier corresponding to the RCAC.
- the verification unit 710 is specifically configured to: verify the RCAC of the second device through an identifier of the RCAC stored in the certificate center.
- the verification unit 710 is specifically used to: search for the identifier of the RCAC in the certificate center; if the certificate center does not include the identifier of the RCAC, determine that the second device is bound to an illegal ecological platform.
- the device 700 also includes an output unit 740, which is used to: if the certificate center does not include the RCAC identifier, output third information, and the third information is used to ask the user whether to continue configuring the second device; the device 700 also includes a trigger unit 730, which is used to: trigger the configuration process of the second device when the user instructs to continue configuring the second device.
- an output unit 740 which is used to: if the certificate center does not include the RCAC identifier, output third information, and the third information is used to ask the user whether to continue configuring the second device
- the device 700 also includes a trigger unit 730, which is used to: trigger the configuration process of the second device when the user instructs to continue configuring the second device.
- the apparatus 700 further includes a trigger unit 730, configured to trigger a configuration process of the second device if the certificate center includes an identifier of the RCAC.
- a trigger unit 730 configured to trigger a configuration process of the second device if the certificate center includes an identifier of the RCAC.
- the verification unit 710 is further configured to: if the certificate center includes the identifier of the RCAC, verify the RCAC of the second device through a manufacturer identifier corresponding to the identifier of the RCAC in the certificate center.
- the verification unit 710 is specifically used to: search for the manufacturer identifier corresponding to the RCAC identifier in the certificate center; if the certificate center includes the RCAC identifier, and the manufacturer identifier of the second device is inconsistent with the manufacturer identifier corresponding to the RCAC identifier, it is determined that the second device is bound to an illegal ecological platform.
- the device 700 also includes an output unit 740, which is used to: if the certificate center includes the identifier of the RCAC, and the manufacturer identifier of the second device is inconsistent with the manufacturer identifier corresponding to the identifier of the RCAC, then output fourth information, and the fourth information is used to ask the user whether to continue configuring the second device; the device 700 also includes a trigger unit 730, which is used to: trigger the configuration process of the second device when the user instructs to continue configuring the second device.
- an output unit 740 which is used to: if the certificate center includes the identifier of the RCAC, and the manufacturer identifier of the second device is inconsistent with the manufacturer identifier corresponding to the identifier of the RCAC, then output fourth information, and the fourth information is used to ask the user whether to continue configuring the second device
- the device 700 also includes a trigger unit 730, which is used to: trigger the configuration process of the second device when the user instructs to continue configuring the second device.
- the apparatus 700 further includes a trigger unit 730, configured to trigger a configuration process of the second device if the certificate center includes an identifier of the RCAC and the manufacturer identifier of the second device is consistent with the manufacturer identifier corresponding to the identifier of the RCAC.
- a trigger unit 730 configured to trigger a configuration process of the second device if the certificate center includes an identifier of the RCAC and the manufacturer identifier of the second device is consistent with the manufacturer identifier corresponding to the identifier of the RCAC.
- the certificate center includes a first grammar
- the first grammar includes a field for recording an identifier of the RCAC
- the verification unit 710 is specifically used to: search for the identifier of the RCAC in the first grammar.
- the certificate center includes a second grammar, which includes a field for recording the RCAC identifier and a field for recording the manufacturer identifier; the verification unit 710 is specifically used to: search for the manufacturer identifier corresponding to the RCAC in the second grammar.
- the identification of the RCAC includes at least one of the following: the subject of the RCAC, the public key of the RCAC and the subject key identification of the RCAC.
- the device 700 also includes a sending unit 750, which is used to: send fifth information to the second device, and the fifth information is used to request the weaving network identification of the second device; the determination unit 720 is specifically used to: if the device receives the sixth information sent by the second device, determine that the current configuration is the secondary network distribution; if the device does not receive the sixth information sent by the second device, determine that the current configuration is the first network distribution; wherein the sixth information is used to indicate the weaving network identification.
- a sending unit 750 which is used to: send fifth information to the second device, and the fifth information is used to request the weaving network identification of the second device
- the determination unit 720 is specifically used to: if the device receives the sixth information sent by the second device, determine that the current configuration is the secondary network distribution; if the device does not receive the sixth information sent by the second device, determine that the current configuration is the first network distribution; wherein the sixth information is used to indicate the weaving network identification.
- the sixth information includes identification information, which is obtained by signing with a first private key.
- the verification unit 710 is also used to: verify the identification information using a first public key to obtain the weaving network identification in the identification information, and the first public key corresponds to the first private key.
- the device 700 also includes a sending unit 750 and a receiving unit 760, the sending unit 750 is used to: send seventh information to the second device, the seventh information is used to request the first attribute value of the second device; the receiving unit 760 is used to: receive eighth information sent by the second device, the eighth information is used to indicate the first attribute value; the determination unit is specifically used to: if the first attribute value is a non-zero value, determine that the current configuration is a secondary network configuration; if the first attribute value is zero, determine that the current configuration is a first network configuration.
- the eighth information includes attribute information, and the attribute information is obtained by signing with a second private key.
- the verification unit 710 is also used to: verify the attribute information using a second public key to obtain the first attribute value in the attribute information, and the second public key corresponds to the second private key.
- the device 700 also includes a sending unit 750 and a receiving unit 760, the sending unit 750 is used to: send ninth information to the second device, the ninth information is used to request RCAC of the second device; the receiving unit 760 is used to: receive tenth information sent by the second device, the tenth information is used to indicate the RCAC.
- the tenth information includes RCAC information
- the RCAC information is obtained by signing a third private key.
- the verification unit 710 is also used to: use a third public key to verify the RCAC information to determine that the RCAC information includes the RCAC, and the third public key corresponds to the third private key.
- the certificate center includes a third grammar
- the third grammar includes a manufacturer grammar and/or a grammar constructed for recording RCAC
- the third grammar includes a field for recording RCAC
- the verification unit 710 is specifically used to: search for the RCAC in the third grammar.
- the certificate center includes a fourth grammar
- the fourth grammar includes a manufacturer grammar and/or a grammar constructed for recording RCAC
- the fourth grammar includes a field for recording RCAC and a field for recording a manufacturer identifier
- the verification unit 710 is specifically used to: search for the manufacturer identifier corresponding to the RCAC in the fourth grammar.
- FIG8 is a schematic structural diagram of an apparatus for configuring a device according to an embodiment of the present application.
- the apparatus 800 for configuring a device in FIG8 includes a receiving unit 810 and a sending unit 820, which are specifically as follows:
- a receiving unit 810 is configured to receive ninth information sent by the first device, wherein the ninth information is used to request a root certification center certificate RCAC of the apparatus;
- the sending unit 820 is configured to send tenth information to the first device, where the tenth information is used to indicate the RCAC.
- the tenth information includes RCAC information
- the device 800 further includes a signing unit 830, which is used to: use a third private key to sign the RCAC to obtain the RCAC information.
- the receiving unit 810 is also used to: receive fifth information sent by the first device, and the fifth information is used to request the weaving network identifier of the device; the sending unit 820 is also used to: if the device has been configured with a weaving network, send sixth information to the first device, and the sixth information is used to indicate the weaving network identifier.
- the sixth information includes identification information
- the device 800 further includes a signing unit 830, which is used to: use the first private key to sign the weaving network identification to obtain the identification information.
- the receiving unit 810 is further used to: receive seventh information sent by the first device, the seventh information is used to request a first attribute value of the apparatus; the sending unit 820 is further used to: send eighth information to the first device, the eighth information is used to indicate the first attribute value.
- the eighth information includes attribute information
- the device 800 further includes a signing unit 830, which is used to: use a second private key to sign the first attribute value to obtain the attribute information.
- FIG9 is a schematic structural diagram of a device provided in an embodiment of the present application.
- the dotted lines in FIG9 indicate that the unit or module is optional.
- the device 900 can be used to implement the method described in the above method embodiment.
- the device 900 can be a chip or a device configuring a device.
- the device 900 may include one or more processors 910.
- the processor 910 may support the device 900 to implement the method described in the above method embodiment.
- the processor 910 may be a general-purpose processor or a special-purpose processor.
- the processor may be a central processing unit (CPU).
- the processor may also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc.
- DSP digital signal processor
- ASIC application specific integrated circuits
- FPGA field programmable gate arrays
- a general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.
- the device 900 may further include one or more memories 920.
- the memory 920 stores a program, which can be executed by the processor 910, so that the processor 910 executes the method described in the above method embodiment.
- the memory 920 may be independent of the processor 910 or integrated in the processor 910.
- the apparatus 900 may further include a transceiver 930.
- the processor 910 may communicate with other devices or chips through the transceiver 930.
- the processor 910 may transmit and receive data with other devices or chips through the transceiver 930.
- the present application also provides a computer-readable storage medium for storing a program.
- the computer-readable storage medium can be applied to the apparatus for configuring the device provided in the present application, and the program enables the computer to execute the method performed by the apparatus for configuring the device in each embodiment of the present application.
- the present application also provides a computer program product.
- the computer program product includes a program.
- the computer program product can be applied to the device for configuring the device provided in the present application, and the program enables the computer to execute the method performed by the device for configuring the device in each embodiment of the present application.
- the embodiment of the present application also provides a computer program.
- the computer program can be applied to the device for configuring a device provided in the embodiment of the present application, and the computer program enables a computer to execute the method executed by the device for configuring a device in each embodiment of the present application.
- B corresponding to A means that B is associated with A, and B can be determined according to A.
- determining B according to A does not mean determining B only according to A, and B can also be determined according to A and/or other information.
- the size of the serial numbers of the above-mentioned processes does not mean the order of execution.
- the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
- the disclosed systems, devices and methods can be implemented in other ways.
- the device embodiments described above are only schematic.
- 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.
- 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.
- each functional unit in each embodiment of the present application 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.
- the computer program product includes one or more computer instructions.
- the computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
- the computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
- the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center.
- the computer-readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated.
- the available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a digital video disc (DVD)), or a semiconductor medium (e.g., a solid state disk (SSD)), etc.
- a magnetic medium e.g., a floppy disk, a hard disk, a magnetic tape
- an optical medium e.g., a digital video disc (DVD)
- DVD digital video disc
- SSD solid state disk
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Telephonic Communication Services (AREA)
Abstract
提供了一种配置设备的方法及装置, 该方法包括: 第一设备通过证书中心验证第二设备的根认证中心证书RCAC, 所述证书中心能够确定所述RCAC的合法性. 本申请实施例中的方法, 能够提高网络配置过程中的安全性.
Description
本申请涉及通信技术领域,并且更为具体地,涉及一种配置设备的方法及装置。
随着编织网络(fabric)的广泛应用,用户对编织网络的功能需求越来越高,因此,如何完善编织网络的功能,以提高用户体验,成为一个亟需解决的技术问题。
发明内容
本申请提供一种配置设备的方法及装置。下面对本申请实施例涉及的各个方面进行介绍。
第一方面,提供了一种配置设备的方法,包括:第一设备通过证书中心验证第二设备的根认证中心证书RCAC,所述证书中心能够确定所述RCAC的合法性。
第二方面,提供了一种配置设备的方法,包括:第二设备接收第一设备发送的第九信息,所述第九信息用于请求所述第二设备的根认证中心证书RCAC;所述第二设备向所述第一设备发送第十信息,所述第十信息用于指示所述RCAC。
第三方面,提供了一种配置设备的装置,包括:验证单元,用于通过证书中心验证第二设备的根认证中心证书RCAC,所述证书中心能够确定所述RCAC的合法性。
第四方面,提供了一种配置设备的装置,包括:接收单元,用于接收第一设备发送的第九信息,所述第九信息用于请求所述装置的根认证中心证书RCAC;发送单元,用于向所述第一设备发送第十信息,所述第十信息用于指示所述RCAC。
第五方面,提供一种配置设备的装置,包括存储器和处理器,所述存储器用于存储程序,所述处理器用于调用所述存储器中的程序,以执行如第一方面所述的方法。
第六方面,提供一种配置设备的装置,包括存储器和处理器,所述存储器用于存储程序,所述处理器用于调用所述存储器中的程序,以执行第二方面所述的方法。
第七方面,提供一种配置设备的装置,包括处理器,用于从存储器中调用程序,以执行第一方面所述的方法。
第八方面,提供一种配置设备的装置,包括处理器,用于从存储器中调用程序,以执行第二方面所述的方法。
第九方面,提供一种芯片,包括处理器,用于从存储器调用程序,使得安装有所述芯片的设备执行第一方面所述的方法。
第十方面,提供一种芯片,包括处理器,用于从存储器调用程序,使得安装有所述芯片的设备执行第二方面所述的方法。
第十一方面,提供一种计算机可读存储介质,其上存储有程序,所述程序使得计算机执行第一方面所述的方法。
第十二方面,提供一种计算机可读存储介质,其上存储有程序,所述程序使得计算机执行第二方面所述的方法。
第十三方面,提供一种计算机程序产品,包括程序,所述程序使得计算机执行第一方面所述的方法。
第十四方面,提供一种计算机程序产品,包括程序,所述程序使得计算机执行第二方面所述的方法。
第十五方面,提供一种计算机程序,所述计算机程序使得计算机执行第一方面所述的方法。
第十六方面,提供一种计算机程序,所述计算机程序使得计算机执行第二方面所述的方法。
在本申请实施例中,第一设备通过证书中心能够验证第二设备的根认证中心证书RCAC,从而能够降低配置过程中被攻击的风险,避免出现生态平台敏感数据泄露的问题。
图1是本申请实施例的一个应用场景的示例图。
图2是本申请实施例中配置设备的方法的示意性流程图。。
图3是本申请一个实施例提供的配置设备的方法的示意性流程图。
图4是本申请另一个实施例提供的配置设备的方法的示意性流程图。
图5是本申请又一个实施例提供的配置设备的方法的示意性流程图。
图6是本申请又一个实施例提供的配置设备的方法的示意性流程图。
图7是本申请一个实施例提供的配置设备的装置的示意性结构图。
图8是本申请另一实施例提供的配置设备的装置的示意性结构图。
图9是本申请一实施例提供的装置的示意性结构图。
下面将结合附图,对本申请中的技术方案进行描述。
图1是本申请实施例的一个应用场景100的示例图。该应用场景100可以包括网络110,终端设备112及终端设备130位于网络110(的覆盖范围)中。终端设备112可以与终端设备130进行数据传输。终端设备112可以为网络110的管理设备,终端设备112可以将终端设备130配置到网络110中(即与网络110建立连接)。
可选地,在将终端设备130配置到网络110中之后,还可以继续将终端设备130配置到其他网络中。例如,该应用场景100还可以包括网络120,终端设备122及终端设备130位于网络120(的覆盖范围内)中,可以看出,终端设备130可以同时位于网络110及网络120中。终端设备122可以与终端设备130进行数据传输。终端设备122可以为网络120的管理设备,终端设备122可以将终端设备130配置到网络120中(即与网络120建立连接)。
网络110与网络120可以为其覆盖范围内的终端设备提供服务,例如,与其覆盖范围内的终端设备建立网络连接、使其覆盖范围内的多个终端设备之间进行数据传输等。网络110与网络120可以为编织网络(fabric)。网络110与网络120可以称为生态网络或生态平台。
图1示例性地示出了两个网络和三个终端设备,可选地,该应用场景100可以包括更多或更少的网络或终端设备,本申请实施例对此不做限定。应理解,本申请实施例并不限于图1所示的***架构,本申请实施例的技术方案可以应用于各种***架构,本申请实施例中对此并不限定。
本申请实施例中的终端设备112或终端设备122也可以称为管理设备、用户设备等。可选地,终端设备112可以为网络110中具有管理员权限的设备(即管理设备),终端设备122也可以为网络120中具有管理员权限的设备。终端设备112或终端设备122可以是手机(mobile phone)、平板电脑(Pad)、笔记本电脑、掌上电脑、可穿戴设备等。
本申请实施例中的终端设备130也可以称为节点(node)设备、用户设备等。终端设备130可以是照明,门锁、百叶窗、电视、暖通和空调***、安全传感器和控制器、网关等设备。终端设备130可以与网络110、网络120建立连接,并与网络110中的终端设备112及网络120中的终端设备122进行数据传输。
在图1中,若终端设备112将终端设备130配置到网络110之前,终端设备130没有与任何网络建立连接,那么终端设备112将终端设备130配置到网络110的过程可以称为首次配网;终端设备122将终端设备130配置到网络120中时,终端设备130已经与网络110建立连接,那么终端设备122将终端设备130配置到网络120的过程可以称为二次配网。需要说明的是,二次配网并非特指第二次配网,除首次配网之外的所有非首次配网均可以称为二次配网。下面结合图2,对二次配网的过程进行描述。
在图2中,管理设备A为生态网络A中的配置器,具有生态网络A中的管理员权限,管理设备B为生态网络B中的配置器,具有生态网络B中的管理员权限,用户设备已与生态网络A建立连接。生态网络A与生态网络B可以对应不同的生态厂商,例如,生态网络A可以对应谷歌(Google)的生态A,生态网络B可以对应小米的生态B。
如图2所示,方法200可以包括下述步骤:
S201,用户开启用户设备的配置模式。
例如,用户可以向管理设备A输入操作指令,以开启管理设备A中的相关应用程序(APP),并使该APP进行(用户设备的)配置模式。
S202,管理设备A产生配置令牌OT。
例如,管理设备A中的APP可以产生配置令牌(Onboarding Token,OT)。在方法200的后续步骤中,管理设备A执行的动作均可以是管理设备A的APP执行的。
S203,管理设备A向用户设备发送开启配置的指令。
该指令可以携带S202中产生的配置令牌。
S204,用户设备进入配置发现模式。
S205,用户设备向管理设备A发送响应消息。
S206,管理设备A向管理设备B发送配置令牌。
例如,管理设备A可以通过邮件、语音等方式将S202中产生的配置令牌发送给管理设备B。
S207,管理设备B发现用户设备。
S208,管理设备B使用配置令牌与用户设备建立安全连接。
该安全连接可以为基于密钥认证的安全会话建立(password authenticated session establishment,PASE)连接。
S209,管理设备B认证用户设备的认证声明(certification declaration,CD)。
S210,管理设备B为生态网络B创建标识。
例如,若生态网络B未在家庭网络中使用过,则管理设备B为生态网络B创建网络标识(fabricID)。
S211,用户设备向管理设备B发送证书签名请求(certificate signing request,CSR)。
例如,用户设备可以为台灯(bulb),用户设备可以向管理设备B发送证书请求CSR.bulb。
S212,管理设备B向认证中心(certificate authority,CA)发送网络标识及CSR。
CA可以指生态网络B对应的认证中心(或证书颁发中心)。管理设备B可以将CSR.bulb和fabricID发送到CA请求设备证书。
S213,CA向管理设备B发送设备证书。
该设备证书可以指生态网络B对应的设备证书。CA可以向管理设备B发送B.OC.bulb(设备证书)。
S214,管理设备B配置用户设备。
管理设备B可以将设备证书B.OC.bulb和访问控制权限ACL.Bulb.B.APP1配置到用户设备(bulb)。
在上述方法200中,生态网络B对应的设备证书可以是基于生态网络B对应的生态厂商的根认证中心证书(root certificate authority certificate,RCAC)确定的。RCAC可以包括多种格式。
例如,在X.509标准中RCAC的格式可以如下:
再例如,RCAC的Matter TLV格式可以如下:
从上述图2中的配网过程可以看出,生态A(中的管理设备A)掌握用户设备的配网密码(如配置令牌等)并分享给生态B中的管理设备B,当管理设备B与用户设备建立PASE连接时,A生态(中的管理设备A)可以发起中间人攻击从而窃听管理设备B与用户设备之间的通信,获取生态B的秘密数据。例如,管理设备A可以创建虚拟的中间设备,并修改其向管理设备B发送的配网密码及相关数据,以使得管理设备B与中间设备(而非用户设备)建立连接,进一步地,还可以在中间设备与用户设备之间建立连接,这样种管理设备A就可以窃听管理设备B与用户设备之间的通信,获取生态B的秘密数据。因此,现有的二次配网过程存在被攻击的风险,可能会出现生态平台敏感数据泄露的问题。
为了解决上述技术问题中的一个或多个,本申请提出一种配置设备的方法及装置,能够提高网络配置过程中的安全性。下面结合图3至图6对本申请实施例进行详细说明。
图3是本申请实施例的配置设备的方法的一个示意性流程图。图3所示的方法300可以包括步骤S310,具体如下:
S310,第一设备通过证书中心验证第二设备的RCAC。
第一设备可以为网络(如生态B)中的管理设备(如配置器(commissioner))。第二设备可以为用户设备。
证书中心能够确定所述RCAC的合法性。可选地,证书中心可以为区块链、云端、认证中心(如图2中的认证中心)或其他服务器,例如,证书中心可以为分布式合规记账本(distributed compliance ledger,DCL)。各生态厂商的RCAC可以存放在共同的证书中心中。证书中心可以采取安全措施以使得其存放的RCAC只能被查询,无法被篡改。后续实施例中,会结合表1至表6对RCAC在证书中心中的存储方式进行说明。
在一些实施例中,在步骤S310之前,方法300还可以包括步骤S320,具体如下:
S320,第一设备确定当前配置是否为二次配网。
可选地,在当前配置为二次配网的情况下,第一设备可以执行上述步骤S310。在上述步骤S310中验证第二设备的RCAC合法的情况下,对第二设备进行二次配网,这样可以能够降低配置过程中被攻击的风险,能够提高网络配置过程中的安全性。
例如,第一设备可以确定当前配置是否为二次配网;在当前配置为二次配网的情况下,第一设备可以通过证书中心验证第二设备的RCAC。
在本申请中,可以通过多种方法确定当前配置是否为二次配网,具体如下:
方法一,根据第二设备是否已配置编织网络确定当前配置是否为二次配网。
例如,第一设备可以向第二设备发送第五信息,第五信息可以用于请求第二设备的编织网络标识;若第二设备已配置编织网络,则第二设备可以向第一设备发送第六信息,若第二设备未配置编织网络,则第二设备可以不向第一设备发送第六信息;相应地,若第一设备接收到第二设备发送的第六信息,则第一设备可以确定当前配置为二次配网,若第一设备未接收到第二设备发送的第六信息,则第一设备可以确定当前配置为首次配网;其中,第六信息可以用于指示编织网络标识。
或者,在接收到第五信息的情况下,无论是否配置编织网络,第二设备可以均向第一设备发送第六信息,此时,第二设备可以通过第六信息指示不同的返回值来表示其是否已配置编织网络。
在发送第六信息之前,第二设备可以使用第一私钥对第六信息携带的编织网络标识(或返回值)进行签名,得到标识信息。相应地,在第一设备接收到第六信息之后,第一设备可以使用第一公钥对标识信息进行验证,以获取标识信息中的编织网络标识。其中,第一公钥可以与第一私钥对应。
方法二,根据第二设备的第一属性值确定当前配置是否为二次配网。
例如,第一设备可以向第二设备发送第七信息,第七信息可以用于请求第二设备的第一属性值;在接收到第七信息之后,第二设备可以向第一设备发送第八信息,第八信息可以用于指示第一属性值。第一设备可以根据第一属性值的取值确定是否为二次配网。例如,若第一属性值为非零值,则第一设备可以确定当前配置为二次配网;若第一属性值为零,则第一设备可以确定当前配置为首次配网。
在发送第八信息之前,第二设备可以使用第二私钥对第一属性值进行签名,得到属性信息。相应地,在第一设备接收到第八信息之后,第一设备可以使用第二公钥对属性信息进行验证,以获取属性信息中的第一属性值。其中,第二公钥可以与第二私钥对应。
在步骤S310之前,第一设备可以获取第二设备的RCAC。例如,在步骤S310之前,方法300还可以包括步骤S330及S340,具体如下:
S330,第一设备向第二设备发送第九信息。
其中,第九信息可以用于请求第二设备的RCAC。
S340,第二设备向第一设备发送第十信息。
其中,第十信息可以用于指示第二设备的RCAC。
在S340之前,第二设备还可以使用第三私钥对RCAC进行签名,得到RCAC信息。此时,第十信息可以包括RCAC信息。
相应地,在接收到第十信息之后,第一设备可以使用第三公钥对RCAC信息进行验证,以确定RCAC信息包括RCAC。其中,第三公钥可以与第三私钥对应。
在获取第二设备的RCAC之后,第一设备就可以通过证书中心验证第二设备的RCAC。例如,第一设备可以通过证书中心中存储的RCAC验证所述第二设备的RCAC。
在本申请实施例中,第一设备可以通过多种方法验证第二设备的RCAC,具体如下:
方法一:根据第二设备的RCAC确定是否配置第二设备。
第一设备可以在证书中心中查找RCAC。
证书中心可以包括第三语法,第三语法可以包括厂商语法和/或用于记录RCAC而构建的语法,第三语法可以包括用于记录RCAC的字段。也就是说,证书中心可以包括第三语法对应的数据库,该数据库可以是基于第三语法的数据结构定义的,各生态厂商的的RCAC可以存储于数据库中的用于记录RCAC的字段。
例如,可以在DCL中增加RCAC语法(schema),RCAC语法用于存储生态厂商的根CA证书。RCAC语法的结构可以如下述表1所示。
表1 RCAC语法的结构
Name | Type | Constraint | Conformance | Mutable |
TrustRootCertificate | string | all | M | No |
或者,也可以在DCL的厂商(vendor)语法中增加TrustRootCertificate字段。厂商语法及加 TrustRootCertificate字段可以如下述表2所示。
表2 厂商语法的结构
Name | Type | Constraint | Conformance | Mutable |
VendorID | vendor-id | all | M | No |
VendorName | string | max 128 | M | Yes |
CompanyLegalName | string | max 256 | M | Yes |
CompanyPreferredName | string | max 256 | O | Yes |
VendorLandingPageUrl | string | max 256 | O | Yes |
TrustRootCertificate | string | all | O | Yes |
例如,如上述表1及表2所示,第一设备可以在RCAC语法或厂商语法中(或者说在语法对应的数据库中)查找第二设备的RCAC。
若证书中心不包括RCAC,则第一设备可以确定第二设备被非法生态平台绑定。
可选地,若证书中心不包括RCAC,则第一设备可以输出第一信息,第一信息可以用于询问用户是否继续配置第二设备。进一步地,在用户指示继续配置第二设备的情况下,第一设备可以触发第二设备的配置流程。
若证书中心包括RCAC,则第一设备可以触发第二设备的配置流程。
下面结合图4对上述实施例进行详细说明,如图4所示,方法400包括步骤S401至S408,具体如下:
S401,配置器发现用户设备并与用户设备建立PASE连接。
S402,配置器配置用户设备的基本信息。
例如,用户设备的时间、用户设备所在区域等。
S403,配置器认证用户设备的合法性。
上述S401至S403可以参照现有技术,这里不再赘述。
S404,配置器确定当前配置是否为二次配网。
配置器可以确定用户设备是否已配置Fabric,若已配置,则确定当前配置为二次配网。
S405,配置器获取用户设备的RCAC。
配置器可以读取用户设备已配置的RCAC。
S406,配置器在DCL中查找RCAC。
配置器可以连接DCL,并在DCL中查找从用户设备处获取的RCAC。
S407,配置器在DCL中未找到该RCAC。
若未在DCL中找到该RCAC,则配置器可以向用户提示该用户设备可能被非法生态平台绑定,并询问用户是否继续配置该用户设备。
S408,配置器配置该用户设备。
若用户同意继续配置,则配置器可以发起CSR请求,为用户设备配置NOC。
或者,配置器在DCL中找到该RCAC,则配置器可以发起CSR请求,为用户设备配置NOC。
在一些实施例中,若证书中心包括RCAC,则第一设备可以进一步通过证书中心中RCAC对应的厂商标识验证第二设备的RCAC。
例如,若证书中心包括RCAC,则第一设备可以在证书中心中查找RCAC对应的厂商标识;第一设备也可以获取第二设备的厂商标识;进一步地,第一设备可以将第二设备的厂商标识(即第二设备的RCAC对应的厂商标识)与(证书中心中查找到的)RCAC对应的厂商标识进行比较,并根据比较结果验证第二设备的RCAC(或者说验证第二设备的RCAC对应的厂商标识)。
证书中心可以包括第四语法,所述第四语法包括厂商语法和/或用于记录RCAC而构建的语法,所述第四语法包括用于记录RCAC的字段及用于记录厂商标识的字段。也就是说,证书中心可以包括第四语法对应的数据库,该数据库可以是基于第四语法的数据结构定义的,第二设备的RCAC可以存储于数据库中的用于记录RCAC的字段,各生态厂商的RCAC对应的厂商标识可以存储于数据库中的用于记录厂商标识的字段。
例如,可以在上述表1中的RCAC语法中增加用于存储RCAC对应的厂商标识的字段(如VendorID字段)。修改后的RCAC语法的结构可以如下述表3所示。
表3 RCAC语法的结构
Name | Type | Constraint | Conformance | Mutable |
VendorID | vendor-id | all | M | No |
TrustRootCertificate | string | all | M | No |
例如,如上述表3所示,第一设备可以在RCAC语法(或者说在语法对应的数据库中)查找RCAC对应的厂商标识。或者,如上述表2所示,第一设备可以在厂商语法中(或者说在语法对应的数据库中)查找RCAC对应的厂商标识(如VendorID字段)。
可选地,若第二设备的厂商标识与证书中心中该RCAC对应的厂商标识不一致,则第一设备可以确定第二设备被非法生态平台绑定。
进一步地,若第二设备的厂商标识与证书中心中该RCAC对应的厂商标识不一致,则第一设备还可以输出第二信息,第二信息可以用于询问用户是否继续配置第二设备。进一步地,在用户指示继续配置第二设备的情况下,第一设备可以触发第二设备的配置流程。
若第二设备的厂商标识与RCAC对应的厂商标识一致,则第一设备可以触发第二设备的配置流程。例如,第一设备可以发起证书签名请求(certificate signing request,CSR)请求,为第二设备配置节点操作证书(node operational certificate,NOC)。
下面结合图5对上述实施例进行详细说明,如图5所示,方法500包括步骤S501至S511,具体如下:
S501,配置器发现用户设备并与用户设备建立PASE连接。
S502,配置器配置用户设备的基本信息。
例如,用户设备的时间、用户设备所在区域等。
S503,配置器认证用户设备的合法性。
上述S501至S503可以参照现有技术,这里不再赘述。
S504,配置器确定当前配置是否为二次配网。
配置器可以确定用户设备是否已配置Fabric,若已配置,则确定当前配置为二次配网。
S505,配置器获取用户设备的RCAC。
配置器可以读取用户设备已配置的RCAC。
S506,配置器在DCL中查找RCAC。
配置器可以连接DCL,并在DCL中查找从用户设备处获取的RCAC。
S507,配置器在DCL中未找到该RCAC。
若未在DCL中找到该RCAC,则配置器可以向用户提示该用户设备可能被非法生态平台绑定,并询问用户是否继续配置该用户设备。
若用户同意继续配置,则配置器可以发起CSR请求,为用户设备配置NOC。
或者,配置器在DCL中找到该RCAC,则可以执行S508。
S508,配置器获取用户设备的厂商标识(VID)。
S509,配置器在DCL中查找RCAC对应的厂商标识。
S510,配置器比较用户设备的VID与(在DCL中查找到的)该RCAC对应的厂商标识是否一致。
若用户设备的VID与(在DCL中查找到的)该RCAC对应的厂商标识不一致,则配置器可以提示用户设备可能被非法生态平台绑定,并询问用户是否继续配置该用户设备。
S511,配置器配置该用户设备。
若用户同意继续配置,则配置器可以发起CSR请求,为用户设备配置NOC。
或者,若用户设备的VID与(在DCL中查找到的)该RCAC对应的厂商标识一致,则配置器可以发起CSR请求,为用户设备配置NOC。
方法二:根据第二设备的RCAC的标识确定是否配置第二设备。
第一设备可以确定RCAC的标识。例如,第一设备可以从第二设备的RCAC中读取RCAC的标识。
可选地,RCAC的标识可以包括以下至少一项:RCAC的主体(subject字段)、RCAC的公钥及RCAC的主体密钥标识(subject key identifier)。
第一设备可以在证书中心中查找RCAC的标识。
证书中心可以包括第一语法,第一语法可以包括用于记录RCAC的标识的字段。也就是说,证书中心可以包括第一语法对应的数据库,各生态厂商的RCAC的标识可以存储于数据库中的用于记录RCAC的标识的字段。
例如,当RCAC的标识为主体字段时,可以在DCL的厂商语法中增加RCACSubject字段。具体可以如下述表4所示。
表4 厂商语法的结构
Name | Type | Constraint | Conformance | Mutable |
VendorID | vendor-id | all | M | No |
VendorName | string | max 128 | M | Yes |
CompanyLegalName | string | max 256 | M | Yes |
CompanyPreferredName | string | max 256 | O | Yes |
VendorLandingPageUrl | string | max 256 | O | Yes |
RCACSubject | string | all | O | Yes |
当RCAC的标识为公钥时,也可以在DCL的厂商语法中增加RCACPubKey字段。具体可以如下述表5所示。
表5 厂商语法的结构
Name | Type | Constraint | Conformance | Mutable |
VendorID | vendor-id | all | M | No |
VendorName | string | max 128 | M | Yes |
CompanyLegalName | string | max 256 | M | Yes |
CompanyPreferredName | string | max 256 | O | Yes |
VendorLandingPageUrl | string | max 256 | O | Yes |
RCACPubKey | string | 65 | O | Yes |
当RCAC的标识为主体密钥标识(subject key identifier)时,可以在DCL的厂商语法中增加RCACSubjectKeyID字段。具体可以如下述表6所示。
表6 厂商语法的结构
Name | Type | Constraint | Conformance | Mutable |
VendorID | vendor-id | all | M | No |
VendorName | string | max 128 | M | Yes |
CompanyLegalName | string | max 256 | M | Yes |
CompanyPreferredName | string | max 256 | O | Yes |
VendorLandingPageUrl | string | max 256 | O | Yes |
RCACSubjectKeyID | string | all | O | Yes |
例如,如上述表4至表6所示,第一设备可以在厂商语法中(或者说在语法对应的数据库中)查找RCAC的标识。
若证书中心不包括RCAC的标识,则第一设备可以确定第二设备被非法生态平台绑定。
进一步地,若证书中心不包括RCAC的标识,则第一设备可以输出第三信息,第三信息可以用于询问用户是否继续配置第二设备。进一步地,在用户指示继续配置第二设备的情况下,第一设备可以触发第二设备的配置流程。
若证书中心包括RCAC的标识,则第一设备可以触发第二设备的配置流程。
在一些实施例中,若证书中心包括RCAC的标识,则第一设备可以进一步通过证书中心中RCAC的标识对应的厂商标识验证第二设备的RCAC。
例如,若证书中心包括RCAC的标识,则第一设备可以在所述证书中心中查找所述RCAC的标识对应的厂商标识;第一设备可以获取第二设备的厂商标识;进一步地,第一设备可以将第二设备的厂商标识与(证书中心中查找到的)RCAC的标识对应的厂商标识进行比较,并根据比较结果验证第二 设备的RCAC(或者说验证第二设备的RCAC的标识对应的厂商标识)。
证书中心可以包括第二语法,第二语法可以包括用于记录RCAC的标识的字段及用于记录厂商标识的字段。也就是说,证书中心可以包括第二语法对应的数据库,该数据库可以是基于第二语法的数据结构定义的,各生态厂商的RCAC的标识可以存储于数据库中的用于记录RCAC的标识的字段,各生态厂商的RCAC的标识对应的厂商标识可以存储于数据库中的用于记录厂商标识的字段。
例如,RCAC的标识对应的厂商标识可以存储于上述表4至表6中的用于记录厂商标识的字段(如VendorID字段)。例如,如上述表4至表6所示,第一设备可以在RCAC语法(或者说在语法对应的数据库中)查找RCAC的标识对应的厂商标识。
可选地,若第二设备的厂商标识与证书中心中RCAC的标识对应的厂商标识不一致,则第一设备可以确定第二设备被非法生态平台绑定。
进一步地,若第二设备的厂商标识与RCAC的标识对应的厂商标识不一致,则第一设备还可以输出第四信息,第四信息可以用于询问用户是否继续配置第二设备。进一步地,在用户指示继续配置第二设备的情况下,第一设备可以触发第二设备的配置流程。
若第二设备的厂商标识与RCAC的标识对应的厂商标识一致,则第一设备可以触发第二设备的配置流程。例如,第一设备可以发起证书签名请求(certificate signing request,CSR)请求,为第二设备配置节点操作证书(node operational certificate,NOC)。
下面结合图6对上述实施例进行详细说明,如图6所示,方法600包括步骤S601至S612,具体如下:
S601,配置器发现用户设备并与用户设备建立PASE连接。
S602,配置器配置用户设备的基本信息。
例如,用户设备的时间、用户设备所在区域等。
S603,配置器认证用户设备的合法性。
上述S601至S603可以参照现有技术,这里不再赘述。
S604,配置器确定当前配置是否为二次配网。
配置器可以确定用户设备是否已配置Fabric,若已配置,则确定当前配置为二次配网。
S605,配置器获取用户设备的RCAC。
配置器可以读取用户设备已配置的RCAC。
S606,配置器获取RCAC的标识。
配置器可以从RCAC中提取RCAC的标识。
S607,配置器在DCL中查找RCAC的标识。
配置器可以连接DCL,并在DCL中查找从用户设备处获取的RCAC的标识。
S608,配置器在DCL中未找到该RCAC的标识。
若未在DCL中找到该RCAC的标识,则配置器可以向用户提示该用户设备可能被非法生态平台绑定,并询问用户是否继续配置该用户设备。
若用户同意继续配置,则配置器可以发起CSR请求,为用户设备配置NOC。
或者,配置器在DCL中找到该RCAC的标识,则可以执行S609。
S609,配置器获取用户设备的厂商标识(VID)。
S610,配置器在DCL中查找RCAC对应的厂商标识。
S611,配置器比较用户设备的VID与(在DCL中查找到的)该RCAC对应的厂商标识是否一致。
若用户设备的VID与(在DCL中查找到的)该RCAC对应的厂商标识不一致,则配置器可以提示用户设备可能被非法生态平台绑定,并询问用户是否继续配置该用户设备。
S612,配置器配置该用户设备。
若用户同意继续配置,则配置器可以发起CSR请求,为用户设备配置NOC。
或者,若用户设备的VID与(在DCL中查找到的)该RCAC对应的厂商标识一致,则配置器可以发起CSR请求,为用户设备配置NOC。
在本申请实施例中,第一设备通过证书中心能够验证第二设备的根认证中心证书RCAC,从而能够降低配置过程中被攻击的风险,避免出现生态平台敏感数据泄露的问题。
上文结合图1至图6,详细描述了本申请的方法实施例,下面结合图7至图9,详细描述本申请的装置实施例。应理解,方法实施例的描述与装置实施例的描述相互对应,因此,未详细描述的部分可以参见前面方法实施例。
图7是本申请一实施例提供的配置设备的装置的示意性结构图。如图7所示,所述装置700包括验证单元710,具体如下:
验证单元710,用于通过证书中心验证第二设备的根认证中心证书RCAC,所述证书中心能够确定所述RCAC的合法性。
可选地,所述装置700还包括确定单元720,用于:确定当前配置是否为二次配网;其中,所述验证单元710具体用于:在当前配置为二次配网的情况下,通过所述证书中心验证第二设备的RCAC。
可选地,所述验证单元710具体用于:通过所述证书中心中存储的RCAC验证所述第二设备的RCAC。
可选地,所述验证单元710具体用于:在所述证书中心中查找所述RCAC;若所述证书中心不包括所述RCAC,则确定所述第二设备被非法生态平台绑定。
可选地,所述验证单元710还用于:若所述证书中心不包括所述RCAC,则输出第一信息,所述第一信息用于询问用户是否继续配置所述第二设备;所述装置700还包括触发单元730,用于:在用户指示继续配置所述第二设备的情况下,触发所述第二设备的配置流程。
可选地,所述装置700还包括触发单元730,用于:若所述证书中心包括所述RCAC,则触发所述第二设备的配置流程。
可选地,所述验证单元710还用于:若所述证书中心包括所述RCAC,则通过所述证书中心中所述RCAC对应的厂商标识验证所述第二设备的RCAC。
可选地,所述验证单元710具体用于:在所述证书中心中查找所述RCAC的厂商标识;若所述证书中心包括所述RCAC、且所述第二设备的厂商标识与所述证书中心中所述RCAC对应的厂商标识不一致,则确定所述第二设备被非法生态平台绑定。
可选地,所述装置700还包括输出单元740,用于:若所述证书中心包括所述RCAC、且所述第二设备的厂商标识与所述证书中心中所述RCAC对应的厂商标识不一致,则输出第二信息,所述第二信息用于询问用户是否继续配置所述第二设备;所述装置700还包括触发单元730,用于:在用户指示继续配置所述第二设备的情况下,触发所述第二设备的配置流程。
可选地,所述装置700还包括触发单元730,用于:若所述证书中心包括所述RCAC、且所述第二设备的厂商标识与所述RCAC对应的厂商标识一致,则触发所述第二设备的配置流程。
可选地,所述验证单元710具体用于:通过所述证书中心中存储的RCAC的标识验证所述第二设备的RCAC。
可选地,所述验证单元710具体用于:在所述证书中心中查找所述RCAC的标识;若所述证书中心不包括所述RCAC的标识,则确定所述第二设备被非法生态平台绑定。
可选地,所述装置700还包括输出单元740,用于:若所述证书中心不包括所述RCAC的标识,则输出第三信息,所述第三信息用于询问用户是否继续配置所述第二设备;所述装置700还包括触发单元730,用于:在用户指示继续配置所述第二设备的情况下,触发所述第二设备的配置流程。
可选地,所述装置700还包括触发单元730,用于:若所述证书中心包括所述RCAC的标识,则触发所述第二设备的配置流程。
可选地,所述验证单元710还用于:若所述证书中心包括所述RCAC的标识,则通过所述证书中心中所述RCAC的标识对应的厂商标识验证所述第二设备的RCAC。
可选地,所述验证单元710具体用于:在所述证书中心中查找所述RCAC的标识对应的厂商标识;若所述证书中心包括所述RCAC的标识、且所述第二设备的厂商标识与所述RCAC的标识对应的厂商标识不一致,则确定所述第二设备被非法生态平台绑定。
可选地,所述装置700还包括输出单元740,用于:若所述证书中心包括所述RCAC的标识、且所述第二设备的厂商标识与所述RCAC的标识对应的厂商标识不一致,则输出第四信息,所述第四信息用于询问用户是否继续配置所述第二设备;所述装置700还包括触发单元730,用于:在用户指示继续配置所述第二设备的情况下,触发所述第二设备的配置流程。
可选地,所述装置700还包括触发单元730,用于:若所述证书中心包括所述RCAC的标识、且所述第二设备的厂商标识与所述RCAC的标识对应的厂商标识一致,则触发所述第二设备的配置流程。
可选地,所述证书中心包括第一语法,所述第一语法包括用于记录RCAC的标识的字段;所述验证单元710具体用于:在所述第一语法中查找所述RCAC的标识。
可选地,所述证书中心包括第二语法,所述第二语法包括用于记录RCAC的标识的字段及用于记录厂商标识的字段;所述验证单元710具体用于:在所述第二语法中查找所述RCAC对应的厂商标识。
可选地,所述RCAC的标识包括以下至少一项:所述RCAC的主体、所述RCAC的公钥及所述RCAC的主体密钥标识。
可选地,所述装置700还包括发送单元750,用于:向所述第二设备发送第五信息,所述第五信息用于请求所述第二设备的编织网络标识;所述确定单元720具体用于:若所述装置接收到所述第二设 备发送的第六信息,则确定当前配置为二次配网;若所述装置未接收到所述第二设备发送的所述第六信息,则确定当前配置为首次配网;其中,所述第六信息用于指示所述编织网络标识。
可选地,所述第六信息包括标识信息,所述标识信息是通过第一私钥签名后得到的,所述验证单元710还用于:使用第一公钥对所述标识信息进行验证,以获取所述标识信息中的所述编织网络标识,所述第一公钥与所述第一私钥对应。
可选地,所述装置700还包括发送单元750和接收单元760,所述发送单元750用于:向所述第二设备发送第七信息,所述第七信息用于请求所述第二设备的第一属性值;所述接收单元760用于:接收所述第二设备发送的第八信息,所述第八信息用于指示所述第一属性值;所述确定单元具体用于:若所述第一属性值为非零值,则确定当前配置为二次配网;若所述第一属性值为零,则确定当前配置为首次配网。
可选地,所述第八信息包括属性信息,所述属性信息是通过第二私钥签名后得到的,所述验证单元710还用于:使用第二公钥对所述属性信息进行验证,以获取所述属性信息中的所述第一属性值,所述第二公钥与所述第二私钥对应。
可选地,所述装置700还包括发送单元750和接收单元760,所述发送单元750用于:向所述第二设备发送第九信息,所述第九信息用于请求所述第二设备的RCAC;所述接收单元760用于:接收所述第二设备发送的第十信息,所述第十信息用于指示所述RCAC。
可选地,所述第十信息包括RCAC信息,所述RCAC信息是通过第三私钥签名后得到的,所述验证单元710还用于:使用第三公钥对所述RCAC信息进行验证,以确定所述RCAC信息包括所述RCAC,所述第三公钥与所述第三私钥对应。
可选地,所述证书中心包括第三语法,所述第三语法包括厂商语法和/或用于记录RCAC而构建的语法,所述第三语法包括用于记录RCAC的字段;所述验证单元710具体用于:在所述第三语法中查找所述RCAC。
可选地,所述证书中心包括第四语法,所述第四语法包括厂商语法和/或用于记录RCAC而构建的语法,所述第四语法包括用于记录RCAC的字段及用于记录厂商标识的字段;所述验证单元710具体用于:在所述第四语法中查找所述RCAC对应的厂商标识。
图8是本申请一实施例提供的配置设备的装置的示意性结构图。图8中的配置设备的装置800包括接收单元810及发送单元820,具体如下:
接收单元810,用于接收第一设备发送的第九信息,所述第九信息用于请求所述装置的根认证中心证书RCAC;
发送单元820,用于向所述第一设备发送第十信息,所述第十信息用于指示所述RCAC。
可选地,所述第十信息包括RCAC信息,所述装置800还包括签名单元830,用于:使用第三私钥对所述RCAC进行签名,得到所述RCAC信息。
可选地,所述接收单元810还用于:接收所述第一设备发送的第五信息,所述第五信息用于请求所述装置的编织网络标识;所述发送单元820还用于:若所述装置已配置编织网络,则向所述第一设备发送第六信息,所述第六信息用于指示所述编织网络标识。
可选地,所述第六信息包括标识信息,所述装置800还包括签名单元830,用于:使用第一私钥对所述编织网络标识进行签名,得到所述标识信息。
可选地,所述接收单元810还用于:接收所述第一设备发送的第七信息,所述第七信息用于请求所述装置的第一属性值;所述发送单元820还用于:向所述第一设备发送第八信息,所述第八信息用于指示所述第一属性值。
可选地,所述第八信息包括属性信息,所述装置800还包括签名单元830,用于:使用第二私钥对所述第一属性值进行签名,得到所述属性信息。
图9是本申请一实施例提供的装置的示意性结构图。图9中的虚线表示该单元或模块为可选的。该装置900可用于实现上述方法实施例中描述的方法。装置900可以是芯片或配置设备的装置。
装置900可以包括一个或多个处理器910。该处理器910可支持装置900实现前文方法实施例所描述的方法。该处理器910可以是通用处理器或者专用处理器。例如,该处理器可以为中央处理单元(central processing unit,CPU)。或者,该处理器还可以是其他通用处理器、数字信号处理器(digital signal processor,DSP)、专用集成电路(application specific integrated circuit,ASIC)、现成可编程门阵列(field programmable gate array,FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
装置900还可以包括一个或多个存储器920。存储器920上存储有程序,该程序可以被处理器910执行,使得处理器910执行前文方法实施例所描述的方法。存储器920可以独立于处理器910也可以 集成在处理器910中。
装置900还可以包括收发器930。处理器910可以通过收发器930与其他设备或芯片进行通信。例如,处理器910可以通过收发器930与其他设备或芯片进行数据收发。
本申请实施例还提供一种计算机可读存储介质,用于存储程序。该计算机可读存储介质可应用于本申请实施例提供的配置设备的装置中,并且该程序使得计算机执行本申请各个实施例中的由配置设备的装置执行的方法。
本申请实施例还提供一种计算机程序产品。该计算机程序产品包括程序。该计算机程序产品可应用于本申请实施例提供的配置设备的装置中,并且该程序使得计算机执行本申请各个实施例中的由配置设备的装置执行的方法。
本申请实施例还提供一种计算机程序。该计算机程序可应用于本申请实施例提供的配置设备的装置中,并且该计算机程序使得计算机执行本申请各个实施例中的由配置设备的装置执行的方法。
应理解,在本申请实施例中,“与A相应的B”表示B与A相关联,根据A可以确定B。但还应理解,根据A确定B并不意味着仅仅根据A确定B,还可以根据A和/或其它信息确定B。
应理解,本文中术语“和/或”,仅仅是一种描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况。另外,本文中字符“/”,一般表示前后关联对象是一种“或”的关系。
应理解,在本申请的各种实施例中,上述各过程的序号的大小并不意味着执行顺序的先后,各过程的执行顺序应以其功能和内在逻辑确定,而不应对本申请实施例的实施过程构成任何限定。
在本申请所提供的几个实施例中,应该理解到,所揭露的***、装置和方法,可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,所述单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个***,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信连接,可以是电性,机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外,在本申请各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中。
在上述实施例中,可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时,可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时,全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中,或者从一个计算机可读存储介质向另一个计算机可读存储介质传输,例如,所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line,DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够读取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质,(例如,软盘、硬盘、磁带)、光介质(例如,数字通用光盘(digital video disc,DVD))或者半导体介质(例如,固态硬盘(solid state disk,SSD))等。
以上所述,仅为本申请的具体实施方式,但本申请的保护范围并不局限于此,任何熟悉本技术领域的技术人员在本申请揭露的技术范围内,可轻易想到变化或替换,都应涵盖在本申请的保护范围之内。因此,本申请的保护范围应以所述权利要求的保护范围为准。
Claims (82)
- 一种配置设备的方法,其特征在于,包括:第一设备通过证书中心验证第二设备的根认证中心证书RCAC,所述证书中心能够确定所述RCAC的合法性。
- 根据权利要求1所述的方法,其特征在于,所述方法还包括:所述第一设备确定当前配置是否为二次配网;其中,所述第一设备通过证书中心验证第二设备的根认证中心证书RCAC,包括:在当前配置为二次配网的情况下,所述第一设备通过所述证书中心验证第二设备的RCAC。
- 根据权利要求1或2所述的方法,其特征在于,所述第一设备通过证书中心验证第二设备的根认证中心证书RCAC,包括:所述第一设备通过所述证书中心中存储的RCAC验证所述第二设备的RCAC。
- 根据权利要求3所述的方法,其特征在于,所述第一设备通过所述证书中心中存储的RCAC验证所述第二设备的RCAC,包括:所述第一设备在所述证书中心中查找所述RCAC;若所述证书中心不包括所述RCAC,则所述第一设备确定所述第二设备被非法生态平台绑定。
- 根据权利要求4所述的方法,其特征在于,所述方法还包括:若所述证书中心不包括所述RCAC,则所述第一设备输出第一信息,所述第一信息用于询问用户是否继续配置所述第二设备;在用户指示继续配置所述第二设备的情况下,所述第一设备触发所述第二设备的配置流程。
- 根据权利要求4或5所述的方法,其特征在于,所述方法还包括:若所述证书中心包括所述RCAC,则所述第一设备触发所述第二设备的配置流程。
- 根据权利要求4或5所述的方法,其特征在于,所述方法还包括:若所述证书中心包括所述RCAC,则所述第一设备通过所述证书中心中所述RCAC对应的厂商标识验证所述第二设备的RCAC。
- 根据权利要求7所述的方法,其特征在于,所述第一设备通过所述证书中心中所述RCAC对应的厂商标识验证所述第二设备的RCAC,包括:所述第一设备在所述证书中心中查找所述RCAC的厂商标识;若所述证书中心包括所述RCAC、且所述第二设备的厂商标识与所述证书中心中所述RCAC对应的厂商标识不一致,则所述第一设备确定所述第二设备被非法生态平台绑定。
- 根据权利要求8所述的方法,其特征在于,所述方法还包括:若所述证书中心包括所述RCAC、且所述第二设备的厂商标识与所述证书中心中所述RCAC对应的厂商标识不一致,则所述第一设备输出第二信息,所述第二信息用于询问用户是否继续配置所述第二设备;在用户指示继续配置所述第二设备的情况下,所述第一设备触发所述第二设备的配置流程。
- 根据权利要求8或9所述的方法,其特征在于,所述方法还包括:若所述证书中心包括所述RCAC、且所述第二设备的厂商标识与所述RCAC对应的厂商标识一致,则所述第一设备触发所述第二设备的配置流程。
- 根据权利要求1或2所述的方法,其特征在于,所述第一设备通过证书中心验证第二设备的根认证中心证书RCAC,包括:所述第一设备通过所述证书中心中存储的RCAC的标识验证所述第二设备的RCAC。
- 根据权利要求11所述的方法,其特征在于,所述第一设备通过所述证书中心中存储的RCAC的标识验证所述第二设备的RCAC,包括:所述第一设备在所述证书中心中查找所述RCAC的标识;若所述证书中心不包括所述RCAC的标识,则所述第一设备确定所述第二设备被非法生态平台绑定。
- 根据权利要求12所述的方法,其特征在于,所述方法还包括:若所述证书中心不包括所述RCAC的标识,则所述第一设备输出第三信息,所述第三信息用于询问用户是否继续配置所述第二设备;在用户指示继续配置所述第二设备的情况下,所述第一设备触发所述第二设备的配置流程。
- 根据权利要求12或13所述的方法,其特征在于,所述方法还包括:若所述证书中心包括所述RCAC的标识,则所述第一设备触发所述第二设备的配置流程。
- 根据权利要求12或13所述的方法,其特征在于,所述方法还包括:若所述证书中心包括所述RCAC的标识,则所述第一设备通过所述证书中心中所述RCAC的标识对应的厂商标识验证所述第二设备的RCAC。
- 根据权利要求15所述的方法,其特征在于,所述第一设备通过所述证书中心中所述RCAC的标识对应的厂商标识验证所述第二设备的RCAC,包括:所述第一设备在所述证书中心中查找所述RCAC的标识对应的厂商标识;若所述证书中心包括所述RCAC的标识、且所述第二设备的厂商标识与所述RCAC的标识对应的厂商标识不一致,则所述第一设备确定所述第二设备被非法生态平台绑定。
- 根据权利要求16所述的方法,其特征在于,所述方法还包括:若所述证书中心包括所述RCAC的标识、且所述第二设备的厂商标识与所述RCAC的标识对应的厂商标识不一致,则所述第一设备输出第四信息,所述第四信息用于询问用户是否继续配置所述第二设备;在用户指示继续配置所述第二设备的情况下,所述第一设备触发所述第二设备的配置流程。
- 根据权利要求16或17所述的方法,其特征在于,所述方法还包括:若所述证书中心包括所述RCAC的标识、且所述第二设备的厂商标识与所述RCAC的标识对应的厂商标识一致,则所述第一设备触发所述第二设备的配置流程。
- 根据权利要求12至18中任一项所述的方法,其特征在于,所述证书中心包括第一语法,所述第一语法包括用于记录RCAC的标识的字段;所述第一设备在所述证书中心中查找所述RCAC的标识,包括:所述第一设备在所述第一语法中查找所述RCAC的标识。
- 根据权利要求15至19中任一项所述的方法,其特征在于,所述证书中心包括第二语法,所述第二语法包括用于记录RCAC的标识的字段及用于记录厂商标识的字段;所述第一设备在所述证书中心中查找所述RCAC对应的厂商标识,包括:所述第一设备在所述第二语法中查找所述RCAC对应的厂商标识。
- 根据权利要求11至20中任一项所述的方法,其特征在于,所述RCAC的标识包括以下至少一项:所述RCAC的主体、所述RCAC的公钥及所述RCAC的主体密钥标识。
- 根据权利要求2所述的方法,其特征在于,所述第一设备确定当前配置是否为二次配网,包括:所述第一设备向所述第二设备发送第五信息,所述第五信息用于请求所述第二设备的编织网络标识;若所述第一设备接收到所述第二设备发送的第六信息,则所述第一设备确定当前配置为二次配网;若所述第一设备未接收到所述第二设备发送的所述第六信息,则所述第一设备确定当前配置为首次配网;其中,所述第六信息用于指示所述编织网络标识。
- 根据权利要求22所述的方法,其特征在于,所述第六信息包括标识信息,所述标识信息是通过第一私钥签名后得到的,所述方法还包括:所述第一设备使用第一公钥对所述标识信息进行验证,以获取所述标识信息中的所述编织网络标识,所述第一公钥与所述第一私钥对应。
- 根据权利要求2所述的方法,其特征在于,所述第一设备确定当前配置是否为二次配网,包括:所述第一设备向所述第二设备发送第七信息,所述第七信息用于请求所述第二设备的第一属性值;所述第一设备接收所述第二设备发送的第八信息,所述第八信息用于指示所述第一属性值;若所述第一属性值为非零值,则所述第一设备确定当前配置为二次配网;若所述第一属性值为零,则所述第一设备确定当前配置为首次配网。
- 根据权利要求24所述的方法,其特征在于,所述第八信息包括属性信息,所述属性信息是通过第二私钥签名后得到的,所述方法还包括:所述第一设备使用第二公钥对所述属性信息进行验证,以获取所述属性信息中的所述第一属性值,所述第二公钥与所述第二私钥对应。
- 根据权利要求1至25中任一项所述的方法,其特征在于,所述方法还包括:所述第一设备向所述第二设备发送第九信息,所述第九信息用于请求所述第二设备的RCAC;所述第一设备接收所述第二设备发送的第十信息,所述第十信息用于指示所述RCAC。
- 根据权利要求26所述的方法,其特征在于,所述第十信息包括RCAC信息,所述RCAC信息是通过第三私钥签名后得到的,所述方法还包括:所述第一设备使用第三公钥对所述RCAC信息进行验证,以确定所述RCAC信息包括所述RCAC,所述第三公钥与所述第三私钥对应。
- 根据权利要求4至10中任一项所述的方法,其特征在于,所述证书中心包括第三语法,所述第三语法包括厂商语法和/或用于记录RCAC而构建的语法,所述第三语法包括用于记录RCAC的字段;所述第一设备在所述证书中心中查找所述RCAC,包括:所述第一设备在所述第三语法中查找所述RCAC。
- 根据权利要求8至10中任一项所述的方法,其特征在于,所述证书中心包括第四语法,所述第四语法包括厂商语法和/或用于记录RCAC而构建的语法,所述第四语法包括用于记录RCAC的字段及用于记录厂商标识的字段;所述第一设备在所述证书中心中查找所述RCAC对应的厂商标识,包括:所述第一设备在所述第四语法中查找所述RCAC对应的厂商标识。
- 一种配置设备的方法,其特征在于,包括:第二设备接收第一设备发送的第九信息,所述第九信息用于请求所述第二设备的根认证中心证书RCAC;所述第二设备向所述第一设备发送第十信息,所述第十信息用于指示所述RCAC。
- 根据权利要求30所述的方法,其特征在于,所述第十信息包括RCAC信息,所述方法还包括:所述第二设备使用第三私钥对所述RCAC进行签名,得到所述RCAC信息。
- 根据权利要求30或31所述的方法,其特征在于,所述方法还包括:所述第二设备接收所述第一设备发送的第五信息,所述第五信息用于请求所述第二设备的编织网络标识;若所述第二设备已配置编织网络,则所述第二设备向所述第一设备发送第六信息,所述第六信息用于指示所述编织网络标识。
- 根据权利要求32所述的方法,其特征在于,所述第六信息包括标识信息,所述方法还包括:所述第二设备使用第一私钥对所述编织网络标识进行签名,得到所述标识信息。
- 根据权利要求30或31所述的方法,其特征在于,所述方法还包括:所述第二设备接收所述第一设备发送的第七信息,所述第七信息用于请求所述第二设备的第一属性值;所述第二设备向所述第一设备发送第八信息,所述第八信息用于指示所述第一属性值。
- 根据权利要求34所述的方法,其特征在于,所述第八信息包括属性信息,所述方法还包括:所述第二设备使用第二私钥对所述第一属性值进行签名,得到所述属性信息。
- 一种配置设备的装置,其特征在于,包括:验证单元,用于通过证书中心验证第二设备的根认证中心证书RCAC,所述证书中心能够确定所述RCAC的合法性。
- 根据权利要求36所述的装置,其特征在于,所述装置还包括确定单元,用于:确定当前配置是否为二次配网;其中,所述验证单元具体用于:在当前配置为二次配网的情况下,通过所述证书中心验证第二设备的RCAC。
- 根据权利要求36或37所述的装置,其特征在于,所述验证单元具体用于:通过所述证书中心中存储的RCAC验证所述第二设备的RCAC。
- 根据权利要求38所述的装置,其特征在于,所述验证单元具体用于:在所述证书中心中查找所述RCAC;若所述证书中心不包括所述RCAC,则确定所述第二设备被非法生态平台绑定。
- 根据权利要求39所述的装置,其特征在于,所述验证单元还用于:若所述证书中心不包括所述RCAC,则输出第一信息,所述第一信息用于询问用户是否继续配置所述第二设备;所述装置还包括触发单元,用于:在用户指示继续配置所述第二设备的情况下,触发所述第二设备的配置流程。
- 根据权利要求39或40所述的装置,其特征在于,所述装置还包括触发单元,用于:若所述证书中心包括所述RCAC,则触发所述第二设备的配置流程。
- 根据权利要求39或40所述的装置,其特征在于,所述验证单元还用于:若所述证书中心包括所述RCAC,则通过所述证书中心中所述RCAC对应的厂商标识验证所述第二设备的RCAC。
- 根据权利要求42所述的装置,其特征在于,所述验证单元具体用于:在所述证书中心中查找所述RCAC的厂商标识;若所述证书中心包括所述RCAC、且所述第二设备的厂商标识与所述证书中 心中所述RCAC对应的厂商标识不一致,则确定所述第二设备被非法生态平台绑定。
- 根据权利要求43所述的装置,其特征在于,所述装置还包括输出单元,用于:若所述证书中心包括所述RCAC、且所述第二设备的厂商标识与所述证书中心中所述RCAC对应的厂商标识不一致,则输出第二信息,所述第二信息用于询问用户是否继续配置所述第二设备;所述装置还包括触发单元,用于:在用户指示继续配置所述第二设备的情况下,触发所述第二设备的配置流程。
- 根据权利要求43或44所述的装置,其特征在于,所述装置还包括触发单元,用于:若所述证书中心包括所述RCAC、且所述第二设备的厂商标识与所述RCAC对应的厂商标识一致,则触发所述第二设备的配置流程。
- 根据权利要求36或37所述的装置,其特征在于,所述验证单元具体用于:通过所述证书中心中存储的RCAC的标识验证所述第二设备的RCAC。
- 根据权利要求46所述的装置,其特征在于,所述验证单元具体用于:在所述证书中心中查找所述RCAC的标识;若所述证书中心不包括所述RCAC的标识,则确定所述第二设备被非法生态平台绑定。
- 根据权利要求47所述的装置,其特征在于,所述装置还包括输出单元,用于:若所述证书中心不包括所述RCAC的标识,则输出第三信息,所述第三信息用于询问用户是否继续配置所述第二设备;所述装置还包括触发单元,用于:在用户指示继续配置所述第二设备的情况下,触发所述第二设备的配置流程。
- 根据权利要求47或48所述的装置,其特征在于,所述装置还包括触发单元,用于:若所述证书中心包括所述RCAC的标识,则触发所述第二设备的配置流程。
- 根据权利要求47或48所述的装置,其特征在于,所述验证单元还用于:若所述证书中心包括所述RCAC的标识,则通过所述证书中心中所述RCAC的标识对应的厂商标识验证所述第二设备的RCAC。
- 根据权利要求50所述的装置,其特征在于,所述验证单元具体用于:在所述证书中心中查找所述RCAC的标识对应的厂商标识;若所述证书中心包括所述RCAC的标识、且所述第二设备的厂商标识与所述RCAC的标识对应的厂商标识不一致,则确定所述第二设备被非法生态平台绑定。
- 根据权利要求51所述的装置,其特征在于,所述装置还包括输出单元,用于:若所述证书中心包括所述RCAC的标识、且所述第二设备的厂商标识与所述RCAC的标识对应的厂商标识不一致,则输出第四信息,所述第四信息用于询问用户是否继续配置所述第二设备;所述装置还包括触发单元,用于:在用户指示继续配置所述第二设备的情况下,触发所述第二设备的配置流程。
- 根据权利要求51或52所述的装置,其特征在于,所述装置还包括触发单元,用于:若所述证书中心包括所述RCAC的标识、且所述第二设备的厂商标识与所述RCAC的标识对应的厂商标识一致,则触发所述第二设备的配置流程。
- 根据权利要求47至53中任一项所述的装置,其特征在于,所述证书中心包括第一语法,所述第一语法包括用于记录RCAC的标识的字段;所述验证单元具体用于:在所述第一语法中查找所述RCAC的标识。
- 根据权利要求50至54中任一项所述的装置,其特征在于,所述证书中心包括第二语法,所述第二语法包括用于记录RCAC的标识的字段及用于记录厂商标识的字段;所述验证单元具体用于:在所述第二语法中查找所述RCAC对应的厂商标识。
- 根据权利要求46至55中任一项所述的装置,其特征在于,所述RCAC的标识包括以下至少一项:所述RCAC的主体、所述RCAC的公钥及所述RCAC的主体密钥标识。
- 根据权利要求37所述的装置,其特征在于,所述装置还包括发送单元,用于:向所述第二设备发送第五信息,所述第五信息用于请求所述第二设备的编织网络标识;所述确定单元具体用于:若所述装置接收到所述第二设备发送的第六信息,则确定当前配置为二次配网;若所述装置未接收到所述第二设备发送的所述第六信息,则确定当前配置为首次配网;其中,所述第六信息用于指示所述编织网络标识。
- 根据权利要求57所述的装置,其特征在于,所述第六信息包括标识信息,所述标识信息是通过第一私钥签名后得到的,所述验证单元还用于:使用第一公钥对所述标识信息进行验证,以获取所述标识信息中的所述编织网络标识,所述第一公钥与所述第一私钥对应。
- 根据权利要求37所述的装置,其特征在于,所述装置还包括发送单元和接收单元,所述发送单元用于:向所述第二设备发送第七信息,所述第七信息用于请求所述第二设备的第一属性值;所述接收单元用于:接收所述第二设备发送的第八信息,所述第八信息用于指示所述第一属性值;所述确 定单元具体用于:若所述第一属性值为非零值,则确定当前配置为二次配网;若所述第一属性值为零,则确定当前配置为首次配网。
- 根据权利要求59所述的装置,其特征在于,所述第八信息包括属性信息,所述属性信息是通过第二私钥签名后得到的,所述验证单元还用于:使用第二公钥对所述属性信息进行验证,以获取所述属性信息中的所述第一属性值,所述第二公钥与所述第二私钥对应。
- 根据权利要求36至60中任一项所述的装置,其特征在于,所述装置还包括发送单元和接收单元,所述发送单元用于:向所述第二设备发送第九信息,所述第九信息用于请求所述第二设备的RCAC;所述接收单元用于:接收所述第二设备发送的第十信息,所述第十信息用于指示所述RCAC。
- 根据权利要求61所述的装置,其特征在于,所述第十信息包括RCAC信息,所述RCAC信息是通过第三私钥签名后得到的,所述验证单元还用于:使用第三公钥对所述RCAC信息进行验证,以确定所述RCAC信息包括所述RCAC,所述第三公钥与所述第三私钥对应。
- 根据权利要求39至45中任一项所述的装置,其特征在于,所述证书中心包括第三语法,所述第三语法包括厂商语法和/或用于记录RCAC而构建的语法,所述第三语法包括用于记录RCAC的字段;所述验证单元具体用于:在所述第三语法中查找所述RCAC。
- 根据权利要求43至45中任一项所述的装置,其特征在于,所述证书中心包括第四语法,所述第四语法包括厂商语法和/或用于记录RCAC而构建的语法,所述第四语法包括用于记录RCAC的字段及用于记录厂商标识的字段;所述验证单元具体用于:在所述第四语法中查找所述RCAC对应的厂商标识。
- 一种配置设备的装置,其特征在于,包括:接收单元,用于接收第一设备发送的第九信息,所述第九信息用于请求所述装置的根认证中心证书RCAC;发送单元,用于向所述第一设备发送第十信息,所述第十信息用于指示所述RCAC。
- 根据权利要求65所述的装置,其特征在于,所述第十信息包括RCAC信息,所述装置还包括签名单元,用于:使用第三私钥对所述RCAC进行签名,得到所述RCAC信息。
- 根据权利要求65或66所述的装置,其特征在于,所述接收单元还用于:接收所述第一设备发送的第五信息,所述第五信息用于请求所述装置的编织网络标识;所述发送单元还用于:若所述装置已配置编织网络,则向所述第一设备发送第六信息,所述第六信息用于指示所述编织网络标识。
- 根据权利要求67所述的装置,其特征在于,所述第六信息包括标识信息,所述装置还包括签名单元,用于:使用第一私钥对所述编织网络标识进行签名,得到所述标识信息。
- 根据权利要求65或66所述的装置,其特征在于,所述接收单元还用于:接收所述第一设备发送的第七信息,所述第七信息用于请求所述装置的第一属性值;所述发送单元还用于:向所述第一设备发送第八信息,所述第八信息用于指示所述第一属性值。
- 根据权利要求69所述的装置,其特征在于,所述第八信息包括属性信息,所述装置还包括签名单元,用于:使用第二私钥对所述第一属性值进行签名,得到所述属性信息。
- 一种配置设备的装置,其特征在于,包括存储器和处理器,所述存储器用于存储程序,所述处理器用于调用所述存储器中的程序,以执行如权利要求1至29中任一项所述的方法。
- 一种配置设备的装置,其特征在于,包括存储器和处理器,所述存储器用于存储程序,所述处理器用于调用所述存储器中的程序,以执行如权利要求30至35中任一项所述的方法。
- 一种配置设备的装置,其特征在于,包括处理器,用于从存储器中调用程序,以执行如权利要求1至29中任一项所述的方法。
- 一种配置设备的装置,其特征在于,包括处理器,用于从存储器中调用程序,以执行如权利要求30至35中任一项所述的方法。
- 一种芯片,其特征在于,包括处理器,用于从存储器调用程序,使得安装有所述芯片的设备执行如权利要求1至29中任一项所述的方法。
- 一种芯片,其特征在于,包括处理器,用于从存储器调用程序,使得安装有所述芯片的设备执行如权利要求30至35中任一项所述的方法。
- 一种计算机可读存储介质,其特征在于,其上存储有程序,所述程序使得计算机执行如权利要求1至29中任一项所述的方法。
- 一种计算机可读存储介质,其特征在于,其上存储有程序,所述程序使得计算机执行如权利要求30至35中任一项所述的方法。
- 一种计算机程序产品,其特征在于,包括程序,所述程序使得计算机执行如权利要求1至29中任一项所述的方法。
- 一种计算机程序产品,其特征在于,包括程序,所述程序使得计算机执行如权利要求30至35中任一项所述的方法。
- 一种计算机程序,其特征在于,所述计算机程序使得计算机执行如权利要求1至29中任一项所述的方法。
- 一种计算机程序,其特征在于,所述计算机程序使得计算机执行如权利要求30至35中任一项所述的方法。
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2022/133415 WO2024108374A1 (zh) | 2022-11-22 | 2022-11-22 | 配置设备的方法及装置 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2022/133415 WO2024108374A1 (zh) | 2022-11-22 | 2022-11-22 | 配置设备的方法及装置 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2024108374A1 true WO2024108374A1 (zh) | 2024-05-30 |
Family
ID=91194950
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2022/133415 WO2024108374A1 (zh) | 2022-11-22 | 2022-11-22 | 配置设备的方法及装置 |
Country Status (1)
Country | Link |
---|---|
WO (1) | WO2024108374A1 (zh) |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080162928A1 (en) * | 2006-12-27 | 2008-07-03 | General Instrument Corporation | Method and Apparatus for Distributing Root Certification |
CN113472541A (zh) * | 2020-03-12 | 2021-10-01 | 华为技术有限公司 | 证书切换方法及装置 |
CN114172740A (zh) * | 2021-12-16 | 2022-03-11 | 广州城市理工学院 | 一种基于配网证书验证的配电网安全接入方法 |
-
2022
- 2022-11-22 WO PCT/CN2022/133415 patent/WO2024108374A1/zh unknown
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080162928A1 (en) * | 2006-12-27 | 2008-07-03 | General Instrument Corporation | Method and Apparatus for Distributing Root Certification |
CN113472541A (zh) * | 2020-03-12 | 2021-10-01 | 华为技术有限公司 | 证书切换方法及装置 |
CN114172740A (zh) * | 2021-12-16 | 2022-03-11 | 广州城市理工学院 | 一种基于配网证书验证的配电网安全接入方法 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11477625B2 (en) | System, apparatus and method for scalable internet of things (IoT) device on-boarding with quarantine capabilities | |
US11153081B2 (en) | System for user-friendly access control setup using a protected setup | |
US11956361B2 (en) | Network function service invocation method, apparatus, and system | |
JP5944596B2 (ja) | ワイヤレスドッキングサービスに対してワイヤレスドッキーを認証すること | |
US11368842B2 (en) | Session establishment method and means and communication system | |
US10326590B2 (en) | Technologies for trusted device on-boarding | |
WO2019015500A1 (zh) | 入网认证方法、装置及*** | |
US9154483B1 (en) | Secure device configuration | |
US20190074981A1 (en) | Post-manufacture generation of device certificate and private key for public key infrastructure | |
US11128438B1 (en) | Systems, methods, and media for sharing IoT device profile data | |
WO2020220865A1 (zh) | 网络功能服务的身份校验方法及相关装置 | |
US20120303952A1 (en) | Dynamic Platform Reconfiguration By Multi-Tenant Service Providers | |
TW201428535A (zh) | 用於管理存取控制之基於原則技術 | |
KR20160127167A (ko) | 다중 팩터 인증 기관 | |
WO2018120913A1 (zh) | 一种获取证书、鉴权的方法及网络设备 | |
US20210144142A1 (en) | Extended trust for onboarding | |
WO2020228751A1 (zh) | 一种通信方法和装置 | |
WO2021196913A1 (zh) | 一种终端参数更新的保护方法和通信装置 | |
WO2018196705A1 (zh) | 网络安全保护方法、设备及*** | |
JP2023533597A (ja) | 電気自動車用充電ステーションの識別方法 | |
WO2024108374A1 (zh) | 配置设备的方法及装置 | |
WO2023087930A1 (zh) | 一种设备身份的认证方法、装置、电子设备及存储介质 | |
US11171786B1 (en) | Chained trusted platform modules (TPMs) as a secure bus for pre-placement of device capabilities | |
EP4340297A1 (en) | Service function authorization | |
WO2018137239A1 (zh) | 一种鉴权方法、鉴权服务器和核心网设备 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 22966075 Country of ref document: EP Kind code of ref document: A1 |