File transfer manager and edge server for use with a file transfer system for file delivery to ambient internet of things devices

Abstract

The disclosure pertains to a file transfer manager configured to manage file transfer of one or more files for one or more ambient Internet of Things, IoT, devices in a file transfer system comprising at least a first edge server associated with a first activation location area and a second edge server associated with a second activation location area. The file transfer manager may be configured to obtain activation location information for the one or more ambient IoT devices. The file transfer manager may also be configured to initiate transfer, or coordinate transfer, of the one or more files to the first edge server associated with the first activation location area or the second edge server associated with the second activation location area based on the obtained activation location information for the one or more ambient IoT devices. The disclosure also relates to an edge server.

Description

[0001] File transfer manager and edge server for use with a file transfer system for file delivery to ambient Internet of Things devices

[0002] TECHNICAL FIELD

[0003] The present disclosure relates to a file transfer manager and edge server for use with a file transfer system for file delivery to, possibly nomadic, ambient Internet of Things devices. In particular, the disclosure relates to a file transfer manager configured to manage file transfer of one or more files for one or more Internet-of-Things, loT, devices in a file transfer system comprising edge servers and to an edge server of such a file transfer system.

[0004] BACKGROUND

[0005] It is generally known that wireless communication devices need to have delivered files relevant to their operation, such as configuration files, every now and then. In 5G telecommunications systems, mechanisms are applied to update the configuration of a user equipment, UE, including access and mobility related parameters and policies provided by a policy configuration function, PCF. In such systems, the network assumes availability and registration of the UE and transmits a UE Configuration Update, UCU, to the UE.

[0006] SUMMARY

[0007] Ambient Internet-of-Things, loT, devices are low complexity devices. The ambient loT devices may be embodied as a sticker, for example, and attached to a product of interest for inventory or product monitoring purposes. Using ambient loT, products may for example be monitored in a (global) logistic chain, from the source, e.g. a factory, wholesale market, or central logistics center, to their destination (s), e.g. a local distribution center, reseller warehouse(s), business customer(s), or endusers. Ambient loT may also be used, for example, to collect sensor data from large amounts of low cost devices, where replacement of batteries to keep the devices powered is not an option.

[0008] 3GPP Technical Recommendation TR 22.840 is a study on ambient power-enabled loT. The document discloses use cases and requirements for ambient power-enabled loT devices being battery-less devices with limited energy storage capability (a capacitor may be included) wherein the energy is provided through the harvesting of radio waves, light, motion, heat or any other power source that could be suitable. As a consequence, periods during which an ambient loT device is reachable are typically short and / or unpredictable.

[0009] The inventors have realized that mechanisms for file delivery typically applied in 5G telecommunications networks as described above are not feasible for file delivery to ambient loT devices. Ambient loT devices are normally not registered in a telecommunications network and connections to these devices are not reliable because of the energy constraints applicable to these devices. On the other hand, there is a need to deliver files to these devices, such as small files (typically less than a few 100 kB) for the operation of these devices, such as configuration files. The configuration files or updates thereof may include information such as a current owner, a contract reference, a local communication network for these devices, etc. To that end, one aspect of the present disclosure amounts to a file transfer manager configured to manage file transfer of one or more files for one or more ambient Internet of Things, loT, devices in a file transfer system comprising at least a first edge server associated with a first activation location area and a second edge server associated with a second activation location area. The file transfer manager may be configured to obtain activation location information for the one or more ambient loT devices. The file transfer manager may also be configured to initiate transfer, or coordinate transfer, of the one or more files to the first edge server associated with the first activation location area or the second edge server associated with the second activation location area based on the obtained activation location information for the one or more ambient loT devices.

[0010] Another aspect of the disclosure pertains to an edge server for use in a file transfer system managed by a file transfer manager as described herein. The edge server is associated with an activation location area and may be configured to receive and store one or more files to be delivered to one or more ambient loT devices in the activation location area under coordination of the file transfer manager.

[0011] Optionally, the edge server is further configured to initiate activation of the one or more ambient loT devices to deliver the one or more files. Alternatively, or in addition, the edge server may be configured to deliver the one or more files to the one or more ambient loT devices upon indication of activation of the one or more ambient loT devices.

[0012] The activation location awareness of the file transfer manager and the file transfer system of edge servers disclosed herein allow the file manager to select an edge server for deployment of the files close to the location where the ambient loT devices can be active, such that the total transmission time can be reduced and the file can be delivered relatively quickly to many devices when these devices become active for a short period of time. The activation location area indicates an area wherein an ambient loT device is activated or expected to be activated such that the one or more files can actually be delivered to the one or more ambient loT devices from a particular edge server. The activation location information may, for that purpose, comprise or have been construed on the basis of knowledge of activation options in the activation location area, such as the presence of an activation source suitable for the type of ambient loT device (including the telecommunications network itself over which the file is transferred and delivered), a separate electromagnetic radiation source, a heat source, and / or knowledge on motion / vibration of the devices during a particular time interval during which energy is collected. The coordination of the file transfer to one or more edge servers by the file transfer manager enhances file delivery to the one or more ambient loT devices.

[0013] It should be noted that an edge server is understood herein to be a local server storing the one or more files close to the ambient loT devices. The edge server may be a control node or application server deployed in a location near the ambient loT devices. The server may be located in a non-public network deployed in a specific location (e.g. factory, warehouse, harbor, etc.) or may be part of an Edge Enablement Framework (e.g. according to 3GPP TS 23.558 , GSMA Operator Platform Group (GSMA OPG 0.2) or lfedge.org) and accessible via the home or visited PLMN. The edge server may also be an extreme / far edge device or fog computing device providing its resources as part of the edge-cloud continuum in 5G or 6G networks. In one embodiment, the file transfer manager may be configured such that the activation location information for the one or more ambient loT devices is obtained from a pre-set activation location schedule comprising the activation location information for the one or more ambient loT devices in the first activation location area or the second activation location area. The pre-set activation location schedule may be obtained by the file manager as a file from the owner of the ambient loT devices or from the owner of the products to which the ambient loT devices are attached.

[0014] The pre-set activation location schedule enables the file transfer manager to have the future location(s) where the ambient loT device can be activated in advance, so that the one or more file can be transferred to the appropriate edge server(s) in advance. This ensures that when an ambient loT device becomes active, the file(s) for this device is (are) stored closely to the current location of the device so that the delivery time of the file can be relatively short when activated. The stored file may then also be delivered to other ambient loT devices of the same group of ambient loT devices as will be explained in more detail below. Furthermore, the pre-set activation location schedule allows active activation control for the ambient loT devices, for example by sending a radiofrequency signal to energize the devices.

[0015] Optionally, the activation location schedule may further comprise time information associated with the activation location information, wherein the time information associates the activation location information with a time indication when the one or more ambient loT devices are in at least one of the first activation location area and the second activation location area. This facilitates the file transfer manager to schedule file transfer to the appropriate edge server(s) and reduce storage requirements in the edge server(s).

[0016] In one embodiment, the file transfer manager may be configured such that the activation location information for the one or more ambient loT devices is obtained from an activation location function configured to detect the presence of one or more of the one or more ambient loT devices in the first activation location area or the second activation location area when the one or more of the one or more ambient loT devices become active.

[0017] The activation location function enables the file transfer manager to determine the activation location (and time) of the ambient loT devices more accurately, for example in real-time, as compared to a pre-set activation location schedule. In this manner, deviations from a predetermined logistic route, for example, can be detected and the file transfer to the edge servers) can be adapted accordingly.

[0018] The activation location function may be used for a two-step delivery of a file to one or more ambient loT devices. In a first step, when activation of an ambient loT device is detected, the file transfer manager may be triggered to initiate transfer of the file to the edge server determined by the activation location function as having an activation location area accommodating the activated ambient loT device. In a second step, upon another, possibly subsequent, activation, the edge server may deliver the file to the ambient loT device. It should be noted that if the file is for a batch of ambient loT devices in the same activation location area, activation of a single ambient loT device may cause transfer of the file to the edge server for all ambient loT devices (for example, using a group definition accessible to the file transfer manager as will be described in further detail below). These other ambient loT devices of the group may then have the file delivered upon their first activation.

[0019] In one embodiment, the file transfer manager may be configured to initiate transfer of the one or more files to the first edge server associated with the first activation location area based on the obtained activation location information for the one or more ambient loT devices and to determine a change in the activation location information for the one or more ambient loT devices. The change of the activation location information may result from the pre-set activation location schedule indicating that the scheduled location of the ambient loT device(s) has changed (for example a new schedule has become available or a time associated with a previous location in the schedule has expired). Alternatively or in addition, the change of the activation location information may result from application of the activation location function. The file transfer manager may further be configured to initiate transfer of the one or more files to the second edge server associated with the second activation location area based on the change in the activation location information for the one or more ambient loT devices. This transfer may occur either from the first edge server to the second edge server in case communication between these edge servers is efficient or from any other place, such as a storage at or in connection to the file transfer manager.

[0020] The embodiment enables the file transfer function to continue storing the file(s) at an edge server close to the activation location of the ambient loT devices when the ambient loT devices move (for example in a logistic chain) from one activation location area to another, for example, next, activation location area.

[0021] Optionally, the file transfer manager may be configured to transmit a file removal signal to the first edge server associated with the first activation location area.

[0022] In one embodiment, the edge server may be configured to receive a file removal signal from the file transfer manager to remove the one or more files stored at the edge server. The embodiment may be applied to free up storage space at the first location server after the ambient loT devices have left the first activation location area or have been delivered the file(s).

[0023] In one embodiment, the file transfer manager may be configured to receive a file delivery status indication from at least one of the first edge server and the second edge server.

[0024] In one embodiment, the edge server may be configured to track delivery of the one or more files to the ambient loT devices and to transmit a file delivery status indication to the file transfer manager.

[0025] In one embodiment, the edge server may be configured to receive acknowledgement signals transmitted from the one or more ambient loT devices and wherein the edge server is configured to construct the file delivery status indication for transmission to the file transfer manager based on the acknowledgement signals.

[0026] The file delivery status indication may comprise the status of delivery of the file to the ambient loT devices. The file delivery status information may assist the file transfer manager to decide when and / or to which edge server the file needs to be transferred and / or which file(s) is / are to be transferred. For example, when the file is for a group of ambient loT devices, the file delivery status indication may signal that the file was delivered to all devices of the group, so that the file does not need to be transferred to another edge server by the file transfer manager. Optionally, the file transfer manager may be configured to request the file delivery status information from an edge server, such as the edge server to which the file was transferred before. Optionally, the edge server may be configured to transmit the file delivery status information in response to receiving the request. This embodiment enables the file transfer manager to obtain the file delivery status information before it needs to decide on initiation of a transfer to a further edge server. The activation location information available at the file transfer manager may be used to time the request.

[0027] In one embodiment, the file transfer manager may be configured to initiate transfer of one or more of the one or more files previously transferred to the first edge server associated with the first activation location area to the second edge server associated with the second activation location area in response to receiving the file delivery status indication. The embodiment enables the file transfer manager to ensure a progressive delivery of the file to the ambient loT devices, taking care of progressive configuration of the ambient loT devices, for example. For example, when the file is for a group of ambient loT devices, the file delivery status indication may signal to the file transfer manager that the file was not delivered to all devices of the group, so that it is beneficial to transfer the file to a next edge server by the file transfer manager based on the activation location information. Optionally, the transfer initiation of the one or more files to the second edge server is based on the file delivery status indication, i.e. the file delivery status indication may additionally indicate which file(s) should be transferred to the second edge server.

[0028] In one embodiment, the file transfer manager may be configured to initiate transfer of a part of the one or more files previously transferred to the first edge server associated with the first activation location area to the second edge server associated with the second activation location area in response to receiving, and optionally based on, the file delivery status indication. For example, when different files should be delivered to a group of ambient loT devices, the file manager may be informed by the file delivery status indication which files are still needed at the next edge server for delivery to the ambient loT devices.

[0029] In one embodiment, the file transfer manager may be configured to initiate transfer of a different version of the one or more files previously transferred to the first edge server associated with the first activation location area to the second edge server associated with the second activation location area in response to receiving the file delivery status indication. The embodiment enables the file transfer manager to decide on different versions of a file to be transferred, for example based on the activation location information and time. For example, overtime a version of the file may become outdated, and the file manager may determine that a new version of the file should be delivered to the edge server based on the activation location information of the ambient loT devices. For example, when the file transfer manager determines that a new version of the file is available, it may initiate transfer of the new version of the file to the first edge server if the activation location information indicates that the ambient loT devices are (still) in the first activation location area associated with the first edge server.

[0030] In one embodiment, the file transfer manager may be configured to obtain activation location information that the one or more ambient loT devices are within the first activation location area and initiate transfer of the one or more files to the first edge server associated with the first activation location area for delivery to the one or more ambient loT devices. The file transfer manager may further be configured to initiate transfer to the first edge server associated with the first activation location area one or more further files and / or different versions of the one or more files transferred to the first edge server for delivery to the one or more ambient loT devices.

[0031] In one embodiment, the edge server may be configured to deliver multiple files and / or parts of files and / or different versions of files to the one or more ambient loT devices during a location activation period. The location activation period is the total duration of activation of the ambient loT device when in the activation location area. When an ambient loT device is activated multiple times, the location activation period is longer than the period of a single activation.

[0032] The embodiment facilitates delivery of multiple files to the ambient loT devices, for example when the ambient loT devices are activated for relatively long periods of time or relatively frequently when in the first activation location area. The file transfer manager may determine this from the activation location information and / or from a file status delivery signal. For example, when the file status delivery signal indicates that all files have been delivered and the file manager determines from the activation location information that the ambient loT devices are still within the first activation location area, the file transfer manager may initiate transfer of the further files, or versions, to the first edge server to attempt delivery of these files. This may obviate the need to transfer the further files, or versions, to a further edge server.

[0033] In one embodiment, the one or more files may need to be delivered to a plurality of ambient loT devices. In this embodiment, the file transfer manager may be configured to apply the activation location function disclosed herein to determine the first activation location area as the activation location area of activation of at least one of the plurality of ambient loT devices and initiate transfer of the at least one file to the first edge server for the plurality of ambient loT devices. The embodiment allows the file transfer manager to be triggered to initiate transfer of a file for a group of ambient loT devices, so that activation of a single ambient loT device may cause the transfer of the file for the entire group to the edge server, so that other ambient loT devices benefit from the transfer allowing one-step delivery upon their respective activation.

[0034] In one embodiment, the one or more files may need to be delivered to a plurality of ambient loT devices. In this embodiment, the file transfer manager may be configured to obtain a group definition of the plurality of ambient loT devices and to manage file transfer to the at least one of the first edge server and the second edge server in accordance with the group definition. The group definition allows the file transfer manager to initiate transfer of files for a group of ambient loT devices based on the activation location information of only one or just a few ambient loT devices. The group definition may be provided to the file transfer manager by the owner of the ambient loT devices or the owner of the products to which the ambient loT devices are attached, for example. The file transfer manager may also obtain group information from the ambient loT devices themselves, for example as part of the file delivery status indication. This group information may comprise explicit group information stored internally in the ambient loT devices or based on other information, such as device type of application type, that can be used to derive the group. Optionally, the group definition is reconfigurable. This allows initial groupings to be changed along the logistic chain, for example.

[0035] In one embodiment, the at least one file is a file configured to be customized for at least one ambient loT device by the first edge server and / or the second edge server.

[0036] In one embodiment, the edge server may be configured to receive a customizable file under coordination of the file transfer manager. The edge server may be configured to customize the customizable file for the one or more ambient loT devices, wherein, optionally, the edge server applies a customization application received from the file transfer manager.

[0037] The embodiment enables the edge server to set certain parameters, such as a local network indication, in the file logic transferred by the file transfer manager and received by the edge server. Optionally, the file transfer manager may provide a customization application to the edge server to enable adaptation of the file to local settings.

[0038] One further aspect of the disclosure pertains to method for managing file transfer of one or more ambient Internet of Things, loT, devices in a file transfer system comprising at least a first edge server associate with a first activation location area and a second edge server associated with a second activation location area. The method may comprise one or more of the following steps. One step involves the file transfer manager obtaining activation location information for the one or more ambient loT devices. Another step involves the file transfer manager to initiate transfer, or coordinate the transfer, of the one or more file to the first edge server associated with the first activation location area or the second edge server associated with the second activation location area based on the obtained activation location information for the one or more ambient loT device in the previous step.

[0039] Another aspect of the disclosure comprises a computer program product comprising one or more software code portions configured to, when run on a computer system, to perform the method as described in the previous paragraph.

[0040] Yet another aspect of the disclosure involves a method of using an edge server in a file transfer system managed by a file transfer manager, wherein the edge server is associated with an activation location area. The method involves the step of the edge server receiving and storing one or more files to be delivered to one or more ambient loT devices in the activation location area under the coordination of the file transfer manager. One optional further step involves the edge server initiating activation of the one or more ambient loT devices to deliver the one or more files. Alternatively, or in addition, the method may involve a step in the edge server of delivering the one or more files to the one or more ambient loT devices upon indication of activation of the one or more ambient loT devices

[0041] Another aspect of the disclosure comprises a computer program product comprising one or more software code portions configured to, when run on a computer system, to perform the method as described in the previous paragraph.

[0042] A still further aspect of the present disclosure amounts to a file transfer and delivery system comprising a file transfer manager as disclosed herein and one or more edge servers as disclosed herein.

[0043] As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, a method or a computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a "circuit," "module" or "system." Functions described in this disclosure may be implemented as an algorithm executed by a processor / microprocessor of a computer. Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied, e.g., stored, thereon.

[0044] Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a computer readable storage medium may include, but are not limited to, the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of the present invention, a computer readable storage medium may be any tangible medium that can contain, or store, a program for use by or in connection with an instruction execution system, apparatus, or device.

[0045] A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

[0046] Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber, cable, RF, etc., or any suitable combination of the foregoing. Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the person's computer, partly on the person's computer, as a stand-alone software package, partly on the person's computer and partly on a remote computer, or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the person's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0047] Aspects of the present invention are described below with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor, in particular a microprocessor or a central processing unit (CPU), of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer, other programmable data processing apparatus, or other devices create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0048] These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function / act specified in the flowchart and / or block diagram block or blocks.

[0049] The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0050] The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and / or flowchart illustrations, and combinations of blocks in the block diagrams and / or flowchart illustrations, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

[0051] Moreover, a computer program for carrying out the methods described herein, as well as a non- transitory computer readable storage-medium storing the computer program are provided.

[0052] Elements and aspects discussed for or in relation with a particular embodiment may be suitably combined with elements and aspects of other embodiments, unless explicitly stated otherwise. Embodiments of the present invention will be further illustrated with reference to the attached drawings, which schematically will show embodiments according to the invention. It will be understood that the present invention is not in any way restricted to these specific embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] Aspects of the invention will be explained in greater detail by reference to exemplary embodiments shown in the drawings, in which:

[0054] FIG. 1 is a schematic illustration of a file transfer and delivery system comprising a file transfer manager and a plurality of edge servers according to an embodiment of the present disclosure;

[0055] FIGS. 2A-2C are schematic illustrations of a file transfer manager, an edge server and an ambient loT device according to embodiments of the present disclosure;

[0056] FIGS. 3A and 3B are schematic time diagrams illustrating some steps for the file transfer to one or more edge servers and file delivery to one or more ambient loT devices according to embodiments of the present disclosure; and

[0057] FIG. 4 is an example of a processing system according to an embodiment of a file transfer manager or edge server or a part thereof as disclosed herein.

[0058] DETAILED DESCRIPTION OF THE DRAWINGS

[0059] FIG. 1 is a schematic illustration of a file transfer and delivery system 1 comprising a file transfer manager 10 and a plurality of edge servers 20A-20C.

[0060] File transfer manager 10 is connected to a network NW that also connects to a first core network CN1 and a second core network CN2. Core network CN1 is connected to radio access network RAN1 comprising a plurality of base stations BS1 for wireless communication with one or more ambient Internet of Things, loT, devices 30. Core network CN2 is connected to radio access network RAN2 comprising a plurality of base stations BS2 arranged for wireless communication with one or more ambient loT devices 30. It should be noted that file transfer manager 10 may also be comprised in core network CN1 or core network CN2 or any other location suitable for performing its functions as disclosed herein.

[0061] The combination of a core network CN1 or CN2 and radio access network RAN1 resp. RAN2 may constitute a 3GPP compliant telecommunications network. The radio technology used for wireless communication may be especially suitable for activation of and / or communication with ambient loT devices and may be different from New Radio, NR, NarrowBand loT, NBIoT, or LTE-M.

[0062] Core network CN2 is also connected to a plurality of edge servers 20A-20C. The edge servers 20A-20C are local servers located in proximity to the ambient loT devices 30 in an activation location area, abbreviated herein as ALA, i.e. a location area where the ambient loT devices 30 can be activated. The local servers are located in or relatively close to their respective ALA and the ambient loT devices 30 in that ALA, typically located much closer to the ALA, for example, than the file transfer manager 10. In FIG. 1 , edge server 20A is associated with activation location area ALA-A, edge server 20B is associated with activation location area ALA-B and edge server 20C is associated with activation location area ALA-C.

[0063] Edge servers 20A-20C may comprise a local server storing the one or more files close to the ambient loT devices 30. The edge server may be a control node or application server deployed in a location near the ambient loT devices. The server may be located in a non-public network deployed in a specific location (e.g. factory, warehouse, harbor, etc.) or may be part of an Edge Enablement Framework (e.g. according to 3GPP TS 23.558 , GSMA Operator Platform Group (GSMA OPG 0.2) or lfedge.org) and accessible via the home or visited PLMN. The edge server may also be an extreme / far edge device or fog computing device providing its resources as part of the edge-cloud continuum in 5G or 6G networks.

[0064] In FIG. 1 , ambient loT devices 30, which may be attached to products as a sticker, for example, are shown to travel over some geographic distance, for example along a logistics route from a first country (hosting core network CN1) to a second country (hosting core network CN2) as indicated by the dash-dotted arrows in FIG. 1 . As an example, products with ambient loT devices 30 may be transported by ship from the first country and arrive in the harbour of the second country, which harbour area, or a part thereof, is covered by activation location area ALA-A associated with edge server 20A. During the overseas travel, ambient loT devices 30 may have sensed and stored humidity and / or temperature, for example, to record travel conditions of the products during shipment. As soon as the products arrive in the harbour, humidity and temperature during shipment can be verified to ensure that the products were transported under appropriate conditions.

[0065] The products with ambient loT devices 30 may then be moved by road transport to a warehouse in the second country, wherein the warehouse area is covered by activation location area ALA-B associated with edge server 20B. Activation location area ALA-B is shown to have a dedicated activation source DAS configured to activate ambient loT devices 30 by electromagnetic waves (light or RF, for example). One or more of the products with the ambient loT devices 30 may subsequently be transported to a reseller having a shop in activation location area ALA-C associated with the edge server 20C. The ambient loT devices 30 may pass other edge servers during transport that do not have activation location areas ALA, i.e. areas where the ambient loT devices 30 are not (expected) to be activated. Accordingly, such edge servers are not suitable for delivery of a file to the ambient loT devices 30.

[0066] Ambient loT devices 30 may each store one or more files. Such files may typically be small, for example less than 1 Mbyte. Such files may need to be provisioned to or updated on the ambient loT devices 30. In the following, an example of provisioning or updating a configuration file on the ambient loT device or devices will be described. Such a configuration file may contain information regarding ownership of the device 30 or product to which it is attached, data for connecting to a local (public or private) network, address of a database to connect to for uploading sensor data, etc.

[0067] However, providing or updating the configuration of an ambient loT device is more complex than over the air changing of configurations of powered devices, such as mobile phones, since the power received by the ambient loT devices may not be sufficient to store or update the configuration file. Additionally, the number of ambient loT devices 30 may be large and, depending on the use case, multiple ambient loT devices 30 requiring a configuration update may be moving following a similar trajectory. Thus, one or more ambient loT devices 30 might be in a new location when they are receiving power and being activated again, as shown in FIG. 1.

[0068] FIGS. 2A-2C are schematic illustrations of a file transfer manager 10, an edge server 20 and an ambient loT device 30 according to embodiments of the present disclosure. FIG. 2A is a schematic illustration of file transfer manager 10. One embodiment of the file transfer manager is a software program or suite of programs with software code portions configured to execute one or more steps of the file transfer manager defined in the appended claims when run by a computer system. The computer system may be a general purpose computer system or may have one or more hardware components dedicated to perform one or more functions for initiation and / or coordination of file transfer to and / or between edge servers 20A-20C. The software program may be represented by some software modules as depicted in FIG. 2A.

[0069] The file transfer manager 10 may have an activation location information module 11 configured to obtain activation location information for the one or more ambient loT devices 30.

[0070] The file transfer manager 10 may also have a transfer module 12 configured to initiate transfer of the one or more files to a first edge server associated with a first activation location area (e.g. edge server 20A associated with ALA-A in FIG. 1) or the second edge server associated with the second activation location area (e.g. edge server 20B associated with ALA-B in FIG. 1). The transfer may be based on the obtained activation location information for the one or more ambient loT devices 30. The transfer module 12 may also have a timer module to time transfer or initiation of transfer of files to one or more edge servers 20A-20C.

[0071] The file transfer manager 10 may obtain the activation location information by generating this activation location information from received data or may receive the activation location information from an external component, for example as a file with data or activation location information from the owner of the ambient loT devices 30 or the products to which these devices have been attached.

[0072] The activation location information may comprise a pre-set activation location schedule 11A comprising the activation location information for the one or more ambient loT devices 30 in the first activation location area, for example ALA-A, or the second activation location area, for example ALA- B. The pre-set activation location schedule 11A enables the file transfer manager 10 to have the future location(s) where the ambient loT devices 30 can be activated in advance, so that the one or more files can be transferred to the appropriate edge servers) using transfer module 12 in advance. This ensures that when an ambient loT device 30 becomes active, the file(s) for this device may already be stored in relative proximity to the current activation location of the device 30 so that the delivery time of the file can be relatively short when the ambient loT device 30 is activated. The activation location schedule 11 A may further comprise time information associated with the activation location information, wherein the time information associates the activation location information with a time indication when the one or more ambient loT devices 30 are in at least one of the first activation location area and the second activation location area. This facilitates the file transfer manager 10 to schedule file transfer to the appropriate edge server(s) 20A, 20B and / or 20C and reduce storage requirements in the edge server(s).

[0073] Alternatively, or in addition, the file transfer manager 10 may comprise an activation location function 11 B configured to detect the presence of one or more of the one or more ambient loT devices 30 in the first activation location area, ALA-A, or in the second activation location area, ALA-B, when the one or more of the one or more ambient loT devices 30 become active. The activation location function 11 B enables the file transfer manager 10 to determine the activation location (and time) of the ambient loT devices 30 more accurately, for example in real-time. Deviations from a predetermined logistic route can be detected and the file transfer to the edge server(s) can be adapted accordingly, for example.

[0074] The file transfer manager 10 also contains a file removal module 13 instructing one or more of the edge servers 20A-20C to remove a file stored at said edge servers 20A-20C. The file removal module 13 enables to free up storage space at the first location server, for example edge server 20A, after the ambient loT devices 30 have left the first activation location area ALA-A or have been delivered the file(s). The file removal module 13 may become active in response to determining that a time in the pre-set activation location schedule 11 A has expired (for example, the time indicating that ambient loT devices 30 should have left ALA-A) and / or in response to the activation location function 11 B determining that the one or more ambient loT devices 30 have left an activation location area, such as ALA-A.

[0075] File transfer manager 10 may further contain a file delivery status module 14 via which the file transfer manager 10 can be informed of the delivery status of one or more files to the ambient loT devices 30 by the one or more edge servers 20A-20C. The file delivery status information may assist the file transfer manager 10 to decide when and / or to which edge server 20A-20C the file needs to be transferred and / or which file(s) is / are to be transferred. For example, when the file is for a group of ambient loT devices 30, the file delivery status indication may signal that the file was delivered to all devices of the group by edge server 20A, so that the file does not need to be transferred to another edge server 20B-20C.

[0076] The file transfer manager 10, through the file delivery status module 14, may be configured to request the file delivery status information from an edge server 20A-20C, such as sending a request for the edge server 20A to which the file was transferred before. This function enables the file transfer manager 10 to obtain the file delivery status information before it needs to decide on a transfer to a further edge server 20B-20C. The activation location information available at the file transfer manager 10 may be used to time the request.

[0077] The one or more files may need to be delivered to a plurality of ambient loT devices 30. To that end, the file transfer manager 10 may be configured to obtain a group definition 15 of the plurality of ambient loT devices 30 and to manage file transfer to the one or more edge servers 20A-20C in accordance with the group definition 15. The group definition allows the file transfer manager 10 to transfer files for a group of ambient loT devices 30 based on the activation location information of only one or just a few ambient loT devices 30. The group definition 15 may be provided to the file transfer manager 10 by the owner of the ambient loT devices or the owner of the products to which the ambient loT devices 30 are attached, for example. The file transfer manager 10 may also obtain group information from the ambient loT devices 30 themselves, for example as part of the file delivery status indication. This group information may comprise explicit group information stored internally in the ambient loT devices or based on other information, such as device type or application type, that can be used to derive the group. The group definition is reconfigurable. This allows initial groupings to be changed along the logistic chain, for example, when a part of the products to which the ambient loT devices 30 are attached in FIG. 1 is not moved to ALA-C, but to a different location. FIG. 2B is a schematic illustration of an embodiment of an edge server 20, such as edge servers 20A-20C in FIG. 1 , for use in cooperation with the file transfer manager 10. For example, the edge server 20 is associated with an activation location area ALA and may be configured to receive and store one or more files to be delivered to one or more ambient loT devices 30 in the activation location area ALA under coordination of the file transfer manager 10. The edge server 20 may further be configured to initiate activation of the one or more ambient loT devices 30 to deliver the one or more files. Alternatively, or in addition, the edge server 20 may be configured to deliver the one or more files to the one or more ambient loT devices 30 upon indication of activation of the one or more ambient loT devices 30.

[0078] Edge server 20 comprises a communication interface 21 for receiving the one or more files transferred under coordination from the file transfer manager 10 and a communication interface 22 for delivery of the one or more files to ambient loT devices 30 through a network, such as a network comprising base stations BS2 as shown in FIG. 1 , and for receipt of one or more acknowledgement signals from the ambient loT devices 30. Communication interfaces 21 , 22 may be similar or identical interfaces and may be configured as a single interface.

[0079] Furthermore edge server 20 comprises a processing unit 23 and a memory 24 configured to store one or more files for delivery of the one or more files to the ambient loT devices 30. Processing unit 23 is configured to process requests from file transfer manager 10, such as a request to transmit file delivery status information

[0080] FIG. 2C shows a schematic illustration of an embodiment of an ambient loT device 30. The ambient loT device 30 comprises a processing part 31 , a storage part 32 for storing one or more files delivered from edge server 20 upon activation and a transceiver part 33 for wirelessly receiving and transmitting radio signals, including receiving of one or more files and transmission of one or more acknowledgement signals. The device 30 may further comprise a power harvesting part 34 and one or more sensors 35, or connectors therefore. It should be appreciated that device 30 may comprise a plurality of sensors 35 or connectors therefore. Examples of sensors include a location sensor, a temperature sensor, a humidity sensor, a light sensor, a pressure sensor, a motion sensor etc.

[0081] The ambient loT device 30 does not have an internal energy source (a capacitor may be included though) and is required to harvest external power as mentioned above for its activation. The ambient loT device 30 is configured to harvest power to activate at least the processing part 31 and, optionally, the other parts, such as at least one of the storage part 32, transceiver part 33 and sensor 55. Power supply lines to these parts are indicated by the solid lines in FIG. 2C. Signaling lines are indicated by the dashed-dotted lines in FIG. 2C.

[0082] It should be appreciated that ambient loT device 30 as depicted in FIG. 2C may comprise more or fewer parts. Essentially, the ambient loT device 30 is a battery-less device with limited, if any, energy storage capability. In one embodiment, the transceiver part 33 and energy harvesting part 34 may be integrated, at least in part, when the ambient loT device 30 gathers energy from wireless radio transmissions, such as from base stations BS2 or activation source DAS in FIG. 1 .

[0083] FIGS. 3A and 3B provide embodiments of operation of the file transfer manager 10 and edge servers 20A, 20B for delivery of a configuration file to one or more ambient loT devices 30. In FIG. 3A, file delivery manager 10 applies a pre-set activation location schedule 11 A to decide when and to which edge server 20A, 20B the configuration file should be transferred. File transfer manager 10 initiates transfer of the configuration file stored at computer system COMP in step S1 . File manager 10 may run on computer system COMP or on a different computer system.

[0084] In step S2, the configuration file is transferred to edge device 20A at an appropriate time scheduled by pre-set activation location schedule. The time is selected such that the configuration file is stored for delivery to the ambient loT devices 30 before or when the ambient loT devices 30 arrive in the activation location area ALA-A associated with edge server 20A. Furthermore, the pre-set activation location schedule 11 A may also determine that the configuration file is transferred to edge server 20B because it is known from the schedule that the ambient loT devices 30 will be in the activation location area ALA-B associated with the edge server 20B as the next destination. The transfer is shown by step S3.

[0085] When the ambient loT devices arrive in the activation location area ALA-A and are activated, the configuration file may be delivered to some of the ambient loT devices as shown by steps S4.

[0086] Instead of transfer of the configuration file to edge server 20B prior to a delivery attempt of the configuration file from edge server 20A as shown by step S3, file transfer manager 10 may request or wait for file delivery status information, as shown by the dashed arrow S5 from edge server 20A. The file delivery status information may indicate that the configuration file has not been delivered to all ambient loT devices. This may be apparent using group definition 15 as described with reference to FIG. 2A. As a result, as shown by dashed arrows S6 and S7, file transfer manager 10 may determine, using pre-set activation location schedule 11 A, that the configuration file needs to be transferred to edge server 20B.

[0087] Irrespective of when the configuration file is transferred to edge server 20B, step S8 shows delivery of the configuration file from edge server 20B to the remaining ambient loT device 30 when activated in activation location area ALA-B.

[0088] FIG. 3B depicts an embodiment of operation of the file transfer manager 10 and the edge servers 20A, 20B for delivery a configuration file to one or more ambient loT devices 30.

[0089] A group of ambient loT devices 30 has arrived in activation location area ALA-A associated with edge server 20A. The group may be defined at the file manager 10, as described with reference to group definition 15 in FIG. 2A. Activation of an ambient loT device 30 in activation location area ALA-A associated with edge server 20A may be detected in step S10 by file transfer manager 10.

[0090] Activation can be detected when the ambient loT device attempts to register in the core network CN2 (similar to normal UEs), or be based on the ambient loT device sending a message, such a connection-less encrypted message or an activation notification to the network.

[0091] The file transfer manager 10, using the activation location function 11 B, may detect the presence of the ambient loT device 30 in the activation location area ALA-A associated with the edge server 20A. The file transfer manager 10 may determine the activation location area ALA or the area may be determined in the core network CN2. If configured to do so, also edge server 20A may determining the activation location area. From the group definition 15, the file transfer manager may also determine that further ambient loT devices 30 of the group should as well be present in the activation location area ALA-A. The file transfer manager 10 may then initiate transfer of the configuration file to edge server 20A in steps S11 and S12.

[0092] When the ambient loT device 30 of which activation was detected becomes activated again, the configuration file may be delivered from edge server 20A to this ambient loT device 30. The ambient loT device may return an acknowledgement signal indicating delivery of the configuration file to this device. These steps are shown by step S13.

[0093] When other ambient loT devices 30 of the group are also activated (possibly for the first time in ALA-A), the configuration file may also be delivered from edge server 20A, which detects that the configuration file is already present now in edge server 20A, to some of these ambient loT devices 30 that may also return acknowledgement signals. These steps are shown by step S14. It is noted that the ambient loT devices 30 may quickly deactivate again, so that delivery of the configuration file to all ambient loT devices 30 of the group may not be successful.

[0094] In step S15, edge server 20A reports a file delivery status indication to file transfer manager 10 based on the acknowledgement signals received from ambient loT devices 30 in steps S13 and S14. From the file delivery status indication, file transfer manager 10 may determine that the configuration file has not been delivered by edge server 20A to all ambient loT devices 30 of the group.

[0095] The group of ambient loT devices may be transported from ALA-A to ALA-B. Activation of the same or another ambient loT device 30 in ALA-B as the device that was previously first activated in ALA-A may be detected by file transfer manager 10 again in step S16. Activation location function 11 B of file transfer manager 10 may detect the presence of this device in ALA-B as described above and, from the group definition 15 and the file delivery status indication received in step S15, the file transfer manager 10 may conclude that it is necessary to transfer the configuration file to edge server 20B to complete delivery of the configuration file to the remaining ambient loT devices 30 of the group. Steps S17 and S18 illustrate initiation of the transfer from file transfer manager 10 and transfer to edge server 20B respectively.

[0096] Alternatively, as shown by the dashed arrows S19 and S20, file transfer manager 10 may instruct edge server 20A to transfer the configuration file directly to edge server 20B, for example, when such a transfer is more efficient.

[0097] Step S21 indicates transmission of a file removal signal to the edge server 20A associated with the activation location area ALA-A to free up storage space at the edge server 20A.

[0098] When the ambient loT devices 30 are activated in ALA-B, edge server 20B may detect that the configuration file is already present now in edge server 20B so that the configuration file may be delivered from edge server 20B to the remaining ambient loT devices 30 as shown in step S22. Also these devices may transmit acknowledgement signals back to the edge server 20B.

[0099] Edge server 20B may report a file delivery status indication in step S23 to file transfer manager 10 from which the file transfer manager 10 may conclude that transfer of the configuration file to the group has been completed. Accordingly, file transfer manager 10 may transmit a file removal signal back to edge server 20B in step S24.

[0100] The operation in FIGS. 3A and 3B allows for the progressive configuration of a group of ambient loT devices 30 that may become inactive and move to a different area during the configuration process, by transferring the configuration file following their mobility to the closest edge server 20 and resuming the configuration update at the device’s location once they receive energy and become active again. This procedure can be repeated over multiple steps and locations, e.g. also in ALA-C as shown in FIG. 1 , until all the ambient loT devices 30in the group are correctly configured.

[0101] Delivery of the configuration file from the edge server 20 to an ambient loT device may be performed in a variety of ways. One example includes using 5G policy configuration procedure, with the policy download immediately triggered in a local control node (e.g. AMF) by the ambient loT device 30 registering with this node. It is noted that the 5G policy configuration procedure assumes that the ambient loT device 30 is registered. Another example is triggered by the ambient loT device sending a lightweight communication message, with the configuration file from an edge server 20 included in a lightweight communication response message from network to ambient loT device 30. Yet another example includes, when the presence of the group of ambient loT devices 30 is detected in an activation location area ALA, the transfer of a common configuration file may be broadcast securely. This secure broadcast can for example be implemented as described in co-pending patent application EP23213643.2.

[0102] It is noted that embodiments described above may be varied in a number of ways.

[0103] In one embodiment, different configuration file versions might be deployed on the different edge server 20A-20C, for example to provide access to a local network provider. If the trajectory of the ambient loT devices 30 is known in advance, the file transfer manager 10 might plan in advance the deployment of different versions of the configuration file at one or more activation location areas ALA where the ambient loT devices 30 are expected to become active. Additionally, time-based configuration might be enabled by deploying different versions based on the expected time of activation of the ambient loT devices 30 in the same activation location area ALA. In addition to location, and time, the file transfer manager 10 may take additional parameters into consideration for initiating transfer of new or updated different versions of the configuration file on the edge servers 20A-20C that are close to the expected locations of activation for the ambient loT devices 30.

[0104] In a different embodiment, if the group of ambient loT devices 30 is split into multiple subgroups that are taking different trajectories, the file transfer manager 10 may transfer multiple copies of the configuration file to the relevant edge servers 20 associated with activation location areas for each trajectory of each group, with possibly different versions based on location, time, or other parameters as described in the previous embodiments. The file transfer manager 10 may also completely disband the group when the ambient loT devices 30 are not following a similar trajectory anymore.

[0105] The configuration file may be a file that is the same for all ambient loT devices 30 in the group, or may be specific for each of the ambient loT devices 30 in the group. When each of the ambient loT devices 30 needs a specific configuration, the file transfer manager 10 may send a configuration application to an edge server 20. The edge server 20 may then be configured to customize the specific configuration for each ambient loT device 30 in the group based on a common part and device specific parts. When the common part is larger than the device specific part, the total amount of data that has to be sent to the edge server 20 can be reduced this way. To optimize the process of update of configuration and reduce the amount of data transmitted to the ambient loT device 30, the file transfer manager 10 may keep track of the detailed state of the configuration file present in an ambient loT device and instruct the edge server(s) 20 to transmit only the difference in information between new configuration file and the current configuration file stored in the ambient loT device 30 instead of the complete configuration file, for each ambient loT device 30. Thus, different versions of the configurations might be sent to different ambient loT devices 30 in the group depending on the status of their configuration file. This allows to reduce the amount of unnecessarily transmitted data to the ambient loT devices 30, and allows to optimize energy consumption for the ambient loT devices 30.

[0106] In a further embodiment, if the trajectory and the time of activation of the ambient loT devices 30 is known in advance for each step, the file transfer manager 10 might schedule the transfer of more than one configuration file to an edge server 20 associated with an activation location area ALA wherein the ambient loT devices 30 are expected to receive more energy and be active for a longer time, if storage capacity of the edge server 20 would allow this. That way, configuration files can be delivered and stored in advance on the ambient loT devices 30, and applied by these devices by receiving a notification only (in which case the older configuration file or configuration information may also be deleted). This embodiment can be useful for cases where the activation time of the ambient loT devices 30 varies, and can be long at certain location areas but very short at other location areas, which might prevent the delivery of the required configuration data at that time. Those different versions might be sent in form of the differences only as described in the previous embodiment.

[0107] In yet another embodiment, based on the “version” of configuration file stored and / or used by the ambient loT devices 30, and in case it is not possible to update all of the ambient loT devices in a group in a single iteration (e.g. due to insufficient energy), the file transfer manager 10 or the edge server 20 may decide to prioritize performing the update for the ambient loT devices 30 with the oldest configuration versions, or the versions that do not allow them to connect at all, or in case of important security updates, and deprioritize less important updates such as minor configuration optimizations. This information may be stored with the group definition 15 as described with reference to FIG. 2A.

[0108] FIG. 4 depicts a block diagram illustrating an exemplary processing system according to a disclosed embodiment, e.g. a file transfer manager or edge server or a part thereof as described above for use in a system 100. As shown in FIG. 4, the processing system 40 may include at least one processor 41 coupled to memory elements 42 through a system bus 43. As such, the processing system may store program code within memory elements 42. Further, the processor 41 may execute the program code accessed from the memory elements 42 via a system bus 43. In one aspect, the processing system may be implemented as a computer system that is suitable for storing and / or executing program code. It should be appreciated, however, that the processing system 40 may be implemented in the form of any system including a processor and a memory that is capable of performing the functions described within this specification.

[0109] The memory elements 42 may include one or more physical memory devices such as, for example, local memory 44 and one or more bulk storage devices 45. The local memory may refer to random access memory or other non-persistent memory device(s) generally used during actual execution of the program code. A bulk storage device may be implemented as a hard drive or other persistent data storage device. The processing system 40 may also include one or more cache memories (not shown) that provide temporary storage of at least some program code in order to reduce the number of times program code must be retrieved from the bulk storage device 45 during execution.

[0110] Input / output (I / O) devices depicted as an input device 46 and an output device 47 optionally can be coupled to the processing system. Examples of input devices may include, but are not limited to, a space access keyboard, a pointing device such as a mouse, or the like. Examples of output devices may include, but are not limited to, a monitor or a display, speakers, or the like. Input and / or output devices may be coupled to the processing system either directly or through intervening I / O controllers.

[0111] In an embodiment, the input and the output devices may be implemented as a combined input / output device (illustrated in FIG. 4 with a dashed line surrounding the input device 46 and the output device 47). An example of such a combined device is a touch sensitive display, also sometimes referred to as a “touch screen display” or simply “touch screen” that may be provided with the UE. In such an embodiment, input to the device may be provided by a movement of a physical object, such as e.g. a stylus or a finger of a person, on or near the touch screen display.

[0112] A network adapter 48 may also be coupled to the processing system to enable it to become coupled to other systems, computer systems, remote network devices, and / or remote storage devices through intervening private or public networks. The network adapter may comprise a data receiver for receiving data that is transmitted by said systems, devices and / or networks to the processing system 40, and a data transmitter for transmitting data from the processing system 40 to said systems, devices and / or networks. Modems, cable modems, and Ethernet cards are examples of different types of network adapter that may be used with the processing system 40.

[0113] As pictured in FIG. 4, the memory elements 42 may store an application 49. In various embodiments, the application 49 may be stored in the local memory 44, the one or more bulk storage devices 45, or apart from the local memory and the bulk storage devices. It should be appreciated that the processing system 40 may further execute an operating system (not shown in FIG. 4) that can facilitate execution of the application 49. The application 49, being implemented in the form of executable program code, can be executed by the processing system 40, e.g., by the processor 41 . Responsive to executing the application, the processing system 40 may be configured to perform one or more operations or method steps described herein.

[0114] In one aspect of the present invention, one or more components of the base station selection support system and / or user device for use with such a base station selection support system, as disclosed herein may represent processing system 40 as described herein.

[0115] Various embodiments of the invention may be implemented as a program product for use with a computer system, where the program(s) of the program product define functions of the embodiments (including the methods described herein). In one embodiment, the program(s) can be contained on a variety of non-transitory computer-readable storage media, where, as used herein, the expression “non-transitory computer readable storage media” comprises all computer-readable media, with the sole exception being a transitory, propagating signal. In another embodiment, the program(s) can be contained on a variety of transitory computer-readable storage media. Illustrative computer-readable storage media include, but are not limited to: (i) non-writable storage media (e.g., read-only memory devices within a computer such as CD-ROM disks readable by a CD-ROM drive, ROM chips or any type of solid-state non-volatile semiconductor memory) on which information is permanently stored; and (ii) writable storage media (e.g., flash memory, floppy disks within a diskette drive or hard-disk drive or any type of solid-state random-access semiconductor memory) on which alterable information is stored. The computer program may be run on the processor 41 described herein.

[0116] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and / or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0117] The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of embodiments of the present invention has been presented for purposes of illustration but is not intended to be exhaustive or limited to the implementations in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope of the claims. The embodiments were chosen and described in order to best explain the principles and some practical applications of the present invention, and to enable others of ordinary skill in the art to understand the present invention for various embodiments with various modifications as are suited to the particular use contemplated.

Claims

CLAIMS1 . A file transfer manager configured to manage file transfer of one or more files for one or more ambient Internet of Things, loT, devices in a file transfer system comprising at least a first edge server associated with a first activation location area and a second edge server associated with a second activation location area, wherein the file transfer manager is configured to: obtain activation location information for the one or more ambient loT devices; and initiate transfer of the one or more files to the first edge server associated with the first activation location area or the second edge server associated with the second activation location area based on the obtained activation location information for the one or more ambient loT devices.

2. The file transfer manager according to claim 1 , wherein the activation location information for the one more ambient loT devices is obtained from at least one of: a pre-set activation location schedule comprising the activation location information for the one or more ambient loT devices in the first activation location area or the second activation location area, wherein, optionally, the pre-set activation location schedule further comprises time information associated with the activation location information, wherein the time information associates the activation location information with a time indication when the one or more ambient loT devices are in at least one of the first activation location area and the second activation location area; an activation location function configured to detect the presence of one or more of the one or more ambient loT devices in the first activation location area or the second activation location area when the one or more of the one or more ambient loT devices are activated.

3. The file transfer manager according to claim 1 or 2, wherein the file transfer manager is configured to: initiate transfer of the one or more files to the first edge server associated with the first activation location area based on the obtained activation location information for the one or more ambient loT devices; determine a change in the activation location information for the one or more ambient loT devices; initiate transfer of the one or more files to the second edge server associated with the second activation location area based on the change in the activation location information for the one or more ambient loT devices; optionally, transmit a file removal signal to the first edge server associated with the first activation location area.

4. The file transfer manager according to one or more of the preceding claims, wherein the file transfer manager is configured to: receive a file delivery status indication from at least one of the first edge server and the second edge server, wherein the file delivery status information is, optionally, requested from the file transfer manager; initiate transfer of at least a part of the one or more files to at least one of the first edge server or the second edge server in dependence on the file delivery status indication.

5. The file transfer manager according to claim 4, wherein the file transfer manager is configured to at least one of: initiate transfer of one or more of the one or more files previously transferred to the first edge server associated with the first activation location area to the second edge server associated with the second activation location area in response to receiving the file delivery status indication, wherein, optionally, the transfer of the one or more files to the second edge server is based on the file delivery status indication; initiate transfer of a part of the one or more files previously transferred to the first edge server associated with the first activation location area to the second edge server associated with the second activation location area in response to receiving the file delivery status indication, wherein the part transferred to the second edge server is based on the file delivery status indication; initiate transfer of a different version of the one or more files previously transferred to the first edge server associated with the first activation location area to the second edge server associated with the second activation location area in response to receiving the file delivery status indication.

6. The file transfer manager according to one or more of the preceding claims, wherein the file transfer manager is configured to: obtain activation location information that the one or more ambient loT devices are within the first activation location area; initiate transfer of the one or more files to the first edge server associated with the first activation location area for delivery to the one or more ambient loT devices; initiate transfer to the first edge server associated with the first activation location area of one or more further files and / or different versions of the one or more files transferred to the first edge server for delivery to the one or more ambient loT devices.

7. The file transfer manager according to one or more of the preceding claims, wherein the one or more files are for a plurality of ambient loT devices and the file transfer manager is configured to: apply the activation location function according to claim 2 to determine the first activation location area as the activation location area of activation of at least one of the plurality of ambient loT devices; initiate transfer of the at least one file to the first edge server for the plurality of ambient loT devices.

8. The file transfer manager according to one or more of the preceding claims, wherein the one or more files are for a plurality of ambient loT devices and the file transfer manager is configured to obtain a group definition of the plurality of ambient loT devices and manage file transfer to the at least one of the first edge server and the second edge server in accordance with the group definition, wherein, optionally, the group definition is reconfigurable.

9. The file transfer manager according to one or more of the preceding claims, wherein the at least one file is a file, such as a configuration file, configured to be customized for at least one ambient loT device by the first edge server and / or the second edge server, wherein, optionally, the file transfer manager provides a customization application to at least one of the first edge server and the second edge server.

10. An edge server for use in a file transfer system managed by a file transfer manager according to one or more of the preceding claims, wherein the edge server is associated with a activation location area and wherein the edge server is configured to receive and store one or more files to be delivered to one or more ambient loT devices in the activation location area under coordination of the file transfer manager, wherein the edge server is, optionally, further configured to at least one of initiate activation of the one or more ambient loT devices to deliver the one or more files and to deliver the one or more files to the one or more ambient loT devices upon indication of activation of the one or more ambient loT devices.11 . The edge server according to claim 11 , wherein the edge server is configured to receive a file removal signal from the file transfer manager to remove the one or more files stored at the edge server.

12. The edge server according to claim 10 or 11 , wherein the edge server is configured to track delivery of the one or more files to the ambient loT devices and to transmit a file delivery status indication to the file transfer manager, optionally on request of the file transfer manager.

13. The edge server according to claim 12, wherein the edge server is configured to receive acknowledgement signals from the one or more ambient loT devices and wherein the edge server is configured to construct the file delivery status indication for transmission to the file transfer manager based on the acknowledgement signals.

14. The edge server according to one or more of the preceding claims 10-14, wherein the edge server is configured to deliver multiple files and / or parts of files and / or different versions of files to the one or more ambient loT devices during a location activation period.

15. The edge server according to one or more of the preceding claims 10-13, wherein the edge server is configured to receive a customizable file under coordination of the file transfer manager and wherein the edge server is further configured to customize the customizable file for the one or more ambient loT devices, wherein, optionally, the edge server applies a customization application received from the file transfer manager.

Images