Systems and methods for telephone transmissions used for assurance and review

Abstract

This disclosure provides a "system and method for telephone transmission with warranty and censorship". Systems and methods for filtering and rejecting unwanted telephone calls are provided. A user can specify a list of telephone numbers to be pre-authorized. A call from any of these numbers will automatically connect to the user's device. If an incoming call is not from any of these pre-authorized telephone numbers, the user's device can send information about obtaining a warranty to the calling device before the call is connected. If the caller has purchased the warranty, the user's device verifies this and allows the call to connect to the user's device. If the warranty has not been purchased, the call is rejected. In other cases, the user can specify that calls originating from certain geographic areas or areas near one or more pre-authorized vehicles are allowed, even if the incoming telephone number is not part of the pre-authorized list of telephone numbers.

Description

Technical Field

[0001] This disclosure relates to the field of telephone communications. Specifically, embodiments of this disclosure relate to methods and systems for telephone communications used for warranty and review. Background Technology

[0002] Unwanted and robocalls have become a pervasive nuisance, causing inconvenience, frustration, and other problems. These calls range from automated telemarketing to more malicious attempts such as phishing scams and fraud schemes. The problem has grown exponentially due to technological advancements that allow robocallers to easily generate large numbers of calls using automated dialing systems and scam phone numbers. This not only wastes time but can also have serious consequences, especially when these calls are received while driving. For drivers, answering or reacting to these calls while on the road can lead to reduced awareness of their surroundings.

[0003] While some solutions exist to reduce the number of these calls received by users, a more robust way to eliminate such calls is needed. Summary of the Invention

[0004] This disclosure describes systems and methods for eliminating unwanted telephone calls. Specifically, embodiments of this disclosure relate to systems and methods for reducing or eliminating unwanted and / or unsolicited telephone calls by requiring the caller to purchase monetary collateral in order to connect to the relevant party.

[0005] Embodiments of this disclosure provide a method. This includes a first device receiving a first telephone call from a second device. The method further includes the first device determining that a telephone number associated with the second device is not part of a pre-authorized list of telephone numbers. The method then includes the first device sending a first message to the second device including information about purchasing a warranty to continue the first telephone call and subsequently receiving a second message indicating that the warranty has been purchased. The method finally includes the first device accepting the first telephone call based on the purchase of the warranty.

[0006] In another embodiment, a method is provided, the method comprising: receiving a first telephone call from a second device by a first device; and determining by the first device that a telephone number associated with the second device is not part of a pre-authorized list of telephone numbers. The method further comprises determining by the first device whether the current location of the second device is within a predetermined geographic area, wherein the predetermined geographic area is associated with a user of the first device. Thereafter, the method comprises determining by the first device whether the current location of the second device is close to the current location of one or more pre-authorized vehicles, wherein the one or more authorized vehicles are associated with a user of the first device; and if the current location of the second device is within the predetermined geographic area, or if the current location of the second device is close to the current location of one or more pre-authorized vehicles, then allowing the first telephone call to continue by the first device.

[0007] In yet another embodiment, a vehicle is provided that may include: an automotive computer including a communication interface configured to communicate via a mobile phone network; and a memory device coupled to the vehicle control unit and storing instructions that, when executed by the controller, cause the automotive computer to perform one or more operations. The instructions may cause the automotive computer to receive a first telephone call from a first device; determine that a telephone number associated with the first device is not part of a pre-authorized list of telephone numbers; place the first telephone call on hold; send a first message to the first device instructing a user of the first device to purchase a warranty; receive a second message indicating that the user of the first device has purchased the warranty; and allow the first telephone call to continue based on the purchase of the warranty.

[0008] These and other advantages of this disclosure are provided in detail herein. Attached Figure Description

[0009] Specific embodiments are illustrated with reference to the accompanying drawings. The same reference numerals may be used to indicate similar or identical items. Various embodiments may utilize elements and / or components other than those shown in the drawings, and some elements and / or components may not be present in various embodiments. Elements and / or components in the drawings are not necessarily drawn to scale. Throughout this disclosure, singular and plural terms may be used interchangeably depending on the context.

[0010] Figure 1 An environment in which embodiments of the present disclosure may be implemented is shown.

[0011] Figure 2 A block diagram of a vehicle according to an embodiment of the present disclosure is shown.

[0012] Figure 3 This is a flowchart of a process for screening telephone calls according to an embodiment of the present disclosure.

[0013] Figure 4 This is a flowchart of a process for adding a number to a blocked number list according to an embodiment of the present invention.

[0014] Figure 5 A flowchart of a process according to another embodiment of the present invention is shown.

[0015] Figure 6 This is a flowchart of a process according to yet another embodiment of the present disclosure.

[0016] Figure 7 A block diagram of a server according to an embodiment of the present disclosure is shown. Detailed Implementation

[0017] The present disclosure will now be described more fully with reference to the accompanying drawings, which illustrate exemplary embodiments of the disclosure and are not intended to be limiting.

[0018] Figure 1 An environment 100 in which embodiments of the present disclosure may be implemented is shown. Vehicle 102 may be any passenger or commercial vehicle, such as a car, truck, tanker, bus, etc. Environment 100 may also include a control server 104. Control server 104 may be part of a cloud-based computing infrastructure and may be associated with and / or include a Telematics Service Delivery Network (SDN) that provides digital data services to vehicle 102. In embodiments, server 104 may be associated with a guarantor entity. Guarantor entity may be a company or financial institution that provides a guarantee on behalf of an individual or business. A guarantee acts as a financial security instrument, ensuring that a specific obligation, contract, or liability will be fulfilled. If an individual or business fails to fulfill its obligations, the guarantor compensates the injured party up to the guaranteed amount and then seeks recourse from the guaranteed party. References are made below. Figure 1 Provide details of control server 104.

[0019] Environment 100 may also include a user device 112. User device 112 may be a mobile phone, tablet, personal computer, smart key fob, etc. User device 112 may be associated with a user 110 of vehicle 102. User 110 may be the driver of vehicle 102 or a passenger in vehicle 102. User device 112 may receive information from vehicle 102 and / or control server 104. User device 112 may have a dedicated application installed thereon, which can interface with vehicle 102 to download and display various types of vehicle-generated information and other control data. In one embodiment, vehicle 102 may communicate directly with user device 112 to send and receive data without network 108 and / or server 104. Environment 100 may include a second device 114. Second device 114 may be similar to user device 112. In embodiments, both user device and second device 114 may be able to make and receive telephone calls and / or text messages via several different methods. In other embodiments, user device 112 may be integrated into vehicle 102, such that second device 114 can be used to make telephone calls that user 110 can accept using the interface / components of vehicle 102. In some embodiments, second device 114 may include any system or device capable of making calls. For example, second device 114 may include any combination of cellular phone, internet device (IP phone), computer, landline phone directed to cellular or satellite phone, etc.

[0020] Environment 100 may also include network 108. Network 108 illustrates an example communication infrastructure in which connected devices discussed in various embodiments of this disclosure may communicate. Network 108 may be and / or include the Internet, a private network, a public network, or other configurations operating using any one or more known communication protocols such as Transmission Control Protocol / Internet Protocol (TCP / IP), Bluetooth, etc. ® Bluetooth ® Low Energy (BLE), Wi-Fi based on the IEEE 802.11 standard, Ultra Wideband (UWB), and cellular technologies such as Time Division Multiple Access (TDMA), Code Division Multiple Access (CDMA), High Speed ​​Packet Access (HSPDA), Long Term Evolution (LTE), Global System for Mobile Communications (GSM), and 5G are just a few examples.

[0021] Vehicle 102 may include multiple units, including but not limited to an automotive computer, a vehicle control unit (VCU), and a detection unit. See below for reference. Figure 2 Details of vehicle 102 are provided.

[0022] Figure 2A block diagram of a vehicle 102 in which embodiments of the present disclosure may be implemented is shown. The vehicle 102 may include multiple units, including but not limited to an automotive computer 208, a vehicle control unit (VCU) 210, and an infotainment unit 238. The VCU 210 may include multiple electronic control units (ECUs) 214 communicating with the automotive computer 208. In embodiments, the automotive computer 208 may include hardware that can be used for communication via a mobile network. Such hardware may include a cellular radio module, a subscriber identity module (SIM), an RF transceiver, a GPS module, and an application processor. The automotive computer 208 may also include software such as baseband firmware, a radio interface layer, protocol stack software, a SIM toolkit, a dialer and messaging applications, network configuration and security software, etc.

[0023] In some embodiments, a user device such as a mobile phone, laptop computer, smart key fob, etc., can be configured to connect to the vehicle computer 208. The user device can communicate via one or more wireless connections, and / or via near field communication (NFC) protocol, Bluetooth, etc. ® Protocols, Wi-Fi, Ultra-Wideband (UWB), and other possible data connectivity and sharing technologies can be used to directly connect to vehicle 102.

[0024] According to this disclosure, the vehicle computer 208 can be installed anywhere in the vehicle 102. The vehicle computer 208 may be or include an electronic vehicle controller having one or more processors 202, one or more memory devices 204, and one or more transceivers 206.

[0025] Processor 202 may be configured to communicate with one or more memory devices (e.g., memory 204 and / or memory) of a corresponding computing system. Figure 2The processor 202 may communicate with one or more external databases (not shown in the diagram). The processor 202 may utilize the memory 204 to store programs and / or data in code form to perform operations according to this disclosure. The memory 204 may be a non-transitory computer-readable storage medium or memory storing vehicle control program code. The memory 204 may include any or a combination of volatile memory elements (e.g., dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), etc.) and may include any one or more non-volatile memory elements (e.g., erasable programmable read-only memory (EPROM), flash memory, electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), etc.). In some embodiments, the memory 204 may include modules 245 that can implement various embodiments of this disclosure. Modules 245 may include instructions that can be executed by the processor 202 to implement various embodiments of this disclosure.

[0026] The vehicle computer 208 may also include a transceiver 206. The transceiver 206 may be configured to receive information / input from one or more external devices or systems (e.g., user device 208, external server, etc.). Furthermore, the transceiver 206 may transmit notifications, requests, signals, etc., to external devices or systems. Additionally, the transceiver 206 may be configured to receive information / input from vehicle components (such as vehicle sensing system 232, one or more ECUs 214, etc.). Furthermore, the transceiver 206 may transmit signals (e.g., command signals) or notifications to vehicle components such as BCM 220, infotainment system 238, etc.

[0027] In some embodiments, VCU 210 may share a power and / or communication bus with vehicle computer 208 and may be configured and / or programmed to coordinate data between vehicle systems, connected servers, etc. VCU 210 may include or communicate with any combination of ECUs 214, such as BCM 220, Engine Control Module (ECM) 222, Transmission Control Module (TCM) 224, Telematics Control Unit (TCU) 226, Driver Assist Technology (DAT) Controller 228, etc. VCU 210 may also include and / or communicate with a Vehicle Sensing System (VPS) 230, which may connect to and / or control one or more vehicle sensing systems 232. The vehicle sensing system 232 may include one or more vehicle sensors, including but not limited to radio detection and ranging (RADAR or "radar") sensors configured to use radio waves to detect and locate objects inside and outside the vehicle 102, seating area latch sensors, seating area sensors, light detection and ranging ("LiDAR") sensors, door sensors, proximity sensors, temperature sensors, wheel sensors, one or more ambient weather or temperature sensors, interior and exterior cameras, steering wheel sensors, etc. Sensors as part of the vehicle sensing system 232 may be coupled to the vehicle 102 at one or more locations in one or more configurations. For example, various sensors of the vehicle sensing system 232 may be integrated into various subsystems of the vehicle 102 (such as doors, mirrors, roof, etc.) or attached to the vehicle 102 using suitable mounting mechanisms. In some embodiments, various sensors of the vehicle sensing system 232 may be located at the front, rear, sides, top, bottom, and underside of the vehicle 102. The location of the sensors may depend on their function. For example, sensors monitoring the area beneath the vehicle can be attached to the underside of vehicle 102, while sensors monitoring areas on either side of vehicle 102 can be mounted or integrated into the doors of vehicle 102. Vehicle sensing system 232 may also include one or more road noise sensors, such as accelerometers coupled to various mechanical components and / or systems of vehicle 102. Those skilled in the art will recognize that sensors can be coupled to the vehicle in various different ways and locations besides those mentioned above.

[0028] In some embodiments, VCU 210 can control vehicle operation aspects and implement one or more instruction sets received from server 104, user device 112, or from one or more instruction sets stored in memory 204.

[0029] TCU 226 can be configured and / or programmed to provide vehicle connectivity to wireless computing systems on and outside the vehicle 102, and may include a navigation (NAV) receiver 234 for receiving and processing GPS signals, BLE ® Module (BLEM) 236, Wi-Fi transceiver, UWB transceiver and / or may be configured to be used in vehicle 102 with other systems (e.g., vehicle key fob). Figure 2 Other wireless transceivers (not shown in the image), external servers, user devices, etc., for wireless communication (including cellular communication) between computers and modules. Figure 2 (Not shown in the image). TCU 226 can communicate with ECU 214 via a wired or wireless bus. In some respects, TCU 226 can be configured to determine the real-time vehicle geolocation, for example, via NAV receiver 234.

[0030] ECU 214 can control various aspects of vehicle operation and communication using inputs from the human driver, inputs from the vehicle computer 208, and / or wireless signal inputs received from other connected devices (such as server 206) via a wireless connection.

[0031] The BCM 220 typically integrates sensors, vehicle performance indicators, and variable reactors associated with vehicle systems. It may also include processor-based power distribution circuitry that controls functions associated with the vehicle body, such as lights, windows, safety devices, cameras, audio systems, wipers, door locks and entry controls, and various comfort controls. The BCM 220 can also operate as a gateway for bus and network interfaces to communicate with remote ECUs ( Figure 2 Interaction (not shown in the image).

[0032] The DAT controller 228 and / or the autonomous driving system 240 can provide Level 1 to Level 5 automated driving and driver assistance functionality, which may include, in particular, features such as active parking assist, vehicle reversing assist, and / or adaptive cruise control, as well as other features. The DAT controller 228 can also provide various aspects of user and environmental inputs that can be used for user authentication.

[0033] In some embodiments, the vehicle computer 208 may be connected to the infotainment system 238 (or vehicle human-machine interface (HMI)). The infotainment system 238 may include a touchscreen interface portion and voice recognition features, enabling it to identify the user's biometrics based on facial recognition, voice recognition, fingerprint recognition, or other biometric methods. In other aspects, the infotainment system 238 may also be configured to receive user commands via the touchscreen interface portion and / or output or display notifications, navigation maps, etc., on the touchscreen interface portion. In some embodiments, the user device 112 may provide an HMI interface.

[0034] The computing system architecture of the automotive computer 208 and / or VCU 210 can omit certain computing modules. This should be easily understood. Figure 2 The computing environment depicted herein is an example of possible implementations according to this disclosure and should therefore not be considered restrictive or exclusive.

[0035] In addition to the components mentioned above, vehicle 102 may also have numerous mechanical systems and subsystems. A chassis, frame, or unibody construction may form the backbone of vehicle 102 and support the body and other components of vehicle 102. Vehicle 102 may include an engine that converts fuel into mechanical power to propel the vehicle forward. The engine includes various components such as the engine block, pistons, valves, and spark plugs. Vehicle 102 may also include a transmission system. The transmission system transmits power from the engine to the wheels. It includes a clutch, gearbox, drive shaft, differential, and other components. The transmission adjusts the power output to suit the vehicle's speed and load. Vehicle 102 may also include a suspension system. The suspension system absorbs shocks and maintains contact between the tires and the road, thus providing a smooth ride. It includes components such as springs, shock absorbers, and linkages. Vehicle 102 also includes a vehicle stopping system that allows the driver to decelerate or stop vehicle 102. It includes components such as pedals, master cylinders, lines, and bushings or shoes. Vehicle 102 also includes a steering system that allows the driver to guide the vehicle. The steering system includes components such as a steering wheel, steering column, rack and pinion, and tie rods. Vehicle 102 may also include an exhaust system for removing and filtering exhaust gases produced by the engine. It includes an exhaust manifold, catalytic converter, muffler, and exhaust tailpipe, among other components. Vehicle 102 also includes a cooling system to prevent overheating of the engine and / or battery. It includes components such as a radiator, water pump, thermostat, and coolant. Vehicle 102 may also include a cooling system for storing fuel and supplying fuel to the engine. It includes a fuel tank, fuel pump, fuel filter, and fuel injectors. The electrical system of vehicle 102 powers the electrical components of the vehicle. It may include a battery, alternator, starter motor, and wiring. The heating, ventilation, and air conditioning (HVAC) system controls the temperature inside vehicle 102. It includes a heater core, blower motor, and air conditioning compressor. In some embodiments, the vehicle may be an electric vehicle (EV) or a hybrid vehicle, and in either case, some of the aforementioned components will be replaced by an electric motor and a high-voltage battery. All the mechanical components working together ensure optimal operation of vehicle 102.

[0036] Robot callers and other unwanted calls are a reality of modern life. When a phone rings while driving, especially from an unknown number, it can create an emergency. The instinctive reaction to check who is calling can cause drivers to take their eyes off the road, even for just a few seconds. According to the National Highway Traffic Safety Administration (NHTSA), taking your eyes off the road for five seconds at 55 mph is equivalent to driving a football field blindfolded. This unconsciousness is problematic, especially when triggered by unexpected and frequent robot calls that can come at any time without prior notice.

[0037] Many drivers use their phones for navigation or music, and these unwanted calls can impair their awareness. When a call connects, drivers may instinctively glance at their screens, unintentionally increasing cognitive load and reducing reaction time. Even using hands-free devices may not alleviate this problem. Some robocalls may be designed to create a sense of urgency or fear, especially when they involve deception impersonating government agencies, utility companies, or financial institutions. Receiving such calls while driving can cause emotional distress, potentially impairing a driver's judgment and attention. In some cases, drivers may feel compelled to respond immediately out of confusion or fear of missing an important call. In recent years, efforts to combat unwanted and robocalls have intensified with policies such as the Criminal Enforcement and Deterrence Act (TRACED) on the Abuse of Robocalls and advancements in call blocking technologies. Despite these measures, the problem persists, largely because robocallers can easily circumvent preventative measures using fraudulent techniques and increasingly sophisticated methods.

[0038] Embodiments of this disclosure provide systems and methods for effectively responding to such unwanted calls and bot calls, and also provide techniques for financially benefiting from these unwanted callers.

[0039] When a user dials a phone number and presses the call button, the mobile device communicates with the nearest cell tower (also known as a base station or eNodeB in LTE networks). The device sends a channel request signal to establish a connection with the network. This request includes the dialed phone number and other necessary information, such as the user's identity (e.g., stored on a SIM card) and the type of service requested (e.g., voice call). The core infrastructure of the mobile network receives the request and begins authenticating and verifying the caller's identity and subscription status. This process is handled by the Home Location Register (HLR) or Authentication Center (AUC). The network checks whether the caller is authorized to make the call and ensures there are no restrictions (e.g., account suspension). The network determines how to route the call based on the dialed number. If the call is local (e.g., within the same operator's network), it is routed directly through the Mobile Switching Center (MSC). If the call is destined for a different network (e.g., domestic or international), the MSC forwards it to the appropriate external network, such as the Public Switched Telephone Network (PSTN) for traditional fixed-line connections or other mobile networks. The network locates the receiver's device by querying the Visitor Location Register (VLR) and identifying which cell tower the receiver is connected to. Once authentication is complete, the network assigns a temporary communication channel and continues the call setup process.

[0040] Once the recipient's device is located, the network signals the device to ring. This process involves a paging request, where the network broadcasts a signal to the recipient's device via the nearest cellular tower. If the recipient's device is powered on and connected to the network, it responds with a paging response, indicating that it is ready to accept a call. When the recipient answers the call, the network establishes a full-duplex communication channel between the calling device and the recipient's device. Voice data is then transmitted in real time using circuit-switched (CS) technology in 2G / 3G networks or Voice over LTE (VoLTE) in 4G and 5G networks. The call is maintained through continuous communication between the mobile device and the network's core infrastructure, switching to a different cellular tower if either the calling or receiving user is mobile. When either party ends the call, they send a call release message to the network. The network then releases the communication channel and frees up resources. Both the calling and receiving devices return to idle mode, ready for the next activity.

[0041] The recipient or the initiator can put a phone call on hold. While a phone call is on hold, both the recipient's device and the calling device can communicate with each other using SMS or other messaging applications, browse the internet, or use other applications that use data.

[0042] In the case of text messages, the process can begin with the originating user typing a message on his / her device. The device can use any of several protocols to send the message. These protocols can include the Short Message Peer-to-Peer Protocol (SMPP), Universal Mobile Telecommunications System (UMTS), or Long Term Evolution (LTE) protocols, depending on the network generation (2G / 3G / 4G / 5G). The message can be a standard SMS (for GSM 7-bit encoding, maximum 160 characters) or concatenated (multi-part) for longer text. The originating device then communicates with the nearest Base Transceiver Station (BTS). This step converts the message into a digital format and sends it over the air interface. The air interface can include Global System for Mobile Communications (GSM), UMTS, LTE, or 5G New Radio (NR) protocols. The BTS forwards the message to the core network and routes it to the Short Message Service Center (SMSC), which acts as a store-and-forward server. The SMSC queries the Home Location Register (HLR) or Home Subscriber Server (HSS) for the recipient's status and location information (e.g., the current MSC). The message is forwarded to the recipient's device via the nearest BTS. The message is received and stored in the recipient's device memory or SIM card. The user is notified via a message alert.

[0043] Figure 3 A flowchart of process 300 according to an embodiment of the present disclosure is shown. Process 300 can be performed by... Figure 1The user device 112 or the vehicle computer 208 of vehicle 102, or a combination thereof, executes this. At step 302, the first device (e.g., user device 112 or vehicle 102) can receive a call from the second device. As described above, the call can be a conventional voice telephone call or a message. The second device may be associated with a second user or entity and has an associated phone number. Once a call is received at the first device, the first device can check at step 304 whether the phone number associated with the second device is a pre-authorized phone number. The user of the first device can pre-authorize one or more phone numbers. For example, the user of the first device can designate phone numbers associated with friends and family members as authorized phone numbers. The user of the first device can designate any phone number as authorized based on his / her wishes. In an embodiment, the first device may store a list of pre-authorized phone numbers that the user of the first device has so designated.

[0044] If, at step 304, the first device determines that the phone number associated with the incoming call is part of a pre-authorized phone number, the first device may allow the call to proceed at step 306. For example, if the phone number associated with the incoming call is part of a pre-authorized phone number, the first device may send a paging response, as explained above, indicating that it is ready to accept the call. The first device may then begin ringing or display a notification that a message has arrived. If, at step 304, it is determined that the phone number associated with the incoming call is not part of a pre-authorized phone number, the incoming call is put on hold at step 308. Simultaneously, or after the incoming call is put on hold, if the user of the second device wishes the call to proceed, the first device sends information to the second device at step 310 regarding securing monetary collateral. The information sent to the second device may include information about one or more collateral service providers, the amount to be paid for the collateral, and the amount of time the phone call will be permitted. This information may be sent via SMS or via a messaging application. Therefore, when processing a phone call via a first communication channel, the first device may send this information at step 310 via a second communication channel different from the first communication channel. For example, a message sent to the second device might say something like "Please post a bond worth..." xx at [bond service provider name] for a total call duration of yy mins (Please pay the value at [bond service provider name]) The information includes a guarantee for xx, with a total call duration of yy minutes. In some embodiments, the information may also include details of whether the guarantee is refundable or non-refundable at the end of the call.

[0045] In one embodiment, to obtain / purchase a guarantee, the first device can send a link to the second device via SMS or a messaging application. The person operating the second device (i.e., the second user) can then access the link and visit the guarantee service provider's website to enter the requested information. Since the phone call is held during this time, the first and second devices remain connected; the guarantee acquisition process proceeds in parallel. The second user can pay for the guarantee amount using a credit / debit card, bank transfer, or a mobile payment platform. The guarantee service provider can then issue an electronic guarantee to the second person and send the details of the electronic guarantee to both the second and first devices. In another scenario, the second user can forward the details of the electronic guarantee to the first device. The first user can then verify the details of the guarantee to ensure its validity. In other embodiments, if the second device is not a smartphone, the user of the second device can complete the guarantee purchase transaction using Unstructured Supplemental Service Data (USSD) codes, SMS-based transfers, proxy-assisted transactions, or a mobile wallet.

[0046] In some embodiments, the user of the first device can specify different monetary amounts for different durations of a telephone call. For example, a one-minute telephone call... 1. A five-minute phone call is 10. In this way, the user of the first device can filter out unwanted or bot callers. Those who genuinely want to speak with the user of the first device for legitimate purposes can pay a guarantee amount to speak with the user of the first device. If the user of the second device wants to speak with the user of the first device, the user of the second device can purchase a guarantee based on information received from the first device. Once the guarantee is purchased, the guarantee service provider can send a message to the first device indicating that the guarantee has been purchased. At step 312, the first device can confirm whether the guarantee has been purchased based on the instruction sent at step 310. In an embodiment, the guarantee service provider can send a message to the first device confirming the purchase of the guarantee and providing details of the user of the second device, the amount of the guarantee purchased, etc. In some cases, the user of the second device can choose not to purchase the guarantee after receiving the message at step 310, and simply hang up. In this case, the first device can determine that the guarantee has not been purchased and can reject or terminate the call at step 314. If the first device determines that the guarantee has been purchased at step 312, the first device can allow the call to continue at step 316. In some embodiments, before connecting the call, the first device can send a message to the second device indicating the amount of time allocated for the telephone call. In this case, the phone call can be automatically terminated when the allocated duration expires.

[0047] In this embodiment, the amount of the requested security deposit may depend on the user or entity associated with the phone number of the second device. For example, if the phone number belongs to a charitable organization, a lower amount (such as...) can be requested. 1) As a guarantee deposit. In other cases, where the phone number is associated with a telemarketing agency or displays "unknown" or "blocked number," the guarantee amount can be set to a higher figure, such as... 10. To block these entities from making calls. The guarantee amount can also be configured based on the time of day, time of year, and other time considerations. In some embodiments, a user of the first device can allow calls from any phone number by using a challenge / response system. For example, the first device can automatically ask a user of the second device to answer one or more questions about the user of the first device to determine if the user of the second device is the genuine caller. In other cases, the user of the second device may be asked to solve a simple math test or answer multiple-choice questions before connecting a call.

[0048] In some cases, the settings for accepting calls can be based on the vehicle's motion status. For example, if the vehicle is in motion, calls may only be allowed from certain people (e.g., immediate family members, children's schools, etc.); other calls may be blocked or automatically sent to voicemail. In some cases, any incoming call from the second device may initially be put on hold, and a payment guarantee message may be sent to the second device. However, the user of the first device may provide a password to certain individuals (e.g., friends and family) that allows them to bypass the guarantee requirement. In one embodiment, if the incoming call's phone number is identified as one of a pre-authorized number (e.g., at step 304), then at step 310, the first device may send a bypass code along with information about the payment guarantee to the second device. The user of the second device or the second device itself may then enter the bypass code, and the call may be allowed to proceed. In other embodiments, if a user or entity associated with the second device wants to pay the guarantee but at that moment does not have sufficient available funds, no means to pay the guarantee, and / or does not know how to actually pay the guarantee, they may indicate their willingness to pay the guarantee (e.g., by entering via a touch tone key). The call can then be routed to a call center where the user of the first device has already established service for this purpose. The call center can help identify the user of the second device, help determine the importance of the call, and / or help the user of the second device pay the guarantee and then reconnect the call to the first device.

[0049] Figure 4A flowchart of process 400 according to another embodiment of this disclosure is shown. Process 400 may be executed by user device 112, vehicle computer 208 of vehicle 102, or a combination thereof. At step 402, a first device associated with a first user (e.g., user device 112) may receive a call from a second device belonging to a second user / entity (e.g., user device 114). At step 404, the first device may determine that the phone number associated with the second device is not a pre-authorized phone number. In response to the determination at step 404, the first device may place the call on hold at step 406, and at step 408 send a message regarding obtaining a guarantee to the second device if the second user wishes the call to continue. If the second user decides to abandon the conversation with the first user, the second user may hang up and terminate the call. At step 410, the first device may determine that the call has been terminated. Based on this, the first device may determine that the phone number associated with the second device may be a spam call or another unwanted call. At step 412, the first device may make a call to the phone number associated with the second device. In other words, the first device can call back the same phone number it received at step 402.

[0050] At step 414, the first device can determine that the phone number is associated with an entity, is disconnected, or is invalid. This may indicate that the phone number is unlikely to be attractive to the first user and may belong to a bot or fraudulent entity. Based on this determination, at step 416, the first device can add the phone number to a blocked number list. Any further calls from that number can be automatically blocked by the first device. In this way, the first device can automatically block suspicious phone numbers even without user intervention. In some embodiments, if the first device determines at step 410 that the call was terminated by a second device, process 400 can proceed directly to step 416, where the first device can add the phone number to the blocked number list. In this case, steps 412 and 414 can be bypassed.

[0051] Figure 5A flowchart of process 500 according to yet another embodiment of the present disclosure is shown. Process 500 may be performed by user device 112, or vehicle computer 208 of vehicle 102, or a combination thereof. At step 502, a first device receives a telephone call from a second device. At step 504, the first device may check the incoming telephone number and determine that the telephone number is not part of a pre-authorized list of telephone numbers. Based on this determination, the first device may place the telephone call on hold at step 506 and send a message to the second device at step 508. If the user of the second device wishes the call to continue, the message may include information about a payment guarantee. As described above, the information may include details of the guarantee service provider, the amount of the guarantee to be purchased, the duration of the telephone call allocated based on the guarantee amount, etc. At step 510, the first device may receive information that a guarantee has been purchased. For example, the guarantee service provider may send a message to the first device providing details of a guarantee purchased by the user of the second device.

[0052] At step 512, after verifying the purchase of the guarantee, the phone call can be allowed to continue. At step 514, the phone call can be ended or terminated by either the first device or the second device. The first device can detect the termination or end of the phone call, and based on this, at step 516, the first device can present the first user with the option to refund or retain the guarantee. This option can be presented via the user interface of the first device. At step 518, the first device can receive input from the first user indicating that the first user intends to retain the guarantee amount. In response, the first device can send a message to the second device indicating that the first user will retain the guarantee amount. Alternatively, the first user can decide to refund the guarantee amount to the second user. At step 520, the first device can receive input indicating that the first user wants to refund the guarantee amount to the second user. Then, the first device can send a message to the second device instructing the refund of the guarantee amount.

[0053] In some situations, a user may want to accept a call from an unknown or unauthorized phone number because the call may be important to them. However, it is impossible for a user to know in advance whether the incoming call is valuable / important and whether they should accept it. For example, consider a situation where a family member needs help and a stranger is offering that help. If the family member calls the user using a stranger's phone, the user may not recognize the number and ignore the call. However, in this case, it might be beneficial for the user to accept the call because it involves their family member. The systems and methods disclosed herein provide a way for users to consider such situations.

[0054] Figure 6A flowchart of process 600 according to an embodiment of the present disclosure is shown. Process 600 may be performed by user device 112, or vehicle computer 208 of vehicle 102, or a combination thereof. At step 602, the first device may receive a call from the second device. At step 604, the first device may determine that the phone number associated with the second device is not part of a pre-authorized list of phone numbers. However, in this case, the first device may determine at step 606 whether the second device is currently within a predetermined geographic area, rather than immediately sending information about obtaining a guarantee to the second device. In an embodiment, the first device may query its mobile network for the location of the second device. The mobile network may use cellular tower triangulation, GPS data associated with the second device, and / or Wi-Fi positioning technology to determine the location of the second device. The mobile network may then enable the location data of the second device to the first device. In some embodiments, to protect the privacy of the second device, the approximate location of the second device may be transmitted to the first device. As described above, a user of the first device may designate certain geographic locations as pre-authorized, such that if a call originates from one of the pre-authorized geographic locations, the call may be allowed to pass through, even if the incoming caller's phone number is not in the pre-authorized list of phone numbers. For example, a user of the first device can designate areas around his / her child's school, areas around the workplaces of one or more family members, etc., as parts of a pre-authorized geographic area. The reason is that if a call originates from one of these pre-authorized geographic areas, the call is less likely to be a bot call or other type of unwanted call, and is more likely to be related to someone the user of the first device is interested in.

[0055] If, at step 606, it is determined that the location of the second device is within one of the pre-authorized geographic areas, then at step 616, a call can be allowed to proceed directly to the first device. If, at step 606, it is determined that the location of the second device is not within one of the pre-authorized geographic areas, then the first device can determine at step 608 whether the location of the second device is currently close to one or more pre-selected vehicles. The one or more pre-selected vehicles may include vehicles associated with a family member of the first user. In an embodiment, the user can specify a distance value from the current location of one or more pre-selected vehicles as close. For example, a distance between 1 meter and 3 meters can be considered close to one or more pre-selected vehicles. It should be understood that the user can specify any reasonable distance for this purpose. The reason for doing so may be that if the call originates from a location close to the current location of one or more pre-selected vehicles, the call may be related to a family member of the user of the first device or someone of concern to the first user. The phone call may originate from a stranger's device but may be related to a family member. For example, consider the following scenario: a family member is involved in an accident related to his / her vehicle and is currently being assisted by a first responder or law enforcement officer, and the first responder or law enforcement officer is attempting to contact the first user using their own phone. In this situation, it would be beneficial to allow calls to the first device to connect even if the second device's phone number is not part of the pre-authorized list of phone numbers.

[0056] At step 608, the first device can determine the current location of one or more pre-ordered vehicles. This can be achieved using an application capable of tracking the location of one or more pre-ordered vehicles. The first device can also obtain location information of the second device that initiated the telephone call. The first device can compare the current location of one or more pre-ordered vehicles with the location information of the second device to determine whether the second device is close to and / or within a certain distance of the current location of one or more pre-ordered vehicles. If the first device determines that the location of the second device is close to and / or within a certain distance of the current location of one or more pre-ordered vehicles, the telephone call is allowed to continue at step 616. If the first device determines that the current location of the second device is not close to and / or not within a certain distance of the current location of one or more pre-ordered vehicles, the first device can send information about the purchase guarantee to the second device at step 610.

[0057] At step 612, the first device can verify whether a warranty has been purchased. If a warranty has been purchased, the call can be allowed to continue at step 616. If the first device determines that a warranty has not been purchased, the call can be rejected or terminated at step 614. Steps 610, 612, and 614 can be performed in a manner similar to those explained above with reference to other embodiments.

[0058] In some embodiments, a user receiving a call can define a bidding process that allows callers to bid for the user's time. Therefore, if a caller does want to speak with the user, they may be inclined to participate in the bidding process. The caller can send a message to the user's device (e.g., via SMS) instructing their bid while the call is on hold. If the user wants to answer the call, they can accept the bid and request the caller to purchase a guarantee for the offered amount. The user's device can then verify the purchase of the guarantee and allow the call to proceed. Fleet managers can use embodiments of this disclosure to block bot calls or unwanted calls during business hours so that these calls do not interrupt workers during working hours. An automated message can be sent to the caller stating that while the worker they are calling may be interested, they are currently busy and will call back at a different time outside of working hours.

[0059] Figure 7 An example control server 700 is depicted according to one or more exemplary embodiments of the present disclosure, on which any one or more technologies (e.g., methods) can be performed, or in conjunction with vehicle 102, the methods described above can be performed. Figure 1 A block diagram of the control server 104. In other embodiments, server 700 may act as a standalone device or may be connected to other servers (e.g., networked). In a networked deployment, server 700 may operate as a server machine, a client machine, or both in a server-client network environment. In the example, server 700 may act as a peer-to-peer (P2P) (or other distributed) network environment. Server 700 may be a personal computer (PC), tablet PC, set-top box (STB), personal digital assistant (PDA), mobile phone, smart keychain, wearable computing device, network device, network router, switch, or bridge, or any machine capable of executing instructions (continuously or otherwise) specifying actions to be taken by the server (such as a base station). Furthermore, although only a single server is shown, the term "server" should also be considered to include any collection of servers that individually or jointly execute a set (or more sets) of instructions for performing any one or more of the methods discussed herein, such as cloud computing, Software as a Service (SaaS), or other computer cluster configurations.

[0060] The examples described herein may include logic or components, modules, or mechanisms, or may operate on logic or components, modules, or mechanisms. A module is a tangible entity (e.g., hardware) capable of performing a specified operation during operation. A module includes hardware. In the examples, the hardware may be specifically configured to perform a specific operation (e.g., hardwired). In another example, the hardware may include a configurable execution unit (e.g., a transistor, circuit, etc.) and a computer-readable medium containing instructions that configure the execution unit to perform a specific task when in operation. The configuration may occur under the guidance of the execution unit or loading mechanism. Thus, when the device is in operation, the execution unit is communicatively coupled to the computer-readable medium. In this example, the execution unit may be a member of more than one module. For example, under operation, the execution unit may be configured at one point in time to implement a first module via a first set of instructions, and at a second point in time to reconfigure the execution unit to implement a second module via a second set of instructions.

[0061] Server (e.g., computer system) 700 may include a hardware processor 702 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), main memory 704, and static memory 706, some or all of which may communicate with each other via interconnect (e.g., bus) 708. Server 700 may also include a graphics display device 710, an alphanumeric input device 712 (e.g., a keyboard), and a user interface (UI) navigation device 714 (e.g., a mouse). In this example, the graphics display device 710, the alphanumeric input device 712, and the UI navigation device 714 may be a touchscreen display. Server 700 may additionally include a storage device (i.e., a drive unit) 716, a network interface device / transceiver 720 coupled to an antenna, and one or more sensors 728, such as a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensors. Server 700 may include output controller 734, such as serial (e.g., Universal Serial Bus (USB)), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connections, to communicate with or control one or more peripheral devices (e.g., printers, card readers, etc.).

[0062] Storage device 716 may include machine-readable medium 722 on which one or more sets of data structures or instructions (e.g., software) embodying or utilized by any or more of the techniques or functions described herein are stored. The instructions may also reside wholly or at least partially within main memory 704, static memory 706, or hardware processor 702 during execution of the instructions by server 700. In this example, one or any combination of hardware processor 702, main memory 704, static memory 706, or storage device 716 may constitute the machine-readable medium.

[0063] Although machine-readable medium 722 is shown as a single medium, the term "machine-readable medium" can include a single medium or multiple media (e.g., a centralized or distributed database, and / or associated caches and servers) configured to store one or more instructions.

[0064] Various embodiments can be implemented entirely or partially in software and / or firmware. This software and / or firmware may take the form of instructions contained in or on a non-transitory computer-readable storage medium. Those instructions can then be read and executed by one or more processors to enable the performance of the operations described herein. The instructions can be in any suitable form, such as, but not limited to, source code, compiled code, interpreted code, executable code, static code, dynamic code, etc. Such computer-readable medium may include any tangible non-transitory medium for storing information in a form readable by one or more computers, such as, but not limited to, read-only memory (ROM); random access memory (RAM); disk storage media; optical storage media; flash memory, etc.

[0065] The term "machine-readable medium" can include any medium having the following properties: capable of storing, encoding, or transporting instructions executable by server 700; and causing server 700 to perform any or more of the technologies disclosed herein; or capable of storing, encoding, or transporting data structures used by or associated with such instructions. Examples of non-limiting machine-readable media can include solid-state memory as well as optical and magnetic media. In examples, large-scale machine-readable media includes machine-readable media having a plurality of particles having rest masses. Specific examples of large-scale machine-readable media can include non-volatile memory, such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM) or electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.

[0066] Instructions can also be transmitted or received over a communication network via a transmission medium using the network interface device / transceiver 720, utilizing any of several transport protocols (e.g., Frame Relay, Internet Protocol (IP), Transmission Control Protocol (TCP), User Datagram Protocol (UDP), Hypertext Transfer Protocol (HTTP), etc.). Example communication networks may include local area networks (LANs), wide area networks (WANs), packet data networks (e.g., the Internet), mobile phone networks (e.g., cellular networks), conventional telephone (POTS) networks, wireless data networks (e.g., the IEEE 802.11 series of standards known as Wi-Fi®, the IEEE 802.16 series of standards known as WiMax®), the IEEE 802.15.4 series of standards, and peer-to-peer (P2P) networks, etc. In the example, the network interface device / transceiver 720 may include one or more physical sockets (e.g., Ethernet sockets, coaxial sockets, or telephone sockets) or one or more antennas for connection to the communication network. In the example, the network interface device / transceiver 720 may include multiple antennas to communicate wirelessly using at least one of the following: Single-Input Multiple-Output (SIMO), Multiple-Input Multiple-Output (MIMO), or Multiple-Input Single-Output (MISO). The term "transmission medium" should be considered to include any intangible medium capable of storing, encoding, or transmitting instructions for execution by server 700 and comprising digital or analog communication signals, or other intangible media used to facilitate communication of such software. The operations and processes described and shown above may be implemented or performed in any suitable order as needed in various implementations. Additionally, in some implementations, at least a portion of the operations may be implemented in parallel. Furthermore, in some implementations, fewer or more operations than those described may be performed.

[0067] It should be noted that the vehicle implements and / or performs the operations described herein in accordance with the owner's manual and safety guidelines. Additionally, any action taken by the vehicle owner / driver based on recommendations or notices provided by the vehicle should comply with all rules specific to the vehicle's location and operation (e.g., federal, state, national, city, etc.). Recommendations or notices provided by the vehicle should be considered as advice and followed only in accordance with any rules specific to the vehicle's location and operation. In the foregoing disclosure, reference has been made to the accompanying drawings, which form a part of the foregoing disclosure, illustrating specific implementations in which the present disclosure may be practiced. It should be understood that other implementations may be utilized and structural changes may be made without departing from the scope of the present disclosure. References to “an embodiment,” “embodiment,” “example embodiment,” etc., in this specification indicate that the described embodiment may include a particular feature, structure, or characteristic, but each embodiment may not necessarily include said particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Moreover, when features, structures, or characteristics are described in connection with embodiments, those skilled in the art will recognize such features, structures, or characteristics in conjunction with other embodiments, whether explicitly described or not.

[0068] Furthermore, where appropriate, 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 implement one or more of the systems and programs described herein. Throughout the specification and claims, certain terms are used to refer to specific system components. As those skilled in the art will appreciate, components may be referred to by different names. This document is not intended to distinguish between components with different names but the same function.

[0069] It should also be understood that the word “example” as used herein is intended to be non-exclusive and non-restrictive in nature. More specifically, the word “example” as used herein refers to one of several examples, and it should be understood that there is no undue emphasis or preference for any particular example described.

[0070] Computer-readable media (also known as processor-readable media) include any non-transitory (e.g., tangible) medium that contributes to providing data (e.g., instructions) that can be read by a computer (e.g., by the computer's processor). Such media can take many forms, including but not limited to non-volatile and volatile media. A computing device may include computer-executable instructions, said instructions which can be executed by one or more computing devices (such as those listed above) and stored on a computer-readable medium.

[0071] Regarding the processes, systems, methods, heuristics, etc., described herein, it should be understood that although the steps of such processes, etc., have been described as occurring in a certain ordered order, such processes can be practiced with the described steps performed in a different order than that described herein. It should also be understood that some steps may be performed simultaneously, other steps may be added, or some steps described herein may be omitted. In other words, the description of processes herein is provided for the purpose of illustrating various embodiments and should in no way be construed as limiting the claims.

[0072] Therefore, it should be understood that the above description is intended to be illustrative rather than restrictive. Many embodiments and applications beyond the examples provided will become apparent upon reading the above description. The scope should not be determined by reference to the above description, but rather by reference to the appended claims and the full scope of their equivalents. Future developments in the techniques discussed herein are anticipated and expected, and the disclosed systems and methods will be incorporated into such future embodiments. In conclusion, it should be understood that modifications and variations are possible with this application.

[0073] Unless explicitly indicated otherwise herein, all terms used in the claims are intended to be given their ordinary meaning as understood by one skilled in the art as described herein. Specifically, unless the claims explicitly limit the recitation to the contrary, the use of singular articles such as “a,” “the,” or “the” should be interpreted as referring to one or more of the elements indicated by the recitation. Unless otherwise specifically stated or otherwise understood in the context of use, conditional language such as, in particular, “may,” “possibly,” “may,” or “can” is generally intended to express that some embodiments may include certain features, elements, and / or steps, while other embodiments may not include certain features, elements, and / or steps. Therefore, such conditional language is generally not intended to imply that one or more embodiments require each feature, element, and / or step in any way.

[0074] According to an embodiment, the vehicle computer receives the first telephone call through a first communication channel, and the vehicle computer sends the first message through a second communication channel different from the first communication channel.

[0075] According to an embodiment, before sending the first message, the vehicle computer determines whether the current location of the first device is within a predetermined geographical area, wherein the predetermined geographical area is associated with the user of the vehicle.

[0076] According to an embodiment, the instructions also cause the vehicle computer to: receive a second telephone call from a second device; determine that the telephone number associated with the second device is not part of the pre-authorized list of telephone numbers; send a third message to the second device, the third message including information about purchasing a guarantee in order to continue the first telephone call; determine that the second device has terminated the second telephone call; and automatically add the telephone number associated with the second device to the list of blocked telephone numbers.

[0077] According to an embodiment, before sending the first message, the vehicle computer determines whether the current location of the first device is within a predetermined distance of the current location of one or more vehicles associated with the user of the vehicle.

[0078] According to an embodiment, the instructions also cause the vehicle computer to receive the second message from the warranty service provider that issued the warranty.

Claims

1. A method comprising: The first device receives a first telephone call from the second device; The first device determines that the telephone number associated with the second device is not part of a pre-authorized list of telephone numbers; The first device sends a first message, including information about the purchase guarantee, to the second device in order to continue the first telephone call; The first device receives a second message indicating that the guarantee has been purchased; as well as The first device accepts the first telephone call based on the guarantee purchased.

2. The method of claim 1, further comprising: Before sending the first message, the first telephone call is put on hold.

3. The method of claim 1, wherein: Receiving the second message also includes receiving the second message from the guarantee service provider that issued the guarantee.

4. The method of claim 1, wherein: Receiving the first telephone call further includes receiving the first telephone call through a first communication channel; and Sending the first message also includes sending the first message through a second communication channel different from the first communication channel.

5. The method of claim 1, further comprising: Before sending the first message, the first device determines whether the current location of the second device is within a predetermined geographical area, wherein the predetermined geographical area is associated with the user of the first device.

6. The method of claim 1, further comprising: Before sending the first message, the first device determines whether the current location of the second device is close to the current location of one or more pre-authorized vehicles, wherein the one or more pre-authorized vehicles are associated with the user of the first device.

7. The method of claim 1, further comprising: Receive a second telephone call from a third device; The first device determines that the telephone number associated with the third device is not part of the pre-authorized list of telephone numbers; The first device sends a third message, including information about the purchase guarantee, to the second device in order to continue the first telephone call; The first device determines that the third device has terminated the second telephone call; as well as The first device automatically adds the phone number associated with the third device to the list of blocked phone numbers.

8. A method comprising: The first device receives a first telephone call from the second device; The first device determines that the telephone number associated with the second device is not part of a pre-authorized list of telephone numbers; The first device determines whether the current location of the second device is within a predetermined geographical area, wherein the predetermined geographical area is associated with the user of the first device; The first device determines whether the current location of the second device is close to the current location of one or more pre-authorized vehicles, wherein the one or more pre-authorized vehicles are associated with a user of the first device; as well as If the current location of the second device is within the predetermined geographical area, or if the current location of the second device is close to the current location of one or more pre-authorized vehicles, then the first device allows the first telephone call to continue.

9. The method of claim 8, further comprising: If the current location of the second device is not within the predetermined geographical area, or if the current location of the second device is not close to the current location of one or more pre-authorized vehicles, then the first device sends a first message to the second device instructing the user of the second device to purchase a guarantee to continue the first telephone call.

10. The method of claim 9, further comprising: The first device receives a second message from the second device, the second message indicating that the warranty has been purchased; and The first phone call is allowed to continue as the first device purchases the guarantee based on the guarantee.

11. The method of claim 10, further comprising: The first device determines that the first telephone call has ended; as well as The guarantee is automatically returned to the user of the second device.

12. The method of claim 9, further comprising: The first device determines that the second device terminates the first telephone call without purchasing the warranty; as well as The first device automatically adds the phone number associated with the second device to the list of blocked phone numbers.

13. The method of claim 8, wherein: Determining whether the current location of the second device is within a predetermined geographical area also includes receiving the current location of the second device from a first mobile network associated with the first device.

14. The method of claim 8, wherein the first telephone call is placed on hold before determining that the telephone number associated with the second device is not part of a pre-authorized list of telephone numbers.

15. A vehicle comprising: An automotive computer, the automotive computer including a communication interface configured to communicate via a mobile phone network; as well as A memory device coupled to a vehicle control unit and storing instructions that, when executed by the controller, cause the vehicle computer to: Receive a first telephone call from the first device; It is determined that the telephone number associated with the first device is not part of a pre-authorized list of telephone numbers; Put the first telephone call on hold; Send a first message to the first device, the first message instructing the user of the first device to purchase a guarantee; Receive a second message indicating that the user of the first device has purchased the guarantee; as well as The first telephone call is allowed to continue based on the purchase of the aforementioned guarantee.

Images