JP2006287518A - Compression rule generation method, compression communication device, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To allow even a particularly low-capability device or a device for radio communication to compress and communicate data without being loaded, in transmitting and receiving data between devices. <P>SOLUTION: A compression rule is generated as follows; data to be transmitted/received is divided into prescribed units likes words; appearance frequencies etc. are analyzed per divided prescribed unit and are aggregated per data transmission source: and words or the like having high frequencies out of contents of data transmitted from a pertinent transmission source are selected by aggregated frequencies etc. to convert the data to information having a smaller data volume. Furthermore, the generated compression rule is reported to the transmission source by using an empty area of data to be necessarily transmitted/received on communication procedures. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a compression rule applied to a system for compressing / decompressing data to be transmitted / received when a device having a communication function capable of communicating with another communication device transmits / receives data to / from another device via the communication function. The present invention relates to a generation method, a compression communication device, and a program.

  In recent years, with the development of various communication technologies and network services and their spread to the general public, transactions and services via networks have become widely used not only for business transactions but also for services used by individuals. In addition, it is widely performed that a terminal device is connected to a server of each company or a server of a service provider to receive a business operation or a service.

  On the other hand, there are various types of terminal devices that perform operations for executing transactions and terminal devices that perform operations for using services. In addition to using a conventional stationary personal computer (personal computer) installed on a desk, there are many occasions where a portable personal computer or a mobile phone that can be carried is used.

  Furthermore, data transmitted and received between the server and the terminal device is often described in structured documents such as HTML (HyperText Markup Language) and XML (eXtensible Markup Language). Tends to be redundant due to the feature of data readability, and the amount of data is only increasing. The increase in the amount of data to be transmitted / received increases the load on the network. In particular, data is transmitted / received by wireless communication such as wireless LAN, infrared communication (IrDA (Infrared Data Association)), BLUETOOTH (registered trademark). If it is, it becomes easy to be affected by radio wave interference and battery shortage of the terminal device, data transmission / reception is not performed normally when executing transactions or using services, and hindering the execution of transactions or using services It is becoming more and more.

  In order to avoid such a situation, data to be transmitted / received is compressed to reduce the data amount and then sent to the network.

As a method for compressing data, gzip, which is a general file compression method, and methods disclosed in Patent Document 1, Patent Document 2, Non-Patent Document 1, and Non-Patent Document 2 specialized for XML are considered. Has been. In Patent Document 1, when message exchange based on the BtoB standard specification is performed, difference information between a past transaction and the current transaction is generated and transmitted to a trading partner, and the current transaction is calculated from the difference information and the past transaction. Is disclosed. Patent Document 2 discloses a technique in which a grammar rule is prepared in advance, a structured document to be transmitted is separated into a structure and a content, and a structure portion is compressed based on the grammar rule. For Non-Patent Document 1 and Non-Patent Document 2, detailed specifications are being formulated, but compression methods focusing on the structure of XML are being studied.
JP 2003-308444 A JP 2001-217720 A Robin Berjon et al., "XML Binary Characterization Working Group Public Page", [online], updated March 4, 2005, [searched March 16, 2005], Internet <URL: http://www.w3.org / XML / Binary /> Dennis M. Sosnoski, "XBIS XML Information Set Encoding", [March 16, 2005 search], Internet <URL: http://xbis.sourceforge.net/>

  However, when data is compressed, compression rules and programs must be prepared between communication devices that transmit and receive data (for example, a server and a terminal device, a desktop terminal device and a mobile terminal device, etc.). I must. In general, a general-purpose compression program or compression rule is provided in both sides for data transfer, and compression / decompression processing of data transmitted / received to / from each other is performed.

Alternatively, dictionary information used for data compression is added to the compressed data, and the compressed data and dictionary information are transmitted as a set as one file.
In the background art section described above, it is assumed that each has the same compression rule and compression program. In the compression / decompression method of gzip, Patent Document 1, Non-Patent Document 1, and Non-Patent Document 2, the processing content of the compression / decompression program becomes enormous, and in particular, the terminal device with low performance executes the compression / decompression program. As a result, the processing time in the terminal device is increased and the throughput of the entire processing is lowered. Also, in Patent Document 1, storing past transactions in the terminal device causes pressure on the storage capacity of the terminal device, so inquiring past transactions similar to the server side during compression processing, and similar It is necessary to identify past transactions to be generated and generate difference information, which increases the number of communication between the terminal device and the server, and is not suitable for compression processing of data transmitted and received between the terminal device and the server.

  Moreover, the performance characteristics differ for every terminal device, and it is not always desirable to apply the same compression rule and compression program uniformly.

  In particular, even in communication between a low-performance terminal device and a server, it is further required to enable compression / decompression processing of transmitted / received data without imposing a burden on the terminal device side and without increasing the number of communications. It has been.

  The inventor of the present application, for example, shows that the content of data transmitted and received between the server and the terminal device increases in similarity according to the business or service provided by the server, and further, for each user. We looked at the fact that the similarity is even higher. Further, attention has been paid to the fact that there is communication data having an area that is not used in the communication procedure among the communication data constantly transmitted and received between the server and the terminal device in accordance with the communication procedure.

  The character strings included in the data transmitted and received between the server and the terminal device are aggregated for each terminal device. For example, the frequently used character strings are extracted for each terminal device based on the aggregation result, and the usage frequency is extracted. It was devised to extract a character string having a high size, generate a compression rule for replacing the extracted character string with a character string having a small amount of data, and notify the terminal device of the generated compression rule.

  Furthermore, when data is transmitted / received between communication devices that transmit / receive data such as between a server and a terminal device, when data transmitted from either is received, the data is received from the data receiving side In many cases, a mechanism for notifying the transmission side is used, but only identification information (message ID, etc.) for identifying the received data is set in the notification data when notifying that the data has been received. In most cases, data of several tens to several hundreds of bytes is set. The unit of data sent from the server or terminal device to the communication network is, for example, generally Ethernet (registered trademark), the MTU (Maximum Transmission Unit) is 1500 bytes, and the header portion (about 40 bytes in the case of TCP). ), There are several hundred bytes of free space. If this free space is used, the generated compression rule can be held between the server and the terminal device without increasing the communication procedure and the number of communication between the server and the terminal device, and processing based on the same compression rule can be performed. It is possible to send and receive data that has been performed. Further, there is a case where a command (for example, a ping command / pong command) for confirming a connection state between communication devices is transmitted / received at a predetermined time interval between communication devices performing data transmission / reception. Also for these commands, the data set in the transmitted / received command may be about several bytes, and considering the MTU in the case of the above-described TCP, there are thousands of bytes of free space. Even when the compression rule is transmitted / received using this free area, the compression rule can be shared without transmitting / receiving excess communication data in the same manner. The present invention divides the data to be transmitted and received into predetermined units such as words, analyzes the appearance frequency for each divided predetermined unit, aggregates it for each data transmission source, Among the contents of data transmitted from the transmission source, a compression rule for selecting a frequently used word or the like and changing the information to a smaller amount of data is created. Furthermore, the generated compression rule is notified to the transmission source using a free area of data that is always transmitted and received in the communication procedure.

  That is, the invention of the present application is a rule generation method for generating a compression rule for compressing data transmitted and received between communication devices that are communicably connected with a communication function. When data sent from another communication device is received, the character string included in the received data is extracted, the appearance status of the extracted character string is aggregated for each character string, and the aggregated result is transmitted. Aggregate each other communication device and store it in the storage unit, and select the character string to be compressed when compressing the data according to the appearance status of the character string stored in the storage unit Then, a compression rule is generated by associating the selected character string with the data after compression processing, and the generated compression rule is stored in the storage unit in association with another communication device that is the transmission source of the data. Sent from another communication device In transmitting the reception notification to chromatography data, and transmits the compression rule stored in association with the other communication apparatus together with the received notification.

  According to the first, second, fourth, and fifth aspects of the present invention, a data compression rule is generated based on the content of the received data and notified to the data transmission source. A compression rule is generated. In addition, by sending compression rules (including dictionary information used for compression) together with data that must be sent and received during communication procedures such as data reception notification, compression is performed without increasing the number of message processing to the communication partner. It becomes possible to share rules. Especially in the mobile communication environment, since communication is frequently disconnected, the increase in the number of messages to be transmitted increases the communication risk that causes a failure such as transmission / reception failure. Since it is possible to share compression rules without increasing the number of transmission / reception, it is possible to transmit / receive data with compression / decompression processing without degrading communication quality even in a mobile communication environment.

  According to the third aspect of the present invention, in order to generate a compression rule based on data transmitted / received to / from another communication apparatus and notify the data transmission source even when there is no data transmitted / received in the past. Immediately after the start of data transmission / reception, the compression rule can be shared and the compression process can be performed.

  Furthermore, according to the invention of claim 4, since it is possible to generate a compression rule not only based on received data but also based on transmission data, it is possible to transmit data with a communication device having a large capability difference. It is possible to generate and notify a compression rule on the higher communication device side.

  FIG. 1 is a diagram for explaining the principle of the present invention.

  The devices 1 and 2 can communicate with each other via the communication network 3. In order to simplify the explanation, only two devices, the device 1 and the device 2, are connected to the communication network 3, but there may be a plurality of devices 1 and 2 connected to the communication network 3. Good. The communication network 3 may also be configured by a plurality of communication networks 3 that are physically and logically different as long as the device 1 and the device 2 can communicate with each other. Furthermore, in order to simplify the description, the apparatus 1 is assumed to be a receiving side apparatus and the apparatus 2 is assumed to be a transmitting side apparatus, and only the minimum necessary functions are described and described. In the following description, the device 1 may be referred to as “receiving device 1” and the device 2 as “transmitting device 2”.

  The device 1 as a receiving device includes a control unit 10, an application 11, a rule storage unit 12, a rule generation unit 13, a rule notification unit 14, a compression / decompression unit 15, a data reception unit 16, and a reception notification transmission unit 17.

  The control unit 10 performs overall control of the device 1.

  The application 11 is a program necessary for inter-business transactions, execution of services provided to users, and the like, and generates data to be transmitted between the devices 1 and 2 and processes received data.

  The data receiving unit 16 receives data transmitted from another device 2 via the communication network 3.

  The compression / decompression unit 15 restores data according to the rules stored in the rule storage unit 12 when the data received by the data reception unit 16 has been shortened (compressed).

  The rule generation unit 13 divides the data received by the data reception unit 16 into predetermined units, totals the number of appearances in the divided units, and accumulates the aggregation results for a predetermined period. Select a character string that is judged to be effective for reducing the amount of data to be transmitted / received based on the accumulated results, and shorten the selected character string and the shortened character to shorten (compress) the character string. The columns are associated with each other and stored in the rule storage unit 12. Thus, the most effective data compression rule (hereinafter, the compression rule may be referred to as “rule”) is generated in accordance with the state of the character string included in the received data. As a unit for dividing data, for example, a method of dividing into words by performing part-of-speech analysis, or in a structured document such as XML, generated during an analysis result of an analysis program of a structured document such as an XML parser or analysis processing The intermediate results are used to perform processing according to the target data, such as a method of separating the tag and data portion and classifying the contents of the tag and data. In addition, as a selection method of the character string to be shortened, select from the highest appearance frequency, select from the longest number of characters in the character string, select from the appearance tendency of the character string, select a combination of each selection method The method of doing is conceivable.

  When the data reception unit 16 receives data, the reception notification transmission unit 17 notifies the transmission source that the data has been received. The timing of notifying that data has been received may be performed every time data is received, or may be performed every time a predetermined number of times are received. In the case where it is defined in the protocol rules, the operator or the user sets a desired timing in accordance with the rules when the system or application can control the rules. Furthermore, in the present invention, when the reception notification transmission unit 17 notifies the transmission source that the data has been received, the rule stored in the rule storage unit 12 is notified using the free space of the message to be notified. To do. Thereby, it is not necessary to newly transmit / receive data for notifying the shortening (compression) rule for each transmission source, and it is possible to notify the rule without increasing the communication load.

  The device 2 as a transmission side device includes a control unit 20, an application 21, a rule storage unit 22, a compression / decompression unit 25, a data reception unit 26, a rule reception unit 28, and a data transmission unit 29.

  The control unit 20 performs overall control of the device 2.

  The application 21 is a business application, processes data received by the data receiving unit 26, and generates data to be transmitted via the data transmitting unit 29.

  The data receiving unit 26 receives data transmitted from the device 1 via the communication network 3.

  The rule receiving unit 28 obtains a rule included in the received data when the data received by the data receiving unit 26 is a reception notification of data transmitted from the device 1 to the device 2, and the rule storage unit 22 to store.

  The rule storage unit 22 stores a rule for shortening (compressing) data sent to the communication network 3. The rule is received via the data receiving unit 26 and the rule receiving unit 28 as described above.

  The compression / decompression unit 25 changes the corresponding portion of the data in accordance with the rules stored in the rule storage unit 22.

  The data transmission unit 29 sends the data subjected to the shortening (compression) processing by the compression / decompression unit 25 to the communication network 3.

  The basic flow of the present invention will be described with reference to FIG.

  When the transmission data to be transmitted to the reception side device 1 is generated by the application 21 in the transmission side device 2 (# 21 in FIG. 2), the compression / decompression unit 25 follows the rules stored in the rule storage unit 22. Based on this, the transmission data is shortened (compressed) (# 22 in FIG. 2). Note that the data shortening process is not executed when the data shortening process cannot be executed, such as when no rule is stored in the rule storage unit 22. After performing the shortening (compression) process on the transmission data, the shortened (compressed) data is transmitted to the receiving apparatus 1 (# 23 in FIG. 2).

  In the receiving apparatus 1, when the data receiving unit 16 receives the data transmitted from the transmitting apparatus 2 (# 11 in FIG. 2), it is determined whether or not the received data is subjected to a shortening (compression) process. judge. When the received data has been shortened (compressed), the compression / decompression unit 15 restores the received data based on the rules stored in the rule storage unit 12 (# 12 in FIG. 2). The rule generation unit 13 performs part-of-speech analysis, grammatical analysis, structured document analysis, etc. on the restored received data according to the characteristics of the data, and divides the received data into predetermined units (character strings) Then, the appearance frequencies are totalized in the divided units (character strings), and the totaled results are accumulated and accumulated for each transmitting side apparatus 2 for a predetermined period (# 13 in FIG. 2). The rule generation unit 13 selects a predetermined unit (character string) to be shortened (compressed) based on the appearance frequency of each stored predetermined unit (character string), and selects the predetermined unit (character string). A rule for performing shortening (compression) processing is generated in association with the shortened character string, and the generated rule is stored in the rule storage unit 12 (# 14 in FIG. 2). The reception notification transmission unit 17 generates a data reception notification message for notifying the transmission side device 2 of the data reception status based on the reception data received by the data reception unit 16, and further generates the generated data reception notification. The contents of the rules of the transmission side device 2 stored in the rule storage unit 12 are set in the free space of the message, and a data reception notification message including the rules of the transmission side device 2 is transmitted to the transmission side device 2 (FIG. 2). # 15).

  In the transmission side device 2, when the data reception unit 26 receives the data reception notification message (# 24 in FIG. 2), the rule for the transmission side device 2 included in the reception notification message is acquired and stored in the rule storage unit 22. (FIG. 2 # 25). Thereafter, transmission data is shortened (compressed) based on the rules stored in the rule storage unit 22 until the reception notification message is received and the rules are updated.

  The above is the basic configuration and processing flow of the present invention.

Specific examples of the present invention will be described below.
<First Embodiment>
In the first embodiment, the transmission-side apparatus 2 is a server 200 that provides an online shopping service, and the reception-side apparatus 1 connects to the server 200 via the communication network 3 to enjoy the online shopping service. Description will be made assuming that the terminal device 100 and data transmitted and received between the server 200 and the terminal device 100 are described in XML. In the following description, data described in XML transmitted / received between the server 200 and the terminal device 100 is referred to as XML data. FIG. 3 is a diagram illustrating a configuration of the first embodiment.

  The server 200 and the terminal device 100 are connected via the communication network 3. As described above, there can be a plurality of servers 200 and terminal devices 100. However, in order to simplify the description, only one server 100 and one terminal device 200 are described.

  The terminal device 100 includes a control unit 10, an online shopping client program 11, a rule storage unit 12, a rule generation unit 13, a transmission data compression unit 151, a reception data restoration unit 152, a data reception unit 16, a reception notification transmission unit 17, and data reception Unit 19 and a communication interface (I / F) 1C. Portions having the same configuration as that described in the above principle diagram are denoted by the same reference numerals, and description thereof is omitted. The transmission data compression unit 151 and the reception data restoration unit 152 correspond to the compression / decompression unit 15 in FIG. The transmission data compression unit 151 acquires the XML data output from the online shopping client program 11 to be transmitted to the server 100, and based on the rules stored in the rule storage unit 12, the acquired XML data A shortening (compression) process is performed, and the data transmission unit 19 is requested to transmit the shortened (compressed) XML data. The reception data restoration unit 152 receives the XML data received by the data reception unit 16 and, based on the rules stored in the rule storage unit 12 when the received XML data is subjected to shortening (compression) processing. The XML data is restored. The rule generating unit 13 includes a received data totaling unit 131, a totaling data storage unit 132, and a rule determining unit 133. The received data totaling unit 131 performs XML structural analysis on the XML data restored by the received data restoring unit 152, divides the tags and values included in the XML data, and the appearance frequency for each of the same tags and values. Is counted. The tabulated results are accumulated and stored in the tabulated data storage unit 132 for each transmission source server 200. The rule determination unit 133 selects a tag or value to be shortened (compressed) from the appearance frequency of the tag or value stored in the total data storage unit 132, and associates the selected tag or value with a shortened symbol. Generated and stored in the rule storage unit 12.

  The server 200 includes a control unit 20, an online shopping program 21, a rule storage unit 22, a rule generation unit 23, a transmission data compression unit 251, a reception data restoration unit 252, a data reception unit 26, a reception notification transmission unit 27, and a data transmission unit 29. And a communication interface (I / F) 2C. Portions having the same configuration as that described in the above principle diagram are denoted by the same reference numerals, and description thereof is omitted. The transmission data compression unit 251 and the reception 200 restoration unit 252 correspond to the compression / decompression unit 25.

  The online shopping program 21 of the server 200 generates XML data for displaying a screen for introducing a handling product, purchasing a product, etc. to a user of the terminal device 100, and sends it to the terminal device 100. The data is displayed on the display device of the terminal device 100, and the terminal device 100 generates XML data for requesting product introduction information and purchasing a product according to an input operation from the user, and the server 200. To send. Various known techniques are used for using the online shopping service. Since the present invention is an invention related to a method for shortening (compressing) data transmitted and received between devices in an online shopping service, a detailed description of an implementation form of the online shopping service is omitted.

  Based on FIG. 4, a flow of processing from generation of a rule for shortening (compressing) the XML data based on the received XML data to notification to the transmission source will be described.

  In the server device 200, the XML data 61 for the terminal device 100 is generated by the online shopping program 21 and sent to the terminal device 100. An example of the XML data 61 generated by the server device 200 is shown in FIG. The XML data 61 shown in FIG. 6A is an example described according to the Xforms convention. Xforms is a form specification for adding an input function by a viewer to an XML document, and was established in W3C (World Wide Web Consortium) in October 2003.

  When the terminal device 100 receives the XML data 61 sent from the server 200 by the data receiving unit 16 (# 41 in FIG. 4), whether or not the shortened processing (compression) processing is performed on the received XML data 61. Is determined (# 42 in FIG. 4). When the shortening (compression) process has been performed (Yes in # 42 of FIG. 4), the reception data restoration unit 152 restores the received XML data based on the rules stored in the rule storage unit 12 (FIG. 4). # 43). If the shortening (compression) process has not been performed (No in # 42 of FIG. 4), the process proceeds to # 44.

  The received data totaling unit 131 decomposes the received XML data or the restored XML data into tags and values in accordance with the XForms grammatical rules (# 45 in FIG. 4). The appearance frequency is counted for each decomposed tag or value, and stored in the total data storage unit 132 in association with the number of times counted for each decomposed tag or value (# 46 in FIG. 4).

  An example of the aggregation table stored in the aggregation data storage unit 132 is shown in FIG. The tabulation table is composed of a character string 71 and items of the number of times 72. In the item of the character string 71, a character string of tags and values obtained by decomposing the received XML data is stored. In the item of the number of times 72, the number of appearances of the aggregated tag and value is stored. The total number of appearances of tags and values is accumulated for each transmission source server. In the example of FIG. 7, the number of appearances of only the tag is counted, and the number of appearances is stored for each tag.

  The rule determination unit 133 refers to the total data storage unit 132, selects a character string to be shortened, and associates it with a character string after shortening (in the following description, it may be referred to as “abbreviated symbol”). And stored in the rule storage unit 12 (# 46 in FIG. 4). Here, as a method for selecting a character string to be shortened, the aggregation table is sorted in descending order of the number of characters of the character string 71 and the number of appearances 72, and the character string is selected in descending order of the number of characters and the number of appearances. . In addition to this selection method, selection may be made from those having a large number of appearances, or from those having a large number of characters in the character string. In addition, the probability that a character string is included in XML data recognized as one unit is calculated, the average value of the probability is accumulated for each character string, and may be included in the XML data. You may make it select from a high character string. Also in this case, selection may be made in combination with the number of characters in the character string. Note that the selection criteria may be determined using any of various statistical analysis methods and unique analysis methods as long as the selection method can more effectively shorten (compress) the XML data transmitted and received. The selected character string is stored in the rule table 80 of the rule storage unit 12 in association with the shortened symbol. An example of the rule table 80 stored in the rule storage unit 12 is shown in FIG. The rule table 80 includes a shortened symbol field 81 and a character string field 82. The abbreviated symbol column 81 stores abbreviated symbols associated with the selected character string. In the example of FIG. 8, the abbreviated symbol is a two-digit character string made up of a one-digit character string “@ (at mark)” and a one-digit number. The contents and style of the abbreviated symbols are not limited to this example, so that it is possible to determine whether the character string is used as the abbreviated symbol or the character string used as the content of normal data. It is desirable that the contents of the data to be transmitted / received are set so that the contents and format are not normally included. In order to improve the data shortening rate, it is desirable that the data be expressed with as few character strings as possible.

  The reception notification transmission unit 17 determines whether or not it is time to send a data reception notification message 90 for notifying the transmission source of the data reception status every time it is received by the data reception unit 16 (# in FIG. 4). 47). The timing for notifying the data reception status can be arbitrarily set, for example, every time data is received or after a predetermined number of cases are received, and is determined according to the set timing. If it is determined that it is time to send the data reception notification message 90 (Yes in # 47 in FIG. 4), for the data received after the previous reception notification, the message ID included in the received data is displayed. To generate a data reception notification message 90. An example of the packet of the data reception notification message 90 is shown in FIG. The upper two stages in the drawing show the packet structure, and an example of the contents of data set in the third stage. The packet is roughly divided into a header part 91 and a body part 92. In the header section 91, control information such as a transmission destination address and a transmission source address is set according to the communication protocol being used. The body portion 92 includes a message ID column 93 for setting information for specifying received data to be notified, and a rule column 94 for setting rules stored in the rule storage unit 12. In the message ID column 93, information that can identify received data, such as a message ID included in received data that is a target of reception notification, is set. In the rule column 94, the contents of the rules stored in the rule storage unit 12 in association with the server 200 that is the notification destination of the reception notification message are set. The packet size of the data reception notification message is an MTU (Maximum Transmission Unit) value determined depending on the communication protocol used in the communication network 3 or the like. In the example of FIG. 9, 1500 bytes, which is the optimum value in the Ethernet environment, is assumed. From 1500 bytes, the length of the header portion 91 (40 bytes in the case of TCP) and the length of the message ID column 93 (for example, 30 bytes to several tens of bytes depending on the number of data to be notified of reception) are subtracted. The remaining length becomes the length of the rule column 94. It is desirable to set the number of abbreviated symbols 81 that can be registered in the rule table 80 according to the length of the rule column 94. In the example of Fig. 9, the contents of the rules illustrated in Fig. 8 are listed for each combination of the short symbol 81 and the character string 82, separated by a delimiter (in this example, ", (comma)"). When the generation of the notification message 90 is completed, the notification message 90 is transmitted to the transmission source server 200 (# 49 in FIG. 4).

  Note that steps # 41 to # 49 in FIG. 4 do not necessarily have to be executed as a series of processes, and the processes from # 41 to # 46 and the processes from # 47 to # 49 may be executed asynchronously. Good.

  Based on FIG. 5, the flow from when the data reception notification message 90 is received until the transmission data is shortened (compressed) will be described.

  When the data is received by the data receiving unit 26 (# 51 in FIG. 5), the server 200 determines whether or not the received data is the data reception notification message 90 (# 52 in FIG. 5). In the case of the data reception notification message 90, the rule contents are acquired from the rule column 94 of the data reception notification message 90, and the acquired rule contents are stored in the rule table 80 of the rule storage unit 22. The contents of the rule table 80 have the same configuration as that illustrated in FIG. The rule table 80 is stored in association with the identification information of the terminal device 100 that is the transmission source of the data reception notification message 90.

  The transmission data compression unit 251 monitors whether or not transmission data is generated (# 54 in FIG. 5), and when transmission data is generated (Yes in # 54 in FIG. 5), the transmission data transmission destination The rule table 80 stored in association with the terminal device 100 is acquired from the rule storage unit 22 (# 55 in FIG. 5). It is determined whether there is a character string 82 registered in the rule table 80 acquired in the transmission data 61 (# 56 in FIG. 5). If it is determined that the character string 82 exists (Yes in # 56 in FIG. 5), the detected character string is replaced with a shortened symbol 81 associated with the character string 82 (# 57 in FIG. 5). . It is confirmed whether or not all the character strings included in the transmission data have been replaced. If the replacement has not been completed (No in FIG. 58), the process returns to # 57 to replace the character string 82 with the short symbol 81. repeat. When the replacement is completed (Yes in # 58 in FIG. 5), the transmission data 62 in which the character string 82 stored in the rule table 80 is replaced with the corresponding short symbol 81 is transmitted to the destination terminal device 100 (FIG. 5). # 59).

  Note that steps # 51 to # 59 and # 591 to # 593 in FIG. 5 do not necessarily have to be executed as a series of processes, and the processes from # 51 to # 53 and # 591 to # 593 and # 54 to # 59 are not necessarily executed. The processes up to # 59 may be executed asynchronously.

  As described above, the XML data transmitted from the server 200 to the terminal device 100 is decomposed into tags and values according to the grammatical rules, the appearance status is analyzed for each decomposed tag and value, and based on the analysis result. , Generate a rule table to reduce the amount of data to be transmitted, and notify the server of the generated rule table, so that both sides have a data compression program that covers all the expected conversion rules Without this, it is possible to realize a data shortening process that is optimal for the content of data transmitted and received between the terminal device 100 and the server 200. In addition, since the transmission / reception of the generated rule table is also performed using the empty area of the received notification of the transmitted data, the rule table is not transmitted without transmitting / receiving extra data to transmit / receive the rule table. Notification can be made, and communication network compression accompanying transmission / reception of the rule table can be avoided.

In the above description, the procedure for generating a rule for each server 200 on the terminal device 100 side based on the data transmitted from the server 200 to the terminal device 100 has been described. The rule generation unit 23 may generate a rule for each terminal device 100 on the server 100 side based on the data transmitted to the server 100 and notify the terminal device 100 from the server 200. In this case, when the appearance tendency of the character string included in the data transmitted from the server 200 to the terminal device 100 is different from the appearance tendency of the character string included in the data transmitted from the terminal device 100 to the server 200. Because a rule table corresponding to each appearance tendency is generated and notified, even when data is transmitted between the same devices, even if the characteristics of the transmitted data differ depending on the direction, respectively. It is possible to perform a shortening (compression) process according to the direction of this.
<Second Embodiment>
In the first embodiment, the rule table 80 is generated on the data receiving side and notified to the data transmission source. However, in the case of a terminal device with low capability, the process of generating the rule table is a heavy load. It may be possible. In the second embodiment, in order to solve this, not only a rule table of data received from the terminal device is created on the high-capacity device side such as a server, but also based on data sent to the terminal device, A mechanism for generating a rule for data transmitted from the server to the terminal device and notifying the terminal device will be described.

  In the example of the second embodiment, a case where data is transmitted from the terminal device 400 to the server 300 is referred to as “uplink”, and a case where data is transmitted from the server 300 to the terminal device 400 is referred to as “downlink”.

  FIG. 10 is a diagram illustrating a system configuration according to the second embodiment.

  In addition, about the part which has the same function as 1st Embodiment, the same referential mark is attached | subjected and detailed description is abbreviate | omitted. As in the first embodiment, data transmitted / received between the server 300 and the terminal device 400 is described in XML.

  In the second embodiment, the rule generation unit 13 exists only on the server 300 side. In addition to the received data totaling unit 131, total data storage unit 132, and rule determining unit 133, the transmission data totaling unit 134 is added to the rule generation unit 13 of the server 300.

  Since the method for generating the rule table based on the data received from the terminal device 400 is the same as that in the first embodiment, the description thereof is omitted.

  An example of creating a rule table based on data transmitted from the server 300 to the terminal device 400 and notifying the terminal device 400 will be described.

  When data to be transmitted from the application 11 to the terminal device 400 is generated (# 1101 in FIG. 11 [similar to # 21 in FIG. 2]), the transmission data totaling unit 134 converts the transmission data generated by the application 11 into data. The analysis is performed according to the grammatical rules, etc., and is decomposed into tags and values (# 1102 in FIG. 11). The number of appearances is counted for each decomposed tag and value, and recorded in the total data storage unit 132 (# 1103 in FIG. 11). ). An example of the total table of the total data storage unit 132 is shown in FIG. In the second embodiment, the management table 1300 records not only the total result of data transmitted from the terminal device 400 to the server 300 but also the total result of data transmitted from the server 300 to the terminal device 400. For each terminal device 400, the data aggregation table 1310 transmitted from the terminal device 400 to the server 300 and the data aggregation table 1320 transmitted from the server 300 to the terminal device 400 are managed in a distinguishable manner. ing. The management table 1300 includes a terminal ID column 1310, a direction column 1302, and a table ID column 1303. The terminal ID column 1301 stores an identifier for identifying the terminal device 400 that is a transmission destination of data transmitted to the server 300 or a reception source of data transmitted from the server 300. When the terminal ID is included in the message ID included in the transmitted / received data, the identifier is acquired, or the address information of the transmission source or the transmission destination is used. The direction column 1302 stores information indicating which direction of the up / down direction the aggregation table is, and stores either “up” or “down”. The table ID column 1303 stores an address on the storage device in which each table is stored. The aggregation tables 1310 and 1320 (FIGS. 13B and 13C) stored at the address specified in the table ID column 1303 have the same configuration as the aggregation table illustrated in FIG.

  The rule determining unit 133 generates a rule table based on the total result stored in the total data storage unit 132 and stores it in the rule storage unit 12. The rule table generation method is the same as that described in the first embodiment. An example of the rule table stored in the rule storage unit 12 is shown in FIG. Similarly to the aggregation table, the management table 1400 can identify whether the rule table is a rule table 1410 for upstream data (FIG. 14B) or a rule table 1420 for downstream data (FIG. 14C). To manage. The management table 1400 includes a terminal ID column 1401, a direction column 1402, a table ID column 1403, and a notification flag column 1404. The terminal ID column 1401 stores an identifier for identifying the terminal device 400 that is a transmission source of data transmitted to the server 300 or a reception destination of data transmitted from the server 300. When the terminal ID is included in the message ID included in the transmitted / received data, the identifier is acquired, or the address information of the transmission source or the reception destination is used. The direction column 1402 stores information indicating whether the rule table is an up / down direction table, and stores either “up” or “down”. The table ID column 1403 stores an address on the storage device in which each table is stored. The notification flag column 1404 can be a flag indicating whether or not the rule table has been notified to the terminal device 400. In the example of FIG. 14, information indicating “completed” when notified, and information indicating “not yet” when not notified yet are stored. Since the notification of the rule table to the terminal device 400 is performed at the time of the data reception notification for notifying that the data has been received from the server 300 in response to the data being transmitted from the terminal device 400 to the server 300, the server is particularly With respect to the downlink rule table generated based on the data transmitted from 300 to the terminal device 400, the rule table is not notified to the terminal device 400 in real time, so the newly generated rule table is sent to the terminal device 400. Until notified, it is necessary to keep it together with the notified rule table. The rule tables 1410 and 1420 stored at the address specified in the table ID column 1403 have the same configuration as the rule table illustrated in FIG. In the upstream rule table 1410 of terminal ID: Terminal-01, rules determined based on data received from the terminal device 400 are stored. The downstream rule table 1420 of terminal ID: Terminal-01 stores rules determined based on data transmitted from the server 300 to the terminal device 400. For example, all of the display-only contents and input items are transmitted from the server 300 to the terminal device 400, but the data transmitted from the terminal device 400 to the server 300 is only the contents related to the input items. If there is a character string, the character string having a high number of appearances is different between upstream and downstream.

  When transmission data to be transmitted to the terminal device 400 is generated (# 1101 in FIG. 11), the terminal device 400 is notified in the rule table stored in association with the terminal ID of the transmission destination terminal device 400. The contents of the completed down rule table are acquired from the rule storage unit 12 (# 1110 in FIG. 11). In the example of FIG. 14, the rule table with the table ID “TBLD-01” is acquired. I got it. The transmission data is shortened (compressed) based on the acquired rule table (# 1112 in FIG. 11).

  Next, based on FIG. 12, the process which notifies the terminal device 400 of the produced | generated rule table is demonstrated.

The reception notification transmission unit 17 monitors whether it is the transmission timing of the data reception notification message,
When it is determined that it is the transmission timing (Yes in # 1201 of FIG. 12), it corresponds to the terminal ID of the terminal device 400 that is the transmission source of the target received data in the rule table stored in the rule storage unit 12. Then, the contents of the rule table which is the uplink and downlink rule table stored in addition and the notification flag is “not yet” is acquired (# 1202 in FIG. 12). The contents of the acquired rule table are set in the rule column 94 of the data reception notification message 90, and a data reception notification message is generated (# 1203 in FIG. 12). An example of the data reception notification message is shown in FIG. The structure of the data reception notification message 90 is the same as the structure illustrated in FIG. Similarly to FIG. 9, the packet configuration is shown in the upper two stages of the drawing, and an example of the contents of data set in the third stage is shown. The example shown in FIG. 15A is an example in which the contents of the uplink and downlink rule tables are listed as they are. In this example, the contents of the upstream rule table are listed in the first half of the rule column 94 as a combination of a shortened symbol and a character string, and the contents of the downstream rule table are listed in the second half as a combination of a shortened symbol and a character string. Yes. The example shown in FIG. 15B is an up-and-down rule table, and in the case of having a common character string, in order to shorten the length of the rule column 94, the up-and-down rule table is mixed. It is enumerated. For example, since the character string “xfroms: model” is present in both the upstream rule table and the downstream rule table, the short symbol “@ 1” in the upstream rule table and the short symbol “# 1” in the downstream rule table. It is enumerated in the form of a combination of "and the string" xfroms: model ". When there is only an uplink rule table or only a downlink rule table, as in the example of FIG. 15A, a combination of a shortened symbol and a character string registered in the uplink rule table or the downlink rule table is used. It is enumerated. This makes it possible to reduce the amount of data when notifying the terminal device of the rule table.

  Based on FIG. 16, the reception process on the terminal device 400 side will be described.

  When the received data is detected (Yes in # 1601 in FIG. 16), the data receiving unit 26 determines whether or not the received data is a data reception notification message 90 for the data transmitted by the terminal device 400 (FIG. 16). 16 # 1602). When it is determined that the data reception notification message 90 is received (Yes in # 1602 in FIG. 16), the contents of the rule table are acquired from the rule column 94 of the data reception notification message 90, and the contents of the upstream rule table or the downstream rule table are acquired. Is stored in the rule storage unit 22 (# 1603 in FIG. 13). FIG. 17 shows an example of the contents of the rule table in the rule storage unit 22 of the terminal device 400. The rule table is managed by the management table 1700 so as to be able to identify the rule table 1710 for upstream data or the rule table 1720 for downstream data for each server that transmits and receives data. The management table 1700 includes a server ID column 1701, a direction column 1702, and a table ID column 1703. The server ID column 1701 stores an identifier for identifying the server 300 that is a transmission source of data transmitted to the terminal device 400 or a reception destination of data transmitted from the terminal device 400. When the server ID is included in the message ID included in the transmitted / received data, the identifier is acquired, or the address information of the transmission source or the transmission destination is used. The direction column 1402 stores information indicating whether the rule table is an up / down direction table, and stores either “up” or “down”. The table ID column 1403 stores an address on the storage device in which each table is stored. The rule tables 1710 and 1720 stored at the address specified in the table ID column 1703 have the same configuration as the rule table illustrated in FIG. If the received data is not a data reception notification message (No in # 1602 in FIG. 16), it is determined whether the received data is XML data (# 1610 in FIG. 16). If the received data is XML data, the rule table ID included in the received data is acquired, the contents stored in the rule storage unit 12 are acquired (# 1611 in FIG. 16), and the rule of the acquired rule is acquired. The part where the shortening process is performed is restored based on the contents (# 1612 in FIG. 16). If the received data is not XML data (No in # 1610 in FIG. 16), other appropriate processing is performed (# 1620 in FIG. 16).

  An example of data transmission on the terminal device 300 side will be described based on FIG. When the transmission data compression unit 251 detects that transmission data from the application 21 to the server 300 has been generated (# 1801 in FIG. 18), the upstream rule table associated with the server ID of the destination server 300 Is obtained from the rule storage unit 22 (# 1802 in FIG. 18). Based on the contents of the acquired rule table, the transmission data is shortened (compressed). At this time, it is desirable to embed the table ID of the used rule table in the data so that it can be identified in which rule table the shortening (compression) processing has been performed. After performing the shortening (compression) process, the data transmission unit 29 transmits the shortened (compressed) data to the server 300 (# 1804 in FIG. 18).

As described above, even when the capability of the terminal device 400 is low, it is possible to generate a rule and execute a shortening process without imposing a load on the terminal device 400.
<Third Embodiment>
Since the status of character strings contained in data sent and received between communication devices is aggregated and a rule table for data compression / decompression is generated, the rule table for devices that are sending and receiving data for the first time between devices The situation that is not generated occurs. In this case, data transmission / reception is performed without performing the shortening (compression) process until the rule table is generated.

  In the third embodiment, the default generation unit 135 is provided in the rule generation unit 13 so that data can be shortened (compressed) even when data is transmitted and received for the first time.

  FIG. 19 shows a system configuration diagram according to the third embodiment.

  A default generation unit 135 is provided in the rule generation unit 13 of the server 500. The configuration other than the default generation unit 135 is the same as that of the first or second embodiment.

  The processing of the default generation unit 135 will be described with reference to FIG.

  The default generation unit 135 determines whether it is time to generate a default rule table (# 2001 in FIG. 20). As a timing for determining whether or not it is a timing to generate, every time a predetermined time elapses, a new transmission / reception device is detected each time a new registration or update occurs in the rule table of the rule storage unit 22 I can think of the timing.

  If it is determined that it is time to generate a default rule table (Yes in # 2001 in FIG. 20), the contents of the rule table stored in the rule storage unit 12 are aggregated. For example, it is assumed that the rule table for three terminal devices is stored in the rule storage unit 12 as shown in FIG. Based on the contents of the management table 2100, the contents of the rule tables 2110, 2111, and 2112 stored in association with each terminal ID 2101 are totalized. FIG. 22C shows an example of the totaled result. FIG. 22C shows the character string 82 registered in the rule tables 2110, 2111, and 1122, with reference to the aggregation tables 2120, 2121, and 2122 stored in association with the terminal devices. Is obtained as a result of totaling each character string and arranging them in descending order of appearance frequency for each character string. It is also possible to refer to only the rule table without referring to the tabulation table, and to count the character strings registered in the rule table for each character string as the number of appearances for each character string. When the number of appearances for each character string is totaled with reference to the tabulation table, it is possible to determine in a state close to the sum of the number of appearances of the character strings included in the transmitted / received data. On the other hand, when the number of appearances for each character string is tabulated with reference to only the rule table, it is merged in a form that more largely reflects the tendency of the rule table that reflects the characteristics of each terminal device. There is a high possibility that a rule table more suitable for actual transmission / reception can be generated even if the variation in communication contents becomes somewhat large. For example, if the character string 1 and the character string 2 are included in the rule table of each terminal device, the appearance frequency of the character string 2 is greater than the appearance frequency of the character string 1 in a certain number of terminal devices. By generating a rule table that gives priority to the character string 2 (for example, twice or more), the effect of compression communication as a whole system can be enhanced.

  Based on the totaled result (FIG. 22C), a default rule table (FIG. 22B) is generated (# 2003 in FIG. 20). Here, a rule table is generated by adding abbreviated symbols corresponding to character strings in the order of appearance. As described above, the method for selecting the character string to be the target of the rule table is not limited to the order in which the number of appearances of the character string is large, and other methods may be used.

  The generated rule table is registered in the rule storage unit 12 (# 2004 in FIG. 20). In the example of FIG. 22A, an example is shown in which the generated rule table (FIG. 22C) is registered in the management table 2100 with the terminal ID 2101 set to “unknown”. The terminal ID 2101 is not limited to “unknown”, but may be distinguished from a rule table generated for each terminal device such as “default”.

  As described above, by generating and registering the default rule table, it is determined that it is time to receive the data at the data receiving unit 16 and transmit the data reception notification message at the reception notification transmitting unit 17. In this case, by adding the following processing to the reception notification transmission unit 17, it is possible to set and notify the default rule table in the data reception notification message.

  The reception notification transmission unit 17 checks whether or not the terminal ID of the terminal device that is the transmission source of the received data is registered in the rule table of the rule storage unit 12, and if not, the terminal ID 2101 is “default”. The contents of the rule table "" are acquired and set in the rule column 94 of the data reception notification message 90, and the data reception notification message is transmitted to the terminal device that is the data transmission source. In addition, when the terminal ID of the terminal device that is the transmission source of the received data is registered, the rule table stored in association with the terminal ID is acquired as described in the above embodiments. The data reception notification message is set in the rule column of the data reception notification message, and the data reception notification message is transmitted to the terminal device of the data transmission source.

This eliminates the problem that the data shortening (compression) process cannot be executed until the rule table is generated after the data transmission / reception is repeated several times, and the data to be transmitted / received immediately after the data transmission / reception is started. (Compression) processing can be performed.
<Fourth embodiment>
In each of the above-described embodiments, the example in which the compression rule is set in the data reception notification message when the data reception notification is transmitted has been described. However, in the fourth embodiment, a network that is transmitted and received between communication devices is described. An example in which a compression rule is notified using a connection status confirmation command will be described. A communication device that transmits and receives data regularly transmits a command for inquiring about a network connection state of a communication partner, and confirms the connection state according to a response to the command. As a command for inquiring the network connection status, PING (Packet Internet Groper) data that is currently generally used will be described as an example. When PING data is transmitted to a communication partner at a predetermined time interval (for example, 1 second), a reply to PING data (hereinafter referred to as PONG data) is returned, or transmission is successful, indicating that transmission is possible. Identify.

  Examples of PING data and PONG data are shown in FIG.

  Normally, when checking the network connection state of the communication partner, only the character string “PI” indicating PING data is set in the command identifier 2313 of the body part 2312 of the PING data 2310, and the communication protocol is set in the header part 2311. Set the appropriate header information and send it to the communication device of the communication partner whose network connection status you want to check. The communication device that has received the PING data sets the character string “PO” indicating that it is a PONG command in the command identifier 2323 of the body portion 2322 of the PONG data 2320, and the header portion 2321 contains header information in accordance with the communication protocol. Set and transmit to the communication device of the PING data transmission source. In both the PING data 2310 and the PONG data 2320, the data set in the body parts 2312 and 2322 are only command identifiers 2313 and 2323, and the other areas can be used as free areas. Similar to the data reception notification message described in the above embodiment, the compression rule generated using this free space is used for notification.

  The flow of data reception processing in the fourth embodiment will be described with reference to FIG.

  When receiving the data (# 2401 in FIG. 24), the data receiving unit 16 determines whether or not the received data is PING data (# 2402 in FIG. 24). Whether or not it is PING data is determined by whether or not “PI” indicating that it is PING data is set in the body portion 2312 of the received data. Note that the character string “PI” is an example, and may be another character string as long as it is a character string agreed between communication apparatuses. If the received data is PING data (Yes in # 2402 in FIG. 24), the rule table 80 stored in association with the communication device that is the transmission source of the PING data is acquired from the rule storage units 12 and 22 ( # 2403 in FIG. The character string “PO” indicating that the data is PONG data is set in the command identifier 2323 of the PONG data 2320, the contents of the acquired rule table 80 are set in the rule column 2324, and the PONG data 2320 is generated (# in FIG. 24). 2404). The generated PONG data is transmitted to the communication device of the PING data transmission source (# 2405 in FIG. 24). If the received data is not PING data (No in # 2402 in FIG. 24), as described in each embodiment, it is determined whether it is a data reception notification message or XML data, and the received data is received. Processing according to the content of the data is performed (# 2410 in FIG. 24).

  In this way, not only the data reception notification but also the PING data is notified including the compression rule, so that the compression rule can be communicated without changing or adding the communication procedure in the same manner as when transmitting together with the data reception notification. There is a similar effect that it can be shared between devices.

Further, when transmitting PING data, an empty area of the PING data may be used as the rule column 2314, and the compression rule generated by the PING data transmission source may be set and notified to the PING data transmission destination. In this case, when it is determined that the transmission timing of the PING data is reached, the rule table 80 stored in association with the communication device that is the transmission destination of the PING data is acquired from the rule storage units 12 and 22, and the acquired rule table is acquired. The content of 80 is set in the rule column 2314 of the PING data 2310, and the PING data is transmitted. The data receiving unit 26 that has received the PING data determines whether or not the contents of the rule table are included in the PING data when it is determined that the data is PING data in addition to the processing described above. If it is determined that it is included, the contents of the rule table are stored in the rule storage units 12 and 22 in association with the communication device that is the transmission source of the PING data.
As a result, the communication between the communication devices is connected, and before the actual data communication is started, the compression rule can be transmitted / received by the PING data or the PONG data. In each of the above-described embodiments, an example of application to online shopping has been described. However, the application field of the present invention is not limited to online shopping. For example, in a mobile environment, a sales employee can register a daily business report on a server or use it when communicating with a business system using a mobile communication terminal such as SFA (Sales Force Automation) that acquires product information from the server. In this case, the terminal device side uses a mobile phone or PDA (Personal Digital Assistance) to access the server-side Web application. On the server side, screen information is defined in XFORMS (XML) and transmitted to the terminal device, so that the terminal device side can generate a general-purpose screen independent of the model. By performing the compression communication processing of the present invention at the time of transmission / reception of XML data defined by XFORMS, data transmission / reception between a terminal and a server can be made efficient in a mobile environment.

  Even when application data is shared between a mobile communication terminal and a server using a SyncML (Synchronization Markup Language) format or the like, the present invention can be applied to communication between the mobile communication terminal and the server. SyncML defines an XML format that can be transmitted and received between a mobile communication terminal and a server.

  Or, using a sensor device such as RFID (Radio Frequency Identification), record it on an RFID tag in a business system such as product management or inventory management that reads goods such as goods and cargo at high speed and registers them on a server. When the RFID reader reads data (for example, product information such as product name and product ID) and registers the data in the server in real time, the present invention is applied to communication between the RFID reader and the server. Data transmission / reception between RFID reader and server can be made more efficient.

In particular, when RFID tags attached to a large number of articles are read at high speed with an RFID reader device, it is required to convert the information to necessary information or to filter only the necessary information and send it to the server side. It has been. For example, EPC Global (Electronic Product Code (registered trademark)) has developed a standard (ALE: Application Level Event) that defines filtering rules for data read from an RFID reader.
As described above, in order to process various filtering rules at a higher speed according to the content of the data of the RFID tag, a method capable of sequentially processing the data of the RFID tag while reading from the head is preferable. In this regard, in data communication that simply uses file compression such as GZIP, after restoring the data, it is necessary to read the data again from the beginning and check whether the data corresponding to the filtering rule is included. Don't be.
In the present invention, since the process of sequentially reading data from the head and comparing the character strings is performed, it can be easily combined with a filtering process such as ALE, and the processing amount can be reduced. Also, the first to fourth embodiments can be implemented in combination as appropriate.

  Further, the rule tables 80 of the storage and storage units 12 and 22 have been described in the example of being stored or generated in association with the communication device (server or terminal device). When the compression rule changes depending on the dependency, it may be stored or generated in association with each application.

  In the above-described embodiment, an example in which data is transmitted and received via the communication network 3 has been described. However, data is directly transmitted between communication devices such as BLUETOOTH (registered trademark) and IrDA without using the communication network 3. Even in such a case, the present invention can be similarly implemented.

Regarding the embodiments including the first to fourth embodiments described above, the following additional notes are further disclosed.
(Appendix 1)
A rule generation method for generating a compression rule for compressing data transmitted and received between communication devices having a communication function,
When receiving data transmitted from another communication device via the communication function, extract the character string included in the received data, and totalize the appearance status of the extracted character string for each character string, Aggregate the results for each other communication device of the transmission source and store them in the storage unit,
Select a character string to be subjected to compression processing when compressing data according to the appearance status of the character string stored in the storage unit, and associate the selected character string with the data after compression processing to compress the data And store the generated compression rule in the storage unit in association with the other communication device that is the transmission source of the data,
A rule generation method characterized in that, when a reception notification for data transmitted from another communication device is transmitted, a compression rule stored in association with the other communication device is transmitted together with the reception notification.
(Appendix 2)
Based on the compression rule generated for each communication device, a new compression rule is generated and stored in the storage unit in association with an identifier representing an unknown communication device,
When transmitting a reception notification for data transmitted from another communication device, if the compression rule stored in association with the other communication device is not stored in the storage unit, it represents an unknown communication device The rule generation method according to appendix 1, wherein the compression rule stored in association with the identifier is transmitted together with the reception notification.
(Appendix 3)
A rule generation method for generating a compression rule for compressing data transmitted and received between communication devices having a communication function,
For each of the first data transmitted from the other communication device and the second data transmitted to the other communication device, the character string included in the data is extracted, and the appearance status of the extracted character string is defined as the first data. 1 data and 2nd data are aggregated and stored in the storage unit in association with each other communication terminal,
Based on the appearance status of the character string for each of the first data and the second data stored in the storage unit, a compression rule for the first data and a compression rule for the second data are generated respectively. Store it in the storage unit in association with the other terminal device,
When a reception notification for data transmitted from another communication device is transmitted, the compression rules of the first data and the second data stored in association with the other communication device are transmitted together with the reception notification. A rule generation method characterized by the above.
(Appendix 4)
Based on the first compression rule and the second compression rule generated for each communication device, a new first compression rule and a second compression rule are generated to correspond to an identifier representing an unknown communication device. And store it in the memory
When transmitting a reception notification for data transmitted from another communication device, the first compression rule or the second compression rule stored in association with the other communication device is not stored in the storage unit. In this case, the rule generation method according to appendix 3, wherein the first compression rule or the second compression rule stored in association with the identifier representing the unknown communication device is transmitted together with the reception notification.
(Appendix 5)
A compression communication device used for a communication device having a communication function capable of communicating with other communication devices, for compressing / decompressing data transmitted / received between the communication devices,
Data receiving means for receiving data transmitted from other communication devices;
Extracts character strings included in the received data, analyzes the appearance status of the extracted character strings, aggregates the extracted character strings, and stores the aggregated results in association with other communication devices Means,
Based on the aggregated results, a character string to be subjected to compression processing is selected, a compression rule that associates the selected character string with a compression symbol associated with the character string is generated, and stored for each communication device. Compression rule generation means to be kept,
When data is received by the data receiving means, it is determined whether or not data reception notification is to be performed, and when it is determined that data reception notification is to be performed, it is stored in association with the communication device that is the transmission source of the received data A compression communication apparatus comprising: a reception notification means for acquiring a compressed compression rule from the compression rule generation means and notifying the transmission source communication apparatus of a data reception notification together with the acquired compression rule.
(Appendix 6)
A second compression rule generating means for generating a new compression rule based on the compression rule stored in the compression rule generating means and storing it in association with an identifier indicating an unknown communication device; Prepared,
The reception notifying means stores a compression rule stored in association with an identifier indicating that the communication device is an unknown communication device when there is no compression rule stored in association with the communication device that is the transmission source of received data. The compressed communication device according to appendix 5, wherein the compressed communication device is acquired and notified together with a data reception notification.
(Appendix 7)
A compression communication device used for a communication device having a communication function capable of communicating with other communication devices, for compressing / decompressing data transmitted / received between the communication devices,
Receiving means for receiving first data transmitted from another communication device;
Transmission data receiving means for receiving second data to be transmitted to another communication device;
A character string included in the first data received by the receiving unit or the second data received by the transmission data receiving unit is extracted, and the appearance status of the extracted character string is determined for each of the first data and the second data. Totaling means for counting and storing in association with each other communication terminal;
Based on the appearance status of the character string for each of the first data or the second data stored in the storage unit, the first compression rule for the first data and the second compression rule for the second data are respectively determined. And a compression rule generating means for generating and storing in association with the other terminal device,
When data is received by the data receiving means, it is determined whether or not data reception notification is to be performed, and when it is determined that data reception notification is to be performed, it is stored in association with the communication device that is the transmission source of the received data Receiving the first compression rule or the second compression rule that has been received from the compression rule generation means, and the reception notification means for notifying the transmission source communication device of the data reception notification together with the acquired compression rule. A compression communication device.
(Appendix 8)
Based on the first compression rule and the second compression rule stored in the compression rule generation means, a new first compression rule and a second compression rule are generated to indicate an unknown communication device. A second compression rule generating means for storing the information in association with the identifier;
The reception notification means corresponds to an identifier indicating the unknown communication device when there is no first compression rule or second compression rule stored in association with the communication device that is the transmission source of the received data. The compressed communication apparatus according to appendix 7, wherein the first compression rule or the second compression rule stored together is acquired and notified together with a data reception notification.
(Appendix 9)
A compression communication device used for a communication device having a communication function capable of communicating with other communication devices, for compressing / decompressing data transmitted / received between the communication devices,
Receiving means for receiving data transmitted from another communication device;
It is determined whether or not the received data is a data reception notification from another communication transmission for data transmitted to another communication device, and if it is determined that the received data is a data reception notification, the compression included in the data reception notification A compression rule acquisition means for acquiring a rule and storing the rule in association with another communication device;
When transmitting data to another communication device, when transmitting data to the other communication device, compression processing of the transmission data is performed based on a compression rule stored in association with the other communication device. Compression means to perform;
A compression communication apparatus, comprising: a transmission unit that transmits the compressed data.
(Appendix 10)
A compression communication device used for a communication device having a communication function capable of communicating with other communication devices, for compressing / decompressing data transmitted / received between the communication devices,
Receiving means for receiving data transmitted from another communication device;
It is determined whether the data received by the receiving means is a data reception notification from another communication transmission for the data transmitted to another communication device, and if it is determined that the data reception notification is received, the data reception notification A compression rule acquisition means for acquiring the first compression rule and the second compression rule included in and storing them in association with other communication devices;
When transmitting data to another communication device, when transmitting data to the other communication device, the transmission data is transmitted based on the first compression rule stored in association with the other communication device. Compression means for performing compression processing;
Transmitting means for transmitting the compressed data; and restoring means for restoring the content of the data based on a second compression rule stored in association with the communication device that is the transmission source of the data received by the receiving means;
A compression communication device comprising:
(Appendix 11)
A program for executing a rule generation method for generating a compression rule for compressing data transmitted and received between communication devices having a communication function,
When data transmitted from another communication device via the communication function is received, the character string included in the received data is extracted, and the appearance status of the extracted character string is totaled for each character string, and totalized Summing up the results obtained for each other communication device of the transmission source and storing them in the storage unit;
Select a character string to be subjected to compression processing when compressing data according to the appearance status of the character string stored in the storage unit, and associate the selected character string with the data after compression processing to compress the data And storing the generated compression rule in a storage unit in association with another communication device that is a transmission source of the data;
And a step of transmitting a compression rule stored in association with the other communication device together with the reception notification when transmitting a reception notification for the data transmitted from the other communication device.
(Supplementary note 12) A program for executing a rule generation method for generating a compression rule for performing compression processing of data transmitted and received between communication devices having a communication function,
For each of the first data transmitted from the other communication device and the second data transmitted to the other communication device, the character string included in the data is extracted, and the appearance status of the extracted character string is defined as the first data. Summing up the data for each of the first data and the second data, and storing the data in the storage unit in association with the other communication terminals;
Based on the appearance status of the character string for each of the first data and the second data stored in the storage unit, a compression rule for the first data and a compression rule for the second data are generated respectively. Storing in the storage unit in association with the other terminal device;
When a reception notification for data transmitted from another communication device is transmitted, the compression rules of the first data and the second data stored in association with the other communication device are transmitted together with the reception notification. And a program.

  According to the present invention, in a communication system that performs business or enjoys a service while performing transmission / reception of data via a communication network, it is possible to dynamically set a compression method of transmitted / received data. By avoiding the compression of processing performance on the terminal device, it is possible to perform business or enjoy services while optimally compressing the increasing amount of transmitted / received data.

Diagram showing the principle of the present invention Flowchart explaining the basic processing flow of the present invention The figure which shows the structure of 1st Embodiment. The flowchart explaining the flow of the rule generation processing in the first embodiment The flowchart explaining the flow of the process which shortens (compresses) data based on the rule produced | generated in 1st Embodiment. The figure which shows the example of the content of the data transmitted / received (A) The figure which shows the example of the content of the data before compression processing (B) The figure which shows the example of the content of the data after compression processing The figure which shows the example of the content of the total table memorize | stored in a total data storage part The figure which shows the example of the content of the rule table memorize | stored in a rule memory | storage part The figure which shows the example of the contents of the data reception notification message The figure which shows the structure of 2nd Embodiment. The flowchart explaining the flow of the rule production | generation based on the transmission data in 2nd Embodiment The flowchart explaining the flow of the process for notifying the produced | generated rule in 2nd Embodiment. The figure which shows the example of the content of the total table memorize | stored in the total memory | storage part in 2nd Embodiment. The figure which shows the example of the content of the rule table memorize | stored in the rule memory | storage part in 2nd Embodiment. The figure which shows the example of the content of the data reception notification message in 2nd Embodiment The flowchart explaining the flow of the reception process by the terminal device side in 2nd Embodiment. The figure which shows the example of the content of the rule table memorize | stored in the rule memory | storage part by the side of the terminal device in 2nd Embodiment. The flowchart explaining the flow of the transmission process by the terminal device side in 2nd Embodiment. The figure which shows the structure of 3rd Embodiment. The flowchart explaining the flow of a process of the default production | generation part in 3rd Embodiment. The figure which shows the example of the content of the rule memory | storage part and total data memory | storage part in 3rd Embodiment The figure which shows the example of the content of the rule memory | storage part and total data memory | storage part in 3rd Embodiment The figure which shows the example of the content of the PING data and PONG data in 4th Embodiment The flowchart explaining the flow of a process of the data receiver in 4th Embodiment

Explanation of symbols

1 device, receiving device, (communication device, compression communication device)
2 device, transmitting device, (communication device, compression communication device)
3 communication network 10, 20 control unit 11, 21 application, business application 12, 22 rule storage unit (compression rule generation means)
13, 23 Rule generation unit (compression rule generation means)
131, 231 Received data totaling unit, (totaling means)
132, 232 Total data storage unit (Totaling means)
133, 233 Rule determining unit, (compression rule generating means)
134 Transmission data totaling unit, (totaling means)
135 Default generation unit (second compression rule generation means)
14, 24 Rule notification section (Reception notification means)
15, 25 Compression / decompression unit 151, 251 Transmission data compression unit 152, 252 Reception data restoration unit 16, 26 Data reception unit 17, 27 Reception notification transmission unit (Reception notification means) 19, 29 Data transmission unit 1C, 2C Communication Interface (communication I / F)

Claims (5)

A rule generation method for generating a compression rule for compressing data transmitted and received between communication devices having a communication function,
When receiving data transmitted from another communication device via the communication function, extract the character string included in the received data, and totalize the appearance status of the extracted character string for each character string, Aggregate the results for each other communication device of the transmission source and store them in the storage unit,
Select a character string to be subjected to compression processing when compressing data according to the appearance status of the character string stored in the storage unit, and associate the selected character string with the data after compression processing to compress the data And store the generated compression rule in the storage unit in association with the other communication device that is the transmission source of the data,
A rule generation method characterized in that, when a reception notification for data transmitted from another communication device is transmitted, a compression rule stored in association with the other communication device is transmitted together with the reception notification. A compression communication device that is used in a communication device having a communication function capable of communicating with other communication devices and compresses / decompresses data transmitted / received between the communication devices,
Data receiving means for receiving data transmitted from other communication devices;
Extracts character strings included in the received data, analyzes the appearance status of the extracted character strings, aggregates the extracted character strings, and stores the aggregated results in association with other communication devices Means,
Based on the aggregated results, a character string to be subjected to compression processing is selected, a compression rule that associates the selected character string with a compression symbol associated with the character string is generated, and stored for each communication device. Compression rule generation means to be kept,
When data is received by the data receiving means, it is determined whether or not data reception notification is to be performed, and when it is determined that data reception notification is to be performed, the data is stored in association with the communication device that is the transmission source of the received data A compression communication apparatus comprising: a reception notification means for acquiring a compressed compression rule from the compression rule generation means and notifying the transmission source communication apparatus of a data reception notification together with the acquired compression rule. A second compression rule generating means for generating a new compression rule based on the compression rule stored in the compression rule generating means and storing it in association with an identifier indicating an unknown communication device; Prepared,
The reception notifying means stores a compression rule stored in association with an identifier indicating that the communication device is an unknown communication device when there is no compression rule stored in association with the communication device that is the transmission source of received data. The compressed communication device according to appendix 5, wherein the compressed communication device is acquired and notified together with a data reception notification. A compression communication device used for a communication device having a communication function capable of communicating with other communication devices, for compressing / decompressing data transmitted / received between the communication devices,
Receiving means for receiving first data transmitted from another communication device;
Transmission data receiving means for receiving second data to be transmitted to another communication device;
A character string included in the first data received by the receiving unit or the second data received by the transmission data receiving unit is extracted, and the appearance status of the extracted character string is determined for each of the first data and the second data. Totaling means for counting and storing in association with each other communication terminal;
Based on the appearance status of the character string for each of the first data or the second data stored in the storage unit, the first compression rule for the first data and the second compression rule for the second data are respectively determined. And a compression rule generating means for generating and storing in association with the other terminal device,
When data is received by the data receiving means, it is determined whether or not data reception notification is to be performed, and when it is determined that data reception notification is to be performed, it is stored in association with the communication device that is the transmission source of the received data Receiving the first compression rule or the second compression rule that has been received from the compression rule generation means, and the reception notification means for notifying the transmission source communication device of the data reception notification together with the acquired compression rule. A compression communication device. A program for executing a rule generation method for generating a compression rule for compressing data transmitted and received between communication devices having a communication function,
When receiving data transmitted from another communication device via the communication function, extract the character string included in the received data, and totalize the appearance status of the extracted character string for each character string, Summing up the totaled results for each other communication device of the transmission source and storing them in the storage unit;
Select a character string to be subjected to compression processing when compressing data according to the appearance status of the character string stored in the storage unit, and associate the selected character string with the data after compression processing to compress the data And storing the generated compression rule in association with another communication device that is the transmission source of the data,
And a step of transmitting a compression rule stored in association with the other communication device together with the reception notification when transmitting a reception notification for the data transmitted from the other communication device.