JP2003157190A - Synchronizing message processing method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a synchronizing message processing method which avoids damage even in the case of reception of large quantities of synchronizing messages. SOLUTION: A terminal 100 is provided with an application part 102 which preserves data to be synchronized and accepts user operation to the data, a synchronizing processing part 104 which generates a synchronizing message for synchronizing the data preserved in the application part 102 with the data of a server 300 and interprets a synchronizing message received from the server 300, and a protocol processing part 106 which performs protocol processing to transmit the synchronizing message generated by the synchronizing processing part 104 to a network 200 and transfers a synchronizing message received from the network 200 to the synchronizing processing part 104. The protocol processing part 106 abandons synchronizing messages which have been received within a certain time after reception of preceding synchronizing messages.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a synchronization message processing method in a terminal device which is connected to a server via a network and performs data synchronization with data managed by the server.

[0002]

2. Description of the Related Art With the spread of information equipment, one user owns several terminal devices such as a mobile terminal, a mobile phone, and a personal computer, and records data such as an address book and a schedule on each of them. There are many cases. In this way, updating the data recorded in a plurality of terminal devices to the latest data is called "data synchronization", and by synchronizing the data, the contents of the data held in each terminal device become uniform. .

In recent years, data necessary for work is shared between related parties via a system for performing data synchronization of each terminal device of the user on behalf of the user or a network, and the related people can refer to this data. , A system called groupware has emerged that can be copied to the terminals of concerned parties.

In such a system, as shown in FIG. 10, as a terminal device (abbreviated as "terminal" in the drawings, the same applies to other drawings) 10, for example, a mobile phone 1
2, the mobile terminal 14, the desktop personal computer 16, the notebook personal computer 18, etc. are connected to the server 30 via the Internet 20. For example, when the address book of the mobile phone 12 is updated, the updated data is stored in the server 30. be registered. Terminal devices 14, 16, 1 other than the mobile phone 12
When updating the address book recorded in No. 8, from the terminal devices 14 to 18 to the server 30, the Internet 20
A request for data synchronization is issued through. In response to this,
The server 30 returns the update data of the address book, and the address book of the terminal devices 14 to 18 is updated.

FIG. 11 shows a processing sequence in this case. First, the terminal device 10 seeking data synchronization
It requests the server 30 to start synchronization and provides initial information such as the last update date and time (1). In response to this, the synchronization process is started, and the server 30 provides the terminal device 10 with initial information such as the last update date and time of the server 30 (2). When the data update is required, the terminal device 10 provides the update history of the address book to the server 30 (3), and the server 30 compares the address book data held by itself with the address book data of the terminal device 10. Then, the update content is transmitted to the terminal device 10 and the update is instructed (4). When the update of the address book is completed according to the update content received from the server 30, the terminal device 10 transmits a synchronization completion notification to the server 30 (5). The server 30 records the update status of the terminal device 10 and sends a synchronization completion confirmation notification to the terminal device 10 (6).

[0006] However, such prior art is not related to a publicly known invention in the literature, and there is no prior art literature information to be described.

In order to perform such data synchronization processing, it is necessary to install dedicated software in the terminal device 10, and this software has no versatility. for that reason,
At present, standardization of data synchronization processing is under study, and this standardization method is generally called "SyncML".

In the new synchronization processing sequence by SyncML, as shown in FIG. 12, first, the server 30a sends a message (referred to as "server alert message") for instructing the terminal device 10a to start data synchronization ( 1), the terminal device 10a interprets this message (message processing) and displays it on the display screen (2). When the user selects the data synchronization process, FIG.
Similarly, the terminal device 10a provides the synchronization start request and the initial information to the server 30a (3), and the same synchronization process as in FIG. 11 is started (4) (see Non-Patent Document 1, for example).

This new synchronization processing sequence by SyncML differs from the case of FIG. 11 in that the server 30a issues a data synchronization start instruction and the terminal device 10a processes the message.

At this time, the server 30a sends a server alert message without knowing the status of the user or the terminal device 10a, so that the terminal device 10a may not send the synchronization start request (3). Therefore, when the server 30a does not receive the synchronization start request (3) from the terminal device 10a, the server 30a repeatedly transmits the server alert message.

As described above, by issuing the synchronization start instruction from the server side, the user can perform the data synchronization of the terminal device without forgetting. In addition, by introducing the SyncML system into a system for registering and managing the sold terminal devices by the server, the terminal device manufacturer can upgrade the software of each terminal device through the server.

FIG. 13 shows a protocol structure of SyncML. In the communication for exchanging application data between the terminal device 10a and the server 30a, in each corresponding layer, the transmitting side performs a process of dividing the data or adding a header to the data, and then receiving the data. On the side, the process of removing the header of the data and combining the data is performed.

FIG. 13 exemplifies a process when the data newly added to the address book database of the terminal device 10a is transmitted to the server 30a. This data is Sy
It is converted by the ncML core into the data format of the synchronization message, and then the session layer (eg HTT
P), a transport layer (for example, TCP), and a network layer (for example, IP), and then formed into a packet with an IP header and transmitted to, for example, a server 30a connected by a LAN.

In the server 30a, the received data is returned to the data in the sync message format by the processing in the network layer, the transport layer and the session layer. The session layer identifies from the format that the data is a sync message and passes it to the SyncML core. The SyncML core interprets this data and translates it into a data structure that is written to the application's address book database. In this way, new data is added to the application database of the server 30a.

The processing of each layer of this protocol structure is performed by the CPU of the terminal device 10a and the server 30a, but the higher the processing of the upper layer, the greater the load on the CPU and the longer the processing. For example, roughly speaking, when processing 100 bytes of data, the total processing time of the network layer, the transport layer, and the session layer is 0.01 s.
Assuming ec, the message processing performed by the SyncML core requires a processing time of 0.1 sec, which is about ten times that.

[0016]

[Non-Patent Document 1] SyncML Sync Proto
col, v1.1, Internet <URL: "http: // s
yncml.org/technology.html ">

[0017]

However, in the SyncML system in which the synchronization start instruction message (server alert message) is sent from the server side, the following problems are expected.

Terminal device 10a in the process of data synchronization processing
The communication between the server 30a and the server 30a waits for the response of the other party before proceeding to the next transmission, but the server alert message instructing the terminal device 10a to start the data synchronization is the user's intention or the terminal device. The message is transmitted regardless of the state of 10a, and the terminal device 10a that receives the message performs a process of interpreting the message. Whether or not to start the data synchronization based on the result of the interpretation is left to the user's selection, but when the server alert message is received, the processing up to the message is indispensable, and the burden on the CPU for the processing. There are many.

If a malicious person (hacker or cracker) is present in the terminal device 10a in large quantity (for example, 100 per second).
If a synchronous message (such as a message) is sent, the terminal device 10a may stop the other processing due to the message processing, and in the worst case, the system may freeze. Here, the "synchronization message" refers to an arbitrary message related to the data synchronization process, and for example, in FIG. 12 (and FIG. 11), all messages shown in the same figure including the server alert message are included. .

Actually, the damage caused by sending a large amount of messages at one time has occurred in the past even on popular homepages and search pages on the Internet.

In order to prevent such a situation, in general, a blacklist that defines senders who reject the reception and a whitelist that specifies only senders that accept the reception are set, and messages from senders on the blacklist are set. Or discarding messages that are not whitelisted by the sender.

However, it takes time for a user to create such a list, and it is difficult to create an effective list. In addition, in a system in which software of a terminal device is set through a server, the server may be changed for the convenience of the manufacturer. In such a case, if the sender of the synchronization message is limited to a white list, the server that should receive the synchronization message will receive the message. There is a possibility that the synchronization message of will not be received. Also, blacklisting hackers that appear and disappear is virtually difficult.

The present invention has been made in view of the above points, and an object thereof is to provide a synchronous message processing method capable of avoiding damage even when a large number of synchronous messages are sent. And

[0024]

The method of the present invention comprises the steps of receiving data, determining whether the received data is a synchronization message, and receiving the received data if it is a synchronization message. The step of recording the reception time of the received data, the step of calculating the reception interval between the synchronization message received last time and the synchronization message received this time based on the recording result of the reception time, and comparing the calculated reception interval with the threshold value. The method includes a step and a step of discarding the synchronization message received this time when the calculated reception interval is less than or equal to the threshold value.

According to this method, when the reception interval between the previously received synchronization message and the currently received synchronization message is less than or equal to the threshold value, the currently received synchronization message is discarded, that is, a plurality of synchronization messages are sent within a fixed time. When they are sent, all but the first one is discarded, so even if a large number of synchronization messages are sent at once, damage can be prevented. Specifically, for example, even when a large number of synchronization messages are sent from a malicious third party, it is possible to avoid damages such as system down or paralysis of functions.

[0026]

BEST MODE FOR CARRYING OUT THE INVENTION Embodiments of the present invention will be described below in detail with reference to the drawings.

(Embodiment 1) FIG. 1 is a block diagram showing an example of the configuration of a terminal apparatus to which the synchronous message processing method according to Embodiment 1 of the present invention is applied.

This terminal device 100 is connected to a server 300 via a network 200, as shown in FIG. The terminal device 100 itself stores data to be data-synchronized, and an application unit 102 that receives a user operation for this data and an application unit 10
2 creates a synchronization message for synchronizing the data stored in 2 with the data in the server 300, and
Synchronization processing unit 104 that interprets the synchronization message received from 00, performs protocol processing to transmit the synchronization message created by the synchronization processing unit 104 to the network 200, and synchronizes the synchronization message received from the network 200 with the synchronization processing unit 104. And a protocol processing unit 106 that performs a protocol process in order to deliver to As a specific example of the application unit 102, for example, a phonebook application of a mobile phone can be cited. Data synchronization processing by SyncML is performed between the terminal device 100 and the server 300. Here, as described above, the “synchronization message” refers to an arbitrary message related to the data synchronization process, and includes the server alert message and the data synchronization process between the terminal device 100 and the server 300. Contains all the messages exchanged for.

The synchronization processing unit 104 sends the transmission data to Syn.
Converted to cML data format, and vice versa
Interpret the received data in the SYNCML format and convert it into the data structure of the data stored in the application unit 102.

If the received data is a synchronization message, the protocol processing unit 106 performs protocol processing until the data is returned to SyncML format data, and passes the processed data to the synchronization processing unit 104. However, in the present embodiment, in the case where this synchronization message is one of a plurality of synchronization messages received within a fixed time, the synchronization processing unit 10 can only perform when the synchronization message is the first data.
4 and discard otherwise. The operation of the protocol processing unit 106 will be described in detail later.

The terminal device 100 is, for example, a mobile phone, a mobile terminal, a personal computer, etc. (see FIG. 10), and as a hardware configuration, for example, as shown in FIG.
It includes a U 110, a ROM 112, a RAM 114, a transmission / reception chip 116, and a timer 118. CPU11
0 is the application unit 102, the synchronization processing unit 104,
And the processing of the protocol processing unit 106. ROM1
Reference numeral 12 stores a program that defines the operation of the CPU 110. The RAM 114 is used as a work area of the CPU 110. The transmission / reception chip 116 transmits / receives data via the network 200 of FIG. The timer 118 measures the reception time of data. Note that the program storage medium is not limited to the ROM, of course, and any recording medium suitable for storing the program (for example, flash memory or the like) can be used.

The load required for the CPU 110 to process the synchronization processing unit 104 and the application unit 102 is the CPU 11
0 is much larger than the load required for the processing of the protocol processing unit 106. Therefore, in this embodiment, the CP
In order to reduce the load on U110, the protocol processing unit 10
6, that is, before interpreting the synchronization message, without looking at the contents of the synchronization message, the received synchronization message is sent to the upper layer (the synchronization processing unit 104 or the application unit 10).
2) Decide whether to hand over or discard.

Next, the terminal device 100 having the above configuration
The operation of the protocol processing unit 106 will be described with reference to the flowchart shown in FIG. FIG. 3 shows the operation of the protocol processing unit 106 for realizing the synchronous message processing method according to this embodiment. The flowchart shown in FIG. 3 is stored in the ROM 112 as a control program and executed by the CPU 110.

First, in step S1000, the server 3
A message (data) is received from 00.

Then, in step S2000, protocol processing is performed on the message received in step S1000, and it is determined from the data format of the obtained data whether the received message is a synchronization message. If the message received as a result of this determination is not a synchronous message (for example, if it is a Web browser or e-mail message) (S200
0: NO), the process proceeds to step S3000, and if the received message is a synchronization message (S2000: Y).
ES), and proceeds to step S4000.

In step S3000, step S20
The message subjected to the protocol processing in 00 is passed to a higher-level module (for example, a Web browser or an electronic mail processing unit).

On the other hand, in step S4000, timer 1
The reception time of the message (synchronization message) measured by 18 is recorded in the RAM 114.

Then, in step S5000, the time interval between the reception time of the synchronization message measured this time and the reception time of the previous synchronization message recorded in RAM 114 is calculated.

Then, in step S6000, it is determined whether or not the time interval calculated in step S5000 is less than or equal to a preset threshold value. The threshold is, for example,
As an example, the processing time until the protocol processing unit 106 receives the server alert message and the synchronization processing unit 104 completes the processing of the message is set. If the time interval calculated as a result of this determination is less than or equal to the threshold value (S6000: YES), the process proceeds to step S7000, and if the calculated time interval is greater than the threshold value (S6:
000: NO), and proceeds to step S8000.

In step S7000, since the time interval from the previous reception is less than or equal to the threshold, that is, the reception time interval with the previously received synchronization message is within a fixed time, the synchronization message received this time is discarded. .

On the other hand, in step S8000, since the time interval since the previous reception is larger than the threshold value, that is, the reception time interval with the previously received synchronization message exceeds a certain time, the synchronization message received this time is ranked higher. It is passed to the synchronization processing unit 104 which is a module of.

Upon receiving the synchronization message from the protocol processing unit 106, the synchronization processing unit 104 interprets the synchronization message. Then, according to the content of the synchronization message, for example, the data synchronization process shown in FIG. 12 is performed.

In this operation, the CPU 110 executes the ROM
When the program that defines the processing of one layer stored in 112 is read and the data in the RAM 114 is read, the data that has been processed in that layer is again stored in the RAM 114.
It is done in the process of repeating writing to.

That is, the CPU 110 makes the server 300
When the data transmitted from the RAM 1 is received by the transmission / reception chip 116 and stored in the RAM 114, the data is transmitted to the RAM 1
The header is read out, the header is removed and the data is connected, and it is determined whether or not this data is a synchronization message (these processes may be executed in a plurality of steps by intermediating the RAM 114). If this data is not a synchronization message (NO in step S2000), it is stored in RAM 114. On the other hand, if this data is a synchronization message (step S200
If YES in 0), the processes of steps S4000 and S5000 are performed, and the determination of step S6000 is performed. Then, if YES in step S6000, the data is discarded without being returned to the RAM 114. on the other hand,
If NO in step S6000, the data is stored in RAM1.
Store in 14.

When the data is not a synchronous message, for example, a Web browser or electronic mail message, the CPU 110 reads the data from the RAM 114 and performs the process according to the corresponding program read from the ROM 112. Similarly, regarding the synchronization message stored in the RAM 114, the data is also RA
The synchronization message is interpreted according to the program read from the M114, read from the ROM 112, and the data synchronization process is executed.

Even if the terminal device 100 receives a large number of synchronization messages and the CPU 110 processes the interpretations of the synchronization messages one after another, the received synchronization messages are accumulated in the RAM 114 and the RAM 114.
In the state where the data overflows, the transmission / reception chip 116 cannot receive data, which may cause a system down.

However, in this terminal device 100, the synchronization message received at a short interval within a predetermined time (threshold value) is discarded without performing the message processing that requires a long processing time by the CPU 110. Even if you receive a large amount of, you can avoid system down.

At this time, even if the discarded synchronization message includes the originally required synchronization message (server alert message) for instructing synchronization, the terminal device 100 does not send the synchronization start request. In this case, since this synchronization message is sent again from the server 300, there is no problem. This point is very different from a Web browser or e-mail message that is not retransmitted when discarded.

As described above, according to the present embodiment, when a plurality of synchronization messages are sent within a fixed time,
Since everything other than the first one is discarded, even if a large number of synchronous messages are sent at once, damage can be prevented. Specifically, for example, even when a large number of synchronization messages are sent from a malicious third party, it is possible to avoid damages such as system down or paralysis of functions.

(Second Embodiment) The second embodiment is a case where a message sent from a server is not accidentally discarded during data synchronization processing.

Since the basic configuration of the terminal device according to this embodiment is the same as that of the terminal device according to the first embodiment shown in FIGS. 1 and 2, description thereof will be omitted. However, the present embodiment is different from the first embodiment in that the synchronization processing unit 104 sets a synchronization processing flag indicating that during synchronization processing (see (4) in FIG. 12).

As described above, the server alert message instructing the terminal device 100 to start synchronization by the server 300 is repeatedly sent from the server 300 unless the terminal device 100 sends a synchronization start request. But,
The message sent from the server 300 to the terminal device 100 during the synchronization process is not guaranteed to be retransmitted. Therefore, in the present embodiment, the synchronization processing unit 104 sets a synchronization processing flag during synchronization processing, and when this flag is set, the protocol processing unit 106 does not discard the synchronization message.

Next, the operation of the protocol processing unit 106 according to this embodiment will be described with reference to the flowchart shown in FIG. FIG. 4 shows the operation of the protocol processing unit 106 for realizing the synchronous message processing method according to this embodiment. The flowchart shown in FIG. 4 is stored in the ROM 112 as a control program and is executed by the CPU 110.

In the present embodiment, as shown in FIG. 4, step S2100 is inserted in the flowchart shown in FIG.

Steps S1000 and S20
00 is the same as each step of the flowchart shown in FIG. 3, and the description thereof will be omitted. However, in the present embodiment, if the received message is a synchronization message (S2000: YES), the process proceeds to step S2100.

Then, in step S2100, it is determined whether or not the synchronization processing flag is set in the synchronization processing unit 104. As a result of this determination, if the synchronization processing flag is not set (OFF) (S2100: YE)
S), the process proceeds to step S4000, and if the synchronization processing flag is set (S2100: NO), the process immediately proceeds to step S8000.

Steps S4000 to S8000
Is the same as each step of the flowchart shown in FIG. 3, and the description thereof will be omitted. However, in the present embodiment, when the time interval is less than the threshold value (S6000: N
In addition to (O), if the synchronization processing flag is set (S
2100: NO), the process of step S8000 is performed.

As described above, according to the present embodiment, the synchronization message to be discarded can be specified (limited) to the server alert message retransmitted from the server, and the synchronization processing can be surely executed.

(Embodiment 3) Embodiment 2 is a case where a whitelist is used to determine whether or not to discard a synchronization message.

Since the basic configuration of the terminal device according to the present embodiment is the same as that of the terminal device according to the first embodiment shown in FIGS. 1 and 2, description thereof will be omitted. However, in the present embodiment, the white list is stored in the RAM 114, and the protocol processing unit 106.
When deciding whether to discard the synchronization message,
The difference from the first embodiment is that the white list is referred to.

Next, the operation of the protocol processing unit 106 corresponding to this embodiment will be described using the flowchart shown in FIG. FIG. 5 shows the operation of the protocol processing unit 106 for realizing the synchronous message processing method according to this embodiment. The flowchart shown in FIG. 5 is stored in the ROM 112 as a control program and is executed by the CPU 110.

In the present embodiment, as shown in FIG. 5, step S6100 and step S6200 are inserted in the flowchart shown in FIG.

Steps S1000 to S6000
Is the same as each step of the flowchart shown in FIG. 3, and the description thereof will be omitted. However, in the present embodiment, when the time interval is equal to or less than the threshold value (S6000: Y
ES), and proceeds to step S6100.

Then, in step S6100, the transmission source of the received synchronization message is confirmed.

Then, in step S6200, it is determined whether or not the transmission source confirmed in step S6100 is on the white list. If the sender is not on the white list as a result of this determination (S6200:
No), the process proceeds to step S7000, and if the transmission source is on the white list (S6200: YES), the process proceeds to step S8000.

In step S7000, since the reception interval of the synchronization message is within the threshold and the sender is not on the white list, the synchronization message received this time is discarded.

On the other hand, in step S8000, the reception interval of the synchronization message exceeds the threshold value or the sender is on the white list, so that the synchronization message received this time is the synchronization processing unit 104 which is the upper module.
Pass to.

As described above, according to the present embodiment, it is possible to avoid discarding the synchronization message sent from the senders on the white list. Moreover, the way to use the whitelist in this case is not to limit the sender of the message to the senders on the whitelist as in the conventional case. Even if the change is made by the manufacturer, it is possible to receive the message from the change destination server.

As an additional function, it is possible to automatically add, to the white list, a transmission source that has been normally synchronized. In this case, for example, in the case of a web browser or an email message, the user needs to judge the content and decide whether or not the sender should be whitelisted. It is possible to automatically generate a whitelist by mechanically determining whether or not the processing has been normally completed, and if the processing is normally completed, the sender is placed on the whitelist.

(Embodiment 4) Embodiment 4 is a case where a whitelist is used to set (change) a threshold value for determining whether or not to discard a synchronization message.

Since the basic configuration of the terminal device according to this embodiment is the same as that of the terminal device according to the first embodiment shown in FIGS. 1 and 2, description thereof will be omitted. However, in the present embodiment, the white list is stored in the RAM 114, and the protocol processing unit 106.
Differs from the first embodiment in that this whitelist is used to determine the threshold value for determining whether to discard the synchronization message.

Next, the operation of the protocol processing unit 106 according to this embodiment will be described with reference to the flowchart shown in FIG. FIG. 6 shows the operation of the protocol processing unit 106 for realizing the synchronous message processing method according to this embodiment. The flowchart shown in FIG. 6 is stored in the ROM 112 as a control program and executed by the CPU 110.

In this embodiment, as shown in FIG. 6, step S5100, step S5200, step S5.
300 and step S5400 are inserted in the flowchart shown in FIG.

Steps S1000 to S5000
Is the same as each step of the flowchart shown in FIG. 3, and the description thereof will be omitted.

Then, in step S5100, the sender of the received synchronization message is confirmed.

Then, in step S5200, it is determined whether or not the transmission source confirmed in step S5100 is on the white list. If the sender is not on the white list as a result of this determination (S5200:
(NO), the process proceeds to step S5300, and if the transmission source is on the white list (S5200: YES), the process proceeds to step S5400.

In step S5300, the sender is not on the white list, so the threshold value is set to a large value, and the flow advances to step S6000. Specifically, for example,
The server alert message is received, and the synchronization processing unit 104
When the processing time until the processing of the message is completed is used as the reference time, a large threshold value is set when the CPU 110 wants to have a margin. In this case, for example, at the worst, only by processing the server alert message, C
In order to occupy only about 50% of PU 110, the threshold value is set to twice the reference time.

On the other hand, in step S5400, the sender is on the white list, so the threshold value is set to a small value, and the flow advances to step S6000. Specifically, for example, it is a case opposite to the case of increasing the threshold value described in step S5300. Further, in the case of the destination of the whitelist as in the present embodiment, the normal threshold value is set to 10 times the reference value to allow a margin, and only 1/10 (if it is on the whitelist ( 1/10).

Steps S6000 to S8000
Is the same as each step of the flowchart shown in FIG. 3, and the description thereof will be omitted. However, in this embodiment, the process of step S6000 is performed using the threshold value set in step S5300 or step S5400.

As described above, according to the present embodiment, it is possible to adjust the message discard condition depending on whether or not the sender is on the white list. For example, if the sender is not on the white list, the message discard condition can be tightened in the direction of discarding.

(Embodiment 5) Embodiment 5 is a case where a blacklist is used to determine whether or not to discard a synchronization message.

Since the basic configuration of the terminal device according to this embodiment is the same as that of the terminal device according to the first embodiment shown in FIGS. 1 and 2, description thereof will be omitted. However, in the present embodiment, the blacklist is stored in the RAM 114, and the protocol processing unit 106.
When deciding whether to discard the synchronization message,
The difference from the first embodiment is that the blacklist is referred to.

Next, the operation of the protocol processing unit 106 according to this embodiment will be described with reference to the flowchart shown in FIG. FIG. 7 shows the operation of the protocol processing unit 106 for realizing the synchronous message processing method according to this embodiment. The flowchart shown in FIG. 7 is stored in the ROM 112 as a control program and executed by the CPU 110.

In the present embodiment, as shown in FIG. 7, step S6100 and step S6300 are inserted in the flowchart shown in FIG. In comparison with the case of the third embodiment shown in FIG. 5, step S6300 is inserted into the flowchart shown in FIG.
It has a configuration in which 0 is deleted.

Steps S1000 to S6000
Is the same as each step of the flowchart shown in FIG. 3, and the description thereof will be omitted. However, in the present embodiment, when the time interval is equal to or less than the threshold value (S6000: Y
ES), and proceeds to step S6100.

Then, in step S6100, the transmission source of the received synchronization message is confirmed.

Then, in step S6300, it is determined whether or not the transmission source confirmed in step S6100 is on the black list. If the sender is on the blacklist as a result of this determination (S6300: Y
ES), the process proceeds to step S7000, and if the transmission source is not on the black list (S6300: NO), the process proceeds to step S8000.

In step S7000, since the reception interval of the synchronization message is within the threshold and the sender is on the black list, the synchronization message received this time is discarded.

On the other hand, in step S8000, the reception interval of the synchronization message exceeds the threshold value or the transmission source is not on the black list.
Pass to 4.

As described above, according to the present embodiment, the synchronization message can be discarded only when the reception interval of the synchronization message is equal to or less than the threshold and the transmission source is on the black list.

(Embodiment 6) Embodiment 6 is a case where a blacklist is used for setting (changing) a threshold value for determining whether or not to discard a synchronization message.

Since the basic configuration of the terminal device according to this embodiment is the same as that of the terminal device according to the first embodiment shown in FIGS. 1 and 2, description thereof will be omitted. However, in the present embodiment, the blacklist is stored in the RAM 114, and the protocol processing unit 106.
Differs from the first embodiment in that this blacklist is used to determine the threshold value for determining whether to discard the synchronization message.

Next, the operation of the protocol processing unit 106 according to this embodiment will be described with reference to the flowchart shown in FIG. FIG. 8 shows the operation of the protocol processing unit 106 for realizing the synchronous message processing method according to this embodiment. The flowchart shown in FIG. 8 is stored in the ROM 112 as a control program and is executed by the CPU 110.

In the present embodiment, as shown in FIG. 8, step S5100, step S5250, step S5.
300 and step S5400 are inserted in the flowchart shown in FIG. In comparison with the case of the fourth embodiment shown in FIG. 6, step S5250 is inserted in the flowchart shown in FIG. 6 and step S5200 is deleted.

Steps S1000 to S5000
Is the same as each step of the flowchart shown in FIG. 3, and the description thereof will be omitted.

Then, in step S5100, the transmission source of the received synchronization message is confirmed.

Then, in step S5250, it is determined whether the transmission source confirmed in step S5100 is on the black list. If the sender is on the blacklist as a result of this determination (S5250: Y
ES), the process proceeds to step S5300, and if the transmission source is not on the black list (S5250: NO), the process proceeds to step S5400.

In step S5300, the sender is on the blacklist, so the threshold value is set to a large value.
It proceeds to step S6000. Specifically, for example, in the case where the processing time until the synchronization processing unit 104 receives the server alert message and completes the processing of the message is set as the reference time, when the CPU 110 wants to have a margin, a large threshold value is set. To set. In this case, for example,
In the worst case, the CPU only processes the server alert message.
In order to occupy only about 50% of 110, the threshold value is set to twice the reference time. Further, as another example, when the transmission source is on the black list and is preferentially discarded, a large threshold value is set. In this case, for example, in order to suppress the processing of the message from the blacklisted sender to 10% of the CPU 110 at the worst, the threshold for the blacklisted sender is set to 10 times the reference time. Set to double.

On the other hand, in step S5400, since the transmission source is not on the black list, the threshold value is set to a small value, and the flow advances to step S6000. Specifically, for example, it is a case opposite to the case of increasing the threshold value described in step S5300.

Steps S6000 to S8000
Is the same as each step of the flowchart shown in FIG. 3, and the description thereof will be omitted. However, in this embodiment, the process of step S6000 is performed using the threshold value set in step S5300 or step S5400.

As described above, according to the present embodiment, it is possible to adjust the message discard condition depending on whether or not the sender is on the blacklist. For example, when the sender is on the blacklist, the discard condition of the message can be tightened in the direction of discarding.

(Embodiment 7) Embodiment 7 is a case where a blacklist is automatically generated.

Since the basic configuration of the terminal device according to this embodiment is the same as that of the terminal device according to the first embodiment shown in FIGS. 1 and 2, its description is omitted. However, in the present embodiment, the blacklist is stored in the RAM 114, and the protocol processing unit 106.
When deciding whether to discard the synchronization message,
With reference to this blacklist, if the same sender sends sync messages continuously for a short time,
This is different from the first embodiment in that this transmission source is added to the blacklist.

Next, the operation of the protocol processing unit 106 according to this embodiment will be described with reference to the flowchart shown in FIG. FIG. 9 shows the operation of the protocol processing unit 106 for realizing the synchronous message processing method according to this embodiment. The flowchart shown in FIG. 9 is stored in the ROM 112 as a control program and executed by the CPU 110.

In the present embodiment, as shown in FIG. 9, step S6100, step S6120, step S6.
140, step S6160, and step S630.
0 is inserted in the flowchart shown in FIG. In addition,
When compared with the case of the fifth embodiment shown in FIG. 7, step S6120, step S6140, and step S6.
It has a configuration in which 160 is inserted into the flowchart shown in FIG.

Steps S1000 to S6000
Is the same as each step of the flowchart shown in FIG. 3, and the description thereof will be omitted. However, in the present embodiment, when the time interval is equal to or less than the threshold value (S6000: Y
ES), and proceeds to step S6100.

Then, in step S6100, the transmission source of the received synchronization message is confirmed.

Then, in step S6120, the transmission source confirmed in step S6100 is stored in RAM 11 for example.
Record in 4.

Then, in step S6140, it is determined whether the synchronization message is continuously sent from the same transmission source by looking at the record of the transmission source. As a result of this determination, when the synchronization message is continuously sent from the same transmission source (S6140: YES), step S6160
If no synchronization message is continuously sent from the same transmission source (S6140: NO), go to step S6.
Proceed to 300.

In step S6160, since synchronization messages are continuously sent from the same transmission source, the transmission source is added to the black list, and the flow advances to step S6300.

Then, in step S6300, it is determined whether the transmission source confirmed in step S6100 is on the black list (including the addition in step S6160). If the transmission source is on the black list as a result of this determination (S6300: YES), the process proceeds to step S7000. If the transmission source is not on the black list (S6300: NO), step S80.
Go to 00.

At step S7000, since the reception interval of the synchronization message is within the threshold and the sender is on the black list, the synchronization message received this time is discarded.

On the other hand, in step S8000, the reception interval of the synchronization message exceeds the threshold value or the transmission source is not on the black list. Therefore, the synchronization message received this time is transmitted to the synchronization processing unit 10 which is the upper module.
Pass to 4.

As described above, according to the present embodiment, the synchronization message can be discarded only when the reception interval of the synchronization message is equal to or less than the threshold and the transmission source is on the blacklist. A blacklist can be automatically generated mechanically.

The present invention is not limited to the above-mentioned embodiments, but can be variously modified within the scope of the claims. For example, the features of each of the above embodiments are
It can be combined arbitrarily.

[0116]

As described above, according to the present invention,
Even if a large number of synchronization messages are sent from a malicious third party, it is possible to avoid the damage that the system goes down or the function is paralyzed.

[Brief description of drawings]

FIG. 1 is a block diagram showing an example of a configuration of a terminal device to which a synchronization message processing method according to a first embodiment of the present invention is applied.

2 is a block diagram showing an example of a hardware configuration of the terminal device shown in FIG.

FIG. 3 is a flowchart showing an operation of a protocol processing unit of the terminal device shown in FIG. 1 for realizing the synchronous message processing method according to the first embodiment.

FIG. 4 is a flowchart showing an operation of a protocol processing unit of the terminal device shown in FIG. 1 for realizing the synchronous message processing method according to the second embodiment of the present invention.

FIG. 5 is a flowchart showing an operation of a protocol processing unit of the terminal device shown in FIG. 1 for realizing the synchronous message processing method according to the third embodiment of the present invention.

FIG. 6 is a flowchart showing an operation of a protocol processing unit of the terminal device shown in FIG. 1 for realizing the synchronous message processing method according to the fourth embodiment of the present invention.

FIG. 7 is a flowchart showing an operation of a protocol processing unit of the terminal device shown in FIG. 1 for realizing the synchronous message processing method according to the fifth embodiment of the present invention.

FIG. 8 is a flowchart showing an operation of a protocol processing unit of the terminal device shown in FIG. 1 for realizing the synchronous message processing method according to the sixth embodiment of the present invention.

FIG. 9 is a flowchart showing the operation of the protocol processing unit of the terminal device shown in FIG. 1 for realizing the synchronous message processing method according to the seventh embodiment of the present invention.

FIG. 10 is a diagram showing an example of a system for performing data synchronization.

11 is a diagram showing an example of a data synchronization processing sequence in the system shown in FIG.

FIG. 12 is a diagram showing an example of a data synchronization processing sequence in SyncML.

FIG. 13 is a conceptual diagram for explaining an example of protocol processing in SyncML.

[Explanation of symbols]

100 terminal device 102 Application section 104 synchronization processing unit 106 Protocol processing unit 110 CPU 112 ROM 114 RAM 116 transceiver chip 118 timer 200 networks 300 servers

Claims (12)

[Claims] 1. A step of receiving data, a step of determining whether the received data is a synchronization message, and a step of recording a reception time of the received data when the received data is a synchronization message. , Calculating the reception interval between the previously received synchronization message and the synchronization message received this time based on the recording result of the reception time, comparing the calculated reception interval with a threshold value, and the calculated reception interval is less than or equal to the threshold value. In the case of, the synchronous message processing method including the step of discarding the synchronous message received this time. 2. The synchronous message processing method according to claim 1, wherein said discarding step is executed before interpreting the received data. 3. The synchronization message processing method according to claim 1, wherein the discarding step discards all received synchronization messages when the calculated reception interval is less than or equal to a threshold value. 4. The synchronization message according to claim 1, further comprising a step of determining whether or not data synchronization processing is being performed, wherein the discarding step does not discard the synchronization message when the data synchronization processing is being performed. Processing method. 5. The method further comprises the steps of confirming the source of the received synchronization message, and determining whether the source of the received synchronization message is on a white list, wherein the discarding step comprises: The synchronization message processing method according to claim 1, wherein the synchronization message received this time is discarded when the calculated reception interval is less than or equal to a threshold value and the sender of the received synchronization message is not on the white list. 6. The step of confirming the source of the received synchronization message, the step of determining whether or not the source of the received synchronization message is on a white list, and the source of the received synchronization message is a white list. Further comprising a step of setting a threshold value used in the comparison step according to whether or not the comparison step is performed, and the comparison step compares the calculated reception interval with the threshold value set in the setting step. 1. The synchronous message processing method described in 1. 7. A step of determining whether or not the data synchronization process has been normally completed based on the received synchronization message, and a step of determining whether the data synchronization process has been normally completed based on the received synchronization message. The method for processing a synchronous message according to claim 5 or 6, further comprising: adding a sender to a white list. 8. The method further comprises the steps of confirming the source of the received synchronization message, and determining whether the source of the received synchronization message is on a blacklist, the discarding step comprising: The synchronization message processing method according to claim 1, wherein the synchronization message received this time is discarded when the calculated reception interval is equal to or less than a threshold and the transmission source of the received synchronization message is on the blacklist. 9. The step of confirming the source of the received synchronization message, the step of determining whether the source of the received synchronization message is on a blacklist, and the source of the received synchronization message being blacklisted. Further comprising a step of setting a threshold value used in the comparison step according to whether or not the comparison step is performed, and the comparison step compares the calculated reception interval with the threshold value set in the setting step. 1. The synchronous message processing method described in 1. 10. If the calculated reception interval is less than or equal to a threshold value,
The step of confirming the sender of the synchronization message received this time, the step of recording the sender of the synchronization message received this time when the calculated reception interval is less than or equal to the threshold, and the reception calculated based on the recording result of the sender All the intervals are less than or equal to the threshold. The step of determining whether the source of the previously received synchronization message and the source of the currently received synchronization message are the same, and the calculated reception intervals are both less than or equal to the threshold. 10. The method further comprising: if the source of the previously received synchronization message and the source of the currently received synchronization message are the same, adding the source of the synchronization message to the blacklist. How to process synchronous messages. 11. A receiving means for receiving data, a judging means for judging whether or not the received data is a sync message, and a receiving means for judging that the received data is a sync message. Recording means for recording the reception time of the data; calculating means for calculating the reception interval between the previously received synchronization message and the currently received synchronization message based on the recording result of the recording means; A synchronization message processing device comprising: a comparison unit that compares a synchronization message with a threshold value; 12. A step of receiving data, a step of determining whether or not the received data is a synchronization message, and a step of recording a reception time of the received data when the received data is a synchronization message. , Calculating the reception interval between the previously received synchronization message and the currently received synchronization message based on the recording result of the reception time, comparing the calculated reception interval with a threshold value, and the calculated reception interval is less than or equal to the threshold value. In the case of, the step of discarding the synchronization message received this time, and the synchronization message processing program for causing the computer to execute.