JP2006013951A - Mobile device and data acquiring method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To suppress traffic quantity when a server device performs push distribution of updating data different in each classification of a mobile device. <P>SOLUTION: This mobile device 10 is provided with a transmission necessity determining part 14 and a classification information transmitting part 15 for acquiring updating data transmitted from a distribution server 20 and different in each classification of a mobile device. The transmission necessity determining part 14 determines the necessity to notify classification information on the basis of a flag showing whether the latest classification information of the mobile device 10 is notified to the distribution server 20 when the mobile device 10 is started or when communication is prepared. The classification information transmitting part 15 transmits the classification information to the distribution server 20 when the notification of classification information is determined to be necessary. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a technique in which a mobile device acquires update data distributed from a server device.

  In recent years, mobile devices such as mobile phones are also concerned about attacks by computer viruses, like personal computers. As one means for addressing such concerns, it is effective to upgrade the software itself using defect correction data (patch data). Alternatively, processing such as addition of anti-virus software for preventing attacks and pattern data of IDS (Intrusion Detection System) is also effective. In the following description, normal software version upgrade data is added to the above-described defect correction data and pattern data, and is referred to as “update data”.

  Mobile devices consist of a wide variety of software and hardware depending on the manufacturer and model, and different update data is provided for each type of mobile device in order to respond appropriately to the vulnerabilities. It is necessary to In general, however, mobile carriers manage user information (contractor name, IMSI (International Mobile Subscriber Identifier), telephone number, e-mail address, address, contract form, etc.). The type of mobile device owned by the user is not sufficiently managed. For this reason, a server device that distributes update data requires a mechanism for accurately grasping the type of mobile device (for example, the version of hardware or software).

  Under the above-described circumstances, for example, Patent Document 1 discloses a method for acquiring update data described below. In this method, as new update data is released, the server device pushes a notification to that effect to all the registered mobile devices. At the same time, the server device notifies the type of mobile device to which the update data is to be applied. Upon receiving these notifications, the mobile device determines whether update data is necessary, and requests the server device to transmit update data if necessary. If not needed, the mobile will ignore these notifications.

As another method, when the update data is released, the server device makes an inquiry about the type to all the registered mobile devices, and based on the response from each mobile device, the user information and the mobile device type information It is also conceivable to create a DB (DataBase) in which In this method, when new update data is released, the server device refers to the DB and pushes update data suitable for each registered mobile device.
JP 2003-418482 A

  However, there are still concerns about the following problems in the above-described prior art. That is, in the technique disclosed in Patent Document 1, every time update data is released, all the mobile devices are notified of this, so notification is made even to mobile devices that do not need to update data. Will be done. As a result, useless communication occurs and the amount of traffic increases.

  In the other method, the server device makes a type inquiry to each mobile device only once (when the first update data is released). For this reason, a mechanism for updating the DB on the server device side is still necessary when there is a change for each mobile model of the user due to replacement of the mobile device or software upgrade. Furthermore, depending on the state of the mobile device at the time of the inquiry, another inquiry is necessary due to the outside of the communication range or power off, and there is a concern that the traffic volume will increase.

In view of the allowable amount of radio resources or the processing capability of the mobile device and the battery driving time, the suppression of the traffic amount in the mobile communication is a particularly important issue for efficient data updating.
Therefore, an object of the present invention is to suppress the traffic amount when the server device push-distributes update data different for each type of mobile device.

  In order to solve the above problems, a mobile device according to the present invention is a mobile device that is transmitted from a server device and is capable of acquiring different update data for each type of mobile device, when the mobile device is activated or ready for communication. Sometimes it is necessary to determine whether or not to notify the type information based on information indicating whether or not the latest type information of the mobile device is notified to the server device, and to notify the type information And a transmission unit that transmits the type information to the server device.

  Here, the update data different for each type of mobile device is data generated depending on the type of mobile device. The type of mobile device includes a type based on software such as an OS (Operating System) and an application program version in addition to a hardware type such as a manufacturer name, model name, and ROM (Read Only Memory) version. Regardless of the purpose, the update data is data for modifying (including adding or deleting) existing data in the mobile device. As described above, the update data is defect correction data, virus pattern data, normal software upgrade data, and the like.

  According to the present invention, the mobile device determines whether or not the latest type information has been notified to the server device in response to a change in the state of the own device, and if notification is necessary, that is, the type of the server device. Notify this only if the information is not up to date. In this way, the mobile device voluntarily notifies the change of the type information of its own device without waiting for a notification or inquiry from the server device. Therefore, on the server device side, the latest type information is always based on this notification. Can be retained. In addition, when the notification to the server device is unnecessary, the type information is not transmitted, and further, the concern that the re-query from the server device is performed due to the state of the mobile device is solved. That is, push distribution of update data to the mobile device is realized with a minimum amount of traffic.

  In the mobile device according to the present invention, the information indicating whether or not the server device is notified is a flag, and the holding means for holding the type information of the mobile device and the type information of the mobile device include the holding information. The information processing apparatus may further include setting means for setting the flag to ON or OFF based on whether the type information is the same as the previous type information held in the means.

  According to the present invention, a mobile device can easily realize a reduction in traffic volume, which is a problem of the present invention, by referring to a flag as information for determining whether notification of type information is necessary. That is, the mobile device holds the type information of the own device in the holding means, and at the time of start-up or communication preparation, the current type information is the same as the previous type information (before acquisition of update data). Determine gender. As a result of the determination, if they are the same, the flag is set to ON, and if different, it is set to OFF and the type information is transmitted. As a result, the mobile device avoids the situation in which the type information is transmitted even though the latest type information is registered in the server device, with simple means. As a result, limited radio resources and batteries can be used efficiently.

  In the mobile device according to the present invention, more preferably, the mobile device further comprises holding means for holding identification information of the UIM inserted into the mobile device, and the determination means is configured to insert the UIM into the mobile device when the UIM is inserted. Whether or not notification of the type information (including UIM identification information) is required is determined based on whether the identification information is the same as the previous identification information held in the holding unit.

The UIM (User Identity Module) includes aliases such as USIM (Universal Subscriber Identity Module), R-UIM (Removable UIM), and SIM (Subscriber Identity Module).
The present invention has been made on the assumption that a plurality of different UIMs are also used as one mobile device. Depending on the contents of the update, it is necessary to appropriately change the update data to be provided in accordance with the type of UIM. Therefore, when the UIM is inserted into the mobile device, the mobile device determines the identity between the UIM inserted this time (current UIM) and the replaced UIM (previous UIM). As a result of the determination, the type information is transmitted only when they are different. In this way, the mobile device omits the type information transmission process when the latest type information is already notified to the server device. As a result, waste of wireless resources and batteries associated with useless data communication is reduced as much as possible.

  In the data acquisition method according to the present invention, the mobile device notifies the type information based on information indicating whether or not the latest type information of the mobile device is notified to the server device at the time of start-up or communication preparation. A determination step for determining whether or not it is necessary, and a transmission step for transmitting the type information to the server device when it is determined that the notification of the type information is necessary in the determination step; Receiving the update data acquired by the server device with reference to the type information.

  According to the present invention, the mobile device determines whether or not the latest type information has been notified to the server device in response to a change in the state of the own device, and if notification is necessary, that is, the type of the server device. Notify this only if the information is not up to date. Therefore, the server device can always manage the database in the latest state while holding the latest type information spontaneously notified from the mobile device. Based on this type information, the server device distributes update data corresponding to the type information. The mobile device receives and stores the distributed update data. As a result, push distribution of update data is realized with a minimum necessary communication amount.

  According to these inventions, it is possible to suppress the amount of traffic when the server device push-distributes update data different for each type of mobile device.

[First Embodiment]
Hereinafter, a data acquisition system according to an embodiment of the present invention will be described with reference to the accompanying drawings.
First, with reference to FIG. 1, functional configurations of the mobile device 10 and the distribution server 20 (corresponding to the server device) in the present embodiment will be described. As shown in FIG. 1, the mobile device 10 includes a UIM 11, a type information holding unit 12 (corresponding to the holding unit), a flag setting unit 13 (corresponding to the setting unit), and a transmission necessity determining unit 14 (corresponding to the determining unit). Correspondence), a type information transmission unit 15 (corresponding to a transmission means), a data reception unit 16, and a data storage unit 17. These components are connected to each other via a bus so that signals can be input and output.

  The UIM 11 is an IC card that is detachably mounted in a card slot of the mobile device 10. The UIM 11 stores information unique to the user such as the user ID and telephone number of the user who is a contractor and a call charge. By replacing this UIM 11 with a UIM owned by a user other than the above-mentioned user, a plurality of people can share one mobile device 10.

  The type information holding unit 12 includes a nonvolatile semiconductor memory such as an EEPROM (Electrically Erasable Programmable Read-Only Memory). The type information holding unit 12 holds hardware and software information (corresponding to type information) indicating the type of the mobile device 10. This type information is referred to when setting the flag, and is transmitted to the distribution server 20 in accordance with an instruction from the type information transmitting unit 15 described later. Furthermore, the type information holding unit 12 includes a UIM information holding unit 12f that holds the UIM ID of the UIM 11. An example of data held in the type information holding unit 12 is shown in FIG. As shown in FIG. 2, the type information holding unit 12 includes data storage areas 12 a to 12 e that hold type information such as a manufacturer name, a model name, a ROM version, a hardware version, and an OS type. In addition, independent of these data areas, the UIM information holding unit 12f, which is a data storage area for holding a UIM ID as data that can uniquely identify a mounted UIM, is provided. The UIMID is “U01”, for example, and corresponds to the UIM identification information.

  The flag setting unit 13 refers to the type information (including UIMID) held in the type information holding unit 12 and sets the flag on or off. This flag is a flag indicating whether or not the latest type information of the mobile device 10 has already been notified to the distribution server 20, and is set to “0” when not notified. In the case of notification, “1” is set. The reference for changing the flag and the timing thereof will be described in detail in the explanation of the operation. However, when the current type information and the previous type information are the same, the flag setting unit 13 indicates that the flag indicates ON. The control is performed so that it is set to “1” and, if different, “0” representing OFF.

  The transmission necessity determination unit 14 determines the necessity of transmission of the type information based on the flag set by the flag setting unit 13 when the mobile device 10 is started up or communication is prepared. If “0” is set in the flag as a result of the determination, the type information transmitting unit 15 is instructed to transmit type information. If “1” is set, the type information is not transmitted. Continue normal processing. Further, the transmission necessity determination unit 14, when the UIM is inserted into the mobile device 10, the ID of the inserted UIM and the UIMID held in advance in the type information holding unit 12 (corresponding to the previous identification information). Whether or not the type information needs to be transmitted is determined based on the identity. If they are different, transmission of type information, that is, transmission of UIMID is instructed. If they are the same, the process proceeds to normal processing without transmitting them.

  The type information transmission unit 15 acquires the latest type information from the type information holding unit 12 and transmits it to the distribution server 20 in accordance with an instruction from the transmission necessity determination unit 14. The type information is transmitted via the radio base station B and the public communication network N. In addition, when some type information is changed, type information may be transmitted only about the changed part, and all type information may be transmitted.

The data receiving unit 16 receives update data reflecting the latest type information from the distribution server 20.
The data storage unit 17 stores update data received by the data reception unit 16. This update data is used for virus pattern data addition, software version upgrade, defect correction, etc., according to the purpose and contents.

  Next, the configuration of the distribution server 20 will be described. Returning to FIG. 1, the distribution server 20 includes a type information receiving unit 21, a type information DB 22, a distribution data instruction unit 23, an update data storage unit 24, and a data distribution unit 25. These components are connected to each other via a bus so that signals can be input and output.

  The type information receiving unit 21 receives type information transmitted from the mobile device 10 via the radio base station B and the public communication network N. The received type information is output to the type information DB 22.

  The type information DB 22 stores this information in a predetermined data area every time the type information is input from the type information receiving unit 21. This keeps the database up to date at all times. The type information DB 22 can be physically configured by a nonvolatile magnetic disk such as an HDD (Hard Disc Drive), but is a storage device in which the confidentiality and safety of data are sufficiently ensured. Is desirable. FIG. 3 is a diagram illustrating an example of data storage in the type information DB 22. As shown in FIG. 3, the type information (for example, “A”, “900i”, “1.2”,...) Is stored in the type information DB 22 with the address (eg, “0001”, “0002”, “0003”, and so on). The address is, for example, an Internet e-mail address or SMS (Short Message Service) address.

  The distribution data instruction unit 23 specifies type information suitable for the update data when the update data is newly registered. Furthermore, by referring to the type information DB 22, a mobile device having an address corresponding to the type information is determined as an update data distribution target. Thereafter, the distribution data instruction unit 23 acquires the determined distribution target address from the type information DB 22 and instructs the data distribution unit 25 to distribute the update data to the address.

In the update data storage unit 24, update data is stored in association with type information suitable for the update data. This update data is added as new update data is released, and is updated as corrections are made.
In response to an instruction from the distribution data instruction unit 23, the data distribution unit 25 distributes the update data to a designated address.

Next, the operation of the data acquisition system 1 realized by cooperation between the mobile device 10 and the distribution server 20 will be described with reference to FIGS. In addition, each step constituting the data acquisition method according to the present invention will be described.
First, triggered by an operation on the mobile device 10 side such as activation upon power-on and communication preparation completion by activation of a communication control program (S1 in FIG. 4), the state of the mobile device 10 changes to a communicable state (S2). . Generally, after this, a so-called standby screen is displayed on the display device of the mobile device 10.

In S3, the flag setting unit 13 determines whether the UIM has been changed from the previous one based on the identity between the previous UIID held in the type information holding unit 12 and the current UIMD. Done.
In S3, it is assumed that the UIM 11 has been inserted into the mobile device 10 in advance, but it is also assumed that it has not been inserted. In this case, the mobile device 10 may not always transmit the mobile device type information to the distribution server 20, or may always transmit the mobile device type information to the distribution server 20.

  If the UIM has not been changed as a result of the determination in S3 (S3; YES), the process proceeds to S4, and further, it is determined whether or not the mobile device type has been changed. That is, the flag setting unit 13 determines whether the UIM has been changed from the previous one based on the identity of the previous type information held in the type information holding unit 12 and the current type information. (S4).

  As a result of the determination, if there is no change in the type information (S4; YES), that is, if it is confirmed that there is no change in both the UIM and the type information, the process proceeds to S5. In S <b> 5, the transmission necessity determination unit 14 refers to the flag and determines whether transmission of the type information is necessary. If the flag is set to “0” (S5; YES), since it can be determined that the latest mobile device type of the mobile device 10 has not been notified yet, the transmission necessity determination unit 14 determines the type information. The transmission unit 15 is instructed to transmit type information.

Upon receiving the transmission instruction from the transmission necessity determination unit 14, the type information transmission unit 15 transmits the mobile device type information to the distribution server 20 (S6). After the transmission, the type information transmission unit 15 notifies the flag setting unit 13 that the transmission is completed. Upon receiving this notification, the flag setting unit 13 changes the flag set to “0” to “1” so that the latest type information is reflected in the database of the distribution server 20. (S7).
When the flag is not set to “0” (when set to “1”) (S5; NO), the above-described processes of S6 and S7 are omitted, and the process proceeds to a normal process. .

  On the other hand, if the result of determination in S3 is that the UIM has been changed (S3; NO), it can be estimated that the user of the mobile device 10 has changed to another user, so that it is necessary to transmit type information, The flag is set to “0” (S8). Similarly, if the type information of the mobile device 10 is different from the previous one as a result of the determination in S4 (S4; NO), it can be estimated that there has been some change in the hardware or software, so the type information needs to be transmitted. Therefore, the flag is set to “0” (S8). After the process of S8 is completed, the process proceeds to S6 and subsequent processes.

  With the above processing, the mobile device 10 can perform incomplete confirmation of the notification of type information triggered by activation or completion of communication preparation. In addition, when the latest mobile device type information is not notified, such information is notified to the distribution server 20 via the network, so that the latest type information of the mobile device 10 can always be referred to in the distribution server 20 as well. . That is, the administrator of the distribution server 20 can surely have the type information corrected by the user of the mobile device.

  The series of processes may be executed in response to the UIM insertion. In this mode, as shown in the flowchart of FIG. 5, the transmission necessity determination unit 14 determines the notification of the type information based on whether or not the UIIMID has been changed without performing the flag reference processing by the flag setting unit 13. You can also That is, when detecting the insertion of a UIM (S11), the transmission necessity determination unit 14 acquires the ID of the inserted UIM and compares the ID with the previous UIIM existing in the type information holding unit 12. .

  As a result of the comparison, if these UIMIDs match (S12; YES), it can be determined that the UIM has not been replaced. Therefore, the transmission necessity determination unit 14 shifts to normal processing without instructing notification of type information. This avoids a situation in which the same type information is transmitted again even though the latest type information is already grasped on the distribution server 20 side.

  On the other hand, when the ID of the inserted UIM is different from the previous UIM (S12; NO), it can be determined that the UIM has been replaced. Therefore, the transmission necessity determination unit 14 instructs the type information transmission unit 15 to transmit the type information of the mobile device 10 in order to notify the UIM ID (part of the type information) of the new user. Upon receiving the transmission instruction, the type information transmitting unit 15 transmits type information including at least the newly inserted UIM ID (latest UIMID) to the distribution server 20 (S13). After transmission, the mobile device 10 shifts to normal processing. Thereby, the delivery server 20 can detect the user's change of the mobile device 10 simply and quickly.

Finally, processing for distributing update data from the distribution server 20 to a plurality of mobile devices will be described with reference to the flowchart of FIG.
The mobile device type information transmitted in S6 of FIG. 4 or S13 of FIG. 5 is received by the type information receiving unit 21 of the distribution server 20, and is stored in the type information DB 22 together with the transmission source address (T1). This process is performed not only for the mobile device 10 but for all mobile devices that are the distribution target of update data, and as a result, the type information DB 22 is always kept in a state in which the latest type information is reflected.

  The distribution data instructing unit 23 monitors the presence or absence of newly registered update data (T2). When the distribution data instruction unit 23 detects new registration of update data (T2; YES), the process after T3 is executed. At T3, the distribution data instruction unit 23 specifies a mobile device that is the distribution target of the update data. That is, the distribution data instructing unit 23 specifies the type information corresponding to the registered update data by referring to the update data storage unit 24, and further selects the mobile device for which the type information is currently notified for update. Identifies the data distribution target.

Thereafter, the distribution data instruction unit 23 acquires the addresses of all the mobile devices specified in T3 from the type information DB 22 (T4). At this time, it is possible to further narrow down the mobile device addresses by checking the contract form of each mobile device.
Then, the distribution data instruction unit 23 push-distributes the update data whose new registration has been detected at T2 to the address acquired at T4.

  That is, the distribution server 20 can distribute update data that conforms to this type information almost simultaneously with the registration based on the database reflecting the latest type information. For this reason, a situation in which the update data is distributed but is not used on the mobile device side because it does not match the type information is avoided. As a result, efficient data distribution in which only the minimum necessary update data is quickly provided to the user becomes possible.

  As described above, according to the data acquisition system 1 in the present embodiment, the mobile device 10 and the distribution server 20 operate in cooperation, whereby the communication traffic amount by the mobile device 10 and the communication by the distribution server 20 Reduce both traffic volume. That is, the mobile device 10 determines whether or not it is necessary to notify the type information by referring to a flag indicating “0” if the type information is not notified and “1” if the type information is already notified. The type information is notified only when it is determined to be necessary. On the other hand, in the distribution server 20, when the necessity for distribution of update data occurs, the distribution server 20 performs distribution only to mobile devices that require the update data. Therefore, the amount of data communication accompanying the provision of update data dependent on the mobile device, and hence the processing load and communication load are reduced. As a result, server facilities or network facilities can be reduced.

[Second Embodiment]
Next, a second embodiment of the present invention will be described with reference to FIG. In the mobile device 10 according to the first embodiment, a flag that can be variably set to on / off is used as information for determining whether notification of type information is necessary. It can be substituted. That is, in the first embodiment, it is assumed that the first type information after shipment is mainly transmitted and the mobile device 10 refers to the flag. However, in the present embodiment, the flag is not necessarily required. Take.

  The configuration of the mobile device in the second embodiment is the same as the configuration of the mobile device 10 described in detail in the first embodiment, except that the flag setting unit is not provided. Accordingly, the same reference numerals are given to the respective constituent elements, illustration and description thereof are omitted, and the operational differences from the first embodiment will be described in detail below.

  FIG. 7 is a flowchart for explaining type information notification processing of a mobile device in the second embodiment. The operation will be described with reference to FIG. In addition, each step constituting the data acquisition method according to the present invention will be described. Note that the operation of the mobile device 10 shown in FIG. 7 includes a plurality of steps in common with the operation of the mobile device described in detail in the first embodiment. Specifically, S21 to S24 in FIG. 7 correspond to S1 to S4 shown in FIG.

Hereinafter, S25 and S26, which are differences between the various types of information notification processing, will be described. As a premise of the operation description, when the mobile device 10 is shipped, type information (including UIMID) that does not match the notified type information (for example, NULL or 00... 00) is the type information holding unit. 12f.
When there is a change in either the UIM or the mobile device type, the process proceeds to S25, and the mobile device 10 transmits the mobile device type information to the distribution server 20. After the transmission, the mobile device 10 updates the type information in the type information holding unit 12 to a new value (S26). Thereafter, the mobile device 10 determines whether or not the latest type information is notified to the distribution server 20 based on the identity of the type information.

  As described above, according to the mobile device 10 in the second embodiment, the type information held in the type information holding unit 12 is used, in other words, the type information is notified without using the flag. Can be done to the limit. As a result, it is possible to suppress the traffic volume, which is a problem of the present invention, with a simpler configuration and operation.

In addition, the aspect described in each said embodiment is a suitable example of the mobile apparatus and distribution server which concern on this invention, and this invention is not limited to this aspect.
For example, in the present embodiment, a mobile phone is assumed as a mobile device. However, the present invention is not limited to this, and any terminal having a communication function such as a PDA (Personal Digital Assistance) or a personal computer may be used. Furthermore, the present invention can be applied particularly effectively to an apparatus such as an Internet home appliance that is not frequently operated by a user.

  The update data is stored in the storage means of the distribution server itself. However, the update data is stored in an external device configured separately from the distribution server (for example, a DB-dedicated device operated by a server manager). It may be stored in the means. In the former case, the distribution server does not need to request the external device to transmit it every time distribution of update data is desired, which is preferable from the viewpoint of reducing communication load and improving response speed. On the other hand, in the latter case, it is not necessary for the distribution server to hold all the update data that may be requested in advance, so that the data capacity of the storage means can be reduced. There are benefits.

It is a figure which shows the functional structure of the data acquisition system which concerns on this invention. It is a figure which shows an example of the classification information hold | maintained at a classification information holding part. It is a figure which shows the example of data storage in the data storage part for an update. In 1st Embodiment, it is a flowchart for demonstrating the process of the mobile apparatus started execution at the time of starting or communication preparation completion. It is a flowchart for demonstrating the process of the mobile apparatus which execution is started at the time of insertion of UIM. It is a flowchart for demonstrating the update data delivery process which a delivery server performs. In 2nd Embodiment, it is a flowchart for demonstrating the process of the mobile apparatus by which execution is started at the time of starting or communication preparation completion.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 1 ... Data acquisition system, 10 ... Mobile station, 11 ... UIM, 12 ... Type information holding part, 13 ... Flag setting part, 14 ... Transmission necessity judgment part, 15 ... Type information transmission part, 16 ... Data reception part, 17 ... Data storage unit, 20 ... Distribution server, 21 ... Type information receiving unit, 22 ... Type information DB, 23 ... Distribution data instruction unit, 24 ... Update data storage unit, 25 ... Data distribution unit, B ... Radio base station, N ... Public communication network

Claims (4)

A mobile device that is transmitted from the server device and can acquire different update data for each type of mobile device,
Determination means for determining whether or not notification of the type information is necessary based on information indicating whether or not the latest type information of the mobile device is notified to the server device at the time of starting the mobile device or preparing for communication. When,
A mobile device comprising: a transmission unit configured to transmit the type information to the server device when the determination unit determines that the notification of the type information is necessary. Information indicating whether or not the server device is notified is a flag,
Holding means for holding type information of the mobile device;
Further comprising setting means for setting the flag on or off based on whether the type information of the mobile device is the same as the previous type information held in the holding means. The mobile device according to claim 1. A holding means for holding identification information of the UIM inserted in the mobile device;
The determination means notifies the type information based on whether or not the UIM identification information is the same as the previous identification information held in the holding means when the UIM is inserted into the mobile device. The mobile device according to claim 1, wherein whether or not it is necessary is determined. A determination step of determining whether or not notification of the type information is necessary based on information indicating whether or not the latest type information of the mobile device is notified to the server device at the time of start-up or communication preparation; ,
If it is determined in this determination step that notification of the type information is necessary, a transmission step of transmitting the type information to the server device;
A data acquisition method comprising: a reception step of receiving update data acquired by the server device with reference to the type information transmitted in the transmission step.

Images