in the following description , protocols of lightweight privacy protection , methods , and systems for rfid and sensor based logistics track and trace data sharing over business subcontracting relations are set forth as preferred examples . it will be apparent to those skilled in the art that modifications , including additions and / or substitutions may be made without departing from the scope and spirit of the invention . specific details may be omitted so as not to obscure the invention ; however , the disclosure is written to enable one skilled in the art to practice the teachings herein without undue experimentation . the presently claimed invention discloses a lightweight privacy protection mechanism for logistics enterprises with subcontracting relationships to securely share and efficient query logistics track and trace data collected with auto - id enabled systems . the mechanism comprises a set of protocols for data security control and data sharing , a method and system to implement the protocols . different embodiments of the invention will be described below in detail with reference to the drawings so that those skilled in the art can practice and implement the invention fully or partially . fig1 illustrates one embodiment of the presently claimed invention , a logistics track and trace data management platform in accordance with other embodiments . the system can be implemented in multi - layer architecture , comprising the lowest level auto - id enabled data capturing systems 20 , edge device middleware 50 for managing auto - id devices and processing primitive auto - id data , subcontracting relationship based track and trace management system 60 and the highest level user interfaces . end - users 30 of the system may include consigner and consignee , logistics services providers with subcontracting relationship 302 and public users . the subcontracting relationship based track and trace management system 60 primarily comprises data repository for subcontract management 660 , track and trace data management database 680 , privacy management engine 620 , track and trace data and query processing engine 640 . a typical cross - border logistics scenario is demonstrated in fig2 to show the complexities of logistics operations of shipping goods from a consigner to a consignee . the operations are conducted in two countries : a 220 and b 240 , involving various service providers and logistics operators ( refer to fig3 ). in country a , goods are shipped from the consignee &# 39 ; s warehouse to consolidation centre via truck , followed by container transportation via barge to port terminal . in country b , goods are shipped from port terminal to the consignee &# 39 ; s distribution centre in multi - transportation mode ( e . g . train and truck ). ocean cargo ship is used for the cross - border 260 transportation from country a &# 39 ; s port to country b &# 39 ; s port . as illustrated in fig3 , stakeholders involved in the scenario shown in fig2 mainly include a consigner 301 , logistics service provider and operators 302 , a consignee and the public user 307 . the consigner usually signs an outsourcing contract 400 with a third party logistics provider ( a freight forwarder ) 304 for delivering goods to its customers ( the consignee ). the logistics third party logistics provider 304 then subcontracts 420 individual logistics jobs to specific logistics operators , e . g . local shipper and cargo liner operator . the local shipper can further subcontract 440 its jobs to consolidator , barge operator and customs declaration and clearance agent . these jobs can be subcontracted 460 again to truck carrier and consolidation centre operator by the consolidator . so , hierarchical or networked subcontracting business relationships 306 are established between these involved logistics service provider and logistics operators . at each operation site of the involved participants , auto - id enabled systems and devices are deployed to sense goods ambient data and capture goods movement data . fig4 shows the method of capturing real - time logistics trace and trace data using auto - id enabled systems with privacy control mechanism . at the source point of goods to be delivered , e . g . factory or exporter &# 39 ; s warehouse , rfid tag , sensor or bar code carrying product code information ( e . g . electronic product code ) may be attached to individual items , product boxes , or logistics equipments , e . g . pallets and containers . when the goods are in transit or pass through each logistics operation site equipped with auto - id enabled readers 20 , their location information are recorded by scanning the attached tags or barcodes , and their ambient information ( e . g . humidity and temperature ) are captured by the deployed sensors . auto - id enabled readers 20 include , but not limited to , rfid reader 202 , barcode reader and senor 204 , etc . business information related to the item and product being scanned may need to be storied in and retrieved from enterprise applications 10 . various types of edge device middleware may be utilized for managing the auto - id devices , transforming the raw tag reads into meaningful event and business object data , signing and encrypting the data , and uploading the encrypted data into central track and trace data repository through internet or virtual private network 80 . as shown in fig5 , in one embodiment of current invention , a logistics track and trace system may provide different involved stakeholders , including but not limited to consigner 301 , consignee 303 , prime logistics service provider 304 , sub - contractors 306 , with privacy control and data sharing functions based on business subcontracting relationships through such user interfaces or application service interfaces 600 as : user administration , contract relationship registration and de - registration , location registration and cancellation , traceability query , tracking report and public traceability query . end - users can access the user interfaces with popular web browsers or invoke service interfaces with standard web service protocols through internet or virtual private network 80 . fig6 illustrates major user cases corresponding to embodiments of the presently claimed invention : 1 ) prime enterprise 304 sets up job information to be outsourced to its subcontractors 900 ; 2 ) prime enterprise 304 registers contracting relationship with its subcontractors 910 ; 3 ) subcontractors 306 scan moving logistics objects , equipments , items and products equipped with rfid tags or sensors and upload encrypted monitoring data 920 ; 4 ) prime enterprise 304 queries the execution progress of specified logistics job 930 ; 5 ) public users 307 query the traceability information of the products they consume 940 ; 6 ) prime enterprise 304 de - registers contracting relationships with subcontractors 950 ; 7 ) prime enterprise 304 clears outsourced jobs &# 39 ; information 960 . fig7 describes the protocols which users and systems involved in the user cases described in fig6 use to process and transit messages for uploading , accessing and sharing logistics track and trace data over subcontracting relationship . in the following descriptions , the prime enterprise 304 is denoted as data owner o , its subcontractors 306 as c , jobs outsourced by o to c as j , items identification related to j as id , location where auto - id devices are deployed as l , track and trace controlling points as x , track and trace service platform as p , data capturing system with auto - id devices installed at location l as e . the prime enterprise 304 needs to initialize and set up job information for outsourcing it to subcontractors ( see solid lines in fig7 ). the job information includes the job related item and product ids , auto - id devices locations , track and trace control points etc . first , o sends job and control points &# 39 ; information to p , job and control points &# 39 ; information and item ids to data capturing system e at location l . then , p stores job and control points information into its central data repository 660 . as shown in fig7 in dotted lines , to register a subcontractor to complete a specified job , the prime enterprise 304 first needs to send to p its own identity information , its subcontractor &# 39 ; s identity information , and the subcontracted job - item id pairs , store these information into p &# 39 ; s static data repository 660 and notify the subcontractor c 306 to set up job . data capturing system e can upload captured data into p over secure communication protocols ( see dashed lines in fig7 ). when items and products pass through c &# 39 ; s logistics site l , c scans tags attached on these objects to get id and logistics information written into the tags with fixed or handheld auto - id readers . then , e digitally signs and encrypts the captured data , and sends the signed and encrypted data to p . in the end , p decrypts and verifies the received data , and stores the decrypted data into its dynamic data repository 680 . the prime enterprise and its subcontractors can track the outsourced job &# 39 ; s execution progress or trace back its execution history by enquiring p with user identity information and job identity information ( see dash - dotted lines in fig7 ). p will return the query results in standard report templates . public users and supervision organizations can obtain traceability report of specified items and products by querying p with identification code , such as electronic product code ( see long dashed lines in fig7 ). p will return the query results in standard report templates . as illustrated in fig7 in long - dash - dot - dotted lines , to de - register subcontracting relationship with its subcontractor , the prime enterprise needs to request p to delete the related job - contractor pairs by providing p with its identity information and the specified job information . besides , p needs to update job location and control point information , and to notify c to delete the related job information . e needs to delete the related job - item id pairs . the prime enterprise 304 can request the track and trace service platform p to clear a specified job data by sending to p its user identity information and the information of the job to be cleared ( see long dash - dotted lines in fig7 ). upon receiving clearing request , p will delete the dynamic data related to the job from its repository 680 and notify c to clear the related job data . c will notify data capturing system e to delete the related job - item id pairs . fig8 describes the schematic flowchart and major steps on how to implement the protocols described in fig6 and fig7 in a logistics track and trace platform / system : 1 ) prime enterprise sets up outsourced job information . once the information have been initialized and stored successfully in the static repository of the logistics track and trace platform / system , 2 ) the prime enterprise registers its subcontracting relationship with its subcontractors ; 3 ) the subcontractors can start scanning objects passing through their sites and upload captured event data into the central dynamic data repository . in the mean time , 4 ) the prime enterprise , subcontractors , and public users can query the execution progress of the outsourced job or trace the logistics history of a specified product / item . for terminating subcontracting relationship with its subcontractors , 5 ) the prime enterprise needs to de - register contracting information in the track and trace platform . after the outsourced job is completed , 6 ) the prime enterprise can clear the job data in the logistics track and trace platform and its own enterprise application system . in some embodiments , the present invention includes a computer storage medium having computer instructions or software codes stored therein which can be used to program a computer or microprocessor to perform any of the processes of the presently claimed invention . the storage medium can include , but is not limited to , floppy disks , optical discs , blu - ray disc , dvd , cd - roms , and magneto - optical disks , roms , rams , flash memory devices , or any type of media or device suitable for storing instructions , codes , and / or data . the foregoing description of the presently claimed invention has been provided for the purposes of illustration and description . it is not intended to be exhaustive or to limit the invention to the precise forms disclosed . many modifications and variations will be apparent to the practitioner skilled in the art . the embodiments were chosen and described in order to best explain the principles of the presently claimed invention and its practical application , thereby enabling others skilled in the art to understand the invention for various embodiments and with various modifications that are suited to the particular use contemplated . it is intended that the scope of the presently claimed invention be defined by the following claims and their equivalence .