Information processing device, information processing method, and information processing system

Abstract

An information processing device according to the present disclosure comprises a control unit and a communication unit. The control unit acquires a contract profile held by a subscriber identification medium mounted on each of a plurality of terminal devices. The control unit holds a plurality of contract profiles in different electronic subscriber identification media, respectively. The control unit selects an electronic subscriber identification medium to be used for communication. The communication unit performs communication according to a contract profile held by the electronic subscriber identification medium.

Description

Information processing device, information processing method, and information processing system

[0001] The present disclosure relates to an information processing device, an information processing method, and an information processing system.

[0002] For example, in recent years, a technology has become known that allows a single communication device to use multiple cellular communications. For example, a communication device equipped with multiple SIMs (Subscriber Identity Modules) can select one of the multiple cellular communications by switching the SIM used for communication.

[0003] There is also known a system that allows a user to use a profile of a mobile communication service that the user is using on a mobile device when the user gets into a car, in an in-car communication device installed in the car.

[0004] JP 2019-193190 A JP 2023-15957 A JP 2022-88980 A

[0005] There may be cases where multiple users wish to receive the provision of a single application service in a car or other room. For example, there is a demand for multiple users to enjoy a music or video distribution service in a car.

[0006] In this case, when a user receives these services on a mobile device owned by the user, the user must determine which mobile device the user owns and on which service the user can receive. Also, if there are multiple mobile devices that can receive the service, the user must decide which user's mobile device the user will use to receive the service.

[0007] In this way, when multiple users receive the same service, the users may be required to perform many operations. Therefore, a mechanism that allows multiple users to receive the service more easily is required.

[0008] Therefore, the present disclosure proposes an information processing device, an information processing method, and an information processing system that allow multiple users to more easily receive the provision of services.

[0009] It should be noted that the above problem or object is merely one of multiple problems or objects that can be solved or achieved by multiple embodiments disclosed in this specification.

[0010] The information processing device disclosed herein includes a control unit and a communication unit. The control unit acquires contract profiles held by subscriber identification media installed in each of a plurality of terminal devices. The control unit holds each of the plurality of contract profiles in a different electronic subscriber identification medium. The control unit selects the electronic subscriber identification medium to be used for communication. The communication unit performs the communication according to the contract profiles held by the electronic subscriber identification medium.

[0011] 1 is a diagram illustrating an example of information processing executed in an information processing system according to a proposed technique of the present disclosure. FIG. 2 is a diagram illustrating an example of the overall configuration of an information processing system according to a first embodiment of the present disclosure. FIG. 3 is a block diagram illustrating an example of the configuration of a database server according to a first embodiment of the present disclosure. FIG. 4 is a block diagram illustrating an example of the configuration of a terminal device according to a first embodiment of the present disclosure. FIG. 5 is a block diagram illustrating an example of the configuration of an in-vehicle device according to a first embodiment of the present disclosure. FIG. 6 is a diagram illustrating an example of a contract table according to a first embodiment of the present disclosure. FIG. 7 is a sequence diagram illustrating an example of an acquisition process according to a first embodiment of the present disclosure. FIG. 8 is a sequence diagram illustrating an example of a generation process according to a first embodiment of the present disclosure. FIG. 9 is a flowchart illustrating an example of the flow of an execution process according to the first embodiment of the present disclosure. FIG. 10 is a diagram illustrating an example of a switching process according to a second embodiment of the present disclosure. FIG. 11 is a diagram illustrating an example of a switching process according to a second embodiment of the present disclosure. FIG. 12 is a diagram illustrating an example of the overall configuration of an information processing system according to a second embodiment of the present disclosure. FIG. 13 is a block diagram illustrating an example of the configuration of a detection server according to a second embodiment of the present disclosure. FIG. 14 is a sequence diagram illustrating an example of a notification process according to a second embodiment of the present disclosure. FIG. 15 is a flowchart illustrating an example of the flow of a determination process according to a second embodiment of the present disclosure.

[0012] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In this specification and drawings, components having substantially the same functional configurations are designated by the same reference numerals, and redundant description will be omitted.

[0013] In addition, in this specification and drawings, similar components of the embodiments may be distinguished by adding at least one different alphabet and number after the same reference numeral.

[0014] However, when there is no need to particularly distinguish between similar components, only the same reference numerals are used. For example, multiple components having substantially the same functional configurations are distinguished as necessary, such as a first terminal device 300A and a second terminal device 300B. For example, when there is no need to particularly distinguish between the first terminal device 300A and the second terminal device 300B, they are simply referred to as terminal devices 300.

[0015] One or more embodiments (including examples, modifications, and application examples) described below can be implemented independently. However, at least a portion of the embodiments described below may be implemented in appropriate combination with at least a portion of another embodiment. These embodiments may include novel features that are different from each other. Therefore, these embodiments may contribute to solving different purposes or problems and may produce different effects from each other.

[0016] <<1. Introduction>> <1-1. Problems> For example, there is a demand for richer enjoyment of entertainment content (hereinafter also simply referred to as content) such as music and videos inside an automobile (vehicle). One method for enjoying such content inside a vehicle is to use a terminal device, such as a smartphone or tablet, carried by the passenger.

[0017] However, terminal devices such as smartphones have small displays and may have low-performance speakers (sound devices). If multiple users want to enjoy richer content in a car, terminal devices such as smartphones may not provide sufficient satisfaction.

[0018] Therefore, one possible method is to connect an information processing device (hereinafter also referred to as an in-vehicle device) installed in a vehicle to a terminal device using, for example, Bluetooth (registered trademark) or Wi-Fi (registered trademark), and play content acquired by the terminal device on the in-vehicle device.

[0019] Generally, speakers installed in automobiles have higher performance than speakers installed in terminal devices. Furthermore, displays are often installed in positions that are easily visible to users inside the vehicle. Therefore, by playing content on an in-vehicle device, multiple users can enjoy the content in a richer way than when playing content on a terminal device.

[0020] However, when the in-vehicle device and the terminal device are connected by tethering using Bluetooth, Wi-Fi, or the like, the speed at which content is downloaded, for example, depends on the communication performance and communication conditions of the terminal device.

[0021] Therefore, if the communication performance of the terminal device is low or the communication conditions are poor, it may take a long time to download the content, delays may occur, or the playback of the content may be interrupted.

[0022] Furthermore, tethering may increase the power consumption of the terminal device and cause it to heat up.

[0023] One possible solution to this problem is to install a SIM card in the in-vehicle device and have the in-vehicle device perform communications such as downloading content. In-vehicle devices have greater flexibility in terms of the placement and performance of antennas and communication devices compared to terminal devices, making it easier to improve communication performance than terminal devices.

[0024] In this case, depending on the frequency of use of the vehicle, it is difficult to conclude a communication contract that is linked to the in-vehicle device and incurs fees. Also, in the case of car sharing, it is difficult to conclude a personalized contract for the vehicle. For this reason, it is desirable to divert the contract concluded with the terminal device used by the user to communication with the in-vehicle device.

[0025] Here, a technique is known in which a SIM card installed in an in-vehicle device is linked one-to-one with a SIM card installed in a user's terminal device.

[0026] However, the above-mentioned technology only allows a one-to-one link between a SIM card installed in a terminal device and a SIM card installed in an in-vehicle device, and therefore the in-vehicle device cannot receive services that are not subscribed to by the user who owns the linked terminal device.

[0027] For example, when multiple users are riding in a car, it is conceivable that all of the users may wish to enjoy a service to which a specific user has subscribed.

[0028] In this case, if it is only possible to link the SIM installed in one terminal device with the SIM installed in the in-vehicle device on a one-to-one basis, it is necessary to link the SIM of the terminal device and the in-vehicle device of a specific user who has subscribed to a service that multiple users want to enjoy.

[0029] Furthermore, when switching services, the SIM card of the terminal device of the user who has subscribed to the service to be switched to must be linked to the new SIM card of the in-vehicle device, which complicates the user's procedures and creates the problem that services cannot be switched immediately.

[0030] As such, there is a demand for a system that allows multiple users to more easily receive services in a car or the like.

[0031] 1 is a diagram illustrating an example of information processing executed in an information processing system according to the proposed technology of the present disclosure. The information processing system according to the proposed technology includes an in-vehicle device 100 and multiple terminal devices 300 (first to third terminal devices 300A to 300C in the example of FIG. 1).

[0032] The multiple terminal devices 300 are devices owned by multiple users, respectively. The terminal devices 300 are equipped with SIMs 400 (an example of a subscriber identification medium). In the example of FIG. 1, first to third terminal devices 300A to 300C are equipped with first to third SIMs 400A to 400C, respectively. Although FIG. 1 shows a case where one terminal device 300 is equipped with one SIM 400, one terminal device 300 may be equipped with multiple SIMs 400.

[0033] The SIM holds information about the terminal device 300 (an example of a contract profile), such as a subscriber number called an IMSI (International Mobile Subscriber Identity) and information about the contract of the terminal device 300 .

[0034] The SIM installed in the terminal device 300 may be a physical SIM (for example, a SIM card), or may be an electronic SIM called an eSIM (embedded SIM) or a soft SIM.

[0035] The terminal device 300 communicates with the base station 500 in accordance with the contract profile held by the SIM 400. In the example of Fig. 1, the first terminal device 300A communicates with the first base station 500A, the second terminal device 300B communicates with the second base station 500B, and the third terminal device 300C communicates with the third base station 500C. In other words, it is assumed here that the first to third terminal devices 300A to 300C each have a contract with a different telecommunications carrier.

[0036] The in-vehicle device 100 is an information processing device mounted on, for example, an automobile 10. The in-vehicle device 100 is equipped with a plurality of eSIMs 200 (an example of an electronic subscriber identity medium). In the example of Fig. 1, the in-vehicle device 100 is equipped with first to third eSIMs 200A to 200C.

[0037] The in-vehicle device 100 executes information processing, for example, when a plurality of users get into the automobile 10 and the engine of the automobile 10 is started. The terminal device 300 is a device used by the users.

[0038] First, the in-vehicle device 100 acquires a contract profile (e.g., information about the terminal device 300, such as the IMSI) held by the SIM 400 installed in the terminal device 300 from the terminal device 300, and stores the acquired contract profile in the eSIM 200 (step S1).

[0039] In the example of FIG. 1, the in-vehicle device 100 acquires contract profiles held in the first to third SIMs 400A to 400C from the first to third terminal devices 300A to 300C.

[0040] For example, the in-vehicle device 100 stores the contract profile stored in the first SIM 400A in the first eSIM 200A. The in-vehicle device 100 stores the contract profile stored in the second SIM 400B in the second eSIM 200B. The in-vehicle device 100 stores the contract profile stored in the third SIM 400C in the third eSIM 200C.

[0041] The in-vehicle device 100 selects the eSIM 200 to be used for communication (step S2). In the example of Fig. 1, it is assumed that the in-vehicle device 100 selects the second eSIM 200B.

[0042] For example, the in-vehicle device 100 selects the eSIM 200 to be used for communication in accordance with an instruction from the user or information regarding a contract that the terminal device 300 has concluded.

[0043] As described above, the terminal device 300 has a contract with a telecommunications carrier and performs communications such as cellular communications. In addition to the contract with the telecommunications carrier, the terminal device 300 may also have a contract with a service distribution provider to receive a distribution service for music, video, and the like.

[0044] For example, it is assumed here that the second terminal device 300B in FIG. 1 (more specifically, the user of the second terminal device 300B) has signed a contract to receive a music distribution service.

[0045] The terminal device 300 holds information relating to a contract between a user and a telecommunications carrier or service provider (hereinafter also referred to as contract information).

[0046] For example, the first terminal device 300A holds contract information with a telecommunications carrier (e.g., "unlimited data plan A"), while the second terminal device 300B holds contract information with a telecommunications carrier (e.g., "unlimited data plan B") and contract information with a music distribution provider (e.g., "paid music distribution plan B"). For example, the third terminal device 300C holds contract information with a telecommunications carrier (e.g., "1 gigabit data plan C").

[0047] For example, when a user (not shown) of the automobile 10 desires to receive a music distribution service, more specifically, when the user instructs the execution of an application that executes the music distribution service, the in-vehicle device 100 selects the second eSIM 200B because the second terminal device 300B linked to the second eSIM 200B has signed a contract to receive the music distribution service.

[0048] In this way, the in-vehicle device 100 selects the eSIM 200 to use for communication, for example, according to the contract information corresponding to the application to be executed.

[0049] The in-vehicle device 100 communicates with the second base station 500B according to the contract profile held by the selected second eSIM 200B (step S3).

[0050] In this way, the in-vehicle device 100 according to the proposed technology stores the contract profiles of the multiple SIMs 400 mounted on the multiple terminal devices 300, linking them to the multiple eSIMs 200 mounted on the in-vehicle device 100 itself. The in-vehicle device 100 selects one of the multiple eSIMs 200 and performs communication.

[0051] This allows the in-vehicle device 100 to select an appropriate eSIM 200 and perform communication without the user having to switch the SIM 400. This allows multiple users in the automobile 10 to more easily receive services such as communication and music distribution. In this way, multiple users in the automobile 10 can enjoy entertainment using high-speed, large-capacity communication within the automobile 10.

[0052] Note that, although a case where multiple users receive the provision of services in a vehicle is assumed here, the location where multiple users receive the provision of services is not limited to a vehicle. For example, the proposed technology of the present disclosure can also be applied to a case where multiple users receive the provision of services in a living room. For example, the proposed technology of the present disclosure can be applied when multiple users receive the provision of services on a large display such as a television or a high-performance audio device such as a surround speaker. In this case, an information processing device (in-vehicle device 100) according to the proposed technology of the present disclosure can be mounted on the display, audio device, or the like.

[0053] 1, the number of terminal devices 300 is three, but the number of terminal devices 300 is not limited to three. The number of terminal devices 300 may be any number as long as it is plural, and may be two, four or more.

[0054] 1, the number of eSIMs 200 mounted on the in-vehicle device 100 is three, but the number of eSIMs 200 is not limited to three. The number of eSIMs 200 may be any number as long as it is plural, and may be two, four, or more.

[0055] Furthermore, the number of eSIMs 200 and the number of terminal devices 300 may be the same or different. For example, the number of eSIMs 200 may be equal to or greater than the number of terminal devices 300, or may be less than the number of terminal devices 300.

[0056] <<2. First embodiment>> <2-1. Example configuration of information processing system> <2-1-1. Example overall configuration of information processing system> Fig. 2 is a diagram showing an example overall configuration of an information processing system according to a first embodiment of the present disclosure. The information processing system shown in Fig. 2 includes an in-vehicle device 100 mounted on an automobile 10, a terminal device 300, a database server 600, and an operator server 700.

[0057] (In-vehicle device 100) The in-vehicle device 100 is an information processing device mounted on the automobile 10. The in-vehicle device 100 performs communication by copying, for example, a contract profile held by a SIM 400 mounted on the terminal device 300 to an eSIM 200 (not shown) mounted on the in-vehicle device 100 itself.

[0058] The in-vehicle device 100 communicates with a database server 600 and the like via a network. The in-vehicle device 100 is connected to the network via, for example, a base station 500 (not shown). The in-vehicle device 100 may also communicate with an application server (not shown) that provides services such as music, videos, and games.

[0059] Furthermore, the in-vehicle device 100 communicates directly with the terminal device 300 without using a network. Examples of direct communication include tethering and side link communication using Bluetooth communication or Wi-Fi communication.

[0060] (Terminal Device 300) The terminal device 300 is, for example, an information processing device used by a user riding in the automobile 10. Examples of the terminal device 300 include a smartphone and a tablet. The terminal device 300 performs communication according to a contract profile held in a SIM 400 (not shown) installed in the terminal device 300.

[0061] The terminal device 300 communicates with a provider server 700 or the like via a network. The terminal device 300 connects to the network via, for example, a base station 500 (not shown). The terminal device 300 may also communicate with an application server (not shown) that provides services such as music, videos, and games.

[0062] (Database Server 600) The database server 600 is an information processing device that stores information (hereinafter also referred to as plan information) relating to the content of a contract that the terminal device 300 may enter into with a telecommunications carrier, etc. The plan information may include, for example, the amount of data that the terminal device 300 can use in a certain period (e.g., one month).

[0063] The database server 600 communicates with the in-vehicle device 100, the carrier server 700, etc. via the network. For example, the database server 600 acquires a list of contract details provided by the telecommunications carrier as plan information from the carrier server 700. The database server 600 notifies the in-vehicle device 100 of the plan information in response to a request from the in-vehicle device 100.

[0064] (Provider Server 700) The provider server 700 is an information processing device that provides communication services to the terminal device 300 and the like. The provider server 700 manages information (e.g., plan information, contract information, etc.) related to services subscribed to by the terminal device 300. The provider server 700 may also have a core network function.

[0065] The business operator server 700 provides communication services to, for example, the terminal device 300 and the in-vehicle device 100. The business operator server 700 also notifies the database server 600 and the terminal device 300 of information related to the contract concluded by the terminal device 300 (for example, plan information, contract information, etc.).

[0066] 3 is a block diagram showing an example of the configuration of the database server 600 according to the first embodiment of the present disclosure. The database server 600 is, for example, a server device (information processing device) that holds a database that stores plan information.

[0067] The database server 600 shown in Fig. 3 includes a communication unit 610, a storage unit 620, and a control unit 630. The configuration shown in Fig. 3 is a functional configuration, and the hardware configuration may be different from this.

[0068] Furthermore, the functions of the database server 600 may be statically or dynamically distributed and implemented in multiple physically separated configurations. The database server 600 may be configured by multiple server devices.

[0069] (Communication Unit 610) The communication unit 610 is a communication interface for communicating with other devices (for example, the in-vehicle device 100). The communication unit 610 may be a network interface or a device connection interface.

[0070] The communication unit 610 may be a LAN (Local Area Network) interface such as a NIC (Network Interface Card), or may be a USB (Universal Serial Bus) host controller or a USB interface configured by a USB port or the like.

[0071] The communication unit 610 may be a wired interface or a wireless interface. The communication unit 610 is controlled by the control unit 630.

[0072] (Storage Unit 620) The storage unit 620 is a readable and writable storage device such as a dynamic random access memory (DRAM), a static random access memory (SRAM), a flash memory, a hard disk, etc. The storage unit 620 has, for example, a plan information database (DB) 621.

[0073] The plan information DB 621 stores information (e.g., plan information) related to service plans (communication plans) provided by, for example, a telecommunications carrier. The plan information may include, for example, at least one of information related to the telecommunications carrier, information related to the service name (plan name), and information related to the service content (plan content).

[0074] The information relating to the service name may be the name of the service, such as "unlimited communication plan A," or may be identification information for identifying the service.

[0075] The information about the service content may include, for example, an upper limit (e.g., "unlimited" or "10 GB") on the amount of data that can be used in a certain period (e.g., one month). The information about the service content may also include, for example, information about communication standards such as "LTE (Long Term Evolution)" or "5G."

[0076] Furthermore, the information regarding the service content may include information regarding services that are associated with service plans provided by the telecommunications carrier, such as a specific video distribution service.

[0077] (Control Unit 630) The control unit 630 is a controller that controls each unit of the database server 600. The control unit 630 is realized by a processor such as a CPU (Central Processing Unit) or an MPU (Micro Processing Unit).

[0078] For example, the control unit 630 is realized by a processor executing various programs stored in a storage device inside the database server 600 using RAM (Random Access Memory) or the like as a working area.

[0079] The control unit 630 may be realized by an integrated circuit such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA). A CPU, an MPU, an ASIC, and an FPGA can all be considered as controllers.

[0080] The control unit 630 acquires plan information relating to a service plan from the carrier server 700 via, for example, the communication unit 610. The control unit 630 stores the acquired plan information in the plan information DB 621 in association with the telecommunications carrier.

[0081] 4 is a block diagram showing a configuration example of the terminal device 300 according to the first embodiment of the present disclosure. The terminal device 300 is, for example, a communication device such as a smartphone or a tablet.

[0082] 4 includes a first communication unit 310, a second communication unit 320, a storage unit 330, an input / output unit 340, and a control unit 350. The terminal device 300 also includes a SIM 400 installed therein.

[0083] (SIM 400) The SIM 400 holds a contract profile 401 that is used when the terminal device 300 performs communication. The SIM 400 may be a physical SIM (for example, a SIM card) or an electronic SIM such as an eSIM.

[0084] The contract profile 401 includes, for example, subscriber information about a user who has a contract with a telecommunications carrier, such as a subscriber number, such as an IMSI.

[0085] (First communication unit 310) The first communication unit 310 is, for example, a communication interface for directly communicating with the in-vehicle device 100. The first communication unit 310 performs communication in accordance with a communication standard such as Bluetooth or Wi-Fi. The first communication unit 310 is controlled by the control unit 350.

[0086] (Second communication unit 320) The second communication unit 320 is a communication interface for communicating in accordance with the contract profile 401 held by the SIM 400. The second communication unit 320 communicates in accordance with a communication standard such as cellular communication. The second communication unit 320 is controlled by the control unit 350.

[0087] Here, the terminal device 300 is described as having two communication units (first and second communication units 310 and 320), but the number of communication units included in the terminal device 300 is not limited to two. For example, in a case where one communication unit can perform both direct communication and cellular communication with the in-vehicle device 100, such as side link communication, the number of communication units included in the terminal device 300 may be one.

[0088] (Storage unit 330) The storage unit 330 is a readable / writable storage device such as a DRAM, an SRAM, a flash memory, or a hard disk. The storage unit 330 stores, for example, application programs and the like that are used by the terminal device 300 to execute information processing and the like, which will be described later. For example, the terminal device 300 downloads in advance, in accordance with a user's instruction, an application program for executing the information processing according to this embodiment, and stores the application program in the storage unit 330.

[0089] The storage unit 330 also includes, for example, a contract information DB 331. The contract information DB 331 stores contract information relating to contracts concluded by the terminal device 300 (more specifically, by the user of the terminal device 300).

[0090] The contract information may include, for example, at least one of information about the service provided to the user and information about the application that provides the service.

[0091] The information about the service provided to the user may include, for example, information indicating a music distribution service, whether or not there is a charge, etc. The information about the application that provides the service may include, for example, information that identifies the application that provides the music or video distribution service.

[0092] (Input / Output Unit 340) The input / output unit 340 is a user interface for exchanging information with the user. For example, the input / output unit 340 is an operation device such as a keyboard, a mouse, operation keys, or a touch panel that allows the user to perform various operations.

[0093] Alternatively, the input / output unit 340 may be a display device such as a liquid crystal display (LCD) or an organic electroluminescence display (OLED). The input / output unit 340 may be an acoustic device such as a speaker or a buzzer. The input / output unit 340 may also be a lighting device such as an LED (Light Emitting Diode) lamp.

[0094] The input / output unit 340 functions as an input / output means (input means, output means, operation means, or notification means) of the terminal device 300 .

[0095] (Control Unit 350) The control unit 350 is a controller that controls each unit of the terminal device 300. The control unit 350 is realized by a processor such as a CPU or an MPU, for example.

[0096] For example, the control unit 350 is realized by a processor executing various programs stored in a storage device inside the terminal device 300 using a RAM or the like as a work area.

[0097] The control unit 350 may be realized by an integrated circuit such as an ASIC or an FPGA. A CPU, an MPU, an ASIC, and an FPGA can all be considered as a controller.

[0098] The control unit 350 includes an acquisition unit 351, a UI control unit 352, and a notification unit 353. Each block (acquisition unit 351 to notification unit 353) constituting the control unit 350 is a functional block indicating a function of the control unit 350.

[0099] These functional blocks may be software blocks or hardware blocks. For example, each of the functional blocks may be a software module implemented in software (including a microprogram) or a circuit block on a semiconductor chip (die).

[0100] Of course, each functional block may be a single processor or a single integrated circuit. The functional blocks may be configured in any manner. Note that the control unit 350 may be configured with functional units different from the above-described functional blocks.

[0101] (Acquisition unit 351) The acquisition unit 351 acquires, for example, information to be notified to the in-vehicle device 100. For example, the in-vehicle device 100 copies the contract profile 401 of the SIM 400, which has been permitted by the user (or the terminal device 300), to the eSIM 200. The acquisition unit 351 acquires information (hereinafter also referred to as permission information) from the user regarding whether or not to copy the contract profile 401 of the SIM 400 to the in-vehicle device 100.

[0102] More specifically, the acquisition unit 351 requests the UI control unit 352 to inquire of the user whether or not to permit copying of the contract profile 401. The acquisition unit 351 acquires permission information in response to an input result from the user to the input / output unit 340. The acquisition unit 351 acquires the permission information in response to a request from the in-vehicle device 100, for example.

[0103] The acquisition unit 351 outputs the acquired permission information to the notification unit 353 .

[0104] The acquisition unit 351 also acquires information (e.g., profile information related to the contract profile 401) for linking the contract profile 401 to the eSIM 200 of the in-vehicle device 100. The acquisition unit 351 acquires the profile information in response to a request from the in-vehicle device 100, for example.

[0105] The acquisition unit 351 outputs the acquired profile information to the notification unit 353 .

[0106] The acquisition unit 351 also acquires contract information relating to a contract that the user has with at least one of a telecommunications carrier and a service provider, for example, in response to a request from the in-vehicle device 100. The contract information includes, for example, information about communication services and information about distribution services of entertainment content such as music and videos.

[0107] The acquiring unit 351 acquires the contract information from, for example, the contract information DB 331. Alternatively, the acquiring unit 351 may acquire the contract information from the business entity server 700 via the second communication unit 320.

[0108] For example, the acquisition unit 351 may acquire, as the contract information, information on a communication service (communication plan), information on the amount of communication already used, or information on the amount of communication currently available (remaining amount of communication) from the provider server 700. The acquisition unit 351 acquires the contract information using, for example, an API (Application Programming Interface) such as getSubscriptionPlans.

[0109] The acquiring unit 351 may acquire contract information indicating whether or not a contract exists for each application. Alternatively, the acquiring unit 351 may acquire information about applications that have a contract as contract information.

[0110] The acquisition unit 351 notifies the notification unit 353 of the acquired contract information. The acquisition unit 351 may notify the notification unit 353 of all of the acquired contract information, or may notify the notification unit 353 of contract information related to a contract (plan) for which the user has permitted notification to the in-vehicle device 100.

[0111] For example, it is assumed that a user has signed a contract that allows unlimited use of a music distribution app (application) for a fee, and a contract that allows unlimited use of a video distribution app for a fee.

[0112] In this case, for example, the acquisition unit 351 may notify the notification unit 353 of both the contract information related to the music distribution app and the contract information related to the video distribution app. Alternatively, the acquisition unit 351 may notify the notification unit 353 of either the contract information related to the music distribution app or the contract information related to the video distribution app in response to a user instruction. Alternatively, the acquisition unit 351 may not notify the notification unit 353 of both the contract information related to the music distribution app and the contract information related to the video distribution app in response to a user instruction.

[0113] The contract information notified to the notification unit 353 may be notified to the in-vehicle device 100 and may be disclosed to other users. Therefore, by allowing the user to select the contract information to be notified to the in-vehicle device 100, the user can prevent contract information that the user does not want to disclose from being notified to the in-vehicle device 100.

[0114] For example, the acquisition unit 351 requests the UI control unit 352 to present a list of applications included in the acquired contract information to the user. The acquisition unit 351 notifies the notification unit 353 of the contract information related to the application selected by the user.

[0115] Alternatively, the acquisition unit 351 excludes the contract information related to the application selected by the user, in other words, notifies the notification unit 353 of the contract information related to the application not selected by the user.

[0116] Alternatively, the acquisition unit 351 may specify the disclosure range for each application for which a contract exists, and notify the contract information to the notification unit 353. For example, the acquisition unit 351 may include disclosure information that specifies the disclosure range of the application in the contract information.

[0117] For example, the user notifies the in-car device 100 of a playlist, favorites, or the like, or selects the range of disclosure to other users for each application. The acquisition unit 351 notifies the notification unit 353 of the contract information including the range selected by the user (disclosure range).

[0118] As described above, the acquisition unit 351 acquires contract information including, for example, information about a communication plan (communication service) contracted with a telecommunications carrier. The information about the communication plan may include, for example, a plan name (service name) such as "unlimited communication plan A."

[0119] The acquiring unit 351 may also acquire contract information including information about a service plan contracted with a service provider. The information about the service plan may include information about an application that provides the service. The information about the service plan may also include a plan name (service name) such as a "premium plan," user information required for signing in (logging in), such as an account and password, and the like.

[0120] (UI Control Unit 352) The UI control unit 352 generates a screen (UI) and receives operations on the UI. For example, the UI control unit 352 generates a UI image in accordance with an instruction from the acquisition unit 351 and presents the UI image to the user via the input / output unit 340.

[0121] For example, the UI control unit 352 generates an image for inquiring whether or not to permit notification of the contract profile 401 to the in-vehicle device 100 (more specifically, binding to the eSIM 200), and presents the image to the user. Note that, when the terminal device 300 is equipped with a plurality of SIMs 400, the UI control unit 352 may inquire whether or not to permit notification of at least one contract profile 401 of the plurality of SIMs 400.

[0122] Furthermore, the UI control unit 352 generates and presents to the user, for example, an image for selecting applications to be notified (or not notified) to the in-vehicle device 100 from among the applications for which the user has made a contract. Specifically, the UI control unit 352 generates and presents to the user an image including a list of applications for which a service provision contract has been made.

[0123] The UI control unit 352 also receives, for example, permission to copy the contract profile 401 from the user via the input / output unit 340. Alternatively, the UI control unit 352 receives, for example, a selection result of an application to be notified (or not notified) to the in-vehicle device 100 from the user via the input / output unit 340.

[0124] The UI control unit 352 notifies the acquisition unit 351 of the input result from the user, for example.

[0125] (Notification Unit 353 ) The notification unit 353 notifies the in-vehicle device 100 of the information acquired by the acquisition unit 351 via the first communication unit 310 .

[0126] For example, the notification unit 353 notifies the in-vehicle device 100 of permission information indicating whether the user has permitted notification of the contract profile 401 to the in-vehicle device 100 (more specifically, binding to the eSIM 200). Note that if the terminal device 300 is equipped with multiple SIMs 400, the permission information may include information indicating whether copying of the contract profile 401 of at least one of the multiple SIMs 400 is permitted. Furthermore, the notification unit 353 notifies the in-vehicle device 100 of profile information for copying the contract profile 401 to the eSIM 200 of the in-vehicle device 100.

[0127] The notification unit 353 also notifies the in-vehicle device 100 of contract information. The contract information may include, for example, information on a communication plan contracted with a communication carrier and information on a service plan contracted with a service provider.

[0128] 5 is a block diagram showing a configuration example of the in-vehicle device 100 according to the first embodiment of the present disclosure. The in-vehicle device 100 shown in FIG. 5 includes a first communication unit 110, a second communication unit 120, a storage unit 130, an input / output unit 140, and a control unit 150.

[0129] (First communication unit 110) The first communication unit 110 is, for example, a communication interface for directly communicating with the terminal device 300. The first communication unit 110 performs communication in accordance with a communication standard such as Bluetooth or Wi-Fi. The first communication unit 110 is controlled by the control unit 150.

[0130] (Second communication unit 120) The second communication unit 120 is a communication interface for communicating in accordance with a contract profile held by the eSIM 200. The second communication unit 120 communicates in accordance with a communication standard such as cellular communication. The second communication unit 120 is controlled by the control unit 150.

[0131] Although the in-vehicle device 100 is described here as having two communication units (first and second communication units 110 and 120), the number of communication units included in the in-vehicle device 100 is not limited to two. For example, in a case where one communication unit can perform both direct communication and cellular communication with the terminal device 300, such as side link communication, the number of communication units included in the in-vehicle device 100 may be one.

[0132] (Storage Unit 130) The storage unit 130 is a readable / writable storage device such as a DRAM, an SRAM, a flash memory, a hard disk, etc. The storage unit 130 stores, for example, application programs and the like that are used by the in-vehicle device 100 to execute information processing and the like, which will be described later.

[0133] The storage unit 130 also includes, for example, an eSIM storage unit 131 and a contract table 132 .

[0134] The eSIM storage unit 131 holds a plurality of eSIMs 200. In the example of Fig. 5, the eSIM storage unit 131 holds a first eSIM 200A, a second eSIM 200B, and so on.

[0135] The number of eSIMs 200 held in the eSIM storage unit 131 may be plural. For example, the number of eSIMs 200 may be set according to the number of passengers that can ride in the automobile 10 in which the in-vehicle device 100 is installed (the capacity of the automobile 10).

[0136] Here, it is preferable that the eSIM 200 held in the eSIM storage unit 131 is an eSIM for consumers, rather than an eSIM for M2M (Machine to Machine), because it is difficult to perform large-volume communication with an eSIM for M2M.

[0137] In order to provide richer entertainment to multiple users, it is desirable that the in-vehicle device 100 be equipped with, for example, a consumer-oriented eSIM that can perform high-speed and large-capacity communication.

[0138] The storage unit 130 also includes a contract table 132. The contract table 132 is generated based on contract information acquired from the terminal device 300 by the control unit 150, which will be described later.

[0139] Fig. 6 is a diagram illustrating an example of the contract table 132 according to the first embodiment of the present disclosure. The example of Fig. 6 illustrates a case in which the in-vehicle device 100 stores contract profiles of the first to third SIMs 400A to 400C in the first to third eSIMs 200A to 200C.

[0140] Also, here, it is assumed that the first eSIM 200A holds the contract profile of the first SIM 400A, the second eSIM 200B holds the contract profile of the second SIM 400B, and the third eSIM 200C holds the contract profile of the third SIM 400C.

[0141] The contract table 132 holds the services to which the user subscribes (or the applications that provide the services) for each SIM 400 (eSIM 200). For example, the contract table 132 stores the service names and the respective SIMs 400 in association with each other.

[0142] 6, the contract table 132 stores the contents of the communication plan for each SIM 400. For example, the communication plan for the first SIM 400A is a "3G flat rate, subsequent communication restriction plan." This indicates that the contract contents stipulate that the communication amount is a flat rate when the communication amount is 3 GB or less, and that the communication speed, etc. is restricted when the communication amount exceeds 3 GB.

[0143] For example, the communication plan for the second SIM 400B is an "unlimited communication plan." This indicates, for example, that this communication plan has no upper limit (restriction) on communication volume. For example, the communication plan for the third SIM 400C is a "10GB flat rate, pay-as-you-go plan." This indicates, for example, that the contract details a flat rate for communication volume up to 10GB, but limits on communication speed, etc., for communication volume over 10GB.

[0144] For example, it is shown that the third SIM 400C has signed a billing contract for video distribution service A. For example, it is shown that the first and second SIMs 400A and 400B have signed up for paid plans for music distribution service B, and the third SIM 400C has signed up for a free plan.

[0145] For example, the free plan for music distribution service B may be a plan that imposes restrictions on the provision of services, such as requiring viewing of advertisements to receive the service and not allowing playback of some content. The paid plan may be a plan that does not require viewing of advertisements to receive the service and does not impose restrictions on the provision of services. For example, a user may switch from the free plan to the paid plan by paying a fee.

[0146] In this way, the contract table 132 stores the services available for each user (more specifically, for each SIM 400) and details of the services (for example, the service content, etc.).

[0147] 5, the input / output unit 140 is a user interface for exchanging information with a user such as a driver. For example, the input / output unit 140 is an operation device such as a keyboard, a mouse, operation keys, or a touch panel that allows the user to perform various operations.

[0148] Alternatively, the input / output unit 140 may be a display device such as a liquid crystal display or an organic EL display. The input / output unit 140 may be an acoustic device such as a speaker or a buzzer. The input / output unit 140 may also be a lighting device such as an LED lamp.

[0149] The input / output unit 140 functions as an input / output means (input means, output means, operation means, or notification means) of the in-vehicle device 100 .

[0150] The input / output unit 140 may be a car navigation device or an infotainment device installed in the automobile 10. Additionally or alternatively, the input / output unit 140 may be a wireless communication device (e.g., a smartphone or a tablet terminal) owned by the driver and connected to the automobile 10 by wire or wirelessly. In this respect, the input / output unit 140 may be an external device of the in-vehicle device 100.

[0151] (Control Unit 150) The control unit 150 is a controller that controls each unit of the in-vehicle device 100. The control unit 150 is realized by a processor such as a CPU or an MPU, for example.

[0152] For example, the control unit 150 is realized by a processor executing various programs stored in a storage device inside the in-vehicle device 100 using a RAM or the like as a working area.

[0153] The control unit 150 may be realized by an integrated circuit such as an ASIC or an FPGA. A CPU, an MPU, an ASIC, and an FPGA can all be considered as controllers.

[0154] The control unit 150 includes a registration unit 151, a management unit 152, a selection unit 153, and a UI control unit 154. Each block constituting the control unit 150 (the registration unit 151 to the UI control unit 154) is a functional block that indicates a function of the control unit 150.

[0155] These functional blocks may be software blocks or hardware blocks. For example, each of the functional blocks may be a software module implemented in software (including a microprogram) or a circuit block on a semiconductor chip (die).

[0156] Of course, each functional block may be a single processor or a single integrated circuit. The functional blocks may be configured in any manner. Note that the control unit 150 may be configured with functional units different from the above-described functional blocks.

[0157] (Registration Unit 151) The registration unit 151 manages the eSIM 200, for example, by registering a contract profile in the eSIM 200.

[0158] Furthermore, for example, when the in-vehicle device 100 is started, the registration unit 151 sends a push notification to the terminal device 300 to inquire whether or not to permit registration of the contract profile to the eSIM 200. The registration unit 151 transmits a beacon from the first communication unit 110 using, for example, Bluetooth Low Energy (BLE).

[0159] The registration unit 151 acquires permission information from the terminal device 300 via the first communication unit 110. The permission information is information indicating whether or not to permit registration of the contract profile to the eSIM 200. In response to the push notification from the registration unit 151, the terminal device 300 notifies the in-vehicle device 100 of the permission information in accordance with a user instruction.

[0160] The registration unit 151 requests eSIM registration from the terminal device 300 that has granted permission to register the contract profile in the eSIM 200, in accordance with the permission information. For example, the registration unit 151 requests eSIM registration by requesting profile information related to the contract profile from the terminal device 300 via the first communication unit 110.

[0161] When the registration unit 151 acquires profile information from the terminal device 300, it causes the eSIM 200 to hold the contract profile of the terminal device 300. For example, the registration unit 151 acquires the contract profile of the terminal device 300 from a profile management server (not shown) via the terminal device 300 based on the profile information, and registers the contract profile in the eSIM 200. More specifically, for example, the registration unit 151 accesses the profile management server by using tethering communication provided by the terminal device 300. The registration unit 151 registers the contract profile in the eSIM 200 by downloading the contract profile from the profile management server. As a result, the contract profile held in the SIM 400 of the terminal device 300 is copied to the eSIM 200 of the in-vehicle device 100.

[0162] The registration unit 151 notifies the management unit 152 that the registration of the contract profile has been completed.

[0163] Furthermore, when an eSIM 200 to be used in communication by the second communication unit 120 is selected, the registration unit 151 registers the selected eSIM 200 as the main eSIM 200. Furthermore, the registration unit 151 registers an eSIM 200 that is not selected as the sub eSIM 200. The second communication unit 120 performs communication using the main eSIM 200.

[0164] In this way, the registration unit 151 switches the main eSIM 200 used for communication. The registration unit 151 also notifies the UI control unit 154 that the switching of the eSIM 200 has been completed.

[0165] Furthermore, the registration unit 151 deletes the contract profile held by the eSIM 200. For example, the registration unit 151 deletes the contract profile in accordance with an instruction from the user. For example, if the eSIM 200 is not used for a certain period (for example, one day), in other words, if communication using the contract profile held by the eSIM 200 is not performed for a certain period, the registration unit 151 deletes the contract profile held by the eSIM 200.

[0166] At this time, the in-vehicle device 100 may delete the contract table 132 stored in the storage unit 130. Alternatively, the in-vehicle device 100 may delete the contract table 132 in response to a user instruction or after a certain period of time (for example, one day or several hours) has elapsed, without deleting the contract profile.

[0167] Alternatively, the in-vehicle device 100 may delete the contract profile and / or the contract table 132 when the engine of the automobile 10 is turned off or when the power of the in-vehicle device 100 is turned off. The timing of deletion may be set by the user. Note that it is desirable that the contract profile held by the eSIM 200 be deleted after a certain period of time has elapsed, regardless of the user's setting.

[0168] If a certain period of time (for example, one day or several hours) has not elapsed since the eSIM 200 was used, the registration unit 151 may register the contract profile to the eSIM 200 without permission from the user. For example, in this case, the registration unit 151 may request profile information from the terminal device 300 without requesting permission information from the terminal device 300.

[0169] Alternatively, the registration unit 151 may omit the request for profile information and / or contract information if a certain period of time (e.g., one day or several hours) has not elapsed since the eSIM 200 was used. For example, in this case, the registration unit 151 performs communication using a contract profile already held by the eSIM 200. Also, for example, in this case, the in-vehicle device 100 presents a list of applications (described later) and selects a SIM 400 using the contract table 132 already stored in the storage unit 130.

[0170] When some processing, such as requesting permission information, is omitted, the in-vehicle device 100 uses information about the terminal device 300 previously stored to identify that the terminal device 300 used by the user in the automobile 10 is the terminal device 300 that previously obtained permission information.

[0171] Alternatively, the My Number function of the terminal device 300 may be used so that the in-vehicle device 100 can identify that the terminal device 300 used by the user in the automobile 10 is the terminal device 300 that previously obtained permission information.

[0172] Here, the registration unit 151 requests permission information from the terminal device 300 by push notification. That is, the registration unit 151 (the registration unit 151) has been described as acquiring permission information directly from the terminal device 300, but the in-vehicle device 100 may acquire permission information from a source other than the terminal device 300.

[0173] For example, the registration unit 151 may acquire permission information from the user via an external server. For example, the user accesses a site managed by a telecommunications carrier or the like and registers, in advance, permission information in the external server indicating whether or not to permit registration to the eSIM 200. In this case, the registration unit 151 accesses the external server and acquires the permission information.

[0174] Alternatively, the user may, for example, previously register in the terminal device 300 permission information indicating whether or not to permit registration to the eSIM 200. The user may, for example, register the permission information from a setting screen of the terminal device 300. In this case, the registration unit 151 accesses the terminal device 300 and acquires the permission information previously stored in the terminal device 300.

[0175] Alternatively, the registration unit 151 may notify the UI control unit 154 to present a screen requesting the user to acquire the permission information. The registration unit 151 acquires the permission information acquired by the UI control unit 154 from the user via the input / output unit 140. In this manner, the user may directly input the permission information into the in-vehicle device 100.

[0176] (Management Unit 152) The management unit 152, for example, manages information related to the SIM 400. For example, the management unit 152 acquires plan information from the terminal device 300 or the database server 600. For example, the management unit 152 requests the database server 600 to acquire plan information, and receives the plan information from the database server 600 in response.

[0177] The management unit 152 acquires plan information from the database server 600 based on, for example, profile information acquired from the terminal device 300 or information related to the communication plan included in the contract information.

[0178] Alternatively, the management unit 152 may acquire plan information when a predetermined period of time has elapsed while the in-vehicle device 100 is running. In this case, the management unit 152 may acquire plan information related to available communication plans from the database server 600, regardless of the communication plan to which the terminal device 300 has subscribed.

[0179] The management unit 152 may acquire the plan information, for example, via the first communication unit 110, in other words, via the terminal device 300. Alternatively, the management unit 152 may access the database server 600 via the second communication unit 120 using a contract profile held by the eSIM 200.

[0180] Alternatively, if the in-vehicle device 100 has a SIM (not shown) other than the eSIM 200 that holds the contract profile of the terminal device 300, the management unit 152 may access the database server 600 using that SIM.

[0181] The SIM may be a physical SIM (e.g., a SIM card) or an electronic SIM (e.g., an eSIM), and may be for M2M or consumer use.

[0182] The management unit 152 also requests the terminal device 300 to acquire the contract information via the first communication unit 110. The management unit 152 creates a contract table 132 based on the acquired contract information and plan information, and stores the contract table 132 in the storage unit 130.

[0183] The management unit 152 creates the contract table 132 by associating the SIM 400 with the contents of the communication plan, for example, from information about the communication plan included in the contract information and the plan information. The management unit 152 also obtains information about applications (services) linked to the communication plan from the plan information, and stores the information in the contract table 132 in association with the SIM 400.

[0184] For example, if there is an application service (such as a music distribution service) that can be used in conjunction with the communication plan, the management unit 152 can store information about the application service in the contract table 132 .

[0185] In this case, for example, there may be cases where there is no limit on the amount of communication for use of the application service. For example, even if the amount of communication is limited to 2 GB, a communication plan may be set in which the amount of communication performed by the application service does not affect this 2 GB limit.

[0186] In this case, the management unit 152 may store in the contract table 132 information indicating that there is no limit on the communication volume depending on the application, in addition to the limit on the communication volume according to the communication plan.

[0187] Furthermore, the management unit 152 stores in the contract table 132 the available services and the SIM 400 in association with each other based on the information about the services included in the contract information.

[0188] The management unit 152 may store in the contract table 132 services limited to applications that can be executed on the in-vehicle device 100. The management unit 152 extracts services provided by applications that can be executed on the in-vehicle device 100 from the services included in the contract information and the plan information, and stores the extracted services in the contract table 132.

[0189] Alternatively, when requesting the terminal device 300 to notify the contract information, the management unit 152 may request the terminal device 300 to notify the contract information limited to services provided by applications that can be executed on the in-vehicle device 100.

[0190] This allows the terminal device 300 to avoid notifying the in-vehicle device 100 of information relating to application services that cannot be provided by the in-vehicle device 100 .

[0191] When a service is requested using an application that cannot be executed, the in-vehicle device 100 may inquire of the user whether or not to download the application program in order to execute the application.

[0192] The in-vehicle device 100 can provide a service requested by the user by downloading and executing an application program in response to a request from the user.

[0193] Based on the created contract table 132, the management unit 152 instructs the UI control unit 154 to present to the user a list of services that can be provided, in other words, a list of applications that provide the services.

[0194] Furthermore, for example, when the management unit 152 acquires information about an application selected by the user, the management unit 152 refers to the contract table 132 and notifies the selection unit 153 of SIM information about the SIM 400 related to the selected application.

[0195] (Selection Unit 153) The selection unit 153 selects the main eSIM 200 to be used for communication depending on, for example, an application to be executed.

[0196] The selection unit 153, for example, acquires application information related to an application selected by the user from the UI control unit 154. The selection unit 153 requests the management unit 152 to notify SIM information corresponding to the application information. Alternatively, the selection unit 153 may acquire the SIM information by referring to the contract table 132 in the storage unit 130.

[0197] The selection unit 153 selects the main eSIM 200 according to the SIM information. For example, if the service provided by the application selected by the user is video distribution service A, the selection unit 153 selects the third SIM 400C for which a billing contract has been concluded (see FIG. 6 ). The selection unit 153 selects the third eSIM 200C linked to the third SIM 400C as the main eSIM 200.

[0198] In this way, the selection unit 153 selects the main eSIM 200 according to the contract details of the service provided by the application.

[0199] Alternatively, the selection unit 153 may select the main eSIM 200 based on the communication status of the terminal device 300 and the contract details of the communication plan, in addition to the contract details of the service provided by the application.

[0200] For example, if the service provided by the application selected by the user is music distribution service B, the selection unit 153 selects the second SIM 400B, which has no communication restrictions, from the first and second SIMs 400A and 400B of the paid plan (see FIG. 6 ). The selection unit 153 selects the second eSIM 200B linked to the second SIM 400B as the main eSIM 200.

[0201] Alternatively, the selection unit 153 may select the main eSIM 200 according to the remaining communication volume that each SIM can use. For example, the selection unit 153 may not select, as the main eSIM 200, an eSIM 200 that is linked to a SIM 400 whose remaining communication volume is equal to or less than a certain value.

[0202] Alternatively, the selection unit 153 may select the main eSIM 200 in response to a user instruction. For example, the selection unit 153 instructs the UI control unit 154 to associate the contract status of the selected application and details of the communication plan with each SIM 400 and present them to the user.

[0203] The selection unit 153 acquires information about the SIM 400 selected by the user according to the presented contract status, etc. from the UI control unit 154. The selection unit 153 selects the eSIM 200 linked to the SIM 400 selected by the user as the main eSIM 200.

[0204] Alternatively, before selecting an application, the user may set the priority order of the SIMs 400 in advance. The selection unit 153 selects the main eSIM 200 according to, for example, the SIM information and the priority order.

[0205] For example, if the service provided by the application selected by the user is music distribution service B, the selection unit 153 selects the SIM 400 with the highest priority specified by the user from the first and second SIMs 400A and 400B of the paid plan (see Figure 6).

[0206] Alternatively, for example, if the service provided by the application selected by the user is music distribution service B, the selection unit 153 selects the SIM 400 with the highest priority designated by the user from among the first to third SIMs 400A to 400C (see FIG. 6). In this case, the third SIM 400C with the free plan may be selected depending on the priority designated by the user.

[0207] The selection unit 153 notifies the registration unit 151 of information related to the selected main eSIM 200. As a result, the main eSIM 200 is switched to the selected eSIM 200. Thereafter, the second communication unit 120 performs communication based on the contract profile held by the eSIM 200 selected by the selection unit 153.

[0208] (UI control unit 154) The UI control unit 154 generates a screen (UI) and accepts operations on the UI. For example, the UI control unit 154 generates a UI image including a list of applications in accordance with an instruction from the management unit 152 and presents the UI image to the user via the input / output unit 140.

[0209] For example, the UI control unit 154 generates a UI image for setting the priority of the SIM 400 and presents it to the user via the input / output unit 140 .

[0210] Furthermore, the UI control unit 154 receives, for example, a selection of an application to be executed from the user via the input / output unit 140. Alternatively, the UI control unit 154 receives, for example, a priority order for the selection of the SIM 400.

[0211] The UI control unit 154 notifies the selection unit 153, for example, of the input results from the user (application selection results, priority order, etc.).

[0212] Furthermore, the UI control unit 154 executes the application in accordance with the notification from the registration unit 151. Note that the execution of the application may be performed by an application execution unit (not shown). This allows the in-car device 100 to provide the user with services provided by the application (for example, services such as music distribution and video distribution).

[0213] <2-2. Information Processing Example> Hereinafter, an example of information processing executed in the information processing system according to the first embodiment of the present disclosure will be described.

[0214] 7 is a sequence diagram showing an example of the acquisition process according to the first embodiment of the present disclosure. The acquisition process shown in FIG. 7 is executed between the in-vehicle device 100 and the database server 600. The acquisition process may be executed after a software update of the in-vehicle device 100, for example. Alternatively, the plan acquisition process may be executed at a predetermined interval.

[0215] 7, the in-vehicle device 100 requests plan information from the database server 600 (step S101). In response to this request, the database server 600 notifies the plan information (step S102).

[0216] For example, the database server 600 periodically acquires information about communication plans published by carriers and generates plan information. In response to a request from the in-vehicle device 100, the database server 600 notifies the in-vehicle device 100 of the generated plan information.

[0217] <2-2-2. Example of Generation Process> Fig. 8 is a sequence diagram showing an example of the generation process according to the first embodiment of the present disclosure. The generation process shown in Fig. 8 is executed between the in-vehicle device 100 and a plurality of terminal devices 300. The number of terminal devices 300 may be two or more, but the example of Fig. 8 shows a case where the number of terminal devices 300 is three (first to third terminal devices 300A to 300C).

[0218] The generation process is executed when the in-vehicle device 100 is started. The in-vehicle device 100 may be started when the engine of the automobile 10 is started, or may be started in accordance with an instruction from a user such as a driver.

[0219] 8, the in-vehicle device 100 transmits a push notification requesting permission information to the first to third terminal devices 300A to 300C (step S201). The permission information indicates whether the user permits the eSIM 200 to store the contract profile.

[0220] In response to this request, the first to third terminal devices 300A to 300C notify the in-vehicle device 100 of the permission information (step S202). The first to third terminal devices 300A to 300C inquire of the user whether or not to permit the eSIM 200 to store the contract profile. The first to third terminal devices 300A to 300C notify the in-vehicle device 100 of the permission information including the permission content specified by the user.

[0221] It is assumed here that all of the first to third terminal devices 300A to 300C notify the in-vehicle device 100 of permission information permitting the eSIM 200 to store the contract profile.

[0222] The in-vehicle device 100 requests profile information from the terminal device 300 that has notified the permission information permitting the eSIM 200 to store the contract profile (step S203). Here, the in-vehicle device 100 requests profile information from the first to third terminal devices 300A to 300C.

[0223] In response to this request, the first to third terminal devices 300A to 300C notify the in-vehicle device 100 of the profile information (step S204). The profile information may include, for example, information about a contract profile, more specifically, information about a subscriber number such as an IMSI. The profile information may also include access information for the in-vehicle device 100 to access a profile management server (not shown). Examples of the access information include address information about the address of the profile management server and code information about a code for identifying the contract profile.

[0224] The in-vehicle device 100 that has acquired the profile information accesses, for example, a profile management server, and acquires a contract profile linked to the SIM 400. The in-vehicle device 100 stores the acquired contract profile in the eSIM 200.

[0225] Next, the in-vehicle device 100 requests the first to third terminal devices 300A to 300C for contract information (step S205).The first to third terminal devices 300A to 300C acquire the contract information (step S206).

[0226] For example, the first to third terminal devices 300A to 300C acquire the contract information from their own contract information DB 231. Alternatively, the first to third terminal devices 300A to 300C may acquire the contract information from an external server such as the business operator server 700.

[0227] The contract information includes, for example, information about a contract (e.g., a communication plan) regarding communications concluded between a telecommunications carrier and a user, and information about a contract (e.g., a distribution service plan for video distribution, music distribution, etc.) regarding an application service concluded between a service provider and a user.

[0228] The first to third terminal devices 300A to 300C notify the acquired contract information to the in-vehicle device 100 (step S207).

[0229] The on-board device 100 creates the contract table 132 using the acquired contract information (step S208). The on-board device 100 stores the created contract table 132 in the storage unit .

[0230] 2-2-3. Example of Execution Process> Fig. 9 is a flowchart showing an example of the flow of the execution process according to the first embodiment of the present disclosure. The execution process shown in Fig. 9 is executed by, for example, the in-vehicle device 100. The in-vehicle device 100 executes the execution process after executing the generation process, for example. Alternatively, the in-vehicle device 100 may execute the execution process in response to an instruction from a user.

[0231] 9, the in-vehicle device 100 displays a list of applications based on the contract table 132 (step S301). That is, the in-vehicle device 100 presents a list of services that can be provided to the user.

[0232] The in-vehicle device 100 determines whether an application has been selected (step S302). If an application has not been selected (step S302; No), the in-vehicle device 100 returns to step S302 and waits for an application to be selected.

[0233] If an application is selected (step S302; Yes), the in-vehicle device 100 selects a SIM 400 according to the selected application (step S303). For example, the in-vehicle device 100 selects the SIM 400 of a user who has signed a contract to receive the service provided by the application.

[0234] The in-vehicle device 100 switches the main eSIM 200 to the eSIM 200 associated with the selected SIM 400 (step S304). After that, the in-vehicle device 100 executes the application (step S305) and ends the process.

[0235] As described above, the in-vehicle device 100 according to this embodiment acquires the contract profile of the SIM 400 mounted on the terminal device 300 and stores it in the eSIM 200. The in-vehicle device 100 switches the main eSIM 200 to be used for communication depending on, for example, the application being executed.

[0236] This allows the in-vehicle device 100 to acquire entertainment content, etc., using the second communication unit 120. Compared to the terminal device 300, the in-vehicle device 100 has a higher degree of freedom in antenna placement, etc., and can improve communication performance.

[0237] Therefore, by performing communication using the second communication unit 120 instead of tethering, the in-vehicle device 100 can achieve high-speed, high-capacity communication. This allows the in-vehicle device 100 to provide more stable services that require high-speed, high-capacity communication, such as music and video distribution. For example, the in-vehicle device 100 can provide more stable services in applications where real-time performance is important, such as games and streaming.

[0238] Furthermore, it is expected that communication applications for the automobile 10 will expand in the future, such as demand for faster and larger-capacity communication from the in-vehicle device 100. It is also conceivable that the in-vehicle device 100 will be responsible for communication of critical functions in driving, such as V2X (Vehicle to Everything). Even in such cases, the in-vehicle device 100 can perform more appropriate communication by, for example, switching the main eSIM 200 depending on the communication application.

[0239] Furthermore, the in-vehicle device 100 has a larger battery capacity than the terminal device 300, and is less susceptible to the effects of heat generation. Therefore, by performing communication using its own eSIM 200, the in-vehicle device 100 can perform communication without worrying about battery consumption or the effects of heat generation.

[0240] <<3. Second embodiment>> In the first embodiment, the in-vehicle device 100 switches the main eSIM 200 depending on the application (service) selected by the user, but the trigger for the in-vehicle device 100 to switch the eSIM 200 is not limited to this.

[0241] For example, the in-vehicle device 100 may switch the eSIM 200 depending on its own communication status, for example, whether congestion or communication failure is occurring in the communication it is conducting.

[0242] 10 and 11 are diagrams illustrating an example of a switching process according to the second embodiment of the present disclosure. The switching process in Fig. 10 and 11 is executed, for example, in an information processing system that performs communication by switching the eSIM 200 depending on an application.

[0243] 10 and 11 , the in-vehicle device 100 mounted on the automobile 10 registers, in the first eSIM 200A, a contract profile held by the first SIM 400A of the first terminal device 300A. The in-vehicle device 100 also registers, in the second eSIM 200B, a contract profile held by the second SIM 400B of the second terminal device 300B.

[0244] Here, it is assumed that the in-vehicle device 100 selects the first SIM 400A, i.e., performs communication mainly using the first eSIM 200A. In this case, it is assumed that a communication failure occurs in a communication service (hereinafter also referred to as the first communication service) provided by a communication carrier (hereinafter also referred to as the first carrier) that has a contract with a user who owns the first terminal device 300A.

[0245] Due to this communication failure, the first terminal device 300A becomes unable to communicate via the first base station 500A, or the in-vehicle device 100 becomes unable to communicate via the first base station 500A based on the first eSIM 200A.

[0246] In this case, the second terminal device 300B acquires fault information related to a communication fault that has occurred in the first communication service via the second base station 500B (step S11). For example, the second terminal device 300B acquires the fault information from a detection server 800 (not shown). The detection server 800 is a server device that collects information related to communication faults from telecommunications carriers and the like.

[0247] The second terminal device 300B that has acquired the fault information notifies the in-vehicle device 100 of the fault information (step S12). For example, the second terminal device 300B notifies the in-vehicle device 100 of the fault information using direct communication such as Bluetooth or Wi-Fi, in other words, via the first communication unit 310.

[0248] The in-vehicle device 100 that has acquired the fault information switches the main eSIM 200 used for communication from the first eSIM 200A to the second eSIM 200B (step S13). The in-vehicle device 100 communicates via the second base station 500B based on the contract profile held by the second eSIM 200B (step S14).

[0249] This allows the in-vehicle device 100 to continue communication even if a failure occurs in the first communication service.

[0250] Although the number of terminal devices 300 that register SIMs 400 in the in-vehicle device 100 is two here, the number of terminal devices 300 may be three or more. The number of SIMs 400 that can be registered in the in-vehicle device 100, in other words, the number of eSIMs 200, may be determined according to, for example, the passenger capacity of the automobile 10.

[0251] <3-1. Configuration example of information processing system> <3-1-1. Overall configuration example of information processing system> Fig. 12 is a diagram showing an overall configuration example of an information processing system according to a second embodiment of the present disclosure. The information processing system shown in Fig. 12 has the same configuration as the information processing system shown in Fig. 2, except that it includes a detection server 800.

[0252] (Detection Server 800) The detection server 800 is an information processing device that detects the occurrence of a failure in a communication service provided by a telecommunications carrier. The detection server 800 accesses, for example, the carrier server 700 and collects information about communication failures announced by the telecommunications carrier. For example, the detection server 800 can collect information about communication failures from a site that presents information about communication failures.

[0253] Alternatively, the detection server 800 may detect a communication failure by collecting information about the communication status of the terminal device 300. For example, the detection server 800 periodically collects information about the location and communication status of the terminal device 300 from the terminal device 300 that notifies the terminal device 300 of failure information when a communication failure occurs. Based on the collected information, the detection server 800 estimates the area and network (in other words, the telecommunications carrier) where the communication failure is occurring.

[0254] It should be noted that the communication failures detected by the detection server 800 are not limited to failures that are currently occurring. For example, the detection server 800 may be configured to detect information about communication failures that will occur in the future. Information about communication failures that will occur in the future may be provided by, for example, a telecommunications carrier.

[0255] When it is known that a communication failure will occur due to, for example, an equipment update, the communication carrier will publish information about the date, time, and area in which the communication failure will occur. The detection server 800 detects future communication failures by collecting information about communication failures provided by the communication carrier.

[0256] When the detection server 800 detects a communication failure, it notifies the terminal device 300 located in the area where the failure occurred of failure information related to the communication failure. The failure information may include, for example, information about the date and time when the failure occurred, the area, and the telecommunications carrier (communication service). The failure information may also include the date and time when the failure is expected to be resolved.

[0257] The terminal device 300 that has acquired the fault information notifies the fault information to the in-vehicle device 100. Upon receiving the notification, the in-vehicle device 100 determines whether or not to switch the main eSIM 200. The in-vehicle device 100 switches the eSIM 200 according to the determination result.

[0258] The detection server 800 may also detect recovery from a failure. Similar to when a failure occurs, the detection server 800 collects information from the telecommunications carrier and / or from the terminal devices 300 located in the area where the communication failure occurred, regarding whether communication has been restored. If a recovery schedule has been disclosed in advance, the detection server 800 may obtain recovery information from the telecommunications carrier regarding whether the communication failure has been resolved after the scheduled date and time.

[0259] The detection server 800 notifies the in-vehicle device 100 and / or the terminal device 300 of recovery information regarding recovery from the failure. The recovery information may include information regarding the date and time when the failure was recovered, the area, and the telecommunications carrier (communication service).

[0260] The terminal device 300 that has acquired the recovery information notifies the recovery information to the in-vehicle device 100. The in-vehicle device 100 that has received the recovery information determines whether or not to switch the main eSIM 200. The in-vehicle device 100 switches the eSIM 200 according to the determination result.

[0261] 13 is a block diagram showing an example of the configuration of a detection server 800 according to the second embodiment of the present disclosure. The detection server 800 is, for example, a server device (information processing device) that detects failures.

[0262] The detection server 800 shown in Fig. 13 includes a communication unit 810, a storage unit 820, and a control unit 830. The configuration shown in Fig. 13 is a functional configuration, and the hardware configuration may be different from this.

[0263] The functions of the detection server 800 may be statically or dynamically distributed across multiple physically separated components. The detection server 800 may be configured by multiple server devices.

[0264] (Communication Unit 810) The communication unit 810 is a communication interface for communicating with other devices (for example, the business server 700 or the terminal device 300). The communication unit 810 may be a network interface or a device connection interface.

[0265] The communication unit 810 may be a LAN interface such as a NIC, or may be a USB interface configured by a USB host controller or a USB port.

[0266] The communication unit 810 may be a wired interface or a wireless interface. The communication unit 810 is controlled by the control unit 830.

[0267] (Storage Unit 820) The storage unit 820 is a readable and writable storage device such as a DRAM, an SRAM, a flash memory, or a hard disk.

[0268] (Control Unit 830) The control unit 830 is a controller that controls each unit of the detection server 800. The control unit 830 is realized by a processor such as a CPU or an MPU, for example.

[0269] For example, the control unit 830 is realized by a processor executing various programs stored in a storage device inside the detection server 800 using RAM (Random Access Memory) or the like as a working area.

[0270] The control unit 830 may be realized by an integrated circuit such as an ASIC or an FPGA. A CPU, an MPU, an ASIC, and an FPGA can all be considered as controllers.

[0271] The control unit 830 includes a collection unit 831 and a notification unit 832. Each block (collection unit 831 and notification unit 832) constituting the control unit 830 is a functional block that indicates the function of the control unit 830.

[0272] These functional blocks may be software blocks or hardware blocks. For example, each of the functional blocks may be a software module implemented in software (including a microprogram) or a circuit block on a semiconductor chip (die).

[0273] Of course, each functional block may be a single processor or a single integrated circuit. The functional blocks may be configured in any manner. Note that the control unit 830 may be configured with functional units different from the above-described functional blocks.

[0274] (Collection Unit 831) The collection unit 831 collects fault information related to communication faults, for example, from the carrier server 700. The collection unit 831 may collect the fault information from posts on the carrier's website, SNS (Social Network Service), or the like, for example.

[0275] The failure information regarding the communication failure may include, for example, information regarding the date and time when the failure occurred, the area, and the telecommunications carrier (or the communication service). The failure information regarding the communication failure may also include information regarding the likelihood of recovery from the failure.

[0276] The collection unit 831 may estimate the occurrence of a communication failure by collecting location information and information related to the communication status from the terminal devices 300. The collection unit 831 estimates failure information related to the communication failure according to, for example, the number and area of ​​the terminal devices 300 that cannot communicate.

[0277] For example, when the communication status of the terminal device 300 satisfies a predetermined condition, the collection unit 831 may collect fault information related to a communication fault from the provider server 700. The predetermined condition may be, for example, when the number of terminal devices 300 that cannot communicate in a predetermined area and / or within a predetermined period of time exceeds a threshold.

[0278] When the collection unit 831 collects fault information, in other words, when it detects a communication fault, it outputs the fault information to the notification unit 832 .

[0279] The collection unit 831 also collects recovery information related to recovery from a communication failure, for example, from the carrier server 700. The recovery information may include, for example, information related to the date and time when the failure was recovered, the area, and the communication carrier (or communication service).

[0280] The collection unit 831 may estimate recovery from a communication failure by collecting location information and information on communication status from the terminal devices 300. The collection unit 831 estimates recovery information according to, for example, the number and area of ​​the terminal devices 300 that have become able to communicate.

[0281] The collection unit 831 may collect recovery information from the provider server 700, for example, when the communication status of the terminal device 300 satisfies a predetermined condition. An example of the predetermined condition is when the number of terminal devices 300 that have become able to communicate in a predetermined area and / or within a predetermined period of time exceeds a threshold.

[0282] When the collection unit 831 collects recovery information, in other words, when it detects recovery from a communication failure, it outputs the recovery information to the notification unit 832 .

[0283] (Notification unit 832) The notification unit 832 notifies the terminal device 300 of the fault information collected by the collection unit 831. For example, the notification unit 832 may notify the terminal device 300 located in the area where the fault occurred of the fault information. For example, the notification unit 832 may notify the terminal device 300 that is using a communication service other than the communication service in which the fault occurred of the fault information.

[0284] Furthermore, the notification unit 832 can notify the in-vehicle device 100 of the failure information. This allows the detection server 800 to urge the in-vehicle device 100 not to switch to the eSIM 200 that uses the communication service in which the failure has occurred.

[0285] The notification unit 832 notifies the terminal device 300 and the in-vehicle device 100 of the recovery information collected by the collection unit 831. The notification unit 832 may notify the terminal device 300 and the in-vehicle device 100 located in an area where the failure has been recovered of the recovery information.

[0286] The configurations of the in-vehicle device 100, the terminal device 300, and the database server 600 are the same as those in the first embodiment, and therefore description thereof will be omitted.

[0287] <3-2. Information Processing Example> Hereinafter, an example of information processing executed in the information processing system according to the second embodiment of the present disclosure will be described.

[0288] 14 is a sequence diagram showing an example of a notification process according to the second embodiment of the present disclosure. The notification process shown in FIG. 14 is executed among the in-vehicle device 100, the terminal device 300, and the detection server 800. The notification process may be executed, for example, when the detection server 800 detects a communication failure.

[0289] Here, it is assumed that a failure has occurred in communication using a contract profile held by the first SIM 400A of the first terminal device 300A, in other words, a failure has occurred in the first communication service provided by the first telecommunications carrier.

[0290] The detection server 800 that detects a failure in the first communication service notifies the second terminal device 300B of the failure information (step S401).

[0291] The second terminal device 300B notifies the in-vehicle device 100 of the fault information (step S402). For example, the second terminal device 300B notifies the in-vehicle device 100 of the fault information directly. More specifically, the second terminal device 300B notifies the in-vehicle device 100 of the fault information via the first communication unit 310 using Bluetooth, Wi-Fi, or the like.

[0292] The in-vehicle device 100 that has acquired the fault information executes a determination process (step S403).

[0293] 15 is a flowchart showing an example of the flow of the determination process according to the second embodiment of the present disclosure. The determination process shown in Fig. 15 is executed by the in-vehicle device 100. The in-vehicle device 100 executes the determination process of Fig. 15 when, for example, fault information is acquired.

[0294] The in-vehicle device 100 (e.g., the selection unit 153) determines whether or not it is necessary to switch the SIM 400 used for communication (step S501). In other words, the in-vehicle device 100 determines whether or not it is necessary to switch the contract profile used for communication. For example, if a failure occurs in the network (communication service) currently used for communication, the in-vehicle device 100 determines that it is necessary to switch the SIM 400.

[0295] When it is determined that switching of the SIM 400 is not necessary (unnecessary) (step S501; No), the in-vehicle device 100 executes the process of step S507.

[0296] On the other hand, if it is determined that the SIM 400 needs to be switched (step S501; Yes), the in-vehicle device 100 determines whether or not an application needs to be switched (step S502). That is, the in-vehicle device 100 determines whether or not a change in the service provided to the user needs to be made.

[0297] For example, if the SIM 400 (eSIM 200) after switching does not have a contract for the currently provided service, the in-vehicle device 100 determines that the application switching is persistent. In other words, if the in-vehicle device 100 cannot switch to the SIM 400 (eSIM 200) that has a contract for the currently provided service, the in-vehicle device 100 determines that the application switching is necessary.

[0298] If it is determined that application switching is not necessary (unnecessary) (step S502; No), the in-car device 100 executes the process of step S505.

[0299] On the other hand, if it is determined that application switching is necessary (step S502; Yes), the in-vehicle device 100 displays a list of applications (step S503). That is, the in-vehicle device 100 presents a list of services that can be provided to the user.

[0300] The in-vehicle device 100 determines whether an application has been selected (step S504). If an application has not been selected (step S504; No), the in-vehicle device 100 returns to step S503 and waits for an application to be selected.

[0301] If an application is selected (step S504; Yes), the in-vehicle device 100 selects a SIM 400 according to the selected application (step S505). For example, the in-vehicle device 100 selects the SIM 400 of a user who has signed a contract to receive the service provided by the application.

[0302] The in-vehicle device 100 switches the main eSIM 200 to the eSIM 200 associated with the selected SIM 400 (step S506). After that, the in-vehicle device 100 executes the application (step S507) and ends the process.

[0303] Furthermore, in the case of recovery from a failure, for example, the information processing system executes a notification process in which failure information is replaced with recovery information.

[0304] In addition, if the fault information includes scheduled information regarding a future fault, the detection server 800 may notify the terminal device 300 and / or the in-vehicle device 100 of the fault information on the date and time when the fault is scheduled to occur.

[0305] Alternatively, the detection server 800 may notify the terminal device 300 and / or the in-vehicle device 100 of the fault information at the time when the schedule information is acquired or a certain period of time before the date and time when the fault is scheduled to occur.

[0306] In this case, the in-vehicle device 100 may be configured to pre-select a SIM 400 (eSIM 200) that does not use the communication service in which a failure is expected to occur. Alternatively, the in-vehicle device 100 may be configured to execute the determination process at the time when the failure is expected to occur.

[0307] As described above, the in-vehicle device 100 according to this embodiment can continue communication even when a failure occurs in the communication service.

[0308] <<4. Other Embodiments>> The processing according to each of the above-described embodiments may be implemented in various different forms (modifications) other than the above-described embodiments.

[0309] For example, in each of the above embodiments, the in-vehicle device 100 switches the main eSIM 200 depending on the application (service provided by the application) and communication failure, but the criteria by which the in-vehicle device 100 switches the eSIM 200 are not limited to this.

[0310] For example, the in-vehicle device 100 may determine whether to switch SIM 400 (eSIM 200) based on the contract details and the amount of communication already used in communication by each SIM 400, in other words, based on the amount of communication (remaining packet amount) that can be used by each SIM 400.

[0311] Alternatively, the in-vehicle device 100 may determine whether to switch the SIM 400 (eSIM 200) depending on communication conditions such as communication speed, communication quality, delay, etc. For example, when the communication conditions deteriorate to a predetermined level or lower, the in-vehicle device 100 determines whether to switch to another SIM 400 (eSIM 200).

[0312] Alternatively, the in-vehicle device 100 may determine whether to switch the SIM 400 (eSIM 200) depending on the route (or direction of travel) of the automobile 10 and the location of the base station 500. For example, the in-vehicle device 100 switches the SIM 400 (eSIM 200) so as to communicate with a base station 500 located in the direction of travel of the automobile 10. This is because it is believed that the closer the in-vehicle device 100 is to the base station 500, the better the communication conditions of the in-vehicle device 100.

[0313] Furthermore, the in-vehicle device 100 may determine the position and / or timing for switching the SIM 400 (eSIM 200) according to the route of the automobile 10 and the position of the base station 500. For example, the in-vehicle device 100 determines to switch the SIM 400 (eSIM 200) when the automobile 10 moves to a determined position or when a determined timing arrives.

[0314] Alternatively, for example, the in-vehicle device 100 may switch the main eSIM 200 to a predetermined eSIM 200 (SIM 400) when the automobile 10 moves to a determined position or when a determined timing arrives.

[0315] Furthermore, if the number of terminal devices 300 that have permitted registration of SIMs 400 is greater than the number of eSIMs 200 installed in the in-vehicle device 100, the in-vehicle device 100 can select a SIM 400 to be registered in the eSIM 200, for example, in accordance with an instruction from a user. For example, the in-vehicle device 100 presents a list of terminal devices 300 that have permitted registration of SIMs 400 to the user as registration candidates. The in-vehicle device 100 registers (links) the SIM 400 (more specifically, the contract profile held by the SIM 400) installed in the terminal device 300 selected by the user from the registration candidates to the eSIM 200.

[0316] Alternatively, when the number of terminal devices 300 that have permitted registration of SIMs 400 is greater than the number of installed eSIMs 200, the in-vehicle device 100 may select the SIMs 400 to be registered in the eSIMs 200 according to the contract information. For example, the in-vehicle device 100 may select the SIMs 400 to be registered in the eSIMs 200 according to the content of the communication plan of the terminal device 300, the content of the contracted service, etc.

[0317] Alternatively, if the number of terminal devices 300 that have authorized the registration of SIMs 400 is greater than the number of installed eSIMs 200, the in-vehicle device 100 may rewrite the already registered contract profile with another contract profile. The in-vehicle device 100 deletes the registered contract profile and registers a new contract profile. The in-vehicle device 100 rewrites the contract profile as needed (for example, in accordance with an application selected by the user).

[0318] Furthermore, in each of the above embodiments, the in-vehicle device 100 selects the eSIM 200 to be used for communication from among the multiple eSIMs 200, but the SIM selected by the in-vehicle device 100 is not limited to the eSIM 200 installed in the in-vehicle device 100. For example, the in-vehicle device 100 may select the eSIM 200 from the SIM 400 installed in the terminal device 300 in addition to or instead of the eSIM 200 installed in the in-vehicle device 100 itself.

[0319] When the SIM 400 installed in the terminal device 300 is selected as the SIM to be used for communication with the in-vehicle device 100, the in-vehicle device 100 performs communication via the terminal device 300 using direct communication such as tethering.

[0320] In this way, the in-vehicle device 100 can select the SIM to be used for communication from the eSIM 200 installed in the in-vehicle device 100 itself and the SIM 400 installed in the terminal device 300.

[0321] In this case, the in-vehicle device 100 may select a SIM to be used for communication depending on the remaining battery power of the terminal device 300, for example.

[0322] The SIMs 400 used for communication of the in-vehicle device 100 may be limited to, for example, SIMs 400 whose registration to the eSIM 200 has been refused. The in-vehicle device 100 may select a SIM to be used for communication for providing a service from among the SIMs 400 whose registration to the eSIM 200 has been refused.

[0323] In this case, the in-vehicle device 100 may acquire contract information from the terminal device 300 equipped with the SIM 400 that has been rejected for registration to the eSIM 200. Based on the acquired contract information, the in-vehicle device 100 may present to the user a list of services (applications) that can be provided.

[0324] This allows the user to receive services via the in-vehicle device 100 even if the user refuses to register the SIM 400 in the in-vehicle device 100 .

[0325] In addition, in each of the above embodiments, the in-vehicle device 100 presents information such as an application list to the user via its own input / output unit 140, but this information may also be presented to the user via the terminal device 300.

[0326] Alternatively, the terminal device 300 may present the information that is to be presented to the user via its own input / output unit 340 to the user via the in-vehicle device 100 .

[0327] Furthermore, among the processes described in the above embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using known methods. Furthermore, the information, including the processing procedures, specific names, various data, and parameters shown in the above documents and drawings, can be changed as desired unless otherwise specified. For example, the various information shown in each drawing is not limited to the information shown in the drawings.

[0328] Furthermore, the components of each device shown in the figure are conceptual functional components and do not necessarily have to be physically configured as shown in the figure. In other words, the specific form of distribution and integration of each device is not limited to that shown in the figure, and all or part of them can be functionally or physically distributed and integrated in any unit depending on various loads, usage conditions, etc.

[0329] <<5. Hardware Configuration>> An information processing device (information equipment) including the in-vehicle device 100, the terminal device 300, the database server 600, the detection server 800, etc. according to each of the above-described embodiments is realized by a computer 1000 having a configuration as shown in FIG. 16, for example.

[0330] 16 is a hardware configuration diagram showing an example of a computer 1000 that realizes the functions of an information processing device. The following description will be given taking the in-vehicle device 100 according to an embodiment as an example. The computer 1000 includes a CPU 1100, a RAM 1200, a ROM (Read Only Memory) 1300, a HDD (Hard Disk Drive) 1400, a communication interface 1500, and an input / output interface 1600. The components of the computer 1000 are connected via a bus 1050.

[0331] The CPU 1100 operates and controls each component based on programs stored in the ROM 1300 or the HDD 1400. For example, the CPU 1100 loads the programs stored in the ROM 1300 or the HDD 1400 into the RAM 1200 and executes processing corresponding to the various programs.

[0332] The ROM 1300 stores boot programs such as a Basic Input Output System (BIOS) that is executed by the CPU 1100 when the computer 1000 is started, and programs that depend on the hardware of the computer 1000 .

[0333] HDD 1400 is a computer-readable recording medium that non-temporarily records programs executed by CPU 1100 and data used by such programs. Specifically, HDD 1400 is a recording medium that records an image generation program according to the present disclosure, which is an example of program data 1450.

[0334] The communication interface 1500 is an interface for connecting the computer 1000 to an external network 1550 (e.g., the Internet). For example, the CPU 1100 receives data from other devices and transmits data generated by the CPU 1100 to other devices via the communication interface 1500.

[0335] The input / output interface 1600 is an interface for connecting the input / output device 1650 and the computer 1000. For example, the CPU 1100 receives data from an input device such as a keyboard or a mouse via the input / output interface 1600. The CPU 1100 also transmits data to an output device such as a display, a speaker, or a printer via the input / output interface 1600. The input / output interface 1600 may also function as a media interface for reading programs and the like recorded on a predetermined recording medium. Examples of media include optical recording media such as a DVD (Digital Versatile Disc) or a PD (Phase Change Rewritable Disc), magneto-optical recording media such as an MO (Magneto-Optical Disk), tape media, magnetic recording media, and semiconductor memories.

[0336] For example, when the computer 1000 functions as the in-vehicle device 100 according to the embodiment, the CPU 1100 of the computer 1000 executes an information processing program loaded onto the RAM 1200 to realize the functions of the control unit 150, etc. The information processing program according to the present disclosure and data in the storage unit 130 are stored in the HDD 1400. The CPU 1100 reads and executes the program data from the HDD 1400, but as another example, the CPU 1100 may obtain these programs from another device via the communication interface 1500.

[0337] <<6. Conclusion>> The effects described in this disclosure are merely examples and are not limited to the disclosed content. Other effects may also be obtained.

[0338] Although the embodiments of the present disclosure have been described above, the technical scope of the present disclosure is not limited to the above-described embodiments, and various modifications are possible within the scope of the gist of the present disclosure. Furthermore, components of different embodiments and modifications may be combined as appropriate.

[0339] The present technology may also be configured as follows. (1) An information processing device comprising: a control unit that acquires contract profiles held in subscriber identification media mounted on a plurality of terminal devices, holds each of the plurality of contract profiles in a different electronic subscriber identification medium, and selects the electronic subscriber identification medium to be used for communication; and a communication unit that performs the communication according to the contract profile held in the electronic subscriber identification medium. (2) The information processing device according to (1), in which the control unit stores the contract profile of the terminal device in the electronic subscriber identification medium when the terminal device permits the contract profile to be stored in the electronic subscriber identification medium. (3) The information processing device according to (2), in which the control unit, upon startup of the information processing device, inquires of the terminal device whether or not to permit the contract profile to be stored in the electronic subscriber identification medium. (4) The information processing device according to any one of (1) to (3), in which the control unit acquires the contract profile via the terminal device. (5) The information processing device according to any one of (1) to (4), in which the control unit selects the electronic subscriber identification medium to be used for communication according to an application to be executed. (6) The information processing device according to any one of (1) to (5), wherein the control unit acquires contract information related to the contract profile, and selects the electronic subscriber identity medium to be used for the communication according to the contract information. (7) The information processing device according to (6), wherein the control unit selects the electronic subscriber identity medium to be used for the communication according to a communication status of the terminal device related to the contract information. (8) The information processing device according to (7), wherein the control unit selects the electronic subscriber identity medium to be used for the communication according to the amount of data available for the communication using the contract profile. (9) The information processing device according to any one of (1) to (8), wherein the control unit selects the electronic subscriber identity medium according to the communication status of the communication unit. (10) The information processing device according to (9), wherein the control unit selects the electronic subscriber identity medium for the communication using a network in which no communication failure occurs.(11) The information processing device according to (10), wherein the control unit acquires information related to the communication status from the terminal device. (12) The information processing device according to any one of (1) to (11), wherein the control unit selects the electronic subscriber identification medium to be used for the communication in accordance with an instruction from the terminal device. (13) The information processing device according to any one of (1) to (12), wherein the control unit deletes the contract profile from the electronic subscriber identification medium after a predetermined period has elapsed since the contract profile was stored in the electronic subscriber identification medium. (14) The information processing device according to any one of (1) to (13), wherein the control unit stores at least one of contract information related to the contract profile and information related to an application to be executed, in association with the electronic subscriber identification medium. (15) The information processing device according to any one of (1) to (14), wherein the information processing device is mounted in a vehicle, and the control unit acquires the contract profile of the terminal device used by a user in the vehicle. (16) An information processing method comprising: acquiring a contract profile held by a subscriber identification medium mounted on each of a plurality of terminal devices, holding each of the plurality of contract profiles in a different electronic subscriber identification medium, selecting the electronic subscriber identification medium to be used for communication, and performing the communication in accordance with the contract profile held by the electronic subscriber identification medium. (17) An information processing system comprising: a plurality of terminal devices mounted with subscriber identification media and performing communication in accordance with the contract profiles held by the subscriber identification media, and an information processing device including: a control unit that acquires the contract profiles held by the subscriber identification media mounted on each of the plurality of terminal devices, holds each of the plurality of contract profiles in a different electronic subscriber identification medium, and selects the electronic subscriber identification medium to be used for communication, and a communication unit that performs the communication in accordance with the contract profile held by the electronic subscriber identification medium.(18) An information processing program that causes a computer to execute the following processes: acquire contract profiles held by subscriber identification media mounted on each of a plurality of terminal devices, hold each of the plurality of contract profiles in a different electronic subscriber identification medium, select the electronic subscriber identification medium to be used for communication, and perform the communication in accordance with the contract profile held by the electronic subscriber identification medium. (19) A computer-readable storage medium that stores a program that causes a computer to execute the following processes: acquire contract profiles held by subscriber identification media mounted on each of a plurality of terminal devices, hold each of the plurality of contract profiles in a different electronic subscriber identification medium, select the electronic subscriber identification medium to be used for communication, and perform the communication in accordance with the contract profile held by the electronic subscriber identification medium. (20) A terminal device comprising: a first communication unit that communicates in accordance with a contract profile held in a subscriber identification medium mounted on the device itself; a second communication unit that communicates directly with an information processing device; and a control unit that notifies the information processing device of the contract profile held in the subscriber identification medium via the second communication unit, wherein the information processing device holds each of the acquired multiple contract profiles in a different electronic subscriber identification medium, selects the electronic subscriber identification medium to be used for communication, and performs the communication in accordance with the contract profile held in the electronic subscriber identification medium. (21) An information processing program that causes a computer to execute processing to communicate in accordance with the contract profile held in a subscriber identification medium mounted on the device itself, communicate directly with an information processing device, and notify the information processing device of the contract profile held in the subscriber identification medium by the direct communication, wherein the information processing device holds each of the acquired multiple contract profiles in a different electronic subscriber identification medium, selects the electronic subscriber identification medium to be used for communication, and performs the communication in accordance with the contract profile held in the electronic subscriber identification medium.(22) A computer-readable storage medium storing a program that causes a computer to execute a process of communicating according to a contract profile held in a subscriber identification medium installed in the computer, communicating directly with an information processing device, and notifying the information processing device of the contract profile held in the subscriber identification medium via the direct communication, wherein the information processing device holds each of the acquired multiple contract profiles in a different electronic subscriber identification medium, selects the electronic subscriber identification medium to be used for communication, and performs the communication according to the contract profile held in the electronic subscriber identification medium.

[0340] REFERENCE SIGNS LIST 100 In-vehicle device 110, 310 First communication unit 120, 320 Second communication unit 130, 330, 620, 820 Storage unit 140, 340 Input / output unit 150, 350, 630, 830 Control unit 200 eSIM 331 Contract information DB 300 Terminal device 400 SIM 500 Base station 600 Database server 610, 810 Communication unit 700 Operator server 800 Detection server

Claims

1. An information processing device comprising: a control unit that acquires contract profiles held by subscriber identification media installed in each of a plurality of terminal devices, holds each of the plurality of contract profiles in a different electronic subscriber identification medium, and selects the electronic subscriber identification medium to be used for communication; and a communication unit that performs the communication in accordance with the contract profiles held by the electronic subscriber identification media.

2. An information processing device according to claim 1, wherein the control unit stores the contract profile of the terminal device in the electronic subscriber identification medium when the control unit permits the terminal device to store the contract profile in the electronic subscriber identification medium.

3. The information processing device according to claim 2, wherein said control unit, when the device is started, inquires of said terminal device whether or not to permit said contract profile to be stored in said electronic subscriber identification medium.

4. The information processing device according to claim 1, wherein the control unit acquires the contract profile via the terminal device.

5. The information processing device according to claim 1, wherein said control unit selects said electronic subscriber identity medium to be used for said communication depending on an application to be executed.

6. The information processing device according to claim 1, wherein the control unit acquires contract information related to the contract profile, and selects the electronic subscriber identity medium to be used for the communication according to the contract information.

7. The information processing device according to claim 6, wherein said control unit selects said electronic subscriber identity medium to be used for said communication in accordance with the communication status of said terminal device related to said contract information.

8. The information processing device according to claim 7, wherein said control unit selects said electronic subscriber identity medium to be used for said communication in accordance with the amount of data available for said communication using said contract profile.

9. The information processing device according to claim 1, wherein said control unit selects said electronic subscriber identity medium according to the communication status of said communication unit.

10. The information processing device according to claim 9, wherein said control unit selects said electronic subscriber identity medium for carrying out said communication using a network in which no communication failure occurs.

11. The information processing device according to claim 9, wherein the control unit acquires information relating to the communication status from the terminal device.

12. The information processing device according to claim 1, wherein said control unit selects said electronic subscriber identity medium to be used for said communication in accordance with an instruction from said terminal device.

13. The information processing device according to claim 1, wherein said control unit deletes said contract profile from said electronic subscriber identification medium after a predetermined period of time has elapsed since said contract profile was held in said electronic subscriber identification medium.

14. The information processing device according to claim 1, wherein said control unit stores at least one of contract information related to said contract profile and information related to an application to be executed, in association with said electronic subscriber identification medium.

15. The information processing device according to claim 1, wherein the information processing device is mounted on a vehicle, and the control unit acquires the contract profile of the terminal device used by a user riding in the vehicle.

16. An information processing method comprising: acquiring contract profiles held in subscriber identification media respectively mounted on a plurality of terminal devices; holding each of the plurality of contract profiles in a different electronic subscriber identification medium; selecting the electronic subscriber identification medium to be used for communication; and conducting the communication in accordance with the contract profile held in the electronic subscriber identification medium.

17. An information processing system comprising: a plurality of terminal devices each equipped with a subscriber identification medium and performing communication in accordance with a contract profile held by the subscriber identification medium; an information processing device including: a control unit that acquires the contract profile held by the subscriber identification medium each equipped in the plurality of terminal devices, holds each of the plurality of contract profiles in a different electronic subscriber identification medium, and selects the electronic subscriber identification medium to be used for communication; and a communication unit that performs the communication in accordance with the contract profile held by the electronic subscriber identification medium.

Images