Method and system for managing device identification

The present disclosure provides a method and a system for managing the identification of devices (DID). A network device may provide the network device information to a server through a network. The server may generate a DID corresponding to the network device, and record the DID and the network device information into a device database. In addition, the network device and the server may share a shared key, which may be used to encrypt the DID and the network device information before the data transmission for enhancing security of the method. Moreover, the server may generate and record an exclusive key (Device Key) for data encryption before the data transmission with the network device, and transmit the Device Key to the network device. Therefore, the Device Key management may be accomplished simultaneously with the DID management to enhance data transmission security between the network device and the server.

FIELD OF THE INVENTION

The present invention relates generally to a device identification (ID) management method and system applied to the management of network device IDs. The device ID management method and system may be further applied to the management of device key used for data encrypting at the network device.

BACKGROUND OF THE INVENTION

Generally, for management purposes, electronic devices sold on the market, such as computers, home appliances and consumer electronic products, are designated a unique device identification (device ID) before they leave the factory. The device ID will be stored in the firmware of the device. In addition, the device ID and other information of each device leaving the factory will be recorded in the device database to record, query and track such device. The device ID and other information stored in the device database may be used to determine whether the device is lawfully acquired. Services such as maintenance, warranty and/or update may be provided to the devices lawfully purchased. Moreover, such service may be provided through the Internet if a server verifies, through the device ID stored in the device database, that the device is lawfully acquired.

FIG. 1Aillustrates an exemplary prior art reference of a device ID management system. The first network device100comprises a first storage module110, and the second network device200comprises a second storage module210. The first storage module110stores a first device ID111and a first device information112, and the second storage module210stores a second device ID211and a second device information212. The first network device100and the second network device200may communicate with a server300through the Internet, and the server300may access the device database400. In addition, as illustrated by the device database log data410, the first device ID111, the first device information112, the second device ID211and the second device information212are stored in the device database400before the first network device100and the second network device200leave the factory. In the prior art reference, the first network device100and the second network device200may transmit the first device ID111and the second device ID211to the server300respectively. In addition, the first network device100and the second network device200may request the server300to provide service, such as maintenance or update, through the Internet. The server may look up the first network device100and the second network device200in the device database400according to the first device ID111and the second device ID211, and determine whether the first network device100and the second network device200have authorization based on the device database log data410. If the first network device100and/or the second network device200possess authorization, the sever300may provide services to the first network device100and/or the second network device200through the Internet. Alternatively, the first network device100and the second network device200may transmit the first device ID111, the first device information112and the second device ID211, the second device information212to the server300respectively, and request the server300to update the device information. Accordingly, the server300may look up the first network device100and the second network device200in the device database400based on the first device ID111and the second device ID211. Moreover, the server300may update the device database log data410according to the first device information112and the second device information212received.

However, device ID management system disclosed in the prior art reference may require the aforementioned device ID and the device information be stored in the device database before the network device leaves the factory. As a result, the log data in the device database may not be updated dynamically and device management becomes complicated and inflexible. For example, when the network device leaves the factory but remains unsold or unactivated, device management may not be necessary, and thus building a device database to maintain the device information may not be necessary. In addition, when a network device is reset by a user, the corresponding device ID of such network device may need to be retrieved from the device database and the corresponding device information may need to be updated. Therefore, there is a need in the art for a device ID management method and system to more conveniently and securely manage the device ID of the network devices. Such management method and system may also be implemented when a network device is reset.

BRIEF SUMMARY OF THE INVENTION

In one embodiment, a method for managing network device ID so as to provide more management flexibility is disclosed. The network device may include a desktop computer, a laptop computer, a tablet computer, a smart phone, a personal digital assistant (PDA), a network-attached storage (NAS), a router, a gateway or any device with internet connectivity. The management method may provide transmitting the device information of the network device to the server through the Internet. The device information may include hardware information such as model number and brand name, and software/firmware information such as software/firmware version, and network information such as network address. The server may generate an unique device ID according to the device information and transmit the device information and the device ID to the device database. The server may further transmit the device ID to the network device to be stored or registered. As a result, a device ID may be automatically designated to a network device after such network device leaves the factory and is activated. In addition, the corresponding device information may be transmitted and registered in the device database. Thereafter, when the network device is reset, a new device ID may be generated by the server and the corresponding device information may be registered in the device database, according to the device ID management method of the present disclosure. Accordingly, the network device being reset may not need to be retrieved in the device database, and corresponding device information may not need to be deleted before a new device information is generated.

In another embodiment, a shared device key may be pre-stored in the network device and the server. The shared device key may enhance the security of the device ID management method of the present disclosure. For example, the device information may be encrypted based on the shared device key before the network device transmits the device information. The server may decrypt the device information based on the shared device key after the server receives the device information. Similarly, the device ID may be encrypted based on the shared device key before the server transmits the device ID. The network device may decrypt the device ID based on the shared device key after the network device receives the device ID. In addition, the server may generate an unique device key for a network device, store the device key in the device database, and transmit the device key to the network device along with the device ID. The network device and the server may encrypt and decrypt the data transmitted between the network device and the server based on the device key after the device ID is designated and the device information is registered. Therefore, the device keys may be managed simultaneously with the management of the device ID to enhance the security of data transmission between a network device and a server.

In yet another embodiment, a second network device may encrypt the device information based on the shared device key and transmit the device information to the first network device. An exemplary second network device may be a terminal device such as a desktop computer, a laptop computer, a tablet computer, a smart phone, a personal digital assistant (PDA) or a network-attached storage (NAS). An exemplary first network device may be an internet device such as a router or a gateway. Consequently, after decrypting the device information based on the shared device key, the first network device may encrypt the device information based on the first device key and transmit the device information to the server. After decrypting the device information based on the first device key, the server may generate an unique second device ID and an unique second device key of the second network device according to the second device information. The server may encrypt based on the first device key and transmit the second device ID, the second device key and the first device key to the first network device. After decrypting the second device ID and the second device key based on the first device key, the first network device may encrypt the second device ID and the second device key based on the shared device key and transmit the second device ID and the second device key to the second network device. Thereafter, the second may acquire and decrypt the second device ID and the second device key based on the shared device key. Therefore, through encrypting the data transmission between the second network device and the server by the first network device, which has already acquired the first device ID and the first device key, the security of the data transmission between the server and the network device in the device ID management method may be enhanced.

In accordance with common practice, the various described features are not drawn to scale and are drawn to emphasize features relevant to the present disclosure. Like reference characters denote like elements throughout the figures and text.

DETAILED DESCRIPTION OF THE INVENTION

It will be understood that, although the terms first, second, third etc. may be used herein to describe various elements, components, regions, parts and/or sections, these elements, components, regions, parts and/or sections should not be limited by these terms. These terms are only used to distinguish one element, component, region, part or section from another element, component, region, layer or section. Thus, a first element, component, region, part or section discussed below could be termed a second element, component, region, layer or section without departing from the teachings of the present invention.

The description will be made as to the embodiments of the present invention in conjunction with the accompanying drawings inFIGS. 1A-3H. Reference will be made to the drawing figures to describe the present invention in detail, wherein depicted elements are not necessarily shown to scale and wherein like or similar elements are designated by same or similar reference numeral through the several views and same or similar terminology. In accordance with the purposes of this invention, as embodied and broadly described herein, this invention,

FIG. 1Ais a schematic illustration of a system for managing device ID disclosed in the prior art reference, as described in the background section, and thus will not be repeated herein.FIGS. 1B-1Gare block diagrams of the system for managing device ID according to some embodiments of the present invention.

FIGS. 1B and 1Cin combination illustrate one embodiment of a system implementing the device ID management method of the present invention. Specifically,FIG. 1Bis an illustration of the system for managing device ID having a first network device100, a server300and a device database400communicative with one another. The server300may access the device database400, and the device database400may store the device IDs and the device information. The first network device100may be a computing device with internet connectivity such as a desktop computer, a laptop computer or a tablet computer, or a handheld device such as a smart phone or a personal digital assistant (PDA). In addition, the first network device100may be a network device such as a modem, a gateway, a router, a access point, a hot spot or a femtocell, or a network equipment such as a network-attached storage (NAS), a firewall, a workstation or a proxy server. The first network device may further be any device having an input, an output and internet connectivity, such as an IP cam, a web cam, a wifi speaker, a TV, a setup box or a wireless sensor. The first storage module110may be an internal or external storage device of the first network device100. For example, the first storage module110may be a thumb drive, a hard disk, a solid state drive, a ROM, a RAM, an EPROM, an EEPROM, or any computer-readable storage medium. The server300may be a server cluster or data center constructed by several servers. The device database400may be part of the server300, or be running on another computing device that may be accessed by the server300. The device database log data may be a table of a relational database. The column of the table may include device ID and device information such as hardware, software or network information. The row of the table may include information of only one network device. The device ID may also serve as a key value of the table. It is to be noted that person having ordinary skill in the art will understand that the device database400of the present invention may not be a relational database, and databases of network model, object model and hierarchy model may also be used.

In detail,FIG. 1Billustrates an exemplary embodiment of the device ID management system before the device ID is generated. The first network device100may comprise a storage module110to store a first device information112and may transmit the first device information112to the server300. The device database400may store the device database log data410, which may include the device ID column and the device information column, as illustrated. The first device information112may include hardware related information such as a brand name, a model number a firmware version, or software related information such as an application version or an application interface version. Moreover, the first device information112may include network information such as an IP address or a web service port number.

FIG. 1Cillustrates an exemplary embodiment of the device ID management system after the device ID is generated. Here, after the first network device100transmits the first device information112to the server300through the internet, the server300may generate a first device ID111of the first network device100according to the first device information112, and may transmit the first device ID111to the first network device100. The first network device100may store the first device ID111in the first storage module11. In addition, the server300may store the first device ID111and the first device information112to the device database400. As illustrated, the server300may further update the device database log data410, i.e., add the first device ID111and the first device information112to the device database log data410. As a result, device ID may be more easily managed as the device ID may not need to be pre-designated to a network device before it leaves the factory, and the device ID may be stored and updated in a server.

FIGS. 1D and 1Ein combination illustrate one embodiment of a system implementing the device ID management method of the present invention. Specifically,FIG. 1Dillustrates an exemplary device ID management system before the device ID is generated. Here, in addition to the first device information112, the first storage module110may be pre-stored with a shared device key113. The first network device100may encrypt the first device information112based on the shared device key113before transmitting the first device information112to the server300. The server300may be pre-stored with a shared device key310, which may be used to encrypt the data encrypted based on the shared device key113. In addition, the shared device key310may be used to encrypt data, which may be decrypted based on the shared device key113. As illustrated, the device database log data may further include columns for device keys.

FIG. 1Eillustrates an exemplary embodiment of the device ID management system after the device ID is generated. Here, the first network device100may encrypt the first device information112based on the shared device key113and may transmit the first device information112to the server300. The server300may decrypt the received first device information112based on the shared device key310, and may generate an first device ID111and a first device key114unique to the first network device100according to the first device information112. The server300may further encrypt the first device ID111and the first device key114based on the shared device key310and transmit encrypted first device ID111and first device key114to the first network device100. The first network device100may decrypt the first device ID111and the first device key114based on the shared device key113and store the decrypted first device ID111and the first device key114to the first storage module110. In addition, the server300may store the first device ID111, the first device information112and the first device key114to the device database400, and may update the device database log data410, i.e., add the first device ID111, the first device information112and the first device key114to the device database log data410. As a result, the device keys may be managed simultaneously with the management of the device ID to enhance the security of data transmission between a network device and a server.

The shared device key113and the shared device key310may be keys of a symmetric encrypting system. That is, the shared device key113may be the same as the shared device key310, and possessed by the first network device100and the server300respectively for encrypting and decrypting data. Alternatively, the shared device key113and the shared device key310may be keys of an asymmetric encrypting system. In this embodiment, the shared device key113may include a first private key and a first public key, and the shared device key300include a second private key and a second public key. The first private key and the second private key are used for decryption. The first public key may be used for encryption, and such encryption may be decrypted by the server300using the second private key. Similarly, the second public key may be used for encryption, and such encryption may be decrypted by the first network device100using the first private key. In another embodiment, all the network devices are pre-stored with the shared device key113when they leave the factory. Therefore, the process of acquiring the device ID in the device ID management system may be encrypted based on the shared device key113. Moreover, the data encrypted by and transmitted from the server300may be decrypted based on the shared device key113.

It is to be noted that although the first device key114may be generated by the server300, person having ordinary skill in the art will understand that the first device key114may be a key of a symmetrical encrypting system or a key of an asymmetrical encrypting system. In yet another embodiment of the present invention, after the first network device100may encrypt data based on the first device key114and transmit such data to the server300after the first network device100acquires the first device key114. The server300then acquires the first device key114from the device database400, and decrypt the data received from the first network device100based on the first device key114.

FIGS. 1F and 1Gin combination illustrate one embodiment of a system implementing the device ID management method of the present invention. Specifically,FIG. 1Fillustrates an exemplary device ID management system before the device ID is generated. The relationships between the first network device100, the server300and the device database400are identical to those illustrated inFIG. 1E, and therefore will not be repeated. Here, a second network device200is provided and the second network device200is communicative with the first network device100. In this embodiment, the first storage module110stores a first device ID111, a first device information112, a shared device key113and a first device key114, and the first network device100may receive data from the second network device200. The second network device200may include a second storage module210for storing the second device information212and the shared device key213. The shared device key213may be used to decrypt the data encrypted by the shared device key113. Furthermore, the shared device key213may be used to encrypt data, which may be decrypted based on the shared device key113. As illustrated, the device database log data410may include columns for device ID, device information and device key. In addition, the device database log data may include the first device ID111, the first device information112and the first device key114of the first network device100.

FIG. 1Gillustrates an exemplary embodiment of the device ID management system after the device ID is generated. The relationships between the first network device100, the second network device200, the server300and the device database400are identical to those illustrated inFIG. 1F, and therefore will not be repeated. Here, the second network device200may use the shared device key213to encrypt the second device information212and transmit the encrypted second device information212to the first network device100. The first network device100may decrypt the second device information212based on the shared device key113, encrypt such based on the first device key114and transmit such to the server300. The server300may acquire the first device key114from the device database400and decrypt the encrypted second device information212. The server300may further generate a second device ID211and a second device key214unique to the second network device according to the second device information212. The server300may then encrypt the second device ID211and the second device key214based on the first device key114and transmit such the encrypted second device ID211and the second device key214to the first network device100. The first network device may decrypt the second device ID211and the second device key214encrypted by the server300based on the first device key114, encrypt the second device ID211and the second device key214based on the shared device key113, and transmit the encrypted second device ID211and the second device key214to the second network device200. The second network device200may decrypt the encrypted second device ID211and second device key214based on the shared device key213, and store the decrypted second device ID211and second device key214to the second storage module210. In addition, the first network device100may transmit the first device ID111and the encrypted second device information212to the server300so as to enable the server300to query and retrieve the first device key114in the device database400according to the first device ID111. Moreover, the server300may store the second device ID211, the first device information212and the first device key214to the device database400, and update the device database log data410as illustrated inFIG. 1G. It is to be noted that the shared device key213and the second device key214may be keys of a symmetric encrypting system or an asymmetric encrypting system, as illustrated in the embodiments inFIGS. 1D and 1E. As a result, through encrypting the data transmission between the second network device200and the server300by the first network device100, which has already acquired the first device ID111and the first device key114, the security of the data transmission between the server300and the network devices in the device ID management method may be enhanced.

In another embodiment, the first network device100and the second network device200may possess the shared device key113and the shared device key213respectively. Accordingly, the first network device100may encrypt the device ID based on the shared device key113, and the second network device200may encrypt the device ID based on the shared device key213. Moreover, the first network device100and the second network device200may decrypt the data received from and encrypted based on the shared device key310by the server300. In yet another embodiment, all the network devices, including the first network device100and the second network device200, may possess a same shared device key. That is, shared device key113and shared device key213may be identical. In addition, after the second network device200acquires the second device key214, the second network device200may encrypt the data based on the second device key214before transmitting such data to the server300. Thereafter, the server300may acquire the second device key214from the device database400, and decrypt the data received from the second network device200based on the second device key214.

FIGS. 2A and 2Bare block diagrams of a network device for managing device ID according to some embodiments of the present invention. Specifically, the network device may be implemented in the aforementioned device ID management system.

FIG. 2Aillustrates an exemplary embodiment of the network device for managing device ID. The first network device100may comprise a first storage module110, which may store a first device information112, as illustrated inFIG. 1B. In addition, the first network device100may comprise a transmission module120and a reception module130. The first network device100may transmit the first device information112to the server300via the transmission module120, and may receive a first device ID111from the server300via the reception module130, as illustrated in the embodiments inFIGS. 1B and 1C. The first device ID111may be generated by the server300according to the first device information112. In addition, the first storage module110may store the first device ID111, as illustrated in the embodiment inFIG. 1C.

FIG. 2Billustrates another exemplary embodiment of the network device for managing device ID. The first network device100may comprise a first storage module110, which may store a first device information112and a shared device key113, as illustrated inFIG. 1D. In addition, the first network device100may comprise a transmission module120, a reception module130, an encryption module140and a decryption module150. The first network device100may encrypt the first device information112by the encryption module140based on the shared device key113, and may transmit the encrypted first device information112to the server via the transmission module120, as illustrated in the embodiment inFIG. 1D. Moreover, the first network device100may receive via the reception module130the first device ID111from the server300, as illustrated in the embodiment inFIG. 1E. Furthermore, the first network device100may decrypt the device ID111based on the shared device key113by the decryption module150, and then transmit the result to the first storage module110. The first device ID111may be generated by the server300according to the first device information112, and transmitted to the first network device100after the server300encrypts it based on the shared device key310.

In another embodiment, with reference toFIG. 1E, the reception module130may receive the first device key114, which is encrypted by the server based on the shared device key310. It is to be noted that the first device key114may be generated by the server300. Moreover, the decryption module150may decrypt the first device key114based on the shared device key113. The decrypted first device key114may be later transmitted to the first storage module110.

In another embodiment, with reference toFIG. 1F, the reception module130may receive from the second network device200, the second device information212, which is encrypted by the second network device200based on the shared device key213. The decryption module150may decrypt the encrypted second device information212based on the shared device key113. The encryption module140may encrypt the second device information212based on the first device key114received from the server300. The transmission module120may transmit the encrypted second device information212to the server300. With reference toFIG. 1G, the reception module130may receive from the server300the second device ID211and the second device key214, which are encrypted based on the first device key114by the server300. The decryption module150may decrypt the first device key114. The encryption module140may encrypt the first device key114based on the shared device key113. The transmission module120may transmit the encrypted second device ID211and the second device key214to the second network device200.

It is to be noted that the transmission module120and the reception module130may respectively be a transmitter or a receiver of the first network device100for accessing the Internet. Alternatively, the transmission module120and the reception module130may be combined as a transceiver for transmitting and receiving wired or wireless signals. In addition, the encryption module140and the decryption module150may utilize any encrypting and decrypting algorithm to encrypt and decrypt the information through keys. The encryption module140and the decryption module150may be stored in computer readable mediums, such as ROM, RAM, EPROM, EEPROM, hard disk, solid state disk, or the like, in the form of a software or a firmware. In some embodiments of the present invention, the aforementioned computer readable medium may be the first storage module110. Moreover, the encryption module140and the decryption module150may be implemented in the form of an electric circuit in semiconductors or circuit boards, such as application-specific integrated circuit (ASIC) or printed circuit board (PCB).

FIGS. 3A-3Hare flowcharts illustrating the device ID management method according to some embodiments of the present invention. Specifically, the device ID management method provides a series of processes for the server to generate a device ID corresponding to a specific network device.

FIG. 3Aillustrates an exemplary embodiment of the device ID management method. Specifically, the present embodiment may be implemented in the system disclosed inFIGS. 1B and 1C. In step S3002, the first network device100may transmit a first device information112to the server300. In step S3004, the server300may generate a first device ID111unique to the first network device100according to the first device information112, and may further store the first device ID111. In step S3006, the server300may transmit the first device ID111to the first network device100. In step S3008, the first network device100may receive and store the first device ID111. In addition, the server300may store the first device ID111and the first device information112. As a result, device ID may be more easily managed as the device ID may not need to be pre-designated to a network device before it leaves the factory, and the device ID may be stored and updated in a server.

In another embodiment, when the first network device100is reset, the first device ID may be accordingly deleted, and the first network device100may acquire another device ID by implementing the method disclosed inFIG. 3A. Therefore, the first device ID111unique to the first network device100may only correspond to the first network device100, but not other network devices. Similarly, the first device key114unique to the first network device100, may only correspond to the first network device100. Moreover, the second device ID211and the second device key214unique to the second network device200may only correspond to the second network device200. Consequently, if the first network device100is reset and running normally, a new device ID may be directly acquired by implementing the device ID management method, instead of searching for the first network device100in the device database400to amend the first device information. As a result, the network device being reset may not need to be retrieved in the device database, and corresponding device information may not need to be deleted before a new device information is generated.

FIG. 3Bis another exemplary embodiment of the device ID management method illustrating the steps executed by a server inFIG. 3A. In step S3012, the server300may receive the first device information112from the first network device100. In step S3014, the server300may generate a first device ID111unique to the first network device100, and may store the first device ID111. In step S3016, the server transmits the first device ID111to the first network device100. In addition, the server300may store the first device ID111and the first device information112in the device database400, as disclosed in the embodiment inFIG. 1C.

FIG. 3Cis another exemplary embodiment of the device ID management method illustrating the steps executed by a network device inFIG. 3A. In step S3022, the first network device100verifies whether it possess the first device ID111. If affirmative, the device ID management method may be terminated. If negative, the first network device100performs step S3024. In step S3024, the first network device100transmits the first device information112to the server300. In step S3026, the first network device100receives and stores the first device ID111from the serve300. The first device ID111was generated by the server300according to the first device information112, and the first device ID111is unique to the first network device100. In step S3028, the first network device100stores the first device ID111. Afterwards, the device ID management method may be terminated.

FIG. 3Dillustrates an exemplary embodiment of the device ID management method. Specifically, the present embodiment may be implemented in the system disclosed inFIGS. 1D and 1E. In step S3032, the first network device100may encrypt the first device information112based on a shared device key, and may transmit the encrypted first device information112to the server300. In step S3034, the server300may decrypt the received first device information112based on the shared device key, and generate a first device ID111unique to the first network device100according to the first device information112. Moreover, the server300may store the first device ID111. In step S3036, the server300may encrypt the first device ID111based on the shared device key, and transmit the encrypted first device ID111to the first network device100. In step S3038, the first network device100may decrypt the received first device ID111based on the shared device key, and store the decrypted first device ID111. As a result, the device keys may be managed simultaneously with the management of the device ID to enhance the security of data transmission between a network device and a server.

FIG. 3Eis another exemplary embodiment of the device ID management method illustrating the steps executed by a server inFIG. 3D. In step S3042, the server300may receive from the first network device100the first device information112encrypted based on the shared device key. In step S3044, the server400may decrypt the first device information112based on the shared device key. In step S3046, the server300may generate a first device ID111unique to the first network device100according to the first device information112. Moreover, the server300may store the first device ID111. In step S3048, the server300may encrypt the first device ID111based on the shared device key, and may transmit the encrypted first device ID111to the first network device100. In addition, the server300may store the first device ID111and the first device information112in the device database410.

FIG. 3Fis another exemplary embodiment of the device ID management method illustrating the steps executed by a network device inFIG. 3D. In step S3052, the first network device100verifies whether it possess the first device ID111. If affirmative, the device ID management method may be terminated. If negative, the first network device100performs step S3054. In step S3054, the first network device100may encrypt the first device information112based on the shared device key and transmit the encrypted first device information112to the server300. In step S3056, the first network device100receives from the server300the first device ID111encrypted based on the shared device key. The first device ID111was generated by the server300according to the first device information112, and the first device ID111is unique to the first network device100. In step S3058, the first network device100decrypts the first device ID111based on the shared device key and stores the decrypted first device ID111. Afterwards, the device ID management method may be terminated.

FIG. 3Gillustrates another exemplary embodiment of the device ID management method. Specifically, the present embodiment may be implemented in the system disclosed inFIGS. 1D and 1E. In step S3062, the first network device100may encrypt the first device information112based on the shared device key, and may transmit the encrypted first device information112to the server300. In step S3064, the server300may decrypt the first device information112based on the shared device key. In addition, the server300may generate according to the first device information112a first device ID111and a first device key114unique to the first network device100. Moreover, the server300may store the first device ID111and the first device key114. In step S3066, the server300may encrypt the first device ID111and the first device key114based on the shared device key, and may transmit the encrypted first device ID111and first device key114to the first network device100. In step S3068, the first network device100may decrypt the first device ID111and the first device key114received from the server300based on the shared device key. In addition, the first network device100may store the decrypted first device ID111and first device key114. As a result, the device keys may be managed simultaneously with the management of the device ID to enhance the security of data transmission between a network device and a server.

In one embodiment, the server300may store the first device ID111, the first device information112and the first device key114in the device database400, and may accordingly update the device database log data410, i.e., add the first device ID111, the first device information112and the first device key114to the device database log data410. In another embodiment, the first network device100may encrypt a data request based on the first device key114after the first network device100acquires the first device key114, and may transmit the encrypted data request to the server300. The server may acquire the first device key114from the device database400, and decrypt the data request transmitted from the first network device100based on the first device key114so as to respond to the data request.

In another embodiment, the present invention provides a device ID management method implemented in a server. Specifically, such device ID management method may be programmed into a computer program, which may be executed by a computing device or may be stored in a computer-readable medium and later read and executed by a computing device. The device ID management method of the server300may include receiving from the first network device100a first device information112encrypted based on shared device key; decrypting the first device information112based on the shared device key; generating a first device ID111unique to the first network device100according to the first device information112, generating a first device key114unique to the first network device100, and storing the first device ID111and the first device key114; encrypting the first device ID111and the first device key114based on the shared device key, and transmitting to the first network device100the first device ID111and the first device key114. In addition, the server300may store the first device ID111, the firs device ID111, the first device information112and the first device key114in the device database400. In another embodiment, the server300may receive from the first network device100a data request encrypted based on the first device key114. Thereafter, after acquiring the first device key114from the device database400, the server300may decrypt encrypted data request transmitted from the first network device100based on the first device key114, and accordingly respond to the data request.

In yet another embodiment, the present invention provides a device ID management method implemented in the first network device100. Similarly, such device ID management method may be programmed into a computer program, which may be executed by a computing device or may be stored in a computer-readable medium and later read and executed by a computing device. Specifically, the device ID management method provides verifying whether the first network device100possess the first device ID111. If negative, the device ID management method may be terminated. If negative, the device ID management method of the first network device100may include encrypting the first device information112based on the shared device key and transmitting the encrypted first device information112to the server300; receiving from the server300a first device ID111and a first device key114, whereas the first device ID111is unique to the first network device100and is generated by server300according to the first device information112, and the first device key114is unique to the first network device100and is generated by server300; storing the first device ID111and the first device key114after decrypting them based on the shared device key. In yet another embodiment, the network device100may encrypt a data request based on the first device key114, and transmit the encrypted data request to the server300. Thereafter, the first network device100may receive from the server300a data encrypted based on the first device key114by the server300, and accordingly decrypt such data based on the first device key114.

FIG. 3Hillustrates another exemplary embodiment of the device ID management method. Specifically, the present embodiment may be implemented in the system disclosed inFIGS. 1F and 1G. In step S3072, the second network device200may encrypt the second device information212based on the shared device key, and transmit the encrypted second device information212to the first network device100. In step S3074, the first network device100may decrypt the second device information212received based on the shared device key, and encrypt such second device information212based on the first device key114before transmitting the second device information212to the server300. In step S3076, the server300may decrypt the second device information212received based on the first device key114. Consequently, the server300may generate a second device ID211unique to the second network device200according to the second device information212, and may generate a second device key214unique to the second network device200. Moreover, the server300may store the second device ID211and the second device key214. In step S3078, the server300may encrypt the second device ID211and the second device key214based on the first device key, and transmit the encrypted second device ID211and second device key214to the first network device100. In step S3080, the first network device100may encrypt the second device ID211and the second device key214received based on the first device key114. Consequently, the first network device100may encrypt the second device ID211and the second device key214based on the shared device key and transmit the encrypted second device ID211and the second device key214to the second network device200. In step S3082, the second network device200may decrypt the second device ID211and the second device key214based on the shared device key and store the decrypted second device ID211and second device key214. As a result, through encrypting the data transmission between the second network device200and the server300by the first network device100, which has already acquired the first device ID111and the first device key114, the security of the data transmission between the server300and the network devices in the device ID management method may be enhanced.

In one embodiment, the server300may store the second device ID211, second device information212and the second device key214to the device database400, and may accordingly update the device database log data410, i.e., add the second device ID211, second device information212and the second device key214to the device database log data410. The first network device100may transmit the first device ID111and the encrypted second device information212to the server300so as to enable to server300to query in the device database400to acquire the first device key114. In another embodiment, after acquiring the second device key214, the second network device200may encrypt a data request based on the second device key214and transmit the encrypted data request to the server300. Thereafter, the server300may acquire the second device key214from the device database400and decrypt the data request received from the second network device200based on the second device key214. Consequently, the server300may respond to the data request.

In another embodiment, the present invention provides a device ID management method implemented in a server. Specifically, such device ID management method may be programmed into a computer program, which may be executed by a computing device or may be stored in a computer-readable medium and later read and executed by a computing device. The device ID management method of the server300may include receiving from the first network device100the second device information212encrypted based on first device key114; decrypting the second device information212based on the first device key114; generating a second device ID211unique to the second network device200according to the second device information212; encrypting the second device ID211based on the first device key114and transmitting the encrypted second device ID211to the first network device100. In addition, the server300may generate a second device key214unique to the second network device200, encrypt such second device key214based on the first device key114, and transmit such encrypted second device key214to the first network device100. In yet another embodiment, the server300may store the second device ID211, the second device information212and the second device key214in the device database400. In addition, the server300may receive a data request transmitted from and encrypted based on the second device key214by the second network device200. Thereafter, the server300may respond to the data request.

In yet another embodiment, the present invention provides a device ID management method implemented in the first network device100. Similarly, such device ID management method may be programmed into a computer program, which may be executed by a computing device or may be stored in a computer-readable medium and later read and executed by a computing device. Specifically, the device ID management method provides receiving from the second network device200the second device information212, which is encrypted based on the shared device key; decrypting the second device information212based on the shared device key, and sending the second device information212to the server300after encrypting the second device information212based on the first device key114; receiving from the server400the second device ID211encrypted based on the shared device key, wherein the second device ID211is generated by the server300according to the second device information212and the second device ID211is unique to the second network device200; decrypting the second device ID211based on the first device key114, and transmitting the second device ID211to the second network device200after encrypting the second device ID based on the shared device key. In addition, the first network device100may receive from the second network device200a second device key214encrypted based on the first device key114, and decrypt such second device key214based on the first device key114. Thereafter, the first network device100may encrypt the second device key214based on the shared device key and transmit the encrypted second device key214to the second network device200. It is to be noted that the second device key214is generated by the server300, and the second device key214is unique to the second network device200.

In yet another embodiment, the present invention provides a device ID management method implemented in the second network device200. Similarly, such device ID management method may be programmed into a computer program, which may be executed by a computing device or may be stored in a computer-readable medium and later read and executed by a computing device. Specifically, the device ID management method provides encrypting the second device information212based on the shared device key and transmitting the encrypted second device information212to the first network device100; receiving from the first network device100the second device ID211encrypted based on the shared device key, wherein the second device ID211is generated by the server300according to the second device information212and the second device ID211is unique to the second network device200; decrypting the second device ID211based on the shared device key and storing the second device ID211. In addition, the second network device200may receive from the first network device100the second device key214encrypted based on the shared device key. Thereafter, the second network device200may decrypt the second device key214based on the shared device key and store the second device key214. It is to be noted that the second device key214is generated by the server300, and the second device key214is unique to the second network device200. In yet another embodiment, the second network device200may encrypt a data request based on the second device key214, and transmit the data request to the server300. Thereafter, the second network device200may receive from the server300data encrypted based on the second device key214, and decrypt such data based on the second device key214.

It is to be noted that the aforementioned device ID management method may be implemented into a computerized product by means of programming language. Examples of such include computer source code or computer-executable files. Alternatively, the aforementioned computer program may be stored in a computer-readable medium and accessed by a computing device to execute the device ID management method. Examples of computer-readable medium include ROM, RAM, EPROM, EEPROM, hard disk, solid-state disk, floppy disk, CD-ROM, DVD-ROM, or other electronic, electro-magnetic or optical recording medium.

Previous descriptions are only embodiments of the present invention and are not intended to limit the scope of the present invention. Many variations and modifications according to the claims and specification of the disclosure are still within the scope of the claimed invention. In addition, each of the embodiments and claims does not have to achieve all the advantages or characteristics disclosed. Moreover, the abstract and the title only serve to facilitate searching patent documents and are not intended in any way to limit the scope of the claimed invention.