ACCESS TO INFOTAINMENT SYSTEM USING NON-LINKED DEVICES

Abstract

Methods for providing content through a server system (112), comprising: Receiving a notification of a linking of an in-vehicle infotainment system (IVI system) (104) with a first device (108) according to a wireless communication protocol; Receiving a control input from a second device (110), wherein the control input is an instruction to reproduce content; in response to the tax return-- Retrieving the content that corresponds to the tax input; and Transferring the content to the first device (108) with an instruction to the first device (108) to cause the IVI system (104) to reproduce the content; wherein the first device (108) has a first mobile client application (118) installed on it, which is authenticated with the server system (112) for a first user account, wherein the method further comprises: Identifying a second user account linked to the first user account in an account database by the server system (112), wherein the second device (110) runs a second mobile client application (118) that is authenticated with the server system (112) for the second user account; and Notifying the second device (110) about the linking of the IVI system (104) with the first device (108) by the server system (112) in response to the determination that the second user account is linked to the first user account in the account database.

Description

AREA OF INVENTION

[0001] This invention relates to access functions of a mobile application using an in-vehicle infotainment system (IVI system). GENERAL STATE OF THE ART

[0002] Modern vehicles incorporate sophisticated infotainment systems, typically featuring a large touchscreen that displays advanced interfaces and content. The functionality of an IVI system is often extended to allow interaction with applications running on a mobile device. By connecting to a device, applications on the mobile device can be controlled via the IVI system, and content (audio, video, etc.) can be played back through the IVI system. Examples of this type of system include Ford's AppLink, Apple's CarPlay, and Google's Android Auto.

[0003] A system that allows a passenger to transmit instructions to a first device belonging to the driver of a vehicle via a second device—for example, a smartphone—is known from US patent 2015 / 0373479A1. This first device is connected to the vehicle's infotainment system and controls the display of content on the infotainment screen. The transmitted instructions can cause the display on the infotainment screen to change accordingly.

[0004] A system that enables communication between a vehicle, in particular a vehicle infotainment system, and a mobile device is described, among other places, in US 2016 / 0157286 A1. A method for controlling this communication is described in DE 102016125711 A1.

[0005] Document US 2016 / 0088052A1 describes a method for establishing a Bluetooth connection between a smartphone and a Bluetooth device, such as a vehicle's infotainment system. A "Service Discovery Protocol," known, among other sources, from Bhagwat, Pravin: Bluetooth: Technology for short-range wireless apps. In: IEEE Internet Computing, Vol. 5, 2001, No. 3, pp. 96-103. - ISSN 1089-7801, is used to determine the services supported by the Bluetooth device before establishing a connection, ensuring that the smartphone only connects to supported services. The distribution of media content based on one or more permissions within a network system is known from document US 2015 / 0201023A1.

[0006] The systems and methods disclosed herein provide an improved approach for extending the functionality of an IVI system using mobile devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] To readily understand the advantages of the invention, a more detailed description of the invention briefly described above is provided by reference to specific embodiments illustrated in the attached drawings. It is understood that these drawings represent only typical embodiments of the invention and are therefore not to be considered as limiting its scope. The invention is described and explained with additional accuracy and detail by the accompanying drawings, which: Fig. 1 a schematic block diagram of an environment into which the systems and methods according to an embodiment of the present invention are to be set up; Fig. 2 is a schematic block diagram of an exemplary computing device suitable for setting up methods according to the embodiments of the invention; Fig. 3 is a process flow diagram illustrating a procedure for registering applications of a mobile device with an IVI system; the Fig. 4A and Fig. 4B are a process flow diagram illustrating a method for accessing an IVI system using a non-linked device according to an embodiment of the present invention; and the Fig. 5A and Fig. 5B schematic diagrams of an alternative method for accessing an IVI system using a non-linked device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0008] With reference to Fig. 1. An environment 100 in which the procedures described herein can be set up may include a vehicle 102 in which an in-vehicle infotainment system (IVI system) 104 is housed. The IVI system 104 may have some or all of the features of a general-purpose computing device. The infotainment system 104 may include a screen 106, which may be a touchscreen.

[0009] As is known in the field, the IVI system 104 can be coupled to speakers or other audio outputs and programmed to provide an interface for selecting audio content to be played back using the speakers or other audio outputs. Audio content can be selected from one or more audio sources coupled to the IVI system 104, such as a radio, compact disc (CD) player, and the like. The IVI system 104 can also display video content on the screen 106 or on one or more other screens arranged within the vehicle 102. The IVI system 104 can display video content selected from one or more video sources, such as a DVD player, a linked mobile device, or other video data sources.

[0010] The infotainment system 104 can also be coupled to one or more systems of the vehicle 102 itself and enable the display of status information for the vehicle 102 and the receipt of inputs that modify the operation of one or more systems of the vehicle 102 itself, such as an air conditioning system, engine operating parameters and the like.

[0011] A vehicle 102 typically carries a driver and one or more passengers. The driver and the one or more passengers can operate two or more mobile devices 108, 110 in the embodiments disclosed herein. For the purposes of this disclosure, the mobile device 108 is connected to the IVI system 104, for example by BLUETOOTH, Universal Serial Bus (USB), or another wired or wireless connection, whereas the mobile device 110 is not connected to the IVI system 104. To clearly and unambiguously explain the different roles of the devices 108, 110, the mobile device 108 is referred to as the driver device 108, and the mobile device 110 is referred to as the passenger device 110.Nevertheless, in some cases the linked mobile device 110 may belong to a passenger and the linked device 108 may belong to another passenger or the driver without changing the functionality described herein.

[0012] The mobile devices 108 and 110 can interact with an application server 112. Specifically, an application server 112 can interact with applications running on the mobile devices 108 and 110. For example, the application server 112 could be an audio content provider, such as Spotify, Pandora, or similar services. The application server 112 could also be a video content provider, such as YouTube, Netflix, or similar services. The application server 112 could also be a navigation content provider, such as Waze or Google Maps.

[0013] The mobile devices 108, 110 can interact with the application server 112 via a cellular communication antenna 114 over a wireless connection. The cellular communication antenna 114 can be connected to the application server 112 via a network 116, which includes one or more wired or wireless connections. The network 116 can be a local area network (LAN), a wide area network (WAN), the internet, or any other type of network.

[0014] The mobile devices 108, 110 execute an application 118, which is programmed to interact with the server system 112, which includes the components 120-126 shown. The application 118 may, for example, include an IVI integration module 120. The IVI integration module 120 is programmed to transmit content to the IVI 104 for display on the screen 106 and / or for playback via the speakers. The IVI integration module 120 may also be programmed to receive and process interactions from the IVI 104 to control the operation of the application 118.

[0015] The application 118 can further include a bridge client 122 and a bridge target 124. The bridge client 122 establishes the functionality by enabling the application 118 to control an IVI system 104 linked to another device. For example, the passenger device 110 can access the IVI 104 via the driver device 108 using the bridge client 122 as described below. The bridge target 124 establishes the functionality by enabling the application running on a linked device to facilitate control of the IVI system 104 by a non-linked device. In the example of Fig. 1. The driver device 108 uses the functionality of the bridge target 124. The operation of the bridge client 122 and the bridge target 124 can be explained in relation to the explanation below. Fig. 4A to 5B should be understood.

[0016] The application 118 can also perform application services and user interface (UI) functions 126. These can include any application functions known in the field, including displaying user interface elements on a screen, receiving input to user interface elements, processing the input according to the programmed functionality, retrieving content from the application server 112, displaying the content, providing data to the application server 112, and any other application functionality known in the field.

[0017] The IVI integration module 120 can couple outputs generated by the application services and the user interface 126 to the screen 106 and provide inputs to the IVI system 104 for the application services and the UI 126. Inputs received by the IVI system 104 can be processed in the same way as corresponding inputs provided by the devices 108 and 110 running the application 118. Similarly, content provided to the IVI system for display on the screen 106 can be generated in the same way as content displayed on the screen of the device running the application 118 or 110.

[0018] Fig. Figure 2 is a block diagram representing an example computing device 200. The computing device 200 can be used to perform various procedures, such as those described herein. The IVI system 104, the mobile devices 108 and 110, and the application server 112 may have some or all of the features of the computing device 200.

[0019] The computing device 200 includes one or more processors 202, one or more storage devices 204, one or more interfaces 206, one or more mass storage devices 208, one or more input / output (I / O) devices 210, and a display device 230, all of which are connected to a bus 212. The processor(s) 202 includes one or more processors or control units that execute instructions stored in the storage device(s) 204 and / or the mass storage device(s) 208. The processor(s) 202 may also include various types of computer-readable media, such as a cache memory.

[0020] The storage device(s) 204 includes / include various computer-readable media, such as volatile memory (e.g., random-access memory (RAM) 214) and / or non-volatile memory (e.g., read-only memory (ROM) 216). The storage device(s) 204 may also include a rewritable ROM, such as flash memory.

[0021] The mass storage device(s) 208 includes / include various computer-readable media, such as magnetic tapes, magnetic disks, optical disks, solid-state storage (e.g., flash memory), and so on. As in Fig. As shown in Figure 2, a special mass storage device is a hard disk drive 224. Various drives may also be included in the mass storage device(s) 208 to enable reading from and / or writing to the various computer-readable media. The mass storage device(s) 208 includes removable media 226 and / or non-removable media.

[0022] The I / O device(s) 210 includes various devices that enable data and / or other information to be entered into or retrieved from the computing device 200. An example of an I / O device 210 includes cursor control devices, keyboards, keypads, microphones, monitors or other display devices, loudspeakers, printers, network interface cards, modems, lenses, CCDs or other image acquisition devices, and the like.

[0023] The display device 230 includes any type of device capable of displaying information to one or more users of the computing device 200. Examples of a display device 230 include a monitor, a display terminal, a video projection device, and the like.

[0024] The interface(s) 206 includes / include various interfaces that enable the computing device 200 to interact with other systems, devices, or computing environments. An example of an interface 206 includes / includes any number of different network interfaces 220, such as interfaces to local area networks (LANs), wide area networks (WANs), wireless networks, and the Internet. Another interface includes / includes a user interface 218 and a peripheral device interface 222. The interface 206 may also include one or more peripheral interfaces, such as interfaces for printers, pointing devices (mice, touchpads, etc.), keyboards, and the like.

[0025] Bus 212 enables the processor(s) 202, the storage device(s) 204, the interface(s) 206, the mass storage device(s) 208, the I / O device(s) 210, and the display device 230 to communicate with each other and with other devices or components connected to bus 212. Bus 212 represents one or more different types of bus structures, such as a system bus, PCI bus, IEEE 1394 bus, USB bus, and so on.

[0026] For illustrative purposes, programs and other executable program components are represented herein as discrete blocks, although it is understood that such programs and components may reside at different times in different memory components of the computing device 200 and may be executed by the processor(s) 202. Alternatively, the systems and procedures described herein may be implemented in hardware or a combination of hardware, software, and / or firmware. For example, one or more application-specific integrated circuits (ASICs) may be programmed to execute one or more of the systems and procedures described herein.

[0027] With reference to Fig. 3. The illustrated procedure 300 can be executed within the environment 100 to provide access to the IVI system 104 by applications 118 running on a driver device 108 and furthermore to inform the application server 112 about the linking of the driver device 108 with the IVI system 104.

[0028] Method 300 can involve linking 302 the driver device 108 with the IVI system 104. This can include linking the devices according to a BLUETOOTH protocol, connecting the driver device 108 to the IVI system 104 by means of a cable, such as a Universal Serial Bus (USB) cable, or any other linking method known in the field.

[0029] In response to the linking, the driver device 108 connects to the IVI system 104 and registers one or more applications with the IVI system 104 via the connection. For example, the driver device 108 can send a data packet or file containing a list of applications installed on the driver device 108 that include an IVI integration module 120, enabling shared control and content playback with the IVI system 104. The data packet or file can also contain graphical symbols for displaying an interface of the IVI system 104 and can include data defining interface elements to be played back on the IVI system 104 for invoking the functionality of the applications.

[0030] The IVI system 104 receives the data sent in step 304 and registers these applications in step 306 in association with the driver device 108. The IVI system 104 can, for example, store a record containing the list of applications and other data sent by the driver device 108. If an application loses connection to an IVI system 104, the application can notify the application server 112, which then deletes the record.

[0031] The IVI system 104 can display available applications on screen 106 308. For example, in response to a user input requesting the display of available mobile applications, a list of the applications registered at step 306 can be displayed in the form of an arrangement of icons, with each icon corresponding to one of the applications.

[0032] In some embodiments, the IVI system 104 can further transmit a list of registered applications 310, for example via a protocol such as BLUETOOTH LOW ENERGY (BLE) or another wireless protocol. In some embodiments, step 310 is performed periodically while the driver device 108 is actually connected to the IVI system 104, or it is transmitted once or several times in response to the establishment of a connection with the driver device 108.

[0033] Some or all of the applications registered in step 304 can notify a corresponding application server 112 of the registration 312. For example, if a Spotify application is registered in step 304, the Spotify application installed on the driver device 108 can notify the application server 112 of the registration. In some embodiments, the notification step 312 is performed by the bridge target 124 of an application 118 that was registered in step 304. After notification 312, the application can then be operated as a target for the passenger device 110 according to the methods disclosed herein.

[0034] After receiving the notification sent in step 312, application server 112 records the availability of a target on 314. Specifically, the application transmitting notification 312 can be authenticated with respect to a user account; that is, a specific user account is logged into application server 112 using the application instance. Accordingly, the notification from step 312 can reference this user account by including a username and / or authentication information, which may be encrypted for security reasons. After receiving notification 312, application server 112 can then store a reference to link it to the IVI system 104 in this user account.

[0035] With reference to the Fig. 4A and Fig. 4B The illustrated method 400 can be used to provide access to an IVI system 104 using a passenger device 110 by linking the driver device 108 to the IVI system 104.

[0036] Procedure 400 can involve the passenger device 110 requesting a list of possible destinations via a 402 request. The 402 request can be invoked in response to a user navigating to an interface element that offers a list of destinations in an application 118 running on the passenger device 110 (“the passenger application”). Step 402 can be executed by the application 118’s bridge client 122. As shown, the 402 request can be sent to the application server 112 corresponding to that passenger application. The 402 request can refer to the account for which the passenger application is authenticated (“the passenger account”), in the form of a username or other credentials.

[0037] In response to receiving the request from step 402, the application server can identify 112 connected users by identifying one or more other user accounts listed as friends or connections in the passenger account (404).

[0038] The application server 112 can then identify among these connected users 406 whether any targets are assigned to them, i.e., whether a link to an IVI system 104 has been recorded in the accounts of these connected users 314. In some embodiments, targets are connected users for whom a link to an IVI system 104 has been recorded and who are currently connected to that IVI system 104. In such embodiments, applications 118 can report to the application server 112 both the linking to the IVI system and the establishment and termination of connections to the IVI system 104.

[0039] When any destinations are identified (406), the application server (408) reports this to the passenger application (112). The passenger application (410) receives this message and displays it to a user as a graphically represented list of available destinations on a screen of the passenger device (110). The list can include, for each destination, an identifier of the connected users in whose accounts the destination was identified (406).

[0040] The user of the passenger device 110 can then select a destination (“the selected destination”) from the list, for example by tapping a representation of the destination on a screen of the passenger device 110. In the illustrated example, the selected destination represents the linking of the driver device 108 with the IVI system 104, which is recorded in the account (“the driver account”) for which the application 118, running on the driver device 108 (“the driver application”), is authenticated.

[0041] The passenger application receives this selection (412) and transmits a reference to the selected destination to the application server (112), for example, using the bridge client (122). The application server (112) receives the destination selection (414) and requests authorization (416) to allow the passenger application to access the IVI system (104). This may involve transmitting an authorization request to the driver device (108). The driver device (108) can then receive this request (418) and forward the request to the IVI system (104), which displays the authorization request on the screen (106) (420).The reproduced 420 request might, for example, contain a message “Allow access to [application] for [username] [Yes] [No]”, where “username” is the username associated with the passenger account, “application” is the name of the driver and passenger applications, “Yes” is a user interface element that will be understood as authorization if selected, and “No” is a user interface element that will be understood as a refusal of authorization if selected.

[0042] When authorization is received (422), it is transmitted to the driver device (108), which receives the authorization and forwards it to the application server (112) (424). The application server (112) receives the authorization (426).

[0043] With reference to Fig. 4B After receiving 426 the authorization, the application server 112 can notify 428 the passenger application that the authorization has been received. After receiving the authorization, the passenger application can display a notification on the passenger device 110 that the control of the IVI system 104 has been authorized. The passenger application can then receive control inputs 430 and transmit them to the application server 432. The application server receives 434 the user inputs and identifies the content based on the inputs. An input can be, for example, a selection of a media file (audio, video, image, text), an input of a destination address, or another instruction that will trigger the display of content. The application server 112 then transmits 436 this content to the driver device 108. The transmission 436 of the content can include transmitting an instruction to play the content on the IVI system 104.The driver device 108 receives the content and calls for playback of the content on the IVI system 438. After receiving this instruction, the IVI system 104 plays back the content. If the content is an audio file, for example, the IVI system 104 calls for playback of the audio file using the speakers connected to the IVI system 104. If the content is an image or video file, the IVI system 440 can play back the content by displaying it on the screen 106. If the control input is a specification of a destination address, the content can be directions to the destination address. Accordingly, the driver device 108 can call for a display of street-by-street directions to the destination address or call for the generation of street-by-street directions by a navigation module housed in the IVI system 104.

[0044] Various modifications of procedure 400 from the Fig. 4A and Fig. 4B can be performed. In addition to initiating the playback of content by the IVI system 104, the control inputs can, for example, include inputs that control the operation of the IVI system 104, such as adjusting the volume, calling up navigation functions, setting vehicle control parameters (e.g., climate control functions), or the like.

[0045] In another alternative, instead of granting control of the IVI system 104 in connection with the passenger account, the passenger device 110 can be granted access to control the IVI system 104 in connection with the driver account. In such embodiments, step 428 can involve both notifying the passenger of the authorization and transferring an interface to the driver account, i.e., an interface with content and functionality defined more according to the preferences and usage of the driver account than the passenger account. In such embodiments, control inputs 430 are also processed by the application server 112 in connection with the driver account at step 436.

[0046] The Fig. 5A and Fig. Figure 5B illustrates an alternative method 500 for controlling an IVI system using a non-linked device. Method 500 may be preceded by the execution of method 300 with respect to the driver device 108.

[0047] Procedure 500 can involve the passenger device 110 searching 502 for BLE destinations transmitted by an IVI system 104 within the passenger device 110's range. As explained above, after registering applications 306 from a linked device, the IVI system 104 can transmit a list of available applications 310. Accordingly, at step 502, the passenger device 110 can monitor such transmissions.

[0048] After receiving such a transmission, the passenger application can display a representation of the connection between the driver application and the IVI system on the passenger device 110, for example by inserting it as an element in a graphically displayed list of available destinations on a screen of the passenger device 110.

[0049] The user of the passenger device 110 can then select a destination (“the selected destination”) from the list 504, e.g. by tapping a representation of the destination on a screen of the passenger device 110.

[0050] In response to receiving the destination selection (504), the passenger device (110) can transmit a request to the IVI system (104) for access to the selected destination application using the IVI system (506). The bridge client (122) of the selected destination application (“the passenger application”) can, for example, transmit a username and password, preferably encrypted, to the IVI system for the user account for which the passenger application is authenticated (“the passenger account”). The passenger application can transmit other credentials sufficient to authenticate an application with the application server (112) with respect to the passenger account.

[0051] After receiving the request and login information (508), the IVI system 104 requests authorization for the passenger device 110 to access the IVI system 104 using the passenger application (510). This authorization can then be granted (512) or denied. Steps 510 and 512 can be performed in the same manner as steps 420 and 422 of procedure 400.

[0052] With reference to Fig. 5B The authorization notification, if an authorization was received at step 512, can then be transmitted to the driver device 108 together with the credentials received at step 508 514. The driver application receives the authorization and the credentials and forwards them to the application server 112 516.

[0053] The application server 112 checks the login credentials in step 518; that is, it verifies, using any authentication technique known in the field, that the login credentials correspond to the passenger account. If, in step 518, it is determined that the login credentials for the passenger account are correct, the application server 112 then transmits, in step 520, to the passenger device the authorization to control the playback of content on the IVI system 104.

[0054] The passenger application, i.e., the bridge client 122, receives this authorization 522 and can generate an output on the screen of the passenger device 110, notifying the user that access to the IVI system 104 has been granted. The passenger application can then receive control inputs 524 and transmit the control inputs to the application server 112 526. The application server 112 receives the control inputs 528 and, in response, identifies content according to the control inputs related to the passenger account and transmits the content 530 to the driver device 108. The transmission 530 of the content can include transmitting an instruction to the driver device 108 to play the content on the IVI system 104. The driver application receives the content and calls a playback of the content on the IVI system 104 532.As explained above with reference to procedure 400, the control inputs can be a selection of a media file (audio, video, or image), so that the content that is transmitted (530) and played back (534) is the media file. As also explained above, a control input can be a specification of a destination address, and the transmitted (530) and played back (534) content can include street-by-street directions to the destination address.

[0055] Various modifications of procedure 500 from the Fig. 5A and Fig. 5B can be performed. In addition to initiating the playback of content by the IVI system 104, the control inputs can include, for example, inputs that control the operation of the IVI system 104, such as adjusting the volume, calling up navigation functions, setting vehicle control parameters (e.g., climate control functions), or the like.

[0056] In another alternative, instead of granting control of the IVI system 104 in connection with the passenger account, the passenger device 110 can be granted access to control the IVI system 104 in connection with the driver account. In such embodiments, the step of checking the credentials 518 can also be omitted, since the driver application will already be authenticated with the application server. Similarly, instead of transmitting credentials 506 in step 506, only a username can be sent and processed instead of the credentials. In such embodiments, step 520 can be both the notification of the passenger about the authorization and the transmission of an interface to the driver account, i.e.,an interface that includes content and functionality defined more according to the preferences and usage of the driver account than the passenger account. In such embodiments, control inputs received at step 528 are also processed by the application server 112 in connection with the driver account at step 530. Reference was made in the preceding disclosure to the accompanying drawings, which form part thereof and in which specific implementations are shown for illustrative purposes in which the disclosure can be carried out. It is understood that other implementations may be used and structural changes may be made without deviating from the scope of the present disclosure. References in the patent specification to “an embodiment”, “an exemplary embodiment”, etc.They state that the described embodiment may include a specific function, structure, or property; however, not every embodiment necessarily includes this specific function, structure, or property. Furthermore, such statements do not necessarily refer to the same embodiment. It is also argued that if a specific function, structure, or property is described in connection with one embodiment, it is within the knowledge of a person skilled in the art to expect such a function, structure, or property to be present in other embodiments, regardless of whether this is explicitly stated or not.

[0057] Implementations of the systems, devices, and methods disclosed herein may include or utilize a specialized or general-purpose computer, which includes computer hardware, such as, as discussed herein, one or more processors and system memory. Implementations within the scope of this disclosure may also include data carriers and other computer-readable media for transmitting or storing computer-executable instructions and / or data structures. Such computer-readable media may be any available media accessible by a general-purpose or specialized computer system. Computer-readable media on which computer-executable instructions are stored are computer storage media (devices). Computer-readable media that transmit computer-executable instructions are transmission media.Therefore, implementations of the disclosure may, for example, and without limitation, include at least two distinctly different types of computer-readable media: computer storage media (devices) and transmission media. Computer storage media (devices) include RAM, ROM, EEPROM, CD-ROM, solid-state drives (“SSDs”) (e.g., based on RAM), flash memory, phase-change memory (“PCM”), other types of memory, other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired program code resources in the form of computer-executable instructions or data structures and that can be accessed by a general-purpose or specialized computer.

[0058] An implementation of the devices, systems, and methods disclosed herein can communicate via a computer network. A "network" is defined as one or more data connections that enable the transmission of electronic data between computer systems and / or modules and / or other electronic devices. When information is provided to or transmitted to a computer via a network or other communication link (either wired, wireless, or a combination of wired and wireless), the computer accordingly indicates the link as a transmission medium. Transmission media can include a network and / or data links that can be used to transmit the desired program code resources in the form of computer-executable instructions or data structures and that can be accessed by a general-purpose or specialized computer.Combinations of the above should also be included in the scope of computer-readable media.

[0059] Computer-executable instructions include, for example, instructions and data that, when executed on a processor, cause a general-purpose computer, specialized computer, or specialized processing device to perform a specific function or group of functions. The computer-executable instructions can be, for example, binary files, intermediate format instructions such as assembly language, or even source code. Although the subject matter has been described in language specific to structural features and / or methodological actions, it is understood that the subject matter defined in the appended claims is not necessarily limited to the features or actions described above. Rather, the described features and actions are disclosed as exemplary forms of implementation of the claims.

[0060] The person skilled in the art can understand that the disclosure can be carried out in network computing environments with many types of computer system configurations, including dashboard vehicle computers, PCs, desktop computers, laptops, message processors, handheld devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, mobile phones, PDAs, tablets, pagers, routers, switches, various storage devices, and the like.

[0061] This disclosure can also be performed in distributed systems environments where both local and remote computer systems connected by a network (either by wired data links, wireless data links, or a combination of both) perform tasks. In a distributed systems environment, program modules can reside in both local and remote storage devices.

[0062] Furthermore, the functions described herein may be performed in one or more of the following: hardware, software, firmware, digital components, or analog components. For example, one or more application-specific integrated circuits (ASICs) may be programmed to execute one or more of the systems and methods described herein. Certain terms are used in the description and claims with respect to specific system components. As a person skilled in the art can understand, components may be referred to by the use of different designations. This document does not distinguish between components that differ in name but not in function.

[0063] It should be noted that the sensor embodiments discussed above may include computer hardware, software, firmware, or any combination thereof to perform at least some of the functions. For example, a sensor may include computer code configured to run on one or more processors and may include a hardware logic / electrical circuit controlled by the computer code. These examples of devices are provided herein for illustrative purposes and are not intended to be limiting. Embodiments of the present disclosure may be implemented in other types of devices, as may be known to a person qualified in the relevant field(s). At least some embodiments of the disclosure have been incorporated into computer program products that include such logic (e.g.,in the form of software) that is stored on any computer-usable medium. When executed in one or more data processing devices, such software causes a device to operate as described herein.

[0064] A computer program code for executing operations of the present invention can be written in any combination of one or more programming languages, including an object-oriented programming language such as Java, Smalltalk, C++, or the like, and conventional procedural programming languages ​​such as the "C" programming language or similar programming languages. The program code can be executed entirely on a computer system as a standalone software package, on a standalone hardware unit, partially on a remote computer located some distance from the computer, or entirely on a remote computer or server.In the latter case, the remote computer can be connected to the computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made with an external computer (for example, via the Internet using an Internet service provider).

[0065] The present invention is described above with reference to flowchart illustrations and / or block diagrams of methods, devices (systems), and computer program products according to the embodiments of the invention. It is understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be configured by computer program instructions or computer program code.These computer program instructions may be provided to a processor of a general-purpose computer, a special-purpose computer, or any other programmable data-processing device for the manufacture of a machine, such that the instructions executed by the processor of the computer or other programmable data-processing device provide means for establishing the functions / actions specified in the block or blocks of the flowchart and / or block diagram.

[0066] These computer program instructions may also be stored in a non-volatile, computer-readable medium that causes a computer or other programmable, data-processing device to function in a particular manner such that the instructions stored in the computer-readable medium produce a manufactured item, including instructional means that establish the function / action specified in the block or blocks of the flowchart and / or block diagram.

[0067] The computer program instructions can also be programmed onto a computer or other programmable data processing device to cause a series of process steps to be carried out on the computer or other programmable device to establish a computer-setup procedure such that the instructions executed on the computer or other programmable device provide procedures for setting up the functions / actions specified in the block or blocks of the flowchart and / or block diagram.

[0068] While various embodiments of the present disclosure have been described above, it is understood that these serve only as examples and not as limitations. It will be apparent to persons qualified in the relevant field that various changes in form and detail can be made without departing from the spirit and scope of the disclosure. Therefore, the breadth and scope of the present disclosure are not intended to be limited by any of the embodiments described above, but are intended to be defined only according to the following claims and their equivalents. The preceding description has been set forth for illustrative and descriptive purposes. It is not to be considered exhaustive and is not intended to limit the disclosure to the specific form disclosed. Many modifications and variations are possible in light of the teachings stated above.Furthermore, it should be noted that any or all of the aforementioned alternative implementations can be used in any desired combination to form additional hybrid implementations of the revelation.

Claims

[1] Methods for providing content by a server system (112), comprising: Receiving a notification of a linking of an in-vehicle infotainment system (IVI system) (104) with a first device (108) according to a wireless communication protocol; Receiving a control input from a second device (110), wherein the control input is an instruction to reproduce content; in response to the tax return-- Retrieving the content that corresponds to the tax input; and Transferring the content to the first device (108) with an instruction to the first device (108) to cause the IVI system (104) to reproduce the content; wherein the first device (108) has a first mobile client application (118) installed on it, which is authenticated with the server system (112) for a first user account, wherein the method further comprises: Identifying a second user account linked to the first user account in an account database by the server system (112), wherein the second device (110) runs a second mobile client application (118) that is authenticated with the server system (112) for the second user account; and Notifying the second device (110) about the linking of the IVI system (104) with the first device (108) by the server system (112) in response to the determination that the second user account is linked to the first user account in the account database. [2] The method of claim 1, further comprising: Receiving an initial request from the second mobile client to access the IVI system (104) via the first mobile client, by the server system (112); The server system (112) transmits a second authorization request to the first device (108) in response to the first request; and Receiving an authorization message from the first device (108) by the server system (112); wherein the transmission of the instruction to the first device (108) is only carried out in response to the receipt of the authorization message from the first device (108). [3] Methods for providing content by a server system (112), comprising: Receiving a notification of a linking of an in-vehicle infotainment system (IVI system) (104) with a first device (108) according to a wireless communication protocol; Receiving a control input from a second device (110), wherein the control input is an instruction to reproduce content; in response to the tax return-- Retrieving the content that corresponds to the tax input; and Transferring the content to the first device (108) with an instruction to the first device (108) to cause the IVI system (104) to reproduce the content; Receiving login information, which was forwarded by the first device (108) from the second device (110), from the first device (108) through the server system (112); and Verification of login information by the server system (112); and wherein the transmission of the instruction to the first device (108) to cause the IVI system (104) to reproduce the content is only permitted after the first device (108) has received the registration information and the registration information has been checked. [4] Method according to claim 3, wherein the first device (108) has a first mobile application (118) installed thereon, which is authenticated with the server system (112) for a first user account; and wherein the login information includes login information for a second user account, wherein the second device (110) houses a second mobile application (118) which is authenticated for the second user account. [5] Methods for providing content by a server system (112), comprising: Receiving a notification of a linking of an in-vehicle infotainment system (IVI system) (104) with a first device (108) according to a wireless communication protocol; Receiving a control input from a second device (110), wherein the control input is an instruction to reproduce content; in response to the tax return-- Retrieving the content that corresponds to the tax input; and Transferring the content to the first device (108) with an instruction to the first device (108) to cause the IVI system (104) to reproduce the content; wherein the first device (108) has a first mobile client application (118) installed on it, which is authenticated with the server system (112) for a first user account; wherein the second device (110) has a second mobile client application (118) installed on it, which is authenticated with the server system (112) for a second user account; the method further includes the processing of the input for selecting the content from the second device (110) in connection with the second user account by the server system (112). [6] Methods for providing content by a server system (112), comprising: Receiving a notification of a linking of an in-vehicle infotainment system (IVI system) (104) with a first device (108) according to a wireless communication protocol; Receiving a control input from a second device (110), wherein the control input is an instruction to reproduce content; in response to the tax return-- Retrieving the content that corresponds to the tax input; and Transferring the content to the first device (108) with an instruction to the first device (108) to cause the IVI system (104) to play back the content; wherein the first device (108) has a first mobile client application (118) installed on it, which is authenticated with the server system (112) for a first user account; wherein the second device (110) has a second mobile client application (118) installed on it, which is authenticated with the server system (112) for a second user account; the method further includes the processing of the input for selecting the content from the second device (110) in connection with the first user account by the server system (112). [7] Method according to claim 6, further comprising: Creating an interface by the server system (112) according to data assigned to the first user account; and Transfer of the interface to the second device (110) by the server system (112); where the control input involves an interaction with the interface. [8] Method according to claim 1, wherein the content is at least one of audio content, video content and navigation information. [9] System comprising one or more processing devices (202) and one or more non-volatile storage devices (204) coupled to the one or more processing devices (202), wherein the one or more storage devices (204) store executable code effective inducing the one or more processing devices (202) to: to connect to a first device (108); to receive from the first device (108) an instruction, an authorization for a second device (110) to control content provided to the system by a mobile application (118) installed on the first device (108); to receive an input; if the input indicates granting authorization, to send a response to the first device (108) indicating granting authorization; to receive content from the first device (108) in response to control inputs received on the second device (110); and to reproduce the content on an output device (106) that is coupled to the system; wherein the executable code is further effective in causing the one or more processors (202) to do the following: to receive from the first device (108) a list of available applications (118) with corresponding interfaces provided by the system; to transmit the list of available applications (118) via a wireless protocol; to receive from the second device (110) a first message that refers to an application (118) from the list of applications (118) and includes authentication information; and In response to receiving the first message, a second message will be sent to the first device (108), referring to the application (118) from the list of applications (118), and containing the authentication information. [10] System according to claim 9, wherein the executable code further enables the one or more processing devices (202) to connect to the first device (108) via at least one BLUETOOTH protocol and a Universal Serial Bus (USB) cable. [11] System according to claim 9, wherein the wireless protocol is a BLUETOOTH LOW ENERGY (BLE). [12] System according to claim 9, wherein the executable code further enables the one or more processors (202) to reproduce the content on the output device (106) coupled to the system by outputting at least one of an audio content, a video content and navigation information.

Images