Fujitsu Corporation

Daisuke Mashima

Wei-Peng Chen

Ulrich Herberg

Jorjeta Gueorguieva Jetcheva

Arnab Roy

Gaurav Lahoti

A method of deploying an unmanned aerial vehicle (UAV) operation system may be provided. A method may include estimating an amount of traffic for one or more routes based on a demand of the one or more routes. The method may also include determining a required number of docking stations for each route of the one or more routes based on the estimated amount of traffic for the route, a distance of the route, and a maximum travel distance for a UAV. Further, the method may include installing the required number of docking stations for each route of the one or more routes, wherein each docking station of the required number of docking stations including at least one of a power supply, a wireless charger, a communication module, a control module, and a camera.

Unmanned aerial vehicle operation systems

A method may include receiving peer data describing a set of peer clients associated with a demand response application server and describing how the peer clients communicate with one another. The peer data may be configured so that a subset of the peer clients directly communicate with the demand response application server and the demand response application server does not directly communicate with each of the peer clients. The method may also include receiving announcement data describing an event specified by the demand response application server and determining event response data responsive to the announcement data. The method may also include identifying, from the set of peer clients specified by the demand response application server, a set of recipient peer clients to receive the event response data.

Demand response event dissemination system and method

A method of residential or small and medium business (SMB) demand response (DR) coordination may include receiving a DR event notification from a DR server. The DR event notification may include DR event information pertaining to a DR event and curtailment information. The method may also include communicating a notification acknowledgement to the DR server. The notification acknowledgement may indicate reception of the DR event notification. The method may include displaying a curtailment request pertaining to the DR event. The curtailment request may be based on the curtailment information included in the DR event notification and may include some portion of the DR event information. The method may also include receiving a user input including a DR event participation confirmation or a DR event participation refusal. The method may further include communicating a participation signal representative of at least a portion of the user input to the DR server.

Residential and small and medium business demand response

A method of sharing energy usage data may include requesting customer-specific energy usage data (CSEUD). The method further includes receiving a modified CSEUD record. The modified CSEUD record includes modified energy usage data with respect to original energy usage data of an original CSEUD record from which the modified CSEUD record is derived. The method also includes authenticating the modified CSEUD record to verify the integrity of the modified energy usage data.

Customer-centric energy usage data sharing

A method of energy usage data privacy preservation is described. The method includes downloading energy usage data and a signature from a repository. The method includes determining whether the signature is that of a utility. When the signature is not that of the utility, the method includes rejecting the energy usage data. When the signature is that of the utility, the method includes generating noisy data, encrypting a message-signature pair, constructing a proof, and communicating the noisy data, the encrypted message-signature pair, and the proof to a third party. The noisy data is generated by adding random noise to the energy usage data. The message-signature pair includes the energy usage data and a verified signature. The proof is configured to establish that the encrypted message-signature pair and the noisy data are members of a corresponding proof language.

Trusted and privacy-preserving mechanism for electricity usage data disclosure using verifiable noise

A method including receiving energy usage data representative of energy usage of a customer during a particular time period. The energy usage data is sign with a digital signature of a utility. The method includes receiving input of a customer effective to select a data block of the energy usage data. The method includes redacting the selected data block from the energy usage data in response to the input. The method includes calculating a hash value for the redacted data block using a per-customer key that is unique to the customer, an initialization vector, and a counter. The method includes replacing in the energy usage data the redacted data block with the calculated hash value corresponding to the redacted data block.

Energy usage data management

A method including generating a mapping in response to an enrollment message received from a customer device. The enrollment message includes a device identification number (device ID) of the customer device. The mapping includes a one-time password (OTP) encrypted using the device ID. The method includes generating a quick response (QR) code including a uniform resource locator (URL), a provider certificate (CRT), and certificate signing request (CSR) content. The method includes receiving a confirmation message at a website identified by the URL. The confirmation message includes a generated public key, a CSR, and a decrypted OTP. The method includes verifying the decrypted OTP against the mapping and communicating one or more application configuration settings. The method includes securely communicating information using the one or more application configuration settings, a provider public key, a provider private key, the generated public key, and a generated private key.

Device configuration for secure communication

A method of customer data management in data analytics outsourcing includes communicating to a third party service provider an anonymous customer identifier (customer ID) that is uniquely associated with a customer. The method includes receiving from the third party service provider a customer data query that references the customer using the customer ID and requests customer data. The method includes determining whether an access control policy allows disclosure of customer data requested in the customer data query. In response to the access control policy allowing disclosure of the requested customer data, the method includes accessing the requested customer data and communicating the requested customer data to the third party service provider. In response to the access control policy prohibiting disclosure of the requested customer data, the method includes denying the customer data query.

Customer data management for data analytics outsourcing

A method may include receiving data and first path-metadata. The first path-metadata may include a first entity identifier. The first entity identifier may be associated with a first receiving entity that receives the data and the first path-metadata from an originating entity. The first path-metadata may also include a first digital signature associated with the originating entity. The method may further include receiving second path-metadata that may include the first path-metadata and a second entity identifier associated with a second receiving entity. The second path-metadata may also include a second digital signature associated with the first receiving entity. The method may additionally include verifying that the data was communicated by the originating entity to the first receiving entity and from the first receiving entity to the second receiving entity based on the first path-metadata, the second path-metadata, the first digital signature, and the second digital signature.

Growing community of inventors

Sunnyvale, CA, United States of America

Daisuke Mashima