CONTAINER, METHOD, AND SYSTEM FOR ENABLING OFFLINE ACCESS CONTROL AND FOR ENABLING OFFLINE SENSOR DATA TRANSMISSION

Abstract

In a method and system for opening a container having a lock device, a mobile terminal exchanges data with the lock device using near-field data transmission and exchanges data with a server using far-filed data transmission. The mobile terminal stores container reconfiguration data and container operating data, which include at least time data and access data. The server generates new container reconfiguration data in response to receiving the container operating data from the mobile terminal and transmits the new container reconfiguration data to the mobile terminal using the far-field data transmission. The new container reconfiguration data are then transmitted from the mobile terminal to the lock device using the near-filed transmission.

Claims

1.-15. (canceled)

16. A container comprising: a main body that encloses an accommodating volume in a multi-sided manner, an opening device that is moveable relative to the main body, and a lock device configured to selectively prevent a defined movement of the opening device relative to the main body, the lock device including: a near-field data transmission device configured to receive data from and send data to at least one mobile terminal while the at least one mobile terminal is temporarily located within a defined distance range from the container, a memory unit configured to temporarily store time data and access data, wherein the time data includes a last opening time point and/or a last closing time point, wherein the access data includes at least authorization data and identification data, wherein the authorization data define, in dependence on the identification data, a condition under which the lock device is converted from a closed configuration to an open configuration by the actuator, and wherein the identification data specify an assignment to the at least one mobile terminal, a processor device configured to compare the authorization data and the identification data, an electrically operated actuator that is controllable, in response to a defined match of the compared authorization data and the authorization data, to convert the lock device to the open configuration, and an energy source that supplies operating current to at least the actuator, the near-field data transmission device, the memory unit and the processor device and that is not a commercial AC supply.

17. The container according to claim 16, wherein: the processor device, the memory unit and the near-field data transmission device are designed as components of the lock device and are disposed, in the closed configuration of the container, in an interior of the container.

18. The container according to claim 17, further comprising: at least one temperature sensor disposed in the interior of the container or on a wall of the container, wherein: the temperature sensor is configured to output temperature values or temperature data, and the processor device is configured to store the temperature values in the memory unit in the form of data or to store the temperature data in the memory unit together with the time data and/or the access data.

19. The container according to claim 17, further comprising: at least one humidity sensor disposed inside the container or on a wall of the container, wherein: the humidity sensor is configured to output humidity values or humidity data, and the processor device is configured to store the humidity values in the memory unit in the form of data or to store the humidity data in the memory unit together with the time data and/or the access data.

20. The container according to claim 17, further comprising: at least one weight sensor disposed in or on a wall forming a base of the container, wherein: the weight sensor is configured to output weight values or weight data, and the processor device is configured to store the weight values in the memory unit in the form of data or to store the weight data in the memory unit together with the time data and/or the access data.

21. The container according to claim 17, wherein the processor device energy source is configured to generate energy source data that include one or more of: a remaining charge level of the energy source, an amount of discharge of the energy source over a defined period of time, and/or a change in voltage of the energy source over a defined period of time.

22. The container according to claim 16, wherein: in the closed configuration, the container delimits a volume of less than 10 m.sup.3, walls of the container have a mean wall thickness of less than 30 mm, the opening device has a surface area that is at least 50% of a surface area of one of the walls that extends parallel to the opening device, the walls are composed of a metal, a polymer material or a composite material, the energy source is a battery having a minimum capacity of 1000 mAh, and the near-field data transmission device comprises an RFID, Bluetooth, WLAN, ZigBee and/or Z-Wave data transmission device.

23. A method for opening the container according to claim 16 using the at least one mobile terminal, wherein the at least one mobile terminal includes: a near-field data transmission means configured to exchange data with the near-field data transmission device of the container, a far-field data transmission means configured to exchange data with a server, a processor device configured to execute a control application, and a memory device that stores container reconfiguration data and container operating data, wherein the container operating data include at least time data and access data, the method comprising: transmitting the container operating data from the near-field data transmission means of the lock device to the near-field data transmission means of the at least one mobile terminal, transmitting the container operating data from the far-field data transmission means of the mobile terminal to the server, generating new container reconfiguration data in the server in response to the container operating data received from the at least one mobile terminal, and transmitting the new container reconfiguration data from the server and receiving, in the at least one mobile terminal, the new container reconfiguration data from the server via the near field data transmission means of the at least one mobile terminal.

24. The method according to claim 23, further comprising: sending data and/or sensor signals from at least one sensor in the container to the processor device of the container, and transmitting, from the near-field data transmission device of the lock device, signals and/or data which represent or delineate the sensor data or sensor signals as part of the container operating data to the near-field data transmission means of the at least one mobile terminal.

25. The method according to claim 23, further comprising: sending identification data from the server to the at least one mobile terminal together with the container reconfiguration data or as a separate data record, storing the identification data from the server in the memory device of the at least one mobile terminal, transmitting the identification data from the mobile terminal together with specific device data of the at least one mobile terminal to the near-field data transmission device of the lock device in response to an access authorization request, comparing at least the identification data and the authorization data stored in the memory unit of the lock device, maintaining the lock device in a locked state or converting the lock device to an open state as a function of a comparison result resulting from the comparison.

26. The method according to claim 23, further comprising: causing the processor device of the lock device to store a specific set of container operating data in modified form in the memory unit of the lock device at least after this set of container operating data has been sent to the at least one mobile terminal.

27. The method according to claim 26, wherein: the new container configuration data specify which specific set of container data to be deleted from the memory unit of the lock device and the processor device of the lock device deletes the data from the memory unit of the lock device as a function of the new container reconfiguration data.

28. The method according to claim 27, wherein the container reconfiguration data include authorization data and an instruction to the processor device of the lock device to replace and/or augment the authorization data held in the memory unit of the lock device with authorization data of the container reconfiguration data.

29. A non-transitory computer storage medium comprising computer-readable instructions that, when executed, carry out the method according to claim 23.

30. A system, comprising: a plurality of containers, each of the containers being configured according to the container of claim 16, and a plurality of mobile terminals, each including: a near-field data transmission means configured to exchange data with the near-field data transmission devices of the containers, a far-field data transmission means configured to exchange data with a server, a processor device configured to execute a control application, and a memory device that stores container reconfiguration data and container operating data, and a server, wherein: the container operating data include at least time data and access data, the time data include at least a last opening time point and/or at least a last closing time point, the system is configured such that: the container operating data is transmitted by the near-field data transmission device of the locking device to one of the mobile terminals and is forwarded to the server device; the server device receives the container operating data from the one of the mobile terminals and, after receiving the container operating data, generates new container reconfiguration data and the new container reconfiguration data is sent to: (i) the one of the mobile terminals, (ii) another one of mobile terminals assigned to the container, or (iii) a group of mobile terminals, wherein all of the mobile terminals assigned to the group are assigned to the container.

31. The system according to claim 30, wherein: the container is located outside of a coverage area of a transmission infrastructure, and each of the mobile terminals is configured to transmit the container operating data from the mobile terminal to the server only when the mobile terminal is in the coverage area of the transmission infrastructure.

32. The system according to claim 30, wherein each of the mobile terminals is configured to transmit the container operating data from the mobile terminal to the server in response to a defined triggering event.

33. The method according to claim 23, wherein: the container is located outside of a coverage area of a transmission infrastructure, and the method further comprises transmitting the container operating data from the mobile terminal to the server only when the mobile terminal is again in the coverage area of the transmission infrastructure.

34. The method according to claim 23, wherein: the method further comprises transmitting the container operating data from the mobile terminal to the server in response to a defined triggering event.

35. The method according to claim 25, wherein: the method further comprises actuating the actuator to convert the lock device to the open configuration in response to a defined match of the authorization data and the identification data as determined by the processor device.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0030] FIGS. 1a-1d show, purely schematically, a top view, a bottom view and two side views, respectively, of an example of lock device for a container according to the present teachings, FIGS. 2 and 3 show additional views of the lock device arranged on a wall of a container, and FIGS. 4-6 show respective containers including the lock device;

[0031] FIGS. 7 to 10 show, purely schematically, an example of data transmission in accordance with a method or system according to the present teachings; and

[0032] FIG. 11 shows, purely by way of example, a preferred method sequence according to the present teachings, wherein a single one of or multiple of the steps shown need not be carried out or can also be carried out in a different sequence or also several times.

DETAILED DESCRIPTION OF THE INVENTION

[0033] FIGS. 1a-1d, 2 and 3 schematically show a lock device 10 for preventing a defined relative movement of an opening device 8 with respect to the main body 4.

[0034] The lock device 10 preferably includes an electrically operated (electrically driven) actuator 12.

[0035] Furthermore, at least or precisely one sensor device or a sensor is arranged in the lock device 10.

[0036] The sensor(s) is/are preferably directly installed in the lock unit or lock device 10. Additionally or alternatively, the possibility can exist to connect one or multiple sensors (e.g., further sensor(s)) directly to the lock device 10 via connection cables or a suitable near-field radio technology (then the sensor(s) need its/their own power supply), e.g. to collect sensor data at a more suitable place (e.g., temperature measurements at different places in the box). With some sensors, detection of a property directly in the lock unit is also not possible (e.g., weight sensor is provided separately from the lock device 10 in order to detect the weight of an object placed in the container 1, as will be further described below).

[0037] The container 1 has an interior space and at least one wall that delimits the interior space from the surroundings. The lock device 10 is arranged (disposed) on a wall of the container 1 or on an opening device 8 that is movable relative to the wall, e.g., on a displaceable or pivotable flap, window or door. The side of the lock device 10 that is arranged on the wall is preferably considered to be the outer side of the lock device 10; the side of the lock device 10 that is essentially parallel or opposite thereto is considered to be the inner side. One, multiple or all of the sensors in the lock device 10 are arranged closer to the inner side of the lock device 10 than to the outer side. Thus, between the sensor and/or the sensor device or the sensors and the wall, e.g., the contact point of the lock device with the wall, there is preferably a distance between 3 mm and 50 mm, e.g., between 5 mm and 20 mm or between 8 mm and 18 mm or at least 5 mm or at least 10 mm to the outer wall of the container. This is advantageous because a thermal decoupling (applies e.g., to a temperature sensor 24 and/or a humidity sensor or an air humidity sensor 29) is created.

[0038] There is a possibility that one or more of the sensors is/are provided and/or installed as an analog sensor. An A/D conversion can then preferably be implemented using a corresponding function or device, e.g., the processor device or an A/D converter unit, in the lock unit or in the lock device 10. Additionally or alternatively, a digital sensor or several digital sensors can be provided and/or connected and/or installed. Because one or more such digital sensors already deliver(s) digital measurement parameters, the digital signals from the lock unit can be processed without further conversion.

[0039] One or at least one or more fingerprint sensors can also be connected to the lock device 10, so that people who want to open the container or receptacle 1 can identify themselves with their fingerprint (e.g. for the highest security requirements). In this case, the fingerprint sensor can also or alternatively be located in the mobile terminal 16 and the recorded data can be transmitted to the near-field data transmission device 14 of the lock device 10 via the near-field data transmission means 34 of the mobile terminal 16 for comparison by the processor device 20 of the lock device 10.

[0040] Furthermore, light-emitting diodes (not shown) can be connected to the lock device 10. Additionally or alternatively, e.g., on the outer side of the container 1, different information can be communicated and/or distributed to the outside by using different colors and/or “blink codes”. Additionally or alternatively, there is the possibility of connecting graphic displays to the lock unit. Due to the low power consumption, ePaper or electronic paper are preferably used here. For example, in the event that information is only displayed for a short time, all other conventional display technologies can also be used (esp. LED segment displays, LCD displays and/or graphic LCD or TFT or OLED displays).

[0041] FIG. 2 shows the lock device 10 arranged on an outer wall 26 of the container 1. The lock device 10 preferably has an energy source 22, e.g., a battery, an electronic unit 19, an actuator unit 12 and a bolt 17 that is movable by means of the actuator unit 12, e.g., an electric motor. The electronic unit 19 preferably includes a processor device 20, a memory unit 18, a near-field data transmission means 14, an antenna unit 15 and a sensor device 23. The aforementioned devices of the electronic unit 19 are preferably connected at least indirectly to the processor device 20. The sensor device 23 can include one or more sensors, e.g., a humidity sensor 29 and/or a temperature sensor 24. The sensor device 23 is arranged in the housing of the lock device 10, wherein the lock device 10 preferably has a recess or an opening 11 in the direction of the interior of the container or facing away from the next container wall, which can preferably be open or covered with a membrane. The sensor device 23 is preferably spaced at a distance, which is represented by reference number 25, of at least 2 mm, e.g., at least 4 mm or at least or exactly or up to 5 mm or at least or exactly or up to 8 mm or at least or exactly or up to 10 mm or at least or exactly up to 15 mm, with respect to the outer wall 26 on which the lock device 10 is arranged or formed.

[0042] FIGS. 4 and 5 schematically show different designs of the container 1. According to FIG. 4 (and FIG. 3), the lock device 10 is arranged on the door; the container 1 or the container wall includes a receiving part 5 for receiving the bolt 17 in the closed (locked) configuration or forms it. According to FIG. 5, the door or the opening device 8 forms the receiving part 5 and the lock device 10 is arranged on or in the container wall.

[0043] FIG. 6 shows purely schematically that the container 10 can also be equipped with one sensor or with several sensors, as will be further described below.

[0044] Depending on the size and nature of the container 1, one or more weight sensors 30, 31 may be installed on the bottom of the container 1, e.g., using a “double bottom” so that the weight of a deposited object can be reliably detected, particularly preferably regardless of the shape or size of the object and/or independently of the location in the container 1 at which the object or the object 2 is deposited (placed). The connection of the weight sensor(s) to the lock device, e.g., the signal and/or data-technical coupling with the processor device 20 of the lock device 10, can take place in a wire-connected or circuit board-connected manner or by a suitable near-field radio technology.

[0045] A vibration sensor or multiple vibration sensors, e.g., acceleration sensor(s) 46, can be installed in the container 1, e.g., in the area of the wall, e.g., on the floor, or in the lock device 10. The acceleration sensor(s) 46 record(s) the acceleration values to which the container 1 is exposed (subjected). Furthermore, the container 1 can include a further temperature sensor 240, e.g., in the upper area, i.e. above the center of the container 1, or in the lower area, i.e. below the center of the container 1, or in the area of the center of the container 1. In this context, “in the area of the center” is to be understood in terms of height as +/−10% or +/−20% or +/−30% or +/−40% above and/or below the (vertical) center and/or the vertical middle. The height percentages relate to the maximum height of the accommodation space.

[0046] An air pressure sensor (not shown) or multiple air pressure sensors can be installed in the container 1, e.g., in the area of the wall, e.g., on the floor, or in the lock device 10, which record(s) the air pressure changes to which the container 1 is exposed (subjected). Additionally or alternatively, one or more gas sensors can be provided in the container 1, e.g., in the area of a wall, e.g., on the floor or on the cover of the container 1. These embodiments are advantageous because the environmental conditions in the area of the container 1 can be recorded very precisely thereby, e.g. in transport containers that are transported by aircraft.

[0047] In addition, a motion sensor or different motion sensors can be connected to the lock device 10 in order to e.g.—should the container 1 be designed as a mailbox or like a mailbox—to recognize that an insertion or a placement has taken place. Here, depending on the application, one or more light sensor(s), infrared-, ultrasonic- and/or magnetic field sensors come into consideration here.

[0048] Another type of sensor that comes into consideration would be a humidity sensor or a liquid sensor that is e.g. analogous to the weight sensor(s) for logical reasons to be installed on the bottom of the container 1 in order to determine whether liquids in the container 1 have leaked.

[0049] To determine whether e.g. a mobile transport box has overturned or a prescribed maximum inclination has been exceeded, a gyroscope sensor (gyro instrument) can be coupled to the lock device, e.g., connected, or built into it.

[0050] Furthermore, there is additionally or alternatively the possibility of connecting a GPS receiver to the lock device 10 or of integrating it.

[0051] FIGS. 7 to 10 show, purely schematically, an example of a sequence of a representative method for opening a container 1.

[0052] It can be seen that a container 1, e.g., a protected container without a permanent Internet connection, is provided, wherein the container 1 includes a near-field data communication device (14—see e.g., FIG. 2) and thereby defines a near field communication area 50, as shown in FIG. 7.

[0053] Furthermore, at least one mobile terminal 16 is provided, e.g., a plurality of mobile terminals, e.g., more than 5 per 100 km.sup.2 or more than or up to 10 per 100 km.sup.2 or more than or up to 15 per 100 km.sup.2 or more than or up to 25 per 100 km.sup.2 or more than or up to 50 per 100 km.sup.2 or more than or up to 100 per 100 km.sup.2 or more than or up to 200 per 100 km.sup.2 or more than or up to 500 per 100 km.sup.2.

[0054] The mobile terminal 16 includes a near-field data transmission means 34 for data exchange with the near-field data transmission device 14 of the container 1 and furthermore it preferably includes a particularly preferable wireless far-field data transmission means 36, e.g., GSM, UMTS, LTE, etc., for data exchange with a server 38 within the coverage area 52 of a far-field communication infrastructure.

[0055] Furthermore, according to the representative method, a far-field transmission infrastructure 37, e.g., one or more transmission stations, e.g., transmission towers, is used. The far-field data transmission means 36 sends and preferably receives data at the same time or at different times or sometimes at the same time. The far-field data transmission means 36 receives the received data via the far-field transmission infrastructure 37 that receives data from a server or a server device 38, e.g., a cloud server. The transmitted data are transmitted from the far-field data transmission device 36 to the transmission infrastructure 37 for forwarding to the server 38 or the server device.

[0056] The mobile terminal 16 includes a processor device 40 for executing a control application, and the mobile terminal 16 also has a memory device 42 for storing container reconfiguration data and container operating data. Preferably, all data that is transmitted from the central server unit 38 or the lock unit 10 to the mobile application (16) and (temporarily) stored there is protected from external access by encryption, e.g., by local encryption. This means that neither the user of the application himself/herself nor a third party can directly access the data stored in the mobile application, e.g., not by reading out the physical memory of the mobile device. The encryption method and/or the exact parameters of the encryption are preferably configured centrally by the administrator of the server unit and transmitted from there to the mobile application.

[0057] In FIG. 8 it is schematically depicted that the mobile terminal 16 receives access data from a server 38 or a server device, wherein the access data is transmitted (see communication paths 54, 56) via the transmission infrastructure 37.

[0058] The user rights and/or the lock configurations, and preferably the transmissions of all relevant sensor data or other data from the lock units, is/are managed by one or more operators/administrators.

[0059] In FIG. 9 it is shown schematically that the mobile terminal 16 transmits the access data to the container via the near-field data transmission device (see communication path 58). The container operating data are then transmitted by the near-field data transmission device 14 to the near-field data transmission means 34 of the mobile terminal 16 for forwarding to the server device. It can be seen in a purely schematic manner that the mobile terminal 16 is outside the range of the transmission infrastructure or cannot establish a mobile data connection to the Internet.

[0060] FIG. 10 shows schematically that the mobile terminal 16, as soon as it is back in the coverage area (52) of the transmission infrastructure (37) or as a result of a defined triggering event (only with an existing data connection to the Internet), e.g., a key actuation and/or a location data comparison and/or a time comparison, transmits container operating data to the server or the server device.

[0061] The mobile terminal 16 receives the container reconfiguration data from the server 38 via the far field data transmission means 36, wherein the container reconfiguration data are generated in response to the container operating data transmitted to the server 38 by the near field data transmission means 34. The container operating data include at least time data and access data.

[0062] FIGS. 7 to 10 thus show a method for opening a container 1. Here, the method includes at least the following steps: providing a container 1, providing at least one mobile terminal 16, wherein the mobile terminal 16 includes: a near-field data transmission means 34 for data exchange with the near-field data transmission device 14 of the container 1; a far-field data transmission means 36, e.g., LTE, for data exchange with a server 38; a processor device 40 for executing a control application; and a storage device 42 for storing container reconfiguration data and container operating data. The container operating data are transmitted by the near-field data transmission device 14 to the near-field data transmission means 34 of the mobile terminal 16 to be forwarded to the server device 38 and the mobile terminal 16 receives the container reconfiguration data from the server 38 via the far field data transmission means 36, wherein the container reconfiguration data are generated in response to the container operating data transmitted to the server 38 by means of the near field data transmission means 34 and wherein the container operating data include at least time data and access data.

[0063] FIG. 11 shows a schematic sequence of the representative method according to the present teachings, wherein this sequence includes a large number of additional or alternative steps. Here, the steps S1-S25 shown in FIG. 11 comprise:

[0064] S1. The operator/administrator creates a lock unit having a unique identifier on the central server unit and, if necessary, links it to a lock group.

[0065] S2. The operator/administrator creates a user on the central server unit or provides a defined user group with the option of registering themselves on the central server unit (self service).

[0066] S3. The user loads the necessary software from an app store or another storage location, which is accessible online, onto his/her mobile device (e. g., a smartphone). In principle, this can be done from anywhere in the world.

[0067] S4. The user logs on to the central server unit via his/her app. To do this, he/she uses known access data (as created by the operator/administrator in step 1) or, in the case of the self-service, he/she registers and chooses his/her access data accordingly.

[0068] S5. The central server unit checks whether access rights are available for the user or the group(s) in which the user is assigned to one or more locks or lock groups. If access rights are available, these are transmitted in encrypted form to the mobile unit (as appropriate with any additional information available). The access rights can also be subject to time restrictions. For example, an access right can automatically expire after 24 hours, as long as no further synchronization takes place between the mobile unit and the central server unit during this period.

[0069] With every synchronization between the mobile unit and the central server unit, in addition to the access rights and further information, the system clocks e.g., are compared so that deviations in the clocks can be taken into account.

[0070] S6. The access data and additional information received by the mobile unit are buffered locally in encrypted form in a “virtual key ring”. Here, the mobile unit regularly checks whether an access right still exists and, if necessary, deletes all access rights that have already expired.

[0071] S7. If the user now wants to open a lock unit and his/her mobile unit is within range, then the mobile unit will either establish a connection to the lock unit automatically (in the background) or after manual entry in the mobile unit (“connect button”). The connection between the mobile unit and the lock unit can be further encrypted beyond the encryption included in the transmission standard.

[0072] S8. When the connection to the mobile unit is established, the lock unit transmits a unique identifier to the mobile unit. If necessary, additional information can also be transmitted (e.g. belonging to a specific lock group).

[0073] S9. The mobile unit checks whether access rights exist in the local memory for this lock or the lock group. In this context, a connection to the central server unit is not established.

[0074] S10. If access rights exist, it may be necessary (depending on the configuration by the operator/administrator) that additional keys are required to operate the lock unit (e.g., PIN input, scanning a barcode, etc.) that must be entered in the mobile unit and transmitted to the lock unit. In addition, it may be necessary to establish a connection to the central server unit, as the configuration specifies that the lock is to be opened only when there is a connection between the mobile unit and the central server unit in order to further increase security, since the access rights also are always synchronized between the mobile and central unit via an active connection.

[0075] S11. The mobile unit sends the lock unit (after a positive check) a signal to open and transmits the corresponding key.

[0076] S12. The lock unit checks the key and will store both the connection attempt and the result of the check, as well as all information transmitted about the user or the mobile unit in the internal temporary memory.

[0077] S13. After a positive check, the lock unit releases the locking mechanism and will also store this event in the temporary memory.

[0078] S14. The mobile unit now transmits data to the lock unit that has been linked to the access right in the central server unit. For example, the information that data provided by the lock unit can be received there and can now be deleted locally. However, changes to the local configuration of the lock unit software can also be transferred.

[0079] S15. The lock unit will delete from the local memory the data received from the central unit and will carry out all other necessary operations.

[0080] S16. The deletion and/or the execution of the operations is acknowledged.

[0081] S17. The lock unit now transfers all data from the temporary memory (log data on accesses, access attempts, as well as all stored sensor data to the mobile unit). All data that are already marked for deletion, but the receipt has not yet been confirmed by the central server unit, are also transmitted.

[0082] S18. The mobile unit receives the data from the lock unit and stores it in a protected area. The receipt is acknowledged.

[0083] S19. The lock unit will now mark all transmitted data with additional information (mark it for deletion), but not yet delete it, as it is not yet certain that this data has also been received on the server unit. If necessary, data that has been transmitted multiple times is enriched with additional information.

[0084] S20. The connection between the lock unit and the mobile unit is terminated again.

[0085] S21. The mobile unit will now try to contact the central server unit at the next possible time or at a configured time and to transfer the data transmitted by the lock unit to it.

[0086] S22. As soon as there is a connection between the mobile unit and the central server unit, the data is transmitted and acknowledged by the central server unit.

[0087] S23. The acknowledged data will now be deleted from the temporary memory of the mobile unit.

[0088] S24. The central server unit now updates the access right to the specific lock with the information that the defined data has been received and can be deleted locally (taking into account the information which data has already been deleted by the unit).

[0089] S25. The access right is now synchronized with all mobile units that have access to the specific lock or the associated lock group.

[0090] Thus, a method for asymmetrical or indirect transmission of data between a transmitter and a receiver is disclosed herein.

[0091] For example, sensor data which are collected in places where there is temporarily or permanently no internet connection or no connection to an alternatively suitable transmission network can be transmitted to a central server. Such “offline situations” exist in dead spots, under ground, under water, etc.

[0092] In terms of content, techniques according to the present teachings are preferably based on the method likewise described above for the secure assignment of unique access rights without the use of specialized hardware and without an existing Internet connection. A component here is a mobile application that runs on a device, e.g., a server and/or multiple mobile terminals, which is connected via a mobile data connection to a server device, e.g., a central server, and from which it can receive keys (analogous to the method described above) and can provide them locally.

[0093] If sensor data of an (offline) container is now to be transmitted to the server device 38, e.g., the central server, the mobile device or the mobile terminal 16 must be brought into the vicinity of the container 1 so that the near field transmission means 34 of the mobile terminal 16 can receive raw or processed or partially processed sensor data from one or more sensors arranged on or in the container 1. The sensor data are transmitted via the near-field data transmission device of the container, e.g., of the lock device 10, to the near-field data transmission means 34 of the mobile terminal 16. The sensor is provided or coupled or connected to an electronic device, e.g., the processor device 20, which stores the data made available by the sensor, e.g., in a configurable manner, locally, e.g., in a memory unit 18.

[0094] If the mobile device 16 comes within range of the near-field data transmission device 14, it preferably authenticates itself using the access key for the container 1, e.g., for the processor device 20, and requests the content or defined data of the data held or temporarily stored in the local memory, e.g., time and/or sensor data.

[0095] If the processor device 20 accepts the access and the request, the requested data is transmitted to the mobile device 16 (e.g., via Bluetooth® or NFC). After checking the completeness and correctness of the transmitted data, the mobile terminal 16 preferably sends a delete signal or delete data, which trigger the deletion of at least part of the locally stored or temporarily stored data, e.g., the sensor data and/or time data (temporary memory erased). Otherwise, the transfer is preferably requested again. The same mechanism can also be used to transfer configuration changes to the container and to synchronize the local times (container and mobile device). After the connection has been disconnected, the container 1 and the sensor or sensors arranged or provided therein preferably operate completely independently and collect data until the next access by the mobile application.

[0096] The container data, e.g., the data generated by the sensor(s), can thus be completely transmitted to a central unit, e.g., to the server device 38, even without a permanent Internet connection, by the upstream transmission to a mobile terminal 16. Thus, a method for asymmetrical and/or indirect transmission of data between a transmitter (mobile terminal) and a receiver (container) is provided, wherein after the data has been set up, the mobile terminal also receives data from the container and/or the container sends data to the mobile terminal.

LIST OF REFERENCE SYMBOLS

[0097] 1 Container [0098] 2 Object [0099] 4 Main body [0100] 5 Receiving part [0101] 6 Accommodation volume [0102] 8 Opening device [0103] 10 Lock device [0104] 11 Opening/membrane [0105] 12 Actuator [0106] 14 Near field data transmission device [0107] 15 Antenna unit [0108] 16 Mobile terminal [0109] 17 Bolt [0110] 18 Memory unit [0111] 19 Electronic unit [0112] 20 Processor device [0113] 22 Energy source [0114] 23 Sensor device [0115] 24 Temperature sensor [0116] 25 Distance [0117] 26 Wall of the container [0118] 28 Humidity sensor [0119] 29 Air humidity sensor [0120] 30 Weight sensor [0121] 31 Further weight sensor [0122] 32 Base [0123] 34 Near field data transmission means [0124] 36 Far field communication means [0125] 37 Far-field communication infrastructure [0126] 38 Server or server device [0127] 40 Processor device of the mobile terminal [0128] 42 Storage device [0129] 44 Hole for fastening screw [0130] 46 Accelerometer [0131] 50 Coverage area of the near field communication means of the container [0132] 52 Coverage area of a far-field communication infrastructure [0133] 54 Communication between server and transmission infrastructure [0134] 56 Communication between the transmission infrastructure and the mobile device [0135] 58 Near field communication between near field communication means and near field communication device [0136] 240 Further temperature sensor