JP5927815B2 - System and method for providing services using trustpoints - Google Patents

Description

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

  Services provided to clients may require sending confidential information over a communication network. For example, when a client sends a service request to a service provider, the service provider may request payment information from the client. The sender of the secret information may desire to authenticate the recipient prior to sending the information.

  According to the present invention, the drawbacks and problems associated with the conventional service providing technology can be reduced or eliminated.

  In certain embodiments, the processor may operate to establish trust with the trustpoint system by performing user authentication, platform authentication, and environment authentication. The processor may communicate information with the trustpoint system in response to establishing trust. In certain embodiments, multiple trustpoint systems cooperate to provide a variety of services such as, for example, escort services, battery charging services, vehicle security services, and / or emissions reporting services.

  Certain embodiments of the invention may provide one or more technical advantages. A technical advantage of one embodiment is that a mobile (mobile) device can include a trustpoint system that can allow the mobile device to be serviced more efficiently. Another technical advantage of one embodiment is that multiple trustpoint systems can work together to provide a variety of services, such as escort services, battery charging services, vehicle security services, and / or emissions reporting services, for example. That is.

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

For a more complete understanding of the present invention and the features and advantages thereof, reference is made to the following detailed description taken in conjunction with the drawings, including the following figures:
1 is a diagram illustrating an example of a network in which one or more service systems provide services to one or more client systems. FIG. It is a figure which shows an example of a client system. It is a figure which shows an example of the method of providing an escort service. It is a figure which shows an example of the method of providing an escort service. It is a figure which shows an example of the method of providing an escort service. It is a figure which shows the example of the method of providing a battery charging service. It is a figure which shows the example of the method of providing a battery charging service. It is a figure which shows the example of the method of providing a battery charging service. It is a figure which shows the example of the method of providing a battery charging service. It is a figure which shows the example of the method of providing a battery charging service. It is a figure which shows the example of the method of providing a battery charging service. It is a figure which shows the example of the method of providing a battery charging service. It is a figure which shows the example of the method of providing a battery charging service. It is a figure which shows an example of the method of providing a vehicle security service. It is a figure which shows an example of the method of providing an emission report service.

  Embodiments of the present invention and its advantages are best understood by referring to FIGS. Like reference numerals are used for like and corresponding parts in the various drawings.

  FIG. 1 shows an example of a network 2 in which one or more service systems 10 provide services to one or more client systems 20. The systems 10 and 20 may include a trustpoint system (TPS) 12 that may be used to establish trust between the systems 10 and 20. In certain embodiments, a mobile (mobile) device may include a trustpoint system 12 that may allow the mobile device to participate more efficiently in providing services. In certain embodiments, these trustpoint systems 12 cooperate to provide a variety of services such as, for example, escort services, battery charging services, vehicle security services, and / or emissions reporting services.

  In the illustrated example, the network 2 includes one or more service systems 10 coupled to one or more client systems 20 via a 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 security and / or emission reporting services. Another example of a service includes managing software and / or firmware updates and / or status.

  Examples of service system 10 include vehicle service centers, traffic information centers, charging systems, payment systems, and other systems that can provide services to client system 20. The vehicle service center may be a center that assists in providing services to the vehicle. The traffic information center may include a center that holds real-time traffic information that can be used to plan driving routes. The charging system may be a system capable of charging a power source (for example, a battery) of the client system 20 (for example, a vehicle). The payment system may be a system that can authorize payment for a service. Examples of payment systems may include banks, credit card companies, credit bureaus, companies, or other suitable organizations that can certify fees for services.

  Service system 10 may include functionality that enables service system 10 to communicate securely with other entities. For example, the service system 10 may include a trustpoint system 12 that establishes trust with other entities. The trust point system 12 will be described later in more detail. As another example, service system 10 may include a server that manages security policies used to authenticate other entities. A security policy may specify a set of attribute values that must be met before the client system 20 is granted permission to access the service.

  The client system 20 can receive a service from the service system 10. Examples of client system 20 include computers, mobile devices, and vehicles. Hereinafter, these are also referred to as a computer client system, a mobile client system, and a vehicle client system, respectively.

  The computer may be any computing device such as a server, a notebook computer, or a desktop computer. The mobile device may be a handheld device capable of wireless communication. Examples of mobile devices include phones (eg, mobile phones, mobile phones, smart phones, etc.), personal digital assistants (eg, for individuals or businesses), and gaming devices. The vehicle may be a device designed to transport people and / or cargo. Examples of vehicles include land transport aircraft (eg, cars, trains, bicycles, motorcycles, etc.), and aircraft (eg, airplanes). In certain embodiments, the vehicle may include a transceiver that enables wireless communication. The communication network 18 will be described in detail later.

  One or more service systems 10 and / or one or more client systems 20 may include a trustpoint system 12 (or trustpoint). In certain embodiments, the trustpoint system 12 performs the user authentication, platform authentication, and / or environment authentication to communicate information with the one or more trustpoint systems 12, thereby providing the one or more other Trust may be established with the trustpoint system 12. This authentication may involve performing service authorization and / or performing accounting for use of the service.

  In certain embodiments, establishing the trust enables the second trustpoint system to authenticate the first trustpoint system from the first trustpoint system to the second trustpoint system. Transmitting the trustpoint information to the network. In certain embodiments, establishing trust may include receiving trustpoint information from the trustpoint system and authenticating the trustpoint system using the trustpoint information. Trustpoint information may include information that can be used to authenticate a trustpoint system. An example of trust point information will be described later in more detail with reference to FIG. Examples of systems and methods that can provide certification reports between multiple trustpoint systems 12 include Trusted Computing and TrustCube.

  In certain embodiments, the client system 20 may also include one or more virtual machines (VMs) 22, a virtual machine manager (VMM) 24, a trusted platform module (TPM) 26, A resource list 28, a client network system 30, a resource 32, and a GPS receiver 40 may be included.

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

  In certain embodiments, virtual machine 22 may correspond to client network system 30 and / or processes associated with client network system 30. For example, the virtual machine 22 can be used to incorporate sensors. One or more virtual machines 22 may start one or more operating systems (OS). In certain embodiments, the virtual machine 22 may share the processing resources of the client system 20 via the virtual machine 24 using a single purpose operating system.

  A virtual machine manager (VMM) 24 may create, start, monitor, and / or terminate virtual machines. Virtual machine manager 24 may intercept interrupts and / or errors between multiple virtual machines 22 and / or control application access to hardware and / or software. The virtual machine manager 24 may also manage multiple tasks of the processor by sharing time between the various threads that the application and / or virtual machine 22 launches. The virtual machine manager 24 can manage communication between a plurality of virtual machines 22.

  The resource list 28 may include a white list of entities that have been granted access and / or a black list of entities that are denied access.

  The client network 30 may be a network in the client system 20 that supports cooperation between the components of the client system 20. For example, the client network 30 may be a network that manages processors in the vehicle (for example, a FlexRay network). As another example, a controller area network (CAN or CAN bus) allows a microcontroller and device to communicate with each other without using a host computer. Further examples include a time triggered protocol (TTP) network and an avionics full-duplex switched Ethernet (AFDX) network.

  The client network 30 may manage resources 32, such as resources of the client system 20, such as processor and / or associated software, firmware, and / or processing instructions for the processor. For example, the client network 30 may have multiple central processing units (CPUs) that each use software and / or firmware for operation. Client network 30 may be involved in the operation and / or maintenance of resources 32, including managing the version and / or update status of software and / or firmware associated with each resource 32 within client system 20.

  A global positioning system (GPS) receiver 40 acts as an interface to a GPS navigation satellite system that provides position and time information.

  FIG. 2 shows an example of the client system 20. The client system 20 may be a computer client system, a mobile client system, a vehicle client system, or the like. In the illustrated example, 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 a user module 140, a platform module 144, and an environment module 148. Service module 134 may include an escort module 150, a battery charging module 152, a vehicle security module 154, and an emissions reporting module 156.

  Trustpoint module 132 may be used to establish trust with other trustpoint systems. The trustpoint module 132 may perform authentication to establish trust. As described above, authentication may involve authorization and / or accounting. Trustpoint module 132 may perform user authentication, platform authentication, and / or environment authentication.

  The trustpoint module 132 may use trustpoint information to perform authentication. Examples of trustpoint information include user, device, and environment information, as described in more detail below. The trustpoint module 132 may verify that the information meets the requirements to determine if a trustpoint is acceptable. For example, a trustpoint may be acceptable if it is whitelisted or not blacklisted. If the trustpoint is acceptable, the trustpoint is authorized to access the service and / or can continue to communicate with the entity.

  The user authentication module 140 performs user authentication and authenticates the user. User authentication module 140 may use the user information to authenticate the user. User information is about individual users and can be entered by the users. The user information may include an identifier (eg, user name and password) and biometric information (eg, physiological information or behavior information). Physiological information relates to the characteristics of the human body. Examples include fingerprints, palm prints, hand features, facial features, DNA, iris or retinal scans, and odors. Behavior information relates to individual behavior. Examples include typing (keystroke) rhythm, walking and voice.

  The platform module 144 performs platform authentication to authenticate the platform. Platform module 144 may use device information provided by the platform to perform authentication. The device information includes an identifier (for example, a registration identifier (ID)), a network address (for example, an internet protocol (IP) address), a machine address (for example, a media access control (MAC) address), a certificate ( For example, public key infrastructure (PKI) certificates, etc.) and / or other identifiers that identify the device.

  The environment module 148 performs environment authentication to authenticate the platform environment. Environment module 148 may use the environment information to perform authentication. The environment information depends on the software information (eg, software version and / or status) of software running on the platform, hardware information (eg, hardware version and / or hardware configuration), and the platform. Peripheral device information (eg, peripheral device identifier) of the managed peripheral device may be included.

  The service module 134 may support services provided to the client system 20. In this example, services include an escort service, a battery charging service, a vehicle security service, and an emissions reporting service. However, any suitable number of any suitable services may be provided.

  The escort module 150 obtains a route planned according to the task list, and executes an escort process that instructs the vehicle to move along the route. In certain embodiments, the escort process may include establishing trust with the mobile trustpoint system by the vehicle trustpoint system of the vehicle. A task list having a plurality of tasks is received from the mobile trustpoint system. Trust with the service trustpoint system is established, and routes for the plurality of tasks are obtained from the service trustpoint system. The vehicle is commanded to move along this route. An example of the escort process will be described later in more detail with reference to FIG.

  The battery charging module 152 performs a battery charging process that allows the battery charging system to charge the vehicle battery. In certain embodiments, the battery charging process may include authenticating the charging trustpoint system with a vehicle trustpoint system of the vehicle. Vehicle trustpoint information is transmitted to allow the charging trustpoint system to authenticate the vehicle trustpoint system. Battery information of the vehicle battery is transmitted to the charging trustpoint system. In order to allow the charging trustpoint system to charge the battery, payment information corresponding to the vehicle is transmitted to the charging trustpoint system. An example of the battery charging process will be described in more detail later with reference to FIGS.

  The vehicle security module 154 performs a vehicle security process that transmits records created in response to a security trigger event to one or more trustpoint systems. In certain embodiments of the vehicle security process, the vehicle trustpoint system of the vehicle within the vehicle environment may detect a security trigger event. The vehicle environment is recorded to create a record in response to a security trigger event. This record is sent to the trustpoint system, which is enabled to send this record to the mobile trustpoint system. The trustpoint system may also store this record in a database. An example of the vehicle security process will be described later in detail with reference to FIG.

  The emissions reporting module 156 performs an emissions reporting process that collects vehicle driving data that is used to calculate vehicle emissions. In certain embodiments, the emissions reporting process may include collecting driving data by a vehicle trustpoint system for the vehicle. This operational data is transmitted to the center trustpoint system, which enables the center trustpoint system to calculate one or more emission values for the vehicle. An example of the emission report process will be described in detail later with reference to FIG.

  3 to 10 show examples of methods related to services. In these examples, client system 20 may include a mobile device, a vehicle, or other client system. Service system 10 may include a vehicle service center, a traffic information center, a charging system, or other service system. In these examples, each system 10 and 20 may have a trustpoint system (or trustpoint). These methods may be performed by the trust points and / or other components of the systems 10 and 20.

  3A to 3C show an example of a method for providing an escort service. In this 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. This method may be performed by a trust point, for example a vehicle trust point.

  At step 210, a task list is received from a user. A task may include an action to be performed (eg, going to grocery shopping), a location (which may be represented as an address), a transaction, or a type of location (eg, a grocery store). In certain embodiments, the user may enter a task list on the mobile device. This may allow the user to enter the task list at the convenience of the user, for example when not driving. At step 212, the mobile device moves with the user into the vehicle. The vehicle may detect that someone has entered the vehicle and request this user to provide a user identifier.

  Steps 214 through 222 are performed to establish trust between the mobile trustpoint and the vehicle trustpoint. At step 214, information is requested. In certain embodiments, the request may request trustpoint information with user information obtained from a user and mobile trustpoint information provided by the mobile device. At step 216, the mobile trustpoint generates trustpoint information.

  At step 218, information is received. At step 220, the vehicle trustpoint is checked to see if this mobile trustpoint is acceptable. Trustpoint verification may be performed by performing user authentication, platform authentication, and / or environment authentication. If the mobile trustpoint is not acceptable, the method returns to step 214 and requests information again. If the mobile trustpoint is acceptable, the method proceeds to step 222 and checks whether the user and the mobile device are acceptable according to the user information and the mobile trustpoint information. If the user and mobile device are not acceptable, the method returns to step 214 and requests information again. If the user and mobile device are acceptable, the method proceeds to step 224.

  At step 224, the vehicle trustpoint requests a task list. At step 226, a task list is received from the mobile trustpoint. At step 228, the vehicle trustpoint requests a route from the center trustpoint.

  Steps 230 through 238 are performed to establish trust between the center trustpoint and the vehicle trustpoint. At step 230, the center trustpoint requests information to authenticate the vehicle trustpoint. At step 232, the vehicle trustpoint generates trustpoint information. This trustpoint information may include device information provided by the vehicle, user information, and / or mobile trustpoint information.

  At step 234, this trustpoint information is transmitted to the center trustpoint, enabling the center trustpoint to authenticate the vehicle trustpoint. At step 236, the center trustpoint is checked to see if the vehicle trustpoint is acceptable. A trustpoint may be considered acceptable if the trustpoint information is acceptable. Information from an acceptable trustpoint can be considered reliable and information from an unacceptable trustpoint can be considered untrustworthy. If the vehicle trustpoint is not acceptable, the method returns to step 230 and the center trustpoint requests information again. If the vehicle trustpoint is acceptable, the method proceeds to step 238.

  At step 238, the center trustpoint is checked to see if it is acceptable to the user and the vehicle. An entity may be considered acceptable according to a policy. A policy may specify what kind of information is required from the entity to be acceptable. For example, the policy may specify what type of user information, device information and / or environmental information is required. If the user and vehicle are not acceptable, the method returns to step 230 and the center trustpoint requests information again. If they are acceptable, the method proceeds to step 240.

  Steps 240 through 244 are performed to obtain a route for the task. At step 240, the center trustpoint sends a route request. In step 242, the traffic information center transmits a route. The route can be planned according to real-time traffic information. For example, routes can be planned to avoid traffic jams. At step 244, the center trustpoint forwards the route to the vehicle trustpoint.

  At step 246, the vehicle trustpoint sends a request for payment information to the mobile trustpoint. In steps 248 and 250, the mobile trustpoint authenticates the vehicle trustpoint. In step 252, the mobile trustpoint transmits information.

  In step 254, escort is started. Escorts may be performed in any suitable manner. For example, one or more components of the vehicle may instruct the vehicle to move along the route or may instruct the user to move the vehicle along the route.

  Steps 256 through 264 are performed to check the center trustpoint. At step 256, the vehicle transmits a user account request to the center trustpoint. At step 258, the center trustpoint generates and transmits trustpoint information. At step 260, the trustpoint information is received. In steps 262 and 264, the vehicle inspects the vehicle service center.

  In step 266, payment information is transmitted. The vehicle service center updates the user account at step 268 and transmits the result to the vehicle trustpoint at step 270. At step 272, the vehicle trustpoint forwards the result to the mobile trustpoint.

  4 to 8 show an example of a method for providing a battery charging service. FIG. 4 shows an outline of an example of a method for providing a battery charging service. In this example, the client system 20 includes a mobile device and a vehicle, and the service system 10 includes a charging system and a payment system. This method may be performed by a trust point, for example a vehicle trust point of a vehicle.

  In certain embodiments, the information for authorizing payment for the service is sent from the mobile device instead of being stored in the vehicle. This can prevent an unauthorized person from getting a service on the vehicle. In certain situations, a user receiving service via a mobile trustpoint may be charged less expensive than a user not using the mobile trustpoint. In such a situation, a user who uses a mobile trustpoint rarely causes a problem and can be said to have a low risk. Thus, the service provider does not provide much insurance for the trustpoint user and can therefore be able to provide the service at a lower cost. Users can also be encouraged to choose to use trustpoints if the cost is low.

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

  Any suitable trustpoint information may be used. The charging trustpoint information may include a charging system identifier (eg, service provider name and / or machine identifier, etc.) and system status (eg, operating or ready to charge). The vehicle trustpoint information may include device information and / or user information, for example. The vehicle device information may include a vehicle description (eg, manufacturer and / or model) and / or vehicle identification number.

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

  At step 316, the charging trustpoint approves the vehicle trustpoint. At step 318, the charging trust point notifies the vehicle trust point that the charging system is ready to charge. At step 320, the vehicle trustpoint approves the vehicle.

  In certain embodiments, at step 321, authentication may be performed to establish trust between the vehicle trustpoint and the mobile trustpoint. In certain embodiments, the authentication 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.

  At step 322, the vehicle trustpoint requests payment information from the mobile trustpoint regarding the user's transaction. At step 324, payment information corresponding to the transaction is received from the mobile trustpoint. Payment information may include information that allows the transaction to be charged for the service. In certain embodiments, the mobile trustpoint may receive a key that allows the mobile trustpoint to encrypt payment information.

  At step 326, payment information is transmitted to the charging trustpoint or payment system, enabling the charging trustpoint to charge the battery. A charging trustpoint may transfer the information to the payment system. The payment system approves the transaction at step 328 and transmits the transaction approval to the vehicle at step 330. At step 332, the vehicle trustpoint approves the settlement.

  At step 334, the vehicle trustpoint performs a status check. The status check may include determining that the vehicle has been approved and / or that the payment has been approved. The situation check may include determining that the vehicle cannot move during charging, for example, that the vehicle is parked and the brake is set. If the status check does not pass, a warning is sent to the mobile trustpoint. If the status check is passed, in step 336, the vehicle trustpoint transmits a request to start charging.

  At step 338, the charging system begins to charge the vehicle. At step 340, the charging status is transmitted to the mobile trustpoint. The charging status can indicate the amount of charge on the battery and the remaining time to charge the battery. The mobile device may display the charging status. In certain embodiments, the charging system may cooperate with a smart meter (eg, an electric meter or a solar panel current collector) connected to an energy source.

  FIG. 5 shows an example of a mutual authentication method between the vehicle trust point and the charging trust point. At step 410, the vehicle detects that the battery is at a warning level. The alert level can be a level at which the battery is to be charged, for example, a level of charge less than 10%, a range of 10% to 25%, or a range of 25% to 50%.

  At step 412, the vehicle trustpoint requests information from the charge trustpoint. The charging trustpoint generates trustpoint information at step 414 and transmits the information to the vehicle trustpoint at step 416. At step 418, it is determined whether the vehicle trustpoint is acceptable for the charge trustpoint. If the charging trustpoint is not acceptable, the method returns to step 412 and the vehicle requests information again. If the charging trustpoint is acceptable, the method proceeds to step 420 and the vehicle trustpoint notifies the charging trustpoint that the charging trustpoint is acceptable.

  At step 422, the charging trustpoint requests information from the vehicle trustpoint. The vehicle trustpoint generates trustpoint information at step 424 and transmits the information at step 426. At step 428, the charging trustpoint is determined if the vehicle trustpoint is acceptable. If the vehicle trustpoint is not acceptable, the method returns to step 422 and requests information again. If the vehicle trustpoint is acceptable, the method proceeds to step 430 and notifies the vehicle trustpoint that the vehicle trustpoint is acceptable. This method continues in FIG.

  FIG. 6 shows an example of a method of charging a vehicle battery. At step 432, the vehicle trustpoint requests charging by the charge trustpoint. At step 434, the charging trustpoint requests battery information. At step 436, the vehicle trustpoint transmits battery information. At step 438, the charge trustpoint sets the charge type. The charge type may include a charge amount to be supplied to the battery described in the battery information. At step 440, the charging station is connected to the vehicle.

  At step 442, the charging trustpoint requests payment information, and the vehicle trustpoint forwards the request to the mobile trustpoint. At step 444, the mobile trustpoint sends payment information to the vehicle trustpoint, which forwards the information. At step 446, the charging trustpoint requests payment approval. At step 448, the payment system notifies the charging trustpoint that the payment has been approved.

  In step 450, the charging stand charges the vehicle battery. In step 452, the vehicle displays the charging status. In step 454, the vehicle transmits the charging status to the mobile device, and in step 456, the mobile device displays the charging status. At step 458, charging is terminated. In step 460, the charging trust point requests settlement, and in step 462, the vehicle trust point notifies settlement approval. At step 464, the charging trustpoint transmits billing information.

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

  In steps 522 to 540, mutual authentication is performed to establish trust between the mobile trustpoint and the vehicle trustpoint. At step 522, the vehicle trustpoint requests information from the mobile trustpoint. The mobile trustpoint generates trustpoint information at step 524 and transmits the information to the vehicle trustpoint at step 526. At step 528, the vehicle trustpoint is checked to see if the mobile trustpoint is acceptable. If the mobile trustpoint is not acceptable, the method returns to step 522 and the information is requested again. If the mobile trustpoint is acceptable, the method proceeds to step 530 where the vehicle trustpoint notifies the mobile trustpoint that the mobile trustpoint is acceptable.

  At step 532, the mobile trustpoint requests information from the vehicle trustpoint. The vehicle trustpoint generates trustpoint information at step 534 and transmits the information to the mobile trustpoint at step 536. At step 538, the mobile trustpoint is checked to see if the vehicle trustpoint is acceptable. If the vehicle trustpoint is not acceptable, the method returns to step 532 and the information is requested again. If the vehicle trustpoint is acceptable, the method proceeds to step 540 where the mobile trustpoint notifies the vehicle trustpoint that the vehicle trustpoint is acceptable.

  The vehicle trustpoint generates a one time key at step 542 and transmits the onetime key to the mobile trustpoint at step 544. In step 546, the mobile trustpoint encrypts the payment information using the one-time key. The encrypted payment information can include, for example, an encrypted credit card number. At step 548, the mobile trustpoint sends the encrypted payment information to the vehicle trustpoint. At step 550, the vehicle trustpoint decrypts the payment information. Steps 552 through 576 may be substantially similar to steps 444 through 464.

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

  Steps 622 through 628 describe that the vehicle service center generates a key for the mobile device. At step 622, the vehicle trustpoint requests a one-time key from the center trustpoint. The center trust point generates a one-time key at step 624, transmits the one-time key to the vehicle trust point at step 626, and transmits the one-time key to the mobile trust point at step 628. Steps 630-660 may be substantially similar to steps 546-576.

  FIG. 9 shows an example of a method for providing a vehicle security service. This method may be performed by a vehicle trustpoint of the vehicle within the vehicle environment. 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 event (eg, a flash), an audible event (eg, a crash sound), or a movement (eg, a shake or vibration). At step 712, the vehicle environment is recorded and a record is generated. The vehicle environment may be recorded by any suitable device configured to detect visual and / or audio signals, such as a camera or a recorder, for example. At step 714, the record is sent to the center trustpoint.

  At step 716, the center trustpoint saves the record in the database. The stored record can be used as evidence in a trial regarding this security trigger event. At step 718, the center trustpoint sends the record to the mobile trustpoint. The user of the mobile trustpoint can play the recording.

  FIG. 10 illustrates an example of a method for providing an emissions reporting service. This method may be performed by the vehicle trustpoint of the vehicle.

  At step 730, operational data is collected. The operational data may include any suitable data from which emissions can be calculated. For example, the data may include emissions detected from temperature, noise, and exhaust. The operational data may specify emissions that are discharged when only the battery (battery) is operating, only the engine is operating, or both are operating. In certain embodiments, personal data about the user may not be included in the driving data. In other embodiments, personal data may also be included.

  At step 732, operating data is transmitted to the center trustpoint. At step 734, the center trustpoint calculates the vehicle emission value. For example, carbon dioxide emissions can be calculated.

  Modifications, additions, or omissions may be made to the systems and devices disclosed herein without departing from the scope of the present invention. These system and device components may be integrated or may be separate. Also, system and apparatus operations may be performed by more, fewer, or other components. For example, the operations of trustpoint module 132 and service module 134 may be performed by one component, or the operations of module 132 or 134 may be performed by two or more components. Further, system and apparatus operations may be performed using any suitable logic including software, hardware and / or other logic. In this application, “each” means each member of a set or each member of a subset of a set.

  Changes, additions, or omissions may be made to the methods disclosed herein without departing from the scope of the present invention. These methods may include more, fewer, or other steps. The group of steps may be executed in any suitable order.

  In certain embodiments, an entity performing the first step that precedes (eg, connects to) the second step may be considered to facilitate the second step. For example, if an entity performs step A preceding step B, that entity also facilitates step B. In certain embodiments, a first entity that performs a first step preceding a second step that can be performed by a second entity enables the second entity to perform the second step. May be considered to be. For example, if the first entity performs step A preceding step B, which may be performed by the second entity, the first entity also allows the second entity to perform step B.

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

  The logic performs processing of the component, for example, executes an instruction to generate an output from the input. The logic may include hardware, software and / or other logic. The logic can be encoded on one or more tangible media and can perform processing when executed by a computer.

  For example, certain logic such as a processor may manage the operation of the component. The processor may have logic (eg, a device or apparatus) that can interpret and / or execute other logic. Examples of processors include computers, microprocessors, microcontrollers, digital signal processors (DSPs), application specific integrated circuits (ASICs), or configured to interpret and / or execute program instructions and / or processing data. One or more of the other digital or analog circuits are included.

  In certain embodiments, the processes of the embodiments are one or more computer-readable encoded with a computer program, software, computer-executable instructions, and / or other instructions that can be executed by a computer. It can be executed by the medium. In certain embodiments, the processing of the embodiments may be performed by one or more computer-readable media that store a computer program, embodied in a computer program, and / or encoded with a computer program. It may also be executed by one or more computer readable media having a computer program stored and / or encoded.

  Logic such as electronic content (“content”), eg, software (including updates), can be accessed by clients, code (eg, object code or executable code), data records, and / or other electronic The data structure recorded in Examples may include text files, spreadsheets, emails, medical records, images, web pages, programs (eg, word processing programs and file management programs, etc.), and / or other electronic data or programs. .

  The memory stores information. The memory may have one or more non-transitory, tangible, computer readable and / or computer executable storage media. Examples of memory include computer memory (eg, random access memory (RAM), read only memory (ROM), or electrically erasable programmable read only memory (EEPROM)), mass storage media (eg, hard disk), Removable storage media (eg, compact disc (CD) or digital video disc (DVD)), database and / or network storage (eg, server), and / or other computer-readable media, volatile memory, or A non-volatile memory that retains data even when no power is supplied is included.

  The components of the system and apparatus may be coupled by any suitable communication network that communicates according to any suitable communication protocol. A communication network (eg, communication network 18) can be a public switched telephone network (PSTN), a public or private data network, a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a local virtual network. One or more of a private network (VPN), for example a regional or global communications or computer network such as the Internet, a wired or wireless network, a corporate intranet, other suitable communications links, or any combination thereof It can have all or part. The communication network may include any suitable form or configuration of routers, hubs, switches, gateways, call controllers, and / or other suitable elements.

  Although the present disclosure has been described with respect to particular embodiments, modifications and substitutions of these embodiments will be apparent to those skilled in the art. Accordingly, the above description of the embodiments does not limit the present disclosure. Other variations, substitutions, and modifications are possible without departing from the spirit and scope of this disclosure as defined by the appended claims.

Regarding the above description, the following additional notes are disclosed.
(Appendix 1)
One or more interfaces operable to communicate with a plurality of trustpoint systems;
One or more processors,
Establishing trust with the plurality of trustpoint systems by performing user authentication, platform authentication and environment authentication, and communicating information with the plurality of trustpoint systems in response to establishing trust;
A system having one or more processors that operate as follows.
(Appendix 2)
Establishing trust
Appending the trustpoint information from the first trustpoint system to the second trustpoint system to allow the second trustpoint system to authenticate the first trustpoint system. The system according to 1.
(Appendix 3)
Establishing trust
Receiving trustpoint information from a trustpoint system;
The system according to claim 1, further comprising: authenticating the trust point system using the trust point information.
(Appendix 4)
The processor further includes:
A task list having a plurality of tasks is received from a first trustpoint system, and the task list is transmitted to a second trustpoint system to obtain a route for the plurality of tasks and along the route By operating the escort process by instructing the vehicle to move
The system according to appendix 1.
(Appendix 5)
The plurality of trustpoint systems includes a charge trustpoint system;
The processor further includes:
Sending battery information of the battery of the vehicle to the charging trustpoint system and sending settlement information corresponding to the vehicle to the charging trustpoint system, allowing the charging trustpoint system to charge the battery To operate the battery charging process,
The system according to appendix 1.
(Appendix 6)
The processor further includes:
Send a security trigger event on the vehicle,
Record the vehicle environment of the vehicle, generate a record, and send the record to a trustpoint system to operate a vehicle security process;
The system according to appendix 1.
(Appendix 7)
The processor further includes:
Emission reporting process by collecting vehicle driving data and sending the driving data to a trustpoint system, allowing the trustpoint system to calculate one or more emissions of the vehicle Work to run,
The system according to appendix 1.
(Appendix 8)
By the vehicle trustpoint system of the vehicle,
Establishing trust with the first trustpoint system;
Receiving a task list having a plurality of tasks from the first trustpoint system;
Establishing trust with the second trustpoint system;
Obtaining routes for the plurality of tasks from the second trustpoint system;
Instructing the vehicle to travel along the route.
(Appendix 9)
Establishing trust with the first trustpoint system comprises:
Receiving user information obtained from a user by the first trustpoint system;
The method according to claim 8, further comprising the step of authenticating the user according to the user information.
(Appendix 10)
Establishing trust with the first trustpoint system comprises:
Receiving device information from the first trustpoint system;
And authenticating the first trustpoint system according to the device information.
(Appendix 11)
Establishing trust with the second trustpoint system comprises:
The method of claim 8, comprising transmitting vehicle trustpoint information to the second trustpoint system to allow the second trustpoint system to authenticate the vehicle trustpoint system.
(Appendix 12)
Receiving second trustpoint information from the second trustpoint system;
Authenticating the second trustpoint system according to the second trustpoint information;
Sending settlement information to the second trustpoint system;
The method according to appendix 8, further comprising:
(Appendix 13)
By the vehicle trustpoint system of the vehicle,
Authenticating the charging trustpoint system;
Transmitting vehicle trustpoint information to allow the charging trustpoint system to authenticate the vehicle trustpoint system;
Transmitting battery information of the vehicle battery to the charging trustpoint system;
Sending settlement information corresponding to the vehicle to the charging trustpoint system to allow the charging trustpoint system to charge the battery;
Having a method.
(Appendix 14)
Establishing trust with the mobile trustpoint system;
The method according to claim 13, further comprising: receiving the payment information from the mobile trustpoint system.
(Appendix 15)
14. The method of claim 13, further comprising the step of transmitting vehicle trustpoint information to a mobile trustpoint system to allow the mobile trustpoint system to authenticate the vehicle trustpoint system.
(Appendix 16)
14. The method of claim 13, further comprising the step of transmitting an encryption key to a mobile trustpoint system to allow the mobile trustpoint system to encrypt the payment information.
(Appendix 17)
The method according to claim 13, further comprising: displaying a charging status indicating charging of the battery.
(Appendix 18)
14. The method of claim 13, further comprising the step of transmitting a charging status indicative of charging of the battery to a mobile trustpoint system to allow the mobile trustpoint system to display the charging status.
(Appendix 19)
Receiving an encryption key from a trustpoint center;
14. The method of claim 13, further comprising the step of transmitting the encryption key to a mobile trustpoint system to allow the mobile trustpoint system to encrypt the payment information.
(Appendix 20)
By the vehicle trustpoint system for vehicles in the vehicle environment,
Detecting a trigger event on security;
Recording the vehicle environment and generating a record;
Sending the record to a center trustpoint system, allowing the center trustpoint system to send the record to a mobile trustpoint system;
Having a method.
(Appendix 21)
The step of sending the record to the center trustpoint system further comprises:
24. The method of appendix 20, comprising transmitting the record to allow the center trustpoint system to store the record in a database.
(Appendix 22)
By the vehicle trustpoint system of the vehicle,
Collecting operational data;
Sending the operational data to a center trustpoint system to allow the center trustpoint system to calculate one or more emission values for the vehicle;
Having a method.

2 Network 10 Service system 12 Trustpoint system (TPS)
18 Communication network 20 Client system 21 Logic 22 Virtual machine (VM)
24 Virtual Machine Manager (VMM)
26 Trusted Platform Module (TPM)
28 Resource List 30 Client Network 32 Resource 40 GPS Receiver 120 Interface 122 Logic 124 Memory 130 Processor 132 Trust Point Module 134 Service Module 140 User Module 144 Platform Module 148 Environment Module 150 Escort Module 152 Battery Charging Module 154 Vehicle Security Module 156 Emissions Reporting module

Claims (8)

One or more interfaces operable to communicate with a plurality of trustpoint systems;
One or more processors,
Processing for verifying the second trustpoint system using second trustpoint information received from a second trustpoint system of the plurality of trustpoint systems;
Processing for generating trustpoint information including information about the device itself and transmitting the trustpoint information to the second trustpoint system;
A process of verifying the first trustpoint system using first trustpoint information received from a first trustpoint system of the plurality of trustpoint systems;
Processing for generating trustpoint information including information about the device itself and transmitting the trustpoint information to the first trustpoint system;
A result of verifying the second trustpoint system, a response related to the verification received from the second trustpoint system, a result of verifying the first trustpoint system, and received from the first trustpoint system A process of transmitting the first data received from the first trustpoint system to the second trustpoint system when all of the responses regarding the verification to be performed are contents indicating successful verification; One or more processors that perform a process of transmitting second data received from the trustpoint system to the first trustpoint system. The second trustpoint system is a charging trustpoint system;
The processor further transmits battery information of a vehicle battery to the charging trustpoint system, and transmits settlement information corresponding to the vehicle to the charging trustpoint system, and the charging trustpoint system charges the battery. Behaves to perform processing that allows
The system of claim 1 . The processor further performs processing to send a security trigger event for the vehicle to the second trustpoint system, record the vehicle environment of the vehicle, and send the record to the second trustpoint system. The system of claim 1, which operates as follows. The processor further performs a process of collecting vehicle driving data and transmitting the driving data as data used to calculate one or more emissions of the vehicle in the second trustpoint system. The system of claim 1 , wherein the system operates. A method performed by a processor of an apparatus operative to communicate with a plurality of trustpoint systems comprising:
Verifying the second trustpoint system using second trustpoint information received from a second trustpoint system of the plurality of trustpoint systems;
Generating trustpoint information including information about the device and transmitting the trustpoint information to the second trustpoint system;
Verifying the first trustpoint system using first trustpoint information received from a first trustpoint system of the plurality of trustpoint systems;
Generating trustpoint information including information about its own device and transmitting it to the first trustpoint system;
A result of verifying the second trustpoint system, a response related to the verification received from the second trustpoint system, a result of verifying the first trustpoint system, and received from the first trustpoint system If all of the responses regarding the verification to be performed are contents indicating the verification success, the first data received from the first trustpoint system is transmitted to the second trustpoint system, and the second trustpoint system is transmitted. Transmitting second data received from the point system to the first trustpoint system. The second trustpoint system is a charging trustpoint system;
The method further transmits battery information of a vehicle battery to the charging trustpoint system, and transmits settlement information corresponding to the vehicle to the charging trustpoint system, and the charging trustpoint system charges the battery. Having steps that allow
The method of claim 5 . 6. The method of claim 5 , further comprising: sending a security trigger event relating to a vehicle to the second trustpoint system, recording a vehicle environment of the vehicle, and sending the record to the second trustpoint system. The method described. 6. The method of claim 5 , further comprising: collecting vehicle driving data and transmitting the driving data as data used to calculate one or more emissions of the vehicle in the second trustpoint system. the method of.

Images