WO2021046822A1

WO2021046822A1 - Device activation method, terminal device, and computer storage medium

Info

Publication number: WO2021046822A1
Application number: PCT/CN2019/105784
Authority: WO
Inventors: 杨宁
Original assignee: Oppo广东移动通信有限公司
Priority date: 2019-09-12
Filing date: 2019-09-12
Publication date: 2021-03-18
Also published as: CN113647075B; CN113647075A

Abstract

A device activation method, a terminal device, and a computer storage medium. The method comprises: a first device receives resource information sent by a second device, the resource information comprising a first owner transfer method supported by the second device, and the resource information further comprising at least one of the following: a credential type supported by the second device, a configuration mode supported by the second device, the working state of the second device, and access permission information (S301); the first device sends to the second device a second owner transfer method configured for the second device and a client-led configuration mode (S302); the first device performs a DTLS handshake with the second device according to the second owner transfer method to establish a secure connection (S303); the first device sends credential information to the second device by means of the secure connection (S304). The method can simplify the operation process and reduce transmission overhead.

Description

Device activation method, terminal device and computer storage medium

Technical field

The present invention relates to the field of communication technology, and in particular to a device activation method, terminal device and computer storage medium.

Background technique

In the Internet of Things system, the newly added terminal device can interact with the activated terminal device after it is activated. The traditional device activation method is: configure device ownership, that is, a legitimate user uses an Owner Transfer Method (Owner Transfer Method, OTM) to establish the ownership of a terminal device through an activation tool (Onboarding Tool, OBT). After the ownership is established, set the device to the normal operating state, including using OBT to configure the terminal device to authorize the management service, and the management service to set the terminal device with the credentials and access permissions required to interact with other activated terminal devices. The terminal device can operate normally and interact with the activated terminal device. The process of realizing device activation can specifically include: discovering new terminal devices, executing owner transfer methods, establishing device identity, establishing owner credentials, assigning devices to management services, configuring device management services, and preparing for interaction between devices, resulting in cumbersome operations , Increase the transmission overhead.

Summary of the invention

The embodiments of the present application provide a device activation method, terminal device, and computer storage medium, which can simplify operation procedures and save transmission overhead.

In the first aspect, an embodiment of the present application provides a device activation method, including:

The first device receives resource information sent by the second device, where the resource information includes the first owner transfer method supported by the second device, and the resource information further includes at least one of the following: Credential type, configuration mode supported by the second device, working status of the second device, and access authority information;

The first device sends a second owner transfer method and a client-led configuration mode for the second device configuration to the second device, and the second owner transfer method is the one in the first owner transfer method At least one method of owner transfer;

The first device performs a DTLS handshake with the second device according to the second owner transfer method to establish a secure connection;

The first device sends credential information to the second device through the secure connection, and the credential information includes the owner credential, the credential for AMS to access the second device, and the credential for CMS to access the second device, the The owner's credential is determined according to the type of credential supported by the second device, so that the management service sends to the second device the security resources required by the second device to interact with the third device. The device is an activated terminal device, and the management service includes the AMS and/or the CMS.

In the second aspect, an embodiment of the present application provides a device activation method, including:

The second device sends resource information to the first device, where the resource information includes the first owner transfer method supported by the second device, and the resource information further includes at least one of the following: credentials supported by the second device Type, the configuration mode supported by the second device, the working status of the second device, and access authority information;

Receiving, by the second device, a second owner transfer method and a client-led configuration mode sent by the first device, and the second owner transfer method is at least one owner transfer method among the first owner transfer methods;

The second device performs a DTLS handshake with the first device according to the second owner transfer method to establish a secure connection;

The second device receives the credential information sent by the first device through the secure connection, the credential information includes the owner credential, the credential for AMS to access the second device, and the credential for CMS to access the second device, so The owner's certificate is determined according to the type of certificate supported by the second device;

The second device receives a security resource that is required when interacting with a third device sent by a management service, the third device is an activated terminal device, and the management service includes the AMS and/or the CMS.

In a third aspect, an embodiment of the present application provides a first device that has a function of implementing the method described in the first aspect. The function can be realized by hardware, or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above-mentioned functions.

In a fourth aspect, an embodiment of the present application provides a first device, the first device includes a processor, and the processor is coupled with the memory, wherein:

The memory is used to store instructions;

The processor is configured to receive resource information sent by a second device, where the resource information includes a first owner transfer method supported by the second device, and the resource information further includes at least one of the following: the second The type of credential supported by the device, the configuration mode supported by the second device, the working status of the second device, and access authority information; and the second owner configured to the second device is sent to the second device Transfer method and client-led configuration mode, the second owner transfer method is at least one owner transfer method among the first owner transfer methods; performing DTLS with the second device according to the second owner transfer method Shaking hands to establish a secure connection; and sending credential information to the second device through the secure connection, the credential information including the owner credential, the credential for AMS to access the second device and the credential for CMS to access the second device , The owner's certificate is determined according to the type of certificate supported by the second device, so that the management service sends the second device to the second device the security resources needed when the second device interacts with the third device, so The third device is an activated terminal device, and the management service includes the AMS and/or the CMS.

In a fifth aspect, an embodiment of the present application provides a second device that has a function of implementing the method described in the second aspect. The function can be realized by hardware, or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above-mentioned functions.

In a sixth aspect, an embodiment of the present application provides a second device, the second device includes a processor, and the processor is coupled with the memory, wherein:

The memory is used to store instructions;

The processor is configured to send resource information to a first device, the resource information includes a first owner transfer method supported by the second device, and the resource information further includes at least one of the following: the second device Supported credential types, configuration modes supported by the second device, working status of the second device, and access authority information; receiving the second owner transfer method and client-led configuration sent by the first device Mode, the second owner transfer method is at least one owner transfer method among the first owner transfer methods; DTLS handshake with the first device is performed according to the second owner transfer method to establish a secure connection; receiving; The credential information sent by the first device via the secure connection, the credential information includes the owner’s credential, the AMS’s credential for accessing the second device and the CMS’s credential for accessing the second device, the owner’s credential is based on The type of credential supported by the second device is determined; and the security resource required to interact with a third device sent by the management service is received. The third device is an activated terminal device, and the management service includes the AMS and/or the CMS.

In a seventh aspect, an embodiment of the present application provides a computer storage medium, wherein the computer-readable storage medium stores a computer program or instruction, and when the program or instruction is executed by a processor, the processor executes The device activation method as described in the first aspect.

In an eighth aspect, the embodiments of the present application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause a computer to execute Part or all of the steps described in the first aspect of the application embodiment. The computer program product may be a software installation package.

In a ninth aspect, an embodiment of the present application provides a computer storage medium, wherein the computer-readable storage medium stores a computer program or instruction, and when the program or instruction is executed by a processor, the processor executes The device activation method as described in the second aspect.

In a tenth aspect, an embodiment of the present application provides a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause a computer to execute Part or all of the steps described in the second aspect of the application embodiment. The computer program product may be a software installation package.

It can be seen that in this embodiment of the application, the first device receives the resource information sent by the second device at one time, the resource information includes the first owner transfer method supported by the second device, and the resource information further includes at least one of the following: Supported credential types, configuration modes supported by the second device, working status of the second device, and access authority information. The first device sends to the second device the second owner transfer method and client for the second device configuration at one time In the dominant configuration mode, the first device performs a DTLS handshake with the second device according to the second owner transfer method to establish a secure connection, and then the first device sends the owner's credentials to the second device through the secure connection at a time, and AMS accesses the second device’s The voucher and the voucher for CMS to access the second device, so that the management service can send to the second device the security resources needed when the second device interacts with the third device. Batch processing can be carried out and the device activation process can be merged to simplify the operation process. Save transmission overhead.

Description of the drawings

The following will briefly introduce the drawings needed to be used in the description of the embodiments or the prior art.

FIG. 1 is a schematic diagram of the architecture of a communication system provided by an embodiment of the present application;

Figure 2 is a schematic diagram of a collection resource provided by an embodiment of the present application;

FIG. 3 is an example flowchart of a device activation method provided by an embodiment of the present application;

4 is a block diagram of the functional unit composition of a first device provided by an embodiment of the present application;

FIG. 5 is a schematic structural diagram of a first device provided by an embodiment of the present application;

FIG. 6 is a block diagram of a functional unit composition of a second device provided by an embodiment of the present application;

Fig. 7 is a schematic structural diagram of a second device provided by an embodiment of the present application.

detailed description

The technical solutions in the embodiments of the present application will be described below in conjunction with the accompanying drawings.

Fig. 1 shows a schematic diagram of the architecture of a communication system involved in the present application. The communication system may include a first device 101, a second device 102, a third device 103, and a management service 104. The first device 101 establishes a communication connection with the second device 102 and the management service 104 respectively, and the second device 102 respectively establishes a communication connection with the management service 104. 104 and the third device 103 establish a communication connection.

The first device 101 may be an activation tool (Onboarding Tool, OBT) device. For example, a legitimate user can use an Owner Transfer Method (Owner Transfer Method, OTM) through OBT devices to establish device ownership. After the device ownership is established, the second device 102 can be set to a normal operating state, for example, the second device 102 can be configured with an OBT device to authorize the management service 104. Exemplarily, the first device may be a client, specifically an entity that operates server resources.

The second device 102 may be a device to be activated. In the Internet of Things system defined by the Open Connectivity Foundation (OCF), devices need to be activated before they can operate in the network or interact with other activated devices. Based on this, the embodiments of this application will need to be activated The device is called the device to be activated. Exemplarily, the second device may be a server.

The third device 103 may be an activated device.

The management service 104 may include an access management service (Access Management Service, AMS), a security credential management service (Credential Management Service, CMS), or a device ownership transfer service (Device Ownership Transfer Service, DOTS). For example, the management service 104 can set the credentials and access permissions for the second device 102 to interact with the third device 103, and finally enable the second device 102 to operate normally and interact with the third device 103.

The traditional device activation method is: discover new terminal devices, execute owner transfer method, establish device identity, establish owner credential, assign device to management service, configure device management service, and prepare for interaction between devices. The execution sequence of the above operations It is fixed, and only one Security Virtual Resource (SVR) is operated at a time, which results in a cumbersome interaction process and high transmission overhead.

The present application provides a device activation method. The first device 101 can receive resource information sent by the second device 102, the resource information includes the first owner transfer method supported by the second device 102, and the resource information further includes at least one of the following: The credential type supported by the second device 102, the configuration mode supported by the second device 102, the working status of the second device 102, and the access authority information; the first device 101 sends to the second device 102 the configuration of the second device 102 The second owner transfer method and the client-led configuration mode, the second owner transfer method is at least one owner transfer method among the first owner transfer methods; the first device 101 performs data with the second device 102 according to the second owner transfer method The packet transport layer security protocol (Datagram Transport Layer Security, DTLS) handshake to establish a secure connection; the first device 101 sends credential information to the second device 102 through the secure connection. The credential information includes the owner’s credential. AMS accesses the second device 102. The credentials and the credentials for the CMS to access the second device 102. The owner's credentials are determined according to the type of credentials supported by the second device 102, so that the management service 104 sends to the second device 102 that the second device 102 interacts with the third device 103 The required security resources.

Compared with the traditional device activation method, this application can operate multiple SVRs at a time, that is, the device activation process is merged in batch processing, thereby simplifying the operation process and saving transmission overhead.

The SVR may include at least one of the following: owner transfer method, voucher type, configuration mode supported by the second device 102, working status of the second device 102, access authority information, client-led configuration mode, owner credential, AMS access section The credentials of the second device 102 and the credentials of the CMS to access the second device 102, as well as security resources, and so on. Specifically, the SVR may include "/oic/sec/doxm", "/oic/sec/pstat", "/oic/sec/cred", "/oic/sec/acl2" and other /oic/sec/obd resources. The "/oic/sec/doxm" resource is a resource defined by the OCF standard, which describes the ownership transfer method supported by the second device 102 and the currently used ownership transfer method. The "/oic/sec/pstat" resource is a resource defined by the OCF standard, which describes the configuration mode type supported by the second device 102 and the currently configured configuration mode. The "/oic/sec/cred" resource is a resource defined by the OCF standard, and describes the credential information required to access the second device 102. The "/oic/sec/acl2" resource is a resource defined by the OCF standard, which describes the access authority information of the second device 102 and so on.

In addition, in the embodiment of the present application, it is possible to obtain or set multiple SVRs at one time by using the "oic.if.b" interface to perform batch processing on the Collection resource. The Collection resource is described in detail below. Please refer to Figure 2. Figure 2 is a schematic diagram of Collection resources. Collection resources can include OCF Links. OCF Links represents a collection of one or more link resources. Multiple target resources or other Collection resources can be referenced through Collection resources. Taking Figure 2 as an example, a Collection resource contains the switch resources of device A (device identification is light) and the switch resources of device B (device identification is fan), forming a centralized resource group. The client can request multiple resources at the same time by accessing the oic.if.b interface of the Collection resource. The Collection resource handler will send the request to each resource in the links, and collect the response returned by each resource, and then return it in a unified manner. To the client.

Among them, the oic.if.b interface refers to an access interface used to access a batch of resources. For example, the second device may increase the /oic/sec/obd resource when it starts or enters the device ready OTM state (RFOTM). The /oic/sec/obd resource may include the /oic/sec/doxm resource, the /oic/sec/pstat resource, the /oic/sec/cred resource, and the /oic/sec/acl2 resource, etc. The /oic/sec/doxm resource can include the first owner transfer method supported by the second device, the /oic/sec/pstat resource can include the configuration mode supported by the second device, and the /oic/sec/cred resource can include the second The type of credential and credential information supported by the device, the /oic/sec/acl2 resource can include access authority information, etc. The first device can send a resource acquisition request to the second device through the oic.if.b interface that accesses the Collection resource, and the second device can use the Collection resource to convert the resource acquisition request into an owner transfer method acquisition request, configuration mode acquisition request, and voucher type Acquisition request and access permission acquisition request. Then, the second device may send the owner transfer method acquisition request to the /oic/sec/doxm resource through the Collection resource, and obtain the first owner transfer method supported by the second device from the /oic/sec/doxm resource. The second device may send the configuration mode acquisition request to the /oic/sec/pstat resource through the Collection resource, and obtain the configuration mode supported by the second device from the /oic/sec/pstat resource. The second device may send the credential type acquisition request to the /oic/sec/cred resource through the Collection resource, and obtain the credential type supported by the second device from the /oic/sec/cred resource. The second device may send the access permission acquisition request to the /oic/sec/acl2 resource through the Collection resource, and obtain the access permission information from the /oic/sec/acl2 resource. Then, the second device can package the first owner transfer method supported by the second device, the configuration mode supported by the second device, the credential type supported by the second device, and the access authority information through the collection resource to generate resource information. Then, the second device can send the resource information to the first device through the collection resource.

In view of the foregoing description, the embodiments of the present application propose the following embodiments, which are described in detail below with reference to the accompanying drawings.

Based on FIG. 1 and FIG. 2, please refer to FIG. 3. FIG. 3 is a device activation method provided by an embodiment of the present application, and the method includes:

S301. The second device sends resource information to the first device, the resource information includes the first owner transfer method supported by the second device, and the resource information further includes at least one of the following: a credential type supported by the second device, Supported configuration modes, working status of the second device, and access authority information.

In a specific implementation, the first device may receive the resource information sent by the second device in a GET manner on a user datagram protocol (User Datagram Protocol, UDP) unicast channel. For example, the first device can read /oic/sec/obd through GET on the UDP unicast channel? if=oic.if.b, the second device returns the owner transfer method supported by the second device, the credential type supported by the second device, the configuration mode supported by the second device, the current working status of the second device, and the default acl2( "Anon-clear" and "auth-crypt" type ace2). Data such as {...,"oxms":[0,1,2,...],"owned":FALSE,"sct":[1,2,4,8,16,32,...] ,"dos":{"s":1,"p":FALSE},"sm":0bXXXX,X1XX,...}.

Wherein, the owner transfer method supported by the second device may include at least one of the following: a simple (Just-works) method, a personal identification number (Personal Identification Number, PIN) method, a certificate method, and a manufacturer-defined method.

Wherein, the voucher type supported by the second device may include symmetric voucher and/or asymmetric voucher. For example, a symmetric certificate may include a pair of symmetric keys or a group of symmetric keys. Asymmetric credentials can include certificates or original asymmetric keys.

Wherein, the configuration mode supported by the second device may include at least one of the following: a client-led configuration mode, a server-led and utilized a single configuration service, and a server-led and utilized multiple configuration services.

Device configuration can be client-led or server-led. The client-led configuration relies on the client device to determine what, how, and when server-side resources should be instantiated and updated. The server-led configuration depends on the server seeking configuration when the conditions are specified. The server-led configuration relies on the configuration of the "rowneruuid" attribute in the "/oic/sec/doxm", "/oic/sec/cred" and "/oic/sec/acl2" resources to indicate the trusted DOTS respectively , CMS and AMS service device ID. Further, "/oic/sec/cred" should be configured with necessary credentials when the owner transfers it to establish a secure connection with appropriate supporting services.

The configuration status resource "/oic/sec/pstat" is used to enable the second device to perform self-directed configuration. The second device knows its current configuration state and target configuration object. If there is a difference between the current and target states, the second device should query the "rowneruuid" attribute of the "/oic/sec/cred" resource to find out whether there is any suitable configuration service. If it is set to active, the second device should request configuration. The om attribute of the "/oic/sec/pstat" resource will specify the expected device behavior under these conditions.

In the embodiments of the present application, the self-directed configuration enables the device to operate with greater autonomy, so as to minimize the dependence on the central configuration organization and prevent it from becoming a single point of failure in the network.

The current working state of the second device may be RFOTM, device ready for configuration state (RFPRO), device ready for normal operation state (RFNOP), device reset state (RESET), or device soft reset state (SRESET).

The platform manufacturer should provide a physical mechanism (such as a button) to force the platform to reset. All devices carried on the same platform change the state of the second device to RESET when the platform is reset. When the device status is RESET, all SVR content is deleted and reset to the manufacturer's default value. The default manufacturer's device status is RESET. After successfully executing the RESET, the SRM transitions to the RFOTM state by setting the "s" attribute of the "/oic/sec/dostype" resource to RFOTM.

The second device in the RFOTM state refers to an operable device that is ready for ownership transfer. When the device status is RFOTM, before OTM is successful, set the deviceuuid attribute of the "/oic/sec/doxm" resource to a temporary non-repeated value. Before OTM is successful, the "s" attribute of the "/oic/sec/dostype" resource is read-only for unauthenticated requesters. After OTM is successful, the "s" attribute of the "/oic/sec/dostype" resource is readable and writable for the authorized requester. The negotiated device owner credential (Owner Credential, OC) is used to create an authenticated session, and the DOTS will instruct the device state to switch to RFPRO through the session. If an authenticated session cannot be created, the ownership transfer session should be disconnected, and the Secure Resource Manager (SRM) will set the device state back to the RESET state. The ownership transfer session should not exceed 60 seconds, otherwise SRM will declare OTM failure, disconnect and switch to the RESET state (/pstat.dos.s=RESET). DOTS changes the "devowneruuid" attribute of the "/doxm" resource to a non-zero UUID value. In the RFOTM state, DOTS (or other authorized clients) can change the value multiple times. The state of other equipment cannot be changed unless the state of the equipment returns to RFOTM from RESET. DOTS may need to perform other configuration tasks in the RFOTM state. After completion, DOTS changes the "owned" attribute of the "/doxm" resource to "true".

RFPRO means that the second device is ready for other configurations. When the device status is RFPRO, the "s" attribute of the "/oic/sec/dostype" resource is read-only for unauthorized requesters and readable and writable for authorized requesters. Authorized clients can configure SVR according to the requirements of the normal operation of RFNOP. Authorized clients can perform a consistency check on the SVR to determine which should be reconfigured. Unsuccessful configuration of SVR may trigger the status change to RESET. For example, if the device has been converted from SRESET, but the consistency check continues to fail. Authorize the client to set /pstat.dos.s=RFNOP.

RFNOP refers to the final state of the second device that is an operable device. When the device status is RFNOP, the "/pstat.dos.s" attribute is read-only for unauthorized requesters and readable and writable for authorized requesters. With normal access procedures, SVRs and core resources can be accessed. The authorized client can convert the device to RFPRO. Only the device owner can switch the device to SRESET or RESET.

SRESET means that the second device is inoperable but still owned by the current owner. When the device status is SRESET, SVR integrity cannot be guaranteed, but it is necessary to access certain SVR attributes. These include the devowneruuid attribute of the "/oic/sec/doxm" resource, the "creds": [{...,{"subjectuuid":<devowneruuid>},...}] attribute of the "/oic/sec/cred" resource and the "/ The "s" attribute of the "/oic/sec/dostype" resource of the "oic/sec/pstat" resource. The certificate for identifying and authorizing the device owner is sufficient to recreate the minimum required "/cred" and "/doxm" resources so that the device owner can control SRESET. If SRM cannot establish these resources, it will transition to the RESET state. Authorize the client to perform SVR consistency checks. It can provide SVRs as needed to ensure that they are available in the continuous configuration of RFPRO or when RFNOP is operating normally. Authorized device owners can avoid entering the RESET and RFOTM states by writing RFPRO or RFNOP into the "dos.s" attribute of the "/pstat" resource. ACLs on SVR are considered invalid. Only the device owner can access it. SRM declares the client-led work mode (for example, /pstat.om=CLIENT_DIRECTED).

In this embodiment, the first device acquires the resources that need to be acquired multiple times in the traditional device activation method at one time, which simplifies the operation process and saves transmission overhead.

In an implementation manner, before the second device sends the resource information to the first device, the first device may discover the device to be activated, that is, the second device. After the first device discovers the second device, it receives the resource information sent by the second device.

In an implementation manner, before the second device sends the resource information to the first device, the second device may generate the resource information when detecting that the operating state of the second device is updated to the RFOTM state.

In this embodiment, the /oic/sec/obd resource is automatically added when the second device enters the RFOTM state. The /oic/sec/obd resource is a Collection resource (ie "oic.wk.col" type), which refers to the following target resources (for example, /oic/sec/doxm, /oic/sec/pstat, /oic/sec/cred, /oic/sec/acl2), the /oic/sec/obd resource supports the "oic.if.b" interface. In this embodiment of the application, the device activation process can be implemented by performing an "oic.if.b" interface operation on the /oic/sec/obd resource.

In an implementation manner, before the second device sends the resource information to the first device, the second device generates the resource information when detecting that the second device is in a running state.

In this embodiment, the second device automatically generates the /oic/sec/obd resource when it is started.

In an implementation manner, the second device deletes the resource information when detecting that the operating state of the second device is updated to the RFNOP state or the RESET state.

In this embodiment, when the second device enters the RFNOP or RESET state, the /oic/sec/obd resource can be automatically deleted.

In an implementation manner, after the resource information is generated by the second device, the resource information may not be deleted. For example, after the second device generates the /oic/sec/obd resource, the /oic/sec/obd resource may not be deleted, but the owner's Universally Unique Identifier (UUID) of the resource may be set as the device owner's UUID .

S302: The first device sends to the second device the second owner transfer method for the configuration of the second device and the client-led configuration mode.

Wherein, the second owner transfer method is at least one owner transfer method among the first owner transfer methods.

In an implementation manner, the first device may send the second owner transfer method for the configuration of the second device and the client-led configuration mode to the second device in a POST manner on the UDP unicast channel.

In this embodiment, the first device can write /oic/sec/obd? via POST on the UDP unicast channel. if=oic.if.b, tell the second device to use oic.sec.oxm.jw to return the owner transfer method and the client-led configuration mode. If the second device successfully receives the second owner transfer method and the client-led configuration mode sent by the first device, the second device may send a success indication message to the first device. If the second device does not successfully receive the second owner transfer method and the client-led configuration mode sent by the first device, the second device can send a failure indication message to the first device, such as {"msg":"The model is not supported","ec":2101}.

In this embodiment, the first device sends the resources that need to be sent multiple times in the traditional device activation method to the second device at one time, which can simplify the operation process and save transmission overhead.

In specific implementation, the first device configures the second owner transfer method for the second device, which can realize the establishment of device ownership. The goal of establishing device ownership is to allow legitimate users who own or purchase the second device to become the owner and administrator of the second device. This process includes using OBT to establish ownership information between the second device and the first device, and to control and manage the second device. OBT is a logical entity running on the second device or the first device, such as a network management console, device management tool, network monitoring tool, network configuration tool, home gateway or home automation controller. The physical device running OBT should meet some security reinforcement requirements, and use integrity and confidentiality protection for the stored credentials. The tool or server that establishes ownership is often referred to as OBT. The "owner transfer" is used here because even for a new device, its ownership is transferred from the manufacturer to the purchaser.

S303: The first device performs a DTLS handshake with the second device according to the second owner transfer method to establish a secure connection.

In specific implementation, the first device can execute Just-Works OTM for DTLS handshake to establish a secure connection.

S304: The first device sends the credential information to the second device through the secure connection.

The credential information may include the owner's credential, the credential for the AMS to access the second device and the credential for the CMS to access the second device, and the owner's credential is determined according to the type of credential supported by the second device.

In an implementation manner, the first device may send the credential information to the second device through a POST method and a secure connection on a UDP unicast channel.

In this embodiment, the first device can write /oic/sec/obd? via POST on the UDP unicast channel. if=oic.if.b, the first device sets the owner UUID of the second device on the DTLS secure connection, resource owner UUID, device persistent UUID, owner certificate, CMS certificate and AMS certificate. The owner's certificate may be composed of a certificate signed by the first device or other organization, user network access information, shared key, and so on.

In one implementation, after the second device receives the credential information sent by the first device through the secure connection, if the second device successfully updates the data according to the credential information, the second device can update the operating status of the second device to the RFPRO state , The second device sends a first feedback message to the first device, and the first feedback message is used to indicate that the second device successfully updates the data.

Wherein, the first feedback message may include the updated owner UUID and the device persistent UUID.

For example, if the second device successfully updates the data, it will automatically modify doxm to "owned=true" and enter the RFPRO state, and then the second device will send a first feedback message to the first device. The first feedback message is used to indicate the first device. Second, the device successfully updated the data. If the second device fails to update the data, the second device sends a failure indication message to the first device.

In one implementation, before the second device updates the operating status of the second device to the RFPRO state, when the second device accesses the owner UUID, resource owner UUID, owner's credentials, CMS's credentials for accessing the second device, and AMS access When the credentials of the second device are all updated successfully, the second device determines that the data update is successful.

In one implementation, after the second device receives the credential information sent by the first device through the secure connection, if the second device fails to update data according to the credential information, the second device sends a second feedback message to the first device, and the second device sends a second feedback message to the first device. The feedback message is used to indicate that the second device fails to update the data.

For example, if the second device fails to update the owner UUID, or fails to update the resource owner UUID, or fails to update the owner credential, or fails to update the CMS credential, or fails to update the AMS credential, the second device sends a second feedback to the first device Message, such as {"msg":"Internal Server operation error", "ec":2000}.

In one implementation, after the second device receives the credential information sent by the first device through the secure connection, if the second device does not support updating the device persistent UUID, the second device sends the device persistent UUID stored in the second device to the first device. UUID.

In an implementation manner, after the second device receives the credential information sent by the first device through the secure connection, if the second device fails to update the device's persistent UUID, the second device sends a second feedback message to the first device, and the second device sends a second feedback message to the first device. The feedback message is used to indicate that the second device fails to update the data.

For example, if the second device supports updating the device's persistent UUID and the second device fails to update the device's persistent UUID, the second device sends a second feedback message to the first device, such as {"msg":"Invalid parameter","ec":1100}.

S305: The management service sends to the second device the security resources required when the second device interacts with the third device.

In an implementation manner, after the management service sends the security resources required by the second device to interact with the third device to the second device, the first device may close the DTLS connection.

In the embodiment of the present application, the first device receives the resource information sent by the second device at one time, the resource information includes the first owner transfer method supported by the second device, and the resource information further includes at least one of the following: The type of credential, the configuration mode supported by the second device, the working status of the second device, and the access authority information, the first device sends to the second device the second owner transfer method and client-led configuration of the second device at one time In configuration mode, the first device performs a DTLS handshake with the second device according to the second owner transfer method to establish a secure connection, and then the first device sends the owner's credentials to the second device through the secure connection at one time, and the AMS accesses the credentials of the second device and CMS accesses the credentials of the second device, so that the management service can send the security resources required by the second device to the third device when the second device interacts with the third device. Batch processing can be carried out and the device activation process can be merged, thereby simplifying the operation process and saving transmission Overhead.

The foregoing mainly introduces the solution of the embodiment of the present application from the perspective of interaction between various network elements. It can be understood that, in order to implement the above-mentioned functions, the terminal device includes a hardware structure and/or software module corresponding to each function. Those skilled in the art should easily realize that in combination with the units and algorithm steps of the examples described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.

The embodiment of the present application may divide the terminal device into functional units according to the foregoing method examples. For example, each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit. The above-mentioned integrated unit can be realized in the form of hardware or software program module. It should be noted that the division of units in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.

In the case of an integrated unit, FIG. 4 shows a block diagram of a possible functional unit composition of the first device involved in the foregoing embodiment, and the first device includes:

The communication unit 401 is configured to receive resource information sent by a second device, where the resource information includes the first owner transfer method supported by the second device, and the resource information further includes at least one of the following: the second device Supported credential types, configuration modes supported by the second device, working status of the second device, and access authority information.

The communication unit 401 is further configured to send a second owner transfer method configured to the second device and a client-led configuration mode to the second device, and the second owner transfer method is the first owner transfer method At least one of the owner’s transfer methods.

The processing unit 402 is configured to perform a DTLS handshake with the second device according to the second owner transfer method to establish a secure connection.

The communication unit 401 is further configured to send credential information to the second device through the secure connection, the credential information including the owner's credential, the credential for AMS to access the second device and the credential for CMS to access the second device, The owner credential is determined according to the credential type supported by the second device, so that the management service sends to the second device the security resources required by the second device to interact with the third device. The third device is an activated terminal device, and the management service includes the AMS and/or the CMS.

The processing unit 402 may be a processor or a controller, and the communication unit 401 may be a transceiver, a transceiver circuit, a radio frequency chip, or the like.

In an implementation manner, the receiving of the resource information sent by the second device by the communication unit 401 includes:

The resource information sent by the second device is received in a GET manner on the UDP unicast channel.

In an implementation manner, the communication unit 401 sending the second owner transfer method for the second device configuration and the client-led configuration mode to the second device includes:

The second owner transfer method and the client-led configuration mode of the configuration of the second device are sent to the second device through the POST method on the UDP unicast channel.

In an implementation manner, the communication unit 401 sending credential information to the second device through the secure connection includes:

The credential information is sent to the second device through the POST mode and the secure connection on the UDP unicast channel.

When the processing unit 402 is a processor and the communication unit 401 is a communication interface, the terminal device involved in the embodiment of the present application may be the first device shown in FIG. 5.

It should be noted that the first device shown in FIG. 4 and FIG. 5 may be used to implement the steps performed by the first device in the above-mentioned embodiment, which will not be repeated in this embodiment of the application.

In the embodiment of the present application, the communication unit 1001 receives the resource information sent by the second device, and sends the second owner transfer method and the client-led configuration mode for the second device configuration to the second device, and the processing unit 1002 according to the second owner The transfer method performs a DTLS handshake with the second device to establish a secure connection. The communication unit 1001 sends credential information to the second device through the secure connection, so that the management service sends the second device to the second device when the second device interacts with the third device. Safe resources can simplify the operation process and save transmission overhead.

In the case of an integrated unit, FIG. 6 shows a block diagram of a possible functional unit composition of the second device involved in the foregoing embodiment, and the first device includes:

The communication unit 601 is configured to send resource information to a first device, where the resource information includes the first owner transfer method supported by the second device, and the resource information further includes at least one of the following: Supported credential types, configuration modes supported by the second device, working status of the second device, and access authority information.

The communication unit 601 is further configured to receive a second owner transfer method and a client-led configuration mode sent by the first device, and the second owner transfer method is at least one owner transfer method among the first owner transfer methods method.

The processing unit 602 is configured to perform a DTLS handshake with the first device according to the second owner transfer method to establish a secure connection.

The communication unit 601 is further configured to receive credential information sent by the first device via the secure connection, the credential information includes owner credential, AMS credential for accessing the second device, and CMS credential for accessing the second device , The owner credential is determined according to the credential type supported by the second device.

The communication unit 601 is further configured to receive security resources required when interacting with a third device sent by a management service, where the third device is an activated terminal device, and the management service includes the AMS and/or the CMS.

The processing unit 602 may be a processor or a controller, and the communication unit 601 may be a transceiver, a transceiver circuit, a radio frequency chip, or the like.

In an implementation manner, after the communication unit 601 receives the credential information sent by the first device through the secure connection, the method further includes:

If the second device successfully updates the data according to the credential information, the processing unit 602 updates the operating status of the second device to the device ready to configure RFPRO status;

The communication unit 601 sends a first feedback message to the first device, where the first feedback message is used to indicate that the second device successfully updates data.

In an implementation manner, the first feedback message includes the updated owner UUID and the device persistent UUID.

In an implementation manner, before the processing unit 602 updates the operating state of the second device to the RFPRO state, the method further includes:

When the second device successfully updates the owner UUID, resource owner UUID, owner credential, the credential for CMS to access the second device, and the credential for AMS to access the second device, the processing unit 602 determines that the data update is successful .

If the second device fails to update data according to the credential information, the communication unit 601 sends a second feedback message to the first device, where the second feedback message is used to indicate that the second device fails to update data .

If the second device does not support updating the device persistent UUID, the communication unit 601 sends the device persistent UUID stored by the second device to the first device.

If the second device-to-device persistent UUID update fails, the communication unit 601 sends a second feedback message to the first device, where the second feedback message is used to indicate that the second device fails to update data.

In an implementation manner, before the communication unit 601 sends resource information to the first device, the method further includes:

The processing unit 602 generates the resource information when detecting that the operating status of the second device is updated to the OTM or RFOTM ready state of the device.

The processing unit 602 generates the resource information when detecting that the second device is in a running state.

The processing unit 602 is further configured to delete the resource information when it is detected that the operating state of the second device is updated to the RFNOP state or RESET.

When the processing unit 602 is a processor and the communication unit 601 is a communication interface, the second device involved in the embodiment of the present application may be the second device shown in FIG. 7.

It should be noted that the second device shown in FIG. 6 and FIG. 7 may be used to implement the steps performed by the second device in the above-mentioned embodiment, which will not be repeated in this embodiment of the application.

In the embodiment of the present application, the communication unit 1001 sends resource information to the first device, and receives the second owner transfer method and the client-led configuration mode sent by the first device, and the processing unit 1002 communicates with the second device according to the second owner transfer method Perform a DTLS handshake to establish a secure connection. The communication unit 1001 receives the credential information sent by the first device through the secure connection, and receives the security resources required to interact with the third device from the management service, which simplifies the operation process and saves transmission. Overhead.

The embodiment of the present application also provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program for electronic data exchange, wherein the computer program causes the computer to execute the method as described in the above method embodiment. Part or all of the steps described by a device.

The embodiments of the present application also provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause a computer to execute the method embodiments described above. Part or all of the steps described in the first device. The computer program product may be a software installation package.

The embodiment of the present application also provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program for electronic data exchange, wherein the computer program causes the computer to execute the method as described in the above method embodiment. 2. Part or all of the steps described in the device.

The embodiments of the present application also provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause a computer to execute the method embodiments described above. Part or all of the steps described in the second device. The computer program product may be a software installation package.

The steps of the method or algorithm described in the embodiments of the present application may be implemented in a hardware manner, or may be implemented in a manner in which a processor executes software instructions. Software instructions can be composed of corresponding software modules, which can be stored in random access memory (Random Access Memory, RAM), flash memory, read-only memory (Read Only Memory, ROM), and erasable programmable read-only memory ( Erasable Programmable ROM (EPROM), Electrically Erasable Programmable Read-Only Memory (Electrically EPROM, EEPROM), registers, hard disk, mobile hard disk, CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor, so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium may also be an integral part of the processor. The processor and the storage medium may be located in the ASIC. In addition, the ASIC may be located in an access network device, a target network device, or a core network device. Of course, the processor and the storage medium may also exist as discrete components in the access network device, the target network device, or the core network device.

Those skilled in the art should be aware that, in one or more of the foregoing examples, the functions described in the embodiments of the present application may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented by software, it can be implemented in the form of a computer program product in whole or in part. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center. Transmission to another website, computer, server or data center via wired (such as coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrated with one or more available media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a digital video disc (Digital Video Disc, DVD)), or a semiconductor medium (for example, a solid state disk (Solid State Disk, SSD)) )Wait.

The specific implementations described above further describe the purpose, technical solutions, and beneficial effects of the embodiments of the application in detail. It should be understood that the foregoing descriptions are only specific implementations of the embodiments of the application, and are not used for To limit the protection scope of the embodiments of the application, any modification, equivalent replacement, improvement, etc. made on the basis of the technical solutions of the embodiments of the application shall be included in the protection scope of the embodiments of the application.

Claims

A device activation method, characterized in that it includes:

The first device receives resource information sent by the second device, where the resource information includes the first owner transfer method supported by the second device, and the resource information further includes at least one of the following: Credential type, configuration mode supported by the second device, working status of the second device, and access authority information;

The first device sends a second owner transfer method and a client-led configuration mode for the second device configuration to the second device, and the second owner transfer method is the one in the first owner transfer method At least one method of owner transfer;

The first device performs a data packet transport layer security protocol DTLS handshake with the second device according to the second owner transfer method to establish a secure connection;

The first device sends credential information to the second device through the secure connection, the credential information includes the owner credential, the credential for the access management service AMS to access the second device, and the security credential management service CMS accesses the second device. The certificate of the second device, the owner certificate is determined according to the certificate type supported by the second device, so that the management service sends the second device to the second device when the second device interacts with the third device A security resource, the third device is an activated terminal device, and the management service includes the AMS and/or the CMS.
The method according to claim 1, wherein the receiving, by the first device, the resource information sent by the second device, comprises:

The first device receives the resource information sent by the second device in a GET manner on a user datagram protocol UDP unicast channel.
The method according to claim 1, wherein the sending, by the first device to the second device, a second owner transfer method for configuration of the second device and a client-led configuration mode comprises:

The first device sends the second owner transfer method and the client-led configuration mode for the second device configuration to the second device in a POST manner on the UDP unicast channel.
The method according to claim 1, wherein the first device sending credential information to the second device through the secure connection comprises:

The first device sends the credential information to the second device through the POST method and the secure connection on the UDP unicast channel.
A device activation method, characterized in that it includes:

The second device sends resource information to the first device, where the resource information includes the first owner transfer method supported by the second device, and the resource information further includes at least one of the following: credentials supported by the second device Type, the configuration mode supported by the second device, the working status of the second device, and access authority information;

Receiving, by the second device, a second owner transfer method and a client-led configuration mode sent by the first device, and the second owner transfer method is at least one owner transfer method among the first owner transfer methods;

The second device performs a data packet transport layer security protocol DTLS handshake with the first device according to the second owner transfer method to establish a secure connection;

The second device receives the credential information sent by the first device through the secure connection, the credential information includes the owner credential, the credential for the access management service AMS to access the second device, and the security credential management service CMS accesses the credential The certificate of the second device, where the owner certificate is determined according to the certificate type supported by the second device;

The second device receives a security resource that is required when interacting with a third device sent by a management service, the third device is an activated terminal device, and the management service includes the AMS and/or the CMS.
The method according to claim 5, wherein after the second device receives the credential information sent by the first device through the secure connection, the method further comprises:

If the second device successfully updates the data according to the credential information, the second device updates the operating state of the second device to the device ready to configure RFPRO state;

The second device sends a first feedback message to the first device, where the first feedback message is used to indicate that the second device successfully updates data.
7. The method according to claim 6, wherein the first feedback message includes the updated owner's universal unique identification code UUID and the device persistent UUID.
The method according to claim 6, wherein before the second device updates the operating state of the second device to the RFPRO state, the method further comprises:

When the second device successfully updates the owner's UUID, resource owner's UUID, owner's credential, CMS's credential for accessing the second device, and AMS's credential for accessing the second device, the second device determines that the data update is successful .
The method according to claim 5, wherein after the second device receives the credential information sent by the first device through the secure connection, the method further comprises:

If the second device fails to update data according to the credential information, the second device sends a second feedback message to the first device, where the second feedback message is used to indicate that the second device fails to update data .
The method according to claim 5, wherein after the second device receives the credential information sent by the first device through the secure connection, the method further comprises:

If the second device does not support updating the device persistent UUID, the second device sends the device persistent UUID stored by the second device to the first device.
The method according to claim 5, wherein after the second device receives the credential information sent by the first device through the secure connection, the method further comprises:

If the second device-to-device persistent UUID update fails, the second device sends a second feedback message to the first device, where the second feedback message is used to indicate that the second device fails to update data.
The method according to claim 5, wherein before the second device sends the resource information to the first device, the method further comprises:

The second device generates the resource information when detecting that the operating state of the second device is updated to the device ready for the owner transfer method RFOTM state.
The method according to claim 5, wherein before the second device sends the resource information to the first device, the method further comprises:

The second device generates the resource information when detecting that the second device is in a running state.
The method of claim 5, wherein the method further comprises:

The second device deletes the resource information when detecting that the operating state of the second device is updated to the device ready for normal operation RFNOP state or device reset state RESET.
A first device, characterized in that the first device includes a unit for implementing the device activation method according to any one of claims 1-4.
A first device, characterized in that the first device includes a processor and a memory, the processor is coupled with the memory, and is characterized in that:

The memory is used to store instructions;

The processor is configured to receive resource information sent by a second device, where the resource information includes a first owner transfer method supported by the second device, and the resource information further includes at least one of the following: the second The type of credential supported by the device, the configuration mode supported by the second device, the working status of the second device, and access authority information; and the second owner configured to the second device is sent to the second device Transfer method and client-led configuration mode, the second owner transfer method is at least one owner transfer method among the first owner transfer methods; and data is performed with the second device according to the second owner transfer method The packet transport layer security protocol DTLS handshake to establish a secure connection; and the credential information is sent to the second device through the secure connection, the credential information includes the owner's credential, and the credential for the access management service AMS to access the second device And the security credential management service CMS to access the credential of the second device, the owner credential is determined according to the credential type supported by the second device, so that the management service sends the second device to the second device A security resource required when interacting with a third device, the third device is an activated terminal device, and the management service includes the AMS and/or the CMS.
A second device, characterized in that the second device includes a unit for implementing the device activation method according to any one of claims 5-14.
A second device, characterized in that, the second device includes a processor and a memory, and the processor is coupled with the memory, and is characterized in that:

The memory is used to store instructions;

The processor is configured to send resource information to a first device, the resource information includes a first owner transfer method supported by the second device, and the resource information further includes at least one of the following: the second device Supported credential types, configuration modes supported by the second device, working status of the second device, and access authority information; receiving the second owner transfer method and client-led configuration sent by the first device Mode, the second owner transfer method is at least one owner transfer method among the first owner transfer methods; the data packet transport layer security protocol DTLS handshake is performed with the first device according to the second owner transfer method , To establish a secure connection; receiving the credential information sent by the first device through the secure connection, the credential information including the owner credential, the credential for the access management service AMS to access the second device, and the credential management service CMS access to the security credential management service The credentials of the second device, the owner's credentials are determined according to the type of credentials supported by the second device; and the security resources required to interact with the third device sent by the management service are received, the third device For an activated terminal device, the management service includes the AMS and/or the CMS.
A computer storage medium, wherein the computer storage medium stores a computer program or instruction, and when the program or instruction is executed by a processor, the processor executes any one of claims 1-4 The described device activation method.
A computer storage medium, wherein the computer storage medium stores a computer program or instruction, and when the program or instruction is executed by a processor, the processor executes any one of claims 5-14 The described device activation method.