CN102404312B - Points of trust is used to provide service - Google Patents

Abstract

Provides services using trustpoints. In some embodiments, the processor can be used to establish trust by performing user authentication, platform authentication, and environment authentication with a trustpoint system. The processor may interact information with the trustpoint system in response to establishing trust. In some embodiments, trustpoint systems may cooperate to provide various services, such as escort, battery charging, vehicle safety, and/or emissions reporting services.

Description

Provide services using trustpoints

related application

This application claims priority to US Provisional Application No. 61/316,498, filed March 23, 2010, entitled "REMOTEMAINTENANCE," which is incorporated herein in its entirety.

This application is a continuation-in-part of U.S. Patent Application Serial No. 12/879,226, filed September 10, 2010, at Attorney Docket No. 073338.0734, and entitled "System and Methods for Remote Maintenance In An Electronic Network With Multiple Clients," the entirety of which Incorporated into this article.

technical field

The present invention relates generally to information exchange, and more particularly to providing services using trustpoints.

Background technique

Services provided to clients may require the transmission of confidential information over a communication network. For example, a client may send a request for service to a service provider, and the service provider may in turn request payment information from the client. A sender of confidential information may want to authenticate the recipient before sending the information.

Description of drawings

For a more complete understanding of the present invention, together with its features and advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, in which:

Figure 1 illustrates an example of a network in which one or more service systems provide services to one or more client systems;

Figure 2 illustrates an example of a client system;

3A-3C illustrate an example of a method for providing escort (escort) services;

Figures 4, 5, 6, 7A-7C and 8A-8B illustrate examples of methods for providing battery charging services;

Figure 9 illustrates an example of a method for providing vehicle safety services; and

FIG. 10 illustrates an example of a method for providing emission reporting services.

detailed description

Embodiments of the present invention and its advantages are best understood by referring to FIGS. 1 through 10 of the drawings, like reference numerals being used for like and corresponding parts of the various drawings.

overview

According to the present invention, problems and disadvantages associated with previous techniques for providing services can be reduced or eliminated.

In some embodiments, the processor may operate to establish trust with the trustpoint system by performing user authentication, platform authentication, and environment authentication. The processor may send information in response to establishing the trust and trustpoint system. In some embodiments, trustpoint systems may cooperate to provide various services, such as escort, battery charging, vehicle safety, and/or emissions reporting services.

Certain embodiments of the invention may provide one or more technical advantages. A technical advantage of one embodiment may be that a mobile device may include a trustpoint system that may allow the mobile device to receive services more efficiently. Another technical advantage of one embodiment may be that trustpoint systems may cooperate to provide various services, such as escort, battery charging, vehicle safety, and/or emissions reporting services.

Certain embodiments of the present invention may not include any, some, or all of the above technical advantages. One or more other technical advantages will be apparent to those skilled in the art from the claims, description, and drawings included herein.

FIG. 1 illustrates an example of a network 2 in which one or more service systems 10 provide services to one or more client systems 20 . Systems 10 and 20 may include a trustpoint system 12 that may be used to establish trust among systems 10 and 12 . In some embodiments, a mobile device may include a trustpoint system 12 that may allow the mobile device to more efficiently participate in providing services. In some embodiments, trustpoint systems 12 may cooperate to provide various services, such as escort, battery charging, vehicle safety, and/or emissions reporting services.

In the illustrated example, network 2 includes one or more service systems 10 coupled to one or more client systems 20 via communication network 18 . Service system 10 may provide one or more services to one or more client systems 20 . Examples of services include escort, battery charging, vehicle safety and/or emissions reporting services. Another example of a service includes managing software and/or firmware updates and/or status.

Examples of service systems 10 include vehicle service centers, traffic information centers, charging systems, payment systems, and any other systems that can provide services to client systems 20 . A vehicle service center may be a center that facilitates providing services to vehicles. Traffic information centers may include centers with real-time traffic information that can be used to plan driving routes. The charging system may be a system that can charge a power source (eg, a battery) of a client system 20 (eg, a vehicle). The payment system may be a system that can authorize payment for services. Examples of payment systems may include banks, credit card companies, credit institutions, businesses, or other suitable organizations that may authorize payment for services.

Service system 10 may include features that allow service system 10 to communicate securely with other entities. For example, service system 10 may include a trustpoint system 12 that establishes trust with other entities. Trustpoint system 12 is described in more detail below. As another example, service system 10 may include a server that manages security policies used to authenticate other entities. A policy may define a set of attribute values that need to be met before a client system 20 is granted permission to access a service.

Client system 20 may receive services from service system 10 . Examples of client systems 20 include computers, mobile devices, and vehicles, which may be referred to as computer client systems, mobile client systems, and vehicle client systems, respectively.

A computer may be any computing device such as a server, laptop or desktop. A mobile device may be a handheld device that can communicate wirelessly. Examples of mobile devices include phones (such as cellular, mobile, or smart), digital assistants (such as personal or business), and gaming devices. A vehicle may be a device designed to transport people and/or goods. Examples of vehicles include land transportation (such as automobiles, trains, bicycles, and motorcycles), watercraft (such as boats and ships), and aircraft (such as airplanes). In some embodiments, a vehicle may include a transceiver to allow wireless communication. The communication network 18 is described in more detail below.

One or more service systems 10 and/or one or more client systems 20 may include a trustpoint system 12 (or trustpoint). In some embodiments, a trustpoint system 12 may establish trust with one or more other trustpoint systems 12 by performing user authentication, platform authentication, and/or context authentication in order to exchange information with other trustpoint systems 12 . Authentication may also involve performing authentication for services and/or performing billing for usage of services.

In some embodiments, establishing trust may include sending trustpoint information from the first trustpoint system to the second trustpoint system to allow the second trustpoint system to authenticate the first trustpoint system. In an embodiment, establishing trust may include receiving trustpoint information from a trustpoint system, and authenticating the trustpoint system using the trustpoint information. Trustpoint information may include information that may be used to authenticate the trustpoint system. An example of trustpoint information is described in more detail with reference to FIG. 2 . Trust Calculations and TrustCubes are examples of methods and systems that can provide assured reporting within the Trustpoint System 12 .

In some embodiments, client system 20 may also include one or more virtual machines (VMs) 22, virtual machine managers (VMMs) 24, trusted platform modules (TPMs) 26, resource lists 28, client network systems 30 , resource 32 and GPS receiver 40 .

Trusted platform module 26 may generate trustpoint information that may be used to authenticate module 26 . In some embodiments, trusted platform module (TPM) 26 may utilize trustpoint system 12 to function. In some embodiments, trusted platform module 26 includes at least one processor with a unique Rivest, Shamir and Adleman (RSA) key that can be burned into the processor. The client system 20 of the trusted platform module 26 may be authenticated using the RSA key. In some embodiments, trusted platform module 26 may generate cryptographic keys using, for example, a pseudo-random number generator.

In some embodiments, a virtual machine 22 may correspond to a client network system 30 and/or a process associated with a client network system 30 . For example, a virtual machine 22 may be used to incorporate sensors. One or more virtual machines 22 may run one or more operating systems (OS). In some embodiments, virtual machine 22 may share processing resources of client system 20 through virtual machine 24 and use a single-purpose operating system.

A virtual machine manager (VMM) 24 may create, run, monitor and/or terminate virtual machines 22 . Virtual machine manager 24 may intercept failures and/or interruptions between virtual machines 22 and/or control access to hardware and/or software that applications have. Virtual machine manager 24 may also manage processor multitasking by sharing time among various threads running by applications and/or virtual machines 22 . Virtual machine manager 24 may manage communications among virtual machines 22 .

Resource list 28 may include a whitelist of entities to which access is permitted and/or a blacklist of entities to which access will be denied.

Client network 30 may be a network within client system 20 that facilitates cooperation among components of client system 20 . For example, client network 30 may be a network managing processors in a vehicle (such as a FlexRay network). As another example, a controller area network (CAN or CAN bus) allows microcontrollers and devices to communicate with each other without a host computer. Additional examples include Time Triggered Protocol (TTP) and Avionics Full Duplex Switched Ethernet (AFDX) networks.

Client network 30 may manage resources 32, such as resources of client system 20, eg, processors and/or their associated software, firmware, and/or processor-related processing instructions. For example, client network 30 may include central processing units (CPUs) each utilizing software and/or firmware to function. Client network 30 may be responsible for maintenance and/or operation of resources 32 , including managing update status and/or versions of firmware and/or software associated with each resource 32 in client system 20 .

A Global Positioning System (GPS) receiver 40 interfaces with the GPS navigation satellite system, which provides location and time information.

FIG. 2 illustrates an example of a client system 20 . The client system 20 may be a computer client system, a mobile client system, or a vehicle client system. In the illustrated instance, the client system includes an interface (IF) 120 , logic 122 , and one or more memories 124 . Logic 122 may include one or more processors 130 and applications such as trustpoint module 132 and service module 134 . Trustpoint module 132 may include user module 140 , platform module 144 , and environment module 148 . The service modules 134 may include an escort module 150 , a battery charging module 152 , a vehicle safety module 154 , and an emissions reporting module 156 .

Trustpoint module 132 may be used to establish trust with other trustpoint systems. Trustpoint module 132 may perform authentication to establish trust. As previously discussed, authentication may also involve authorization and/or accounting. Trustpoint module 132 may perform user authentication, platform authentication, and/or context authentication.

Trustpoint module 132 may use the trustpoint information to perform authentication. Examples of trustpoint information include user, device, and context information, described in more detail below. The trustpoint module 132 may check to see that the information meets requirements to determine whether the trustpoint is acceptable. For example, a trustpoint may be acceptable if it is on a whitelist or not on a blacklist. If the trustpoint is acceptable, the trustpoint may be allowed to access the service and/or may continue to communicate with the entity.

The user authentication module 140 performs user authentication to authenticate a user. The user authentication module 140 may authenticate a user using user information. User information belongs to a specific user and can be entered by the user. User information may include identifiers (such as usernames and passwords) and biometric information (such as physiological or behavioral information). Physiological information relates to characteristics of the body. Examples include fingerprints, palm prints, hand features, facial features, DNA, iris or retina scans, and smell. Behavioral information is related to human behavior. Examples include typing rhythm, gait, and voice.

The platform module 144 performs platform authentication to authenticate the platform. The platform module 144 may perform authentication using device information provided by the platform. Device information may include identifiers such as registry identifiers (IDs), network addresses such as Internet Protocol (IP) addresses, machine addresses such as Media Access Control (MAC) addresses, certificates such as public key infrastructure (PKI ) certificate) and/or other identifiers that identify the device.

The environment module 148 performs platform environment authentication to authenticate the platform environment. The environment module 148 may use the environment information to perform authentication. Environmental information may include software information (such as software version and/or status) of software running on the platform, hardware information (such as hardware version and hardware architecture), and peripheral information (such as peripheral identifiers) of peripherals managed by the platform. ).

The service module 134 facilitates providing services to the client systems 20 . In an example, services include escort, battery charging, vehicle safety, and/or emissions reporting services. However, any suitable service may be provided in any suitable number.

The convoy module 150 performs convoy processing, which obtains the route planned according to the task list, and then instructs the vehicle to move along the route. In some embodiments, the convoy process may include establishing trust with the mobile trustpoint system through the vehicle's vehicle trustpoint system. A task list including tasks is received from the mobile trustpoint system. Establish trust with the service trustpoint system and get the route of the task from the service trustpoint system. Directs the vehicle to move along the route. An example of escort processing is described in more detail with reference to FIG. 3 .

The battery charging module 152 performs battery charging processes that allow the battery charging system to charge the vehicle's battery. In some embodiments, the battery charging process may include authenticating the charging trustpoint system with the vehicle's vehicle trustpoint system. The vehicle trustpoint information is sent to allow the charging trustpoint system to authenticate the vehicle trustpoint system. Send the battery information of the vehicle battery to the charging trust point system. Payment information corresponding to the vehicle is sent to the charging trustpoint system to allow the charging trustpoint system to charge the battery. An example of battery charging processing is described in more detail with reference to FIGS. 4-8 .

The vehicle security module 154 performs vehicle security processing that sends records made in response to security triggering events to one or more trustpoint systems. In certain embodiments of vehicle security processing, a vehicle point of trust system of a vehicle in the vehicle environment may sense a security triggering event. The vehicle environment is recorded in response to the safety trigger event to generate a record. Send record to trustpoint system to allow the trustpoint system to send the record to the mobile trustpoint system. Trustpoint systems can also store records in a database. An example of vehicle security processing is described in more detail with reference to FIG. 9 .

The emissions reporting module 156 performs an emissions reporting process that collects vehicle driving data used to calculate the emissions of the vehicle. In some embodiments, the emissions reporting process may include collecting driving data through a vehicle's vehicle trustpoint system. The driving data is sent to the central point of trust system to allow the central point of trust system to calculate one or more emission values for the vehicle. An example of emissions reporting processing is described in more detail with reference to FIG. 10 .

3 to 10 illustrate examples of service methods. In examples, client systems 20 may include mobile devices, vehicles, or other client systems. The service system 10 may include a vehicle service center, a traffic information center, a charging system or other service systems. In an example, each system 10 and 20 may have a trustpoint system (or trustpoints). The method may be performed by other components of systems 10 and 20 and/or trustpoints.

Figure 3 illustrates an example of a method for providing escort services. In an example, the client system 20 includes a mobile device and a vehicle, and the service system 10 includes a vehicle service center and a traffic information center. The methods may be performed through a trustpoint, such as a vehicle trustpoint.

At step 210 a task list is received from a user. A task may include an action to be performed (such as making a grocery shopping), a location (which can be expressed as an address), a business, or a type of location (such as a grocery store). In some embodiments, a user may enter a task list into a mobile device. This may allow the user to enter the task list at the user's convenience, such as when not driving. The mobile device moves into the vehicle with the user at step 212 . The vehicle may detect that a person has entered the vehicle and may request the user to provide a user identification.

Steps 214 to 222 may be performed to establish trust between the mobile trustpoint and the vehicle trustpoint. Information is requested at step 214 . In some embodiments, the request may require trustpoint information including user information obtained from the user and mobile trustpoint information provided by the mobile device. The mobile trustpoint generates trustpoint information at step 216 .

Information is received at step 218 . The vehicle trustpoint checks at step 220 whether the mobile trustpoint is acceptable. Trustpoints can be checked by performing user, platform and/or environment authentication. If the mobile trustpoint is not acceptable, the method returns to step 214 to request the information again. If the mobile trustpoint is acceptable, the method proceeds to step 222, where the vehicle checks whether the user and the mobile device are acceptable based on the user information and the mobile trustpoint information. If the user and mobile device are not acceptable, the method returns to step 214 to request the information again. If acceptable to the user and mobile device, the method proceeds to step 224 .

The vehicle trustpoint requests a task list at step 224 . At step 226 a task list is received from the mobile trustpoint. The vehicle trustpoint requests a route at step 228 from the central trustpoint.

Steps 230 to 238 may be performed to establish trust between the central trustpoint and the vehicle trustpoint. The central trustpoint requests information at step 230 to authenticate the vehicle trustpoint. The vehicle trustpoint generates trustpoint information at step 232 . Trustpoint information may include device information, user information, and/or mobile trustpoint information provided by the vehicle.

The trustpoint information is sent to the central trustpoint at step 234 to allow the central trustpoint to authenticate the vehicle trustpoint. The central trustpoint checks at step 236 whether the vehicle trustpoint is acceptable. A trustpoint may be considered acceptable if the trustpoint information is acceptable. Information from acceptable trust points can be considered trustworthy; information from unacceptable trust points can be considered untrustworthy. If the vehicle trustpoint is not acceptable, the method returns to step 230 where the central trustpoint requests the information again. If the vehicle trustpoint is acceptable, the method proceeds to step 238 .

The central trust point checks at step 238 whether the user and vehicle are acceptable. Entities can be considered acceptable based on policy. Policies may specify what types of information are required in order to be acceptable from an entity. For example, a policy may specify what types of user information, device information, and/or context information are required. If they are not, the method returns to step 230 and the central trust point again requests the information. If they are acceptable, the method proceeds to step 240 .

Steps 240 to 244 may be performed to obtain the route of the task. The central trust point sends a request for a route at step 240 . The traffic information center sends the route at step 242 . Routes can be planned according to real-time traffic reports. For example, routes can be planned to avoid traffic jams. The central trustpoint forwards the route to the vehicle trustpoint at step 244 .

The vehicle trustpoint sends a request for payment information at step 246 to the mobile trustpoint. The mobile trustpoint authenticates the vehicle trustpoint at steps 248 and 250 . The mobile trustpoint sends the information at step 252 .

At step 254 the escort is initiated. Escorting may be performed by any suitable means. For example, one or more components of the vehicle may instruct the vehicle to move along a route or may instruct a user to move the vehicle along a route.

Steps 256 to 264 are performed to check the central trust point. The vehicle sends a request for a user account to the central trust point at step 256 . The central trustpoint generates and sends trustpoint information at step 258 . At step 260 trustpoint information is received. The vehicle checks with the vehicle service center at steps 262 and 264 .

In step 266 payment information is sent. The vehicle service center updates the user account at step 268 and sends the result to the vehicle trustpoint at step 270 . The vehicle trustpoint forwards the results to the mobile trustpoint at step 272 .

4-8 illustrate examples of methods for providing battery charging services. 4 illustrates an example overview of a method for providing battery charging services. In an example, the client system 20 includes mobile devices and vehicles, and the service system 10 includes a charging system and a payment system. The method may be performed by a trustpoint, such as a vehicle trustpoint of a vehicle.

In some embodiments, the information used to authorize payment for services is transmitted from the mobile device rather than stored in the vehicle. This prevents unauthorized persons from gaining access to the vehicle and services. In some cases, users who obtain services via the mobile trustpoint are charged less than users who do not use the mobile trustpoint. In these scenarios, users using mobile trustpoints cause fewer problems and are less risky. Accordingly, service providers may pay less for trustpoint users for insurance, and thus may be able to provide services at a lower cost. Additionally, users can be encouraged to adopt the use of trustpoints at less cost.

In some embodiments, authentication may be performed at step 308 to establish trust between the vehicle trustpoint and the charging trustpoint. In some embodiments, authenticating may include receiving charging trustpoint information at the vehicle trustpoint, and authenticating the charging trustpoint using the charging trustpoint information. Authentication may also include sending the vehicle trustpoint information to allow the charging trustpoint to authenticate the vehicle trustpoint.

Any suitable trustpoint information may be used. Charging trustpoint information may include a charging system identifier (such as servicer name and/or machine identifier) and system status (such as working or ready to charge). Vehicle trustpoint information may include, for example, device information and/or user information. Vehicle equipment information may include a vehicle description (such as make and/or model) and/or a vehicle identification number.

The vehicle trustpoint requests charging at step 310 . The charging trustpoint requests battery information at step 312 . Battery information may include parameters describing the battery, eg, voltage, make, model, current charge (such as x% capacity), capacity, vacancy, temperature, or other characteristics of the battery. At step 314 the battery information is sent to the charging trustpoint.

The charging trustpoint authorizes the vehicle trustpoint at step 316 . The charging trustpoint notifies the vehicle trustpoint at step 318 that the charging system is ready to charge. The vehicle trustpoint authorizes the vehicle at step 320 .

In particular embodiments, authentication may be performed at step 321 to establish trust between the vehicle trustpoint and the mobile trustpoint. In particular embodiments, authenticating may include receiving mobile trustpoint information at the vehicle trustpoint and authenticating the mobile trustpoint using the mobile trustpoint information. Authentication may also include sending vehicle trustpoint information to allow the mobile trustpoint to authenticate the vehicle trustpoint.

The vehicle trustpoint requests payment information for the user account at step 322 from the mobile trustpoint. Payment information corresponding to the account is received at step 324 from the mobile trustpoint. Payment information may include information that allows the account to be charged for the service. In some embodiments, the mobile trustpoint may receive a key that allows the mobile trustpoint to encrypt payment information.

The payment information is sent to the charging trustpoint or to the payment system at step 326 to allow the charging trustpoint to charge the battery. Charging trustpoints can forward information to payment systems. The payment system authorizes the account at step 328 and sends the account authorization to the vehicle at step 330 . The vehicle trustpoint authorizes payment at step 332 .

The vehicle trustpoint performs a status check at step 334 . A status check may involve determining that the vehicle is authorized and/or the payment is authorized. A status check may involve determining that the vehicle is unable to move during charging, eg, the vehicle is parked and the brakes are set. If the status check fails, an alert is sent to the mobile trustpoint. If the status check passes, the vehicle sends a request to begin charging at step 336 .

The charging system begins charging the vehicle at step 338 . At step 340 the state of charge is sent to the mobile trust point. The state of charge may indicate the charge of the battery and the time remaining to charge the battery. Mobile devices can display charging status. In some embodiments, the charging system may cooperate with smart meters connected to the energy source, such as electric meters or solar panel harvesters. Smart meters may be able to evaluate charging parameters such as charging time.

Figure 5 illustrates an example of a method for mutual authentication between a vehicle trustpoint and a charging trustpoint. The vehicle detects at step 410 that the battery is at an alert level. The alert level may be the level at which the battery should be charged, eg, a level in the range of less than 10, 10 to 25, or 25 to 50 percent charge.

The vehicle trustpoint requests information from the charging trustpoint at step 412 . The charging trustpoint generates trustpoint information at step 414 and sends the information to the vehicle trustpoint at step 416 . The vehicle trustpoint determines at step 418 whether the charging trustpoint is acceptable. If the charging trust point is not acceptable, the method returns to step 412 where the vehicle requests the information again. If the charging trustpoint is acceptable, the method proceeds to step 420 where the vehicle trustpoint notifies the charging trustpoint that the charging trustpoint is acceptable.

The charging trustpoint requests information from the vehicle trustpoint at step 422 . The vehicle trustpoint generates trustpoint information at step 424 and sends the information at step 426 . The charging trustpoint determines whether the vehicle trustpoint is acceptable at step 428 . If the vehicle trustpoint is not acceptable, the method returns to step 422 to request the information again. If the vehicle trust point is acceptable, the method proceeds to step 430 to notify the vehicle trust point that the vehicle trust point is acceptable. The method may continue with FIGS. 6 , 7 , or 8 .

Figure 6 illustrates an example of a method for charging a battery of a vehicle. The vehicle trustpoint requests charging from the charging trustpoint at step 432 . The charging trustpoint requests battery information at step 434 . The vehicle trustpoint sends battery information at step 436 . The charging trustpoint sets the charging type at step 438 . The charge type may include the amount of charge described by the battery information to be provided to the battery. At step 440 the charging station is connected to the vehicle.

The charging trustpoint requests payment information at step 442, and the vehicle trustpoint forwards the request to the mobile trustpoint. The mobile trustpoint sends the payment information to the vehicle trustpoint which forwards the information at step 444 . The charging trustpoint requests authorization of payment at step 446 . The payment system notifies the charging trustpoint at step 448 that the payment is authorized.

The charging station charges the vehicle's battery at step 450 . The vehicle displays the status of charging at step 452 . The vehicle sends the charging status to the mobile device at step 454 and the mobile device displays the status at step 456 . Charging ends at step 458 . The charging trustpoint requests payment at step 460 and the vehicle trustpoint notifies at step 462 that payment is authorized. The charging trustpoint then sends charging information at step 464 .

FIG. 7 illustrates another example of a method for charging a battery of a vehicle. Steps 510 to 520 may be substantially similar to steps 432 to 442 of FIG. 6 .

Mutual authentication is performed at steps 522 to 540 to establish trust between the mobile trustpoint and the vehicle trustpoint. The vehicle trustpoint requests information from the mobile trustpoint at step 522 . The mobile trustpoint generates trustpoint information at step 524 and sends the information to the vehicle trustpoint at step 526 . The vehicle trustpoint checks at step 528 whether the mobile trustpoint is acceptable. If the mobile trustpoint is not acceptable, the method returns to step 522 to request the information again. If the mobile trust point is acceptable, the method proceeds to step 530, where the vehicle trust point notifies the mobile trust point that the mobile trust point is acceptable.

The mobile trustpoint requests information from the vehicle trustpoint at step 532 . The vehicle trustpoint generates trustpoint information at step 534 and sends the information to the mobile trustpoint at step 536 . The mobile trustpoint checks at step 538 whether the vehicle trustpoint is acceptable. If the vehicle trustpoint is not acceptable, the method returns to step 532 to request the information again. If the vehicle trust point is acceptable, the method proceeds to step 540 where the mobile trust point notifies the vehicle trust point that the vehicle trust point is acceptable.

The vehicle trustpoint information generates a one-time key at step 542 and sends the one-time key to the mobile trustpoint at step 554 . The mobile trustpoint encrypts the payment information at step 546 using the one-time key. Encrypted payment information may include, for example, encrypted credit card numbers. The mobile trustpoint then sends the encrypted payment information to the vehicle trustpoint at step 548 . The vehicle trustpoint decrypts the payment information at step 550 . Steps 552-576 may be substantially similar to steps 444-464.

FIG. 8 illustrates another example of a method for charging a vehicle's battery. Steps 610-620 may be substantially similar to steps 432-442.

Steps 622 to 628 describe the vehicle service center generating a key for the mobile device. The vehicle trustpoint requests a one-time key at step 622 from the central trustpoint. The central trustpoint generates a one-time key at step 624 and sends the one-time key to the vehicle trustpoint at step 626 and to the mobile trustpoint at step 628 . Steps 630-660 may be substantially similar to steps 546-576.

Figure 9 illustrates an example of a method for providing vehicle safety services. The method may be performed in a vehicle environment by a vehicle trust point of the vehicle. The vehicle environment may include at least a portion of any of: the interior of the vehicle, the exterior of the vehicle, and/or the area surrounding the vehicle.

At step 710 a security trigger event is detected. A security trigger event may be a visual phenomenon (such as a flashing light), an auditory phenomenon (such as a crashing sound), or a movement (such as a shake or vibration).

The vehicle environment is recorded at step 712 to generate a record. The vehicle environment may be recorded by any suitable device configured to detect visual and/or audible signals, such as a camera or recorder. At step 714 the record is sent to the central trust point.

The central trust point stores the record in a database at step 716 . Stored records can be used as evidence in interrogations regarding security trigger events. The central trustpoint sends the record to the mobile trustpoint at step 718 . The user of the mobile device can then play the recording.

FIG. 10 illustrates an example of a method for providing emission reporting services. The method may be performed by a vehicle trustpoint of the vehicle.

Driving data is collected at step 730 . Driving data may include any suitable data from which emissions can be calculated. For example, data may include temperature, noise, and emissions detected from the exhaust. Driving data can identify emissions emitted when only the battery is operating, only the engine is operating, or both. In some embodiments, the driving data may not include the user's personal data. In other embodiments, personal data may be included.

At step 732, the driving data is sent to the central trust point. The central point of trust calculates the vehicle's emissions value at step 734 . For example, carbon dioxide emissions can be calculated.

Modifications, additions or omissions may be made to the devices and systems disclosed herein without departing from the scope of the present invention. Devices and system components may be integrated or separated. In addition, operations of devices and systems may be performed by more, fewer or other components. For example, the operations of service module 134 and trustpoint module 132 may be performed by one component, or the operations of modules 132 or 134 may be performed by more than one component. Additionally, operations of the devices and systems may be performed using any suitable logic, including software, hardware, and/or other logic. As used in this document, "each" refers to each member of a collection or each member of a sub-collection of a collection.

Modifications, additions or omissions may be made to the methods disclosed herein without departing from the scope of the present invention. Methods may include more, fewer or other steps. Additionally, the steps may be performed in any suitable order.

In some embodiments, an entity performing a first step that precedes (such as causes) a second step may be considered to contribute to the second step. For example, if an entity performs step A prior to step B, the entity also contributes to step B. In some embodiments, a first entity performing a first step prior to a second step that a second entity can perform may be considered to allow the second entity to perform the second step. For example, if a first entity performs step A prior to step B that a second entity can perform, the first entity also allows the second entity to perform step B.

Components of the devices and systems disclosed herein may include interfaces, logic, memory, and/or other suitable elements. An interface receives input, sends output, processes the input and/or output, and/or performs other suitable operations. An interface may include hardware and/or software.

Logic executes the operation of components, eg, executes instructions to generate output from inputs. Logic may include hardware, software, and/or other logic. Logic may be encoded in one or more tangible media and may perform operations when executed by a computer.

Some logic, such as a processor, may manage the operation of the components. A processor may include logic (such as a device or means) operable to interpret and/or execute other logic. Examples of processors include one or more of any of the following: computers, microprocessors, microcontrollers, digital signal processors (DSPs), application specific integrated circuits (ASICs), or Program instructions and/or any other digital or analog circuitry that processes data.

In certain embodiments, operations of the embodiments may be performed by one or more computer-readable media encoded with computer programs, software, computer-executable instructions, and/or instructions capable of being executed by a computer. In certain embodiments, the operations of the embodiments may be performed by one or more computer-readable media storing, embodying, and/or encoding a computer program and/or having a computer program stored and/or encoded.

Logic such as electronic content ("Content") (e.g., software (including updates)) may include files, code (such as objects or executable code), data records, and/or any other electronically recorded data structure. Examples may include text files, spreadsheets, emails, medical records, images, web pages, programs (such as word processing and document management programs), and/or other electronic data or programs.

Memory stores information. Memory may include one or more non-transitory, tangible, computer-readable and/or computer-executable storage media. Examples of memory include computer memory (e.g., random access memory (RAM), read-only memory (ROM), or electrically erasable programmable read-only memory (EEPROM), mass storage media (e.g., hard disks), removable storage media ( For example, compact disks (CDs) or digital video disks (DVDs), databases, and/or network storage (e.g., servers), and/or other computer-readable media that retain data even when power is not volatile or nonvolatile memory.

The components of the devices and systems can be coupled by any suitable communications network that communicates according to any suitable communications protocol. The communication network (e.g., network 18) may include some or all of one or more of the following: public switched telephone network (PSTN), public or private data network, local area network (LAN), metropolitan area network (MAN), wide area network ( WAN), local area, virtual private network (VPN), area such as the Internet, or global communication or computer network, wired or wireless network, intranet, other suitable communication link, or any combination of any of the foregoing. A communications network may include routers, hubs, switches, gateways, call controllers, and/or any other suitable components in any suitable form or arrangement.

While this disclosure has been described in terms of certain embodiments, alterations and modifications of the embodiments will be apparent to those skilled in the art. Accordingly, the above description of the embodiments does not limit the present disclosure. There may be other changes, substitutions, and transformations without departing from the scope and spirit of the present invention as defined by the appended claims.

Claims (7)

1. the method that the service being associated with the vehicles is provided, including:

By the vehicles points of trust system of the vehicles by following steps and the first points of trust system Set up and trust:

At least one user profile and facility information is received from described first points of trust system, And

User according to the vehicles described in described user profile or described facility information certification or The equipment being associated with the user of the described vehicles；

The task list including multiple task, the plurality of task is received from described first points of trust system Treat to be performed by the user of the described vehicles；

By sending vehicles points of trust information to allow described second letter to the second points of trust system Appoint vehicles points of trust system described in dot system certification, set up letter with described second points of trust system Appoint；

The route performing the plurality of task is obtained from described second points of trust system；And

The described vehicles are indicated to move along described route.

2. the method for claim 1, also includes:

The second points of trust information is received from described second points of trust system；

According to the second points of trust system described in described second points of trust authentification of message；And

Payment information is sent to described second points of trust system.

3. the method that the service being associated with the vehicles is provided, including:

By the vehicles points of trust system authentication charging points of trust system of the vehicles；

Vehicles points of trust information is sent, to allow described charging letter to described charging points of trust system Appoint vehicles points of trust system described in dot system certification；

The battery information of the battery of the described vehicles is sent to described charging points of trust system；

The request to payment information is received from described charging points of trust system；

Vehicles letter is sent to the Mobile trust dot system being associated with the user of the described vehicles Appoint dot information, to allow vehicles points of trust system described in described Mobile trust dot system certification；

After vehicles points of trust system described in described Mobile trust dot system success identity, from institute State Mobile trust dot system and receive described payment information；And

The payment information corresponding with the described vehicles that will receive from described Mobile trust dot system It is sent to described charging points of trust system, to allow described charging points of trust system that battery is filled Electricity.

4. method as claimed in claim 3, also includes:

Key is sent to described Mobile trust dot system, to allow described Mobile trust dot system to encrypt Described payment information.

5. method as claimed in claim 3, also includes:

Display shows the charged state of the electric charge of described battery.

6. method as claimed in claim 3, also includes:

Will indicate that the charged state of the electric charge of described battery is sent to Mobile trust dot system, to allow State Mobile trust dot system and show described charged state.

7. method as claimed in claim 3, also includes:

Key is received from points of trust center；And

Send the key to described Mobile trust dot system, to allow described Mobile trust dot system Encrypt described payment information.