Content delivery network data sharing between mobile devices

Abstract

A mobile communication device is configured to receive updated network data, such as updated content delivery network (CDN) data for accessing a first network, without having to access the first network and a second network, such as a Wi-Fi or cellular network. The mobile communication device periodically transmits a beacon signal indicating a network data request for the updated network data via a peer-to-peer (P2P) network. The rate at which the mobile communication device periodically transmits the beacon signal is based on various criteria, such as an origination date of network data stored on the mobile communication device, an amount of time between the origination date and a current date, a battery health of the mobile communication device, and / or various inputs to the mobile communication device. Additionally mobile communication devices receive the beacon signal and transmit the updated network data to the mobile communication device.

Description

[0001] Cross-references to related applications

[0002] This application claims priority to U.S. Provisional Application No. 63 / 245070, filed September 16, 2021, entitled “CONTENT DELIVERY NETWORK DATASHARING BETWEEN MOBILE DEVICES,” which is incorporated herein by reference in its entirety for all purposes. Background Technology

[0003] This disclosure relates in its entirety to data sharing between mobile communication devices. More specifically, this disclosure relates to data sharing in a content delivery network (CDN) between mobile communication devices.

[0004] Mobile communication devices can utilize various networks, such as cellular networks, Wi-Fi networks, terrestrial networks, and non-terrestrial (e.g., satellite) networks, to transmit and / or receive data. In some cases, mobile communication devices receive network data, such as Content Delivery Network (CDN) data, containing information that enables the mobile communication device to access a first network (such as a cellular or satellite network). For example, network data may include the projected characteristics of the first network over time, such as the location of projected network nodes over time, the projected frequency channel used by the first network over time, etc. Unfortunately, if the network data is not periodically refreshed, the deviation between the actual characteristics and the projected characteristics of the first network can increase over time. Therefore, the network data and corresponding projected characteristics of the first network may become unreliable. Additionally or alternatively, the network data received by the mobile communication device may include the projected characteristics of the first network over a finite time period, such as two weeks. Therefore, the network data and corresponding projected characteristics of the first network become expired after the finite time period has elapsed, even if they were reliable during the duration of the finite time period. Summary of the Invention

[0005] In one embodiment, a mobile communication device includes: a transmitter; a memory configured to store first content delivery network (CDN) data; and processing circuitry communicatively coupled to the memory and the transmitter, and configured to cause the transmitter to transmit a beacon signal indicating a CDN sharing request for second CDN data via a peer-to-peer (P2P) network.

[0006] In another embodiment, a mobile communication device includes: a transceiver; a memory configured to store Content Delivery Network (CDN) data; and processing circuitry communicatively coupled to the memory and the transceiver, and configured to cause the transceiver to receive, from another mobile communication device and via a peer-to-peer (P2P) network, a beacon signal indicating a CDN sharing request for the CDN data. The processing circuitry is also configured to cause the transceiver to transmit the CDN data to the other mobile communication device via the P2P network.

[0007] In another embodiment, a non-transitory computer-readable medium includes instructions that, when executed by one or more processors, are configured to cause the one or more processors to transmit a beacon signal indicating a request for content delivery network (CDN) data sharing via a peer-to-peer (P2P) network through a transmitter of the mobile communication device when the mobile communication device is unable to access Wi-Fi and cellular networks. These instructions, when executed by the one or more processors, are also configured to cause the one or more processors to receive the CDN data from another mobile communication device via a receiver of the mobile communication device and through the P2P network.

[0008] Various modifications to the above-described features may exist with respect to various aspects of the invention. Other features may also be incorporated into these aspects. These modifications and additional features may exist individually or in any combination. For example, various features discussed below relating to one or more illustrated embodiments may be incorporated individually or in any combination into any of the above aspects of the invention. The brief summary presented above is intended only to familiarize the reader with specific aspects and context of the embodiments disclosed herein and does not limit the claimed subject matter. Attached Figure Description

[0009] Various aspects of this disclosure can be better understood by reading the following detailed description and referring to the accompanying drawings, wherein similar figures refer to similar parts.

[0010] Figure 1 This is a block diagram of an electronic device according to an embodiment of the present disclosure;

[0011] Figure 2 It is based on the implementation scheme of this disclosure. Figure 1 Functional diagram of electronic devices;

[0012] Figure 3 It is shown in the embodiments of this disclosure. Figure 1 A block diagram illustrating the communication coupling between one electronic device and another electronic device via a peer-to-peer (P2P) network.

[0013] Figure 4 It is in accordance with the implementation scheme of this disclosure Figure 1 A process flow diagram of a method for sharing network data, such as Content Delivery Network (CDN) data, between electronic devices and other electronic devices;

[0014] Figure 5 It is shown in the embodiments of this disclosure. Figure 1 A diagram illustrating how an electronic device uses a time-based standard to determine the frequency or rate at which it requests network data from another electronic device.

[0015] Figure 6 It is shown in the embodiments of this disclosure. Figure 1 A diagram illustrating how an electronic device uses a priority index table to determine the frequency or rate at which it requests network data from other electronic devices.

[0016] Figure 7 Based on the implementation scheme of this disclosure Figure 6 The priority index table in Figure 1 A process flow diagram illustrating a method for sharing network data between electronic devices and other electronic devices; and

[0017] Figure 8 It is in accordance with the implementation scheme of this disclosure Figure 1 A map displayed on the screen of an electronic device and used by the user of the electronic device to reach a point of sufficient proximity to another electronic device used for sharing network data. Detailed Implementation

[0018] This disclosure relates to sharing network data, such as content delivery network (CDN) data, between mobile communication devices via a peer-to-peer (P2P) network. For example, mobile communication devices may utilize various networks to transmit and / or receive data. Mobile communication devices may access a first network (e.g., a non-terrestrial network, a satellite network) via network data (such as CDN data) that includes the projected characteristics of the first network. The projected characteristics of the first network may include the projected network node locations of the first network at a given point in time, the projected frequency channels used by the first network at that point in time, etc. However, the actual characteristics of the first network may deviate from the projected characteristics. Furthermore, the deviation between the actual characteristics and the projected characteristics of the first network may increase over time. Therefore, the projected characteristics may become unreliable, and the mobile communication device may be unable to access the first network.

[0019] Furthermore, each instance of network data received by the mobile communication device may include the projected characteristics of the first network over a limited time period, such as two weeks. Therefore, even if the network data is reliable enough within a limited time period, it may eventually expire. Generally, the mobile communication device periodically downloads updated network data from the data source when it connects to a second network (such as Wi-Fi or a cellular network) different from the first network. In practice, the network data corresponding to the first network may be too large to be downloaded via the first network, the first network may be periodically inaccessible due to the incompatible locations of network nodes relative to the mobile communication device, and / or the first network may only be accessible to the mobile communication device during emergency scenarios.

[0020] According to embodiments of the present invention, a mobile communication device may include features configured to enable the mobile communication device to receive network data without connection to a central server (such as a second network, e.g., Wi-Fi or a cellular network). This may be the case when the mobile communication device is located in a remote location that does not provide access to a second network. For example, the mobile communication device may be equipped with components and control logic that enable the mobile communication device to receive network data from another mobile communication device via a third network, such as a P2P network, different from the first and second networks. The mobile communication device may periodically transmit beacon signals indicating a network data sharing request for updated network data (e.g., CDN data) via the P2P network. The mobile communication device may determine the frequency of transmitting the beacon signals based on various criteria. Criteria may include, for example, the origin date of the network data stored on the mobile communication device, the amount of time between the origin date and the current date, the battery health of the mobile communication device, whether the mobile communication device has received input indicating an emergency (e.g., associated with the user of the mobile communication device), and other criteria described in detail below. In some implementations, the mobile communication device may include features that enable the mobile communication device to locate an area expected to have a relatively high density of other mobile communication devices, in order to increase the likelihood that the mobile communication device will receive updated network data from one of the other mobile communication devices via a P2P network.

[0021] According to embodiments of the present invention, the mobile communication device may further include features enabling it to transmit network data to another mobile communication device that requests network data. For example, the mobile communication device may receive from the other mobile communication device a beacon signal indicating a network data sharing request for network data. The mobile communication device may present to its user an option to approve the transmission of network data residing on the mobile communication device to the other mobile communication device. In some embodiments, the mobile communication device may first determine that additional network data residing on the other mobile communication device is older than the network data residing on the mobile communication device, and then present an option to approve the transmission of network data residing on the mobile communication device to the other mobile communication device. Furthermore, in certain circumstances, such as when a user pre-approves network data transmission before the mobile communication device receives the beacon signal, the mobile communication device may automatically transmit network data to the other mobile communication device in response to the mobile communication device receiving the beacon signal.

[0022] This document provides various apparatuses and techniques to enable a mobile communication device to receive reliable network data, such as CDN data, from another mobile communication device when the mobile communication device is unable to receive network data via another means (e.g., via a Wi-Fi network connection or a cellular network connection from another data source). Furthermore, this document provides various apparatuses and techniques to enable a mobile communication device to send reliable network data (such as CDN data) to another mobile communication device that requests CDN data. These and other features are described in detail below with reference to the accompanying drawings.

[0023] In view of the foregoing, Figure 1 This is a block diagram of an electronic device or mobile communication device 10 according to an embodiment of the present disclosure. Among other things, the electronic device 10 may include one or more processors 12 (collectively referred to herein as a single processor, which may be implemented in any suitable form of processing circuitry), memory 14, non-volatile storage device 16, display 18, input structure 22, input / output (I / O) interface 24, network interface 26, and power supply 29. Figure 1 The various functional blocks shown may include hardware elements (including circuitry), software elements (including machine-executable instructions), or combinations of hardware and software elements (which may be referred to as logic). Processor 12, memory 14, non-volatile storage device 16, display 18, input structure 22, input / output (I / O) interface 24, network interface 26, and / or power supply 29 may each be directly or indirectly communicatively coupled to each other (e.g., via or through another component, communication bus, network) to transmit and / or receive data between them. It should be noted that... Figure 1 This is merely one example of a specific implementation and is intended to illustrate the types of components that may exist in electronic device 10.

[0024] For example, electronic device 10 may include any suitable computing device, including desktop computers or laptops (e.g., those available from Apple Inc., Cupertino, California). Pro, MacBook mini or Mac (in the form of) portable electronic devices or handheld electronic devices such as wireless electronic devices or smartphones (e.g., available from Apple Inc. in Cupertino, California). (Model form), tablet computers (for example, those available from Apple in Cupertino, California) (in the form of a model), wearable electronic devices (e.g., Apple products available from Apple Inc. in Cupertino, California) (in the form of) and other similar devices. It should be noted that, Figure 1 The processor 12 and other related items herein may be generally referred to as "data processing circuitry". This data processing circuitry may be embodied wholly or partially in software, hardware, or both. Furthermore, the processor 12 and... Figure 1 Other related items may be a single, independent processing module, or may be incorporated, wholly or partially, into any of the other elements within the electronic device 10. Processor 12 may be implemented using a combination of a general-purpose microprocessor, microcontroller, digital signal processor (DSP), field-programmable gate array (FPGA), programmable logic device (PLD), controller, state machine, gated logic, discrete hardware components, dedicated hardware finite state machine, or any other suitable entity capable of performing computations or other manipulations of information. Processor 12 may perform the various functions described herein.

[0025] exist Figure 1 In the electronic device 10, a processor 12 may be operatively coupled to a memory 14 and a non-volatile storage device 16 to execute various algorithms. Such programs or instructions executed by the processor 12 may be stored in any suitable article of writing comprising one or more tangible computer-readable media. The tangible computer-readable media may include the memory 14 and / or the non-volatile storage device 16, individually or jointly, to store instructions or routines. The memory 14 and the non-volatile storage device 16 may include any suitable article of writing for storing data and executable instructions, such as random access memory, read-only memory, rewritable flash memory, hard disk drive, and optical disk. Furthermore, programs (e.g., operating systems) encoded on such computer program products may also include instructions executable by the processor 12 to enable the electronic device 10 to provide various functions.

[0026] In some embodiments, display 18 may facilitate a user's viewing of images generated on electronic device 10. In some embodiments, display 18 may include a touchscreen that facilitates user interaction with the user interface of electronic device 10. Furthermore, it should be understood that in some embodiments, display 18 may include one or more liquid crystal displays (LCDs), light-emitting diode (LED) displays, organic light-emitting diode (OLED) displays, active-matrix organic light-emitting diode (AMOLED) displays, or some combination of these and / or other display technologies.

[0027] The input structure 22 of electronic device 10 allows a user to interact with electronic device 10 (e.g., press a button to increase or decrease the volume level). Like network interface 26, I / O interface 24 enables electronic device 10 to interact with a variety of other electronic devices. In some embodiments, I / O interface 24 may include I / O ports for hardwired connections for charging and / or content manipulation using standard connectors and protocols such as the Lightning connector supplied by Apple Inc. of Cupertino, California, Universal Serial Bus (USB), or other similar connectors and protocols.

[0028] Network interface 26 may include one or more interfaces for, for example, terrestrial (e.g., land-based) networks or non-terrestrial networks (NTNs), peer-to-peer connections, personal area networks (PANs) such as ultra-wideband (UWB) or Networks, local area networks (LANs), or wireless local area networks (WLANs) that employ a protocol from the IEEE 802.11x series (e.g., Networks and / or wide area networks (WANs) such as any standards related to the 3rd Generation Partnership Project (3GPP), including, for example, third-generation (3G) cellular networks, Universal Mobile Telecommunications System (UMTS), fourth-generation (4G) cellular networks, Long Term Evolution (LTE) networks, and wide area networks (WANs). Cellular networks, Long Term Evolution License Assisted Access (LTE-LAA) cellular networks, fifth-generation (5G) cellular networks, and / or New Radio (NR) cellular networks, etc. Network interface 26 can further communicate via segments of the NTN or such networks using airborne or space-based vehicles (e.g., satellites). As used herein, an airborne vehicle refers to a High Altitude Platform (HAP) operating at high altitudes, encompassing satellites, unmanned aerial vehicle systems (UAS) including tethered UAS, lighter-than-air UAS, and heavier-than-air UAS; typically between 8 km and 50 km, quasi-stationary. Specifically, network interface 26 may include, for example, one or more interfaces for cellular communication standards using 5G specifications including millimeter-wave (mmWave) frequency ranges (e.g., 24.25–300 GHz). Network interface 26 of electronic device 10 may allow communication via the aforementioned networks (e.g., 5G, Wi-Fi, LTE-LAA, etc.). Network interface 26 may also include one or more interfaces for, for example, a broadband fixed wireless access network (e.g., Mobile broadband wireless network (mobile) Asynchronous digital subscriber lines (e.g., ADSL, VDSL) and digital video terrestrial broadcasting Network and its extensions DVB handheld Networks, UWB networks, AC power lines, etc. Network interface 26 may, for example, include a transceiver 30 for transmitting data using one of the aforementioned networks. The power supply 29 of electronic device 10 may include any suitable power source, such as a rechargeable lithium polymer (Li-poly) battery and / or an AC power converter.

[0029] Figure 2 It is based on the implementation scheme of this disclosure. Figure 1 A functional diagram of an electronic device 10 or a mobile communication device. As shown, the processor 12, memory 14, transceiver 30 (shown as 30A-30N, collectively referred to as transceiver 30), transmitter 52 of transceiver 30, receiver 54 of transceiver 30, and / or antenna 55 (shown as 55A-55N, collectively referred to as antenna 55) may be directly or indirectly communicatively coupled to each other (e.g., through or via another component, communication bus, network) to transmit and / or receive data between each other.

[0030] Electronic device 10 may include transmitter 52 and / or receiver 54, which respectively enable the transmission and reception of data between electronic device 10 and external devices via, for example, a network (e.g., including a base station) or a direct connection. As shown, transmitter 52 and receiver 54 may be combined into transceiver 30. Electronic device 10 may also have one or more antennas 55A to 55N electrically coupled to transceiver 30. Antennas 55A-55N may be configured in an omnidirectional or directional configuration, a single-beam, dual-beam, or multi-beam arrangement, etc. Each antenna 55 may be associated with one or more beams and various configurations. In some embodiments, multiple antennas of antennas 55A to 55N in an antenna group or module may be communicatively coupled to a respective transceiver 30 and each transmits a radio frequency signal that can be advantageously and / or destructively combined to form a beam. Electronic device 10 may include multiple transmitters, multiple receivers, multiple transceivers (e.g., transceivers 30A-30N), and / or multiple antennas suitable for various communication standards. For example, electronic device 10 may include a first transceiver 30A that transmits and receives messages using a first wireless communication (e.g., satellite or non-terrestrial) network, a second transceiver 30B that transmits and receives messages using a second wireless communication (e.g., Wi-Fi or cellular) network, and a third transceiver 30N that transmits and receives messages using a third wireless communication (e.g., P2P) network, but any or all of these transceivers may be combined into a single transceiver. In some embodiments, transmitter 52 and receiver 54 may transmit and receive information via other wired or wired systems or devices.

[0031] Electronic device 10 may also include one or more cameras or image or light sensors (e.g., as part of input structure 22). One or more cameras or image or light sensors (collectively referred to herein as “camera 56”) can capture images or determine the amount of light around electronic device 10. In some embodiments, camera 56 may include a front-facing camera (e.g., disposed on the display surface of electronic device 10 having display 18) and / or a rear-facing camera (e.g., disposed on the base or back surface of electronic device 10 opposite to the display surface).

[0032] Electronic device 10 may include one or more motion sensors 58 (e.g., as part of input structure 22). One or more motion sensors (collectively referred to herein as "motion sensors 58") may include accelerometers, gyroscopes, rotation testers, etc., that detect or facilitate the determination of the orientation (e.g., including pitch, yaw, roll, etc.) and / or motion of electronic device 10.

[0033] As shown in the figure, various components of electronic device 10 can be coupled together via bus system 60. Bus system 60 may include, for example, a data bus, as well as power buses, control signal buses, and status signal buses in addition to the data bus. Components of electronic device 10 can be coupled together or use some other mechanism to accept or provide input to each other.

[0034] As previously described, and according to this disclosure, electronic device 10 can access various networks to transmit and / or receive data. For example, electronic device 10 can access Wi-Fi or cellular networks to transmit and / or receive data. Under certain conditions, electronic device 10 may be unable to access Wi-Fi and cellular networks. Therefore, when electronic device 10 cannot access Wi-Fi and cellular networks, electronic device 10 can access different networks, such as satellite networks or non-terrestrial networks. For example, electronic device 10 can receive and utilize network data, such as Content Delivery Network (CDN) data, to access satellite networks or non-terrestrial networks.

[0035] Network data may include the projection characteristics of satellite or non-terrestrial networks over time, such as the location of network nodes (e.g., satellites, HAPs) of the satellite or non-terrestrial network at a given point in time, the frequency channel of the satellite or non-terrestrial network at a given point in time, etc. These projection characteristics may deviate from the actual characteristics of the satellite or non-terrestrial network over time. Furthermore, network data including information related to projection characteristics may eventually expire. Therefore, when network data becomes unreliable and / or nears expiration, electronic device 10 may download updated network data. In cases where electronic device 10 cannot access Wi-Fi networks, cellular networks, satellite networks, or non-terrestrial networks to download updated network data related to satellite or non-terrestrial networks, electronic device 10 according to this disclosure may request updated network data from other electronic devices via a peer-to-peer network between electronic device 10 and other electronic devices. It should be understood that a peer-to-peer or device-to-device network may include a network of interconnected nodes or "peers" (e.g., including electronic device 10 and other electronic devices) that share resources with each other without using a centralized management system. Therefore, a peer-to-peer network can operate without a central server.

[0036] In view of the foregoing, Figure 3 It is shown Figure 1 A block diagram illustrating an embodiment of a communication coupling 100 between electronic device 10 and another electronic device 110 via a peer-to-peer (P2P) network. The communication coupling 100 in the illustrated embodiment is a P2P communication coupling. It should be noted that... Figure 3 The electronic device 10 and the other electronic device 110 shown are relative to Figure 1 and Figure 2 The electronic device 10 shown is simplified, but Figure 3Electronic device 10 and other electronic device 110 may include those with Figure 1 and Figure 2 The features presented are the same or similar. For example, the additional electronic device 110 includes an additional processor 112, an additional memory 114, an additional display 118, an additional power supply 129, an additional transceiver 130, and one or more additional antennas 155. Furthermore, the electronic device 10 is referred to below as the first mobile communication device 10, and the additional electronic device 110 is referred to below as the second mobile communication device 110.

[0037] As previously described, in some cases, the first mobile communication device 10 may be unable to access certain networks, such as Wi-Fi networks and / or cellular networks. As an alternative to Wi-Fi and cellular networks, the first mobile communication device 10 may attempt to access different networks, such as satellite or non-terrestrial networks. For example, access to satellite or non-terrestrial networks may depend on the first mobile communication device 10 utilizing network data stored thereon, such as CDN data, including the projection characteristics of the satellite or non-terrestrial network (e.g., network node location at a given point in time, frequency channel at a given point in time, etc.). For example, CDN data may include ephemeris data (e.g., a set of parameters that enables an accurate determination of the network node location or projected network node location at a specific time, including the current time or a future time). If the network data is unreliable due to discrepancies between the actual and projected characteristics of the satellite or non-terrestrial network, or if the network data expires, the first mobile communication device 10 may be unable to access the satellite or non-terrestrial network.

[0038] Furthermore, in some cases, even if the network data is reliable and not expired, the first mobile communication device 10 may be unable to access satellite or non-terrestrial networks (or otherwise be unable to receive network data via access to satellite or non-terrestrial networks). For example, the location of a network node may be periodically incompatible with the location of the first mobile communication device 10, or the file size containing the network data may be too large to be transmitted to the first mobile communication device 10 via a satellite network. According to an embodiment of the present invention, the first mobile communication device 10 may utilize the P2P communication coupling 100 between the first mobile communication device 10 and the second mobile communication device 110 to attempt to receive updated network data from the second mobile communication device 110.

[0039] For example, the first mobile communication device 10 may determine that network data stored on the first mobile communication device 10 (e.g., stored in memory 14, storage device 16, or a separate storage location) is expired, relatively old, or otherwise unreliable or nearly unreliable. The processor 12 of the first mobile communication device 10 may initiate a beacon transmitted via the transceiver 30 and corresponding antenna 55 of the first mobile communication device 10, the beacon corresponding to a network data sharing request from the second mobile communication device 110 for updated network data. When the mobile communication devices 10 and 110 are within sufficient proximity to each other, in response to a beacon initiated by the processor 12 of the first mobile communication device 10, or a combination thereof, a P2P communication coupling 100 may be established between the first mobile communication device 10 and the second mobile communication device 110.

[0040] A second mobile communication device 110 receives a beacon from a first mobile communication device 10 via a P2P communication coupling 100. In some embodiments, the second mobile communication device 110 displays data indicating the beacon on its display 118. A user of the second mobile communication device 110 can approve the transmission of network data stored on the second mobile communication device 110 (e.g., stored in memory 114 or another storage location) to the first mobile communication device 10. In some embodiments, the beacon includes data indicating the origin date of the network data stored on the first mobile communication device 10. In such embodiments, the second mobile communication device 110 may first determine that the network data stored on the second mobile communication device 110 is newer than the network data stored on the first mobile communication device 10, and then present an option to transmit or share network data via the P2P communication coupling 100 on the display 118 of the second mobile communication device 110. The second mobile communication device 110 transmits network data to the first mobile communication device 10 in response to the selection of the option to transmit or share network data.

[0041] As described above, a P2P communication coupling 100 can be established when the first mobile communication device 10 and the second mobile communication device 110 are within sufficient proximity of each other, for example, via a beacon from the first mobile communication device 10. Furthermore, the transmission of updated network data from the second mobile communication device 110 to the first mobile communication device 10 may depend on the user of the second mobile communication device 110 who has approved the transmission. For these and other reasons, the first mobile communication device 10 may send multiple beacon signals until it receives updated network data. The frequency or rate at which the first mobile communication device 10 transmits beacon signals may be based on various criteria, including the origin date of the network data residing on the mobile communication device, the amount of time between the origin date and the current date, the battery health of the mobile communication device, whether the mobile communication device has received input indicating an emergency (e.g., associated with the user of the mobile communication device), etc. These and other features will be described in detail below with reference to the accompanying drawings.

[0042] Figure 4 Is Figure 1 A process flow diagram of method 160 for sharing network data (such as Content Delivery Network (CDN) data) between electronic device 10 (hereinafter referred to as first mobile communication device 10) and another electronic device 110 (hereinafter referred to as second mobile communication device 110). In the illustrated embodiment, method 160 is divided between actions taken by first mobile communication device 10 and actions taken by second mobile communication device 110 (e.g., via line 162). At block 164, first mobile communication device 10 determines whether a first origin date of first CDN data stored on first mobile communication device 10 is older than a threshold time amount. In other words, first mobile communication device 10 determines whether the difference between the current date and the first origin date is greater than a threshold time amount. The threshold amount may be based on the possibility that network data older than the threshold time amount is unreliable and / or expired. For example, the threshold time amount may be any number of days, such as one day, two days, three days, four days, five days, six days, or up to fourteen days (or more days in some embodiments).

[0043] If the first origin date of the network data stored on the first mobile communication device 10 is not older than a threshold time amount, method 160 may return to box 164. In some embodiments, method 160 includes waiting at box 166 for a duration before returning to box 164, or waiting until the first origin date is older than a threshold time amount, and then proceeding to box 168.

[0044] At box 168, the first mobile communication device 10 transmits a beacon signal via a P2P network indicating a network data sharing request for second network data (e.g., CDN data), the second network data having a second origin date newer than the first origin date. As will be understood in view of the following figures and their description, the first mobile communication device 10 transmits multiple beacon signals at a rate or frequency determined by the first mobile communication device 10 based on various criteria (such as the age of the first origin date, the battery health of the first mobile communication device 10, whether the first mobile communication device 10 has received input indicating an emergency (e.g., indicating that the user of the first mobile communication device 10 is lost or injured), etc.).

[0045] At frame 170, the second mobile communication device 110 receives a beacon signal from the first mobile communication device 10 via a P2P network. As previously described, a beacon signal is established when the first mobile communication device 10 and the second mobile communication device 110 are within sufficient proximity to each other. Figure 3 The P2P communication coupling 100 shown is illustrated. The P2P network may include, for example, a Bluetooth network, a Bluetooth Low Energy (“Bluetooth LE”) network, a P2P Wi-Fi network, a near-field communication network, etc. It should be noted that multiple instances of the second mobile communication device 110 may receive beacon signals from the first mobile communication device 10, thereby increasing the likelihood that one or more of the second mobile communication devices 110 will transmit updated network data to the first mobile communication device 10.

[0046] At block 172, the second mobile communication device 110 determines whether a second origin date of network data (e.g., CDN data) stored on the second mobile communication device 110 is newer than a first origin date of network data (e.g., CDN data) stored on the first mobile communication device 10. For example, in some embodiments, a beacon signal transmitted from the first mobile communication device 10 to the second mobile communication device 110 includes data indicating the first origin date, and the second mobile communication device 110 compares the first origin date with the second origin date associated with the network data stored on the second mobile communication device 110. If the second origin date is not newer than the first origin date, the operation of the second mobile communication device 110 ends at block 174.

[0047] If the second mobile communication device 110 determines that the second origination date is newer than the first origination date, method 160 proceeds to block 176. However, in some embodiments, the beacon signal received by the second mobile communication device 110 does not contain data indicating the first origination date associated with the first mobile communication device 10. In this case, method 160 proceeds directly from block 170 to block 176. At block 176, the second mobile communication device 110 presents an option (e.g., a display 118 presented to the second mobile communication device 110) to share second network data (e.g., second CDN data) with the first mobile communication device 10. The user of the second mobile communication device 110 can choose to share the second network data with or without the first mobile communication device 10. In some embodiments, the second mobile communication device 110 may be configured by the user or default to sharing the second network data with or without other mobile communication devices (e.g., including the first mobile communication device 10).

[0048] At block 178, the second mobile communication device 110 transmits second network data to the first mobile communication device 10 via a P2P network and in response to the selection of an option to share second network data. At block 180, the first mobile communication device 10 receives the second network data from the second mobile communication device 110. The first mobile communication device 10 downloads the second network data and uses the second network data to access a network (e.g., a satellite or non-terrestrial network) associated with the second (or updated) network data received from the second mobile communication device 110.

[0049] As previously described, the first mobile communication device 10 continues to transmit beacon signals (e.g., at block 168) until the beacon signals are received and acknowledged by an instance of the second mobile communication device 110. The reliability of network data stored on the first mobile communication device 10 (i.e., before receiving updated network data) can decrease over time and eventually expire. Therefore, the need for updated network data (e.g., CDN data) can increase over time. Furthermore, transmitting beacon signals for updated network data via a P2P network can tend to deplete the battery life of the power supply 29 of the first mobile communication device 10. Therefore, as described in detail below, the first mobile communication device 10 may consider various criteria (e.g., the age of the network data stored on the first mobile communication device 10, the battery life of the power supply 29 of the first mobile communication device 10, etc.) to determine the rate or frequency (e.g., how frequently) of transmitting beacon signals until the beacon signals are answered.

[0050] Figure 5This is a schematic diagram illustrating an embodiment of a first mobile communication device 10 determining a time-dependent standard for the frequency or rate 200 of network data used to request updates from a second mobile communication device 110. The rate 200 may include, for example, the number of beacon signals transmitted by the mobile communication device 10 per minute, wherein the rate 200 depends on the age 201 of the network data stored on the mobile communication device 10 (e.g., the number of days that have elapsed since the date the network data was first transmitted). In the illustrated embodiment, if the age 201 of the network data is between three days 204 and six days 206, the rate 200 includes a first rate 205 of one beacon signal every 120 minutes. If the age 201 is between six days 206 and nine days 208, the rate 200 includes a second rate 207 of one beacon signal every 60 minutes. If the age 201 is between nine days 208 and twelve days 210, the rate 200 includes a third rate 209 of one beacon signal every 20 minutes. If age 201 is between 12 days 210 and 14 days 212, then rate 200 includes a fourth rate 211 of one beacon signal every two minutes. As previously stated, in Figure 4 In method 160 shown, at box 168, the rate 200 for frequently transmitting beacon signals is determined by the mobile communication device 10 (e.g., until the beacon signal is answered, such as...). Figure 4 (As shown in boxes 178 and 180). It should be noted that, Figure 5 Provided only as an example, and the control logic used to determine the beacon signal transmission rate 200 based on the age 201 of network data stored on the mobile communication device 10 may be different.

[0051] It is also possible for the mobile communication device 10 to determine the rate at which it requests network data, such as CDN data, using other technologies. In fact, the mobile communication device 10 may consider standards other than the age 201 of the network data stored on the mobile communication device 10 to determine the rate at which it sends beacon signals indicating a network sharing request for updated network data. For example, Figure 6 It is shown Figure 1 A schematic diagram of a table 230 showing the priority index used by an electronic device 10 (hereinafter referred to as mobile communication device 10) to determine the rate at which it requests network data from another mobile communication device 110. Figure 6 The following detailed description follows the initial description. Figure 7 Based on Figure 6 The process flow diagram of method 250 for sharing network data such as CDN data between mobile communication device 10 and another mobile communication device 110, with table 230 of medium priority index.

[0052] exist Figure 6Table 230 includes a priority index column 232 and a standard column 234. Priority index column 232 includes a zero-priority index 236, a default priority index 238, a first-priority index 240, a second-priority index 242, and a third-priority index 244. Zero-priority index 236 corresponds to the zero standard set 237 in standard column 234, default priority index 238 corresponds to the default standard set 239 in standard column 234, first-priority index 240 corresponds to the first standard set 241 in standard column 234, second-priority index 242 corresponds to the second standard set 243 in standard column 234, and third-priority index 244 corresponds to the third standard set 245 in standard column 234.

[0053] If the age of the network data (e.g., CDN data) on mobile communication device 10 is between zero and five days, then the zero criterion set 237 corresponding to the zero priority index 236 is satisfied. That is, the zero criterion set 237 is satisfied regardless of the battery health (e.g., state of charge percentage) of mobile communication device 10 and regardless of any user input of mobile communication device 10 associated with the network data request. If any of the other criterion sets 237, 241, 243, and 245 are not satisfied, then the default criterion set 239 corresponding to the default priority index 238 is satisfied.

[0054] If the battery health (e.g., state of charge percentage) of mobile communication device 10 is low (e.g., below a first battery health threshold), no emergency input has been entered into mobile communication device 10 (or a non-emergency input has been entered), and the age of the network data stored on mobile communication device 10 is between 0 and 10 days, then the first standard set 241 corresponding to the first priority index 240 is satisfied. The first battery health threshold can be, for example, 10%, 20%, or 30% state of charge. If an emergency input has been entered into mobile communication device 10 and the age of the network data stored on mobile communication device 10 is between five and 15 days, then the second standard set 243 corresponding to the second priority index 242 is satisfied. Therefore, the second standard set 243 does not include the battery health (e.g., state of charge percentage) of mobile communication device 10. If the network data stored on mobile communication device 10 expires (or if no network data is stored on mobile communication device 10), then the third standard set 245 corresponding to the third priority index 244 is satisfied.

[0055] It should be pointed out that, Figure 6This is provided merely as an example of how mobile communication device 10 may consider various criteria (e.g., the age of network data stored on mobile communication device 10, the presence of an emergency, and the battery health of mobile communication device 10), and other control logic may be employed, including differences in the allocation of various criteria to various priority indices. Furthermore, it should be noted that some of the criteria sets 237, 239, 241, 243, and 245 described above may include overlapping parameters, and the state of mobile communication device 10 may satisfy multiple criteria sets 237, 239, 241, 243, and 245. However, as should be understood from the following description, mobile communication device 10 may consider criteria sets 237, 239, 241, 243, and 245 in an ordered sequence. Therefore, once one of the criteria sets 237, 239, 241, 243, and 245 is satisfied, mobile communication device 10 may select the corresponding priority index 236, 238, 240, 242, or 244 and disregard the remaining criteria sets.

[0056] As previously stated, Figure 7 Based on Figure 6 Table 230 of the priority index is a flow chart of a method 250 for sharing network data, such as CDN data, between mobile communication device 10 and another mobile communication device 110. At block 252 in the illustrated embodiment, mobile communication device 10 transitions from an area with Wi-Fi or cellular network coverage to an area without coverage. Therefore, mobile communication device 10 cannot download updated network data (e.g., CDN data) corresponding to another network, such as a satellite or non-terrestrial network, via a Wi-Fi or cellular network connection.

[0057] At block 254, the processor 12 of the mobile communication device 10 receives an indication or selection of one or more options associated with network data sharing, including an option to automatically share and receive CDN data, an option to manually trigger a search for CDN data, and / or an option to input an indication of an emergency. In some embodiments, the option to manually trigger a search for CDN data automatically triggers an emergency. That is, the option to manually trigger a search for CDN data may correspond to inputting an indication of an emergency to the mobile communication device 10. As described above and in more detail below, the selection of the various available options may affect the rate at which the mobile communication device 10 transmits a beacon signal indicating a CDN data sharing request for updated CDN data.

[0058] At box 256, the processor 12 of the mobile communication device 10 determines whether the age of the CDN data stored on the mobile communication device 10 is between zero days and five days. If the CDN data stored on the mobile communication device 10 is between zero days and five days, then regardless of battery health (e.g., state of charge percentage) and user input, the processor 12 determines the age corresponding to the data from... Figure 6 The zero-priority index 236 of the zero standard set 237 applies, which corresponds to transmitting a beacon signal once every 240 minutes. If the processor 12 determines that the age of the CDN data is not between zero days and five days, method 250 proceeds to box 260.

[0059] At box 260, the processor 12 of the mobile communication device 10 determines whether the battery health (e.g., state of charge percentage) is low (e.g., below a minimum battery health threshold), whether an emergency input has not been entered (or a non-emergency input has been entered), and whether the age of the CDN data is between 0 and 10 days. In other words, the mobile communication device 10 determines whether the data originates from... Figure 6 Whether the first standard set 241 and the corresponding first priority index 240 are applicable. If yes, then method 250 proceeds to block 262, whereby processor 12 transmits a beacon signal indicating a CDN data sharing request for updated CDN data every 60 minutes via transmitter 52. Otherwise, method 250 proceeds to block 264.

[0060] At box 264, the processor 12 of the mobile communication device 10 determines whether an input indicating an emergency has been entered, and whether the age of the CDN data stored on the mobile communication device 10 is between five and 15 days, regardless of battery health (e.g., state of charge percentage). In other words, the processor 12 determines whether the input comes from... Figure 6 Whether the second standard set 243 and the corresponding second priority index 242 are applicable. If yes, then method 250 proceeds to block 266, where processor 12 transmits a beacon signal indicating a CDN data sharing request for updated CDN data every 20 minutes via transmitter 52. Otherwise, method 250 proceeds to block 268.

[0061] At box 268, the processor 12 of the mobile communication device 10 determines whether the CDN data stored on the mobile communication device 10 has expired, regardless of battery health (e.g., state of charge percentage) and regardless of any input from the user to the mobile communication device 10. In other words, the mobile communication device 10 determines whether the CDN data is due from... Figure 6 Whether the third standard set 245 and the corresponding third priority index 244 are applicable. If yes, then method 250 proceeds to block 270, where processor 12 transmits a beacon signal indicating a CDN data sharing request for updated CDN data every 3 minutes via transmitter 52. Otherwise, method 250 proceeds to block 272.

[0062] At box 272, the processor 12 of the mobile communication device 10 (e.g., after excluding all other standard sets and priority indices) determines the source from Figure 6The default standard set 239 and the corresponding default priority index 238 apply. Then, method 250 proceeds to block 274, where processor 12 transmits a beacon signal indicating a CDN data sharing request for updated CDN data every 120 minutes via transmitter 52. Block 276 in the illustrated method 250 indicates that the beacon signal indicating a CDN data sharing request for CDN data is transmitted at a rate determined by the processor 12 of the mobile communication device 10 at blocks 258, 262, 266, 270, or 274.

[0063] As previously described, this disclosure relates to network data sharing (e.g., CDN data sharing) between mobile communication devices 10 and 110 via a P2P network. The P2P network connection depends on the proximity between the mobile communication devices 10 and 110. Therefore, the mobile communication device 10 requesting updated network data is equipped with components that facilitate the display of a map on the mobile communication device 10's screen, wherein the map allows a user to move the mobile communication device 10 to an area with a relatively high density of other mobile communication devices 110 capable of sharing network data with it. Figure 8 yes Figure 1 The map 300 is displayed on the display 18 of the electronic device 10 (hereinafter referred to as mobile communication device 10).

[0064] In some implementations, mobile communication device 10 presents map 300 in an offline mode that does not require a network connection to allow the user to locate an area expected to have a relatively high density of other mobile communication devices 110. For example, the starting position 302 of mobile communication device 10 may be marked on map 300 while mobile communication device 10 accesses one or more networks. Subsequently, mobile communication device 10 may lose network access. Movement 304 of mobile communication device 10 from starting position 302 may be tracked by features on mobile communication device 10 (e.g., sensors, such as accelerometers, gyroscopes, rotation testers, etc.), which do not require a network connection to operate. The current position 306 of mobile communication device 10 may also be represented on map 300.

[0065] Furthermore, boundary markers 308 (e.g., trail start indicators) set in boundary indicators 310 (e.g., park boundary indicators) may be included on map 300 and indicate to the user of mobile communication device 10 areas that may include other mobile communication devices 110 with a relatively high or higher density than the current density. The user of mobile communication device 10 can utilize map 300 (including the indicated starting position 302, indicated movement 304, indicated current position 306, boundary markers 308 within boundary indicators 310, and other map features) to move to areas where they expect to have a relatively high or higher density of other mobile communication devices 110. In this way, the user can increase the proximity of mobile communication device 10 to one or more of the other communication devices 110 to enable data sharing between mobile communication device 10 and the other mobile communication devices 110 via a P2P network.

[0066] In some implementations, map 300 does not show the starting position 302 of mobile communication device 10, the movement of mobile communication device 10 from starting position 302 304, and / or the current position 306 of mobile communication device 10. However, map 300 still allows the user of mobile communication device 10 to identify (e.g., himself) the landmarks marked by landmark indication 308 on map 300.

[0067] Embodiments of this disclosure relate to mobile communication devices that transmit and receive network data, such as CDN data for accessing satellite or non-terrestrial networks, via P2P networks. For example, when a first mobile communication device cannot access Wi-Fi and cellular networks and therefore cannot download updated CDN data via Wi-Fi and cellular networks, the first mobile communication device may transmit a beacon signal indicating a CDN data sharing request for the CDN data to a second mobile communication device. Technical effects associated with embodiments of this disclosure include, particularly, an improved ability to connect to networks associated with CDN data, such as satellite networks, especially when the first mobile communication device cannot access Wi-Fi and cellular networks.

[0068] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0069] The specific embodiments described above have been illustrated by way of example, and it should be understood that various modifications and alternatives are permissible. It should also be understood that the claims are not intended to limit us to the specific forms disclosed, but rather to cover all modifications, equivalents, and alternatives falling within the substance and scope of this disclosure.

[0070] The techniques described herein and protected by the claims are referenced and applied to specific examples of physical and practical nature that significantly improve the technical field and are therefore not abstract, intangible, or purely theoretical. Furthermore, if any claim appended to the end of this specification contains one or more elements designated as "means for [performing] [function]..." or "steps for [performing] [function]...", those elements shall be interpreted in accordance with 35U.SC112(f). However, for any claim containing elements designated in any other manner, those elements shall not be interpreted in accordance with 35U.SC112(f).

Claims

1. A mobile communication device comprising: a transmitter; a memory configured to store first content delivery network (CDN) data; and processing circuitry communicatively coupled to the memory and the transmitter and configured to: cause the mobile communication device to access a network via the first CDN data; cause the transmitter to transmit a plurality of beacon signals at a first rate when the first CDN data is a first age, and at a second rate greater than the first rate when the first CDN data is a second age greater than the first age, wherein each of the plurality of beacon signals indicates a CDN data sharing request for second CDN data over a peer-to-peer (P2P) network.

2. The mobile communication device of claim 1, wherein the processing circuitry is configured to cause the transmitter to transmit the plurality of beacon signals over the P2P network when the mobile communication device is unable to access a wireless service different from the network.

3. The mobile communication device of claim 1, wherein the processing circuitry is configured to cause the transmitter to transmit the beacon signals over the P2P network when a first origination date of the first CDN data is older than a threshold amount of time.

4. The mobile communication device of claim 1, wherein the first CDN data comprises information related to a location and movement of a mobile base station.

5. The mobile communication device of claim 1, wherein the first CDN data comprises first satellite ephemeris information, the second CDN data comprises second satellite ephemeris information, and the network comprises a satellite network.

6. The mobile communication device of claim 1, wherein the first rate, the second rate, or both the first rate and the second rate are further dependent on a state of charge (SOC) of a battery of the mobile communication device.

7. The mobile communication device of claim 1, wherein the first rate, the second rate, or both the first rate and the second rate are further dependent on whether the mobile communication device has received an input indicating an emergency.

8. A mobile communication device comprising: a transceiver; a memory configured to store content delivery network (CDN) data; and processing circuitry communicatively coupled to the memory and the transceiver and configured to cause the transceiver to: receive a beacon signal from another mobile communication device and over a peer-to-peer (P2P) network, the beacon signal indicating a CDN data sharing request for the CDN data, transmit the CDN data to the other mobile communication device over the P2P network, and to transmit a plurality of additional beacon signals through the P2P network at a first rate when the CDN data is a first age, and at a second rate greater than the first rate when the CDN data is a second age greater than the first age, each of the plurality of additional beacon signals indicating an additional CDN data share request for additional CDN data when the mobile communication device has no access to a Wi-Fi network and a cellular network.

9. The mobile communication device of claim 8, comprising: a display, wherein the processing circuitry is configured to: present, on the display, an option to share the CDN data with the additional mobile communication device, receive input indicating a selection of the option to share the CDN data with the additional mobile communication device, and cause the transceiver to transmit the CDN data to the additional mobile communication device through the P2P network and based on the input.

10. The mobile communication device of claim 8, wherein the beacon signal or additional signal indicates a first date of origin of pre-selected existing CDN data stored on the additional mobile communication device, and the processing circuitry is configured to transmit the CDN data to the additional mobile communication device through the P2P network when the first date of origin of the pre-selected existing CDN data is older than a second date of origin of the CDN data stored on the memory of the mobile communication device.

11. The mobile communication device of claim 8, wherein the CDN data comprises satellite ephemeris information.

12. The mobile communication device of claim 8, wherein the first rate, the second rate, or both the first rate and the second rate are further dependent on a state of charge of a battery of the mobile communication device or a rate dependent on an age of the CDN data stored on the memory of the mobile communication device, and the plurality of additional beacon signals comprises the additional beacon signal.

13. A mobile telecommunication device, comprising: means for transmitting a plurality of beacon signals through a peer-to-peer (P2P) network at a first rate when pre-existing content delivery network (CDN) data residing on the mobile telecommunication device is a first age, and at a second rate greater than the first rate when the pre-existing CDN data is a second age greater than the first age, each of the plurality of beacon signals indicating a CDN data share request for updated CDN data when the mobile telecommunication device has no access to a Wi-Fi network and a cellular network; means for receiving the updated CDN data from an additional mobile telecommunication device through the P2P network; and means for accessing a network via the updated CDN data received from the additional telecommunication device. ​ 14. The mobile telecommunication device of claim 13, wherein the pre-existing CDN data comprises satellite ephemeris information, the updated CDN data comprises updated satellite ephemeris information, and the network comprises a satellite network.

15. The mobile telecommunication device of claim 13, wherein the first rate, the second rate, or both the first rate and the second rate are further dependent on a rate of a state of charge of a battery of the mobile telecommunication device.

16. The mobile telecommunication device of claim 13, wherein the first rate, the second rate, or both the first rate and the second rate are further dependent on a rate of whether the mobile telecommunication device has received an input indicative of an emergency, the plurality of beacon signals comprising the beacon signal.

17. The mobile telecommunication device of claim 13, comprising: means for presenting a map on a display of the mobile telecommunication device in an offline mode, the map comprising an area in which the mobile telecommunication device is disposed; means for presenting a first indication of a first location of the mobile telecommunication device on the map; and means for presenting a second indication of a second location on the map that is expected to comprise a higher density of mobile telecommunication devices than the first location.

Images