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

Abstract

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

Description

Technical Field

[0001] This disclosure relates to a file transfer manager and an edge server for use with a file transfer system for file delivery to IoT devices in potentially roaming environments. Specifically, this disclosure relates to a file transfer manager configured to manage file transfers of one or more files from one or more IoT devices within a file transfer system that includes an edge server, and to an edge server for such a file transfer system. Background Technology

[0002] As is well known, wireless communication devices need to periodically deliver documents related to their operation, such as configuration files. In 5G telecommunications systems, application mechanisms are used to update the configuration of User Equipment (UE), including access and mobility-related parameters and policies provided by the Policy Configuration Function (PCF). In such systems, the network assumes the availability and registration of the UE and transmits a UE Configuration Update (UCU) to the UE. Summary of the Invention

[0003] Environmental IoT devices are low-complexity devices. For example, environmental IoT devices can be embodied as tags attached to products of interest for inventory or product monitoring purposes. For instance, using ambient IoT, products can be monitored along a (global) logistics chain from their source (e.g., a factory, wholesale market, or central logistics center) to their destination(s) (e.g., a local distribution center, one or more distributor warehouses, one or more business customers, or end users). Environmental IoT can also be used, for example, to collect sensor data from a large number of low-cost devices where battery replacement to keep the devices powered is not an option.

[0004] 3GPP Technical Recommendation TR 22.840 is a study on ambient power-enabled IoT. This document discloses use cases and requirements for ambient power-enabled IoT devices as battery-free devices with limited energy storage capabilities (which may include capacitors), where energy is provided by harvesting radio waves, light, motion, heat, or any other suitable power source. Therefore, the time periods during which ambient power-enabled IoT devices are typically available are usually short and / or unpredictable.

[0005] The inventors have recognized that file delivery mechanisms commonly used in 5G telecommunications networks, as described above, are not feasible for file transfers to environmental IoT devices. Environmental IoT devices are typically not registered in telecommunications networks, and connections to these devices are unreliable due to energy constraints applicable to them. On the other hand, there is a need to deliver files (e.g., small files used for the operation of these devices, typically less than a few 100 kB), such as configuration files) to these devices. Configuration files or their updates may include information such as the current owner, contract references, and the local communication network of these devices.

[0006] Therefore, one aspect of this disclosure relates to a file transfer manager configured to manage file transfers of one or more files from one or more environmental IoT devices in a file transfer system, the file transfer system including at least a first edge server associated with a first active location area and a second edge server associated with a second active location area. The file transfer manager can be configured to obtain active location information of one or more environmental IoT devices. The file transfer manager can also be configured to initiate or coordinate transfers of one or more files to the first edge server associated with the first active location area or the second edge server associated with the second active location area based on the obtained active location information of the one or more environmental IoT devices.

[0007] Another aspect of this disclosure relates 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 active location area and can be configured to receive and store one or more files to be delivered to one or more environmental IoT devices in the active location area, under the coordination of the file transfer manager.

[0008] Optionally, the edge server is also configured to initiate the activation of the one or more environmental IoT devices to deliver the one or more files. Alternatively or additionally, the edge server may be configured to deliver one or more files to one or more environmental IoT devices upon indicative activation of the one or more environmental IoT devices.

[0009] The file transfer system of the file transfer manager and edge server disclosed herein, with its activation location awareness, allows the file manager to select edge servers to deploy files near locations where environmental IoT devices are likely to be active. This reduces overall transfer time and enables relatively rapid delivery of files to multiple devices when these devices become active within short timeframes. An activation location area represents an area where environmental IoT devices are activated or expected to be activated so that one or more files can be actually delivered from a specific edge server to one or more environmental IoT devices. For this purpose, activation location information may include, or has already been interpreted based on knowledge of activation options within the activation location area (e.g., activation sources suitable for the type of environmental IoT device (including the telecommunications network itself through which files are transmitted and delivered), the presence of individual electromagnetic radiation sources, heat sources) and / or knowledge about the movement / vibration of the device during a specific time interval when energy is harvested. Coordination of file transfers to one or more edge servers by the file transfer manager enhances file delivery to one or more environmental IoT devices.

[0010] It should be noted that, in this document, an edge server is understood as a local server located near an environmental IoT device that stores one or more files. An edge server can be a control node or application server deployed in a location near the environmental IoT device. The server can reside in a non-public network deployed in a specific location (e.g., a factory, warehouse, port, etc.) or can be part of an edge enabling framework (e.g., according to 3GPP TS 23.558, GSMA Operator Platform Group (GSMA OPG 0.2), or lfedge.org) and can be accessed via a home or access PLMN. An edge server can also be an extreme / far-edge device or fog computing device that provides its resources as part of an edge cloud continuum in a 5G or 6G network.

[0011] In one embodiment, the file transfer manager can be configured to obtain activation location information for one or more environmental IoT devices from a preset activation location schedule, which includes activation location information for one or more environmental IoT devices in a first activation location region or a second activation location region. The preset activation location schedule can be obtained by the file manager from the owner of the environmental IoT device or from the owner of a product to which the environmental IoT device is attached.

[0012] The preset activation location schedule enables the file transfer manager to have the future locations of one or more environmental IoT devices that can be activated in advance, allowing one or more files to be transferred to the appropriate edge servers in advance. This ensures that when an environmental IoT device becomes active, the device's files are stored near its current location, allowing for relatively short file delivery times when activated. The stored files can then also be delivered to other environmental IoT devices in the same group, as will be explained in more detail below. Furthermore, the preset activation location schedule allows for proactive activation control of environmental IoT devices, such as stimulating the device by sending radio frequency signals.

[0013] Optionally, the activation location schedule may also include 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 environmental IoT devices are in at least one of the first activation location area and the second activation location area. This facilitates the file transfer manager scheduling file transfers to appropriate edge servers(s) and reduces storage requirements in the edge servers(s).

[0014] In one embodiment, the file transfer manager may be configured to obtain activation location information of one or more environmental IoT devices from an activation location function, which is configured to detect the presence of one or more environmental IoT devices in a first activation location area or a second activation location area when one or more of the one or more environmental IoT devices become active.

[0015] Compared to a preset activation location schedule, the activation location function enables the file transfer manager to more accurately determine the activation location (and time) of environmental IoT devices, for example, in real time. In this way, for example, deviations from a predetermined logistics route can be detected, and file transfers can be adapted accordingly to one or more edge servers(s).

[0016] The Activation Location feature can be used for two-step delivery of files to one or more ambient IoT devices. In the first step, when activation of an ambient IoT device is detected, the File Transfer Manager can be triggered to initiate a file transfer to an edge server, which is determined by the Activation Location feature to have an Activation Location area that accommodates the activated ambient IoT device. In the second step, upon another, and possibly subsequent, activation, the edge server can deliver the file to the ambient IoT device. It should be noted that if the file is for a batch of ambient devices within the same Activation Location area, activation of a single ambient batch device can result in the file being transferred to the edge server for all ambient batch devices (e.g., using a group definition accessible by the File Transfer Manager, as described further below). These other ambient IoT devices in the group can then deliver the file upon their first activation.

[0017] In one embodiment, the file transfer manager can be configured to initiate the transfer of one or more files to a first edge server associated with a first active location area based on active location information obtained from one or more environmental IoT devices, and to determine changes in the active location information of one or more environmental IoT devices. Changes in the active location information may be generated by a preset active location schedule indicating that the scheduled location of one or more environmental preset active location schedules has changed (e.g., a new schedule becomes available or a time associated with a previous location in the schedule has expired). Alternatively or additionally, changes in the active location information may be generated by the application of an active location function. The file transfer manager can also be configured to initiate the transfer of one or more files to a second edge server associated with a second active location area based on changes in the active location information of one or more environmental IoT devices. If communication between the first and second edge servers is effective, such transfer can occur from the first edge server to the second edge server, or from anywhere else, such as at the file transfer manager or a storage device connected to the file transfer manager.

[0018] When an ambient IoT device moves from one active location area (e.g., in a logistics chain) to another active location area, such as the next active location area, this embodiment enables the file transfer function to continue storing (one or more) files at an edge server located close to the active location of the ambient IoT device.

[0019] Optionally, the file transfer manager can be configured to send a file removal signal to a first edge server associated with the first activated location region.

[0020] In one embodiment, the edge server can be configured to receive a file removal signal from a file transfer manager to remove one or more files stored at the edge server. This embodiment can be applied to release storage space at the first location server after an environmental IoT device has left the first active location area or after one or more files(s) have been delivered.

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

[0022] In one embodiment, the edge server may be configured to track the delivery of one or more files to an environmental IoT device and send file delivery status indications to a file transfer manager.

[0023] In one embodiment, the edge server may be configured to receive an acknowledgment signal transmitted from one or more environmental IoT devices, and wherein the edge server is configured to construct a file delivery status indication for transmission to a file transfer manager based on the acknowledgment signal.

[0024] File delivery status indicators can include the delivery status of files to environmental IoT devices. File delivery status information can help the file transfer manager determine when and / or to which edge server files need to be transferred and / or which files(s) need to be transferred. For example, when a file is used for a group of environmental IoT devices, the file delivery status indicator can signal that the file has been delivered to all devices in that group, so that the file does not need to be transferred by the file transfer manager to another edge server.

[0025] Optionally, the file transfer manager can be configured to request file delivery status information from an edge server (e.g., an edge server to which the file was previously transferred). Optionally, the edge server can be configured to transmit the file delivery status information in response to receiving the request. This embodiment allows the file transfer manager to obtain file delivery status information before it needs to decide to initiate a transfer to another edge server. Activation location information available at the file transfer manager can be used to time the request.

[0026] In one embodiment, a file transfer manager can be configured to, in response to receiving a file delivery status indication, initiate the transfer of one or more files previously transferred to a first edge server associated with a first active location region to a second edge server associated with a second active location region. This embodiment enables the file transfer manager to ensure progressive delivery of files to environmental IoT devices, for example, to be responsible for the progressive configuration of environmental IoT devices. For example, when a file is used for a group of environmental IoT devices, the file delivery status indication can signal to the file transfer manager that the file has not been delivered to all devices in that group, making it beneficial for the file transfer manager to transfer the file to the next edge server based on the active location information. Optionally, the initiation of the transfer of one or more files to the second edge server is based on the file delivery status indication, i.e., the file delivery status indication can additionally indicate which files(s) should be delivered to the second edge server.

[0027] In one embodiment, a file transfer manager may be configured to, in response to receiving the file delivery status indication, and optionally based on the file delivery status indication, initiate the transfer of a portion of one or more files previously transferred to a first edge server associated with the first active location region to a second edge server associated with the second active location region. For example, when different files should be delivered to a set of environmental IoT devices, the file manager can be informed via the file delivery status indication which files are still needed at the next edge server for delivery to the environmental IoT devices.

[0028] In one embodiment, a file transfer manager can be configured to, in response to receiving the file delivery status indication, initiate the transfer of different versions of one or more files previously transferred to a first edge server associated with a first active location region to a second edge server associated with a second active location region. This embodiment enables the file transfer manager to determine the different versions of files to transfer, for example, based on active location information and time. For example, over time, a version of a file may become outdated, and the file manager can determine that a new version of the file should be delivered to the edge server based on the active location information of the ambient IoT device. For example, when the file transfer manager determines that a new version of the file is available, if the active location information indicates that the ambient IoT device is (still) in the first active location region associated with the first edge server, it can initiate the transfer of the new version of the file to the first edge server.

[0029] In one embodiment, a file transfer manager may be configured to obtain activation location information of one or more environmental IoT devices located within a first activation location area, and initiate the transfer of one or more files to a first edge server associated with the first activation location area for delivery to one or more environmental IoT devices. The file delivery manager may also be configured to initiate the transfer of one or more additional files and / or different versions of one or more files to the first edge server associated with the first activation location area for delivery to one or more environmental IoT devices.

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

[0031] This embodiment facilitates the delivery of multiple files to an environmental IoT device, for example, when the environmental IoT device is activated for an extended period or is activated relatively frequently while within a first activation location area. The file transfer manager can determine this based on activation location information and / or file status delivery signals. For example, when the file status delivery signal indicates that all files have been delivered, and the file manager determines based on the activation location information that the environmental IoT device is still within the first activation location area, the file transfer manager can initiate a transfer of additional files or versions to a first edge server to attempt to deliver these files. This avoids the need to transfer additional files or versions to a separate edge server.

[0032] In one embodiment, one or more files may need to be delivered to multiple environmental IoT devices. In this embodiment, a file transfer manager can be configured to apply the activation location functionality disclosed herein to determine a first activation location area as the activation location area for at least one of the multiple environmental IoT devices, and initiate the transfer of at least one file to a first edge server for the multiple environmental IoT devices. This embodiment allows the file transfer manager to be triggered to initiate file transfers to a group of environmental IoT devices, such that activation of a single environmental IoT device can cause the entire group of files to be transferred to the edge server, allowing other environmental IoT devices to benefit from the transfer that allows for one-step delivery upon their respective activation.

[0033] In one embodiment, one or more files may need to be delivered to multiple environmental IoT devices. In this embodiment, a file transfer manager can be configured to obtain group definitions for multiple environmental IoT devices and manage file transfers to at least one of a first edge server and a second edge server based on the group definitions. The group definitions allow the file transfer manager to initiate file transfers for a group of environmental IoT devices based on the activation location information of only one or a few environmental IoT devices. For example, the group definitions may be provided to the file transfer manager by the owner of the environmental IoT devices or the owner of the product to which the environmental IoT devices are attached. The file transfer manager may also obtain group information from the environmental IoT devices themselves, for example, as part of a file delivery status indication. This group information may include explicit group information internally stored in the environmental IoT devices or based on other information that can be used to derive the group, such as device type or application type.

[0034] Optionally, the group definition is reconfigurable. For example, this allows the initial grouping to be changed along the logistics chain.

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

[0036] In one embodiment, the edge server can be configured to receive customizable files under the coordination of a file transfer manager. The edge server can be configured to customize customizable files for one or more environmental IoT devices, wherein, optionally, the edge server applies a customized application received from the file transfer manager.

[0037] This embodiment enables the edge server to set certain parameters, such as local network indication, in the file logic transferred by the file transfer manager and received by the edge server. Optionally, the file transfer manager can provide a customized application to the edge server so that the files can be adapted to local settings.

[0038] Another aspect of this disclosure relates to a method for managing file transfers of one or more environmental IoT devices in a file transfer system, said file transfer system including at least a first edge server associated with a first active location area and a second edge server associated with a second active location area. The method may include one or more of the following steps. One step involves a file transfer manager obtaining active location information of one or more environmental IoT devices. Another step involves the file transfer manager initiating or coordinating the transfer of one or more files to the first edge server associated with the first active location area or the second edge server associated with the second active location area, based on the active location information obtained by the one or more environmental IoT devices in the previous step.

[0039] Another aspect of this disclosure includes a computer program product comprising one or more software code portions configured to perform the methods described in the preceding paragraph when run on a computer system.

[0040] Another aspect of this disclosure relates to 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 includes the steps of: the edge server receiving and storing one or more files under the coordination of the file transfer manager, the one or more files being delivered to one or more environmental IoT devices in the activation location area. An optional additional step involves the edge server initiating the activation of one or more environmental IoT devices to deliver the one or more files. Alternatively or additionally, the method may involve the step in the edge server: upon instruction to activate one or more environmental IoT devices, delivering one or more files to one or more environmental IoT devices. Another aspect of this disclosure includes a computer program product comprising one or more software code portions configured to perform the methods described in the preceding paragraph when run on a computer system.

[0041] There are other aspects of this disclosure that are equivalent to file transfer and delivery systems, including file transfer managers as disclosed herein and one or more edge servers as disclosed herein.

[0042] As those skilled in the art will appreciate, aspects of the invention can be embodied as systems, methods, or computer program products. Therefore, aspects of the invention can take the form of entirely hardware embodiments, entirely software embodiments (including firmware, resident software, microcode, etc.), or embodiments combining software and hardware aspects, all of which are generally referred to herein as “circuit,” “module,” or “system.” The functionality described in this disclosure can be implemented as algorithms executed by a computer’s processor / microprocessor. Furthermore, aspects of the invention can take the form of computer program products embodied in one or more computer-readable media, on which computer-readable program code is embodied (e.g., stored).

[0043] Any combination of one or more computer-readable media may be used. A computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. A computer-readable storage medium can be, for example, but not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or apparatuses, or any suitable combination of the foregoing. More specific examples of computer-readable storage media include, but are not limited to, electrical connections having one or more wires, portable computer floppy disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In the context of this invention, a computer-readable storage medium can be any tangible medium capable of containing or storing a program for use by or in conjunction with an instruction execution system, device, or apparatus.

[0044] Computer-readable signal media may include propagated data signals in which computer-readable program code is embodied, for example, in baseband or as part of a carrier wave. Such propagated signals may take any of a variety of forms, including, but not limited to, electromagnetic, optical, or any suitable combination thereof. Computer-readable signal media may be any computer-readable medium that is not a computer-readable storage medium and is capable of conveying, propagating, or transmitting a program for use by or in conjunction with an instruction execution system, device, or apparatus.

[0045] Program code embodied on a computer-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, fiber optic, cable, RF, or any suitable combination of the foregoing. Computer program code used to carry out aspects of the invention may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" programming language or similar programming languages. The program code may be executed entirely on a personal computer, partially on a personal computer, as a standalone software package, partially on a personal computer and partially on a remote computer, or entirely on a remote computer or server. In the latter case, the remote computer may be connected to the personal computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet provided by an Internet service provider).

[0046] Aspects of the 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 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 can be provided to a processor (particularly a microprocessor or 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, executable via the processor of the computer, other programmable data processing apparatus, or other means, create components for implementing the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams.

[0047] These computer program instructions may also be stored in a computer-readable medium capable of directing a computer, other programmable data processing apparatus or other means to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of writing comprising instructions that implement the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0048] Computer program instructions may also be loaded onto a computer, other programmable data processing apparatus or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device, thereby producing a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide a process for implementing the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0049] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code comprising one or more executable instructions for implementing one or more specified logical functions. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two blocks shown consecutively may actually be executed substantially simultaneously, or these blocks may sometimes be executed in reverse order, depending on the functionality involved. It will also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented by a system based on dedicated hardware, or a combination of dedicated hardware and computer instructions, that performs the specified functions or actions.

[0050] In addition, a computer program for implementing the methods described herein and a non-transitory computer-readable storage medium for storing the computer program are provided.

[0051] Elements and aspects discussed with respect to a particular embodiment or with respect to a particular embodiment may be suitably combined with elements and aspects of other embodiments, unless otherwise expressly stated. Embodiments of the invention will be further described with reference to the accompanying drawings, which will schematically illustrate embodiments according to the invention. It will be understood that the invention is by no means limited to these specific embodiments. Attached Figure Description

[0052] Aspects of the invention will be explained in more detail with reference to exemplary embodiments shown in the accompanying drawings, in which: Figure 1 This is a schematic diagram of a file transfer and delivery system including a file transfer manager and multiple edge servers according to an embodiment of the present disclosure; Figure 2A-2C This is a schematic diagram of a file transfer manager, an edge server, and an environmental IoT device according to embodiments of the present disclosure; Figure 3A and 3B The following is a schematic timing diagram illustrating some steps of file transfer to one or more edge servers and file delivery to one or more environmental IoT devices according to embodiments of the present disclosure; and Figure 4 Examples of processing systems based on embodiments of a file transfer manager or edge server or a portion thereof as disclosed herein. Detailed Implementation

[0053] Figure 1 This is a schematic diagram of a file transfer and delivery system 1 that includes a file transfer manager 10 and multiple edge servers 20A-20C.

[0054] File transfer manager 10 is connected to network NW, which is also connected to a first core network CN1 and a second core network CN2. Core network CN1 is connected to radio access network RAN1, which includes multiple base stations BS1 for wireless communication with one or more environmental IoT devices 30. Core network CN2 is connected to radio access network RAN2, which includes multiple base stations BS2 arranged for wireless communication with one or more environmental IoT devices 30. It should be noted that file transfer manager 10 may also be included in core network CN1 or core network CN2, or in any other location suitable for performing its functions as disclosed herein.

[0055] A combination of core network CN1 or CN2 and radio access network RAN1 and / or RAN2 can constitute a 3GPP-compliant telecommunications network. The radio technology used for wireless communication may be particularly well-suited for activating and / or communicating with environmental IoT devices, and may differ from new radio (NR), narrowband IoT (NBIoT), or LTE-M. The core network CN2 is also connected to multiple edge servers 20A-20C. Edge servers 20A-20C are local servers located near the environmental IoT devices 30 within an activation location area (abbreviated herein as ALA, i.e., the location area where the environmental IoT devices 30 can be activated). The local servers are located at or relatively close to their respective ALAs and the environmental IoT devices 30 within those ALAs, typically closer to the ALA than the file transfer manager 10 is positioned within. Figure 1 In this context, edge server 20A is associated with the active location region ALA-A, edge server 20B is associated with the active location region ALA-B, and edge server 20C is associated with the active location region ALA-C.

[0056] Edge servers 20A-20C may include local servers located near the environmental IoT device 30, storing one or more files. The edge server may be a control node or application server deployed in a location near the environmental IoT device. The server may be located in a non-public network deployed in a specific location (e.g., a factory, warehouse, port, etc.) or may be part of an edge enabling framework (e.g., according to 3GPP TS 23.558, GSMA Operator Platform Group (GSMA OPG0.2), or lfedge.org) and may be accessed via a home or access PLMN. The edge server may also be an extreme / far-edge device or fog computing device providing its resources as part of an edge cloud continuum in a 5G or 6G network.

[0057] exist Figure 1 In this context, for example, an environmental IoT device 30, which can be attached as a tag to a product, is shown traveling a certain geographical distance, such as along a logistics route from a first country (hosting core network CN1) to a second country (hosting core network CN2), as by... Figure 1 As indicated by the dashed arrow. As an example, a product equipped with an environmental IoT device 30 can be transported from a first country by ship to a port in a second country, the port area or a portion thereof being covered by an active location area ALA-A associated with edge server 20A. During the overseas journey, the environmental IoT device 30 may have sensed and stored, for example, humidity and / or temperature, to record the product's travel conditions during transit. Once the product arrives at the port, the humidity and temperature during transit can be verified to ensure the product was transported under appropriate conditions.

[0058] Products equipped with environmental IoT devices 30 can then be transported by road to a warehouse in a second country, where the warehouse area is covered by an activation location area ALA-B associated with edge server 20B. Activation location area ALA-B is shown as having a dedicated activation source DAS configured to activate environmental IoT devices 30 via electromagnetic waves (e.g., light or RF). One or more of the products equipped with environmental IoT devices 30 can then be transported to a distributor with a store in activation location area ALA-C associated with edge server 20C. Environmental IoT devices 30 may pass through other edge servers during transport that do not have activation location areas ALA, i.e., areas where environmental IoT devices 30 are not (intended) to be activated. Therefore, such edge servers are not suitable for delivering documents to environmental IoT devices 30.

[0059] Environmental IoT devices 30 may each store one or more files. Such files are typically small, for example, less than 1 megabyte. Such files may need to be provided to or updated on environmental IoT devices 30. Examples of providing or updating configuration files on one or more environmental IoT devices are described below. Such configuration files may contain information about ownership of device 30 or products attached to it, data for connecting to a local (public or private) network, addresses of databases connected to for uploading sensor data, etc.

[0060] However, configuring or updating the configuration of environmental IoT devices is more complex than changing the configuration of electrically powered devices (such as mobile phones) via radio, because the power received by the environmental IoT devices may be insufficient to store or update configuration profiles. Furthermore, the number of environmental IoT devices 30 can be large, and depending on usage, multiple environmental IoT devices 30 requiring configuration updates may move along similar trajectories. Therefore, as... Figure 1 As shown, when one or more environmental IoT devices 30 receive power and are reactivated, they may be in a new location.

[0061] Figure 2A-2C This is a schematic diagram of a file transfer manager 10, an edge server 20, and an environmental IoT device 30 according to embodiments of the present disclosure.

[0062] Figure 2AThis is a schematic diagram of a file transfer manager 10. One embodiment of the file transfer manager is a software program or program suite having a software code portion configured to execute one or more steps of the file transfer manager as defined in the appended claims when run by a computer system. The computer system may be a general-purpose computer system, or it may have one or more hardware components dedicated to performing one or more functions for initiating and / or coordinating file transfers to and / or between edge servers 20A-20C. Figure 2A It is represented by some software modules described in the document.

[0063] The file transfer manager 10 may have an activation location information module 11, which is configured to obtain activation location information of one or more environmental IoT devices 30.

[0064] The file transfer manager 10 may also include a transfer module 12, which is configured to initiate the transfer of one or more files to a first edge server (e.g., with) associated with a first active location region. Figure 1 The edge server 20A associated with ALA-A in the middle) or the second edge server associated with the second active location area (e.g., with Figure 1 The transmission can be based on the activation location information obtained from one or more environmental IoT devices 30. The transmission module 12 may also have a timer module for timing the transmission of files to or the initiation of transmissions to one or more edge servers 20A-20C.

[0065] The file transfer manager 10 can obtain the activation location information by generating it from the received data, or by receiving it from an external component, such as a file containing data or activation location information from the owner of the environmental IoT device 30 or products to which these devices are attached.

[0066] The activation location information may include a preset activation location schedule 11A, which includes activation location information for one or more environmental IoT devices 30 in a first activation location area (e.g., ALA-A) or a second activation location area (e.g., ALA-B). The preset activation location schedule 11A allows the file transfer manager 10 to have future(one or more) locations where the environmental IoT devices 30 can be activated in advance, enabling the transfer module 12 to transfer one or more files to appropriate(one or more) edge servers in advance. This ensures that when the environmental IoT device 30 becomes active, the device(s) may already have their files stored relatively close to the current activation location of the device 30, allowing for relatively short file delivery times when the environmental IoT device 30 is activated. The activation location schedule 11A may also include time information associated with the activation location information, wherein the time information associates the activation location information with a time indication when one or more environmental IoT devices 30 are in at least one of the first and second activation location areas. This facilitates the file transfer manager 10 in scheduling file transfers to appropriate(one or more) edge servers 20A, 20B, and / or 20C, and reduces storage requirements in the edge servers(s).

[0067] Alternatively or additionally, the file transfer manager 10 may include an activation location function 11B, configured to detect the presence of one or more environmental IoT devices 30 in a first activation location region ALA-A or a second activation location region ALA-B when one or more of the environmental IoT devices 30 become active. The activation location function 11B enables the file transfer manager 10 to determine the activation location (and time) of the environmental IoT devices 30 more accurately (e.g., in real-time). For example, deviations from a predetermined logical route can be detected, and file transfers to the edge server can be adapted accordingly.

[0068] The file transfer manager 10 also includes a file removal module 13, which instructs one or more of the edge servers 20A-20C to remove files stored at the edge servers 20A-20C. The file removal module 13 enables the release of storage space at the first location server (e.g., edge server 20A) after the ambient IoT device 30 has left the first active location area ALA-A or has delivered (one or more) files. The file removal module 13 may become active in response to determining that a time in a preset active location timetable 11A has expired (e.g., a time indicating that the ambient IoT device 30 should have left ALA-A) and / or in response to the active location function 11B determining that one or more ambient IoT devices 30 have left the active location area (e.g., ALA-A). The file transfer manager 10 may also include a file delivery status module 14, through which the file transfer manager 10 can be informed of the delivery status of one or more files to the environmental IoT devices 30 by one or more edge servers 20A-20C. The file delivery status information helps the file transfer manager 10 determine when and / or to which edge servers 20A-20C a file needs to be delivered and / or which files(s) need to be delivered. For example, when a file is used for a group of environmental IoT devices 30, the file delivery status indicator can signal that the file has already been delivered by edge server 20A to all devices in that group, so that the file does not need to be transferred to another edge server 20B-20C.

[0069] Through the file delivery status module 14, the file transfer manager 10 can be configured to request file delivery status information from edge servers 20A-20C, such as sending a request for a file previously transferred to edge server 20A. This functionality allows the file transfer manager 10 to obtain file delivery status information before it needs to decide on a transfer to another edge server 20B-20C. The activation location information available at the file transfer manager 10 can be used to time the requests.

[0070] One or more files may need to be delivered to multiple environmental IoT devices 30. For this purpose, the file transfer manager 10 can be configured to obtain a group definition 15 for the multiple environmental IoT devices 30 and manage file transfers to one or more edge servers 20A-20C based on the group definition 15. The group definition allows the file transfer manager 10 to transfer files for a group of environmental IoT devices 30 based on the active location information of only one or a few of the environmental IoT devices 30. For example, the group definition 15 may be provided to the file transfer manager 10 by the owner of the environmental IoT device or the owner of the product to which the environmental IoT device 30 is attached. The file transfer manager 10 can also obtain group information from the environmental IoT device 30 itself, for example, as part of a file delivery status indication. This group information may include explicit group information internally stored in the environmental IoT device or based on other information that can be used to derive the group, such as device type or application type. The group definition is reconfigurable. This allows the initial grouping to change along the logistics chain, for example, when... Figure 1 When a portion of the product attached to the IoT device 30 in the environment does not move to ALA-C, but instead moves to a different location.

[0071] Figure 2B It is an edge server 20 used in conjunction with the file transfer manager 10 (e.g., Figure 1The diagram illustrates an embodiment of an edge server (20A-20C). For example, edge server 20 is associated with an activation location area ALA and can be configured to receive and store one or more files to be delivered to one or more environmental IoT devices 30 in the activation location area ALA, under the coordination of file transfer manager 10. Edge server 20 can also be configured to initiate the activation of one or more environmental IoT devices 30 to deliver one or more files. Alternatively or additionally, edge server 20 can be configured to deliver one or more files to one or more environmental IoT devices 30 upon indication of activation of one or more environmental IoT devices 30.

[0072] Edge server 20 includes: a communication interface 21 for receiving one or more files transferred under the coordination of file transfer manager 10; and a communication interface 22 for communicating over a network (e.g., including...). Figure 1 The network of base station BS2 shown delivers one or more files to environmental IoT device 30 and receives one or more acknowledgment signals from environmental IoT device 30. Communication interfaces 21 and 22 can be similar or identical interfaces and can be configured as a single interface.

[0073] Furthermore, the edge server 20 includes a processing unit 23 and a memory 24, which is configured to store one or more files for delivery of one or more files to the environmental IoT device 30. The processing unit 23 is configured to process requests from the file transfer manager 10, such as requests to transmit file delivery status information. Figure 2C A schematic diagram illustrating an embodiment of an environmental IoT device 30 is shown. The environmental IoT device 30 includes a processing section 31, a storage section 32, and a transceiver section 33. The storage section 32 stores one or more files delivered from an edge server 20 upon activation. The transceiver section 33 wirelessly receives and transmits radio signals, including receiving one or more files and transmitting one or more acknowledgment signals. The device 30 may also include a power acquisition section 34 and one or more sensors 35, or therefore include a connector. It should be understood that the device 30 may include multiple sensors 35 or therefore include a connector. Examples of sensors include position sensors, temperature sensors, humidity sensors, light sensors, pressure sensors, motion sensors, etc.

[0074] The environmental IoT device 30 does not have an internal power source (but may include a capacitor) and requires external power, as described above, for its activation. The environmental IoT device 30 is configured to acquire power to at least activate the processing section 31, and optionally activate other sections, such as at least one of the storage section 32, transceiver section 33, and sensor 55. Power supply lines to these sections are provided by… Figure 2C The solid lines in the diagram represent signal lines. Figure 2C The dotted lines in the text represent...

[0075] It should be understood, such as Figure 2C The environmental IoT device 30 depicted may include more or fewer components. Essentially, the environmental IoT device 30 is a battery-free device with limited (if any) energy storage capacity. In one embodiment, when the environmental IoT device 30 receives energy from sources such as… Figure 1 When collecting energy in radio transmissions such as base station BS2 or active source DAS, the transceiver section 33 and the energy harvesting section 34 can be at least partially integrated.

[0076] Figure 3A and 3B An embodiment is provided showing how a file transfer manager 10 and edge servers 20A, 20B deliver configuration files to one or more environmental IoT devices 30.

[0077] exist Figure 3A In step S1, the file transfer manager 10 uses a preset activation location schedule 11A to determine when the configuration file should be transferred and to which edge servers 20A and 20B it should be transferred to. In step S1, the file transfer manager 10 initiates the transfer of the configuration file stored on the computer system COMP. The file transfer manager 10 can run on the computer system COMP or on a different computer system.

[0078] In step S2, the configuration file is transmitted to edge device 20A at an appropriate time scheduled by a preset activation location schedule. This time is chosen such that the configuration file is stored and delivered to environmental IoT device 30 before or at the time of its arrival in the activation location area ALA-A associated with edge server 20A. Furthermore, the preset activation location schedule 11A also determines that the configuration file is transmitted to edge server 20B because the schedule indicates that environmental IoT device 30 will be in the activation location area ALA-B associated with edge server 20B as its next destination. This transmission is illustrated in step S3.

[0079] When an environmental IoT device arrives at the activation location area ALA-A and is activated, a profile may be delivered to some of the environmental IoT devices, as shown in step S4.

[0080] File transfer manager 10 can request or wait for file delivery status information, as indicated by the dashed arrow S5 from edge server 20A, instead of transferring the configuration file to edge server 20B before delivery attempts from edge server 20A are made, as shown in step S3. The file delivery status information can indicate that the configuration file has not been delivered to all IoT devices in the environment. (Using reference...) Figure 2A The group definition 15 described is probably obvious. As a result, as shown by dashed arrows S6 and S7, the file transfer manager 10 can use a preset activation location schedule 11A to determine which configuration files need to be transferred to the edge server 20B.

[0081] Regardless of when the configuration file is transmitted to the edge server 20B, step S8 shows that when activated in the activation location area ALA-B, the configuration file is delivered from the edge server 20B to the remaining environmental IoT devices 30.

[0082] Figure 3B An embodiment depicts the operation of file transfer manager 10 and edge servers 20A, 20B delivering configuration files to one or more environmental IoT devices 30.

[0083] A group of environmental IoT devices 30 has arrived at the activation location region ALA-A associated with the edge server 20A. This group can be defined at the file manager 10, as shown in the reference. Figure 2A As described in group definition 15. In step S10, the activation of the environmental IoT device 30 in the activation location area ALA-A associated with the edge server 20A can be detected by the file transfer manager 10.

[0084] Activation can be detected when an ambient IoT device attempts to register in the core network CN2 (similar to a regular UE), or when the ambient IoT device sends a message to the network, such as a connectionless encrypted message or activation notification.

[0085] Using the Activated Location function 11B, the File Transfer Manager 10 can detect the presence of environmental IoT devices 30 in the Activated Location Area ALA-A associated with the Edge Server 20A. The File Transfer Manager 10 can determine the Activated Location Area ALA, or it can determine the area within the core network CN2. If configured to do so, the Edge Server 20A can also determine the Activated Location Area. Based on group definition 15, the File Transfer Manager can also determine that other environmental IoT devices 30 in the group should also be present in the Activated Location Area ALA-A. Then, in steps S11 and S12, the File Transfer Manager 10 can initiate a transfer of a configuration file to the Edge Server 20A.

[0086] When the environmental IoT device 30 (activated by detection) is reactivated, a configuration file can be delivered from the edge server 20A to the environmental IoT device 30. The environmental IoT device can return an acknowledgment signal indicating that the configuration file has been delivered to the device. These steps are illustrated in step S13.

[0087] When other environmental IoT devices 30 in the group are also activated (possibly for the first time in ALA-A), the configuration file can also be delivered from the edge server 20A to some of these environmental IoT devices 30. The edge server 20A detects that the configuration file is now present in the edge server 20A, and these environmental IoT devices 30 can also return an acknowledgment signal. These steps are illustrated in step S14. Note that the environmental IoT devices 30 may quickly deactivate again, causing the delivery of the configuration file to all environmental IoT devices 30 in the group to fail.

[0088] In step S15, the edge server 20A reports a file delivery status indication to the file transfer manager 10 based on the acknowledgment signals received from the environmental IoT devices 30 in steps S13 and S14. Based on the file delivery status indication, the file transfer manager 10 can determine that the configuration file has not been delivered by the edge server 20A to all environmental IoT devices 30 in that group.

[0089] The group of environmental IoT devices can be transported from ALA-A to ALA-B. In step S16, the file transfer manager 10 can again detect the activation of either the same device or another environmental IoT device 30 that was first activated in ALA-A. The activation location function 11B of the file transfer manager 10 can detect the presence of the device in ALA-B as described above, and based on the group definition 15 and file delivery status indication received in step S15, the file transfer manager 10 can infer that it is necessary to transfer the configuration file to the edge server 20B to complete the delivery of the configuration file to the remaining environmental IoT devices 30 in the group. Steps S17 and S18 respectively illustrate initiating the transfer from the file transfer manager 10 and the transfer to the edge server 20B.

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

[0091] Step S21 instructs the transmission of a file removal signal to the edge server 20A associated with the active location region ALA-A, in order to free up storage space at the edge server 20A.

[0092] When the ambient IoT device 30 is activated in ALA-B, the edge server 20B can detect that the configuration file now exists in the edge server 20B, allowing the configuration file to be delivered from the edge server 20B to the remaining ambient IoT devices 30, as shown in step S22. These devices can also transmit an acknowledgment signal back to the edge server 20B.

[0093] In step S23, edge server 20B can report a file delivery status indication to file transfer manager 10, which file transfer manager 10 can use to infer that the transfer of the configuration file to the group has been completed. Therefore, in step S24, file transfer manager 10 can send a file removal signal back to edge server 20B.

[0094] Figure 3A and 3B The operation allows for the progressive configuration of a group of environmental IoT devices 30 that may become inactive and move to different areas by transmitting their moved configuration profiles to the nearest edge server 20 during the configuration process, and resuming configuration updates at the device location once the device receives power and becomes active again. This procedure can be repeated through multiple steps and locations, for example, also... Figure 1 Repeat ALA-C as shown until all environmental IoT devices 30 in the group are correctly configured.

[0095] The delivery of a configuration file from edge server 20 to an environmental IoT device can be performed in several ways. One example includes using a 5G policy configuration procedure, where the environmental IoT device 30, registered with a local control node (e.g., AMF), immediately triggers a policy download at that node. Note that the 5G policy configuration procedure assumes that the environmental IoT device 30 is already registered. Another example is triggered by the environmental IoT device sending a lightweight communication message, where the configuration file from edge server 20 is included in a lightweight communication response message from the network to the environmental IoT device 30. Yet another example includes the secure broadcasting of a public configuration file when the presence of a group of environmental IoT devices 30 is detected in an active location area (ALA). This secure broadcast can be implemented, for example, as described in co-pending patent application EP23213643.2.

[0096] Note that the above embodiments can be varied in many ways.

[0097] In one embodiment, different configuration file versions may be deployed on different edge servers 20A-20C, for example, to provide access to a local network provider. If the trajectory of the ambient IoT device 30 is known in advance, the file transfer manager 10 can pre-plan the deployment of different versions of the configuration file at one or more activation location areas (ALAs) where the ambient IoT device 30 is expected to become active. Furthermore, time-based configuration can be achieved by deploying different versions based on the expected time of activation of the ambient IoT device 30 in the same activation location area (ALA). In addition to location and time, the file transfer manager 10 may also consider additional parameters for initiating the transfer of new or updated versions of the configuration file on edge servers 20A-20C, which are located near the expected activation location of the ambient IoT device 30.

[0098] In different embodiments, if the group of environmental IoT devices 30 is divided into multiple subgroups taking different trajectories, the file transfer manager 10 can transfer multiple copies of the configuration file to the relevant edge server 20 associated with the activation location area of ​​each trajectory for each group, which may have different versions based on location, time, or other parameters as described in the preceding embodiments. The file transfer manager 10 can also completely disband the group when the environmental IoT devices 30 no longer follow similar trajectories.

[0099] The configuration file can be the same file for all environmental IoT devices 30 in the group, or it can be a file specific to each environmental IoT device 30 in the group. When each environmental IoT device 30 requires a specific configuration, the file transfer manager 10 can send a configuration request to the edge server 20. The edge server 20 can then be configured to customize a specific configuration for each environmental IoT device 30 in the group based on a common portion and a device-specific portion. When the common portion is larger than the device-specific portion, the total amount of data that must be sent to the edge server 20 can be reduced in this way.

[0100] To optimize the configuration update process and reduce the amount of data transmitted to the environmental IoT device 30, the file transfer manager 10 can track the detailed status of the configuration files present in the environmental IoT device and instruct one or more edge servers 20 to transmit only the information difference between the new configuration file and the current configuration file stored in the environmental IoT device 30 for each environmental IoT device 30, rather than the complete configuration file. Therefore, different versions of the configuration can be sent to different environmental IoT devices 30 in the group based on the status of their configuration files. This allows for a reduction in the amount of unnecessary data transmitted to the environmental IoT device 30 and allows for optimization of the energy consumption of the environmental IoT device 30.

[0101] In another embodiment, if the activation trajectory and time of the ambient IoT device 30 are known in advance for each step, the file transfer manager 10 can arrange to transfer more than one configuration file to the edge server 20 associated with the activation location region ALA, wherein the ambient IoT device 30 is expected to receive more energy and be active for a longer period of time if the storage capacity of the edge server 20 will allow it. In this way, the configuration files can be pre-delivered and stored on the ambient IoT device 30, and applied by these devices by simply receiving notifications (in which case, older configuration files or configuration information can also be deleted). This embodiment is useful where the activation time of the ambient IoT device 30 varies, and may be long in some location regions but short in others, which may prevent the delivery of the required configuration data at that time. Those different versions can be sent only in a differentiated form, as described in the coil embodiment.

[0102] In yet another embodiment, based on the "version" of the configuration file stored and / or used by the environmental IoT device 30, and if it is impossible to update all environmental IoT devices in a group in a single iteration (e.g., due to insufficient power), the file transfer manager 10 or the edge server 20 may decide to prioritize updating environmental IoT devices 30 with the oldest configuration version or those that are not allowed to connect at all, or in the case of important security updates, and de-prioritize less important updates, such as minor configuration optimizations. (See reference...) Figure 2A This information can be stored together with group definition 15.

[0103] Figure 4 The diagram depicts a block diagram of an exemplary processing system according to a disclosed embodiment, such as a file transfer manager or edge server, or a portion thereof, as described above for use in system 100. Figure 4 As shown, the processing system 40 may include at least one processor 41 coupled to the memory element 42 via a system bus 43. Therefore, the processing system can store program code within the memory element 42. Furthermore, the processor 41 can execute program code accessed from the memory element 42 via the system bus 43. In one aspect, the processing system may be implemented as a computer system suitable for storing and / or executing program code. However, it should be understood that the processing system 40 may be implemented in the form of any system including a processor and memory capable of performing the functions described herein.

[0104] Memory element 42 may include one or more physical memory devices, such as, for example, local memory 44 and one or more mass storage devices 45. Local memory may refer to random access memory or one or more other non-persistent memory devices that are typically used during the actual execution of the program code. Mass storage devices may be implemented as hard disk drives or other persistent data storage devices. Processing system 40 may also include one or more cache memories (not shown) that provide temporary storage for at least some program code to reduce the number of times program code must be retrieved from mass storage device 45 during execution.

[0105] The input / output (I / O) devices, depicted as input device 46 and output device 47, may optionally be coupled to the processing system. Examples of input devices include, but are not limited to, a spatial access keyboard, a pointing device such as a mouse, etc. Examples of output devices include, but are not limited to, a monitor or display, a speaker, etc. The input and / or output devices may be coupled to the processing system directly or via an intermediate I / O controller.

[0106] In embodiments, the input device and the output device may be implemented as a combined input / output device (in... Figure 4 (Seen in the diagram with dashed lines surrounding input device 46 and output device 47). An example of such a combined device is a touch-sensitive display, sometimes referred to as a "touchscreen display" or simply a "touchscreen," which may be equipped with a UE. In such embodiments, input to the device may be provided by the movement of a physical object, such as a stylus or a human finger, on or near the touchscreen display.

[0107] Network adapter 48 may also be coupled to the processing system to enable it to couple to other systems, computer systems, remote network devices, and / or remote storage devices via an intermediate private or public network. The network adapter may include a data receiver for receiving data transmitted to the processing system 40 by the systems, devices, and / or networks, and a data transmitter for transmitting data from the processing system 40 to the systems, devices, and / or networks. Modems, cable modems, and Ethernet cards are examples of different types of network adapters that can be used with the processing system 40.

[0108] like Figure 4 As depicted, memory element 42 can store application 49. In various embodiments, application 49 may be stored in local memory 44, one or more mass storage devices 45, or separately from local memory and mass storage devices. It should be understood that processing system 40 may also execute an operating system (not shown in the original text) that facilitates the execution of application 49. Figure 4(As shown in the figure). The application 49, implemented in the form of executable program code, can be executed by the processing system 40 (e.g., by the processor 41). In response to executing the application, the processing system 40 can be configured to perform one or more operational or method steps described herein.

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

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

[0111] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the invention. As used herein, the singular forms “a” (“a”, “an”) and “described” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that, when used in this specification, the terms “comprises” and / or “comprising” 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.

[0112] All components or steps plus functional elements in the following claims are intended to include corresponding structures, materials, actions, and equivalents for performing functions in combination with other claimed elements as expressly claimed. The description of embodiments of the invention is presented for illustrative purposes and is not intended to be exhaustive or limited to implementations of the disclosed forms. Many modifications and variations will be apparent to those skilled in the art without departing from the scope of the claims. These embodiments were chosen and described in order to best explain the principles of the invention and some practical applications, and to enable others skilled in the art to understand the invention with respect to various embodiments having various modifications suitable for the particular intended use.

Claims

1. A file transfer manager configured to manage file transfers of one or more files from one or more environmental Internet of Things (IoT) devices in a file transfer system, said file transfer system comprising at least a first edge server associated with a first active location region and a second edge server associated with a second active location region, wherein said file transfer manager is configured to: Obtain the activation location information of the one or more environmental IoT devices; and Based on the activation location information obtained from the one or more environmental IoT devices, the system initiates the transfer of the one or more files to the first edge server associated with the first activation location region or the second edge server associated with the second activation location region.

2. The file transfer manager according to claim 1, wherein, The activation location information of the one or more environmental IoT devices is obtained from at least one of the following: A preset activation location timetable includes activation location information of the one or more environmental IoT devices in the first activation location area or the second activation location area. Optionally, the preset activation location timetable also includes 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 environmental IoT devices are in at least one of the first activation location area and the second activation location area. An activation location function is configured to detect the presence of one or more of the environmental IoT devices in a first activation location area or a second activation location area when one or more of the environmental IoT devices are activated.

3. The file transfer manager according to claim 1 or 2, wherein, The file transfer manager is configured to: Based on the activation location information obtained from the one or more environmental IoT devices, initiate the transmission of the one or more files to the first edge server associated with the first activation location area; Determine the changes in the activation location information of the one or more environmental IoT devices; Based on the change in the activation location information of the one or more environmental IoT devices, initiate the transfer of the one or more files to the second edge server associated with the second activation location region; Optionally, a file removal signal is transmitted to the first edge server associated with the first activated location region.

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; Based on the file delivery status indication, initiate the transfer of at least a portion of the one or more files to at least one of the first edge server or the second edge server.

5. The file transfer manager according to claim 4, wherein, The file transfer manager is configured to be at least one of the following: In response to receiving the file delivery status indication, an initiation is made to transfer one or more of the one or more files previously transferred to the first edge server associated with the first active location region to the second edge server associated with the second active location region, wherein, optionally, the transfer of the one or more files to the second edge server is based on the file delivery status indication; In response to receiving the file delivery status indication, a portion of one or more files previously transferred to the first edge server associated with the first active location region is initiated to be transferred to the second edge server associated with the second active location region, wherein the portion transferred to the second edge server is based on the file delivery status indication; In response to receiving the file delivery status indication, a different version of the one or more files previously transferred to the first edge server associated with the first active location region is initiated to be transferred to the second edge server associated with the second active location region.

6. The file transfer manager according to one or more of the preceding claims, wherein, The file transfer manager is configured to: Obtain the activation location information of the one or more environmental IoT devices located within the first activation location area; Initiate the transfer of the one or more files to the first edge server associated with the first activated location region for delivery to the one or more environmental IoT devices; Initiate the transfer of one or more additional files and / or different versions of the one or more files to the first edge server associated with the first activated location region for delivery to one or more environmental IoT devices.

7. The file transfer manager according to one or more of the preceding claims, wherein, The one or more files are used for multiple environmental IoT devices, and the file transfer manager is configured to: The activation location function according to claim 2 is used to determine the first activation location region as the activation location region of at least one of the plurality of environmental IoT devices; Initiate the transmission of at least one file to the first edge server for the plurality of environmental IoT devices.

8. The file transfer manager according to one or more of the preceding claims, wherein, The one or more files are used for multiple environmental IoT devices, and the file transfer manager is configured to obtain group definitions for the multiple environmental IoT devices and manage file transfers to at least one of the first edge server and the second edge server according to the group definitions, wherein, optionally, the group definitions are reconfigurable.

9. A 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, which is configured to be customized by the first edge server and / or the second edge server for at least one environmental IoT device, wherein, optionally, the file transfer manager provides the customized 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 an activation location region, and wherein the edge server is configured to receive and store one or more files to be delivered to one or more environmental IoT devices in the activation location region under the coordination of the file transfer manager, wherein the edge server is optionally further configured to perform at least one of the following: initiating activation of the one or more environmental IoT devices to deliver the one or more files and delivering the one or more files to the one or more environmental IoT devices when activation of the one or more environmental IoT devices is indicated.

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 one or more files stored on the edge server.

12. The edge server according to claim 10 or 11, wherein, The edge server is configured to track the delivery of the one or more files to the environmental IoT device, and optionally, upon request from the file transfer manager, to transmit a file delivery status indication to the file transfer manager.

13. The edge server according to claim 12, wherein, The edge server is configured to receive an acknowledgment signal from the one or more environmental IoT devices, and wherein the edge server is configured to construct a file delivery status indication for transmission to the file transfer manager based on the acknowledgment signal.

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

15. The edge server according to one or more of claims 10-13, wherein, The edge server is configured to receive customizable files under the coordination of the file transfer manager, and the edge server is also configured to customize the customizable files for the one or more environmental IoT devices, wherein, optionally, the edge server applies a customized application received from the file transfer manager.

Images