Vehicle

Abstract

To avoid a failure of handshake between an on-vehicle device and a communicator caused by resetting of a modem of the communicator.SOLUTION: A vehicle comprises an on-vehicle device and a communicator. The communicator includes a modem, is connected with the on-vehicle device, and performs radio communication with a base station. The on-vehicle device and the communicator are configured to execute handshake with the start of power of the vehicle. The on-vehicle device is configured to generate diagnosis information when the handshake fails. The communicator is configured to be switchable between a first mode for permitting resetting of the modem according to a specific reason for rejection from the base station, and a second mode for inhibiting resetting of the modem according to the specific reason for rejection.SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] The present disclosure relates to a vehicle including an in-vehicle device and a communication device.

Background Art

[0002] Patent Document 1 discloses a modem inspection device that inspects a modem used for mobile data communication. The modem inspection device includes a reset unit that resets the modem.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] A vehicle including an in-vehicle device and a communication device connected to the in-vehicle device and performing wireless communication with a base station may have the following configuration. That is, a handshake by an initial sequence may be executed when the vehicle is powered on. And when the handshake fails, the in-vehicle device generates and records diagnostic information. According to such a configuration, when the diagnostic information is recorded, it can be found that there is a problem in the connection between the in-vehicle device and the communication device.

[0005] In a vehicle having the above-described configuration, when the communication device includes a modem that is reset when a specific rejection reason is received from the base station, there are the following problems. That is, the period of the above handshake may overlap with the period of resetting the modem. As a result, the handshake communication may not be established due to the reset of the modem, and diagnostic information may be recorded in an unintended manner.

[0006] The present disclosure has been made in view of the above-described problems, and an object thereof is to provide a vehicle capable of avoiding a failure of handshake between an in-vehicle device and a communication device due to reset of a modem of the communication device.

Means for Solving the Problems

[0007] A vehicle according to a first aspect of the present disclosure includes an in-vehicle device and a communication device. The communication device includes a modem, is connected to the in-vehicle device, and performs wireless communication with a base station. The in-vehicle device and the communication device are configured to execute a handshake when the vehicle is powered on (Configuration A). The in-vehicle device is configured to generate diagnostic information when the handshake fails (Configuration B). The communication device is configured to be switchable between a first mode that permits reset of the modem in response to a specific rejection reason from the base station and a second mode that prohibits reset of the modem in response to a specific rejection reason.

[0008] A vehicle according to a second aspect of the present disclosure includes an in-vehicle device and a communication device. The communication device is connected to the in-vehicle device and performs wireless communication with a base station. The vehicle includes the above-described Configurations A and B. The communication device includes a modem, a SIM that stores telephone number information, and a processor, and is configured to reset the modem after power-on when a specific rejection reason is received from the base station. The communication device is configured to be switchable between a first mode and a second mode. In the first mode, the processor executes an acquisition request for requesting the modem to acquire telephone number information from the SIM in response to a request for return of telephone number information from the in-vehicle device in the handshake, and when the resetting modem returns an error response to the processor, transmits a response without telephone number information to the in-vehicle device. In the second mode, the processor executes an acquisition request in response to the return request, prohibits responding to the in-vehicle device from the processor during reset when the resetting modem returns an error response to the processor, continues the acquisition request to the modem, executes the acquisition request after the reset is completed to acquire telephone number information from the SIM via the modem, and then transmits a response with telephone number information to the in-vehicle device.

[0009] The vehicle according to the third aspect of the present disclosure is different from the vehicle according to the second aspect in the operation of the second mode. Specifically, according to the third aspect, in the second mode, the processor executes an acquisition request in response to a reply request and waits for a reply to the in-vehicle device until a response to the acquisition request is transmitted from the modem. Then, in the second mode, when the modem receives an acquisition request during reset, it prohibits transmitting an error response to the processor until the reset is completed, requests the SIM to transmit the telephone number information after the reset is completed, and then transmits the telephone number information transmitted from the SIM to the processor.

[0010] The vehicle according to the fourth aspect of the present disclosure is different from the vehicle according to the second aspect in the operation of the second mode. Specifically, according to the fourth aspect, in the second mode, the processor executes an acquisition request in response to a reply request, and when the modem during reset returns an error response to the processor, prohibits a reply from the processor to the in-vehicle device until a retransmission of the reply request from the in-vehicle device to the processor is made.

Advantages of the Invention

[0011] According to the present disclosure, by pre-selecting the second mode, even if the above-mentioned specific rejection reason is actually notified, it is possible to avoid the failure of the handshake between the in-vehicle device and the communication device due to the reset of the modem of the communication device. Thereby, it is possible to prevent unintentional diagnostic information from being recorded.

Brief Description of the Drawings

[0012]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Mode for Carrying Out the Invention

[0013] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. In the drawings, the same reference numerals are assigned to common elements, and duplicate explanations are omitted or simplified.

[0014] 1. Example of Vehicle Configuration FIG. 1 is a diagram schematically showing an example of the configuration of a vehicle 1 according to the embodiment. The vehicle 1 includes an in-vehicle device 10 and a communication device (in-vehicle communication device) 20.

[0015] The in-vehicle device 10 is more specifically an in-vehicle electronic device, for example, a head unit of an in-vehicle multimedia system. The in-vehicle device 10 includes a processor 12 and a storage device 14. The processor 12 executes various processes described later. For example, the processor 12 includes a CPU (Central Processing Unit). The storage device 14 stores various information necessary for the processing by the processor 12. The storage device 14 is, for example, at least one of a volatile memory, a non-volatile memory, an HDD (Hard Disk Drive), and an SSD (Solid State Drive).

[0016] The in-vehicle device 10 is connected to the communication device 20. Specifically, the connection between the in-vehicle device 10 and the communication device 20 is a wired connection such as a USB connection, for example.

[0017] The communication device 20 is, for example, a DCM (Data Communication Module). The communication device 20 can communicate wirelessly with a network 40 provided by a mobile communication carrier with which the user of the vehicle 1 has a contract. More specifically, the communication device 20 can communicate with each base station constituting the network 40. The communication device 20 has, for example, a function of performing communication operations via the network 40 using a telephone number assigned to itself.

[0018] Specifically, the communication device 20 includes an application processor (AP) 22, a storage device 24, a modem 26, a SIM (Subscriber Identity Module) 28, and a backup power supply 30. The AP 22 executes various processes described later.

[0019] The AP 22 includes, for example, an AT command processing unit 32 and a SIM manager 34. The AT command processing unit 32 executes processes related to various AT commands transmitted from the in-vehicle device 10. The SIM manager 34 executes a process of acquiring various information such as telephone number information from the SIM 28 via the modem 26 in response to a request from the AT command processing unit 32.

[0020] The modem 26 includes a modulator that modulates information to be transmitted to the network 40, a demodulator that demodulates information received from the network 40, and a processor.

[0021] The SIM 28 may include an insertion part into which a SIM card can be inserted, or may include an eSIM (embedded Subscriber Identity Module) pre-mounted in the communication device 20. The SIM card or eSIM stores information used for communicating with the network 40. Specifically, the information stored in the SIM 28 includes telephone number information. Further, the SIM 28 includes, for example, a reader and a processor.

[0022] Also, even when the communication device 20 is not receiving power supply from the power source (battery) of the vehicle 1, it is periodically activated by the power supplied from the backup power source 30 and performs necessary communication (e.g., base station search) with the network 40.

[0023] 2. Handshake FIG. 2 is a sequence diagram for explaining the outline and problems of the handshake executed between the in-vehicle device 10 and the communication device 20. More specifically, the operations shown in FIG. 2 correspond to the operations at the time of the first mode selection described later.

[0024] When the accessory power source of the vehicle 1 is turned ON (ACC ON), power is supplied to the in-vehicle device 10 and the communication device 20. As a result, the USB connection becomes ON (if there is no problem with the connection). Then, when the ignition power source is turned ON (IG ON) following the accessory power source being ON (in other words, as the vehicle 1 is powered on), the in-vehicle device 10 and the communication device 20 execute a predetermined handshake as an initial sequence before starting normal communication. More specifically, such a handshake is performed each time the vehicle power is turned on.

[0025] In the handshake, first, for example, an "ACC ON instruction" for notifying the communication device 20 that the accessory power source has become ON is transmitted from the in-vehicle device 10 to the communication device 20. In response to receiving this instruction, an "ACC ON confirmation" indicating that it has been confirmed that the accessory power source is in the ON state is returned from the communication device 20 to the in-vehicle device 10. Although detailed explanation is omitted here, in the handshake, an exchange of a predetermined number of information is performed between the in-vehicle device 10 and the communication device 20. One such exchange of information is the AT command [AT$DNID] shown in FIG. 2. This AT command [AT$DNID] is for the in-vehicle device 10 to request the communication device 20 to transmit telephone number information.

[0026] In the handshake, the in-vehicle device 10 checks whether the connection between the in-vehicle device 10 and the communication device 20 is correctly established. If the handshake fails, the in-vehicle device 10 generates and records diagnostic information. The diagnostic information is generated, for example, as information indicating the disconnection of the USB cable. According to such a configuration, when the diagnostic information is recorded, it can be found that there is a problem with the connection between the in-vehicle device 10 and the communication device 20.

[0027] On the other hand, basically, when the communication device 20 receives a specific reject reason (RC) from a base station included in the network 40, it is configured to reset and initialize the modem 26 (the "first mode" according to the present embodiment). The "specific reject reason RC" here refers to a notification that requests the communication device 20 not to perform a base station search. Such a reject reason RC is notified, for example, when communication by the communication device 20 is performed when a vehicle 1 equipped with a communication device of the US specification (more specifically, a communication device with a US-specification SIM 28) is produced and shipped at a Japanese factory. That is, the reject reason RC is notified when communication by a communication device 20 for a certain country or region is performed in another country or region with a different communication standard (that is, outside the coverage area of the communication device 20). In addition, the notification of the reject reason RC is not limited to such factory shipment, and can also be notified, for example, during communication when the contract for the communication service using the communication device 20 is canceled by the user of the vehicle 1. The reason why the communication device 20 resets the modem 26 when receiving the reject reason RC is to attempt to search for another base station.

[0028] Here, the communication device 20 may communicate with the network 40 (base station) using the backup power supply 30 before the vehicle power supply is activated, for example, for the purpose of searching for a base station. When the communication device 20 performs such communication, it may receive a specific rejection reason RC as illustrated in FIG. 2. The reset of the modem 26 when the rejection reason RC is received is executed after the vehicle power supply is activated (after IG ON) as shown in FIG. 2. Therefore, the period of the reset of the modem 26 executed due to the communication before the vehicle power supply is activated overlaps with the period of the handshake executed with the activation of the vehicle power supply. Additionally, the reset period includes the period required for the initialization of the modem 26.

[0029] FIG. 2 illustrates a situation where the period of the reset of the modem 26 and the period of the handshake overlap as described above. When the reset of the modem 26 occurs during the handshake period in this way, the communication device 20 cannot perform the expected response of the in-vehicle device 10, and the handshake fails. That is, the handshake communication cannot be established. As a result, the in-vehicle device 10 generates the above-described diagnostic information (for example, information indicating the disconnection of the USB cable) and records it in the storage device 14.

[0030] More specifically, as shown in FIG. 2, when the AT command [AT$DNID] (request for telephone number information) is transmitted from the in-vehicle device 10 to the communication device 20 during the reset of the modem 26, an error response is made from the modem 26 to the AP22 (SIM manager 34). That is, the AP22 cannot obtain the telephone number information from the SIM 28. For this reason, as shown in FIG. 2, the communication device 20 (AP22) cannot return the telephone number information to the in-vehicle device 10. Details of such an operation are shown in the upper part of FIG. 4 described later. More specifically, in the example of the operation shown in FIG. 2, the communication device 20 (AP22) cannot return the telephone number information and returns (responds) only the result code of the "OK response". When only the result code of the "OK response" is returned in this way, the in-vehicle device 10 waits for the return of the telephone number information from the communication device 20 until a predetermined time (for example, 90 seconds) elapses from the time of transmission of the AT command [AT$DNID]. Then, when the predetermined time elapses without the return of the telephone number information, the in-vehicle device 10 generates the above-described diag information and records it in the storage device 14.

[0031] The handshake failure caused by the reset of the modem 26 as described above does not indicate that there is a problem with the connection itself between the in-vehicle device 10 and the communication device 20. In other words, the recording of the diag information at the time of the failure is made in an unintended form. However, for example, in a scenario where the diag information is recorded due to the reset of the modem 26 in the handshake executed when the vehicle power is turned on during the inspection at the time of factory shipment of the vehicle 1, the vehicle 1 may be erroneously determined to be non-conforming to the inspection and proceed to a reinspection.

[0032] Note that "command transmission stop" in the example of the operation shown in FIG. 2 means that the in-vehicle device 10 has stopped transmitting commands after the AT command [AT$DNID] because the result code of "OK response" has been returned from the communication device 20 to the in-vehicle device 10. Additionally, in the handshake, commands other than the AT command [AT$DNID] are for communication between the processor of the in-vehicle device 10 and the AP22, and thus can be executed regardless of whether the modem 26 is being reset.

[0033] In view of the above problems, in this embodiment, the communication device 20 is configured to be switchable between a "first mode" that permits reset of the modem 26 in response to a specific rejection reason RC from the base station and a "second mode" that prohibits reset of the modem 26 in response to the rejection reason RC. Mode information indicating whether the current mode of the modem 26 is the first or second mode is stored in the storage device 24 of the communication device 20. The switching of the mode of the modem 26 can be performed, for example, by a person operating a predetermined switching tool to update the mode information.

[0034] More specifically, the second mode is, for example, a mode (shipping mode) selected during the inspection at the time of factory shipment of the vehicle 1. Additionally, assuming the handshake at the time of factory shipment, the communication device 20 may be mounted on the vehicle 1, for example, with the second mode selected. Alternatively, for example, during the inspection at the time of factory shipment, the operator operating the above tool may switch from the first mode to the second mode. Then, for example, after the vehicle 1 is transported to the country or region where the user of the vehicle 1 is located, the switching from the second mode to the first mode may be performed.

[0035] Also, the second mode may be selected, for example, when the contract for the communication service using the communication device 20 is terminated by the user of the vehicle 1.

[0036] Additionally, the first mode is a basic mode that is selected, for example, when the second mode is not selected. Note that the mode of the modem 26 may include one or more modes other than the first and second modes.

[0037] FIG. 3 is a sequence diagram for explaining the handshake operation when the second mode is selected according to the embodiment (corresponding to the "first aspect" according to the present disclosure). Similar to FIG. 2, FIG. 3 targets the scenario where a specific rejection reason RC is notified.

[0038] The communication device 20 (AP22) can determine whether the current mode of the modem 26 is either the first or second mode based on the above mode information stored in the storage device 24. When the current mode is the second mode when the vehicle power is activated, as shown in FIG. 3, the reset of the modem 26 according to the rejection reason RC is prohibited. Thereby, even when the rejection reason RC is notified, the AP22 (SIM manager 34) can acquire the phone number information from the SIM 28 via the modem 26 in response to the AT command [AT$DNID] from the in-vehicle device 10 during the execution of the handshake. For this reason, as shown in FIG. 3, the communication device 20 can reply to the in-vehicle device 10 with the phone number information together with the result code of "OK response".

[0039] As described above, according to the present embodiment, the communication device 20 is configured to be able to switch between the first mode and the second mode. Therefore, by pre-selecting the second mode as a mode for scenarios where the reception of a specific rejection reason RC such as at factory shipment is assumed, even if the rejection reason RC is actually notified, it is possible to avoid the failure of the handshake between the in-vehicle device 10 and the communication device 20 due to the reset of the modem 26. Thereby, it is possible to prevent unintentional diagnostic information from being recorded.

[0040] In addition, when the second mode is selected at the time of factory shipment, unintentional diagnostic information resulting from the reset of the modem 26 is not recorded, thereby avoiding the vehicle 1 being erroneously determined to be inspection non-conforming due to the recording of such unintentional diagnostic information.

[0041] 3. Modification Example In order to avoid the failure of the handshake described above, instead of the example shown in FIG. 3, for example, any one of the following first to third modification examples may be executed.

[0042] 3-1. First Modification Example (corresponding to the "second aspect" according to the present disclosure) FIG. 4 is a sequence diagram for explaining the operation related to the acquisition of telephone number information according to the first modification example of the embodiment. More specifically, in FIG. 4, the upper part shows the operation related to the acquisition of telephone number information when the first mode is selected, and the lower part shows the operation related to the acquisition of telephone number information when the second mode is selected. Note that FIG. 4, similar to FIGS. 2 and 3, targets the scenario where a specific rejection reason RC is notified. And in response to the notification of the rejection reason RC, the communication device 20 resets the modem 26 as the vehicle power is turned on as shown in FIG. 4. This also applies to FIGS. 5 and 6 described later.

[0043] First, the operation when the first mode is selected according to the first modification example is the same as the operation when the AT command [AT$DNID] is transmitted in FIG. 2. That is, in the first mode, the AP 22 requests the modem 26 to execute an "acquisition request R2" for acquiring telephone number information from the SIM 28 in response to the "reply request R1" (that is, the AT command [AT$DNID]) of the telephone number information from the in-vehicle device 10 in the handshake. More specifically, the AT command processing unit 32 that has received the reply request R1 from the in-vehicle device 10 transmits the reply request R1 to the SIM manager 34. Then, the SIM manager 34 that has received the reply request R1 transmits the acquisition request R2 to the modem 26.

[0044] However, since the modem 26 that has received the acquisition request R2 is in the process of resetting, it cannot transmit the acquisition request R2 to the SIM 28. That is, the modem 26 cannot receive (acquire) the telephone number information from the SIM 28. As a result, the modem 26 returns an error response to the SIM manager 34. As a result, the SIM manager 34 that has received the error response from the modem 26 transmits a response without telephone number information (i.e., only the result code of the "OK response") to the AT command processing unit 32. Then, the AT command processing unit 32 transmits the said response to the in-vehicle device 10.

[0045] Next, the second mode according to the first modification example will be described. Similar to the second mode shown in FIG. 3, specific examples of this second mode also include the mode (shipping mode) selected during the inspection at the time of factory shipment of the vehicle 1, and the time when the user cancels the communication service. The operation at the time of selection of this second mode differs from the second mode according to the example shown in FIG. 3 in the following points. That is, as shown in the lower part of FIG. 4, the modem 26 is reset in response to the reception of the rejection reason RC. For this reason, the modem 26 that has received the acquisition request R2 based on the reply request R1 from the in-vehicle device 10 returns an error response to the SIM manager 34 in the same manner as when the first mode is selected.

[0046] Moreover, in this second mode, the SIM manager 34 that has received the error response from the modem 26 continues to send the acquisition request R2 to the modem 26 while prohibiting the reply from the AP 22 to the in-vehicle device 10 during the reset. For example, the retry of the acquisition request R2 is repeatedly executed every predetermined time (for example, several seconds). More specifically, the time required for the reset (including initialization) of the modem 26 is, for example, 6 to 10 seconds. The predetermined time regarding the above retry is set to be shorter than the time required for the reset of the modem 26. Additionally, the time required for the reset of the modem 26 is shorter than the predetermined time (i.e., the predetermined time from the transmission time of the AT command [AT$DNID]) for the in-vehicle device 10 to determine whether to generate the above diagnostic information.

[0047] When the reset of the modem 26 is completed, as shown in the lower part of FIG. 4, the SIM 28 can receive the acquisition request R2 from the modem 26. The SIM 28 that has received the acquisition request R2 after the reset as described above transmits the requested telephone number information to the modem 26. The modem 26 that has received the telephone number information from the SIM 28 transmits the telephone number information to the SIM manager 34. Then, the AP 22 that has received (acquired) the telephone number information from the modem 26 releases the reply prohibition to the in-vehicle device 10 and transmits a reply accompanied by the telephone number information (that is, the telephone number information and the result code of the "OK response") to the in-vehicle device 10. More specifically, the reply is transmitted from the SIM manager 34 to the in-vehicle device 10 via the AT command processing unit 32.

[0048] As described above, also according to the first modification example, the communication device 20 is configured to be able to switch between the first mode and the second mode. Therefore, by pre-selecting the second mode as a mode for a scenario where reception of a specific rejection reason RC such as at the time of factory shipment is assumed, even if the rejection reason RC is actually notified, the handshake failure can be avoided by the AP 22 (SIM manager 34) operating as shown in the lower part of FIG. 4. Thereby, it is possible to prevent unintended diagnostic information from being recorded.

[0049] 3-2. Second Modification Example (Corresponding to the "Third Aspect" according to the Present Disclosure) FIG. 5 is a sequence diagram for explaining the operation related to the acquisition of telephone number information at the time of selecting the second mode according to the second modification example of the embodiment. The operation at the time of selecting the first mode according to the second modification example is the same as that in the upper part of FIG. 4, and thus the illustration thereof is omitted. Specific examples of the second mode according to the second modification example also include the mode (shipping mode) selected at the time of inspection at the time of factory shipment of the vehicle 1 and the time of cancellation of the communication service by the user, similar to the second mode shown in FIG. 3.

[0050] The operation during the selection of this second mode differs from the second mode according to the first modification example in the following points. That is, when the acquisition request R2 is received from the AP22 (SIM manager 34) during the reset in response to the reception of the rejection reason RC, the modem 26 prohibits sending an error response to the acquisition request R2 to the SIM manager 34 until the reset is completed. On the other hand, the AP22 (SIM manager 34) waits (stands by) for a response to the in-vehicle device 10 until a response to the acquisition request R2 is sent from the modem 26.

[0051] After the reset is completed thereafter, the modem 26 sends the acquisition request R2 to the SIM28 (that is, requests the SIM28 to send the telephone number information). Then, the modem 26 sends the telephone number information sent from the SIM28 to the AP22 (SIM manager 34) (that is, responds to the acquisition request R2 from the SIM manager 34). The AP22 that has received the telephone number information from the modem 26 releases the standby state for the response to the in-vehicle device 10 and sends a response accompanied by the telephone number information (that is, the telephone number information and the result code of the "OK response") to the in-vehicle device 10.

[0052] As described above, also according to the second modification example, the communication device 20 is configured to be able to switch between the first mode and the second mode. Therefore, by pre-selecting the second mode as a mode for a scenario where the reception of a specific rejection reason RC such as at the time of factory shipment is assumed, even if the rejection reason RC is actually notified, it is possible to avoid the failure of the handshake by the AP22 (SIM manager 34) and the modem 26 that operate as shown in FIG. 5. Thereby, it is possible to prevent unintended diagnostic information from being recorded.

[0053] Supplement on the standby (standby) for the response from the in-vehicle device 10 by AP22 (SIM manager 34) in the second modification example. During such standby for the response, AP22 may determine whether or not a predetermined time has elapsed since the start of the standby. This predetermined time is set to be longer than the time required for resetting (including initialization) the modem 26. And if a response to the acquisition request R2 is not transmitted from the modem 26 during the predetermined time, AP22 may end the standby state and transmit an error response to the in-vehicle device 10. According to such processing, when a response from the modem 26 to AP22 is not transmitted due to the fact that the modem 26 or the SIM 28 is not functioning properly, such an abnormality of the modem 26 or the SIM 28 can be notified to the in-vehicle device 10.

[0054] 3-3. Third Modification Example (corresponding to the "fourth aspect" according to the present disclosure) FIG. 6 is a sequence diagram for explaining the operation regarding the acquisition of telephone number information at the time of selecting the second mode according to the third modification example of the embodiment. Since the operation at the time of selecting the first mode according to the third modification example is the same as that in the upper part of FIG. 4, its illustration is omitted. Specific examples of the second mode according to the third modification example also include the mode (shipping mode) selected during the inspection at the time of factory shipment of the vehicle 1 and the time of cancellation of the communication service by the user, similar to the second mode shown in FIG. 3.

[0055] The operation at the time of selecting this second mode is different from the second mode according to the first modification example in the following points. That is, when an error response is received from the modem 26 during reset in response to the reception of the rejection reason RC, AP22 (SIM manager 34) prohibits the response from AP22 to the in-vehicle device 10 until a retransmission (retry) of the return request R1 from the in-vehicle device 10 to AP22 is made. In other words, AP22 (SIM manager 34) waits for the retransmission of the return request R1 from the in-vehicle device 10.

[0056] More specifically, the period from the time of sending the first reply request R1 by the in-vehicle device 10 to the time of retransmission (for example, 10 to 20 seconds) is longer than the time required for resetting (including initialization) of the modem 26, and is set to be shorter than a predetermined time for determining whether the in-vehicle device 10 generates the above-described diag information (shorter than the "predetermined time from the time of sending the AT command [AT$DNID]").

[0057] When the in-vehicle device 10 retransmits (retry) the reply request R1 to the AP 22, as shown in FIG. 6, an acquisition request R2 is transmitted from the AP 22 that has received the retransmitted reply request R1 to the modem 26. Then, the telephone number information transmitted from the SIM 28 in response to the acquisition request R2 from the modem 26 is transmitted to the in-vehicle device 10 via the modem 26 and the AP 22.

[0058] As described above, also according to the third modification example, the communication device 20 is configured to be able to switch between the first mode and the second mode. For this reason, by pre-selecting the second mode as a mode for a scenario where reception of a specific rejection reason RC such as at the time of factory shipment is assumed, even if the rejection reason RC is actually notified, the handshake failure can be avoided by the AP 22 (SIM manager 34) that operates as shown in FIG. 6 in anticipation of retransmission of the reply request from the in-vehicle device 10. Thereby, it is possible to prevent unintentional diag information from being recorded.

Description of Reference Numerals

[0059] 1 Vehicle, 10 In-vehicle device, 20 Communication device, 22 Application processor, 24 Storage device, 26 Modem, 28 SIM, 30 Backup power supply, 32 AT command processing unit, 34 SIM manager, 40 Network

Claims

1. An in-vehicle device, a communication device including a modem, connected to the in-vehicle device, and performing wireless communication with a base station, A vehicle comprising: The in-vehicle device and the communication device are configured to perform a handshake upon startup of the vehicle's power supply. The in-vehicle device is configured to generate diagnostic information when the handshake fails. The communication device is configured to be switchable between a first mode that permits reset of the modem in response to a specific rejection reason from the base station and a second mode that prohibits reset of the modem in response to the specific rejection reason. Vehicle.

2. A vehicle comprising an in-vehicle device and a communication device connected to the in-vehicle device and performing wireless communication with a base station, The in-vehicle device and the communication device are configured to perform a handshake upon startup of the vehicle's power supply. The in-vehicle device is configured to generate diagnostic information when the handshake fails. The communication device includes a modem, a SIM storing telephone number information, and a processor. When receiving a specific rejection reason from the base station, the communication device is configured to reset the modem after startup of the power supply. The communication device is configured to be switchable between a first mode and a second mode. In the first mode, the processor executes an acquisition request to request the modem to acquire the telephone number information from the SIM in response to a reply request for the telephone number information from the in-vehicle device in the handshake. When the modem during reset returns an error response to the processor, the communication device transmits a reply without the telephone number information to the in-vehicle device. In the second mode, the processor executes the acquisition request in response to the reply request. When the modem during reset returns the error response to the processor, while prohibiting the processor from replying to the in-vehicle device during reset, the communication device continues the acquisition request to the modem and after completion of the reset, executes the acquisition request to acquire the telephone number information from the SIM via the modem and then transmits a reply with the telephone number information to the in-vehicle device. Vehicle.

3. A vehicle comprising an in-vehicle device and a communication device connected to the in-vehicle device and performing wireless communication with a base station, The in-vehicle device and the communication device are configured to perform a handshake upon startup of the vehicle's power supply. The in-vehicle device is configured to generate diagnostic information when the handshake fails. The communication device includes a modem, a SIM that stores telephone number information, and a processor, and is configured to reset the modem after power-on when a specific rejection reason is received from the base station. The communication device is configured to be able to switch between a first mode and a second mode. In the first mode, the processor executes an acquisition request to request the modem to acquire the telephone number information from the SIM in response to a reply request for the telephone number information from the in-vehicle device in the handshake. When the modem during reset returns an error response to the processor, it transmits a reply without the telephone number information to the in-vehicle device. In the second mode, the processor executes the acquisition request in response to the reply request. waits for a reply to the in-vehicle device until a response to the acquisition request is transmitted from the modem. In the second mode, the modem prohibits transmitting the error response to the processor until the reset ends when the acquisition request is received during the reset. requests the SIM to transmit the telephone number information after the reset ends, and then transmits the telephone number information transmitted from the SIM to the processor. Vehicle.

4. The second mode is a mode selected during inspection at the time of factory shipment of the vehicle. The vehicle according to any one of claims 1 to 3.

Images