Blockchains (smart contracts, distributed ledgers) and rights management broadly construed are the themes of today's Spotlight Applications. Assigned to Hitachi (JP), the first application discloses techniques for managing transactions in a supply chain. Assigned to Cloud Privacy Labs, the second application discloses techniques for context-aware consent management.
20210294914, "Distribution management apparatus, distribution management system, and distribution management method," assigned to Hitachi, Ltd (JP).
A traceability information management server includes: a transaction reception part that receives transaction data from a user client, the transaction data containing information on a completed process in distribution of a product and a concerned party in the completed process; an access right information generation part that generates access right information, the access right information being information on a relation between the completed process, the concerned party in the completed process, and a predetermined access right of the concerned party; an access right determination part that identifies, based on the access right information, information on a process in the distribution to which a sender of the received information provision request from the user client has an access right; and an information transmission part that transmits the identified information on the process to the user client that has sent the information provision request.
20210303705, "Context-aware consent management," assigned to Cloud Privacy Labs, LLC
A consent and privacy preferences management environment (300) includes an application (302) and a Consent Management System (CMS) (304). The CMS (304) stores and processes consent information (306) of an end user (308). The application (302) obtains the consent information and uses the CMS (304) to manage choices of the end users (308) about certain activities, events, or other situations. Third parties (310) use the application (302) to submit requests for consent. The application (302) maps the request into fields of an API (314) for processing by the CMS (304) and receives a response from the CMS (304). The application then provides or denies consent regarding the end user (308) based on the response and filters or masks data based on organizational policies, end user consent, and the context. The data structure of the CMS (304) adapts to a wide variety of consent application environments.