TWI531910B - Data management method, computer program product and managing server - Google Patents

Description

Data management method, computer program product and management server

The invention relates to a data management method, in particular to a data management method between an application and a server, a computer program product and a management server end.

Existing mobile devices, such as mobile phones and tablets, can be connected to a server and a plurality of peripheral devices such as a network monitor (IP Cam) via the Internet, so that the mobile device can receive the video captured by the network monitor. . In order to achieve the above functions, the mobile device installs and executes the application, and the application first receives the connection information of the peripheral devices one by one, and informs the server one by one of the connection information, and the server connects the mobile device and the surrounding area via the Internet. device.

There are also some peripheral devices that support the function of pushing information. For example, when you want to add peripheral devices, the mobile device needs to install and execute the application, and then read the first network monitoring through the camera of the mobile device. The two-dimensional barcode of the device is parsed out of the first device identification code, and combined with the mobile phone device identification code to form a first combined code to be transmitted to the server, so that the server records the first combined code to complete the addition of the peripheral device; Delete the perimeter In the device, the mobile device executes the application, sends an instruction to delete the first combination code to the server, and causes the server to delete the first combination code to complete the deletion of the peripheral device.

However, under this mechanism, the mobile device has executed the application to transmit the first combination code to the server, and after the server completes the record, if the mobile device deletes the application without the Internet condition, and then connects When the Internet re-installs the application again, after reading the second device identifier of the second network monitor, a second combination code is generated and transmitted to the server, and the server can successfully record the second. The combination code, but the first combination code remains in the server, and since the first combination code is not retained in the application of the mobile device at this time, it is already unknown information, so the mobile device cannot release the first code. A combination code delete command, when the first network monitor sends a notification message, the server will transmit the notification message to the mobile device, causing user confusion.

At present, there is also a solution to the above problem, that is, when the mobile device removes the application, all the corresponding combination codes belonging to the mobile device in the server are deleted, and the user reinstalls the application and increases network monitoring. After the device, the newly generated combination code is recorded. However, this method will have the problem of "time dependency", that is, when some peripheral devices have customized settings, for example, there is a settable notification message interval. In the timing function, if all the combination codes are deleted, the data being timed will be cleared. For example, the mobile device has set up to transmit only the message from the second network monitor to the mobile device within one hour, so when the message is transmitted once, the server will start timing and prevent the next small one. The other notification message of the second network monitor is transmitted during the period; but during this period, the server deletes the entire combination code of the mobile device and then re-records the new combination code, although the second network monitor in the server side After the combination code is deleted, it has been added again, but the timing record related to the second network monitor on the server side will also be deleted and all re-timed, that is, the server-side information (timekeeping record) has generated an error. As long as the server receives the notification message from the peripheral device, it can immediately send the message to the mobile device through the tweet server, regardless of whether the last transmission has been separated by one hour, causing the user to receive it within one hour. More than one notification message.

Another problem is that when the mobile device is offline, the action of deleting and adding multiple data is performed. After entering the connection state, each deletion and new action must cooperate with the data verification to make the server It is determined that which mobile device is to perform the action, and the speed is slow. Therefore, it is necessary to further improve the management method between the application and the server.

One of the objects of the present invention is to provide a faster data management method that avoids server-side information errors.

Another object of the present invention is to provide a computer program product that avoids server-side information errors and is faster.

Yet another object of the present invention is to provide a faster management of the server side by avoiding server-side information errors.

In some implementations, the data management method of the present invention is executed by a management server, and the management server includes a database. The database can store a plurality of key data including a plurality of link codes from a plurality of user terminals, a plurality of application unique codes, a plurality of device identification codes, and a plurality of user end setting information, and the method is applicable to a user. End, the user end stores a link code, an application unique code, and a list of user devices, and the method includes the following steps:

Receiving the link code of the user end, the application unique code, and the list of the client device.

Delete all key data in the database that has the same connection code as the user but differs from the unique code of the application.

Determining whether the user equipment list is a blank list, and if not, the data content of the user equipment list includes at least one user equipment list data having a device identification code and a user end setting information, and The pen reads the user device list data.

Determining whether the device identifier of the user terminal, the application unique code, and the device identifier of the user device list data in the database have the same connection code and the same application identifier The code and the corresponding key data of the same device identification code, if yes, updating the user terminal setting information in the corresponding key binding data in the database as the user end setting of the user terminal device list data Information, and add the corresponding key information to a white list.

Delete all the key data in the database that does not exist on the white list but has the same link code and the application unique code as the user end.

In some implementations, wherein the received use is determined The connection code of the terminal, the application unique code, and the device identifier of the user device list data have the same step of the corresponding key data in the database. If not, the method includes the following steps:

The corresponding key data including the link code, the application unique code, and the device identification code is added to the database.

In some implementations, the step of determining whether the user device list is a blank list, if yes, includes the following steps:

Delete all key data in the database that has the same link code and the unique code of the application.

In some implementations, the link code is used to connect the user terminal to a push server, so that the user terminal can receive a push message from the push server.

In some implementations, the device identifier corresponds to a peripheral device, and the peripheral device sends a notification message to the management server, and the management server uses the notification information and the link code corresponding to the device identifier. And transmitting to the push server, causing the push server to transmit the push message corresponding to the notification information to the user end.

In some implementations, the user equipment list data includes the device identification code, the corresponding key information includes the connection code, the application unique code, the device identification code, the user end setting information, and a The server retains information; wherein the step of updating the corresponding key data further includes the following steps:

Keep the server-side retention information.

In some implementations, the user setting information includes a minimum interval value required to be pushed, the server-side retention information includes a previous communication time that the management server transmits the notification information and the connection code corresponding to the device identification code to the push server for the previous time. .

In some implementations, the management server includes the following steps each time before transmitting the notification information and the link code to the push server:

It is judged whether the current time minus the previous communication time is greater than the minimum interval value of the required push, and if so, the transmission is performed.

In some implementations, the computer program product of the present invention loads the program via a computer to perform the data management method as described.

In some implementations, the management server of the present invention performs the data management method as described.

The effect of the present invention is that by deleting the key data not on the white list, the problem that the unknown peripheral device cannot be deleted can be successfully solved; by updating the user end setting information of the corresponding key binding data, the server retaining information is retained. It can avoid the error of managing the information on the server side; it can reduce the time of data verification and speed up the processing by transmitting the data of the user equipment list at one time.

1‧‧‧Manage server side

11‧‧‧Management Server

12‧‧‧Database

2‧‧‧Mobile devices

3‧‧‧Pushing server

4‧‧‧ peripheral equipment

S1 to S9‧‧ steps

S51, S61, S62‧‧‧ steps

S11 to S18‧‧‧ steps

S111‧‧‧Steps

Other features and advantages of the present invention will be apparent from the following detailed description of the embodiments of the invention, wherein: FIG. 1 is a system block diagram illustrating the use of the management server end and its cooperation in accordance with an embodiment of the present invention. a server, a push server and a peripheral device; FIG. 2 is a flowchart illustrating a data management method according to an embodiment of the present invention; Figure 3 is a flow chart showing the step S1 of the embodiment; and Figure 4 is a flow chart showing another embodiment of the step S1 of the embodiment.

Referring to FIG. 1 and FIG. 2, an embodiment of the data management method of the present invention is executed by a management server terminal 1 and is adapted to cooperate with a user terminal, a push server 3, and a peripheral device 4.

The management server terminal 1 is a server terminal for providing application services, and includes a management server 11 and a database 12 for mutual information connection. In this embodiment, an independent database is used for explanation, that is, It is said that the data management server 11 and the database 12 are located in different but interconnected computers, but not limited thereto, and may be located in the same computer.

In this embodiment, the user terminal is a mobile device 2, and stores a link (token) for receiving a push message, an application unique code, and a list of user devices. The mobile device 2 is, for example, a portable electronic device such as a smart mobile phone, a tablet computer, or a notebook computer.

In detail, the link code is used to connect the mobile device 2 and the push server 3 to enable the mobile device 2 to receive the push message from the push server 3. When the application on the mobile device 2 wants to use the push message function, it will make a request to the push server 3 associated with its operating system, and the push server 3 will return the link code, and the mobile device 2 Transmitting the link code to the management server 11, and when the management server 11 wants to transmit the push message, the content to be pushed and the link code are transmitted. To the push server 3, the push server 3 can transmit a push message to the mobile device 2.

As for the application unique code, in this embodiment, it is necessary to independently generate each application when it is installed in any device. For example, in the Android system, since the Android system does not provide the service, in this embodiment, the application unique code includes an application ID (Application ID) and a hardware number, wherein the same application The same version will have the same application number, and the hardware number will be generated by serial number, Media Access Control Address (MAC Address) and random data. The application unique code generation method of Apple's mobile device 2 operating system (iOS) is not disclosed, but it provides an application programming interface (API) that can generate the application unique code, and the application is installed. When you request from the application interface, you can get the unique code of the application installed this time. In summary, the same version of the same application is installed twice on the same or different hardware, or the same application will be different before and after the update. The application unique code can assist the management server 11 in identifying the objects it communicates with.

The peripheral device 4 is, for example, a network camera (IP Cam), a network monitor, various smart appliances, an alarm device, or a network hard disk and other peripheral devices having a network connection function, and has a device identification code for identification. The peripheral device 4 is registered with the management server 11 after being connected to the Internet. In general, the device identification code can also be attached to the surface of the peripheral device 4 for a user to know and input to the mobile device 2, for example, a action. The device 2 needs to install the application before inputting the device identification code and performing the subsequent steps, or providing the device identification code of the peripheral device 4 by the user through other description files. In detail, after the mobile device 2 installs the application, the device identification code received and transmitted is transmitted to the management server 11. In the present embodiment, the mobile device device list is a list of user device devices that transmit a list of user device devices including all device identification codes stored therein to the management server 11.

In the case of the above-mentioned link code, the push message is transmitted, for example, according to the user setting, when the network camera detects that a certain behavior occurs in a certain block, a notification message is sent to the management server 11, the management server. The device 11 queries the corresponding code of the mobile device 2 from the database 12 according to the device identification code of the network camera, and transmits the notification information and the connection code to the push server 3 to push the server 3 The push message corresponding to the notification information can be transmitted to the mobile device 2.

In general, the management server 11 integrates the mobile device 2, the push server 3, and the peripheral device 4 so that when the peripheral device 4 issues notification information, it can be sent to the mobile device 2 via the push server 3. However, the premise of being able to operate smoothly is that the information about the peripheral device 4 in the management server 11 must be processed in an appropriate manner with the relevant information on the mobile device 2, and the notification information can be delivered smoothly and without error. Accordingly, the embodiment of the data management method of the present invention includes the following steps performed by the management server 11:

Step S1: receiving the link code of the mobile device 2, the application unique code, and the list of the client device, and performing data verification. The part of the data verification is described later, and the following proceeds to step S2.

In step S2, compared with the link code of the mobile device 2 and the application unique code, all the key data of the database 12 having the same link code but different application unique codes are deleted. The details of the keying data are described in the format. It should be noted that, in the database 12, there may be 0, 1 or more key binding data that meet the foregoing conditions. Therefore, the number of "all" keying data that meets the requirements in this step may be 0, 1 Pen or more than 2 strokes, in any case, are deleted in this step. Further, the database 12 may store 0 pens (when no key data has been stored), 1 or more key data, which does not affect all the steps in this embodiment. get on.

The same link code means that it corresponds to the same mobile device, in other words, any one of the same set of link codes will correspond to the same mobile device. Therefore, if there are one or more keying materials with different application unique codes in the database 12, but have the same linking code, it may be that the mobile device corresponding to the linking code is left when the application is previously installed. News. The previously installed application has the same application unique code as the currently used application unique code, but is connected to the push server 3 on the same mobile device, and therefore has the same link code. After the application is removed or updated, the application unique code corresponding to the mobile device has been changed, so that the one or more key binding data with different application unique codes can be deleted. The process proceeds to step S3 below.

Step S3 - determining whether the user terminal device list is a blank list, and if so, proceeds to step S4, and if not, proceeds to step S5. In detail, when there is data in the user device list, it represents the mobile device. 2 The device identification code of the peripheral device 4 has been added, so the data update is required; if it is a blank list, the reverse is true.

Step S4 - Delete all the keying data of the database 12 having the same concatenated code and the application unique code compared with the concatenated code of the mobile device 2 and the application unique code. This means that the user side removes all device identification code information during the process of losing the Internet, so the key data retained in the database 12 also needs to be deleted synchronously in the database 12. End the process after completing the above process.

Step S5-Reading a piece of user device list data in the list of the user device, the user device device list data includes the device identification code and a user terminal setting information.

The user terminal setting information is information about the peripheral device 4 set by the mobile device 2, that is, the user terminal, for example, including a minimum interval value for requesting push and other setting information, and the minimum required for the push broadcast. The interval value is a minimum time interval for setting the request to receive the push message about the peripheral device 4. In this embodiment, if the minimum interval value of the request push is less than zero, it means that the setting is never received, but not Limited. The other setting information includes, for example, a displayed device name. The list of user equipments is shown in Table 1.

In this embodiment, the device identification code is represented by a combination of 20 codes and an English number. The unit of the minimum interval value of the required push is seconds, and the length of the displayed device name is limited to 30 words, but not the above. Limited. The process proceeds to step S51.

Step S51 - determining whether the peripheral device 4 to which the device identification code belongs has been online. In detail, the database 12 stores a list of existing devices storing device identification codes and device information of all registered peripheral devices 4. By recording the list of existing devices, it can be known which paging devices 4 are provided by the management server 11.

In this embodiment, the database 12 also stores a key list, and the key data is stored in the key list in this embodiment. The field of the key list includes fields for storing the link code, the application unique code, the device identification code, the user terminal setting information, and a server end reservation information, thereby storing the mobile device 2 The binding relationship between the application on the peripheral device 4 and the peripheral device 4, wherein the server end retains the information after the description. In the foregoing step S2, all the key data of the application unique code having the same contig code but different in the key list of the database 12 are deleted. The process proceeds to step S6 below.

Step S6 - determining whether the device identification code of the user equipment list data of the pen has been keyed in the key list of the database 12. In detail, in this step, it is determined whether the connection code of the mobile device 2, the application unique code, and the device identification code of the user device list data have a corresponding keying data in the management server terminal 1. If yes, enter the step At step S61, if no, the process proceeds to step S62.

Step S61 - update the corresponding keying material in the database 12. In this step, the user end setting information of the corresponding key data in the key list of the database 12 is updated to the user end setting information of the piece of data of the user device list.

The aforementioned server-side reservation information has not been modified or deleted due to the update of this step. The server-side reservation information is information about the peripheral device 4 retained by the management server terminal 1, for example, the management server 11 transmits the notification information and the link code corresponding to the device identification code to the push broadcast. a previous communication time of the server 3, and the management server 11 first determines whether the current time minus the previous communication time is greater than before transmitting the notification information and the connection code to the push server 3 The minimum interval value for the request is pushed, and if so, the transmission is performed; if not, the next notification message is waited for the same determination. However, if the update method is to directly delete the entire key data in the key list of the database 12, the server-side reservation information will also be deleted, which will cause the problem of "time dependency" in the prior art. Since this step only updates the user-side setting information, the server can be prevented from retaining information and generating errors. After completing this step, the process proceeds to step S7.

Step S62 - adding the corresponding keying data to the database 12. In detail, in this step, a new link including the link code, the application unique code, the device identifier, the user terminal setting information, and the server-side reservation information is added to the key list of the database 12. Key data, but the server side retains information may be added to the fashion no content. Enter below Step S7.

Step S7 - adding the corresponding key data to the white list. The whitelisted keying information is the latest and correct information that has been updated. The process proceeds to step S8 below.

Step S8 - determining whether all the user equipment list data in the user equipment list has been read, and if not, re-entering step S5, and if yes, proceeding to step S9.

Step S9-Complete the connection code of the mobile device 2 and the application unique code, and delete all the key data of the database 12 that are not on the white list but have the same connection code and the application unique code, and end management. Process. By recording the whitelist, this step deletes the keying material of the unknown device as described in the previous paragraph. In detail, the unknown peripheral device 4 may be an old network camera that has established a key relationship with the mobile device 2, and after the management server terminal 1 completes the addition of the key data of the old network camera, the mobile device 2 Delete the app. When the mobile device 2 installs the application again, the device identification code of the old network camera is not added, so that the old network camera becomes an unknown device. In this step, since the corresponding key data corresponding to the device identification code of the old network camera in the database 12 is not added to the white list, the corresponding key data will be deleted. So far, the data in the database 12 has been correctly synchronized with the mobile device 2. The above is all the main steps of the embodiment of the data management method of the present invention, and the details of step S1 are further supplemented below.

Referring to FIG. 1 and FIG. 3, the detailed steps of data registration and verification in step S1 will be described below.

Step S11 - receiving the link code, the application unique code, and the registration command of the mobile device 2. However, it is not limited thereto, for example, it can also receive other user device environment information. Go to step S12.

Step S12 - determining whether the application unique code exists in the database 12, and if not, proceeds to step S13, and if yes, proceeds to step S14.

In this embodiment, the database 12 further stores a registration list for storing the registration data, including the connection code of the mobile device 2, the application unique code, and the environment information of the user device, wherein the user device environment The information may include the type of operating system of the mobile device 2, the version, the usage language information, and the like. This step is to determine whether the application unique code exists in the registration list. It is to be noted that the user terminal device environment information is related to the overall operating environment information of the mobile device 2, and the user terminal setting information described in step S5 is related to the application information of the peripheral device 4, and there are multiple peripheral devices 4 In this case, there will be multiple user-side setting information.

It should be noted that, in this embodiment, although the registration list and the key list are separately used to manage the registration data and the key information, but not limited thereto, it may be managed by a single list, or similarly. List to manage.

Step S13 - The registration data of the link code and the application unique code is added to the database 12, and the registration is completed, and the process proceeds to step S16. In this embodiment, the user equipment environment information is added to the database 12 for other purposes, such as the mobile device 2 using the language system. When the peripheral device 4 transmits the notification information, the management server 11 can correctly push the message The content and the usage language are forwarded to the push server 3 for transmission to the mobile device 2 for display to the user, but not limited thereto.

Step S14 - determining whether the concatenated code is the same as the concatenated code of the corresponding registration material in the database 12, and if so, the verification is completed to proceed to step S16, and if not, proceeding to step S15.

Step S15 - Update the link code and the user end information in the registration data of the database 12, and the verification is completed, and the process proceeds to step S16.

Step S16 - receiving the link code of the mobile device 2, the application unique code, the user device list, and the synchronization command. Proceed to step S17.

Step S17 - determining whether the registration data of the same application unique code and the link code exists in the registration list of the database 12, and if so, the correctness of the registration data is ensured, and the process proceeds to step S2 (see FIG. 2), and if not, Go to step S18.

Step S18 - Return the error message and end the process.

Through the above steps S11 to S18, it is ensured that the registration data having the same application unique code and the connection code already exist in the database 12, and the registration code of the mobile device 2 and the registration and verification of the application unique code are completed.

In this embodiment, since the device identification code to be synchronized is transmitted to the management server 11 in the user terminal device list at one time, it is not necessary to perform data verification before each device identification code performs data update, which can speed up The processing speed, especially when the mobile device 2 performs the actions of deleting multiple times and adding data in an offline state, when entering the connection state, the required data can be transmitted at one time, and the steps S12 and S17 are performed once. Data registration and verification can be. The above is an embodiment of the details of step S1. Further embodiment of step S1 in this embodiment is further supplemented below.

Referring to FIG. 1 and FIG. 4, in another embodiment, the following step S111 is first performed:

Step S111 - receiving the link code of the mobile device 2, the application unique code, and the list of the client device.

Then, after steps S13 to S15 are completed, steps S16 to S18 are omitted, and the process proceeds directly to step S2 (see FIG. 2). The main reason for omitting steps S16 to S18 is that step S17 can be omitted because the determination of the theoretical step S17 will be YES after step S12 to S15, and step S17 is only to ensure the correctness of the registration data again. .

In summary, by deleting the keying data that is not on the whitelist, the problem of not being able to delete the unknown peripheral device can be successfully solved; by updating the user-side setting information of the corresponding keying data, the server-side retention information can be retained. Avoiding the error in managing the information on the server side; by transmitting the list of user device devices to be synchronized at one time, the time for data verification can be reduced, and the synchronization speed can be accelerated, so that the object of the present invention can be achieved.

However, the above is only the embodiment of the present invention, and the scope of the present invention is not limited thereto, that is, the simple equivalent changes and modifications made by the patent application scope and the patent specification of the present invention are still It is within the scope of the patent of the present invention.

S1 to S9‧‧ steps

S51, S61, S62‧‧‧ steps

Claims (10)

A data management method is executed by a management server, and the management server includes a database, and the database can store a plurality of multiple connection codes from multiple users, multiple application unique codes, and multiple The device identification code and the binding data of the plurality of user end setting information, the method is applicable to a user end, wherein the user end stores a link code, an application unique code and a user device list, the method The method includes the following steps: receiving the link code of the user end, the unique code of the application, and the list of the client device; deleting the link code in the database that is the same as the user end, but different from the application unique code All the keying data; determining whether the user equipment list is a blank list; if not, the data content of the user equipment list includes at least one user end having a device identification code and a user end setting information Device list data, and reading the user device list data one by one; determining the received link code of the user end, the application only Whether the code and the device identifier of the user terminal device list have corresponding key data in the database that includes the same link code, the same application unique code, and the same device identifier, and if so, Updating the user-side setting information in the corresponding keying data in the database for the user-side setting information of the user-side device list data, and adding the corresponding keying information to a whitelist; and Delete all the key data in the database that does not exist on the white list but has the same link code and the application unique code as the user end. The data management method of claim 1, wherein determining whether the connection code of the user end, the application unique code, and the device identification code of the user device list data are present in the database The step of the corresponding keying data, if not, includes the following steps: adding the corresponding keying data including the linking code, the application unique code, and the device identification code to the database. The data management method of claim 1, wherein the step of determining whether the user device list is a blank list, if yes, comprising the steps of: deleting all the same link code and the application unique code in the database Bond data. The data management method of claim 1, wherein the link code is used to connect the user terminal to a push server, so that the user terminal can receive a push message from the push server. The data management method of claim 4, wherein the device identification code corresponds to a peripheral device, and the peripheral device sends a notification message to the management server, and the management server identifies the notification information and the corresponding device. The link code of the code is transmitted to the push server, so that the push server transmits the push message corresponding to the notification information to the user end. The data management method of claim 1, wherein the user equipment list data includes the device identification code, the corresponding key information includes the connection code, the application unique code, the device identification code, and the user The terminal setting information and a server-side reservation information; wherein, the step of updating the corresponding keying data further includes the following steps: retaining the server-side reservation information. The data management method of claim 1, wherein the user-side setting information includes a minimum interval value required to be pushed, and the server-side reservation information includes the management server last time to notify the information and the corresponding device. The link code of the identification code is transmitted to a previous communication time of the push server. The data management method of claim 7, wherein the management server further includes the following steps each time before transmitting the notification information and the connection code to the push server: determining the current time minus the previous communication. Whether the time is greater than the minimum interval value required to be pushed, and if so, the transmission is performed. A computer program product for loading a program via a computer to execute a data management method as claimed in any one of claims 1 to 8. A management server that performs the data management method as claimed in any one of claims 1 to 8.